Thursday, 2016-02-11

*** spzala has quit IRC00:00
*** tellesnobrega is now known as tellesnobrega_af00:00
*** tej has joined #openstack-meeting-300:01
*** tej has quit IRC00:02
*** tej has joined #openstack-meeting-300:02
*** irenab_ has joined #openstack-meeting-300:02
*** crinkle has quit IRC00:03
*** FallenPegasus has quit IRC00:04
*** crinkle_ has joined #openstack-meeting-300:04
*** crinkle_ is now known as crinkle00:04
*** rbak has quit IRC00:04
*** irenab has quit IRC00:04
*** irenab_ is now known as irenab00:04
*** nelsnels_ has joined #openstack-meeting-300:07
*** nelsnelson has quit IRC00:08
*** armax has joined #openstack-meeting-300:10
*** lblanchard has joined #openstack-meeting-300:11
*** lblanchard has quit IRC00:12
*** rocky_g has quit IRC00:15
*** safchain has quit IRC00:19
*** rhochmuth1 has quit IRC00:26
*** lblanchard has joined #openstack-meeting-300:30
*** kebray has joined #openstack-meeting-300:33
*** vahidh_ has quit IRC00:35
*** vahidh has joined #openstack-meeting-300:35
*** vahidh has quit IRC00:40
*** kebray has quit IRC00:40
*** Swami has quit IRC00:44
*** Aish has quit IRC00:55
*** spzala has joined #openstack-meeting-300:55
*** Aish has joined #openstack-meeting-300:56
*** ajmiller has quit IRC01:00
*** spzala has quit IRC01:00
*** Aish has quit IRC01:04
*** Aish has joined #openstack-meeting-301:05
*** galstrom_zzz is now known as galstrom01:16
*** Aish has quit IRC01:32
*** jasondotstar has quit IRC01:35
*** eliqiao_ has quit IRC01:36
*** eliqiao_ has joined #openstack-meeting-301:36
*** dims_ has joined #openstack-meeting-301:37
*** jasondotstar has joined #openstack-meeting-301:37
*** dims has quit IRC01:38
*** dims_ has quit IRC01:41
*** zz_dimtruck is now known as dimtruck01:42
*** alex_xu has quit IRC01:43
*** alex_xu has joined #openstack-meeting-301:45
*** dims has joined #openstack-meeting-301:49
*** baoli has joined #openstack-meeting-301:53
*** mickeys has quit IRC01:57
*** spzala has joined #openstack-meeting-301:58
*** madhu_ak has quit IRC01:58
*** eliqiao_ has quit IRC02:00
*** eliqiao_ has joined #openstack-meeting-302:00
*** baoli has quit IRC02:00
*** spzala has quit IRC02:02
*** rossella_s has quit IRC02:03
*** rossella_s has joined #openstack-meeting-302:03
*** asahlin has joined #openstack-meeting-302:04
*** mtanino has quit IRC02:04
*** lblanchard1 has joined #openstack-meeting-302:07
*** Aish has joined #openstack-meeting-302:08
*** alex_xu has quit IRC02:08
*** Aish has left #openstack-meeting-302:08
*** stanzgy_ has joined #openstack-meeting-302:09
*** rmoe_ has joined #openstack-meeting-302:10
*** megm_ has joined #openstack-meeting-302:10
*** alex_xu has joined #openstack-meeting-302:10
*** terryw has joined #openstack-meeting-302:14
*** lblanchard has quit IRC02:15
*** bpokorny has quit IRC02:15
*** ctlaugh has quit IRC02:15
*** otherwiseguy has quit IRC02:15
*** stanzgy has quit IRC02:15
*** rmoe has quit IRC02:15
*** megm has quit IRC02:15
*** galstrom is now known as galstrom_zzz02:16
*** baoli has joined #openstack-meeting-302:17
*** spzala has joined #openstack-meeting-302:21
*** baoli has quit IRC02:23
*** ctlaugh has joined #openstack-meeting-302:23
*** baoli has joined #openstack-meeting-302:24
*** spzala has quit IRC02:29
*** baoli has quit IRC02:29
*** galstrom_zzz is now known as galstrom02:40
*** Poornima has joined #openstack-meeting-302:41
*** armax has quit IRC02:43
*** woodster_ has quit IRC02:46
*** shwetaap has joined #openstack-meeting-302:48
*** Poornima has quit IRC03:05
*** Poornima has joined #openstack-meeting-303:06
*** ivar-laz_ has joined #openstack-meeting-303:10
*** ivar-lazzaro has quit IRC03:12
*** Poornima has quit IRC03:13
*** fawadkhaliq has joined #openstack-meeting-303:16
*** iyamahat has quit IRC03:16
*** yamahata has quit IRC03:17
*** ivar-laz_ has quit IRC03:21
*** ivar-lazzaro has joined #openstack-meeting-303:23
*** sc68cal has quit IRC03:23
*** Poornima has joined #openstack-meeting-303:27
*** baoli has joined #openstack-meeting-303:27
*** neelashah has joined #openstack-meeting-303:28
*** ivar-lazzaro has quit IRC03:30
*** Poornima has quit IRC03:32
*** asahlin has quit IRC03:43
*** asahlin has joined #openstack-meeting-303:44
*** amotoki has joined #openstack-meeting-303:50
*** tej has quit IRC03:51
*** piet has joined #openstack-meeting-303:51
*** amotoki has quit IRC03:57
*** pt_15 has quit IRC04:15
*** dimtruck is now known as zz_dimtruck04:17
*** sc68cal has joined #openstack-meeting-304:20
*** woodster_ has joined #openstack-meeting-304:23
*** amotoki has joined #openstack-meeting-304:29
*** armax has joined #openstack-meeting-304:34
*** baoli has quit IRC04:39
*** salv-orl_ has joined #openstack-meeting-304:41
*** amotoki has quit IRC04:42
*** piet has quit IRC04:42
*** dims has quit IRC04:43
*** salv-orlando has quit IRC04:44
*** fawadkhaliq has quit IRC04:46
*** ajmiller has joined #openstack-meeting-304:49
*** ajmiller has quit IRC04:50
*** armax has quit IRC04:51
*** tej has joined #openstack-meeting-304:51
*** lblanchard1 has quit IRC04:52
*** galstrom is now known as galstrom_zzz04:53
*** tej has quit IRC04:57
*** stendulker has joined #openstack-meeting-304:57
*** julim has joined #openstack-meeting-305:00
*** markvoelker has quit IRC05:03
*** armax has joined #openstack-meeting-305:05
*** piet has joined #openstack-meeting-305:05
*** shwetaap has quit IRC05:09
*** fawadkhaliq has joined #openstack-meeting-305:11
*** neelashah has quit IRC05:14
*** iyamahat has joined #openstack-meeting-305:15
*** piet has quit IRC05:18
*** shwetaap has joined #openstack-meeting-305:19
*** shwetaap1 has joined #openstack-meeting-305:20
*** vahidh has joined #openstack-meeting-305:21
*** bpokorny has joined #openstack-meeting-305:22
*** shwetaap has quit IRC05:24
*** vahidh has quit IRC05:25
*** yamahata has joined #openstack-meeting-305:36
*** piet has joined #openstack-meeting-305:36
*** armax has quit IRC05:37
*** tej has joined #openstack-meeting-305:54
*** piet has quit IRC05:54
*** vgridnev has joined #openstack-meeting-305:58
*** tej has quit IRC05:59
*** ivar-lazzaro has joined #openstack-meeting-306:00
*** rossella_s has quit IRC06:03
*** rossella_s has joined #openstack-meeting-306:03
*** markvoelker has joined #openstack-meeting-306:04
*** shwetaap1 has quit IRC06:12
*** bpokorny has quit IRC06:22
*** hdaniel has joined #openstack-meeting-306:27
*** markvoelker has quit IRC06:34
*** woodster_ has quit IRC06:36
*** vgridnev has quit IRC06:43
*** ivar-lazzaro has quit IRC06:52
*** ivar-lazzaro has joined #openstack-meeting-306:53
*** vgridnev has joined #openstack-meeting-306:55
*** tej has joined #openstack-meeting-306:56
*** vishwanathj has quit IRC07:00
*** tej has quit IRC07:00
*** lekha|away is now known as lekha07:03
*** sc68cal has quit IRC07:03
*** vgridnev has quit IRC07:10
*** baojg has joined #openstack-meeting-307:13
*** vgridnev has joined #openstack-meeting-307:18
*** ivar-lazzaro has quit IRC07:20
*** baojg has quit IRC07:35
*** baojg has joined #openstack-meeting-307:35
*** jtomasek has joined #openstack-meeting-307:36
*** mrmartin has joined #openstack-meeting-307:36
*** amotoki has joined #openstack-meeting-307:38
*** baojg has quit IRC07:42
*** numans has quit IRC07:48
*** baojg has joined #openstack-meeting-307:55
*** tej has joined #openstack-meeting-307:57
*** nkrinner has joined #openstack-meeting-307:59
*** tej has quit IRC08:02
*** vgridnev has quit IRC08:06
*** nate_gone has joined #openstack-meeting-308:07
*** nate_gone is now known as njohnston08:08
*** mkovacik has joined #openstack-meeting-308:17
*** mickeys has joined #openstack-meeting-308:18
*** jlanoux has joined #openstack-meeting-308:25
*** mickeys has quit IRC08:25
*** jed56 has joined #openstack-meeting-308:26
*** nkrinner has quit IRC08:26
*** nkrinner has joined #openstack-meeting-308:32
*** dedery has joined #openstack-meeting-308:41
*** e0ne has joined #openstack-meeting-308:42
*** mrmartin has quit IRC08:43
*** mkovacik_ has joined #openstack-meeting-308:44
*** amotoki has quit IRC08:45
*** irenab_ has joined #openstack-meeting-308:46
*** matrohon has joined #openstack-meeting-308:46
*** numans has joined #openstack-meeting-308:48
*** alex_xu_ has joined #openstack-meeting-308:49
*** nkrinner has quit IRC08:52
*** mkovacik has quit IRC08:52
*** jtomasek has quit IRC08:52
*** alex_xu has quit IRC08:52
*** irenab has quit IRC08:52
*** irenab_ is now known as irenab08:52
*** nkrinner has joined #openstack-meeting-308:57
*** jtomasek has joined #openstack-meeting-308:57
*** itxaka has joined #openstack-meeting-308:59
*** fawadkhaliq has quit IRC08:59
*** tej has joined #openstack-meeting-308:59
*** mbound has joined #openstack-meeting-309:02
*** bmotz has joined #openstack-meeting-309:03
*** tej has quit IRC09:03
*** safchain has joined #openstack-meeting-309:04
*** mrmartin has joined #openstack-meeting-309:06
*** ihrachys has joined #openstack-meeting-309:07
*** reedip has quit IRC09:14
*** mrmartin has quit IRC09:18
*** vgridnev has joined #openstack-meeting-309:25
*** eliqiao_ has quit IRC09:29
*** markvoelker has joined #openstack-meeting-309:31
*** sheeprine has quit IRC09:33
*** sheeprine has joined #openstack-meeting-309:35
*** eliqiao_ has joined #openstack-meeting-309:35
*** markvoelker has quit IRC09:36
*** mrmartin has joined #openstack-meeting-309:39
*** Poornima has joined #openstack-meeting-309:43
*** neiljerram has joined #openstack-meeting-309:46
*** andymaier has joined #openstack-meeting-309:50
*** andymaier has quit IRC09:56
*** baojg_ has joined #openstack-meeting-309:58
*** baojg has quit IRC09:58
*** tej has joined #openstack-meeting-310:00
*** rossella_s has quit IRC10:03
*** reed_ has joined #openstack-meeting-310:03
*** rossella_s has joined #openstack-meeting-310:03
*** vgridnev has quit IRC10:03
*** tej has quit IRC10:05
*** vgridnev has joined #openstack-meeting-310:08
*** vgridnev has quit IRC10:09
*** yamamoto has quit IRC10:10
*** yamamoto has joined #openstack-meeting-310:10
*** vgridnev has joined #openstack-meeting-310:11
*** vgridnev has quit IRC10:12
*** vgridnev has joined #openstack-meeting-310:12
*** vgridnev has quit IRC10:13
*** kzaitsev_mb has joined #openstack-meeting-310:14
*** vgridnev has joined #openstack-meeting-310:15
*** tellesnobrega_af is now known as tellesnobrega10:19
*** matrohon has quit IRC10:26
*** vgridnev has quit IRC10:34
*** yamamoto has quit IRC10:38
*** itxaka_ has joined #openstack-meeting-310:41
*** Poornima has quit IRC10:41
*** itxaka_ has quit IRC10:41
*** itxaka has quit IRC10:41
*** itxaka has joined #openstack-meeting-310:41
*** salv-orlando has joined #openstack-meeting-310:42
*** vgridnev has joined #openstack-meeting-310:42
*** salv-orl_ has quit IRC10:45
*** vgridnev has quit IRC10:45
*** vgridnev has joined #openstack-meeting-310:46
*** dims has joined #openstack-meeting-310:48
*** yamamoto has joined #openstack-meeting-310:49
*** yamamoto has quit IRC10:49
*** Poornima has joined #openstack-meeting-310:55
*** Poornima_K has joined #openstack-meeting-310:56
*** Poornima_K has quit IRC10:57
*** tej has joined #openstack-meeting-311:02
*** tellesnobrega is now known as tellesnobrega_af11:06
*** tej has quit IRC11:07
*** alexpilotti has quit IRC11:09
*** baojg_ has quit IRC11:12
*** reed_ has quit IRC11:15
*** baojg has joined #openstack-meeting-311:16
*** fawadkhaliq has joined #openstack-meeting-311:16
*** lazy_prince has joined #openstack-meeting-311:25
*** markvoelker has joined #openstack-meeting-311:32
*** markvoelker has quit IRC11:37
*** Poornima has quit IRC11:39
*** amotoki has joined #openstack-meeting-311:41
*** yamamoto has joined #openstack-meeting-311:50
*** stendulker_ has joined #openstack-meeting-311:55
*** stendulker_ has quit IRC11:55
*** vgridnev has quit IRC11:56
*** vgridnev has joined #openstack-meeting-311:56
*** stendulker has quit IRC11:57
*** yamamoto has quit IRC11:58
*** amotoki has quit IRC12:00
*** amotoki has joined #openstack-meeting-312:03
*** tej has joined #openstack-meeting-312:03
*** kzaitsev_mb has quit IRC12:06
*** tdurakov_ is now known as tdurakov12:07
*** tej has quit IRC12:08
*** reedip has joined #openstack-meeting-312:08
*** ig0r_ has joined #openstack-meeting-312:12
*** hdaniel is now known as hdaniel|afk12:21
*** doug-fish has joined #openstack-meeting-312:29
*** markvoelker has joined #openstack-meeting-312:33
*** markvoelker has quit IRC12:37
*** rtheis has joined #openstack-meeting-312:38
*** dims has quit IRC12:40
*** amotoki has quit IRC12:41
*** baoli has joined #openstack-meeting-312:47
*** baoli_ has joined #openstack-meeting-312:48
*** kzaitsev_mb has joined #openstack-meeting-312:49
*** baoli has quit IRC12:51
*** bmotz has left #openstack-meeting-312:55
*** jaypipes has joined #openstack-meeting-312:56
*** galstrom_zzz is now known as galstrom12:57
*** galstrom is now known as galstrom_zzz13:03
*** tej has joined #openstack-meeting-313:05
*** amotoki has joined #openstack-meeting-313:09
*** tej has quit IRC13:10
*** NobodyCa1 has joined #openstack-meeting-313:18
*** dims has joined #openstack-meeting-313:20
*** jtomasek_ has joined #openstack-meeting-313:20
*** vhoward has joined #openstack-meeting-313:21
*** tej has joined #openstack-meeting-313:22
*** markvoelker has joined #openstack-meeting-313:23
*** kzaitsev_mb has quit IRC13:24
*** NobodyCa1 has quit IRC13:24
*** tosky has joined #openstack-meeting-313:27
*** asahlin has quit IRC13:29
*** asahlin has joined #openstack-meeting-313:30
*** woodster_ has joined #openstack-meeting-313:33
*** jtomasek_ has quit IRC13:37
*** _crobertsrh has joined #openstack-meeting-313:39
*** AndreyPavlov has joined #openstack-meeting-313:45
*** tej has quit IRC13:45
*** tej has joined #openstack-meeting-313:46
*** tej has quit IRC13:47
*** tej has joined #openstack-meeting-313:48
*** pino|work has joined #openstack-meeting-313:49
*** tej has quit IRC13:52
*** DevonBoatwright has joined #openstack-meeting-313:54
*** DevonBoatwright has left #openstack-meeting-313:55
*** kzaitsev_mb has joined #openstack-meeting-313:57
SergeyLukjanovhey sahara folks13:59
elmikohi13:59
*** mionkin has joined #openstack-meeting-313:59
*** esikachev has joined #openstack-meeting-314:00
*** huichun has joined #openstack-meeting-314:00
_crobertsrhhello/14:00
SergeyLukjanov#startmeeting sahara14:00
huichunhello14:00
openstackMeeting started Thu Feb 11 14:00:13 2016 UTC and is due to finish in 60 minutes.  The chair is SergeyLukjanov. 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
esikachevhi!14:00
SergeyLukjanov#chair elmiko14:00
openstackCurrent chairs: SergeyLukjanov elmiko14:00
elmikoo/14:00
SergeyLukjanov(backup)14:00
SergeyLukjanov#link https://wiki.openstack.org/wiki/Meetings/SaharaAgenda14:00
toskyhi14:00
elmikogood idea ;)14:00
NikitaKonovalovo/14:00
mionkinhello14:00
*** alexpilotti has joined #openstack-meeting-314:00
vgridnevo/14:00
AndreyPavlovhi14:00
SergeyLukjanov#topic News / updates14:01
*** openstack changes topic to "News / updates (Meeting topic: sahara)"14:01
_crobertsrhStill looking for reviews on the UI reorg.  https://review.openstack.org/#/c/270478/ will get you all the changes to try out.14:01
elmikoi've been working on api v2, and looking at more security bugs and improvements on our bandit gate14:01
AndreyPavlovi was working on periodic tasks14:02
_crobertsrhIdeally, I'd like to get reviews soon because rebasing them every 20 min for 3 months is not my idea of a fun springtime.14:02
vgridnevWorking on health mostly, there are few changes on review already: https://review.openstack.org/#/q/status:open++branch:master+topic:bp/cluster-verification14:02
_crobertsrhvgridnev:  cool, I can't wait to see that in action14:02
*** rossella_s has quit IRC14:03
*** rossella_s has joined #openstack-meeting-314:03
toskyand the feature freeze is in... 18 days?14:03
sreshetn1ako/14:03
*** _crobertsrh is now known as crobertsrh14:03
*** tmckay has joined #openstack-meeting-314:04
SergeyLukjanovNikitaKonovalov could you please review the UI reorg to land it faster?14:04
tmckayhi folks!14:04
NikitaKonovalovSergeyLukjanov: yes sure14:04
tmckayhttps://review.openstack.org/#/q/owner:tmckay%2540redhat.com+status:open14:04
tmckayplease review :) ^^ some are old14:04
*** julim has quit IRC14:05
*** lazy_prince has quit IRC14:05
tmckayalso, we turned off the mapr gate test in sahara-ci, I have built a mapr image and plan today to figure out why it fails (something wrong in apt-get for oozie)14:05
SergeyLukjanovtmckay ack, thx14:06
tmckay2 more patches for regex searching (job_execution, which has special stuff, and job_binary_internal, which hardly matters I think :) )14:06
tmckayalso, in open discussion, I have an idea for a regex search tweak14:06
tmckayAnd, I fixed #1453953 for job binary internal upload from horizon14:07
tmckayhttps://review.openstack.org/#/c/278027/14:07
*** lazy_prince has joined #openstack-meeting-314:07
*** sheeprine_ has joined #openstack-meeting-314:07
tmckayThis was tried and abandoned a few months ago, but I hit it, so I decided to try to fix it :)14:07
crobertsrhwtg tmckay14:07
tmckaysimple fix, and only the one case that was breaking for me14:07
tmckaythose are all my updates :)  nothing left to say14:08
*** sheeprine has quit IRC14:08
SergeyLukjanov#topic API v2 progress14:09
*** openstack changes topic to "API v2 progress (Meeting topic: sahara)"14:09
SergeyLukjanov#link https://review.openstack.org/#/c/273316/14:09
SergeyLukjanov#link https://wiki.openstack.org/wiki/Sahara/api-v214:09
*** sheeprine_ is now known as sheeprine14:09
*** sheeprine has joined #openstack-meeting-314:09
elmikothanks SergeyLukjanov14:09
elmikojust a quick update, the initial commit is ready for reviews14:10
elmikoand i am adding more content to the wiki page14:10
elmikoonce the initial commit is merged, i'll have more to follow.14:10
elmikoand hopefully there will be a clear workload that others can join in on =)14:10
elmikothat's all from me, unless there are questions about api v214:11
*** zz_dimtruck is now known as dimtruck14:11
SergeyLukjanov#topic Open discussion14:12
*** openstack changes topic to "Open discussion (Meeting topic: sahara)"14:12
*** neelashah has joined #openstack-meeting-314:13
SergeyLukjanovwe have a short agenda for today :)14:13
SergeyLukjanovelmiko thx for the updates on v214:13
*** neelashah has quit IRC14:13
*** reedip has quit IRC14:13
NikitaKonovalovgood news, voting for talks is now open14:13
elmiko\o/14:13
elmikoshould we all throw up links now? ;)14:14
NikitaKonovalovwhy not14:14
elmikohttps://www.openstack.org/summit/austin-2016/vote-for-speakers/presentation/779714:14
crobertsrhheh14:14
elmiko=D14:14
huichunvgridnev:  I have updated suspend EDP job patch according to your reviews  https://review.openstack.org/#/c/201448/14:14
vgridnevok will do review later14:14
huichunvgridnev:  add engine support and cluster check before running job14:15
*** lazy_prince has quit IRC14:15
SergeyLukjanovDeploy OpenStack as containers using Marathon and Mesos -- https://www.openstack.org/summit/austin-2016/vote-for-speakers/Presentation/811314:15
SergeyLukjanovData Processing in OpenStack: The State of the Art in Sahara -- https://www.openstack.org/summit/austin-2016/vote-for-speakers/Presentation/822814:15
SergeyLukjanovArchitecture and Best Practices to Deploy Hadoop and Spark Clusters with Sahara -- https://www.openstack.org/summit/austin-2016/vote-for-speakers/Presentation/868314:15
*** krotscheck_dcm is now known as krotscheck14:15
*** jpomeroy has joined #openstack-meeting-314:15
SergeyLukjanovwould appreciate votes :)14:16
*** mrmartin has quit IRC14:16
elmikoSergeyLukjanov: did you see this one, https://www.openstack.org/summit/austin-2016/vote-for-speakers/presentation/682614:16
elmikocurious if they are using sahara at all14:16
*** lblanchard has joined #openstack-meeting-314:16
NikitaKonovalovI also participate in https://www.openstack.org/summit/austin-2016/vote-for-speakers/Presentation/8683 and https://www.openstack.org/summit/austin-2016/vote-for-speakers/Presentation/868714:16
elmikoi'm guessing that they are not, but i'm curious none-the-less14:17
SergeyLukjanovelmiko no, thx for the link14:17
tmckayokay, so I have an additional idea for regex searching, not sure if it's good or not14:18
tmckayAs you know, we have some fields with regex (name, description, url for example) and some exact match (uuids, version numbers, job types, basically ids and things with defined values)14:19
SergeyLukjanovelmiko I think they are doing bare metal provisioning of mesos or k8s14:19
SergeyLukjanovmost probably k8s14:19
tmckaybut, I was playing yesterday and thought that maybe an OR function on something exact might be nice.  Like job types  "pig|shell"14:20
toskyI have two questions related to sahara-scenario: a) I saw there is a pending request to add a the project sahara-tests to "Sahara Official", is it sahara-scenario that needs to be renamed?14:20
elmikoSergeyLukjanov: ack, thanks14:20
tmckayWhat if you want exact match on more than one thing?14:20
tmckaySo, what do you think about allowing "|" in exact match cases?14:20
elmikotmckay: would we be passing the "|" through the rest api?14:21
tmckayyeah. I tried it yesterday from horizon14:21
*** spzala has joined #openstack-meeting-314:21
elmikoi'm only asking because there has been work in the api-wg on creating a guideline for more complex search queries, i'm trying to find the review now14:22
tmckaythe logic would be "if an exact match field contains an "|", then allow regex but treat the stuff between the |'s as exact matches"14:22
tmckayelmiko, ok. Maybe defer then14:22
tmckayThe current logic is that in general, you do not want to do regex on things like version number (but you might want to search for more than one)14:23
*** DevonBoatwright has joined #openstack-meeting-314:23
*** DevonBoatwright has left #openstack-meeting-314:23
*** ajmiller has joined #openstack-meeting-314:23
tmckayof course, if the spec covers comparators, then you could treat version numbers as actually numbers and not strings, and do ranges like in requirements14:23
elmikoi think the prevailing wisdom from the api gurus, was to separate all search terms and pass them using specific args params in the rest14:23
SergeyLukjanovtosky rename will be tomorrow14:24
elmikotmckay: my only concern would be us building this network of regex-yes/regex-no search fields. it could make it tough for end-users to know when they can use which types of search.14:24
tmckayah, I see. so you may have a field appear multiple times14:24
SergeyLukjanovesikachev ^^ (rename)14:24
toskySergeyLukjanov: ah, good to know, thanks14:24
tmckayelmiko, yes. so far what we have done matchines nova. some fields are exact, others are regex.  Fields will be listed in user docs somewhere (haven't done that yet)14:25
toskynow, second question (input appreciated from you all): as scenario-tests is branchless like tempest, I was thinking that we could move API tempest tests there, outside tempest repository14:25
toskywhat do you think?14:25
toskyif you think it's worth of, I guess I would need a spec14:26
tmckayoh, by the way, there are pep8 errors on tempest tests in sahara on master right now14:26
tmckayI keep seeing them when I check changes. Why is that?14:26
elmikotosky: not a bad idea, imo. i'm curious how we will layer in the v2 tests, is there a separate directory or config for each api version?14:26
toskyelmiko: I don't know, I will check the other projects with multiple APIs14:27
toskybut I suspect it's a solved problem somewhere else14:27
elmikotmckay: on the question of the expanding the regex, i think it's a cool idea but maybe we should generate a spec to fight it out over?14:27
elmikotosky: yea, most likely it is solved. i'm just curious. in general though, i don't have an objection to moving those tests into the scenario repo.14:27
tmckayelmiko, yeah, just looking for initial feedback. If everyone said "No, terrible" I wouldn't bother :)14:27
elmikotmckay: ack14:28
tmckaytosky, ++ I am all for as much local control in the sahara repos as possible14:28
toskyesikachev: what would you think about moving tempest API tests into sahara-tests (using the tempest plugin mechanism of course)?14:28
*** tej has joined #openstack-meeting-314:28
SergeyLukjanovtosky I'm not sure that it'll be working correctly with current way how jobs done14:29
toskySergeyLukjanov: do you mean the jenkins jobs?14:29
*** ajmiller has quit IRC14:30
*** hdaniel|afk is now known as hdaniel14:30
esikachevtosky: tempest tests of sahara is a plugin for tempest not good move them to new repo14:31
tmckayoh, crobertsrh, I had a thought. I think the nova panels have a "*" next to the search items that are regex, and no "*" next to the ones that are exact14:31
toskyesikachev: why not? The alternative is move it into sahara repository, but then it's going to be not branchless14:31
tmckaywhat do you think of that?14:31
crobertsrhI'm all for being consistent with other services14:32
tmckaySo it looks like "Name *" on the filter list14:32
toskyesikachev: the new repo is perfect, as it follows the same life of tempest; if you don't need to run the tests, you just don't run them14:32
SergeyLukjanovtosky yup, jenkins job14:32
tmckayI will double check that that's actually true, but I'm pretty sure I saw it14:32
elmikotmckay, crobertsrh, does horizon have the ability to create those little question mark helper links? (with a hover over explaining what is going on)14:32
toskySergeyLukjanov: they can be easily adapted, we already do it for python-saharaclient tempest (scenario) tests, which are in python-saharaclient repo14:32
tmckaythat would be cool14:33
elmikoregardless of what nova is doing, i think having a hover-over with an explanation would be better14:33
tmckayelmiko, ++14:33
crobertsrhMight be useful as well14:33
SergeyLukjanovtosky if it could be fixed, I would say, I like idea of having tempest in sahara-tests14:34
crobertsrhelmiko:  We can do pretty much anything you can imagine.14:34
crobertsrhWhether or not it "fits" is another issue.14:34
toskySergeyLukjanov: as vgridnev remembers from the last review, even tempest core suggested moving API tests outside tempest core14:35
esikachevSergeyLukjanov: tosky let's do it?14:35
elmikocrobertsrh: i thought maybe the horizon folks had already implemented something like this14:35
toskyesikachev, SergeyLukjanov: do we need a spec, right?14:36
tmckaycrobertsrh, I wouldn't pioneer tooltips unless they are already there. Or, maybe, if you want to be a trailblazer :)14:36
crobertsrhOh, they have "?" with hover that appear in places.  Not sure I've seen it on a table page yet though.14:36
toskyand would it be a candidate for a feature exception?14:36
tosky(as time is running)14:36
SergeyLukjanovtosky spec is good14:36
*** mrmartin has joined #openstack-meeting-314:36
toskyokidoki14:36
*** baojg has quit IRC14:37
*** mrmartin has quit IRC14:38
SergeyLukjanovanything else to discuss today?14:39
elmikonothing from me14:40
tmckaynothing from me14:40
*** neelashah has joined #openstack-meeting-314:40
*** jmckind has joined #openstack-meeting-314:42
elmiko314:44
elmiko214:44
elmiko114:45
elmiko#endmeeting14:45
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:45
openstackMeeting ended Thu Feb 11 14:45:08 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:45
huichunBye14:45
openstackMinutes:        http://eavesdrop.openstack.org/meetings/sahara/2016/sahara.2016-02-11-14.00.html14:45
*** tosky has left #openstack-meeting-314:45
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/sahara/2016/sahara.2016-02-11-14.00.txt14:45
openstackLog:            http://eavesdrop.openstack.org/meetings/sahara/2016/sahara.2016-02-11-14.00.log.html14:45
SergeyLukjanovthx folks14:45
elmikothanks SergeyLukjanov14:45
SergeyLukjanovthx elmiko for closing meeting, I've been trying to find some coffee :) (6:45am now)14:45
elmikoSergeyLukjanov: so early.... good luck with coffee ;)14:46
*** tidwellr has joined #openstack-meeting-314:46
*** mionkin has quit IRC14:46
huichunI am continuing to have Chinese holidays14:47
*** adis has joined #openstack-meeting-314:47
adisneko iz Bosne za razgovor14:47
adisbilo ko14:47
adis???14:47
*** vikram__ has joined #openstack-meeting-314:50
*** adis has quit IRC14:51
*** julim has joined #openstack-meeting-314:52
*** janzian has joined #openstack-meeting-314:55
elmikohuichun: hope you are having a good new year!14:56
huichunThx14:56
*** mlavalle has joined #openstack-meeting-314:56
tidwellrhi14:58
mlavalleo/14:59
tidwellr#startmeeting neutron_l315:00
openstackMeeting started Thu Feb 11 15:00:16 2016 UTC and is due to finish in 60 minutes.  The chair is tidwellr. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: neutron_l3)"15:00
openstackThe meeting name has been set to 'neutron_l3'15:00
* tidwellr lets people file in15:00
vikram__hi15:00
tidwellr#topic Announcements15:01
*** openstack changes topic to "Announcements (Meeting topic: neutron_l3)"15:01
tidwellrMitaka-3 is approaching quickly15:01
carl_baldwinHi15:02
tidwellrAny other announcements?15:02
*** stephen-ma has joined #openstack-meeting-315:02
mlavallethe Neutron mid-cycle in Rochester MN15:03
* neiljerram says hi15:03
mlavallehttps://etherpad.openstack.org/p/neutron-mitaka-midcycle15:03
tidwellryes, lots of good topics being discussed15:03
tidwellrunfortunately I will not be able to make it :(15:04
tidwellrany other announcements?15:04
tidwellr#topic Bugs15:05
*** openstack changes topic to "Bugs (Meeting topic: neutron_l3)"15:05
tidwellr#link https://bugs.launchpad.net/neutron/+bug/147810015:05
openstackLaunchpad bug 1478100 in neutron "DHCP agent scheduler can schedule dnsmasq to an agent without reachability to the network its supposed to serve" [High,In progress] - Assigned to Cedric Brandily (cbrandily)15:05
*** piet has joined #openstack-meeting-315:06
tidwellrany updates or items to discuss on this one?15:07
*** sc68cal has joined #openstack-meeting-315:07
carl_baldwinHas been somewhat starve for review time.15:07
mlavalleJUst that the patchset https://review.openstack.org/#/c/205631/ got a -1 from Garyk. I think CEdric will respond soon15:08
*** rbak has joined #openstack-meeting-315:08
mlavalleactually he already responded15:08
*** jwang_ has joined #openstack-meeting-315:08
*** shwetaap has joined #openstack-meeting-315:09
tidwellrok, anything we need to discuss in this setting?15:09
mlavallenot from me15:10
*** SridarK has quit IRC15:11
tidwellrmlavalle: thanks15:11
tidwellrnext is https://bugs.launchpad.net/neutron/+bug/154309415:11
openstackLaunchpad bug 1543094 in neutron "[Pluggable IPAM] DB exceeded retry limit (RetryRequest) on create_router call" [High,Confirmed] - Assigned to Salvatore Orlando (salvatore-orlando)15:11
*** sdake_ has joined #openstack-meeting-315:11
*** piet has quit IRC15:12
*** crobertsrh has left #openstack-meeting-315:12
*** piet has joined #openstack-meeting-315:12
*** jwang has quit IRC15:12
carl_baldwinLooks like we just wait for salv-orlando to post a fix.15:12
mlavalleyeap15:13
tidwellrok15:13
tidwellralright, moving on15:13
tidwellrthere a couple of IPAM RFE's #link https://bugs.launchpad.net/neutron/+bug/1541895 and #link https://bugs.launchpad.net/neutron/+bug/154051215:14
openstackLaunchpad bug 1541895 in neutron "[RFE] [IPAM] Make IPAM driver a per-subnet pool option" [Wishlist,Confirmed] - Assigned to John Belamaric (jbelamaric)15:14
openstackLaunchpad bug 1540512 in neutron "Host dependent IPAM" [Wishlist,Confirmed]15:14
neiljerramI can provide context for the latter, if helpful15:15
mlavalleI added them yesterday to the agenda. carl_baldwin mentioned a few days ago that we want to track the rfe's now15:15
carl_baldwin:)15:15
tidwellrneiljerram: please go ahead :)15:15
neiljerramOK, interesting situation here.15:16
neiljerramBasic idea is to be able to allocate VM IP addresses in a clustered way - per-host, per-rack or per-pod.15:16
*** sdake_ is now known as sdake15:16
neiljerramMain reason for that is to allow fabric routers to aggregate VM routes - if you're using a routed network implementation.15:17
*** sigmavirus24_awa is now known as sigmavirus2415:17
neiljerramI suggested this as an Outreachy project, and Petra Sargent stepped up there, and hence is now my mentee on this.15:17
neiljerramInterestingly, though, it came to my notice yesterday that the Romana project have already implemented something that looks very like this.15:18
neiljerramBut anyway, questions for this forum....15:18
carl_baldwinneiljerram: Do you have any links to Romana?15:19
neiljerram1. whether it's interesting to do a pluggable IPAM driver for this class of use cases; Carl suggested that the routed networks spec would provide an alternative approach based on the proposed Segments15:19
neiljerramhttps://github.com/romana/networking-romana/blob/master/networking_romana/driver/ipam_romana.py15:19
carl_baldwinneiljerram: I think there is that one significant different between your requirements and those of the routed networks spec.15:20
neiljerram2. if yes, whether there's any part of this that is worth commonizing/upstreaming, and hence for possible inclusion in core Neutron15:20
carl_baldwinneiljerram: namely that your boundaries are soft.15:20
neiljerramcarl_baldwin, yes indeed15:20
*** ig0r_ has quit IRC15:21
carl_baldwinneiljerram: Looking at the spec now, I see that both use cases have deferred port binding in common.15:21
neiljerramcarl_baldwin, yes, and that's a part of the problem that I haven't really tackled at all yet.15:21
carl_baldwin... because you need the host binding information to make the IP allocation.15:21
tidwellrneiljerram: From a BGP perspective I like the idea of being able to aggregate DVR host routes where possible, this sounds like a way we could enable that15:21
carl_baldwinneiljerram: We'll need to figure that one out together.15:21
carl_baldwintidwellr: Good point, when we work floating IPs in to routed networks, this could indeed be useful in that scenario.15:22
neiljerramAnother angle here is our experience of ramping up on the pluggable IPAM driver API...15:23
neiljerramFirst that it's been hard, and secondly that a relatively simple enhancement like this seems to require subclassing lots of classes.15:23
carl_baldwinneiljerram: I notice that your third point in the rfe description is a prerequisite for the first point.15:23
* carl_baldwin doesn't see johnbelemaric around.15:24
neiljerramStrictly no, I think15:24
neiljerramI managed to find a sequence of existing CLI commands that would cause Neutron to allocate a new IP after the host was known15:25
neiljerramStepping back... the reason this RFE exists is because the neutron-specs process requires it.15:26
neiljerramAnd the reason I asked Petra to write a neutron-spec was to be a forum where we could start discussing design with John, Pavel etc.15:27
carl_baldwinneiljerram: Is there a spec up for review?15:27
neiljerramBut as it's not clear that any upstreaming is needed, perhaps I should make that a networking-calico spec instead, and cancel this as a Neutron RFE15:28
neiljerramcarl_baldwin, yes: https://review.openstack.org/#/c/273868/15:28
neiljerramBut currently it doesn't have much more content than the RFE15:28
carl_baldwinneiljerram: Thanks.15:28
carl_baldwinneiljerram: You make some good points.  It sounds like you can make some progress without any upstreaming.  But, I think to do deferred port binding correctly in all cases will require some work in Neutron and Nova.15:29
carl_baldwinCould you document your cli commands that cause Neutron to allocate after the host is known?  Is it just letting Nova create the port?15:30
neiljerramYes, will do.15:31
neiljerramUnfortunately I don't recall the detail right now - it was tricky!15:31
carl_baldwinneiljerram: Thanks.15:31
tidwellrneiljerram: very interesting topic, I have thought a lot about host-aware IPAM, thanks doing more than just thinking!15:31
carl_baldwinneiljerram: I'm going to move the RFE to Triaged to discuss it in an upcoming drivers meeting.15:32
*** AndreyPavlov has quit IRC15:32
neiljerramcarl_baldwin, OK, thanks.15:32
tidwellrneiljerram: anything else you'd like to discuss?15:32
neiljerramNo, thank you.15:32
tidwellralright, moving on15:32
tidwellrnext RFE is #link https://bugs.launchpad.net/neutron/+bug/137003315:33
openstackLaunchpad bug 1370033 in neutron "Admin should be able to manually select the active instance of a HA router" [Wishlist,Triaged] - Assigned to Hong Hui Xiao (xiaohhui)15:33
mlavalletidwellr: I just wanted to draw attention to this one. Seems to have been languishing for some time15:33
*** ajmiller has joined #openstack-meeting-315:33
tidwellrmlavalle: thanks, attention drawn :)15:34
carl_baldwinMore or less, yes.  We may need the rest of the time for other topics though.15:34
tidwellrok, we'll move on then15:34
tidwellr#topic Routed Networks15:35
*** esikachev has left #openstack-meeting-315:35
*** openstack changes topic to "Routed Networks (Meeting topic: neutron_l3)"15:35
tidwellrcarl_baldwin: you have the floor15:35
carl_baldwinI justed wanted to let people know that I'm going to run another meeting to dive in to the details of routed networks.15:35
carl_baldwin#link https://review.openstack.org/#/c/278114/15:36
carl_baldwinWe'll make the decision on the time(s) soon and then I'll worry about why Jenkins is failing and get it merged.15:36
*** woodster_ has quit IRC15:36
carl_baldwinIt is time for the rubber to hit the road.15:36
carl_baldwinAlso, please review the specs15:36
carl_baldwin#link https://review.openstack.org/#/c/225384/15:37
tidwellrok, so we'll start having deeper discussions in that forum15:37
carl_baldwin#link #link https://review.openstack.org/#/c/263898/15:37
carl_baldwintidwellr: Back to you.15:37
tidwellrcarl_baldwin: thanks15:37
tidwellr#topic BGP15:37
*** openstack changes topic to "BGP (Meeting topic: neutron_l3)"15:37
*** piet has quit IRC15:37
tidwellrVikram__: ping15:38
carl_baldwintidwellr: I just rebased your patch due to conflict.15:38
carl_baldwinThe conflict resolution was trivial.15:38
*** FallenPegasus has joined #openstack-meeting-315:38
tidwellrcarl_baldwin: thanks15:39
carl_baldwintidwellr: I'd be happy to continue rebasing the chain if you want to focus on other stuff.15:39
tidwellrcarl_baldwin: thanks for the help, that would be great15:39
tidwellrI think we have a solution to some of the gate issues for now15:40
carl_baldwintidwellr: vikram__ : Be advised that I'll be rebasing the chain.15:40
*** mtanino has joined #openstack-meeting-315:40
carl_baldwinActually, looks like vikram__ has already been working on rebasing.15:41
carl_baldwinI'll pick up where he left off.15:41
tidwellrI'm going to spend some time today testing with the patch sets we have15:41
carl_baldwintidwellr: Great, I'll be reviewing these patches today as my top priority.15:41
tidwellrI want to be sure we can start merging the code that handles centralized routers, the DVR stuff can wait for a minute while we get that moving15:42
*** fawadkhaliq has quit IRC15:42
tidwellrI didn't have anything else, Vikram__?15:43
*** fawadkhaliq has joined #openstack-meeting-315:43
carl_baldwin... or vikram__ ?15:43
carl_baldwinLet's just keep merging!15:44
tidwellr+115:44
tidwellr#topic DNS15:44
*** openstack changes topic to "DNS (Meeting topic: neutron_l3)"15:44
mlavallehi again15:44
tidwellrmlavalle: anything on your mind?15:44
mlavallequick update15:45
mlavallethe Nova side patch is waiting a final +2 https://review.openstack.org/#/c/27157815:45
mlavalleI also added unit tests and a realease note here: https://review.openstack.org/#/c/27730215:45
*** dandruta has joined #openstack-meeting-315:45
mlavalleand finally over the next few days I will be pushing the Networking Guide chapter that covers this topic15:46
mlavalleso, good progress overall15:46
mlavalleany questions?15:46
*** rhochmuth has joined #openstack-meeting-315:47
carl_baldwinmlavalle: Just reading Michael's comment about validation.15:47
mlavallecarl_baldwin: I responded to him15:48
carl_baldwinmlavalle: Are they really validating against the same RFCs?15:48
*** tmckay has quit IRC15:48
mlavallecarl_baldwin: I let myself to be guided by the comment... you don't think so?15:48
*** vahidh has joined #openstack-meeting-315:48
carl_baldwinMaybe I forgot the outcome of the discussion but I still had it in mind that their validation was *slightly* different.15:48
*** pino|work has left #openstack-meeting-315:48
carl_baldwinThough, I agree that it shouldn't be seen as a problem either way.15:49
mlavalleyeah, I agree15:49
*** jlanoux has quit IRC15:49
carl_baldwinBut, now that the discussion is coming back to me.  Maybe my concern is no longer valid.15:49
carl_baldwinI had thought they would allow a name to begin with a digit and we would not.15:50
tidwellrmlavalle: thanks for the update and the great work here15:50
mlavalle:-)15:51
tidwellranything else you'd like to discuss?15:51
mlavalleI'm done15:51
*** cdent has joined #openstack-meeting-315:51
tidwellr#topic Address Scopes15:51
*** openstack changes topic to "Address Scopes (Meeting topic: neutron_l3)"15:51
tidwellrcarl_baldwin: we have address scopes!!!!15:51
carl_baldwinYeah!15:52
*** amotoki has quit IRC15:52
*** dobson has quit IRC15:52
carl_baldwinI need to document now.  I've started but that is a whole other learning curve to climb.15:52
carl_baldwinI didn't make progress as quickly as I wanted to.15:52
mlavalle++15:52
carl_baldwinBut, I blogged with some good technical content that I plan to work in to the docs15:53
carl_baldwin#link http://blog.episodicgenius.com/post/neutron-address-scopes/15:53
tidwellrblogs are how we doc things these days, right? ;)15:54
*** rosmaita has joined #openstack-meeting-315:54
*** njohnston has quit IRC15:55
carl_baldwinDon't let Sam-I-Am hear you say that!15:55
*** HenryG has quit IRC15:55
* tidwellr ducks under the table15:55
mlavalleyeah, tidwellr you are getting yourself in deep trouble :-)15:55
carl_baldwinIt did help me.  There is something about writing a blog post that makes it easier for me to get through.15:56
carl_baldwinAnyway, back to you tidwellr15:56
tidwellrthanks, looks like features are getting buttoned up nicely for Mitaka15:57
tidwellr#topic Open Discussion15:57
*** openstack changes topic to "Open Discussion (Meeting topic: neutron_l3)"15:57
*** gouthamr has joined #openstack-meeting-315:57
* tidwellr begins counting down15:57
mlavalleLOL15:58
tidwellralright, thanks everyone!15:58
mlavallethanks!15:58
*** dan_nguyen has joined #openstack-meeting-315:58
tidwellr#endmeeting15:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:59
openstackMeeting ended Thu Feb 11 15:59:01 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_l3/2016/neutron_l3.2016-02-11-15.00.html15:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_l3/2016/neutron_l3.2016-02-11-15.00.txt15:59
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_l3/2016/neutron_l3.2016-02-11-15.00.log.html15:59
carl_baldwinThanks, all!15:59
*** mlavalle has left #openstack-meeting-315:59
*** janzian has left #openstack-meeting-315:59
*** annegentle_ has joined #openstack-meeting-316:00
*** tidwellr has left #openstack-meeting-316:00
elmiko#startmeeting api wg16:00
openstackMeeting started Thu Feb 11 16:00:40 2016 UTC and is due to finish in 60 minutes.  The chair is elmiko. 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
elmiko#chair cdent etoews16:00
openstackCurrent chairs: cdent elmiko etoews16:00
elmikohi16:00
gouthamrhello o/16:00
etoewshello16:01
cdenthowdy16:01
* elmiko hands mic to etoews 16:01
* etoews drops mic16:01
* cdent was waiting for that16:01
*** HenryG has joined #openstack-meeting-316:02
elmikohaha16:02
elmiko#link https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda16:02
* etoews fumbles about for mic16:02
elmiko#topic previous meeting action items16:02
*** openstack changes topic to "previous meeting action items (Meeting topic: api wg)"16:02
cdentso: we had disco balls and glitter in the service catlog meeting, this meeting has a high bar to meet16:02
annegentle_ha16:02
elmikolol, nice16:02
elmiko#link http://eavesdrop.openstack.org/meetings/api_wg/2016/api_wg.2016-01-28-16.00.html16:02
etoewswell the summit submission is done so +116:03
elmikoso, i got all of mine. the server-side traceback guideline merged today16:03
etoews\o/16:03
elmikohuzzah!16:03
cdentmotion16:03
annegentle_nice!16:04
elmikoit actually got a really solid response since the rework, nicely done jaypipes16:04
etoewsah i haven't reached out directly to the CPLs about the errors guideline but have been working with the magnum team.16:04
elmikocool16:04
etoewsmore on that later (if we get to it)16:04
elmikok16:04
*** mkovacik_ has quit IRC16:04
elmikolet's dig in to the meat and potatoes16:04
elmiko#topic service type vs. project name for use in headers16:04
*** openstack changes topic to "service type vs. project name for use in headers (Meeting topic: api wg)"16:04
elmiko#link http://lists.openstack.org/pipermail/openstack-dev/2016-January/085145.html16:05
*** kzaitsev_mb has quit IRC16:05
elmiko#link http://eavesdrop.openstack.org/meetings/tc/2016/tc.2016-02-02-20.01.log.html#l-26316:05
elmikoetoews16:05
*** dobson has joined #openstack-meeting-316:05
etoewsi managed to read through the email thread yesterday16:05
elmiko\o/16:05
annegentle_that's an accomplishment16:06
cdentthe first three agenda items are all really a piece of the same thing16:06
elmikocdent: yea, pretty much16:06
etoewsya16:06
etoewsi'm in agreement with cdent on that thread fwiw16:06
cdentSo I would be curious to get etoews' reaction to the whole pile16:06
*** stephen-ma has quit IRC16:07
etoews:)16:07
cdent\o/16:07
annegentle_heh there you have it16:07
* etoews warms his hands on the fire in cdent's belly16:07
elmikoso, basically, we should have a registry based on service types and that we should curate it?16:07
*** piet has joined #openstack-meeting-316:07
elmikolol16:07
*** kzaitsev_mb has joined #openstack-meeting-316:07
* cdent has been experiencing a bit of discomfort lately16:08
etoewshold on. let me check something.16:08
*** tellesnobrega_af is now known as tellesnobrega16:08
elmikoor am i jumping ahead?16:08
etoewsi was thinking primarily of this16:08
*** vikram__ has quit IRC16:08
etoews"I think that's pretty weak sauce and we need to take both a more assertive and more aggressive stance with regard to achieving quality and consistency in the APIs[1]. Reaching consistency is the primary mission of the group but consistent crap is still crap and our API consumers deserve better."16:08
elmikook, cool16:09
elmikoand yea, i agree with cdent on this one too. i'm just timid about how we achieve it...16:09
cdentthat statement puts us oh so mildly in conflict with sdague's belly's fire16:09
annegentle_What I keep sensing is "if we had a good API docs site we would have discoverability of conflicts"16:10
cdentIf I understand him correctly he doesn't want us striving for purity for purity's sake at the cost of "breaking" existing things.16:10
annegentle_but can't boil the ocean of course16:10
sdaguecdent: right16:10
sdaguewe did that once16:10
sdagueit was called Nova v3.016:10
sdagueafter two years we had to throw the whole thing out because no one was ever going to drop v2 if we did that16:10
elmikothe real question then becomes, where to draw the line between purity and absurdity16:10
cdentyeah, I think we can find a middle ground16:11
cdentWhat's important to me is that we don't _always_ use precendent as truth16:11
elmikoimo, we have been trying to do that by doing api evaluations before we create guidelines16:11
cdentthere's a lot of stuff that is just wrong16:11
cdentelmiko: yes16:11
elmikoagreed16:11
*** woodster_ has joined #openstack-meeting-316:11
sdagueright, but my particular point here was the 4 characters coming out of the header we being deleted for no real reason than purity16:12
etoewsit's the standard deprecation dance. right it comes down to a question of how long anyone is willing to support previous versions.16:12
sdagueetoews: it's not standard deprecation dance when it comes to APIs16:12
etoewsin what regrad?16:13
sdagueyou can use the original ec2 api as it was in 200616:13
annegentle_heh sdague well.16:13
cdentsdague: I'm not disputing the truth of that, but I guess why we've decided replicating that behavior is a goal?16:13
etoewsright. aws has the willingness (and developer workforce) to more or less indefinitely support apis.16:13
sdagueif we are looking for adoption on the openstack front, compatibility is key16:13
etoewsi'm in full agreement.16:14
annegentle_totally agree, what would change that would be concerning sdague?16:14
sdagueannegentle_: the mailing list post I had16:14
etoewsa v3 is conceivable as long as we're willing to support v2 (ideally indefinitely)16:14
*** vgridnev has quit IRC16:15
sdagueabout changing a header name for no good reason16:15
annegentle_sdague: ah ok16:15
elmikoi'm a little stumped on the whole "remove API_" issue, it makes sense to me to remove it from an outside perspective, but i acknowledge sdague's point as well. it's not clear for me how to draw the line.16:15
sdaguehttp://lists.openstack.org/pipermail/openstack-dev/2016-February/085670.html16:15
annegentle_we're in a different world though where contributors want to have experimental APIs. what can we do about that?16:15
etoewscan we save experimental apis for a bit later?16:16
annegentle_etoews: sure16:16
elmiko+116:16
sdagueyeh, lets sort this one on the microversion spec16:16
annegentle_sdague: so the other side that I see tho is "just cuz nova did it first we all have to agree?"16:17
cdentI feel like etoews has more to say on the general topic. Do you?16:17
sdaguebasically I didn't want gratuitious header change. I agree service type instead of code name is important, but dropping API- is gratuitious16:17
annegentle_sdague: I'm not arguing, I'm pointing out the other view16:17
elmikoannegentle_: yea, that's kinda my question too16:17
etoewslet me start by saying i'm willing to back off on having to remove API-16:17
annegentle_sdague: but I can't tell from reading if it's the four characters or the nova start point?16:17
elmikoetoews: agreed, but i think it makes a good pinata for now16:17
sdagueannegentle_: it's because we have multiple things out in the field that do it.16:18
etoewsbut it really point to what annegentle_ brought up above "just cuz nova did it first we all have to agree?"16:18
sdaguetelling released services you have to break your users needs a real benefit16:18
sdaguenot just cuz someone thinks it's nicer16:18
elmikoi don't feel like we're advocating for a reverse in direction for those who implement it with the API-16:18
elmikowe're trying to forge a new way forward16:19
annegentle_sdague: so, I'm working with SDK devs who are implementing microversions now16:19
sdagueelmiko: so instead you'll have to keep a decoder ring of headers16:19
annegentle_sdague: it's going fine but we are having to explain in one:one conversations. This spec helps immensely of course.16:19
elmikosdague: i feel like we'll have to do that either way, imo it's part of the evolutionary process16:19
sdaguebecause you can't OpenStack-%s-API-Minimum-Version % service16:19
cdent#idea: For future reference resist standardizing on header types with meaingful and changeable identifiers in the header left hand side. Bad for flexibility and bad HTTP.16:19
*** stanzgy_ has quit IRC16:20
sdagueelmiko: see, I feel like this was going to be  OpenStack-%s-API-Minimum-Version % service in the code, which is fine.16:20
elmikointeresting though cdent, how do we write guidelines then?16:20
etoewssdague: nope. step 1. add new header to nova. step 2. remove all documentation on old header. step 3. likely nothing (support both headers server side forever)16:20
sdagueetoews: you *CAN'T* removal all documentat16:21
sdaguethere are clouds out there, publicly deployed, where this is the interface16:21
cdentelmiko: generic left hand side, multi-variant right hand side16:21
sdagueand the other header isn't accepted16:21
sdaguethis is a key part of the bootstrapping16:21
*** vgridnev has joined #openstack-meeting-316:22
elmikocdent: maybe, probably, i'm missing something but how would we avoid the API- no API- question?16:22
cdent(elmiko let's punt on that for a minute)16:22
elmikok16:22
*** vgridnev has quit IRC16:22
cdentsdague: I think part of the thinking here is that the number of user and clouds that don't exist yet are much bigger than those that do16:22
sdaguecdent: that's always the theory16:23
cdenthope, perhaps?16:23
elmikolol16:23
elmikodefinitely hope ;)16:23
sdagueuntil you piss off all your current users and they go elsewhere and take your future users with them16:23
cdent(btw, I'm not really arguing against sdague, just trying to flesh out the concerns)16:23
annegentle_sdague: thing is, we don't have a docs site that can document microversions yet.16:23
elmikosame, i'm not opposed to what sdague is talking about. but i want to better understand the problem space.16:23
cdentgithub keeps changing shit in their api and I haven't left yet?16:23
annegentle_sdague: so to me, and I sound like I'm single minded, the docs space is the problem space.16:24
annegentle_sdague: we can't support without docs16:24
sdagueannegentle_: we also have a docs issue, and I'll agree with that16:24
etoewsit's a significant aspect of it for sure16:24
sdagueannegentle_: we're already supporting it16:24
elmikoannegentle_: agreed to a large extent, having good, *fresh*, api docs help alleviate some of these issues.16:24
sdaguepeople are already writing software using this16:24
sdaguewe're already using it between services today16:24
annegentle_sdague: yes, I talk to them a lot :)16:24
annegentle_sdague: about how hard it is to find out what to do :)16:24
cdent:)16:24
sdagueannegentle_: sure16:25
sdaguebut a huge part of fixing all of that has been held up on getting this base spec sorted out, which is hung up on breaking users that have figured out how to use our stuff16:25
*** jlanoux has joined #openstack-meeting-316:25
sdagueanyway, the point is, in this case, this is a really really critical part of the bootstrapping process. There will be production clouds which don't work with the new header out there for the next 5+ years16:26
cdentI think we have general consensus that we can be flexible abot the -API thing, but the more general issue is still live.16:26
elmikocdent: +116:26
sdagueeven though documentation hasn't fully caught up, when it does, it's important it works for all clouds16:26
sdaguecdent: the more general issue being?16:27
etoewscdent: +116:27
elmikoi'm still struggling to figure out how we guide this process in future16:27
elmikoare we allowed to advise changing the namespace for a header, etc...16:27
elmikodo we need a header registry guideline of some sort?16:27
*** vkmc|midcycle is now known as vkmc16:27
cdentelmiko: no, we need to not promulgate headers easily16:28
elmikoor even a header name guideline, it just feels kind murky to me16:28
cdentthere are much better and correct ways to do http16:28
elmikocdent: ok, interesting. i'd like to hear more about that16:28
*** absubram has joined #openstack-meeting-316:28
elmiko(also, meeting halfway point approaching)16:29
annegentle_is the general issue nova instead of compute? or header names changing generally?16:29
etoewsi've been working with swift metadata lately and the headers are an dumping ground of inconsistency.16:29
cdentit's too late to go back in time, but the correct way to have done microversions could have been content-type parameters or a single headler incidcating microversion with the service type on the rhs16:29
cdentetoews: all bets are off with swift16:29
cdentwe shouldn't even try there16:29
etoewstrue16:29
cdent:(16:29
elmikoannegentle_: my issue was header names in general16:29
annegentle_also swift has over 70 headers and nova has 216:30
elmikocdent: so, are you saying we should back off header advise in general, when possible?16:30
cdentfor existing headers we should advise16:30
notmyname?16:30
cdentand when new ones are proposed we should consider ways to avoid the creation of more headers, or ways to consolidate multiple header propositions under one header16:30
annegentle_we do already advise against the X- naming16:31
elmikocdent: maybe a general header guideline to address some of these thoughts would be helpful?16:31
annegentle_so we are in there doing this as guideance16:31
elmikoannegentle_: right, i was kinda thinking about that16:31
*** bpokorny has joined #openstack-meeting-316:31
annegentle_heh I said swift which is "accio notmyname!"16:31
notmynameheh, yeah16:31
notmynamejust checking IRC before I get on the bus :-)16:31
sdaguecdent: I'm totally open if you'd like to propose content type negotiation as a follow on instead of changing to OpenStack-[Service-Type]-API-Min-Version16:31
*** bpokorny has quit IRC16:31
elmikoi like the idea of capturing the thoughts cdent is talking about, namely alternative to headers and why you would/should use them16:32
sdaguebut I don't think we should go from name -> service type -> something else16:32
cdentI can write up the resist-headers idea16:32
sdaguewe get kind of one correction, and carrying around the 2 things forever16:32
*** bpokorny has joined #openstack-meeting-316:32
sdaguecorrection, then another correction, and that's just churn16:32
cdentsdague: I don't think we should change the mechanics of microversions now, I'm just saying for other headers people might like to come up with there are other ways16:32
*** Swami has joined #openstack-meeting-316:32
sdaguecdent: ok16:32
etoewsthat all sounds reasonable to me.16:32
elmikosdague: agreed, and i'm happy to decide on one direction for the microvers. headers and not changing that (header naming-wise)16:32
cdentso just  name -> service-type16:32
annegentle_sdague: it's only 2 not 7216:33
annegentle_and a pattern16:33
etoewswe actually have a start on header guidelines here http://specs.openstack.org/openstack/api-wg/guidelines/headers.html16:33
sdagueannegentle_: sure, but I'm not using 70 as my success bar :)16:33
annegentle_hell to the no :)16:33
sdaguecdent: ok, I'm fine with that then16:33
cdent#action: cdent writes up his ideas on resist headers16:33
elmikoetoews: yea, i was thinking about capturing the more indepth ideas that cdent is talking about16:33
elmikoshould we talk about the registry then?16:34
*** bpokorny_ has joined #openstack-meeting-316:34
elmikoor get more into naming?16:34
etoewsone sec.16:34
elmikoi feel like we are agreed about the service_type being the choice for naming16:35
etoewsso do we comment on https://review.openstack.org/#/c/243429/4/guidelines/microversion_specification.rst and ask to put API- back in?16:35
elmikosadly, i feel like we have to for consistency sake16:35
cdentI think that's the compromise we reached16:35
annegentle_I ... Uh.16:35
annegentle_an API is a collection of operations?16:35
elmikoi hate to make alex_xu_  go through that again...16:35
annegentle_or is an API a single interface to the service?16:36
annegentle_our precision with this term "API" is odd.16:36
sdagueI think it will be fine, I can respin for him even16:36
sdaguethough, the experimental thing is still the problematic one16:36
annegentle_and honetly to me it's about nova/compute16:36
annegentle_honestly even16:36
elmikoannegentle_: i think the feeling on the review was that adding API- to the header was kind of redundant16:36
annegentle_elmiko: ok wasn't just me then16:36
annegentle_sdague: yeah... that design space without breaking users is really where the conflict lies16:37
*** skath_ has quit IRC16:37
sdaguebecause I *really* don't think we should be endorsing putting experimental things into the APIs, once things are out in the world, they are used16:37
elmikothe main problem with that is that it thrashes the few microversion impls that are actually out there16:37
*** huichun has quit IRC16:37
elmikosdague: i have an issue about the experimental stuff16:37
annegentle_sdague: Me. too.16:37
*** bpokorny has quit IRC16:37
etoewscan we nail down exactly what the action is on moving forward on https://review.openstack.org/#/c/243429/4/guidelines/microversion_specification.rst and who will take that action?16:37
sdagueannegentle_: right, this is just a case where we did it already one way. And the only harm was 4 bytes.16:37
annegentle_four nova bytes or api- four bytes?16:38
elmikoetoews: it sounds like sdague volunteered to adjust the spec by adding API- back in16:38
cdentI concur with elmiko16:38
elmikoannegentle_: api- , as i understand16:38
sdagueelmiko: yes +116:38
*** sergek has quit IRC16:38
annegentle_ok16:38
*** wendar_ has joined #openstack-meeting-316:38
*** dandruta has quit IRC16:38
*** zhenguo_ has quit IRC16:38
*** davidsha has joined #openstack-meeting-316:38
elmiko#action sdage to update https://review.openstack.org/#/c/243429 by adding API- back in16:38
*** tpeoples has quit IRC16:38
etoews#action sdague to16:39
elmikosorry16:39
etoewsoops.16:39
*** toan has quit IRC16:39
annegentle_that Dage guy will be busy16:39
etoewsno no. i meant to delete that and hit enter instead16:39
elmikodo we need an undo on the last one?16:39
*** wendar has quit IRC16:39
*** piet has quit IRC16:39
*** mrmartin has joined #openstack-meeting-316:39
etoewsthanks and let's carry on to a new topic16:39
*** asahlin has quit IRC16:39
cdentwe seemed to be naturally veering into experimental territory or shall we go to registry?16:39
elmikook, experimental apis isn't on the agenda, but i feel like we should discuss16:39
elmikoyea..16:40
*** toan has joined #openstack-meeting-316:40
gouthamr+116:40
etoews#undo16:40
elmiko#topic experimental api inclusion16:40
openstackRemoving item from minutes: <ircmeeting.items.Action object at 0x90811d0>16:40
*** openstack changes topic to "experimental api inclusion (Meeting topic: api wg)"16:40
elmikook, experimental stuffs16:40
*** dtroyer has joined #openstack-meeting-316:40
*** skath_ has joined #openstack-meeting-316:40
*** krtaylor has quit IRC16:40
gouthamr#link: https://review.openstack.org/#/c/273158/16:40
elmikoi like this, because i'm working a new api version for sahara and it helps. but i could live without it16:40
*** armax has joined #openstack-meeting-316:41
elmikoi can also see how having pieces of experimental stuff in a fully production api might be discordant16:41
cdentIt is absoluately critical to the health of openstack that there is a way to make experimental apis available to real users. The mechanism of how that is done is what's up for discussion, right?16:41
*** sergek has joined #openstack-meeting-316:41
elmikocdent: i feel so, but i think sdague has other ideas16:41
* cdent looks at sdague 16:41
* elmiko looks at sdague 16:41
elmiko;)16:41
*** salv-orl_ has joined #openstack-meeting-316:41
etoewsi think one of the reasons we have suboptimal api designs is because openstack projects seemingly have to come to the table with a fully baked api.16:41
*** asahlin has joined #openstack-meeting-316:41
cdentetoews: yeah, my belly wrote about that too. It's a huge problem.16:42
sdagueit feels to me that experimental API should hang off a different endpoint16:42
*** huichun has joined #openstack-meeting-316:42
elmikoand i agree with cdent's position16:42
cdentI'm okay with different endpoint16:42
etoewswithout getting an api infront of users in some beta form that's just not doable.16:42
*** dandruta has joined #openstack-meeting-316:42
elmikoi'm fine with advising different endpoint as well16:42
annegentle_new endpoint ++16:42
gouthamrcdent: yes, before we allow for bad API evolution with the guise of microversions.... Some projects would want APIs for an entire feature to be experimental until they get feedback and the feature stabilizes..16:42
sdaguelike 'compute' is nova API. There could be a 'compute-experimental' that only advertizes experimental resources16:42
elmikobut, i really like the header option too because it forces acknowledgement16:42
etoewsagreed16:43
cdentelmiko: if people are using service catalog to find endpoints, isn't it the same thing?16:43
*** piet has joined #openstack-meeting-316:43
cdentand we want them to use service catalog...16:43
*** tpeoples has joined #openstack-meeting-316:43
sdagueit is a different amount of work16:43
annegentle_there's more acknowledgement from a new entry in the service catalog in my mind16:43
elmikocdent: would the experimental api have a separate entry in the catalog?16:43
* cdent considers making endpoints have opaque urls :)16:43
sdagueand different than bob in IT setting experimental true in their shade fork16:44
*** zhenguo_ has joined #openstack-meeting-316:44
elmikoi'm trying to think from a development standpoint here.16:44
sdagueI also think that experimental in the main API is going to be just like javascript github projects16:44
*** salv-orlando has quit IRC16:44
sdaguemeh, why release, just pull from master16:44
elmikoif i am working on a experimental feature, would i need to adjust the service catalog to acces it?16:44
cdentwhen we say "different endpoint" doesn't that imply a different entry in the catalog?16:44
etoewshow about identifing the experimental nature in the service catalog?16:44
sdaguecdent: yes16:44
elmikosdague: lol!16:44
etoewstype: compute16:45
etoewsbeta: true16:45
elmikocdent: i guess it didn't for me16:45
elmikoi was thinking different endpoint like using /v2/... instead of /v1.1/....16:45
cdentetoews: that came up at summit and was considered...dangerous?16:46
sdagueelmiko: no, this needs to be != existing service types16:46
cdentwhere "that" == "beta: true"16:46
annegentle_can you give the sahara example?16:46
sdagueyeh, that means different things to different people16:46
sdagueright, an example might be helpful16:46
elmikosdague: service catalog would be like, type="data-processing-experimental" ?16:46
sdagueelmiko: yeh16:46
elmikointeresting, and i like it16:46
sdagueand, importantly, that endpoint *should not* include resources in the main API16:47
etoewssuffix is better than a separate field in the structure?16:47
elmikoi definitely agree that driving folks to the service catalog is better than gating through headers16:47
cdentetoews: yeah, because of the lookup process16:47
sdagueetoews: it should not be discoverable as a data-processing endpoint16:47
sdagueit is not16:47
*** mrmartin has quit IRC16:47
elmikook, this makes sense to me16:47
annegentle_"hey I want to do some data processing, whatcha got?"16:48
cdentthis aligns with my growing sense of service catalog uber alles16:48
sdaguerealistically this should be about many many many signals that this bit isn't ready16:48
etoewsah. it's the namespace collision that's the concern. got it.16:48
elmikosdague: service catalog entry and header... ;)16:48
sdagueelmiko: and it doesn't contain the main API resources16:49
elmikoyou have to unlock all the deadbolts16:49
sdagueso you can't just point your app at the other endpoint16:49
elmikosdague: yup, agreed16:49
sdagueyou have to explicitly be calling both16:49
SergeyLukjanov++ for data-processing-experimental16:49
elmikohere's a real world example16:49
etoewsgouthamr: thought?16:49
* elmiko waves at SergeyLukjanov 16:49
etoewsthoughts?16:49
*** piet has quit IRC16:49
elmikowe have old sahara at http://host:port/v1.1/...16:49
elmikowe have new sahara at http://host:port/v2/...16:49
gouthamretoews: I'm still racking my brains about how resource isolation can be achieved.. what if a feature has DB implications..16:50
elmikoservice catalog shows the first for data-processing, the second for data-processing-experimental16:50
elmikodoes that sound right?16:50
annegentle_are we sorta letting teams be bad at API design a little longer? Or is it not really like that?16:50
sdagueelmiko: you could do it that way16:50
* annegentle_ recalls the termie talk in Vancouver was it?16:50
sdaguebut, honestly, I also think that major API revisions are things projects should just not do any more16:50
elmikosdague: why not?16:51
sdaguewe're 3 years into migrating from cinder v1 -> v2, glance v1 -> v2, keystone v2 -> v316:51
etoewsannegentle_: in some sense i guess. give them space/time to figure out better designs without having to worry about backwards compat.16:51
annegentle_sdague: yeah I feel like we don't have that luxury because our users lose16:51
annegentle_sdague: We can be 10 years in and have good user outcomes though.16:51
elmikosdague: fair point, but our api could really use some major overhauls...16:51
annegentle_sdague: it's not a time concern as it is a "does it work well" concern16:51
sdagueelmiko: right, but if you can get to it in steps, that's what microversions let you do16:52
elmikoand following semver, i can't see how to get use there from here16:52
sdaguetrust me, we went down this road in Nova16:52
cdentso... I think we are be far to accepting of what the past has shown and letting us drive decision too much. It should certainly inform, but should not control16:52
sdaguespent 2 years on it16:52
sdaguethen lit it all on fire16:52
elmikohmm16:52
cdentNova is a nightmare of horrible process that should not control the rest of the projects16:52
* elmiko thinks "is sdague predicting my next 2 years"16:52
*** amotoki has joined #openstack-meeting-316:52
sdaguecdent: sure, many things aren't great16:53
*** tellesnobrega is now known as tellesnobrega_af16:53
cdentDesperately unhealthy is nova. Other projects may be better.16:53
sdaguehowever, glance v216:53
cdentyeah, all these "old" projects16:53
sdaguecinder v216:53
sdaguekeystone v316:53
*** kzaitsev_mb has quit IRC16:53
elmikoi feel like we can get away with this in sahara though16:53
sdagueelmiko: sure, maybe16:53
cdentsometimes evolution needs to be revolutionary.16:53
*** kzaitsev_mb has joined #openstack-meeting-316:53
etoewsshow us the way elmiko :)16:53
sdagueno project every has though in openstack16:54
cdentDifferent contexts have different concerns16:54
elmikoi totally understand how migrating nova or keystone might be really tough16:54
elmikoetoews: i'm trying... ;)16:54
elmikook, 5 min left16:54
etoewsi think magnum is looking at a v2 too16:54
elmikoand we are way  off in left field16:54
elmikodo we want to talk registry quickly?16:54
cdentso yeah: we should talk naming registry stuff a little bit16:54
cdentjinx buy me a cooke16:54
etoewsi think it was a necessary detour.16:54
elmiko#topic service type name registry16:54
etoewsya16:54
*** openstack changes topic to "service type name registry (Meeting topic: api wg)"16:54
elmikoetoews: agreed16:54
elmikook, so yes, registry, woo, party-time, excellent!16:55
cdentseque here is that an experimental api should never show up in the service registry...16:55
elmikohaha!16:55
elmikosigh...16:55
* elmiko labels cdent "habitual line-stepper"16:55
*** mrmartin has joined #openstack-meeting-316:56
annegentle_I still want to ask, if we had our docs ducks in a row, would we need this separate registry?16:56
cdentsorry, I like continuity16:56
sdagueannegentle_: yes16:56
elmikoi think yes, if only to help new projects16:56
annegentle_or could the docs site discover / preach truth16:56
sdagueno, yes entirely16:56
annegentle_heh16:56
annegentle_so the service registry is a pre-doc doc16:56
annegentle_lookup list16:56
sdaguecongress grabbed 'policy' as service type16:56
sdaguewhich is just crazy16:57
sdaguewe do need to mitigate "good names" here16:57
*** mickeys has joined #openstack-meeting-316:57
*** krtaylor has joined #openstack-meeting-316:57
*** vishwanathj has joined #openstack-meeting-316:57
sdagueotherwise we preclude future services in openstack16:57
sdaguea registry here is important16:57
annegentle_now, if a team grabs a name and takes on a mission, what if they don't deliver on it?16:57
elmikoi can't remember how the email chain ended, sdague were you planning on generating a spec for the registry or is this something we could work on through the api-wg?16:57
elmikoannegentle_: i liked the idea about checking the registry at regular intervals to drop kruft16:58
sdagueelmiko: I ended with I would create this repo - https://review.openstack.org/#/c/278612/16:58
elmikoalso, cdent's idea about projects only grabbing the name when they acutally *need* it16:58
elmikosdague: oh, awesome!16:58
*** amotoki has quit IRC16:58
sdaguein the service catalog tng group we're sketching basic format16:58
elmikoand thank you =)16:58
annegentle_ok, yeah, the timing is good too. Only take a name when you really have a service running16:58
sdagueand I think we'll just review bits in16:58
annegentle_yeah that was the happy dance party16:59
elmikoannegentle_: right, no squatting16:59
*** nelsnels_ has quit IRC16:59
elmiko1min16:59
sdaguehttp://lists.openstack.org/pipermail/openstack-dev/2016-February/086269.html16:59
elmiko#link https://review.openstack.org/#/c/278612/17:00
etoewsno squatting, no cookie licking17:00
elmikodefinitely no cookie licking lol17:00
*** nelsnelson has joined #openstack-meeting-317:00
elmikook, thanks everybody!17:00
cdentwe're still kind of dancing around the problem of an API needing to be something close to done before being able to be "real" (where real means persisting in the registry and the service catalog)17:00
* cdent takes it to #openstack-sdks17:00
elmikoi'm more on your side with that one cdent17:00
annegentle_cdent: yeah it's about getting better at API design, yep yep17:00
elmikoand yea, we're out of time17:00
elmikotake it top -sdks17:00
elmiko#endmeeting17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:00
openstackMeeting ended Thu Feb 11 17:00:56 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/api_wg/2016/api_wg.2016-02-11-16.00.html17:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/api_wg/2016/api_wg.2016-02-11-16.00.txt17:01
openstackLog:            http://eavesdrop.openstack.org/meetings/api_wg/2016/api_wg.2016-02-11-16.00.log.html17:01
docaedo#startmeeting app-catalog17:01
openstackMeeting started Thu Feb 11 17:01:25 2016 UTC and is due to finish in 60 minutes.  The chair is docaedo. Information about MeetBot at http://wiki.debian.org/MeetBot.17:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:01
*** openstack changes topic to " (Meeting topic: app-catalog)"17:01
openstackThe meeting name has been set to 'app_catalog'17:01
*** cdent has left #openstack-meeting-317:01
docaedoCourtesy ping doug-fish markvan markvan_ kzaitsev_mb kfox111117:01
*** bpokorny_ has quit IRC17:01
markvan_yo!17:01
kzaitsev_mbo/17:01
docaedohello!17:02
*** bpokorny has joined #openstack-meeting-317:02
docaedoPretty light agenda today:17:02
docaedo#link https://wiki.openstack.org/wiki/Meetings/app-catalog17:02
doug-fishhi!17:02
docaedo#topic Status updates17:02
*** openstack changes topic to "Status updates (Meeting topic: app-catalog)"17:02
docaedoOne thing on the agenda for today was the "Fix Create Image angularjs code"17:02
docaedo#link https://review.openstack.org/#/c/251670/17:02
docaedoand that merged (woohoo!) so that's a nice update :)17:02
*** dtroyer has left #openstack-meeting-317:03
docaedooh statusbot, keep up!17:03
markvan_I noticed yesterday is still was not fully working, but looks to be bug17:03
markvan_but the fields are being populated17:03
docaedoAnyway was really glad to see that horizon fix merge - oh you had issues? I ran devstack a few minutes after it got into master and all was good for me17:03
docaedowhat did you run in to?17:04
markvan_the form had incorrectly displayed the kernel and ramdisk fields, which are not used in the qcow2 case17:04
*** huichun has quit IRC17:04
doug-fishmarkvan_: did you open a new bug for that yet?17:05
docaedotrue, I guess I never even notice those fields since I just ignore 'em .. but a logged bug would be good17:05
markvan_naw, was going to hit it again today, that I can open it.17:05
docaedocool thanks17:05
docaedoThe other status update I wanted to bring up:17:06
docaedoHorizon integration tests17:06
docaedo#link https://review.openstack.org/#/c/276440/17:06
*** gouthamr has left #openstack-meeting-317:06
markvan_yup, that should be ready now17:06
docaedomarkvan_: thanks for this! I'll try to review it today, really appreciate your effort17:07
markvan_#link https://review.openstack.org/#/c/276438/17:07
markvan_well, this is just the start, after these get in I can push to actually make it run a valid test.17:07
*** mrmartin has quit IRC17:08
*** tej has quit IRC17:08
docaedoright :) I'm excited for that, it's been something on agenda in the past, and something we've talked about, but it was beyond me to do it and nobody else had time17:08
docaedo(BTW I have to bail in 10 minutes or so, but can pass chair to someone else if we still have a raging debate happening)17:09
docaedoAnyone else have status updates? kzaitsev_mb maybe?17:09
kzaitsev_mbI don17:09
kzaitsev_mbI don't have much =)17:09
docaedokzaitsev_mb: ok17:10
kzaitsev_mbI'm going to update my glare plugin patch today, would add Bundles and work on directory structure17:10
kzaitsev_mbsorry, finger slipped =)17:10
docaedokzaitsev_mb: cool - keep us posted on things, and reach out on the regular channel if/when there's stuff we can look at the help with17:10
kzaitsev_mbafter that — I was planning to work on the scripts, that would install the glare itself on a.o.o =)17:11
docaedokzaitsev_mb: ok, that's going to get somewhat complicated - it'll have to be done via puppet through infra repo,17:11
docaedoand of course will have to deal with DB side of things17:11
*** mrmartin has joined #openstack-meeting-317:12
docaedoso before we even get to that, good plan to make a WIP that installs locally (which we can all do for testing) and work through the kinks17:12
*** sdake has quit IRC17:12
kzaitsev_mbdocaedo: yep, I think I can peek at the way python server was installed, so it shouldn't be too scary =)17:12
kzaitsev_mbdocaedo: do you want me to add, maybe a README how to test it?17:12
docaedokzaitsev_mb: absolutely, that would be great!17:13
*** neiljerram has quit IRC17:13
*** numans has quit IRC17:13
kzaitsev_mbmakes sense indeed. I had a couple of mishaps along the way, so I should document them )17:13
*** e0ne has quit IRC17:14
docaedofor sure, also I think other people wanting to kick the tires on glare would appreciate it, as it will be an easy way to test/experiment17:14
docaedoOK moving on then...17:16
docaedo#topic Open discussion17:16
*** openstack changes topic to "Open discussion (Meeting topic: app-catalog)"17:16
docaedoI don't have anything for open discussion today, but will wait a few minutes for anyone else17:16
*** tellesnobrega_af is now known as tellesnobrega17:18
docaedoI'll give it one more minute, and then we just get to end early17:18
*** nkrinner has quit IRC17:19
docaedoalrighty - thanks everyone, talk to you later!17:20
docaedo#endmeeting17:20
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:20
openstackMeeting ended Thu Feb 11 17:20:16 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:20
openstackMinutes:        http://eavesdrop.openstack.org/meetings/app_catalog/2016/app_catalog.2016-02-11-17.01.html17:20
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/app_catalog/2016/app_catalog.2016-02-11-17.01.txt17:20
openstackLog:            http://eavesdrop.openstack.org/meetings/app_catalog/2016/app_catalog.2016-02-11-17.01.log.html17:20
*** annegentle_ has quit IRC17:26
*** tej has joined #openstack-meeting-317:27
*** tej has quit IRC17:29
*** tej has joined #openstack-meeting-317:29
*** davidsha has quit IRC17:32
*** fawadkhaliq has quit IRC17:33
*** jlanoux has quit IRC17:38
*** itxaka has quit IRC17:39
*** mrmartin has quit IRC17:40
*** cbouch has joined #openstack-meeting-317:44
*** cbouch has quit IRC17:46
*** cbouch has joined #openstack-meeting-317:47
*** dtardivel has joined #openstack-meeting-317:47
*** igordcard has joined #openstack-meeting-317:48
*** mrmartin has joined #openstack-meeting-317:49
*** mrmartin has quit IRC17:54
*** fawadkhaliq has joined #openstack-meeting-317:56
*** longstaff has joined #openstack-meeting-317:57
*** longstaff has left #openstack-meeting-317:59
*** SumitNaiksatam has joined #openstack-meeting-318:00
*** rkukura has joined #openstack-meeting-318:01
*** tbachman has joined #openstack-meeting-318:01
*** ivar-lazzaro has joined #openstack-meeting-318:01
SumitNaiksatamrkukura: tbachman igordcard ivar-lazzaro: hi18:02
rkukurahi18:02
tbachmanSumitNaiksatam: hi!18:02
igordcardhi all18:02
SumitNaiksatam#startmeeting networking_policy18:02
openstackMeeting started Thu Feb 11 18:02:20 2016 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot.18:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:02
*** openstack changes topic to " (Meeting topic: networking_policy)"18:02
openstackThe meeting name has been set to 'networking_policy'18:02
SumitNaiksatam#info agenda https://wiki.openstack.org/wiki/Meetings/GroupBasedPolicy#Feb_11th.2C_4th.2C_201618:02
*** rossella_s has quit IRC18:03
SumitNaiksatam#topic Bugs18:03
*** openstack changes topic to "Bugs (Meeting topic: networking_policy)"18:03
ivar-lazzarohi18:03
*** madhu_ak has joined #openstack-meeting-318:03
*** rossella_s has joined #openstack-meeting-318:03
*** hemanthravi has joined #openstack-meeting-318:03
SumitNaiksatamthe fix for the critical bug which we was reported last week in the UI, is still making its way through the backports18:03
SumitNaiksatamhemanthravi: hi18:04
hemanthravihi18:04
*** songole has joined #openstack-meeting-318:04
SumitNaiksatamother than that i dont see any critical priority pending bugs18:04
SumitNaiksatamsongole: hi18:04
songoleHi SumitNaiksatam18:04
SumitNaiksatamspeak up if anyone has any high priority bugs to discuss18:05
*** kzaitsev_mb has quit IRC18:05
SumitNaiksatam#topic Packaging18:05
*** openstack changes topic to "Packaging (Meeting topic: networking_policy)"18:05
SumitNaiksatamrkukura: still no new releases of the stable branches18:05
SumitNaiksatamsince i noticed that we still seem to be fix some issues in the drivers18:06
rkukuraright, but a bit of news on the RDO front18:06
SumitNaiksatamrkukura: yes, saw the email18:06
SumitNaiksatamplease go ahead18:06
rkukuraThe Red Hat folks are proceeding with setting up our kilo and liberty branches in Delorean18:06
SumitNaiksatamrkukura: nice!18:07
rkukuraSo package builds for RDO on CentOS 7 will be generated on each commit to those branches18:07
tbachmanrkukura: sweet!18:07
rkukuraI believe some CI is done on those as well.18:07
SumitNaiksatamrkukura: ok, that was my question18:08
SumitNaiksatamdo they run a CI, and if so what does it do?18:08
rkukuraThey run tempest smoke tests on the packages. Initially I think this will just verify that installing our packages doesn’t break those tests.18:09
SumitNaiksatamrkukura: ok, that sounds reasonable18:09
rkukuraI think we will need puppet modules integrating GBP with the base RDO install to actually configure GBP18:09
rkukuraThen it should be possible to get additional tests run against the deployment18:10
SumitNaiksatamrkukura: is there a specific time frame by which we need to get this done?18:10
SumitNaiksatamand/or is it a requirement for “certification”?18:10
rkukuraI don’t think this is directly a requirement for vendor product certification that is based on RHEL OSP, not RDO.18:11
SumitNaiksatamrkukura: okay18:12
rkukuraWe do need to make a bit of a commitment though18:12
SumitNaiksatamrkukura: committment to add the puppet modules?18:12
rkukuraOnce GBP is turned on in Delorean, we are obligated to fix issues that show up.18:12
rkukuraI don’t think we are commited to add the puppet modules, at least not yet18:13
rkukuraBut if we commit something that breaks whatver testing is being done with Delorean, we are expected to promptly fix it18:13
rkukuraThere would be automated email notification to the maintainer(s) if something breaks18:14
SumitNaiksatamrkukura: okay18:14
rkukuraRight now, I’m the only maintainer listed. But we should add at least one more to make sure we can always respond quickly18:14
*** mrmartin has joined #openstack-meeting-318:14
SumitNaiksatamrkukura: until there are no tests are not run against GBP, then no GBP modules will get loaded18:14
*** e0ne has joined #openstack-meeting-318:15
SumitNaiksatamrkukura: so the chances that it breaks their tests (say tempest tests for neutron) is pretty slim, right?18:15
rkukuraRight, but it is still possible something could change that prevented RPMs from building or installing, and that would need to be fixed18:15
SumitNaiksatamrkukura: absolutely18:15
*** mrmartin has quit IRC18:15
rkukuraLike dependency issues, etc.18:15
SumitNaiksatamrkukura: right18:16
rkukuraOf course, we will want to enable this for master too as soon as possible18:16
SumitNaiksatamrkukura: yes, since you bring up master18:16
rkukuraWhich I think requires our master to depend on the other projects’ master branches rather than liberty18:16
SumitNaiksatami hit a bit of a speed bump on syncing our master with openstack master18:17
SumitNaiksatamhaving some problems with extension loading in the tests18:17
SumitNaiksatamso i am working on that18:17
SumitNaiksatamone thing to note, all extension definitions should always extend ExtensionDescriptor18:17
rkukuraSumitNaiksatam: I wouldn’t be surprised if something has changed that would require our monkeypaching to be updated18:18
*** songole has quit IRC18:18
SumitNaiksatamrkukura: true, but i have not reached that point yet18:18
rkukuraOK18:18
SumitNaiksatammy thinking was that some of the monkey patching would not be needed any more18:18
rkukurathat would be ideal18:19
SumitNaiksatamour Group_policy_mapping extension was not extending ExtensionDescriptor and that was preventing it from being loaded18:19
SumitNaiksatamthe next problem i am facing is that our tests fail at loading a new extension “router_availability” extension that was just introduced in neutron18:20
SumitNaiksatamideally we should not have to load this extension18:20
*** baoli_ has quit IRC18:20
SumitNaiksatambut the way our UTs are setup its getting into some wierd extension dependency issue18:20
* tbachman wonders if that has to do with our L3 plugin inheriting from DVS18:20
tbachmans/DVS/DVR/18:20
SumitNaiksatamtbachman: good point18:20
SumitNaiksatamtbachman: however, I dont think our UTs use the DVR based extension18:21
tbachmanSumitNaiksatam: ACK18:21
* SumitNaiksatam cant help notice that tbachman also lives in DVS in land, chuckle!!18:21
tbachmanlol18:21
tbachmanSumitNaiksatam: if only I had a nickel for everytime I mis-typed GBP and BGP18:22
SumitNaiksatamso anyone, just wanted to say that i am slowed up on that front18:22
tbachmantoo many TLAs18:22
SumitNaiksatamtbachman: lol!18:22
rkukura;)18:22
SumitNaiksatamso the other thing about sycing up with the master, i am only doing things that will get the UTs and integration tests to pass18:23
rkukuraSumitNaiksatam: Let me know if I can help (although I’ll be on PTO next week)18:23
SumitNaiksatami anticipate that we will have to add follow up patches to incorporate some of the newer “features"18:23
SumitNaiksatamrkukura: yes sure, will definitely ping you when you are available18:23
SumitNaiksatamrkukura: thanks for the update on packaging18:24
rkukuranp18:24
*** piet has joined #openstack-meeting-318:24
SumitNaiksatam#topic Design Specs18:24
*** openstack changes topic to "Design Specs (Meeting topic: networking_policy)"18:24
*** dandruta has quit IRC18:24
SumitNaiksatamQoS #link https://review.openstack.org/#/c/275358/18:24
SumitNaiksatamigordcard: hi18:24
SumitNaiksatami noticed igordcard posted an update on the spec18:25
SumitNaiksatamnot sure if folks got a chance to take a look18:25
SumitNaiksatamif not we can spend a couple of mins reading this section:18:26
SumitNaiksatam#link https://review.openstack.org/#/c/275358/3/specs/mitaka/initial-qos-support.rst18:26
SumitNaiksatamits short18:26
SumitNaiksatami meant “REST API impact” section18:26
igordcardSumitNaiksatam, hi18:26
SumitNaiksatamigordcard: ah you are back18:26
SumitNaiksatamthanks for the updated spec18:26
igordcardSumitNaiksatam, yes I'm here but I'm splitting my attention, unfortunately18:27
SumitNaiksatamigordcard: np18:27
SumitNaiksatamigordcard: so i am leaning towards an abstracted resource definition for QoS in GBP18:27
SumitNaiksatamwhat does the rest of the team think?18:27
*** ihrachys has quit IRC18:28
rkukuraSumitNaiksatam: I think that makes sense18:29
SumitNaiksatamrkukura: okay18:29
SumitNaiksatamany one else have thoughts on this please comment on the review18:29
ivar-lazzaroSumitNaiksatam: will do18:30
SumitNaiksatamigordcard: could you provide a strawman of what the abstracted QoS definition would look like in this spec?18:30
SumitNaiksatamivar-lazzaro: thanks18:30
hemanthraviQoS was one of the actions we had from the start, will go through and post my comments18:30
SumitNaiksatamhemanthravi: ok thanks18:30
igordcardSumitNaiksatam, yes I'll come up with something18:30
SumitNaiksatamigordcard: great thanks!18:30
igordcardSumitNaiksatam, can you leave a comment on the spec with the abstract resource idea?18:30
*** nkrinner has joined #openstack-meeting-318:31
SumitNaiksatamigordcard: ok18:31
*** sdake has joined #openstack-meeting-318:31
SumitNaiksatamnext one, “NFP” #link # https://review.openstack.org/#/c/239743 (we have a new TLA ;-) _18:32
tbachmanSumitNaiksatam: ;)18:32
SumitNaiksatamhemanthravi: thanks for posting the update18:32
SumitNaiksatamhemanthravi: but i dont think the team would have had a change to go through your latest rev18:32
SumitNaiksatam*chance18:32
hemanthraviupdate has most of the structure and the apis, would like to get comments on this once they have a chance to review18:33
SumitNaiksatami had some comments (probably the same as what i had communicated offline) but i did not get a chance to note them18:33
*** zhenguo_ has quit IRC18:33
SumitNaiksatamhemanthravi: is this spec complete at your end, or is it still WIP?18:34
hemanthraviSumitNaiksatam:addressed some of them in the updated one, will respond to the other18:34
*** ivar-lazzaro has quit IRC18:34
SumitNaiksatamhemanthravi: specifically my question in the context of the API definition and data model18:34
hemanthravisome of the api's might change, but i think it'c complete enough to get reviews18:34
SumitNaiksatamhemanthravi: okay18:35
SumitNaiksatamhemanthravi: what is NSD?18:35
*** zhenguo_ has joined #openstack-meeting-318:35
hemanthravinetwork service device18:35
hemanthravifor eg a vm that renders the service18:36
*** mbound has quit IRC18:36
hemanthravii'll add the description in the spec, if it's missing18:36
SumitNaiksatamhemanthravi: okay, i see that you have it defined, sorry did not find that earlier18:36
hemanthraviaddressed that from the last set of comments18:37
*** baoli has joined #openstack-meeting-318:37
SumitNaiksatamany questions for hemanthravi at this point?18:37
*** rosmaita has left #openstack-meeting-318:37
SumitNaiksatamthere was an offline meeting to discuss some of this context, at which most of this team was present18:38
*** ivar-lazzaro has joined #openstack-meeting-318:38
*** jlvillal has quit IRC18:38
SumitNaiksatamhemanthravi: assignees - “Rukhsana Ansari (rukansari)” still valid?18:38
hemanthravii'll change that18:38
hemanthraviafter i check with her18:39
SumitNaiksatamhemanthravi: thanks18:39
*** neiljerram has joined #openstack-meeting-318:39
SumitNaiksatamit will be great to have her contribute18:39
hemanthraviafter everyone had a chance to review, we could do another hangout if reqd18:39
*** jlvillal has joined #openstack-meeting-318:39
hemanthraviSumitNaiksatam:yes18:39
SumitNaiksatamhemanthravi: does “network_service_healthmonitor” have anything to do with the lbaas healthmonitor or is it an independent definition?18:40
*** mrmartin has joined #openstack-meeting-318:40
hemanthravithis is independent of lb18:40
*** neiljerram has quit IRC18:40
SumitNaiksatamhemanthravi: okay18:40
hemanthraviand will apply to any type of service, the impl abstracted by a driver18:40
SumitNaiksatamhemanthravi: okay, the status will be something binary, like UP or DOWN?18:41
hemanthraviyes18:41
SumitNaiksatami can check later if its defined in the spec somewhere18:41
SumitNaiksatamhemanthravi: okay thanks18:41
SumitNaiksatamrequesting everyone in the team to take a look at this revised version of the spec18:42
SumitNaiksatamhemanthravi: should we expect to see WIP implementation patches while we are discussing this spec?18:42
hemanthraviSumitNaiksatam:yes, magesh, ahmed should be submitting patches soon18:43
SumitNaiksatamhemanthravi: okay great, thanks for the update and looking forward to the patches as well18:43
hemanthraviwill go in parallel for some time18:43
*** piet has quit IRC18:43
SumitNaiksatamhemanthravi: cool18:44
SumitNaiksatam#topic Open Discussion18:44
*** openstack changes topic to "Open Discussion (Meeting topic: networking_policy)"18:44
*** safchain has quit IRC18:44
SumitNaiksatamlast week rkukura brought up the topic of Austin Summit submissions18:44
SumitNaiksatamsome of use submitted this:18:45
SumitNaiksatam#link https://www.openstack.org/summit/austin-2016/vote-for-speakers/Presentation/689418:45
SumitNaiksatamas a hands on session18:45
SumitNaiksatamplease vote18:46
SumitNaiksatamanyone submit anything else specific to GBP?18:46
hemanthravihttps://www.openstack.org/summit/austin-2016/vote-for-speakers/Presentation/872418:46
hemanthravivote on this one too18:46
SumitNaiksatamhemanthravi: thanks18:47
hemanthravifew more below18:47
hemanthravihttps://www.openstack.org/summit/austin-2016/vote-for-speakers/Presentation/735918:47
hemanthravihttps://www.openstack.org/summit/austin-2016/vote-for-speakers/Presentation/859518:47
hemanthravifrom a GBP based cloud deployer18:48
*** numans has joined #openstack-meeting-318:48
SumitNaiksatamanything else to discuss today?18:48
* tbachman wonders if his IRC client is stuck18:49
SumitNaiksatamtbachman: we see you18:49
SumitNaiksatamif nothing else, we can wrap up for today!18:49
SumitNaiksatamthanks all for joining18:49
SumitNaiksatambye!18:49
ivar-lazzarobye!18:50
rkukurathanks SumitNaiksatam!18:50
SumitNaiksatam#endmeeting18:50
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:50
hemanthravibye18:50
rkukurabye18:50
*** eliqiao_ has quit IRC18:50
openstackMeeting ended Thu Feb 11 18:50:03 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:50
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_policy/2016/networking_policy.2016-02-11-18.02.html18:50
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_policy/2016/networking_policy.2016-02-11-18.02.txt18:50
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_policy/2016/networking_policy.2016-02-11-18.02.log.html18:50
*** rkukura has left #openstack-meeting-318:50
*** eliqiao_ has joined #openstack-meeting-318:52
*** ivar-lazzaro has quit IRC18:52
*** mrmartin has quit IRC18:53
*** mrmartin has joined #openstack-meeting-318:54
*** amotoki has joined #openstack-meeting-318:55
*** tbachman has quit IRC18:57
*** galstrom_zzz is now known as galstrom18:57
*** tbachman has joined #openstack-meeting-318:58
*** ig0r_ has joined #openstack-meeting-318:58
*** mrmartin has quit IRC18:58
*** amotoki has quit IRC18:59
*** kzaitsev_mb has joined #openstack-meeting-318:59
*** vishwana_ has joined #openstack-meeting-319:00
*** hemanthravi has quit IRC19:01
*** FallenPegasus has quit IRC19:01
*** FallenPegasus has joined #openstack-meeting-319:02
*** ig0r_ has quit IRC19:03
*** vishwanathj has quit IRC19:03
*** tbachman has left #openstack-meeting-319:04
*** iyamahat has quit IRC19:08
*** yamahata has quit IRC19:08
*** ig0r_ has joined #openstack-meeting-319:08
*** fawadkhaliq has quit IRC19:12
*** nelsnels_ has joined #openstack-meeting-319:12
*** nelsnelson has quit IRC19:15
*** shwetaap has quit IRC19:17
*** numans has quit IRC19:19
*** galstrom is now known as galstrom_zzz19:20
*** iyamahat has joined #openstack-meeting-319:27
*** shwetaap has joined #openstack-meeting-319:32
*** AndreyPavlov has joined #openstack-meeting-319:33
*** FallenPe_ has joined #openstack-meeting-319:34
*** cbouch has quit IRC19:35
*** neelashah has quit IRC19:36
*** FallenPegasus has quit IRC19:37
*** ajmiller_ has joined #openstack-meeting-319:44
*** ajmiller has quit IRC19:47
*** ivar-lazzaro has joined #openstack-meeting-319:52
*** dimtruck is now known as zz_dimtruck19:55
*** zz_dimtruck is now known as dimtruck19:55
*** eliqiao_ has quit IRC19:56
*** amotoki has joined #openstack-meeting-319:56
*** neelashah has joined #openstack-meeting-319:56
*** Swami has quit IRC19:57
*** eliqiao_ has joined #openstack-meeting-319:58
*** neelashah has quit IRC20:00
*** amotoki has quit IRC20:00
*** neelashah has joined #openstack-meeting-320:02
*** fawadkhaliq has joined #openstack-meeting-320:02
*** baoli has quit IRC20:03
*** alexpilotti has quit IRC20:03
*** Aish has joined #openstack-meeting-320:05
*** Aish has quit IRC20:06
*** vgridnev has joined #openstack-meeting-320:07
*** dan_nguyen has left #openstack-meeting-320:09
*** iyamahat has quit IRC20:13
*** Aish has joined #openstack-meeting-320:19
*** neelashah1 has joined #openstack-meeting-320:25
*** rhochmuth has quit IRC20:25
*** neelashah has quit IRC20:28
*** fawadkhaliq has quit IRC20:30
*** jtomasek has quit IRC20:31
*** kzaitsev_mb has quit IRC20:32
*** Swami has joined #openstack-meeting-320:33
*** alexpilotti has joined #openstack-meeting-320:35
*** neelashah1 has quit IRC20:37
*** alexpilotti has quit IRC20:40
*** julim has quit IRC20:40
*** madhu_ak_ has joined #openstack-meeting-320:45
*** ivar-lazzaro has quit IRC20:47
*** madhu_ak has quit IRC20:47
*** spzala has quit IRC20:49
*** alexpilotti has joined #openstack-meeting-320:51
*** e0ne has quit IRC20:53
*** alexpilotti has quit IRC20:55
*** iyamahat has joined #openstack-meeting-320:55
*** baoli has joined #openstack-meeting-321:00
*** neelashah has joined #openstack-meeting-321:02
*** DevonBoatwright has joined #openstack-meeting-321:06
*** yamahata has joined #openstack-meeting-321:06
*** ShillaSaebi has joined #openstack-meeting-321:10
*** ihrachys has joined #openstack-meeting-321:11
*** vishwanathj has joined #openstack-meeting-321:13
*** kzaitsev_mb has joined #openstack-meeting-321:14
*** vishwana_ has quit IRC21:15
*** neelashah has quit IRC21:16
*** tej has quit IRC21:17
*** spzala has joined #openstack-meeting-321:19
*** spzala has quit IRC21:19
*** tej has joined #openstack-meeting-321:19
*** ajmiller_ is now known as ajmiller21:26
*** ihrachys has quit IRC21:26
*** ihrachys has joined #openstack-meeting-321:27
DevonBoatwright #startmeeting Ops Guide Specialty Team21:30
DevonBoatwrightHi everyone. I hope I'm doing this correctly. I'm Devon and I work with Shilla in OpenStack community group.21:31
njohnston_o/21:31
DevonBoatwrightThis is my first irc meeting.21:31
njohnston_I don't think you are listed as a chair, only a chair can #startmeeting21:31
*** njohnston_ is now known as njohnston21:32
DevonBoatwrightAh, ok. Shilla requested I begin the meeting21:32
ShillaSaebihello21:33
DevonBoatwrightHey there21:33
ShillaSaebi#startmeeting Ops Guide Specialty Team21:33
openstackMeeting started Thu Feb 11 21:33:22 2016 UTC and is due to finish in 60 minutes.  The chair is ShillaSaebi. Information about MeetBot at http://wiki.debian.org/MeetBot.21:33
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:33
*** openstack changes topic to " (Meeting topic: Ops Guide Specialty Team)"21:33
openstackThe meeting name has been set to 'ops_guide_specialty_team'21:33
njohnstono/21:33
ShillaSaebii had no idea you had to be listed for that to work21:33
ShillaSaebihi everyone21:33
ShillaSaebican we get a roll call?21:33
njohnstonhere21:33
ShillaSaebiok21:34
ShillaSaebiand @DevonBoatwright as well21:34
darrenchere21:34
ShillaSaebianyone else?21:34
ShillaSaebihi Darrenc21:34
darrenchi!21:34
ShillaSaebihow it goes?21:34
ShillaSaebialright so lets go ahead and get started21:34
darrencbusy!21:34
njohnstonAccording to the eavesdrop .ics feed the meeting is next week FYI21:35
darrencoh?21:35
ShillaSaebireally21:35
darrencI was going with the google calendar invite21:35
ShillaSaebii thought it was odd weeks21:35
ShillaSaebi:\21:36
ShillaSaebiyeah same here21:36
ShillaSaebical invite21:36
darrencI don't mind having one today21:36
ShillaSaebias long as were not interfering with another meeting21:36
darrencthere's a few things to discuss21:36
ShillaSaebiwhich is entirely possible21:36
ShillaSaebiDarrenC is that cal invite from you or me21:37
ShillaSaebiwe should cancel it21:37
darrencI think me21:37
ShillaSaebiuse ics so that we get it right21:37
darrencok21:37
ShillaSaebiok awesome21:37
darrencwill do21:37
ShillaSaebiso that will be our first order of business!21:37
vhowardo/21:37
ShillaSaebihi vhoward21:37
vhowardhey guys/gals21:37
ShillaSaebialso can we list others as chairs too?21:37
njohnstonyep21:37
ShillaSaebii had no idea nobody else could start the meeting21:37
ShillaSaebiso im currently at an appointment right now21:38
darrencyeah anyone can21:38
ShillaSaebiwasnt going to make the meeting21:38
njohnstonI can put in a change in the irc-meetings project to add Devon if you like21:38
DevonBoatwrightThanks21:38
vhowardthanks nate21:38
ShillaSaebiso i might drop off in 10-15 min or so21:38
ShillaSaebithanks guys!21:38
ShillaSaebiok so #topic Welcome Devon!21:38
*** MarkAtwood has joined #openstack-meeting-321:39
ShillaSaebiDevon is new to our team, she has been setup with Gerrit and launchpad and has been contributing this week as well21:39
darrencWelcome DevonBoatwright21:39
ShillaSaebishe will be helping us w/the ops and arch guides and were excited to have her21:39
darrenc\o/21:39
ShillaSaebi@darrenc i was wondering if we can update the wiki w/our team members21:40
darrencwill do21:40
ShillaSaebiit seems like we have a lot of ppl listed however no participation21:40
DevonBoatwrightThanks! Excited to be here!21:40
ShillaSaebishould we update the list and start with the members who are participating then do a call for help again?21:40
darrencyeah, I'll edit the list21:40
ShillaSaebimaybe seeing a long list of names makes it seem like we have a full staff21:40
darrencgood idea21:40
ShillaSaebiyeah i noticed that the other day21:40
ShillaSaebiand i thought wow thats a long list of names21:41
ShillaSaebilooks like we have a big team21:41
njohnstonHey, since I am editing the meeting config, shall I change this from biweekly-odd to biweekly-even and make this meeting legit?21:41
ShillaSaebiyes!21:41
ShillaSaebithat works21:41
vhoward+1 on that njohnston:21:41
darrencthanks njohnston21:41
ShillaSaebiso yeah maybe we can start the team list on our wiki from scratch and go from there21:41
njohnstonhttps://review.openstack.org/27927621:42
*** dan_nguyen has joined #openstack-meeting-321:43
ShillaSaebicool thanks Nate that was quick!21:43
*** dan_nguyen has left #openstack-meeting-321:43
njohnstonno time like the present!21:43
ShillaSaebibrb21:44
darrencok edited the team list21:45
ShillaSaebicool just saw it21:48
ShillaSaebilooks much better21:48
ShillaSaebi#topic arch guide21:48
*** openstack changes topic to "arch guide (Meeting topic: Ops Guide Specialty Team)"21:48
ShillaSaebion the agenda, we have: convert tasks to bugs, focus on arch guide21:48
ShillaSaebi#link https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Mitaka21:48
*** neelashah has joined #openstack-meeting-321:49
ShillaSaebithats Monday-Wednesday, March 7-9, 201621:49
darrencyeah so I thought converting those tasks inhttps://wiki.openstack.org/wiki/Architecture_Design_Guide_work_items would give some exposure21:49
darrencto bug*21:49
darrencurrgh bugs*21:49
darrencand might encourage other people to work on them21:50
ShillaSaebiok thats a good call21:50
darrencand fyi, there's a global hackfest happening, so I thought it would be a great opportunity to focus on the arch guide21:50
ShillaSaebi+121:50
darrencsee who we could round up21:50
ShillaSaebimaybe @DevonBoatwright and I can sit together and go through some of this21:50
*** bpokorny has quit IRC21:51
darrencSo i'm going to the Sydney hackfest with a few other writers, and we'll focus on the arch guide21:51
DevonBoatwrightI would love to go through it21:51
ShillaSaebisuweeet21:51
darrencplus there will be some SMEs at the hackfest which could be handy21:51
ShillaSaebiyes!21:51
darrencgreat21:51
ShillaSaebiUSA - New York City (hosted by IBM): https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Mitaka-NewYorkCity21:51
ShillaSaebithis might work for us21:51
ShillaSaebi@njohnston @vhoward what do you guys think?21:52
vhowardyou mean in person or just grabbin' stuff of etherpad21:52
njohnstonvhoward: just what I was wondering :-)21:53
ShillaSaebiin person21:53
ShillaSaebii think thats more effective21:53
ShillaSaebibut thats just my opinion21:53
njohnstonI'll run it up the flagpole21:53
darrencin person for each timezone21:54
vhoward+1 what nate said21:54
ShillaSaebi+1 what nate and vic said21:54
ShillaSaebiheh21:54
ShillaSaebithats a good idea though21:54
vhowardlol shilla we will get with you and come up with a solid list to justify and do our best21:54
ShillaSaebiand 3 weeks out21:54
ShillaSaebiok sounds great21:54
darrenccool, so shall we pull the call out to see who can get involved?21:55
ShillaSaebisure yes21:56
ShillaSaebiops ml and docs ml ?21:56
darrencsounds good21:56
ShillaSaebiok i will take that task on21:56
*** amotoki has joined #openstack-meeting-321:56
darrencand I'll poke a few ppl in APAC21:56
ShillaSaebisounds good21:57
ShillaSaebiawesome21:57
ShillaSaebianything else on that?21:57
darrencI guess the other action item is creating bugs21:58
*** alexpilotti has joined #openstack-meeting-321:58
ShillaSaebiso we'll need people to go through the entire guide21:58
*** sdake has quit IRC21:58
darrencfyi, in each bug we'll need to mention to do in the work arch-guide-draft directory, not arch-guide21:58
ShillaSaebiand find stuff21:58
ShillaSaebisure21:58
ShillaSaebithats fine21:58
darrencand reference the bug number in the work items list21:59
ShillaSaebiwe can work on that too21:59
ShillaSaebisure21:59
darrenccool, I can help with that as well21:59
ShillaSaebior we can use a tag21:59
ShillaSaebiso that we can pull all the bugs up related to the arch guide21:59
darrencgood idea21:59
*** mickeys has left #openstack-meeting-321:59
ShillaSaebiok hows just arch-guide21:59
darrencoh, and mention to tag commits to the blueprint as well22:00
*** nkrinner has quit IRC22:00
darrencsounds good22:00
darrencwell, mention the blueprint in commit messages22:00
*** amotoki has quit IRC22:01
*** sdake has joined #openstack-meeting-322:01
ShillaSaebiok22:01
ShillaSaebithat sounds like a plan22:01
darrencindeed!22:01
*** alexpilotti has quit IRC22:02
*** AndreyPavlov has quit IRC22:02
ShillaSaebiok22:02
ShillaSaebimoving alone22:02
ShillaSaebialong*22:02
ShillaSaebi#topic ops guide22:02
*** openstack changes topic to "ops guide (Meeting topic: Ops Guide Specialty Team)"22:02
ShillaSaebiScope changes before deciding on a revision or new edition22:03
ShillaSaebiso we had an email go out on the ML22:03
*** rossella_s has quit IRC22:03
*** rossella_s has joined #openstack-meeting-322:03
darrencyeah, so it appears everyone wants a new edition or revision22:03
darrencbut I think we need to work out what needs changing or updating to determine whether it is a revision or new edition22:04
darrencI was thinking the ops midcycle would be a great opportunity to do that22:04
darrencand someone on the team could moderate a session22:05
darrencAlex offered, but she missed out on a ticket22:05
*** ajmiller_ has joined #openstack-meeting-322:05
ShillaSaebiyeah im not going to that either22:07
*** katomo has joined #openstack-meeting-322:07
ShillaSaebido we have anyone else thats willing to do that22:07
darrencOne of the ops?22:07
darrencWe could ask on the ops ML22:07
ShillaSaebiok22:08
ShillaSaebiwe can just reply all to the email thread thats already going?22:08
darrencyeah22:08
*** ajmiller has quit IRC22:08
ShillaSaebido we have it listed on the ops meetup etherpad22:08
darrencI did like tom22:08
ShillaSaebiyeah tom is great22:08
*** igordcard has quit IRC22:09
darrenctom's suggestion of everyone posting sticky notes of everything they could think of22:09
ShillaSaebiok22:09
darrencand then collating and grouping them22:09
darrencIt's kind of a good way to look at things with fresh eyes22:10
ShillaSaebiyes definitely22:10
*** rtheis has quit IRC22:10
*** dimtruck is now known as zz_dimtruck22:11
darrencanyway, I think we need to at least finish the arch guide before tackling the ops guide22:12
darrencdoing two books at once is too much22:12
*** ivar-lazzaro has joined #openstack-meeting-322:12
*** ivar-lazzaro has quit IRC22:12
darrencbut it doesn't hurt to start looking scoping changes to the ops guide now22:13
darrencat*22:13
*** ivar-lazzaro has joined #openstack-meeting-322:13
*** rhochmuth has joined #openstack-meeting-322:14
darrencanyone else have any thoughts on this?22:14
katomowhat action is needed for arch guide?22:14
*** ajmiller_ is now known as ajmiller22:14
darrencoh, hi katomo!22:15
katomoI don't know the current status22:15
katomohi darrenc22:15
darrencSorry not sure when you joined the meeting22:15
darrencbut we were discussing converting work items in https://wiki.openstack.org/wiki/Architecture_Design_Guide_work_items to bugs22:16
darrencand focussing on them during the OpenStack hackfest22:16
vhowardso i feel like scoping or listing things in detail is never a bad practice, i really liked the "hear is a managable unit of work sign up for one item"22:16
katomothanks22:17
vhowardhere not hear sigh22:17
*** ivar-lazzaro has quit IRC22:17
ShillaSaebii have to step away22:18
darrencyes, thanks vhoward22:18
ShillaSaebiok if i do the end meeting or can someone else do it22:18
ShillaSaebiDarrenc are you listed as a chair as well?22:19
darrencno, but I can still do it22:19
ShillaSaebiok cool22:19
ShillaSaebiim going to step away22:19
ShillaSaebithanks for everything22:19
ShillaSaebiyou will see an email from Devon or I tomorrow22:19
darrencthanks ShillaSaebi22:19
*** vgridnev has quit IRC22:19
ShillaSaebithanks bye!22:19
*** lblanchard has quit IRC22:20
*** zz_dimtruck is now known as dimtruck22:20
katomobye ShillaSaebi22:20
darrenc, #action create bugs for task listed in https://wiki.openstack.org/wiki/Architecture_Design_Guide_work_items22:21
darrenc#action create bugs for task listed in https://wiki.openstack.org/wiki/Architecture_Design_Guide_work_items22:21
darrencdang that didn't work22:21
katomo:)22:21
darrenc#action Ask on ops ML who can moderate an ops guide session during the ops midcycle22:22
*** dims has quit IRC22:23
darrenc#action Ask on ops and docs ML who can participate in the OS hackfest22:23
katomo#action darrenc create bugs for task listed in https://wiki.openstack.org/wiki/Architecture_Design_Guide_work_items22:23
katomosorry, duplicate... didn't work22:24
*** ShillaSaebi has quit IRC22:24
darrencno worries22:24
*** markvan_ has quit IRC22:24
darrencok moving on22:24
darrenc#topic open discussion22:25
darrencok, I guess you need to be chair for this to work22:25
*** markvan has joined #openstack-meeting-322:25
DevonBoatwrightI think Shilla's intention was that I would be able to fill in for her.22:25
DevonBoatwrightBut I guess I can't yet.22:25
*** markvan has quit IRC22:25
*** Swami has quit IRC22:26
darrencyeah, not until njohnston patch is merged22:26
*** dims has joined #openstack-meeting-322:26
darrencok, anything else to discuss?22:26
katomonothing from me22:27
*** markvan has joined #openstack-meeting-322:27
darrencok, I think we're done22:28
darrenc #endmeeting22:28
darrencdarn22:28
darrencwe can't end the meeting :P22:29
katomothanks, all22:29
darrencthanks everyone!22:29
katomowow22:29
katomo#endmeeting22:29
katomo...22:30
*** DevonBoatwright has left #openstack-meeting-322:30
*** katomo has quit IRC22:31
*** dtardivel has quit IRC22:38
*** tej has quit IRC22:40
*** tej has joined #openstack-meeting-322:40
*** salv-orlando has joined #openstack-meeting-322:42
*** salv-orl_ has quit IRC22:44
*** tej has quit IRC22:45
*** ivar-lazzaro has joined #openstack-meeting-322:47
*** ivar-lazzaro has quit IRC22:48
*** ivar-lazzaro has joined #openstack-meeting-322:49
anteaya#endmeeting22:50
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"22:50
openstackMeeting ended Thu Feb 11 22:50:11 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:50
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ops_guide_specialty_team/2016/ops_guide_specialty_team.2016-02-11-21.33.html22:50
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ops_guide_specialty_team/2016/ops_guide_specialty_team.2016-02-11-21.33.txt22:50
openstackLog:            http://eavesdrop.openstack.org/meetings/ops_guide_specialty_team/2016/ops_guide_specialty_team.2016-02-11-21.33.log.html22:50
*** sdake_ has joined #openstack-meeting-322:54
*** vhoward has quit IRC22:54
*** sdake has quit IRC22:57
*** alexpilotti has joined #openstack-meeting-322:57
*** sigmavirus24 is now known as sigmavirus24_awa22:58
*** bpokorny has joined #openstack-meeting-322:59
*** alexpilotti has quit IRC23:01
*** edleafe has quit IRC23:02
*** jmckind has quit IRC23:02
*** neelashah has quit IRC23:07
*** vishwanathj has quit IRC23:08
*** edleafe has joined #openstack-meeting-323:10
*** shwetaap has quit IRC23:11
*** ihrachys has quit IRC23:11
*** dedery has quit IRC23:13
*** jpomeroy has quit IRC23:24
*** baoli has quit IRC23:33
*** outofmemory is now known as reedip23:36
*** baoli has joined #openstack-meeting-323:36
*** MarkAtwood has quit IRC23:44
*** FallenPe_ has quit IRC23:45
*** Shillasaebi has joined #openstack-meeting-323:51
Shillasaebi#endmeeting23:51
*** dimtruck is now known as zz_dimtruck23:52
*** Shillasaebi is now known as ShillaSaebi23:52
anteayaShillaSaebi: yeah so I ended the meeting23:55
anteayaafter 60 minutes anyone can end the meeting23:55
anteayaprior to that only meeting chairs can end it23:55
anteayathe person who starts the meeting is a chair23:55
anteayaand they can make other people chair by using the #chair command23:56
anteayaso using #chair <nick of other chair>23:56
anteayaalso any whitespace before a command doesn't get parsed23:56
*** absubram has quit IRC23:57
anteayaso the reason the meeting couldn't begin the first time is due to the whitespace before the # in the startmeeting command23:57
*** ShillaSaebi has quit IRC23:57
*** amotoki has joined #openstack-meeting-323:57
anteayaif you have difficulty with meetings in the future do pop into #openstack-infra and let us know so we can helpl23:57
anteayahelp23:57

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