APPLICATION ENVIRONMENT PROVISIONING

• US 20200136930A1
• Filed: 10/24/2018
• Published: 04/30/2020
• Est. Priority Date: 10/24/2018
• Status: Abandoned Application

• Current Assignee: CA Software Österreich GmbH (Broadcom, Inc.)
• Original Assignee: CA Software Österreich GmbH (Broadcom, Inc.)
• Inventors: Szulman, Peter Miklos, Holzer, Markus, Pomajbik, Stefan
• Application Number:
  US16/169,314
• Publication Number:
  US 20200136930A1
• Time in Patent Office: Days
• CPC Class Codes: G06F 2009/45562 Creating, deleting, cloning virtual machine instances
• CPC Class Codes: G06F 2009/45583 Memory management, e.g. access or allocation
• CPC Class Codes: G06F 8/60 Software deployment
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects
• CPC Class Codes: G06F 9/5077 Logical partitioning of resources; Management or configuration of virtualized resources specific details on emulation or internal functioning of virtual machines G06F9/455
• CPC Class Codes: H04L 41/046 comprising network management agents or mobile agents therefor
• CPC Class Codes: H04L 41/0806 for initial configuration or provisioning, e.g. plug-and-play
• CPC Class Codes: H04L 41/0843 based on generic templates
• CPC Class Codes: H04L 41/0895 Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
• CPC Class Codes: H04L 41/40 using virtualisation of network functions or resources, e.g. SDN or NFV entities
• CPC Class Codes: H04L 41/5048 Automatic or semi-automatic definitions, e.g. definition templates
• CPC Class Codes: H04L 41/5054 Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
• CPC Class Codes: H04L 41/5096 wherein the managed service relates to distributed or central networked applications
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416

Abstract

According to at least one embodiment, an application environment is provisioned. In some embodiments, a stack template is accessed in response to a request to provision the application environment, with the stack template defining provider-independent configuration information for a particular stack. A deployment target template corresponding to the stack template is accessed, with the deployment target template defining provider-independent configuration information for middleware. A provisioning workflow is selected based at least on stack provider information indicated by the stack template, with the stack provider information indicating an infrastructure for provisioning the particular stack indicated by the stack template. A stack is provisioned on the infrastructure based on the selected workflow, the stack template, and the stack provider information, and middleware is then on the provisioned stack based on the deployment target template.

Claims

1. A method comprising:

receiving a command to initiate deployment of an application instance;

accessing a particular environment blueprint from a plurality of environment blueprints based on the application indicated in the command, the particular environment blueprint comprising a plurality of component templates corresponding to respective application components, each component template indicating;

a stack template defining provider-independent configuration information for a particular stack, the stack template pointing to particular stack provider information indicating a provisioning infrastructure for the stack; and

a deployment target template defining provider-independent configuration information for middleware to serve as an application deployment target;

provisioning an application environment based on the environment blueprint, wherein the environment comprises multiple application deployment targets, each application deployment target comprising middleware corresponding to a particular deployment target template of the particular environment blueprint that runs on a stack corresponding to a particular stack template of the particular environment blueprint; and

deploying application components on the application deployment targets of the provisioned environment based on the particular environment blueprint.

2. The method of claim 1, wherein provisioning the environment comprises:

provisioning, for each stack template indicated in the particular environment blueprint, a stack on the provisioning infrastructure indicated by the stack provider; and

provisioning, at each provisioned stack, the middleware indicated by the deployment target template.

3. The method of claim 1, wherein provisioning the environment comprises selecting, for each stack template indicated in the particular environment blueprint based at least on the stack provider corresponding to the stack template, a stack provisioning workflow to provision the stack indicated by the stack template.

4. The method of claim 1, wherein at least one component template comprises multiple deployment target templates corresponding to one stack template.

5. The method of claim 1, wherein the stack template comprises information identifying a particular image for use in provisioning the stack.

6. The method of claim 5, wherein the image includes a virtual machine template, a container image, or a virtual appliance template.

7. The method of claim 1, wherein the stack provider information comprises an application programming interface (API) for provisioning a stack on the provisioning infrastructure.

8. The method of claim 1, wherein the stack provider information comprises connection information for the infrastructure provider, comprising one or more of a uniform resource locator (URL) for a daemon, a server address for a hypervisor, and credential information for the infrastructure provider.

9. The method of claim 1, wherein deploying application components on the application deployment targets of the provisioned environment comprises deploying application packages on each stack of the provisioned environment based on an application deployment workflow.

10. The method of claim 1, wherein the particular environment blueprint is formatted according to a JavaScript Object Notation (JSON) format, and includes metadata to describe the configuration information for the stack templates and deployment targets of the particular environment blueprint.

11. The method of claim 1, wherein:

the environment blueprint is accessed in response to a GET command of a Representational State Transfer (REST) API; and

the application environment is provisioned in response to a POST command of the REST API.

12. A non-transitory computer readable medium having program instructions stored therein, wherein the program instructions are executable by a computer system to perform operations comprising:

accessing a stack template in response to a request to provision an application environment, the stack template defining provider-independent configuration information for a particular stack;

accessing a deployment target template corresponding to the stack template, the deployment target template defining provider-independent configuration information for middleware;

selecting a provisioning workflow based at least on stack provider information indicated by the stack template, the stack provider information indicating an infrastructure for provisioning the particular stack indicated by the stack template; and

provisioning a stack on the infrastructure based on the selected workflow, the stack template, and the stack provider information; and

provisioning middleware on the provisioned stack based on the deployment target template.

13. The non-transitory computer readable medium of claim 12, wherein the operations further comprise deploying application software onto the provisioned middleware.

14. The non-transitory computer readable medium of claim 12, wherein the stack template is formatted according to a JavaScript Object Notation (JSON) format, and includes metadata to describe the configuration information for the particular stack.

15. The non-transitory computer readable medium of claim 12, wherein the stack template comprises identifies a virtual machine image, a container image, or a virtual appliance image.

16. The non-transitory computer readable medium of claim 12, wherein the deployment target template is formatted according to a JavaScript Object Notation (JSON) format, and includes metadata to describe the configuration information for the middleware.

17. The non-transitory computer readable medium of claim 12, wherein the provisioning workflow defines a set of operations for provisioning a stack at the stack provider infrastructure.

18. The non-transitory computer readable medium of claim 12, wherein provisioning the stack on the infrastructure comprises using an application programming interface (API) of the stack provider information to provision the stack on the infrastructure.

19. The non-transitory computer readable medium of claim 12, wherein the stack provider information comprises provisioning server information indicating a server address for accessing provisioning resources of the stack provider.

20. A system comprising:

a data processing apparatus;

a memory; and

an environment provisioning manager, executable by the data processing apparatus to;

access a stack template in response to a request to provision an application environment, the stack template defining provider-independent configuration information for a particular stack;

access a deployment target template corresponding to the stack template, the deployment target template defining provider-independent configuration information for middleware;

select one or more provisioning workflows based at least on stack provider information indicated by the stack template, the stack provider information indicating an infrastructure for provisioning the particular stack indicated by the stack template; and

provision a deployment target on infrastructure of the stack provider based on the selected provisioning workflow, the deployment target comprising a stack provisioned on the infrastructure that corresponds to the stack template and middleware on the stack that corresponds to the deployment target template.