Creating a highly-available private cloud gateway based on a two-node hyperconverged infrastructure cluster with a self-hosted hypervisor management system
View Patent ↗Embodiments described herein are generally directed to a creation of an HA private cloud gateway based on a two-node HCI cluster with a self-hosted HMS. According to an example, a request to register a private cloud to be supported by on-premises infrastructure is received by a SaaS portal, which causes a base station to discover servers within the on-premises infrastructure. The base station is then instructed to prepare a server as a deployment node for use in connection with creation of a cluster of two HCI nodes of the servers to represent the HA private cloud gateway, including installing a seed HMS on the deployment node. The base station is further instructed to cause the seed HMS to create the cluster, install a self-hosted HMS within the cluster to manage the cluster, register the cluster to the self-hosted HMS, and finally delete the seed HMS from the deployment node.
1. A method comprising:
instructing, by a computing device, a base station to install a seed hypervisor management system on a deployment node;
instructing, by the computing device, the base station to cause the seed hypervisor management system running on the deployment node to create a hyperconverged infrastructure cluster managed by the seed hypervisor management system; and
instructing, by the computing device, the base station to cause the deployment node to install a self-hosted hypervisor management system within the hyperconverged infrastructure cluster, the self-hosted hypervisor management system to manage the hyperconverged infrastructure cluster.
2. The method of claim 1 , further comprising:
instructing, by the computing device, the base station to cause the deployment node to register the hyperconverged infrastructure cluster to the self-hosted hypervisor management system; and
instructing, by the computing device, the base station to cause the deployment node to delete the seed hypervisor management system from the deployment node.
3. The method of claim 1 , wherein the hyperconverged infrastructure cluster includes only two nodes, and wherein the deployment node is included in the hyperconverged infrastructure cluster.
4. The method of claim 1 , wherein the hyperconverged infrastructure cluster comprises a high-availability private cloud gateway, and wherein the computing device comprises a Software-as-a-Service (SaaS) portal device.
5. The method of claim 1 , further comprising:
instructing, by the computing device, the base station to create a Virtual Private Cloud (VPC) within a public cloud that includes the base station.
6. The method of claim 1 , further comprising:
receiving, by the computing device, a request to register a private cloud to be supported by an enterprise infrastructure; and
in response to the received request, the computing device instructing the base station to discover a plurality of servers within the private cloud.
7. The method of claim 6 , further comprising:
identifying, by the computing device, the base station from among a plurality of geographically distributed base stations based on a geographical location of the private cloud.
8. A system comprising:
a processing resource; and
a non-transitory computer-readable medium, coupled to the processing resource, having stored therein instructions that when executed by the processing resource cause the processing resource to:
instruct a base station to install a seed hypervisor management system on a deployment node;
instruct the base station to cause the seed hypervisor management system running on the deployment node to create a hyperconverged infrastructure cluster managed by the seed hypervisor management system; and
instruct the base station to cause the deployment node to install a self-hosted hypervisor management system within the hyperconverged infrastructure cluster, the self-hosted hypervisor management system to manage the hyperconverged infrastructure cluster.
9. The system of claim 8 , wherein the instructions further cause the processing resource to:
instruct the base station to cause the deployment node to register the hyperconverged infrastructure cluster to the self-hosted hypervisor management system; and
instruct the base station to cause the deployment node to delete the seed hypervisor management system from the deployment node.
10. The system of claim 8 , wherein the hyperconverged infrastructure cluster includes only two nodes, and wherein the deployment node is included in the hyperconverged infrastructure cluster.
11. The system of claim 8 , wherein the hyperconverged infrastructure cluster comprises a high-availability private cloud gateway, and wherein the system comprises a Software-as-a-Service (SaaS) portal system.
12. The system of claim 8 , wherein the instructions further cause the processing resource to:
instruct the base station to create a Virtual Private Cloud (VPC) within a public cloud that includes the base station.
13. The system of claim 8 , wherein the instructions further cause the processing resource to:
receive a request to register a private cloud to be supported by an enterprise infrastructure; and
in response to the received request, instruct the base station to discover a plurality of servers within the private cloud.
14. The system of claim 13 , wherein the instructions further cause the processing resource to:
identify the base station from among a plurality of geographically distributed base stations based on a geographical location of the private cloud.
15. A non-transitory machine readable medium storing instructions that when executed by a processing resource of a computer system cause the processing resource to:
instruct a base station to install a seed hypervisor management system on a deployment node;
instruct the base station to cause the seed hypervisor management system running on the deployment node to create a hyperconverged infrastructure cluster managed by the seed hypervisor management system; and
instruct the base station to cause the deployment node to install a self-hosted hypervisor management system within the hyperconverged infrastructure cluster, the self-hosted hypervisor management system to manage the hyperconverged infrastructure cluster.
16. The non-transitory machine readable medium of claim 15 , wherein the instructions further cause the processing resource to:
instruct the base station to cause the deployment node to register the hyperconverged infrastructure cluster to the self-hosted hypervisor management system; and
instruct the base station to cause the deployment node to delete the seed hypervisor management system from the deployment node.
17. The non-transitory machine readable medium of claim 15 , wherein:
the hyperconverged infrastructure cluster includes only two nodes,
the deployment node is included in the hyperconverged infrastructure cluster, and
the hyperconverged infrastructure cluster comprises a high-availability private cloud gateway.
18. The non-transitory machine readable medium of claim 15 , wherein the instructions further cause the processing resource to:
instruct the base station to create a Virtual Private Cloud (VPC) within a public cloud that includes the base station.
19. The non-transitory machine readable medium of claim 15 , wherein the instructions further cause the processing resource to:
receive a request to register a private cloud to be supported by an enterprise infrastructure; and
in response to the received request, instruct the base station to discover a plurality of servers within the private cloud.
20. The non-transitory machine readable medium of claim 19 , wherein the instructions further cause the processing resource to:
identify the base station from among a plurality of geographically distributed base stations based on a geographical location of the private cloud.