c796d38b6a
We're getting to have a lot of "advanced" docs, and most of those fit into one of a few categories. This change separates the advanced topics into one of the following categories: -Feature Config -Baremetal Node Config -Backend Config -Custom Config -Developer Docs Single image building is moved to post deployment since it's not a normal part of the initial deployment. Change-Id: I14e31469a533efbfe3c18c4bd11da8b3f8f455e6
98 lines
2.9 KiB
ReStructuredText
98 lines
2.9 KiB
ReStructuredText
tripleo.sh
|
||
==========
|
||
|
||
`tripleo.sh
|
||
<http://git.openstack.org/cgit/openstack-infra/tripleo-ci/tree/scripts/tripleo.sh>`_
|
||
is a script that can be used to help bootstrap development environments. It
|
||
automates many of the steps in this documentation to help get setup faster.
|
||
It's opinionated automation around other production tooling
|
||
(`python-tripleoclient
|
||
<http://git.openstack.org/cgit/openstack/python-tripleoclient>`_ , etc).
|
||
tripleo.sh is also used by tripleo-ci to test TripleO patches.
|
||
|
||
Get tripleo.sh
|
||
--------------
|
||
|
||
tripleo.sh is from the `tripleo-ci
|
||
<http://git.openstack.org/cgit/openstack-infra/tripleo-ci>`_ project. git
|
||
clone tripleo-ci, and the script is under the scripts/ directory::
|
||
|
||
git clone https://git.openstack.org/openstack-infra/tripleo-ci
|
||
tripleo-ci/scripts/tripleo.sh --help
|
||
|
||
|
||
Using tripleo.sh
|
||
----------------
|
||
|
||
The tripleo.sh script is intended to run on an new instack undercloud setup.
|
||
That is, you would follow the `environment setup <http://docs.openstack.org/developer/tripleo-docs/environments/environments.html#environment-setup>`_ docs through to and including
|
||
`instack-virt-setup` (for a virt setup), ssh onto the resulting undercloud
|
||
node and then run tripleo.sh with the options identified below.
|
||
|
||
Options
|
||
^^^^^^^
|
||
|
||
The help text shows what options are available, and the options are listed in
|
||
corresponding order with how a TripleO deployment is done.
|
||
|
||
Repository setup::
|
||
|
||
tripleo-ci/scripts/tripleo.sh --repo-setup
|
||
|
||
Installing the undercloud::
|
||
|
||
tripleo-ci/scripts/tripleo.sh --undercloud
|
||
|
||
Building overcloud images::
|
||
|
||
tripleo-ci/scripts/tripleo.sh --overcloud-images
|
||
|
||
Registering nodes::
|
||
|
||
tripleo-ci/scripts/tripleo.sh --register-nodes
|
||
|
||
Introspect nodes::
|
||
|
||
tripleo-ci/scripts/tripleo.sh --introspect-nodes
|
||
|
||
Deploy overcloud::
|
||
|
||
tripleo-ci/scripts/tripleo.sh --overcloud-deploy
|
||
|
||
Alternatively, all of the above options can be execute at once with::
|
||
|
||
tripleo-ci/scripts/tripleo.sh --all
|
||
|
||
Test overcloud::
|
||
|
||
tripleo-ci/scripts/tripleo.sh --overcloud-pingtest
|
||
|
||
Requirements for testing the overcloud: overcloudrc file (Located by default
|
||
in the undercloud current user’s directory).
|
||
|
||
This option will check that the overcloud is able to create a stack,
|
||
testing several OpenStack components in the process. The following steps
|
||
are made in order to check the stack creation:
|
||
|
||
- Download a Linux image and upload it to glance with the name pingtest_image.
|
||
|
||
- Create an external neutron network called nova.
|
||
|
||
- Create a subnet in the nova network.
|
||
|
||
- Create a test stack called tenant-stack, using heat, which spawns a guest
|
||
in the overcloud and attach it to the nova network.
|
||
|
||
- Ping the floating IP address assigned to the new guest.
|
||
|
||
After the test, the created resources are deleted.
|
||
|
||
|
||
Environment variables
|
||
^^^^^^^^^^^^^^^^^^^^^
|
||
|
||
Certain values and assumptions can be changed via environment variables. See
|
||
the `tripleo.sh
|
||
<http://git.openstack.org/cgit/openstack-infra/tripleo-ci/tree/scripts/tripleo.sh>`_
|
||
source code for details.
|