No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

OceanStor 9000 V300R006C00 Object Storage Service (Compatible with Amazon S3 APIs) Administrator Guide 07

Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Adding a Cluster

Adding a Cluster

After clusters are added into AZs, you can manage them in a unified manner.

Prerequisites

You must add the current cluster to an AZ prior to adding another cluster to the AZ.

Because other clusters can only be added to the default cluster of the default AZ, you must set the current cluster to which you have logged in to the default cluster of the default AZ when you add a cluster for the first time.

The default region is used as an example when adding clusters into AZs. The operations in other regions are similar to those in the default region.

Procedure

  1. Log in to DeviceManager.
  2. Choose Settings > Storage Region Settings > Region Information Configuration > Region.
  3. Click in front of Global, and click in front of the region, and click the AZ where you want to add the cluster.
  4. Click Add. The Add Cluster dialog box is displayed.
  5. Set the cluster parameters and click OK.

    Table 6-8 lists related parameters.

    Table 6-8  Parameters for adding a cluster

    Parameter

    Description

    Value

    ID

    Cluster ID

    NOTE:

    The cluster ID is automatically generated during the deployment.

    [Possible value]

    A string of 1 to 127 characters, including letters, digits, hyphens (-), and underscores (_). It must start with a letter and cannot end with a hyphen (-) or an underscore (_).

    [Example]

    Region01_AZ01_cluster01

    Name

    Cluster name

    [Possible value]

    A string of 1 to 127 characters, including letters, digits, hyphens (-), and underscores (_). It must start with a letter and cannot end with a hyphen (-) or an underscore (_).

    [Example]

    beijing

    Alias

    Cluster alias.

    [Possible value]

    • A string of 1 to 255 characters, including lowercase letters, digits, hyphens (-), and periods (.).
    • It must start with a letter or digit and cannot end with a hyphen (-).
    • It cannot be an IP address, and cannot contain consecutive periods (.), or a period (.) following or followed by a hyphen (-).
    • The parameter value cannot be set to a subdomain name of the global domain name.

    Service Address

    Address for providing services externally, such as receiving or sending service requirements.
    NOTE:

    After the Service Address is configured, you do not need to configure LS Monitoring Address.

    [Value]

    An IPv4 address, IPv6 address, or domain name.

    [Example]

    192.168.1.100, fc00::1234, or test.com

    Management Address

    Management IP address of the cluster for communication between clusters.

    [Possible value]

    An IPv4 address, a string of 1 to 255 characters.

    [Example]

    192.168.1.100

    LS Monitoring Address

    Service address for monitoring cluster status.
    NOTE:
    • After the Service Address is configured, you do not need to configure LS Monitoring Address.
    • If the current cluster is the primary cluster, keep the configuration the same as the RLS Active Service Address in the public parameters.

    [Value]

    An IPv4 address, IPv6 address, or domain name.

    [Example]

    192.168.1.100, fc00::1234, or test.com

    Default Cluster

    Whether the current cluster is the default cluster in the local AZ

    NOTE:

    Each AZ has only one default cluster.

    [Possible value]

    Yes or No

    [Example]

    Yes

    LS Role

    LS role of the cluster. The value can be:
    • Primary: Provides the service of querying the locations of all the buckets that belong to the owning region of the cluster.
    • Not running: A cluster that is not running does not provide the service of querying bucket locations.
    NOTE:

    After the LS Role is selected, you do not need to select Provisioning Orchestration Engine Role.

    [Possible value]

    Primary, or Not running

    [Example]

    Primary

    Provisioning Orchestration Engine Role

    Provisioning orchestration engine role of the cluster. The value can be:
    • Primary: Provides the authentication service for the owning region of the cluster.
    • Not running: A cluster that is not running does not provide the authentication service.
    NOTE:

    After the LS Role is selected, you do not need to select Provisioning Orchestration Engine Role.

    [Possible value]

    Primary, or Not running

    [Example]

    Primary

    CDR Role

    CDR role of the cluster. The value can be:
    • Primary: Provides the CDR service for the owning region of the cluster.
    • Secondary: If the owning cluster of the active CDR fails, the standby CDR provides the CDR service for the owning region of the cluster.
    • Not running: A cluster that is not running does not provide the CDR service.

    [Possible value]

    Primary, Secondary, or Not running

    [Example]

    Primary

    Description

    Cluster description

    [Possible value]

    A string of 0 to 255 characters.

    [Example]

    Information about the Beijing (China) cluster 1

Translation
Download
Updated: 2019-04-28

Document ID: EDOC1000122523

Views: 12716

Downloads: 84

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next