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

[Charles Kozler]

Sorry, I meant "remove the static configuration of 1G full duplex and set
back to auto-negotiation to the 10G when ready"

On Thu, Sep 14, 2017 at 6:19 PM, Charles Kozler 
wrote:

> You could, I believe, turn off auto-negotiation and set it 1G full duplex
> on both sides and then add the links in and then remove the old 1G's when
> ready then remove auto-negotiation from the 10G
>
> But, it would ultimately be much, much easier to create a new LAG and then
> take an outage on ovirt and move everything to the new one
>
> On Thu, Sep 14, 2017 at 6:51 AM, Misak Khachatryan 
> wrote:
>
>> Hi,
>>
>> JunOS supports LAG over links with different speeds, so if you have MX
>> series routers in-between, you can try to accomplish that.
>> But it's always better to be on safe side, it's very risky to use in
>> production, IMHO.
>>
>> Best regards,
>> Misak Khachatryan
>>
>>
>> On Thu, Sep 14, 2017 at 2:41 PM, Yaniv Kaul  wrote:
>> >
>> >
>> > On Thu, Sep 14, 2017 at 1:21 AM, Chris Adams  wrote:
>> >>
>> >> 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 highly doubt that's feasible. They usually are in the same speeds...
>> > Y.
>> >
>> >>
>> >>
>> >> 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
>> >
>> >
>> >
>> > ___
>> > 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] Different link speeds in LACP LAG?

[Charles Kozler]

You could, I believe, turn off auto-negotiation and set it 1G full duplex
on both sides and then add the links in and then remove the old 1G's when
ready then remove auto-negotiation from the 10G

But, it would ultimately be much, much easier to create a new LAG and then
take an outage on ovirt and move everything to the new one

On Thu, Sep 14, 2017 at 6:51 AM, Misak Khachatryan  wrote:

> Hi,
>
> JunOS supports LAG over links with different speeds, so if you have MX
> series routers in-between, you can try to accomplish that.
> But it's always better to be on safe side, it's very risky to use in
> production, IMHO.
>
> Best regards,
> Misak Khachatryan
>
>
> On Thu, Sep 14, 2017 at 2:41 PM, Yaniv Kaul  wrote:
> >
> >
> > On Thu, Sep 14, 2017 at 1:21 AM, Chris Adams  wrote:
> >>
> >> 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 highly doubt that's feasible. They usually are in the same speeds...
> > Y.
> >
> >>
> >>
> >> 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
> >
> >
> >
> > ___
> > 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] Server Not Responding

[Piotr Kliczewski]

Bryan,

In your engine logs I see :

2017-09-13 04:07:07,599-05 ERROR
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetAllVmStatsVDSCommand]
(DefaultQuartzScheduler3) [] Command 'GetAllVmStatsVDSCommand(HostName
= vm-host-colo-1, VdsIdVDSCommandParametersBase:{runAsync='true',
hostId='e75d4446-9bfc-47cb-8bf8-a2e681720b66'})' execution failed:
VDSGenericzException: VDSNetworkException: Heartbeat exceeded

It would br great to understand what happened on vdsm side because the
engine was still trying to connect at: 2017-09-13 09:30:46,275-05

In vdsm logs you provided I see that they start at 2017-09-13
09:01:08,895-0500 and end at 2017-09-13 09:53:24,760-0500.

Please provide vdsm logs from the time the issue occurred.

Thanks,
Piotr

On Wed, Sep 13, 2017 at 5:09 PM, Bryan Sockel  wrote:
>
> Hi
>
> Having an issue where i frequently have a server that is set to not
> responsive.  VM's are set to unknown status, but still continue to run.
> This issue is isolated to just a single host.  My Setup is currently a 2
> Data Center Configuration with 2 servers in each data center.  Issue is
> occurring at my remote site.
>
> The primary storage volumes are setup on dedicated hardware, with the
> arbiter running on the server that is having issues.  There is also another
> gluster replica volume hosted on this box, the replica is the other
> dedicated server.
>
> The logs are showing:
>
> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand]
> (DefaultQuartzScheduler8) [] Command 'GetCapabilitiesVDSCommand(HostName =
> vm-host-colo-1, VdsIdAndVdsVDSCommandParametersBase:{runAsync='true',
> hostId='e75d4446-9bfc-47cb-8bf8-a2e681720b66',
> vds='Host[vm-host-colo-1,e75d4446-9bfc-47cb-8bf8-a2e681720b66]'})' execution
> failed: java.rmi.ConnectException: Connection timeout
>
> [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring]
> (DefaultQuartzScheduler8) [] Failure to refresh host 'vm-host-colo-1'
> runtime info: java.rmi.ConnectException: Connection timeout.
>
>
> I have attached the vdsm.log from the server with issues and the engine.log.
>
> Thanks
>
> Bryan Sockel
>
>
> ___
> 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] Update posgtresql on engine

[Gianluca Cecchi]

Suppose an update of postgresql server rpm (eg security issue) is released
and you have to install it.

Preliminary:
Put in global maintenance if SHE environment

Is this below then a good workflow of commands to run on engine?
systemctl stop ovirt-engine
systemctl stop ovirt-engine-dwhd
systemctl stop postgresql

yum update postgresql*

shutdown engine vm

start engine vm or exit from global maintenance to have SHE automatically
start


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

[ovirt-users] engine randomly updated 1 package on all my hosts overnight

[Charles Kozler]

I received an alert from OSSEC HIDS that a package was installed at 00:59.
Nobody uses this infrastructure but me

Upon investigation I find this

Sep 14 00:59:18 ovirthost1 sshd[93263]: Accepted publickey for root from
10.0.16.50 port 50197 ssh2: RSA
1c:fc:0d:b8:40:2c:bf:87:f7:8f:b2:52:0b:c4:f6:4d
Sep 14 00:59:18 ovirthost1 sshd[93263]: pam_unix(sshd:session): session
opened for user root by (uid=0)
Sep 14 00:59:46 ovirthost1 sshd[93263]: pam_unix(sshd:session): session
closed for user root

10.0.16.50 is my ovirt engine

And the yum log

Sep 14 00:59:28 Updated: iproute-3.10.0-87.el7.x86_64

However, what is baffling to me is that this is a cluster I setup about 9
months ago and have not updated at all (its a testing env for VM systems)

Why would ovirt seemingly randomly update and install a package? I know the
engine checks for updates on hosts but this is the first time in my time
using ovirt that ovirt instructed a host to install a package. This
occurred on all of my ovirt nodes in this infrastructure (3)

ovirt Version 4.0.1.1-1.el7.centos
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

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

[Matthias Leopold]

Hi Daniel and other friendly contributors,

finally i sorted out how to set provisioned_size/initial_size correctly 
in upload_disk.py and my error is gone. It wasn't so easy, but maybe i 
took an awkard route when starting with a preallocated qcow2 image. In 
this special case you have to set provisioned_size to st_size, whereas 
with sparse images provisioned_size is "virtual size" from "qemu-img 
info". This may seem obvious to others, i took the hard route.


My approach stems from my desire to repeat the exact example in 
upload_disk.py (which uses a qcow image) and my actual use case, which 
is uploading a rather large image converted from vmdk (i only tested 
this with raw format yet), so i wanted to have some "real large" data to 
upload.


@nsoffer:
I'll open a bug for better ovirt-imageio-daemon as soon as i can.

thanks a lot for help
matthias

Am 2017-09-13 um 16:49 schrieb 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 
> 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
 >>
  

Re: [ovirt-users] update to centos 7.4

[FERNANDO FREDIANI]

It has been released yesterday. I don't thing such a quick upgrade is 
recommended. It might work well but I wouldn't find strange if there are 
issues until this is fully tested with current oVirt versions.


Fernando

On 14/09/2017 11:01, Nathanaël Blanchet wrote:

Hi all,

Now centos 7.4 is available, is it recommanted to update nodes (and 
engine os) knowing that ovirt 4.1 is officially supported for 7.3 or 
later?




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

Re: [ovirt-users] V4.1 questions

[Alexander Wels]

On Thursday, September 14, 2017 8:56:05 AM EDT Colin Coe wrote:
> Hi Ryan and thanks for the quick reply.
> 
> This is an entirely new system, no VM, no nothing.  This was built for
> testing v4.1.  I'll log a case with GSS on this if it  is not normal.
> 
> Bit confiused, so what do I need to do for the Installation -> Check for
> Upgrades to work in RHV-M?  I'm using an old RHEV-H 7.1 image for the
> hypervisors so there should definitely be an upgrade available.
> 
> Also, any thoughts on the webUI timeout?
> 

Default logout timeout is 30 minutes. You can configure this using engine-
config

For instance:

engine-config -g UserSessionTimeoutInterval will return 30

you can change it using engine-config as well for instance

engine-config -s UserSessionTimeoutInterval=60 will set it to 1 hour.

If logging is taking a long time and the UI is not very responsive you 
probably have one or more of the following:

The engine is running in a VM and there is not enough entropy (logging in 
takes a long time).
The DNS/rDNS is not configured properly and the engine cannot resolve itself 
(Sluggish UI, things take 30-60 seconds to happen in UI)

> Thanks again
> 
> CC
> 
> On Thu, Sep 14, 2017 at 8:45 PM, Ryan Barry  wrote:
> > On Thu, Sep 14, 2017 at 8:36 AM, Colin Coe  wrote:
> >> Hi all
> >> 
> >> We're in the process of upgrading from RHEV 3.5 to 4.1.5 and I have a
> >> couple of questions.
> >> 
> >> RHV 4.1.5 takes between 10-15 minutes to become usable after a service
> >> restart, is this expected or is something wrong with our environment?
> > 
> > 10-15 minutes seems long, but it depends on the database. How much
> > historical data is present?
> > 
> >> The webUI seems to timeout and go back to the logon page after a very
> >> short time.  Can this behavior be changed?
> >> 
> >> Lastly, the RH318 course book states that to upgrade a RHEV-H node via
> >> RHEV-M, you need to install the "rhev-hypervisor7" package on the RHEV-M
> >> node.  Is this still correct?
> > 
> > Node/RHVH for 4.x now upgrades straight from yum, so nothing is needed on
> > the engine :)
> > 
> >> Thanks
> >> 
> >> CC
> >> 
> >> ___
> >> Users mailing list
> >> Users@ovirt.org
> >> http://lists.ovirt.org/mailman/listinfo/users
> > 
> > --
> > 
> > RYAN BARRY
> > 
> > SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHEV HYPERVISOR
> > 
> > Red Hat NA 
> > 
> > rba...@redhat.comM: +1-651-815-9306 IM: rbarry
> > 


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

[ovirt-users] update to centos 7.4

[Nathanaël Blanchet]

Hi all,

Now centos 7.4 is available, is it recommanted to update nodes (and 
engine os) knowing that ovirt 4.1 is officially supported for 7.3 or later?


--
Nathanaël Blanchet

Supervision réseau
Pôle Infrastrutures Informatiques
227 avenue Professeur-Jean-Louis-Viala
34193 MONTPELLIER CEDEX 5   
Tél. 33 (0)4 67 54 84 55
Fax  33 (0)4 67 54 84 14
blanc...@abes.fr

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

Re: [ovirt-users] Hyper converged network setup

[Tailor, Bharat]

Hi,

I've reinstall Centos7 Minimal on all three hosts. Installed Ovirt self
hosted ova 4.1 on test1.localdomain.
After installation completed, I got an error like engine vm is unreachable.
I am able to ping engine from both IP and FQDN but unable to access it in
browser. When I check engine VM status I got an error "Failed to connect to
broker".
I've enclosed engine-vm config snap and Error snap for more details. Kind
help to resolve it.


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:14 PM, Tailor, Bharat <
bha...@synergysystemsindia.com> wrote:

> 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 

Re: [ovirt-users] V4.1 questions

[Colin Coe]

Hi Ryan and thanks for the quick reply.

This is an entirely new system, no VM, no nothing.  This was built for
testing v4.1.  I'll log a case with GSS on this if it  is not normal.

Bit confiused, so what do I need to do for the Installation -> Check for
Upgrades to work in RHV-M?  I'm using an old RHEV-H 7.1 image for the
hypervisors so there should definitely be an upgrade available.

Also, any thoughts on the webUI timeout?

Thanks again

CC

On Thu, Sep 14, 2017 at 8:45 PM, Ryan Barry  wrote:

>
>
> On Thu, Sep 14, 2017 at 8:36 AM, Colin Coe  wrote:
>
>> Hi all
>>
>> We're in the process of upgrading from RHEV 3.5 to 4.1.5 and I have a
>> couple of questions.
>>
>> RHV 4.1.5 takes between 10-15 minutes to become usable after a service
>> restart, is this expected or is something wrong with our environment?
>>
>
> 10-15 minutes seems long, but it depends on the database. How much
> historical data is present?
>
>
>>
>> The webUI seems to timeout and go back to the logon page after a very
>> short time.  Can this behavior be changed?
>>
>> Lastly, the RH318 course book states that to upgrade a RHEV-H node via
>> RHEV-M, you need to install the "rhev-hypervisor7" package on the RHEV-M
>> node.  Is this still correct?
>>
>
> Node/RHVH for 4.x now upgrades straight from yum, so nothing is needed on
> the engine :)
>
>
>>
>> Thanks
>>
>> CC
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>
>
> --
>
> RYAN BARRY
>
> SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHEV HYPERVISOR
>
> Red Hat NA 
>
> rba...@redhat.comM: +1-651-815-9306 IM: rbarry
> 
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] oVirt node with SHE on FC

[Ryan Barry]

On Mon, Sep 11, 2017 at 10:39 AM, Gianluca Cecchi  wrote:

> On Mon, Sep 11, 2017 at 4:13 PM, Simone Tiraboschi 
> wrote:
> Are the ovirt repos already setup when I have installed from the iso or do
> I have to install ovirt-release-xx rpm?
>

They're already ready-to-go, so engine will pick up any updates when
there's available.


>
> I'm exploring situations where NGN could be suitable better than full
> CentOS OS for hypervisors and I would like to know clearly advantages and
> limits.
>

The primary advantage is that it's a system which comes ready for oVirt,
and the entire thing is updated in one shot, with rollback capability. So
you can "yum upgrade" from 4.0.3 (for example) to 4.1.5 in one command, and
go back to the old version of something doesn't work as expected.

As of 4.1, we also reinstall any vendor tooling you've installed with yum,
so packages "stick" across images. If all you want is a hypervisor, and you
don't need the flexibility of a full CentOS host, Node is probably a good
choice.


>
> Thanks in advance
>
>>
>> On Sat, Sep 9, 2017 at 8:25 PM, Gianluca Cecchi <
>> gianluca.cec...@gmail.com> wrote:
>>
>>> Hello,
>>> it is not clear to me the exact workflow in case of testing what in
>>> object.
>>>
>>> For sure first step is to install base node from iso.
>>> NGN has no more read only filesystem.
>>> Does this mean that I have to set up eg multipath for FC LUNs (engine
>>> and data domain) before running the engine setup via cockpit?
>>> Or when I specify FC in type of storage domain it would ask and setup
>>> automatically multipath for me?
>>>
>>
>> No, it doesn't: HBA and mutipath are supposed to be directly configured
>> before running hosted-engine-setup.
>> It's exactly the same as for vlan and bonding.
>>
>
> Ah, ok.
> So I can also customize my multipath.conf file on oVirt Node as desired,
> if storage vendor requires it, using
>
> # VDSM REVISION 1.3
> # VDSM PRIVATE
>
> as I do in regular CentOS 7, correct?
>

Yep, you can configure it exactly like CentOS 7.

The VDSM header is not required AFAIK.


>
> And if so, what is the mapping of "1.3" in VDSM REVISION line above?
> I didn't find reference in oVirt docs and also in RHEV kb I only found
> this:
> https://access.redhat.com/solutions/43458
>

The idea of persistence is gone in oVirt Node 4.x, so you don't need to
worry about any of this.


> that doesn't clarify much in my opinion and seems to cover version 4.x in
> the summary of knowledge base article, but then I don't seem to find  its
> real application...
>
> 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

Re: [ovirt-users] V4.1 questions

[Ryan Barry]

On Thu, Sep 14, 2017 at 8:36 AM, Colin Coe  wrote:

> Hi all
>
> We're in the process of upgrading from RHEV 3.5 to 4.1.5 and I have a
> couple of questions.
>
> RHV 4.1.5 takes between 10-15 minutes to become usable after a service
> restart, is this expected or is something wrong with our environment?
>

10-15 minutes seems long, but it depends on the database. How much
historical data is present?


>
> The webUI seems to timeout and go back to the logon page after a very
> short time.  Can this behavior be changed?
>
> Lastly, the RH318 course book states that to upgrade a RHEV-H node via
> RHEV-M, you need to install the "rhev-hypervisor7" package on the RHEV-M
> node.  Is this still correct?
>

Node/RHVH for 4.x now upgrades straight from yum, so nothing is needed on
the engine :)


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


-- 

RYAN BARRY

SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHEV HYPERVISOR

Red Hat NA 

rba...@redhat.comM: +1-651-815-9306 IM: rbarry

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

[ovirt-users] V4.1 questions

[Colin Coe]

Hi all

We're in the process of upgrading from RHEV 3.5 to 4.1.5 and I have a
couple of questions.

RHV 4.1.5 takes between 10-15 minutes to become usable after a service
restart, is this expected or is something wrong with our environment?

The webUI seems to timeout and go back to the logon page after a very short
time.  Can this behavior be changed?

Lastly, the RH318 course book states that to upgrade a RHEV-H node via
RHEV-M, you need to install the "rhev-hypervisor7" package on the RHEV-M
node.  Is this still correct?

Thanks

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

Re: [ovirt-users] Panasas File System panfs POSIX compliant

[Fred Rolland]

Hi,

Can you provide the Vdsm log ?

Thanks,
Fred

On Thu, Sep 7, 2017 at 1:25 AM, Allen Dial  wrote:

> Hello Ovirt users!
>
> I am trying to add a POSIX compliant filesystem to Ovirt but keep getting
> "Error while executing action Add Storage Connection: Problem while trying
> to mount target."
>
> To mount via terminal after adding to fstab the command is  panfs://ipaddress/test> but using that in "Path" results in the above
> mentioned error.
>
> Does anyone here have knowledge of panfs or Panasas or how one might get
> this work?
>
> Thank you,
>
> Allen
>
>
> ___
> 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] AcquireHostIdFailure and code 661

[Neil]

Sorry to re-post, but does anyone have any ideas?

Thank you.

Regards.

Neil Wilson.

On Mon, Sep 11, 2017 at 4:46 PM, Neil  wrote:

> Hi guys,
>
> Please could someone shed some light on this issue I'm facing.
>
> I'm trying to add a new NFS storage domain but when I try add it, I get a
> message saying "Acquire hostID failed" and it fails to add.
>
> I can mount the NFS share manually and I can see that once the attaching
> has failed the NFS share is still mounted on the hosts, as per the
> following...
>
> 172.16.0.11:/raid1/data/_NAS_NFS_Exports_/STOR2 on
> /rhev/data-center/mnt/172.16.0.11:_raid1_data___NAS__NFS__Exports___STOR2
> type nfs (rw,soft,nosharecache,timeo=600,retrans=6,nfsvers=3,addr=
> 172.16.0.11)
>
> Also looking at the folders on the NFS share I can see that some data has
> been written, so it's not a permissions issue...
>
> drwx---r-x+ 4 vdsm kvm 4096 Sep 11 16:08 16ab135b-0362-4d7e-bb11-
> edf5b93535d5
> -rwx---rwx. 1 vdsm kvm0 Sep 11 16:08 __DIRECT_IO_TEST__
>
> I have just upgraded from 3.3 to 3.5 as well as upgraded my 3 hosts in the
> hope it's a known bug, but I'm still encountering the same problem.
>
> It's not a hosted engine and you might see in the logs that I have a
> storage domain that is out of space which I'm aware of, and I'm hoping the
> system using this space will be decommissioned in 2 days
>
> FilesystemSize  Used Avail Use% Mounted on
> /dev/sda2 420G  2.2G  413G   1% /
> tmpfs  48G 0   48G   0% /dev/shm
> 172.16.0.10:/raid0/data/_NAS_NFS_Exports_/RAID1_1TB
>   915G  915G  424M 100% /rhev/data-center/mnt/172.16.
> 0.10:_raid0_data___NAS__NFS__Exports___RAID1__1TB
> 172.16.0.10:/raid0/data/_NAS_NFS_Exports_/STORAGE1
>   5.5T  3.7T  1.8T  67% /rhev/data-center/mnt/172.16.
> 0.10:_raid0_data___NAS__NFS__Exports___STORAGE1
> 172.16.0.20:/data/ov-export
>   3.6T  2.3T  1.3T  65% /rhev/data-center/mnt/172.16.
> 0.20:_data_ov-export
> 172.16.0.11:/raid1/data/_NAS_NFS_Exports_/4TB
>   3.6T  2.0T  1.6T  56% /rhev/data-center/mnt/172.16.
> 0.11:_raid1_data___NAS__NFS__Exports___4TB
> 172.16.0.253:/var/lib/exports/iso
>   193G   42G  141G  23% /rhev/data-center/mnt/172.16.
> 0.253:_var_lib_exports_iso
> 172.16.0.11:/raid1/data/_NAS_NFS_Exports_/STOR2
>   5.5T  3.7G  5.5T   1% /rhev/data-center/mnt/172.16.
> 0.11:_raid1_data___NAS__NFS__Exports___STOR2
>
> The "STOR2" above is left mounted after attempting to add the new NFS
> storage domain.
>
> Engine details:
> Fedora release 19 (Schrödinger’s Cat)
> ovirt-engine-dbscripts-3.5.0.1-1.fc19.noarch
> ovirt-release34-1.0.3-1.noarch
> ovirt-image-uploader-3.5.0-1.fc19.noarch
> ovirt-engine-websocket-proxy-3.5.0.1-1.fc19.noarch
> ovirt-log-collector-3.5.0-1.fc19.noarch
> ovirt-release35-006-1.noarch
> ovirt-engine-setup-3.5.0.1-1.fc19.noarch
> ovirt-release33-1.0.0-0.1.master.noarch
> ovirt-engine-tools-3.5.0.1-1.fc19.noarch
> ovirt-engine-lib-3.5.0.1-1.fc19.noarch
> ovirt-engine-sdk-python-3.5.0.8-1.fc19.noarch
> ovirt-host-deploy-java-1.3.0-1.fc19.noarch
> ovirt-engine-backend-3.5.0.1-1.fc19.noarch
> sos-3.1-1.1.fc19.ovirt.noarch
> ovirt-engine-setup-base-3.5.0.1-1.fc19.noarch
> ovirt-engine-extensions-api-impl-3.5.0.1-1.fc19.noarch
> ovirt-engine-webadmin-portal-3.5.0.1-1.fc19.noarch
> ovirt-engine-setup-plugin-ovirt-engine-3.5.0.1-1.fc19.noarch
> ovirt-iso-uploader-3.5.0-1.fc19.noarch
> ovirt-host-deploy-1.3.0-1.fc19.noarch
> ovirt-engine-setup-plugin-ovirt-engine-common-3.5.0.1-1.fc19.noarch
> ovirt-engine-3.5.0.1-1.fc19.noarch
> ovirt-engine-setup-plugin-websocket-proxy-3.5.0.1-1.fc19.noarch
> ovirt-engine-userportal-3.5.0.1-1.fc19.noarch
> ovirt-engine-cli-3.5.0.5-1.fc19.noarch
> ovirt-engine-restapi-3.5.0.1-1.fc19.noarch
> libvirt-daemon-driver-nwfilter-1.1.3.2-1.fc19.x86_64
> libvirt-daemon-driver-qemu-1.1.3.2-1.fc19.x86_64
> libvirt-daemon-driver-libxl-1.1.3.2-1.fc19.x86_64
> libvirt-daemon-driver-secret-1.1.3.2-1.fc19.x86_64
> libvirt-daemon-config-network-1.1.3.2-1.fc19.x86_64
> libvirt-daemon-driver-storage-1.1.3.2-1.fc19.x86_64
> libvirt-daemon-driver-network-1.1.3.2-1.fc19.x86_64
> libvirt-1.1.3.2-1.fc19.x86_64
> libvirt-daemon-kvm-1.1.3.2-1.fc19.x86_64
> libvirt-client-1.1.3.2-1.fc19.x86_64
> libvirt-daemon-driver-nodedev-1.1.3.2-1.fc19.x86_64
> libvirt-daemon-driver-uml-1.1.3.2-1.fc19.x86_64
> libvirt-daemon-driver-xen-1.1.3.2-1.fc19.x86_64
> libvirt-daemon-driver-interface-1.1.3.2-1.fc19.x86_64
> libvirt-daemon-config-nwfilter-1.1.3.2-1.fc19.x86_64
> libvirt-daemon-1.1.3.2-1.fc19.x86_64
> libvirt-daemon-qemu-1.1.3.2-1.fc19.x86_64
> libvirt-daemon-driver-vbox-1.1.3.2-1.fc19.x86_64
> libvirt-daemon-driver-lxc-1.1.3.2-1.fc19.x86_64
> qemu-system-lm32-1.4.2-15.fc19.x86_64
> qemu-system-s390x-1.4.2-15.fc19.x86_64
> libvirt-daemon-driver-qemu-1.1.3.2-1.fc19.x86_64
> qemu-system-ppc-1.4.2-15.fc19.x86_64
> 

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

[Misak Khachatryan]

Hi,

JunOS supports LAG over links with different speeds, so if you have MX
series routers in-between, you can try to accomplish that.
But it's always better to be on safe side, it's very risky to use in
production, IMHO.

Best regards,
Misak Khachatryan


On Thu, Sep 14, 2017 at 2:41 PM, Yaniv Kaul  wrote:
>
>
> On Thu, Sep 14, 2017 at 1:21 AM, Chris Adams  wrote:
>>
>> 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 highly doubt that's feasible. They usually are in the same speeds...
> Y.
>
>>
>>
>> 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
>
>
>
> ___
> 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] Different link speeds in LACP LAG?

[Yaniv Kaul]

On Thu, Sep 14, 2017 at 1:21 AM, Chris Adams  wrote:

> 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 highly doubt that's feasible. They usually are in the same speeds...
Y.


>
> 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
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

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

[Fred Rolland]

Hi,

Welcome !!

The VM disks are stored on Storage Server over the network (NFS,ISCSI,FC)
[1] , unless you use Hyperconverged setup [2]

The disks snapshots are on the same location. Ovirt makes the image read
only and add a COW layer above it.

Regards,

Fred

[1]
https://www.ovirt.org/documentation/install-guide/chap-Configuring_Storage/
[2]
https://www.ovirt.org/develop/release-management/features/gluster/glusterfs-hyperconvergence/

On Wed, Sep 13, 2017 at 12:33 AM, Shashwat shagun  wrote:

> 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
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users