Systems and methods for multilayer monitoring of network function virtualization architectures
In one embodiment, a method is performed by a computer system. The method includes creating an integrated topology model (ITM) instance of interconnected topology objects. The ITM instance includes a physical infrastructure topology model (PITM) instance comprising first interconnected topology objects, a virtual infrastructure topology model (VITM) instance comprising second interconnected topology objects, a network service topology model (NSTM) instance comprising third interconnected topology objects and inter-model linking information. The method also includes generating dependencies between the interconnected topology objects of the ITM instance based, at least in part, on the inter-model linking information. Further, the method includes generating a dependency graph based, at least in part, on the dependencies. The method also includes outputting at least a portion of the dependency graph for presentation to a user.
1. A method comprising, by a computer system:
responsive to deployment of at least one component of a virtual network function (VNF) in a multilayer network function virtualization (NFV) architecture, creating an integrated topology model (ITM) instance of interconnected topology objects, the ITM instance comprising:
a physical infrastructure topology model (PITM) instance comprising first interconnected topology objects, the first interconnected topology objects representing a plurality of monitored physical resources residing at a physical infrastructure layer of the multilayer NFV architecture, wherein interconnections between the first interconnected topology objects reflect relationships between the plurality of monitored physical resources;
a virtual infrastructure topology model (VITM) instance comprising second interconnected topology objects, the second interconnected topology objects representing a plurality of monitored virtual resources residing at a virtual infrastructure layer of the multilayer NFV architecture, wherein the plurality of monitored virtual resources are physically implemented at the physical infrastructure layer, wherein interconnections between the second interconnected topology objects reflect relationships between the plurality of monitored virtual resources;
a network service topology model (NSTM) instance comprising third interconnected topology objects, the third interconnected topology objects representing a plurality of monitored virtual network resources residing at a network service layer of the multilayer NFV architecture, wherein the monitored virtual network resources are virtually realized at the virtual infrastructure layer, wherein interconnections between the third interconnected topology objects reflect relationships between the plurality of monitored virtual network resources; and
inter-model linking information usable to relate at least some of the third interconnected topology objects to at least some of the second interconnected topology objects;
generating dependencies between the interconnected topology objects of the ITM instance based, at least in part, on the inter-model linking information, wherein the dependencies comprise:
a dependency of at least one of the third interconnected topology objects on at least one of the second topology objects; and
a dependency of at least one of the second interconnected topology objects on at least one of the first interconnected topology objects
generating a dependency graph for the multilayer NFV architecture based, at least in part, on the dependencies; and
outputting at least a portion of the dependency graph for presentation to a user.
2. The method of claim 1 , wherein:
the first interconnected topology objects of the PITM instance comprise:
a plurality of physical host objects that model physical hosts residing at the physical infrastructure layer; and
a plurality of physical path objects that each model a physical path between at least two physical hosts;
the second interconnected topology objects of the VITM instance comprise:
a plurality of virtual container objects that model virtual containers residing at the virtual infrastructure layer;
a plurality of virtual path objects that each model a virtual path between at least two virtual containers;
the third interconnected topology objects of the NSTM instance comprise:
a plurality of VNF objects that model VNFs residing at the network service layer;
a plurality of VNF path objects that each model a path between at least two VNFs;
a plurality of VNF component (VNFC) objects that model VNFCs residing at the network service layer; and
a plurality of VNFC path objects that each model a path between at least two VNFCs.
3. The method of claim 2 , wherein the generating dependencies comprises:
determining internal dependencies within each of the PITM instance, the VITM instance and the NSTM instance;
determining, for each VNFC object in the NSTM instance, a corresponding virtual container object in the VITM instance, wherein the dependencies comprise a dependency of the VNFC object on the corresponding virtual container object;
determining, for each virtual container object in the VITM instance, a corresponding physical host object in the PITM instance, wherein the dependencies comprise a dependency of the virtual container object on the corresponding physical host object;
determining, for each VNFC path object in the NSTM instance, a corresponding virtual path object in the VITM instance, wherein the dependencies comprise a dependency of the VNFC path object on the corresponding virtual path object; and
determining, for each virtual path object in the VITM instance, a corresponding physical path object in the PITM instance, wherein the dependencies comprise a dependency of the virtual path object on the corresponding physical path object.
4. The method of claim 3 , wherein the determining, for each VNFC object in the NSTM instance, a corresponding virtual container object in the VITM instance, comprises:
traversing the NSTM instance; and
for each VNFC object in the NSTM instance, looking up an identifier of the VNFC object in a linking object, wherein the linking object comprises a plurality of entries, each entry linking a VNFC object identifier to a virtual container object identifier.
5. The method of claim 3 , wherein the determining, for each VNFC object in the NSTM instance, a corresponding virtual container object in the VITM instance, comprises:
traversing the NSTM instance; and
determining a virtual container object identifier stored within each VNFC object.
6. The method of claim 3 , wherein the determining, for each virtual container object in the VITM instance, a corresponding physical host object in the PITM instance, comprises:
determining two VNFC endpoints for each VNFC path object in the NSTM instance;
for each determined VNFC endpoint, determining a corresponding virtual container object in the VITM instance;
for each determined VNFC endpoint, creating a list of virtual network interfaces of the corresponding virtual container object, wherein the creating results in two lists for each VNFC path object in the NSTM instance; and
for each VNFC path object in the NSTM instance, determining, based at least in part on a traversal of the VITM instance, a virtual path object in the VITM instance that includes a virtual network interface from each of the two lists for the VNFC path object.
7. The method of claim 3 , wherein the determining, for each virtual path object in the VITM instance, a corresponding physical path object in the PITM instance, comprises:
for each virtual path object in the VITM instance, determining two virtual network interfaces that serve as virtual endpoints of a virtual path modeled thereby;
for each determined virtual network interface, determining a physical host object in the PITM instance which models a physical host that services the determined virtual network interface, wherein the determining results in a first physical host object and a second physical host object being determined for each virtual path object in the VITM instance;
for each virtual path object in the VITM instance, determining, based at least in part on a traversal of the PITM instance, a physical network interface object contained by the first physical host object and a physical network interface contained by the second physical host object; and
for each virtual path object in the VITM instance, identifying, based at least in part on a traversal of the PITM instance, a physical path object that identifies both the physical network interface object contained by the first physical host object and the physical network interface object contained by the second physical host object.
8. The method of claim 1 , wherein the creating an ITM instance comprises creating, as at least part of the inter-model linking information, a linking object that links each VNFC object of the NSTM instance to a virtual container object of the VITM instance.
9. The method of claim 1 , comprising:
receiving monitoring data related to the plurality of monitored resources;
transforming the monitoring data in real-time into the ITM instance; and
presenting the transformed monitoring data to the user in relation to the dependency graph.
10. The method of claim 9 , wherein the transforming comprises propagating a detected event at one layer of the multilayer NFV architecture to at least one other layer of the multilayer NFV architecture based, at least in part, on the dependency graph.
11. The method of claim 9 , wherein the transforming comprises propagating a detected event at the physical infrastructure layer to the virtual infrastructure layer and to the physical infrastructure layer based, at least in part, on the dependency graph.
12. An information handling system comprising a processor, wherein the processor is operable to implement a method comprising:
responsive to deployment of at least one component of a virtual network function (VNF) in a multilayer network function virtualization (NFV) architecture, creating an integrated topology model (ITM) instance of interconnected topology objects, the ITM instance comprising:
a physical infrastructure topology model (PITM) instance comprising first interconnected topology objects, the first interconnected topology objects representing a plurality of monitored physical resources residing at a physical infrastructure layer of the multilayer NFV architecture, wherein interconnections between the first interconnected topology objects reflect relationships between the plurality of monitored physical resources;
a virtual infrastructure topology model (VITM) instance comprising second interconnected topology objects, the second interconnected topology objects representing a plurality of monitored virtual resources residing at a virtual infrastructure layer of the multilayer NFV architecture, wherein the plurality of monitored virtual resources are physically implemented at the physical infrastructure layer, wherein interconnections between the second interconnected topology objects reflect relationships between the plurality of monitored virtual resources;
a network service topology model (NSTM) instance comprising third interconnected topology objects, the third interconnected topology objects representing a plurality of monitored virtual network resources residing at a network service layer of the multilayer NFV architecture, wherein the monitored virtual network resources are virtually realized at the virtual infrastructure layer, wherein interconnections between the third interconnected topology objects reflect relationships between the plurality of monitored virtual network resources; and
inter-model linking information usable to relate at least some of the third interconnected topology objects to at least some of the second interconnected topology objects;
generating dependencies between the interconnected topology objects of the ITM instance based, at least in part, on the inter-model linking information, wherein the dependencies comprise:
a dependency of at least one of the third interconnected topology objects on at least one of the second topology objects; and
a dependency of at least one of the second interconnected topology objects on at least one of the first interconnected topology objects
generating a dependency graph for the multilayer NFV architecture based, at least in part, on the dependencies; and
outputting at least a portion of the dependency graph for presentation to a user.
13. The information handling system of claim 12 , wherein:
the first interconnected topology objects of the PITM instance comprise:
a plurality of physical host objects that model physical hosts residing at the physical infrastructure layer; and
a plurality of physical path objects that each model a physical path between at least two physical hosts;
the second interconnected topology objects of the VITM instance comprise:
a plurality of virtual container objects that model virtual containers residing at the virtual infrastructure layer;
a plurality of virtual path objects that each model a virtual path between at least two virtual containers;
the third interconnected topology objects of the NSTM instance comprise:
a plurality of VNF objects that model VNFs residing at the network service layer;
a plurality of VNF path objects that each model a path between at least two VNFs;
a plurality of VNF component (VNFC) objects that model VNFCs residing at the network service layer; and
a plurality of VNFC path objects that each model a path between at least two VNFCs.
14. The information handling system of claim 13 , wherein the generating dependencies comprises:
determining internal dependencies within each of the PITM instance, the VITM instance and the NSTM instance;
determining, for each VNFC object in the NSTM instance, a corresponding virtual container object in the VITM instance, wherein the dependencies comprise a dependency of the VNFC object on the corresponding virtual container object;
determining, for each virtual container object in the VITM instance, a corresponding physical host object in the PITM instance, wherein the dependencies comprise a dependency of the virtual container object on the corresponding physical host object;
determining, for each VNFC path object in the NSTM instance, a corresponding virtual path object in the VITM instance, wherein the dependencies comprise a dependency of the VNFC path object on the corresponding virtual path object; and
determining, for each virtual path object in the VITM instance, a corresponding physical path object in the PITM instance, wherein the dependencies comprise a dependency of the virtual path object on the corresponding physical path object.
15. The information handling system of claim 14 , wherein the determining, for each VNFC object in the NSTM instance, a corresponding virtual container object in the VITM instance, comprises:
traversing the NSTM instance; and
for each VNFC object in the NSTM instance, looking up an identifier of the VNFC object in a linking object, wherein the linking object comprises a plurality of entries, each entry linking a VNFC object identifier to a virtual container object identifier.
16. The information handling system of claim 14 , wherein the determining, for each VNFC object in the NSTM instance, a corresponding virtual container object in the VITM instance, comprises:
traversing the NSTM instance; and
determining a virtual container object identifier stored within each VNFC object.
17. The information handling system of claim 14 , wherein the determining, for each virtual container object in the VITM instance, a corresponding physical host object in the PITM instance, comprises:
determining two VNFC endpoints for each VNFC path object in the NSTM instance;
for each determined VNFC endpoint, determining a corresponding virtual container object in the VITM instance;
for each determined VNFC endpoint, creating a list of virtual network interfaces of the corresponding virtual container object, wherein the creating results in two lists for each VNFC path object in the NSTM instance; and
for each VNFC path object in the NSTM instance, determining, based at least in part on a traversal of the VITM instance, a virtual path object in the VITM instance that includes a virtual network interface from each of the two lists for the VNFC path object.
18. The information handling system of claim 14 , wherein the determining, for each virtual path object in the VITM instance, a corresponding physical path object in the PITM instance, comprises:
for each virtual path object in the VITM instance, determining two virtual network interfaces that serve as virtual endpoints of a virtual path modeled thereby;
for each determined virtual network interface, determining a physical host object in the PITM instance which models a physical host that services the determined virtual network interface, wherein the determining results in a first physical host object and a second physical host object being determined for each virtual path object in the VITM instance;
for each virtual path object in the VITM instance, determining, based at least in part on a traversal of the PITM instance, a physical network interface object contained by the first physical host object and a physical network interface contained by the second physical host object; and
for each virtual path object in the VITM instance, identifying, based at least in part on a traversal of the PITM instance, a physical path object that identifies both the physical network interface object contained by the first physical host object and the physical network interface object contained by the second physical host object.
19. The information handling system of claim 12 , wherein the creating an ITM instance comprises creating, as at least part of the inter-model linking information, a linking object that links each VNFC object of the NSTM instance to a virtual container object of the VITM instance.
20. A computer-program product comprising a non-transitory computer-usable medium having computer-readable program code embodied therein, the computer-readable program code adapted to be executed to implement a method comprising:
responsive to deployment of at least one component of a virtual network function (VNF) in a multilayer network function virtualization (NFV) architecture, creating an integrated topology model (ITM) instance of interconnected topology objects, the ITM instance comprising:
a physical infrastructure topology model (PITM) instance comprising first interconnected topology objects, the first interconnected topology objects representing a plurality of monitored physical resources residing at a physical infrastructure layer of the multilayer NFV architecture, wherein interconnections between the first interconnected topology objects reflect relationships between the plurality of monitored physical resources;
a virtual infrastructure topology model (VITM) instance comprising second interconnected topology objects, the second interconnected topology objects representing a plurality of monitored virtual resources residing at a virtual infrastructure layer of the multilayer NFV architecture, wherein the plurality of monitored virtual resources are physically implemented at the physical infrastructure layer, wherein interconnections between the second interconnected topology objects reflect relationships between the plurality of monitored virtual resources;
a network service topology model (NSTM) instance comprising third interconnected topology objects, the third interconnected topology objects representing a plurality of monitored virtual network resources residing at a network service layer of the multilayer NFV architecture, wherein the monitored virtual network resources are virtually realized at the virtual infrastructure layer, wherein interconnections between the third interconnected topology objects reflect relationships between the plurality of monitored virtual network resources; and
inter-model linking information usable to relate at least some of the third interconnected topology objects to at least some of the second interconnected topology objects;
generating dependencies between the interconnected topology objects of the ITM instance based, at least in part, on the inter-model linking information, wherein the dependencies comprise:
a dependency of at least one of the third interconnected topology objects on at least one of the second topology objects; and
a dependency of at least one of the second interconnected topology objects on at least one of the first interconnected topology objects
generating a dependency graph for the multilayer NFV architecture based, at least in part, on the dependencies; and
outputting at least a portion of the dependency graph for presentation to a user.