Automated failure recovery of subsystems in a management system
First Claim
1. A system comprising:
- a processor; and
at least one memory storage device having stored thereon instructions executable by the processor to cause the system to perform operations comprising;
deploying a service manager using a microkernel controller of a plurality of microkernel controllers, the service manager corresponding to a management service that is one of a plurality of management services configured to collectively manage a plurality of domain services, the plurality of management services being configured to collectively monitor the domain services and dynamically allocate resources to the plurality of domain services such that each of the plurality of domain services maintains a predefined performance level;
receiving and parsing, at the service manager, a first pre-defined topology of a plurality of pre-defined topologies, the first pre-defined topology specifying a plurality of logical types of resources to be used by the management service;
loading, at the service manager, one or more controllers corresponding to the management service;
deploying the management service using first the pre-defined topology, including;
for a first one of the plurality of logical types of resources, binding a first respective quantity of instances of a type of physical hardware resource to the management service; and
for a second one of the plurality of logical types of resources, binding a second respective quantity of instances of a type of software resource to the management service;
in response to a failure of at least one of the first quantity of instances of a type of physical hardware resource or a failure of at least one of the second quantity of instances of a type of software resource, dynamically re-deploying the management service using the first pre-defined topology, including;
for the first logical type of resource, binding at least one different instance of the type of physical hardware to the management service;
orfor the second logical type of resource, binding at least one different instance of the type of software resource to the management service.
2 Assignments
0 Petitions
Accused Products
Abstract
Systems and methods for automated failure recovery of subsystems of a management system are described. The subsystems are built and modeled as services, and their management, specifically their failure recovery, is done in a manner similar to that of services and resources managed by the management system. The management system consists of a microkernel, service managers, and management services. Each service, whether a managed service or a management service, is managed by a service manager. The service manager itself is a service and so is in turn managed by the microkernel. Both managed services and management services are monitored via in-band and out-of-band mechanisms, and the performance metrics and alerts are transported through an event system to the appropriate service manager. If a service fails, the service manager takes policy-based remedial steps including, for example, restarting the failed service.
-
Citations
17 Claims
-
1. A system comprising:
-
a processor; and at least one memory storage device having stored thereon instructions executable by the processor to cause the system to perform operations comprising; deploying a service manager using a microkernel controller of a plurality of microkernel controllers, the service manager corresponding to a management service that is one of a plurality of management services configured to collectively manage a plurality of domain services, the plurality of management services being configured to collectively monitor the domain services and dynamically allocate resources to the plurality of domain services such that each of the plurality of domain services maintains a predefined performance level; receiving and parsing, at the service manager, a first pre-defined topology of a plurality of pre-defined topologies, the first pre-defined topology specifying a plurality of logical types of resources to be used by the management service; loading, at the service manager, one or more controllers corresponding to the management service; deploying the management service using first the pre-defined topology, including; for a first one of the plurality of logical types of resources, binding a first respective quantity of instances of a type of physical hardware resource to the management service; and for a second one of the plurality of logical types of resources, binding a second respective quantity of instances of a type of software resource to the management service; in response to a failure of at least one of the first quantity of instances of a type of physical hardware resource or a failure of at least one of the second quantity of instances of a type of software resource, dynamically re-deploying the management service using the first pre-defined topology, including; for the first logical type of resource, binding at least one different instance of the type of physical hardware to the management service;
orfor the second logical type of resource, binding at least one different instance of the type of software resource to the management service. - View Dependent Claims (2, 3, 4, 5, 6, 7)
-
-
8. A method comprising:
-
at a microkernel, deploying a service manager using a microkernel controller, the service manager corresponding to a management service, the management service being one of a plurality of management services configured to collectively manage a plurality of domain services, the plurality of management services configured to collectively monitor the domain services and dynamically allocate resources to the plurality of domain services such that each of the plurality of domain services maintains a predefined performance level; receiving and parsing, at the service manager, a first pre-defined topology that specifies a plurality of logical types of resources to be used by the management service; loading, at the service manager, one or more controllers corresponding to the management service; deploying the management service using first the pre-defined topology, including; for a first one of the plurality of logical types of resources, binding a first respective quantity of instances of a type of physical hardware resource to the management service; and for a second one of the plurality of logical types of resources, binding a second respective quantity of instances of a type of software resource to the management service; in response to a failure of at least one of the first quantity of instances of a type of physical hardware resource or a failure of at least one of the second quantity of instances of a type of software resource, dynamically re-deploying the management service using the first pre-defined topology, including; for the first logical type of resource, binding at least one different instance of the type of physical hardware to the management service;
orfor the second logical type of resource, binding at least one different instance of the type of software resource to the management service. - View Dependent Claims (9, 10, 11, 12)
-
-
13. A non-transitory computer readable storage medium having instructions embodied thereon, the instructions executable by a processor for performing a method for managing one or more components of a management system, the method comprising:
-
at a microkernel, deploying a service manager using a microkernel controller, the service manager corresponding to a management service, the management service being one of a plurality of management services configured to collectively manage a plurality of domain services, the plurality of management services configured to collectively monitor the domain services and dynamically allocate resources to the plurality of domain services such that each of the plurality of domain services maintains a predefined performance level; receiving and parsing, at the service manager, a first pre-defined topology that specifies a plurality of logical types of resources to be used by the management service; loading, at the service manager, one or more controllers corresponding to the management service; deploying the management service using first the pre-defined topology, including; for a first one of the plurality of logical types of resources, binding a first respective quantity of instances of a type of physical hardware resource to the management service; and for a second one of the plurality of logical types of resources, binding a second respective quantity of instances of a type of software resource to the management service; in response to a failure of at least one of the first quantity of instances of a type of physical hardware resource or a failure of at least one of the second quantity of instances of a type of software resource, dynamically re-deploying the management service using the first pre-defined topology, including; for the first logical type of resource, binding at least one different instance of the type of physical hardware to the management service;
orfor the second logical type of resource, binding at least one different instance of the type of software resource to the management service. - View Dependent Claims (14, 15, 16, 17)
-
Specification