Serverless methodology for system management of heterogeneous infrastructure
Disclosed methods and systems for implementing serverless management of platform resources maintain a function-as-a-service (FaaS) mapping database associating a resource and management function combination with a locator identifying a container image for implementing management interactions required to perform the management function. When a FaaS request indicating a function-resource combination is detected, the applicable locator is retrieved from the mapping database and the corresponding container image is deployed. Each resource may correspond to a specific version of a specific make or model, e.g., a server model and a firmware version. API, protocol, and messaging specifics for performing the function on the resource are embedded in each container image. Thus, the container image for an inventory operation on a server with a first version of firmware may execute SOAP-based messaging while the image for the same operation on the same server model provisioned with a second firmware version may invoke a RESTful API.
1 . A method, comprising:
maintaining a function as a service (FaaS) mapping database comprising a plurality of entries, wherein each entry associates a resource and a management function with a locator identifying a container image configured to implement management exchanges required to perform the management function on the resource;
responsive to detecting a FaaS request indicating a management function and a resource, obtaining from the FaaS mapping database, the locator for the entry corresponding to the management function and the resource; and
deploying the container image identified by the locator to complete the FaaS request
wherein each resource is associated with a model and a version and wherein each entry in the FaaS mapping database corresponds to a particular model and version, and further wherein the model is provisioned with firmware and wherein the version indicates a version of the firmware, and further wherein the FaaS mapping database includes:
a first entry corresponding to a management function for the model provisioned with a first version of the firmware; and
a second entry corresponding to the management function for the model provisioned with a second version of the firmware.
2 . The method of claim 1 , the management exchanges include management exchanges in compliance with at least one management API selected from:
a representational transfer state (REST) API; and
a simple object access protocol (SOAP) API.
3 . The method of claim 1 , wherein the FaaS mapping database includes:
a first entry corresponding to a management function for a first model provisioned with a first version of the firmware; and
a second entry corresponding to the management function for a second model provisioned with the first version of the firmware;
wherein the locators associated with the first and second entries identify the same container image.
4 . The method of claim 1 , wherein the FaaS mapping database includes:
a first entry corresponding to a management function for a first version of a particular model; and
a second entry corresponding to the management function for a second version of the particular model.
5 . The method of claim 4 , wherein the container image corresponding to the first entry is configured to implement different management exchanges than the container image corresponding to the second entry.
6 . The method of claim 4 , wherein the container image corresponding to the first entry is configured to implement management exchanges in accordance with a first management API and the container image for the second entry is configured to implement management exchanges in accordance with a second management API.
7 . The method of claim 1 , wherein deploying the container image includes provisioning a management component of the resource with the container image, wherein the management component is selected from:
an original equipment manufacturer management controller;
an in-band network switch; and
a third party management controller.
8 . An information handling system, comprising:
a central processing unit (CPU); and
a computer readable memory, accessible to the CPU, including processor executable instructions that, when executed by the CPU, cause the system to perform operations including:
maintaining a function as a service (FaaS) mapping database comprising a plurality of entries, wherein each entry associates a resource and a management function with a locator identifying a container image configured to implement management exchanges required to perform the management function on the resource;
responsive to detecting a FaaS request indicating a management function and a resource, obtaining from the FaaS mapping database, the locator for the entry corresponding to the management function and the resource; and
deploying the container image identified by the locator to complete the FaaS request;
wherein each resource is associated with a model and a version and wherein each entry in the FaaS mapping database corresponds to a particular model and version, and further wherein the model is provisioned with firmware and wherein the version indicates a version of the firmware, and further wherein the FaaS mapping database includes:
a first entry corresponding to a management function for a first model provisioned with a first version of the firmware; and
a second entry corresponding to the management function for a second model provisioned with the first version of the firmware;
wherein the locators associated with the first and second entries identify the same container image.
9 . The information handling system of claim 8 , the management exchanges include management exchanges in compliance with at least one management API selected from:
a representational transfer state (REST) API; and
a simple object access protocol (SOAP) API.
10 . The information handling system of claim 8 , wherein the FaaS mapping database includes:
a first entry corresponding to a management function for the model provisioned with a first version of the firmware; and
a second entry corresponding to the management function for the model provisioned with a second version of the firmware.
11 . The information handling system of claim 8 , wherein the FaaS mapping database includes:
a first entry corresponding to a management function for a first version of a particular model; and
a second entry corresponding to the management function for a second version of the particular model.
12 . The information handling system of claim 11 , wherein the container image corresponding to the first entry is configured to implement different management exchanges than the container image corresponding to the second entry.
13 . The information handling system of claim 11 , wherein the container image corresponding to the first entry is configured to implement management exchanges in accordance with a first management API and the container image for the second entry is configured to implement management exchanges in accordance with a second management API.
14 . The information handling system of claim 8 , wherein deploying the container image includes provisioning a management component of the resource with the container image, wherein the management component is selected from:
an original equipment manufacturer management controller;
an in-band network switch; and
a third party management controller.