[Edge-computing] Edge Node locator

Christopher Price christopher.price at est.tech
Wed Feb 13 15:01:29 UTC 2019


Yes it’s been under investigation/development for a long long time. 😊
Supported in routers as of today, however you need an application layer that takes advantage of it and well let’s be honest IP prevails in a centralized architecture.  We seem as an industry to be moving toward a scenario where these types of approaches may begin to become viable, I’m not sure if it would really take off as anything other than an overlay but as SDN approaches the edge...
/ Chris

From: "Addepalli, Srinivasa R" <srinivasa.r.addepalli at intel.com>
Date: Wednesday, 13 February 2019 at 15:54
To: Christopher Price <christopher.price at est.tech>, bharath thiruveedula <bharath_ves at hotmail.com>, "edge-computing at lists.openstack.org" <edge-computing at lists.openstack.org>
Subject: RE: [Edge-computing] Edge Node locator

It sounds like “Named Data Networking”.   If so, I agree, this is one of the novel approaches to name content object as the endpoint instead of IP address.  I think it is still in research phase and not sure whether it is adopted by endpoints and network infrastructure yet.  Any deployments or plans you are aware of?

Srini


From: Christopher Price [mailto:christopher.price at est.tech]
Sent: Wednesday, February 13, 2019 6:20 AM
To: bharath thiruveedula <bharath_ves at hotmail.com>; edge-computing at lists.openstack.org
Subject: Re: [Edge-computing] Edge Node locator

Sorry I was “auto-corrected”:  CBN (content based networking), not CDN.

From: Christopher Price <christopher.price at est.tech<mailto:christopher.price at est.tech>>
Date: Wednesday, 13 February 2019 at 15:17
To: bharath thiruveedula <bharath_ves at hotmail.com<mailto:bharath_ves at hotmail.com>>, "edge-computing at lists.openstack.org<mailto:edge-computing at lists.openstack.org>" <edge-computing at lists.openstack.org<mailto:edge-computing at lists.openstack.org>>
Subject: Re: [Edge-computing] Edge Node locator

Bharath,

A left field thought which I find quite interesting is to run your application on a CDN overlay.
This can be constrained to the application layer and run over IP which reduces the need to try and weld this type of function to the infrastructure layer or expose too much service awareness through an extended mesh.  (security security)  Moves the problem to a defined space and keeps your infrastructure and app workloads simple and focused on what they should be doing.

Millions of ways to skin that poor little cat though, imagination Vs cost…

/ Chris

From: bharath thiruveedula <bharath_ves at hotmail.com<mailto:bharath_ves at hotmail.com>>
Date: Tuesday, 12 February 2019 at 18:53
To: "edge-computing at lists.openstack.org<mailto:edge-computing at lists.openstack.org>" <edge-computing at lists.openstack.org<mailto:edge-computing at lists.openstack.org>>
Subject: [Edge-computing] Edge Node locator

Hi ,

Disclaimer: I am not sure the question following is in the scope of this forum.

I am trying to understand the Edge Architecture from UE point of view. How an app in UE can detect what the nearest edge it has to contact and how does it know whether the app is provisioned in that edge or not?

Can you please share some pointers from this perspective?

Best Regards
Bharath T
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/edge-computing/attachments/20190213/1a96aa70/attachment.html>


More information about the Edge-computing mailing list