CN117729217B - Cloud platform and bucket management method for object storage service provided by cloud platform - Google Patents

Abstract

The application provides a cloud platform and a barrel management method thereof, wherein the method comprises the following steps: the method comprises the following steps: receiving a dynamic barrel creation instruction input by a tenant, creating a domain name of the dynamic barrel according to the dynamic barrel creation instruction, and associating the domain name of the dynamic barrel with a first static barrel arranged in a first area and a second static barrel arranged in a second area, wherein an object stored in the second static barrel is a trans-regional backup of an object stored in the first static barrel, detecting working states of the first static barrel and the second static barrel, receiving an access request for the domain name of the dynamic barrel sent by a client, and sending an IP address of the first static barrel associated with the domain name of the dynamic barrel or an IP address of the second static barrel associated with the domain name of the barrel to the client according to the working states. Based on the scheme, the client can access the first static bucket or the second static bucket only by accessing the domain name of the dynamic bucket, and the client does not need to consider the working states of the first static bucket and the second static bucket.

Description

Bucket management method for cloud platform and object storage service provided by the same

Technical Field

The present application relates to the field of cloud technology, and in particular to a cloud platform and a bucket management method for an object storage service provided by the cloud platform.

Background Art

Object Storage Service (OBS) is an object-based mass storage service for the public cloud, providing public cloud tenants with massive, secure, highly reliable, and low-cost data storage capabilities.

A bucket is a container for storing objects in OBS. Each bucket has its own storage category, access rights, region, and other attributes. Tenants locate buckets on the Internet through the bucket access domain name. Buckets can be set in different regions based on actual needs.

Buckets have the need for cross-regional data disaster recovery and backup, but the existing OBS service sets different domain names for at least two buckets in the cross-region backup strategy. The client needs to access buckets in different regions based on different domain names. When a bucket in one region fails, the client needs to change the domain name of the bucket to be accessed to access the bucket in another region, which causes inconvenience.

Summary of the invention

The present application provides a cloud platform and a bucket management method thereof, which can improve the convenience of a client accessing a static bucket with cross-region backup.

In a first aspect, the present application provides a method for providing cloud storage services, including: configuring a first data bucket and a second data bucket for a tenant, the first data bucket being set in a first region, the second data bucket being set in a second region, the data object stored in the second data bucket being a cross-region backup of the data object stored in the first data bucket, receiving a third data bucket creation instruction input by the tenant, providing the tenant with a domain name of a third data bucket according to the third data bucket creation instruction, receiving an access request for the domain name of the third data bucket sent by a client, selecting a target data bucket from the first data bucket and the second data bucket according to the working status of the first data bucket and the second data bucket, and returning the IP address of the target data bucket to the client.

This application sets the domain name of a third data bucket for the first data bucket and the second data bucket that have a backup relationship. The client only needs to access the domain name of the third data bucket to access the first data bucket or the second data bucket. The client does not need to consider the working status of the first data bucket and the second data bucket, thereby improving the user experience.

In a possible implementation of the first aspect, configuring a first data bucket and a second data bucket for a tenant is implemented in the following manner: receiving a first data bucket creation instruction input by the tenant, the first data bucket creation instruction is used to indicate a first area specified by the tenant, creating a first data bucket in the first area according to the first data bucket creation instruction, wherein the first data bucket is used to store objects uploaded by the tenant, receiving a second data bucket creation instruction input by the tenant, the second data bucket creation instruction is used to indicate a second area specified by the tenant, and creating a second data bucket in the second area according to the second data bucket creation instruction.

In this implementation, the cloud platform receives a data bucket creation instruction and creates a first and second data bucket. The tenant can first create the first and second data buckets, and then create a domain name for the third data bucket when needed, and set the domain name of the third data bucket to associate with the first and second data buckets. Therefore, the cloud platform can provide a flexible bucket setting method, allowing tenants to further set domain names and associate with multiple data buckets that have been created based on the multiple data buckets that have been created when there is a business need.

In a possible implementation of the first aspect, the method described in the first aspect also includes the following steps: receiving an inter-bucket cross-region configuration instruction input by a tenant, the inter-bucket cross-region configuration instruction is used to indicate the first data bucket as a source bucket and the second data bucket as a target bucket, and copying the objects stored in the source bucket across regions to the target bucket according to the inter-bucket cross-region configuration instruction.

In this implementation, the cloud platform receives inter-bucket cross-region configuration instructions and creates inter-bucket cross-region backups. Tenants can first create two data buckets and then set up the two data buckets for cross-region backup when needed, which can provide a flexible bucket setting method.

In a possible implementation of the first aspect, a target data bucket is selected from the first data bucket and the second data bucket according to the working status of the first data bucket and the second data bucket, including: when the working status of any one of the first data bucket and the second data bucket is abnormal, a data bucket with a normal working status is selected from the first data bucket and the second data bucket as the target data bucket.

In this implementation, the cloud platform is responsible for checking the status of the data bucket to ensure that the IP address of the data bucket with abnormal working status will not be sent to the client.

In a possible implementation of the first aspect, a target data bucket is selected from the first data bucket and the second data bucket according to the working status of the first data bucket and the second data bucket, including: selecting a data bucket specified by the tenant as the target data bucket, or selecting a data bucket that is physically closest to the client as the target data bucket.

In this implementation, when the cloud platform determines that the first and second data buckets are both working properly, the cloud platform can select a data bucket as the target data bucket according to a fixed rule.

In a possible implementation of the first aspect, the method also includes obtaining the tenant's bucket access policy, where the bucket access policy instructs the cloud platform to select the data bucket that is physically closest to the client as the target data bucket when confirming that the working status of the first data bucket and the second data bucket are both normal, or to select the data bucket specified by the tenant as the target data bucket.

In this implementation, the cloud platform provides an expression entry for the tenant, and the tenant inputs a strategy to determine which rule is used to select the data bucket as the target data bucket when both the first and second data buckets work normally.

In a second aspect, the present application provides a data bucket management method for an object storage service, including: receiving a data bucket creation instruction input by a tenant, the data bucket creation instruction indicating a first region and a second region, creating a first data bucket in the first region, and creating a second data bucket in the second region, wherein the object stored in the first data bucket is set as a cross-region backup of the object stored in the second data bucket, providing the tenant with a domain name of a third data bucket, receiving an access request for the domain name of the third data bucket sent by a client, selecting a target data bucket from the first data bucket and the second data bucket according to the working status of the first data bucket and the second data bucket, and returning the IP address of the target data bucket to the client.

The tenant creates a third data bucket by specifying at least two regions. The cloud platform can create the first and second buckets respectively in the specified regions and set up a backup relationship between the data buckets, which can reduce the workload of the tenant.

In a possible implementation of the second aspect, a target data bucket is selected from the first data bucket and the second data bucket according to the working status of the first data bucket and the second data bucket, including: when it is confirmed that the working status of one of the first data bucket and the second data bucket is abnormal, a data bucket with a normal working status is selected from the first data bucket and the second data bucket as the target data bucket.

The cloud platform provides a fault-tolerant function. When the cloud platform finds that the working status of a data bucket is abnormal, it directly returns the IP address of the data bucket in normal working status to the client, which can prevent the client from accessing the abnormal data bucket.

In a possible implementation of the second aspect, a target data bucket is selected from the second data bucket and the third data bucket according to the working status of the first data bucket and the second data bucket, including: when it is confirmed that the working status of the first data bucket and the second data bucket are normal, selecting the first data bucket or the second data bucket as the target data bucket.

In a third aspect, the present application provides a data bucket management method for an object storage service, including: configuring a first data bucket and a second data bucket for a tenant, the first data bucket being set in a first region, the second data bucket being set in a second region, the data object stored in the second data bucket being a cross-region backup of the data object stored in the first data bucket, receiving an access request for the domain name of the first data bucket sent by a client, selecting a target data bucket from the first data bucket and the second data bucket according to the working status of the first data bucket and the second data bucket, and returning the IP address of the target data bucket to the client.

In this implementation, the client does not need to change the domain name to be accessed. The tenant only needs to create a second data bucket on the cloud platform and input cross-region configuration instructions between buckets to the cloud platform. After the cloud platform obtains the access request for the domain name of the first data bucket issued by the client, it returns the IP address of the data bucket with normal working status to the client based on the working status of the first data bucket and the second data bucket. Example 3 is particularly suitable for scenarios where the tenant does not want to change the existing data bucket domain name to the dynamic bucket domain name on the client.

In a possible implementation of the third aspect, a first data bucket and a second data bucket are configured for a tenant, including: receiving a first data bucket creation instruction input by the tenant, the first data bucket creation instruction is used to indicate a first area specified by the tenant, creating a first data bucket in the first area according to the first data bucket creation instruction, wherein the first data bucket is used to store objects uploaded by the tenant, receiving a second data bucket creation instruction input by the tenant, the second data bucket creation instruction is used to indicate a second area specified by the tenant, and creating a second data bucket in the second area according to the second data bucket creation instruction.

In this implementation, the cloud platform receives a data bucket creation instruction and creates a first and second data bucket. The tenant can first create the first and second data buckets, and then create a domain name for the third data bucket when needed, and set the domain name of the third data bucket to associate with the first and second data buckets. Therefore, the cloud platform can provide a flexible bucket setting method, allowing tenants to further set domain names and associate with multiple data buckets that have been created based on the multiple data buckets that have been created when there is a business need.

In a possible implementation of the third aspect, the method also includes: receiving an inter-bucket cross-region configuration instruction input by a tenant, the inter-bucket cross-region configuration instruction is used to indicate the first data bucket as a source bucket and the second data bucket as a target bucket, and copying the objects stored in the source bucket across regions to the target bucket according to the inter-bucket cross-region configuration instruction.

In this implementation, the cloud platform receives the inter-bucket cross-region configuration instructions input by the tenant to replicate the data buckets across regions, thereby achieving disaster recovery.

In a possible implementation of the third aspect, a target data bucket is selected from the first data bucket and the second data bucket according to the working status of the first data bucket and the second data bucket, including: when the working status of one of the first data bucket and the second data bucket is abnormal, a data bucket with a normal working status is selected from the first data bucket and the second data bucket as the target data bucket.

In a possible implementation of the third aspect, a target data bucket is selected from the first data bucket and the second data bucket according to the working status of the first data bucket and the second data bucket, including: selecting a data bucket specified by the tenant as the target data bucket, or selecting a data bucket that is physically closest to the client as the target data bucket.

In this implementation, when the cloud platform determines that the first and second data buckets are both working properly, the cloud platform can select a data bucket as the target data bucket according to a fixed rule.

In a possible implementation of the third aspect, the method also includes obtaining the tenant's bucket access policy, where the bucket access policy instructs the cloud platform to select the data bucket that is physically closest to the client as the target data bucket when confirming that the working status of the first data bucket and the second data bucket are both normal, or to select the data bucket specified by the tenant as the target data bucket.

In this implementation, the cloud platform provides an expression entry for the tenant, and the tenant inputs a strategy to determine which rule is used to select the data bucket as the target data bucket when both the first and second data buckets work normally.

In a fourth aspect, the present application provides a cloud platform, including: a data bucket configuration module, used to configure a first data bucket and a second data bucket for a tenant, the first data bucket is set in a first area, the second data bucket is set in a second area, the data object stored in the second data bucket is a cross-regional backup of the data object stored in the first data bucket, an instruction receiving module, used to receive a third data bucket creation instruction input by the tenant, an instruction processing module, used to provide the tenant with a domain name of a third data bucket according to the third data bucket creation instruction, a data bucket selection module, used to receive an access request for the domain name of the third data bucket sent by the client, and select a target data bucket from the first data bucket and the second data bucket according to the working status of the first data bucket and the second data bucket, and a sending module, used to return the IP address of the target data bucket to the client.

The fourth aspect or any implementation method of the fourth aspect is a method implementation corresponding to the first aspect or any implementation method of the first aspect. The description in the first aspect or any implementation method of the first aspect is applicable to the fourth aspect or any implementation method of the fourth aspect, and will not be repeated here.

In a fifth aspect, the present application provides a cloud platform, including: an instruction receiving module, used to receive a data bucket creation instruction input by a tenant, the data bucket creation instruction indicates a first region and a second region, a data bucket configuration module, used to create a first data bucket in the first region, and a second data bucket in the second region, wherein the object stored in the first data bucket is set as a cross-region backup of the object stored in the second data bucket, a domain name providing module, used to provide the tenant with the domain name of a third data bucket, a data bucket selection module, used to receive an access request for the domain name of the third data bucket sent by a client, and select a target data bucket from the first data bucket and the second data bucket according to the working status of the first data bucket and the second data bucket, and a sending module, used to return the IP address of the target data bucket to the client.

The fifth aspect or any implementation of the fifth aspect is a method implementation corresponding to the second aspect or any implementation of the second aspect. The description in the second aspect or any implementation of the second aspect is applicable to the fifth aspect or any implementation of the fifth aspect, and will not be repeated here.

In a sixth aspect, the present application provides a cloud platform, including: a data bucket configuration module, used to configure a first data bucket and a second data bucket for a tenant, the first data bucket is set in a first region, the second data bucket is set in a second region, the data object stored in the second data bucket is a cross-regional backup of the data object stored in the first data bucket, a data bucket selection module, used to receive an access request for the domain name of the first data bucket sent by the client, and select a target data bucket from the first data bucket and the second data bucket according to the working status of the first data bucket and the second data bucket, and a sending module, used to return the IP address of the target data bucket to the client.

The sixth aspect or any implementation of the sixth aspect is a method implementation corresponding to the third aspect or any implementation of the third aspect. The description in the third aspect or any implementation of the third aspect is applicable to the sixth aspect or any implementation of the sixth aspect, and will not be repeated here.

In a seventh aspect, the present application provides a computer device, comprising: a processor and a memory, the memory being used to store computer execution instructions, and the processor being used to execute the computer execution instructions stored in the memory, so that the computer device implements the method disclosed in the first aspect and any possible implementation manner of the first aspect.

In an eighth aspect, the present application provides a computer storage medium, comprising computer-readable instructions, which, when executed, implement the method disclosed in the first aspect and any possible implementation manner of the first aspect.

In a ninth aspect, the present application provides a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute the method disclosed in the first aspect and any possible implementation of the first aspect.

In the tenth aspect, the present application provides a computer device, comprising: a processor and a memory, the memory being used to store computer execution instructions, and the processor being used to execute the computer execution instructions stored in the memory, so that the computer device implements the method disclosed in the second aspect and any possible implementation method of the second aspect.

In an eleventh aspect, the present application provides a computer storage medium comprising computer-readable instructions, which, when executed, implement the method disclosed in the second aspect and any possible implementation manner of the second aspect.

In a twelfth aspect, the present application provides a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute the method disclosed in the second aspect and any possible implementation of the second aspect.

In the thirteenth aspect, the present application provides a computer device, which includes: a processor and a memory, the memory being used to store computer execution instructions, and the processor being used to execute the computer execution instructions stored in the memory, so that the computer device implements the method disclosed in the third aspect and any possible implementation method of the third aspect.

In a fourteenth aspect, the present application provides a computer storage medium comprising computer-readable instructions, which, when executed, implement the method disclosed in the third aspect and any possible implementation of the third aspect.

In a fifteenth aspect, the present application provides a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute the method disclosed in the third aspect and any possible implementation of the third aspect.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 is a schematic diagram of the logical architecture of an object storage service;

FIG2 is a schematic diagram of the system architecture of the object storage system;

3 is a schematic diagram of the architecture of an object storage system provided with a cross-region replication service according to an embodiment of the present invention;

FIG4 is a data interaction diagram of an object storage system according to an embodiment of the present invention;

5 is a flow chart of a bucket management method of a cloud platform according to an embodiment of the present invention;

6a to 6i are schematic diagrams of a console configuration interface provided by a cloud platform according to an embodiment of the present invention;

7 is another flow chart of the bucket management method of the cloud platform according to an embodiment of the present invention;

8 is another schematic diagram of a console configuration interface provided by a cloud platform according to an embodiment of the present invention;

FIG9 is another flow chart of a bucket management method of a cloud platform according to an embodiment of the present invention;

10 is another schematic diagram of a console configuration interface provided by a cloud platform according to an embodiment of the present invention;

11 is a schematic diagram of connections of data centers in an object storage system according to an embodiment of the present invention;

FIG12 is a schematic diagram of the structure of a storage node according to an embodiment of the present invention;

FIG. 13 is a schematic diagram of the structure of another storage node according to an embodiment of the present invention.

FIG14 is a schematic diagram of a device structure of a cloud platform according to an embodiment of the present invention;

FIG15 is a schematic diagram of another device structure of a cloud platform according to an embodiment of the present invention;

FIG16 is a schematic diagram of another device structure of a cloud platform according to an embodiment of the present invention;

FIG. 17 is a schematic diagram of the device structure of a computer device according to an embodiment of the present invention.

DETAILED DESCRIPTION

The technical solutions in the embodiments of the present invention will be described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

In order to facilitate understanding of the embodiments of the present application, first, some terms involved in the present application are explained.

Cloud platform: It can provide pages related to public cloud services for tenants to remotely access public cloud services. Tenants can log in to the cloud platform on the public cloud access page using a pre-registered account and password. After a successful login, they can select and purchase the corresponding public cloud services on the public cloud access page, such as OBS services, virtual machine services, container services, etc. For OBS services, tenants can further configure OBS services through the configuration interface or application programming interface (API) provided on the public cloud access page, such as creating buckets, configuring bucket access policies, uploading objects to buckets from the tenant's local computer via the Internet, and other bucket-specific operations.

Bucket: A container for storing objects in OBS. Object storage provides a flat storage method based on buckets and objects. All objects in a bucket are at the same logical level, eliminating the multi-level tree directory structure in the file system. Each bucket has its own storage category, access rights, region, and other attributes. Tenants can create buckets with different storage categories and access rights in different regions (described in detail below), and configure more advanced attributes to meet the storage requirements of different scenarios.

In OBS, bucket names are globally unique and cannot be modified. That is, a bucket created by a tenant cannot have the same name as other buckets that the tenant has created, nor can it have the same name as buckets created by other tenants. The region to which a bucket belongs cannot be modified after it is created. When each bucket is created, a default bucket access list ACL (Access Control List) is generated. Each item in the ACL list contains what permissions are granted to the authorized tenant, such as read permissions, write permissions, etc. Tenants can only operate on buckets, such as create, delete, display, and set bucket ACLs, if they have the corresponding permissions on the bucket.

Tenants can log in to the cloud platform using their accounts, and can create multiple buckets through the configuration interface or API on the public cloud access page provided by the cloud platform. There is no limit on the total number and size of objects stored in each bucket, and tenants do not need to consider the scalability of data. OBS is a service based on the REST (Representational State Transfer) style and the hypertext transport protocol (HTTP) and the hypertext transfer protocol secure (HTTPS) protocols. Tenants can locate bucket resources through the Uniform Resource Locator (URL, also referred to as the domain name in the embodiment of the present invention). The relationship between buckets and objects in OBS is shown in Figure 1. Figure 1 is a schematic diagram of the logical architecture of the object storage service. As shown in Figure 1, each bucket can include multiple objects (described in detail below), and the objects between buckets are isolated from each other. Tenants purchase the object storage service remotely by operating the client, and the object storage service provides buckets to tenants. Specifically, the domain name of the bucket can be provided, and the tenant can operate the client to access the domain name, so that data can be uploaded to the bucket and downloaded from the bucket, wherein the uploaded data is stored in the bucket in the form of objects.

Static bucket: In the embodiment of the present invention, the static bucket refers to the bucket provided by the above object storage service.

Dynamic bucket: In the embodiment of the present invention, the dynamic bucket is a virtual bucket. The function of the dynamic bucket is to associate multiple static buckets. The dynamic bucket is set with the domain name of the dynamic bucket. After the client accesses the domain name of the dynamic bucket, the cloud platform can return the IP address of a static bucket among multiple static buckets to the client.

It is worth noting that the static bucket and dynamic bucket described in the present invention can be called data buckets. The static bucket and dynamic bucket are respectively a specific implementation of the data bucket, where "static" means that the data bucket is set on a physical storage device, such as the physical disk described below, and can be used to store objects. "Dynamic" means that the data bucket is not set on a physical storage device, and the dynamic bucket is not used to store objects. It only provides a domain name for the client to access the domain name, so as to access the object stored in the corresponding static bucket according to the domain name. Object: It is the basic unit of data storage in OBS. An object is actually a collection of data of a file and its related attribute information (metadata). The data uploaded by the tenant to OBS is stored in the bucket in the form of an object. The object includes three parts: key value Key, source data Metadata, and data Data. Key: Key value, that is, the name of the object, for example, a character sequence with a length greater than 0 and not more than 1024 encoded by UTF-8. Each object in a bucket has a unique object key value. Metadata: Metadata, that is, the description information of the object, including system metadata and tenant metadata. These metadata are uploaded to the object storage service in the form of key-value pairs. System metadata is automatically generated by the object storage service and is used when processing object data. It includes date, content length, last modification time, MD5 encrypted content, etc. Tenant metadata is specified by the tenant when uploading an object to a bucket. It is the tenant's customized object description information. Data: Data refers to the data content uploaded by the tenant.

Usually, objects can be managed as files. However, to make it easier for tenants to manage data, the object storage service provides a way to simulate folders: by adding "/" to the name of the object, for example, "test/123.jpg", "test" is simulated as a folder, and "123.jpg" is simulated as the file name under the "test" folder. In fact, the object name (Key) is "test/123.jpg" and the data is the 123.jpg file itself.

When a tenant uploads an object, he or she can specify the storage category of the object. If not specified, the default is the same as the storage category of the bucket. After uploading, the storage category of the object can be modified. The bucket can be accessed through a client, which can be, for example, a browser used locally by the tenant or a dedicated client provided by the cloud platform. For example, the tenant can access the bucket through a browser set in the local computer. After entering the account and passing the verification, the tenant can use the browser to upload objects to the bucket, or delete objects in the bucket, etc., where the local computer is connected to the Internet.

Furthermore, the client can also be set up in the virtual machine, container, or bare metal server provided by the public cloud service, and access the bucket through the public cloud internal network.

It is worth noting that any device that can access a bucket through the Internet or a public cloud internal network can be referred to as a client in an embodiment of the present invention.

Region: Region is used to describe the geographical location of a data center. Tenants can create cloud resources provided by public cloud services in a specific region. When selecting a region, tenants need to consider the following factors:

Geographical location: Generally, it is recommended that tenants who create cloud resources select a region close to the target tenants who use the cloud resources, so as to reduce network latency and increase access speed. The various regions include South China, North China, East China, Southwest China, etc. For example, when a tenant selects South China, the cloud resources created by the tenant (such as the static bucket involved in the embodiment of the present invention) are set in the data center in South China. Tenants who have business in Africa can select the "Africa" region. Tenants who have business in Europe can select the "Europe" region.

Price: The price of cloud resources in different regions may vary.

In an embodiment of the present invention, tenants can create buckets in different regions and upload objects to different buckets for multi-region backup, which can effectively prevent the problem of objects in the bucket being unable to be accessed normally due to power outages, network outages or other emergencies in a data center in one region.

Object Storage Device (OSD), the basic storage unit of the object storage system, is set on the physical disk, specifically a fixed-size storage space of the physical disk. The object storage system manages the physical disks of multiple storage nodes in the form of OSD.

Please refer to Figure 2 below, which is a schematic diagram of the architecture of an object storage system. In the embodiment shown in Figure 2, the object storage system includes a data center 1 set in region 1, a data center 2 set in region 2, and a cloud platform 10. In this architecture, the tenant can create static bucket 1 and static bucket 2 in the cloud platform 10 in advance. Static bucket 1 is set in region 1, and static bucket 2 is set in region 2. The domain name of static bucket 1 is bucket1.region1.com, and the IP address of static bucket 1 is IP1. The domain name of static bucket 2 is bucket2.region2.com, and the IP address of static bucket 2 is IP2. Further, the tenant can set the objects in static bucket 1 to be copied across regions to static bucket 2 for backup.

In the domain name bucket1.region1.com of static bucket 1, bucket1 is the bucket name of static bucket 1, and region1 is region 1 where static bucket 1 is located. Similarly, in the domain name bucket2.region2.com of static bucket 2, bucket2 is the bucket name of static bucket 2, and region2 is region 2 where static bucket 2 is located.

Specifically, after the static bucket 1 is created, the cloud platform 10 registers the correspondence 1 between the domain name bucket1.region1.com and IP1 in the domain name service node 30, and after the static bucket 2 is created, the cloud platform 10 registers the correspondence 2 between the domain name bucket2.region2.com and IP2 in the domain name service node 30.

Optionally, the domain name service node 30 can be implemented by at least one top-level domain name service node and multiple second-level domain name service nodes set in different regions. In the above domain name registration process, the top-level domain name service node records the correspondence between region1 and the second-level domain name service node 1 set in region 1, and records the correspondence between region2 and the second-level domain name service node 2 set in region 2. The second-level domain name service node 1 records the correspondence between bucket1 and IP1, and the second-level domain name service node 2 records the correspondence between bucket2 and IP2. Among them, the cloud platform 10 can be set in data center 1 or data center 2. Data center 1 and data center 2 are data centers belonging to the cloud service provider. Further, the cloud platform 10 can also be set in other data centers of the cloud service provider.

Based on the architecture shown in FIG2 , the process of client 20 accessing static bucket 1 is as follows:

Step 1: The client 20 sends an access request for the domain name bucket1.region1.com to the domain name service node 30 .

Step 2: The domain name service node 30 obtains IP1 according to the correspondence 1, and sends IP1 to the client 20.

Optionally, when the domain name service node 30 is jointly implemented by at least one top-level domain name service node and multiple second-level domain name service nodes set in different regions, the top-level domain name service node sends the access request to the second-level domain name service node 1 according to the pre-recorded correspondence between region1 and the second-level domain name service node 1 set in region 1, and the second-level domain name service node 1 sends IP1 to the client 20 according to the pre-recorded correspondence between bucket1 and IP1.

Step 3: Client 20 accesses static bucket 1 according to IP1.

Specifically, client 20 sends an access request for IP1 to static bucket 1, the destination address of the IP message is IP1, the source address is the IP address of client 20, and the payload carries a read/write request for static bucket 1.

In this embodiment, if static bucket 1 fails, client 20 cannot access the objects stored in static bucket 1. Since the objects stored in static bucket 2 are cross-regional replication backups of static bucket 1, as a disaster recovery solution, client 20 can access the objects stored in static bucket 2, thereby ensuring that client 20 can access the required objects from static bucket 2 even if static bucket 1 fails.

Specifically, the tenant can operate the client 20 to send an access request for the domain name bucket2.region2.com to the domain name service node 30. The domain name service node 30 obtains IP2 according to the correspondence 2, sends IP2 to the client 20, and the client accesses the static bucket 2 according to IP2.

Optionally, when the domain name service node 30 is jointly implemented by at least one top-level domain name service node and multiple second-level domain name service nodes set in different regions, the top-level domain name service node sends the access request to the second-level domain name service node 2 according to the pre-recorded correspondence between region2 and the second-level domain name service node 2 set in region 2, and the second-level domain name service node 1 sends IP2 to the client 20 according to the pre-recorded correspondence between bucket2 and IP2.

In the above scheme, even if static bucket 2 is set up as a cross-regional replication backup of static bucket 1, in the event of a failure in static bucket 1, such as a power outage in data center 1, a downtime of the storage node where static bucket 1 is located (described in detail below), or other situations that affect the normal operation of static bucket 1, tenants using client 20 can clearly feel that the data in static bucket 1 cannot be accessed. For example, if client 20 is stuck, the tenant needs to reset client 20 to send an access request for another domain name bucket2.region2.com. In this way, the stuck client 20 may cause the operating system where client 20 is located to crash, and the tenant needs to manually set client 20 and change the domain name to be accessed (from bucket1.region1.com to bucket2.region2.com) by manual memory. This will result in a poor tenant experience.

For example, assume that client 20 is set in a server for providing a shopping website. The server is provided with a shopping website. The log data of tenants visiting the shopping website needs to be regularly sent to static bucket 1 for storage in the form of objects, and the objects of static bucket 1 are regularly or in real time copied to static bucket 2 for cross-regional backup. When static bucket 1 fails, client 20 cannot send log data to static bucket 1. At this time, client 20 needs to send a domain name access request for bucket2.region2.com, obtain IP2 of static bucket 2 from domain name service node 30, and access static bucket 2 according to IP2.

Optionally, the client 20 may obtain IP2 of the static bucket 2 from the domain name service node 30 in advance. When the static bucket 1 fails, there is no need to access the domain name service node 30 again, and the static bucket 2 can be accessed directly by switching from IP1 to IP2.

Regardless of which of the above methods is used, the client 20 needs to pay attention to the working status of the static bucket 1. When its working status is abnormal, it switches to access the static bucket 2. The above operations need to be manually performed by the tenant, which results in a poor user experience and will cause delays, affecting the normal operation of the shopping website.

In view of the above technical problems, an embodiment of the present invention provides an object storage system, which can be specifically referred to in FIG3 . FIG3 is a schematic diagram of the architecture of the object storage system according to an embodiment of the present invention. Compared with the system shown in FIG2 , the cloud platform 10 of FIG3 provides a dynamic bucket configuration interface to create a dynamic bucket with a domain name (hereinafter referred to as the domain name of the dynamic bucket, such as bucket3.obs.huaweicloud.com) according to the request of the tenant, and set the dynamic bucket to be associated with the static bucket 1 and the static bucket 2 specified by the tenant, and the cloud platform 10 registers the correspondence 3 between bucket3.obs.huaweicloud.com and its own IP address IP0 to the domain name service node 30, wherein the dynamic bucket is a virtual bucket, and its bucket name and the domain name of the dynamic bucket are recorded in the cloud platform 10. The cloud platform 10 further records the correspondence between the bucket name of the dynamic bucket and the bucket names, regions and IP addresses of static buckets 1 and 2, for example, Table 1 can be recorded:

It is worth noting that the cloud platform 10 may also record the correspondence between the bucket name of the dynamic bucket and the bucket names, regions and IP addresses of static bucket 1 and static bucket 2 in other ways, and the embodiment of the present invention is not limited to this.

Furthermore, after creating the dynamic bucket, the cloud platform 10 starts status detection for the static bucket 1 and the static bucket 2 .

The workflow of the object storage system shown in FIG. 3 can be specifically described in conjunction with FIG. 4 . FIG. 4 is a data interaction diagram of the object storage system according to an embodiment of the present invention. The method shown in FIG. 4 assumes that the tenant logs in to the cloud platform 10 and creates static buckets 1 and 2, dynamic buckets through the cloud platform 10, and configures the dynamic buckets to be associated with static buckets 1 and 2. As shown in FIG. 4 , the workflow of the object storage system is as follows:

Step S201: the cloud platform 10 starts status detection for the static bucket 1.

Among them, the cloud platform 10 periodically (for example, every 10ms) sends a status detection request to the static bucket 1 (specifically, to the storage node where the static bucket 1 is located, which will be introduced in detail below). If a response is obtained from the storage node where the static bucket 1 is located, it is confirmed that the status of the static bucket 1 is normal, otherwise it is confirmed that it has failed.

For example, the status detection request is a heartbeat message. The cloud platform 10 periodically sends a heartbeat message to the storage node where the static bucket 1 is located. Each time the storage node receives a heartbeat message, it returns a response message. When the cloud platform 10 detects the corresponding response message, it confirms that the static bucket 1 is normal. When the corresponding response message is not detected, it is confirmed that it has failed (in actual applications, a threshold can be set. When the response message corresponding to a preset number of heartbeat messages is not detected, it is confirmed that the static bucket 1 has failed).

Step S202: the cloud platform 10 starts status detection for the static bucket 2.

The detection method of static bucket 2 is similar to step S201, and will not be described in detail here. In steps S201 and S202, the cloud platform records the working status of static bucket 1 and static bucket 2, and updates the recorded working status according to the latest query result.

Step S203: the client 20 sends an access request 1 for the domain name bucket3.obs.huaweicloud.com of the dynamic bucket to the domain name service node 30 .

In this step, the tenant can operate the client 20 to send the access request. The client 20 provides a user interaction interface, and receives the domain name of the dynamic bucket input by the tenant through the user interaction interface, thereby triggering the client 20 to start sending the access request for the domain name of the dynamic bucket.

It is worth noting that the source IP address of the access request is the IP address of the client 20, for example, 114.115.0.2.

Step S204 : the domain name service node 30 forwards the access request 1 to the cloud platform 10 .

Prior to this step, during the process of cloud platform 10 creating a dynamic bucket, a correspondence 3 between the IP address IP0 of cloud platform 10 and the domain name bucket3.obs.huaweicloud.com of the dynamic bucket is registered in domain name service node 30. When domain name service node 30 receives an access request 1 for bucket3.obs.huaweicloud.com sent by client 20, it determines IP0 according to correspondence 3 and forwards the access request 1 to cloud platform 10 corresponding to IP0.

Step S205: The cloud platform 10 confirms the IP1 of the static bucket 1 and the IP2 of the static bucket 2, and returns IP1 to the client 20 according to the bucket access policy.

Specifically, the cloud platform 10 determines the dynamic bucket (whose bucket name is bucket3) based on the domain name of the dynamic bucket bucket3.obs.huaweicloud.com, queries Table 1, confirms that the dynamic bucket is associated with static bucket 1 and static bucket 2, determines the IP1 of static bucket 1 and the IP2 of static bucket 2 from Table 1, and selects the IP address of the static bucket with normal working status according to the working status of static bucket 1 and static bucket 2 recorded in steps S201 and S202, and returns the IP address to the client 20.

The cloud platform 10 confirms the IP address of the client 20 according to the source IP address carried in the access request 1, and sends a message carrying the IP address of a static bucket in normal working status to the IP address.

For example, when the working status of static bucket 1 is normal and the working status of static bucket 2 is abnormal, the IP address IP1 of static bucket 1 is selected as the target IP address and returned to the client 20 .

When the working status of static bucket 2 is normal and the working status of static bucket 1 is abnormal, the IP address IP2 of static bucket 2 is selected as the target IP address and returned to the client 20 .

Further, when the cloud platform 10 detects that the working status of static bucket 1 and the working status of static bucket 2 are both normal, the IP address IP1 of static bucket 1 is preferentially selected as the target IP address and returned to the client 20 .

When the cloud platform 10 detects that the working status of static bucket 1 and the working status of static bucket 2 are both normal, the IP address IP2 of static bucket 2 is preferentially selected as the target IP address and returned to the client 20 .

The above solution can ensure that when a static bucket fails, the client 20 can access another static bucket that serves as a backup of the static bucket. Even if a static bucket fails, the failure is transparent to the client 20 and will not affect the normal working status of the client 20.

Moreover, when all static buckets are not faulty, the static bucket to be accessed can be selected according to the tenant's needs. Furthermore, in the scenario where one dynamic bucket is associated with more than two static buckets, the tenant can also set a priority order for the static buckets to be accessed.

The cloud platform 10 may provide the tenant with options or an input interface, and select, based on the tenant's input, which static bucket's IP address should be returned first when all static buckets are not faulty.

When the cloud platform 10 detects that the working status of static bucket 1 and the working status of static bucket 2 are both normal, it selects a target static bucket from static bucket 1 and static bucket 2, and returns the IP address of the target static bucket as the target IP address to the client 20, where the area where the target static bucket is located is the area in area 1 and area 2 that is physically closest to the client 20.

For example, the cloud platform 10 may record the physical distance 1 between the area where the preset IP address segment range is located and area 1, as well as the physical distance 2 between the area where the preset IP address segment range is located and area 2. When it is confirmed that the IP address of the client 20 (the IP address carried in the source IP address of the access request 1 in step S203) belongs to the preset IP address segment range, a static bucket located in the area corresponding to the smallest value of physical distance 1 and physical distance 2 is selected from static bucket 1 and static bucket 2 as the target static bucket.

Further, see Table 2 below:

The cloud platform 10 records Table 2 in advance, and analyzes that the IP address 114.115.0.2 of the client 20 is located in the range segment 114.115.0.0/16, and obtains the physical distance 18 from the range segment to area 1, and the physical distance 7 from the range segment to area 2. After comparing the sizes of 18 and 7, the cloud platform 10 determines that the physical distance from the client 20 to area 2 is the shortest, and uses the static bucket 2 as the target static bucket, and returns the IP2 of the static bucket 2 to the client 20, so that the client 20 can access the static bucket 2 in area 2 nearby, which can shorten the network transmission time and improve the tenant experience.

The above solution can ensure that when all static buckets are not faulty, the physical distance between the client and the static bucket to be accessed is the shortest, which can shorten the network transmission distance.

The cloud platform 10 may provide the tenant with options or an input interface, and based on the tenant's input selection, when all static buckets are not faulty, the IP address of the static bucket that is closest to the client 20 in physical distance is returned preferentially.

In this step, it is assumed that the working status of static bucket 1 is abnormal and the working status of static bucket 2 is normal. At this time, the cloud platform 10 returns the IP address IP2 of static bucket 2 to the client 20.

Step S206 : the client 20 sends an access request 2 to the static bucket 2 .

Since in step S205 , the client 20 obtains the IP2 of the static bucket 2 from the cloud platform 10 , the client 20 sends an access request 2 for the IP2 to the static bucket 2 .

The destination IP address of access request 2 is IP2, which may carry, for example, data to be uploaded or instructions for downloading data.

Step S207: Static bucket 2 returns a response according to access request 2. In the case where access request 1 carries data to be uploaded, static bucket 2 receives and stores the data to be uploaded from client 20. In the case where the bucket access request carries a download data instruction, static bucket 2 sends the object specified by the download data instruction to client 20.

It is worth noting that for the sake of ease of explanation, in this step, static bucket 2 returns a response to client 20 as the main body. In actual applications, it is actually the storage node where static bucket 2 is located that returns a response to client 20 as the main body. The relationship between the storage node and the static bucket will be explained in detail below.

In the above embodiments, it is assumed that static bucket 1, static bucket 2, and dynamic bucket are all set up in the cloud platform 10. The system disclosed in the above embodiments is based on the operation of static bucket 1, static bucket 2, and dynamic bucket. Therefore, the client only needs to access the domain name of the dynamic bucket to obtain the IP address of the appropriate static bucket. However, static bucket 1, static bucket 2, and dynamic bucket in the embodiments of the present invention can be opened by the cloud platform 10 to tenants for their own selection, creation, and configuration, so that tenants can manage static buckets according to their own needs. The above configuration process is specifically described below.

Bucket Management Method

To further explain the bucket management method implemented by the cloud platform 10, please refer to Example 1:

For details, please refer to FIG. 5 and FIG. 6a to FIG. 6i. FIG. 5 is a flow chart of a bucket management method of a cloud platform according to an embodiment of the present invention. FIG. 6a to FIG. 6i are schematic diagrams of a console configuration interface provided by a cloud platform according to an embodiment of the present invention. As shown in FIG. 5, the method includes the following steps:

Step S301: receiving a static bucket creation instruction 1 input by a tenant, and creating a static bucket 1 in region 1 according to the static bucket creation instruction 1.

For example, the cloud platform 10 may receive a static bucket creation instruction 1 input by a tenant through a configuration interface or an API. The static bucket creation instruction is used to indicate the region 1 and bucket name bucket1 specified by the tenant, and the cloud platform 10 creates a static bucket 1 in region 1 according to the static bucket creation instruction 1.

In this embodiment, a configuration interface implementation is used for detailed description.

Reference can be made in conjunction with Figure 6a. As shown in Figure 6a, the cloud platform 10 provides a console configuration interface 1. When the tenant selects the "Static Bucket Creation" option in the console configuration interface 1, the cloud platform 10 provides a console configuration interface 2 shown in Figure 6b. The tenant enters the name of the static bucket to be created "bucket1", enters the bucket type "static bucket", and enters the region of the static bucket "region 1", and then clicks the "Confirm" option. At this time, the cloud platform 10 creates a static bucket 1 with the bucket name "bucket1" in the data center 1 of region 1 (as shown in Figure 2) according to the above-mentioned static bucket creation instruction entered by the tenant. Correspondingly, the cloud platform 10 configures the domain name bucket1.region1.com and IP1 for static bucket 1.

Further, after creating static bucket 1, the tenant uploads an object to static bucket 1, where the object is the data uploaded by the tenant.

Step S302: receiving a static bucket creation instruction 2 input by the tenant, and creating a static bucket 2 in area 2 according to the static bucket creation instruction 2.

For example, the cloud platform 10 may receive a static bucket creation instruction 2 input by a tenant through a configuration interface or an API. The static bucket creation instruction 2 is used to indicate the region 2 and bucket name bucket2 specified by the tenant, and the cloud platform 10 creates a static bucket 2 in region 2 according to the static bucket creation instruction 2.

Similarly, the tenant can create a static bucket 2 in the console configuration interface 3 shown in Figure 6c. The cloud platform 10 creates a static bucket 2 with the bucket name "bucket2" in the data center 2 of region 2 (as shown in Figure 2) according to the static bucket creation instruction 2 input by the tenant. Correspondingly, the cloud platform 10 configures the domain name bucket2.region2.com and IP2 for the static bucket 2.

Furthermore, in the process of creating a static bucket, the cloud platform 10 may register the correspondence 1 between bucket1.region1.com and IP1 and the correspondence 2 between bucket2.region2.com and IP2 in the domain name service node 30 shown in FIG. 2 .

In steps S301 and S302 , the cloud platform 10 configures static bucket 1 and static bucket 2 for the tenant.

Step S303: the cloud platform 10 receives the inter-bucket cross-region configuration instruction input by the tenant, and copies the object stored in the source bucket to the target bucket across regions according to the inter-bucket cross-region configuration instruction.

The cloud platform 10 may receive inter-bucket cross-region configuration instructions input by the tenant through a configuration interface or an API, where the inter-bucket cross-region configuration instructions are used to indicate static bucket 1 as a source bucket and static bucket 2 as a target bucket.

For example, when the tenant selects the "Cross-region replication policy creation" option in the console configuration interface 1, the cloud platform 10 provides the console configuration interface 4 shown in Figure 6e. The tenant enters the name of static bucket 1 "bucket1" in the "Source bucket" option of the console configuration interface 4, enters the name of static bucket 2 "bucket2" in the "Target bucket" option of the console configuration interface 4, and clicks the "Confirm" option. At this time, the cloud platform 10 will periodically synchronize and replicate the objects of static bucket 1 to static bucket 2 across regions at predetermined time intervals, so that the objects stored in static bucket 1 and the objects stored in static bucket 2 are completely consistent.

Whenever a new object is uploaded to static bucket 1 or an object is modified, the new object or the modified object can be synchronously stored in static bucket 2 by the cloud platform 10 .

Step S304: the cloud platform 10 receives the dynamic bucket creation instruction input by the tenant, creates a domain name of the dynamic bucket according to the dynamic bucket creation instruction, and associates the domain name of the dynamic bucket with static bucket 1 set in area 1 and static bucket 2 set in area 2.

Among them, the cloud platform 10 can receive the dynamic bucket creation instruction input by the tenant through the configuration interface or API, and the dynamic bucket creation instruction is used to instruct the cloud platform 10 to create a dynamic bucket with a domain name of the dynamic bucket, and associate the domain name of the dynamic bucket with the static bucket 1 set in area 1 and the static bucket 2 set in area 2.

For example, referring to the console configuration interface 5 shown in Figure 6g, the tenant enters the bucket name "bucket3" of the dynamic bucket, and enters the name "bucket1" of the static bucket 1 and the name "bucket2" of the static bucket 2 associated with it in the "Associated Bucket" input box, and clicks the "Confirm" option to complete the creation of the dynamic bucket.

Optionally, the dynamic bucket creation instruction may also specify whether the client should access static bucket 1 or static bucket 2 first when both static bucket 1 and static bucket 2 are working normally, or may specify whether the client should access the static bucket with the shortest distance based on the distance between the static bucket and the client.

Specifically, in combination with the console configuration interface 1 shown in Figure 6h, after the tenant clicks the "Bucket Access Policy Creation" option, the cloud platform 10 provides the console configuration interface 6 shown in Figure 6i. The tenant enters the name of the dynamic bucket "bucket3" in the "Bucket Name" input box of the interface, and selects the "Nearby Policy" option in the bucket access policy input box to complete the policy configuration.

It is worth noting that the interface shown in FIG. 6i does not show other options, such as giving priority to accessing bucket 1 or giving priority to accessing bucket 2, which are also options provided to tenants by the bucket access policy.

Step S305: the cloud platform 10 detects the working status of static bucket 1 and static bucket 2.

The cloud platform 10 may periodically detect the working status of the static bucket 1 and the static bucket 2, record the working status of the static bucket 1 and the static bucket 2, and periodically update the recorded working status.

Step S305: the cloud platform 10 receives an access request 1 for the domain name of the dynamic bucket sent by the client, and sends the IP1 of the static bucket 1 associated with the domain name of the dynamic bucket or the IP2 of the static bucket 2 associated with the bucket domain name to the client according to the working status.

For example, the cloud platform 10 determines IP1 and IP2 associated with the dynamic bucket based on the access request 1 (as described in Figure 3 and the corresponding embodiment). When the working status of one of the static bucket 1 and the static bucket 2 is abnormal, the cloud platform 10 sends the IP address of the static bucket with normal working status selected from the static bucket 1 and the static bucket 2 to the client 20.

When the dynamic bucket creation instruction also includes the bucket access policy selected or input by the tenant, the cloud platform 10 sends the IP address of the static bucket 1 or static bucket 2 specified by the tenant to the client 20 after confirming that the working status of the static bucket 1 and the static bucket 2 are normal.

Optionally, when the bucket access policy is the "proximity policy", the cloud platform sends the IP address of the static bucket that is physically closest to the client 20 after confirming that the working status of static bucket 1 and static bucket 2 are both normal.

In summary, the cloud platform 10 of the embodiment of the present invention provides an input interface, such as a configuration interface or API, for tenants to manage buckets, thereby meeting the tenants' needs to implement cross-regional backup of data in buckets according to their own needs. In addition, tenants can also create dynamic buckets to manage them with at least two static buckets. The client only needs to access the domain name of the dynamic bucket to address the appropriate static bucket and access the required data. The client does not need to know whether the working status of the static bucket is normal. The cloud platform 10 detects the working status of the static bucket, and the tenant does not need to care about which static bucket has an abnormal working status, so it is more convenient for the tenant.

In implementation one, the tenant creates a static bucket and a dynamic bucket respectively, and sets the dynamic bucket to be associated with the static bucket. However, in other implementations of the bucket management method, unlike the need to create a static bucket in implementation one, the tenant does not need to create a static bucket on the cloud platform 10 first. Instead, the tenant can directly create a dynamic bucket on the cloud platform 10 and specify at least two regions. The cloud platform 10 can create multiple static buckets associated with the dynamic bucket in the background and set the domain name of the dynamic bucket, and there is no need to set the domain name of the static bucket for the static bucket.

To further explain the bucket management method implemented by the cloud platform 10, please refer to Example 2:

Please refer to FIG. 7, which is another flow chart of the bucket management method according to an embodiment of the present invention. As shown in FIG. 7, the method includes the following steps:

S401: The cloud platform 10 receives a dynamic bucket creation instruction input by a tenant, and the dynamic bucket creation instruction is used to specify the dynamic bucket name bucket3 and the associated regions of the dynamic bucket, such as region 1 and region 2. The cloud platform 10 creates a domain name bucket3.obs.huaweicloud.com of the dynamic bucket according to the dynamic bucket creation instruction, creates a static bucket 1 in region 1, creates a static bucket 2 in region 2, and associates the domain name bucket3.obs.huaweicloud.com of the dynamic bucket with the static bucket 1 set in region 1 and the static bucket 2 set in region 2, and the static bucket 2 is set by the cloud platform 10 as a cross-region backup bucket of the static bucket 1, that is, the objects stored in the static bucket 2 are cross-region backups of the objects stored in the static bucket 1.

Whenever a new object is uploaded to static bucket 1 or an object is modified, the new object or the modified object can be synchronously stored in static bucket 2 by the cloud platform.

In addition, the cloud platform 10 registers the correspondence between bucket3.obs.huaweicloud.com and IP0 of the cloud platform in the domain name service node 30 .

Among them, during the creation process of static bucket 1, cloud platform 10 sets IP1 for static bucket 1, and does not set the domain name of the static bucket. During the creation process of static bucket 2, cloud platform 10 sets IP2 for static bucket 2, but does not set the domain name and of the static bucket.

S402: The cloud platform 10 detects the working status of static bucket 1 and static bucket 2.

This step is similar to that of the first embodiment and will not be described in detail here.

S403: The cloud platform 10 receives an access request for the domain name of the dynamic bucket sent by the client 20, and sends the IP1 of the static bucket 1 associated with the domain name of the dynamic bucket or the IP2 of the static bucket 2 associated with the domain name of the dynamic bucket to the client according to the working status.

In this step, the client 20 sends an access request for the domain name bucket3.obs.huaweicloud.com of the dynamic bucket to the domain name service node 30. The domain name service node 30 forwards the access request to the cloud platform 10 according to the correspondence between bucket3.obs.huaweicloud.com and IP0 of the cloud platform. The cloud platform 10 determines IP1 of static bucket 1 and IP2 of static bucket 2 according to the domain name bucket3.obs.huaweicloud.com of the dynamic bucket.

Among them, when it is confirmed that the working status of one of static bucket 1 and static bucket 2 is abnormal, the cloud platform 10 sends the IP address of the static bucket with normal working status selected from static bucket 1 and static bucket 2 to the client 20; when it is confirmed that the working status of static bucket 1 and static bucket 2 are both normal, the IP address of static bucket 1 or static bucket 2 is sent to the client 20.

Optionally, in Embodiment 2, when confirming that the working statuses of static bucket 1 and static bucket 2 are both normal, the cloud platform 10 may randomly send the IP address of static bucket 1 or static bucket 2 to the client 20 .

In this embodiment, the cloud platform 10 can receive the dynamic bucket creation instruction input by the tenant through the configuration interface or API. The dynamic bucket instruction is also used to indicate the area 1 and area 2 selected by the tenant. Taking the configuration interface as an example, it can be referred to in conjunction with Figure 8. In this embodiment, after the tenant clicks the "Dynamic Bucket Creation" option as shown in Figure 6f, the cloud platform 10 provides a console configuration interface 7 shown in Figure 8. After the tenant enters the name of the dynamic bucket to be created, the tenant can further select or enter multiple areas, such as area 1 and area 2, and then click "Confirm". The cloud platform 10 creates static bucket 1 in area 1 and static bucket 2 in area 2 according to the above dynamic bucket creation instruction. Static bucket 1 and static bucket 2 are set with IP1 and IP2, but there is no need to set the domain name of the static bucket, and the cloud platform 10 only needs to register the correspondence between the domain name of the dynamic bucket and the IP0 of the cloud platform in the domain name service node 30.

In the first and second embodiments, the tenant needs to create a dynamic bucket on the cloud platform 10 to obtain the domain name of the dynamic bucket. However, in other scenarios, if the tenant has created a static bucket 1 and the client 20 has been set to a fixed domain name for accessing the static bucket 1, and the tenant does not want to change the domain name for accessing the client 20, the solution of the third embodiment of the bucket management method described below can be used. In the third embodiment, the tenant does not need to create a static bucket, but only needs to create a static bucket 2, and input the inter-bucket cross-region replication instruction to the cloud platform 10. At this time, the cloud platform 10 copies the objects of the static bucket 1 to the dynamic bucket 2 across regions according to the inter-bucket cross-region replication instruction, and returns the IP address of the static bucket 1 or the static bucket 2 to the client 20 according to the working status of the static bucket 1 and the static bucket 2. The third embodiment is suitable for the scenario where the tenant does not want to change the domain name of the existing static bucket to the domain name of the dynamic bucket.

For details, please refer to FIG. 9 , which is another flow chart of the bucket management method according to an embodiment of the present invention. As shown in FIG. 9 , the method includes the following steps:

Step S501: The cloud platform 10 receives the static bucket creation instruction 1 input by the tenant, and creates a static bucket 1 in region 1 according to the static bucket creation instruction 1, where the static bucket creation instruction 1 is used to indicate the region 1 and bucket name bucket 1 specified by the tenant. The static bucket 1 is set with a bucket name bucket 1, a domain name bucket 1.region 1.com and an IP 1 of the static bucket.

The cloud platform 10 registers the correspondence 1 between the domain name bucket1.region1.com of the static bucket and IP1 in the domain name service node 30 .

For example, the cloud platform 10 may receive a static bucket creation instruction 1 input by a tenant through a configuration interface or an API. The static bucket creation instruction is used to indicate a region 1 specified by the tenant, and the cloud platform 10 creates a static bucket 1 in region 1 according to the static bucket creation instruction 1.

In this embodiment, a configuration interface implementation is used for detailed description.

Reference can be made in conjunction with Figure 6a. As shown in Figure 6a, the cloud platform 10 provides a console configuration interface 1. When the tenant selects the "Static Bucket Creation" option in the console configuration interface 1, the cloud platform 10 provides a console configuration interface 2 shown in Figure 6b. The tenant enters the name of the static bucket to be created "bucket1", enters the bucket type "static bucket", and enters the region of the static bucket "region 1", and then clicks the "Confirm" option. At this time, the cloud platform 10 creates a static bucket 1 with the bucket name "bucket1" in the data center 1 of region 1 (as shown in Figure 2) according to the above-mentioned static bucket creation instruction entered by the tenant. Correspondingly, the cloud platform 10 configures the domain name bucket1.region1.com and IP1 for static bucket 1.

The cloud platform 10 may register the correspondence 1 between bucket1.region1.com and IP1 at the domain name service node 30 shown in FIG. 2 .

Furthermore, after creating the static bucket 1, the tenant uploads the object to the static bucket 1 so that the static bucket 1 stores the object, and the cloud platform 10 can provide the tenant with an upload interface, which will not be described in detail here.

Step S502: The cloud platform 10 receives the static bucket creation instruction 2 input by the tenant, and creates a static bucket 2 in region 2 according to the static bucket creation instruction 2. The static bucket creation instruction 2 is used to indicate the region 2 and bucket name bucket 2 specified by the tenant. The static bucket 2 is set with a bucket name bucket 2, a domain name bucket 2.region 2.com and an IP 2 of the static bucket.

For example, the cloud platform 10 may receive a static bucket creation instruction 2 input by a tenant through a configuration interface or an API. The static bucket creation instruction 2 is used to indicate the region 2 and bucket name bucket2 specified by the tenant, and the cloud platform 10 creates a static bucket 2 in region 2 according to the static bucket creation instruction 2.

Similarly, the tenant can create a static bucket 2 in the console configuration interface 3 shown in Figure 6c. The cloud platform 10 creates a static bucket 2 with the bucket name "bucket2" in the data center 2 of region 2 (as shown in Figure 2) according to the static bucket creation instruction 2 input by the tenant. Correspondingly, the cloud platform 10 configures the domain name bucket2.region2.com and IP2 for the static bucket 2.

Furthermore, in the process of creating a static bucket, the cloud platform 10 may register the correspondence 2 between bucket2.region2.com and IP2 in the domain name service node 30 shown in FIG. 2 .

Step S503: The cloud platform 10 receives the inter-bucket cross-region configuration instruction input by the tenant. The inter-bucket cross-region configuration instruction is used to indicate that static bucket 1 is the source bucket and static bucket 2 is the target bucket. The cloud platform 10 copies the objects stored in the source bucket to the target bucket across regions according to the inter-bucket cross-region configuration instruction.

Whenever a new object is uploaded to static bucket 1 or an object is modified, the new object or the modified object can be synchronously stored in static bucket 2 by the cloud platform.

The cloud platform 10 can receive inter-bucket cross-region configuration instructions input by the tenant through a configuration interface or API. For example, after the tenant clicks the "Cross-region Replication Policy Creation" option shown in Figure 6d, the cloud platform 10 provides the console configuration interface 8 shown in Figure 10, and the tenant can enter the bucket name of the source bucket and the bucket name of the target bucket in the console configuration interface 8.

Optionally, the bucket cross-region configuration instruction also includes the tenant's bucket access policy, which is used to instruct the cloud platform 10 to send the IP address of the static bucket 1 or static bucket 2 specified by the tenant to the client 20 when the working status of the static bucket 1 and the static bucket 2 are confirmed to be normal. Or instruct the cloud platform 10 to send the IP address of the static bucket that is physically closest to the client 20 to the client 20 when the working status of the static bucket 1 and the static bucket 2 are confirmed to be normal.

As shown in Figure 10, the console configuration interface 8 may provide a "bucket access policy" configuration item, in which the tenant may enter or select a "nearby access" policy to instruct the cloud platform 10 to send the IP address of the static bucket that is physically closest to the client 20 to the client 20 after confirming that the working status of static bucket 1 and static bucket 2 are both normal.

Alternatively, bucket1 can be directly entered in the configuration item to instruct the cloud platform 10 to send the IP address of static bucket 1 to the client 20 after confirming that the working status of static bucket 1 and static bucket 2 are both normal. Similarly, bucket2 can also be entered in the configuration item to instruct the cloud platform 10 to send the IP address of static bucket 2 to the client 20 after confirming that the working status of static bucket 1 and static bucket 2 are both normal.

In addition, the cloud platform 10 further deletes the correspondence 1 between bucket1.region1.com and IP1 at the domain name service node 30 shown in FIG. 3 according to the inter-bucket cross-region configuration instruction, and re-registers the correspondence 4 between bucket1.region1.com and IP0 of the cloud platform.

Step S504: the cloud platform 10 detects the working status of static bucket 1 and static bucket 2.

Step S505: the cloud platform 10 receives an access request for the domain name bucket1.region1.com of the static bucket 1 sent by the client 20, and sends the IP1 of the static bucket 1 or the IP2 of the static bucket 2 to the client according to the working status.

In this step, the client 20 sends an access request for the domain name bucket1.region1.com of the static bucket of static bucket 1 to the domain name service node 30, and the domain name service node 30 forwards the access request to the cloud platform 10 according to the correspondence 4 between bucket1.region1.com and IP0 of the cloud platform.

When the working status of one of static bucket 1 and static bucket 2 is abnormal, the cloud platform 10 sends the IP address of the static bucket with normal working status selected from static bucket 1 and static bucket 2 to the client 20 .

When confirming that the working statuses of static bucket 1 and static bucket 2 are both normal, the cloud platform 10 sends the IP address of static bucket 1 or static bucket 2 to the client 20 .

Optionally, when the cross-region configuration instructions between buckets also include the tenant's bucket access policy, the cloud platform 10 sends the IP address of static bucket 1 or static bucket 2 specified by the tenant via the bucket access policy to the client 20 according to the bucket access policy; or sends the IP address of the static bucket that is physically closest to the client 20 to the client 20 according to the bucket access policy.

Therefore, in the third embodiment, the client 20 does not need to change the domain name bucket1.region1.com to be accessed. The tenant only needs to create a static bucket 2 on the cloud platform 10 and input the cross-region configuration instruction between buckets to the cloud platform 10, so that the access request for bucket1.region1.com issued by the client 20 can be forwarded to the cloud platform 10, and the cloud platform 10 returns a suitable IP address to the client according to the working status of the static bucket 1 and the static bucket 2. The third embodiment is particularly suitable for the scenario where the tenant does not want to change the domain name of the existing static bucket to the domain name of the dynamic bucket on the client 20.

It is worth noting that, in the embodiment of the present invention, the client 20 is not necessarily operated by the tenant, but may be operated by other persons. However, in this case, the client 20 is provided with a token authorized by the tenant.

Furthermore, in other embodiments of the present invention, the domain name of the static bucket does not need to include the identifier of the region where the static bucket is located. For example, the domain name of static bucket 1, bucket1.region1.com, includes the identifier of region 1, region1. Optionally, the domain name of static bucket 1 may be, for example, bucket1.obs.huawei.com, and its format is similar to that of the domain name of the dynamic bucket. This is not limited in the embodiments of the present invention.

Furthermore, the “static bucket creation instruction” and the “dynamic bucket creation instruction” described in the embodiment of the present invention are both specific implementation methods of the “data bucket creation instruction”.

The object storage system shown in FIG3 is specifically described below in conjunction with FIGS. 11 to 13 . FIG. 11 is a connection diagram of a data center in an object storage system according to an embodiment of the present invention. FIGS. 12 and 13 are structural diagrams of storage nodes according to an embodiment of the present invention.

First, please refer to Figure 11. In this embodiment, the cloud platform 10 is set in the data center 1, and is connected to the storage node 201, the storage node 202 and the remote connection gateway 204 through the switching device 203. The data center 2 is provided with a switching device 206, a storage node 207, a storage node 208 and a remote connection gateway 205. The storage node 207, the storage node 208 and the remote connection gateway 205 are connected to the switching device 206 respectively. The data center 1 is set in the area 1, and the data center 2 is set in the area 2. The remote connection gateway 204 and the remote connection gateway 205 are directly provided with a remote connection channel, so that the data center 1 and the data center 2 are connected across regions.

For example, the remote connection gateway may be implemented through a virtual private network (VPN) or a dedicated network, and the storage node may be implemented through a server provided with multiple physical disks.

Please refer to Figure 12. The storage node 201 includes a software layer and a hardware layer. The hardware layer includes a disk controller 2015, a physical network card 2016, a physical disk 1 and a physical disk 2. The software layer includes an object storage device OSD control unit 2011 and an operating system 2012. The OSD control unit 2011 runs on the operating system 2012. The operating system 2012 includes a disk driver 2013 and a physical network card driver 2014. The cloud platform 10 can communicate with the OSD control unit 2011 through the physical network card 2016. The OSD control unit 2011 controls the disk controller 2015 through the disk driver 2013 to set the physical disk 1 and the physical disk 2 as multiple object storage devices OSD. After receiving the creation instruction of the static bucket 1, the cloud platform 10 notifies the OSD control unit 2011 to create the static bucket 1. At this time, the OSD control unit 2011 sets OSD1-3 as static bucket 1.

The storage node 207 shown in Figure 13 also has a similar structure. After receiving the creation instruction of static bucket 2, the cloud platform 10 notifies the OSD control unit 2071 to create static bucket 2. At this time, the OSD control unit 2071 sets OSD5-7 as static bucket 2.

Further, after receiving the cross-zone configuration policy instructions described in Example 1 or Example 3, or the dynamic bucket creation instructions described in Example 2, the cloud platform 10 notifies the OSD control unit 2011 to send the objects stored in OSD1-3 in the static bucket 1 to the storage node 207 via the remote connection channel, and the OSD control unit 2071 in the storage node 207 stores these objects in OSD5-7.

Please refer to Figure 14 below, which is a schematic diagram of the device structure of the cloud platform according to an embodiment of the present invention. As shown in Figure 14, the cloud platform 10 includes a data bucket configuration module 101, an instruction receiving module 102, an instruction processing module 103, a data bucket selection module 104, and a sending module 105. The above-mentioned functional modules are used to implement the relevant functions of the cloud platform 10 of the above-mentioned embodiment one.

Please refer to Figure 15 below, which is a schematic diagram of the device structure of the cloud platform according to an embodiment of the present invention. As shown in Figure 15, the cloud platform 10 includes an instruction receiving module 601, a data bucket configuration module 602, a domain name providing module 603, a data bucket selection module 604, a sending module 605, and a sending module 606. The above-mentioned functional modules are used to implement the relevant functions of the cloud platform 10 in the above-mentioned embodiment one.

Please refer to Figure 16 below, which is a schematic diagram of the device structure of the cloud platform according to an embodiment of the present invention. As shown in Figure 16, the cloud platform 10 includes a data bucket configuration module 701, a data bucket selection module 702, a sending module 703, an instruction receiving module 704, an object replication module 705, and a bucket access policy acquisition module 706. The above-mentioned functional modules are used to implement the relevant functions of the cloud platform 10 in the above-mentioned embodiment one.

Further, please refer to Figure 17, which is a schematic diagram of the device structure of a computer device according to an embodiment of the present invention. As shown in Figure 17, the computer device includes a processor 1001, a memory 1002, a communication interface 1003 and a bus 1004. The processor 1001, the memory 1002, and the communication interface 1003 are respectively connected to the bus 1004, the memory 1002 is used to store computer execution instructions, and the processor 1001 is used to execute the computer execution instructions stored in the memory 1002, so that the computer device implements the method executed by the above-mentioned cloud platform 10.

Optionally, the cloud platform 10 may also be implemented by a computer cluster including a plurality of computer devices, which is not limited in the embodiment of the present invention.

In addition, an embodiment of the present invention further provides a computer storage medium, including computer-readable instructions, which, when executed, implement the method executed by the above-mentioned cloud platform 10.

An embodiment of the present invention also provides a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute the method executed by the above-mentioned cloud platform 10.

Through the description of the above implementation mode, the technicians in the field can clearly understand that the present application can be implemented by means of software plus necessary general hardware, and of course, it can also be implemented by special hardware including special integrated circuits, special CPUs, special memories, special components, etc. In general, all functions completed by computer programs can be easily implemented by corresponding hardware, and the specific hardware structure used to implement the same function can also be various, such as analog circuits, digital circuits or special circuits. However, for the present application, software program implementation is a better implementation mode in more cases. Based on such an understanding, the technical solution of the present application is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a readable storage medium, such as a computer floppy disk, a U disk, a mobile hard disk, a ROM, a RAM, a disk or an optical disk, etc., including a number of instructions to enable a computer device (which can be a personal computer, a training device, or a network device, etc.) to execute the methods described in each embodiment of the present application.

In the above embodiments, all or part of the embodiments may be implemented by software, hardware, firmware or any combination thereof. When implemented by software, all or part of the embodiments may be implemented in the form of a computer program product.

The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website site, a computer, a training device, or a data center by wired (e.g., coaxial cable, optical fiber, digital tenant line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, training device, or data center. The computer-readable storage medium may be any available medium that a computer can store or a data storage device such as a training device, a data center, etc. that includes one or more available media integrations. The available medium may be a magnetic medium, (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive (SSD)), etc.

Claims (12)

1. A method of providing cloud storage services, comprising:

Acquiring a third data bucket creation instruction input by a tenant;

providing domain names of the third data barrels to the tenants according to the third data barrel creation instruction;

According to the association instruction input by the tenant, the third data bucket is associated with a first data bucket arranged in a first area and a second data bucket arranged in a second area, the data object stored in the second data bucket is a trans-regional backup of the data object stored in the first data bucket, the third data bucket is used for determining a target data bucket for providing data required to be accessed from the first data bucket and the second data bucket after receiving an access request for the domain name of the third data bucket, and in the case that the working state of any one of the first data bucket and the second data bucket is abnormal, the data bucket with normal working state is selected from the first data bucket and the second data bucket to serve as the target data bucket; or selecting a data bucket closest to the physical distance of the client or a data bucket appointed by a tenant from the first data bucket and the second data bucket as the target data bucket.

2. The method according to claim 1, wherein the method further comprises:

Receiving a first data bucket creation instruction input by the tenant, wherein the first data bucket creation instruction is used for indicating the first area appointed by the tenant, and creating the first data bucket in the first area according to the first data bucket creation instruction, and the first data bucket is used for storing an object uploaded by the tenant;

And receiving a second data bucket creation instruction input by the tenant, wherein the second data bucket creation instruction is used for indicating the second area designated by the tenant, and creating the second data bucket in the second area according to the second data bucket creation instruction.

3. The method according to claim 1 or 2, wherein selecting, as the target data bucket, a data bucket or a tenant designated data bucket closest to a physical distance of a client from among the first data bucket and the second data bucket, comprises:

And under the condition that the working states of the first data bucket and the second data bucket are normal, selecting a data bucket closest to the physical distance of the client or a data bucket appointed by a tenant from the first data bucket and the second data bucket as the target data bucket.

4. The method according to claim 1 or 2, characterized in that the method further comprises:

receiving inter-bucket cross-region configuration instructions input by the tenant, wherein the inter-bucket cross-region configuration instructions are used for indicating the first data bucket as a source bucket and the second data bucket as a target bucket;

And copying the object stored in the source barrel to the target barrel in a transregional mode according to the transregional configuration instruction between barrels.

5. The method according to claim 1 or 2, further comprising obtaining a bucket access policy of the tenant, wherein the bucket access policy instructs a cloud platform to select, as the target data bucket, a data bucket closest to the physical distance of the client or a data bucket specified by the tenant, in a case where it is confirmed that the working states of the first data bucket and the second data bucket are both normal.

6. A cloud platform for providing cloud storage services, comprising:

the instruction receiving module is used for acquiring a third data bucket creation instruction input by the tenant;

The instruction processing module is used for providing domain names of the third data barrels for the tenants according to the third data barrel creation instruction; according to the association instruction input by the tenant, the third data bucket is associated with a first data bucket arranged in a first area and a second data bucket arranged in a second area, the data object stored in the second data bucket is a trans-regional backup of the data object stored in the first data bucket, the third data bucket is used for determining a target data bucket for providing data required to be accessed from the first data bucket and the second data bucket after receiving an access request for the domain name of the third data bucket, and in the case that the working state of any one of the first data bucket and the second data bucket is abnormal, the data bucket with normal working state is selected from the first data bucket and the second data bucket to serve as the target data bucket; or selecting a data bucket closest to the physical distance of the client or a data bucket appointed by a tenant from the first data bucket and the second data bucket as the target data bucket.

7. The cloud platform of claim 6, further comprising a data bucket configuration module to:

Receiving a first data bucket creation instruction input by the tenant, wherein the first data bucket creation instruction is used for indicating the first area appointed by the tenant, and creating the first data bucket in the first area according to the first data bucket creation instruction, and the first data bucket is used for storing an object uploaded by the tenant;

And receiving a second data bucket creation instruction input by the tenant, wherein the second data bucket creation instruction is used for indicating the second area designated by the tenant, and creating the second data bucket in the second area according to the second data bucket creation instruction.

8. The cloud platform of claim 6 or 7, further comprising a data bucket selection module comprising:

And under the condition that the working states of the first data bucket and the second data bucket are normal, selecting a data bucket closest to the physical distance of the client or a data bucket appointed by a tenant from the first data bucket and the second data bucket as the target data bucket.

9. The cloud platform of claim 6 or 7, further comprising an instruction receiving module for

Receiving inter-bucket cross-region configuration instructions input by the tenant, wherein the inter-bucket cross-region configuration instructions are used for indicating the first data bucket as a source bucket and the second data bucket as a target bucket;

and the instruction processing module is further used for copying the object stored in the source barrel to the target barrel in a cross-region mode according to the cross-region configuration instruction between barrels.

10. The cloud platform of claim 6 or 7, wherein the instruction receiving module is further configured to obtain a bucket access policy of the tenant, where the bucket access policy instructs the cloud platform to select, when it is confirmed that the working states of the first data bucket and the second data bucket are both normal, a data bucket closest to a physical distance of the client as the target data bucket, or select a data bucket specified by the tenant as the target data bucket.

11. A computer device, the computer device comprising: a processor and a memory;

the memory is used for storing computer execution instructions;

the processor is configured to execute computer-executable instructions stored in the memory to cause the computer device to implement the method of any one of claims 1 to 5.

12. A computer storage medium comprising computer readable instructions which, when executed, implement the method of any one of claims 1 to 5.