Versions Compared

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.

...

If you need technical help from the Linux Foundation IT staff, please submit a ticket

Future Meetings

  • ...

8-

...

27-24  (Topics for Next Meeting)

  • ...InfrastructureJiraProduction site available at https://jira.aetherproject

8-20-24

  • SD-RAN
    • Still targeting 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 with other PRs
    • No progress on logging
    • Discussion about e2e test on PRs
    • Waiting on repo omec-cni, omec-pod-init (to rename)

8-13-24

  • SD-Core
    • Check with Ajay again about an SD Core deployment mode (below)
    • Status update:
      • Removed in gnbsim dependency from the CommonConsumerTestData. There were a few functions calling the CommonConsumerTestData  but these functions were not used. So, CommonConsumerDataTest  repo is now archived
    • golangci-lint not detecting all issues. For example, staticcheck  is enable in golangci  and it successfully completes. However, if we run staticcheck  by itself, it finds several issues that are not found through golangci 
    • We use logrus  (https://github.com/sirupsen/logrus) for logging, where the last commit is from June 2023. This might mean that the project is inactive (none is actively maintaining it). Based on this, I explore a few options and zap (https://github.com/uber-go/zap) seems to be a good alternative. As per its description zap is "Blazing fast, structured, leveled logging in Go". My suggestion would be to replace the logger. What are your thoughts? If agree, who can volunteer to work on this?
    • It would be good to check whether golanci-lint catches issues when using zap
    • GitHub Action (or Jenkins job) to run E2E tests for PR verification/validation
      • This could mean the use of a simplified version of AiaB
    • Bring omec-cni  and omec-pod-init from Gerrit to GitHub (omec-project organization)
    • A "Scalability" PR is in progress
    • Metrics currently not being displayed by Grafana → dashboard spec has fallen out-of-date
  • OnRamp
  • Infrastructure
    • Jira
      • Setting up production site – anticipate availability EOD Wed.
        • Site will be lf-aether.atlassian.net → jira.aetherproject.org
      • Accounts will be initially all invited members of the TSC
        • Please file a ticket (in lf-aether-test.atlassian.net) if you want to pre-seed other accounts
    • Confluence
      • Migration to Cloud (from existing LF-hosted site)
        • Test migration of existing content (from current wiki.aetherproject.org) this week
          • No downtime
          • Will request (on #aether-dev?) BETTER SUGGESTION? (Yes – largest subscription) for folks to review test site for validity
        • Ideally, request production migration next week's TSC
        • Upon approval, site will be offline approximately 4 hours
        • No functional changes anticipated.

...

  • 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 (Deactivated) 
    • 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. 
  • ...

...

...