Meeting Time: 07:00 AM PT / 03:00 PM UTC (See call time in different zones)

BRIDGE: https://zoom.us/j/184289009?pwd=aWRuMUs2dW5kUTNodS95UTZpTWh6QT09

Meeting Recording: TBA

(Example of collaborative meeting minutes, using Presos/Notes/Links: https://wiki.onap.org/display/DW/TSC+2020-03-12)

Attendance 

Attendance is taken purely upon #info in Zoom Chat 

Action Items (Open Action Item Tracker)

Votes (template below)

Zoom Chat Log

Voting Template

TSC Voting to Approve CPS Robot Blueprint family - Akraino - Akraino Confluence:

Motion: Tina Tsou (Deactivated)

Second: Peter Pouliot khemendra kumar

Minutes (notes taken by Oleg Berzin ):

##### Araino CI/CD

Eric: Feedback on CI is needed

Eric: How many people are using Jenkins? Looks like nothing is being verified on Akraino Jenkins.

Tina: Yes. the inactivity is due to transition between releases (R5 to R6).
Khem: we are using Jenkins jobs. Now in planning phases. ELTEdge.

Jeff: What is CI?
Eric: Continuous Integration using Akraino Jenkins

Ike: Suggest to review internally on PTL meeting on Tuesday and get back to Eric with a written response.

Peter: Fine if community needs few more days to respond. Need to take a survey of what is being used in CI/Jenkins.

Peter: Eric, can you tell what's consuming Jenkins today?

Eric: if I looks on Gerrit looks like verifications are done manually. Code review also often comes from the same committer.

Peter: Akraino is different from code perspective due to the use of prescriptive scripts written once. Majority of BPs historically used mannual verification rather than Jenkins.

Eric: A lot of peojects verify things on their own systems and then push logs. How many projects actually use Akraino Jenkins CI. Does each PTL consider Akraino Jenkins as integral part of reviewing/releasing code or "we don't" touch it.

Peter: Likely that majority do not use Akraino Jenkins.

Jeff: Agree, but there may be a change coming. E.g., Fujitsu has a strong academic component. They might be happy to have Akraino Jenkins support.

Peter: Just need a survey to get a better insight. The more we understand the nature of the needs of projects the more we can provide resources to support the effort.

Tina: For release cert DC logs are mandatory, but they can use Akraino CI or their own CI.

Oleg: PCEI R5 used private Jenkins.

Bart: AR/VR uses Akraino Jenkins

Fukano-san: Robotics BP is in discussions on how to use Akraino Jenkins.

Asif: My BP uses private Jenkins and we push logs to Akraino Nexus.

Tina: Peter - we are giving you the answer in this meeting but feel free to create survey monkey.

Eric: If four projects that are using Akraino Jenkins - is anything wrong with it? Do you require any changes? At this point Jenkins is very under-utilized but there's a fair amount of expense on it. If there are changes to improve interactions between Jenkins and Gerrit.

Peter: Does it make sense to combine Jenkins between EdgeX, LFE, Akraino?

Eric: EdgeX do not want to do that. LFE Jenkins is not in use. But it would be possible to merge LFE and Akraino.

Peter: Does it make sense to merge with the rest of the lab at the top level in LFE.

Eric: there was an initiative to merge Jenkins with LFE lab but it's not that easy due to separate lab managemnt.

Tina: how much do we pay for Jenkins server?

Eric: Not sure. Jenkins server is a packaged deal with Jira, Nexus, Gerrit. They are all together. It's not exactly a waste of $$$ but since it's there should it be utilized more and can it be made more useful.

Tina: The bottom line Akraino Jenkins is being used. The low utilization may be due to in-between release timing. We should keep it.

Eric: I am well aware that it's been used. We are not looking at shutting it down. Just trying to understand how to make it better.

Jeff: When projects get security check, does that involve Jenkins?

Randy: not normally. The scripts are built in BluVal. I don't think Jenkins is coming into play.

Tina: Two ways for developers: own Jenkins master with Jenkins peering to Akraino. I think we are in-sync and we answered your questions.

Peter: there is a good understanding now.

Eric: This is helpful. I would still like to get a better idea of how it is being used and what fixes are needed.

Tina: I recommend to keep the logs for longer than 6 months. Recommend not to delete logs.

Eric: how long to keep logs:

Tina: Two years.

Eric: Exactly what I was looking for. Extend time and increase storage.

Paul: TSC should decide if we should delete based on time (this is probably wrong).

#### NEXT TOPIC:

Tina: Akraino Spring Event.

Ike: It should based on PTL interest. Challenge due to diversity of projects and lack of synergy across technologies. I have not seen reactions from people on what is useful. No feedback on how it was helpful and what follow ups are needed? Example 5G private networks. If participants wanted to learn more about specs? Asif is working on V2E. Fukano-san can use that too. Would like to keep the topics general. Personal interest or company interest. In Akraino case both are okay.

Tina: Lsited current topics and who expressed interest.

Jeff: Is there a page we can add companies and their interest.

Tina: It's on the event page agenda. Do we need to list interested parties or just the topics?

Jeff: recommend to list interested parties.

Ike: Good to have Goog and Dell. To find synergies between them and Akraino. If I understand internal interest (e.g. Asif V2E) then I can assist with synergies with Goog/Dell/AWS/Vz/Telefonika/Ericsson/Nokia - this would be great coverage from different companies.

Tina: Updates from sub-committees