此内容没有您所选择的语言版本。
Chapter 2. Configuring the Fujitsu ETERNUS device
Configure storage pools and ports on the device before you define the Fujitsu ETERNUS device as a Block Storage back end. Consult your device documentation for details on each step:
Procedure
- Configure a LAN connection between the Controller nodes that host the Block Storage service and the MNT ports of the ETERNUS device.
- Configure a SAN connection between the Compute nodes and CA ports of the ETERNUS device.
-
Log in to the ETERNUS device using an account with the
Admin
role. - Enable the SMI-S of ETERNUS DX.
- Set the SSH key
-
Add a user account with
software
role. -
Register an
Advanced Copy Feature
license and configure the copy table size. -
Create a storage pool for volumes. You use this pool later in the
EternusPool
setting in Section 3.1, “Creating driver definitions for each Fujitsu ETERNUS back end”. -
Optional: Create a separate storage pool for volume snapshots. This pool represents the
EternusSnapPool
setting in Section 3.1, “Creating driver definitions for each Fujitsu ETERNUS back end”. Optional: Create a
Snap Data Pool Volume (SDPV)
to enable Snap Data Pool (SDP) for thecreate a snapshot
function.TipSkip this step if you use a Thin Provision Pool for
EternusSnapPool
.-
Configure
storage ports
to be used by the Block Storage service. -
Set the
storage ports
ports toCA
mode. To enable
host-affinity
for the storage ports, enter the following command from the ETERNUS CLI for each port:set <PROTO>-parameters -host-affinity enable -port <CM#> <CA#> <PORT>
-
Replace <PROTO> with the storage protocol, such as
fc
oriscsi
. - Replace <CM#> and <CA#> with the name of the controller enclosure where the port is located.
- Replace <PORT> with the port number.
-
Replace <PROTO> with the storage protocol, such as
Use the following commands to generate the SSH key on the undercloud, and upload the
eternus.ietf
file to the ETERNUS device.ssh-keygen -t rsa -N "" -f ./eternus ssh-keygen -e -f ./eternus.pub > ./eternus.ietf
NoteSave the
eternus
file for later use. For security reasons, do not copy or move it from the undercloud or overcloud.