Page History

...

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

Sep 16, 2019

attendees: Bill, Lionel Pelamourgues
some discussion about use cases for this blueprint - Bill to introduce Lionel to Glenn Seiller for further discussion

...

Hayde Martinez Landa (Intel)
discussion around next steps for Ada & Hayde to get the 2nd lab up & running (on Intel's premises)
the following actions were identified, with some progress notes since then...
- Ada/Hayde send their server information – we’ll review & assess how similar it is to where we’re running our Distributed Cloud
  - Memory: 64GB
  - CPU: Intel(R) Xeon(R) CPU E3-1275 v6 @ 3.80GHz (8 cores)
  - Disks: 2x447GB
  - Network Cards: Intel X550T, Intel I210
- Bill send Jenkins information/instructions
  - see Jenkins Guide, Jenkins Peering Guide and Push Logs to Nexus
- Bill find out how soon (roughly) we think we’ll be able to send the Distributed Cloud installation recipe
  - current plan is that this information should be available at some time during the week of Sep 23rd
- Bill to send the recurring meeting info to Ada/Hayde
  - I’ve added you to the recurring meeting directly
  - please follow the instructions at Akraino TSC Group Calendar

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

...