Bug 1386302

Summary: [RFE] Discover and display graphically all available nodes in a network or sub-network
Product: Red Hat OpenStack Reporter: Anandeep Pannu <apannu>
Component: openstack-tripleo-uiAssignee: RHOS Maint <rhos-maint>
Status: CLOSED DUPLICATE QA Contact: Ola Pavlenko <opavlenk>
Severity: high Docs Contact:
Priority: high    
Version: 12.0 (Pike)CC: beth.white, jjoyce, jrist, jschluet, sclewis, slinaber, tvignaud
Target Milestone: Upstream M3Keywords: FutureFeature, Triaged
Target Release: 12.0 (Pike)   
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: 2017-05-31 15:12:59 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:
Bug Depends On: 1430485    
Bug Blocks: 1442136    

Description Anandeep Pannu 2016-10-18 15:27:54 UTC 
Description of problem: User Story Epic

As a Cloud Ops administrator I want to provide a few readily accessible pieces of information to the Director UI and have the Director UI return a graphical representation of all the nodes I want ot use with their network interconnectivity so that I can provision the cloud topology I want in an easy to conceptualize manner without having to represent the cloud in hard to use formats.

Tests: 1. (Tentative) Any Red Hat approved reference architecture topology of hardware and networking should be represented correctly
2. (Tentative) The following network topologies should be correctly represented
1. Isolated networks
2. Provider networks

Constraints: 1. Industry standard security practices should be used in accessing nodes and networks
2. Director should provide the underlying capabiity to discover and get the neccessary information from the nodes and the network switches and routers
Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 3 Beth White 2017-05-31 15:12:59 UTC 

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