Configuring new nodes for using a storage system managed by a unified storage manager

• US 9,596,135 B1
• Filed: 08/31/2016
• Issued: 03/14/2017
• Est. Priority Date: 08/31/2016
• Status: Active Grant

• Current Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Original Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Inventors: Thomas, Nishanth, Mayilsamy, Kanagaraj
• Primary Examiner(s): Meky, Moustafa M
• Application Number:
  US15/253,069
• Time in Patent Office: 195 Days
• US Class Current: 1/1
• CPC Class Codes: H04L 41/0806 for initial configuration or provisioning, e.g. plug-and-play
• CPC Class Codes: H04L 41/5012 determining service availability, e.g. which services are available at a certain point in time
• CPC Class Codes: H04L 41/5054 Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
• CPC Class Codes: H04L 41/5096 wherein the managed service relates to distributed or central networked applications
• CPC Class Codes: H04L 67/1097 for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]

Abstract

Systems and methods for configuring new nodes for using a storage system managed by a unified storage manager (USM) are disclosed. An example method may comprise detecting, by a processing device executing a unified storage manager (USM), a connection of a machine to the USM, invoking a provisioning component of the USM to initiate a provisioning process for the machine, utilizing, via the provisioning process, an external provisioning service to cause a bootstrapping process to execute on the machine, the bootstrapping process to install an operating system (OS) on the machine and to execute a kickstart file on the machine, responsive to execution of the kickstart file, performing a handshake process with the machine to establish a communication channel between the USM and the machine, and receiving, via the established communication channel, an availability status of the machine as a storage node for storage services managed by the USM.

Claims

1. A method comprising:

detecting, by a processing device executing a unified storage manager (USM), a connection of a machine to the USM;

invoking a provisioning component of the USM to initiate a provisioning process for the machine;

utilizing, by the processing device via the provisioning process, an external provisioning service to cause a bootstrapping process to execute on the machine, the bootstrapping process to install an operating system (OS) on the machine and to execute a kickstart file on the machine;

responsive to execution of the kickstart file, performing, by the processing device, a handshake process with the machine to establish a communication channel between the USM and the machine; and

receiving, via the established communication channel, an availability status of the machine as a storage node for storage services managed by the USM.

2. The method of claim 1, wherein the kickstart file comprises instructions that, when executed by the machine, cause a handshake to occur with the USM to enable communication between the USM and the machine, and wherein a handshake comprises an automated process of negotiation that dynamically sets parameters of the communication channel.

3. The method of claim 1, wherein the handshake process comprises exchanging one or more keys between the machine and the USM in order to establish the communication channel.

4. The method of claim 1, wherein detecting the connection of the machine comprises receiving a network connection request from the machine.

5. The method of claim 1, wherein detecting the connection of the machine comprises receiving an indication of a manual request to connect the machine to the USM.

6. The method of claim 1, further comprising:

receiving an indication of selection of the machine as a storage node;

initiating an inventory process to determine capabilities of the machine;

receiving, from the machine response to the inventory process, the capabilities of the machine; and

storing the received capabilities in a data store of the USM.

7. The method of claim 6, further comprising:

receiving an identification of a cluster type to apply to the machine;

identifying storage service packages associated with the identified cluster type, the storage service packages maintained by the provisioning component; and

causing the external provisioning service to install the identified storage service packages on the machine for the machine to operate as a storage node for one of the storage services associated with the storage service packages.

8. The method of claim 7 wherein the cluster type is based on the capabilities of the machine.

9. The method of claim 1, wherein the capabilities comprise at least one of CPU data of the machine, disk space data of the machine, memory space data of the machine, or networking configuration data of the machine.

10. The method of claim 1, wherein the external provisioning service communicates with the provisioning component via application programming interfaces (APIs) provided via a plugin installed in the provisioning component.

11. A system comprising,

a memory;

and

a processing device communicably coupled to the memory, the processing device to;

detect a connection of a machine to a unified storage manager (USM) executed by the processing device;

invoke a provisioning component of the USM to initiate a provisioning process for the machine;

utilize, via the provisioning process, an external provisioning service to cause a bootstrapping process to execute on the machine, the bootstrapping process to install an operating system (OS) on the machine and to execute a kickstart file on the machine;

perform a handshake process with the machine to establish a communication channel between the USM and the machine, the handshake process initiated by execution of the kickstart file at the machine;

receive, via the established communication channel, an availability status of the machine as a storage node for storage services managed by the USM.

12. The system of claim 11, wherein the kickstart file comprises instructions that, when executed by the machine, cause a handshake to occur with the USM to enable communication between the USM and the machine, and wherein a handshake comprises an automated process of negotiation that dynamically sets parameters of the communication channel.

13. The system of claim 11, wherein the handshake process comprises exchanging one or more keys between the machine and the USM in order to establish the communication channel.

14. The system of claim 11, further comprising:

receiving an indication of selection of the machine as a storage node;

initiating an inventory process to determine capabilities of the machine;

receiving, from the machine response to the inventory process, the capabilities of the machine; and

storing the received capabilities in a data store of the USM.

15. The system of claim 14, further comprising:

receiving an identification of a cluster type to apply to the machine;

identifying storage service packages associated with the identified cluster type, the storage service packages maintained by the provisioning component; and

causing the external provisioning service to install the identified storage service packages on the machine for the machine to operate as a storage node for one of the storage services associated with the storage service packages.

16. The system of claim 11, wherein the external provisioning service communicates with the provisioning component via application programming interfaces (APIs) provided via a plugin installed in the provisioning component.

17. A non-transitory machine-readable storage medium storing instructions that cause a processing device to:

receive an indication of a selection of an available storage node, the available storage node provisioned by a provisioning component of a unified storage manager (USM) executed by the processing device;

initiate, by the processing device, an inventory process to determine capabilities of the selected storage node;

receive, from the selected storage node responsive to the inventory process, the capabilities of the storage node;

store the received capabilities of the selected storage node in a data store of the USM;

receive identification of a cluster type to apply to the selected storage node, the identified cluster type based on the capabilities of the selected storage node; and

provide, by the processing device via an external provisioning service, storage service packages corresponding to the identified cluster type, the storage service packages for installation on the selected storage node.

18. The non-transitory machine-readable storage medium of claim 17, wherein the capabilities comprise capabilities comprise at least one of CPU data of the machine, disk space data of the machine, memory space data of the machine, or networking configuration data of the machine.

19. The non-transitory machine-readable storage medium of claim 17, wherein the storage service packages enable the selected storage node to provide storage services for a storage provider system managed by the USM.

20. The non-transitory machine-readable storage medium of claim 17, wherein the external provisioning service communicates with the provisioning component via application programming interfaces (APIs) provided via a plugin installed in the provisioning component.