Thursday, 2015-07-16

*** dannywilson has quit IRC00:01
*** padkrish has quit IRC00:02
*** FallenPegasus has quit IRC00:02
*** Sukhdev has quit IRC00:03
*** carl_baldwin has joined #openstack-meeting-400:05
*** sbalukoff has quit IRC00:06
*** padkrish has joined #openstack-meeting-400:09
*** ivar-laz_ has quit IRC00:11
*** ivar-lazzaro has joined #openstack-meeting-400:12
*** carl_baldwin has quit IRC00:12
*** galstrom_zzz is now known as galstrom00:13
*** ivar-laz_ has joined #openstack-meeting-400:18
*** ivar-lazzaro has quit IRC00:22
*** ivar-laz_ has quit IRC00:23
*** padkrish has quit IRC00:23
*** padkrish has joined #openstack-meeting-400:23
*** salv-orlando has quit IRC00:24
*** salv-orlando has joined #openstack-meeting-400:26
*** padkrish has quit IRC00:28
*** britthouser has joined #openstack-meeting-400:28
*** ajmiller has quit IRC00:31
*** ajmiller has joined #openstack-meeting-400:31
*** mitchjameson has quit IRC00:32
*** salv-orlando has quit IRC00:34
*** sballe has quit IRC00:42
*** padkrish has joined #openstack-meeting-400:45
*** padkrish has joined #openstack-meeting-400:46
*** galstrom is now known as galstrom_zzz00:49
*** banix has joined #openstack-meeting-400:50
*** padkrish has quit IRC00:52
*** clif_h has left #openstack-meeting-401:11
*** akwasnie has quit IRC01:11
*** _ody has quit IRC01:12
*** KunalGandhi has joined #openstack-meeting-401:13
*** lazy_prince has joined #openstack-meeting-401:14
*** openstack has joined #openstack-meeting-401:23
*** ChanServ sets mode: +o openstack01:23
*** lazy_prince has quit IRC01:24
*** lazy_prince has joined #openstack-meeting-401:24
*** harshs has quit IRC01:26
*** yamahata has quit IRC01:26
*** mestery_ is now known as mestery01:34
*** xingchao has quit IRC01:34
*** fitoduarte has joined #openstack-meeting-401:36
*** puranamr has joined #openstack-meeting-401:36
*** lazy_prince has quit IRC01:43
*** ivar-lazzaro has joined #openstack-meeting-401:50
*** dims_ has quit IRC01:58
*** puranamr has quit IRC02:03
*** galstrom_zzz is now known as galstrom02:14
*** dims__ has joined #openstack-meeting-402:18
*** puranamr has joined #openstack-meeting-402:18
*** yamamoto has joined #openstack-meeting-402:22
*** markvoelker has quit IRC02:22
*** yamamoto_ has joined #openstack-meeting-402:24
*** yamamoto has quit IRC02:24
*** dims__ has quit IRC02:30
*** yamahata has joined #openstack-meeting-402:34
*** yamahata has quit IRC02:36
*** yamahata has joined #openstack-meeting-402:37
*** puranamr has quit IRC02:40
*** KunalGandhi has quit IRC02:44
*** galstrom is now known as galstrom_zzz02:46
*** Raman has joined #openstack-meeting-402:50
*** ivar-lazzaro has quit IRC02:50
*** yamahata has quit IRC02:50
*** Raman has quit IRC02:51
*** harshs has joined #openstack-meeting-402:51
*** harshs has quit IRC02:52
*** sdake_ has joined #openstack-meeting-402:53
*** sdake has quit IRC02:57
*** harshs has joined #openstack-meeting-402:59
*** harshs has quit IRC02:59
*** harshs has joined #openstack-meeting-402:59
*** harshs has quit IRC02:59
*** bradjones has quit IRC03:14
*** bradjones has joined #openstack-meeting-403:19
*** bradjones has quit IRC03:19
*** bradjones has joined #openstack-meeting-403:19
*** galstrom_zzz is now known as galstrom03:24
*** britthou_ has joined #openstack-meeting-403:30
*** britthouser has quit IRC03:33
*** markvoelker has joined #openstack-meeting-403:33
*** dannywilson has joined #openstack-meeting-403:34
*** markvoelker has quit IRC03:34
*** markvoelker has joined #openstack-meeting-403:34
*** markvoelker_ has joined #openstack-meeting-403:37
*** FallenPegasus has joined #openstack-meeting-403:37
*** lazy_prince has joined #openstack-meeting-403:38
*** markvoelker has quit IRC03:39
*** sweston has quit IRC03:44
*** briancurtin has quit IRC03:45
*** ChrisPriceAB has quit IRC03:45
*** serverascode has quit IRC03:45
*** zhiyan has quit IRC03:45
*** masteinhauser has quit IRC03:46
*** banix has quit IRC03:48
*** dougwig has quit IRC03:50
*** harshs has joined #openstack-meeting-403:50
*** dannywilson has quit IRC03:52
*** dannywilson has joined #openstack-meeting-403:52
*** harshs has quit IRC03:53
*** zhiyan has joined #openstack-meeting-403:54
*** sdake_ has quit IRC03:55
*** mandre has left #openstack-meeting-403:55
*** briancurtin has joined #openstack-meeting-403:56
*** serverascode has joined #openstack-meeting-403:58
*** masteinhauser has joined #openstack-meeting-404:09
*** masteinhauser is now known as Guest247004:09
*** sbalukoff has joined #openstack-meeting-404:11
*** britthouser has joined #openstack-meeting-404:15
*** belmoreira has joined #openstack-meeting-404:16
*** britthou_ has quit IRC04:16
*** sweston has joined #openstack-meeting-404:16
*** lakshmiS has joined #openstack-meeting-404:23
*** yamamoto_ has quit IRC04:23
*** yamamoto has joined #openstack-meeting-404:26
*** belmoreira has quit IRC04:28
*** dougwig has joined #openstack-meeting-404:29
*** ChrisPriceAB has joined #openstack-meeting-404:31
*** KunalGandhi has joined #openstack-meeting-404:32
*** KunalGandhi has quit IRC04:37
*** KunalGandhi has joined #openstack-meeting-404:38
*** irenab has quit IRC04:40
*** markvoelker has joined #openstack-meeting-404:49
*** galstrom is now known as galstrom_zzz04:49
*** markvoelker_ has quit IRC04:53
*** _ody has joined #openstack-meeting-405:06
*** jpekkari has joined #openstack-meeting-405:10
*** _ody has quit IRC05:11
*** killer_prince has joined #openstack-meeting-405:16
*** lazy_prince has quit IRC05:19
*** daneyon has joined #openstack-meeting-405:24
*** vishwana_ has joined #openstack-meeting-405:43
*** irenab has joined #openstack-meeting-405:44
*** Swami has quit IRC05:46
*** vishwanathj has quit IRC05:47
*** fitoduarte has quit IRC05:51
*** puranamr has joined #openstack-meeting-405:55
*** puranamr has quit IRC05:57
*** lakshmiS has quit IRC05:59
*** lazy_prince has joined #openstack-meeting-405:59
*** lakshmiS has joined #openstack-meeting-406:01
*** killer_prince has quit IRC06:02
*** nkrinner_afk is now known as nkrinner06:07
*** kobis has joined #openstack-meeting-406:09
*** Sukhdev has joined #openstack-meeting-406:11
*** bouthors has joined #openstack-meeting-406:15
*** belmoreira has joined #openstack-meeting-406:25
*** puranamr has joined #openstack-meeting-406:26
*** dannywilson has quit IRC06:26
*** jpekkari has quit IRC06:29
*** bouthors has quit IRC06:32
*** jpekkari has joined #openstack-meeting-406:33
*** Sukhdev has quit IRC06:45
*** puranamr has quit IRC06:55
*** KunalGan_ has joined #openstack-meeting-407:01
*** KunalGandhi has quit IRC07:04
*** KunalGan_ has quit IRC07:05
*** _ody has joined #openstack-meeting-407:07
*** _ody has quit IRC07:11
*** evgenyf has joined #openstack-meeting-407:36
*** yamamoto has quit IRC07:47
*** lakshmiS has quit IRC07:53
*** markvoelker has quit IRC08:04
*** armax has quit IRC08:06
*** markvoelker has joined #openstack-meeting-408:11
*** yamamoto has joined #openstack-meeting-408:11
*** markvoelker has quit IRC08:16
*** markvoelker has joined #openstack-meeting-408:17
*** markvoelker has quit IRC08:25
*** markvoelker has joined #openstack-meeting-408:29
*** evgenyf has quit IRC08:30
*** markvoelker has quit IRC08:33
*** markvoelker has joined #openstack-meeting-408:44
*** salv-orlando has joined #openstack-meeting-408:46
*** kobis has quit IRC08:47
*** markvoelker has quit IRC08:48
*** belmoreira has quit IRC08:51
*** markvoelker has joined #openstack-meeting-408:58
*** evgenyf has joined #openstack-meeting-408:58
*** killer_prince has joined #openstack-meeting-409:03
*** markvoelker has quit IRC09:03
*** belmoreira has joined #openstack-meeting-409:05
*** lazy_prince has quit IRC09:06
*** lazy_prince has joined #openstack-meeting-409:07
*** _ody has joined #openstack-meeting-409:08
*** killer_prince has quit IRC09:08
*** zeih has joined #openstack-meeting-409:09
*** _ody has quit IRC09:12
*** numan has joined #openstack-meeting-409:17
*** kobis has joined #openstack-meeting-409:23
johnthetubaguyjokke_: sorry, I can't make a meeting at that time on a wednesday, I am out my brass band practice, wanting to move logging forward, but I just don't have much time right now sadly09:36
*** zeih has quit IRC09:39
*** lazy_prince has quit IRC09:39
*** salv-orlando has quit IRC09:40
*** kent_w has joined #openstack-meeting-409:47
*** xingchao has joined #openstack-meeting-409:53
*** evgenyf has quit IRC10:00
*** kent_w has quit IRC10:05
*** evgenyf has joined #openstack-meeting-410:11
*** lazy_prince has joined #openstack-meeting-410:12
*** Apsu has quit IRC10:15
*** Apsu has joined #openstack-meeting-410:17
*** numan has quit IRC10:20
*** dims_ has joined #openstack-meeting-410:24
jokke_johnthetubaguy: no worries ... there has been multiple requests to change that time anyways, so we setup poll for next week to see if we should have alternative timeslot ... everyone seems to be really busy on this cycle as well10:25
*** xingchao has quit IRC10:31
*** amotoki has joined #openstack-meeting-410:32
*** xingchao has joined #openstack-meeting-410:33
*** dims_ has quit IRC10:39
*** salv-orlando has joined #openstack-meeting-410:40
*** bunting has joined #openstack-meeting-410:41
*** xingchao has quit IRC10:57
*** lakshmiS has joined #openstack-meeting-411:04
*** _ody has joined #openstack-meeting-411:08
*** niwa has joined #openstack-meeting-411:10
*** niwa has left #openstack-meeting-411:13
*** _ody has quit IRC11:13
*** belmoreira has quit IRC11:15
*** sambetts has quit IRC11:21
*** wko has joined #openstack-meeting-411:28
*** wko has quit IRC11:28
*** zeih has joined #openstack-meeting-411:30
*** zeih has joined #openstack-meeting-411:30
TheJuliawin 4311:33
TheJuliadoh11:33
*** venza has joined #openstack-meeting-411:35
*** sambetts has joined #openstack-meeting-411:37
*** belmoreira has joined #openstack-meeting-411:40
*** zeih has quit IRC11:40
*** lazy_prince has quit IRC11:59
*** lazy_prince has joined #openstack-meeting-412:01
*** amotoki has quit IRC12:04
*** venza has quit IRC12:10
*** dims_ has joined #openstack-meeting-412:14
*** harshs has joined #openstack-meeting-412:15
*** nkrinner is now known as nkrinner_afk12:18
*** markvoelker has joined #openstack-meeting-412:29
*** dims_ has quit IRC12:30
*** salv-orlando has quit IRC12:31
*** dims__ has joined #openstack-meeting-412:32
*** harshs has quit IRC12:34
*** markvoelker has quit IRC12:34
*** kobis has quit IRC12:37
*** dims__ has quit IRC12:39
*** markvoelker has joined #openstack-meeting-412:43
*** harshs has joined #openstack-meeting-412:44
*** krtaylor has quit IRC12:44
*** markvoelker has quit IRC12:48
*** iurygregory has left #openstack-meeting-412:48
*** krtaylor has joined #openstack-meeting-412:51
*** salv-orlando has joined #openstack-meeting-412:53
*** jpekkari has quit IRC12:54
*** yamamoto has quit IRC12:54
*** lakshmiS has quit IRC12:56
*** markvoelker has joined #openstack-meeting-412:57
*** zeih has joined #openstack-meeting-413:01
*** markvoelker has quit IRC13:02
*** markvoelker has joined #openstack-meeting-413:05
*** klamath has joined #openstack-meeting-413:05
*** zeih has quit IRC13:06
*** markvoelker_ has joined #openstack-meeting-413:06
*** _ody has joined #openstack-meeting-413:09
*** markvoelker has quit IRC13:10
*** _ody has quit IRC13:14
*** bnemec has joined #openstack-meeting-413:14
*** dims_ has joined #openstack-meeting-413:16
*** Bjoern_ has joined #openstack-meeting-413:19
*** bunting has left #openstack-meeting-413:22
*** gema has left #openstack-meeting-413:24
*** bknudson has joined #openstack-meeting-413:25
*** sdake has joined #openstack-meeting-413:25
*** Guest2470 is now known as masteinhauser13:26
*** kobis has joined #openstack-meeting-413:31
*** xingchao has joined #openstack-meeting-413:32
*** TheIntern has joined #openstack-meeting-413:34
*** yamamoto has joined #openstack-meeting-413:46
*** dshakhray has joined #openstack-meeting-413:47
*** jckasper has quit IRC13:48
*** bunting has joined #openstack-meeting-413:49
*** irenab has quit IRC13:49
*** yamamoto has quit IRC13:51
*** ativelkov has joined #openstack-meeting-413:54
*** wayne__ has joined #openstack-meeting-413:54
*** kent_w has joined #openstack-meeting-413:56
*** bpoulos has joined #openstack-meeting-413:58
*** banix has joined #openstack-meeting-413:59
nikhil_kCourtesy meeting reminder: ativelkov, cpallares, esheffield, flaper87, flwang1, hemanthm, ivasilevskaya, jokke_, kragniz, lakshmiS, mclaren, mfedosin, nikhil_k, Nikolay_St, Olena, pennerc, rosmaita, sigmavirus24, sabari, TravT, zhiyan, pkoniszewski, krykowski, ajayaa, GB21, bpoulos, harshs, abhishekk14:01
*** yamahata has joined #openstack-meeting-414:01
hemanthmo/14:01
mfedosino/14:02
ativelkovo/14:02
jokke_o/14:02
harshso/14:02
dshakhrayo/14:02
nikhil_k#startmeeting glance14:02
openstackMeeting started Thu Jul 16 14:02:18 2015 UTC and is due to finish in 60 minutes.  The chair is nikhil_k. Information about MeetBot at http://wiki.debian.org/MeetBot.14:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:02
*** openstack changes topic to " (Meeting topic: glance)"14:02
openstackThe meeting name has been set to 'glance'14:02
kragnizo/14:02
rosmaitao/14:02
bpouloso/14:02
buntingo/14:02
*** stevelle_ has joined #openstack-meeting-414:02
*** sigmavirus24_awa is now known as sigmavirus2414:02
nikhil_k#info Agenda: https://etherpad.openstack.org/p/glance-team-meeting-agenda14:02
sigmavirus24 o/14:03
ativelkovo/14:03
*** aventerav has joined #openstack-meeting-414:03
nikhil_k#topic Updates14:03
*** openstack changes topic to "Updates (Meeting topic: glance)"14:03
nikhil_k#info Mid-cycles14:04
nikhil_k#info Glance mid-cycle: https://etherpad.openstack.org/p/liberty-glance-mid-cycle-meetup14:04
*** mclaren has joined #openstack-meeting-414:04
*** lakshmiS has joined #openstack-meeting-414:04
nikhil_k#info Other mid-cycles: https://wiki.openstack.org/wiki/Sprints14:04
*** Olena has joined #openstack-meeting-414:04
nikhil_kNova and Horizon are next week, those who plan to attend (or virtually attend)14:05
nikhil_k#info Artifacts Sub-team meeting updates14:05
Olenao/14:05
ativelkovoslo.version_objects commits on review14:06
mfedosinclient's too14:06
ativelkovhttps://review.openstack.org/196041, https://review.openstack.org/19681914:06
ativelkovcommit adopting o.vo in glance - as well: https://review.openstack.org/19879814:06
mfedosinjokke_, you said about experimental branch for the client14:07
ativelkovcreated a doc on V3 open issues: https://etherpad.openstack.org/p/glance-v3-open-issues14:07
mfedosincan you do that?14:07
ativelkov(still in progress of populating)14:07
nikhil_kjokke_: will you or will someone from rel-mgrs will be able to create the feature branch?14:08
ativelkovThere is a good suggestion on refactong V3 code so it's images plugin may run kind-of-on-top-of Images v2 api, thus reusing the existing code14:08
nikhil_k++14:08
ativelkovI'll summarize that suggestion in a separate message to the ML14:08
jokke_I think it just needs to be proposed to the projects where our branches are defined ... I'll figure it out14:08
*** yamamoto has joined #openstack-meeting-414:08
nikhil_kthanks jokke_14:09
nikhil_ksounds like a plan, ativelkov14:09
mfedosinjokke_, thanks14:09
*** yamamoto_ has joined #openstack-meeting-414:09
nikhil_k#info Drivers' team meeting updates14:09
jokke_#action jokke_ propose feature branch for python-glanceclient artifacts work14:09
jokke_ouch sorry ;)14:10
nikhil_kjokke_: sorry :)14:10
nikhil_kThis week we prioritized the specs14:10
nikhil_kA few of them look good and I was waiting to see if someone wants to give last minute feedback after today's meeting14:10
nikhil_kelse we will merge them today14:11
jokke_whoaa :)14:11
*** wxy has joined #openstack-meeting-414:11
mclarennikhil_k: which specs do you hope to merge?14:11
nikhil_k#link http://eavesdrop.openstack.org/meetings/glance_drivers/2015/glance_drivers.2015-07-14-14.01.html14:11
nikhil_kmclaren: point # c14:12
mclarenk, thanks14:12
*** malini has joined #openstack-meeting-414:13
malinigood morning!14:13
nikhil_kAnd this one has code ready and almost agreed upon. The lastest changes from wayne can help it merge #link https://review.openstack.org/#/c/179674/14:13
*** yamamoto has quit IRC14:13
*** wxy_ has joined #openstack-meeting-414:14
*** jwagner_away is now known as jwagner14:14
*** jecarey has joined #openstack-meeting-414:14
nikhil_kI hope no one expects a pre-midcycle virtual meetup this time14:15
nikhil_kThis one is over 3 days so we can plan to schedule sessions to include people from various timezones over video conferencing14:15
jokke_can we open parallel bug with that spec, stating that glanclient does not support the tag metadefs? :P14:15
nikhil_kFor the rest of the day, we will host whiteboardig and informal discussions (face to face time, basically)14:16
jokke_preferably high priority14:16
jokke_so we cab backport that to kilo glanceclient14:16
jokke_/cab/can/14:17
nikhil_kjokke_: Please feel free to and ask it to be added/amended to the spec. It makes sense14:17
nikhil_kumm, that I doubt14:17
*** wxy has quit IRC14:17
jokke_I know, I wish it was that easy :(14:17
nikhil_k:/14:18
nikhil_kMoving on14:18
nikhil_k#topic Should all API changes require a spec ?14:18
*** openstack changes topic to "Should all API changes require a spec ? (Meeting topic: glance)"14:18
nikhil_kWho proposed that?14:18
jokke_looks like it was me14:19
sigmavirus24Not me, but that kind of grooves with the three reviews I added to today's agenda14:19
jokke_but we have been talking about this a bit around14:19
mfedosintoo many specs spoil the broth :)14:19
jokke_so if we streamline our specs process that would aid the documentation and release work when we have clear indication that we have merged something that has changed our APIs14:20
buntingAs someone now to glance, more specs would help very much, when trying to understand what is going on.14:20
*** jwagner is now known as jwagner_away14:21
jokke_I think that should be very much lite version of spec14:21
buntingYeah, a even a lite version would make understanding come much quicker14:22
jokke_and relating to that juis FYI how much I love specs I proposed talk to Tokyo summit with topic "Specs - Taking agility out of agile development" ;)14:22
nikhil_kIt may soon become a must have very soon the way I see it14:22
*** pbourke has quit IRC14:22
* nikhil_k back after irc conn timed out14:22
*** pbourke has joined #openstack-meeting-414:22
nikhil_kcan we add release cycles to that agility discussion?14:23
jokke_nikhil_k: the deadline was last night ;)14:23
nikhil_kpun intented (irc can be hard)14:24
*** markvoelker_ has quit IRC14:24
nikhil_kAPI is gettig a very close attention from those who are pushing the interop capacities to OpenStack APIs14:25
nikhil_kHaving specs is only going to help14:25
sigmavirus24Agreed14:25
jokke_yep ... I think changing the v2 api probably becomes next to impossible after nova starts consuming it14:26
sigmavirus24There are legitimate bugs in the behaviour of our API that we now can't fix because we're afraid of backwards incompatibility14:26
sigmavirus24so14:26
nikhil_kAnyways, I had a very interesting discussion with John Garbutt on this topic yesterday. The way Nova specs is evolving seems to make sense from that(Nova) perspective.14:26
sigmavirus24we need specs, or we need v3 tomorrow =P14:26
sigmavirus24nikhil_k: can you link to how they're evolving?14:26
*** dshakhray has quit IRC14:26
jokke_so can we agree lite spec required for API changes regardless if it is "bug" fix or not?14:27
nikhil_k#info Nova specs evolution: https://wiki.openstack.org/wiki/Nova/Liberty_Release_Schedule14:27
maliniLite specs works! Hate to interrupt, but our lite spec, discussed back in Vancouver is starving for some review: https://review.openstack.org/#/c/194868/14:27
nikhil_k#startvote do we require lite spec for API changes regardless if it is "bug" fix or not ?14:28
openstackBegin voting on: do we require lite spec for API changes regardless if it is "bug" fix or not ? Valid vote options are Yes, No.14:28
openstackVote using '#vote OPTION'. Only your last vote counts.14:28
jokke_#vote yes14:28
rosmaita#vote yes14:28
lakshmiS#vote yes14:28
stevelle_#vote yes14:28
hemanthm#vote yes14:28
nikhil_k#vote yes14:28
mclarenwhat is a lite spec?14:28
*** dshakhray has joined #openstack-meeting-414:28
wayne__#vote no14:29
kragnizspecs make the most sense for API changes, but we'd need to make sure these specs actually move forward14:29
nikhil_k#action nikhil_k : define `light spec` in specs evolution documentation14:29
mfedosin#vote no14:29
hemanthmjokke_: do you have a spec up for proposing lite specs? :)14:29
ativelkov#vote yes14:29
jokke_mclaren: I was planning to propose a template for it if we pass the vote ;)14:29
jokke_hemanthm: almost14:30
malini#vote yes14:30
kragnizwhy not make our speed of dealing with specs faster before we start mandating them for every api change?14:30
bpoulos#vote yes14:30
mfedosindo we need ApiImpact flag then?14:30
wayne__kragniz: +114:30
nikhil_k#endvote14:31
openstackVoted on "do we require lite spec for API changes regardless if it is "bug" fix or not ?" Results are14:31
sigmavirus24mfedosin: we do have an ApiImpact flag14:31
*** jckasper has joined #openstack-meeting-414:31
nikhil_kThat's for the API WG and related parties14:31
malinimfedosin +1 on APIimpact flag, docimpact14:31
sigmavirus24Doesn't mean we can't also use it. Plus having their attention isn't going to hurt14:32
*** rfolco has quit IRC14:32
mfedosinsigmavirus24, maybe just link for 'lite' spec is enough?14:32
nikhil_kSpec would be for everyone to keep track of the API changes and why/how14:32
sigmavirus24Unless we don't want their attention at all in which case, why do we keep asking for it?14:32
jokke_looks like openstack does not know how to count. Yes: 9 No: 214:32
johnthetubaguynikhil_k: yeah, was good to chat, can I help with any context?14:32
nikhil_kThanks for the gist jokke_14:32
johnthetubaguyFWIW, Neutron is trying out a lite spec kind of thing, it might being a process worth copying?14:33
mfedosinI want to explain my concern. This patch changes api https://review.openstack.org/#/c/200980/14:33
mfedosindo we need a spec for it?14:33
nikhil_kjohnthetubaguy: Thanks for the feedback. We are just have a small discussion on when do specs make most sense. Please feel to chime in :)14:33
johnthetubaguyso I think that question is best answered after you get the code merged, and I am not totally joking...14:34
jokke_mfedosin: I'm happy to revert that change if it really changes the behavior of our v1 Images API (which IMHO it does not)14:35
nikhil_kmfedosin: that's a good pointer. I think we need to see if this is being validated at the API level. We can't make a change to v1 at this point14:35
johnthetubaguywhen you have a decision you need to record, mostly to make sure everyone is on the same page, specs work really well, when you need to just see the code to answer a question, you don't want a spec to make that decision14:36
jokke_mfedosin: difference being does it change our api code or does it change our public api14:36
mfedosinjokke_, it does (see my comment), but very slightly14:36
lakshmiSi think spec will make the commiter think about all the things covered in the template  specifically for api related changes and also act as document initially14:36
*** jwagner_away is now known as jwagner14:36
jokke_mfedosin: Jenkins agrees, did not merge ;)14:37
johnthetubaguylakshmiS: yeah, API changes are the only thing we require a spec for in Nova, be it a bug fix or a feature14:37
malinimfedosin -- https://review.openstack.org/#/c/200980/ does not change any API, no spec -- am I missing something,14:37
mclarenSpecs have a reputation for slowing things down, in the case of API changes that actually may not be a bad thing14:37
jokke_malini: read the review comments ... there is pretty valid statement it actually changing the v1 API14:38
mfedosinmalini, before if we put is_public='on' it returned None, but with this patch it becomes True.14:38
johnthetubaguymclaren: +1 it sounds terrible like that, but you really need to sit back and think about the problems the change can cause14:38
jokke_++14:38
sigmavirus24mfedosin: good catch14:38
nikhil_kI think we have had some issue with the DB migration / schema changes in Glance14:39
nikhil_kSome deployments had corruption of data with changes merged in without much context where a spec would be have been really benefitial14:39
mclarento give a concrete example (a bug fix) https://review.openstack.org/#/c/199104 this is the kind of thing we'd define a mini-spec for?14:41
*** malini has quit IRC14:41
sigmavirus24mclaren: I'd say yes14:41
sigmavirus24mclaren: that's the kind of thing that's mildly backwards incompatible14:42
sigmavirus24I think 200980 is mildly backwards incompatible too but in a different way14:42
*** malini has joined #openstack-meeting-414:43
jokke_in that context ... and specifically this mentioned change ... could we please stop doing changes like this just "because oslo" for the bits of the code we have agreed that we fix only criticals as we try to deprecate it14:43
mclarenthe specs would then act as reference for similar future changes, like common law14:43
wxy_'14:43
jokke_I think this is good example of doing "totally harmless" change in benefit of using someone elses reinvented wheel and by that causing a change to API we try to deprecate14:43
*** radez_g0n3 is now known as radez14:44
nikhil_kOk, we need to move on for now.14:46
nikhil_k#topic Reviews, Bugs and Releases14:46
*** openstack changes topic to "Reviews, Bugs and Releases (Meeting topic: glance)"14:46
nikhil_k#link      https://review.openstack.org/19937814:47
sigmavirus24That was me14:47
sigmavirus24This ties in with our micro specs discussion14:47
*** sbalukoff has quit IRC14:47
sigmavirus24That's a tiny change that corrects the behaviour of the API14:47
sigmavirus24And yes, the behaviour they're suggesting is correct.14:48
sigmavirus24That said, it will mean a change in the behaviour which (while again, no one should be relying on it) will be somewhat backwards incompatible14:48
nikhil_kumm, I doubt if this needs to throw a NotFound14:48
nikhil_kthe image exists, data doesn'14:49
sigmavirus24nikhil_k: this is specifically for download14:49
mclarenDoes anyone know what other projects do about this kind of change? As far as I know swift are ultra conservative, but I'm not sure about others, or if there are guidelines anywhere14:49
sigmavirus24mclaren: the API WG hasn't written guidelines for making changes like this14:50
*** carl_baldwin has joined #openstack-meeting-414:50
jokke_sigmavirus24: personally I think that should be their top priority then ;)14:50
sigmavirus24We've discussed it but frequently punted on it to define actual api behavour instead of development behaviour14:50
nikhil_ksigmavirus24: hmm, I see the file bit is NotFound :/14:50
sigmavirus24jokke_: the wg has different goals that are focused on api behaviour more than development of APIs14:50
*** rfolco has joined #openstack-meeting-414:51
sigmavirus24nikhil_k: yeah if you can't find the image data to download, 404 is the least objectionable error code here14:51
*** Vikram has joined #openstack-meeting-414:51
nikhil_kBut it's confusing given we define that a image not in active status doesn't have image data14:51
jokke_sigmavirus24: maybe it should be defcores priority then as they are driving ultra concervatism towards stable apis14:51
sigmavirus24jokke_: or just an openstack-spec14:52
jokke_and current behavior is that we return 204, which IMO is correct. The image exists, it does not have content14:52
sigmavirus24perhaps written by defcore members, but put in place for openstack14:52
nikhil_k#link https://review.openstack.org/#/c/199104/14:52
nikhil_ktrying to move faster in the interest of time14:53
sigmavirus24that one is a review by bunting14:53
*** markvoelker has joined #openstack-meeting-414:53
mclarennova have microversions so I guess you can just bump the version if you fix one of these -- a user can still supply the old version in their request header to continue getting unchanged behaviour (in principle)14:53
sigmavirus24mclaren: and I seem to agree that people probably aren't relying on this, but we'll need an API version bump14:53
jokke_ok, tl;dr will this affect only update?14:54
sigmavirus24I'm not sure if we want to do that14:54
maliniBut no decision was made on https://review.openstack.org/199378 !!14:54
sigmavirus24malini: we don't need to make decisions here14:54
sigmavirus24Just bring the reviews to people's attention14:54
nikhil_kI think we have been trying to bump up the v2 versions when we see changes like these14:55
malinisigmavirus24 -- :-) my first glance IRC meeting, thank you!14:55
nikhil_k#link https://review.openstack.org/#/c/195820/14:56
nikhil_kI looked at that one last week but forgot to comment :/ (while in the middle of a meeting)14:56
mclarennikhil_k: yes, but my understanding is that in glance the version is just informational, whereas in nova you can send the old version in a header to get 'guaranteed' unchanged behaviour14:56
nikhil_kmclaren: I think we may soon have to move towards that. Once we know more from the DefCore team in the late july.14:57
jokke_yes, we just inform that we have different api versions, they do not make it backwards compatible14:57
nikhil_kWe just need to agree on a stable API and then establish a pattern for micro=version upgrades for the following years14:57
mclarennikhil_k: ok, interesting. I wonder if that's a big amount of work...14:58
* nikhil_k shrugs14:58
sigmavirus24nikhil_k: that last link is more of a "I'd like more people to look at this"14:58
sigmavirus24That looks like an important change that wayne__ needs to move through for metadefs to function appropriately and so far, very few people are reviewing it14:58
jokke_wayne__: do we have other options than change that?14:58
nikhil_kThanks sigmavirus24 , it would be nice to get diverse reviews on that on specifically14:59
sigmavirus24jokke_: do you have suggestions for how to fix database problems other than with a migration?14:59
nikhil_kI agree that models should have been changes, so shoud have been for images+image-members14:59
nikhil_kso +2 from me on that proposal14:59
nikhil_kchanged*15:00
wayne__jokke_: change the need for unique constraints?15:00
jokke_sigmavirus24: I do not do databases, that's why I asked ... because if we do not have other options, then I'm in favor to do it now rather than later ;)15:00
nikhil_kOk, we can roll over a couple of mins15:00
nikhil_kAs I am chairing the next meeting :P15:00
lakshmiS:)15:00
nikhil_k#info python-glanceclient release 0.17.2 https://review.openstack.org/#/c/202559/ && https://review.openstack.org/20256415:00
nikhil_kjokke_: was that you?15:00
jokke_yes15:01
jokke_the release management team is working with nifty way to do lib releases15:01
* nikhil_k like15:01
wayne__I don't know any other way to do it that would ensure the uniqueness of the data.15:01
nikhil_kkragniz: what's news on glance_store release 0.7.0 ?15:01
*** daneyon_ has joined #openstack-meeting-415:02
jokke_there is new repo where the releases are yaml docs, you request a new release by changing the correlated file with new version number and change id you'd like to tag15:02
kragnizhaypo's been asking for a new release for a while15:02
nikhil_kI guess you and haypo have the answer above15:02
kragnizanyone have any problems with releasing what's currently in head?15:02
sigmavirus24we're over time15:02
jokke_wayne__: fair enough ... as said in that case I'm in favor without understanding the details what's going on at that change ;)15:02
nikhil_ksigmavirus24: thanks for pointing that out.15:02
sigmavirus24let's move to #openstack-glance15:03
sigmavirus24#openstack-searchlight is supposed to be meeting now15:03
jokke_yeah ... thanks all15:03
kragnizthanks15:03
nikhil_kThanks all for joining15:03
mfedosinthanks15:03
nikhil_k#endmeeting15:03
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:03
openstackMeeting ended Thu Jul 16 15:03:22 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:03
openstackMinutes:        http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-07-16-14.02.html15:03
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-07-16-14.02.txt15:03
openstackLog:            http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-07-16-14.02.log.html15:03
wayne__I hope other's will at least test with glance-manage db_upgrade 4215:03
nikhil_k#startmeeting openstack search15:03
openstackMeeting started Thu Jul 16 15:03:37 2015 UTC and is due to finish in 60 minutes.  The chair is nikhil_k. Information about MeetBot at http://wiki.debian.org/MeetBot.15:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:03
*** openstack changes topic to " (Meeting topic: openstack search)"15:03
openstackThe meeting name has been set to 'openstack_search'15:03
*** Olena has quit IRC15:03
*** kent_w has left #openstack-meeting-415:03
nikhil_k#topic roll call and agenda15:03
*** openstack changes topic to "roll call and agenda (Meeting topic: openstack search)"15:03
*** bpoulos has left #openstack-meeting-415:04
*** sjmc7 has joined #openstack-meeting-415:04
lakshmiSo/15:04
sjmc7o/15:04
kragnizo/15:04
rosmaitao/15:04
nikhil_k#link https://etherpad.openstack.org/p/search-team-meeting-agenda15:04
*** wxy_ has quit IRC15:04
*** daneyon has quit IRC15:04
*** kobis has quit IRC15:05
*** bunting has quit IRC15:05
nikhil_k#topic Updates15:05
*** openstack changes topic to "Updates (Meeting topic: openstack search)"15:05
*** dshakhray has quit IRC15:05
*** wayne____ has joined #openstack-meeting-415:06
*** ativelkov has left #openstack-meeting-415:06
nikhil_kThe webinar video that describes plans for liberty and accomplishments for kilo is out on the openstack foundation you tube channel.15:06
sjmc7ah yes, travis mentioned that15:06
nikhil_k#info Horizon mid-cycle next week https://wiki.openstack.org/wiki/Sprints15:06
nikhil_k#info Nova mid-cycle next week: https://wiki.openstack.org/wiki/Sprints15:07
sjmc7i'll be in FC for the horizon one15:07
*** wayne__ has quit IRC15:07
sjmc7one of the agenda items is to add some support for SL to horizon15:07
nikhil_ksjmc7: I was earlier planning to travel however, things have not permitted to do so.15:07
sjmc7ah, that's a shame15:08
nikhil_kCool15:08
lakshmiSsjmc7: would be great to see Horizon use SL15:08
david-lyle./15:08
* david-lyle apparently has long arms today15:08
nikhil_kCan we plan to collaborate on video next week partially and depending on the schedule we can keep a brainstorming session on searchlight for glance and nova related things during the glance mid-cycle ?15:09
sjmc7yeah15:09
*** blahRus has joined #openstack-meeting-415:09
sjmc7travis' schedule is the one to workaround since he's heavily involved in horizon too15:09
sjmc7but yeah, we can find some time15:09
nikhil_kglance one spreads over 3 days and we should have enough time to schedule different events while accomodating timezone15:10
*** _ody has joined #openstack-meeting-415:10
sjmc7ok. i'm in FC tuesday through friday15:10
*** amotoki has joined #openstack-meeting-415:10
nikhil_kdavid-lyle: I guess we will have to wait on Travis for the remote conn details?15:11
david-lylenikhil_k: they are still in flux15:11
*** sdake has quit IRC15:11
david-lyleprobably vidyo based15:11
nikhil_ksounds good15:12
lakshmiSdavid-lyle: that sounds good15:12
lakshmiSdavid-lyle: is there a link on timings somewhere?15:12
david-lylelakshmiS: yes :)15:12
david-lylelet me locate15:12
david-lyle#link https://docs.google.com/spreadsheets/d/1w0eI6SPCA2IrOyHiEYC2uDO3fbYGzahZRUQSva0UD3Y/edit#gid=178884169215:12
lakshmiSthx15:12
david-lylemost of the time is meant as more of a sprint, but there are a few topics lined up15:13
nikhil_kdavid-lyle: objects to putting that on the wiki https://wiki.openstack.org/wiki/Sprints ?15:13
*** belmoreira has quit IRC15:13
david-lyleI think it bounces through the etherpad version15:13
david-lylebut I can check15:13
nikhil_kPossible Short Hike / Dinner sounds interesting15:14
nikhil_kI was planning one for Glance too15:14
sjmc7we can do that remotely :)15:14
nikhil_kha :)15:14
david-lyleI guess I never completed the wiring15:14
*** sballe has joined #openstack-meeting-415:15
lakshmiSwell travis took us on a supposedly short hike which was enough for us :)15:15
*** _ody has quit IRC15:15
nikhil_k:)15:15
nikhil_kAlso, this basically covers the next topic "Cross Project Updates (nikhil_k, david-lyle?)"15:15
*** stevelle_ has left #openstack-meeting-415:16
nikhil_k#topic Bug review15:16
*** openstack changes topic to "Bug review (Meeting topic: openstack search)"15:16
nikhil_k#link https://bugs.launchpad.net/searchlight15:16
lakshmiShttps://review.openstack.org/#/c/20239215:16
*** dannywilson has joined #openstack-meeting-415:16
lakshmiSI have tested the change in searchlight which works well.15:16
* david-lyle has a working sprint link now15:17
lakshmiSand also made changes to ceilometer to introduce a pool name15:17
sjmc7lakshmiS - i asked on the review, but what's the effect if ceilometer doesn't also add a pool name?15:17
nikhil_kthanks david-lyle !15:17
*** sdake has joined #openstack-meeting-415:17
nikhil_klakshmiS: is the review to ceilometer merged?15:17
lakshmiSsjmc7: without a pool name it defaults to some "default" name15:17
*** dshakhray has joined #openstack-meeting-415:17
lakshmiSceilometer team hasn't responded. there is a weekly IRC meeting going on right now where I will be disussing that topic15:18
sjmc7so your proposed change will still work because there'll be two pools? i'm not familiar with oslo.messaging at all15:18
*** armax has joined #openstack-meeting-415:18
lakshmiSon #openstack-meeting15:18
nikhil_kI think it would be nice to add a Depends On: <Change Id> tag to commit message15:18
sjmc7i can also put you in touch with HP's ceilometer folks if that'd be helpful15:18
lakshmiSany help is appreciated15:18
sjmc7ok. i'll email you after this15:19
lakshmiSi am waiting for the open questions session to discuss it right now on #openstack-meeting15:19
lakshmiSwill update after this meeting15:20
nikhil_kThanks lakshmiS15:20
nikhil_ksjmc7: I think we stalled on the discussion on this bug last week #link https://bugs.launchpad.net/searchlight/+bug/147187815:21
openstackLaunchpad bug 1471878 in OpenStack Search (Searchlight) "Service client auth in listener" [Undecided,New] - Assigned to Steve McLellan (sjmc7)15:21
sjmc7yeah.. i put a review up to address the problem for now15:21
nikhil_kforgot if you had a proposed patch or were we discussing the possible approach15:21
sjmc7there's a BP to discuss better long term solutions15:21
sjmc7https://blueprints.launchpad.net/searchlight/+spec/openstack-client-usage15:22
nikhil_kcool!15:22
nikhil_k#topic Blueprint review15:23
*** openstack changes topic to "Blueprint review (Meeting topic: openstack search)"15:23
nikhil_k#link  https://blueprints.launchpad.net/searchlight/+spec/devstack-plugin15:23
nikhil_kI guess we are waiting on some updates here #link https://review.openstack.org/#/c/197885/15:24
sjmc7the base support is merged; that patch is for keystone v315:24
nikhil_kDoes anyone have objections to cut a release without keystone v3 support?15:26
sjmc7no, unless we'd be the only ones15:26
lakshmiSdoes glance support it?15:26
david-lyleI think that's fine for now15:27
nikhil_kI think the patches for keytsone v3 to client are pending review15:27
* nikhil_k needs to check15:27
sjmc7well, we don't have a client :)15:27
sjmc7i'll try and review the devstack patch today or tomorrow15:28
*** galstrom_zzz is now known as galstrom15:28
nikhil_kSorry the comment was about glance client15:29
nikhil_kand I am not too familiar with keystone v3 updates to devstack for glance15:29
nikhil_k#link https://blueprints.launchpad.net/searchlight/+spec/designate-plugin15:30
nikhil_kI think this just needs some review attention15:31
sjmc7endre's had a patch up since last week. it looks really close now, although i don't have designate running to test it15:31
nikhil_klooks like comments have been addressed15:31
* nikhil_k neither15:31
david-lylewhat's the access model in that patch? it doesn't seem to be gated on anything15:31
sjmc7which one, david-lyle?15:32
david-lylesorry, designate15:32
david-lylejust glancing at it15:32
sjmc7you mean RBAC?15:32
david-lyleis this only population15:32
david-lyleyes, I was referring to RBAC15:33
sjmc7get_rbac_filter in the XYZIndex classes provides rbac filtering15:33
sjmc7we "and" that with whatever the query is15:33
lakshmiSWill be reviewing the RBAC stuff tomorrow on that15:33
david-lylewasn't part of the goal, the plugin providing it's own RBAC?15:34
sjmc7yeah, the plugin does15:34
lakshmiSyes15:34
lakshmiSthats how other plugins are too15:34
lakshmiSsince it specific to each plugin15:34
sjmc7i'm confused :)15:34
david-lyleok, I see it now15:34
david-lylemy fault, I overlooked the method15:35
lakshmiSplugin model only intercepts but takes the rbac queries from plugin15:35
*** blahRus has quit IRC15:35
david-lylebut it just allows global access15:35
david-lyleI'll dig in off line15:35
* david-lyle moves out of the way15:35
sjmc7:)15:35
lakshmiSit has term filter on "project_id"15:35
nikhil_k:)15:35
sjmc7ask in the SL channel once you've had a second look. we may well have overlooked something15:36
nikhil_k#info https://blueprints.launchpad.net/searchlight/+spec/plugin-config-options15:36
nikhil_kI think it makes sense15:36
sjmc7i don't think there's been much movement on that one. i'm in favor of it15:36
sjmc7if only to allow e.g. notification topic parameters15:36
sjmc7ekarlso, did you get anywhere with it?15:37
nikhil_k:)15:37
*** blahRus has joined #openstack-meeting-415:38
nikhil_kHe was not around earlier (at least)15:38
nikhil_kso, we can chat with him offline15:38
sjmc7ok. there are some oddities around the oslo.config/stevedore load order i think15:38
nikhil_ksjmc7: for the separate sections of configs?15:39
sjmc7yeah. but donwe 't need to discuss it here15:40
sjmc7we don't15:40
nikhil_kok, thanks15:40
nikhil_k#info https://blueprints.launchpad.net/searchlight/+spec/nova-instances-plugin15:40
nikhil_kThanks for putting that review up sjmc715:40
sjmc7i put a review up that replicates the summit demo functionality15:40
*** ig0r_ has quit IRC15:40
nikhil_kI had a interesting discussion with Nova PTL on this yday15:40
sjmc7uh oh :)15:40
*** kobis has joined #openstack-meeting-415:40
lakshmiSand..15:41
nikhil_kwell not on the review to say15:41
nikhil_khe was suggesting that we should index only via the API15:41
nikhil_kand not touch the DB15:41
*** dshakhray has quit IRC15:41
nikhil_kbut it really depends on what we want to do15:41
sjmc7we are15:41
sjmc7only using the API15:41
nikhil_khmm, I missed the review completely :/15:42
sjmc7direct database access was something we ruled out for various reasons15:43
nikhil_kbecause I was thinking about other database tables15:43
*** aventerav has quit IRC15:44
nikhil_kI think we have potentially contradictory cases for metadefs and instances15:44
sjmc7ok15:44
nikhil_kinstances are more dynamic and senstive on the DB front15:44
sjmc7that's a shame :)15:44
nikhil_kwhereas metadefs are potentially static entries15:44
*** aventerav has joined #openstack-meeting-415:44
sjmc7right15:45
nikhil_kso a DB direct index on metadef would be really helpful even for images in some cases while for instances it would hurt more than help15:45
sjmc7anything we can't get from the API and/or notifications is going to be tough to work with15:45
nikhil_kThe pitfall is that notifications and admin api can have more info15:45
*** vishwanathj has joined #openstack-meeting-415:45
nikhil_kwhereas the tenant specfic api is going to be rather restrictive15:46
sjmc7well, SL is an admin15:46
sjmc7it's not authing as an ordinary user15:46
nikhil_kthe query won't be though15:46
sjmc7no. so we'll need to restrict fields15:46
*** vishwana_ has quit IRC15:47
sjmc7if there are specific examples then note them on the BP or review; i don't know enough to address this15:47
nikhil_kthanks, I will try to recollect examples.15:49
nikhil_kon another note, I haven't followed up much on metadef indexing but was hoping to have direct db access for that15:49
nikhil_kcalls to glance api would be pretty expensive for re-indexing15:49
sjmc7ok. we need to discuss that. direct DB access is not ideal from a deployment and functionality perspective15:49
nikhil_kand it won't need much restrictions on fields15:50
*** stevelle has joined #openstack-meeting-415:50
nikhil_k(hopefully unless the cloud deployment is supre complicated)15:50
nikhil_kMoving on for now15:51
*** kobis has quit IRC15:51
nikhil_kDo we want to cover all the specs?15:51
*** kobis has joined #openstack-meeting-415:51
nikhil_koops, I meant BPs15:52
sjmc7still want to discuss openstack-client-usage but not necessarily here15:52
lakshmiSI added a new BP for named queries15:52
sjmc7since there's no decision on it15:52
nikhil_kcool, we can discuss some of these on #openstack-searchlight15:53
nikhil_klakshmiS: do you have something on the named queries for today?15:53
lakshmiSi have been worknig on the code without a BP :) so added a BP today.15:53
nikhil_k:)15:54
lakshmiSessentially its meant to save useful queries as named queries.15:54
lakshmiSwould need help from glance/horizo to know what are usef queries though?15:54
sjmc7talk to TravT when he's back since he's doing some horizon integration work15:55
lakshmiSsure sjmc7:15:55
nikhil_k#info Liberty 2 Release plan15:56
nikhil_kI guess we should wait unitl the Nova plugin is merged15:56
sjmc7yeah, i think so15:56
sjmc7whens the deadline?15:56
nikhil_kare there any more blockers people know of?15:56
sjmc7no15:57
nikhil_kL-2 July 30th15:57
sjmc7ok. we can aim for that15:57
nikhil_kcool15:57
nikhil_k#info Summit speaking proposals - anyone interested in being added as copresenters?15:57
nikhil_kwas that you sjmc7 ?15:57
sjmc7this was me15:57
sjmc7travis and i filed a couple of proposals - one similar to what we presented to glance and horizon, at a higher product level15:58
sjmc7and one at a more technical level about how data gets in and out of e-s15:58
sjmc7for developers15:58
sjmc7i don't have links yet but if anyone's interested in being named as a co-speaker let me or travis know15:58
*** harshs has quit IRC15:59
sjmc7if we don't get either we'll try and get some working session time, although not sure about travel budgets15:59
*** evgenyf has quit IRC15:59
nikhil_ksounds good16:00
*** banix has quit IRC16:00
nikhil_k#action all: Code reviews, particularly for Endre's designate plugin and Steve's WIP nova support16:00
sjmc7yes please!16:00
nikhil_kThanks all for joining, have a nice rest of the day/evening!16:00
nikhil_k#endmeeting16:00
lakshmiSupdate on ceilometer notifications: chatted with ceilometer team and they seemed to be opposing using pools since they had previous issues with missing notifications. their suggestion is to configure glance to send to multiple topcis as the stacktach project does.16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
openstackMeeting ended Thu Jul 16 16:00:45 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_search/2015/openstack_search.2015-07-16-15.03.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_search/2015/openstack_search.2015-07-16-15.03.txt16:00
*** sjmc7 has left #openstack-meeting-416:00
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_search/2015/openstack_search.2015-07-16-15.03.log.html16:00
nikhil_koops, sorry lakshmiS16:00
*** KunalGandhi has joined #openstack-meeting-416:00
lakshmiSnp: will discuss on #openstack-searchlight16:01
nikhil_kawesome16:01
*** banix has joined #openstack-meeting-416:01
cloudnull#startmeeting OpenStack Ansible Meeting16:02
openstackMeeting started Thu Jul 16 16:02:43 2015 UTC and is due to finish in 60 minutes.  The chair is cloudnull. Information about MeetBot at http://wiki.debian.org/MeetBot.16:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:02
*** openstack changes topic to " (Meeting topic: OpenStack Ansible Meeting)"16:02
openstackThe meeting name has been set to 'openstack_ansible_meeting'16:02
*** prometheanfire has joined #openstack-meeting-416:02
cloudnullhello everyone16:03
cloudnull#topic Agenda & rollcall16:03
*** openstack changes topic to "Agenda & rollcall (Meeting topic: OpenStack Ansible Meeting)"16:03
cloudnullo/16:03
jwagner\o16:03
*** odyssey4me has joined #openstack-meeting-416:03
odyssey4meo/16:03
prometheanfire\o16:03
sigmavirus24o/16:03
*** ccrouch has left #openstack-meeting-416:03
serverascodeo/16:04
*** Bjoern_ is now known as BjoernT16:04
stevelleo/16:04
andymccro/16:04
*** TheIntern has quit IRC16:04
hughsaunderslo16:04
palendaeHi16:05
cloudnullso i guess we're all here.16:06
sigmavirus24Anddddd endmeeting16:06
sigmavirus24=P16:06
cloudnull#topic Review action items from last week16:06
*** openstack changes topic to "Review action items from last week (Meeting topic: OpenStack Ansible Meeting)"16:06
*** Sam-I-Am has joined #openstack-meeting-416:06
cloudnullwe only had the one - test upgrading from kilo to liberty (master)16:06
cloudnullpalendae:  i think that you gave this a go16:07
*** sdake_ has joined #openstack-meeting-416:07
cloudnulland we found that the not having an epoch in the version number for liberty was causing problems.16:07
cloudnullcc sigmavirus2416:07
sigmavirus24so16:07
sigmavirus24I think I figured out a way to work around that16:07
sigmavirus24But I have yet to put together a POC16:07
palendaecloudnull: I did juno to master, but yes16:07
palendaeI'd assume any upgrade where master is the end target would happen, though16:08
sigmavirus24Basically the plan I have is that if we just change the wheel names, pip will work with the upgrade from kilo to liberty16:08
palendaeAnd *technically* we don't support Juno straight to Liberty16:08
sigmavirus24Then we purge the kilo versions and change the liberty wheel names if we want to keep them around16:08
palendaeCause our unspoken rule was upgrades should go ((current + 1) + 1)16:08
sigmavirus24The versions of the servers will be X.0.0 and so upgrading without epochs from there will be fine16:08
*** adityav has joined #openstack-meeting-416:08
sigmavirus24But we can't keep around legacy (read Kilo) packages16:09
*** ivar-lazzaro has joined #openstack-meeting-416:09
sigmavirus24Basically upgrading kilo to liberty will be a nightmare because the release team cares more about aesthetics16:09
cloudnullwhich sucks.16:09
sigmavirus24¯\_(ツ)_/¯16:10
*** s3wong has joined #openstack-meeting-416:10
*** erikmwilson has joined #openstack-meeting-416:10
*** sdake has quit IRC16:10
sigmavirus24They've made it clear at this point they will not deal with the problems they've caused so I'm not going to expend more energy on a mailing list discussion that isn't going to progress. Even if they misrepresent how installs actually work from people doing production source-based installs16:10
cloudnullif we have oppinions about this, which i think we do please contribute to the conversation here: http://lists.openstack.org/pipermail/openstack-dev/2015-July/069556.html16:11
*** FallenPegasus has quit IRC16:12
Sam-I-Amsigmavirus24: tell us how you really feel?16:12
cloudnullso we'll need to  carry an action item to figure our a fix for that moving forward.16:12
sigmavirus24cloudnull: I just need to find time to put together a POC16:12
sigmavirus24The one off upgrades will be a nightmare for in-place upgrades16:12
cloudnull#action add more hours to the day so sigmavirus24 can put together a POC16:13
sigmavirus24And just for kilo->liberty16:13
sigmavirus24Appreciated16:13
cloudnulllol16:13
cloudnull#topic Blueprints16:13
*** openstack changes topic to "Blueprints (Meeting topic: OpenStack Ansible Meeting)"16:13
cloudnullthere are a few more specs online https://review.openstack.org/#/q/status:open+project:stackforge/os-ansible-deployment-specs,n,z16:13
cloudnullthey all need reviews.16:13
cloudnullspecifically https://review.openstack.org/#/c/194255/16:14
cloudnullwhich i think is not far off from the work that has been going into upstream for better Keystone support.16:14
cloudnull#link https://blueprints.launchpad.net/openstack-ansible/+spec/keystone-sp-adfs-idp16:14
cloudnull#link https://blueprints.launchpad.net/openstack-ansible/+spec/keystone-federation16:15
cloudnullodyssey4me: miguelgrinberg hughsaunders how are things going on all that16:16
odyssey4menot doing too badly - some work is still ongoing for the keystone IdP16:17
miguelgrinbergthe SP is looking pretty good, IdP needs a day or two more16:17
hughsaunderscloudnull: nearly there, just testing the playbook modifications at the moment16:17
odyssey4methe Keystone SP is largely done - we have a tested configuration working for TestShib (a public test IdP)16:17
*** mitchjameson has joined #openstack-meeting-416:18
odyssey4meI'm busy validating the ADFS use-case and have discovered a lovely issue when doing SSL offloading, which is obviously a production related thing16:18
odyssey4meanyway, I'm not giving up yet16:18
cloudnulli changed the keystone-deferation in LP to good progress.16:18
cloudnull*federation16:18
cloudnullanything that we want to touch on in terms of specs / bps ?16:19
cloudnullanything that needs a spec / bp that we're not already working that we think we should be ?16:19
cloudnullcc BjoernT ^16:20
*** b3rnard0 has joined #openstack-meeting-416:20
BjoernT?? are talking still over federation?16:20
cloudnull[11:19] <cloudnull> anything that we want to touch on in terms of specs / bps ?16:21
cloudnull[11:19] <cloudnull> anything that needs a spec / bp that we're not already working that we think we should be ?16:21
BjoernTnope16:21
cloudnullokiedokie.16:21
cloudnull#topic Open discussion16:21
*** openstack changes topic to "Open discussion (Meeting topic: OpenStack Ansible Meeting)"16:21
cloudnull#startvote Can/should we re-enable the successerator w/ 1 retry for Master / Kilo?16:22
openstackBegin voting on: Can/should we re-enable the successerator w/ 1 retry for Master / Kilo? Valid vote options are Yes, No.16:22
openstackVote using '#vote OPTION'. Only your last vote counts.16:22
cloudnullthis is around our gating issues .16:22
cloudnullwe presently set the successerator to 0/1 for master kilo16:22
cloudnullshould we re-enable it ?16:22
stevelleis this the original successerator?16:23
jwagnersorry if i am out of the loop, but why was it lowered?16:23
cloudnullmost of the issues inflight have been seen as transient except in the case of HPB4.16:23
cloudnullstevelle: yup16:23
cloudnullits still there.16:23
cloudnulljust with retries set to 016:23
cloudnullgit-harry hughsaunders ^16:23
andymccrhm16:23
odyssey4mehm16:24
cloudnull#vote yes16:24
hughsaunders#vote yes16:24
stevelle#vote yes16:24
*** KunalGan_ has joined #openstack-meeting-416:24
cloudnullthat said we can rip it back out once ansible v2 drops and we get it baked in16:24
andymccrin theory we should address the issues if possible, but im guessing that isnt the case16:24
andymccrso16:24
andymccr#vote yes16:24
andymccrahh yeh treu16:24
andymccrtrue16:24
andymccrlets set that as an aim16:24
palendae#vote yes16:24
palendaeOn the provision that we do the v2 rip out and such16:25
odyssey4meyeah, happy to do it to see if it helps and until ansible v2 drops16:25
odyssey4me#vote yes16:25
prometheanfire#vote yes16:25
*** dwalleck has joined #openstack-meeting-416:25
*** KunalGandhi has quit IRC16:26
cloudnull#endvote16:26
openstackVoted on "Can/should we re-enable the successerator w/ 1 retry for Master / Kilo?" Results are16:26
cloudnullnext: How should we handle the change in OpenStack package version numbers? odyssey4me16:27
cloudnullcc sigmavirus2416:27
*** Swami has joined #openstack-meeting-416:27
sigmavirus24You mean in liberty?16:27
cloudnulli guess we already covered this,16:27
cloudnullyes16:27
cloudnulli assume odyssey4me ?16:27
odyssey4melol, personally I think this is best handled as a once-off... if we perpetuate the model we're going to have to live with it for ever16:28
sigmavirus24Yeah leave the actual python package metadata alone, muck with the filenames since that's what pip checks for upgrades/installs16:28
sigmavirus24odyssey4me: read upwards, that's what I'm suggesting16:28
sigmavirus24I think there's a way to do it, but that one-off will be painful no matter waht16:28
cloudnull#link http://lists.openstack.org/pipermail/openstack-operators/2015-June/007390.html16:28
sigmavirus24Thanks ReleaseMGMTTeam16:28
cloudnull#link http://legacy.python.org/dev/peps/pep-0440/#version-epochs16:28
*** evgenyf has joined #openstack-meeting-416:28
odyssey4meand what's the issue with doing a kilo->liberty reboot of packages?16:29
odyssey4meie remove then install again for hosts, and kill containers and rebuild16:29
odyssey4me(or something to that effect)16:29
sigmavirus24Are in-place upgrades no longer wanted?16:29
sigmavirus24I thought that was a bit of a goal/feature we had going16:29
cloudnullwe want in-place upgrades for sure.16:29
*** dims_ has quit IRC16:30
odyssey4meI'm just saying that containers can be replaced easily. If we stage it right, it'll even be without downtime.16:30
odyssey4meAnd packages too - we could even try a force 'downgrade' as an approach.16:31
cloudnulli think that we need to spike on how to best deal with these changes moving forward.16:31
andymccragree with that16:31
odyssey4meI just don't see the point of introducing some arbitrary prefix to packages.16:31
cloudnullcan someone get a thread going on the ML to that effect  ?16:31
*** armax has quit IRC16:31
*** dims_ has joined #openstack-meeting-416:32
*** dims_ has quit IRC16:32
*** adityav has quit IRC16:32
*** sbalukoff has joined #openstack-meeting-416:33
cloudnullSo maybe next time? Anyone want to help out with that effort?16:35
*** fitoduarte has joined #openstack-meeting-416:36
odyssey4meI'm interested in doing a spike on it, but it'll only probably happen in two weeks or so for me.16:37
andymccrcloudnull: im happy to get on board with that too16:37
andymccr(im ooto after next week though for a bit so same deal as odyssey4me really)16:37
sigmavirus24I'll see if I can get a spike done next week16:38
*** ivar-lazzaro has quit IRC16:38
sigmavirus24I don't see anyway to prevent the operator from having to be very cognizant of this upgrade problem though16:38
*** mclaren has quit IRC16:38
palendaetbh the operator should be cognizant of upgrade problems16:38
sigmavirus24If there's any that we can make easier, though, we should16:39
sigmavirus24This one we can't16:39
palendaeTrue16:39
sigmavirus24We'll need really good documentation around this though so we'll need Sam-I-Am's help16:39
palendaeThey are still ultimately using openstack, though, so it's very much worth pointing out that this decision happened16:39
sigmavirus24certainly16:40
stevelledocument the atrocities16:41
cloudnullok so anything else we want to talk about ?16:41
cloudnullits open mic time16:41
cloudnullokiedokie.16:43
cloudnull#action reenable the successerator for a single retry within the gate. To be removed as soon as Ansible v2 drops upstream - someone16:43
cloudnull#action get a thread going on the mailing list surrounding issues with upgrading Kilo > Liberty - someone16:44
cloudnull#endmeeting16:44
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:44
openstackMeeting ended Thu Jul 16 16:44:23 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:44
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-07-16-16.02.html16:44
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-07-16-16.02.txt16:44
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-07-16-16.02.log.html16:44
*** cloudnull has left #openstack-meeting-416:44
*** padkrish has joined #openstack-meeting-416:44
*** lakshmiS has quit IRC16:45
*** odyssey4me has left #openstack-meeting-416:48
*** ajmiller has quit IRC16:48
*** prometheanfire has left #openstack-meeting-416:51
*** erikmwilson has left #openstack-meeting-416:54
*** ajmiller has joined #openstack-meeting-416:54
*** ajmiller__ has joined #openstack-meeting-416:54
*** ajmiller__ has quit IRC16:55
*** padkrish has quit IRC16:55
*** xingchao has quit IRC16:56
*** padkrish has joined #openstack-meeting-416:56
*** LouisF has joined #openstack-meeting-416:58
*** galstrom is now known as galstrom_zzz16:58
*** DericHorn-HP has joined #openstack-meeting-416:59
*** cathy_ has joined #openstack-meeting-416:59
*** Mohankumar_ has joined #openstack-meeting-416:59
*** stevelle has left #openstack-meeting-417:00
cathy_#startmeeting service_chaining17:00
openstackMeeting started Thu Jul 16 17:00:28 2015 UTC and is due to finish in 60 minutes.  The chair is cathy_. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: service_chaining)"17:00
openstackThe meeting name has been set to 'service_chaining'17:00
*** banix has quit IRC17:00
s3wonghello17:00
cathy_hi everyone17:00
Vikramhi17:00
LouisFhi17:00
*** Brain_ has joined #openstack-meeting-417:00
Mohankumar_Hi all17:01
cathy_#topic •Spec status update17:02
*** openstack changes topic to "•Spec status update (Meeting topic: service_chaining)"17:02
Swamihi everyone17:02
cathy_so the spec is ready for merge.17:02
cathy_of course after the merge, we can still modify it if needed17:03
Mohankumar_yes it looks good to go ..17:03
s3wongcathy_: sc68cal just gave a -1... :-)17:03
cathy_Mohankumar_: yes:-)17:03
*** TheIntern has joined #openstack-meeting-417:03
amotokihi17:04
cathy_s3wong: I will take a look and address the comments. But that will not impact the merge.17:04
*** xingchao has joined #openstack-meeting-417:04
cathy_amotoki: hi, thanks for joinging17:04
s3wongcathy_: sure17:04
sc68cali'm here17:05
cathy_#topic •SFC CLI client and Horizon Client dependency on base Neutron CLI and Horizon code17:05
*** openstack changes topic to "•SFC CLI client and Horizon Client dependency on base Neutron CLI and Horizon code (Meeting topic: service_chaining)"17:05
cathy_Mohankumar_: would you like to explain the issue you faced?17:06
s3wongsc68cal: you gave a -1 on the networking-sfc API spec, and cathy_ will address it... that's all :-)17:06
cathy_sc68cal: hi17:06
cathy_sc68cal: yes, I will address it17:07
Mohankumar_cathy_ , we can't do UT in networking-SFC stackforge directory as many dependency files are misssing .17:07
*** evgenyf has quit IRC17:07
cathy_Mohankumar_: why stackforge? we are on OpenStack repo.17:07
Vikramsc68cal: i don't see any cross dependencies... even the spec itself says that..17:07
Mohankumar_cathy_ i  mean networking-sfc17:08
Mohankumar_repo17:08
cathy_Mohankumar_: ok17:08
cathy_so you mean the CLI client codes have dependency on the base Neutron CLI codes?17:09
Vikramcathy_: +117:09
cathy_amotoki: Do you have any suggestion how to resolve this?17:09
Mohankumar_cathy_ yes17:09
LouisFsc68cal: just posted response to your comment17:09
amotokicathy_: i haven't caught up with the context....17:10
*** yamamoto_ has quit IRC17:10
Vikramcathy_: for running UT there is already a framework developed in the master branch..17:10
-amotoki- cathing up17:10
cathy_My understanding of the issue is that The Python Neutron client code for SFC can not link properly to the base neutron Client codes. Maybe Vikram or Mohankumar_ can clarify more on this?17:11
Vikramamotoki: the question here is how to run the UT for the new developed cli code..17:12
Mohankumar_vikram +117:12
Vikramamotoki: as discussed before we used the extension method for writing the test17:12
cathy_give me 2 minutes since I need to move to another conf room.17:12
amotokiVikram: i think it dpends on what code we have. we can talk it in reviews more efficiently17:13
Vikramthe question here is how to write the unit test for this..17:13
*** krtaylor has quit IRC17:13
fitoduarte.17:13
amotokiVikram: ah... I can join the review later. let me share the link17:13
Vikramamotoki: ok,, will take it offline then!17:13
Vikramamotoki: we have done a part of it17:14
*** armax has joined #openstack-meeting-417:14
Vikramit will be better if you can review and suggest us the way17:14
Vikramhttps://review.openstack.org/#/c/200065/17:15
cathy_#action take the discussion of "SFC CLI client and Horizon Client dependency" offline and amotoki will review the codes and give guidance17:15
cathy_#topic •OVS Driver and OVS support for classifier and SFF17:15
*** openstack changes topic to "•OVS Driver and OVS support for classifier and SFF (Meeting topic: service_chaining)"17:15
amotokii am not sure about Horizon dependency but I can help from both perspective.17:15
*** FallenPegasus has joined #openstack-meeting-417:16
cathy_amotoki: Thanks so much!!!17:16
Vikramamotoki: thanks!17:16
amotokibtw, SFF?17:16
cathy_For the OVS support, if we decide to go for no SFC header with chain ID, then the OVS has to build a forwarding table based on 5-tuple or n-tuple for flow identification.17:16
cathy_amotoki: service function forwarder, the vSwitch17:17
amotokigot it. many abbrevs17:17
cathy_Sorry that I am using the terminology of IETF SFC17:17
cathy_amotoki: yes:-) It is confusing17:17
cathy_Everyone, what's your take and input?17:18
s3wongcathy_: and without full support of NSH in OVS, I believe that injecting flow entry on every hop within the chain is the only way to go17:18
s3wong* injection OF flow entry...17:18
LouisFneed to decide on mods to the OVS agent to handle the flow tables17:19
*** KunalGan_ has quit IRC17:19
*** KunalGandhi has joined #openstack-meeting-417:19
*** KunalGandhi has quit IRC17:19
*** Mohankumar_ has quit IRC17:19
LouisFs3wong: agree17:19
cathy_s3wong: without NSH, we also need the OVS driver to inject/program flow entries into OVS from every hop. The difference is that the OVS table index is different17:19
amotokis3wong: agree to some extent, but how does it bother SFC without NSH?17:20
*** Mohankumar__ has joined #openstack-meeting-417:20
cathy_amotoki: it does not bother. The difference is that with chain ID, the table in OVS will be much simpler and smaller17:20
amotokiyes. with NSH we can simplify flow tables.17:21
s3wongamotoki: with NSH and more specifically chain ID, one only needs to inject simpler flow entries to hops17:21
cathy_and the forwarding operation in OVS will be much efficient since the index is a single chain-ID instead of checking 5-tupe or 7-tuple17:21
amotokitotally agree.17:21
s3wongamotoki: but correct, we still need to inject flow entry every hop, so control plane perspective is pretty much the same17:22
cathy_or in the future 11-tuple for more granular flow treatment17:22
cathy_Also control plane will need to map every hop to the n-tuple instead of a single ID index17:23
LouisFs3wong: do you see changes to the OVS Integration bridge?17:23
LouisFs3wong: to handle the new port chain flows?17:23
cathy_Actually as far as I know, people are working OVS to add support of chain-ID.17:23
LouisFcathy_: you mean NSH extensions to OVS?17:24
cathy_So maybe our reference implementation should be using chain-ID to really make the SFC performance acceptable17:24
s3wongLouisF: changes to the communication between Neutron server and OVS agents? probably no change there17:24
amotokiwe can improve the efficiency by OVS support, but from the control plane perspective it does affect anything as ref impl.17:25
cathy_LouisF: you can say that, but not exactly17:25
LouisFs3wong: agree, just the flow tables processing on the OVS bridge17:26
*** rfolco has quit IRC17:26
cathy_amotoki: you mean it DOES NOT affect anything?17:26
cathy_It affects the OVS driver implementation17:26
s3wongLouisF: that would be what I expect --- but of course things may change once we implement it :-)17:26
amotokicathy_: I mean the communication between neutron-server and angets17:26
*** mitchjameson has quit IRC17:26
LouisFs3wong: agree17:26
cathy_amotoki: it will affects since the messages between the OVS drive and the OVS agent will be different.17:27
amotokicathy_: so I said it affects performance or efficiency. perhaps we are in the same page.17:28
s3wongcathy_: the message content changes. But what amotoki and I meant was the efficiency in terms of control plane (# of Neutron server -> OVS agent messages) is not affected17:28
cathy_One is to push a chain header (the chain-ID) into the packet and then program the OVS table with ID as the index. The other does not push any header ans use n-tuple as index of the table17:28
amotokis3wong: right17:29
s3wongcathy_: but certainly DATA PLANE efficiency will be drastically improved via NSH/chain-ID support17:29
*** puranamr has joined #openstack-meeting-417:29
cathy_minor difference on the efficiency on control plane, I think, but I need to think about it more to be sure.17:30
cathy_s3wong: yes17:30
cathy_we need to reach consensus so that we can choose which implemenation to go.17:30
*** yamahata has quit IRC17:31
s3wongcathy_: I thought we established that we will do the full-flow entry programming in OVS for Liberty (as OVS support isn't there yet)?17:32
s3wongcathy_: so what is the other option of implementation?17:32
LouisFs3wong: agree17:32
cathy_other option is to support chain-ID.17:32
*** dims_ has joined #openstack-meeting-417:32
LouisFcathy_: but then we have a dependency on NSH support in OVS17:33
cathy_OK, then let's do the no-ChainID impelementation with the performance limitation in mind17:33
amotokiI think the bottom line is that we have a referement impl support and we can go more.17:33
s3wongcathy_: meaning that we will have someone in this team contributing to ovs-dev?  :-)17:33
cathy_amotoki: agree.17:33
LouisFcathy_: this is just a reference implementation17:33
amotokiwe can accpet an impl with a bit less performace.17:34
LouisFamotoki: agree17:34
cathy_#agreed The OVS driver and agent implementation will be no NSH since OVS does not support it yet17:34
*** armax has quit IRC17:34
amotokithe ref impl will have more performacne once OVS supports us.17:34
*** xingchao has quit IRC17:35
s3wongcathy_: chain ID also has implication on the API (w.r.t. the parameters field), right?17:35
*** banix has joined #openstack-meeting-417:35
*** vivek__ has joined #openstack-meeting-417:36
LouisFs3wong: the correlation field in chain-parameters will be = none17:36
cathy_s3wong: I don;t think so. User can choose which option to go in the API and that parameter is optional.17:37
s3wongLouisF: for now. But once OVS supports NSH / chain-ID, and we decide to adopt it, then users of the API would need to fill up the parameters, right?17:37
*** evgenyf has joined #openstack-meeting-417:37
LouisFs3wong: yes17:38
LouisFs3wong: the corrlation field in chain-parameters could be set = nsh17:38
cathy_Some status update. Now that the spec is merged, I am working on the system design as suggested by amotoki and will have it ready for review next week. Louis and I are also working on the OVS driver design document17:38
*** dims_ has quit IRC17:39
*** wayne____ has quit IRC17:39
LouisFfeel free to suggestion ideas17:39
amotokisorry I couldn't take enough to review the API, but it is would be grate if the API provides full funtionality17:39
s3wongcathy_, LouisF: I would also like to jump into the OVS driver design and implementation17:40
LouisFs3wong: great!17:40
cathy_amotoki: the API provides full functionality for supporting the SFC for the first release and options for future extension17:40
amotokiNSH can help us bring more performacne and efficiency17:40
*** SumitNaiksatam has joined #openstack-meeting-417:40
*** KunalGandhi has joined #openstack-meeting-417:40
cathy_s3wong: great. Thanks! let's work together on that17:41
*** ajmiller__ has joined #openstack-meeting-417:41
amotokilet me check soon early next week.17:41
*** lazy_prince has quit IRC17:41
cathy_amotoki: Thanks17:41
*** puranamr has quit IRC17:42
cathy_any other topic for the meeting discussion? We are efficient and still have 18 minutes left.17:42
s3wongcathy_, LouisF: cool17:42
s3wongcathy_: once we get into coding, the meeting should be morphed into more a status update moving forward :-)17:42
*** geoffarnold has joined #openstack-meeting-417:43
cathy_s3wong: yes:-)17:43
*** ajmiller has quit IRC17:43
cathy_Given our time constraint, we need to move forward with the coding much faster to catch the Liberty release17:43
amotokibtw, do we have a wiki page to collect our efforts?17:43
cathy_amotoki: yes let me post the link17:44
amotokicathy_: nice17:44
*** vivek__ has quit IRC17:44
cathy_#link https://wiki.openstack.org/wiki/Neutron/APIForServiceChaining17:44
cathy_any other topic you folks like to discuss?17:45
s3wongcathy_: agreed, we are a little over two weeks away from end of L-217:45
*** bknudson has quit IRC17:45
cathy_amotoki: could you guide us on what integration testing we need to do for getting into the L release? Any other gating or requirements we need to plan to get them done?17:46
amotokis3wong: we are not so tightly constrainted by the release cycle. networking-sfc repo has a freedom17:46
s3wongamotoki: true... but as a team we want to hit at least a demo-able implementation by M-Summit17:47
*** krtaylor has joined #openstack-meeting-417:47
*** puranamr has joined #openstack-meeting-417:47
s3wongamotoki: this time around, the Liberty Release and M-Summit is only TWO weeks apart17:47
amotokicathy_: it depends on us. We are not strictly required to have integarated gating at this moment.17:47
cathy_s3wong: agree. Let's work hard on it17:47
*** ivar-lazzaro has joined #openstack-meeting-417:47
amotokiwe can first complete our first round and then explore better testing.17:47
*** ivar-lazzaro has quit IRC17:48
amotokiof course we can start testing along with implementation, but we have limited resources.17:48
amotokiI think we can focus on features for LIberty and Mitaka summit17:49
*** jckasper has quit IRC17:49
s3wongamotoki: agreed17:49
amotokicathy_: what do you think?17:49
*** ivar-lazzaro has joined #openstack-meeting-417:49
cathy_amotoki: Could you point us to the OpenStack integration gating and required testing link if we would like to satisfy those gating?17:49
cathy_amotoki: agree.17:50
amotokicathy_: functional testing is now being moved to in-tree17:50
*** igordcard has joined #openstack-meeting-417:50
*** ivar-lazzaro has quit IRC17:50
cathy_As s3wong said we would like to have some good codes for demo ready for the Liberty summit to feel good about ourselves:-)17:51
*** iymht has joined #openstack-meeting-417:51
amotokiso most things are up to us, the community. can we believe we have enough tesitng? we can ask ourselves.17:51
*** ivar-lazzaro has joined #openstack-meeting-417:51
LouisFamotoki: what do you mean by "in-tree"?17:52
cathy_amotoki: Ok. thanks. I still would like to make the testing very comprehensive and strict. Let's work on that part later17:52
amotokiif we have a good coverage to some extent, we can say SFC is a good and mature project :-)17:52
*** auld has quit IRC17:52
*** dims_ has joined #openstack-meeting-417:52
amotokiLouisF: under "big tent" content, we no longer have all functioanal and scenaro tesitng in tempest.17:53
*** dims_ has quit IRC17:53
cathy_amotoki: sure, that should be the way this project is delivered17:53
s3wongLouisF: not Tempest, I suppose that is what amotoki meant?17:53
*** puranamr has quit IRC17:53
amotokis3wong: LouisF: correct.17:53
amotokitempest decided not to have all tests in their repository in Vancouver.17:54
cathy_amotoki: you mean we should check in our funcitonal testing codes into our project repo, right?17:54
amotokicathy_: what i want to say is that we need to have funcational testing in our repo gradually.17:55
cathy_amotoki: OK17:55
amotokitempest team can help us but they feel they don't scale.17:55
cathy_amotoki: Ok, i see17:56
amotokiwe need to share our knowledge as a whole neutron stadium. I am learning too.17:56
cathy_So it seems no more "topic" for this meeting. Then let's end this meeting and go to work on the code design/implementation. OK?17:56
*** carl_baldwin has quit IRC17:56
cathy_amotoki: Is there a link for that knowledge sharing?17:57
s3wongcathy_: +117:57
Vikram+117:57
cathy_amotoki: Could you keep us in the loop on that? Thanks.17:57
Swamicathy_: I think we should still have weekly meeting to go over the status, blocking issues etc.,17:57
amotokicathy_: i have no exact link ..17:57
cathy_Swami: sure we will continue the IRC meeting17:57
*** dims_ has joined #openstack-meeting-417:57
amotokicathy_: it is a bit late, but i try to join the effort !17:57
cathy_amotoki: we need you !17:58
LouisF+117:58
*** Sam-I-Am has left #openstack-meeting-417:58
cathy_OK, thanks everyone! talk to you in next meeting.17:58
s3wongSwami: yeah, I don't think we are suggesting stopping the weekly meeting :-)17:58
Swamis3wong: thanks.17:58
LouisFbye17:58
amotokithe meeitng is a great time to share the progress17:59
Vikrambye17:59
cathy_bye now17:59
Mohankumar__bye17:59
*** dwalleck has quit IRC17:59
s3wongThanks all!17:59
amotokinight17:59
cathy_amotoki: yes, agree17:59
cathy_bye17:59
*** Vikram has quit IRC17:59
cathy_#endmeeting17:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:59
openstackMeeting ended Thu Jul 16 17:59:30 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/service_chaining/2015/service_chaining.2015-07-16-17.00.html17:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/service_chaining/2015/service_chaining.2015-07-16-17.00.txt17:59
openstackLog:            http://eavesdrop.openstack.org/meetings/service_chaining/2015/service_chaining.2015-07-16-17.00.log.html17:59
*** harshs has joined #openstack-meeting-418:00
*** amotoki has quit IRC18:00
*** malini has quit IRC18:01
*** rfolco has joined #openstack-meeting-418:01
*** padkrish has quit IRC18:01
*** padkrish has joined #openstack-meeting-418:02
*** ivar-laz_ has joined #openstack-meeting-418:02
*** DericHorn-HP has quit IRC18:04
*** Sukhdev has joined #openstack-meeting-418:04
*** rfolco has quit IRC18:05
*** cathy_ has quit IRC18:05
*** Brain_ has quit IRC18:06
*** ivar-lazzaro has quit IRC18:06
*** rfolco has joined #openstack-meeting-418:09
*** isq has quit IRC18:10
*** yamamoto has joined #openstack-meeting-418:10
*** vivek_ has joined #openstack-meeting-418:11
*** isq has joined #openstack-meeting-418:13
*** sdake has joined #openstack-meeting-418:13
*** yamamoto has quit IRC18:15
*** sdake_ has quit IRC18:16
*** FallenPegasus has quit IRC18:21
*** padkrish has quit IRC18:22
*** padkrish has joined #openstack-meeting-418:23
*** TheIntern has quit IRC18:27
*** _ody has joined #openstack-meeting-418:29
*** auld has joined #openstack-meeting-418:31
*** jckasper has joined #openstack-meeting-418:32
*** FallenPegasus has joined #openstack-meeting-418:32
*** _ody has quit IRC18:34
*** FallenPegasus has quit IRC18:35
*** jwagner is now known as jwagner_away18:37
*** jwang has joined #openstack-meeting-418:38
*** sbalukoff has quit IRC18:39
*** ivar-laz_ has quit IRC18:49
*** dims_ has quit IRC18:51
*** dims_ has joined #openstack-meeting-418:52
*** FallenPegasus has joined #openstack-meeting-418:53
*** dims_ has quit IRC18:56
*** puranamr has joined #openstack-meeting-418:58
*** bknudson has joined #openstack-meeting-418:59
*** jwagner_away is now known as jwagner18:59
*** jecarey_ has joined #openstack-meeting-419:01
*** galstrom_zzz is now known as galstrom19:01
*** jecarey has quit IRC19:02
*** TheIntern has joined #openstack-meeting-419:04
*** sdake_ has joined #openstack-meeting-419:08
*** puranamr has quit IRC19:08
*** padkrish has quit IRC19:10
*** padkrish has joined #openstack-meeting-419:11
*** sdake has quit IRC19:11
*** sbalukoff has joined #openstack-meeting-419:14
*** padkrish has quit IRC19:15
*** Mohankumar__ has quit IRC19:16
*** belmoreira has joined #openstack-meeting-419:18
*** bknudson has quit IRC19:19
*** ivar-lazzaro has joined #openstack-meeting-419:20
*** evgenyf has quit IRC19:21
*** ivar-lazzaro has quit IRC19:24
*** carl_baldwin has joined #openstack-meeting-419:29
*** banix has quit IRC19:32
*** mitchjameson has joined #openstack-meeting-419:36
*** padkrish has joined #openstack-meeting-419:38
*** padkrish has quit IRC19:43
*** FallenPegasus has quit IRC19:43
*** jecarey_ has quit IRC19:52
*** jecarey has joined #openstack-meeting-419:52
*** jecarey_ has joined #openstack-meeting-419:53
*** Swami has quit IRC19:55
*** jecarey has quit IRC19:57
*** LouisF has quit IRC20:03
*** Sukhdev has quit IRC20:04
*** FallenPegasus has joined #openstack-meeting-420:06
*** padkrish has joined #openstack-meeting-420:07
*** belmoreira has quit IRC20:11
*** padkrish has quit IRC20:11
*** salv-orlando has quit IRC20:11
*** DericHorn-HP has joined #openstack-meeting-420:11
*** Sukhdev has joined #openstack-meeting-420:15
*** ajmiller__ has quit IRC20:17
*** igordcard has quit IRC20:25
*** jasondotstar has joined #openstack-meeting-420:30
*** ivar-laz_ has joined #openstack-meeting-420:31
*** auld has quit IRC20:33
*** krtaylor has quit IRC20:36
*** dims_ has joined #openstack-meeting-420:37
*** delattec has quit IRC20:37
*** jwagner is now known as jwagner_away20:39
*** FallenPegasus has quit IRC20:42
*** geoffarnold has quit IRC20:42
*** geoffarnold has joined #openstack-meeting-420:43
*** geoffarnold has quit IRC20:43
*** salv-orlando has joined #openstack-meeting-420:45
*** geoffarnold has joined #openstack-meeting-420:45
*** ivar-laz_ has quit IRC20:46
*** ivar-lazzaro has joined #openstack-meeting-420:46
*** ivar-lazzaro has quit IRC20:47
*** ivar-lazzaro has joined #openstack-meeting-420:47
*** geoffarnold has quit IRC20:49
*** ivar-lazzaro has quit IRC20:52
*** FallenPegasus has joined #openstack-meeting-420:52
*** ajmiller has joined #openstack-meeting-420:58
*** armax has joined #openstack-meeting-421:03
*** cdelatte has joined #openstack-meeting-421:05
*** padkrish has joined #openstack-meeting-421:08
*** padkrish has quit IRC21:12
*** ivar-lazzaro has joined #openstack-meeting-421:17
*** ivar-lazzaro has quit IRC21:21
*** ajmiller has quit IRC21:24
*** ajmiller has joined #openstack-meeting-421:25
*** ajmiller__ has joined #openstack-meeting-421:27
*** ajmiller has quit IRC21:27
*** ajmiller__ has quit IRC21:28
*** ajmiller has joined #openstack-meeting-421:29
*** TheIntern has quit IRC21:31
*** ajmiller has quit IRC21:32
*** Swami has joined #openstack-meeting-421:33
*** sbalukoff has quit IRC21:36
*** krtaylor has joined #openstack-meeting-421:37
*** ajmiller has joined #openstack-meeting-421:43
*** bnemec has quit IRC21:46
*** auld has joined #openstack-meeting-421:47
*** sbalukoff has joined #openstack-meeting-421:50
*** vivek_ has quit IRC21:51
*** ivar-lazzaro has joined #openstack-meeting-421:51
*** auld has quit IRC21:53
*** vivek_ has joined #openstack-meeting-421:58
*** padkrish has joined #openstack-meeting-421:59
*** padkrish has quit IRC22:00
*** padkrish has joined #openstack-meeting-422:01
*** TheIntern has joined #openstack-meeting-422:01
*** jecarey_ has quit IRC22:01
*** DericHorn-HP has quit IRC22:02
*** auld has joined #openstack-meeting-422:03
*** ajmiller__ has joined #openstack-meeting-422:05
*** ajmiller has quit IRC22:07
*** sbalukoff has quit IRC22:08
*** puranamr has joined #openstack-meeting-422:08
*** kfjohnson has joined #openstack-meeting-422:11
*** Sukhdev has quit IRC22:14
*** jasondotstar has quit IRC22:15
*** vivek__ has joined #openstack-meeting-422:15
*** vivek_ has quit IRC22:15
*** Sukhdev has joined #openstack-meeting-422:16
*** klamath has quit IRC22:18
*** radez is now known as radez_g0n322:19
*** padkrish has quit IRC22:23
*** puranamr has quit IRC22:24
*** padkrish has joined #openstack-meeting-422:26
*** puranamr has joined #openstack-meeting-422:30
*** padkrish has quit IRC22:32
*** padkrish has joined #openstack-meeting-422:32
*** puranamr has quit IRC22:33
*** padkrish has quit IRC22:37
*** aventerav has quit IRC22:38
*** mmedvede has quit IRC22:39
*** mmedvede has joined #openstack-meeting-422:47
*** padkrish has joined #openstack-meeting-422:58
*** BjoernT has quit IRC22:59
*** hogepodge has quit IRC23:02
*** sdake_ has quit IRC23:12
*** daneyon_ has left #openstack-meeting-423:15
*** galstrom is now known as galstrom_zzz23:16
*** salv-orlando has quit IRC23:16
*** FallenPegasus has quit IRC23:16
*** fitoduarte has quit IRC23:21
*** zigo has quit IRC23:21
*** zigo has joined #openstack-meeting-423:22
*** bharath has joined #openstack-meeting-423:25
*** jasondotstar has joined #openstack-meeting-423:25
*** vivek__ has quit IRC23:26
*** sbalukoff has joined #openstack-meeting-423:28
*** FallenPegasus has joined #openstack-meeting-423:28
*** openstackstatus has joined #openstack-meeting-423:34
*** ChanServ sets mode: +v openstackstatus23:34
*** padkrish has quit IRC23:36
*** padkrish has joined #openstack-meeting-423:36
*** jpekkari has joined #openstack-meeting-423:40
*** padkrish has quit IRC23:41
*** padkrish has joined #openstack-meeting-423:43
*** britthouser has quit IRC23:47
*** britthouser has joined #openstack-meeting-423:50
*** vivek_ has joined #openstack-meeting-423:52
*** harshs has quit IRC23:53
*** barra204 has joined #openstack-meeting-423:54

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