openstack/openstack-ansible-os_neutron
Code Issues Proposed changes

Add placement client for neutron

Browse Source 
This is required if segmented provider networks are used in a cloud.
Neutron looks up which compute nodes are associated with each segment
with the placement API.

Change-Id: I7e8c0e3ef7aefd0574aa2a28560653005f2640d6
Related-Bug: 1818943
This commit is contained in:
Jonathan Rosser 2019-07-01 17:12:30 +01:00
parent 712ad0567b
commit 2cafbd1ae3
1 changed files with 12 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
templates/neutron.conf.j2
View File

@ -124,6 +124,18 @@ ipv4_ptr_zone_prefix_size = {{ neutron_ipv4_ptr_zone_prefix_size }}
ipv6_ptr_zone_prefix_size = {{ neutron_ipv6_ptr_zone_prefix_size }}
{% endif %}
[placement]
auth_type = password
username = {{ neutron_service_user_name }}
password = {{ neutron_service_password }}
project_name = {{ neutron_service_project_name }}
user_domain_id = {{ neutron_service_user_domain_id }}
project_domain_id = {{ neutron_service_project_domain_id }}
region_name = {{ neutron_service_region }}
auth_url = {{ keystone_service_adminurl }}
insecure = {{ keystone_service_adminuri_insecure | bool }}
endpoint_type = internal
[nova]
auth_type = password
username = {{ neutron_service_user_name }}