Source to image transformation pipeline for a platform-as-a-service system

Implementations provide for a source to image transformation pipeline for a Platform-as-a-Service (PaaS) system. A method of the disclosure includes receiving a request to create an application for execution on a multi-tenant PaaS system, introspecting received source files associated with the application to identify at least one of a language or a framework corresponding to the application, identifying a build image corresponding to the identified at least one of the language or the framework, constructing a build configuration object, a deployment configuration object, and a networking configuration object for the application, and transmitting, by the processing device, the build configuration object, the deployment configuration object, and the networking configuration object to a master layer of the multi-tenant PaaS system to enable the multi-tenant PaaS system to build and deploy the application at one or more nodes of the multi-tenant PaaS system.

TECHNICAL FIELD

The implementations of the disclosure relate generally to Platform-as-a-Service (PaaS) systems and, more specifically, relate to a source to image transformation pipeline for a PaaS system.

BACKGROUND

A variety of Platform-as-a-Service (PaaS) system offerings exists that include software and/or hardware facilities for facilitating the execution of web applications in a cloud computing environment (the “cloud”). Cloud computing is a computing paradigm in which a customer pays a “cloud provider” to execute a program on computer hardware owned and/or controlled by the cloud provider. It is common for cloud providers to make virtual machines (VMs) hosted on their computer hardware available to customers for this purpose.

The cloud provider typically provides an interface that a customer can use to requisition virtual machines and associated resources such as processors, storage, and network services, etc., as well as an interface a customer can use to install and execute the customer's program on the virtual machines that the customer requisitions, together with additional software on which the customer's program depends. For some such programs, this additional software can include software components, such as a kernel and an operating system, and/or middleware and a framework. Customers that have installed and are executing their programs “in the cloud” typically communicate with the executing program from remote geographic locations using Internet protocols.

PaaS offerings facilitate deployment of web applications without the cost and complexity of buying and managing the underlying hardware and software and provisioning hosting capabilities, providing the facilities to support the complete lifecycle of building and delivering web applications and services entirely available from the Internet. Typically, these facilities operate as one or more VMs running on top of a hypervisor in a host server.

DETAILED DESCRIPTION

Implementations of the disclosure provide for a source to image transformation pipeline for a Platform-as-a-Service (PaaS) system. Implementations provide a new PaaS application creation component that is implemented as part of a PaaS system. The PaaS application creation component can be implemented on client devices utilizing the PaaS system and/or on a server device executing a master layer of the PaaS system. In one implementation, the PaaS application creation component provides a tool to help automatically build and deploy a new application on the PaaS system with minimal to no manual intervention.

The PaaS application creation component simplifies the process for building and deploying an application in the PaaS system by analyzing an existing set of application source files (“source”) and determining a build strategy for building the source, based on the language and framework the source appears to use. The PaaS application creation component then identifies an appropriate build image that is capable of building source, using the determined build strategy, for that particular language/framework into a new application image that can be deployed on the PaaS system. An image, such as a build image, refers to data representing executables and files of an application used to deploy functionality for a runtime instance of the application. In one implementation, a build image is an ordered collection of root filesystem changes and the corresponding execution parameters for use within a container runtime. An image typically contains a union of layered filesystems stacked on top of each other. An image does not have state and it does not change.

Next, the PaaS application creation component defines a build configuration, which takes as input the source and the identified build image, to generate the new application image. In addition to the build configuration, the PaaS application creation component also constructs a deployment configuration that takes as an input the new application image and, when the deployment configuration is executed, results in that application image being run on a deployment system of the PaaS (a system capable of running containerized application images). The PaaS application creation component defines networking configuration that enables the running application as created by the deployment to be accessible by users. The build configuration, deployment configuration, and networking configurations are all provided as objects for building, deploying, and running the application being created on the PaaS system.

Previous solutions generally have not provided an automated process to build and deploy a running application in a multi-tenant PaaS system using as input the source code from the end user (e.g., an application developer). Prior PaaS solutions dictated that the end user provide the manual specification of the build image to use to build the source files into a new application image. In addition, in prior PaaS solutions, the end user would also have to manually deploy any built application images to the deployment system and provide the proper networking configurations (e.g., routing, etc.) for other users to access the running application. Implementations of the disclosure automatically combine inputted source files with the appropriate build images, linking this together with configurations that allow the PaaS system to build and deploy a running application without any other interaction from the end user.

FIG. 1is a block diagram of a network architecture100in which implementations of the disclosure may operate. The network architecture100includes a cloud130managed by a cloud provider system104. The cloud provider system104provides nodes111,112,121,122to execute software and/or other processes. In some implementations, these nodes are virtual machines (VMs) that are hosted on a physical machine, such as host1110through host N120, configured as part of the cloud130. For example, nodes111and112are hosted on physical machine110in cloud130provided by cloud provider104. When nodes111,112,121,122are implemented as VMs, they may be executed by OSes115,125on each host machine110,120. Users can interact with applications executing on the cloud-based nodes111,112,121,122using client computer systems, such as clients160,170and180, via corresponding web browser applications161,171and181.

In some implementations, the host machines110,120are often located in a data center. In other implementations, the applications may be hosted directly on hosts1through N110-120without the use of VMs (e.g., a “bare metal” implementation), and in such an implementation, the hosts themselves are referred to as “nodes”.

Clients160,170, and180are connected to hosts110,120in cloud130and the cloud provider system104via a network102, which may be a private network (e.g., a local area network (LAN), a wide area network (WAN), intranet, or other similar private networks) or a public network (e.g., the Internet). Each client160,170,180may be a mobile device, a PDA, a laptop, a desktop computer, a tablet computing device, a server device, or any other computing device. Each host110,120may be a server computer system, a desktop computer or any other computing device. The cloud provider system104may include one or more machines such as server computers, desktop computers, etc.

In one implementation, the cloud provider system104is coupled to a cloud controller108via the network102. The cloud controller108may reside on one or more machines (e.g., server computers, desktop computers, etc.) and may manage the execution of applications in the cloud130. In some implementations, cloud controller108receives commands from PaaS system controller140. Based on these commands, the cloud controller108provides data (e.g., such as pre-generated images) associated with different applications to the cloud provider system104. In some implementations, the data may be provided to the cloud provider104and stored in an image repository106, in an image repository (not shown) located on each host110,120, or in an image repository (not shown) located on each VM111,112,121,122. This data may be used for the execution of applications for a multi-tenant PaaS system managed by the PaaS provider controller140.

Upon receiving a command identifying specific data (e.g., application data and files used to initialize an application on the cloud), the cloud provider104retrieves the corresponding data from the image repository106, creates an instance of it, and loads it to the host110,120to run on nodes111,112,121,122. In addition, a command may identify specific data to be executed on one or more of the nodes111,112,121, and122. The command may be received from the cloud controller108, from the PaaS system controller140, or a user (e.g., a system administrator) via a console computer or a client machine. The image repository106may be local or remote and may represent a single data structure or multiple data structures (databases, repositories, files, etc.) residing on one or more mass storage devices, such as magnetic or optical storage based discs, solid-state-drives (SSDs) or hard drives.

In one implementation, client devices160-180may include a PaaS application creation component165that automatically builds and deploys new applications on the nodes111,112,121,122of the PaaS system with minimal end user interaction. In some implementations, the PaaS application creation component165may alternatively operate on the PaaS system controller140, or may operate on a combination of the client devices160-180and PaaS system controller140.

The PaaS application creation component165simplifies the process for building and deploying an application in the PaaS system by receiving specification of source files (“source”) from an end user and analyzing the specified source. Based on the analysis of the source, the PaaS application creation component165identifies build images to associate with the source, constructs a build configuration that builds the source into a new application image, constructs a deployment configuration that deploys the new image, and constructs a networking configuration to allow the running application to be accessible. The build configuration, deployment configuration, and networking configurations are all provided as objects that can build, deploy, and run the application being created on the PaaS system.

In one implementation, nodes111,112,121,122may include a source to image (STI) component150that utilizes the output objects (build configuration, deployment configuration, and networking configuration) to build and deploy a running application on the nodes111,112,121,122using the end-user provided source. The STI component150provides a logic framework to produce ready-to-run application images for applications of the PaaS system. The STI component150may utilize the build configuration, deployment configuration, and networking configuration created by the PaaS application creation component165to generate a usable runtime image for the application in the PaaS system. In one implementation, the STI component150may utilize a Docker™ tool to build an application image, which is then referred to as a Docker image. Further details of PaaS application creation component165and its related workflows can be found below with respect toFIG. 2 through 5.

While various implementations are described in terms of the environment described above, those skilled in the art will appreciate that the facility may be implemented in a variety of other environments including a single, monolithic computer system, as well as various other combinations of computer systems or similar devices connected in various ways. For example, the data from the image repository106may run directly on a physical host110,120instead of being instantiated on nodes111,112,121,122. In some implementations, an environment other than a VM may be used to execute functionality of PaaS applications. As such, in some implementations, a “node” providing computing functionality may provide the execution environment for an application of the PaaS system. The “node” may refer to a VM or any other type of computing environment.

FIG. 2is a block diagram of a multi-tenant PaaS system architecture200according to an implementation of the disclosure. The PaaS architecture200allows users to launch software applications in a cloud computing environment, such as cloud computing environment provided in network architecture100described with respect toFIG. 1. The PaaS system architecture200, in one implementation, includes a client layer210, a PaaS master layer220, and a node layer230.

In one implementation, the components of the PaaS system architecture are in communication with each other via a network (not shown). The network may include, for example, the Internet in one implementation. In other implementations, other networks, wired and wireless, such as an intranet, local area network (LAN), wide area network (WAN), or broadcast network may be used.

In one implementation, the client layer210is a collection of components that reside on a client machine, such as a workstation of a software developer, and provide an interface to a user of the client machine to the PaaS master layer220of the PaaS system200. In one implementation, the client machine can be a client160,170,180described with respect toFIG. 1. The PaaS master layer220is a collection of components that may facilitate the creation and deployment on the cloud (via node layer230) of software applications being developed by an end user at client layer210. In one implementation, the PaaS master layer220may comprise components executing on one or more server devices.

In one implementation, the client layer210includes a source code management system212, sometimes referred to as “SCM” or revision control system. One example of such an SCM or revision control system is Git, available as open source software. Git and other such distributed SCM systems typically include a working directory for making changes, and a local software repository for storing the changes for each application associated with the end user of the PaaS system200. The packaged software application can then be “pushed” from the local SCM repository to a remote SCM repository, such as repositories233a,233b,233c, at the node(s)232a,232b,232crunning the associated application. From the remote SCM repository233a,233b,233c, the code may be edited by others with access, or the application may be executed by a machine. Other SCM systems work in a similar manner.

The client layer210, in one implementation, also includes a set of command line tools214that a user can utilize to create, launch, and manage applications. In one implementation, the command line tools214can be downloaded and installed on the user's client machine, and can be accessed via a command line interface or a graphical user interface, or some other type of interface. In one implementation, the command line tools214expose an application programming interface (“API”) of the PaaS master layer220and perform other applications management tasks in an automated fashion using other interfaces, as will be described in more detail further below in accordance with some implementations.

In one implementation, the PaaS master layer220acts as middleware between the client layer210and the node layer230. The node layer230is a collection of components that includes the nodes232a-con which applications235a-bare provisioned and executed. In one implementation, each node232a-cis a VM. In some implementations, the VMs are provisioned by an Infrastructure as a Service (IaaS) provider. In other implementations, the nodes232a-cmay be physical machines or VMs residing on a single physical machine. In one implementation, the PaaS master layer220is implemented on one or more machines, such as server computers, desktop computers, etc. In some implementations, the PaaS master layer220may be implemented on one or more machines separate from machines implementing each of the client layer210and the node layer230, or may be implemented together with the client layer210and/or the node layer230on one or more machines, or some combination of the above.

In one implementation, the PaaS master layer220includes a PaaS master component222that coordinates requests from the client layer210with actions to be performed at the node layer230. Examples of the requests can include a request to create an application, a request to perform an action on a container (e.g., creating, removing, and/or managing a container), a request to deploy source code of an application, a request to designate a system to host a remote SCM repository (e.g., an indication that a system has been designated by a user to host a remote SCM repository), etc.

In one implementation, a user, using the command line tools214at client layer210, can request the creation of a new application235a-b, deployment of source code of the application235a-b, the designation of a system that hosts a remote SCM repository, etc. In response to receiving such a request, the PaaS master component222may first authenticate the user using an authentication service224. In one implementation, the authentication service224may comprise custom authentication methods, or standard protocols such as SAML, Oauth, etc. Once the user has been authenticated and allowed access to the system by authentication service224, the PaaS master component222uses a server orchestration system226to collect information and configuration information about the nodes232a-c.

The server orchestration system226, in one implementation, functions to coordinate server-client interaction between multiple (sometimes a large number of) servers. In one implementation, the servers being orchestrated are nodes232a-c, which are acting as application servers and web servers.

In one implementation, the PaaS master component222manages the business logic and model representing the nodes232a-cand the applications235a-bresiding on the nodes, and acts as a controller that generates the actions requested by users via an API of the command line tools214. The server orchestration system226then takes the actions generated by the PaaS master component222and orchestrates their execution on the many nodes232a-cmanaged by the system.

In one implementation, the information collected about the nodes232a-ccan be stored in a data store228. In one implementation, the data store228can be a locally-hosted database or file store, or it can be a cloud-based storage service provided by a Software-as-a-Service (SaaS) provider. The PaaS master component222uses the information about the nodes232a-cand their applications235a-bto model the application hosting service and to maintain records about the nodes. In one implementation, data of a node232a-cis stored in the form of a JavaScript™ Object Notation (JSON) blob or string that maintains key-value pairs to associate a unique identifier, a hostname, a list of applications, and other such attributes with the node.

In implementations of the disclosure, the PaaS system architecture200ofFIG. 2is a multi-tenant PaaS environment. In a multi-tenant PaaS environment, each node232a-cruns multiple applications235a-bthat may be owned or managed by different users and/or organizations. As such, a first customer's deployed applications235a-bmay co-exist with any other customer's deployed applications on the same node232that is hosting the first customer's deployed applications235a-b. In some implementations, portions of an application execute on multiple different nodes232a-c. For example, as shown inFIG. 2, components of application1235arun in both node232aand node232b. Similarly, components of application2235bmay run in node232band node232c.

In one implementation, each node232a-cis implemented as a VM and has an operating system234a-cthat can execute applications235a-cusing the repositories233a-cthat are resident on the nodes232a-c. Each node232a-calso includes a server orchestration system agent (not shown) configured to track and collect information about the node232a-cand to perform management actions on the node232a-c. The server orchestration system agent may operate in tandem with the server orchestration system226to send requests, queries, and commands between the node232a-cand the PaaS master layer220.

In one implementation, the client layer210may include a PaaS application creator component165. The PaaS application creator component165may be the same as its counterpart described with respect toFIG. 1. The PaaS application creator component165may alternatively be implemented as part of the PaaS master layer220, or may be implemented as part of a combination of the client layer210and the PaaS master layer220. As discussed above, the PaaS application creation component165simplifies the process for building and deploying an application in the PaaS system200by receiving specification of source files (“source”) from an end user and analyzing the specified source. Based on the analysis of the source, the PaaS application creation component165identifies build images to associate with the source, constructs a build configuration that builds the source into a new application image, constructs a deployment configuration that deploys the new image, and constructs a networking configuration to allow the running application to be accessible. The build configuration, deployment configuration, and networking configurations are all provided as objects that can build, deploy, and run the application being created on the PaaS system.

In one implementation, nodes232a-cmay include an STI component250. STI component250may be the same as STI component150described with respect toFIG. 1. STI component250may utilize the output objects (build configuration, deployment configuration, and networking configuration) of the PaaS application creator component165to build and deploy a running application on the nodes232a-cusing the end-user provided source. The STI component250provides a logic framework to produce ready-to-run application images for applications235a-cof the PaaS system. The STI component250may utilize the build configuration, deployment configuration, and networking configuration created by the PaaS application creation component165to generate a usable runtime image for the application in the PaaS system. Further details of the automated application creation process are described below with respect toFIG. 3.

Each application image may map to a functional component of the application235a-c. As such, an application may have more than one application image associated with the application. The application images include support software providing functionality (e.g., configuration templates, scripts, dependencies, etc.) used to run the application235a-cand/or add a feature to the application235a-c. For example, the images may support languages such as, but not limited to, Java™, PHP, Ruby, Python, Perl, and so on. In addition, application images may be generated that support databases, such as MySQL™ PostgreSQL™, Mongo™, and others. Application images may also be generated that support build and continuous integration environments, such as a Jenkins-based image. Lastly, application images may be generated to support management capabilities and/or tools, such as PHPmyadmin, RockMongo™, 10gen-mms-agent, cron scheduler, HAProxy, Maven, and Gradle for example.

Once STI component250builds an application image, the application image may be committed to a repository, such as repository233a-cor to a remote repository (not shown) outside of nodes232a-c. The committed application image may then be used to subsequently launch the application235a-c.

As discussed above, the application images include the underlying support software that implements the functionality of applications235a-c. In one implementation, an application235a-cmay utilize one or more resource-constrained containers240on nodes232a-cusing instances of application image. A container240is a resource-constrained process space on the node232a-cto execute functionality of an application235a-c. In some implementations, a container240is established by the node232a-cwith resource boundaries, including a limit and/or designation of the amount of memory, amount of storage, and security types and/or labels to be applied to any functions executed by the container240. In one implementation, containers240may be established using Linux Containers (LXC) or Docker containers. In further implementations, containers240may also be established using more primitive features, such as cgroups, SELinux™, and kernel namespaces, to name a few examples.

Application image instances for an application235a-cmay be launched in containers240dispersed over more than one node232a-b. In other implementations, application images instances for an application235a-cmay run in one or more containers240on the same node232a-c. Furthermore, an application235a-cmay use more than one application image240as part of providing functionality for the application235a-c. One example of this is a JavaEE™ application that uses a JBoss™ application server-based application image with a supporting MySQL™ database provided by a MySQL™-based application image.

FIG. 3is a block diagram of a communication architecture300of a multi-tenant PaaS providing a source to image transformation pipeline for applications of the multi-tenant PaaS system according to an implementation of the disclosure. Architecture300includes the PaaS master component222in communication with a client320and node layer310. Node layer310includes STI orchestration component250, repository233, and application350(which includes container360and380distributed across one or more nodes of node layer310). Client320includes a PaaS application creator component165. PaaS application creator component165, PaaS master component222, STI orchestration component250, and repository233may be the same as their counterparts described with respect toFIG. 2.

In one implementation, the PaaS application creator component165would receive a request to create a new application. The request may be received via a CLI or via a web console interface provided by the PaaS system via the client device320. The request received at the PaaS application creator component165includes specification of source files (“source”) for the new application. The source files may include source code, images, or templates. A template is a set of objects that can be parameterized and processed to produce a list of objects for creation by the PaaS system.

The PaaS application creator component165includes image locator logic352that first determines a build strategy for building the source, based on the language and framework that the source appears to use. The image locator logic352can introspect the specified source to determine the language and framework of the source. A build is the process of transforming input parameters into a resulting object. The build process is often used to transform source code into a runnable image. A build strategy defines the type of build supported by the PaaS system, including the commands used by the build, and the repositories and artifacts expected to be used by the build. One example build strategy is a Docker build strategy. Another example build strategy is a source strategy. The type of build strategy to define for the source may be based on the files found in the specified source (e.g., if a Dockerfile is found in a repository of the source, then a Docker build strategy is specified). Furthermore, the presence of certain marker files in the source can also be used to determine the language and/or framework to associate with the source (e.g., presence of a Gemfile in the source would indicate the Ruby language).

The image locator logic352then identifies an appropriate build image that is capable of building the source, using the determined build strategy, for that particular language/framework into a new application image that can be deployed on the PaaS system. The image locator logic352may look for images in a local registry, a public registry, or stored at a server of the PaaS system. In some implementations, if multiple possible matches for build images are found, the image locator logic352may apply weights to the different images based on, for example, how accurately the name matches to the determined language/platform of the source. Other factors contributing to a weight may include how accurate of a match metadata information of the located build image has with the determined language/platform of the source. The weights may then be used to apply scores to each potential build image for purposes of determining a highest scoring build image to select for the source.

Once a build image is selected, build config logic354of the PaaS application creation component165defines a build configuration. The build configuration is an object that defines the entire build process. The build configuration may also be referred to as a build configuration object. The generated build configuration takes as input the source and the identified build image and generates a new application image. The build configuration specifies the build strategy to use, the source location, and the build output location. For the build configuration, two image streams may be created: one to represent the input image (the build image) and another to represent the output image. In one implementation, the build configuration is a REST object that can be used in a POST to the PaaS server to create the new application image instance.

In addition to the build config logic354, the PaaS application creation component165also includes deployment config logic356that constructs a deployment configuration. The deployment configuration is an object that defines details of the deployment, such as replication control definitions, triggers for creating new deployments automatically, strategy for transitioning between deployments, and lifecycle hooks. The deployment configuration may also be referred to as a deployment configuration object. The deployment configuration takes as an input the new application image and, when the deployment configuration is executed, results in that application image being run on a deployment system of the PaaS (a system capable of running containerized application images). The deployment configuration is created either to deploy the output of a build, or a specified image.

In some implementations, the deployment configuration object causes the new application image to be analyzed and determines if the image declares a “volume”. A volume may refer to a mounted file system that is available to the application and which may be backed by a number of node-local or network attached storage endpoints. If the new application image does declare one or more volumes, then the deployment configuration object can match the volume to attached storage in the PaaS, which then provides persistent storage for the application, located at a file path defined by the volume declaration.

The PaaS application creation component165further includes networking config logic358that defines networking configuration that enables the running application as created by the deployment to be accessible by users. The networking configuration may also be referred to as a networking configuration object. The networking configuration attempts to detect exposed ports in the source. It uses the lowest numeric exposed port to generate a service that exposes the port.

Once generated, the build configuration, deployment configuration, and networking configurations are all provided as objects that can build, deploy, and run the application being created on the PaaS system. In one implementation, the build configuration, deployment configuration, and networking configuration are passed to PaaS master component222. PaaS master component222would then invoke STI orchestration component250. STI orchestration component250may use the build configuration to inject the source (identified in the build configuration) for an application into a base image providing core functionality for the application (e.g., also identified in the build configuration) in order to assemble an application image (i.e., base image+source code) for running the application on the PaaS system.

In one implementation, STI orchestration component250may launch a build container360. The build container360may be a resource-constrained process space on the node layer310that executes the received build configuration object to combine the build image362and the source364to create the new application image. In some implementations, build container360is established with resource boundaries, including a limit and/or designation of the amount of memory, amount of storage, and security types and/or labels to be applied to any functions executed by the build container360.

The build image362may be maintained in a repository of the multi-tenant PaaS, such as repository233of node layer310, or in a remote repository305maintained outside of node layer310. As discussed above, the build image362may be associated with core functionality of the application, such as application frameworks including, but not limited to, PHP™, Ruby™, J2EE™, and so on.

Logic of the build container360may then apply the application source364(e.g., binaries, zipped source, source code, etc.) to the build image362to build or assemble the new application image. The application source364may be provided to build container360through various delivery methodologies. In one implementation, the application source364may be streamed, for example, as a TAR file to the build container360. The application source364may be streamed from a client device of an end user, or from another remote location indicated by the user. In another implementation, the application source364may be bind-mounted to the build container360. In a further implementation, the application source364may be accessed or downloaded using a remote Uniform Resource Locator (URL) provided to build container360. When the new application image is built, the logic run by build container360causes the application image to be committed to a repository233,305.

The STI orchestration component250may also use the deployment configuration and the networking configuration to cause the assembled application image to be deployed on the node layer310. The deployment configuration and the networking configuration may cause the committed application image370to be used to subsequently launch the application350. As discussed above, the deployment configuration provided by PaaS application creator component165defines behaviors to be executed when one or more runtime containers380A-Z are launched from the committed application image370. Multiple runtime containers380A-Z may launch using instances370a-zof built application image370in order to scale up the functionality provided by application image370in application350.

FIG. 4is a flow diagram illustrating a method400for a PaaS application creation component to provide a source to image transformation pipeline for a PaaS system according to an implementation of the disclosure. Method400may be performed by processing logic that may comprise hardware (e.g., circuitry, dedicated logic, programmable logic, microcode, etc.), software (such as instructions run on a processing device), firmware, or a combination thereof. In one implementation, method400is performed by PaaS application creator component165, ofFIGS. 2 and 3.

Method400begins at block410where a request is received to create a new application to run on a PaaS system. Then, at block420, specification of source files associated with the new application are received. At block430, the source files are introspected. Subsequently, at block440, application requirements are identified based on the introspection of the source files.

At block,450, a build image corresponding to the identified application requirements is located. Then, at block460, a build configuration is constructed. The build configuration uses the source files and the located build image as inputs to produce a new application image. Then, at block470, a deployment configuration is constructed to cause the new application image to run on a deployment system of the PaaS system. At block480, a networking configuration is defined to enable a running application, as created by a deployment of the new application image, to be accessible. Lastly, at block490, the build configuration, deployment configuration, and networking configuration are outputted as objects to the PaaS system. These objects may then be used for a subsequent build and deployment of the application on the PaaS system.

FIG. 5is a flow diagram illustrating a method500for building and deployment of an application on a PaaS system using a source to image transformation pipeline according to an implementation of the disclosure. Method500may be performed by processing logic that may comprise hardware (e.g., circuitry, dedicated logic, programmable logic, microcode, etc.), software (such as instructions run on a processing device), firmware, or a combination thereof. In one implementation, method500is performed by STI orchestration component250, ofFIGS. 2 and 3.

Method500begins at block510where a build configuration object is received from a PaaS application creation component. At block520, a new application image is built from source file using a build image, where the source files and build image are both specified in the build configuration object. In one implementation, the new application image is built using a build strategy that is also identified in the build configuration.

Then, at block530, a deployment configuration is received from the PaaS application creation component. At block540, the new application image is deployed on the PaaS system according to the deployment configuration object. Subsequently, at block550, a networking configuration object is received from the PaaS application creation component. At block560, network configurations are applied to the deployed application image according to the networking configuration object. In some implementations, the build, deployment, and networking configurations may all be received at the same time or separately.

The computer system600includes a processing device602, a main memory604(e.g., read-only memory (ROM), flash memory, dynamic random access memory (DRAM) (such as synchronous DRAM (SDRAM) or DRAM (RDRAM), etc.), a static memory606(e.g., flash memory, static random access memory (SRAM), etc.), and a data storage device618, which communicate with each other via a bus630.

The computer system600may further include a network interface device608communicably coupled to a network620. The computer system600also may include a video display unit610(e.g., a liquid crystal display (LCD) or a cathode ray tube (CRT)), an alphanumeric input device612(e.g., a keyboard), a cursor control device614(e.g., a mouse), and a signal generation device616(e.g., a speaker).

The data storage device618may include a machine-accessible storage medium624on which is stored software626embodying any one or more of the methodologies of functions described herein. The software626may also reside, completely or at least partially, within the main memory604as instructions626and/or within the processing device602as processing logic626during execution thereof by the computer system600; the main memory604and the processing device602also constituting machine-accessible storage media.

The machine-readable storage medium624may also be used to store instructions626to implement PaaS application creation component165to provide a source to image transformation pipeline for a PaaS system in a computer system, such as the computer system described with respect toFIG. 1, and/or a software library containing methods that call the above applications. While the machine-accessible storage medium628is shown in an example implementation to be a single medium, the term “machine-accessible storage medium” should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions. The term “machine-accessible storage medium” shall also be taken to include any medium that is capable of storing, encoding or carrying a set of instruction for execution by the machine and that cause the machine to perform any one or more of the methodologies of the disclosure. The term “machine-accessible storage medium” shall accordingly be taken to include, but not be limited to, solid-state memories, and optical and magnetic media.

In the foregoing description, numerous details are set forth. It will be apparent, however, that the disclosure may be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form, rather than in detail, in order to avoid obscuring the disclosure.

The terms “first”, “second”, “third”, “fourth”, etc. as used herein are meant as labels to distinguish among different elements and may not necessarily have an ordinal meaning according to their numerical designation.