Obtaining software updates from neighboring hosts in a virtualized computing system
An example method of upgrading a host in a cluster under management of a lifecycle manager in a virtualized computing system includes: receiving, from the lifecycle manager at a host in the cluster being upgraded, a desired software specification for a hypervisor of the host; determining, by the host, a list of required software installation bundles (SIBs) to satisfy the desired software specification; identifying a neighboring host in the cluster for the host; downloading, from the neighboring host to the host, at least at portion of the required SIBs; and executing an upgrade of the hypervisor in the host using the required SIBs.
1. A method of upgrading a host in a cluster under management of a lifecycle manager in a virtualized computing system, the method comprising:
receiving, from the lifecycle manager at a host in the cluster being upgraded, a desired software specification for a hypervisor of the host;
determining, by the host, a list of required software installation bundles (SIBs) to satisfy the desired software specification;
identifying a neighboring host in the cluster for the host;
downloading, from the neighboring host to the host, at least at portion of the required SIBs; and
executing an upgrade of the hypervisor in the host using the required SIBs.
2. The method of claim 1 , wherein the host receives a list of neighboring hosts having the neighboring host from the lifecycle manager.
3. The method of claim 1 , wherein the host determines a list of neighboring hosts having the neighboring host autonomously.
4. The method of claim 1 , wherein the host obtains a list of neighboring hosts, and wherein the neighboring host has a shorter response time than other neighboring hosts having the required SIBs.
5. The method of claim 1 , further comprising:
downloading, from the lifecycle manager to the host, at least one missing SIB of the required SIBs not present on any neighboring host.
6. The method of claim 1 , wherein the neighboring host is configured to perform a method comprising:
obtaining, by a SIB generator, image metadata from the neighboring host, the image metadata describing a running image of another hypervisor executing on the neighboring host;
identifying, from the image metadata, a plurality of SIBs used to install the running image on the neighboring host;
obtaining, from the image metadata, SIB descriptors and SIB signatures for the plurality of SIBs;
obtaining, from storage on the neighboring host, payloads referenced in the image metadata for the SIBs;
recreating the plurality of SIBs from the SIB descriptors, the SIB signatures, and the payloads; and
storing the recreated plurality of SIBs for access by the host.
7. The method of claim 6 , further comprising:
verifying, by the neighboring host, checksums of the plurality of SIBs as recreated against checksums for the plurality of SIBs as stored in the image metadata.
8. A non-transitory computer readable medium comprising instructions to be executed in a computing device to cause the computing device to carry out a method of a method of upgrading a host in a cluster under management of a lifecycle manager in a virtualized computing system, the method comprising:
receiving, from the lifecycle manager at a host in the cluster being upgraded, a desired software specification for a hypervisor of the host;
determining, by the host, a list of required software installation bundles (SIBs) to satisfy the desired software specification;
identifying a neighboring host in the cluster for the host;
downloading, from the neighboring host to the host, at least at portion of the required SIBs; and
executing an upgrade of the hypervisor in the host using the required SIBs.
9. The non-transitory computer readable medium of claim 8 , wherein the host receives a list of neighboring hosts having the neighboring host from the lifecycle manager.
10. The non-transitory computer readable medium of claim 8 , wherein the host determines a list of neighboring hosts having the neighboring host autonomously.
11. The non-transitory computer readable medium of claim 8 , wherein the host obtains a list of neighboring hosts, and wherein the neighboring host has a shorter response time than other neighboring hosts having the required SIBs.
12. The non-transitory computer readable medium of claim 8 , further comprising:
downloading, from the lifecycle manager to the host, at least one missing SIB of the required SIBs not present on any neighboring host.
13. The non-transitory computer readable medium of claim 8 , wherein the neighboring host is configured to perform a method comprising:
obtaining, by a SIB generator, image metadata from the neighboring host, the image metadata describing a running image of another hypervisor executing on the neighboring host;
identifying, from the image metadata, a plurality of SIBs used to install the running image on the neighboring host;
obtaining, from the image metadata, SIB descriptors and SIB signatures for the plurality of SIBs;
obtaining, from storage on the neighboring host, payloads referenced in the image metadata for the SIBs;
recreating the plurality of SIBs from the SIB descriptors, the SIB signatures, and the payloads; and
storing the recreated plurality of SIBs for access by the host.
14. The non-transitory computer readable medium of claim 13 , further comprising:
verifying, by the neighboring host, checksums of the plurality of SIBs as recreated against checksums for the plurality of SIBs as stored in the image metadata.
15. A virtualized computing system having a cluster comprising hosts connected to a network, the virtualized computing system comprising:
a lifecycle manager;
a host; and
a neighboring host to the host;
the host configured to:
receive, from the lifecycle manager, a desired software specification for a hypervisor of the host;
determine a list of required software installation bundles (SIBs) to satisfy the desired software specification;
identify the neighboring host in the cluster for the host;
download, from the neighboring host, at least at portion of the required SIBs; and
execute an upgrade of the hypervisor in the host using the required SIBs.
16. The virtualized computing system of claim 15 , wherein the host receives a list of neighboring hosts having the neighboring host from the lifecycle manager.
17. The virtualized computing system of claim 15 , wherein the host determines a list of neighboring hosts having the neighboring host autonomously.
18. The virtualized computing system of claim 15 , wherein the host obtains a list of neighboring hosts, and wherein the neighboring host has a shorter response time than other neighboring hosts having the required SIBs.
19. The virtualized computing system of claim 15 , wherein the host is configured to:
downloading, from the lifecycle manager, at least one missing SIB of the required SIBs not present on any neighboring host.
20. The virtualized computing system of claim 15 , wherein the neighboring host is configured to:
obtain, by a SIB generator, image metadata from the neighboring host, the image metadata describing a running image of another hypervisor executing on the neighboring host;
identify, from the image metadata, a plurality of SIBs used to install the running image on the neighboring host;
obtain, from the image metadata, SIB descriptors and SIB signatures for the plurality of SIBs;
obtain, from storage on the neighboring host, payloads referenced in the image metadata for the SIBs;
recreate the plurality of SIBs from the SIB descriptors, the SIB signatures, and the payloads; and
store the recreated plurality of SIBs for access by the host.