[Users] Nagios monitoring plugin check_rhev3 1.2.1 released
I'm happy to announce version 1.2.1 of check_rhev3. check_rhev3 is a monitoring plugin for Icinga/Nagios and it's forks, which is used to monitor datacenters, clusters, hosts, vms, vm pools and storage domains of Red Hat Enterprise Virtualization (RHEV) and oVirt virtualization environments. Download this plugin from: https://github.com/ovido/check_rhev3/releases/check_rhev3-1.2.1 For further information on how to install this plugin visit: https://github.com/ovido/check_rhev3/wiki/Installation-Documentation A detailed usage documentation can be found here: https://github.com/ovido/check_rhev3/wiki/Usage-Documentation Changelog: * Bug fixed: * Fixed search regex for hosts and networks If you have any questions or ideas, please drop me an email: r.koch@ovido.at. Thank you for using check_rhev3. -- Best regards René Koch Senior Solution Architect ============================================ ovido gmbh - "Das Linux Systemhaus" Brünner Straße 163, A-1210 Wien Phone: +43 720 / 530 670 Mobile: +43 660 / 512 21 31 E-Mail: r.koch@ovido.at ============================================
On Tue, Jul 23, 2013 at 5:44 PM, René Koch (ovido) wrote:
I'm happy to announce version 1.2.1 of check_rhev3.
A detailed usage documentation can be found here: https://github.com/ovido/check_rhev3/wiki/Usage-Documentation
Thank you for using check_rhev3.
Inside the detailed doc " All RHEV Checks are executed via RHEV REST-API, so the following requirements must be met: HTTPS connection from Monitoring server to RHEV Manager (default: TCP/8443) RHEV Admin user for REST-API login " Can we somehow limit the power of the user? Is there a predefined role that has a sort of "select all" (such as 'select any table' in Oracle terms) or could it be easily built and set? Thanks, Gianluca
This is a good point. Can there be a "read only" type of user? Thank you, Christian Hernandez 1225 Los Angeles Street Glendale, CA 91204 Phone: 877-782-2737 ext. 4566 Fax: 818-265-3152 christianh@4over.com <mailto:christianh@4over.com> www.4over.com <http://www.4over.com> On Tue, Jul 23, 2013 at 9:11 AM, Gianluca Cecchi <gianluca.cecchi@gmail.com>wrote:
On Tue, Jul 23, 2013 at 5:44 PM, René Koch (ovido) wrote:
I'm happy to announce version 1.2.1 of check_rhev3.
A detailed usage documentation can be found here: https://github.com/ovido/check_rhev3/wiki/Usage-Documentation
Thank you for using check_rhev3.
Inside the detailed doc " All RHEV Checks are executed via RHEV REST-API, so the following requirements must be met:
HTTPS connection from Monitoring server to RHEV Manager (default: TCP/8443) RHEV Admin user for REST-API login "
Can we somehow limit the power of the user? Is there a predefined role that has a sort of "select all" (such as 'select any table' in Oracle terms) or could it be easily built and set?
Thanks, Gianluca _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
On 07/23/2013 07:13 PM, Christian Hernandez wrote:
This is a good point. Can there be a "read only" type of user?
have you tried a user with the 'viewer' role?
Thank you,
Christian Hernandez 1225 Los Angeles Street Glendale, CA 91204 Phone: 877-782-2737 ext. 4566 Fax: 818-265-3152 christianh@4over.com <mailto:christianh@4over.com> <mailto:christianh@4over.com <mailto:christianh@4over.com>> www.4over.com <http://www.4over.com/> <http://www.4over.com <http://www.4over.com/>>
On Tue, Jul 23, 2013 at 9:11 AM, Gianluca Cecchi <gianluca.cecchi@gmail.com <mailto:gianluca.cecchi@gmail.com>> wrote:
On Tue, Jul 23, 2013 at 5:44 PM, René Koch (ovido) wrote: > > I'm happy to announce version 1.2.1 of check_rhev3.
> A detailed usage documentation can be found here: > https://github.com/ovido/check_rhev3/wiki/Usage-Documentation >
> > Thank you for using check_rhev3.
Inside the detailed doc " All RHEV Checks are executed via RHEV REST-API, so the following requirements must be met:
HTTPS connection from Monitoring server to RHEV Manager (default: TCP/8443) RHEV Admin user for REST-API login "
Can we somehow limit the power of the user? Is there a predefined role that has a sort of "select all" (such as 'select any table' in Oracle terms) or could it be easily built and set?
Thanks, Gianluca _______________________________________________ Users mailing list Users@ovirt.org <mailto:Users@ovirt.org> http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
On Tue, 2013-07-23 at 18:11 +0200, Gianluca Cecchi wrote:
On Tue, Jul 23, 2013 at 5:44 PM, René Koch (ovido) wrote:
I'm happy to announce version 1.2.1 of check_rhev3.
A detailed usage documentation can be found here: https://github.com/ovido/check_rhev3/wiki/Usage-Documentation
Thank you for using check_rhev3.
Inside the detailed doc " All RHEV Checks are executed via RHEV REST-API, so the following requirements must be met:
HTTPS connection from Monitoring server to RHEV Manager (default: TCP/8443) RHEV Admin user for REST-API login "
Can we somehow limit the power of the user? Is there a predefined role that has a sort of "select all" (such as 'select any table' in Oracle terms) or could it be easily built and set?
This was required for RHEV 3.0, which was the version I initially wrote the plugin for. For newer versions (>= 3.1) of oVirt and RHEV you only need the following permissions (create new role for it, or is there a role available in oVirt > 3.2.1?): Account Type: Admin System - Configure System - Login Permissions This allows a user to connect to REST-API (and Administrator Portal) and read everything, but doesn't allow any changes (=> read only). I'll update the documentation. Thanks for reporting this documentation bug. Regards, René
On 07/24/2013 11:26 AM, René Koch (ovido) wrote:
On Tue, 2013-07-23 at 18:11 +0200, Gianluca Cecchi wrote:
On Tue, Jul 23, 2013 at 5:44 PM, René Koch (ovido) wrote:
I'm happy to announce version 1.2.1 of check_rhev3.
A detailed usage documentation can be found here: https://github.com/ovido/check_rhev3/wiki/Usage-Documentation
Thank you for using check_rhev3.
Inside the detailed doc " All RHEV Checks are executed via RHEV REST-API, so the following requirements must be met:
HTTPS connection from Monitoring server to RHEV Manager (default: TCP/8443) RHEV Admin user for REST-API login "
Can we somehow limit the power of the user? Is there a predefined role that has a sort of "select all" (such as 'select any table' in Oracle terms) or could it be easily built and set?
This was required for RHEV 3.0, which was the version I initially wrote the plugin for.
For newer versions (>= 3.1) of oVirt and RHEV you only need the following permissions (create new role for it, or is there a role available in oVirt > 3.2.1?): Account Type: Admin System - Configure System - Login Permissions
there should be a built-in 'viewer' role with this
This allows a user to connect to REST-API (and Administrator Portal) and read everything, but doesn't allow any changes (=> read only).
I'll update the documentation. Thanks for reporting this documentation bug.
On Wed, 2013-07-24 at 11:58 +0300, Itamar Heim wrote:
On 07/24/2013 11:26 AM, René Koch (ovido) wrote:
On Tue, 2013-07-23 at 18:11 +0200, Gianluca Cecchi wrote:
On Tue, Jul 23, 2013 at 5:44 PM, René Koch (ovido) wrote:
I'm happy to announce version 1.2.1 of check_rhev3.
A detailed usage documentation can be found here: https://github.com/ovido/check_rhev3/wiki/Usage-Documentation
Thank you for using check_rhev3.
Inside the detailed doc " All RHEV Checks are executed via RHEV REST-API, so the following requirements must be met:
HTTPS connection from Monitoring server to RHEV Manager (default: TCP/8443) RHEV Admin user for REST-API login "
Can we somehow limit the power of the user? Is there a predefined role that has a sort of "select all" (such as 'select any table' in Oracle terms) or could it be easily built and set?
This was required for RHEV 3.0, which was the version I initially wrote the plugin for.
For newer versions (>= 3.1) of oVirt and RHEV you only need the following permissions (create new role for it, or is there a role available in oVirt > 3.2.1?): Account Type: Admin System - Configure System - Login Permissions
there should be a built-in 'viewer' role with this
In my oVirt 3.2.1 setup there's no such predefined role. Was this maybe added later?
This allows a user to connect to REST-API (and Administrator Portal) and read everything, but doesn't allow any changes (=> read only).
I'll update the documentation. Thanks for reporting this documentation bug.
On 07/24/2013 12:48 PM, René Koch (ovido) wrote:
On Wed, 2013-07-24 at 11:58 +0300, Itamar Heim wrote:
On 07/24/2013 11:26 AM, René Koch (ovido) wrote:
On Tue, 2013-07-23 at 18:11 +0200, Gianluca Cecchi wrote:
On Tue, Jul 23, 2013 at 5:44 PM, René Koch (ovido) wrote:
I'm happy to announce version 1.2.1 of check_rhev3.
A detailed usage documentation can be found here: https://github.com/ovido/check_rhev3/wiki/Usage-Documentation
Thank you for using check_rhev3.
Inside the detailed doc " All RHEV Checks are executed via RHEV REST-API, so the following requirements must be met:
HTTPS connection from Monitoring server to RHEV Manager (default: TCP/8443) RHEV Admin user for REST-API login "
Can we somehow limit the power of the user? Is there a predefined role that has a sort of "select all" (such as 'select any table' in Oracle terms) or could it be easily built and set?
This was required for RHEV 3.0, which was the version I initially wrote the plugin for.
For newer versions (>= 3.1) of oVirt and RHEV you only need the following permissions (create new role for it, or is there a role available in oVirt > 3.2.1?): Account Type: Admin System - Configure System - Login Permissions
there should be a built-in 'viewer' role with this
In my oVirt 3.2.1 setup there's no such predefined role. Was this maybe added later?
its ovirt test day, worth checking in 3.3 ;)
This allows a user to connect to REST-API (and Administrator Portal) and read everything, but doesn't allow any changes (=> read only).
I'll update the documentation. Thanks for reporting this documentation bug.
participants (4)
-
Christian Hernandez -
Gianluca Cecchi -
Itamar Heim -
René Koch (ovido)