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
Looking for hackers with the skills:
This project is part of:
Hack Week 16
Activity
Comments
Be the first to comment!
Similar Projects
SUSE Health Check Tools by roseswe
SUSE HC Tools Overview
A collection of tools written in Bash or Go 1.24++ to make life easier with handling of a bunch of tar.xz balls created by supportconfig.
Background: For SUSE HC we receive a bunch of supportconfig tar balls to check them for misconfiguration, areas for improvement or future changes.
Main focus on these HC are High Availability (pacemaker), SLES itself and SAP workloads, esp. around the SUSE best practices.
Goals
- Overall improvement of the tools
- Adding new collectors
- Add support for SLES16
Resources
csv2xls* example.sh go.mod listprodids.txt sumtext* trails.go README.md csv2xls.go exceltest.go go.sum m.sh* sumtext.go vercheck.py* config.ini csvfiles/ getrpm* listprodids* rpmdate.sh* sumxls* verdriver* credtest.go example.py getrpm.go listprodids.go sccfixer.sh* sumxls.go verdriver.go
docollall.sh* extracthtml.go gethostnamectl* go.sum numastat.go cpuvul* extractcluster.go firmwarebug* gethostnamectl.go m.sh* numastattest.go cpuvul.go extracthtml* firmwarebug.go go.mod numastat* xtr_cib.sh*