This repo is now testing only with Python 3, so let's make a few cleanups: - Update requirements, no need for python_version anymore - Use newer openstackdocstheme version - Remove install_command from tox.ini, the default is fine Change-Id: Ib57fed37abe408b047b1ec364aea945ad06d75a5
|5 months ago|
|doc||5 months ago|
|labs||6 months ago|
|playbooks/scripts||2 years ago|
|tools||3 years ago|
|.gitignore||2 years ago|
|.gitreview||1 year ago|
|.zuul.yaml||1 year ago|
|CONTRIBUTING.rst||5 years ago|
|HACKING.rst||1 year ago|
|LICENSE||5 years ago|
|README.rst||1 year ago|
|bindep.txt||2 years ago|
|labs.py||5 years ago|
|tox.ini||5 months ago|
Training-labs provides an automated way to deploy Vanilla OpenStack, closely following the OpenStack Install Guide.
Training-labs offers an easy way to set up an OpenStack cluster which is a good starting point for beginners to learn OpenStack, and for advanced users to test out new features, and check out different capabilities of OpenStack.
On top of that training-labs is also a good way to test the installation instructions on a regular basis.
Training-labs is a project under OpenStack Documentation. For more information see the OpenStack wiki.
VirtualBox is the default hypervisor used by training-labs. Alternatively, you can use KVM (just set
The current release is master which usually deploys the current stable OpenStack release. Unless you have a reason to go with an older release, we recommend using master.
For non-development purposes (training, etc.), the easiest way to get the code is through downloading the desired archive from OpenStack Training Labs. Unpack the archive and you are good to go.
$ cd training-labs/labs/
By default, the cluster is built on Virtualbox VMs.
Run the script by:
$ ./st.py -b cluster
The easiest and recommended way to get everything you need besides VirtualBox is to download a zip file for Windows from the Training Labs page.
The zip files include pre-generated Windows batch files.
Creates the host-only networks used by the node VMs to communicate:
Creates the base disk:
Creates the node VMs based on the base disk:
Running this will automatically spin up 2 virtual machines in VirtualBox/KVM:
Now you have a multi-node deployment of OpenStack running with the following services installed.
There are two ways to access the services:
You can access the dashboard at: http://10.0.0.11/horizon
Demo User Login:
You can ssh to each of the nodes by:
# Controller node $ ssh firstname.lastname@example.org # Compute node $ ssh email@example.com
Credentials for all nodes:
After you have ssh access, you need to source the OpenStack credentials in order to access the services.
Two credential files are present on each of the nodes:
Source the following credential files
For Admin user privileges:
$ source admin-openstackrc.sh
For Demo user privileges:
$ source demo-openstackrc.sh
Note: Instead 'source' you can use '.', or you define an alias. Now you can access the OpenStack services via CLI.
To review specifications, see Training-labs
To contribute, join the IRC channel,
#openstack-doc, on IRC freenode or write an e-mail to the OpenStack Development Mailing List
firstname.lastname@example.org. Please use
[training-labs] tag in the subject of the email message.
You may have to subscribe to the OpenStack Development Mailing List to have your mail accepted by the mailing list software.
Feel free to ping Roger, Julen, or Pranav via email or on the IRC channel
#openstack-doc regarding any queries about training-labs.
Training-labs uses the Doc Team Meeting: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting
Follow various links on training-labs here: https://wiki.openstack.org/wiki/Documentation/training-labs