Supportconfig to VM/Container
an idea by puzel
Updated over 5 years ago. 2 hacker ♥️. Has no hacker: grab it!

Supportconfig contains plenty of information about the system at which it has been generated. Common task within the support chain is reproduction of the customer reported issues in our environment. The goal is to develop a tool which takes supportconfig as input and produces either a VM or a container image, resembling as closely as possible the system described by the suportconfig (e.g. installed SP, package versions, storage layout, networking layout, ...). Benefit: help with setting up the reproduction environment.

On top of that, having a workflow and associated tooling+infrastructure to pass the VM/container through the support chain (backline->L3->product engineering and/or QAM) could avoid duplicated work.

No Hackers yet

Join this project

Looking for hackers with the skills:

l3 support supportconfig

This project is part of:

Hack Week 16

Activity

  • about 7 years ago: mkubecek liked this project.
  • about 7 years ago: salisburyk liked this project.
  • about 7 years ago: puzel added keyword "l3" to this project.
  • about 7 years ago: puzel added keyword "support" to this project.
  • about 7 years ago: puzel added keyword "supportconfig" to this project.
  • about 7 years ago: puzel originated this project.


    • Comments

    Be the first to comment!

    Similar Projects

    ghostwrAIter - a local AI assisted tool for helping with support cases by paolodepa

    Description

    This project is meant to fight the loneliness of the support team members, providing them an AI assistant (hopefully) capable of scraping supportconfigs in a RAG fashion, trying to answer specific questions.

    Goals

    • Setup an Ollama backend, spinning one (or more??) code-focused LLMs selected by license, performance and quality of the results between:
    • Setup a Web UI for it, choosing an easily extensible and customizable option between:
    • Extend the solution in order to be able to:
      • Add ZIU/Concord shared folders to its RAG context
      • Add BZ cases, splitted in comments to its RAG context
        • A plus would be to login using the IDP portal to ghostwrAIter itself and use the same credentials to query BZ
      • Add specific packages picking them from IBS repos
        • A plus would be to login using the IDP portal to ghostwrAIter itself and use the same credentials to query IBS
        • A plus would be to desume the packages of interest and the right channel and version to be picked from the added BZ cases

    suse-rancher-supportconfig by eminguez

    Description

    Update: Live at https://github.com/e-minguez/suse-rancher-supportconfig I finally didn't used golang but used gum instead add-emoji

    SUSE's supportconfig support tool collects data from the SUSE Operating system. Rancher's rancher2_logs_collector.sh support tool does the same for RKE2/K3s.

    Wouldn't be nice to have a way to run both and collect all data for SUSE based RKE2/K3s clusters? Wouldn't be even better with a fancy TUI tool like bubbletea?

    Ideally the output should be an html page where you can see the logs/data directly from the browser.

    Goals

    • Familiarize myself with both supportconfig and rancher2_logs_collector.sh tools
    • Refresh my golang knowledge
    • Have something that works at the end of the hackweek ("works" may vary add-emoji )
    • Be better in naming things

    Resources

    All links provided above as well as huh