Mesh version control lifecycle service
A system and method of performing a version control in a mesh network of nodes is disclosed. The method includes executing, by a processing device, a mesh version control life cycle service (VCLS) to maintain a manifest of a mesh network. The manifest comprises, for each node in the mesh network, a history of one or more services executing on a node and a service version for each service of the one or more services. The method includes performing a version control of the mesh network based on the manifest, comprising sending a message to a first node of the mesh network to instruct the first node to change a version of a service executing on the first node from a first version to a second version.
1. A method comprising:
executing, by a processing device, a mesh version control life cycle service (VCLS) to initiate a manifest of a mesh network by querying each node in the mesh network, the manifest comprising, for each node in the mesh network, a history of one or more services executing on a node and a service version for each service of the one or more services; and
performing a version control of the mesh network based on the manifest, comprising:
sending a message to a first node of the mesh network to instruct the first node to change a version of a service executing on the first node from a first version to a second version.
2. The method of claim 1 , wherein the manifest comprises a mapping including a history of one or more versions of the mesh network corresponding to one or more points in time, and wherein each version of the mesh network has a numerical identifier.
3. The method of claim 2 , wherein each version of the mesh network including, at a point in time, for each node in the mesh network, one or more services on a node, a service version for each service of the one or more services and a firmware version of the node.
4. The method of claim 1 , wherein the performing the version control of the mesh network based on the manifest further comprises sending a message to each node in at least a portion of the mesh network to instruct each node in at least the portion of the mesh network to perform a rollback of a service from a current version to a previous version.
5. The method of claim 1 , wherein the performing the version control of the mesh network based on the manifest further comprises sending a message to each node in at least a portion of the mesh network to instruct each node in at least the portion of the mesh network to perform a roll forward of the service from the previous version to the current version.
6. The method of claim 1 , wherein the executing the mesh VCLS to maintain the manifest of the mesh network comprises executing the mesh VCLS to issue a command associated with a repository, and wherein the manifest of the mesh network is stored at the repository.
7. A system comprising:
a memory; and
a processing device, operatively coupled to the memory, the processing device to:
execute, by a processing device, a mesh version control life cycle service (VCLS) to initiate a manifest of a mesh network by querying each node in the mesh network, the manifest comprising, for each node in the mesh network, a history of one or more services executing on a node and a service version for each service of the one or more services; and
perform a version control of the mesh network based on the manifest, comprising:
send a message to a first node of the mesh network to instruct the first node to change a version of a service executing on the first node from a first version to a second version.
8. The system of claim 7 , wherein the manifest comprises a mapping including a history of one or more versions of the mesh network corresponding to one or more points in time, and wherein each version of the mesh network has a numerical identifier.
9. The system of claim 8 , wherein each version of the mesh network including, at a point in time, for each node in the mesh network, one or more services on a node, a service version for each service of the one or more services and a firmware version of the node.
10. The system of claim 7 , wherein the processing device is further to:
send a message to each node in at least a portion of the mesh network to instruct each node in at least the portion of the mesh network to perform a rollback of a service from a current version to a previous version.
11. The system of claim 7 , wherein the processing device is further to:
send a message to each node in at least a portion of the mesh network to instruct each node in at least the portion of the mesh network to perform a roll forward of the service from the previous version to the current version.
12. The system of claim 7 , wherein the processing device is further to:
execute the mesh VCLS to issue a command associated with a repository, and wherein the manifest of the mesh network is stored at the repository.
13. A non-transitory computer-readable medium storing instructions that, when executed by a processing device, cause the processing device to:
execute, by the processing device, a mesh version control life cycle service (VCLS) to initiate a manifest of a mesh network by querying each node in the mesh network, the manifest comprising, for each node in the mesh network, a history of one or more services executing on a node and a service version for each service of the one or more services; and
perform a version control of the mesh network based on the manifest, comprising:
send a message to a first node of the mesh network to instruct the first node to change a version of a service executing on the first node from a first version to a second version.
14. The non-transitory computer-readable medium of claim 13 , wherein the manifest comprises a mapping including a history of one or more versions of the mesh network corresponding to one or more points in time, and wherein each version of the mesh network has a numerical identifier.
15. The non-transitory computer-readable medium of claim 14 , wherein each version of the mesh network including, at a point in time, for each node in the mesh network, one or more services on a node, a service version for each service of the one or more services and a firmware version of the node.
16. The non-transitory computer-readable medium of claim 13 , wherein the processing device is further to:
send a message to each node in at least a portion of the mesh network to instruct each node in at least the portion of the mesh network to perform a rollback of a service from a current version to a previous version.
17. The non-transitory computer-readable medium of claim 13 , wherein the processing device is further to:
send a message to each node in at least a portion of the mesh network to instruct each node in at least the portion of the mesh network to perform a roll forward of the service from the previous version to the current version, and
execute the mesh VCLS to issue a command associated with a repository, and wherein the manifest of the mesh network is stored at the repository.