Re: [ovirt-users] Limitation in using Ovirt SSO Token
On Mar 8, 2018 7:35 PM, "Hari Prasanth Loganathan" < hariprasant...@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 i...@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 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Limitation in using Ovirt SSO Token
Yes, we will take a SSO token using SSO auth Rest API call and use the same token for all the API hits for next 4 days (Example If 4 days is the SSO token timeout). Is there an issue with using like that? If there is a session concept there for SSO token in using as Rest API? On Thu, Mar 8, 2018 at 11:05 PM, Hari Prasanth Loganathan < hariprasant...@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. so We would > like to take a benchmark to finalise the number of hits to ovirt. > > This is what we are trying to achieve. > > 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 i...@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 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Limitation in using Ovirt SSO Token
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. so We would like to take a benchmark to finalise the number of hits to ovirt. This is what we are trying to achieve. 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 i...@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 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Limitation in using Ovirt SSO Token
On Mar 8, 2018 3:53 PM, "Hari Prasanth Loganathan" < hariprasant...@msystechnologies.com> wrote: Hi Team, I would like to know, Is there any limitation in using the same sso token for multiple request. Are you reusing it or abusing it? Are you actually using it in a single session, to avoid reauthentication, or just sharing between multiple sessions? While I'd still would not want to see the engine affected by such abuse, the latter is quite atypical use case. Can you share engine and server logs? And again, it'd be very helpful if you could share what you'd like to achieve and we'll gladly assist. Y. I observe that when I use the same sso token for more than 900 HTTP Rest request, the application went down. Is there any limitation in using same SSO token? I could see that my status is showing as ACTIVE and memory and CPU seem fine. Still, the oVirt is not reachable and I need to restart it to access again. sudo systemctl status ovirt-engine.service -l ● ovirt-engine.service - oVirt Engine Loaded: loaded (/usr/lib/systemd/system/ovirt-engine.service; enabled; vendor preset: disabled) Active: active (running) since Thu 2018-03-08 19:15:10 IST; 30s ago Main PID: 10370 (ovirt-engine.py) CGroup: /system.slice/ovirt-engine.service ├─10370 /usr/bin/python /usr/share/ovirt-engine/ services/ovirt-engine/ovirt-engine.py --redirect-output --systemd=notify start └─10423 ovirt-engine -server -XX:+TieredCompilation -Xms5961M -Xmx5961M -Djava.awt.headless=true -Dsun.rmi.dgc.client.gcInterval=360 -Dsun.rmi.dgc.server.gcInterval=360 -Djsse.enableSNIExtension=false -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/var/log/ovirt-engine/dump -Djava.util.logging.manager=org.jboss.logmanager -Dlogging.configuration=file:///var/lib/ovirt-engine/jboss_ runtime/config/ovirt-engine-logging.properties -Dorg.jboss.resolver.warning=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djboss.server.default.config=ovirt-engine -Djboss.home.dir=/usr/share/ovirt-engine-wildfly -Djboss.server.base.dir=/usr/share/ovirt-engine -Djboss.server.data.dir=/var/lib/ovirt-engine -Djboss.server.log.dir=/var/log/ovirt-engine -Djboss.server.config.dir=/var/lib/ovirt-engine/jboss_runtime/config -Djboss.server.temp.dir=/var/lib/ovirt-engine/jboss_runtime/tmp -Djboss.controller.temp.dir=/var/lib/ovirt-engine/jboss_runtime/tmp -jar /usr/share/ovirt-engine-wildfly/jboss-modules.jar -mp /usr/share/ovirt-engine/modules/common:/usr/share/ ovirt-engine-extension-aaa-jdbc/modules:/usr/share/ovirt-engine-wildfly/modules -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -c ovirt-engine.xml Mar 08 19:15:10 ovirtengine.localdomain systemd[1]: Starting oVirt Engine... Mar 08 19:15:10 ovirtengine.localdomain ovirt-engine.py[10370]: 2018-03-08 19:15:10,228+0530 ovirt-engine: INFO _detectJBossVersion:187 Detecting JBoss version. Running: /usr/lib/jvm/jre/bin/java ['ovirt-engine-version', '-server', '-XX:+TieredCompilation', '-Xms5961M', '-Xmx5961M', '-Djava.awt.headless=true', '-Dsun.rmi.dgc.client.gcInterval=360', '-Dsun.rmi.dgc.server.gcInterval=360', '-Djsse.enableSNIExtension=false', '-XX:+HeapDumpOnOutOfMemoryError', '-XX:HeapDumpPath=/var/log/ovirt-engine/dump', '-Djava.util.logging.manager=org.jboss.logmanager', '-Dlogging.configuration=file:///var/lib/ovirt-engine/jboss_ runtime/config/ovirt-engine-logging.properties', '-Dorg.jboss.resolver.warning=true', '-Djboss.modules.system.pkgs=org.jboss.byteman', '-Djboss.server.default.config=ovirt-engine', '-Djboss.home.dir=/usr/share/ovirt-engine-wildfly', '-Djboss.server.base.dir=/usr/share/ovirt-engine', '-Djboss.server.data.dir=/var/lib/ovirt-engine', '-Djboss.server.log.dir=/var/log/ovirt-engine', '-Djboss.server.config.dir=/ var/lib/ovirt-engine/jboss_runtime/config', '-Djboss.server.temp.dir=/var/ lib/ovirt-engine/jboss_runtime/tmp', '-Djboss.controller.temp.dir=/ var/lib/ovirt-engine/jboss_runtime/tmp', '-jar', '/usr/share/ovirt-engine-wildfly/jboss-modules.jar', '-mp', '/usr/share/ovirt-engine/modules/common:/usr/share/ ovirt-engine-extension-aaa-jdbc/modules:/usr/share/ovirt-engine-wildfly/modules', '-jaxpmodule', 'javax.xml.jaxp-provider', 'org.jboss.as.standalone', '-v'] Mar 08 19:15:10 ovirtengine.localdomain ovirt-engine.py[10370]: 2018-03-08 19:15:10,668+0530 ovirt-engine: INFO _detectJBossVersion:207 Return code: 1, | stdout: '[u'WildFly Full 10.1.0.Final (WildFly Core 2.2.0.Final)'], | stderr: '[]' Mar 08 19:15:10 ovirtengine.localdomain systemd[1]: Started oVirt Engine. Anyhelp would be Appreaciated. 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 i...@msystechnologies.com, then delete the e-mail and destroy any copies of it. If you are not the intended rec
[ovirt-users] Limitation in using Ovirt SSO Token
Hi Team, I would like to know, Is there any limitation in using the same sso token for multiple request. I observe that when I use the same sso token for more than 900 HTTP Rest request, the application went down. Is there any limitation in using same SSO token? I could see that my status is showing as ACTIVE and memory and CPU seem fine. Still, the oVirt is not reachable and I need to restart it to access again. sudo systemctl status ovirt-engine.service -l ● ovirt-engine.service - oVirt Engine Loaded: loaded (/usr/lib/systemd/system/ovirt-engine.service; enabled; vendor preset: disabled) Active: active (running) since Thu 2018-03-08 19:15:10 IST; 30s ago Main PID: 10370 (ovirt-engine.py) CGroup: /system.slice/ovirt-engine.service ├─10370 /usr/bin/python /usr/share/ovirt-engine/services/ovirt-engine/ovirt-engine.py --redirect-output --systemd=notify start └─10423 ovirt-engine -server -XX:+TieredCompilation -Xms5961M -Xmx5961M -Djava.awt.headless=true -Dsun.rmi.dgc.client.gcInterval=360 -Dsun.rmi.dgc.server.gcInterval=360 -Djsse.enableSNIExtension=false -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/var/log/ovirt-engine/dump -Djava.util.logging.manager=org.jboss.logmanager -Dlogging.configuration=file:///var/lib/ovirt-engine/jboss_runtime/config/ovirt-engine-logging.properties -Dorg.jboss.resolver.warning=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djboss.server.default.config=ovirt-engine -Djboss.home.dir=/usr/share/ovirt-engine-wildfly -Djboss.server.base.dir=/usr/share/ovirt-engine -Djboss.server.data.dir=/var/lib/ovirt-engine -Djboss.server.log.dir=/var/log/ovirt-engine -Djboss.server.config.dir=/var/lib/ovirt-engine/jboss_runtime/config -Djboss.server.temp.dir=/var/lib/ovirt-engine/jboss_runtime/tmp -Djboss.controller.temp.dir=/var/lib/ovirt-engine/jboss_runtime/tmp -jar /usr/share/ovirt-engine-wildfly/jboss-modules.jar -mp /usr/share/ovirt-engine/modules/common:/usr/share/ovirt-engine-extension-aaa-jdbc/modules:/usr/share/ovirt-engine-wildfly/modules -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -c ovirt-engine.xml Mar 08 19:15:10 ovirtengine.localdomain systemd[1]: Starting oVirt Engine... Mar 08 19:15:10 ovirtengine.localdomain ovirt-engine.py[10370]: 2018-03-08 19:15:10,228+0530 ovirt-engine: INFO _detectJBossVersion:187 Detecting JBoss version. Running: /usr/lib/jvm/jre/bin/java ['ovirt-engine-version', '-server', '-XX:+TieredCompilation', '-Xms5961M', '-Xmx5961M', '-Djava.awt.headless=true', '-Dsun.rmi.dgc.client.gcInterval=360', '-Dsun.rmi.dgc.server.gcInterval=360', '-Djsse.enableSNIExtension=false', '-XX:+HeapDumpOnOutOfMemoryError', '-XX:HeapDumpPath=/var/log/ovirt-engine/dump', '-Djava.util.logging.manager=org.jboss.logmanager', '-Dlogging.configuration=file:///var/lib/ovirt-engine/jboss_runtime/config/ovirt-engine-logging.properties', '-Dorg.jboss.resolver.warning=true', '-Djboss.modules.system.pkgs=org.jboss.byteman', '-Djboss.server.default.config=ovirt-engine', '-Djboss.home.dir=/usr/share/ovirt-engine-wildfly', '-Djboss.server.base.dir=/usr/share/ovirt-engine', '-Djboss.server.data.dir=/var/lib/ovirt-engine', '-Djboss.server.log.dir=/var/log/ovirt-engine', '-Djboss.server.config.dir=/var/lib/ovirt-engine/jboss_runtime/config', '-Djboss.server.temp.dir=/var/lib/ovirt-engine/jboss_runtime/tmp', '-Djboss.controller.temp.dir=/var/lib/ovirt-engine/jboss_runtime/tmp', '-jar', '/usr/share/ovirt-engine-wildfly/jboss-modules.jar', '-mp', '/usr/share/ovirt-engine/modules/common:/usr/share/ovirt-engine-extension-aaa-jdbc/modules:/usr/share/ovirt-engine-wildfly/modules', '-jaxpmodule', 'javax.xml.jaxp-provider', 'org.jboss.as.standalone', '-v'] Mar 08 19:15:10 ovirtengine.localdomain ovirt-engine.py[10370]: 2018-03-08 19:15:10,668+0530 ovirt-engine: INFO _detectJBossVersion:207 Return code: 1, | stdout: '[u'WildFly Full 10.1.0.Final (WildFly Core 2.2.0.Final)'], | stderr: '[]' Mar 08 19:15:10 ovirtengine.localdomain systemd[1]: Started oVirt Engine. Anyhelp would be Appreaciated. 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 i...@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, corrupte
