<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:262691722;
mso-list-type:hybrid;
mso-list-template-ids:1634375602 197686228 68026371 68026373 68026369 68026371 68026373 68026369 68026371 68026373;}
@list l0:level1
{mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:23.25pt;
text-indent:-.25in;
mso-ascii-font-family:Calibri;
mso-fareast-font-family:Calibri;
mso-hansi-font-family:Calibri;
mso-bidi-font-family:"Times New Roman";}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:59.25pt;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:95.25pt;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:131.25pt;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:167.25pt;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:203.25pt;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:239.25pt;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:275.25pt;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:311.25pt;
text-indent:-.25in;
font-family:Wingdings;}
@list l1
{mso-list-id:395592441;
mso-list-template-ids:343211168;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">Fyi – could this help? <a href="https://www.linuxfoundation.org/blog/2018/06/edge-computing-just-got-its-rosetta-stone/">
https://www.linuxfoundation.org/blog/2018/06/edge-computing-just-got-its-rosetta-stone/</a>
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><a href="https://imasons.org/">https://imasons.org/</a> starting to host workshops about this as well
<a href="https://imasons.org/events/2018-im-edge-congress/">https://imasons.org/events/2018-im-edge-congress/</a>
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Csatari, Gergely (Nokia - HU/Budapest) <gergely.csatari@nokia.com>
<br>
<b>Sent:</b> Friday, October 19, 2018 1:05 AM<br>
<b>To:</b> OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.openstack.org>; fulton@redhat.com; edge-computing@lists.openstack.org<br>
<b>Cc:</b> openstack-sigs@lists.openstack.org<br>
<b>Subject:</b> [EXTERNAL] Re: [Edge-computing] [openstack-dev] [Openstack-sigs] [FEMDC] [Edge] [tripleo] On the use of terms "Edge" and "Far Edge"<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="HU">Hi, <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="HU"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="HU">I’m adding the ECG mailing list to the discussion.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="HU"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="HU">I think the root of the problem is that there is no single definition of „the edge” (except for [<a href="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=">1</a>]),
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.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="HU"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="HU">The different edge variants are putting different emphasis on these common needs based ont he use case discussed.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="HU"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="HU">To have a more clear understanding of these definitions we could try the following:
<o:p></o:p></span></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoListParagraph" style="margin-left:-12.75pt;mso-list:l0 level1 lfo3">
<span lang="HU">Always add the definition of these to the given context<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:-12.75pt;mso-list:l0 level1 lfo3">
<span lang="HU">Check what other groups are using and adopt to that<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:-12.75pt;mso-list:l0 level1 lfo3">
<span lang="HU">Define our own language and expect everyone else to adopt<o:p></o:p></span></li></ol>
<p class="MsoNormal"><span lang="HU"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="HU">Br, <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="HU">Gerg0<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="HU"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="HU"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="HU"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="HU">[1]: <a href="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=">
https://en.wikipedia.org/wiki/The_Edge</a><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="HU"><o:p> </o:p></span></p>
<p class="MsoNormal"><b>From:</b> Jim Rollenhagen <<a href="mailto:jim@jimrollenhagen.com">jim@jimrollenhagen.com</a>>
<br>
<b>Sent:</b> Thursday, October 18, 2018 11:43 PM<br>
<b>To:</b> <a href="mailto:fulton@redhat.com">fulton@redhat.com</a>; OpenStack Development Mailing List (not for usage questions) <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<b>Cc:</b> <a href="mailto:openstack-sigs@lists.openstack.org">openstack-sigs@lists.openstack.org</a><br>
<b>Subject:</b> Re: [openstack-dev] [Openstack-sigs] [FEMDC] [Edge] [tripleo] On the use of terms "Edge" and "Far Edge"<o:p></o:p></p>
<p class="MsoNormal"><span lang="HU"><o:p> </o:p></span></p>
<div>
<div>
<div>
<p class="MsoNormal"><span lang="HU">On Thu, Oct 18, 2018 at 4:45 PM John Fulton <<a href="mailto:johfulto@redhat.com">johfulto@redhat.com</a>> wrote:<o:p></o:p></span></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<p class="MsoNormal"><span lang="HU">On Thu, Oct 18, 2018 at 11:56 AM Jim Rollenhagen <<a href="mailto:jim@jimrollenhagen.com" target="_blank">jim@jimrollenhagen.com</a>> wrote:<br>
><br>
> On Thu, Oct 18, 2018 at 10:23 AM Dmitry Tantsur <<a href="mailto:dtantsur@redhat.com" target="_blank">dtantsur@redhat.com</a>> wrote:<br>
>><br>
>> Hi all,<br>
>><br>
>> Sorry for chiming in really late in this topic, but I think $subj is worth<br>
>> discussing until we settle harder on the potentially confusing terminology.<br>
>><br>
>> I think the difference between "Edge" and "Far Edge" is too vague to use these<br>
>> terms in practice. Think about the "edge" metaphor itself: something rarely has<br>
>> several layers of edges. A knife has an edge, there are no far edges. I imagine<br>
>> zooming in and seeing more edges at the edge, and then it's quite cool indeed,<br>
>> but is it really a useful metaphor for those who never used a strong microscope? :)<br>
>><br>
>> I think in the trivial sense "Far Edge" is a tautology, and should be avoided.<br>
>> As a weak proof of my words, I already see a lot of smart people confusing these<br>
>> two and actually use Central/Edge where they mean Edge/Far Edge. I suggest we<br>
>> adopt a different terminology, even if it less consistent with typical marketing<br>
>> term around the "Edge" movement.<br>
><br>
><br>
> FWIW, we created rough definitions of "edge" and "far edge" during the edge WG session in Denver.<br>
> 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.<br>
<br>
Perhaps these are the pictures Jim was referring to?<br>
<a href="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=" target="_blank">https://www.dropbox.com/s/255x1cao14taer3/MVP-Architecture_edge-computing_PTG.pptx?dl=0#</a><o:p></o:p></span></p>
</blockquote>
<div>
<p class="MsoNormal"><span lang="HU"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="HU">That's it, thank you!<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="HU"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="HU">// jim<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="HU"> <o:p></o:p></span></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<p class="MsoNormal"><span lang="HU"><br>
<br>
I'm involved in some TripleO work called the split control plane:<br>
<a href="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=" target="_blank">
https://specs.openstack.org/openstack/tripleo-specs/specs/rocky/split-controlplane.html</a><br>
<br>
After the PTG I saw that the split control plane was compatible with<br>
the type of deployment discussed at the edge WG session in Denver and<br>
described the compatibility at:<br>
<a href="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=" target="_blank">
https://etherpad.openstack.org/p/tripleo-edge-working-group-split-control-plane</a><br>
<br>
> See the picture and table here: <a href="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=" target="_blank">
https://wiki.openstack.org/wiki/Edge_Computing_Group/Edge_Reference_Architectures#Overview</a><br>
><br>
>> Now, I don't have really great suggestions. Something that came up in TripleO<br>
>> discussions [1] is Core/Hub/Edge, which I think reflects the idea better.<br>
><br>
><br>
> I'm also fine with these names, as they do describe the concepts well. :)<br>
><br>
> // jim<br>
<br>
I'm fine with these terms too. In split control plane there's a<br>
deployment method for deploying a central site and then deploying<br>
remote sites independently. That deployment method could be used to<br>
deploy Core/Hub/Edge sites too. E.g. deploy the Core using Heat stack<br>
N. Deploy a Hub using stack N+1 and then deploy an Edge using stack<br>
N+2 etc.<br>
<br>
John<br>
<br>
>><br>
>> I'd be very interested to hear your ideas.<br>
>><br>
>> Dmitry<br>
>><br>
>> [1] <a href="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=" target="_blank">
https://etherpad.openstack.org/p/tripleo-edge-mvp</a><br>
>><br>
>> _______________________________________________<br>
>> openstack-sigs mailing list<br>
>> <a href="mailto:openstack-sigs@lists.openstack.org" target="_blank">openstack-sigs@lists.openstack.org</a><br>
>> <a href="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=" target="_blank">
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs</a><br>
><br>
> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="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=" target="_blank">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a href="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=" target="_blank">
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="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=" target="_blank">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="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=" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><o:p></o:p></span></p>
</blockquote>
</div>
</div>
</div>
</body>
</html>