Management of computer systems by using a hierarchy of autonomic management elements
View Patent ↗A method and system for managing a computing system by using a hierarchy of autonomic management elements are described. The autonomic management elements operate in a master-slave mode and negotiate a division of management responsibilities regarding various components of the computing system.
1. A method for managing a computing system having components, the components including a hardware platform, an operating system or a hypervisor, a guest operating system, and software applications, the method comprising:
arranging the components of the computing system in a hierarchy of layers, comprising a lowest layer, a highest layer and one or more intermediate layers, comprising arranging:
the hardware platform to occupy the lowest layer;
the hypervisor to occupy an intermediate layer of the one or more intermediate layers;
the guest operating system to occupy another intermediate layer of the one or more intermediate layers; and
the software applications to occupy the highest layer;
launching at least two autonomic management elements, each autonomic management element running in a different layer, comprising launching:
one autonomic management element in the hardware platform;
another autonomic management element in the hypervisor; and
yet another autonomic management element in the guest operating system; and
configuring each autonomic management element as a master or a slave depending on a position of the each autonomic management element in the hierarchy of layers, and running the at least two autonomic management elements in a master-slave mode, the master controlling the management responsibilities of the slave, comprising configuring:
the one autonomic management element running in the hardware platform as the master for all other autonomic management elements;
the yet another autonomic management element running in the guest operating system as the slave for all other autonomic management elements; and
the another autonomic management element running in the hypervisor:
as the master for the yet another autonomic management element running in the guest operating system; and
as the slave for the one autonomic management element running in the hardware platform.
2. The method of claim 1 , further comprising:
negotiating a division of management responsibilities between the at least two autonomic management elements regarding the components of the computing system; and
managing the components of the computing system by the at least two autonomic management elements according to the division of management responsibilities.
3. The method of claim 1 , further comprising exchanging information between the at least two autonomic elements, including exchanging unique tokens between the at least two autonomic elements.
4. The method of claim 1 , further comprising maintaining a heartbeat signal between the at least two autonomic elements.
5. The method of claim 1 , further comprising:
listening for a connection request from a slave for an autonomic management element;
assuming management responsibilities regarding a component in which the autonomic management element is running before arrival of the connection request; and
upon the arrival of the connection request, communicating with the slave regarding a division of the management responsibilities.
6. The method of claim 1 , further comprising:
sending a connection request to a master for an autonomic management element;
assuming management responsibilities regarding a component in which the autonomic management element is running before the connection request is satisfied; and
upon satisfying the connection request, communicating with the master regarding a division of the management responsibilities.
7. The method of claim 1 , further comprising launching, by a slave, an automatic discovery procedure, based on a communication protocol, to connect to a master.
8. The method of claim 1 , further comprising, upon successful automatic discovery procedure, performing one or more of the following:
accepting the slave;
redirecting the slave to another master;
delegating management tasks to the slave;
updating resource configuration information;
re-negotiating management responsibilities between the master and the slave.
9. The method of claim 8 , further comprising, upon successful automatic discovery procedure, registering with the master, comprising reporting:
a layer where the slave is located;
which other slaves the slave is a master of;
current resource profile of the slave; and
current management responsibilities of the slave and the other slaves.
10. The method of claim 1 , wherein the configuring comprises configuring the slave according to one or more of the following:
manual configuration;
network-based configuration; or
direct memory access configuration.
11. A system for managing a computing system having components, the components including a hardware platform, an operating system or a hypervisor, a guest operating system, and software applications, the system comprising:
at least one processor;
a non-transitory computer readable storage medium, having computer-readable instructions stored thereon for execution by the processor, causing the processor to:
arrange the components of the computing system in a hierarchy of layers, comprising a lowest layer, a highest layer and one or more intermediate layers, comprising arranging:
the hardware platform to occupy the lowest layer;
the hypervisor to occupy an intermediate layer of the one or more intermediate layers;
the guest operating system to occupy another intermediate layer of the one or more intermediate layers; and
the software applications to occupy the highest layer;
launch at least two autonomic management elements, each autonomic management element running in a different layer, comprising launching:
one autonomic management element in the hardware platform;
another autonomic management element in the hypervisor; and
yet another autonomic management element in the guest operating system; and
configure each autonomic management element as a master or a slave depending on a position of the each autonomic management element in the hierarchy of layers, and running the at least two autonomic management elements in a master-slave mode, the master controlling the management responsibilities of the slave, comprising configuring:
the one autonomic management element running in the hardware platform as the master for all other autonomic management elements;
the yet another autonomic management element running in the guest operating system as the slave for all other autonomic management elements and
the another autonomic management element running in the hypervisor;
as the master for the yet another autonomic management element running in the guest operating system; and
as the slave for the one autonomic management element running in the hardware platform.
12. The system of claim 11 , wherein the computer-readable instructions further cause the processor to:
negotiate a division of management responsibilities between the at least two autonomic management elements regarding the components of the computing system; and
manage the components of the computing system by the at least two autonomic management elements according to the division of management responsibilities.
13. The system of claim 11 , wherein the computer-readable instructions further cause the processor to exchange unique tokens between the at least two autonomic elements to identify a connection between the at least two autonomic elements.
14. The system of claim 11 , wherein the computer-readable instructions further cause the processor to maintain a heartbeat signal communication between the at least two autonomic elements.
15. The system of claim 11 , wherein the computer-readable instructions further cause the processor to:
listen for a connection request from a slave for an autonomic management element;
assume management responsibilities regarding a component in which the autonomic management element is running before arrival of the connection request; and
upon the arrival of the connection request, communicate with the slave regarding a division of the management responsibilities.
16. The system of claim 11 , wherein the computer-readable instructions further cause the processor to:
send a connection request to a master for an autonomic management element;
assume management responsibilities regarding a component in which the autonomic management element is running before the connection request is satisfied; and
upon satisfying the connection request, communicate with the master regarding a division of the management responsibilities.
17. The system of claim 11 , wherein the computer-readable instructions further cause the processor to launch, by a slave, an automatic discovery procedure, based on a communication protocol, to connect to a master.
18. The system of claim 17 , wherein the computer-readable instructions further cause the processor, upon successful automatic discovery procedure, to register with the master, comprising reporting:
a layer where the slave is located;
which other slaves the slave is a master of;
current resource profile of the slave; and
current management responsibilities of the slave and the other slaves.
19. The system of claim 11 , wherein the computer-readable instructions further cause the processor to perform one or more of the following, upon successful automatic discovery procedure:
accept the slave;
redirect the slave to another master;
delegate management tasks to the slave;
update resource configuration information;
re-negotiate management responsibilities between the master and the slave.
20. The system of claim 11 , wherein the computer-readable instructions further cause the processor to configure the slave according to one of:
manual configuration;
network-based configuration; or
direct memory access configuration.