Thursday, 2015-03-12

*** vishwanathj has quit IRC00:00
*** banix has joined #openstack-meeting-300:01
*** terrylhowe has left #openstack-meeting-300:01
*** Longgeek has joined #openstack-meeting-300:03
*** bpokorny_ has joined #openstack-meeting-300:04
*** annegentle has joined #openstack-meeting-300:06
*** Longgeek has quit IRC00:07
*** bpokorny has quit IRC00:07
*** sreshetn1 has joined #openstack-meeting-300:11
*** sreshetn1 has quit IRC00:16
*** Longgeek has joined #openstack-meeting-300:19
*** melwitt has quit IRC00:21
*** mwagner_lap has joined #openstack-meeting-300:21
*** Longgeek has quit IRC00:26
*** banix has quit IRC00:26
*** stendulker has joined #openstack-meeting-300:28
*** shwetaap has joined #openstack-meeting-300:30
*** annegentle has quit IRC00:31
*** shwetaap1 has joined #openstack-meeting-300:33
*** absubram has joined #openstack-meeting-300:33
*** shwetaap has quit IRC00:37
*** annegentle has joined #openstack-meeting-300:38
*** vishy has quit IRC00:41
*** vishy has joined #openstack-meeting-300:42
*** jgravel has left #openstack-meeting-300:43
*** annegentle has quit IRC00:48
*** annegentle has joined #openstack-meeting-300:49
*** nati_uen_ has quit IRC00:58
*** marun has joined #openstack-meeting-301:00
*** igordcard_ has quit IRC01:03
*** claired has quit IRC01:04
*** marun has quit IRC01:05
*** Yi has joined #openstack-meeting-301:06
*** annegentle has quit IRC01:08
*** SumitNaiksatam has quit IRC01:13
*** sigmavirus24 is now known as sigmavirus24_awa01:19
*** markvoelker has quit IRC01:27
*** ivar-laz_ has joined #openstack-meeting-301:27
*** markvoelker has joined #openstack-meeting-301:27
*** wojdev has quit IRC01:29
*** ivar-lazzaro has quit IRC01:30
*** ivar-laz_ has quit IRC01:32
*** markvoelker has quit IRC01:32
*** stanzgy_ has joined #openstack-meeting-301:36
*** stanzgy has joined #openstack-meeting-301:36
*** nati_ueno has joined #openstack-meeting-301:50
*** Longgeek has joined #openstack-meeting-301:52
*** Longgeek has quit IRC01:56
*** salv-orlando has quit IRC01:58
*** yamahata has quit IRC01:59
*** sreshetn1 has joined #openstack-meeting-302:00
*** armax has quit IRC02:01
*** sreshetn1 has quit IRC02:05
*** s3wong has quit IRC02:07
*** armax has joined #openstack-meeting-302:08
*** nelsnelson has joined #openstack-meeting-302:10
*** banix has joined #openstack-meeting-302:11
*** nati_ueno has quit IRC02:11
*** lhcheng has quit IRC02:12
*** jckasper has quit IRC02:13
*** bpokorny_ has quit IRC02:15
*** etoews_ has joined #openstack-meeting-302:22
*** ivar-lazzaro has joined #openstack-meeting-302:23
*** vishwanathj has joined #openstack-meeting-302:32
*** nelsnelson has quit IRC02:42
*** ivar-lazzaro has quit IRC02:43
*** david-lyle is now known as david-lyle_afk02:45
*** stendulker has quit IRC02:45
*** marun has joined #openstack-meeting-302:53
*** shwetaap1 has quit IRC02:55
*** fischerw has quit IRC02:56
*** fischerw has joined #openstack-meeting-302:56
*** shwetaap has joined #openstack-meeting-302:58
*** salv-orlando has joined #openstack-meeting-302:59
*** zz_jgrimm is now known as jgrimm03:03
*** nati_ueno has joined #openstack-meeting-303:09
*** dkehn has quit IRC03:10
*** salv-orlando has quit IRC03:10
*** nati_ueno has quit IRC03:11
*** Yi has quit IRC03:12
*** dkehn has joined #openstack-meeting-303:15
*** salv-orlando has joined #openstack-meeting-303:19
*** nelsnelson has joined #openstack-meeting-303:19
*** ivar-lazzaro has joined #openstack-meeting-303:19
*** SumitNaiksatam has joined #openstack-meeting-303:22
*** Yi has joined #openstack-meeting-303:22
*** salv-orlando has quit IRC03:23
*** Networkn3rd has joined #openstack-meeting-303:23
*** salv-orlando has joined #openstack-meeting-303:24
*** salv-orlando has quit IRC03:29
*** Yi has quit IRC03:33
*** Longgeek has joined #openstack-meeting-303:37
*** banix has quit IRC03:41
*** etoews_ has quit IRC03:41
*** etoews_ has joined #openstack-meeting-303:42
*** Yi has joined #openstack-meeting-303:44
*** etoews_ has quit IRC03:46
*** mattgriffin has joined #openstack-meeting-303:48
*** sreshetn1 has joined #openstack-meeting-303:48
*** nelsnelson has quit IRC03:51
*** sreshetn1 has quit IRC03:53
*** shwetaap1 has joined #openstack-meeting-303:55
*** shwetaap has quit IRC03:57
*** SridharRamaswamy has joined #openstack-meeting-304:00
*** Longgeek has quit IRC04:03
*** Yi has quit IRC04:09
*** sankarshan_away is now known as sankarshan04:10
*** shwetaap has joined #openstack-meeting-304:14
*** shwetaap1 has quit IRC04:17
*** jckasper has joined #openstack-meeting-304:17
*** amotoki has joined #openstack-meeting-304:22
*** devlaps has quit IRC04:25
*** ivar-lazzaro has quit IRC04:33
*** ivar-lazzaro has joined #openstack-meeting-304:34
*** SridharRamaswam1 has joined #openstack-meeting-304:36
*** masco has joined #openstack-meeting-304:37
*** SridharRamaswamy has quit IRC04:38
*** ivar-lazzaro has quit IRC04:39
*** killer_prince is now known as lazy_prince04:39
*** jckasper has quit IRC04:41
*** fischerw has quit IRC04:45
*** marun has quit IRC04:47
*** salv-orlando has joined #openstack-meeting-304:49
*** lazy_prince has quit IRC04:49
*** marun has joined #openstack-meeting-304:50
*** lazy_prince has joined #openstack-meeting-304:51
*** nelsnelson has joined #openstack-meeting-304:53
*** lazy_prince is now known as killer_prince04:53
*** killer_prince is now known as lazy_prince04:58
*** salv-orlando has quit IRC05:00
*** yamahata has joined #openstack-meeting-305:04
*** Poornima has joined #openstack-meeting-305:04
*** david-ly_ has joined #openstack-meeting-305:04
*** cbader02 has joined #openstack-meeting-305:04
*** aleksandr_null_ has joined #openstack-meeting-305:04
*** omnibus7 has joined #openstack-meeting-305:05
*** lazy_pri- has joined #openstack-meeting-305:05
*** kevinbenton_ has joined #openstack-meeting-305:05
*** asahlin has joined #openstack-meeting-305:06
*** devanand1 has joined #openstack-meeting-305:07
*** mestery_ has joined #openstack-meeting-305:07
*** SumitNaiksatam has quit IRC05:07
*** mestery has quit IRC05:08
*** lazy_prince has quit IRC05:09
*** asahlin_ has quit IRC05:09
*** lazy_pri- is now known as lazy_prince05:09
*** david-lyle_afk has quit IRC05:09
*** sreshetnyak has quit IRC05:09
*** beagles has quit IRC05:09
*** sreshetnyak has joined #openstack-meeting-305:09
*** mikal_ has joined #openstack-meeting-305:09
*** devananda has quit IRC05:09
*** aleksandr_null has quit IRC05:09
*** davidlenwell has quit IRC05:09
*** kevinbenton has quit IRC05:09
*** cbader has quit IRC05:09
*** mikal has quit IRC05:09
*** b3nt_pin has joined #openstack-meeting-305:10
*** b3nt_pin is now known as Guest2707405:10
*** absubram has quit IRC05:15
*** mattgriffin has quit IRC05:17
*** SridharRamaswam1 has quit IRC05:17
*** mattgriffin has joined #openstack-meeting-305:17
*** mattgriffin has quit IRC05:18
*** marun has quit IRC05:19
*** marun has joined #openstack-meeting-305:22
*** shwetaap has quit IRC05:23
*** stendulker has joined #openstack-meeting-305:23
*** markvoelker has joined #openstack-meeting-305:25
*** markvoelker has quit IRC05:30
*** reed has quit IRC05:30
*** sreshetn1 has joined #openstack-meeting-305:37
*** obondarev_ has joined #openstack-meeting-305:42
*** sreshetn1 has quit IRC05:42
*** obondarev has quit IRC05:42
*** marun has quit IRC05:42
*** nelsnelson has quit IRC05:44
*** Longgeek has joined #openstack-meeting-305:45
*** mattgriffin has joined #openstack-meeting-305:45
*** yamamoto has joined #openstack-meeting-305:47
*** wuhg has joined #openstack-meeting-305:56
*** mattgriffin has quit IRC06:01
*** mrmartin has joined #openstack-meeting-306:01
*** bknudson has quit IRC06:10
*** Longgeek has quit IRC06:18
*** markvoelker has joined #openstack-meeting-306:26
*** yamahata has quit IRC06:26
*** sreshetn1 has joined #openstack-meeting-306:30
*** markvoelker has quit IRC06:32
*** lazy_prince is now known as killer_prince06:35
*** killer_prince is now known as lazy_prince06:37
*** Piet has quit IRC06:55
*** mrunge has joined #openstack-meeting-307:02
*** armax has quit IRC07:06
*** pkoniszewski has joined #openstack-meeting-307:09
*** Yi has joined #openstack-meeting-307:10
*** Yi has quit IRC07:14
*** lazy_prince has quit IRC07:15
*** lazy_prince has joined #openstack-meeting-307:16
*** watanabe_isao has joined #openstack-meeting-307:17
*** stevemar has quit IRC07:22
*** jcoufal has joined #openstack-meeting-307:27
*** salv-orlando has joined #openstack-meeting-307:27
*** markvoelker has joined #openstack-meeting-307:28
*** sahid has joined #openstack-meeting-307:28
*** evgenyf has joined #openstack-meeting-307:32
*** lazy_prince has quit IRC07:33
*** markvoelker has quit IRC07:33
*** lazy_prince has joined #openstack-meeting-307:34
*** lazy_prince is now known as killer_prince07:35
*** salv-orlando has quit IRC07:35
*** sergef has joined #openstack-meeting-307:37
*** cbader02 has quit IRC07:38
*** rhagarty has quit IRC07:39
*** rhagarty_ has quit IRC07:39
*** salv-orlando has joined #openstack-meeting-307:39
*** etoews has quit IRC07:39
*** rhagarty_ has joined #openstack-meeting-307:39
*** rhagarty has joined #openstack-meeting-307:39
*** killer_prince is now known as lazy_prince07:39
*** cbader has joined #openstack-meeting-307:39
*** salv-orl_ has joined #openstack-meeting-307:42
*** salv-orlando has quit IRC07:43
*** salv-orl_ has quit IRC07:46
*** wojdev has joined #openstack-meeting-307:48
*** wojdev has quit IRC07:50
*** wojdev has joined #openstack-meeting-307:51
*** safchain has joined #openstack-meeting-307:51
*** lazy_prince has quit IRC07:52
*** lazy_prince has joined #openstack-meeting-307:53
*** lazy_prince is now known as killer_prince07:54
*** kozhukalov has joined #openstack-meeting-307:56
*** killer_prince is now known as lazy_prince07:57
*** scheuran has joined #openstack-meeting-307:59
*** jrist has quit IRC07:59
*** cbader has quit IRC07:59
*** rhagarty has quit IRC07:59
*** rhagarty_ has quit IRC08:00
*** rhagarty_ has joined #openstack-meeting-308:00
*** cbader has joined #openstack-meeting-308:00
*** jrist has joined #openstack-meeting-308:00
*** rhagarty has joined #openstack-meeting-308:00
*** salv-orlando has joined #openstack-meeting-308:01
*** Longgeek has joined #openstack-meeting-308:03
*** salv-orlando has quit IRC08:06
*** matrohon has joined #openstack-meeting-308:11
*** Longgeek has quit IRC08:12
*** zz_ttrifonov is now known as ttrifonov08:21
*** mrda is now known as mrda-away08:27
*** markvoelker has joined #openstack-meeting-308:29
*** megm has joined #openstack-meeting-308:29
*** megm_ has quit IRC08:30
*** watanabe_isao has quit IRC08:32
*** markvoelker has quit IRC08:34
*** salv-orlando has joined #openstack-meeting-308:34
*** doug-fish has quit IRC08:36
*** jschwarz has joined #openstack-meeting-308:40
*** sreshetn1 has quit IRC08:42
*** wojdev has quit IRC08:45
*** wojdev has joined #openstack-meeting-308:49
*** sreshetn1 has joined #openstack-meeting-308:57
*** JeanBriceCombebi has joined #openstack-meeting-308:57
*** sergef has quit IRC09:01
*** JeanBriceCombebi has quit IRC09:10
*** ttrifonov is now known as zz_ttrifonov09:14
*** lazy_prince is now known as killer_prince09:15
*** zz_ttrifonov is now known as ttrifonov09:15
*** sreshetn1 has quit IRC09:17
*** sergef has joined #openstack-meeting-309:21
*** yamamoto has quit IRC09:21
*** stanzgy_ has quit IRC09:26
*** stanzgy_ has joined #openstack-meeting-309:26
*** sreshetn1 has joined #openstack-meeting-309:29
*** markvoelker has joined #openstack-meeting-309:30
*** markvoelker has quit IRC09:35
*** wojdev has quit IRC09:35
*** rhagarty has quit IRC09:37
*** rhagarty_ has quit IRC09:37
*** cbader has quit IRC09:37
*** rhagarty has joined #openstack-meeting-309:38
*** rhagarty_ has joined #openstack-meeting-309:38
*** cbader has joined #openstack-meeting-309:38
*** sarob has quit IRC09:40
*** Guest27074 is now known as b3nt_pin09:41
*** sarob has joined #openstack-meeting-309:42
*** sarob has quit IRC09:47
*** yamamoto has joined #openstack-meeting-309:51
*** vgridnev has joined #openstack-meeting-309:52
*** Longgeek has joined #openstack-meeting-309:54
*** e0ne has joined #openstack-meeting-309:56
*** e0ne is now known as e0ne_09:56
*** JeanBriceCombebi has joined #openstack-meeting-310:00
*** e0ne_ has quit IRC10:05
*** zz_johnthetubagu is now known as johnthetubaguy10:07
*** killer_prince is now known as lazy_prince10:09
*** e0ne has joined #openstack-meeting-310:10
*** Longgeek has quit IRC10:14
*** salv-orl_ has joined #openstack-meeting-310:18
*** lazy_pri- has joined #openstack-meeting-310:18
*** lazy_prince has quit IRC10:18
*** lazy_pri- is now known as lazy_prince10:18
*** stanzgy has quit IRC10:19
*** stanzgy has joined #openstack-meeting-310:20
*** salv-orlando has quit IRC10:20
*** salv-orl_ has quit IRC10:22
*** lazy_pri- has joined #openstack-meeting-310:24
*** jtomasek has joined #openstack-meeting-310:25
*** lazy_prince has quit IRC10:26
*** lazy_pri- is now known as lazy_prince10:26
*** lazy_prince is now known as killer_prince10:27
*** markvoelker has joined #openstack-meeting-310:31
*** sreshetn1 has quit IRC10:32
*** killer_prince is now known as lazy_prince10:33
*** yamamoto has quit IRC10:35
*** markvoelker has quit IRC10:36
*** safchain has quit IRC10:43
*** sarob has joined #openstack-meeting-310:43
*** sarob has quit IRC10:49
*** stanzgy has quit IRC10:50
*** stanzgy_ has quit IRC10:51
*** lblanchard has joined #openstack-meeting-311:10
*** JeanBriceCombebi has quit IRC11:11
*** JeanBriceCombebi has joined #openstack-meeting-311:14
*** safchain has joined #openstack-meeting-311:19
*** markvoelker has joined #openstack-meeting-311:33
*** markvoelker has quit IRC11:37
*** lblanchard1 has joined #openstack-meeting-311:44
*** lblanchard has quit IRC11:44
*** scheuran_ has joined #openstack-meeting-311:46
*** scheuran has quit IRC11:49
*** isviridov_vction is now known as isviridov11:54
*** stendulker has quit IRC11:56
*** JeanBriceCombebi has quit IRC11:57
*** Yi has joined #openstack-meeting-311:57
*** Longgeek has joined #openstack-meeting-311:59
*** salv-orlando has joined #openstack-meeting-312:00
*** mwagner_lap has quit IRC12:04
*** masco has quit IRC12:05
*** salv-orlando has quit IRC12:08
*** baoli has joined #openstack-meeting-312:08
*** salv-orlando has joined #openstack-meeting-312:08
*** Poornima has quit IRC12:11
*** markvoelker has joined #openstack-meeting-312:15
*** marun has joined #openstack-meeting-312:17
*** Longgeek has quit IRC12:19
*** salv-orlando has quit IRC12:20
*** lblanchard1 has quit IRC12:23
*** lazy_prince is now known as killer_prince12:24
*** megm_ has joined #openstack-meeting-312:33
*** megm has quit IRC12:33
*** johnthetubaguy is now known as zz_johnthetubagu12:35
*** e0ne is now known as e0ne_12:35
*** Longgeek has joined #openstack-meeting-312:39
*** marun has quit IRC12:41
*** e0ne_ has quit IRC12:45
*** devanand1 has quit IRC12:49
*** elmiko has joined #openstack-meeting-312:49
*** devananda has joined #openstack-meeting-312:50
*** pavel_bondar has joined #openstack-meeting-312:51
*** mwagner_lap has joined #openstack-meeting-312:52
*** amotoki has quit IRC12:57
*** Yi_ has joined #openstack-meeting-313:00
*** jschwarz has quit IRC13:03
*** Yi has quit IRC13:04
*** mestery_ has quit IRC13:08
*** yamamoto has joined #openstack-meeting-313:13
*** sreshetn1 has joined #openstack-meeting-313:14
*** stevemar has joined #openstack-meeting-313:18
*** mestery has joined #openstack-meeting-313:20
*** Piet has joined #openstack-meeting-313:23
*** shwetaap has joined #openstack-meeting-313:23
*** Longgeek has quit IRC13:24
*** jtomasek has quit IRC13:25
*** jckasper has joined #openstack-meeting-313:25
*** bknudson has joined #openstack-meeting-313:26
*** peristeri has joined #openstack-meeting-313:27
*** lblanchard has joined #openstack-meeting-313:31
*** jtomasek has joined #openstack-meeting-313:33
*** annegentle has joined #openstack-meeting-313:37
*** Longgeek has joined #openstack-meeting-313:37
*** jtomasek has quit IRC13:38
*** Yi has joined #openstack-meeting-313:40
*** shwetaap1 has joined #openstack-meeting-313:42
*** masco has joined #openstack-meeting-313:43
*** JeanBriceCombebi has joined #openstack-meeting-313:44
*** e0ne has joined #openstack-meeting-313:44
*** weiting has joined #openstack-meeting-313:44
*** Yi_ has quit IRC13:44
*** shwetaap has quit IRC13:45
*** sarob has joined #openstack-meeting-313:48
*** sigmavirus24_awa is now known as sigmavirus2413:51
*** tidwellr has joined #openstack-meeting-313:51
*** jtomasek has joined #openstack-meeting-313:53
*** sarob has quit IRC13:53
*** tosky has joined #openstack-meeting-313:56
elmikohey13:57
*** huichun has joined #openstack-meeting-313:57
*** kchen has joined #openstack-meeting-314:00
elmiko#startmeeting Sahara14:00
openstackMeeting started Thu Mar 12 14:00:07 2015 UTC and is due to finish in 60 minutes.  The chair is elmiko. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: Sahara)"14:00
openstackThe meeting name has been set to 'sahara'14:00
*** pino|work has joined #openstack-meeting-314:00
*** baoli has quit IRC14:00
*** TravT has left #openstack-meeting-314:00
elmikohey saharans14:00
*** crobertsrh has joined #openstack-meeting-314:00
elmikoi'll give folks a few minutes to arrive and then we'll get rolling14:01
huichun^^14:01
*** Nikolay_St has joined #openstack-meeting-314:01
crobertsrhHello/14:01
kchenhello/14:02
Nikolay_Sto/14:02
*** baoli_ has joined #openstack-meeting-314:02
weitingO/14:02
*** huichun_ has joined #openstack-meeting-314:02
*** baoli_ has quit IRC14:02
*** thangp has joined #openstack-meeting-314:02
elmikook then14:03
elmiko#topic sahara@horizon status (crobertsrh, NikitaKonovalov)14:03
*** openstack changes topic to "sahara@horizon status (crobertsrh, NikitaKonovalov) (Meeting topic: Sahara)"14:03
crobertsrhAbout 11 items in the review queue.  Good progress though.  I think I've had 4 or 5 merge in the last week.14:03
sreshetn1o/14:03
elmiko#link https://etherpad.openstack.org/p/sahara-reviews-in-horizon14:03
crobertsrhCertainly need more eyes on the cluster and job guides14:03
elmikoyea, i highly recommend folks give the guides a run-through if you have the chance14:04
*** baoli_ has joined #openstack-meeting-314:04
NikitaKonovalovthe new event-log tab for cluster is also on review14:04
elmikocol14:05
elmikocool even =)14:05
NikitaKonovalovbut if you want to try it out, you need a sahara-client patched with this change https://review.openstack.org/#/c/159451/14:05
elmikogood to know14:05
crobertsrhI'm adding it to the etherpad of reviews14:06
*** egafford has joined #openstack-meeting-314:06
NikitaKonovalovand sahara patched with this one https://review.openstack.org/#/c/163812/14:06
NikitaKonovalov^^ is very minor thing so I hope we'll get it merged fast14:06
*** tidwellr has quit IRC14:06
*** nelsnelson has joined #openstack-meeting-314:06
*** nelsnelson has quit IRC14:07
*** Yi_ has joined #openstack-meeting-314:07
elmikoanything else from horizon land?14:07
crobertsrhNot that I can think of.14:07
*** yamamoto has quit IRC14:07
*** esikachev has joined #openstack-meeting-314:07
elmikook then, moving on14:08
*** mattfarina has joined #openstack-meeting-314:08
elmiko#topic News / updates14:08
*** openstack changes topic to "News / updates (Meeting topic: Sahara)"14:08
elmikofolks, please14:08
toskyhelped pushing two horizon/selenium tests; pending tempest test review to decouple testing from vanilla plugin14:09
sreshetn1i'm working on tempest client tests in sahara14:09
vgridnevi'm finished work with timeouts patches, work event-log bug-fixes14:10
*** qwebirc80517 has joined #openstack-meeting-314:10
egaffordWorking with sgotliv on the Spark shell job and generally getting him up to speed on Sahara dev.14:10
*** Yi has quit IRC14:10
Nikolay_Stuhm.. not sure that it's for this section, but yesterday I attend the LogWorkingGroup meeting. Looks like we are the first team who is implemented a spec for new logging.14:10
elmikoi've been doing reviews and working on a bug fix for the key manager usage with swift14:10
*** qwebirc80517 has quit IRC14:10
vgridnevalso, we are going to remove sahara.conf.sample, need review https://review.openstack.org/#/c/163779/14:10
elmikoNikolay_St: nice! i was going to cover action items next. we can talk more =)14:11
*** rprakash has joined #openstack-meeting-314:11
Nikolay_Stalso, try to figure our what wrong with saharaclient gate job of juno cycle14:12
*** amotoki has joined #openstack-meeting-314:12
*** tmckay has joined #openstack-meeting-314:12
tmckaynews updates still?14:14
elmikoyea14:14
tmckayOkay, I am working on the default-cli CR, it's got an exception for FPF and probably FF if necessary.  Reviews would be great (post link in a second)14:14
egaffordNikolay_St: If you're looking into that, I'd like to help.14:14
tmckayI need to add a README for context, and still working on polish but the essential thing is there14:14
huichun_tmckay: Trevor, hbase common lib is under review14:14
tmckay#link https://review.openstack.org/#/c/163649/14:14
huichun_tmckay: https://review.openstack.org/#/c/162657/14:14
*** thomasem_ has quit IRC14:14
*** krotscheck has quit IRC14:14
tmckayhuichun_, great!  Sorry I couldn't help resolve the oozie libpath issue, maybe during the freeze I can take a look14:14
elmikoany more news or updates?14:15
tmckayalso, job-type-endpoints has stalled a little bit.  Working on that, too.  We need agreement on the spec.14:15
elmikotmckay: is there a burning question or just details?14:15
tmckay#link https://review.openstack.org/#/c/157563/14:16
*** masco has quit IRC14:16
Nikolay_Stegafford: I appreciate your help. After two days investigation I only can say that it's not devstack fault. pure devstack installation is look ok.14:16
tmckayelmiko, spec is not merged yet, and the related client CR has some -1 because we were discussing ouput.14:16
elmikotmckay: ack14:16
elmikook, moving on14:16
tmckay#link https://review.openstack.org/#/c/161448/14:16
egaffordNikolay_St: I agree with your assessment. :)14:17
huichun_tmckay:hi Trevor, i am now have time to research that issue, will email you if any updates14:17
tmckayelmiko, I hope to spin through that stuff again today14:17
elmiko#topic Action items from the last meeting14:17
*** openstack changes topic to "Action items from the last meeting (Meeting topic: Sahara)"14:17
tmckayhuichun_, excellent, thank you.14:17
elmikoNikolay_St: do you want to brief us on the log meeting?14:17
Nikolay_Stelmiko: yeap14:17
*** krotscheck has joined #openstack-meeting-314:17
Nikolay_StI don't have much to say - look like community is busy before FF, so no active discussions on Logs.14:18
huichun_tmckay: if you have edp job related bp or bugs, you can assign it to me, we have finished the cdh integrtion tests, so we have lots of time now14:18
*** thomasem has joined #openstack-meeting-314:18
elmikoNikolay_St: ok, good to know14:19
Nikolay_StAt the next meeting I will present a short list of how we can improve logging. some notices about where we should|shouldn't have LOG entries14:19
Nikolay_Stsmthg like that14:19
*** yamamoto has joined #openstack-meeting-314:19
tmckayhuichun_, excellent.  Take a look through existing [EDP] bugs, and if you see something you would like to fix, just assign yourself (I think you have privilege)14:19
elmikoNikolay_St: great!14:19
elmikook, other action item was, Nikolay_St to investigate hacking checks for import groups14:19
*** qwebirc89060 has joined #openstack-meeting-314:19
huichun_ok14:19
Nikolay_Stthis guys expect that the more work started after 31march iirc14:20
Nikolay_Stelmiko: that's done14:20
elmikoNikolay_St: excellent!14:20
elmikothat's all for action items from last week14:20
Nikolay_St#link https://review.openstack.org/#/c/163021/14:20
tmckayhuichun_, oh, I will need help soon for default-templates.  I will need a sane default template set for each plugin14:20
elmiko#topic Open discussion14:20
*** openstack changes topic to "Open discussion (Meeting topic: Sahara)"14:20
Nikolay_St#link https://review.openstack.org/#/c/163123/14:21
tmckayhuichun_, the README will explain it (up soon).  Just JSON files, with some replacement fields14:21
elmikoNikolay_St: thanks14:21
tmckayhuichun_, so, if you can help me make a CDH set, that would be great14:21
kchentmckay: when you say default templates, do you mean the cluster or node group template?14:21
tmckayjust a generic CDH cluster that a user would like to launch "out of the box"14:21
*** qwebirc89060 has quit IRC14:21
huichun_tmckay: i have seen that, you just finish HDP plugin, right?14:21
tmckaykchen, yes, cluster and node group templates14:21
*** etoews has joined #openstack-meeting-314:22
tmckayhuichun_, oh, that was job types endpoint.  That's another issue :)14:22
huichun_tmckay: sorry, that's edp endpoint bp, does that bp need for every plugin?14:23
tmckaykchen, the idea is that you run the default templates CLI and it loads template sets distributed with Sahara into the database (with some config added by user) and then a user can run a cluster without the manual steps of adding templates themselves14:23
*** mrmartin has quit IRC14:23
tmckaykchen, aimed at ease of use and quick introduction to Sahara14:23
tmckayhuichun_, yes14:23
kchentmckay: it is be/default-templates, right?14:23
huichun_tmckay: ok, I will help on CDH set on default-template14:23
tmckayhuichun_, pretty easy, but I hadn't done the plugin CRs because the spec and main CR are not merged yet14:23
tmckaykchen, yes14:24
weitingtmckay, so the default template provide a minimal cluster to help the customer launch the cluster, right?14:24
kchenso it is only for CLI. Can we use it on Horizon?14:25
tmckayweiting, exactly14:25
toskyabout templates: I had to create cluster/node group templates for Tempest tests, and I noticed that, for cluster configuration, the parameters are like dfs_replication instead of dfs.replication like all the others14:25
egaffordtmckay: I can pitch in on any default templates that don't have coverage; let me know.14:26
tmckaykchen, well, the templates will be available from the UI once they are installed.  But the installation itself will be from a new (small) CLI14:26
toskyis it something that depends on CDH internal? Could it be changed in the plugin to have the same parameter as the other Hadoop flavors? Is it worth to file a bug/wishlist?14:26
tmckaytosky, yes, file a bug/wishlist and we can discuss on the bug14:27
tmckayegafford, thank you14:27
tmckaykchen, the idea is that a Sahara admin will install default templates for the desired plugins at Sahara installation time, and then will update them occasionally (when needs change, or a Sahara update, etc)14:28
tmckaykchen, they are special because they cannot be deleted or modified, except from the CLI.14:28
tmckaykchen, there is an "is_default" field that can only be set through the conductor API, not REST.14:28
*** masco has joined #openstack-meeting-314:29
*** mattfarina has quit IRC14:31
elmikoanyone have more topics for discussion?14:31
crobertsrhNothing from me14:32
Nikolay_StI have14:32
Nikolay_Stjust a request14:32
kchentmckay: so "is_default" means the template cannot be changed by REST, right?14:32
Nikolay_Stas far as we have a spec for logging style, please, follow it :)14:33
tmckaykchen, yes14:33
kchentmckay: i see, thanks14:33
elmikoNikolay_St: can you link the logging spec again please14:33
tmckayNikolay_St, ack, I was in a hurry and just typed what came into my head :)  I will change it.14:33
Nikolay_Stfor example, don't use crazy string formatting14:33
Nikolay_Sttmckay: ok14:33
Nikolay_St#link: https://github.com/openstack/sahara-specs/blob/master/specs/kilo/sahara-log-guidelines.rst14:34
elmikoNikolay_St: thanks14:34
tmckay#link https://review.openstack.org/#/c/162209/14:34
tmckaykchen, ^^ default template spec14:35
tmckaykchen, needs to be adjust slightly (will do that today) based on work14:35
*** sankarshan is now known as sankarshan_away14:35
*** marun has joined #openstack-meeting-314:35
*** etoews_ has joined #openstack-meeting-314:35
kchentmckay: ok. I will check that14:37
*** JeanBriceCombebi has quit IRC14:37
*** JeanBriceCombebi has joined #openstack-meeting-314:37
kchenNikolay_St: is it for bp/new-style-logging?14:39
Nikolay_Stkchen: yeap14:39
*** seizadi has joined #openstack-meeting-314:40
*** stendulker has joined #openstack-meeting-314:41
kchenNikolay_St: I saw you already have a patch https://review.openstack.org/#/c/154037/, so what need we do other than reviewing it?14:41
Nikolay_Stkchen: in the spec we have an instructions about what log levels to use in general. also, we decide to use pep3101 for log formats.14:44
Nikolay_St#link https://www.python.org/dev/peps/pep-3101/14:44
kchenok14:45
Nikolay_Stkchen: we try to make it as simple as possible14:47
*** sreshetn1 has quit IRC14:47
*** sarob has joined #openstack-meeting-314:48
*** esikachev has left #openstack-meeting-314:49
*** carl_baldwin has joined #openstack-meeting-314:49
elmikoanything else?14:50
Nikolay_Stnot from my side14:51
elmikook then, thank you to everyone for attending!14:52
egaffordThanks elmiko!14:53
elmiko#endmeeting14:53
*** openstack changes topic to "OpenStack Meetings"14:53
openstackMeeting ended Thu Mar 12 14:53:03 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:53
openstackMinutes:        http://eavesdrop.openstack.org/meetings/sahara/2015/sahara.2015-03-12-14.00.html14:53
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/sahara/2015/sahara.2015-03-12-14.00.txt14:53
openstackLog:            http://eavesdrop.openstack.org/meetings/sahara/2015/sahara.2015-03-12-14.00.log.html14:53
Nikolay_Stelmiko: thanks14:53
kchenthanks14:53
Nikolay_Stbye, guys!14:53
*** Nikolay_St has quit IRC14:53
*** sarob has quit IRC14:54
*** amuller has joined #openstack-meeting-314:55
*** etoews has quit IRC14:55
*** etoews_ is now known as etoews14:55
*** Longgeek has quit IRC14:55
*** dtroyer has joined #openstack-meeting-314:56
*** tmckay has left #openstack-meeting-314:58
*** kchen has quit IRC14:58
carl_baldwinhi14:59
*** mlavalle has joined #openstack-meeting-314:59
pavel_bondarhi14:59
mlavallehi15:00
*** pc_m has joined #openstack-meeting-315:00
pc_mhi15:00
*** baoli_ has quit IRC15:00
*** jschwarz has joined #openstack-meeting-315:00
*** mattfarina has joined #openstack-meeting-315:00
*** e0ne is now known as e0ne_15:01
haleybhi15:01
*** kaufer has joined #openstack-meeting-315:01
yamamotohi15:01
carl_baldwinpavel_bondar: mlavalle: pc_m: haleyb: hi15:01
carl_baldwin#startmeeting neutron_l315:01
openstackMeeting started Thu Mar 12 15:01:20 2015 UTC and is due to finish in 60 minutes.  The chair is carl_baldwin. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: neutron_l3)"15:01
carl_baldwin#topic Announcements15:01
openstackThe meeting name has been set to 'neutron_l3'15:01
*** openstack changes topic to "Announcements (Meeting topic: neutron_l3)"15:01
*** pino|work has left #openstack-meeting-315:01
carl_baldwinOne more week until K3.  I can’t believe it myself.15:01
carl_baldwin#link https://wiki.openstack.org/wiki/Meetings/Neutron-L3-Subteam15:01
carl_baldwin#link https://wiki.openstack.org/wiki/Kilo_Release_Schedule15:02
carl_baldwinAny other announcements?15:02
*** saggi- has joined #openstack-meeting-315:03
carl_baldwinI think we’ll have a short meeting today.15:04
carl_baldwin#topic Bugs15:04
*** openstack changes topic to "Bugs (Meeting topic: neutron_l3)"15:04
carl_baldwinAny bugs we need to be aware of?15:04
pc_mI had questions on https://bugs.launchpad.net/neutron/+bug/143107715:04
openstackLaunchpad bug 1431077 in neutron "TRACE: attribute error when trying to fetch the router.snat_namespace.name" [Undecided,New]15:04
pc_mWhen _process_added_router() called for DVR , should there be a namespace set up already?15:05
*** emw has joined #openstack-meeting-315:05
* carl_baldwin looks at code...15:05
*** tosky has left #openstack-meeting-315:06
*** e0ne_ has quit IRC15:06
carl_baldwinAt the point _process_added_router is called, there may not be a namespace.  It is part of _router_added to create the namespace.15:07
carl_baldwinpc_m: ^15:07
pc_mcarl_baldwin: OK, so looks like VPN code is expecting there to be a namespace.15:08
*** saggi has joined #openstack-meeting-315:08
*** baoli has joined #openstack-meeting-315:08
*** saggi- has quit IRC15:08
*** MarkAtwood has joined #openstack-meeting-315:08
pc_mdo we know if the sequence there has changed a bit?15:09
*** zz_johnthetubagu is now known as johnthetubaguy15:09
pc_m(did it create namespace earlier, before?)15:09
carl_baldwinpc_m: I don’t think so but we can look at it a bit later on in the day.15:09
pc_mcarl_baldwin: sure15:10
mlavallepc_m: the way I understand this is that the sequence didn't change. What I discovered when working in the refactoring is that the namespace is created implcitely under certain circumstances.15:10
carl_baldwinpc_m: I will be on-and-off a bit this morning but will be working late.15:10
pc_mLooks like VPN expects the router to have a namespace.15:11
pc_mI'll look at the VPN code more and can touch base later.15:11
carl_baldwinpc_m: It seems like a reasonable expectation for vpn.15:11
carl_baldwinpc_m: I mean, if it isn’t there vpnaas can’t do much.  :)15:12
mlavallepc_m: I can share with you whant I discovered after the meting and maybe we can come to a better understanding15:12
pc_mmlavalle: that would be nice. Thanks!15:12
*** esp has left #openstack-meeting-315:12
carl_baldwinpc_m: mlavalle: I should be on solidly after about 11MDT and until 7MDT.  Grab me then.15:12
mlavallewill do15:13
*** erikmwilson has joined #openstack-meeting-315:13
pc_mroger that15:13
carl_baldwinAny other bugs?15:13
*** tmorin has joined #openstack-meeting-315:13
carl_baldwin#topic L3 Agent Restructuring15:15
*** openstack changes topic to "L3 Agent Restructuring (Meeting topic: neutron_l3)"15:15
carl_baldwinI did put up one more patch to clean up some remaining router stuff in the agent.15:15
carl_baldwin#link https://review.openstack.org/#/c/163222/15:16
carl_baldwinIt changes the sequence of some things wrt to ha routers but I didn’t think it would be a problem.15:16
carl_baldwinamuller: ^15:16
amullerack15:16
*** masco has quit IRC15:17
*** yamahata has joined #openstack-meeting-315:17
carl_baldwinIt was very tangly.  :)  Teasing it apart was an interesting mental exercise.15:17
carl_baldwinThat is about all I have.  Just hoping it can all get in.15:18
carl_baldwin#topic neutron-ipam15:18
*** openstack changes topic to "neutron-ipam (Meeting topic: neutron_l3)"15:18
*** MarkAtwood_ has joined #openstack-meeting-315:19
carl_baldwinI think we’re missing John, Salvatore, and Ryan today.15:19
seizadicarl:john is on PTO I'm sitting in for him15:20
seizadiI don't have anything new to report15:20
carl_baldwinWe are planning to get together tomorrow morning to discuss testing of the reference implementation integration with external IPAM.15:20
seizadiOn IRC?15:20
carl_baldwinWe don’t know yet exactly whre we’ll meet.  Possibly IRC.  If you’re interested, contact me directly and I’ll let you know where/how we will discuss.15:21
*** e0ne has joined #openstack-meeting-315:21
seizadiOK, I'll15:21
carl_baldwinIt looks like the time will be 8am PDT to accomodate various parts of the world.15:21
carl_baldwinseizadi: Thanks.15:22
carl_baldwinAnything else?15:23
*** david-ly_ is now known as david-lyle15:23
carl_baldwin#topic dvr15:23
*** openstack changes topic to "dvr (Meeting topic: neutron_l3)"15:23
carl_baldwinI don’t think I have anything to discuss and I don’t see dvr team around.15:24
carl_baldwin#topic Open Discussion15:24
*** openstack changes topic to "Open Discussion (Meeting topic: neutron_l3)"15:24
pc_mcarl_baldwin: Can you review https://review.openstack.org/#/c/162840/? I think it may avert the issue we see with the namespace.15:26
pc_mcarl_baldwin: It's a VPN commit.15:26
*** ChuckC has joined #openstack-meeting-315:26
carl_baldwinpc_m: Yes, I will review it.15:27
pc_mcarl_baldwin: Essentially, as part of fixing another issue, it changes the sync in VPN to not create a process manager for the VPN process and then turn around an immediately delete it, because no VPN associated with router.15:27
pc_mDoing that, it will never ask for namespace.15:27
pc_mAlthough we do need to understand why the expected namespace is not available.15:28
*** weiting has quit IRC15:28
haleybpc_m, carl_baldwin: did we need a solution to force an iptables apply? i am still struggling through https://review.openstack.org/#/c/158863/ but there's a dependent VPN commit that seems to need the funcionality15:29
haleybit would be easy to add a flag to apply() in the short term15:29
*** bpokorny has joined #openstack-meeting-315:29
carl_baldwinpc_m: We can still discuss later.  I’ll take a look at the review.15:30
pc_mcarl_baldwin: OK.15:30
carl_baldwinhaleyb: What is the dependent VPN commit?15:30
haleybhttps://review.openstack.org/#/c/158865/15:30
pc_mhaleyb: So this is to defer the apply() and VPN applies immediately?15:30
pc_mthat's FWaaS15:31
haleybdoh, you're right15:31
*** Swami has joined #openstack-meeting-315:31
pc_mhad me confused a bit as I didn't know of such change.15:32
carl_baldwinhaleyb: pc_m:  Makes more sense now.15:32
carl_baldwin;)15:32
haleybyes, i will go get more coffee :)15:32
*** masco has joined #openstack-meeting-315:33
haleybcarl_baldwin: you can ping me offline on that if you want15:33
carl_baldwinhaleyb: ok.  Let’s chat about it a bit later.15:33
*** shwetaap1 has quit IRC15:34
*** reed has joined #openstack-meeting-315:34
carl_baldwinLast call for Open Discussion...15:36
carl_baldwin:)15:36
*** shwetaap has joined #openstack-meeting-315:36
carl_baldwinThanks everyone.15:37
carl_baldwin#endmeeting15:37
*** openstack changes topic to "OpenStack Meetings"15:37
openstackMeeting ended Thu Mar 12 15:37:20 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:37
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_l3/2015/neutron_l3.2015-03-12-15.01.html15:37
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_l3/2015/neutron_l3.2015-03-12-15.01.txt15:37
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_l3/2015/neutron_l3.2015-03-12-15.01.log.html15:37
yamamotobye15:37
mlavallebye15:37
pc_mbye15:38
*** pc_m has left #openstack-meeting-315:38
*** mrmartin has joined #openstack-meeting-315:41
*** seizadi has quit IRC15:42
*** Poornima has joined #openstack-meeting-315:42
*** sreshetn1 has joined #openstack-meeting-315:43
*** armax has joined #openstack-meeting-315:46
*** nelsnelson has joined #openstack-meeting-315:48
*** ryansb has joined #openstack-meeting-315:54
*** katco has joined #openstack-meeting-315:54
*** mlavalle has quit IRC15:55
*** Longgeek has joined #openstack-meeting-315:56
*** mrmartin has quit IRC15:58
*** cdent has joined #openstack-meeting-315:59
etoews#startmeeting api wg16:00
openstackMeeting started Thu Mar 12 16:00:23 2015 UTC and is due to finish in 60 minutes.  The chair is etoews. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: api wg)"16:00
openstackThe meeting name has been set to 'api_wg'16:00
annegentleo/16:00
etoewshello annegentle16:00
dtroyero/16:00
kauferhello16:00
elmikoyo/16:01
miguelgrinberghello16:01
*** carl_baldwin has quit IRC16:01
sigmavirus24o/16:01
cdento/16:01
annegentleagenda link?16:02
etoews#topic agenda16:02
*** openstack changes topic to "agenda (Meeting topic: api wg)"16:02
etoews#link https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda16:02
annegentleheh I'm first16:02
etoews#topic JSON schema in WADL for http://developer.openstack.org/api-ref.html16:02
*** saggi has left #openstack-meeting-316:02
*** openstack changes topic to "JSON schema in WADL for http://developer.openstack.org/api-ref.html (Meeting topic: api wg)"16:02
etoews#link https://review.openstack.org/#/c/158348/16:02
annegentlethanks etoews16:03
etoewswanna give us a run down annegentle ?16:03
annegentleI don't know how much more introduction is needed, but I wanted to bring a use case to this group to get input16:03
annegentlebasically, we now use WADL to create http://developer.openstack.org/api-ref.html16:03
annegentleThose WADLs have... okay some of the WADLs have schema in XSD format.16:03
*** emw has quit IRC16:03
*** TravT has joined #openstack-meeting-316:03
*** lakshmiS has joined #openstack-meeting-316:04
cdentis that WADL hand made ?16:04
*** krykowski has joined #openstack-meeting-316:04
annegentlethe schemas aren't complete, but they do tell us what parameter types are expected16:04
*** killer_prince is now known as lazy_prince16:04
*** rosmaita has joined #openstack-meeting-316:04
katcoannegentle: sorry this is my first meeting, can i add something?16:04
annegentlecdent: yes, and hand maintained, so that the service code doesn't get changed out from under us16:04
elmikoi'm really curious about the WADL too, i've been wanting to do something for sahara but i thought there were plans to move away from WADL for the api-ref page?16:05
annegentlecdent: they can be generated, sure, but then shouldn't be autogenerated all the time, so that app devs can rely on the "contract"16:05
etoewsannegentle: hand maintained by who?16:05
*** emw has joined #openstack-meeting-316:05
annegentleetoews: Not very many people. Stats: http://stackalytics.com/report/contribution/api-site/9016:05
cdentannegentle: I wasn't suggesting they should be auto-generated, just was curious how they were generated, as I have tried to use them to auto-generate gabbi tests and had some issues as well.16:06
annegentlekatco: sure, there's gonna need to be a lot of background looks like16:06
annegentlecdent: ah ok, sure.16:06
*** wko has joined #openstack-meeting-316:06
annegentlecdent: you can see the maintenance is tough :)16:06
cdent:)16:06
*** emilyw has joined #openstack-meeting-316:06
elmikoannegentle: has there been any further talk of moving away from WADL?16:06
katcoso i just wanted to clarify; the docs do a great job at generating a human readable site that hints at what parameters are needed, but in terms of semantic structure, it doesn't outline the actual format expected16:07
etoewsannegentle: IMO the maintenance should be on the project teams for the raw schema info16:07
annegentleelmiko: yes, I'd like to next release, but there is no resource assigned to that now16:07
annegentlekatco: yes, agreed.16:07
elmikoannegentle: ack, thanks. i'd really like for sahara to participate in api-ref16:07
annegentlekatco: some of the struggle is in "human-readable or contract-based"?16:07
*** JeanBriceCombebi has quit IRC16:08
annegentleelmiko: great, you got my bug and request then?16:08
katcoannegentle: i don't think the two are mutually exclusive16:08
etoewselmiko: do you think sahara would be willing to be an early adopter (guniea pig) for whatever comes after WADL?16:08
elmikoannegentle: i don't think i saw it, refresh?16:08
annegentleelmiko: oh it was to Sergey, sorry https://bugs.launchpad.net/openstack-api-site/+bug/143086016:08
openstackLaunchpad bug 1430860 in openstack-api-site "Sahara project does not have API docs on the API Reference page at http://developer.openstack.org/api-ref.html" [High,Confirmed]16:08
*** nikhil_k has joined #openstack-meeting-316:08
elmikoetoews: i think it's a real possibility. i'd be happy to help on the effort16:09
elmikoannegentle: no worries =)16:09
*** scheuran_ has quit IRC16:09
*** msundara has joined #openstack-meeting-316:09
elmikoetoews: just as an aside, i did generate swagger for sahara so i think that's a step in the right direction for whatever format we end up moving to16:09
annegentleelmiko: cool16:10
*** sreshetn1 has quit IRC16:10
*** emw has quit IRC16:10
elmikoannegentle: also, i've started a project to help generate swagger for pecan based apps as well16:10
annegentleelmiko: my recent request is due to sahara being included in the "big tent" but not having required API reference16:10
annegentlebut we are digressing off topic, is that enough background info?16:10
*** pkoniszewski has quit IRC16:10
elmikoannegentle: ack, thanks!16:10
*** rprakash has quit IRC16:11
annegentleknowing we are going off of WADL but without a true timeline with deadlines, katco went ahead and made JSON Schema fit into the WADL16:11
annegentlefor Block Storage API16:11
cdentI would prefer to see us move to a modern format (like swagger) instead of further relying upon (and confusing-up) the WADL16:11
elmikocdent: +116:11
cdentHowever, given the lack of timeline, that may not be practical.16:11
annegentlecdent: sure, but what about the timeline? should people wait another six months (minimum)16:11
cdent:)16:12
annegentlecdent: right16:12
*** smc7 has joined #openstack-meeting-316:12
etoewscdent: +1 OTOH most of it wouldn't be wasted effort. the json schema can be reused in swagger (or whatever)16:12
cdentyeah, if katco has already done the work, why not use it?16:12
*** e0ne is now known as e0ne_16:13
annegentlemy guess is we wouldn't get full json schema coverage (unless katco is really really amazing) :)16:13
katcoannegentle: well i certainly plan on doing so for cinder16:14
cdentwe dont need to require parity do we: it's an added bonus where it is provided16:14
annegentleand that was Jon's difficulty16:14
katcoannegentle: we'll see what my team's appetite is for the rest of openstack :)16:14
annegentlekatco: right :) it's a lot16:14
katcoannegentle: well when you're maintaining an sdk...16:15
*** amuller has left #openstack-meeting-316:15
annegentleso my thought was to bring it to this group, for arbitration? Mediation? Meditation? :)16:16
annegentleGuidance really.16:16
etoewskatco: right. it's a huge effort on the doc side but that saves a ton of effort times the number of sdks being supported16:16
katcoetoews: definitely16:17
*** e0ne_ is now known as e0ne16:17
annegentlekatco: what also gave me pause was that Jon is also working on a Go SDK -- so if he was hesitant, what did that mean?16:17
annegentlesince I'm no SDK dev16:18
katcoannegentle: i don't know, i don't know why additional information would hinder his progress16:18
annegentleI just play one on TV, er stayed at a Holiday Inn last night, er.16:18
katcolol16:18
elmikolol16:18
annegentlegenerally speaking is consistency across all OpenStack APIs a requirement for gaining trust in the info provided?16:19
*** JeanBriceCombebi has joined #openstack-meeting-316:19
annegentleperhaps that's the heart of this... that people don't know if they can trust upstream?16:19
annegentlecdent: might have an opinion based on what you saw16:19
*** mrmartin has joined #openstack-meeting-316:19
cdentI'm no sure I understand the question?16:20
etoewsannegentle: in terms of the accuracy of the api doc?16:20
annegentleetoews: in terms of accuracy which in this case extends to machine readability16:20
annegentleetoews: as in, should the upstream doc offer machine readability at all16:20
cdentah. my very first expectation was for strict accuracy, but was quickly disabused of that notion...16:21
annegentlecdent: if you couldn't do what you needed machine-wise with the upstream WADL then perhaps they are meant for human eyes only.16:21
katcoisn't machine readability the point of wadl/swagger/etc.? it's how the documentation site is generated after all16:21
cdentYeah, that's the conclusion I reached, but it would have been helped by having that stated explicitly16:22
cdent(if it already is, I missed it)16:22
annegentlekatco: cdent: ok then the next question is, are the machines going to have to read only XSD for now until we get our timelines in place for swagger16:22
annegentlekatco: (does that accurately encapsulate the difficulty, that your machines can't read XSD?)16:22
*** mrmartin has quit IRC16:22
katcoannegentle: i can support whatever format you find most agreeable; what's important to me is only that the information is present in any format.16:23
cdentI defer to katco: i satisfied my needs (for now), by hand :)16:23
annegentlecdent: in what format did you make those in?16:23
katcoi would sort of like to stick with the work i've already done if possible though :)16:23
*** tmckay has joined #openstack-meeting-316:23
cdentI was trying to auto-generate tests from the WADL when I realized I couldn't do that, I wrote the tests by hand, using the HTML output by the WADL as a guideline.16:24
elmikoeven if we migrate to swagger, i have a feeling there will still be a need for hand hacking some information in16:24
annegentlecdent: ah ok16:24
annegentlecdent: so the WADL and XSD was still the "source of truth"16:24
ryansbelmiko: yeah, that's somewhat expected, and (IMO) swagger is a bit easier to hand-hack16:24
elmikoryansb: agreed16:24
*** seizadi has joined #openstack-meeting-316:24
annegentlehonestly I'm fine with accepting the patch as-is -- it's community doc after all.16:24
annegentlebut consistency and re-use and trust are of course needed.16:25
cdentannegentle: I'd have to say _a_ "source of truth" that got me started, but was not complete16:25
*** seizadi has quit IRC16:25
*** seizadi has joined #openstack-meeting-316:25
annegentlecdent: and incompleteness is also unfortunately a side effect of "community doc"16:25
cdentyeah, and something I understood from the start16:25
annegentleok16:26
*** johnthetubaguy is now known as zz_johnthetubagu16:26
annegentledon't want to take up all meeting time with the topic, but thank you all for the input.16:26
annegentleIf you could vote on the review itself, that'll help a lot!16:26
*** Longgeek has quit IRC16:26
etoewsannegentle: can we call it an experiment? have a look at the results of whatever consumes that json schema before going all in?16:26
katcoetoews: ask and ye shall receive :) https://github.com/katco-/goose/blob/cinder-support/cinder/autogenerated_client.go16:27
annegentlekatco: can you link to go goose16:27
annegentle:) yes thank you16:27
*** stendulker has quit IRC16:27
annegentleetoews: yep definitely want to experiment!16:27
katcoetoews: that is 100% generated code from https://github.com/katco-/wadl2go16:27
cdentwhat a _fanstastic_ name16:28
cdent(goose)16:28
etoewskatco: wadl+json schema?16:28
elmikokatco: neat!16:28
katcoetoews: yes; however, wadl is the driver16:28
*** baoli has quit IRC16:28
katcoetoews: it could support xsd, xml schema, etc. etc.16:28
katcoelmiko: ty!16:28
etoewsthis definitely looks interesting. nice work katco.16:30
katcoetoews: ty, couldn't have done it with the support of this community16:30
*** matrohon has quit IRC16:30
etoewsannegentle: katco: thanks for bringing this up. i think the action here is for people who are interested to review https://review.openstack.org/#/c/158348/316:30
annegentleyes. thanks etoews!16:30
etoewslet's move on16:31
*** salv-orlando has joined #openstack-meeting-316:31
etoews#topic errors16:31
*** openstack changes topic to "errors (Meeting topic: api wg)"16:31
katcoi need to run, but feel free to ping me here on freenode with any questions16:31
katcothank you for your time!16:31
etoews#link http://lists.openstack.org/pipermail/openstack-dev/2015-January/055570.html16:31
etoewsthanks katco16:31
etoewsso there was that extensive thread on errors16:32
etoewsi'd like to come up with a guideline for errors16:32
etoewsi'd probably use json schema to express it16:32
etoewsany thoughts on that?16:32
cdentjson schema seems right, was there resolution on the idea of codes within the message body (instead of just messages)?16:33
* cdent kind of lost track of the thread16:33
*** stendulker has joined #openstack-meeting-316:33
elmikoi wonder if any of the logging wg folks have weighed in on this as well. if we are going to define a schema for output it might be nice to see if they have any ideas.16:34
etoewsthere was some intersection between the two16:34
elmikocool16:35
etoewsi'd like to decouple it as much as possible though. the error code could be the interface between the two. doesn't that make sense?16:35
*** megm has joined #openstack-meeting-316:35
*** egafford has left #openstack-meeting-316:35
etoewss/doesn't/does/16:35
cdentyes16:35
*** megm_ has quit IRC16:35
cdentthe point of the code is to allow (and limit to just) that kind of coupling16:35
etoewsyep16:36
etoewsand maybe some kind of "transaction id" too16:36
elmikomakes sense16:36
elmikowe added unique id's to the error messages in sahara recently, i think they are useful if there is a clear path on what to do with the ids16:36
cdentisn't there already some kind of request id middleware thingie used in some of the projects (which would allow _it_ to be decoupled from _this_)16:37
elmikootherwise it's just another uuid to clutter up the log16:37
*** absubram has joined #openstack-meeting-316:37
etoewselmiko: ya. there needs to be a clear connect between the error response and what's going on in the log.16:38
*** baoli has joined #openstack-meeting-316:38
etoewsonce the guideline is ready i would definitely ask the logging folks to review.16:38
elmikonice16:38
etoews#action etoews to create an error guideline16:39
elmikoi'm not sure the best way to make that connection, but i've experienced some head-scratching moments trying to figure out what all these extra ids and codes are supposed to help with16:39
etoewselmiko: i've got ideas in my head about that and need to get them out to see if the match up with anyone else's ideas about that16:40
elmikoetoews: awesome!16:40
etoews#topic versioning16:40
*** openstack changes topic to "versioning (Meeting topic: api wg)"16:40
etoewssigmavirus24: did you want to talk about this?16:40
*** SridharRamaswamy has joined #openstack-meeting-316:41
rosmaitaif not, i added the subtopic16:41
sigmavirus24I'll defer to rosmaita16:42
rosmaitaok, suppose there is a project, not glance, that is considering adding some new functionality16:42
rosmaitaon a new endpoint16:42
rosmaitaand it's not completely clear that the api is right16:42
rosmaitai mean16:42
rosmaitait is right syntactically, restful and all that16:43
rosmaitabut may not expose all the right stuff for the purpose16:43
rosmaitawhat would it mean if we called it EXPERIMENTAL16:43
rosmaitawhat are our obligations about deprecation, etc16:43
rosmaitathat's basically it16:44
etoewsbeta might be a better word but i get what you mean16:44
rosmaitawell, i was looking at the api ref, it's got current, supported and experimental16:44
etoewsah16:44
elmikois there an X-DONT-EXPECT-TO-LAST header? ;)16:44
rosmaitathat could be arranged16:45
sigmavirus24elmiko: +216:45
elmikoi like being able to have an experimental api, but i also know how experimental can quickly lead to production if too many people get used to it16:45
etoews*wonders if there's any room for expressing "experiementalness" in nova's microversions*16:46
rosmaitawell, we think it's pretty much ready, but want it to get a workout16:46
dtroyerso break it once in a while?16:46
miguelgrinberghow about the traditional approach of not documenting what you don't want people to massively adopt?16:46
etoewselmiko: definitely a valid concern16:46
rosmaitamiguelgrinberg: that also can be arranged16:46
sigmavirus24jaypipes: has also had choice words to say about experimental APIs.16:47
etoewsmiguelgrinberg: basically the approach to a "private" api16:47
sigmavirus24I suspect if cyeoh were around he'd agree16:47
miguelgrinbergright, you can expose undocumented endpoints to test the waters, then decide in a later release if they make it as a public endpoint or not16:47
*** yamahata has quit IRC16:47
etoewsrosmaita: would you have people willing to code to the undocumented endpoints to test them?16:48
rosmaitarosmaita: we actually want it to be used, though16:48
rosmaitaetoews: i think the endpoints would have to exist in service catalogs16:48
*** yamamoto has quit IRC16:48
TravTThink of it like Nova extensions.16:48
*** carl_baldwin has joined #openstack-meeting-316:48
dtroyerI don't like the undocumented bit, that leads to undocumented production APIs.16:48
sigmavirus24etoews: one would likely be tested by Murano16:48
elmikois this a case where increased usage of json-home would help to clear up what is experimental and what is not?16:49
TravTthere is code today in horizon that optionally exposes a feature if the extension is available.16:49
sigmavirus24The other is desired by Horizon but Horizon will probably be less likely to adopt an experimental (undocumented) API16:49
sigmavirus24TravT: difference between experimental and extension is that an extension is ostensibly production ready16:49
rosmaitahow about we doc it as experimental?16:49
rosmaitawe just want to hedge on whether we can introduce breaking changes16:50
dtroyerit is up to the discipline of client-side devs to not make experimental APIs default…if they always require specific action to be used, there should be no surprises down the road16:50
elmikodtroyer++16:51
dtroyerand it will be those devs (and their users) who feel the pain when things break because they did not follow that16:51
etoewsdtroyer: that's reasonable to me16:51
rosmaitadtroyer: so are you saying it's ok to make a breaking change, it's buyer-beware?16:52
etoewsrosmaita: in terms of doc'ing it, i don't think these nova docs go far enough http://developer.openstack.org/api-ref-compute-v2.1.html16:52
dtroyerfor experimental, yes16:52
TravTdtroyer: that makes sense and the experimental designation is just more of notification so developers know and can make an informed decision?16:52
dtroyerit would still be nice to do the versioning thing though16:52
lakshmiSdtroyer: +116:52
etoewsall they say is EXPERIMENTAL but don't explain what it really means.16:53
rosmaitaetoews: yes, we would be much more explicit16:53
rosmaitain fact, that's why i raised the question16:53
rosmaitawhat about the header business?16:54
rosmaitawe are thinking experimental in K, will make a decision to finalize in L16:54
rosmaitanot sure a header will really help16:54
rosmaitabut maybe that was a joke16:54
elmikoi'm not sure that it would help, just throwing it out there16:54
TravTX-API-Status: Experimental16:55
etoewsrosmaita: and this would be for a new endpoint of an existing api or a new project/api altogether.16:55
elmikogiven that many apis use the version as the root, e.g. /v1/.... , couldn't we recommend using /experimental/... or similar? (or does this break too many wsgi servers)16:55
*** Swami has quit IRC16:55
dtroyerI'm not sure what a header adds if you already know the API is experimental by picking it out of the service catalog that way16:55
rosmaitaelmiko: that's an interesting idea16:56
TravTor typically, you'd see v0.116:56
dtroyeror even use /x1/ or similar so you still follow the conventions of production16:56
elmikoright, x1 is nice and short too =)16:57
rosmaitaworks for me16:57
*** jschwarz has left #openstack-meeting-316:57
elmikothen you would know from the endpoint in the service catalog what you are pointing at16:57
TravTthat seems nice and clean16:57
dtroyerI think one of the keys is that while experimental, it should still mirror production practices16:57
TravTand we don't have to upgrade keystone features to support it.16:57
rosmaitadtroyer: no problem there16:57
*** crobertsrh has quit IRC16:58
etoewshmmmm...so what's the path for going from experimental to production in terms of versioning?16:58
elmikothat's a tougher question imo16:58
TravTx1 become v1?  or x2.4 becomes v2.4?16:58
etoewsi somehow thought we were moving away from putting the version in the url16:58
*** mwagner_lap has quit IRC16:59
dtroyerTravT: that was my thinking, or start over at /v116:59
*** seizadi has quit IRC16:59
*** SridharRamaswamy has quit IRC16:59
etoewse.g. nova using a header for it's versioning16:59
*** seizadi has joined #openstack-meeting-316:59
dtroyeretoews: I'd love that, but if it will have one in production it should have one in exp...16:59
sigmavirus24etoews: I'd love to move away from that16:59
elmikoetoews: i had not considered that16:59
sigmavirus24Accept headers for JSON APIs are the de facto standard mostly anywhere else17:00
etoewslooks like we'll have to continue in #openstack-api17:00
etoews#endmeeting17:00
*** openstack changes topic to "OpenStack Meetings"17:00
openstackMeeting ended Thu Mar 12 17:00:23 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/api_wg/2015/api_wg.2015-03-12-16.00.html17:00
cdentsigmavirus24++17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/api_wg/2015/api_wg.2015-03-12-16.00.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/api_wg/2015/api_wg.2015-03-12-16.00.log.html17:00
elmikothanks etoews !17:00
*** smc7 has left #openstack-meeting-317:00
*** smc7 has joined #openstack-meeting-317:00
*** smc7 has left #openstack-meeting-317:00
*** cdent has left #openstack-meeting-317:00
*** sahid has quit IRC17:01
*** krykowski has quit IRC17:03
*** elmiko has left #openstack-meeting-317:06
*** hemanthravi has joined #openstack-meeting-317:06
*** Swami has joined #openstack-meeting-317:07
*** LouisF has joined #openstack-meeting-317:08
*** wko has left #openstack-meeting-317:09
*** yamahata has joined #openstack-meeting-317:09
*** kaufer has quit IRC17:10
*** hemanthravi has left #openstack-meeting-317:11
*** tmorin has quit IRC17:11
*** JeanBriceCombebi has quit IRC17:12
*** JeanBriceCombebi has joined #openstack-meeting-317:14
*** crobertsrh has joined #openstack-meeting-317:15
*** ryansb has left #openstack-meeting-317:20
*** sbalukoff has quit IRC17:22
*** melwitt has joined #openstack-meeting-317:22
*** LouisF has quit IRC17:24
*** zz_johnthetubagu is now known as johnthetubaguy17:25
*** devlaps has joined #openstack-meeting-317:26
*** evgenyf has quit IRC17:29
*** wuhg has quit IRC17:29
*** ivar-lazzaro has joined #openstack-meeting-317:33
*** e0ne has quit IRC17:37
*** lazy_prince is now known as killer_prince17:41
*** shwetaap1 has joined #openstack-meeting-317:45
*** shwetaap has quit IRC17:48
*** JeanBriceCombebi has quit IRC17:50
*** jtomasek has quit IRC17:50
*** Yi has joined #openstack-meeting-317:52
*** safchain has quit IRC17:52
*** Yi_ has quit IRC17:55
*** johnthetubaguy is now known as zz_johnthetubagu17:57
*** SumitNaiksatam has joined #openstack-meeting-317:59
*** annegentle has quit IRC18:00
*** lakshmiS has quit IRC18:00
SumitNaiksatamivar-lazzaro: hi18:00
ivar-lazzarohi18:00
*** SridharRamaswamy has joined #openstack-meeting-318:01
SumitNaiksatami think we have “lighter” attendance today?18:01
SumitNaiksatami dont see rkukura18:01
SumitNaiksatammagesh-gv is sick, and banix indicated he can’t make it either18:01
SumitNaiksatamYi: yapeng: hi18:01
YiSumitNaiksatam: hi18:02
*** rkukura has joined #openstack-meeting-318:02
Yitime got changed?18:02
*** igordcard_ has joined #openstack-meeting-318:02
SumitNaiksatamYi: yes i sent out an email, its on account of PDT18:03
SumitNaiksatamYi: oops, i think i missed you on that email, apologies18:03
SumitNaiksatamlets get started18:03
SumitNaiksatam#startmeeting networking_policy18:03
openstackMeeting started Thu Mar 12 18:03:34 2015 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot.18:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:03
*** openstack changes topic to " (Meeting topic: networking_policy)"18:03
openstackThe meeting name has been set to 'networking_policy'18:03
SumitNaiksatam#info agenda https://wiki.openstack.org/wiki/Meetings/GroupBasedPolicy#March_12th_201518:03
SumitNaiksatamso i tweaked the meeting format a wee bit and added a “standing items” agenda at the top18:04
SumitNaiksatam#link https://wiki.openstack.org/wiki/Meetings/GroupBasedPolicy#Standing_items18:04
yapenghello18:04
*** hemanthravi has joined #openstack-meeting-318:04
SumitNaiksatamyapeng: hemanthravi rkukura: hi18:04
hemanthravihi18:05
rkukuraSumitNaiksatam: hi18:05
SumitNaiksatamwe can add/delete from the standing items as necessary18:05
yapengthe meeting time has changed?18:05
SumitNaiksatamyapeng: daylight savings18:05
SumitNaiksatamUTC time has not changed18:05
rkukurayapeng: Its UTC time hasn’t changed18:05
yapengSumitNaiksatam: oh, i forgot this :)18:06
*** mwagner_lap has joined #openstack-meeting-318:06
SumitNaiksatamyapeng: i sent out a reminder email, but i think i forgot to add you and Yi, apologies18:06
*** seizadi has quit IRC18:06
*** seizadi1 has joined #openstack-meeting-318:06
SumitNaiksatam#info Kilo-2 is March 16th18:06
SumitNaiksatamwith that lets quickly run through the standing agenda items18:07
SumitNaiksatam#topic Bugs18:07
*** openstack changes topic to "Bugs (Meeting topic: networking_policy)"18:07
*** stendulker has quit IRC18:07
SumitNaiksatamI have not posted the new stable/juno yes because we still have some reviews pending which targeted for this18:08
SumitNaiksatam#link https://wiki.openstack.org/wiki/GroupBasedPolicy/kilo-bug-squash18:08
*** crobertsrh has left #openstack-meeting-318:08
SumitNaiksatamrkukura: i believe ivar-lazzaro had comments on each of your two patches18:08
rkukurayes, on https://review.openstack.org/#/c/161619/, he wanted me to change the UT approach18:09
*** rosmaita has left #openstack-meeting-318:09
SumitNaiksatamrkukura: okay, so once we wrap up these two bugs, and backport, i think we can cut the new stable18:10
rkukuraAnd just a nit on https://review.openstack.org/#/c/161968/18:10
SumitNaiksatamrkukura: i will look out for the new patches (other cores please look out as well)18:10
rkukuraChanging the UTs would take me some time - probably next week18:10
rkukuraWith neutron kilo-3 coming up, I need to prioritize that right now18:11
*** Longgeek has joined #openstack-meeting-318:11
*** annegentle has joined #openstack-meeting-318:12
SumitNaiksatamrkukura: ivar-lazzaro: is there any middle ground on this? i would hate to delay the stable/juno even further18:12
rkukuraI’d think we could file a bug to improve the UT later18:12
SumitNaiksatamrkukura: okay, ivar-lazzaro does that work for you?18:12
ivar-lazzarosure18:13
rkukuraI could also add a REVISIT comment in the current UT18:13
SumitNaiksatamrkukura: either one works for me18:13
*** nbouthors has joined #openstack-meeting-318:13
rkukuraI’ll respin both patches today, adding the REVISIT and fixing the nit.18:14
SumitNaiksatamgreat, lets try to close this today, and the backport by tomorrow, so i can cut the new stable/juno over the weekend18:14
SumitNaiksatamrkukura: thanks!18:14
rkukuraSumitNaiksatam: sounds good18:14
SumitNaiksatami dont think the bug which magesh-gv has is critical for the backport18:14
SumitNaiksatamokay, any other bugs that we need to discuss today?18:15
*** annegentle has quit IRC18:15
SumitNaiksatami just noticed that the links i have posted for the bug categories are not working any more, will fix18:15
SumitNaiksatami meant links in the meetings page18:15
*** annegentle has joined #openstack-meeting-318:15
*** baoli has quit IRC18:16
SumitNaiksatam#topic Functional/Integration Tests18:16
*** openstack changes topic to "Functional/Integration Tests (Meeting topic: networking_policy)"18:16
SumitNaiksatammay be i will spend a couple of mins here explaining to the team what we need to do18:16
SumitNaiksatamfirst we need to configur an openstack-infra gate job such that it will trigger a run on every patch-set (just like we have pep8 and py27 UT jobs today)18:17
SumitNaiksatamfor this i had posted the patch:18:17
SumitNaiksatam#link https://review.openstack.org/#/c/16151118:17
*** susaant has joined #openstack-meeting-318:17
SumitNaiksatamstill waiting for reviews on that18:18
SumitNaiksatamcurrently this is being proposed as an experimental job18:18
*** Poornima has quit IRC18:18
SumitNaiksatamwhich means it will not run automatically, you would have to do a “check experimental” to trigger it18:18
SumitNaiksatamonce we are comfortable that the job works as desired, we will make it voting on all patches18:19
SumitNaiksatamfor this job to run, we need to implement pre- and post-job hooks in GBP as well18:19
SumitNaiksatami have posted a patch for this in GBP: #link https://review.openstack.org/#/c/16153218:20
SumitNaiksatamthe above scripts are to help customize the job for GBP18:20
SumitNaiksatamthe job can trigger all kinds of functional and tempest tests18:20
ivar-lazzaronice18:21
SumitNaiksatamjishnub is working on adapting his test suite such that the job will run those tests18:21
SumitNaiksatami would characterize those tests more in the functional category18:21
SumitNaiksatamwe still need the tempest tests18:22
SumitNaiksatamgood development here is that other projects have started moving their tempest tests from the tempest repo to the individual project repos18:22
SumitNaiksatamso there is some precedence that we can use18:22
SumitNaiksatamin terms of how this is done, and how the tempest lib is used18:23
SumitNaiksatamof course, we need to write the tempest tests as well18:23
rkukuraSumitNaiksatam: Are tempest-speciifc clients required, or can we use python-gbpclient?18:23
SumitNaiksatamrkukura: i am not clear on that level of detail, but i believe tempest used to have a client wrapper inside to make rest calls?18:24
SumitNaiksatamrkukura: i dont think that has changed18:24
rkukuraSumitNaiksatam: That’s what I was refering to18:24
SumitNaiksatamrkukura: so good point, we need someone to do this investigation, and hence...18:25
SumitNaiksatamany volunteers to work on this? ;-)18:25
SumitNaiksatamthis is a critical area of the project, and will need ongoing effort and committment18:25
SumitNaiksatamwe dont have to decide here, but please let me know if you would like to pitch in18:26
SumitNaiksatamas it stands, this is the responsibility of the entire team - so if you write a new feature, you sign up to write the tempest tests for that as well!18:26
ivar-lazzaroSumitNaiksatam: +1 on that18:26
SumitNaiksatamof course, we need to have the framework in place first, but assuming we have that18:27
SumitNaiksatamivar-lazzaro: ack18:27
SumitNaiksatamany questions, on the above?18:27
SumitNaiksatamthis aspect has been top of mind for a long time, but we really have to get this done now, and we will track the progress on a weekly basis18:28
SumitNaiksatamokay moving on :-)18:29
SumitNaiksatam#topic Packaging update18:29
*** openstack changes topic to "Packaging update (Meeting topic: networking_policy)"18:29
SumitNaiksatamrkukura: anything significant to report?18:29
SumitNaiksatamwe already discussed the stable branches18:29
rkukuranothing recent - plan to update fedora and RDO once the stable/juno release happens18:29
SumitNaiksatamrkukura: ah so one more on that18:30
SumitNaiksatami notice susaant is here too18:30
SumitNaiksatamwe owe susaant at least three reviews on the heat/automation side18:30
SumitNaiksatamand couple of those are backport-worthy18:30
SumitNaiksatamsusaant: apologies, i believe you have been patiently waiting for almost a month now18:31
*** Longgeek has quit IRC18:31
susaantSumitNaiksatam: Not a problem.18:31
SumitNaiksatamrkukura: so we will need to include those in the stable/juno for gbp-automation18:31
SumitNaiksatami will coordinate with susaant today and tomorrow18:31
SumitNaiksatamsusaant: thanks!18:31
SumitNaiksatam#topic Docs18:31
*** openstack changes topic to "Docs (Meeting topic: networking_policy)"18:31
rkukuraWill we be releasing for all 4 repos?18:31
SumitNaiksatam#undo18:32
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0x90890d0>18:32
SumitNaiksatamrkukura: yes18:32
rkukurathanks18:32
SumitNaiksatami have a patch that i need to post on UI side that i have been sitting on18:32
SumitNaiksatamso we need to get that reviewed and merged as well18:32
SumitNaiksatamphew!18:33
SumitNaiksatam#topic Docs18:33
*** openstack changes topic to "Docs (Meeting topic: networking_policy)"18:33
*** masco has quit IRC18:33
SumitNaiksatami dont have anything specific on this for today, but i wanted to note this as a standing agenda item18:33
SumitNaiksatamover course of time we need to track that each feature is documented (just like tempest test support)18:34
SumitNaiksatambtw, if you haven’t noticed already, we do have in-tree documentation:18:34
SumitNaiksatam#link https://github.com/stackforge/group-based-policy/tree/master/doc/source18:34
SumitNaiksatamwould really appreciate more feedback on this and  feel free to propose patches to edit/update this18:35
SumitNaiksatamnow coming to the agenda items specifically for today18:36
SumitNaiksatam#topic GBP Project Proposal18:36
*** openstack changes topic to "GBP Project Proposal (Meeting topic: networking_policy)"18:36
SumitNaiksatam#link https://review.openstack.org/#/c/161902/18:36
SumitNaiksatamper discussion in last meeting, we went ahead and put forward the proposal18:36
SumitNaiksatamplease read and feel free to comment18:37
SumitNaiksatamit should not surprise any one, since its mostly what we have been discussing all along18:37
SumitNaiksatami changed this to WIP earlier today since there were some comments, and it was felt that we should address them before proposal gets discussed in the TC meeting18:38
SumitNaiksatamany thoughts on the above?18:38
*** Sukhdev has joined #openstack-meeting-318:38
SumitNaiksatamone of the things that we needed to do was to have the PTL elections18:39
rkukuraAre we going to wait for temest-based gate tests before removing WIP?18:39
SumitNaiksatamrkukura: at this point i think we would want the gate job to be running18:40
rkukuraSumitNaiksatam: Do you mean the current no-op test?18:41
SumitNaiksatami do not believe this is an explicit requirement though18:41
hemanthraviis that the only reqmt for removing wip18:41
SumitNaiksatamrkukura: perhaps more than just the no-op test :-)18:41
ivar-lazzarohemanthravi: I think the PTL election is another one18:41
SumitNaiksatamhemanthravi: we have proactively put this into WIP18:41
*** sbalukoff has joined #openstack-meeting-318:42
SumitNaiksatamivar-lazzaro: true18:42
*** lblanchard has quit IRC18:42
SumitNaiksatamthough even on that we did not get -118:42
ivar-lazzaroThose seem reasonable requirements to me18:42
*** pkoniszewski has joined #openstack-meeting-318:43
SumitNaiksatamsince there is no prior precedence of PTL elections for stackforge projects18:43
SumitNaiksatamivar-lazzaro: yeah18:43
SumitNaiksatamhence we proactively put into WIP18:43
SumitNaiksatamdoes everyone agree with the approach, or have other suggestions?18:43
ivar-lazzaroThat's what we are here for right? setting precedents ;)18:43
SumitNaiksatamivar-lazzaro: nice one! ;-)18:43
SumitNaiksatamhemanthravi: to your question, i dont know18:44
SumitNaiksatamhemanthravi: this is an evolving topic, so if you see the TC meeting last week, there were a number of things which came up during the discussion of the Magnum proposal18:44
SumitNaiksatamthough to the best of my knowledge there are not new requirements, yet18:45
SumitNaiksatami believe the TC will evaluate a few more proposals in the next meeting, and take if from there18:45
SumitNaiksatamwe are running behind schedule today18:45
SumitNaiksatam#topic GBP PTL elections18:46
*** openstack changes topic to "GBP PTL elections (Meeting topic: networking_policy)"18:46
SumitNaiksatam#link http://lists.openstack.org/pipermail/openstack-dev/2015-March/058783.html18:46
SumitNaiksatamthere is one candidate so far: #link http://lists.openstack.org/pipermail/openstack-dev/2015-March/058925.html18:47
SumitNaiksatamI expect the wiki page: #link https://wiki.openstack.org/wiki/GroupBasedPolicy/PTL_Elections_Kilo_Liberty18:47
SumitNaiksatamto be updated with the list of candidates and the results18:47
*** SridharRamaswamy is now known as sridhar_ram18:48
SumitNaiksatamif you have a commit in the GBP project, you get to vote18:48
SumitNaiksatamanye questions/comments on the above?18:48
rkukuraSumitNaiksatam: Do you know when the polling starts/ends?18:48
ivar-lazzaro--> March 17, 2015 - 1300 UTC March 24, 2015: PTL elections18:49
SumitNaiksatamrkukura: i think its mentioned on the wiki, i believe starts on march 18th, ends on march 24th18:49
SumitNaiksatamoh march 17th then18:49
SumitNaiksatamivar-lazzaro: thanks18:49
rkukuraI see - thanks18:49
SumitNaiksatammoving on18:50
SumitNaiksatam#topic Re-factor Group Based Policy with Neutron RESTful APIs18:50
*** openstack changes topic to "Re-factor Group Based Policy with Neutron RESTful APIs (Meeting topic: networking_policy)"18:50
SumitNaiksatami know yapeng and Yi are patiently waiting18:50
SumitNaiksatamso we spent significant amount of time on the reviews yesterday18:50
SumitNaiksatamivar-lazzaro: and rkukura thanks for the reviews18:50
SumitNaiksatamYi: and yapeng thanks for your time and indulging as well18:50
SumitNaiksatamYi: yapeng do we need to discuss anything today, or are you good?18:51
yapengthanks for all the comments. I think we are all good for now18:51
YiSumitNaiksatam: I am good here18:51
SumitNaiksatamhttps://review.openstack.org/#/c/159725, https://review.openstack.org/#/c/156776, https://review.openstack.org/#/c/15685618:51
SumitNaiksatamyapeng: Yi: sweet18:51
SumitNaiksatam#topic Floating IP support18:51
*** openstack changes topic to "Floating IP support (Meeting topic: networking_policy)"18:51
SumitNaiksatammagesh-gv has been sick for the past couple of days, so he is not able to make it18:52
SumitNaiksatamhe still working on this though, and has sent an update18:52
SumitNaiksatamhe says - “For floating IP support I am going ahead with Nat Pool and use admin context to do the floating IP create and attach in single step. “18:53
SumitNaiksatamhe also says - “The ability to specify floating IP in create operation is added recently only.” (he is referring to Neutron)18:53
SumitNaiksatami was not sure about the later18:54
SumitNaiksatamso need to follow up with him18:54
SumitNaiksatamrkukura: if you are familiar with the changes there, please respond to the email thread18:54
*** jcoufal has quit IRC18:54
rkukuraSumitNaiksatam: I’m not, so will need to investigate a bit18:55
SumitNaiksatamrkukura: okay18:55
SumitNaiksatami will skip task flow investigation for today18:55
SumitNaiksatam#topic Cross Project Liaisons18:55
*** openstack changes topic to "Cross Project Liaisons (Meeting topic: networking_policy)"18:55
SumitNaiksatamas we are growing, and aspire to enhance our interaction with other OpenStack projects, we need to have people who will take lead on these18:56
*** mattgriffin has joined #openstack-meeting-318:56
SumitNaiksatamat the very least, we need to track the meeting logs of some the other projects we depend on, or have interlocks18:57
SumitNaiksatamso four projects come to mind upfront18:58
*** thangp has quit IRC18:58
SumitNaiksatamoslo, neutron, keystone and nova18:58
rkukuraheat and horizon?18:58
SumitNaiksatamrkukura: you bet, sorry i missed those18:58
rkukuraSumitNaiksatam: I’d consider oslo and/or nova18:59
*** sreshetn1 has joined #openstack-meeting-318:59
SumitNaiksatamrkukura: great, thanks18:59
SumitNaiksatamrkukura: i thought you would want to look at neutron since you are deeply involved :-)18:59
rkukura:(18:59
SumitNaiksatamof course, anyone can look at any project, but we want one go-to person19:00
SumitNaiksatamso rkukura for oslo and nova19:00
rkukuraSumitNaiksatam: I’m lucky to keep up with just ML2 in neutron19:00
SumitNaiksatamrkukura: :-)19:00
*** TravT has left #openstack-meeting-319:00
SumitNaiksatamlet me know if you have interest in other areas19:00
SumitNaiksatam#topic Open Discussion19:00
*** openstack changes topic to "Open Discussion (Meeting topic: networking_policy)"19:00
SumitNaiksatamivar-lazzaro: had an excellent suggestion that we should plan the mid-cycle code sprint19:01
rkukuraI have one item19:01
SumitNaiksatamrkukura: please go ahead19:01
rkukuraGiven that neutron has postponed the pecan BP post-kilo, should we consider having our master track neutron master, at least until we become a standalone server?19:01
rkukuraCouple of benefits:19:02
ivar-lazzarorkukura: that requires some refactoring as well (although it's not the same amount of work)19:02
SumitNaiksatamrkukura: absolutely, we have to do that19:03
rkukura1) We’ll be ready to take advantage of kilo features, especially the subnet pools19:03
SumitNaiksatamrkukura: that is a major item on to-do list19:03
rkukura2) fedora rawhide, RDO, and probably other distros are packaging kilo, and we get left out for now19:03
rkukura3) tracking only juno could come up during project proposal review19:04
rkukurathats all19:04
SumitNaiksatamrkukura: agree19:04
SumitNaiksatamrkukura: and that is a kilo item we have to accomplish19:04
SumitNaiksatamrkukura: we just need to figure out the right sequence of refactor activities19:05
SumitNaiksatamrkukura: lets discuss on this, and get this rolling at the earliest19:05
SumitNaiksatammagesh-gv also brought this up in his email19:05
SumitNaiksatamregarding the code-sprint i am thinking end of March/beginning of April19:05
rkukuraI’m not saying we should postpone becoming standalone beyond our kilo, but if that happens, we are probably better of tracking kilo now than just at the end19:05
ivar-lazzaroSumitNaiksatam: I'll be in Italy at that time :)19:06
SumitNaiksatamrkukura: absolutely19:06
SumitNaiksatamivar-lazzaro: oops19:06
SumitNaiksatamivar-lazzaro: okay, lets coordinate in #openstack-gbp then19:06
ivar-lazzaroSumitNaiksatam: however I can attend remotely, no problems19:06
ivar-lazzarorkukura: +119:06
SumitNaiksatamwe need to get all the specs sorted out before we get to code sprint19:06
*** bpokorny_ has joined #openstack-meeting-319:06
SumitNaiksatami noticed that nbouthors also joined earlier19:07
SumitNaiksatamnot sure if he had an update19:07
rkukuraI’d be willing to travel for a sprint, but 1st week of April wouldn’t work for me I think19:07
SumitNaiksatamrkukura: ah okay, lets coordinate, i just wanted to throw in the idea19:07
SumitNaiksatamokay i will sync up with nbouthors offline19:08
SumitNaiksatamthanks all19:08
SumitNaiksatambye19:08
ivar-lazzarociaoooo19:08
*** hemanthravi has left #openstack-meeting-319:08
rkukurabye19:08
SumitNaiksatam#endmeeting19:08
*** openstack changes topic to "OpenStack Meetings"19:08
openstackMeeting ended Thu Mar 12 19:08:34 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:08
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_policy/2015/networking_policy.2015-03-12-18.03.html19:08
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_policy/2015/networking_policy.2015-03-12-18.03.txt19:08
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_policy/2015/networking_policy.2015-03-12-18.03.log.html19:08
*** bpokorn__ has joined #openstack-meeting-319:09
*** bpokorny has quit IRC19:10
*** carl_baldwin has quit IRC19:10
*** seizadi1 has quit IRC19:12
*** bpokorny_ has quit IRC19:13
*** rkukura has left #openstack-meeting-319:13
*** seizadi has joined #openstack-meeting-319:18
*** seizadi has quit IRC19:19
*** tmckay has left #openstack-meeting-319:20
*** yapeng has quit IRC19:23
*** yapeng has joined #openstack-meeting-319:26
*** sigmavirus24 is now known as sigmavirus24_awa19:27
*** sigmavirus24_awa is now known as sigmavirus2419:28
*** smc7 has joined #openstack-meeting-319:29
*** dtroyer has left #openstack-meeting-319:31
*** e0ne has joined #openstack-meeting-319:39
*** Yi has quit IRC19:40
*** marun has quit IRC19:54
mattgriffinHA Guide Update meeting in 4 minutes19:56
*** igordcard_ has left #openstack-meeting-319:59
mattgriffinmegm, hello!20:00
mattgriffinseen nick around?20:00
megmHi, Matt!  No, I haven't seen nick, but I'm in Cal and he's in N Carolina so...20:01
mattgriffinmegm, ok. how about sam-i-am?20:01
megmNo, I see noone except thee and me here.20:01
* mattgriffin scrolls up20:02
mattgriffin:)20:02
*** melwitt_ has joined #openstack-meeting-320:02
*** mikal_ is now known as mikal20:02
*** seizadi has joined #openstack-meeting-320:02
*** melwitt has quit IRC20:02
*** melwitt_ is now known as melwitt20:02
mattgriffinmegm, ok to wait a few minutes?20:03
*** seizadi has quit IRC20:03
*** seizadi has joined #openstack-meeting-320:03
megmI just skype'd Nick20:03
mattgriffinok20:03
*** baoli has joined #openstack-meeting-320:03
*** baoli has quit IRC20:04
megmNo response.20:04
*** baoli has joined #openstack-meeting-320:05
megmWhile we're waiting, do you know why the old HA guide was subdivided into active/passive and active/active?20:05
mattgriffinmegm, i don't know the history there20:06
mattgriffinmegm, i have a few things on the agenda. i'd like to go ahead and start. can email log to others later. ok?20:06
megmOkay.  We're wiping out that distinction in the new structure, which I think is fine, but it's worth verifying.20:06
megmSure, go ahead.20:07
mattgriffin#startmeeting HA-Guide-Update20:07
openstackMeeting started Thu Mar 12 20:07:11 2015 UTC and is due to finish in 60 minutes.  The chair is mattgriffin. Information about MeetBot at http://wiki.debian.org/MeetBot.20:07
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:07
*** openstack changes topic to " (Meeting topic: HA-Guide-Update)"20:07
openstackThe meeting name has been set to 'ha_guide_update'20:07
mattgriffinagenda: https://wiki.openstack.org/wiki/Documentation/HA_Guide_Update#Next_Meeting20:07
mattgriffin#link https://wiki.openstack.org/wiki/Documentation/HA_Guide_Update#Next_Meeting20:07
*** jgrimm is now known as zz_jgrimm20:07
mattgriffin#topic Review HA Guide update for Docs20:07
*** openstack changes topic to "Review HA Guide update for Docs (Meeting topic: HA-Guide-Update)"20:07
mattgriffinmegm, the first topic has to do with just what you were asking about :)20:08
mattgriffincan you take a look at this draft update to the rest of the Docs team on what we're doing?20:08
mattgriffin#link https://etherpad.openstack.org/p/ha-guide-march-2015-update20:08
mattgriffinmegm, ^20:08
megmJust a sec -- looking20:09
mattgriffinmegm, ok. it brings up that point about changing the structure completely. feel free to modify anything in the pad though20:09
megmOkay.  I'll do that after we're done here.20:10
mattgriffincool20:10
*** matrohon has joined #openstack-meeting-320:10
mattgriffinnext topic on the agenda20:10
mattgriffin#topic Outline/TOC update20:10
*** openstack changes topic to "Outline/TOC update (Meeting topic: HA-Guide-Update)"20:10
megmWe are scoping this work to just include the core pieces.  I'm thinking that Ceph also needs to be included20:10
megmDo you disagree?  Hopefully we can mostly link to Ceph docs but I see no other way to really have HA data storage20:11
mattgriffinmegm, i think probably a placeholder but might be some pushback since it's not official20:11
mattgriffinmegm, good point re: the docs links20:12
megmOkay, it's currently mentioned in the outline so that's probably good20:12
mattgriffincool20:12
mattgriffinmegm, any other significant updates this past week?20:12
megmNo, I'm reading docs and tweaking the outline.20:13
megmHow do we move forward and start the actual work?20:13
mattgriffinmegm, ok. related to the third topic on the agenda... i'm going to get some eyes on the TOC from Percona20:13
megmDo you have contributors from Percona to offer?  Nick was supposed to dig up some Mirantis people.20:13
*** seizadi has quit IRC20:13
*** seizadi has joined #openstack-meeting-320:14
mattgriffinmegm, i'm digging too :)20:14
*** zz_jgrimm is now known as jgrimm20:14
mattgriffinmegm, regarding moving forward, i think we should look to reuse as much from the current HA Guide content as possible20:14
megmFor mechanics, can we create a "new" doc structure and move content from the old as appropriate?  Or do we need to work in the existing ha_guide?20:15
megmI agree about reusing -- I suspect everything needs to be refined and modified.20:15
mattgriffinmegm, my guess is "new" b/c of the size of the changes20:15
megmSo putting the pieces we plan to use in place and then getting review might be a next step?20:16
*** Longgeek has joined #openstack-meeting-320:16
mattgriffinprobably see what sam-i-am thinks based on his experience with the Networking Guide20:16
mattgriffinmegm, +1. i like that plan20:16
megmGood idea!  I'm new to a lot of this but I'm confused about the docbook->RST conversion and then restructuring this doc20:17
mattgriffinheh... me too20:17
megm;-)20:17
mattgriffinok... some action items then20:17
megmI like the idea of opening a "new" doc and then we can convert individual sections to RST, add to new structure, review, rewrite...20:18
mattgriffinack20:18
*** sambetts has quit IRC20:18
mattgriffin#action megm review the Docs team email draft on the pad20:18
mattgriffin#action check with sam-i-am and nickchase on starting a "new" doc structure20:19
*** emilyw has quit IRC20:19
megmHow do I communicate that the email draft on the pad is ready for your review?20:19
*** emilyw has joined #openstack-meeting-320:20
mattgriffinmegm, add your name and review status at the top (just added)20:20
mattgriffinwork for you?20:20
*** sambetts has joined #openstack-meeting-320:20
megmAh, I see.  Perfect!20:21
mattgriffinany other action items?20:21
megmDo we want to include a link to our actual outline here?20:21
mattgriffinmegm, should be in the footnotes20:21
megmPreserve last week's actions for you and Nick to enlist some people?20:21
megmOf course!  I need to pay attention ;-)20:22
mattgriffin#action mattgriffin & nickchase: enlist people20:22
*** cbader has quit IRC20:22
mattgriffindone :)20:22
megmSounds good to me!20:22
mattgriffincool. anything else?20:22
megmNope.20:22
mattgriffinmegm, great. that's a wrap. ending meeting20:23
mattgriffin#endmeeting20:23
*** openstack changes topic to "OpenStack Meetings"20:23
openstackMeeting ended Thu Mar 12 20:23:03 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:23
megmUntil next week then?20:23
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ha_guide_update/2015/ha_guide_update.2015-03-12-20.07.html20:23
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ha_guide_update/2015/ha_guide_update.2015-03-12-20.07.txt20:23
openstackLog:            http://eavesdrop.openstack.org/meetings/ha_guide_update/2015/ha_guide_update.2015-03-12-20.07.log.html20:23
*** Longgeek has quit IRC20:23
mattgriffinmegm, thanks! have a great day20:25
megmYou too!20:25
mattgriffinmegm, notes added to https://wiki.openstack.org/wiki/Documentation/HA_Guide_Update#Past_Meetings20:25
*** cbader has joined #openstack-meeting-320:27
*** e0ne has quit IRC20:30
*** e0ne has joined #openstack-meeting-320:34
*** mattgrif_ has joined #openstack-meeting-320:35
*** sreshetn1 has quit IRC20:35
*** megm_ has joined #openstack-meeting-320:37
*** mattgriffin has quit IRC20:37
*** khal has joined #openstack-meeting-320:37
*** megm has quit IRC20:38
*** Sukhdev has quit IRC20:38
*** kyle4879 has joined #openstack-meeting-320:40
*** kyle4879 has quit IRC20:40
*** Yi has joined #openstack-meeting-320:41
*** mrda-away is now known as mrda20:42
*** erikmwilson has quit IRC20:43
*** Yi has quit IRC20:45
*** carl_baldwin has joined #openstack-meeting-320:48
*** khal has left #openstack-meeting-320:49
*** marun has joined #openstack-meeting-320:54
*** mattgriffin has joined #openstack-meeting-320:54
*** mattgrif_ has quit IRC20:58
*** cbader has quit IRC21:01
*** bpokorny has joined #openstack-meeting-321:01
*** bpokorn__ has quit IRC21:04
*** seizadi has quit IRC21:05
*** Sam-I-Am has joined #openstack-meeting-321:05
Sam-I-Ammattgriffin: ha meeting?21:06
*** sarob has joined #openstack-meeting-321:06
mattgriffinSam-I-Am, time change... oh wait21:06
mattgriffindoh!21:07
Sam-I-Ami think everything added an hour to US local21:07
mattgriffinSam-I-Am, we did it an hour ago... you're right21:07
Sam-I-Amcrap21:07
mattgriffinSam-I-Am, sorry. notes are here - https://wiki.openstack.org/wiki/Documentation/HA_Guide_Update#Past_Meetings21:08
mattgriffinapologies. my fault21:08
Sam-I-Ami sent an update from the ops meetup to the docs list21:08
mattgriffinit was only myself and megm_21:08
Sam-I-Amim still recovering from the meetup21:08
Sam-I-Amwe should take a look at the notes and see what we can scour out of the toc21:10
*** Sam-I-Am has left #openstack-meeting-321:14
mattgriffinmegm_ and i discussed that... what is the next step. were hoping you could provide some advice given your experience with the Networking Guide update21:14
mattgriffinbye sam-i-am21:14
megm_Hi, Sam-i-am.  Stupid time change!21:15
mattgriffinarg21:17
*** mattfarina has quit IRC21:19
*** erikmwilson has joined #openstack-meeting-321:20
*** erikmwilson has quit IRC21:23
*** shwetaap1 has quit IRC21:24
*** eghobo has joined #openstack-meeting-321:25
*** shwetaap has joined #openstack-meeting-321:27
*** Yi has joined #openstack-meeting-321:30
*** kevinbenton_ is now known as kevinbenton21:30
*** SridharRamaswamy has joined #openstack-meeting-321:31
*** sridhar_ram has quit IRC21:32
*** mattgriffin has quit IRC21:39
*** Yi has quit IRC21:43
*** susaant has quit IRC21:44
*** Sukhdev has joined #openstack-meeting-321:44
*** msundara has quit IRC21:47
*** amotoki has quit IRC21:49
*** katco has left #openstack-meeting-321:49
*** nbouthors has quit IRC21:50
*** emilyw has quit IRC21:52
*** emw has joined #openstack-meeting-321:53
*** bknudson has quit IRC21:55
*** annegentle has quit IRC21:56
*** SridharRamaswamy has quit IRC22:01
*** melwitt_ has joined #openstack-meeting-322:01
*** sigmavirus24 is now known as sigmavirus24_awa22:02
*** melwitt_ has quit IRC22:02
*** melwitt has quit IRC22:03
*** peristeri has quit IRC22:03
*** SridharRamaswamy has joined #openstack-meeting-322:04
*** sarob has quit IRC22:04
*** e0ne has quit IRC22:05
*** Longgeek has joined #openstack-meeting-322:08
*** eghobo has quit IRC22:10
*** pkoniszewski has quit IRC22:11
*** nelsnels_ has joined #openstack-meeting-322:17
*** carl_baldwin has quit IRC22:18
*** nelsnelson has quit IRC22:19
*** mattgriffin has joined #openstack-meeting-322:19
*** carl_baldwin has joined #openstack-meeting-322:23
*** sergef has quit IRC22:30
*** Longgeek has quit IRC22:32
*** SridharRamaswamy has quit IRC22:35
*** melwitt has joined #openstack-meeting-322:36
*** SridharRamaswamy has joined #openstack-meeting-322:38
*** Yi has joined #openstack-meeting-322:43
*** SridharRamaswamy has quit IRC22:47
*** SridharRamaswamy has joined #openstack-meeting-322:47
*** Yi has quit IRC22:48
*** amotoki has joined #openstack-meeting-322:49
*** nelsnels_ has quit IRC22:50
*** mattgriffin has quit IRC22:51
*** carl_baldwin has quit IRC22:51
*** carl_baldwin has joined #openstack-meeting-322:54
*** amotoki has quit IRC22:55
*** Yi has joined #openstack-meeting-322:55
*** baoli has quit IRC22:55
*** thomasem has quit IRC22:55
*** annegentle has joined #openstack-meeting-322:56
*** emw has quit IRC22:56
*** emw has joined #openstack-meeting-322:56
*** emilyw has joined #openstack-meeting-322:58
*** melwitt has quit IRC22:59
*** emw has quit IRC23:01
*** annegentle has quit IRC23:02
*** MarkAtwood has quit IRC23:04
*** melwitt has joined #openstack-meeting-323:05
*** shwetaap has quit IRC23:06
*** SridharRamaswamy has quit IRC23:08
*** SridharRamaswamy has joined #openstack-meeting-323:08
*** SridharRamaswamy has quit IRC23:09
*** matrohon has quit IRC23:10
*** nelsnelson has joined #openstack-meeting-323:13
*** Yi has quit IRC23:16
*** yamamoto has joined #openstack-meeting-323:18
*** yamamoto has quit IRC23:29
*** absubram has quit IRC23:35
*** melwitt has quit IRC23:35
*** david-lyle is now known as david-lyle_afk23:41
*** Sukhdev has quit IRC23:44
*** smc7 has quit IRC23:51
*** yamamoto has joined #openstack-meeting-323:52
*** shwetaap has joined #openstack-meeting-323:54
*** Yi has joined #openstack-meeting-323:54
*** reed has quit IRC23:55
*** ChuckC has quit IRC23:56
*** nelsnelson has quit IRC23:57
*** annegentle has joined #openstack-meeting-323:58

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