Cannot figure out to provision my overcloud from myconfigfile.yml given the present documentation

[Henrik Bach]

Hi,

I cannot figure out how to provision my overcloud from myconfigfile.yml given the present documentation from: http://docs.openstack.org/developer/tripleo-quickstart/configuration.html

To be more specific:

1) From which machine do I issue: ansible-playbook playbook.yml -e @myconfigfile.yml

and

2) which playbook.yml should I use?

The myconfigfile.yml is the same as given in your example.

/Henrik

[wes hayutin (weshayutin)]

Try using the default configuration files first in config/general_config/minimal.yml and config/general_config/ha.yml

[Henrik Bach (henrik-bach)]

Ok.

But, which playbook.yml should I use together with the default configuration files?

ansible-playbook playbook.yml -e @config/.../ha.yml

Thank you.

/Henrik

[John Trowbridge (trown)]

This is a docs bug, we should fix up the docs to show using quickstart.sh with custom configs.

[wes hayutin (weshayutin)]

need to expand on https://review.openstack.org/#/c/423385/1/roles/collect-logs/docs/static/env-setup-virt.rst

[John Trowbridge (trown)]

Moved from tripleo-quickstart launchpad (Moving bug trackers in progress).

[Emilien Macchi (emilienm)]

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (FUTURE, PIKE, QUEENS, ROCKY, STEIN).
  Valid example: CONFIRMED FOR: FUTURE