Creating a namespace

Content Platform Tenant Management Help

File Size
4269 KB
Part Number

You create namespaces in the Tenant Management Console. When you create a namespace, you set some of its properties. Other namespace properties have default settings that you can change only after the namespace has been created.

You can change most of the properties for existing namespaces.

  • If the tenant supports Active Directory authentication, you can create a namespace only while HCP can communicate with AD.
  • Under certain circumstances, the current state of replication for the tenant may prevent namespace creation.
To create a namespace, you need the administrator role.
  1. In the top-level menu of the Tenant Management Console, click Namespaces.
  2. On the Namespaces page, click Create Namespace.
    The Create Namespace panel opens. Below the Namespace Name field, this panel shows the number of namespaces the tenant currently owns and the number of additional namespaces currently available for the tenant to create.

    The default settings that appear in the Create Namespace panel are determined by the settings on the Namespace Defaults page.

  3. In the Namespace Name field, type a name for the namespace.
    HCP derives the hostname for the namespace from this name. The hostname is used in URLs for access to the namespace.

    In English, the name you specify for a namespace must be from one through 63 characters long and can contain only alphanumeric characters and hyphens (-) but cannot start or end with a hyphen. In other languages, because the derived hostname cannot be more than 63 characters long, the name you specify may be limited to fewer than 63 characters.

    Namespace names cannot contain special characters other than hyphens and are not case sensitive. White space is not allowed.

    Namespace names cannot start with xn-- (that is, the characters x and n followed by two hyphens).

    The namespace name must be unique for the current tenant. Different tenants can have namespaces with the same name.

    You can change the namespace name any time after you create the namespace, except while the CIFS or NFS protocol is enabled for the namespace. However, when you change the name, the URL for the namespace may change as well.

    You can reuse namespace names that are not currently in use. So, for example, if you delete a namespace, you can give a new namespace the same name as the deleted namespace had.

  4. (Optional) Specify an owner for the namespace:
    • If the owner has an HCP user account, select Local. Then type the username for the account in the Namespace Owner field.
    • If the owner has an AD user account, select Active Directory. Then, in the Namespace Owner field, type the account username along with the name of the AD domain in which the account is defined, in this format: username@ad-domain-name.
  5. (Optional) In the Description field, type a description of the namespace.
    The description can be up through 1,024 characters long and can contain any valid UTF-8 characters, including white space. However, it must not include special characters such as \n (carriage return) and \r (line feed).
  6. In the Hash Algorithm field, select the cryptographic hash algorithm for the namespace.
  7. In the Hard Quota field, type the number of gigabytes or terabytes of storage to allocate to the namespace and select either GB or TB to indicate the measurement unit.
    Valid values are decimal numbers with up to two places after the period. The minimum is 1 (one) for GB and .01 for TB. The maximum value is the amount of space the tenant still has available to allocate to its namespaces.
    Tip: To the right of the Hard Quota field, the panel shows the amount of space the tenant has already allocated to its namespaces and the amount of space it still has available to allocate.
  8. In the Soft Quota field, type the percent at which you want HCP to notify the tenant that free storage space for the namespace is running low.
    Valid values are integers in the range ten through 95.
  9. (Optional) Associate tags with the namespace:
    1. Click Tags.
    2. In the field in the Tags section, type a text string to be used as a tag.
      Tags must be from one through 64 characters long, can contain any valid UTF-8 characters except commas (,), and are not case sensitive. White space is allowed.
    3. Click Add Tag.
  10. Under Replication:
    • Select On to replicate the namespace along with the tenant.
    • Select Off to exclude it from replication.
    The Replication option is present only if the tenant is allowed to create namespaces with replication enabled.
    Note: Depending on current replication requirements, if the tenant is being replicated, this option may be selected automatically. In this case, you cannot deselect it.
  11. (Optional) If you selected On for Replication, select Allow erasure coding to allow HCP to use erasure coding to implement replication of the objects in the namespace.
    The Allow erasure coding option is present only while Replication is On and only if the tenant is allowed to manage erasure coding for namespaces.
    When you select Allow erasure coding, the Cloud Optimized option is automatically set to On.
  12. Under Cloud Optimized:
    • Select On to optimize the namespace for cloud protocols only.
    • Select Off to optimize the namespace for all protocols.
    The Cloud Optimized option is present only if the tenant is allowed to create namespaces with replication enabled.
    When you select Off while Allow erasure coding is selected, that option is automatically deselected.
  13. Under Directory Usage:
    • Select Balanced to configure the namespace for balanced directory usage.
    • Select Unbalanced to configure the namespace for unstructured data usage.
  14. Under Retention Type, select either S3 Object Lock or HCP Retention to set the retention type for the namespace.
    The HCP Retention Mode option is present only if the Retention Mode Selection is enabled. You can enable S3 Object Lock only if versioning is enabled on the tenant.
    Note: When configuring namespaces that use S3 Object Lock, you cannot use existing retention related namespace configuration options that conflict with S3 Object Lock. For example, retention period values that Amazon S3 does not support, initial unspecified, event-based retention, and retention classes are not allowed.
  15. Under Search:
    • Select On to enable search for the namespace.
    • Select Off to disable search.
    The Search option is present only if the tenant is allowed to create namespaces with search enabled.
  16. In the Service Plan field, either type the name of an existing service plan or click the arrow control ().
    If you click the arrow control:
    1. In the Service Plans window, select the service plan you want.
    2. Click Apply Service Plan.
    The Service Plan field is present only if the tenant is allowed to associate service plans with namespaces.
  17. Under Versioning:
    • Select On to enable object versioning in the namespace.
    • Select Off to disable object versioning in the namespace.
    The Versioning option is present only if the tenant is allowed to create namespaces with versioning enabled.
    When you select On, you can also enable version pruning and delete markers.
    1. In the Versioning Options section, select the Prune versions older than ... days option.
    2. In the option field, type the number of days old versions of objects must remain in the namespace before they are pruned.
      Valid values are integers from zero through 36,500 (that is, 100 years). A value of zero means prune immediately.
      If version pruning is enabled for a namespace, you can apply a backup policy to keep milestone versions for specified periods of time. You cannot delete versions that are under retention. The milestone versioning policy can apply to an object only when it is outside the retention policy of that object.
    3. In the Versioning Options section, select the Enable delete markers option.

      This option allows you to use the delete markers in Amazon S3 using Hitachi API for Amazon S3 and REST API. After you enable versioning and delete markers, you cannot disable them.

      When you delete an object in a version-enabled namespace, a delete marker is created. The delete marker then becomes the current version. The object behaves as if it is deleted. However, it automatically maintains previous versions of the object. The delete marker has the following characteristics:

      • Like in any other versioned object, the delete marker has a version ID associated with it.
      • Using an S3 DELETE request, you can delete the delete marker by specifying the version ID of the marker.
      • Using a GET bucket version request, you can retrieve a delete marker version ID.
      For non-versioned namespaces, allow object overwrites if desired. See Allowing object overwrites.
  18. Click Create Namespace.
    If Versioning is set to On but Prune versions is not selected, a confirming message appears.
  19. In the window with the confirming message, select I understand to confirm that you understand the consequences of your action.
  20. Click Update Settings.