Edge computing PPT slides and it's benifits and drawbacks
- 1. Edge computing The way forward for Eclipse IoT
- 2. Agenda ● Introduction to Edge computing ● Open source on the Edge ● Way forward
- 3. Intro
- 4. Where we are today? ● Everything connected to the core cloud ○ Websites ○ Mobile phones ○ Even IoT devices in most cases
- 5. How we got here? ● Mainframes (centralized) ● Client server (distributed) ● Cloud computing (centralized) ● Edge computing (distributed)
- 6. Edge is everything outside of the core cloud
- 7. Bring compute resources closer to the source
- 8. Key triggers? ● IoT ● Much more data ● Need for real time processing ● Much more compute resources
- 9. Key enablers? ● Cloud native computing ● 5G ● Machine learning ● Inexpensive, power-efficient hardware (SoC modules, etc.) ● ...
- 10. THERE ARE MANY EDGES
- 11. Latency ● React locally on sensor or scheduled events ● Compute offload ○ Schedule resource intensive tasks on the dedicated hardware on the Edge ○ Example AR/VR renderings ● Machine learning ○ Cloud trained models - executed on the Edge ○ Edge specific training (environment and data policies)
- 12. Reliability and HA ● Buffer and batch ○ Store and forward ○ Brokers on Edge nodes ● Caching ○ Local (partial) databases on Edge nodes ○ Sync data with the cloud and other Edge nodes
- 13. Data preprocessing ● Data sensitivity ○ GDPR ● Convert data to general structured messages ○ Normalize data structure ● Data analytics ○ Send only relevant data ○ Combine multiple sources ● Add metadata ○ Location, Identity, Security
- 14. WHAT IS EDGE COMPUTING? Centralize where you can, distribute where you must
- 15. Key applications? ● Large scale IoT and IIoT ● Smart infrastructure ● Gaming industry ● VR/AR ● AI/ML ● Automotive / Autonomous vehicles ● Security and Surveillance ● ….
- 16. Challenges ● Infrastructure ○ How to manage resources (nodes and clusters) on the Edge? ● Control plane ○ How to manage workloads on the Edge? ● Data plane ○ How Edge sites communicate with the cloud and between themselves?
- 17. Challenges ● Resources ○ Limited number of nodes on the Edge ○ No “bursting” to newly provisioned capacity like a public cloud or large datacenter ○ Workloads typically have a wide range of priorities ○ Need more emphasis on prioritization, triage ● Network ○ Network capacity can be limited, and variable ○ Like resources, different workloads can have different network policies/priorities
- 18. Security ● Unattended operation ● Physical security ● Purity of images ● Secure delivery of secrets ● Unauthorized microservices ● Controlled access to resources ● Guaranteed remote shutdown
- 19. Microservices ● Deployment ● Resources ○ Pod priorities ● Communication ○ VPN ○ VAN ● Security ○ Matching microservices to edge hardware ○ Unauthorized outbound
- 20. Open source for the Edge
- 21. Open source for the Edge Eclipse ioFog
- 22. Where does it fit?
- 23. What does it do… on the lowest level?
- 24. What does it do… in the bigger picture?
- 25. What does it do… to development lifecycle?
- 26. Introducing the Edge Compute Network (ECN)
- 27. Edge networking ● Hybrid cloud, microservice architecture, agile integration, etc. ○ Not client/server ○ Services/processes want to be deployable and addressable everywhere (north/south/east/west) ● Edge computing - Lots of private subnetworks Private Subnet 10.1.0.200 10.1.0.5 Private Subnet 10.1.0.5 10.1.0.8 Public Network nat nat
- 28. Application Layer Addressing 28 10.1.2.5/24 10.1.2.10/24 10.2.2.8/24 54.193.17.106/16 C S S S S service service service service service S service
- 29. Application Layer Addressing 29 10.1.2.5/24 10.1.2.10/24 10.2.2.8/24 54.193.17.106/16 C S S S S service service service service service S service
- 30. Implications of Application Addressing ● Security ○ Access control for addresses - at the service/process/business resolution ○ Locked-down network membership - Mutual TLS for inter-site connections ○ Cross-cluster applications not exposed via Kube networking ■ Public exposure limited to ingress ○ Trusted and untrusted edges ● Management ○ Metrics collected at business resolution
- 31. Skupper.io ● Operational Ease ○ Easy to deploy in a multi-cluster network ○ No advanced networking (SDN, VPNs, Tunnels, Firewall rules, etc.) ○ No need for elevated or admin privileges ○ No problem with overlapping CIDR subnets or mixes of IPv4 and IPv6 ○ No single point of failure - use redundant topology ● Not just for messaging ○ Proxy maps HTTP, TCP, UDP, etc. to AMQP ● http://skupper.io ○ Examples, demo-videos, etc. ○ New, emerging project
- 32. Way forward
- 34. Way forward ● Cloud is not obsolete ● Cloud IoT platforms still needed ○ Hono ○ Ditto ● Work on distributed Edge deployments for IoT services
- 35. Eclipse Hono AMQP Network Business services Protocol adapter Protocol adapter Device Device Device Device Device
- 36. Eclipse Hono AMQP Network Business services Protocol adapter Device Device Device Device Device AMQP Network AMQP Network Business services Business services Protocol adapter
- 37. Eclipse Ditto
- 38. Next generation"gateways" ● Move to cloud native development of gateways services ● More compute resources ○ More caching ○ More analytics ○ More ML ● CI/CD