Normalized searchable cloud layer

• US 9,747,314 B2
• Filed: 07/25/2013
• Issued: 08/29/2017
• Est. Priority Date: 07/25/2013
• Status: Active Grant

• Current Assignee: Rackspace US Incorporated (Apollo Global Management, Inc.)
• Original Assignee: Rackspace US Incorporated (Apollo Global Management, Inc.)
• Inventors: Sigler, Egle
• Primary Examiner(s): Mackes, Kris
• Assistant Examiner(s): Lin, Allen
• Application Number:
  US13/950,989
• Publication Number:
  US 20150032756A1
• Time in Patent Office: 1,496 Days
• Field of Search: 707741
• CPC Class Codes: G06F 16/2228 Indexing structures

Abstract

An example system for indexing heterogeneous resources includes a data module that invokes one or more APIs, and responsive to the invoked one or more APIs, receives a first set of attributes of one or more cloud resources of a first subset of the set of cloud resources and a second set of attributes of one or more cloud resources of a second subset of the set of cloud resources. The system also includes a normalization module that for at least one attribute of the first and second sets of attributes, searches a database for a normalized attribute corresponding to the respective one attribute, normalizes based on the uniform schema the respective attribute, and places the normalized attribute in a data structure. The system further includes an indexing module that indexes the normalized attributes in the data structure.

Claims

1. A system for indexing heterogeneous resources, the system comprising:

a database including a set of mappings from an attribute name of a physical resource specific to a cloud to a normalized attribute name based on a uniform schema; and

one or more processors coupled to the database and configured to execute computer program modules, the computer program modules comprising;

a data module executable by the one or more processors, wherein the data module identifies a set of physical resources in a plurality of virtual datacenters, invokes a single application programming interface (API), wherein the invoked API causes invocation of a first API and a second API different from the first API, and wherein responsive to the invoked first API the data module receives a first set of attribute names, and responsive to the invoked second API the data module receives a second set of attribute names,

wherein each virtual datacenter of the plurality of virtual datacenters is associated with a cloud consumer'"'"'s account, and wherein a first virtual datacenter includes one or more physical resources located in a first physical data center and one or more physical resources located in a second physical data center, and a second virtual datacenter includes one or more physical resources located in the first physical data center and one or more physical resources located in a third physical data center,

wherein a first subset of physical resources is executable in the first cloud, and a second subset of physical resources is executable in the second cloud, and

wherein the first set of attribute names is compatible with the first cloud and incompatible with the second cloud, and the second set of attribute names is compatible with the second cloud and incompatible with the first cloud;

a normalization module executable by the one or more processors, wherein for a first attribute name of the first set of attribute names, the normalization module searches the database for a first normalized attribute name corresponding to the first attribute name, normalizes based on the uniform schema the first attribute name, and places the normalized first attribute name in a data structure, wherein the first attribute name is different from the normalized first attribute name,

wherein for a second attribute name of the second set of attribute names, the normalization module searches the database for a second normalized attribute name corresponding to the second attribute name, normalizes based on the uniform schema the second attribute name, and places the normalized second attribute name in the data structure, wherein the second attribute name is different from the normalized second attribute name; and

an indexing module executable by the one or more processors, wherein the indexing module indexes the normalized first and second attribute names in the data structure and outputs the indexes to index data files, and the index data files are accessible via a search API.

2. The system of claim 1, wherein the database includes a second set of mappings from a second attribute name of a cloud resource specific to the cloud to a third normalized attribute name based on the uniform schema,

wherein the data module identifies a set of cloud resources in the plurality of virtual datacenters, and responsive to the invoked APIs, receives a third set of attribute names of one or more cloud resources of a first subset of the set of cloud resources and a fourth set of attribute names of one or more cloud resources of a second subset of the set of cloud resources,

wherein the first subset of cloud resources is executable in the first cloud, and the second subset of cloud resources is executable in the second cloud, and wherein the third set of attribute names is compatible with the first cloud and incompatible with the second cloud, and the fourth set of attribute names is compatible with the second cloud and incompatible with the first cloud;

and

wherein for at least one attribute name of the third and fourth sets of attribute names, the normalization module searches the database for the third normalized attribute name corresponding to the at least one attribute name, normalizes based on the uniform schema the at least one attribute name, and places the normalized at least one attribute name in the data structure.

3. The system of claim 2, wherein the first cloud is at least one of a private cloud, public cloud, and hybrid cloud.

11. The system of claim 1, wherein the single API includes programming code that invokes multiple APIs across different cloud deployments.

4. A method of indexing heterogeneous resources, the system comprising:

identifying a set of physical resources in a plurality of virtual datacenters;

invoking a single application programming interface (API), wherein the invoked API causes invocation of a first API and a second API different from the first API;

responsive to the invoked first API, receiving a first set of attribute names of one or more physical resources of a first subset of the set of physical resources;

responsive to the invoked second API, receiving a second set of attribute names of one or more physical resources of a second subset of the set of physical resources;

wherein each virtual datacenter of the plurality of virtual datacenters is associated with a cloud consumer'"'"'s account, and wherein a first virtual datacenter includes one or more physical resources located in a first physical data center and one or more physical resources located in a second physical data center, and a second virtual datacenter includes one or more physical resources located in the first physical data center and one or more physical resources located in a third physical data center,

wherein the first subset of physical resources is executable in the first cloud, and the second subset of physical resources is executable in the second cloud, and wherein the first set of attribute names is compatible with the first cloud and incompatible with the second cloud, and the second set of attribute names is compatible with the second cloud and incompatible with the first cloud;

for a first attribute name of the first set of attribute names;

searching a database for a first normalized attribute name corresponding to the first attribute name, the database including a set of mappings from a particular attribute name of a physical resource specific to a cloud to a particular normalized attribute name based on a uniform schema;

normalizing based on the uniform schema the first attribute name; and

placing the normalized first attribute name in a data structure, wherein the first attribute name is different from the normalized first attribute name; and

for a second attribute name of the second set of attribute names;

searching the database for a second normalized attribute name corresponding to the second attribute name;

normalizing based on the uniform schema the second attribute name; and

placing the normalized second attribute name in the data structure, wherein the second attribute name is different from the normalized second name;

indexing the normalized first and second attribute names in the data structure; and

outputting the indexes to index data files, wherein the index data files are accessible via a search API.

5. The method of claim 4, further including:

identifying a set of cloud resources in the plurality of virtual datacenters;

responsive to the invoked single API, receiving a third set of attribute names of one or more cloud resources of a first subset of the set of cloud resources and a fourth set of attribute names of one or more cloud resources of a second subset of the set of cloud resources,

wherein the first subset of cloud resources is executable in the first cloud, and the second subset of cloud resources is executable in the second cloud, and wherein the third set of attribute names is compatible with the first cloud and incompatible with the second cloud, and the fourth set of attribute names is compatible with the second cloud and incompatible with the first cloud; and

for at least one attribute name of the third and fourth sets of attribute names;

searching the database for a normalized attribute name corresponding to the at least one attribute name, the database including a set of mappings from an attribute name of a cloud resource specific to a cloud to a normalized attribute name based on the uniform schema;

normalizing based on the uniform schema the at least one attribute name; and

placing the normalized at least one attribute name in the data structure.

6. The method of claim 4, further comprising:

dynamically creating the data structure based on the at least one attribute name.

7. The method of claim 4, wherein the placing the normalized at least one attribute name in a data structure includes placing the normalized at least one attribute name in a JavaScript Object Notation (JSON) formatted document.

8. The method of claim 4, further comprising:

determining an expected change frequency of a value of a received attribute name;

assigning a time-to-live to the received attribute name, the time-to-live being based on the expected change frequency;

identifying a first value of the received attribute name;

after the time-to-live has expired, identifying a second value of the received attribute name;

determining whether the first value is the same as the second value; and

when the first value is determined to not be the same as the second value, updating the first value with the second value.

12. The method of claim 4, wherein the plurality of virtual datacenters includes one or more physical resources located in a first physical data center and one or more physical resources located in a second physical data center.

13. The method of claim 4, wherein the single API includes programming code that invokes multiple APIs across different cloud deployments.

9. A non-transitory machine-readable medium comprising a first plurality of machine-readable instructions that when executed by one or more processors is adapted to cause the one or more processors to perform a method comprising:

identifying a set of physical resources in a plurality of virtual datacenters;

invoking a single application programming interface (API), wherein the invoked API causes invocation of a first API and a second API different from the first API;

responsive to the invoked first API, receiving a first set of attribute names of one or more physical resources of a first subset of the set of physical resources;

responsive to the invoked second API, receiving a second set of attribute names of one or more physical resources of a second subset of the set of physical resources,

wherein each virtual datacenter of the plurality of virtual datacenters is associated with a cloud consumer'"'"'s account, and wherein a first virtual datacenter includes one or more physical resources located in a first physical data center and one or more physical resources located in a second physical data center, and a second virtual datacenter includes one or more physical resources located in the first physical data center and one or more physical resources located in a third physical data center,

wherein the first subset of physical resources is executable in the first cloud, and the second subset of physical resources is executable in the second cloud, and wherein the first set of attribute names is compatible with the first cloud and incompatible with the second cloud, and the second set of attribute names is compatible with the second cloud and incompatible with the first cloud;

for a first attribute name of the first set of attribute names;

searching a database for a first normalized attribute name corresponding to the first attribute name, the database including a set of mappings from an attribute name of a physical resource specific to a cloud to a normalized attribute name based on a uniform schema;

normalizing based on the uniform schema the first attribute name; and

placing the normalized first attribute name in a data structure, wherein the first attribute name is different from the normalized first attribute name; and

for a second attribute name of the second set of attribute names;

searching the database for a second normalized attribute name corresponding to the second attribute name;

normalizing based on the uniform schema the second attribute name; and

placing the normalized second attribute name in the data structure, wherein the second attribute name is different from the normalized second attribute name; and

indexing the normalized first and second attribute names in the data structure.

10. The non-transitory machine-readable medium of claim 9, the non-transitory machine-readable medium comprising a second plurality of machine-readable instructions that when executed by one or more processors is adapted to cause the one or more processors to perform a method comprising:

identifying a set of cloud resources in the plurality of virtual datacenters, wherein the set of cloud resources span the first and second virtual datacenters;

responsive to the invoked one or more APIs, receiving a third set of attribute names of one or more cloud resources of a first subset of the set of cloud resources and a fourth set of attribute names of one or more cloud resources of a second subset of the set of cloud resources,

wherein the first subset of cloud resources is executable in the first cloud, and the second subset of cloud resources is executable in the second cloud, and wherein the third set of attribute names is compatible with the first cloud and incompatible with the second cloud, and the fourth set of attribute names is compatible with the second cloud and incompatible with the first cloud; and

for at least one attribute name of the third and fourth sets of attribute names;

searching the database for a normalized attribute name corresponding to the at least one attribute name, the database including a set of mappings from an attribute name of a cloud resource specific to a cloud to a normalized attribute name based on the uniform schema;

normalizing based on the uniform schema the at least one attribute name; and

placing the normalized at least one attribute name in the data structure.