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@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@vapor.io> wrote:
>
> Teresa Peluso <tpeluso@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@lists.openstack.org> wrote:
> Send Edge-computing mailing list submissions to
>         edge-computing@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@lists.openstack.org
>
> You can reach the person managing the list at
>         edge-computing-owner@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@equinix.com>
> To: "Csatari, Gergely (Nokia - HU/Budapest)"
>         <gergely.csatari@nokia.com>, "OpenStack Development Mailing List (not
>         for usage questions)" <openstack-dev@lists.openstack.org>,
>         "fulton@redhat.com" <fulton@redhat.com>,
>         "edge-computing@lists.openstack.org"
>         <edge-computing@lists.openstack.org>
> Cc: "openstack-sigs@lists.openstack.org"
>         <openstack-sigs@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@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@nokia.com>
> Sent: Friday, October 19, 2018 1:05 AM
> To: OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.openstack.org>; fulton@redhat.com; edge-computing@lists.openstack.org
> Cc: openstack-sigs@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@jimrollenhagen.com<mailto:jim@jimrollenhagen.com>>
> Sent: Thursday, October 18, 2018 11:43 PM
> To: fulton@redhat.com<mailto:fulton@redhat.com>; OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
> Cc: openstack-sigs@lists.openstack.org<mailto:openstack-sigs@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@redhat.com<mailto:johfulto@redhat.com>> wrote:
> On Thu, Oct 18, 2018 at 11:56 AM Jim Rollenhagen <jim@jimrollenhagen.com<mailto:jim@jimrollenhagen.com>> wrote:
> >
> > On Thu, Oct 18, 2018 at 10:23 AM Dmitry Tantsur <dtantsur@redhat.com<mailto:dtantsur@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@lists.openstack.org<mailto:openstack-sigs@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@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@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@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@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing