CN115774742A

CN115774742A - Data storage newly-increased method, device, equipment, medium and product of private cloud

Info

Publication number: CN115774742A
Application number: CN202211538409.XA
Authority: CN
Inventors: 马涛; 韩兆晖; 王家学
Original assignee: China Construction Bank Corp; CCB Finetech Co Ltd
Current assignee: China Construction Bank Corp; CCB Finetech Co Ltd
Priority date: 2022-12-02
Filing date: 2022-12-02
Publication date: 2023-03-10

Abstract

The application relates to the technical field of cloud storage, and provides a data storage adding method, device, equipment, medium and product of a private cloud, which comprises the following steps: receiving a work order application sent by a user side; sending the application work order to a management end, and receiving approval information sent by the management end according to the application work order; if the approval result of the approval information is determined to be passed, summarizing the approval information and the application work order to obtain task information, generating a task queue according to the task information, sequentially creating session connection between the task information and the private cloud through the task queue, and mounting data storage corresponding to the task information to the private cloud through the session connection; the task queue is a message queue which is sequentially arranged by task IDs of at least one piece of task information. The method and the device improve the efficiency of data mounting operation and achieve the technical effect of carrying out batch mounting on a plurality of data storages.

Description

Data storage newly-increased method, device, equipment, medium and product of private cloud

Technical Field

The present application relates to the field of cloud storage technologies, and in particular, to a data storage adding method, apparatus, device, medium, and product for a private cloud.

Background

Virtualization is a resource management technology, which can create a plurality of mutually independent virtual servers on one physical machine, pool physical resources including servers, CPUs, memories, networks, storages, GPUs, and the like, and dynamically and flexibly allocate the physical resources to the virtual servers. The virtual server allows different operating systems to be installed and different network IP addresses to be configured. Currently, enterprises typically deploy virtualized private clouds based on technologies such as Vmware, citrix, KVM, and the like.

In a virtualized cloud environment realized based on Vmware, data storage is usually mounted to a virtual server (such as an Esxi server) through an NFS protocol, and then the data storage is divided into small hard disks to be distributed to the virtual server for use, so that the technical effect of newly adding data storage in a private cloud is realized; the data storage is a logic container which can hide the characteristics of various storage devices and provides a uniform model for storing virtual server files.

However, the inventor finds that, in the current private cloud, it is usually necessary to manually access the private cloud, manually create a data volume in the private cloud, and manually invoke the private cloud to mount the data storage to the data volume, so as to achieve the effect of adding a new data storage in the private cloud, which leads to complex operation and low efficiency of adding a new data storage.

Disclosure of Invention

The application provides a data storage adding method, device, equipment, medium and product of a private cloud, which are used for solving the problems of complex operation and low efficiency of the current data storage adding.

In a first aspect, the present application provides a method for newly adding data storage to a private cloud, including:

receiving a work order application sent by a user side; the application work order is used for indicating that the data storage is mounted in a preset private cloud; the private cloud is a cloud storage service cluster consisting of a plurality of virtual servers for storing data; the data storage is a logic container storing file information;

sending the application work order to a management end, and receiving examination and approval information sent by the management end according to the application work order; the approval information is used for indicating permission or refusal of mounting the data storage into a private cloud;

if the approval result of the approval information is determined to be passed, summarizing the approval information and the application work order to obtain task information, generating a task queue according to the task information, sequentially creating session connection between the task information and the private cloud through the task queue, and mounting data storage corresponding to the task information to the private cloud through the session connection; the task queue is a message queue which is sequentially arranged by task IDs of at least one piece of task information.

In the above scheme, the receiving of the application work order sent by the user side includes:

sending a user application page to a user side;

receiving an application work order generated by a user side through form input information filled in the user application page; wherein the form input information includes: the method comprises the following steps of applying a name, a target cluster name, a data storage name and an execution type; the application name is a unique identifier of the application work order; the target cluster name is the name of the private cloud to which the application work order indicates to mount the data storage; the data store name is a unique identification of the data store; the execution type represents an execution mode of the application work order; the execution type comprises immediate execution and timed execution; the immediate execution is used for indicating that the task ID of the task information is recorded into the message queue when the task information is obtained; and the timing execution is used for recording the task ID of the task information into the message queue when the current time is consistent with the execution time in the timing execution.

In the above solution, the sending of the application work order to the management end and the receiving of the approval information sent by the management end according to the application work order include:

loading the application work order into a preset examination and approval vacant page to obtain an examination and approval page, and sending the examination and approval page to the management end;

receiving approval information sent by the management terminal on the approval page according to the application work order; wherein the approval information comprises: approval conclusion and target server name; the approval conclusion is used for indicating that the data storage is allowed or refused to be mounted into the private cloud; the target server name is the name of the storage server that created the data volume in the private cloud and defines the execution authority of the data volume.

In the above scheme, after the approval information and the application work order are collected to obtain the task information, the method further includes:

and loading the task information into a preset detail page template to obtain a detail page, and sending the detail page to the user side and/or the management side.

In the foregoing solution, the generating a task queue according to the task information includes:

performing authority verification on the task information;

if the task information passes the authority verification, the task information passing the authority verification is stored in a preset database, and the task state of the task information stored in the database is set to be approved;

extracting the execution type of the task information in the database;

if the execution type is determined to be immediate execution, outputting the task ID of the task information to a preset message queue, converting the message queue into a task queue, and setting the task state of task data with the task ID in the message queue as a queue; wherein the task ID is a unique identification of the task information.

In the above scheme, after the extracting the execution type of the task information in the database, the method further includes:

if the execution type is determined to be the timing execution, polling the execution time of the task information in the database;

if the execution time is determined to be consistent with the current time, outputting the task ID of the task information corresponding to the execution time consistent with the current time to the message queue, converting the message queue into a task queue, and setting the task state of the task information with the task ID in the message queue as the queue.

In the foregoing solution, the sequentially creating session connections between the task information and the private cloud through the task queue includes:

acquiring a task ID positioned at the head from the task queue, setting task information corresponding to the task ID positioned at the head as task execution information, and setting the task state of the task execution information as execution;

extracting a target server name in the task execution information, accessing a storage server corresponding to the target server name, and sending a creation request and an authorization request to the storage server; the storage server is used for creating a data volume in the private cloud and defining execution authority of the data volume; the creation request is to instruct the storage server to create a data volume in the private cloud; the authorization request is used for instructing the storage server to define the execution authority of the task execution information in the data volume;

receiving session connection sent by the storage server; wherein the session connection is used to specify a session between management platforms corresponding to the storage servers in the private cloud.

In the foregoing scheme, the mounting the data storage corresponding to the task information to the private cloud through the session connection includes:

accessing a management platform of the private cloud through the session connection;

acquiring a service object of a virtual server in a private cloud corresponding to a target cluster name in the task information; the service object is used for accessing a data mounting rule of the virtual server and attribute information of the virtual server; the virtual server is a virtual host having the data volume and used to mount the data storage;

generating a change request according to the service object, the address information of the storage server and the volume name of the data volume, and sending the change request to the management platform; the change request is used for indicating the management platform to access the storage server according to the address information, access a data volume created in the virtual server by the storage server according to the volume name and through the storage server, acquire a data mounting rule of the virtual server according to the service object, and mount the data storage to the data volume according to the data mounting rule.

In the foregoing solution, after sending the change request to the management platform, the method further includes:

if the successful change information sent by the management platform according to the change request is received, deleting the task ID corresponding to the task information from the task queue, and setting the task state of the task information as successful mounting; wherein the change success information indicates that the data storage is mounted in the data volume;

if receiving change failure information sent by the management platform according to the change request, deleting a task ID corresponding to the task information from the task queue, and setting the task state of the task information as mounting failure; wherein the change failure information indicates that the data storage is not mounted in the data volume.

In the above scheme, after the task information is loaded into a preset detail page template to obtain a detail page, the method further includes:

loading the task state of the task information into the detail page; wherein the task state comprises: approval pass, queue in, execution in, mount success, and mount failure.

In a second aspect, the present application provides a data storage adding apparatus for a private cloud, including:

the front-end application module is used for receiving an application work order sent by a user side; the application work order is used for indicating that the data storage is mounted in a preset private cloud; the private cloud is a cloud storage service cluster consisting of a plurality of virtual servers for storing data; the data storage is a logical container storing file information;

the front-end approval module is used for sending the application work order to a management end and receiving approval information sent by the management end according to the application work order; the approval information is used for indicating permission or refusal of mounting the data storage into a private cloud;

the data mounting module is used for summarizing the approval information and the application work order to obtain task information if the approval result of the approval information is determined to be passed, generating a task queue according to the task information, sequentially creating session connection between the task information and the private cloud through the task queue, and mounting data storage corresponding to the task information to the private cloud through the session connection; the task queue is a message queue which is sequentially arranged by task IDs of at least one piece of task information.

In the foregoing solution, the data storage newly adding apparatus further includes:

the front-end detailed condition module is used for loading the task information into a preset detailed page template to obtain a detailed page; and sending the detail page to the user side and/or the management side.

In the above solution, the front-end detail module is further configured to load the task state of the task information into the detail page; wherein the task state comprises: approval pass, in queue, in execution, mount success, and mount failure.

In a third aspect, the present application provides a computer device comprising: a processor and a memory communicatively coupled to the processor;

the memory stores computer-executable instructions;

the processor executes computer-executable instructions stored in the memory to implement the data storage augmentation method as claimed above.

In a fourth aspect, the present application provides a computer-readable storage medium, in which computer-executable instructions are stored, and when the computer-executable instructions are executed by a processor, the computer-executable instructions are used to implement the data storage adding method described above.

In a fifth aspect, the present application provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, the computer program implements the data storage adding method.

According to the method, the device, the equipment, the medium and the product for newly adding the data storage of the private cloud, the user only needs to determine that the data storage needs to be mounted by receiving the application work order sent by the user side, and the subsequent data mounting operation can be realized by the private cloud needing to mount the data storage; the application work order is sent to the management end, and the examination and approval information sent by the management end according to the application work order is received, so that the management end can judge whether the data storage is allowed to be mounted to the data mounting operation of the private cloud or not only by generating the examination and approval information; the method comprises the steps of obtaining task information by summarizing approval information and applying a work order, generating a task queue according to the task information, sequentially establishing session connection between the task information and a private cloud through the task queue, and mounting data storage corresponding to the task information to the private cloud through the session connection, so that the operation of automatically mounting the data storage corresponding to a plurality of task information to the private cloud according to the task queue is realized, the efficiency of data mounting operation is improved, the technical effect of batch mounting of a plurality of data storage is realized, manual access to the private cloud is not needed, a data volume is manually created in the private cloud, the private cloud is manually called to mount the data storage to the data volume, and the problems that data storage adding operation is complicated and the efficiency is low in the prior art are solved.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and together with the description, serve to explain the principles of the application.

Fig. 1 is a schematic view of an application scenario provided in an embodiment of the present application;

fig. 2 is a flowchart of an embodiment 1 of a data storage addition method provided in an embodiment of the present application;

fig. 3 is a flowchart of an embodiment 2 of a data storage addition method according to an embodiment of the present application;

FIG. 4 is a schematic diagram of program modules of a data storage adding apparatus according to the present invention;

fig. 5 is a schematic diagram of a hardware structure of a computer device in the computer device according to the present invention.

Specific embodiments of the present application have been shown by way of example in the drawings and will be described in more detail below. The drawings and written description are not intended to limit the scope of the inventive concepts in any manner, but rather to illustrate the concepts of the application by those skilled in the art with reference to specific embodiments.

Detailed Description

Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. The following description refers to the accompanying drawings in which the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.

Referring to fig. 1, the application scenario is as follows:

the server 2 running the data storage adding method of the private cloud is respectively connected with the user side 3, the management side 4 and the private cloud 5; the server 2 receives a work order application sent by the user side 3; the server 2 sends the application work order to the management terminal 4, and receives approval information sent by the management terminal according to the application work order; if the server 2 determines that the approval result of the approval information is passed, the approval information and the application work order are collected to obtain task information, a task queue is generated according to the task information, session connection between the task information and the private cloud 5 is sequentially established through the task queue, and data storage corresponding to the task information is mounted to the private cloud 5 through the session connection. The private cloud 5 is provided with at least one storage server 51 and at least one virtual server 52, wherein the storage server 51 is used for creating a data volume in the virtual server 52 of the private cloud 5 and defining the execution authority of the data volume; the virtual server 52 is used to mount data storage.

The noun explains:

data storage: the data store is a logical container that hides the features of the various storage devices and provides a unified model to store virtual server files. In VMware, a user can format the data store using VMFS or using the NFS protocol based shared file system of the storage device stripe, depending on the type of storage used.

A network file system: network File Systems (NFS) allow users to access files on remote hosts in the same way as any local file is accessed. This file access is completely transparent to the client and can work on a variety of servers and a variety of host architectures.

Exi Server: in the virtualization scheme of vmware, an Esxi operating system is installed on a host machine, and then a virtual server is created thereon.

VPSHERE SDK: the Vsphere-oriented software development kit provided by VMWARE corporation, through which various virtualized resources of VCenter or Vsphere may be accessed and operated.

Django: an open source Web application framework that follows the MTV framework, written by Python, emphasizes code reuse and multiple components can conveniently serve the entire framework in a "plug-in" fashion.

VUE: a progressive web front-end framework for constructing a user interface realizes responsive data binding and combined view components through an API (application programming interface) which is as simple as possible, and provides characteristics of event monitoring, dynamic rendering, data bidirectional binding and the like.

The following describes the technical solution of the present application and how to solve the above technical problems in detail by specific embodiments. These several specific embodiments may be combined with each other below, and details of the same or similar concepts or processes may not be repeated in some embodiments. Embodiments of the present application will be described below with reference to the accompanying drawings.

Example 1:

referring to fig. 2, the present application provides a method for adding data storage to a private cloud, including:

s101: receiving a work order application sent by a user side; the application work order is used for indicating that the data storage is mounted in a preset private cloud; the private cloud is a cloud storage service cluster consisting of a plurality of virtual servers for storing data; the data store is a logical container that stores file information.

In a preferred embodiment, the receiving of the application work order sent by the user side includes:

sending a user application page to a user side;

receiving an application work order generated by a user through form input information filled in a user application page; wherein, form input information includes: the method comprises the following steps of applying a name, a target cluster name, a data storage name and an execution type; the application name is a unique identifier of the application work order; the target cluster name is the name of a private cloud to which the application work order indicates to mount the data storage; the data store name is a unique identification of the data store; executing the execution mode of the type characterization application work order; the execution type comprises immediate execution and timing execution; immediately executing a task ID used for indicating that the task information is recorded into a message queue when the task information is obtained; and the timing execution is used for recording the task ID of the task information into the message queue when the current time is consistent with the execution time in the timing execution.

In this example, by sending the user application page to the user side and receiving the application work order mode generated by the user side through the form input information filled in the user application page, the visualization of data operation of mounting the data storage to the private cloud is realized, and the generation efficiency and convenience of the application work order are improved. In this embodiment, the user end converts the form input information into the application work form by clicking the application submission button on the user application page. Mount (mounting) refers to a process by which computer files and directories on a storage device, such as a hard disk, CD-ROM, or shared resource, are made available to a user through the computer's file system by an operating system.

S102: sending the application work order to a management end, and receiving approval information sent by the management end according to the application work order; wherein the approval information is used for indicating permission or refusal of mounting the data storage into the private cloud.

In a preferred embodiment, the sending the application work order to the management end, and receiving the approval information sent by the management end according to the application work order, includes:

loading the application work order into a preset examination and approval vacant page to obtain an examination and approval page, and sending the examination and approval page to a management end;

receiving approval information sent by a management end on an approval page according to the application work order; wherein the approval information includes: approval conclusion and target server name; the approval conclusion is used for indicating permission or refusal of mounting the data storage into the private cloud; the target server name is the name of the storage server that created the data volume in the private cloud and defines the execution authority of the data volume.

In the embodiment, the approval page is obtained by loading the application work order into the preset approval vacant page, the approval page is sent to the management end, and the approval information sent by the management end on the approval page according to the application work order is received, so that the visualization of the mounting operation of the approval data is realized, and the convenience of the approval of the application work order is improved.

In this embodiment, the storage management user acquires the created application work order, selects a target storage server for each data storage, and after clicking an approval pass button, triggers an implementation process of adding the data storage and generates approval information.

The approval page provides a list of existing storage servers for a storage administrator user, and after the administrator selects a target storage server for each data storage in the application, the administrator clicks a confirmation button to complete resource allocation, that is, the name of the target server in the approval information is generated.

In an exemplary embodiment, the user application page and the approval page are implemented using VUE technology. Vue is a progressive framework for constructing a user interface, is applied from the bottom layer to the top layer, and a core library of Vue only focuses on a view layer, is easy to enter a door, can be integrated with a third-party library or an existing project, and can be used for complex single-page application. Briefly, vue is a set of front-end development framework, vue is one of the three mainstream frameworks at present, and the other two frameworks are React and Angular.

S103: if the approval result of the approval information is confirmed to be passed, summarizing the approval information and the application work order to obtain task information, generating a task queue according to the task information, sequentially creating session connection between the task information and the private cloud through the task queue, and mounting data storage corresponding to the task information to the private cloud through the session connection; the task queue is a message queue which is sequentially arranged by task IDs of at least one piece of task information.

It should be noted that the implementation is realized through a Python/Django technology, the approval information and the application work order are summarized to obtain the task information, the task queue is generated according to the task information, the session connection between the task information and the private cloud is sequentially established through the task queue, and the data storage corresponding to the task information is mounted to the data mounting operation of the private cloud through the session connection. Python is an object-oriented interpreted computer programming language; django is an open source Web application framework written by Python.

In a preferred embodiment, generating the task queue according to the task information includes:

performing authority verification on the task information;

if the task information passes the authority verification, the task information passing the authority verification is stored in a preset database, and the task state of the task information stored in the database is set to be approved.

In this example, the permission check is to determine whether the user side has the right to mount the data storage to the private cloud;

if the task information passes the permission verification, storing the task information passing the permission verification into a preset database, and setting the task state of the task information stored into the database as approved; and if the task information is determined not to pass the authority verification, deleting the task information which does not pass the authority verification, and ending.

In this embodiment, user identity information of a user side corresponding to the task information is obtained; if the user identity information is confirmed to belong to a preset user authority list, determining that the task information passes authority verification; if the user identity information is confirmed not to belong to the user authority list, determining that the task information does not pass the authority verification; the user authority list at least has one user identity information.

Therefore, the permission of the task information is verified, so that the user side is ensured to be authorized to mount the data storage to the private cloud, and the data security in the private cloud is ensured.

Further, extracting the execution type of the task information in the database;

In this example, by outputting the task ID whose execution type is to immediately execute the corresponding task information to the preset message queue and setting the task state of the task data whose task ID is in the message queue to be in the queue, the ordered batch data mounting operation for the data storage corresponding to a large amount of task information is realized, and the orderliness and the mounting efficiency of data mounting are ensured.

Further, after extracting the execution type of the task information in the database, the method further includes:

and if the execution time is consistent with the current time, outputting the task ID of the task information corresponding to the execution time consistent with the current time to a message queue, converting the message queue into a task queue, and setting the task state of the task information with the task ID in the message queue as the queue.

In this example, by outputting the task ID of the task information corresponding to the execution time consistent with the current time to the message queue and setting the task state of the task information with the task ID in the message queue as the queue, the ordered batch data mounting operation on the data storage corresponding to a large amount of task information is realized according to the settable execution time, and the orderliness and the mounting efficiency of data mounting and the operability of data mounting are ensured.

In a preferred embodiment, sequentially creating session connections between the task information and the private cloud through the task queue includes:

acquiring a task ID positioned at the head from the task queue, setting task information corresponding to the task ID positioned at the head as task execution information, and setting the task state of the task execution information as in execution;

extracting a target server name in the task execution information, accessing a storage server corresponding to the target server name, and sending a creation request and an authorization request to the storage server; the storage server is used for creating a data volume in the private cloud and defining the execution authority of the data volume; the creation request is used for instructing the storage server to create a data volume in the private cloud; the authorization request is used for indicating the storage server to define the execution authority of the task execution information in the data volume;

receiving session connection sent by a storage server; wherein the session connection is used to specify a session between management platforms corresponding to the storage servers in the private cloud.

In this example, the creation request is generated by calling a storage creation interface provided by the storage server of the private cloud, where the storage creation interface is a computer interface provided by the storage server to create a data volume function in the private cloud.

The authorization request is generated by calling a storage authorization interface provided by a storage server of the private cloud, and the storage authorization interface is a computer interface provided by the storage server and used for defining the execution authority of the data volume.

The Data volume (Data Volumes) is a directory or file in the host, and the design goal of the Data volume is Data persistence, which is completely independent of the life cycle of the container.

The execution authority defines the operation authority of the data volume, for example: authorizing reading data from the data volume, authorizing inserting new data into the data volume, authorizing updating data in the data volume, and authorizing deleting data in the data volume.

Therefore, by means of sending the creation request and the authorization request to the storage server, the data volume can be created in the private cloud directly by calling the storage creation interface and the storage authorization, the situation that the creation and authorization efficiency of the data volume is low due to manual access to the storage server of the private cloud is avoided, and the creation efficiency of the data volume is improved.

In a preferred embodiment, the mounting the data storage corresponding to the task information to the private cloud through the session connection includes:

accessing a management platform of the private cloud through session connection;

acquiring a service object of a virtual server in a private cloud corresponding to a target cluster name in the task information; the service object is used for accessing a data mounting rule of the virtual server and attribute information of the virtual server; a virtual server is a virtual host that has data volumes and is used to mount data storage;

generating a change request according to the service object, the address information of the storage server and the volume name of the data volume, and sending the change request to the management platform; the change request is used for indicating the management platform to access the storage server according to the address information, access the data volume created in the virtual server by the storage server according to the volume name and through the storage server, acquire the data mounting rule of the virtual server according to the service object, and mount the data storage to the data volume according to the data mounting rule.

In this example, the management platform accessing the private cloud is connected through the session, so that a technical effect of automatically accessing the management platform of the private cloud is achieved. The management platform is a VCenter, the VCenter refers to a VMware vCenterServer, and the VMware vCenterServer provides a scalable and extensible platform, so that a foundation is laid for virtualization management. The VMware vCenter Server (formerly called VMware virtual center) can centrally manage the VMware vSphere environment, and compared with other management platforms, the control of an IT administrator on the virtual environment is greatly improved. VMware vCenter Server: the method improves centralized control and visibility on each level of a virtual infrastructure, develops vSphere potential through active management, and is a scalable and extensible platform supported by a wide partner system.

The virtual server is an Esxi server which is a virtual server designed for running the virtual server, reducing the configuration requirement to the maximum extent and simplifying the deployment based on a VMware vSphere virtualization management program architecture.

The service object is a Server object which defines a class associated with the virtual Server to enable access to methods and attributes on the virtual Server to be provided for external devices to access resources on the virtual Server via the methods and attributes; the data mounting rule is a computer method preset in the virtual server and used for realizing mounting data storage; the attribute information describes attributes of the virtual server, such as: the total storage space of the virtual server, occupied space and unoccupied space, and the like.

Generating a change request according to the service object, the address information of the storage server and the volume name of the data volume, and sending the change request to the management platform; and enabling the management platform to acquire the service objects of the virtual servers in the private cloud according to a preset development specification, wherein the development specification is a Vspee SDK specification which is used for deploying the virtual servers in the private cloud and defining the service objects of the virtual servers, so that the service objects of the virtual servers in the private cloud can be directly acquired according to the development specification.

Furthermore, calling a createnasdastore () function according to the service object, configuring the address of the storage server and the volume name of the data volume 5, and generating a change request; wherein, NAS (Network Attached Storage: network Attached Storage)

The technology is a data center integrating distributed and independent data into large-scale and centralized management so as to facilitate access to different hosts and application servers; datastore is a manageable storage entity that typically serves as a repository for virtual server files (including log files, scripts, configuration files, virtual disks, etc.). Thus, by createNasDataStore ()

The function mounts the data storage to the data volume and forms a virtual file of the data storage in the data volume.

Further, after sending the change request to the management platform, the method further includes:

if the successful change information sent by the management platform according to the change request is received, deleting the task ID corresponding to the task information from the task queue, and setting the task state of the task information as successful mounting; wherein the change success information represents that the data storage is mounted in the data volume;

if receiving the change failure information sent by the management platform according to the change request, deleting the task ID5 corresponding to the task information from the task queue, and setting the task state of the task information as mounting failure; wherein the change failure information represents the number

The data store is not mounted to the data volume.

In this example, by receiving the change success information or the change failure information sent by the management platform, the closed-loop management of the mount operation of the data storage to the data volume is realized, and the reliability of the data mount operation is ensured.

S104: and if the approval result of the approval information is determined to be failed, deleting the application work order and the approval information, and ending. 0 in the technical solution of the present application, the collection, storage, use, addition of the related information such as financial data or user data

The processes of industry, transmission, supply, disclosure and the like all accord with the regulations of relevant laws and regulations without violating the customs of public order.

Example 2:

referring to fig. 3, the present application provides a method for adding data storage to a private cloud, including: 5S201: receiving a work order application sent by a user side; the application work order is used for indicating that the data storage is mounted in a preset private cloud; the private cloud is a cloud storage service cluster consisting of a plurality of virtual servers for storing data; the data store is a logical container in which file information is stored.

This step is the same as S101 in embodiment 1, and therefore will not be described herein.

S202: sending the application work order to a management end, and receiving examination and approval information sent by the management end according to the application work order; wherein the 0 approval information is used for indicating permission or refusal of mounting the data storage into the private cloud.

This step is the same as S102 in embodiment 1, and therefore will not be described herein.

S203: if the approval result of the approval information is determined to be passed, summarizing the approval information and the application work order to obtain task information, generating a task queue according to the task information, sequentially establishing session connection between the task information and the private cloud through the task queue,

mounting data storage corresponding to the task information to a private cloud through session connection; wherein the task queue is a message queue in which task IDs of at least one of the 5-task information are sequentially arranged.

This step is the same as S103 in embodiment 1, and therefore will not be described herein.

S204: and if the approval result of the approval information is determined to be failed, deleting the application work order and the approval information, and ending.

This step is the same as S104 in embodiment 1, and therefore will not be described herein.

S205: and loading the task information into a preset detail page template to obtain a detail page, and sending the detail page to the user side and/or the management side.

In this example, the task information is visually displayed by setting a detail page, so that the user side and/or the management side can conveniently check the task information, and the data mounting operation of the data storage can be conveniently managed; wherein, the task information comprises: the application name, the target cluster name, the data storage name, the execution type, the approval conclusion, and the target server name. The task information is displayed on the detail page, so that the user and/or a manager can conveniently perform visual management on the task information of each data mounting operation.

Illustratively, the details page also includes identity information of the user terminal carrying the task information (i.e., the applicant of the task information), application time (time for generating the application work order), and resource amount (amount of resources required for mounting the data storage into the private cloud). So that the user end and/or the management end can track the implementation progress through the page or be used for information backtracking.

In an exemplary embodiment, the user application page, the approval page, and the details page are implemented using VUE technology. Vue is a progressive framework for constructing a user interface, is applied from the bottom layer to the top layer, and a core library of Vue only focuses on a view layer, is easy to enter a door, can be integrated with a third-party library or an existing project, and can be used for complex single-page application. Briefly, vue is a set of front-end development framework, vue is one of the three mainstream frameworks at present, and the other two frameworks are React and Angular.

In a preferred embodiment, after loading the task information into a preset detail page template to obtain a detail page, the method further includes:

loading the task state of the task information into a detail page; wherein the task state comprises: approval pass, queue in, execution in, mount success, and mount failure.

In this example, the task state of each task information is displayed to the user side and/or the management side in the detail page, so that the user side and/or the management side can know the execution condition of each task information, the task information can be managed conveniently, and the task information with a fault can be analyzed in time.

Example 3:

referring to fig. 4, the present application provides a new data storage device 1 for a private cloud, including:

the front-end application module 11 is used for receiving an application work order sent by a user side; the application work order is used for indicating that the data storage is mounted in a preset private cloud; the private cloud is a cloud storage service cluster consisting of a plurality of virtual servers for storing data;

the front-end approval module 12 is used for sending the application work order to the management end and receiving approval information sent by the management end according to the application work order; the approval information is used for indicating permission or refusal of mounting the data storage into the private cloud;

the data mounting module 13 is configured to, if it is determined that the approval result of the approval information passes, collect the approval information and the application work order to obtain task information, generate a task queue according to the task information, sequentially create session connections between the task information and the private cloud through the task queue, and mount data storage corresponding to the task information to the private cloud through the session connections; the task queue is a message queue which is sequentially arranged by task IDs of at least one piece of task information.

Optionally, the data storage adding apparatus 1 further includes:

and the deleting module 14 is configured to delete the application worksheet and the approval information if the approval result of the approval information is determined to be failed, and then end.

Optionally, the data storage adding apparatus 1 further includes:

the front-end detail module 15 is used for loading the task information into a preset detail page template to obtain a detail page; and sending the detail page to the user side and/or the management side.

Optionally, the front-end details module 15 is further configured to load the task state of the task information into a details page; wherein the task state comprises: approval pass, in queue, in execution, mount success, and mount failure.

Example 4:

to achieve the above object, the present application also provides a computer device 6, including: a processor 62 and a memory 61 communicatively coupled to the processor 62; memory 61 stores computer-executable instructions;

the processor executes the computer execution instruction stored in the memory 61 to implement the data storage adding method, where components of the data storage adding device may be distributed in different computer devices, and the computer device 6 may be a smart phone, a tablet computer, a notebook computer, a desktop computer, a rack server, a blade server, a tower server, or a rack server (including an independent server or a server cluster formed by multiple application servers) that executes programs, and the like. The computer device of the embodiment at least includes but is not limited to: a memory 61, a processor 62, which may be communicatively coupled to each other via a system bus, as shown in FIG. 5. It should be noted that fig. 5 only shows a computer device with components, but it should be understood that not all of the shown components are required to be implemented, and more or fewer components may be implemented instead. In the present embodiment, the memory 61 (i.e., a readable storage medium) includes a flash memory, a hard disk, a multimedia card, a card-type memory (e.g., SD or DX memory, etc.), a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a programmable read-only memory (PROM), a magnetic memory, a magnetic disk, an optical disk, and the like. In some embodiments, the memory 61 may be an internal storage unit of the computer device, such as a hard disk or a memory of the computer device. In other embodiments, the memory 61 may also be an external storage device of the computer device, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), or the like, provided on the computer device. Of course, the memory 61 may also include both internal and external storage devices of the computer device. In this embodiment, the memory 61 is generally used for storing an operating system and various application software installed in the computer device, for example, a program code of the data storage device in the third embodiment. Further, the memory 61 may also be used to temporarily store various types of data that have been output or are to be output. Processor 62 may be a Central Processing Unit (CPU), controller, microcontroller, microprocessor, or other data Processing chip in some embodiments. The processor 62 is typically used to control the overall operation of the computer device. In this embodiment, the processor 62 is configured to run the program code stored in the memory 61 or process the data, for example, run the data storage adding apparatus, so as to implement the data storage adding method of the above-mentioned embodiment.

The integrated module implemented in the form of a software functional module may be stored in a computer-readable storage medium. The software functional module is stored in a storage medium and includes several instructions to enable a computer device (which may be a personal computer, a server, or a network device) or a processor to execute some steps of the methods according to the embodiments of the present application. It should be understood that the Processor may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in the incorporated application may be directly implemented by a hardware processor, or may be implemented by a combination of hardware and software modules in the processor. The memory may comprise a high speed RAM memory, and may further comprise a non-volatile storage NVM, such as at least one magnetic disk memory, and may also be a usb disk, a removable hard disk, a read-only memory, a magnetic or optical disk, or the like.

To achieve the above objects, the present application also provides a computer readable storage medium, such as a flash memory, a hard disk, a multimedia card, a card type memory (e.g., SD or DX memory, etc.), a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a Read Only Memory (ROM), an Electrically Erasable Programmable Read Only Memory (EEPROM), a Programmable Read Only Memory (PROM), a magnetic memory, a magnetic disk, an optical disk, a server, an App, etc., on which computer executable instructions are stored, and the program implements corresponding functions when executed by the processor 62. The computer-readable storage medium of the embodiment is used for storing computer-executable instructions for implementing the data storage addition method, and when executed by the processor 62, the computer-readable storage medium implements the data storage addition method of the above-mentioned embodiment.

The storage medium may be implemented by any type or combination of volatile or non-volatile memory devices, such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disks. A storage media may be any available media that can be accessed by a general purpose or special purpose computer.

An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. Of course, the storage medium may also be integral to the processor. The processor and the storage medium may reside in an Application Specific Integrated Circuits (ASIC). Of course, the processor and the storage medium may reside as discrete components in an electronic device or host device.

The application provides a computer program product, which comprises a computer program, and the computer program realizes the data storage adding method when being executed by a processor.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrases "comprising a component of' 8230; \8230;" does not exclude the presence of another like element in a process, method, article, or apparatus that comprises the element.

Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the invention following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the invention pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.

It will be understood that the present application is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the application is limited only by the appended claims.

Claims

1. A data storage adding method for a private cloud is characterized by comprising the following steps:

receiving a work order application sent by a user side; the application work order is used for indicating that the data storage is mounted in a preset private cloud; the private cloud is a cloud storage service cluster consisting of a plurality of virtual servers for storing data; the data storage is a logical container storing file information;

2. The data storage addition method as claimed in claim 1, wherein the receiving of the application work order sent by the user side includes:

sending a user application page to a user side;

receiving an application work order generated by a user side through form input information filled in the user application page; wherein the form input information includes: the method comprises the following steps of applying a name, a target cluster name, a data storage name and an execution type; the application name is a unique identifier of the application work order; the target cluster name is the name of the private cloud to which the application work order indicates to mount the data storage; the data store name is a unique identification of the data store; the execution type represents an execution mode of the application work order; the execution type comprises immediate execution and timing execution; the immediate execution is used for indicating that the task ID of the task information is recorded into the message queue when the task information is obtained; and the timing execution is used for recording the task ID of the task information into the message queue when the current time is consistent with the execution time in the timing execution.

3. The data storage addition method according to claim 1, wherein the sending the application work order to a management end and receiving approval information sent by the management end according to the application work order comprises:

receiving approval information sent by the management terminal on the approval page according to the application work order; wherein the approval information comprises: approval conclusion and target server name; the approval conclusion is used for indicating that the data storage is allowed or refused to be mounted into the private cloud; the target server name is a name of a storage server that creates a data volume in the private cloud and defines execution rights for the data volume.

4. The data storage addition method as claimed in claim 1, wherein after the approval information and the application work order are collected to obtain task information, the method further comprises:

5. The data storage addition method as claimed in claim 1, wherein the generating a task queue according to the task information includes:

performing authority verification on the task information;

extracting the execution type of the task information in the database;

if the execution type is determined to be immediate execution, outputting the task ID of the task information to a preset message queue, converting the message queue into a task queue, and setting the task state of the task data with the task ID in the message queue as a queue; wherein the task ID is a unique identification of the task information.

6. The data storage adding method as claimed in claim 5, wherein after the extracting the execution type of the task information in the database, the method further comprises:

7. The data storage addition method as claimed in claim 1, wherein the creating of the session connection between the task information and the private cloud in sequence through the task queue includes:

acquiring a first task ID from the task queue, setting task information corresponding to the first task ID as task execution information, and setting a task state of the task execution information as being executed;

extracting a target server name in the task execution information, accessing a storage server corresponding to the target server name, and sending a creation request and an authorization request to the storage server; wherein the storage server is used for creating a data volume in the private cloud and defining the execution authority of the data volume; the creation request is used for instructing the storage server to create a data volume in the private cloud; the authorization request is used for instructing the storage server to define the execution authority of the task execution information in the data volume;

8. The data storage addition method according to claim 7, wherein the mounting, to the private cloud, the data storage corresponding to the task information through the session connection includes:

acquiring a service object of a virtual server in a private cloud corresponding to a target cluster name in the task information; the service object is used for accessing a data mounting rule of the virtual server and attribute information of the virtual server; the virtual server is a virtual host having the data volume and mounting the data storage;

generating a change request according to the service object, the address information of the storage server and the volume name of the data volume, and sending the change request to the management platform; the change request is used for indicating the management platform to access the storage server according to the address information, access a data volume created by the storage server in the virtual server according to the volume name and through the storage server, acquire a data mounting rule of the virtual server according to the service object, and mount the data storage to the data volume according to the data mounting rule.

9. The method of claim 8, wherein after sending the change request to the management platform, the method further comprises:

if receiving successful change information sent by the management platform according to the change request, deleting a task ID corresponding to the task information from the task queue, and setting the task state of the task information as successful mounting; wherein the change success information indicates that the data storage is mounted in the data volume;

if receiving change failure information sent by the management platform according to the change request, deleting a task ID corresponding to the task information from the task queue, and setting the task state of the task information as mounting failure; wherein the failure to change information indicates that the data storage is not mounted to the data volume.

10. The data storage addition method according to claim 4, wherein after the task information is loaded into a preset detail page template to obtain a detail page, the method further comprises:

11. A data storage newly-added device of private cloud, characterized in that includes:

the data mounting module is used for summarizing the approval information and the application work order to obtain task information if the approval result of the approval information is determined to be passed, generating a task queue according to the task information, sequentially creating session connection between the task information and the private cloud through the task queue, and mounting the data storage corresponding to the task information to the private cloud through the session connection; the task queue is a message queue which is sequentially arranged by task IDs of at least one piece of task information.

12. The data storage addition device as recited in claim 11, wherein the data storage addition device further comprises:

13. The data storage adding device as claimed in claim 12, wherein the front-end details module is further configured to load a task status of the task information into the details page; wherein the task state comprises: approval pass, queue in, execution in, mount success, and mount failure.

14. A computer device, comprising: a processor and a memory communicatively coupled to the processor;

the memory stores computer execution instructions;

the processor executes computer-executable instructions stored in the memory to implement the data storage adding method of any one of claims 1 to 10.

15. A computer-readable storage medium having computer-executable instructions stored thereon, which when executed by a processor, implement a data storage addition method as claimed in any one of claims 1 to 10.

16. A computer program product comprising a computer program which, when executed by a processor, implements a data storage augmentation method as claimed in any one of claims 1 to 10.