openstack
/
tripleo-heat-templates
Code Issues Proposed changes
RETIRED, Heat templates for deploying OpenStack
1,297 Commits 3 Branches 28 Tags 318 MiB
Go to file
Giulio Fidente b4c4de71fa Add sample environment file to document usage of predictable IPs 
This change adds a sample environment file which documents how to
assign to controllers a predictable IP on each network.

Change-Id: I5be21428c66c82488af8e0240c1614ac3b9b55f0
 		2015-12-15 12:52:15 +01:00
docker Point registry at tripleoupstream 2015-11-20 13:21:39 -05:00
environments Add sample environment file to document usage of predictable IPs 2015-12-15 12:52:15 +01:00
extraconfig Merge "Add pcmk constraints against haproxy-clone only if applicable" 2015-12-03 09:08:19 +00:00
firstboot Update typos 2015-11-24 19:20:35 +05:30
network Allow for usage of pre-allocated IPs for the controller nodes 2015-12-15 12:44:19 +01:00
puppet Allow for usage of pre-allocated IPs for the controller nodes 2015-12-15 12:44:19 +01:00
tools Add YAML sanity check 2015-09-15 15:31:43 -05:00
validation-scripts Add validation to ping the default gateway(s) 2015-10-21 16:47:50 -04:00
.gitignore Rename overcloud-without-mergepy to overcloud. 2015-12-03 16:01:33 -05:00
.gitreview Update stackforge references to openstack 2013-08-17 22:57:57 -04:00
Gemfile Add Puppet 4.x lint checks 2015-11-05 15:44:18 +01:00
LICENSE Add license file 2014-01-20 11:58:20 +01:00
MANIFEST.in Add release configuration. 2013-10-22 17:49:35 +01:00
README.rst Drop os-apply-config. No longer maintained. 2015-12-03 16:01:41 -05:00
Rakefile Make puppet manifests compliant with Puppet 4.x 2015-11-05 15:52:28 +01:00
all-nodes-validation.yaml network validation to ping test each interface 2015-07-24 16:36:57 -04:00
babel.cfg Add release configuration. 2013-10-22 17:49:35 +01:00
bootstrap-config.yaml Remove NO_SIGNAL from ControllerBootstrapNodeDeployment 2015-06-03 16:30:53 +02:00
net-config-bond.yaml Configure ctlplane network with a static IP 2015-09-17 20:39:54 -04:00
net-config-bridge.yaml Configure ctlplane network with a static IP 2015-09-17 20:39:54 -04:00
net-config-linux-bridge.yaml Add simple linux bridge as network environment 2015-11-16 18:34:37 +00:00
net-config-noop.yaml Configure ctlplane network with a static IP 2015-09-17 20:39:54 -04:00
net-config-static-bridge.yaml Add DnsServers param to network config templates 2015-09-30 17:05:37 -04:00
overcloud-resource-registry-puppet.yaml Allow for usage of pre-allocated IPs for the controller nodes 2015-12-15 12:44:19 +01:00
overcloud-without-mergepy.yaml Rename overcloud-without-mergepy to overcloud. 2015-12-03 16:01:33 -05:00
overcloud.yaml Allow for usage of pre-allocated IPs for the controller nodes 2015-12-15 12:44:19 +01:00
requirements.txt Add release configuration. 2013-10-22 17:49:35 +01:00
setup.cfg Drop deprecated templates/Makefile/merge.py 2015-11-25 15:00:13 -05:00
setup.py Add release configuration. 2013-10-22 17:49:35 +01:00
test-requirements.txt Add release configuration. 2013-10-22 17:49:35 +01:00
tox.ini Add YAML sanity check 2015-09-15 15:31:43 -05:00

README.rst

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