Jump to: navigation, search

Difference between revisions of "Identity topology canvas"

(SVG based canvas)
(Identity Topology UX Design)
Line 12: Line 12:
 
==== SVG based canvas ====
 
==== SVG based canvas ====
 
[[file: Identity-topology.png]]
 
[[file: Identity-topology.png]]
figure 2
+
==== Bootstrap based canvas ====
figure 3
+
[[file: Identity-topology-Bootstrap-Version-pure-bootstrap-mouse-hover-new.png]]
 +
==== Forced Graph based canvas ====
 +
[[file: network-topology-simple-real-case.png]]
  
 
The following table shows advantages and disadvantages of each types of canvas types:
 
The following table shows advantages and disadvantages of each types of canvas types:

Revision as of 19:23, 3 November 2015

Identity Topology Idea

Providing a topological view of identity entities (domains, projects, groups, users and roles) aims openstack users to have a bird-eye-view of how identity is structured in their cloud. With Domains, Projects, Users, Groups and Roles, understanding the organization and relationship of these ideas can be difficult. So, to easily disposed of any complexity out of identity service, we should create a more graphic depiction of these relationships in a topological view something strongly like currently implemented network-topology canvas.

Identity Topology UX Design

At openstack invision identity topology project , several different types of topology wireframes has been drawn:

  • SVG based canvas (This layout has been deprecated from horizon)
  • Bootstrap based canvas
  • Network topology based canvas (Forced graph)

The following three consecutive figures show these three types of different identity topology drawings:

SVG based canvas

Identity-topology.png

Bootstrap based canvas

Identity-topology-Bootstrap-Version-pure-bootstrap-mouse-hover-new.png

Forced Graph based canvas

Network-topology-simple-real-case.png

The following table shows advantages and disadvantages of each types of canvas types:

Development