@Haruhisa Fukano

@Peter Pouliot

Ampere Computing

@Ike Alisson

@Ricardo Noriega

Red Hat

@jim.xu@zenlayer.com (Deactivated)

@Rong Huang

China Unicom

@Jeff Brower

@Kuralamudhan Ramakrishnan (Deactivated)

Intel

@khemendra kumar

@Sukhdev Kapur

Juniper

@Yu, Liya

@thorking

PGTalk

@Mark Shan

/ @Bart Dong

@Fu Li

Socnoc AI Inc.

@douge (Deactivated)

@Tina Tsou (Deactivated)

Arm

@Oleg Berzin (Deactivated)

@xinhuili

Salesforce

@Randy Stricklin 

@Yanjun Chen

China Mobile Research Institute

Tuesday Guest talk

The Design and Application of Baetyl

Guest speaker Leding Li invited by TSC member @Yu, Liya

Open

Key points:

1. Baetyl problem statements are to address edge computing issues related to devices in the private networks, processing the data in real-time, synchronization between edge and cloud, and secure the data and edge.

2. Baetyl is the open-source project under LFedge to manage both clouds and edge. Baetyl consists of two components Baetyl-cloud and Baetyl in the edge.

3. Baetyl cloud run in the cloud side has the synchronizer with Baetyk in the edge, Baetyl edge is directly connected to IoT device based on the EdgexFoundry standard, and use the Baetyl cloud to get the application data, ML model and transfer the data for sampling and log to Baetyl cloud

4. AI vision demo is implemented with camera and Intel Movidius AI chipset.  Baetyl cloud loads the AI Model on an AI chipset and sampling happens in real-time.

5. Speaker showcased various use cases such as Intel OpenVino and commercial use cases such as Smart Grid and Intelligent quality inspection

Questions:

Q: @Jeff Brower  How model run with different architecture. is the optimization is taken care of.

A: Leding - should be taking into consideration, only computer vision uses cases are taken into the consideration

Q: @Ike Alisson How to bring the standard into this solution

A: Leding - There are around 100 vendors getting such standard is very difficult.

Akraino Hackathon Logistic discussion 

@Kuralamudhan Ramakrishnan (Deactivated)

@Oleg Berzin (Deactivated) what's the difference between the google doc created for the discussion? Why we should look into the different venues, let take the one suggested by the MEC community itself?

@Kuralamudhan Ramakrishnan (Deactivated) Wants to see the structure in how the hackathon is conducted to see stakeholder and volunteers structure. Like to do the brainstorm as the community on various pros and cons of the venue. Want to see the success criteria for the event, don't want the event to be "yet another event" with no impact. The purpose of the document is to have the structure of why we taking the action and what our end goals for the hackathon are. Getting the sponsor required a structured document with success criteria, the impact of the hackathon, and why the actions are taken? The sponsor required these items for the sponsorship.

@Kuralamudhan Ramakrishnan (Deactivated) took an action item to sync up with Oleg on the difference and come up with the standard solution and understand the urgency on this ? who is driving the urgency here.

Akraino's annual review

@Ike Alisson @Oleg Berzin (Deactivated) @Kuralamudhan Ramakrishnan (Deactivated)

Akraino - Stage 3 - 2022-02-09 Draft

Moved to next TSC meeting

• PTLs to provide updates on the status of the Blueprints and Feature Projects

Blueprint Maturity Reviews

@haihui wang @jin peng @Yu, Liya

Moved to next TSC meeting

SL No.

Voting Member

Member Company

Y/N/A

1

@Haruhisa Fukano

2

@Ike Alisson

3

@jim.xu@zenlayer.com (Deactivated)

4

@Jeff Brower

5

@khemendra kumar

6

@Yu, Liya

7

@Mark Shan

/ @Peiying Huang

8

@douge (Deactivated)

9

@Oleg Berzin (Deactivated)

10

@Randy Stricklin 

(w/ @Paul Carver )

11

@Peter Pouliot

Ampere Computing

12

@Ricardo Noriega

Red Hat

13

@Rong Huang

China Unicom

14

@Kuralamudhan Ramakrishnan (Deactivated)

Intel

15

@Sukhdev Kapur

Juniper

16

@thorking

PGTalk

17

@Fu Li

Socnoc AI Inc.

18

@Tina Tsou (Deactivated)

Arm

19

@xinhuili

Salesforce

20

@Yanjun Chen

China Mobile Research Institute