I have no idea - I guess the data is not necessary.

From: "Sven Kieske" <S.Kieske(a)mittwald.de&gt; To: engine-devel(a)ovirt.org Sent: Monday, March 3, 2014 6:25:39 PM Subject: [Engine-devel] Tweaking backup/restore of engine Hi, currently all events are stored in the table audit_log which all gets saved when you use the engine-backup shell script. the event log is full of these login lines (engine 3.3.2): 25652 fdfc627c-d875-11e0-90f0-83df133b58cc admin@internal 00000000-0000-0000-0000-000000000000 \N \N \N \N \N 2014-01-20 06:39:17.222+01 USER_VDC_LOGIN 30 0 User admin@internal logged in. f \N \N 00000000-0000-0000-0000-000000000000 \N \N \N \N 00000000-0000-0000-0000-000000000000 \N oVirt -1 30 f \N this makes the log and db grow very large when you use the REST-API to query ovirt for various data. Is this necessary for a working restore? It would be cool if we could tweak the engine-backup tool to just dump necessary tables so you don't have to restore events from the past no one is interested in. How does ovirt react, if I do not restore the content of the audit_log table? If this works (restore without audit_log) I would prefer to have this code upstream in ovirt git so I don't have to maintain my own backupscript. Would it be possible to extend the existing backupscript with a switch to not backup logs? Currently it's just "all" or "just db". I also recall that there shouldn't occur multiple login events any more since ovirt 3.3. but it still seems to be the case.

I also do not understand how you would manage a stored authentication via REST as REST is stateless. I would appreciate any feedback or thoughts on this topic. -- 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(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel

From: "Sven Kieske" <S.Kieske(a)mittwald.de&gt; To: engine-devel(a)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?

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(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel

On 03/04/2014 12:00 PM, Sven Kieske wrote: > 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. > audit log gets deleted after 30 days by default. you can change that via config: packaging/dbscripts/upgrade/pre_upgrade/0000_config.sql:select fn_db_add_config_value('AuditLogAgingThreshold','30','general'); packaging/etc/engine-config/engine-config.properties:AuditLogAgingThreshold.description="Audit Log Aging Threshold (in days)" p

From: "Sven Kieske" <S.Kieske(a)mittwald.de&gt; To: engine-devel(a)ovirt.org Sent: Monday, March 3, 2014 6:25:39 PM Subject: [Engine-devel] Tweaking backup/restore of engine Hi, currently all events are stored in the table audit_log which all gets saved when you use the engine-backup shell script. the event log is full of these login lines (engine 3.3.2): 25652 fdfc627c-d875-11e0-90f0-83df133b58cc admin@internal 00000000-0000-0000-0000-000000000000 \N \N \N \N \N 2014-01-20 06:39:17.222+01 USER_VDC_LOGIN 30 0 User admin@internal logged in. f \N \N 00000000-0000-0000-0000-000000000000 \N \N \N \N 00000000-0000-0000-0000-000000000000 \N oVirt -1 30 f \N this makes the log and db grow very large when you use the REST-API to query ovirt for various data. Is this necessary for a working restore? It would be cool if we could tweak the engine-backup tool to just dump necessary tables so you don't have to restore events from the past no one is interested in. How does ovirt react, if I do not restore the content of the audit_log table? If this works (restore without audit_log) I would prefer to have this code upstream in ovirt git so I don't have to maintain my own backupscript. Would it be possible to extend the existing backupscript with a switch to not backup logs? Currently it's just "all" or "just db".

I also recall that there shouldn't occur multiple login events any more since ovirt 3.3. but it still seems to be the case. I also do not understand how you would manage a stored authentication via REST as REST is stateless. I would appreciate any feedback or thoughts on this topic. -- 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(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel

From: "Yedidyah Bar David" <didi(a)redhat.com&gt; To: "Eli Mesika" <emesika(a)redhat.com&gt; Cc: "Sven Kieske" <S.Kieske(a)mittwald.de&gt;, engine-devel(a)ovirt.org Sent: Wednesday, March 5, 2014 5:02:40 PM Subject: Re: [Engine-devel] Tweaking backup/restore of engine ----- Original Message ----- > From: "Eli Mesika" <emesika(a)redhat.com&gt; > To: "Sven Kieske" <S.Kieske(a)mittwald.de&gt; > Cc: engine-devel(a)ovirt.org > Sent: Wednesday, March 5, 2014 4:50:42 PM > Subject: Re: [Engine-devel] Tweaking backup/restore of engine > > > > ----- Original Message ----- > > From: "Sven Kieske" <S.Kieske(a)mittwald.de&gt; > > To: engine-devel(a)ovirt.org > > Sent: Monday, March 3, 2014 6:25:39 PM > > Subject: [Engine-devel] Tweaking backup/restore of engine > > > > Hi, > > > > currently all events are stored in the table audit_log > > which all gets saved when you use the engine-backup > > shell script. > > > > > > the event log is full of these login lines (engine 3.3.2): > > > > 25652 fdfc627c-d875-11e0-90f0-83df133b58cc admin@internal > > 00000000-0000-0000-0000-000000000000 \N \N \N \N \N 2014-01-20 > > 06:39:17.222+01 USER_VDC_LOGIN 30 0 User admin@internal > > logged in. f \N \N 00000000-0000-0000-0000-000000000000 \N \N \N > > \N 00000000-0000-0000-0000-000000000000 \N oVirt -1 30 f \N > > > > this makes the log and db grow very large when you use the REST-API > > to query ovirt for various data. > > > > Is this necessary for a working restore? > > It would be cool if we could tweak the engine-backup > > tool to just dump necessary tables so you don't have > > to restore events from the past no one is interested > > in. > > > > How does ovirt react, if I do not restore the content of the audit_log > > table? > > > > If this works (restore without audit_log) I would prefer to have > > this code upstream in ovirt git so I don't have to maintain > > my own backupscript. > > > > Would it be possible to extend the existing backupscript > > with a switch to not backup logs? > > Currently it's just "all" or "just db". > > Hi Sven > > engine-backup is calling eventually a postgres utility named pg_dump > this utility supports the following flag : > > --exclude-table-data=TABLE do NOT dump data for the named table(s) Oh, didn't notice that one. Added in 9.2, so not for el6. > > > I think that a RFE for adding support for this flag in engine-backup will > easily solve your problem Perhaps better to allow passing arbitrary options to pg_dump. Or something like that.

-- Didi