Thursday, 2017-01-05

*** gouthamr has quit IRC00:04
*** marst has quit IRC00:04
*** jrist_ has joined #openstack-meeting-300:09
*** jrist has quit IRC00:10
*** Swami_ has joined #openstack-meeting-300:12
*** Swami__ has joined #openstack-meeting-300:15
*** Swami has quit IRC00:15
*** spzala has quit IRC00:15
*** Swami_ has quit IRC00:18
*** absubram has quit IRC00:20
*** sdague has quit IRC00:21
*** chyka has quit IRC00:29
*** amotoki has quit IRC00:34
*** shinya_kwbt has joined #openstack-meeting-300:35
*** dimtruck is now known as zz_dimtruck00:39
*** neiljerram has quit IRC00:44
*** hoangcx has joined #openstack-meeting-300:47
*** Marcellin__ has quit IRC00:49
*** huanxuan has joined #openstack-meeting-301:08
*** yamamoto has joined #openstack-meeting-301:09
*** VW has joined #openstack-meeting-301:11
*** tuanluong has joined #openstack-meeting-301:12
*** tuanluong_ has joined #openstack-meeting-301:12
*** liuyulong has joined #openstack-meeting-301:14
*** VW has quit IRC01:15
*** fitoduarte has quit IRC01:16
*** yamamoto has quit IRC01:18
*** yamamoto has joined #openstack-meeting-301:18
*** sdake has quit IRC01:21
*** Swami__ has quit IRC01:28
*** yamamoto has quit IRC01:33
*** yamamoto has joined #openstack-meeting-301:34
*** bobmel has quit IRC01:35
*** yamamoto has quit IRC01:43
*** yamamoto has joined #openstack-meeting-301:49
*** yamamoto has quit IRC01:52
*** yamamoto has joined #openstack-meeting-301:54
*** baoli has joined #openstack-meeting-301:55
*** baoli has quit IRC02:06
*** yamamoto has quit IRC02:11
*** zz_dimtruck is now known as dimtruck02:22
*** s3wong has quit IRC02:37
*** baoli has joined #openstack-meeting-302:42
*** qwebirc88570 has joined #openstack-meeting-302:48
*** qwebirc88570 has left #openstack-meeting-302:49
*** baoli has quit IRC02:55
*** baoli has joined #openstack-meeting-302:58
*** clu_ has quit IRC03:04
*** harlowja has quit IRC03:05
*** tonyb has quit IRC03:05
*** rhagarty has quit IRC03:05
*** cgayan has quit IRC03:05
*** vgridnev has quit IRC03:05
*** gothicmindfood has quit IRC03:05
*** yantarou has quit IRC03:05
*** cgayan_ has joined #openstack-meeting-303:05
*** tonyb has joined #openstack-meeting-303:05
*** yantarou has joined #openstack-meeting-303:05
*** gothicmindfood has joined #openstack-meeting-303:05
*** vgridnev- has joined #openstack-meeting-303:05
*** rhagarty has joined #openstack-meeting-303:06
*** baoli has quit IRC03:18
*** baoli has joined #openstack-meeting-303:19
*** gouthamr has joined #openstack-meeting-303:19
*** yamamoto has joined #openstack-meeting-303:20
*** zhurong has joined #openstack-meeting-303:21
*** iyamahat has quit IRC03:22
*** yamahata has quit IRC03:22
*** dimtruck is now known as zz_dimtruck03:24
*** amotoki has joined #openstack-meeting-303:30
*** julim has joined #openstack-meeting-303:32
*** marst has joined #openstack-meeting-303:34
*** baoli has quit IRC03:36
*** zhurong has quit IRC03:41
*** VW has joined #openstack-meeting-303:45
*** bobmel has joined #openstack-meeting-303:47
*** bobmel has quit IRC03:52
*** psachin has joined #openstack-meeting-304:29
*** kenji-i has quit IRC04:33
*** gouthamr has quit IRC04:43
*** VW has quit IRC04:52
*** prateek has joined #openstack-meeting-305:28
*** prateek has quit IRC05:30
*** prateek has joined #openstack-meeting-305:30
*** salv-orlando has joined #openstack-meeting-305:41
*** VW has joined #openstack-meeting-306:06
*** gouthamr has joined #openstack-meeting-306:15
*** nkrinner_afk is now known as nkrinner06:40
*** bobmel has joined #openstack-meeting-306:47
*** sdake has joined #openstack-meeting-306:51
*** bobmel has quit IRC06:51
*** pgadiya has joined #openstack-meeting-306:54
*** hoangcx_ has joined #openstack-meeting-306:54
*** hoangcx has quit IRC06:56
*** pcaruana has joined #openstack-meeting-307:05
*** salv-orl_ has joined #openstack-meeting-307:13
*** salv-orl_ has quit IRC07:13
*** salv-orlando has quit IRC07:16
*** lpetrut has joined #openstack-meeting-307:16
*** pgadiya has quit IRC07:19
*** pgadiya has joined #openstack-meeting-307:20
*** sdake_ has joined #openstack-meeting-307:28
*** armax has joined #openstack-meeting-307:30
*** sdake has quit IRC07:30
*** VW has quit IRC07:33
*** anilvenkata has joined #openstack-meeting-307:36
*** zhurong has joined #openstack-meeting-307:37
*** yamahata has joined #openstack-meeting-307:39
*** hoangcx has joined #openstack-meeting-307:53
*** gouthamr has quit IRC07:53
*** gouthamr has joined #openstack-meeting-307:54
*** matrohon has joined #openstack-meeting-307:55
*** hoangcx_ has quit IRC07:56
*** lpetrut has quit IRC07:58
*** stevejims has joined #openstack-meeting-308:04
*** gouthamr has quit IRC08:06
*** armax has quit IRC08:13
*** armax has joined #openstack-meeting-308:22
*** sdake_ is now known as sdake08:54
*** jtomasek has quit IRC08:58
*** pgadiya has quit IRC09:03
*** jtomasek has joined #openstack-meeting-309:05
*** yamamoto has quit IRC09:14
*** armax has quit IRC09:14
*** bobmel has joined #openstack-meeting-309:14
*** pgadiya has joined #openstack-meeting-309:18
*** bobmel has quit IRC09:18
*** jtomasek has quit IRC09:33
*** VW has joined #openstack-meeting-309:33
*** yamahata has quit IRC09:34
*** iyamahat has joined #openstack-meeting-309:34
*** jtomasek has joined #openstack-meeting-309:36
*** VW has quit IRC09:38
*** zhurong has quit IRC09:40
*** sdake_ has joined #openstack-meeting-309:42
*** sdake has quit IRC09:44
*** lpetrut has joined #openstack-meeting-309:48
*** rmart04 has joined #openstack-meeting-309:52
*** neiljerram has joined #openstack-meeting-309:52
*** rmart04 has quit IRC09:52
*** amotoki has quit IRC09:55
*** hoangcx has quit IRC09:57
*** yamamoto has joined #openstack-meeting-309:59
*** rmart04 has joined #openstack-meeting-310:01
*** yamamoto_ has joined #openstack-meeting-310:02
*** egallen has joined #openstack-meeting-310:03
*** yamamoto has quit IRC10:06
*** sdake_ has quit IRC10:06
*** yamamoto_ has quit IRC10:08
*** neiljerram has quit IRC10:12
*** iyamahat has quit IRC10:13
*** openstack has joined #openstack-meeting-310:16
*** ChanServ sets mode: +o openstack10:16
*** rmart04 has quit IRC10:31
*** rmart04 has joined #openstack-meeting-310:33
*** zhiyong has joined #openstack-meeting-310:34
*** yamamoto has joined #openstack-meeting-310:34
*** neiljerram has joined #openstack-meeting-310:43
*** salv-orlando has joined #openstack-meeting-310:52
*** salv-orlando has quit IRC10:57
*** mickeys has quit IRC10:57
*** salv-orlando has joined #openstack-meeting-310:57
*** salv-orlando has quit IRC11:02
*** bobmel has joined #openstack-meeting-311:04
*** salv-orlando has joined #openstack-meeting-311:04
*** armax has joined #openstack-meeting-311:05
*** amotoki has joined #openstack-meeting-311:16
*** salv-orlando has quit IRC11:19
*** salv-orlando has joined #openstack-meeting-311:19
*** sambetts|afk is now known as sambetts11:20
*** salv-orlando has quit IRC11:24
*** armax has quit IRC11:26
*** lpetrut has quit IRC11:29
*** lpetrut has joined #openstack-meeting-311:31
*** zhiyong has quit IRC11:37
*** rmart04 has quit IRC11:40
*** rmart04 has joined #openstack-meeting-311:41
*** rmart04 has quit IRC11:41
*** rmart04 has joined #openstack-meeting-311:42
*** psachin has quit IRC11:43
*** psachin has joined #openstack-meeting-311:44
*** bobmel has quit IRC11:46
*** bobmel has joined #openstack-meeting-311:47
*** bobmel has quit IRC11:50
*** matrohon has quit IRC11:55
*** mariannelm has quit IRC11:55
*** tdurakov has quit IRC11:55
*** sambetts has quit IRC11:55
*** jgrassle1 has quit IRC11:55
*** mtreinish has quit IRC11:55
*** lkoranda has quit IRC11:55
*** bauzas has quit IRC11:55
*** dansmith has quit IRC11:55
*** topol has quit IRC11:55
*** devananda has quit IRC11:55
*** dosaboy has quit IRC11:55
*** Anticimex has quit IRC11:55
*** jgrassler has joined #openstack-meeting-311:55
*** dosaboy has joined #openstack-meeting-311:55
*** sambetts_ has joined #openstack-meeting-311:55
*** topol_ has joined #openstack-meeting-311:55
*** bauzas has joined #openstack-meeting-311:56
*** matrohon has joined #openstack-meeting-311:56
*** dansmith has joined #openstack-meeting-311:56
*** devananda has joined #openstack-meeting-311:56
*** mtreinish has joined #openstack-meeting-311:56
*** mariannelm has joined #openstack-meeting-311:56
*** dansmith is now known as Guest4110011:56
*** armax has joined #openstack-meeting-311:56
*** sambetts_ is now known as sambetts11:56
*** tdurakov has joined #openstack-meeting-311:56
*** bobmel has joined #openstack-meeting-311:58
*** mickeys has joined #openstack-meeting-311:58
*** serverascode has quit IRC11:59
*** serverascode has joined #openstack-meeting-312:00
*** lkoranda has joined #openstack-meeting-312:02
*** mickeys has quit IRC12:03
*** rtheis has joined #openstack-meeting-312:14
*** tuanluong_ has quit IRC12:14
*** tuanluong has quit IRC12:14
*** yamamoto has quit IRC12:36
*** yamamoto has joined #openstack-meeting-312:38
*** alexismonville has joined #openstack-meeting-312:39
*** alexismonville has quit IRC12:40
*** alexismonville has joined #openstack-meeting-312:40
*** alexismonville has quit IRC12:42
*** psachin has quit IRC12:48
*** alexismonville has joined #openstack-meeting-312:49
*** sdague has joined #openstack-meeting-312:51
*** yamamoto has quit IRC12:52
*** sdague_ has quit IRC12:54
*** armax has quit IRC12:54
*** psachin has joined #openstack-meeting-312:54
*** sdague_ has joined #openstack-meeting-312:56
*** sdague_ has quit IRC12:56
*** mickeys has joined #openstack-meeting-312:59
*** zhiyong has joined #openstack-meeting-313:02
*** mickeys has quit IRC13:03
*** prateek has quit IRC13:21
*** Anticimex has joined #openstack-meeting-313:25
*** d0ugal has quit IRC13:34
*** d0ugal has joined #openstack-meeting-313:35
*** abalutoiu has joined #openstack-meeting-313:44
*** tellesnobrega has joined #openstack-meeting-313:45
*** tenobreg has quit IRC13:48
*** baoli has joined #openstack-meeting-313:51
*** yamamoto has joined #openstack-meeting-313:55
*** salv-orlando has joined #openstack-meeting-313:56
*** marst has quit IRC13:57
*** sankarshan_away is now known as sankarshan13:57
*** mickeys has joined #openstack-meeting-314:00
* fungi yawns14:00
EmilienMhello14:00
gothicmindfoodohhai14:00
* gothicmindfood got back from her errands in time14:00
ttxalright14:01
gothicmindfood#startmeeting openstack-swg14:01
openstackMeeting started Thu Jan  5 14:01:25 2017 UTC and is due to finish in 60 minutes.  The chair is gothicmindfood. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: openstack-swg)"14:01
openstackThe meeting name has been set to 'openstack_swg'14:01
EmilienMo/14:01
gothicmindfoodamrith, dhellmann, gothicmindfood, ttx, jroll, johnthetubaguy, sdague, mordred, carolbarrett, nikhil, mugsie, thingee, alexismonville, edleafe, EmilienM, harlowja, devananda, bastafidli14:01
gothicmindfoodthose are our courtesy pings14:01
jroll\o14:01
johnthetubaguyo/14:02
alexismonvilleo/14:02
gothicmindfoodmy sincere apologies for not updating the agenda, folks14:02
alexismonvillehappy new year :)14:02
gothicmindfoodIt's been a rather long month for me here14:02
gothicmindfoodhappy new year and post-holidays to you all14:02
gothicmindfoodI do think we probably know a bit about what we need to talk about based on our last meeting14:02
ttxjohnthetubaguy posted https://etherpad.openstack.org/p/AtlantaPTG-SWG-TCVision14:03
gothicmindfoodyup14:03
johnthetubaguyyeah, sorry that took a month, but moving it out of gerrit, so we can start work on it14:03
ttxI started to list on that etherpad what the TC actually does, and which we should probably cover in the vision somehow14:03
gothicmindfoodand I have some news on the Atlanta visioning ront as well14:03
johnthetubaguytried to collect some questions from the last meeting too14:03
johnthetubaguyttx: liking that list, thanks14:04
ttxI like to put things into categories :)14:04
gothicmindfoodwhat do you all say that I start with a couple announcements, and then we move on to talking through our overarching vision for the PTG (as the SWG) and then dig into the beginnings of the TC vision etherpad?14:04
gothicmindfooddoes that sound like a decent plan for the hour?14:04
*** mickeys has quit IRC14:05
fungiwfm14:05
EmilienM++14:05
gothicmindfoodsweet.14:05
jroll++14:05
gothicmindfoodOkay - so on the training/PTG front14:05
gothicmindfoodI had a great convo with Timo over at ZingTrain about the week of April 10th being targeted for leadership training14:05
*** marst has joined #openstack-meeting-314:05
gothicmindfoodwhich is awesome14:05
EmilienMgothicmindfood: maybe use #topic so we have a nice summary at the end14:06
gothicmindfoodEmilienM: ah, cool14:06
gothicmindfoodI do when we have an agenda, just failed this time at that :)14:06
gothicmindfood#topic Leadership training & PTG announcements14:06
*** openstack changes topic to "Leadership training & PTG announcements (Meeting topic: openstack-swg)"14:06
* edleafe shuffles in late14:06
gothicmindfoodso - April 10th is the week we're targeting for training14:07
gothicmindfoodit'll be 3 days again - 2 days facilitated and 1 day of after-training discussion hosted for attendees14:07
alexismonvillegreat!14:07
gothicmindfoodI'm still working on getting the full list of invitees together, but ostensibly it'll be any TC members who haven't done it, plus ttx, plus some user committee and hopefully board folks plus anyone else who is interested14:08
gothicmindfoodI got a quote for 20 people to attend again14:08
gothicmindfoodand also managed to get a quote combined with that for a 1 day vision facilitation at the Atlanta PTG14:08
gothicmindfoodwhich ZingTrain is very interested in helpig us out on14:08
gothicmindfoodfrom their perspective: having an outsider facilitate a vision is pretty important, and also having folks who've done large scale visions before might help us in areas where we falter, especially w/r/t keeping on task14:09
*** spzala has joined #openstack-meeting-314:09
*** pgadiya has quit IRC14:09
gothicmindfoodso I wanted to check in with this group before going to the TC about it - how would we feel about taking one day of the PTG for vision facilitation there?14:09
*** marst has quit IRC14:10
*** yamamoto has quit IRC14:10
ttxWe'll have a one-day SWG room there14:10
ttxso that fits the agenda14:10
johnthetubaguyI guess there are quite a few TC folks who will be at other horizontal stuff than the SWG, but its probably the best shot we have14:11
gothicmindfoodttx: kinda. I'm worried about making this vision our whole agenda, especially when so many others in the community seemed to want to learn skills/various things about what we're up to14:11
*** marst has joined #openstack-meeting-314:11
EmilienMdo we know which day ? (during horizontal sessions)14:11
ttxjust creates a bit of constraints as I have a pretty busy Monday/Tuesday14:11
gothicmindfoodwe would choose the day for the vision stuff14:11
gothicmindfoodit could be any day14:11
ttxEmilienM: Monday or Tuesday, undecided yet. Architecture WG is supposed to take the other day14:12
EmilienMttx: cool14:12
johnthetubaguyttx: ah, that makes sense14:12
ttxBy default I'd say Monday for SWG14:12
ttxsince ArchWG is likely to attract more people14:12
fungiyeah, monday/tuesday i'll be running infra stuff all day14:12
johnthetubaguyyeah14:12
ttx(people who might want to travel on Monday)14:12
ttxcould also be a one-day thing on Friday14:12
gothicmindfoodI was wondering about Friday14:12
ttxout of the SWG room14:12
gothicmindfoodor Thursday14:12
ttxin some corner of the venue14:13
johnthetubaguyI can't do friday, but that might give you a bigger number of folks14:13
gothicmindfoodI know people will be pretty exhausted14:13
* fungi expects to start the week exhausted14:13
EmilienMI'm not sure we can satifsfy everyone. Thursday is vertical sessions, some folks will also be busy14:13
ttxThursday I'll likely be stuck releasing the thing known as OpenStack14:13
ttxsame for dhellmann14:13
gothicmindfoodyeah14:13
johnthetubaguyEmilienM: +1 right, people are going to be busy on every day at this point14:13
EmilienMttx: during PTG?14:13
fungioh, right, i forgot thursday at the ptg is release day ;)14:13
gothicmindfoodSo - the biggest thing I'm concerned about is 100% TC attendance14:14
ttxEmilienM: we like difficulty14:14
gothicmindfoodat least at pieces of the day-long session14:14
EmilienM(out of topic but releasing OpenStack during PTG is not the best idea ever)14:14
jrollI seem to remember TC folks thoguht they'd be too tired for a board meeting, I can't imagine they wouldn't be too tired for a full day visioning session14:14
gothicmindfoodso that everyone gets a chance to participate14:14
fungiactually, being able to get all the release team in a room together physically on release day sounds pretty helpful</offtopic>14:14
jroll(but don't remember the final decision on that board meeting thing)14:14
ttxEmilienM: when we discussed it at past Summits it sounded like a good idea14:14
ttx(fwiw we won't do that for the second PTG)14:15
EmilienMcool then :-) good luck!14:15
*** pkoniszewski has quit IRC14:15
*** luzC has quit IRC14:15
ttxwe prefer the PTG week to the week just before or after14:15
alexismonvilleI will not be at the PTG (personal reason) but I would like to say that I would start with the visioning when people are fresh14:15
*** luzC has joined #openstack-meeting-314:15
gothicmindfoodso it sounds like Monday or Friday are the best options for a potential day long visioning session14:15
*** pkoniszewski has joined #openstack-meeting-314:15
gothicmindfoodand I lean towards Monday14:15
johnthetubaguyyeah, I had it in my head we do the release the week after the ptg, duno why14:15
ttxthe week after ptg I'll be sleeping14:16
johnthetubaguyttx: good point14:16
gothicmindfoodttx: you sleep?14:16
gothicmindfood;)14:16
ttxgothicmindfood: the week after events yes14:16
gothicmindfoodweek-after-openstack-event-ttx-hibernation14:16
fungiwhile 100% tc attendance is a great goal, i have serious doubts we'll ever get all 13 tc members' attention so accepting <100% would be more practical14:16
jrollfungi: ++14:16
ttxonly way to get 75% of tc would be to do it outside of PTG week14:17
johnthetubaguyfungi: +!14:17
*** baoli has quit IRC14:17
ttxwe've been on that discussion about a Board+TC meeting14:17
gothicmindfoodfungi: totally get that. My concern is getting 70% of them in the room doing the work and then having the other 30% lacking context and getting upset about the work post-PTG14:17
ttxthe PTg week is basically already more than full for cross-project people14:17
*** baoli has joined #openstack-meeting-314:17
johnthetubaguyso, I had always assumed we would have to find some way to make visioning async, I know thats not normal14:17
*** hoangcx has joined #openstack-meeting-314:17
gothicmindfoodjohnthetubaguy: I think it can be, and should be during a phase of it14:18
fungiwe always find ways to make everything async in our community. sometimes it doesn't work out great, but it's by necessity14:18
gothicmindfoodbut for initial drafting, I think it's best to have folks as syncronous as possible14:18
johnthetubaguynow a selection of folks kick starting things, in a traditional method, responsible for helping the the draft makes sense14:18
gothicmindfoodbut - I certainly understand the crazy schedules at the PTG14:18
johnthetubaguytrouble is, anything synchronous will always exclude folks, I am just saying 50% attendance might be considered a win here, and it has less value, but its better than not doing it14:19
gothicmindfoodokay - alexismonville had a point about freshness/perspective, too, that makes me lean even harder towards the monday14:19
EmilienMright, meeting in person to bootstrap things is best than emails/irc14:19
EmilienMs/best/better/ (imho)14:19
fungimaybe if we took turns as "meeting secretary" recording minutes so that people who missed have more context than just the draft output?14:19
gothicmindfoodttx: how do we confirm that we want an all-day session monday - just with you? :)14:19
fungi(whereby "we" i don't necessarily mean to imply that i'm assuming i'll be present)14:20
gothicmindfoodfungi: we'll be doing a lot of writing and pasting up on walls, so I'm sure we can preserve that14:20
gothicmindfoodin pictures and with transcriptions if necessary14:20
fungiif i get to write on walls in crayon, i'll find a way to be tehre ;)14:20
johnthetubaguyI think promising lots of pictures, a various folks blogs on the event would certainly help14:21
gothicmindfoodfungi: I bet it's scratch-n-sniff sharpies :)14:21
johnthetubaguyfungi: heh14:21
ttxgothicmindfood: it's the default situation14:21
gothicmindfoodttx: okay cool.14:21
ttxWe have a room earmarked for SWG/ArchWG on Monday/Tuesday14:21
gothicmindfoodso I just have to reconfirm with the foundation that we can wrap this into training funding, and then reach out to ZingTrain to coordinate scheduling on that side14:21
ttxas mentioned on http://www.openstack.org/ptg14:21
ttxSo who gets monday and who gets tuesday can be arranged between ArchWG and SWG14:21
gothicmindfood#action gothicmindfood to finalize TC Vision Facilitation timing with Foundation/ZingTrain/TC14:22
gothicmindfoodokay awesome. Thank you for the advice everyone14:22
fungijust to clarify, i don't expect to have any time to be in the swg room monday/tuesday due to ptl responsibilities, but have faith others who are there can do a bang-up job drafting something i'll read and help polish later14:22
gothicmindfoodand please pencil in that week of April 10 on your calendars for leadership training if you'd like to attend14:22
johnthetubaguyI vote we just try it with who can be there, certainly shouldn't be exclusive to TC members14:22
gothicmindfoodjohnthetubaguy: I'm definitely open to that, too14:23
gothicmindfood#topic SWG's PTG Vision14:23
*** openstack changes topic to "SWG's PTG Vision (Meeting topic: openstack-swg)"14:23
gothicmindfood#link https://etherpad.openstack.org/p/AtlantaPTG-SWG14:23
ttxwe could do a TC visioning dinner too. But we all know how that usually turns out14:24
gothicmindfoodso - my next question is if we do a full day visioning session - does that mean our other sessions/ideas get pushed back to another time?14:24
ttxWe seem to have a vision track -> SWG vision -> TC vision -> OpenStack vision. Is tehre anything else we want to actively pursue in the coming months ?14:25
gothicmindfoodttx: I think that's probably the most important goal, but I would like to start digging into a leadership "passport" for OpenStack and what that might look like14:25
gothicmindfoodeven though I think that's a longer term project14:26
ttxok14:26
gothicmindfoodit might be nice to write an SWG vision that goes beyond our presence at events, too :)14:26
*** yamamoto has joined #openstack-meeting-314:27
gothicmindfoodI think we'll all learn a lot from the vision facilitation at the PTG, though14:27
gothicmindfoodare we of a mind that we might have a TC vision finalized by Boston?14:27
johnthetubaguyhonestly, I was assuming lots of the TC vision would end up needing signification support from the SWG, and would help drive a lot of what we do14:27
gothicmindfoodjohnthetubaguy: totally agree with that14:28
johnthetubaguyso I tried to write questions on that etherpad, based on this kind of thing14:28
johnthetubaguyI was thinking there is initial draft, vs finalized14:28
gothicmindfood#link https://etherpad.openstack.org/p/AtlantaPTG-SWG-TCVision14:28
gothicmindfoodjohnthetubaguy: that one ^^ ?14:28
johnthetubaguyinitial draft means the TC has signed off on it maybe?14:28
johnthetubaguyyeah14:28
johnthetubaguysorry, missing context there14:29
johnthetubaguywe were talking about getting UC and board reviews, I was thinking we should get the TC on roughly the same page first, but maybe thats too waterfall?14:30
gothicmindfooddo we think that the TC vision, once a draft is accepted by the TC, should also be pushed to the community more broadly for feedback?14:30
gothicmindfoodas a separate cycle?14:30
gothicmindfoodha. Same question, sorta.14:30
gothicmindfoodI mean, it feels like this whole thing will be iterative in terms of opening up the feedback loops to different groups while we align ourselves with one another14:31
johnthetubaguyI think everyone can be involved in the first cycle14:31
alexismonvilleI think one of the success criteria could be that the TC is committed to publish a first version of the vision by 30 days after the PTG14:31
gothicmindfoodeach group will be inspired to think about how the vision aligns with their own (or doesn't)14:31
gothicmindfoodas they write htem down for the first time14:31
johnthetubaguyI just really wondering what finalised means14:31
jrollgiven this is a vision for the TC, I think it makes sense to get TC on board first :)14:31
alexismonvilleso yes a draft should be available for feedback before14:31
fungi"final" is probably a poor term for the goal there14:32
gothicmindfoodjohnthetubaguy: yeah, right? :)  I imagine finalized might mean, in an official sense, committed to an official governance repo and posted for the world to see14:32
gothicmindfoodbut that doesn't mean it can't change from there, obvs14:32
fungi(i don't expect there will ever be a completely final version of any document in our community)14:32
fungiright, that14:32
gothicmindfoodand one of the powers of a vision is that it expires and you have to make a new one14:32
johnthetubaguyso I think the TC should all agree on something by Boston14:32
persiaPerhaps we could call it an "approved" revision?14:32
gothicmindfoodbecause it's really just about a point in time14:32
johnthetubaguymaybe thats a better way to look at it?14:33
alexismonville+1 for approved revision14:33
gothicmindfoodjohnthetubaguy: I was hoping that by Boston we could have already had a larger community involvement as well14:33
*** lblanchard has joined #openstack-meeting-314:33
fungiapproved sounds good. an agreed-upon and consensual initial revision14:33
johnthetubaguyttx: when is TC elections?14:33
gothicmindfoodbootstrapping the TC in post-PTG by April or so, and then asking for feedback pre-Boston to maybe finalize/publish there?14:33
johnthetubaguywould that be a good aim, get it aggreed before?14:33
fungi#link https://governance.openstack.org/election/14:34
fungijohnthetubaguy: ^14:34
alexismonvilleI think that is needed to give a direction to the different project14:34
fungiwe don't have finalized tc election dates listed yet14:34
gothicmindfoodjohnthetubaguy: yeah, I think agreed on before and then publicized/asking UC & Board for feedback so Boston can be a discussion14:34
fungibut they'll be at least after the ptl elections14:35
ttxjohnthetubaguy: weeks before Boston14:35
johnthetubaguyttx: right, we were re-aligning with that14:35
johnthetubaguywell, not changing it14:35
* gothicmindfood just added a thing in th etherpad for timing14:36
gothicmindfoodlooking at q 1.1 - was there ever a decision made between 18 months and 24 months?14:37
gothicmindfoodit'd be nice to walk into the PTG knowing what our vision timescale is14:38
johnthetubaguymy original thinking was agree it for a timeframe after all those who have voted on it will be re-elected14:38
johnthetubaguythat being the minimum amount of time14:38
*** VW has joined #openstack-meeting-314:38
*** mlavalle has joined #openstack-meeting-314:39
johnthetubaguygothicmindfood: what more normal, longer term?14:39
gothicmindfoodyeah, usually 5-10 years is a common visioning timeframe14:39
gothicmindfoodbut I think there's absolutely a case to do 2 years here14:39
johnthetubaguyleaning longer seems to make sense, so lets start off with two years?14:40
gothicmindfoodis anyone uncomfortable with a 2 year vision?14:40
EmilienMit sounds a lot, but it seems "normal" (/me learning here)14:41
gothicmindfoodI think it works for us pretty well, given the uniqueness of our community14:41
gothicmindfood(changing tech, fluctuating members based on corporate interest, etc.)14:41
*** jbryce has joined #openstack-meeting-314:41
gothicmindfoodso let's say 2 years going into the PTG14:41
gothicmindfoodwe may decide that doesn't work when we get in the room, but I think that's okay too :)14:42
johnthetubaguyseems like a good starting point14:42
alexismonville++14:42
jroll2 years sounds good to me14:44
gothicmindfoodso - out of curiosity - has everyone here read a vision that's outside of OpenStack context before?14:44
gothicmindfoodI think that might be a good thing to recommend, too, before the PTG14:44
johnthetubaguygothicmindfood: can you put those links you sent me before in there as pre-work, thats a good idea14:44
gothicmindfoodmaybe I will post them in the etherpad for folks to read?14:44
jroll++14:44
gothicmindfood#action gothicmindfood to post some visions-as-reference in TC Vision etherpad14:45
johnthetubaguygothicmindfood: added a Recomended Preparation work section14:45
alexismonvillegreat14:45
johnthetubaguyttx: I wonder if we should turn your list on its head?14:45
ttxjohnthetubaguy: what do you mean ?14:46
johnthetubaguyttx: that one you are typing now is more what I was thinking, like listing categorised "problems"14:46
johnthetubaguyright now lots of them are solutions we have proposed14:46
ttxjohnthetubaguy: I built the list based on things we have done in the past, as I summarize them in annual Foundation reports14:47
johnthetubaguylike documenting existing culture helps ensure an inclusive and welcoming environment for open collaboration14:47
ttxclearly there is still room for things we are not doing and should be doing :)14:47
johnthetubaguyyeah, its a good starting point, I guess what I am proposing is a second list14:47
ttxIt's just that we probably need to cover what we are actually doing, too14:47
johnthetubaguy++ covering that14:47
ttxjohnthetubaguy: sounds like a good idea14:47
johnthetubaguynot throwing the baby out with the bathwater, as they save over here14:48
johnthetubaguys/save/say/14:48
gothicmindfoodI'm really excited that we might get a draft vision by the end of the PTG14:49
gothicmindfooddo we want to talk any more about this TC Vision etherpad, or should we move to open discussion for the last 10 minutes?14:50
*** salv-orlando has quit IRC14:50
ttxjohnthetubaguy: the inverted list will be interesting to make sure we identify improvements/aspirations14:50
johnthetubaguyI guess I am curious what the next steps14:51
johnthetubaguyttx: cool, yeah, I like having both lists now I see a little bit of both14:51
johnthetubaguygothicmindfood you are talking to the facilitators14:51
johnthetubaguyrest of us are filling out the lists and questions on the etherpad to get the creative juices flowing, so to speak14:51
johnthetubaguyare we missing an action there?14:52
gothicmindfoodyup. I may ask them to take a peek at that etherpad, too :)14:52
gothicmindfoodI don't think so - I just have to follow through with that setup I mentioned earlier btwn foundation and zingtrain14:52
gothicmindfoodand I already action'd that14:52
gothicmindfooddo you think I should show up at a TC meeting and like, talk about this stuff?14:52
gothicmindfoodor does someone else want to bring it up there?14:53
gothicmindfood;)14:53
* gothicmindfood jokes, but will have a much more normal schedule starting next week and will actually be able to go to meetings again14:53
persiaI think there are enough TC members here that it would be sensible for one of them to represent to the TC14:53
persia(unless that creates unwanted impression of bias)14:53
johnthetubaguyyeah, lets get this on the agenda for next time, as a heads up14:53
gothicmindfoodjohnthetubaguy: dyou want to take that action?14:53
ttxjohnthetubaguy: we can mention it in open discussion14:54
johnthetubaguyttx: yeah, lets do that, simpler14:54
gothicmindfoodyay.14:54
johnthetubaguyI can take that action14:54
fungiseems fine to me (tc hat on)14:54
gothicmindfoodand as a context-filler, I've been remarkably absent from work life because I've been working on this: http://publictheater.org/Tickets/Calendar/PlayDetailsCollection/UTR/UTR-2017/Hundred-Days/14:54
gothicmindfoodif anyone's in NYC in the next week and wants to come :)14:54
gothicmindfoodnow that we're open, I get my life back14:55
johnthetubaguygovernance repo patches are getting abandoned with a note to see the etherpad too14:55
gothicmindfood#action ttx and johnthetubaguy to bring up vision planning at TC meeting open discussion14:55
alexismonvillecongrats gothicmindfood14:56
gothicmindfoodalexismonville: thanks! :)14:56
gothicmindfoodanything else for our last 4 minutes?14:56
*** sankarshan is now known as sankarshan_away14:57
*** janzian has joined #openstack-meeting-314:57
gothicmindfoodalright - I'm going to give folks a couple minutes back, then. we can take the rest of convo over to #openstack-swg as usual14:57
gothicmindfoodthanks so much everyone!14:57
gothicmindfood#endmeeting14:57
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:57
openstackMeeting ended Thu Jan  5 14:57:57 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_swg/2017/openstack_swg.2017-01-05-14.01.html14:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_swg/2017/openstack_swg.2017-01-05-14.01.txt14:58
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_swg/2017/openstack_swg.2017-01-05-14.01.log.html14:58
ttxThanks gothicmindfood!14:58
johnthetubaguy+114:58
*** absubram has joined #openstack-meeting-314:58
mlavalle#startmeeting neutron_l315:00
openstackMeeting started Thu Jan  5 15:00:22 2017 UTC and is due to finish in 60 minutes.  The chair is mlavalle. 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
*** mickeys has joined #openstack-meeting-315:00
mlavallehi there!15:00
janziano/15:01
haleybhappy new year15:01
*** spotz_zzz is now known as spotz_15:01
mlavallehaleyb, janzian: happy new year!15:01
baolihi,happy new year15:01
mlavallewelcome baoli !15:01
mlavalle#topic Announcements15:02
*** openstack changes topic to "Announcements (Meeting topic: neutron_l3)"15:02
*** anilvenkata has quit IRC15:02
mlavalleAgenda for today is here: https://etherpad.openstack.org/p/neutron-l3-subteam15:02
*** cleong has joined #openstack-meeting-315:03
mlavalleWe are less ~ 3 weeks from Ocata-3: January 23 - 2715:04
mlavalle#link https://releases.openstack.org/ocata/schedule.html15:04
*** bobmel has quit IRC15:05
mlavalleBefore we now it, it will be Project Team Gathering time, February 20 - 2415:05
mlavalle#link https://www.openstack.org/ptg/15:05
mlavalleany other announcements?15:06
*** mickeys has quit IRC15:06
*** psachin has quit IRC15:06
haleybYes, we need to start a wiki page for discussion topics (if someone hasn't already)15:06
mlavallehaleyb: for the PTG?15:07
haleybmlavalle: yes15:07
mlavallewhy not an etherpad?15:07
*** janzian_ has joined #openstack-meeting-315:08
*** janzian has quit IRC15:08
mlavalleI find them friendlier15:08
*** janzian_ is now known as janzian15:08
haleybmlavalle: because wiki is easier to type :)  yes, i meant etherpad15:08
mlavalleLOL, ok..... I'll start one if you want and send a message to the ML. Does that work?15:09
haleybmlavalle: well there might already be a neutron one, i just haven't checked15:09
mlavallehaleyb: ahhh, ok. Maybe we can ask this question on Monday, during the Neutron meeting15:10
mlavalleI haven't seen a message in the ML from armax15:10
haleybsounds good15:11
mlavalle#action mlavalle to question about PTG etherpad during the next Neutron meeting15:11
mlavalle#topic Bugs15:11
*** openstack changes topic to "Bugs (Meeting topic: neutron_l3)"15:12
*** prateek has joined #openstack-meeting-315:13
*** Guest41100 is now known as dansmith15:15
mlavalleWith the holidays slowdown there hasn't been much change in the overall picture15:15
mlavalleFirst one is https://bugs.launchpad.net/neutron/+bug/161048315:15
mlavalleThis is the one about the IPAM rollback mechanism not being robust enough15:15
mlavalle(bot seems to be slow today)15:15
openstackLaunchpad bug 1610483 in neutron "Pluggable IPAM rollback mechanism is not robust" [High,In progress] - Assigned to Aliaksandr Dziarkach (aliaksandr-dziarkach)15:15
mlavalleProposed fix is here: https://review.openstack.org/39059415:15
mlavalleI encourage folks to review the fix15:15
*** dansmith is now known as Guest5735515:15
mlavalleany other comments?15:15
*** Guest57355 is now known as dansmith15:16
mlavalleok, next up is https://bugs.launchpad.net/neutron/+bug/157012215:16
openstackLaunchpad bug 1570122 in neutron "ipv6 prefix delegated subnets are not accessable external of the router they are attached." [High,In progress] - Assigned to John Davidge (john-davidge)15:16
mlavallejohn-davidge is working on this one. Proposed fix is https://review.openstack.org/#/c/407025/15:17
haleyblooks to just need a test15:18
mlavallesince john-davidge is off this week, we won't see any change until next week15:18
mlavalleyeah, I think he will address that when he comes back15:19
*** spzala has quit IRC15:19
mlavalleany other comments?15:19
*** sdake has joined #openstack-meeting-315:20
*** bobmel has joined #openstack-meeting-315:21
mlavalleNext one is https://bugs.launchpad.net/neutron/+bug/162742415:21
openstackLaunchpad bug 1627424 in neutron "FlushError on IPAllocation" [High,Confirmed] - Assigned to Miguel Lavalle (minsel)15:21
mlavalleWe've had 17 hits of this one over the past week15:21
mlavalleIt mostly happens as a consequence of rally tests15:22
mlavalleIN those cases, it happens when deleting a subnet15:22
mlavallewhen deleting the ports15:22
mlavalleI am narrowing it down from there right now15:23
*** sdake_ has joined #openstack-meeting-315:23
mlavalleany comments, advice, questions?15:23
*** zz_dimtruck is now known as dimtruck15:23
haleybthanks for continuing to look at it miguel15:24
mlavalle:-)15:24
*** prateek has quit IRC15:24
*** bobmel has quit IRC15:25
*** sdake has quit IRC15:25
mlavalleThere are other paths that trigger it, but yesterday I decided to exhaust the rally one in my digging. That way I can accumulate some knowledge. Let's see where I get over the next couple of days15:25
mlavalleNext one is https://bugs.launchpad.net/neutron/+bug/162748015:26
openstackLaunchpad bug 1627480 in neutron "create_port can succeed without returning fixed_ips on all requested subnets" [High,Confirmed]15:26
mlavalleI don't have any updates here, other than when I am done with the previous one, I'll pursue this one. If someone wants to take it please go ahead15:27
mlavalleany other bugs from the team?15:28
mlavalleok....15:29
mlavalle#topic Prefix Delegation15:29
*** openstack changes topic to "Prefix Delegation (Meeting topic: neutron_l3)"15:29
mlavalleany updates baoli?15:29
baolimlavalle: I have a couple of patches for review, both of them have passed jenkins15:30
*** prateek has joined #openstack-meeting-315:30
*** bobmel has joined #openstack-meeting-315:30
baolihaleyb: thanks for review and the +215:30
haleybbaoli: thanks for the change, i need to get to the other review15:31
*** prateek has quit IRC15:31
mlavallebaoli: ok, I'll take a look at https://review.openstack.org/#/c/408306/15:32
*** prateek has joined #openstack-meeting-315:32
baolimlavalle: thanks!15:32
mlavallebaoli: most likely I'll do it tomorrow :-)15:33
*** salv-orlando has joined #openstack-meeting-315:34
mlavalleany other comments?15:34
mlavalleok15:34
mlavalle#topic Service Subnets15:34
*** openstack changes topic to "Service Subnets (Meeting topic: neutron_l3)"15:35
mlavalleI see good progress was made on https://review.openstack.org/#/c/411463/15:35
mlavallebefore the holidays15:35
mlavallethe docs guys are reviewing it15:35
mlavalleany other comments?15:36
haleybmlavalle: i was going to update it today, but others were nice to update while i was out15:36
mlavalleyeah, I can see it15:36
mlavalleLet's keep an eye on it:-)15:36
*** tonytan4ever has joined #openstack-meeting-315:37
mlavalle#topic Routed Networks15:37
*** openstack changes topic to "Routed Networks (Meeting topic: neutron_l3)"15:37
mlavalleOn this topic I made great progress over the holidays (while juggling visiting kids and wife)15:37
mlavalleI have two patchsets up for review15:38
*** d0ugal has quit IRC15:38
mlavalleThe first one is the ReST client that we need in Neutron to talk to the placement API in Nova to update it about the availability of IPv4 addresses in routed networks subnets15:39
mlavalle#link https://review.openstack.org/#/c/414726/15:39
*** qwebirc1221 has joined #openstack-meeting-315:39
*** rosmaita has joined #openstack-meeting-315:39
*** qwebirc1221 has quit IRC15:39
mlavalleI tested it extensively over the holidays and is fully functional. I encourage folks to review it15:40
* haleyb adds to review queue15:40
mlavalleThe second one is the piece in Neutron server that uses the aforementioned client to actually update Nova with the IPv4 inventories15:41
mlavalle#link https://review.openstack.org/#/c/35865815:41
*** d0ugal has joined #openstack-meeting-315:41
mlavalleI also tested it extensively over the holidays. It is also fully functional, with a little exception15:41
*** elmiko has joined #openstack-meeting-315:42
mlavalleduring my testin I uncovered a bug on the Nova side:15:42
mlavalle#link https://bugs.launchpad.net/nova/+bug/165264215:42
openstackLaunchpad bug 1652642 in OpenStack Compute (nova) "Nova API doesn't return aggregate's uuid, which is needed when using the placement API" [High,In progress] - Assigned to Jay Pipes (jaypipes)15:42
haleybmlavalle: so holidays != rest ? :)15:43
janzianIn his case, holidays = ReST15:43
mlavalleThe Nova team jumped at it really quickly so I am getting all the help I need from that side15:43
haleybjanzian: nice one!15:44
janzian:)15:44
mlavalleI encourage people to review the code in my patchset. The places where the bug affects it is very well isolated and marked with TODOs15:44
mlavalleso I think we can make progress in parallel with the Nova guys if Neutron reviewers take a look at the code ignoring those few TODOs15:45
mlavalleany questions / comments?15:46
mlavalleI plan to update the blueprint with this progress prior to the Neutron meeting on Monday15:47
mlavalle#topic Open Agenda15:48
*** openstack changes topic to "Open Agenda (Meeting topic: neutron_l3)"15:48
mlavalleAny other topics from the team?15:48
mlavalleGoing once....15:49
*** reedip_outofmemo has joined #openstack-meeting-315:49
*** VW has quit IRC15:49
mlavalleGoing twice....15:49
mlavalleSold!15:50
mlavalle#endmeeting15:50
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:50
openstackMeeting ended Thu Jan  5 15:50:18 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:50
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_l3/2017/neutron_l3.2017-01-05-15.00.html15:50
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_l3/2017/neutron_l3.2017-01-05-15.00.txt15:50
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_l3/2017/neutron_l3.2017-01-05-15.00.log.html15:50
mlavalleThanks for attending guys!15:50
haleybthanks mlavalle15:50
*** ocartier_ has quit IRC15:52
*** spzala has joined #openstack-meeting-315:52
*** janzian has left #openstack-meeting-315:52
*** bobmel has quit IRC15:53
*** spzala has quit IRC15:53
*** spzala has joined #openstack-meeting-315:53
*** salv-orl_ has joined #openstack-meeting-315:53
*** VW has joined #openstack-meeting-315:54
*** stevelle has joined #openstack-meeting-315:55
*** salv-orlando has quit IRC15:56
*** cdent has joined #openstack-meeting-315:58
*** nkrinner is now known as nkrinner_afk15:59
cdent#startmeeting api-wg16:00
openstackMeeting started Thu Jan  5 16:00:00 2017 UTC and is due to finish in 60 minutes.  The chair is cdent. 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
elmikohola16:00
cdenthello! who has shown up from the api-wg meeting?16:00
rosmaitao/16:00
sigmavirushello, e'rybody!16:00
cdent#chair elmiko etoews edleafe16:00
openstackCurrent chairs: cdent edleafe elmiko etoews16:00
cdent#link https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda16:00
cdentThere's, like, actual stuff on the agenda this week!16:01
etoewso/16:01
cdent#topic previous action items16:01
*** openstack changes topic to "previous action items (Meeting topic: api-wg)"16:01
cdent#link last meeting http://eavesdrop.openstack.org/meetings/api_wg/2016/api_wg.2016-12-15-16.01.html16:01
elmikoooh neat16:01
cdentagitating about capabilities (done)16:01
*** sdake_ has quit IRC16:02
*** stevejims has quit IRC16:02
cdented making some new guidelines on booleans and state status (done)16:02
cdent#topic Glance Community Images and the API stability guidelines (rosmaita)16:03
*** openstack changes topic to "Glance Community Images and the API stability guidelines (rosmaita) (Meeting topic: api-wg)"16:03
cdent#link https://etherpad.openstack.org/p/glance-ocata-community-images-api-stability16:03
*** sdake has joined #openstack-meeting-316:03
cdenttake it away rosmaita16:03
rosmaitathanks16:03
rosmaita#link https://etherpad.openstack.org/p/glance-ocata-community-images-api-stability16:03
*** VW_ has joined #openstack-meeting-316:03
rosmaitayou may have seen the item on the ML before the holidays16:03
*** mickeys has joined #openstack-meeting-316:03
rosmaitathe etherpad linked above has the basic info about my question16:04
rosmaitaprobably best to read through the etherpad?16:04
elmikoreading now16:04
*** VW_ has quit IRC16:05
* rosmaita sits on his hands16:05
elmikolol16:05
*** VW_ has joined #openstack-meeting-316:05
cdentI'l start by saying that I don't agree with the evaluating api changes document, but it is the "standard" that we have.16:06
*** ocartier has joined #openstack-meeting-316:06
sigmaviruscdent: what don't you agree with?16:06
*** VW has quit IRC16:06
sigmavirusIt's also not as if all standards are written in stone16:07
cdentnor do I agree that tempest maintainers shoud be the arbiters of what is correct behavior in an api16:07
elmikorosmaita: question about the visibility stuff, are these values in the body response?16:07
sigmaviruselmiko: they're both request parameters and response body parameters iirc16:07
cdentbut I make both comments as an independent observer, not as API-WG core™16:07
* sigmavirus is here with Glance and also not with Glance ;)16:07
elmikosigmavirus: ack, thanks16:07
elmikonice16:07
rosmaitaelmiko: what sigmavirus said16:07
*** mickeys has quit IRC16:08
* stevelle is like sigmavirus16:08
* sigmavirus is also here to discuss pagination 16:08
elmikoas to #1, i don't see why that is not possible16:08
etoewsthe way i read it is that the tempest maintainers are being the arbiters of backwards incompatible changes but i may not have all of the context16:08
elmikoif you are rev'ing the version anyways, seems ok to expand those definitions16:09
sigmaviruselmiko: I agree. It's an API expansion which I always  understood to be acceptable16:09
sigmavirusetoews: agreed with you16:09
rosmaitaelmiko: i bring it up, becase a literal reading of the guideline seems to rule it out16:09
elmikocorrect me if i'm wrong, but i thought with the new versioning changes we are bumping the major release for each openstack version. so, wouldn't that dictate that backward incompat changes are acceptable?16:10
sigmaviruselmiko: which versioning changes?16:10
elmikorosmaita: ok, let me re-review the guidance16:10
sigmavirusas in Glance 13.0.0 to 14.0.0?16:10
elmikosigmavirus: yeah, not exactly new. bad phrasing on my part.16:10
cdentelmiko: I don't think that applies to exposed HTTP APIs16:11
elmikocdent: ah16:11
sigmaviruselmiko: right, so I've disagreed with the way openstack versions and does "semantic versioning" for a long time but that does not really follow convention or defacto rule son backwards compat16:11
elmikoyeah, certainly seems that way16:11
* edleafe is back16:12
cdentrosmaita: can I present a summary to you so you can tell me if my brain is wrong?16:12
sigmaviruselmiko: yeah, the APIs are versioned independently of the software16:12
rosmaitacdent: fire away!16:12
sigmaviruscdent: that'd probably benefit everyone :)16:12
cdentBefore 2017 there was a long an arduous debate about how to deal with visibility. That reached a conclusion that didn't make everyone happy but at least made everyone not want to burn it all to the ground. Then16:13
*** rmart04 has quit IRC16:13
cdentimplementation of that solution has resulted in a conflict with the norms enforced in tempest16:14
cdentbecause behavior has changed16:14
*** VW_ has quit IRC16:14
cdenta proposal to work around that changed behvior by changing the test has been rejected as that is, in fact, a work around, and as such violates proper backwards compatibility16:14
*** VW has joined #openstack-meeting-316:15
sigmaviruscdent: correct thus far16:15
cdentthus we are now trying to decide which norms to follow, which to break, or just some way to move foward16:15
rosmaitarem acu tetigisti16:15
stevelleit isn't terribly important, but I'll point it out: the tempest test in question was added during Ocata16:15
*** yamamoto has quit IRC16:16
cdentIf that's all correct, my only source of confusion is really around: what are we trying to decide? What are our options? Do we want to/think we can tell tempest to do things differently?16:16
*** sdake has quit IRC16:16
rosmaitahere's the situation16:16
cdentstevelle: I think that's a pretty important consideration16:16
rosmaitathe specific test breaks if you include an optional 'visibility' when creating an image16:17
cdent(the age of the test)16:17
rosmaitaif you don't include the optional 'visibility', it would pass16:17
rosmaitaso our opinion is that the change is "mostly" backward compatible16:18
rosmaita(or *my* opinion, anyway)16:18
sigmaviruscdent: specifically if you say you want your image to have "visibility = private" and then try to share it, that's what breaks16:18
edleaferosmaita: was 'visibility' a valid param in the past?16:18
sigmavirusedleafe: yes16:18
edleafesigmavirus: then it breaks the API16:18
rosmaitaedleafe: the break doesn't happen in the creation of the image16:19
elmikois there an issue with simply expanding the tempest tests for visbility, or does that run against the backward compat issue?16:19
stevelleedleafe: it was default to private, and the other choice (public) was limited by to admin by RBAC by default16:19
edleafe...or at least the tempest test16:19
rosmaitait happens when you try to add a member to the image16:19
etoewsi don't suppose you have any real data on who is depending on the current behaviour in real life (non-tempest-wise)16:19
sigmavirusedleafe: I absolutely sympathize with that, but I think along those lines that this will break the API regardless based on what tempest suggests we do16:19
clarkbrandom drive by comment, these changes are particularly bad for users when there is no way to discover whether or not such a param is valid from the outside16:19
rosmaitaclarkb: the param is valid16:19
clarkbif I have been using it for years then all of a sudden it stops working on some portion of my clouds then I have a bad day16:19
rosmaitawhat happens is that what you can do with your image depends on what visibility you give it16:20
sigmavirusedleafe: a similar test could create the image with visibility "private", add an image and then assert the visibility is still private afterwards. The "workaround" the tempest team suggested will break that16:20
sigmavirusThat's not meant to justify anything, just to give perspective that really the whole thing can be considered breaking, especially provided a user isn't already familiar with glance or changes introduced in ocata16:21
cdentmy understanding from the pre-2107 debate was that there was awareness that this chang was going to have user impact but that it was an important change to make a better future, the past was a bug, and this is pain that just needs to be eaten, now.16:21
edleafeWell, unless the existing test is invalid or incorrect in what it tests (which happens a lot), then the change isn't backwards compatible16:21
sigmavirusIf a user creates the image, adds a member to it, and then sees that it's suddenly marked as "shared" instead of "private" I have to wonder if they'll be surprised by that or not16:21
cdentIf my statement is correct, then I would think that changing tempest is the right thing to do.16:22
stevelleedleafe: see above, where it is not claimed to be backwards compatible16:22
clarkbrosmaita: right my specific thing is don't change behavior without any way of making it discoverable between clouds that otherwise appear the same to the user (which I think is the case here if I am reading about why tempest fails. Yesterday it was fine, today not, clouds look the same)16:22
stevelleclaimed to be mostly*16:22
elmikocdent: +116:22
*** VW_ has joined #openstack-meeting-316:22
sigmavirusclarkb: so you're right. Since Glance doesn't have microversions, there's no way for a user to get yesterday's behaviour back16:23
rosmaitacdent: i agree with your "my understanding" comment above16:23
*** VW has quit IRC16:23
sigmavirusBut Glance will report that the version has changed which is a pittance of a way to discover the new version16:23
*** tobybot11 has joined #openstack-meeting-316:23
sigmavirus(or changes)16:23
etoewssigmavirus: if you add a member, how could it be considered anything but shared? it's literally being shared.16:23
edleafesigmavirus: this would be a non-issue with microversions16:23
sigmavirusetoews: because right now it remains private16:23
sigmavirusedleafe: agreed16:23
clarkbsigmavirus: right and that to me is the actual major issue with these changes16:24
clarkbsigmavirus: it makes using openstack as a user incredibly frustrating16:24
sigmavirusclarkb: I'm 100% with you16:24
sigmavirusWe have a vocal minority in glance that's opposed to microversions16:24
edleafeSo it's a trade-off of one frustrating thing for another potentially frustrating thing16:24
rosmaitaclarkb: the tradeoff is that the visibility semantics will now make sense16:24
edleafejust different users being frustrated16:25
rosmaitaedleafe: +116:25
stevelleedleafe: agreed16:25
sigmavirusedleafe: correct. And don't get me wrong. I absolutely think this behaviour is a huge improvement16:25
cdentthe theory is: fewer users being frustrated16:25
edleafecdent: fewer is better, unless it's in a serious way16:25
clarkbrosmaita: edleafe yes but the impact to someone who is now broken in production and has no clue why vs someone learning funky semantics vs just telling the user whats up properly are not the same16:25
edleafeclarkb: makes sense16:26
cdentwe need to timebox this in some fashion.16:26
sigmavirusAdditional consideration: This change also auto-migrates existing images16:26
sigmavirusSo private images with members will automagically become shared after this change16:26
rosmaitaclarkb: the change is designed so that if you use defaults, everything works the same16:26
rosmaitaso don't anticipate problems in production systems16:26
sigmavirus^ is very true16:27
etoewsthat's significant16:27
cdentFrom what I recall the discussion of the details of the change were _well_ trod when making the spec and discussing the email. We don't want to revisit that now.16:27
edleafesigmavirus: how serious is that?16:27
edleafesigmavirus: IOW, is it a potential security hole?16:27
*** jokke_ has joined #openstack-meeting-316:27
sigmavirusedleafe: is what a potential security hole?16:27
sigmavirusauto-translating image visibility?16:27
stevelleedleafe: it is backwards compatible16:27
sigmavirusI think it is16:27
edleafesigmavirus: yeah16:27
etoewsglance is clearly making a real effort to mitigate the risk16:28
edleafeE.g.: I made this private, but suddenly it's shared16:28
clarkb(I don't intend to retrod anything, just want to point out that to me as a user that is the actual concern, I think improving APIs is great we just need to be better and communicating to users how things have changed across clouds)16:28
sigmaviruscopy-paste wrong image-id and now you've shared an image, but that's the same thing as the current behaviour16:28
sigmavirusso it's not a new risk16:28
sigmavirusclarkb: agreed16:28
sigmavirusedleafe: right now "private" can mean "private" or "private with members == shared"16:28
rosmaitathat's the key problem, i think16:28
*** hoangcx has quit IRC16:29
rosmaita'private' != "private"16:29
edleafesigmavirus: I only ask because unless it would do something horribly nasty, it sure sounds like this change would be a big improvement16:29
elmikoyeah, that seems imprecise16:29
cdentSo let me ask again: How can the api-wg help in this matter, now?16:29
rosmaitathe issue is whether this change would violate the guidelines16:30
jokke_edleafe: really only nastyness it does is that it breaks one very precise tempest test16:30
rosmaitathe -1 on the tempest patch says it does16:30
sigmaviruscdent: I think Glance is just stuck on technicalities with guidelines and dealing with Tempest's/QA Team's feedback16:30
*** baoli has quit IRC16:31
edleafejokke_: which means it doesn't do anything nasty to actual users16:31
cdenta) they are just guidelines, they are violated all the time b) the existing semantics are (to me) a bug, at least mentally a security bug, so gravy16:31
cdentwhere "gravy" means "the guidance approves"16:31
elmikoi tend to agree with cdent16:31
edleafeSo could a case be made that the existing Tempest test suffers from the same imprecision?16:32
jokke_edleafe: and anyone who has bee creating images with --visibility='private' will need to first change the image to shared before running the member actions16:32
edleafe(as the private has more than one meaning)16:32
sigmavirusedleafe: the current test represents a potential real usage of Glance16:32
rosmaitaedleafe: what i'd say is this: the existing test explicitly says to create a private image16:32
rosmaitathen, when you share it, it fails, as it should16:32
rosmaita(though, currently, it would succeed)16:32
jokke_cdent: we've actually had multiple bugs opened complaining that private is really not private16:33
rosmaitathe test would succeed if you (a) created an image with no viz specified, or (b) created it with viz == shared16:33
edleafeSo it currently passes on something that should really be a failure?16:33
sigmaviruswe also don't recommend that users specify visibility necessarily but allow it16:33
sigmavirusedleafe: ugh that's half-true, I guess?16:33
jokke_edleafe: correct16:33
cdentYeah sounds like the test is pretty much wrong16:33
sigmavirusI mean presently with only two visibilities, a failure is hard to quantify16:33
stevelleso as an action, either replies in support of changing the tempest test to support the spec as written, or responses to the tempest change may be helpful16:33
sigmavirusBecause public visibility's members don't matter16:34
sigmavirusAnd I don't think you can add members to "public" images now16:34
sigmavirusSo you have to have a private image to add a member16:34
jokke_edleafe: not by design should fail but by any basic logic should fail16:34
cdentcan someone # link the review of the tempest in here please?16:34
sigmavirusSo it's a failure and it's a not failure too16:34
edleafeThen I think it's clear that the test should be changed if it passes on a disallowed action16:34
stevellehttps://review.openstack.org/#/c/414261/16:34
*** ocartier_ has joined #openstack-meeting-316:34
cdentthanks16:34
sigmavirusGlance's visibility logic is just really bad presently16:34
cdent#action (everyone) go comment on tempest test change https://review.openstack.org/#/c/414261/16:34
etoewsi abhor backwards incompatible changes but the current behaviour really is a bug and flat out needs to be fixed. i lean towards it being acceptable.16:34
* edleafe doesn't hold tests as sacred16:34
cdentwe need to move on16:34
rosmaitaok, thanks everyone16:35
elmikosigmavirus: seems like it16:35
rosmaitai think this has been helpful, let's see what the QA team says16:35
cdentthat was fun16:35
sigmavirus(That's not the only thing that has that description in glance though =P)16:35
jokke_thanks all ... we really appreciate your time on this!16:35
*** ocartier has quit IRC16:35
cdent#topic open mic16:35
*** openstack changes topic to "open mic (Meeting topic: api-wg)"16:35
cdentresource actions came up again shortly before christmas16:36
elmikosigmavirus, rosmaita, jokke_, thanks for bringing it up =)16:36
cdent#link resource actions email: http://lists.openstack.org/pipermail/openstack-dev/2016-December/109136.html16:36
cdentthe usual three perspectives on that were represented, with the usual lack of consensus16:36
cdentI mention it here because it is something we probably need to continue to think about as it is going to keep coming back up16:36
*** stevejims has joined #openstack-meeting-316:37
cdentthoughts for the record? or if you want to add to that thread, that would be cool. Or if you want to resurrect the guideline process that would be cool too.16:38
cdentIf not, I'll move on.16:38
edleafeI added my thoughts to the thread16:38
cdentWho added the boston cfp link?16:39
etoewsmoi16:39
cdent#link boston cfp: https://www.openstack.org/summit/boston-2017/call-for-presentations/16:39
etoewsjust as a reminder that we need to do the usual song and dance for boston16:39
cdentNot confirmed but I predict I will not be there (I won't be at ptg either).16:40
edleafeI will be at ptg, but boston is still a question mark16:40
etoewsboth are questionable for me as well16:40
cdentelmiko?16:41
elmikoi highly doubt i'll be able to attend, unless i pay my own way there16:41
elmikomaybe, if i got a paper accepted about the stuff i'm currently working on, but it's kinda removed from the openstack world. sadly16:42
cdentnext open mic topic: Do we want to have a process/discussion about setting some 2017 goals, or shall we go with the flow?16:42
edleafeYou mean like New Years resolutions? :)16:43
elmikohehe16:43
cdentThe world at large thinks we are doing a pretty good job and not overreaching, so the status quo may be just fine16:43
cdentpretty much yeah16:43
cdentthings we plan to do but don't16:43
elmikohmm, given that feedback cdent, go with the flow seems appropriate16:43
elmikoi like the idea of setting some goals16:43
etoewsour new year's resolution is to maintain the status quo16:43
edleafeWe don't have any huge gaping voids that we're aware of, so the flow seems right16:43
elmikoetoews: LOL +116:43
sigmavirusbut that's no fun16:43
cdentmy feelings exactly sigmavirus16:44
sigmavirusalways be agitating16:44
edleafeok, maintain the status quo, but lose 10 pounds16:44
cdentthat too16:44
elmikoour plan for 2017 is to increase overreach?16:44
* sigmavirus wonders if there is weight gain associated with working on OpenStack like there is with college16:44
cdentI personally think we can do more on the aspirational side of thing, but some people think that would be overreach16:44
elmikosigmavirus: don't even get me started...16:44
* rosmaita has experienced the OpenStack weight gain16:45
cdentmetoo@aol.com16:45
sigmaviruscdent: aspirational *ideas* wouldn't be bad16:45
elmikohaha16:45
*** ocartier_ has quit IRC16:45
sigmavirus(Says the person including them in his present review)16:45
etoewsi think one the real issues around this is that we don't necessarily have the bandwidth to take action on the aspirations.16:45
sigmavirus(totally not a shameless plug right there)16:45
elmikoetoews: +116:45
edleafeetoews: true that16:46
sigmavirusetoews: but I thought we were here to lead other's thoughts16:46
etoewsheh16:46
sigmavirusthought leaders don't take action. They come up with actions for others16:46
cdentone thing we could do is propose work/issues for the arch-wg around api stuff16:46
*** prateek_ has joined #openstack-meeting-316:46
cdentjinx!16:46
etoewsto the twitters!16:46
*** gouthamr has joined #openstack-meeting-316:46
* sigmavirus lies face in palm16:46
cdentanyway, don't need to do anything immediately, another one for the "think about" queue16:46
cdent#topic guidelines16:46
*** openstack changes topic to "guidelines (Meeting topic: api-wg)"16:46
cdent#link guidelines https://review.openstack.org/#/q/status:open+project:openstack/api-wg,n,z16:47
cdentwe have some16:47
cdentbut I don't reckon any are ready for freeze (due to xmas)16:47
edleafeyeah, I'd like further review16:47
cdentthe capability one had a lot of discussion in the nova-api meeting recently:16:47
sigmavirusI was wondering if people had comments on edleafe's comment on the pagination review16:47
cdent#link capability in nova-api: http://eavesdrop.openstack.org/meetings/nova_api/2017/nova_api.2017-01-04-13.00.log.html#l-5916:48
edleafeI just kind of threw some of those out there for others to pound on16:48
*** stevejims has quit IRC16:48
edleafesigmavirus: comments on comments?16:48
sigmavirusI don't doubt that having "last" is expensive for some projects, but I wonder if there needs to be mention of optional components on something that's purely aspirational16:48
cdentpeople like clarity, ed's comment corresponds to the one I made earlier about optionality16:49
cdentsome of those are MUST and some are MAY16:49
edleafesigmavirus: I think that someone looking at these as guidelines will try to copy them as closely as possible. It's good to let them know where the pitfalls may lie16:49
sigmavirusSure, I thought I had expanded on that well enough16:49
*** prateek has quit IRC16:49
*** iyamahat has joined #openstack-meeting-316:49
*** ocartier has joined #openstack-meeting-316:50
cdentsigmavirus: i haven't looked at version 4 yet16:50
sigmavirusedleafe: sure, I just think that last tends to be more useful than folks reckon and making it optional will introduce inconsistency where Cinder always includes it and NOva doesn't because it's optional16:50
etoewsi think we can just workflow+1 https://review.openstack.org/#/c/411391/16:50
sigmavirusI don't know that we want to allow that kind of problem16:50
sigmavirusWe could just not recommend "last" at all16:50
edleafesigmavirus: sure, but the reason for paginating in the first place is not having to pull large amounts of data16:51
cdentetoews: go for it16:51
stevelleI think it is helpful to offer explicit stretch goals, like last, but it has to be clear there is no expectation. For those that opt in, it lets them standardize which is helpful.16:51
*** VW_ has quit IRC16:51
edleafestevelle: that's pretty much what I feel16:51
sigmavirusedleafe: agreed. I just feel like there are absolutely ways around pulling large amounts of data to provide "last"16:51
*** VW has joined #openstack-meeting-316:52
stevelleusing the right data structures, ^16:52
edleafesigmavirus: sure, but with a million records, it can be tough to find the one that's 30 from the end :)16:52
etoewscdent: ermmmm...apparently i can't workflow+1 anymore...16:53
edleafe...and do that with every hit on the link16:53
edleafeetoews: need +2s first?16:53
elmikoetoews: +1 on wf for that16:53
etoewsi can't even +2 :P16:54
sigmavirusedleafe: yeah I think if you're only considering pulling it from the database dynamically every time, you'll always have terrible API performance around your pagination16:54
*** sdake has joined #openstack-meeting-316:54
cdentetoews: are you logged in as your usual person?16:54
edleafesigmavirus: and if you're not pulling it every time, it will be stale and pretty much useless16:54
cdentedleafe: that's categorically not true16:55
sigmavirusI disagree strongly, but we have 3 conversations happening right now16:55
edleafesigmavirus: if you want, I can post an update that adds language around last16:55
cdentbut openstack has little experience with effective caching and caching namespaces16:55
etoewscdent: oops. guess not.16:55
sigmavirusI guess large non-OpenStack APIs that do Last consistently and correctly and usefully are just wrong16:55
*** amotoki has quit IRC16:55
sigmavirus(or they don't exist and I'm imagining having worked on them)16:55
*** olaph has joined #openstack-meeting-316:56
cdentso I would _love_ to have a discussion about how openstack is out of date in the api world, but let's leave that for another time please as we only have a few more minutes left16:56
edleafesigmavirus: like I said, it depends on how stale they are16:56
elmikocdent: LOL16:56
cdentare there other things to contend about on the other reviews?16:56
cdentthings we know need to happen: more review on ed's strawmen for booleans and state16:56
cdentmore eyes on the capabiities review because it is being driven by nova and cinder right now and they are not the whole world16:57
cdentand further discussion on the pagination thing so we can reach some consensus16:57
cdentanything else?16:57
cdent#topic bug review16:57
*** openstack changes topic to "bug review (Meeting topic: api-wg)"16:57
cdentThere is a new bug that came along today as a result of a keystone bug.16:58
cdent#link 400 on bad query params: https://bugs.launchpad.net/openstack-api-wg/+bug/165408416:58
openstackLaunchpad bug 1654084 in openstack-api-wg "Listing resources with invalid filters should result in a 400" [Medium,Confirmed]16:58
*** pcaruana has quit IRC16:58
cdentwe have guidance on that issue for bodies, but not that easy to find on query params. that bug says we shoudl16:58
cdentsomebody want to volunteer for that?16:58
cdentif so, assign yourself to the bug16:59
* edleafe takes it16:59
cdentany one eager on the newletter or shall I do it?16:59
*** matrohon has quit IRC17:00
cdentThanks to everyone for coming today, I think we've actually set some good foundation for stuff that matters for the coming year, based on the things we've disagreed about today.17:00
cdentthat's good17:00
cdentso17:00
cdentawesome17:00
cdent#endmeeting17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:00
openstackMeeting ended Thu Jan  5 17:00:16 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/api_wg/2017/api_wg.2017-01-05-16.00.html17:00
elmikothanks all17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/api_wg/2017/api_wg.2017-01-05-16.00.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/api_wg/2017/api_wg.2017-01-05-16.00.log.html17:00
cdentmore in #openstack-sdks for anyone who wants to continue17:00
*** elmiko has left #openstack-meeting-317:01
*** singlethink has joined #openstack-meeting-317:01
*** tobybot11 has quit IRC17:01
*** stevelle has left #openstack-meeting-317:01
etoewsthx!17:01
*** spzala has quit IRC17:02
*** iyamahat has quit IRC17:02
*** spzala has joined #openstack-meeting-317:02
*** cdent has left #openstack-meeting-317:03
*** spzala_ has joined #openstack-meeting-317:04
*** mickeys has joined #openstack-meeting-317:04
*** spzala has quit IRC17:07
*** tellesnobrega has quit IRC17:07
*** spzala_ has quit IRC17:08
*** mickeys has quit IRC17:09
*** seanhandley has left #openstack-meeting-317:11
*** sambetts is now known as sambetts|afk17:13
*** yamamoto has joined #openstack-meeting-317:16
*** yamahata has joined #openstack-meeting-317:17
*** tonytan4ever has quit IRC17:18
*** tonytan4ever has joined #openstack-meeting-317:18
*** tonytan4ever has quit IRC17:23
*** tonytan4ever has joined #openstack-meeting-317:23
*** prateek_ has quit IRC17:24
*** sdake has quit IRC17:24
*** tellesnobrega has joined #openstack-meeting-317:26
*** yamamoto has quit IRC17:26
*** sdake has joined #openstack-meeting-317:29
*** anilvenkata has joined #openstack-meeting-317:34
*** tellesnobrega has quit IRC17:35
*** lpetrut has quit IRC17:37
*** stevejims has joined #openstack-meeting-317:37
*** iyamahat has joined #openstack-meeting-317:38
*** matrohon has joined #openstack-meeting-317:40
*** tbachman has joined #openstack-meeting-317:43
*** anilvenkata has quit IRC17:44
*** tellesnobrega has joined #openstack-meeting-317:46
*** rtheis has quit IRC17:48
*** tonytan4ever has quit IRC17:54
*** tonytan4ever has joined #openstack-meeting-317:54
*** fitoduarte has joined #openstack-meeting-317:55
*** mickeys has joined #openstack-meeting-317:58
*** yamahata has quit IRC17:58
*** yamahata has joined #openstack-meeting-317:59
*** VW_ has joined #openstack-meeting-317:59
*** VW_ has quit IRC17:59
*** MarkBaker has quit IRC18:00
*** VW_ has joined #openstack-meeting-318:00
*** VW_ has quit IRC18:00
*** MarkBaker has joined #openstack-meeting-318:00
*** songole has joined #openstack-meeting-318:01
*** galstrom_zzz is now known as galstrom18:01
*** rkukura has joined #openstack-meeting-318:01
tbachmanFYI for folks attending the group-based-policy IRC meeting — we will be starting a few minutes late. Stay tuned.18:01
*** Swami has joined #openstack-meeting-318:02
*** VW has quit IRC18:02
*** spzala has joined #openstack-meeting-318:04
*** SumitNaiksatam has joined #openstack-meeting-318:07
SumitNaiksatamtbachman: rkukura songole: hi18:07
rkukurahi18:08
tbachmanSumitNaiksatam: hi!18:08
SumitNaiksatamsorry i am late18:08
songolehi18:08
SumitNaiksatam#startmeeting networking_policy18:08
openstackMeeting started Thu Jan  5 18:08:14 2017 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot.18:08
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:08
*** openstack changes topic to " (Meeting topic: networking_policy)"18:08
openstackThe meeting name has been set to 'networking_policy'18:08
SumitNaiksatamhappy 2017 to all!18:08
tbachmanSumitNaiksatam: likewise!18:08
SumitNaiksatamlets starting on the happy note of pending patches18:08
SumitNaiksatam#topic Pending Patches18:08
*** openstack changes topic to "Pending Patches (Meeting topic: networking_policy)"18:08
SumitNaiksatam#link https://review.openstack.org/#/c/416527/18:09
SumitNaiksatam“Set project when doing neutron DB migrations"18:09
SumitNaiksatam(i am picking up the patches which are not driver or nfp-specific"18:09
SumitNaiksatam)18:09
SumitNaiksatamanyone seen this one?18:10
SumitNaiksatamas long as all that this is doing is pointing to the neutron conf directories i am good with that18:10
SumitNaiksatamit didnt seem to break our integration job, so i think this should be good18:10
SumitNaiksatamany objections to the above?18:11
rkukuramakes sense to me, I guess, but I don’t claim to know the config internals18:11
SumitNaiksatamrkukura: same here, hence wanted to check with the team :-)18:12
*** hurgleburgler has joined #openstack-meeting-318:12
SumitNaiksatami will +218:12
SumitNaiksatamnext, “neutron-lib: use L3 constant from neutron-lib” - #link https://review.openstack.org/#/c/414976/18:12
SumitNaiksatammy feeling on this (and the one we will pick after this) is that we need to do the newton refactor first before we can get to this18:13
rkukuraSumitNaiksatam: I +2/+A’d the config patch. Does that one need back-porting?18:13
SumitNaiksatamrkukura: yes, it would18:13
SumitNaiksatamrkukura: thanks18:13
SumitNaiksatamthe integration jobs fail on this presumably because we are still on mitaka, and it doesnt go well with the use of the neutron-lib18:14
rkukuraI do think we should use neutron_lib, at least as far as it exists in mitaka18:14
SumitNaiksatamrkukura: okay, i just checked, it seems that it exists in mitaka18:15
songoleneutron-lib is available in mitaka itself I suppose18:15
rkukuraIts evolved since, but I think the changes in this patch only depend on what’s in it in mitaka, or else UTs would file, right?18:16
SumitNaiksatamokahy my bad18:16
SumitNaiksatamwe are already using neutron_lib18:16
SumitNaiksatamyeah my bad18:16
SumitNaiksatamso need to go back and look at this patch as to why this is failing18:17
SumitNaiksatamnext one - “Change passing session to context in segments db functions” - #link https://review.openstack.org/#/c/400811/18:17
rkukuraHow do you get a context when you don’t have one?18:18
SumitNaiksatami dont think this is a mitaka compatible change18:18
*** stevejims has quit IRC18:18
SumitNaiksatamrkukura: create one?18:19
rkukurasure18:19
rkukuraActually, this patch is just for one function call, not a general change18:19
SumitNaiksatamoh you mean, here where the change is made18:19
*** tonytan4ever has quit IRC18:19
*** tonytan4ever has joined #openstack-meeting-318:20
SumitNaiksatamthe last i checked, the changed behavior that is being referred to in this patch, is in neutron newton18:20
rkukuraSumitNaiksatam: So this release_network_segments signature changed post-mitaka?18:20
SumitNaiksatamrkukura: thats what i recall, but need to double check18:21
rkukuraok18:21
rkukuraSumitNaiksatam: Any idea what this enginefacade change was, and whether we should be using context instead of session in more places (our own DB layets, etc.)?18:22
SumitNaiksatamrkukura: #link https://github.com/openstack/neutron/commit/df7e36c8c8b894ff385e0404b30698f7cb2a2ffb18:23
SumitNaiksatamrkukura: i think Anna had sent out an email, and there are some pointers in that email, but i dont recall enough to summarize here18:23
SumitNaiksatamrkukura: so confirmed, in mitaka its still the old signature #link https://github.com/openstack/neutron/blob/stable/mitaka/neutron/plugins/ml2/managers.py#L25418:24
SumitNaiksatamand that would explain the failed UTs18:24
SumitNaiksatamso unfortunately, this patch would have to wait until the newton catch up (which will hopefully happen soon)18:25
SumitNaiksatamany other patches we need to discuss?18:25
rkukuraright - we need this patch when we support newton, but I’m more concerned about whether we should be passing context everywhere we pass session right now18:25
SumitNaiksatamrkukura: sure, we would need to evaluate that18:26
rkukura#link https://blueprints.launchpad.net/neutron/+spec/enginefacade-switch18:26
SumitNaiksatamactually this signature exists in newton as well: #link https://github.com/openstack/neutron/blob/stable/newton/neutron/plugins/ml2/managers.py18:26
SumitNaiksatamso this is a Ocata feature18:27
SumitNaiksatamrkukura: thanks18:27
SumitNaiksatami think Anna posted this change on the master branches of different projects assuming they are all on Ocata18:27
rkukurait looks like it was addressed in OSLO in kilo18:27
SumitNaiksatamrkukura: okay18:28
SumitNaiksatamsongole: anything at your end we need to look at?18:28
songoleSumitNaiksatam: are you referring to this Enginefacade?18:29
SumitNaiksatamsongole: no, NFP18:29
songoleSumitNaiksatam: no outstanding patches18:29
SumitNaiksatamsongole: oh cool18:29
SumitNaiksatamokay, so if no one has anything else, lets wrap a little early today18:30
SumitNaiksatamrkukura and I have another meeting to catch18:30
SumitNaiksatamthanks all for joining, and happy new year again!18:30
SumitNaiksatambye!18:30
tbachmanSumitNaiksatam: bye!18:30
songolebye18:30
SumitNaiksatam#endmeeting18:31
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:31
rkukurathanks SumitNaiksatam!18:31
openstackMeeting ended Thu Jan  5 18:31:00 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:31
rkukurabue18:31
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_policy/2017/networking_policy.2017-01-05-18.08.html18:31
rkukurabye18:31
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_policy/2017/networking_policy.2017-01-05-18.08.txt18:31
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_policy/2017/networking_policy.2017-01-05-18.08.log.html18:31
*** rkukura has left #openstack-meeting-318:31
*** VW has joined #openstack-meeting-318:35
*** VW has quit IRC18:40
*** baoli has joined #openstack-meeting-318:43
*** hurgleburgler has quit IRC18:48
*** LiberalSquash has joined #openstack-meeting-318:48
*** LiberalSquash has left #openstack-meeting-318:48
*** reedip_outofmemo has quit IRC18:54
*** s3wong has joined #openstack-meeting-319:00
*** VW has joined #openstack-meeting-319:00
*** eliqiao has quit IRC19:04
*** eliqiao has joined #openstack-meeting-319:04
*** bobmel has joined #openstack-meeting-319:10
*** eliqiao has quit IRC19:13
*** harlowja has joined #openstack-meeting-319:16
*** lpetrut has joined #openstack-meeting-319:19
*** iyamahat has quit IRC19:31
*** yamahata has quit IRC19:32
*** SumitNaiksatam has left #openstack-meeting-319:33
*** gouthamr has quit IRC19:39
*** gouthamr has joined #openstack-meeting-319:40
*** salv-orl_ has quit IRC19:41
*** abalutoiu has quit IRC19:50
*** tonytan4ever has quit IRC19:51
*** iyamahat has joined #openstack-meeting-319:51
*** sdake has quit IRC19:52
*** cleong has quit IRC19:53
*** Swami has quit IRC19:54
*** mtanino has joined #openstack-meeting-319:57
*** markvoelker has quit IRC19:59
*** markvoelker has joined #openstack-meeting-319:59
*** marst_ has joined #openstack-meeting-320:01
*** cleong has joined #openstack-meeting-320:02
*** Sukhdev has joined #openstack-meeting-320:02
*** huanxuan has quit IRC20:04
*** marst has quit IRC20:05
*** egallen has quit IRC20:09
*** yamahata has joined #openstack-meeting-320:10
*** bobmel has quit IRC20:15
*** bobmel has joined #openstack-meeting-320:15
*** bobmel has quit IRC20:20
*** VW has quit IRC20:21
*** VW has joined #openstack-meeting-320:23
*** VW has quit IRC20:26
*** VW has joined #openstack-meeting-320:27
*** songole has quit IRC20:30
*** sdake has joined #openstack-meeting-320:41
*** mlavalle has left #openstack-meeting-320:50
*** ddyer has quit IRC20:53
*** ddyer has joined #openstack-meeting-321:00
*** lblanchard has quit IRC21:01
*** tellesnobrega has quit IRC21:08
*** alexismonville has quit IRC21:12
*** salv-orlando has joined #openstack-meeting-321:14
*** tellesnobrega has joined #openstack-meeting-321:16
*** armax has joined #openstack-meeting-321:22
*** reed has quit IRC21:30
*** reed has joined #openstack-meeting-321:32
*** dimtruck is now known as zz_dimtruck21:50
*** salv-orl_ has joined #openstack-meeting-321:53
*** cleong has quit IRC21:54
*** alexismonville has joined #openstack-meeting-321:55
*** salv-orlando has quit IRC21:56
*** zz_dimtruck is now known as dimtruck22:01
*** darrenc is now known as darrenc_afk22:07
*** dimtruck is now known as zz_dimtruck22:13
*** matrohon has quit IRC22:21
*** darrenc_afk is now known as darrenc22:25
*** baoli has quit IRC22:26
*** salv-orl_ has quit IRC22:33
*** bobmel has joined #openstack-meeting-322:34
*** salv-orlando has joined #openstack-meeting-322:36
*** alexismonville has quit IRC22:38
*** bobmel has quit IRC22:39
*** sdake has quit IRC22:39
*** bobmel has joined #openstack-meeting-322:43
*** zz_dimtruck is now known as dimtruck22:45
*** lpetrut has quit IRC22:58
*** marst_ has quit IRC22:59
*** spotz_ is now known as spotz_zzz23:01
*** sdake has joined #openstack-meeting-323:03
*** galstrom is now known as galstrom_zzz23:09
*** gouthamr has quit IRC23:21
*** gouthamr has joined #openstack-meeting-323:22
*** Sukhdev has quit IRC23:22
*** absubram has quit IRC23:28
*** salv-orlando has quit IRC23:45
*** spzala has quit IRC23:46
*** VW has quit IRC23:48
*** singlethink has quit IRC23:51
*** Sukhdev has joined #openstack-meeting-323:53
*** baoli has joined #openstack-meeting-323:56

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