Re: [ovirt-users] Frustration defines the deployment of Hosted Engine

[Sven Kieske]

On 28.06.2017 12:33, Sandro Bonazzola wrote:
>> 2. Should I migrate from XenServer to oVirt? This is biased, I know, but
>> I would like to hear opinions. The folks with @redhat.com email
>> addresses will know how to advocate in favor of oVirt.
>>
> I don't know, and I don't think (having a @redhat.com email myself) I
> should advocate.
> If someone made a comparison (even if it's just for their own specific use
> case), it could be great if it could be shared. If you do - please share
> your thoughts.

Hi,

for what it's worth, here is a matrix like comparison (you can configure
the products and should select rhev for ovirt like features):

https://www.whatmatrix.com/comparison/Virtualization

some features of xen are not available in ovirt/rhev, e.g. live
migration with local storage.

HTH

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

[ovirt-users] Ovirt installation planning question

[Alan Bunch]

Hello all,

I have a question about the initial setup for ovirt. I have 3 nodes
that I am about ready to install a hyper converged setup using Gluster
for storage and hosted-engine.

My question is this:

What does the networking setup need to look like at install time ? Do
I need to setup all of the bonds, vlans and bridges before I start the install
or should I just set an ovirtmgmt bond/vlan/bridge and setup the rest of the
networking inside of ovirt. I expect to need 3 or 4 networks/vlan to match
my existing networks to attach vm's to.

Any help or pointers would be appreciated.

Thank You

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

[ovirt-users] ovirt-guest-agent - Ubuntu 16.04

[FERNANDO FREDIANI]

Hello

Is the maintainer of ovirt-guest-agent for Ubuntu on this mail list ?

I have noticed that if you install ovirt-guest-agent package from Ubuntu 
repositories it doesn't start. Throws an error about python and never 
starts. Has anyone noticied the same ? OS in this case is a clean 
minimal install of Ubuntu 16.04.


Installing it from the following repository works fine - 
http://download.opensuse.org/repositories/home:/evilissimo:/ubuntu:/16.04/xUbuntu_16.04


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

[ovirt-users] ovirt can't find user

[Fabrice Bacchella]

I tried to add a user in ovirt, but it's not identified:
2017-06-28 16:48:48,505+02 ERROR 
[org.ovirt.engine.core.sso.utils.NegotiateAuthUtils] (default task-22) [] 
External Authentication Failed: Cannot resolve principal 'rexecutor@internal'


/usr/bin/ovirt-aaa-jdbc-tool user  show rexecutor
-- User rexecutor(b1727291-5ad4-4575-b8ec-53bdc9ce4aef) --
Namespace: *
Name: rexecutor
ID: b1727291-5ad4-4575-b8ec-53bdc9ce4aef
Display Name: 
Email: 
First Name: 
Last Name: 
Department: 
Title: 
Description: 
Account Disabled: false
Account Locked: false
Account Unlocked At: 2017-06-16 13:49:31Z
Account Valid From: 2017-06-15 16:41:14Z
Account Valid To: 2217-06-15 16:41:14Z
Account Without Password: true
Last successful Login At: 1970-01-01 00:00:00Z
Last unsuccessful Login At: 1970-01-01 00:00:00Z
Password Valid To: 2025-08-15 10:30:00Z

It's listed as a known user:

  
  
62313732373239312D356164342D343537352D623865632D353362646339636534616566
  
  
  
  *
  rexecutor
  rexecutor@internal-authz
  
internal-authz
  
  
  
  
  


My admin domain authentication looks OK:
config.datasource.jdbcurl=jdbc:postgresql://pgdb:5432/ovirt_engine?sslfactory=org.postgresql.ssl.NonValidatingFactory
config.datasource.dbuser=ovirt
config.datasource.dbpassword=XXX
config.datasource.jdbcdriver=org.postgresql.Driver
config.datasource.schemaname=aaa_jdbc

It tried to increase org.ovirt.engine.core.sso.utils debug log level by 
modifying /usr/share/ovirt-engine/services/ovirt-engine/ovirt-engine.xml.in

diff ovirt-engine.xml.in*
201,204d200
<   
< 
<   
< 

I just got in the log:
2017-06-28 17:17:09,404+02 DEBUG 
[org.ovirt.engine.core.sso.utils.NonInteractiveAuth] (default task-7) [] 
Performing Negotiate Auth
2017-06-28 17:17:09,404+02 DEBUG 
[org.ovirt.engine.core.sso.utils.NegotiateAuthUtils] (default task-7) [] 
Performing external authentication
2017-06-28 17:17:09,410+02 ERROR 
[org.ovirt.engine.core.sso.utils.NegotiateAuthUtils] (default task-7) [] 
External Authentication Failed: Cannot resolve principal 'rexecutor@internal'
2017-06-28 17:17:09,410+02 DEBUG 
[org.ovirt.engine.core.sso.utils.NegotiateAuthUtils] (default task-7) [] 
External Authentication Failed: Class: class 
org.ovirt.engine.core.extensions.mgr.ExtensionInvokeCommandFailedException
Input:
{Extkey[name=EXTENSION_INVOKE_COMMAND;type=class 
org.ovirt.engine.api.extensions.ExtUUID;uuid=EXTENSION_INVOKE_COMMAND[485778ab-bede-4f1a-b823-77b262a2f28d];]=AAA_AUTHZ_FETCH_PRINCIPAL_RECORD[5a5bf9bb-9336-4376-a823-26efe1ba26df],
 Extkey[name=AAA_AUTHZ_QUERY_FLAGS;type=class 
java.lang.Integer;uuid=AAA_AUTHZ_QUERY_FLAGS[97d226e9-8d87-49a0-9a7f-af689320907b];]=3,
 Extkey[name=EXTENSION_INVOKE_CONTEXT;type=class 
org.ovirt.engine.api.extensions.ExtMap;uuid=EXTENSION_INVOKE_CONTEXT[886d2ebb-312a-49ae-9cc3-e1f849834b7d];]={Extkey[name=AAA_AUTHZ_AVAILABLE_NAMESPACES;type=interface
 
java.util.Collection;uuid=AAA_AUTHZ_AVAILABLE_NAMESPACES[6dffa34c-955f-486a-bd35-0a272b45a711];]=[DC=XXX],
 Extkey[name=EXTENSION_LICENSE;type=class 
java.lang.String;uuid=EXTENSION_LICENSE[8a61ad65-054c-4e31-9c6d-1ca4d60a4c18];]=ASL
 2.0, Extkey[name=EXTENSION_GLOBAL_CONTEXT;type=class 
org.ovirt.engine.api.extensions.ExtMap;uuid=EXTENSION_GLOBAL_CONTEXT[9799e72f-7af6-4cf1-bf08-297bc8903676];]=*skip*,
 Extkey[name=EXTENSION_NAME;type=class 
java.lang.String;uuid=EXTENSION_NAME[651381d3-f54f-4547-bf28-b0b01a103184];]=ovirt-engine-extension-aaa-ldap.authz,
 Extkey[name=EXTENSION_MANAGER_TRACE_LOG;type=interface 
org.slf4j.Logger;uuid=EXTENSION_MANAGER_TRACE_LOG[863db666-3ea7-4751-9695-918a3197ad83];]=org.slf4j.impl.Slf4jLogger(org.ovirt.engine.core.extensions.mgr.ExtensionsManager.trace.ovirt-engine-extension-aaa-ldap.authz.XXX-authz),
 Extkey[name=EXTENSION_CONFIGURATION_SENSITIVE_KEYS;type=interface 
java.util.Collection;uuid=EXTENSION_CONFIGURATION_SENSITIVE_KEYS[a456efa1-73ff-4204-9f9b-ebff01e35263];]=[],
 Extkey[name=EXTENSION_VERSION;type=class 
java.lang.String;uuid=EXTENSION_VERSION[fe35f6a8-8239-4bdb-ab1a-af9f779ce68c];]=1.3.1,
 Extkey[name=EXTENSION_PROVIDES;type=interface 
java.util.Collection;uuid=EXTENSION_PROVIDES[8cf373a6-65b5-4594-b828-0e275087de91];]=[org.ovirt.engine.api.extensions.aaa.Authz],
 Extkey[name=EXTENSION_AUTHOR;type=class 
java.lang.String;uuid=EXTENSION_AUTHOR[ef242f7a-2dad-4bc5-9aad-e07018b7fbcc];]=The
 oVirt Project, Extkey[name=EXTENSION_LOCALE;type=class 
java.lang.String;uuid=EXTENSION_LOCALE[0780b112-0ce0-404a-b85e-8765d778bb29];]=en_US,
 Extkey[name=EXTENSION_CONFIGURATION_FILE;type=class 
java.lang.String;uuid=EXTENSION_CONFIGURATION_FILE[4fb0ffd3-983c-4f3f-98ff-9660bd67af6a];]=/etc/ovirt-engine/extensions.d/-authz.properties,
 Extkey[name=EXTENSION_HOME_URL;type=class 
java.lang.String;uuid=EXTENSION_HOME_URL[4ad7a2f4-f969-42d4-b399-72d192e18304];]=http://www.ovirt.org,
 Extkey[name=EXTENSION_CONFIGURATION;type=class 
java.util.Properties;uuid=EXTENSION_CONFIGURATION[2d48ab72-f0a1-4312-b4ae-5068a226b0fc];]=***,
 

Re: [ovirt-users] Moving thin provisioned disks question

[Gianluca Cecchi]

On Wed, Jun 28, 2017 at 1:14 PM, Fred Rolland  wrote:

>
> Hi,
>
> Yes, the /etc/vdsm/logger.conf contains log level settings for most of the
> operations, but not all.
>
> You can use vdsm-client to enable logging :
>
> vdsm-client  Host setLogLevel level=DEBUG name=QemuImg
>
>
>
Thanks.
The vdsm-client commnad was not installed by default during my host setup
(plain CentOS 7.3 server); not in default packages installed when deploying
host from web ui.
So I manually installed it (at the version matching the current vdsm one):
yum install vdsm-client-4.19.10.1-1.el7.centos.x86_64

[root@ov300 vdsm]# vdsm-client Host setLogLevel level=DEBUG name=QemuImg
true
[root@ov300 vdsm]#

And then I see in vdsm.log

2017-06-28 16:20:08,396+0200 DEBUG (tasks/5) [QemuImg] qemu-img operation
progress: 3.0% (qemuimg:330)

How to have it persistent across reboots? Is it safe and should imply only
debug log for qemu-img commands?



> Regarding the UI, see attached a screenshot. Under the "Locked" status
> there is a progress bar.
>

It is not my case.
See this screenshot while qemu-imh convert is already in place, moving a
900Gb disk from iSCSI SD to iSCSI SD:
https://drive.google.com/file/d/0BwoPbcrMv8mvcmpOVWZFM09RM00/view?usp=sharing

My engine is 4.1.1.8-1.el7.centos on CentOS 7.3 and my host has
qemu-kvm-ev-2.6.0-28.el7_3.6.1.x86_64 and vdsm-4.19.10.1-1.el7.centos.x86_64
In which version was it introduced?
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] [ansible/ansible] ovirt_storage_domains can not find iscsi disk during creation (state: present) (#25417)

[Yaniv Kaul]

Can you share vdsm log?

On Wed, Jun 28, 2017 at 4:16 PM, victor 600833 
wrote:

> Hi ondra,
>
> As you pointed. in your previous mail.
>
> The iscsiadm discovered througth  10.11.8.190. It should  have probed  
> 10.10.1.1.
> This may be the root cause.
>
>
>
> Victor,
>
>
>
>
>
> If you lookup at our playbook.
>
>   - name: create iscsi_dsk02
> ovirt_storage_domains:
>  auth:
>   url: https://rhevm2.res1/ovirt-engine/api
>   token: "{{ ovirt_auth.token }}"
>   insecure: True
>  name: iscsi_dsk02
>  domain_function: data
>  host: pdx1cr207
>  data_center: default
>  iscsi:
>   target: iqn.2017-06.stet.iscsi.server:target
>   address: *10.10.1.1*
>   lun_id: 3600140550738b53dd774303bfedac122
>  state: absent
>  destroy: true
> register: res_iscsi_dsk02
>   - debug:
>  var: res_iscsi_dsk02
>
> On Wed, Jun 28, 2017 at 7:58 AM, Ondra Machacek 
> wrote:
>
>> It's using the host, which you will pass as host parameter to the task
>> for iscsi discover.
>>
>> As Yaniv said, can you please share your issue on our mailing list:
>>
>> users@ovirt.org
>>
>> There are people with knowledge of iSCSI and they will help you.
>>
>> —
>> You are receiving this because you were mentioned.
>> Reply to this email directly, view it on GitHub
>> ,
>> or mute the thread
>> 
>> .
>>
>
>
> ___
> 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] [ansible/ansible] ovirt_storage_domains can not find iscsi disk during creation (state: present) (#25417)

[victor 600833]

Hi ondra,

As you pointed. in your previous mail.

The iscsiadm discovered througth  10.11.8.190. It should  have probed
10.10.1.1.
This may be the root cause.



Victor,





If you lookup at our playbook.

  - name: create iscsi_dsk02
ovirt_storage_domains:
 auth:
  url: https://rhevm2.res1/ovirt-engine/api
  token: "{{ ovirt_auth.token }}"
  insecure: True
 name: iscsi_dsk02
 domain_function: data
 host: pdx1cr207
 data_center: default
 iscsi:
  target: iqn.2017-06.stet.iscsi.server:target
  address: *10.10.1.1*
  lun_id: 3600140550738b53dd774303bfedac122
 state: absent
 destroy: true
register: res_iscsi_dsk02
  - debug:
 var: res_iscsi_dsk02

On Wed, Jun 28, 2017 at 7:58 AM, Ondra Machacek 
wrote:

> It's using the host, which you will pass as host parameter to the task
> for iscsi discover.
>
> As Yaniv said, can you please share your issue on our mailing list:
>
> users@ovirt.org
>
> There are people with knowledge of iSCSI and they will help you.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> ,
> or mute the thread
> 
> .
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Unable to rename disks via REST API

[Juan Hernández]

On 06/28/2017 01:34 PM, Bruno Rodriguez wrote:
> Shit, I got it. Sorry
> 
> The problem is that I was accessing to the v4 disk-attachment id and I
> was getting everything quite messed up. I was doing all of this while
> creating a machine, so I was trying to rename the disk at the same time
> it's being created.
> 
> I'll delete all the "if ($ovirt_major == 3)" I have in my code. If I
> have any problem I'll let you know.
> 
> Thank you 
> 

If what you want to do is set the name of the disk for a VM that you are
creating then you can just set it when adding the disk:

  POST /ovirt-engine/api/vms/123/diskattachments

  

  yourfavoritename
  ...

...
  

That way you don't need to modify it later.

Also, in general, try to wait till the objects are completely created
before trying to use or update them. For disks in particular, it is good
idea to repeatedly retrieve the disk till the 'status' is 'OK':


https://github.com/oVirt/ovirt-engine-sdk/blob/master/sdk/examples/add_vm_disk.py#L73-L80

(This is an example from the Python SDK, but you get the idea. There are
SDKs for Ruby and Java as well.)

Finally, if you get a 500 error then there is most probably a bug. The
API should never return that, even if you try to do something that
doesn't make sense it should respond with a reasonable error message. If
you keep getting that 500 error please share the details.

> On Wed, Jun 28, 2017 at 1:03 PM, Juan Hernández  > wrote:
> 
> On 06/28/2017 12:55 PM, Bruno Rodriguez wrote:
> > I'm sorry about bothering you again, but after trying it some times I'm
> > still getting a "500 Internal Server Error". I'm using a REST client
> > instead of CURL and I tried adding a "Version: 3" to headers and used
> > the URL with the v3 as well.
> >
> > I'm issuing a PUT of
> >
> > Alias_for_disk
> >
> > To the URL
> >
> > 
> https://myserver/ovirt-engine/api/v3/vms/62498f51-0203-48b9-83c8-4c6f3bdfe05c/disks/583ed952-46a8-4bc5-8a27-8660e4a24ea2
> 
> 
> >
> > I mean, I can live without it but we are using oVirt as a "static
> > virtualization" environment and is quite useful for us being able to
> > recognize easily each disk by its server name. In case I have to wait
> > until the 4.2 API version to automatize this I'll do :(
> >
> 
> That should work. Can you please check if you get any useful message in
> /var/log/ovirt-engine/server.log or /var/log/ovirt-engine/engine.log?
> 
> >
> >
> > On Wed, Jun 28, 2017 at 11:18 AM, Bruno Rodriguez  
> > >> wrote:
> >
> > Thank you very much !!!
> >
> > I expected I was missing something like that. Thanks again!
> >
> > On Wed, Jun 28, 2017 at 11:12 AM, Juan Hernández
> > 
> >> wrote:
> >
> > On 06/28/2017 10:43 AM, Bruno Rodriguez wrote:
> > > Thank you, Daniel
> > >
> > > I tried a PUT with the same XML body, I got a "405
> Method Not Allowed".
> > > It's quite strange, there must be someting I'm missing
> > >
> >
> > The operation to update a disk will be introduced in version 4
> > of the
> > API with version 4.2 of the engine. Meanwhile the way to
> update
> > the disk
> > is to use version 3 of the API and the disks
> sub-collection of the
> > virtual machine. That means that if you have a VM with id 123
> > and a disk
> > with id 456 you can send a request like this:
> >
> >   PUT /ovirt-engine/api/v3/vms/123/disks/456
> >
> > With a request body like this:
> >
> >   
> > newalias
> >   
> >
> > Note that you can use the above "v3" prefix in the URL or
> else the
> > "Version: 3" header. A complete example using curl:
> >
> > ---8<---
> > #!/bin/bash -ex
> >
> > url="https://.../ovirt-engine/api;
> > user="admin@internal"
> > password="..."
> > vm_id="..."
> > disk_id="..."
> >
> > curl \
> > --verbose \
> > --cacert "ca.pem" \
> > --header "Version: 3" \
> > --header "Content-Type: application/xml" \
> > --user "${user}:${password}" \
> > --request PUT \
> > --data "
> > 
> >   newalias
> > 
> > " \
> > 

Re: [ovirt-users] Unable to rename disks via REST API

[Bruno Rodriguez]

Shit, I got it. Sorry

The problem is that I was accessing to the v4 disk-attachment id and I was
getting everything quite messed up. I was doing all of this while creating
a machine, so I was trying to rename the disk at the same time it's being
created.

I'll delete all the "if ($ovirt_major == 3)" I have in my code. If I have
any problem I'll let you know.

Thank you

On Wed, Jun 28, 2017 at 1:03 PM, Juan Hernández  wrote:

> On 06/28/2017 12:55 PM, Bruno Rodriguez wrote:
> > I'm sorry about bothering you again, but after trying it some times I'm
> > still getting a "500 Internal Server Error". I'm using a REST client
> > instead of CURL and I tried adding a "Version: 3" to headers and used
> > the URL with the v3 as well.
> >
> > I'm issuing a PUT of
> >
> > Alias_for_disk
> >
> > To the URL
> >
> > https://myserver/ovirt-engine/api/v3/vms/62498f51-0203-48b9-
> 83c8-4c6f3bdfe05c/disks/583ed952-46a8-4bc5-8a27-8660e4a24ea2
> >
> > I mean, I can live without it but we are using oVirt as a "static
> > virtualization" environment and is quite useful for us being able to
> > recognize easily each disk by its server name. In case I have to wait
> > until the 4.2 API version to automatize this I'll do :(
> >
>
> That should work. Can you please check if you get any useful message in
> /var/log/ovirt-engine/server.log or /var/log/ovirt-engine/engine.log?
>
> >
> >
> > On Wed, Jun 28, 2017 at 11:18 AM, Bruno Rodriguez  > > wrote:
> >
> > Thank you very much !!!
> >
> > I expected I was missing something like that. Thanks again!
> >
> > On Wed, Jun 28, 2017 at 11:12 AM, Juan Hernández
> > > wrote:
> >
> > On 06/28/2017 10:43 AM, Bruno Rodriguez wrote:
> > > Thank you, Daniel
> > >
> > > I tried a PUT with the same XML body, I got a "405 Method Not
> Allowed".
> > > It's quite strange, there must be someting I'm missing
> > >
> >
> > The operation to update a disk will be introduced in version 4
> > of the
> > API with version 4.2 of the engine. Meanwhile the way to update
> > the disk
> > is to use version 3 of the API and the disks sub-collection of
> the
> > virtual machine. That means that if you have a VM with id 123
> > and a disk
> > with id 456 you can send a request like this:
> >
> >   PUT /ovirt-engine/api/v3/vms/123/disks/456
> >
> > With a request body like this:
> >
> >   
> > newalias
> >   
> >
> > Note that you can use the above "v3" prefix in the URL or else
> the
> > "Version: 3" header. A complete example using curl:
> >
> > ---8<---
> > #!/bin/bash -ex
> >
> > url="https://.../ovirt-engine/api;
> > user="admin@internal"
> > password="..."
> > vm_id="..."
> > disk_id="..."
> >
> > curl \
> > --verbose \
> > --cacert "ca.pem" \
> > --header "Version: 3" \
> > --header "Content-Type: application/xml" \
> > --user "${user}:${password}" \
> > --request PUT \
> > --data "
> > 
> >   newalias
> > 
> > " \
> > "${url}/vms/${vm_id}/disks/${disk_id}"
> > --->8---
> >
> > >
> > > On Wed, Jun 28, 2017 at 10:07 AM, Daniel Erez <
> de...@redhat.com 
> > > >> wrote:
> > >
> > > Hi,
> > >
> > > Updating is done using the PUT method.
> > > Please try that with the same XML body.
> > >
> > > Thanks,
> > > Daniel
> > >
> > > On Wed, Jun 28, 2017 at 10:26 AM Bruno Rodriguez <
> br...@pic.es 
> > > >> wrote:
> > >
> > > Hello everyone,
> > >
> > > I'm having some problems about renaming some disks
> (setting a
> > > different alias, name or description) for VMs disks
> created from
> > > a template. When I get this URL
> > >
> > > https://ovirt-manager/ovirt-engine/api/disks/0123
> > 
> > >  > >
> > >
> > > I can see are the methods sparsify, export, move and
> copy. I
> > > tried to POST the following XML to the previous URL
> with no
> > > result (as expected, it won't work)
> > >
> > > 
> > >   my_machine_Disk1
> > > 
> > >
> > > I'm quite sure I'm thinking about it 

[ovirt-users] CVE-2017-1000364

[Fabrice Bacchella]

Distributions like Redhat and Ubuntu issued a buggy patch for CVE-2017-1000364.

http://www.openwall.com/lists/oss-security/2017/06/22/6 


Many applications are affected:
 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1698919 


Did oVirt's team did check it ? Can we safely apply this patch ?___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Unable to rename disks via REST API

[Juan Hernández]

On 06/28/2017 12:55 PM, Bruno Rodriguez wrote:
> I'm sorry about bothering you again, but after trying it some times I'm
> still getting a "500 Internal Server Error". I'm using a REST client
> instead of CURL and I tried adding a "Version: 3" to headers and used
> the URL with the v3 as well.
> 
> I'm issuing a PUT of 
> 
> Alias_for_disk
> 
> To the URL
> 
> https://myserver/ovirt-engine/api/v3/vms/62498f51-0203-48b9-83c8-4c6f3bdfe05c/disks/583ed952-46a8-4bc5-8a27-8660e4a24ea2
> 
> I mean, I can live without it but we are using oVirt as a "static
> virtualization" environment and is quite useful for us being able to
> recognize easily each disk by its server name. In case I have to wait
> until the 4.2 API version to automatize this I'll do :(
> 

That should work. Can you please check if you get any useful message in
/var/log/ovirt-engine/server.log or /var/log/ovirt-engine/engine.log?

> 
> 
> On Wed, Jun 28, 2017 at 11:18 AM, Bruno Rodriguez  > wrote:
> 
> Thank you very much !!!
> 
> I expected I was missing something like that. Thanks again!
> 
> On Wed, Jun 28, 2017 at 11:12 AM, Juan Hernández
> > wrote:
> 
> On 06/28/2017 10:43 AM, Bruno Rodriguez wrote:
> > Thank you, Daniel
> >
> > I tried a PUT with the same XML body, I got a "405 Method Not 
> Allowed".
> > It's quite strange, there must be someting I'm missing
> >
> 
> The operation to update a disk will be introduced in version 4
> of the
> API with version 4.2 of the engine. Meanwhile the way to update
> the disk
> is to use version 3 of the API and the disks sub-collection of the
> virtual machine. That means that if you have a VM with id 123
> and a disk
> with id 456 you can send a request like this:
> 
>   PUT /ovirt-engine/api/v3/vms/123/disks/456
> 
> With a request body like this:
> 
>   
> newalias
>   
> 
> Note that you can use the above "v3" prefix in the URL or else the
> "Version: 3" header. A complete example using curl:
> 
> ---8<---
> #!/bin/bash -ex
> 
> url="https://.../ovirt-engine/api;
> user="admin@internal"
> password="..."
> vm_id="..."
> disk_id="..."
> 
> curl \
> --verbose \
> --cacert "ca.pem" \
> --header "Version: 3" \
> --header "Content-Type: application/xml" \
> --user "${user}:${password}" \
> --request PUT \
> --data "
> 
>   newalias
> 
> " \
> "${url}/vms/${vm_id}/disks/${disk_id}"
> --->8---
> 
> >
> > On Wed, Jun 28, 2017 at 10:07 AM, Daniel Erez  
> > >> wrote:
> >
> > Hi,
> >
> > Updating is done using the PUT method.
> > Please try that with the same XML body.
> >
> > Thanks,
> > Daniel
> >
> > On Wed, Jun 28, 2017 at 10:26 AM Bruno Rodriguez  
> > >> wrote:
> >
> > Hello everyone,
> >
> > I'm having some problems about renaming some disks (setting 
> a
> > different alias, name or description) for VMs disks created 
> from
> > a template. When I get this URL
> >
> > https://ovirt-manager/ovirt-engine/api/disks/0123
> 
> >  >
> >
> > I can see are the methods sparsify, export, move and copy. I
> > tried to POST the following XML to the previous URL with no
> > result (as expected, it won't work)
> >
> > 
> >   my_machine_Disk1
> > 
> >
> > I'm quite sure I'm thinking about it in a wrong way (as 
> usual).
> > Any help would be welcome...
> >
> > Thank you in advance
> >
> > --
> > Bruno Rodríguez Rodríguez
> >
> > *Port d'Informació Científica (PIC)*
> >
> > ___
> > Users mailing list
> > Users@ovirt.org 
> >
> > http://lists.ovirt.org/mailman/listinfo/users
> 
> > 

Re: [ovirt-users] Unable to rename disks via REST API

[Bruno Rodriguez]

I'm sorry about bothering you again, but after trying it some times I'm
still getting a "500 Internal Server Error". I'm using a REST client
instead of CURL and I tried adding a "Version: 3" to headers and used the
URL with the v3 as well.

I'm issuing a PUT of

Alias_for_disk

To the URL

https://myserver/ovirt-engine/api/v3/vms/62498f51-0203-48b9-83c8-4c6f3bdfe05c/disks/583ed952-46a8-4bc5-8a27-8660e4a24ea2

I mean, I can live without it but we are using oVirt as a "static
virtualization" environment and is quite useful for us being able to
recognize easily each disk by its server name. In case I have to wait until
the 4.2 API version to automatize this I'll do :(



On Wed, Jun 28, 2017 at 11:18 AM, Bruno Rodriguez  wrote:

> Thank you very much !!!
>
> I expected I was missing something like that. Thanks again!
>
> On Wed, Jun 28, 2017 at 11:12 AM, Juan Hernández 
> wrote:
>
>> On 06/28/2017 10:43 AM, Bruno Rodriguez wrote:
>> > Thank you, Daniel
>> >
>> > I tried a PUT with the same XML body, I got a "405 Method Not Allowed".
>> > It's quite strange, there must be someting I'm missing
>> >
>>
>> The operation to update a disk will be introduced in version 4 of the
>> API with version 4.2 of the engine. Meanwhile the way to update the disk
>> is to use version 3 of the API and the disks sub-collection of the
>> virtual machine. That means that if you have a VM with id 123 and a disk
>> with id 456 you can send a request like this:
>>
>>   PUT /ovirt-engine/api/v3/vms/123/disks/456
>>
>> With a request body like this:
>>
>>   
>> newalias
>>   
>>
>> Note that you can use the above "v3" prefix in the URL or else the
>> "Version: 3" header. A complete example using curl:
>>
>> ---8<---
>> #!/bin/bash -ex
>>
>> url="https://.../ovirt-engine/api;
>> user="admin@internal"
>> password="..."
>> vm_id="..."
>> disk_id="..."
>>
>> curl \
>> --verbose \
>> --cacert "ca.pem" \
>> --header "Version: 3" \
>> --header "Content-Type: application/xml" \
>> --user "${user}:${password}" \
>> --request PUT \
>> --data "
>> 
>>   newalias
>> 
>> " \
>> "${url}/vms/${vm_id}/disks/${disk_id}"
>> --->8---
>>
>> >
>> > On Wed, Jun 28, 2017 at 10:07 AM, Daniel Erez > > > wrote:
>> >
>> > Hi,
>> >
>> > Updating is done using the PUT method.
>> > Please try that with the same XML body.
>> >
>> > Thanks,
>> > Daniel
>> >
>> > On Wed, Jun 28, 2017 at 10:26 AM Bruno Rodriguez > > > wrote:
>> >
>> > Hello everyone,
>> >
>> > I'm having some problems about renaming some disks (setting a
>> > different alias, name or description) for VMs disks created from
>> > a template. When I get this URL
>> >
>> > https://ovirt-manager/ovirt-engine/api/disks/0123
>> > 
>> >
>> > I can see are the methods sparsify, export, move and copy. I
>> > tried to POST the following XML to the previous URL with no
>> > result (as expected, it won't work)
>> >
>> > 
>> >   my_machine_Disk1
>> > 
>> >
>> > I'm quite sure I'm thinking about it in a wrong way (as usual).
>> > Any help would be welcome...
>> >
>> > Thank you in advance
>> >
>> > --
>> > Bruno Rodríguez Rodríguez
>> >
>> > *Port d'Informació Científica (PIC)*
>> >
>> > ___
>> > Users mailing list
>> > Users@ovirt.org 
>> > http://lists.ovirt.org/mailman/listinfo/users
>> > 
>> >
>> >
>> >
>> >
>> > --
>> > Bruno Rodríguez Rodríguez
>> >
>> > *Port d'Informació Científica (PIC)*
>> > Campus UAB - Edificio D,
>> > C / Albareda, s / n
>> > 08193-Bellaterra (Barcelona), España
>> > Telf. +34 93 170 27 30
>> > GPS  coordenadas:  41.500850 2.110628
>> >
>> > "Si algo me ha enseñado el tetris, es que los errores se acumulan y los
>> > triunfos desaparecen"
>> >
>> >
>> > ___
>> > Users mailing list
>> > Users@ovirt.org
>> > http://lists.ovirt.org/mailman/listinfo/users
>> >
>>
>>
>
>
> --
> Bruno Rodríguez Rodríguez
>
> *Port d'Informació Científica (PIC)*
> Campus UAB - Edificio D,
> C / Albareda, s / n
> 08193-Bellaterra (Barcelona), España
> Telf. +34 93 170 27 30
> GPS  coordenadas:  41.500850 2.110628
>
> "Si algo me ha enseñado el tetris, es que los errores se acumulan y los
> triunfos desaparecen"
>



-- 
Bruno Rodríguez Rodríguez

*Port d'Informació Científica (PIC)*
Campus UAB - Edificio D,
C / Albareda, s / n
08193-Bellaterra (Barcelona), España
Telf. +34 93 170 27 30
GPS  coordenadas:  41.500850 2.110628

"Si algo me ha enseñado el tetris, es que los errores se acumulan y los
triunfos desaparecen"
___
Users mailing 

Re: [ovirt-users] Frustration defines the deployment of Hosted Engine

[Sandro Bonazzola]

On Mon, Jun 26, 2017 at 9:15 AM, Yaniv Kaul  wrote:

>
>
> On Mon, Jun 26, 2017 at 1:16 AM, Vinícius Ferrão 
> wrote:
>
>> Hello again,
>>
>> Setting the folder permissions to vdsm:kvm (36:36) done the trick to make
>> NFS work. I wasn't expecting this to work since it does not make sense to
>> me, making a parallel with the iSCSI problem.
>>
>> I'm starting to believe that's something just bad. Perhaps the Storage
>> system is running with something broken or the host machine is just
>> unstable.
>>
>> I will consider this as solved, since further inside the oVirt Engine
>> panel I was able to mount and use the same iSCSI sharing.
>>
>> But let me ask for sincere answers here:
>>
>> 1. oVirt is feature complete comparing to RHEV?
>>
>
> Yes. In fact it may have additional features unavailable in RHV.
>
>
>>
>> 2. Should I migrate from XenServer to oVirt? This is biased, I know, but
>> I would like to hear opinions. The folks with @redhat.com email
>> addresses will know how to advocate in favor of oVirt.
>>
>
> I don't know, and I don't think (having a @redhat.com email myself) I
> should advocate.
> If someone made a comparison (even if it's just for their own specific use
> case), it could be great if it could be shared. If you do - please share
> your thoughts.
>
>
>>
>> 3. Some "journalists" says that oVirt is like Fedora in comparison to
>> RHEL, is this really true? Or it's more aligned with a CentOS-like release?
>> Because Fedora isn't really an Enterprise OS, and I was looking for an
>> Enterprise Hypervisor. I'm aware that oVirt is the upstream from RHEV.
>>
>
> I'd cautiously say 'in between'. We strive to ensure oVirt is stable, and
> I believe we make good progress in every release.
> We also make an effort to quickly release fixes (minor releases). That
> being said, RHV has a longer life cycle, and for example, when oVirt
> stopped releasing oVirt 3.6.x, Red Hat continued to release minor versions
> of it.
>
> We have hundreds of oVirt users running it in production, many in large
> scale, with mission critical workloads.
>

And probably not surprisingly, oVirt is running oVirt in production:
https://engine-phx.ovirt.org/ovirt-engine/
for all the oVirt Ci infrastructure (13 hosts, 200 VMs).


>
> Lastly, oVirt  enables features in upstream before they are delivered in
> RHV.
>
> (That being said, I've had a very good experience with Fedora 24 which was
> rock solid for me, then I've had some misfortune with Fedora 25, and now
> I'm assessing if I should upgrade to F26 beta...)
>

For what it's worth, I'm on Fedora 26 since April 14th and works like a
charm for me.



>
>
>> 4. There is any good SPICE client for macOS? Or should I just use the
>> HTML5 version instead?
>>
>
> I'm afraid not.
> Y.
>
>
>>
>> Thanks,
>> V.
>>
>> Sent from my iPhone
>>
>> On 23 Jun 2017, at 18:50, Yaniv Kaul  wrote:
>>
>>
>>
>> On Sat, Jun 24, 2017 at 12:23 AM, Vinícius Ferrão 
>> wrote:
>>
>>> Hello Adam and Karli,
>>>
>>> I will remap uid and gid of NFS to 36 and try again with NFS sharing.
>>>
>>> But this does not make much sense, because on iSCSI this should not
>>> happen. There are no permissions involved and when oVirt runs the
>>> hosted-engine setup it creates the ext3 filesystem on the iSCSI share
>>> without any issue. Here’s a photo of the network bandwidth during the OVF
>>> deployment: http://www.if.ufrj.br/~ferrao/ovirt/bandwidth-iscsi-ovf.jpg
>>>
>>> So it’s appears to be working. Something happens after the deployment
>>> that brokes the connections and kills vdsm.
>>>
>>
>> Indeed - may be two different issues. Let us know how the NFS works
>> first, then let's try with iSCSI.
>> Y.
>>
>>
>>>
>>> Thanks,
>>> V.
>>>
>>> On 23 Jun 2017, at 17:47, Adam Litke  wrote:
>>>
>>>
>>>
>>> On Fri, Jun 23, 2017 at 4:40 PM, Karli Sjöberg 
>>> wrote:
>>>


 Den 23 juni 2017 21:08 skrev Vinícius Ferrão :

 Hello oVirt folks.

 I’m a traitor of the Xen movement and was looking for some good
 alternatives for XenServer hypervisors. I was aware of KVM for a long time
 but I was missing a more professional and appliance feeling of the product,
 and oVirt appears to deliver exactly what I’m looking for.

 Don’t get me wrong, I’m not saying that Xen is not good, I’m looking
 for equal or better alternatives, but I’m starting to get frustrated with
 oVirt.

 Firstly I’ve tried to install the oVirt Node on a VM in VMware Fusion
 on my notebook, it was a no go. For whatever reasons I don’t know
 vdsmd.service and libvirtd failed to start. I make sure that I was running
 with EPT support enabled to achieve nested virtualization, but as I said:
 it was a no go.

 So I’ve decommissioned a XenServer machine that was in production just
 to try oVirt. The hardware is not new, but’s it’s very capable: 

Re: [ovirt-users] HostedEngine VM not visible, but running

[cmc]

Hi Martin,

yes, on two of the machines they have the same host_id. The other has
a different host_id.

To update since yesterday: I reinstalled and deployed Hosted Engine on
the other host (so all three hosts in the cluster now have it
installed). The second one I deployed said it was able to host the
engine (unlike the first I reinstalled), so I tried putting the host
with the Hosted Engine on it into maintenance to see if it would
migrate over. It managed to move all hosts but the Hosted Engine. And
now the host that said it was able to host the engine says
'unavailable due to HA score'. The host that it was trying to move
from is now in 'preparing for maintenance' for the last 12 hours.

The summary is:

kvm-ldn-01 - one of the original, pre-Hosted Engine hosts, reinstalled
with 'Deploy Hosted Engine'. No icon saying it can host the Hosted
Hngine, host_id of '2' in /etc/ovirt-hosted-engine/hosted-engine.conf.
'add_lockspace' fails in sanlock.log

kvm-ldn-02 - the other host that was pre-existing before Hosted Engine
was created. Reinstalled with 'Deploy Hosted Engine'. Had an icon
saying that it was able to host the Hosted Engine, but after migration
was attempted when putting kvm-ldn-03 into maintenance, it reports:
'unavailable due to HA score'. It has a host_id of '1' in
/etc/ovirt-hosted-engine/hosted-engine.conf. No errors in sanlock.log

kvm-ldn-03 - this was the host I deployed Hosted Engine on, which was
not part of the original cluster. I restored the bare-metal engine
backup in the Hosted Engine on this host when deploying it, without
error. It currently has the Hosted Engine on it (as the only VM after
I put that host into maintenance to test the HA of Hosted Engine).
Sanlock log shows conflicts

I will look through all the logs for any other errors. Please let me
know if you need any logs or other clarification/information.

Thanks,

Campbell

On Wed, Jun 28, 2017 at 9:25 AM, Martin Sivak  wrote:
> Hi,
>
> can you please check the contents of
> /etc/ovirt-hosted-engine/hosted-engine.conf or
> /etc/ovirt-hosted-engine-ha/agent.conf (I am not sure which one it is
> right now) and search for host-id?
>
> Make sure the IDs are different. If they are not, then there is a bug 
> somewhere.
>
> Martin
>
> On Tue, Jun 27, 2017 at 6:26 PM, cmc  wrote:
>> I see this on the host it is trying to migrate in /var/log/sanlock:
>>
>> 2017-06-27 17:10:40+0100 527703 [2407]: s3528 lockspace
>> 207221b2-959b-426b-b945-18e1adfed62f:1:/dev/207221b2-959b-426b-b945-18e1adfed62f/ids:0
>> 2017-06-27 17:13:00+0100 527843 [27446]: s3528 delta_acquire host_id 1
>> busy1 1 2 1042692 3d4ec963-8486-43a2-a7d9-afa82508f89f.kvm-ldn-03
>> 2017-06-27 17:13:01+0100 527844 [2407]: s3528 add_lockspace fail result -262
>>
>> The sanlock service is running. Why would this occur?
>>
>> Thanks,
>>
>> C
>>
>> On Tue, Jun 27, 2017 at 5:21 PM, cmc  wrote:
>>> Hi Martin,
>>>
>>> Thanks for the reply. I have done this, and the deployment completed
>>> without error. However, it still will not allow the Hosted Engine
>>> migrate to another host. The
>>> /etc/ovirt-hosted-engine/hosted-engine.conf got created ok on the host
>>> I re-installed, but the ovirt-ha-broker.service, though it starts,
>>> reports:
>>>
>>> 8<---
>>>
>>> Jun 27 14:58:26 kvm-ldn-01 systemd[1]: Starting oVirt Hosted Engine
>>> High Availability Communications Broker...
>>> Jun 27 14:58:27 kvm-ldn-01 ovirt-ha-broker[6101]: ovirt-ha-broker
>>> ovirt_hosted_engine_ha.broker.storage_broker.StorageBroker ERROR
>>> Failed to read metadata from
>>> /rhev/data-center/mnt/blockSD/207221b2-959b-426b-b945-18e1adfed62f/ha_agent/hosted-engine.metadata
>>>   Traceback (most
>>> recent call last):
>>> File
>>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/broker/storage_broker.py",
>>> line 129, in get_raw_stats_for_service_type
>>>   f =
>>> os.open(path, direct_flag | os.O_RDONLY | os.O_SYNC)
>>>   OSError: [Errno 2]
>>> No such file or directory:
>>> '/rhev/data-center/mnt/blockSD/207221b2-959b-426b-b945-18e1adfed62f/ha_agent/hosted-engine.metadata'
>>>
>>> 8<---
>>>
>>> I checked the path, and it exists. I can run 'less -f' on it fine. The
>>> perms are slightly different on the host that is running the VM vs the
>>> one that is reporting errors (600 vs 660), ownership is vdsm:qemu. Is
>>> this a san locking issue?
>>>
>>> Thanks for any help,
>>>
>>> Cam
>>>
>>> On Tue, Jun 27, 2017 at 1:41 PM, Martin Sivak  wrote:
> Should it be? It was not in the instructions for the migration from
> bare-metal to Hosted VM

 The hosted engine will only migrate to hosts that have the services
 running. Please put one 

Re: [ovirt-users] vm shutdown long delay is a problem for users of pools

[Paul]

Hi Sharon,

Thanks for your comments. My findings on those:

1.   Yes all VMs have ovirt-guest-agent installed and active, shutdown time 
is still about 90 seconds. Any other way to reduce this? I see in the logs “Jun 
28 11:49:03 pool python: Shutdown scheduled for Wed 2017-06-28 11:50:03 CEST, 
use 'shutdown -c' to cancel.” And then a wait of 60 seconds. Is it possible to 
adjust this delay?

2.   Clicking twice works. Thanks for the tip!

3.

a.   More VMs per user: yes, could be a good option

b.  I have some trouble with the “console disconnect action” and filed a 
bug for it last week [1]. Any disconnect action (except shutdown) combined with 
“strict user checking” (security wise recommended) blocks and depletes pool 
resources and in my opinion jeopardizes the pool functionality. I am curious 
what your thoughts are on this.

Kind regards,

Paul

[1]: https://bugzilla.redhat.com/show_bug.cgi?id=1464396

 

From: Sharon Gratch [mailto:sgra...@redhat.com] 
Sent: dinsdag 27 juni 2017 19:04
To: Paul 
Cc: users 
Subject: Re: [ovirt-users] vm shutdown long delay is a problem for users of 
pools

 

Hi,

Please see comments below.

 

On Thu, Jun 22, 2017 at 7:15 PM, Paul  > 
wrote:

Hi,

Shutting down VM’s in the portal with the red downfacing arrow takes quite some 
time (about 90 seconds). I read this is mainly due to a 60 second delay in the 
ovirt-guest-agent. I got used to right-click and use “power off” instead of 
“shutdown”, which is fine.

 

My users make use of VM in a VM-pool. They get assigned a VM and after console 
disconnect the VM shuts down (default recommended behavior). My issue is that 
the users stays assigned to this VM for the full 90 seconds and cannot do 
“power off”. Suppose he disconnected by accident, he has to wait 90 seconds 
until he is assigned to the pool again until he can connect to another VM. 

 

My questions are:

-  Is it possible to decrease the time delay of a VM shutdown? 90 
seconds is quite a lot, 10 seconds should be enough

​​

​Is ovirt-guest-agent installed on all pool's VMs? Consider installing 
ovirt-guest-agent in all VMs in your Pool to decrease the time taken for the VM 
shutdown. 

 

-  Is it possible for normal users to use “power off”?

​There is no option in UserPortal to power-off a VM but you can 

​try to click twice (sequential clicks) on the 'shutdown' button. Two 
sequential shutdown requests are handled in oVirt as "power off".

-  Is it possible to “unallocate” the user from a VM if it is powering 
down? So he can allocate another VM

​You can consider assigning two VMs per each user, if possible of-course (via 
WebAdmin->edit Pool -> and set "Maximum number of VMs per user" field to "2") 
so that way while one VM is still shutting down, the user can switch and 
connect to a second VM without waiting.

Another option is to create a pool with a different policy for console 
disconnecting so that the VM won't shutdown each time the user close the  
console (via WebAdmin->Pool->Console tab->"Console Disconnect Action"). 
Consider changing this field to "Lock screen" or "Logout user" instead of 
"shutdown virtual machine". 
This policy will avoid accidentally console disconnection waiting each 
time...but on the other hand the VM state will remain as is since no shutdown 
occurs, so it really depends on your requirements.

Regards,

Sharon

 

Kind regards,

 

Paul


___
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] Moving thin provisioned disks question

[Gianluca Cecchi]

On Wed, Jun 28, 2017 at 8:48 AM, Fred Rolland  wrote:

> Hi,
>
> The qemu operation progress is parsed [1] and is printed on debug level in
> Vdsm log [2].
>

Where should I see this information: vdsm.log ?

It seems I see nothing. Could it depend on settings in
 /etc/vdsm/logger.conf ?
Which part of this file in case would rule the presence of the log messages
related to move progress?

In the UI, a progress indication of the operation is available on the disks
> status for the "Move Disk" operation.
> Currently only for this operation.
>
>
I have not understood.
In all parts in te gui where there is a disk section  only see "Locked" in
status

eg

Disks -> the line with the moving disk presents "Locked"
Virtual Machines -> select my vm -> Disks -> select the moving disk, it
contains "Locked"
Virtual Machines -> select my vm -> Snapshots -> Disks, it presents "Locked"

Version is 4.1.1

Thanks


Gianluca

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

[ovirt-users] Fwd: Windows USB Redirection

[Abi Askushi]

Hi All,

I have Ovirt 4.1 with 3 nodes on top glusterfs.

I Have 2 VMs: Windows 2016 64bit and Windows 10 64bit

When I attach a USB flash disk to a VM (from host devices) the VM cannot
see the USB drive and report driver issue at device manager (see attached).
This happens with both VMs when tested.

When testing with Windows 7 or Windows XP USB is attached and accessed
normally.
Have you encountered such issue?
I have installed latest guest tools on both VMs.

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

Re: [ovirt-users] Unable to rename disks via REST API

[Bruno Rodriguez]

Thank you very much !!!

I expected I was missing something like that. Thanks again!

On Wed, Jun 28, 2017 at 11:12 AM, Juan Hernández 
wrote:

> On 06/28/2017 10:43 AM, Bruno Rodriguez wrote:
> > Thank you, Daniel
> >
> > I tried a PUT with the same XML body, I got a "405 Method Not Allowed".
> > It's quite strange, there must be someting I'm missing
> >
>
> The operation to update a disk will be introduced in version 4 of the
> API with version 4.2 of the engine. Meanwhile the way to update the disk
> is to use version 3 of the API and the disks sub-collection of the
> virtual machine. That means that if you have a VM with id 123 and a disk
> with id 456 you can send a request like this:
>
>   PUT /ovirt-engine/api/v3/vms/123/disks/456
>
> With a request body like this:
>
>   
> newalias
>   
>
> Note that you can use the above "v3" prefix in the URL or else the
> "Version: 3" header. A complete example using curl:
>
> ---8<---
> #!/bin/bash -ex
>
> url="https://.../ovirt-engine/api;
> user="admin@internal"
> password="..."
> vm_id="..."
> disk_id="..."
>
> curl \
> --verbose \
> --cacert "ca.pem" \
> --header "Version: 3" \
> --header "Content-Type: application/xml" \
> --user "${user}:${password}" \
> --request PUT \
> --data "
> 
>   newalias
> 
> " \
> "${url}/vms/${vm_id}/disks/${disk_id}"
> --->8---
>
> >
> > On Wed, Jun 28, 2017 at 10:07 AM, Daniel Erez  > > wrote:
> >
> > Hi,
> >
> > Updating is done using the PUT method.
> > Please try that with the same XML body.
> >
> > Thanks,
> > Daniel
> >
> > On Wed, Jun 28, 2017 at 10:26 AM Bruno Rodriguez  > > wrote:
> >
> > Hello everyone,
> >
> > I'm having some problems about renaming some disks (setting a
> > different alias, name or description) for VMs disks created from
> > a template. When I get this URL
> >
> > https://ovirt-manager/ovirt-engine/api/disks/0123
> > 
> >
> > I can see are the methods sparsify, export, move and copy. I
> > tried to POST the following XML to the previous URL with no
> > result (as expected, it won't work)
> >
> > 
> >   my_machine_Disk1
> > 
> >
> > I'm quite sure I'm thinking about it in a wrong way (as usual).
> > Any help would be welcome...
> >
> > Thank you in advance
> >
> > --
> > Bruno Rodríguez Rodríguez
> >
> > *Port d'Informació Científica (PIC)*
> >
> > ___
> > Users mailing list
> > Users@ovirt.org 
> > http://lists.ovirt.org/mailman/listinfo/users
> > 
> >
> >
> >
> >
> > --
> > Bruno Rodríguez Rodríguez
> >
> > *Port d'Informació Científica (PIC)*
> > Campus UAB - Edificio D,
> > C / Albareda, s / n
> > 08193-Bellaterra (Barcelona), España
> > Telf. +34 93 170 27 30
> > GPS  coordenadas:  41.500850 2.110628
> >
> > "Si algo me ha enseñado el tetris, es que los errores se acumulan y los
> > triunfos desaparecen"
> >
> >
> > ___
> > Users mailing list
> > Users@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/users
> >
>
>


-- 
Bruno Rodríguez Rodríguez

*Port d'Informació Científica (PIC)*
Campus UAB - Edificio D,
C / Albareda, s / n
08193-Bellaterra (Barcelona), España
Telf. +34 93 170 27 30
GPS  coordenadas:  41.500850 2.110628

"Si algo me ha enseñado el tetris, es que los errores se acumulan y los
triunfos desaparecen"
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Unable to rename disks via REST API

[Juan Hernández]

On 06/28/2017 10:43 AM, Bruno Rodriguez wrote:
> Thank you, Daniel
> 
> I tried a PUT with the same XML body, I got a "405 Method Not Allowed".
> It's quite strange, there must be someting I'm missing
> 

The operation to update a disk will be introduced in version 4 of the
API with version 4.2 of the engine. Meanwhile the way to update the disk
is to use version 3 of the API and the disks sub-collection of the
virtual machine. That means that if you have a VM with id 123 and a disk
with id 456 you can send a request like this:

  PUT /ovirt-engine/api/v3/vms/123/disks/456

With a request body like this:

  
newalias
  

Note that you can use the above "v3" prefix in the URL or else the
"Version: 3" header. A complete example using curl:

---8<---
#!/bin/bash -ex

url="https://.../ovirt-engine/api;
user="admin@internal"
password="..."
vm_id="..."
disk_id="..."

curl \
--verbose \
--cacert "ca.pem" \
--header "Version: 3" \
--header "Content-Type: application/xml" \
--user "${user}:${password}" \
--request PUT \
--data "

  newalias

" \
"${url}/vms/${vm_id}/disks/${disk_id}"
--->8---

> 
> On Wed, Jun 28, 2017 at 10:07 AM, Daniel Erez  > wrote:
> 
> Hi,
> 
> Updating is done using the PUT method.
> Please try that with the same XML body.
> 
> Thanks,
> Daniel
> 
> On Wed, Jun 28, 2017 at 10:26 AM Bruno Rodriguez  > wrote:
> 
> Hello everyone,
> 
> I'm having some problems about renaming some disks (setting a
> different alias, name or description) for VMs disks created from
> a template. When I get this URL
> 
> https://ovirt-manager/ovirt-engine/api/disks/0123
> 
> 
> I can see are the methods sparsify, export, move and copy. I
> tried to POST the following XML to the previous URL with no
> result (as expected, it won't work)
> 
> 
>   my_machine_Disk1
> 
> 
> I'm quite sure I'm thinking about it in a wrong way (as usual).
> Any help would be welcome...
> 
> Thank you in advance
> 
> -- 
> Bruno Rodríguez Rodríguez
> 
> *Port d'Informació Científica (PIC)* 
> 
> ___
> Users mailing list
> Users@ovirt.org 
> http://lists.ovirt.org/mailman/listinfo/users
> 
> 
> 
> 
> 
> -- 
> Bruno Rodríguez Rodríguez
> 
> *Port d'Informació Científica (PIC)* 
> Campus UAB - Edificio D,
> C / Albareda, s / n 
> 08193-Bellaterra (Barcelona), España
> Telf. +34 93 170 27 30
> GPS  coordenadas:  41.500850 2.110628
> 
> "Si algo me ha enseñado el tetris, es que los errores se acumulan y los
> triunfos desaparecen"
> 
> 
> ___
> 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] hosted-engine network

[Evgenia Tokar]

Yes, you can try that.



On Tue, Jun 27, 2017 at 5:03 PM, Arsène Gschwind 
wrote:

> Would re-deploying the hosted-engine and restoring the backup be an option?
>
> Thanks a lot for your help
>
> Rgds,
> Arsène
>
> On 06/27/2017 03:15 PM, Evgenia Tokar wrote:
>
> The set-shared-config does not allow editing of the vm.conf or the ovf.
>
> The original vm.conf that the hosted engine vm was started with contains
> the correct network, so it must have been removed at a later stage.
>
> To get a working environment I don't see another option then fixing the
> network in the db.
> What do the following queries return:
>   1. select vm_interface.vm_guid, vnic_profile_id from vm_interface,
> vm_static where vm_name='HostedEngine';
>   2. select id from vnic_profiles where name='ovirtmgmt';
> The vnic profile id that is returned from the first query should be the
> same as the one that has the ovirtmgmt name in the second query.
>
> Thanks,
> Jenny
>
>
>
> Jenny Tokar
>
>
> On Thu, Jun 22, 2017 at 2:53 PM, Yedidyah Bar David 
> wrote:
>
>> On Thu, Jun 22, 2017 at 2:32 PM, Yanir Quinn  wrote:
>> > Adding Didi,
>> > Didi, do you happen to know of scenarios where we use the migration
>> scripts
>> > and the nic in the OVF is gone missing ?  (maybe after the restore
>> stage)
>>
>> I do not think I understand the question.
>>
>> Migration from standalone to hosted-engine does not involve a nic
>> in an ovf, AFAIU.
>>
>> To get/set stuff on the shared storage, hosted-engine has options
>> '--{get,set}-shared-config', see also:
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1301681
>>
>> For the engine vm.conf, indeed it's updated from data in the engine
>> db, but I do not know well the details. Adding Simone.
>>
>> >
>> > Regards,
>> > Yanir
>> >
>> > On Wed, Jun 21, 2017 at 12:02 PM, Arsène Gschwind
>> >  wrote:
>> >>
>> >> Hi Yanir,
>> >>
>> >> We had our oVirt Engine running on a HW server so we decided to move
>> it to
>> >> hosted-engine. For this I've followed the Howto at
>> >> http://www.ovirt.org/documentation/self-hosted/chap-
>> Migrating_from_Bare_Metal_to_an_EL-Based_Self-Hosted_Environment/.
>> >>
>> >> The Hosted-Storage is located on a FC SAN LUN.
>> >>
>> >> Please find attached the setup log.
>> >>
>> >> Tanks a lot.
>> >>
>> >> Regards,
>> >> Arsène
>> >>
>> >>
>> >> On 06/21/2017 10:14 AM, Yanir Quinn wrote:
>> >>
>> >> HI Arsene
>> >>
>> >> Just to be clear, can you write down the steps to reproduce ? (the
>> >> migration procedure . and if possible the state before and after)
>> >>
>> >> Thanks
>> >>
>> >> On Mon, Jun 19, 2017 at 8:34 PM, Arsène Gschwind
>> >>  wrote:
>> >>>
>> >>> Hi Jenny,
>> >>>
>> >>> Thanks for the explanations..
>> >>>
>> >>> Please find vm.conf attached, it looks like the ovirtmgmt network is
>> >>> defined
>> >>>
>> >>> Regards,
>> >>> Arsène
>> >>>
>> >>>
>> >>> On 06/19/2017 01:46 PM, Evgenia Tokar wrote:
>> >>>
>> >>> Hi,
>> >>>
>> >>> It should be in one of the directories on your storage domain:
>> >>> /cd1f6775-61e9-4d04-b41c-c64925d5a905/images//
>> >>>
>> >>> To see which one you can run the following command:
>> >>>
>> >>> vdsm-client Volume getInfo volumeID= imageID=
>> >>> storagedomainID= storagepoolID=
>> >>>
>> >>> the storage domain id is: cd1f6775-61e9-4d04-b41c-c64925d5a905
>> >>> the storage pool id can be found using: vdsm-client StorageDomain
>> getInfo
>> >>> storagedomainID=cd1f6775-61e9-4d04-b41c-c64925d5a905
>> >>>
>> >>> The volume that has "description": "HostedEngineConfigurationImage"
>> is
>> >>> the one you are looking for.
>> >>> Untar it and it should contain the original vm.conf which was used to
>> >>> start the hosted engine.
>> >>>
>> >>> Jenny Tokar
>> >>>
>> >>>
>> >>> On Mon, Jun 19, 2017 at 12:59 PM, Arsène Gschwind
>> >>>  wrote:
>> 
>>  Hi Jenny,
>> 
>>  1. I couldn't locate any tar file containing vm.conf, do you know the
>>  exact place where it is stored?
>> 
>>  2. The ovirtmgmt appears in the network dropdown but I'm not able to
>>  change since it complains about locked values.
>> 
>>  Thanks a lot for your help.
>> 
>>  Regards,
>>  Arsène
>> 
>> 
>> 
>>  On 06/14/2017 01:26 PM, Evgenia Tokar wrote:
>> 
>>  Hi Arseny,
>> 
>>  Looking at the log the ovf doesn't contain the ovirtmgmt network.
>> 
>>  1. Can you provide the original vm.conf file the engine was started
>>  with? It is located in a tar archive on your storage domain.
>>  2. It's uncelar from the screenshot, in the network dropdown do you
>> have
>>  an option to add a ovirtmgmt network?
>> 
>>  Thanks,
>>  Jenny
>> 
>> 
>>  On Tue, Jun 13, 2017 at 11:19 AM, Arsène Gschwind
>>   wrote:
>> >
>> > Sorry for that, I haven't checked.
>> >
>> > 

Re: [ovirt-users] Unable to rename disks via REST API

[Bruno Rodriguez]

Thank you, Daniel

I tried a PUT with the same XML body, I got a "405 Method Not Allowed".
It's quite strange, there must be someting I'm missing



On Wed, Jun 28, 2017 at 10:07 AM, Daniel Erez  wrote:

> Hi,
>
> Updating is done using the PUT method.
> Please try that with the same XML body.
>
> Thanks,
> Daniel
>
> On Wed, Jun 28, 2017 at 10:26 AM Bruno Rodriguez  wrote:
>
>> Hello everyone,
>>
>> I'm having some problems about renaming some disks (setting a different
>> alias, name or description) for VMs disks created from a template. When I
>> get this URL
>>
>> https://ovirt-manager/ovirt-engine/api/disks/0123
>>
>> I can see are the methods sparsify, export, move and copy. I tried to
>> POST the following XML to the previous URL with no result (as expected, it
>> won't work)
>>
>> 
>>   my_machine_Disk1
>> 
>>
>> I'm quite sure I'm thinking about it in a wrong way (as usual). Any help
>> would be welcome...
>>
>> Thank you in advance
>>
>> --
>> Bruno Rodríguez Rodríguez
>>
>> *Port d'Informació Científica (PIC)*
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>


-- 
Bruno Rodríguez Rodríguez

*Port d'Informació Científica (PIC)*
Campus UAB - Edificio D,
C / Albareda, s / n
08193-Bellaterra (Barcelona), España
Telf. +34 93 170 27 30
GPS  coordenadas:  41.500850 2.110628

"Si algo me ha enseñado el tetris, es que los errores se acumulan y los
triunfos desaparecen"
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] HostedEngine VM not visible, but running

[Martin Sivak]

Hi,

can you please check the contents of
/etc/ovirt-hosted-engine/hosted-engine.conf or
/etc/ovirt-hosted-engine-ha/agent.conf (I am not sure which one it is
right now) and search for host-id?

Make sure the IDs are different. If they are not, then there is a bug somewhere.

Martin

On Tue, Jun 27, 2017 at 6:26 PM, cmc  wrote:
> I see this on the host it is trying to migrate in /var/log/sanlock:
>
> 2017-06-27 17:10:40+0100 527703 [2407]: s3528 lockspace
> 207221b2-959b-426b-b945-18e1adfed62f:1:/dev/207221b2-959b-426b-b945-18e1adfed62f/ids:0
> 2017-06-27 17:13:00+0100 527843 [27446]: s3528 delta_acquire host_id 1
> busy1 1 2 1042692 3d4ec963-8486-43a2-a7d9-afa82508f89f.kvm-ldn-03
> 2017-06-27 17:13:01+0100 527844 [2407]: s3528 add_lockspace fail result -262
>
> The sanlock service is running. Why would this occur?
>
> Thanks,
>
> C
>
> On Tue, Jun 27, 2017 at 5:21 PM, cmc  wrote:
>> Hi Martin,
>>
>> Thanks for the reply. I have done this, and the deployment completed
>> without error. However, it still will not allow the Hosted Engine
>> migrate to another host. The
>> /etc/ovirt-hosted-engine/hosted-engine.conf got created ok on the host
>> I re-installed, but the ovirt-ha-broker.service, though it starts,
>> reports:
>>
>> 8<---
>>
>> Jun 27 14:58:26 kvm-ldn-01 systemd[1]: Starting oVirt Hosted Engine
>> High Availability Communications Broker...
>> Jun 27 14:58:27 kvm-ldn-01 ovirt-ha-broker[6101]: ovirt-ha-broker
>> ovirt_hosted_engine_ha.broker.storage_broker.StorageBroker ERROR
>> Failed to read metadata from
>> /rhev/data-center/mnt/blockSD/207221b2-959b-426b-b945-18e1adfed62f/ha_agent/hosted-engine.metadata
>>   Traceback (most
>> recent call last):
>> File
>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/broker/storage_broker.py",
>> line 129, in get_raw_stats_for_service_type
>>   f =
>> os.open(path, direct_flag | os.O_RDONLY | os.O_SYNC)
>>   OSError: [Errno 2]
>> No such file or directory:
>> '/rhev/data-center/mnt/blockSD/207221b2-959b-426b-b945-18e1adfed62f/ha_agent/hosted-engine.metadata'
>>
>> 8<---
>>
>> I checked the path, and it exists. I can run 'less -f' on it fine. The
>> perms are slightly different on the host that is running the VM vs the
>> one that is reporting errors (600 vs 660), ownership is vdsm:qemu. Is
>> this a san locking issue?
>>
>> Thanks for any help,
>>
>> Cam
>>
>> On Tue, Jun 27, 2017 at 1:41 PM, Martin Sivak  wrote:
 Should it be? It was not in the instructions for the migration from
 bare-metal to Hosted VM
>>>
>>> The hosted engine will only migrate to hosts that have the services
>>> running. Please put one other host to maintenance and select Hosted
>>> engine action: DEPLOY in the reinstall dialog.
>>>
>>> Best regards
>>>
>>> Martin Sivak
>>>
>>> On Tue, Jun 27, 2017 at 1:23 PM, cmc  wrote:
 I changed the 'os.other.devices.display.protocols.value.3.6 =
 spice/qxl,vnc/cirrus,vnc/qxl' line to have the same display protocols
 as 4 and the hosted engine now appears in the list of VMs. I am
 guessing the compatibility version was causing it to use the 3.6
 version. However, I am still unable to migrate the engine VM to
 another host. When I try putting the host it is currently on into
 maintenance, it reports:

 Error while executing action: Cannot switch the Host(s) to Maintenance 
 mode.
 There are no available hosts capable of running the engine VM.

 Running 'hosted-engine --vm-status' still shows 'Engine status:
 unknown stale-data'.

 The ovirt-ha-broker service is only running on one host. It was set to
 'disabled' in systemd. It won't start as there is no
 /etc/ovirt-hosted-engine/hosted-engine.conf on the other two hosts.
 Should it be? It was not in the instructions for the migration from
 bare-metal to Hosted VM

 Thanks,

 Cam

 On Thu, Jun 22, 2017 at 1:07 PM, cmc  wrote:
> Hi Tomas,
>
> So in my /usr/share/ovirt-engine/conf/osinfo-defaults.properties on my
> engine VM, I have:
>
> os.other.devices.display.protocols.value = 
> spice/qxl,vnc/vga,vnc/qxl,vnc/cirrus
> os.other.devices.display.protocols.value.3.6 = 
> spice/qxl,vnc/cirrus,vnc/qxl
>
> That seems to match - I assume since this is 4.1, the 3.6 should not apply
>
> Is there somewhere else I should be looking?
>
> Thanks,
>
> Cam
>
> On Thu, Jun 22, 2017 at 11:40 AM, Tomas Jelinek  
> wrote:
>>
>>
>> On Thu, Jun 22, 2017 at 12:38 PM, Michal Skrivanek
>>  wrote:

[ovirt-users] Test Email

[Konstantinos Bonaros]

Sending test email please ignore!
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Unable to rename disks via REST API

[Daniel Erez]

Hi,

Updating is done using the PUT method.
Please try that with the same XML body.

Thanks,
Daniel

On Wed, Jun 28, 2017 at 10:26 AM Bruno Rodriguez  wrote:

> Hello everyone,
>
> I'm having some problems about renaming some disks (setting a different
> alias, name or description) for VMs disks created from a template. When I
> get this URL
>
> https://ovirt-manager/ovirt-engine/api/disks/0123
>
> I can see are the methods sparsify, export, move and copy. I tried to POST
> the following XML to the previous URL with no result (as expected, it won't
> work)
>
> 
>   my_machine_Disk1
> 
>
> I'm quite sure I'm thinking about it in a wrong way (as usual). Any help
> would be welcome...
>
> Thank you in advance
>
> --
> Bruno Rodríguez Rodríguez
>
> *Port d'Informació Científica (PIC)*
>
> ___
> 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] Windows USB Redirection

[Konstantinos Bonaros]

Hi All,

I have Ovirt 4.1 with 3 nodes on top glusterfs, all are running smoothly
except USB redirection.

I Have 2 VMs:

   - Windows 2016 64bit
   - Windows 10 64bit

Although both are able to see USB have attached issue.

On Past when testing on Windows 7 VM USB redirection was running smoothly.

Can i have your suggestion on this issue.

Thank you in advanced.

Regards,
Konstantinos

On Tue, Jun 27, 2017 at 4:27 PM, Konstantinos Bonaros <
bonaros.konstanti...@gmail.com> wrote:

> Hi All,
>
> I have Ovirt 4.1 with 3 nodes on top glusterfs, all are running smoothly
> except USB redirection.
>
> I Have 2 VMs:
>
>- Windows 2016 64bit
>- Windows 10 64bit
>
> Although both are able to see USB have attached issue.
>
> On Past when testing on Windows 7 VM USB redirection was running smoothly.
>
> Can i have your suggestion on this issue.
>
> Thank you in advanced.
>
> Regards,
>
> Konstantinos
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Unable to rename disks via REST API

[Bruno Rodriguez]

Hello everyone,

I'm having some problems about renaming some disks (setting a different
alias, name or description) for VMs disks created from a template. When I
get this URL

https://ovirt-manager/ovirt-engine/api/disks/0123

I can see are the methods sparsify, export, move and copy. I tried to POST
the following XML to the previous URL with no result (as expected, it won't
work)


  my_machine_Disk1


I'm quite sure I'm thinking about it in a wrong way (as usual). Any help
would be welcome...

Thank you in advance

-- 
Bruno Rodríguez Rodríguez

*Port d'Informació Científica (PIC)*
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Ovirt remove network from hosted engine

[Abi Askushi]

Hi,

I was trying to remove the nic from the edit menu of the VM and that failed.

I had to unplug the nic first to be able to remove it from the network
interfaces submenu of the vm.

On Jun 28, 2017 08:29, "knarra"  wrote:

> On 06/27/2017 09:49 PM, Abi Askushi wrote:
>
> Hi all,
>
> Just in case ones needs it, in order to remove the secondary network
> interface from engine, you can go to:
> Virtual Machines -> Hostedengine -> Network Interfaces -> edit -> unplug
> it -> confirm -> remove it.
>
> cool. But in your previous mail you did mention that it fails for you
> since the engine is running. Instead of remove you tried unplug here ?
>
>
> It was simple...
>
>
> On Tue, Jun 27, 2017 at 4:54 PM, Abi Askushi 
> wrote:
>
>> Hi Knarra,
>>
>> Then I had already enabled NFS on ISO gluster volume.
>> Maybe i had some networking issue then. I need to remove the secondary
>> interface in order to test that again.
>>
>>
>>
>> On Tue, Jun 27, 2017 at 4:25 PM, knarra  wrote:
>>
>>> On 06/27/2017 06:34 PM, Abi Askushi wrote:
>>>
>>> Hi Knarra,
>>>
>>> The ISO domain is of type gluster though I had nfs enabled on that
>>> volume.
>>>
>>> you need to have nfs enabled on the volume. what i meant is nfs.disable
>>> off which means nfs is on.
>>>
>>> For more info please refer to bug https://bugzilla.redhat.com/sh
>>> ow_bug.cgi?id=1437799
>>>
>>> I will disable the nfs and try. Though in order to try I need first to
>>> remove that second interface from engine.
>>> Is there a way I can remove the secondary storage network interface from
>>> the engine?
>>>
>>> I am not sure how to do that, but   you may shutdown the vm using the
>>> command hosted-engine --vm-shutdown which will power off the vm and try to
>>> remove the networks using vdsclient. (not sure if this is right, but
>>> suggesting a way)
>>>
>>>
>>> Thanx
>>>
>>>
>>>
>>> On Tue, Jun 27, 2017 at 3:32 PM, knarra  wrote:
>>>
 On 06/27/2017 05:41 PM, Abi Askushi wrote:

 Hi all,

 When setting up hosted engine setup on top gluster with 3 nodes, I had
 gluster configured on a separate network interface, as recommended. When I
 tried later to upload ISO from engine to ISO domain, the engine was not
 able to upload it since the VM did not have access to the separate storage
 network. I then added the storage network interface to the hosted engine
 and ISO upload succeeded.

 May i know what was the volume type created and added as ISO domain ?

 If you plan to use a glusterfs volume below is the procedure :

 1) Create a glusterfs volume.
 2) While adding storage domain select Domain Function as 'ISO' and
 Storage Type as 'glusterfs' .
 3) You can either use 'use managed gluster volume' check box and select
 the gluster volume which you have created for storing ISO's or you can type
 the full path of the volume.
 4) Once this is added please make sure to set the option nfs.disable
 off.
 5) Now you can go to HE engine and run the command engine-iso-uploader
 upload -i  

 Iso gets uploaded successfully.


 1st question: do I need to add the network interface to engine in order
 to upload ISOs? does there exist any alternate way?

 AFAIK, this is not required when glusterfs volume is used.

 Attached is the screenshot where i have only one network attached to my
 HE which is ovirtmgmt.


 Then I proceeded to configure bonding for the storage domain, bonding 2
 NICs at each server. When trying to set a custom bond of mode=6 (as
 recommended from gluster) I received a warning that mode0, 5 and 6 cannot
 be configured since the interface is used from VMs. I also understood that
 having the storage network assigned to VMs makes it a bridge which
 decreases performance of networking. When trying to remove the network
 interface from engine it cannot be done, since the engine is running.

 2nd question: Is there a way I can remove the secondary storage network
 interface from the engine?

 Many thanx


 ___
 Users mailing 
 listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users


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

Re: [ovirt-users] Storage, extend or new lun ?

[Enrico Becchetti Gmail]

 Hi All,
There are other ways to avoid using two lun ? If necessary I can also 
shutdown the entire cluster.

thanks a lot !
Bye
Enrico


Il 26/06/2017 12:32, Fred Rolland ha scritto:

Hi,

The support for refreshing the LUN size in an existing storage domain 
has been introduced in 3.6, so it is not relevant for you.


You can add an additional LUN to an existing storage domain.

Regards,

Fred

[1] 
https://www.ovirt.org/develop/release-management/features/storage/lun-resize/


On Mon, Jun 26, 2017 at 9:35 AM, Enrico Becchetti Gmail 
> wrote:


Dear All,
I've oVirt 3.5.3-1-1.el6 with two kind of storage , NFS and Fibre
Channel.  Each Hypervisor
has HBA controller and Data CLutser has four Storage named:
DATA_FC, DATA_NFS, EXPORT
and ISO-DOMAIN.

Anybody know how can I extend a DATA_FC ? Which is the best practies ?
Extend LUN from HP MSA controller or adding a new lun ?
if I extend lun inside HP MSA oVirt see the new size ?
Enrico
Thanks a lot.
Best Regards

___
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] Moving thin provisioned disks question

[Fred Rolland]

Hi,

The qemu operation progress is parsed [1] and is printed on debug level in
Vdsm log [2].
In the UI, a progress indication of the operation is available on the disks
status for the "Move Disk" operation.
Currently only for this operation.

Regards,

Fred


[1]
https://github.com/oVirt/vdsm/blob/917905d85abb1a24d8beea09f012b81ed594b349/lib/vdsm/qemuimg.py#L280
[2]
https://github.com/oVirt/vdsm/blob/917905d85abb1a24d8beea09f012b81ed594b349/lib/vdsm/qemuimg.py#L332

On Tue, Jun 27, 2017 at 6:50 PM, Gianluca Cecchi 
wrote:

> On Tue, Jun 27, 2017 at 3:09 PM, InterNetX - Juergen Gotteswinter <
> j...@internetx.com> wrote:
>
>>
>> > >
>> > > Suppose I have one 500Gb thin provisioned disk
>> > > Why can I indirectly see that the actual size is 300Gb only in
>> Snapshots
>> > > tab --> Disks of its VM ?
>> >
>> > if you are using live storage migration, ovirt creates a qcow/lvm
>> > snapshot of the vm block device. but for whatever reason, it does
>> NOT
>> > remove the snapshot after the migration has finished. you have to
>> remove
>> > it yourself, otherwise disk usage will grow more and more.
>> >
>> >
>> > I believe you are referring to the "Auto-generated" snapshot created
>> > during live storage migration. This behavior is reported
>> > in https://bugzilla.redhat.com/1317434 and fixed since 4.0.0.
>>
>> yep, thats what i meant. i just wasnt aware of the fact that this isnt
>> the case anymore for 4.x and above. sorry for confusion
>>
>>
> I confirm that the snapshot of the VM, named "Auto-generated for Live
> Storage Migration" has been removed after the disk moving completion.
> Also, for a preallocated disk the "qemu-img convert" has format options
> raw/raw:
>
> [root@ov300 ~]# ps -ef|grep qemu-img
> vdsm 18343  3585  1 12:07 ?00:00:04 /usr/bin/qemu-img convert
> -p -t none -T none -f raw /rhev/data-center/mnt/blockSD/
> 5ed04196-87f1-480e-9fee-9dd450a3b53b/images/303287ad-
> b7ee-40b4-b303-108a5b07c54d/fd408b9c-fdd5-4f72-a73c-332f47868b3c -O raw
> /rhev/data-center/mnt/blockSD/fa33df49-b09d-4f86-9719-
> ede649542c21/images/303287ad-b7ee-40b4-b303-108a5b07c54d/
> fd408b9c-fdd5-4f72-a73c-332f47868b3c
>
>
> for a thin provisioned disk instead it is of the form qcow2/qcow2
> [root@ov300 ~]# ps -ef|grep qemu-img
> vdsm 28545  3585  3 12:49 ?00:00:01 /usr/bin/qemu-img convert
> -p -t none -T none -f qcow2 /rhev/data-center/mnt/blockSD/
> 5ed04196-87f1-480e-9fee-9dd450a3b53b/images/9302dca6-
> 285e-49f7-a64c-68c5c95bdf91/0f3f927d-bb42-479f-ba86-cbd7d4c0fb51 -O qcow2
> -o compat=1.1 /rhev/data-center/mnt/blockSD/fa33df49-b09d-4f86-9719-
> ede649542c21/images/9302dca6-285e-49f7-a64c-68c5c95bdf91/
> 0f3f927d-bb42-479f-ba86-cbd7d4c0fb51
>
>
> BTW: the "-p" option should give
>
>-p  display progress bar (compare, convert and rebase commands
> only).  If the -p option is not used for a
>command that supports it, the progress is reported when the
> process receives a "SIGUSR1" signal.
>
> Is it of any meaning? I don't see any progress bar/information inside the
> gui? Is it perhaps in any other file on filesystem?
>
> Thanks,
> Gianluca
>
> ___
> 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