Allow to specify a custom AUTH_URL for the templates in case instances cannot reach internalURL which is the case in mose deployment. A new variable in trust section: trustee_keystone_interface which default to public is introduced. Change-Id: I2a908c0752387e4ff4ad2b0fdf0c1025a73ce806 Closes-Bug: #1643197
2.9 KiB
- Edit the
/etc/magnum/magnum.conf
file:In the
[api]
section, configure the host:[api] ... host = CONTROLLER_IP
Replace
CONTROLLER_IP
with the IP address on which you wish magnum api should listen.In the
[certificates]
section, selectbarbican
(orx509keypair
if you don't have barbican installed):Use barbican to store certificates:
[certificates] ... cert_manager_type = barbican
Important
Barbican is recommended for production environments.
To store x509 certificates in magnum's database:
[certificates] ... cert_manager_type = x509keypair
In the
[cinder_client]
section, configure the region name:[cinder_client] ... region_name = RegionOne
In the
[database]
section, configure database access:[database] ... connection = mysql+pymysql://magnum:MAGNUM_DBPASS@controller/magnum
Replace
MAGNUM_DBPASS
with the password you chose for the magnum database.In the
[keystone_authtoken]
and[trust]
sections, configure Identity service access:[keystone_authtoken] ... memcached_servers = controller:11211 auth_version = v3 auth_uri = http://controller:5000/v3 project_domain_id = default project_name = service user_domain_id = default password = MAGNUM_PASS username = magnum auth_url = http://controller:35357 auth_type = password [trust] ... trustee_domain_name = magnum trustee_domain_admin_name = magnum_domain_admin trustee_domain_admin_password = DOMAIN_ADMIN_PASS trustee_keystone_interface = KEYSTONE_INTERFACE
Replace MAGNUM_PASS with the password you chose for the magnum user in the Identity service and DOMAIN_ADMIN_PASS with the password you chose for the
magnum_domain_admin
user.Replace KEYSTONE_INTERFACE with either
public
orinternal
depending on your network configuration. If your instances cannot reach internal keystone endpoint which is often the case in production environments it should be set topublic
. Default topublic
In the
[oslo_messaging_notifications]
section, configure thedriver
:[oslo_messaging_notifications] ... driver = messaging
In the
[DEFAULT]
section, configureRabbitMQ
message queue access:[DEFAULT] ... transport_url = rabbit://openstack:RABBIT_PASS@controller
Replace
RABBIT_PASS
with the password you chose for theopenstack
account inRabbitMQ
.