Versions Compared

Old Version 6

changes.mady.by.user Robert Heinemann

Saved on

compared with

New Version 7

changes.mady.by.user David McBride

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
  • Zoom bridge: https://zoom.us/j/283628617?pwd=aWM3WjliUkFtcGFPUEdEMStIRll1UT09  passcode: 248130 
  • PTL Recordings
  • Antitrust Policy Notice

We will start our meetings 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.

Agenda

START RECORDING

Duration

Agenda Item

Requested byNotes / Links
1 hour

Cross-project discussions

David McBride 

Unmaintained projects meeting resumed this week at a new time, 6 a.m. Pacific

New "relman" repo has been created to support work by the unmaintained projects team, as well as other release management tasks.

LF IT Support


Testing EnvironmentStephen Gooch 

Intel ==> UNH Lab

migration

transition

  • Intel lab will shut down on April 1 - please ensure that you backup any critical data prior this date !
  • Represents a risk to the Jakarta release schedule

Stephen Gooch 

  • How do we manage quotas?
    • Stephen to review quotas setup for Wind River Lab
  • Do we need to restrict users to specific projects?
  • Who should get admin access?
    • INT PTL (committers?)
    • How about OOM?
  •  Stephen Gooch to send email to onap ptl mailing list detailing process for lab transition and questions that need to be answered by ONAP community to complete administrative setup

Testing Improvement



CSIT Review



ToolChain Improvement

cl664y@att.com Kenny Paul 

After Jakarta, how best will we handle our OOM activities?

A "Call to Action" will be sent to the ONAP Community to check if any ONAP Member is interested to take it over

If nobody is interested then we will ask the project teams to take over and manage their artefacts

In order to not break the "Gating" flow, the recommandations will be to not move the code out of OOM repos

Open for discussion ....

Concerning MS Azure Lab, dedicated meeting to be setup by Kenny Paul - is it still required since we have a brand-new Intel lab (smile)?

Agreement that we need to continue the Azure Lab for the foreseeable future.

Documentation

Other Improvement suggestion



Subcommittee Updates for PTLs

Robert Heinemann 

Updates to Security Logging Fields

View file
nameSecurity Logging Update - PTL Meeting.pptx
height250

Note from Dan Timoney: Logging-analytics project needs to be updated.  Dan can contribute an update, but we need a committer.

Sharing Best Practices



IF TIME ALLOWS ....
15 minsRelease status


Jakarta release


Istanbul Maintenance Release
  • Completion of this release is gated by issues related to release notes.
    • Question about scope of release:  is this focused specifically on addressing the 'log4shell' vulnerability found in log4j2, or are we required also to migrate from log4j1 → log4j2, if not already done?


Kohn Release

  • You may find a draft of the schedule for the Kohn release here. This schedule will be reviewed by the TSC and voted on in the coming weeks.
  • We discussed coordination of the ONAP Kohn release schedule with the ODL Sulfur and Chlorine schedules at the ODL/ONAP Integration Sync meeting on Mar 15.
    • You may find the meeting minutes here.
    • The Plan is to migrate to Sulfur, internally, then to Chlorine for the Kohn release.
    • The ODL team is confident that they can deliver a release candidate for Chlorine, well in advance of Dan's deadline of one month prior to Kohn M3.
    • If there are problems transitioning to Chlorine, then the fallback position will be to use ODL Sulfur.
    • One significant issue related to integration with ODL Chorine is a major change to RESTCONF.  @TIMONEY, DAN is taking this up with the ONAP Arch Subcommittee.
    • We will meet again in the same meeting slot on April 19 to discuss status.
    • Going forward, we intend to follow this same coordination process for all future releases of ONAP.
5 minsUpcoming Events


  • LFN Developer & Testing Forum EU
    •  June 13-16, 2022, Porto, Portugal
    • In-Person
    • Topic Proposals: 
  • ONE Summit NA  Save the Date!
    • Nov. 15 & 16 2022 Seattle, WA, USA
    • In Person
  • LFN Developer & Testing Forum NA  Save the Date!
    • Nov. 17 & 18 2022 Seattle, WA, USA
    • In Person
10 minsRemaining Action Items



Zoom Chat Log 

07:14:48 From Fiachra CORCORAN (EST) : https://wiki.onap.org/display/DW/ONAP+IOL-UNH+Lab
07:53:32 From Bob Heinemann (MITRE) : Please visit and comment on security logging fields: https://wiki.onap.org/display/DW/Jakarta+Best+Practice+Proposal+for+Standardized+Logging+Fields+-+v2
07:53:50 From Bob Heinemann (MITRE) : i'm dropping.  thank you for everyone's time today.
08:01:07 From Tony HANSEN (ATT) : Reload4j

Action Items 

  •  Type your task here, using "@" to assign to a user and "//" to select a due date