[Edge-computing] Edge Node locator

bharath thiruveedula bharath_ves at hotmail.com
Wed Feb 13 14:20:39 UTC 2019 

Hi Sebastian,

Yeah I was actually looking for architecture point of view rather than actual solutions.

>> From a system’s perspective the UE is/will eventually become part of the networking system

Exactly, I was looking for such discussions in edge computing forum. In the current demos of MEC, are we considering the UE with such functionalities?

>> The shortcomings of DNS and how services are tight to an IP address which immediately binds you physically to an instance where the service is instantiated is well understood as a problem. Several solutions have various answers to that (floating IPs,  DNS black-boxes as VNFs, triangular routing, tunneling, etc)

This is interesting. How can the IP be resolved if the UE is moving and the DNS has to be refreshed if the edge is changed that serving the application? I am not sure, if it is already discussed.

Best Regards
Bharath T

________________________________
From: Sebastian Robitzsch <Sebastian.Robitzsch at InterDigital.com>
Sent: Wednesday, February 13, 2019 4:36 AM
To: Addepalli, Srinivasa R; Rob Hirschfeld
Cc: bharath thiruveedula; edge-computing at lists.openstack.org; ramkik at vmware.com
Subject: RE: [Edge-computing] Edge Node locator


Dear all,



Let me chime in at this point and go back to the very interesting question Bharat asked:  “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?”



He asked about architectural viewpoints and not solutions which were mainly presented as an answer so far. From a system’s perspective the UE is/will eventually become part of the networking system with the edge expanding to the terminal (leaving it up to your interpretation what a terminal could be – ranging from traditional handsets, to all-in-one devices up to constraint devices that have only particular functionalities (such as displaying content, processing them or storing them)).

In all UE/terminal-centric views the only task an endpoint must solve is how it can communicate with the system (point of attachment) in order to become part of it. Next is to announce/negotiate the resources so that its cloud resources (CPU, RAM, disk, networking) can be orchestrated correctly by the infrastructure’s orchestrator.

If the endpoint is seeking other resources inside/outside the system’s domain (such as an FQDN in the modern world) a resource pool is queried (traditionally DNS) which results in a communication between the initializing endpoint and the serving endpoint – across domains.



An edge compute architecture (from OpenStack’s aka Open Infrastructure’s point of view) allows the orchestration of infrastructure resources which might include the terminal. But it should leave it to the system / platform deployed on top of the infrastructure to determine the where a service initializer on the UE (application) is receiving its information from; this could be a traditional IP stack with DNS (not very dynamic and scalable in a modern edge environment) or a more edge-focused solution which does not necessarily follow the traditional way the internet works (see ETSI MEC PoC’s).



Bottom line, the app in the UE does not “detect” the nearest edge. In an ideal world the routing inside the network system is fully decoupled from the information two or more endpoints would like to exchange (e.g. your app on the UE and a service in some (edge) instance). The shortcomings of DNS and how services are tight to an IP address which immediately binds you physically to an instance where the service is instantiated is well understood as a problem. Several solutions have various answers to that (floating IPs, customised DNS black-boxes as VNFs, triangular routing, tunneling, etc). But one thing I’d like to stress: the UE must not detect the nearest edge itself. There’s approaches like service function chaining and name-based routing where any application simply communicates its intent what service to access to the platform deployed on top of the infrastructure. How the actual request makes it to the service instance is decoupled from the intend of the application on the UE. And this is what an edge (infrastructure) architecture should support and outline in its specification.





Best Regards,

Sebastian



From: Addepalli, Srinivasa R <srinivasa.r.addepalli at intel.com>
Sent: 12 February 2019 21:00
To: Rob Hirschfeld <rob at rackn.com>
Cc: bharath thiruveedula <bharath_ves at hotmail.com>; edge-computing at lists.openstack.org; ramkik at vmware.com
Subject: Re: [Edge-computing] Edge Node locator



Yes. It is confusing due to common term ‘EdgeX’ in both places.



JFYI



EdgeXFoundry : Is IOT platform.

MobileEdgeX, EVE and ONAP:  Mainly to orchestrate and automate applications/VNFs on several edge locations.



There is  confusion with Airship too.  Airship is for bare-metal provisioning with respect to deploying host operating system and related utilities/processes to make edge/DC ready.



Thanks

Srini





From: Rob Hirschfeld [mailto:rob at rackn.com]
Sent: Tuesday, February 12, 2019 12:51 PM
To: Addepalli, Srinivasa R <srinivasa.r.addepalli at intel.com<mailto:srinivasa.r.addepalli at intel.com>>
Cc: 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>; ramkik at vmware.com<mailto:ramkik at vmware.com>
Subject: Re: [Edge-computing] Edge Node locator



Thank you for clarifying.  I suspect I'm not the only person getting confused about that.



[https://lh6.googleusercontent.com/ySrnpZRlg0FK6BwnZw-GLxA8PuamwCARuiMJ_VjL4muhF_ifki9TWNgZvtavVZKSv_2mEBFYbr6BEeeb6BkBiJ0l27qL7yCHC7hsPvE1ZbTkyY30JPVO_uKHlH2w3yv4OQI-WUyg]<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Ft.sidekickopen10.com%2Fs2t%2Fc%2F5%2Ff18dQhb0S7lC8dDMPbW2n0x6l2B9nMJW7t5XZs3M2bjgW64zKpj3LyR22W1qMCsg56dVpDf9jJGjx02%3Ft%3Dhttps%253A%252F%252Fwww.rackn.com%252F%26si%3D5660451956457472%26pi%3De084781c-677c-403c-d2c8-81edf582fdae&data=02%7C01%7Csebastian.robitzsch%40interdigital.com%7Ce967d11039a349c2deb208d6912dde14%7Ce351b779f6d54e50856880e922d180ae%7C0%7C0%7C636856023517650301&sdata=0oOno9RQ%2FpJhCh%2BB0IVu3VIX9DyVUSET6rZoCpGhFRw%3D&reserved=0>


Rob Hirschfeld

Co-Founder and Chief Executive Officer, RackN

(512) 773-7522


[https://lh6.googleusercontent.com/HlA5qvRA4ba1F5C0kOubBXP0qF4DlXlIdKyQJG_sWo2FKAIZbsicvGS-8F9WbXQ2ZNLySHg-bb1W3V2BxSR1Z8vpd7mOH798iSxdmvo8q75DqVkq29Cj7Y5VvqiB9sViJwHqSSNY]<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Ft.sidekickopen10.com%2Fs2t%2Fc%2F5%2Ff18dQhb0S7lC8dDMPbW2n0x6l2B9nMJW7t5XZs3M2bjgW64zKpj3LyR22W1qMCsg56dVpDf9jJGjx02%3Ft%3Dhttps%253A%252F%252Ftwitter.com%252Fzehicle%253Flang%253Den%26si%3D5660451956457472%26pi%3De084781c-677c-403c-d2c8-81edf582fdae&data=02%7C01%7Csebastian.robitzsch%40interdigital.com%7Ce967d11039a349c2deb208d6912dde14%7Ce351b779f6d54e50856880e922d180ae%7C0%7C0%7C636856023517650301&sdata=ltzE1WmpjGHJaq0dSxxzZKb3N31oQ9l28Y11iKon8QI%3D&reserved=0>[https://lh6.googleusercontent.com/fQXQPBYLS6cl3yZhjq2LhPlzqrCc5WLLZcdFqxsSQjis3xb34H5hoaZkcAYpHIgKEksvW6qhrZYFCscWitnWmR3yTJ34uLfTX0ozwOl_JwJn9c1VFpTtq3xj15SNw66zt8X3-rHc]<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Ft.sidekickopen10.com%2Fs2t%2Fc%2F5%2Ff18dQhb0S7lC8dDMPbW2n0x6l2B9nMJW7t5XZs3M2bjgW64zKpj3LyR22W1qMCsg56dVpDf9jJGjx02%3Ft%3Dhttps%253A%252F%252Fwww.linkedin.com%252Fin%252Frhirschfeld%252F%26si%3D5660451956457472%26pi%3De084781c-677c-403c-d2c8-81edf582fdae&data=02%7C01%7Csebastian.robitzsch%40interdigital.com%7Ce967d11039a349c2deb208d6912dde14%7Ce351b779f6d54e50856880e922d180ae%7C0%7C0%7C636856023517660306&sdata=GRoJ4LWkUQ%2B7H898HX%2FVz%2Bmlj5FZDiC5fGSPaMwRhBU%3D&reserved=0>








On Tue, Feb 12, 2019 at 2:47 PM Addepalli, Srinivasa R <srinivasa.r.addepalli at intel.com<mailto:srinivasa.r.addepalli at intel.com>> wrote:

MobileEdgeX is not yet part of LFE.  It may that you might be referring to EdgeXFoundry.  MobileEdgX and EdgeXFoundry are two different projects addressing two different scenarios.



Thanks

Srini





From: Rob Hirschfeld [mailto:rob at rackn.com<mailto:rob at rackn.com>]
Sent: Tuesday, February 12, 2019 12:23 PM
To: Addepalli, Srinivasa R <srinivasa.r.addepalli at intel.com<mailto:srinivasa.r.addepalli at intel.com>>
Cc: 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>; ramkik at vmware.com<mailto:ramkik at vmware.com>
Subject: Re: [Edge-computing] Edge Node locator



This needs to be corrected ASAP since they are both spotlighted as LF Edge projects > "MobileEdgeX and LFE EVE projects (These two are not yet open sourced)."




Rob Hirschfeld









On Tue, Feb 12, 2019 at 12:12 PM Addepalli, Srinivasa R <srinivasa.r.addepalli at intel.com<mailto:srinivasa.r.addepalli at intel.com>> wrote:

Hi Bharath,



JFYI

This work is going on in ONAP (OOF project and Edge automation project).



Other possible projects are  MobileEdgeX and LFE EVE projects (These two are not yet open sourced).



ONAP OOF project intention is to figure out the best edge location for a given workload based on following criteria:



-        Latency/Distance with respect to UEs.

-        Availability of right hardware capabilities required for the workload.

-        Cost

-        Affinity and Anti-affinity rules

-        Etc…



Once ONAP OOF chooses the edge location to  place the workload, then ONAP (via Multi-Cloud project) will place the workload by calling Openstack API or K8S API etc…



You may want to check out ONAP project.



Thanks

Srini









Thanks

Srini





From: bharath thiruveedula [mailto:bharath_ves at hotmail.com<mailto:bharath_ves at hotmail.com>]
Sent: Tuesday, February 12, 2019 9:52 AM
To: 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

_______________________________________________
Edge-computing mailing list
Edge-computing at lists.openstack.org<mailto:Edge-computing at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.openstack.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fedge-computing&data=02%7C01%7Csebastian.robitzsch%40interdigital.com%7Ce967d11039a349c2deb208d6912dde14%7Ce351b779f6d54e50856880e922d180ae%7C0%7C0%7C636856023517670316&sdata=n9uveD%2BZidGfWr0SUDBN2ZyR1d63Cils1iqftUbO1os%3D&reserved=0>

[Banner]


[Banner] [Banner]
This e-mail is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential and/or otherwise protected from disclosure to anyone other than its intended recipient. Unintended transmission shall not constitute waiver of any privilege or confidentiality obligation. If you received this communication in error, please do not review, copy or distribute it, notify me immediately by email, and delete the original message and any attachments. Unless expressly stated in this e-mail, nothing in this message or any attachment should be construed as a digital or electronic signature.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/edge-computing/attachments/20190213/dc139c44/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 332 bytes
Desc: image001.jpg
URL: <http://lists.openstack.org/pipermail/edge-computing/attachments/20190213/dc139c44/attachment-0001.jpg>

More information about the Edge-computing mailing list