9da99e1f7c3de3c28011ef39966894a2735bee20
Andrew Bonney
9da99e1f7c
Use nova_management_address as a default VNC bind address
Our installation uses separate networks for deployment and OpenStack management. The current default of 'ansible_host' for the VNC server results in it binding to our deployment network. Whilst this could be resolved via variable overrides, the majority of the defaults and templated options in this role use the Nova management address as the default choice for binding to. This patch changes the default VNC bind address to match the existing standard pattern, which should avoid the need for overrides in most cases. As a result, for our setup, when nova_management_address is identified and set in the OSA nova playbooks to match the OpenStack management network, the VNC server bind address gets set to the correct address. Change-Id: I9c5e2584f8f1d9bd76120b8b236e25f63804473a
Team and repository tags
OpenStack-Ansible nova
Ansible role that installs and configures OpenStack nova and all of its corresponding services.
- This role will install the following:
-
- nova-api
- nova-conductor
- nova-scheduler
- nova-console
- nova-compute
Documentation for the project can be found at: https://docs.openstack.org/openstack-ansible-os_nova/latest/
Release notes for the project can be found at: https://docs.openstack.org/releasenotes/openstack-ansible-os_nova/
The project source code repository is located at: https://opendev.org/openstack/openstack-ansible-os_nova/
The project home is at: https://launchpad.net/openstack-ansible
The project bug tracker is located at: https://bugs.launchpad.net/openstack-ansible
Description
Languages
Jinja
66.8%
Python
30.8%
Shell
2.4%