Managing hyper-converged infrastructure (HCI) device nodes and clusters with DHCP-based resources

Abstract

A disclosed method can assign two static IP addresses to each of one or more hyper-converged infrastructure nodes with a DHCP module. The two static IP addresses can include an out-of-band IP address for a baseboard management controller (BMC) network interface of an OOB management network, and an internal management IP address for a network interface associated with an internal management network. The disclosed method can then, for each of the one or more nodes, access the BMC at the OOB IP address to invoke a BMC tool to retrieve cluster configuration information for each node. A dashboard user interface can then be generated and displayed based on the configuration retrieved for each node. The cluster configuration information can indicate whether the node is a cluster node including a node assigned to a cluster or a free node including a node not assigned to a cluster.

Description

Technical Field

[0001] This disclosure relates to information processing systems, and more specifically, to information processing system devices with hyperconverged infrastructure. Background Technology

[0002] As the value and use of information continue to increase, individuals and businesses are seeking alternative ways to process and store information. One option available to users is an information processing system. Information processing systems typically process, compile, store, and / or communicate information or data for business, personal, or other purposes, thereby allowing users to leverage the value of information. Because technologies and information processing needs and requirements vary between different users or applications, information processing systems can also vary in the following aspects: what information is processed, how it is processed, how much information is processed, stored, or communicated, and how quickly and efficiently it can be processed, stored, or communicated. Variations in information processing systems allow them to be general-purpose or configured for specific users or purposes (such as financial transaction processing, flight booking, corporate data storage, or global communications). Furthermore, information processing systems can include various hardware and software components that can be configured to process, store, and communicate information, and can include one or more computer systems, data storage systems, and networking systems.

[0003] Information processing systems can be implemented using hyperconverged infrastructure (HCI) that features virtualized computing, storage, and networking resources, as well as centralized management. Examples of commercially available HCI designs include Dell Technologies' VxRail series of HCI appliances. HCI appliances can support various node and cluster configurations. In some cases, the level of virtualization and configuration complexity may obscure the underlying architectural aspects of an HCI solution. Summary of the Invention

[0004] The methods and systems disclosed herein can use a Dynamic Host Configuration Protocol (DHCP) module to assign two static IP addresses to each of one or more hyperconverged infrastructure nodes within a set of nodes associated with an information processing system. The two static IP addresses may include an OOB IP address for a Baseboard Management Controller (BMC) network interface for an out-of-band (OOB) management network, and an internal management IP address for a network interface associated with an internal management network. The disclosed method can then, for each of the one or more nodes, access the BMC at the OOB IP address to invoke BMC tools to retrieve cluster configuration information for each node. A user interface (referred to herein as a dashboard user interface) can then be generated and displayed based on the configuration retrieved for each node. The cluster configuration information may include information indicating whether the node is a cluster node including nodes assigned to the cluster or a free node including nodes not assigned to the cluster. The cluster configuration information may also include, for each free node, information indicating whether the free node is a new node including previously unconfigured nodes or a dirty node including previously configured nodes. The cluster configuration may also indicate, for each cluster node, the cluster management instance associated with the cluster node.

[0005] In some implementations, the cluster configuration information may include a cloud infrastructure window indicating nodes within a VMware cloud infrastructure (VCF). The VCF may include a management domain and one or more workload domains. The cloud infrastructure window may indicate nodes within the management domain and nodes within each of the one or more workload domains.

[0006] The cluster management engine API can be invoked to determine cluster membership information indicating other cluster nodes associated with the cluster management engine instance, wherein the cluster configuration information includes the cluster membership information. The cluster configuration display may include a free node window listing the free nodes and a cluster window identifying one or more clusters. Each cluster can be identified using a list of nodes belonging to that cluster. The configuration information may include version information indicating the version of the HCI device. The tool allows administrators and other users to initiate re-imaging requests to re-image any dirty nodes. Hardware information indicating the hardware implemented in the node can be obtained from an agent executing on the hypervisor associated with the node. The cluster configuration user interface may group or otherwise arrange the display of one or more free node groups, wherein the nodes in the free node groups are implemented with similar hardware.

[0007] In response to user input selecting two or more new nodes, a new cluster encompassing each of the two or more new nodes can be created. In response to user input specifying a particular node, that particular node can be configured as the master node of the cluster. The cluster management engine for that particular node can be enabled, while the cluster management engines for the other nodes in the cluster can be disabled.

[0008] The configuration tool allows user input to drag and drop new nodes into the cluster list, thereby adding the new nodes to the cluster list. Conversely, the tool allows dragging and dropping cluster nodes into a free pool to release the nodes from the cluster.

[0009] The technical advantages of this disclosure will be apparent to those skilled in the art from the accompanying drawings, description, and claims included herein. The objectives and advantages of the embodiments will be achieved and realized, at least by means of the elements, features, and combinations particularly pointed out in the claims.

[0010] It will be understood that the foregoing general description and the following detailed description are exemplary and illustrative, and not limiting of the claims set forth in this disclosure. Attached Figure Description

[0011] A more complete understanding of the embodiments and advantages of the invention can be obtained from the following description taken in conjunction with the accompanying drawings, in which like reference numerals indicate like features, and wherein:

[0012] Figure 1 A block diagram of the information processing system disclosed herein, including node configuration tools, is shown.

[0013] Figure 2 An exemplary dashboard user interface for displaying node configuration information is shown;

[0014] Figure 3 This shows the generation Figure 2 A flowchart of the methods for using the dashboard user interface; and

[0015] Figure 4 Is it suitable for and Figures 1 to 3 A block diagram of an information processing system that combines the methods and systems disclosed herein. Detailed Implementation

[0016] By reference Figures 1 to 4 The exemplary embodiments and their advantages are best understood, wherein, unless otherwise expressly indicated, similar reference numerals are used to indicate similar and corresponding parts.

[0017] For the purposes of this disclosure, an information processing system may include any tool or set of tools operable to compute, classify, process, transmit, receive, retrieve, generate, switch, store, display, indicate, detect, record, reproduce, dispose of, or utilize any form of information, intelligence, or data for commercial, scientific, control, entertainment, or other purposes. For example, an information processing system may be a personal computer, a personal digital assistant (PDA), a consumer electronic device, a network storage device, or any other suitable device, and may vary in size, shape, performance, functionality, and price. An information processing system may include memory, one or more processing resources such as a central processing unit (“CPU”), a microcontroller, or hardware or software control logic. Additional components of the information processing system may include one or more storage devices, one or more communication ports for communicating with external devices, and various input / output (“I / O”) devices such as a keyboard, mouse, and video display. The information processing system may also include one or more buses operable to transmit communication between various hardware components.

[0018] Additionally, the information processing system may include firmware for controlling and / or communicating with, for example, hard disk drives, network circuitry, memory devices, I / O devices, and other peripheral devices. For example, a management program and / or other components may include firmware. As used in this disclosure, firmware includes software embedded in an information processing system component for performing predefined tasks. Firmware is typically stored in non-volatile memory or memory in which stored data is not lost upon power failure. In some embodiments, firmware associated with an information processing system component is stored in non-volatile memory accessible to one or more information processing system components. In the same or alternative embodiments, firmware associated with an information processing system component is stored in non-volatile memory dedicated to and including as a part of that component.

[0019] For the purposes of this disclosure, computer-readable media may include any tool or set of tools that can retain data and / or instructions for a period of time. Computer-readable media may include, but is not limited to: storage media such as direct access storage devices (e.g., hard disk drives or floppy disks), sequential access storage devices (e.g., magnetic tape drives), optical discs, CD-ROMs, DVDs, random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), and / or flash memory; and communication media such as wires, optical fibers, microwaves, radio waves, and other electromagnetic and / or optical carrier waves; and / or any combination of the foregoing.

[0020] For the purposes of this disclosure, "information processing resources" can be broadly defined to refer to any component system, apparatus, or device of an information processing system, including but not limited to: processors, service processors, basic input / output systems (BIOS), buses, memory, I / O devices and / or interfaces, storage resources, network interfaces, motherboards, and / or any other components and / or elements of the information processing system.

[0021] In the following description, details are illustrated by example to facilitate discussion of the disclosed subject matter. However, those skilled in the art will understand that the disclosed embodiments are exemplary and not a detailed account of all possible embodiments.

[0022] Figure 1 An information processing system 100 based on the disclosed teachings is shown. Figure 1 The information processing system 100 shown includes information processing resources, which are referred to herein as hyperconverged infrastructure (HCI) nodes or more simply as node 110, wherein Figure 1 Three examples, 110-1, 110-2, and 110-3, are shown. Other implementations may include more or fewer nodes 110.

[0023] Each node 110 can be implemented using rack-mounted server-class hardware and a tightly integrated set of software components that support virtualized compute, storage, and network resources with advanced management capabilities. Virtualization abstracts and pools the node's resources and dynamically allocates them to applications running in virtual machines or containers. Each node 110 can be configured as an HCI device. Suitable for use in... Figure 1 Examples of commercially distributed HCI devices used within the information processing system 100 depicted include any of Dell Technologies' VxRail series of HCI devices. In at least one embodiment, each node 110 corresponds to a single-node, 1U, or 2U rack-mounted HCI device. In some embodiments, the node 110 is housed within a single rack-mounted cabinet. In other embodiments, the node 110 may occupy slots in two or more cabinets.

[0024] Node 110 is shown within a management domain 120 associated with management module 125, which provides a centralized platform for managing virtual infrastructure within management domain 120. In some implementations, configuration management module 125 may be implemented using vCenter server software from VMware enhanced with a VxRail Manager plugin from Dell Technologies.

[0025] According to the publicly available teachings, Figure 1The information processing system also includes a configuration tool 130. The configuration tool 130 can utilize out-of-band management resources within each node to retrieve configuration information from each node 110 and generate a user interface (referred to herein as an HCI dashboard) indicating node and cluster configuration information for all nodes 110 within the management domain 120. The configuration tool 130 may support additional configuration functions, as described in more detail below.

[0026] Configuration tool 130 can be implemented as an HTTP server including an embedded Dynamic Host Configuration Protocol (DHCP) server 127. Two network interfaces are assigned to... Figure 1 The configuration tool 130 is depicted in the diagram. An internal management structure 132 connects the configuration tool 130 to the management module 125, while an out-of-band network interface 134 connects to a remote out-of-band management network 140. In at least some embodiments, the configuration tool 130 has access to information indicating account information to connect to out-of-band management resources and virtualization hosts.

[0027] When configuration tool 130 is launched, it assigns internal management IP addresses to internal management network interfaces 112 on each node 110 and assigns OOB IP addresses to OOB network interfaces 114. These network interfaces may correspond to baseboard management controllers, remote access controllers (such as iDRAC from Dell Technologies), etc., on each node 110. If management domain 120 includes existing nodes that already have assigned IP addresses, the administrator can manually provide the IP address information to configuration tool 130.

[0028] Configuration tool 130 has access to a list of IP addresses assigned by DHCP server 127. Based on this list, configuration tool 130 can determine which IP addresses are associated with OOB resources on each node. Once the OOB IP addresses are known, configuration tool 130 can use existing OOB management services or tools for node configuration information. For OOB management resources in an implementation of an Integrated Dell Remote Access Controller (iDRAC), as a non-limiting example, configuration tool 130 may utilize the ipmitool or racadm command system.

[0029] The node configuration information obtained by configuration tool 130 may include information indicating which nodes have been assigned to the multi-node cluster and which nodes are "free" (i.e., not assigned to the cluster).

[0030] For nodes that have already been added to the cluster, the node configuration information may include information that identifies the nodes in the cluster and the corresponding HCI management software.

[0031] For free nodes, i.e., nodes that have not yet been assigned to any cluster, the node configuration information includes “clean / dirty” information indicating whether the node was previously configured and therefore needs to be re-imagined or was not previously configured and therefore available for use.

[0032] In some implementations, the node configuration dashboard can group clean and dirty nodes together within the free nodes section of the dashboard. In some implementations, free nodes (both clean and dirty) can be grouped according to the version of the HCI management software used to manage the nodes.

[0033] Node configuration tool 130 may also include functionality for initiating re-imaging of dirty nodes, and in some implementations, this functionality is available directly from the dashboard homepage (discussed below). Figure 2 (As shown in the image) call.

[0034] At least some implementations of the node configuration tool can support more advanced configuration capabilities. As a non-limiting example, an implementation of node configuration tool 130 can communicate with an agent running on those nodes to identify the hardware resources associated with each node. Based on the received hardware information, node configuration tool 130 can define class hardware groups of nodes, where each node in the group shares the same or substantially similar hardware.

[0035] Node configuration tool 130 also enables administrators to identify clusters by defining names for each cluster. In at least some implementations, node configuration tool 130 may also instruct administrators to select ready-state nodes (i.e., clean nodes not yet assigned to a cluster) to create a new cluster and initiate an initialization process to initialize the new cluster. In at least some implementations, this functionality can be further extended by calling the HCI management API to perform multiple cluster initializations. In an implementation using a VxRail device for node 110, this functionality is implemented as an example using the VxRail initialization API.

[0036] In some implementations, when multiple nodes are added to different clusters, the administrator can use the node configuration tool 130 to designate one node as the master node. In some implementations, the designation of the master node designates the HCI manager residing on the master node as the active HCI manager, while HCI management resources running on non-master nodes in the same cluster are automatically powered off.

[0037] The node configuration tool 130 also allows administrators to perform the first run by specifying the JSON file required for initial startup. This will prevent VxRail Manager from automatically discovering nodes. In at least some implementations, the node configuration tool supports the simultaneous startup of multiple clusters.

[0038] Using the node configuration tool 130, the manager can also drag and drop ready nodes from the free pool to any existing cluster for node expansion. Conversely, the administrator can also drag and drop a node from the cluster and place it into the free pool for node removal.

[0039] In at least some implementations that support VCF on HCI devices, including implementations that support VCF on VxRail, node configuration tool 130 enables administrators to specify which nodes to include in the VCF deployment.

[0040] Now for reference Figure 2 This illustrates an exemplary dashboard user interface 200 generated by the node configuration tool 130. Figure 2 The dashboard user interface 200 depicted includes a free pool window 202 that identifies free nodes 210 (i.e., nodes not assigned to the cluster). In the depicted example, the identifier for each free node 210 includes an IP address 212, a node name 214, and a version number 216. Additionally, free nodes 210 may be encoded via font color or another visibility attribute to distinguish new nodes (i.e., available nodes that do not require re-imaging) from previously configured dirty nodes that need to be imaged before subsequent deployments. For each dirty free node 210, Figure 2 The user interface 200 displays imaging progress information 218. The dashboard user interface shown also includes grouping options 220, which allow administrators to group free nodes 210 based on version information (grouping option 210-2) or based on a combination of version and hardware configuration (grouping option 210-1). Other implementations may display more, less, and / or different information about the free nodes 210. As an example, dirty nodes and new nodes may be indicated by additional fields instead of font attributes. This variation and similar variations of the depicted dashboard user interface are to be understood as being covered by the dashboard described herein.

[0041] The dashboard user interface 200 shown also includes a cluster window 230 that identifies one or more multi-node clusters. Figure 2 The cluster window 230 shown includes a standard cluster window 240 and an advanced cluster window 250. Figure 2 The standard cluster window 240 depicted identifies two standard clusters 242-1 and 242-2. Each of the standard clusters 242 is shown as having identification information, including a cluster name 244, a version identifier 246, and a status identifier 248. Additionally, Figure 2 Each standard cluster 242 depicted in the standard cluster window 240 identifies each node as part of the cluster. (As shown in...) Figure 2 As described, each cluster node is identified by its IP address (247) and node name (249).

[0042] Figure 2 The advanced cluster window 250 shown identifies one or more hierarchical or tiered cluster objects, each of which includes two or more multi-node component clusters. Figure 2 The advanced cluster window 250 shown identifies a single VCF 252 consisting of two multi-node domains 254. Figure 2 The domain 254 shown includes management domain 254-1 and workload domain 254-2. Figure 2 Each multi-node domain 254 depicted includes information identifying the included nodes via IP address 284 and corresponding node name 286.

[0043] The depicted dashboard user interface 230 also includes a task window 290 that identifies one or more ongoing configuration tasks. Figure 2 Task window 290 indicates the ongoing imaging task 292-1 and cluster startup task 292-2. Imaging task 292-1 reports the re-imaging of dirty nodes 210-3 within the free pool window 202, while cluster startup task 292-2 identifies the ongoing startup of standard cluster 242-2 within the standard cluster window 240. Figure 2 Each configuration task 292 shown indicates a start time 294, an elapsed time 296, and a version number 298.

[0044] although Figure 2 A specific set of information is shown arranged in a particular manner, but those skilled in the art will recognize that the depicted information can be conveyed using an interface arrangement that differs from the illustrated example in one or more aspects. As a non-limiting example, the dashboard user interface 200 shown is a single-page view covering free nodes, standard clusters, and advanced clusters, while alternative implementations (not depicted) may include two or more pages, each depicting... Figure 2 A subset of the information shown. For example, the free node window 202, the standard cluster window 240, and the advanced cluster window 250 can each be represented as a separate page or pane.

[0045] Now go to Figure 3 This illustrates a method 300 for obtaining and displaying or otherwise communicating configuration information for complex infrastructure. Figure 3 The method 300 shown includes assigning (box 302) two static IP addresses (using a Dynamic Host Configuration Protocol (DHCP) module) to each of one or more nodes within a group of nodes. These two IP addresses include an OOB IP address for the Baseboard Management Controller (BMC) network interface used for the out-of-band (OOB) management network, and an internal management IP address for the network interface associated with the internal management network.

[0046] Then, access the BMC at each node via the OOB IP address (Box 304) to invoke the BMC tool to retrieve the cluster configuration information for each node. Then generate (Box 306) a configuration dashboard user interface suitable for generating such interfaces. Figure 2 The dashboard user interface displays information.

[0047] Now for reference Figure 4 , Figures 1 to 3 Any or more of the elements shown can be implemented by Figure 4 The illustrated information processing system 400 is an example of an information processing system or is implemented within said information processing system. The illustrated information processing system includes one or more general-purpose processors or central processing units (CPUs) 401 communicatively coupled to memory resources 410 and input / output hubs 420, with various I / O resources and / or components communicatively coupled to said input / output hubs. Figure 4 The I / O resources explicitly depicted include a network interface 440 (commonly referred to as a NIC (Network Interface Card)), storage resources 430, and additional I / O devices, components, or resources 450. As a non-limiting example, these additional I / O devices, components, or resources include a keyboard, mouse, monitor, printer, speaker, microphone, etc. The illustrated information processing system 400 includes a baseboard management controller (BMC) 460, which, among other features and services, provides out-of-band management resources that can be coupled to a management server (not depicted). In at least some embodiments, the BMC 460 manages the information processing system 400, even when the information processing system 400 is powered off or powered to a standby state. The BMC 460 may include a processor, memory, an out-of-band network interface separate from and physically isolated from the in-band network interface of the information processing system 400, and / or other embedded information processing resources. In some embodiments, the BMC 460 may include or be an integral part of a remote access controller (e.g., a Dell remote access controller or an integrated Dell remote access controller) or a chassis management controller.

[0048] Throughout this disclosure, reference numerals with hyphens refer to specific instances of an element, while reference numerals without hyphens refer to the element in general. Thus, for example, "device 12-1" refers to an instance of a class of devices, which may be collectively referred to as "device 12," and any of them may be generally referred to as "device 12."

[0049] As used herein, when two or more elements are referred to as “coupled” to each other, the term indicates that such two or more elements are in electronic communication, mechanical connection (including thermal and fluid connection, thermal connection or mechanical connection), whether the connection is indirect or direct, and whether there is an intermediate element or not.

[0050] This disclosure covers all changes, substitutions, variations, alterations, and modifications to the exemplary embodiments herein that would be contemplated by those skilled in the art. Similarly, where appropriate, the appended claims cover all changes, substitutions, variations, alterations, and modifications to the exemplary embodiments herein that would be contemplated by those skilled in the art. References in the appended claims to a device or system adapted to, arranged to, capable of, configured to, enable, operable to, or operated to perform a particular function, or to a component of such device or system, cover said device, system, or component whether or not said device, system, component, or said particular function is activated, turned on, or unlocked, provided that said device, system, or component is adapted to, arranged to, capable of, configured to, enable, operable to, or operated to perform said particular function.

[0051] All examples and conditional language described herein are intended for pedagogical purposes to aid the reader in understanding the disclosure and concepts developed by the inventors to advance the technology, and are to be construed as not being limited to such specifically described examples and conditions. Although embodiments of the disclosure have been described in detail, it should be understood that various changes, substitutions, and alterations may be made to the disclosure without departing from its spirit and scope.

Claims

1. A method for an information processing system, the method comprising: The Dynamic Host Configuration Protocol (DHCP) module assigns two static IP addresses to each of one or more nodes within a set of nodes associated with the information processing system, wherein the two static IP addresses include: The OOB IP address for the Baseboard Management Controller (BMC) network interface used for out-of-band (OOB) management network; and Internal management IP addresses used for network interfaces associated with the internal management network; For each of the one or more nodes, access the BMC at the OOB IP address to invoke the BMC tool to retrieve the cluster configuration information for each node; and Generate display information suitable for generating a cluster configuration user interface that indicates the cluster configuration information.

2. The method of claim 1, wherein the cluster configuration information includes information indicating the following: The node is either a cluster node that includes nodes assigned to the cluster, or a free node that includes nodes not assigned to the cluster. For each free node, is the free node a new node that includes previously unconfigured nodes or a dirty node that includes previously configured nodes? as well as For each cluster node, a cluster management engine instance associated with that cluster node.

3. The method of claim 2, wherein the cluster configuration information includes a cloud infrastructure portion indicating nodes within a VMware cloud infrastructure, the VMware cloud infrastructure including a management domain and one or more workload domains, wherein the cloud infrastructure portion indicates nodes within the management domain and nodes within each of the one or more workload domains.

4. The method of claim 1, further comprising: The cluster management engine API is invoked to determine cluster membership information that indicates other cluster nodes associated with the cluster management engine instance, wherein the cluster configuration information includes the cluster membership information.

5. The method of claim 4, wherein the cluster configuration display includes: List the free node parts of the free nodes; as well as The cluster portion includes one or more cluster lists corresponding to one or more clusters, wherein each cluster list includes a list of nodes belonging to the cluster.

6. The method of claim 4, wherein the configuration information includes version information indicating the version of the hyperconverged infrastructure (HCI) device.

7. The method of claim 4, further comprising: In response to receiving user input corresponding to a user interaction with a portion of the user interface indicating a dirty node, a re-imaging request is initiated to re-image the dirty node.

8. The method of claim 4, further comprising: Hardware information indicating the hardware implemented in the node is obtained from an agent that executes on the management program associated with the node.

9. The method of claim 8, wherein the cluster configuration user interface displays one or more groups of free nodes, wherein the nodes in the groups of free nodes are implemented with similar hardware.

10. The method of claim 9, further comprising defining a cluster name based on user input to the user interface.

11. The method of claim 4, further comprising, in response to user input selecting two or more new nodes, creating a new cluster covering each of the two or more new nodes.

12. The method of claim 11, further comprising configuring the specific node as the master node of the cluster in response to user input instructing the specific node, wherein the cluster manager engine of the specific node is enabled and the cluster management engines of the other nodes in the cluster are disabled.

13. The method of claim 4, further comprising adding the new node to the cluster list in response to user input of dragging and dropping the new node into the cluster list.

14. An information processing system, the information processing system comprising: Central Processing Unit (CPU); as well as A computer-readable storage medium accessible by the CPU, the computer-readable storage medium including processor-executable instructions that, when executed by the CPU, cause the system to perform operations, the operations including: The Dynamic Host Configuration Protocol (DHCP) module assigns two static IP addresses to each of one or more nodes within a set of nodes associated with the information processing system, wherein the two static IP addresses include: The OOB IP address for the Baseboard Management Controller (BMC) network interface used for out-of-band (OOB) management network; and Internal management IP addresses used for network interfaces associated with the internal management network; For each of the one or more nodes, access the BMC at the OOB IP address to invoke the BMC tool to retrieve the cluster configuration information for each node; and Generate display information suitable for generating a cluster configuration user interface that indicates the cluster configuration information.

15. The information processing system of claim 14, wherein the cluster configuration information includes information indicating the following: The node is either a cluster node that includes nodes assigned to the cluster, or a free node that includes nodes not assigned to the cluster. For each free node, is the free node a new node that includes previously unconfigured nodes or a dirty node that includes previously configured nodes? as well as For each cluster node, a cluster management engine instance associated with that cluster node.

16. The information processing system of claim 15, wherein the cluster configuration information includes a cloud infrastructure portion indicating nodes within a VMware cloud infrastructure, the VMware cloud infrastructure including a management domain and one or more workload domains, wherein the cloud infrastructure portion indicates nodes within the management domain and nodes within each of the one or more workload domains.

17. The information processing system of claim 14, further comprising: The cluster management engine API is invoked to determine cluster membership information that indicates other cluster nodes associated with the cluster management engine instance, wherein the cluster configuration information includes the cluster membership information.

18. The information processing system of claim 17, wherein the cluster configuration display includes: List the free node parts of the free nodes; as well as The cluster portion includes one or more cluster lists corresponding to one or more clusters, wherein each cluster list includes a list of nodes belonging to the cluster.

19. The information processing system of claim 17, wherein the configuration information includes version information indicating the version of the hyperconverged infrastructure (HCI) device.

20. The information processing system of claim 17, further comprising: In response to receiving user input corresponding to a user interaction with a portion of the user interface indicating a dirty node, a re-imaging request is initiated to re-image the dirty node.

Images