Bug 1360495

Summary: UI for defining OpenStack regions
Product: [Retired] Beaker Reporter: matt jia <mjia>
Component: openstackAssignee: beaker-dev-list
Status: CLOSED EOL QA Contact: tools-bugs <tools-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: developCC: mastyk, mjia
Target Milestone: ---Keywords: FutureFeature, Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-07 15:40:16 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description matt jia 2016-07-26 23:21:19 UTC
Right now, adding a new OpenStack region requires a manually step to insert a row into the db. We need to have a UI for it.

Comment 1 Dan Callaghan 2016-07-27 07:13:17 UTC

*** This bug has been marked as a duplicate of bug 1100519 ***

Comment 2 Dan Callaghan 2016-07-27 07:13:49 UTC
We do need to build a UI, but it shouldn't accept usernames and passwords, it should use the OpenStack token delegation stuff (like Heat does).

Comment 3 Dan Callaghan 2016-07-27 07:14:41 UTC
Oops, sorry... wrong bug!

Comment 4 Dan Callaghan 2017-07-24 07:04:40 UTC
We should probably design the UI having multiple regions in mind (bug 1360498) although *right now* the scheduler assumes there is only one region defined at any time.

Comment 5 Roman Joost 2018-05-25 03:58:52 UTC
This seems to be not a requirement, because multiple OpenStack regions have not been deployed so far. If it comes up again, we'll either reopen or create a new bug.

Comment 6 Roman Joost 2018-05-25 04:06:10 UTC
I think I was too quick with this one. Dan reminded me that not having a UI would lower the usefulness of our integration, so having a UI for it would be beneficial.