Versions Compared

Old Version 223

changes.mady.by.user Larry Peterson

Saved on

compared with

New Version Current

changes.mady.by.user Gabriel Arrobo

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


For an archive of meeting notes pre-dating the Aether Project moving from ONF to LF, click here.

...

  • Component = 'Release Engineering'
  • Product = Aether

...

1-

...

7-

...

25 (Topics for Next Meeting)

  • ...
  • SD-Core
    • Need to review/update maintainer's group in the omec-project organization (Gabriel)
      • Add Ghislain to maintainer's group and should we still require a single approver, or should we increase to 2 approvers?
    • Do we need to keep creating "per-PR" images? There are not used anywhere (Gabriel)


12-17-24

  • Remaining meetings: December 24 and December 31 - keep or cancel?
    • To cancel. Next meeting Jan 7th. 
  • ROC
    • GitHub Actions to publish ROC artifacts. Status?
      • Have merged latest changes .github → to publish helm charts
      • Next step is to test run in an example repo 
      • Avoided being "overly generic" → targeting ROC in onosproject repos, but can be adapted
      • Publishing images will be next
      • Want to port to the omec-project repos once done (related to other Jira ticket)
    • Why it is not possible to configure OP (or OPc) and Key through GUI? (Gabriel)
  • Infrastructure
    • Jenkins performance/stability. Any update?
    • Blocked on AWS credentials
  • OnRamp
    • Version control: It would be good to tag versions/releases such that it is easier to provide support to end users (Gabriel)
      • Should be done.
      • Challenges
        • Need well-defined release process => Need dependable testing of blueprints.
          • Releases paced by "weakest" blueprint.
          • E.g., Latest SD-Core release gated by having all the blueprints work correctly.
        • Today, OnRamp releases ~ SD-Core Releases
    • Subnet variables working and ready for PR (see subnets branch of various repos)
    • srsRAN Jenkins job being debugged
    • Process to add other blueprints (e.g., Confidential compute, N3IWF, etc.)? (Gabriel)
  • SD-RAN (Woojoong)
    • Release blockers
      • SD-Core chart 1.4 has an issue in RiaB (4G)
        • It pointed aether helm chart, which seems to be removed → updated it with sdcore-helm-charts
        • It was used very old SD-Core chart → bumped up the version to 1.4.0
        • UPF was facing OOMKilled → fixed by doubling memory limit
        • Too many open files issue in MME and PCRF → set fs.file-max
        • PR: https://github.com/onosproject/sdran-in-a-box/pull/207
      • 4G hardware document (4G)
        • Out-of-dated → updating now
    • What is the plan to merge currently open PRs from Dependabot? (Gabriel)
      • High priority for next release, which hope to start working on after the holidays
    • Why do we maintain/keep RiaB instead of OnRamp? (Gabriel)
      • RiaB currently includes 4G elements that are not supported by OnRamp
  • SD-Core
    • Update GitHub Actions to properly handle tag creation when PRs are towards release branches (e.g., rel-1.5)
    • Continue effort to move code to 3GPP Release 18
      • Created models and APIs for some specs including Nnrf_NFDiscovery that is used in the nrf_cache
  • ARA
    • SD-Core
      • Currently checking logs to understand the UE context release issue (details posted on on-ramp slack channel)
      • Almost done debugging
    • SD-RAN
      • No updates (Tianyi on travel)
    • Blueprints
      • In progress → One for Ericsson radio and one for OAI radio
      • Could include ARA-specifics (e.g., for UEs, including experiments)
      • Intent is end-to-end deployment blueprints
        • related to OnRamp releases since more blueprints => higher hurdle
        • Need "owner" for every blueprint; some may be "core" and others "auxiliary"

...

...

  • OnRamp
    • PR related to k8s configuration pending - meeting with Gabriel, Suresh and Larry to sync up on this



  • ROC
    • No progress on updating Wiki - Sean to continue on this


8-20-24

  • SD-RAN
    • Working on v1.5 release
      • Working on documentation and release notes
      • To include OAI 5G RAN 
        • includes "ONF" E2 agent (not OAI's)
        • implies need to rebuild OAI images (since E2 agent is statically included)
      • Not include update to golang 
      • Expect announce 1st week of September
      • E2SM → Will add O-RAN RC Service Model 
        • Backward compatible with the old ONF Service Model
  • Infrastructure
    • Jira
      • Production site available at https://jira.aetherproject.org
        • Still working out Anonymous creation of issues
      • Permission Question:
        • Currently four levels of access
          1. Anonymous (users without Atlassian accounts or not logged into them) can Browse and Read existing Issues but not modify anything
          2. Any Logged in user can basically change almost any field in an issue, and invite people to join the site and become a user
            1. When invited, specific domains are automatically approved when invitee makes the request
            2. Basically, any  TSC user's domain (that is NOT public (ie, not gmail, yahoo, aol, ...))] is currently automatically approved.
          3. aether-jira-admin users can update group and user permissions
          4. admin can do anything.
        • QUESTION: Any need now to restrict (beyond being logged in as an approved Aether Jira user) things like:
          • Transitioning a ticket between states (including closing)
          • Mucking with assignee
          • editting fields beyond comments
          • → Taking a wait-and-see approach
      • Known TODOs
        • Figure out how to let Anonymous users create new tickets
          • Currently looks like a separate form to embed on an appropriate webpage that will then go create a ticket based on provided input
        • TST Guidance: Lowering the barrier to creating a Jira account >> creating Anonymous Tickets does not need to be supported
    • Confluence
      • Test migration appeared to complete successfully
      • QUESTION: Can I perform the formal migration from existing Confluence DataServer to Confluence Cloud between 12:00 noon Wednesday(8/21) and 12:00 noon Thursday (8/22) (PDT)?
        • Will require read-only Confluence installation at start of process until completion.
        • Upon completion, existing wiki.aetherproject.org will point to new site
          • Previous site will be maintained for approximately 30 days as an archive/reference site and then hopefully deleted.
        • I would hope that people can spend a 30-60 minutes reviewing the site after completion and ensuring things look okay.   Hoping to have acceptance of new site by next week's TST.
        • Post note on migration to #aether-dev channel
    • Jenkins
      • No progress as yet
      • No roadblocks
    • SD-RAN DNS
      • No progress from last week
  • OnRamp
    • PR related to k8s configuration pending
    • Still debugging monitoring system (metricfunc failing)
  • Question to Group: Anyone connected to "Aether Using Nephio" project?
  • SD-Core
    • Incorporating the static checks for linting with other PRs
    • No progress on logging
    • Discussion about e2e test on PRs
    • Waiting on repo omec-cni, omec-pod-init (to rename)

...

  • Aether Jira Proposal:  Aether Jira Proposal
    • Tweaked proposal and accepted as "good enough to get started"
    • Should be ready to play with next week
  • Github org renaming: https://docs.github.com/en/organizations/managing-organization-settings/renaming-an-organization
    • More representative → Mostly focused on "opennetworkinglab" (should be "aether")
    • May break external links, but now is a good time to change since we're creating new docs/pages
    • No objection...
  • Slack vs Element (https://element.io/)
    • Limiting history to 1 year (affects "grandfathered" workspaces like onf-community)
    • Proposal: prune onf-community back to "aether" and accept history limit (take up with voltha and p4)
  • Code of Conduct ((https://lfprojects.org/policies/code-of-conduct/)
    • Look through the LF standard and decide at a future meeting
  • Jenkins Status
    • ONOS GitHub Actions
      • Actions that run for PR (ROC done)
      • Actions that run for PR (SD-RAN done)
      • Not yet publishing new Docker images (in progress)
    • OnRamp Integration tests
      • JJB Related: Jobs with same name as the one created earlier, are not getting created again.
      • Native Tests: All the Jenkins jobs are not able to go beyond aether-5gc-install step. → "new group" command hanging
  • omec-pod-init and omec-cni repos Gabriel Arrobo 
    • These repos are in Gerrit → Why? Not updated in years. Move to omec GitHub? → Yes.
  • TST Meetings in July → Will remain on the schedule and expect them to happen (with some people missing)

6-18-24

  • DCO (instead of CLA) in place Larry Peterson David Ferguson (Deactivated) 
  • Configuring new Jira Larry Peterson  David Ferguson (Deactivated)
    • Archiving old Jira
    • Proposal
      • Projects: SD-Core, SD-RAN, ROC, OnRamp, Smart5G
      • Workflow: New, Assigned, Resolved, Reopened (start simple)
      • What Fields: Description, Status
      • Hopefully will demo at next week's TST
  • GitHub default branch should be main instead of master. Ajay Lotan Thakur 
    • Master is old way; main is the new way (and the default)
    • Prefer to have all the same; most currently master
    • Decision: leave it as is (expect to be mixed)
  • BESS-UPF Helm Charts: Current charts assume symmetry for the access and core interfaces (i.e., same CNI Plug-in for both) Gabriel Arrobo
    • Any objection about making the Helm Charts as generic as possible such that each individual CNI can be independently chosen?
    • Example: access=macvlan, core=host-device
    • But it remains the default that they are the same (currently macvlan); so remains backward compatible
    • Will eventually want to expose in OnRamp
  • Road map cleanup Ajay Lotan Thakur Gabriel Arrobo 
    • Priority to take up only SBI upgrade this quarter/end of Sept 2024
    • Priority on bug fixes and issues reported by other community members
    • See Roadmap for more details
    • Work harder to get info to the community / work to attract contributors
  • SD-RAN update Woojoong Kim 
    • Working with a team of 5 students
    • Github action → Almost done (run tests and publish images)
    • Scalable RAN Simulator → on going; hopefully done in Jun.
    • Dependency update → dependabot has been busy; resolving 1-by-1 (waiting on GitHub Actions)
  • OnRamp Update Bilal Saleem 
    • Separate Management Node → Dealing with local charts was the complication
    • Dueling Docker installs → Ansible playbook now checks for existing Docker, per Docker best practices
    • Check that multiple gNBs work for data plane
    • Working on proposal for incorporating scalable Core into OnRamp
  • QA Update Kunal Kapoor 
    • JJB code commit is done
    • Working on updating Readme and streamlining the code as per the current requirement.
    • David Ferguson (Deactivated) :  Customizing the job as opposed to customizing the build machine (so can dynamically grab and release VMs)

...

  • Archive "tiny" (unused) repos [Gabriel]
    • As part of release 1.4, several repos were consolidated into the "util" repo
  • Do a patch release for Docker images (1.4.1) [Gabriel]
    • New Helm Chart also just published
    • Expect a PR to update OnRamp
  • Working on a blueprint for a DPDK configuration
  • SD-Core Roadmap Discussion
    • What's the process
      • We have an old Google Doc
      • Move it in the Wiki
      • Community contributes
    • How do we move past Release 15?
      • Start with OpenAPI spec for R17
      • Generate code (and test/fix)
      • Results in the wish-list
  • SD-RAN Status
    • Training new contributors
      • To document in a new wiki page for future onboarding
    • Jenkins to Github action conversion for SD-RAN is mostly done
      • Expect to complete this week 
  • ROC Status
    • PR now merged
    • New Helm Chart published by GitHub Action
    • New version (2.1.36) was published => it did not exist (but has been used by OnRamp)
    • What gives???
  • OnRamp Status
    • Bilal looking into two issues
    • Docker issue when deploying in CloudLab
    • Local helm charts on master node
  • JJB Status
    •  Testing on AWS (Goal is to be re-producible)
    • Automate Jenkins job creation using JJB and definitions from git repo
      • Seed Job on builtin node to pull the latest changes in aether-jenkins repo - Done.
      • Cron job to update the jobs in Jenkins. 
  • ...

...

...