Friday, 2015-08-07

*** reldan has quit IRC01:16
*** smekel has joined #openstack-freezer04:09
*** reldan has joined #openstack-freezer07:37
*** reldan has quit IRC07:47
*** reldan has joined #openstack-freezer07:52
*** reldan has quit IRC08:03
*** reldan has joined #openstack-freezer08:52
openstackgerritMemo Garcia proposed stackforge/freezer: Fix for issues in the parsing of mysql credentials.  https://review.openstack.org/21027209:28
reldanPlease review https://review.openstack.org/#/c/209916/09:55
*** marzif has joined #openstack-freezer09:59
*** reldan has quit IRC10:45
*** openstackgerrit has quit IRC10:45
*** freezerBot` has quit IRC10:45
*** reldan has joined #openstack-freezer10:49
*** openstackgerrit has joined #openstack-freezer10:49
*** freezerBot` has joined #openstack-freezer10:49
*** smekel has quit IRC10:51
*** smekel has joined #openstack-freezer10:53
*** reldan has quit IRC11:01
*** reldan has joined #openstack-freezer11:18
*** jonaspf has quit IRC12:00
*** jonaspf has joined #openstack-freezer12:24
openstackgerritMemo Garcia proposed stackforge/freezer: Fix for issues in the parsing of mysql credentials.  https://review.openstack.org/21027212:47
*** NM has joined #openstack-freezer13:11
openstackgerritMemo Garcia proposed stackforge/freezer: Add freezerc entry point for windows  https://review.openstack.org/21041413:27
*** NM has quit IRC13:31
daemontool_fabriziov, I remember we had a conversation in the past about this? can you take a look at your earliest convenience? https://review.openstack.org/#/c/210414/1 thanks13:36
daemontool_m3m0,  ^^13:36
fabriziovyes13:36
fabriziovare we going to rename the freezerc ?13:37
m3m0what was the conversation about?13:39
fabrizioventry-point and its setup.py (or setup.cfg) definition13:40
m3m0because in the README we are still referring  as freezerc13:40
fabriziovwe were talking about installation of the scheduler, we did not talk about any renaming of the freezerc13:41
m3m0for windows is mandatory to add an entry point13:41
m3m0aaaa k k13:41
fabriziovbut I remember talking about the name "freezerc" in other occasions13:42
daemontool_fabriziov, it wasn't like that entry point was bypassing the freezerc call?13:42
daemontool_or something like that? I might be wrong13:42
fabriziovyes, because we had try/catch code in the freezerc13:43
fabriziovwe *have*13:43
fabriziovand that was bypassed13:43
fabriziovlet me check ...13:43
daemontool_and now would be all good if we reintroduce that?13:43
daemontool_all please take a look at: https://review.openstack.org/#/c/210272/ and https://review.openstack.org/#/c/209916/13:55
fabriziovyes. that would bypass the try/catch code in bin/freezerc14:00
daemontool_fabriziov,  m3m0 that was my concern14:00
*** jonaspf has quit IRC14:32
*** jonaspf has joined #openstack-freezer14:47
*** reldan has quit IRC14:47
*** reldan has joined #openstack-freezer14:57
*** dschroeder has joined #openstack-freezer15:27
*** reldan has quit IRC16:16
*** reldan has joined #openstack-freezer16:17
*** reldan has quit IRC16:18
*** marzif has quit IRC16:45
*** jonaspf has quit IRC17:02
*** reldan has joined #openstack-freezer18:13
*** reldan has quit IRC23:01
*** reldan has joined #openstack-freezer23:09
*** reldan has quit IRC23:17
*** dschroeder has quit IRC23:17

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!