From ildiko at openstack.org  Tue Oct  2 12:37:11 2018
From: ildiko at openstack.org (Ildiko Vancsa)
Date: Tue, 2 Oct 2018 14:37:11 +0200
Subject: [Edge-computing] Weekly call in APAC slot this week
Message-ID: <6BC7E46B-9D90-43CD-B0A9-AE634705ACC1@openstack.org>

Hi,

It is a friendly reminder that we are having our weekly call this week in the APAC friendly time slot, on Thursday (October4), 0700 UTC.

Please see the wiki for details: https://wiki.openstack.org/wiki/Edge_Computing_Group#Meetings

Thanks and Best Regards,
Ildikó




From ildiko at openstack.org  Wed Oct  3 12:29:48 2018
From: ildiko at openstack.org (Ildiko Vancsa)
Date: Wed, 3 Oct 2018 14:29:48 +0200
Subject: [Edge-computing] Rescheduling and alternating the Use cases weekly
	call
Message-ID: <6FEB690C-6AC4-4791-8187-C078B7E4FF13@openstack.org>

Hi,

As it came up earlier it is important to be inclusive and provide possibilities for everyone around the globe to participate in our activities.

Our Use cases weekly calls are in a very inconvenient time slot for both Europe and APAC therefore we decided to look for better time slots and also alternate them for a better coverage.

I created a Doodle poll with a few time slots in the morning in the States as well as for the afternoon which should provide better options on other continents as well. If you’re interested in joining this call please fill out the form as soon as possible. Please avoid the dates and mark every slot that can work for you in general: https://doodle.com/poll/cdc8sgc6hwu6hqgw

Please let me know if you have any questions.

Thanks and Best Regards,
Ildikó




From Greg.Waines at windriver.com  Wed Oct  3 18:23:57 2018
From: Greg.Waines at windriver.com (Waines, Greg)
Date: Wed, 3 Oct 2018 18:23:57 +0000
Subject: [Edge-computing] Weekly call in APAC slot this week
In-Reply-To: <6BC7E46B-9D90-43CD-B0A9-AE634705ACC1@openstack.org>
References: <6BC7E46B-9D90-43CD-B0A9-AE634705ACC1@openstack.org>
Message-ID: <D6272FD3-0211-40BA-A099-6AEB41DAE1F2@windriver.com>

Just curious ...

Will there be an update from Gergely and/or MarkB. on Federated Keystone Testing ?

I have done some evaluation testing on Federated Keystone with testshib and am interested in comparing results.

Greg.


From: Ildiko Vancsa <ildiko at openstack.org>
Date: Tuesday, October 2, 2018 at 8:37 AM
To: edge-computing <edge-computing at lists.openstack.org>
Subject: [Edge-computing] Weekly call in APAC slot this week

Hi,

It is a friendly reminder that we are having our weekly call this week in the APAC friendly time slot, on Thursday (October4), 0700 UTC.

Please see the wiki for details: https://wiki.openstack.org/wiki/Edge_Computing_Group#Meetings

Thanks and Best Regards,
Ildikó



_______________________________________________
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/20181003/d3e723f1/attachment.html>

From ildiko at openstack.org  Wed Oct  3 18:54:11 2018
From: ildiko at openstack.org (Ildiko Vancsa)
Date: Wed, 3 Oct 2018 20:54:11 +0200
Subject: [Edge-computing] Weekly call in APAC slot this week
In-Reply-To: <D6272FD3-0211-40BA-A099-6AEB41DAE1F2@windriver.com>
References: <6BC7E46B-9D90-43CD-B0A9-AE634705ACC1@openstack.org>
 <D6272FD3-0211-40BA-A099-6AEB41DAE1F2@windriver.com>
Message-ID: <4662AC03-44B1-4628-89C9-524D35FBD8D0@openstack.org>

Hi Greg,

Gergely is on vacation this week. I will ping him and Mark on Monday to see whether they would be available to check back on this next Tuesday on the weekly call. Would this plan work or you had a separate meeting in mind?

Thanks,
Ildikó


> On 2018. Oct 3., at 20:23, Waines, Greg <Greg.Waines at windriver.com> wrote:
> 
> Just curious ...
>  
> Will there be an update from Gergely and/or MarkB. on Federated Keystone Testing ?
>  
> I have done some evaluation testing on Federated Keystone with testshib and am interested in comparing results.
>  
> Greg. 
>  
>  
> From: Ildiko Vancsa <ildiko at openstack.org>
> Date: Tuesday, October 2, 2018 at 8:37 AM
> To: edge-computing <edge-computing at lists.openstack.org>
> Subject: [Edge-computing] Weekly call in APAC slot this week
>  
> Hi,
>  
> It is a friendly reminder that we are having our weekly call this week in the APAC friendly time slot, on Thursday (October4), 0700 UTC.
>  
> Please see the wiki for details: https://wiki.openstack.org/wiki/Edge_Computing_Group#Meetings
>  
> Thanks and Best Regards,
> Ildikó
>  
>  
>  
> _______________________________________________
> Edge-computing mailing list
> Edge-computing at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
>  



From Greg.Waines at windriver.com  Wed Oct  3 19:04:06 2018
From: Greg.Waines at windriver.com (Waines, Greg)
Date: Wed, 3 Oct 2018 19:04:06 +0000
Subject: [Edge-computing] Weekly call in APAC slot this week
In-Reply-To: <4662AC03-44B1-4628-89C9-524D35FBD8D0@openstack.org>
References: <6BC7E46B-9D90-43CD-B0A9-AE634705ACC1@openstack.org>
 <D6272FD3-0211-40BA-A099-6AEB41DAE1F2@windriver.com>
 <4662AC03-44B1-4628-89C9-524D35FBD8D0@openstack.org>
Message-ID: <579CFAFE-10E7-485B-9C6A-9CB59BFE6B9F@windriver.com>

That works ... I can wait til next Tuesday.
Thanks,
Greg.

From: Ildiko Vancsa <ildiko at openstack.org>
Date: Wednesday, October 3, 2018 at 2:54 PM
To: Greg Waines <Greg.Waines at windriver.com>
Cc: edge-computing <edge-computing at lists.openstack.org>
Subject: Re: [Edge-computing] Weekly call in APAC slot this week

Hi Greg,

Gergely is on vacation this week. I will ping him and Mark on Monday to see whether they would be available to check back on this next Tuesday on the weekly call. Would this plan work or you had a separate meeting in mind?

Thanks,
Ildikó


On 2018. Oct 3., at 20:23, Waines, Greg <Greg.Waines at windriver.com<mailto:Greg.Waines at windriver.com>> wrote:
Just curious ...

Will there be an update from Gergely and/or MarkB. on Federated Keystone Testing ?

I have done some evaluation testing on Federated Keystone with testshib and am interested in comparing results.

Greg.


From: Ildiko Vancsa <ildiko at openstack.org<mailto:ildiko at openstack.org>>
Date: Tuesday, October 2, 2018 at 8:37 AM
To: edge-computing <edge-computing at lists.openstack.org<mailto:edge-computing at lists.openstack.org>>
Subject: [Edge-computing] Weekly call in APAC slot this week

Hi,

It is a friendly reminder that we are having our weekly call this week in the APAC friendly time slot, on Thursday (October4), 0700 UTC.

Please see the wiki for details: https://wiki.openstack.org/wiki/Edge_Computing_Group#Meetings

Thanks and Best Regards,
Ildikó



_______________________________________________
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/20181003/ad788fb0/attachment-0001.html>

From ildiko at openstack.org  Wed Oct  3 19:25:24 2018
From: ildiko at openstack.org (Ildiko Vancsa)
Date: Wed, 3 Oct 2018 21:25:24 +0200
Subject: [Edge-computing] Weekly call in APAC slot this week
In-Reply-To: <579CFAFE-10E7-485B-9C6A-9CB59BFE6B9F@windriver.com>
References: <6BC7E46B-9D90-43CD-B0A9-AE634705ACC1@openstack.org>
 <D6272FD3-0211-40BA-A099-6AEB41DAE1F2@windriver.com>
 <4662AC03-44B1-4628-89C9-524D35FBD8D0@openstack.org>
 <579CFAFE-10E7-485B-9C6A-9CB59BFE6B9F@windriver.com>
Message-ID: <E2A05438-B8D0-423C-967D-2D35E6FBBF2B@openstack.org>

Great, thank you.

I’m also working on moving James’s document on the MVP architecure over to the wiki. I hope to get there tomorrow to finish and then we can iterate on it easier from there.

Thanks,
Ildikó


> On 2018. Oct 3., at 21:04, Waines, Greg <Greg.Waines at windriver.com> wrote:
> 
> That works ... I can wait til next Tuesday.
> Thanks,
> Greg.
>  
> From: Ildiko Vancsa <ildiko at openstack.org>
> Date: Wednesday, October 3, 2018 at 2:54 PM
> To: Greg Waines <Greg.Waines at windriver.com>
> Cc: edge-computing <edge-computing at lists.openstack.org>
> Subject: Re: [Edge-computing] Weekly call in APAC slot this week
>  
> Hi Greg,
>  
> Gergely is on vacation this week. I will ping him and Mark on Monday to see whether they would be available to check back on this next Tuesday on the weekly call. Would this plan work or you had a separate meeting in mind?
>  
> Thanks,
> Ildikó
>  
>  
> On 2018. Oct 3., at 20:23, Waines, Greg <Greg.Waines at windriver.com> wrote:
> Just curious ...
>   
> Will there be an update from Gergely and/or MarkB. on Federated Keystone Testing ?
>   
> I have done some evaluation testing on Federated Keystone with testshib and am interested in comparing results.
>   
> Greg. 
>   
>   
> From: Ildiko Vancsa <ildiko at openstack.org>
> Date: Tuesday, October 2, 2018 at 8:37 AM
> To: edge-computing <edge-computing at lists.openstack.org>
> Subject: [Edge-computing] Weekly call in APAC slot this week
>   
> Hi,
>   
> It is a friendly reminder that we are having our weekly call this week in the APAC friendly time slot, on Thursday (October4), 0700 UTC.
>   
> Please see the wiki for details: https://wiki.openstack.org/wiki/Edge_Computing_Group#Meetings
>   
> Thanks and Best Regards,
> Ildikó
>   
>   
>   
> _______________________________________________
> Edge-computing mailing list
> Edge-computing at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
>   
>  
>  



From ildiko at openstack.org  Thu Oct  4 19:54:51 2018
From: ildiko at openstack.org (Ildiko Vancsa)
Date: Thu, 4 Oct 2018 21:54:51 +0200
Subject: [Edge-computing] Rescheduling and alternating the Use cases
 weekly call
In-Reply-To: <6FEB690C-6AC4-4791-8187-C078B7E4FF13@openstack.org>
References: <6FEB690C-6AC4-4791-8187-C078B7E4FF13@openstack.org>
Message-ID: <4EB5E3A7-018E-4981-8B95-5E31D4594A84@openstack.org>

Hi,

Based on the current results of the poll the two preferred slots so far:

* Monday, 8am US Eastern
* Monday, 8pm US Eastern

In case you would like to participate in these weekly calls and have another preference please make sure you fill out the Doodle poll as soon as possible: https://doodle.com/poll/cdc8sgc6hwu6hqgw

Do we want to start to alternate already next Monday? In case we do I suggest to start with the 8am Eastern slot as next Monday is holiday in Japan.

Please let me know your thoughts.

Thanks,
Ildikó


> On 2018. Oct 3., at 14:29, Ildiko Vancsa <ildiko at openstack.org> wrote:
> 
> Hi,
> 
> As it came up earlier it is important to be inclusive and provide possibilities for everyone around the globe to participate in our activities.
> 
> Our Use cases weekly calls are in a very inconvenient time slot for both Europe and APAC therefore we decided to look for better time slots and also alternate them for a better coverage.
> 
> I created a Doodle poll with a few time slots in the morning in the States as well as for the afternoon which should provide better options on other continents as well. If you’re interested in joining this call please fill out the form as soon as possible. Please avoid the dates and mark every slot that can work for you in general: https://doodle.com/poll/cdc8sgc6hwu6hqgw
> 
> Please let me know if you have any questions.
> 
> Thanks and Best Regards,
> Ildikó
> 
> 
> 
> _______________________________________________
> Edge-computing mailing list
> Edge-computing at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing



From Mark.Beierl at dell.com  Fri Oct  5 14:34:54 2018
From: Mark.Beierl at dell.com (Beierl, Mark)
Date: Fri, 5 Oct 2018 14:34:54 +0000
Subject: [Edge-computing] Rescheduling and alternating the Use cases
 weekly call
In-Reply-To: <4EB5E3A7-018E-4981-8B95-5E31D4594A84@openstack.org>
References: <6FEB690C-6AC4-4791-8187-C078B7E4FF13@openstack.org>
 <4EB5E3A7-018E-4981-8B95-5E31D4594A84@openstack.org>
Message-ID: <E16E42B2-F159-4F68-8DF4-385A396CDF2A@emc.com>

Hello, Ildiko,

As Monday is a holiday in Canada as well, I will not be able to attend either way, sorry.

Regards,
Mark
 
Mark Beierl
SW System Sr Principal Developer
Dell EMC | Cloud & Communication Service Provider Solution
Mark.Beierl at Dell.com

On 2018-10-04, 15:54, "Ildiko Vancsa" <ildiko at openstack.org> wrote:

    
    [EXTERNAL EMAIL] 
    Please report any suspicious attachments, links, or requests for sensitive information.
    
    
    Hi,
    
    Based on the current results of the poll the two preferred slots so far:
    
    * Monday, 8am US Eastern
    * Monday, 8pm US Eastern
    
    In case you would like to participate in these weekly calls and have another preference please make sure you fill out the Doodle poll as soon as possible: https://doodle.com/poll/cdc8sgc6hwu6hqgw
    
    Do we want to start to alternate already next Monday? In case we do I suggest to start with the 8am Eastern slot as next Monday is holiday in Japan.
    
    Please let me know your thoughts.
    
    Thanks,
    Ildikó
    
    
    > On 2018. Oct 3., at 14:29, Ildiko Vancsa <ildiko at openstack.org> wrote:
    > 
    > Hi,
    > 
    > As it came up earlier it is important to be inclusive and provide possibilities for everyone around the globe to participate in our activities.
    > 
    > Our Use cases weekly calls are in a very inconvenient time slot for both Europe and APAC therefore we decided to look for better time slots and also alternate them for a better coverage.
    > 
    > I created a Doodle poll with a few time slots in the morning in the States as well as for the afternoon which should provide better options on other continents as well. If you’re interested in joining this call please fill out the form as soon as possible. Please avoid the dates and mark every slot that can work for you in general: https://doodle.com/poll/cdc8sgc6hwu6hqgw
    > 
    > Please let me know if you have any questions.
    > 
    > Thanks and Best Regards,
    > Ildikó
    > 
    > 
    > 
    > _______________________________________________
    > 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 beth.cohen at verizon.com  Mon Oct  8 20:13:02 2018
From: beth.cohen at verizon.com (beth.cohen at verizon.com)
Date: Mon, 8 Oct 2018 20:13:02 +0000
Subject: [Edge-computing] Invitation: Edge Computing - Use Case Meeting @
 Weekly from 8 AM to 9AM on Monday (EST)
 (edge-computing@lists.openstack.org)
Message-ID: <7da5b0148bdf44e09fe36f0011b0dbb2@scwexch25apd.uswin.ad.vzwcorp.com>

Folks -
Join us as we work through the details of the edge use cases.  This is the APAC friendly time.  It will alternate with the EMEA friendly time.

Monday 8AM EST - EMEA and US
Monday 8PM EST - APAC and US
*       https://wiki.openstack.org/wiki/Edge_Computing_Group/Use_Cases
*       https://etherpad.openstack.org/p/edge-use-case
 Weekly calls on Mondays at 1pm PDT / 2000 UTC

Zoom link: https://zoom.us/j/879678938
Dialing in from phone:
   Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923
   Meeting ID: 879 678 938
   International numbers available: https://zoom.us/u/ed95sU7aQ


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/edge-computing/attachments/20181008/08a185a5/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/calendar
Size: 4690 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/edge-computing/attachments/20181008/08a185a5/attachment-0001.ics>

From beth.cohen at verizon.com  Mon Oct  8 20:16:42 2018
From: beth.cohen at verizon.com (beth.cohen at verizon.com)
Date: Mon, 8 Oct 2018 20:16:42 +0000
Subject: [Edge-computing] Invitation: Edge Computing - Use Case Meeting @
 Weekly from 8 PM to PAM on Monday (EST)
 (edge-computing@lists.openstack.org)
Message-ID: <e4c8e4163ea04d01841c2d643092a58a@scwexch25apd.uswin.ad.vzwcorp.com>

Folks -
Join us as we work through the details of the edge use cases.  This is the EMEA friendly time.  It will alternate with the APAC friendly time.

Monday 8AM EST - EMEA and US
Monday 8PM EST - APAC and US
*       https://wiki.openstack.org/wiki/Edge_Computing_Group/Use_Cases
*       https://etherpad.openstack.org/p/edge-use-case
 Weekly calls on Mondays at 1pm PDT / 2000 UTC

Zoom link: https://zoom.us/j/879678938
Dialing in from phone:
   Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923
   Meeting ID: 879 678 938
   International numbers available: https://zoom.us/u/ed95sU7aQ


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/edge-computing/attachments/20181008/f3e73233/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/calendar
Size: 4690 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/edge-computing/attachments/20181008/f3e73233/attachment.ics>

From gergely.csatari at nokia.com  Mon Oct 15 10:49:52 2018
From: gergely.csatari at nokia.com (Csatari, Gergely (Nokia - HU/Budapest))
Date: Mon, 15 Oct 2018 10:49:52 +0000
Subject: [Edge-computing] [edge][keystone][ptg]: Keystone edge architectures
	wiki updated
Message-ID: <HE1PR07MB1722519971C45E50E9A7A03FE1FD0@HE1PR07MB1722.eurprd07.prod.outlook.com>

Hi,

I've updated the Keystone edge architectures wiki [1<https://wiki.openstack.org/wiki/Keystone_edge_architectures>] based on the notes [2<https://etherpad.openstack.org/p/keystone-stein-edge-architecture>] we generated in the Denver workshop.

Please check and comment.

Thanks,
Gerg0

[1]: https://wiki.openstack.org/wiki/Keystone_edge_architectures
[2]: https://etherpad.openstack.org/p/keystone-stein-edge-architecture

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

From gergely.csatari at nokia.com  Mon Oct 15 11:29:05 2018
From: gergely.csatari at nokia.com (Csatari, Gergely (Nokia - HU/Budapest))
Date: Mon, 15 Oct 2018 11:29:05 +0000
Subject: [Edge-computing] [edge][glance][ptg]: Image handling wiki updated
Message-ID: <HE1PR07MB17221E8CEF3C38FF80B4D2AFE1FD0@HE1PR07MB1722.eurprd07.prod.outlook.com>

Hi,

I've updated the Image handling in edge environment wiki [1<https://wiki.openstack.org/wiki/Image_handling_in_edge_environment>] based on the notes [2<https://etherpad.openstack.org/p/glance-stein-edge-architecture>] from the Denver ptg discussions.

Please check and comment.

Thanks,
Gerg0

[1]: https://wiki.openstack.org/wiki/Image_handling_in_edge_environment
[2]: https://etherpad.openstack.org/p/glance-stein-edge-architecture
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/edge-computing/attachments/20181015/27edb8cb/attachment-0001.html>

From claire at openstack.org  Mon Oct 15 19:54:20 2018
From: claire at openstack.org (Claire Massey)
Date: Mon, 15 Oct 2018 14:54:20 -0500
Subject: [Edge-computing] October 24 OSF Community Mtg: StarlingX First
	Release
Message-ID: <1284B9B5-6C33-46A4-A8DF-EC84BDEE8569@openstack.org>

Hi everyone,

For the upcoming OpenStack Foundation Community Meeting[1] we will focus on the StarlingX project and edge computing. 

Please join us on *October 24 at 8:00am PDT* for a StarlingX community on-boarding webinar that's scheduled to coincide with the first release for the StarlingX project. Ian Jolliffe and Bruce Jones will lead the project on-boarding presentation followed by Q&A. Please mark your calendars and plan to join us. Meeting link: https://zoom.us/j/112003649 <https://zoom.us/j/112003649>. 

More information and news around the StarlingX first release will be shared on October 24. In the meantime you can learn more and get involved with StarlingX though theses channels:
	• Website: starlingx.io <http://starlingx.io/>
	• Git: git.starlingx.io <http://git.starlingx.io/>
	• Docs: docs.starlingx.io <http://docs.starlingx.io/>
	• Freenode IRC: #starlingx
	• Mailing Lists: lists.starlingx.io <http://lists.starlingx.io/>
Thanks,
Claire


[1] https://etherpad.openstack.org/p/openstack-community-meeting <https://etherpad.openstack.org/p/openstack-community-meeting>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/edge-computing/attachments/20181015/2941a7ca/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Mail Attachment.ics
Type: text/calendar
Size: 3160 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/edge-computing/attachments/20181015/2941a7ca/attachment.ics>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/edge-computing/attachments/20181015/2941a7ca/attachment-0001.html>

From beth.cohen at verizon.com  Mon Oct 15 19:50:59 2018
From: beth.cohen at verizon.com (beth.cohen at verizon.com)
Date: Mon, 15 Oct 2018 19:50:59 +0000
Subject: [Edge-computing] Canceled: Invitation: Edge Computing - Use Case
 Meeting @ Weekly from 1pm to 2pm on Monday (PDT)
 (edge-computing@lists.openstack.org)
Message-ID: <459faaeb060b459786f6f9dcaa5dfc43@scwexch25apd.uswin.ad.vzwcorp.com>

This meeting has been replaced with two meetings that alternate times.

Monday 8AM EST – EMEA and US
Monday 8PM EST – APAC and US
•       https://wiki.openstack.org/wiki/Edge_Computing_Group/Use_Cases
•       https://etherpad.openstack.org/p/edge-use-case
 Weekly calls on Mondays at 1pm PDT / 2000 UTC

Zoom link: https://zoom.us/j/879678938
Dialing in from phone:
   Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923
   Meeting ID: 879 678 938
   International numbers available: https://zoom.us/u/ed95sU7aQ


Folks –
Join us as we work through the details of the edge use cases.
•       https://wiki.openstack.org/wiki/Edge_Computing_Group/Use_Cases
•       https://etherpad.openstack.org/p/edge-use-case
 Weekly calls on Mondays at 1pm PDT / 2000 UTC

Zoom link: https://zoom.us/j/879678938
Dialing in from phone:
   Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923
   Meeting ID: 879 678 938
   International numbers available: https://zoom.us/u/ed95sU7aQ




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/edge-computing/attachments/20181015/2e6d876f/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/calendar
Size: 7744 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/edge-computing/attachments/20181015/2e6d876f/attachment-0001.ics>

From ildiko at openstack.org  Tue Oct 16 13:00:54 2018
From: ildiko at openstack.org (Ildiko Vancsa)
Date: Tue, 16 Oct 2018 15:00:54 +0200
Subject: [Edge-computing] MVP Architecture doc on the wiki
Message-ID: <1F196899-A4A6-4727-B0A9-5F2CBCB40E1E@openstack.org>

Hi,

I moved over James Penick’s (Thanks James!) notes from a Google Doc to the wiki with a little bit of structure to cover what we’ve discussed on the last PTG in Denver.

You can find the overall architecture diagrams and notes here: https://wiki.openstack.org/wiki/Edge_Computing_Group/Edge_Reference_Architectures

The Keystone federation scenario is captured here: https://wiki.openstack.org/wiki/Keystone_edge_architectures#Identity_Provider_.28IdP.29_Master_with_shadow_users

For the Glance scenario please check the following wiki: https://wiki.openstack.org/wiki/Image_handling_in_edge_environment#Edge_Scenarios_for_Glance

We can continue to discuss the notes and open questions on the weekly call along with preparing for the Summit which will be held in Berlin in less than a month.

The call today is at 1400 UTC, for dial-in info please check this wiki: https://wiki.openstack.org/wiki/Edge_Computing_Group#Meetings

Please let me know if you have any questions or comments.

Thanks and Best Regards,
Ildikó




From gergely.csatari at nokia.com  Fri Oct 19 08:05:24 2018
From: gergely.csatari at nokia.com (Csatari, Gergely (Nokia - HU/Budapest))
Date: Fri, 19 Oct 2018 08:05:24 +0000
Subject: [Edge-computing] [openstack-dev] [Openstack-sigs] [FEMDC]
 [Edge] [tripleo] On the use of terms "Edge" and "Far Edge"
In-Reply-To: <CAJCXu8fBFUHwbiMM3nf81GTOwVoXP5uoFaNx612xKju9aZ4m3A@mail.gmail.com>
References: <713a4c9a-d628-ee6d-49e8-c8e9763cdbfe@redhat.com>
 <CAJCXu8ebO4kpNGcFFHh39jAoKkAkSbnaPXz4h37bFJfsTZDoxQ@mail.gmail.com>
 <CAE66OMASyg1xJxoVT9wevmSpCUENVyHJ21mi5UasRKn6OPSSsw@mail.gmail.com>
 <CAJCXu8fBFUHwbiMM3nf81GTOwVoXP5uoFaNx612xKju9aZ4m3A@mail.gmail.com>
Message-ID: <HE1PR07MB172281F95F7CC131EE93AE76E1F90@HE1PR07MB1722.eurprd07.prod.outlook.com>

Hi,

I’m adding the ECG mailing list to the discussion.

I think the root of the problem is that there is no single definition of „the edge” (except for [1<https://en.wikipedia.org/wiki/The_Edge>]), but it changes from group to group or use case to use case. What I recognise as the commonalities in these edge definitions, are 1) a distributed cloud infrastructure (kind of a cloud of clouds) 2) need for automation or everything 3) resource constraints for the control plane.

The different edge variants are putting different emphasis on these common needs based ont he use case discussed.

To have a more clear understanding of these definitions we could try the following:

  1.  Always add the definition of these to the given context
  2.  Check what other groups are using and adopt to that
  3.  Define our own language and expect everyone else to adopt

Br,
Gerg0



[1]: https://en.wikipedia.org/wiki/The_Edge

From: Jim Rollenhagen <jim at jimrollenhagen.com>
Sent: Thursday, October 18, 2018 11:43 PM
To: fulton at redhat.com; OpenStack Development Mailing List (not for usage questions) <openstack-dev at lists.openstack.org>
Cc: openstack-sigs at lists.openstack.org
Subject: Re: [openstack-dev] [Openstack-sigs] [FEMDC] [Edge] [tripleo] On the use of terms "Edge" and "Far Edge"

On Thu, Oct 18, 2018 at 4:45 PM John Fulton <johfulto at redhat.com<mailto:johfulto at redhat.com>> wrote:
On Thu, Oct 18, 2018 at 11:56 AM Jim Rollenhagen <jim at jimrollenhagen.com<mailto:jim at jimrollenhagen.com>> wrote:
>
> On Thu, Oct 18, 2018 at 10:23 AM Dmitry Tantsur <dtantsur at redhat.com<mailto:dtantsur at redhat.com>> wrote:
>>
>> Hi all,
>>
>> Sorry for chiming in really late in this topic, but I think $subj is worth
>> discussing until we settle harder on the potentially confusing terminology.
>>
>> I think the difference between "Edge" and "Far Edge" is too vague to use these
>> terms in practice. Think about the "edge" metaphor itself: something rarely has
>> several layers of edges. A knife has an edge, there are no far edges. I imagine
>> zooming in and seeing more edges at the edge, and then it's quite cool indeed,
>> but is it really a useful metaphor for those who never used a strong microscope? :)
>>
>> I think in the trivial sense "Far Edge" is a tautology, and should be avoided.
>> As a weak proof of my words, I already see a lot of smart people confusing these
>> two and actually use Central/Edge where they mean Edge/Far Edge. I suggest we
>> adopt a different terminology, even if it less consistent with typical marketing
>> term around the "Edge" movement.
>
>
> FWIW, we created rough definitions of "edge" and "far edge" during the edge WG session in Denver.
> It's mostly based on latency to the end user, though we also talked about quantities of compute resources, if someone can find the pictures.

Perhaps these are the pictures Jim was referring to?
 https://www.dropbox.com/s/255x1cao14taer3/MVP-Architecture_edge-computing_PTG.pptx?dl=0#<https://www.dropbox.com/s/255x1cao14taer3/MVP-Architecture_edge-computing_PTG.pptx?dl=0>

That's it, thank you!

// jim



I'm involved in some TripleO work called the split control plane:
  https://specs.openstack.org/openstack/tripleo-specs/specs/rocky/split-controlplane.html

After the PTG I saw that the split control plane was compatible with
the type of deployment discussed at the edge WG session in Denver and
described the compatibility at:
  https://etherpad.openstack.org/p/tripleo-edge-working-group-split-control-plane

> See the picture and table here: https://wiki.openstack.org/wiki/Edge_Computing_Group/Edge_Reference_Architectures#Overview
>
>> Now, I don't have really great suggestions. Something that came up in TripleO
>> discussions [1] is Core/Hub/Edge, which I think reflects the idea better.
>
>
> I'm also fine with these names, as they do describe the concepts well. :)
>
> // jim

I'm fine with these terms too. In split control plane there's a
deployment method for deploying a central site and then deploying
remote sites independently. That deployment method could be used to
deploy  Core/Hub/Edge sites too. E.g. deploy the Core using Heat stack
N. Deploy a Hub using stack N+1 and then deploy an Edge using stack
N+2 etc.

  John

>>
>> I'd be very interested to hear your ideas.
>>
>> Dmitry
>>
>> [1] https://etherpad.openstack.org/p/tripleo-edge-mvp
>>
>> _______________________________________________
>> openstack-sigs mailing list
>> openstack-sigs at lists.openstack.org<mailto:openstack-sigs at lists.openstack.org>
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe<http://OpenStack-dev-request at lists.openstack.org?subject:unsubscribe>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe<http://OpenStack-dev-request at lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/edge-computing/attachments/20181019/74be9d4d/attachment-0001.html>

From tpeluso at equinix.com  Fri Oct 19 15:38:33 2018
From: tpeluso at equinix.com (Teresa Peluso)
Date: Fri, 19 Oct 2018 15:38:33 +0000
Subject: [Edge-computing] [openstack-dev] [Openstack-sigs] [FEMDC]
 [Edge] [tripleo] On the use of terms "Edge" and "Far Edge"
In-Reply-To: <HE1PR07MB172281F95F7CC131EE93AE76E1F90@HE1PR07MB1722.eurprd07.prod.outlook.com>
References: <713a4c9a-d628-ee6d-49e8-c8e9763cdbfe@redhat.com>
 <CAJCXu8ebO4kpNGcFFHh39jAoKkAkSbnaPXz4h37bFJfsTZDoxQ@mail.gmail.com>
 <CAE66OMASyg1xJxoVT9wevmSpCUENVyHJ21mi5UasRKn6OPSSsw@mail.gmail.com>
 <CAJCXu8fBFUHwbiMM3nf81GTOwVoXP5uoFaNx612xKju9aZ4m3A@mail.gmail.com>
 <HE1PR07MB172281F95F7CC131EE93AE76E1F90@HE1PR07MB1722.eurprd07.prod.outlook.com>
Message-ID: <BY1PR0401MB1350FCABDEF1BF76C8917285A6F90@BY1PR0401MB1350.namprd04.prod.outlook.com>

Fyi – could this help?  https://www.linuxfoundation.org/blog/2018/06/edge-computing-just-got-its-rosetta-stone/

https://imasons.org/ starting to host workshops about this as well https://imasons.org/events/2018-im-edge-congress/

From: Csatari, Gergely (Nokia - HU/Budapest) <gergely.csatari at nokia.com>
Sent: Friday, October 19, 2018 1:05 AM
To: OpenStack Development Mailing List (not for usage questions) <openstack-dev at lists.openstack.org>; fulton at redhat.com; edge-computing at lists.openstack.org
Cc: openstack-sigs at lists.openstack.org
Subject: [EXTERNAL] Re: [Edge-computing] [openstack-dev] [Openstack-sigs] [FEMDC] [Edge] [tripleo] On the use of terms "Edge" and "Far Edge"

Hi,

I’m adding the ECG mailing list to the discussion.

I think the root of the problem is that there is no single definition of „the edge” (except for [1<https://urldefense.proofpoint.com/v2/url?u=https-3A__en.wikipedia.org_wiki_The-5FEdge&d=DwMGaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=JcbYkw8s_8JtubERIbsy_0Qc_q0zGK9nUrtf2IWVNmQ&m=VtNo9cSRcnVhW9PH68IA26gNRrJ96V0O7MHTeONQ-hY&s=J6lr_T9m7mkisVR7l1QzmBki20r5He3fuZXvbYg-EPs&e=>]), but it changes from group to group or use case to use case. What I recognise as the commonalities in these edge definitions, are 1) a distributed cloud infrastructure (kind of a cloud of clouds) 2) need for automation or everything 3) resource constraints for the control plane.

The different edge variants are putting different emphasis on these common needs based ont he use case discussed.

To have a more clear understanding of these definitions we could try the following:

  1.  Always add the definition of these to the given context
  2.  Check what other groups are using and adopt to that
  3.  Define our own language and expect everyone else to adopt

Br,
Gerg0



[1]: https://en.wikipedia.org/wiki/The_Edge<https://urldefense.proofpoint.com/v2/url?u=https-3A__en.wikipedia.org_wiki_The-5FEdge&d=DwQGaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=JcbYkw8s_8JtubERIbsy_0Qc_q0zGK9nUrtf2IWVNmQ&m=VtNo9cSRcnVhW9PH68IA26gNRrJ96V0O7MHTeONQ-hY&s=J6lr_T9m7mkisVR7l1QzmBki20r5He3fuZXvbYg-EPs&e=>

From: Jim Rollenhagen <jim at jimrollenhagen.com<mailto:jim at jimrollenhagen.com>>
Sent: Thursday, October 18, 2018 11:43 PM
To: fulton at redhat.com<mailto:fulton at redhat.com>; OpenStack Development Mailing List (not for usage questions) <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Cc: openstack-sigs at lists.openstack.org<mailto:openstack-sigs at lists.openstack.org>
Subject: Re: [openstack-dev] [Openstack-sigs] [FEMDC] [Edge] [tripleo] On the use of terms "Edge" and "Far Edge"

On Thu, Oct 18, 2018 at 4:45 PM John Fulton <johfulto at redhat.com<mailto:johfulto at redhat.com>> wrote:
On Thu, Oct 18, 2018 at 11:56 AM Jim Rollenhagen <jim at jimrollenhagen.com<mailto:jim at jimrollenhagen.com>> wrote:
>
> On Thu, Oct 18, 2018 at 10:23 AM Dmitry Tantsur <dtantsur at redhat.com<mailto:dtantsur at redhat.com>> wrote:
>>
>> Hi all,
>>
>> Sorry for chiming in really late in this topic, but I think $subj is worth
>> discussing until we settle harder on the potentially confusing terminology.
>>
>> I think the difference between "Edge" and "Far Edge" is too vague to use these
>> terms in practice. Think about the "edge" metaphor itself: something rarely has
>> several layers of edges. A knife has an edge, there are no far edges. I imagine
>> zooming in and seeing more edges at the edge, and then it's quite cool indeed,
>> but is it really a useful metaphor for those who never used a strong microscope? :)
>>
>> I think in the trivial sense "Far Edge" is a tautology, and should be avoided.
>> As a weak proof of my words, I already see a lot of smart people confusing these
>> two and actually use Central/Edge where they mean Edge/Far Edge. I suggest we
>> adopt a different terminology, even if it less consistent with typical marketing
>> term around the "Edge" movement.
>
>
> FWIW, we created rough definitions of "edge" and "far edge" during the edge WG session in Denver.
> It's mostly based on latency to the end user, though we also talked about quantities of compute resources, if someone can find the pictures.

Perhaps these are the pictures Jim was referring to?
 https://www.dropbox.com/s/255x1cao14taer3/MVP-Architecture_edge-computing_PTG.pptx?dl=0#<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.dropbox.com_s_255x1cao14taer3_MVP-2DArchitecture-5Fedge-2Dcomputing-5FPTG.pptx-3Fdl-3D0&d=DwMGaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=JcbYkw8s_8JtubERIbsy_0Qc_q0zGK9nUrtf2IWVNmQ&m=VtNo9cSRcnVhW9PH68IA26gNRrJ96V0O7MHTeONQ-hY&s=Zh9LBq_sTlZxC5xI7FupdttxdRrhrwmoIsY4eZRlvjM&e=>

That's it, thank you!

// jim



I'm involved in some TripleO work called the split control plane:
  https://specs.openstack.org/openstack/tripleo-specs/specs/rocky/split-controlplane.html<https://urldefense.proofpoint.com/v2/url?u=https-3A__specs.openstack.org_openstack_tripleo-2Dspecs_specs_rocky_split-2Dcontrolplane.html&d=DwMGaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=JcbYkw8s_8JtubERIbsy_0Qc_q0zGK9nUrtf2IWVNmQ&m=VtNo9cSRcnVhW9PH68IA26gNRrJ96V0O7MHTeONQ-hY&s=tuDTh6QOmYEza4K8a7S2RoUpc1ttgBTHVC8re5vfcdg&e=>

After the PTG I saw that the split control plane was compatible with
the type of deployment discussed at the edge WG session in Denver and
described the compatibility at:
  https://etherpad.openstack.org/p/tripleo-edge-working-group-split-control-plane<https://urldefense.proofpoint.com/v2/url?u=https-3A__etherpad.openstack.org_p_tripleo-2Dedge-2Dworking-2Dgroup-2Dsplit-2Dcontrol-2Dplane&d=DwMGaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=JcbYkw8s_8JtubERIbsy_0Qc_q0zGK9nUrtf2IWVNmQ&m=VtNo9cSRcnVhW9PH68IA26gNRrJ96V0O7MHTeONQ-hY&s=5Ak84Rb4c98_jEqNWjvWYCeVAN0XkbZzdXVWax9oo_Q&e=>

> See the picture and table here: https://wiki.openstack.org/wiki/Edge_Computing_Group/Edge_Reference_Architectures#Overview<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.openstack.org_wiki_Edge-5FComputing-5FGroup_Edge-5FReference-5FArchitectures-23Overview&d=DwMGaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=JcbYkw8s_8JtubERIbsy_0Qc_q0zGK9nUrtf2IWVNmQ&m=VtNo9cSRcnVhW9PH68IA26gNRrJ96V0O7MHTeONQ-hY&s=yqEH7weN-I2YvoYDRi6nSWGtNzQsX-HfBieGuOBow1M&e=>
>
>> Now, I don't have really great suggestions. Something that came up in TripleO
>> discussions [1] is Core/Hub/Edge, which I think reflects the idea better.
>
>
> I'm also fine with these names, as they do describe the concepts well. :)
>
> // jim

I'm fine with these terms too. In split control plane there's a
deployment method for deploying a central site and then deploying
remote sites independently. That deployment method could be used to
deploy  Core/Hub/Edge sites too. E.g. deploy the Core using Heat stack
N. Deploy a Hub using stack N+1 and then deploy an Edge using stack
N+2 etc.

  John

>>
>> I'd be very interested to hear your ideas.
>>
>> Dmitry
>>
>> [1] https://etherpad.openstack.org/p/tripleo-edge-mvp<https://urldefense.proofpoint.com/v2/url?u=https-3A__etherpad.openstack.org_p_tripleo-2Dedge-2Dmvp&d=DwMGaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=JcbYkw8s_8JtubERIbsy_0Qc_q0zGK9nUrtf2IWVNmQ&m=VtNo9cSRcnVhW9PH68IA26gNRrJ96V0O7MHTeONQ-hY&s=XI1J9s1i2KxUSnOX9Yk3XQ_5kH08UoWZ_uqd6Y3efQU&e=>
>>
>> _______________________________________________
>> openstack-sigs mailing list
>> openstack-sigs at lists.openstack.org<mailto:openstack-sigs at lists.openstack.org>
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs<https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_openstack-2Dsigs&d=DwMGaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=JcbYkw8s_8JtubERIbsy_0Qc_q0zGK9nUrtf2IWVNmQ&m=VtNo9cSRcnVhW9PH68IA26gNRrJ96V0O7MHTeONQ-hY&s=TmAFzLOVMjHTW569gUKwSRI4OwLlF5tOqAlcYuPaCHM&e=>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe<https://urldefense.proofpoint.com/v2/url?u=http-3A__OpenStack-2Ddev-2Drequest-40lists.openstack.org-3Fsubject-3Aunsubscribe&d=DwMGaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=JcbYkw8s_8JtubERIbsy_0Qc_q0zGK9nUrtf2IWVNmQ&m=VtNo9cSRcnVhW9PH68IA26gNRrJ96V0O7MHTeONQ-hY&s=fH-cGOV9QxQ5JB6p2hhzcysjmij8hCyy3ptvz6tystU&e=>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_openstack-2Ddev&d=DwMGaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=JcbYkw8s_8JtubERIbsy_0Qc_q0zGK9nUrtf2IWVNmQ&m=VtNo9cSRcnVhW9PH68IA26gNRrJ96V0O7MHTeONQ-hY&s=161pS98mNzJwzSvHGBh3w1L6xADUAa9R08Qf-LQEjUQ&e=>

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe<https://urldefense.proofpoint.com/v2/url?u=http-3A__OpenStack-2Ddev-2Drequest-40lists.openstack.org-3Fsubject-3Aunsubscribe&d=DwMGaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=JcbYkw8s_8JtubERIbsy_0Qc_q0zGK9nUrtf2IWVNmQ&m=VtNo9cSRcnVhW9PH68IA26gNRrJ96V0O7MHTeONQ-hY&s=fH-cGOV9QxQ5JB6p2hhzcysjmij8hCyy3ptvz6tystU&e=>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_openstack-2Ddev&d=DwMGaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=JcbYkw8s_8JtubERIbsy_0Qc_q0zGK9nUrtf2IWVNmQ&m=VtNo9cSRcnVhW9PH68IA26gNRrJ96V0O7MHTeONQ-hY&s=161pS98mNzJwzSvHGBh3w1L6xADUAa9R08Qf-LQEjUQ&e=>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/edge-computing/attachments/20181019/4b140cb6/attachment-0001.html>

From fdelicato at gmail.com  Mon Oct 22 13:44:35 2018
From: fdelicato at gmail.com (Flavia Delicato)
Date: Mon, 22 Oct 2018 10:44:35 -0300
Subject: [Edge-computing] IEEE Fog Computing: Call for Contributions -
	Deadline Approaching
Message-ID: <CAKe3RKoGZ+ejL-mfhB1dAROkKC=OBbf2b8kizQHJw3GJUzWqcw@mail.gmail.com>

=================================================================================
IEEE International Conference on Fog Computing (ICFC 2019)
June 24-26, 2019
Prague, Czech Republic
http://conferences.computer.org/ICFC/2019/
Co-located with the IEEE International Conference on Cloud Engineering
(IC2E 2019)
==================================================================================

Important Dates
---------------
Paper registration and abstract: Nov 1st, 2018
Full paper submission due: Nov 8th, 2018
Notification of paper acceptance: Jan. 20th, 2019
Workshop and tutorial proposals due: Nov 11, 2018
Notification of proposal acceptance: Nov 18, 2018

Call for Contributions
----------------------
Fog computing is the extension of cloud computing into its edge and
the physical world to meet the data volume and decision velocity
requirements in many emerging applications, such as augmented and
virtual realities (AR/VR), cyber-physical systems (CPS), intelligent
and autonomous systems, and mission-critical systems. The boundary
between centralized, powerful computing cloud and massively
distributed, Internet connected sensors, actuators, and things is
blurred in this new computing paradigm.

The ICFC 2019 technical program will feature tutorials, workshops, and
research paper sessions. We solicit high-quality contributions in the
above categories. Details of submission is available on the conference
Web site. Topics of interest include but are not limited to:

* System architecture for fog computing
* Coordination between cloud, fog, and sensing/actuation endpoints
* Connectivity, storage, and computation in the edge
* Data processing and management for fog computing
* Efficient and embedded AI in the fog
* System and network manageability
* Middleware and coordination platforms
* Power, energy, and resource management
* Device and hardware support for fog computing
* Programming models, abstractions, and software engineering for fog computing
* Security, privacy, and ethics issues related to fog computing
* Theoretical foundations and formal methods for fog computing systems
* Applications and experiences

Organizing Committee
--------------------
General Chairs:
Hui Lei, IBM
Albert Zomaya, The University of Sydney

PC Co-chairs:
Erol Gelenbe, Imperial College London
Jie Liu, Microsoft Research

Tutorials and Workshops Chair:
David Bermbach, TU Berlin

Publicity Co-chairs:
Flavia Delicato,Federal University of Rio de Janeiro
Mathias Fischer, University Hamburg

Publication Chair
Javid Taheri, Karlstad University

Webmaster
Wei Li, The University of Sydney

Steering Committee
------------------
Mung Chiang, Purdue University
Erol Gelenbe, Imperial College London
Christos Kozarakis, Stanford University
Hui Lei, IBM
Chenyang Lu, Washington University in St Louis
Beng Chin Ooi, National University of Singapore
Neeraj Suri, TU Darmstadt
Albert Zomaya, The University of Sydney

Program Committee
------------------

Tarek Abdelzaher, UIUC
Anne Benoit, ENS Lyon
David Bermbach, TU Berlin
Bharat Bhargava, Purdue University
Olivier Brun, LAAS/CNRS Laboratory
Jiannong Cao, Hong Kong Polytech
Flavia C. Delicato, UFRJ, Brazil
Xiaotie Deng, Peking University, China
Schahram Dustdar, TU Wien, Germany
Maria Gorlatova, Duke University
Dharanipragada Janakiram, IIT Madras
Wenjing Luo, Virginia Tech
Pedro José Marrón, Universität Duisburg-Essen
Geyong Min, University of Exeter
Suman Nath, Microsoft Research
Vincenzo Piuri, Universita Degli Studi Di Milano
Yong Meng Teo, National University of Singapore
Guoliang Xing, Chinese University of Hong Kong
Yuanyuan Yang, SUNY Stony Brook
Xiaoyun Zhu, Cloudera

-- 
Flávia Delicato

Associate Professor
Federal University of Rio de Janeiro
---


From mtrifiro at vapor.io  Tue Oct 23 04:40:57 2018
From: mtrifiro at vapor.io (Matt Trifiro)
Date: Mon, 22 Oct 2018 21:40:57 -0700
Subject: [Edge-computing] [openstack-dev] [Openstack-sigs] [FEMDC]
 [Edge] [tripleo] On the use of terms "Edge" and "Far Edge" (Teresa Peluso)
Message-ID: <CANJ_P_LGe981y+GA3+dSFd_K7J1nKQdd3ziHVajFB+8kH6_+FA@mail.gmail.com>

Teresa Peluso <tpeluso at equinix.com> wrote:

Fyi – could this help?
https://www.linuxfoundation.org/blog/2018/06/edge-computing-just-got-its-
rosetta-stone/

https://imasons.org/ starting to host workshops about this as well
https://imasons.org/events/2018-im-edge-congress/


I am the Chair of the Open Glossary of Edge Computing, the Linux Foundation
project mentioned in the blog post. I would be happy to invite an OpenStack
nominee onto our TSC. We seek to harmonize and define the various flavors
of edge, and OpenStack is doing interesting work and I'd like to see the
communities collaborate. I am also part of the iMasosn effort.

m

On Fri, Oct 19, 2018 at 8:39 AM <edge-computing-request at lists.openstack.org>
wrote:

> Send Edge-computing mailing list submissions to
>         edge-computing at lists.openstack.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
> or, via email, send a message with subject or body 'help' to
>         edge-computing-request at lists.openstack.org
>
> You can reach the person managing the list at
>         edge-computing-owner at lists.openstack.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Edge-computing digest..."
>
>
> Today's Topics:
>
>    1. Re: [openstack-dev] [Openstack-sigs] [FEMDC] [Edge] [tripleo]
>       On the use of terms "Edge" and "Far Edge" (Teresa Peluso)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 19 Oct 2018 15:38:33 +0000
> From: Teresa Peluso <tpeluso at equinix.com>
> To: "Csatari, Gergely (Nokia - HU/Budapest)"
>         <gergely.csatari at nokia.com>, "OpenStack Development Mailing List
> (not
>         for usage questions)" <openstack-dev at lists.openstack.org>,
>         "fulton at redhat.com" <fulton at redhat.com>,
>         "edge-computing at lists.openstack.org"
>         <edge-computing at lists.openstack.org>
> Cc: "openstack-sigs at lists.openstack.org"
>         <openstack-sigs at lists.openstack.org>
> Subject: Re: [Edge-computing] [openstack-dev] [Openstack-sigs] [FEMDC]
>         [Edge] [tripleo] On the use of terms "Edge" and "Far Edge"
> Message-ID:
>         <
> BY1PR0401MB1350FCABDEF1BF76C8917285A6F90 at BY1PR0401MB1350.namprd04.prod.outlook.com
> >
>
> Content-Type: text/plain; charset="utf-8"
>
> Fyi – could this help?
> https://www.linuxfoundation.org/blog/2018/06/edge-computing-just-got-its-rosetta-stone/
>
> https://imasons.org/ starting to host workshops about this as well
> https://imasons.org/events/2018-im-edge-congress/
>
> From: Csatari, Gergely (Nokia - HU/Budapest) <gergely.csatari at nokia.com>
> Sent: Friday, October 19, 2018 1:05 AM
> To: OpenStack Development Mailing List (not for usage questions) <
> openstack-dev at lists.openstack.org>; fulton at redhat.com;
> edge-computing at lists.openstack.org
> Cc: openstack-sigs at lists.openstack.org
> Subject: [EXTERNAL] Re: [Edge-computing] [openstack-dev] [Openstack-sigs]
> [FEMDC] [Edge] [tripleo] On the use of terms "Edge" and "Far Edge"
>
> Hi,
>
> I’m adding the ECG mailing list to the discussion.
>
> I think the root of the problem is that there is no single definition of
> „the edge” (except for [1<
> https://urldefense.proofpoint.com/v2/url?u=https-3A__en.wikipedia.org_wiki_The-5FEdge&d=DwMGaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=JcbYkw8s_8JtubERIbsy_0Qc_q0zGK9nUrtf2IWVNmQ&m=VtNo9cSRcnVhW9PH68IA26gNRrJ96V0O7MHTeONQ-hY&s=J6lr_T9m7mkisVR7l1QzmBki20r5He3fuZXvbYg-EPs&e=>]),
> but it changes from group to group or use case to use case. What I
> recognise as the commonalities in these edge definitions, are 1) a
> distributed cloud infrastructure (kind of a cloud of clouds) 2) need for
> automation or everything 3) resource constraints for the control plane.
>
> The different edge variants are putting different emphasis on these common
> needs based ont he use case discussed.
>
> To have a more clear understanding of these definitions we could try the
> following:
>
>   1.  Always add the definition of these to the given context
>   2.  Check what other groups are using and adopt to that
>   3.  Define our own language and expect everyone else to adopt
>
> Br,
> Gerg0
>
>
>
> [1]: https://en.wikipedia.org/wiki/The_Edge<
> https://urldefense.proofpoint.com/v2/url?u=https-3A__en.wikipedia.org_wiki_The-5FEdge&d=DwQGaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=JcbYkw8s_8JtubERIbsy_0Qc_q0zGK9nUrtf2IWVNmQ&m=VtNo9cSRcnVhW9PH68IA26gNRrJ96V0O7MHTeONQ-hY&s=J6lr_T9m7mkisVR7l1QzmBki20r5He3fuZXvbYg-EPs&e=
> >
>
> From: Jim Rollenhagen <jim at jimrollenhagen.com<mailto:
> jim at jimrollenhagen.com>>
> Sent: Thursday, October 18, 2018 11:43 PM
> To: fulton at redhat.com<mailto:fulton at redhat.com>; OpenStack Development
> Mailing List (not for usage questions) <openstack-dev at lists.openstack.org
> <mailto:openstack-dev at lists.openstack.org>>
> Cc: openstack-sigs at lists.openstack.org<mailto:
> openstack-sigs at lists.openstack.org>
> Subject: Re: [openstack-dev] [Openstack-sigs] [FEMDC] [Edge] [tripleo] On
> the use of terms "Edge" and "Far Edge"
>
> On Thu, Oct 18, 2018 at 4:45 PM John Fulton <johfulto at redhat.com<mailto:
> johfulto at redhat.com>> wrote:
> On Thu, Oct 18, 2018 at 11:56 AM Jim Rollenhagen <jim at jimrollenhagen.com
> <mailto:jim at jimrollenhagen.com>> wrote:
> >
> > On Thu, Oct 18, 2018 at 10:23 AM Dmitry Tantsur <dtantsur at redhat.com
> <mailto:dtantsur at redhat.com>> wrote:
> >>
> >> Hi all,
> >>
> >> Sorry for chiming in really late in this topic, but I think $subj is
> worth
> >> discussing until we settle harder on the potentially confusing
> terminology.
> >>
> >> I think the difference between "Edge" and "Far Edge" is too vague to
> use these
> >> terms in practice. Think about the "edge" metaphor itself: something
> rarely has
> >> several layers of edges. A knife has an edge, there are no far edges. I
> imagine
> >> zooming in and seeing more edges at the edge, and then it's quite cool
> indeed,
> >> but is it really a useful metaphor for those who never used a strong
> microscope? :)
> >>
> >> I think in the trivial sense "Far Edge" is a tautology, and should be
> avoided.
> >> As a weak proof of my words, I already see a lot of smart people
> confusing these
> >> two and actually use Central/Edge where they mean Edge/Far Edge. I
> suggest we
> >> adopt a different terminology, even if it less consistent with typical
> marketing
> >> term around the "Edge" movement.
> >
> >
> > FWIW, we created rough definitions of "edge" and "far edge" during the
> edge WG session in Denver.
> > It's mostly based on latency to the end user, though we also talked
> about quantities of compute resources, if someone can find the pictures.
>
> Perhaps these are the pictures Jim was referring to?
>
> https://www.dropbox.com/s/255x1cao14taer3/MVP-Architecture_edge-computing_PTG.pptx?dl=0#
> <
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.dropbox.com_s_255x1cao14taer3_MVP-2DArchitecture-5Fedge-2Dcomputing-5FPTG.pptx-3Fdl-3D0&d=DwMGaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=JcbYkw8s_8JtubERIbsy_0Qc_q0zGK9nUrtf2IWVNmQ&m=VtNo9cSRcnVhW9PH68IA26gNRrJ96V0O7MHTeONQ-hY&s=Zh9LBq_sTlZxC5xI7FupdttxdRrhrwmoIsY4eZRlvjM&e=
> >
>
> That's it, thank you!
>
> // jim
>
>
>
> I'm involved in some TripleO work called the split control plane:
>
> https://specs.openstack.org/openstack/tripleo-specs/specs/rocky/split-controlplane.html
> <
> https://urldefense.proofpoint.com/v2/url?u=https-3A__specs.openstack.org_openstack_tripleo-2Dspecs_specs_rocky_split-2Dcontrolplane.html&d=DwMGaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=JcbYkw8s_8JtubERIbsy_0Qc_q0zGK9nUrtf2IWVNmQ&m=VtNo9cSRcnVhW9PH68IA26gNRrJ96V0O7MHTeONQ-hY&s=tuDTh6QOmYEza4K8a7S2RoUpc1ttgBTHVC8re5vfcdg&e=
> >
>
> After the PTG I saw that the split control plane was compatible with
> the type of deployment discussed at the edge WG session in Denver and
> described the compatibility at:
>
> https://etherpad.openstack.org/p/tripleo-edge-working-group-split-control-plane
> <
> https://urldefense.proofpoint.com/v2/url?u=https-3A__etherpad.openstack.org_p_tripleo-2Dedge-2Dworking-2Dgroup-2Dsplit-2Dcontrol-2Dplane&d=DwMGaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=JcbYkw8s_8JtubERIbsy_0Qc_q0zGK9nUrtf2IWVNmQ&m=VtNo9cSRcnVhW9PH68IA26gNRrJ96V0O7MHTeONQ-hY&s=5Ak84Rb4c98_jEqNWjvWYCeVAN0XkbZzdXVWax9oo_Q&e=
> >
>
> > See the picture and table here:
> https://wiki.openstack.org/wiki/Edge_Computing_Group/Edge_Reference_Architectures#Overview
> <
> https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.openstack.org_wiki_Edge-5FComputing-5FGroup_Edge-5FReference-5FArchitectures-23Overview&d=DwMGaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=JcbYkw8s_8JtubERIbsy_0Qc_q0zGK9nUrtf2IWVNmQ&m=VtNo9cSRcnVhW9PH68IA26gNRrJ96V0O7MHTeONQ-hY&s=yqEH7weN-I2YvoYDRi6nSWGtNzQsX-HfBieGuOBow1M&e=
> >
> >
> >> Now, I don't have really great suggestions. Something that came up in
> TripleO
> >> discussions [1] is Core/Hub/Edge, which I think reflects the idea
> better.
> >
> >
> > I'm also fine with these names, as they do describe the concepts well. :)
> >
> > // jim
>
> I'm fine with these terms too. In split control plane there's a
> deployment method for deploying a central site and then deploying
> remote sites independently. That deployment method could be used to
> deploy  Core/Hub/Edge sites too. E.g. deploy the Core using Heat stack
> N. Deploy a Hub using stack N+1 and then deploy an Edge using stack
> N+2 etc.
>
>   John
>
> >>
> >> I'd be very interested to hear your ideas.
> >>
> >> Dmitry
> >>
> >> [1] https://etherpad.openstack.org/p/tripleo-edge-mvp<
> https://urldefense.proofpoint.com/v2/url?u=https-3A__etherpad.openstack.org_p_tripleo-2Dedge-2Dmvp&d=DwMGaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=JcbYkw8s_8JtubERIbsy_0Qc_q0zGK9nUrtf2IWVNmQ&m=VtNo9cSRcnVhW9PH68IA26gNRrJ96V0O7MHTeONQ-hY&s=XI1J9s1i2KxUSnOX9Yk3XQ_5kH08UoWZ_uqd6Y3efQU&e=
> >
> >>
> >> _______________________________________________
> >> openstack-sigs mailing list
> >> openstack-sigs at lists.openstack.org<mailto:
> openstack-sigs at lists.openstack.org>
> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs<
> https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_openstack-2Dsigs&d=DwMGaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=JcbYkw8s_8JtubERIbsy_0Qc_q0zGK9nUrtf2IWVNmQ&m=VtNo9cSRcnVhW9PH68IA26gNRrJ96V0O7MHTeONQ-hY&s=TmAFzLOVMjHTW569gUKwSRI4OwLlF5tOqAlcYuPaCHM&e=
> >
> >
> >
> __________________________________________________________________________
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe:
> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe<
> https://urldefense.proofpoint.com/v2/url?u=http-3A__OpenStack-2Ddev-2Drequest-40lists.openstack.org-3Fsubject-3Aunsubscribe&d=DwMGaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=JcbYkw8s_8JtubERIbsy_0Qc_q0zGK9nUrtf2IWVNmQ&m=VtNo9cSRcnVhW9PH68IA26gNRrJ96V0O7MHTeONQ-hY&s=fH-cGOV9QxQ5JB6p2hhzcysjmij8hCyy3ptvz6tystU&e=
> >
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<
> https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_openstack-2Ddev&d=DwMGaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=JcbYkw8s_8JtubERIbsy_0Qc_q0zGK9nUrtf2IWVNmQ&m=VtNo9cSRcnVhW9PH68IA26gNRrJ96V0O7MHTeONQ-hY&s=161pS98mNzJwzSvHGBh3w1L6xADUAa9R08Qf-LQEjUQ&e=
> >
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> <
> https://urldefense.proofpoint.com/v2/url?u=http-3A__OpenStack-2Ddev-2Drequest-40lists.openstack.org-3Fsubject-3Aunsubscribe&d=DwMGaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=JcbYkw8s_8JtubERIbsy_0Qc_q0zGK9nUrtf2IWVNmQ&m=VtNo9cSRcnVhW9PH68IA26gNRrJ96V0O7MHTeONQ-hY&s=fH-cGOV9QxQ5JB6p2hhzcysjmij8hCyy3ptvz6tystU&e=
> >
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<
> https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_openstack-2Ddev&d=DwMGaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=JcbYkw8s_8JtubERIbsy_0Qc_q0zGK9nUrtf2IWVNmQ&m=VtNo9cSRcnVhW9PH68IA26gNRrJ96V0O7MHTeONQ-hY&s=161pS98mNzJwzSvHGBh3w1L6xADUAa9R08Qf-LQEjUQ&e=
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://lists.openstack.org/pipermail/edge-computing/attachments/20181019/4b140cb6/attachment.html
> >
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> Edge-computing mailing list
> Edge-computing at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
>
>
> ------------------------------
>
> End of Edge-computing Digest, Vol 12, Issue 6
> *********************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/edge-computing/attachments/20181022/948d8e29/attachment-0001.html>

From gergely.csatari at nokia.com  Tue Oct 23 09:26:12 2018
From: gergely.csatari at nokia.com (Csatari, Gergely (Nokia - HU/Budapest))
Date: Tue, 23 Oct 2018 09:26:12 +0000
Subject: [Edge-computing] [openstack-dev] [Openstack-sigs] [FEMDC]
 [Edge] [tripleo] On the use of terms "Edge" and "Far Edge"
In-Reply-To: <BY1PR0401MB1350FCABDEF1BF76C8917285A6F90@BY1PR0401MB1350.namprd04.prod.outlook.com>
References: <713a4c9a-d628-ee6d-49e8-c8e9763cdbfe@redhat.com>
 <CAJCXu8ebO4kpNGcFFHh39jAoKkAkSbnaPXz4h37bFJfsTZDoxQ@mail.gmail.com>
 <CAE66OMASyg1xJxoVT9wevmSpCUENVyHJ21mi5UasRKn6OPSSsw@mail.gmail.com>
 <CAJCXu8fBFUHwbiMM3nf81GTOwVoXP5uoFaNx612xKju9aZ4m3A@mail.gmail.com>
 <HE1PR07MB172281F95F7CC131EE93AE76E1F90@HE1PR07MB1722.eurprd07.prod.outlook.com>
 <BY1PR0401MB1350FCABDEF1BF76C8917285A6F90@BY1PR0401MB1350.namprd04.prod.outlook.com>
Message-ID: <HE1PR07MB172255B449C0B1F3CB589BD5E1F50@HE1PR07MB1722.eurprd07.prod.outlook.com>

Hi,

Yes, https://github.com/State-of-the-Edge/glossary is a good initiative. Maybe we should all just start using the terms defined there and contribute if we have problems with the definitions.

Br,
Gerg0

From: Teresa Peluso <tpeluso at equinix.com>
Sent: Friday, October 19, 2018 4:39 PM
To: Csatari, Gergely (Nokia - HU/Budapest) <gergely.csatari at nokia.com>; OpenStack Development Mailing List (not for usage questions) <openstack-dev at lists.openstack.org>; fulton at redhat.com; edge-computing at lists.openstack.org
Cc: openstack-sigs at lists.openstack.org
Subject: RE: [openstack-dev] [Openstack-sigs] [FEMDC] [Edge] [tripleo] On the use of terms "Edge" and "Far Edge"

Fyi – could this help?  https://www.linuxfoundation.org/blog/2018/06/edge-computing-just-got-its-rosetta-stone/

https://imasons.org/ starting to host workshops about this as well https://imasons.org/events/2018-im-edge-congress/

From: Csatari, Gergely (Nokia - HU/Budapest) <gergely.csatari at nokia.com<mailto:gergely.csatari at nokia.com>>
Sent: Friday, October 19, 2018 1:05 AM
To: OpenStack Development Mailing List (not for usage questions) <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>; fulton at redhat.com<mailto:fulton at redhat.com>; edge-computing at lists.openstack.org<mailto:edge-computing at lists.openstack.org>
Cc: openstack-sigs at lists.openstack.org<mailto:openstack-sigs at lists.openstack.org>
Subject: [EXTERNAL] Re: [Edge-computing] [openstack-dev] [Openstack-sigs] [FEMDC] [Edge] [tripleo] On the use of terms "Edge" and "Far Edge"

Hi,

I’m adding the ECG mailing list to the discussion.

I think the root of the problem is that there is no single definition of „the edge” (except for [1<https://urldefense.proofpoint.com/v2/url?u=https-3A__en.wikipedia.org_wiki_The-5FEdge&d=DwMGaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=JcbYkw8s_8JtubERIbsy_0Qc_q0zGK9nUrtf2IWVNmQ&m=VtNo9cSRcnVhW9PH68IA26gNRrJ96V0O7MHTeONQ-hY&s=J6lr_T9m7mkisVR7l1QzmBki20r5He3fuZXvbYg-EPs&e=>]), but it changes from group to group or use case to use case. What I recognise as the commonalities in these edge definitions, are 1) a distributed cloud infrastructure (kind of a cloud of clouds) 2) need for automation or everything 3) resource constraints for the control plane.

The different edge variants are putting different emphasis on these common needs based ont he use case discussed.

To have a more clear understanding of these definitions we could try the following:

  1.  Always add the definition of these to the given context
  2.  Check what other groups are using and adopt to that
  3.  Define our own language and expect everyone else to adopt

Br,
Gerg0



[1]: https://en.wikipedia.org/wiki/The_Edge<https://urldefense.proofpoint.com/v2/url?u=https-3A__en.wikipedia.org_wiki_The-5FEdge&d=DwQGaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=JcbYkw8s_8JtubERIbsy_0Qc_q0zGK9nUrtf2IWVNmQ&m=VtNo9cSRcnVhW9PH68IA26gNRrJ96V0O7MHTeONQ-hY&s=J6lr_T9m7mkisVR7l1QzmBki20r5He3fuZXvbYg-EPs&e=>

From: Jim Rollenhagen <jim at jimrollenhagen.com<mailto:jim at jimrollenhagen.com>>
Sent: Thursday, October 18, 2018 11:43 PM
To: fulton at redhat.com<mailto:fulton at redhat.com>; OpenStack Development Mailing List (not for usage questions) <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Cc: openstack-sigs at lists.openstack.org<mailto:openstack-sigs at lists.openstack.org>
Subject: Re: [openstack-dev] [Openstack-sigs] [FEMDC] [Edge] [tripleo] On the use of terms "Edge" and "Far Edge"

On Thu, Oct 18, 2018 at 4:45 PM John Fulton <johfulto at redhat.com<mailto:johfulto at redhat.com>> wrote:
On Thu, Oct 18, 2018 at 11:56 AM Jim Rollenhagen <jim at jimrollenhagen.com<mailto:jim at jimrollenhagen.com>> wrote:
>
> On Thu, Oct 18, 2018 at 10:23 AM Dmitry Tantsur <dtantsur at redhat.com<mailto:dtantsur at redhat.com>> wrote:
>>
>> Hi all,
>>
>> Sorry for chiming in really late in this topic, but I think $subj is worth
>> discussing until we settle harder on the potentially confusing terminology.
>>
>> I think the difference between "Edge" and "Far Edge" is too vague to use these
>> terms in practice. Think about the "edge" metaphor itself: something rarely has
>> several layers of edges. A knife has an edge, there are no far edges. I imagine
>> zooming in and seeing more edges at the edge, and then it's quite cool indeed,
>> but is it really a useful metaphor for those who never used a strong microscope? :)
>>
>> I think in the trivial sense "Far Edge" is a tautology, and should be avoided.
>> As a weak proof of my words, I already see a lot of smart people confusing these
>> two and actually use Central/Edge where they mean Edge/Far Edge. I suggest we
>> adopt a different terminology, even if it less consistent with typical marketing
>> term around the "Edge" movement.
>
>
> FWIW, we created rough definitions of "edge" and "far edge" during the edge WG session in Denver.
> It's mostly based on latency to the end user, though we also talked about quantities of compute resources, if someone can find the pictures.

Perhaps these are the pictures Jim was referring to?
 https://www.dropbox.com/s/255x1cao14taer3/MVP-Architecture_edge-computing_PTG.pptx?dl=0#<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.dropbox.com_s_255x1cao14taer3_MVP-2DArchitecture-5Fedge-2Dcomputing-5FPTG.pptx-3Fdl-3D0&d=DwMGaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=JcbYkw8s_8JtubERIbsy_0Qc_q0zGK9nUrtf2IWVNmQ&m=VtNo9cSRcnVhW9PH68IA26gNRrJ96V0O7MHTeONQ-hY&s=Zh9LBq_sTlZxC5xI7FupdttxdRrhrwmoIsY4eZRlvjM&e=>

That's it, thank you!

// jim



I'm involved in some TripleO work called the split control plane:
  https://specs.openstack.org/openstack/tripleo-specs/specs/rocky/split-controlplane.html<https://urldefense.proofpoint.com/v2/url?u=https-3A__specs.openstack.org_openstack_tripleo-2Dspecs_specs_rocky_split-2Dcontrolplane.html&d=DwMGaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=JcbYkw8s_8JtubERIbsy_0Qc_q0zGK9nUrtf2IWVNmQ&m=VtNo9cSRcnVhW9PH68IA26gNRrJ96V0O7MHTeONQ-hY&s=tuDTh6QOmYEza4K8a7S2RoUpc1ttgBTHVC8re5vfcdg&e=>

After the PTG I saw that the split control plane was compatible with
the type of deployment discussed at the edge WG session in Denver and
described the compatibility at:
  https://etherpad.openstack.org/p/tripleo-edge-working-group-split-control-plane<https://urldefense.proofpoint.com/v2/url?u=https-3A__etherpad.openstack.org_p_tripleo-2Dedge-2Dworking-2Dgroup-2Dsplit-2Dcontrol-2Dplane&d=DwMGaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=JcbYkw8s_8JtubERIbsy_0Qc_q0zGK9nUrtf2IWVNmQ&m=VtNo9cSRcnVhW9PH68IA26gNRrJ96V0O7MHTeONQ-hY&s=5Ak84Rb4c98_jEqNWjvWYCeVAN0XkbZzdXVWax9oo_Q&e=>

> See the picture and table here: https://wiki.openstack.org/wiki/Edge_Computing_Group/Edge_Reference_Architectures#Overview<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.openstack.org_wiki_Edge-5FComputing-5FGroup_Edge-5FReference-5FArchitectures-23Overview&d=DwMGaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=JcbYkw8s_8JtubERIbsy_0Qc_q0zGK9nUrtf2IWVNmQ&m=VtNo9cSRcnVhW9PH68IA26gNRrJ96V0O7MHTeONQ-hY&s=yqEH7weN-I2YvoYDRi6nSWGtNzQsX-HfBieGuOBow1M&e=>
>
>> Now, I don't have really great suggestions. Something that came up in TripleO
>> discussions [1] is Core/Hub/Edge, which I think reflects the idea better.
>
>
> I'm also fine with these names, as they do describe the concepts well. :)
>
> // jim

I'm fine with these terms too. In split control plane there's a
deployment method for deploying a central site and then deploying
remote sites independently. That deployment method could be used to
deploy  Core/Hub/Edge sites too. E.g. deploy the Core using Heat stack
N. Deploy a Hub using stack N+1 and then deploy an Edge using stack
N+2 etc.

  John

>>
>> I'd be very interested to hear your ideas.
>>
>> Dmitry
>>
>> [1] https://etherpad.openstack.org/p/tripleo-edge-mvp<https://urldefense.proofpoint.com/v2/url?u=https-3A__etherpad.openstack.org_p_tripleo-2Dedge-2Dmvp&d=DwMGaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=JcbYkw8s_8JtubERIbsy_0Qc_q0zGK9nUrtf2IWVNmQ&m=VtNo9cSRcnVhW9PH68IA26gNRrJ96V0O7MHTeONQ-hY&s=XI1J9s1i2KxUSnOX9Yk3XQ_5kH08UoWZ_uqd6Y3efQU&e=>
>>
>> _______________________________________________
>> openstack-sigs mailing list
>> openstack-sigs at lists.openstack.org<mailto:openstack-sigs at lists.openstack.org>
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs<https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_openstack-2Dsigs&d=DwMGaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=JcbYkw8s_8JtubERIbsy_0Qc_q0zGK9nUrtf2IWVNmQ&m=VtNo9cSRcnVhW9PH68IA26gNRrJ96V0O7MHTeONQ-hY&s=TmAFzLOVMjHTW569gUKwSRI4OwLlF5tOqAlcYuPaCHM&e=>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe<https://urldefense.proofpoint.com/v2/url?u=http-3A__OpenStack-2Ddev-2Drequest-40lists.openstack.org-3Fsubject-3Aunsubscribe&d=DwMGaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=JcbYkw8s_8JtubERIbsy_0Qc_q0zGK9nUrtf2IWVNmQ&m=VtNo9cSRcnVhW9PH68IA26gNRrJ96V0O7MHTeONQ-hY&s=fH-cGOV9QxQ5JB6p2hhzcysjmij8hCyy3ptvz6tystU&e=>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_openstack-2Ddev&d=DwMGaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=JcbYkw8s_8JtubERIbsy_0Qc_q0zGK9nUrtf2IWVNmQ&m=VtNo9cSRcnVhW9PH68IA26gNRrJ96V0O7MHTeONQ-hY&s=161pS98mNzJwzSvHGBh3w1L6xADUAa9R08Qf-LQEjUQ&e=>

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe<https://urldefense.proofpoint.com/v2/url?u=http-3A__OpenStack-2Ddev-2Drequest-40lists.openstack.org-3Fsubject-3Aunsubscribe&d=DwMGaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=JcbYkw8s_8JtubERIbsy_0Qc_q0zGK9nUrtf2IWVNmQ&m=VtNo9cSRcnVhW9PH68IA26gNRrJ96V0O7MHTeONQ-hY&s=fH-cGOV9QxQ5JB6p2hhzcysjmij8hCyy3ptvz6tystU&e=>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_openstack-2Ddev&d=DwMGaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=JcbYkw8s_8JtubERIbsy_0Qc_q0zGK9nUrtf2IWVNmQ&m=VtNo9cSRcnVhW9PH68IA26gNRrJ96V0O7MHTeONQ-hY&s=161pS98mNzJwzSvHGBh3w1L6xADUAa9R08Qf-LQEjUQ&e=>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/edge-computing/attachments/20181023/1cf2d53b/attachment-0001.html>

From ildiko.vancsa at gmail.com  Tue Oct 23 11:39:06 2018
From: ildiko.vancsa at gmail.com (Ildiko Vancsa)
Date: Tue, 23 Oct 2018 13:39:06 +0200
Subject: [Edge-computing] [openstack-dev] [Openstack-sigs] [FEMDC]
 [Edge] [tripleo] On the use of terms "Edge" and "Far Edge" (Teresa Peluso)
In-Reply-To: <CANJ_P_LGe981y+GA3+dSFd_K7J1nKQdd3ziHVajFB+8kH6_+FA@mail.gmail.com>
References: <CANJ_P_LGe981y+GA3+dSFd_K7J1nKQdd3ziHVajFB+8kH6_+FA@mail.gmail.com>
Message-ID: <72DACF95-5BFD-4F60-AA99-E2C324DDB57B@gmail.com>

Hi Matt,

That sounds great, thank you for inviting the group to participate in the Open Glossary of Edge Computing initiative.

I agree that collaboration is crucial and I support to explore the options how we can work together including participation in the TSC group.

I will bring this up on our next weekly call[1], which is happening today at 1400 UTC / 7am PDT, to see who would be interested in participating besides me.

Also I believe a few of our community members will attend the Edge Congress in Austin tomorrow, I hope you will have a chance to connect and talk more about collaboration. :)

Do you have any suggestion on where to start getting involved with the Open Glossary of Edge Computing initiative?

Thanks and Best Regards,
Ildikó

[1] https://wiki.openstack.org/wiki/Edge_Computing_Group#Meetings


> On 2018. Oct 23., at 6:40, Matt Trifiro <mtrifiro at vapor.io> wrote:
> 
> Teresa Peluso <tpeluso at equinix.com> wrote:
> 
> Fyi – could this help?  https://www.linuxfoundation.org/blog/2018/06/edge-computing-just-got-its-rosetta-stone/
> 
> https://imasons.org/ starting to host workshops about this as well https://imasons.org/events/2018-im-edge-congress/
> 
> I am the Chair of the Open Glossary of Edge Computing, the Linux Foundation project mentioned in the blog post. I would be happy to invite an OpenStack nominee onto our TSC. We seek to harmonize and define the various flavors of edge, and OpenStack is doing interesting work and I'd like to see the communities collaborate. I am also part of the iMasosn effort.
> 
> m
> 
> On Fri, Oct 19, 2018 at 8:39 AM <edge-computing-request at lists.openstack.org> wrote:
> Send Edge-computing mailing list submissions to
>         edge-computing at lists.openstack.org
> 
> To subscribe or unsubscribe via the World Wide Web, visit
>         http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
> or, via email, send a message with subject or body 'help' to
>         edge-computing-request at lists.openstack.org
> 
> You can reach the person managing the list at
>         edge-computing-owner at lists.openstack.org
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Edge-computing digest..."
> 
> 
> Today's Topics:
> 
>    1. Re: [openstack-dev] [Openstack-sigs] [FEMDC] [Edge] [tripleo]
>       On the use of terms "Edge" and "Far Edge" (Teresa Peluso)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Fri, 19 Oct 2018 15:38:33 +0000
> From: Teresa Peluso <tpeluso at equinix.com>
> To: "Csatari, Gergely (Nokia - HU/Budapest)"
>         <gergely.csatari at nokia.com>, "OpenStack Development Mailing List (not
>         for usage questions)" <openstack-dev at lists.openstack.org>,
>         "fulton at redhat.com" <fulton at redhat.com>,
>         "edge-computing at lists.openstack.org"
>         <edge-computing at lists.openstack.org>
> Cc: "openstack-sigs at lists.openstack.org"
>         <openstack-sigs at lists.openstack.org>
> Subject: Re: [Edge-computing] [openstack-dev] [Openstack-sigs] [FEMDC]
>         [Edge] [tripleo] On the use of terms "Edge" and "Far Edge"
> Message-ID:
>         <BY1PR0401MB1350FCABDEF1BF76C8917285A6F90 at BY1PR0401MB1350.namprd04.prod.outlook.com>
> 
> Content-Type: text/plain; charset="utf-8"
> 
> Fyi – could this help?  https://www.linuxfoundation.org/blog/2018/06/edge-computing-just-got-its-rosetta-stone/
> 
> https://imasons.org/ starting to host workshops about this as well https://imasons.org/events/2018-im-edge-congress/
> 
> From: Csatari, Gergely (Nokia - HU/Budapest) <gergely.csatari at nokia.com>
> Sent: Friday, October 19, 2018 1:05 AM
> To: OpenStack Development Mailing List (not for usage questions) <openstack-dev at lists.openstack.org>; fulton at redhat.com; edge-computing at lists.openstack.org
> Cc: openstack-sigs at lists.openstack.org
> Subject: [EXTERNAL] Re: [Edge-computing] [openstack-dev] [Openstack-sigs] [FEMDC] [Edge] [tripleo] On the use of terms "Edge" and "Far Edge"
> 
> Hi,
> 
> I’m adding the ECG mailing list to the discussion.
> 
> I think the root of the problem is that there is no single definition of „the edge” (except for [1<https://urldefense.proofpoint.com/v2/url?u=https-3A__en.wikipedia.org_wiki_The-5FEdge&d=DwMGaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=JcbYkw8s_8JtubERIbsy_0Qc_q0zGK9nUrtf2IWVNmQ&m=VtNo9cSRcnVhW9PH68IA26gNRrJ96V0O7MHTeONQ-hY&s=J6lr_T9m7mkisVR7l1QzmBki20r5He3fuZXvbYg-EPs&e=>]), but it changes from group to group or use case to use case. What I recognise as the commonalities in these edge definitions, are 1) a distributed cloud infrastructure (kind of a cloud of clouds) 2) need for automation or everything 3) resource constraints for the control plane.
> 
> The different edge variants are putting different emphasis on these common needs based ont he use case discussed.
> 
> To have a more clear understanding of these definitions we could try the following:
> 
>   1.  Always add the definition of these to the given context
>   2.  Check what other groups are using and adopt to that
>   3.  Define our own language and expect everyone else to adopt
> 
> Br,
> Gerg0
> 
> 
> 
> [1]: https://en.wikipedia.org/wiki/The_Edge<https://urldefense.proofpoint.com/v2/url?u=https-3A__en.wikipedia.org_wiki_The-5FEdge&d=DwQGaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=JcbYkw8s_8JtubERIbsy_0Qc_q0zGK9nUrtf2IWVNmQ&m=VtNo9cSRcnVhW9PH68IA26gNRrJ96V0O7MHTeONQ-hY&s=J6lr_T9m7mkisVR7l1QzmBki20r5He3fuZXvbYg-EPs&e=>
> 
> From: Jim Rollenhagen <jim at jimrollenhagen.com<mailto:jim at jimrollenhagen.com>>
> Sent: Thursday, October 18, 2018 11:43 PM
> To: fulton at redhat.com<mailto:fulton at redhat.com>; OpenStack Development Mailing List (not for usage questions) <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
> Cc: openstack-sigs at lists.openstack.org<mailto:openstack-sigs at lists.openstack.org>
> Subject: Re: [openstack-dev] [Openstack-sigs] [FEMDC] [Edge] [tripleo] On the use of terms "Edge" and "Far Edge"
> 
> On Thu, Oct 18, 2018 at 4:45 PM John Fulton <johfulto at redhat.com<mailto:johfulto at redhat.com>> wrote:
> On Thu, Oct 18, 2018 at 11:56 AM Jim Rollenhagen <jim at jimrollenhagen.com<mailto:jim at jimrollenhagen.com>> wrote:
> >
> > On Thu, Oct 18, 2018 at 10:23 AM Dmitry Tantsur <dtantsur at redhat.com<mailto:dtantsur at redhat.com>> wrote:
> >>
> >> Hi all,
> >>
> >> Sorry for chiming in really late in this topic, but I think $subj is worth
> >> discussing until we settle harder on the potentially confusing terminology.
> >>
> >> I think the difference between "Edge" and "Far Edge" is too vague to use these
> >> terms in practice. Think about the "edge" metaphor itself: something rarely has
> >> several layers of edges. A knife has an edge, there are no far edges. I imagine
> >> zooming in and seeing more edges at the edge, and then it's quite cool indeed,
> >> but is it really a useful metaphor for those who never used a strong microscope? :)
> >>
> >> I think in the trivial sense "Far Edge" is a tautology, and should be avoided.
> >> As a weak proof of my words, I already see a lot of smart people confusing these
> >> two and actually use Central/Edge where they mean Edge/Far Edge. I suggest we
> >> adopt a different terminology, even if it less consistent with typical marketing
> >> term around the "Edge" movement.
> >
> >
> > FWIW, we created rough definitions of "edge" and "far edge" during the edge WG session in Denver.
> > It's mostly based on latency to the end user, though we also talked about quantities of compute resources, if someone can find the pictures.
> 
> Perhaps these are the pictures Jim was referring to?
>  https://www.dropbox.com/s/255x1cao14taer3/MVP-Architecture_edge-computing_PTG.pptx?dl=0#<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.dropbox.com_s_255x1cao14taer3_MVP-2DArchitecture-5Fedge-2Dcomputing-5FPTG.pptx-3Fdl-3D0&d=DwMGaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=JcbYkw8s_8JtubERIbsy_0Qc_q0zGK9nUrtf2IWVNmQ&m=VtNo9cSRcnVhW9PH68IA26gNRrJ96V0O7MHTeONQ-hY&s=Zh9LBq_sTlZxC5xI7FupdttxdRrhrwmoIsY4eZRlvjM&e=>
> 
> That's it, thank you!
> 
> // jim
> 
> 
> 
> I'm involved in some TripleO work called the split control plane:
>   https://specs.openstack.org/openstack/tripleo-specs/specs/rocky/split-controlplane.html<https://urldefense.proofpoint.com/v2/url?u=https-3A__specs.openstack.org_openstack_tripleo-2Dspecs_specs_rocky_split-2Dcontrolplane.html&d=DwMGaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=JcbYkw8s_8JtubERIbsy_0Qc_q0zGK9nUrtf2IWVNmQ&m=VtNo9cSRcnVhW9PH68IA26gNRrJ96V0O7MHTeONQ-hY&s=tuDTh6QOmYEza4K8a7S2RoUpc1ttgBTHVC8re5vfcdg&e=>
> 
> After the PTG I saw that the split control plane was compatible with
> the type of deployment discussed at the edge WG session in Denver and
> described the compatibility at:
>   https://etherpad.openstack.org/p/tripleo-edge-working-group-split-control-plane<https://urldefense.proofpoint.com/v2/url?u=https-3A__etherpad.openstack.org_p_tripleo-2Dedge-2Dworking-2Dgroup-2Dsplit-2Dcontrol-2Dplane&d=DwMGaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=JcbYkw8s_8JtubERIbsy_0Qc_q0zGK9nUrtf2IWVNmQ&m=VtNo9cSRcnVhW9PH68IA26gNRrJ96V0O7MHTeONQ-hY&s=5Ak84Rb4c98_jEqNWjvWYCeVAN0XkbZzdXVWax9oo_Q&e=>
> 
> > See the picture and table here: https://wiki.openstack.org/wiki/Edge_Computing_Group/Edge_Reference_Architectures#Overview<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.openstack.org_wiki_Edge-5FComputing-5FGroup_Edge-5FReference-5FArchitectures-23Overview&d=DwMGaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=JcbYkw8s_8JtubERIbsy_0Qc_q0zGK9nUrtf2IWVNmQ&m=VtNo9cSRcnVhW9PH68IA26gNRrJ96V0O7MHTeONQ-hY&s=yqEH7weN-I2YvoYDRi6nSWGtNzQsX-HfBieGuOBow1M&e=>
> >
> >> Now, I don't have really great suggestions. Something that came up in TripleO
> >> discussions [1] is Core/Hub/Edge, which I think reflects the idea better.
> >
> >
> > I'm also fine with these names, as they do describe the concepts well. :)
> >
> > // jim
> 
> I'm fine with these terms too. In split control plane there's a
> deployment method for deploying a central site and then deploying
> remote sites independently. That deployment method could be used to
> deploy  Core/Hub/Edge sites too. E.g. deploy the Core using Heat stack
> N. Deploy a Hub using stack N+1 and then deploy an Edge using stack
> N+2 etc.
> 
>   John
> 
> >>
> >> I'd be very interested to hear your ideas.
> >>
> >> Dmitry
> >>
> >> [1] https://etherpad.openstack.org/p/tripleo-edge-mvp<https://urldefense.proofpoint.com/v2/url?u=https-3A__etherpad.openstack.org_p_tripleo-2Dedge-2Dmvp&d=DwMGaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=JcbYkw8s_8JtubERIbsy_0Qc_q0zGK9nUrtf2IWVNmQ&m=VtNo9cSRcnVhW9PH68IA26gNRrJ96V0O7MHTeONQ-hY&s=XI1J9s1i2KxUSnOX9Yk3XQ_5kH08UoWZ_uqd6Y3efQU&e=>
> >>
> >> _______________________________________________
> >> openstack-sigs mailing list
> >> openstack-sigs at lists.openstack.org<mailto:openstack-sigs at lists.openstack.org>
> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs<https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_openstack-2Dsigs&d=DwMGaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=JcbYkw8s_8JtubERIbsy_0Qc_q0zGK9nUrtf2IWVNmQ&m=VtNo9cSRcnVhW9PH68IA26gNRrJ96V0O7MHTeONQ-hY&s=TmAFzLOVMjHTW569gUKwSRI4OwLlF5tOqAlcYuPaCHM&e=>
> >
> > __________________________________________________________________________
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe<https://urldefense.proofpoint.com/v2/url?u=http-3A__OpenStack-2Ddev-2Drequest-40lists.openstack.org-3Fsubject-3Aunsubscribe&d=DwMGaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=JcbYkw8s_8JtubERIbsy_0Qc_q0zGK9nUrtf2IWVNmQ&m=VtNo9cSRcnVhW9PH68IA26gNRrJ96V0O7MHTeONQ-hY&s=fH-cGOV9QxQ5JB6p2hhzcysjmij8hCyy3ptvz6tystU&e=>
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_openstack-2Ddev&d=DwMGaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=JcbYkw8s_8JtubERIbsy_0Qc_q0zGK9nUrtf2IWVNmQ&m=VtNo9cSRcnVhW9PH68IA26gNRrJ96V0O7MHTeONQ-hY&s=161pS98mNzJwzSvHGBh3w1L6xADUAa9R08Qf-LQEjUQ&e=>
> 
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe<https://urldefense.proofpoint.com/v2/url?u=http-3A__OpenStack-2Ddev-2Drequest-40lists.openstack.org-3Fsubject-3Aunsubscribe&d=DwMGaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=JcbYkw8s_8JtubERIbsy_0Qc_q0zGK9nUrtf2IWVNmQ&m=VtNo9cSRcnVhW9PH68IA26gNRrJ96V0O7MHTeONQ-hY&s=fH-cGOV9QxQ5JB6p2hhzcysjmij8hCyy3ptvz6tystU&e=>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_openstack-2Ddev&d=DwMGaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=JcbYkw8s_8JtubERIbsy_0Qc_q0zGK9nUrtf2IWVNmQ&m=VtNo9cSRcnVhW9PH68IA26gNRrJ96V0O7MHTeONQ-hY&s=161pS98mNzJwzSvHGBh3w1L6xADUAa9R08Qf-LQEjUQ&e=>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.openstack.org/pipermail/edge-computing/attachments/20181019/4b140cb6/attachment.html>
> 
> ------------------------------
> 
> Subject: Digest Footer
> 
> _______________________________________________
> Edge-computing mailing list
> Edge-computing at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
> 
> 
> ------------------------------
> 
> End of Edge-computing Digest, Vol 12, Issue 6
> *********************************************
> _______________________________________________
> Edge-computing mailing list
> Edge-computing at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing



From ildiko at openstack.org  Tue Oct 23 16:54:19 2018
From: ildiko at openstack.org (Ildiko Vancsa)
Date: Tue, 23 Oct 2018 18:54:19 +0200
Subject: [Edge-computing] Reminder, October 24 StarlingX On-Boarding Webinar
Message-ID: <E4A7ED3D-B898-4AF6-A946-A092FC5656B6@openstack.org>

Hi,

I would like to remind you to the upcoming OpenStack Foundation Community Meeting[1] where we will focus on the StarlingX project and edge computing as the first release of the project is quickly approaching.

Please join the call to get an overview about the project, learn more about the technology and ways to get involved with the community on *October 24 at 8:00am PDT* on the following link: https://zoom.us/j/112003649

We also invite you to follow @StarlingX on Twitter for announcements and news moving forward. 

Thanks,
Ildikó

-------------- next part --------------
A non-text attachment was scrubbed...
Name: Mail Attachment.ics
Type: text/calendar
Size: 3160 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/edge-computing/attachments/20181023/164714ea/attachment.ics>
-------------- next part --------------




From jgershater at gmail.com  Tue Oct 23 17:06:14 2018
From: jgershater at gmail.com (Jonathan Gershater)
Date: Tue, 23 Oct 2018 10:06:14 -0700
Subject: [Edge-computing] Reminder,
 October 24 StarlingX On-Boarding Webinar
In-Reply-To: <E4A7ED3D-B898-4AF6-A946-A092FC5656B6@openstack.org>
References: <E4A7ED3D-B898-4AF6-A946-A092FC5656B6@openstack.org>
Message-ID: <D284C1D3-1C67-46D7-9C17-388C03AA49BB@gmail.com>

five followers and zero tweets?
https://twitter.com/starlingx <https://twitter.com/starlingx>


> On Oct 23, 2018, at 9:54 AM, Ildiko Vancsa <ildiko at openstack.org> wrote:
> 
> We also invite you to follow @StarlingX on Twitter for announcements and news moving forward. 

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

From ildiko at openstack.org  Tue Oct 23 17:17:58 2018
From: ildiko at openstack.org (Ildiko Vancsa)
Date: Tue, 23 Oct 2018 19:17:58 +0200
Subject: [Edge-computing] Reminder,
 October 24 StarlingX On-Boarding Webinar
In-Reply-To: <D284C1D3-1C67-46D7-9C17-388C03AA49BB@gmail.com>
References: <E4A7ED3D-B898-4AF6-A946-A092FC5656B6@openstack.org>
 <D284C1D3-1C67-46D7-9C17-388C03AA49BB@gmail.com>
Message-ID: <238097E7-5086-4251-9BDC-A3F22DE8BCD0@openstack.org>

Hi Jonathan,

The community has been hard at work on the first release. Now that we are approaching the release date we can focus some efforts on marketing and outreach, including Twitter.

Thanks for following, I hope many others will follow your example. :)

Stay tuned for news about the first release and more soon!

Thanks,
Ildikó


> On 2018. Oct 23., at 19:06, Jonathan Gershater <jgershater at gmail.com> wrote:
> 
> five followers and zero tweets?
> https://twitter.com/starlingx
> 
> 
>> On Oct 23, 2018, at 9:54 AM, Ildiko Vancsa <ildiko at openstack.org> wrote:
>> 
>> We also invite you to follow @StarlingX on Twitter for announcements and news moving forward. 
> 



From beth.cohen at verizon.com  Tue Oct 23 21:31:05 2018
From: beth.cohen at verizon.com (beth.cohen at verizon.com)
Date: Tue, 23 Oct 2018 21:31:05 +0000
Subject: [Edge-computing] Invitation: Edge Computing - Use Case Meeting @
 Weekly from 8 AM to 9AM on Monday (EST)
 (edge-computing@lists.openstack.org)
Message-ID: <47f37c63532f4ac296fd48a9ac83d079@scwexch25apd.uswin.ad.vzwcorp.com>

Folks -
Join us as we work through the details of the edge use cases.  This is the APAC friendly time.  It will alternate with the EMEA friendly time.

Monday 8AM EST - EMEA and US
Monday 8PM EST - APAC and US
*       https://wiki.openstack.org/wiki/Edge_Computing_Group/Use_Cases
*       https://etherpad.openstack.org/p/edge-use-case
 Weekly calls on Mondays at 1pm PDT / 2000 UTC

Zoom link: https://zoom.us/j/879678938
Dialing in from phone:
   Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923
   Meeting ID: 879 678 938
   International numbers available: https://zoom.us/u/ed95sU7aQ


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/edge-computing/attachments/20181023/1f7aca2c/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/calendar
Size: 5272 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/edge-computing/attachments/20181023/1f7aca2c/attachment-0001.ics>

From beth.cohen at verizon.com  Tue Oct 23 21:34:44 2018
From: beth.cohen at verizon.com (beth.cohen at verizon.com)
Date: Tue, 23 Oct 2018 21:34:44 +0000
Subject: [Edge-computing] Invitation: Edge Computing - Use Case Meeting @
 Weekly from 8 PM to PAM on Monday (EST)
 (edge-computing@lists.openstack.org)
Message-ID: <100fd7beebf44355bd789be6d388baf4@scwexch25apd.uswin.ad.vzwcorp.com>

Folks -
Join us as we work through the details of the edge use cases.  This is the EMEA friendly time.  It will alternate with the APAC friendly time.

Monday 8AM EST - EMEA and US
Monday 8PM EST - APAC and US
*       https://wiki.openstack.org/wiki/Edge_Computing_Group/Use_Cases
*       https://etherpad.openstack.org/p/edge-use-case
 Weekly calls on Mondays at 1pm PDT / 2000 UTC

Zoom link: https://zoom.us/j/879678938
Dialing in from phone:
   Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923
   Meeting ID: 879 678 938
   International numbers available: https://zoom.us/u/ed95sU7aQ


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/edge-computing/attachments/20181023/eee88534/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/calendar
Size: 5178 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/edge-computing/attachments/20181023/eee88534/attachment-0001.ics>

From mtrifiro at vapor.io  Wed Oct 24 12:53:44 2018
From: mtrifiro at vapor.io (Matt Trifiro)
Date: Wed, 24 Oct 2018 05:53:44 -0700
Subject: [Edge-computing] [openstack-dev] [Openstack-sigs] [FEMDC]
 [Edge] [tripleo] On the use of terms "Edge" and "Far Edge" (Teresa Peluso)
In-Reply-To: <72DACF95-5BFD-4F60-AA99-E2C324DDB57B@gmail.com>
References: <CANJ_P_LGe981y+GA3+dSFd_K7J1nKQdd3ziHVajFB+8kH6_+FA@mail.gmail.com>
 <72DACF95-5BFD-4F60-AA99-E2C324DDB57B@gmail.com>
Message-ID: <CANJ_P_KBL_zQyj_ztvPvMPgkTYRPvncMefPjEomx0W4J6aFdJg@mail.gmail.com>

Ildikó,

Thank you for your response and collaborating spirit.

I will not be at the Edge Congress but I encourage you to send a delegate
to the iMasons meeting. They are doing two working sessions where they are
crowdsourcing a detailed infrastructure taxonomy at the edge, and I believe
this could inform and inspire the work of this group.

Moreover, I am currently putting together what I'm calling The Taxonomy
Project, and i think this would be a perfect place for OpenStack to join.
My idea is to form a working group under the auspices of the Open Glossary
to coordinate with key stakeholder communities like iMasons, CNCF and
OpenStack Edge to nail down and clarify detailed taxonomies on device edge,
the infrastructure edge and the edge software stack. I would welcome your
help in getting that initiative off the ground.

Let me know how the group responds on the call. I'm excited to work with
you and your colleagues.

matt

On Tue, Oct 23, 2018 at 4:39 AM Ildiko Vancsa <ildiko.vancsa at gmail.com>
wrote:

> Hi Matt,
>
> That sounds great, thank you for inviting the group to participate in the
> Open Glossary of Edge Computing initiative.
>
> I agree that collaboration is crucial and I support to explore the options
> how we can work together including participation in the TSC group.
>
> I will bring this up on our next weekly call[1], which is happening today
> at 1400 UTC / 7am PDT, to see who would be interested in participating
> besides me.
>
> Also I believe a few of our community members will attend the Edge
> Congress in Austin tomorrow, I hope you will have a chance to connect and
> talk more about collaboration. :)
>
> Do you have any suggestion on where to start getting involved with the
> Open Glossary of Edge Computing initiative?
>
> Thanks and Best Regards,
> Ildikó
>
> [1] https://wiki.openstack.org/wiki/Edge_Computing_Group#Meetings
>
>
> > On 2018. Oct 23., at 6:40, Matt Trifiro <mtrifiro at vapor.io> wrote:
> >
> > Teresa Peluso <tpeluso at equinix.com> wrote:
> >
> > Fyi – could this help?
> https://www.linuxfoundation.org/blog/2018/06/edge-computing-just-got-its-rosetta-stone/
> >
> > https://imasons.org/ starting to host workshops about this as well
> https://imasons.org/events/2018-im-edge-congress/
> >
> > I am the Chair of the Open Glossary of Edge Computing, the Linux
> Foundation project mentioned in the blog post. I would be happy to invite
> an OpenStack nominee onto our TSC. We seek to harmonize and define the
> various flavors of edge, and OpenStack is doing interesting work and I'd
> like to see the communities collaborate. I am also part of the iMasosn
> effort.
> >
> > m
> >
> > On Fri, Oct 19, 2018 at 8:39 AM <
> edge-computing-request at lists.openstack.org> wrote:
> > Send Edge-computing mailing list submissions to
> >         edge-computing at lists.openstack.org
> >
> > To subscribe or unsubscribe via the World Wide Web, visit
> >
> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
> > or, via email, send a message with subject or body 'help' to
> >         edge-computing-request at lists.openstack.org
> >
> > You can reach the person managing the list at
> >         edge-computing-owner at lists.openstack.org
> >
> > When replying, please edit your Subject line so it is more specific
> > than "Re: Contents of Edge-computing digest..."
> >
> >
> > Today's Topics:
> >
> >    1. Re: [openstack-dev] [Openstack-sigs] [FEMDC] [Edge] [tripleo]
> >       On the use of terms "Edge" and "Far Edge" (Teresa Peluso)
> >
> >
> > ----------------------------------------------------------------------
> >
> > Message: 1
> > Date: Fri, 19 Oct 2018 15:38:33 +0000
> > From: Teresa Peluso <tpeluso at equinix.com>
> > To: "Csatari, Gergely (Nokia - HU/Budapest)"
> >         <gergely.csatari at nokia.com>, "OpenStack Development Mailing
> List (not
> >         for usage questions)" <openstack-dev at lists.openstack.org>,
> >         "fulton at redhat.com" <fulton at redhat.com>,
> >         "edge-computing at lists.openstack.org"
> >         <edge-computing at lists.openstack.org>
> > Cc: "openstack-sigs at lists.openstack.org"
> >         <openstack-sigs at lists.openstack.org>
> > Subject: Re: [Edge-computing] [openstack-dev] [Openstack-sigs] [FEMDC]
> >         [Edge] [tripleo] On the use of terms "Edge" and "Far Edge"
> > Message-ID:
> >         <
> BY1PR0401MB1350FCABDEF1BF76C8917285A6F90 at BY1PR0401MB1350.namprd04.prod.outlook.com
> >
> >
> > Content-Type: text/plain; charset="utf-8"
> >
> > Fyi – could this help?
> https://www.linuxfoundation.org/blog/2018/06/edge-computing-just-got-its-rosetta-stone/
> >
> > https://imasons.org/ starting to host workshops about this as well
> https://imasons.org/events/2018-im-edge-congress/
> >
> > From: Csatari, Gergely (Nokia - HU/Budapest) <gergely.csatari at nokia.com>
> > Sent: Friday, October 19, 2018 1:05 AM
> > To: OpenStack Development Mailing List (not for usage questions) <
> openstack-dev at lists.openstack.org>; fulton at redhat.com;
> edge-computing at lists.openstack.org
> > Cc: openstack-sigs at lists.openstack.org
> > Subject: [EXTERNAL] Re: [Edge-computing] [openstack-dev]
> [Openstack-sigs] [FEMDC] [Edge] [tripleo] On the use of terms "Edge" and
> "Far Edge"
> >
> > Hi,
> >
> > I’m adding the ECG mailing list to the discussion.
> >
> > I think the root of the problem is that there is no single definition of
> „the edge” (except for [1<
> https://urldefense.proofpoint.com/v2/url?u=https-3A__en.wikipedia.org_wiki_The-5FEdge&d=DwMGaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=JcbYkw8s_8JtubERIbsy_0Qc_q0zGK9nUrtf2IWVNmQ&m=VtNo9cSRcnVhW9PH68IA26gNRrJ96V0O7MHTeONQ-hY&s=J6lr_T9m7mkisVR7l1QzmBki20r5He3fuZXvbYg-EPs&e=>]),
> but it changes from group to group or use case to use case. What I
> recognise as the commonalities in these edge definitions, are 1) a
> distributed cloud infrastructure (kind of a cloud of clouds) 2) need for
> automation or everything 3) resource constraints for the control plane.
> >
> > The different edge variants are putting different emphasis on these
> common needs based ont he use case discussed.
> >
> > To have a more clear understanding of these definitions we could try the
> following:
> >
> >   1.  Always add the definition of these to the given context
> >   2.  Check what other groups are using and adopt to that
> >   3.  Define our own language and expect everyone else to adopt
> >
> > Br,
> > Gerg0
> >
> >
> >
> > [1]: https://en.wikipedia.org/wiki/The_Edge<
> https://urldefense.proofpoint.com/v2/url?u=https-3A__en.wikipedia.org_wiki_The-5FEdge&d=DwQGaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=JcbYkw8s_8JtubERIbsy_0Qc_q0zGK9nUrtf2IWVNmQ&m=VtNo9cSRcnVhW9PH68IA26gNRrJ96V0O7MHTeONQ-hY&s=J6lr_T9m7mkisVR7l1QzmBki20r5He3fuZXvbYg-EPs&e=
> >
> >
> > From: Jim Rollenhagen <jim at jimrollenhagen.com<mailto:
> jim at jimrollenhagen.com>>
> > Sent: Thursday, October 18, 2018 11:43 PM
> > To: fulton at redhat.com<mailto:fulton at redhat.com>; OpenStack Development
> Mailing List (not for usage questions) <openstack-dev at lists.openstack.org
> <mailto:openstack-dev at lists.openstack.org>>
> > Cc: openstack-sigs at lists.openstack.org<mailto:
> openstack-sigs at lists.openstack.org>
> > Subject: Re: [openstack-dev] [Openstack-sigs] [FEMDC] [Edge] [tripleo]
> On the use of terms "Edge" and "Far Edge"
> >
> > On Thu, Oct 18, 2018 at 4:45 PM John Fulton <johfulto at redhat.com<mailto:
> johfulto at redhat.com>> wrote:
> > On Thu, Oct 18, 2018 at 11:56 AM Jim Rollenhagen <jim at jimrollenhagen.com
> <mailto:jim at jimrollenhagen.com>> wrote:
> > >
> > > On Thu, Oct 18, 2018 at 10:23 AM Dmitry Tantsur <dtantsur at redhat.com
> <mailto:dtantsur at redhat.com>> wrote:
> > >>
> > >> Hi all,
> > >>
> > >> Sorry for chiming in really late in this topic, but I think $subj is
> worth
> > >> discussing until we settle harder on the potentially confusing
> terminology.
> > >>
> > >> I think the difference between "Edge" and "Far Edge" is too vague to
> use these
> > >> terms in practice. Think about the "edge" metaphor itself: something
> rarely has
> > >> several layers of edges. A knife has an edge, there are no far edges.
> I imagine
> > >> zooming in and seeing more edges at the edge, and then it's quite
> cool indeed,
> > >> but is it really a useful metaphor for those who never used a strong
> microscope? :)
> > >>
> > >> I think in the trivial sense "Far Edge" is a tautology, and should be
> avoided.
> > >> As a weak proof of my words, I already see a lot of smart people
> confusing these
> > >> two and actually use Central/Edge where they mean Edge/Far Edge. I
> suggest we
> > >> adopt a different terminology, even if it less consistent with
> typical marketing
> > >> term around the "Edge" movement.
> > >
> > >
> > > FWIW, we created rough definitions of "edge" and "far edge" during the
> edge WG session in Denver.
> > > It's mostly based on latency to the end user, though we also talked
> about quantities of compute resources, if someone can find the pictures.
> >
> > Perhaps these are the pictures Jim was referring to?
> >
> https://www.dropbox.com/s/255x1cao14taer3/MVP-Architecture_edge-computing_PTG.pptx?dl=0#
> <
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.dropbox.com_s_255x1cao14taer3_MVP-2DArchitecture-5Fedge-2Dcomputing-5FPTG.pptx-3Fdl-3D0&d=DwMGaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=JcbYkw8s_8JtubERIbsy_0Qc_q0zGK9nUrtf2IWVNmQ&m=VtNo9cSRcnVhW9PH68IA26gNRrJ96V0O7MHTeONQ-hY&s=Zh9LBq_sTlZxC5xI7FupdttxdRrhrwmoIsY4eZRlvjM&e=
> >
> >
> > That's it, thank you!
> >
> > // jim
> >
> >
> >
> > I'm involved in some TripleO work called the split control plane:
> >
> https://specs.openstack.org/openstack/tripleo-specs/specs/rocky/split-controlplane.html
> <
> https://urldefense.proofpoint.com/v2/url?u=https-3A__specs.openstack.org_openstack_tripleo-2Dspecs_specs_rocky_split-2Dcontrolplane.html&d=DwMGaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=JcbYkw8s_8JtubERIbsy_0Qc_q0zGK9nUrtf2IWVNmQ&m=VtNo9cSRcnVhW9PH68IA26gNRrJ96V0O7MHTeONQ-hY&s=tuDTh6QOmYEza4K8a7S2RoUpc1ttgBTHVC8re5vfcdg&e=
> >
> >
> > After the PTG I saw that the split control plane was compatible with
> > the type of deployment discussed at the edge WG session in Denver and
> > described the compatibility at:
> >
> https://etherpad.openstack.org/p/tripleo-edge-working-group-split-control-plane
> <
> https://urldefense.proofpoint.com/v2/url?u=https-3A__etherpad.openstack.org_p_tripleo-2Dedge-2Dworking-2Dgroup-2Dsplit-2Dcontrol-2Dplane&d=DwMGaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=JcbYkw8s_8JtubERIbsy_0Qc_q0zGK9nUrtf2IWVNmQ&m=VtNo9cSRcnVhW9PH68IA26gNRrJ96V0O7MHTeONQ-hY&s=5Ak84Rb4c98_jEqNWjvWYCeVAN0XkbZzdXVWax9oo_Q&e=
> >
> >
> > > See the picture and table here:
> https://wiki.openstack.org/wiki/Edge_Computing_Group/Edge_Reference_Architectures#Overview
> <
> https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.openstack.org_wiki_Edge-5FComputing-5FGroup_Edge-5FReference-5FArchitectures-23Overview&d=DwMGaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=JcbYkw8s_8JtubERIbsy_0Qc_q0zGK9nUrtf2IWVNmQ&m=VtNo9cSRcnVhW9PH68IA26gNRrJ96V0O7MHTeONQ-hY&s=yqEH7weN-I2YvoYDRi6nSWGtNzQsX-HfBieGuOBow1M&e=
> >
> > >
> > >> Now, I don't have really great suggestions. Something that came up in
> TripleO
> > >> discussions [1] is Core/Hub/Edge, which I think reflects the idea
> better.
> > >
> > >
> > > I'm also fine with these names, as they do describe the concepts well.
> :)
> > >
> > > // jim
> >
> > I'm fine with these terms too. In split control plane there's a
> > deployment method for deploying a central site and then deploying
> > remote sites independently. That deployment method could be used to
> > deploy  Core/Hub/Edge sites too. E.g. deploy the Core using Heat stack
> > N. Deploy a Hub using stack N+1 and then deploy an Edge using stack
> > N+2 etc.
> >
> >   John
> >
> > >>
> > >> I'd be very interested to hear your ideas.
> > >>
> > >> Dmitry
> > >>
> > >> [1] https://etherpad.openstack.org/p/tripleo-edge-mvp<
> https://urldefense.proofpoint.com/v2/url?u=https-3A__etherpad.openstack.org_p_tripleo-2Dedge-2Dmvp&d=DwMGaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=JcbYkw8s_8JtubERIbsy_0Qc_q0zGK9nUrtf2IWVNmQ&m=VtNo9cSRcnVhW9PH68IA26gNRrJ96V0O7MHTeONQ-hY&s=XI1J9s1i2KxUSnOX9Yk3XQ_5kH08UoWZ_uqd6Y3efQU&e=
> >
> > >>
> > >> _______________________________________________
> > >> openstack-sigs mailing list
> > >> openstack-sigs at lists.openstack.org<mailto:
> openstack-sigs at lists.openstack.org>
> > >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs<
> https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_openstack-2Dsigs&d=DwMGaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=JcbYkw8s_8JtubERIbsy_0Qc_q0zGK9nUrtf2IWVNmQ&m=VtNo9cSRcnVhW9PH68IA26gNRrJ96V0O7MHTeONQ-hY&s=TmAFzLOVMjHTW569gUKwSRI4OwLlF5tOqAlcYuPaCHM&e=
> >
> > >
> > >
> __________________________________________________________________________
> > > OpenStack Development Mailing List (not for usage questions)
> > > Unsubscribe:
> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe<
> https://urldefense.proofpoint.com/v2/url?u=http-3A__OpenStack-2Ddev-2Drequest-40lists.openstack.org-3Fsubject-3Aunsubscribe&d=DwMGaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=JcbYkw8s_8JtubERIbsy_0Qc_q0zGK9nUrtf2IWVNmQ&m=VtNo9cSRcnVhW9PH68IA26gNRrJ96V0O7MHTeONQ-hY&s=fH-cGOV9QxQ5JB6p2hhzcysjmij8hCyy3ptvz6tystU&e=
> >
> > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<
> https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_openstack-2Ddev&d=DwMGaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=JcbYkw8s_8JtubERIbsy_0Qc_q0zGK9nUrtf2IWVNmQ&m=VtNo9cSRcnVhW9PH68IA26gNRrJ96V0O7MHTeONQ-hY&s=161pS98mNzJwzSvHGBh3w1L6xADUAa9R08Qf-LQEjUQ&e=
> >
> >
> >
> __________________________________________________________________________
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe:
> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe<
> https://urldefense.proofpoint.com/v2/url?u=http-3A__OpenStack-2Ddev-2Drequest-40lists.openstack.org-3Fsubject-3Aunsubscribe&d=DwMGaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=JcbYkw8s_8JtubERIbsy_0Qc_q0zGK9nUrtf2IWVNmQ&m=VtNo9cSRcnVhW9PH68IA26gNRrJ96V0O7MHTeONQ-hY&s=fH-cGOV9QxQ5JB6p2hhzcysjmij8hCyy3ptvz6tystU&e=
> >
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<
> https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_openstack-2Ddev&d=DwMGaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=JcbYkw8s_8JtubERIbsy_0Qc_q0zGK9nUrtf2IWVNmQ&m=VtNo9cSRcnVhW9PH68IA26gNRrJ96V0O7MHTeONQ-hY&s=161pS98mNzJwzSvHGBh3w1L6xADUAa9R08Qf-LQEjUQ&e=
> >
> > -------------- next part --------------
> > An HTML attachment was scrubbed...
> > URL: <
> http://lists.openstack.org/pipermail/edge-computing/attachments/20181019/4b140cb6/attachment.html
> >
> >
> > ------------------------------
> >
> > Subject: Digest Footer
> >
> > _______________________________________________
> > Edge-computing mailing list
> > Edge-computing at lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
> >
> >
> > ------------------------------
> >
> > End of Edge-computing Digest, Vol 12, Issue 6
> > *********************************************
> > _______________________________________________
> > 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/20181024/fd63b7ec/attachment-0001.html>

From ildiko at openstack.org  Wed Oct 24 19:38:57 2018
From: ildiko at openstack.org (Ildiko Vancsa)
Date: Wed, 24 Oct 2018 21:38:57 +0200
Subject: [Edge-computing] Announcing the First Release of StarlingX,
 an open source edge computing platform
Message-ID: <1E266F44-13D5-4A72-8AE2-01816B909E0C@openstack.org>

Hi,

You may have heard, StarlingX[1] is a new independent, top-level, open source pilot project that's supported by the OpenStack Foundation. StarlingX joins other pilot projects hosted at OpenStack Foundation[2], including Airship, Kata Containers and Zuul.

Today the first release of StarlingX is here!

We invite you to participate in getting the word out that the release is ready and that we’re eager to welcome more contributors to this project.

Learn more about it:
	• Read more about the project at starlingx.io
	• Listen to a recording of the onboarding webinar[3]
	• On-boarding slide deck[4]
	• Overview document[5]

Some things you can share:
	• A blog on starlingx.io[6]
	• Social sharing: Announcements on Twitter[7]

Want to get involved in the community?
	• Mailing Lists[8] 
	• Weekly Calls[9]
	• Freenode IRC: #starlingx channel[10]

Ready to dive into the code?
	• You can get download the first release at git.starlingx.io 
	• StarlingX Install Guide[11] 
	• StarlingX Developer Guide[12]

If you’re at the Berlin Summit November 13-15[13]:
Tuesday 11/13
	• StarlingX – Project update – 6 months in the life of a new Open Source project with Brent Rowsell & Dean Troyer
	• StarlingX CI, from zero to Zuul with Hazzim Anaya & Elio Martinez

Wednesday 11/14 
	• Keynote spotlight on the main stage with Ian Jolliffe & Dean Troyer
	• MVP (Minimum Viable Product) architecture for edge - Forum session
	• "Ask Me Anything" about StarlingX - Forum session
	• StarlingX Enhancements for Edge Networking presentation with Kailun Qin, Ruijing Guo & Dan Chen
	• Project Onboarding session with Greg Waines
	• Integrating IOT Device Management with the Edge Cloud - Forum session

Thursday 11/15
	• Containerized Applications' Requirements on Kubernetes Cluster at the Edge - Forum session

Check out the materials to learn about the project, try out the software and join the community! We hope to see many of you in Berlin!

Ildikó

[1] https://www.starlingx.io/ 
[2] https://www.openstack.org/foundation/
[3] https://www.youtube.com/watch?v=G9uwGnKD6tM&t=232s 
[4] https://www.starlingx.io/collateral/StarlingX-Onboarding-Deck-Web.pdf 
[5] https://www.starlingx.io/collateral/StarlingX_OnePager_Web-102318pdf/
[6] https://www.starlingx.io/blog/starlingx-initial-release.html
[7] https://twitter.com/starlingx
[8] http://lists.starlingx.io/cgi-bin/mailman/listinfo
[9] https://wiki.openstack.org/wiki/Starlingx/Meetings
[10] https://freenode.net/
[11] https://docs.starlingx.io/installation_guide/index.html
[12] https://docs.starlingx.io/developer_guide/index.html
[13] https://www.openstack.org/summit/berlin-2018




From ildiko at openstack.org  Mon Oct 29 18:31:31 2018
From: ildiko at openstack.org (Ildiko Vancsa)
Date: Mon, 29 Oct 2018 19:31:31 +0100
Subject: [Edge-computing] Weekly call at APAC time slot
Message-ID: <5E0FD468-2F61-44CE-B86A-2CF8D27CA388@openstack.org>

Hi,

It is a friendly reminder that we will have our weekly call in the APAC time slot this week, which is __Thursday at 0700 UTC__.

For agenda and dial-in info please see the wiki: https://wiki.openstack.org/wiki/Edge_Computing_Group#Meetings

Please let me know if you have any questions.

Thanks and Best Regards,
Ildikó




From bdobreli at redhat.com  Wed Oct 31 14:57:00 2018
From: bdobreli at redhat.com (Bogdan Dobrelya)
Date: Wed, 31 Oct 2018 15:57:00 +0100
Subject: [Edge-computing] [tripleo][FEMDC] IEEE Fog Computing: Call for
 Contributions - Deadline Approaching
In-Reply-To: <CAKe3RKoGZ+ejL-mfhB1dAROkKC=OBbf2b8kizQHJw3GJUzWqcw@mail.gmail.com>
References: <CAKe3RKoGZ+ejL-mfhB1dAROkKC=OBbf2b8kizQHJw3GJUzWqcw@mail.gmail.com>
Message-ID: <53cf2d33-cee7-3f0d-7f28-74b29091a7ef@redhat.com>

(cross-posting openstack-dev)

Hello.
[tl;dr] I'm looking for co-author(s) to come up with "Edge clouds data 
consistency requirements and challenges" a position paper [0] (papers 
submitting deadline is Nov 8).

The problem scope is synchronizing control plane and/or 
deployments-specific data (not necessary limited to OpenStack) across 
remote Edges and central Edge and management site(s). Including the same 
aspects for overclouds and undercloud(s), in terms of TripleO; and other 
deployment tools of your choice.

Another problem is to not go into different solutions for Edge 
deployments management and control planes of edges. And for tenants as 
well, if we think of tenants also doing Edge deployments based on Edge 
Data Replication as a Service, say for Kubernetes/OpenShift on top of 
OpenStack.

So the paper should name the outstanding problems, define data 
consistency requirements and pose possible solutions for synchronization 
and conflicts resolving. Having maximum autonomy cases supported for 
isolated sites, with a capability to eventually catch up its distributed 
state. Like global database [1], or something different perhaps (see 
causal-real-time consistency model [2],[3]), or even using git. And 
probably more than that?.. (looking for ideas)

See also the "check" list in-line, which I think also meets the data 
consistency topics well - it would be always nice to have some 
theoretical foundations at hand, when repairing some 
1000-edges-spread-off and fully broken global database, by hand :)

PS. I must admit I have yet any experience with those IEEE et al 
academic things and looking for someone who has it, to team and 
co-author that positioning paper by. That's as a start, then we can 
think of presenting it and expanding into work items for OpenStack Edge 
WG and future development plans.

[0] http://conferences.computer.org/ICFC/2019/Paper_Submission.html
[1] https://review.openstack.org/600555
[2] https://jepsen.io/consistency
[3] http://www.cs.cornell.edu/lorenzo/papers/cac-tr.pdf

On 10/22/18 3:44 PM, Flavia Delicato wrote:
> =================================================================================
> IEEE International Conference on Fog Computing (ICFC 2019)
> June 24-26, 2019
> Prague, Czech Republic
> http://conferences.computer.org/ICFC/2019/
> Co-located with the IEEE International Conference on Cloud Engineering
> (IC2E 2019)
> ==================================================================================
> 
> Important Dates
> ---------------
> Paper registration and abstract: Nov 1st, 2018
> Full paper submission due: Nov 8th, 2018
> Notification of paper acceptance: Jan. 20th, 2019
> Workshop and tutorial proposals due: Nov 11, 2018
> Notification of proposal acceptance: Nov 18, 2018
> 
> Call for Contributions
> ----------------------
> Fog computing is the extension of cloud computing into its edge and
> the physical world to meet the data volume and decision velocity
> requirements in many emerging applications, such as augmented and
> virtual realities (AR/VR), cyber-physical systems (CPS), intelligent
> and autonomous systems, and mission-critical systems. The boundary
> between centralized, powerful computing cloud and massively
> distributed, Internet connected sensors, actuators, and things is
> blurred in this new computing paradigm.
> 
> The ICFC 2019 technical program will feature tutorials, workshops, and
> research paper sessions. We solicit high-quality contributions in the
> above categories. Details of submission is available on the conference
> Web site. Topics of interest include but are not limited to:
> 
> * System architecture for fog computing

(check)

> * Coordination between cloud, fog, and sensing/actuation endpoints
> * Connectivity, storage, and computation in the edge
> * Data processing and management for fog computing

(check)

> * Efficient and embedded AI in the fog
> * System and network manageability
> * Middleware and coordination platforms
> * Power, energy, and resource management
> * Device and hardware support for fog computing
> * Programming models, abstractions, and software engineering for fog computing

(check)

> * Security, privacy, and ethics issues related to fog computing
> * Theoretical foundations and formal methods for fog computing systems

(check)

> * Applications and experiences
> 
> Organizing Committee
> --------------------
> General Chairs:
> Hui Lei, IBM
> Albert Zomaya, The University of Sydney
> 
> PC Co-chairs:
> Erol Gelenbe, Imperial College London
> Jie Liu, Microsoft Research
> 
> Tutorials and Workshops Chair:
> David Bermbach, TU Berlin
> 
> Publicity Co-chairs:
> Flavia Delicato,Federal University of Rio de Janeiro
> Mathias Fischer, University Hamburg
> 
> Publication Chair
> Javid Taheri, Karlstad University
> 
> Webmaster
> Wei Li, The University of Sydney
> 
> Steering Committee
> ------------------
> Mung Chiang, Purdue University
> Erol Gelenbe, Imperial College London
> Christos Kozarakis, Stanford University
> Hui Lei, IBM
> Chenyang Lu, Washington University in St Louis
> Beng Chin Ooi, National University of Singapore
> Neeraj Suri, TU Darmstadt
> Albert Zomaya, The University of Sydney
> 
> Program Committee
> ------------------
> 
> Tarek Abdelzaher, UIUC
> Anne Benoit, ENS Lyon
> David Bermbach, TU Berlin
> Bharat Bhargava, Purdue University
> Olivier Brun, LAAS/CNRS Laboratory
> Jiannong Cao, Hong Kong Polytech
> Flavia C. Delicato, UFRJ, Brazil
> Xiaotie Deng, Peking University, China
> Schahram Dustdar, TU Wien, Germany
> Maria Gorlatova, Duke University
> Dharanipragada Janakiram, IIT Madras
> Wenjing Luo, Virginia Tech
> Pedro José Marrón, Universität Duisburg-Essen
> Geyong Min, University of Exeter
> Suman Nath, Microsoft Research
> Vincenzo Piuri, Universita Degli Studi Di Milano
> Yong Meng Teo, National University of Singapore
> Guoliang Xing, Chinese University of Hong Kong
> Yuanyuan Yang, SUNY Stony Brook
> Xiaoyun Zhu, Cloudera
> 


-- 
Best regards,
Bogdan Dobrelya,
Irc #bogdando


From bdobreli at redhat.com  Wed Oct 31 16:53:38 2018
From: bdobreli at redhat.com (Bogdan Dobrelya)
Date: Wed, 31 Oct 2018 17:53:38 +0100
Subject: [Edge-computing] [tripleo][FEMDC] IEEE Fog Computing: Call for
 Contributions - Deadline Approaching
In-Reply-To: <53cf2d33-cee7-3f0d-7f28-74b29091a7ef@redhat.com>
References: <CAKe3RKoGZ+ejL-mfhB1dAROkKC=OBbf2b8kizQHJw3GJUzWqcw@mail.gmail.com>
 <53cf2d33-cee7-3f0d-7f28-74b29091a7ef@redhat.com>
Message-ID: <8acb2f9e-9fbd-77be-a274-eb3d54ae2ab4@redhat.com>

I forgot to mention the submission registration and abstract has to be 
submitted today. I've created it as #1570506394, and the paper itself 
can be uploaded until the Nov 8 (or Nov 9 perhaps as the registration 
system shows to me). I'm not sure that paper number is searchable 
publicly, so here is the paper name and abstract for your kind review 
please:

name: "Edge clouds control plane and management data consistency challenges"
abstract: "Fog computing is emerging Cloud of (Edge) Clouds technology. 
Its control plane and deployments data synchronization is a major 
challenge. Autonomy requirements expect even the most distant edge sites 
always manageable, available for monitoring and alerting, scaling 
up/down, upgrading and applying security fixes. Whenever temporary 
disconnected sites are managed locally or centrally, some changes and 
data need to be eventually synchronized back to the central site(s) with 
having its merge-conflicts resolved for the central data hub(s). While 
some data needs to be pushed from the central site(s) to the Edge, which 
might require resolving data collisions at the remote sites as well. In 
this paper, we position the outstanding data synchronization problems 
for OpenStack cloud platform becoming a solution number one for fog 
computing. We outline the data consistency requirements and design 
approaches to meet the AA (Always Available) autonomy expectations. 
Finally, the paper brings the vision of unified tooling, which solves 
the data synchronization problems the same way for infrastructure 
owners, IaaS cloud operators and tenants running workloads for PaaS like 
OpenShift or Kubernetes deployed on top of OpenStack. The secondary goal 
of this work is to help cloud architects and developers to federate 
stateful cloud components over reliable distributed data backends and 
having its failure modes known."
Thank you  for your time, if still reading this.

On 10/31/18 3:57 PM, Bogdan Dobrelya wrote:
> (cross-posting openstack-dev)
> 
> Hello.
> [tl;dr] I'm looking for co-author(s) to come up with "Edge clouds data 
> consistency requirements and challenges" a position paper [0] (papers 
> submitting deadline is Nov 8).
> 
> The problem scope is synchronizing control plane and/or 
> deployments-specific data (not necessary limited to OpenStack) across 
> remote Edges and central Edge and management site(s). Including the same 
> aspects for overclouds and undercloud(s), in terms of TripleO; and other 
> deployment tools of your choice.
> 
> Another problem is to not go into different solutions for Edge 
> deployments management and control planes of edges. And for tenants as 
> well, if we think of tenants also doing Edge deployments based on Edge 
> Data Replication as a Service, say for Kubernetes/OpenShift on top of 
> OpenStack.
> 
> So the paper should name the outstanding problems, define data 
> consistency requirements and pose possible solutions for synchronization 
> and conflicts resolving. Having maximum autonomy cases supported for 
> isolated sites, with a capability to eventually catch up its distributed 
> state. Like global database [1], or something different perhaps (see 
> causal-real-time consistency model [2],[3]), or even using git. And 
> probably more than that?.. (looking for ideas)
> 
> See also the "check" list in-line, which I think also meets the data 
> consistency topics well - it would be always nice to have some 
> theoretical foundations at hand, when repairing some 
> 1000-edges-spread-off and fully broken global database, by hand :)
> 
> PS. I must admit I have yet any experience with those IEEE et al 
> academic things and looking for someone who has it, to team and 
> co-author that positioning paper by. That's as a start, then we can 
> think of presenting it and expanding into work items for OpenStack Edge 
> WG and future development plans.
> 
> [0] http://conferences.computer.org/ICFC/2019/Paper_Submission.html
> [1] https://review.openstack.org/600555
> [2] https://jepsen.io/consistency
> [3] http://www.cs.cornell.edu/lorenzo/papers/cac-tr.pdf
> 
> On 10/22/18 3:44 PM, Flavia Delicato wrote:
>> ================================================================================= 
>>
>> IEEE International Conference on Fog Computing (ICFC 2019)
>> June 24-26, 2019
>> Prague, Czech Republic
>> http://conferences.computer.org/ICFC/2019/
>> Co-located with the IEEE International Conference on Cloud Engineering
>> (IC2E 2019)
>> ================================================================================== 
>>
>>
>> Important Dates
>> ---------------
>> Paper registration and abstract: Nov 1st, 2018
>> Full paper submission due: Nov 8th, 2018
>> Notification of paper acceptance: Jan. 20th, 2019
>> Workshop and tutorial proposals due: Nov 11, 2018
>> Notification of proposal acceptance: Nov 18, 2018
>>
>> Call for Contributions
>> ----------------------
>> Fog computing is the extension of cloud computing into its edge and
>> the physical world to meet the data volume and decision velocity
>> requirements in many emerging applications, such as augmented and
>> virtual realities (AR/VR), cyber-physical systems (CPS), intelligent
>> and autonomous systems, and mission-critical systems. The boundary
>> between centralized, powerful computing cloud and massively
>> distributed, Internet connected sensors, actuators, and things is
>> blurred in this new computing paradigm.
>>
>> The ICFC 2019 technical program will feature tutorials, workshops, and
>> research paper sessions. We solicit high-quality contributions in the
>> above categories. Details of submission is available on the conference
>> Web site. Topics of interest include but are not limited to:
>>
>> * System architecture for fog computing
> 
> (check)
> 
>> * Coordination between cloud, fog, and sensing/actuation endpoints
>> * Connectivity, storage, and computation in the edge
>> * Data processing and management for fog computing
> 
> (check)
> 
>> * Efficient and embedded AI in the fog
>> * System and network manageability
>> * Middleware and coordination platforms
>> * Power, energy, and resource management
>> * Device and hardware support for fog computing
>> * Programming models, abstractions, and software engineering for fog 
>> computing
> 
> (check)
> 
>> * Security, privacy, and ethics issues related to fog computing
>> * Theoretical foundations and formal methods for fog computing systems
> 
> (check)
> 
>> * Applications and experiences
>>
>> Organizing Committee
>> --------------------
>> General Chairs:
>> Hui Lei, IBM
>> Albert Zomaya, The University of Sydney
>>
>> PC Co-chairs:
>> Erol Gelenbe, Imperial College London
>> Jie Liu, Microsoft Research
>>
>> Tutorials and Workshops Chair:
>> David Bermbach, TU Berlin
>>
>> Publicity Co-chairs:
>> Flavia Delicato,Federal University of Rio de Janeiro
>> Mathias Fischer, University Hamburg
>>
>> Publication Chair
>> Javid Taheri, Karlstad University
>>
>> Webmaster
>> Wei Li, The University of Sydney
>>
>> Steering Committee
>> ------------------
>> Mung Chiang, Purdue University
>> Erol Gelenbe, Imperial College London
>> Christos Kozarakis, Stanford University
>> Hui Lei, IBM
>> Chenyang Lu, Washington University in St Louis
>> Beng Chin Ooi, National University of Singapore
>> Neeraj Suri, TU Darmstadt
>> Albert Zomaya, The University of Sydney
>>
>> Program Committee
>> ------------------
>>
>> Tarek Abdelzaher, UIUC
>> Anne Benoit, ENS Lyon
>> David Bermbach, TU Berlin
>> Bharat Bhargava, Purdue University
>> Olivier Brun, LAAS/CNRS Laboratory
>> Jiannong Cao, Hong Kong Polytech
>> Flavia C. Delicato, UFRJ, Brazil
>> Xiaotie Deng, Peking University, China
>> Schahram Dustdar, TU Wien, Germany
>> Maria Gorlatova, Duke University
>> Dharanipragada Janakiram, IIT Madras
>> Wenjing Luo, Virginia Tech
>> Pedro José Marrón, Universität Duisburg-Essen
>> Geyong Min, University of Exeter
>> Suman Nath, Microsoft Research
>> Vincenzo Piuri, Universita Degli Studi Di Milano
>> Yong Meng Teo, National University of Singapore
>> Guoliang Xing, Chinese University of Hong Kong
>> Yuanyuan Yang, SUNY Stony Brook
>> Xiaoyun Zhu, Cloudera
>>
> 
> 


-- 
Best regards,
Bogdan Dobrelya,
Irc #bogdando


From ildiko.vancsa at gmail.com  Wed Oct 31 17:54:46 2018
From: ildiko.vancsa at gmail.com (Ildiko Vancsa)
Date: Wed, 31 Oct 2018 18:54:46 +0100
Subject: [Edge-computing] [tripleo][FEMDC] IEEE Fog Computing: Call for
 Contributions - Deadline Approaching
In-Reply-To: <8acb2f9e-9fbd-77be-a274-eb3d54ae2ab4@redhat.com>
References: <CAKe3RKoGZ+ejL-mfhB1dAROkKC=OBbf2b8kizQHJw3GJUzWqcw@mail.gmail.com>
 <53cf2d33-cee7-3f0d-7f28-74b29091a7ef@redhat.com>
 <8acb2f9e-9fbd-77be-a274-eb3d54ae2ab4@redhat.com>
Message-ID: <B0E8D7E2-67A5-4465-B7EE-ACA82E1B787B@gmail.com>

Hi,

Thank you for sharing your proposal.

I think this is a very interesting topic with a list of possible solutions some of which this group is also discussing. It would also be great to learn more about the IEEE activities and have experience about the process in this group on the way forward.

I personally do not have experience with IEEE conferences, but I’m happy to help with the paper if I can.

Thanks,
Ildikó


> On 2018. Oct 31., at 17:53, Bogdan Dobrelya <bdobreli at redhat.com> wrote:
> 
> I forgot to mention the submission registration and abstract has to be submitted today. I've created it as #1570506394, and the paper itself can be uploaded until the Nov 8 (or Nov 9 perhaps as the registration system shows to me). I'm not sure that paper number is searchable publicly, so here is the paper name and abstract for your kind review please:
> 
> name: "Edge clouds control plane and management data consistency challenges"
> abstract: "Fog computing is emerging Cloud of (Edge) Clouds technology. Its control plane and deployments data synchronization is a major challenge. Autonomy requirements expect even the most distant edge sites always manageable, available for monitoring and alerting, scaling up/down, upgrading and applying security fixes. Whenever temporary disconnected sites are managed locally or centrally, some changes and data need to be eventually synchronized back to the central site(s) with having its merge-conflicts resolved for the central data hub(s). While some data needs to be pushed from the central site(s) to the Edge, which might require resolving data collisions at the remote sites as well. In this paper, we position the outstanding data synchronization problems for OpenStack cloud platform becoming a solution number one for fog computing. We outline the data consistency requirements and design approaches to meet the AA (Always Available) autonomy expectations. Finally, the paper brings the vision of unified tooling, which solves the data synchronization problems the same way for infrastructure owners, IaaS cloud operators and tenants running workloads for PaaS like OpenShift or Kubernetes deployed on top of OpenStack. The secondary goal of this work is to help cloud architects and developers to federate stateful cloud components over reliable distributed data backends and having its failure modes known."
> Thank you  for your time, if still reading this.
> 
> On 10/31/18 3:57 PM, Bogdan Dobrelya wrote:
>> (cross-posting openstack-dev)
>> Hello.
>> [tl;dr] I'm looking for co-author(s) to come up with "Edge clouds data consistency requirements and challenges" a position paper [0] (papers submitting deadline is Nov 8).
>> The problem scope is synchronizing control plane and/or deployments-specific data (not necessary limited to OpenStack) across remote Edges and central Edge and management site(s). Including the same aspects for overclouds and undercloud(s), in terms of TripleO; and other deployment tools of your choice.
>> Another problem is to not go into different solutions for Edge deployments management and control planes of edges. And for tenants as well, if we think of tenants also doing Edge deployments based on Edge Data Replication as a Service, say for Kubernetes/OpenShift on top of OpenStack.
>> So the paper should name the outstanding problems, define data consistency requirements and pose possible solutions for synchronization and conflicts resolving. Having maximum autonomy cases supported for isolated sites, with a capability to eventually catch up its distributed state. Like global database [1], or something different perhaps (see causal-real-time consistency model [2],[3]), or even using git. And probably more than that?.. (looking for ideas)
>> See also the "check" list in-line, which I think also meets the data consistency topics well - it would be always nice to have some theoretical foundations at hand, when repairing some 1000-edges-spread-off and fully broken global database, by hand :)
>> PS. I must admit I have yet any experience with those IEEE et al academic things and looking for someone who has it, to team and co-author that positioning paper by. That's as a start, then we can think of presenting it and expanding into work items for OpenStack Edge WG and future development plans.
>> [0] http://conferences.computer.org/ICFC/2019/Paper_Submission.html
>> [1] https://review.openstack.org/600555
>> [2] https://jepsen.io/consistency
>> [3] http://www.cs.cornell.edu/lorenzo/papers/cac-tr.pdf
>> On 10/22/18 3:44 PM, Flavia Delicato wrote:
>>> ================================================================================= 
>>> IEEE International Conference on Fog Computing (ICFC 2019)
>>> June 24-26, 2019
>>> Prague, Czech Republic
>>> http://conferences.computer.org/ICFC/2019/
>>> Co-located with the IEEE International Conference on Cloud Engineering
>>> (IC2E 2019)
>>> ================================================================================== 
>>> 
>>> Important Dates
>>> ---------------
>>> Paper registration and abstract: Nov 1st, 2018
>>> Full paper submission due: Nov 8th, 2018
>>> Notification of paper acceptance: Jan. 20th, 2019
>>> Workshop and tutorial proposals due: Nov 11, 2018
>>> Notification of proposal acceptance: Nov 18, 2018
>>> 
>>> Call for Contributions
>>> ----------------------
>>> Fog computing is the extension of cloud computing into its edge and
>>> the physical world to meet the data volume and decision velocity
>>> requirements in many emerging applications, such as augmented and
>>> virtual realities (AR/VR), cyber-physical systems (CPS), intelligent
>>> and autonomous systems, and mission-critical systems. The boundary
>>> between centralized, powerful computing cloud and massively
>>> distributed, Internet connected sensors, actuators, and things is
>>> blurred in this new computing paradigm.
>>> 
>>> The ICFC 2019 technical program will feature tutorials, workshops, and
>>> research paper sessions. We solicit high-quality contributions in the
>>> above categories. Details of submission is available on the conference
>>> Web site. Topics of interest include but are not limited to:
>>> 
>>> * System architecture for fog computing
>> (check)
>>> * Coordination between cloud, fog, and sensing/actuation endpoints
>>> * Connectivity, storage, and computation in the edge
>>> * Data processing and management for fog computing
>> (check)
>>> * Efficient and embedded AI in the fog
>>> * System and network manageability
>>> * Middleware and coordination platforms
>>> * Power, energy, and resource management
>>> * Device and hardware support for fog computing
>>> * Programming models, abstractions, and software engineering for fog computing
>> (check)
>>> * Security, privacy, and ethics issues related to fog computing
>>> * Theoretical foundations and formal methods for fog computing systems
>> (check)
>>> * Applications and experiences
>>> 
>>> Organizing Committee
>>> --------------------
>>> General Chairs:
>>> Hui Lei, IBM
>>> Albert Zomaya, The University of Sydney
>>> 
>>> PC Co-chairs:
>>> Erol Gelenbe, Imperial College London
>>> Jie Liu, Microsoft Research
>>> 
>>> Tutorials and Workshops Chair:
>>> David Bermbach, TU Berlin
>>> 
>>> Publicity Co-chairs:
>>> Flavia Delicato,Federal University of Rio de Janeiro
>>> Mathias Fischer, University Hamburg
>>> 
>>> Publication Chair
>>> Javid Taheri, Karlstad University
>>> 
>>> Webmaster
>>> Wei Li, The University of Sydney
>>> 
>>> Steering Committee
>>> ------------------
>>> Mung Chiang, Purdue University
>>> Erol Gelenbe, Imperial College London
>>> Christos Kozarakis, Stanford University
>>> Hui Lei, IBM
>>> Chenyang Lu, Washington University in St Louis
>>> Beng Chin Ooi, National University of Singapore
>>> Neeraj Suri, TU Darmstadt
>>> Albert Zomaya, The University of Sydney
>>> 
>>> Program Committee
>>> ------------------
>>> 
>>> Tarek Abdelzaher, UIUC
>>> Anne Benoit, ENS Lyon
>>> David Bermbach, TU Berlin
>>> Bharat Bhargava, Purdue University
>>> Olivier Brun, LAAS/CNRS Laboratory
>>> Jiannong Cao, Hong Kong Polytech
>>> Flavia C. Delicato, UFRJ, Brazil
>>> Xiaotie Deng, Peking University, China
>>> Schahram Dustdar, TU Wien, Germany
>>> Maria Gorlatova, Duke University
>>> Dharanipragada Janakiram, IIT Madras
>>> Wenjing Luo, Virginia Tech
>>> Pedro José Marrón, Universität Duisburg-Essen
>>> Geyong Min, University of Exeter
>>> Suman Nath, Microsoft Research
>>> Vincenzo Piuri, Universita Degli Studi Di Milano
>>> Yong Meng Teo, National University of Singapore
>>> Guoliang Xing, Chinese University of Hong Kong
>>> Yuanyuan Yang, SUNY Stony Brook
>>> Xiaoyun Zhu, Cloudera
>>> 
> 
> 
> -- 
> Best regards,
> Bogdan Dobrelya,
> Irc #bogdando
> 
> _______________________________________________
> Edge-computing mailing list
> Edge-computing at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing



From mike_mp at zzzcomputing.com  Wed Oct 31 18:11:10 2018
From: mike_mp at zzzcomputing.com (Mike Bayer)
Date: Wed, 31 Oct 2018 14:11:10 -0400
Subject: [Edge-computing] [tripleo][FEMDC] IEEE Fog Computing: Call for
 Contributions - Deadline Approaching
In-Reply-To: <53cf2d33-cee7-3f0d-7f28-74b29091a7ef@redhat.com>
References: <CAKe3RKoGZ+ejL-mfhB1dAROkKC=OBbf2b8kizQHJw3GJUzWqcw@mail.gmail.com>
 <53cf2d33-cee7-3f0d-7f28-74b29091a7ef@redhat.com>
Message-ID: <CA+RjkXHZwo4VA-9GdUFnWJUkYkSQkci0TZ3=4NLUNXyqRC7f2Q@mail.gmail.com>

On Wed, Oct 31, 2018 at 10:57 AM Bogdan Dobrelya <bdobreli at redhat.com> wrote:
>
> (cross-posting openstack-dev)
>
> Hello.
> [tl;dr] I'm looking for co-author(s) to come up with "Edge clouds data
> consistency requirements and challenges" a position paper [0] (papers
> submitting deadline is Nov 8).
>
> The problem scope is synchronizing control plane and/or
> deployments-specific data (not necessary limited to OpenStack) across
> remote Edges and central Edge and management site(s). Including the same
> aspects for overclouds and undercloud(s), in terms of TripleO; and other
> deployment tools of your choice.
>
> Another problem is to not go into different solutions for Edge
> deployments management and control planes of edges. And for tenants as
> well, if we think of tenants also doing Edge deployments based on Edge
> Data Replication as a Service, say for Kubernetes/OpenShift on top of
> OpenStack.
>
> So the paper should name the outstanding problems, define data
> consistency requirements and pose possible solutions for synchronization
> and conflicts resolving. Having maximum autonomy cases supported for
> isolated sites, with a capability to eventually catch up its distributed
> state. Like global database [1], or something different perhaps (see
> causal-real-time consistency model [2],[3]), or even using git. And
> probably more than that?.. (looking for ideas)


I can offer detail on whatever aspects of the "shared  / global
database" idea.  The way we're doing it with Galera for now is all
about something simple and modestly effective for the moment, but it
doesn't have any of the hallmarks of a long-term, canonical solution,
because Galera is not well suited towards being present on many
(dozens) of endpoints.     The concept that the StarlingX folks were
talking about, that of independent databases that are synchronized
using some kind of middleware is potentially more scalable, however I
think the best approach would be API-level replication, that is, you
have a bunch of Keystone services and there is a process that is
regularly accessing the APIs of these keystone services and
cross-publishing state amongst all of them.   Clearly the big
challenge with that is how to resolve conflicts, I think the answer
would lie in the fact that the data being replicated would be of
limited scope and potentially consist of mostly or fully
non-overlapping records.

That is, I think "global database" is a cheap way to get what would be
more effective as asynchronous state synchronization between identity
services.

>
> See also the "check" list in-line, which I think also meets the data
> consistency topics well - it would be always nice to have some
> theoretical foundations at hand, when repairing some
> 1000-edges-spread-off and fully broken global database, by hand :)
>
> PS. I must admit I have yet any experience with those IEEE et al
> academic things and looking for someone who has it, to team and
> co-author that positioning paper by. That's as a start, then we can
> think of presenting it and expanding into work items for OpenStack Edge
> WG and future development plans.
>
> [0] http://conferences.computer.org/ICFC/2019/Paper_Submission.html
> [1] https://review.openstack.org/600555
> [2] https://jepsen.io/consistency
> [3] http://www.cs.cornell.edu/lorenzo/papers/cac-tr.pdf
>
> On 10/22/18 3:44 PM, Flavia Delicato wrote:
> > =================================================================================
> > IEEE International Conference on Fog Computing (ICFC 2019)
> > June 24-26, 2019
> > Prague, Czech Republic
> > http://conferences.computer.org/ICFC/2019/
> > Co-located with the IEEE International Conference on Cloud Engineering
> > (IC2E 2019)
> > ==================================================================================
> >
> > Important Dates
> > ---------------
> > Paper registration and abstract: Nov 1st, 2018
> > Full paper submission due: Nov 8th, 2018
> > Notification of paper acceptance: Jan. 20th, 2019
> > Workshop and tutorial proposals due: Nov 11, 2018
> > Notification of proposal acceptance: Nov 18, 2018
> >
> > Call for Contributions
> > ----------------------
> > Fog computing is the extension of cloud computing into its edge and
> > the physical world to meet the data volume and decision velocity
> > requirements in many emerging applications, such as augmented and
> > virtual realities (AR/VR), cyber-physical systems (CPS), intelligent
> > and autonomous systems, and mission-critical systems. The boundary
> > between centralized, powerful computing cloud and massively
> > distributed, Internet connected sensors, actuators, and things is
> > blurred in this new computing paradigm.
> >
> > The ICFC 2019 technical program will feature tutorials, workshops, and
> > research paper sessions. We solicit high-quality contributions in the
> > above categories. Details of submission is available on the conference
> > Web site. Topics of interest include but are not limited to:
> >
> > * System architecture for fog computing
>
> (check)
>
> > * Coordination between cloud, fog, and sensing/actuation endpoints
> > * Connectivity, storage, and computation in the edge
> > * Data processing and management for fog computing
>
> (check)
>
> > * Efficient and embedded AI in the fog
> > * System and network manageability
> > * Middleware and coordination platforms
> > * Power, energy, and resource management
> > * Device and hardware support for fog computing
> > * Programming models, abstractions, and software engineering for fog computing
>
> (check)
>
> > * Security, privacy, and ethics issues related to fog computing
> > * Theoretical foundations and formal methods for fog computing systems
>
> (check)
>
> > * Applications and experiences
> >
> > Organizing Committee
> > --------------------
> > General Chairs:
> > Hui Lei, IBM
> > Albert Zomaya, The University of Sydney
> >
> > PC Co-chairs:
> > Erol Gelenbe, Imperial College London
> > Jie Liu, Microsoft Research
> >
> > Tutorials and Workshops Chair:
> > David Bermbach, TU Berlin
> >
> > Publicity Co-chairs:
> > Flavia Delicato,Federal University of Rio de Janeiro
> > Mathias Fischer, University Hamburg
> >
> > Publication Chair
> > Javid Taheri, Karlstad University
> >
> > Webmaster
> > Wei Li, The University of Sydney
> >
> > Steering Committee
> > ------------------
> > Mung Chiang, Purdue University
> > Erol Gelenbe, Imperial College London
> > Christos Kozarakis, Stanford University
> > Hui Lei, IBM
> > Chenyang Lu, Washington University in St Louis
> > Beng Chin Ooi, National University of Singapore
> > Neeraj Suri, TU Darmstadt
> > Albert Zomaya, The University of Sydney
> >
> > Program Committee
> > ------------------
> >
> > Tarek Abdelzaher, UIUC
> > Anne Benoit, ENS Lyon
> > David Bermbach, TU Berlin
> > Bharat Bhargava, Purdue University
> > Olivier Brun, LAAS/CNRS Laboratory
> > Jiannong Cao, Hong Kong Polytech
> > Flavia C. Delicato, UFRJ, Brazil
> > Xiaotie Deng, Peking University, China
> > Schahram Dustdar, TU Wien, Germany
> > Maria Gorlatova, Duke University
> > Dharanipragada Janakiram, IIT Madras
> > Wenjing Luo, Virginia Tech
> > Pedro José Marrón, Universität Duisburg-Essen
> > Geyong Min, University of Exeter
> > Suman Nath, Microsoft Research
> > Vincenzo Piuri, Universita Degli Studi Di Milano
> > Yong Meng Teo, National University of Singapore
> > Guoliang Xing, Chinese University of Hong Kong
> > Yuanyuan Yang, SUNY Stony Brook
> > Xiaoyun Zhu, Cloudera
> >
>
>
> --
> Best regards,
> Bogdan Dobrelya,
> Irc #bogdando


From ildiko.vancsa at gmail.com  Wed Oct 31 18:20:38 2018
From: ildiko.vancsa at gmail.com (Ildiko Vancsa)
Date: Wed, 31 Oct 2018 19:20:38 +0100
Subject: [Edge-computing] [tripleo][FEMDC] IEEE Fog Computing: Call for
 Contributions - Deadline Approaching
In-Reply-To: <CA+RjkXHZwo4VA-9GdUFnWJUkYkSQkci0TZ3=4NLUNXyqRC7f2Q@mail.gmail.com>
References: <CAKe3RKoGZ+ejL-mfhB1dAROkKC=OBbf2b8kizQHJw3GJUzWqcw@mail.gmail.com>
 <53cf2d33-cee7-3f0d-7f28-74b29091a7ef@redhat.com>
 <CA+RjkXHZwo4VA-9GdUFnWJUkYkSQkci0TZ3=4NLUNXyqRC7f2Q@mail.gmail.com>
Message-ID: <C5CA162A-AB99-4F68-8D25-267A609E86D0@gmail.com>



> On 2018. Oct 31., at 19:11, Mike Bayer <mike_mp at zzzcomputing.com> wrote:
> 
> On Wed, Oct 31, 2018 at 10:57 AM Bogdan Dobrelya <bdobreli at redhat.com> wrote:
>> 
>> (cross-posting openstack-dev)
>> 
>> Hello.
>> [tl;dr] I'm looking for co-author(s) to come up with "Edge clouds data
>> consistency requirements and challenges" a position paper [0] (papers
>> submitting deadline is Nov 8).
>> 
>> The problem scope is synchronizing control plane and/or
>> deployments-specific data (not necessary limited to OpenStack) across
>> remote Edges and central Edge and management site(s). Including the same
>> aspects for overclouds and undercloud(s), in terms of TripleO; and other
>> deployment tools of your choice.
>> 
>> Another problem is to not go into different solutions for Edge
>> deployments management and control planes of edges. And for tenants as
>> well, if we think of tenants also doing Edge deployments based on Edge
>> Data Replication as a Service, say for Kubernetes/OpenShift on top of
>> OpenStack.
>> 
>> So the paper should name the outstanding problems, define data
>> consistency requirements and pose possible solutions for synchronization
>> and conflicts resolving. Having maximum autonomy cases supported for
>> isolated sites, with a capability to eventually catch up its distributed
>> state. Like global database [1], or something different perhaps (see
>> causal-real-time consistency model [2],[3]), or even using git. And
>> probably more than that?.. (looking for ideas)
> 
> 
> I can offer detail on whatever aspects of the "shared  / global
> database" idea.  The way we're doing it with Galera for now is all
> about something simple and modestly effective for the moment, but it
> doesn't have any of the hallmarks of a long-term, canonical solution,
> because Galera is not well suited towards being present on many
> (dozens) of endpoints.     The concept that the StarlingX folks were
> talking about, that of independent databases that are synchronized
> using some kind of middleware is potentially more scalable, however I
> think the best approach would be API-level replication, that is, you
> have a bunch of Keystone services and there is a process that is
> regularly accessing the APIs of these keystone services and
> cross-publishing state amongst all of them.   Clearly the big
> challenge with that is how to resolve conflicts, I think the answer
> would lie in the fact that the data being replicated would be of
> limited scope and potentially consist of mostly or fully
> non-overlapping records.
> 
> That is, I think "global database" is a cheap way to get what would be
> more effective as asynchronous state synchronization between identity
> services.

Recently we’ve been also exploring federation with an IdP (Identity Provider) master: https://wiki.openstack.org/wiki/Keystone_edge_architectures#Identity_Provider_.28IdP.29_Master_with_shadow_users

One of the pros is that it removes the need for synchronization and potentially increases scalability.

Thanks,
Ildikó


> 
>> 
>> See also the "check" list in-line, which I think also meets the data
>> consistency topics well - it would be always nice to have some
>> theoretical foundations at hand, when repairing some
>> 1000-edges-spread-off and fully broken global database, by hand :)
>> 
>> PS. I must admit I have yet any experience with those IEEE et al
>> academic things and looking for someone who has it, to team and
>> co-author that positioning paper by. That's as a start, then we can
>> think of presenting it and expanding into work items for OpenStack Edge
>> WG and future development plans.
>> 
>> [0] http://conferences.computer.org/ICFC/2019/Paper_Submission.html
>> [1] https://review.openstack.org/600555
>> [2] https://jepsen.io/consistency
>> [3] http://www.cs.cornell.edu/lorenzo/papers/cac-tr.pdf
>> 
>> On 10/22/18 3:44 PM, Flavia Delicato wrote:
>>> =================================================================================
>>> IEEE International Conference on Fog Computing (ICFC 2019)
>>> June 24-26, 2019
>>> Prague, Czech Republic
>>> http://conferences.computer.org/ICFC/2019/
>>> Co-located with the IEEE International Conference on Cloud Engineering
>>> (IC2E 2019)
>>> ==================================================================================
>>> 
>>> Important Dates
>>> ---------------
>>> Paper registration and abstract: Nov 1st, 2018
>>> Full paper submission due: Nov 8th, 2018
>>> Notification of paper acceptance: Jan. 20th, 2019
>>> Workshop and tutorial proposals due: Nov 11, 2018
>>> Notification of proposal acceptance: Nov 18, 2018
>>> 
>>> Call for Contributions
>>> ----------------------
>>> Fog computing is the extension of cloud computing into its edge and
>>> the physical world to meet the data volume and decision velocity
>>> requirements in many emerging applications, such as augmented and
>>> virtual realities (AR/VR), cyber-physical systems (CPS), intelligent
>>> and autonomous systems, and mission-critical systems. The boundary
>>> between centralized, powerful computing cloud and massively
>>> distributed, Internet connected sensors, actuators, and things is
>>> blurred in this new computing paradigm.
>>> 
>>> The ICFC 2019 technical program will feature tutorials, workshops, and
>>> research paper sessions. We solicit high-quality contributions in the
>>> above categories. Details of submission is available on the conference
>>> Web site. Topics of interest include but are not limited to:
>>> 
>>> * System architecture for fog computing
>> 
>> (check)
>> 
>>> * Coordination between cloud, fog, and sensing/actuation endpoints
>>> * Connectivity, storage, and computation in the edge
>>> * Data processing and management for fog computing
>> 
>> (check)
>> 
>>> * Efficient and embedded AI in the fog
>>> * System and network manageability
>>> * Middleware and coordination platforms
>>> * Power, energy, and resource management
>>> * Device and hardware support for fog computing
>>> * Programming models, abstractions, and software engineering for fog computing
>> 
>> (check)
>> 
>>> * Security, privacy, and ethics issues related to fog computing
>>> * Theoretical foundations and formal methods for fog computing systems
>> 
>> (check)
>> 
>>> * Applications and experiences
>>> 
>>> Organizing Committee
>>> --------------------
>>> General Chairs:
>>> Hui Lei, IBM
>>> Albert Zomaya, The University of Sydney
>>> 
>>> PC Co-chairs:
>>> Erol Gelenbe, Imperial College London
>>> Jie Liu, Microsoft Research
>>> 
>>> Tutorials and Workshops Chair:
>>> David Bermbach, TU Berlin
>>> 
>>> Publicity Co-chairs:
>>> Flavia Delicato,Federal University of Rio de Janeiro
>>> Mathias Fischer, University Hamburg
>>> 
>>> Publication Chair
>>> Javid Taheri, Karlstad University
>>> 
>>> Webmaster
>>> Wei Li, The University of Sydney
>>> 
>>> Steering Committee
>>> ------------------
>>> Mung Chiang, Purdue University
>>> Erol Gelenbe, Imperial College London
>>> Christos Kozarakis, Stanford University
>>> Hui Lei, IBM
>>> Chenyang Lu, Washington University in St Louis
>>> Beng Chin Ooi, National University of Singapore
>>> Neeraj Suri, TU Darmstadt
>>> Albert Zomaya, The University of Sydney
>>> 
>>> Program Committee
>>> ------------------
>>> 
>>> Tarek Abdelzaher, UIUC
>>> Anne Benoit, ENS Lyon
>>> David Bermbach, TU Berlin
>>> Bharat Bhargava, Purdue University
>>> Olivier Brun, LAAS/CNRS Laboratory
>>> Jiannong Cao, Hong Kong Polytech
>>> Flavia C. Delicato, UFRJ, Brazil
>>> Xiaotie Deng, Peking University, China
>>> Schahram Dustdar, TU Wien, Germany
>>> Maria Gorlatova, Duke University
>>> Dharanipragada Janakiram, IIT Madras
>>> Wenjing Luo, Virginia Tech
>>> Pedro José Marrón, Universität Duisburg-Essen
>>> Geyong Min, University of Exeter
>>> Suman Nath, Microsoft Research
>>> Vincenzo Piuri, Universita Degli Studi Di Milano
>>> Yong Meng Teo, National University of Singapore
>>> Guoliang Xing, Chinese University of Hong Kong
>>> Yuanyuan Yang, SUNY Stony Brook
>>> Xiaoyun Zhu, Cloudera
>>> 
>> 
>> 
>> --
>> Best regards,
>> Bogdan Dobrelya,
>> Irc #bogdando
> 
> _______________________________________________
> Edge-computing mailing list
> Edge-computing at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing