Age | Commit message (Collapse) | Author | Files | Lines | |
---|---|---|---|---|---|
2017-08-16 | Render IP map and host maps according to network_data.yaml | 1 | -2/+2 | ||
This change renders the network IP maps and hostname maps for
all networks defined in network_data.yaml. This should make it
possible to create custom networks that will be rendered for
all applicable roles.
Note that at this time all networks will be rendered whether
they are enabled or not. All networks will be present in all
roles, but ports will be associated with noop.yaml in roles
that do not use the network. This is in accordance with
previous behavior, although we may wish to change this in
the future to limit the size of the role definitions and
reduce the number of placeholder resources in deployments
with many networks.
Note that this patch is a replacement for original patch
https://review.openstack.org/#/c/486280, which I was having
trouble rebasing to current.
Change-Id: I445b008fc1240af57c2b76a5dbb6ccassandra:
authenticator: AllowAllAuthenticator
contrail-analytics:
openstack-origin: cloud:trusty-juno
contrail-configuration:
openstack-origin: cloud:trusty-juno
contrail-control:
openstack-origin: cloud:trusty-juno
glance:
openstack-origin: cloud:trusty-juno
keystone:
admin-password: password
admin-role: admin
openstack-origin: cloud:trusty-juno
mysql:
dataset-size: 15%
neutron-api:
manage-neutron-plugin-legacy-mode: false
openstack-origin: cloud:trusty-juno
nova-cloud-controller:
network-manager: Neutron
openstack-origin: cloud:trusty-juno
nova-compute:
manage-neutron-plugin-legacy-mode: false
openstack-origin: cloud:trusty-juno
openstack-dashboard:
openstack-origin: cloud:trusty-juno
|