
Interested Interns: DO NOT apply through this platform. Due to a bug, it does not contact the Mentor. Please go to https://wiki.lfnetworking.org/x/EqsZB. nRead the complete description. When you a ready to apply send your application documents to your Mentor(s) and mentorship@lfnetworking.org nSelected interns will then apply here to finalize their paperwork. n nODL CI/CD toolchain, as most of the LFN ones, is based on Jenkins which has developed new key features around Kubernetes not yet implemented by ODL (more generally LFN). nAs part of ODL IT modernization, the proposal here is to update our system by switching from agents running on baremetal or on virtual machines to containers running on a Kubernetes cluster. nThe clear first benefit is to make sure that resources are used effectively when testing our patchsets and when building our distributions. nBut, as important, it also enforces clean isolation between jobs and increase the capability to troubleshot the continuous integration issues more easily. nIt should be noted that this topic was also discussed during LFN Events in Anuket tracks and many projects could be very interested in these actions.
No project history available for this organization.
Counts are based on projects listed in the Contribo catalog.
Showing 1 of 1 projects. Click any project card for scope, mentors, and proposal studio.
Interested Interns: DO NOT apply through this platform. Due to a bug, it does not contact the Mentor. Please go to https://wiki.lfnetworking.org/x/EqsZB. nRead the complete description. When you a ready to apply send your application documents to your Mentor(s) and mentorship@lfnetworking.org nSelected interns will then apply here to finalize their paperwork. n nODL CI/CD toolchain, as most of the LFN ones, is based on Jenkins which has developed new key features around Kubernetes not yet implemented by ODL (more generally LFN). nAs part of ODL IT modernization, the proposal here is to update our system by switching from agents running on baremetal or on virtual machines to containers running on a Kubernetes cluster. nThe clear first benefit is to make sure that resources are used effectively when testing our patchsets and when building our distributions. nBut, as important, it also enforces clean isolation between jobs and increase the capability to troubleshot the continuous integration issues more easily. nIt should be noted that this topic was also discussed during LFN Events in Anuket tracks and many projects could be very interested in these actions.