openstack/tripleo-heat-templates
Code Issues Proposed changes
b49a96da29
tripleo-heat-templates/README.rst
Dan Prince 84aa3e8c39 Update README.rst 
This commit renames and updates the rather outdated README
for this project.

Change-Id: Ibd1531dc14a2c04d8d91a3339c1df47a41c94790
2015-10-08 14:11:57 -04:00

1.9 KiB
Raw Blame History

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, os-apply-config, and (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.

  • deprecated: contains templates that have been deprecated
  • 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.

  • os-apply-config: templates mostly driven by configuration w/

    os-collect-config and bash based elements (which use the Heat os-apply-config group). These will soon be deprecated and are no longer part of the upstream CI testing efforts.

  • validation-scripts: validation scripts useful to all deployment

    configurations