| commit | ff10ac318ce4be49d8bceafb7fea92ae1655b497 | [log] [tgz] |
|---|---|---|
| author | Matt Riedemann <mriedem@us.ibm.com> | Mon Feb 13 12:44:24 2017 -0500 |
| committer | Matt Riedemann <mriedem@us.ibm.com> | Mon Feb 13 16:31:39 2017 -0500 |
| tree | 0c53e834d7a3b8854d51b0b6d56fb2783d8d9c3c | |
| parent | e0a37cf21e43fbb4ba3f9f8fa5321a0a0e1bedf1 [diff] |
Remove distro support based on new libvirt minimum Nova is going to increase the minimum required libvirt in Pike to 1.2.9 in change: I9a972e3fde2e4e552f6fc98350820c07873c3de3 Based on the libvirt distro support matrix wiki [1] that drops support for Ubuntu Trusty and Debian 7.0/Wheezy. Trusty has libvirt 1.2.2 and Wheezy has 0.9.12 (the Wheezy support should have been removed long ago apparently). The 7.0 removed here is for Wheezy also based on commit b2ef890db3d78b24f9da2f4dd80502165c669ad0. This does not undo the check for "trusty" with the EBTABLES_RACE_FIX in lib/nova_plugins/function-libvirt since you can still force devstack to run on Trusty if you specify the FORCE=yes variable. Note that RHEL 7.1 has libvirt 1.2.8 so it won't technically work with devstack and nova + pike + libvirt, but with the way os_RELEASE is calculated the minor version is dropped for RHEL distros so we just get "rhel7". Also note that this doesn't attempt to continue supporting Trusty or Wheezy if nova is not configured to use libvirt, simply in order to start moving forward on devstack distro support in general and to keep some sanity and closeness to what we test with in the CI system. While we're in here, we also drop Fedora 23 and add Ubuntu Zesty. [1] https://wiki.openstack.org/wiki/LibvirtDistroSupportMatrix Depends-On: I9a972e3fde2e4e552f6fc98350820c07873c3de3 Depends-On: If69f99bd789e646b0261e27a8a061efde32436f7 Change-Id: I6617283afd798af37e64913b7865cea3c8a62aba
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.