Hello, everyone!
This post will share with you the object storage service.
Function Description
This section describes main functions and application values of OBS.
Lifecycle Management
Lifecycle management means periodically deleting objects in a bucket by configuring a lifecycle rule.
Lifecycle management applies to the following scenarios:
· Periodically uploaded log files need to be retained for only one week or one month, and therefore they need to be deleted periodically.
· Some documents are frequently accessed within a certain period of time. After the period of time elapses, the documents are seldom accessed and therefore need to be deleted.
You can define lifecycle management rules for identifying objects and manage lifecycles of the objects based on the rules. After unnecessary files are deleted, less OBS storage space is required, thereby reducing the rent fee.
Lifecycle management rules have two key elements:
· Configuration policy: You can specify the prefix of object names so that objects whose names have this prefix are restricted by the rules. You can configure lifecycle rules for a bucket so that all objects in the bucket can be restricted by the lifecycle rules.
· Expiration time: You can specify the number of days after which objects are automatically deleted or the day after which objects that match with a rule are deleted by OBS.
For example, the following files are saved on OBS on January 7, 2017:
· log/test1.log
· log/test2.log
· doc/example.doc
· doc/good.txt
The following files are saved on OBS on January 10, 2017:
· log/clientlog.log
· log/serverlog.log
· doc/work.doc
· doc/travel.txt
If the expiration time of objects prefixed with log/ is set to January 11, 2017 (or one day later) on January 10, 2017, OBS will delete the objects log/test1.log, log/test2.log, log/clientlog.log, and log/serverlog.log on January 11, 2017.
NOTE:
The deletion of an object may be delayed after the object expires. Generally, the delay does not exceed 48 hours.
Managing Fragments
The fragment management function enables you to clear fragments that were generated due to object upload failures 90 days ago.
Fragments are incomplete data in buckets generated due to data upload failures.
OBS uploads data by blocks. In the following situations (but not limited to the following situations), fragments are generated due to data upload failures. These fragments need to be cleared to free up space.
· The network is in poor conditions, and the connection to the OBS server is interrupted frequently.
· An upload task is manually interrupted.
· A device is faulty.
· The device is powered off suddenly.
Versioning
OBS can store multiple versions of an object. You can quickly search for and restore different versions as well as restore data in the event of misoperations or application faults.
Versioning is an effective means to restore objects that are overwritten or deleted incorrectly. By default, versioning is disabled for new buckets on OBS. New objects uploaded to a bucket will overwrite the existing objects with the same names in the bucket.
After versioning is enabled:
· When an object is uploaded, OBS automatically allocates a unique version ID to the object. Objects with the same name are stored on OBS with different version IDs.
· An object can be downloaded by specifying a version ID. By default, the latest object is downloaded if no version ID is specified.
· Objects can be permanently deleted by specifying version IDs. They cannot be restored after being deleted. If an object is deleted with no version ID specified, OBS will generate a deletion mark with a unique version ID for the object but will not actually delete the object.
· The latest objects in a bucket are listed by default after a GET Object request is received. You can also send a request to list a bucket's objects with all version IDs.
When versioning is no longer required for objects in a bucket, you can suspend it. After versioning is suspended:
· Old version data remains on OBS. You need to manually delete unnecessary old version data.
Accessing and Using OBS
Accessing the Management Console
CloudOpera ServiceCenter can be accessed through a management console.
If you are a resource administrator of CloudOpera ServiceCenter or have the operation permission for OBS, you can directly log in to the management console and select Object Storage Servicefrom the Product or Console page.
Restrictions
This section describes restrictions of OBS.
Restrictions of the OBS are as follows:
· The OBS provides storage for FusionCloud internal cloud services and backup and archiving services.
· The OBS is compatible with standard Amazon S3 APIs.
· Charging data records (CDRs) are generated in the HEC format.
· S3 quotas are updated every five minutes. After a file is uploaded successfully, no quota detection is performed for files uploaded to the same bucket within 10s.
· The LVS is used for load balancing by default. The RH2288H V3 is recommended.
· The network address translation (NAT) feature is enabled for firewalls when Internet users access the OBS on the Internet plane or tenant VMs access the OBS on the tenant plane.
· Back-end service switches are deployed independently and are not shared with other services.
· Front-end service switches support equal and weighted cost multi-path (ECMP).
· The OBS supports multiple regions, each region supports one available zone (AZ) and one cluster.
· Each FusionStorage cluster contains a maximum of 20 nodes.
· A tenant can create a maximum of 100 buckets.
· A file with a maximum size of 50 MB can be uploaded by using the OBS Console. You can upload files with a size of greater than 50 MB by using the third-party tool or self-developing tools according to the S3 interface.
· To ensure object upload continuity for users, OBS does not require reserving storage space, but uses the on-demand allocation mechanism. In addition, OBS does not check the object size during the upload. Before the OBS quota reaches the upper limit, it is possible that the size of the object being uploaded is larger than the remaining quota.
· After a user adds a bucket, this bucket can only be used in the sessions of the current browser. If any of the following occurs, add the bucket again:
o The login timed out.
o The browser is closed.
o The cached data of the browser is cleared.
· A user cannot use the global domain name to access the buckets and objects in a non-default region.
· After a user is assigned all rights of other tenents' buckets, the user has only the rights that map to the user's role.
· When a third-party S3 client is used to access object storage, only the domain name of the default region and the global domain name can be used to create buckets. You are advised to create buckets on the OBS interface.
· When login through OBS Console:
o To upload and download objects, you must import the purchased commercial certificate or the certificate made by the storage administrator using the browser.
o Only the buckets of tenants can be added.
o Object storage administrators and resource tenant administrators cannot add buckets.
· When you use an Internet Explorer browser, OBS Console supports only Internet Explorer 10.0 and 11.0. You are advised to use Internet Explorer 11.0, which helps you better use the functions of the software.
· You are advised to use third-party tools or tools tailored to the S3 interface to access FusionStorage. When using third-party tools, you are advised to use domain names to access FusionStorage.
That's all, thanks!
