IP Library Granted Patent US 10,164,986
Granted Patent B2
US 10,164,986 · App. 15/028,540 · Granted Dec 25, 2018

Realized topology system management database

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,164,986
App. No.
15/028,540
Granted
Dec 25, 2018
Kind
B2
Abstract

A realized topology system management (RTSM) database, comprising a database, a number of stored realized topologies, and in which the realized topologies within the DBMS are searchable. A method of generating and tracking a realized topology, comprising deriving a realized topology from an instantiated topology, storing the realized topology in a realized topology system management (RTSM) database, and storing a data file representing an association of the realized topology with data describing attributes of a number of nodes on the realized topology and relationships between the nodes.

Claims (58)

1. A system comprising:

a non-transitory storage medium to store a realized topology system management (RTSM) database, comprising:

a number of stored realized topologies stored within the RTSM database, wherein the realized topologies within the RTSM database are searchable;

a processor; and

a memory to store machine-readable instructions executable on the processor to:

instantiate a first topology comprising nodes representing computing resources, and branches between the nodes representing relationships between the nodes, the instantiating of the first topology creating an instantiated service by deploying the computing resources to form the instantiated service;

create a first realized topology based on the instantiated service, the first realized topology comprising a model of the first topology with policies associated with the nodes of the first topology;

store the first realized topology in the RTSM database;

detect a failure associated with the instantiated service;

apply a remediation action according to a remediation policy to resolve the failure, the remediation policy included in the policies associated with the nodes of the first topology;

modify the first realized topology based on applying the remediation action, to produce a different version of the first realized topology; and

present, in a user interface, the first realized topology and the different version of the first realized topology, and information indicating why the first realized topology was replaced by the different version of the first realized topology.

2. The system of claim 1 , wherein the RTSM database is searchable via an application programming interface (API).

3. The system of claim 1 , wherein the first realized topology comprises data describing attributes of the nodes of the first topology and the relationships between the nodes.

4. The system of claim 3 , wherein the attributes of the nodes of the first topology comprise data describing a hardware device operating as a node of the first topology, and a software associated with a node of the first topology.

5. The system of claim 1 , wherein the machine-readable instructions are executable on the processor to:

store the different version of the first realized topology in the RTSM database.

6. The system of claim 1 , wherein the different version of the first realized topology is associated with a different version of the instantiated service, and wherein the machine-readable instructions are executable on the processor to:

receive, in the user interface, a selection to rollback to a previous version of the instantiated service; and

in response to the selection, retrieve a previous version of the first realized topology from the RTSM database, and instantiate the previous version of the first realized topology to produce the previous version of the instantiated service.

7. The system of claim 6 , wherein the selection to rollback is made based on the presentation of the first realized topology and the different version of the first realized topology in the user interface.

8. A method executed by a system comprising a processor, comprising:

instantiating a first topology comprising nodes representing computing resources, and branches between the nodes representing relationships between the nodes, the instantiating of the first topology creating an instantiated service by deploying the computing resources to form the instantiated service;

deriving a realized topology from the instantiated service;

storing the realized topology in a realized topology system management (RTSM) database;

storing a data file representing an association of the realized topology with data describing attributes of the nodes of the first topology and the relationships between the nodes;

detecting an event associated with the instantiated service;

applying a remediation action according to a remediation policy to address the event, the remediation policy included in policies associated with the nodes of the first topology;

modifying the realized topology based on applying the remediation action, to produce a different version of the realized policy; and

presenting, in a user interface, the realized topology and the different version of the realized topology, and information indicating why the realized topology was replaced by the different version of the realized topology.

9. The method claim 8 , further comprising:

designing the first topology comprising a lifecycle management (LCM) topology, the LCM topology representing a computing network; and

creating a number of scripts for execution, the number of scripts defining executable logic for instantiating the instantiated service based on the LCM topology and the policies.

10. The method of claim 9 , further comprising:

monitoring, by a monitoring system, the instantiated service for the event according to a monitoring policy included in the policies.

11. The method of claim 8 , further comprising:

storing, by the system, the different version of the realized topology in the RTSM database.

12. The method of claim 8 , wherein the RTSM database stores realized topologies associated with a customer who caused instantiation of the first topology.

13. The method of claim 8 ,

wherein the different version of the realized topology is associated with a different version of the instantiated service, the method further comprising receiving, by the system in the user interface, a selection to rollback to a previous version of the instantiated service.

14. The method of claim 13 , further comprising:

in response to the selection, retrieving, by the system, a previous version of the realized topology from the RTSM database, and instantiating the previous version of the realized topology to produce the previous version of the instantiated service.

15. A non-transitory computer readable storage medium comprising instructions that upon execution cause a system to:

instantiate a first topology comprising nodes representing computing resources, and branches between the nodes representing relationships between the nodes, the instantiating of the first topology creating an instantiated cloud service by deploying the computing resources to form the instantiated cloud service;

derive a realized topology from the instantiated service;

store the realized topology in a realized topology system management (RTSM) database;

detect a failure associated with the instantiated cloud service;

apply a remediation action according to a remediation policy to resolve the failure, the remediation policy included in policies associated with the nodes of the first topology;

modify the realized topology based on applying the remediation action, to produce a different version of the realized topology; and

present, in a user interface, the realized topology and the different version of the realized topology, and information indicating why the realized topology was replaced by the different version of the realized topology.

16. The non-transitory computer readable storage medium of claim 15 , wherein the instructions upon execution cause the system to:

design the first topology comprising a lifecycle management (LCM) topology, the LCM topology representing a computing network; and

create a number of scripts for execution, the number of scripts defining executable logic for instantiating the instantiated cloud service based on the LCM topology and the policies.

17. The non-transitory computer readable storage medium of claim 15 , wherein the instructions upon execution cause the system to:

store different versions of the realized topology in the RTSM database.

18. The non-transitory computer readable storage medium of claim 17 , wherein the different versions of the realized topology are associated with respective different versions of the instantiated cloud service, and wherein the instructions upon execution cause the system to:

receive, in the user interface, a selection to rollback to a previous version of the instantiated cloud service from a current version of the instantiated cloud service; and

in response to the selection, retrieve a previous version of the different versions of the realized topology from the RTSM database, and instantiate the previous version of the realized topology to produce the previous version of the instantiated cloud service.

Assignments (8)
RELEASE OF SECURITY INTEREST REEL/FRAME 044183/0577 Recorded Feb 2, 2023
From: JPMORGAN CHASE BANK, N.A.
To: MICRO FOCUS LLC (F/K/A ENTIT SOFTWARE LLC)
Reel/Frame 063560/0001 →
RELEASE OF SECURITY INTEREST REEL/FRAME 044183/0718 Recorded Feb 2, 2023
From: JPMORGAN CHASE BANK, N.A.
To: MICRO FOCUS LLC (F/K/A ENTIT SOFTWARE LLC); BORLAND SOFTWARE CORPORATION; MICRO FOCUS (US), INC.; SERENA SOFTWARE, INC; ATTACHMATE CORPORATION; MICRO FOCUS SOFTWARE INC. (F/K/A NOVELL, INC.); NETIQ CORPORATION
Reel/Frame 062746/0399 →
CHANGE OF NAME Recorded Aug 8, 2019
From: ENTIT SOFTWARE LLC
To: MICRO FOCUS LLC
Reel/Frame 050004/0001 →
SECURITY INTEREST Recorded Oct 11, 2017
From: ATTACHMATE CORPORATION; BORLAND SOFTWARE CORPORATION; NETIQ CORPORATION; MICRO FOCUS (US), INC.; MICRO FOCUS SOFTWARE, INC.; ENTIT SOFTWARE LLC; ARCSIGHT, LLC; SERENA SOFTWARE, INC.
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 044183/0718 →
SECURITY INTEREST Recorded Oct 11, 2017
From: ENTIT SOFTWARE LLC; ARCSIGHT, LLC
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 044183/0577 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 9, 2017
From: HEWLETT PACKARD ENTERPRISE DEVELOPMENT LP
To: ENTIT SOFTWARE LLC
Reel/Frame 042746/0130 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 10, 2016
From: MAES, STEPHANE HERMAN
To: HEWLETT-PACKARD DEVELOPMENT COMPANY, L.P.
Reel/Frame 039393/0335 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 27, 2016
From: HEWLETT-PACKARD DEVELOPMENT COMPANY, L.P.
To: HEWLETT PACKARD ENTERPRISE DEVELOPMENT LP
Reel/Frame 038536/0001 →