- Users - oVirt List Archives

[Users] oVirt 3.3.1 RC
by Sandro Bonazzola 18 Nov '13

18 Nov '13

The oVirt team is pleased to announce that the 3.3.1 Release candidate is now available in beta [1] and will be released on Tue Nov 19th 2013 if no other blockers will be found while we're testing it [2]. Feel free to join us verifying the bugzilla entries actually under verification [3]. Release notes for this update are available on the wiki [4]. A new oVirt Node build will be available soon as well. [1] http://resources.ovirt.org/releases/beta [2] http://www.ovirt.org/Testing/Ovirt_3.3.1_testing [3] http://red.ht/1gQAdEo [4] http://www.ovirt.org/OVirt_3.3.1_release_notes -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

[Users] Fencing virtual machines
by Nicolas Ecarnot 18 Nov '13

18 Nov '13

Hi, In the case I want to setup a virtual cluster amongst many virtual machines, and this virtual cluster needs to fence some VM, what is the best way to achieve this? I guess this has to use something like vdsClient to "unplug" the VM, but I found it hard to find any more information about this. -- Nicolas Ecarnot

4 6

Re: [Users] [Spice-devel] govirt 0.30 plans
by Itamar Heim 18 Nov '13

18 Nov '13

On 11/06/2013 11:15 PM, i iordanov wrote: > Hi Christophe, > > This one may turn out to not be an actual issue. > > I had gotten used to the functionality offered by oVirt Live 0.8 (I > think it bundles oVirt 3.0) where I was able to attach as user > "admin@internal" to virtual machines created in the Administrative > Console (rather than in the User Console). > > It appears that oVirt 3.2 and 3.3 either do not allow this anymore or > something else is amiss. One may not attach to such machines despite > them being reported at /api/vms. > > To make a long story short, I made one of these machines a Template > and created a VM based on it in the User Console of admin@internal. > After that, I was able to connect! > > Do you think there is still anything wrong? Should we be able to > attach to those vms (e.g. win and winbak)? (if you see a behavior change in ovirt, you an also ask/cc on users(a)ovirt.org) in 3.0 we only allowed admin access to the API. in 3.1 we added user level access. main difference is users only get entities they have permissions with User Role on. an user with admin role can ask to get 'all', or just "me as a user" - all VMs which that admin has a User Role to. to not break api backward compatibility, default mode of the API remained 'admin mode', so you need to pass to the API "filter=true" to behave as a user. (we don't like this, and will try to come up with a better solution). i assume from Christophe next reply govirt (sensibly, as its geared for user access) default to user mode api. so you have two options - move to admin mode in govirt, or easier (and probably more consistent if you are aiming your solution for users rather than admins), give admin@internal a UserRole on the VMs, not an Admin Role. HTH, ITamar > > Cheers, > iordan > > > > On Wed, Nov 6, 2013 at 4:22 AM, Christophe Fergeau <cfergeau(a)redhat.com> wrote: >> On Tue, Nov 05, 2013 at 06:03:21PM -0600, i iordanov wrote: >>> What I have done is manually navigated to https://FQDN/api/vms in >>> order to attach the output I get there for you to see if you can spot >>> why libgovirt fails to look up the VMs. The call failed with name set >>> to both "win" and "winbak". >> >> This code is happily parsed by the attached test program, so I'm not sure >> parsing is at fault. You can look at the REST calls by setting the >> REST_DEBUG env variable to 'proxy' >> >> Christophe > > >

3 2

[Users] Ovirt 3.3 removing disk failure
by Saša Friedrich 17 Nov '13

17 Nov '13

When I try to remove viritual disk from ovirt engine I get error "User admin@internal finished removing disk test_vm with storage failure in domain DATA_DOMAIN." VM itself was running fine with no errors. DATA_DOMAIN is GlusterFS replicated volume (on ovirt host). ovirt engine comp (fc19) ovirt-engine.noarch 3.3.0.1-1.fc19 ovirt host (fc19) vdsm.x86_64 4.12.1-4.fc19 vdsm-gluster.noarch 4.12.1-4.fc19 glusterfs-server.x86_64 3.4.1-1.fc19 tnx for help

2 4

[Users] Info on snapshot removal operations and final disk format
by Gianluca Cecchi 17 Nov '13

17 Nov '13

Hello, I'm on oVirt 3.2.3-1 on a Fedora 18 all-in-one test server. I have a Windows XP VM that has a disk in qcow2 format and has a snapshot on it. When I delete the snapshot I see, from the commands intercepted, that the final effect is to have a raw disk (aka preallocated) .... is this correct and always true? Does this mean that even if I create a VM with thin provisioned disks, as soon as I take at least one snapshot and I then delete it I only have raw disks? Or am I missing anything? This what I observed: as soon as I launch delete snapshot operation: raw format of new disk vdsm 30805 1732 6 13:24 ? 00:00:00 /usr/bin/dd if=/dev/zero of=/rhev/data-center/65c9777e-23f1-4f04-8cea-e7c8871dc88b/0a8035e6-e41d-40ff-a154-e0a374f264b2/images/75c54716-5222-4ad6-91f2-8b312eacc4b4/d4fa7785-8a89-4d13-9082-52556ab0b326_MERGE bs=1048576 seek=0 skip=0 conv=notrunc count=11264 oflag=direct after about 5 minutes: convert from qemu format to raw format vdsm 31287 1732 7 13:29 ? 00:00:08 /usr/bin/qemu-img convert -t none -f qcow2 /rhev/data-center/65c9777e-23f1-4f04-8cea-e7c8871dc88b/0a8035e6-e41d-40ff-a154-e0a374f264b2/images/75c54716-5222-4ad6-91f2-8b312eacc4b4/d4fa7785-8a89-4d13-9082-52556ab0b326 -O raw /rhev/data-center/65c9777e-23f1-4f04-8cea-e7c8871dc88b/0a8035e6-e41d-40ff-a154-e0a374f264b2/images/75c54716-5222-4ad6-91f2-8b312eacc4b4/d4fa7785-8a89-4d13-9082-52556ab0b326_MERGE at the end probably there is a rename of the disk file and qemu-img info /rhev/data-center/65c9777e-23f1-4f04-8cea-e7c8871dc88b/0a8035e6-e41d-40ff-a154-e0a374f264b2/images/75c54716-5222-4ad6-91f2-8b312eacc4b4/d4fa7785-8a89-4d13-9082-52556ab0b326 image: /rhev/data-center/65c9777e-23f1-4f04-8cea-e7c8871dc88b/0a8035e6-e41d-40ff-a154-e0a374f264b2/images/75c54716-5222-4ad6-91f2-8b312eacc4b4/d4fa7785-8a89-4d13-9082-52556ab0b326 file format: raw virtual size: 11G (11811160064 bytes) disk size: 9.5G # ll /rhev/data-center/65c9777e-23f1-4f04-8cea-e7c8871dc88b/0a8035e6-e41d-40ff-a154-e0a374f264b2/images/75c54716-5222-4ad6-91f2-8b312eacc4b4/ total 9995476 -rw-rw----. 1 vdsm kvm 1048576 Nov 16 12:09 6ac73ee2-6419-43a4-91e7-7d4ef2026943_MERGE.lease -rw-rw----. 1 vdsm kvm 11811160064 Nov 16 13:32 d4fa7785-8a89-4d13-9082-52556ab0b326 -rw-rw----. 1 vdsm kvm 1048576 Mar 23 2013 d4fa7785-8a89-4d13-9082-52556ab0b326.lease -rw-rw----. 1 vdsm kvm 1048576 Nov 16 13:29 d4fa7785-8a89-4d13-9082-52556ab0b326_MERGE.lease -rw-r--r--. 1 vdsm kvm 274 Nov 16 13:29 d4fa7785-8a89-4d13-9082-52556ab0b326.meta Thanks Gianluca

2 1

Re: [Users] Users Digest, Vol 26, Issue 72
by Ryan Barry 17 Nov '13

17 Nov '13

Without knowing how the disks are split among the controllers, I don't want to make any assumptions about how shared it actually is, since it may be half and half with no multipathing. While a multi-controller DAS array *may* be shared storage, it may not be. Moreover, I have no idea whether VDSM looks at by-path, by-bus, dm-*, or otherwise, and there are no guarantees that a SAS disk will present like a FC LUN (by-path/pci...-fc-$wwn...), whereas OCFS POSIXFS is assured to work, albeit with a more complex setup and another intermediary layer. On Nov 17, 2013 10:00 AM, <users-request(a)ovirt.org> wrote: > Send Users mailing list submissions to > users(a)ovirt.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.ovirt.org/mailman/listinfo/users > or, via email, send a message with subject or body 'help' to > users-request(a)ovirt.org > > You can reach the person managing the list at > users-owner(a)ovirt.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Users digest..." > > > Today's Topics: > > 1. Re: oVirt and SAS shared storage?? (Jeff Bailey) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sat, 16 Nov 2013 21:39:35 -0500 > From: Jeff Bailey <bailey(a)cs.kent.edu> > To: users(a)ovirt.org > Subject: Re: [Users] oVirt and SAS shared storage?? > Message-ID: <52882C67.9000707(a)cs.kent.edu> > Content-Type: text/plain; charset=ISO-8859-1 > > > On 11/16/2013 9:22 AM, Ryan Barry wrote: > > > > unfortunally, I didn't got a reply for my question. So.. let's try > > again. > > > > Does oVirt supports SAS shared storages (p. e. MSA2000sa) as > > storage domain? > > If yes.. what kind of storage domain I've to choose at setup time? > > > > SAS is a bus which implements the SCSI protocol in a point-to-point > > fashion. The array you have is the effective equivalent of attaching > > additional hard drives directly to your computer. > > > > It is not necessarily faster than iSCSI or Fiber Channel; almost any > > nearline storage these days will be SAS, almost all the SANs in > > production, and most of the tiered storage as well (because SAS > > supports SATA drives). I'm not even sure if NetApp uses FC-AL drives > > in their arrays anymore. I think they're all SAS, but don't quote me > > on that. > > > > What differentiates a SAN (iSCSI or Fiber Channel) from a NAS is that > > a SAN presents raw devices over a fabric or switched medium rather > > than point-to-point (point-to-point Fiber Channel still happens, but > > it's easier to assume that it doesn't for the sake of argument). A NAS > > presents network file systems (CIFS, GlusterFS, Lustre, NFS, Ceph, > > whatever), though this also gets complicated when you start talking > > about distributed clustered network file systems. > > > > Anyway, what you have is neither of these. It's directly-attached > > storage. It may work, but it's an unsupported configuration, and is > > only shared storage in the sense that it has multiple controllers. If > > I were going to configure it for oVirt, I would: > > > > It's shared storage in every sense of the word. I would simply use an > FC domain and choose the LUNs as usual. > > > Attach it to a 3rd server and export iSCSI LUNs from it > > Attach it to a 3rd server and export NFS from it > > Attach it to multiple CentOS/Fedora servers, configure clustering (so > > you get fencing, a DLM, and the other requisites of a clustered > > filesystem), and use raw cLVM block devices or GFS2/OCFS filesystems > > as POSIXFS storage for oVirt. > > > > These would be terrible choices for both performance and reliability. > It's exactly the same as fronting an FC LUN would be with all of that > crud when you could simply access the LUN directly. If the array port > count is a problem then just toss an SAS switch in between and you have > an all SAS equivalent of a Fibre Channel SAN. This is exactly what we > do in production vSphere environments and there are no technical reasons > it shouldn't work fine with oVirt. > > > Thank you for your help > > > > Hans-Joachim > > > > > > Hans > > > > -- > > while (!asleep) { sheep++; } > > > > > > _______________________________________________ > > Users mailing list > > Users(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/users > > > > ------------------------------ > > _______________________________________________ > Users mailing list > Users(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > > > End of Users Digest, Vol 26, Issue 72 > ************************************* >

1 0

Re: [Users] oVirt and SAS shared storage??
by Ryan Barry 16 Nov '13

16 Nov '13

> > unfortunally, I didn't got a reply for my question. So.. let's try again. > > Does oVirt supports SAS shared storages (p. e. MSA2000sa) as storage > domain? > If yes.. what kind of storage domain I've to choose at setup time? > > SAS is a bus which implements the SCSI protocol in a point-to-point fashion. The array you have is the effective equivalent of attaching additional hard drives directly to your computer. It is not necessarily faster than iSCSI or Fiber Channel; almost any nearline storage these days will be SAS, almost all the SANs in production, and most of the tiered storage as well (because SAS supports SATA drives). I'm not even sure if NetApp uses FC-AL drives in their arrays anymore. I think they're all SAS, but don't quote me on that. What differentiates a SAN (iSCSI or Fiber Channel) from a NAS is that a SAN presents raw devices over a fabric or switched medium rather than point-to-point (point-to-point Fiber Channel still happens, but it's easier to assume that it doesn't for the sake of argument). A NAS presents network file systems (CIFS, GlusterFS, Lustre, NFS, Ceph, whatever), though this also gets complicated when you start talking about distributed clustered network file systems. Anyway, what you have is neither of these. It's directly-attached storage. It may work, but it's an unsupported configuration, and is only shared storage in the sense that it has multiple controllers. If I were going to configure it for oVirt, I would: Attach it to a 3rd server and export iSCSI LUNs from it Attach it to a 3rd server and export NFS from it Attach it to multiple CentOS/Fedora servers, configure clustering (so you get fencing, a DLM, and the other requisites of a clustered filesystem), and use raw cLVM block devices or GFS2/OCFS filesystems as POSIXFS storage for oVirt. Thank you for your help > > Hans-Joachim > Hans -- while (!asleep) { sheep++; }

2 1

[Users] oVirt and SAS shared storage??
by Hans-Joachim 16 Nov '13

16 Nov '13

--========GMXBoundary25901384583304721109 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Hello, unfortunally, I didn't got a reply for my question. So.. let's try again. Does oVirt supports SAS shared storages (p. e. MSA2000sa) as storage domain? If yes.. what kind of storage domain I've to choose at setup time? Thank you for your help Hans-Joachim --========GMXBoundary25901384583304721109 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable <span style=3D'font-family:Verdana'><span style=3D'font-size:12px'>Hello,<b= r /><br />unfortunally, I didn't got a reply for my question. So.. let's tr= y again.<br /><br />Does oVirt supports SAS shared storages (p. e. MSA2000s= a) as storage domain?<br />If yes.. what kind of storage domain I've to cho= ose at setup time?<br /><br />Thank you for your help<br /><br />Hans-Joach= im<br />=C2=A0</span></span> --========GMXBoundary25901384583304721109--

1 0

[Users] Low quality of el6 vdsm rpms
by Patrick Hurrelmann 15 Nov '13

15 Nov '13

Hi all, sorry for this rant, but... I now tried several times to test the beta 3.3.1 rpms, but they can't even be installed in the most times. One time it required a future selinux-policy, although the needed selinux fix was delivered in a much lower version. Now the rpms have broken requirements. It requires "hostname" instead of "/bin/hostname". This broken requirement is not included in the vdsm 3.3 branch, so I wonder where it comes from? Anyway. So I proceeded and tried to build vdsm myself once again. Currently the build fails with (but worked fine some days ago): /usr/bin/pep8 --exclude="config.py,constants.py" --filename '*.py,*.py.in' \ client lib/cpopen/*.py lib/vdsm/*.py lib/vdsm/*.py.in tests vds_bootstrap vdsm-tool vdsm/*.py vdsm/*.py.in vdsm/netconf vdsm/sos/vdsm.py.in vdsm/storage vdsm/vdsm vdsm_api vdsm_hooks vdsm_reg vdsm/storage/imageRepository/formatConverter.py:280:29: E128 continuation line under-indented for visual indent - How can the quality of the vdsm builds be increased? It is frustrating to spend time on testing and then the hosts cannot even be installed to broken vdsm rpms. - How are the builds prepared? Is there a Jenkins job that prepares "stable" rpms in addition to the nightly job? Or is this totally handcrafted? - How can it be that the rpm spec differs between the 3.3 branch and released rpms? What is the source/branch for el6 vdsm rpms? Maybe I'm just tracking on the wrong source tree... Thx and Regards Patrick -- Lobster LOGsuite GmbH, Münchner Straße 15a, D-82319 Starnberg HRB 178831, Amtsgericht München Geschäftsführer: Dr. Martin Fischer, Rolf Henrich

10 23

[Users] EL5 support for VirtIO SCSI?
by Paul Jansen 15 Nov '13

15 Nov '13

---1504104896-299338706-1384321468=:29063 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable I have just set up an Ovirt 3.3.0 install and have done a test install of C= entos 6.4 in a VM.=A0 The VM was configured with an IDE drive and a virtio-= scsi drive.=A0 The Centos 6.4 install sees both drives OK.=0AI'm wanting to= do some testing on a product that is based on EL5, but I'm finding that it= cannot see the virtio-scsi drive.=A0 It does show up in the output of 'lsp= ci', but I don't see a corresponding 'sd' device.=0A=0AI've just tried inst= alling Centos 5.10 and the support is not there.=0A=0ADoes anyone know of a= ny tricks to allow EL5 to see the virtio-scsi device? ---1504104896-299338706-1384321468=:29063 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable <html><body><div style=3D"color:#000; background-color:#fff; font-family:ti= mes new roman, new york, times, serif;font-size:12pt"><div>I have just set = up an Ovirt 3.3.0 install and have done a test install of Centos 6.4 in a V= M.  The VM was configured with an IDE drive and a virtio-scsi drive.&n= bsp; The Centos 6.4 install sees both drives OK.</div><div>I'm wanting to d= o some testing on a product that is based on EL5, but I'm finding that it c= annot see the virtio-scsi drive.  It does show up in the output of 'ls= pci', but I don't see a corresponding 'sd' device.<br></div><div>I've just = tried installing Centos 5.10 and the support is not there.</div><div><br></= div><div style=3D"color: rgb(0, 0, 0); font-size: 16px; font-family: times = new roman,new york,times,serif; background-color: transparent; font-style: = normal;">Does anyone know of any tricks to allow EL5 to see the virtio-scsi= device?<br></div><div style=3D"color: rgb(0, 0, 0); font-size: 16px; font-family: times new roman,new york,times,serif; background-color: trans= parent; font-style: normal;"><span><br></span></div></div></body></html> ---1504104896-299338706-1384321468=:29063--

9 16