The process for an AIO installation of openstack-ansible involves a bash script
to do the initial bootstrapping of the AIO host. This script works well, but it
becomes difficult to update over time and a conversion to Ansible would make
future updates, such as multi-platform-host blueprint, a little easier.

The openstack-ansible playbooks themselves shouldn’t change as a result of this
update. The AIO bootstrap is a prerequisite step in the deployment right now
and that won’t change after the AIO Ansible playbook is available for use.

If deployers are doing greenfield AIO deployments, they will need to follow new
steps and ensure they bootstrap Ansible prior to running the new AIO Ansible
playbook. Documentation for AIO builds will require updates.

If deployers are doing deployments to multiple servers (non-AIO), their steps
for deploying openstack-ansible will not change.

These changes will impact gating since the gating jobs run an AIO build.
However, if the bootstrap-aio.sh script is changed to call the AIO bootstrap
Ansible playbook, the gating job itself will not need to be changed.

No additional resources should be required during gating to run the Ansible AIO
playbook.

The documentation for AIO deployments would need to be updated with the new
steps for bootstrapping an AIO build. The changes in the steps are in the
Proposed Changes section at the top of this spec.

Also, deployers would need to note which environment variables and/or Ansible
variables to set to control various parts of the deployment, such as whether or
not to deploy certain OpenStack services in their environment.