cl664y@att.com 

Log4j status

• PTLs need to create an Istanbul maintenance branch for scans
• TSC agreed that this was the top priority for ONAP
• Target for update 2.17.1 version
• CLM jobs are already configured to check branches - PTLs just need to add the different branches in the jjb file
  • Instructions sent to the list by Jessica Gonzalez (Thursday, Jan 20)
  • Note:  do not need to include Honolulu (Jessica to update email instructions)
• Jakarta would be on the master branch - ok there.
• Istanbul maintenance release will be released on the Istanbul branch
• Jira tickets have been created for any project that has direct dependencies
• Creation of the CVE is still an open item
  • Mail sent to Krzysztof Opasiak 

Feedback from the Enterprise Task Force - Is there any additional best practice to be documented in our release note/documentation guide?

Here is a recent example:

• Lukasz Rajewski  Our latest presentation at LFN DDF, CNF Orchestration Tutorial, covers this aspect. At least slides 16 and 19 describe Helm & Kubernetes requirements + current VSP onboarding package.
• Thomas Kulik an extra section could be added to the docs, maybe https://docs.onap.org/en/latest/guides/onap-operator/settingup/index.html

Muddasar Ahmed and Thomas raise issues about how sufficient documentation is to support installation.  Kenny Paul to add agenda item to TSC meeting.

Istanbul Left Over

• Keguang He Platform Maturity for UUI - completed - thank you !

Istanbul Maintenance

• Issues
  • Reminder:  do not assign other issues to maintenance release besides log4j mediation unless urgent
  • In Jira, use Fix Version = "Istanbul Maintenance Release 1"
• Status of Nexus IQ scans on Istanbul branch for log4j instances?

Jakarta

• M2 scheduled for Jan 27
• Milestone status
  • Projects: 41%
  • Req Owners: 7% 
  • M2 includes a new task for PTL's to color code the Impact View per Component page

Reminder that TSC agreed to Log4j fix to Istanbul is the priority