Extra Ansible roles to automate TripleO deployments
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

131 lines
6.4 KiB

<html lang="en-US">
<title>README for Quickstart Job Reproducer Script</title>
<h1>How to reproduce a job result using the reproducer-quickstart.sh script</h1>
<p>Check the top-level logs directory for a file <b>reproducer-quickstart.sh</b>.
Running this file will set up a stack on a personal tenant where the job run
can be reproduced.
If no <b>reproducer-quickstart.sh</b> file is found, that usually means an
infra failure before Quickstart could start or a problem in collecting logs.
Check on IRC OFTC channel <i>#tripleo</i> to see if there's an ongoing infra
<h2>What is the reproducer-quickstart.sh script?</h2>
<p>A <b>reproducer-quickstart.sh</b> script is generated at the top-level log directory
for jobs that run TripleO-Quickstart and toci_gate_test.sh. Running the script
from a host machine will set up a stack to the point where the user can ssh to the
undercloud, source a variable file, and run <b>toci_gate_test.sh</b>. As such,
reproducing the complete jobs result requires some manual interaction.</p>
<p>The <b>reproducer-quickstart.sh</b> script is generated to be specific to that
job and <b>reproducer-quickstart.sh</b> scripts from other jobs will be different.</p>
<h2>Running the reproducer-quickstart.sh script</h2>
<p>Use <code>cURL</code>, <code>wget</code> or a similar tool to copy the
<b>reproducer-quickstart.sh</b> to a clean working directory on a host from
where you can access the cloud tenant you want to run the reproducer on.
Make sure that the copied script is executable (has +x permissions) before you
attempt to run it.
<b>Source the tenant credentials before running the script on a host cloud.</b>
Also, it is a good idea to check that the tenant has enough capacity
and resources to reproduce the job before you begin.</p>
<p>Note that, by default, the <b>reproducer-quickstart.sh</b>
script is written to run an a personal RDO Cloud tenant. Instructions on how to
modify the script to run on another host cloud are included in a section below.</p>
<h2>Running the reproducer-quickstart.sh script on a single virt host using libvirt</h2>
<p>The <code>-l|--libvirt</code> option allows the user to reproduce multinode
or single node jobs running on a single virt host, using libvirt. This
option was added as an alternative when host clouds are not available.</p>
<p>Note that the script sets the virthost to be so the reproducer
<b>must be run from the virt host itself</b>. Attempting to use a
working machine/laptop as the Ansible host and targeting a test box
indirectly is not recommended.
Run <code>cat ~/.ssh/id_rsa.pub >> ~/.ssh/authorized_keys</code>
to allow for login to</p>
<p>When using libvirt, volumes (and later snapshots) have to be stored.
The directory defaults to <code>/opt/vm_images</code> but can be overridden
using the <code>-e|--extras-params</code> option, setting
<code>libvirt_volume_path</code> to another location. This is useful because
in a default Fedora installation, the root partition is not large enough
to support the volumes.</p>
<p>When using libvirt, the default DNS server added to the VMs provides
insufficient access in some cases. As such, a second DNS server,
can be added by defining the <code>custom_nameserver</code> setting
in the <code>-e|--extras-params</code> option.
This nameserver is added to <code>/etc/resolv.conf</code>
files on the VMs.</p>
<h2>Executing toci_gate_test-oooq.sh</h2>
<p>When the script completes, you will see a list of instructions printed out on how
to run <b>toci_gate_test.sh</b> from the undercloud:</p>
<li><code>ssh to the undercloud: $ ssh zuul@$ansible_host</code></li>
<li><code>Source the environment settings file: $ source /home/zuul/env_vars_to_src.sh</code></li>
<li><code>Run the toci gate script: $ /opt/stack/tripleo-ci/toci_gate_test.sh</code></li>
<p> If you pass the <code>-a</code> options the above steps will be executed
<h2>Input argument options in the reproducer-quickstart.sh script</h2>
<p>Running <code>reproducer-quickstart.sh --help</code> will show a list of the
input options. All the options have a default and none are required.
The options are listed below with explanations:</p>
<li><code>-w, --workspace</code>: directory where the virtualenv, inventory files, etc.
Defaults to creating a directory in /tmp</li>
<li><code>-v, --create-virtualenv</code>: create a virtualenv to install Ansible and dependencies.
Defaults to true.</li>
<li><code>-r, --remove-stacks-keypairs</code>: delete all stacks in the tenant before deployment.
will also delete associated keypairs if they exist.
Defaults to false.</li>
<li><code>-p, --nodestack-prefix</code>: add a unique prefix for multinode and singlenode stacks
Defaults to empty.</li>
<li><code>-a, --autorun</code>: run toci gate script on prepared environment automatically
Default is to stop after the environment is set up.</li>
<li><code>-t, --timeout</code>: set the timeout in minutes for the deployment.
Defaults to 240 minutes.</li>
<li><code>-l, --libvirt</code>:runs a 2-node multinode job or singlenode job on a
single virthost using libvirt to create the nodes.
Defaults to false.</li>
<li><code>-e, --extra-params</code>: File(s) and/or parameters used to override
playbook settings.</li>
Defaults to /opt/vm_images.</li>
<li><code>-n, --nodes-file</code>: node config file of the topology needed.
Defaults to $NODES_FILE (set in the job).</li>
<li><code>-z, --zuul-changes</code>: refspecs with changes to test.
Defaults to $ZUUL_CHANGES (set in the job).</li>
<li><code>-j, --toci-jobtype</code>: TOCI description of the job to run.
Defaults to $TOCI_JOBTYPE (set in the job).</li>
<li><code>-h, --help</code>:Displays usage text and exits.</li>
<h2>Using an alternative host cloud</h2>
<p>The <b>reproducer-quickstart.sh</b> script is written to run an a personal RDO Cloud tenant.
If you want to run on a different host cloud, modify the <b>reproducer-quickstart.sh</b> as follows:</p>
<li>Add git clone of <code>tripleo-environments</code> or any other repository containing
the cloud details, after cloning <code>tripleo-quickstart-extras</code></li>
<li>Add the repository to quickstart-extras-requirements.txt:
<code>echo "file://$WORKSPACE/tripleo-environments/#egg=tripleo-environments" >>
<li>Use that host cloud's environment file in place of RDO Cloud's environment file.</li>