Creating drives (Cloud)

Virtual Storage Platform One SDS Block Storage Administrator Guide

Version

1.17.x

Audience

anonymous

Part Number

MK-24VSP1SDS002-04

CAUTION:

When you perform the following maintenance operations, do not perform multiple operations for the same storage cluster simultaneously.
- Adding storage nodes
- Replacing storage nodes
- Exporting the configuration file
- Adding drives
- Replacing drives
If you are using EBS encryption, you must add rights to access AWS Key Management Service to an IAM role to be set in the account or controller node for operating AWS. For details, see the AWS user guide.

Note:

When the Floating base license is applied, see Requirements for addition of drives (Cloud) to verify whether the storage pool logical capacity after adding drives is within the licensed capacity of the AWS License Manager license.

Configuration files are used for drive addition. Configuration file export can be performed by logging in to the controller node and then operating a VSP One SDS Block installer similarly with the operation for drive replacement.

Required role: Security, Storage, Monitor, Service, or Resource
The VSP One SDS Block installer must be installed on the controller node intended for use.

Note on the procedure

In the following procedure, long command lines begin on a new line delimited by "\". You can copy and paste command lines including "\" for normal operation.
The procedure in this section uses AWS CLI to perform operations. However, you can use the AWS CloudFormation console of the AWS Management Console to confirm the CloudFormation stack status or operation status.
Recording console outputs (for example, by using script command, redirecting operation, or tee command) can help to confirm the execution result or handle errors.

Log in to the controller node.
Run the following AWS CLI command to verify the current number of drives per storage node.
```
aws cloudformation describe-stacks \
--stack-name <stack-name-set-during-installation-from-Marketplace> \
--query Stacks[0].Parameters
```
Verify the value of "ParameterValue" for the items whose "ParameterKey" is "DriveCount."
See Exporting the configuration file (Cloud) to obtain configuration files from VSP One SDS Block for drive addition.

To perform configuration file export, verify to specify "AddDrives" for the --mode option. You must specify a number larger than the number of drives confirmed in step 2 for the --total_drive_counts option. This step is mandatory and ensures that you use the latest configuration files.

CAUTION:

Do not edit the configuration files you obtained for configuration file export. If you do so, drive addition might be unsuccessful. If you specified an incorrect value, set the correct value, and then retry configuration file export.
Store the set of configuration files obtained by configuration file export to the Amazon S3 bucket you specified for the --template_s3_url option in step 3.
One way to store files in Amazon S3 is to copy the file to Amazon S3 by using the AWS CLI, for example. For details, see Example Amazon S3 operations in the VSP One SDS Block Cloud Setup and Configuration Guide.
CAUTION:

Do not include periods (.) in the name of the Amazon S3 bucket to which VM configuration files are to be stored.

Run the following AWS CLI command to create a change set.

aws cloudformation create-change-set \
--stack-name <stack-name-set-during-installation-from-Marketplace> \
--change-set-name <any-change-set-name*> \
--template-url <Amazon-S3-URL(https)-of-VMConfigurationFile.yml> \
--include-nested-stacks \
--capabilities CAPABILITY_NAMED_IAM

* For details about the characters that can be used, see the following website.

https://docs.aws.amazon.com/cli/latest/reference/cloudformation/create-change-set.html

Run the following AWS CLI command to view the change set (first layer).
```
aws cloudformation describe-change-set \
--stack-name <stack-name-set-during-installation-from-Marketplace> \
--change-set-name <change-set-name-specified-in-step-5>
```
Verify the following.
- "Status" must be "CREATE_COMPLETE."
  
  If "Status" is "CREATE_IN_PROGRESS", wait for a while, and then retry the operation.
- The number of items in "Changes" must be one.
- About "ResourceChange" in "Changes":
  - "Action" must be "Modify."
  - The value of "LogicalResourceId" must be as follows.
    - For HPEC 4D+2P: StorageCluster4D2P
    - For Mirroring Duplication: "StorageClusterDuplication"
  - Note down the value of "ChangeSetId" to perform the next step.
Run the following AWS CLI command to view the change set (second layer).
```
aws cloudformation describe-change-set \
--change-set-name <ChangeSetId-recorded-in-step-6>
```
Verify the following.
- The number of items in "Changes" must be one.
- The number of items in "ResourceChange" is no less than the number of storage nodes^*.
  
  * In Multi-AZ configuration, the tiebreaker node, which does not have capacity (no drives exist), is not included in the number of storage nodes.
- Note down the value of "ChangeSetId" to perform the next step.
Run the following AWS CLI command to view the change set of stacks for each storage node (third layer).
```
aws cloudformation describe-change-set \
--change-set-name <ChangeSetId-recorded-in-step-7>
```
Verify the following.
- About "ResourceChange" for each item in "Changes":
  - For the items whose "Action" is "Add", "LogicalResourceId" must be "VolumeAttachmentXX" or "UserDataDiskXX" (where XX is the drive number to be created).
  - "Action" for all other items must be "Modify." (No item with "Remove" exists.)

Run the following AWS CLI command to execute the created change set.

aws cloudformation execute-change-set \
--stack-name <stack-name-set-during-installation-from-Marketplace> \
--change-set-name <change-set-name-specified-in-step-5>

Run the following AWS CLI command to verify the execution result of the change set.
If you run "wait stack-update-complete", you can wait until the change-set execution completes.
```
aws cloudformation wait stack-update-complete \
--stack-name <stack-name-set-during-installation-from-Marketplace>
```
After the change-set execution completes, run "describe-stacks" to verify whether "StackStatus" is "UPDATE_COMPLETE."
```
aws cloudformation describe-stacks \
--stack-name <stack-name-set-during-installation-from-Marketplace>
```
Obtain a list of drives to verify that drives have been added to the storage node to be added.

Use the query parameter to specify the ID of each storage node, and then run either of the following commands.

REST API: GET /v1/objects/drives

CLI: drive_list

Confirmation of the added drives might take approximately one minute. If the added drives cannot be verified, see Action to be taken when added drives cannot be recognized in the VSP One SDS Block Troubleshooting Guide to take appropriate action.