Ask Your Question

craigtracey's profile - activity

2014-05-24 16:34:21 -0500 answered a question unable to launch instance on second compute node

From the looks of the logs, this is due to a nova-compute failure to create the instance on the remote compute host. And, further, it looks like the issue is that the user running the nova service is unable to write to /var/lib/nova. I would check permissions there first - they are almost certainly incorrect and the root cause of this issue.

Secondarily, be sure to check that the nova services are in a good state. "nova service-list" will show you what the state of each nova service is throughout the cluster. While it would not show this runtime failure, it may alert you to other issues.

Hope this helps, Craig

2014-05-24 16:28:33 -0500 answered a question "nova agent-list" returns empty

There are many reasons why the Nova scheduler would put an instance into an error state. Most common, in my opinion, would be that there is no valid host to schedule it to, but your mileage may vary. The best way to determine why an instance is in the error state is to run "nova show <uuid>". This should give you the error that was encountered. Similarly, the nova-scheduler log will clearly state why it could not proceed as expected.

As for "nova agent-list" being empty, what you really want to be running is "nova service-list." This will give you the current status of the various nova services within the cluster.

Hope this helps, Craig

2014-05-15 03:56:02 -0500 answered a question post creation script when launching server through novaclient python bindings?


Yes you can automate a wide variety of things via a package named cloud-init. This package primarily reads from provided user-data (or a variety is other sources), and configures a guest instance accordingly. I wrote a blog post about this done time ago...hopefully this will help you:

Let me know if this gets you moving... Best, Craig

2014-04-06 22:39:28 -0500 received badge  Citizen Patrol
2014-04-05 02:08:47 -0500 received badge  Nice Answer (source)
2014-04-04 22:29:08 -0500 answered a question Centos 6.5 - Havana - InstanceTypeDiskTooSmall

Hi theoni,

The issue here is that the image you are trying to boot is too large for the flavor you have requested. If you click on the 'Flavor' tab in the Horizon UI, you will see that you can change the size of the 'Root Disk' by clicking 'Edit Flavor.'

Similarly, you can manipulate flavors by way of the nova CLI.

In either case, simply updating or creating a flavor with a Root Disk large enough to accommodate your image will resolve the issue.

Hope this helps... Craig

2014-01-30 13:34:06 -0500 received badge  Enthusiast
2014-01-22 16:13:55 -0500 received badge  Nice Answer (source)
2014-01-21 05:15:53 -0500 received badge  Teacher (source)
2014-01-21 05:15:53 -0500 received badge  Necromancer (source)
2014-01-09 15:13:35 -0500 answered a question 'ExtensionManager' object does not support item assignment

Hi Atti,

The problem here is that you are using the latest version of cliff (1.5.2). See this bug:

Ultimately cliff has changed in 1.5.2 and the python requirements called out by python-neutronclient only call for cliff>=1.4.1, hence you got the latest.

I also ran into this. I think you have a few options: 1) install the latest python-neutronclient from github 2) ensure that you are using cliff < 1.5.2. (The next latest is 1.4.5)

Are you installing via packages?

Hope this helps, Craig

2013-11-23 20:55:39 -0500 answered a question what is the password for ubuntu 12.04 cloud image?

dathomir, in order to use the Ubuntu precise image, simply create a new keypair (or, of course, use an existing one) and specify that during instance boot. This will allow you in with root access just as you would do with any other OpenStack instance.

Hope this helps, Craig