Go to file
Steven Hardy e6273f9376 Update yaml-validate.py to accept files or directories
For developer usage it's helpful to have the choice to provide either
an individual files, list of files, or some mix of files and directories
as you don't necessarily want to walk everything all the time.

Change-Id: I050de123bba51402a0dbb42d71e97fd27d7ce4bc
2016-01-28 19:04:25 +00:00
2015-11-24 19:20:35 +05:30
2016-01-12 17:31:04 +00:00
2013-10-22 17:49:35 +01:00
2015-12-15 10:48:30 -05:00
2015-11-05 15:44:18 +01:00
2014-01-20 11:58:20 +01:00
2013-10-22 17:49:35 +01:00
2013-10-22 17:49:35 +01:00
2013-10-22 17:49:35 +01:00
2016-01-20 15:33:23 -06:00

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

Description
RETIRED, Heat templates for deploying OpenStack
Readme 322 MiB