openstack
/
tripleo-quickstart-extras
Code Issues Proposed changes
tripleo-quickstart-extras/roles/standalone
History
Cédric Jeanneret df2f5f4f5c Allow console stream for standalone 
While the console is working, it's relying on the "established" state -
if, for any reason, the stream dies, it won't be able to restart
properly.

We already address this case for Undercloud and Overcloud in another
patch:
https://review.opendev.org/c/openstack/tripleo-quickstart-extras/+/857096

The standalone case was overlooked, since it was working just fine.

Change-Id: Idcaaed92e6cc6e5554f1c22d129d962e8daa7272
 		2022-09-23 08:12:44 +02:00
..
defaults Fixing condition for ceph custom parameters updates 2022-07-19 09:30:02 -03:00
meta Adopt yamllint strict linting 2018-11-26 12:37:21 +00:00
tasks Fix resolution of tripleo_ceph_deploy_container_namespace 2022-09-12 20:52:45 +05:30
templates Allow console stream for standalone 2022-09-23 08:12:44 +02:00
README.md Standalone configure neutron bridge correctly 2020-10-19 12:13:03 +00:00

README.md

Standalone

An Ansible role to deploy the Standalone ( all-in-one ) deployment of TripleO

Requirements

This role expects the requirements for deploying a TripleO undercloud to be met. For example python-tripleoclient is installed and hardware requirements met.

Role Variables

  • standalone_config: <'standalone_config.yaml.j2'> -- jinja template of the deployment configuration

  • standalone_network: <'192.168.24'> -- First three octets of the network used

  • standalone_network_prefix: <'24'> -- The subnet size for the standalone deployment network

  • standalone_ip: <'192.168.24.1'> -- The IP address of the standalone deployment

  • standalone_interface: <'br-ex'> -- The interface for the standalone deployment

  • standalone_neutron_bridge_mapping: <'datacentre:br-ctlplane,tenant:br-tenant'> -- The mapping for neutron network bridges

  • standalone_neutron_physical_bridge: <'br-ctlplane'> -- Neutron physical bridge

  • standalone_hostname: <'standalone.localdomain'> -- FQDN to use for the system being deployed. Must be a fully qualified hostname with the domain.

  • standalone_container_prep_options: <''> -- additional parameters for the container prep command

  • standalone_container_prep_script: <'standalone-container-prep.sh.j2'> -- The script name use to perform container prep actions

  • standalone_container_prep_log: <'standalone_container_prep.log'> -- The log of the container prepa ctions

  • standalone_container_prep_updates: <'true'> -- Adds needed parameters to containers-prepare-parameters.yaml so that new container images and packages will be retrieved

  • standalone_deploy_log: <'standalone_deploy.log'> -- The log of the deployment

  • standalone_ansible_lint_log: <'standalone_ansible_lint.log'> -- The ansible lint output

  • standalone_role: <'Standalone.yaml'> -- The TripleO Heat Template role definition of the deployment

  • standalone_libvirt_type: <'kvm'> -- The type of libvirt to run on the standalone (qemu|kvm)

  • standalone_selinux_mode: <'permissive'> -- The selinux mode to use.

  • standalone_ansible_lint: <'false'> -- Perform ansible lint on the generated ansible playbooks

  • standalone_custom_env_files: <'[]'> -- list of additional environment files to be added to the deployment command (do not include the -e)

  • standalone_tripleo_deploy_debug_arg: -- makes tripleoclient invoked with --debug, that results in calling ansible -vv commands as well.

Dependencies

The dependencies documented for TripleO Quickstart and TripleO