<div dir="ltr"><div class="gmail_quote"><div dir="ltr">On Thu, Oct 18, 2018 at 4:45 PM John Fulton <<a href="mailto:johfulto@redhat.com">johfulto@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">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#" rel="noreferrer" target="_blank">https://www.dropbox.com/s/255x1cao14taer3/MVP-Architecture_edge-computing_PTG.pptx?dl=0#</a></blockquote><div><br></div><div>That's it, thank you!</div><div><br></div><div>// jim</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><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" rel="noreferrer" 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" rel="noreferrer" 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" rel="noreferrer" 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" rel="noreferrer" 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" rel="noreferrer" 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" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" 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" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div></div>