Page History

...

1. IBM booth demos:
   1. Workload runtime security (OH + KubeArmor + ???)
   2. Application-centric connectivity (OH + Skupper + ???)
   3. ML deployment automation (OH + TinyLlama? or Yolo v8 or v9?)
2. LF Edge booth demos:
   
   1. Handsfree device onboarding (OH + FDO + LF Edge Sandbox + Project EVE)
   2. Realtime workload metrics (OH + EdgeLake + Grafana + optionally KubeArmor)
   3. Dynamic runtime secrets binding (OpenBao

...

1. 1. with Open Horizon

...

1. 1. )

...

KubeArmor is the gold standard for workload runtime security

Value prop: Open Horizon works with KubeArmor on bare Linux and Kubernetes clusters to enforce security at the host and workload levelsSecure and harden your edge solutions using Security-by-default principles and active mitigation measures from Days 0 - N.

Owner: Prashant Mishra and Sanjeev Gupta 

...

1. How do we stop, not just detect.  Not post-detect strategies but active mitigation.  Ex. application without hardening has these misconfigurations/access.  KubeArmor will sandbox the application behavior to only allow the specified behavior and nothing else.
2. Multiple applications on a device.  If one is compromised, the blast radius could impact other running containers.  How do you isolate the workloads to limit the blast radius.
3. Specific use cases for Vault
4. ORRA Kamakura demo showing addition of KubeArmor to the running application to enforce network micro-segmentation

Provide application-centric and -directed connectivity

Value-prop: Quickly connect deployed applications with remote resources in any location.  Align distributed application connectivity with the applications themselves so both can be deployed and managed together by the same team.

Owner: Jeff Lu  and Sanjeev Gupta?

Todo: Create Skupper service and show how to connect a distributed application to its remote services.  Linux host to start, then Kubernetes example?

Adopters: IBM Hybrid Cloud Mesh with Red Hat Service Interconnect

Dynamic ML association/placement/delivery/bi-directional sync

Value prop: Associate ML models with the applications that use them while allowing independent delivery and lifecycle management of each.  Separate teams typically develop and maintain ML assets and their consuming applications.  Why force the assets and applications to be deployed together by the same pipelines?

Owner: Jeff Lu 

Todo: Determine which models/framework to show, how to update?

Adopters:

Zero-touch device onboarding with FDO is a reality

...

1. Create a secret in the OpenBao secrets manager named hw-secret-name
2. Register an edge node with the helloSecretWorld example service
3. Show the "<your-node-id> says: Hello <secret-value>!" output of the service in a separate terminal updating every 5 seconds ("<secret-value>" here is the contents of the hw-secret-name secret)
4. Update the hw-secret-name secret with a new value "<new-secret-value>"
5. A few seconds later in the still open terminal window being updated live with the service output, observe the output change to "<your-node-id> says: Hello <new-secret-value>!"

Demonstrate OH managing ML placement/delivery/bi-directional sync

Value prop: Models are trained in the cloud or elsewhere, but don't have the ability to deliver securely to edge devices.  OH can be that last mile delivery solution.

Owner: Jeff Lu 

Todo: Determine which models/framework to show, how to update?

Adopters:

Provide application-centric and -directed connectivity

Value-prop: Align distributed application connectivity with the applications themselves so both can be deployed and managed together by the same team.

Owner: Jeff Lu  and Sanjeev Gupta?

Todo: Create Skupper service and show how to connect a distributed application to its remote services.  Linux host to start, then Kubernetes example?

...