R-CORD Profile

The latest version of R-CORD differs from versions included in earlier releases in that it does not include the vSG service. In the code, this new configuration is called rcord-lite, but since it is the only version of Residential CORD currently supported, we simply call it the R-CORD profile.

Prerequisites

• Kubernetes: Follow one of these guides to install either a single node or a multi node cluster.
• Helm: Follow this guide.

Install VOLTHA

When running on a physical POD with OLT/ONU hardware, the first step to bringing up R-CORD is to install the VOLTHA helm chart.

Install CORD Platform

The R-CORD profile has dependencies on the following platform charts, so they need to be installed next:

• xos-core
• onos-fabric
• onos-voltha

Install R-CORD Profile

You are now ready to install the R-CORD profile:

helm dep update xos-profiles/rcord-lite
helm install -n rcord-lite xos-profiles/rcord-lite

Optionally, if you want to use the "bottom up" subscriber provisioning workflow described in the Operations Guide, you will also need to install the following two charts:

• cord-kafka
• hippie-oss

Note: If you install both VOLTHA and the optional Kafka, you will end up with two instantiations of Kafka: kafka-voltha and kafka-cord.

Once your R-CORD deployment is complete, please read the following guide to understand how to configure it: Configure R-CORD

Customize an R-CORD Install

Define a my-rcord-values.yaml that looks like:

# in service charts
addressmanager:
  imagePullPolicy: 'Always'
fabric:
  imagePullPolicy: 'Always'
onos-service:
  imagePullPolicy: 'Always'
volt:
  imagePullPolicy: 'Always'
vsg-hw:
  imagePullPolicy: 'Always'
kubernetes:
  imagePullPolicy: 'Always'
vrouter:
  imagePullPolicy: 'Always'
xos-gui:
  imagePullPolicy: 'Always'
simpleexampleservice:
  imagePullPolicy: 'Always'

and use it during the installation with:

helm install -n rcord-lite xos-profiles/rcord-lite -f my-rcord-values.yaml