Automated cloud set up
US-9083653-B2 · Jul 14, 2015 · US
US11799727B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11799727-B2 |
| Application number | US-202117482403-A |
| Country | US |
| Kind code | B2 |
| Filing date | Sep 22, 2021 |
| Priority date | Nov 20, 2018 |
| Publication date | Oct 24, 2023 |
| Grant date | Oct 24, 2023 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
The present technology addresses a need to automatically configure a new compute resource to join an existing cluster of computing resources. The present technology provides a mechanism to ensure that the new compute resource is executing the same kernel version which further permits subsequent exchange at least one configuration message informing the new compute resource of necessary configuration parameters and an address to retrieve required software packages.
Opening claim text (preview).
The invention claimed is: 1. A computer-implemented method comprising: receiving, at a computing cluster, a request to join the computing cluster from a computing resource; authenticating the computing resource for membership to the computing cluster in response to the computing resource conforming to requirements to join the computing cluster including at least a software bundle used by members in the computing cluster; and accepting the computing resource in the computing cluster. 2. The computer-implemented method of claim 1 , wherein the request to join the computing cluster is a request to at least one member of the computing cluster for the information describing requirements to join the computing cluster. 3. The computer-implemented method of claim 2 , wherein the information describing requirements to join the computing cluster includes membership authentication information. 4. The computer-implemented method of claim 1 , further comprising: transmitting a reply in response to the request, including information describing requirements to join the computing cluster and a reference to a software bundle used by the at least one member in the computing cluster and, wherein the reference to the software bundle is a result of a determination made by at least one member of the computing cluster that the computing resource is not running a same version of the software bundle as the at least one member of the computing cluster. 5. The computer-implemented method of claim 1 , further comprising: prior to the receiving of the request to join the computing cluster, receiving a preboot execution environment request; and transmitting a boot image in response to the preboot execution environment request. 6. The computer-implemented method of claim 1 , wherein the software bundle is contained in a Docker container that is executable by the computing resource. 7. The computer-implemented method of claim 1 , further comprising: installing a software or configuration update by at least one member of the computing cluster; and generating the software bundle containing the software or configuration included in the update and labeling the software bundle with a release version. 8. A system comprising: at least one processor; and at least one memory storing instructions, which when executed by the at least one processor, cause the at least one processor to: receive a request to join a computing cluster from a computing resource; authenticate the computing resource for membership to the computing cluster in response to the computing resource conforming to requirements to join the computing cluster including at least a software bundle used by members in the computing cluster; and accept the computing resource in the computing cluster. 9. The system of claim 8 , wherein the request to join the computing cluster is a request to at least one member of the computing cluster for the information describing requirements to join the computing cluster. 10. The system of claim 9 , wherein the information describing requirements to join the computing cluster includes membership authentication information. 11. The system of claim 8 , further comprising instructions, which when executed by the at least one processor, causes the at least one processor to: transmit a reply in response to the request, including information describing requirements to join the computing cluster and a reference to a software bundle used by the at least one member in the computing cluster and, wherein the reference to the software bundle is a result of a determination made by at least one member of the computing cluster that the computing resource is not running a same version of the software bundle as the at least one member of the computing cluster. 12. The system of claim 8 , further comprising instructions, which when executed by the at least one processor, causes the at least one processor to: prior to the receiving of the request to join the computing cluster, receive a preboot execution environment request; and transmit a boot image in response to the preboot execution environment request. 13. The system of claim 8 , wherein the software bundle is contained in a Docker container that is executable by the computing resource. 14. The system of claim 8 , further comprising instructions, which when executed by the at least one processor, causes the at least one processor to:: install a software or configuration update by at least one member of the computing cluster; and generate the software bundle containing the software or configuration included in the update and labeling the software bundle with a release version. 15. At least one non-transitory computer-readable medium storing instructions, which when executed by the at least one processor, cause the at least one processor to: receive a request to join a computing cluster from a computing resource; authenticate the computing resource for membership to the computing cluster in response to the computing resource conforming to requirements to join the computing cluster including at least a software bundle used by members in the computing cluster; and accept the computing resource in the computing cluster. 16. The at least one non-transitory computer-readable medium of claim 15 , wherein the request to join the computing cluster is a request to at least one member of the computing cluster for the information describing requirements to join the computing cluster. 17. The at least one non-transitory computer-readable medium of claim 16 , wherein the information describing requirements to join the computing cluster includes membership authentication information. 18. The at least one non-transitory computer-readable medium of claim 15 , further comprising instructions, which when executed by the at least one processor, causes the at least one processor to: transmit a reply in response to the request, including information describing requirements to join the computing cluster and a reference to a software bundle used by the at least one member in the computing cluster and, wherein the reference to the software bundle is a result of a determination made by at least one member of the computing cluster that the computing resource is not running a same version of the software bundle as the at least one member of the computing cluster. 19. The at least one non-transitory computer-readable medium of claim 15 , further comprising instructions, which when executed by the at least one processor, causes the at least one processor to: prior to the receiving of the request to join the computing cluster, receive a preboot execution environment request; and transmit a boot image in response to the preboot execution environment request. 20. The at least one non-transitory computer-readable medium of claim 15 , wherein the software bundle is contained in a Docker container that is executable by the computing resource.
of virtualised topologies, e.g. software-defined networks [SDN] or network function virtualisation [NFV] · CPC title
Policy-based network configuration management · CPC title
Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements · CPC title
Assignment of logical groups to network elements · CPC title
Installation · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.