Current state: in order to load credentials, our shell scripts source a passwords file ($CWD/tripleo-*cloud-passwords by default; if that's not present, $TRIPLEO_ROOT/triple-*cloud-passwords is attempted). This logic is a little confusing, but does allow flexibility: for instance, someone running multiple overclouds from a single undercloud can use different sets of credentials for each overcloud by running the scripts in a different directory for each overcloud (and thus sourcing a different file for each).
Eventually we'd like to have these passwords stored somewhere like Barbican, or in Tuskar, or maybe somewhere in Heat..
In an intermediate timeframe it would be handy if we could integrate them into the testenv.json file, to have one fewer place which stores information about the test environment.
As a first step towards making it possible to update all our scripts to use these other places, it would be handy to have an abstraction layer on top of the passwords. Instead of just referring to `$OVERCLOUD_ADMIN_TOKEN`, a script might have to use `$(retrieve-password OVERCLOUD_ADMIN_TOKEN)`; this (or something like it) would make it easier for us to change the source of the passwords with minimal code changes.
This bug was reported against an old version of TripleO, and may no longer be valid.
Since it was reported before the start of the liberty cycle (and our oldest stable
branch is stable/liberty), I'm marking this incomplete.
Please reopen this (change the status from incomplete) if the bug is still valid
on a current supported (stable/liberty, stable/mitaka or trunk) version of TripleO,
thanks!