Reading through the docs for the first time, the reader encounters an instruction to provide a minimal configuration, with a link that they'd expect to tell them how to do this. At present the link actually takes them to the top of configuration.html, where they read some history about how devstack's configuration has changed over time. This is interesting and important and should be in the docs - but in my opinion a link about setting up a minimal configuration would be more useful if it takes me to a place that tells them about a minimal configuration. To get this, I've had to an an explicit link target into configuration.rst. I'm not hugely keen on this approach, as I don't think it scales well. I'd be open to suggestions about other approaches. The only idea I've had so far though is to simply move the minimal configuration section right to the top of the page, so that a link to the doc is a link to the minimal config - the historical information could be moved to its own topic somewhere further down the doc. Change-Id: I231ca1b7f17b55f09a4e058dab8ee433893f737e
6.7 KiB
DevStack - an OpenStack Community Production
overview configuration plugins faq changes hacking
Quick Start
Select a Linux Distribution
Only Ubuntu 14.04 (Trusty), Fedora 20 and CentOS/RHEL 7 are documented here. OpenStack also runs and is packaged on other flavors of Linux such as OpenSUSE and Debian.
Install Selected OS
In order to correctly install all the dependencies, we assume a specific minimal version of the supported distributions to make it as easy as possible. We recommend using a minimal install of Ubuntu or Fedora server in a VM if this is your first time.
Download DevStack
git clone https://git.openstack.org/openstack-dev/devstack
The
devstack
repo contains a script that installs OpenStack and templates for configuration filesConfigure
We recommend at least a
minimal-configuration
be set up.Start the install
cd devstack; ./stack.sh
It takes a few minutes, we recommend reading the script while it is building.
Guides
Walk through various setups used by stackers
guides/single-vm guides/single-machine guides/multinode-lab guides/neutron guides/devstack-with-nested-kvm guides/nova guides/devstack-with-lbaas-v2
All-In-One Single VM
Run OpenStack in a VM <guides/single-vm>
. The VMs
launched in your cloud will be slow as they are running in QEMU
(emulation), but it is useful if you don't have spare hardware laying
around. [Read] <guides/single-vm>
All-In-One Single Machine
Run OpenStack on dedicated hardware <guides/single-machine>
This can include a server-class machine or a laptop at home. [Read] <guides/single-machine>
Multi-Node Lab
Setup a multi-node cluster <guides/multinode-lab>
with
dedicated VLANs for VMs & Management. [Read] <guides/multinode-lab>
DevStack with Neutron Networking
Building a DevStack cluster with Neutron Networking <guides/neutron>
. This guide
is meant for building lab environments with a dedicated control node and
multiple compute nodes.
DevStack with KVM-based Nested Virtualization
Procedure to setup DevStack with KVM-based Nested Virtualization
<guides/devstack-with-nested-kvm>
. With this setup, Nova
instances will be more performant than with plain QEMU emulation.
Nova and devstack
Guide to working with nova features Nova and devstack <guides/nova>
.
DevStack Documentation
Overview
An overview of DevStack goals and priorities <overview>
Configuration
Configuring and customizing the stack <configuration>
Plugins
Extending DevStack with new features <plugins>
Recent Changes
An incomplete summary of recent changes <changes>
FAQ
The DevStack FAQ <faq>
Contributing
Pitching in to make DevStack a better place <hacking>
Code
A look at the bits that make it all go
Scripts
- stack.sh - The main script
- functions - DevStack-specific functions
- functions-common - Functions shared with other projects
- lib/apache
- lib/ceilometer
- lib/ceph
- lib/cinder
- lib/database
- lib/dstat
- lib/glance
- lib/heat
- lib/horizon
- lib/infra
- lib/ironic
- lib/keystone
- lib/ldap
- lib/neutron-legacy
- lib/nova
- lib/oslo
- lib/rpc_backend
- lib/sahara
- lib/swift
- lib/tempest
- lib/tls
- lib/trove
- lib/zaqar
- unstack.sh
- clean.sh
- run_tests.sh
- extras.d/50-ironic.sh
- extras.d/60-ceph.sh
- extras.d/70-sahara.sh
- extras.d/70-trove.sh
- extras.d/70-tuskar.sh
- extras.d/70-zaqar.sh
- extras.d/80-tempest.sh
- inc/ini-config
- inc/meta-config
- inc/python
- pkg/elasticsearch.sh
Configuration
local.conf stackrc openrc exerciserc eucarc
Tools
- tools/build_docs.sh
- tools/build_venv.sh
- tools/build_wheels.sh
- tools/create-stack-user.sh
- tools/create_userrc.sh
- tools/fixup_stuff.sh
- tools/info.sh
- tools/install_pip.sh
- tools/install_prereqs.sh
- tools/make_cert.sh
- tools/upload_image.sh
Samples
Exercises
- exercise.sh
- exercises/aggregates.sh
- exercises/boot_from_volume.sh
- exercises/bundle.sh
- exercises/client-args.sh
- exercises/client-env.sh
- exercises/euca.sh
- exercises/floating_ips.sh
- exercises/horizon.sh
- exercises/neutron-adv-test.sh
- exercises/sahara.sh
- exercises/sec_groups.sh
- exercises/swift.sh
- exercises/trove.sh
- exercises/volumes.sh
- exercises/zaqar.sh