RETIRED, Heat templates for deploying OpenStack
Go to file
2017-06-26 23:58:58 +00:00
ci Merge "scenario004: containerize services for CI" 2017-06-23 22:28:04 +00:00
common Remove duplicate docker/puppet services.yaml 2017-06-09 17:10:43 +01:00
deployed-server Add DeploymentSwiftDataMap parameter 2017-06-15 14:45:11 -04:00
docker Merge "Make sensu-client log to file" 2017-06-26 13:18:36 +00:00
environments Temporarily disable containerized cinder 2017-06-25 18:54:55 +02:00
extraconfig Merge "Revert "Blacklist support for ExtraConfig"" 2017-06-22 21:22:02 +00:00
firstboot
network Merge "Fix descriptions on bonding templates" 2017-06-26 18:25:35 +00:00
plan-samples Providing parameters specific to a workflow via plan-environment 2017-06-12 11:59:14 +05:30
puppet Merge "Add DeploymentSwiftDataMap parameter" 2017-06-26 23:58:58 +00:00
releasenotes Merge "Add DeploymentSwiftDataMap parameter" 2017-06-26 23:58:58 +00:00
roles Merge "Add an example IronicConductor role" 2017-06-19 15:26:20 +00:00
sample-env-generator Add nested sample environments for inject-trust-anchor 2017-06-12 15:02:50 -05:00
scripts
tools Merge "Support config dir for env generator input files" 2017-06-19 15:26:33 +00:00
tripleo_heat_templates Add nested sample environments for inject-trust-anchor 2017-06-12 15:02:50 -05:00
validation-scripts
.gitignore Sample environment generator 2017-06-12 15:02:50 -05:00
.gitreview
.testr.conf Sample environment generator 2017-06-12 15:02:50 -05:00
all-nodes-validation.yaml
babel.cfg
bindep.txt
bootstrap-config.yaml
capabilities-map.yaml
default_passwords.yaml
hosts-config.yaml
j2_excludes.yaml
LICENSE
MANIFEST.in
net-config-bond.yaml Fix descriptions on bonding templates 2017-06-21 17:09:29 -07:00
net-config-bridge.yaml
net-config-linux-bridge.yaml
net-config-noop.yaml
net-config-static-bridge-with-external-dhcp.yaml
net-config-static-bridge.yaml
net-config-static.yaml
net-config-undercloud.yaml
network_data.yaml
overcloud-resource-registry-puppet.j2.yaml Merge "Remove duplicate docker/puppet services.yaml" 2017-06-17 09:46:33 +00:00
overcloud.j2.yaml Merge "Add os-collect-config data as an output" 2017-06-26 23:58:51 +00:00
plan-environment.yaml
README.rst Standardize example role definitions 2017-06-07 20:20:03 +00:00
requirements.txt
roles_data_undercloud.yaml Merge "Add templates to configure Ironic inspector" 2017-06-16 15:48:15 +00:00
roles_data.yaml Merge "Move iscsid to a container" 2017-06-14 01:00:01 +00:00
services.yaml Remove duplicate docker/puppet services.yaml 2017-06-09 17:10:43 +01:00
setup.cfg
setup.py
test-requirements.txt Updated from global requirements 2017-06-19 05:49:19 +00:00
tox.ini Support config dir for env generator input files 2017-06-12 15:02:50 -05:00

Team and repository tags

image

tripleo-heat-templates

Heat templates to deploy OpenStack using OpenStack.

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:

- scenario001 scenario002 scenario003 scenario004 multinode-nonha
keystone

X

X

X

X

X

glance

rbd

swift

file

swift + rbd

swift

cinder

rbd

iscsi

iscsi

heat

X

X

X

X

X

mysql

X

X

X

X

X

neutron

ovs

ovs

ovs

ovs

X

neutron-bgpvpn

X

neutron-l2gw

X

rabbitmq

X

X

X

X

X

mongodb

X

X

redis

X

haproxy

X

X

X

X

X

keepalived

X

X

X

X

X

memcached

X

X

X

X

X

pacemaker

X

X

X

X

X

nova

qemu

qemu

qemu

qemu

X

ntp

X

X

X

X

X

snmp

X

X

X

X

X

timezone

X

X

X

X

X

sahara

X

mistral

X

swift

X

X

aodh

X

ceilometer

X

gnocchi

X

panko

X

barbican

X

zaqar

X

ec2api

X

cephrgw

X

X

tacker

X

congress

X

cephmds

X

manila

X

collectd

X

fluentd

X

sensu-client

X