77c82f6645
The subnet property is added to puppet/role.role.j2.yaml as
`{{role}}ControlPlaneSubnet`. Roles with a different subnet specified
can be used to deploy a routed network architecture by using one
role per routed network.
When enabling the neutron segments plug-in to support routed-networks
the neutron IPAM code will defer ipallocation unless the port create
request contain enough details. (Ref: LP Bug: #1695740) By adding the
subnet to port create request this change enables tripleo deployment
on an undercloud with Neutron segments plug-in and routed networks.
This depends on a Heat change that improves network logic in server
resource to not replace the current port if new props match what is
on the current interface. Without this adding the subnet property on
update/upgrades would cause a port replacement, which in turn would
cause IPAM info in undercloud neutron to miss-match the deployed
overcloud nodes.
Depends-On: Iab75ec49b962617943017dcaf1b04b89f91a982e
Change-Id: I33804bfd105a13c25d6057e8414e09957939e8af
Implements: blueprint tripleo-routed-networks-deployment
Team and repository tags
tripleo-heat-templates
Heat templates to deploy OpenStack using OpenStack.
- Free software: Apache License (2.0)
- Documentation: https://docs.openstack.org/tripleo-docs/latest/
- Source: http://git.openstack.org/cgit/openstack/tripleo-heat-templates
- Bugs: https://bugs.launchpad.net/tripleo
Features
The ability to deploy a multi-node, role based OpenStack deployment using OpenStack Heat. Notable features include:
- Choice of deployment/configuration tooling: puppet, (soon) docker
- Role based deployment: roles for the controller, compute, ceph, swift, and cinder storage
- physical network configuration: support for isolated networks, bonding, and standard ctlplane networking
Directories
A description of the directory layout in TripleO Heat Templates.
- environments: contains heat environment files that can be used with -e
on the command like to enable features, etc.
- extraconfig: templates used to enable 'extra' functionality. Includes
functionality for distro specific registration and upgrades.
- firstboot: example first_boot scripts that can be used when initially
creating instances.
- network: heat templates to help create isolated networks and ports
- puppet: templates mostly driven by configuration with puppet. To use these
templates you can use the overcloud-resource-registry-puppet.yaml.
- validation-scripts: validation scripts useful to all deployment
configurations
- roles: example roles that can be used with the tripleoclient to generate
a roles_data.yaml for a deployment See the roles/README.rst for additional details.
Service testing matrix
The configuration for the CI scenarios will be defined in tripleo-heat-templates/ci/ and should be executed according to the following table:
| - | scn001 | scn002 | scn003 | scn004 | scn006 | scn007 | scn009 | non-ha | ovh-ha |
|---|---|---|---|---|---|---|---|---|---|
| openshift |
|
||||||||
| keystone |
|
|
|
|
|
|
|
|
|
| glance |
|
swift |
|
|
|
|
|
|
|
| cinder |
|
iscsi | |||||||
| heat |
|
|
|||||||
| ironic |
|
||||||||
| mysql |
|
|
|
|
|
|
|
|
|
| neutron |
|
|
|
|
|
|
|
|
|
| neutron-bgpvpn |
|
||||||||
| ovn |
|
||||||||
| neutron-l2gw |
|
||||||||
| rabbitmq |
|
|
|
|
|
|
|
|
|
| mongodb | |||||||||
| redis |
|
|
|||||||
| haproxy |
|
|
|
|
|
|
|
|
|
| memcached |
|
|
|
|
|
|
|
|
|
| pacemaker |
|
|
|
|
|
|
|
|
|
| nova |
|
|
|
|
ironic |
|
|
|
|
| ntp |
|
|
|
|
|
|
|
|
|
| snmp |
|
|
|
|
|
|
|
|
|
| timezone |
|
|
|
|
|
|
|
|
|
| sahara |
|
||||||||
| mistral |
|
||||||||
| swift |
|
||||||||
| aodh |
|
|
|||||||
| ceilometer |
|
|
|||||||
| gnocchi |
|
|
|||||||
| panko |
|
|
|||||||
| barbican |
|
||||||||
| zaqar |
|
||||||||
| ec2api |
|
||||||||
| cephrgw |
|
||||||||
| tacker |
|
||||||||
| congress |
|
||||||||
| cephmds |
|
||||||||
| manila |
|
||||||||
| collectd |
|
||||||||
| fluentd |
|
||||||||
| sensu-client |
|