Working with extended storage components

Last updated
Save as PDF

HCP uses extended storage components to provide you with an interface to use, manage, and monitor extended storage devices and cloud storage service endpoints.

Using the System Management Console, you can perform the following actions on extended storage components:

Configure HCP to access specific extended storage devices and cloud storage service endpoints.
Configure HCP to monitor, manage, and use all of the extended storage that is accessed using one or more extended storage components of the same type as a single storage pool.
Monitor the health, availability, capacity, and usage of the extended storage that is represented by each component, and appropriately provision storage.
Pause (suspend), retire, or abandon extended storage that is represented by a single storage component, or retire all of the extended storage that is represented by the components in a single storage pool.

Creating an extended storage component

Use the Add Component wizard on the Storage page to create and configure an extended storage component.

Each time you use the Storage page to access the Add Component wizard, you are prompted to select the type of extended storage component that you want to create. The System Management Console then dynamically builds the pages in the Add Component wizard to present only the fields you need to use to configure HCP to access and use the specified type of extended storage component.

Before you begin

To view the Storage page, you need the monitor or administrator role. To create, modify, or delete extended storage components and extended storage pools, you need the administrator role.

Procedure

On the left side of the Storage page, click the Components tab.
On the Components panel, click Add Component.

The Get Started wizard opens.
In the wizard, click the arrow and select the type of component that you want to create.

Note
To create a ThinkOn cloud storage component, select ThinkOn as the type of component to configure. Then follow the same procedure as you do to configure other S3 compatible storage components.
Click Go.

The Get Started wizard exits and the System Management Console opens the applicable Add Component wizard.
Specify the information that HCP needs to use to access and use the extended storage component:
- To create an Amazon S3 storage component, use the Amazon S3 storage component settings. Then return to this procedure.
- To create a Google Cloud storage component, use the Google Cloud storage component settings. Then return to this procedure.
- To create a Microsoft Azure storage component, use the Microsoft Azure storage component settings. Then return to this procedure.
- To create a S3 compatible storage component, including a ThinkOn cloud storage component, use the S3 compatible storage component settings. Then return to this procedure.
- To create an NFS storage component, use the NFS storage component settings. Then return to this procedure.
Click Next to save the information you entered and advance to the last page of the wizard.
On the Review page, take one of these actions:
- If the extended storage component configuration information that you entered is correct, click Finish.
- If the extended storage component configuration information is not correct, use the Previous and Next buttons to navigate through the pages in the wizard and change any settings that are not correct. Then navigate to the Review page and click Finish.
The wizard closes and the System Management Console displays the Components panel on the Storage page

Results

You created and configured the extended storage component.

HCP can use the storage that is represented by a given component only if at least one of its access points (a mount point, bucket, or container) is contained in a storage pool that’s included in at least one storage tier that’s defined for a namespace by its service plan.

Amazon S3 storage component settings

Each Amazon S3 component represents a single endpoint that’s used to access cloud storage using one or more Amazon S3 Web Services user accounts.

To enable HCP to access the storage that’s represented by an Amazon S3 storage component, when you create that component, you specify the following information:

The component name.
Optionally, a description of the component.
Optionally, the network you want HCP to use for communication with storage component. This field is only visible if Virtual network management is enabled.
Whether you want HCP to use the default endpoint, s3.amazonaws.com, to connect to Amazon S3 Web Services, and if not, the fully qualified domain name (FQDN) of the endpoint that you want HCP to use instead of the default.
Optionally, any of these advanced configuration settings:
- Whether you want HCP to use HTTPS to access the endpoint, and if so, the HTTPS port you want to use to connect to the endpoint (default is 443)
- The HTTP port you want to use to connect to the endpoint (default is 80)
- Whether you want to use a proxy server to connect to the endpoint, and if so, the following information about the proxy server:
  - The hostname or IP address of the proxy server
  - The port number you want to use to connect to the proxy server (default is 0)
  - The user name, password, and AD domain of the user account that HCP needs to use to access the proxy server
- Whether you want HCP to use path-style URLs to access the storage that’s represented by the storage component, and if so, the region that includes the Amazon S3 Web Services datacenter that hosts the storage that’s represented by this component. If you select this option, you need to specify a region-specific endpoint instead of using the default endpoint.
- The region that includes the Amazon S3 Web Services datacenter that hosts the storage that’s represented by this component (default is us-east-1).
  For faster access to storage located in a particular region, you should specify a region-specific endpoint instead of using the default endpoint.
- Whether the extended storage component supports S3 metadata on objects. If you are unsure whether S3 metadata is supported, contact your service provider.
- In the Max metadata size field, type the maximum size (in bytes) of the S3 metadata that will be attached to objects tiered to the storage component. Each extended storage service provider permits a different maximum size. Contact your service provider to learn the maximum size.
Whether the storage that’s represented by this component is considered to be compliant.
The account label that you want to associate with the initial Amazon S3 Web Services user account that you want HCP to use to access the storage that’s represented by the component. In the System Management Console, HCP uses the account label to represent the user account with the specified credentials.
The authentication type you want to use to authenticate all requests sent from HCP to the storage component.
The access key and secret key for the Amazon S3 Web Services user account that you want HCP to use to access the storage that’s represented by the component. After you create an Amazon S3 storage component, you can modify it to specify credentials for one or more additional user accounts.
If you are using AWS STS or CAP authentication, the authentication endpoint text field appears. This is the endpoint to which you send your credentials in order to generate an AWS STS authentication token.
If you are using CAP authentication, the following additional fields are displayed:
- Authentication port field. Enter the port of your CAP endpoint.
- Authentication certificate drop down menu. Select the account certificate that connects HCP to the CAP authentication endpoint. To see the account certificate in the dropdown field, it must already exist in the HCP system.
Optionally, any custom request headers that you want HCP to include in the access request URLs that are sent to Amazon S3 Web Services to request read or write access to the storage associated with the specified user account.
Whether you want to access existing buckets associated with the specified user account. If yes, enter the name of each existing bucket to access.
At any given time, a bucket can be associated with only one storage component.
You can add an existing bucket to an Amazon S3 storage component only if that bucket is empty or has only HCP data in it.
Whether you want to create any new buckets for the specified user account. If yes, enter the name of each new bucket to create.
NoteBy default, the Add Component wizard displays a list of the existing buckets that HCP can access using the specified user account credentials. However, the wizard does not display the controls required to create a new bucket. To create a new bucket, you must click Bucket Actions, select Create new from the dropdown list, and specify the name of the bucket you want to create.

Google Cloud storage component settings

Each Google Cloud component represents a single endpoint that’s used to access cloud storage using one or more Google Cloud Platform user accounts.

To enable HCP to access the storage that’s represented by a Google Cloud storage component, when you create that component, you specify the following information:

The component name.
Optionally, a description of the component.
Optionally, the network you want communicating with the storage component. This field is only visible if Virtual network management is enabled.
Whether you want HCP to use the default endpoint, storage.googleapis.com, to connect to Google Cloud Platform, and if not, the fully qualified domain name (FQDN) of the endpoint that you want HCP to use instead of the default.
Optionally, any of these advanced configuration settings:
- Whether you want HCP to use HTTPS to access the endpoint, and if so, the HTTPS port you want to use to connect to the endpoint (default is 443)
- The HTTP port you want to use to connect to the endpoint (default is 80)
- Whether you want to use a proxy server to connect to the endpoint, and if so, the following information about the proxy server:
  - The hostname or IP address of the proxy server
  - The port number you want to use to connect to the proxy server (default is 0)
  - The user name, password, and AD domain of the user account that HCP needs to use to access the proxy server
- Whether you want HCP to use path-style URLs to access the storage that’s represented by the storage component
- Whether the extended storage component supports S3 metadata on objects. If you are unsure whether S3 metadata is supported, contact your service provider.
- In the Max metadata size field, type the maximum size (in bytes) of the S3 metadata that will be attached to objects tiered to the storage component. Each extended storage service provider permits a different maximum size. Contact your service provider to learn the maximum size.
Whether the storage that’s represented by this component is considered to be compliant.
The account label that you want to associate with the initial Google Cloud Platform user account that you want HCP to use to access the storage that’s represented by the component. In the System Management Console, HCP uses the account label to represent the user account with the specified credentials.
The access key and secret key for the Google Cloud Platform user account that you want HCP to use to access the storage that’s represented by the component.
After you create a Google Cloud storage component, you can modify it to specify credentials for one or more additional user accounts.
Optionally, any custom request headers that you want HCP to include in the access request URLs that are sent to Google Cloud Platform to request read or write access to the storage associated with the specified user account.
Whether you want to access existing buckets associated with the specified user account, and if so, the name of each existing bucket you want to access.
At any given time, a bucket can be associated with only one storage component.
You can add an existing bucket to a Google Cloud storage component only if that bucket is empty or has only HCP data in it.
Whether you want to create any new buckets for the specified user account, and if so, the name of each new bucket you want to create.
NoteBy default, the Add Component wizard displays a list of the existing buckets that HCP is able to access using the specified user account credentials, but the wizard does not display the controls required to create a new bucket. To create a new bucket, you need to click Bucket Actions, then select Create new from the dropdown list, then specify the name of the bucket you want to create.

Microsoft Azure storage component settings

Each Microsoft Azure component represents a single endpoint that’s used to access cloud storage using one or more Microsoft Azure user accounts.

To enable HCP to access the storage that’s represented by a Microsoft Azure storage component, when you create that component, you specify the following information:

The component name.
Optionally, a description of the component.
Optionally, the network you want communicating with the storage component. This field is only visible if Virtual network management is enabled.
Whether you want HCP to use the default endpoint, blob.core.windows.net, to connect to Windows Azure, and if not, the fully qualified domain name (FQDN) of the endpoint that you want HCP to use instead of the default.
Optionally, any of these advanced configuration settings:
- You can display an advanced option that lets you specify whether to connect to Microsoft Azure using HTTPS. This option is enabled by default.
- Whether you want to use a proxy server to connect to the endpoint, and if so, the following information about the proxy server:
  - The hostname or IP address of the proxy server
  - The port number you want to use to connect to the proxy server (default is 0)
- Whether the extended storage component supports S3 metadata on objects. If you are unsure whether S3 metadata is supported, contact your service provider.
- In the Max metadata size field, type the maximum size (in bytes) of the S3 metadata that will be attached to objects tiered to the storage component. Each extended storage service provider permits a different maximum size. Contact your service provider to learn the maximum size.
Whether the storage that’s represented by this component is considered to be compliant.
The account label that you want to associate with the initial Microsoft Azure user account that you want HCP to use to access the storage that’s represented by the component. In the System Management Console, HCP uses the account label to represent the user account with the specified credentials.
The access key and secret key for the Microsoft Azure user account that you want HCP to use to access the storage that’s represented by the component.
After you create a Microsoft Azure storage component, you can modify it to specify credentials for one or more additional user accounts.
Optionally, any custom request headers that you want HCP to include in the access request URLs that are sent to Microsoft Azure to request read or write access to the storage associated with the specified user account.
Whether you want to access existing containers associated with the specified user account, and if so, the name of each existing container you want to access.
At any given time, a container can be associated with only one storage component.
You can add an existing container to a Microsoft Azure storage component only if that container is empty or has only HCP data in it.
Whether you want to create any new containers for the specified user account, and if so, the name of each new container you want to create.
NoteBy default, the Add Component wizard displays a list of the existing containers that HCP is able to access using the specified user account credentials, but the wizard does not display the controls required to create a new container. To create a new container, you need to click Container Actions, then select Create new from the dropdown list, then specify the name of the container you want to create.

S3 compatible storage component settings

Each S3 compatible component represents a single physical storage device or cloud storage service that’s used to access storage using a protocol that’s compatible with the Amazon S3 access protocol.

To enable HCP to access the storage that’s represented by an S3 compatible storage component, when you create that component, you specify the following information:

Optionally, the network you want communicating with the storage component. This field is only visible if Virtual network management is enabled.
The endpoint that HCP needs to use to access the physical device or cloud storage service that manages the storage that’s represented by this component.
Optionally, any of these advanced configuration settings:
- Whether you want HCP to use HTTPS to access the endpoint, and if so, the HTTPS port you want to use to connect to the endpoint (default is 443)
- The HTTP port you want to use to connect to the endpoint (default is 80)
- Whether you want to use a proxy server to connect to the endpoint, and if so, the following information about the proxy server:
  - The host name or IP address of the proxy server
  - The port number you want to use to connect to the proxy server (default is 0)
  - The user name, password, and AD domain of the user account that HCP needs to use to access the proxy server
- Whether you want HCP to use path-style URLs to access the storage that’s represented by the storage component
- Whether the extended storage component supports S3 metadata on objects. If you are unsure whether S3 metadata is supported, contact your service provider.
- In the Max metadata size field, type the maximum size (in bytes) of the S3 metadata that will be attached to objects tiered to the storage component. Each extended storage service provider permits a different maximum size. Contact your service provider to learn the maximum size.
Whether the storage that’s represented by this component is considered to be compliant.
The account label that you want to associate with the initial user account that you want HCP to use to access the storage that’s represented by the component. In the System Management Console, HCP uses the account label to represent the user account with the specified credentials.
The authentication type you want to use to authenticate all requests sent from HCP to the storage component.
The access key and secret key for the user account that you want HCP to use to access the storage that’s represented by the component.
After you create an S3 compatible storage component, you can modify it to specify credentials for one or more additional user accounts.
If you are using AWS STS or AWS STS V4 authentication, the authentication endpoint text field appears. This is the endpoint to which you send your credentials, in order to generate an authentication token.
Optionally, any custom request headers that you want HCP to include in the access request URLs that are sent to the target storage device or cloud service to request read or write access to the storage associated with the specified user account.
Whether you want to access existing buckets associated with the specified user account, and if so, the name of each existing bucket you want to access.
At any given time, a bucket can be associated with only one storage component.
You can add an existing bucket to an S3 compatible storage component only if that bucket is empty or has only HCP data in it.
Whether you want to create any new buckets for the specified user account, and if so, the name of each new bucket you want to create.
NoteBy default, the Add Component wizard displays a list of the existing buckets that HCP is able to access using the specified user account credentials, but the wizard does not display the controls required to create a new bucket. To create a new bucket, you need to click Bucket Actions, then select Create new from the dropdown list, then specify the name of the bucket you want to create.

NFS storage component settings

Each NFS storage component represents a single physical storage device on which one or more volumes are accessed using NFS mount points.

When you create an NFS storage component, you provide HCP with the information that it needs to create an NFS mount point for each volume that you want to access on the device that’s represented by the NFS storage component. However, HCP creates an NFS mount point that’s associated with a given storage component only when that mount point is added to an NFS storage pool.

When an HCP system is upgraded from release 6.x to release 7.0 or later, HCP automatically creates an NFS storage component and an NFS storage pool for each external volume that was configured on the HCP system before it was upgraded, and defines each NFS storage pool as a storage tier. For each namespace that was configured to use NFS storage before the upgrade, HCP automatically configures the service plan for that namespace to define the applicable NFS storage pool as a storage tier.

On the Hardware page of the System Management Console, HCP uses an external volume (also called an NFS volume) to represent the storage that’s accessed using a single NFS mount point that’s contained in an NFS storage pool. You can use the Storage page to view information about all NFS volumes stored on a single physical storage device that’s represented by an NFS storage component.

Creating NFS shares on a physical storage device

Before you can create an NFS storage component, you need to create and configure the NFS shares for the volumes you want to access on the physical storage device that’s represented by the component.

The main steps for creating NFS shares on a physical storage device for which you want to create an NFS storage component are:

Procedure

On the physical storage device, create the directories you want to share.
Export each directory as an NFS share.

Exports and required NFS component settings

Directories for export

For each storage volume you want to access on the physical storage device that’s represented by an NFS storage component, you need to create a directory on that physical storage device. For each directory, you need to set the permissions to allow read, write, and execute access to all users.

For example, on Linux systems, each directory you want to share must have its permissions set to 777.

Exported shares

Each directory that you want to mount as an NFS volume on an HCP node must be exported as an NFS share on the physical storage device that’s represented by the NFS storage component you want to create. To ensure that other systems and applications cannot mount the same storage, you should export each share exclusively to the HCP system. You can identify each the HCP system in one of three ways:

Using the fully-qualified domain name (FQDN) of the domain that’s associated with the [hcp_system] network, preceded by admin (for example, admin.hcp.example.com). This option is available only if the HCP system is using DNS.
By the CIDR notation for any IPv4 or IPv6 gateway that’s defined for the [hcp_system] network.
By the node IP addresses that the extended storage device needs to use to communicate with the [hcp_system] network. In this case, you need to export the share to the applicable IPv4 or IPv6 addresses for all the HCP nodes.
You need to export each share to all nodes because you cannot predict with which node HCP will associate the NFS storage volume you create for a share. If you omit a node and HCP associates a volume with that node, HCP has no access to the share for that volume.
If you use node IP addresses to identify the HCP system and you subsequently change any of those IP addresses in the [hcp_system] network, you need to update the export specification for the share with the new addresses. Then you need to export the share again.

The method you use to export the shares and the export options you specify depend on the type of storage device for which you want to create an NFS storage component. Minimally, the exported share must allow read and write access by the HCP system.

The following information on exporting shares on Linux systems is included for explanatory purposes only. The extended storage devices that are represented by NFS storage components should be enterprise-class, purpose-built appliances. The storage volumes that are accessed using NFS mount points should be on storage that’s RAID-protected, secure, and monitored closely for its health.

The extended devices that are represented by the NFS storage component must support the Linux file naming scheme. When using a non-Linux OS, you need to reconfigure mapping on the NFS storage device.

On Linux systems, you specify the shares to be exported in the /etc/exports file. To ensure that HCP correctly uses the NFS volumes that you make available to it, the specification of each exported share must minimally include these options:

rw,sync,no_wdelay

For example, to export the share named /hcp_shares/share1 to the HCP system with the domain name hcp.example.com, you would add this line to the /etc/exports file:

/hcp_shares/share1 admin.hcp.example.com(rw,sync,no_wdelay)

The export options in each line in the /etc/exports file must directly follow the system identifier with no space between them.

After you’ve specified the shares to exported, you use this command to export them:

exportfs -a

For information about how to export shares on non-Linux storage devices, see the device-specific documentation.

Required NFS storage component configuration settings

To enable HCP to access the storage that’s represented by an NFS storage component, when you create that component, you specify the following information:

The IP address or hostname that HCP needs to use to connect to the physical storage device on which you want to access storage volumes using NFS mount points.
The mount command options that you want HCP to use when it creates NFS mount points to access NFS shares on the device that’s represented by the component.
To ensure that NFS volumes are mounted correctly, HCP always uses these options to the mount command:
```
rw,sync,soft,nodev,nfsvers=3
```
HCP uses the options that you specify in addition to the above options. The additional options that you can specify are:
```
lookupcache=none
noatime
nodiratime
nosuid
port=n
retrans=n
rsize=n
tcp
proto=tcp6
timeo=n
wsize=n
```
Other mount command options are not supported.
If the [hcp_system] network is currently configured to use both IPv4 and IPv6 addresses, you need to specify tcp or proto=tcp6 to indicate which type of IP address you want HCP to use to connect to the NFS storage component.
The full pathname of each directory that you want to access using an NFS mount point.
NoteAt any given time, a mount point can be associated with only one NFS storage component.
By default, the Add Component wizard displays a list of the existing mount points that HCP is able to access using the specified user account credentials, but the wizard does not display the controls required to specify the pathname for an existing NFS share. To specify a directory that does not appear in the list, you need to click Mount Point Actions, then specify the full path name of the directory for which you want to create an NFS mount point.

Modifying an extended storage component

You can use the Components panel on the Storage page to view and modify the configuration of any extended storage component. To display this panel, click the Components tab on the left side of the Storage page.

You can modify the following items associated with an extended storage component:

Change one or more of the configuration settings that are specified when the component is first created.
Modify one or more of the default values for the advanced settings used for the extended storage component. Each type of extended storage component has slightly different advanced settings.
Typically, you do not need to change any of the default values that are used for the advanced settings for an extended storage component.
Add a new access point (a mount point, bucket, or container) to an existing storage component.
Delete any access point that’s not currently in use.
For all types of extended storage components except NFS:
- Configure a new user account to be used to access the cloud storage service endpoint or S3 compatible storage device endpoint that’s represented by the component.
- Delete any user account that’s not currently in use.

Modifying the configuration settings that are specified for an extended storage component

Before you begin

To view the Storage page, you need the monitor or administrator role. To create, modify, or delete extended storage components and extended storage pools, you need the administrator role.

Procedure

On the left side of the Storage page, click the Components tab.
On the Components panel, click the table row that contains the name of the component that you want to modify.
At the top of the panel that opens, click the Settings tab.
On the panel that opens, use the fields to change any of the settings that are currently used for the component.
Click Update Settings.

Modifying the advanced configuration settings that are used for an extended storage component

Before you begin

To view the Storage page, you need the monitor or administrator role. To create, modify, or delete extended storage components and extended storage pools, you need the administrator role.

Procedure

On the left side of the Storage page, click the Components tab.
On the Components panel, click the table row that contains the name of the component that you want to modify.
At the top of the panel that opens, click the Advanced tab.
On the panel that opens, use the fields to change any of the settings that are currently used for the component or click Reset Advanced Settings to change all advanced settings to use the default values.
Click Update Settings.

Adding access points to an extended storage component

Before you begin

To view the Storage page, you need the monitor or administrator role. To create, modify, or delete extended storage components and extended storage pools, you need the administrator role.

Procedure

On the left side of the Storage page, click the Components tab.
On the Components panel, click the table row that contains the name of the component for which you want to configure one or more new access points.
At the top of the panel that opens, click the tab that corresponds to the type of access point that’s used for the component (Mount Points, Buckets, or Containers).
At the bottom of the panel that opens, click Add AccessPointType.
For every type of extended storage except NFS, in the window that opens, use the dropdown list to select the account label that’s associated with the user account that’s used to access the bucket or container you want to add, and click Go. The window does not appear if you’re adding a mount point to an NFS storage component.

The Add AccessPointType wizard opens, displaying a table that contains a list of existing access points (mount points, buckets, or containers) that are available for use, along with a check box that corresponds to each access point in the list.
Click AccessPointType Actions.
Take either or both of these actions:

To add existing access points to the storage component:
1. In the AccessPointType Actions section, in the Action field, select Add existing.
  When you first expand the AccessPointType Actions section, Add existing is selected by default.
2. Use the check boxes in the left column in the table to select each existing access point that you want to add to the storage component configuration.
3. Click Go.
To create one or more new buckets or containers for use by the specified user account or to create one or more mount points:
1. In the AccessPointType Actions section, in the Action field, select Create new.
2. In the AccessPointTypeName field, for each new access point you want to create, type a name for the new access point, and click Go.
  Each new access point you create is added to the list of existing access points, and its checkbox is automatically selected.
  NoteYou can delete any new access point from the list before you actually create the new access point on the extended storage device. To do this, click the delete control ( ) in the row that corresponds to the access point name.
3. When you’re finished creating new access points, in the Action field, select Add existing, and then click Go.
When you’re finished adding both new and existing access points to the extended storage components, click Finish at the bottom of the panel.

When you click Finish, the Add AccessPointType wizard exits, and the AccessPointType panel (Mount Points, Buckets, or Containers) for the storage component you’ve modified is displayed, showing the list of access points that are currently configured for the component and the current status of each access point. All of the new and existing access points you’ve just added are included in the list.

Configuring a new user account for access to an extended storage endpoint

You can configure a new user account to be used to access any cloud storage service endpoint or S3 compatible storage device endpoint that’s represented by an extended storage component.

Before you begin

To view the Storage page, you need the monitor or administrator role. To create, modify, or delete extended storage components and extended storage pools, you need the administrator role.

Procedure

On the left side of the Storage page, click the Components tab.
On the Components panel, click the table row that contains the name of the component for which you want to configure a new user account.
At the top of the panel that opens, click the tab that corresponds to the type of access point that’s used for the component (Buckets or Containers).
At the top of the Buckets or Containers panel, click the Accounts tab.
At the bottom of the Accounts panel, click Add Account.

The Add Account wizard opens.
In the Add Account wizard, specify the following information to configure the new user account:
- The account label that you want HCP to use to identify the user account in the System Management Console
- The access key and secret key that HCP needs to use to access the new user account
- For S3 compatible storage components, the authentication type you want to use to authenticate all requests sent from HCP to the storage component
- Optionally, any custom request headers that you want HCP to include in the access request URLs that are sent to the cloud storage service or storage device that’s represented by the storage component in order to request read or write access to the storage associated with the new user account
Click Finish.

When you click Finish, the Add Account wizard exits, and the AccessPointType panel (Buckets or Containers) for the storage component you’ve modified is displayed, showing the list of user accounts that are currently configured for the component and the current status of each account. The new and user account you’ve just added is included in the list.

Updating the owner of a bucket in an extended storage component

Before you update the owner of a bucket or container in an extended storage component, make sure you have configured a new user account for access to any cloud storage service endpoint or S3 compatible storage device endpoint represented by an extended storage component. This procedure is not applicable to NFS components.

Before you begin

To view the Storage page, you need the monitor or administrator role. To create, modify, or delete extended storage components and extended storage pools, you need the administrator role.

Procedure

On the left side of the Storage page, click the Components tab.
Click the component you want.
Click the tab for the applicable type of access point (Buckets or Containers).
Click the Buckets or Containers tab, as applicable.
Click the bucket or container that you have created and want to update.
In the Select Account section that opens, select the account that you want to own the bucket.
Click Continue.

Deleting an unused access point from an extended storage component

Before you begin

To view the Storage page, you need the monitor or administrator role. To create, modify, or delete extended storage components and extended storage pools, you need the administrator role.

Procedure

On the left side of the Storage page, click the Components tab.
On the Components panel, click the table row that contains the name of the component from which you want to delete an unused access point.
At the top of the panel that opens, click the tab that corresponds to the type of access point that’s used for the component (Mount Points, Buckets, or Containers).

The AccessPointType panel opens, showing a list of access points that are currently configured for the component. A delete control (

) appears in the row for each unused access point.
Click the delete control for any access point to delete it from the component.

Deleting an unused user account from an extended storage component

Before you begin

To view the Storage page, you need the monitor or administrator role. To create, modify, or delete extended storage components and extended storage pools, you need the administrator role.

Procedure

On the left side of the Storage page, click the Components tab.
On the Components panel, click the table row that contains the name of the component from which you want to delete an unused user account.
At the top of the panel that opens, click the tab that corresponds to the type of access point that’s used for the component (Buckets or Containers).
At the top of the Buckets or Containers panel, click the Accounts tab.

The Accounts panel opens, showing a list of user accounts that are currently configured for the component. A delete control ( ) appears in the row for each unused user account.
Click the delete control for any user account to delete it from the component.

Uploading an account certificate for CAP authentication

The C2S CAP server acts as an intermediary between HCP and AWS STS authentication. CAP looks up the user's S3 credentials based off HCP account credentials sent to CAP. If the check passes, CAP then sends the S3 credentials to a predefined AWS STS endpoint. STS, in turn, issues a temporary token which CAP sends back to HCP.

C2S CAP authentication can only be used with the S3 compatible component. In order to use C2S CAP authentication you need to provide an account certificate.

Before you begin

To view the Storage page, you need the monitor or administrator role. To create, modify, or delete extended storage components and extended storage pools, you need the administrator role.

Procedure

On theStorage Certificates & Keys page, under the Account Certificates panel, click Browse and navigate to the location of your C2S CAP authentication certificate.
Click Upload Certificate.
Click Next.
Review your certificate information.
Click Finish.

NoteIn order to upload a account certificate, you need the administrator role.

Pausing and resuming an extended storage component

When an extended storage component is in use, you can pause all read and write operations on the associated extended storage at any time.

In certain situations, the storage that is represented by an extended storage component might become temporarily inaccessible. Reasons for the temporary inaccessibility can include scheduled maintenance or an unforeseen problem with an extended storage device or cloud-storage-service endpoint. If this situation occurs, you might need to temporarily pause all read and write operations on the storage component.

While a storage component is paused, the associated extended storage is unavailable for storage tiering and does not attempt to communicate with that device or service. Any alerts that would normally be generated by attempts to communicate with the inaccessible extended storage device or cloud-storage-service endpoint are not displayed when the component is paused. When an extended storage component is resumed, the associated storage becomes available for storage tiering, and HCP resumes attempting to communicate with the extended storage device or cloud storage endpoint. If such attempts fail, HCP displays the applicable alerts on the Components panel on the Storage page.

Before you begin

To view the Storage page, you need the monitor or administrator role. To create, modify, or delete extended storage components and extended storage pools, you need the administrator role.

Procedure

On the left side of the Storage page, click the Components tab.
On the Components panel, click the table row that contains the name of the component that you want to pause or resume.
At the top of the panel that opens, click the Manage tab.
On the Manage panel, take one of these actions:
- To pause a component, click Pause Component. HCP pauses the component, and the panel displays Resume Component.
- To resume a component that is currently paused, click Resume Component. HCP attempts to resume communications with the component, and the panel displays Pause Component.

Deleting or abandoning an extended storage component

If the storage that’s represented by an extended storage component is not currently being used to store objects in any namespaces defined on the HCP system, you can safely delete that storage component.

If, however, the storage that’s represented by an extended storage component is currently being used to store object data, you cannot delete that component. Instead you need to either retire that component or abandon it.

When you retire an extended storage component, HCP migrates the data off that component and then deletes that component from the system.

When you abandon an extended storage component, HCP deletes that component from the system without attempting to migrate any of the stored data off the extended storage component. This operation is not recommended because it may result in data loss. If the only existing copies of the data for a given object are stored on a single extended storage component, when you abandon that component, the object data becomes permanently inaccessible to HCP.

Retiring and deleting a component is a much safer alternative to abandoning that component, as retiring a component ensures that the data stored on that component remains protected at the applicable levels. You should consider abandoning an extended storage component only as a last resort and only after you’ve taken the necessary steps to ensure that the data stored on the component exists elsewhere in the HCP system.

Deleting an unused extended storage component

Before you begin

To view the Storage page, you need the monitor or administrator role. To create, modify, or delete extended storage components and extended storage pools, you need the administrator role.

Procedure

On the left side of the Storage page, click the Components tab.
On the Components panel, click the table row that contains the name of the component that you want to delete.
At the top of the panel that opens, click the Manage tab.
On the Manage panel, click Delete Component.

Abandoning an extended storage component

Before you begin

To view the Storage page, you need the monitor or administrator role. To create, modify, or delete extended storage components and extended storage pools, you need the administrator role.

Procedure

On the left side of the Storage page, click the Components tab.
On the Components panel, click the table row that contains the name of the component that you want to abandon.
At the top of the panel that opens, click the Manage tab.
On the Manage panel, click Abandon Component.

Quick Links

Creating an extended storage component

Amazon S3 storage component settings

Google Cloud storage component settings

Microsoft Azure storage component settings

S3 compatible storage component settings

NFS storage component settings

Creating NFS shares on a physical storage device

Exports and required NFS component settings

Modifying an extended storage component

Modifying the configuration settings that are specified for an extended storage component

Modifying the advanced configuration settings that are used for an extended storage component

Adding access points to an extended storage component

Configuring a new user account for access to an extended storage endpoint

Updating the owner of a bucket in an extended storage component

Deleting an unused access point from an extended storage component

Deleting an unused user account from an extended storage component

Uploading an account certificate for CAP authentication

Pausing and resuming an extended storage component

Deleting or abandoning an extended storage component

Deleting an unused extended storage component

Abandoning an extended storage component