Workbook name: | tripleo.access.v1 |
---|
TripleO administration access workflows
Workflows in the Access Workbook
tripleo.access.v1.create_admin_via_nova
Workflow inputs:
Input tasks: | Required. |
---|---|
Input queue_name: | |
Default: tripleo | |
Input ssh_servers: | |
Default: [] | |
Input overcloud_admin: | |
Default: tripleo-admin | |
Input ansible_extra_env_variables: | |
Default: {‘ANSIBLE_HOST_KEY_CHECKING’: ‘False’} |
tripleo.access.v1.create_admin_via_ssh
Workflow inputs:
Input tasks: | Required. |
---|---|
Input ssh_private_key: | |
Required. | |
Input ssh_user: | Required. |
Input ssh_servers: | |
Required. | |
Input ansible_extra_env_variables: | |
Default: {‘ANSIBLE_HOST_KEY_CHECKING’: ‘False’} |
tripleo.access.v1.enable_ssh_admin
This workflow creates an admin user on the overcloud nodes, which can then be used for connecting for automated administrative or deployment tasks, e.g. via Ansible. The workflow can be used both for Nova-managed and split-stack deployments, assuming the correct input values are passed in. The workflow defaults to Nova-managed approach, for which no additional parameters need to be supplied. In case of split-stack, temporary ssh connection details (user, key, list of servers) need to be provided – these are only used temporarily to create the actual ssh admin user for use by Mistral.
Workflow inputs:
Input ssh_private_key: | |
---|---|
Default: None | |
Input ssh_user: | Default: None |
Input ssh_servers: | |
Default: [] | |
Input overcloud_admin: | |
Default: tripleo-admin | |
Input queue_name: | |
Default: tripleo | |
Input plan_name: | |
Default: overcloud |
Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.