CN110673787A - Volume configuration method and device - Google Patents
Volume configuration method and device Download PDFInfo
- Publication number
- CN110673787A CN110673787A CN201910833570.1A CN201910833570A CN110673787A CN 110673787 A CN110673787 A CN 110673787A CN 201910833570 A CN201910833570 A CN 201910833570A CN 110673787 A CN110673787 A CN 110673787A
- Authority
- CN
- China
- Prior art keywords
- volume
- target storage
- created
- storage
- attributes
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 37
- 230000006835 compression Effects 0.000 claims description 11
- 238000007906 compression Methods 0.000 claims description 11
- 230000004044 response Effects 0.000 claims description 8
- 238000010586 diagram Methods 0.000 description 6
- 238000004891 communication Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
- G06F3/0604—Improving or facilitating administration, e.g. storage management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0629—Configuration or reconfiguration of storage systems
- G06F3/0632—Configuration or reconfiguration of storage systems by initialisation or re-initialisation of storage systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0638—Organizing or formatting or addressing of data
- G06F3/0644—Management of space entities, e.g. partitions, extents, pools
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Human Computer Interaction (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application discloses a method and a device for configuring a volume, which comprise the following steps: acquiring configuration information of a user aiming at a volume to be created, wherein the configuration information comprises an identifier of the volume to be created and the capacity of the volume to be created; determining a target storage pool from the target storage service according to the capacity of the volume to be created, wherein the residual capacity of the determined target storage pool is not lower than the capacity of the volume to be created, and the target storage pool and the target storage service are bound in advance; volumes desired to be created by the user may be created based on the target storage pool and the identification of the volumes to be created. Therefore, in the process of configuring the volume, the user can only input the identification and the capacity size of the volume to be configured without paying attention to the actual physical volume object, and even after the attribute of the target storage service is preset, the user does not need to configure the attribute of the volume, so that the operation required to be executed by the user in the process of configuring the volume can be effectively simplified, and the use experience of the user can be improved.
Description
Technical Field
The present application relates to the field of volume configuration technologies, and in particular, to a method and an apparatus for configuring a volume.
Background
The storage system is a system composed of various storage devices for storing programs and data, a control unit, a device (hardware) for managing information scheduling, and an algorithm (software) in a computer. The storage system can be directly used by a user, for example, the user (such as a platform administrator, etc.) can perform related operations by operating corresponding storage system management software. In practical applications, users can use the storage system on different platforms.
However, users do not usually care about the actual physical volume objects when configuring volumes using the storage system on the platform, and may not even want to set the attributes of the volumes, and the focus is usually on the usage level of the volumes. Therefore, how to simplify the usage operations that the user needs to perform when configuring the volume becomes an important issue for improving the usage experience when the user configures the volume.
Disclosure of Invention
The embodiment of the application provides a method and a device for configuring a volume, so as to simplify the use operation required to be executed by a user when configuring the volume, and improve the use experience when the user configures the volume based on the simplification of the use operation.
In a first aspect, an embodiment of the present application provides a method for configuring a volume, where the method includes:
acquiring configuration information of a user aiming at a volume to be created, wherein the configuration information comprises an identifier of the volume to be created and the capacity of the volume to be created;
determining a target storage pool from target storage services according to the capacity of the volume to be created, wherein the target storage pool and the target storage services are bound in advance, and the residual capacity of the target storage pool is not lower than the capacity of the volume to be created;
and creating the volume according to the target storage pool and the identification of the volume to be created.
In some possible embodiments, the method further comprises:
in response to a selection operation of a user aiming at the attributes of the candidate storage services, determining an initial storage service from the candidate storage services, wherein the initial storage service has the attributes corresponding to the selection operation, and the attributes of the initial storage service comprise one or more of thick stock attributes, thin attributes, compression attributes and encryption attributes;
and determining a target storage service from the initial storage services in response to the selection operation of the user aiming at the target storage service.
In some possible embodiments, the method further comprises:
binding at least one storage pool with the target storage service, the at least one storage pool including the target storage pool.
In some possible embodiments, the method further comprises:
acquiring attribute setting information of a user aiming at the target storage service, wherein the attribute setting information represents attributes set by the user for the target storage service, and the attributes comprise one or more of thick spare attributes, simplified attributes, compression attributes and encryption attributes.
In some possible embodiments, the target storage service is fully bound to one or more storage pools of a storage system;
alternatively, the target storage service is completely bound to storage pools of multiple storage systems.
In a second aspect, an embodiment of the present application further provides an apparatus for configuring a volume, where the apparatus includes:
the device comprises a first acquisition module, a second acquisition module and a third acquisition module, wherein the first acquisition module is used for acquiring configuration information of a user aiming at a volume to be created, and the configuration information comprises an identifier of the volume to be created and the capacity of the volume to be created;
a first determining module, configured to determine a target storage pool from a target storage service according to a capacity of the volume to be created, where the target storage pool and the target storage service are bound in advance, and a remaining capacity of the target storage pool is not lower than a capacity of the volume to be created;
and the creating module is used for creating the volume according to the target storage pool and the identification of the volume to be created.
In some possible embodiments, the apparatus further comprises:
the second determining module is used for determining an initial storage service from the candidate storage services in response to a selection operation of a user aiming at the attributes of the candidate storage services, wherein the initial storage service has the attributes corresponding to the selection operation, and the attributes of the initial storage service comprise one or more of thick stock attributes, thin attributes, compression attributes and encryption attributes;
and the third determination module is used for determining the target storage service from the initial storage service in response to the selection operation of the user aiming at the target storage service.
In some possible embodiments, the apparatus further comprises:
a binding module to bind at least one storage pool with the target storage service, the at least one storage pool including the target storage pool.
In some possible embodiments, the apparatus further comprises:
and the second acquisition module is used for acquiring attribute setting information of the user aiming at the target storage service, wherein the attribute setting information represents the attribute set by the user on the target storage service, and the attribute comprises one or more of a thick stock attribute, a simplified attribute, a compression attribute and an encryption attribute.
In some possible embodiments, the target storage service is fully bound to one or more storage pools of a storage system;
alternatively, the target storage service is completely bound to storage pools of multiple storage systems.
In the implementation manner of the embodiment of the present application, the storage pools that correspond to the volumes desired to be configured by the user are automatically screened from the storage pools bound to the storage service, so that the volumes desired to be configured by the user are created based on the storage pools. Specifically, configuration information of a user for a volume to be created may be obtained, where the configuration information includes an identifier of the volume to be created and a capacity size of the volume to be created; then, according to the capacity of the volume to be created, a target storage pool can be determined from the target storage service, wherein the determined residual capacity of the target storage pool is not lower than the capacity of the volume to be created, and the target storage pool and the target storage service are bound in advance; finally, the volume that the user desires to create (configure) may be created based on the target storage pool and the identification of the volume to be created. Therefore, in the process of configuring the volume, the user can only input the identification and the capacity size of the volume to be configured without paying attention to the actual physical volume object, and even after the attribute of the target storage service is preset, the user does not need to configure the attribute of the volume, so that the operation required to be executed by the user in the process of configuring the volume can be effectively simplified, and the use experience of the user can be improved.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments described in the present application, and other drawings can be obtained by those skilled in the art according to the drawings.
FIG. 1 is a schematic diagram of an application scenario in an embodiment of the present application;
FIG. 2 is a flow chart illustrating a method for configuring a volume according to an embodiment of the present application;
FIG. 3 is a schematic diagram of a storage service binding a single storage pool in an embodiment of the present application;
FIG. 4 is a schematic diagram of a storage service binding multiple storage pools in an embodiment of the present application;
FIG. 5 is a schematic diagram of a storage pool in which a storage service binds multiple storage systems in an embodiment of the present application;
fig. 6 is a schematic structural diagram of an apparatus for configuring a roll in an embodiment of the present application.
Detailed Description
Presently, storage systems are typically provided for use by one or more platforms. For example, the platform may be a VMware platform, an OpenStack platform, a kubernets platform, or the like. In general, when configuring a volume using the storage system on these platforms, a user (e.g., a platform administrator, etc.) does not care about the actual physical volume object, and even does not want to set the attributes of the volume, but only needs to determine the information on the usage level, such as the size, identification, etc., of the volume to be configured (or created). Thus, if the storage system is directly interfaced to the platform, it may cause the user to need excessive specific information concerning the physical volume object, such as the need to determine on which storage pool to create the volume, etc., in order to successfully complete the configuration of the volume, which increases the user's actual workload. Moreover, if the user does not understand the storage deeply enough, the user may perform a volume configuration operation that is not in line with the actual needs, such that the finally configured volume may be significantly different from the volume of the expected configuration or the configured volume may fail.
Based on the above, embodiments of the present application provide a method for configuring a volume, which automatically filters out storage pools, from storage pools bound to a storage service, of volumes that meet a configuration desired by a user, so as to create a volume desired to be configured by the user based on the storage pools. Specifically, configuration information of a user for a volume to be created may be obtained, where the configuration information includes an identifier of the volume to be created and a capacity size of the volume to be created; then, according to the capacity of the volume to be created, a target storage pool can be determined from the target storage service, wherein the determined residual capacity of the target storage pool is not lower than the capacity of the volume to be created, and the target storage pool and the target storage service are bound in advance; finally, the volume that the user desires to create (configure) may be created based on the target storage pool and the identification of the volume to be created. Therefore, in the process of configuring the volume, the user can only input the identification and the capacity size of the volume to be configured without paying attention to the actual physical volume object, and even after the attribute of the target storage service is preset, the user does not need to configure the attribute of the volume, so that the operation required to be executed by the user in the process of configuring the volume can be effectively simplified, and the use experience of the user can be improved.
As an example, the embodiment of the present application may be applied to an exemplary application scenario as shown in fig. 1. In this scenario, the storage system 101 may be provided for use by the VMware platform 102. When the administrator 103 of the VMware platform 102 configures (creates) a volume on the VMware platform 102, the user 103 can input the name of the volume to be created and the volume size of the volume to be created on the VMware platform 102; then, the VMware platform 102 may determine, from the target storage service, a target storage pool on the storage system 101 according to the capacity size of the volume to be created, where the determined target storage pool is bound to the storage system 101 in advance, and a remaining capacity size of the target storage pool is not lower than the capacity size to be created; finally, the VMware platform 102 may create a volume on the target storage pool that the user desires to configure, wherein the name of the created volume is the name to be created entered by the user.
It is to be understood that the above scenario is only one example of a scenario provided in the embodiment of the present application, and the embodiment of the present application is not limited to this scenario. For example, in other possible implementations, the embodiments of the present application may also be applied to other platforms, such as an OpenStack platform and a kubernets platform; as another example, in other possible embodiments, the VMware platform 102 can use multiple storage systems, and the like. In summary, the embodiments of the present application can be applied to any applicable application scenario, and are not limited to the scenario examples described above.
In order to make the aforementioned objects, features and advantages of the present application more comprehensible, various non-limiting embodiments accompanying the present application examples are described below with reference to the accompanying drawings. It is to be understood that the embodiments described are only a few embodiments of the present application and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Referring to fig. 2, fig. 2 is a flowchart illustrating a method for configuring a volume according to an embodiment of the present application, where the method may be applied to a storage management platform using a storage system, and the method specifically may include:
s201: the method comprises the steps of obtaining configuration information of a user aiming at a volume to be created, wherein the configuration information comprises an identification of the volume to be created and the capacity size of the volume to be created.
In this embodiment, when a user needs to configure a volume (i.e., create a volume), an identifier of the volume to be created and a size of the volume to be created may be input on a platform, where the identifier of the volume to be created may specifically be a name of the volume to be created, and of course, may also be other identifiers used for distinguishing different volumes. For example, when an administrator of the OpenStack platform needs to create a volume with a name of "volume 01" and a capacity size of 100GB on the OpenStack platform, the administrator may input configuration information of the volume to be created, that is, the name of "volume 01" and the capacity size of 100GB of the volume to be created, on a configuration interface of the OpenStack platform for the volume.
S202: and determining a target storage pool from the target storage service according to the capacity of the volume to be created, wherein the target storage pool and the target storage service are bound in advance, and the residual capacity of the target storage pool is not lower than the capacity of the volume to be created.
In this embodiment, the storage management platform may use at least one storage system. In practical applications, at least one storage system may be added to the storage management platform in advance, and the storage system added to the storage management platform includes at least one storage pool (i.e., storage resource). Then, the storage management platform may specifically establish the volume on the storage pool of one of the storage systems when creating the volume. Further, after at least one storage system is added to the storage management platform, the storage management platform may obtain storage pool information in the storage system through an API (application programming interface) provided externally by the storage system, so as to determine a storage pool that each storage system can use to create a volume. The API Interface may be a REST (representational state transfer) mode or a CLI (Command-Line Interface) mode. Then, the storage pools of the storage system can be instantiated, and unified management of the storage pools is performed by the storage management platform.
In practical applications, in the process of uniformly managing storage pools available for creating volumes in each storage system, one or more storage services may be created, and these storage pools (at least one storage pool) may be further bound with the created storage services, where when multiple storage services are created, the storage pools bound by different storage services may be different from each other. In particular implementations, separate storage spaces may be created on the storage management platform that are logical concepts corresponding to one or more storage pools of the storage system. Then, one or more storage services can be created under the independent storage space, and binding between the storage services and the corresponding storage pools can be completed. Each storage service created may then be provided with an external interface.
Thus, when a user needs to create a volume on the storage management platform, the storage management platform may determine, according to the obtained size of the volume to be created, a target storage pool that meets the user's expectation from at least one storage pool bound by the created storage service according to the size of the volume to be created, so as to complete the volume creation on the target storage pool subsequently. Accordingly, the determined remaining capacity size of the target storage pool is not less than the capacity size of the volume to be created.
It should be noted that, because the created storage service binds to the storage pool, it is perceived to the user that the storage pool exists on the storage service, which can shield the differences on different storage systems and different storage pools, so that the logic is simpler, and the user only needs to pay attention to the name and the size of the volume to be created, so that the user is more convenient to use.
Of course, if there is no storage pool with a remaining capacity size not lower than the capacity size of the volume to be created in the storage pools bound to the target storage service, the user may be prompted that the volume was created (configured) unsuccessfully.
It is noted that in this embodiment, the created storage service may be bound to a storage pool on a storage system. As shown in FIG. 3, storage service A may be bound to storage pools 1-2 in storage system 1, but not to storage pools 1-1 and storage pools 1-3 in the storage system; for storage service B, a binding may be made with storage pool 2-2 in storage system 2, but not with storage pool 2-1 and storage pool 2-3 in the storage system, etc.
Of course, in other possible embodiments, the created storage service may also be bound to multiple storage pools on a storage system. As shown in FIG. 4, the created storage service includes storage service A and storage service B, and storage service A may be bound to storage pools 1-1, 1-2 and 1-3 in storage system 1, respectively, while storage service B may be bound to storage pools 2-1, 2-2 and 2-3 in storage system 2, respectively, and so on.
In addition, in yet other possible embodiments, the created storage service may also be bound to storage pools on multiple storage systems. As shown in FIG. 5, for created storage service A, it may include storage service A1 and storage service A2, where storage service A1 may be bound to storage pools 1-2 and 1-4 in storage system 1 and storage pools 2-1 and 2-3 in storage system 2, respectively; and for storage service A2, it may be bound to storage pool 1-1 and storage pool 1-3 in storage system 1, and to storage pool 2-2 in storage system 2, respectively.
In practical applications, the volume that the user needs to create usually needs to perform attribute setting, for example, the attribute of the volume that the user desires to create is a thin attribute, that is, how much storage space is occupied when the volume is actually used, and how much storage space is allocated to the volume. Then, in a further possible implementation manner, when creating a storage service, a corresponding attribute may also be set for the created storage service, where the set attribute may be one or more of a thick provisioning attribute, a thin attribute, a compression attribute, and an encryption attribute. Thus, when a volume is created on a storage pool bound to the storage service, the created volume also has corresponding attributes. Wherein different storage services may be configured to have different attributes, and of course may be configured to have the same attributes. Thus, when a user desires to create a volume with a particular attribute, a corresponding target storage pool may be determined from the storage services that also have the same attribute, such that a volume with the user-desired attribute may be created based on the target storage pool.
For example, when a user desires to create a volume with a thick provisioning attribute, the storage management platform may locate a storage pool from a storage service that also has a thick provisioning attribute that has a capacity size that is not less than the capacity size of the volume to be created. Thus, after a volume is created based on the located storage pool, the volume has the same attributes as the storage service, i.e., thick provisioning attributes desired by the user.
In particular implementations, the storage management platform may pre-create multiple candidate storage services, which may have different attributes. Then, the user may perform a selection operation with respect to the attribute from the plurality of candidate storage services, for example, the user may input an attribute name, etc., so that the storage management platform can determine the storage service that meets the user attribute expectation. In this way, the storage management platform may determine, in response to a selection operation of a user for an attribute of a candidate storage service, a target storage service from the plurality of candidate storage services, where the determined attribute of the target storage service is an attribute corresponding to the selection operation performed by the user. The storage management platform may then look up the corresponding target storage pool from the determined target storage services to complete the volume creation based on the target storage pool.
For example, the storage management platform may pre-create 10 candidate storage services, wherein each candidate storage service binds one or more different storage pools, and the attributes set by the 10 candidate storage services at the time of creation are not identical. Then, the user may input on the storage management platform that the attribute of the volume to be created is "thick stock attribute" or the user may click a button on the storage management platform to select "thick stock attribute", etc., so that the storage management platform screens out the target storage service with the attribute as thick stock attribute from the 10 storage services based on the selection of the attribute by the user, so that the storage management platform can determine the target storage pool for creating the volume from the storage pools to which the target storage service is bound.
In the above embodiment, the attributes of the storage service are preset when the storage service is created, but in other possible embodiments, the storage service may not be set with the attributes when the storage service is created, and when a user needs to create a volume, the storage attributes are set with the corresponding attributes according to the attribute requirements of the user for the volume. In a specific implementation, after the storage service is created and bound to the storage pool, the storage service may not be set for attributes, and after the user inputs configuration information including an identifier of a volume to be created and a capacity size on the storage management platform and determines the target storage service through storage management, because the determined target storage service does not have a corresponding attribute, the user may also input attribute setting information for the target storage service on the storage management platform, where the attribute setting information represents an attribute set by the user for the target storage service, and of course, the attribute may be one or more of a thick provisioning attribute, a thin attribute, a compressed attribute, and an encrypted attribute. In this way, the storage management platform completes the setting of the attribute of the target storage service based on the attribute setting information input by the user, so that the attribute of the volume created based on the target storage pool bound by the target storage service conforms to the attribute desired to be set by the user.
S203: volumes are created based on the target storage pool and the identity of the volume to be created.
In this embodiment, after determining the target storage pool, the storage management platform may create a corresponding volume based on the target storage pool, and the name of the created volume corresponds to the identifier of the volume to be created, and particularly, when the identifier of the volume to be created is the name of the volume to be created, the name of the created volume is the name of the volume to be created, which is acquired by the storage management platform.
In this embodiment, the storage pools corresponding to the volumes configured as desired by the user are automatically screened from the storage pools bound to the storage service, so that the volumes configured as desired by the user are created based on the storage pools. Specifically, configuration information of a user for a volume to be created may be obtained, where the configuration information includes an identifier of the volume to be created and a capacity size of the volume to be created; then, according to the capacity of the volume to be created, a target storage pool can be determined from the target storage service, wherein the determined residual capacity of the target storage pool is not lower than the capacity of the volume to be created, and the target storage pool and the target storage service are bound in advance; finally, the volume that the user desires to create (configure) may be created based on the target storage pool and the identification of the volume to be created. Therefore, in the process of configuring the volume, the user can only input the identification and the capacity size of the volume to be configured without paying attention to the actual physical volume object, and even after the attribute of the target storage service is preset, the user does not need to configure the attribute of the volume, so that the operation required to be executed by the user in the process of configuring the volume can be effectively simplified, and the use experience of the user can be improved.
In addition, the embodiment of the application also provides a device for configuring the volume. Referring to fig. 6, fig. 6 is a schematic structural diagram illustrating an apparatus for configuring a volume according to an embodiment of the present application, where the apparatus may be applied to a storage management platform, and the apparatus 600 may include:
a first obtaining module 601, configured to obtain configuration information of a user for a volume to be created, where the configuration information includes an identifier of the volume to be created and a size of a capacity of the volume to be created;
a first determining module 602, configured to determine a target storage pool from a target storage service according to a capacity size of the volume to be created, where the target storage pool and the target storage service are bound in advance, and a remaining capacity size of the target storage pool is not lower than a capacity size of the volume to be created;
a creating module 603 configured to create a volume according to the target storage pool and the identifier of the volume to be created.
In some possible embodiments, the apparatus 600 further includes:
and the second determining module is used for determining a target storage service from the candidate storage services in response to a selection operation of a user aiming at the attributes of the candidate storage services, wherein the target storage service has the attributes corresponding to the selection operation, and the attributes of the target storage service comprise one or more of thick stock attributes, thin attributes, compression attributes and encryption attributes.
In some possible embodiments, the apparatus 600 further includes:
a binding module to bind at least one storage pool with the target storage service, the at least one storage pool including the target storage pool.
In some possible embodiments, the apparatus 600 further includes:
and the second acquisition module is used for acquiring attribute setting information of the user aiming at the target storage service, wherein the attribute setting information represents the attribute set by the user on the target storage service, and the attribute comprises one or more of a thick stock attribute, a simplified attribute, a compression attribute and an encryption attribute.
In some possible embodiments, the target storage service is fully bound to one or more storage pools of a storage system;
alternatively, the target storage service is completely bound to storage pools of multiple storage systems.
In this embodiment, a user may only input the identifier and the capacity size of the volume to be configured in the process of configuring the volume, without paying attention to an actual physical volume object, and even after the attribute of the target storage service is preset, the user does not need to configure the attribute of the volume, so that the operation that the user needs to execute in the process of configuring the volume can be effectively simplified, and the use experience of the user can be improved.
In the names of the "first obtaining module", "first determining module", and the like, the "first" mentioned in the embodiments of the present application is only used for name identification, and does not represent the first in sequence. The same applies to "second" etc.
As can be seen from the above description of the embodiments, those skilled in the art can clearly understand that all or part of the steps in the above embodiment methods can be implemented by software plus a general hardware platform. Based on such understanding, the technical solution of the present application may be embodied in the form of a software product, which may be stored in a storage medium, such as a read-only memory (ROM)/RAM, a magnetic disk, an optical disk, or the like, and includes several instructions for enabling a computer device (which may be a personal computer, a server, or a network communication device such as a router) to execute the method according to the embodiments or some parts of the embodiments of the present application.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the apparatus embodiment, since it is substantially similar to the method embodiment, it is relatively simple to describe, and reference may be made to some descriptions of the method embodiment for relevant points. The above-described embodiments of the apparatus are merely illustrative, and the modules described as separate parts may or may not be physically separate, and the parts displayed as modules may or may not be physical modules, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
The above description is only an exemplary embodiment of the present application, and is not intended to limit the scope of the present application.
Claims (10)
1. A method of configuring a volume, the method comprising:
acquiring configuration information of a user aiming at a volume to be created, wherein the configuration information comprises an identifier of the volume to be created and the capacity of the volume to be created;
determining a target storage pool from target storage services according to the capacity of the volume to be created, wherein the target storage pool and the target storage services are bound in advance, and the residual capacity of the target storage pool is not lower than the capacity of the volume to be created;
and creating the volume according to the target storage pool and the identification of the volume to be created.
2. The method of claim 1, further comprising:
and in response to the selection operation of the user aiming at the attributes of the candidate storage services, determining a target storage service from the candidate storage services, wherein the target storage service has the attributes corresponding to the selection operation, and the attributes of the target storage service comprise one or more of thick stock attributes, thin attributes, compression attributes and encryption attributes.
3. The method of claim 2, further comprising:
binding at least one storage pool with the target storage service, the at least one storage pool including the target storage pool.
4. The method of claim 1, further comprising:
acquiring attribute setting information of a user aiming at the target storage service, wherein the attribute setting information represents attributes set by the user for the target storage service, and the attributes comprise one or more of thick spare attributes, simplified attributes, compression attributes and encryption attributes.
5. The method of any of claims 1 to 4, wherein the target storage service is fully bound to one or more storage pools of a storage system;
alternatively, the target storage service is completely bound to storage pools of multiple storage systems.
6. An apparatus for configuring a volume, the apparatus comprising:
the device comprises a first acquisition module, a second acquisition module and a third acquisition module, wherein the first acquisition module is used for acquiring configuration information of a user aiming at a volume to be created, and the configuration information comprises an identifier of the volume to be created and the capacity of the volume to be created;
a first determining module, configured to determine a target storage pool from a target storage service according to a capacity of the volume to be created, where the target storage pool and the target storage service are bound in advance, and a remaining capacity of the target storage pool is not lower than a capacity of the volume to be created;
and the creating module is used for creating the volume according to the target storage pool and the identification of the volume to be created.
7. The apparatus of claim 6, further comprising:
and the second determining module is used for determining a target storage service from the candidate storage services in response to a selection operation of a user aiming at the attributes of the candidate storage services, wherein the target storage service has the attributes corresponding to the selection operation, and the attributes of the target storage service comprise one or more of thick stock attributes, thin attributes, compression attributes and encryption attributes.
8. The apparatus of claim 7, further comprising:
a binding module to bind at least one storage pool with the target storage service, the at least one storage pool including the target storage pool.
9. The apparatus of claim 6, further comprising:
and the second acquisition module is used for acquiring attribute setting information of the user aiming at the target storage service, wherein the attribute setting information represents the attribute set by the user on the target storage service, and the attribute comprises one or more of a thick stock attribute, a simplified attribute, a compression attribute and an encryption attribute.
10. The apparatus of any of claims 6 to 9, wherein the target storage service is fully bound to one or more storage pools of a storage system;
alternatively, the target storage service is completely bound to storage pools of multiple storage systems.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910833570.1A CN110673787A (en) | 2019-09-04 | 2019-09-04 | Volume configuration method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910833570.1A CN110673787A (en) | 2019-09-04 | 2019-09-04 | Volume configuration method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110673787A true CN110673787A (en) | 2020-01-10 |
Family
ID=69076307
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910833570.1A Pending CN110673787A (en) | 2019-09-04 | 2019-09-04 | Volume configuration method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110673787A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112162700A (en) * | 2020-09-18 | 2021-01-01 | 北京浪潮数据技术有限公司 | Storage volume creation method and device, electronic equipment and storage medium |
| CN112882653A (en) * | 2021-01-26 | 2021-06-01 | 北京金山云网络技术有限公司 | Storage volume creation method and device and electronic equipment |
| CN113721850A (en) * | 2021-08-26 | 2021-11-30 | 苏州浪潮智能科技有限公司 | Volume management method, system, device and medium |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109032521A (en) * | 2018-07-25 | 2018-12-18 | 星环信息科技（上海）有限公司 | Storage volume creation method, device, server and storage medium |
-
2019
- 2019-09-04 CN CN201910833570.1A patent/CN110673787A/en active Pending
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109032521A (en) * | 2018-07-25 | 2018-12-18 | 星环信息科技（上海）有限公司 | Storage volume creation method, device, server and storage medium |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112162700A (en) * | 2020-09-18 | 2021-01-01 | 北京浪潮数据技术有限公司 | Storage volume creation method and device, electronic equipment and storage medium |
| CN112882653A (en) * | 2021-01-26 | 2021-06-01 | 北京金山云网络技术有限公司 | Storage volume creation method and device and electronic equipment |
| CN113721850A (en) * | 2021-08-26 | 2021-11-30 | 苏州浪潮智能科技有限公司 | Volume management method, system, device and medium |
| CN113721850B (en) * | 2021-08-26 | 2023-08-25 | 苏州浪潮智能科技有限公司 | Volume management method, system, equipment and medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20210004258A1 (en) | Method and Apparatus for Creating Virtual Machine | |
| US11416307B2 (en) | System and method for processing task resources | |
| JP6542810B2 (en) | System and method for providing a work manager in a multi-tenant application server environment | |
| US10523709B2 (en) | System and method for dynamic security configuration in a multitenant application server environment | |
| CN110673787A (en) | Volume configuration method and device | |
| US20220276904A1 (en) | Job execution with managed compute environments | |
| US9519595B1 (en) | Provisioning resource using quota | |
| US20220244998A1 (en) | Method and apparatus for acquiring device information, storage medium and electronic device | |
| US10877796B1 (en) | Job execution with scheduled reserved compute instances | |
| WO2023045467A1 (en) | Container cpu resource scheduling and isolation method and apparatus, and storage medium and electronic device | |
| US9264339B2 (en) | Hosted network management | |
| CN111831232A (en) | Data storage method and device, storage medium and electronic device | |
| CN111061432A (en) | Service migration method, device, equipment and readable storage medium | |
| KR20220070020A (en) | Network resource management method, system, network device and readable storage medium | |
| US10395219B1 (en) | Location policies for reserved virtual machine instances | |
| US9417997B1 (en) | Automated policy based scheduling and placement of storage resources | |
| EP3698246A1 (en) | Management of a virtual network function | |
| US9521085B1 (en) | Policy-based bandwidth allocation | |
| CN111726241B (en) | Network resource management method, system, network device and readable storage medium | |
| US9710194B1 (en) | Port provisioning based on initiator usage | |
| CN112860421B (en) | Method, apparatus and computer program product for job processing | |
| RU2716742C1 (en) | Method and apparatus for administering object of administered function | |
| US9135457B1 (en) | System and method for recording and applying access privileges in a virtualized environment | |
| CN109218259B (en) | License management method and device, APPLM functional entity and computer readable storage medium | |
| US10013273B1 (en) | Virtual machine termination management |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200110 |