Figure Tpgy.03 - Topology Example- Data Center and Routers

MODA / Information Framework / Business Entity / Patterns Domain / Topology ABE / Figure Tpgy.03 - Topology Example- Data Center and Routers

Project:

Figure Tpgy.03 - Topology Example- Data Center and Routers : Object diagram

Created:	10/25/2023 10:33:29 AM
Modified:	6/11/2024 9:51:22 AM
Project:
Author:	Kevin Scaggs
Version:	1.0
Advanced:
ID:	{651B9B02-A2CF-448c-87D1-A2D30D8A59E2}

TMF920A Topology Discovery Service and TMF686 Topology API Typical examples considered in the TMF920A Topology Discovery Service (which uses this graph model ) are Routers with Port Cards interconnected by communication link . An interconnected router exemplar within a Data Center is described in TR288 Study of Topology Discovery Service use with Property Graph Databases v1.0.0 | TM Forum, This studies the use of graph based languages - Open Cipher and Gremlin - for queries that traverse such a network graph. (Examples below are in Open Cipher). This study created a graph representation of an actual data center and routers illustrated as Objects in this diagram This shows Data Center(green) and routers (Blue) Interface cards (Mauve) and links (graph edges) between Router Interface Cards. A mapping of these instance to SID Information Framework Concepts is shown in the following table: Exemplar Vertex Information Framework ABE Entity Location Location ABE#gt;#gt; GeographicPlace Data Center Location ABE#gt;#gt; GeographicSite Core Router Physical Resource ABE#gt;#gt; Equipment ABE#gt;#gt; Equipment IP Interface Physical Resource ABE#gt;#gt; Equipment ABE#gt;#gt; NetworkCard DISK Physical Resource ABE#gt;#gt; Equipment ABE#gt;#gt; MemoryCard CPU Physical Resource ABE#gt;#gt; Equipment ABE#gt;#gt; SystemCard VM LogicalResourceABE#gt;#gt;Compute and Software ABE#gt;#gt;Software Resource and Software ABE#gt;#gt; SoftwareResource/ Installed Software NOTE for virtualized Resources these may be modeled as Resource Functions Exemplar Directed Edge Entities Information framework ABEAssociation LOCATION_of Geographic Place ABE GeoSiteRelatedTo CONTAINS Standard UML relation Or Root Business Entities ABE Root#gt;#gt; Entity Group ABE RootEntityGroupComprisedOf Contains Interface Equipment HolderABE HoldsHardware Hosted_ON LogicalResourceABE#gt;#gt;Compute and Software ABE#gt;#gt;Software Resource and Software ABE#gt;#gt; InstallSoftwareRuns or InstalledSoftwareUses LINK Physical Resource ABE PhysicalLink Image 1 Open Cypher creation code //version 2 //Create Vertices CREATE (Paris:Location {name: 'Paris',Region:'Europe'}) CREATE (Paris_DC_1:DataCenter {name:'Paris_DC_1'}) CREATE (Core_Router_1:CoreRouter {vendor:'Vendor1', name: 'Core Router 1'}) CREATE (Core_Router_2:CoreRouter {vendor:'Vendor1', name: 'Core Router 2'}) CREATE (DC1_VM1:VM {name: 'DC1-VM1'}) CREATE (CR1_CPU1:CPU {name: 'CR1-CPU1'}) CREATE (CR1_Disk1:DISK {name: 'CR1-Disk1'}) CREATE (DC1_VM2:VM {name: 'DC1-VM2'}) CREATE (CR2_CPU1:CPU {name: 'CR2-CPU1'}) CREATE (CR2_Disk1:DISK {name: 'CR2-Disk1'}) CREATE (CR1_IPInterface1:IP_Interface {name: 'CR1-IpInterface1', protocol: 'IP' }) CREATE (CR2_IPInterface1:IP_Interface {name: 'CR2-IpInterface1', protocol: 'IP' }) CREATE (CR1_IPInterface2:IP_Interface {name: 'CR1-IpInterface2', protocol: 'IP' }) CREATE (CR2_IPInterface2:IP_Interface {name: 'CR2-IpInterface2', protocol: 'IP' }) //Create Edges CREATE (Paris)-[:LOCATION_OF]-#gt;(Paris_DC_1), (Paris_DC_1)-[:CONTAINS]-#gt;(Core_Router_1), (Core_Router_1)-[:HOSTED_ON]-#gt;(DC1_VM1), (Core_Router_1)-[:CONTAINS]-#gt;(CR1_CPU1), (Core_Router_1)-[:CONTAINS]-#gt;(CR1_Disk1), (Core_Router_1)-[:CONTAINS_INTERFACE]-#gt;(CR1_IPInterface1), (Core_Router_1)-[:CONTAINS_INTERFACE]-#gt;(CR1_IPInterface2), (Paris_DC_1)-[:CONTAINS]-#gt;(Core_Router_2), (Core_Router_2)-[:HOSTED_ON]-#gt;(DC1_VM2), (Core_Router_2)-[:CONTAINS]-#gt;(CR2_CPU1), (Core_Router_2)-[:CONTAINS]-#gt;(CR2_Disk1), (Core_Router_2)-[:CONTAINS_INTERFACE]-#gt;(CR2_IPInterface1), (Core_Router_2)-[:CONTAINS_INTERFACE]-#gt;(CR2_IPInterface2), (CR1_IPInterface1)-[:IP_LINK {protocol:['IP']}]-#gt;(CR2_IPInterface1), (CR1_IPInterface2)-[:IP_LINK {protocol:['IP']}]-#gt;(CR2_IPInterface2)