Use the following information to install EdgeView on RAMP on Kubernetes.

Warning

Installation is performed only by Ribbon Professional Services. RAMP-EV installation on the Kubernetes Platform is a controlled deployment. Contact your Ribbon Account prime if you are interested in this type of deployment.

Overview

       Helm chart provides the installation of EdgeView application on RAMP Kubernetes platform.

Helm chart

The Helm chart for deploying EdgeView will consist of the following configurable parameters:

  1. Placeholder for definition private container image registry accesses (both for Ribbon distributed images as well as mirrors of OpenSource images).

  2. Values for specifying a number of different cpu limits/requests for pods and resources. This includes:

    1. High resource requirements

    2. High resource requirements with addition of hugepages

    3. Medium resource requirements

    4. Low resource requirements

    5. Volume initialization resource requirements (ultra-low)

  3. Enablement of Geo-Redundancy.

    1. Datacenter designation (0, 1, 2)

    2. Multus Network Attachment Definition to use for replication

  4. Public IP address (this maps to the EdgeView configuration address for either devices to contact EdgeView or for users to access the EdgeView web interface). This may be an addresses that is NAT'd to a private IP actually used by the EdgeView but not otherwise configured on the EdgeView.

  5. Multus Network Attachment Definition to use for the public interface (does not have to be mapped directed to Public IP if it's NAT'd)

  6. Routes used for the public interface above if it's not defined in the network attachment.

  7. Volume size of Time-Series data stored in Cassandra (per node)

  8. Volume size of object store volumes.

  9. Add volume size for configuration data, device node information, etc. (MySQL).


Download process

Follow instructions from Ribbon Support Portal - Download Center.  The product is RAMP-EV and version is 22.07.


Install Process

Customization

The file used to customize your installation is in YAML format.

Common Customizations

The most common values you will need to customize will be this snippet from the file:

Copy customization file
.
.
.
publicNetwork:
  create: true
  name: "public-interface"
  ipAddress: 172.29.117.148
  bitMaskLength: 24
  gateway: 172.29.117.1
replicationNetwork:
  create: true
  name: "replication-interface"
  ipAddress: 172.29.117.149
  bitMaskLength: 24
  gateway: 172.29.117.1

geoRedundancy:
  enabled: false
  datacenter: 1
.
.
.

Note that the publicNetwork and replicationNetwork structures correspond to the public IP requirements outlined in the previous diagrams. Change the ipAddress, bitMaskLength, and gateway values as appropriate.

The geoRedundancy structure is used to configure the feature. If the installation will be standalone, or a single EdgeView cluster, then enabled should be left false. Use the following information to modify the other values:

KeyValueNotes
datacenter1 or 2This designates the role of this cluster in a geo-redundant configuration. 1 means this is the primary and 2 means this is the standby.
witnessAddressIP address of geo-redundant witness (or quorum master)
peerAddressIP address of other EdgeView clusterThis should be the replicationNetwork.ipAddress value used for the other cluster participating in the geo-redundancy feature.

Less Common Customizations

Depending on the size of the volumes allocated for the RAMP platform itself, the size of persistent storaged used for the various services in EdgeView may need to be customized.

To discover the size of the volumes allocated per node by the RAMP platform:

size of storage
df -h /var/lib/longhorn

The total size of volumes you have available will be the result of the above command multiplied by the number of nodes for your cluster.

Recommended values to start with:

mysql: 1/12

minio: 1/20

cassandra: 1/12

In values_ramp.yaml, add/modify the size attribute under persistence for the corresponding service. For example:

volume customize
cassandra:
  .
  .
  .
  persistence:
    storageClass: "longhorn-fast"
    size: 10Gi


Configuring TLS Certificate for EdgeView GUI access

In values_ramp.yaml, change serverCertificateFile and serverKeyFile values to actual location of the certificate and key file. For example:

  • This is for HTTPS access to EdgeView GUI, nothing else tls:

    • Configure to something like tls/server.crt to pick up the file from tls directory (you will need to create it in EV helm root) server

      CertificateFile: null

    • Configure to something like tls/server.key to pick up the file from tls directory (you will need to create it in EV helm root)

        serverKeyFile: null

Install Process

Once customization is completed, you can install the system with:

Installing Helm Chart
cd edgeview-chart/edgeview
helm install -f values.yaml -f values_ramp.yaml evtest .