Re: [Users] oVirt 3.3 and Neutron
- Original Message - Hi ricardo, snip On 09/28/2013 02:47 PM, riccardo.brune...@dnshosting.it wrote: Dear all. Please, does anybody have some suggestions? I'm getting stuck with this issue. Hi Ricardo, Since this feature has been targeted as tech preview, such issues are unfortunately happening as the current integration didn't count for L3 services yet. Thank you very much Riccardo On 2013-09-27 14:09, Riccardo Brunetti wrote: Dear oVirt users. I'm trying to setup oVirt 3.3 using an OpenStack Neutron existing service as network provider. It works pretty well: I can use the networks defined in Neutron, import them and when I launch VM instances from oVirt they get an internal-IP address from Neutron. A can also associate a floating IP to the Neutron port and get inbound connectivity for the virtual machine. The problem is that if I shutdown the VM (both from inside the VM itself and from the oVirt WEB GUI) the association port/internal-IP/floating-IP is lost and when the VM is booted again It will get a different internal-IP on a different port and I have to manually re-associate the floating-IP. It seems like we are currently creating a port on VM start and deleting the port on VM stop, which causes the behavior you described. Yes this is the initial design of the feature. Since it didn't account for L3 services, there is this side effect. Is there a way to keep the IP addresses when the VM is simply shutted down and not deleted? This is the behavior when using OpenStack: if I poweroff the VM, the IPs are kept for the future. There should be a way, would you mind reporting a bug on that? In addition, do you mind trying to use static IPs inside the VMs and not DHCP that is provided by neutron, and see if this would help? Moreover: can you confirm that in oVirt 3.3 there is still no support for the Neutron security rules? Unfortunately we did not get to handle that yet, but we are looking at that as part of extending the integration. Thank you very much Best Regards Riccardo ___ 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] 500 Internal Server Error when provisioning via Foreman (using nightly build)
- Original Message - From: Andrew Timmes andrew.tim...@gmail.com To: users@ovirt.org Sent: Wednesday, September 25, 2013 8:49:35 PM Subject: [Users] 500 Internal Server Error when provisioning via Foreman (using nightly build) All, I'm using oVirt 3.4.0-0.2.master.20130925104201.git8ab6304.el6 on CentOS 6.4 as a compute resource for Foreman (1.2.2, also running on CentOS 6.4). When I attempt to provision a machine, I get a 500 server error. Logs are posted below: https://gist.github.com/andrew-timmes/d41f465d2c25af5905c8 It looks similar to the issue that Andrew Lau reported in August ( http://lists.ovirt.org/pipermail/users/2013-August/015693.html ) but I'm still seeing the issue in the nightly build. Any ideas? Thanks, Andrew Timmes ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users any chance your DB is not up to date? looks like 'comment' column is missing ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Export Domain Upgrade
- Original Message - From: Nicholas Kesick cybertimber2...@hotmail.com To: oVirt Mailing List users@ovirt.org Sent: Wednesday, September 25, 2013 8:43:47 PM Subject: [Users] Export Domain Upgrade This is the first time I've run through an 'upgrade', so I'm very new to export domains, and I'm having some trouble getting one connected to 3.3. I had hoped to add this to the wiki, but it hasn't been as straightforward as I thought. On my oVirt 3.2 install, I created a NFS export (/var/lib/exports/DAONE) and exported my VMs to it. I created a tarball of everything in DAONE, and then formatted the system and installed Fedora 19, and then oVirt 3.3. Created the NFS resource (/var/lib/exports/DAONE), extracted the tarball, and followed these directions to clear the storage domain. However when I try to add it, the webadmin reports the following error: Error while executing action New NFS Storage Domain: Error in creating a Storage Domain. The selected storage path is not empty (probably contains another Storage Domain). Either remove the existing Storage Domain from this path, or change the Storage path). Any suggestions? I wonder if anything changed for 3.3 that need to be in the instructions? looks like you should have done 'import existing export domain' to this path instead of trying create a new one. I also tried making another export domain (/var/lib/exports/export) and dumping everything into the UUID under that, but no VMs showed up to import. #showmount -e f19-ovirt.mkesick.net Export list for f19-ovirt.mkesick.net: /var/lib/exports/storage 0.0.0.0/0.0.0.0 /var/lib/exports/iso 0.0.0.0/0.0.0.0 /var/lib/exports/export 0.0.0.0/0.0.0.0 /var/lib/exports/DAONE 0.0.0.0/0.0.0.0 [root@f19-ovirt dom_md]# cat metadata CLASS=Backup DESCRIPTION=DaOne IOOPTIMEOUTSEC=1 LEASERETRIES=3 LEASETIMESEC=5 LOCKPOLICY= LOCKRENEWALINTERVALSEC=5 MASTER_VERSION=0 POOL_UUID= REMOTE_PATH=localhost:/var/lib/exports/DAONE ROLE=Regular SDUUID=8e4f6fbd-b635-4f47-b113-ba146ee1c0cf TYPE=NFS VERSION=0 ___ 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] 500 Internal Server Error when provisioning via Foreman (using nightly build)
On 09/29/2013 12:12 PM, Omer Frenkel wrote: *From: *Andrew Timmes andrew.tim...@gmail.com *To: *users@ovirt.org *Sent: *Wednesday, September 25, 2013 8:49:35 PM *Subject: *[Users] 500 Internal Server Error when provisioning via Foreman (using nightly build) All, I'm using oVirt 3.4.0-0.2.master.20130925104201.git8ab6304.el6 on CentOS 6.4 as a compute resource for Foreman (1.2.2, also running on CentOS 6.4). When I attempt to provision a machine, I get a 500 server error. Logs are posted below: https://gist.github.com/andrew-timmes/d41f465d2c25af5905c8 It looks similar to the issue that Andrew Lau reported in August (http://lists.ovirt.org/pipermail/users/2013-August/015693.html) but I'm still seeing the issue in the nightly build. Any ideas? Thanks, Andrew Timmes ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users any chance your DB is not up to date? looks like 'comment' column is missing ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users isn't that because the db field name is free_text_comment? http://gerrit.ovirt.org/#/c/19217/ ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Migration issues with ovirt 3.3
On Fri, Sep 27, 2013 at 03:36:22PM -0300, emi...@gmail.com wrote: So Dan, could I do some other test for you?, The live migration it's only working with a Debian install, I've just finished to install a windows server 2K8 and it doesn't work neither, gives the following error VM W2K8 is down. Exit message: 'iface'. Frankly, I am out of ideas of what could be causing this very important bug :-( It is unrelated to hotplugging, and probably not to migration - something bad happens when the VM parameters are persisted to disk, or loaded from it. I do not see how the type of the guest could matter. Could you tell if there is any other difference betrween your W2K8 VM and your Debian one? Could you post here the first vmCreate command of the two VMs, and their libvirt domxml? Regards, Dan. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Export Domain Upgrade
On 09/29/2013 12:15 PM, Omer Frenkel wrote: *From: *Nicholas Kesick cybertimber2...@hotmail.com *To: *oVirt Mailing List users@ovirt.org *Sent: *Wednesday, September 25, 2013 8:43:47 PM *Subject: *[Users] Export Domain Upgrade This is the first time I've run through an 'upgrade', so I'm very new to export domains, and I'm having some trouble getting one connected to 3.3. I had hoped to add this to the wiki, but it hasn't been as straightforward as I thought. On my oVirt 3.2 install, I created a NFS export (/var/lib/exports/DAONE) and exported my VMs to it. I created a tarball of everything in DAONE, and then formatted the system and installed Fedora 19, and then oVirt 3.3. Created the NFS resource (/var/lib/exports/DAONE), extracted the tarball, and followed these directions http://www.ovirt.org/How_to_clear_the_storage_domain_pool_config_of_an_exported_nfs_domain to clear the storage domain. However when I try to add it, the webadmin reports the following error: Error while executing action New NFS Storage Domain: Error in creating a Storage Domain. The selected storage path is not empty (probably contains another Storage Domain). Either remove the existing Storage Domain from this path, or change the Storage path). Any suggestions? I wonder if anything changed for 3.3 that need to be in the instructions? looks like you should have done 'import existing export domain' to this path instead of trying create a new one. indeed. also note you could have just upgraded rather than export/import all the vms: Bug 1009335 - TestOnly - upgrade path from Fedora 18 with oVirt 3.2 to Fedora 19 with oVirt 3.3 I also tried making another export domain (/var/lib/exports/export) and dumping everything into the UUID under that, but no VMs showed up to import. #showmount -e f19-ovirt.mkesick.net Export list for f19-ovirt.mkesick.net: /var/lib/exports/storage 0.0.0.0/0.0.0.0 /var/lib/exports/iso 0.0.0.0/0.0.0.0 /var/lib/exports/export 0.0.0.0/0.0.0.0 /var/lib/exports/DAONE 0.0.0.0/0.0.0.0 [root@f19-ovirt dom_md]# cat metadata CLASS=Backup DESCRIPTION=DaOne IOOPTIMEOUTSEC=1 LEASERETRIES=3 LEASETIMESEC=5 LOCKPOLICY= LOCKRENEWALINTERVALSEC=5 MASTER_VERSION=0 POOL_UUID= REMOTE_PATH=localhost:/var/lib/exports/DAONE ROLE=Regular SDUUID=8e4f6fbd-b635-4f47-b113-ba146ee1c0cf TYPE=NFS VERSION=0 ___ 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] could not add iscsi disk in ovirt.
On 09/27/2013 05:59 PM, Dafna Ron wrote: I don't think its supported for NFS... I can check for you on Monday for sure. direct lun is for nfs/other as well. not limited to fc/iscsi. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Export Domain Upgrade
Date: Mon, 30 Sep 2013 00:33:08 +0300 From: ih...@redhat.com To: ofren...@redhat.com CC: cybertimber2...@hotmail.com; users@ovirt.org Subject: Re: [Users] Export Domain Upgrade On 09/29/2013 12:15 PM, Omer Frenkel wrote: *From: *Nicholas Kesick cybertimber2...@hotmail.com *To: *oVirt Mailing List users@ovirt.org *Sent: *Wednesday, September 25, 2013 8:43:47 PM *Subject: *[Users] Export Domain Upgrade This is the first time I've run through an 'upgrade', so I'm very new to export domains, and I'm having some trouble getting one connected to 3.3. I had hoped to add this to the wiki, but it hasn't been as straightforward as I thought. On my oVirt 3.2 install, I created a NFS export (/var/lib/exports/DAONE) and exported my VMs to it. I created a tarball of everything in DAONE, and then formatted the system and installed Fedora 19, and then oVirt 3.3. Created the NFS resource (/var/lib/exports/DAONE), extracted the tarball, and followed these directions http://www.ovirt.org/How_to_clear_the_storage_domain_pool_config_of_an_exported_nfs_domain to clear the storage domain. However when I try to add it, the webadmin reports the following error: Error while executing action New NFS Storage Domain: Error in creating a Storage Domain. The selected storage path is not empty (probably contains another Storage Domain). Either remove the existing Storage Domain from this path, or change the Storage path). Any suggestions? I wonder if anything changed for 3.3 that need to be in the instructions? looks like you should have done 'import existing export domain' to this path instead of trying create a new one. indeed. also note you could have just upgraded rather than export/import all the vms: Bug 1009335 - TestOnly - upgrade path from Fedora 18 with oVirt 3.2 to Fedora 19 with oVirt 3.3 I should have responded to this sooner, I got it working thanks to some help in IRC. I should have been using import domain, but I also found that the path has to match what was in the metdata file. So while I was trying to use hostname:/var/lib/exports/export I had used localhost:/var/lib/exports/export in ovirt 3.2, so that caused some delay. I also tried making another export domain (/var/lib/exports/export) and dumping everything into the UUID under that, but no VMs showed up to import. #showmount -e f19-ovirt.mkesick.net Export list for f19-ovirt.mkesick.net: /var/lib/exports/storage 0.0.0.0/0.0.0.0 /var/lib/exports/iso 0.0.0.0/0.0.0.0 /var/lib/exports/export 0.0.0.0/0.0.0.0 /var/lib/exports/DAONE 0.0.0.0/0.0.0.0 [root@f19-ovirt dom_md]# cat metadata CLASS=Backup DESCRIPTION=DaOne IOOPTIMEOUTSEC=1 LEASERETRIES=3 LEASETIMESEC=5 LOCKPOLICY= LOCKRENEWALINTERVALSEC=5 MASTER_VERSION=0 POOL_UUID= REMOTE_PATH=localhost:/var/lib/exports/DAONE ROLE=Regular SDUUID=8e4f6fbd-b635-4f47-b113-ba146ee1c0cf TYPE=NFS VERSION=0 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
