RETIRED, Heat templates for deploying OpenStack
2d60799c49
CinderVolumeEdge is an optional service (defaults to OS::Heat::None)
that can be enabled on DCN/Edge nodes for edge sites that support
persistent block storage (i.e. cinder). The dcn-hci.yaml environment
file enables the service.
The new service supports the following edge deployment models:
1. Edge site with no block storage
- Deploy DistributedCompute nodes
- Use dcn.yaml environment file (the CinderVolumeEdge service
remains disabled)
2. Edge site with traditional HCI storage
- Deploy DistributedComputeHCI nodes
- Use dcn-hci.yaml env file to enable the CinderVolumeEdge service
- Use ceph-ansible.yaml env file to deploy ceph for the RBD backend
3. Edge site with quasi-hyperconverged storage
- Deploy DistributedCompute nodes
- Use dcn-hci.yaml env file to enable the CinderVolumeEdge service
- Use ceph-ansible-external.yaml env file so the RBD backend can
access an external ceph cluster
This patch adds support for number 3, which is a new capability. Whereas
traditional HCI means ceph and cinder services run on compute nodes, the
new model is still quasi-hyperconverged because cinder (as well as
glance) runs on the compute nodes.
Change-Id: I56b5792c1d53bb8659e440f598006e471894ff2e
|
||
|---|---|---|
| ci | ||
| common | ||
| container_config_scripts | ||
| deployed-server | ||
| deployment | ||
| environments | ||
| extraconfig | ||
| firstboot | ||
| network | ||
| plan-samples | ||
| puppet | ||
| releasenotes | ||
| roles | ||
| sample-env-generator | ||
| scripts | ||
| tools | ||
| tripleo_heat_templates | ||
| zuul.d | ||
| .gitignore | ||
| .gitreview | ||
| .testr.conf | ||
| babel.cfg | ||
| bindep.txt | ||
| config-download-software.yaml | ||
| config-download-structured.yaml | ||
| default_passwords.yaml | ||
| j2_excludes.yaml | ||
| LICENSE | ||
| lower-constraints.txt | ||
| network_data_dashboard.yaml | ||
| network_data_ganesha.yaml | ||
| network_data_routed.yaml | ||
| network_data_subnets_routed.yaml | ||
| network_data_undercloud.yaml | ||
| network_data.yaml | ||
| overcloud-resource-registry-puppet.j2.yaml | ||
| overcloud.j2.yaml | ||
| plan-environment.yaml | ||
| README.rst | ||
| requirements.txt | ||
| roles_data_undercloud.yaml | ||
| roles_data.yaml | ||
| setup.cfg | ||
| setup.py | ||
| test-ansible-requirements.txt | ||
| test-requirements.txt | ||
| tox.ini | ||
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: https://opendev.org/openstack/tripleo-heat-templates
- Bugs: https://bugs.launchpad.net/tripleo
- Release notes: https://docs.openstack.org/releasenotes/tripleo-heat-templates/
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:
| - | scn000 | scn001 | scn002 | scn003 | scn004 | scn006 | scn007 | scn009 | scn010 | scn013 | non-ha | ovh-ha |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| keystone |
|
|
|
|
|
|
|
|
|
|
|
|
| glance |
|
swift |
|
|
|
|
|
|
|
|
||
| cinder |
|
iscsi | ||||||||||
| heat |
|
|
||||||||||
| ironic |
|
|||||||||||
| mysql |
|
|
|
|
|
|
|
|
|
|
|
|
| neutron |
|
|
|
|
|
|
|
|
|
|
||
| neutron-bgpvpn |
|
|||||||||||
| ovn |
|
|||||||||||
| neutron-l2gw |
|
|||||||||||
| om-rpc | rabbit | rabbit |
|
rabbit | rabbit | rabbit | rabbit | rabbit | rabbit | rabbit | ||
| om-notify | rabbit | rabbit | rabbit | rabbit | rabbit | rabbit | rabbit | rabbit | rabbit | rabbit | ||
| redis |
|
|
||||||||||
| haproxy |
|
|
|
|
|
|
|
|
|
|
||
| memcached |
|
|
|
|
|
|
|
|
|
|
||
| pacemaker |
|
|
|
|
|
|
|
|
|
|
||
| nova |
|
|
|
|
ironic |
|
|
|
|
|
||
| placement |
|
|
|
|
|
|
|
|
|
|
||
| ntp |
|
|
|
|
|
|
|
|
|
|
|
|
| snmp |
|
|
|
|
|
|
|
|
|
|
|
|
| timezone |
|
|
|
|
|
|
|
|
|
|
|
|
| mistral |
|
|||||||||||
| swift |
|
|||||||||||
| aodh |
|
|
||||||||||
| ceilometer |
|
|
||||||||||
| gnocchi |
|
|
||||||||||
| barbican |
|
|||||||||||
| zaqar |
|
|||||||||||
| cephrgw |
|
|||||||||||
| cephmds |
|
|||||||||||
| manila |
|
|||||||||||
| collectd |
|
|||||||||||
| designate |
|
|||||||||||
| octavia |
|
|
||||||||||
| rear |
|
|||||||||||
| Extra Firewall |
|