Akraino Community Call: KubeEdge Edge Service Blueprint Family, Type 1: ML Inference Offloading && Public Cloud Edge Interface (PCEI) Blueprint Family proposal
Thursday, 26 March 2020
6:00am to 7:00am
(UTC-07:00) America/Los Angeles
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
New project proposal:
KubeEdge Edge Service Blueprint Family, Type 1: ML Inference Offloading (https://wiki.akraino.org/display/AK/KubeEdge+Edge+Service+Blueprint)
The Public Cloud Edge Interface (PCEI) Blueprint provides Open APIs between Telcos and public cloud edge compute platforms such as Google Cloud Platform (GCP) Anthos, AliCloud Edge Node Service (ENS), AWS Wavelength, Microsoft Azure, Tencent ECM, to name a few. Open API coverage includes edge capability exposure, edge orchestration and management, Edge monitoring (KPIs), and more.
The partnership announcement between AWS and Verizon/KDDI/SKTelecom/Vodafone during last November's AWS re'Invent signified the official entrance of Hyperscalers into the MEC domain. Over the last 12 months, AT&T has announced partnerships with the big 3 Hyperscalers (AWS, Microsoft Azure and Google Cloud). In Asia, similar partnerships have formed between China Mobile and Tencent/Alibaba. It seems that after years of exploration, the MEC domain sees a viable business model where Hyperscalers bring in applications and end users, while the mobile network operators leverage their edge capabilities and locations.
Telcos and Hyperscalers are powerful in their respective domains. How would their partnerships work when they meet at the edge ? What would be the technical collaboration interfaces? Within each country usually there are M operators with overlapping coverages and N Hyperscalers serving the same areas. With this M to N mesh relationship, would it make sense to have common interfaces ? Hyperscalers are big on APIs – how would Telco network edge capabilities be exposed as APIs? There are many questions. However there are no ready made answers.
Needless to say, business relationships of all MEC players is equally important in this domain. Telcos and Hyperscalers both carry their own eco-systems. How these eco-systems would collaborate poses another challenge.
This blueprint project family intends to help find these answers. The project will showcase collaboration via case studies. Meanwhile, broader discussions will be held with telcos and Hyperscalers during the project phase. With the massive deployment of 5G in coming years, MEC is not only a location play, but also a network capability play. The game for Telco Edge starts to get interesting.