Add_workflow_for_techpubs |
---|
AUTH1 | UserResourceIdentifier{userKey=8a00a0c86ca23f8a016cd6ed6fe90013, userName='null'} |
---|
REV5 | UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'} |
---|
REV6 | UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'} |
---|
REV3 | UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'} |
---|
REV1 | UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'} |
---|
|
...
- Five CentOS 7 or Ubuntu 18 Virtual Machines
- These should be dedicated virtual machines with unique hostnames and with no other production applications running on them. Base OS packages should be installed and updated to the latest versions.
- Requires an active internet connection. This is used to automatically install and configure software dependencies.
- Should not have any pre-existing OS level firewall rules (iptables).
- vCPU/Core: 8
- Example: Intel(R) Xeon(R) Platinum 8175M CPU @ 2.50 GHz
- RAM: 8 GB
- NIC Interface: 1
- Disks mounted to each Virtual Machine: 4
- Host OS: 100 GB minimum
- 3x disks for Docker storage: 100 GB minimum each per VM (this will grow as you add data to the system over time)
- Disk space monitoring and alerting configured at safe threshold (for example, 80% used capacity)
- Ability to expand disk space when it reaches the threshold
- Docker version 19.03.4
- Stordige version Storidge version 1.0.0-30853186
Info |
---|
|
This is the minimum recommendation for initial installation. You will need to monitor your network environment and add additional CPU, RAM, and Disk space as required. |
...
In order to provide a concrete example of how to proceed, documented below is an example set of servers. It’s recommended that you make a similar document for your environment so that you can reference it later. We use references from this table in the following install installation instructions.
Hostname | IP Address | Swarm Role | Storidge Role | Notes |
---|
prod-ev-cluster-1 | 10.10.10.1 | Manager | SDS | Primary and install files located here |
prod-ev-cluster-2 | 10.10.10.2 | Manager | Backup 1 | — |
prod-ev-cluster-3 | 10.10.10.3 | Manager | Backup 2 | — |
prod-ev-cluster-4 | 10.10.10.4 | Worker | Storage | — |
prod-ev-cluster-5 | 10.10.10.5 | Worker | Storage | — |
Install Storidge
To install Storidge, perform the following steps using an SSH client such as PuTTY:
SSH into each of the five servers and run the following command to install the Storidge software:
Code Block |
---|
$ curl -fsSL ftp://104.131.153.182/pub/ce/cio-ce | sudo bash -s -- -f -r 3085 |
Wait for the above command to finish its execution successfully. It is expected to take several minutes.
On the first node (primary node) in the cluster, run the following command:
Code Block |
---|
$ cioctl create |
Copy the join command and run that on the rest of the nodes in the cluster (nodes 2 to 5).
For example:
Code Block |
---|
$ cioctl node add 10.10.10.1 3b6ca81e9370a228c7fc8 edbfa3c6361-3aff2bb8 |
Once you have added all your nodes to the cluster, return to the primary node and initialize the cluster with the ‘cioctl init’ command that was displayed after running the ‘cioctl create’ command.
For example:
Code Block |
---|
$ cioctl init e2e14943 |
You can now see the cluster form. This may take several minutes.
To verify that all five nodes are present and that their status is ‘normal’, run the following command:
Install
...
Download the
artifacts ‘cluster-install-ev.sh’ and ‘ev-fullpkg.tar.xz’ to the /opt directory of the primary node (reach out to support@rbbn.com for the URLs of these artifacts. Also note that you will need an HA license to utilize this functionality).
wget ftp://$url_from_support |
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:
“EdgeView Installation/Upgrade Completed”
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: Code Block |
---|
docker service ps $service_name –no-trunc |
|
- For the initial SCC configuration, register your server by accessing it through the web interface at its IP address and entering the registration information that you received in your email. If you didn’t receive the registration information, reach out to support@rbbn.com.
- Enter the admin registration details and click NEXT.
- Enter the Tenant admin registration details and click NEXT.
- Click APPLY to complete the registration.
- Click LOGIN to navigate to the login screen.
- Enter the credentials and click SIGN IN to log in to .