...
Download the
Spacevars | ||
---|---|---|
|
Code Block |
---|
cd /opt/ wget ftp://$url_from_support wget ftp://$url_from_support |
Enable read-write-execute permissions for the copied files using the command given below:
Code Block |
---|
chmod +x cluster-install-ev.sh |
To execute the installation process, use the following command:
Code Block |
---|
./cluster-install-ev.sh |
The installation procedure will begin. Please provide input as prompted by the console output during the installation process.
The installation creates a log file of all the performed actions for historical review/troubleshooting. The name of this file is $MM-DD-YYYY-ev-install.log.
You are prompted to enter information related to your networking configuration. Please read this section carefully and provide appropriate values for your network environment.
Once the installation is complete, the console screen displays the following message:
“
Spacevars | ||
---|---|---|
|
A directory named scc-build is created.
All the services start and all replica-expected-values reach their target (for example 1/1 or 5/5) over the next several minutes. To validate, run the following command:
Code Block |
---|
docker service ls |
Tip | ||
---|---|---|
| ||
Make sure that the replicas are all meeting their targets – for example, 1/1 or 5/5. If they are not, run the following command and check the Health section of the output using the following command:
|
Spacevars | ||
---|---|---|
|
Spacevars | ||
---|---|---|
|
Spacevars | ||
---|---|---|
|
...
Download the
Spacevars | ||
---|---|---|
|
Code Block |
---|
cd /opt/ wget ftp://$url_from_support wget ftp://$url_from_support |
Enable read-write-execute permissions for the copied files using the commands given below:
Code Block |
---|
chmod +x cluster-install-ev.sh |
Execute the following command to start the installation process:
Code Block |
---|
./cluster-install-ev.sh |
The installation creates a log file of all actions for historical review/troubleshooting using the file format: $MM-DD-YYYY-ev-install.log. When prompted, enter validation or update information related to your networking configuration environment. Once the installation completes, the console screen displays the message “
Installation/Upgrade Completed”. Spacevars 0 product
To check whether the containers started successfully, use the following command:
Code Block |
---|
docker service ls |
All the services start and all replica-expected-values reach their target (for example 1/1 or 5/5) over the next several minutes.
Example:
...
Linux systems should be updated and patched for security require security updates and patches on a regular basis. When running When
is run in HA mode, apply patches may be applied as required in the environment. Take care to Update only update one member of the cluster at a time to ensure the availability of the application. After each node update, verify that all services return to a healthy state before moving to the next. Spacevars 0 product
Info | ||||
---|---|---|---|---|
| ||||
|
For more information, refer to Storidge Node Maintenance.
To safely evict all services before performing maintenance on a node, execute the following command:
Code Block |
---|
cioctl node cordon |
This command puts the node in drain state so services are rescheduled. The node is then isolated from other nodes in the cluster.
Identify the name of the node you need to cordon. List the nodes in the cluster using the following command:
Code Block |
---|
cio node ls |
For CIO to cordon the node, execute the following command:
Code Block |
---|
cioctl node cordon NODENAME |
In the cordoned state, a node is temporarily isolated from the rest of the cluster. Change block tracking is engaged to track updates that are destined for the cordoned node. This enables fast rebuilds when the node is rejoined to the cluster. When the cioctl node cordon command returns, proceed with maintenance. Perform desired CIO software upgrades, driver updates, hardware replacements, and package updates.
After the node maintenance is completed, run reboot to clean state the node. This step is optional
Restore the node to full operation after maintenance is complete, using the following command:
Code Block |
---|
cioctl node uncordon NODENAME |
The uncordoned node rejoins the cluster and exits drain state.
Repeat these steps for each node in the cluster until all member nodes are upgraded.
Steps to migrate data from existing
system (for Spacevars 0 product
versions 15.1.0 and higher) to Storidge Cluster: Spacevars 0 product
To install Storidge in single-node configuration on the source system, run the following commands:
Code Block |
---|
curl -fsSL http://download.storidge.com/pub/ce/cio-ce | sudo bash cioctl create --single-node |
Spacevars | ||
---|---|---|
|
Create Storidge profile on the single node system:
Code Block |
---|
cd scc-build/; cio profile create storidge-profile |
Copy root ssh key from single node to root authorized keys on sds node:
Code Block |
---|
cat /root/.ssh/id_rsa.pub ; vim /root/.ssh/authorized_keys |
Paste the key from other server.
Convert the local docker volumes to remote cio volumes in a single command:
Code Block |
---|
cioctl migrate docker $LOCAL_DOCKER_VOLUME $REMOTE_CIO_VOLUME -p storidge-profile -v --ip $INTERNAL_IP_SDS_NODE_REMOTE |
The remote name should match the naming convention in the cluster.
Example: ev_mysql_data for things to work seamlessly.
Spacevars | ||
---|---|---|
|
...