April 17, 2024 Attendees: Linda, Mark, Michel, Rob 1. General Topics 1.1 Log into git before download the source * How to pass the credential through the tooling layer when log into git repo. * workaround: currently use repo sync outside of the containers. * AI: Scott to write up a feature request for the tool - file a request in Story Board. 2. ARM Support 2.1 Equipment * The location of the hosts, 4 in Alameda (for CI/CD server for testing), and 2 in Ottawa lab (build process) , 2 were returned * ARM is sending those machines to these locations. Steve update the address of the Ottawa office. * 2 machines for ARM has already been setup in Ottawa Lab. Installed with Debian OS. IT has fixed the network issue, in the correct network(?). * 2 servsers in YOW had resent to ALA, ALA now has 6 servers.. * Setting up the mirroring of the ARM server for Debian ARM repo server. No time allocated for build ARM server. * Jackie got the access to the 4 servers in ALA and installed StarlingX on them, but StarlingX testing team (Rob's team) haven't run test on them yet * STATUS: QA team is still working with IT to get the system ready for Testing. 2.2 CI/CD try to set up the workflow in ARM's local lab (ARM's Shanghai Lab), applied Jackie's patches, but may still need more patches to do builds. * Tianyu is trying to reproduce the environment in local lab, but still have some error on generating the ISO image. * Still have the same problem. Can't generate the ISO image as needed from Jenkins, so will need help from the Jackie, will need to get help from Jackie. Working on using docker image for CI/CD, talking to Jackie for help. * Took 20 hours to build the packages. Very time consuming, some builds time out and driver issues. Some difficult to get to next stage. * TianYu to reach out to Rob Cook directly to get help on auto testing infrastructure. * Rob will take the image and manually run the tests on the systems, and get the results to debug the issues together. * The servers are ready. Jackie is able to access them to install them. so that the testsuites can be run. * For the 2 servers in YOW, the IT person is jason.beauchamp@windriver.com. => send to ALA. * For the 4 servers in ALA, the IT person is lee.asnault@windriver.com * For the 2 new server from YOW, the LabOps person is chris.wong@windriver.com * Run into technical issue during build. * Supermicro provided firmware infor and ISO image can be loaded now. * 4 test servers that are already in ALA, all racked up and setup for AIO Simplex, waiting for IT on external access for the community. Jacke can access them internally. * Tianyu send container information to Jackie. Next step to get the build system up and running. * STATUS: 2 new servers in ALA, try to get build server setup. 2.3 Porting still in progreess (Jakie) * Not spending much time in this area * Rebase all the code to latest master, send all the code reivews * There are 40 code review requests, 4 merged and there are 36 reviews still pending. * https://review.opendev.org/q/prefixtopic:arm64+is:open * Code reviewers are different for different repos. 3- 4 weeks ago * Jackie reached out to ARM for more resources to help porting of the failure the packages: qemu, ice networking driver, secureboot. * ARM needs to find resources to help with prepare patches for these failure packages. * Per Jackie: There were more feedbacks and two patches in starlingx/ha repo has been merged, but there are still 33 patches pending in review. * 1 patch has been updated in review, its related to the driver. 2.4 Packages for x86_64 are in CNGN, need to push ARM packages in CNGN * 1. generic Debian mirror. 2. various build config files 3. publishing the build artifacts. 4. naming and tagging of docker images (not decided on naming or tagging yet). * We have enough disk space, add another arch support for the mirror. * Need man power to help get the mirror to support ARM? Q: Another people resource question to Mike M. * Need to change meta-lat layer for ELF SDK, but want to link the task to different repo, not yet done. * AI: Per Jackie: no progress in this, I haven't had time to do this yet * AI: Check to see if Tianyu has access to the WR StarlingX server to help with packaging with arm packages. 2.5 OSTree (Per Tech Meeting last week, this item should be closed) * removing OSTree from the installer ISO. (not from the StarlingX) * Work in progress, not sure when it will be ready. Possible early next year, StarlingX 9. * AI: Dostov is now return, Will need to check with Dostro on this work. * Per Greg's 05/08/2024 reply: * "This is DEFINITELY a STALE requirement. * We made the decision late last year that for WRCP 24.09 / STX 10.0 * ISOs would continue to have a PRE-BUILT OSTREE REPO with 1x commit (containing a rootfs with all the pre-installed packages) * … since removing it and replacing it with DEB PKGs and building the rootfs/ostree-commit/ostree-repo as part of the installation, * would slow down the WRCP/STX install too much * Not having the DEB PKGs in the ISO does not cause issues for us * And for usability, although not done yet (dosto), we are going to add the list of DEB PKG names and versions as meta data to the ISO * PATCHES will be changed (have already been changed) to contain ONLY DEB PKGs … with the new OSTree commit being built on WRCP/STX controller" 3.0 StarlingX 9.0 -> 10.0 * SPEC file will be coming from OS team on in-Tree driver support in 6.6. * Pending on driver version checks before submission. Validation of their test results based on the firmware version given from vendors. * Status: will share the driver versions next week once confirmed with the vendor test results.