simplify process for associating newly created network to domain

Bug #1340873 reported by Cindy Lu on 2014-07-11
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Dashboard (Horizon)
Undecided
Unassigned

Bug Description

Prereq: identity v3 support.

Scenario: Creating a network and associating it to a project within a domain.

Issues :

1) In the Create Network panel, the user is unable to identify which project to select based on a domain - because in the project listing choice, he/she is given a list of projects across *all* domains ... but with no indication regarding the domain to which the project belongs

2) the above issue makes it quite impossible for the admin to find the appropriate project and the only evident workaround is to go back to all the projects in the environment and change their names to assign them a name where the domain can be understood

3) Even setting the domain context in the Horizon UI does not improve the situation...still the entire list of projects shows up....

4) At this point the other workaround is to logout and log back in to the specific domain - and then do the above action from the Projects->Network entry point...

Liz Blanchard (lblanchard) wrote :

Would it be helpful to add a "Domain" selection that filters down the list of Projects that the user can choose from?

Justin Pomeroy (jpomero) on 2014-08-01
Changed in horizon:
assignee: nobody → Justin Pomeroy (jpomero)

Fix proposed to branch: master
Review: https://review.openstack.org/111390

Changed in horizon:
status: New → In Progress

Change abandoned by David Lyle (<email address hidden>) on branch: master
Review: https://review.openstack.org/111390
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results.

Justin Pomeroy (jpomero) on 2015-06-03
Changed in horizon:
assignee: Justin Pomeroy (jpomero) → nobody
Akihiro Motoki (amotoki) wrote :

This is the same problem as bug 1600383. bug 1600383 has the active assignee, so I would like to keep bug 1600383 open and mark this as duplicated.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers