Jeff Peeler d4785d9c2c Support non-role resources in resource registry
This change allows for resources utilized in the master seed that are
specified in the resource registry, but are not a provider resource to
be stored and saved to disk. There is no additional information required
to pass as all the data is stored while loading roles.

Previously tuskar always assumed that there was a 1:1 correspondence
between the final resource registry and the number of roles, but this is
no longer the case. The API for /v2/plans/templates has changed to
include non-role resources specified in the resource registry (CLI
operation tuskar plan-templates).

(Also, ignores tags file in git)

Change-Id: Ia15c0fdad0c036564b81f664e49fca280bc7ce7e
2015-03-04 17:54:58 -05:00
2015-02-06 08:04:49 -05:00
2014-08-20 07:58:20 +01:00
2013-05-02 17:32:04 -04:00
2013-05-02 14:55:43 -04:00
2014-10-21 10:29:46 +01:00
2015-01-28 14:53:39 +01:00
2014-09-11 19:46:18 +00:00
2015-01-28 14:53:39 +01:00

Tuskar

What is Tuskar?

Tuskar is a management service for planning TripleO deployments.

Interested in seeing the full Tuskar and Tuskar UI setup? Watch the demo.

For additional information, take a look at the Tuskar documentation.

Installation Information

Please see install.rst for an installation guide.

Building the Docs

From the root directory:

python setup.py build_sphinx

Contributing

Interested in contributing? Take a look at contributing.rst for details on how to do so.

Contact Us

Join us on IRC (Internet Relay Chat):

Network: Freenode (irc.freenode.net/tuskar)
Channel: #tripleo and #tuskar
Description
RETIRED, A service for managing OpenStack deployments
Readme 5.8 MiB