Centralized automation system for resource management

1. A data center management system comprising:

processor hardware; and

memory hardware coupled to the processor hardware,

wherein the memory hardware stores:

a set of resource records, wherein each resource record of the set of resource records includes (i) a name of a resource hosted at a first data center and a second data center, and (ii) dependency data of the resource;

one or more resource templates; and

instructions to be executed by the processor hardware, including:

in response to receiving a selection of one or more resources via an operator portal, (i) generating a resource group based on the dependency data of the selected one or more resources, (ii) organizing resources in the resource group into one or more ordered components based on dependency data of each resource in the resource group, and (iii) generating a resource management page for the resource group;

displaying the resource management page; and

in response to receiving a failover request via the operator portal, stopping every resource in the resource group at the first data center and starting every resource in the resource group at the second data center,

wherein each template of the one or more resource templates includes a set of control elements,

wherein the instructions include, in response to receiving a request to register a new resource:

selecting a first template of the one or more resource templates;

obtaining (i) a name of the new resource and (ii) a description of the new resource; and

in response to obtaining (i) the name of the new resource and (ii) the description of the new resource, adding a new resource record to the set of resource records, and

wherein the new resource record includes the name of the new resource, the description of the new resource, and the set of control elements of the first template.

2. The data center management system of claim 1 wherein:

stopping every resource in the resource group at the first data center includes stopping each component of the one or more ordered components sequentially from a first component of the one or more ordered components to a last component of the one or more ordered components at the first data center;

stopping each component includes stopping each resource associated with the component;

starting every resource in the resource group at the second data center includes starting each component of the one or more ordered components sequentially from the last component to the first component at the second data center; and

starting each component includes starting each resource associated with the component.

3. The data center management system of claim 2 wherein:

the dependency data of the resource includes at least one of a parent resource that must be stopped before the resource is stopped and a child resource that must be started before the resource is started;

the first component of the resource group includes only resources that do not have an associated parent resource; and

the last component of the resource group includes only resources that do not have an associated child resource.

4. The data center management system of claim 1 wherein:

the request to register a new resource is received via the operator portal;

the selection of the first template is performed based on input from an operator; and

the operator is prompted to provide (i) the name of the new resource and (ii) the description of the new resource.

5. The data center management system of claim 1 wherein each element of the set of control elements includes a label, a default value, an order value, and one or more associated tasks.

6. The data center management system of claim 5 wherein the one or more associated tasks includes at least one of start, stop, and status.

7. The data center management system of claim 1 wherein:

stopping every resource in the resource group at the first data center includes, for each resource in the resource group, (i) generating a stop instruction based on the set of control elements associated with the resource and (ii) executing the stop instruction at the first data center; and

starting every resource in the resource group at the second data center includes, for each resource in the resource group, (i) generating a start instruction based on the set of control elements associated with the resource and (ii) executing the start instruction at the second data center.

8. The data center management system of claim 1 wherein the instructions include, in response to receiving a group status request, obtaining a status of each resource in the resource group at the first data center and the second data center.

9. The data center management system of claim 1 wherein the instructions include, in response to receiving a request to stop a selected component, stopping each resource associated with the selected component at one of the first data center and the second data center independent of dependency data of each resource associated with the selected component.

10. The data center management system of claim 1 wherein the instructions include, in response to receiving a request to start a selected resource, starting the selected resource at one of the first data center and the second data center independent of dependency data of the selected resource.

11. A data center management method comprising:

storing a set of resource records in a management data store, wherein each resource record of the set of resource records includes (i) a name of a resource hosted at a first data center and a second data center, and (ii) dependency data of the resource;

receiving a selection, via an operator portal, of one or more resources;

generating a resource group based on the dependency data of the selected one or more resources;

organizing resources in the resource group into one or more ordered components based on dependency data of each resource in the resource group;

generating a resource management page for the resource group;

displaying, via the operator portal, the resource management page to an operator;

in response to receiving, via the operator portal, a failover request, (i) stopping every resource in the resource group at the first data center and (ii) starting every resource in the resource group at the second data center;

storing one or more resource templates in the management data store, wherein each template of the one or more resource templates includes a set of control elements; and

in response to receiving a request to register a new resource:

selecting a first template of the one or more resource templates;

obtaining (i) a name of the new resource and (ii) a description of the new resource; and

adding a new resource record to the set of resource records,

wherein the new resource record includes the name of the new resource, the description of the new resource, and the set of control elements of the first template.

12. The data center management method of claim 11 wherein:

stopping every resource in the resource group at the first data center includes stopping each component of the one or more ordered components sequentially from a first component of the one or more ordered components to a last component of the one or more ordered components at the first data center;

stopping each component includes stopping each resource associated with the component;

starting every resource in the resource group at the second data center includes starting each component of the one or more ordered components sequentially from the last component to the first component at the second data center; and

starting each component includes starting each resource associated with the component.

13. The data center management method of claim 12 wherein:

the dependency data of the resource includes at least one of a parent resource that must be stopped before the resource is stopped and a child resource that must be started before the resource is started;

the first component of the resource group includes only resources that do not have an associated parent resource; and

the last component of the resource group includes only resources that do not have an associated child resource.

14. The data center management method of claim 11 wherein:

the request to register a new resource is received via the operator portal: portal;

the selection of the first template is performed based on input from the operator; and

the operator is prompted to provide (i) name of the new resource and (ii) the description of the new resource.

15. The data center management method of claim 11 wherein each element of the set of control elements includes a label, a default value, an order value, and one or more associated tasks.

16. The data center management method of claim 15 wherein the one or more associated tasks includes at least one of start, stop, and status.

17. The data center management method of claim 11 wherein:

stopping every resource in the resource group at the first data center includes, for each resource in the resource group, (i) generating a stop instruction based on the set of control elements associated with the resource and (ii) executing the stop instruction at the first data center; and

starting every resource in the resource group at the second data center includes, for each resource in the resource group, (i) generating a start instruction based on the set of control elements associated with the resource and (ii) executing the start instruction at the second data center.

18. The data center management method of claim 11 further comprising, in response to receiving a group status request via the operator portal, obtaining a status of each resource in the resource group at the first data center and the second data center.

19. The data center management method of claim 11 further comprising, in response to receiving a request to stop a selected component, stopping each resource associated with the selected component at one of the first data center and the second data center independent of dependency data of each resource associated with the selected component.

20. The data center management method of claim 11 further comprising, in response to receiving a request to start a selected resource, starting the selected resource at one of the first data center and the second data center independent of dependency data of the selected resource.