huntdatacenter / charm-megaraid-check Goto Github PK

View Code? Open in Web Editor NEW

1.0 1.0 0.0 26 KB

MegaRAID Check Charm

Home Page: https://jaas.ai/u/huntdatacenter/megaraid-check

License: MIT License

Makefile 43.48% Python 56.52%

juju charm megaraid nrpe

charm-megaraid-check's Introduction

MegaRAID Check

This subordinate charm is used to monitor MegaRAID controllers via NRPE (Nagios Remote Plugin Executor) with the check_lsi_raid Nagios plugin from Thomas-Krenn. This charm installs the StorCLI tool (Storage Command Line Tool) which is used interact with the MegaRAID controller on the host.

Usage

This charm can be deployed to any principal application, but requires that the nrpe charm is deployed and related to it. Here is an example where ubuntu is the principal application:

juju deploy cs:~huntdatacenter/megaraid-check
juju deploy nrpe
juju deploy ubuntu
juju deploy nagios
juju add-relation nrpe ubuntu
juju add-relation nrpe megaraid-check
juju add-relation ubuntu megaraid-check
juju add-relation nagios nrpe

Development

Here are some helpful commands to get started with development and testing:

$ make help
lint                 Run linter
build                Build charm
deploy               Deploy charm
upgrade              Upgrade charm
force-upgrade        Force upgrade charm
test-xenial-bundle   Test Xenial bundle
test-bionic-bundle   Test Bionic bundle
push                 Push charm to stable channel
clean                Clean .tox and build
help                 Show this help

Further information

charm-megaraid-check's People

Stargazers

Watchers

charm-megaraid-check's Issues

Add Juju 2.7 to ci

Juju 2.7 has been released and should be added to ci.

Test cross model relations

Change default check_lsi_raid repository to upstream

I chose to fork the upstream check_lsi_raid repository https://github.com/thomas-krenn/check_lsi_raid to https://github.com/huntdatacenter/check_lsi_raid due to the long standing issue thomas-krenn/check_lsi_raid#24 which blocks the use of newer versions of StorCLI.

The default check-repo should be set to upstream again when the issue has been resolved upstream.

Handle existing installations of storcli more gracefully

Currently the charm just removes storcli before installing from the archive supplied by storcli-url. That is not always so graceful and possible upgrade/downgrade scenarios need to be tested more.

Add docs on releasing to charm store

NRPE checks are not cleaned up when removing charm

The charm does not clean up/remove the NRPE checks on the Nagios server when destroying/removing the charm.

I am not sure how to implement this and have asked for advice on discourse.jujucharms.com

As a workaround, I have implemented a config flag called check-remove which can be used while the charm is still running. However this may be too late for folks that have already removed the charm. Removing and redeploying the accompanying nrpe charm on the principal application/charm should clear out the checks though.

The specific failure is:

Run sudo snap install juju --classic --channel=2.4/stable
2019-11-26T20:55:21Z INFO Waiting for restart...
error: cannot perform the following tasks:
- Run configure hook of "juju" snap if present (run hook "configure": / not root-owned 501:50)

For some reason this works in another test repository: https://github.com/szeestraten/charm-extra-nrpe-example/runs/321938679

Only related bug/issue I have found online is the following: https://forum.snapcraft.io/t/permissions-problem-using-snapcraft-in-azure-pipelines/13258/7

Add deploy bundle test to ci

Need to add a deploy bundle test to ci.