Versions Compared

Key

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


Attendance

Please enter you name and company. Tag yourself using LF ID User Name. Don't have an LF ID yet? Go here: https://myprofile.lfx.linuxfoundation.org/.

NameCompany
Linux Foundation
Rajesh Krishnan Peraton Labs
Lincoln Thurlow University of Southern California/ Information Sciences Institute
Prajith Paran Du Telecom
























                        

Agenda:

  • Antitrust
  • Start Recording- helps facilitate minutes and Action Items
  • Welcome 1st Time Attendees
  • Project Updates
  • Events
  • 5G Super Blueprint Library Update
  • Upcoming Meetings

  • Documentation (reference)
  • Any Other Business
    • Look for a new Zoom bridge on the LFX Meeting platform

...

  • SEDIMENT+KubeArmor
    • Initial PoC:
    • Kaloom lab- VMs built - Risk
      • Need VPN to Kaloom. LJ to Contact Ganesh (gave@kaloom.com)
    • Potential Hex Five sub project - Cesare/Rajesh
      • Investigative meeting took place between Peraton and Hex Five (Cesare).
      • Next Step- Hex Five to come back with a proposal
    • Next Steps:
      • Rajesh- Set back. Need to revaluate camera wrt memory
        • Options
          • Potential to use a low end sensor (ex: temperature sensor)
          • Find camera that requires less memory
      • Kaloom/UNH implementation
      • Aarno labs has implemented SEDIMENT. Raj to get details
        • Can they provide a demo or overview to the community?
      • Identify and develop a security Use Case - Yogen?
        •  Yogen - in process (08/09)
        •  Yogendra Pal - setup meeting with Accuknox to discuss security use case.  Report back on an upcoming meeting

...

  • SABRES: Slice Selection, Path Validation, Multiparty Management
    • Three use cases will have separate services associated
    • What orchestrator will/can be used?
      • potential to duplicate Simplified E2E Network Slicing (Aarna) using EMCO
        • Aarna confirms all Simplified network slicing solution will be open source and NDA will not be required.
        • Check on licensing
      • potential to leverage Wavelabs slicing using EMCO
    • ICCCN paper: ICCCN_2023_paper_187.pdf
    • Code repository (https://pulwar.isi.edu/sabres/cbs/cbs) that was used during the last government demonstration.  This is the initial code base (src directory), which will not be the final product (as this version only works on 2-3 variables, rather than arbitrary).  This code was used to replace ETSI's OSM's PLA module (using minizinc constraint solver) with CBS [https://osm.etsi.org/gitlab/osm/pla].
    • EMCO failed to come up - waiting on Simplified Slicing repo
    • SD-Core setup at ICI
    • Next Steps:
      • Open question on open sourcing SABREs (university policy)
      • Replicate Simplified Slicing demo locally in ISI lab (Lincoln)
      • Debug the environment (Lincoln)
      • Set up a drop-in replacement for the current slicing algorithm with CBS algorithm (Lincoln)
      • Leverage UNH and Kaloom. Ganesh and Lincoln

...

  • ONAP SMO

    • Scope-
      • use ONAP SMO to exercise gNodeB. Showcase RAN connectivity (O1 interface)
      • Showcase orchestration
      • Connect gNodeB to Kaloom core - Risk
      • Potential reference point/tie-in with ORAN-SC
    • Requirements/Goals
      • Showcase RAN connectivity (O1 interface)
      • exercise gNodeB (UNH)
      • Demonstate core connectivity
      • Demonstate core connectivity
      • Stretch goal- tie-in with ORAN-SC
    •  Resources-
      • Aarna Networks
      • UNH - gNodeB
        • UNH has space for a core but no people resources. Potential for a 5G SBP  resource to help
      • Kaloom - Core- Risk
        • UNH has space for a core but no people resources. Potential for a 5G SBP  resource to help
    • Next Steps-
      • Readout from 09/01 meeting on Next Steps
        • gNodeB config
      • confirm availability of gNodeB (Lincoln)
      • confirm availability of core at Kaloom (Ganesh) - Risk


Edge Site Selection and Placement (Equinix) - On Hold

...

Documentation - Deliverables to the 5G SBP

From Use Case Template:

Blueprint Outputs 

(Mandatory)

check all that apply:

  •  Code repository
  •  Configuration files (e.g. Helm charts, etc.)
  •  Upstreaming to relevant projects 
  •  Continuous Integration
  •  Test requirements and test results (if applicable)
  •  Documentation:
    •  Overview and Theory of Operation (i.e., what does it do?)
    •  Deployment and setup
  •  Videos
    •  demo
    •  lab setup/behind the scenes
    •  other
    •  YouTube
  • Create a template for documentation collateral
  • Playbook-like theme
  • YouTube - independent of any D&TF YouTube postings, but cross-linked

...