Re: [Users] Migration issues with ovirt 3.3
On Fri, Oct 04, 2013 at 02:55:42PM -0300, emi...@gmail.com wrote: > Dan, I've made a whole new installation of oVirt 3.3 using the stable > repos, I've updated libvirt to 1.1.2-1 and configured a glusterFS cluster. > > I've just tried the live migration of the Windows Host, here i send you the > vdsm, libvir and qemu logs Here goes. vm.Vm._getUnderlyingDriveInfo() matches the list of disks provided by Engine with the list of disks reported back by libvirt. After a match has been found, the libvirt-assigned address of each disk is reported to Engine. _getUnderlyingDriveInfo is awfully naive. If the cdrom is empty, the function matches it with the gluster volume, and overides the cdrom's address with the gluster volume's. Would you please test if http://gerrit.ovirt.org/19906 solves the issue? (I haven't. Too late at night.) Regards, Dan. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Migration issues with ovirt 3.3
On Mon, Oct 07, 2013 at 12:25:30AM +0200, Gianluca Cecchi wrote: > I've done some further tests and comparisons Is this related to emitor's bug? For emitor, when a VM does not start it happens when libvirt recongnizes that its devices have bad addresses. It never gets to qemu command line phase. > > In this F19 based + ovirt stable repo the difference in qemu command > line between the working run once with cd enabled of this CentOS 6.4 > x86_64 and the normal run that doesn't proceed is: > > run once > -drive > file=/rhev/data-center/mnt/f18engine.mydomain:_var_lib_exports_iso/cc790a86-72e2-4aa2-a0b6-700756c399c3/images/----/CentOS-6.4-x86_64-bin-DVD1.iso,if=none,id=drive-ide0-1-0,readonly=on,format=raw,serial= > -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0,bootindex=2 > > run > -drive if=none,id=drive-ide0-1-0,readonly=on,format=raw,serial= > -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 > > > A working normal run of a WinXP 32bit VM in another oVirt 3.2.3 environment is > -drive if=none,id=drive-ide0-1-0,readonly=on,format=raw,serial= > -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 > > so it is the same as in 3.3. > > Possible problems: > > - 64bit OS > I can try tomorrow to create a CentOS 6.4 32 bit and compare results > > - qemu default emulated pc version > > Some comparisons > > a) f18 host (AIO) with oVirt 3.2.3 > > qemu-kvm-1.2.2-14.fc18.x86_64 > > [root@tekkaman polimi]# qemu-kvm -machine ? > Supported machines are: > none empty machine > pc Standard PC (alias of pc-1.2) > pc-1.2 Standard PC (default) > pc-1.1 Standard PC > pc-1.0 Standard PC > pc-0.15 Standard PC > pc-0.14 Standard PC > pc-0.13 Standard PC > pc-0.12 Standard PC > pc-0.11 Standard PC, qemu 0.11 > pc-0.10 Standard PC, qemu 0.10 > isapcISA-only PC > > When I start WinXP (32bit of course) I see this command line: > /usr/bin/qemu-kvm -name winxp -S -M pc-0.14 -cpu Opteron_G3 > > b) f19 host in oVirt 3.3 > > qemu-kvm-1.4.2-11.fc19.x86_64 > > [root@f18ovn03 ~]# qemu-kvm -machine ? > Supported machines are: > none empty machine > pc Standard PC (i440FX + PIIX, 1996) (alias of > pc-i440fx-1.4) > pc-i440fx-1.4Standard PC (i440FX + PIIX, 1996) (default) > pc-1.3 Standard PC > pc-1.2 Standard PC > pc-1.1 Standard PC > pc-1.0 Standard PC > pc-0.15 Standard PC > pc-0.14 Standard PC > pc-0.13 Standard PC > pc-0.12 Standard PC > pc-0.11 Standard PC, qemu 0.11 > pc-0.10 Standard PC, qemu 0.10 > isapcISA-only PC > q35 Standard PC (Q35 + ICH9, 2009) (alias of pc-q35-1.4) > pc-q35-1.4 Standard PC (Q35 + ICH9, 2009) > > qemu command line for a CentOS 6.4 64bit vm is: > /usr/bin/qemu-system-x86_64 -machine accel=kvm -name c6s -S -machine > pc-1.0,accel=kvm,usb=off -cpu Opteron_G2 > > both /usr/bin/qemu-kvm and /usr/bin/qemu-system-x86_64 are in > qemu-system-x86 rpm package. > > Questions: > - given a version of oVirt, pc version in qemu generated command line > is the same for every defined VM or is there any logic depending on OS > chosen and/or bit (32 vs 64)? emulatedMachine is set by the effective clusterLevel. > - if answer to previous question is fixed pc version, is there any > particular reason to use pc-0.14 in oVirt 3.2.3 and pc-1.0 in oVirt > 3.3 and not the latest available (so pc-1.2 in 3.2.3 and pc-1.3 or > pc-i440fx-1.4 in 3.3)? We promise inter-cluster migration of VMs. Hence, 3.2.3 may use only the newest machine available at 3.2.0. > - where can I find documentation about difference between the > different pc-x.y versions? I am not aware of anything beyond the qemu source code and release notes. > - can I use a wrapper in oVirt 3.3 to start VM with a different pc-x.y > (eg pc-0.14) and see if anything changes helping debug and solve the > problem? Yes, you may write a vdsm before_vm_start hook. It should search for the 'machine' attribute and set it to whatever value you please. Dan. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Migration issues with ovirt 3.3
I've done some further tests and comparisons In this F19 based + ovirt stable repo the difference in qemu command line between the working run once with cd enabled of this CentOS 6.4 x86_64 and the normal run that doesn't proceed is: run once -drive file=/rhev/data-center/mnt/f18engine.mydomain:_var_lib_exports_iso/cc790a86-72e2-4aa2-a0b6-700756c399c3/images/----/CentOS-6.4-x86_64-bin-DVD1.iso,if=none,id=drive-ide0-1-0,readonly=on,format=raw,serial= -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0,bootindex=2 run -drive if=none,id=drive-ide0-1-0,readonly=on,format=raw,serial= -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 A working normal run of a WinXP 32bit VM in another oVirt 3.2.3 environment is -drive if=none,id=drive-ide0-1-0,readonly=on,format=raw,serial= -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 so it is the same as in 3.3. Possible problems: - 64bit OS I can try tomorrow to create a CentOS 6.4 32 bit and compare results - qemu default emulated pc version Some comparisons a) f18 host (AIO) with oVirt 3.2.3 qemu-kvm-1.2.2-14.fc18.x86_64 [root@tekkaman polimi]# qemu-kvm -machine ? Supported machines are: none empty machine pc Standard PC (alias of pc-1.2) pc-1.2 Standard PC (default) pc-1.1 Standard PC pc-1.0 Standard PC pc-0.15 Standard PC pc-0.14 Standard PC pc-0.13 Standard PC pc-0.12 Standard PC pc-0.11 Standard PC, qemu 0.11 pc-0.10 Standard PC, qemu 0.10 isapcISA-only PC When I start WinXP (32bit of course) I see this command line: /usr/bin/qemu-kvm -name winxp -S -M pc-0.14 -cpu Opteron_G3 b) f19 host in oVirt 3.3 qemu-kvm-1.4.2-11.fc19.x86_64 [root@f18ovn03 ~]# qemu-kvm -machine ? Supported machines are: none empty machine pc Standard PC (i440FX + PIIX, 1996) (alias of pc-i440fx-1.4) pc-i440fx-1.4Standard PC (i440FX + PIIX, 1996) (default) pc-1.3 Standard PC pc-1.2 Standard PC pc-1.1 Standard PC pc-1.0 Standard PC pc-0.15 Standard PC pc-0.14 Standard PC pc-0.13 Standard PC pc-0.12 Standard PC pc-0.11 Standard PC, qemu 0.11 pc-0.10 Standard PC, qemu 0.10 isapcISA-only PC q35 Standard PC (Q35 + ICH9, 2009) (alias of pc-q35-1.4) pc-q35-1.4 Standard PC (Q35 + ICH9, 2009) qemu command line for a CentOS 6.4 64bit vm is: /usr/bin/qemu-system-x86_64 -machine accel=kvm -name c6s -S -machine pc-1.0,accel=kvm,usb=off -cpu Opteron_G2 both /usr/bin/qemu-kvm and /usr/bin/qemu-system-x86_64 are in qemu-system-x86 rpm package. Questions: - given a version of oVirt, pc version in qemu generated command line is the same for every defined VM or is there any logic depending on OS chosen and/or bit (32 vs 64)? - if answer to previous question is fixed pc version, is there any particular reason to use pc-0.14 in oVirt 3.2.3 and pc-1.0 in oVirt 3.3 and not the latest available (so pc-1.2 in 3.2.3 and pc-1.3 or pc-i440fx-1.4 in 3.3)? - where can I find documentation about difference between the different pc-x.y versions? - can I use a wrapper in oVirt 3.3 to start VM with a different pc-x.y (eg pc-0.14) and see if anything changes helping debug and solve the problem? Thanks, Gianluca ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] oVirt Roadmap feature requests - Summary
so, a lot of input post my question for 3.4 planning on "what do you want next"[1] I've just aggregated the replies here at this point for easier processing going forward: Infra - ability to give permissions to group of objects (namely, VMs) - support users/groups in oVirt DB as an authentication provider - support keystone as an authentication provider - kerberos login to webadmin/user portal - stateless host (pxe boot, no local disks) - detect updates and update host accordingly - embedded pxe/tftp boot server, setup to deploy the nodes - snmp & snmp trap monitoring Virt - template versions (ability to update template of a pool) - pci passthrough for devices like Telephone modem, PCI-express cards, Graphic cards - usbhost hook as supported feature (hardware license tokens) - ability to provide libvirt features directly[2] - dependencies between VMs (start db vm before webapp vm) - Allow to clone a VM without snapshot/template - Integrate v2v into engine - oVirt guest agent for Ubuntu/openSUSE/SLES/Debian - compatibility with OVF 2.0.1 - solaris as supported guest OS Network - private network between VMs - Network NAT for VMs (with buildin DHCP). - openvswitch support (in 3.3, via neutron?) - nic ordering Storage - import existing data domain - live merge (delete snapshot) - ability to resize a storage domain lun - multiple storage domains (local/gluster/FC) - ISO and export domains on FC/iSCSI - Upload ISOs within the GUI to ISO domain - Use an existing share for ISO domain - A backup and restore option - iSCSI EqualLogic SAN support or use standard iscsi tools/configuration - ATA over ethernet (AoE) as an optional storage transport - DR - DRBD, either with CLVM or perhaps GFS - live disk resize - disk ordering SLA - positive/negative affinity between group of VMs - power saving policy moving hosts to sleep - time based policy (SLA during the day, power saving at night) - collect and show power consumption of hosts - allow to give weights to prefer "faster" hosts to other hosts - application level HA (monitor the service inside the VM) Other - Zabbix monitoring [1] http://lists.ovirt.org/pipermail/users/2013-August/015807.html [2] http://lists.ovirt.org/pipermail/engine-devel/2013-August/005364.html ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] so, what do you want next in oVirt?
On 09/05/2013 11:31 AM, René Koch (ovido) wrote: - Resource pools At the moment only Quotas are available (which is great, btw), but in some cases it's necessary to implement resource pools. E.g. Limit CPU, Memory and Network for group of test vms, but give full resources to production vms. Maybe this could be done with cgroups? So e.g. I don't want to give a compile machine a full cpu core, but only 1 core with 500MHz or limit the bandwith to e.g. 10Mbit/s. doron - doesn't cpu shared provide this? ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] so, what do you want next in oVirt?
On 09/03/2013 11:31 AM, Hans-Joachim wrote: 4.) database script, which cleans/repaires unused entries (p.e. storage_server_connections, images, ...) while there isn't one for storage connections, there is a script to release/unlock entities like vm/template/disk (from image locked status mostly) ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] so, what do you want next in oVirt?
On 09/03/2013 11:31 AM, Hans-Joachim wrote: 3.) Priorisation of hosts to put the VMs on p.e. the fastest node just a btw, you should be able to do this with a weight function of your own in ovirt 3.3.1 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] so, what do you want next in oVirt?
On 08/29/2013 05:22 PM, Juan Pablo Lorier wrote: Hi, I think that one of the best things from Proxmox is the ability to connect to any of the hosts via web and been able to admin the hole infrastructure from there. This avoids the single point of failure that today engine represents in ovirt plataform. hosted engine should resolve this one. I agree with Jakub that been able to mix Intel and AMD hosts would be great so we can use the hole of the servers into a DC and engine may migrate VM to the same kind of processors if available but if not, as i replied just now, afaik, live migration between intel/amd isn't supported by kvm. migrate to any available host and alert about the performance degradation. you can't really migrate to a "lesser" host, only to at least same cpu level. I'm still a rookie to ovirt so at this time I don't know all the features to make further coments. I think you have a great product and the best of it is the speed it's improving. thanks, glad to hear. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] so, what do you want next in oVirt?
On 08/27/2013 09:48 PM, Dead Horse wrote: This: http://lists.ovirt.org/pipermail/users/2013-August/015713.html (freedom in mixing storage domain types no SPF Master Storage domain) going forward, the focus is to remove the concept of pool and master storage domain all together. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] so, what do you want next in oVirt?
On 08/27/2013 06:47 PM, Jakub Bittner wrote: and the absolutely fantastic feature would be to create clusters from Intel and AMD processors together! well, you can do that today if you want to via a config change. the only thing is live migration won't work (you should probably use -cpu host to get best performance, since live migration won't be used anyway) (well, in theory we could live migrate only between hosts of same cpu vendor, but not sure interesting enough use case to make cluster and scheduling more complex). though you can do that part on your own with the new pluggable scheduler, or use -cpu host to get max performance if you don't care about live migration From my point of view it is better to have slower cpu performance and possibility to use all of our servers in cluster. I would like to have live migration available from intel to amd. The problem is only in cpu instruction sets? If so, I can use only common sets. the problem is afaik kvm doesn't really support it for live migration (other than a prototype several years ago). Another feature which I forgot is network between VMs and mirroring traffic. Both configurable from WUI. port mirroring is supported today? ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Gluster network info
On Fri, Oct 4, 2013 at 12:15 PM, Sahina Bose wrote: > > I believe it should. When you add host to engine you would use node01. > Please let us know how it goes, > > thanks again > sahina I tried and it works. I was able to maintain my data too. I stopped the only VM created and put both hosts in maintenance. Then from f18ovn01 (with 10.4.4.58 on ovirtmgmt and 192.168.3.1 on new replication network): please note f18 in the name but is fedora 19 gluster volume stop gvdata gluster volume delete gvdata gluster peer detach 10.4.4.59 change /etc/hosts on both hosts and activate another interface with 192.168.3.1 and 192.168.3.3 to clear data about previous gluster volume and reuse it with same values: on both hosts setfattr -x trusted.glusterfs.volume-id /gluster/DATA_GLUSTER/brick1 setfattr -x trusted.gfid /gluster/DATA_GLUSTER/brick1 rm -rf rm -rf /gluster/DATA_GLUSTER/brick1/.glusterfs gluster peer probe f18ovn03.mydomain remake the manual steps to create gvdata volume and settings as before from oVirt webadmin activated both hosts and all came up transparently. able to start c6s VM (from run once only due to bug...) wget a netinst.iso for fedora 19 from inside VM and during transfer (VM is running on this f18ovn01 node): [root@f18ovn01 ]# bwm-ng v0.6 (probing every 1.000s), press 'h' for help input: libstatnet type: rate | iface Rx TxTotal == ovirtmgmt: 0.19 KB/s0.24 KB/s0.43 KB/s enp3s0: 214.34 KB/s28794.59 KB/s29008.93 KB/s -- total: 214.53 KB/s28794.82 KB/s29009.35 KB/s Also restarted ovirt-engine service on engine. Note that from engine point of view when I go in volumes --> gvdata --> bricks, still I see 10.4.4.58 and 10.4.4.59, probably because for the engine those are the ip addresses of f18ovn01 and f18ovn03 nodes Or I don't know if it wrote anywhere in the db the gluster data or only gets them dinamically Gianluca ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] internal networks in Ovirt
Lior gave a very detailed explanation, I added inline some comments on how you can use the Neutron integration to achieve some of the things. Regards, Mike - Original Message - > Hello, > > I'll start with your second question because it's simpler to answer: the > only way to configure multiple networks on one physical host interface > in oVirt is if all networks are VLAN-tagged, except for at most one > network which would then have to be marked as non-VM (AKA bridgeless). > In cases like yours ovirtmgmt is usually configured to be non-VM (you > can edit it from the networks main tab, for example), and then add other > bridged networks to be used within the VMs and VLAN-tag them. > > As for your first question, I'll do my best to answer it, and hopefully > others will correct me if I get anything wrong. > > Bridged networks are the default in oVirt. When you create a new logical > network within the oVirt webadmin console, mark it as a VM network and > attach it to a host (and presumably later to a VM) - a bridge is created > on the host with the logical network's name. > > By internal networks, do you mean networks that are common to a host and > to the VMs running on that host? If so, then this doesn't yet exist in > oVirt, although the feature has been brought up and will probably be > added sometime in the future (can't guarantee when though). I can think > of a workaround, but it would require you to pin VMs to specific hosts, > which is usually not something you'd wanna do when managing a virtual > DC. Also, you might just connect to one VM from another on the same host > (with a network that isn't defined as internal) and the traffic should > be internal. This can be achieved by using the Neutron integration, with the Linux Bridge/OVS plugin set to "local" network type. This way every external network you'll create will be host only. I believe that starting from Havana you need to update the "default" security group to allow all ingress traffic, in order for the VMs to be able to communicate with each other. > > If I'm not mistaken, NATing is not currently handled for you by oVirt; > you would have to set it up manually on your network's default gateway > or on your physical router. This can also be achieved with the Neutron integration (but don't use local networks) using routers that you configure directly on Neutron (this integration is not supported from oVirt yet, but it should work). For this to work, you need to make ovirtmgmt a non-VM network, as Lior explained. > > Other than that, if there's anything more specific you'd like to > achieve, we'd be happy to help. > > Yours, Lior. > > On 06/10/13 16:45, subscription sites wrote: > > Hi, > > > > > > I just installed ovirt 3.3 and got everything up and running with an > > ovirt node. > > However, I can't figure out how the networking works in ovirt. > > > > First of all, I'm looking for a feature like you have in virtualbox: > > configure bridged networks, internal networks and natted networks, how > > do you do each of these in ovirt? > > > > Also, I have only one physical nic and ovirtmgmt default network is > > already assigned to this nic. > > How can I attach other bridged networks to this same physical nic? > > > > > > Thanks for any help you can provide! > > > > > > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] internal networks in Ovirt
Hello, I'll start with your second question because it's simpler to answer: the only way to configure multiple networks on one physical host interface in oVirt is if all networks are VLAN-tagged, except for at most one network which would then have to be marked as non-VM (AKA bridgeless). In cases like yours ovirtmgmt is usually configured to be non-VM (you can edit it from the networks main tab, for example), and then add other bridged networks to be used within the VMs and VLAN-tag them. As for your first question, I'll do my best to answer it, and hopefully others will correct me if I get anything wrong. Bridged networks are the default in oVirt. When you create a new logical network within the oVirt webadmin console, mark it as a VM network and attach it to a host (and presumably later to a VM) - a bridge is created on the host with the logical network's name. By internal networks, do you mean networks that are common to a host and to the VMs running on that host? If so, then this doesn't yet exist in oVirt, although the feature has been brought up and will probably be added sometime in the future (can't guarantee when though). I can think of a workaround, but it would require you to pin VMs to specific hosts, which is usually not something you'd wanna do when managing a virtual DC. Also, you might just connect to one VM from another on the same host (with a network that isn't defined as internal) and the traffic should be internal. If I'm not mistaken, NATing is not currently handled for you by oVirt; you would have to set it up manually on your network's default gateway or on your physical router. Other than that, if there's anything more specific you'd like to achieve, we'd be happy to help. Yours, Lior. On 06/10/13 16:45, subscription sites wrote: > Hi, > > > I just installed ovirt 3.3 and got everything up and running with an > ovirt node. > However, I can't figure out how the networking works in ovirt. > > First of all, I'm looking for a feature like you have in virtualbox: > configure bridged networks, internal networks and natted networks, how > do you do each of these in ovirt? > > Also, I have only one physical nic and ovirtmgmt default network is > already assigned to this nic. > How can I attach other bridged networks to this same physical nic? > > > Thanks for any help you can provide! > > > > > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] internal networks in Ovirt
On Sun, Oct 6, 2013 at 4:45 PM, subscription sites wrote: > Hi, > > > I just installed ovirt 3.3 and got everything up and running with an ovirt > node. > However, I can't figure out how the networking works in ovirt. > > First of all, I'm looking for a feature like you have in virtualbox: > configure bridged networks, internal networks and natted networks, how do > you do each of these in ovirt? > > Also, I have only one physical nic and ovirtmgmt default network is already > assigned to this nic. > How can I attach other bridged networks to this same physical nic? > > > Thanks for any help you can provide! > Se here about similar questions and possible resolutions with dummy networks for example. I think discussions in 3.2 are applicable also now to 3.3 (not tested myself): http://lists.ovirt.org/pipermail/users/2013-May/014330.html HIH, Gianluca ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] internal networks in Ovirt
Hi, I just installed ovirt 3.3 and got everything up and running with an ovirt node. However, I can't figure out how the networking works in ovirt. First of all, I'm looking for a feature like you have in virtualbox: configure bridged networks, internal networks and natted networks, how do you do each of these in ovirt? Also, I have only one physical nic and ovirtmgmt default network is already assigned to this nic. How can I attach other bridged networks to this same physical nic? Thanks for any help you can provide! ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] CentOS or Fedora?
Hi, You can use the Gluster repo to install on CentOS. That's how we run 3.3 Regards, Vincent Connected by Motorola Rickard Kristiansson wrote: >___ >Users mailing list >Users@ovirt.org >http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] CentOS or Fedora?
Hi, We have been testing oVirt since 3.2.1, and have now upgraded the engine to 3.3 with the aim to use it in production for about 50 VMs currently running on 7 standalone CentOS 6.4 KVM hypervisors. We would prefer to use native GlusterFS integration, but I understand that CentOS 6.4 doesn't have the necessary library versions. Would it make sense to reinstall the hypervisors to oVirt nodes on Fedora19, or should we wait for CentOS 6.5? I'm not sure it feels very safe to use Fedora in production, even though it's the 'native' oVirt distribution..? I'm also not sure if Dell OpenManage is supported on Fedora, as this would be required for connecting the hypervisors/nodes into our common surveillance system. Maybe someone would say that we should use RHEV instead, but since we have managed with CentOS without vendor support on this particular service until now, I think we would be very comfortable with oVirt and the great support provided by the community. Anyone else having similar thoughts..? Regards Rickard ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] About the Backup-Restore API Integration
- Original Message - > From: "Itamar Heim" > To: emi...@gmail.com > Cc: users@ovirt.org > Sent: Wednesday, October 2, 2013 10:23:04 PM > Subject: Re: [Users] About the Backup-Restore API Integration > > On 10/02/2013 01:44 AM, emi...@gmail.com wrote: > > Hi, > > > > I'm testing ovirt to replace ESXi. Right now I want know if there is > > something like guettoVCB.sh > > (https://communities.vmware.com/docs/DOC-8760) that i can use with oVirt. > > > > I'm checking the following link: > > http://www.ovirt.org/Features/Backup-Restore_API_Integration but i don't > > understand if this feature it's aviable right now and if it allow me to > > do something like what guettoVCB.sh do. Hi Emiliano, The backup/restore API is a set of supported operations by ovirt. The support fir some of the operations is already merged and some should be merged upstream soon. > > > > Regards! > > Emiliano > > > > > > > > ___ > > Users mailing list > > Users@ovirt.org > > http://lists.ovirt.org/mailman/listinfo/users > > > > it missed 3.3.0 (which should be mentioned in the RN). > it may get into 3.3.1 or 3.3.2 still. > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] ovirt-node post-reboot no persistent networks config .. !!! urgent update req for POC coming weekend
- Original Message - > From: "Anil Dhingra" > To: "Fabian Deutsch" > Cc: users@ovirt.org > Sent: Wednesday, October 2, 2013 6:07:26 PM > Subject: Re: [Users] ovirt-node post-reboot no persistent networks config .. > !!! urgent update req for POC coming > weekend > > Hey Fabian > Thanks you so much .. abv mentioned iso draft for el6 works like a charm > config is persistent now ..only issue I faced is after configuring first > interface "eth0" when it starts VDSM & other service it hangs at & > hard reboot > was required but after that no issue tried multiple reboots different n/w > configs ..looks perfect. > just wanted to ask some n/w related q to clear my doubts .. may be its not a > right group to ask such question > Please find attached image for below > 1- ovirt-node creates Bridged network only when "vm network" option is > selected ... ? correct me if I am wrong The engine directs vdsm how to create the network on the host. If the logical network definition is 'vm network', the network will be created as a bridge which is the current vm network implementation. > 2- is it recommended or best practice to select ovirtmgmt for VM n/w ? so > that it make a Bridged n/w It depends on you h/w capabilities. If you have a single nic per host, it would be better defining it as a non-vm network, so you will be able to attach additional tagged networks to that nic, so you can support multiple private networks (you'll have to specify a specific vlan-id for each additional network). If you have multiple nics, it would be better to define the ovirtmgmt as a non-vm network, and not use it as a migration network. (traffic considerations). > 3- for Migration/Display network whats the best practice do we need to create > manual bridge setup ? There is no need for that. You must have a network with IP configured and obtained by the engine (on the host nics sub-tab you should see the engine reports the ip of the network you wish to use as a display network and/or a migration network). > Thanks again for prompt response really appreciate yours help .. > Anil > > > On Wed, Oct 2, 2013 at 5:16 PM, Fabian Deutsch < fabi...@redhat.com > wrote: > > > Am Dienstag, den 01.10.2013, 15:05 + schrieb Sven Kieske: > > Hi, > > > > we encountered the same problem as Anil. > > > > We wanted to give this nightly iso a try: > > http://jenkins.ovirt.org/job/node-devel/825/distro=centos64/artifact/ovirt-node-iso-3.1.0-0.999.825.el6.iso > > > > but it seems it doesn't contain the required vdsm-plugin? > > True. The plugin is missing. > > I've prepared two isos (but untested) which address this bug: > http://fedorapeople.org/~fabiand/node/ovirt-node-iso-3.0.1-1.0.201310020841draft.vdsm.el6.iso > http://fedorapeople.org/~fabiand/node/ovirt-node-iso-3.1.0-0.999.201310020841draft.vdsm.fc19.iso > > They are basically the base iso (found in jenkins) plus an edit-node > run: > /edit-node --repo edit-node-el6.repo --install ovirt-node-plugin-vdsm > ovirt-node-iso-3.0.1-1.0.201310020841draft.el6.iso > > Please let me know if they fix the problem. > > Greetings > fabian > > > So any help on this topic would be appreciated. > > > > Greetings > > > > Sven > > > > On 30/09/13 20:52, Fabian Deutsch wrote: > > > > > > > > Hey Anil, > > > > > > you were doing the right thing to persist the network cfg files. It > > > might have been node that was to greedy when reconfiguring DNS :) > > > > > > You might take a look at this fix: > > > http://gerrit.ovirt.org/19705 > > > It is untested but at least I could reproduce the behavior you were > > > seeing and prepared the patch based on that findings. > > > An ISO containing that fix will sooner or later land here: > > > http://jenkins.ovirt.org/job/node-devel/ > > > > > > (The queue is currently quite long, which can take a day until the patch > > > above is turned into an ISO). > > > > > > Long story short, please check if this patch fixes your problem, I'll > > > also try to take a look at it when an iso is ready. > > > > > > And file a bug if you want to track the state of this issue. > > > > > > Greetings > > > fabian > > ___ > > Users mailing list > > Users@ovirt.org > > http://lists.ovirt.org/mailman/listinfo/users > > > > > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] What should be the default for adding network from specific Cluster
Lior Vernia wrote: The upside is that we'd keep consistency with "the context" (i.e. operation as part of specific cluster). The downside would be that users might not always aware of "the context" and thus might be confused by the different behavior of the seemingly same dialog. On 06/10/13 08:46, Genadi Chereshnya wrote: Hi all, We would like to consult community about adding the Network from Cluster tab. In 3.3 we can add Network from the DataCenter tab and then that network will be attached to all Clusters of that DataCenter. When adding network from specific Cluster the default behavior today is to attach that network to all the Clusters under the same DataCenter as well. We think that the right behavior should be add that network by default only to the Cluster from which we add that Network from. Any feedback will be appreciated. Thanks, Genadi I think this context sensitivity is already used when creating a new VM. If the datacenter is selected then you can choose which cluster the VM should be in but if the cluster is selected you don't have that choice. To that is logical but a big RED TIP in the manual might make things much clearer :-) So find out what is used more often and confirm to that or go for the context. Joop ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] What should be the default for adding network from specific Cluster
The upside is that we'd keep consistency with "the context" (i.e. operation as part of specific cluster). The downside would be that users might not always aware of "the context" and thus might be confused by the different behavior of the seemingly same dialog. On 06/10/13 08:46, Genadi Chereshnya wrote: > Hi all, > > We would like to consult community about adding the Network from Cluster tab. > In 3.3 we can add Network from the DataCenter tab and then that network will > be attached to all Clusters of that DataCenter. > When adding network from specific Cluster the default behavior today is to > attach that network to all the Clusters under the same DataCenter as well. > We think that the right behavior should be add that network by default only > to the Cluster from which we add that Network from. > Any feedback will be appreciated. > Thanks, >Genadi >Rhevm-Network QE > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
