2019-03-05 LDCG SC Face To Face Minutes

Owned by Vicky Janicki (Deactivated)
Last updated: Apr 09, 2019 by Former user (Deleted)


=

Attendance

Committee Members 

NamePresent

Elsie Wahlig Linaro

  (tick)  

Andy Wafaa ARM

 

  (tick)  

Jon Masters Red Hat

 

  (tick)  

Kangkang Shen Huawei

 

  (tick)  

Larry Wikelius Marvell

 

  (tick)  

Zi Shen Lim Marvell(tick)

 

Guests 

NamePresent
Vicky Janicki (Linaro)(tick)
Ganesh Raju (Linaro)(tick)
Jorge (Linaro)(tick)
Tony Niedbalski (Arm)(tick)
Stephen Cole (Arm)(tick)
Leif Lindholm Linaro) (remote)(tick)
Gema Gomez-Solano (Linaro) (Remote)(tick)
Ard Biesheuvel (Linaro) (Remote)(tick)

Minutes

LDCG Roadmaps

Day 1 Recording

Raw Notes Here

Introductions

  • LW:  How do we connect with the broader Linaro.  Recommendation is via the TSC

  • KK:  Arm server is in a different place.  It’s here and working.

  • AW: How much capacity is there in DC?

  • LW: How does ML/AI tie into HPC and LDCG?

  • LW:  Assignees need to be transparent, checked monthly.  Describe contractual obligations vs actual assignees working.

  • LW: frustrated with lack of enforcement of assignees.

  • KK:   Follow-up on designating CCIX Member Engineer

  • EW: GCC (Green Computer Consortium - China) is joining as Associate Member. Another Associate Member is pending. Both interested in Developer Cloud. Expect Associate Members to start up China Developer Cloud setup with Jorge’s help.

  • LW:  Split between timezones.  Is LDCG divided?

  • EW:  consider if we want to merge the TZ call

  • KK:  Huawei Contact for OS is Hanjun Guo.  For Drivers is Kenneth Lee. For Big Data its the solution group, through Kenneth Lee.  

Enterprise Reference Architecture slide

  • LW:  Is ERP still relevant since we are now in an enabled state? Do we need it?   Members enable their own platform.

  • KK:  needs ERP to enable CCIX project.  

  • LW:  we don’t have luxury of sponsoring things that need to be in landing team.

  • Leif:  we were juggling a lot of things in the past that needed a single focus.  Now we have a single focus for work.

Reference Firmware

  • Was part of ERP

  • LW: Wants to either kill ERP or merge requirements into other activities.
  • JN:  support for M400 - now deprecated - is in ERP.   DC can deploy with upstream kernels
  • KK: Who’s working on ERP?
  • Gema:   ERP was consuming â…“ resources every year.
  • Z:  EDK2 is within scope?   Leif: Yes
  • …
  • LW: Is Reference Firmware passing Server Ready today?  
  • Leif:  Ask me in a month


Slide:  Platform Server architecture


  • KK:Both Open source firmware and SBSA QEMU Machine are very important to KangKang

  • Z: Is there an endpoint for Platform Server Architecture

    • Leif:  continues with each new SBSA level

    • Z: Define what SBSA level we are targeting in QEMU project.

  • EW: Need to define and document what is meant as a project

  • KK: How many resources are being consumed by ERP?  

    • Gema: Each project has been individually counting.

    • EW:  Need transparency here.


Slide: Server Ready Process


  • KK: Suggestion that Linaro provide a chargeable service for non-Members

  • LW: Missing a key part of the chain which hardware partners (OEM/ODM); Don’t believe OEM/ODM will pay for this service.

  • Concern about the quality of the firmware along the supply chain

  • SCole:  ODM’s claim they do more testing than SBSA do

  • EW: Value is in the compliance

  • Jon:  RH runs ACS on vendor platforms

  • Server Ready proposal (AW)

  • should be a project outside LDCG

  • Linaro exec management supportive

  • Where is TBD (like professional services)

  • In LDCG, because server is in the name

  • Jon:  Need OEM’s involvement

  • Jon:  Is this something we can take on?

CCIX - Ard

  • Z:  No CCIX roadmap yet.  

  • Main contributions have been with Arm landing team

  • J: On Linux needs to be done generic, upstream friendly way

  • LW: Proposed Ard provides 1 day a week of support

OpenBMC Enablement- Leif

  • Not much progress on OpenBMC due to lack of platforms

  • Planning to use QEMU in lieu of available hardware.

  • FYI: OCP Presentation

  • There is ThunderX Sabre board that could be available.  

  • Projects using ThunderX can’t be shared with openbmc development

  • Larry:  They can find a dedicated Sabre system to support openBMC

  • Action:  determine logistics of what/where to put platform.

  • Larry: What are the human resource requirements.  This was HXT

    • Elsie: Determine with Graeme.

  • Jon:  general comment.  For each community what are our touchpoints

  • Jon: We have to determine what it is we want.

  • KK:  Will look to see what resources Huawei can contribute.  

  • LW: Understand the state of the broader union to determine gaps. (Next step for SC to talk to Dong Wei @ Arm)

  • Jon: Need to define the task

  • Determine requirements before ServerAC event in mid April - right after BKK

Kernel Testing Integration - Rafael / Ard

  • LKFT was done in parallel with Kernel CI

  • Could be an interim solution to getting to a 0 day kernel test

  • Z:  Is 0 Day a Linaro, Arm issue?  It’s an Arm ecosystem issue.

  • Is AMD part of it?  No, but they ride the coat-tails (because ISA)

Larry will donate hardware

  • Jon:  Wants cloud management for testing so we can scale out across other facilities.

  • Rafael: LKFT does spin up VM’s

  • JN: no current openstack api implementation in LAVA

  • Gema:   Kubernetes is not multi-tenant so difficult to replace Openstack at the moment.

Outcome:

  1. How much will it take to integrate testing into Lava?  Minimum amount of work. AI: Gema scope

  2. What is needed for cloud management for testing so we can scale out across other facilities.

  3. Work with ARM for 0-day end goal


Android In The Cloud - Larry W


  • LW: Let’s target things we can do differently

  • Option A:

    • Licensing can’t be solved without Arm business folks.

    • Action item:  Steve Cole

  • Option B

    • Steve Cole: End-user/consumers needs this

    • Larry:  Wants Android CI in LKFT scoped.  AI: Elsie

  • Option C

    • Steve Cole: End-user/consumers needs this

  • Option D

    • Need path for AMD to generate revenue

    • Discussions between Arm & AMD next week @ GDC

    • Action item:  Steve Cole

  • More

    • Jon: do B and C for selling the dream

    • All in agreement we want A and D.

ILP32 - Matteo

  • KK: Customers do not want to change. Need ILP32 already; Custom software

  • Jon: Need to recompile to use ILP32; Networking/Wireless use cases

  • Matteo: Need LTS Support

  • Larry:   Needs ILP32 for selling servers to produce benchmarks.

    • He can use openSUSE for spec.org submission.  Uses current branch.

  • Matteo:  In order to get it mainlined, they need SLES commitment.  

  • KK:  Needs it for communication business.

  • LW: Propose Arm to provide the scoping and effort to support this branch - Andy W to find out

  • KK: ¼ of an engineer to support (3 months effort over a year)

  • Revisit at BKK19


OpenJDK

  • Arm has not had much help from members for OpenJDK.

  • They will continue working on OpenJDK at Arm

  • Stuart will no longer be an assignee.  Will focus on AdoptOpenJDK and Arm team development.

  • Releases will be done through AdoptOpenJDK

  • Let’s celebrate the success and move on

  • Current distributions


Ecosystem Enablement - KangKang

  • Slide 1 -

1. Alot of commercial sw is based on open source

2. If there is a proprietary application, there is often an open source equivalent

3. Making sure the open source version is equivalent can be used as leverage

  • Slide 2:

    • Bullet 1 - Open Source Arm Tools - in Lead Projects.  What are these?

  • Slide 4:

    • What can we/Linaro do?

<end>