- Edge-computing - lists.opendev.org

CFP Deadline Today - OpenStack Summit Vancouver
by Claire Massey 08 Feb '18

08 Feb '18

Hi everyone, Final reminder - the Vancouver Summit <https://www.openstack.org/summit/vancouver-2018/> CFP closes TODAY at 11:59pm PST (February 9 at 6:59am UTC). Please consider submitting a talk to the *Edge Computing* track and invite your colleagues from other open source communities to come speak and collaborate. List of tracks: • Container infrastructure • Edge computing • CI/CD • HPC/GPU/AI • Open source community • OpenStack private, public and hybrid cloud View topic ideas for each track HERE <https://www.openstack.org/summit/vancouver-2018/summit-categories/>. Please submit your proposals <https://www.openstack.org/summit/vancouver-2018/call-for-presentations/> before the deadline today. Thanks! Claire

1 0

2018 Work Sessions for Attemting to drive Edge Computing towards Abstractions
by prakash RAMCHANDRAN 06 Feb '18

06 Feb '18

Hi all, First returning to Edge after few months and like to understand what I saw was discussed in this forum till now, from OpenDev at SF last year till date: 1. General idea of Special VM at edge as cloudlet by Prof Satya of CMU with his App centric approach and more geared towards computing 1 hop from device, clearly the best reserach to date for Edge cloud/computing. 2.use cases - edge could infra, single vs multi-operator, capacity, alarms/monitor, unified dashbaord, PM, FM, VM migration, Discovery, Registry, VM Overlay/Sythesys, VM Residual3. LTE based edge with RRH, ENB, Front end micro DC for Mobile apps.(like CMU /Nokia labs)4. Classifiation of Infra based on sizing of requirments at edge by compute/HPC, stoarge, throughput,latnecy, Interaction and typical use cases in auto for V2I with hierarchial cloud with edge closer to device. All variations have some or the other proprietary approach and we need lowest common base to make sense from to defining edge cloud Infra or edge cloud App. Abstractions are key and here is an attempt to arrive at commn absractions for use cases. Suggest we discuss how to derive lowest coomon objects based on following Abstracions as a start: Abstratiing edge compute Infrastructure & Applications for Openstack 1. IDP - Third Party/ CSP2. Cloud and/or CSP - Provider/Tenanant, Type - Central/Ditributed/Edge3. Cluster - node (Compute, Network, Storage, Mixed, cloudlet ), type (Phy, Virt), topology, template, capability(Bandwidth, Latency, Jitter)4. Service composition over Cluster using VM, Containers or Unikernal5. Serbice Discovery & Registartion in Catalog6. Workload Supported - Video Streaming, Real time Application(Audio, Alarms), IoT Application, Interactive apps like Games/AR/VR/MR, Presence and Messaging (twitter/IM)7. Hardware Acceleration - Compression, Encryption, Offloading workloads8.Stateless and State Management for Applications on Edge Infrastructure 9. End-to-End Service level Policy, Resource pooling/Charging , Resiliance and other Opesrational complexity management. Since we have had many false starts sticking to basics like Prof. Saty suggetss is the best way and you are welcome to tear apart what I write here to give some alternate approach to simplify the complexity of dancing elephents as our reaserch folks call it. Also if you can educate on any projects that have covered of late any of the above which I am un-aware please educate me. Our window to close is Thursday for Vanouver CFP and like to hear from you all to see where are we headed after several attempts to get consensus on Edge Computing. We discuss this based on time available this or few more weeks when we continue this to get some reasoanble idea for blueprints and directions we take in 2018. ThanksPrakash

1 0

Request for people interested in an Edge Computing Security session at Summit
by beth.cohen＠verizon.com 04 Feb '18

04 Feb '18

Folks - I have submitted a proposal for a session at the Vancouver Summit on Securing the Edge. I am looking for people who would like to join me on the panel/presentation. Drop me a note if you are interested in participating. Cloud Edge computing use cases range from IoT to VR/AR and any widely distributed application in between. However, taking OpenStack out of the data center requires an entirely new approach to security when there is far less ability to restrict access and often the applications require a shared tenant model. Some of the factors that need to be considered include: • More stringent requirements for infrastructure software (code/design) in exposed environments • New ways of thinking about RBAC at the control interfaces • Conflicts arising from shared ownership and divided responsibilities for devices/systems/applications • Managing lifecycle operations and deployments over insecure WAN connections • Different ways of looking at tenant spaces in remote locations • Imposing network/compute/storage/memory separation from the underlying virtualization/hardware components • Managing security over intermittent WAN connections • Securing semi-autonomous and self-managed locations Beth Cohen NFV/SDN Network Product Strategy O +781-466-2055 | M +781-434-8553 beth.cohen(a)verizon.com

1 0

OpenStack Vancouver Summit CFP is open - what’s new
by Claire Massey 31 Jan '18

31 Jan '18

Hi all, Last week, we opened the Call for Presentations <https://www.openstack.org/summit/vancouver-2018/call-for-presentations/> for the OpenStack Vancouver Summit <https://www.openstack.org/summit/vancouver-2018/>, which will take place May 21-24. The deadline to submit your proposal is February 8th. What’s New? We’re focused on open infrastructure integration. The Summit has evolved over the years to cover more than just OpenStack, but we’re making an even bigger effort to attract speakers across the open infrastructure ecosystem. In addition to OpenStack-related sessions, we’ll be featuring the newest project at the Foundation -- Kata Containers -- as well as recruiting many others from projects like Ansible, Ceph, Kubernetes, ONAP and many more. We’ve also organized Tracks around specific problem domains. We encourage you to submit proposals covering OpenStack and the “open infrastructure” tools you’re using, as well as the integration work needed to address these problem domains. We also encourage you to invite peers from other open source communities to come speak and collaborate. The Tracks are: CI/CD Container Infrastructure Edge Computing HPC / GPU / AI Open Source Community Private & Hybrid Cloud Public Cloud Telecom & NFV Where previously we had Track Chairs, we now have Programming Committees <https://www.openstack.org/summit/vancouver-2018/call-for-presentations/sele…> for each Track, made up of both Members and a Chair (or co-chairs). We’re also recruiting members and chairs from many different open source communities working in open infrastructure, in addition to the many familiar faces in the OpenStack community who will lead the effort. If you’re interested in nominating yourself or someone else to be a member of the Summit Programming Committee for a specific Track, please fill out the nomination form <https://openstackfoundation.formstack.com/forms/openstackvancouver2018_prog…>. Nominations will close on January 26, 2018. Again, the deadline to submit proposals <https://www.openstack.org/summit/vancouver-2018/call-for-presentations/> is February 8, 2018. Please note topic submissions for the OpenStack Forum (planning/working sessions with OpenStack devs and operators) will open at a later date. We can’t wait to see you in Vancouver! We’re working hard to make it the best Summit yet, and look forward to bringing together different open infrastructure communities to solve these hard problems together! Want to provide feedback on this process? Please focus discussion on the openstack-community mailing list, or contact me or the OpenStack Foundation Summit Team directly at summit(a)openstack.org <mailto:summit@openstack.org>. Thanks, Claire

1 1

[FEMDC] A first step to the gap analysis of the OpenStack code base
by lebre.adrien＠free.fr 23 Jan '18

23 Jan '18

Dear all, Following our last exchanges, we had a few discussions regarding the OpenStack code base w.r.t the edge challenges. Our idea was (i) to identify a couple of requirements (from the simplest one, i.e. starting a VM at a specific location, to the most advanced one, i.e. interoperability issues between distinct cloud stacks) and (ii) to analyse how the OpenStack codebase can fulfil these requirements. Our exchanges have been summarised at : https://etherpad.openstack.org/p/edge-gap-analysis Please feel free to comment/complete it. Best regards, On behalf of the FEMDC SiG. ad_ri3n_

1 0

Tomorrow's meeting
by Jonathan Bryce 22 Jan '18

22 Jan '18

Hi everyone, I’m traveling tomorrow and will not be able to join the weekly call. I’ve asked Allison Randal to lead it and she agreed. In addition to continuing to review the scenarios, it would also be great if we could identify a few high level themes or topics that we’d like to see covered during the edge track at the Vancouver Summit. Also, next week, the call collides with the same time as a Foundation Board meeting that I know several of us will be joining, so I’d propose we skip the 2017-01-30 call. Thanks! Jonathan

2 1

Classifying edge-site scenarios / Identifying expected features
by lebre.adrien＠free.fr 11 Jan '18

11 Jan '18

Hi, Following the LTE discussion, I'm wondering whether we should not try to classify the edge-site scenarios by level of the complexity (i.e., features/capabilities each scenario implies/requires). A possible classification can start with: a) An edge infrastructure composed of several edge sites operated by a same organisation with WAN wired connections. b) The same infrastructure but with LTE connections c) Scenario a) but where the edge infrastructure is spread over several edge sites belonging to different organisations/operators d) scenario c) but with LTE e) .. In parallel, we can try to identify w.r.t these scenarios what are the expected features/services from the administrator viewpoint and then from the developers viewpoint. I have the feeling that we all have relevant scenarios with specifics according to our targets. Having a classification can allow us to move forward by just focusing on classes instead of each particular scenario independently. My two cents, ad_ri3n_

9 16

Upcoming Work Sessions Schedule - Edge
by Claire Massey 08 Jan '18

08 Jan '18

Hi there, Welcome to the new Edge-Computing mailing list! Starting this week the OpenStack Foundation will host a series of work sessions to pick up on the progress made at the OpenDev event in September [0] and the Edge Use Cases & Architecture forum session [1] at the Sydney Summit. The goal for the work sessions is to end 2017 with a clear set of edge operational requirements and documentation (there’s a whitepaper already in the works). If you’d like to become an active participant to support this effort please join us. Agenda and notes will be updated here: https://etherpad.openstack.org/p/2017_edge_computing_working_sessions <https://etherpad.openstack.org/p/2017_edge_computing_working_sessions>. The calls will be held on Tuesday’s at 9:00am CST (15:00 UTC) on *November 28 *December 12 *December 19 Meeting Link: https://zoom.us/j/777719876 Or Telephone: US: +1 646 876 9923 or +1 669 900 6833 or +1 408 638 0968 Meeting ID: 777 719 876 International numbers available: https://zoom.us/zoomconference?m=QQS_rcoIKkXtIdC_0EpVQ80nU8MYS4Y0 **** [0] http://www.opendevconf.com/schedule/ <http://www.opendevconf.com/schedule/> [1] https://etherpad.openstack.org/p/OS_Sydney_edge_computing_use_cases <https://etherpad.openstack.org/p/OS_Sydney_edge_computing_use_cases> Thanks, Claire Massey

16 36

User stories clarification
by Csatari, Gergely (Nokia - HU/Budapest) 08 Jan '18

08 Jan '18

Hi, One clarification to user story 8 from [1]: This makes sense only if the encryption is required to the traffic between physical hosts. I agree that in other cases the encryption should be done on application level. Br, Gerg0 [1]: https://etherpad.openstack.org/p/2017_edge_computing_working_sessions_exist…

1 0

Re: [Edge-computing] : Connectivity (WAS: Upcoming Work Sessions Schedule - Edge)
by Csatari, Gergely (Nokia - HU/Budapest) 05 Jan '18

05 Jan '18

Hi, You mean that the whole edge cloud is connected via LTE or any other mobile network? Br, Gerg0 From: Suyash Sinha [mailto:suyash.sinha@gmail.com] Sent: Tuesday, January 2, 2018 6:45 PM To: Csatari, Gergely (Nokia - HU/Budapest) <gergely.csatari(a)nokia.com> Cc: Claire Massey <claire(a)openstack.org>; edge-computing(a)lists.openstack.org Subject: Re: [Edge-computing] Upcoming Work Sessions Schedule - Edge Thanks Gergely. very helpful/ Based on my experience, there is also an issue of endpoint public IP address for the "edge cloudlet". We take the public IP for granted in the main datacenter but this may not be the case for edge. The edge cloudlet maybe connecting to the rest of the world via a client IP over LTE or other network that can change very often. On Tue, Jan 2, 2018 at 8:34 AM, Csatari, Gergely (Nokia - HU/Budapest) <gergely.csatari(a)nokia.com<mailto:gergely.csatari@nokia.com>> wrote: Hi, For telco the edge cloud is a necesary tool to bring the computing capability close to the end user. This is a must in case of latency sensitive applications. The main differences compared to a central cloud are: * Size is smaller, therefore the relative price of the management of the cloud is expensive (from a 4 node big cloud I would not like to have 3 dedicated control nodes) * Location is not central, therefore any management activities which are not remote are very expensive and security should be provided * Cardinality is a lot, therefore automatization of management activities are needed * Workload is very volatile, therefore it should be very fast to start and stop workloads * Workload is roaming, therefore there shold be a way to migrate the context of a workload They are similar with the main clouds in a sense, that: * low latency networking and compute are needed * some workloads are delivered as VM images and some are as container images * Resource limits are needed for the applications * Network separation is needed between the applications Br, Gerg0 From: Suyash Sinha [mailto:suyash.sinha@gmail.com<mailto:suyash.sinha@gmail.com>] Sent: Friday, December 22, 2017 3:21 PM To: Csatari, Gergely (Nokia - HU/Budapest) <gergely.csatari(a)nokia.com<mailto:gergely.csatari@nokia.com>> Cc: Claire Massey <claire(a)openstack.org<mailto:claire@openstack.org>>; edge-computing(a)lists.openstack.org<mailto:edge-computing@lists.openstack.org> Subject: Re: [Edge-computing] Upcoming Work Sessions Schedule - Edge Gergely - Thanks for the share. What you are suggesting makes sense from a structural perspective. I have been studying the edge cloud space and writing on it since 2015 (https://www.linkedin.com/pulse/pushing-cloud-edge-suyash-sinha/) . So glad to see the work starting at openstack. For me, the fundamental question that we must start with is "why edge cloud". what necessitates it? What are the technical, business and ecosystem reasons. What use cases about edge cloud are fundamentally different from the "mainframe" cloud? Perhaps, that will better help educate us about the structural aspects like VMs and containers etc. Thanks, Suyash On Wed, Dec 20, 2017 at 2:31 AM, Csatari, Gergely (Nokia - HU/Budapest) <gergely.csatari(a)nokia.com<mailto:gergely.csatari@nokia.com>> wrote: Hi, Thanks for the discussions around the user stories. Some follow up questions and notes: * Generic: I tried to use the user story<https://en.wikipedia.org/wiki/User_story#Common_templates> template, but I think we should add more descriptions becouse I feel the user story format a bit to restrctive to add all information we discussed. * Definitions: I’ve added four definitions to make the discussion about the user stories more easy. Should we add a definition to „Edge cloud” and/or „Edge cloud infrastructure” also? * Workload: Several VM or linux containers of any kind * The whole point of this, is to indicate that we are talking about VM-s and (OCI compliant) containers * Maybe we can change „workload” to „virtualisation container” if you are not very mutch agains using terms from ETSI NFV 😊. * (Edge Cloud) Infrastructure operator: an organisation responsible for operating an (edge cloud) infrastrucure * (Edge Cloud) infrastructure user: an organisation or person who is using the (edge cloud) infrastructure services to start workload * application user: an organisation or person who is using the application services runnig on top of the workloads in the (edge cloud) infrastructure * User story 1: * Can someone provide some references to the Glance edge friendly images? * User story 2: * From requirements point of view what is the difference between the multiple operator and the single operator case? In both cases there will be a need to transfer user metadata, workload images and realtime memory content between two edge clouds. Do I miss something (accounting maybe)? * User story 3: * Should we extend this to contain all FM and PM data and configurable views? * Here I do not see the case when one edge cloud infrastructure operator would be interested in the FM and PM data of an other edge cloud infrastructure operators infrastructure. Can you please explain this a bit? Is this the case when one uber operator uses edge cloud infrastructure sevice from other operators? * User Story 5: * In the Kuberentes is deployed directly on bare metal case. OpenStack should only provide the hardware management part and the capability to deploy Kubernetes. * For the Kuberentes deployed in VM-s case: What is the purpose of this? This is benefitial only if there is only an OpenStack what needs to be extended with the capaility to run containers (and still Magnum can deploy COE to bare metal if I remember correctly) or someone would like to run VM-s and contaienr in the same infra. * The question how to deploy OpenStack to the edge sites is very valid. I think this should be a separate user story. Do we want to deploy OpenStack remotely? * User Story 7: * Can someone provide a reference to Mahadev Satyanarayanan-s cloudlet material? * I understand that the different application cases generate different traffic patterns, but what is the differentce in terms of infrastructure requirements? * User Story 10 * I think the sharing of OpenStack users and tenants is not needed between operators. Maybe I’m totally missing this multi operator case, so please explain 😊 * User Story 12 * So here the required functionly is that when a new edge site is built it automaically finds the other clouds in the edge cloud infrastructure and builds up the needed connections? Is it ok to provide an ip address or fqdn as a hint for this or this should be totally automatic? Any comments to anything are welcome 😊 Br, Gerg0 From: Csatari, Gergely (Nokia - HU/Budapest) Sent: Tuesday, December 19, 2017 2:35 PM To: 'Claire Massey' <claire(a)openstack.org<mailto:claire@openstack.org>>; edge-computing(a)lists.openstack.org<mailto:edge-computing@lists.openstack.org> Subject: RE: [Edge-computing] Upcoming Work Sessions Schedule - Edge Hi, I think ont he existing gaps we should collect user stories to a separate etherpad, so I sarted just an other one: https://etherpad.openstack.org/p/2017_edge_computing_working_sessions_exist… From the user stories we can generate requirements which can be turned into implementable pieces after a while 😊 Br, Gerg0 From: Claire Massey [mailto:claire@openstack.org] Sent: Tuesday, December 19, 2017 12:24 AM To: edge-computing(a)lists.openstack.org<mailto:edge-computing@lists.openstack.org> Subject: Re: [Edge-computing] Upcoming Work Sessions Schedule - Edge Correction - December 19th at 9:00am CST. Meeting Link: https://zoom.us/j/777719876 On Dec 18, 2017, at 5:12 PM, Claire Massey <claire(a)openstack.org<mailto:claire@openstack.org>> wrote: Quick reminder - we have another community Edge Work Session call tomorrow Tuesday, December 18 at 9:00am CST. Meeting Link: https://zoom.us/j/777719876 Etherpad: : https://etherpad.openstack.org/p/2017_edge_computing_working_sessions We look forward to chatting with you all then. Thanks! On Dec 11, 2017, at 4:31 PM, Claire Massey <claire(a)openstack.org<mailto:claire@openstack.org>> wrote: Hi everyone, Quick reminder that we have another community Edge Work Session call tomorrow, Tuesday, at 9:00am CST. Meeting Link: https://zoom.us/j/777719876 Etherpad: : https://etherpad.openstack.org/p/2017_edge_computing_working_sessions We look forward to chatting with you all then. Thanks, Claire On Nov 29, 2017, at 12:15 PM, Claire Massey <claire(a)openstack.org<mailto:claire@openstack.org>> wrote: Thank you to everyone who attended the first edge work session call yesterday! Records from the meeting: * Etherpad: https://etherpad.openstack.org/p/2017_edge_computing_working_sessions * Audio recording of the November 28 meeting: https://zoom.us/recording/play/t_XmAP-VK1RRGKhy_Epb4TF57rlOIM1gkd9qvJQ18G9e… During the meeting we established three focus areas for work to be done: - OpenStack existing gaps - Cross-community efforts - Potential new project needs Volunteers have signed up to help lead these efforts. More details and next steps will soon be shared on the mailing list as well as the opportunity for others to get involved. The next edge work session call will be on Tuesday, December 12, at 9:00am CST (15:00 UTC) at https://zoom.us/j/777719876. Thanks, Claire On Nov 26, 2017, at 4:15 PM, Claire Massey <claire(a)openstack.org<mailto:claire@openstack.org>> wrote: Hi there, Welcome to the new Edge-Computing mailing list! Starting this week the OpenStack Foundation will host a series of work sessions to pick up on the progress made at the OpenDev event in September [0] and the Edge Use Cases & Architecture forum session [1] at the Sydney Summit. The goal for the work sessions is to end 2017 with a clear set of edge operational requirements and documentation (there’s a whitepaper already in the works). If you’d like to become an active participant to support this effort please join us. Agenda and notes will be updated here: https://etherpad.openstack.org/p/2017_edge_computing_working_sessions. The calls will be held on Tuesday’s at 9:00am CST (15:00 UTC) on *November 28 *December 12 *December 19 Meeting Link: https://zoom.us/j/777719876 Or Telephone: US: +1 646 876 9923<tel:(646)%20876-9923> or +1 669 900 6833<tel:(669)%20900-6833> or +1 408 638 0968<tel:(408)%20638-0968> Meeting ID: 777 719 876 International numbers available: https://zoom.us/zoomconference?m=QQS_rcoIKkXtIdC_0EpVQ80nU8MYS4Y0 **** [0] http://www.opendevconf.com/schedule/ [1] https://etherpad.openstack.org/p/OS_Sydney_edge_computing_use_cases Thanks, Claire Massey _______________________________________________ Edge-computing mailing list Edge-computing(a)lists.openstack.org<mailto:Edge-computing@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing _______________________________________________ Edge-computing mailing list Edge-computing(a)lists.openstack.org<mailto:Edge-computing@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing _______________________________________________ Edge-computing mailing list Edge-computing(a)lists.openstack.org<mailto:Edge-computing@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing _______________________________________________ Edge-computing mailing list Edge-computing(a)lists.openstack.org<mailto:Edge-computing@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing _______________________________________________ Edge-computing mailing list Edge-computing(a)lists.openstack.org<mailto:Edge-computing@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing -- s -- s

4 3