| commit | 19f4b3faae5f64a497bf6c13fb29b65301ae499c | [log] [tgz] |
|---|---|---|
| author | Ihar Hrachyshka <ihrachys@redhat.com> | Thu Feb 23 20:44:18 2017 +0000 |
| committer | Ihar Hrachyshka <ihrachys@redhat.com> | Tue Feb 28 21:07:52 2017 +0000 |
| tree | 202da91d294f5124ca7ca6d3eb81b2c881c62b82 | |
| parent | 0e1e78117e63af1d55b969469642a7337c616aa0 [diff] |
lib/neutron: stop loading all config files into all processes DHCP agent should not load core plugin config file; L3 agent has no interest in metadata agent configuration file; etc. It's a mistake to form a single global list of configuration files and pass it into all processes. Every process should have its own list, that may or may not have some files in common with other processes. The only file that is common to all neutron processes is neutron.conf, and we could in theory keep it into the common list. But I decided at this point it's better to be explicit about what's loaded into services. Also the order of arguments is important, and neutron.conf should always be the first CLI argument, which is hard to achieve by keeping neutron.conf file in the global list. Plugins may be interested in loading additional files into neutron processes. For example, dragonflow needs to load /etc/neutron/dragonflow.ini into neutron-server. But we should not necessarily load all those files into all processes, so such extendable lists should be per process. Besides, neutron_server_config_add_new is already available to use to append additional configuration files for neutron-server. That's why the patch completely kills the NEUTRON_CONFIG_ARG variable. Depends-On: I4bd54a41a45486a5601373f9a9cce74d7686d1aa Change-Id: Ia3c3862399bba335db5edf9ea70f850fb2638d09
DevStack is a set of scripts and utilities to quickly deploy an OpenStack cloud.
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.
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
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 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).
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.