Discuss Minute taking and scribe. We have to rotate among the TOC members.
Discussion on Cherry
Release Votes and Approval
SMO Vote: Jack: Last week a few people dropped early. We got 4 in favor 1 abstaining 1 against. We need to get to 5 votes across TOC even though we had majority present I want to make sure the TOC takes time to work through it and get approval. We have a standing motion on creating an SMO project brought by Rittwik on the RSAC committee. Are there further clarifications.
AT&T, Ericsson, NTT DOCOMO, and Nokia voted in favor. Jinri abstained.
Jack: We need to add the SMO to wiki and create a repo in gerrit. Action/ user-59b16 add the SMO project to the wiki and gerrit.
Jack: We will need a PTL. Looking for people to take on a role as a PTL for the new SMO project. We should be following Best Practices. As an interested party anyone can contribute to the project. Requires an LF ID. We prefer you use your company's email. If you want to take a more active role you can offer to be a committer. There are a small number of committers per project, minimum 2, maximum 5. The PTL can also be a committer.
You also have to sign the CLA agreement for licensing. There are two different licenses
Apache license
O-RAN license
For SMO we expect contributions under the Apache license. We are not under the 3GPP interfaces. One of the questions asked by EC. For RIC Near RT controller we have separate applications. We are going to try to capture these applications as SMO applications and continue to see if that works or we need to separate. R-Apps under the SMO projects. We will create a structure that clearly identifies the people.
Action/ user-59b16 start the Principles we will kick the wiki off with these principles. The RSAC has proposed minimum viable product. Looking at O-RAN Alliance working groups specifications. If we don't find specs there then we try to work with them towards the specification so we are not creating throw away code.
Lusheng: Email voting request was sent to the ML on July 9th. The vote if for 3 procedures and best practices.
All gerrit code submissions to include at least 1 Jira issue. This is for tracking purposes. This creates a Link between gerrit submissions and Jira issues.
We currently have 3 votes. Who wants to vote in favor?
Jinri: I thought I already cast my vote via email. I vote yes.
Jack: I vote yes.
That brings us to 5 votes.
VOTE: Vote taken, item passed
Lusheng get clarification from LF how to list multiple issue IDs to gerrit.
Will this be a gerrit pre-check?
Yes, the system will return with a warning message.
License scans are not done until one or two weeks prior to a release. We require more time. LF does not scan SCP repos. That leaves those repos open. LF does have a tool called nexus iq. People have been using that to do license scans. Because of the language the security vulnerability may not be helpful for Java but for Go C++ is not as helpful. Requesting all the repos to add this nexus iq job. Action item for repo owners is to define a job. There are samples available for you to follow.Any questions?
On motion made by Lusheng to include a license scan to all repos.
Adopting semantic versioning for the artifacts (libraries and docker images and use it for the artifacts). The action item is for the developers and contributors in the future please use major, minor, and patch versioning. We can write some best practices in the future but this is the format. Another action item is what will be the best way to verify a version.
On motion made by Lusheng to include a semantic versioning process to all repos.
Jinri: Zbynek sent an official copyright notification to us.
Jack: We have an action item that we have to make a proposal to the EC with Stefan but that is still in process.
John-Paul: Is this the 60 day impacts?
Jack: No we were talking about the copyright permission from O-RAN Alliance on any copyrighted material. The 60 day gets approved by us and we're refining the language for that feature. That is an alliance issue when the material can be managed copyright material.
John-Paul: Is that resolved?
Jack: Has the 60 day copyright IPR issues resolved?
Action/ Jinri Huang will check with Zbynek of whether this will imapact.
Marketing of the current release (WG, LF, PR)
Status of Open Action Items (Old Business)
Standing Agenda Items (Brief Status of Ongoing Activities)
August 1st is the close out date. I will look to Lusheng to give us a report but I think the progress is less than hoped for in a few areas.
Lusheng: Status: we have a couple deliverables planned.
O-DU Low running in the OSC integration lab and completing the O-DU high. This is lagging behind. We've been having system related issues. We had 2 dell servers. For some reason the NIC and FPGA cards do not work right on these two servers. Later we got the wolf pass servers. We're having problems installing OS on this server. It will not make it to this weekend.
KPI-MON xApp flow the near real time xApp team have been trying to build the docker image with other xApps to complete this flow. There were some problems with the routing.
Matti: The subscription manager is rejecting the request. I reached out to the team but have not gotten the response. The internal communication is working but given the time I am not sure we will deliver.
Additional minor improvements in documentation and the integration repo to upload demo scripts for people to run the demo.
Rittwik: O-DU High is ready to integrate with O-DU Low.
Lusheng: The O-DU High can follow the future enhancement to move feature code in Bronze release, update their release notes.
John Keeney We don't see the verification jobs when we release. I assume there will be full integration tests. I want to know if we can help.
Lusheng; The issue is the base image that your docker file requires has expired on the staging docker registry. We need to generate that first.
Henrik Anderson: Will the staging jobs be ready?
Lusheng: The LF has two registrys STAGING and RELEASE. If it's in the staging registry it will live there for 30 days. Jenkins has a job that will regenerate the newest version of the base image. That image gets refreshed. It will exist in the staging repo. The build reference is to the previous version of the base image. We need to figure out to regenerate.
Henrik: When we push things to the Bronze branch they don't exist in the staging repo.
Lusheng: Let's work offline.
Jack: We are looking for people who will be interested in Integration and Test. Lusheng will be reducing his time. We need more participation in the integration and test area beyond their project. We need coordination work to have a few more people involved.
Rittwik: EC has reqested a requirements document for the RAN simulator. That allows us to socialized with the EC and TOC for bidding for a RAN simulator.
Jack: Any PTL who wants to leverage the simulator beyond planning and generating data should communicate to your their requests and requirements. Anyone who has needs in that space reach out to user-59b16 for the Cherry release. Since there is a cost associated we want to make sure we're getting everyone's input.
Are all the use cases finalized for Cherry?
Rittwik: Yes, they are in the wiki and lifecycle management for the SMO and the traffic steering and health-check use cases.
Matti: I have new teams that want to contribute to xApps. I will reach out to you.