We will start by mentioning the project's Antitrust Policy, which you can find linked from the LF and project websites. The policy is important where multiple companies, including potential industry competitors, are participating in meetings. Please review and if you have any questions, please contact your company legal counsel. Members of the LF may contact Andrew Updegrove at the firm Gesmer Updegrove LLP, which provides legal counsel to the LF.
Discussion about the community CI and if we need to have a backup of services.
The community agreed that the CI should be managed by the LF. However, if there is a short term outage for maintenance, we would not need the extra expense of a backup service.
Release Image
Marek Chwal based on Nick Davey confirmation seems feasible to use Juniper images for the TF 2011 release. "RH has confirmed TF is fine to distribute the containers, the UBI has no license requirements, and is free to use/distribute. We still need to confirm that there are no commercial RH repos we use that would prevent us from distributing the containers. I’ve followed up again with the build team."
Andrey Pavlov will ask Juniper CI engineers to check if commercial Red Hat repos are not used while building Juniper images so TF will be able to use them as well.
Juniper uses several RHEL satellites for yum packages. These packages are installed during containers build. There are many packages (c++ libraries, common python libraries, openstack python libraries, etc...) from several repos like rhel-7-server-rpms, rhel-7-server-openstack-13-rpms, rhel-7-server-openstack-13-devtools-rpms, rhel-7-server-extras-rpms, etc. Subscription is required for all these repos. We tried to build docker images just from UBI yum repositories but that trying failed. UBI repos don't have all required pacakges.
Action items
Chandra Dasari to follow up with the community on the linking of LFID, Git, and Lanuchpad to ensure continuity when migrating to LFID SSO.