CN114428668A

CN114428668A - Method, device and system for updating data

Info

Publication number: CN114428668A
Application number: CN202210112250.9A
Authority: CN
Inventors: 宋家亮
Original assignee: Beijing Baidu Netcom Science and Technology Co Ltd
Current assignee: Beijing Baidu Netcom Science and Technology Co Ltd
Priority date: 2022-01-29
Filing date: 2022-01-29
Publication date: 2022-05-03

Abstract

The disclosure provides a method, a device and a system for updating data, relates to the technical field of computers, and particularly relates to a cloud computing technology and a container technology. The specific implementation scheme is as follows: mounting the updated user read-only layer data in a read-only mode, wherein the updated user read-only layer data is stored in a non-host machine; and adding a readable and writable layer on the basis of the mounted updated user read-only layer data, wherein the readable and writable layer is used for supporting a user to write data corresponding to the updated user read-only layer data. Therefore, the updating speed can be greatly improved, and the human resources can be obviously saved when the data of the large-batch containers are updated. And because the mirror image does not need to be downloaded locally, the mirror image is not limited by the storage space of the host, and the container and the node do not have a binding relationship, thereby providing a technical basis for resource pooling and being beneficial to improving the resource use efficiency.

Description

Method, device and system for updating data

Technical Field

The present disclosure relates to the field of computer technologies, and in particular, to a cloud computing technology and a container technology, and in particular, to a method, an apparatus, and a system for updating data.

Background

Multiple containers in a cloud cluster of containers encounter the problem of requiring large amounts of data updates to be completed quickly for the multiple containers.

In the prior art, data in a container is updated by manually logging in each container on a K8s (Kubernets) platform or data needing to be updated is packaged into a new container mirror at each updating time so as to regenerate the container based on the new container mirror.

Disclosure of Invention

A method, an apparatus, an electronic device, and a storage medium for updating data are provided.

According to a first aspect, there is provided a method for updating data, the method comprising: mounting the updated user read-only layer data in a read-only mode, wherein the updated user read-only layer data is stored in a non-host machine; and adding a readable and writable layer on the basis of the mounted updated user read-only layer data, wherein the readable and writable layer is used for supporting a user to write data corresponding to the updated user read-only layer data.

According to a second aspect, there is provided an apparatus for updating data, the apparatus comprising: the mounting unit is configured to mount the updated user read-only layer data in a read-only mode, wherein the updated user read-only layer data is stored in the non-host machine; and the adding unit is configured to add a readable and writable layer on the basis of the mounted updated user read-only layer data, wherein the readable and writable layer is used for supporting a user to write data corresponding to the updated user read-only layer data.

According to a third aspect, there is provided a system for updating data, comprising a master node and at least one slave node running a container; wherein the master node is configured to: writing the updating data into a storage end for storing the data to be updated through a preset updating container to generate updated user read-only layer data, wherein the updating data belongs to a pre-divided read-only data type; the at least one slave node running a container is configured to: a method for updating data as described in any implementation form of the first aspect is performed.

According to a fourth aspect, there is provided an electronic device comprising: at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being executable by the at least one processor to enable the at least one processor to perform the method as described in any one of the implementations of the first aspect.

According to a fifth aspect, there is provided a non-transitory computer readable storage medium having stored thereon computer instructions for enabling a computer to perform the method as described in any one of the implementations of the first aspect.

According to a sixth aspect, there is provided a computer program product comprising a computer program which, when executed by a processor, implements the method as described in any one of the implementations of the first aspect.

According to the technology disclosed by the invention, the effect of rapidly updating the user read-only layer data stored by the non-host machine to the local by dividing the data for updating into the read-only data and the readable write data and adopting a remote mounting mode is realized, and the readable and writable layer is added on the basis of the user read-only layer data for supporting the updating of the user data, so that the updating speed can be greatly increased, the mirror image does not need to be downloaded to the local, the storage space of the host machine is not limited, and the human resources can be remarkably saved when large-batch container data is updated.

It should be understood that the statements in this section do not necessarily identify key or critical features of the embodiments of the present disclosure, nor do they limit the scope of the present disclosure. Other features of the present disclosure will become apparent from the following description.

Drawings

The drawings are included to provide a better understanding of the present solution and are not to be construed as limiting the present disclosure. Wherein:

FIG. 1 is a schematic diagram according to a first embodiment of the present disclosure;

FIG. 2 is a schematic diagram according to a second embodiment of the present disclosure;

FIG. 3 is a schematic diagram of one application scenario in which a method for updating data of an embodiment of the present disclosure may be implemented;

FIG. 4 is a schematic diagram of an apparatus for updating data according to an embodiment of the present disclosure;

FIG. 5 is a timing diagram of interactions between various devices in one embodiment of a system for updating data used to implement embodiments of the present disclosure;

FIG. 6 is a block diagram of an electronic device used to implement a method for updating data of an embodiment of the present disclosure.

Detailed Description

Exemplary embodiments of the present disclosure are described below with reference to the accompanying drawings, in which various details of the embodiments of the disclosure are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the present disclosure. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.

Fig. 1 is a schematic diagram 100 illustrating a first embodiment according to the present disclosure. The method for updating data comprises the following steps:

s101, mounting the updated user read-only layer data in a read-only mode.

In this embodiment, an execution subject (e.g., a node running a container) of the method for updating data may mount the updated user read-only layer data in a read-only manner. The updated user read-only layer data can be stored in a non-host machine.

In this embodiment, the user read-only layer data may include various data for providing a user with read-only rights. The updated user read-only layer data may refer to data itself or a data mirror (Mirroring) updated based on the user read-only layer data. As an example, the user read-only layer data may be, for example, an installation file (version 1.0) of a certain cloud game. The updated user read-only layer data may be an installation file (version 2.0) of a certain cloud game.

It should be noted that the updated user read-only layer data is usually stored in a storage medium other than the host, for example, other electronic devices connected in communication. The host may refer to a physical machine in which the execution main body is located.

And S102, adding a readable and writable layer on the basis of the mounted updated user read-only layer data.

In this embodiment, the execution main body may add a readable and writable layer on the basis of the updated user read-only layer data mounted in step S101 in various ways. The readable and writable layer may be configured to support a user to write data corresponding to the updated user read-only layer data.

In this embodiment, as an example, the execution body may execute an operation of adding a readable and writable layer by an AUFS (Advanced Multi-layer configuration File system) File system or an overlay File system.

In this embodiment, the data corresponding to the updated user read-only layer data may include various data that is associated with the updated user read-only layer data and needs to support reading and writing by a user. As an example, the data corresponding to the user read-only layer data may be a configuration file of a certain cloud game, which may include data related to personalization such as a user archive.

According to the method provided by the embodiment of the disclosure, the data used for updating is divided into the read-only data and the readable write data, the effect of quickly updating the user read-only layer data stored by the non-host computer to the local by adopting a remote mounting mode is realized, and the readable and writable layer is added on the basis of the user read-only layer data for supporting the updating of the user data, so that the updating speed can be greatly increased, the mirror image does not need to be downloaded to the local, the storage space of the host computer is not limited, and the human resources can be obviously saved when a large amount of container data is updated.

In some optional implementations of this embodiment, the updated user read-only layer data may include an update data Snapshot (Snapshot).

In these implementations, the update data snapshot may be a data snapshot generated from data used to update the user read-only data.

Based on the optional implementation manner, the scheme can support data or recovery at corresponding time points in a manner of mounting the data snapshot instead of the original data.

Optionally, based on the above optional implementation manner, the updated user read-only layer data may be stored based on a network storage end; and the update data snapshot is generated in response to determining that the update of the user read-only layer data stored in the network storage end is completed.

In these implementations, the network storage may include various distributed storage services, such as Ceph, GlusterFS, or public cloud storage. In response to determining that the update of the user read-only layer data stored in the distributed storage service is completed, an execution subject (e.g., the k8s control node) for creating a data snapshot may perform a snapshot operation, thereby generating the update data snapshot at the network storage.

Based on the optional implementation mode, the scheme can store the updated user read-only layer data based on a network storage end with high availability and reliability, and greatly reduces the requirement on the storage space of the host machine node; in addition, the updated user read-only layer data is stored in the non-host, so that no binding relation exists between the container and the node, resource pooling is supported, and resource utilization efficiency is improved.

With continued reference to fig. 2, fig. 2 is a schematic diagram 200 according to a second embodiment of the present disclosure. The method for updating data comprises the following steps:

s201, mounting the user read-only layer data stored in the non-host machine in a read-only mode.

In this embodiment, an execution subject (e.g., a node running a container) of the method for updating data may mount user read-only layer data stored on a non-host in a read-only manner.

In this embodiment, the user read-only layer data may include various data itself or data mirror (Mirroring) for providing the user read-only right. As an example, the user read-only layer data may be, for example, an installation file (version 1.0) of a certain cloud game.

It should be noted that the user read-only layer data is generally stored in a storage medium other than the host, for example, other electronic devices connected in communication. The host may refer to a physical machine in which the execution main body is located.

In this embodiment, the user read-only layer data is generated by writing initialization data into a storage terminal for storing data to be updated based on the initialization container. The data to be updated belongs to a read-only data type which is divided in advance. The storage end for storing the data to be updated may be a storage medium other than the host.

In the present embodiment, data may be divided into a read-only data type and a read-write data type in advance. Then, the node running the initialization container may write the initialization data in the initialization container into a storage end for storing data to be updated. Wherein the initialization data is also typically of the read-only type. Alternatively, the data to be updated may be the same as the initialization data.

S202, a readable and writable layer is added on the basis of the mounted user read-only layer data.

In this embodiment, the execution main body may add a readable and writable layer on the basis of the user read-only layer data mounted in step S201 in various ways. The readable and writable layer may be configured to support a user to write data corresponding to the user read-only layer data.

In this embodiment, the data corresponding to the user read-only layer data may include various data associated with the user read-only layer data and required to support reading and writing by a user. As an example, the data corresponding to the user read-only layer data may be a configuration file of a certain cloud game, which may include data related to personalization such as a user archive.

S203, mounting the updated user read-only layer data in a read-only mode.

And S204, adding a readable and writable layer on the basis of the mounted updated user read-only layer data.

The above S203 and S204 may be respectively consistent with S101 and S102 in the foregoing embodiment and their optional implementation manners, and the above description on S101 and S102 and their optional implementation manners also applies to SS203 and S204, which is not described herein again.

Optionally, the user read-only layer data described in the first step may include an initialization data snapshot generated based on the initialization data.

In these implementations, the initialization data snapshot may be a data snapshot generated by performing a snapshot operation on the initialization data.

Optionally, based on the optional implementation manner, the user read-only layer data may be stored based on a network storage terminal; and the initialization data snapshot is generated in response to determining that the data stored in the network storage end is initialized.

In these implementations, the network storage may include various distributed storage services, such as Ceph, GlusterFS, or public cloud storage. In response to determining that the data stored in the distributed storage service completes initialization, an execution subject (e.g., the K8s control node) for creating a data snapshot may perform a snapshot operation, thereby generating the initialization data snapshot at the network storage.

Based on the optional implementation mode, the scheme can store initialized user read-only layer data based on a network storage end with high availability and reliability, and greatly reduces the requirement on the storage space of the host machine node; in addition, because the initialized data of the user read-only layer is stored in the non-host machine, no binding relation exists between the container and the node, so that resource pooling is supported, and the resource utilization efficiency is improved.

As can be seen from fig. 2, a flow 200 of the method for updating data in this embodiment represents a step of mounting user read-only layer data stored in a non-host in a read-only manner, and a step of adding a readable and writable layer on the basis of the mounted user read-only layer data. Therefore, in the scheme described in this embodiment, the initialization container can be used to write initialization data into a non-host, the read-only layer data of the user can be quickly synchronized to the local in a remote mounting manner, and the user is supported to write data in a manner of adding a read-write layer, so that quick initialization of multiple containers can be realized, and human resources can be remarkably saved.

With continued reference to fig. 3, fig. 3 is a schematic diagram of an application scenario of a method for updating data according to an embodiment of the present disclosure. In the application scenario of fig. 3, optionally, a user may update the user read-only layer data 305 through the container-running node 301 accessing the remote storage 304 in a read-write manner. Alternatively, data snapshot 0 before the user read-only layer data 305 is updated may be shown as 306 in fig. 3. The updated data snapshot 1 of the user read-only layer data 305 can be shown as 307 in fig. 3. Thereafter, both

nodes

302, 303 running the container may mount the updated user read-only layer data 305 or data snapshot 1 (shown as 307 in fig. 3) stored in the remote storage 304 in a read-only manner. Then, the

nodes

302 and 303 running with the container may add a readable and writable layer on the basis of the mounted updated user read-only layer data, so as to support the user to write data corresponding to the updated user read-only layer data.

At present, one of the prior art often uses manual login to each container to update data in the container or packages data to be updated into a new container image during each update, so as to regenerate the container based on the new container image, thereby when a large amount of data is updated, because the time consumed by manually updating each container in sequence is long, errors are easy to occur, and because the updated data or downloading the new container image needs to occupy the storage space of a node host, there is a limit on the hardware (especially, the storage space) of the host. In the method provided by the embodiment of the disclosure, the data for updating is divided into read-only data and readable write data, the effect of quickly updating the user read-only layer data stored by the non-host computer to the local by adopting a remote mounting mode is realized, and the readable and writable layer is added on the basis of the user read-only layer data to support the updating of the user data, so that the updating speed can be greatly increased, and the human resources can be remarkably saved when large-batch container data is updated. And because the mirror image does not need to be downloaded locally, the mirror image is not limited by the storage space of the host machine, and because the user read-only layer data stored by the non-host machine is adopted instead of storing the data locally on the host machine, the container and the node do not have a binding relationship, thereby providing a technical basis for resource pooling and being beneficial to improving the resource use efficiency.

With further reference to fig. 4, as an implementation of the methods shown in the above figures, the present disclosure provides an embodiment of an apparatus for updating data, which corresponds to the method embodiment shown in fig. 1 or fig. 2, and which may be applied in various electronic devices in particular.

As shown in fig. 4, the apparatus 400 for updating data provided by the present embodiment includes a mount unit 401 and an add unit 402. The mounting unit 401 is configured to mount updated user read-only layer data in a read-only manner, where the updated user read-only layer data is stored in a non-host; an adding unit 402, configured to add a readable and writable layer on the basis of the mounted updated user read-only layer data, where the readable and writable layer is used to support a user to write data corresponding to the updated user read-only layer data.

In the present embodiment, in the apparatus 400 for updating data: the detailed processing of the mounting unit 401 and the adding unit 402 and the technical effects thereof can refer to the related descriptions of steps S101 and S102 in the corresponding embodiment of fig. 1, which are not repeated herein.

In some optional implementations of this embodiment, the updated user read-only layer data includes an updated data snapshot.

In some optional implementation manners of this embodiment, the updated user read-only layer data is stored based on a network storage terminal; and the update data snapshot is generated in response to determining that the update of the user read-only layer data stored in the network storage end is completed.

In some optional implementations of this embodiment, the mount unit 401 may be further configured to: mounting user read-only layer data stored in a non-host computer in a read-only mode, wherein the user read-only layer data is generated by writing initialization data into a storage end for storing data to be updated based on an initialization container, and the data to be updated belongs to a pre-divided read-only data type; the adding unit 402 may be further configured to: and adding a readable and writable layer on the basis of the mounted user read-only layer data, wherein the readable and writable layer is used for supporting a user to write data corresponding to the user read-only layer data.

In some optional implementations of this embodiment, the user read-only layer data may include an initialization data snapshot generated based on the initialization data.

In some optional implementation manners of this embodiment, the user read-only layer data may be stored based on a network storage side. The initialization data snapshot may be generated in response to determining that the data stored in the network storage completes initialization.

According to the device provided by the above embodiment of the present disclosure, data for updating is divided into read-only data and readable write data, and the mounting unit 401 is used for rapidly updating the user read-only layer data stored by the non-host computer to the local by using a remote mounting method, and the adding unit 402 is used for adding the readable and writable layer for supporting the updating of the user data on the basis of the user read-only layer data, so that the updating speed can be greatly increased, and human resources can be significantly saved when large-batch container data is updated. And because the mirror image does not need to be downloaded locally, the mirror image is not limited by the storage space of the host machine, and because the user read-only layer data stored by the non-host machine is adopted instead of storing the data locally on the host machine, the container and the node do not have a binding relationship, thereby providing a technical basis for resource pooling and being beneficial to improving the resource use efficiency.

With further reference to FIG. 5, a timing diagram 500 of interactions between various devices in one embodiment of a system for updating data is illustrated. The system for updating data may include: a master node (e.g., a control node of K8 s) and at least one slave node running a container (e.g., a Worker node of K8 s). Wherein the master node may be configured to: and writing the updating data into a storage end for storing the data to be updated through a preset updating container to generate updated user read-only data, wherein the updating data belongs to a pre-divided read-only data type. The at least one slave node running the container may be configured to: the method for updating data as described in the previous embodiments is performed.

In some optional implementations of this embodiment, the master node may be further configured to: and writing the initialization data into a storage end through a preset initialization container to generate user read-only layer data.

As shown in fig. 5, in step 501, the master node writes the update data into the storage end for storing the data to be updated through a preset container for updating, and generates updated user read-only layer data.

In this embodiment, the master node may create a container for updating (running in the slave node 1 described above), that is, a preset container, in advance. And then, the main node writes the updating data into a storage end for storing the data to be updated through the preset updating container to generate updated user read-only layer data. The update data may belong to a pre-divided read-only data type.

It should be noted that the above-mentioned generating updated user read-only layer data and the related content related to the storage end may be consistent with the description in the foregoing embodiments, and are not described herein again. The update data may include the data itself or a data snapshot for updating the user read-only data.

In step 502, the master node starts a container running on the slave node 2, and the container mounts the updated user read-only layer data in a read-only manner.

In step 503, the container running on the slave node 2 adds a readable and writable layer on the basis of the mounted updated user read-only layer data.

Step 502 and step 503 are respectively consistent with step 101 and step 102 in the foregoing embodiment and their optional implementations, and the above description on step 101 and step 102 and their optional implementations also applies to step 502 and step 503, which is not described herein again.

In some optional implementations of this embodiment, before creating the container for updating, the master node may also create an initialization container in advance, that is, a preset initialization container. And then, the main node can write the initialization data into the storage end through the preset initialization container to generate user read-only layer data.

Alternatively, the master node may push out the initialization container after the data initialization is completed.

It should be noted that the above-mentioned manner of generating the user read-only layer data may be consistent with the corresponding description in the optional implementation manner of the foregoing embodiment, and is not described herein again.

In the system for updating data provided in the foregoing embodiment of the present application, first, the master node writes, through a preset update container, update data belonging to a pre-divided read-only data type into a storage end for storing data to be updated, and generates updated user read-only layer data. Then, at least one slave node operating with a container mounts updated user read-only layer data stored in a non-host machine in a read-only mode; and adding a readable and writable layer for supporting a user to write data corresponding to the updated user read-only layer data on the basis of the mounted updated user read-only layer data. Therefore, the updating speed can be greatly improved, and the human resources can be obviously saved when the data of the large-batch containers are updated. And because the mirror image does not need to be downloaded locally, the mirror image is not limited by the storage space of the host machine, and because the user read-only layer data stored by the non-host machine is adopted instead of storing the data locally on the host machine, the container and the node do not have a binding relationship, thereby providing a technical basis for resource pooling and being beneficial to improving the resource use efficiency.

In the technical scheme of the disclosure, the collection, storage, use, processing, transmission, provision, disclosure and other processing of the personal information of the related user are all in accordance with the regulations of related laws and regulations and do not violate the good customs of the public order.

The present disclosure also provides an electronic device, a readable storage medium, and a computer program product according to embodiments of the present disclosure.

FIG. 6 illustrates a schematic block diagram of an example electronic device 600 that can be used to implement embodiments of the present disclosure. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be examples only, and are not meant to limit implementations of the disclosure described and/or claimed herein.

As shown in fig. 6, the apparatus 600 includes a computing unit 601, which can perform various appropriate actions and processes according to a computer program stored in a Read Only Memory (ROM)602 or a computer program loaded from a storage unit 608 into a Random Access Memory (RAM) 603. In the RAM 603, various programs and data required for the operation of the device 600 can also be stored. The calculation unit 601, the ROM 602, and the RAM 603 are connected to each other via a bus 604. An input/output (I/O) interface 605 is also connected to bus 604.

A number of components in the device 600 are connected to the I/O interface 605, including: an input unit 606 such as a keyboard, a mouse, or the like; an output unit 607 such as various types of displays, speakers, and the like; a storage unit 608, such as a magnetic disk, optical disk, or the like; and a communication unit 609 such as a network card, modem, wireless communication transceiver, etc. The communication unit 609 allows the device 600 to exchange information/data with other devices via a computer network such as the internet and/or various telecommunication networks.

The computing unit 601 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of the computing unit 601 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various dedicated Artificial Intelligence (AI) computing chips, various computing units running machine learning model algorithms, a Digital Signal Processor (DSP), and any suitable processor, controller, microcontroller, and so forth. The calculation unit 601 performs the respective methods and processes described above, such as a method for updating data. For example, in some embodiments, the method for updating data may be implemented as a computer software program tangibly embodied on a machine-readable medium, such as storage unit 608. In some embodiments, part or all of a computer program may be loaded onto and/or installed onto device 600 via ROM 602 and/or communications unit 609. When the computer program is loaded into the RAM 603 and executed by the computing unit 601, one or more steps of the method for updating data described above may be performed. Alternatively, in other embodiments, the computing unit 601 may be configured to perform the method for updating data by any other suitable means (e.g. by means of firmware).

Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuitry, Field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), system on a chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, receiving data and instructions from, and transmitting data and instructions to, a storage system, at least one input device, and at least one output device.

Program code for implementing the methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowchart and/or block diagram to be performed. The program code may execute entirely on the machine, partly on the machine, as a stand-alone software package partly on the machine and partly on a remote machine or entirely on the remote machine or server.

In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which a user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic, speech, or tactile input.

The systems and techniques described here can be implemented in a computing system that includes a back-end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), Wide Area Networks (WANs), and the Internet.

The computer system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server may be a cloud server, a server of a distributed system, or a server with a combined blockchain.

It should be understood that various forms of the flows shown above, reordering, adding or deleting steps, may be used. For example, the steps described in the present disclosure may be executed in parallel or sequentially or in different orders, and are not limited herein as long as the desired results of the technical solutions disclosed in the present disclosure can be achieved.

The above detailed description should not be construed as limiting the scope of the disclosure. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may be made in accordance with design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present disclosure should be included in the scope of protection of the present disclosure.

Claims

1. A method for updating data, comprising:

mounting updated user read-only layer data in a read-only mode, wherein the updated user read-only layer data is stored in a non-host machine;

and adding a readable and writable layer on the basis of the mounted updated user read-only layer data, wherein the readable and writable layer is used for supporting a user to write data corresponding to the updated user read-only layer data.

2. The method of claim 1, wherein the updated user read-only layer data comprises an update data snapshot.

3. The method of claim 2, wherein the updated user read-only layer data is stored based on a network storage; and

the update data snapshot is generated in response to determining that a user read-only layer data update stored at the network storage is complete.

4. The method of any of claims 1-3, wherein prior to said mounting updated user read-only layer data in a read-only manner, the method further comprises:

the method comprises the steps that user read-only layer data stored in a non-host computer are mounted in a read-only mode, wherein the user read-only layer data are generated by writing initialization data into a storage end used for storing data to be updated on the basis of an initialization container, and the data to be updated belong to a pre-divided read-only data type;

and adding a readable and writable layer on the basis of the mounted user read-only layer data, wherein the readable and writable layer is used for supporting a user to write data corresponding to the user read-only layer data.

5. The method of claim 4, wherein the user read-only layer data comprises an initialization data snapshot generated based on the initialization data.

6. The method of claim 5, wherein the user read-only layer data is stored based on a network storage; and the initialization data snapshot is generated in response to determining that the data stored in the network storage end completes initialization.

7. An apparatus for updating data, comprising:

a mounting unit configured to mount updated user read-only layer data in a read-only manner, wherein the updated user read-only layer data is stored in a non-host;

and the adding unit is configured to add a readable and writable layer on the basis of the mounted updated user read-only layer data, wherein the readable and writable layer is used for supporting a user to write data corresponding to the updated user read-only layer data.

8. A system for updating data comprising a master node and at least one slave node running a container;

wherein the master node is configured to: writing update data into a storage end for storing data to be updated through a preset container for updating to generate updated user read-only layer data, wherein the update data belongs to a read-only data type which is divided in advance;

the at least one slave node running a container is configured to: performing the method for updating data according to one of claims 1 to 6.

9. The system of claim 8, wherein the master node is further configured to:

and writing the initialization data into the storage terminal through a preset initialization container to generate user read-only layer data.

10. An electronic device, comprising:

at least one processor; and

a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,

the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-6.

11. A non-transitory computer readable storage medium having stored thereon computer instructions for causing the computer to perform the method of any one of claims 1-6.

12. A computer program product comprising a computer program which, when executed by a processor, implements the method according to any one of claims 1-6.