Ask Your Question
0

Mirantis 8.0 - cannot create any instances

asked 2016-05-24 16:08:45 -0500

Bart gravatar image

Hi, I installed Mirantis 8.0 using the VirtualBox scripts. The host machine is Ubuntu 14.04 - 32GB ram. I tweaked the config.sh script to create 10 VirtualBox VMs each having 2.5 GB ram. Installation of MMirantis 8.0 went OK. I configured an Openstack environment - with pretty uch all default settings on 5 out of my 10 available nodes: 1 controller, 3 compute+storage nodes and 1 ceilometer node. Configuration of this also seems to be succesful, however I cannot create any instances at all - it always fails to spawn the instance with an exception (max retries exceeded) in the Nova manager.py script. All attempts use the Horizon UI and the testVM image. No clue why this is so, so any help is appreciated. I had good experiences with Mirantis 6.0, but this is starting to throw me off. Kind regards, Bart

edit retag flag offensive close merge delete

Comments

can you see any hypervisors in system admin panel, what is the status of nova-compute?

rduncan-t gravatar imagerduncan-t ( 2016-05-25 06:29:55 -0500 )edit

hypervisors are OK for all 3 compute nodes - all services are reported as up and running in the Horizon dashboards - thx - Bart

Bart gravatar imageBart ( 2016-05-25 16:23:39 -0500 )edit

Probably you don't have enough resources. How many CPUs are assigned to computes? Are you trying to launch a cirros with which flavor?

Fsoppelsa gravatar imageFsoppelsa ( 2016-05-31 05:21:28 -0500 )edit

2 answers

Sort by ยป oldest newest most voted
0

answered 2016-05-28 20:32:35 -0500

jdiaz9 gravatar image

Do you know if you chose KVM or QEMU as the hypervisor during deployment? I don't believe virtualbox has CPU hardware acceleration to allow for KVM to work. If you deployed as KVM that would explain the issue. You can check on a compute node and change it if necessary /etc/nova/nova-compute.conf.

Also, check pcs status and nova service-list to check that all services are up and running.

edit flag offensive delete link more
0

answered 2016-05-30 17:26:54 -0500

Bart gravatar image

Hi, A short follow up on this issue. As MOS 8.0 did not work for me and also was slow in any actions I decided to try MOS 7.0. I have has more success with this: - installation was quick and was working nice from the first attempt on - referring to a suggestion above - I know I have to use the qcow2 image format and qemu hypervisor, Mirantis Fuel is very clear on that - I now have 2 instances launched with a slightly different public IP setup - one I can reach from my hot machine, the other one not, this for sure is a networking issue (also judging from the network topology for both instances) - I am not a networking specialist at all though, so I am happy with having a way to reach my instance - what lacks in this Mirantis openstack 7 with Neutron networking compared to the Mirantis openstack 6 with Nova networking is this: from another machine in my real network (with a fixed route to the openstack host machine) I cannot access any VM from MOS 7 (Neutron), which I could in MOS 6 (Nova network)

I would like to understand this last issue - just to learn, I a fine with my current setup as it will suit my purposes.

Kind regards, and thanks for previous suggestions, Bart

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

1 follower

Stats

Asked: 2016-05-24 16:08:45 -0500

Seen: 216 times

Last updated: May 30 '16