Anuket Project

 

Attendees

  1. Walter Kozlowski (Telstra)
  2. Al Morton
  3. Frank Brockners (Cisco)
  4. Trevor Cooper (Intel)
  5. Beth Cohen (Verizon)
  6. Mark Beierl (Canonical)
  7. Sridhar Rao  (Spirent)
  8. Lincoln Lavoie  (UNH-IOL)
  9. Georg Kunz (Ericsson)
  10. Emma Foley (Red Hat)
  11. Cedric Ollivier (Orange)
  12. Gergely Csatari (Nokia)

Absent (TSC)

  1. Riccardo Gasparetto Stori (Vodafone)
  2. Qiao Fu (China Mobile)
  3. Ahmed El Sawaf (STC)


Other Attendees 

  1. Scot Steele (AT&T)
  2. Jim Baker (LFN)
  3. Pankaj Goyal (AT&T)
  4. Ulrich Kleber
  5. David McBride  
  6. Scott Steinbrueck
  7. Karine Sevilla (Orange)
  8. Ildiko Vancsa
  9. Trevor Bramwell
  10. James Gu
  11. Toshiyasu Wakayama(KDDI)

Agenda

TimeTopicPresentersNotes
5 min

Meeting Administration

Al Morton

  • Agenda APPROVED
  • Minutes of last week's meeting APPROVED
5 min

Announcements

Al Morton

  • Mailing list deprecation: From today onwards, mail sent to the old lists will bounce, with a guiding message where to send email instead.
  • Internships: No deadlines for proposals yet. Please start to create proposals for internships so that we can get those published.
  • Release naming: Historic naming theme for OPNFV as "rivers". Use the link to submit your ideas how the evolve/change the naming scheme.
15 min
  • Continue Release process discussions, Goals and Management
    • Presentation (from the event)
    • Summary from the Virtual Conference <link>
    • Conclusions
      • Need a candidate process to edit/work with for 1H 2021 Release!
      • Each Release Process is an EXPERIMENT !!!
      • Need to fix target dates very soon! 
      • https://wiki.anuket.io/x/bwBD
    • David provides an outline of the necessary components/discussion to get us to a release process: Release Process
    • Meeting today!

David McBride

On Docs: https://readthedocs.org/projects/anuket/ already exists. There is a need for consolidated documentation (which was earlier driven in OPNFV by the docs project).

Earlier documentation:

15 min
  • Assuming a successful Anuket recruiting program, 
    • Anticipate new people in the specification WS and the Development Projects.
    • Thus developer on-boarding needs to be really easy, incl. a comprehensive set of documentation, wiki, etc. 
    • What are the activities to accomplish this?

Heather Kirksey

Defer to  

0 min

Gergely Csatari



10 min
  • Wiki site updates
    • Anuket Wiki page 
      • We'll use spaces to avoid namespace conflicts. But use with care.
    • If you want sub-trees copied from CNTT or OPNFV wiki, send email to Jim Baker, identifying the root of the sub-tree. Jim will create the associated tickets with LF. 
      • How did we do on this call for action?
      • Will we drop blank Wiki Pages from the Wiki? (#agree on this??)
    •  Further topics:
      • Alignment of groups/IDs across LF LDAP and Github.
      • Issue tracking (Jira/Github?).  
    • Active OPNFV JIRA users: New Instance for Anuket!
      • let's drop much cruft of the past...

Jim Baker Everyone

  • Anuket per project wiki:
    TSC AGREES to remove projects from the wiki that don't update their wiki by  . Note that this does not include archiving the project (which might happen at a later stage).
15 min
  • Active Repo Migration
  • DockerHub Migration - no change to OPNFV Dockerhub
  • Contributor License Agreement → Only "DCO": Developer's Certificate of Origin

https://opensource.com/article/18/3/cla-vs-dco-whats-difference

Jim Baker
  • Copy active docker repos to: https://hub.docker.com/u/anuket, and instruct projects on how to update CI.
    • Barometer
    • Dovetail (dovetail-webportal)
    • Functest
    • LaaS
    • NFVBench
    • SampleVNF
    • Storperf
  • Propose 6 months Interval for active project MIRRORS repo migration
  • OPNFV Dockerhub will continue to exist - proposal is to CLONE repos in Anuket space, and it's up to projects to update their CI.
  • Only DCO is planned in Anuket: indemnify LF regarding applicable licenses.
    • Any concerns?  no, more follow-up.
10 min
  • Workstream Leads/ Project PTLs standup (continued)
  • Volunteers are needed to re-juvenate
    • DOCS  what's next?
      • Projects write the documentation - the DOCS project is mostly about organizing and structuring the content.
      • Can this be a small part of the Release process for Development documents?
    • PHAROS -??? Can we get a view of the project-wide resources that are at our disposal, and how we manage them?
      • Need a person to step up for this, it's an important job!
  • STATUS still needed from:
PTLs/Co-Chairs
  • "Pharos":
    • Anuket needs a view of the available build/deploy/lab (incl. member labs) resources. TSC looks for volunteers to provide that overview - so that we can effectively use Anuket's budget in 2021 (before we spend money on new resources, the TSC needs a proper view on the current set of resources and their availability).
    • ACTION: for all PTLs - identify the Lab resources you are currently using!
      • This should give us a fairly broad view, but only as complete as the response.
5 min

  • Status Updates

    • Linux Foundation Lab (Portland) hardware upgrade status
    • LF IT/Infra update: (Aric Gardner, Trevor Bramwell)
    • gitlab POC
    • GSMA interaction

  • Please don't use the UCS pod - trying to de-comission, but there are some Functest jobs running there - suggest to move toi LaaS.
  • LF Pods 4 and 5 are in Portland - will move to Oregon State to save costs. Scheduling has been a problem. Current allocation of 4 and 5 to Functest
  • gitlab POC: Scheduled follow-up discussion from the DDF for next monday
  • Joint meeting with OITF with FASG planned for 10 March.
5 min
  • AOB



Future topics:

  • How do we figure out who are the WS stream leads AND PTLs in an automated way?

Mark Beierl  (question)



Action Items

  • for all PTLs - identify the Lab resources you are currently using!  by  



  • No labels