CN112631739A - Container control method and device, medium and computer equipment - Google Patents
Container control method and device, medium and computer equipment Download PDFInfo
- Publication number
- CN112631739A CN112631739A CN202110253853.6A CN202110253853A CN112631739A CN 112631739 A CN112631739 A CN 112631739A CN 202110253853 A CN202110253853 A CN 202110253853A CN 112631739 A CN112631739 A CN 112631739A
- Authority
- CN
- China
- Prior art keywords
- container
- user
- user directory
- instruction
- directory
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
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
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/17—Details of further file system functions
- G06F16/172—Caching, prefetching or hoarding of files
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/17—Details of further file system functions
- G06F16/174—Redundancy elimination performed by the file system
- G06F16/1744—Redundancy elimination performed by the file system using compression, e.g. sparse files
-
- 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/45575—Starting, stopping, suspending or resuming virtual machine instances
-
- 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/45595—Network integration; Enabling network access in virtual machine instances
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The embodiment of the application provides a container control method and device, a medium and computer equipment, wherein the container control method comprises the following steps: in response to an instruction to stop running a container, storing a user directory corresponding to a user running the container to a storage space outside the container; and stopping the operation of the container after the user catalog is stored. The technical scheme in the embodiment of the application is favorable for improving the operation efficiency of the container.
Description
Technical Field
The embodiment of the application relates to the field of computers, in particular to a container control method and device, a medium and computer equipment.
Background
Container technology is a technology that achieves lightweight resource isolation. The container technology based on the distributed architecture can be used for managing containerized applications on a plurality of hosts in a cloud platform, performing container cluster management and providing container services for users. This technology may also be referred to as a distributed architecture based on container technology.
In such a scenario that the container service is provided for different users by the distributed architecture based on the container technology, the efficiency of the users using the container service needs to be improved.
Disclosure of Invention
In view of this, an embodiment of the present application provides a container control method based on a distributed architecture, including:
in response to an instruction to stop running a container, storing a user directory corresponding to a user running the container to a storage space outside the container;
and stopping the operation of the container after the user catalog is stored.
Optionally, the user directory corresponding to the user operating the container includes: a public user directory and a private user directory; wherein the common user directory corresponds to a plurality of users; the private user directory corresponds to one user.
Optionally, the storing the user directory corresponding to the user operating the container into a storage space outside the container includes: and storing the public user directory to a public storage space shared by a plurality of users, and storing the private user directory to a private storage space of a corresponding user.
Optionally, the storage manner of storing the user directory corresponding to the user operating the container to the storage space outside the container is compressed storage.
Optionally, the storage space outside the container includes a space of a cloud; the storing, in response to the instruction to stop running the container, a user directory corresponding to a user running the container to a storage space outside the container includes: triggering a first blocking type event through the instruction of stopping the running of the container, and triggering a storage script by the first blocking type event so as to compress and store the user directory, wherein the storage script is stored in a storage space outside the container.
Optionally, the storage space outside the container includes a storage space of a cloud.
Optionally, all or part of the user directory is stored in a storage manner of incremental storage.
Optionally, the storing all or part of the user directory in the storage manner of incremental storage includes:
determining a difference directory with content change in the user directory after the container is operated;
determining a file to be saved in the difference directory;
and compressing and saving the file to be saved.
Optionally, the container control method further includes:
in response to an instruction to start a container, determining the user directory corresponding to a user who issued the instruction to start the container from a storage space outside the container;
loading the user directory into the container;
and running the container after the user directory is completely loaded.
Optionally, the storage space outside the container includes a space of a cloud;
the storing, in response to the instruction to stop running the container, a user directory corresponding to a user running the container to a storage space outside the container includes: triggering a first blocking type event through the instruction of the container stopping operation, and triggering a storage script through the first blocking type event so as to compress and store the user directory, wherein the storage script is stored in the cloud end;
the determining, in response to the instruction to start the container, the user directory corresponding to the user who issued the instruction to start the container from the storage space outside the container comprises: triggering a second blocking type event through an instruction of starting a container, and triggering a recovery script through the second blocking type event so as to recover the user directory stored in the cloud to the container, wherein the recovery script is stored in the cloud.
Optionally, the storing the user directory corresponding to the user operating the container into a storage space outside the container includes:
determining a difference directory with content change in the user directory after the container is operated;
determining a file to be saved in the difference directory;
compressing and saving the file to be saved;
the loading the user catalog into the container comprises:
restoring the user directory to the container;
and restoring the compressed and saved file to the corresponding user directory.
An embodiment of the present application further provides a container control method based on a distributed architecture, including:
in response to an instruction to start a container, determining a user directory corresponding to a user who issued the instruction to start the container from a storage space outside the container;
loading the user directory into the container;
and running the container after the user directory is completely loaded.
Optionally, the user directory includes a public user directory and a private user directory; wherein the common user directory corresponds to a plurality of users; the private user directory corresponds to one user.
Optionally, the loading the user directory into the container includes:
loading the public user directory from a public storage space to the container, the public storage space being unencrypted;
and loading the public user directory from a private storage space to the container, wherein the private storage space corresponds to the user and is an encrypted storage space.
Optionally, the storage space outside the container includes a space in a cloud.
Optionally, in response to an instruction to start a container, determining, from a storage space outside the container, a user directory corresponding to a user who issued the instruction to start the container includes: triggering a second blocking type event through an instruction of starting a container, triggering a recovery script by the second blocking type event so as to recover the user directory stored in the storage space outside the container to the container, wherein the recovery script is stored in the storage space outside the container.
Optionally, all or part of the user directory is stored in an incremental storage manner; the determining, in response to the instruction to start the container, the user directory corresponding to the user who issued the instruction to start the container from the storage space outside the container comprises: determining a difference file stored in the incremental saving mode and a base user directory corresponding to the difference file, wherein the base user directory is a part of the user directory which is used as a base of the incremental saving;
the loading the user catalog into the container comprises:
restoring the base user directory to the container;
and recovering the difference file to the corresponding basic user directory.
Optionally, the container control method further includes running the container if a user directory corresponding to the user who sends the instruction to start the container is not stored in the storage space outside the container.
An embodiment of the present application further provides a container control device based on a distributed architecture, including:
a stop instruction response unit adapted to store a user directory corresponding to a user who operates the container to a storage space outside the container in response to an instruction to stop operating the container;
and the operation stopping unit is suitable for stopping the operation of the container after the user catalog is stored.
Optionally, the user directory corresponding to the user operating the container includes: a public user directory and a private user directory; wherein the common user directory corresponds to a plurality of users; the private user directory corresponds to one user.
Optionally, the stop instruction response unit is adapted to store the public user directory in a public storage space shared by multiple users, and store the private user directory in a private storage space of a corresponding user.
Optionally, the stop instruction response unit is adapted to store, in a compressed storage manner, a user directory corresponding to a user operating the container in a storage space outside the container.
Alternatively to this, the first and second parts may,
the stop instruction response unit is suitable for triggering a first blocking type event through the instruction of the stop operation container, and triggering a storage script by the first blocking type event so as to compress and store the user directory, wherein the storage script is stored in a storage space outside the container.
Optionally, the storage space outside the container includes a space of a cloud;
optionally, the stop instruction response unit is adapted to store all or part of the user directory in a storage manner of incremental saving.
Optionally, the stop instruction response unit includes:
the difference catalog unit is suitable for determining the difference catalog with content change in the user catalog after the container runs;
the file to be saved determining unit is suitable for determining a file to be saved in the difference directory;
and the file compression unit is suitable for compressing and storing the file to be stored.
Optionally, the container control device further includes:
a start instruction response unit adapted to determine, in response to an instruction to start a container, the user directory corresponding to a user who issued the instruction to start the container from a storage space outside the container;
a loading unit adapted to load the user directory into the container;
and the operation unit is suitable for waiting for indicating that the user directory is completely loaded and operating the container.
Optionally, the storage space outside the container includes a space of a cloud;
the stop instruction response unit is suitable for triggering a first blocking type event through an instruction of the stop operation container, and storing a storage script triggered by the first blocking type event to compress and store the user directory, wherein the storage script is stored in the cloud end;
the starting instruction response unit is suitable for triggering a second blocking type event through an instruction of a starting container, and triggering a recovery script through the second blocking type event so as to recover the user directory stored in the cloud end to the container.
Optionally, the stop instruction response unit includes:
the difference catalogue unit is suitable for determining a difference catalogue of which the content is changed in the user catalogue after the container is operated;
a file to be saved determining unit which determines a file to be saved in the difference directory;
the file compression unit is used for compressing and storing the file to be stored;
the start instruction response unit includes:
a catalog retrieval unit adapted to retrieve the user catalog to the container;
and the file recovery unit is suitable for recovering the compressed and saved files to the corresponding user directory.
An embodiment of the present application further provides a container control device based on a distributed architecture, including:
a start instruction response unit adapted to determine, in response to an instruction to start a container, the user directory corresponding to a user who issued the instruction to start the container from a storage space outside the container;
a loading unit adapted to load the user directory into the container;
and the operation unit is suitable for waiting for indicating that the user directory is completely loaded and operating the container.
Optionally, the user directory includes a public user directory and a private user directory; wherein the common user directory corresponds to a plurality of users; the private user directory corresponds to one user.
Optionally, the loading unit is adapted to load the public user directory from a public storage space to the container, where the public storage space is not encrypted; and loading the public user directory from a private storage space to the container, wherein the private storage space corresponds to the user and is an encrypted storage space.
Optionally, the storage space outside the container includes a space in a cloud.
Optionally, the start instruction response unit is adapted to trigger a second blocking type event through an instruction to start a container, and trigger a recovery script by the second blocking type event, so as to recover the user directory stored in the storage space outside the container to the container.
Optionally, all or part of the user directory is stored in an incremental storage manner;
the starting instruction response unit is suitable for determining a difference file stored in the incremental saving mode and a basic user directory corresponding to the difference file, wherein the basic user directory is a part of the user directory which is used as a basis for the incremental saving;
the loading unit includes:
a base user directory recovery unit adapted to recover the base user directory to the container;
and the difference file recovery unit is suitable for recovering the difference file to the corresponding basic user directory.
Optionally, the container control device further comprises:
and the storage judging unit is suitable for operating the container when the user directory corresponding to the user sending the instruction for starting the container is not stored in the storage space outside the container.
The embodiment of the present application further provides a computer device, which includes a memory and a processor, where the memory stores a computer program that can be executed on the processor, and the processor executes the container control method when executing the computer program.
The embodiment of the application also provides a computer readable storage medium, on which a computer program is stored, and the computer program executes the container control method when running.
According to the technical scheme in the embodiment of the application, in response to an instruction for stopping the operation of the container, storing a user directory corresponding to a user operating the container into a storage space outside the container; and stopping the operation of the container after the user catalog is stored. The storage space from the user catalog corresponding to the user operating the container to the outside of the container is used for storing the environment for operating the container for the user before the container stops operating, so that a data base can be provided for the environment creation when the user restarts the container, and the efficiency of the container during starting can be further improved.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
FIG. 1 is a flow chart of a container control method in an embodiment of the present application;
FIG. 2 is a flowchart of a method for incrementally saving all or a portion of a user directory in an embodiment of the present application;
FIG. 3 is a flow chart of another method of controlling a container in an embodiment of the present application;
FIG. 4 is a flow chart of another method of controlling a container in an embodiment of the present application;
FIG. 5 is a flow chart of another method of controlling a container in an embodiment of the present application;
FIG. 6 is a flow chart of another method of controlling a container in an embodiment of the present application;
FIG. 7 is a schematic structural diagram of a container control device according to an embodiment of the present application;
FIG. 8 is a block diagram of a stall command response unit according to an embodiment of the present application;
FIG. 9 is a schematic structural view of another container control device according to an embodiment of the present application;
fig. 10 is a schematic structural diagram of another container control device in the embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
As described in the background, container technology is a technology that enables lightweight resource isolation. A distributed architecture based on container technology can provide container services to different users. The inventor researches and discovers that in a distributed architecture, when a user uses a container in a cluster, an environment supporting the use of the container needs to be installed. These environments are purged when the vessel is shut down. When the user uses the container service again, the corresponding environment needs to be reinstalled. As such, the efficiency of container servicing is yet to be improved.
With reference to fig. 1, an embodiment of the present invention provides a container control method based on a distributed architecture, which may include the following steps:
step S11, responding to the instruction of stopping the container operation, and storing a user directory corresponding to the user operating the container to the cloud end;
and step S12, after the user directory is stored, stopping the operation of the container.
In a specific implementation, the instruction to stop operating the container may be issued by a user currently operating the container, or may also be issued by the cloud platform according to a requirement of platform operation or container allocation.
In particular implementations, the platform of the distributed architecture may be diverse, and may be, for example, a Kubernets-Docker cluster. Alternatively, other types of container clusters are possible, and are not limited herein. The instructions to stop running the container may be different in different platforms. Taking the kubernets-Docker cluster as an example, the instruction to notify the running container may be a termination (Terminate) request sent by the user.
In the embodiment of the invention, the user directory corresponding to the user operating the container is stored in the cloud, so that the environment of the user operating the container can be saved for the user, and a data basis is provided for the environment creation when the user starts the container again.
In specific implementation, when the cloud platform manages the container cluster, containers can be allocated to users according to resource conditions of the platform, the same user can operate different containers each time, and the same container can be operated by different users in a time-sharing manner. And the data of the user can not be stored in the container every time the operation of the container is stopped, so that the safety of the data of the user is improved. By storing the user directory corresponding to the user operating the container to the cloud end, the user directory can be loaded from the cloud end when the same user starts the container service again, the operating environment of the container does not need to be reinstalled, the container starting speed can be increased, and the container service efficiency can be further improved.
In particular implementations, the user directory corresponding to the user running the container may include an environment that supports the user running the container. In particular, the user directories may include a public user directory and a private user directory. Wherein the common user directory corresponds to a plurality of users; the private user directory corresponds to one user.
Further, the common user directory may store data supporting the use of the container by multiple users, such as tools provided by the platform, event scripts (which may include, for example, storage scripts and/or recovery scripts in the present application), and/or user data managed by the platform. The stored content in the private user directory may include private data of the user, such as software installed by the user and/or data private to the user.
In particular implementations, storage space other than containers, corresponding to storage within containers, does not represent more of a limitation. And the other storage space except the container can be a cloud storage space. The cloud may be from the perspective of a user of the container, and storage space outside of devices used by non-users may be referred to as the cloud. The storage space other than the container may be, in terms of hardware, a storage space physically electrically connected to the container or communicatively connected through a communication network.
In a specific implementation, as described above, the user directory corresponding to the user operating the container includes: a public user directory and a private user directory. Further, storing a user directory corresponding to a user running the container to a storage space outside the container may include: and storing the public user directory to a public storage space shared by a plurality of users, and storing the private user directory to a private storage space of a corresponding user.
Further, a public user directory may be stored to a public cloud and a private user directory may be stored to a private cloud. By storing the private user directory to the private cloud, the security of private user directory storage can be improved. In a particular implementation, the user directory, the public user directory, and the private user directory each include files that are subordinate to the directories.
In particular implementations, the user directory may be stored using blocking type instructions. The blocking type instructions may be different in different platform environments. For example, in a Kubernets-Docker cluster, this may be done by a container initiated callback event (preStop). Specifically, the content triggered by the event may be a storage space for storing the user directory outside the container, for example, a cloud-side mounted disk. Further, the event may be set to be triggered by an instruction to stop running the container, for example, the container start callback event may be set to be triggered by the aforementioned Terminate request, and the container may be blocked from being closed until the storage user directory finishes closing the container.
In particular implementations, the manner in which the user directory is stored may be compressed storage. And the occupation of space resources can be reduced by a compression storage mode.
In a specific implementation, the storage space outside the container may be a mount disk on which the container is mounted, and the mount disk may be a mount disk on the cloud, which may be referred to as a cloud mount disk. A first blocking event may be triggered by an instruction to stop running a container, and a script triggered by the blocking event, that is, a storage script, is stored in the cloud mount disk, and the user directory is compressed and stored by the script.
It is to be understood that, in the present application, the first and second are not limitations on the blocking type event, but merely to distinguish the application scenario of the blocking type event. The blocking type event triggered by the instruction to stop the operation of the container is the first blocking type event, and the blocking type event triggered by the instruction to start the container is the second blocking type event hereinafter. A choke-type event triggered by an instruction to shut down a container is used to choke the shut down of the container, and a choke-type event triggered by an instruction to start a container may be used to choke the start of the container.
The first blocking type event triggered by the instruction to stop the running container may be various, and may be an event that can implement the closing of the blocking container and can trigger the running of the stored script, and may be a blocking type event triggered by the instruction to stop the running container.
Continuing with the kubernets-Docker cluster example, a preStop event may be triggered at a Terminate request sent by a user, causing the container to wait until the preStop event is complete. The preStop event triggered shell script (storage script) may be stored in a read-only mount disk of the container. Before the container operation is finished, the shell script can compress and store the user directory. And after the user directory storage is finished, stopping the operation of the container. The storage script triggered by the preStop event can be consistent with the content in the directory/axer/. system/preStop, and specifically can be an instruction for compressing the user directory. Taking the path of the user directory as/bin/etc/opt/usr/lib/lib 64/sbin as an example, the instruction may be tar-zcvf/home/work/. test/test.
It should be understood that the above path of the user directory, the target path of the stored user directory, and the like are only examples, and are not limiting to the specific implementation means of the platform and the storage in the present application. The blocking type instructions may be different under different platforms. The directory in which the execution content of the blocking type event is located may be different. In addition, the storage path of the user directory may be various.
As previously described, in implementations, the user directories may include a public user directory and a private user directory. When the user directories are stored in a compressed manner, the public user directories may be compressed and stored in the public storage space, and the private user directories may be stored in the private storage space of the corresponding user.
In particular implementations, all or a portion of the user directory may be stored in an incremental save manner to storage space outside of the container. The basis of the incremental saving may be a user directory when the user starts the container, which may be used as a part of the user directory corresponding to the end of the current operation, and may be referred to as a basic user directory as the basis of the incremental saving. The user directory obtained by the user in the embodiment of the present application and stored when the same user stops the container operation last time may be the user directory when the user starts the container this time, or the user directory established before the container is started may be the user directory when the user operates the container.
In one embodiment of the invention, the private user directory may be saved incrementally. Specifically, it may be determined that the difference file generated by the user in the process of starting the container at this time is compared with the difference file generated by the base user directory, and only the difference file is saved. Furthermore, it may be determined that the user has modified directories, and further determine the differential file list in the modified directories, that is, the list of files that have changed after the container is run, and store the files in the differential file list.
In particular implementations, the incremental save may be a compressed save. Accordingly, the saving of the directory with the modification may be a compressed saving. The public user directory that has been saved before this incremental saving may be stored in a public cloud, and the private user directory may be stored in a private cloud. The difference file saved in the increment mode can be stored in the same or different private cloud as the private user directory.
By means of incremental storage, the data amount required to be stored when the container stops running each time can be reduced, and resource occupancy rate is reduced.
Referring to fig. 2 in combination, in an embodiment of the present invention, incrementally saving all or part of the user directory may include the following steps:
step S21, determining a difference directory with content change in the user directory after the container is operated;
step S22, determining the files to be saved in the difference directory;
and step S23, compressing and saving the file to be saved.
The difference directory in which the content changes in the user directory may be a difference directory that changes compared with the stored base user directory. The file to be saved may be referred to as a difference file. In a specific implementation, the directory modified by the user, that is, the difference directory, may be further determined, and the directory that needs to be saved therein is determined. Thus, the occupation of the storage resource can be further reduced.
In an embodiment of the present invention, a compressed and saved script (a storage script) may be stored in a public cloud, and a private user directory when a container is started is stored in a private cloud, where the private user directory includes an original file under the directory. The difference file generated in the container operation process of the user, that is, the file to be saved determined after the judgment of the difference directory, may be stored in the aforementioned private cloud or another private cloud.
In a specific implementation, in a scenario where the user directory has been stored when the user last runs the container, the corresponding user directory may be incrementally stored based on the stored basic user directory.
In particular implementations, the particular implementation of the incremental save may be different. Continuing with the example of the platform being a kubernets-Docker cluster, the incremental store may be triggered by a container-initiated callback event. Specifically, the PreStop script may be called through a PreStop callback function before the container is terminated, and incremental storage may be implemented through a p-reStop script. Further, the modified content needing to be stored in the private user directory can be determined through the preStop script, and the difference judging instruction is circularly used for the directory with the modified content needing to be stored, so that a difference file list is obtained. For example, the user directory structure during the start-up is named sourcePaths, and the directory that needs to be saved during the current operation is named basePath, and then the specific implementation form of the difference determination instruction in this scenario may be: "rsync-dry-run-a-out-format ="% n "< basePath > < sourcePath > | grep-v"/$ ". After the difference file list is determined, a tar tool can be adopted for packing and compressing the difference file list and storing the difference file list into the private cloud to obtain a difference file compression package.
The container control method in the embodiment of the present invention may be used in a stage of stopping operation of the container, and may save an environment for operating the container for a user operating the container before stopping operation of the container, and provide a data base for creating an operating environment when the user restarts the container.
The embodiment of the present invention further provides another container control method, which may be used in a container starting stage, and with reference to fig. 3, specifically, the method may include the following steps:
step S31, responding to the container starting instruction, determining a user directory corresponding to the user who sends the container starting instruction from the storage space outside the container;
step S32, loading the user directory into the container;
and step S33, waiting for the indication that the user directory is loaded, and operating the container.
In the embodiment of the invention, the user directory is loaded to the container in response to the instruction for starting the container, and the container is operated after the user directory is completely loaded, so that the user can continuously operate the container based on the past environment configuration of the container, repeated operation is avoided, and the use efficiency of the container is improved.
In an embodiment of the present invention, the container control method for the phase of starting the container may be used in combination with the container control method for the phase of stopping the operation of the container. The principles, concepts and specific embodiments related to the container control method described above may be referenced to one another. Therefore, the content already described in the container control method for the container start-up stage is not repeated here.
The container control method for the container shutdown phase may also be combined with other user directory methods that may provide a user corresponding to the user who issued the instruction to start the container, which is not limited herein.
In particular implementations, the instructions to launch a container may be varied, and the particular instructions may be different in different platforms. For example, in an application scenario of a Kubernets-Docker cluster, the instruction to Start a container may be the user sending a Start request.
In specific implementation, a second blocking type event may be triggered by an instruction to start a container, and a recovery script that returns a user directory to the container is triggered by the second blocking type event, where the recovery script may determine whether there is content to be recovered, and if so, perform recovery, otherwise, run the container.
For example, in the application scenario of the kubernets-Docker cluster, the restoration of the user directory may be performed by the second blocking type event, postStart event, it supports, so that the container is run after the restoration is finished. Specifically, the script of the postStart event may first determine whether a user directory corresponding to the start container exists, and if so, restore the user directory to the container. The script of postStart event may be referred to as a recovery script in this application. Further, the script of postStart event may be stored in the public cloud.
In particular implementation, the blocking type event triggered by the instruction to start the container may be different for different platforms, the blocking type event can block the container start, and the time to trigger the recovery script to run can be used as the blocking type triggered by the instruction to start the container. The blocking event triggered recovery script may also be different.
In implementations, the user directory may be compressed, and the compressed user directory may be decompressed to a container.
In a specific implementation, referring to fig. 4 in combination, in an embodiment of the present invention, a container control method may include the steps of:
step S41, responding to the instruction of starting the container, determining the difference file stored in the incremental saving mode;
step S42, restoring a basic user directory to the container, wherein the basic user directory is the basis for incremental storage when the container is operated last time by a user;
step S43, restoring the difference file to the corresponding basic user directory to obtain the user directory corresponding to the last time when the container operation is finished;
and step S44, waiting until the user directory is restored, and operating the container.
The difference file corresponds to a user of an instruction for starting the container, and can be stored in the cloud-side hanging disc. In a specific implementation, the process of restoring the difference file to the basic user directory is a process of updating the basic user directory, and after the restoration is completed, a user directory which is consistent with the user directory when the user stops operating the container last time can be obtained.
In particular implementations, the user directory and difference files may be stored in any one or a combination of ways as previously described. The manner of loading the user directory into the container may be restored in a corresponding manner.
For example, in implementations, the difference file may be compressively saved. Accordingly, in an implementation of step S42, the difference file may be decompressed to the corresponding user directory.
In a specific implementation, as previously described, the user directories include a public user directory and a private user directory; wherein the common user directory corresponds to a plurality of users; the private user directory corresponds to one user. Loading the user catalog into the container may include: loading the public user directory from a public storage space to the container, the public storage space being unencrypted; and loading the public user directory to the container from a private storage space, wherein the private storage space has a corresponding relation with the user and is an encrypted storage space, and the privacy is stronger.
As previously described, the container control method for the phase of container start-up may be used in combination with the container control method for the phase of container stop-operation. In particular, both may also belong together to the same vessel control method.
Referring to fig. 5 in combination, in an embodiment of the present invention, a container control method may include the steps of:
step S51, in response to the instruction of stopping the container, storing a user directory corresponding to the user operating the container into a storage space outside the container;
step S52, the operation of the container is stopped after the user directory is stored;
step S53, responding to the container starting instruction, determining the user directory corresponding to the user who sends the container starting instruction from the storage space outside the container;
step S54, loading the user directory into the container;
and step S55, waiting for the indication that the user directory is loaded, and operating the container.
The specific implementation manner and advantageous effects of step S51 and step S52 may be referred to as the specific implementation manner and advantageous effects of step S11 and step S12 shown in fig. 1, and the specific implementation manner and advantageous effects of step S53 to step S55 may be referred to as the specific implementation manner and advantageous effects of step S31 to step S33 shown in fig. 3, which is not described herein again.
Referring to fig. 6 in combination, in an embodiment of the present invention, a container control method may include the steps of:
step S61, waiting for a container start request;
step S62, responding to the device start request, determining whether there is a user directory corresponding to the user initiating the container start request; if the user directory exists, performing step S63, otherwise performing step S64;
step S63, triggering a second blocking type event to restore the user directory to the container;
step S64, operating the container;
step S65, waiting for a request to stop the operation of the container;
step S66, in response to the request to stop the container operation, triggering a first blocking type event to compress the user directory to the mounted disk;
step S67, the operation of the container is stopped after the user directory is stored;
step S68, a request to start a container is awaited.
The container start request may be the aforementioned instruction to start the container, and the container stop request may be an instruction to stop operating the container.
Those of skill in the art will understand that the description herein of "in a particular implementation," "an embodiment," "for example," etc., means that a particular feature, structure, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the present application. Furthermore, the particular features, structures, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, various embodiments or examples and features of different embodiments or examples described in this application can be combined and combined by those skilled in the art without contradiction.
Additionally, any process or method descriptions in flow charts or otherwise described herein in the foregoing embodiments may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps of the process. And the scope of the preferred embodiments of the present application includes other implementations in which functions may be performed out of the order shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved.
In the technical scheme of the embodiment of the application, in response to an instruction for stopping the operation of the container, storing a user directory corresponding to a user operating the container to a cloud; and stopping the operation of the container after the user catalog is stored. Through storing the user directory corresponding to the user who operates the container to the cloud, the environment of the container operated by the user can be saved for the user, a data base is provided for the environment creation when the user starts the container again, and the efficiency of the container can be improved.
In addition, the user directory is loaded to the container in response to the instruction for starting the container, and the container is operated after the user directory is completely loaded, so that the user can continuously operate the container based on the past environment configuration of the user on the container, repeated operation is avoided, and the use efficiency of the container is improved.
An embodiment of the present application further provides a container control device based on a distributed architecture, which, with reference to fig. 7, may specifically include the following units:
a stop instruction response unit 71 adapted to store a user directory corresponding to a user who operates the container to a storage space outside the container in response to an instruction to stop operating the container;
a stop operation unit 72 adapted to wait until the end of storing the user directory, and stop the operation of the container.
In a specific implementation, the user directory corresponding to the user running the container may include: a public user directory and a private user directory; wherein the common user directory corresponds to a plurality of users; the private user directory corresponds to one user.
In a specific implementation, the stop instruction response unit 71 is adapted to store the public user directory in a public storage space shared by a plurality of users, and store the private user directory in a private storage space of a corresponding user.
In a specific implementation, the stop instruction response unit 71 is adapted to store the user directory corresponding to the user operating the container in a compressed storage manner in a storage space outside the container.
In a specific implementation, the storage space outside the container may include a space in a cloud.
In a specific implementation, the stop instruction response unit 71 is adapted to trigger a first blocking type event by the instruction to stop running the container, and trigger a storage script by the first blocking type event to compress and store the user directory, where the storage script is stored in a storage space outside the container.
In a specific implementation, the stop instruction response unit 71 is adapted to store all or part of the user directory in an incremental storage manner.
Referring to fig. 8 in combination, in a specific implementation, the stop instruction response unit may include:
a difference list 81, adapted to determine a difference list with content change in the user list after the container is operated;
a file to be saved determining unit 82 adapted to determine a file to be saved in the difference directory;
and a file compression unit 83 adapted to compress and store the file to be stored.
With combined reference to fig. 7 and 9, in a specific implementation, the container control apparatus may further include:
a start instruction responding unit 91 adapted to determine, in response to an instruction to start a container, the user directory corresponding to a user who issued the instruction to start the container from a storage space outside the container;
a loading unit 92 adapted to load the user directory into the container;
an operation unit 93 adapted to wait for an indication that the user directory is completely loaded to operate the container.
In a specific implementation, the storage space outside the container may include a space in a cloud;
the stop instruction response unit 71 is adapted to trigger a first blocking type event through the instruction of the stop operation container, and store a storage script triggered by the first blocking type event to compress and store the user directory, where the storage script is stored in the cloud;
the start instruction response unit 91 is adapted to trigger a second blocking type event through an instruction of a start container, and trigger a recovery script by the second blocking type event, so as to recover the user directory stored in the cloud to the container.
In a specific implementation, the stop instruction response unit 71 may include:
the difference catalogue unit is suitable for determining a difference catalogue of which the content is changed in the user catalogue after the container is operated;
a file to be saved determining unit which determines a file to be saved in the difference directory;
the file compression unit is used for compressing and storing the file to be stored;
the start instruction response unit 91 may include:
a catalog retrieval unit adapted to retrieve the user catalog to the container;
and the file recovery unit is suitable for recovering the compressed and saved files to the corresponding user directory.
An embodiment of the present application further provides a container control apparatus based on a distributed architecture, and with reference to fig. 10, the apparatus may include the following units:
a start instruction response unit 101 adapted to determine, in response to an instruction to start a container, the user directory corresponding to a user who issued the instruction to start the container from a storage space outside the container;
a loading unit 102 adapted to load the user directory into the container;
the running unit 103 is adapted to wait for indicating that the user directory is completely loaded, and run the container.
The specific implementation manner of each unit may be the same as or similar to that of the corresponding unit in fig. 9, and is not described herein again. It will be appreciated that the apparatus shown in fig. 10 may be used in conjunction with the apparatus shown in fig. 7, or may be used with other apparatus that may provide a corresponding user profile.
In particular implementations, the user directories may include a public user directory and a private user directory; wherein the common user directory corresponds to a plurality of users; the private user directory corresponds to one user.
In a specific implementation, the loading unit 102 is adapted to load the public user directory into the container from a public storage space, where the public storage space is not encrypted; and loading the public user directory from a private storage space to the container, wherein the private storage space corresponds to the user and is an encrypted storage space.
In a specific implementation, the storage space outside the container may include a space in a cloud.
In a specific implementation, the start instruction responding unit 101 is adapted to trigger a second blocking type event through an instruction to start a container, and trigger a recovery script by the second blocking type event, so as to recover the user directory stored in the storage space outside the container to the container.
In specific implementation, all or part of the user directory is stored in an increment storage mode;
the starting instruction response unit is suitable for determining a difference file stored in the incremental saving mode and a basic user directory corresponding to the difference file, wherein the basic user directory is a part of the user directory which is used as a basis for the incremental saving;
the loading unit 102 may include:
a base user directory recovery unit adapted to recover the base user directory to the container;
and the difference file recovery unit is suitable for recovering the difference file to the corresponding basic user directory.
In a specific implementation, the container control device may further include:
and the storage judging unit 104 is adapted to operate the container when the storage space outside the container does not store the user directory corresponding to the user who sends the instruction for starting the container.
The container control apparatus and the units described in the embodiments of the present application may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer programs. The procedures or functions according to the present application are generated in whole or in part when the computer program instructions are loaded and executed on a computer. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer program may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another computer readable storage medium.
Furthermore, each of the functional modules may be integrated into one processing component, or each of the functional modules may exist alone physically, or two or more functional modules may be integrated into one component. The integrated components can be realized in a hardware form, and can also be realized in a software functional module form. The integrated components described above may also be stored in a computer-readable storage medium if implemented in the form of software functional modules and sold or used as a stand-alone product. The storage medium may be a read-only memory, a magnetic or optical disk, or the like.
The embodiment of the present application further provides a computer device, which may include a memory and a processor, where the memory stores a computer program executable on the processor, and the processor executes the container control method when executing the computer program.
The computer devices include, but are not limited to: the system comprises a server, a desktop computer, a smart phone, a notebook computer, a tablet computer, a smart bracelet, a smart watch, other smart devices or a distributed processing system formed by connecting any one or more devices in a communication way.
The embodiment of the application also provides a computer readable storage medium, on which a computer program is stored, and the computer program executes the container control method when running.
That is, the container control method in the above-described embodiments of the present application may be implemented as software or computer code that can be stored in a recording medium such as a CD ROM, a RAM, a floppy disk, a hard disk, or a magneto-optical disk, or computer code that is originally stored in a remote recording medium or a non-transitory machine-readable medium downloaded through a network and is to be stored in a local recording medium, so that the method described herein may be stored in such software processing on a recording medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware such as an ASIC or FPGA. It will be appreciated that the computer, processor, microprocessor controller or programmable hardware includes memory components (e.g., RAM, ROM, flash memory, etc.) that can store or receive software or computer code that, when accessed and executed by the computer, processor or hardware, implements the container control method described herein. Further, when a general-purpose computer accesses code for implementing the container control method shown herein, execution of the code transforms the general-purpose computer into a special-purpose computer for executing the chemistry container control method shown herein.
Although the embodiments of the present application are disclosed above, the present application is not limited thereto. Various changes and modifications may be effected by one skilled in the art without departing from the spirit and scope of the embodiments of the application, and it is intended that the scope of the application be limited only by the claims appended hereto.
Claims (38)
1. A container control method based on a distributed architecture is characterized by comprising the following steps:
in response to an instruction to stop running a container, storing a user directory corresponding to a user running the container to a storage space outside the container;
and stopping the operation of the container after the user catalog is stored.
2. The container control method according to claim 1, wherein the user directory corresponding to a user who runs the container includes: a public user directory and a private user directory; wherein the common user directory corresponds to a plurality of users; the private user directory corresponds to one user.
3. The container control method according to claim 2, wherein the storing a user directory corresponding to a user who operates the container to a storage space outside the container comprises: and storing the public user directory to a public storage space shared by a plurality of users, and storing the private user directory to a private storage space of a corresponding user.
4. The container control method according to claim 1, wherein the storing of the user directory corresponding to the user operating the container into the storage space outside the container is by compressed storage.
5. The container control method according to claim 1, wherein the storing, in response to the instruction to stop operating the container, the user directory corresponding to the user operating the container to a storage space outside the container comprises: triggering a first blocking type event through the instruction of stopping the operation of the container, and triggering a storage script by the first blocking type event so as to compress and store the user directory, wherein the storage script is stored in a storage space outside the container.
6. The container control method according to claim 1, wherein the storage space outside the container includes a space in a cloud.
7. The container control method according to claim 1, wherein all or part of the user directory is stored in a storage manner of incremental saving.
8. The container control method according to claim 7, wherein the storing all or part of the user directory in the incrementally stored storage manner comprises:
determining a difference directory with content change in the user directory after the container is operated;
determining a file to be saved in the difference directory;
and compressing and saving the file to be saved.
9. The container control method according to claim 1, further comprising:
in response to an instruction to start a container, determining the user directory corresponding to a user who issued the instruction to start the container from a storage space outside the container;
loading the user directory into the container;
and running the container after the user directory is completely loaded.
10. The container control method according to claim 9, wherein the storage space outside the container includes a space in a cloud;
the storing, in response to the instruction to stop running the container, a user directory corresponding to a user running the container to a storage space outside the container includes: triggering a first blocking type event through the instruction of the container stopping operation, and triggering a storage script through the first blocking type event so as to compress and store the user directory, wherein the storage script is stored in the cloud end;
the determining, in response to the instruction to start the container, the user directory corresponding to the user who issued the instruction to start the container from the storage space outside the container comprises: triggering a second blocking type event through an instruction of starting a container, and triggering a recovery script through the second blocking type event so as to recover the user directory stored in the cloud to the container, wherein the recovery script is stored in the cloud.
11. The container control method according to claim 9, wherein the storing a user directory corresponding to a user who operates the container to a storage space outside the container comprises:
determining a difference directory with content change in the user directory after the container is operated;
determining a file to be saved in the difference directory;
compressing and saving the file to be saved;
the loading the user catalog into the container comprises:
restoring the user directory to the container;
and restoring the compressed and saved file to the corresponding user directory.
12. A container control method based on a distributed architecture is characterized by comprising the following steps:
in response to an instruction to start a container, determining a user directory corresponding to a user who issued the instruction to start the container from a storage space outside the container;
loading the user directory into the container;
and running the container after the user directory is completely loaded.
13. The container control method according to claim 12, wherein the user directory comprises a public user directory and a private user directory; wherein the common user directory corresponds to a plurality of users; the private user directory corresponds to one user.
14. The container control method of claim 13, wherein the loading the user directory into the container comprises:
loading the public user directory from a public storage space to the container, the public storage space being unencrypted;
and loading the public user directory from a private storage space to the container, wherein the private storage space corresponds to the user and is an encrypted storage space.
15. The container control method according to claim 12, wherein determining, in response to an instruction to start a container, a user directory corresponding to a user who issued the instruction to start the container from a storage space outside the container comprises: triggering a second blocking type event through an instruction of starting a container, triggering a recovery script by the second blocking type event to recover the user directory stored in the storage space outside the container to the container, wherein the recovery script is stored in the storage space outside the container.
16. The container control method according to claim 12, wherein the storage space outside the container includes a space in a cloud.
17. The container control method according to claim 12, wherein all or part of the user directory is stored by means of incremental saving; the determining, in response to the instruction to start the container, the user directory corresponding to the user who issued the instruction to start the container from the storage space outside the container comprises: determining a difference file stored in the incremental saving mode and a base user directory corresponding to the difference file, wherein the base user directory is a part of the user directory which is used as a base of the incremental saving;
the loading the user catalog into the container comprises:
restoring the base user directory to the container;
and recovering the difference file to the corresponding basic user directory.
18. The container control method according to claim 12, further comprising executing the container if a user directory corresponding to a user who issued the instruction to start the container is not stored in the storage space outside the container.
19. A container control apparatus based on a distributed architecture, comprising:
a stop instruction response unit adapted to store a user directory corresponding to a user who operates the container to a storage space outside the container in response to an instruction to stop operating the container;
and the operation stopping unit is suitable for stopping the operation of the container after the user catalog is stored.
20. The container control device according to claim 19, wherein the user directory corresponding to a user who operates the container includes: a public user directory and a private user directory; wherein the common user directory corresponds to a plurality of users; the private user directory corresponds to one user.
21. The container control device according to claim 20, wherein the stop instruction response unit is adapted to store the public user directory to a public storage space shared by a plurality of users, and store the private user directory to a private storage space of a corresponding user.
22. The container control device according to claim 19, wherein the stop instruction responding unit is adapted to store a user directory corresponding to a user who operates the container in a compressed storage manner to a storage space outside the container.
23. The container control device according to claim 19, wherein the stop instruction response unit is adapted to trigger a first blocking type event by the instruction to stop the operation of the container, and trigger a storage script by the first blocking type event to compress and store the user directory, the storage script being stored in a storage space outside the container.
24. The container control apparatus of claim 19, wherein the storage space outside the container comprises a cloud-based space.
25. The container control apparatus according to claim 19, wherein the stop instruction responding unit is adapted to store all or part of the user directory in a storage manner of incremental saving.
26. The container control device according to claim 25, wherein the stop instruction response unit includes:
the difference catalog unit is suitable for determining the difference catalog with content change in the user catalog after the container runs;
the file to be saved determining unit is suitable for determining a file to be saved in the difference directory;
and the file compression unit is suitable for compressing and storing the file to be stored.
27. The container control apparatus of claim 19, further comprising:
a start instruction response unit adapted to determine, in response to an instruction to start a container, the user directory corresponding to a user who issued the instruction to start the container from a storage space outside the container;
a loading unit adapted to load the user directory into the container;
and the operation unit is suitable for waiting for indicating that the user directory is completely loaded and operating the container.
28. The container control apparatus according to claim 27, wherein the storage space outside the container includes a space in a cloud;
the stop instruction response unit is suitable for triggering a first blocking type event through an instruction of the stop operation container, and storing a storage script triggered by the first blocking type event to compress and store the user directory, wherein the storage script is stored in the cloud end;
the starting instruction response unit is suitable for triggering a second blocking type event through an instruction of a starting container, and triggering a recovery script through the second blocking type event so as to recover the user directory stored in the cloud end to the container.
29. The container control device according to claim 27, wherein the stop instruction response unit includes:
the difference catalogue unit is suitable for determining a difference catalogue of which the content is changed in the user catalogue after the container is operated;
a file to be saved determining unit which determines a file to be saved in the difference directory;
the file compression unit is used for compressing and storing the file to be stored;
the start instruction response unit includes:
a catalog retrieval unit adapted to retrieve the user catalog to the container;
and the file recovery unit is suitable for recovering the compressed and saved files to the corresponding user directory.
30. A container control apparatus based on a distributed architecture, comprising:
a start instruction response unit adapted to determine, in response to an instruction to start a container, the user directory corresponding to a user who issued the instruction to start the container from a storage space outside the container;
a loading unit adapted to load the user directory into the container;
and the operation unit is suitable for waiting for indicating that the user directory is completely loaded and operating the container.
31. The container control apparatus according to claim 30, wherein the user directory comprises a public user directory and a private user directory; wherein the common user directory corresponds to a plurality of users; the private user directory corresponds to one user.
32. The distributed architecture based container control apparatus of claim 31, wherein the loading unit is adapted to load the common user directory into the container from a common storage space, the common storage space being unencrypted; and loading the public user directory from a private storage space to the container, wherein the private storage space corresponds to the user and is an encrypted storage space.
33. The apparatus according to claim 30, wherein the start instruction responding unit is adapted to trigger a second blocking type event by an instruction to start a container, and trigger a recovery script by the second blocking type event to recover a storage space outside the container to store the user directory in the container.
34. The container control apparatus of claim 30, wherein the storage space outside the container comprises a cloud-based space.
35. The container control apparatus according to claim 30, wherein all or part of the user directory is stored by means of incremental saving;
the starting instruction response unit is suitable for determining a difference file stored in the incremental saving mode and a basic user directory corresponding to the difference file, wherein the basic user directory is a part of the user directory which is used as a basis for the incremental saving;
the loading unit includes:
a base user directory recovery unit adapted to recover the base user directory to the container;
and the difference file recovery unit is suitable for recovering the difference file to the corresponding basic user directory.
36. The container control apparatus of claim 30, further comprising:
and the storage judging unit is suitable for operating the container when the user directory corresponding to the user sending the instruction for starting the container is not stored in the storage space outside the container.
37. A computer device comprising a memory and a processor, the memory having stored thereon a computer program operable on the processor, wherein the processor, when executing the computer program, performs the container control method of any of claims 1 to 11, or performs the container control method of any of claims 12 to 18.
38. A computer-readable storage medium, on which a computer program is stored, characterized in that the computer program executes the container control method according to any one of claims 1 to 11, or the container control method according to any one of claims 12 to 18.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110253853.6A CN112631739A (en) | 2021-03-09 | 2021-03-09 | Container control method and device, medium and computer equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110253853.6A CN112631739A (en) | 2021-03-09 | 2021-03-09 | Container control method and device, medium and computer equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112631739A true CN112631739A (en) | 2021-04-09 |
Family
ID=75297742
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110253853.6A Pending CN112631739A (en) | 2021-03-09 | 2021-03-09 | Container control method and device, medium and computer equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112631739A (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108170777A (en) * | 2017-12-26 | 2018-06-15 | 郑州云海信息技术有限公司 | A kind of distributed file system |
| CN110083490A (en) * | 2019-04-29 | 2019-08-02 | 浙江豪联信息科技有限公司 | A kind of database backup method, restoring method and storage medium |
| CN111263933A (en) * | 2017-09-30 | 2020-06-09 | 甲骨文国际公司 | Real-time debug instances in deployed container platforms |
| CN111279314A (en) * | 2017-09-30 | 2020-06-12 | 甲骨文国际公司 | Providing tenant isolation in a multi-tenant API gateway using micro-service containers |
| CN112015438A (en) * | 2020-07-29 | 2020-12-01 | 烽火通信科技股份有限公司 | Lightweight containerized distributed system based on infrastructure and deployment method |
-
2021
- 2021-03-09 CN CN202110253853.6A patent/CN112631739A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111263933A (en) * | 2017-09-30 | 2020-06-09 | 甲骨文国际公司 | Real-time debug instances in deployed container platforms |
| CN111279314A (en) * | 2017-09-30 | 2020-06-12 | 甲骨文国际公司 | Providing tenant isolation in a multi-tenant API gateway using micro-service containers |
| CN108170777A (en) * | 2017-12-26 | 2018-06-15 | 郑州云海信息技术有限公司 | A kind of distributed file system |
| CN110083490A (en) * | 2019-04-29 | 2019-08-02 | 浙江豪联信息科技有限公司 | A kind of database backup method, restoring method and storage medium |
| CN112015438A (en) * | 2020-07-29 | 2020-12-01 | 烽火通信科技股份有限公司 | Lightweight containerized distributed system based on infrastructure and deployment method |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3299957B1 (en) | Performing live updates to file system volumes | |
| US8924954B2 (en) | Application software installation method and application software installation apparatus | |
| EP2765508A1 (en) | Installation method and installation device for application software | |
| CN104866365B (en) | Promote the method, apparatus and electronic equipment of starting up speed | |
| CN113282377B (en) | Code loading method, equipment, system and storage medium under server-free architecture | |
| CN112463290A (en) | Method, system, apparatus and storage medium for dynamically adjusting the number of computing containers | |
| CN104144202B (en) | Access method, system and the device of Hadoop distributed file system | |
| JP6749677B2 (en) | Automatic backup device based on real-time file change detection | |
| CN113626286A (en) | Multi-cluster instance processing method and device, electronic equipment and storage medium | |
| CN113590169B (en) | Application deployment method, application deployment system, and computer-readable storage medium | |
| CN111400105A (en) | Database backup method and device | |
| CN111240892A (en) | Data backup method and device | |
| CN110209525B (en) | Operating system restoration method and device | |
| CN116450287A (en) | Method, device, equipment and readable medium for managing storage capacity of service container | |
| CN113641640B (en) | Data processing method, device, equipment and medium for stream type computing system | |
| CN112416245B (en) | Storage volume management method based on multi-architecture container cloud platform and related components | |
| CN110620798A (en) | Control method, system, equipment and storage medium for FTP connection | |
| CN111190878B (en) | Method, device, equipment and storage medium for sharing access NAS snapshot | |
| CN112631739A (en) | Container control method and device, medium and computer equipment | |
| CN111431951B (en) | Data processing method, node equipment, system and storage medium | |
| US7350065B2 (en) | Method, apparatus and program storage device for providing a remote power reset at a remote server through a network connection | |
| CN109995590A (en) | A kind of user's self-defining device data processing service trustship method | |
| CN1474268A (en) | Service binding system and method | |
| CN108848136B (en) | Shared storage method of cloud service cluster | |
| CN110795113A (en) | Redis cluster service installation method, server and medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |