Paul, Usually Juju goes by the OS_TENANT_NAME, and the OS_TENANT_ID is never needed (correct if I am wrong ...)
Since the TENANT_ID is only required for generating tempurls (gatekeeper) in HPCloud, I decided to prefix it with HP_ and keep this set of variables more controlled. It turns out that it is also causing trouble in staging/production because it was poorly designed on my side. Thus, I am proposing a change to only require HP_* variables if the deployment is targeted to HP (based on the AUTH_URL), on canonistack the variables will automatically be set as empty. Apologies for the unnecessary pain I caused during the last days. [] On Tue, May 6, 2014 at 12:45 AM, Paul Larson <[email protected]> wrote: > On Mon, May 5, 2014 at 10:11 AM, Celso Providelo > <[email protected]> wrote: >> Hi guys, >> >> As part of the Gatekeeper (Swift TempUrl manager) landing and >> deployment integration, there is a requirement for setting up new >> environment variables for unit_config. >> >> Here is a quick setup guide: >> >> HP_ACCESS_KEY_ID: >> >> Available in horizon UI under *[email protected]* (your account) -> >> Manage Access Keys >> >> HP_SECRET_KEY: >> >> Idem but click "Show Secret Keys" >> >> HP_TENANT_ID: >> >> <14-digits sequence> referring to your project in HP (tenant_name) > This seems to be the same as the existing OS_TENANT_ID I had specified > for my hpcloud setup. Is it not? > > -Paul Larson -- Celso Providelo [email protected] -- Mailing list: https://launchpad.net/~canonical-ci-engineering Post to : [email protected] Unsubscribe : https://launchpad.net/~canonical-ci-engineering More help : https://help.launchpad.net/ListHelp
