Configuring a data center

Patent metadata

Field	Value
Publication number	US-9542205-B2
Application number	US-201414568740-A
Country	US
Kind code	B2
Filing date	Dec 12, 2014
Priority date	Dec 23, 2013
Publication date	Jan 10, 2017
Grant date	Jan 10, 2017

Abstract

Embodiments of the present disclosure disclose a method and an apparatus for configuring a data center. The method comprises obtaining a function call corresponding to data to be configured based on a template for configuring the data center; obtaining a vendor driver corresponding to the data based on the template for configuring the data center. The method further comprises configuring the data by the vendor driver executing the function call. Based on the embodiments of the present disclosure, the way of automatically configuring the data center based on the template may improve the efficiency and security for configuration of the data center.

First claim

What is claimed is:

1. A method for configuring a data center, comprising:
obtaining a function call corresponding to data to be configured based on a template for configuring the data center;
wherein the template is a set of resource model instances used to describe a configuration;
obtaining a vendor driver corresponding to the data based on the template for configuring the data center;
wherein obtaining the function call corresponding to the data based on the template for configuring the data center comprises:
dividing the template into a sub-template for configuring compute data, a sub-template for configuring network data, and a sub-template for configuring storage data respectively for the compute data, wherein the network data and the storage data included in the data; and
obtaining a function call corresponding to the compute data, a function call corresponding to the network data, and a function call corresponding to the storage data respectively based on the sub-template for configuring compute data, the sub-template for configuring network data, and/or the sub-template for configuring storage data; and
configuring the data by the vendor driver by executing the function call;

wherein prior to obtaining the function call corresponding to the data based on the template for configuring the data center: determining an execution order of the function call corresponding to the compute data, the function call corresponding to the network data, and the function call corresponding to the storage data based on a predetermined configuration order of the compute data, the network data and the storage data;

wherein prior to determining the execution order:
storing at least one of a pre-defined template or a template created by a user in a template repository; and
determining from the template repository an appropriate template required for configuring the data center.

2. The method according to claim 1 , wherein prior to storing:
checking syntax of the template.

3. The method according to claim 1 , wherein prior to storing:
verifying available resource of the template.

4. The method according to claim 3 , further comprises:
checking user's authorization on the available resource.

5. The method according to any of claim 1 , wherein obtaining a vendor driver corresponding to the data based on the template for configuring the data center comprises:
obtaining
a template name of a sub-template for configuring compute data,
a template name of a sub-template for configuring network data, and
a template name of a sub-template for configuring storage data, respectively; and

obtaining vendor drivers corresponding to the template name for the compute data, network data and storage data.

6. The method according to any of claim 1 , wherein obtaining a vendor driver corresponding to the data based on the template for configuring the data center comprises:
obtaining an identifier corresponding to compute data, an identifier corresponding to network data, and an identifier corresponding to storage data, respectively; and
looking up based on each of the identifier, a driver lookup table for storing a corresponding relationship between each of the identifiers and the vendor driver to obtain the vendor driver.

7. The method according to any of claim 1 , wherein obtaining a vendor driver corresponding to the data based on the template for configuring the data center comprises:
obtaining an attribute of a vendor driver corresponding to compute data, an attribute of a vendor driver corresponding to network data, and an attribute of a vendor driver corresponding to storage data, respectively; and
obtaining vendor drivers corresponding to the attributes.

8. An apparatus for configuring a data center, comprising:
a system including one or more modules and one or more processors, wherein a module of the one or more modules is configured
to obtain a function call corresponding to data to be configured based on a template for configuring the data center;
wherein the template is a set of resource model instances used to describe a configuration;
to obtain a vendor driver corresponding to the data based on the template for configuring the data center;
to obtain the data by the vendor driver executing the function call;
dividing the template into
a sub-template for configuring compute data,
a sub-template for configuring network data, and
a sub-template for configuring storage data respectively for the compute data, the network data and the storage data included in the data; and

to obtain a function call corresponding to the compute data, a function call corresponding to the network data, and a function call corresponding to the storage data respectively based on the sub-template for configuring compute data, the sub-template for configuring network data, and the sub-template for configuring storage data;
wherein the module is further configured to determine an execution order of
the function call corresponding to the compute data,
the function call corresponding to the network data, and
the function call corresponding to the storage data based on a predetermined configuration order of the compute data, the network data and the storage data wherein the module is further configured:
to store a pre-defined template or a template created by a user in a template repository; and
to determine from the template repository an appropriate template for configuring the data center.

9. The apparatus according to claim 8 , wherein the module is further configured
to check syntax of the template;
to verify available resource of the template; and
to check user's authorization on the available resource.

10. The apparatus according to any of claim 8 , wherein the module is further configured to obtain
a template name of a sub-template for configuring compute data,
a template name of a sub-template for configuring network data, and
a template name of a sub-template for configuring storage data, respectively; and
vendor drivers corresponding to the template names.

11. The apparatus according to any of claim 8 , wherein the module is further configured
to obtain
an identifier corresponding to compute data,
an identifier corresponding to network data, and
an identifier corresponding to storage data, respectively; and

to look up based on the identifiers, a driver lookup table for storing a corresponding relationship between the identifiers and the vendor driver to obtain the vendor driver.

12. The apparatus according claim 8 , wherein the module is further configured
to obtain
an attribute of a vendor driver corresponding to compute data,
an attribute of a vendor driver corresponding to network data, and
an attribute of a vendor driver corresponding to storage data; and

to obtain vendor drivers corresponding to the attributes.

13. The Apparatus according to claim 8 , wherein the module comprises at least one of a software component, a hardware component or a firmware component.

Assignees

• Emc Corp
• Emc Ip Holding Co Llc

Inventors

• Zhang Yun
• Peng Lin
• Wang Tianqing
• Yan Kai
• Guo Feng

Classifications

• G06F9/44505 Primary

  Configuring for program initiating, e.g. using registry, configuration files · CPC title

• G06F9/54

  Interprogram communication · CPC title

• G06F9/4411

  Configuring for operating with peripheral devices; Loading of device drivers · CPC title

• G06F9/445

  Program loading or initiating (bootstrapping G06F9/4401; security arrangements for program loading or initiating G06F21/57) · CPC title

• H04L41/0806

  for initial configuration or provisioning, e.g. plug-and-play · CPC title