Exosphere

Overview While spelunking the code for another reason, I found some dead code from Jetstream1, we aren't using it, this MR removes it. How to Test N/A, dead code removal Screenshots No visual changes.

Overview When a user logs into a project, and selects multiple regions, Exosphere creates an application credential for each region. (I believe this isn't strictly necessary in Keystone -- a single application credential can authenticate a project ... [More] in multiple regions -- but Exosphere is currently architected to use a separate app credential per region.) Sometimes, this results in an error because Exosphere creates multiple application credentials with the exact same name. In Keystone, application credential names must be unique. (The name includes a timestamp with milliseconds, but Exosphere is fast here.) This MR includes the OpenStack region ID in the name of the application credential, which resolves the conflict. Fixes #742 How to Test Log into a project, select multiple regions, confirm you do not get the error described in #742. Screenshots N/A, just lack of error. [Less]

Thanks @cmart. ♻ 👋 And so long Jetstream1! You served us well.

Thanks @cmart for smoothing this rough edge! 🙇

@aszenz is this ready to review?

Julian Pistorius (4206379a) at 24 Feb 16:20 Merge branch 'remove-dead-jetstream1-code' into 'master' ... and 1 more commit

Overview While spelunking the code for another reason, I found some dead code from Jetstream1, we aren't using it, this MR removes it. How to Test N/A, dead code removal Screenshots No visual changes.

Julian Pistorius (6d6cb1dc) at 24 Feb 16:21 Merge branch 'issue-742' into 'master' ... and 1 more commit

Overview When a user logs into a project, and selects multiple regions, Exosphere creates an application credential for each region. (I believe this isn't strictly necessary in Keystone -- a single application credential can authenticate a project ... [More] in multiple regions -- but Exosphere is currently architected to use a separate app credential per region.) Sometimes, this results in an error because Exosphere creates multiple application credentials with the exact same name. In Keystone, application credential names must be unique. (The name includes a timestamp with milliseconds, but Exosphere is fast here.) This MR includes the OpenStack region ID in the name of the application credential, which resolves the conflict. Fixes #742 How to Test Log into a project, select multiple regions, confirm you do not get the error described in #742. Screenshots N/A, just lack of error. [Less]