HA and Large Scale Deployment

Overview

EdgeView15 can be deployed in a clustered configuration. This provides the following functionalities in addition to all the features provided by a traditional single node deployment:

• Automatic system recovery from failures or planned infrastructure maintenance with minimal application disruption.
• Supports large scale deployments in excess of 100,000 connected EdgeMarc devices with horizontal and vertical scaling. 

The following technologies are implemented to provide the mentioned functionalities:

• Container orchestration to schedule and scale our microservices across a cluster of hosts.
• Storage abstraction layer for stateful applications, to store, replicate and provide failover capabilities for persistent data.

The following diagram represents the deployment model.

Requirements

Minimum Requirements

• 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.8
• Storidge version 1.0.0-3186

Network Port Requirements

The following ports should be open for successful HA EdgeView installation:

• 80, 443 for HTTP/HTTPS

Inbound (EdgeView GUI access and initial ZTP connection from EdgeMarc)

• 5671 for EMPath

Inbound (RabbitMQ communication between EdgeMarc and EdgeView)

• 8022, 8443 for EM GUI access

Inbound (Communication between EdgeView and EdgeMarc)

• 9042 for legacy support data syncing
  Inbound (Cassandra connection for legacy support)

• 22 for SSH

• Inbound (Connection of EdgeMarc devices in environments that have both EdgeView14 and EdgeView15 deployed)

• 9000 Portainer Management GUI

• 5000 Docker Private Registry Service

• 3260 ISCSI communication between Storidge Hosts

• 8282 Storidge REST API

• 8383 Storidge Secure cluster configuration

• 16995 Storidge Metrics Exporter

• 16996 Storidge DFS internode communication

• 16997 Storidge SDS CLI server

• 16998 Storidge Controller nodes heartbeat

• 16999 DFS-CIO internode communication

Deployment

The main difference between deploying EdgeView in a multi-node configuration vs. single node configuration is that you must first install and configure a Storidge cluster before proceeding with EdgeView installation in the former. At a high level, these are the required steps:

1. Install Storidge software on each node you plan on including in the cluster.
2. Initialize the Storidge Cluster.
3. Install EdgeView in HA mode.

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 installation instructions.

Install Storidge

To install Storidge, perform the following steps using an SSH client such as PuTTY:

1. SSH into each of the five servers and run the following command to install the Storidge software:

   $ 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.

2. On the first node (primary node) in the cluster, run the following command:

   $ cioctl create --all-managers --noportainer

   Copy the join command and run that on the rest of the nodes in the cluster (nodes 2 to 5).

   For example: 

   $ cioctl node add 10.10.10.1 3b6ca81e9370a228c7fc8 edbfa3c6361-3aff2bb8

3. 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: 

   $ cioctl init e2e14943

   You can now see the cluster form. This may take several minutes.

4. To verify that all five nodes are present and that their status is ‘normal’, run the following command:

   $ cio node ls

Install EdgeView

To install and configure EdgeView, perform the following steps:

1. Download the EdgeView 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).

   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:

   chmod +x cluster-install-ev.sh

2. To execute the installation process, use the following command:

   ./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.

3. 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:

   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: 

   docker service ps $service_name –no-trunc

4. For the initial SCC configuration, register your EdgeView 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.
   
5. Enter the EdgeView admin registration details and click NEXT.
   
6. Enter the Tenant admin registration details and click NEXT.
   
7. Click APPLY to complete the registration.
   
8. Click LOGIN to navigate to the login screen.
   
9. Enter the credentials and click SIGN IN to log in to EdgeView.