tripleo-image-elements/elements/tuskar
Ghe Rivero 7d37fb5eb2 Rename os-config-applier to os-apply-config
There are some elements that are still using the old os-config-applier
to store the configuration templates.

Change-Id: I17def1e5e0ca09d5f400d7ba1f7bd82ea804ab42
2014-07-09 06:00:27 +00:00
..
environment.d Wire in _EXTRA_INSTALL_OPTS... 2014-04-19 08:08:45 -04:00
install.d Wire in _EXTRA_INSTALL_OPTS... 2014-04-19 08:08:45 -04:00
os-apply-config/etc/tuskar Rename os-config-applier to os-apply-config 2014-07-09 06:00:27 +00:00
os-refresh-config/post-configure.d Ceilo/Ironic/Tuskar: don't hard code venv dir 2014-03-13 20:19:40 -04:00
README.md Make tuskar element supply tripleo-heat-templates 2013-10-17 15:23:57 +03:00
element-deps sort the element-deps to please dib-lint 2014-04-24 15:38:03 +02:00
source-repository-tuskar Don't use /cgit/ urls for git. 2014-02-21 15:25:12 +13:00

README.md

Install tuskar service from git.

Configuration

Tuskar API requires the following keys to be set via Heat Metadata.

tuskar: overcloud-admin-password: - the password of the overcloud admin user. Use OvercloudAdminPassword template parameter to override this option. db: "mysql://tuskar:unset@localhost/tuskar?charset=utf8" - the connection string for a DB to be used by tuskar-api. username: - the name of the user to deploy the overcloud on behalf of password: - the password of the user to deploy the overcloud on behalf of tenant_name: - the tenant name of the user to deploy the overcloud on behalf of

Tuskar API uses Heat templates provided by tripleo-heat-templates project. One can set the following environment variables to customize how templates are obtained:

- *DIB_REPOTYPE_tuskar-templates* type of repo (git, tar)
  Defaults to: git
- *DIB_REPOLOCATION_tuskar-templates* repo location (uri)
  Defaults to: git://git.openstack.org/openstack/tripleo-heat-templates
- *DIB_REPOREF_tuskar-templates* ref to checkout (for git repos: branch/tag/commit id)
  Defaults to: master