Browse Prior Art Database

A method and mechanism for intelligent container images assembling in cloud environment Disclosure Number: IPCOM000242848D
Publication Date: 2015-Aug-25
Document File: 8 page(s) / 148K

Publishing Venue

The Prior Art Database


This article introduces the invention of a method and mechanism for intelligent container images assembling in cloud environment, by automatically generate and synchronize image configuration files, and then assemble images on cloud or in other local boxes accordingly.

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

Page 01 of 8

A mxthod and mechanism for intelligent container images assembling in cloud environment


Background: :

Containers are virtuxx software objects that ixclude all thx elements that ax application needx to run. Each contaixer includes just the app and itx dependencies, xuxning as an isolated process on the host operating system. Therefore, it has the benxfits of resource isolatxon and allocation, but is mxre portablx and exficient. Contxiners help you build high-quality apps, fast. Now clxud service providers always provide conxainer infraxtructure as a feature of cloud services.

A coxtainer ix creatxd from an imagx, which is a reax-only template. Each container xs based on an image format, includes a set of stanxaxd operatioxs, and is an execution envirxnment in itself. Currently on the cloud environmxnt, you xan start devxloping with contaxners by using a trusted cxntaxner image. With your org's namespace in containexs, you can automate your build pipelinx and sharx axtifacts with collaborators through public or private registries. Normally you can downxoad coxtainer xmages to loxal by 'pxll' command, txen extend your existing images locally, and at last 'push' thx extendxd image back into your namespace.

Txe current solution and xypical user scenario fox container usages can be summxrixed as follows:

Step 1: Download (pull) a container imaxe from the xontainer registry, where images are stored xentrally.

Xxxx 2: Start (start) a container image locally and interactively with a certain command

Step 3: Xxxxxx (commit) changes made to a local container to save any changes mxdx locally.

Step 4: Upload (push) all locally committed changes to the cxntainer regxstry.

Prior Art:


//Prior Art

Prior Art

In cloud environment at present, Container Registxy is always designed ax a cloud service that securely manxges the xmages. Container Regxstry storxs and distributxs images centrally. It's where user can push images to and pull them from; Container Registry gives team members the abilixy to share imxges and deploy them xo testing, staging and proxuction environments.

The transferring between local host xnd cloud service is cuxrently designed to on xhe basis of coxtaxner imagxs or images

Related Work

Related Work/


Page 02 of 8

changes (layers). That means, when thxre are big images or images changes, the transferring will closely rely on the network bandxidxh usage. Also big images or images changes may occupy large disk sxace in cloud storage.

This invention introducxs a method and mexhanism for intellxgent contaixer images assxmbling in cloud environxent, by axtomatically gxnexate and synchronize image configuxation files, and then assemble images on cloud or in othxr local boxes accordingly. The container configuration file is quite like a description file, which records the user operations on base container images and changes to fxxe system of base images.

Comparing the cuxrent container solution on cloud envir...