IP Library Granted Patent US 10,346,443
Granted Patent B2
US 10,346,443 · App. 15/590,148 · Granted Jul 9, 2019

Managing services instances

Inventors: Prashant Gupte (Sunnyvale, CA); Stephane Herman Maes (Fremont, CA)
Assignee: ENTIT SOFTWARE LLC
G06F16/288G06F8/60G06F9/44521G06F16/90335G06N5/043H04L41/0893H04L41/145H04L67/16G06N5/04H04L41/12
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,346,443
App. No.
15/590,148
Granted
Jul 9, 2019
Kind
B2
Abstract

In some examples, information of a service instance provisioned or modified by a first system distinct from a management system is received, where the provisioning or modification of the service instance by the first system is initially unknown to the management system. As part of a binding phase, a model of the service instance is inferred. The management system manages a lifecycle of the service instance using the model and the policy.

Claims (40)

1. A method executed by at least one processor, comprising:

as part of a discovery phase, receiving information of a service instance provisioned or modified by a first system distinct from a management system, wherein the provisioning or modification of the service instance by the first system is initially unknown to the management system;

as part of a binding phase, inferring a model representing the service instance provisioned or modified by the first system, wherein the model comprises nodes representing service components of the service instance, and links between the nodes representing relationships between the service components, and wherein inferring the model comprises accessing information of the service components of the service instance and determining how the service components are related to one another, and

managing, by the management system, a lifecycle of the service instance using the model.

2. The method of claim 1 , further comprising, as part of the binding phase, associating an action with a node of the model, wherein managing the lifecycle of the service instance further uses the action.

3. The method of claim 2 , wherein associating the action with the model comprises associating an application programming interface (API) that is useable by the management system to perform the action as part of the managing of the lifecycle of the service instance.

4. The method of claim 2 , wherein the action is a lifecycle action selected from among starting a service instance, moving a service instance, terminating a service instance, scaling operation of a service instance, monitoring a service instance, or managing a service instance.

5. The method of claim 1 , wherein the managing comprises one or both of monitoring the service instance and tracking the service instance.

6. The method of claim 1 , wherein receiving the information of the service instance as part of the discovery phase comprises obtaining, by the management system, the information of the service instance from a discovery engine that gathers information of attributes of service instances and relationships between the service instances and components of the service instances.

7. The method of claim 1 , wherein receiving the information of the service instance as part of the discovery phase comprises obtaining the information of the service instance from an engine that tracks assets of an environment and produces information about service instances that are tracked and dependencies of service components of the service instances.

8. The method of claim 1 , wherein receiving the information of the service instance as part of the discovery phase comprises obtaining the information of the service instance from an analytics system that performs analysis of service instances in an environment.

9. The method of claim 1 , wherein receiving the information of the service instance as part of the discovery phase comprises querying data from a configuration management database (CMDB).

10. The method of claim 1 , further comprising, as part of the binding phase, associating a policy with the model, the policy indicating any one or a combination of the service instance to monitor or manage, an entity to notify during the managing of the lifecycle of the service instance, a cloud zone in which the service instance is to be placed, or updating of the service instance.

11. The method of claim 1 , wherein the binding phase further comprises associating a user or organization with the service instance, and wherein associating the user or the organization with the service instance comprises associating a permission for the user or the organization to access or manage the service instance.

12. The method of claim 1 , further comprising:

receiving a user edit of the inferred model to perform one of:

adapt the model for a first environment to deploy the service instance in a different second environment, or

correct the model.

13. The method of claim 1 , wherein the management system is a cloud controller to manage a cloud, and wherein the provisioning of the service instance by the first system is responsive to delegation, by the cloud controller, of the provisioning or day-2 management to the first system.

14. The method of claim 1 , wherein the first system that provisioned or modified the service instance is selected from among a cloud controller, a PaaS module, a container controller, a program, a tool, or a device responsive to user input.

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

receive information of a service instance provisioned or modified by a provider system distinct from a management system, wherein the provisioning or modification of the service instance by the provider system is initially unknown to the management system;

as part of a binding phase,

create a model representing service components of the service instance provisioned or modified by the provider system, wherein the model comprises nodes representing the service components of the service instance, and links between the nodes representing relationships between the service components, and wherein creating the model comprises accessing information of the service components of the service instance and determining how the service components are related to one another, and

associate a lifecycle action with an element or a group of elements of the model; and

use the management system to manage a lifecycle of the service instance using the model and the lifecycle action.

16. The non-transitory machine-readable storage medium of claim 15 , wherein the instructions upon execution cause the system to associate a policy with the model, the policy relating to monitoring or managing the service instance.

17. A system comprising:

a processor; and

a non-transitory storage medium storing instructions executable on the processor to:

as part of a discovery phase, receive information of a service instance provisioned or modified by a first system distinct from a cloud controller, wherein the provisioning or modification of the service instance by the first system is initially unknown to the management system;

as part of a binding phase,

infer a model of the service instance provisioned or modified by the first system, wherein the model comprises nodes representing service components of the service instance, and links between the nodes representing relationships between the service components, and wherein inferring the model comprises accessing information of the service components of the service instance and determining how the service components are related to one another,

associate a policy with an element or group of elements of the model, and

associate a lifecycle action with an element or a group of elements of the model; and

use the cloud controller to manage a lifecycle of the service instance using the model, the policy, and the lifecycle action.

18. The system of claim 17 , wherein the model that is inferred is different from an initial model that the cloud controller is aware of, the initial model not reflecting the service instance as provisioned or modified by the first system distinct from the cloud controller.

19. The method of claim 1 , wherein the information of the service components accessed to infer the model comprises observed traffic between the service components.

20. The method of claim 1 , wherein the model that is inferred is different from an initial model that the management system is aware of, the initial model not reflecting the service instance as provisioned or modified by the first system distinct from the management system.

21. The non-transitory machine-readable storage medium of claim 15 , wherein the model that is created is different from an initial model that the management system is aware of, the initial model not reflecting the service instance as provisioned or modified by the provider system distinct from the management system.

Assignments (11)
RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 063546/0181) Recorded Jun 21, 2024
From: BARCLAYS BANK PLC
To: MICRO FOCUS LLC
Reel/Frame 067807/0076 →
SECURITY INTEREST Recorded Aug 30, 2023
From: MICRO FOCUS LLC
To: THE BANK OF NEW YORK MELLON
Reel/Frame 064760/0862 →
SECURITY INTEREST Recorded May 4, 2023
From: MICRO FOCUS LLC
To: BARCLAYS BANK PLC
Reel/Frame 063546/0190 →
SECURITY INTEREST Recorded May 4, 2023
From: MICRO FOCUS LLC
To: BARCLAYS BANK PLC
Reel/Frame 063546/0230 →
SECURITY INTEREST Recorded May 4, 2023
From: MICRO FOCUS LLC
To: BARCLAYS BANK PLC
Reel/Frame 063546/0181 →
RELEASE OF SECURITY INTEREST REEL/FRAME 052295/0041 Recorded Feb 2, 2023
From: JPMORGAN CHASE BANK, N.A.
To: MICRO FOCUS LLC; MICRO FOCUS SOFTWARE INC. (F/K/A NOVELL, INC.); NETIQ CORPORATION
Reel/Frame 062625/0754 →
RELEASE OF SECURITY INTEREST REEL/FRAME 052294/0522 Recorded Feb 2, 2023
From: JPMORGAN CHASE BANK, N.A.
To: MICRO FOCUS LLC; MICRO FOCUS SOFTWARE INC. (F/K/A NOVELL, INC.); NETIQ CORPORATION
Reel/Frame 062624/0449 →
SECURITY AGREEMENT Recorded Apr 2, 2020
From: MICRO FOCUS LLC; BORLAND SOFTWARE CORPORATION; MICRO FOCUS SOFTWARE INC.; NETIQ CORPORATION; MICRO FOCUS (US), INC.
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 052294/0522 →
SECURITY AGREEMENT Recorded Apr 2, 2020
From: MICRO FOCUS LLC; BORLAND SOFTWARE CORPORATION; MICRO FOCUS SOFTWARE INC.; NETIQ CORPORATION; MICRO FOCUS (US), INC.
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 052295/0041 →
CHANGE OF NAME Recorded Aug 8, 2019
From: ENTIT SOFTWARE LLC
To: MICRO FOCUS LLC
Reel/Frame 050004/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 9, 2017
From: GUPTE, PRASHANT; MAES, STEPHANE HERMAN
To: ENTIT SOFTWARE LLC
Reel/Frame 042303/0543 →
Continuity (1)
Related Publication 20180329981A1 · Nov 15, 2018