{"id":15,"date":"2015-07-29T16:53:32","date_gmt":"2015-07-29T15:53:32","guid":{"rendered":"http:\/\/www.haxed.me.uk\/?p=15"},"modified":"2015-07-30T10:27:25","modified_gmt":"2015-07-30T09:27:25","slug":"argumentative-supernova-and-python-pip","status":"publish","type":"post","link":"https:\/\/haxed.me.uk\/index.php\/2015\/07\/29\/argumentative-supernova-and-python-pip\/","title":{"rendered":"Argumentative Supernova and python pip"},"content":{"rendered":"

My first few weeks at working in cloud, particularly openstack were challenging. There were quite a few tools ,and interpreters that I had to get used to using and debugging to properly use software, and as always, the compiler or interpreters messages aren’t usually helpful. It’s worth noting that before we start, some of the messages from python applications can be unhelpful and appear to be dependency issues but in one case it was because of an extra character lurking in my .supernova configuration, thanks to a colleague of mine who pointed this out yesterday.<\/p>\n

\"openstack\"<\/a><\/p>\n

One of the important things to get a handle on was the installation and configuration of my supernova and nova openstack for use with the Rackspace UK API. Here is some of the ‘arguments’ we had at the commandline.<\/p>\n

There is some pretty helpful information listed at: https:\/\/developer.rackspace.com\/blog\/supernova-managing-openstack-environments-made-easy\/<\/p>\n

but I decided that after all the problems I had, specific to my Mac OS X Yosemite 10.10.4 that some sort of additional documentation on getting started was necessary, if not for other people, but my own personal record! I list quite a few of the common mishaps I ran into when installing.<\/p>\n

# I had lots of problems so I started from scratch<\/p>\n

pip freeze |\u00a0 xargs pip uninstall -y<\/p>\n

git clone https:\/\/github.com\/major\/supernova
\n# install latest supernova from github (optional)
\nsudo python setup.py install<\/p><\/blockquote>\n

After doing this and running a ‘supernova’ command from the commandline I am quickly informed that<\/p>\n

ERROR (AuthSystemNotFound): AuthSystemNotFound: \u2018rackspace’<\/p><\/blockquote>\n

We should make sure that the novaclient and supernova are installed and note that the supernova application is merely a wrapper for the the nova openstack api connector.<\/p>\n

pip install supernova rackspace-novaclient<\/p><\/blockquote>\n

I also got a bit crazy and started trying to install different versions of novaclient noting that there were some possible compatibility problems between supernova and nova due to differences in the packages. I also resorted to running a ‘brew install python’ after getting fed up, but I won’t need to cover this here because brew is fairly simple<\/p>\n

pip install -U python-novaclient==2.11.1<\/p><\/blockquote>\n

This didn’t bring me much luck and I was sitll encountering the AuthSystemNotFound error. So I started to try and dig deeper into what was going on, and what packages were available and\/or might be missing.<\/p>\n

pip search rackspace<\/p>\n

pip search rackspace | grep auth<\/p>\n

rackspace-auth-openstack\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 – Rackspace Auth Plugin for OpenStack Clients.
\nrackspace-auth-neutronclientext\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 – Rackspace Auth Plugin for OpenStack Neutron Clients.
\nrackspace-glanceclient\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 – Metapackage to install python-glanceclient and Rackspace auth package<\/p><\/blockquote>\n

Confirming my suspicions that a plugin was not installed by pip when I ran pip install supernova rackspace-novaclient. So I ran<\/p>\n

pip install rackspace-auth-openstack
\nsupernova lon image-list
\n__ Error Output ______________________________________________________________
\nERROR: No module named auth_plugin<\/p><\/blockquote>\n

Which certainly meant progress, now a different error, “auth_plugin”. So I re-ran an install of rackspace-novaclient<\/p>\n

pip install rackspace-novaclient<\/p>\n

 <\/p><\/blockquote>\n

paying special attention to these particular entries:<\/p>\n

Successfully installed os-diskconfig-python-novaclient-ext-0.1.2 os-networksv2-python-novaclient-ext-0.25 os-virtual-interfacesv2-python-novaclient-ext-0.19 rackspace-novaclient-1.4 rax-default-network-flags-python-novaclient-ext-0.3.1 rax-scheduled-images-python-novaclient-ext-0.3.1<\/p><\/blockquote>\n

It looked like the two were missing some dependencies that were causing this particular cryptic error above with auth_plugin.<\/p>\n

I found then when running a supernova lon image-list I was presented with a new difficulty:<\/p>\n

supernova lon image-list<\/p>\n

__ Error Output ______________________________________________________________
\nERROR: cannot import name cliutils<\/p><\/blockquote>\n

This was probably the least cryptic error because simply searching for cliutils with pip was easy enough, and then i installed that package:<\/p>\n

pip search cliutils
\ncliutils\u00a0\u00a0\u00a0\u00a0 – A collection of utilities easing the creation of command line scripts<\/p>\n

pip install cliutils<\/p><\/blockquote>\n

for special measure I also installed a package called ‘rack’ and upgraded supernova once more from pip repository. I do not know if these steps are necessary but if your still having trouble running supernova you can always try them:<\/p>\n

pip install rack<\/p>\n

pip install supernova –upgrade<\/p><\/blockquote>\n

Which gives the friendly and expected output:<\/p>\n

supernova customer image-list
\n[SUPERNOVA] Running nova against customer…
\n+————————————–+————————————————————–+——–+————————————–+
\n| ID\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 | Name\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 | Status | Server\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 |
\n+————————————–+————————————————————–+——–+————————————–+
\n| 8785022e-a29c-4e31-9d9c-213b87c63e2a | Arch 2015.7 (PVHVM)\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 | ACTIVE |\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 |
\n| 6e44a225-85f4-4d53-858b-a3022939845b | CentOS 5 (PV)\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 |
\n……. etc<\/p>\n

Please note IMPORTANTLY that to properly query the Rackspace Openstack API thru supernova nova wrapper you will require a properly formatted .supernova config file. This actually takes some time to get to grips with. Your supernova file should , usually be in your user context home, ie cd ~<\/strong><\/p>\n

.supernova config template<\/p>\n[myopenstackconfig]\nOS_AUTH_URL=https:\/\/identity.api.rackspacecloud.com\/v2.0\/
\nOS_AUTH_SYSTEM=rackspace
\nOS_COMPUTE_API_VERSION=1.1
\nNOVA_RAX_AUTH=1
\nOS_REGION_NAME=LON
\nNOVA_SERVICE_NAME=cloudServersOpenStack
\nOS_PASSWORD=yourrackspaceAPIkeygoeshere
\nOS_USERNAME=yourrackspacemycloudusernamegoeshere
\nOS_TENANT_NAME=yourrackspaceaccountnumbergoeshere<\/p>\n

If you don’t like the idea of using plaintext in your config file you could use supernova-keyring your .supernova config file must look like this:<\/p>\n[myopenstackconfig]\nOS_AUTH_URL=https:\/\/identity.api.rackspacecloud.com\/v2.0\/
\nOS_AUTH_SYSTEM=rackspace
\nOS_COMPUTE_API_VERSION=1.1
\nNOVA_RAX_AUTH=1
\nOS_REGION_NAME=LON
\nNOVA_SERVICE_NAME=cloudServersOpenStack
\nOS_PASSWORD=USE_KEYRING[‘UKRackspaceAccountAPIKey’]\nOS_USERNAME=USE_KEYRING[‘UKRackspaceAccountUser’]\nOS_TENANT_NAME=USE_KEYRING[‘UKRackspaceAccountDDI’]\n

at the shell you will have to set the variables for the ‘keyring’ do that like this and you will be prompted to type in your account API Key, and username and DDI (which is the 6 or 7 digit number your account is in the url address when using mycloud) the details there:<\/p>\n

Type this at the commandline<\/p>\n

# something like myusername
\nsupernova-keyring -s global RackspaceAccountUser
\n# something like 80aa1af9a6Bc459076834592ab324a<\/p>\n

supernova-keyring -s global RackspaceAccountAPIKey<\/p>\n

# something like 1004345
\nsupernova-keyring -s global RackspaceAccountDDI<\/p><\/blockquote>\n

Here are some critically important and helpful links for supernova guides , tutorials, examples and so on, the developer “Major Harden” is a great guy and I am sure if you have issues further to what I had he will be able to help you further over at GitHub.<\/p>\n

Supernova Developers’ website and documentation https:\/\/major.io\/2012\/06\/05\/supernova-manage-multiple-openstack-nova-environments-with-ease\/<\/a>
\nLatest github for cloning on Github https:\/\/github.com\/major\/supernova<\/a>
\n1 Hour Presentation on Supernova https:\/\/www.youtube.com\/watch?v=BZGhoCYZKEM<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

My first few weeks at working in cloud, particularly openstack were challenging. There were quite a few tools ,and interpreters that I had to get used to using and debugging to properly use software, and as always, the compiler or … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-15","post","type-post","status-publish","format-standard","hentry","category-uncategorised"],"_links":{"self":[{"href":"https:\/\/haxed.me.uk\/index.php\/wp-json\/wp\/v2\/posts\/15","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/haxed.me.uk\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/haxed.me.uk\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/haxed.me.uk\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/haxed.me.uk\/index.php\/wp-json\/wp\/v2\/comments?post=15"}],"version-history":[{"count":0,"href":"https:\/\/haxed.me.uk\/index.php\/wp-json\/wp\/v2\/posts\/15\/revisions"}],"wp:attachment":[{"href":"https:\/\/haxed.me.uk\/index.php\/wp-json\/wp\/v2\/media?parent=15"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/haxed.me.uk\/index.php\/wp-json\/wp\/v2\/categories?post=15"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/haxed.me.uk\/index.php\/wp-json\/wp\/v2\/tags?post=15"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}