From d340d84522a3d3adc3f88dfe3ff125684f951f5c Mon Sep 17 00:00:00 2001 From: Jose Luis Franco Arza Date: Mon, 22 Oct 2018 09:54:40 +0200 Subject: [PATCH] Remove tripleo.sh entry from developer docs. The tripleo.sh is not in used anymore now that the CI has been migrated to zuul v3. This patch removes the documentation entry explaining its functioning from Developer docs. Change-Id: I9a23e95cb8240e0a60c7a18b06d5a81c3fa2872d --- doc/source/install/developer/developer.rst | 1 - doc/source/install/developer/tripleo.sh.rst | 97 --------------------- 2 files changed, 98 deletions(-) delete mode 100644 doc/source/install/developer/tripleo.sh.rst diff --git a/doc/source/install/developer/developer.rst b/doc/source/install/developer/developer.rst index b8a7295e..eed1dadd 100644 --- a/doc/source/install/developer/developer.rst +++ b/doc/source/install/developer/developer.rst @@ -6,7 +6,6 @@ Documentation of developer-specific options in |project|. .. toctree:: - tripleo.sh tht_walkthrough/tht_walkthrough upgrades/upgrades release diff --git a/doc/source/install/developer/tripleo.sh.rst b/doc/source/install/developer/tripleo.sh.rst deleted file mode 100644 index 8ce3c4bc..00000000 --- a/doc/source/install/developer/tripleo.sh.rst +++ /dev/null @@ -1,97 +0,0 @@ -tripleo.sh -========== - -`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 -`_ , etc). -tripleo.sh is also used by tripleo-ci to test TripleO patches. - -Get tripleo.sh --------------- - -tripleo.sh is from the `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 `_ 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 -`_ -source code for details.