Date   
Upcoming Event: Akraino Technical Community Call (Weekly) - Thu, 01/02/2020 11:00am-12:00pm #cal-reminder

technical-discuss@lists.akraino.org Calendar <technical-discuss@...>
 

Reminder: Akraino Technical Community Call (Weekly)

When: Thursday, 2 January 2020, 11:00am to 12:00pm, (GMT-05:00) America/New York

Where:https://zoom.us/j/919148693

View Event

Organizer: technical-discuss@...

Description:

Akraino Technical Community Call: TSC updates to technical community and deeper dives into topics as applicable. Meeting content posted to Technical Community Wiki.
Meeting Lead: Kandan Kathirvel, Akraino TSC Chair


Akraino Edge Stack is inviting you to a scheduled Zoom meeting.
Join from PC, Mac, Linux, iOS or Android:
https://zoom.us/j/919148693
Or iPhone one-tap : US: +16699006833,,919148693# or +16465588656,,919148693#
Or Telephone: Dial(for higher quality, dial a number based on your current location):
US: +1 669 900 6833 or +1 646 558 8656 or +1 877 369 0926 (Toll Free) or +1 855 880 1246 (Toll Free)
Meeting ID: 919 148 693
International numbers available:
https://zoom.us/u/adnlim1pfM

Upcoming Event: Akraino Technical Community Call (Weekly) - Thu, 01/02/2020 11:00am-12:00pm #cal-reminder

technical-discuss@lists.akraino.org Calendar <technical-discuss@...>
 

Reminder: Akraino Technical Community Call (Weekly)

When: Thursday, 2 January 2020, 11:00am to 12:00pm, (GMT-05:00) America/New York

Where:https://zoom.us/j/919148693

View Event

Organizer: technical-discuss@...

Description:

Akraino Technical Community Call: TSC updates to technical community and deeper dives into topics as applicable. Meeting content posted to Technical Community Wiki.
Meeting Lead: Kandan Kathirvel, Akraino TSC Chair


Akraino Edge Stack is inviting you to a scheduled Zoom meeting.
Join from PC, Mac, Linux, iOS or Android:
https://zoom.us/j/919148693
Or iPhone one-tap : US: +16699006833,,919148693# or +16465588656,,919148693#
Or Telephone: Dial(for higher quality, dial a number based on your current location):
US: +1 669 900 6833 or +1 646 558 8656 or +1 877 369 0926 (Toll Free) or +1 855 880 1246 (Toll Free)
Meeting ID: 919 148 693
International numbers available:
https://zoom.us/u/adnlim1pfM

Re: [Akraino TSC] New Blueprint proposaled for review

Tapio Tallgren
 

________________________________________
From: Zhang,Hechun <zhanghechun@...>
Sent: Thursday, January 2, 2020 13:19
To: Tallgren, Tapio (Nokia - FI/Espoo); Andrew Wilkinson
Cc: Andrew Wilkinson; technical-discuss@...; tsc@...
Subject: Re: [Akraino TSC] New Blueprint proposaled for review

Hi all,

Can we postpone this presentation until the next week? I need to go to the hospital right now since family's illness.
Sorry for the inconvenience.


--
Best regards.

Baidu
NetArch
Tel: 010-56796212
Mobile: +86-15010096386
Email: zhanghechun@...




在 2020/1/2 下午4:12,“Zhang,Hechun”<zhanghechun@...> 写入:

OK. That time will be fine for me. It's 10:00 PM in Beijing.

在 2019/12/27 下午10:16,“tsc@... 代表 Tapio Tallgren”<tsc@... 代表 @tapio_t> 写入:


Date sounds good, but the time after TSC meeting is kinda late for China (midnight if I can calculate right).


________________________________________
From: Andrew Wilkinson <arkwilkinson@...>
Sent: Friday, December 27, 2019 14:42
To: Tallgren, Tapio (Nokia - FI/Espoo)
Cc: Andrew Wilkinson; technical-discuss@...; tsc@...; zhanghechun@...
Subject: Re: [Akraino TSC] New Blueprint proposaled for review

Hi Tapio,

I don’t think we’ll get the best attendance on January 2nd.

Would suggest it’s best to do it after the TSC Thursday call on the following week (9th)

Andrew

On Fri, Dec 27, 2019 at 1:09 AM Tapio Tallgren <@tapio_t<mailto:@tapio_t>> wrote:

Yes, no problem. Should we use the January 2 slot for this, although there is no TSC call that day? And would 6 AM PST/2 PM UTC be too late? We have used that timeslot earlier with presentations from China.

-Tapio

________________________________________
From: Andrew Wilkinson <andrew.wilkinson@...<mailto:andrew.wilkinson@...>>
Sent: Thursday, December 26, 2019 17:15
To: zhanghechun@...<mailto:zhanghechun@...>; technical-discuss@...<mailto:technical-discuss@...>; tsc@...<mailto:tsc@...>; Tallgren, Tapio (Nokia - FI/Espoo)
Subject: RE: New Blueprint proposaled for review

Hi Tapio,

Can you schedule at the next free community call for Zhang to present this proposal first.

Thanks,

Andrew

From: process@...<mailto:process@...> <process@...<mailto:process@...>> On Behalf Of Zhang,Hechun via Lists.Akraino.Org<http://Lists.Akraino.Org>
Sent: Wednesday, December 25, 2019 18:42
To: tsc@...<mailto:tsc@...>; process@...<mailto:process@...>; technical-discuss@...<mailto:technical-discuss@...>
Cc: process@...<mailto:process@...>
Subject: [Akraino Process Sub-Committee] New Blueprint proposaled for review

Dear Colleagues,

Attached is a new proposal blueprint from Baidu, with the name of Robotaxi, for your reference. And this is a blueprint that focuses on establishing an open source MEC platform combined with AI capabilities in the autonomous driving scenario.

Listed below is the wiki link for your information:
https://wiki.akraino.org/display/AK/The+AI+Edge%3A+RoboTaxi<https://protect2.fireeye.com/v1/url?k=ec0a3f9c-b0801304-ec0a7f07-0cc47ad93eae-11377fb361a3ac27&q=1&e=3ebd0e24-e8e5-4ecb-a2af-76d90fb85929&u=https%3A%2F%2Fwiki.akraino.org%2Fdisplay%2FAK%2FThe%2BAI%2BEdge%253A%2BRoboTaxi>

May I ask for a UTC +8:00 friendly time to have a review for this BP?


--
Best regards.

Baidu
NetArch
Tel: 010-56796212
Mobile: +86-15010096386
Email: zhanghechun@...<mailto:zhanghechun@...><mailto:zhanghechun@...<mailto:zhanghechun@...>>

Re: [Akraino TSC] New Blueprint proposaled for review

Tapio Tallgren
 

Yes, next week was proposed.

-Tapio

________________________________________
From: Zhang,Hechun <zhanghechun@...>
Sent: Thursday, January 2, 2020 13:19
To: Tallgren, Tapio (Nokia - FI/Espoo); Andrew Wilkinson
Cc: Andrew Wilkinson; technical-discuss@...; tsc@...
Subject: Re: [Akraino TSC] New Blueprint proposaled for review

Hi all,

Can we postpone this presentation until the next week? I need to go to the hospital right now since family's illness.
Sorry for the inconvenience.


--
Best regards.

Baidu
NetArch
Tel: 010-56796212
Mobile: +86-15010096386
Email: zhanghechun@...




在 2020/1/2 下午4:12,“Zhang,Hechun”<zhanghechun@...> 写入:

OK. That time will be fine for me. It's 10:00 PM in Beijing.

在 2019/12/27 下午10:16,“tsc@... 代表 Tapio Tallgren”<tsc@... 代表 @tapio_t> 写入:


Date sounds good, but the time after TSC meeting is kinda late for China (midnight if I can calculate right).


________________________________________
From: Andrew Wilkinson <arkwilkinson@...>
Sent: Friday, December 27, 2019 14:42
To: Tallgren, Tapio (Nokia - FI/Espoo)
Cc: Andrew Wilkinson; technical-discuss@...; tsc@...; zhanghechun@...
Subject: Re: [Akraino TSC] New Blueprint proposaled for review

Hi Tapio,

I don’t think we’ll get the best attendance on January 2nd.

Would suggest it’s best to do it after the TSC Thursday call on the following week (9th)

Andrew

On Fri, Dec 27, 2019 at 1:09 AM Tapio Tallgren <@tapio_t<mailto:@tapio_t>> wrote:

Yes, no problem. Should we use the January 2 slot for this, although there is no TSC call that day? And would 6 AM PST/2 PM UTC be too late? We have used that timeslot earlier with presentations from China.

-Tapio

________________________________________
From: Andrew Wilkinson <andrew.wilkinson@...<mailto:andrew.wilkinson@...>>
Sent: Thursday, December 26, 2019 17:15
To: zhanghechun@...<mailto:zhanghechun@...>; technical-discuss@...<mailto:technical-discuss@...>; tsc@...<mailto:tsc@...>; Tallgren, Tapio (Nokia - FI/Espoo)
Subject: RE: New Blueprint proposaled for review

Hi Tapio,

Can you schedule at the next free community call for Zhang to present this proposal first.

Thanks,

Andrew

From: process@...<mailto:process@...> <process@...<mailto:process@...>> On Behalf Of Zhang,Hechun via Lists.Akraino.Org<http://Lists.Akraino.Org>
Sent: Wednesday, December 25, 2019 18:42
To: tsc@...<mailto:tsc@...>; process@...<mailto:process@...>; technical-discuss@...<mailto:technical-discuss@...>
Cc: process@...<mailto:process@...>
Subject: [Akraino Process Sub-Committee] New Blueprint proposaled for review

Dear Colleagues,

Attached is a new proposal blueprint from Baidu, with the name of Robotaxi, for your reference. And this is a blueprint that focuses on establishing an open source MEC platform combined with AI capabilities in the autonomous driving scenario.

Listed below is the wiki link for your information:
https://wiki.akraino.org/display/AK/The+AI+Edge%3A+RoboTaxi<https://protect2.fireeye.com/v1/url?k=ec0a3f9c-b0801304-ec0a7f07-0cc47ad93eae-11377fb361a3ac27&q=1&e=3ebd0e24-e8e5-4ecb-a2af-76d90fb85929&u=https%3A%2F%2Fwiki.akraino.org%2Fdisplay%2FAK%2FThe%2BAI%2BEdge%253A%2BRoboTaxi>

May I ask for a UTC +8:00 friendly time to have a review for this BP?


--
Best regards.

Baidu
NetArch
Tel: 010-56796212
Mobile: +86-15010096386
Email: zhanghechun@...<mailto:zhanghechun@...><mailto:zhanghechun@...<mailto:zhanghechun@...>>

Re: [Akraino TSC] New Blueprint proposaled for review

Zhang,Hechun
 

Hi all,

Can we postpone this presentation until the next week? I need to go to the hospital right now since family's illness.
Sorry for the inconvenience.


--
Best regards.

Baidu
NetArch
Tel: 010-56796212
Mobile: +86-15010096386
Email: zhanghechun@...




在 2020/1/2 下午4:12,“Zhang,Hechun”<zhanghechun@...> 写入:

OK. That time will be fine for me. It's 10:00 PM in Beijing.

在 2019/12/27 下午10:16,“tsc@... 代表 Tapio Tallgren”<tsc@... 代表 @tapio_t> 写入:


Date sounds good, but the time after TSC meeting is kinda late for China (midnight if I can calculate right).


________________________________________
From: Andrew Wilkinson <arkwilkinson@...>
Sent: Friday, December 27, 2019 14:42
To: Tallgren, Tapio (Nokia - FI/Espoo)
Cc: Andrew Wilkinson; technical-discuss@...; tsc@...; zhanghechun@...
Subject: Re: [Akraino TSC] New Blueprint proposaled for review

Hi Tapio,

I don’t think we’ll get the best attendance on January 2nd.

Would suggest it’s best to do it after the TSC Thursday call on the following week (9th)

Andrew

On Fri, Dec 27, 2019 at 1:09 AM Tapio Tallgren <@tapio_t<mailto:@tapio_t>> wrote:

Yes, no problem. Should we use the January 2 slot for this, although there is no TSC call that day? And would 6 AM PST/2 PM UTC be too late? We have used that timeslot earlier with presentations from China.

-Tapio

________________________________________
From: Andrew Wilkinson <andrew.wilkinson@...<mailto:andrew.wilkinson@...>>
Sent: Thursday, December 26, 2019 17:15
To: zhanghechun@...<mailto:zhanghechun@...>; technical-discuss@...<mailto:technical-discuss@...>; tsc@...<mailto:tsc@...>; Tallgren, Tapio (Nokia - FI/Espoo)
Subject: RE: New Blueprint proposaled for review

Hi Tapio,

Can you schedule at the next free community call for Zhang to present this proposal first.

Thanks,

Andrew

From: process@...<mailto:process@...> <process@...<mailto:process@...>> On Behalf Of Zhang,Hechun via Lists.Akraino.Org<http://Lists.Akraino.Org>
Sent: Wednesday, December 25, 2019 18:42
To: tsc@...<mailto:tsc@...>; process@...<mailto:process@...>; technical-discuss@...<mailto:technical-discuss@...>
Cc: process@...<mailto:process@...>
Subject: [Akraino Process Sub-Committee] New Blueprint proposaled for review

Dear Colleagues,

Attached is a new proposal blueprint from Baidu, with the name of Robotaxi, for your reference. And this is a blueprint that focuses on establishing an open source MEC platform combined with AI capabilities in the autonomous driving scenario.

Listed below is the wiki link for your information:
https://wiki.akraino.org/display/AK/The+AI+Edge%3A+RoboTaxi<https://protect2.fireeye.com/v1/url?k=ec0a3f9c-b0801304-ec0a7f07-0cc47ad93eae-11377fb361a3ac27&q=1&e=3ebd0e24-e8e5-4ecb-a2af-76d90fb85929&u=https%3A%2F%2Fwiki.akraino.org%2Fdisplay%2FAK%2FThe%2BAI%2BEdge%253A%2BRoboTaxi>

May I ask for a UTC +8:00 friendly time to have a review for this BP?


--
Best regards.

Baidu
NetArch
Tel: 010-56796212
Mobile: +86-15010096386
Email: zhanghechun@...<mailto:zhanghechun@...><mailto:zhanghechun@...<mailto:zhanghechun@...>>

Re: [Akraino TSC] New Blueprint proposaled for review

Zhang,Hechun
 

OK. That time will be fine for me. It's 10:00 PM in Beijing.

在 2019/12/27 下午10:16,“tsc@... 代表 Tapio Tallgren”<tsc@... 代表 @tapio_t> 写入:


Date sounds good, but the time after TSC meeting is kinda late for China (midnight if I can calculate right).


________________________________________
From: Andrew Wilkinson <arkwilkinson@...>
Sent: Friday, December 27, 2019 14:42
To: Tallgren, Tapio (Nokia - FI/Espoo)
Cc: Andrew Wilkinson; technical-discuss@...; tsc@...; zhanghechun@...
Subject: Re: [Akraino TSC] New Blueprint proposaled for review

Hi Tapio,

I don’t think we’ll get the best attendance on January 2nd.

Would suggest it’s best to do it after the TSC Thursday call on the following week (9th)

Andrew

On Fri, Dec 27, 2019 at 1:09 AM Tapio Tallgren <@tapio_t<mailto:@tapio_t>> wrote:

Yes, no problem. Should we use the January 2 slot for this, although there is no TSC call that day? And would 6 AM PST/2 PM UTC be too late? We have used that timeslot earlier with presentations from China.

-Tapio

________________________________________
From: Andrew Wilkinson <andrew.wilkinson@...<mailto:andrew.wilkinson@...>>
Sent: Thursday, December 26, 2019 17:15
To: zhanghechun@...<mailto:zhanghechun@...>; technical-discuss@...<mailto:technical-discuss@...>; tsc@...<mailto:tsc@...>; Tallgren, Tapio (Nokia - FI/Espoo)
Subject: RE: New Blueprint proposaled for review

Hi Tapio,

Can you schedule at the next free community call for Zhang to present this proposal first.

Thanks,

Andrew

From: process@...<mailto:process@...> <process@...<mailto:process@...>> On Behalf Of Zhang,Hechun via Lists.Akraino.Org<http://Lists.Akraino.Org>
Sent: Wednesday, December 25, 2019 18:42
To: tsc@...<mailto:tsc@...>; process@...<mailto:process@...>; technical-discuss@...<mailto:technical-discuss@...>
Cc: process@...<mailto:process@...>
Subject: [Akraino Process Sub-Committee] New Blueprint proposaled for review

Dear Colleagues,

Attached is a new proposal blueprint from Baidu, with the name of Robotaxi, for your reference. And this is a blueprint that focuses on establishing an open source MEC platform combined with AI capabilities in the autonomous driving scenario.

Listed below is the wiki link for your information:
https://wiki.akraino.org/display/AK/The+AI+Edge%3A+RoboTaxi<https://protect2.fireeye.com/v1/url?k=ec0a3f9c-b0801304-ec0a7f07-0cc47ad93eae-11377fb361a3ac27&q=1&e=3ebd0e24-e8e5-4ecb-a2af-76d90fb85929&u=https%3A%2F%2Fwiki.akraino.org%2Fdisplay%2FAK%2FThe%2BAI%2BEdge%253A%2BRoboTaxi>

May I ask for a UTC +8:00 friendly time to have a review for this BP?


--
Best regards.

Baidu
NetArch
Tel: 010-56796212
Mobile: +86-15010096386
Email: zhanghechun@...<mailto:zhanghechun@...><mailto:zhanghechun@...<mailto:zhanghechun@...>>

Re: [Akraino TSC] New Blueprint proposaled for review

Tapio Tallgren
 

Date sounds good, but the time after TSC meeting is kinda late for China (midnight if I can calculate right).


________________________________________
From: Andrew Wilkinson <arkwilkinson@...>
Sent: Friday, December 27, 2019 14:42
To: Tallgren, Tapio (Nokia - FI/Espoo)
Cc: Andrew Wilkinson; technical-discuss@...; tsc@...; zhanghechun@...
Subject: Re: [Akraino TSC] New Blueprint proposaled for review

Hi Tapio,

I don’t think we’ll get the best attendance on January 2nd.

Would suggest it’s best to do it after the TSC Thursday call on the following week (9th)

Andrew

On Fri, Dec 27, 2019 at 1:09 AM Tapio Tallgren <@tapio_t<mailto:@tapio_t>> wrote:

Yes, no problem. Should we use the January 2 slot for this, although there is no TSC call that day? And would 6 AM PST/2 PM UTC be too late? We have used that timeslot earlier with presentations from China.

-Tapio

________________________________________
From: Andrew Wilkinson <andrew.wilkinson@...<mailto:andrew.wilkinson@...>>
Sent: Thursday, December 26, 2019 17:15
To: zhanghechun@...<mailto:zhanghechun@...>; technical-discuss@...<mailto:technical-discuss@...>; tsc@...<mailto:tsc@...>; Tallgren, Tapio (Nokia - FI/Espoo)
Subject: RE: New Blueprint proposaled for review

Hi Tapio,

Can you schedule at the next free community call for Zhang to present this proposal first.

Thanks,

Andrew

From: process@...<mailto:process@...> <process@...<mailto:process@...>> On Behalf Of Zhang,Hechun via Lists.Akraino.Org<http://Lists.Akraino.Org>
Sent: Wednesday, December 25, 2019 18:42
To: tsc@...<mailto:tsc@...>; process@...<mailto:process@...>; technical-discuss@...<mailto:technical-discuss@...>
Cc: process@...<mailto:process@...>
Subject: [Akraino Process Sub-Committee] New Blueprint proposaled for review

Dear Colleagues,

Attached is a new proposal blueprint from Baidu, with the name of Robotaxi, for your reference. And this is a blueprint that focuses on establishing an open source MEC platform combined with AI capabilities in the autonomous driving scenario.

Listed below is the wiki link for your information:
https://wiki.akraino.org/display/AK/The+AI+Edge%3A+RoboTaxi<https://protect2.fireeye.com/v1/url?k=ec0a3f9c-b0801304-ec0a7f07-0cc47ad93eae-11377fb361a3ac27&q=1&e=3ebd0e24-e8e5-4ecb-a2af-76d90fb85929&u=https%3A%2F%2Fwiki.akraino.org%2Fdisplay%2FAK%2FThe%2BAI%2BEdge%253A%2BRoboTaxi>

May I ask for a UTC +8:00 friendly time to have a review for this BP?


--
Best regards.

Baidu
NetArch
Tel: 010-56796212
Mobile: +86-15010096386
Email: zhanghechun@...<mailto:zhanghechun@...><mailto:zhanghechun@...<mailto:zhanghechun@...>>

Re: [Akraino TSC] New Blueprint proposaled for review

Andrew Wilkinson
 

Hi Tapio,

I don’t think we’ll get the best  attendance on January 2nd. 

Would suggest it’s best to do it after the TSC Thursday call on the following week (9th)

Andrew

On Fri, Dec 27, 2019 at 1:09 AM Tapio Tallgren <tapio.tallgren@...> wrote:

Yes, no problem. Should we use the January 2 slot for this, although there is no TSC call that day? And would 6 AM PST/2 PM UTC be too late? We have used that timeslot earlier with presentations from China.

-Tapio

________________________________________
From: Andrew Wilkinson <andrew.wilkinson@...>
Sent: Thursday, December 26, 2019 17:15
To: zhanghechun@...; technical-discuss@...; tsc@...; Tallgren, Tapio (Nokia - FI/Espoo)
Subject: RE: New Blueprint proposaled for review

Hi Tapio,

Can you schedule at the next free community call for Zhang to present this proposal first.

Thanks,

Andrew

From: process@... <process@...> On Behalf Of Zhang,Hechun via Lists.Akraino.Org
Sent: Wednesday, December 25, 2019 18:42
To: tsc@...; process@...; technical-discuss@...
Cc: process@...
Subject: [Akraino Process Sub-Committee] New Blueprint proposaled for review

Dear Colleagues,

Attached is a new proposal blueprint from Baidu, with the name of Robotaxi, for your reference. And this is a blueprint that focuses on establishing an open source MEC platform combined with AI capabilities in the autonomous driving scenario.

Listed below is the wiki link for your information:
https://wiki.akraino.org/display/AK/The+AI+Edge%3A+RoboTaxi<https://protect2.fireeye.com/v1/url?k=ec0a3f9c-b0801304-ec0a7f07-0cc47ad93eae-11377fb361a3ac27&q=1&e=3ebd0e24-e8e5-4ecb-a2af-76d90fb85929&u=https%3A%2F%2Fwiki.akraino.org%2Fdisplay%2FAK%2FThe%2BAI%2BEdge%253A%2BRoboTaxi>

May I ask for a UTC +8:00 friendly time to have a review for this BP?


--
Best regards.

Baidu
NetArch
Tel: 010-56796212
Mobile: +86-15010096386
Email: zhanghechun@...<mailto:zhanghechun@...>







Re: New Blueprint proposaled for review

Tapio Tallgren
 

Yes, no problem. Should we use the January 2 slot for this, although there is no TSC call that day? And would 6 AM PST/2 PM UTC be too late? We have used that timeslot earlier with presentations from China.

-Tapio

________________________________________
From: Andrew Wilkinson <andrew.wilkinson@...>
Sent: Thursday, December 26, 2019 17:15
To: zhanghechun@...; technical-discuss@...; tsc@...; Tallgren, Tapio (Nokia - FI/Espoo)
Subject: RE: New Blueprint proposaled for review

Hi Tapio,

Can you schedule at the next free community call for Zhang to present this proposal first.

Thanks,

Andrew

From: process@... <process@...> On Behalf Of Zhang,Hechun via Lists.Akraino.Org
Sent: Wednesday, December 25, 2019 18:42
To: tsc@...; process@...; technical-discuss@...
Cc: process@...
Subject: [Akraino Process Sub-Committee] New Blueprint proposaled for review

Dear Colleagues,

Attached is a new proposal blueprint from Baidu, with the name of Robotaxi, for your reference. And this is a blueprint that focuses on establishing an open source MEC platform combined with AI capabilities in the autonomous driving scenario.

Listed below is the wiki link for your information:
https://wiki.akraino.org/display/AK/The+AI+Edge%3A+RoboTaxi<https://protect2.fireeye.com/v1/url?k=ec0a3f9c-b0801304-ec0a7f07-0cc47ad93eae-11377fb361a3ac27&q=1&e=3ebd0e24-e8e5-4ecb-a2af-76d90fb85929&u=https%3A%2F%2Fwiki.akraino.org%2Fdisplay%2FAK%2FThe%2BAI%2BEdge%253A%2BRoboTaxi>

May I ask for a UTC +8:00 friendly time to have a review for this BP?


--
Best regards.

Baidu
NetArch
Tel: 010-56796212
Mobile: +86-15010096386
Email: zhanghechun@...<mailto:zhanghechun@...>

Re: New Blueprint proposaled for review

Andrew Wilkinson
 

Hi Tapio,

 

Can you schedule at the next free community call for Zhang to present this proposal first.

 

Thanks,

 

Andrew

 

From: process@... <process@...> On Behalf Of Zhang,Hechun via Lists.Akraino.Org
Sent: Wednesday, December 25, 2019 18:42
To: tsc@...; process@...; technical-discuss@...
Cc: process@...
Subject: [Akraino Process Sub-Committee] New Blueprint proposaled for review

 

Dear Colleagues,

 

Attached is a new proposal blueprint from Baidu, with the name of Robotaxi, for your reference. And this is a blueprint that focuses on establishing an open source MEC platform combined with AI capabilities in the autonomous driving scenario.

 

Listed below is the wiki link for your information:

https://wiki.akraino.org/display/AK/The+AI+Edge%3A+RoboTaxi

 

May I ask for a UTC +8:00 friendly time to have a review for this BP?

 

 

-- 

Best regards.

 

Baidu

NetArch

Tel: 010-56796212

Mobile: +86-15010096386

Email: zhanghechun@...

 

 

 

New Blueprint proposaled for review

Zhang,Hechun
 

Dear Colleagues,

 

Attached is a new proposal blueprint from Baidu, with the name of Robotaxi, for your reference. And this is a blueprint that focuses on establishing an open source MEC platform combined with AI capabilities in the autonomous driving scenario.

 

Listed below is the wiki link for your information:

https://wiki.akraino.org/display/AK/The+AI+Edge%3A+RoboTaxi

 

May I ask for a UTC +8:00 friendly time to have a review for this BP?

 

 

-- 

Best regards.

 

Baidu

NetArch

Tel: 010-56796212

Mobile: +86-15010096386

Email: zhanghechun@...

 

 

 

Cancelled Event: Akraino Technical Community Call (Weekly) - Thursday, 26 December 2019 #cal-cancelled

technical-discuss@lists.akraino.org Calendar <technical-discuss@...>
 

Cancelled: Akraino Technical Community Call (Weekly)

This event has been cancelled.

When:
Thursday, 26 December 2019
11:00am to 12:00pm
(UTC-05:00) America/New York

Where:
https://zoom.us/j/919148693

Organizer: technical-discuss@...

Description:

Akraino Technical Community Call: TSC updates to technical community and deeper dives into topics as applicable. Meeting content posted to Technical Community Wiki.
Meeting Lead: Kandan Kathirvel, Akraino TSC Chair


Akraino Edge Stack is inviting you to a scheduled Zoom meeting.
Join from PC, Mac, Linux, iOS or Android:
https://zoom.us/j/919148693
Or iPhone one-tap : US: +16699006833,,919148693# or +16465588656,,919148693#
Or Telephone: Dial(for higher quality, dial a number based on your current location):
US: +1 669 900 6833 or +1 646 558 8656 or +1 877 369 0926 (Toll Free) or +1 855 880 1246 (Toll Free)
Meeting ID: 919 148 693
International numbers available:
https://zoom.us/u/adnlim1pfM

Cancelled Event: Akraino Technical Community Call (Weekly) - Thursday, 19 December 2019 #cal-cancelled

technical-discuss@lists.akraino.org Calendar <technical-discuss@...>
 

Cancelled: Akraino Technical Community Call (Weekly)

This event has been cancelled.

When:
Thursday, 19 December 2019
11:00am to 12:00pm
(UTC-05:00) America/New York

Where:
https://zoom.us/j/919148693

Organizer: technical-discuss@...

Description:

Akraino Technical Community Call: TSC updates to technical community and deeper dives into topics as applicable. Meeting content posted to Technical Community Wiki.
Meeting Lead: Kandan Kathirvel, Akraino TSC Chair


Akraino Edge Stack is inviting you to a scheduled Zoom meeting.
Join from PC, Mac, Linux, iOS or Android:
https://zoom.us/j/919148693
Or iPhone one-tap : US: +16699006833,,919148693# or +16465588656,,919148693#
Or Telephone: Dial(for higher quality, dial a number based on your current location):
US: +1 669 900 6833 or +1 646 558 8656 or +1 877 369 0926 (Toll Free) or +1 855 880 1246 (Toll Free)
Meeting ID: 919 148 693
International numbers available:
https://zoom.us/u/adnlim1pfM

Upcoming Event: Akraino Technical Community Call (Weekly) - Thu, 12/12/2019 11:00am-12:00pm #cal-reminder

technical-discuss@lists.akraino.org Calendar <technical-discuss@...>
 

Reminder: Akraino Technical Community Call (Weekly)

When: Thursday, 12 December 2019, 11:00am to 12:00pm, (GMT-05:00) America/New York

Where:https://zoom.us/j/919148693

View Event

Organizer: technical-discuss@...

Description:

Akraino Technical Community Call: TSC updates to technical community and deeper dives into topics as applicable. Meeting content posted to Technical Community Wiki.
Meeting Lead: Kandan Kathirvel, Akraino TSC Chair


Akraino Edge Stack is inviting you to a scheduled Zoom meeting.
Join from PC, Mac, Linux, iOS or Android:
https://zoom.us/j/919148693
Or iPhone one-tap : US: +16699006833,,919148693# or +16465588656,,919148693#
Or Telephone: Dial(for higher quality, dial a number based on your current location):
US: +1 669 900 6833 or +1 646 558 8656 or +1 877 369 0926 (Toll Free) or +1 855 880 1246 (Toll Free)
Meeting ID: 919 148 693
International numbers available:
https://zoom.us/u/adnlim1pfM

Upcoming Event: Akraino Technical Community Call (Weekly) - Thu, 12/12/2019 11:00am-12:00pm #cal-reminder

technical-discuss@lists.akraino.org Calendar <technical-discuss@...>
 

Reminder: Akraino Technical Community Call (Weekly)

When: Thursday, 12 December 2019, 11:00am to 12:00pm, (GMT-05:00) America/New York

Where:https://zoom.us/j/919148693

View Event

Organizer: technical-discuss@...

Description:

Akraino Technical Community Call: TSC updates to technical community and deeper dives into topics as applicable. Meeting content posted to Technical Community Wiki.
Meeting Lead: Kandan Kathirvel, Akraino TSC Chair


Akraino Edge Stack is inviting you to a scheduled Zoom meeting.
Join from PC, Mac, Linux, iOS or Android:
https://zoom.us/j/919148693
Or iPhone one-tap : US: +16699006833,,919148693# or +16465588656,,919148693#
Or Telephone: Dial(for higher quality, dial a number based on your current location):
US: +1 669 900 6833 or +1 646 558 8656 or +1 877 369 0926 (Toll Free) or +1 855 880 1246 (Toll Free)
Meeting ID: 919 148 693
International numbers available:
https://zoom.us/u/adnlim1pfM

Re: [Akraino TSC] New project presentation in Akraino Technical Call today: IEC Type 5: SmartNIC for Integrated Edge Cloud (IEC)

Paul Carver
 

I agree with Andrew, and if you look at our REC blueprint documentation you’ll see that we’ve been careful to distinguish what between what we think will probably work vs what we’ve tested. We’ve welcomed the participation from several contributors who have been in the process of adding ARM support to the blueprint, but we don’t yet claim the blueprint supports ARM because the continuous deployment pipeline only tests on Open Edge hardware with Mellanox CX5 NICs. The exact hardware on which the CD pipeline tests run is shown in the second URL below. We also hope the blueprint will be deployable on Dell and HP servers, but our documentation doesn’t claim that these are part of the CD pipeline.

 

Anyone is welcome to use the REC blueprint on totally different hardware, and they can submit bug fixes if they want to, but we only claim what the CD pipeline tests. Given enough people and money we welcome additional hardware to the CD pipeline, but we won’t overextend what the blueprint claims has been tested. The purpose of the blueprint is to announce exactly what hardware and software combination(s) is(are) being tested on a continuous basis with every new code commit.

 

https://wiki.akraino.org/display/AK/REC+Installation+Guide

https://wiki.akraino.org/display/AK/Radio+Edge+Cloud+Validation+Lab

https://wiki.akraino.org/display/AK/Radio+Edge+Cloud+Release+2+Maturity+Review+Certification

 

 

From: technical-discuss@... <technical-discuss@...> On Behalf Of Andrew Wilkinson via Lists.Akraino.Org
Sent: Thursday, December 5, 2019 18:47
To: Tina Tsou <Tina.Tsou@...>; tnadeau@...
Cc: technical-discuss@...
Subject: Re: [Akraino Technical-Discuss] [Akraino TSC] New project presentation in Akraino Technical Call today: IEC Type 5: SmartNIC for Integrated Edge Cloud (IEC)

 

Hi Tom,

 

In answer to your point – sorry if it’s a bit long but it’s touching on a key aspect of Akraino so I think worth it.

 

>> That is going to add another dimension of complexity to the BPs that gets amplified with testing, etc...  Are we sure we want to include them

directly in the BPs or just in the CI/testing later?

 

I think it is a choice of each BP PTL (with their team) as to what HW they decide to validate in their BP and submit to the community for approval (as either Core, Mature or Incubation self-certified).

 

For example today in our BP (the NC Unicycle OVS-DPDK BP) we already validate using a defined NIC – that’s what’s proven and deployed in our validation lab and it is with that NIC in Dell 740XD servers that we are requesting for inclusion as self certified in R2. [I would expect the BP to work on a HP DL380 but we haven’t validated that in the CD lab thus it’s not included as a validated configuration in the R2 release]

 

We haven’t validated any other config in R2 but we could, for example, in R3 choose to also validate against this smart NIC in the same or different server as well as the HW configuration we used in R1 and R2.

 

 

 

If we want to submit both configurations we would need to submit evidence of success for either (a) two deployments in the form of two logs from two different CDs, one with the original NICs and one with the SmartNICs or (b) we could submit a single CD with machines running both types of NICs if our BP supported that.

 

Either way we are submitting a proven successfully deployed HW+SW stack for TSC approval.

 

If we did do this I’d argue it’s the same BP but just a different HW configuration of a POD deployed by that BP.

 

 

 

But this is actually getting to a more fundamental point – from the technical charter: “A Blueprint is a declarative configuration of an edge Cloud Stack that includes a combination of infrastructure hardware components, SW components ….”

 

This DECLARATIVE set of specific components is what is validated when a CD is successful – the success (or failure) of that is shown by the CD logs loaded to LF Nexus after each CD in a validation lab. This is a cornerstone of the TSC’s approval of every BP in a release. This is one of the reasons we’ve reviewed every CD log and been very ‘specific’ that a BP’s R2 release documentation should only include that which has been proven to successfully deploy. A project can include other aspirational targets and capabilities but only that which is validated in an Akraino validation lab should be included in the release documentation for that BP

 

Andrew

 

 

 

From: Tina Tsou <Tina.Tsou@...>
Sent: Thursday, December 5, 2019 14:40
To: tnadeau@...
Cc: Andrew Wilkinson <andrew.wilkinson@...>; technical-discuss@...
Subject: Re: [Akraino Technical-Discuss] [Akraino TSC] New project presentation in Akraino Technical Call today: IEC Type 5: SmartNIC for Integrated Edge Cloud (IEC)

 

Dear all,

 

Please refer to these sections in Akraino Technical Community Document.

 

 

3.3.2.3   Akraino Validation Projects

Multiple labs will be used to validate Akraino projects to ensure production quality of blueprint and/or feature project releases. The Community CI lab is owned by the Akraino community and LF. In addition a number of Edge Validation labs are owned by an Akraino community company, organization or participant.

Comprehensive validation of the blueprint within the community will include testing of the OS layer, the undercloud layer, the upper cloud layer, VNF layer and the application layer. Test results should be available to the Akraino Edge Stack community for review via automated push to the wiki.  Any defects identified should be logged in JIRA and assigned to the responsible party.  When defects are identified in upstream components, Akraino coordinators should be assigned defect ownership.  Akraino coordinators will work with upstream communities to resolve defects. For defects that do not involve upstream communities, impacted Protect Technical Leaders should be assigned defect ownership.

Akraino Validation Projects will also include testing of Akraino releases.

An automation framework should be used for test procedures and leverage existing test automation suites for upstream projects as required.  It is the responsibility of the blueprint submitter to ensure that the Edge Validation and Community CI labs can support comprehensive validation of the blueprint and cover all use case characteristics.  

The TSC subcommittees tasked with the setup and structuring of operating procedures for the validation labs shall work to define the licensing requirements for the external labs.

 

3.3.2.3.1   Feature project unit testing in Community CI lab

The Akraino Community CI labs are owned by the Akraino community and LF. Access is controlled by LF best practices.

TSC will propose a subcommittee to maintain and coordinate the Community CI lab.

The following would be conducted in the Community CI lab:

Unit testing of Feature projects or

Integration of Feature projects to a blueprint

Upstream projects together in the support of Akraino Blueprints.

 A full CD that works with the Akraino CI pipeline should be included in the validation project.

 

3.2.2.3.2   Blueprint and application testing in Akraino Edge Validation lab

Akraino Edge Validation labs are owned by an Akraino community company, organization or participant.

The Validation labs can be owned and operated by the supplier of the lab with limited access or no access to the hardware but results of the validation testing need to be shared to the community.

TSC will propose a subcommittee to maintain and coordinate the Validation labs.

Blueprint, application and VNF testing may be performed over a number of Validations labs concurrently in a coordinated manner as required.

The Validation labs should be able to connect to Akriano Edge Stack CI hosted by LF to pull in Akraino blueprints for the validation. Necessary Firewalls can be opened by the Akriano Community on request.

All Validation labs should be available most of the year for the community use and if the lab is not used for validation more than 3 consecutive months then it will be removed from the community list.

Hardware and Network configuration used within the Validation labs should be declared and information should be documented in the wiki

All the Validation labs addition, modifications or removable need to be approved by TSC

All historic results (minimum of 1 year) of blueprint validation, Applications and VNF testing should be maintained in the wiki.

 

3.2.2.3.2.1   Blueprint testing

The test plan and associated test cases to validate the blueprint will be published on the Akraino wiki and reviewed by blueprint stakeholders.  

The lab configuration should support functional, performance, security, and other test cases for the blueprint and cover the full stack for the blueprint. 

Any license or support beyond the Community supplied software should be funded, owned and operated by the Validation supplier

Open source test tools and vendor tools with appropriate configurations should drive test traffic profiles that mimic in-scope use cases.  Akraino coordinators will engage upstream open source communities to get access to upstream community labs for the Akraino blueprint test team.  The submitter is responsible to establish access to necessary vendor labs.

 

3.2.2.3.2.2   Application and VNF testing

Akraino blueprint releases ensure that applications and virtual network functions (VNFs) can on-board and operate effectively on the Akraino solution. Validation labs can be further used for the validation of Edge applications and VNFs.

Application and VNF testing may take a number of forms including performance, scalability, security and usability, resilience etc.

Submission of results to the Akriano community is optional in case of commercially sensitive applications.

 

 

Thank you,

Tina ^ ^

 

On Dec 5, 2019, at 2:24 PM, Thomas Nadeau via Lists.Akraino.Org <tnadeau=redhat.com@...> wrote:



 

 

On Thu, Dec 5, 2019 at 1:31 PM Andrew Wilkinson via Lists.Akraino.Org <andrew.wilkinson=ericsson.com@...> wrote:

Hi Jim,

I also feel it would be more appropriate to consider introducing a Feature Project to enable smart NIC support in Akraino BPs in general but (and) then I also think we do need to introduce specific NIC integrations in to specific BPs (both plural). Akraino after all is fundamentally about blueprints that are actual definitive integrated and deployment validated HW+SW stacks (i.e. deployment proven HW+SW integration projects).

 

That is going to add another dimension of complexity to the BPs that gets amplified with testing, etc...  Are we sure we want to include them

directly in the BPs or just in the CI/testing later?

 

--Tom

 

 

Why do I think both are needed? - The reason I also include support for specific NICs in specific BPs is because an Akriano Blueprint is by definition a project that validates the integration of HW and SW and validation means proving an actual configuration of HW & SW works and does what is claimed (the CD logs we use judge successful BP deployments are the ultimate proof of successful deployment of a given configuration).

Of course there can be (1) multiple individual BP POD validations each with a given single homogenous HW configuration or (2) a single validation of multiple HW variants in the same POD (running the same SW stack) but both scenarios requires an actual physical deployment to prove it works.

Andrew



-----Original Message-----
From: tsc@... <tsc@...> On Behalf Of St Leger, Jim via Lists.Akraino.Org
Sent: Thursday, December 5, 2019 10:02
To: technical-discuss@...
Cc: tsc@...
Subject: Re: [Akraino TSC] New project presentation in Akraino Technical Call today: IEC Type 5: SmartNIC for Integrated Edge Cloud (IEC)

I missed this call today, but I did just listen to the recording (thanks Tapio for posting that.) https://protect2.fireeye.com/v1/url?k=2cc25f38-704bf0f1-2cc21fa3-0cc47ad93e1c-c86774c20018ec3d&q=1&e=5585f8f6-7eee-4000-bd73-368b117a3e68&u=https%3A%2F%2Fwiki.akraino.org%2Fdownload%2Fattachments%2F4456465%2FGMT20191205-140454_Akraino-Te_1280x778.mp4%3Fversion%3D1%26modificationDate%3D1575559822096%26api%3Dv2

My question to the team here is whether the proposal is to build a blueprint that can be applied to ANY SmartNIC, or whether the proposal is to build a blueprint that is specifically tied to and coupled to Broadcom's Stingray SmartNIC card.  The slides and discussion made it seem look like it would be tied to Stingray.

I think broad market SmartNIC enabling would make for a very interesting blueprint. But if we are narrowly doing this for one SmartNIC then does it really belong in Akraino as an open source blueprint? It would then feel more like a vendor-specific POC. I don't believe that's the charter of Akraino nor LF Edge.

I also heard discussion of blueprint, feature project, and validation project. The slides say "blueprint." Is that what is being proposed or not?
Andrew poked at this question towards the end of the call (Thanks Andrew.)

Thoughts?

Jim


-----Original Message-----
From: technical-discuss@... <technical-discuss@...> On Behalf Of Tapio Tallgren
Sent: Thursday, December 5, 2019 1:17 AM
To: technical-discuss@...
Cc: tsc@...
Subject: [Akraino Technical-Discuss] New project presentation in Akraino Technical Call today: IEC Type 5: SmartNIC for Integrated Edge Cloud (IEC)

Hi all,

Today, we have a new project presentation in Akraino Technical Call today! The link is

https://protect2.fireeye.com/v1/url?k=2628006f-7aa1afa6-262840f4-0cc47ad93e1c-38744566f21c32df&q=1&e=5585f8f6-7eee-4000-bd73-368b117a3e68&u=https%3A%2F%2Fwiki.akraino.org%2Fdisplay%2FAK%2FIEC%2BType%2B5%253A%2BSmartNIC%2Bfor%2BIntegrated%2BEdge%2BCloud%2B%2528IEC%2529%2BBlueprint%2BFamily

The purpose is to allow the technical community to have a discussion of the project.

Please notice the new time: 6 PST so before the TSC call.

The presentation will also be recorded.







IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

Re: [Akraino TSC] New project presentation in Akraino Technical Call today: IEC Type 5: SmartNIC for Integrated Edge Cloud (IEC)

Andrew Wilkinson
 

Hi Tom,

 

In answer to your point – sorry if it’s a bit long but it’s touching on a key aspect of Akraino so I think worth it.

 

>> That is going to add another dimension of complexity to the BPs that gets amplified with testing, etc...  Are we sure we want to include them

directly in the BPs or just in the CI/testing later?

 

I think it is a choice of each BP PTL (with their team) as to what HW they decide to validate in their BP and submit to the community for approval (as either Core, Mature or Incubation self-certified).

 

For example today in our BP (the NC Unicycle OVS-DPDK BP) we already validate using a defined NIC – that’s what’s proven and deployed in our validation lab and it is with that NIC in Dell 740XD servers that we are requesting for inclusion as self certified in R2. [I would expect the BP to work on a HP DL380 but we haven’t validated that in the CD lab thus it’s not included as a validated configuration in the R2 release]

 

We haven’t validated any other config in R2 but we could, for example, in R3 choose to also validate against this smart NIC in the same or different server as well as the HW configuration we used in R1 and R2.

 

 

 

If we want to submit both configurations we would need to submit evidence of success for either (a) two deployments in the form of two logs from two different CDs, one with the original NICs and one with the SmartNICs or (b) we could submit a single CD with machines running both types of NICs if our BP supported that.

 

Either way we are submitting a proven successfully deployed HW+SW stack for TSC approval.

 

If we did do this I’d argue it’s the same BP but just a different HW configuration of a POD deployed by that BP.

 

 

 

But this is actually getting to a more fundamental point – from the technical charter: “A Blueprint is a declarative configuration of an edge Cloud Stack that includes a combination of infrastructure hardware components, SW components ….”

 

This DECLARATIVE set of specific components is what is validated when a CD is successful – the success (or failure) of that is shown by the CD logs loaded to LF Nexus after each CD in a validation lab. This is a cornerstone of the TSC’s approval of every BP in a release. This is one of the reasons we’ve reviewed every CD log and been very ‘specific’ that a BP’s R2 release documentation should only include that which has been proven to successfully deploy. A project can include other aspirational targets and capabilities but only that which is validated in an Akraino validation lab should be included in the release documentation for that BP

 

Andrew

 

 

 

From: Tina Tsou <Tina.Tsou@...>
Sent: Thursday, December 5, 2019 14:40
To: tnadeau@...
Cc: Andrew Wilkinson <andrew.wilkinson@...>; technical-discuss@...
Subject: Re: [Akraino Technical-Discuss] [Akraino TSC] New project presentation in Akraino Technical Call today: IEC Type 5: SmartNIC for Integrated Edge Cloud (IEC)

 

Dear all,

 

Please refer to these sections in Akraino Technical Community Document.

 

 

3.3.2.3   Akraino Validation Projects

Multiple labs will be used to validate Akraino projects to ensure production quality of blueprint and/or feature project releases. The Community CI lab is owned by the Akraino community and LF. In addition a number of Edge Validation labs are owned by an Akraino community company, organization or participant.

Comprehensive validation of the blueprint within the community will include testing of the OS layer, the undercloud layer, the upper cloud layer, VNF layer and the application layer. Test results should be available to the Akraino Edge Stack community for review via automated push to the wiki.  Any defects identified should be logged in JIRA and assigned to the responsible party.  When defects are identified in upstream components, Akraino coordinators should be assigned defect ownership.  Akraino coordinators will work with upstream communities to resolve defects. For defects that do not involve upstream communities, impacted Protect Technical Leaders should be assigned defect ownership.

Akraino Validation Projects will also include testing of Akraino releases.

An automation framework should be used for test procedures and leverage existing test automation suites for upstream projects as required.  It is the responsibility of the blueprint submitter to ensure that the Edge Validation and Community CI labs can support comprehensive validation of the blueprint and cover all use case characteristics.  

The TSC subcommittees tasked with the setup and structuring of operating procedures for the validation labs shall work to define the licensing requirements for the external labs.

 

3.3.2.3.1   Feature project unit testing in Community CI lab

The Akraino Community CI labs are owned by the Akraino community and LF. Access is controlled by LF best practices.

TSC will propose a subcommittee to maintain and coordinate the Community CI lab.

The following would be conducted in the Community CI lab:

Unit testing of Feature projects or

Integration of Feature projects to a blueprint

Upstream projects together in the support of Akraino Blueprints.

 A full CD that works with the Akraino CI pipeline should be included in the validation project.

 

3.2.2.3.2   Blueprint and application testing in Akraino Edge Validation lab

Akraino Edge Validation labs are owned by an Akraino community company, organization or participant.

The Validation labs can be owned and operated by the supplier of the lab with limited access or no access to the hardware but results of the validation testing need to be shared to the community.

TSC will propose a subcommittee to maintain and coordinate the Validation labs.

Blueprint, application and VNF testing may be performed over a number of Validations labs concurrently in a coordinated manner as required.

The Validation labs should be able to connect to Akriano Edge Stack CI hosted by LF to pull in Akraino blueprints for the validation. Necessary Firewalls can be opened by the Akriano Community on request.

All Validation labs should be available most of the year for the community use and if the lab is not used for validation more than 3 consecutive months then it will be removed from the community list.

Hardware and Network configuration used within the Validation labs should be declared and information should be documented in the wiki

All the Validation labs addition, modifications or removable need to be approved by TSC

All historic results (minimum of 1 year) of blueprint validation, Applications and VNF testing should be maintained in the wiki.

 

3.2.2.3.2.1   Blueprint testing

The test plan and associated test cases to validate the blueprint will be published on the Akraino wiki and reviewed by blueprint stakeholders.  

The lab configuration should support functional, performance, security, and other test cases for the blueprint and cover the full stack for the blueprint. 

Any license or support beyond the Community supplied software should be funded, owned and operated by the Validation supplier

Open source test tools and vendor tools with appropriate configurations should drive test traffic profiles that mimic in-scope use cases.  Akraino coordinators will engage upstream open source communities to get access to upstream community labs for the Akraino blueprint test team.  The submitter is responsible to establish access to necessary vendor labs.

 

3.2.2.3.2.2   Application and VNF testing

Akraino blueprint releases ensure that applications and virtual network functions (VNFs) can on-board and operate effectively on the Akraino solution. Validation labs can be further used for the validation of Edge applications and VNFs.

Application and VNF testing may take a number of forms including performance, scalability, security and usability, resilience etc.

Submission of results to the Akriano community is optional in case of commercially sensitive applications.

 

 

Thank you,

Tina ^ ^



On Dec 5, 2019, at 2:24 PM, Thomas Nadeau via Lists.Akraino.Org <tnadeau=redhat.com@...> wrote:



 

 

On Thu, Dec 5, 2019 at 1:31 PM Andrew Wilkinson via Lists.Akraino.Org <andrew.wilkinson=ericsson.com@...> wrote:

Hi Jim,

I also feel it would be more appropriate to consider introducing a Feature Project to enable smart NIC support in Akraino BPs in general but (and) then I also think we do need to introduce specific NIC integrations in to specific BPs (both plural). Akraino after all is fundamentally about blueprints that are actual definitive integrated and deployment validated HW+SW stacks (i.e. deployment proven HW+SW integration projects).

 

That is going to add another dimension of complexity to the BPs that gets amplified with testing, etc...  Are we sure we want to include them

directly in the BPs or just in the CI/testing later?

 

--Tom

 

 

Why do I think both are needed? - The reason I also include support for specific NICs in specific BPs is because an Akriano Blueprint is by definition a project that validates the integration of HW and SW and validation means proving an actual configuration of HW & SW works and does what is claimed (the CD logs we use judge successful BP deployments are the ultimate proof of successful deployment of a given configuration).

Of course there can be (1) multiple individual BP POD validations each with a given single homogenous HW configuration or (2) a single validation of multiple HW variants in the same POD (running the same SW stack) but both scenarios requires an actual physical deployment to prove it works.

Andrew



-----Original Message-----
From: tsc@... <tsc@...> On Behalf Of St Leger, Jim via Lists.Akraino.Org
Sent: Thursday, December 5, 2019 10:02
To: technical-discuss@...
Cc: tsc@...
Subject: Re: [Akraino TSC] New project presentation in Akraino Technical Call today: IEC Type 5: SmartNIC for Integrated Edge Cloud (IEC)

I missed this call today, but I did just listen to the recording (thanks Tapio for posting that.) https://protect2.fireeye.com/v1/url?k=2cc25f38-704bf0f1-2cc21fa3-0cc47ad93e1c-c86774c20018ec3d&q=1&e=5585f8f6-7eee-4000-bd73-368b117a3e68&u=https%3A%2F%2Fwiki.akraino.org%2Fdownload%2Fattachments%2F4456465%2FGMT20191205-140454_Akraino-Te_1280x778.mp4%3Fversion%3D1%26modificationDate%3D1575559822096%26api%3Dv2

My question to the team here is whether the proposal is to build a blueprint that can be applied to ANY SmartNIC, or whether the proposal is to build a blueprint that is specifically tied to and coupled to Broadcom's Stingray SmartNIC card.  The slides and discussion made it seem look like it would be tied to Stingray.

I think broad market SmartNIC enabling would make for a very interesting blueprint. But if we are narrowly doing this for one SmartNIC then does it really belong in Akraino as an open source blueprint? It would then feel more like a vendor-specific POC. I don't believe that's the charter of Akraino nor LF Edge.

I also heard discussion of blueprint, feature project, and validation project. The slides say "blueprint." Is that what is being proposed or not?
Andrew poked at this question towards the end of the call (Thanks Andrew.)

Thoughts?

Jim


-----Original Message-----
From: technical-discuss@... <technical-discuss@...> On Behalf Of Tapio Tallgren
Sent: Thursday, December 5, 2019 1:17 AM
To: technical-discuss@...
Cc: tsc@...
Subject: [Akraino Technical-Discuss] New project presentation in Akraino Technical Call today: IEC Type 5: SmartNIC for Integrated Edge Cloud (IEC)

Hi all,

Today, we have a new project presentation in Akraino Technical Call today! The link is

https://protect2.fireeye.com/v1/url?k=2628006f-7aa1afa6-262840f4-0cc47ad93e1c-38744566f21c32df&q=1&e=5585f8f6-7eee-4000-bd73-368b117a3e68&u=https%3A%2F%2Fwiki.akraino.org%2Fdisplay%2FAK%2FIEC%2BType%2B5%253A%2BSmartNIC%2Bfor%2BIntegrated%2BEdge%2BCloud%2B%2528IEC%2529%2BBlueprint%2BFamily

The purpose is to allow the technical community to have a discussion of the project.

Please notice the new time: 6 PST so before the TSC call.

The presentation will also be recorded.








IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

Re: [Akraino TSC] New project presentation in Akraino Technical Call today: IEC Type 5: SmartNIC for Integrated Edge Cloud (IEC)

Tina Tsou
 

Dear all,

Please refer to these sections in Akraino Technical Community Document.


3.3.2.3   Akraino Validation Projects
Multiple labs will be used to validate Akraino projects to ensure production quality of blueprint and/or feature project releases. The Community CI lab is owned by the Akraino community and LF. In addition a number of Edge Validation labs are owned by an Akraino community company, organization or participant.
Comprehensive validation of the blueprint within the community will include testing of the OS layer, the undercloud layer, the upper cloud layer, VNF layer and the application layer. Test results should be available to the Akraino Edge Stack community for review via automated push to the wiki.  Any defects identified should be logged in JIRA and assigned to the responsible party.  When defects are identified in upstream components, Akraino coordinators should be assigned defect ownership.  Akraino coordinators will work with upstream communities to resolve defects. For defects that do not involve upstream communities, impacted Protect Technical Leaders should be assigned defect ownership.
Akraino Validation Projects will also include testing of Akraino releases.
An automation framework should be used for test procedures and leverage existing test automation suites for upstream projects as required.  It is the responsibility of the blueprint submitter to ensure that the Edge Validation and Community CI labs can support comprehensive validation of the blueprint and cover all use case characteristics.  
The TSC subcommittees tasked with the setup and structuring of operating procedures for the validation labs shall work to define the licensing requirements for the external labs.

3.3.2.3.1   Feature project unit testing in Community CI lab
The Akraino Community CI labs are owned by the Akraino community and LF. Access is controlled by LF best practices.
TSC will propose a subcommittee to maintain and coordinate the Community CI lab.
The following would be conducted in the Community CI lab:
Unit testing of Feature projects or
Integration of Feature projects to a blueprint
Upstream projects together in the support of Akraino Blueprints.
 A full CD that works with the Akraino CI pipeline should be included in the validation project.

3.2.2.3.2   Blueprint and application testing in Akraino Edge Validation lab
Akraino Edge Validation labs are owned by an Akraino community company, organization or participant.
The Validation labs can be owned and operated by the supplier of the lab with limited access or no access to the hardware but results of the validation testing need to be shared to the community.
TSC will propose a subcommittee to maintain and coordinate the Validation labs.
Blueprint, application and VNF testing may be performed over a number of Validations labs concurrently in a coordinated manner as required.
The Validation labs should be able to connect to Akriano Edge Stack CI hosted by LF to pull in Akraino blueprints for the validation. Necessary Firewalls can be opened by the Akriano Community on request.
All Validation labs should be available most of the year for the community use and if the lab is not used for validation more than 3 consecutive months then it will be removed from the community list.
Hardware and Network configuration used within the Validation labs should be declared and information should be documented in the wiki
All the Validation labs addition, modifications or removable need to be approved by TSC
All historic results (minimum of 1 year) of blueprint validation, Applications and VNF testing should be maintained in the wiki.

3.2.2.3.2.1   Blueprint testing
The test plan and associated test cases to validate the blueprint will be published on the Akraino wiki and reviewed by blueprint stakeholders.  
The lab configuration should support functional, performance, security, and other test cases for the blueprint and cover the full stack for the blueprint. 
Any license or support beyond the Community supplied software should be funded, owned and operated by the Validation supplier
Open source test tools and vendor tools with appropriate configurations should drive test traffic profiles that mimic in-scope use cases.  Akraino coordinators will engage upstream open source communities to get access to upstream community labs for the Akraino blueprint test team.  The submitter is responsible to establish access to necessary vendor labs.

3.2.2.3.2.2   Application and VNF testing
Akraino blueprint releases ensure that applications and virtual network functions (VNFs) can on-board and operate effectively on the Akraino solution. Validation labs can be further used for the validation of Edge applications and VNFs.
Application and VNF testing may take a number of forms including performance, scalability, security and usability, resilience etc.
Submission of results to the Akriano community is optional in case of commercially sensitive applications.


Thank you,
Tina ^ ^

On Dec 5, 2019, at 2:24 PM, Thomas Nadeau via Lists.Akraino.Org <tnadeau=redhat.com@...> wrote:




On Thu, Dec 5, 2019 at 1:31 PM Andrew Wilkinson via Lists.Akraino.Org <andrew.wilkinson=ericsson.com@...> wrote:
Hi Jim,

I also feel it would be more appropriate to consider introducing a Feature Project to enable smart NIC support in Akraino BPs in general but (and) then I also think we do need to introduce specific NIC integrations in to specific BPs (both plural). Akraino after all is fundamentally about blueprints that are actual definitive integrated and deployment validated HW+SW stacks (i.e. deployment proven HW+SW integration projects).

That is going to add another dimension of complexity to the BPs that gets amplified with testing, etc...  Are we sure we want to include them
directly in the BPs or just in the CI/testing later?

--Tom

 
Why do I think both are needed? - The reason I also include support for specific NICs in specific BPs is because an Akriano Blueprint is by definition a project that validates the integration of HW and SW and validation means proving an actual configuration of HW & SW works and does what is claimed (the CD logs we use judge successful BP deployments are the ultimate proof of successful deployment of a given configuration).

Of course there can be (1) multiple individual BP POD validations each with a given single homogenous HW configuration or (2) a single validation of multiple HW variants in the same POD (running the same SW stack) but both scenarios requires an actual physical deployment to prove it works.

Andrew



-----Original Message-----
From: tsc@... <tsc@...> On Behalf Of St Leger, Jim via Lists.Akraino.Org
Sent: Thursday, December 5, 2019 10:02
To: technical-discuss@...
Cc: tsc@...
Subject: Re: [Akraino TSC] New project presentation in Akraino Technical Call today: IEC Type 5: SmartNIC for Integrated Edge Cloud (IEC)

I missed this call today, but I did just listen to the recording (thanks Tapio for posting that.) https://protect2.fireeye.com/v1/url?k=2cc25f38-704bf0f1-2cc21fa3-0cc47ad93e1c-c86774c20018ec3d&q=1&e=5585f8f6-7eee-4000-bd73-368b117a3e68&u=https%3A%2F%2Fwiki.akraino.org%2Fdownload%2Fattachments%2F4456465%2FGMT20191205-140454_Akraino-Te_1280x778.mp4%3Fversion%3D1%26modificationDate%3D1575559822096%26api%3Dv2

My question to the team here is whether the proposal is to build a blueprint that can be applied to ANY SmartNIC, or whether the proposal is to build a blueprint that is specifically tied to and coupled to Broadcom's Stingray SmartNIC card.  The slides and discussion made it seem look like it would be tied to Stingray.

I think broad market SmartNIC enabling would make for a very interesting blueprint. But if we are narrowly doing this for one SmartNIC then does it really belong in Akraino as an open source blueprint? It would then feel more like a vendor-specific POC. I don't believe that's the charter of Akraino nor LF Edge.

I also heard discussion of blueprint, feature project, and validation project. The slides say "blueprint." Is that what is being proposed or not?
Andrew poked at this question towards the end of the call (Thanks Andrew.)

Thoughts?

Jim


-----Original Message-----
From: technical-discuss@... <technical-discuss@...> On Behalf Of Tapio Tallgren
Sent: Thursday, December 5, 2019 1:17 AM
To: technical-discuss@...
Cc: tsc@...
Subject: [Akraino Technical-Discuss] New project presentation in Akraino Technical Call today: IEC Type 5: SmartNIC for Integrated Edge Cloud (IEC)

Hi all,

Today, we have a new project presentation in Akraino Technical Call today! The link is

https://protect2.fireeye.com/v1/url?k=2628006f-7aa1afa6-262840f4-0cc47ad93e1c-38744566f21c32df&q=1&e=5585f8f6-7eee-4000-bd73-368b117a3e68&u=https%3A%2F%2Fwiki.akraino.org%2Fdisplay%2FAK%2FIEC%2BType%2B5%253A%2BSmartNIC%2Bfor%2BIntegrated%2BEdge%2BCloud%2B%2528IEC%2529%2BBlueprint%2BFamily

The purpose is to allow the technical community to have a discussion of the project.

Please notice the new time: 6 PST so before the TSC call.

The presentation will also be recorded.









IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

Re: [Akraino TSC] New project presentation in Akraino Technical Call today: IEC Type 5: SmartNIC for Integrated Edge Cloud (IEC)

Thomas Nadeau
 



On Thu, Dec 5, 2019 at 1:31 PM Andrew Wilkinson via Lists.Akraino.Org <andrew.wilkinson=ericsson.com@...> wrote:
Hi Jim,

I also feel it would be more appropriate to consider introducing a Feature Project to enable smart NIC support in Akraino BPs in general but (and) then I also think we do need to introduce specific NIC integrations in to specific BPs (both plural). Akraino after all is fundamentally about blueprints that are actual definitive integrated and deployment validated HW+SW stacks (i.e. deployment proven HW+SW integration projects).

That is going to add another dimension of complexity to the BPs that gets amplified with testing, etc...  Are we sure we want to include them
directly in the BPs or just in the CI/testing later?

--Tom

 
Why do I think both are needed? - The reason I also include support for specific NICs in specific BPs is because an Akriano Blueprint is by definition a project that validates the integration of HW and SW and validation means proving an actual configuration of HW & SW works and does what is claimed (the CD logs we use judge successful BP deployments are the ultimate proof of successful deployment of a given configuration).

Of course there can be (1) multiple individual BP POD validations each with a given single homogenous HW configuration or (2) a single validation of multiple HW variants in the same POD (running the same SW stack) but both scenarios requires an actual physical deployment to prove it works.

Andrew



-----Original Message-----
From: tsc@... <tsc@...> On Behalf Of St Leger, Jim via Lists.Akraino.Org
Sent: Thursday, December 5, 2019 10:02
To: technical-discuss@...
Cc: tsc@...
Subject: Re: [Akraino TSC] New project presentation in Akraino Technical Call today: IEC Type 5: SmartNIC for Integrated Edge Cloud (IEC)

I missed this call today, but I did just listen to the recording (thanks Tapio for posting that.) https://protect2.fireeye.com/v1/url?k=2cc25f38-704bf0f1-2cc21fa3-0cc47ad93e1c-c86774c20018ec3d&q=1&e=5585f8f6-7eee-4000-bd73-368b117a3e68&u=https%3A%2F%2Fwiki.akraino.org%2Fdownload%2Fattachments%2F4456465%2FGMT20191205-140454_Akraino-Te_1280x778.mp4%3Fversion%3D1%26modificationDate%3D1575559822096%26api%3Dv2

My question to the team here is whether the proposal is to build a blueprint that can be applied to ANY SmartNIC, or whether the proposal is to build a blueprint that is specifically tied to and coupled to Broadcom's Stingray SmartNIC card.  The slides and discussion made it seem look like it would be tied to Stingray.

I think broad market SmartNIC enabling would make for a very interesting blueprint. But if we are narrowly doing this for one SmartNIC then does it really belong in Akraino as an open source blueprint? It would then feel more like a vendor-specific POC. I don't believe that's the charter of Akraino nor LF Edge.

I also heard discussion of blueprint, feature project, and validation project. The slides say "blueprint." Is that what is being proposed or not?
Andrew poked at this question towards the end of the call (Thanks Andrew.)

Thoughts?

Jim


-----Original Message-----
From: technical-discuss@... <technical-discuss@...> On Behalf Of Tapio Tallgren
Sent: Thursday, December 5, 2019 1:17 AM
To: technical-discuss@...
Cc: tsc@...
Subject: [Akraino Technical-Discuss] New project presentation in Akraino Technical Call today: IEC Type 5: SmartNIC for Integrated Edge Cloud (IEC)

Hi all,

Today, we have a new project presentation in Akraino Technical Call today! The link is

https://protect2.fireeye.com/v1/url?k=2628006f-7aa1afa6-262840f4-0cc47ad93e1c-38744566f21c32df&q=1&e=5585f8f6-7eee-4000-bd73-368b117a3e68&u=https%3A%2F%2Fwiki.akraino.org%2Fdisplay%2FAK%2FIEC%2BType%2B5%253A%2BSmartNIC%2Bfor%2BIntegrated%2BEdge%2BCloud%2B%2528IEC%2529%2BBlueprint%2BFamily

The purpose is to allow the technical community to have a discussion of the project.

Please notice the new time: 6 PST so before the TSC call.

The presentation will also be recorded.









Re: [Akraino TSC] New project presentation in Akraino Technical Call today: IEC Type 5: SmartNIC for Integrated Edge Cloud (IEC)

St Leger, Jim
 

Tom:

That’s a great point. We need to consider our long term position. As we grow and succeed how much platform, blueprint, feature project, etc. proliferation will we have? And do we have and can we afford (budget, people, etc.) the resources to scale to that level?

All great points we should consider.

Jim

 

 

From: Thomas Nadeau <tnadeau@...>
Sent: Thursday, December 5, 2019 3:10 PM
To: andrew.wilkinson@...
Cc: St Leger, Jim <jim.st.leger@...>; technical-discuss@...
Subject: Re: [Akraino Technical-Discuss] [Akraino TSC] New project presentation in Akraino Technical Call today: IEC Type 5: SmartNIC for Integrated Edge Cloud (IEC)

 

 

 

On Thu, Dec 5, 2019 at 1:31 PM Andrew Wilkinson via Lists.Akraino.Org <andrew.wilkinson=ericsson.com@...> wrote:

Hi Jim,

I also feel it would be more appropriate to consider introducing a Feature Project to enable smart NIC support in Akraino BPs in general but (and) then I also think we do need to introduce specific NIC integrations in to specific BPs (both plural). Akraino after all is fundamentally about blueprints that are actual definitive integrated and deployment validated HW+SW stacks (i.e. deployment proven HW+SW integration projects).

 

That is going to add another dimension of complexity to the BPs that gets amplified with testing, etc...  Are we sure we want to include them

directly in the BPs or just in the CI/testing later?

 

--Tom

 

 

Why do I think both are needed? - The reason I also include support for specific NICs in specific BPs is because an Akriano Blueprint is by definition a project that validates the integration of HW and SW and validation means proving an actual configuration of HW & SW works and does what is claimed (the CD logs we use judge successful BP deployments are the ultimate proof of successful deployment of a given configuration).

Of course there can be (1) multiple individual BP POD validations each with a given single homogenous HW configuration or (2) a single validation of multiple HW variants in the same POD (running the same SW stack) but both scenarios requires an actual physical deployment to prove it works.

Andrew



-----Original Message-----
From: tsc@... <tsc@...> On Behalf Of St Leger, Jim via Lists.Akraino.Org
Sent: Thursday, December 5, 2019 10:02
To: technical-discuss@...
Cc: tsc@...
Subject: Re: [Akraino TSC] New project presentation in Akraino Technical Call today: IEC Type 5: SmartNIC for Integrated Edge Cloud (IEC)

I missed this call today, but I did just listen to the recording (thanks Tapio for posting that.) https://protect2.fireeye.com/v1/url?k=2cc25f38-704bf0f1-2cc21fa3-0cc47ad93e1c-c86774c20018ec3d&q=1&e=5585f8f6-7eee-4000-bd73-368b117a3e68&u=https%3A%2F%2Fwiki.akraino.org%2Fdownload%2Fattachments%2F4456465%2FGMT20191205-140454_Akraino-Te_1280x778.mp4%3Fversion%3D1%26modificationDate%3D1575559822096%26api%3Dv2

My question to the team here is whether the proposal is to build a blueprint that can be applied to ANY SmartNIC, or whether the proposal is to build a blueprint that is specifically tied to and coupled to Broadcom's Stingray SmartNIC card.  The slides and discussion made it seem look like it would be tied to Stingray.

I think broad market SmartNIC enabling would make for a very interesting blueprint. But if we are narrowly doing this for one SmartNIC then does it really belong in Akraino as an open source blueprint? It would then feel more like a vendor-specific POC. I don't believe that's the charter of Akraino nor LF Edge.

I also heard discussion of blueprint, feature project, and validation project. The slides say "blueprint." Is that what is being proposed or not?
Andrew poked at this question towards the end of the call (Thanks Andrew.)

Thoughts?

Jim


-----Original Message-----
From: technical-discuss@... <technical-discuss@...> On Behalf Of Tapio Tallgren
Sent: Thursday, December 5, 2019 1:17 AM
To: technical-discuss@...
Cc: tsc@...
Subject: [Akraino Technical-Discuss] New project presentation in Akraino Technical Call today: IEC Type 5: SmartNIC for Integrated Edge Cloud (IEC)

Hi all,

Today, we have a new project presentation in Akraino Technical Call today! The link is

https://protect2.fireeye.com/v1/url?k=2628006f-7aa1afa6-262840f4-0cc47ad93e1c-38744566f21c32df&q=1&e=5585f8f6-7eee-4000-bd73-368b117a3e68&u=https%3A%2F%2Fwiki.akraino.org%2Fdisplay%2FAK%2FIEC%2BType%2B5%253A%2BSmartNIC%2Bfor%2BIntegrated%2BEdge%2BCloud%2B%2528IEC%2529%2BBlueprint%2BFamily

The purpose is to allow the technical community to have a discussion of the project.

Please notice the new time: 6 PST so before the TSC call.

The presentation will also be recorded.