Objectives

1. Reduce friction to deployment of LF Edge Blueprints
2. Provide a centralized location for all deployable Blueprints

Concept

• Provide (potential hierarchy of) recipes for deployment of blueprints
  • For Kubernetes based projects (like Akraino) this could be a set of Helm charts
  • For other container based projects (which don't necessarily have K8S) this could be docker-compose
• Have a web-page which consolidates these along with simple instructions and potential parameters

Examples

• artifacthub.io : maintains a catalog of public helm charts and has a concept of organizations (so we could host under an LFEdge organization there)
  • Organizational View Example: https://artifacthub.io/packages/search?org=smarter&sort=relevance&page=1
  • Project View Example: https://artifacthub.io/packages/helm/device-manager/smarter-device-manager
  • We could potentially augment descriptions with badges (Cassini Ready, etc.)
• hub.balena.io: has a similar structure to the above, but actually couples a container recipe with a platform to provide a burnable sdcard
• rancher provides a git repository of recipes: https://github.com/rancher/community-catalog which are used by their platform to provide catalog based installation
• portal.sagecontinuum.org maintains a catalog of edge deployable applications for their smarter-cities project

Requirements

• For helm appropriate projects (those that use kubernetes as a base layer)
  • helm-ifying (as necessary) blueprint components
  • umbrella helm which deploys those components
  • role-designation methodology for multi-node blueprints (or even to specify cloud-side versus edge-side)
  • host on a catalog platform
• For other projects
  • TBD - options include using things like portainer.io or just docker-compose, but unaware of a artifacthub.io equivalent for those so maybe just github/gitlab?

Proposal

• Prototype requirements with a single blueprint (strawman: Akraino smarter cities blueprint) and then broaden to all Akraino blueprints to evaluate