commit	682e7df1663e5f80ac50243fe9ed77e426b106b0	[log] [tgz]
author	Alex <osavatieiev@mirantis.com>	Fri Apr 12 17:51:55 2019 -0500
committer	Alex <osavatieiev@mirantis.com>	Fri Apr 12 17:56:58 2019 -0500
tree	322ef53af505add29d4f05bf394aaa8054c7b17e
parent	4148552173c5ca56d19d14a3b799a667a61230ce [diff]

tree: 322ef53af505add29d4f05bf394aaa8054c7b17e

README.md

salt-cfg-checker

This checker module is used to verify and validate cloud after the deployment using number of routines to create reports

Local run

It is pretty simple:

deploy on cfg node, using root creds, on /root/

git clone https://github.com/savex/salt-cfg-checker
cd salt-cfg-checker
virtualenv .cfgcheck
source .cfgcheck/bin/activate
pip install -r requirements.txt

you can check your local.env file for parameters (no need to update for running on cfg node)
packages report (HTML): mcp_check packages report --html cloud-packages.html
packages report (CSV): mcp_check packages report --csv cloud-packages.csv

External cloud

You can also create your env file to connect to env

create your *.env file or supply environment vars to module other way
in the env file set host and user for SSH. For options, use your ~/.ssh/config
if node listing fails, execute salt-key on master and create an etc/nodes.list file with minions list

Version history

[Done] Update messages to same style
[Done] Release versions support with customizable updates
[Done] Upgrades, errors and downgrades detection
[Done] Proper Debian package version naming convention support

TODO:

Check root on startup, exit
Prepare script to create venv
Format reclass compare file

Cheers!