From gergely.csatari at nokia.com  Tue Jan  2 16:34:34 2018
From: gergely.csatari at nokia.com (Csatari, Gergely (Nokia - HU/Budapest))
Date: Tue, 2 Jan 2018 16:34:34 +0000
Subject: [Edge-computing] Upcoming Work Sessions Schedule - Edge
In-Reply-To: <CAN9VmJ_ff-68Wr1fdt0QwgQtv=QorS8-UKQmt60FE8rh==Dbzg@mail.gmail.com>
References: <65B731CF-65C7-47C0-997C-0C5B21C204DE@openstack.org>
 <A2E5AD7F-8373-45ED-8866-287E029E438C@openstack.org>
 <A10E0283-34D5-4338-B996-8CAD529AF2AB@openstack.org>
 <C52DFBA7-6633-430B-83B0-811607511286@openstack.org>
 <76CAF51A-F83B-4CC0-B577-3706D25CD319@openstack.org>
 <HE1PR07MB3355F223FC193344DEDDD7A9E10F0@HE1PR07MB3355.eurprd07.prod.outlook.com>
 <HE1PR07MB3355880FE9F1C0C0BA24442EE10C0@HE1PR07MB3355.eurprd07.prod.outlook.com>
 <CAN9VmJ_ff-68Wr1fdt0QwgQtv=QorS8-UKQmt60FE8rh==Dbzg@mail.gmail.com>
Message-ID: <HE1PR07MB335527DF1D0A40A49B9FB618E1190@HE1PR07MB3355.eurprd07.prod.outlook.com>

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 at gmail.com]
Sent: Friday, December 22, 2017 3:21 PM
To: Csatari, Gergely (Nokia - HU/Budapest) <gergely.csatari at nokia.com>
Cc: Claire Massey <claire at openstack.org>; edge-computing at 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 at nokia.com<mailto:gergely.csatari at 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 at openstack.org<mailto:claire at openstack.org>>; edge-computing at lists.openstack.org<mailto:edge-computing at 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_existing_gaps

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 at openstack.org]
Sent: Tuesday, December 19, 2017 12:24 AM
To: edge-computing at lists.openstack.org<mailto:edge-computing at 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 at openstack.org<mailto:claire at 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 at openstack.org<mailto:claire at 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 at openstack.org<mailto:claire at 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_Epb4TF57rlOIM1gkd9qvJQ18G9eidjhBS-UHprOzCjA6NSB

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 at openstack.org<mailto:claire at 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 at lists.openstack.org<mailto:Edge-computing at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing

_______________________________________________
Edge-computing mailing list
Edge-computing at lists.openstack.org<mailto:Edge-computing at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing

_______________________________________________
Edge-computing mailing list
Edge-computing at lists.openstack.org<mailto:Edge-computing at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing

_______________________________________________
Edge-computing mailing list
Edge-computing at lists.openstack.org<mailto:Edge-computing at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing


_______________________________________________
Edge-computing mailing list
Edge-computing at lists.openstack.org<mailto:Edge-computing at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing



--
s
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/edge-computing/attachments/20180102/8e39cc9b/attachment-0001.html>

From gergely.csatari at nokia.com  Tue Jan  2 16:40:06 2018
From: gergely.csatari at nokia.com (Csatari, Gergely (Nokia - HU/Budapest))
Date: Tue, 2 Jan 2018 16:40:06 +0000
Subject: [Edge-computing] Upcoming Work Sessions Schedule - Edge
In-Reply-To: <201712261137.09435.satya@cs.cmu.edu>
References: <65B731CF-65C7-47C0-997C-0C5B21C204DE@openstack.org>
 <HE1PR07MB3355880FE9F1C0C0BA24442EE10C0@HE1PR07MB3355.eurprd07.prod.outlook.com>
 <447fbe3e-56c5-90bf-c8af-41134f39df66@lohutok.net>
 <201712261137.09435.satya@cs.cmu.edu>
Message-ID: <HE1PR07MB33556E61004FC5D27A63B6DCE1190@HE1PR07MB3355.eurprd07.prod.outlook.com>

Hi, 

Thanks for the links. 
Wow, thats a lots of papers 😊

Do you have any suggestion where to start?

Br, 
Gerg0

-----Original Message-----
From: Mahadev Satyanarayanan [mailto:satya at cs.cmu.edu] 
Sent: Tuesday, December 26, 2017 5:37 PM
To: edge-computing at lists.openstack.org
Cc: Allison Randal <allison at lohutok.net>; Csatari, Gergely (Nokia - HU/Budapest) <gergely.csatari at nokia.com>
Subject: Re: [Edge-computing] Upcoming Work Sessions Schedule - Edge

A better URL, just for edge computing papers, is this:
  http://elijah.cs.cmu.edu/publications.html

The URL Allison gave also works, but covers all my papers rather than just those on edge computing.

      -- Satya


On Tuesday 26 December 2017 11:30:36 Allison Randal wrote:
> On 12/20/2017 05:31 AM, Csatari, Gergely (Nokia - HU/Budapest) wrote:
> >   * User Story 7:
> >       o Can someone provide a reference to Mahadev Satyanarayanan-s
> >         cloudlet material?
> 
> Start here:
> 
> https://www.cs.cmu.edu/~satya/satya_papers.html
> 
> Especially:
> 
> http://www.cs.cmu.edu/%7Esatya/docdir/satya-mobicase2014.pdf
> 
> Allison
> 
> _______________________________________________
> Edge-computing mailing list
> Edge-computing at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
> 

From suyash.sinha at gmail.com  Tue Jan  2 17:45:28 2018
From: suyash.sinha at gmail.com (Suyash Sinha)
Date: Tue, 2 Jan 2018 09:45:28 -0800
Subject: [Edge-computing] Upcoming Work Sessions Schedule - Edge
In-Reply-To: <HE1PR07MB335527DF1D0A40A49B9FB618E1190@HE1PR07MB3355.eurprd07.prod.outlook.com>
References: <65B731CF-65C7-47C0-997C-0C5B21C204DE@openstack.org>
 <A2E5AD7F-8373-45ED-8866-287E029E438C@openstack.org>
 <A10E0283-34D5-4338-B996-8CAD529AF2AB@openstack.org>
 <C52DFBA7-6633-430B-83B0-811607511286@openstack.org>
 <76CAF51A-F83B-4CC0-B577-3706D25CD319@openstack.org>
 <HE1PR07MB3355F223FC193344DEDDD7A9E10F0@HE1PR07MB3355.eurprd07.prod.outlook.com>
 <HE1PR07MB3355880FE9F1C0C0BA24442EE10C0@HE1PR07MB3355.eurprd07.prod.outlook.com>
 <CAN9VmJ_ff-68Wr1fdt0QwgQtv=QorS8-UKQmt60FE8rh==Dbzg@mail.gmail.com>
 <HE1PR07MB335527DF1D0A40A49B9FB618E1190@HE1PR07MB3355.eurprd07.prod.outlook.com>
Message-ID: <CAN9VmJ_Mu8iN7Wn+XXvb1e6b8f3zC_+YoVFS37tpzRm9w0CB=A@mail.gmail.com>

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 at 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 at gmail.com]
> *Sent:* Friday, December 22, 2017 3:21 PM
> *To:* Csatari, Gergely (Nokia - HU/Budapest) <gergely.csatari at nokia.com>
> *Cc:* Claire Massey <claire at openstack.org>; edge-computing at 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 at 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 at openstack.org>; edge-computing at 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_existing_gaps
>
>
>
> 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 at openstack.org <claire at openstack.org>]
>
> *Sent:* Tuesday, December 19, 2017 12:24 AM
> *To:* edge-computing at 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 at 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 at 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 at 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_Epb4TF57rlOIM1gkd9qvJQ18G9eidj
> hBS-UHprOzCjA6NSB
>
>
>
> 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 at 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 <(646)%20876-9923>  or +1 669 900 6833
> <(669)%20900-6833>  or +1 408 638 0968 <(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 at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
>
>
>
> _______________________________________________
> Edge-computing mailing list
> Edge-computing at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
>
>
>
> _______________________________________________
> Edge-computing mailing list
> Edge-computing at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
>
>
>
> _______________________________________________
> Edge-computing mailing list
> Edge-computing at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
>
>
>
>
> _______________________________________________
> Edge-computing mailing list
> Edge-computing at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
>
>
>
>
>
> --
>
> s
>



-- 
s
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/edge-computing/attachments/20180102/d4ecbffc/attachment-0001.html>

From satya at cs.cmu.edu  Tue Jan  2 18:47:21 2018
From: satya at cs.cmu.edu (Mahadev Satyanarayanan)
Date: Tue, 2 Jan 2018 13:47:21 -0500
Subject: [Edge-computing] Upcoming Work Sessions Schedule - Edge
In-Reply-To: <HE1PR07MB33556E61004FC5D27A63B6DCE1190@HE1PR07MB3355.eurprd07.prod.outlook.com>
References: <65B731CF-65C7-47C0-997C-0C5B21C204DE@openstack.org>
 <HE1PR07MB3355880FE9F1C0C0BA24442EE10C0@HE1PR07MB3355.eurprd07.prod.outlook.com>
 <447fbe3e-56c5-90bf-c8af-41134f39df66@lohutok.net>
 <201712261137.09435.satya@cs.cmu.edu>
 <HE1PR07MB33556E61004FC5D27A63B6DCE1190@HE1PR07MB3355.eurprd07.prod.outlook.com>
Message-ID: <CAPj9B=T0+mp-qwqxg8f5Z4f-1O3vwDg27gJ+FyjDeY_-tiMa6g@mail.gmail.com>

0. "The  Emergence  of Edge Computing
<http://gabriel.cs.cmu.edu/DOCS/satya-edge2016.pdf>" is the best place to
start.

After that, I suggest these 4 papers in this order:
  1. "An Open Ecosystem for Mobile-Cloud Convergence"
<http://gabriel.cs.cmu.edu/DOCS/satya-cloudlet-ecosystem-2015.pdf>
      (especially the section "Industry-Wide Business Opportunities Drive
an Open Ecosystem"
  2. "Just-in-Time Provisioning for Cyber Foraging
<http://gabriel.cs.cmu.edu/DOCS/ha-mobisys-vmsynthesis-2013.pdf>"
  3. ‘‘You Can Teach Elephants to Dance: Agile VM Handoff for Edge Computing
<http://gabriel.cs.cmu.edu/DOCS/ha-sec2017.pdf>’’
  4. "OpenStack++ for Cloudlet Deployment
<http://gabriel.cs.cmu.edu/DOCS/CMU-CS-15-123.pdf>"

#2 and #3 describe valuable functionality for edge computing infrastructure,
along with motivating use cases.  #4 describes the integration of this
functionality
into OpenStack.

   -- Satya

On Tue, Jan 2, 2018 at 11:40 AM, Csatari, Gergely (Nokia - HU/Budapest) <
gergely.csatari at nokia.com> wrote:

> Hi,
>
> Thanks for the links.
> Wow, thats a lots of papers 😊
>
> Do you have any suggestion where to start?
>
> Br,
> Gerg0
>
> -----Original Message-----
> From: Mahadev Satyanarayanan [mailto:satya at cs.cmu.edu]
> Sent: Tuesday, December 26, 2017 5:37 PM
> To: edge-computing at lists.openstack.org
> Cc: Allison Randal <allison at lohutok.net>; Csatari, Gergely (Nokia -
> HU/Budapest) <gergely.csatari at nokia.com>
> Subject: Re: [Edge-computing] Upcoming Work Sessions Schedule - Edge
>
> A better URL, just for edge computing papers, is this:
>   http://elijah.cs.cmu.edu/publications.html
>
> The URL Allison gave also works, but covers all my papers rather than just
> those on edge computing.
>
>       -- Satya
>
>
> On Tuesday 26 December 2017 11:30:36 Allison Randal wrote:
> > On 12/20/2017 05:31 AM, Csatari, Gergely (Nokia - HU/Budapest) wrote:
> > >   * User Story 7:
> > >       o Can someone provide a reference to Mahadev Satyanarayanan-s
> > >         cloudlet material?
> >
> > Start here:
> >
> > https://www.cs.cmu.edu/~satya/satya_papers.html
> >
> > Especially:
> >
> > http://www.cs.cmu.edu/%7Esatya/docdir/satya-mobicase2014.pdf
> >
> > Allison
> >
> > _______________________________________________
> > Edge-computing mailing list
> > Edge-computing at lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/edge-computing/attachments/20180102/ee854bf9/attachment.html>

From lebre.adrien at free.fr  Tue Jan  2 23:26:53 2018
From: lebre.adrien at free.fr (lebre.adrien at free.fr)
Date: Wed, 3 Jan 2018 00:26:53 +0100 (CET)
Subject: [Edge-computing] Upcoming Work Sessions Schedule - Edge
In-Reply-To: <CAN9VmJ_Mu8iN7Wn+XXvb1e6b8f3zC_+YoVFS37tpzRm9w0CB=A@mail.gmail.com>
Message-ID: <2030474958.263337939.1514935613746.JavaMail.root@zimbra29-e5>

Hi Gentlemen, 

Would it be possible to start a new thread each time there is a specific discussion? 
I think it is hard to follow the conversation related to the bibliographies and the one related to why edge/what is edge, keeping in mind that the current thread is related to the ''Upcoming Working Sessions Schedule''

Thanks, 
ad_ri3n_

----- Mail original -----
> De: "Suyash Sinha" <suyash.sinha at gmail.com>
> À: "Gergely Csatari (Nokia - HU/Budapest)" <gergely.csatari at nokia.com>
> Cc: edge-computing at lists.openstack.org
> Envoyé: Mardi 2 Janvier 2018 18:45:28
> Objet: 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 at 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 at gmail.com ]
> Sent: Friday, December 22, 2017 3:21 PM
> To: Csatari, Gergely (Nokia - HU/Budapest) <
> gergely.csatari at nokia.com >
> Cc: Claire Massey < claire at openstack.org >;
> edge-computing at 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 at 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 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 at openstack.org >;
> edge-computing at 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_existing_gaps
> 
> 
> 
> 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 at openstack.org ]
> Sent: Tuesday, December 19, 2017 12:24 AM
> To: edge-computing at 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 at 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 at 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 at 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_Epb4TF57rlOIM1gkd9qvJQ18G9eidjhBS-UHprOzCjA6NSB
> 
> 
> 
> 
> 
> 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 at 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 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/
> 
> 
> [1]
> https://etherpad.openstack.org/p/OS_Sydney_edge_computing_use_cases
> 
> 
> 
> 
> 
> Thanks,
> 
> 
> Claire Massey
> 
> _______________________________________________
> Edge-computing mailing list
> Edge-computing at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
> 
> 
> 
> _______________________________________________
> Edge-computing mailing list
> Edge-computing at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
> 
> 
> 
> _______________________________________________
> Edge-computing mailing list
> Edge-computing at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
> 
> 
> 
> _______________________________________________
> Edge-computing mailing list
> Edge-computing at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
> 
> 
> 
> 
> _______________________________________________
> Edge-computing mailing list
> Edge-computing at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
> 
> 
> 
> 
> 
> 
> 
> 
> --
> 
> 
> 
> 
> 
> s
> 
> 
> 
> --
> 
> 
> 
> 
> s
> 
> _______________________________________________
> Edge-computing mailing list
> Edge-computing at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
> 


From gergely.csatari at nokia.com  Wed Jan  3 07:23:05 2018
From: gergely.csatari at nokia.com (Csatari, Gergely (Nokia - HU/Budapest))
Date: Wed, 3 Jan 2018 07:23:05 +0000
Subject: [Edge-computing] : Meta discussion (WAS: Upcoming Work Sessions
 Schedule - Edge)
Message-ID: <HE1PR07MB3355BE51B5EB86EAC1E212DAE11E0@HE1PR07MB3355.eurprd07.prod.outlook.com>

Hi, 

Sure, it is a good idea. 

Br, 
Gerg0

-----Original Message-----
From: lebre.adrien at free.fr [mailto:lebre.adrien at free.fr] 
Sent: Wednesday, January 3, 2018 12:27 AM
To: Suyash Sinha <suyash.sinha at gmail.com>
Cc: edge-computing at lists.openstack.org; Csatari, Gergely (Nokia - HU/Budapest) <gergely.csatari at nokia.com>
Subject: Re: [Edge-computing] Upcoming Work Sessions Schedule - Edge

Hi Gentlemen, 

Would it be possible to start a new thread each time there is a specific discussion? 
I think it is hard to follow the conversation related to the bibliographies and the one related to why edge/what is edge, keeping in mind that the current thread is related to the ''Upcoming Working Sessions Schedule''

Thanks,
ad_ri3n_

----- Mail original -----
> De: "Suyash Sinha" <suyash.sinha at gmail.com>
> À: "Gergely Csatari (Nokia - HU/Budapest)" <gergely.csatari at nokia.com>
> Cc: edge-computing at lists.openstack.org
> Envoyé: Mardi 2 Janvier 2018 18:45:28
> Objet: 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 at 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 at gmail.com ]
> Sent: Friday, December 22, 2017 3:21 PM
> To: Csatari, Gergely (Nokia - HU/Budapest) < gergely.csatari at nokia.com 
> >
> Cc: Claire Massey < claire at openstack.org >; 
> edge-computing at 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 at 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 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 at openstack.org >; 
> edge-computing at 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_
> existing_gaps
> 
> 
> 
> 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 at openstack.org ]
> Sent: Tuesday, December 19, 2017 12:24 AM
> To: edge-computing at 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 at 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 at 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 at 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_Epb4TF57rlOIM1gkd9qvJQ
> 18G9eidjhBS-UHprOzCjA6NSB
> 
> 
> 
> 
> 
> 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 at 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 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/
> 
> 
> [1]
> https://etherpad.openstack.org/p/OS_Sydney_edge_computing_use_cases
> 
> 
> 
> 
> 
> Thanks,
> 
> 
> Claire Massey
> 
> _______________________________________________
> Edge-computing mailing list
> Edge-computing at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
> 
> 
> 
> _______________________________________________
> Edge-computing mailing list
> Edge-computing at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
> 
> 
> 
> _______________________________________________
> Edge-computing mailing list
> Edge-computing at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
> 
> 
> 
> _______________________________________________
> Edge-computing mailing list
> Edge-computing at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
> 
> 
> 
> 
> _______________________________________________
> Edge-computing mailing list
> Edge-computing at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
> 
> 
> 
> 
> 
> 
> 
> 
> --
> 
> 
> 
> 
> 
> s
> 
> 
> 
> --
> 
> 
> 
> 
> s
> 
> _______________________________________________
> Edge-computing mailing list
> Edge-computing at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
> 

From gergely.csatari at nokia.com  Wed Jan  3 13:47:05 2018
From: gergely.csatari at nokia.com (Csatari, Gergely (Nokia - HU/Budapest))
Date: Wed, 3 Jan 2018 13:47:05 +0000
Subject: [Edge-computing] : Satya papers (WAS: Upcoming Work Sessions
 Schedule - Edge)
Message-ID: <HE1PR07MB335581934401214877A809F3E11E0@HE1PR07MB3355.eurprd07.prod.outlook.com>

Hi,

Thanks for the suggestions. I’ve added the links to the etherpad (https://etherpad.openstack.org/p/2017_edge_computing_working_sessions_existing_gaps).

Br,
Gerg0

From: Mahadev Satyanarayanan [mailto:satya at cs.cmu.edu]
Sent: Tuesday, January 2, 2018 7:47 PM
To: Csatari, Gergely (Nokia - HU/Budapest) <gergely.csatari at nokia.com>
Cc: edge-computing at lists.openstack.org; Allison Randal <allison at lohutok.net>
Subject: Re: [Edge-computing] Upcoming Work Sessions Schedule - Edge

0. "The  Emergence  of Edge Computing<http://gabriel.cs.cmu.edu/DOCS/satya-edge2016.pdf>" is the best place to start.

After that, I suggest these 4 papers in this order:
  1. "An Open Ecosystem for Mobile-Cloud Convergence"<http://gabriel.cs.cmu.edu/DOCS/satya-cloudlet-ecosystem-2015.pdf>
      (especially the section "Industry-Wide Business Opportunities Drive an Open Ecosystem"
  2. "Just-in-Time Provisioning for Cyber Foraging<http://gabriel.cs.cmu.edu/DOCS/ha-mobisys-vmsynthesis-2013.pdf>"
  3. ‘‘You Can Teach Elephants to Dance: Agile VM Handoff for Edge Computing<http://gabriel.cs.cmu.edu/DOCS/ha-sec2017.pdf>’’
  4. "OpenStack++ for Cloudlet Deployment<http://gabriel.cs.cmu.edu/DOCS/CMU-CS-15-123.pdf>"

#2 and #3 describe valuable functionality for edge computing infrastructure,
along with motivating use cases.  #4 describes the integration of this functionality
into OpenStack.

   -- Satya

On Tue, Jan 2, 2018 at 11:40 AM, Csatari, Gergely (Nokia - HU/Budapest) <gergely.csatari at nokia.com<mailto:gergely.csatari at nokia.com>> wrote:
Hi,

Thanks for the links.
Wow, thats a lots of papers 😊

Do you have any suggestion where to start?

Br,
Gerg0

-----Original Message-----
From: Mahadev Satyanarayanan [mailto:satya at cs.cmu.edu<mailto:satya at cs.cmu.edu>]
Sent: Tuesday, December 26, 2017 5:37 PM
To: edge-computing at lists.openstack.org<mailto:edge-computing at lists.openstack.org>
Cc: Allison Randal <allison at lohutok.net<mailto:allison at lohutok.net>>; Csatari, Gergely (Nokia - HU/Budapest) <gergely.csatari at nokia.com<mailto:gergely.csatari at nokia.com>>
Subject: Re: [Edge-computing] Upcoming Work Sessions Schedule - Edge
A better URL, just for edge computing papers, is this:
  http://elijah.cs.cmu.edu/publications.html

The URL Allison gave also works, but covers all my papers rather than just those on edge computing.

      -- Satya


On Tuesday 26 December 2017 11:30:36 Allison Randal wrote:
> On 12/20/2017 05:31 AM, Csatari, Gergely (Nokia - HU/Budapest) wrote:
> >   * User Story 7:
> >       o Can someone provide a reference to Mahadev Satyanarayanan-s
> >         cloudlet material?
>
> Start here:
>
> https://www.cs.cmu.edu/~satya/satya_papers.html
>
> Especially:
>
> http://www.cs.cmu.edu/%7Esatya/docdir/satya-mobicase2014.pdf
>
> Allison
>
> _______________________________________________
> Edge-computing mailing list
> Edge-computing at lists.openstack.org<mailto:Edge-computing at lists.openstack.org>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/edge-computing/attachments/20180103/e5fc0872/attachment.html>

From lebre.adrien at free.fr  Thu Jan  4 16:14:30 2018
From: lebre.adrien at free.fr (lebre.adrien at free.fr)
Date: Thu, 4 Jan 2018 17:14:30 +0100 (CET)
Subject: [Edge-computing] : Satya papers (WAS: Upcoming Work Sessions
 Schedule - Edge) - BIBLIOGRAPHY
In-Reply-To: <HE1PR07MB335581934401214877A809F3E11E0@HE1PR07MB3355.eurprd07.prod.outlook.com>
Message-ID: <602792034.270300759.1515082470759.JavaMail.root@zimbra29-e5>

Hi, 

thanks for opening a new thread :-P
 
Just to complete the Satya'papers, I think it would be great to maintain somewhere papers that deal with the question of Fog/Edge under the perspective of OpenStack (or other open-source frameworks).

You can complete the initial list with: 
http://ieeexplore.ieee.org/document/7785190/
http://ieeexplore.ieee.org/document/7923796/

The first one presents the global idea of an OpenStack with a global DB (i.e. based on a REDIS prototype - as I mentioned there is an ongoing implementation with cockroach in order to keep the SQL API). 
The second one tries to investigate what will be other issues to deal with if you consider that you have a global DB. 

More generally, the weakness of all those papers (and probably others you can find on the web or in other ACM/IEEE/Usenix Conferences) is that they focus on one particular challenge: they are interesting, relevant and valuable to move forward but they do not propose/evaluate a global architecture. 

IMHO, the challenge it would be nice to deal with is related to the definition of such a global architecture w.r.t. available solutions such as OpenStack (or other open-source frameworks). 
Maybe I miss an important article but AFAIK, there is not such a paper that defines major components, how they should interact each other and which open-source components we can re-used (keeping in mind the development effort it will require, it is important to do not reinvent the wheel and use as much as available pieces of code...)

Remarks/comments welcome.
Best,
ad_ri3n_




----- Mail original -----
> De: "Gergely Csatari (Nokia - HU/Budapest)" <gergely.csatari at nokia.com>
> À: "Mahadev Satyanarayanan" <satya at cs.cmu.edu>
> Cc: edge-computing at lists.openstack.org
> Envoyé: Mercredi 3 Janvier 2018 14:47:05
> Objet: Re: [Edge-computing] : Satya papers (WAS: Upcoming Work Sessions Schedule - Edge)
> 
> 
> 
> 
> 
> Hi,
> 
> 
> 
> Thanks for the suggestions. I’ve added the links to the etherpad (
> https://etherpad.openstack.org/p/2017_edge_computing_working_sessions_existing_gaps
> ).
> 
> 
> 
> Br,
> 
> Gerg0
> 
> 
> 
> From: Mahadev Satyanarayanan [mailto:satya at cs.cmu.edu]
> Sent: Tuesday, January 2, 2018 7:47 PM
> To: Csatari, Gergely (Nokia - HU/Budapest)
> <gergely.csatari at nokia.com>
> Cc: edge-computing at lists.openstack.org; Allison Randal
> <allison at lohutok.net>
> Subject: Re: [Edge-computing] Upcoming Work Sessions Schedule - Edge
> 
> 
> 
> 
> 
> 0. " The Emergence of Edge Computing " is the best place to start.
> 
> 
> 
> 
> 
> After that, I suggest these 4 papers in this order:
> 
> 
> 1. "An Open Ecosystem for Mobile-Cloud Convergence"
> 
> 
> (especially the section "Industry-Wide Business Opportunities Drive
> an Open Ecosystem"
> 
> 
> 2. " Just-in-Time Provisioning for Cyber Foraging "
> 
> 
> 3. ‘‘ You Can Teach Elephants to Dance: Agile VM Handoff for Edge
> Computing ’’
> 
> 
> 4. " OpenStack++ for Cloudlet Deployment "
> 
> 
> 
> 
> 
> #2 and #3 describe valuable functionality for edge computing
> infrastructure,
> 
> 
> along with motivating use cases. #4 describes the integration of this
> functionality
> 
> 
> into OpenStack.
> 
> 
> 
> 
> -- Satya
> 
> 
> 
> 
> 
> On Tue, Jan 2, 2018 at 11:40 AM, Csatari, Gergely (Nokia -
> HU/Budapest) < gergely.csatari at nokia.com > wrote:
> 
> 
> 
> Hi,
> 
> Thanks for the links.
> Wow, thats a lots of papers 
> 
> Do you have any suggestion where to start?
> 
> Br,
> Gerg0
> 
> -----Original Message-----
> From: Mahadev Satyanarayanan [mailto: satya at cs.cmu.edu ]
> Sent: Tuesday, December 26, 2017 5:37 PM
> To: edge-computing at lists.openstack.org
> Cc: Allison Randal < allison at lohutok.net >; Csatari, Gergely (Nokia -
> HU/Budapest) < gergely.csatari at nokia.com >
> Subject: Re: [Edge-computing] Upcoming Work Sessions Schedule - Edge
> 
> 
> 
> A better URL, just for edge computing papers, is this:
> http://elijah.cs.cmu.edu/publications.html
> 
> The URL Allison gave also works, but covers all my papers rather than
> just those on edge computing.
> 
> -- Satya
> 
> 
> On Tuesday 26 December 2017 11:30:36 Allison Randal wrote:
> > On 12/20/2017 05:31 AM, Csatari, Gergely (Nokia - HU/Budapest)
> > wrote:
> > > * User Story 7:
> > > o Can someone provide a reference to Mahadev Satyanarayanan-s
> > > cloudlet material?
> > 
> > Start here:
> > 
> > https://www.cs.cmu.edu/~satya/satya_papers.html
> > 
> > Especially:
> > 
> > http://www.cs.cmu.edu/%7Esatya/docdir/satya-mobicase2014.pdf
> > 
> > Allison
> > 
> > _______________________________________________
> > Edge-computing mailing list
> > Edge-computing at lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
> > 
> 
> 
> _______________________________________________
> Edge-computing mailing list
> Edge-computing at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
>


From lebre.adrien at free.fr  Thu Jan  4 16:19:26 2018
From: lebre.adrien at free.fr (lebre.adrien at free.fr)
Date: Thu, 4 Jan 2018 17:19:26 +0100 (CET)
Subject: [Edge-computing] Preparation of the PTG - Please do not forget to
	fill the etherpad
Message-ID: <86386961.270319330.1515082766211.JavaMail.root@zimbra29-e5>

Hi all, 


Please do not forget to give a look at and contribute to https://etherpad.openstack.org/p/edge-ptg-dublin
Some folks already provided valuable comments/questions. 

Thanks in advance, 
ad_ri3n_




From gergely.csatari at nokia.com  Fri Jan  5 13:24:14 2018
From: gergely.csatari at nokia.com (Csatari, Gergely (Nokia - HU/Budapest))
Date: Fri, 5 Jan 2018 13:24:14 +0000
Subject: [Edge-computing] : Satya papers (WAS: Upcoming Work Sessions
 Schedule - Edge) - BIBLIOGRAPHY
In-Reply-To: <602792034.270300759.1515082470759.JavaMail.root@zimbra29-e5>
References: <HE1PR07MB335581934401214877A809F3E11E0@HE1PR07MB3355.eurprd07.prod.outlook.com>
 <602792034.270300759.1515082470759.JavaMail.root@zimbra29-e5>
Message-ID: <HE1PR07MB3355ED5DDE6ACF92D2A12066E11C0@HE1PR07MB3355.eurprd07.prod.outlook.com>

Hi, 

I've added these from line 216 of https://etherpad.openstack.org/p/2017_edge_computing_working_sessions

Br, 
Gerg0

-----Original Message-----
From: lebre.adrien at free.fr [mailto:lebre.adrien at free.fr] 
Sent: Thursday, January 4, 2018 5:15 PM
To: edge-computing at lists.openstack.org
Subject: Re: [Edge-computing] : Satya papers (WAS: Upcoming Work Sessions Schedule - Edge) - BIBLIOGRAPHY

Hi, 

thanks for opening a new thread :-P
 
Just to complete the Satya'papers, I think it would be great to maintain somewhere papers that deal with the question of Fog/Edge under the perspective of OpenStack (or other open-source frameworks).

You can complete the initial list with: 
http://ieeexplore.ieee.org/document/7785190/
http://ieeexplore.ieee.org/document/7923796/

The first one presents the global idea of an OpenStack with a global DB (i.e. based on a REDIS prototype - as I mentioned there is an ongoing implementation with cockroach in order to keep the SQL API). 
The second one tries to investigate what will be other issues to deal with if you consider that you have a global DB. 

More generally, the weakness of all those papers (and probably others you can find on the web or in other ACM/IEEE/Usenix Conferences) is that they focus on one particular challenge: they are interesting, relevant and valuable to move forward but they do not propose/evaluate a global architecture. 

IMHO, the challenge it would be nice to deal with is related to the definition of such a global architecture w.r.t. available solutions such as OpenStack (or other open-source frameworks). 
Maybe I miss an important article but AFAIK, there is not such a paper that defines major components, how they should interact each other and which open-source components we can re-used (keeping in mind the development effort it will require, it is important to do not reinvent the wheel and use as much as available pieces of code...)

Remarks/comments welcome.
Best,
ad_ri3n_




----- Mail original -----
> De: "Gergely Csatari (Nokia - HU/Budapest)" 
> <gergely.csatari at nokia.com>
> À: "Mahadev Satyanarayanan" <satya at cs.cmu.edu>
> Cc: edge-computing at lists.openstack.org
> Envoyé: Mercredi 3 Janvier 2018 14:47:05
> Objet: Re: [Edge-computing] : Satya papers (WAS: Upcoming Work 
> Sessions Schedule - Edge)
> 
> 
> 
> 
> 
> Hi,
> 
> 
> 
> Thanks for the suggestions. I’ve added the links to the etherpad ( 
> https://etherpad.openstack.org/p/2017_edge_computing_working_sessions_
> existing_gaps
> ).
> 
> 
> 
> Br,
> 
> Gerg0
> 
> 
> 
> From: Mahadev Satyanarayanan [mailto:satya at cs.cmu.edu]
> Sent: Tuesday, January 2, 2018 7:47 PM
> To: Csatari, Gergely (Nokia - HU/Budapest) <gergely.csatari at nokia.com>
> Cc: edge-computing at lists.openstack.org; Allison Randal 
> <allison at lohutok.net>
> Subject: Re: [Edge-computing] Upcoming Work Sessions Schedule - Edge
> 
> 
> 
> 
> 
> 0. " The Emergence of Edge Computing " is the best place to start.
> 
> 
> 
> 
> 
> After that, I suggest these 4 papers in this order:
> 
> 
> 1. "An Open Ecosystem for Mobile-Cloud Convergence"
> 
> 
> (especially the section "Industry-Wide Business Opportunities Drive an 
> Open Ecosystem"
> 
> 
> 2. " Just-in-Time Provisioning for Cyber Foraging "
> 
> 
> 3. ‘‘ You Can Teach Elephants to Dance: Agile VM Handoff for Edge 
> Computing ’’
> 
> 
> 4. " OpenStack++ for Cloudlet Deployment "
> 
> 
> 
> 
> 
> #2 and #3 describe valuable functionality for edge computing 
> infrastructure,
> 
> 
> along with motivating use cases. #4 describes the integration of this 
> functionality
> 
> 
> into OpenStack.
> 
> 
> 
> 
> -- Satya
> 
> 
> 
> 
> 
> On Tue, Jan 2, 2018 at 11:40 AM, Csatari, Gergely (Nokia -
> HU/Budapest) < gergely.csatari at nokia.com > wrote:
> 
> 
> 
> Hi,
> 
> Thanks for the links.
> Wow, thats a lots of papers 
> 
> Do you have any suggestion where to start?
> 
> Br,
> Gerg0
> 
> -----Original Message-----
> From: Mahadev Satyanarayanan [mailto: satya at cs.cmu.edu ]
> Sent: Tuesday, December 26, 2017 5:37 PM
> To: edge-computing at lists.openstack.org
> Cc: Allison Randal < allison at lohutok.net >; Csatari, Gergely (Nokia -
> HU/Budapest) < gergely.csatari at nokia.com >
> Subject: Re: [Edge-computing] Upcoming Work Sessions Schedule - Edge
> 
> 
> 
> A better URL, just for edge computing papers, is this:
> http://elijah.cs.cmu.edu/publications.html
> 
> The URL Allison gave also works, but covers all my papers rather than 
> just those on edge computing.
> 
> -- Satya
> 
> 
> On Tuesday 26 December 2017 11:30:36 Allison Randal wrote:
> > On 12/20/2017 05:31 AM, Csatari, Gergely (Nokia - HU/Budapest)
> > wrote:
> > > * User Story 7:
> > > o Can someone provide a reference to Mahadev Satyanarayanan-s 
> > > cloudlet material?
> > 
> > Start here:
> > 
> > https://www.cs.cmu.edu/~satya/satya_papers.html
> > 
> > Especially:
> > 
> > http://www.cs.cmu.edu/%7Esatya/docdir/satya-mobicase2014.pdf
> > 
> > Allison
> > 
> > _______________________________________________
> > Edge-computing mailing list
> > Edge-computing at lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
> > 
> 
> 
> _______________________________________________
> Edge-computing mailing list
> Edge-computing at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
>

_______________________________________________
Edge-computing mailing list
Edge-computing at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing

From gergely.csatari at nokia.com  Fri Jan  5 14:04:17 2018
From: gergely.csatari at nokia.com (Csatari, Gergely (Nokia - HU/Budapest))
Date: Fri, 5 Jan 2018 14:04:17 +0000
Subject: [Edge-computing] : Connectivity (WAS: Upcoming Work Sessions
 Schedule - Edge)
Message-ID: <HE1PR07MB3355E28889AFEB3CF28CA73BE11C0@HE1PR07MB3355.eurprd07.prod.outlook.com>

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 at gmail.com]
Sent: Tuesday, January 2, 2018 6:45 PM
To: Csatari, Gergely (Nokia - HU/Budapest) <gergely.csatari at nokia.com>
Cc: Claire Massey <claire at openstack.org>; edge-computing at 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 at nokia.com<mailto:gergely.csatari at 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 at gmail.com<mailto:suyash.sinha at gmail.com>]
Sent: Friday, December 22, 2017 3:21 PM
To: Csatari, Gergely (Nokia - HU/Budapest) <gergely.csatari at nokia.com<mailto:gergely.csatari at nokia.com>>
Cc: Claire Massey <claire at openstack.org<mailto:claire at openstack.org>>; edge-computing at lists.openstack.org<mailto:edge-computing at 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 at nokia.com<mailto:gergely.csatari at 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 at openstack.org<mailto:claire at openstack.org>>; edge-computing at lists.openstack.org<mailto:edge-computing at 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_existing_gaps

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 at openstack.org]
Sent: Tuesday, December 19, 2017 12:24 AM
To: edge-computing at lists.openstack.org<mailto:edge-computing at 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 at openstack.org<mailto:claire at 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 at openstack.org<mailto:claire at 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 at openstack.org<mailto:claire at 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_Epb4TF57rlOIM1gkd9qvJQ18G9eidjhBS-UHprOzCjA6NSB

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 at openstack.org<mailto:claire at 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 at lists.openstack.org<mailto:Edge-computing at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing

_______________________________________________
Edge-computing mailing list
Edge-computing at lists.openstack.org<mailto:Edge-computing at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing

_______________________________________________
Edge-computing mailing list
Edge-computing at lists.openstack.org<mailto:Edge-computing at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing

_______________________________________________
Edge-computing mailing list
Edge-computing at lists.openstack.org<mailto:Edge-computing at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing


_______________________________________________
Edge-computing mailing list
Edge-computing at lists.openstack.org<mailto:Edge-computing at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing



--
s



--
s
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/edge-computing/attachments/20180105/54b21fcd/attachment-0001.html>

From beth.cohen at verizon.com  Fri Jan  5 14:53:36 2018
From: beth.cohen at verizon.com (beth.cohen at verizon.com)
Date: Fri, 5 Jan 2018 14:53:36 +0000
Subject: [Edge-computing] [E] Re: : Connectivity (WAS: Upcoming Work
 Sessions Schedule - Edge)
In-Reply-To: <HE1PR07MB3355E28889AFEB3CF28CA73BE11C0@HE1PR07MB3355.eurprd07.prod.outlook.com>
References: <HE1PR07MB3355E28889AFEB3CF28CA73BE11C0@HE1PR07MB3355.eurprd07.prod.outlook.com>
Message-ID: <ceda04f7237a426e902b8521aed70fb0@OMZP1LUMXCA08.uswin.ad.vzwcorp.com>

Yes.  That is a common Telco use case!  That is why I am so concerned with making sure that it will work as a “mesh” network, because that is one major use case.


[Verizon]<http://www.verizon.com/>

Beth Cohen
NFV/SDN Network Product Strategy

O +781-466-2055 | M +781-434-8553
beth.cohen at verizon.com<mailto:beth.cohen at verizon.com>

<http://www.facebook.com/verizon>  [Twitter] <http://twitter.com/verizon>   [Instagram] <http://www.instagram.com/verizon>


From: Csatari, Gergely (Nokia - HU/Budapest) [mailto:gergely.csatari at nokia.com]
Sent: Friday, January 05, 2018 9:04 AM
To: Suyash Sinha <suyash.sinha at gmail.com>
Cc: edge-computing at lists.openstack.org
Subject: [E] Re: [Edge-computing] : Connectivity (WAS: Upcoming Work Sessions Schedule - Edge)

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 at gmail.com]
Sent: Tuesday, January 2, 2018 6:45 PM
To: Csatari, Gergely (Nokia - HU/Budapest) <gergely.csatari at nokia.com<mailto:gergely.csatari at nokia.com>>
Cc: Claire Massey <claire at openstack.org<mailto:claire at openstack.org>>; edge-computing at lists.openstack.org<mailto:edge-computing at 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 at nokia.com<mailto:gergely.csatari at 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 at gmail.com<mailto:suyash.sinha at gmail.com>]
Sent: Friday, December 22, 2017 3:21 PM
To: Csatari, Gergely (Nokia - HU/Budapest) <gergely.csatari at nokia.com<mailto:gergely.csatari at nokia.com>>
Cc: Claire Massey <claire at openstack.org<mailto:claire at openstack.org>>; edge-computing at lists.openstack.org<mailto:edge-computing at 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/<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.linkedin.com_pulse_pushing-2Dcloud-2Dedge-2Dsuyash-2Dsinha_&d=DwMGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=zSPYRgoBij7eDdloAJpktY4pyBQRGnvgrz_9Wy3fyA4&m=gX2jwSutgBIfQu2nHHAhjJZa3rYxNUUlPklu-B2Wp10&s=O53ZJHGOhUJlXmCKrhNaPamNSX2kjkltt8_yzCNRjlU&e=>) . 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 at nokia.com<mailto:gergely.csatari at 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://urldefense.proofpoint.com/v2/url?u=https-3A__en.wikipedia.org_wiki_User-5Fstory-23Common-5Ftemplates&d=DwMGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=zSPYRgoBij7eDdloAJpktY4pyBQRGnvgrz_9Wy3fyA4&m=gX2jwSutgBIfQu2nHHAhjJZa3rYxNUUlPklu-B2Wp10&s=NIfeyi9d-8caz65ATde3GIY9WPW-FuG-9hCBmLT_Llo&e=> 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 at openstack.org<mailto:claire at openstack.org>>; edge-computing at lists.openstack.org<mailto:edge-computing at 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_existing_gaps<https://urldefense.proofpoint.com/v2/url?u=https-3A__etherpad.openstack.org_p_2017-5Fedge-5Fcomputing-5Fworking-5Fsessions-5Fexisting-5Fgaps&d=DwMGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=zSPYRgoBij7eDdloAJpktY4pyBQRGnvgrz_9Wy3fyA4&m=gX2jwSutgBIfQu2nHHAhjJZa3rYxNUUlPklu-B2Wp10&s=kE2xubp3axJ_DcZKqj4bJ6ktaWWwF5r3l6V3oYhu6j0&e=>

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 at openstack.org]
Sent: Tuesday, December 19, 2017 12:24 AM
To: edge-computing at lists.openstack.org<mailto:edge-computing at 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<https://urldefense.proofpoint.com/v2/url?u=https-3A__zoom.us_j_777719876&d=DwMGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=zSPYRgoBij7eDdloAJpktY4pyBQRGnvgrz_9Wy3fyA4&m=gX2jwSutgBIfQu2nHHAhjJZa3rYxNUUlPklu-B2Wp10&s=MxhNg6oaywDDK7Fjnjc2d4TQP0Ra29h4dCc0td1-9FU&e=>

On Dec 18, 2017, at 5:12 PM, Claire Massey <claire at openstack.org<mailto:claire at 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<https://urldefense.proofpoint.com/v2/url?u=https-3A__zoom.us_j_777719876&d=DwMGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=zSPYRgoBij7eDdloAJpktY4pyBQRGnvgrz_9Wy3fyA4&m=gX2jwSutgBIfQu2nHHAhjJZa3rYxNUUlPklu-B2Wp10&s=MxhNg6oaywDDK7Fjnjc2d4TQP0Ra29h4dCc0td1-9FU&e=>

Etherpad: : https://etherpad.openstack.org/p/2017_edge_computing_working_sessions<https://urldefense.proofpoint.com/v2/url?u=https-3A__etherpad.openstack.org_p_2017-5Fedge-5Fcomputing-5Fworking-5Fsessions&d=DwMGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=zSPYRgoBij7eDdloAJpktY4pyBQRGnvgrz_9Wy3fyA4&m=gX2jwSutgBIfQu2nHHAhjJZa3rYxNUUlPklu-B2Wp10&s=ntQsUuqblcc5cbBuI3JS2qnKbWj3l6Rdz2fO_YBfi3I&e=>

We look forward to chatting with you all then. Thanks!



On Dec 11, 2017, at 4:31 PM, Claire Massey <claire at openstack.org<mailto:claire at 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<https://urldefense.proofpoint.com/v2/url?u=https-3A__zoom.us_j_777719876&d=DwMGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=zSPYRgoBij7eDdloAJpktY4pyBQRGnvgrz_9Wy3fyA4&m=gX2jwSutgBIfQu2nHHAhjJZa3rYxNUUlPklu-B2Wp10&s=MxhNg6oaywDDK7Fjnjc2d4TQP0Ra29h4dCc0td1-9FU&e=>

Etherpad: : https://etherpad.openstack.org/p/2017_edge_computing_working_sessions<https://urldefense.proofpoint.com/v2/url?u=https-3A__etherpad.openstack.org_p_2017-5Fedge-5Fcomputing-5Fworking-5Fsessions&d=DwMGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=zSPYRgoBij7eDdloAJpktY4pyBQRGnvgrz_9Wy3fyA4&m=gX2jwSutgBIfQu2nHHAhjJZa3rYxNUUlPklu-B2Wp10&s=ntQsUuqblcc5cbBuI3JS2qnKbWj3l6Rdz2fO_YBfi3I&e=>

We look forward to chatting with you all then.

Thanks,
Claire


On Nov 29, 2017, at 12:15 PM, Claire Massey <claire at openstack.org<mailto:claire at 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<https://urldefense.proofpoint.com/v2/url?u=https-3A__etherpad.openstack.org_p_2017-5Fedge-5Fcomputing-5Fworking-5Fsessions&d=DwMGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=zSPYRgoBij7eDdloAJpktY4pyBQRGnvgrz_9Wy3fyA4&m=gX2jwSutgBIfQu2nHHAhjJZa3rYxNUUlPklu-B2Wp10&s=ntQsUuqblcc5cbBuI3JS2qnKbWj3l6Rdz2fO_YBfi3I&e=>
 * Audio recording of the November 28 meeting: https://zoom.us/recording/play/t_XmAP-VK1RRGKhy_Epb4TF57rlOIM1gkd9qvJQ18G9eidjhBS-UHprOzCjA6NSB<https://urldefense.proofpoint.com/v2/url?u=https-3A__zoom.us_recording_play_t-5FXmAP-2DVK1RRGKhy-5FEpb4TF57rlOIM1gkd9qvJQ18G9eidjhBS-2DUHprOzCjA6NSB&d=DwMGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=zSPYRgoBij7eDdloAJpktY4pyBQRGnvgrz_9Wy3fyA4&m=gX2jwSutgBIfQu2nHHAhjJZa3rYxNUUlPklu-B2Wp10&s=wiB1INTtk90DO6DdyqotuCMlURdqEB_MQMg_bYQ5EKc&e=>

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<https://urldefense.proofpoint.com/v2/url?u=https-3A__zoom.us_j_777719876&d=DwMGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=zSPYRgoBij7eDdloAJpktY4pyBQRGnvgrz_9Wy3fyA4&m=gX2jwSutgBIfQu2nHHAhjJZa3rYxNUUlPklu-B2Wp10&s=MxhNg6oaywDDK7Fjnjc2d4TQP0Ra29h4dCc0td1-9FU&e=>.

Thanks,
Claire




On Nov 26, 2017, at 4:15 PM, Claire Massey <claire at openstack.org<mailto:claire at 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<https://urldefense.proofpoint.com/v2/url?u=https-3A__etherpad.openstack.org_p_2017-5Fedge-5Fcomputing-5Fworking-5Fsessions&d=DwMGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=zSPYRgoBij7eDdloAJpktY4pyBQRGnvgrz_9Wy3fyA4&m=gX2jwSutgBIfQu2nHHAhjJZa3rYxNUUlPklu-B2Wp10&s=ntQsUuqblcc5cbBuI3JS2qnKbWj3l6Rdz2fO_YBfi3I&e=>.

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<https://urldefense.proofpoint.com/v2/url?u=https-3A__zoom.us_j_777719876&d=DwMGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=zSPYRgoBij7eDdloAJpktY4pyBQRGnvgrz_9Wy3fyA4&m=gX2jwSutgBIfQu2nHHAhjJZa3rYxNUUlPklu-B2Wp10&s=MxhNg6oaywDDK7Fjnjc2d4TQP0Ra29h4dCc0td1-9FU&e=>

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<https://urldefense.proofpoint.com/v2/url?u=https-3A__zoom.us_zoomconference-3Fm-3DQQS-5FrcoIKkXtIdC-5F0EpVQ80nU8MYS4Y0&d=DwMGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=zSPYRgoBij7eDdloAJpktY4pyBQRGnvgrz_9Wy3fyA4&m=gX2jwSutgBIfQu2nHHAhjJZa3rYxNUUlPklu-B2Wp10&s=C6OTPmHnr6NGC9qgRoZI09qCE1ndd1D3Wg8LQhLSp8M&e=>


****
[0] http://www.opendevconf.com/schedule/<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.opendevconf.com_schedule_&d=DwMGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=zSPYRgoBij7eDdloAJpktY4pyBQRGnvgrz_9Wy3fyA4&m=gX2jwSutgBIfQu2nHHAhjJZa3rYxNUUlPklu-B2Wp10&s=By3uQzo_89zwNniz80L2-KqyNiws_EKJRo1_2D1OfZ4&e=>
[1] https://etherpad.openstack.org/p/OS_Sydney_edge_computing_use_cases<https://urldefense.proofpoint.com/v2/url?u=https-3A__etherpad.openstack.org_p_OS-5FSydney-5Fedge-5Fcomputing-5Fuse-5Fcases&d=DwMGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=zSPYRgoBij7eDdloAJpktY4pyBQRGnvgrz_9Wy3fyA4&m=gX2jwSutgBIfQu2nHHAhjJZa3rYxNUUlPklu-B2Wp10&s=TS6NjY9RyM_r_jOg_fIjSdJDedbToXfRXPEHOBJU3qk&e=>

Thanks,
Claire Massey
_______________________________________________
Edge-computing mailing list
Edge-computing at lists.openstack.org<mailto:Edge-computing at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing<https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_edge-2Dcomputing&d=DwMGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=zSPYRgoBij7eDdloAJpktY4pyBQRGnvgrz_9Wy3fyA4&m=gX2jwSutgBIfQu2nHHAhjJZa3rYxNUUlPklu-B2Wp10&s=r2jWc4JaAaugqSaOwMWmWixXHETyfviEPs-DmXRXcEo&e=>

_______________________________________________
Edge-computing mailing list
Edge-computing at lists.openstack.org<mailto:Edge-computing at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing<https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_edge-2Dcomputing&d=DwMGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=zSPYRgoBij7eDdloAJpktY4pyBQRGnvgrz_9Wy3fyA4&m=gX2jwSutgBIfQu2nHHAhjJZa3rYxNUUlPklu-B2Wp10&s=r2jWc4JaAaugqSaOwMWmWixXHETyfviEPs-DmXRXcEo&e=>

_______________________________________________
Edge-computing mailing list
Edge-computing at lists.openstack.org<mailto:Edge-computing at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing<https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_edge-2Dcomputing&d=DwMGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=zSPYRgoBij7eDdloAJpktY4pyBQRGnvgrz_9Wy3fyA4&m=gX2jwSutgBIfQu2nHHAhjJZa3rYxNUUlPklu-B2Wp10&s=r2jWc4JaAaugqSaOwMWmWixXHETyfviEPs-DmXRXcEo&e=>

_______________________________________________
Edge-computing mailing list
Edge-computing at lists.openstack.org<mailto:Edge-computing at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing<https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_edge-2Dcomputing&d=DwMGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=zSPYRgoBij7eDdloAJpktY4pyBQRGnvgrz_9Wy3fyA4&m=gX2jwSutgBIfQu2nHHAhjJZa3rYxNUUlPklu-B2Wp10&s=r2jWc4JaAaugqSaOwMWmWixXHETyfviEPs-DmXRXcEo&e=>


_______________________________________________
Edge-computing mailing list
Edge-computing at lists.openstack.org<mailto:Edge-computing at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing<https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_edge-2Dcomputing&d=DwMGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=zSPYRgoBij7eDdloAJpktY4pyBQRGnvgrz_9Wy3fyA4&m=gX2jwSutgBIfQu2nHHAhjJZa3rYxNUUlPklu-B2Wp10&s=r2jWc4JaAaugqSaOwMWmWixXHETyfviEPs-DmXRXcEo&e=>



--
s



--
s
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/edge-computing/attachments/20180105/e1a97d74/attachment-0001.html>

From suyash.sinha at gmail.com  Fri Jan  5 16:32:36 2018
From: suyash.sinha at gmail.com (Suyash Sinha)
Date: Fri, 5 Jan 2018 08:32:36 -0800
Subject: [Edge-computing] [E] Re: : Connectivity (WAS: Upcoming Work
 Sessions Schedule - Edge)
In-Reply-To: <ceda04f7237a426e902b8521aed70fb0@OMZP1LUMXCA08.uswin.ad.vzwcorp.com>
References: <HE1PR07MB3355E28889AFEB3CF28CA73BE11C0@HE1PR07MB3355.eurprd07.prod.outlook.com>
 <ceda04f7237a426e902b8521aed70fb0@OMZP1LUMXCA08.uswin.ad.vzwcorp.com>
Message-ID: <CAN9VmJ_ML+LR2ZOTPc3Jy6=ve-jabN_OiFWzyij7GxQ6pp8+Pg@mail.gmail.com>

Yes. This is what I have been seeing as well.

On Jan 5, 2018 6:54 AM, <beth.cohen at verizon.com> wrote:

> Yes.  That is a common Telco use case!  That is why I am so concerned with
> making sure that it will work as a “mesh” network, because that is one
> major use case.
>
>
>
>
> [image: Verizon] <http://www.verizon.com/>
>
> Beth Cohen
> NFV/SDN Network Product Strategy
>
> O +781-466-2055 | M +781-434-8553
> beth.cohen at verizon.com
>
> [image: Facebook] <http://www.facebook.com/verizon>  [image: Twitter]
> <http://twitter.com/verizon>  [image: Instagram]
> <http://www.instagram.com/verizon>
>
>
>
> *From:* Csatari, Gergely (Nokia - HU/Budapest) [mailto:
> gergely.csatari at nokia.com]
> *Sent:* Friday, January 05, 2018 9:04 AM
> *To:* Suyash Sinha <suyash.sinha at gmail.com>
> *Cc:* edge-computing at lists.openstack.org
> *Subject:* [E] Re: [Edge-computing] : Connectivity (WAS: Upcoming Work
> Sessions Schedule - Edge)
>
>
>
> 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 at gmail.com
> <suyash.sinha at gmail.com>]
> *Sent:* Tuesday, January 2, 2018 6:45 PM
> *To:* Csatari, Gergely (Nokia - HU/Budapest) <gergely.csatari at nokia.com>
> *Cc:* Claire Massey <claire at openstack.org>; edge-computing at 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 at 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 at gmail.com]
> *Sent:* Friday, December 22, 2017 3:21 PM
> *To:* Csatari, Gergely (Nokia - HU/Budapest) <gergely.csatari at nokia.com>
> *Cc:* Claire Massey <claire at openstack.org>; edge-computing at 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/
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.linkedin.com_pulse_pushing-2Dcloud-2Dedge-2Dsuyash-2Dsinha_&d=DwMGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=zSPYRgoBij7eDdloAJpktY4pyBQRGnvgrz_9Wy3fyA4&m=gX2jwSutgBIfQu2nHHAhjJZa3rYxNUUlPklu-B2Wp10&s=O53ZJHGOhUJlXmCKrhNaPamNSX2kjkltt8_yzCNRjlU&e=>)
> . 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 at 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://urldefense.proofpoint.com/v2/url?u=https-3A__en.wikipedia.org_wiki_User-5Fstory-23Common-5Ftemplates&d=DwMGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=zSPYRgoBij7eDdloAJpktY4pyBQRGnvgrz_9Wy3fyA4&m=gX2jwSutgBIfQu2nHHAhjJZa3rYxNUUlPklu-B2Wp10&s=NIfeyi9d-8caz65ATde3GIY9WPW-FuG-9hCBmLT_Llo&e=>
>    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 at openstack.org>; edge-computing at 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_existing_gaps
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__etherpad.openstack.org_p_2017-5Fedge-5Fcomputing-5Fworking-5Fsessions-5Fexisting-5Fgaps&d=DwMGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=zSPYRgoBij7eDdloAJpktY4pyBQRGnvgrz_9Wy3fyA4&m=gX2jwSutgBIfQu2nHHAhjJZa3rYxNUUlPklu-B2Wp10&s=kE2xubp3axJ_DcZKqj4bJ6ktaWWwF5r3l6V3oYhu6j0&e=>
>
>
>
> 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 at openstack.org <claire at openstack.org>]
>
> *Sent:* Tuesday, December 19, 2017 12:24 AM
> *To:* edge-computing at 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
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__zoom.us_j_777719876&d=DwMGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=zSPYRgoBij7eDdloAJpktY4pyBQRGnvgrz_9Wy3fyA4&m=gX2jwSutgBIfQu2nHHAhjJZa3rYxNUUlPklu-B2Wp10&s=MxhNg6oaywDDK7Fjnjc2d4TQP0Ra29h4dCc0td1-9FU&e=>
>
>
>
> On Dec 18, 2017, at 5:12 PM, Claire Massey <claire at 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
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__zoom.us_j_777719876&d=DwMGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=zSPYRgoBij7eDdloAJpktY4pyBQRGnvgrz_9Wy3fyA4&m=gX2jwSutgBIfQu2nHHAhjJZa3rYxNUUlPklu-B2Wp10&s=MxhNg6oaywDDK7Fjnjc2d4TQP0Ra29h4dCc0td1-9FU&e=>
>
>
>
> Etherpad: : https://etherpad.openstack.org/p/2017_edge_
> computing_working_sessions
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__etherpad.openstack.org_p_2017-5Fedge-5Fcomputing-5Fworking-5Fsessions&d=DwMGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=zSPYRgoBij7eDdloAJpktY4pyBQRGnvgrz_9Wy3fyA4&m=gX2jwSutgBIfQu2nHHAhjJZa3rYxNUUlPklu-B2Wp10&s=ntQsUuqblcc5cbBuI3JS2qnKbWj3l6Rdz2fO_YBfi3I&e=>
>
>
>
> We look forward to chatting with you all then. Thanks!
>
>
>
>
>
>
>
> On Dec 11, 2017, at 4:31 PM, Claire Massey <claire at 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
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__zoom.us_j_777719876&d=DwMGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=zSPYRgoBij7eDdloAJpktY4pyBQRGnvgrz_9Wy3fyA4&m=gX2jwSutgBIfQu2nHHAhjJZa3rYxNUUlPklu-B2Wp10&s=MxhNg6oaywDDK7Fjnjc2d4TQP0Ra29h4dCc0td1-9FU&e=>
>
>
>
> Etherpad: : https://etherpad.openstack.org/p/2017_edge_
> computing_working_sessions
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__etherpad.openstack.org_p_2017-5Fedge-5Fcomputing-5Fworking-5Fsessions&d=DwMGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=zSPYRgoBij7eDdloAJpktY4pyBQRGnvgrz_9Wy3fyA4&m=gX2jwSutgBIfQu2nHHAhjJZa3rYxNUUlPklu-B2Wp10&s=ntQsUuqblcc5cbBuI3JS2qnKbWj3l6Rdz2fO_YBfi3I&e=>
>
>
>
> We look forward to chatting with you all then.
>
>
>
> Thanks,
>
> Claire
>
>
>
>
>
> On Nov 29, 2017, at 12:15 PM, Claire Massey <claire at 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
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__etherpad.openstack.org_p_2017-5Fedge-5Fcomputing-5Fworking-5Fsessions&d=DwMGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=zSPYRgoBij7eDdloAJpktY4pyBQRGnvgrz_9Wy3fyA4&m=gX2jwSutgBIfQu2nHHAhjJZa3rYxNUUlPklu-B2Wp10&s=ntQsUuqblcc5cbBuI3JS2qnKbWj3l6Rdz2fO_YBfi3I&e=>
>
>  * Audio recording of the November 28 meeting: https://zoom.us/
> recording/play/t_XmAP-VK1RRGKhy_Epb4TF57rlOIM1gkd9qvJQ18G9eidj
> hBS-UHprOzCjA6NSB
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__zoom.us_recording_play_t-5FXmAP-2DVK1RRGKhy-5FEpb4TF57rlOIM1gkd9qvJQ18G9eidjhBS-2DUHprOzCjA6NSB&d=DwMGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=zSPYRgoBij7eDdloAJpktY4pyBQRGnvgrz_9Wy3fyA4&m=gX2jwSutgBIfQu2nHHAhjJZa3rYxNUUlPklu-B2Wp10&s=wiB1INTtk90DO6DdyqotuCMlURdqEB_MQMg_bYQ5EKc&e=>
>
>
>
> 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
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__zoom.us_j_777719876&d=DwMGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=zSPYRgoBij7eDdloAJpktY4pyBQRGnvgrz_9Wy3fyA4&m=gX2jwSutgBIfQu2nHHAhjJZa3rYxNUUlPklu-B2Wp10&s=MxhNg6oaywDDK7Fjnjc2d4TQP0Ra29h4dCc0td1-9FU&e=>
> .
>
>
>
> Thanks,
>
> Claire
>
>
>
>
>
>
>
>
>
> On Nov 26, 2017, at 4:15 PM, Claire Massey <claire at 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
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__etherpad.openstack.org_p_2017-5Fedge-5Fcomputing-5Fworking-5Fsessions&d=DwMGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=zSPYRgoBij7eDdloAJpktY4pyBQRGnvgrz_9Wy3fyA4&m=gX2jwSutgBIfQu2nHHAhjJZa3rYxNUUlPklu-B2Wp10&s=ntQsUuqblcc5cbBuI3JS2qnKbWj3l6Rdz2fO_YBfi3I&e=>
> .
>
>
>
> 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
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__zoom.us_j_777719876&d=DwMGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=zSPYRgoBij7eDdloAJpktY4pyBQRGnvgrz_9Wy3fyA4&m=gX2jwSutgBIfQu2nHHAhjJZa3rYxNUUlPklu-B2Wp10&s=MxhNg6oaywDDK7Fjnjc2d4TQP0Ra29h4dCc0td1-9FU&e=>
>
>
>
> Or Telephone:
>
>         US: +1 646 876 9923 <(646)%20876-9923>  or +1 669 900 6833
> <(669)%20900-6833>  or +1 408 638 0968 <(408)%20638-0968>
>
>         Meeting ID: 777 719 876
>
>
>
> International numbers available: https://zoom.us/zoomconference?m=QQS_
> rcoIKkXtIdC_0EpVQ80nU8MYS4Y0
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__zoom.us_zoomconference-3Fm-3DQQS-5FrcoIKkXtIdC-5F0EpVQ80nU8MYS4Y0&d=DwMGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=zSPYRgoBij7eDdloAJpktY4pyBQRGnvgrz_9Wy3fyA4&m=gX2jwSutgBIfQu2nHHAhjJZa3rYxNUUlPklu-B2Wp10&s=C6OTPmHnr6NGC9qgRoZI09qCE1ndd1D3Wg8LQhLSp8M&e=>
>
>
>
>
>
> ****
>
> [0] http://www.opendevconf.com/schedule/
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.opendevconf.com_schedule_&d=DwMGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=zSPYRgoBij7eDdloAJpktY4pyBQRGnvgrz_9Wy3fyA4&m=gX2jwSutgBIfQu2nHHAhjJZa3rYxNUUlPklu-B2Wp10&s=By3uQzo_89zwNniz80L2-KqyNiws_EKJRo1_2D1OfZ4&e=>
>
> [1] https://etherpad.openstack.org/p/OS_Sydney_edge_computing_use_cases
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__etherpad.openstack.org_p_OS-5FSydney-5Fedge-5Fcomputing-5Fuse-5Fcases&d=DwMGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=zSPYRgoBij7eDdloAJpktY4pyBQRGnvgrz_9Wy3fyA4&m=gX2jwSutgBIfQu2nHHAhjJZa3rYxNUUlPklu-B2Wp10&s=TS6NjY9RyM_r_jOg_fIjSdJDedbToXfRXPEHOBJU3qk&e=>
>
>
>
> Thanks,
>
> Claire Massey
>
> _______________________________________________
> Edge-computing mailing list
> Edge-computing at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_edge-2Dcomputing&d=DwMGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=zSPYRgoBij7eDdloAJpktY4pyBQRGnvgrz_9Wy3fyA4&m=gX2jwSutgBIfQu2nHHAhjJZa3rYxNUUlPklu-B2Wp10&s=r2jWc4JaAaugqSaOwMWmWixXHETyfviEPs-DmXRXcEo&e=>
>
>
>
> _______________________________________________
> Edge-computing mailing list
> Edge-computing at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_edge-2Dcomputing&d=DwMGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=zSPYRgoBij7eDdloAJpktY4pyBQRGnvgrz_9Wy3fyA4&m=gX2jwSutgBIfQu2nHHAhjJZa3rYxNUUlPklu-B2Wp10&s=r2jWc4JaAaugqSaOwMWmWixXHETyfviEPs-DmXRXcEo&e=>
>
>
>
> _______________________________________________
> Edge-computing mailing list
> Edge-computing at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_edge-2Dcomputing&d=DwMGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=zSPYRgoBij7eDdloAJpktY4pyBQRGnvgrz_9Wy3fyA4&m=gX2jwSutgBIfQu2nHHAhjJZa3rYxNUUlPklu-B2Wp10&s=r2jWc4JaAaugqSaOwMWmWixXHETyfviEPs-DmXRXcEo&e=>
>
>
>
> _______________________________________________
> Edge-computing mailing list
> Edge-computing at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_edge-2Dcomputing&d=DwMGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=zSPYRgoBij7eDdloAJpktY4pyBQRGnvgrz_9Wy3fyA4&m=gX2jwSutgBIfQu2nHHAhjJZa3rYxNUUlPklu-B2Wp10&s=r2jWc4JaAaugqSaOwMWmWixXHETyfviEPs-DmXRXcEo&e=>
>
>
>
>
> _______________________________________________
> Edge-computing mailing list
> Edge-computing at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_edge-2Dcomputing&d=DwMGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=zSPYRgoBij7eDdloAJpktY4pyBQRGnvgrz_9Wy3fyA4&m=gX2jwSutgBIfQu2nHHAhjJZa3rYxNUUlPklu-B2Wp10&s=r2jWc4JaAaugqSaOwMWmWixXHETyfviEPs-DmXRXcEo&e=>
>
>
>
>
>
> --
>
> s
>
>
>
>
>
> --
>
> s
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/edge-computing/attachments/20180105/24dd0ae2/attachment-0001.html>

From lebre.adrien at free.fr  Fri Jan  5 23:48:17 2018
From: lebre.adrien at free.fr (lebre.adrien at free.fr)
Date: Sat, 6 Jan 2018 00:48:17 +0100 (CET)
Subject: [Edge-computing] LTE scenario
In-Reply-To: <CAN9VmJ_ML+LR2ZOTPc3Jy6=ve-jabN_OiFWzyij7GxQ6pp8+Pg@mail.gmail.com>
Message-ID: <1662053125.277038158.1515196097378.JavaMail.root@zimbra29-e5>

Hi, 

Could someone elaborate a bit more on such a use-case (in the user stories etherpad if possible [1])? 
It looks at least from my side,  to be an advanced scenario. Advanced in the sense that it increases  the number of challenges to deal with significantly.  

Diving into the detail, there are some points that are unclear from my side with such a LTE use-case. 
If I consider that a cloudlet is a edge site and if this edge site is operated by a telco, I guess the IP
of this edge site will not be so dynamic? 
Moreover, by using a Dynamic DNS approach,  it can be rather ok to find how interacting with this edge site. I'm not sure I'm seeing the issue here. 

Maybe, the performance of the LTE connection will be the major issue in particular if we have to administrate and use the edge site remotely. For instance if you want provision any kind of VM, then dedicated mechanisms have to be designed to prefetch the VM image from a remote repo to this edge site. 
There are academic proposals (e.g., see the previous publications that have been pointed by Satya for instance) but those solutions require to have at least a few templates/backing files already available in the edge site.  
If you expect to have a VM image repository available on this ``LTE'' edge site, are you considering to be able to provision/relocate/migrate a VM from that site to another one? In such a case, dedicated mechanisms are mandatory to deal with all data mouvements related to this relocation between the edge sites !? Here there are also academics proposals but they have specific requirements.

[1] https://etherpad.openstack.org/p/2017_edge_computing_working_sessions_existing_gaps

----- Mail original -----
> De: "Suyash Sinha" <suyash.sinha at gmail.com>
> À: "beth cohen" <beth.cohen at verizon.com>
> Cc: edge-computing at lists.openstack.org
> Envoyé: Vendredi 5 Janvier 2018 17:32:36
> Objet: Re: [Edge-computing] [E] Re: : Connectivity (WAS: Upcoming Work Sessions Schedule - Edge)
> 
> 
> 
> Yes. This is what I have been seeing as well.
> 
> 
> On Jan 5, 2018 6:54 AM, < beth.cohen at verizon.com > wrote:
> 
> 
> 
> 
> 
> 
> Yes. That is a common Telco use case! That is why I am so concerned
> with making sure that it will work as a “mesh” network, because that
> is one major use case.
> 
> 
> 
> 
> 
> Verizon
> 
> Beth Cohen
> NFV/SDN Network Product Strategy
> 
> O +781-466-2055 | M +781-434-8553
> beth.cohen at verizon.com
> 
> FacebookTwitterInstagram
> 
> 
> 
> 
> 
> 
> 
> From: Csatari, Gergely (Nokia - HU/Budapest) [mailto:
> gergely.csatari at nokia.com ]
> Sent: Friday, January 05, 2018 9:04 AM
> To: Suyash Sinha < suyash.sinha at gmail.com >
> Cc: edge-computing at lists.openstack.org
> Subject: [E] Re: [Edge-computing] : Connectivity (WAS: Upcoming Work
> Sessions Schedule - Edge)
> 
> 
> 
> 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 at gmail.com ]
> Sent: Tuesday, January 2, 2018 6:45 PM
> To: Csatari, Gergely (Nokia - HU/Budapest) <
> gergely.csatari at nokia.com >
> Cc: Claire Massey < claire at openstack.org >;
> edge-computing at 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 at 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 at gmail.com ]
> Sent: Friday, December 22, 2017 3:21 PM
> To: Csatari, Gergely (Nokia - HU/Budapest) <
> gergely.csatari at nokia.com >
> Cc: Claire Massey < claire at openstack.org >;
> edge-computing at 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 at 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 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 at openstack.org >;
> edge-computing at 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_existing_gaps
> 
> 
> 
> 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 at openstack.org ]
> Sent: Tuesday, December 19, 2017 12:24 AM
> To: edge-computing at 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 at 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 at 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 at 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_Epb4TF57rlOIM1gkd9qvJQ18G9eidjhBS-UHprOzCjA6NSB
> 
> 
> 
> 
> 
> 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 at 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 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/
> 
> 
> [1]
> https://etherpad.openstack.org/p/OS_Sydney_edge_computing_use_cases
> 
> 
> 
> 
> 
> Thanks,
> 
> 
> Claire Massey
> 
> _______________________________________________
> Edge-computing mailing list
> Edge-computing at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
> 
> 
> 
> _______________________________________________
> Edge-computing mailing list
> Edge-computing at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
> 
> 
> 
> _______________________________________________
> Edge-computing mailing list
> Edge-computing at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
> 
> 
> 
> _______________________________________________
> Edge-computing mailing list
> Edge-computing at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
> 
> 
> 
> 
> _______________________________________________
> Edge-computing mailing list
> Edge-computing at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
> 
> 
> 
> 
> 
> 
> 
> 
> --
> 
> 
> 
> 
> 
> s
> 
> 
> 
> 
> 
> 
> 
> 
> --
> 
> 
> 
> 
> 
> s
> _______________________________________________
> Edge-computing mailing list
> Edge-computing at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
>


From lebre.adrien at free.fr  Fri Jan  5 23:53:46 2018
From: lebre.adrien at free.fr (lebre.adrien at free.fr)
Date: Sat, 6 Jan 2018 00:53:46 +0100 (CET)
Subject: [Edge-computing] Classifying edge-site scenarios / Identifying
	expected features
In-Reply-To: <543291377.277041136.1515196214166.JavaMail.root@zimbra29-e5>
Message-ID: <1766448670.277045684.1515196426206.JavaMail.root@zimbra29-e5>

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_


From gergely.csatari at nokia.com  Mon Jan  8 09:49:19 2018
From: gergely.csatari at nokia.com (Csatari, Gergely (Nokia - HU/Budapest))
Date: Mon, 8 Jan 2018 09:49:19 +0000
Subject: [Edge-computing] User stories clarification
Message-ID: <VI1PR07MB332550453102D90FE1CC6EEAE1130@VI1PR07MB3325.eurprd07.prod.outlook.com>

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_existing_gaps
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/edge-computing/attachments/20180108/ce54e566/attachment-0001.html>

From claire at openstack.org  Mon Jan  8 16:48:11 2018
From: claire at openstack.org (Claire Massey)
Date: Mon, 8 Jan 2018 10:48:11 -0600
Subject: [Edge-computing] 2018 Work Sessions Schedule - Edge
In-Reply-To: <9E09BA98-7BEA-4871-9586-8A0CE1859301@openstack.org>
References: <65B731CF-65C7-47C0-997C-0C5B21C204DE@openstack.org>
 <A2E5AD7F-8373-45ED-8866-287E029E438C@openstack.org>
 <A10E0283-34D5-4338-B996-8CAD529AF2AB@openstack.org>
 <C52DFBA7-6633-430B-83B0-811607511286@openstack.org>
 <76CAF51A-F83B-4CC0-B577-3706D25CD319@openstack.org>
 <HE1PR07MB3355F223FC193344DEDDD7A9E10F0@HE1PR07MB3355.eurprd07.prod.outlook.com>
 <9E09BA98-7BEA-4871-9586-8A0CE1859301@openstack.org>
Message-ID: <999D630B-89A0-4FA7-BEC7-9E1B00446A3C@openstack.org>

HI All,

Friendly reminder that starting tomorrow we will pick back up the weekly Edge Work Session calls - happening every Tuesday at 9:00am CST.  We have standing calls scheduled January 9 through February 20, leading up to the PTG. 

 * Dial-in: https://zoom.us/j/777719876 <https://zoom.us/j/777719876>
 * Notes: https://etherpad.openstack.org/p/2017_edge_computing_working_sessions <https://etherpad.openstack.org/p/2017_edge_computing_working_sessions>

Please join us.

Thanks,
Claire


> On Dec 19, 2017, at 10:36 AM, Claire Massey <claire at openstack.org> wrote:
> 
> Hi everyone,
> 
> Thanks to those who have been participating in our weekly Edge Working Session calls. It’s been a productive few weeks!
> 
> If you missed the calls, you can review the notes, recordings and other helpful links from those discussions here: https://etherpad.openstack.org/p/2017_edge_computing_working_sessions <https://etherpad.openstack.org/p/2017_edge_computing_working_sessions>.
> 
> We’re taking a break for the next few weeks but will pick up the regular call schedule again on Tuesdays at 9:00am CST running January 9 - February 20. I’ll circle back with reminders then.
> 
> Happy holidays!
> 
> Cheers,
> Claire
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/edge-computing/attachments/20180108/89906d6b/attachment.html>

From pvaanane at redhat.com  Tue Jan  9 18:48:36 2018
From: pvaanane at redhat.com (Pasi Vaananen)
Date: Tue, 9 Jan 2018 13:48:36 -0500
Subject: [Edge-computing] Classifying edge-site scenarios / Identifying
 expected features
In-Reply-To: <1766448670.277045684.1515196426206.JavaMail.root@zimbra29-e5>
References: <1766448670.277045684.1515196426206.JavaMail.root@zimbra29-e5>
Message-ID: <cae6e197-3c23-45c4-1c03-2f67db4dafe2@redhat.com>

We should probably focus more on defining the connectivity
characteristics between the associated entities between the edge
entities to make progress here. We could start discussion of the network
connectivity at high level as "black box" representation of the network
focusing on the latency, bandwith, drop rates, attachment redundancy,
maximum un-availability etc. characteristics in the context of various
specific use cases and/or connectivity constraints. These parameters can
vary widely depending on the specific deployment scenarios.

It is also possible to have connectivity from the e.g. "thick" vCPE edge
instance located in customer customer premises that has heterogenous
connectivity - to use the "LTE" example below, you can have a box that
has a single wired (say ethernet) connectivity that is used normally,
and wireless LTE connectivity that is used when the main connection
fails, but has dissimilar bandwith, latency etc. characteristics.

Also, top level separation should perhaps be at higher level constructs
at this early stage, e.g. "mobile" 4G/LTE...5G/eMBB/URULL/...,
"wireless" (802 stuff), "satellite", "wireline" (ptp fiber, xPON, Cable,
xDSL/g.fast, ...) rather than getting to technology specifics
(characteristics of connectivity vary a lot depending on the tech.).

So far it seems to me that there is not yet sufficient focus on the
cases for "edge" locations that are within the network, such as cell
sites, V/CRAN aggregation sites, COs, metro locations etc. - esp. 5G
vRAN edge has already three tiers of sites on many plans (i.e. radio
sites, distributed aggregation sites w/ low-latency connections to radio
sites and central sites, which all should be in the scope of the "edge").

Pasi 


On 01/05/2018 06:53 PM, lebre.adrien at free.fr wrote:
> 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_
>
> _______________________________________________
> Edge-computing mailing list
> Edge-computing at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing



From allison at lohutok.net  Tue Jan  9 23:00:08 2018
From: allison at lohutok.net (Allison Randal)
Date: Tue, 9 Jan 2018 18:00:08 -0500
Subject: [Edge-computing] Classifying edge-site scenarios / Identifying
 expected features
In-Reply-To: <1766448670.277045684.1515196426206.JavaMail.root@zimbra29-e5>
References: <1766448670.277045684.1515196426206.JavaMail.root@zimbra29-e5>
Message-ID: <25bb9633-7fb2-375e-7888-4a7174bbf075@lohutok.net>

Following up on the conversation in the call today, have folks on the
list read "My VM is Lighter (and Safer) than your Container"[0]? It's a
good example of the kind of work we could do now on OpenStack, if we
select a small number of representative use cases/scenarios, build
sample deployments, and share concrete data with developers on specific
changes we need in OpenStack. This kind of work can be ongoing at the
same time as higher-level and broader-scope conversations about areas
where we're still unsure of the best architecture or implementation details.

Allison

[0] Filipe Manco, Costin Lupu, Florian Schmidt, Jose Mendes, Simon
Kuenzer, Sumit Sati, Kenichi Yasukata, Costin Raiciu, and Felipe Huici
(2017) "My VM is Lighter (and Safer) than your Container." In
Proceedings of the 26th Symposium on Operating Systems Principles (SOSP
'17). ACM, New York, NY, USA, 218-233. DOI:
https://doi.org/10.1145/3132747.3132763, Also available at:
http://cnp.neclab.eu/projects/lightvm/lightvm.pdf

On 01/05/2018 06:53 PM, lebre.adrien at free.fr wrote:
> 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_
> 
> _______________________________________________
> Edge-computing mailing list
> Edge-computing at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
> 


From paul-andre.raymond at b-yond.com  Wed Jan 10 03:38:44 2018
From: paul-andre.raymond at b-yond.com (Paul-Andre Raymond)
Date: Wed, 10 Jan 2018 03:38:44 +0000
Subject: [Edge-computing] Classifying edge-site scenarios / Identifying
 expected features
In-Reply-To: <25bb9633-7fb2-375e-7888-4a7174bbf075@lohutok.net>
References: <1766448670.277045684.1515196426206.JavaMail.root@zimbra29-e5>
 <25bb9633-7fb2-375e-7888-4a7174bbf075@lohutok.net>
Message-ID: <405A359D-DE00-46EE-8EBD-C34B0A013197@b-yond.com>

Allison, 

Thanks for sharing. I was not aware of this work and I found the article interesting.
Today we discussed two aspects:
1- How to make openstack fit into smaller footprint (i.e. into an edge site)
2- How to make openstack more distributed (with Compute nodes at edge sites connected via a WAN link)

This article certainly fits in the first category. 
In particular, if we think about deploying Openstack components in Unikernels instead of deploying them with Containers.

 
Paul-André
--
 

On 1/9/18, 6:00 PM, "Allison Randal" <allison at lohutok.net> wrote:

    Following up on the conversation in the call today, have folks on the
    list read "My VM is Lighter (and Safer) than your Container"[0]? It's a
    good example of the kind of work we could do now on OpenStack, if we
    select a small number of representative use cases/scenarios, build
    sample deployments, and share concrete data with developers on specific
    changes we need in OpenStack. This kind of work can be ongoing at the
    same time as higher-level and broader-scope conversations about areas
    where we're still unsure of the best architecture or implementation details.
    
    Allison
    
    [0] Filipe Manco, Costin Lupu, Florian Schmidt, Jose Mendes, Simon
    Kuenzer, Sumit Sati, Kenichi Yasukata, Costin Raiciu, and Felipe Huici
    (2017) "My VM is Lighter (and Safer) than your Container." In
    Proceedings of the 26th Symposium on Operating Systems Principles (SOSP
    '17). ACM, New York, NY, USA, 218-233. DOI:
    https://doi.org/10.1145/3132747.3132763, Also available at:
    http://cnp.neclab.eu/projects/lightvm/lightvm.pdf
    
    On 01/05/2018 06:53 PM, lebre.adrien at free.fr wrote:
    > 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_
    > 
    > _______________________________________________
    > Edge-computing mailing list
    > Edge-computing at lists.openstack.org
    > http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
    > 
    
    _______________________________________________
    Edge-computing mailing list
    Edge-computing at lists.openstack.org
    http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
    


From Hyde at redhat.com  Wed Jan 10 04:20:07 2018
From: Hyde at redhat.com (Hyde SUGIYAMA)
Date: Wed, 10 Jan 2018 13:20:07 +0900
Subject: [Edge-computing] Classifying edge-site scenarios / Identifying
 expected features
In-Reply-To: <cae6e197-3c23-45c4-1c03-2f67db4dafe2@redhat.com>
References: <1766448670.277045684.1515196426206.JavaMail.root@zimbra29-e5>
 <cae6e197-3c23-45c4-1c03-2f67db4dafe2@redhat.com>
Message-ID: <CABxuFYkfnmfQQ233TZ8BVwUTx3CDibcKwodGCGJ9EyBq=qO4Pw@mail.gmail.com>

Hi,



I agree with you when we classify edge-site scenarios.   Also we need to
understand applicability of edge computing use case (not NFV use case we
already know) at each type of edge-site.

According to the following 5G Automotive Association’s WP(p11),  “A typical
challenge in IoV is the big data processing and storage resulting from a
huge and growing number of sensors in smart/connected vehicles and roads.
This, in turn, requires new services platforms with powerful processing and
computing resources, low cost and trusted storage, and real-time
communication capabilities. MEC appears as a promising opportunity to
migrate Cloud resources closer to the vehicles and the data sources and
hence save network resources and reduce the latency. “

http://5gaa.org/news/toward-fully-connected-vehicles-edge-computing-for-advanced-automotive-communications/



How can OpenStack Edge Computing help Automotive industry?


-Hyde


2018-01-10 3:48 GMT+09:00 Pasi Vaananen <pvaanane at redhat.com>:

> We should probably focus more on defining the connectivity
> characteristics between the associated entities between the edge
> entities to make progress here. We could start discussion of the network
> connectivity at high level as "black box" representation of the network
> focusing on the latency, bandwith, drop rates, attachment redundancy,
> maximum un-availability etc. characteristics in the context of various
> specific use cases and/or connectivity constraints. These parameters can
> vary widely depending on the specific deployment scenarios.
>
> It is also possible to have connectivity from the e.g. "thick" vCPE edge
> instance located in customer customer premises that has heterogenous
> connectivity - to use the "LTE" example below, you can have a box that
> has a single wired (say ethernet) connectivity that is used normally,
> and wireless LTE connectivity that is used when the main connection
> fails, but has dissimilar bandwith, latency etc. characteristics.
>
> Also, top level separation should perhaps be at higher level constructs
> at this early stage, e.g. "mobile" 4G/LTE...5G/eMBB/URULL/...,
> "wireless" (802 stuff), "satellite", "wireline" (ptp fiber, xPON, Cable,
> xDSL/g.fast, ...) rather than getting to technology specifics
> (characteristics of connectivity vary a lot depending on the tech.).
>
> So far it seems to me that there is not yet sufficient focus on the
> cases for "edge" locations that are within the network, such as cell
> sites, V/CRAN aggregation sites, COs, metro locations etc. - esp. 5G
> vRAN edge has already three tiers of sites on many plans (i.e. radio
> sites, distributed aggregation sites w/ low-latency connections to radio
> sites and central sites, which all should be in the scope of the "edge").
>
> Pasi
>
>
> On 01/05/2018 06:53 PM, lebre.adrien at free.fr wrote:
> > 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_
> >
> > _______________________________________________
> > Edge-computing mailing list
> > Edge-computing at lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
>
>
> _______________________________________________
> Edge-computing mailing list
> Edge-computing at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/edge-computing/attachments/20180110/11227841/attachment-0001.html>

From satya at cs.cmu.edu  Wed Jan 10 12:34:43 2018
From: satya at cs.cmu.edu (Mahadev Satyanarayanan)
Date: Wed, 10 Jan 2018 07:34:43 -0500
Subject: [Edge-computing] Classifying edge-site scenarios / Identifying
	expected features
In-Reply-To: <405A359D-DE00-46EE-8EBD-C34B0A013197@b-yond.com>
References: <1766448670.277045684.1515196426206.JavaMail.root@zimbra29-e5>
 <25bb9633-7fb2-375e-7888-4a7174bbf075@lohutok.net>
 <405A359D-DE00-46EE-8EBD-C34B0A013197@b-yond.com>
Message-ID: <201801100734.43218.satya@cs.cmu.edu>

On Tuesday 09 January 2018 22:38:44 Paul-Andre Raymond wrote:
> 2- How to make openstack more distributed (with Compute nodes at edge sites connected via a WAN link)

One key capability  for this is VM Handoff over WAN links.  Essentially "live migration" of VMs across cloudlets outside
the data center.    We have extended OpenStack to do this.  See cmusatyalab/elijah-openstack on github
and this description of how it works: http://elijah.cs.cmu.edu/DOCS/ha-sec2017.pdf

  -- Satya


From satya at cs.cmu.edu  Wed Jan 10 12:40:49 2018
From: satya at cs.cmu.edu (Mahadev Satyanarayanan)
Date: Wed, 10 Jan 2018 07:40:49 -0500
Subject: [Edge-computing] Classifying edge-site scenarios / Identifying
	expected features
In-Reply-To: <CABxuFYkfnmfQQ233TZ8BVwUTx3CDibcKwodGCGJ9EyBq=qO4Pw@mail.gmail.com>
References: <1766448670.277045684.1515196426206.JavaMail.root@zimbra29-e5>
 <cae6e197-3c23-45c4-1c03-2f67db4dafe2@redhat.com>
 <CABxuFYkfnmfQQ233TZ8BVwUTx3CDibcKwodGCGJ9EyBq=qO4Pw@mail.gmail.com>
Message-ID: <201801100740.49331.satya@cs.cmu.edu>

On Tuesday 09 January 2018 23:20:07 Hyde SUGIYAMA wrote:
> How can OpenStack Edge Computing help Automotive industry?

A key insight is that "edge" has to mean inside the vehicle, not only
at cell tower or close to it.  In other words, every vehicle should have
a substantial on-board cloudlet.   See these two references on why:
 - http://elijah.cs.cmu.edu/DOCS/hu-livemap2017.pdf
 - http://elijah.cs.cmu.edu/DOCS/satya-lanman2017.pdf

Edge-enabled OpenStack in every vehicle?

              -- Satya



From allison at lohutok.net  Wed Jan 10 14:17:52 2018
From: allison at lohutok.net (Allison Randal)
Date: Wed, 10 Jan 2018 09:17:52 -0500
Subject: [Edge-computing] Classifying edge-site scenarios / Identifying
 expected features
In-Reply-To: <405A359D-DE00-46EE-8EBD-C34B0A013197@b-yond.com>
References: <1766448670.277045684.1515196426206.JavaMail.root@zimbra29-e5>
 <25bb9633-7fb2-375e-7888-4a7174bbf075@lohutok.net>
 <405A359D-DE00-46EE-8EBD-C34B0A013197@b-yond.com>
Message-ID: <9580d4d4-0af4-7660-02da-3038edd3b296@lohutok.net>

The typical pattern for unikernels is to deploy the application
workloads as unikernels rather than as containers or VM/cloud images. (I
also pondered the possibility of trying the OpenStack services deployed
as unikernels, as I read the article, but that was more idle curiosity,
since it wouldn't buy us much in an edge scenario.)

I also wasn't suggesting directly trying the LightVM implementation in
OpenStack, since it's mostly a proof-of-concept at the moment. (Though
I'll be interested to see where they go with it.)

Mainly, I was suggesting that their workflow for performance analysis
and optimization of Xen is a good example of what we could do with
OpenStack Edge deployments, once we've defined a small set of
representative edge-site scenarios. That performance analysis workflow
applies equally well to either the small-footprint or distributed
approach to using OpenStack for edge infrastructure, you just have to
use a more distributed set of performance analysis tools for the
distributed case.

Allison

On 01/09/2018 10:38 PM, Paul-Andre Raymond wrote:
> Allison, 
> 
> Thanks for sharing. I was not aware of this work and I found the article interesting.
> Today we discussed two aspects:
> 1- How to make openstack fit into smaller footprint (i.e. into an edge site)
> 2- How to make openstack more distributed (with Compute nodes at edge sites connected via a WAN link)
> 
> This article certainly fits in the first category. 
> In particular, if we think about deploying Openstack components in Unikernels instead of deploying them with Containers.
> 
>  
> Paul-André
> --
>  
> 
> On 1/9/18, 6:00 PM, "Allison Randal" <allison at lohutok.net> wrote:
> 
>     Following up on the conversation in the call today, have folks on the
>     list read "My VM is Lighter (and Safer) than your Container"[0]? It's a
>     good example of the kind of work we could do now on OpenStack, if we
>     select a small number of representative use cases/scenarios, build
>     sample deployments, and share concrete data with developers on specific
>     changes we need in OpenStack. This kind of work can be ongoing at the
>     same time as higher-level and broader-scope conversations about areas
>     where we're still unsure of the best architecture or implementation details.
>     
>     Allison
>     
>     [0] Filipe Manco, Costin Lupu, Florian Schmidt, Jose Mendes, Simon
>     Kuenzer, Sumit Sati, Kenichi Yasukata, Costin Raiciu, and Felipe Huici
>     (2017) "My VM is Lighter (and Safer) than your Container." In
>     Proceedings of the 26th Symposium on Operating Systems Principles (SOSP
>     '17). ACM, New York, NY, USA, 218-233. DOI:
>     https://doi.org/10.1145/3132747.3132763, Also available at:
>     http://cnp.neclab.eu/projects/lightvm/lightvm.pdf
>     
>     On 01/05/2018 06:53 PM, lebre.adrien at free.fr wrote:
>     > 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_
>     > 
>     > _______________________________________________
>     > Edge-computing mailing list
>     > Edge-computing at lists.openstack.org
>     > http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
>     > 
>     
>     _______________________________________________
>     Edge-computing mailing list
>     Edge-computing at lists.openstack.org
>     http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
>     
> 


From asimha at redhat.com  Thu Jan 11 00:10:07 2018
From: asimha at redhat.com (Ajay Simha)
Date: Wed, 10 Jan 2018 19:10:07 -0500
Subject: [Edge-computing] Classifying edge-site scenarios / Identifying
 expected features
In-Reply-To: <cae6e197-3c23-45c4-1c03-2f67db4dafe2@redhat.com>
References: <1766448670.277045684.1515196426206.JavaMail.root@zimbra29-e5>
 <cae6e197-3c23-45c4-1c03-2f67db4dafe2@redhat.com>
Message-ID: <3E638DA7-6A9D-4426-BC20-8C10493EE17A@redhat.com>

In addition to cell sites and V/CRAN aggregation Control and Data Plane seperation efforts in 5G may result in keeping control plane elements anchored at a central or regional core and only have data plane SDN switches or something light on the edge. 

Ajay

> On Jan 9, 2018, at 1:48 PM, Pasi Vaananen <pvaanane at redhat.com> wrote:
> 
> We should probably focus more on defining the connectivity
> characteristics between the associated entities between the edge
> entities to make progress here. We could start discussion of the network
> connectivity at high level as "black box" representation of the network
> focusing on the latency, bandwith, drop rates, attachment redundancy,
> maximum un-availability etc. characteristics in the context of various
> specific use cases and/or connectivity constraints. These parameters can
> vary widely depending on the specific deployment scenarios.
> 
> It is also possible to have connectivity from the e.g. "thick" vCPE edge
> instance located in customer customer premises that has heterogenous
> connectivity - to use the "LTE" example below, you can have a box that
> has a single wired (say ethernet) connectivity that is used normally,
> and wireless LTE connectivity that is used when the main connection
> fails, but has dissimilar bandwith, latency etc. characteristics.
> 
> Also, top level separation should perhaps be at higher level constructs
> at this early stage, e.g. "mobile" 4G/LTE...5G/eMBB/URULL/...,
> "wireless" (802 stuff), "satellite", "wireline" (ptp fiber, xPON, Cable,
> xDSL/g.fast, ...) rather than getting to technology specifics
> (characteristics of connectivity vary a lot depending on the tech.).
> 
> So far it seems to me that there is not yet sufficient focus on the
> cases for "edge" locations that are within the network, such as cell
> sites, V/CRAN aggregation sites, COs, metro locations etc. - esp. 5G
> vRAN edge has already three tiers of sites on many plans (i.e. radio
> sites, distributed aggregation sites w/ low-latency connections to radio
> sites and central sites, which all should be in the scope of the "edge").
> 
> Pasi 
> 
> 
> On 01/05/2018 06:53 PM, lebre.adrien at free.fr wrote:
>> 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_
>> 
>> _______________________________________________
>> Edge-computing mailing list
>> Edge-computing at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
> 
> 
> _______________________________________________
> Edge-computing mailing list
> Edge-computing at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing



From jass.zhao at gmail.com  Thu Jan 11 02:55:09 2018
From: jass.zhao at gmail.com (Gnep Zhao)
Date: Thu, 11 Jan 2018 02:55:09 +0000
Subject: [Edge-computing] Classifying edge-site scenarios / Identifying
 expected features
In-Reply-To: <9580d4d4-0af4-7660-02da-3038edd3b296@lohutok.net>
References: <1766448670.277045684.1515196426206.JavaMail.root@zimbra29-e5>
 <25bb9633-7fb2-375e-7888-4a7174bbf075@lohutok.net>
 <405A359D-DE00-46EE-8EBD-C34B0A013197@b-yond.com>
 <9580d4d4-0af4-7660-02da-3038edd3b296@lohutok.net>
Message-ID: <d2e824dd-0f0b-1b32-7079-aa3850a1d347@mixmax.com>

Hi,
Just wondering whether multit-tenancy is a hard requirement for some Edge
environment, e.g. device, gateway, NFV appliance? Those setup sound more like
single tenancy, therefore container + baremetal is good enough?  





On Wed, Jan 10, 2018 10:17 PM, Allison Randal allison at lohutok.net  wrote:
The typical pattern for unikernels is to deploy the application

workloads as unikernels rather than as containers or VM/cloud images. (I

also pondered the possibility of trying the OpenStack services deployed

as unikernels, as I read the article, but that was more idle curiosity,

since it wouldn't buy us much in an edge scenario.)




I also wasn't suggesting directly trying the LightVM implementation in

OpenStack, since it's mostly a proof-of-concept at the moment. (Though

I'll be interested to see where they go with it.)




Mainly, I was suggesting that their workflow for performance analysis

and optimization of Xen is a good example of what we could do with

OpenStack Edge deployments, once we've defined a small set of

representative edge-site scenarios. That performance analysis workflow

applies equally well to either the small-footprint or distributed

approach to using OpenStack for edge infrastructure, you just have to

use a more distributed set of performance analysis tools for the

distributed case.




Allison




On 01/09/2018 10:38 PM, Paul-Andre Raymond wrote:

> Allison, 

> 

> Thanks for sharing. I was not aware of this work and I found the article
interesting.

> Today we discussed two aspects:

> 1- How to make openstack fit into smaller footprint (i.e. into an edge site)

> 2- How to make openstack more distributed (with Compute nodes at edge sites
connected via a WAN link)

> 

> This article certainly fits in the first category. 

> In particular, if we think about deploying Openstack components in Unikernels
instead of deploying them with Containers.

> 

> 

> Paul-André

> --

> 

> 

> On 1/9/18, 6:00 PM, "Allison Randal" <allison at lohutok.net> wrote:

> 

> Following up on the conversation in the call today, have folks on the

> list read "My VM is Lighter (and Safer) than your Container"[0]? It's a

> good example of the kind of work we could do now on OpenStack, if we

> select a small number of representative use cases/scenarios, build

> sample deployments, and share concrete data with developers on specific

> changes we need in OpenStack. This kind of work can be ongoing at the

> same time as higher-level and broader-scope conversations about areas

> where we're still unsure of the best architecture or implementation details.

> 

> Allison

> 

> [0] Filipe Manco, Costin Lupu, Florian Schmidt, Jose Mendes, Simon

> Kuenzer, Sumit Sati, Kenichi Yasukata, Costin Raiciu, and Felipe Huici

> (2017) "My VM is Lighter (and Safer) than your Container." In

> Proceedings of the 26th Symposium on Operating Systems Principles (SOSP

> '17). ACM, New York, NY, USA, 218-233. DOI:

> https://doi.org/10.1145/3132747.3132763, Also available at:

> http://cnp.neclab.eu/projects/lightvm/lightvm.pdf

> 

> On 01/05/2018 06:53 PM, lebre.adrien at free.fr wrote:

> > 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_

> > 

> > _______________________________________________

> > Edge-computing mailing list

> > Edge-computing at lists.openstack.org

> > http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing

> > 

> 

> _______________________________________________

> Edge-computing mailing list

> Edge-computing at lists.openstack.org

> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing

> 

> 




_______________________________________________

Edge-computing mailing list

Edge-computing at lists.openstack.org

http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing






============================================================Our greatest
contribution to the world is our dissatisfaction of everything
============================================================
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/edge-computing/attachments/20180111/ac4d0269/attachment-0001.html>

From allison at lohutok.net  Thu Jan 11 03:21:25 2018
From: allison at lohutok.net (Allison Randal)
Date: Wed, 10 Jan 2018 22:21:25 -0500
Subject: [Edge-computing] Classifying edge-site scenarios / Identifying
 expected features
In-Reply-To: <d2e824dd-0f0b-1b32-7079-aa3850a1d347@mixmax.com>
References: <1766448670.277045684.1515196426206.JavaMail.root@zimbra29-e5>
 <25bb9633-7fb2-375e-7888-4a7174bbf075@lohutok.net>
 <405A359D-DE00-46EE-8EBD-C34B0A013197@b-yond.com>
 <9580d4d4-0af4-7660-02da-3038edd3b296@lohutok.net>
 <d2e824dd-0f0b-1b32-7079-aa3850a1d347@mixmax.com>
Message-ID: <2abb075c-6b9f-62fd-e755-1ef54b0ab174@lohutok.net>

Sometimes even unikernel + bare metal is enough. It really depends on
the use case and target application workloads.

On 01/10/2018 09:55 PM, Gnep Zhao wrote:
> Hi,
> 
> Just wondering whether multit-tenancy is a hard requirement for some
> Edge environment, e.g. device, gateway, NFV appliance? Those setup sound
> more like single tenancy, therefore container + baremetal is good enough?
> 
> 
> 
> On Wed, Jan 10, 2018 10:17 PM, Allison Randal allison at lohutok.net
> <mailto:allison at lohutok.net> wrote:
> 
>     __
> 
>     The typical pattern for unikernels is to deploy the application
> 
>     workloads as unikernels rather than as containers or VM/cloud images. (I
> 
>     also pondered the possibility of trying the OpenStack services deployed
> 
>     as unikernels, as I read the article, but that was more idle curiosity,
> 
>     since it wouldn't buy us much in an edge scenario.)
> 
> 
>     I also wasn't suggesting directly trying the LightVM implementation in
> 
>     OpenStack, since it's mostly a proof-of-concept at the moment. (Though
> 
>     I'll be interested to see where they go with it.)
> 
> 
>     Mainly, I was suggesting that their workflow for performance analysis
> 
>     and optimization of Xen is a good example of what we could do with
> 
>     OpenStack Edge deployments, once we've defined a small set of
> 
>     representative edge-site scenarios. That performance analysis workflow
> 
>     applies equally well to either the small-footprint or distributed
> 
>     approach to using OpenStack for edge infrastructure, you just have to
> 
>     use a more distributed set of performance analysis tools for the
> 
>     distributed case.
> 
> 
>     Allison
> 
> 
>     On 01/09/2018 10:38 PM, Paul-Andre Raymond wrote:
> 
>     > Allison,
> 
>     >
> 
>     > Thanks for sharing. I was not aware of this work and I found the
>     article interesting.
> 
>     > Today we discussed two aspects:
> 
>     > 1- How to make openstack fit into smaller footprint (i.e. into an
>     edge site)
> 
>     > 2- How to make openstack more distributed (with Compute nodes at
>     edge sites connected via a WAN link)
> 
>     >
> 
>     > This article certainly fits in the first category.
> 
>     > In particular, if we think about deploying Openstack components in
>     Unikernels instead of deploying them with Containers.
> 
>     >
> 
>     >
> 
>     > Paul-André
> 
>     > --
> 
>     >
> 
>     >
> 
>     > On 1/9/18, 6:00 PM, "Allison Randal" <allison at lohutok.net> wrote:
> 
>     >
> 
>     > Following up on the conversation in the call today, have folks on the
> 
>     > list read "My VM is Lighter (and Safer) than your Container"[0]?
>     It's a
> 
>     > good example of the kind of work we could do now on OpenStack, if we
> 
>     > select a small number of representative use cases/scenarios, build
> 
>     > sample deployments, and share concrete data with developers on
>     specific
> 
>     > changes we need in OpenStack. This kind of work can be ongoing at the
> 
>     > same time as higher-level and broader-scope conversations about areas
> 
>     > where we're still unsure of the best architecture or
>     implementation details.
> 
>     >
> 
>     > Allison
> 
>     >
> 
>     > [0] Filipe Manco, Costin Lupu, Florian Schmidt, Jose Mendes, Simon
> 
>     > Kuenzer, Sumit Sati, Kenichi Yasukata, Costin Raiciu, and Felipe Huici
> 
>     > (2017) "My VM is Lighter (and Safer) than your Container." In
> 
>     > Proceedings of the 26th Symposium on Operating Systems Principles
>     (SOSP
> 
>     > '17). ACM, New York, NY, USA, 218-233. DOI:
> 
>     > https://doi.org/10.1145/3132747.3132763, Also available at:
> 
>     > http://cnp.neclab.eu/projects/lightvm/lightvm.pdf
> 
>     >
> 
>     > On 01/05/2018 06:53 PM, lebre.adrien at free.fr wrote:
> 
>     > > 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_
> 
>     > >
> 
>     > > _______________________________________________
> 
>     > > Edge-computing mailing list
> 
>     > > Edge-computing at lists.openstack.org
> 
>     > > http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
> 
>     > >
> 
>     >
> 
>     > _______________________________________________
> 
>     > Edge-computing mailing list
> 
>     > Edge-computing at lists.openstack.org
> 
>     > http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
> 
>     >
> 
>     >
> 
> 
>     _______________________________________________
> 
>     Edge-computing mailing list
> 
>     Edge-computing at lists.openstack.org
> 
>     http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
> 
> 
> 
> 
> ============================================================
> *Our greatest contribution to the world is our dissatisfaction of
> everything*
> ============================================================


From Hyde at redhat.com  Thu Jan 11 04:26:10 2018
From: Hyde at redhat.com (Hyde SUGIYAMA)
Date: Thu, 11 Jan 2018 13:26:10 +0900
Subject: [Edge-computing] Classifying edge-site scenarios / Identifying
 expected features
In-Reply-To: <201801100740.49331.satya@cs.cmu.edu>
References: <1766448670.277045684.1515196426206.JavaMail.root@zimbra29-e5>
 <cae6e197-3c23-45c4-1c03-2f67db4dafe2@redhat.com>
 <CABxuFYkfnmfQQ233TZ8BVwUTx3CDibcKwodGCGJ9EyBq=qO4Pw@mail.gmail.com>
 <201801100740.49331.satya@cs.cmu.edu>
Message-ID: <CABxuFY=LMohfxXBPaZLRch0ozJAOn5e0n0shHonm1PyKpoJJbg@mail.gmail.com>

Thanks for sharing the links, but my current scope is Edge in
infrastructure to aggregate data traffic(like your MQTT traffic) from
vehicles.

PS.
Discussion about edge inside the vehicle should start from Automotive Linux
summit.
So far, they focus on IVI but the scope is not limited as far as I know.
I have't heard that they need Edge-enabled OpenStack in every vehicle...

-- Hyde

2018-01-10 21:40 GMT+09:00 Mahadev Satyanarayanan <satya at cs.cmu.edu>:

> On Tuesday 09 January 2018 23:20:07 Hyde SUGIYAMA wrote:
> > How can OpenStack Edge Computing help Automotive industry?
>
> A key insight is that "edge" has to mean inside the vehicle, not only
> at cell tower or close to it.  In other words, every vehicle should have
> a substantial on-board cloudlet.   See these two references on why:
>  - http://elijah.cs.cmu.edu/DOCS/hu-livemap2017.pdf
>  - http://elijah.cs.cmu.edu/DOCS/satya-lanman2017.pdf
>
> Edge-enabled OpenStack in every vehicle?
>
>               -- Satya
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/edge-computing/attachments/20180111/b875191e/attachment.html>

From gergely.csatari at nokia.com  Thu Jan 11 10:16:08 2018
From: gergely.csatari at nokia.com (Csatari, Gergely (Nokia - HU/Budapest))
Date: Thu, 11 Jan 2018 10:16:08 +0000
Subject: [Edge-computing] Classifying edge-site scenarios / Identifying
 expected features
In-Reply-To: <CABxuFY=LMohfxXBPaZLRch0ozJAOn5e0n0shHonm1PyKpoJJbg@mail.gmail.com>
References: <1766448670.277045684.1515196426206.JavaMail.root@zimbra29-e5>
 <cae6e197-3c23-45c4-1c03-2f67db4dafe2@redhat.com>
 <CABxuFYkfnmfQQ233TZ8BVwUTx3CDibcKwodGCGJ9EyBq=qO4Pw@mail.gmail.com>
 <201801100740.49331.satya@cs.cmu.edu>
 <CABxuFY=LMohfxXBPaZLRch0ozJAOn5e0n0shHonm1PyKpoJJbg@mail.gmail.com>
Message-ID: <VI1PR07MB3325BC883CC13C1DCCE44EBAE1160@VI1PR07MB3325.eurprd07.prod.outlook.com>

Hi,

Hmm, runing OpenStack components in unikernels limits the hw variants that can be used and the os features the guests can use.

Br,
Gerg0

From: Hyde SUGIYAMA [mailto:Hyde at redhat.com]
Sent: Thursday, January 11, 2018 5:26 AM
To: Mahadev Satyanarayanan <satya at cs.cmu.edu>
Cc: edge-computing at lists.openstack.org
Subject: Re: [Edge-computing] Classifying edge-site scenarios / Identifying expected features


Thanks for sharing the links, but my current scope is Edge in infrastructure to aggregate data traffic(like your MQTT traffic) from vehicles.

PS.
Discussion about edge inside the vehicle should start from Automotive Linux summit.
So far, they focus on IVI but the scope is not limited as far as I know.
I have't heard that they need Edge-enabled OpenStack in every vehicle...

-- Hyde

2018-01-10 21:40 GMT+09:00 Mahadev Satyanarayanan <satya at cs.cmu.edu<mailto:satya at cs.cmu.edu>>:
On Tuesday 09 January 2018 23:20:07 Hyde SUGIYAMA wrote:
> How can OpenStack Edge Computing help Automotive industry?

A key insight is that "edge" has to mean inside the vehicle, not only
at cell tower or close to it.  In other words, every vehicle should have
a substantial on-board cloudlet.   See these two references on why:
 - http://elijah.cs.cmu.edu/DOCS/hu-livemap2017.pdf
 - http://elijah.cs.cmu.edu/DOCS/satya-lanman2017.pdf

Edge-enabled OpenStack in every vehicle?

              -- Satya

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/edge-computing/attachments/20180111/e0cbb0e2/attachment-0001.html>

From gergely.csatari at nokia.com  Thu Jan 11 13:18:58 2018
From: gergely.csatari at nokia.com (Csatari, Gergely (Nokia - HU/Budapest))
Date: Thu, 11 Jan 2018 13:18:58 +0000
Subject: [Edge-computing] Classifying edge-site scenarios / Identifying
 expected features
In-Reply-To: <VI1PR07MB3325BC883CC13C1DCCE44EBAE1160@VI1PR07MB3325.eurprd07.prod.outlook.com>
References: <1766448670.277045684.1515196426206.JavaMail.root@zimbra29-e5>
 <cae6e197-3c23-45c4-1c03-2f67db4dafe2@redhat.com>
 <CABxuFYkfnmfQQ233TZ8BVwUTx3CDibcKwodGCGJ9EyBq=qO4Pw@mail.gmail.com>
 <201801100740.49331.satya@cs.cmu.edu>
 <CABxuFY=LMohfxXBPaZLRch0ozJAOn5e0n0shHonm1PyKpoJJbg@mail.gmail.com>
 <VI1PR07MB3325BC883CC13C1DCCE44EBAE1160@VI1PR07MB3325.eurprd07.prod.outlook.com>
Message-ID: <VI1PR07MB3325BFFA54D8BE737FF083EFE1160@VI1PR07MB3325.eurprd07.prod.outlook.com>

Hi,

I’ve added MY view of the answers to the use case questions to the medium edge deployment scenario from line 13 to here: https://etherpad.openstack.org/p/edge-use-case-questions
Also mapped the user stories from here https://etherpad.openstack.org/p/2017_edge_computing_working_sessions_existing_gaps to the same text.

Any comments are welcome, but be aware, that I will be out of office for two weeks starting from Friday.

Br,
Gerg0

From: Csatari, Gergely (Nokia - HU/Budapest)
Sent: Thursday, January 11, 2018 11:16 AM
To: 'Hyde SUGIYAMA' <Hyde at redhat.com>; Mahadev Satyanarayanan <satya at cs.cmu.edu>
Cc: edge-computing at lists.openstack.org
Subject: RE: [Edge-computing] Classifying edge-site scenarios / Identifying expected features

Hi,

Hmm, runing OpenStack components in unikernels limits the hw variants that can be used and the os features the guests can use.

Br,
Gerg0

From: Hyde SUGIYAMA [mailto:Hyde at redhat.com]
Sent: Thursday, January 11, 2018 5:26 AM
To: Mahadev Satyanarayanan <satya at cs.cmu.edu<mailto:satya at cs.cmu.edu>>
Cc: edge-computing at lists.openstack.org<mailto:edge-computing at lists.openstack.org>
Subject: Re: [Edge-computing] Classifying edge-site scenarios / Identifying expected features


Thanks for sharing the links, but my current scope is Edge in infrastructure to aggregate data traffic(like your MQTT traffic) from vehicles.

PS.
Discussion about edge inside the vehicle should start from Automotive Linux summit.
So far, they focus on IVI but the scope is not limited as far as I know.
I have't heard that they need Edge-enabled OpenStack in every vehicle...

-- Hyde

2018-01-10 21:40 GMT+09:00 Mahadev Satyanarayanan <satya at cs.cmu.edu<mailto:satya at cs.cmu.edu>>:
On Tuesday 09 January 2018 23:20:07 Hyde SUGIYAMA wrote:
> How can OpenStack Edge Computing help Automotive industry?

A key insight is that "edge" has to mean inside the vehicle, not only
at cell tower or close to it.  In other words, every vehicle should have
a substantial on-board cloudlet.   See these two references on why:
 - http://elijah.cs.cmu.edu/DOCS/hu-livemap2017.pdf
 - http://elijah.cs.cmu.edu/DOCS/satya-lanman2017.pdf

Edge-enabled OpenStack in every vehicle?

              -- Satya

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/edge-computing/attachments/20180111/2d7ddba5/attachment.html>

From pvaanane at redhat.com  Thu Jan 11 18:38:28 2018
From: pvaanane at redhat.com (Pasi Vaananen)
Date: Thu, 11 Jan 2018 13:38:28 -0500
Subject: [Edge-computing] Classifying edge-site scenarios / Identifying
 expected features
In-Reply-To: <3E638DA7-6A9D-4426-BC20-8C10493EE17A@redhat.com>
References: <1766448670.277045684.1515196426206.JavaMail.root@zimbra29-e5>
 <cae6e197-3c23-45c4-1c03-2f67db4dafe2@redhat.com>
 <3E638DA7-6A9D-4426-BC20-8C10493EE17A@redhat.com>
Message-ID: <c591a9de-af3e-8cf1-9a40-5b20c2f06119@redhat.com>

There are two aspects to this, first being the split architecture of the
functionality between the (Remote)Radio Heads, Distributed Units and
Centralized units for RAN, and second aspects is the CP/DP separation.
In addition, core location (and associated splits) as well as splicing
affect location of functions, and can be service specific - i.e.
location of components for URULL service can be different than location
for same components for eMBB service.

RAN functions themselves have hard real-time requirements constraining
the latencies (e.g. 100us OWD target for L1 stuff in CPRI/eCPRI and
other low level split specs), which limits distance from radio to ~20km.
Since goal of some new services / edge deployments is latency
minimization (including the 1ms target for whole RAN, including both
transmission and processing), that further limits on what can be placed
where.

Pasi


On 01/10/2018 07:10 PM, Ajay Simha wrote:
> In addition to cell sites and V/CRAN aggregation Control and Data Plane seperation efforts in 5G may result in keeping control plane elements anchored at a central or regional core and only have data plane SDN switches or something light on the edge. 
>
> Ajay
>
>> On Jan 9, 2018, at 1:48 PM, Pasi Vaananen <pvaanane at redhat.com> wrote:
>>
>> We should probably focus more on defining the connectivity
>> characteristics between the associated entities between the edge
>> entities to make progress here. We could start discussion of the network
>> connectivity at high level as "black box" representation of the network
>> focusing on the latency, bandwith, drop rates, attachment redundancy,
>> maximum un-availability etc. characteristics in the context of various
>> specific use cases and/or connectivity constraints. These parameters can
>> vary widely depending on the specific deployment scenarios.
>>
>> It is also possible to have connectivity from the e.g. "thick" vCPE edge
>> instance located in customer customer premises that has heterogenous
>> connectivity - to use the "LTE" example below, you can have a box that
>> has a single wired (say ethernet) connectivity that is used normally,
>> and wireless LTE connectivity that is used when the main connection
>> fails, but has dissimilar bandwith, latency etc. characteristics.
>>
>> Also, top level separation should perhaps be at higher level constructs
>> at this early stage, e.g. "mobile" 4G/LTE...5G/eMBB/URULL/...,
>> "wireless" (802 stuff), "satellite", "wireline" (ptp fiber, xPON, Cable,
>> xDSL/g.fast, ...) rather than getting to technology specifics
>> (characteristics of connectivity vary a lot depending on the tech.).
>>
>> So far it seems to me that there is not yet sufficient focus on the
>> cases for "edge" locations that are within the network, such as cell
>> sites, V/CRAN aggregation sites, COs, metro locations etc. - esp. 5G
>> vRAN edge has already three tiers of sites on many plans (i.e. radio
>> sites, distributed aggregation sites w/ low-latency connections to radio
>> sites and central sites, which all should be in the scope of the "edge").
>>
>> Pasi 
>>
>>
>> On 01/05/2018 06:53 PM, lebre.adrien at free.fr wrote:
>>> 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_
>>>
>>> _______________________________________________
>>> Edge-computing mailing list
>>> Edge-computing at lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
>>
>> _______________________________________________
>> Edge-computing mailing list
>> Edge-computing at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing



From pvaanane at redhat.com  Thu Jan 11 18:41:00 2018
From: pvaanane at redhat.com (Pasi Vaananen)
Date: Thu, 11 Jan 2018 13:41:00 -0500
Subject: [Edge-computing] Classifying edge-site scenarios / Identifying
 expected features
In-Reply-To: <d2e824dd-0f0b-1b32-7079-aa3850a1d347@mixmax.com>
References: <1766448670.277045684.1515196426206.JavaMail.root@zimbra29-e5>
 <25bb9633-7fb2-375e-7888-4a7174bbf075@lohutok.net>
 <405A359D-DE00-46EE-8EBD-C34B0A013197@b-yond.com>
 <9580d4d4-0af4-7660-02da-3038edd3b296@lohutok.net>
 <d2e824dd-0f0b-1b32-7079-aa3850a1d347@mixmax.com>
Message-ID: <7bfebb3e-ca91-bcc9-00a6-e14b4a53ca57@redhat.com>

Cannot comment on "some", but it is generally requirement for "many".
Containers do not mean that the do not need multi-tenancy, but if you
want to include "all" cases vs. only "some", then it is a requirement.

Pasi


On 01/10/2018 09:55 PM, Gnep Zhao wrote:
> Hi,
>
> Just wondering whether multit-tenancy is a hard requirement for some
> Edge environment, e.g. device, gateway, NFV appliance? Those setup
> sound more like single tenancy, therefore container + baremetal is
> good enough?
>
>
>
> On Wed, Jan 10, 2018 10:17 PM, Allison Randal allison at lohutok.net
> <mailto:allison at lohutok.net> wrote:
>
>     The typical pattern for unikernels is to deploy the application
>
>     workloads as unikernels rather than as containers or VM/cloud
>     images. (I
>
>     also pondered the possibility of trying the OpenStack services
>     deployed
>
>     as unikernels, as I read the article, but that was more idle
>     curiosity,
>
>     since it wouldn't buy us much in an edge scenario.)
>
>
>     I also wasn't suggesting directly trying the LightVM implementation in
>
>     OpenStack, since it's mostly a proof-of-concept at the moment. (Though
>
>     I'll be interested to see where they go with it.)
>
>
>     Mainly, I was suggesting that their workflow for performance analysis
>
>     and optimization of Xen is a good example of what we could do with
>
>     OpenStack Edge deployments, once we've defined a small set of
>
>     representative edge-site scenarios. That performance analysis workflow
>
>     applies equally well to either the small-footprint or distributed
>
>     approach to using OpenStack for edge infrastructure, you just have to
>
>     use a more distributed set of performance analysis tools for the
>
>     distributed case.
>
>
>     Allison
>
>
>     On 01/09/2018 10:38 PM, Paul-Andre Raymond wrote:
>
>     > Allison,
>
>     >
>
>     > Thanks for sharing. I was not aware of this work and I found the
>     article interesting.
>
>     > Today we discussed two aspects:
>
>     > 1- How to make openstack fit into smaller footprint (i.e. into
>     an edge site)
>
>     > 2- How to make openstack more distributed (with Compute nodes at
>     edge sites connected via a WAN link)
>
>     >
>
>     > This article certainly fits in the first category.
>
>     > In particular, if we think about deploying Openstack components
>     in Unikernels instead of deploying them with Containers.
>
>     >
>
>     >
>
>     > Paul-André
>
>     > --
>
>     >
>
>     >
>
>     > On 1/9/18, 6:00 PM, "Allison Randal" <allison at lohutok.net> wrote:
>
>     >
>
>     > Following up on the conversation in the call today, have folks
>     on the
>
>     > list read "My VM is Lighter (and Safer) than your Container"[0]?
>     It's a
>
>     > good example of the kind of work we could do now on OpenStack, if we
>
>     > select a small number of representative use cases/scenarios, build
>
>     > sample deployments, and share concrete data with developers on
>     specific
>
>     > changes we need in OpenStack. This kind of work can be ongoing
>     at the
>
>     > same time as higher-level and broader-scope conversations about
>     areas
>
>     > where we're still unsure of the best architecture or
>     implementation details.
>
>     >
>
>     > Allison
>
>     >
>
>     > [0] Filipe Manco, Costin Lupu, Florian Schmidt, Jose Mendes, Simon
>
>     > Kuenzer, Sumit Sati, Kenichi Yasukata, Costin Raiciu, and Felipe
>     Huici
>
>     > (2017) "My VM is Lighter (and Safer) than your Container." In
>
>     > Proceedings of the 26th Symposium on Operating Systems
>     Principles (SOSP
>
>     > '17). ACM, New York, NY, USA, 218-233. DOI:
>
>     > https://doi.org/10.1145/3132747.3132763, Also available at:
>
>     > http://cnp.neclab.eu/projects/lightvm/lightvm.pdf
>
>     >
>
>     > On 01/05/2018 06:53 PM, lebre.adrien at free.fr wrote:
>
>     > > 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_
>
>     > >
>
>     > > _______________________________________________
>
>     > > Edge-computing mailing list
>
>     > > Edge-computing at lists.openstack.org
>
>     > > http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
>
>     > >
>
>     >
>
>     > _______________________________________________
>
>     > Edge-computing mailing list
>
>     > Edge-computing at lists.openstack.org
>
>     > http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
>
>     >
>
>     >
>
>
>     _______________________________________________
>
>     Edge-computing mailing list
>
>     Edge-computing at lists.openstack.org
>
>     http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
>
>
>
>
> ============================================================
> *Our greatest contribution to the world is our dissatisfaction of
> everything*
> ============================================================
>
>
> _______________________________________________
> Edge-computing mailing list
> Edge-computing at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/edge-computing/attachments/20180111/6eae5bde/attachment-0001.html>

From jass.zhao at gmail.com  Fri Jan 12 02:24:42 2018
From: jass.zhao at gmail.com (Gnep Zhao)
Date: Fri, 12 Jan 2018 02:24:42 +0000
Subject: [Edge-computing] Classifying edge-site scenarios / Identifying
 expected features
In-Reply-To: <7bfebb3e-ca91-bcc9-00a6-e14b4a53ca57@redhat.com>
References: <1766448670.277045684.1515196426206.JavaMail.root@zimbra29-e5>
 <25bb9633-7fb2-375e-7888-4a7174bbf075@lohutok.net>
 <405A359D-DE00-46EE-8EBD-C34B0A013197@b-yond.com>
 <9580d4d4-0af4-7660-02da-3038edd3b296@lohutok.net>
 <d2e824dd-0f0b-1b32-7079-aa3850a1d347@mixmax.com>
 <7bfebb3e-ca91-bcc9-00a6-e14b4a53ca57@redhat.com>
Message-ID: <4de27b6c-34c0-3df6-15f3-0cb5774d573e@mixmax.com>

Agreed.
The infra layer (compute, not storage and network) has two type of runtime
technologies: container and virtualization. To provide a universal and portable
platform for applications, the underlying runtime is an implementation choice.
The package format, aka Image, is the key. Application should be packaged only
once in a "standard" format, and be deployed on any runtime, based on various
requirements.
With that said, not all apps can be "dockerized" or turned into "micro-service",
some are built with the notion of Server. But that doesn't necessarily mean that
it has to run as VMs. LXD is able to provide a VM-like experience on top of
cgroup/namespace; and Kata is able to provide a Docker experience on top of KVM.
The myth is that Docker image has to be microservices. In fact, we can build
"fat", full server-like Docker images. But uniting both container and
virtualization under one single, de-facto image format and workflow has
tremendous benefits.  





On Fri, Jan 12, 2018 2:41 AM, Pasi Vaananen pvaanane at redhat.com  wrote:
Cannot comment on "some", but it is generally requirement for "many". Containers
do not mean that the do not need multi-tenancy, but if you want to include "all"
cases vs. only "some", then it is a requirement. 


Pasi



On 01/10/2018 09:55 PM, Gnep Zhao wrote:
Hi,  
Just wondering whether multit-tenancy is a hard requirement for some Edge
environment, e.g. device, gateway, NFV appliance? Those setup sound more like
single tenancy, therefore container + baremetal is good enough?  





On Wed, Jan 10, 2018 10:17 PM, Allison Randal allison at lohutok.net  wrote:
The typical pattern for unikernels is to deploy the application

workloads as unikernels rather than as containers or VM/cloud images. (I

also pondered the possibility of trying the OpenStack services deployed

as unikernels, as I read the article, but that was more idle curiosity,

since it wouldn't buy us much in an edge scenario.)




I also wasn't suggesting directly trying the LightVM implementation in

OpenStack, since it's mostly a proof-of-concept at the moment. (Though

I'll be interested to see where they go with it.)




Mainly, I was suggesting that their workflow for performance analysis

and optimization of Xen is a good example of what we could do with

OpenStack Edge deployments, once we've defined a small set of

representative edge-site scenarios. That performance analysis workflow

applies equally well to either the small-footprint or distributed

approach to using OpenStack for edge infrastructure, you just have to

use a more distributed set of performance analysis tools for the

distributed case.




Allison




On 01/09/2018 10:38 PM, Paul-Andre Raymond wrote:

> Allison, 

> 

> Thanks for sharing. I was not aware of this work and I found the article
interesting.

> Today we discussed two aspects:

> 1- How to make openstack fit into smaller footprint (i.e. into an edge site)

> 2- How to make openstack more distributed (with Compute nodes at edge sites
connected via a WAN link)

> 

> This article certainly fits in the first category. 

> In particular, if we think about deploying Openstack components in Unikernels
instead of deploying them with Containers.

> 

> 

> Paul-André

> --

> 

> 

> On 1/9/18, 6:00 PM, "Allison Randal" <allison at lohutok.net>  wrote:

> 

> Following up on the conversation in the call today, have folks on the

> list read "My VM is Lighter (and Safer) than your Container"[0]? It's a

> good example of the kind of work we could do now on OpenStack, if we

> select a small number of representative use cases/scenarios, build

> sample deployments, and share concrete data with developers on specific

> changes we need in OpenStack. This kind of work can be ongoing at the

> same time as higher-level and broader-scope conversations about areas

> where we're still unsure of the best architecture or implementation details.

> 

> Allison

> 

> [0] Filipe Manco, Costin Lupu, Florian Schmidt, Jose Mendes, Simon

> Kuenzer, Sumit Sati, Kenichi Yasukata, Costin Raiciu, and Felipe Huici

> (2017) "My VM is Lighter (and Safer) than your Container." In

> Proceedings of the 26th Symposium on Operating Systems Principles (SOSP

> '17). ACM, New York, NY, USA, 218-233. DOI:

> https://doi.org/10.1145/3132747.3132763, Also available at:

> http://cnp.neclab.eu/projects/lightvm/lightvm.pdf

> 

> On 01/05/2018 06:53 PM, lebre.adrien at free.fr  wrote:

> > 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_

> > 

> > _______________________________________________

> > Edge-computing mailing list

> > Edge-computing at lists.openstack.org

> > http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing

> > 

> 

> _______________________________________________

> Edge-computing mailing list

> Edge-computing at lists.openstack.org

> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing

> 

> 




_______________________________________________

Edge-computing mailing list

Edge-computing at lists.openstack.org

http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing






============================================================  Our greatest
contribution to the world is our dissatisfaction of everything  
============================================================  

_______________________________________________
Edge-computing mailing list
Edge-computing at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing





============================================================Our greatest
contribution to the world is our dissatisfaction of everything
============================================================
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/edge-computing/attachments/20180112/9922fd3b/attachment.html>

From claire at openstack.org  Tue Jan 16 16:18:23 2018
From: claire at openstack.org (Claire Massey)
Date: Tue, 16 Jan 2018 10:18:23 -0600
Subject: [Edge-computing] =?utf-8?q?OpenStack_Vancouver_Summit_CFP_is_open?=
 =?utf-8?b?IC0gd2hhdOKAmXMgbmV3?=
Message-ID: <DE8EA874-5D00-40E6-9CCC-476B6BC9100D@openstack.org>

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/selection-process> 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_programmingcommitteenom>. 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 at openstack.org <mailto:summit at openstack.org>.

Thanks,
Claire
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/edge-computing/attachments/20180116/495e1333/attachment-0001.html>

From jonathan at openstack.org  Mon Jan 22 21:15:22 2018
From: jonathan at openstack.org (Jonathan Bryce)
Date: Mon, 22 Jan 2018 15:15:22 -0600
Subject: [Edge-computing] Tomorrow's meeting
Message-ID: <BB3B79CD-6F8A-4024-928A-F90C11A54960@openstack.org>

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

From lebre.adrien at free.fr  Tue Jan 23 14:49:44 2018
From: lebre.adrien at free.fr (lebre.adrien at free.fr)
Date: Tue, 23 Jan 2018 15:49:44 +0100 (CET)
Subject: [Edge-computing] [FEMDC] A first step to the gap analysis of the
	OpenStack code base
In-Reply-To: <1073909094.359978697.1516718776029.JavaMail.root@zimbra29-e5>
Message-ID: <1560444865.359995003.1516718984389.JavaMail.root@zimbra29-e5>

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_


From Arkady.Kanevsky at dell.com  Mon Jan 22 21:21:57 2018
From: Arkady.Kanevsky at dell.com (Arkady.Kanevsky at dell.com)
Date: Mon, 22 Jan 2018 21:21:57 +0000
Subject: [Edge-computing] Tomorrow's meeting
In-Reply-To: <BB3B79CD-6F8A-4024-928A-F90C11A54960@openstack.org>
References: <BB3B79CD-6F8A-4024-928A-F90C11A54960@openstack.org>
Message-ID: <27da60f385044096b6f136a63554a157@AUSX13MPS308.AMER.DELL.COM>

I will miss one next week also.
Support skipping it next week

-----Original Message-----
From: Jonathan Bryce [mailto:jonathan at openstack.org] 
Sent: Monday, January 22, 2018 3:15 PM
To: edge-computing at lists.openstack.org
Subject: [Edge-computing] Tomorrow's meeting

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
_______________________________________________
Edge-computing mailing list
Edge-computing at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing

From claire at openstack.org  Wed Jan 31 21:10:24 2018
From: claire at openstack.org (Claire Massey)
Date: Wed, 31 Jan 2018 15:10:24 -0600
Subject: [Edge-computing]
 =?utf-8?q?OpenStack_Vancouver_Summit_CFP_is_open?=
 =?utf-8?b?IC0gd2hhdOKAmXMgbmV3?=
In-Reply-To: <DE8EA874-5D00-40E6-9CCC-476B6BC9100D@openstack.org>
References: <DE8EA874-5D00-40E6-9CCC-476B6BC9100D@openstack.org>
Message-ID: <020B22DF-D365-490F-B949-027B2CEDC411@openstack.org>

Hi there,

Friendly reminder- 

February 8th is the Call for Presentations <https://www.openstack.org/summit/vancouver-2018/call-for-presentations/> deadline for the OpenStack Summit <https://www.openstack.org/summit/vancouver-2018/> which will take place in Vancouver, May 21-24. 

Please consider submitting a talk to the *Edge Computing* track and invite your colleagues from other open source communities to come speak and collaborate.

Thanks,
Claire



> On Jan 16, 2018, at 10:18 AM, Claire Massey <claire at openstack.org> wrote:
> 
> 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/selection-process> 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_programmingcommitteenom>. 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 at openstack.org <mailto:summit at openstack.org>.
> 
> Thanks,
> Claire
> _______________________________________________
> Edge-computing mailing list
> Edge-computing at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/edge-computing/attachments/20180131/576fede8/attachment-0001.html>