/
LF Edge Catalog

LF Edge Catalog

Objectives

  1. Reduce friction to deployment of LF Edge Templates

  2. Provide a centralized location for all deployable Templates

Definition

  • Template = software + configuration

Concept

  • Provide (potential hierarchy of) recipes for deployment of templates

    • For Kubernetes based projects (like Akraino) this could be a set of Helm charts or k8s manifests

    • For other container based projects (which don't necessarily have K8S) this could be docker-compose

    • For bare-metal deployments, we are open to suggestions on potential solutions

  • Have a web-page (per template) which consolidates these along with simple instructions and potential parameters

Examples

Requirements

  • For helm appropriate projects (those that use kubernetes as a base layer)

    • helm-ifying (as necessary) template 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?

Current Status





Related content

Existing Project Taxonomy
Existing Project Taxonomy
More like this
LF Edge Proposal Template
LF Edge Proposal Template
More like this
LF Edge Projects
LF Edge Projects
More like this
EdgeLake Technical Project Getting Started Checklist
EdgeLake Technical Project Getting Started Checklist
More like this
Technical Project Getting Started Checklist
Technical Project Getting Started Checklist
More like this
Documentation Roadmap
Documentation Roadmap
More like this