[Openstack] Nova can not detached a volume
Hi all, I have been faced a problem that the volume can not be detached when an instance is booted from a volume with an invalid name. Here is a sequence that the problem happens: --- Version: Essex, Folsom-2 (use nova.volume.driver.ISCSIDriver) 1. Create volume (volume name: vol001) 2. Lunch instance (Boot From Volume) - name: test001 - Volume or Volume Snapshot: vol001 - Device Name: aaa <- select illegal device 3. Check: instance status - Status: error - Task: Spawning - Power State: No State 4. 4-1. detach volume - Horizon: Success message is displayed. "Success: Detached Volume: Attachment aaa on [UUID]" - nova-compute.log: Error (http://paste.openstack.org/show/19305/) 4-2. terminate instance - Horizon: Success message is dispalyed. "Success: Terminated Instance: test" - nova-compute.log: Error(http://paste.openstack.org/show/19306/) --- Is this a bug? If you terminated instance without detaching volume. - instace terminate: Success - detach volume: Success Cause: --- o Detach volume - iSCSI delete: Success - DB update: Fail - libvirt can not find domain (# virsh list --all -> no entry) o Terminate instance - iSCSI delete: Fail - it has been already iscsi logout. - DB update: Fail --- As a transitory measure: --- mysql> use nova mysql> update volumes set mountpoint=NULL,status="available",attach_status="detached",instance_id=NULL where id=XXX; mysql> update block_device_mapping set deleted_at = now(),deleted = 1 where id = XXX; --- Best Regards, Hiroki Ishikawa -- Hiroki Ishikawa ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Per host floating ip
I'm currently building up, i did a test setup with 3 machines and it worked. Now i'm doing it again with secure passwords, firewall etc. Btw, i just bought 3 EX 4 servers with a private lan between them using the switch + additional nic option they provide. I was thinking that another solution would be to use failover ip and when i assign an ip to an instance a custom hook calls the hetzner api to change the routing to point the ip to the server which is running the vm. Next step would be to use a shared fs like gluster for vm HA. I was thinking to make a blog post as soon as i get everything working to share how i did the setup. Regards Il giorno 06/lug/2012, alle ore 23:45, Michael Grosser ha scritto: > Sounds like a solution, but a manual one. A more automatic way would > be great I reckon. > > On Fri, Jul 6, 2012 at 7:00 PM, Marnus van Niekerk wrote: >> I have limited knowledge of OpenStack, but I host many servers with Hetzner >> and know their infrastructure well. >> >> Since nova allows you to assign specific floating IPs to specific instances >> you could do the following. >> Create a floating range include all of the IPs Hetzner has given you. >> Then just associate the IP from the underlying host with a VM running on it >> that host using euca-associate-address. >> >> On 06/07/2012 18:17, Michael Grosser wrote: >> >> Hey, >> >> I would love to hear more on your setup at hetzner, I was looking to >> setup openstack there myself, but I didn't see a solution for the per >> server ip issue. >> How many machines do you use? >> How did you set it up? >> Do you use only nova or swift too? >> >> I would love to get more insight. >> >> Thanks for taking the time >> Cheers Michael >> >> On Fri, Jul 6, 2012 at 12:24 PM, Alessandro Tagliapietra >> wrote: >> >> Hello guys, i've some servers at hetzner, >> i've actually installed essex on those and they're working fine, the step >> i'm missing is that hetzner gives you additional ip fixed to one host or >> failover ip that i can move to one server to another with the api. >> What i want is to assign floating ip to vm, depending on which host the vm >> is running or use a create hook to move the failover ip to the host which is >> running the vm. Is it possible in some way? >> >> Best Regards >> ___ >> Mailing list: https://launchpad.net/~openstack >> Post to : openstack@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~openstack >> More help : https://help.launchpad.net/ListHelp >> >> ___ >> Mailing list: https://launchpad.net/~openstack >> Post to : openstack@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~openstack >> More help : https://help.launchpad.net/ListHelp >> >> >> ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Per host floating ip
I have tried gluster for live migration but could net get it working. Please post back here if get that working. Instances ran fine with /var/lib/nova/instances on gluster, but live migration would change vm state to migrating and then back to running but still have it running where it was without any errors in the logs. M On Saturday, 7 July 2012, Alessandro Tagliapietra < tagliapietra.alessan...@gmail.com> wrote: > I'm currently building up, i did a test setup with 3 machines and it worked. > Now i'm doing it again with secure passwords, firewall etc. > Btw, i just bought 3 EX 4 servers with a private lan between them using the switch + additional nic option they provide. > > I was thinking that another solution would be to use failover ip and when i assign an ip to an instance a custom hook calls the hetzner api to change the routing to point the ip to the server which is running the vm. > > Next step would be to use a shared fs like gluster for vm HA. > > I was thinking to make a blog post as soon as i get everything working to share how i did the setup. > > Regards > > Il giorno 06/lug/2012, alle ore 23:45, Michael Grosser ha scritto: > >> Sounds like a solution, but a manual one. A more automatic way would >> be great I reckon. >> >> On Fri, Jul 6, 2012 at 7:00 PM, Marnus van Niekerk wrote: >>> I have limited knowledge of OpenStack, but I host many servers with Hetzner >>> and know their infrastructure well. >>> >>> Since nova allows you to assign specific floating IPs to specific instances >>> you could do the following. >>> Create a floating range include all of the IPs Hetzner has given you. >>> Then just associate the IP from the underlying host with a VM running on it >>> that host using euca-associate-address. >>> >>> On 06/07/2012 18:17, Michael Grosser wrote: >>> >>> Hey, >>> >>> I would love to hear more on your setup at hetzner, I was looking to >>> setup openstack there myself, but I didn't see a solution for the per >>> server ip issue. >>> How many machines do you use? >>> How did you set it up? >>> Do you use only nova or swift too? >>> >>> I would love to get more insight. >>> >>> Thanks for taking the time >>> Cheers Michael >>> >>> On Fri, Jul 6, 2012 at 12:24 PM, Alessandro Tagliapietra >>> wrote: >>> >>> Hello guys, i've some servers at hetzner, >>> i've actually installed essex on those and they're working fine, the step >>> i'm missing is that hetzner gives you additional ip fixed to one host or >>> failover ip that i can move to one server to another with the api. >>> What i want is to assign floating ip to vm, depending on which host the vm >>> is running or use a create hook to move the failover ip to the host which is >>> running the vm. Is it possible in some way? >>> >>> Best Regards >>> ___ >>> Mailing list: https://launchpad.net/~openstack >>> Post to : openstack@lists.launchpad.net >>> Unsubscribe : https://launchpad.net/~openstack >>> More help : https://help.launchpad.net/ListHelp >>> >>> ___ >>> Mailing list: https://launchpad.net/~openstack >>> Post to : openstack@lists.launchpad.net >>> Unsubscribe : https://launchpad.net/~openstack >>> More help : https://help.launchpad.net/ListHelp >>> >>> >>> > > ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Per host floating ip
I'm on other tasks actually but as soon as i get everything working i'll send a msg to the list with blog post with my tutorial for sure. Regards Il giorno 07/lug/2012, alle ore 12:19, Marnus van Niekerk ha scritto: > I have tried gluster for live migration but could net get it working. Please > post back here if get that working. > Instances ran fine with /var/lib/nova/instances on gluster, but live > migration would change vm state to migrating and then back to running but > still have it running where it was without any errors in the logs. > > M > > On Saturday, 7 July 2012, Alessandro Tagliapietra > wrote: > > I'm currently building up, i did a test setup with 3 machines and it worked. > > Now i'm doing it again with secure passwords, firewall etc. > > Btw, i just bought 3 EX 4 servers with a private lan between them using the > > switch + additional nic option they provide. > > > > I was thinking that another solution would be to use failover ip and when i > > assign an ip to an instance a custom hook calls the hetzner api to change > > the routing to point the ip to the server which is running the vm. > > > > Next step would be to use a shared fs like gluster for vm HA. > > > > I was thinking to make a blog post as soon as i get everything working to > > share how i did the setup. > > > > Regards > > > > Il giorno 06/lug/2012, alle ore 23:45, Michael Grosser ha scritto: > > > >> Sounds like a solution, but a manual one. A more automatic way would > >> be great I reckon. > >> > >> On Fri, Jul 6, 2012 at 7:00 PM, Marnus van Niekerk wrote: > >>> I have limited knowledge of OpenStack, but I host many servers with > >>> Hetzner > >>> and know their infrastructure well. > >>> > >>> Since nova allows you to assign specific floating IPs to specific > >>> instances > >>> you could do the following. > >>> Create a floating range include all of the IPs Hetzner has given you. > >>> Then just associate the IP from the underlying host with a VM running on > >>> it > >>> that host using euca-associate-address. > >>> > >>> On 06/07/2012 18:17, Michael Grosser wrote: > >>> > >>> Hey, > >>> > >>> I would love to hear more on your setup at hetzner, I was looking to > >>> setup openstack there myself, but I didn't see a solution for the per > >>> server ip issue. > >>> How many machines do you use? > >>> How did you set it up? > >>> Do you use only nova or swift too? > >>> > >>> I would love to get more insight. > >>> > >>> Thanks for taking the time > >>> Cheers Michael > >>> > >>> On Fri, Jul 6, 2012 at 12:24 PM, Alessandro Tagliapietra > >>> wrote: > >>> > >>> Hello guys, i've some servers at hetzner, > >>> i've actually installed essex on those and they're working fine, the step > >>> i'm missing is that hetzner gives you additional ip fixed to one host or > >>> failover ip that i can move to one server to another with the api. > >>> What i want is to assign floating ip to vm, depending on which host the vm > >>> is running or use a create hook to move the failover ip to the host which > >>> is > >>> running the vm. Is it possible in some way? > >>> > >>> Best Regards > >>> ___ > >>> Mailing list: https://launchpad.net/~openstack > >>> Post to : openstack@lists.launchpad.net > >>> Unsubscribe : https://launchpad.net/~openstack > >>> More help : https://help.launchpad.net/ListHelp > >>> > >>> ___ > >>> Mailing list: https://launchpad.net/~openstack > >>> Post to : openstack@lists.launchpad.net > >>> Unsubscribe : https://launchpad.net/~openstack > >>> More help : https://help.launchpad.net/ListHelp > >>> > >>> > >>> > > > > ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Glance Image Upload error.
On 07/06/2012 01:26 AM, Trinath Somanchi wrote: > Hi - > > Nope, I'm not working on Diablo release. > > But I have image in 3 parts. I want to store these three parts of the > image into glance as a single image. To achieve the same while doing a > google search found this procedure. > > Hence, implemented the same. > > Can any one guide me on how to store multiple parts of a single image > into glance. You cannot store multiple image parts in Glance -- you must store the image as a single file. The backend that Glance uses for storage *may* split the incoming file into chunks, but that's not something you will see as a user of the Glance AAPI. That said, I *think* you mean that you want to store a kernel image, a ramdisk image and a disk image in Glance, and that is certainly possible -- but it's wrong to call those "image parts" :) Best, -jay ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Performance metrics of RabbitMQServer
On 07/06/2012 06:52 AM, Naveen Kuna wrote: > > Hi All, > > Can anyone know performance metrics of RabbitMQServer ? Google is your friend :) http://stackoverflow.com/questions/7921324/performance-comparison-between-zeromq-rabbitmq-and-apache-qpid Keep in mind you have different feature sets between different message queue servers, so it's unlikely you will ever really get an apples to apples comparison. It's better for you to decide what features are critical to you *before* you just blindly go for one server that has "better performance". The features you want to look over include things like persistence of messages (and options for persistence), HA setups, monitoring and management, etc. > Is there any better alternative than RabbitMQServer ? See above. Best, -jay ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] Guest IP configuration using libvirt
Hi, Does Nova enable to configure guest IP address using libvirt? In particular such configuration requires to utilize libvirt 'network' capabilities, but I didn't see any Nova configuration that support it. Thanks, RamiC ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] [keystone] Keystone V3 API - draft 3 - implementation draft available
Thanks again to everyone that read, commented, and suggested improvements into the Keystone V3 API. This process has been immensely valuable, although far more time consuming than I expected. I've created a 3rd draft, now available at https://docs.google.com/document/d/1VP-bTBbwsn6q-rDzuS9CEKb2ubE1VjbWRFd4BkkjoOY/edit The third draft is *mostly* a refinement of the 2nd, with the notable difference being that (as threatened at the design summit), I've renamed "tenant" to "project" to revert back to the original naming structure. (sorry Jay, changing it to "account" - while semantically pretty good - lost out to existing terms in our documentation and history) We don't have all the questions answered, and the largest the consistently came up in this last draft was how to deal with requesting related items - potentially through query-able arguments to GET verbs on the resources. While I may regret not nailing that down right now, I'm going to run with Brian's learning from the Glance API implementation and leave this draft "open", but begin implementation so we can see what in there (while nice) is made up of unimplementium. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [Nova] Networking changes and quantum
> L3 + Floating IPs are being added to Quantum in F-3 (got bumped from F-2). > So, I should wait until L3 and try again, but in quantum? > I haven't looked at your patch in detail, but it seems like you're looking > to notice when a floating-ip is allocated or deallocated, and use that to > trigger a change to the configuration of an external BGP daemon. > Yes, on a per network-node basis. Also, rather than binding the IP to the public network device, it should bind the IP to lo (to avoid arp issues). Binding the IPs to lo is likely doable without any changes, though. > Assuming that's the case, I'd much rather we take the approach of creating a > notification API that would let you build this functionality as an external > component process that feeds off of notifications about floating IPs being > allocated and deallocated. We're looking at something similar for DHCP as > well. This let's people implement custom functionality without having to > modify the core code and config files. We have a blueprint to add such a > notification framework to Quantum (likely based on work in Nova), but at > this point, but its not clear when this will land (likely depends on whether > it is used for DHCP improvements in F-3 or not). If you're interested in > helping out with it, let me know. > Well, I can write this as a plugin, based on the plugin code in openstack-common. I thought this was a useful enough change to go in core, though. If everything in quantum is going to be a plugin, I'm more than happy to have this as a plugin. When do you expect this API to be available? I plan on backporting my work to nova for diablo and essex, but I'd like to make sure I have this upstream in the right place, and in the preferred way. - Ryan ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
