Devstack as a testing ground

Devstack as a testing ground

Monday, Mar 20, 2017

@ Chris Suttles

In my last post, I ran into some challenges with Ocata. The placement API and cells v2 configuration was not yet documented (that documentation is actually still only in draft form), and this made configuring them more difficult than most OpenStack services. This is where Devstack can be a very useful tool. In the post on ask.openstack where I found some help before there was much available, there's this very helpful suggestion for configuring cells and placement on devstack:
Placement API and Cells in Ocata

Placement API and Cells in Ocata

Saturday, Mar 11, 2017

@ Chris Suttles

What's up, Doc? In Ocata release, the placement API and cells (v2) are mandatory. This is not currently documented in the official installation documentation: https://docs.openstack.org/ocata/install-guide-ubuntu/nova-controller-install.html edit: There's now a draft of docs, based on the work on the bug mentioned later in this post here: http://docs-draft.openstack.org/28/438328/12/check/gate-openstack-manuals-tox-doc-publish-checkbuild/846ac33//publish-docs/draft/install-guide-ubuntu/nova-controller-install.html At the time of writing this post, there is no mention of placement API of cells v2, which are both mandatory in Ocata release.
Troubleshooting OpenStack

Troubleshooting OpenStack

Tuesday, Mar 7, 2017

@ Chris Suttles

Everything begins with Keystone This is nothing new, but it's important to point out. Nothing works if Keystone is not set up properly. The easiest way to check if Keystone and your client are set up correctly is to run: openstack token issue An often overlooked part of Keystone is the service catalog. Keystone is responsible for authentication and authorization in OpenStack, but it's also responsible for the service catalog. If you run the following, you'll see the contents of the service catalog:
Getting started with OpenStack

Getting started with OpenStack

Monday, Feb 27, 2017

@ Chris Suttles

OpenStack is exciting! I started using OpenStack at work; in fact, my desire to work on it and learn more about it was a major factor in accepting my current position. The learning curve is steep, but don't let that intimidate you. The rewards for persistence are great. Crawl, Walk, Run OpenStack is a really large project, with a lot of moving parts. My approach, after some trial and error, and the approach I advise to people new to OpenStack is to crawl, walk, and run.

Social Links