Product Certification with VOLTHA¶
The following document describes the procedure to include and certify an OLT or an ONU with VOLTHA. The process of getting a product certified consists of several phases:
testing and validation with VOLTHA at the vendor premises
showcase of successful integration with VOLTHA to the TST
shipment and integration of the product (OLT/ONU) at a community lab (e.g. Berlin with DT)
Creation of automated CI jobs in Jenkins that start nightly automation tests.
Test maintenance. It’s the Vendors and the VOLTHA community responsibility to maintain the created tests.
Once all these steps are completed the product will be certified for the next release of VOLTHA. Let’s describe each phase in detail.
Vendor’s premises Testing¶
The first step is for the vendor to guarantee that the OLT or the ONU are VOLTHA compatible is complying got ONF’s automated sanity test. To do so we suggest setting up a HW test pod according as described in the physical setup guide.
Once the setup is running the next step is running the Sanity tests, as described in the testing documentation. If those pass the hardware is ready to be shown to the VOLTHA TST.
Showcase to VOLTHA TST¶
Once the OLT has passed tests in the Vendor lab it’s ready to be showcased to the VOLTHA Technical Steering Team. The request needs to be performed to the Technical TST leader or to Timon Sloane who will forward the request appropriately. During a scheduled TST meeting (Tuesday 8 AM PST) the vendor will showcase the OLT/ONU to the TST by starting from a fresh VOLTHA instance, connecting the OLT and then performing the Sanity test. With the test passing the TST will give approval for shipment of the device (ONU/OLT) to an ONF community lab.
ONF’s community lab integration¶
Once the TST has given approval for device integration in VOLTHA nighly tests the Vendor needs to ship the device to any one of the ONF community lab, including a wiring diagram (if needed) Currently there are two locations:
DT Office in Berlin, Germany. Address: Winterfeldtstraße 21, 10781 Berlin, Germany. Point of contact Bjoern Nagel @ DT
Radisys Laboratory in Hilssboro, Oregon
Once the OLT arrives the technicians will rack it and wire it according to the diagram shared. For an OLT the NNI connection will be provided to the AGG switch and all the management will also be connected with management IP assigned according to the network of the pod. For an ONU it will be connected to one of the existing OLTs in the pod, according to space, technology and topology requirements. Once all the racking and wiring is complete the device will appear under the ONF network, accessible via VPN.
Automated CI Jobs¶
Once the device in included in one of the community pods it’s the responsibility of the vendor to integrate it into the nightly VOLTHA tests. This process is done by submitting a series of patches to different repositories. The process is different for ONUs and OLTs. To create jenkins jobs see https://docs.voltha.org/master/testing/voltha_test_automation.html#hardware-or-physical-pod-jobs
A new OLT needs a full new configuration, job and data. The job can be created according to the desired workflow to be tested. Information can be found in the system tests information The required patches are:
ci-management. Creates the job that will run in jenkins. Job Example
voltha-system-tests. Adds the sadis configuration for the OLT and the ONU. Sadis Example
Once these are created and merged the job will appear on jenkins and run accordingly.
A new ONU it’s attached to an existing OLT, so just the information for that ONU needs to be added to the proper OLT files.
The required patches are:
It’s the responsibility of the Vendor, the VOLTHA TST and the community at large to mantain, manage and update the job to make sure the OLT gets certified for each of the following VOLTHA releases.