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

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