Browse Prior Art Database

Method for the creation of a standalone package from a continuous delivery pipeline using an orchestrator

IP.com Disclosure Number: IPCOM000239329D
Publication Date: 2014-Oct-30
Document File: 6 page(s) / 275K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is a method, applicable to a continuous delivery (DevOps) pipeline, through which a specific deployment can be exported from the orchestrator tool into another deployment technology of choice. The core idea is to create a standalone installer by extending the orchestrator and leveraging the deployment process definition within the orchestrator to collect the assets and define the actions that need to be taken.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 49% of the total text.

Page 01 of 6

Method for the creation of a standalone package from a continuous delivery pipeline using an orchestrator

A continuous delivery(DevOps) pipeline using an orchestration tool is the new norm for delivering software to users in the public cloud. Such processes are piecemeal, relying directly upon an automated build to provide the artifacts to be deployed, and any code to perform the actual deployment is written and stored within the orchestration tool .

In practice, consumers of the software might want to take one of those rigorously tested production deployments and deploy it into an isolated on premise environment with an existing, mature deployment framework that makes no use of the orchestration tool . Often consumers attempt this in secure environments where restrictions exist in the tools that can be used . The problem, then, is that such endeavors increase engineering costs for both the provider and consumer. The provider has to make an investment in

writing specific installation technology(and locking down clients in technology choice) to perform an on premise installation; the consumer needs to invest in adapting an existing framework to handle a new type of installation technology. In addition, organizations with multiple product lines or streams, or with third-party componentized offerings need to find ways to align the continuous delivery processes (DevOps) with more traditional install patterns.

The solution is a method through which a specific deployment (e.g., last week's deployment) can be exported from the orchestrator tool into another deployment technology of choice, such as a scripting language or other installation technology. The core idea of the solution is to create a standalone installer by extending the orchestrator and leveraging the deployment process definition

within the orchestrator to collect the assets and define the actions that need to be taken .

Existing prior art assumes that the installation is derived before the solution is deployed into production . In a cloud environment

where speed is of the essence, the installation process is often defined within an orchestrator and not defined within a standalone installation technology. Creating a standalone installer from a successful deployment in production can be accomplished through the orchestrator using the novel method described herein.

Figure 1: An orchestrator with four deployment projects and an available build of the artifacts in one of those deployment projects

1


Page 02 of 6

Figure 1 illustrates an orchestrator with four deployment projects and an available build of the artifacts in one of those deployment projects. Within a deployment project, a series of steps are defined in order to deploy a given application. In "Deploy Project 1", the method defines five steps. The first three steps are downloading files onto the location machine and the last two steps are

2


Page 03 of 6

running enterprise software commands to deploy and configure the...