supportconfig database
an invention by leonardocf
Updated over 5 years ago. 2 hacker ♥️.

The supportconfig utility is used by support teams to collect all information needed to troubleshoot a system in one shot.

The objective of this project is to create a central repository of supportconfig tarballs. To do so, we're going to develop a set of tools to automatically fetch tarballs from known sources, parse the information, import the useful parts into an SQL database and expose it in a Web front-end where users can run some simple queries.

The following components will be developed:

  • Collector: Retrieves supportconfigs from the usual sources (Bugzilla, ftp.novell.com).
  • Parser: Parses the data from a supportconfig tarball and imports it into a database.
  • Front-end: Displays the collected data in useful formats, generate statistics and allow simple queries.

Looking for hackers with the skills:

python django shell

This project is part of:

Hack Week 10

Activity

  • over 7 years ago: barendartchuk liked this project.
  • over 9 years ago: mkoutny liked this project.
  • about 12 years ago: leonardocf removed keyword xml from this project.
  • about 12 years ago: leonardocf added keyword "python" to this project.
  • about 12 years ago: leonardocf added keyword "django" to this project.
  • about 12 years ago: leonardocf added keyword "shell" to this project.
  • about 12 years ago: leonardocf added keyword "xml" to this project.
  • about 12 years ago: leonardocf started this project.
  • about 12 years ago: leonardocf originated this project.


    • Comments

    • leonardocf
      about 12 years ago by leonardocf | Reply

      The "Collector" and "Parser" components were developed during Hack Week 9.

    • leonardocf
      about 12 years ago by leonardocf | Reply

      A working prototype of the front-end (using python-django) was developed during Hack Week 10.

    Similar Projects

    Bring to Cockpit + System Roles capabilities from YAST by miguelpc

    Bring to Cockpit + System Roles features from YAST

    Cockpit and System Roles have been added to SLES 16 There are several capabilities in YAST that are not yet present in Cockpit and System Roles We will follow the principle of "automate first, UI later" being System Roles the automation component and Cockpit the UI one.

    Goals

    The idea is to implement service configuration in System Roles and then add an UI to manage these in Cockpit. For some capabilities it will be required to have an specific Cockpit Module as they will interact with a reasource already configured.

    Resources

    A plan on capabilities missing and suggested implementation is available here: https://docs.google.com/spreadsheets/d/1ZhX-Ip9MKJNeKSYV3bSZG4Qc5giuY7XSV0U61Ecu9lo/edit

    Linux System Roles: https://linux-system-roles.github.io/