euca-describe-services -Eand note the state and status message of the Storage Controller(s). The output for an unconfigured SC will look like:
SERVICE storage PARTI00 SC71 BROKEN 37 http://192.168.51.71:8773/services/Storage arn:euca:eucalyptus:PARTI00:storage:SC71/ SERVICEEVENT 6c1f7a0a-21c9-496c-bb79-23ddd5749222 arn:euca:eucalyptus:PARTI00:storage:SC71/ SERVICEEVENT 6c1f7a0a-21c9-496c-bb79-23ddd5749222 ERROR SERVICEEVENT 6c1f7a0a-21c9-496c-bb79-23ddd5749222 Sun Nov 18 22:11:13 PST 2012 SERVICEEVENT 6c1f7a0a-21c9-496c-bb79-23ddd5749222 SC blockstorageamanger not configured. Found empty or unset manager(unset). Legal values are: das,overlay
euca-describe-properties | grep blockstorage
This was the default configuration option for the SC in pre-3.2 Eucalyptus. In this configuration the SC itself hosts the volume and snapshots for EBS and stores them as files on the local filesystem. It uses standard linux iSCSI tools to serve the volumes to instances running on NCs.
euca-modify-property -p <partition>.storage.blockstoragemanager=overlayThe output of the command should be similar to:
PROPERTY PARTI00.storage.blockstoragemanager overlay was <unset>
euca-describe-properties | grep blockstorage
euca-modify-property -p <partition>.storage.blockstoragemanager=equallogicThe output of the command should be similar to:
PROPERTY PARTI00.storage.blockstoragemanager equallogic was <unset>
euca-describe-properties | grep blockstorage
euca_conf --list-scs
euca-modify-property -p [partition_name].storage.sanhost=[SAN_IP_address] euca-modify-property -p [partition_name].storage.sanuser=[SAN_admin_user_name] euca-modify-property -p [partition_name].storage.sanpassword=[SAN_admin_password]
euca-modify-property -p <partition>.storage.blockstoragemanager=dasThe output of the command should be similar to:
PROPERTY PARTI00.storage.blockstoragemanager das was <unset>
euca-describe-properties | grep blockstorage
euca_conf --list-scs
euca-modify-property -p <cluster name>.storage.dasdevice=<device name>
euca-modify-property -p cluster0.storage.dasdevice=/dev/sdb
NoteBy default Eucalyptus assumes aggr1 as
the aggregate name. If you wish to use a different
aggregate see step 13.
|
euca-modify-property -p <partition>.storage.blockstoragemanager=netappThe output of the command should be similar to:
PROPERTY PARTI00.storage.blockstoragemanager netapp was <unset>
euca-describe-properties | grep blockstorage
euca_conf --list-scs
euca-modify-property -p [partition_name].storage.sanhost=[SAN_IP_address] euca-modify-property -p [partition_name].storage.sanuser=[SAN_admin_user_name] euca-modify-property -p [partition_name].storage.sanpassword=[SAN_admin_password]
euca-modify-property -p <partition_name>.storage.aggregate=<SAN_aggregate_name>
ImportantYou must create a clone private LUN (CPL) of at least 1GB on each SP. For
more information on creating private LUNs, go to Allocating clone private LUNs.
|
ImportantEucalyptus currently supports
version 7.32.0.5.54 or later of the Navisphere
CLI.
|
/opt/Navisphere/bin/naviseccli -User <your SAN username> -Password <your SAN password> -Scope 0 -Address <management port IP> connection -pingnode -address <a data port IP on your VNX>Verify that the command runs successfully and the ping gets replies from the SAN.
euca_conf --list-scs
euca-modify-property -p <partition>.storage.blockstoragemanager=emc-vnxThe output of the command should be similar to:
PROPERTY PARTI00.storage.blockstoragemanager emc-vnx was <unset>
euca_conf --list-scs
euca-modify-property -p [partition_name].storage.sanhost=[SAN_IP_address] euca-modify-property -p [partition_name].storage.sanuser=[SAN_admin_user_name] euca-modify-property -p [partition_name].storage.sanpassword=[SAN_admin_password]
euca-modify-property -p <partition_name>.storage.loginscope=<login_scope>
euca-modify-property -p <partition_name>.storage.chapuser=<chap_username>
euca-modify-property -p <partition_name>.storage.storagepool=0
euca-modify-property -p <partition_name>.storage.ncpaths=<ip>
euca-modify-property -p <partition_name>.storage.scpaths=<ip>
euca-modify-property -p <partition_name>.storage.clipath=/opt/Navisphere/bin/naviseccli
TipNote: The time it takes for a LUN migration to
complete will depend on the exact VNX model, workload, and
volume size, and the amount of data actually stored in the
volume. The default timeout for LUN migrations is 12
hours. If your deployment uses volumes >50GB, or if you
find that snapshots fail and a "migration timeout" message
is seen in the SC logs, then you should increase the timeout
to a larger value. It is recommended that if you plan on
using volumes in the 100GB range that you set that timeout
to 3600 or larger. You can set the timeout using
euca-modify-property as follows:
euca-modify-property -p [partition].storage.lunmigrationtimeout=[time in hours] |