Performing customized deployment scenarios in shared environments

Patent metadata

Field	Value
Publication number	US-9614730-B2
Application number	US-201314068269-A
Country	US
Kind code	B2
Filing date	Oct 31, 2013
Priority date	Oct 31, 2013
Publication date	Apr 4, 2017
Grant date	Apr 4, 2017

Abstract

Various embodiments of systems and methods to process customized deployment scenarios in a shared computing environment are described. In one aspect, a deployment request is received at the shared computing environment by a client associated with a customized deployment scenario. In a response, a deploy service of the shared computing environment is instantiated. In another aspect, one or more custom deploy processors are identified by the deploy service, where the one or more custom deploy processors correspond to one or more customized deployment scenarios. In yet another aspect, a part of a deployable content passed to the one or more custom deploy processors by the deploy service, is deployed to the shared computing environment by at least one corresponding custom deploy processor.

First claim

What is claimed is:

1. A computer system that processes customized deploy scenarios, the system comprising:
a memory that stores computer executable instructions;
at least one computer processor coupled to the memory that executes the instructions to receive a deploy request from a client of a plurality of clients of a cloud-based application platform, wherein the client is associated with a customized deploy scenario;
a deploy service that accesses deployable content associated with the deploy request; and
one or more custom deploy processors identifiable upon an instantiation of the deploy service, wherein at least one custom deploy processor of the one or more custom deploy processors provides a functionality for handling the customized deploy scenario when the functionality for handling the customized deploy scenario is not provided by the deploy service, wherein the at least one custom deploy processor of the one or more custom deploy processors corresponds to the customized deploy scenario, and wherein the at least one custom deploy processor of the one or more custom deploy processors recognizes and deploys a corresponding part of the deployable content according to the customized deploy scenario associated with the client.

2. The system of claim 1 further comprising:
a registry that stores information for the one or more custom deploy processors, wherein the one or more custom deploy processors are discoverable based on the information stored in the registry.

3. The system of claim 1 , wherein the at least one custom deploy processor further generates a deploy error notification in response to a failure of the deployment of the corresponding part of the deployable content.

4. The system of claim 1 , wherein the at least one custom deploy processor further rollbacks the deployment of the corresponding part of the deployable content in response to a deploy error notification associated with the deployable content.

5. The system of claim 1 , wherein the deploy service further:
preprocesses the deployable content to extract the corresponding part of the deployable content based on a metadata associated with the at least one custom deploy processor; and
passes the corresponding part of the deployable content to the at least one custom deploy processor for deployment.

6. The system of claim 1 , wherein the deploy service further:
passes the deployable content associated with the deploy request to the one or more custom deploy processors.

7. A non-transitory computer-readable storage medium comprising instructions that, when executed by at least one processor of a machine, cause the machine to perform operations comprising:
receive a deploy request from a client of a plurality of clients of a cloud-based application platform, wherein the client is associated with a customized deploy scenario;
in response to the deploy request, instantiate a deploy service of the cloud-based application platform to access deployable content associated with the deploy request;
upon the instantiation of the deploy service, identify one or more custom deploy processors, wherein at least one custom deploy processor of the one or more custom deploy processors corresponds to the customized deploy scenario, and wherein the at least one custom deploy processor of the one or more custom deploy processors provides a functionality for handling the customized deploy scenario when the functionality for handling the customized deploy scenario is not provided by the deploy service;
recognize a part of the deployable content that corresponds to the at least one custom deploy processor of the one or more custom deploy processors; and
deploy the corresponding part of the deployable content by the least one custom deploy processor of the one or more custom deploy processors, wherein the corresponding part of the deployable content corresponds to the customized deploy scenario associated with the client.

8. The non-transitory computer-readable storage medium of claim 7 comprising instructions that, when executed by the at least one processor of the machine, cause the machine to perform operations further comprising:
generate a deploy error notification by the at least one custom deploy processor when the deployment of the corresponding part of the deployable content fails.

9. The non-transitory computer-readable storage medium of claim 7 comprising instructions that, when executed by the at least one processor of the machine, cause the machine to perform operations further comprising:
rollback the deployment of the corresponding part of the deployable content by the at least one custom deploy processor in response to a deploy error notification associated with the deployable content.

10. The non-transitory computer-readable storage medium of claim 7 , wherein identifying the one or more custom deploy processors comprises:
discover the one or more custom deploy processors by the deploy service based on a registry, wherein the registry stores information for the one or more custom deploy processors.

11. The non-transitory computer-readable storage medium of claim 10 , wherein deploying the corresponding part of the deployable content comprises:
preprocess the deployable content by the deploy service to extract the corresponding part of the deployable content based on information stored in the registry for the at least one custom deploy processor; and
pass the corresponding part of the deployable content to the at least one custom deploy processor for deployment.

12. The non-transitory computer-readable storage medium of claim 7 , wherein recognizing the corresponding part of the deployable content comprises:
pass the deployable content associated with the deploy request to the one or more custom deploy processors; and
search the deployable content by the at least one custom deploy processor for the corresponding part of the deployable content.

13. The non-transitory computer-readable storage medium of claim 7 , wherein deploying the corresponding part of the deployable content comprises:
store the corresponding part of the deployable content in a repository associated with the at least one custom deploy processor to be available for a runtime of the cloud-based application platform.

14. A computer implemented method to process customized deployment scenarios, the method comprising:
at a cloud-based application platform, receiving a deploy request from a client of a plurality of clients of the cloud-based application platform, wherein the client is associated with a customized deploy scenario;
instantiating, by at least one computer processor, a deploy service of the cloud-based application platform to access deployable content associated with the deploy request;
in response to the deployment request, identifying, by the deploy service, one or more custom deploy processors, wherein at least one custom deploy processor of the one or more custom deploy processors corresponds to the customized deploy scenario, and wherein the at least one custom deploy processor of one or more custom deploy processors provides a functionality for handling the customized deploy scenario when the functionality for handling the customized deploy scenario is not provided by the deploy service;
recognizing a part of the deployable content that corresponds to the at least one custom deploy processor of the one or more custom deploy processors; and
deploying the corresponding part of the deployable content by the at least one custom deploy processor of the one or more custom deploy processors, wherein the corresponding part of the deployable content corresponds to the cu

Assignees

• Boshev Stoyan
• Yousouf Shenol
• Sap Se

Inventors

• Boshev Stoyan
• Yousouf Shenol

Classifications

• H04L67/16

  Electricity · mapped topic

• H04L67/10 Primary

  in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46) · CPC title

• H04L41/0863

  by rolling back to previous configuration versions · CPC title

• H04L41/0893 Primary

  Assignment of logical groups to network elements · CPC title

• H04L63/20

  for managing network security; network security policies in general (filtering policies H04L63/0227) · CPC title