KR20160003515A - Device and method for operation atomicity and storage replication of cloud storage based collaborative middleware - Google Patents

Abstract

The present invention relates to a device and method for an atomic operation and storage replication of collaborative middleware based on a cloud storage. According to an embodiment of the present invention, the method includes: a first step for conducting storage primitive operations (SPOs) wherein a cloud manager processes the resource of a cloud storage; a second step for conducting metadata primitive operations (MPOs) wherein a database manager processes metadata of the resource stored in a database; and a third step wherein the cloud manager resets the cloud storage to a condition prior to the execution of the SPOs, while the database manager resets the metadata of the resources to a condition prior to the execution of the MPOs, if at least any one of SPO or MPO has not been executed.

Description

TECHNICAL FIELD [0001] The present invention relates to an atomic operation of a collaborative middleware based on cloud storage, a storage replication apparatus, and a storage replication apparatus and method.

Embodiments of the present invention relate to atomic computing and storage replication devices and methods of collaborative middleware based on cloud storage.

Cloud Storage Service is one of the cloud computing services that provides remote storage management work on resources.

Cloud storage has features like cloud computing in terms of agility, scalability, resiliency, and multi-tenancy, and the virtualized pool of storage provides massive storage and storage for individual users as well as groups of users do.

C3ware can manage workspace resources at the same time as group tasks such as creating groups or creating memberships in groups, and using multiple cloud storages simultaneously for reliable resource management.

C3ware can provide collaborative services and work space through cloud storage and can provide multiple types of workplaces to users and groups. At this time, the workplace may be provided with a personal workspace, a group workspace, and an open workspace.

Conventional cloud storage services do not store metadata about resources. For this reason, there is a problem that resource management on a system is not easy.

Related Prior Art Korean Patent Publication No. 10-2014-0032862 (entitled " Integrated Cloud Service Providing Apparatus and Method, Public Date: March 17, 2014) "

One embodiment of the present invention is to provide an operation atomicity method capable of maintaining consistency in a cloud-based collaborative middleware.

In addition, one embodiment of the present invention defines a primitive operation for a resource of a cloud storage and metadata stored in a database, and performs a service operation ) Is configured as a queue of primitive operations, and all primitive operations are performed or all primitive operations are not performed, thereby preventing only a part of resources and metadata from being updated.

In addition, according to an embodiment of the present invention, it is possible to ensure that the most available storage among the storages storing the resources including all the latest information is the master storage, so that the master storage can easily and quickly I want to be able to access it.

In addition, one embodiment of the present invention seeks to provide replication and recovery of resources in multiple cloud storages.

The problems to be solved by the present invention are not limited to the above-mentioned problem (s), and another problem (s) not mentioned can be clearly understood by those skilled in the art from the following description.

The atomic operation and the storage replication method of the collaborative middleware based on the cloud storage according to an embodiment of the present invention include a first step in which a cloud manager performs storage primitive operations (SPO) for processing resources of a cloud storage ; A second step of a database manager performing metadata primitive operations (MPO) for processing metadata of the resource stored in the database; And if the raw operation of at least one of the storage raw operations and the metadata raw operations is not performed, the cloud manager returns the cloud storage to a state prior to execution of the storage raw operations, And returning the metadata of the resource to a state before the execution of the metadata primitive operations.

Wherein the first step sequentially executes operations included in the storage source operations by the cloud manager, and the second step allows the database manager to sequentially execute the operations included in the metadata source operations .

In the third step, the database manager performs a commit command when all the primitive operations of the metadata primitive operations are executed, and if the primitive operation of at least one of the metadata primitive operations is not executed, ) Command.

The storage primitive operation and the metadata primitive operation may be Create, Read, Update and Delete operations of data.

The first step includes a first step of the cloud manager including a primitive operation in a queue in a primitive operation queue of each of a plurality of storages in a requested order; A first step of each of the storages executing an operation according to a sequence of primitive operations included in the queue; And a third step of the cloud manager designating one of the storages in which the primitive operation of the queue is executed as the master storage.

The first step is that the cloud manager does not remove the primitive operation from the queue if the primitive operation included in the queue is not executed in each of the storages; And (5) when the storage manager is restored to a normal state, the cloud manager executes a raw operation that is included in the queue but is not executed.

Further comprising the step of displaying a green indicating that each of the plurality of storages is in a standby state before the step of the first step, Displays a yellow color indicating that a raw operation included in the queue is being executed in each of the storages, and the step (1-4) displays the raw operation included in the queue in each of the storages The storage status display unit displays a blue color indicating that each storage is restored to a normal status, and the first step displays a red color indicating that the storage has not been executed, If the queues are full or the storage is not available because the primitive operations included in the queue are not executed in each of the storages, Ridge status display unit is the first stage 1-6 for displaying black (Black); can further comprise a.

In the step 1-3, the cloud manager may designate, as sub-storage, storage other than the designated master storage among the storages in which all the primitive operations of the queue are executed.

The atomic operation of the collaboration middleware based on the cloud storage according to an embodiment of the present invention and the storage replication apparatus include a cloud storage for storing resources; A cloud manager for performing storage primitive operations (SPOs) for processing resources of the cloud storage; A database for storing metadata of the resources; And a database manager for performing metadata primitive operations (MPOs) for processing metadata of the resources stored in the database, wherein at least one of the storage primitive operations and the metadata primitive operations The cloud manager returns the cloud storage to a state prior to execution of the storage primitive operations and the database manager returns the metadata of the resource to a state prior to execution of the metadata primitive operations Turn it.

The cloud manager may sequentially execute the operations included in the storage primitive operations, and the database manager may sequentially execute the operations included in the metadata primitive operations.

The database manager performs a commit command when all the primitive operations of the metadata primitive operations are executed and performs a rollback command if at least one primitive operation of the metadata primitive operations is not executed .

The storage primitive operation and the metadata primitive operation may be Create, Read, Update and Delete operations of data.

Wherein the cloud manager includes a primitive operation in a queue of primitive operations of each of a plurality of storages in a requested order, and each storage executes an operation according to a sequence of primitive operations included in the queue , And designate one of the storages in which the primitive operation of the queue is executed as master storage.

Wherein the cloud manager does not remove the primitive operations from the queue if primitive operations included in the queues are not performed in the respective storages and if the respective storages are restored to a normal state, You can perform primitive operations.

Wherein the storage status display unit displays green when each of the plurality of storages is in a standby state and displays yellow when each of the storages is executing a primitive operation included in the queue, Displaying red when the primitive operations included in the queue are not executed and displaying blue when the respective storage is restored to a normal state and primitive operations included in the queue are not executed in each of the storages If the queue is full or the storage is not available, the storage status indicator may display black.

The cloud manager may designate, as sub-storage, storage other than the specified master storage among the storages in which all the primitive operations of the queue are executed.

The details of other embodiments are included in the detailed description and the accompanying drawings.

According to an embodiment of the present invention, it is possible to provide an operation atomicity method capable of maintaining consistency in collaborative middleware based on cloud storage.

According to an embodiment of the present invention, a resource of a cloud storage and a primitive operation for metadata stored in a database are defined, and a service operation, Is configured as a queue of primitive operations and all primitive operations are performed or all primitive operations are not performed to prevent only a part of the resources and metadata from being updated.

According to an embodiment of the present invention, it is possible to easily and quickly access the latest version of resources through the master storage by ensuring that the most available storage among the storages storing resources including all the latest information is the master storage .

One embodiment of the present invention seeks to provide replication and recovery of resources in multiple cloud storages.

1 is a view for explaining a collaborative service and a work space according to an embodiment of the present invention.
FIG. 2 is a view for explaining a configuration for atomic computing of a collaboration middleware based on cloud storage according to an embodiment of the present invention.
FIG. 3 is a diagram for explaining a configuration for replicating storages of collaborative middleware based on cloud storage according to an embodiment of the present invention. Referring to FIG.
FIG. 4 is a diagram illustrating a method of displaying the state of the cloud storage according to an embodiment of the present invention. Referring to FIG.
5 is a flowchart illustrating an atomic operation and a storage replication method of a collaborative middleware based on cloud storage according to an embodiment of the present invention.
6 is a flowchart illustrating a replication method of a cloud storage according to an embodiment of the present invention.
7 is a graph for comparing the performance of the conventional technology with the atomic operation of the collaboration middleware based on the cloud storage according to an embodiment of the present invention and the storage replication method.

BRIEF DESCRIPTION OF THE DRAWINGS The advantages and / or features of the present invention, and how to accomplish them, will become apparent with reference to the embodiments described in detail below with reference to the accompanying drawings. It should be understood, however, that the invention is not limited to the disclosed embodiments, but is capable of many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, To fully disclose the scope of the invention to those skilled in the art, and the invention is only defined by the scope of the claims. Like reference numerals refer to like elements throughout the specification.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.

FIG. 1 is a diagram for explaining a collaborative service and a work space according to an embodiment of the present invention. FIG. 2 is a diagram illustrating an atomic operation of a collaboration middleware based on cloud storage according to an embodiment of the present invention. Fig.

As shown in FIG. 1, according to an embodiment of the present invention, a middleware 100 can provide a collaborative service and a work space through a cloud storage.

In more detail, the atomic operation of the collaborative middleware based on the cloud storage and the storage replication apparatus 100 may be constituted by C3ware, and the atomic operation and the storage replication apparatus 100, May provide a personal workspace 115, a group workspace 125, and an open workspace 135 to the users 110, 111, 112 and the user group 120.

The atomic operation and the storage replica device 100 can manage the resources of the workplace at the time of executing group operations such as creating a group 120 or making a membership in a group. , A plurality of cloud storages 215 and 216 are used simultaneously as shown in FIG.

Generally, the cloud storage service provides basic resource management functions through the cloud storage 215 and 216 and stores metadata of resources in the database 225 in order to support operations required during group operations metadata can be stored to maintain consistency between the plurality of cloud storages 215 and 216 and the metadata.

2, the atomic operation and the storage replication apparatus of the collaboration middleware based on the cloud storage according to an embodiment of the present invention includes the cloud storage 215 and 216, the cloud managers 211 and 212, the database 225, And a database manager 220.

The cloud storages 215 and 216 store resources and the cloud managers 211 and 212 perform storage primitive operations (SPO) for processing the resources of the cloud storages 215 and 216.

The database 225 stores metadata of the resource and the database manager 220 performs metadata primitive operations (MPO) for processing the metadata of the resource stored in the database 225 .

The primitive operations included in the storage primitive operations and the metadata primitive operations are operations for handling resource information of the cloud storages 211 and 212 and meta data of the database 225, (Create), Read (Read), Update (Update), and Delete (Delete) operations.

Table 1 shows the primitive operations according to an embodiment of the present invention by dividing them into the storage primitive operation and the metadata primitive operation.

The primitive operation according to an embodiment of the present invention can be divided into a storage primitive operation and a metadata primitive operation as shown in Table 1. [

Kinds calculate Explanation

Storage Primitive Operation S1 Create Folder S2 Remove folder S3 File creation S4 Remove file S5 Edit documents / folders S6 Read document information S7 Getting documents S8 Restoring documents / folders using versioning Metadata Raw Operations
(Metadata Primitive Operation) M1 Metadata generation M2 Remove metadata M3 Edit metadata M4 Read Metadata

As shown in Table 1, the storage primitive operation is a primitive operation for recovering and managing the resources of the cloud storage, and the metadata primitive operation is a primitive operation for processing the metadata of the resource at the time of group operation.

In a collaborative service according to an embodiment of the present invention, all primitive operations are executed in an atomic manner such as a transaction.

When executing the collaboration service, all the primitive operations constituting the collaboration service are executed in order. If the execution of one primitive operation fails during the execution of the primitive operations in the above order, Cancel all collaborative services partially performed by

That is, if the raw operation of at least one of the storage primitive operations and the metadata primitive operations is not performed, the cloud managers 211 and 212 may cause the cloud storage 215 and 216 to execute the storage primitive operations The database manager 220 returns the metadata of the resource to a state prior to execution of the metadata primitive operations.

More specifically, the database manager 220 performs a commit command when all the primitive operations of the metadata primitive operations are executed, and if at least one primitive operation of the metadata primitive operations is not performed You can perform a rollback command.

FIG. 3 is a diagram for explaining a configuration for replicating storages of collaborative middleware based on cloud storage according to an embodiment of the present invention. Referring to FIG.

As shown in FIG. 3, when each of the cloud managers 211, 212, and 213 of the cloud storage 215, 216, and 217 receives the Storage Primitive Operation through the storage connector manager 230, And includes the received primitive operations in queues 201, 202, and 203 of the respective cloud storages in the order received.

Each of the queues 201, 202, and 203 is allocated to each of the storages 215, 216, and 217, and the storages 215, 216, and 217 of the respective cloud managers 211, 201, 202, and 203 in accordance with the order of the primitive operations.

At this time, if the primitive operations included in the queues 201, 202, and 203 are successfully executed, they are removed from the queues 201, 202, and 203 and the next primitive operation is performed. Until then, the execution and removal of primitive operations continues.

The cloud managers 211, 212, and 213 may perform the primitive operations in the queues 201, 202, and 203 in the respective storages 215, 216, and 217, 202 and 203 and when the respective storage units 215, 216, and 217 are restored to their normal state, they execute raw operations that are included in the queues 201, 202, and 203 but are not executed.

That is, when the primitive operation fails due to a network failure or the like, the cloud managers 211, 212, and 213 stop the primitive operation and do not remove operations from the queues 201, 202, and 203, And the raw operations remaining in the queues 201, 202, 203 can be executed in the storage 215, 216, 217 in order when the storage is restored to a normal state.

Thus, each of the cloud managers 211, 212, and 213 can execute all primitive operations included in the queues 201, 202, and 203, and when all the queues are emptied, all the storages 215, 216, Resources.

In addition, the cloud managers 211, 212, and 213 may designate at least one of the arithmetic operations of the queues 201, 202, and 203 as master storage. Therefore, according to an embodiment of the present invention, by designating the most available storage among the storages storing resources including all the latest information as master storage, it is possible to easily and quickly access the latest version of resources Access.

In another embodiment of the present invention, the cloud managers 211, 212, and 213 may be configured to ensure master storage so that primitive operations are performed only when at least one master storage is specified.

For example, when the cloud managers 211, 212, and 213 fail to specify the master storage because the operations are not completely executed in all the cloud storages, the cloud managers 211, 212, and 213 do not perform the primitive operations included in the queues allocated to each of the cloud storages And waiting for at least one of the cloud storage to be designated as master storage, master storage can be guaranteed by performing the primitive operations included in the queue.

FIG. 4 is a diagram illustrating a method of displaying the state of the cloud storage according to an embodiment of the present invention. Referring to FIG.

According to an exemplary embodiment of the present invention, in order to monitor and manage the state of the cloud storage, each of the cloud storage devices may be classified into one of green, yellow, red, blue, ) Can be displayed in a total of five colors.

The color representing the state of each storage varies according to the state of each of the cloud storages.

More specifically, as shown in FIG. 4, the storage status display unit displays green when each of the plurality of storages is in the standby state, and when executing the primitive operation included in the queue in each of the storages Yellow (Yellow) can be displayed.

The storage status display unit may display a red color if the primitive operation included in the queue is not executed in each of the storages, and may display a blue color when the storage is restored to a normal state or the network is disconnected. And can display black if the queues in which the primitive operations included in the queue are not executed in the storage are full or the respective storage is not available.

Thus, according to one embodiment of the present invention, by monitoring each state of the cloud storage more effectively and designating the highest available storage containing all the latest information as master storage, it is possible to easily access the latest version of the resource can do.

5 is a flowchart illustrating an atomic operation and a storage replication method of a collaborative middleware based on cloud storage according to an embodiment of the present invention.

First, the cloud manager performs storage primitive operations (SPO) for processing resources of the cloud storage (S510).

At this time, the cloud manager sequentially executes the operations included in the storage primitive operations.

Thereafter, the database manager performs metadata primitive operations (MPO) for processing metadata of the resources stored in the database (S520).

Similarly, the database manager sequentially executes the operations included in the metadata primitive operations.

The storage primitive operation and the meta data primitive operation may be composed of data generation (Create), read (Read), update (Update), and delete (Delete) operations.

Thereafter, it is determined whether the atomic operation of the collaboration middleware and the storage replication apparatus have executed at least one of the storage source operations and the metadata source operations (S530), and the storage source operations and the meta If at least one of the primitive operations of the data source operations is not executed, the cloud manager returns the cloud storage to a state before execution of the storage primitive operations through a rollback command (S540) The metadata of the resource is restored to a state before execution of the metadata primitive operations through a rollback command in operation S545.

More specifically, the database manager performs a commit command when all the primitive operations of the metadata primitive operations are executed, and performs a rollback when at least one of the metadata primitive operations is not executed. ) Command.

That is, when executing the collaboration service, all of the primitive operations constituting the collaboration service are executed in order, and when execution of one of the primitive operations fails during the execution of the primitive operations in the above order, Cancel all collaborative services partially performed by the operation.

FIG. 6 is a flowchart for explaining a replication method of a cloud storage according to an embodiment of the present invention, in more detail, step S510 in which the storage primitive operations of FIG. 5 are performed.

When the storage manager receives the storage primitive operation, the cloud manager includes the received primitive operations in the queue of each cloud storage in the order received, S511.

Each of the queues is allocated to each storage, and the cloud manager causes each storage to perform an operation according to the order of primitive operations included in the queue (S512).

At this time, if the primitive operation included in the queue is successfully executed, the primitive operation is removed from the queue, the next primitive operation is executed, and the execution and removal of the primitive operation is continued until the end of the queue.

However, if the raw operation included in the queue is not executed in each of the storages (S513), the cloud manager does not remove the original operation from the queue (S514). If the storage is restored to the normal state (S515 ), A raw operation that is contained in the queue but is not executed is executed (S516).

That is, when a primitive operation fails due to a network failure or the like, the cloud manager stops the operation, does not remove the operation from the queue, marks the storage as unusable, and if the storage is restored to the normal state, Operations can be run in sequence on storage.

Thus, each cloud manager can execute all the primitive operations contained in the queue, and when all the queues are empty, all the storage will have the same resources, and the cloud manager will have one of the queues' It can be designated as master storage.

7 is a graph for comparing the performance of the conventional technology with the atomic operation of the collaboration middleware based on the cloud storage according to an embodiment of the present invention and the storage replication method.

Hereinafter, the performance of the present invention and the conventional DEPSKY will be compared with reference to FIG.

The prior art DEPSKY is a technology for storing information in cloud storage through data replication of various cloud storages.

DEPSKY is implemented as a software library on the client that provides object storage interfaces similar to those used for parallel file systems that allow reading and writing back-end storage and uses multiple cloud storage .

However, since DEPSKY does not support the concept of master storage, there is a disadvantage that it can not guarantee the configuration of cloud storage that always maintains all resources.

In order to compare the present invention with the conventional DEPSKY, four cloud storages were used and 100 read and write operations were performed for each operation, and files of various sizes were used for each operation.

As shown in FIG. 7, the present invention and the prior art have performed the same operation, but the present invention shows superior performance.

That is, in the prior art, DEPSKY needs to access all connected storages in order to check the version information of each storage resource at the time of executing the read and write operations, and thus requires an overhead time required .

However, according to an embodiment of the present invention, by designating the most available storage among the storages storing resources including all the latest information as master storage, it is possible to easily and quickly access the latest version of the resources through the master storage can do.

Embodiments of the present invention include computer readable media including program instructions for performing various computer implemented operations. The computer-readable medium may include program instructions, local data files, local data structures, etc., alone or in combination. The media may be those specially designed and constructed for the present invention or may be those known to those skilled in the computer software. Examples of computer-readable media include magnetic media such as hard disks, floppy disks and magnetic tape, optical recording media such as CD-ROMs and DVDs, magneto-optical media such as floppy disks, and ROMs, And hardware devices specifically configured to store and execute the same program instructions. Examples of program instructions include machine language code such as those produced by a compiler, as well as high-level language code that can be executed by a computer using an interpreter or the like.

While the present invention has been described in connection with what is presently considered to be practical exemplary embodiments, it is to be understood that the invention is not limited to the disclosed embodiments. Therefore, the scope of the present invention should not be limited to the described embodiments, but should be determined by the scope of the appended claims and equivalents thereof.

While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it is to be understood that the invention is not limited to the disclosed exemplary embodiments, but, on the contrary, Modification is possible. Accordingly, the spirit of the present invention should be understood only in accordance with the following claims, and all equivalents or equivalent variations thereof are included in the scope of the present invention.

100: Atomic operation and storage replication device
110, 111, 112: user
115: Private Workshop
120: User group
125: Group workshop
135: open workshop
201, 202, 203: Queue
205, 206, 207: storage connector
211, 212, 213: Cloud manager
215, 216, 217: Cloud storage
220: Database Manager
225: Database
230: Storage Connector Manager

Claims (16)

A first step in which the cloud manager performs storage primitive operations (SPO) for processing resources of the cloud storage;
A second step of a database manager performing metadata primitive operations (MPO) for processing metadata of the resource stored in the database; And
Wherein the cloud manager returns the cloud storage to a state prior to execution of the storage primitive operations if the primitive operations of the storage primitive operations and / or the metadata primitive operations are not performed, A third step of returning the metadata of the metadata to the state before execution of the metadata primitive operations;
And a storage replication method for collaborative middleware based on cloud storage. The method according to claim 1,
In the first step,
Wherein the cloud manager sequentially executes operations included in the storage primitive operations,
The second step comprises:
Wherein the database manager sequentially executes the operations included in the meta data primitive operations, and the atomic operation and storage replication method of the collaboration middleware based on the cloud storage. The method according to claim 1,
In the third step,
The database manager performs a commit command when all the primitive operations of the metadata primitive operations are executed and performs a rollback command if at least one primitive operation of the metadata primitive operations is not executed Atomic computing and storage replication methods for collaborative middleware based on cloud storage. The method according to claim 1,
Wherein the storage primitive operation and the metadata primitive operation are performed in a non-
An atomic operation and storage cloning method of collaborative middleware based on cloud storage, which is data creation (create), read (read), update (update) and delete (delete) operations. The method according to claim 1,
In the first step,
A first step of the cloud manager including a primitive operation in a queue in a primitive operation queue of each of a plurality of storages in a requested order;
A first step of each of the storages executing an operation according to a sequence of primitive operations included in the queue; And
A first step of the cloud manager designating one of the storages in which the primitive operation of the queue is executed as a master storage;
And a storage replication method for collaborative middleware based on cloud storage. The method of claim 5,
In the first step,
The method comprising: (1-4) the cloud manager not removing the primitive operation from the queue if the primitive operation included in the queue is not executed in each of the storages; And
(1-5), when the storage is restored to a normal state, executing a primitive operation that is included in the queue but is not executed;
And a storage replication method for collaborative middleware based on cloud storage. The method of claim 6,
Before the step 1-1,
Displaying a green indicating that each of the plurality of storages is in a standby state;
Further comprising:
In the step 1-2,
Wherein the storage status display unit displays a yellow color indicating that each storage is executing a primitive operation included in the queue,
In the step 1-4,
Wherein the storage status display unit displays a red color indicating that a primitive operation included in the queue has not been executed in each of the storages,
In the step 1-5,
The storage status display unit displays a blue color indicating that each storage is restored to a normal status,
In the first step,
(1-6) when the storage state indicator indicates black when the queues are full or when the respective arrays are not available because the primitive operations included in the queues are not executed in the respective storages;
And a storage replication method for collaborative middleware based on cloud storage. The method of claim 6,
In the step 1-3,
The atomic operation and the storage replication of the collaborative middleware based on the cloud storage in which the cloud manager designates the storage other than the designated master storage as the sub storage among the storages in which all the primitive operations of the queue are executed. Cloud storage to store resources;
A cloud manager for performing storage primitive operations (SPOs) for processing resources of the cloud storage;
A database for storing metadata of the resources; And
A database manager for performing metadata primitive operations (MPO) for processing metadata of the resources stored in the database;
Lt; / RTI >
If the raw operation of at least one of the storage raw operations and the metadata raw operations is not performed, the cloud manager returns the cloud storage to a state prior to execution of the storage raw operations, Wherein the meta data of the meta data is returned to a state prior to the execution of the meta data primitive operations. The method of claim 9,
The cloud manager includes:
Sequentially executing operations included in the storage primitive operations,
Wherein the database manager comprises:
And atomic operation and storage replication of collaborative middleware based on cloud storage that sequentially executes operations included in the metadata primitive operations. The method of claim 9,
Wherein the database manager comprises:
Based on cloud storage that performs a commit command when all of the primitive operations of the metadata primitive operations are executed and performs a rollback command if at least one primitive operation of the metadata primitive operations is not performed, The atomic operation and storage replication device of collaborative middleware. The method of claim 9,
Wherein the storage primitive operation and the metadata primitive operation are performed in a non-
An atomic operation and storage cloning device for collaborative middleware based on cloud storage, which is the creation, read, update and delete operation of data. The method of claim 9,
The cloud manager includes:
The method comprising: storing primitive operations in queues of primitive operations of a plurality of storages in a requested order; controlling each of the storages to execute operations according to a sequence of primitive operations included in the queues; And an atomic operation and storage replica of the collaborative middleware based on the cloud storage designating one of the storages in which the raw operation of the queue is executed as the master storage. 14. The method of claim 13,
The cloud manager includes:
If the raw operation contained in the queue is not executed in each of the storages, the raw operation is not removed from the queue, and when each storage is restored to a normal state, a raw operation that is contained in the queue but is not executed is executed The atomic operation and storage replication device of collaborative middleware based on cloud storage. 15. The method of claim 14,
The storage status display unit displays,
Wherein each of the plurality of storages displays green when each of the plurality of storages is in a standby state and displays yellow when each of the storages is executing a primitive operation included in the queue, Displays red when the primitive operation is not performed, displays blue when the storage is restored to a normal state, and displays primitive operations such as blue Wherein the storage status display unit displays black when the storage is unavailable, wherein the storage status indicator displays black. 15. The method of claim 14,
The cloud manager includes:
And an atomic operation and storage replica of the collaborative middleware based on cloud storage that designates, among the storages in which all the primitive operations of the queue are executed, the storage other than the designated master storage as a sub storage.

Images