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.
>
>
>