Open Horizon Project Proposal By Joe Pearson IBM

Open Horizon Project Proposal By: Joe Pearson, IBM

Project Description Open Horizon is a platform designed to autonomously and securely manage the service software lifecycle of global or local fleets of heterogeneous edge compute nodes in various connected states at scale. It interoperates with existing orchestration tools and conventions. It can be considered as a single component of a complete Cloud-to-Edge workload management solution; covering both services and related metadata, including machine learning assets.

A Thousand Words

Design Philosophy and Considerations › Autonomy – With large device fleets, conventional software management techniques do not scale. Open Horizon provides a policy-driven mechanism for specifying actors and constraints, and monitors conditions continually for changes. › Security – The goal is to minimize attack surfaces. Each OH Agent has authority only for its own device and each acts autonomously. All components have tightly restricted scopes of authority, and Hub Services have no authority over the Agents. Components communicate securely and indirectly. Only signed and verified workloads are run. › Connectivity – Edge compute nodes may not always be connected to the Internet. Agents allow for partially- and completely-disconnected operations.

History, Trivia, Background, and Useless Facts › IBM began Horizon development mid 2015, demo’d at Io. T World Forum on 12/2015 › Scaled in the lab to 10 K edge compute devices with single service definition and policy › Previously named Project Mountain, then Blue Horizon, now Open Horizon › › IBM’s mature edge computing solution -- IBM Edge Application Manager 4. 0 -- is built with Open Horizon Created by IBM’s Applied Sciences boffins, half of which are still on the current development team (five years later) › Agent will run on a Raspberry Pi 2 B (arm 32 v 6) with only 512 MB RAM, but why would you?

Defining the Edge From: https: //www. ibm. com/cloud/architectures/edge-computing/overview

Edge Target and Specifications › › › Targeting the Edge Gateway/Server and Device tiers of Edge Computing Works with Debian variants and OSX, on x 86_64, and arm 32 v 6 through arm 64 v 8. Running the Agent only requires a single core. Both the Agent and Docker together consume around 100 MB RAM, leaving excess memory for workloads on an edge node with 512 MB RAM. › The Agent and Docker combined use about 400 MB storage on disk. › Written in Golang and Scala Attributes Agent Hub Services Supported Architectures x 86_64, arm 32 v 6 arm 64 v 8 Minimum Hardware Requirements 1+ v. CPU, 512 MB RAM, 2 GB storage 1+ v. CPU, 4 GB RAM, 20 GB storage Applications Debian-based OS or OSX, Docker engine or Kubernetes Workload Type Containers, Metadata Containers Hardware onboarding SDO or possibly Project EVE Sensor/Device connectivity Edge. X Foundry or Fledge

Mission Alignment with LF Edge "LF Edge provides a neutral structure for building a diverse open source community capable of driving better, more secure development at the edge. It also unifies an aligned vision for the diverse and complex edge projects being built today. " from the LF Edge FAQ. In order to further the mission of LF Edge, Open Horizon's goals include: › › To enlist partners as stakeholders › To establish our approaches as de facto standards and blueprints and speed industry adoption › To create an ecosystem of components and services from LF-contributed code to enable enterprise-ready solutions › To provide a migration path from individual projects to complete enterprise-ready solutions To build an active, thriving community of developer contributors

High Level Synergy with LF Edge Projects Where we compliment, overlap, and harmonize

Collaborating with LF Edge Projects › Open Horizon works with Edge. X Foundry, and potentially Fledge, to deliver and manage their solution and to synchronize any needed ML assets with their origin. › Open Horizon is collaborating with Home Edge to synchronize ML assets from the cloud to the home gateway. › Open Horizon is talking to Project EVE about using them solution as a device management solution and to bootstrap the Open Horizon Agent. Open Horizon is in discussions with several Akraino Blueprint Family owners on contributing to their blueprints as a portion of their solutions in the areas of workload management on edge devices and delivery of assets in an ML deployment pipeline. Open Horizon may overlap with Baetyl when it comes to containerized application management on the Far Edge (Edge Devices). The fundamental differences are in scope (OH is not a complete solution Cloud-to. Edge), and in implementation (OH has autonomous disconnected Agents, OH components have narrow scopes of authority, and OH does not provide a data plane). OH would like to see if our APIs are (or could be made to be) compatible.

TAC Sponsors › Jim St. Leger, Intel › Sukhdev Kapur, Juniper › Frank Zdarsky, Red Hat › Joe Pearson, IBM › and … the Edge. X Foundry project TSC endorses this proposal

Thank You

Contact Us The Linux Foundation General Inquiries info@linuxfoundation. org 1 Letterman Drive Membership Building D, Suite D 4700 membership@linuxfoundation. org San Francisco CA 94129 Corporate Training Phone/Fax: +1 415 7239709 training@linuxfoundation. org www. linuxfoundation. org Event Sponsorship sponsorships@linuxfoundation. org

Legal The Linux Foundation, The Linux Foundation logos, and other marks that may be used herein are owned by The Linux Foundation or its affiliated entities, and are subject to The Linux Foundation’s Trademark Usage Policy at https: //www. linuxfoundation. org/trademarkusage, as may be modified from time to time. Linux is a registered trademark of Linus Torvalds. Please see the Linux Mark Institute’s trademark usage page at https: //lmi. linuxfoundation. org for details regarding use of this trademark. Some marks that may be used herein are owned by projects operating as separately incorporated entities managed by The Linux Foundation, and have their own trademarks, policies and usage guidelines. TWITTER, TWEET, RETWEET and the Twitter logo are trademarks of Twitter, Inc. or its affiliates. Facebook and the “f” logo are trademarks of Facebook or its affiliates. Linked. In, the Linked. In logo, the IN logo and In. Mail are registered trademarks or trademarks of Linked. In Corporation and its affiliates in the United States and/or other countries. You. Tube and the You. Tube icon are trademarks of You. Tube or its affiliates. All other trademarks are the property of their respective owners. Use of such marks herein does not represent affiliation with or authorization, sponsorship or approval by such owners unless otherwise expressly specified. The Linux Foundation is subject to other policies, including without limitation its Privacy Policy at https: //www. linuxfoundation. org/privacy and its Antitrust Policy at https: //www. linuxfoundation. org/antitrust-policy. each as may be modified from time to time. More information about The Linux Foundation’s policies is available at https: //www. linuxfoundation. org. Please email legal@linuxfoundation. org with any questions about The Linux Foundation’s policies or the notices set forth on this slide.