Source to image framework for a platform-as-a-service system

US10037196B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-10037196-B2
Application numberUS-201514606311-A
CountryUS
Kind codeB2
Filing dateJan 27, 2015
Priority dateJan 27, 2015
Publication dateJul 31, 2018
Grant dateJul 31, 2018

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

Implementations provide for a source to image framework for a Platform-as-a-Service (PaaS) system. A method of the disclosure includes invoking source-to-image (STI) orchestration logic to perform a build for an application of a multi-tenant PaaS system, launching a build container for the build in view of a base image of the application, the base image providing a core functionality for the application, accessing source code of the application at the build container, assembling an application image using the base image and the source code, and committing the application image to a repository.

First claim

Opening claim text (preview).

What is claimed is: 1. A method, comprising: invoking source-to-image (STI) orchestration logic to perform a build of an application image for an application of a multi-tenant Platform-as-a-Service (PaaS) system, wherein the multi-tenant PaaS system comprises a node layer having a plurality of nodes to deploy the application image for the application; launching, by a processing device using the STI orchestration logic, a build container for implementing the build using a base image providing a core functionality of the application, wherein the build container comprises a resource-constrained process space that is provided in a node of the plurality of nodes of the PaaS system, the resource-constrained process space to execute an assemble script provided by the STI orchestration logic, wherein the assemble script is separate from the base image; accessing, at the build container without user interaction, source code of the application; executing, by the processing device at the build container without user interaction, the assemble script to cause the application image to be assembled by applying the source code to the base image; committing the application image to a repository; and executing, by the processing device using the STI orchestration logic, a run script to cause one or more run-time containers to be launched on the node layer of the multi-tenant PaaS system, the one or more run-time containers separate from the build container on the node layer and used to launch instances of the application image from the repository. 2. The method of claim 1 , wherein the base image is corresponded to the application when the application is registered with the multi-tenant PaaS. 3. The method of claim 1 , further comprising defining behaviors to be executed when using the committed application image to launch the application in the multi-tenant PaaS. 4. The method of claim 3 , wherein the STI orchestration logic comprises run logic to perform the defining the behaviors. 5. The method of claim 1 , wherein the repository is internal to the multi-tenant PaaS. 6. The method of claim 1 , wherein the repository is external to the multi-tenant PaaS. 7. The method of claim 1 , wherein the source code is streamed to the build container. 8. The method of claim 1 , wherein the source code is bind-mounted to the build container. 9. The method of claim 1 , wherein the source code is accessed via a remote Uniform Resource Locator (URL) by the build container. 10. The method of claim 1 , further comprising: accessing the application image subsequent to the committing; generating a new container from the application image, the new container comprising a save artifacts volume; executing a save artifacts script of the STI orchestration logic, the save artifacts script to copy identified build artifacts of the application image into the artifacts volume; and utilizing the artifacts in the artifacts volume in subsequent builds of the application image. 11. The method of claim 1 , wherein the processing device is part of a node that executes multiple applications comprising at least the application, and wherein the multiple applications are owned by different owners. 12. A system, comprising: a memory; a processing device communicably coupled to the memory, the processing device to: invoke source-to-image (STI) orchestration logic to perform a build of an application image for an application of a multi-tenant Platform-as-a-Service (PaaS) system, wherein the multi-tenant PaaS system comprises a node layer having a plurality of nodes to deploy the application image for the application; launch, using the STI orchestration logic, a build container for implementing the build using a base image providing a core functionality of the application, wherein the build container comprises a resource-constrained process space that is provided in a node of the plurality of nodes of the PaaS system, the resource-constrained process space to execute an assemble script provided by the STI orchestration logic, wherein the assemble script is separate from the base image; access, at the build container without user interaction, source code of the application; execute, at the build container without user interaction, the assemble script to cause the application image to be assembled by applying the source code to the base image; commit the application image to a repository; and execute, using the STI orchestration logic, a run script to cause one or more run-time containers to be launched on the node layer of the multi-tenant PaaS system, the one or more run-time containers separate from the build container on the node layer and used to launch instances of the application image from the repository. 13. The system of claim 12 , wherein the base image is corresponded to the application when the application is registered with the multi-tenant PaaS. 14. The system of claim 12 , wherein the processing device further to use the committed application image to launch the application in the multi-tenant PaaS. 15. The system of claim 12 , further comprising: accessing the application image subsequent to the committing; generating a new container from the application image, the new container comprising a save artifacts volume; executing a save artifacts script of the STI orchestration logic, the save artifacts script to copy identified build artifacts of the application image into the artifacts volume; and utilizing the artifacts in the artifacts volume in subsequent builds of the application image. 16. The system of claim 12 , wherein the processing device is part of a node that executes multiple applications comprising at least the application, and wherein the multiple applications are owned by different owners. 17. A non-transitory machine-readable storage medium including instructions that, when accessed by a processing device, cause the processing device to: invoke source-to-image (STI) orchestration logic to perform a build of an application image for an application of a multi-tenant Platform-as-a-Service (PaaS) system, wherein the multi-tenant PaaS system comprises a node layer having a plurality of nodes to deploy the application image for the application; launch, by the processing device using the STI orchestration logic, a build container for implementing the build using a base image providing a core functionality of the application, wherein the build container comprises a resource-constrained process space that is provided in a node of the plurality of nodes of the PaaS system, the resource-constrained process space to execute an assemble script provided by the STI orchestration logic, wherein the assemble script is separate from the base image; access, at the build container without user interaction, source code of the application; execute, by the processing device at the build container without user interaction, the assemble script to cause the application image to be assembled by applying the source code to the base image; commit the application image to a repository; and execute, by the processing device using the STI orchestration logic, a run script to cause one or more run-time containers to be launched on the node layer of the multi-tenant PaaS system, the one or more run-time containers separate from the build container on the node layer and used to launch instances of the application image from the repository. 18. The non-transitory machine-readable storage medium of claim 17 , wherein the processing device is further to use the committed application image to la

Assignees

Inventors

Classifications

  • G06F8/36Primary

    Software reuse · CPC title

  • Version control (security arrangements therefor G06F21/57); Configuration management · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US10037196B2 cover?
Implementations provide for a source to image framework for a Platform-as-a-Service (PaaS) system. A method of the disclosure includes invoking source-to-image (STI) orchestration logic to perform a build for an application of a multi-tenant PaaS system, launching a build container for the build in view of a base image of the application, the base image providing a core functionality for the ap…
Who is the assignee on this patent?
Red Hat Inc
What technology area does this patent fall under?
Primary CPC classification G06F8/36. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Jul 31 2018 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 5 related publications on this page (citations in our corpus or others sharing the same primary CPC).