consumption report

Practical usage

This script helps diagnose the consumption problems when a satellite activation is failing. It is also a great tool when it comes to verifying if there is an over-allocation problem in the sub organizations.

Usage

Usage: usage : consumption-report.py [-e "entitlement_label" [-s]] [-o orgid] [-l]
 by default displays the general consumption information of the satellite

Options:
  --version             show program's version number and exit
  -h, --help            show this help message and exit
  -e ENTITLEMENT, --entitlement=ENTITLEMENT
                        Displays the allocation details of that entitlement
                        for all sub organizations. Use a label ; Does not work
                        pre satellite 5.3
  -s, --syslist         Displays the systems in the organization of the user
                        consuming that entitlement at the moment
  -l, --list            Displays the entitlements available on the satellite
                        and their names
  -o ORGID, --orgid=ORGID
                        Number of the organization to report entitlements for
  --url=SATURL          URL of the satellite api, e.g.
                        https://satellite.example.com/rpc/api or
                        http://127.0.0.1/rpc/api ; can also be just the
                        hostname or ip of the satellite. Facultative.
  --user=SATUSER        username to use with the satellite. Should be admin of
                        the organization owning the channels. Faculative.
  --password=SATPWD     password of the user. Will be asked if not given and
                        not in the configuration file.
  --org=SATORG          name of the organization to use - design the section
                        of the config file to use. Facultative, defaults to
                        baseorg
  -v, --verbose         activate verbose output

Standard usage

$ python consumption-report.py

Known issues

• Satellite 5.3 is compatible enough for most of the api calls used but the over-allocation can't be immediately seen. use the -o option to check the consumption of each of your sub organizations.
• using -o on org 1 may also include in the consumption what is allocated to sub organization depending on the satellite version used. don't rely on this information, rather use the standard output.