Magma CI is broken. https://magma-ci.web.app/ Need to be fixed ASAP. Wave labs PRs related to 1.8 Release can be merged only after the CI issue is fixed. -- Owners -@Tim,@Shubham Tatvamasi,@Maximilian Huber (maxhbr)and TNG Team. Respective owners, please comment on the next steps. We need to plan on creating 1.8 Release branch. GAPs to be manually tested (or) validated through wavelabs internal CI ? 4G/5G specific traffic tests will be tested – wavelabs
Setting the registry location in all the relevant files in magma artifactory - Timothee Dzik ~lte/gateway/deploy/roles/magma_deploy/vars/all.yaml, from 1. debian -> debian-test 2. focal-1.7.0 -> focal-ci
Hosting Arm AGW docker image in magma artifactory through CI build job. – Timothee Dzik
Wave labs team made changes in OVS. Whether OVS debian packages in JFrog is up to date with this change and tested with dockerized AGW on Arm/x86 targets ? – Yogesh Pandey
Add a CI job to build the debian package and upload in JFrog and test the docker image hosted in magma artifactory.
Security issue with AMI and needs to be fixed before 1.8 branching – Shubham Tatvamasi
stateful artifactory - 1.8 deb packages from magma artifactory is not reliable, 5G test
MME and pipelined process is not coming up due to pipelined variables are not set properly and files are not visible. Python3 package is getting installed.
Timeline is unknown to stabilize CI.
Vagrant cloud has rate limiting an causing CI jobs to fail.
Postpone 1.8 Release till CI is stabilized. – Raise this in TSC meeting
Arm CI build job is progressing well per Timothee Dzik