Openstack conflicts with kvm virtual machine manager
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
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.
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.
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?
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.
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).