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(a)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(a)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(a)ovirt.org <mailto:Users@ovirt.org>
http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users