[IEC-37] [IEC][SEBA] Move to the new SEBA version in CI Created: 31/Mar/20 Updated: 29/Jun/20 Resolved: 26/Jun/20 |
|
| Status: | Done |
| Project: | Integrated Edge Cloud |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Medium |
| Reporter: | Ciprian Barbu | Assignee: | Catalin Iova |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Description |
|
The work for upgrading our IEC SEBA version for arm64 to the latest stable is nearly complete. For this effort we have employed the use of upstream Opencord tools for deploying SEBA (specifically SEBA-in-a-Box), by means of forking the automation-tools and helm-charts repositories from Opencord. The longer term goal is to also integrate arm64 support in upstream, so that forking is not necessary, but that is another subject. Currently, the Akraino CI still uses the old version of SEBA in the corresponding job: We need to complete the switch to the new version by modifying the installation script: The method used instead will be the same proposed in my previous change (WIP) which installed PONSim: The main difference to this gerrit change will be that we will no longer assume SEBA has been previously installed by some other means, and instead we will explicitly rely on the installation script to deploy SEBA, specifically this slightly altered version of SEBA-in-a-Box which, compared to the established meaning in Opencord, is able to run on 3-node clusters running the IEC platform. |
| Comments |
| Comment by Ciprian Barbu [ 29/Jun/20 ] |
|
At the same time with switching to the new SEBA version in CI we moved away from virtual PODs because they simply don't have the processing power to successfully deploy SEBA in a predictable manner. |
| Comment by Catalin Iova [ 26/Jun/20 ] |
|
Updates done: |
| Comment by Ciprian Barbu [ 31/Mar/20 ] |
|
One other useful information, the Akraino CI defines two executors for the IEC project, both representing virtual aarch64 PODs. These PODs might not meet the requirements for successfully deploying and running SEBA, a baremetal POD is highly recommeneded. But until we solve this we will have to make due with the virtual PODs. In the interest of making this integration seamless, I would also recommend experimenting in the sandbox first. There are some instructions here: https://docs.releng.linuxfoundation.org/en/latest/jenkins-sandbox.html |