File classification method, device and equipment of automation system and storage medium

Abstract

The application relates to the technical field of data storage, and discloses a file grading method, device and equipment of an automation system and a storage medium, the method comprising the following steps: creating an authentication user group in a cluster and creating authentication users based on the authentication user group; keeping an active connection between the cluster and a client; synchronizing the authentication user group and the authentication users to the client; creating a tenant; creating an object scene user associated with the authentication users and the tenant; creating a bucket belonging to the tenant through a related key of the object scene user; setting a network file system share for the bucket, and mounting the network file system share on the client; obtaining, through the network file system share on the client, a latest target time of an object uploaded into the bucket through an object storage protocol, the target time comprising a creation time, a content modification time and / or a permission change time; and grading the object based on the latest target time. The application realizes automatic acquisition of metadata required for file grading in a fusion scene.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of data storage, and particularly relates to a file grading method, device and equipment of an automation system and a storage medium. BACKGROUND

[0002] Mass storage automation operation has been widely applied in the fields of IT enterprises, cloud computing, big data and virtualization.

[0003] Meanwhile, the requirements of these fields on the fusion of file scenarios and object scenarios are increasingly high. The automation system cannot support file grading metadata processing in the fusion scenarios, and cannot meet the user requirements. The automation system also needs to be able to process file grading metadata in the fusion scenarios. SUMMARY

[0004] Therefore, the present application provides a file grading method, device and equipment of an automation system and a storage medium to solve the problem that the automation system cannot process file grading metadata in the fusion scenarios.

[0005] In a first aspect, the present application provides a file grading method of an automation system, which comprises the following steps.

[0006] The cluster creates an authentication user group and creates an authentication user based on the authentication user group;

[0007] The cluster maintains an active connection with the client;

[0008] The authentication user group and the authentication user are synchronized to the client;

[0009] A tenant is created;

[0010] An object scenario user associated with the authentication user and the tenant is created;

[0011] A bucket belonging to the tenant is created through a related key of the object scenario user, and the bucket is used for the client to upload objects;

[0012] A network file system share is set for the bucket, and the network file system share is mounted on the client;

[0013] The client obtains the latest target time of the objects uploaded to the bucket through an object storage protocol through the network file system share, and the target time comprises a creation time, a content modification time and / or a permission change time;

[0014] The objects are graded based on the latest target time.

[0015] The application can be applied to an automatic platform of a mass storage distributed system. In the application, the storage cluster is kept in active connection with the client, so that the client can obtain the creation time, content modification time and / or permission change time of the object uploaded into the bucket through the object storage protocol through the NFS share, thereby realizing automatic acquisition of the metadata (i.e. the creation time, content modification time and permission change time) required for file classification in the fusion scenario, and further realizing file classification in the fusion scenario. Moreover, the acquisition of the metadata required for file classification in the fusion scenario in the application does not need to limit the model and operating system of each storage device in the distributed storage system, that is, it can be compatible with multiple models / operating systems. The application improves the robustness, ease of use, multi-model / operating system compatibility and functionality of the distributed system, and improves the competitiveness of the mass storage automatic platform and the work efficiency of data processing.

[0016] In an optional embodiment, the method further comprises:

[0017] acquiring, by the client through the NFS share, the latest target time of the target object uploaded into the bucket through the object storage protocol;

[0018] performing a first operation on the target object, the first operation comprising a content modification operation and / or a permission modification operation;

[0019] acquiring the target time of the target object after each operation;

[0020] comparing the size relationship between the target time before and after each operation, and determining whether to pass the verification according to the size relationship between the target time before and after each operation.

[0021] In an optional embodiment, performing the first operation on the target object comprises:

[0022] performing a content modification operation on the target object;

[0023] performing a permission modification operation on the target object after the content modification operation.

[0024] In an optional embodiment, each target time comprises a date time and a time minute second time;

[0025] comparing the size relationship between the target time before and after each operation, and determining whether to pass the verification according to the size relationship between the target time before and after each operation, comprises:

[0026] determining whether the date time of the creation time after the content modification operation is equal to the date time of the creation time after the content modification operation;

[0027] If equal, then judge whether the time of minute and second of the creation time after the content modification operation on the target object is equal to the time of minute and second of the creation time after the content modification operation.

[0028] If equal, then judge whether the date time of the content modification time after the content modification operation on the target object is equal to the date time of the content modification time after the content modification operation.

[0029] If equal, then judge whether the time of minute and second of the content modification time after the content modification operation on the target object is greater than the time of minute and second of the content modification time after the content modification operation.

[0030] If greater, then judge whether the date time of the permission change time after the content modification operation on the target object is equal to the date time of the permission change time after the content modification operation.

[0031] If equal, then judge whether the time of minute and second of the permission change time after the content modification operation on the target object is greater than the time of minute and second of the permission change time after the content modification operation.

[0032] If greater, then continue to judge the size relationship between the target time before and after the permission modification operation.

[0033] In an optional embodiment, before the client obtains the latest target time of the object uploaded into the bucket through the object storage protocol through the network file system share, further comprising:

[0034] Determine whether the size file separation switch is closed.

[0035] In an optional embodiment, before the client obtains the latest target time of the object uploaded into the bucket through the object storage protocol through the network file system share, further comprising:

[0036] Determine whether the cluster all node NFS service state is in a normal state.

[0037] In an optional embodiment, before the client obtains the latest target time of the object uploaded into the bucket through the object storage protocol through the network file system share, further comprising:

[0038] Determine whether the cluster exists a network virtual IP.

[0039] In a second aspect, the application provides a file grading device of an automatic system, which comprises:

[0040] An authentication user module is configured to create an authentication user group in the cluster and create an authentication user based on the authentication user group.

[0041] A connection module is configured to maintain an active connection between the cluster and the client;

[0042] A synchronization module is configured to synchronize the authentication user group and the authentication user to the client;

[0043] A tenant creation module is configured to create a tenant;

[0044] An object-scene user creation module is configured to create an object-scene user associated with the authentication user and the tenant;

[0045] A bucket creation module is configured to create a bucket belonging to the tenant through a related key of the object-scene user, and the bucket is used for the client to upload an object;

[0046] A sharing module is configured to set a network file system sharing for the bucket, and mount the network file system sharing on the client;

[0047] A time acquisition module is configured to acquire, on the client, a latest target time of an object uploaded into the bucket through an object storage protocol via the network file system sharing, and the target time includes a creation time, a content modification time and / or a permission change time;

[0048] A file grading module is configured to grade the object based on the latest target time.

[0049] In a third aspect, the present application provides a computer device, comprising a memory and a processor, the memory and the processor are communicatively connected with each other, the memory stores computer instructions, and the processor executes the computer instructions to perform the file grading method of the automatic system according to the first aspect or any one of the corresponding embodiments thereof.

[0050] In a fourth aspect, the present application provides a computer readable storage medium, which stores computer instructions, and the computer instructions are used to make a computer execute the file grading method of the automatic system according to the first aspect or any one of the corresponding embodiments thereof. BRIEF DESCRIPTION OF DRAWINGS

[0051] In order to more clearly illustrate the specific embodiments of the present application or the technical solutions in the prior art, the drawings needed in the specific embodiments or prior art description will be briefly introduced below. Obviously, the drawings in the following description are some embodiments of the present application, and those skilled in the art can obtain other drawings according to these drawings without creative labor.

[0052] Figure 1 is a flowchart of a file grading method of an automatic system according to an embodiment of the present application;

[0053] Figure 2is a flowchart of cluster virtual IP verification according to an embodiment of the present application;

[0054] Figure 3 is a flowchart of NFS service state verification according to an embodiment of the present application;

[0055] Figure 4 is a flowchart of large file separation switch verification according to an embodiment of the present application;

[0056] Figure 5 is a flowchart of authentication user group and authentication user creation according to an embodiment of the present application;

[0057] Figure 6 is a flowchart of object creation time verification according to an embodiment of the present application;

[0058] Figure 7 is a flowchart of object content modification time verification according to an embodiment of the present application;

[0059] Figure 8 is a flowchart of object permission change time verification according to an embodiment of the present application;

[0060] Figure 9 is a structural block diagram of a file classification device of an automation system according to an embodiment of the present application;

[0061] Figure 10 is a hardware structure diagram of a computer device according to an embodiment of the present application. DETAILED DESCRIPTION

[0062] In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are some but not all of the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative work fall within the protection scope of the present application.

[0063] With the development of the Internet industry, people's demand for storage is growing, and centralized storage has become a bottleneck of data center systems, which cannot meet the needs of large-scale storage applications. Benefiting from the development and maturity of server technology, distributed storage with standard servers has emerged, and distributed storage has been widely applied.

[0064] Distributed storage is to store data on multiple storage servers, and to construct a virtual storage device from these scattered storage resources. In fact, data is scattered and stored in every corner of the enterprise. The advantage of distributed storage is to improve the reliability, availability and access efficiency of the system, and it is also easy to expand. The continuous and stable operation of the storage system is the prerequisite for the IT infrastructure to guarantee high-availability services, and its importance is self-evident. Distributed storage systems need to be deployed on many machines, involving dozens of hardware modules, operating systems, software packages, various firmware, networks, file systems and many other aspects, and good operation and maintenance is needed to ensure smooth operation. Some large cloud computing companies maintain a large maintenance team to ensure business continuity, but the cost of manpower is high. With the rise of artificial intelligence (AI), the storage industry is trying to rely on artificial intelligence for automated operation and maintenance, which can reduce the dependence on maintenance personnel.

[0065] However, in the related art, in the fusion scene of the file scene and the object scene, the metadata required for file classification needs to be obtained manually, and the automatic system has not yet realized the automatic acquisition of the metadata required for file classification. Therefore, the embodiment of the present application provides a file classification method of an automatic system, which keeps the storage cluster and the client in active connection, so that the client can obtain the creation time, content modification time and / or permission change time of the object uploaded to the bucket through the object storage protocol through the NFS share, thereby realizing the automatic acquisition of the metadata (i.e. creation time, content modification time, permission change time) required for file classification in the fusion scene, and further realizing the file classification in the fusion scene. Moreover, the acquisition of the metadata required for file classification in the fusion scene in the embodiment of the present application does not need to limit the model of each storage device in the distributed storage system and the operating system, that is, it can be compatible with multiple models / operating systems. The embodiment of the present application improves the robustness, ease of use, multi-model / operating system compatibility and functionality of the distributed system, and improves the competitiveness of the mass storage automation platform and the work efficiency of data processing.

[0066] According to the embodiment of the present application, a file classification method of an automatic system is provided. It should be noted that the steps shown in the flowchart of the drawings can be executed in a computer system such as a set of computer executable instructions, and although the logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in a different order from here.

[0067] In the present embodiment, a file classification method of an automatic system is provided, which can be used in a computer device, Figure 1 The flowchart of the file classification method of the automatic system according to the embodiment of the present application is shown in Figure 1 The flowchart includes the following steps:

[0068] Step S101, create an authentication user group $AUTH_GROUP in the cluster and create an authentication user $AUTH_USER based on the authentication user group $AUTH_GROUP; specifically, the authentication user group $AUTH_GROUP and the authentication user $AUTH_USER can be created by

[0069] Step S102, synchronize the authentication user group $AUTH_GROUP and the authentication user $AUTH_USER to the client.

[0070] The embodiment is applicable to a distributed storage system, which includes multiple storage devices to form a storage cluster, and storage spaces of the storage devices are aggregated into a storage pool capable of providing an application server with a unified access interface and management interface. An application can transparently access and utilize disks on all the storage devices through the access interface, so that the performance of the storage devices and the utilization of the disks can be fully exerted.

[0071] Step S102, start a keep-alive connection between the cluster and the client.

[0072] In the subsequent steps, the cluster and the client always maintain a keep-alive connection. Specifically, the authentication user $AUTH_USER can be used to log in to the client to refresh the connection $CLIENT_SSH, and this step can be repeatedly executed at a short interval to maintain the keep-alive connection between the cluster and the client.

[0073] Step S103, synchronize the authentication user group and the authentication user to the client.

[0074] Step S104, create a tenant $TENANT_USER.

[0075] This step can be executed in advance, for example, before the authentication user group and the authentication user are created. Specifically, the tenant $TENANT_USER can be created by create_tenant_name().

[0076] Step S105, create an object scenario user $S3_USER associated with the authentication user and the tenant.

[0077] Specifically, the S3 user $S3_USER can be created by create_user_s3_nas_mix($S3_USER, $TENANT_USER, $AUTH_USER).

[0078] At step S106, a bucket $BUCKET belonging to the tenant is created by the relevant key of the object scene user, and the bucket is used for the client to upload the object $OBJECT; that is, after the creation of the bucket $BUCKET, the client can upload the object $OBJECT to the bucket $BUCKET.

[0079] For example, the bucket $BUCKET can be created through the S3 protocol. Specifically, the bucket $BUCKET belonging to the $TENANT_USER can be created through the access key $ACCESS_KEY and the key $SECRET_KEY of the $S3_USER using s3_create_bucket() combined with the S3 protocol, and the object file $OBJECT is uploaded to the $BUCKET.

[0080] At step S107, the network file system (NFS) share $NFS_SHARE is set for the bucket $BUCKET, and the NFS share $NFS_SHARE is mounted on the client.

[0081] Specifically, the NFS share can be set through set_nfs_share($BUCKET). The NFS share is mounted on the client through nfs_mount_cmd($BUCKET, $CLIENT_NFS_DIR / $OBJECT).

[0082] At step S108, the latest target time of the object uploaded to the bucket through the object storage protocol is obtained through the NFS share on the client, and the target time includes the creation time (atime), the content modification time (btime or mtime), and / or the permission change time (ctime).

[0083] Specifically, the object storage protocol can be the S3 protocol.

[0084] At step S109, the object is classified based on the latest target time. Specifically, the classification here can be divided into two levels, one level is hot data, and the other level is cold data. The hot data is stored in a solid state disk (SSD), and the cold data is stored in a hard disk drive (HDD).

[0085] The embodiment can be applied to an automatic platform of a mass storage distributed system. In the embodiment, the storage cluster is kept in active connection with the client, so that the client can obtain the creation time, content modification time and / or permission change time of the object uploaded into the bucket through the object storage protocol through the NFS share, thereby realizing automatic acquisition of the metadata (i.e., the creation time, content modification time and permission change time) required for file classification in the fusion scenario, and further realizing file classification in the fusion scenario. Moreover, in the embodiment, the acquisition of the metadata required for file classification in the fusion scenario does not need to limit the model and operating system of each storage device in the distributed storage system, that is, it can be compatible with multiple models / operating systems. The embodiment improves the robustness, ease of use, multi-model / operating system compatibility and functionality of the distributed system, and improves the competitiveness of the mass storage automatic platform and the work efficiency of data processing.

[0086] In some optional embodiments, the method further comprises:

[0087] The client obtains the latest target time of the target object uploaded into the bucket through the object storage protocol through the NFS share; wherein the target object is part or all of the objects uploaded into the bucket by the client through the object storage protocol. That is, in the embodiment, time verification can be performed on all objects uploaded into the bucket, or time verification can be performed on part of the objects uploaded into the bucket through sampling.

[0088] The target object is subjected to a first operation, and the first operation includes a content modification operation and / or a permission modification operation;

[0089] That is, the target object can be subjected to only a content modification operation, can be subjected to only a permission modification operation, can be subjected to a content modification operation first and then a permission modification operation, or can be subjected to a permission modification operation first and then a content modification operation;

[0090] The target time of the target object after each operation is obtained;

[0091] Specifically, the target time can be obtained in time after each operation;

[0092] The size relationship between the target time before and after each operation is compared, and it is determined whether to pass the verification according to the size relationship between the target time before and after each operation.

[0093] Specifically, when comparing the sizes between the target times, the creation time before the operation is compared with the creation time after the operation, the content modification time before the operation is compared with the content modification time after the operation, and the permission change time before the operation is compared with the permission change time after the operation. Of course, when verifying the time of a certain object, only the creation time of the object can be verified, only the content modification time of the object can be verified, only the permission change time of the object can be verified, the creation time and the content modification time of the object can be verified, the content modification time and the permission change time of the object can be verified, or the creation time, the content modification time, and the permission change time of the object can be verified.

[0094] If the size relationship between the target times before and after the operation meets the preset condition, it is determined that the verification is passed, otherwise the verification is not passed.

[0095] If the size relationship between the target times before and after the operation does not meet the preset condition, the next operation is not needed.

[0096] In the embodiment, it can be ensured that the target time can be updated in real time according to the actual situation, and since the target time is the basis for file classification, the accuracy of file classification can be improved. Specifically, if the size relationship between the target times before and after the operation cannot pass the verification, it means that the update of the target time has a problem, and therefore the file classification cannot be based on the latest target time.

[0097] In some optional specific embodiments, before the client obtains the latest target time of the object uploaded into the bucket through the object storage protocol through the network file system share, the method further includes:

[0098] Determining whether the large file separation switch is closed.

[0099] In some optional specific embodiments, before the client obtains the latest target time of the object uploaded into the bucket through the object storage protocol through the network file system share, the method further includes:

[0100] Determining whether the NFS service state of all nodes of the cluster is in a normal state.

[0101] In some optional specific embodiments, before the client obtains the latest target time of the object uploaded into the bucket through the object storage protocol through the network file system share, the method further includes:

[0102] Determining whether the cluster has a network virtual IP. The network virtual IP can be a gigabit virtual IP.

[0103] The embodiment provides a file classification method of an automatic system, which can be used for a computer device and the like, and the method includes the following steps:

[0104] Step S201, check whether the cluster virtual IP is configured.

[0105] Specifically, the cluster's gigabit virtual IP can be obtained by get_ctdb_vir_ip_list(), and it is ensured that the cluster has a gigabit network virtual IP to ensure the network connection between the cluster and the client. Please refer to Figure 2 The virtual IP check module can obtain the cluster's gigabit virtual IP ($CTDB_VIR_IP) by get_ctdb_vir_ip_list(). If it is obtained, the program returns 1, normal, and if it is not obtained, the program returns 0 and reports an error.

[0106] Step S202, check whether the NFS service status on each node is normal.

[0107] Specifically, please refer to Figure 3 The NFS service status can be obtained by get_nfs_service_status(). If the cluster has a node with abnormal NFS service status, the program returns 0 and reports an error and exits.

[0108] Step S203, determine whether the size file split switch conflicting with the file tiering feature is closed.

[0109] Specifically, please refer to Figure 4 The file size file split switch can be obtained by get_big_small_file_filetier_status(). If it is not closed, the program returns 0 and reports an error and exits.

[0110] Step S204, create the authentication user group $AUTH_GROUP and the authentication user $AUTH_USER in the cluster, and synchronize the authentication user group $AUTH_GROUP and the authentication user $AUTH_USER to the client.

[0111] Step S205, enable the keep-alive connection between the cluster and the client.

[0112] Step S206, create the tenant $TENANT_USER.

[0113] Step S207, create the $S3_USER associated with the authentication user $AUTH_USER and the tenant $TENANT_USER.

[0114] Step S208, create the bucket $BUCKET using the S3 protocol.

[0115] Step S209, the client uploads the object $OBJECT to the bucket $BUCEKT.

[0116] Step S210, set NFS share $NFS_SHARE for the bucket $BUCKET, and mount $NFS_SHARE on the client.

[0117] Step S211, obtain the target time of the object, the target time including the creation time, the content modification time and / or the permission change time.

[0118] Step S212, perform the first operation on the target object, the first operation including the content modification operation and / or the permission modification operation.

[0119] Step S213, obtain the target time of the target object after each operation.

[0120] Step S214, compare the size relationship between the target time before and after each operation, and determine whether to pass the verification according to the size relationship between the target time before and after each operation.

[0121] Step S215, if the verification passes, perform the classification on the objects in the bucket based on the target time.

[0122] A file classification method of an automated system is provided in the embodiment, which can be used in a computer device and the like, and the method comprises the following steps:

[0123] Step S301, check whether the cluster virtual IP is configured.

[0124] Step S302, check whether the NFS service state is normal on each node.

[0125] Step S303, determine whether the size file separation switch conflicting with the file classification optimization feature is closed.

[0126] Step S304, create the authentication user group $AUTH_GROUP and the authentication user $AUTH_USER in the cluster, and synchronize the authentication user group $AUTH_GROUP and the authentication user $AUTH_USER to the client.

[0127] Step S305, start the keep-alive connection between the cluster and the client.

[0128] Step S306, create the tenant $TENANT_USER.

[0129] Step S307, create $S3_USER associated with the authentication user $AUTH_USER and the tenant $TENANT_USER.

[0130] Step S308, create the bucket $BUCKET using the S3 protocol.

[0131] Step S309, uploading the object $OBJECT to the bucket $BUCKET.

[0132] Step S310, setting the NFS share $NFS_SHARE for the bucket $BUCKET, and mounting the $NFS_SHARE on the client.

[0133] Step S311, obtaining the date time $CREATE_FILE_DATA_A_1 and the hour minute second time $CREATE_FILE_TIME_A_1 of the creation time (atime) of the object $OBJECT uploaded to the bucket $BUCKET through the S3 protocol through the Network File System (NFS) share, obtaining the date time $CREATE_FILE_DATA_B_1 and the hour minute second time $CREATE_FILE_TIME_B_1 of the content modification time (btime) of the object $OBJECT, and obtaining the date time $CREATE_FILE_DATA_C_1 and the hour minute second time $CREATE_FILE_TIME_C_1 of the permission change time (ctime) of the object $OBJECT.

[0134] Step S312, appending writing to the $OBJECT file through the NFS share.

[0135] Specifically, the $OBJECT object file can be appended and written through echo_cmd($CLIENT_SSH, $CLIENT_NFS_DIR / $OBJECT), and the $OBJECT content is changed.

[0136] Step S313, obtaining the date time $CREATE_FILE_DATA_A_2 and the hour minute second time $CREATE_FILE_TIME_A_2 of the creation time (atime) of the object $OBJECT file.

[0137] Step S314, checking whether $CREATE_FILE_DATA_A_1 is equal to $CREATE_FILE_DATA_A_2, and if not, the program exits with an error. Here, if $CREATE_FILE_DATA_A_2 crosses a date, the actual number of days crossed is added to $CREATE_FILE_DATA_A_1 in advance, and the date times involved in the following are the same, and will not be repeated.

[0138] Step S315, checking whether $CREATE_FILE_TIME_A_1 is equal to $CREATE_FILE_TIME_A_2, and if not, the program exits with an error.

[0139] Step S316, get the date time $CREATE_FILE_DATA_B_2 and the time minute second time $CREATE_FILE_TIME_B_2 of the content modification time (btime) of the object $OBJECT.

[0140] Step S317, check whether $CREATE_FILE_DATA_B_1 is equal to $CREATE_FILE_DATA_B_2, if not, the program exits with an error.

[0141] Step S318, check whether $CREATE_FILE_TIME_B_2 is greater than $CREATE_FILE_TIME_B_1, if not, the program exits with an error.

[0142] Step S319, get the date time $CREATE_FILE_DATA_C_2 and the time minute second time $CREATE_FILE_TIME_C_2 of the permission change time (ctime) of the object $OBJECT.

[0143] Step S320, check whether the object $CREATE_FILE_DATA_C_1 is equal to $CREATE_FILE_DATA_C_2, if not, the program exits with an error.

[0144] Step S321, check whether $CREATE_FILE_TIME_C_2 is greater than $CREATE_FILE_TIME_C_1, if not, the program exits with an error.

[0145] Step S322, perform the permission modification operation on the object $OBJECT file.

[0146] Step S323, get the date time $CREATE_FILE_DATA_B_3 and the time minute second time $CREATE_FILE_TIME_B_3 of the content modification time (btime) of the object $OBJECT.

[0147] Step S324, check whether $CREATE_FILE_DATA_B_3 is equal to $CREATE_FILE_DATA_B_2, if not, the program exits with an error.

[0148] Step S325, check whether $CREATE_FILE_TIME_B_3 is equal to $CREATE_FILE_TIME_B_2, if not, the program exits with an error.

[0149] Step S326, get the date and time $CREATE_FILE_DATA_C_3 and the time $CREATE_FILE_TIME_C_3 of the ctime of the $OBJECT.

[0150] Step S327, check whether $CREATE_FILE_DATA_C_3 is equal to $CREATE_FILE_DATA_C_2, if not, the program exits with an error.

[0151] Step S328, check whether $CREATE_FILE_TIME_C_3 is greater than $CREATE_FILE_TIME_C_2, if not, the program exits with an error.

[0152] Step S329, if the above checks are passed, the objects in the bucket are classified based on the target time.

[0153] A file classification method of an automated system is provided in the embodiment, which can be used in computer devices and the like, and the method comprises the following steps:

[0154] Step S401, check whether the cluster virtual IP is configured.

[0155] Step S402, check whether the NFS service state is normal on each node.

[0156] Step S403, determine whether the size file separation switch conflicting with the file classification optimization feature is closed.

[0157] Step S404, create a tenant $TENANT_USER.

[0158] Step S405, create an authentication user group $AUTH_GROUP and an authentication user $AUTH_USER in the cluster and the associated client in synchronization.

[0159] Step S406, enable the keep-alive connection between the cluster and the client.

[0160] Step S407, create an object scenario user $S3_USER associated with the authentication user and the tenant.

[0161] Step S408, create a bucket $BUCKET belonging to the tenant through the related key of the object scenario user, and the bucket is used for the client to upload an object $OBJECT.

[0162] Step S409, set an NFS share $NFS_SHARE for the bucket $BUCKET, and mount the $NFS_SHARE on the client.

[0163] Step S410, in the NFS shared directory of the client, the date and time $CREATE_DATA_A_1 of the creation time (atime) of the $OBJECT object file in the bucket $BUCKET is obtained by get_file_data_time($CLIENT_SSH, $CLIENT_NFS_DIR / $OBJECT, "Access"), the minute and second time $CREATE_TIME_A_1 of the creation time (atime) of the $OBJECT object file is obtained by get_file_time_min_sec($CLIENT_SSH, $CLIENT_NFS_DIR / $OBJECT, "Access"); the date and time $CREATE_DATA_B_1 of the content modification time (btime) of the $OBJECT object file in the bucket $BUCKET is obtained by get_file_data_time($CLIENT_SSH, $CLIENT_NFS_DIR / $OBJECT, "Modify"), the minute and second time $CREATE_TIME_B_1 of the content modification time (btime) of the $OBJECT object file is obtained by get_file_time_min_sec($CLIENT_SSH, $CLIENT_NFS_DIR / $OBJECT, "Modify"); the date and time $CREATE_DATA_C_1 of the permission change time (ctime) of the $OBJECT object file in the bucket $BUCKET is obtained by get_file_data_time($CLIENT_SSH, $CLIENT_NFS_DIR / $OBJECT, "Change"), the minute and second time $CREATE_TIME_C_1 of the permission change time (ctime) of the $OBJECT object file is obtained by get_file_time_min_sec($CLIENT_SSH, $CLIENT_NFS_DIR / $OBJECT, "Change").

[0164] Step S411, the $OBJECT object file is written by echo_cmd($CLIENT_SSH, $CLIENT_NFS_DIR / $OBJECT) to change the $OBJECT content.

[0165] Step S412, get the date time $CREATE_DATA_A_2 of the creation time (atime) of the $OBJECT object file in the bucket $BUCKET through get_file_data_time($CLIENT_SSH, $CLIENT_NFS_DIR / $OBJECT, "Access"), and get the minute-second time $CREATE_TIME_A_2 of the creation time (atime) of the $OBJECT object file through get_file_time_min_sec($CLIENT_SSH, $CLIENT_NFS_DIR / $OBJECT, "Access"). Get the date time $CREATE_DATA_B_2 of the content modification time (btime) of the $OBJECT object file in the bucket $BUCKET through get_file_data_time($CLIENT_SSH, $CLIENT_NFS_DIR / $OBJECT, "Modify"), and get the minute-second time $CREATE_TIME_B_2 of the content modification time (btime) of the $OBJECT object file through get_file_time_min_sec($CLIENT_SSH, $CLIENT_NFS_DIR / $OBJECT, "Modify"). Get the date time $CREATE_DATA_C_2 of the permission change time (ctime) of the $OBJECT object file in the bucket $BUCKET through get_file_data_time($CLIENT_SSH, $CLIENT_NFS_DIR / $OBJECT, "Change"), and get the minute-second time $CREATE_TIME_C_2 of the permission change time (ctime) of the $OBJECT object file through get_file_time_min_sec($CLIENT_SSH, $CLIENT_NFS_DIR / $OBJECT, "Change");

[0166] Step S413, automatically check whether $CREATE_DATA_A_2 is equal to $CREATE_DATA_A_1, if not, the program returns 0 and exits with error. Automatically check whether $CREATE_TIME_A_2 is equal to $CREATE_TIME_A_1, if not, the program returns 0 and exits with error. Automatically check whether $CREATE_DATA_B_2 is equal to $CREATE_DATA_B_1, if not, the program returns 0 and exits with error. Automatically check whether $CREATE_TIME_B_2 is greater than $CREATE_TIME_B_1, if not, the program returns 0 and exits with error. Automatically check whether $CREATE_DATA_C_2 is equal to $CREATE_DATA_C_1, if not, the program returns 0 and exits with error. Automatically check whether $CREATE_TIME_C_2 is greater than $CREATE_TIME_C_1, if not, the program returns 0 and exits with error.

[0167] Step S414, modify the $OBJECT object file permission by chmod_cmd($CLIENT_SSH, $CLIENT_NFS_DIR / $OBJECT).

[0168] Step S415, get the date time $CREATE_DATA_A_3 of the atime of the $OBJECT object file in the bucket $BUCKET through get_file_data_time($CLIENT_SSH, $CLIENT_NFS_DIR / $OBJECT, "Access"), and get the time minute second time $CREATE_TIME_A_3 of the atime of the $OBJECT object file through get_file_time_min_sec($CLIENT_SSH, $CLIENT_NFS_DIR / $OBJECT, "Access"). Get the date time $CREATE_DATA_B_3 of the btime of the $OBJECT object file in the bucket $BUCKET through get_file_data_time($CLIENT_SSH, $CLIENT_NFS_DIR / $OBJECT, "Modify"), and get the time minute second time $CREATE_TIME_B_3 of the btime of the $OBJECT object file through get_file_time_min_sec($CLIENT_SSH, $CLIENT_NFS_DIR / $OBJECT, "Modify"). Get the date time $CREATE_DATA_C_3 of the ctime of the $OBJECT object file in the bucket $BUCKET through get_file_data_time($CLIENT_SSH, $CLIENT_NFS_DIR / $OBJECT, "Change"), and get the time minute second time $CREATE_TIME_C_3 of the ctime of the $OBJECT object file through get_file_time_min_sec($CLIENT_SSH, $CLIENT_NFS_DIR / $OBJECT, "Change").

[0169] Step S416, automatically check whether $CREATE_DATA_A_3 is equal to $CREATE_DATA_A_2, if not, the program returns 0 and exits with error. Automatically check whether $CREATE_TIME_A_3 is equal to $CREATE_TIME_A_2, if not, the program returns 0 and exits with error. Automatically check whether $CREATE_DATA_B_2 is equal to $CREATE_DATA_B_3, if not, the program returns 0 and exits with error. Automatically check whether $CREATE_TIME_B_3 is equal to $CREATE_TIME_B_2, if not, the program returns 0 and exits with error. Automatically check whether $CREATE_DATA_C_3 is equal to $CREATE_DATA_C_2, if not, the program returns 0 and exits with error. Automatically check whether $CREATE_TIME_C_3 is greater than $CREATE_TIME_C_2, if not, the program returns 0 and exits with error.

[0170] Step S417, if the above verification is passed, file classification is performed on the objects uploaded into the bucket based on the target time.

[0171] In the embodiment, a file classification method of an automated system is provided, which can be used in a computer device and the like, and the method comprises the following steps.

[0172] Step S501, check whether the cluster virtual IP is configured.

[0173] Step S502, check whether the NFS service state is normal on each node.

[0174] Step S503, determine whether the size file separation switch conflicting with the file classification optimization feature is closed.

[0175] Step S504, create a tenant $TENANT_USER.

[0176] Step S505, create an authentication user group $AUTH_GROUP and an authentication user $AUTH_USER synchronously on the cluster and the associated client.

[0177] Step S506, enable the keep-alive connection on the cluster and the client.

[0178] The above steps S505 and S506 are shown as follows. Figure 5

[0179] Step S507, create an object scenario user $S3_USER associated with the authentication user and the tenant.

[0180] ​Step S508, create a bucket $BUCKET belonging to the tenant through the relevant key of the object scene user, and the bucket is used for the client to upload an object $OBJECT.

[0181] Step S509, set an NFS share $NFS_SHARE for the bucket $BUCKET, and mount the $NFS_SHARE on the client.

[0182] Step S509, in the NFS shared directory of the client, obtain the date and time $CREATE_DATA_A_1 of the atime of the $OBJECT object file in the bucket $BUCKET through get_file_data_time($CLIENT_SSH, $CLIENT_NFS_DIR / $OBJECT, “Access”), and obtain the time, minute and second time $CREATE_TIME_A_1 of the atime of the $OBJECT object file through get_file_time_min_sec($CLIENT_SSH, $CLIENT_NFS_DIR / $OBJECT, “Access”).

[0183] Step S510, perform an append write on the $OBJECT object file through echo_cmd($CLIENT_SSH, $CLIENT_NFS_DIR / $OBJECT), and change the content of the $OBJECT.

[0184] Step S511, obtain the date and time $CREATE_DATA_A_2 of the atime of the $OBJECT object file in the bucket $BUCKET through get_file_data_time($CLIENT_SSH, $CLIENT_NFS_DIR / $OBJECT, “Access”), and obtain the time, minute and second time $CREATE_TIME_A_2 of the atime of the $OBJECT object file through get_file_time_min_sec($CLIENT_SSH, $CLIENT_NFS_DIR / $OBJECT, “Access”).

[0185] Step S512, automatically check whether $CREATE_DATA_A_2 is equal to $CREATE_DATA_A_1, if not, the program returns 0 and exits with an error; then automatically check whether $CREATE_TIME_A_2 is equal to $CREATE_TIME_A_1, if not, the program returns 0 and exits with an error.

[0186] Step S513, modify the $OBJECT object file permission by chmod_cmd($CLIENT_SSH, $CLIENT_NFS_DIR / $OBJECT).

[0187] Step S514, get the atime date time $CREATE_DATA_A_3 of the $OBJECT object file in the bucket $BUCKET by get_file_data_time($CLIENT_SSH, $CLIENT_NFS_DIR / $OBJECT, "Access"), and get the atime minute-second time $CREATE_TIME_A_3 of the $OBJECT object file by get_file_time_min_sec($CLIENT_SSH, $CLIENT_NFS_DIR / $OBJECT, "Access").

[0188] Step S515, automatically check whether $CREATE_DATA_A_3 is equal to $CREATE_DATA_A_2, if not, the program returns 0 and exits with an error; then automatically check whether $CREATE_TIME_A_3 is equal to $CREATE_TIME_A_2, if not, the program returns 0 and exits with an error.

[0189] The above steps S509-S515, please refer to Figure 6 .

[0190] Step S516, in the NFS shared directory of the client, get the btime date time $CREATE_DATA_B_1 of the $OBJECT object file in the bucket $BUCKET by get_file_data_time($CLIENT_SSH, $CLIENT_NFS_DIR / $OBJECT, "Modify"), and get the btime minute-second time $CREATE_TIME_B_1 of the $OBJECT object file by get_file_time_min_sec($CLIENT_SSH, $CLIENT_NFS_DIR / $OBJECT, "Modify").

[0191] Step S517, change the $OBJECT content by appending writing to the $OBJECT object file by echo_cmd($CLIENT_SSH, $CLIENT_NFS_DIR / $OBJECT).

[0192] Step S518, get the date time $CREATE_DATA_B_2 of the btime of the $OBJECT object file in the bucket $BUCKET through get_file_data_time($CLIENT_SSH, $CLIENT_NFS_DIR / $OBJECT, "Modify"), and get the minute-second time $CREATE_TIME_B_2 of the btime of the $OBJECT object file through get_file_time_min_sec($CLIENT_SSH, $CLIENT_NFS_DIR / $OBJECT, "Modify").

[0193] Step S519, automatically check whether $CREATE_DATA_B_2 is equal to $CREATE_DATA_B_1, if not, the program returns 0 and exits with an error; then automatically check whether $CREATE_TIME_B_2 is greater than $CREATE_TIME_B_1, if not, the program returns 0 and exits with an error.

[0194] Step S520, modify the permission of the $OBJECT object file through chmod_cmd($CLIENT_SSH, $CLIENT_NFS_DIR / $OBJECT).

[0195] Step S521, get the date time $CREATE_DATA_B_3 of the btime of the $OBJECT object file in the bucket $BUCKET through get_file_data_time($CLIENT_SSH, $CLIENT_NFS_DIR / $OBJECT, "Modify"), and get the minute-second time $CREATE_TIME_B_3 of the btime of the $OBJECT object file through get_file_time_min_sec($CLIENT_SSH, $CLIENT_NFS_DIR / $OBJECT, "Modify").

[0196] Step S522, automatically check whether $CREATE_DATA_B_3 is equal to $CREATE_DATA_B_2, if not, the program returns 0 and exits with an error; then automatically check whether $CREATE_TIME_B_3 is equal to $CREATE_TIME_B_2, if not, the program returns 0 and exits with an error.

[0197] The above steps S516-S522, please refer to Figure 7 .

[0198] Step S523, get the ctime date time $CREATE_DATA_C_1 of the $OBJECT object file in the bucket $BUCKET through get_file_data_time($CLIENT_SSH, $CLIENT_NFS_DIR / $OBJECT, "Change"), and get the ctime minute-second time $CREATE_TIME_C_1 of the $OBJECT object file through get_file_time_min_sec($CLIENT_SSH, $CLIENT_NFS_DIR / $OBJECT, "Change").

[0199] Step S524, perform the append write on the $OBJECT object file through echo_cmd($CLIENT_SSH, $CLIENT_NFS_DIR / $OBJECT), and change the $OBJECT content.

[0200] Step S525, get the ctime date time $CREATE_DATA_C_2 of the $OBJECT object file in the bucket $BUCKET through get_file_data_time($CLIENT_SSH, $CLIENT_NFS_DIR / $OBJECT, "Change"), and get the ctime minute-second time $CREATE_TIME_C_2 of the $OBJECT object file through get_file_time_min_sec($CLIENT_SSH, $CLIENT_NFS_DIR / $OBJECT, "Change").

[0201] Step S526, automatically check whether $CREATE_DATA_C_2 is equal to $CREATE_DATA_C_1, if not, the program returns 0 and exits with an error; then automatically check whether $CREATE_TIME_C_2 is greater than $CREATE_TIME_C_1, if not, the program returns 0 and exits with an error.

[0202] Step S527, modify the permission of the $OBJECT object file through chmod_cmd($CLIENT_SSH, $CLIENT_NFS_DIR / $OBJECT).

[0203] Step S528, get the date and time of ctime of the $OBJECT object file in the bucket $BUCKET through get_file_data_time($CLIENT_SSH, $CLIENT_NFS_DIR / $OBJECT, "Change") to obtain $CREATE_DATA_C_3, and get the minute and second time of ctime of the $OBJECT object file through get_file_time_min_sec($CLIENT_SSH, $CLIENT_NFS_DIR / $OBJECT, "Change") to obtain $CREATE_TIME_C_3.

[0204] Step S529, automatically check whether $CREATE_DATA_C_3 is equal to $CREATE_DATA_C_2, if not, the program returns 0 and exits with an error; then automatically check whether $CREATE_TIME_C_3 is greater than $CREATE_TIME_C_2, if not, the program returns 0 and exits with an error.

[0205] The above steps S523-S529, please refer to Figure 8 .

[0206] Step S530, if the above verification is passed, the object uploaded into the bucket is file graded based on the target time.

[0207] In the embodiment, a file grading device of an automated system is also provided, which is used to implement the above embodiments and preferred embodiments, and has been described and will not be repeated. As used below, the term "module" can be a combination of software and / or hardware that implements a predetermined function. Although the device described in the following embodiments is preferably implemented in software, implementation of hardware, or a combination of software and hardware, is also possible and is contemplated.

[0208] The embodiment provides a file grading device of an automated system, as Figure 9 shown, comprising:

[0209] An authentication user module 901 is configured to create an authentication user group in the cluster and create an authentication user based on the authentication user group;

[0210] A connection module 902 is configured to maintain an active connection between the cluster and the client;

[0211] A synchronization module 903 is configured to synchronize the authentication user group and the authentication user to the client;

[0212] A tenant creation module 904 is configured to create a tenant;

[0213] The object scene user creation module 905 is configured to create an object scene user associated with the authenticated user and the tenant.

[0214] The bucket creation module 906 is configured to create a bucket belonging to the tenant by using the related key of the object scene user, and the bucket is used for the client to upload objects.

[0215] The sharing module 907 is configured to set a network file system share for the bucket, and mount the network file system share on the client.

[0216] The time acquisition module 908 is configured to acquire, on the client, a latest target time of an object uploaded into the bucket by using the object storage protocol through the network file system share, and the target time includes a creation time, a content modification time and / or a permission change time.

[0217] The file grading module 909 is configured to grade the object based on the latest target time.

[0218] In some optional embodiments, the apparatus further includes:

[0219] The first acquisition module is configured to acquire, on the client, a latest target time of a target object uploaded into the bucket by using the object storage protocol through the NFS share.

[0220] The operation module is configured to perform a first operation on the target object, and the first operation includes a content modification operation and / or a permission modification operation.

[0221] The second acquisition module is configured to acquire a target time of the target object after each operation.

[0222] The comparison and verification module is configured to compare a size relationship between the target time before each operation and the target time after each operation, and determine whether to pass the verification according to the size relationship between the target time before each operation and the target time after each operation.

[0223] In some optional embodiments, the operation module includes:

[0224] The first operation unit is configured to perform a content modification operation on the target object.

[0225] The second operation unit is configured to perform a permission modification operation on the target object after the content modification operation.

[0226] In some optional embodiments, each target time includes a date time and a time minute second time.

[0227] The comparison and verification module includes:

[0228] The first judgment unit is configured to judge whether the date time of the creation time after the content modification operation on the target object is equal to the date time of the creation time after the content modification operation.

[0229] the second judging unit judges whether the hour-minute-second time of the creation time after the content modification operation on the target object is equal to the hour-minute-second time of the creation time after the content modification operation on the target object in the case that the hour-minute-second time of the creation time after the content modification operation on the target object is equal to the hour-minute-second time of the creation time after the content modification operation on the target object;

[0230] the third judging unit judges whether the date time of the content modification time after the content modification operation on the target object is equal to the date time of the content modification time after the content modification operation on the target object in the case that the hour-minute-second time of the creation time after the content modification operation on the target object is equal to the hour-minute-second time of the creation time after the content modification operation on the target object;

[0231] the fourth judging unit judges whether the hour-minute-second time of the content modification time after the content modification operation on the target object is greater than the hour-minute-second time of the content modification time after the content modification operation on the target object in the case that the date time of the content modification time after the content modification operation on the target object is equal to the date time of the content modification time after the content modification operation on the target object;

[0232] the fifth judging unit judges whether the date time of the authority change time after the content modification operation on the target object is equal to the date time of the authority change time after the content modification operation on the target object in the case that the hour-minute-second time of the content modification time after the content modification operation on the target object is greater than the hour-minute-second time of the content modification time after the content modification operation on the target object;

[0233] the sixth judging unit judges whether the hour-minute-second time of the authority change time after the content modification operation on the target object is greater than the hour-minute-second time of the authority change time after the content modification operation on the target object in the case that the date time of the authority change time after the content modification operation on the target object is equal to the date time of the authority change time after the content modification operation on the target object;

[0234] the seventh judging unit continues to judge the size relationship between the target time before and after the content modification operation on the target object in the case that the hour-minute-second time of the authority change time after the content modification operation on the target object is greater than the hour-minute-second time of the authority change time after the content modification operation on the target object.

[0235] In some optional embodiments, the apparatus further comprises:

[0236] the size file separation checking module is configured to determine whether the size file separation switch is closed.

[0237] In some alternative embodiments, the above-described apparatus further includes:

[0238] The NFS service module is used to determine whether the NFS service status of all nodes in the cluster is in a normal state.

[0239] In some alternative embodiments, the above-described apparatus further includes:

[0240] The virtual IP verification module is used to determine whether a network virtual IP exists in the cluster.

[0241] Further functional descriptions of the above modules and units are the same as those in the corresponding embodiments described above, and will not be repeated here.

[0242] In this embodiment, the document classification device of the automated system is presented in the form of a functional unit. Here, a unit refers to an ASIC (Application Specific Integrated Circuit) circuit, a processor and memory that execute one or more software or fixed programs, and / or other devices that can provide the above functions.

[0243] This invention also provides a computer device having the above-described features. Figure 9 The document classification device of the automated system shown.

[0244] Please see Figure 10 , Figure 10 This is a schematic diagram of the structure of a computer device provided in an optional embodiment of the present invention, such as... Figure 10 As shown, the computer device includes one or more processors 10, memory 20, and interfaces for connecting the components, including high-speed interfaces and low-speed interfaces. The components communicate with each other via different buses and can be mounted on a common motherboard or otherwise installed as needed. The processors can process instructions executed within the computer device, including instructions stored in or on memory to display graphical information of a GUI on external input / output devices (such as display devices coupled to the interfaces). In some alternative implementations, multiple processors and / or multiple buses can be used with multiple memories and multiple memory modules, if desired. Similarly, multiple computer devices can be connected, each providing some of the necessary operations (e.g., as a server array, a group of blade servers, or a multiprocessor system). Figure 10 Take a processor 10 as an example.

[0245] The processor 10 can be a central processor, a network processor, or a combination thereof. The processor 10 can further include hardware chips. The hardware chips can be application specific integrated circuits, programmable logic devices, or a combination thereof. The programmable logic devices can be complex programmable logic devices, field programmable logic gate arrays, general array logic, or any combination thereof.

[0246] The memory 20 stores instructions executable by the at least one processor 10 to cause the at least one processor 10 to perform the methods illustrated by the above embodiments.

[0247] The memory 20 can include a program storage area and a data storage area. The program storage area can store an operating system, application programs required by at least one function, and the like. The data storage area can store data created according to the use of the computer device, and the like. In addition, the memory 20 can include a high-speed random access memory, and can further include a non-transitory memory such as at least one disk storage device, a flash memory device, or other non-transitory solid state storage device. In some alternative embodiments, the memory 20 can optionally include a memory disposed remotely from the processor 10, which can be connected to the computer device through a network. Examples of the network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and a combination thereof.

[0248] The memory 20 can include a volatile memory such as a random access memory, and can also include a non-volatile memory such as a flash memory, a hard disk, or a solid state disk. The memory 20 can further include a combination of the above-mentioned types of memories.

[0249] The computer device further includes a communication interface 30 for communication of the computer device with other devices or communication networks.

[0250] The embodiments of the present application also provide a computer readable storage medium. The above-mentioned methods according to the embodiments of the present application can be implemented in hardware, firmware, or recorded in a storage medium, or stored in a remote storage medium or a non-transitory machine readable storage medium and downloaded to a local storage medium through network downloading, so that the methods described herein can be processed by such software on a storage medium using a general purpose computer, a special purpose processor, or programmable or special purpose hardware. The storage medium can be a disk, an optical disk, a read-only memory, a random access memory, a flash memory, a hard disk, or a solid state disk, etc. Further, the storage medium can further include a combination of the above-mentioned types of memories. It can be understood that the computer, the processor, the microprocessor controller, or the programmable hardware includes a storage component that can store or receive software or computer code, when the software or computer code is accessed and executed by the computer, the processor, or the hardware, the methods illustrated by the above embodiments are implemented.

[0251] While embodiments of the present application have been described in conjunction with the appended drawings, various modifications and changes can be suggested by persons skilled in the art, and all such modifications and changes are believed to fall within the scope of the present application as defined by the appended claims.

Claims

1. A method of file staging for an automation system, the method comprising: The method comprises: The cluster creates an authentication user group and creates an authentication user based on the authentication user group; The cluster maintains an active connection with the client; The authentication user group and the authentication user are synchronized to the client; A tenant is created; An object scenario user associated with the authentication user and the tenant is created; A bucket belonging to the tenant is created through the related key of the object scenario user, and the bucket is used for the client to upload objects; A network file system share is set for the bucket, and the network file system share is mounted on the client; The client obtains the latest target time of an object uploaded into the bucket through an object storage protocol through the network file system share, and the target time comprises a creation time, a content modification time and / or a permission change time; The object is classified based on the latest target time; The file classification method of the automatic system further comprises: The client obtains the latest target time of a target object uploaded into the bucket through an object storage protocol through the network file system share; A first operation is performed on the target object, and the first operation comprises a content modification operation and / or a permission modification operation; The target time of the target object after each operation is obtained; The size relationship between the target time before and after each operation is compared, and whether to pass the verification is determined according to the size relationship between the target time before and after each operation.

2. The method of claim 1, wherein, The first operation performed on the target object comprises: The content modification operation is performed on the target object; The permission modification operation is performed on the target object after the content modification operation.

3. The method of claim 2, wherein, Each target time comprises a date time and a time, minute and second time; The comparison of the size relationship between the target time before and after each operation and the determination of whether to pass the verification according to the size relationship between the target time before and after each operation comprise: It is judged whether the date time of the creation time after the content modification operation on the target object is equal to the date time of the creation time after the content modification operation; If equal, it is judged whether the time, minute and second time of the creation time after the content modification operation on the target object is equal to the time, minute and second time of the creation time after the content modification operation; If equal, it is judged whether the date time of the content modification time after the content modification operation on the target object is equal to the date time of the content modification time after the content modification operation; If equal, it is judged whether the time, minute and second time of the content modification time after the content modification operation on the target object is greater than the time, minute and second time of the content modification time after the content modification operation; If greater, it is judged whether the date time of the permission change time after the content modification operation on the target object is equal to the date time of the permission change time after the content modification operation; If equal, it is judged whether the time, minute and second time of the permission change time after the content modification operation on the target object is greater than the time, minute and second time of the permission change time after the content modification operation; If greater, continue to determine the size relationship between the target time before and after the permission modification operation.

4. The method of claim 1, wherein, Before the client obtains the latest target time of the target object uploaded into the bucket through the object storage protocol through the network file system shared, further comprising: Determine whether the large file separation switch is off.

5. The method of claim 1, wherein, Before the client obtains the latest target time of the target object uploaded into the bucket through the object storage protocol through the network file system shared, further comprising: Determine whether the cluster all node NFS service state is in a normal state.

6. The method of claim 1, wherein, Before the client obtains the latest target time of the target object uploaded into the bucket through the object storage protocol through the network file system shared, further comprising: Determine whether the cluster exists a network virtual IP.

7. A file staging device of an automation system, characterized in that The device comprises: An authentication user module for creating an authentication user group in the cluster and creating an authentication user based on the authentication user group; A connection module for maintaining an active connection between the cluster and the client; A synchronization module for synchronizing the authentication user group and the authentication user to the client; A tenant creation module for creating a tenant; An object scenario user creation module for creating an object scenario user associated with the authentication user and the tenant; A bucket creation module for creating a bucket belonging to the tenant through the related key of the object scenario user, the bucket being used for the client to upload objects; A sharing module for setting a network file system shared for the bucket and mounting the network file system shared in the client; A time acquisition module for obtaining the latest target time of the object uploaded into the bucket through the object storage protocol through the network file system shared in the client, the target time including a creation time, a content modification time and / or a permission change time; A file grading module for grading the object based on the latest target time; The file grading device of the automation system further comprises: A first acquisition module for obtaining the latest target time of the target object uploaded into the bucket through the object storage protocol through the network file system shared in the client; An operation module for performing a first operation on the target object, the first operation including a content modification operation and / or a permission modification operation; A second acquisition module for obtaining the target time of the target object after each operation; A comparison verification module for comparing the size relationship between the target time before and after each operation and determining whether to pass the verification according to the size relationship between the target time before and after each operation.

8. A computer device, comprising: Comprise: A memory and a processor, which are communicatively connected between each other, the memory stores computer instructions, and the processor executes the computer instructions to perform the file grading method of the automation system according to any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, The computer readable storage medium stores computer instructions, and the computer instructions are used to make the computer execute the file grading method of the automation system according to any one of claims 1 to 6.

Images