openstack
/
devstack
Code Issues Proposed changes
System for quickly installing an OpenStack cloud from upstream git for testing and development.
8,268 Commits 10 Branches 12 Tags 122 MiB
Shell 93.6%
Python 6%
Makefile 0.3%
Jinja 0.1%
Go to file
Matt Riedemann f15224c740 Create cell1 cell before n-api starts 
Change ac5fdb4c40 introduced
a problem for gnocchi CI because the deployments steps
are now:

1. create cell0
2. start nova-api (with multiple workers)
3. install ceilometer via extras
4. ceilometer calls nova-api to list servers; at this point
   nova-api getes the list of cells and caches them, which
   will just be cell0
5. create cell1 via simple_cell_setup which also discovers
   the n-cpu node so we can schedule instances
6. gnocchi tests create and list instances and at this point it hits
   an n-api worker that only has cell0 cached so it does not
   find some test servers it created and fails.

The cell0 and cell1 cells should be created in the nova_api db
before starting n-api so that when we first list instances, we
store both cells in the cache that's in n-api. This deployment
order is also how the nova docs describe rolling out cells v2
but the way we were doing this devstack wasn't following that,
or accounting for when devstack plugins are loaded via extras.

This change creates the main cell1 cell earlier in the setup
before n-api is started, and then changes to just run
discover_hosts at the end after n-cpu is running (which is what
simple_cell_setup and map_cell_and_hosts would do implicitly).

Change-Id: I38eab6707340253a10159a169ae61d34784c2d28
Related-Bug: #1669473
 		2017-03-02 15:33:08 -05:00
data Fix comment in plugin-registry header 2016-08-31 10:07:06 +10:00
doc/source Using sudo in the Quick start section 2017-02-13 15:14:41 +01:00
exercises Neutron: use "OSC show -f value -c id" instead of "OSC list + grep" 2016-11-18 12:18:09 +01:00
extras.d Merge "Ensure testing configuration can run as late as possible" 2016-11-30 16:30:38 +00:00
files Use qemu-kvm-ev package on centos 2017-02-27 18:59:49 +11:00
gate Mostly docs cleanups 2015-03-28 14:35:12 -05:00
inc Merge "install LIBS_FROM_GIT using python 2 and 3 where appropriate" 2017-02-28 16:37:49 +00:00
lib Create cell1 cell before n-api starts 2017-03-02 15:33:08 -05:00
pkg Use java version independent package on Ubuntu 2016-12-15 08:48:02 -08:00
samples Update local.sh sample file to use OSC 2016-11-11 15:11:54 +01:00
tests allow config to manage python3 use explicitly 2017-01-10 16:08:14 +00:00
tools Ensure we install setuptools from requirements 2017-02-27 11:35:43 +11:00
.gitignore Add files/*.deb and files/*.deb.* to gitignore 2016-08-25 23:36:12 +08:00
.gitreview Add .gitreview config file for gerrit. 2011-11-16 11:24:49 -08:00
.mailmap Remove AUTHORS 2014-08-14 13:52:28 +10:00
FUTURE.rst Document where we are going 2015-02-05 16:20:52 -05:00
HACKING.rst Fixes language: "following allowing" -> "allowing" 2016-08-23 10:08:03 +01:00
LICENSE Add Apache 2 LICENSE file 2012-04-18 01:45:35 -05:00
MAINTAINERS.rst Move Sahara into in-tree plugin 2015-07-01 16:09:56 +00:00
Makefile Suppressed echoing of the line. 2016-04-30 14:11:52 +05:30
README.md Update stable branch example 2016-11-03 10:10:03 +00:00
clean.sh Use delete action for clean up *.pyc files 2017-01-13 09:16:42 -06:00
exercise.sh Remove EC2 API from devstack 2016-03-15 13:32:23 +11:00
exerciserc Remove EC2 API from devstack 2016-03-15 13:32:23 +11:00
functions unify logging setup on all services 2017-01-20 10:48:29 -05:00
functions-common Merge "Remove distro support based on new libvirt minimum" 2017-02-25 16:02:50 +00:00
openrc Remove OS_NO_CACHE from openrc 2017-01-31 11:59:09 -05:00
run_tests.sh Remove old comment in run_tests.sh 2015-04-17 13:23:25 +10:00
setup.cfg Replace the devstack.org with devstack docs url 2015-09-26 18:05:34 +05:30
setup.py Convert all HTML doc to RST 2014-10-22 12:27:00 -04:00
stack.sh Create cell1 cell before n-api starts 2017-03-02 15:33:08 -05:00
stackrc Merge "install OSC with py3 by default" 2017-03-02 05:39:08 +00:00
tox.ini Update to bashate 0.5.1 2016-04-26 17:53:45 +10:00
unstack.sh Merge "Load neutron-legacy only if enabled" 2017-01-03 19:53:37 +00:00

README.md

DevStack is a set of scripts and utilities to quickly deploy an OpenStack cloud.

Goals

  • To quickly build dev OpenStack environments in a clean Ubuntu or Fedora environment
  • To describe working configurations of OpenStack (which code branches work together? what do config files look like for those branches?)
  • To make it easier for developers to dive into OpenStack so that they can productively contribute without having to understand every part of the system at once
  • To make it easy to prototype cross-project features
  • To provide an environment for the OpenStack CI testing on every commit to the projects

Read more at http://docs.openstack.org/developer/devstack

IMPORTANT: Be sure to carefully read stack.sh and any other scripts you execute before you run them, as they install software and will alter your networking configuration. We strongly recommend that you run stack.sh in a clean and disposable vm when you are first getting started.

Versions

The DevStack master branch generally points to trunk versions of OpenStack components. For older, stable versions, look for branches named stable/[release] in the DevStack repo. For example, you can do the following to create a Newton OpenStack cloud:

git checkout stable/newton
./stack.sh

You can also pick specific OpenStack project releases by setting the appropriate *_BRANCH variables in the localrc section of local.conf (look in stackrc for the default set). Usually just before a release there will be milestone-proposed branches that need to be tested::

GLANCE_REPO=git://git.openstack.org/openstack/glance.git
GLANCE_BRANCH=milestone-proposed

Start A Dev Cloud

Installing in a dedicated disposable VM is safer than installing on your dev machine! Plus you can pick one of the supported Linux distros for your VM. To start a dev cloud run the following NOT AS ROOT (see DevStack Execution Environment below for more on user accounts):

./stack.sh

When the script finishes executing, you should be able to access OpenStack endpoints, like so:

We also provide an environment file that you can use to interact with your cloud via CLI:

# source openrc file to load your environment with OpenStack CLI creds
. openrc
# list instances
nova list

DevStack Execution Environment

DevStack runs rampant over the system it runs on, installing things and uninstalling other things. Running this on a system you care about is a recipe for disappointment, or worse. Alas, we're all in the virtualization business here, so run it in a VM. And take advantage of the snapshot capabilities of your hypervisor of choice to reduce testing cycle times. You might even save enough time to write one more feature before the next feature freeze...

stack.sh needs to have root access for a lot of tasks, but uses sudo for all of those tasks. However, it needs to be not-root for most of its work and for all of the OpenStack services. stack.sh specifically does not run if started as root.

DevStack will not automatically create the user, but provides a helper script in tools/create-stack-user.sh. Run that (as root!) or just check it out to see what DevStack's expectations are for the account it runs under. Many people simply use their usual login (the default 'ubuntu' login on a UEC image for example).

Customizing

DevStack can be extensively configured via the configuration file local.conf. It is likely that you will need to provide and modify this file if you want anything other than the most basic setup. Start by reading the configuration guide for details of the configuration file and the many available options.