Pull based inner-loop code deployment

Abstract

A method includes determining whether a code update for the service is available at a central repository of the computing environment and, in response to determining that the code update is available, retrieving the code update from the central repository. The method further includes performing a modification of the service in view of the code update.

What is claimed is: 
     
         1 . A method comprising:
 determining, by a processing device executing an instance of a service within a computing environment, whether a code update for the service is available at a central repository of the computing environment;   in response to determining that the code update is available, retrieving the code update from the central repository; and   performing, by the processing device, a modification of the instance of the service in view of the code update.   
     
     
         2 . The method of  claim 1 , wherein determining whether the code update for the service is available is in response to determining that the instance of the service has been accessed. 
     
     
         3 . The method of  claim 1 , wherein the computing environment comprises a cluster of host computing devices executing a high performance computing workload. 
     
     
         4 . The method of  claim 1 , wherein the service executes in a container comprising an isolated execution environment. 
     
     
         5 . The method of  claim 4 , wherein performing the modification comprises:
 applying the code update to a local file system of the container of the instance of the service without restarting the container.   
     
     
         6 . The method of  claim 1 , wherein determining whether a code update for the service is available comprises determining whether metadata of the central repository indicates that the code update is stored at the centralized repository. 
     
     
         7 . The method of  claim 6 , wherein the metadata of the central repository comprises a signature of the code updates. 
     
     
         8 . A system comprising:
 a plurality of host machines executing one or more instances of a service for a computing workload; and   a central code repository communicatively coupled to the plurality of host machines, the central code repository comprising a processing device to:
 receive modifications to the service; 
 publish the modifications to be available to the one or more instances of the service; and 
 in response to receiving a request to retrieve the modifications from one of the one or more instances of the service, provide the modifications to the instance of the service. 
   
     
     
         9 . The system of  claim 8 , wherein the central code repository comprises a continuously running code repository accessible by each of the one or more instances of the service. 
     
     
         10 . The system of  claim 8 , wherein the modifications to the service comprise one or more code changes for the service pushed to the central code repository from a developer system. 
     
     
         11 . The system of  claim 8 , wherein the modifications are associated with an access location of the service, and wherein the request to retrieve the modifications comprises the access location of the modifications. 
     
     
         12 . The system of  claim 8 , wherein to publish the modifications, the processing device is to:
 store a signature of the modifications as metadata associated with the modifications, the metadata being accessible by each of the one or more instances of the service.   
     
     
         13 . The system of  claim 12 , wherein the signature comprises a checksum of the modifications. 
     
     
         14 . The system of  claim 12 , wherein to store the signature of the modifications as metadata the processing device is to:
 store the signature in a configuration map (configMap) associated with the plurality of host machines and the central code repository.   
     
     
         15 . A non-transitory computer-readable storage medium including instructions that, when executed by a processing device, cause the processing device to:
 determine, by a processing device, that a code update for a service of a computing environment is available at a centralized repository;   retrieve, by each of a plurality of instances of the service, the code update from the centralized repository; and   update, by the processing device, each of the plurality of instances of the service in view of the code update retrieved from the centralized repository.   
     
     
         16 . The non-transitory computer-readable storage medium of  claim 15 , wherein the processing device determines that a code update for the service is available at periodic intervals. 
     
     
         17 . The non-transitory computer-readable storage medium of  claim 15 , wherein to determine that the code update for the service is available, the processing device is to:
 access metadata associated with the central repository, the access metadata comprising a signature of the code update; and   determine that the signature of the code update indicates that the code update is stored at the central repository.   
     
     
         18 . The non-transitory computer-readable storage medium of  claim 15 , wherein to retrieve the code update from the central repository, the processing device is to:
 download the code update from the central repository to a container associated with each of the plurality of instances of the service.   
     
     
         19 . The non-transitory computer-readable storage medium of  claim 15 , wherein the processing device is further to:
 perform a snapshot of each of the plurality of instances of the service prior to updating each of the plurality of instances of the service.   
     
     
         20 . The non-transitory computer-readable storage medium of  claim 19 , wherein the processing device is further to:
 monitor performance of each of the plurality of instances of the service; and   in response to detecting a performance regression of the service associated with the code update, revert each of the plurality of instances of the service to a previous state in view of the snapshot of each of the plurality of instances of the service.