<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:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" 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:0cm;
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:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
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:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
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:-18.0pt;
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:-18.0pt;
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:-18.0pt;
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:-18.0pt;
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:-18.0pt;
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:-18.0pt;
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:-18.0pt;
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:-18.0pt;
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:-18.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></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="HU" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Hi, <o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">I’m adding the ECG mailing list to the discussion.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">I think the root of the problem is that there is no single definition of „the edge” (except for [<a href="https://en.wikipedia.org/wiki/The_Edge">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 style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">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 style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">To have a more clear understanding of these definitions we could try the following:
<o:p></o:p></span></p>
<ol style="margin-top:0cm" start="1" type="1">
<li class="MsoListParagraph" style="margin-left:-12.75pt;mso-list:l0 level1 lfo1">
<span style="mso-fareast-language:EN-US">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 lfo1">
<span style="mso-fareast-language:EN-US">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 lfo1">
<span style="mso-fareast-language:EN-US">Define our own language and expect everyone else to adopt<o:p></o:p></span></li></ol>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Br, <o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Gerg0<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">[1]: https://en.wikipedia.org/wiki/The_Edge<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> Jim Rollenhagen <jim@jimrollenhagen.com>
<br>
<b>Sent:</b> Thursday, October 18, 2018 11:43 PM<br>
<b>To:</b> fulton@redhat.com; OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.openstack.org><br>
<b>Cc:</b> openstack-sigs@lists.openstack.org<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></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<div>
<p class="MsoNormal">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></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<p class="MsoNormal">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://www.dropbox.com/s/255x1cao14taer3/MVP-Architecture_edge-computing_PTG.pptx?dl=0" target="_blank">https://www.dropbox.com/s/255x1cao14taer3/MVP-Architecture_edge-computing_PTG.pptx?dl=0#</a><o:p></o:p></p>
</blockquote>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">That's it, thank you!<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">// jim<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<p class="MsoNormal"><br>
<br>
I'm involved in some TripleO work called the split control plane:<br>
<a href="https://specs.openstack.org/openstack/tripleo-specs/specs/rocky/split-controlplane.html" 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://etherpad.openstack.org/p/tripleo-edge-working-group-split-control-plane" 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://wiki.openstack.org/wiki/Edge_Computing_Group/Edge_Reference_Architectures#Overview" 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://etherpad.openstack.org/p/tripleo-edge-mvp" 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="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs" 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="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" 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="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><o:p></o:p></p>
</blockquote>
</div>
</div>
</div>
</body>
</html>