openstack
/
tripleo-heat-templates
Code Issues Proposed changes
tripleo-heat-templates/deployment
History
Harald Jensås 8665a0d97b Make NetCidrMapValue contain list of cidrs in each net 
Prior to routed networks we only had one subnet per network.
With routed networks each network can have multiple subnets.
The NetCidrMapValue should contain a list storing the cidr
of each subnet for each network.

Ceph:
  list_join is used to make a comma separated list of
  cidrs for public_network, monitor_address_block,
  cluster_network and radosgw_address_block.

Partial: blueprint tripleo-routed-networks-templates
Depends-On: Ia8e219b30d4f8b199b882e95fe2834252a92c15a
Depends-On: I1ace0a02e6aa2610559fee0d8576e6f1bc98d699
Change-Id: I68e064d23ec5d43f59146d974cae604d2c5fdb52
 		2019-01-06 18:20:27 +01:00
..
aodh Merge "Fix service naming conventions" 2018-12-15 02:43:28 +00:00
glance The monitoring_subscription was lost in translation 2018-12-21 23:42:51 +00:00
ironic Flatten Ironic services configuration 2018-12-14 07:25:13 +01:00
keepalived Flatten Keepalived service configuration 2018-12-13 10:26:26 -05:00
memcached Make NetCidrMapValue contain list of cidrs in each net 2019-01-06 18:20:27 +01:00
podman Move podman into deployment directory 2018-12-17 11:37:19 +00:00
snmp Make NetCidrMapValue contain list of cidrs in each net 2019-01-06 18:20:27 +01:00
timesync Fix service naming conventions 2018-12-13 08:12:36 -07:00
tripleo-firewall flatten tripleo-firewall service configuration 2018-12-14 13:16:34 -05:00
tuned flatten tuned service configuration 2018-12-14 13:13:40 -05:00
zaqar Flatten Zaqar service configuration 2018-12-14 07:45:24 +01:00
README.rst Add deployments/README.rst 2018-12-13 10:25:09 -05:00

README.rst

TripleO Deployments

This directory contains files that represent individual service deployments, orchestration tools, and the configuration tools used to deploy them.

Directory Structure

Each logical grouping of services will have a directory. Example: 'timesync'. Within this directory related timesync services would exist to for example configure timesync services on baremetal or via containers.

Filenaming conventions

As a convention each deployments service filename will reflect both the deployment engine (baremetal, or containers) along with the config tool used to deploy that service.

The convention is <service-name>-<engine>-<config management tool>.

Examples:

deployment/aodh/aodh-api-container-puppet.yaml (containerized Aodh service configured with Puppet)

deployment/aodh/aodh-api-container-ansible.yaml (containerized Aodh service configured with Ansible)

deployment/timesync/chrony-baremetal-ansible.yaml (baremetal Chrony service configured with Ansible)

deployment/timesync/chrony-baremetal-puppet.yaml (baremetal Chrony service configured with Puppet)