Wednesday, 2013-09-25

*** markwash has quit IRC00:00
*** ErikB has joined #openstack-meeting-alt00:06
*** yidclare has quit IRC00:14
*** sarob has joined #openstack-meeting-alt00:16
*** nosnos has joined #openstack-meeting-alt00:16
*** kgriffs is now known as kgriffs_afk00:20
*** sarob has quit IRC00:20
*** wastrel has quit IRC00:23
*** jmaron has joined #openstack-meeting-alt00:35
*** jmaron has quit IRC00:39
*** sacharya has quit IRC00:42
*** malini is now known as malini_afk00:43
*** colinmcnamara has joined #openstack-meeting-alt00:52
*** ErikB1 has joined #openstack-meeting-alt00:55
*** ErikB1 has quit IRC00:55
*** ErikB1 has joined #openstack-meeting-alt00:56
*** ErikB has quit IRC00:58
*** lblanchard has quit IRC01:02
*** anteaya has quit IRC01:02
*** amytron has joined #openstack-meeting-alt01:06
*** demorris has joined #openstack-meeting-alt01:07
*** IlyaE has joined #openstack-meeting-alt01:10
*** sacharya has joined #openstack-meeting-alt01:10
*** IlyaE has quit IRC01:21
*** saurabhs has quit IRC01:33
*** jmaron has joined #openstack-meeting-alt01:35
*** jmaron has quit IRC01:40
*** markwash has joined #openstack-meeting-alt01:44
*** markwash has quit IRC01:45
*** IlyaE has joined #openstack-meeting-alt01:47
colinmcnamara#meetingtopic openstack-training-guides01:53
colinmcnamara#startmeeting01:53
openstackcolinmcnamara: Error: A meeting name is required, e.g., '#startmeeting Marketing Committee'01:53
colinmcnamara#startmeeting test01:53
openstackMeeting started Wed Sep 25 01:53:45 2013 UTC and is due to finish in 60 minutes.  The chair is colinmcnamara. Information about MeetBot at http://wiki.debian.org/MeetBot.01:53
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.01:53
*** openstack changes topic to " (Meeting topic: test)"01:53
openstackThe meeting name has been set to 'test'01:53
colinmcnamara#endmeeting01:53
*** openstack changes topic to "OpenStack meetings (alternate)"01:54
openstackMeeting ended Wed Sep 25 01:53:59 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)01:54
openstackMinutes:        http://eavesdrop.openstack.org/meetings/test/2013/test.2013-09-25-01.53.html01:54
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/test/2013/test.2013-09-25-01.53.txt01:54
openstackLog:            http://eavesdrop.openstack.org/meetings/test/2013/test.2013-09-25-01.53.log.html01:54
*** tanisdl has quit IRC01:58
colinmcnamararoll call, OpenStack-Training meeting02:00
*** sarob has joined #openstack-meeting-alt02:01
colinmcnamara#startmeeting openstack-training weekly team meeting02:01
openstackMeeting started Wed Sep 25 02:01:03 2013 UTC and is due to finish in 60 minutes.  The chair is colinmcnamara. Information about MeetBot at http://wiki.debian.org/MeetBot.02:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.02:01
*** openstack changes topic to " (Meeting topic: openstack-training weekly team meeting)"02:01
openstackThe meeting name has been set to 'openstack_training_weekly_team_meeting'02:01
colinmcnamarahello @sarob02:01
colinmcnamarahello sarob:02:01
sarobHay02:01
colinmcnamaralogged in through phone?02:01
colinmcnamarawe'll give 3 min for anyone else wanting to join02:02
sarobThe meeting name gots to be training-manuals02:02
colinmcnamara#endmeeting02:02
*** openstack changes topic to "OpenStack meetings (alternate)"02:02
openstackMeeting ended Wed Sep 25 02:02:53 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)02:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_training_weekly_team_meeting/2013/openstack_training_weekly_team_meeting.2013-09-25-02.01.html02:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_training_weekly_team_meeting/2013/openstack_training_weekly_team_meeting.2013-09-25-02.01.txt02:02
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_training_weekly_team_meeting/2013/openstack_training_weekly_team_meeting.2013-09-25-02.01.log.html02:02
sarobTo line up with the eavesdrop02:03
colinmcnamara#startmeeting training-manuals02:03
openstackMeeting started Wed Sep 25 02:03:03 2013 UTC and is due to finish in 60 minutes.  The chair is colinmcnamara. Information about MeetBot at http://wiki.debian.org/MeetBot.02:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.02:03
*** openstack changes topic to " (Meeting topic: training-manuals)"02:03
openstackThe meeting name has been set to 'training_manuals'02:03
sarobThx :)02:03
colinmcnamarabetter?02:03
sarobYup02:03
colinmcnamaraok, 2 more min and I'll kick it off02:03
*** ctracey has joined #openstack-meeting-alt02:03
sarobI'm on phone with bad reception02:03
*** SergeyLukjanov has joined #openstack-meeting-alt02:03
*** SergeyLukjanov has quit IRC02:03
colinmcnamarano worries02:03
sarobSo I will phase in and out02:03
colinmcnamarait's just you and I right now02:04
colinmcnamara60 second warning02:04
*** SergeyLukjanov has joined #openstack-meeting-alt02:04
colinmcnamaraits go time. Kicking meeting off02:04
colinmcnamarafirst topic02:05
colinmcnamara#Topic - Proposed Topics02:05
*** openstack changes topic to "- Proposed Topics (Meeting topic: training-manuals)"02:05
colinmcnamara1. Burn Down Status02:05
colinmcnamara2. Major Blocking issues02:05
colinmcnamara3. RST - Docbooks Status02:05
colinmcnamara4. david kramer log bug standard 70% done02:05
colinmcnamara5. check for prior commit02:05
colinmcnamaraare there any other topics that anyone would like to propose02:05
colinmcnamara?02:05
sarobNope02:05
colinmcnamara#info no additional proposed topics02:06
colinmcnamarachanging topic02:06
colinmcnamara#Topic Burn Down Status02:06
*** openstack changes topic to "Burn Down Status (Meeting topic: training-manuals)"02:06
colinmcnamarathis last week was a very productive week for the project02:06
sarobI'm going to be offline for 15min02:06
colinmcnamaraok02:06
colinmcnamarait's only you and I02:06
colinmcnamaraI will run through the meeting for the logs02:06
sarobIf you want to hold I'll be back02:07
colinmcnamaraon Sept 16 - 43 hours completed02:07
sarobOr not02:07
sarobUp to you02:07
colinmcnamarasure, what time will you return?02:07
colinmcnamara7:20?02:07
colinmcnamara#topic meeting break until 7:20 PDT02:08
*** openstack changes topic to "meeting break until 7:20 PDT (Meeting topic: training-manuals)"02:08
*** sarob has quit IRC02:10
*** crajohnson has joined #openstack-meeting-alt02:10
*** sarob has joined #openstack-meeting-alt02:21
sarobI'm back02:21
sarobI'm back02:21
sarobCool thx dude02:21
colinmcnamaracool02:22
colinmcnamara#topic meeting break end.02:22
*** openstack changes topic to "meeting break end. (Meeting topic: training-manuals)"02:22
colinmcnamara#Topic Burn Down Status02:22
*** openstack changes topic to "Burn Down Status (Meeting topic: training-manuals)"02:22
colinmcnamaraok, back on track02:23
colinmcnamaralast weeks meeting we had 43 cards completed02:23
colinmcnamaraas of today we have 5902:23
colinmcnamarathat is a huge increase02:23
colinmcnamarathis work brought the estimated burn down date from 12/22 to 12/102:23
colinmcnamaraeven with 5 cards added02:23
colinmcnamarahttps://BurndownForTrello.com/share/9c3rfd2fu902:24
colinmcnamara5 extra cards added - not in backlog02:24
colinmcnamara02:24
colinmcnamaraTotal Cards:134Remaining Cards:75Done Cards:59Percent of cards done:Hours at start:80Hours est total:134Hours remaining:75Hours done:59Percent of hours done:--------Days Elapsed54Daily Burndown1.09Est. Days Left68Est. Completion Date12/01/1302:24
colinmcnamaraSummary stats02:24
colinmcnamaraTotal Cards:13402:24
colinmcnamaraRemaining Cards:7502:24
colinmcnamaraDone Cards:5902:24
colinmcnamaraPercent of cards done:44.03%02:24
colinmcnamaraHours at start:8002:24
colinmcnamaraHours est total:13402:24
colinmcnamaraHours remaining:7502:24
colinmcnamaraHours done:5902:24
colinmcnamaraPercent of hours done:44.03%02:24
colinmcnamara--------02:24
colinmcnamaraDays Elapsed5402:24
colinmcnamaraDaily Burndown1.0902:24
colinmcnamaraEst. Days Left6802:24
colinmcnamaraEst. Completion Date12/01/1302:24
colinmcnamarathats better02:24
colinmcnamaraany questions / comments on our burn down rate?02:24
sarob Nope02:25
colinmcnamara#topic Major Blocking issues02:25
*** openstack changes topic to "Major Blocking issues (Meeting topic: training-manuals)"02:25
sarobRst to xml?02:26
colinmcnamaraI don't see any current issues blocking work, though I do forsea the RST to XML becoming an issue in 2 weeks02:26
colinmcnamaraI think that we need to figure it out in relatively short order02:26
colinmcnamaraI would say that it needs to be a status topic on next weeks meeting. and if there isn't forward process that we set a date the week after to do something ghetto02:27
colinmcnamarabut I do think we are close02:27
sarobAren't the dev rst docs where roles info should come from?02:27
colinmcnamararoles info?02:27
colinmcnamaraI've been mining them for the concepts and technology overview02:27
colinmcnamarasections02:27
colinmcnamarathey are a gold mine02:27
sarobI'm going to do a sample run of pandoc tomorrow02:28
colinmcnamaragood, let's multi-thread it02:28
colinmcnamarai'm at home all week, (no airplanes or cars) so I should make progress too02:28
sarobAny advice on tags to convert to02:28
sarobSections?02:29
colinmcnamaraI suggest let's over communicate if either finds something interesting02:29
sarobSounds good02:29
colinmcnamaraso, the output is article - section -section - section02:29
colinmcnamaralots of work, won't get solved tonight02:29
colinmcnamarabut I suggest that we both work on it, and then when kramer gets done with the bug link we rope him in02:30
sarobHmm, if I can just parse the article02:30
colinmcnamaraI suggest we both try alternate methods, and then compare our findings and communicate02:30
sarobSure, new bug file cool02:30
colinmcnamarait might just take a second set of eyes02:30
sarobSure02:30
colinmcnamaramoving on02:31
colinmcnamara#topic - david kramer log bug standard 70% done02:31
*** openstack changes topic to "- david kramer log bug standard 70% done (Meeting topic: training-manuals)"02:31
sarobVery nifty02:31
colinmcnamarahave you been following david's work on auto bug creation?02:31
sarobYup02:31
colinmcnamarame too02:31
sarobI'm ready to replace ours with his02:31
sarobWhen it's ready02:32
colinmcnamarais it added at post, or in the xml?02:32
sarobXml I believe02:32
colinmcnamaraI would agree that we should go and edit our XML, though I want to discuss whether that should be added to the backlog and we just change the example02:32
colinmcnamarajust being aware of adding work that does not get us to an alpha02:33
colinmcnamarayour perspective?02:33
colinmcnamarasarob: ?02:34
sarobIf it's easy replacement of a few lines, then it's okay with me02:35
sarobOtherwise it cab wait02:35
sarobCan02:35
colinmcnamaralet's see what it looks like.02:35
sarobYup02:35
colinmcnamara#topic check for prior commit - rebase / merge02:35
*** openstack changes topic to "check for prior commit - rebase / merge (Meeting topic: training-manuals)"02:35
colinmcnamaraso, last week I merged some code02:36
*** jmaron has joined #openstack-meeting-alt02:36
colinmcnamarathat overwrote bk001-ch003...02:36
colinmcnamarathat was my bad for not reviewing with a diff the chapter file02:36
sarobAh, right02:37
colinmcnamaraI worked out the proper procedure for dealing with that, and it is kind of complicated02:37
colinmcnamarainvolves a git rebase02:37
sarobSo you rebased?02:37
colinmcnamarayup02:37
colinmcnamarait was a pain, but I think I can get it down to not a pain02:37
sarobYeah, had to rebase02:38
sarobOnce last week too02:38
colinmcnamaraI think it will become second hand. but we may want to update the primary docs to have people check for a commit ahead of them02:38
colinmcnamaramost likely documented with treeview02:38
colinmcnamaraand then document the rebase procedure02:39
sarobSounds great02:39
colinmcnamaraand .. I think both of us need to make sure to take a close look at bk001-ch003... each time we merge in the review site to make sure lines aren't deleted02:39
sarobYup02:39
colinmcnamaraoh, think I should add one more topic02:40
sarobOkey dokey02:41
colinmcnamara#topic - sfbay meetup goal for next week02:41
*** openstack changes topic to "- sfbay meetup goal for next week (Meeting topic: training-manuals)"02:41
*** jmaron has quit IRC02:41
colinmcnamaraI'm assuming the goal is to get contributors, I think we will be at a point by mid next week that we should be able to get a bunch of commits02:41
colinmcnamarato keep focusing on increasing the average card rate02:42
colinmcnamarawhich will bring in our date02:42
sarobSounds good02:42
colinmcnamaraoh, and I have a couple new team members coming on line in the next few weeks. So expect increasing commits from NexusIS02:43
sarobSweet02:43
colinmcnamaraany other business ?02:43
sarobNope02:44
colinmcnamarak, meeting adjuourned02:44
sarobGood stuff02:44
colinmcnamara#endmeeting02:44
*** openstack changes topic to "OpenStack meetings (alternate)"02:44
sarobThx02:44
openstackMeeting ended Wed Sep 25 02:44:22 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)02:44
openstackMinutes:        http://eavesdrop.openstack.org/meetings/training_manuals/2013/training_manuals.2013-09-25-02.03.html02:44
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/training_manuals/2013/training_manuals.2013-09-25-02.03.txt02:44
colinmcnamarathank you02:44
openstackLog:            http://eavesdrop.openstack.org/meetings/training_manuals/2013/training_manuals.2013-09-25-02.03.log.html02:44
*** colinmcnamara has quit IRC02:45
*** sarob has quit IRC02:51
*** saurabhs has joined #openstack-meeting-alt02:57
*** saurabhs has quit IRC02:59
*** bdpayne has quit IRC03:04
*** kiall has quit IRC03:04
*** SergeyLukjanov has quit IRC03:05
*** demorris has quit IRC03:26
*** alok_ has quit IRC03:30
*** bdpayne has joined #openstack-meeting-alt03:33
*** bdpayne has quit IRC03:33
*** jmaron has joined #openstack-meeting-alt03:37
*** alok_ has joined #openstack-meeting-alt03:37
*** nosnos has quit IRC03:40
*** nosnos has joined #openstack-meeting-alt03:41
*** jmaron has quit IRC03:41
*** nosnos has quit IRC03:42
*** nosnos has joined #openstack-meeting-alt03:44
*** kgriffs_afk is now known as kgriffs03:48
*** kgriffs is now known as kgriffs_afk04:01
*** kiall has joined #openstack-meeting-alt04:09
*** flwang has quit IRC04:09
*** vipul is now known as vipul-away04:12
*** vipul-away is now known as vipul04:16
*** sarob has joined #openstack-meeting-alt04:17
*** IlyaE has quit IRC04:19
*** flwang has joined #openstack-meeting-alt04:25
*** sacharya has quit IRC04:26
*** sarob has quit IRC04:29
*** sarob has joined #openstack-meeting-alt04:29
*** sarob has quit IRC04:34
*** sarob_ has joined #openstack-meeting-alt04:34
*** IlyaE has joined #openstack-meeting-alt04:35
*** jmaron has joined #openstack-meeting-alt04:37
*** sarob_ has quit IRC04:38
*** sarob has joined #openstack-meeting-alt04:39
*** jmaron has quit IRC04:42
*** sarob has quit IRC04:43
*** nadya has joined #openstack-meeting-alt04:45
*** nadya has quit IRC04:55
*** nadya has joined #openstack-meeting-alt05:01
*** dmakogon_ has joined #openstack-meeting-alt05:02
*** nadya has quit IRC05:10
*** ErikB1 has quit IRC05:13
*** SergeyLukjanov has joined #openstack-meeting-alt05:18
*** SergeyLukjanov has quit IRC05:18
*** jmaron has joined #openstack-meeting-alt05:38
*** jmaron has quit IRC05:42
*** sarob has joined #openstack-meeting-alt05:49
*** flwang has quit IRC05:51
*** sarob has quit IRC05:54
*** akuznetsov has joined #openstack-meeting-alt06:02
*** jmaron has joined #openstack-meeting-alt06:39
*** nadya has joined #openstack-meeting-alt06:40
*** jmaron has quit IRC06:43
*** akuznetsov has quit IRC06:54
*** akuznetsov has joined #openstack-meeting-alt06:56
*** IlyaE has quit IRC07:14
*** enikanorov-w has quit IRC07:15
*** flwang has joined #openstack-meeting-alt07:16
*** enikanorov-w has joined #openstack-meeting-alt07:16
*** nadya has quit IRC07:19
*** jcoufal has joined #openstack-meeting-alt07:21
*** akuznetsov has quit IRC07:23
*** flaper87|afk is now known as flaper8707:30
*** ozstacker has quit IRC07:35
*** ozstacker has joined #openstack-meeting-alt07:35
*** jmaron has joined #openstack-meeting-alt07:39
*** jtomasek has joined #openstack-meeting-alt07:41
*** jmaron has quit IRC07:44
*** dmakogon_ has quit IRC07:56
*** NikitaKonovalov has joined #openstack-meeting-alt08:02
*** boris-42 has joined #openstack-meeting-alt08:20
*** jmaron has joined #openstack-meeting-alt08:40
*** NikitaKonovalov has quit IRC08:40
*** jmaron has quit IRC08:44
*** SergeyLukjanov has joined #openstack-meeting-alt08:58
*** aignatov has quit IRC09:15
*** aignatov has joined #openstack-meeting-alt09:16
*** jmaron has joined #openstack-meeting-alt09:40
*** jmaron has quit IRC09:45
*** jmaron has joined #openstack-meeting-alt10:41
*** jmaron has quit IRC10:46
*** crajohnson has quit IRC10:51
*** ruhe has joined #openstack-meeting-alt11:05
*** sacharya has joined #openstack-meeting-alt11:41
*** jmaron has joined #openstack-meeting-alt11:42
*** jmaron has quit IRC11:46
*** venkatesh has joined #openstack-meeting-alt11:58
*** ruhe has quit IRC12:00
*** pdmars has joined #openstack-meeting-alt12:12
*** shanks has quit IRC12:29
*** shanks has joined #openstack-meeting-alt12:32
*** venkatesh has quit IRC12:35
*** ruhe has joined #openstack-meeting-alt12:39
*** lblanchard has joined #openstack-meeting-alt12:43
*** jmaron has joined #openstack-meeting-alt12:58
*** jmaron has quit IRC13:03
*** anteaya has joined #openstack-meeting-alt13:09
*** julim has joined #openstack-meeting-alt13:12
*** SergeyLukjanov has quit IRC13:15
*** venkatesh has joined #openstack-meeting-alt13:15
*** demorris has joined #openstack-meeting-alt13:16
*** kgriffs_afk is now known as kgriffs13:25
*** amytron has quit IRC13:26
*** matty_dubs|gone is now known as matty_dubs13:26
*** jmaron has joined #openstack-meeting-alt13:31
*** eankutse has joined #openstack-meeting-alt13:44
*** julim has quit IRC13:45
*** tanisdl has joined #openstack-meeting-alt13:50
*** sacharya has quit IRC13:54
*** sacharya has joined #openstack-meeting-alt13:57
*** amytron has joined #openstack-meeting-alt13:57
*** nosnos has quit IRC14:08
*** kebray has joined #openstack-meeting-alt14:08
*** ruhe has quit IRC14:09
*** malini_afk is now known as malini14:13
*** rnirmal has joined #openstack-meeting-alt14:18
*** julim has joined #openstack-meeting-alt14:21
*** betsy has quit IRC14:25
*** kgriffs is now known as kgriffs_afk14:26
*** IlyaE has joined #openstack-meeting-alt14:27
*** jcoufal_ has joined #openstack-meeting-alt14:28
*** ruhe has joined #openstack-meeting-alt14:28
*** jcoufal has quit IRC14:28
*** jtomasek has quit IRC14:29
*** jmontemayor has joined #openstack-meeting-alt14:32
*** lblanchard has quit IRC14:32
*** bill_ibm has joined #openstack-meeting-alt14:35
*** markmcclain has joined #openstack-meeting-alt14:39
*** zane has joined #openstack-meeting-alt14:40
*** sacharya has joined #openstack-meeting-alt14:40
*** sacharya has quit IRC14:44
*** jtomasek has joined #openstack-meeting-alt14:45
*** ruhe has quit IRC14:51
*** yidclare has joined #openstack-meeting-alt14:55
*** bill_ibm has quit IRC15:00
*** bill_az_ has joined #openstack-meeting-alt15:01
*** betsy has joined #openstack-meeting-alt15:11
*** zane has quit IRC15:21
*** demorris has quit IRC15:26
*** zane has joined #openstack-meeting-alt15:29
*** zane has left #openstack-meeting-alt15:29
*** zane has joined #openstack-meeting-alt15:29
*** venkatesh has quit IRC15:32
*** venkatesh has joined #openstack-meeting-alt15:34
*** jtomasek has quit IRC15:36
*** jmaron has quit IRC15:39
*** demorris has joined #openstack-meeting-alt15:53
*** julim has quit IRC15:57
*** jcoufal_ is now known as jcoufal16:02
*** esker has joined #openstack-meeting-alt16:04
*** esker has quit IRC16:04
*** esker has joined #openstack-meeting-alt16:05
*** SergeyLukjanov has joined #openstack-meeting-alt16:05
*** akuznetsov has joined #openstack-meeting-alt16:05
*** venkatesh has quit IRC16:07
*** sarob has joined #openstack-meeting-alt16:07
*** alok_ has quit IRC16:14
*** markwash has joined #openstack-meeting-alt16:16
*** zane has quit IRC16:19
*** julim has joined #openstack-meeting-alt16:19
*** julim has quit IRC16:21
*** zane has joined #openstack-meeting-alt16:22
*** jmaron has joined #openstack-meeting-alt16:25
*** vinodmr has joined #openstack-meeting-alt16:48
*** sarob has quit IRC16:54
*** sarob has joined #openstack-meeting-alt16:55
*** akuznetsov has quit IRC16:55
*** Kiall2 has joined #openstack-meeting-alt16:58
*** Kiall2 has quit IRC16:59
*** Kiall2 has joined #openstack-meeting-alt16:59
*** kiall has quit IRC16:59
*** Kiall2 is now known as Kiall16:59
*** sarob has quit IRC17:00
Kiall#startmeeting Designate17:00
openstackMeeting started Wed Sep 25 17:00:25 2013 UTC and is due to finish in 60 minutes.  The chair is Kiall. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: Designate)"17:00
openstackThe meeting name has been set to 'designate'17:00
KiallHeya17:00
KiallWho's about?17:00
vinodmrhere17:00
betsy\o17:01
simonmcco/17:01
*** tsimmons has joined #openstack-meeting-alt17:01
*** mugsie has joined #openstack-meeting-alt17:01
KiallOkay :)17:01
Kiall#topic Review action items from previous weeks17:01
*** openstack changes topic to "Review action items from previous weeks (Meeting topic: Designate)"17:01
*** jcoufal has quit IRC17:01
*** matty_dubs is now known as matty_dubs|lunch17:01
*** matty_dubs|lunch has left #openstack-meeting-alt17:01
KiallFirst up - MySQL BIND9 Docs (CaptTofu)17:02
KiallHe's AFK at the moment, but it's still on his todo list :(17:02
KiallBP for Pools/Agent Replacement (mugsie)17:02
*** bill_az_ has quit IRC17:02
Kiallmugsie: here?17:02
mugsieyup17:02
Kiall#link https://wiki.openstack.org/wiki/Designate/Server_Pools17:02
*** bill_az_ has joined #openstack-meeting-alt17:02
mugsieany comments / feedback, let me know17:02
KiallCLI Docs (simonmcc)17:03
Kialland Python Binding Docs (kiall)17:03
simonmccyep, up & published to readthedocs17:03
KiallBoth are up on RTD17:03
Kiall#link http://python-designateclient.readthedocs.org/en/latest/17:03
KiallHopefully complete enough to be usable :)17:03
tsimmonsThat's great guys, thank you.17:04
simonmccindeed!17:04
KiallAnd .. That's all the open items from previous weeks .. just CaptTofu's to get closed :)17:04
Kiall#action CaptTofu MySQL BIND9 Docs17:04
KiallOkay so ..17:04
Kiall#topic Talk about standardizing logging17:04
*** openstack changes topic to "Talk about standardizing logging (Meeting topic: Designate)"17:04
Kiallvinodmr: about?17:04
Kiall#link https://blueprints.launchpad.net/designate/+spec/standardize-logging17:05
vinodmrI just wanted to be sure that the logs we use are useful for investigating issues when they arise17:05
*** bill_az_ has left #openstack-meeting-alt17:05
KiallSo, I'm guessing you guys have done some digging and have areas that could be improved?17:06
vinodmrDo you know if other openstack projects have a format for logging or standards on what they log to info vs debug?17:06
KiallThere was a push in nova maybe 2 releases ago to get INFO+ logging actually useful, they may have some guidelines from that excercise17:06
KiallBefore that, running nova without DEBUG logging was basically a requirement.17:07
vinodmrDo you mean running nova with DEBUG logging?17:08
KiallYea, about 2 releases ago.. running nova without DEBUG logging enabled basically meant you had no useful logs..17:08
KiallSomewhat similar to Designate today17:08
KiallSo - I reckon they came up with some guidelines on what to log, and at what level.. It would be worth trying to dig those out to help guide us :)17:09
vinodmrWe noticed the logging was not consistent or useful at some parts but did not spend enough time to look through to see what is needed etc17:09
vinodmrI can take a look at that as an action item17:10
*** sarob has joined #openstack-meeting-alt17:10
*** sarob has quit IRC17:10
KiallSure17:10
Kiall#action vinodmr Search out any logging guidelines from other OpenStack projects17:10
*** sarob has joined #openstack-meeting-alt17:11
KiallAnyway, we know the logging is missing in some areas, and set "too low" or inconsistently in others :(17:11
KiallIt's certainly something we need to figure out a standard for, and stick to it!17:11
mugsieagreed17:11
Kiall#action kiall review HP's DEBUG level logs, increase anything generally useful to INFO or above17:13
KiallI'll review our DEBUG logs over the next few days, and try and bump the level on anything that's generally useful for production..17:13
KiallProbably a good start.17:13
vinodmrThanks kiall.  That would be helpful17:13
*** eankutse has quit IRC17:14
KiallOkay - We'll come back to this next week after I've had a chance to review our logs, and we've had a chance to see what other projects do..17:14
*** eankutse has joined #openstack-meeting-alt17:14
*** jmcbride has joined #openstack-meeting-alt17:14
Kiallmake sense? :)17:14
vinodmrYes it does17:15
betsysounds perfect17:15
KiallCool17:15
KiallOkay ..17:15
Kiall#topic API v2.0 RecordSets - API Change17:15
*** openstack changes topic to "API v2.0 RecordSets - API Change (Meeting topic: Designate)"17:15
KiallSo .. while working on the v2 RecordSets API, we've found a issue that will need a change to the API spec.17:15
KiallEssentially, as whole RecordSets are updated in 1 go, we run into some concurrency issues with either multiple users making changes to the same recordset at once17:16
Kiallor users and automated services (designate-sink) making changes at once..17:16
KiallSo, I think we need to support both the "old style" and "new style" at once, meaning we would reintroduce /recordsets/<id>/records/<id> to the spec, to allow for single records to be changed independently of each other17:18
KiallI've not had a chance to update the spec yet, but wanted to get everyones thoughts before I do17:18
zaneThats a good idea17:19
betsyboth in the v2 spec?17:19
mugsieyeah, its also fits in with the changes I have made for pools / servers, having them as sub resources17:19
vinodmrSo do multiple users have access to the same recordset?17:19
Kiallbetsy: the spec is not updated yet, but the recordset container will still exist as it allows us to cleanly enforce some details of the RFCs17:20
zaneby multiple user you mean like subuser within an account17:20
jmcbrideSounds like the concern is that a record set could potentially contain a lot of data, which *might lead to a conflict as more users might need to update it.17:20
Kiallzane: well, more concurrency .. 1 user making two API calls at once, or a user and the sink service both modifying a recordset at once etc17:20
vinodmrkiall: yes17:20
Kialljmcbride: Well, This really hit me as I was updating the designate-sink code..17:21
zaneok17:21
KiallIn that case, the system itself is modifying customers recordsets, maybe adding a record matching the instance name etc17:21
KiallIf that happens while a user is making a call to the same recordset, one would "win"17:21
jmcbrideIs this a potential scenario for all create/update scenarios (its the age old pessimistic/optimistic locking problem)17:22
betsyBut would an 'A' record only consist of the IP address or would it be the full record like in v1?17:22
KiallIt's most noticeable on updates of recordsets, where the spec as it stands requires you to provide all the records at once..17:22
Kialle.g. a RRSet with 1.1.1.1 and 2.2.2.2 in it.17:23
KiallTo add 3.3.3.317:23
Kiallyou POST /domain/ID/recordsets/ID with {"records": [1.1.1.1, 2.2.2.2, 3.3.3.3]}17:23
KiallBut.. What if another concurrent API call adds 4.4.4.4, by doing a17:23
Kiallyou POST /domain/ID/recordsets/ID with {"records": [1.1.1.1, 2.2.2.2, 4.4.4.4]}17:23
Kiall(^ pseudocode examples btw)17:24
betsyright.17:25
betsyI just don't see how that's a different problem in RecordSets than exists current in v1 records17:25
betsy*currently17:25
vinodmrSo with this change, you minimize the chance of concurrency issues, but it will still exist - correct?17:25
Kiallbetsy: so, with the v1 API, you CRUD on 1 record at a time, while with the v2 spec as it is today, you CRUD on the recordset as a whole.17:26
betsytrue17:26
betsyI see what  you're saying17:27
Kiallvinodmr: I think we'll be down to the best case with the change I plan on making to the spec, i.e if two API calls come in to update the IP address of an A record at the exact same time.. One of them really has to "win"17:27
KiallBut, if two API calls come in to add/update/delete different records in an RRSet, they will both succeed17:27
betsyBut they still both also have to update the RS17:28
betsyThe update field in the RS would have to be updated in both cases17:28
tsimmonsSo RecordSets would just be full or Record ID's, that can then be changed independently, and unless you're creating or deleting a RecordSet, you need not modify the RecordSet? To create a record you just POST to recordsets/id/records?17:29
*** demorris has quit IRC17:29
Kialltsimmons: Essentially, yes. That said, batch operations on the RRSet should still be in spec (Create a recordset with these 10 records, delete the recordset including all records, replace the records in a RRSet with these 5 etc)17:30
tsimmonsFor sure, but if you're just messing with one record, which is most of the time, you don't need to modify the RRSet.17:30
*** eankutse has quit IRC17:31
tsimmonsThat way you kind of get the best of both worlds, you can do operations with multiple records with RRSets, but you can also do single operations with less concurrency issues.17:31
betsytsimmons: I think you still have to update the RRSet. The updated date field would need to be changed17:31
*** sacharya has joined #openstack-meeting-alt17:31
Kialltsimmons: yea, I think the "Replace a RRSet's records with these 5" is another case where it's perfectly okay for cases for 2 concurrent calls to have a "winner"17:32
KiallAnd allowing the records to be managed individually makes the common case easier17:32
vinodmrWith the change you are suggesting, if you get one update to an A record another to delete it - what would the behavior be?17:32
*** SergeyLukjanov has quit IRC17:32
KiallAnyway - I'll have the spec updated before Monday, hopefully you guys will have a chance on monday/tuesday to review before the next week..17:32
Kiallvinodmr: it depends, if the delete is processed first, the update would fail.17:33
Kialland if the update is processed first, the delete should suceed17:33
Kiallbefore the next meet*17:33
tsimmonsAgreed. So the operation to RRSet on a one-record update is just changing the updated_date field, and maybe something else small, but that would be done in one API call.17:33
KiallPretty much :)17:34
tsimmonsCool. I like that17:34
Kiall#action kiall Update APIv2 Spec (before Monday) with proposed RRset/Record changes17:35
KiallOkay .. Any more Q's before we move onto the last item?17:35
KiallGuess not :)17:36
Kiall#topic Pools Functionality17:36
*** openstack changes topic to "Pools Functionality (Meeting topic: Designate)"17:36
mugsiecool17:36
Kiallmugsie: you're up ..17:36
mugsieif you have had a chance to read the wiki page, you will see it has been broken up into 3 phases17:36
mugsiePhase One is nearly done - I need to fix the tests, but the code is in place, and the APIs have been updated17:37
mugsieif people want to review the code, the link to the gerrit patch is on that pages...17:37
mugsiehttps://blueprints.launchpad.net/designate/+spec/initial-server-pools17:38
mugsie^ that is the launchpad blueprint for phase one17:38
mugsieis there any questions about it?17:38
vinodmrNone now.  I will look at the wikipage and the code and might have questions for it next week17:39
betsyI haven't had a chance to review it yet, but I like that you have a link to the gerrit patch and the launchpad blueprint on the wiki page17:39
mugsievinodmr: if you want to ping me whenever its fine17:39
mugsiei am in the irc room permanetly17:40
vinodmrsure17:40
mugsiebetsy: thanks17:40
tsimmonsI'm hoping to give it a good look as well.17:40
mugsiecool17:40
Kiallas I am ;)17:40
mugsiephase one is *fairly big*17:40
mugsie(code additions wise)17:41
*** eankutse has joined #openstack-meeting-alt17:41
mugsie+1431, -15217:41
mugsieso it probably has a few issues17:41
mugsieanything else on it? or questions on the pools stuff in general?17:42
KiallOkay :) So .. It's another one to keep on the list for next week after people (including myself!) have a chance to poke holes and review17:43
KiallOkay ...17:43
Kiall#topic Open Discussion17:43
*** openstack changes topic to "Open Discussion (Meeting topic: Designate)"17:43
KiallAnything else from anyone? I've got nothing17:43
simonmccnothing here17:43
mugsienot from me17:44
tsimmonsMaybe just a quick status update on some of the open code reviews?17:44
Kialltsimmons: sure..17:44
vinodmrI just wanted to check on one the questions that I had yesterday - about created_by and last_modified_by17:45
KiallSome of the open code reviews should really just be abandoned!17:45
Kialle.g. my mockup of what statsd integration might look like17:45
*** julim has joined #openstack-meeting-alt17:45
tsimmonsYeah, Dirk Mueller hasn't been around either, we might reach out to him if possible and see what's up.17:45
Kialland "WIP Support for Floating IP PTRs" was little more than an experiment, I don't think anyone agreed with that approach ;)17:46
tsimmonsI'm not 100% sure about any others, but I know mine is in a waiting state? Is there anything I can do to help, or is there any update on that?17:46
KiallRe Dirk's, one of them seems invalid (Explicitely convert objects to string)17:46
Kialltsimmons: humm - I thought there was something outstanding in that17:47
KiallLooking again, no. There wasn't.17:47
Kiallhttps://review.openstack.org/#/c/45745/17:47
*** venkatesh has joined #openstack-meeting-alt17:47
Kiall^ I'll review that again this evening, but it should be good to merge :)17:47
tsimmonsCool, then I'm not sure about eankutse's but I think he's close.17:48
*** kiall_ has joined #openstack-meeting-alt17:48
Kialleankutse's is a little harder, he brought up a good point a day or so back17:48
Kiallre updating the serial when a server changes17:48
tsimmonsOh yeahhh. Forgot about that.17:48
vinodmrWhat about the powerdns backend - does it handle this?17:49
KiallSo .. I'm of 2 minds on that .. Perviousally, we didn't even update the servers at all.. So we're defiantly in a better place even if we don't come up with a fix for the serial issue straight away17:49
*** vipul is now known as vipul-away17:49
*** vipul-away is now known as vipul17:49
KiallBut I'm not sure if anyone has given it too much thought on how to fix it yet, I know I've been too busy the last couple of days.17:49
KiallI think it's something we should sit on for a few more days, hopefully come up with a fix before we land the change.17:51
vinodmrSince the serial # was not updated previously, should that be a separate change to ensure that it is fixed everywhere correctly?17:52
*** flaper87 has left #openstack-meeting-alt17:52
KiallThat was my "of 2 minds" bit, we're certainly in a better position with the review as is, but hopefully we can figure out a fix before we merge it :017:53
Kiall:)*17:53
*** pdmars has quit IRC17:53
*** pdmars has joined #openstack-meeting-alt17:53
KiallMake sense?17:54
tsimmonsYup. That's cool.17:54
vinodmryes17:54
KiallIf someone can't dream up a fix over the next few days, I'd say we push it in and add another bug for that part.17:55
KiallOkay .. Anything else? Nearly hitting on time!17:55
tsimmonsSo perhaps an action item to clean up the open reviews? If you think it's necessary.17:55
Kiall#action kiall Abandon his useless reviews17:56
vinodmrI just wanted to check on one the questions that I had yesterday - about created_by and last_modified_by17:56
tsimmonshahaha17:56
Kiall#action kiall Review pending stuff :)17:56
Kiallvinodmr: Sure17:56
*** eankutse has quit IRC17:56
vinodmrCurrently you mentioned that the modified by and created by are sent as notifications - so this would mean that someone else other than designate needs to track this information17:57
KiallSo, we don't currently store that info, and there is precedent in OpenStack projects for storing the user_id who created the "thing"..17:57
vinodmrwith things like concurrent changes in recordsets, if we want to look up who made the change, then it would be helpful to have this information handy17:58
Kiallvinodmr: yea, personally I feel that an audit trail is something we shouldn't include in designate, we should provide the hooks necessary to integrate with one, but not implement the whole end -> end audit trail ..17:58
*** pdmars has quit IRC17:58
Kialle.g. Deployers with Nova / Quantum and Designate will likely want an audit trail for everything17:58
vinodmrsure i will take a look at the links and we can revisit this issue later if needed18:00
*** eankutse has joined #openstack-meeting-alt18:00
vinodmrnothing else from me18:00
KiallYea, makes sense. I reckon we'll need to add hooks in places to send this info out, but I'm scared of implementing "Audit Trail as a Service" ;)18:00
*** rnirmal has quit IRC18:01
KiallOkay .. Time, and I think there's another meeting here now ..18:01
KiallThanks all :)18:01
Kiall#endmeeting18:01
*** openstack changes topic to "OpenStack meetings (alternate)"18:01
openstackMeeting ended Wed Sep 25 18:01:22 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/designate/2013/designate.2013-09-25-17.00.html18:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/designate/2013/designate.2013-09-25-17.00.txt18:01
openstackLog:            http://eavesdrop.openstack.org/meetings/designate/2013/designate.2013-09-25-17.00.log.html18:01
tsimmonsthanks guys18:01
*** tsimmons has left #openstack-meeting-alt18:01
mugsieo/18:02
*** mugsie has left #openstack-meeting-alt18:02
*** julim has quit IRC18:03
*** julim has joined #openstack-meeting-alt18:05
*** CaptTofu has joined #openstack-meeting-alt18:07
*** noslzzp has quit IRC18:08
*** pdmars has joined #openstack-meeting-alt18:09
*** vinodmr has left #openstack-meeting-alt18:10
*** julim has quit IRC18:10
*** Kiall has quit IRC18:11
*** dmyznikov has quit IRC18:11
*** demorris has joined #openstack-meeting-alt18:13
*** SergeyLukjanov has joined #openstack-meeting-alt18:17
*** slagle has quit IRC18:17
*** slagle has joined #openstack-meeting-alt18:19
*** sarob has quit IRC18:20
*** sarob has joined #openstack-meeting-alt18:31
*** esker has quit IRC18:40
*** julim has joined #openstack-meeting-alt18:42
*** jmcbride has quit IRC18:59
*** bdpayne has joined #openstack-meeting-alt19:00
*** eankutse has quit IRC19:01
*** eankutse has joined #openstack-meeting-alt19:03
*** julim has quit IRC19:05
*** venkatesh has quit IRC19:06
*** julim has joined #openstack-meeting-alt19:06
*** isviridov_ has joined #openstack-meeting-alt19:07
*** demorris has quit IRC19:09
*** venkatesh has joined #openstack-meeting-alt19:09
*** noslzzp has joined #openstack-meeting-alt19:16
*** IlyaE has quit IRC19:20
*** rnirmal has joined #openstack-meeting-alt19:25
*** dmakogon_ has joined #openstack-meeting-alt19:26
*** venkatesh has quit IRC19:28
*** vipul is now known as vipul-away19:30
*** KennethWilke has joined #openstack-meeting-alt19:31
*** IlyaE has joined #openstack-meeting-alt19:34
*** vipul-away is now known as vipul19:37
*** sarob_ has joined #openstack-meeting-alt19:38
*** dukhlov_ has joined #openstack-meeting-alt19:38
*** sarob has quit IRC19:40
*** sarob_ has quit IRC19:42
*** CaptTofu has quit IRC19:43
*** jmaron has quit IRC19:44
*** redthrux has joined #openstack-meeting-alt19:44
*** SergeyLukjanov has quit IRC19:47
*** julim has quit IRC19:49
*** imsplitbit has joined #openstack-meeting-alt19:50
*** vipul is now known as vipul-away19:52
*** julim has joined #openstack-meeting-alt19:52
*** datsun180b has joined #openstack-meeting-alt19:55
*** jmaron has joined #openstack-meeting-alt19:57
*** SlickNik has joined #openstack-meeting-alt19:59
*** robertmyers has joined #openstack-meeting-alt20:00
*** grapex has joined #openstack-meeting-alt20:00
*** vipul-away is now known as vipul20:00
*** cp16net has joined #openstack-meeting-alt20:00
*** jcru has joined #openstack-meeting-alt20:00
cp16netword20:00
*** malini is now known as malini_afk20:00
*** sarob has joined #openstack-meeting-alt20:01
KennethWilkehowdy20:01
SlickNikhey20:01
*** cweid has joined #openstack-meeting-alt20:01
vipulo/20:01
dmakogon_o/20:01
grapexo/20:02
imsplitbito/20:02
cp16neto^/20:02
cweido/20:02
robertmyerso/20:02
dukhlov_o/20:02
yogeshhi20:02
isviridov_Hi20:02
datsun180bhello20:02
*** sarob has quit IRC20:02
vipulhub_cap: ??20:02
*** lblanchard has joined #openstack-meeting-alt20:03
*** eankutse has quit IRC20:03
KennethWilkehe mentioned that he's about 5 minutes out20:03
grapexvipul: He'll be here in a minute20:03
david-lyleo/20:03
*** sarob has joined #openstack-meeting-alt20:03
amytrono/20:03
vipulok20:03
grapex#startmeeting trove20:03
SlickNikcool20:03
openstackMeeting started Wed Sep 25 20:03:22 2013 UTC and is due to finish in 60 minutes.  The chair is grapex. Information about MeetBot at http://wiki.debian.org/MeetBot.20:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:03
*** openstack changes topic to " (Meeting topic: trove)"20:03
openstackThe meeting name has been set to 'trove'20:03
SlickNikthanks grapex20:03
kevinconway7o720:03
SlickNik#link https://wiki.openstack.org/wiki/Meetings/TroveMeeting20:03
pdmarso/20:03
SlickNik#link http://eavesdrop.openstack.org/meetings/trove/2013/trove.2013-09-18-20.01.html20:04
grapex#topic Update to Action items20:04
*** openstack changes topic to "Update to Action items (Meeting topic: trove)"20:04
SlickNikFirst one is mine.20:04
*** saurabhs has joined #openstack-meeting-alt20:04
SlickNik1. SlickNik to check with hub_cap to make sure all contributors can create/edit blueprints.20:04
SlickNikI checked with hub_cap, and he is aware.20:04
*** akuznetsov has joined #openstack-meeting-alt20:05
SlickNikWe need to sync with other teams to find out how they do the permissions on LaunchPad.20:05
hub_captap tap tap... is this thing on20:05
hub_caphi guys20:05
hub_capoya we didnt do that SlickNik :D20:05
SlickNikhey20:05
SlickNikyeah, still WIP20:05
cp16netreaction it20:05
hub_caphey, im not sure how long its taking for my stuffs to reach you.... im on a slow connection20:05
imsplitbithub_cap: fail20:05
hub_capim gonna go directly to my proxy server20:06
vipulare you traveling again20:06
*** eankutse has joined #openstack-meeting-alt20:06
datsun180bsomewhere in berkeley there is a train with carrier pigeons streaming out of the back trying to carry irc packets20:06
SlickNik#action SlickNik, hub_cap to check with other teams to set  groups permissions correctly on LaunchPad20:06
*** eankutse has quit IRC20:06
*** eankutse has joined #openstack-meeting-alt20:06
hub_capok im on irssi now20:06
hub_capshould be good to go20:07
grapexMove on to ML or die?20:07
hub_capyes fail imsplitbit, im at UC berkeley career fair tethered to my phone.. 500+ kids w/ att iphones20:07
hub_capML OR DIE20:07
grapex#topic ML or die20:07
*** openstack changes topic to "ML or die (Meeting topic: trove)"20:07
SlickNikyes, grapex move on20:07
SlickNikthx20:07
hub_capok thats me20:07
hub_capsooooooo20:08
kevinconwayso what things should we send through the ML?20:08
hub_capive had a ton of private conversations w/ people20:08
kevinconwaycan we reply-all instead of irc?20:08
hub_capfor instance, weve talked a lot of service types20:08
*** NehaV has joined #openstack-meeting-alt20:08
grapexhub_cap: Service types seems perfect for the mailing list20:08
hub_capand amcrn and i have been talking a lot about how itll work20:08
hub_capyes i agree20:08
dmakogon_altough about clustering API20:08
hub_capyes clustering is perfect for the ML20:08
dmakogon_and clustering itself20:08
hub_capbasically use this as a rule of thumb20:09
hub_capif you want people to talk about if for more than 1 hr20:09
hub_capsend it ot the mailing list20:09
datsun180bjust tag it as [trove] in the subject of course20:09
hub_capie, api design discussions20:09
hub_capyes datsun180b good point to note20:09
kevinconwayis the tag case sensitive?20:09
kevinconway[TrOvE]?20:09
hub_capi get a lot of private emails, and i will send them to the ML20:09
datsun180bkevinconway: would advise sticking to all lowercase20:09
hub_capkevinconway: if you are jorgewiliams you can do that20:09
hub_capgrapex: knows what im talking about20:10
grapexhub_cap: lol20:10
grapexI wonder if there's a good catalyst here? Seems like has come up before. :)20:10
hub_capnot terribly case sensitive, but trove looks cleaner than say Trove or TrOvE20:10
hub_capor TROVE20:10
kevinconwayi like TROVE20:10
kevinconwayit matches HEAT20:10
hub_capill do my best to reply to people and ask them to push convo to the mailing list20:10
cp16netsounds good20:10
grapexhub_cap: Cool20:11
hub_caplol kevinconway nice nod to the heat is not a acronym20:11
vipulopenstack-dev20:11
hub_capyes20:11
hub_caplets start discussing in the public... we have good points to make20:11
hub_capand design especially20:11
kevinconwayare there topics that should start in ML rather than IRC?20:11
hub_capif we didnt cover it in a summit, lets hash it out together20:11
hub_capkevinconway: i think its fair to say if youre writing a email, send it to the list20:12
hub_capbut you can always say things in irc and we can say20:12
hub_caphey, this seems like we shoudl get input from people who arent around right now20:12
hub_capand send out thoughts to the ML20:12
kevinconwaygotcha20:12
hub_capmy rule of thumb20:12
hub_capif you think it cant be solved in ~1 hr20:12
vipulYea, thre have been several discussions in the past few weeks like that.. that i've missed20:12
hub_capyes me too vipul20:12
cp16net#agree20:13
hub_capand the more i travel lol the less i see :)20:13
grapexIt also is easier to start a thread of communication on the ML than on the wiki20:13
cp16netor gists20:13
hub_capya wiki is terible for conversation20:13
grapexcp16net: agreed20:13
hub_capgists are great to add in to a ML20:13
kevinconwayyeah, i'm really not liking the gists thing20:13
cp16nettrue20:13
hub_capcuz u can fork them and say "this is what im thinking"20:13
kevinconwaynone of them fit in the text box and i have to raw view them20:13
hub_capbut lets not use them as _the_ method of comm20:13
hub_capshow examples there so to speak20:13
cp16netyea code20:14
hub_capweve been saying this for a long time "we need to use the ML more"20:14
hub_capnow that its not rax and hp20:14
hub_capits time20:14
vipullet's finally do it?20:14
hub_cap:)20:14
hub_capyes vipul and i have probably had this conversation 20+ times20:14
vipulwhat about the 'die part'20:14
hub_capits like vote ore die20:14
hub_capif you dont use the ML puffy will come to your house and scream at you20:14
vipul:)20:14
SlickNikheh20:15
grapexDo I need to add an action that if people don't use the ML there will be... consequences?20:15
hub_capor p diddy or whatever his name is20:15
hub_cap"dire consequences" ;) jk20:15
grapexOk, ready to move on?20:15
hub_capactually there are consequences20:15
hub_capone more point20:15
hub_capthe consequences of "you will have to re-explain this 900 times"20:15
grapexThe consequences is we never settle the debate.20:15
hub_capto 900 different people20:15
grapexhub_cap: That too20:15
hub_capyup grapex20:15
SlickNikthat's a horrible consequence.20:15
hub_capsame vain really..20:15
hub_capeveryone will say something else and itll be hard to settle things20:16
hub_capso hip hip horray for the ML!20:16
hub_capmake a smart inbox for [trove]|[TrOvE]20:16
hub_capcuz u know kevinconway si gonna do that ;)20:16
datsun180bwould we create an ouroboros by declaring on the ML that we're supposed to be using the ML20:16
* cp16net starts typing email to the list....20:17
grapexdatsun180b: That's perfect20:17
hub_capyes cp16net's config stuff is also great for the ML20:17
cp16netyup20:17
hub_caplol @ datsun180b's comment20:17
*** sarob has quit IRC20:17
hub_capok horse beat20:17
hub_capto death20:17
grapexAlright20:17
grapex#topic voting out of band20:17
*** openstack changes topic to "voting out of band (Meeting topic: trove)"20:17
*** sarob has joined #openstack-meeting-alt20:18
grapexhub_cap: Is this about your recent experiment?20:18
hub_capyes it is20:18
hub_caphow do yall think it went? its kinda odd20:18
vipulweird20:18
dmakogon_hub_cap: what's this topic about ??20:18
hub_capbut it was suggested by -infra guys20:18
cp16netyeah but it worked out20:18
hub_capwe recently voted to log the channel communication dmakogon_20:18
SlickNikI think it was okay.20:18
cp16netand its on record now20:18
hub_capby pushing a review to gerrit20:19
dmakogon_aaa20:19
hub_capand then +1'ing it20:19
cp16neti dont understand why the doc had to be merged in tho...20:19
hub_capcp16net: formal record20:19
hub_capwe can go back and see the vote20:19
vipuli could see it clutter commit history20:19
hub_capgerrit holds that shiz forever20:19
vipulif we do this often that is20:19
hub_capyes vipul it would if we do it a ton20:19
SlickNikonly issue is git logs show voting stuff now.20:19
hub_cap#link https://github.com/openstack/trove/commit/15b706e2e0c37c2fa18e10c140d876c54c65fef420:19
hub_capim ok w that20:20
hub_capgit is a history20:20
cp16netthere shouldnt be a reason to do something like that out of band REALLY tho...20:20
hub_capits up to us to fill in what that history is20:20
kevinconwaydo we have by-laws that describe if and when we can call for a revote on a topic?20:20
hub_capnope20:20
kevinconwayand is it pure majority or some other rule?20:20
hub_capits very grey20:20
hub_capits what we want as a community (trove)20:20
SlickNikCan we have the formal records in the trove-integration repo?20:20
hub_capSlickNik: assuming trove-integration stays around forever, yes ;)20:21
grapexSlickNik: Good idea20:21
datsun180bthat's what i was going to bring up, that repo's longevity20:21
hub_capwe are teh only project that requires a "extra" noncode repo20:21
hub_capbut lets not get into that now :D20:21
hub_capi think for doc related stuff we can use database-api20:21
*** jasonb365 has joined #openstack-meeting-alt20:21
hub_capand honestly20:21
grapexI know the infra team uses it but I bet at some point someone will join the project and object to having a ton of text files int he votes directory.20:21
hub_capsome of this will be solved w the ML20:21
kevinconwayso can anyone call a vote for trove?20:21
hub_capgrapex: they dont really... it was a experiment20:22
kevinconwayhow do we make sure everyone gets a chance to vote? ML?20:22
hub_capkevinconway: sure why not20:22
hub_capbut remember this is for something specific that is not needed to be voted on in a meeting20:22
*** sarob has quit IRC20:22
hub_capor something the ML cant solve20:22
kevinconwayso what about spec/designs?20:22
hub_capspec/design i think is ML20:22
hub_capunless we have a total split and it dies on the ML20:22
hub_capthen its kinda up to core to decide20:22
kevinconwayright, i meant as more of a feedback type system20:23
hub_capsure i thin kthats faire20:23
hub_cap*Fair20:23
hub_capbut again, voiceing on the ML will help this20:23
hub_capespecialy if we are using the ML to talk design20:23
vipulthose things could also be voted on in meetings20:23
vipulassuming you've had good enough conversation on ML20:23
vipulthe vote would be quick20:24
grapexvipul: Good point20:24
hub_capyes thats a good point20:24
kevinconwaythe votes work just like code reviews though right? core has final decision.20:24
grapexI think this is a neat idea, but long term I think the artifacts might be too awkard.20:24
kevinconwaykeep out weird one off votes.20:24
hub_caponce we are all voting it might be mo-bettah20:24
hub_caperrrrrr20:25
SlickNikI'm thinking +1, or −1 for everyone. Unless we need to break a tie.20:25
hub_caponce we are all reading the ml voting will be mo-bettah20:25
hub_capSlickNik: thats the job of ptl20:25
hub_capand of core in general20:25
hub_capto me its, core first, if core is split, ptl makes a hard decision20:25
grapexAgreed, the fact core votes count more won't matter if we're fair. If this is for odd one-offs that won't be an issue.20:25
hub_cap^ ^ for a tie20:25
kevinconwaydo we need a set timeout for voting?20:25
kevinconwayor when do we declare voting done?20:26
hub_capkevinconway: i think we can set a majority #20:26
hub_capif it gets X votes in teh pos/neg its done20:26
SlickNikhub_cap: yup, sounds good20:26
hub_capbut really20:26
hub_capi think the ML is gonna help deal w this20:26
hub_capso lets focus a bit less on this now and try the ML20:26
hub_capand i agree w vipul that it will sort itself out20:26
hub_capbut we NEEEEEED to do our homework20:26
hub_capdont come to a meeting not being up to speed on your mail20:27
hub_capif you are not reading the trove ML things, you arent participating20:27
hub_capthen its the same as where we were in teh past :)20:27
hub_capitll be kinda bumpy in the beginning... just set a special tag / smart inbox whatever for trove20:27
hub_capand make sure u stay up on them if u care about the direction of trove ;)20:28
hub_cap#done20:28
grapexOk.20:28
grapex#topic capabilities (example, mysql+redis, under same api server, one having volumes and one not)20:28
*** openstack changes topic to "capabilities (example, mysql+redis, under same api server, one having volumes and one not) (Meeting topic: trove)"20:28
hub_capok i put this20:28
hub_capand i think its a GREAT ML discussion so i may just punt it to the ML20:29
hub_capbut to let everyone udnerstand20:29
hub_capnot every service will have the same capabilities (such as maybe we dont want floating ips for a particular service)20:29
hub_capso we need a way to say "this service has these", or at least i think we do20:29
hub_capand a way to config the services so they are, and can be, different20:29
hub_capmaybe we dont need a way to tell a customer how its different20:30
* grapex just realized we could solve the ML problem by putting all topics on the mailing list and ending the meeting early.20:30
hub_cap#endmeeting20:30
vipullol20:30
yogeshi remember sometime back we talked about this being handled through service extensions20:30
hub_capgood thing i cant do that ;)20:30
imsplitbit:)20:30
datsun180byeah, good thing20:30
vipulservice_type based config?20:30
hub_capyogesh: yes theres was talk about that20:30
hub_capvipul: kinda... ya20:30
kevinconwayhub_cap: grapex: a pre-meeting ML of the agenda might not be a bad idea either. 24hrs ahead?20:30
david-lylehub_cap, as requested, I added a blueprint for this particular item https://blueprints.launchpad.net/trove/+spec/capabilities20:30
kevinconwayoff topic. sorry.20:31
hub_capmaybe we mod the config to do [service_type]\nthing=value....20:31
grapexhub_cap: Are you suggesting we make the values of certain capabilities traditionally in the conf files available via an API or something?20:31
hub_capthank you david-lyle20:31
hub_capohhhhhh yes yes, so things like horizon do need this exposed20:31
hub_capso they know how to craft the ui20:31
yogeshwould there be a master set of capabilities...?20:31
hub_capi knew there was a reason for that, david can you do a #link ....20:31
vipulthat's a bit different from service_type based config though..20:31
hub_capyogesh: possibly? i dont think its out of the question to have a default list if you dont have that explicitly defined in the service_type20:32
david-lyleand dug up a past mailing list thread regarding extensions and capabilities in general http://lists.openstack.org/pipermail/openstack-dev/2013-May/008436.html20:32
vipulyou could solve it by requiring that you run separate config-specific deployment of a component (like nova-compute or something)20:32
hub_capdavid-lyle: when putting links on the meeting start a new line with #link http....20:32
hub_capso it shows up on the meeting logs fancy style20:32
hub_capcan u #link the BP and the ML20:32
kevinconway#info you can #link things20:33
david-lyle#link https://blueprints.launchpad.net/trove/+spec/capabilities20:33
SlickNikYou could have a system where if a [service_type] \n thing=value is defined, we use that.20:33
hub_capperfect!!!! (nice kevinconway )20:33
datsun180b#info you can #info things too20:33
hub_cap#undo20:33
hub_cap:P20:33
SlickNikIf not we fallback to the [default]\n thing=value20:33
kevinconway#info #agreed20:33
datsun180bcouldn't resist20:33
hub_capyes i think so SlickNik20:33
david-lyle#link http://lists.openstack.org/pipermail/openstack-dev/2013-May/008436.html20:33
hub_capthx david-lyle20:33
david-lylenp20:33
hub_capit would also break up the config in general20:33
hub_capi fear itll get hairy if u have 6 services running and dont split them up20:34
hub_capthere are going to be things that have NO reason to be in [DEFAULT]20:34
SlickNikSo we would maintain backwards compat with existing configs as well.20:34
hub_capredthrux: #agreed?20:34
hub_capSlickNik: yes thatll be the default effectively..20:34
redthrux#agreed20:35
hub_capthen maybe custoomize it with [mysql]volume_support=False20:35
vipulevery lookup of a cfg will require passing looking up the service_type?20:35
hub_capi did somethign on cinder that did this20:35
hub_capfor multi backends20:35
hub_capit first checked the service_type and then falldeded back to default20:35
cp16netparsing that wont be very hard20:36
hub_caplet me find20:36
hub_capit was for multi backends20:36
grapexWould it change the code so that rather than referencing a single config object, it would grab a collection of config objects using the service_type as a key and then pass that around via method arguments?20:36
hub_capehh cant find it right now20:36
hub_capcfg.service_type.blah is how it works grapex20:36
hub_capif its in a [different] area it would be cfg.different.some_value20:37
grapexhub_cap: Ok, the reason I ask is that "volume_support" could be in a general Trove code path20:37
hub_cap#link https://github.com/openstack/cinder/blob/master/cinder/volume/configuration.py20:37
grapexSo we'd probably want to find it via "configs = cfg[service_type]\n configs.some_value"20:37
hub_capgrapex: this code first checks for cfg.service_type.volume_support, if its not ther it asks for cfg.volume_support20:38
grapexhub_cap: I see. I guess my point is the Trove code path to provision a server and volume may not normally care about the service type. I guess all I'm saying is we use a dictionary key instead of an attribute.20:38
hub_capif we dont put a particular [service_type] in it, it wont care20:39
hub_capitll be up to the configuror of the system20:39
grapexhub_cap: This is getting into the weeds, we'll figure it out. :)20:39
SlickNikgrapex: I think you'd still be able to get the default values if you don't specify the service type.20:39
hub_capyes20:39
hub_capya we are 40 in and likely need to move on20:40
SlickNikSounds god.20:40
SlickNikgood*20:40
hub_cap#info defaults + [service_type] values are a good thing20:40
hub_capWOO my legs r shaking ive almost downed a quad americano from a little coffee shop across the street from Cal20:41
grapex#topic decision on servicetype/flavor in trove (yet again :-)), https://gist.github.com/mehrayogesh/1dfac0b4ffaf97fb885b (yogesh)20:41
*** openstack changes topic to "decision on servicetype/flavor in trove (yet again :-)), https://gist.github.com/mehrayogesh/1dfac0b4ffaf97fb885b (yogesh) (Meeting topic: trove)"20:41
yogeshso there are couple options...per gist20:41
hub_caplongest topic name. evar.20:41
grapexhub_cap: Copy and paste fail on my part.20:42
hub_cap:P20:42
yogesh:-)20:42
yogeshmaintaining the nova flavors from within trove api or not, thats the main difference20:42
grapexIt seems like the moment we have extra Trove info for flavors, we have to maintain them in the database.20:43
grapexSo there's no other option. Unless I'm missing something?20:43
hub_capi think he means creating/destroying from trove, correct yogesh20:43
hub_cap?20:43
SlickNikWasn't there some way of maintaining metadata as part of the flavor in nova.20:43
vipulWhat i see is we introduce a 'registration' API20:43
SlickNik?20:43
hub_capyes i do not want to add/delete from trove. register is a good word for the functionality vipul20:44
hub_capi want to "add" to trove20:44
hub_capbut barf if the flavor specified is not in nova20:44
yogeshare we taling about option 220:44
yogeshflavor has to be there in nova, for option 2 to work20:45
hub_cap#link https://gist.github.com/mehrayogesh/1dfac0b4ffaf97fb885b20:45
hub_capyogesh: nice gist. perfect for the mailing list (future, not this one... :) )20:45
yogeshthanks hub_cap20:45
yogeshsure20:45
hub_capogeez.. deregister is perfect for http PATCH20:46
* hub_cap jumps on PATCH soapbox20:46
hub_capjk20:46
hub_capi think option 2 makes more sense20:46
*** venkatesh has joined #openstack-meeting-alt20:46
hub_capwe may not be able to add flavors to nova even20:46
grapexhub_cap: Agreed.20:46
yogeshyeah20:47
grapexOk. Moving on...20:47
grapex#topic Configuration API update20:47
yogeshso, option 2 is decided...thanks20:47
*** openstack changes topic to "Configuration API update (Meeting topic: trove)"20:47
SlickNikI prefer approach 2 as well20:47
hub_capGO GO GO cp16net20:47
cp16netjoy20:47
dmakogon_cp16net: gist looks good20:47
hub_capis amcrn around? poop i guess not hes not tab completing20:47
cp16netyeah so i compiled a list of all th api calls20:48
cp16net#link https://gist.github.com/cp16net/670459020:48
hub_capfor the record, not having to do w/ this20:48
* cp16net is in the process of putting this in ML20:48
cp16net:-P20:48
hub_cappublic gists plz (thx cp16net !!!!)20:48
dmakogon_https://gist.github.com/cp16net/670459020:48
hub_capthere is no reason for private gists...20:48
yogeshsure20:49
cp16nethmm its public20:49
hub_capcp16net: u KNOW im gonna be all over PATCH20:49
hub_capcp16net: slow your roll... i thanked u above20:49
hub_cap;)20:49
dmakogon_what about making Configurations API being a part of Clustering API20:49
cp16netbut the main thing is making everyone aware of what is happening20:49
cp16netthe PUT could be changed to PATCH but its still relativley new20:50
dmakogon_cuz we have no ability to pass additional parameters to group of nodes in cluster20:50
hub_capdmakogon_: there should be a way to have cluster based configurations but it should be its own api20:50
hub_capclusteing will have to use configurations20:50
cp16neti've thought alot about using PATCH and i am not sold on it in at least this rev of the API20:50
dmakogon_hub_cap: there could be an overlaps20:50
kevinconwayi'd say don't even bother with PATCH until we can be sure it works on different clients20:50
hub_cappssh. put it on the ML20:50
dmakogon_ok20:51
hub_capdmakogon_: lets make sure we do it so there arent.. configuratiosn are not unique to clusters20:51
cp16netyeah thats where this is headed today.... to the ML!20:51
cp16net:-)20:51
imsplitbithub_cap: +120:51
hub_capdmakogon_: the "pssh" was to cp16net and his "PATCH is new" comment20:51
grapexHurray for the ML!20:51
dmakogon_aaa20:51
grapexOk, moving on20:51
cp16netlets do20:51
grapex#topic Configuration + service type and versions20:51
*** openstack changes topic to "Configuration + service type and versions (Meeting topic: trove)"20:51
grapexAgh20:51
hub_capkevinconway: /me doesnt care about someone building a rest api in their browser ;)20:51
imsplitbit:)20:51
cp16netalright20:51
hub_capwow nice grapex20:51
hub_capcopy pasta fail #220:52
hub_cap:P20:52
dmakogon_hub_cap: that is why i'm wondering firstly adding Configurations to CLusteing and then re-use it in Conf.API20:52
hub_capcuz clustering doesnt exist20:52
cp16netwe good...20:52
grapexcp16net: Ok.20:52
hub_capya i guess you have to start over again cp16net20:52
cp16netso i notcied there was overlap on the configuration and some of the service type stuff20:52
grapex#topic MySQL HA20:52
*** openstack changes topic to "MySQL HA (Meeting topic: trove)"20:52
hub_capoh this is different! ML topic again? amcrn has input on thsi20:53
hub_cap*this20:53
hub_capmy bad for copy pasta remark grapex !!!! i didnt notice the subtle differences ;)20:53
cp16netarg...20:53
grapexhub_cap: Me neither. I thought I'd copied it in twice it was so similar.20:53
hub_capkwarg? cp16net20:53
grapexWhich ironically means I was paying more attention than I thought.20:53
cp16netwell amcrn isnt here20:53
hub_capya cp16net MAAAAAAAILING LIST20:53
* hub_cap harps20:53
cp16netlol20:53
grapexAction item: Move all topics to ML20:53
dmakogon_lol20:54
hub_capamcrn is amazing at email fwiw20:54
cp16netso then i will say whats the point of these meetings then?20:54
hub_capyou will get some great topics20:54
hub_captouch base w/ the week on the ML20:54
grapexOk20:54
hub_caphelp make dscsions that are droning on in ML format20:54
grapex#topic Service Registration using conf file20:54
*** openstack changes topic to "Service Registration using conf file (Meeting topic: trove)"20:54
hub_capvote20:54
hub_capthings like that20:54
hub_capok someone splain this to me20:54
grapex#link https://review.openstack.org/#/c/41055/20:54
grapexThis was the last thing on the agenda20:54
vipulhub_cap: prolly just needs your approval20:55
yogeshso, on service registry, do we still want to keep it in code..20:55
hub_capoh ok ok20:55
yogesh:-)20:55
hub_capim ok w/ adding "additinoal services" thru a config file20:55
yogeshall moving into the conf will make it monolithic...20:56
dmakogon_+120:56
hub_capbut do we need to kill it alltogether?20:56
hub_capwill we have special implz for these?20:56
hub_capas in, do we need a user to be able to swap out the mysql impl20:56
hub_capor just add the cough cough vertica impl?20:56
yogeshlol20:56
yogeshservice registry seems more fitting into the conf20:57
hub_capif its just the latter lets make it extensible enough to _add_ out of scope services, but not make every installation config the basic ones20:57
vipulI thnk the main thing is how do we allow a single package / config of guest agent to be dynamic20:57
hub_capim not sure this is the answer to taht question vipul20:57
vipulso that the right code gets executed based on the service_type20:57
*** IlyaE has quit IRC20:57
hub_caphell who knows if service_registry doesnt go away as we amke this a smarter service20:57
vipulsure, that could be the case20:58
kevinconwayyou could run one guest agent for every possible db on your guest20:58
hub_capit was a way to "add" services quick-n-dirty20:58
hub_caplol kevinconway20:58
hub_cap26 guests, 1 responds20:58
hub_capMINE MINE MIEN MIEENE MINE20:58
* hub_cap thinks of teh gulls in that one movie20:58
vipulso either we need a way to load in Guest impl that's not already in the pre-defined list20:58
hub_cap#link http://www.mannahattamamma.com/Nemo-seagulls%5B1%5D.jpg20:58
vipulor need a way to make the registry be much more flexible20:59
hub_capvipul: im totally cool w/ that20:59
hub_capmake it additive in teh beginning at least20:59
hub_capas opposed to _all_ in the config20:59
vipulso just don't remove what's there..20:59
hub_capyou could even have a service_type_vertica=bla.impl20:59
hub_capand say "if not in service_registry" conf.get("service_type_%s"%service_type)21:00
*** rnirmal has quit IRC21:00
hub_capsimple enough21:00
yogeshthe thought was to make the design more monolithic..21:00
hub_caphow does this doe that?21:00
yogeshand have all at one place..21:00
*** rnirmal has joined #openstack-meeting-alt21:00
hub_capthe goal of this is to be able to add one off services21:00
hub_capright?21:00
hub_capnot to move somethign from one place (in code) to another place (in config)21:01
yogeshyeah thats true21:01
hub_capi dont think youre solving anythign by just moving code to config21:01
*** akuznetsov has quit IRC21:01
hub_capits just changing the monolitic location21:01
*** datsun180b has left #openstack-meeting-alt21:01
hub_capcrap we are over21:01
hub_capwe need to end21:01
yogesh:-)21:01
*** datsun180b has joined #openstack-meeting-alt21:01
hub_capwe need to be good openstackers21:01
vipultrovers21:01
grapexhub_cap: lol21:01
yogeshok, let us have it additive..21:01
hub_cap+1 yogesh21:01
grapexOk21:01
hub_capitll make me happier!21:01
grapex#endmeeting21:01
*** openstack changes topic to "OpenStack meetings (alternate)"21:02
hub_capcall it grapex21:02
openstackMeeting ended Wed Sep 25 21:01:59 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/trove/2013/trove.2013-09-25-20.03.html21:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/trove/2013/trove.2013-09-25-20.03.txt21:02
openstackLog:            http://eavesdrop.openstack.org/meetings/trove/2013/trove.2013-09-25-20.03.log.html21:02
*** imsplitbit has left #openstack-meeting-alt21:02
SlickNikThanks grapex!21:02
*** SlickNik has left #openstack-meeting-alt21:02
*** NehaV has left #openstack-meeting-alt21:03
*** pdmars has quit IRC21:04
*** grapex has quit IRC21:05
*** julim has quit IRC21:09
*** eankutse has quit IRC21:13
*** eankutse has joined #openstack-meeting-alt21:15
*** dmakogon_ has quit IRC21:15
*** lblanchard has quit IRC21:21
*** malini_afk is now known as malini21:26
*** jasonb365 has quit IRC21:27
*** sarob has joined #openstack-meeting-alt21:28
*** RajeshMohan has quit IRC21:31
*** RajeshMohan has joined #openstack-meeting-alt21:32
*** dukhlov_ has quit IRC21:33
*** sarob has quit IRC21:33
*** malini is now known as malini_afk21:39
*** robertmyers has quit IRC21:44
*** isviridov_ has quit IRC21:45
*** esker has joined #openstack-meeting-alt21:47
*** malini_afk is now known as malini21:47
*** vipul is now known as vipul-away21:47
*** vipul-away is now known as vipul21:47
*** jasonb365 has joined #openstack-meeting-alt21:49
*** dmakogon_ has joined #openstack-meeting-alt21:49
*** eankutse has quit IRC21:51
*** boris-42 has quit IRC21:55
*** eankutse has joined #openstack-meeting-alt21:56
*** sacharya has quit IRC21:57
*** IlyaE has joined #openstack-meeting-alt21:57
*** tanisdl has quit IRC21:58
*** jmaron has quit IRC21:58
*** tanisdl has joined #openstack-meeting-alt22:00
*** tanisdl has quit IRC22:01
*** tanisdl has joined #openstack-meeting-alt22:03
*** datsun180b has quit IRC22:08
*** venkatesh has quit IRC22:10
*** kebray has quit IRC22:13
*** betsy has quit IRC22:14
*** KennethWilke has quit IRC22:16
*** jcru has quit IRC22:20
*** eankutse has quit IRC22:20
*** jasonb365 has quit IRC22:28
*** jmaron has joined #openstack-meeting-alt22:30
*** jmaron has quit IRC22:35
*** dmakogon_ has quit IRC22:38
*** dhellmann is now known as dhellmann_22:42
*** sarob has joined #openstack-meeting-alt22:43
*** zane has quit IRC22:43
*** sarob has quit IRC22:55
*** IlyaE has quit IRC22:56
*** markwash has quit IRC23:14
*** amytron has quit IRC23:15
*** jmontemayor has quit IRC23:17
*** noslzzp has quit IRC23:18
*** noslzzp has joined #openstack-meeting-alt23:20
*** jasonb365 has joined #openstack-meeting-alt23:22
*** boris-42 has joined #openstack-meeting-alt23:26
*** jasonb365 has quit IRC23:26
*** julim has joined #openstack-meeting-alt23:27
*** jmaron has joined #openstack-meeting-alt23:32
*** jmaron has quit IRC23:37
*** malini is now known as malini_afk23:37
*** julim has quit IRC23:40
*** noslzzp has quit IRC23:47
*** noslzzp has joined #openstack-meeting-alt23:49
*** malini_afk is now known as malini23:56
*** sacharya has joined #openstack-meeting-alt23:56

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