Remote resource configuration mechanism

Abstract

The present disclosure relates to a remote resource configuration mechanism. A system for facilitating configuration of infrastructure resources is described. The system includes a plurality of on-premise infrastructure devices, each device including a plurality of infrastructure equipment and an on-premise infrastructure controller for controlling the plurality of infrastructure equipment. The system also includes a cloud service resource configuration manager communicatively coupled to each of the on-premise infrastructure controllers to configure each of the on-premise infrastructure devices via the respective on-premise infrastructure controller.

Description

BACKGROUND

[0001] Cloud services can refer to services that include infrastructure resources (computing resources, storage resources, networking resources, etc.) connected to each other and / or to a platform. Such infrastructure resources can be collectively referred to as“cloud resources.” As an example, a host (also referred to as a cloud service provider) can provide software as a service (SaaS) by hosting applications or other machine-readable instructions; infrastructure as a service (IaaS) by hosting equipment (servers, storage components, network components, etc.); or platform as a service (PaaS) by hosting computing platforms (operating systems, hardware, storage, etc.).

[0002] A hybrid cloud is a public cloud and / or private cloud environment at which a cloud service provider gives IaaS or PaaS. Services of the public cloud can be used to deploy applications. In other examples, a hybrid cloud can also give SaaS, such as in the example of a public cloud giving SaaS as a utility (e.g., according to a subscription or pay-per-use model). BRIEF DESCRIPTION OF DRAWINGS

[0003] In the following drawings similar elements are referred to by like reference numbers. Although the following drawings depict various examples, one or more implementations are not limited to the examples depicted in the drawings.

[0004] Figure 1 FIGURE 1 illustrates one embodiment of an infrastructure management system.

[0005] Figure 2 is a block diagram illustrating another embodiment of an infrastructure management system.

[0006] Figure 3 is a block diagram illustrating one embodiment of a configuration manager.

[0007] Figure 4 is a flow diagram illustrating one embodiment of a remote configuration process. DETAILED DESCRIPTION

[0008] Composable resource infrastructure (or composable infrastructure) encompasses the abstraction of on-premises infrastructure resources (e.g., compute, storage, and networking resources) from physical locations, such as data centers, to provide software management of the resources via a web-based interface. Thus, composable infrastructure underpins private cloud and hybrid cloud solutions by making data center resources easy to use as cloud services.

[0009] However, it is often necessary to configure (e.g., for connectivity to the data center and internal configuration of physical resources) the racks of the composable infrastructure (e.g., the composable racks) via a local deployment software controller that is physically located at the data center site. Such configuration can include configuration of one or more of the following: a set of physical data center network connections (or uplinks); ports on the composable racks to which the uplinks are connected; a level of port aggregation; a level of connection redundancy; configuration of virtual local area networks (VLANS) on each uplink; configuration of internet protocol (IP) subnet addresses available on each network; and connectivity of the frames / cages to a pool of storage disks such that some frames can access the pool while others cannot. Such configuration typically occurs after the composable racks have been physically wired and powered on. However, the problem is that an operator must physically access the data center site to implement the rack configuration described above in order to initialize the racks based on user requirements. This manual process is both time consuming, prone to human error, and costly.

[0010] In embodiments, a remote resource configuration mechanism is provided that supports remote configuration of a plurality of local deployment composable racks via a SaaS application. In such embodiments, the plurality of composable racks can be physically located in data centers around the world. In further embodiments, the SaaS application can remotely provide updates to the composable rack configuration (e.g., when frames / cages are added / activated). Thus, only the configuration of a secure and encrypted network path from the SaaS to the local deployment infrastructure controller needs to be provided at the physical site.

[0011] In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the present disclosure. It will be apparent, however, to one skilled in the art that the present disclosure can be practiced without some of these specific details. In other instances, well-known structures and devices are shown in block diagram form to avoid obscuring the underlying principles of the present disclosure.

[0012] Reference in the specification to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the disclosure. The appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment.

[0013] Throughout this document, terms like “logic,” “component,” “module,” “engine,” “model,” and the like can be referenced interchangeably and include, by way of example, software, hardware, and / or any combination of software and hardware, such as firmware. Moreover, any use of any trade name, word(s), term(s), phrase(s), slogan(s), or trademark(s) in this document is for descriptive purposes only and does not constitute an intent to invoke the service mark, trademark, or brand ownership rights of the applicant or publisher, respectively.

[0014] It is contemplated that any number and type of components can be added and / or removed to facilitate various embodiments, including adding, removing, and / or enhancing certain features. For brevity, clarity, and ease of understanding, many standard and / or known components, such as those of a computing device, are not shown or discussed here. It is contemplated that embodiments as described herein are not limited to any particular technology, topology, system, architecture, and / or standard, and are dynamic enough to adopt and adapt to any future changes.

[0015] Figure 1 One embodiment of an infrastructure management system 100 is illustrated, having a computing device 120 that employs a resource configuration manager (or configuration manager) 110. In one embodiment, the configuration manager 110 is a remote configuration service hosted within a SaaS that is provided to manage configurations and updates to each of a plurality of locally deployed infrastructure resource devices (e.g., racks) located in different data centers. In further embodiments, the configuration manager 110 is enabled by a client on behalf of a plurality of client (or customer) organizations to configure infrastructure resources within the devices.

[0016] As Figure 1 As shown in the middle, the computing device 120 includes a host server computer that serves as a host for employing the configuration manager 110, which provides a platform for configuring infrastructure resources. The computing device 120 can include, but is not limited to, a server computer (e.g., a cloud server computer, etc.), a desktop computer, a cluster-based computer, a set-top box (e.g., an Internet-based cable television set-top box, etc.), and the like. The computing device 120 includes an operating system (“OS”) 106 that serves as an interface between one or more hardware / physical resources of the computing device 120 and one or more client devices 117, and the like. The computing device 120 further includes a processor(s) 102, a memory 104, an input / output (“I / O”) source 108, such as a touchscreen, touch panel, touchpad, virtual or regular keyboard, virtual or regular mouse, and the like. In one embodiment, the configuration manager 110 can be executed by a separate processor application-specific integrated circuit (ASIC) other than the processor 102. In further embodiments, the configuration manager 110 can act out-of-band, and can be on a separate power rail from the processor 102. Thus, the configuration manager 110 can operate in the event that the processor 102 is powered off.

[0017] In one embodiment, the host organization 101 can further employ a production environment that is communicatively interfaced by the host organization 101 with client devices 117 at the customer organizations 115. The client devices 117 can include, but are not limited to, customer organization-based server computers, desktop computers, laptop computers, mobile computing devices such as smartphones, tablet computers, personal digital assistants, e-readers, media internet devices, smart televisions, television platforms, wearable devices (e.g., eyeglasses, watches, bracelets, smart cards, jewelry, clothing items, etc.), media players, global positioning system-based navigation systems, cable set-top boxes, and the like.

[0018] In one embodiment, the illustrated database(s) 140 store, but are not limited to, information and underlying database records with customer and user data therein to process data on behalf of the customer organizations 115. In some embodiments, the host organization 101 receives inputs and other requests from the plurality of customer organizations 115 over one or more networks 135; for example, incoming data or other inputs can be received from the customer organizations 115 for processing using the database system 140.

[0019] In one embodiment, each customer organization 115 is an entity selected from the group consisting of: a separate and distinct remote organization, a group of organizations within the host organization 101, a business partner of the host organization 101, a customer organization 115 that subscribes to cloud computing services provided by the host organization 101, and the like.

[0020] In one embodiment, requests are received at a web server within the host organization 101, or are submitted to a web server within the host organization 101. The host organization 101 can receive various requests to be processed by the host organization 101. For example, incoming requests received at a web server can specify that a service from the host organization 101 is to be provided. Further, the host organization 101 can implement a request interface via the web server or as a standalone interface to receive request packets or other requests from the client devices 117. The request interface can further support the return of response packets or other replies and responses in an outgoing direction from the host organization 101 to one or more client devices 117.

[0021] In one embodiment, the computing device 120 can include a server computer that can further communicate with one or more databases or repositories, such as the database(s) 140, located locally or remotely, through one or more networks, such as the network(s) 135 (e.g., a cloud network, the Internet, a proximity network, an intranet, the Internet of Things (“IoT”), the Cloud of Things (“CoT”), etc.). It is also shown that the computing device 120 communicates with any number and type of other computing devices, such as the client computing device 117, through one or more networks, such as the network(s) 135.

[0022] In one embodiment, the host organization 101 provides a service to configure resources within the data centers 121A-121N. The data centers 121A-121N represent separate infrastructure resource providers that offer a service to provide hardware resources (e.g., compute, storage, network elements, etc.) or software resources. In further embodiments, one or more of the providers 121A-121N can provide virtualization of their resources as a virtualization infrastructure for virtualization of their resources. In this embodiment, one or more of the computing device 120 resources and / or the physical infrastructure resources provided by the providers 121A-121N can be configured as one or more points of development (PODs) (or instance machines), where an instance machine (or instance) includes a cluster of infrastructure (e.g., compute, storage, software, network equipment, etc.) that operates together.

[0023] According to one embodiment, each of the provider data centers 121A-121N implements one or more on-premise infrastructure controllers 130 to control its respective resources. In this embodiment, each infrastructure controller 130 controls on-premise infrastructure appliances that provide access to infrastructure equipment within the appliance or to one or more infrastructure elements (e.g., instances of managed infrastructure) of its respective infrastructure resources. In one embodiment, each infrastructure controller 130 includes software-defined network (SDN) controllers, such as The infrastructure management system’s SDN controllers provide on-premise infrastructure management of the physical infrastructure resources. However, other embodiments can implement different infrastructure management systems.

[0024] Figure 2 is a block diagram illustrating another embodiment of an infrastructure management system 100. As Figure 2As shown, the infrastructure management system 100 may include the management of resources within a data center. For example, the infrastructure management system 100 includes a data center 250A having racks 220A and 220B. Each rack includes an infrastructure controller 221 and resources 251. In one embodiment, each infrastructure controller 221 manages its corresponding resources 251. According to one embodiment, a configuration manager 210 is communicatively coupled to each infrastructure controller 221. For example, the configuration manager 210 is a cloud server (e.g., such as...). Figure 1 (As discussed in the document), it configures all resources within each data center 250 (e.g., data centers 250A and 250B) via infrastructure controllers 221A-221D.

[0025] Figure 3 An example of configuration manager 210 is illustrated. Figure 3 As shown, configuration manager 210 includes application programming interface (API) 210, user interface 320, and connection manager 330. According to one embodiment, API 210 includes a representative state transition (REST) ​​interface that facilitates communication with infrastructure controller 221 via an interconnected network such as the Internet. In another embodiment, API 210 is communicatively coupled to each infrastructure controller 221 via a secure tunneling protocol to enable communication over a private network of the network.

[0026] Prior to communication with infrastructure controller 221, devices within data center 250 are physically connected to and powered on one or more networks within data center 250. Additionally, infrastructure controller 221, which manages the devices, is activated. According to one embodiment, a data center user (e.g., at client device 117) can log in to configuration manager 210 via user interface 320 and select the data center 250 to access. The user can then implement user interface 320 to request access to infrastructure controller 221 at data center 250. In this embodiment, the request may include an address and user credentials associated with a specific infrastructure controller 221. API 310 receives the address and credentials and uses this information to establish a connection with infrastructure controller 221 via a pre-existing secure tunnel.

[0027] In further embodiments, the user interface 320 prompts the user for one or more configuration questions related to various device configuration parameters that are to be requested to configure the device. In such embodiments, the configuration parameters can include information related to a set of uplink and aggregation / redundancy configurations, VLANs, IP addresses, storage configurations, etc. In response to receiving the configuration parameters as a configuration request (e.g., via answers to the questions), a request is made to the connection manager 330 to configure the device according to the configuration parameters. In one embodiment, the connection manager 330 is a controller API that is configured to control the infrastructure controller 221.

[0028] In response, the connection manager 330 performs a discovery of the device inventory (e.g., available infrastructure resources) to determine whether the requested configuration is compatible with the infrastructure resources available at the device. In one embodiment, the infrastructure controller 221 provides an API that allows the configuration manager 210 to remotely interrogate and determine the physical makeup of the device (e.g., number of enclosures / frames, number of hardware servers (computes) per enclosure / frame, number of disk enclosures (capacity information), networking information (number of uplinks, number of interconnections to compute resources), etc.). In another embodiment, the configuration manager 210 can perform an initial interrogation and discovery prior to prompting the user for configuration parameters. In response to determining that the requested configuration is compatible, the connection manager 330 facilitates the application of the requested configuration at the device via the associated infrastructure controller 221 (e.g., via the infrastructure controller 221 API).

[0029] In one embodiment, the configuration includes a configuration of uplinks, assignment of uplinks to frames / enclosures, and configuration of connectivity between frames / enclosures and storage arrays. Subsequently, the device is ready to apply infrastructure workloads. In response to determining that the requested configuration is not compatible, the user interface 320 sends a message to the user indicating that the configuration request is not compatible with the infrastructure resources available at the device. In one embodiment, the user is again prompted for configuration questions related to various device configuration parameters.

[0030] Figure 4is a flowchart illustrating one embodiment of a process to illustrate the remote configuration infrastructure controller 221. At processing block 410, a data center selection is received at the configuration manager (e.g., via a user interface). Subsequently, at processing block 420, a request to access the infrastructure controller 221 is received. As described above, the request can include an address associated with the infrastructure controller at the data center and user credentials. At processing block 430, the credentials are used to establish a connection between the configuration manager and the infrastructure controller. As described above, the connection is established via a pre-existing secure tunnel. At processing block 440, configuration questions are sent to the user. As previously mentioned, the configuration questions include questions related to various device configuration parameters (e.g., related to a set of uplink and aggregation / redundancy configuration, VLAN, IP address, storage configuration, etc.) that are to be implemented to configure the device.

[0031] At processing block 450, a configuration request including configuration parameters is received in response to the configuration questions. At processing block 460, a discovery of available infrastructure resources is performed to determine whether the requested configuration is compatible with the available infrastructure resources at the device. At decision block 470, a determination is made as to whether the requested configuration is compatible with the available infrastructure resources. In response to a determination that the requested configuration is compatible, at processing block 480, the requested configuration is applied at the device. As a result, the device is ready to apply the infrastructure workload. Otherwise, in response to a determination that the requested configuration is not compatible, at processing block 490, a message is sent to the user indicating that the configuration request is not compatible with the available infrastructure resources.

[0032] The above-described process can also be implemented to remotely reconfigure the device. For example, the rack configuration can be updated (e.g., when a rack and / or enclosure is added / activated). As a result, the implementation of the configuration manager results in lower costs due to a reduced number of visits to the customer site.

[0033] Embodiments can be implemented as any or a combination of: one or more microchips or integrated circuits interconnected using a motherboard, hardwired logic, software stored by a memory device and executed by a microprocessor, firmware, an application-specific integrated circuit (ASIC), and / or a field-programmable gate array (FPGA). As an example, the term "logic" can include software or hardware and / or a combination of software and hardware.

[0034] For example, embodiments can be provided, as a computer program product, which can include one or more machine-readable media having stored thereon instructions that, when executed by one or more machines such as a computer, network of computers, or other electronic devices, can result in the one or more machines carrying out operations according to embodiments described herein. A machine- readable medium can include, without limitation, floppy diskettes, optical disks, CD-ROMs (Compact Disc-Read Only Memories), and magneto-optical disks, ROMs, RAMs, EPROMs (Erasable Programmable Read Only Memories), EEPROMs (Electrically Erasable Programmable Read Only Memories), magnetic or optical cards, flash memory, or other type of media / machine-readable medium suitable for storing machine-executable instructions.

[0035] Moreover, embodiments can be downloaded as a computer program product, wherein the program can be transferred from a remote computer (e.g., a server) to a requesting computer (e.g., a client) by way of one or more data signals embodied in and / or modulated by a carrier wave or other propagation medium via a communication link (e.g., a modem and / or network connection).

[0036] The drawings and preceding description give examples of embodiments. Those skilled in the art will understand that one or more of the described elements can well be combined into a single function element. Alternatively, certain elements can be split into multiple function elements. Elements from one embodiment can be added to another embodiment. For example, the order of processes described herein can be changed, and not all processes are necessarily performed. Also, actions can be performed in parallel whether or not that is explicitly stated. The scope of embodiments is limited only by the terms of the claims, and nothing else. Numerous modifications, such as differences in structure, size, and materials used, are possible without departing from the scope of the embodiments. The scope of the embodiments is at least as broad as the scope of the claims.

Claims

1. A system for facilitating the allocation of infrastructure resources, comprising: Multiple locally deployed racks, each of the multiple locally deployed racks including an infrastructure controller, and each locally deployed rack including a set of composable infrastructure resources managed by a respective infrastructure controller in the infrastructure controller; The cloud service resource configuration manager, communicatively coupled to the infrastructure controller, is used to: The cloud service resource configuration manager receives a request from the client device to access a first infrastructure controller within the infrastructure controller. The request includes an address associated with the first infrastructure controller. Use the address in the request to establish a connection between the cloud service resource configuration manager and the first infrastructure controller. A configuration request is generated, comprising configuration information regarding the assignment of uplinks to a frame or shell of a first locally deployed rack, the first locally deployed rack including a first infrastructure controller with which the cloud service resource configuration manager has established a connection, wherein the uplink assignment includes configuration of connectivity between the frame or shell and the storage array. Based on the configuration information, it is determined whether the requested configuration is compatible with the set of composable infrastructure resources of the first locally deployed rack, and Based on the determination that the requested configuration is compatible with the set of composable infrastructure resources of the first locally deployed rack, the set of composable infrastructure resources of the first locally deployed rack is configured according to the configuration information.

2. The system of claim 1, wherein the request to access the first infrastructure controller further includes credentials, and wherein the cloud service resource configuration manager uses the credentials to establish a connection with the first infrastructure controller.

3. The system of claim 1, wherein configuring the set of composable infrastructure resources includes configuring a virtual local area network on the uplink.

4. The system of claim 1, wherein the cloud service resource configuration manager includes an application programming interface (API) to facilitate communication with the plurality of locally deployed racks.

5. The system according to claim 1, wherein the cloud service resource configuration manager is used to: This causes the user interface to be rendered, and The decision to include the configuration information in the configuration request is based on information obtained from the user interface.

6. The system according to claim 5, wherein the cloud service resource configuration manager is used to: The user interface prompts the user with one or more configuration questions. The information obtained from the user interface is based on configuration parameters provided by the user in response to one or more configuration questions in the user interface.

7. The system according to claim 6, wherein the cloud service resource configuration manager is used to receive the user's login at the user interface.

8. The system of claim 1, wherein the cloud service resource configuration manager is used to access the application programming interface of the first infrastructure controller to discover a list of the set of composable infrastructure resources of the first locally deployed rack.

9. The system according to claim 1, wherein the configuration information in the configuration request includes configuration parameters, and the configuration parameters include one or more of the following: Virtual Local Area Network (VLAN) information, Internet Protocol (IP) address, or storage configuration.

10. A non-transitory machine-readable medium storing instructions for a configuration manager, said instructions, when executed, causing one or more processors to: At the configuration manager, a request to access a first infrastructure controller among a plurality of infrastructure controllers is received from a client computing device via a network. The plurality of infrastructure controllers are portions of a respective local deployment rack. The request includes an address associated with the first infrastructure controller, and each local deployment rack includes a set of composable infrastructure resources managed by a respective infrastructure controller among the plurality of infrastructure controllers. Using the address in the request, establish a connection between the configuration manager and the first infrastructure controller; A configuration request is generated, the configuration request including configuration information regarding the assignment of uplinks to a frame or enclosure of a first locally deployed rack, the first locally deployed rack including a first infrastructure controller with which the configuration manager has established a connection, wherein the assignment of the uplinks includes configuration of connectivity between the frame or enclosure and the storage array; Based on the configuration information, it is determined whether the requested configuration is compatible with the set of composable infrastructure resources of the first locally deployed rack, and Based on the determination that the requested configuration is compatible with the set of composable infrastructure resources of the first locally deployed rack, the set of composable infrastructure resources of the first locally deployed rack is configured according to the configuration information.

11. The non-transitory machine-readable medium of claim 10, wherein the request to access the first infrastructure controller further includes credentials, and wherein the instructions, when executed, cause the one or more processors to: use the credentials to establish the connection between the configuration manager and the first infrastructure controller.

12. The non-transitory machine-readable medium of claim 10, wherein the configuration information in the configuration request includes configuration parameters, the configuration parameters including one or more of the following: Virtual Local Area Network (VLAN) information, Internet Protocol (IP) address, or storage configuration.

13. The non-transitory machine-readable medium of claim 10, wherein the instructions, when executed, cause the one or more processors to: The configuration manager causes the rendering of the user interface, and The decision to include the configuration information in the configuration request is based on information obtained from the user interface.

14. The non-transitory machine-readable medium of claim 13, wherein the instructions, when executed, cause the one or more processors to: The user interface prompts the user with one or more configuration questions, wherein the information obtained from the user interface at the configuration manager is based on configuration parameters provided by the user in response to the one or more configuration questions in the user interface.

15. The non-transitory machine-readable medium of claim 13, wherein the instructions, when executed, cause the one or more processors to: The user login to the configuration manager is received at the user interface.

16. A method for facilitating infrastructure management, comprising: At the configuration manager of the computing system, a request to access a first infrastructure controller among a plurality of infrastructure controllers is received from a client computing device via a network. The plurality of infrastructure controllers are portions of a respective local deployment rack. The request includes an address associated with the first infrastructure controller, and each local deployment rack includes a set of composable infrastructure resources managed by the respective infrastructure controller among the plurality of infrastructure controllers. The configuration manager uses the address in the request to establish a connection between the configuration manager and the first infrastructure controller; The configuration manager generates a configuration request, which includes configuration information regarding the assignment of uplinks to a frame or enclosure of a first local deployment rack, the first local deployment rack including a first infrastructure controller with which the configuration manager has established a connection, wherein the assignment of the uplinks includes configuration of connectivity between the frame or enclosure and the storage array. as well as The configuration manager determines, based on the configuration information, whether the requested configuration is compatible with the set of composable infrastructure resources of the first locally deployed rack, and Based on the determination that the requested configuration is compatible with the set of composable infrastructure resources of the first locally deployed rack, the configuration manager configures the set of composable infrastructure resources of the first locally deployed rack according to the configuration information.

17. The method of claim 16, wherein the request to access the first infrastructure controller further includes credentials, and the method further includes: The configuration manager uses the credentials to establish the connection with the first infrastructure controller.

18. The method of claim 16, wherein the configuration information of the configuration request includes configuration parameters, and the configuration parameters include virtual local area network (VLAN) information and storage configuration.

19. The method of claim 16, further comprising: The configuration manager causes the rendering of the user interface, and The configuration manager determines whether to include the configuration information in the configuration request based on information obtained from the user interface.

Images