Thursday, 2015-11-12

« Wednesday, 2015-11-11 Index Friday, 2015-11-13 »
*** dschroeder has quit IRC00:19
*** memogarcia has quit IRC00:23
*** memogarcia has joined #openstack-freezer00:32
*** memogarcia has quit IRC00:55
*** memogarcia has joined #openstack-freezer01:02
*** miqui has quit IRC01:10
*** szaher has quit IRC01:11
*** szaher has joined #openstack-freezer01:23
*** miqui has joined #openstack-freezer01:23
*** memogarcia has quit IRC02:08
*** memogarcia has joined #openstack-freezer02:10
*** szaher has quit IRC03:04
*** vannif has quit IRC03:04
*** miqui has quit IRC03:05
*** memogarcia has quit IRC03:09
*** memogarcia has joined #openstack-freezer03:11
*** szaher has joined #openstack-freezer03:16
*** vannif has joined #openstack-freezer03:17
*** memogarcia has quit IRC03:23
*** memogarcia has joined #openstack-freezer03:25
*** memogarcia has quit IRC03:54
*** memogarcia has joined #openstack-freezer03:56
*** memogarcia has quit IRC04:39
*** memogarcia has joined #openstack-freezer04:41
*** reldan has joined #openstack-freezer09:11
*** reldan has quit IRC09:21
*** memogarcia has quit IRC09:25
*** jonaspf has joined #openstack-freezer09:29
*** memogarcia has joined #openstack-freezer09:32
*** openstackgerrit has quit IRC09:46
*** openstackgerrit has joined #openstack-freezer09:47
*** memogarcia has quit IRC09:58
*** reldan has joined #openstack-freezer10:01
*** memogarcia has joined #openstack-freezer10:06
*** openstackgerrit has quit IRC10:16
*** openstackgerrit has joined #openstack-freezer10:17
*** memogarcia has quit IRC10:41
*** jonaspf has quit IRC10:43
*** jonaspf has joined #openstack-freezer10:49
*** memogarcia has joined #openstack-freezer10:51
*** memogarcia has quit IRC10:55
*** memogarcia has joined #openstack-freezer10:57
openstackgerritMemo Garcia proposed openstack/freezer-api: Backup UUID  https://review.openstack.org/24456311:04
m3m0__vannif, https://review.openstack.org/24456311:05
openstackgerritMemo Garcia proposed openstack/freezer-web-ui: Improved horizon dashboard for freezer  https://review.openstack.org/23617511:06
*** memogarcia has quit IRC11:16
*** memogarcia has joined #openstack-freezer11:23
*** memogarcia has quit IRC11:41
*** memogarcia has joined #openstack-freezer11:42
*** reldan has quit IRC11:45
*** reldan has joined #openstack-freezer12:03
reldanPlan: I will continue to work on parallel backup feature.12:04
m3m0__Plan, there is a backup_uuid patch in review12:07
m3m0__https://review.openstack.org/24456312:07
m3m0__please review12:07
m3m0__and I'm working on restore functionality from the ui12:08
*** marzif has joined #openstack-freezer12:08
szaher Plan: Will work on freezer-api, routes, paste, pasteDeploy, Controllers, oslo.config, oslo.log12:09
reldanHave backup.id and backup.uuid makes no sense for me12:09
marzifPlan: code review, integrated tests, branching and new release12:09
szaherevaluating how long it will take to move to new style and create blueprints12:09
m3m0__the thing is that backup_is contains container, backup name and incremental12:09
m3m0__and that information is need it for remove backups12:10
m3m0__or restore from incremental12:10
m3m0__that's why it make sense to have a separate backup_uuid just to query stuff from the ui or the api12:10
reldanBut it is still conterintuitive, you know. You have something with id and uuid12:10
*** memogarcia has quit IRC12:11
m3m0__what would you recommend?12:11
reldanI don’t know. But I feel we have a problem here. Because backup.id is not id at all. It is complex key that can have duplicates. In this case it seems right to rename it to backup.info, backup.description. Because id means that it is unique, don’t it?12:13
reldanI know, that it is not related to your changes12:13
reldanBut now, we have backup.id and backup.uuid and backup.id is not id at all12:14
m3m0__I completely agree with you on this12:16
m3m0__let's have a further discussion on this topic, but as far as my change this is not related, I just need an uuid to query things correctly12:16
reldanYes, sure!12:17
*** memogarcia has joined #openstack-freezer12:19
*** memogarcia has quit IRC12:43
marzifm3m0__, vannif how are we doing with the web ui / api?12:43
*** reldan has quit IRC12:46
*** reldan has joined #openstack-freezer12:47
*** memogarcia has joined #openstack-freezer12:50
vanniftesting. I have a small issue with this: https://www.elastic.co/guide/en/elasticsearch/reference/1.7/docs-delete-by-query.html12:54
vannifthat method is going to be removed. probably it's already removed in the python-elasticsearch library12:55
m3m0__marzif13:11
m3m0__there are 2 commits to finish this13:11
m3m0__the first one is related to backup_ip : https://review.openstack.org/#/c/244245/13:11
m3m0__sorry, is this commit https://review.openstack.org/24456313:11
m3m0__and the second one from vannif https://review.openstack.org/#/c/244245/13:12
m3m0__if things stays the ui won't change at all13:12
*** jonaspf has quit IRC13:16
*** memogarcia has quit IRC13:27
*** memogarcia has joined #openstack-freezer13:29
*** jonaspf has joined #openstack-freezer13:40
*** memogarcia has quit IRC13:42
*** memogarcia has joined #openstack-freezer13:51
*** jonaspf has quit IRC13:55
*** memogarcia has quit IRC14:12
szaherall: check this link http://www.slideshare.net/lhrc_mikeyp/openstack-apis-and-wsgi14:15
szaherdaemontool_ , vannif waiting for your feedback you14:16
*** memogarcia has joined #openstack-freezer14:17
*** ffresh has joined #openstack-freezer14:18
*** marzif has quit IRC14:20
*** sc has joined #openstack-freezer14:24
*** Saad has joined #openstack-freezer14:26
*** memogarcia has quit IRC14:26
*** Saad has quit IRC14:26
*** szaher_ has joined #openstack-freezer14:27
vannifsuggesting to use paste httpserver ?14:28
*** jonaspf has joined #openstack-freezer14:29
scvannif: I think it's a good idea to use the same modules used in other project as they are the standard14:30
*** ffresh has quit IRC14:31
*** memogarcia has joined #openstack-freezer14:32
scbut if this means adding lots of code and then bracking fuctionalities that are already running this needs to evaluated14:34
scthese are my 2cent14:35
*** memogarcia has quit IRC14:40
*** memogarcia has joined #openstack-freezer14:42
*** reldan has quit IRC14:48
*** reldan has joined #openstack-freezer14:50
*** memogarcia has quit IRC14:56
*** memogarcia has joined #openstack-freezer14:59
m3m0__please review :) https://review.openstack.org/#/c/236175/15:08
*** memogarcia has quit IRC15:13
*** memogarcia has joined #openstack-freezer15:16
*** freezerBot has quit IRC15:18
*** marzif has joined #openstack-freezer15:21
*** reldan has quit IRC15:28
*** memogarcia has quit IRC15:29
*** reldan has joined #openstack-freezer15:34
*** memogarcia has joined #openstack-freezer15:35
*** memogarcia has quit IRC15:46
*** memogarcia has joined #openstack-freezer15:51
*** dschroeder has joined #openstack-freezer15:54
*** memogarcia has quit IRC15:56
openstackgerritFabrizio Vanni proposed openstack/freezer-api: create actions when creating jobs  https://review.openstack.org/24424515:57
*** dschroeder has quit IRC15:59
m3m0__who's ready to rumble16:01
m3m0__#startmeeting openstack-freezer 12-11-201516:02
openstackMeeting started Thu Nov 12 16:02:33 2015 UTC and is due to finish in 60 minutes.  The chair is m3m0__. Information about MeetBot at http://wiki.debian.org/MeetBot.16:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:02
openstackThe meeting name has been set to 'openstack_freezer_12_11_2015'16:02
m3m0__All: meetings notes available in real time at: https://etherpad.openstack.org/p/freezer_meetings16:02
m3m0__hello all, the first topic of the meeting will be parallel backups16:03
m3m0__#topic parallel backups16:03
m3m0__reldan any update?16:03
daemontool_Hi m3m0__16:03
reldanHi m3m016:03
*** memogarcia has joined #openstack-freezer16:03
reldanI’m working on parallelb backups. Everything seems to be nice, I have a MultipleStorage now, so it seems a big of part of code will be the same as before16:04
reldanI’m going to show result next week16:04
m3m0__cool, any blockers that you have so far?16:04
reldanNope, have no blockers. Everything is clear16:05
m3m0__is this going to be release for liberty right?16:05
m3m0__what will be next?16:05
reldanI don’t know, Fausto should know better. We decided that deadline will be 25 November.16:06
m3m0__we need to define that on the freezer roadmap16:06
daemontool_yep16:07
daemontool_==16:07
daemontool_++16:07
m3m0__https://wiki.openstack.org/wiki/FreezerRoadmap16:07
reldanWhat will be next. I would like to make some changes in swift storage.16:07
m3m0__anything critical?16:07
reldanNope, just code optimization and cleaning16:07
reldanI also would like to refactor 1) lvm and shadow (separate database locking from snapshotting)16:08
reldan2) mysql, mssql etc - I would like to have classes with some structure instead of functions16:09
daemontool_yes16:09
m3m0__#agree on that16:09
daemontool_reldan,  that sounds reasonable16:09
daemontool_#agreed16:09
m3m0__and I would like to add something to that16:09
m3m0__the sql server behaviour should be similar to the one in mysql16:09
daemontool_yep16:09
vannifreldan, code for snapshots and mysql needs to be intermixed. are we going to use some kind of "hooks" ?16:09
m3m0__where the database only gets locked at the snapshot creation16:10
reldanI don’t believe it should be intermixed. We should have separated objects for application and for lvm/shadow. Like16:10
reldanApplication: stop(); run()16:11
vannifyes. separated objects16:11
reldanSnapshot: create(); delete()16:11
reldanAnd probably the third class that will be actually execut it16:11
vannifbut, the procedure to backup calls the various methods in sequence16:11
vannifand has to roll back in case of errors16:11
reldanappllication.stop(); snapshot.create(); application.run(); snapshot.detete()16:11
reldanOk then16:12
reldanapplication.stop();16:12
reldantry snapshot.create()16:12
reldanfinally application.run()16:12
daemontool_the ; at the end came from Perl? lol :)16:12
reldanBecause now I cannot execute mysql backup on windows16:13
reldanAnd it’s really wrong16:13
m3m0__yes, the behaviour right now is very *unix16:14
reldanOr we can provide application to snapshot, or snapshot to application. But I absolutly belive, we shouldn’t know doing lvm/shadow about concrete mysql, mssql, mongodb stop/run implementation16:14
daemontool_#agreed16:15
m3m0__the less dependencies between each other the better16:15
daemontool_yep16:15
reldanhttp://pastebin.com/abeDAQ0h16:16
m3m0__that will allow us to create an snapshot at the begginig of the job and not in the action itself16:16
reldanline 7016:16
*** memogarcia has quit IRC16:16
reldanline 8516:16
reldanOtherwise it will be a lot of checks if mode is mysql … elif mode is mongodb … elif msserver ...16:17
reldanNext thing16:18
reldanI know that Zaher wants to provide possiblity to write plugins for freezer16:18
reldanLike I need to create s3 storage, but don’t want to share it. Probably it is not good enough for merging to master, but good engough to me16:18
reldanSo If I understand it correct, we should have some dir in freezer, scan this directory and loading modules from it16:19
m3m0__we need to explore the option on how horizon handles this16:19
reldanSounds good, but requres from us to think very carefully about internal interfaces16:19
m3m0__that way we can import/extend/override freezer functions and classes16:20
reldanWe should say, if you want to have new storage: 1) create class 2) implement methods a, b, c 3) add metainformation16:20
reldanyes, agree16:20
reldanSo we need to decide which components we would like to have pluggable16:21
reldanDecide and fix interfaces16:21
m3m0__I would like to be involved in that :)16:21
daemontool_m3m0__,  you are involved already :)16:21
m3m0__that's true :)16:22
reldanGreat ) So probably when we have time, we shold review components and interfaces between them16:22
reldanIt is all from my side16:22
m3m0__yep #agree16:22
daemontool_#agreed16:22
m3m0__does anyone has anything more to say on this topic?16:22
openstackgerritMemo Garcia proposed openstack/freezer-web-ui: Improved horizon dashboard for freezer  https://review.openstack.org/23617516:23
daemontool_(let's use a subsection in the wiki)16:23
*** memogarcia has joined #openstack-freezer16:23
m3m0__ok, next topic16:24
*** dschroeder has joined #openstack-freezer16:24
m3m0__#topic freezer included in the big tent16:24
daemontool_http://governance.openstack.org/reference/projects/freezer.html16:24
daemontool_congratulations to everybody :)16:24
m3m0__I would like to take a minute and congratulate everyone for this amazing achievement16:24
daemontool_++16:24
daemontool_#agreed16:25
m3m0__we need some more beers to celebrate :)16:25
daemontool_tonight 6:30 pm GMT :)16:25
daemontool_McSwiggans of Galway if anyone is interested :)16:25
m3m0__+216:25
Slashme_+1 congrats everyone16:26
m3m0__well moving to the next topic :) we are short on time16:26
*** memogarcia has quit IRC16:26
m3m0__#topic freezer api16:26
m3m0__vannif, any news?16:26
vannifyep. sent the code for review, with unit tests and coverage16:27
m3m0__which commit is it?16:27
m3m0__is the one related to action_id ??16:27
vannifnow, when creating a job in the api, the api can understand the content of the job, extract the actions and put them in the actions db with a proper action_id16:28
vannifhttps://review.openstack.org/#/c/24424516:28
m3m0__so guys, please review ^^16:28
vannifthe, solved some minor bugs with the db-init16:29
m3m0__question16:29
vannifhttps://review.openstack.org/#/c/244072/16:29
vannifhttps://review.openstack.org/#/c/243679/16:29
m3m0__when freezer is installed it create a freezer-db-init executable16:29
vannifshoot16:29
vannifyes16:29
*** fabriziof has joined #openstack-freezer16:29
m3m0__should it be there? I don't think it make sense in an end user perspective16:29
m3m0__but I could be wrong16:29
fabriziofhello all, sorry to be late16:30
vannifto be more precise, its in the freezer-api repo16:30
vannifnot freezer (agent)16:30
m3m0__oooooo16:30
*** memogarcia has joined #openstack-freezer16:30
m3m0__well makes more sense now16:30
vannifthe. you suggested the addition of a backup_uuid to support the  web-ui16:31
vannifand there is the issue of the client_id16:32
m3m0__there is also this commit related to the api: https://review.openstack.org/#/c/244563/16:32
vannifexaclty16:32
vannifregarding the client_id, we talked a little about that16:32
vannifto summarize:16:32
openstackgerritMerged openstack/freezer-api: fix freezer-db-init modifies replicas in test mode  https://review.openstack.org/24407216:33
vannifhaving it default to ptoject-id_hostname can result in conflicts16:33
vannifbut having it created as a uuid everytime can be a problem as well16:34
m3m0__yes, while retrieving data from the api when the you don't now the id for example16:34
vannifyes. so we are thinking of having it stored in a configuration file.16:34
m3m0__what happens if that configuration gets deleted?16:35
fabriziofvannif: a file where ?16:35
vannifwhen not defined it gets created, but then stored. so subsequent invocation of the freezer-scheduler (and the future python-freezerclient) will result in using the same client_if16:35
vannif*client_id16:35
vannifwe were thinking of ~/.freezer/scheduler.conf16:35
vannifor (if not present) /etc/freezer/scheduler.conf16:36
m3m0__why not /etc?16:36
m3m0__etc should be first IMO16:36
fabriziofin /etc you need to be root16:36
vannifto modify it, yes. anyway, we'll stick to *nix standard way of looking for config files, that's a side problem, I think.16:37
vannifthe important concept is that of storing the client_id locally16:38
fabriziofexactly vannif, I don't like the idea16:38
m3m0__why not? fabriziof ?16:39
vannifI'm not that sure too, but I can see it has some good points16:39
fabriziofif you loose the file ?16:40
m3m0__yes I agree with that point16:40
m3m0__is this a blocker vannif?16:41
Slashme_If you lose the file, you can recover the id from freezer-scheduler client-list16:41
*** memogarcia has quit IRC16:41
m3m0__there is a bp on this:16:41
Slashme_About the api, I'm working on a patch that will allow to define property that will span across multiple actions of a job.16:42
Slashme_When the api will receive a job that contains actions_default, it will expand those properties to all actions in that job.16:42
vannifhttps://blueprints.launchpad.net/freezer/+spec/better-client-id16:42
Slashme_Oosps wrong copy / paste16:42
Slashme_https://blueprints.launchpad.net/freezer/+spec/better-client-id16:42
m3m0__please all review this bp and send feedback16:43
fabriziofif you can retrieve the client_id then the only problem I see is security16:43
vannifthe client_id is not a secret even now16:44
vannifeven if you provide the client_id of another user, you need to provide valid OS credentials to access that information16:45
vannifor you mean something else ?16:45
fabriziofI'm just worried saving sensible thing locally on disk16:47
emildihttps://docs.python.org/2/library/uuid.html16:47
fabriziofsince most of the customers I have been in touch are concerned16:48
Slashme_What sensible info ?16:48
fabriziofusers / pwds / ids etc...16:49
*** memogarcia has joined #openstack-freezer16:49
fabriziofsometimes users of vm's are not allowed to access the openstack part16:49
Slashme_Yes, but the scheduler client_id is not sensitive at all16:50
fabriziofbut let's skip this for now and have a security specific discussion in the near future16:50
daemontool_++16:50
m3m0__and the users should have permissions at least to store data on swift and get a keystone token16:50
m3m0__#agree on that16:50
m3m0__we need to define that on the roadmap as well16:51
daemontool_I think we can move forward16:51
m3m0__anything more to say related to the api?16:51
daemontool_yes16:51
m3m0__#topic free4all16:51
daemontool_branching16:51
daemontool_so currently our code is aligned with kilo requirements16:51
m3m0__yes16:51
daemontool_as soon as https://review.openstack.org/#/c/244245/16:52
daemontool_is in we can create the stable/kilo branch16:52
m3m0__and as soon as we merge the new changes on the ui and api we have to create that branch16:52
daemontool_yes16:52
m3m0__this: https://review.openstack.org/#/c/236175/16:52
m3m0__and this: https://review.openstack.org/#/c/244563/16:52
daemontool_eggsactly thanks16:52
daemontool_after that16:52
Slashme_So, stable/kilo tomorrow? And we need to define the date where we will branch liberty so I can put it on the roadmap16:52
m3m0__do we need to agree on that this very moment Slashme_ ?16:53
daemontool_after stable/kilo, master will be liberty16:53
daemontool_Slashme_, I think as soon as the parallel backup change is in16:53
daemontool_we can branch liberty16:53
*** memogarcia has quit IRC16:54
daemontool_and in master align the requirements with mitaka16:54
daemontool_so I think, no late than tomorrow we need to create stable/kilo16:54
m3m0__so, as Slashme_ said after kilo, liberty should be very quick relase16:54
m3m0__only containing few new features and bug fixes16:55
m3m0__because we need to catch up with mitaka16:55
daemontool_and also see if anything brake after we change the requirements16:55
daemontool_yes16:55
m3m0__for liberty we need to send the windows scheduler16:55
m3m0__I'll work on that16:55
daemontool_we need to make sure freezer works with kilo onwards..16:55
daemontool_ok16:55
daemontool_#agreed16:56
m3m0__and for mitaka test coverage for web-ui16:56
daemontool_++16:56
daemontool_let's write that in the wiki please16:56
daemontool_so we can send an email to the OS ml16:56
m3m0__yes, and send an email to the openstack-dev16:56
daemontool_++16:57
daemontool_and release also a new pypi version16:57
daemontool_so looks like16:57
m3m0__so we can agree that will release liberty by the end of december?16:57
daemontool_openstack is movign away16:57
daemontool_from release with dates16:57
m3m0__to releases with ...?16:57
daemontool_m3m0__,  before Christmass16:57
daemontool_like16:57
daemontool_release 2015.12.1016:58
m3m0__liberty by 24 of of december?16:58
daemontool_that is not used anymore16:58
daemontool_liberty16:58
daemontool_I'd say by 18th of dicember16:58
daemontool_december16:58
daemontool_no later than that16:58
*** memogarcia has joined #openstack-freezer16:58
daemontool_it would be more then 1 month from now16:58
*** marzif has quit IRC16:59
m3m0__20 is a friday16:59
Slashme_+1 fot 2016:59
m3m0__ok guys we are running out of time16:59
daemontool_isn't 18th of December aq Friday?16:59
m3m0__are we clear on the next steps?16:59
*** marzif has joined #openstack-freezer17:00
daemontool_ok17:00
daemontool_also17:00
daemontool_I'd like to propose the following17:00
daemontool_Slashme_, as a core reviewer, all in favor?17:00
m3m0__+217:00
daemontool_vannif, fabriziof ?17:01
daemontool_reldan,  ?17:01
daemontool_sounds good?17:01
vannif#agree17:01
daemontool_and reldan also as a core reviewer, all in favor?17:01
vannifand reldan too17:01
daemontool_yes17:02
daemontool_:)17:02
vannifyes17:02
reldan:)17:02
m3m0__+2 for reldan as well17:02
Slashme_+1 for @reldan17:02
daemontool_we have to send an email to the openstack-dev ml17:02
daemontool_but before17:02
daemontool_I'd like to send the roadmap changes that was requested by the TC17:02
daemontool_so please let's do that fast :)17:02
daemontool_so please when I send the email for Slashme_  and reldan, the current cores send a reply with +117:03
daemontool_as that is how it works in os17:03
m3m0__yes of course17:03
daemontool_I'm also revisiting the mission17:04
daemontool_with dhellmann17:04
daemontool_that's all from me17:04
m3m0__thanks a lot daemontool_17:04
daemontool_I'd like to add block based incrementals for Liberty17:04
daemontool_let's see if I can make it17:04
*** marzif has quit IRC17:05
m3m0__guys thanks for your time17:05
m3m0__and please review17:05
m3m0__#endmeeting17:05
openstackMeeting ended Thu Nov 12 17:05:27 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:05
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_freezer_12_11_2015/2015/openstack_freezer_12_11_2015.2015-11-12-16.02.html17:05
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_freezer_12_11_2015/2015/openstack_freezer_12_11_2015.2015-11-12-16.02.txt17:05
reldanthank you m3m017:05
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_freezer_12_11_2015/2015/openstack_freezer_12_11_2015.2015-11-12-16.02.log.html17:05
vannifthanks everyone17:05
*** marzif has joined #openstack-freezer17:06
daemontool_vannif,  just a minor comment here https://review.openstack.org/#/c/244245/17:06
vannifto have a single exit point ? sounds good17:07
daemontool_m3m0__,  as you are the chairman, can you take a look here? https://review.openstack.org/#/c/241039/ revive it17:08
daemontool_and find a suitable time17:08
daemontool_?17:08
daemontool_:)17:08
daemontool_https://review.openstack.org/#/c/241039/3/meetings/freezer-meeting.yaml17:08
m3m0__ok I will17:08
*** memogarcia has quit IRC17:10
openstackgerritFabrizio Vanni proposed openstack/freezer-api: create actions when creating jobs  https://review.openstack.org/24424517:11
*** memogarcia has joined #openstack-freezer17:13
*** marzif has quit IRC17:20
*** szaher_ has quit IRC17:22
*** memogarcia has quit IRC17:41
*** memogarcia has joined #openstack-freezer17:43
*** reldan has quit IRC17:50
*** reldan has joined #openstack-freezer17:51
*** memogarcia has quit IRC17:53
*** memogarcia has joined #openstack-freezer18:00
*** reldan has quit IRC18:01
*** memogarcia has quit IRC18:11
*** memogarcia has joined #openstack-freezer18:13
*** memogarcia has quit IRC18:16
openstackgerritMerged openstack/freezer-api: create actions when creating jobs  https://review.openstack.org/24424518:17
*** memogarcia has joined #openstack-freezer18:23
*** memogarcia has quit IRC18:26
*** memogarcia has joined #openstack-freezer18:29
*** jonaspf has quit IRC18:31
*** fabriziof has quit IRC18:51
*** memogarcia has quit IRC18:58
*** memogarcia has joined #openstack-freezer19:01
*** reldan has joined #openstack-freezer19:12
*** memogarcia has quit IRC19:27
*** memogarcia has joined #openstack-freezer20:40
*** memogarcia has quit IRC20:46
*** samuelBartel has joined #openstack-freezer20:55
*** memogarcia has joined #openstack-freezer20:55
*** memogarcia has quit IRC20:57
*** reldan has quit IRC21:11
*** reldan has joined #openstack-freezer21:25
*** reldan has quit IRC21:35
*** memogarcia has joined #openstack-freezer21:35
*** reldan has joined #openstack-freezer21:39
*** memogarcia has quit IRC21:48
*** memogarcia has joined #openstack-freezer21:51
*** memogarcia has quit IRC21:58
*** reldan has quit IRC22:18
*** memogarcia has joined #openstack-freezer22:23
*** reldan has joined #openstack-freezer22:31
*** memogarcia has quit IRC22:43
*** memogarcia has joined #openstack-freezer23:03
*** reldan has quit IRC23:09
*** reldan has joined #openstack-freezer23:10
*** memogarcia has quit IRC23:16
*** samuelBartel has quit IRC23:18
*** reldan has quit IRC23:55
*** reldan has joined #openstack-freezer23:55
*** reldan has quit IRC23:56
« Wednesday, 2015-11-11 Index Friday, 2015-11-13 »

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