Chapter 2. Overview
This section contains information about installing, configuring, and deploying a simple single-node OpenStack environment. In this scenario, there is no pre-existing Undercloud dependency. Instead, the installer runs an inline heat-all instance to bootstrap the deployment process and convert the selected Heat templates into Ansible playbooks that you can execute on a local machine.
Use the all-in-one OpenStack installation for basic testing and development. The all-in-one installation is a good starting point and test environment for OpenStack, but if you want to perform complex operations, you must deploy a production-level scaled cloud installation.
To install, configure, and deploy a simple single-node OpenStack environment, complete the tasks in the following basic workflow:
- Enable the repositories necessary to deploy the all-in-one OpenStack installation.
- Install the TripleO command line interface (CLI).
- Configure basic network configuration and deployment parameters for your all-in-one OpenStack installation.
- Deploy the all-in-one OpenStack installation.
Benefits of the all-in-one OpenStack installation
- Composable services.
- Pre-defined roles.
- Condensed single-node environment.
- Playbooks that you can use to run the small-footprint installer in a container and generate Ansible playbooks.
The all-in-one Red Hat OpenStack installation does not require configuration pre-deployment or post-deployment. However, this guide also contains information about configuring roles and services that you can use to experiment with OpenStack.
You can create custom composable roles and deploy specific services for each role.
This installation applies Ansible playbooks automatically with the deployment command. However, you can also direct the deployment command to output Ansible playbooks that you can use on other instances. For example, you can complete testing in the all-in-one installation, and then apply the verified Ansible playbook to other instances.