[ovirt-users] Different link speeds in LACP LAG?

[Chris Adams]

I have a small oVirt setup for one customer, with two servers each
connected to a two-switch stack with 1G links.  Now the customer would
like to upgrade the server links to 10G.  My question is this: can I add
a 10G NIC and do this with minimal "fuss" by just adding the 10G links
to the same LAG, then removing the 1G links?  I would have the host in
maintenance mode no matter what.

I haven't checked the switch to see if it'll support that yet, figured
I'd start on the oVirt side.

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

Re: [ovirt-users] Disk image upload via CLI?

[Nir Soffer]

On Wed, Sep 13, 2017 at 5:03 PM Matthias Leopold <
matthias.leop...@meduniwien.ac.at> wrote:

> i tried it again twice:
>
> when using upload_disk.py from the ovirt engine host itself the disk
> upload succeeds (despite an "503 Service Unavailable Completed 100%" in
> script output in the end)
>
> another try was from an ovirt-sdk installation on my ubuntu desktop
> itself (yesterday i tried it from a centos VM on my desktop machine).
> this failed again, this time with "socket.error: [Errno 32] Broken pipe"
> after reaching "200 OK Completed 100%". in imageio-proxy log i have
> again the 403 error in this moment
>
> what's the difference between accessing the API from the engine host and
> from "outside" in this case?
>

There should be no difference - did you run the same code for uploading?


>
> thx
> matthias
>
> Am 2017-09-12 um 16:42 schrieb Matthias Leopold:
> > Thanks, i tried this script and it _almost_ worked ;-)
> >
> > i uploaded two images i created with
> > qemu-img create -f qcow2 -o preallocation=full
> > and
> > qemu-img create -f qcow2 -o preallocation=falloc
> >
> > for initial_size and provisioned_size i took the value reported by
> > "qemu-img info" in "virtual size" (same as "disk size" in this case)
> >
> > the upload goes to 100% and then fails with
> >
> > 200 OK Completed 100%
> > Traceback (most recent call last):
> >File "./upload_disk.py", line 157, in 
> >  headers=upload_headers,
> >File "/usr/lib64/python2.7/httplib.py", line 1017, in request
> >  self._send_request(method, url, body, headers)
> >File "/usr/lib64/python2.7/httplib.py", line 1051, in _send_request
> >  self.endheaders(body)
> >File "/usr/lib64/python2.7/httplib.py", line 1013, in endheaders
> >  self._send_output(message_body)
> >File "/usr/lib64/python2.7/httplib.py", line 864, in _send_output
> >  self.send(msg)
> >File "/usr/lib64/python2.7/httplib.py", line 840, in send
> >  self.sock.sendall(data)
> >File "/usr/lib64/python2.7/ssl.py", line 746, in sendall
> >  v = self.send(data[count:])
> >File "/usr/lib64/python2.7/ssl.py", line 712, in send
> >  v = self._sslobj.write(data)
> > socket.error: [Errno 104] Connection reset by peer
> >
> > in web GUI the disk stays in Status: "Transferring via API"
> > it can only be removed when manually unlocking it (unlock_entity.sh)
> >
> > engine.log tells nothing interesting
> >
> > i attached the last lines of ovirt-imageio-proxy/image-proxy.log and
> > ovirt-imageio-daemon/daemon.log (from the executing node)
> >
> > the HTTP status 403 in ovirt-imageio-daemon/daemon.log doesn't look too
> > nice to me
> >
> > can you explain what happens?
> >
> > ovirt engine is 4.1.5
> > ovirt node is 4.1.3 (is that a problem?)
> >
> > thx
> > matthias
> >
> >
> >
> > Am 2017-09-12 um 13:15 schrieb Fred Rolland:
> >> Hi,
> >>
> >> You can check this example:
> >>
> https://github.com/oVirt/ovirt-engine-sdk/blob/master/sdk/examples/upload_disk.py
> >>
> >>
> >> Regards,
> >> Fred
> >>
> >> On Tue, Sep 12, 2017 at 11:49 AM, Matthias Leopold
> >>  >> > wrote:
> >>
> >> Hi,
> >>
> >> is there a way to upload disk images (not OVF files, not ISO files)
> >> to oVirt storage domains via CLI? I need to upload a 800GB file and
> >> this is not really comfortable via browser. I looked at ovirt-shell
> >> and
> >>
> >>
> https://www.ovirt.org/develop/release-management/features/storage/image-upload/
> >>
> >>
> >> <
> https://www.ovirt.org/develop/release-management/features/storage/image-upload/
> >,
> >>
> >> but i didn't find an option in either of them.
> >>
> >> thx
> >> matthias
> >>
> >> ___
> >> Users mailing list
> >> Users@ovirt.org 
> >> http://lists.ovirt.org/mailman/listinfo/users
> >> 
> >>
> >>
> >
>
> --
> Matthias Leopold
> IT Systems & Communications
> Medizinische Universität Wien
> Spitalgasse 23 / BT 88 /Ebene 00
> A-1090 Wien
> Tel: +43 1 40160-21241 <+43%201%204016021241>
> Fax: +43 1 40160-921200 <+43%201%2040160921200>
> ___
> 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] Disk image upload via CLI?

[Nir Soffer]

On Tue, Sep 12, 2017 at 5:45 PM Matthias Leopold <
matthias.leop...@meduniwien.ac.at> wrote:

> Thanks, i tried this script and it _almost_ worked ;-)
>
> i uploaded two images i created with
> qemu-img create -f qcow2 -o preallocation=full
> and
> qemu-img create -f qcow2 -o preallocation=falloc
>
> for initial_size and provisioned_size i took the value reported by
> "qemu-img info" in "virtual size" (same as "disk size" in this case)

the upload goes to 100% and then fails with
>
> 200 OK Completed 100%
> Traceback (most recent call last):
>File "./upload_disk.py", line 157, in 
>  headers=upload_headers,
>File "/usr/lib64/python2.7/httplib.py", line 1017, in request
>  self._send_request(method, url, body, headers)
>File "/usr/lib64/python2.7/httplib.py", line 1051, in _send_request
>  self.endheaders(body)
>File "/usr/lib64/python2.7/httplib.py", line 1013, in endheaders
>  self._send_output(message_body)
>File "/usr/lib64/python2.7/httplib.py", line 864, in _send_output
>  self.send(msg)
>File "/usr/lib64/python2.7/httplib.py", line 840, in send
>  self.sock.sendall(data)
>File "/usr/lib64/python2.7/ssl.py", line 746, in sendall
>  v = self.send(data[count:])
>File "/usr/lib64/python2.7/ssl.py", line 712, in send
>  v = self._sslobj.write(data)
> socket.error: [Errno 104] Connection reset by peer
>
> in web GUI the disk stays in Status: "Transferring via API"
> it can only be removed when manually unlocking it (unlock_entity.sh)
>
> engine.log tells nothing interesting
>
> i attached the last lines of ovirt-imageio-proxy/image-proxy.log and
> ovirt-imageio-daemon/daemon.log (from the executing node)
>
> the HTTP status 403 in ovirt-imageio-daemon/daemon.log doesn't look too
> nice to me
>
> can you explain what happens?
>

Hi Matthias,

I think qemu-img reports the wrong size in disk size, so the disk you
created
for the upload was smaller than the file you tried to upload. This will end
in
404 forbidden error when you try to write after the end of the specified
size.

In this case we send a detailed error to the proxy but it cannot get this
response
since it tries to send the data to the daemon, but the daemon will never
read
data from invalid request.

You should get the file size using os.path.getsize() instead of qemu-img
info.

That said, our logging is not good enough:

2017-09-12 16:07:13,188 WARNING (Thread-641) [web] xxx.yyy.215.2 - PUT
/1e12aa19-f122-4f6c-bfad-ce84abe2684e 403 138 (0.00s)

This log should explain why the operation is forbidden - for example:

Trying to write to offset x, maximum offset y

Can you file a bug for more detailed logging when upload/download request
is invalid?

Regarding the logs you submitted, please submit complete logs. For example
in this case we would see the ticket size in the log for adding the ticket
for this
upload, which makes the issue more clear.


>
> ovirt engine is 4.1.5
> ovirt node is 4.1.3 (is that a problem?)
>

No but you want to run latest code to get the all the fixes introduced
in 4.1.5.

Cheers,
Nir


>
> thx
> matthias
>
>
>
> Am 2017-09-12 um 13:15 schrieb Fred Rolland:
> > Hi,
> >
> > You can check this example:
> >
> https://github.com/oVirt/ovirt-engine-sdk/blob/master/sdk/examples/upload_disk.py
> >
> > Regards,
> > Fred
> >
> > On Tue, Sep 12, 2017 at 11:49 AM, Matthias Leopold
> >  > > wrote:
> >
> > Hi,
> >
> > is there a way to upload disk images (not OVF files, not ISO files)
> > to oVirt storage domains via CLI? I need to upload a 800GB file and
> > this is not really comfortable via browser. I looked at ovirt-shell
> > and
> >
> https://www.ovirt.org/develop/release-management/features/storage/image-upload/
> > <
> https://www.ovirt.org/develop/release-management/features/storage/image-upload/
> >,
> > but i didn't find an option in either of them.
> >
> > thx
> > matthias
> >
> > ___
> > Users mailing list
> > Users@ovirt.org 
> > http://lists.ovirt.org/mailman/listinfo/users
> > 
> >
> >
>
> --
> Matthias Leopold
> IT Systems & Communications
> Medizinische Universität Wien
> Spitalgasse 23 / BT 88 /Ebene 00
> A-1090 Wien
> Tel: +43 1 40160-21241 <+43%201%204016021241>
> Fax: +43 1 40160-921200 <+43%201%2040160921200>
> ___
> 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] why force bond* naming?

[Charles Kozler]

Hello -

I had setup my server somewhat before installing ovirt. I left em1 alone
for the ovirtmgmt but I had bonded two NICs on a separate card and named it
storage0 and storage1 accordingly.

Everything setup fine and when I went to add more networks for em3+em4 in
LACP named bond0, the web UI would not let me proceed because my two NICs
named storage0 and storage1. It didnt say directly it was those but it said
it needed "bond" in the name followed by a number. I shut everything down
and renamed them bond100 and bond101 and all was well

However, I cant stop and think that I was not trying to set those NICs
(storage0/1) up in ovirt so why would ovirt UI care about NICs in the
server that it wasnt even responsible for managing nor I had any
modifications to from the UI?

I get forcing it when you're adding through to UI but making the UI force
the user to use bond* for all of their NICs doesnt seem right

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

Re: [ovirt-users] Disk image upload via CLI?

[Daniel Erez]

Hi Matthias,

The 403 response from the daemon means the ticket can't be authenticated
(for some reason). I assume that the issue here is the initial size of the
disk.
When uploading/downloading a qcow image, you should specify the apparent
size of the file (see 'st_size' in [1]). You can get it simply by 'ls -l'
[2] (which is
a different value from 'disk size' of qemu-img info [3]).
btw, why are you creating a preallocated qcow disk? For what use-case?

[1] https://linux.die.net/man/2/stat

[2] $ ls -l test.qcow2
-rw-r--r--. 1 user user 1074135040 Sep 13 16:50 test.qcow2

[3]
$ qemu-img create -f qcow2 -o preallocation=full test.qcow2 1g
$ qemu-img info test.qcow2
image: test.qcow2
file format: qcow2
virtual size: 1.0G (1073741824 bytes)
disk size: 1.0G
cluster_size: 65536
Format specific information:
compat: 1.1
lazy refcounts: false
refcount bits: 16
corrupt: false



On Wed, Sep 13, 2017 at 5:03 PM Matthias Leopold <
matthias.leop...@meduniwien.ac.at> wrote:

> i tried it again twice:
>
> when using upload_disk.py from the ovirt engine host itself the disk
> upload succeeds (despite an "503 Service Unavailable Completed 100%" in
> script output in the end)
>
> another try was from an ovirt-sdk installation on my ubuntu desktop
> itself (yesterday i tried it from a centos VM on my desktop machine).
> this failed again, this time with "socket.error: [Errno 32] Broken pipe"
> after reaching "200 OK Completed 100%". in imageio-proxy log i have
> again the 403 error in this moment
>
> what's the difference between accessing the API from the engine host and
> from "outside" in this case?
>
> thx
> matthias
>
> Am 2017-09-12 um 16:42 schrieb Matthias Leopold:
> > Thanks, i tried this script and it _almost_ worked ;-)
> >
> > i uploaded two images i created with
> > qemu-img create -f qcow2 -o preallocation=full
> > and
> > qemu-img create -f qcow2 -o preallocation=falloc
> >
> > for initial_size and provisioned_size i took the value reported by
> > "qemu-img info" in "virtual size" (same as "disk size" in this case)
> >
> > the upload goes to 100% and then fails with
> >
> > 200 OK Completed 100%
> > Traceback (most recent call last):
> >File "./upload_disk.py", line 157, in 
> >  headers=upload_headers,
> >File "/usr/lib64/python2.7/httplib.py", line 1017, in request
> >  self._send_request(method, url, body, headers)
> >File "/usr/lib64/python2.7/httplib.py", line 1051, in _send_request
> >  self.endheaders(body)
> >File "/usr/lib64/python2.7/httplib.py", line 1013, in endheaders
> >  self._send_output(message_body)
> >File "/usr/lib64/python2.7/httplib.py", line 864, in _send_output
> >  self.send(msg)
> >File "/usr/lib64/python2.7/httplib.py", line 840, in send
> >  self.sock.sendall(data)
> >File "/usr/lib64/python2.7/ssl.py", line 746, in sendall
> >  v = self.send(data[count:])
> >File "/usr/lib64/python2.7/ssl.py", line 712, in send
> >  v = self._sslobj.write(data)
> > socket.error: [Errno 104] Connection reset by peer
> >
> > in web GUI the disk stays in Status: "Transferring via API"
> > it can only be removed when manually unlocking it (unlock_entity.sh)
> >
> > engine.log tells nothing interesting
> >
> > i attached the last lines of ovirt-imageio-proxy/image-proxy.log and
> > ovirt-imageio-daemon/daemon.log (from the executing node)
> >
> > the HTTP status 403 in ovirt-imageio-daemon/daemon.log doesn't look too
> > nice to me
> >
> > can you explain what happens?
> >
> > ovirt engine is 4.1.5
> > ovirt node is 4.1.3 (is that a problem?)
> >
> > thx
> > matthias
> >
> >
> >
> > Am 2017-09-12 um 13:15 schrieb Fred Rolland:
> >> Hi,
> >>
> >> You can check this example:
> >>
> https://github.com/oVirt/ovirt-engine-sdk/blob/master/sdk/examples/upload_disk.py
> >>
> >>
> >> Regards,
> >> Fred
> >>
> >> On Tue, Sep 12, 2017 at 11:49 AM, Matthias Leopold
> >>  >> > wrote:
> >>
> >> Hi,
> >>
> >> is there a way to upload disk images (not OVF files, not ISO files)
> >> to oVirt storage domains via CLI? I need to upload a 800GB file and
> >> this is not really comfortable via browser. I looked at ovirt-shell
> >> and
> >>
> >>
> https://www.ovirt.org/develop/release-management/features/storage/image-upload/
> >>
> >>
> >> <
> https://www.ovirt.org/develop/release-management/features/storage/image-upload/
> >,
> >>
> >> but i didn't find an option in either of them.
> >>
> >> thx
> >> matthias
> >>
> >> ___
> >> Users mailing list
> >> Users@ovirt.org 
> >> http://lists.ovirt.org/mailman/listinfo/users
> >> 
> >>
> >>
> >
>
> --
> Matthias Leopold
> IT Systems & Communications
> Medizinische Universität Wien
> Spitalgasse 23 / BT 88 /Ebene 00
> A-1090 Wien
> Tel: +43 1 40160-21241 <+43%201%204016021241>
> Fax: +43 1 40160-

Re: [ovirt-users] vmware ova import problem

[Michal Skrivanek]

> On 13 Sep 2017, at 16:33, Jiří Sléžka  wrote:
> 
> Hi,
> 
> thanks for reply
> 
> 
> On 09/12/2017 12:44 PM, Michal Skrivanek wrote:
>> 
>>> On 11 Sep 2017, at 14:12, Jiří Sléžka  wrote:
>>> 
>>> Hi,
>>> 
>>> today I tested vmware ova import for first time but unfortunately it
>>> failed. (btw. it would be great to have a possibility to upload ova
>>> directly from manager…)
>> 
>> in 4.1 you can only upload qcow disks, in future we will support complete 
>> OVA (native oVirt’s OVA’s though)
> 
> good news :-)
> 
>>> 
>>> problem seems to be this (vdsm/import log)
>>> 
>>> ...
>>> libguestfs: trace: v2v: inspect_get_type = "linux"
>>>  i_root = /dev/sda1
>>> i_type =
>>> linux
>>> i_distro = debian
>>>i_arch = i386
>>> 
>>>  i_major_version = 9
>>> i_minor_version = 0
>>> 
>>> i_package_format = deb
>>>  i_package_management = apt
>>> 
>>> i_product_name = 9.0
>>>  i_product_variant = unknown
>>> i_uefi =
>>> false
>>> 
>>> ...
>>> ...
>>> ...
>>> [  13.7] Converting 9.0 to run on KVM
>>>  virt-v2v: error: virt-v2v is unable to
>>> convert this guest type
>>> (linux/debian)
>>>  rm -rf '/var/tmp/ova.lB3mEN'
>>> rm -rf
>>> '/var/tmp/null.kaX2uZ'
>>> ...
>>> 
>>> so is debian really unsupported to be imported fom vmware ova?
>> 
>> it is supported only in libguestfs 1.36+ which is released in EL 7.4
> 
> nice, I can't wait for CentOS7.4 release

http://mirror.centos.org/centos/7.4.1708/
yay!:)
still missing qemu-kvm-ev, so do not upgrade yet. But very soon...

> 
>>> 
>>> I believe this vm could run as is, even without v2v convert.
>>> 
>>> It would be nice to have a possibility to bypass v2v process and import
>>> appliance as is, just disk(s) and vm definition. Does it make sense?
>> 
>> the disk needs conversion, as well as changes to be able to boot (that’s the 
>> part originally missing for debina-based guests)
> 
> It depends. In this case I converted vmdk disk to raw, created vm in
> oVirt, dded raw image to this vm and I had to change just ethernet
> interface name. It was ugly workaround but it is working. So for this
> case it would be nice to have a possibility to bypass v2v :-) but ok,
> this is very specific case.

Sure, you can always just do the same steps manually. virt-v2v just tries to 
wrap that into a single step process. But it just connects the dots and uses 
other tools to do that, it’s definitely doable manually

> 
> Cheers,
> 
> Jiri Slezka
> 
>> 
>> Thanks,
>> michal
>> 
>>> 
>>> Cheers,
>>> 
>>> Jiri Slezka
>>> 
>>> ___
>>> 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] oVirt node and bonding options cutomizations

[Gianluca Cecchi]

On Wed, Sep 13, 2017 at 3:46 PM, Petr Horacek  wrote:

> Hello,
>
> you can specify more bondings options by selecting Bonding Mode
> "custom" and passing "miimon=100 updelay=0 downdelay=0 mode=802.3ad
> lacp_rate=1" there.
>
> Regards,
> Petr
>
>
Ok, but this means that these kind of customization are to be done only
after I have also installed the engine and added the node to it.
And not in the preliminary phase where I have only installed the ovirt node
OS from the iso and I'm accessing it from http://host_ip_addr:9090 cockpit
interface, correct?
Thanks,
Gianluca
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] vmware ova import problem

[Jiří Sléžka]

Hi,

thanks for reply


On 09/12/2017 12:44 PM, Michal Skrivanek wrote:
> 
>> On 11 Sep 2017, at 14:12, Jiří Sléžka  wrote:
>>
>> Hi,
>>
>> today I tested vmware ova import for first time but unfortunately it
>> failed. (btw. it would be great to have a possibility to upload ova
>> directly from manager…)
> 
> in 4.1 you can only upload qcow disks, in future we will support complete OVA 
> (native oVirt’s OVA’s though)

good news :-)

>>
>> problem seems to be this (vdsm/import log)
>>
>> ...
>> libguestfs: trace: v2v: inspect_get_type = "linux"
>>   i_root = /dev/sda1
>>  i_type =
>> linux
>>  i_distro = debian
>> i_arch = i386
>>
>>   i_major_version = 9
>>  i_minor_version = 0
>>
>> i_package_format = deb
>>   i_package_management = apt
>>
>> i_product_name = 9.0
>>   i_product_variant = unknown
>>  i_uefi =
>> false
>>
>> ...
>> ...
>> ...
>> [  13.7] Converting 9.0 to run on KVM
>>   virt-v2v: error: virt-v2v is unable to
>> convert this guest type
>> (linux/debian)
>>   rm -rf '/var/tmp/ova.lB3mEN'
>>  rm -rf
>> '/var/tmp/null.kaX2uZ'
>> ...
>>
>> so is debian really unsupported to be imported fom vmware ova?
> 
> it is supported only in libguestfs 1.36+ which is released in EL 7.4

nice, I can't wait for CentOS7.4 release

>>
>> I believe this vm could run as is, even without v2v convert.
>>
>> It would be nice to have a possibility to bypass v2v process and import
>> appliance as is, just disk(s) and vm definition. Does it make sense?
> 
> the disk needs conversion, as well as changes to be able to boot (that’s the 
> part originally missing for debina-based guests)

It depends. In this case I converted vmdk disk to raw, created vm in
oVirt, dded raw image to this vm and I had to change just ethernet
interface name. It was ugly workaround but it is working. So for this
case it would be nice to have a possibility to bypass v2v :-) but ok,
this is very specific case.

Cheers,

Jiri Slezka

> 
> Thanks,
> michal
> 
>>
>> Cheers,
>>
>> Jiri Slezka
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
> 




smime.p7s
Description: S/MIME Cryptographic Signature
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Disk image upload via CLI?

[Matthias Leopold]

i tried it again twice:

when using upload_disk.py from the ovirt engine host itself the disk 
upload succeeds (despite an "503 Service Unavailable Completed 100%" in 
script output in the end)


another try was from an ovirt-sdk installation on my ubuntu desktop 
itself (yesterday i tried it from a centos VM on my desktop machine). 
this failed again, this time with "socket.error: [Errno 32] Broken pipe" 
after reaching "200 OK Completed 100%". in imageio-proxy log i have 
again the 403 error in this moment


what's the difference between accessing the API from the engine host and 
from "outside" in this case?


thx
matthias

Am 2017-09-12 um 16:42 schrieb Matthias Leopold:

Thanks, i tried this script and it _almost_ worked ;-)

i uploaded two images i created with
qemu-img create -f qcow2 -o preallocation=full
and
qemu-img create -f qcow2 -o preallocation=falloc

for initial_size and provisioned_size i took the value reported by 
"qemu-img info" in "virtual size" (same as "disk size" in this case)


the upload goes to 100% and then fails with

200 OK Completed 100%
Traceback (most recent call last):
   File "./upload_disk.py", line 157, in 
 headers=upload_headers,
   File "/usr/lib64/python2.7/httplib.py", line 1017, in request
 self._send_request(method, url, body, headers)
   File "/usr/lib64/python2.7/httplib.py", line 1051, in _send_request
 self.endheaders(body)
   File "/usr/lib64/python2.7/httplib.py", line 1013, in endheaders
 self._send_output(message_body)
   File "/usr/lib64/python2.7/httplib.py", line 864, in _send_output
 self.send(msg)
   File "/usr/lib64/python2.7/httplib.py", line 840, in send
 self.sock.sendall(data)
   File "/usr/lib64/python2.7/ssl.py", line 746, in sendall
 v = self.send(data[count:])
   File "/usr/lib64/python2.7/ssl.py", line 712, in send
 v = self._sslobj.write(data)
socket.error: [Errno 104] Connection reset by peer

in web GUI the disk stays in Status: "Transferring via API"
it can only be removed when manually unlocking it (unlock_entity.sh)

engine.log tells nothing interesting

i attached the last lines of ovirt-imageio-proxy/image-proxy.log and 
ovirt-imageio-daemon/daemon.log (from the executing node)


the HTTP status 403 in ovirt-imageio-daemon/daemon.log doesn't look too 
nice to me


can you explain what happens?

ovirt engine is 4.1.5
ovirt node is 4.1.3 (is that a problem?)

thx
matthias



Am 2017-09-12 um 13:15 schrieb Fred Rolland:

Hi,

You can check this example:
https://github.com/oVirt/ovirt-engine-sdk/blob/master/sdk/examples/upload_disk.py 



Regards,
Fred

On Tue, Sep 12, 2017 at 11:49 AM, Matthias Leopold 
> wrote:


Hi,

is there a way to upload disk images (not OVF files, not ISO files)
to oVirt storage domains via CLI? I need to upload a 800GB file and
this is not really comfortable via browser. I looked at ovirt-shell
and

https://www.ovirt.org/develop/release-management/features/storage/image-upload/ 


, 


but i didn't find an option in either of them.

thx
matthias

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







--
Matthias Leopold
IT Systems & Communications
Medizinische Universität Wien
Spitalgasse 23 / BT 88 /Ebene 00
A-1090 Wien
Tel: +43 1 40160-21241
Fax: +43 1 40160-921200
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] oVirt node and bonding options cutomizations

[Petr Horacek]

Hello,

you can specify more bondings options by selecting Bonding Mode
"custom" and passing "miimon=100 updelay=0 downdelay=0 mode=802.3ad
lacp_rate=1" there.

Regards,
Petr

2017-09-08 12:09 GMT+02:00 Gianluca Cecchi :
> Hello,
> when using CentOS as OS for hypervisor and mode=4 for bonding (802.3ad) in
> the past I had to use lacp_rate=1 (aka fast), because I noticed problems
> with the default lacp_rate=0 parameter.
> Now I'm testing an oVirt node and I see that into the graphical interface
> there are the options to set mode, link up and down delays, but not the
> lacp_rate option.
>
> It is a different environment from the one where I had to modify it, so I
> will start with the default value and see if I get any problems again.
>
> Now the ifcfg-bond0 file created at oVirt node level by the web mgmt
> interface contains:
>
> BONDING_OPTS="miimon=100 updelay=0 downdelay=0 mode=802.3ad"
>
> Would I be able to modify it in case of need and have it persistent across
> reboot, something like this:
>
> BONDING_OPTS="miimon=100 updelay=0 downdelay=0 mode=802.3ad lacp_rate=1"
>
> ?
>
> Thanks in advance,
> 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

Re: [ovirt-users] Hyper converged network setup

[Tailor, Bharat]

I can't. I've destroyed that VM and clean all files. Now I am trying to
reinstall new engine VM.

Regrards
Bharat Kumar

G15- Vinayak Nagar complex,Opp.Maa Satiya, ayad
Udaipur (Raj.)
313001
Mob: +91-9950-9960-25





On Wed, Sep 13, 2017 at 5:12 PM, Donny Davis  wrote:

> Can you ping the VM when it comes up?
>
> On Wed, Sep 13, 2017 at 7:40 AM, Tailor, Bharat <
> bha...@synergysystemsindia.com> wrote:
>
>> I am not using any DNS server. I have made entries in /etc/hosts for all
>> Nodes and for engine VM also.
>>
>> Regrards
>> Bharat Kumar
>>
>> G15- Vinayak Nagar complex,Opp.Maa Satiya, ayad
>> Udaipur (Raj.)
>> 313001
>> Mob: +91-9950-9960-25
>>
>>
>>
>>
>>
>> On Wed, Sep 13, 2017 at 5:02 PM, Donny Davis 
>> wrote:
>>
>>> Bharat,
>>>
>>> Are you using DNS for host names or /etc/hosts
>>>
>>> I personally place the engines hostname with ip address in /etc/hosts on
>>> all the hypervisors in case my DNS services go down.
>>> I also put the hypervisors in /etc/hosts too
>>>
>>> Hope this helps.
>>>
>>> On Wed, Sep 13, 2017 at 6:04 AM, Yaniv Kaul  wrote:
>>>


 On Wed, Sep 13, 2017 at 8:42 AM, Tailor, Bharat <
 bha...@synergysystemsindia.com> wrote:

> Hi Charles & Donny,
>
> Thank you so much.
>
> @Donny my 3rd node's IP is 192.168.100.17(Mentioned wrong in above
> mail).
> I was trying to install ovirt ova on test2.localdomain. I've cleared
> all the steps and at last I got a message like "Engine is still
> unreachable". Kindly help me to troubleshoot it.
>
> @Ykaul How can I register myself in mailing list?
>

 http://lists.ovirt.org/mailman/listinfo/users

 Y.


>
> Regrards
> Bharat Kumar
>
> G15- Vinayak Nagar complex,Opp.Maa Satiya, ayad
> Udaipur (Raj.)
> 313001
> Mob: +91-9950-9960-25
>
>
>
>
>
> On Wed, Sep 13, 2017 at 3:06 AM, Charles Kozler 
> wrote:
>
>> Bharat -
>>
>> 1. Yes. Will need to configure switch port as a trunk and setup your
>> VLANs and VLAN ID's
>> 2. Yes
>> 3. You can still access the hosts. The engine itself crashing or
>> being down wont stop your VMs or hosts or anything (unless fencing). You
>> can use virsh
>> 4. My suggestion here is start immediately after a fresh server
>> install and yum update. Installer does a lot and checks a lot and wont 
>> like
>> things: ex - you setup ovirtmgmt bridged network yourself
>> 5. Yes. See #1, usually what I do is each ovirt node I have I set an
>> IP of .5, then .6, and so on. This way I can be sure my network itself is
>> working before adding a VM and attaching that NIC to it
>>
>> On Tue, Sep 12, 2017 at 4:41 PM, Donny Davis 
>> wrote:
>>
>>> 1. Yes, you can do this
>>> 2. Yes, In linux it's called bonding and this can be done from the UI
>>> 3. You can get around using the Engine machine if required with
>>> virsh or virt-manager - however I would just wait for the manager to
>>> migrate and start on another host in the cluster
>>> 4.  The deployment will take care of everything for you. You just
>>> need an IP
>>> 5. Yes, you can use vlans or virtual networking(NSXish) called OVS
>>> in oVirt.
>>>
>>> I noticed on your deployment machines 2 and 3 have the same IP.
>>> Might want to fix that before deploying
>>>
>>> Happy trails
>>> ~D
>>>
>>>
>>> On Tue, Sep 12, 2017 at 2:00 PM, Tailor, Bharat <
>>> bha...@synergysystemsindia.com> wrote:
>>>
 Hi Charles,

 Thank you so much to share a cool stuff with us.

 My doubts are still not cleared.


1. What If I have only single Physical network adaptor? Can't I
use it for management network & production network both.
2. If I have two Physical network adaptor, Can I configure NIC
teaming as like Vmware ESXi.
3. What If my ovirt machine fails during production period? In
vmware we can access ESXi hosts and VM without Vcenter and do all 
 the
stuffs. Can we do the same with Ovirt & KVM.
4. To deploy ovirt engine VM, what kind of configuration I'll
have to do on network adaptors? (eg. just configure IP on physical 
 network
or have to create br0 for it.)
5. Can I make multiple VM networks for vlan configuration?


 Regrards
 Bharat Kumar

 G15- Vinayak Nagar complex,Opp.Maa Satiya, ayad
 Udaipur (Raj.)
 313001
 Mob: +91-9950-9960-25





 On Tue, Sep 12, 2017 at 9:30 PM, Charles Kozler <
 ckozler...@gmail.com> wrote:

>
> Interestingly enough I literally just went through this same thing
> with a slight variation.
>
>>

Re: [ovirt-users] Hyper converged network setup

[Tailor, Bharat]

I am not using any DNS server. I have made entries in /etc/hosts for all
Nodes and for engine VM also.

Regrards
Bharat Kumar

G15- Vinayak Nagar complex,Opp.Maa Satiya, ayad
Udaipur (Raj.)
313001
Mob: +91-9950-9960-25





On Wed, Sep 13, 2017 at 5:02 PM, Donny Davis  wrote:

> Bharat,
>
> Are you using DNS for host names or /etc/hosts
>
> I personally place the engines hostname with ip address in /etc/hosts on
> all the hypervisors in case my DNS services go down.
> I also put the hypervisors in /etc/hosts too
>
> Hope this helps.
>
> On Wed, Sep 13, 2017 at 6:04 AM, Yaniv Kaul  wrote:
>
>>
>>
>> On Wed, Sep 13, 2017 at 8:42 AM, Tailor, Bharat <
>> bha...@synergysystemsindia.com> wrote:
>>
>>> Hi Charles & Donny,
>>>
>>> Thank you so much.
>>>
>>> @Donny my 3rd node's IP is 192.168.100.17(Mentioned wrong in above mail).
>>> I was trying to install ovirt ova on test2.localdomain. I've cleared all
>>> the steps and at last I got a message like "Engine is still unreachable".
>>> Kindly help me to troubleshoot it.
>>>
>>> @Ykaul How can I register myself in mailing list?
>>>
>>
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>> Y.
>>
>>
>>>
>>> Regrards
>>> Bharat Kumar
>>>
>>> G15- Vinayak Nagar complex,Opp.Maa Satiya, ayad
>>> Udaipur (Raj.)
>>> 313001
>>> Mob: +91-9950-9960-25
>>>
>>>
>>>
>>>
>>>
>>> On Wed, Sep 13, 2017 at 3:06 AM, Charles Kozler 
>>> wrote:
>>>
 Bharat -

 1. Yes. Will need to configure switch port as a trunk and setup your
 VLANs and VLAN ID's
 2. Yes
 3. You can still access the hosts. The engine itself crashing or being
 down wont stop your VMs or hosts or anything (unless fencing). You can use
 virsh
 4. My suggestion here is start immediately after a fresh server install
 and yum update. Installer does a lot and checks a lot and wont like things:
 ex - you setup ovirtmgmt bridged network yourself
 5. Yes. See #1, usually what I do is each ovirt node I have I set an IP
 of .5, then .6, and so on. This way I can be sure my network itself is
 working before adding a VM and attaching that NIC to it

 On Tue, Sep 12, 2017 at 4:41 PM, Donny Davis 
 wrote:

> 1. Yes, you can do this
> 2. Yes, In linux it's called bonding and this can be done from the UI
> 3. You can get around using the Engine machine if required with virsh
> or virt-manager - however I would just wait for the manager to migrate and
> start on another host in the cluster
> 4.  The deployment will take care of everything for you. You just need
> an IP
> 5. Yes, you can use vlans or virtual networking(NSXish) called OVS in
> oVirt.
>
> I noticed on your deployment machines 2 and 3 have the same IP. Might
> want to fix that before deploying
>
> Happy trails
> ~D
>
>
> On Tue, Sep 12, 2017 at 2:00 PM, Tailor, Bharat <
> bha...@synergysystemsindia.com> wrote:
>
>> Hi Charles,
>>
>> Thank you so much to share a cool stuff with us.
>>
>> My doubts are still not cleared.
>>
>>
>>1. What If I have only single Physical network adaptor? Can't I
>>use it for management network & production network both.
>>2. If I have two Physical network adaptor, Can I configure NIC
>>teaming as like Vmware ESXi.
>>3. What If my ovirt machine fails during production period? In
>>vmware we can access ESXi hosts and VM without Vcenter and do all the
>>stuffs. Can we do the same with Ovirt & KVM.
>>4. To deploy ovirt engine VM, what kind of configuration I'll
>>have to do on network adaptors? (eg. just configure IP on physical 
>> network
>>or have to create br0 for it.)
>>5. Can I make multiple VM networks for vlan configuration?
>>
>>
>> Regrards
>> Bharat Kumar
>>
>> G15- Vinayak Nagar complex,Opp.Maa Satiya, ayad
>> Udaipur (Raj.)
>> 313001
>> Mob: +91-9950-9960-25
>>
>>
>>
>>
>>
>> On Tue, Sep 12, 2017 at 9:30 PM, Charles Kozler > > wrote:
>>
>>>
>>> Interestingly enough I literally just went through this same thing
>>> with a slight variation.
>>>
>>> Note to the below: I am not sure if this would be considerd best
>>> practice or good for something long term support but I made due with 
>>> what I
>>> had
>>>
>>> I had 10Gb cards for my storage network but no 10Gb switch, so I
>>> direct connected them with some fun routing and /etc/hosts settings. I 
>>> also
>>> didnt want my storage network on a routed network (have firewalls in the
>>> way of VLANs) and I wanted the network separate from my ovirtmgmt - 
>>> and, as
>>> I said, had no switches for 10Gb. Here is what you need at a bare 
>>> minimum.
>>> Adapt / change it as you need
>>>
>>> 1 dedicated NIC on each node for ovirtmgmt. Ex: eth0
>>>
>>> 1 dedicated NIC to 

Re: [ovirt-users] epel and collectd

[Fabrice Bacchella]

> Le 13 sept. 2017 à 10:39, Sandro Bonazzola  a écrit :
> 
>  In general, I still consider EPEL harmful so just dropped the part related 
> to collectd. 
> 

What kind of problems do you have with it ?
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] mode 4 bonding for VMs with NetworkManager anyone?

[Gianluca Cecchi]

On Wed, Sep 13, 2017 at 1:53 PM, Donny Davis  wrote:

> As long as the switch is setup for 802.3AD (LACP) then you should be fine.
> I used the UI to setup my bond's and here is the output from my hypervisor
>
>
OK, thanks.
I suppose bond0 is where you have your lacp bonding
What do you get in output on your node with the command

cat /proc/net/bonding/bond0

?
Could it do any difference to do 802.3ad on a tagged or untagged vlan?
Thanks,
Gianluca
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] mode 4 bonding for VMs with NetworkManager anyone?

[Donny Davis]

As long as the switch is setup for 802.3AD (LACP) then you should be fine.
I used the UI to setup my bond's and here is the output from my hypervisor

[root@virtnode-3 ~]# systemctl status NetworkManager

● NetworkManager.service - Network Manager

   Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled;
vendor preset: enabled)

   Active: active (running) since Mon 2017-09-11 19:07:06 UTC; 1 day 16h ago

 Docs: man:NetworkManager(8)

 Main PID: 952 (NetworkManager)

   CGroup: /system.slice/NetworkManager.service

   └─952 /usr/sbin/NetworkManager --no-daemon


Sep 11 20:12:15 virtnode-3.fortnebula.com NetworkManager[952]: 
[1505160735.0612]
ifcfg-rh: Ignoring connection /etc/sysconfig/network-scripts/ifcfg-storage
(53b19d46-6b08-f...me:storage.

Sep 11 20:12:16 virtnode-3.fortnebula.com NetworkManager[952]: 
[1505160736.8563]
device (p3p1): link connected

Sep 11 20:12:17 virtnode-3.fortnebula.com NetworkManager[952]: 
[1505160737.0798]
device (p3p2): link connected

Sep 11 20:12:17 virtnode-3.fortnebula.com NetworkManager[952]: 
[1505160737.0839]
device (bond0): link connected

Sep 11 20:12:17 virtnode-3.fortnebula.com NetworkManager[952]: 
[1505160737.7324]
ifcfg-rh: new connection /etc/sysconfig/network-scripts/ifcfg-bond0.600
(cad7be9f-9e8c-bcab-4...m bond0.600")

Sep 11 20:12:17 virtnode-3.fortnebula.com NetworkManager[952]: 
[1505160737.7324]
ifcfg-rh: Ignoring connection
/etc/sysconfig/network-scripts/ifcfg-bond0.600
(cad7be9f-9e8c-b...me:bond0.600.

Sep 11 20:12:17 virtnode-3.fortnebula.com NetworkManager[952]: 
[1505160737.7533]
manager: (bond0.600): new VLAN device
(/org/freedesktop/NetworkManager/Devices/37)

Sep 11 20:12:17 virtnode-3.fortnebula.com NetworkManager[952]: 
[1505160737.7705]
manager: (storage): new Bridge device
(/org/freedesktop/NetworkManager/Devices/38)

Sep 11 20:12:17 virtnode-3.fortnebula.com NetworkManager[952]: 
[1505160737.7905]
device (bond0.600): link connected

Sep 11 20:12:17 virtnode-3.fortnebula.com NetworkManager[952]: 
[1505160737.8477]
device (storage): link connected

Hint: Some lines were ellipsized, use -l to show in full.

[root@virtnode-3 ~]# rpm -qa vdsm

vdsm-4.19.28-1.el7.centos.x86_64

[root@virtnode-3 ~]#

On Wed, Sep 13, 2017 at 7:46 AM, Gianluca Cecchi 
wrote:

> On Wed, Sep 13, 2017 at 1:43 PM, Donny Davis  wrote:
>
>> Just use the UI to manage your network interfaces.
>>
>>
> Just used and prolems arose...
> hence the question ;-)
>
> In the mean time, as I have no control on network configuration from a
> switch point of view, I have asked network guys to verify.
> My question was to verify that NM + 802.3AD is used ok from others
>
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] mode 4 bonding for VMs with NetworkManager anyone?

[Gianluca Cecchi]

On Wed, Sep 13, 2017 at 1:43 PM, Donny Davis  wrote:

> Just use the UI to manage your network interfaces.
>
>
Just used and prolems arose...
hence the question ;-)

In the mean time, as I have no control on network configuration from a
switch point of view, I have asked network guys to verify.
My question was to verify that NM + 802.3AD is used ok from others
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] mode 4 bonding for VMs with NetworkManager anyone?

[Donny Davis]

Just use the UI to manage your network interfaces.

On Wed, Sep 13, 2017 at 6:23 AM, Gianluca Cecchi 
wrote:

> Hello,
> I'm testing ovirt node, both 4.1.5 and 4.1.6rc2.
> I see that in both versions the network stack is configured with
> NetworkManager enabled.
>
> With plain CentOS I always disabled NetworkManager and only used classical
> network service alone, so I have not background with NM, related to
> hypervisor.
>
> I have configured a vlan (untagged) for VMs, using bonding mode=4
> (802.3ad).
>
> I have some problems with my VMs: they are reachable from some parts and
> not from others.
>
> In parallel I have already asked network guys to crosscheck network
> configurations of the datacenter, but I would like to have confirmation
> that other ones are already using with success the combination of:
>
> - NetworkManager on hypervisor
> - bonding mode = 4 for VMs traffic
>
> Another question for another aspect I never understood: with an
> environment in the past (before 3.5 times if I remember well) I used
> 802.3ad but I had to set lacp_rate=1 (fast) because I had connection
> problems with the default lacp_rate=0 (slow) parameter.
> I see that still the default is lacp_rate=0
> Could it be the same this time? Is there any reason to set default
> lacp_rate=0 in oVirt (or the reverse... ;-)?
>
> Thanks in advance,
> 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

Re: [ovirt-users] Hyper converged network setup

[Donny Davis]

Can you ping the VM when it comes up?

On Wed, Sep 13, 2017 at 7:40 AM, Tailor, Bharat <
bha...@synergysystemsindia.com> wrote:

> I am not using any DNS server. I have made entries in /etc/hosts for all
> Nodes and for engine VM also.
>
> Regrards
> Bharat Kumar
>
> G15- Vinayak Nagar complex,Opp.Maa Satiya, ayad
> Udaipur (Raj.)
> 313001
> Mob: +91-9950-9960-25
>
>
>
>
>
> On Wed, Sep 13, 2017 at 5:02 PM, Donny Davis  wrote:
>
>> Bharat,
>>
>> Are you using DNS for host names or /etc/hosts
>>
>> I personally place the engines hostname with ip address in /etc/hosts on
>> all the hypervisors in case my DNS services go down.
>> I also put the hypervisors in /etc/hosts too
>>
>> Hope this helps.
>>
>> On Wed, Sep 13, 2017 at 6:04 AM, Yaniv Kaul  wrote:
>>
>>>
>>>
>>> On Wed, Sep 13, 2017 at 8:42 AM, Tailor, Bharat <
>>> bha...@synergysystemsindia.com> wrote:
>>>
 Hi Charles & Donny,

 Thank you so much.

 @Donny my 3rd node's IP is 192.168.100.17(Mentioned wrong in above
 mail).
 I was trying to install ovirt ova on test2.localdomain. I've cleared
 all the steps and at last I got a message like "Engine is still
 unreachable". Kindly help me to troubleshoot it.

 @Ykaul How can I register myself in mailing list?

>>>
>>> http://lists.ovirt.org/mailman/listinfo/users
>>>
>>> Y.
>>>
>>>

 Regrards
 Bharat Kumar

 G15- Vinayak Nagar complex,Opp.Maa Satiya, ayad
 Udaipur (Raj.)
 313001
 Mob: +91-9950-9960-25





 On Wed, Sep 13, 2017 at 3:06 AM, Charles Kozler 
 wrote:

> Bharat -
>
> 1. Yes. Will need to configure switch port as a trunk and setup your
> VLANs and VLAN ID's
> 2. Yes
> 3. You can still access the hosts. The engine itself crashing or being
> down wont stop your VMs or hosts or anything (unless fencing). You can use
> virsh
> 4. My suggestion here is start immediately after a fresh server
> install and yum update. Installer does a lot and checks a lot and wont 
> like
> things: ex - you setup ovirtmgmt bridged network yourself
> 5. Yes. See #1, usually what I do is each ovirt node I have I set an
> IP of .5, then .6, and so on. This way I can be sure my network itself is
> working before adding a VM and attaching that NIC to it
>
> On Tue, Sep 12, 2017 at 4:41 PM, Donny Davis 
> wrote:
>
>> 1. Yes, you can do this
>> 2. Yes, In linux it's called bonding and this can be done from the UI
>> 3. You can get around using the Engine machine if required with virsh
>> or virt-manager - however I would just wait for the manager to migrate 
>> and
>> start on another host in the cluster
>> 4.  The deployment will take care of everything for you. You just
>> need an IP
>> 5. Yes, you can use vlans or virtual networking(NSXish) called OVS in
>> oVirt.
>>
>> I noticed on your deployment machines 2 and 3 have the same IP. Might
>> want to fix that before deploying
>>
>> Happy trails
>> ~D
>>
>>
>> On Tue, Sep 12, 2017 at 2:00 PM, Tailor, Bharat <
>> bha...@synergysystemsindia.com> wrote:
>>
>>> Hi Charles,
>>>
>>> Thank you so much to share a cool stuff with us.
>>>
>>> My doubts are still not cleared.
>>>
>>>
>>>1. What If I have only single Physical network adaptor? Can't I
>>>use it for management network & production network both.
>>>2. If I have two Physical network adaptor, Can I configure NIC
>>>teaming as like Vmware ESXi.
>>>3. What If my ovirt machine fails during production period? In
>>>vmware we can access ESXi hosts and VM without Vcenter and do all the
>>>stuffs. Can we do the same with Ovirt & KVM.
>>>4. To deploy ovirt engine VM, what kind of configuration I'll
>>>have to do on network adaptors? (eg. just configure IP on physical 
>>> network
>>>or have to create br0 for it.)
>>>5. Can I make multiple VM networks for vlan configuration?
>>>
>>>
>>> Regrards
>>> Bharat Kumar
>>>
>>> G15- Vinayak Nagar complex,Opp.Maa Satiya, ayad
>>> Udaipur (Raj.)
>>> 313001
>>> Mob: +91-9950-9960-25
>>>
>>>
>>>
>>>
>>>
>>> On Tue, Sep 12, 2017 at 9:30 PM, Charles Kozler <
>>> ckozler...@gmail.com> wrote:
>>>

 Interestingly enough I literally just went through this same thing
 with a slight variation.

 Note to the below: I am not sure if this would be considerd best
 practice or good for something long term support but I made due with 
 what I
 had

 I had 10Gb cards for my storage network but no 10Gb switch, so I
 direct connected them with some fun routing and /etc/hosts settings. I 
 also
 didnt want my storage network on a routed network (have firewalls

Re: [ovirt-users] Hyper converged network setup

[Donny Davis]

Bharat,

Are you using DNS for host names or /etc/hosts

I personally place the engines hostname with ip address in /etc/hosts on
all the hypervisors in case my DNS services go down.
I also put the hypervisors in /etc/hosts too

Hope this helps.

On Wed, Sep 13, 2017 at 6:04 AM, Yaniv Kaul  wrote:

>
>
> On Wed, Sep 13, 2017 at 8:42 AM, Tailor, Bharat <
> bha...@synergysystemsindia.com> wrote:
>
>> Hi Charles & Donny,
>>
>> Thank you so much.
>>
>> @Donny my 3rd node's IP is 192.168.100.17(Mentioned wrong in above mail).
>> I was trying to install ovirt ova on test2.localdomain. I've cleared all
>> the steps and at last I got a message like "Engine is still unreachable".
>> Kindly help me to troubleshoot it.
>>
>> @Ykaul How can I register myself in mailing list?
>>
>
> http://lists.ovirt.org/mailman/listinfo/users
>
> Y.
>
>
>>
>> Regrards
>> Bharat Kumar
>>
>> G15- Vinayak Nagar complex,Opp.Maa Satiya, ayad
>> Udaipur (Raj.)
>> 313001
>> Mob: +91-9950-9960-25
>>
>>
>>
>>
>>
>> On Wed, Sep 13, 2017 at 3:06 AM, Charles Kozler 
>> wrote:
>>
>>> Bharat -
>>>
>>> 1. Yes. Will need to configure switch port as a trunk and setup your
>>> VLANs and VLAN ID's
>>> 2. Yes
>>> 3. You can still access the hosts. The engine itself crashing or being
>>> down wont stop your VMs or hosts or anything (unless fencing). You can use
>>> virsh
>>> 4. My suggestion here is start immediately after a fresh server install
>>> and yum update. Installer does a lot and checks a lot and wont like things:
>>> ex - you setup ovirtmgmt bridged network yourself
>>> 5. Yes. See #1, usually what I do is each ovirt node I have I set an IP
>>> of .5, then .6, and so on. This way I can be sure my network itself is
>>> working before adding a VM and attaching that NIC to it
>>>
>>> On Tue, Sep 12, 2017 at 4:41 PM, Donny Davis 
>>> wrote:
>>>
 1. Yes, you can do this
 2. Yes, In linux it's called bonding and this can be done from the UI
 3. You can get around using the Engine machine if required with virsh
 or virt-manager - however I would just wait for the manager to migrate and
 start on another host in the cluster
 4.  The deployment will take care of everything for you. You just need
 an IP
 5. Yes, you can use vlans or virtual networking(NSXish) called OVS in
 oVirt.

 I noticed on your deployment machines 2 and 3 have the same IP. Might
 want to fix that before deploying

 Happy trails
 ~D


 On Tue, Sep 12, 2017 at 2:00 PM, Tailor, Bharat <
 bha...@synergysystemsindia.com> wrote:

> Hi Charles,
>
> Thank you so much to share a cool stuff with us.
>
> My doubts are still not cleared.
>
>
>1. What If I have only single Physical network adaptor? Can't I
>use it for management network & production network both.
>2. If I have two Physical network adaptor, Can I configure NIC
>teaming as like Vmware ESXi.
>3. What If my ovirt machine fails during production period? In
>vmware we can access ESXi hosts and VM without Vcenter and do all the
>stuffs. Can we do the same with Ovirt & KVM.
>4. To deploy ovirt engine VM, what kind of configuration I'll have
>to do on network adaptors? (eg. just configure IP on physical network 
> or
>have to create br0 for it.)
>5. Can I make multiple VM networks for vlan configuration?
>
>
> Regrards
> Bharat Kumar
>
> G15- Vinayak Nagar complex,Opp.Maa Satiya, ayad
> Udaipur (Raj.)
> 313001
> Mob: +91-9950-9960-25
>
>
>
>
>
> On Tue, Sep 12, 2017 at 9:30 PM, Charles Kozler 
> wrote:
>
>>
>> Interestingly enough I literally just went through this same thing
>> with a slight variation.
>>
>> Note to the below: I am not sure if this would be considerd best
>> practice or good for something long term support but I made due with 
>> what I
>> had
>>
>> I had 10Gb cards for my storage network but no 10Gb switch, so I
>> direct connected them with some fun routing and /etc/hosts settings. I 
>> also
>> didnt want my storage network on a routed network (have firewalls in the
>> way of VLANs) and I wanted the network separate from my ovirtmgmt - and, 
>> as
>> I said, had no switches for 10Gb. Here is what you need at a bare 
>> minimum.
>> Adapt / change it as you need
>>
>> 1 dedicated NIC on each node for ovirtmgmt. Ex: eth0
>>
>> 1 dedicated NIC to direct connect node 1 and node 2 - eth1 node1
>> 1 dedicated NIC to direct connect node 1 and node 3 - eth2 node1
>>
>> 1 dedicated NIC to direct connect node 2 and node 1 - eth1 node2
>> 1 dedicated NIC to direct connect node 2 and node 3 - eth2 node2
>>
>> 1 dedicated NIC to direct connect node 3 and node 1 - eth1 node3
>> 1 dedicated NIC to direct connect node 3 and node 2 - eth2 node3
>>

[ovirt-users] mode 4 bonding for VMs with NetworkManager anyone?

[Gianluca Cecchi]

Hello,
I'm testing ovirt node, both 4.1.5 and 4.1.6rc2.
I see that in both versions the network stack is configured with
NetworkManager enabled.

With plain CentOS I always disabled NetworkManager and only used classical
network service alone, so I have not background with NM, related to
hypervisor.

I have configured a vlan (untagged) for VMs, using bonding mode=4 (802.3ad).

I have some problems with my VMs: they are reachable from some parts and
not from others.

In parallel I have already asked network guys to crosscheck network
configurations of the datacenter, but I would like to have confirmation
that other ones are already using with success the combination of:

- NetworkManager on hypervisor
- bonding mode = 4 for VMs traffic

Another question for another aspect I never understood: with an environment
in the past (before 3.5 times if I remember well) I used 802.3ad but I had
to set lacp_rate=1 (fast) because I had connection problems with the
default lacp_rate=0 (slow) parameter.
I see that still the default is lacp_rate=0
Could it be the same this time? Is there any reason to set default
lacp_rate=0 in oVirt (or the reverse... ;-)?

Thanks in advance,
Gianluca
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Hyper converged network setup

[Yaniv Kaul]

On Wed, Sep 13, 2017 at 8:42 AM, Tailor, Bharat <
bha...@synergysystemsindia.com> wrote:

> Hi Charles & Donny,
>
> Thank you so much.
>
> @Donny my 3rd node's IP is 192.168.100.17(Mentioned wrong in above mail).
> I was trying to install ovirt ova on test2.localdomain. I've cleared all
> the steps and at last I got a message like "Engine is still unreachable".
> Kindly help me to troubleshoot it.
>
> @Ykaul How can I register myself in mailing list?
>

http://lists.ovirt.org/mailman/listinfo/users

Y.


>
> Regrards
> Bharat Kumar
>
> G15- Vinayak Nagar complex,Opp.Maa Satiya, ayad
> Udaipur (Raj.)
> 313001
> Mob: +91-9950-9960-25
>
>
>
>
>
> On Wed, Sep 13, 2017 at 3:06 AM, Charles Kozler 
> wrote:
>
>> Bharat -
>>
>> 1. Yes. Will need to configure switch port as a trunk and setup your
>> VLANs and VLAN ID's
>> 2. Yes
>> 3. You can still access the hosts. The engine itself crashing or being
>> down wont stop your VMs or hosts or anything (unless fencing). You can use
>> virsh
>> 4. My suggestion here is start immediately after a fresh server install
>> and yum update. Installer does a lot and checks a lot and wont like things:
>> ex - you setup ovirtmgmt bridged network yourself
>> 5. Yes. See #1, usually what I do is each ovirt node I have I set an IP
>> of .5, then .6, and so on. This way I can be sure my network itself is
>> working before adding a VM and attaching that NIC to it
>>
>> On Tue, Sep 12, 2017 at 4:41 PM, Donny Davis 
>> wrote:
>>
>>> 1. Yes, you can do this
>>> 2. Yes, In linux it's called bonding and this can be done from the UI
>>> 3. You can get around using the Engine machine if required with virsh or
>>> virt-manager - however I would just wait for the manager to migrate and
>>> start on another host in the cluster
>>> 4.  The deployment will take care of everything for you. You just need
>>> an IP
>>> 5. Yes, you can use vlans or virtual networking(NSXish) called OVS in
>>> oVirt.
>>>
>>> I noticed on your deployment machines 2 and 3 have the same IP. Might
>>> want to fix that before deploying
>>>
>>> Happy trails
>>> ~D
>>>
>>>
>>> On Tue, Sep 12, 2017 at 2:00 PM, Tailor, Bharat <
>>> bha...@synergysystemsindia.com> wrote:
>>>
 Hi Charles,

 Thank you so much to share a cool stuff with us.

 My doubts are still not cleared.


1. What If I have only single Physical network adaptor? Can't I use
it for management network & production network both.
2. If I have two Physical network adaptor, Can I configure NIC
teaming as like Vmware ESXi.
3. What If my ovirt machine fails during production period? In
vmware we can access ESXi hosts and VM without Vcenter and do all the
stuffs. Can we do the same with Ovirt & KVM.
4. To deploy ovirt engine VM, what kind of configuration I'll have
to do on network adaptors? (eg. just configure IP on physical network or
have to create br0 for it.)
5. Can I make multiple VM networks for vlan configuration?


 Regrards
 Bharat Kumar

 G15- Vinayak Nagar complex,Opp.Maa Satiya, ayad
 Udaipur (Raj.)
 313001
 Mob: +91-9950-9960-25





 On Tue, Sep 12, 2017 at 9:30 PM, Charles Kozler 
 wrote:

>
> Interestingly enough I literally just went through this same thing
> with a slight variation.
>
> Note to the below: I am not sure if this would be considerd best
> practice or good for something long term support but I made due with what 
> I
> had
>
> I had 10Gb cards for my storage network but no 10Gb switch, so I
> direct connected them with some fun routing and /etc/hosts settings. I 
> also
> didnt want my storage network on a routed network (have firewalls in the
> way of VLANs) and I wanted the network separate from my ovirtmgmt - and, 
> as
> I said, had no switches for 10Gb. Here is what you need at a bare minimum.
> Adapt / change it as you need
>
> 1 dedicated NIC on each node for ovirtmgmt. Ex: eth0
>
> 1 dedicated NIC to direct connect node 1 and node 2 - eth1 node1
> 1 dedicated NIC to direct connect node 1 and node 3 - eth2 node1
>
> 1 dedicated NIC to direct connect node 2 and node 1 - eth1 node2
> 1 dedicated NIC to direct connect node 2 and node 3 - eth2 node2
>
> 1 dedicated NIC to direct connect node 3 and node 1 - eth1 node3
> 1 dedicated NIC to direct connect node 3 and node 2 - eth2 node3
>
> You'll need custom routes too:
>
> Route to node 3 from node 1 via eth2
> Route to node 3 from node 2 via eth2
> Route to node 2 from node 3 via eth2
>
> Finally, entries in your /etc/hosts which match to your routes above
>
> Then, advisably, a dedicated NIC per box for VM network but you can
> leverage ovirtmgmt if you are just proofing this out
>
> At this point if you can reach all of your nodes via this dir

Re: [ovirt-users] Hyper converged network setup

[Tailor, Bharat]

Hi Charles & Donny,

Thank you so much.

@Donny my 3rd node's IP is 192.168.100.17(Mentioned wrong in above mail).
I was trying to install ovirt ova on test2.localdomain. I've cleared all
the steps and at last I got a message like "Engine is still unreachable".
Kindly help me to troubleshoot it.

@Ykaul How can I register myself in mailing list?

Regrards
Bharat Kumar

G15- Vinayak Nagar complex,Opp.Maa Satiya, ayad
Udaipur (Raj.)
313001
Mob: +91-9950-9960-25





On Wed, Sep 13, 2017 at 3:06 AM, Charles Kozler 
wrote:

> Bharat -
>
> 1. Yes. Will need to configure switch port as a trunk and setup your VLANs
> and VLAN ID's
> 2. Yes
> 3. You can still access the hosts. The engine itself crashing or being
> down wont stop your VMs or hosts or anything (unless fencing). You can use
> virsh
> 4. My suggestion here is start immediately after a fresh server install
> and yum update. Installer does a lot and checks a lot and wont like things:
> ex - you setup ovirtmgmt bridged network yourself
> 5. Yes. See #1, usually what I do is each ovirt node I have I set an IP of
> .5, then .6, and so on. This way I can be sure my network itself is working
> before adding a VM and attaching that NIC to it
>
> On Tue, Sep 12, 2017 at 4:41 PM, Donny Davis  wrote:
>
>> 1. Yes, you can do this
>> 2. Yes, In linux it's called bonding and this can be done from the UI
>> 3. You can get around using the Engine machine if required with virsh or
>> virt-manager - however I would just wait for the manager to migrate and
>> start on another host in the cluster
>> 4.  The deployment will take care of everything for you. You just need an
>> IP
>> 5. Yes, you can use vlans or virtual networking(NSXish) called OVS in
>> oVirt.
>>
>> I noticed on your deployment machines 2 and 3 have the same IP. Might
>> want to fix that before deploying
>>
>> Happy trails
>> ~D
>>
>>
>> On Tue, Sep 12, 2017 at 2:00 PM, Tailor, Bharat <
>> bha...@synergysystemsindia.com> wrote:
>>
>>> Hi Charles,
>>>
>>> Thank you so much to share a cool stuff with us.
>>>
>>> My doubts are still not cleared.
>>>
>>>
>>>1. What If I have only single Physical network adaptor? Can't I use
>>>it for management network & production network both.
>>>2. If I have two Physical network adaptor, Can I configure NIC
>>>teaming as like Vmware ESXi.
>>>3. What If my ovirt machine fails during production period? In
>>>vmware we can access ESXi hosts and VM without Vcenter and do all the
>>>stuffs. Can we do the same with Ovirt & KVM.
>>>4. To deploy ovirt engine VM, what kind of configuration I'll have
>>>to do on network adaptors? (eg. just configure IP on physical network or
>>>have to create br0 for it.)
>>>5. Can I make multiple VM networks for vlan configuration?
>>>
>>>
>>> Regrards
>>> Bharat Kumar
>>>
>>> G15- Vinayak Nagar complex,Opp.Maa Satiya, ayad
>>> Udaipur (Raj.)
>>> 313001
>>> Mob: +91-9950-9960-25
>>>
>>>
>>>
>>>
>>>
>>> On Tue, Sep 12, 2017 at 9:30 PM, Charles Kozler 
>>> wrote:
>>>

 Interestingly enough I literally just went through this same thing with
 a slight variation.

 Note to the below: I am not sure if this would be considerd best
 practice or good for something long term support but I made due with what I
 had

 I had 10Gb cards for my storage network but no 10Gb switch, so I direct
 connected them with some fun routing and /etc/hosts settings. I also didnt
 want my storage network on a routed network (have firewalls in the way of
 VLANs) and I wanted the network separate from my ovirtmgmt - and, as I
 said, had no switches for 10Gb. Here is what you need at a bare minimum.
 Adapt / change it as you need

 1 dedicated NIC on each node for ovirtmgmt. Ex: eth0

 1 dedicated NIC to direct connect node 1 and node 2 - eth1 node1
 1 dedicated NIC to direct connect node 1 and node 3 - eth2 node1

 1 dedicated NIC to direct connect node 2 and node 1 - eth1 node2
 1 dedicated NIC to direct connect node 2 and node 3 - eth2 node2

 1 dedicated NIC to direct connect node 3 and node 1 - eth1 node3
 1 dedicated NIC to direct connect node 3 and node 2 - eth2 node3

 You'll need custom routes too:

 Route to node 3 from node 1 via eth2
 Route to node 3 from node 2 via eth2
 Route to node 2 from node 3 via eth2

 Finally, entries in your /etc/hosts which match to your routes above

 Then, advisably, a dedicated NIC per box for VM network but you can
 leverage ovirtmgmt if you are just proofing this out

 At this point if you can reach all of your nodes via this direct
 connect IPs then you setup gluster as you normally would referencing your
 entries in /etc/hosts when you call "gluster volume create"

 In my setup, as I said, I had 2x 2 port PCIe 10Gb cards per server so I
 setup LACP as well as you can see below

 This is what my Frankenstein POC lo

[ovirt-users] Question: Where does Ovirt stores VM snapshots?

[Shashwat shagun]

Hi,
I’m new to Ovirt, I just wanted to know where does Ovirt stores VM snapshots 
(On the hosts?) and
It stores the VM virtual hard drives on hosts right? Because wouldn’t it’ll be 
slow if they stores it on a Network drive?

P.S sorry for my bad English, English is not my first language


Regards,
Shashwat Shagun
m...@shashwat.tech

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

Re: [ovirt-users] epel and collectd

[Yedidyah Bar David]

On Wed, Sep 13, 2017 at 11:39 AM, Sandro Bonazzola 
wrote:

>
>
> 2017-09-12 15:03 GMT+02:00 Fabrice Bacchella 
> :
>
>> In the releases notes, even for the 4.6 rc, I see:
>>
>> https://www.ovirt.org/release/4.1.6/
>> ...
>> OpsTools currently includes collectd 5.7.0, and the write_http plugin is
>> packaged separately.
>>
>> But if I check the current state:
>> yum list collectd-write_http collectd
>> ...
>> collectd.x86_64
>>5.7.2-1.el7
>> @centos-opstools-release
>> collectd-write_http.x86_64
>>   5.7.2-1.el7
>> @centos-opstools-release
>>
>> So I think the warning is not needed any more. One can uses both ovirt
>> and epel without any special check.
>>
>
>
> Pushed https://gerrit.ovirt.org/81667 taking care of this too. In
> general, I still consider EPEL harmful so just dropped the part related to
> collectd.
>

Please note that there are still certain differences between OpsTools SIG
repo and EPEL in collectd* packaging, so you can be hit in the future
exactly the same way if you happen to mix and EPEL releases a new version.


>
>
>
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>
>
>
> --
>
> SANDRO BONAZZOLA
>
> ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D
>
> Red Hat EMEA 
> 
> TRIED. TESTED. TRUSTED. 
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>


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

Re: [ovirt-users] ovirt high points

[Eduardo Mayoral]

My 0.02€

Cost aside (which is actually not the main reason for the organization I
work for):

  * Avoid putting all your eggs in one basket / vendor. This holds true
for any particula area. (Virtualization, storage, network equipment,
server HW). This gives you leverage when negotiating purchases /
renewals / maintenance contract.
  * The community support for oVirt ABSOLUTELY ROCKS
  * If you are planning to do something with openstack in the short or
mid term, I think oVirt is a nice path to go.
  o Integration with Glance / Cinder / Neutron is cool.
  o The hypervisor is the same (KVM).
  o I have successfully moved VM images to/from openstack and they
worked seamlessly.
  o At the same time, the architecture is quite similar to VCenter,
and import of VMs from VMWare works pretty well .
  * As the compute nodes (hosts) are mostly plain CentOS 7 it is much
easier to integrate them with whatever you have in place for
monitoring, configuration management, backup...
  * The user portal with user quotas can work nicely as self-service for
users, depending on your needs.
  * Version update procedures way less painful with oVirt than with VMWare.
  * On the downside, I think that functionality-wise, VMWare still has
an edge, but oVirt is good-enough for a lot of use cases.

Eduardo Mayoral Jimeno (emayo...@arsys.es)
Administrador de sistemas. Departamento de Plataformas. Arsys internet.
+34 941 620 145 ext. 5153

On 07/09/17 13:33, david caughey wrote:
> Hi Folks,
>
> I'm giving a demo of our new 3 node oVirt deployment next week and am
> looking for some high points that I can give to the Managers that will
> be a sell point.
> If you could help with the below questions I would really appreciate it:
>
> Who are the big users of oVirt??
>
> Why oVirt and not vMware??
> (we are a big vMware house so free doesn't cover it)
>
> What is the future for oVirt??
>
> Why do you use oVirt??
>
> Any links or ideas appreciated,
>
> BR/David
>
>
> ___
> 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] epel and collectd

[Sandro Bonazzola]

2017-09-12 15:03 GMT+02:00 Fabrice Bacchella :

> In the releases notes, even for the 4.6 rc, I see:
>
> https://www.ovirt.org/release/4.1.6/
> ...
> OpsTools currently includes collectd 5.7.0, and the write_http plugin is
> packaged separately.
>
> But if I check the current state:
> yum list collectd-write_http collectd
> ...
> collectd.x86_64
>  5.7.2-1.el7
>   @centos-opstools-release
> collectd-write_http.x86_64
>   5.7.2-1.el7
> @centos-opstools-release
>
> So I think the warning is not needed any more. One can uses both ovirt and
> epel without any special check.
>


Pushed https://gerrit.ovirt.org/81667 taking care of this too. In general,
I still consider EPEL harmful so just dropped the part related to collectd.



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



-- 

SANDRO BONAZZOLA

ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D

Red Hat EMEA 

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