Revision as of 18:45, 30 April 2014

Overview

The purpose of this page is to describe a change in architecture to use Heat templates and environments as the data store for Tuskar.

This design assumes the completion of the Juno changes to the TripleO Heat templates to use provider resources.

Format

There are two main types of information that are needed when configuring an overcloud:

• The selection and count of what services will be run in the cloud.
• The configuration for those services.

The Icehouse release for Tuskar uses a database to store both pieces of information. For Juno, the goal is to move that information directly into the Heat templates themselves. This will be accomplished using two recently added features of Heat: provider resources and environments. Provider resources allow for fine-grained stacks to be defined and built up into a larger Heat stack. Environments are a way to capture the selection of which provider resources to use and their configuration values.

Using these features, Tuskar will be able to choose a subset of the TripleO Heat templates to include in the overcloud. Those templates remain static and unedited by Tuskar. Tuskar is then responsible for generating the overall cloud template that includes each of the provider resources and the environment file for saving the configuration.

Provider Resources and Environments

The following series of diagrams shows the relationships between the provider resource templates (labelled as "Static") and the Tuskar-generated files that will use them for configuring a cloud.

Open Questions