Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 54 Next »

Table of Contents

Team Info

Project Technical Lead

Bill Zvonar.  Elected 1/17/19.

Committers

Committer

Company

Contact Info

 Committer BioPicture 

PTL

Bill ZvonarWind Riverbill.zvonar@windriver.com


Y

Bruce Jones

Intel

bruce.e.jones@intel.com



N

Dariush EslimiWind RiverDariush.Eslimi@windriver.com

N
Alex KozyrevWind RiverAlex.Kozyrev@windriver.com

N

Documentation

Presentations

Blueprint Proposal

StarlingX Far Edge Distributed Cloud Blueprint Proposal

Blueprint Specification

StarlingX Far Edge Distributed Cloud Blueprint Specification

Rel 1 Documentation

Rel 1 Self-Certification Status

See StarlingX Far Edge Distributed Cloud Documentation for further Rel 1 documentation.

Demo Video (from ONS)

Meetings

Meetings will be held bi-weekly on Mondays at 3 pm EST/EDT,  will be provided here.

Jul 22, 2019

  • attendees: Bill, Dariush, Neil Oliver
  • abbreviated meeting today, will work via email and ad-hoc discussions on Rel 2 planning and blueprint family expansion 
  • Neil Oliver from Intel joined today - Neill is part of the OpenNess group in the Network & Custom Logic group at Intel 
  • OpenNESS is Open Network Edge Services Software
    • https://www.openness.org/
    • was NEV SDK
    • inspired by ETSI MEC platform
    • support LTE, WiFi, Landline I/F
    • added the data plane – e.g. traffic steering at the edge node to the right application (e.g. a Container or a VM)
    • also a controller component
  • Open NESS controller can use underlying components (like an OpenStack controller)
  • they're in their initial release open source s/w
  • many customers that have experience with the NEV SDK, which has been out for 2-3 years
    • there’s a Wind River Linux (Titanium Server) and a CentOS version
  • Neill's looking at synergy with StarlingX control components – maybe the Open NESS controller could act as a plug-in that StarlingX could use
  • OpenNESS is in a couple of other blueprints as well - one is the Tencent connected vehicle blueprint – traffic steering to a vehicle or an edge device
  • we'll continue talking to Neill about the possibilities for defining a blueprint that includes StarlingX and OpenNESS

Jul 8, 2019

  • team is currently working on defining the plan for Rel 2, and what our "infrastructure" work items are, as defined by the various sub-committees
  • working through the charts and updates from the Mini-Summit in June (per 06/17-19/2019 Technical Mini-Summit and Release 2 Planning)
  • currently, unclear on what the sub-committee requirements are in most cases, need to firm this up (will ask at the TSC Working meeting tomorrow)
  • missed a number of meetings leading up to Rel 1 completion - should go back and add the details here at some point

April 1, 2019

  • meeting cancelled, next one will be held on April 15 

Mar 18, 2019

  • Attendees

    • Alex, Bill, Dariush, Glenn, Greg, Numan

  • ONS Demo Video
    • lab setup is in progress, should be ready tomorrow
    • Bill: post the video up on the SFEDC blueprint wiki
    • Dariush: put a preliminary README file up on the SFEDC Gerrit
  • ONS Booth
  • ONS TSC Face to Face
    • per Glenn, it’s on Tuesday
    • Dariush will be on vacation, not able to attend, Glenn will work a plan with Ian to cover
  • SFEDC Dedicated Hardware
    • while we're working our plan to get our own dedicated HW, we should confirm that we’re planning to validate our blueprint on the Community Lab
    • Bill to raise with the process sub-committee 
  • Release 1 Planning
    • Rel 1 pushed to end of May now (May 31st), approved at the last TSC meeting
    • it was acknowledged that all of the blueprints will remain in incubation after this release

Mar 4, 2019

  • focused on plan for ONS demo video using in-house lab facilities - target by March 15
  • no line of sight yet to lab HW, expecting update by end of week 

Feb 25, 2019

Agenda items:

  • plan for dedicated lab H/W
  • refining plan for Rel 1 - lab setup, use cases, CI/CD
  • plan for ONS demo video - subset of Rel 1 functionality 
  • day/time/cadence for regular meeting - bi-weekly on Mondays, need to create meeting on Akraino calendar

Attachments

  File Modified
No files shared here yet.

  • No labels