Thursday, 2015-11-26

*** reldan has joined #openstack-freezer00:07
*** reldan_ has joined #openstack-freezer00:24
*** reldan has quit IRC00:24
*** reldan_ is now known as reldan00:24
*** memogarcia has quit IRC00:45
*** reldan has quit IRC01:04
*** openstack has joined #openstack-freezer05:57
*** szaher has quit IRC05:58
*** szaher has joined #openstack-freezer06:58
*** szaher has quit IRC07:02
*** openstack has quit IRC07:28
*** openstack has joined #openstack-freezer14:08
*** daemontool has quit IRC14:12
*** daemontool has joined #openstack-freezer14:14
*** reldan has quit IRC14:22
openstackgerritFabrizio Vanni proposed openstack/freezer-api: fix db_init number of replicas  https://review.openstack.org/25040814:24
*** vannif has joined #openstack-freezer14:24
daemontoolvannif,  is this critical https://review.openstack.org/#/c/250408/1 ?14:30
SlashmeYes14:31
SlashmeAnd we need to backport id14:32
Slashmes/id/it/14:32
daemontoolwell... we need to do that fast then...14:33
*** reldan has joined #openstack-freezer14:43
openstackgerritMerged openstack/freezer-api: fix db_init number of replicas  https://review.openstack.org/25040814:57
SlashmeBackport change, please approve: https://review.openstack.org/25042615:02
openstackgerritMemo Garcia proposed openstack/freezer-web-ui: General dashboard enhancements  https://review.openstack.org/24984515:05
openstackgerritMerged openstack/freezer-web-ui: General dashboard enhancements  https://review.openstack.org/24984515:17
daemontoolall: after branching liberty, I'm going to add as voting the dsvm gate job on the 3 repos15:20
*** daemontool has quit IRC15:31
*** samuelBartel has joined #openstack-freezer15:34
*** daemontool has joined #openstack-freezer15:39
*** jonaspf has quit IRC15:42
*** daemontool has quit IRC15:44
*** daemontool has joined #openstack-freezer15:48
SlashmeBackport change #1 for the freezer-web-ui : https://review.openstack.org/#/c/250460/15:55
*** jonaspf has joined #openstack-freezer15:58
SlashmePlease approve15:59
daemontoolm3m0_,  let's try to have 2 different persons to approve, unless there are catastrphic events16:00
m3m0_guys are you ready for the meeting?16:01
daemontoolyes16:01
m3m0_#startmeeting openstack-freezer 26-11-201516:02
openstackMeeting started Thu Nov 26 16:02:05 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_26_11_2015'16:02
m3m0_All: meetings notes available in real time at: https://etherpad.openstack.org/p/freezer_meetings16:02
m3m0_daemontool, you are first16:02
daemontoolok16:02
daemontoolI've been doing mainly code reviews16:02
daemontoolstarted to reintegrate16:03
daemontoolthe block based incremetnal16:03
daemontoolto mster16:03
*** ffresh has joined #openstack-freezer16:03
daemontoolI think we'll have it for mitaka,16:03
daemontoolstretch goal for liberty16:03
daemontoolI need to modify the mission statement for freezer in openstack/governance16:04
daemontoolenable the dsvm gate jobs in the 3 repos as voting16:04
daemontooland as soon as we can16:04
daemontooldo the branching for liberty16:04
daemontoolthere's a discussion going on on the openstack-dev ml16:04
daemontoolfor stable branching16:04
m3m0_what about having the need for 2 cores to approve a commit?16:04
daemontoolwe might have to change16:04
daemontoolour branches name16:05
daemontoolm3m0_,  yes, I think that make sense16:05
daemontooleven more for stble branch16:05
daemontool1 eng give +2 and one give +A16:05
daemontoolallthogh we need to devine16:05
daemontooldefine16:05
daemontoolhow to manage urgent situation16:05
daemontoollike hotfix, security patches16:05
daemontooland something that is really critical16:05
daemontoolI think on that case one eng can give +2+A but at any rate16:06
daemontoolthe same person that submit the patchset, shouldn't approve his/her own code16:06
m3m0_I agree on those special sitations but still we have several cores at the same time available16:06
m3m0_oh yeah thats for sure16:06
m3m0_not even in remote cases16:07
daemontoolyep. Other than that, I need to create a asap the openstack/python-freezerclient16:07
daemontoolrepo and also the openstack/freezer-specs16:07
daemontoolso we can put our specs ther like other projects are doing16:07
m3m0_how long will it take?16:07
daemontoolcreating the repo is fast16:08
daemontoolsplitting the code I don't know16:08
daemontoolbut we need to do that for Mitaka for sure16:08
daemontoolI also have the perception16:08
daemontoolthat we are not writing bp16:08
daemontoollike before16:08
daemontooleven for simple tasks16:09
daemontoolthat's important16:09
daemontoolas if there's a new contributor16:09
daemontoolthat want to start with easy things16:09
daemontoolnow it's difficult16:09
m3m0_you are correct there, should we start giving -1 if a bp is not present?16:09
daemontoolyes16:09
daemontooljenkins should give -116:09
daemontoolbp or bug16:09
daemontoolalso16:09
daemontoolI think we need to add in the wiki16:10
m3m0_#action every commit have to have bp or bug associated with it16:10
daemontool#agreed16:10
daemontoolwe need to add to the wiki16:10
daemontoolprobably who's mainly working on something16:10
daemontoolthat help us to organize etter16:10
daemontoolbetter16:10
m3m0_do you want to do that?16:10
daemontoolas i.e. m3m0_  can write the bp for web ui16:10
daemontoolvannif,  can write bp for api16:11
daemontooland so on16:11
daemontoolso if there's someone that looks for someone on some specific component16:11
daemontoolwe have the guy/girl right there16:11
daemontooljust a thought, not sure it make sense or not16:11
m3m0_it makes a lot of sense16:12
daemontooleach one of us should be responsible/accountable for one component16:12
m3m0_altough I'm not so sure if everyone has to have knowledge of all the components16:12
daemontoolexactly16:12
daemontoolthat's also one of the reasons16:13
daemontoolalso...16:13
daemontoolwe need to thing, what we can do16:13
daemontoolto involve more people in the project16:13
daemontoolwe need to be more16:13
m3m0_how can we do that?16:14
daemontoolI don't know16:14
daemontoolevents16:14
daemontoolmeet up16:14
daemontooltalks16:14
daemontoolsessions16:14
daemontooland so on16:14
daemontoollike the one you wanted to do at pycon16:14
daemontoolthat things helps a lot16:14
daemontoolthings is16:14
daemontoolthat now it's not very easy to start contributing on freezer16:15
daemontoolwe need to make that more simple16:15
m3m0_let's first start with the bp, wiki and roadmap16:15
daemontoolok16:15
m3m0_so that way at least new people will have an idea on what they can contribute16:15
m3m0_it's not like they will be bound to that path but its a good starting point16:16
daemontoolyes16:16
daemontoolyep16:16
daemontoolwe need to document things like16:16
daemontoolif you want to add a new storage media, do this this and that16:17
daemontoolif you want to add a new application aware backup touch here and here and there16:17
daemontoolweb ui the same16:17
daemontoolapi the same16:17
m3m0_I completly agree on that point, even for us sometimes is difficult to modify code :P16:18
daemontoolquestion is, in the new company where I'm going...  if there are people interested (and there will be)16:18
daemontoolwhere should tey start?16:18
daemontools/tey/they/16:18
m3m0_read the roadmap16:18
daemontoolhow can we make thigns easy for new comers16:18
daemontoolyes16:18
daemontoolthat ok16:18
daemontooleven coming on irc16:18
daemontooland reading all the docs16:19
m3m0_yes of course16:19
daemontooland play with devstack16:19
daemontoolthat's documented16:19
daemontoolbut how to be orientated16:19
daemontoolwithin the code16:19
daemontoolthat's the difficult part16:19
m3m0_I will suggest that new people start documenting stuff (boring I know but useful)16:19
daemontoolyes16:19
daemontoolso that's all from me16:19
m3m0_inline comments will be perfect16:19
daemontoolyes16:19
m3m0_once we have the bp in place16:20
m3m0_and the specs16:20
m3m0_will be easier16:20
daemontoolyes16:20
m3m0_ok, thanks daemontool16:20
daemontooleach one of us16:20
m3m0_please let us know when the repos are available16:20
daemontoolshould probably spent 20 minutes every week16:20
daemontoolwriting bp of things that we need have to be improved16:20
daemontoolsmall or big16:20
daemontoolok16:20
m3m0_I did this template16:21
m3m0_https://blueprints.launchpad.net/freezer-web-ui/+spec/template-blueprint16:21
m3m0_is quite specific to the ui16:21
m3m0_but can be implemented for the whole project16:22
daemontoolm3m0_,  we just said the same engineer doesn't give +2 +A if there's not +2 already by some different engineer16:22
daemontoolhttps://review.openstack.org/#/c/250474/16:22
daemontool:)16:22
daemontoolok16:22
m3m0_hahahaha I was under preasure :) and those changes are only backported to kilo :P16:22
daemontooleven more in kilo16:22
m3m0_but won't happen again :P16:22
daemontoolto modify stable/kilo16:22
daemontoolor any stable16:22
daemontoolwe need to have 2 or more people16:23
daemontoolok16:23
m3m0_do you have anything more to say daemontool?16:24
*** szaher has joined #openstack-freezer16:24
daemontoolm3m0_,  nope all good16:25
m3m0_thanks a lot :)16:26
m3m0_vannif, you;re next16:26
vannifthanks mr chairman16:26
vannifbesides some code reviews and quick fixes, I've been looking to the user point of view16:27
vannifthat means16:27
vannifthe BaaS aspect16:27
vannifso. backup of cinder volumes, ephemeral volumes, VMs16:28
vannifand how to make it usable from the ui for a "normal" user16:28
vannifI'm also messing with screen recordings and video editing to record some demos16:29
m3m0_perfect16:29
vannifin particular, the first would be the backup and restore of mysql on the control plane16:29
m3m0_BTW have you think about including elasticsearch as a mode in freezer?16:29
vannifthe type of demo we have been presenting from time to time16:29
vannifyou mean, backing up of elasticsearch besides mysql ?16:30
m3m0_yes16:30
vannifno. I think that postgres and oracle have precedence16:30
vannifbut that's my idea16:30
m3m0_not so sure about this, at least we should have a way to backup ourselves16:31
m3m0_daemontool Slashme any thoughts?16:31
ffreshmaybe elasticseaarch is easy to backup16:32
*** memogarcia has joined #openstack-freezer16:32
ffreshat least freezer stuff16:32
*** daemontool_ has joined #openstack-freezer16:32
m3m0_as long as we can flush the data shouldn't be that difficult16:33
reldanActually elasticsearch is more like swift. You can setup as many replics as you want16:34
m3m0_so, should be worried about that?16:35
*** daemontool has quit IRC16:35
reldanI don’t know actually. In case if we have possiblity to lose all replicas with hdd. and it is criticall data - it have sense to have backup16:36
*** memogarcia has quit IRC16:37
reldanhttps://www.elastic.co/guide/en/elasticsearch/guide/current/backing-up-your-cluster.html16:37
reldanBut I suppose just file level backup of elasticsearch isn’t best option16:37
m3m0_let's think about this further16:39
m3m0_vannif do you have anything more to say?16:39
vannifno16:39
vannifthanks16:39
m3m0_cool, thanks a lot16:39
m3m0_reldan you are next16:39
reldanThank you m3m0_ !16:39
reldanI have an amazion pull request, please review it - https://review.openstack.org/#/c/247840/16:40
reldanToday we had a discussion with m3m0 about parallel backup16:40
m3m0_all, please review this https://review.openstack.org/#/c/247840/16:40
reldanI really believe everyone should take a look and say his opinion16:41
m3m0_and as we agreed, the next iteration should have a way to continue storing the backups even if one or more than one but not all storages fails16:41
reldanm3m0_ is right, next thing will be policies / new version of metadata (we should discuss format)16:42
m3m0_do you want to setup and irc or local meeting when you are ready for discussion?16:42
reldanBecause now we can have a lot of containers / ssh-usernames / ssh-ports in one config file and we should show result accordiingly16:42
daemontool_I think you can have a local meeting, came up with something written16:44
daemontool_and organize a meeting16:44
reldanI would to prefer have a review first and answer any questions about this pull request. In this case everyone will have understanding how it works and will be able to have his own opinion16:44
daemontool_publicly16:44
daemontool_even asking feedback on openstack-dev16:44
m3m0_what do you mean about "show result accordiingly"?16:44
reldanI mean result of execution. Now if we have only one storage we are binary - backup success / backup fail or restore success /restore fail16:45
reldanAfter having different plicies it may be16:45
reldanBackup success (storage1 success, storage2 success, storage3 fail)16:45
m3m0_yep yep I agree with that16:45
m3m0_please all review the parallel backup commit16:46
m3m0_reldan do we have test case scenarios for this?16:46
reldanNow I have only one policiy - one fails - all fails. But I’m going to add one success - all success policy16:47
reldanAnd it is an open question - how I should inform user16:47
reldanThat some storages are failed, some are succeed16:47
reldanAnd what does it mean16:48
daemontool_reldan,  that's what we discussed in the past16:48
m3m0_logging.warning?16:48
daemontool_?16:48
daemontool_policy for multiple storage16:48
reldanYes, let’s say we have policy16:48
reldandifferent - but we should define output format for task16:49
reldanbefore policices it may be - failed/succeed16:49
daemontool_yes write down a few lines bp16:49
daemontool_so we can elaborate on that16:49
reldannow it may be succeed for 3 storages, failed for 116:49
m3m0_agree with daemontool_16:49
reldanAgree16:49
reldanBut please review my request )16:50
reldanThank you16:50
daemontool_reldan,  yes it takes a bit of time16:50
daemontool_to review it, try it16:50
daemontool_with different scenarios16:50
daemontool_I'll do my best to test and review it tomorrow16:50
*** daemontool_ has quit IRC16:51
reldanThank you, please give me any feedback not only about bugs in my code, but also any comments about approach/architecture are were appreciated16:51
reldanIt’s all from my side16:51
m3m0_thanks reldan16:51
*** daemontool_ has joined #openstack-freezer16:51
reldanThank you!16:51
m3m0_Slashme anything on your side?16:52
SlashmeI want to do some updates on the wiki16:52
SlashmeAnd work a few demo to put on youtube16:52
m3m0_cool, that really great16:53
daemontool_Slashme, brilliant16:53
SlashmeI was thinking: freezer-intro / freezer-install / freezer-cli /freezer-web-ui16:53
SlashmeAlso please review : https://review.openstack.org/#/c/24302116:53
m3m0_are we going to have french, italian, russian and spanish subtitles?16:53
SlashmeThat's all from my side16:53
Slashmem3m0_: good idea for subtitles16:54
m3m0_jajaja I'll do the russian ones16:54
daemontool_lol16:54
Slashme:)16:54
daemontool_there's something I think we should do...16:54
vannifI'll manage the arabic :)16:54
daemontool_we need to write in the commit message16:54
daemontool_why we are doing that16:54
m3m0_agree at least a short description of why, what and how16:55
daemontool_we need to think about api v216:55
daemontool_when why what in it16:55
daemontool_yes16:55
m3m0_so, all.16:56
m3m0_after this commits, every single commit has to have a bp or a bug, and a meaningful commit message16:56
m3m0_otherwise will get -1 by default is that ok with everyone?16:56
daemontool_yes16:56
daemontool_++16:56
Slashme#agreed16:56
daemontool_#agreed16:57
m3m0_http://cdn.meme.am/instances/65275854.jpg16:57
m3m0_cool, does anyone have anything to say?16:57
daemontool_samuelBartel, hi16:58
daemontool_m3m0_,  lol16:58
m3m0_we are running out of time16:59
m3m0_thanks everyone16:59
reldanThank you!16:59
m3m0_#endmeeting17:00
openstackMeeting ended Thu Nov 26 17:00:00 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_freezer_26_11_2015/2015/openstack_freezer_26_11_2015.2015-11-26-16.02.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_freezer_26_11_2015/2015/openstack_freezer_26_11_2015.2015-11-26-16.02.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_freezer_26_11_2015/2015/openstack_freezer_26_11_2015.2015-11-26-16.02.log.html17:00
daemontool_thanks m3m0_17:00
openstackgerritMerged openstack/freezer-api: Add support for properties that span across all action of a job  https://review.openstack.org/24302117:07
*** samuelBartel has quit IRC17:33
*** reldan has quit IRC17:44
openstackgerritFabrizio Vanni proposed openstack/freezer-api: change default value for number of replicas  https://review.openstack.org/25050817:49
openstackgerritMerged openstack/freezer-api: change default value for number of replicas  https://review.openstack.org/25050818:01
*** daemontool_ has quit IRC18:34
*** openstackgerrit has quit IRC18:49
*** vannif_ has joined #openstack-freezer18:58
*** jonaspf has quit IRC19:01
*** vannif has quit IRC19:01
*** emildi has quit IRC19:01
*** Jokke_ has quit IRC19:01
*** epheo_ has quit IRC19:01
*** smekel has quit IRC19:01
*** ffresh has quit IRC19:01
*** Slashme has quit IRC19:01
*** emildi has joined #openstack-freezer19:02
*** Jokke_ has joined #openstack-freezer19:05
*** openstackgerrit has joined #openstack-freezer19:11
*** ffresh has joined #openstack-freezer19:11
*** Slashme has joined #openstack-freezer19:11
*** Slashme has quit IRC19:14
*** epheo_ has joined #openstack-freezer19:14
*** smekel has joined #openstack-freezer19:14
*** Slashme has joined #openstack-freezer19:18
*** Jokke_ has quit IRC19:26
*** emildi has quit IRC19:27
*** Jokke_ has joined #openstack-freezer19:29
*** vannif_ has quit IRC19:39
*** reldan has joined #openstack-freezer19:39
*** vannif_ has joined #openstack-freezer19:39
*** emildi has joined #openstack-freezer19:48
*** reldan has quit IRC20:14
*** reldan has joined #openstack-freezer20:24
openstackgerritMemo Garcia proposed openstack/freezer: Initialize freezer-scheduler with insecure mode  https://review.openstack.org/25052820:26
*** Slashme_ has joined #openstack-freezer20:53
*** Slashme has quit IRC20:57
*** openstackgerrit has quit IRC21:06
*** openstackgerrit has joined #openstack-freezer21:07
*** reldan has quit IRC21:36
*** reldan has joined #openstack-freezer21:38
*** reldan has quit IRC21:56
*** memogarcia has joined #openstack-freezer22:00
*** reldan has joined #openstack-freezer22:00
*** reldan has quit IRC22:37
*** smekel has quit IRC22:51
*** nullvariable has quit IRC22:51
*** nullvariable has joined #openstack-freezer23:39
*** memogarcia_ has joined #openstack-freezer23:47
*** openstackgerrit has quit IRC23:47
*** openstackgerrit_ has joined #openstack-freezer23:48
*** openstackgerrit_ is now known as openstackgerrit23:48
*** memogarcia has quit IRC23:54

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