Your next step is to install the TripleO Undercloud. We will use the same
command used in the provisioning step but we’ll need to indicate to quickstart
to reuse the ansible inventory file and not to teardown any of the nodes we just
provisioned:

This step will run tests to determine the quality of the deployment. The
preferred method to determine the quality is to execute tempest however one can
also deploy a test heat stack on the Overcloud that includes a ping test.

Developers and testers may be interested in only running discrete tasks in an
atomic fashion. Ansible offers an additional powerful way to control the flow
of execution via ansible tags.
A TripleO-Quickstart with TripleO-Quickstart-Extras deployment can be driven
with tags by using the main playbook quickstart-extras.yml, which contains
the four playbooks mentioned above.
The specific tags that help users to control the workflow are:

The two main options here are --retain-inventory which keep all the
previously generated configurations (hosts and ssh files) and
--teardownnone which will preserve any previously created virtual machine.
At this point we will be able to list virtual machines as unprivileged user
stack on the $VIRTHOST::

In which basically we move on with the deployment, launching the libvirt setup
on the remote host that will deploy the undercloud virtual machine and get its
IP address to be able to include it inside the inventory.
At the end of these steps we will have all the virtual machines prepared, with
the undercloud already running::

And in addition the hosts file inside the working directory will be
populated with the new data coming from the newly installed undercloud machine,
making us able to access it like this::

ssh-F/path/to/workdir/ssh.config.ansibleundercloud

At this point we’re able to proceed with the undercloud configuration part,
following the same approach and using the tags that are relevant to this
specific phase. Looking at quickstart-extras-undercloud.yml playbook the
tags for our purpose are undercloud-setup and undercloud-deploy, so
the command line will be::