Re: [Engine-devel] Schema upgrade failure on master
- Original Message - > From: "Liran Zelkha" > To: "Adam Litke" > Cc: "engine-devel" > Sent: Tuesday, March 4, 2014 3:20:57 PM > Subject: Re: [Engine-devel] Schema upgrade failure on master > > had the same issue. Run from psql: > truncate table event_subscriber; > Then run the script. Note that this will delete all the rows from your > table... Sorry for jumping on that late, but if this occurs when event_subscriber is not empty then this is a bug since it will fail also in customer site. In that case I think that you should open a bug and since the notification mechanism is heavily used , I think this is a blocker Can you please open a bug and assign on me Thanks Eli > > > On Tue, Mar 4, 2014 at 3:18 PM, Adam Litke < ali...@redhat.com > wrote: > > > On 04/03/14 00:10 -0500, Martin Perina wrote: > > > Hi Adam, > > I didn't notice any problem with this script. Was the database you tried to > upgrade empty? > If not could you please send me contents of your event_subscriber table? > > engine=> select * from event_subscriber ; > subscriber_id | event_up_name | method_id | method_address | tag_name > -- +- > +--- > +--+-- > fdfc627c-d875-11e0-90f0- 83df133b58cc | VM_SET_TICKET | 0 | > ali...@brewer.alitke.net | fdfc627c-d875-11e0-90f0- 83df133b58cc | > VM_DOWN_ERROR | 0 | ali...@brewer.alitke.net | fdfc627c-d875-11e0-90f0- > 83df133b58cc | VDS_INITIATED_RUN_VM_FAILED | 0 | ali...@brewer.alitke.net | > (3 rows) > > > > > > Thanks > > Martin Perina > > - Original Message - > > > From: "Adam Litke" < ali...@redhat.com > > To: engine-devel@ovirt.org > Sent: Monday, March 3, 2014 11:26:28 PM > Subject: [Engine-devel] Schema upgrade failure on master > > Hi, > > I've recently rebased to master and it looks like the > 03_05_0050_event_notification_ methods.sql script is failing on schema > upgrade. Is this a bug or am I doing something wrong? To upgrade I > did the normal proceedure with my development installation: > > make install-dev ... > ~/ovirt/bin/engine-setup > > Got this result in the log file: > > psql:/home/alitke/ovirt-** FILTERED**/share/ovirt-** > FILTERED**/dbscripts/upgrade/ 03_05_0050_event_notification_ methods.sql:10: > ERROR: column "notification_method" contains null values > FATAL: Cannot execute sql command: > --file=/home/alitke/ovirt-** FILTERED**/share/ovirt-** > FILTERED**/dbscripts/upgrade/ 03_05_0050_event_notification_ methods.sql > > 2014-03-03 17:20:34 DEBUG otopi.context context._executeMethod:152 method > exception > Traceback (most recent call last): > File "/usr/lib/python2.7/site- packages/otopi/context.py", line 142, in > _executeMethod > method['method']() > File > "/home/alitke/ovirt-** FILTERED**/share/ovirt-** FILTERED**/setup/bin/../ > plugins/ovirt-**FILTERED**- setup/ovirt-**FILTERED**/db/ schema.py", > line 280, in _misc > osetupcons.DBEnv.PGPASS_FILE > File "/usr/lib/python2.7/site- packages/otopi/plugin.py", line 451, in > execute > command=args[0], > RuntimeError: Command > '/home/alitke/ovirt-** FILTERED**/share/ovirt-** FILTERED**/dbscripts/schema. > sh' > failed to execute > > -- > Adam Litke > __ _ > Engine-devel mailing list > Engine-devel@ovirt.org > http://lists.ovirt.org/ mailman/listinfo/engine-devel > > > -- > Adam Litke > __ _ > Engine-devel mailing list > Engine-devel@ovirt.org > http://lists.ovirt.org/ mailman/listinfo/engine-devel > > > ___ > Engine-devel mailing list > Engine-devel@ovirt.org > http://lists.ovirt.org/mailman/listinfo/engine-devel > ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] Schema upgrade failure on master
had the same issue. Run from psql: truncate table event_subscriber; Then run the script. Note that this will delete all the rows from your table... On Tue, Mar 4, 2014 at 3:18 PM, Adam Litke wrote: > On 04/03/14 00:10 -0500, Martin Perina wrote: > >> Hi Adam, >> >> I didn't notice any problem with this script. Was the database you tried >> to upgrade empty? >> If not could you please send me contents of your event_subscriber table? >> > > engine=> select * from event_subscriber ; >subscriber_id |event_up_name| > method_id | method_address | tag_name > --+- > +--- > +--+-- > fdfc627c-d875-11e0-90f0-83df133b58cc | VM_SET_TICKET | > 0 | ali...@brewer.alitke.net | fdfc627c-d875-11e0-90f0-83df133b58cc | > VM_DOWN_ERROR | 0 | ali...@brewer.alitke.net | > fdfc627c-d875-11e0-90f0-83df133b58cc | VDS_INITIATED_RUN_VM_FAILED | > 0 | ali...@brewer.alitke.net | (3 rows) > > > >> Thanks >> >> Martin Perina >> >> - Original Message - >> >>> From: "Adam Litke" >>> To: engine-devel@ovirt.org >>> Sent: Monday, March 3, 2014 11:26:28 PM >>> Subject: [Engine-devel] Schema upgrade failure on master >>> >>> Hi, >>> >>> I've recently rebased to master and it looks like the >>> 03_05_0050_event_notification_methods.sql script is failing on schema >>> upgrade. Is this a bug or am I doing something wrong? To upgrade I >>> did the normal proceedure with my development installation: >>> >>> make install-dev ... >>> ~/ovirt/bin/engine-setup >>> >>> Got this result in the log file: >>> >>> psql:/home/alitke/ovirt-**FILTERED**/share/ovirt-** >>> FILTERED**/dbscripts/upgrade/03_05_0050_event_notification_ >>> methods.sql:10: >>> ERROR: column "notification_method" contains null values >>> FATAL: Cannot execute sql command: >>> --file=/home/alitke/ovirt-**FILTERED**/share/ovirt-** >>> FILTERED**/dbscripts/upgrade/03_05_0050_event_notification_methods.sql >>> >>> 2014-03-03 17:20:34 DEBUG otopi.context context._executeMethod:152 method >>> exception >>> Traceback (most recent call last): >>> File "/usr/lib/python2.7/site-packages/otopi/context.py", line 142, in >>> _executeMethod >>> method['method']() >>> File >>> "/home/alitke/ovirt-**FILTERED**/share/ovirt-** >>> FILTERED**/setup/bin/../plugins/ovirt-**FILTERED**- >>> setup/ovirt-**FILTERED**/db/schema.py", >>> line 280, in _misc >>> osetupcons.DBEnv.PGPASS_FILE >>> File "/usr/lib/python2.7/site-packages/otopi/plugin.py", line 451, in >>> execute >>> command=args[0], >>> RuntimeError: Command >>> '/home/alitke/ovirt-**FILTERED**/share/ovirt-** >>> FILTERED**/dbscripts/schema.sh' >>> failed to execute >>> >>> -- >>> Adam Litke >>> ___ >>> Engine-devel mailing list >>> Engine-devel@ovirt.org >>> http://lists.ovirt.org/mailman/listinfo/engine-devel >>> >>> > -- > Adam Litke > ___ > Engine-devel mailing list > Engine-devel@ovirt.org > http://lists.ovirt.org/mailman/listinfo/engine-devel > ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] Schema upgrade failure on master
On 04/03/14 00:10 -0500, Martin Perina wrote: Hi Adam, I didn't notice any problem with this script. Was the database you tried to upgrade empty? If not could you please send me contents of your event_subscriber table? engine=> select * from event_subscriber ; subscriber_id |event_up_name| method_id | method_address | tag_name --+-+--- +--+-- fdfc627c-d875-11e0-90f0-83df133b58cc | VM_SET_TICKET | 0 | ali...@brewer.alitke.net | fdfc627c-d875-11e0-90f0-83df133b58cc | VM_DOWN_ERROR | 0 | ali...@brewer.alitke.net | fdfc627c-d875-11e0-90f0-83df133b58cc | VDS_INITIATED_RUN_VM_FAILED | 0 | ali...@brewer.alitke.net | (3 rows) Thanks Martin Perina - Original Message - From: "Adam Litke" To: engine-devel@ovirt.org Sent: Monday, March 3, 2014 11:26:28 PM Subject: [Engine-devel] Schema upgrade failure on master Hi, I've recently rebased to master and it looks like the 03_05_0050_event_notification_methods.sql script is failing on schema upgrade. Is this a bug or am I doing something wrong? To upgrade I did the normal proceedure with my development installation: make install-dev ... ~/ovirt/bin/engine-setup Got this result in the log file: psql:/home/alitke/ovirt-**FILTERED**/share/ovirt-**FILTERED**/dbscripts/upgrade/03_05_0050_event_notification_methods.sql:10: ERROR: column "notification_method" contains null values FATAL: Cannot execute sql command: --file=/home/alitke/ovirt-**FILTERED**/share/ovirt-**FILTERED**/dbscripts/upgrade/03_05_0050_event_notification_methods.sql 2014-03-03 17:20:34 DEBUG otopi.context context._executeMethod:152 method exception Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/otopi/context.py", line 142, in _executeMethod method['method']() File "/home/alitke/ovirt-**FILTERED**/share/ovirt-**FILTERED**/setup/bin/../plugins/ovirt-**FILTERED**-setup/ovirt-**FILTERED**/db/schema.py", line 280, in _misc osetupcons.DBEnv.PGPASS_FILE File "/usr/lib/python2.7/site-packages/otopi/plugin.py", line 451, in execute command=args[0], RuntimeError: Command '/home/alitke/ovirt-**FILTERED**/share/ovirt-**FILTERED**/dbscripts/schema.sh' failed to execute -- Adam Litke ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel -- Adam Litke ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
[Engine-devel] [ANN] oVirt 3.3.4 release
The oVirt development team is pleased to announce the general availability of oVirt 3.3.4 as of March 4th 2014. This release solidifies oVirt as a leading KVM management application and open source alternative to VMware vSphere. oVirt is available now for Fedora 19 and Red Hat Enterprise Linux 6.5 (or similar). This release of oVirt includes numerous bug fixes. See the release notes [1] for a list of the new features and bugs fixed. The existing repository ovirt-stable has been updated for delivering this release without the need of enabling any other repository. A new oVirt Node build is also available [2]. [1] http://www.ovirt.org/OVirt_3.3.4_release_notes [2] http://resources.ovirt.org/releases/3.3.4/iso/ovirt-node-iso-3.0.4-1.0.201401291204.vdsm33.el6.iso -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] Tweaking backup/restore of engine
Hi, I forgot to mention a crucial point: How long does the engine store past events, are they stored forever or is there some kind of rotation? We mainly use the engine as a REST provider for managing the virtual machines. -- Mit freundlichen Grüßen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] Schema upgrade failure on master
- Original Message - > From: "Liran Zelkha" > To: "Martin Perina" > Cc: "engine-devel" > Sent: Tuesday, March 4, 2014 10:15:47 AM > Subject: Re: [Engine-devel] Schema upgrade failure on master > > Happens to me too, on engine_dao_tests. > DB is not empty, one line: > engine_dao_tests=> select * from event_subscriber; > subscriber_id | event_up_name | method_id | > method_address | tag_name | notification_method > --+---+---++--+- > 9bf7c640-b620-456f-a550-0348f366544a | TestRun | 1 | >| testrun | > (1 row) This row caused the issue, I wonder how it was created when notification_method column is created during 03_05_0050_event_notification_methods.sql script execution ... Delete this row and after this run schema upgrade. I tested with master and empty db and dao tests work fine. > > > > > On Tue, Mar 4, 2014 at 7:10 AM, Martin Perina wrote: > > > Hi Adam, > > > > I didn't notice any problem with this script. Was the database you tried > > to upgrade empty? > > If not could you please send me contents of your event_subscriber table? > > > > Thanks > > > > Martin Perina > > > > - Original Message - > > > From: "Adam Litke" > > > To: engine-devel@ovirt.org > > > Sent: Monday, March 3, 2014 11:26:28 PM > > > Subject: [Engine-devel] Schema upgrade failure on master > > > > > > Hi, > > > > > > I've recently rebased to master and it looks like the > > > 03_05_0050_event_notification_methods.sql script is failing on schema > > > upgrade. Is this a bug or am I doing something wrong? To upgrade I > > > did the normal proceedure with my development installation: > > > > > > make install-dev ... > > > ~/ovirt/bin/engine-setup > > > > > > Got this result in the log file: > > > > > > > > psql:/home/alitke/ovirt-**FILTERED**/share/ovirt-**FILTERED**/dbscripts/upgrade/03_05_0050_event_notification_methods.sql:10: > > > ERROR: column "notification_method" contains null values > > > FATAL: Cannot execute sql command: > > > > > --file=/home/alitke/ovirt-**FILTERED**/share/ovirt-**FILTERED**/dbscripts/upgrade/03_05_0050_event_notification_methods.sql > > > > > > 2014-03-03 17:20:34 DEBUG otopi.context context._executeMethod:152 method > > > exception > > > Traceback (most recent call last): > > > File "/usr/lib/python2.7/site-packages/otopi/context.py", line 142, in > > > _executeMethod > > > method['method']() > > > File > > > > > "/home/alitke/ovirt-**FILTERED**/share/ovirt-**FILTERED**/setup/bin/../plugins/ovirt-**FILTERED**-setup/ovirt-**FILTERED**/db/schema.py", > > > line 280, in _misc > > > osetupcons.DBEnv.PGPASS_FILE > > > File "/usr/lib/python2.7/site-packages/otopi/plugin.py", line 451, in > > > execute > > > command=args[0], > > > RuntimeError: Command > > > > > '/home/alitke/ovirt-**FILTERED**/share/ovirt-**FILTERED**/dbscripts/schema.sh' > > > failed to execute > > > > > > -- > > > Adam Litke > > > ___ > > > Engine-devel mailing list > > > Engine-devel@ovirt.org > > > http://lists.ovirt.org/mailman/listinfo/engine-devel > > > > > ___ > > Engine-devel mailing list > > Engine-devel@ovirt.org > > http://lists.ovirt.org/mailman/listinfo/engine-devel > > > ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
[Engine-devel] oVrit 3.4.0 branch created
Hi, as announced yesterday the new branch ovirt-engine-3.4.0 branch has been created from 3.4. Branch commit was: * 9ab9f01 - (origin/ovirt-engine-3.4) core: Remove error messages from log when adding host Only critical fixes will be accepted on ovirt-engine-3.4.0 branch. Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] Schema upgrade failure on master
Happens to me too, on engine_dao_tests. DB is not empty, one line: engine_dao_tests=> select * from event_subscriber; subscriber_id | event_up_name | method_id | method_address | tag_name | notification_method --+---+---++--+- 9bf7c640-b620-456f-a550-0348f366544a | TestRun | 1 | | testrun | (1 row) On Tue, Mar 4, 2014 at 7:10 AM, Martin Perina wrote: > Hi Adam, > > I didn't notice any problem with this script. Was the database you tried > to upgrade empty? > If not could you please send me contents of your event_subscriber table? > > Thanks > > Martin Perina > > - Original Message - > > From: "Adam Litke" > > To: engine-devel@ovirt.org > > Sent: Monday, March 3, 2014 11:26:28 PM > > Subject: [Engine-devel] Schema upgrade failure on master > > > > Hi, > > > > I've recently rebased to master and it looks like the > > 03_05_0050_event_notification_methods.sql script is failing on schema > > upgrade. Is this a bug or am I doing something wrong? To upgrade I > > did the normal proceedure with my development installation: > > > > make install-dev ... > > ~/ovirt/bin/engine-setup > > > > Got this result in the log file: > > > > > psql:/home/alitke/ovirt-**FILTERED**/share/ovirt-**FILTERED**/dbscripts/upgrade/03_05_0050_event_notification_methods.sql:10: > > ERROR: column "notification_method" contains null values > > FATAL: Cannot execute sql command: > > > --file=/home/alitke/ovirt-**FILTERED**/share/ovirt-**FILTERED**/dbscripts/upgrade/03_05_0050_event_notification_methods.sql > > > > 2014-03-03 17:20:34 DEBUG otopi.context context._executeMethod:152 method > > exception > > Traceback (most recent call last): > > File "/usr/lib/python2.7/site-packages/otopi/context.py", line 142, in > > _executeMethod > > method['method']() > > File > > > "/home/alitke/ovirt-**FILTERED**/share/ovirt-**FILTERED**/setup/bin/../plugins/ovirt-**FILTERED**-setup/ovirt-**FILTERED**/db/schema.py", > > line 280, in _misc > > osetupcons.DBEnv.PGPASS_FILE > > File "/usr/lib/python2.7/site-packages/otopi/plugin.py", line 451, in > > execute > > command=args[0], > > RuntimeError: Command > > > '/home/alitke/ovirt-**FILTERED**/share/ovirt-**FILTERED**/dbscripts/schema.sh' > > failed to execute > > > > -- > > Adam Litke > > ___ > > Engine-devel mailing list > > Engine-devel@ovirt.org > > http://lists.ovirt.org/mailman/listinfo/engine-devel > > > ___ > Engine-devel mailing list > Engine-devel@ovirt.org > http://lists.ovirt.org/mailman/listinfo/engine-devel > ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
[Engine-devel] python docs in wiki up to date?
Hi, is this still state of the art? http://www.ovirt.org/Testing/PythonApi If not I could update it myself if you provide me with the necessary information. Thanks -- Mit freundlichen Grüßen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] Tweaking backup/restore of engine
On 03/04/2014 09:38 AM, Yair Zaslavsky wrote:
>
>
> - Original Message -
>> From: "Sven Kieske"
>> To: engine-devel@ovirt.org
>> Sent: Tuesday, March 4, 2014 10:25:31 AM
>> Subject: Re: [Engine-devel] Tweaking backup/restore of engine
>>
>> Thanks for the clarification,
>>
>> I couldn't find this change any more, but I knew
>> there was something done.
>>
>> However this makes me think about an RFE:
>> It would be cool if ovirt could provide a way
>> to use the REST-API without always have to login
>> and logout.
>>
>> Maybe something like a hook into
>> some message passing queue like rabbitMQ or zeroMQ
>> or a similar process for receiving and submitting
>> messages. So you could register once with an API
>> consumer and use that.
>>
>> What do you think?
>
> CC'ing Juan - the maintainer of the REST API
Using the RESTAPI without repeated login/logout is already supported,
and it is what the SDKs do by default. In order to use it you need to
add the "Prefer: persistent-auth" header to the HTTP request, and keep
track of the cookies returned by the engine. For, example, the following
example sends events to the engine, without repeatedly performing the
login process:
#!/bin/sh -x
# The details to connect to the engine:
url="https://whatever/ovirt-engine/api";
user="admin@internal"
password=""
# The file where we store the cookies, including the
# session id:
cookies="cookies.txt"
curl \
--insecure \
--request POST \
--header "Accept: application/xml" \
--header "Content-Type: application/xml" \
--header "Prefer: persistent-auth" \
--user "${user}:${password}" \
--cookie "${cookies}" \
--cookie-jar "${cookies}" \
--data "
myorigin
normal
Something from me
$(date +%s)
" \
${url}/events
This will keep a session alive in the server. If you want to explicitly
close it just send an additional request, with the same cookies and
without the "Prefer" header.
It is described in more detail here:
http://www.ovirt.org/Features/RESTSessionManagement
>>
>> Am 04.03.2014 07:53, schrieb Yair Zaslavsky:
>>> Hi Sven,
>>> This is not entirely accurate -
>>> The solution introduced at commit hash
>>> cb56de8808cec33b7599828ead890f52e32bcaea solves the problem for a
>>> specific case in which we have a multiple login in a very short interval
>>> of time -
>>> mainly due to attempt to login from webadmin, while UI plugin tries to
>>> login as well.
>>> We have an "anti flood" mechanism for events, allowing us to define an
>>> interval, in which an event will not be logged twice. In the case of the
>>> login event this is set to 5 seconds, which is enough to solve the above
>>> described scenario.
>>
>> --
>> Mit freundlichen Grüßen / Regards
>>
>> Sven Kieske
>>
>> Systemadministrator
>> Mittwald CM Service GmbH & Co. KG
>> Königsberger Straße 6
>> 32339 Espelkamp
>> T: +49-5772-293-100
>> F: +49-5772-293-333
>> https://www.mittwald.de
>> Geschäftsführer: Robert Meyer
>> St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen
>> Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen
>> ___
>> Engine-devel mailing list
>> Engine-devel@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/engine-devel
>>
--
Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta
3ºD, 28016 Madrid, Spain
Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L.
___
Engine-devel mailing list
Engine-devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] Tweaking backup/restore of engine
- Original Message - > From: "Sven Kieske" > To: engine-devel@ovirt.org > Sent: Tuesday, March 4, 2014 10:25:31 AM > Subject: Re: [Engine-devel] Tweaking backup/restore of engine > > Thanks for the clarification, > > I couldn't find this change any more, but I knew > there was something done. > > However this makes me think about an RFE: > It would be cool if ovirt could provide a way > to use the REST-API without always have to login > and logout. > > Maybe something like a hook into > some message passing queue like rabbitMQ or zeroMQ > or a similar process for receiving and submitting > messages. So you could register once with an API > consumer and use that. > > What do you think? CC'ing Juan - the maintainer of the REST API > > Am 04.03.2014 07:53, schrieb Yair Zaslavsky: > > Hi Sven, > > This is not entirely accurate - > > The solution introduced at commit hash > > cb56de8808cec33b7599828ead890f52e32bcaea solves the problem for a > > specific case in which we have a multiple login in a very short interval > > of time - > > mainly due to attempt to login from webadmin, while UI plugin tries to > > login as well. > > We have an "anti flood" mechanism for events, allowing us to define an > > interval, in which an event will not be logged twice. In the case of the > > login event this is set to 5 seconds, which is enough to solve the above > > described scenario. > > -- > Mit freundlichen Grüßen / Regards > > Sven Kieske > > Systemadministrator > Mittwald CM Service GmbH & Co. KG > Königsberger Straße 6 > 32339 Espelkamp > T: +49-5772-293-100 > F: +49-5772-293-333 > https://www.mittwald.de > Geschäftsführer: Robert Meyer > St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen > Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen > ___ > Engine-devel mailing list > Engine-devel@ovirt.org > http://lists.ovirt.org/mailman/listinfo/engine-devel > ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] Tweaking backup/restore of engine
Thanks for the clarification, I couldn't find this change any more, but I knew there was something done. However this makes me think about an RFE: It would be cool if ovirt could provide a way to use the REST-API without always have to login and logout. Maybe something like a hook into some message passing queue like rabbitMQ or zeroMQ or a similar process for receiving and submitting messages. So you could register once with an API consumer and use that. What do you think? Am 04.03.2014 07:53, schrieb Yair Zaslavsky: > Hi Sven, > This is not entirely accurate - > The solution introduced at commit hash > cb56de8808cec33b7599828ead890f52e32bcaea solves the problem for a specific > case in which we have a multiple login in a very short interval of time - > mainly due to attempt to login from webadmin, while UI plugin tries to login > as well. > We have an "anti flood" mechanism for events, allowing us to define an > interval, in which an event will not be logged twice. In the case of the > login event this is set to 5 seconds, which is enough to solve the above > described scenario. -- Mit freundlichen Grüßen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] Tweaking backup/restore of engine and the table 'audit_log'
Thanks for your answer so far. Is there anyone around who knows if the audit_log data is needed for a successful restore? I'd rather not try this out myself. The reasoning behind this all is of course to keep backup space as small as possible. Am 03.03.2014 21:41, schrieb Yedidyah Bar David: > I have no idea - I guess the data is not necessary. -- Mit freundlichen Grüßen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
