How to start Seed VM, Overcloud and Undercloud VM in HP Helion Commuity Virtual via manual

asked 2014-12-02 03:24:40 -0500

Nesta Guo gravatar image

Hi all,

 I had installed sucessfully HP helion community Virtual installation in HP Z600 workstation last week. and seed VM, overcloud and undercloud VMs are ok, I can log in hp helion portal via web page of broswer. I can set up VM, network and so on in HP Helion system. Everything is work I think. But I have to restart my HP Z600 workstation today because of planned update. After I restart workstation, I find all VMs(seed, overcloud, undercloud) are still power off. I use 'virsh autostart' command to start all VMs, when I restart Z600 workstation again, all VMs can start, but network and VM network of all VMs are still not working. I can't ping IP of seed VM, overcloud VM and undercloud VM. I also can't ssh seed VM, overcloud and undercloud VM. I also can't see the HP Helion portal in Broswer. I check the network script under /etc/libvirt/qemu/networks, I think every script is ok. I don't know how I should solve this problem.

so who can help me for this question? Many Thanks.

Regards Nesta Guo

edit retag flag offensive close merge delete

2 answers

Sort by ยป oldest newest most voted

answered 2015-01-01 18:12:13 -0500

When HP Helion OpenStack CE is installed using the Virtual Install method, it will not survive a restart of the physical machine that is hosting the environment because of the multiple layers of virtualization that are used in this installation method. This is stated in the documentation, and requires reinstalling the environment starting from the step where you launch the script to create the Seed -- each time you power down the physical Ubuntu host machine.

edit flag offensive delete link more

answered 2014-12-15 00:52:09 -0500

9lives gravatar image

you have to make sure the seed vm and undercloud vm is working well first. second login to overcloud restart the service using os-refreash-config third restart all the services ad check the status. fourthly, restart the overcloud vm using virsh start

My suggestion is that if there is no critical data in your overcloud vms, the best way to resolve this is reinstall the helion openstack ce, just follow the pets and cattle theory in cloud computing. :-)

Hope that helps!


edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2014-12-02 03:24:40 -0500

Seen: 945 times

Last updated: Dec 15 '14