[ovirt-users] Wrong CPU type set on ovirt node on ovirt version 3.6.4.1-1.el6 - anyone know a fix ?

2017-07-26 Thread Joseph Kelly
Hello,

Has anyone come across a fix for this, in that I have a one node cluster in 
which the cluster CPU type is reporting correctly as:
Cluster CPU Type:Intel SandyBridge Family


But the only node is showing:

CPU Type:Intel Haswell-noTSX Family

However on my node both vdsm and cpuinfo agree on the the cpu model its just 
that webadmin GUI is reporting
"Intel Haswell-noTSX Family" as the CPU type.

# vdsClient -s 0 getVdsCapabilities | egrep -i cpuModel
cpuModel = 'Intel(R) Xeon(R) CPU E5-2670 v3 @ 2.30GHz'
#cat /proc/cpuinfo | grep "model name" | head -n 1
model name : Intel(R) Xeon(R) CPU E5-2670 v3 @ 2.30GHz

We're still using ovirt t version 3.6.4.1-1.el6 but are trying to move to 4.1.x

And I suspect that a possible fix might to do this:

1) shutdown VM's on the problem node put it into maintenance mode and online it 
again.
2) if that doesn't work then put into maintenance mode again and restart vdsmd 
and online the node again.

or does this need to be directly updated in the postgres DB for that node ? If 
so does anyone know how to do that ?

Thanks,
Joe.


--
J. Kelly
Infrastructure Engineer
TradingScreen
www.tradingscreen.com


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] fence issue adding host

2017-07-26 Thread Bill James
I'm adding 3 hardware nodes to our cluster. All 3 same type of server 
and software, HP DL360 G8, centos 7.

One fails the fence agent test.
The one I'm having problems with has a newer version of ilo firmware, 
not sure if related.

Troublemaker: 2.54
Others: 2.53

ovirt-engine-4.1.0.4-1.el7.centos.noarch
vdsm-4.19.4-1.el7.centos.x86_64


2017-07-26 15:14:30,215-07 INFO 
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(default task-52) [4d72d360-2b92-43f6-b2df-e80ee305c622] EVENT_ID: 
FENCE_OPERATION_USING_AGENT_AND_PROXY_STARTED(9,020), Correlation ID: 
null, Call Stack: null, Custom Event ID: -1, Message: Executing power 
management status on Host ovirt6.j2noc.com using Proxy Host 
ovirt1.j2noc.com and Fence Agent ilo4:10.144.254.89.
2017-07-26 15:14:30,216-07 INFO 
[org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand] (default 
task-52) [4d72d360-2b92-43f6-b2df-e80ee305c622] START, 
FenceVdsVDSCommand(HostName = ovirt1.j2noc.com, 
FenceVdsVDSCommandParameters:{runAsync='true', 
hostId='23d2c0ab-5dd1-43af-9db3-2a426a539faf', 
targetVdsId='----', action='STATUS', 
agent='FenceAgent:{id='null', hostId='null', order='1', type='ilo4', 
ip='10.144.254.89', port='null', user='Administrator', password='***', 
encryptOptions='false', options='power_wait=4'}', policy='null'}), log 
id: 1498b3c4
*2017-07-26 15:14:30,414-07 INFO 
[org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand] (default 
task-52) [4d72d360-2b92-43f6-b2df-e80ee305c622] FINISH, 
FenceVdsVDSCommand, return: FenceOperationResult:{status='ERROR', 
powerStatus='UNKNOWN', message='[Failed: Unable to obtain correct plug 
status or plug is not available, , ]'}, log id: 1498b3c4*
2017-07-26 15:14:30,420-07 WARN 
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(default task-52) [4d72d360-2b92-43f6-b2df-e80ee305c622] EVENT_ID: 
FENCE_OPERATION_USING_AGENT_AND_PROXY_FAILED(9,021), Correlation ID: 
null, Call Stack: null, Custom Event ID: -1, Message: Execution of power 
management status on Host ovirt6.j2noc.com using Proxy Host 
ovirt1.j2noc.com and Fence Agent ilo4:10.144.254.89 failed.
2017-07-26 15:14:30,420-07 WARN 
[org.ovirt.engine.core.bll.pm.FenceAgentExecutor] (default task-52) 
[4d72d360-2b92-43f6-b2df-e80ee305c622] Fence action failed using proxy 
host '10.144.110.99', trying another proxy
2017-07-26 15:14:30,740-07 INFO 
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(default task-52) [4d72d360-2b92-43f6-b2df-e80ee305c622] EVENT_ID: 
FENCE_OPERATION_USING_AGENT_AND_PROXY_STARTED(9,020), Correlation ID: 
null, Call Stack: null, Custom Event ID: -1, Message: Executing power 
management status on Host ovirt6.j2noc.com using Proxy Host 
ovirt2.j2noc.com and Fence Agent ilo4:10.144.254.89.
2017-07-26 15:14:30,741-07 INFO 
[org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand] (default 
task-52) [4d72d360-2b92-43f6-b2df-e80ee305c622] START, 
FenceVdsVDSCommand(HostName = ovirt2.j2noc.com, 
FenceVdsVDSCommandParameters:{runAsync='true', 
hostId='91d8fa70-fd24-4530-90f7-982ff068230b', 
targetVdsId='----', action='STATUS', 
agent='FenceAgent:{id='null', hostId='null', order='1', type='ilo4', 
ip='10.144.254.89', port='null', user='Administrator', password='***', 
encryptOptions='false', options='power_wait=4'}', policy='null'}), log 
id: 67d837da
2017-07-26 15:14:30,898-07 INFO 
[org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand] (default 
task-52) [4d72d360-2b92-43f6-b2df-e80ee305c622] FINISH, 
FenceVdsVDSCommand, return: FenceOperationResult:{status='ERROR', 
powerStatus='UNKNOWN', message='[Failed: Unable to obtain correct plug 
status or plug is not available, , ]'}, log id: 67d837da
2017-07-26 15:14:30,903-07 WARN 
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(default task-52) [4d72d360-2b92-43f6-b2df-e80ee305c622] EVENT_ID: 
FENCE_OPERATION_USING_AGENT_AND_PROXY_FAILED(9,021), Correlation ID: 
null, Call Stack: null, Custom Event ID: -1, Message: Execution of power 
management status on Host ovirt6.j2noc.com using Proxy Host 
ovirt2.j2noc.com and Fence Agent ilo4:10.144.254.89 failed.




I'm not sure the right syntax for fence_ipmilan since even a "good" host 
fails:



[root@ovirt4 prod vdsm]# fence_ipmilan -a 10.144.254.87 -P -l 
Administrator -p *** -o status -v chassis power status
Executing: /usr/bin/ipmitool -I lanplus -H 10.144.254.87 -U 
Administrator -P [set] -p 623 -L ADMINISTRATOR chassis power status


1  Error: Unable to establish IPMI v2 / RMCP+ session


Failed: Unable to obtain correct plug status or plug is not available




Any ideas on what the issue is?

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Feature: Maximum memory size | BUG

2017-07-26 Thread Jakub Niedermertl
yes, max memory size is customizabe even for Blank template

On Wed, Jul 26, 2017 at 4:32 PM, Ladislav Humenik  wrote:

> Hello, thank you for fast response.
>
> The point of changing the max_mem_size is little tricky, as we have
> environments with together ~13k VMs running on top of ovirt, no kidding :)
> and currently doing upgrades from 3.6 > 4.1. So we can easy set those
> values to the needed ones for every VM, thats not a big deal.
>
> However, I was just hoping it is editable without changing/modifying our
> current API calls, for any newly created VM (as this is the reason for
> asking for help), somewhere in engine-config or in DB.
>
> I'll just opened an RFE https://bugzilla.redhat.com/
> show_bug.cgi?id=1475382
>
> Best regards,
> Ladislav Humenik
>
>
> On 26.07.2017 15:58, Michal Skrivanek wrote:
>
>
> On 26 Jul 2017, at 16:50, Jakub Niedermertl  wrote:
>
> Hello Ladislav,
>
> the function computing size of default maximum memory size is currently
> not configurable from DB.
>
> If you want it to be so please feel free to file an RFE [1].
>
> [1]: https://bugzilla.redhat.com/enter_bug.cgi?product=ovirt-engine
>
> Best regards,
> Jakub
>
> On Wed, Jul 26, 2017 at 1:59 PM, Ladislav Humenik <
> ladislav.hume...@1und1.de> wrote:
>
>> Hallo, after engine update to 4.1.2 from 4.0.6 we have following bug
>>
>> *Your Future Description: *
>>
>> Maximum memory value is stored in |VmBase.maxMemorySizeMb| property. It
>> is validated against range [/memory of VM/, /*MaxMemorySizeInMB/], where
>> /*MaxMemorySizeInMB/ is one of |VM32BitMaxMemorySizeInMB|,
>> |VM64BitMaxMemorySizeInMB| and |VMPpc64BitMaxMemorySizeInMB| configuration
>> options depending on selected operating system of the VM. Default value in
>> webadmin UI is 4x size of memory.
>>
>> During migration of engine 4.0 -> 4.1 all VM-like entities will get max
>> memory = 4x memory.
>>
>> If a VM (or template) is imported (from export domain, snapshot, external
>> system) and doesn't have max memory set yet, the maximum value of max
>> memory is set (|*MaxMemorySizeInMB| config options).
>>
>> *Our engine settings:*
>> [root@ovirt]# engine-config -g VM64BitMaxMemorySizeInMB
>> VM64BitMaxMemorySizeInMB: 8388608 version: 4.1
>> VM64BitMaxMemorySizeInMB: 8388608 version: 3.6
>> VM64BitMaxMemorySizeInMB: 8388608 version: 4.0
>> [root@ovirt# engine-config -g VM32BitMaxMemorySizeInMB
>> VM32BitMaxMemorySizeInMB: 20480 version: general
>>
>> *Template:
>> *engine=# select vm_guid,vm_name,mem_size_mb,max_memory_size_mb from
>> vm_static where vm_name LIKE 'Blank';
>>vm_guid| vm_name | mem_size_mb |
>> max_memory_size_mb
>> --+-+---
>> --+
>>  ---- | Blank   |8192 |
>> 32768
>> (1 row)
>>
>> *Created VM*
>> - expected is mem_size_mb * VM64BitMaxMemorySizeInMB
>> - we get mem_size_mb * 4 (default)
>>
>> *Engine: *engine=# select vm_guid,vm_name,mem_size_mb,max_memory_size_mb
>> from vm_static where vm_name LIKE 'vm-hotplug%';
>>vm_guid|   vm_name   | mem_size_mb |
>> max_memory_size_mb
>> --+-+---
>> --+
>>  254a0c61-3c0a-41e7-a2ec-5f77cabbe533 | vm-hotplug  |1024 |
>>  4096
>>  c0794a03-58ba-4e68-8f43-e0320032830c | vm-hotplug2 |3072 |
>> 12288
>> (2 rows)
>>
>> *Question:*
>> It is possible to change this (default * 4) behavior in DB??
>>
>
> if the issue is with GUI then setting the max memory in the template would
> be inherited to all VMs from that template, you can even change that in
> “Blank” I think, Jakube?
> That’s for the default case, you can change that any way you like for the
> concrete VM you’re creating.
> if the issue is with API you can simply provide any number for the max mem
> in all the requests
>
> the VM[64|32]BitMaxMemorySizeInMB values are for the total maximum the
> particular qemu we ship supports, it’s not anything you should need to
> change.
>
> Thanks,
> michal
>
>
>> Kind Regards,
>> Ladislav Humenik, System administrator
>>
>>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
>
> --
> Ladislav Humenik
>
> System administrator / VI
> IT Operations Hosting Infrastructure
>
> 1&1 Internet SE | Ernst-Frey-Str. 5 | 76135 Karlsruhe | Germany
> Phone: +49 721 91374-8361 <+49%20721%20913748361>
> E-Mail: ladislav.hume...@1und1.de | Web: www.1und1.de
>
> Hauptsitz Montabaur, Amtsgericht Montabaur, HRB 24498
>
> Vorstand: Robert Hoffmann, Hans-Henning Kettler, Uwe Lamnek, Matthias 
> Steinberg
> Aufsichtsratsvorsitzender: René Obermann
>
>
> Member of United Internet
>
> Diese E-Mail kann vertrauliche und/oder gesetzlich geschützte Informationen 
> enthalten. Wenn Sie nicht der bestimmungsgemäße Adressat sind 

Re: [ovirt-users] user can see other user's vms

2017-07-26 Thread Hari Gowtham
Hi,
Thanks for the quick response,

comments inline.

On Wed, Jul 26, 2017 at 6:15 PM, Michal Skrivanek
 wrote:
>
>> On 26 Jul 2017, at 15:39, Ondra Machacek  wrote:
>>
>> Hi,
>>
>> one possible way is to add PowerUserRole to user on datacenter where you want
>> the users to operate. That way, they only can create VMs from
>> templates which are
>> public or they have direct permissions on and if the VM is created they can 
>> use
>> only that VM, and not any other.

can me point me to the doc so i can take a look at this.
And we dont want to restrict the user to make use of templates alone.
we have to give them access to spawn vms from iso too.

>>
>> On Wed, Jul 26, 2017 at 2:22 PM, Hari Gowtham  wrote:
>>> Hi,
>>>
>>> we have been trying to use ovirt to let the other devs in our team
>>> spawn vms and use it.
>>> we are nearly done with the setup. we have the hosted engine up,
>>> created gluster volumes and now we have setup the login to the portal
>>> too. While trying to spawn vms we noticed that,
>>> The admin can view, start or stop the vms on the machines which is fine.
>>> But we can see that the users can see each other user's vms too.
>>> This will make it possible for one user to start or stop other user's
>>> vm which we don't want to happen.
>>> we need to avoid this situation were one user has access to other user's vm.
>>> A particular user should be able to see the vms created by him alone
>>> So that he will have the ability to stop his own vms alone. What is
>>> the best way to create this setup?
>
> is that within the admin portal? That’s for dmins which have visibility (not 
> necessarily control) to all VMs/infrastructure
> There’s the User Portal (VM Portal since 4.1) for regular “powerless” user 
> which can see only their VMs

From the admin portal, the admin is able to see all the vms. this is
an expected behavior and this works fine.
But when the user logs in into the user portal, he can still see other
vms (which don't belong to him)

I want to mention one thing here.
We are trying to have two types of users.
1) with admin sort of access who can see and access others's vms
2) regular users who can create and use those vms in their quota.

The people who are similar to admins have certain special privileges.
we want them to be able to look into others vms
(stop, start or delete it). So we have gave them those rights.
The issue I'm talking now is with people who don't have these
privileges (the regular users who should access thier vms alone)
They are able to see others vms like the ones with elevated
privileges(the admin rights for the few users).

We want the ones with elevated privileges to be able to access others'
vm but the ones with the elevated privileges are also
able to access others vms, which we don't want to happen.

I would be happy if we have a direct solution, instead of adding
PowerUserRole to the user.

>
> Thanks,
> michal
>
>>>
>>> Is this the way it was designed to work or have i done something wrong here?
>>> Do let me know.
>>>
>>> --
>>> Regards,
>>> Hari Gowtham.
>>> ___
>>> Users mailing list
>>> Users@ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/users
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>



-- 
Regards,
Hari Gowtham.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] Windows 2016 Sysprep - Fixed IP

2017-07-26 Thread Sven Achtelik
Hi All,

I'm looking into configuring a Windows 2016 Template via Run Once to have an 
static IP. Is there any way to do that ? Maybe over the Sysrep Section ? I 
didn't find an answer about how to use it or what syntax should be used ? Must 
I put a complete answer file into it or will this section on overwrite specific 
parts of the original file that resides on the engine ?

Thank you,
Sven
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Feature: Maximum memory size | BUG

2017-07-26 Thread Michal Skrivanek

> On 26 Jul 2017, at 16:50, Jakub Niedermertl  wrote:
> 
> Hello Ladislav,
> 
> the function computing size of default maximum memory size is currently not 
> configurable from DB.
> 
> If you want it to be so please feel free to file an RFE [1].
> 
> [1]: https://bugzilla.redhat.com/enter_bug.cgi?product=ovirt-engine 
> 
> 
> Best regards,
> Jakub
> 
> On Wed, Jul 26, 2017 at 1:59 PM, Ladislav Humenik  > wrote:
> Hallo, after engine update to 4.1.2 from 4.0.6 we have following bug
> 
> *Your Future Description: *
> 
> Maximum memory value is stored in |VmBase.maxMemorySizeMb| property. It is 
> validated against range [/memory of VM/, /*MaxMemorySizeInMB/], where 
> /*MaxMemorySizeInMB/ is one of |VM32BitMaxMemorySizeInMB|, 
> |VM64BitMaxMemorySizeInMB| and |VMPpc64BitMaxMemorySizeInMB| configuration 
> options depending on selected operating system of the VM. Default value in 
> webadmin UI is 4x size of memory.
> 
> During migration of engine 4.0 -> 4.1 all VM-like entities will get max 
> memory = 4x memory.
> 
> If a VM (or template) is imported (from export domain, snapshot, external 
> system) and doesn't have max memory set yet, the maximum value of max memory 
> is set (|*MaxMemorySizeInMB| config options).
> 
> *Our engine settings:*
> [root@ovirt]# engine-config -g VM64BitMaxMemorySizeInMB
> VM64BitMaxMemorySizeInMB: 8388608 version: 4.1
> VM64BitMaxMemorySizeInMB: 8388608 version: 3.6
> VM64BitMaxMemorySizeInMB: 8388608 version: 4.0
> [root@ovirt# engine-config -g VM32BitMaxMemorySizeInMB
> VM32BitMaxMemorySizeInMB: 20480 version: general
> 
> *Template:
> *engine=# select vm_guid,vm_name,mem_size_mb,max_memory_size_mb from 
> vm_static where vm_name LIKE 'Blank';
>vm_guid| vm_name | mem_size_mb | 
> max_memory_size_mb
> --+-+-+
>  ---- | Blank   |8192 |  
> 32768
> (1 row)
> 
> *Created VM*
> - expected is mem_size_mb * VM64BitMaxMemorySizeInMB
> - we get mem_size_mb * 4 (default)
> 
> *Engine: *engine=# select vm_guid,vm_name,mem_size_mb,max_memory_size_mb from 
> vm_static where vm_name LIKE 'vm-hotplug%';
>vm_guid|   vm_name   | mem_size_mb | 
> max_memory_size_mb
> --+-+-+
>  254a0c61-3c0a-41e7-a2ec-5f77cabbe533 | vm-hotplug  |1024 |   
> 4096
>  c0794a03-58ba-4e68-8f43-e0320032830c | vm-hotplug2 |3072 |   
>12288
> (2 rows)
> 
> *Question:*
> It is possible to change this (default * 4) behavior in DB??

if the issue is with GUI then setting the max memory in the template would be 
inherited to all VMs from that template, you can even change that in “Blank” I 
think, Jakube?
That’s for the default case, you can change that any way you like for the 
concrete VM you’re creating.
if the issue is with API you can simply provide any number for the max mem in 
all the requests

the VM[64|32]BitMaxMemorySizeInMB values are for the total maximum the 
particular qemu we ship supports, it’s not anything you should need to change.

Thanks,
michal

> 
> Kind Regards,
> Ladislav Humenik, System administrator
> 
> 
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Feature: Maximum memory size | BUG

2017-07-26 Thread Jakub Niedermertl
Hello Ladislav,

the function computing size of default maximum memory size is currently not
configurable from DB.

If you want it to be so please feel free to file an RFE [1].

[1]: https://bugzilla.redhat.com/enter_bug.cgi?product=ovirt-engine

Best regards,
Jakub

On Wed, Jul 26, 2017 at 1:59 PM, Ladislav Humenik  wrote:

> Hallo, after engine update to 4.1.2 from 4.0.6 we have following bug
>
> *Your Future Description: *
>
> Maximum memory value is stored in |VmBase.maxMemorySizeMb| property. It is
> validated against range [/memory of VM/, /*MaxMemorySizeInMB/], where
> /*MaxMemorySizeInMB/ is one of |VM32BitMaxMemorySizeInMB|,
> |VM64BitMaxMemorySizeInMB| and |VMPpc64BitMaxMemorySizeInMB| configuration
> options depending on selected operating system of the VM. Default value in
> webadmin UI is 4x size of memory.
>
> During migration of engine 4.0 -> 4.1 all VM-like entities will get max
> memory = 4x memory.
>
> If a VM (or template) is imported (from export domain, snapshot, external
> system) and doesn't have max memory set yet, the maximum value of max
> memory is set (|*MaxMemorySizeInMB| config options).
>
> *Our engine settings:*
> [root@ovirt]# engine-config -g VM64BitMaxMemorySizeInMB
> VM64BitMaxMemorySizeInMB: 8388608 version: 4.1
> VM64BitMaxMemorySizeInMB: 8388608 version: 3.6
> VM64BitMaxMemorySizeInMB: 8388608 version: 4.0
> [root@ovirt# engine-config -g VM32BitMaxMemorySizeInMB
> VM32BitMaxMemorySizeInMB: 20480 version: general
>
> *Template:
> *engine=# select vm_guid,vm_name,mem_size_mb,max_memory_size_mb from
> vm_static where vm_name LIKE 'Blank';
>vm_guid| vm_name | mem_size_mb |
> max_memory_size_mb
> --+-+---
> --+
>  ---- | Blank   |8192 |
> 32768
> (1 row)
>
> *Created VM*
> - expected is mem_size_mb * VM64BitMaxMemorySizeInMB
> - we get mem_size_mb * 4 (default)
>
> *Engine: *engine=# select vm_guid,vm_name,mem_size_mb,max_memory_size_mb
> from vm_static where vm_name LIKE 'vm-hotplug%';
>vm_guid|   vm_name   | mem_size_mb |
> max_memory_size_mb
> --+-+---
> --+
>  254a0c61-3c0a-41e7-a2ec-5f77cabbe533 | vm-hotplug  |1024 |
>  4096
>  c0794a03-58ba-4e68-8f43-e0320032830c | vm-hotplug2 |3072 |
> 12288
> (2 rows)
>
> *Question:*
> It is possible to change this (default * 4) behavior in DB??
>
> Kind Regards,
> Ladislav Humenik, System administrator
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] user can see other user's vms

2017-07-26 Thread Michal Skrivanek

> On 26 Jul 2017, at 15:39, Ondra Machacek  wrote:
> 
> Hi,
> 
> one possible way is to add PowerUserRole to user on datacenter where you want
> the users to operate. That way, they only can create VMs from
> templates which are
> public or they have direct permissions on and if the VM is created they can 
> use
> only that VM, and not any other.
> 
> On Wed, Jul 26, 2017 at 2:22 PM, Hari Gowtham  wrote:
>> Hi,
>> 
>> we have been trying to use ovirt to let the other devs in our team
>> spawn vms and use it.
>> we are nearly done with the setup. we have the hosted engine up,
>> created gluster volumes and now we have setup the login to the portal
>> too. While trying to spawn vms we noticed that,
>> The admin can view, start or stop the vms on the machines which is fine.
>> But we can see that the users can see each other user's vms too.
>> This will make it possible for one user to start or stop other user's
>> vm which we don't want to happen.
>> we need to avoid this situation were one user has access to other user's vm.
>> A particular user should be able to see the vms created by him alone
>> So that he will have the ability to stop his own vms alone. What is
>> the best way to create this setup?

is that within the admin portal? That’s for dmins which have visibility (not 
necessarily control) to all VMs/infrastructure
There’s the User Portal (VM Portal since 4.1) for regular “powerless” user 
which can see only their VMs

Thanks,
michal

>> 
>> Is this the way it was designed to work or have i done something wrong here?
>> Do let me know.
>> 
>> --
>> Regards,
>> Hari Gowtham.
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
> 
> 

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] user can see other user's vms

2017-07-26 Thread Ondra Machacek
Hi,

one possible way is to add PowerUserRole to user on datacenter where you want
the users to operate. That way, they only can create VMs from
templates which are
public or they have direct permissions on and if the VM is created they can use
only that VM, and not any other.

On Wed, Jul 26, 2017 at 2:22 PM, Hari Gowtham  wrote:
> Hi,
>
> we have been trying to use ovirt to let the other devs in our team
> spawn vms and use it.
> we are nearly done with the setup. we have the hosted engine up,
> created gluster volumes and now we have setup the login to the portal
> too. While trying to spawn vms we noticed that,
> The admin can view, start or stop the vms on the machines which is fine.
> But we can see that the users can see each other user's vms too.
> This will make it possible for one user to start or stop other user's
> vm which we don't want to happen.
> we need to avoid this situation were one user has access to other user's vm.
> A particular user should be able to see the vms created by him alone
> So that he will have the ability to stop his own vms alone. What is
> the best way to create this setup?
>
> Is this the way it was designed to work or have i done something wrong here?
> Do let me know.
>
> --
> Regards,
> Hari Gowtham.
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] user can see other user's vms

2017-07-26 Thread Hari Gowtham
Hi,

we have been trying to use ovirt to let the other devs in our team
spawn vms and use it.
we are nearly done with the setup. we have the hosted engine up,
created gluster volumes and now we have setup the login to the portal
too. While trying to spawn vms we noticed that,
The admin can view, start or stop the vms on the machines which is fine.
But we can see that the users can see each other user's vms too.
This will make it possible for one user to start or stop other user's
vm which we don't want to happen.
we need to avoid this situation were one user has access to other user's vm.
A particular user should be able to see the vms created by him alone
So that he will have the ability to stop his own vms alone. What is
the best way to create this setup?

Is this the way it was designed to work or have i done something wrong here?
Do let me know.

-- 
Regards,
Hari Gowtham.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users