...
Note that at the moment, the work for verifying SEBA on ARM on TA is still in progress.
Base components
For this second iteration, the main base SW components that have been verified are as follows:
| Component | Version | Comments |
|---|---|---|
| Base OS | Ubuntu 18.04 for aarch64 | CentOS should also work when deploying SEBA on TA for example |
| Linux Kernel | 4.15.0-99-generic #100-Ubuntu | |
| Kubernetes | 1.15.0-00 | |
| Docker | 18.06.1~ce~3-0~ubuntu | |
| helm | v2.12.3 | Client: &version.Version{SemVer:"v2.12.3", GitCommit:"eecf22f77df5f65c823aacd2dbd30ae6c65f186e", GitTreeState:"clean"} Server: &version.Version{SemVer:"v2.12.3+unreleased", GitCommit:"cdc09e54bca50a53c1e54f0e67b15a0913f5af1d", GitTreeState:"dirty"} |
Software base
The 2nd interation of the SEBA for ARM port uses a snapshot of the master (development) branch of the various Opencord components, which was taken at a point in time where it was stable enough to be considered for porting.
...
The table below lists the components by categories:
| Component | Chart version |
|---|---|
| Incubator | |
| Zookeeper | 0.13.3 |
| Kafka | 1.2.0 |
| Stable | |
| etcd-operator | 0.8.3 |
| elasticsearch | 1.15.3 |
| fluentd-elasticsearch | 1.4.1 |
| grafana | 4.0.2 |
| kibana | 1.1.2 |
| logstash | 1.4.2 |
| prometheus | 9.3.1 |
SEBA-in-a-Box and automation-tools
...
Once the installation is finished, you can also try to run the SIAB tests:
| Code Block |
|---|
make run-tests |
Continuous Integration work for SEBA on ARM
As with the other Blueprints in Akraino, SEBA is also periodically verified for correct functionality in the Akraino Jenkins infrastructure.
For the moment, the CI jobs make use of the IEC Type 2 Platform, deployed using the Fuel Installer. Alternatively, the IEC Type 2 Platform can also be deployed using the Compass Installer, which is not in the scope of this documentation.
Hardware setup
Please refer to the Deployment Architecture documentation for better understanding the HW setup and requirements.
At this moment, the Jenkins jobs for deploying and verifying SEBA on ARM, are running on a single POD, located in the ENEA Kista Lab, and connected to the Akraino Jenkins Master.
The jump host that connects to the Akraino Jenkins master is designated by the following Jenkins executor.
https://jenkins.akraino.org/computer/prd-ubuntu1804-dev-96c-256g-1/
There is also work in progress for adding another POD, the ThunderX2 Pod 2 from the Akraino Community Lab at UNH-IOL.
Jenkins pipeline
Currently, SEBA for ARM is verified as part of a bigger pipeline for IEC, which is located under the IEC Jenkins project:
https://jenkins.akraino.org/view/iec/job/iec-type2-fuel-baremetal-ubuntu1804-daily-master/
Note that at this moment, only IEC Type 2 Fuel Baremetal Jenkins jobs support deploying and testing SEBA.
Deploying on the virtual PODs in the Akraino Jenkins brings little value, because of performance penalties.
Also, the Fuel Installer is the only that has been verified, but Compass should work as well. However, there are currently no Compass Baremetal jobs, so the CI needs to be restricted to Fuel baremetal installations for now.
Jenkins jobs
As you can see, the parent job runs a few different jobs:
- iec-type2-deploy-fuel-baremetal-ubuntu1804-daily-master - this deploys the IEC Type 2 Platform using the Fuel Installer and Ubuntu 18.04 as base OS
- validation-enea-daily-master - IEC Blueprint Validation as per Akraino requirements
- iec-type2-install-seba_on_arm-fuel-baremetal-ubuntu1804-daily-master - deploys SEBA-in-a-Box using automation-tools
- iec-type2-test-seba_on_arm-fuel-baremetal-ubuntu1804-daily-master - runs the SEBA-in-a-Box Robot tests
For the test-seba_on_arm job, the robot logs are collected and sent to the Jenkins master for aggregation and visualization.