[ovirt-users] Limitation in using Ovirt SSO Token

[Yaniv Kaul]

On Mar 8, 2018 7:35 PM, "Hari Prasanth Loganathan" <
hariprasanth.l at msystechnologies.com> wrote:

Hi Yaniv,

To give an example, We are planning to create and manage our VM's using
oVirt.
Instead of managing oVirt using UI, We will be writing the script which
hits the oVirt engine periodically for different functionality.


May I suggest Ansible, or any of our SDKs?
It'll surely make your work more productive and quite likely higher
performance (as it's already quite built for performance, with pipelining,
multiplexing, compression and connection management).

so We would like to take a benchmark to finalise the number of hits to
ovirt.


Hits for which functionality exactly?


This is what we are trying to achieve.


I suspect you focus too much on synthetic benchmark rather than a real use
case.
Y.


Coming to my query,
What is the difference between sso token and session maintance in oVirt, If
I have a token timeout of 4 days, How the concept of session plays a role
in oVirt?

Thanks,
Hari


DISCLAIMER

The information in this e-mail is confidential and may be subject to legal
privilege. It is intended solely for the addressee. Access to this e-mail
by anyone else is unauthorized. If you have received this communication in
error, please address with the subject heading "Received in error," send to
it at msystechnologies.com,  then delete the e-mail and destroy any copies of
it. If you are not the intended recipient, any disclosure, copying,
distribution or any action taken or omitted to be taken in reliance on it,
is prohibited and may be unlawful. The views, opinions, conclusions and
other information expressed in this electronic mail and any attachments are
not given or endorsed by the company unless otherwise indicated by an
authorized representative independent of this message.
MSys cannot guarantee that e-mail communications are secure or error-free,
as information could be intercepted, corrupted, amended, lost, destroyed,
arrive late or incomplete, or contain viruses, though all reasonable
precautions have been taken to ensure no viruses are present in this e-mail.
As our company cannot accept responsibility for any loss or damage arising
from the use of this e-mail or attachments we recommend that you subject
these to your virus checking procedures prior to use
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20180309/07e5c1e2/attachment.html>