CPU
|
1 core or more
|
Memory
|
4 GiB or more
|
Free system disk space
|
10 GiB or more*
|
* Note the following when configuring an EBS to be
used as a system disk.
-
Any volume type can be used. However, if you leave the
IOPS or throughput (MB/sec) settings blank, an error
might occur.
Example: When using a general purpose SSD (gp3), set IOPS
to 3000 and set the throughput (MB/sec) to 125.
-
More free space is required when performing the following
operations on the controller node:
- If you are collecting dump log files according to Procedure for collecting VSP One SDS Block dump log
files in the VSP One SDS Block Troubleshooting Guide, additional
free space of 13 GiB or more is required for each
storage node comprising the storage cluster.
- If you are collecting dump log files including performance information
according to Procedure for
obtaining performance information of VSP One SDS Block
in the VSP One SDS Block Troubleshooting Guide,
additional free space of 90 GiB or more is required
for each storage cluster.
- If you are instructed by customer support to collect
dump log files with the mode set to "All",
additional free space of 150 GiB or more is required
for each file.
-
If free capacity becomes insufficient after starting operation, perform
either a or b, as follows:
- a. When you create a new EBS volume and attach
it, see the following website.
-
-
Creating an Amazon EBS volume
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-creating-volume.html
-
Attaching an Amazon EBS volume to an
instance
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-attaching-volume.html
-
Making an Amazon EBS volume available on
Linux
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-using-volumes.html
- b. When you expand a system volume capacity, see
the following website:
- https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-modify-volume.html
|