# US 2020/0403886 A1 · Node addition in cloud networks

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2020/0403886 A1
- Document ID: US20200403886A1
- Status: Published application
- Kind: A1
- Application number: 16/444,896
- Filed: 2019-06-18
- Published: 2020-12-24
- Earliest claimed: 2019-06-18
- Assignees: Hewlett Packard Enterprise Development LP
- Applicants: Hewlett Packard Enterprise Development LP
- Inventors: Charan Acharya Chandrashekar
- Web page: https://patentgrep.com/patent/US20200403886A1

## CPC

- H04L 41/0853: by actively collecting configuration information or by backing up configuration information
- H04L 41/5048: {Automatic or semi-automatic definitions, e.g. definition templates}
- H04L 41/0806: for initial configuration or provisioning, e.g. plug-and-play
- H04L 41/0895: Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
- H04L 41/40: using virtualisation of network functions or resources, e.g. SDN or NFV entities
- H04L 41/5054: Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
- H04L 63/08: {for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32)}
- H04L 41/082: the condition being updates or upgrades of network functionality
- H04L 41/22: comprising specially adapted graphical user interfaces [GUI]
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Example techniques of addition of nodes in cloud networks managed by a multi-cloud management platform, are described. In an example, a node addition request is received at a multi-cloud management platform. The node addition request includes identification information of a node and a cloud network in which the node is to be added. The identification information is indicative of a functionality of the node, a network address of the node, and an identifier of the cloud network. Based on the identifier of the cloud network, cloud account details of the cloud network may be obtained from one of the multi-cloud management platform and a user input. A controller node of the cloud network may be accessed based on the cloud account details. The node may be registered at the controller node of the cloud network, based on the identification information of the node and the cloud network.

## Claims

### Claim 1

A method for addition of nodes in cloud networks, comprising:
receiving a node addition request at a multi-cloud management platform, wherein the multi-cloud management platform is to manage a plurality of cloud networks, the node addition request including identification information of a node and a cloud network, amongst the plurality of cloud networks, in which the node is to be added, the identification information being indicative of a functionality of the node, a network address of the node, and an identifier of the cloud network;
obtaining, based on the identifier of the cloud network, cloud account details of the cloud network from one of the multi-cloud management platform and a user input, the cloud account details indicative of data for authentication of a user account that controls access to computing resources of the cloud network;
accessing a controller node of the cloud network based on the cloud account details, wherein the controller node is to manage non-compute services of the cloud network; and
registering the node at the controller node of the cloud network, based on the identification information of the node and the cloud network.

### Claim 2 (depends on 1)

The method as claimed in claim 1, wherein registering the node at the controller node of the cloud network comprises:
determining, based on the functionality and the network address of the node, whether the node is operationally compatible for being registered at the controller node of the cloud network; and
in response to determining that the node is operationally compatible for being registered at the controller node of the cloud network, updating a node registration database maintained in the controller node to include a node identifier of the node, wherein the node registration database is to store a list of node identifiers, each corresponding to one of a plurality of nodes registered at the controller node of the cloud network.

### Claim 3 (depends on 1)

The method as claimed in claim 1, further comprising:
in response to receiving the node addition request, checking whether an Operating System (OS) is pre-installed in the node; and
installing the OS in the node based on the identification information of the node and the cloud network, in response to identifying that the OS is not pre-installed in the node.

### Claim 4 (depends on 3)

The method as claimed in claim 3, wherein installing the OS comprises:
identifying service provider related information of the cloud network based on the identifier of the cloud network;
obtaining, based on the functionality of the node and the service provider related information of the cloud network, an image file of the OS from one of a user input and a predefined image store of the multi-cloud management platform; and
executing the image file of the OS to install the OS in the node.

### Claim 5 (depends on 1)

The method as claimed in claim 1, further comprising, generating an addition successful message, in response to the node being successfully registered at the controller node of the cloud network.

### Claim 6 (depends on 1)

The method as claimed in claim 1, wherein the network address of the node is one of an Internet Protocol (IP) address of the node, a Media Access Control (MAC) address of the node, an IP address of a Baseboard Management Controller of the node, and a combination thereof.

### Claim 7 (depends on 1)

The method as claimed in claim 1, wherein the controller node is to manage Application Programming Interfaces (APIs), web interfaces, schedulers, database servers, and message queues of the cloud network.

### Claim 8

A system for addition of nodes in cloud networks, comprising:
a processor; and
a memory coupled to the processor, the memory storing instructions executable by the processor to:
generate a list of a plurality of cloud networks managed by a multi-cloud management platform;
receive a node addition request at the multi-cloud management platform, the node addition request including identification information of a node and a cloud network, amongst the plurality of cloud networks, in which the node is to be added, the identification information being indicative of a functionality of the node, a network address of the node, and an identifier of the cloud network;
install an Operating System (OS) in the node based on the identification information of the node and the cloud network, in response to identifying that the OS is not pre-installed in the node;
obtain, based on the identifier of the cloud network, cloud account details of the cloud network from one of the multi-cloud management platform and a user input, the cloud account details indicative of data for authentication of a user account that controls access to computing resources of the cloud network;
access a controller node of the cloud network based on the cloud account details, wherein the controller node is to manage non-compute services of the cloud network; and
register the node at the controller node of the cloud network, based on the identification information of the node and the cloud network.

### Claim 9 (depends on 8)

The system as claimed in claim 8, wherein the processor is further to:
determine, based on the functionality and the network address of the node, whether the node is operationally compatible for being registered at the controller node of the cloud network; and
in response to determining that the node is operationally compatible for being registered at the controller node of the cloud network, update a node registration database maintained in the controller node to include a node identifier of the node, wherein the node registration database is to store a list of node identifiers, each corresponding to one of a plurality of nodes registered at the controller node of the cloud network.

### Claim 10 (depends on 8)

The system as claimed in claim 8, wherein the processor is further to:
identify service provider related information of the cloud network based on the identifier of the cloud network;
obtain, based on the functionality of the node and the service provider related information of the cloud network, an image file of the OS from one of a user input and a predefined image store of the multi-cloud management platform; and
execute the image file of the OS to install the OS in the node.

### Claim 11 (depends on 8)

The system as claimed in claim 8, wherein the processor is further to, generate an addition successful message, in response to the node being successfully registered at the controller node of the cloud network.

### Claim 12 (depends on 8)

The system as claimed in claim 8, wherein the network address of the node is one of an Internet Protocol (IP) address of the node, a Media Access Control (MAC) address of the node, an IP address of a Baseboard Management Controller of the node, and a combination thereof.

### Claim 13 (depends on 8)

The system as claimed in claim 8, wherein the controller node is to manage Application Programming Interfaces (APIs), web interfaces, schedulers, database servers, and message queues of the cloud network.

### Claim 14

A non-transitory computer-readable medium comprising computer-readable instructions for addition of nodes in cloud networks, the computer-readable instructions when executed by a processor, cause the processor to:
generate a list of a plurality of cloud networks managed by a multi-cloud management platform;
receive a node addition request including identification information of a node and a cloud network, amongst the plurality of cloud networks, in which the node is to be added, the identification information being indicative of a functionality of the node, a network address of the node, and an identifier of the cloud network;
obtain, based on the identifier of the cloud network, cloud account details of the cloud network from one of the multi-cloud management platform and a user input, the cloud account details indicative of data for authentication of a user account that controls access to computing resources of the cloud network;
access a controller node of the cloud network based on the cloud account details, wherein the controller node is to manage non-compute services of the cloud network; and
update a node registration database maintained in the controller node to include a node identifier of the node, wherein the node registration database is to store a list of node identifiers, each corresponding to one of a plurality of nodes registered at the controller node of the cloud network.

### Claim 15 (depends on 14)

The non-transitory computer-readable medium as claimed in claim 14, wherein the computer-readable instructions to update the node registration database when executed by the processor, further cause the processor to:
determine, based on the functionality and the network address of the node, whether the node is operationally compatible for being registered at the controller node of the cloud network.

### Claim 16 (depends on 14)

The non-transitory computer-readable medium as claimed in claim 14, wherein the computer-readable instructions when executed by the processor, further cause the processor to:
check whether an Operating System (OS) is pre-installed in the node, in response to receiving the node addition request; and
install the OS in the node based on the identification information of the node and the cloud network, in response to identifying that the OS is not pre-installed in the node.

### Claim 17 (depends on 16)

The non-transitory computer-readable medium as claimed in claim 16, wherein the computer-readable instructions to install the OS in the node, when executed by the processor, further cause the processor to:
identify service provider related information of the cloud network based on the identifier of the cloud network;
obtain, based on the functionality of the node and the service provider related information of the cloud network, an image file of the OS from one of a user input and a predefined image store of the multi-cloud management platform; and
execute the image file of the OS to install the OS in the node.

### Claim 18 (depends on 14)

The non-transitory computer-readable medium as claimed in claim 14, wherein the computer-readable instructions, when executed by the processor, further cause the processor to generate an addition successful message, in response to the node being successfully registered at the controller node of the cloud network.

### Claim 19 (depends on 14)

The non-transitory computer-readable medium as claimed in claim 14, wherein the network address of the node is one of an Internet Protocol (IP) address of the node, a Media Access Control (MAC) address of the node, an IP address of a Baseboard Management Controller of the node, and a combination thereof.

### Claim 20 (depends on 14)

The non-transitory computer-readable medium as claimed in claim 14, wherein the controller node is to manage Application Programming Interfaces (APIs), web interfaces, schedulers, database servers, and message queues of the cloud network.
