WO2021013248A1 - 容器分层部署方法及系统 - Google Patents
容器分层部署方法及系统 Download PDFInfo
- Publication number
- WO2021013248A1 WO2021013248A1 PCT/CN2020/104491 CN2020104491W WO2021013248A1 WO 2021013248 A1 WO2021013248 A1 WO 2021013248A1 CN 2020104491 W CN2020104491 W CN 2020104491W WO 2021013248 A1 WO2021013248 A1 WO 2021013248A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- software package
- docker
- public
- container
- characteristic
- Prior art date
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45562—Creating, deleting, cloning virtual machine instances
Definitions
- the present disclosure relates to, but is not limited to, the computer field.
- Computer system virtualization has many advantages. An important benefit is to improve the utilization efficiency of hardware resources. Embedded devices also face the choice of virtualization. Compared with traditional virtual machines, Docker has lower overhead, faster startup, and better performance. It is currently the most widely used virtualization technology.
- Docker is an open source application container platform, based on this platform, you can develop-deploy-run (developing, shipping, and running) applications.
- the container can create an isolated program running space in user mode, in which to run specified user mode programs and dependencies, so as to isolate different applications and isolate Unusual influence.
- the traditional way of deploying Docker has the following problems: there are a lot of redundant content between multiple image files in the same system, resulting in a very large version file, a long version build time, and a large number of disks on the main control board after the version file is loaded to the device.
- Space using a registry to manage images will consume a lot of memory resources. Each image needs to be loaded into the memory on the main control first, and then pushed to the registry, which consumes two more memory. When there are many mirror images, the memory of the main control board will be overwhelmed.
- you push the mirror from the local to the registry you need to perform conflict detection at each layer of the mirror, which consumes CPU resources.
- the embodiment of the present disclosure provides a container layered deployment method, including: each functional single board downloads version files from the disk of the main control single board, where the version files may include: basic image files, public software packages, and characteristic software packages ; And each functional single board is based on the basic image file, the public software package and the characteristic software package for the hierarchical creation of containers.
- the embodiment of the present disclosure also provides a container hierarchical deployment system, which is set on each functional single board and includes: a download module for downloading version files from the disk of the main control single board, where the version files may include: basic image files , Public software packages, and feature software packages; and a container creation module, used for hierarchical creation of containers based on basic image files, public software packages, and feature software packages.
- the embodiment of the present disclosure further provides a computer-readable storage medium on which a computer program is stored.
- the processor implements the container layered deployment method according to the embodiment of the present disclosure.
- Figure 1 is a schematic diagram of Docker components in related technologies
- Figure 2 is a schematic diagram of mirror image composition in related technologies
- Figure 3 is a diagram showing the composition of telecommunication equipment in related technologies
- Figure 4 is a schematic diagram of a traditional Docker deployment method in related technologies
- Fig. 5 is a flowchart of a container layered deployment method according to an embodiment of the present disclosure
- Fig. 6 is a schematic diagram of an improved Docker container deployment according to an embodiment of the present disclosure.
- Fig. 7 is a schematic diagram of a container layered deployment system according to an embodiment of the present disclosure.
- Docker uses a C/S architecture.
- the client and server can run on the same machine or on different hosts. RESTful APIs are used to interact between them.
- the Docker client provides management tools to manage images, containers, networks, data volumes, etc. Users interact with the Docker server (ie, Docker daemon) through these tools. Docker daemon generally runs in the background of the host, waiting to receive messages from the client.
- an embodiment of the present disclosure proposes a container layered deployment method.
- the Docker client receives the basic image, public software packages, and feature software packages, processes the public software packages and feature software packages on the Docker server, integrates them into the basic image, and dynamically generates container instances.
- FIG. 5 is a flowchart of a container layered deployment method according to an embodiment of the present disclosure. As shown in FIG. The deployment method may include step 501 to step 502.
- each functional single board downloads a version file from the disk of the main control single board, where the version file may include: a basic image file, a public software package, and a feature software package.
- step 501 the following preparations can be performed.
- the basic image baseimage.tar that is, the above-mentioned basic image file
- the basic image has only the root file system; make the common software of each board into a common TAR package or a Docker image package common.tar (that is, The above-mentioned public software package), the software specific to each board is made into a common TAR package or a Docker image package boardx.tar (ie, the above-mentioned characteristic software package).
- the Docker client and Docker server code need to be modified to support the new command options -commontar and -individualtar, and/or, -commonimg and -individualimg.
- the Docker client passes the option parameters to the Docker server.
- the code can parse the new options, decompress the public software packages and feature software packages, and selectively copy the content of the public software and feature software to Container read-write layer.
- the version file is loaded into the disk of the main control single board through the version management service, where the version file may include: basic image file, public software package, and feature software package.
- each functional board performs layered creation of containers based on the basic image file, the public software package, and the characteristic software package.
- Step 502 may include the following processing.
- Each function board downloads the basic image file, public software package, and feature software package from the disk of the main control single board.
- the registry deploys an FTP server to manage mirrors.
- Each functional board downloads basic mirror files, public software packages, and characteristic software from the disk of the main control board through the FTP service.
- Packages namely, baseimage.tar, common.tar and boardx.tar, and then run the image through the Docker API.
- the Docker client on each function board loads the basic image file into the local mirror warehouse, obtains the image ID, and sends the public software package and the characteristic software package to the Docker service through two new options added in the Docker client in advance. And send the image ID to the Docker server.
- the Docker server on each functional board parses the public software packages and feature software packages, decompresses them in whole or in part to the read-write layer of the container, and then according to the image ID and the public software packages and feature software packages in the read-write layer Create a container.
- step 502 may include: each The Docker server on the function board uses the postContainersCreate function to parse the -commontar and -individualtar parameters, and uses the daemon.create function to decompress the public and characteristic software packages into the container's read-write layer.
- step 502 may include: The Docker server on each functional board parses the -commonimg and -individualimg parameters through the postContainersCreate function, decompresses the public software package and the feature software package to the temporary directory through the daemon.create function, removes the content of the basic image, removes the metadata file, and Application files are copied to the container's read-write layer.
- the public software package and the characteristic software package are ordinary TAR packages.
- the background production version includes step 1 and step 2.
- step 1 make the basic image file baseimage.tar, make the common software package into a common TAR package common.tar, and make the characteristic software package into a common TAR package boardx.tar.
- step 2 put baseimage.tar, common.tar, boardx.tar and other files in the version into the version file version.set.
- modifying the Docker source code includes steps 1 to 4.
- step 1 obtain the Docker source code from the Docker official website, including three components, docker-engine, containerd, and runc.
- step 2 modify the Docker client code NewCreateCommand function, which defines the docker create command, and add two options -commontar and -individualtar.
- step 3 modify the Docker daemon code, parse the -commontar and -individualtar parameters in the postContainersCreate function, and decompress the common.tar and individual.tar into the container's read-write layer in the daemon.create function.
- step 4 use the cross tool chain of the target environment to compile the Docker source code in the background to obtain Docker and Dockerd.
- the deployment process of the target system includes step 1 to step 6.
- step 1 deploy Docker and Dockerd to the target system.
- step 2 the FTP server is deployed on the main control board.
- step 3 load version.set to the disk of the main control board, and parse out baseimage.tar, common.tar, and boardx.tar through the version management service.
- each function board downloads baseimage.tar, common.tar, boardx.tar from the main control board through the FTP service.
- step 5 load baseimage.tar into the local mirror warehouse using the docker load command or REST API on each function board.
- the command line is as follows: Docker load-i baseimage.tar.
- step 6 create a container based on the image ID obtained in step 5. Docker run-it baseimageID-commontar common.tar-individualtar boardx.tar.
- the public software package and the characteristic software package are Docker image packages.
- the background production version includes step 1 and step 2.
- step 1 make the base image file baseimage.tar, use the public software package to make the common image file common.tar, and use the feature software package to make each feature image file boardx.tar.
- step 2 put baseimage.tar, common.tar, boardx.tar and other files in the version into the version file version.set.
- modifying the Docker source code includes steps 1 to 4.
- step 1 obtain the Docker source code from the Docker official website, including three components, docker-engine, containerd, and runc.
- step 2 modify the Docker client code NewCreateCommand function, which defines the docker create command, and add two options -commonimg and -individualimg.
- step 3 modify the Docker daemon code, parse the -commonimg and -individualimg parameters in the postContainersCreate function, unzip the common.tar and individual.tar in the daemon.create function to the temporary directory, remove the basic image related content, and remove the metadata files. Copy the application files to the read-write layer of the container.
- step 4 use the cross tool chain of the target environment to compile the Docker source code in the background to obtain Docker and Dockerd.
- the deployment process of the target system includes step 1 to step 6.
- step 1 deploy Docker and Dockerd to the target system.
- step 2 the FTP server is deployed on the main control board.
- step 3 load version.set to the disk of the main control board, and parse out baseimage.tar, common.tar, and boardx.tar through the version management process.
- each function board downloads baseimage.tar, common.tar, boardx.tar from the main control board through the FTP service.
- step 5 load baseimage.tar into the local mirror warehouse using the docker load command or REST API on each function board.
- the command line is as follows: Docker load-i baseimage.tar.
- step 6 create a container based on the image ID obtained in step 5. Docker run-it baseimageID-commonimg common.tar-individualimg boardx.tar.
- the technical solutions implemented in the present disclosure can be used in data products.
- the technical solutions in the embodiments of the present disclosure can be applied to high-end routers and switches.
- the technical solutions of the embodiments of the present disclosure can also be applied.
- FIG. 7 is a schematic diagram of the container layered deployment system according to an embodiment of the present disclosure, which may include a download module 70 and a container creation module 72 .
- the download module 70 is used for downloading version files from the disk of the main control single board, where the version files may include: basic image files, public software packages, and feature software packages.
- a basic image baseimage.tar that is, the above-mentioned basic image file
- the basic image has only the root file system; make the common software of each board into a common TAR package or a Docker image package common.tar (that is, The above-mentioned public software package), the software specific to each board is made into a common TAR package or a Docker image package boardx.tar (ie, the above-mentioned characteristic software package).
- the Docker client and Docker server code need to be modified to support the new command options -commontar and -individualtar, and/or, -commonimg and -individualimg.
- the Docker client passes the option parameters to the Docker server.
- the code can parse the new options, decompress the public software packages and feature software packages, and selectively copy the content of the public software and feature software to Container read-write layer.
- the version file is loaded into the disk of the main control single board through the version management service module, where the version file may include: a basic image file, a public software package, and a feature software package.
- the download module 70 may be used to download the basic image file, the public software package, and the characteristic software package from the disk of the main control single board.
- the download module 70 can download the basic image file, the public software package, and the characteristic software package from the disk of the main control single board through the FTP service, and send it to the corresponding function single board.
- the container creation module 72 is used for layered creation of containers based on basic image files, public software packages, and characteristic software packages.
- the container creation module 72 may include a Docker client and a Docker server.
- the Docker client is used to load the basic image file into the local mirror warehouse, obtain the image ID, and send the public software package and the feature software package to the Docker server through the two new options added in the Docker client in advance, and The image ID is also sent to the Docker server.
- the Docker server is used to parse public software packages and characteristic software packages and decompress them in whole or in part into the read-write layer of the container, and create containers based on the image ID and public software packages and characteristic software packages in the read-write layer.
- the Docker server can be used to parse the -commontar and -individualtar parameters through the postContainersCreate function, and decompress the public software packages and characteristic software packages into the read-write layer of the container through the daemon.create function.
- the Docker client loads the basic image file into the local mirror warehouse, obtains the image ID, and sends the public software package and the characteristic software package to the Docker server through two new options added to the Docker client in advance.
- the image ID is also sent to the Docker server; the Docker server parses public software packages and characteristic software packages and decompresses them in whole or in part to the container's read-write layer, and according to the image ID and public software in the read-write layer Packages and feature packages create containers.
- the public software package and the characteristic software package may be ordinary TAR packages, and the two newly added options in the Docker client include: options -commontar and -individualtar in the NewCreateCommand function.
- each functional single board 74 is used for: the Docker server on it parses the -commontar and -individualtar parameters through the postContainersCreate function, and decompresses the public software packages and characteristic software packages to the read-write layer of the container through the daemon.create function in.
- the public software package and the feature software package can be Docker mirrored packages, and the two new options added to the Docker client include: options -commonimg and -individualimg in the NewCreateCommand function.
- each functional single board 74 is used for: the Docker server on it parses the -commonimg and -individualimg parameters through the postContainersCreate function, and decompresses the public software packages and characteristic software packages to the temporary directory through the daemon.create function, removing the basics Mirror related content, remove metadata files, and copy application files to the read-write layer of the container.
- a computer-readable storage medium on which a computer program is stored.
- the processor implements the container layered deployment method according to the embodiments of the present disclosure .
- modules or steps of the present disclosure can be implemented by a general computing device, and they can be concentrated on a single computing device or distributed in a network composed of multiple computing devices.
- they can be implemented with program codes executable by a computing device, so that they can be stored in a storage device for execution by the computing device, and in some cases, can be executed in a different order than here.
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
Description
Claims (13)
- 一种容器分层部署方法,包括:各功能单板从主控单板的磁盘中下载版本文件,其中,所述版本文件包括:基础镜像文件、公共软件包以及特性软件包;以及各功能单板基于所述基础镜像文件、所述公共软件包以及所述特性软件包进行容器的分层创建。
- 如权利要求1所述的方法,其中,各功能单板基于所述基础镜像文件、所述公共软件包以及所述特性软件包进行容器的分层创建的步骤包括:各功能单板上的Docker客户端将所述基础镜像文件加载到本地镜像仓库中,获取镜像ID,并通过预先在Docker客户端新增的两个选项,将所述公共软件包和所述特性软件包发送到Docker服务端,并将镜像ID也发送到Docker服务端;以及各功能单板上的Docker服务端解析所述公共软件包和所述特性软件包并将其全部或者部分解压缩到容器的读写层中,并根据所述镜像ID和所述读写层中的所述公共软件包和所述特性软件包创建容器。
- 如权利要求1所述的方法,其中,各功能单板从所述主控单板的磁盘中下载所述基础镜像文件、所述公共软件包以及所述特性软件包的步骤包括:各功能单板通过FTP服务从所述主控单板的磁盘中下载所述基础镜像文件、所述公共软件包以及所述特性软件包。
- 如权利要求2所述的方法,其中,所述公共软件包和所述特性软件包为普通TAR包;在所述Docker客户端新增的两个选项包括:NewCreateCommand函数中的选项-commontar和-individualtar。
- 如权利要求4所述的方法,其中,各功能单板上的所述Docker服务端解析所述公共软件包和所述特性软件包并将其全部或者部分解压缩到所述容器的读写层中的步骤包括:各功能单板上的所述Docker服务端通过postContainersCreate函数解析-commontar和-individualtar参数,并通过daemon.create函数把所述公共软件包和所述特性软件包解压到所述容器的读写层中。
- 如权利要求2所述的方法,其中,所述公共软件包和所述特性软件包为Docker镜像包;在所述Docker客户端新增的两个选项包括:NewCreateCommand函数中的选项-commonimg和-individualimg。
- 如权利要求6所述的方法,其中,各功能单板上的所述Docker服务端解析所述公共软件包和所述特性软件包并将其全部或者部分解压缩到所述容器的读写层中的步骤包括:各功能单板上的所述Docker服务端通过postContainersCreate函数解析-commonimg和-individualimg参数,并通过daemon.create函数把所述公共软件包和所述特性软件包解压到临时目录,剔除基础镜像相关内容,剔除元数据文件,把应用文件复制到容器的读写层中。
- 一种容器分层部署系统,设置于各功能单板,所述系统包括:下载模块,用于从主控单板的磁盘中下载版本文件,其中,所述版本文件包括:基础镜像文件、公共软件包、以及特性软件包;以及容器创建模块,用于基于所述基础镜像文件、所述公共软件包以及所述特性软件包进行容器的分层创建。
- 如权利要求8所述的系统,其中,所述容器创建模块包括:Docker客户端,用于将所述基础镜像文件加载到本地镜像仓库中,获取镜像ID,并通过预先在所述Docker客户端新增的两个选项,将所述公共软件包和所述特性软件包发送到Docker服务端,并将镜像ID也发送到所述Docker服务端;以及所述Docker服务端,用于解析所述公共软件包和所述特性软件包并将其全部或者部分解压缩到所述容器的读写层中,并根据所述镜像ID和所述读写层中的所述公共软件包和所述特性软件包创建所述容器。
- 如权利要求8所述的系统,其中,所述下载模块用于:通过FTP服务从所述主控单板的磁盘中下载所述基础镜像文件、所述公共软件包以及所述特性软件包,并发送给相应的功能单板。
- 如权利要求9所述的系统,其中,所述公共软件包和所述特性软件包为普通TAR包;在所述Docker客户端新增的两个选项包括:NewCreateCommand函数中的选项-commontar和-individualtar;所述Docker服务端用于:通过postContainersCreate函数解析-commontar和-individualtar参数,通过daemon.create函数把所述公共软件包和所述特性软件包解压到所述容器的读写层中。
- 如权利要求9所述的系统,其中,所述公共软件包和所述特性软件包为Docker镜像包;在所述Docker客户端新增的两个选项包括:NewCreateCommand函数中的选项-commonimg和-individualimg;所述Docker服务端用于:通过postContainersCreate函数解析-commonimg和-individualimg参数,通过daemon.create函数把所述公共软件包和所述特性软件包解压到临时目录,剔除基础镜像相关内容,剔除元 数据文件,把应用文件复制到容器的读写层中。
- 一种计算机可读存储介质,其上存储有计算机程序,所述计算机程序被处理器运行时,所述处理器实现根据权利要求1至7中任一项所述的容器分层部署方法。
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201910670480.5 | 2019-07-24 | ||
CN201910670480.5A CN112306621A (zh) | 2019-07-24 | 2019-07-24 | 容器分层部署方法及系统 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2021013248A1 true WO2021013248A1 (zh) | 2021-01-28 |
Family
ID=74193331
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2020/104491 WO2021013248A1 (zh) | 2019-07-24 | 2020-07-24 | 容器分层部署方法及系统 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN112306621A (zh) |
WO (1) | WO2021013248A1 (zh) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN113032736A (zh) * | 2021-03-05 | 2021-06-25 | 海能达通信股份有限公司 | Docker分层镜像的加解密方法及相关装置 |
Families Citing this family (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN113342359B (zh) * | 2021-05-13 | 2023-03-24 | 烽火通信科技股份有限公司 | 容器镜像文件智能生成方法、装置、设备及存储介质 |
CN113296766B (zh) * | 2021-05-31 | 2022-10-11 | 中电福富信息科技有限公司 | 基于Seldon的AI模型发布方法及系统 |
CN114327754B (zh) * | 2021-12-15 | 2022-10-04 | 中电信数智科技有限公司 | 一种基于容器分层技术的镜像导出与组装方法 |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN107644374A (zh) * | 2017-10-19 | 2018-01-30 | 方欣科技有限公司 | 一种基于Docker云计算技术涉税文书系统构建平台 |
CN107729020A (zh) * | 2017-10-11 | 2018-02-23 | 北京航空航天大学 | 一种实现大规模容器快速部署的方法 |
CN109062655A (zh) * | 2018-06-05 | 2018-12-21 | 腾讯科技(深圳)有限公司 | 一种容器化云平台及服务器 |
CN109190386A (zh) * | 2018-04-04 | 2019-01-11 | 中国电子科技网络信息安全有限公司 | 基于Device Mapper的容器镜像分层加密存储方法 |
-
2019
- 2019-07-24 CN CN201910670480.5A patent/CN112306621A/zh active Pending
-
2020
- 2020-07-24 WO PCT/CN2020/104491 patent/WO2021013248A1/zh active Application Filing
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN107729020A (zh) * | 2017-10-11 | 2018-02-23 | 北京航空航天大学 | 一种实现大规模容器快速部署的方法 |
CN107644374A (zh) * | 2017-10-19 | 2018-01-30 | 方欣科技有限公司 | 一种基于Docker云计算技术涉税文书系统构建平台 |
CN109190386A (zh) * | 2018-04-04 | 2019-01-11 | 中国电子科技网络信息安全有限公司 | 基于Device Mapper的容器镜像分层加密存储方法 |
CN109062655A (zh) * | 2018-06-05 | 2018-12-21 | 腾讯科技(深圳)有限公司 | 一种容器化云平台及服务器 |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN113032736A (zh) * | 2021-03-05 | 2021-06-25 | 海能达通信股份有限公司 | Docker分层镜像的加解密方法及相关装置 |
Also Published As
Publication number | Publication date |
---|---|
CN112306621A (zh) | 2021-02-02 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2021013248A1 (zh) | 容器分层部署方法及系统 | |
US10853047B2 (en) | Method for virtualizing software applications | |
US10802835B2 (en) | Rule-based data protection | |
US10908999B2 (en) | Network block device based continuous replication for Kubernetes container management systems | |
Ma et al. | Efficient live migration of edge services leveraging container layered storage | |
US9933956B2 (en) | Systems and methods for implementing stretch clusters in a virtualization environment | |
JP5065295B2 (ja) | 異なる仮想マシン・イメージ間でファイルを共有するための方法、システム、およびコンピュータ読み取り可能媒体 | |
US20200034167A1 (en) | Automatic application migration across virtualization environments | |
WO2021129733A1 (zh) | 云操作系统的管理方法、装置、服务器、管理系统及介质 | |
US8606886B2 (en) | System for conversion between physical machines, virtual machines and machine images | |
RU2495481C2 (ru) | Размещение программного обеспечения в больших сетевых системах | |
US10574524B2 (en) | Increasing reusability of and reducing storage resources required for virtual machine images | |
US9805041B2 (en) | Policy based layered filesystem management | |
US8495352B2 (en) | System and method for instantiation of distributed applications from disk snapshots | |
US20080163171A1 (en) | Virtual resource templates | |
US20120144391A1 (en) | Provisioning a virtual machine | |
US20110061046A1 (en) | Installing Software Applications in a Layered Virtual Workspace | |
US20110040812A1 (en) | Layered Virtual File System | |
Zhang et al. | 4VP: A novel meta OS approach for streaming programs in ubiquitous computing | |
KR20060051932A (ko) | 소프트웨어를 실행 동안 업데이트하는 시스템, 방법 및컴퓨터-판독가능 매체 | |
CN102693230B (zh) | 用于存储区域网络的文件系统 | |
US8893272B2 (en) | Method and device for recombining runtime instruction | |
US11934886B2 (en) | Intra-footprint computing cluster bring-up | |
US20220206902A1 (en) | Application template for application consistent backup and restore of database applications in kubernetes | |
WO2011022388A1 (en) | Layered virtual file system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 20844726 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 20844726 Country of ref document: EP Kind code of ref document: A1 |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 20844726 Country of ref document: EP Kind code of ref document: A1 |
|
32PN | Ep: public notification in the ep bulletin as address of the adressee cannot be established |
Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 210922) |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 20844726 Country of ref document: EP Kind code of ref document: A1 |