Cluster-Tester for SAP HANA System Replication Cluster
a project by fmherschel
Updated about 2 years ago. 5 hacker ♥️. 3 followers.

Project Description

Cluster-Tester for SAP HANA System Replication Cluster. The tester checks all SAPHanaSR attributes and tries to fins out, if the cluster is in a good status (before, during and after the test-case). The Cluster tester should also be used to tell customers, if their SAPHanaSR* cluster is ready for a maintenance procedure.

Goal for this Hackweek

The goal of this project is to automatically detect the cluster and SAP HANA SR status and to run a list of test-cases and check for the cluster (attribute) reaction, if the cluster recovery is as expected. Providing customers a tool to check cluster prerequisites for beginning maintenance procedures.

Resources

GitHub: https://github.com/SUSE/SAPHanaSR/tree/main/test (the hackweek project will take an own branch to be defined later)

Join this project

Looking for hackers with the skills:

testing python3 saphanasr pacemakercluster hakube

This project is part of:

Hack Week 23

Activity

  • about 2 years ago: mpagot liked this project.
  • about 2 years ago: lpinne joined this project.
  • about 2 years ago: epenchev liked this project.
  • about 2 years ago: mfatrez liked this project.
  • about 2 years ago: athoma liked this project.
  • about 2 years ago: fmherschel started this project.
  • about 2 years ago: fmherschel liked this project.
  • about 2 years ago: fmherschel added keyword "testing" to this project.
  • about 2 years ago: fmherschel added keyword "python3" to this project.
  • about 2 years ago: fmherschel added keyword "saphanasr" to this project.
  • about 2 years ago: fmherschel added keyword "pacemakercluster" to this project.
  • about 2 years ago: fmherschel added keyword "hakube" to this project.
  • about 2 years ago: fmherschel originated this project.


    • Comments

    Be the first to comment!

    Similar Projects

    openQA log viewer by mpagot

    Description

    *** Warning: Are You at Risk for VOMIT? ***

    Do you find yourself staring at a screen, your eyes glossing over as thousands of lines of text scroll by? Do you feel a wave of text-based nausea when someone asks you to "just check the logs"?

    You may be suffering from VOMIT (Verbose Output Mental Irritation Toxicity).

    This dangerous, work-induced ailment is triggered by exposure to an overwhelming quantity of log data, especially from parallel systems. The human brain, not designed to mentally process 12 simultaneous autoinst-log.txt files, enters a state of toxic shock. It rejects the "Verbose Output," making it impossible to find the one critical error line buried in a 50,000-line sea of "INFO: doing a thing."

    Before you're forced to rm -rf /var/log in a fit of desperation, we present the digital antacid.

    No panic: The openQA Log Visualizer (Also known as the "VOMIT-B-Gone 9000")

    This is your web-based hazmat suit for handling toxic log environments. It bravely dives into the chaotic, multi-machine mess of your openQA test runs, finds all the related, verbose logs, and force-feeds them into a parser.

    image

    Goals

    Work on the existing POC openqa-log-visualizer and change it to something usable

    Resources

    openqa-log-visualizer

    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*

    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*