Automated Lifecycle Management at the Edge
an invention by bkampen
Updated almost 3 years ago. 2 hacker ♥️. 2 followers.

Project Description

We have a lot of solutions for the Edge like: Rancher, k3s, Elemental, SLE Micro but we don't have a complete end to end example solution the deliver these. For example if a Edge device at a customer location fails somebody without any knowledge should be able the replace the device. The installation and provisioning should be automatic, this should also be for new devices.

Goals for this Hackweek

  • Automated generation of the Elemental image
  • Automated creation of the cluster and configuration in Rancher
  • A method to deliver this image to the edge device (via network)
  • Installation of the operation system and K3s on the edge device
  • Joining the Edge Device to the Cluster

Resources

Looking for hackers with the skills:

edge elemental

This project is part of:

Hack Week 22

Activity

  • almost 3 years ago: fgiudici liked this project.
  • almost 3 years ago: bkampen added keyword "edge" to this project.
  • almost 3 years ago: bkampen added keyword "elemental" to this project.
  • almost 3 years ago: paulgonin liked this project.
  • almost 3 years ago: bkampen started this project.
  • almost 3 years ago: bkampen originated this project.


    • Comments

    Be the first to comment!

    Similar Projects

    SUSE Edge Image Builder MCP by eminguez

    Description

    Based on my other hackweek project, SUSE Edge Image Builder's Json Schema I would like to build also a MCP to be able to generate EIB config files the AI way.

    Realistically I don't think I'll be able to have something consumable at the end of this hackweek but at least I would like to start exploring MCPs, the difference between an API and MCP, etc.

    Goals

    • Familiarize myself with MCPs
    • Unrealistic: Have an MCP that can generate an EIB config file

    Resources

    Set Uyuni to manage edge clusters at scale by RDiasMateus

    Description

    Prepare a Poc on how to use MLM to manage edge clusters. Those cluster are normally equal across each location, and we have a large number of them.

    The goal is to produce a set of sets/best practices/scripts to help users manage this kind of setup.

    Goals

    step 1: Manual set-up

    Goal: Have a running application in k3s and be able to update it using System Update Controler (SUC)

    • Deploy Micro 6.2 machine

    • Deploy k3s - single node

      • https://docs.k3s.io/quick-start

    • Build/find a simple web application (static page)

      • Build/find a helmchart to deploy the application

    • Deploy the application on the k3s cluster

    • Install App updates through helm update

    • Install OS updates using MLM

    step 2: Multi-node cluster

    Goal: Use SUC to update a multi-node cluster.

    • Create a multi-node cluster
    • Deploy application
    • Install App updates through helm update
    • Prepare a SUC for OS update (k3s also? How?)
      • https://github.com/rancher/system-upgrade-controller
      • https://documentation.suse.com/cloudnative/k3s/latest/en/upgrades/automated.html

    step 3: Automate day 2

    Goal: Trigger the application deployment and update from MLM

    • Salt states For application (with static data)
      • Deploy the application helmchart, if not present
      • Update/deploy the SUC?
      • Update/deploy the SUC CRD with the update procedure
    • Salt states to deploy k3s cluster?
    • Link it to GIT
      • Define how to link the state to the machines (based in some pillar data? Using configuration channels by importing the state? Naming convention?)
      • Use git update to trigger helmchart app update
      • Update git SUC - CR and apply the state to trigger the update of the machine.
    • Recurrent state applying configuration channel?

    SUSE Edge Image Builder json schema by eminguez

    Description

    Current SUSE Edge Image Builder tool doesn't provide a json schema (yes, I know EIB uses yaml but it seems JSON Schema can be used to validate YAML documents yay!) that defines the configuration file syntax, values, etc.

    Having a json schema will make integrations straightforward, as once the json schema is in place, it can be used as the interface for other tools to consume and generate EIB definition files (like TUI wizards, web UIs, etc.)

    I'll make use of AI tools for this so I'd learn more about vibe coding, agents, etc.

    Goals

    • Learn about json schemas
    • Try to implement something that can take the EIB source code and output an initial json schema definition
    • Create a PR for EIB to be adopted
    • Learn more about AI tools and how those can help on similar projects.

    Resources