Ask Your Question
1

Openstack conflicts with kvm virtual machine manager

asked 2014-02-22 01:31:17 -0600

Avanti Ajay gravatar image

updated 2014-02-26 08:13:59 -0600

rahmu gravatar image

Hi..

I have created an instance in Openstack with name : virtualMachine1.

When I open the kvm Virtual Machine Manager I see this new instance launched with the name:instance-00000001. Both virtualMachine1 and instance-00000001 have the same uuid.

When I try making any changes from kvm VMM ie stop this vm or pause this vm, the kvm VMM doesnt allow me to perform any changes.

But when I change the name of the this vm from instance-00000001 to virtualMachine1 through the kvm virtual machine manager, I can perform operations on this vm through kvm VMM but these changes are not reflected in openstack.

Is this some configuration issue or there is lack of synchronization between frontend and backend?

Please help..

Thank you

edit retag flag offensive close merge delete

Comments

I don't have an answer for your question, but I'm curious, why would you need to manipulate your instances with VMM? I would advise against bypassing the frontend as much as you can.

rahmu gravatar imagerahmu ( 2014-02-22 02:50:48 -0600 )edit
1

Indeed, in particularly this bit "I can perform operations on this vm through kvm VMM but these changes are not reflected in openstack." is not really surprising, since OpenStack assumes it's solely in control of the virtual machine's lifecycle.

sgordon gravatar imagesgordon ( 2014-02-22 13:47:09 -0600 )edit

What if Openstack is down for some reason and customer needs his disk resized then we will need to make changes from VMM and once openstack is up this needs to be communicated to Openstack?

Avanti Ajay gravatar imageAvanti Ajay ( 2014-02-24 01:34:52 -0600 )edit
1

OpenStack is simply not designed to support that use case. Planning on manually supporting your users if/while your control plane is down is simply not scalable.

dtroyer gravatar imagedtroyer ( 2014-02-24 18:54:32 -0600 )edit
1

Avanti, OpenStack is made up of many components, most (all?) of which are horizontally scalable. If anything is completely down you likely have an architectural problem in your deployment and resizing your customer's disk is the least of your issues (let alone doing it with an unrelated tool).

sgordon gravatar imagesgordon ( 2014-02-25 08:31:00 -0600 )edit

1 answer

Sort by ยป oldest newest most voted
2

answered 2014-02-26 08:18:09 -0600

rahmu gravatar image

This is rephrasing the answers you already got in the comments to your question.

OpenStack doesn't support you manipulating your VMs with the hypervisor's specific managers directly. "OpenStack assumes it's solely in control of the virtual machine's lifecycle". If OpenStack itself is unavailable for some reason, "you likely have an architectural problem in your deployment and resizing your customer's disk is the least of your issues" since designed to be horizontally scalable.

In other words, it is normal that the changes you make through KVM VMM aren't reflected in OpenStack. It's a desired behavior.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

Stats

Asked: 2014-02-22 01:31:17 -0600

Seen: 347 times

Last updated: Feb 26 '14