discuss whether this testing infrastructure can cover SEBA on TA as well as on IEC
Minutes
Lab status update
HW network (OpenEdge HW) in place, Akraino regional controller set up/functioning (tested several times) - automated build to complete on TA (including k8s, Helm)
Note: for release 2, no plans for community lab to support OpenEdge; future work to port to ARM, Dell - those can be supported in community lab
Telco Appliance stack using K8s 1.16 - note: this is when they changed API versions (older API versions disabled by default)
To Do: wrap Jenkins job around so that we can capture logs and push back to Linux Foundation, SEBA install on top of stack; ran into permissions issues - will need to work with SEBA/CORD development community (and local Foundry team) to resolve
expect Jenkins/log push portion to be complete by end of week
MBI2: what remaining items to achieve milestone?
fully documented = what is switch and server HW; basic network topology; should be identical to REC lab; single Cisco 5501; OpenEdge chassis with 3 blades cabled (2 conn each) to switch
Repo for SEBA established; committers identified there constitute the "team"; follow same structure as REC repo for release 2
David will gather files using for automated install and propose a patch in the repo for review
MBI2-4 will likely be met at roughly same time
Develop slide deck to support meeting the MBI1-4 milestones (Julie will start pulling together info); this will need to be presented to TSC;
In documentation, phrases related to "install SEBA on SEBA" cause readability issues. For Release 2, can use phrasing "install SEBA on REC" - more technically correct
what is status of porting SEBA on TA on ARM? Tina indicated that this may now be ready; need more details on what patches are involved, which are merged, etc.;
request that we have someone join this meeting to review on a future call