Monday, 2017-02-06

*** caowei has quit IRC00:04
*** EricGonczer_ has joined #openstack-meeting-alt00:11
*** EricGonczer_ has quit IRC00:12
*** jesusaur has quit IRC00:12
*** gouthamr has quit IRC00:12
*** ansmith has quit IRC00:15
*** knangia has joined #openstack-meeting-alt00:17
*** michapma_alt has joined #openstack-meeting-alt00:19
*** FiveBrother-Prof has joined #openstack-meeting-alt00:32
*** mtanino has joined #openstack-meeting-alt00:40
*** jesusaur has joined #openstack-meeting-alt00:40
*** kzaitsev_mb has joined #openstack-meeting-alt00:41
*** ricolin has joined #openstack-meeting-alt00:42
*** pkholkin has joined #openstack-meeting-alt00:44
*** gouthamr has joined #openstack-meeting-alt00:47
*** gouthamr has quit IRC00:55
*** FiveBrother-Prof has quit IRC00:56
*** jistr has quit IRC01:00
*** hiro-kobayashi has joined #openstack-meeting-alt01:08
*** mtanino has quit IRC01:08
*** zhurong has joined #openstack-meeting-alt01:13
*** gongysh has joined #openstack-meeting-alt01:28
*** gongysh has quit IRC01:35
*** gcb has joined #openstack-meeting-alt01:45
*** tovin07 has joined #openstack-meeting-alt01:49
*** gcb has quit IRC01:49
*** gcb has joined #openstack-meeting-alt01:50
*** ianychoi has quit IRC01:52
*** gongysh has joined #openstack-meeting-alt01:52
*** ianychoi has joined #openstack-meeting-alt01:54
*** nadya has joined #openstack-meeting-alt01:55
*** beslemon has joined #openstack-meeting-alt01:57
*** nadya has quit IRC01:59
*** beslemon_ has joined #openstack-meeting-alt02:01
*** beslemon has quit IRC02:01
*** mtanino has joined #openstack-meeting-alt02:02
*** beslemon has joined #openstack-meeting-alt02:03
*** beslemon_ has quit IRC02:05
*** PagliaccisCloud has quit IRC02:05
*** beslemon has quit IRC02:07
*** zz_dimtruck is now known as dimtruck02:08
*** tuanluong has joined #openstack-meeting-alt02:12
*** hiro-kobayashi has quit IRC02:14
*** beekhof has joined #openstack-meeting-alt02:16
*** baoli has joined #openstack-meeting-alt02:21
*** spzala has quit IRC02:21
*** baoli has quit IRC02:22
*** adrian_otto has joined #openstack-meeting-alt02:26
*** adrian_otto1 has joined #openstack-meeting-alt02:27
*** adrian_otto has quit IRC02:31
*** fredli has joined #openstack-meeting-alt02:33
*** yonglihe has joined #openstack-meeting-alt03:14
*** caowei has joined #openstack-meeting-alt03:22
*** jrobinson is now known as jrobinson-afk03:26
*** tenobreg has joined #openstack-meeting-alt03:29
*** mikal has quit IRC03:29
*** toan has quit IRC03:33
*** mhayden has quit IRC03:34
*** mikal has joined #openstack-meeting-alt03:34
*** toan has joined #openstack-meeting-alt03:36
*** ianychoi has quit IRC03:37
*** mhayden has joined #openstack-meeting-alt03:37
*** ianychoi has joined #openstack-meeting-alt03:39
*** nadya has joined #openstack-meeting-alt03:55
*** amotoki has quit IRC03:56
*** tenobreg has quit IRC03:57
*** dimtruck is now known as zz_dimtruck03:59
*** sdake has joined #openstack-meeting-alt03:59
*** nadya has quit IRC04:00
*** zhurong has quit IRC04:04
*** kzaitsev_mb has quit IRC04:04
*** jrobinson-afk is now known as jrobinson04:05
*** links has joined #openstack-meeting-alt04:09
*** amotoki has joined #openstack-meeting-alt04:11
*** ianychoi has quit IRC04:12
*** ianychoi has joined #openstack-meeting-alt04:14
*** hieulq has joined #openstack-meeting-alt04:14
*** jokke__ has quit IRC04:14
*** gongysh has quit IRC04:19
*** fredli has quit IRC04:45
*** david-lyle has joined #openstack-meeting-alt04:46
*** stingaci has joined #openstack-meeting-alt04:48
*** zhurong has joined #openstack-meeting-alt04:50
*** david-lyle_ has joined #openstack-meeting-alt04:50
*** david-lyle has quit IRC04:50
*** trinaths has joined #openstack-meeting-alt04:52
*** david-lyle_ is now known as david-lyle04:52
*** benj_ has quit IRC04:55
*** amotoki has quit IRC05:04
*** janki has joined #openstack-meeting-alt05:05
*** gongysh has joined #openstack-meeting-alt05:10
*** nadya has joined #openstack-meeting-alt05:11
*** nadya has quit IRC05:16
*** sdake has quit IRC05:18
*** david-lyle has quit IRC05:21
*** zhurong has quit IRC05:26
*** amotoki has joined #openstack-meeting-alt05:35
*** mickeys has joined #openstack-meeting-alt05:35
*** adrian_otto1 has quit IRC05:43
*** mickeys has quit IRC05:46
*** stingaci has quit IRC05:47
*** r-mibu has quit IRC05:59
*** r-mibu has joined #openstack-meeting-alt06:00
*** salv-orlando has joined #openstack-meeting-alt06:00
*** pgadiya has joined #openstack-meeting-alt06:04
*** chhavi has joined #openstack-meeting-alt06:09
*** lpetrut has joined #openstack-meeting-alt06:14
*** liuyulong_ is now known as liuyulong06:16
*** sridharg has joined #openstack-meeting-alt06:18
*** links has quit IRC06:19
*** janki has quit IRC06:25
*** links has joined #openstack-meeting-alt06:35
*** mtanino has quit IRC06:46
*** nadya has joined #openstack-meeting-alt06:53
*** links has quit IRC07:05
*** nkrinner_afk is now known as nkrinner07:07
*** tesseract has joined #openstack-meeting-alt07:12
*** gcb has quit IRC07:13
*** vAlexa has quit IRC07:13
*** gcb has joined #openstack-meeting-alt07:14
*** links has joined #openstack-meeting-alt07:17
*** lpetrut has quit IRC07:17
*** iyamahat has joined #openstack-meeting-alt07:18
*** saneax-_-|AFK is now known as saneax07:21
*** tovin07 has quit IRC07:21
*** jprovazn has joined #openstack-meeting-alt07:24
*** florianf has joined #openstack-meeting-alt07:24
*** yamamoto has quit IRC07:25
*** andreas_s has joined #openstack-meeting-alt07:28
*** janki has joined #openstack-meeting-alt07:33
*** mfedosin has joined #openstack-meeting-alt07:36
*** haijie has joined #openstack-meeting-alt07:36
*** iyamahat has quit IRC07:39
*** tremble has joined #openstack-meeting-alt07:44
*** tremble has quit IRC07:44
*** tremble has joined #openstack-meeting-alt07:44
*** ccamacho has joined #openstack-meeting-alt07:48
*** hiro-kobayashi has joined #openstack-meeting-alt07:49
*** salv-orl_ has joined #openstack-meeting-alt07:49
*** haijie has quit IRC07:49
*** gcb has quit IRC07:52
*** salv-orlando has quit IRC07:52
*** gcb has joined #openstack-meeting-alt07:54
*** fzdarsky has joined #openstack-meeting-alt07:56
*** jrobinson has quit IRC07:58
*** rarcea has joined #openstack-meeting-alt07:59
*** apetrich has quit IRC07:59
*** nkrinner has quit IRC08:00
*** nkrinner has joined #openstack-meeting-alt08:00
*** apetrich has joined #openstack-meeting-alt08:02
*** zhurong has joined #openstack-meeting-alt08:03
*** shohel has joined #openstack-meeting-alt08:16
*** shohel has left #openstack-meeting-alt08:16
*** benj_ has joined #openstack-meeting-alt08:24
*** panda|Zz is now known as panda08:25
*** vAlexa has joined #openstack-meeting-alt08:28
*** alexchadin has joined #openstack-meeting-alt08:29
*** dtardivel has joined #openstack-meeting-alt08:34
*** yamamoto has joined #openstack-meeting-alt08:35
*** alexchadin has quit IRC08:40
*** alexchadin has joined #openstack-meeting-alt08:40
*** lpetrut has joined #openstack-meeting-alt08:42
*** links has quit IRC08:45
*** links has joined #openstack-meeting-alt08:45
*** yamamoto has quit IRC08:47
*** vAlexa has quit IRC08:52
*** salv-orl_ has quit IRC08:52
*** ralonsoh has joined #openstack-meeting-alt08:54
*** lifeless has quit IRC08:54
*** lifeless has joined #openstack-meeting-alt08:55
*** mjura has joined #openstack-meeting-alt08:59
*** kzaitsev_mb has joined #openstack-meeting-alt08:59
*** knangia has quit IRC09:00
*** pgadiya has quit IRC09:02
*** pgadiya has joined #openstack-meeting-alt09:04
*** sshnaidm is now known as sshnaidm|afk09:27
*** tovin07 has joined #openstack-meeting-alt09:29
*** salv-orlando has joined #openstack-meeting-alt09:31
*** kzaitsev_mb has quit IRC09:33
*** bogdando has joined #openstack-meeting-alt09:34
*** links has quit IRC09:35
*** itamaro has joined #openstack-meeting-alt09:38
*** derekh has joined #openstack-meeting-alt09:50
*** itamaro has quit IRC09:50
*** chhavi has quit IRC09:51
*** sshnaidm|afk is now known as sshnaidm09:53
*** gcb has quit IRC09:54
*** zhurong has quit IRC09:56
*** nadya has quit IRC10:01
*** vAlexa has joined #openstack-meeting-alt10:02
*** sambetts|afk is now known as sambetts10:06
*** neiljerram has joined #openstack-meeting-alt10:14
*** jokke_ has joined #openstack-meeting-alt10:16
*** chhavi has joined #openstack-meeting-alt10:16
*** caowei has quit IRC10:16
*** MarkBaker has joined #openstack-meeting-alt10:17
*** ricolin has quit IRC10:25
*** tuanluong has quit IRC10:26
*** nadya has joined #openstack-meeting-alt10:27
*** kzaitsev_mb has joined #openstack-meeting-alt10:31
*** pgadiya has quit IRC10:32
*** mkoderer has quit IRC10:36
*** dalgaaf has quit IRC10:41
*** hiro-kobayashi has quit IRC10:42
*** bfernando has joined #openstack-meeting-alt10:43
*** dalgaaf has joined #openstack-meeting-alt10:43
*** yamamoto has joined #openstack-meeting-alt10:45
*** zhurong has joined #openstack-meeting-alt10:45
*** pgadiya has joined #openstack-meeting-alt10:46
*** yamamoto has quit IRC10:48
*** MarkBaker has quit IRC10:51
*** alij has joined #openstack-meeting-alt10:52
*** amotoki has quit IRC10:55
*** ccamacho is now known as ccamacho|lunch10:58
*** mjura has quit IRC11:03
*** alij has quit IRC11:06
*** alij has joined #openstack-meeting-alt11:06
*** alij has quit IRC11:09
*** alij has joined #openstack-meeting-alt11:10
*** nadya has quit IRC11:12
*** alij has quit IRC11:15
*** dsariel has quit IRC11:17
*** rfolco has joined #openstack-meeting-alt11:17
*** alij has joined #openstack-meeting-alt11:17
*** vAlexa is now known as cerealkiller11:17
*** yamamoto has joined #openstack-meeting-alt11:20
*** links has joined #openstack-meeting-alt11:21
*** alij has quit IRC11:21
*** alij has joined #openstack-meeting-alt11:23
*** links has quit IRC11:25
*** alij has quit IRC11:28
*** yamamoto has quit IRC11:31
*** aarefiev_afk is now known as aarefiev11:35
*** amotoki has joined #openstack-meeting-alt11:35
*** gongysh has quit IRC11:39
*** jkilpatr has quit IRC11:40
*** rmart04 has joined #openstack-meeting-alt11:43
*** chhavi has quit IRC11:48
*** chhavi has joined #openstack-meeting-alt11:49
*** kzaitsev_mb has quit IRC11:51
*** kzaitsev_mb has joined #openstack-meeting-alt11:52
*** alij has joined #openstack-meeting-alt11:53
*** dizquierdo has joined #openstack-meeting-alt11:56
*** alij has quit IRC11:57
*** alij has joined #openstack-meeting-alt11:59
*** alij has quit IRC12:01
*** dsariel has joined #openstack-meeting-alt12:02
*** amotoki has quit IRC12:03
*** yamamoto has joined #openstack-meeting-alt12:04
*** ansmith has joined #openstack-meeting-alt12:05
*** yamamoto has quit IRC12:08
*** amotoki has joined #openstack-meeting-alt12:10
*** jkilpatr has joined #openstack-meeting-alt12:12
*** early has quit IRC12:12
*** mjura has joined #openstack-meeting-alt12:13
*** dave-mccowan has joined #openstack-meeting-alt12:14
*** ansmith has quit IRC12:14
*** EricGonczer_ has joined #openstack-meeting-alt12:20
*** bogdando has quit IRC12:21
*** ccamacho|lunch is now known as ccamacho12:21
*** bogdando has joined #openstack-meeting-alt12:21
*** sdague has joined #openstack-meeting-alt12:23
*** mjura has quit IRC12:24
*** clopez has quit IRC12:25
*** early has joined #openstack-meeting-alt12:28
*** clopez has joined #openstack-meeting-alt12:31
*** amotoki has quit IRC12:33
*** saneax is now known as saneax-_-|AFK12:34
*** salv-orlando has quit IRC12:37
*** salv-orlando has joined #openstack-meeting-alt12:40
*** EricGonczer_ has quit IRC12:46
*** trinaths has quit IRC12:50
*** pgadiya has quit IRC13:07
*** julim has quit IRC13:08
*** janki has quit IRC13:09
*** mjura has joined #openstack-meeting-alt13:09
*** janki has joined #openstack-meeting-alt13:09
*** EricGonczer_ has joined #openstack-meeting-alt13:10
*** sdague has quit IRC13:10
*** sdague has joined #openstack-meeting-alt13:12
*** sdague_ has joined #openstack-meeting-alt13:12
*** amotoki has joined #openstack-meeting-alt13:12
*** dprince has joined #openstack-meeting-alt13:15
*** sdague_ has quit IRC13:15
*** jheroux has joined #openstack-meeting-alt13:22
*** gongysh has joined #openstack-meeting-alt13:26
*** EricGonczer_ has quit IRC13:26
*** jcoufal has joined #openstack-meeting-alt13:27
*** jaypipes has joined #openstack-meeting-alt13:30
*** jpena is now known as jpena|lunch13:31
*** mjura has quit IRC13:35
*** EricGonczer_ has joined #openstack-meeting-alt13:37
*** sdake has joined #openstack-meeting-alt13:37
*** amotoki has quit IRC13:38
*** EricGonczer_ has quit IRC13:38
*** pradk has joined #openstack-meeting-alt13:39
*** ansmith has joined #openstack-meeting-alt13:39
*** sdake_ has joined #openstack-meeting-alt13:40
*** chhavi has quit IRC13:42
*** sdake has quit IRC13:44
*** dims_ has quit IRC13:47
*** dims has joined #openstack-meeting-alt13:48
*** dustins has joined #openstack-meeting-alt13:49
*** salv-orl_ has joined #openstack-meeting-alt13:49
*** salv-orlando has quit IRC13:52
*** diga has joined #openstack-meeting-alt13:55
*** _gryf has joined #openstack-meeting-alt13:55
*** PagliaccisCloud has joined #openstack-meeting-alt13:55
*** chhavi has joined #openstack-meeting-alt13:56
*** reedip_ has joined #openstack-meeting-alt13:57
*** gouthamr has joined #openstack-meeting-alt13:58
*** edleafe- is now known as edleafe13:59
*** mriedem has joined #openstack-meeting-alt13:59
edleafe#startmeeting nova_scheduler14:00
openstackMeeting started Mon Feb  6 14:00:19 2017 UTC and is due to finish in 60 minutes.  The chair is edleafe. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: nova_scheduler)"14:00
openstackThe meeting name has been set to 'nova_scheduler'14:00
edleafeGood UGT morning!14:00
_gryfo/14:00
mriedemo/14:00
edleafeWho's here today?14:00
*** cdent has joined #openstack-meeting-alt14:00
* bauzas waves for 25 mins14:00
alex_xuo/14:00
cdento/14:01
* edleafe thinks bauzas's arm will get tired14:01
* cdent worries bauzas is going to get tired14:01
cdentaw14:01
bauzasheh14:01
cdentjinx14:01
johnthetubaguyo/14:01
edleafenice to see everyone concerned about bauzas comfort14:01
*** julim has joined #openstack-meeting-alt14:01
digao/14:01
bauzaswell, I'm not a Patriots quarterback, but my arm is still strong14:02
edleafeok, let's get started14:02
edleafe#topic Specs & Reviews14:02
*** openstack changes topic to "Specs & Reviews (Meeting topic: nova_scheduler)"14:02
jaypipeso/14:02
edleafeNobody added anything to the agenda14:02
*** ihrachys has joined #openstack-meeting-alt14:02
*** adrian_otto has joined #openstack-meeting-alt14:03
edleafeAnyone want to bring something up for discussion?14:03
cdenteverybody is tired and confused and disoriented?14:03
edleafeOtherwise, we could get more confused by discussing https://review.openstack.org/#/c/404472/14:03
bauzasI think I need rest after last week14:04
johnthetubaguyI think I am in a better place with the current revision14:04
digahttps://review.openstack.org/#/c/423872/3/specs/pike/approved/placement-notifications.rst can you go through this spec,  I know its not an priority for ocata but need some inputs from you14:04
johnthetubaguyI just have a niggle over setting the inventory where its not needed14:04
edleafejohnthetubaguy: I think there's a lot of "just to be on the safe side" calls that really aren't needed14:04
edleafeAnd that's throughout the placement work, not just this patch14:05
*** rossella_s has joined #openstack-meeting-alt14:05
edleafeI can see a lot of cleaning up in Pike14:05
*** matrohon has joined #openstack-meeting-alt14:05
digacdent: Thanks for your inputs :)14:05
*** jprovazn has quit IRC14:05
cdent"I can see a lot of cleaning up in Pike" aye14:06
digaI was on leave for couple of days so didn't get chance to go through14:06
digaYes14:06
edleafeBut the only way to determine that is if we have a clear understanding of the code paths for the various scenarious14:06
edleafes/scenarious/scenarios14:06
johnthetubaguyagreed, but my problem is that is inconsistent with the current allocation setting logic elsewhere in the client14:06
johnthetubaguyi.e. it sets allocations assuming the inventory is already updated14:07
edleafejaypipes: can you respond on the review?14:07
johnthetubaguy(which is nice, so we don't have two different places where we try to update the inventory)14:07
jaypipesedleafe: yes14:07
edleafethx14:07
johnthetubaguycdent: I am curious how we power forward with the performance enhancements, if we do them early, its possible some might be sensible backports?14:08
cdentjohnthetubaguy: I think if we want to do that, we'll have to push hard on creating sensible tests so we know what we're not blowing things up14:09
cdentso much of the resource tracker appears to be "we'll do this just to be sure, but we're not sure why and the people who were may be gone now"14:09
*** adrian_otto has quit IRC14:09
edleafeSo that kind of aligns with the desire to determine all the code paths14:09
cdentyes14:09
*** david-lyle has joined #openstack-meeting-alt14:09
*** zhurong has quit IRC14:09
johnthetubaguycdent: very true, tests first would make sense14:10
edleafeWe need to be sure that we have functional tests for each such scenario14:10
*** saneax-_-|AFK is now known as saneax14:10
cdentyeah, hard to write tests for scenarios without first knowing the scenarios14:10
*** adrian_otto has joined #openstack-meeting-alt14:10
edleafecdent: well, we know several. It's the less obvious cases that we need to document14:11
edleafeI'm thinking of the bug last week with inventory not being removed when a compute node is destroyed14:11
jaypipesya14:12
bauzasagreed14:12
johnthetubaguycdent: you are right though, regression risk may be too high14:12
johnthetubaguytoo high for the backport, that is14:12
edleafeSo how do we document? My first instinct is "etherpad!", but those never seem to stay relevant for long14:13
edleafeA post to the ML is great, but hard to update14:13
*** nadya has joined #openstack-meeting-alt14:13
johnthetubaguyML post with a link to an etherpad?14:13
*** szaher has quit IRC14:14
johnthetubaguylooks like cdent got some good data on some smoking guns, I guess its a case of working out how we work through those, and split up the work14:14
bauzaswe should probably start drafting what we realistically want for Pike14:15
*** qwebirc6205 has joined #openstack-meeting-alt14:15
edleafebauzas: I assume that will be a big focus at the PTG14:15
bauzassure, but preparing it before could be nice, nope ? :)14:16
edleafeof course14:16
*** qwebirc6205 has quit IRC14:16
johnthetubaguywas going to say, great to start with a proposal we can discuss14:16
*** david-lyle has quit IRC14:16
bauzasviolent silence ?14:18
*** baoli has joined #openstack-meeting-alt14:18
edleafeOK, then how about this:14:18
* jroll walks in late as heck14:18
cdentbauzas: when you say "what we realistically want" do you mean what we want to fix in what already exists, or what features are we hoping to accomplish, or something else?14:18
bauzascdent: just trying to make sure we don't want too much features14:19
edleafebauzas and johnthetubaguy start with that proposal. edleafe and cdent to start documenting the needed functional test scenarios14:19
bauzasbut rather trying to see which ones are really important for Pike so we are sure we have review traction14:19
edleafeAnd then we have something to chew on at the next meeting14:19
*** salv-orl_ has quit IRC14:20
johnthetubaguyhonestly, I am only going to be good for reviewing proposals at this point, currently worrying about quota and policy things14:20
edleafejaypipes: would you have bandwidth to help bauzas with this?14:22
johnthetubaguymacsz: could you help out bauzas at all?14:22
bauzasfine, just ping me next hour14:23
*** eggmaster has joined #openstack-meeting-alt14:23
edleafeSince bauzas has to leave soon, do you have anything else, Sylvain>14:23
bauzasbecause I need to opt out since I have to go to the child school14:23
edleafe?14:23
johnthetubaguy(he may not be here, its early)14:23
bauzasedleafe: not really14:23
edleafeok, just checking14:23
digabauzas: I can help you if you want14:23
bauzasdiga: macsz: jaypipes: okay, ping me around 1500UTC14:24
bauzasand we'll see14:24
macszjohnthetubaguy: sure, just give me a sec to catch up14:24
edleafecdent: you cool with documenting the needed functional scenarios with me?14:24
digabauzas: okay14:24
cdentedleafe: yes14:24
edleafe#action edleafe and cdent to document functional scenarios and post that to the ML14:25
cdent14:25
edleafe#action bauzas, diga and macsz to begin defining the goals for Pike14:25
diga+114:25
edleafeMoving on...14:26
edleafe#topic Bugs14:26
*** openstack changes topic to "Bugs (Meeting topic: nova_scheduler)"14:26
edleafeANything to discuss here?14:26
cdentjust for reference I think the discussion this bug is interesting:14:26
cdenthttps://bugs.launchpad.net/nova/+bug/166157014:27
openstackLaunchpad bug 1661570 in OpenStack Compute (nova) "Failed to create resource provider record in placement API" [Undecided,New]14:27
johnthetubaguyI am curious about RC2 candidates if there are any that are spotted14:27
cdentIt's about some failing tests where placement was suggested as the problem, because n-cpu is warning14:27
cdentbut there's no actual placement problem, it's an ordering issue14:27
*** jprovazn has joined #openstack-meeting-alt14:27
cdent(see my comment, the last one)14:27
edleafe#link https://bugs.launchpad.net/nova/+bug/166157014:28
*** cerealki1ler has joined #openstack-meeting-alt14:28
*** cerealkiller has quit IRC14:28
*** cleong has joined #openstack-meeting-alt14:28
*** cerealki1ler is now known as cerealkiller14:28
edleafeAny other bugs spotted? Especially RC blockers?14:29
cdentjohnthetubaguy: i'm not yet aware of any rc2 stuff14:29
johnthetubaguycdent: cool14:30
*** superdan is now known as dansmith14:30
edleafeFinally...14:31
edleafe#topic Open Discussion14:31
*** openstack changes topic to "Open Discussion (Meeting topic: nova_scheduler)"14:31
edleafeAnyone have anything else on their mind?14:31
cdentthat looks like a big no14:32
alex_xuI want to ask is there any more expectation except poc for traits14:32
cdentanti-jinx!14:32
alex_xubefore PTG14:32
edleafealex_xu: I doubt it14:32
cdentWe're still reviewing the spec, yeah?14:32
alex_xucdent: yea, and PoC is up https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/resource-provider-tags14:33
* cdent nods14:33
edleafealex_xu: I'm hoping to get more focus on traits in Pike now that the guts of placement are in14:33
alex_xujust try to make sure I provide enough info for people disucss traits in PTG14:33
alex_xuedleafe: cool14:34
edleafeHeh - you should change the BP name :)14:34
alex_xuedleafe: yes, sir!14:34
alex_xuok, so I just continue poc and change bp name, and I need to update spec now14:34
edleafealex_xu: thanks for pushing ahead on traits. I've been ignoring that in favor of the resource provider stuff14:35
*** jaugustine has joined #openstack-meeting-alt14:35
*** jpena|lunch is now known as jpena14:35
edleafealex_xu: but every time we hit flavor extra-specs I scream inside14:35
alex_xunp, people already super busy on the release14:35
alex_xuheh14:35
edleafeAnything else?14:36
alex_xuthat is all from me14:37
edleafeOK, then it's back to work/play/sleep!14:37
edleafe#endmeeting14:37
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:37
openstackMeeting ended Mon Feb  6 14:37:33 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:37
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_scheduler/2017/nova_scheduler.2017-02-06-14.00.html14:37
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_scheduler/2017/nova_scheduler.2017-02-06-14.00.txt14:37
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_scheduler/2017/nova_scheduler.2017-02-06-14.00.log.html14:37
*** baoli has quit IRC14:39
*** _gryf has left #openstack-meeting-alt14:41
*** spzala has joined #openstack-meeting-alt14:42
*** cerealkiller has quit IRC14:46
*** baoli has joined #openstack-meeting-alt14:46
*** cerealkiller has joined #openstack-meeting-alt14:48
*** sdake_ is now known as sdake14:49
*** matrohon has quit IRC14:49
*** mriedem has left #openstack-meeting-alt14:50
*** numans has joined #openstack-meeting-alt14:52
*** johndperkins has joined #openstack-meeting-alt14:56
*** jchhatbar has joined #openstack-meeting-alt14:57
*** EricGonczer_ has joined #openstack-meeting-alt14:58
*** jmckind has joined #openstack-meeting-alt14:58
*** janki has quit IRC14:58
*** cerealkiller has quit IRC14:58
*** korzen has joined #openstack-meeting-alt14:59
*** mjura has joined #openstack-meeting-alt15:00
*** electrocucaracha has joined #openstack-meeting-alt15:00
*** cerealkiller has joined #openstack-meeting-alt15:00
ihrachys#startmeeting neutron_upgrades15:00
openstackMeeting started Mon Feb  6 15:00:56 2017 UTC and is due to finish in 60 minutes.  The chair is ihrachys. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: neutron_upgrades)"15:01
openstackThe meeting name has been set to 'neutron_upgrades'15:01
korzenhello15:01
electrocucarachahola15:01
sindhuhi15:01
dasanindhi15:01
ihrachys#link https://wiki.openstack.org/wiki/Meetings/Neutron-Upgrades-Subteam Agenda15:02
ihrachyshey everyone15:02
ihrachys#topic Announcements15:02
*** openstack changes topic to "Announcements (Meeting topic: neutron_upgrades)"15:02
ihrachysrc1 is cut off master, so master is pike now, and we can start landing patches as usual15:02
ihrachyswe may have some preparation work before we do merge full steam, but overall, the branch is open15:03
sshankHello15:03
ihrachysbefore we proceed, I'd like to run through ptg plans once again15:04
ihrachys#topic PTG in Atlanta15:04
*** openstack changes topic to "PTG in Atlanta (Meeting topic: neutron_upgrades)"15:04
*** jchhatbar has quit IRC15:05
*** gongysh has quit IRC15:05
*** alexchadin has quit IRC15:05
*** baoli has quit IRC15:05
ihrachyskorzen: I think you were planning to walk through the agenda pad and write up something for our cause15:05
korzenhttps://etherpad.openstack.org/p/neutron-ptg-pike-upgrades15:05
ihrachys#link https://etherpad.openstack.org/p/neutron-ptg-pike PTG etherpad15:05
ihrachyskorzen++15:05
*** baoli has joined #openstack-meeting-alt15:05
korzenmy intention was to have more detailed technical identification of tasks to be done15:06
ihrachysto be done, or to be covered during PTG?15:07
*** cdent has left #openstack-meeting-alt15:07
korzento be done15:07
korzenputting the priority on online data migration15:08
electrocucarachakorzen: about online data migration, can you expand more that definition?15:08
ihrachysyes, that's the most fuzzy topic. do we want to do prior research?15:08
korzenyes, I will do the research15:08
ihrachyskorzen: thanks.15:10
korzenelectrocucaracha, moving the data from one format to the newer15:10
korzenonline15:10
korzen;)15:10
*** bogdando has quit IRC15:10
korzenwe do not have the candidate for it now, but when it will appear, the framework should be ready to use15:11
ihrachysI believe it comprises of 1) some common hooking mechanism into get_object(s)/create/delete/update that would allow us to reduce the code needed for each case and 2) some hook in neutron-db-manage allowing to enforce transition for all pending updates.15:11
electrocucarachakorzen: during that time the table needs to be blocked?15:11
korzenelectrocucaracha, no, table should not be block15:12
korzenat least not for long period of time15:12
korzenthe operations on DB should be atomic and doable in chunks15:12
korzenso it can be done in background15:13
korzenalso when accessing the object, the data will be also migrated15:13
korzenso get_objects etc will count15:13
korzenas ihrachys said, neutron-db-manage -online-data-migration or similar command should be added15:14
*** mfedosin has quit IRC15:14
korzenand when all data is migrated, when old format is not needed, it can be removed in following release15:15
korzenin contact migration script15:15
*** mfedosin has joined #openstack-meeting-alt15:15
electrocucarachaso basically all the new calls will be addressed to the new schema15:15
korzenin n+2 yes15:16
korzenn+1 should be backward compatible15:16
*** baoli has quit IRC15:16
*** iyamahat has joined #openstack-meeting-alt15:17
*** yamahata has joined #openstack-meeting-alt15:17
ihrachyskorzen: ok I think the agenda makes sense, should we move it into the common etherpad? or at least link to it from there?15:17
*** gcb has joined #openstack-meeting-alt15:17
korzenyes, we can link to it15:17
*** chhavi has quit IRC15:18
*** manjeets has joined #openstack-meeting-alt15:18
*** baoli has joined #openstack-meeting-alt15:19
*** baoli has quit IRC15:19
ihrachysok done. drivers team will work this week on clarifying general agenda for the event.15:19
ihrachys#topic Partial Multinode Grenade15:20
*** openstack changes topic to "Partial Multinode Grenade (Meeting topic: neutron_upgrades)"15:20
ihrachyskorzen: any update on mixed server version?15:20
korzenno yet, I was fighting with the setup15:21
korzenNow, when the Ocata rc1 is released I can check the Newton/Ocata compatibility15:23
*** saneax is now known as saneax-_-|AFK15:23
korzenI'm fixing last issues with the k8s enviroment and should be ready to test15:23
korzenthe containers should gave us the proper approach for upgrading the neutron servers15:24
*** erikmwilson has quit IRC15:24
*** erikwilson has joined #openstack-meeting-alt15:24
korzenI would roll out the new neutron server with old one running on the other node15:24
korzenwith one DB15:24
korzenand the new server will call expand on DB schema15:25
korzenon that level, I will check the API CRUD operations and launching the VMs15:25
*** edtubill has joined #openstack-meeting-alt15:27
korzenI've heard that mirantis done the zero downtime in their tests, including neutron but it seams that they stopped the neutron server for a short while15:27
ihrachys'new server will call expand' - you mean, you will restart with new code, then call neutron-db-manage --upgrade --expand from that same container?15:27
korzenihrachys, yes15:27
ihrachysok makes sense15:27
korzenfunny think that Mirantis claims that only nova scheduler is a problem to achieve zero downtime15:28
korzenbut technically speaking neutron and other projects does not support the zero downtime upgrade as of now15:29
*** beslemon has joined #openstack-meeting-alt15:29
korzenI guess that they were lucky enough to have for example large offline data migration that would delay the networking API to get up15:30
korzennot to have*15:30
electrocucarachamaybe, or they're still using nova-network15:31
ihrachysthey don't15:31
korzenI will need to ask more details15:31
*** zz_dimtruck is now known as dimtruck15:32
korzenhopefully we can get an answer before PTG15:32
*** kzaitsev_mb has quit IRC15:32
ihrachyssome people even feel ok to change underlying schema while service is running. it may produce some hickups during the time, but in some cases it's well isolated. so that's maybe that.15:32
electrocucarachaby other hand, zero downtime is a hot topic in OSIC, we have guys from nova, QA, cinder and Ansible-Kolla working on that15:32
*** kzaitsev_mb has joined #openstack-meeting-alt15:34
*** jaugustine has quit IRC15:34
ihrachysok moving on15:34
ihrachys#topic Object implementation15:35
*** openstack changes topic to "Object implementation (Meeting topic: neutron_upgrades)"15:35
ihrachys#link https://review.openstack.org/#/q/status:open+project:openstack/neutron+branch:master+topic:bp/adopt-oslo-versioned-objects-for-db Open patches15:35
ihrachysI am going to walk through the list to see what we blocked before rc1 cut-off, and will land where it's due.15:35
ihrachysasingh_: please rebase https://review.openstack.org/356825 (tag patch), that should be ready I think15:36
ihrachyskorzen: as for port binding patch, we don't see to have a resolution yet? https://review.openstack.org/#/c/407868/15:36
*** Liuqing has joined #openstack-meeting-alt15:37
electrocucarachaI have a couple of patches that only refactor the existing code15:37
korzenihrachys, nope, it is till not passing the gate15:38
*** hurricanerix has left #openstack-meeting-alt15:38
*** cdelatte has joined #openstack-meeting-alt15:38
ihrachyselectrocucaracha: I will get back to those, opened in tabs15:38
manjeetsi have two patches 1. quota ovo https://review.openstack.org/#/c/338625/15:39
manjeets2. external network ovo https://review.openstack.org/#/c/353088/15:39
*** beekneemech is now known as bnemec15:40
*** Liuqing has quit IRC15:40
ihrachysmanjeets: ack15:41
sshankihrachys, How do we go about the network segment synthetic field in porting binding level? Shall we include both segment id and segment object? https://review.openstack.org/#/c/382037/.15:41
electrocucarachaI can suggest to change the status on the spreadsheet to "Ready", in that way we can distinguish those patches that are ready to be reviewed to those who are in progresss15:41
*** cerealkiller has quit IRC15:41
ihrachyssshank: wait, you are talking about 'creating' a segment object there. in which case, there won't be a level?15:42
*** cerealkiller has joined #openstack-meeting-alt15:43
ihrachysso the order would be 1. create segment 2. create port 3. create binding and levels. I don't see where we have a circular creation problem. or do I miss something?15:43
*** nijaba has quit IRC15:43
sshankihrachys, For the create segment, we need segment_id in the fields on level object.15:44
*** adrian_otto has quit IRC15:44
ihrachyssshank: when you create a new segment, you don't pass any levels, they will be created later.15:44
*** nadya has quit IRC15:44
*** rloo has joined #openstack-meeting-alt15:45
*** jaugustine has joined #openstack-meeting-alt15:45
sshankihrachys, But for creating the segment, it needs segment ID in level object for foreign key reference. I just wanted to confirm if we need to add this since I was told in the previous reviews to not have segment_id and segment synthetic field.15:46
ihrachyswait, do you talk about 'creating an object' as in 'instantiating python object', not a model?15:46
*** jaugustine has quit IRC15:47
ihrachysit may be the case that there is some work to do to make object-field handling code to work for this scenario15:47
*** jaugustine has joined #openstack-meeting-alt15:47
ihrachyslemme check once more, and I will report back on gerrit15:48
*** jaugustine has quit IRC15:48
sshankihrachys, I think we need segment id and segment synthetic field since the former is needed for foreign key referral and the latter for push notificaitons.15:48
ihrachysI think foreign key referral usage is bound to how we implemented that logic, not to the essence of the goal, that is, pulling the right related objects.15:49
ihrachysanyhow, let's take it to gerrit15:50
sshankihrachys, Okay. Thank you.15:50
*** kgiusti has joined #openstack-meeting-alt15:50
ihrachysI will skip 'Other patches' for this meeting, nothing interesting there15:50
ihrachys#topic Open discussion15:50
*** openstack changes topic to "Open discussion (Meeting topic: neutron_upgrades)"15:50
ihrachysI have one thing to point out15:50
ihrachyssome of you may have noticed already that gate is unstable lately15:51
ihrachysone of the failures we see is memory consumption going too high, making oom-killer shooting processes, usually mysql.15:51
*** nijaba has joined #openstack-meeting-alt15:51
*** nijaba has quit IRC15:51
*** nijaba has joined #openstack-meeting-alt15:51
ihrachyswe also see libvirtd dying on malloc() so that can also be related15:51
ihrachysthere is a long thread on that started by armax at http://lists.openstack.org/pipermail/openstack-dev/2017-February/111413.html15:52
ihrachysbasically, neutron and nova are the memory hoggers15:52
ihrachysand we raised memory consumption during mitaka to newton to ocata significantly15:52
ihrachysso we were thinking what could trigger that15:53
electrocucarachaihrachys: does neutron has a periodic task mechanism as nova?15:53
ihrachysand both nova folks and some of us were thinking, maybe it's OVO adoption that makes services keep some object references in memory15:53
ihrachyselectrocucaracha: what's the mechanism? you would need to elaborate.15:53
electrocucarachaihrachys: by default, nova checks every 60 secs the status of the VMs15:54
*** knangia has joined #openstack-meeting-alt15:54
electrocucarachaihrachys: there is a way to change this behavior to subscribe instead of asking compute nodes15:54
ihrachysso, though we don't have any numbers yet (people are working on generating memory usage profiles), it's worth a note here that OVO is a suspect, and we may need to get involved in whatever comes from the investigation.15:55
*** tremble has quit IRC15:55
ihrachyselectrocucaracha: how does it relate to memory consumption?15:55
ihrachysI think it could change cpu usage pattern but not memory?15:55
korzenihrachys, is it OVO lib general problem?15:56
ihrachyswe don't know yet, maybe nova and neutron do something wrong; maybe it's not even OVO.15:56
ihrachysbut nova folks said they noticed memory usage going up when they started adoption15:57
ihrachysso that's now two of us15:57
korzen:)15:57
ihrachysmaybe that's related, maybe not. a memory profile should give us data.15:57
ihrachysfor now, let's point fingers into oslo direction :))15:57
manjeetsi guess cinder also have ovo it may or may not be ovo15:57
ihrachysyeah, for now it's just unfounded suspicions15:58
ihrachysbut it's bad for PR ;)15:58
*** jungleboyj has joined #openstack-meeting-alt15:58
ihrachysok let's call it a day. thanks everyone.15:59
ihrachys#endmeeting15:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:59
openstackMeeting ended Mon Feb  6 15:59:14 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_upgrades/2017/neutron_upgrades.2017-02-06-15.00.html15:59
korzenthanks15:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_upgrades/2017/neutron_upgrades.2017-02-06-15.00.txt15:59
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_upgrades/2017/neutron_upgrades.2017-02-06-15.00.log.html15:59
sshankThank you.15:59
ndahiwadethanks15:59
sindhuthanks15:59
manjeetsthanks15:59
*** hongbin has joined #openstack-meeting-alt15:59
electrocucarachathanks15:59
gcb#startmeeting  oslo16:00
openstackMeeting started Mon Feb  6 16:00:08 2017 UTC and is due to finish in 60 minutes.  The chair is gcb. 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: oslo)"16:00
gcbcourtesy ping for amotoki, amrith, bknudson, bnemec, dansmith, dhellmann, dims16:00
openstackThe meeting name has been set to 'oslo'16:00
gcbcourtesy ping for dougwig, e0ne, electrocucaracha, flaper87, garyk, gcb, GheRivero16:00
gcbcourtesy ping for haypo, jd__, jecarey, johnsom, jungleboyj, kgiusti, kragniz16:00
johnsomo/16:00
johndperkinso/16:00
kgiustio/16:00
jungleboyjo/16:00
gcbcourtesy ping for lifeless, lxsli, Nakato, ozamiatin, rbradfor, redrobot, rloo16:00
ansmitho/16:00
electrocucarachao/16:00
gcbcourtesy ping for rpodolyaka, sergmelikyan, sileht, spamaps, sreshetnyak, sreshetnyak, stevemar16:00
rlooo/16:01
gcbcourtesy ping for therve, thinrichs, toabctl, viktors, zhiyan, zzzeek16:01
gcbwelcome guys, that's really a long name lists :-)16:01
rpodolyakao/16:01
bknudsonhi16:01
toabctlhi16:01
gcb#topic Red flags for/from liaisons16:02
*** openstack changes topic to "Red flags for/from liaisons (Meeting topic: oslo)"16:02
bknudsonnothing from keystone that I know of.16:02
*** xin9972 has joined #openstack-meeting-alt16:02
gcbbknudson,  thanks16:02
johnsomSmooth sailing with Octavia16:02
rloono complaints from ironic16:02
jungleboyjNo issues from Cinder ...16:02
gcbjohnsom, rloo, jungleboyj : ack16:03
gcb#topic Releases for Pike16:03
*** openstack changes topic to "Releases for Pike (Meeting topic: oslo)"16:03
*** kzaitsev_mb has quit IRC16:04
*** korzen has quit IRC16:04
gcbwe cut stable/ocata branch recently, so I think we need hold new release for Pike16:04
gcbwill check with dhellmann  when we can release new versions of oslo libraries16:05
kgiustigcb: actually... would it be possible to release another ocata stable oslo.messaging?16:05
kgiustigcb: https://bugs.launchpad.net/oslo.messaging/+bug/165748516:05
openstackLaunchpad bug 1657485 in oslo.messaging "[AMQP 1.0] IPv6 host address raises getaddressinfo() error" [Undecided,Fix released] - Assigned to Andy Smith (ansmith-t)16:05
kgiustigcb: embarrassing bug :(16:06
gcbkgiusti, let's make a minor release 5.17.116:07
gcbnot sure it's the time to update g-r16:08
kgiustigcb: agreed.16:08
gcbso please help submit release commit, and add me as reviewer16:08
kgiustigcb: kk16:09
gcbokay, let's move on16:09
gcb#topic  daily work16:09
*** openstack changes topic to "daily work (Meeting topic: oslo)"16:09
gcb#link https://etherpad.openstack.org/p/oslo-pike-tracking16:09
gcbthis is new topic  to track our daily work16:10
*** sridharg has quit IRC16:10
bknudsonbookmarked16:10
gcbplease add your irc name in section Libraries and focus if you can help for specific lib16:10
jungleboyjWow, I didn't realize we had that many libraries.16:12
*** armax has joined #openstack-meeting-alt16:12
gcboslo core reviewers or liaisons please add item on sections "High prioritiy items" we can focus on them16:12
gcbjungleboyj, yeah we have many16:12
gcbbut some are outdated, like hacking which doesn't belong to Oslo team now16:13
*** fnaval has joined #openstack-meeting-alt16:14
gcbWe plan to review items in the etherpad on weekly meeting ,so please add any necessary  items , then we have enough time before discussing16:15
gcb#topic PTG16:15
*** openstack changes topic to "PTG (Meeting topic: oslo)"16:15
gcbI just sent a email to collect ideas and suggestions for PTG oslo16:16
gcb#link https://etherpad.openstack.org/p/oslo-ptg-pike16:16
gcbplease add items :-)16:16
*** jaugustine has joined #openstack-meeting-alt16:17
gcb#topic Open discussion16:18
*** openstack changes topic to "Open discussion (Meeting topic: oslo)"16:18
gcbIs there anything want to be raised ?16:18
*** florianf has quit IRC16:18
electrocucarachagcb: I won't be able to attend the PTG but I'd be nice to spend some time talking about this http://lists.openstack.org/pipermail/openstack-dev/2017-February/111526.html16:19
electrocucarachagcb: it's about the assumption that OVO is consuming a lot of memory16:20
gcboom-kill, a common issue for OpenStack service16:20
bknudsonas far as I know, nobody's done any analysis of keystone memory usage16:21
gcbdo you mean you would like to share some insight about that?16:21
*** florianf has joined #openstack-meeting-alt16:21
gcbAs I remember libvirt has memory leak when create new domain16:22
bknudsonif we ever hit a problem in memory usage on our production keystone deployment we'd just ask for a bigger machine ... never got around to doing the memory profiling.16:22
*** jmckind has quit IRC16:22
*** jmckind has joined #openstack-meeting-alt16:23
gcbbknudson: so it's time to figure out the root cause, I just go through emails ,will read more, hope can give some output16:23
*** vinaypotluri has left #openstack-meeting-alt16:24
*** mdong has joined #openstack-meeting-alt16:24
*** jcoufal_ has joined #openstack-meeting-alt16:25
*** armax has quit IRC16:25
electrocucarachamaybe this patch can help to get a clue of the problem https://review.openstack.org/#/c/428220/16:25
*** jcoufal has quit IRC16:27
*** nadya has joined #openstack-meeting-alt16:28
*** lpetrut has quit IRC16:29
gcbelectrocucaracha: yeah , thanks for the link. but just for process level, not sure that's useful enough16:29
*** jprovazn is now known as jprovazn_bbl16:30
gcbanyway, will look at the issue from oslo side16:30
*** adrian_otto has joined #openstack-meeting-alt16:30
electrocucarachathanks gcb16:31
*** beslemon has quit IRC16:31
*** tonytan4ever has joined #openstack-meeting-alt16:31
gcbokay, any otherthing ?16:31
gcbif not, we can call it a meeting now16:32
*** rossella_s has quit IRC16:32
gcbthanks everyone16:32
jungleboyjThank you!16:32
electrocucarachabye16:32
*** electrocucaracha has left #openstack-meeting-alt16:33
gcb#endmeeting16:33
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:33
openstackMeeting ended Mon Feb  6 16:33:16 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:33
openstackMinutes:        http://eavesdrop.openstack.org/meetings/oslo/2017/oslo.2017-02-06-16.00.html16:33
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/oslo/2017/oslo.2017-02-06-16.00.txt16:33
openstackLog:            http://eavesdrop.openstack.org/meetings/oslo/2017/oslo.2017-02-06-16.00.log.html16:33
*** kgiusti has left #openstack-meeting-alt16:33
*** gcb has quit IRC16:33
*** baoli has joined #openstack-meeting-alt16:35
*** panda is now known as panda|bbl16:35
*** beslemon has joined #openstack-meeting-alt16:35
*** mdong has quit IRC16:36
*** salv-orlando has joined #openstack-meeting-alt16:36
*** iyamahat has quit IRC16:38
*** iyamahat has joined #openstack-meeting-alt16:38
*** diga has quit IRC16:38
*** rloo has left #openstack-meeting-alt16:38
*** chhavi has joined #openstack-meeting-alt16:40
*** mdong has joined #openstack-meeting-alt16:42
*** kfarr has joined #openstack-meeting-alt16:43
*** andreas_s has quit IRC16:43
*** stingaci has joined #openstack-meeting-alt16:51
*** dizquierdo has quit IRC16:54
*** stingaci has quit IRC16:56
*** baoli has quit IRC16:56
*** mjura has quit IRC16:59
*** rmart04 has quit IRC17:01
*** armax has joined #openstack-meeting-alt17:04
*** Swami has joined #openstack-meeting-alt17:08
*** dims has quit IRC17:11
*** jose-phillips has joined #openstack-meeting-alt17:16
*** dims has joined #openstack-meeting-alt17:18
*** tesseract has quit IRC17:18
*** jaugustine has quit IRC17:19
*** mariannelm has quit IRC17:20
*** harlowja has joined #openstack-meeting-alt17:20
*** florianf has quit IRC17:26
*** florianf has joined #openstack-meeting-alt17:26
*** cerealkiller has quit IRC17:29
*** mdong has quit IRC17:30
*** cerealkiller has joined #openstack-meeting-alt17:31
*** mdong has joined #openstack-meeting-alt17:31
*** zhonghua has quit IRC17:37
*** zhonghua has joined #openstack-meeting-alt17:38
*** spzala has quit IRC17:39
*** baoli has joined #openstack-meeting-alt17:43
*** raliev has quit IRC17:44
*** stingaci has joined #openstack-meeting-alt17:45
*** reedip_ has left #openstack-meeting-alt17:47
*** rmart04 has joined #openstack-meeting-alt17:47
*** chhavi has quit IRC17:48
*** harlowja has quit IRC17:49
*** derekh has quit IRC17:49
*** AlanClark has joined #openstack-meeting-alt17:55
*** iyamahat has quit IRC17:55
*** ralonsoh has quit IRC17:56
*** yamahata has quit IRC17:56
*** lpetrut has joined #openstack-meeting-alt17:57
*** bfernando has quit IRC17:58
*** tonytan4ever has quit IRC18:04
*** tonytan4ever has joined #openstack-meeting-alt18:04
*** nadya has quit IRC18:05
*** spzala has joined #openstack-meeting-alt18:08
*** sambetts is now known as sambetts|afk18:11
*** anilvenkata has joined #openstack-meeting-alt18:13
*** ijw has joined #openstack-meeting-alt18:23
*** mariannelm has joined #openstack-meeting-alt18:23
*** iyamahat has joined #openstack-meeting-alt18:24
*** dfflanders has joined #openstack-meeting-alt18:26
*** cerealkiller has quit IRC18:29
*** diablo_rojo has joined #openstack-meeting-alt18:30
*** AlanClark has quit IRC18:31
*** AlanClark has joined #openstack-meeting-alt18:31
*** AlanClark has quit IRC18:32
*** ijw has quit IRC18:32
*** AlanClark has joined #openstack-meeting-alt18:32
*** iyamahat has quit IRC18:32
*** iyamahat has joined #openstack-meeting-alt18:32
*** anilvenkata has quit IRC18:33
*** jaugustine has joined #openstack-meeting-alt18:36
*** beslemon has quit IRC18:36
*** jungleboyj has quit IRC18:37
*** nkrinner is now known as nkrinner_afk18:40
*** harlowja has joined #openstack-meeting-alt18:44
*** yamahata has joined #openstack-meeting-alt18:45
*** xyang1 has joined #openstack-meeting-alt18:48
*** gouthamr has quit IRC18:52
*** AlanClark has quit IRC18:52
*** AlanClark has joined #openstack-meeting-alt18:54
*** sambetts|afk has quit IRC18:55
*** sambetts_ has joined #openstack-meeting-alt18:56
*** dizquierdo has joined #openstack-meeting-alt18:58
*** gouthamr has joined #openstack-meeting-alt18:58
*** nadya has joined #openstack-meeting-alt18:59
*** snackewm has joined #openstack-meeting-alt19:00
*** degorenko has quit IRC19:01
*** ijw has joined #openstack-meeting-alt19:05
*** sdague has quit IRC19:07
*** degorenko has joined #openstack-meeting-alt19:07
*** raj_singh_ has joined #openstack-meeting-alt19:10
*** s3wong has joined #openstack-meeting-alt19:15
*** stingaci has quit IRC19:16
*** mfedosin has quit IRC19:17
*** dizquierdo has quit IRC19:18
*** jaugustine has quit IRC19:19
*** raj_singh_ has quit IRC19:19
*** skarthik has joined #openstack-meeting-alt19:21
*** kzaitsev_mb has joined #openstack-meeting-alt19:22
*** kjw3 has joined #openstack-meeting-alt19:23
*** numans has quit IRC19:24
*** karts has quit IRC19:25
*** salv-orlando has quit IRC19:25
*** numans has joined #openstack-meeting-alt19:25
*** cerealkiller has joined #openstack-meeting-alt19:27
*** nadya has quit IRC19:29
*** korzen has joined #openstack-meeting-alt19:30
*** beslemon has joined #openstack-meeting-alt19:30
*** jaugustine has joined #openstack-meeting-alt19:31
*** edtubill has quit IRC19:31
*** kberger has joined #openstack-meeting-alt19:37
*** kberger has quit IRC19:37
*** kberger has joined #openstack-meeting-alt19:38
*** dsariel has quit IRC19:39
*** mfedosin has joined #openstack-meeting-alt19:43
*** pvaneck has joined #openstack-meeting-alt19:49
*** tonanhngo has joined #openstack-meeting-alt19:51
*** strigazi is now known as strigazi_AFK19:58
dave-mccowan#startmeeting barbican20:00
openstackMeeting started Mon Feb  6 20:00:12 2017 UTC and is due to finish in 60 minutes.  The chair is dave-mccowan. Information about MeetBot at http://wiki.debian.org/MeetBot.20:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
*** openstack changes topic to " (Meeting topic: barbican)"20:00
openstackThe meeting name has been set to 'barbican'20:00
dave-mccowan#topic roll call20:00
*** openstack changes topic to "roll call (Meeting topic: barbican)"20:00
redroboto/20:02
* dave-mccowan waves to redrobot 20:02
*** alee has joined #openstack-meeting-alt20:02
*** jaosorior has joined #openstack-meeting-alt20:02
jaosorioro/20:02
aleeo/20:02
dave-mccowan\o/20:03
redrobotwoo!20:03
redrobotit's a party!20:03
kfarro/20:03
dave-mccowanas usual, our agenda is here:20:03
dave-mccowan#link https://wiki.openstack.org/wiki/Meetings/Barbican20:03
dave-mccowan#topic Summit20:04
dave-mccowantoday is the last day to submit a proposal for the Boston summit.20:04
*** openstack changes topic to "Summit (Meeting topic: barbican)"20:04
*** dtardivel has quit IRC20:04
dave-mccowanhas anyone submitted a barbican talk?  (or want to throw one together quickly today?)20:04
redrobotI'm thinking a Vault vs Barbican talk20:05
redrobotwill try to throw something together20:05
redrobotI'm thinking a security model comparison20:05
redrobotmaybe a feature comparison as well20:05
redrobotobviously very biased towards Barbican :D20:06
aleedave-mccowan, thanks for the reminder -- I had completely forgotten ..20:06
dave-mccowanredrobot i like it!  what use case for each one would be good too.20:06
redrobotyup20:06
redrobotmaybe even throw in possible integration20:07
redrobotlike Vault as a backend for Barbican20:07
redrobotor Keystone as an auth backend for Vault20:07
dave-mccowando we want to submit the hands-on barbican session again?20:08
*** MarkBaker has joined #openstack-meeting-alt20:09
dave-mccowanlet me know if anyone wants help putting something together.20:09
dave-mccowanmoving on...20:09
redrobotI thought Fernando was going to do that?20:09
redrobotI'd love some help on the Vault v Barbican talk if anyone is interested20:10
dave-mccowanredrobot count me in20:10
dave-mccowan#topic PTG20:11
redrobotdave-mccowan \o/20:11
*** openstack changes topic to "PTG (Meeting topic: barbican)"20:11
redrobotI'm officially not going :(20:11
*** mtanino has joined #openstack-meeting-alt20:11
dave-mccowantwo weeks until the PTG.  we've got a pretty good agenda, but we're light on attendees.20:11
redrobotbut I'd love to be a floating head on the projector20:11
dave-mccowanhttps://etherpad.openstack.org/p/ptg-barbican-pike20:11
redrobotmaybe we can schedule a couple of 1hr hangouts each day?20:11
dave-mccowanI'll definitely set up something for anyone who want to attend remotely.20:11
aleedave-mccowan, I think we're going to feel like an episode of futurama ..20:12
redrobotalee lol20:12
dave-mccowanthe PTG is intended to kick off the Pike cyle20:12
mrhillsmanyou all do not have an open item on the agenda20:13
mrhillsmanso will drop in something here if ok20:13
dave-mccowanalee, kfarr i know you are coming, but also have other project sessions you want to go to.  we should try to firm up an agenda with days and times to help with coordination.20:13
mrhillsmanhttps://etherpad.openstack.org/p/ops-adopt-a-project-pike20:13
mrhillsmanit is 'relevant' i think to ptg20:13
mrhillsmanwithin osic the ops team would like to assist with offering feedback to barbican, details in the etherpad20:14
dave-mccowan#topic Ops Proposition20:14
*** openstack changes topic to "Ops Proposition (Meeting topic: barbican)"20:14
dave-mccowanhi mrhillsman20:14
mrhillsmanif possible at ptg it can be brought up and how it could be beneficial that would be great20:14
mrhillsmanor not beneficial :)20:14
*** fzdarsky has quit IRC20:15
mrhillsmanand how we can collaborate to be successful over pike with some expected outcomes20:15
mrhillsmanwe just put what we thought made sense there and looking for feedback20:15
mrhillsmanhey dave-mccowan20:15
dave-mccowanmrhillsman that sounds great.  we, as a community, have been wanting to boost our adoption.  we're open to any contributions in that regards.20:16
*** david-lyle has joined #openstack-meeting-alt20:16
dave-mccowanis the PTG the best place to start the conversation?20:16
dave-mccowanthat's fine with me.20:16
mrhillsmanwe will not be at the ptg i believe20:16
redrobot"we plan to add to OSIC for Pike" YES!!! :D20:17
redrobot^^ this makes me happy20:17
*** dsariel has joined #openstack-meeting-alt20:17
*** sdague has joined #openstack-meeting-alt20:17
mrhillsmanwe just thought maybe you all could discuss and we could work to define some goals together through this effort20:17
mrhillsmanamongst the other items you all come up with20:17
redrobotmrhillsman are you at OSIC in San Antonion?20:17
redrobot*Antonio20:17
mrhillsmanif you do however setup remote access, someone will sit in for sure20:18
mrhillsmani am not redrobot, in Houston20:18
mrhillsmanbut our team is there20:18
redrobotredrobot ah, ok20:18
mrhillsmani can schedule a time after the ptg to be in sa though and we can get together20:18
mrhillsmanbarbican and osic ops folks20:18
redrobotmrhillsman sounds good20:18
mrhillsmancool, i'll email you20:18
mrhillsmanthat is all i wanted to offer20:19
*** dizquierdo has joined #openstack-meeting-alt20:19
redrobotmrhillsman I'm is Douglas Mendizábal at Rackspace btw20:19
mrhillsmanthanks for your time20:19
mrhillsmanyep, i got you :)20:19
redrobot😎20:19
mrhillsmanwe've talked/met20:19
dave-mccowanmrhillsman thanks!  i'll add this as a standing agenda item for our weekly calls, so we can track this going into Pike.20:20
dave-mccowan#topic Ocata Status20:20
*** openstack changes topic to "Ocata Status (Meeting topic: barbican)"20:20
*** adrian_otto has quit IRC20:20
mrhillsmanthx dave-mccowan20:20
dave-mccowanLast Friday, we released RC1 and pulled stable/ocata for Barbican20:21
*** cerealkiller has quit IRC20:21
dave-mccowanalso kfarr pull stable/ocata for Castellan (the first stable branch for Castellan)20:21
*** number80 has quit IRC20:21
kfarrYup!20:21
dave-mccowanbarbican master is for Pike developmet20:21
redrobotwoot!20:22
redrobotcan I resubmit the ID change?20:22
dave-mccowanif we don't find any showstoppers this week, RC1 will become our Ocata release.20:22
dave-mccowanredrobot yes, let's do that soon.  we need the co-requisite changes to client.20:23
redrobotdave-mccowan ack, I can work on the client bits and then submit both at the same time20:23
dave-mccowangreat!  thanks!20:23
dave-mccowanany other questions on Ocata?20:24
*** dfflanders has quit IRC20:24
dave-mccowan#topic tempest testing20:24
*** openstack changes topic to "tempest testing (Meeting topic: barbican)"20:24
dave-mccowanthere is one outstanding review now in barbican-tempest-plugin20:25
*** salv-orlando has joined #openstack-meeting-alt20:25
kfarrDane and Peter are planning on working on scenario tests this week20:26
kfarrto test the integration with Glance / Nova / etc20:26
dave-mccowan\o/  kfarr let them know we appreciate it. :-)20:26
kfarrYeah, thanks for the code reviews!20:27
*** dimtruck is now known as zz_dimtruck20:27
dave-mccowan#topic payload_content_type bug20:27
*** openstack changes topic to "payload_content_type bug (Meeting topic: barbican)"20:27
dave-mccowanthis morning, someone in the channel asked about https://bugs.launchpad.net/barbican/+bug/147943920:27
openstackLaunchpad bug 1479439 in Barbican "cannot retrieve certificate payload with snakeoil plugin" [Undecided,Confirmed]20:27
*** florianf has quit IRC20:28
dave-mccowanwhich is a really old bug, that is apparently still there20:28
dave-mccowanhe's using the python client, and it is sending the content type as None which failing20:29
*** gyee has joined #openstack-meeting-alt20:29
dave-mccowancomments in the code from 2015 say we've deprecated support for a user specifying payload_content_type, but it seems we need to for the code work.20:30
*** rfolco has quit IRC20:30
dave-mccowanif you have any thoughts on this, please attach them to the bug.20:31
*** jaugustine has quit IRC20:31
dave-mccowan#topic any other business20:31
*** openstack changes topic to "any other business (Meeting topic: barbican)"20:31
*** jaugustine has joined #openstack-meeting-alt20:32
dave-mccowanok... we're done a little early.20:32
dave-mccowaneveryone can use the time to submit summit talk proposals. :-)20:33
redroboto/20:33
redrobotoh I have a spec I'm working on20:33
redrobotfor Pike20:33
redrobotbasically I want to steal some ideas from Vault and add  Shamir's Secret Sharing support to SimpleCrypto20:34
dave-mccowanredrobot cool.  i think the community is hoping for something like this...20:35
*** MeganR has joined #openstack-meeting-alt20:35
redrobotso instead of storing an encryption key in the conf file, we would be able to split the key into K pieces and only require N of them to start up Barbican20:35
*** rmart04 has quit IRC20:35
redrobotanyway, I'll try to get an initial spec this week20:35
redrobotthinking maybe API calls to provide the key pieces...20:36
*** jaugustine has quit IRC20:36
*** salv-orlando has quit IRC20:36
*** salv-orlando has joined #openstack-meeting-alt20:37
dave-mccowancool.  6 months to go until Pike release. :-)20:37
*** diazjf has joined #openstack-meeting-alt20:38
dave-mccowanlast call for any other business20:38
diazjfo/ sorry was in a meeting20:38
redrobotdiazjf did you submit the workshop?20:38
diazjfredrobot, nope. When is the deadline?20:39
redrobotdiazjf today20:39
dave-mccowanmidnight tonight (i think PST)20:39
diazjfredrobot, I'll put it up within the next hour20:39
redrobotdiazjf awesome!20:40
diazjfkfarr, dave-mccowan, alee, I will add all of you as well :)20:40
dave-mccowandiazjf thanks!20:40
*** rmart04 has joined #openstack-meeting-alt20:41
dave-mccowandiazjf we're just wrapping up.  did you want to bring anything up?20:41
redrobotdave-mccowan so are you officially PTL for Pike now?20:41
dave-mccowanyes.  i couldn't pass off the hot potato. :-)20:42
redrobotlol, congrats dave-mccowan !20:42
jaosoriorcongrats dude! and thanks20:42
redrobotyeah, thanks for hanging on to the patata :D20:42
*** zz_dimtruck is now known as dimtruck20:43
*** matrohon has joined #openstack-meeting-alt20:44
dave-mccowanno worries.  happy to help.  everyone start thinking about next cycle, if you're interested.20:44
diazjfcongrats!!20:44
dave-mccowancatch everyone later...20:45
dave-mccowan#endmeeting20:45
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:45
openstackMeeting ended Mon Feb  6 20:45:19 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:45
openstackMinutes:        http://eavesdrop.openstack.org/meetings/barbican/2017/barbican.2017-02-06-20.00.html20:45
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/barbican/2017/barbican.2017-02-06-20.00.txt20:45
openstackLog:            http://eavesdrop.openstack.org/meetings/barbican/2017/barbican.2017-02-06-20.00.log.html20:45
*** rfolco has joined #openstack-meeting-alt20:46
*** rfolco has quit IRC20:46
*** cdelatte has quit IRC20:46
*** arunkant has joined #openstack-meeting-alt20:47
*** Rockyg has joined #openstack-meeting-alt20:47
*** rmart04 has quit IRC20:50
*** korzen has quit IRC20:52
*** jaosorior has left #openstack-meeting-alt20:52
*** hichihara has joined #openstack-meeting-alt20:55
*** leong has joined #openstack-meeting-alt20:55
*** numans has quit IRC20:56
*** gouthamr has quit IRC20:56
*** adrian_otto has joined #openstack-meeting-alt20:56
*** skarthik has quit IRC20:57
leong#startmeeting product_working_group21:00
openstackMeeting started Mon Feb  6 21:00:28 2017 UTC and is due to finish in 60 minutes.  The chair is leong. Information about MeetBot at http://wiki.debian.org/MeetBot.21:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:00
*** openstack changes topic to " (Meeting topic: product_working_group)"21:00
openstackThe meeting name has been set to 'product_working_group'21:00
Rockygo/21:00
leonganyone here for Product WG meeting?21:00
MeganRo/21:00
leong#topic rollcall21:00
leongo/21:00
*** openstack changes topic to "rollcall (Meeting topic: product_working_group)"21:00
kencjohnstono/21:01
*** KrishR has joined #openstack-meeting-alt21:01
leonghi rockyg, meganr, kencjohnston and krishr...21:01
KrishRhi Leong21:01
leongtoday agenda can be found here:21:01
leong#link Agenda: https://wiki.openstack.org/wiki/Meetings/product-team21:01
*** alee has left #openstack-meeting-alt21:01
*** jaugustine has joined #openstack-meeting-alt21:01
*** david-lyle has quit IRC21:02
leonghopefully shamail can join us as well....21:02
leonganything else that you would like to add to today Agenda?21:02
*** Arkady_Kanevsky has joined #openstack-meeting-alt21:02
Arkady_Kanevskyhello21:02
leonghi arkady21:02
*** numans has joined #openstack-meeting-alt21:03
Arkady_Kanevskyhi leong21:03
leong#topic Action items from previous meeting21:03
*** openstack changes topic to "Action items from previous meeting (Meeting topic: product_working_group)"21:03
mrhillsmano/21:03
* Rockyg waves to everbody21:03
leong#link Last week action items: http://eavesdrop.openstack.org/meetings/product_working_group/2017/product_working_group.2017-01-30-21.00.html21:03
* leong wave... 21:03
leonglet's have a quick update from last week meeting...21:04
leongthe PWG midcycle location21:04
leongRockyg, do you have anything from Huawei?21:04
*** heidijoy has joined #openstack-meeting-alt21:04
*** jungleboyj has joined #openstack-meeting-alt21:05
leongalso a question to everyone, have anyone receive/confirm travel to Milan Ops midcycle?21:05
Arkady_Kanevskyno on Milan21:06
leongi think we need to estimate the attendees and size of room21:06
Arkady_Kanevskybut I planning to21:06
leongmy travel to Milan is approved21:06
*** yamamoto has joined #openstack-meeting-alt21:06
MeganRI will not be going21:07
heidijoyI will be there.21:07
*** Shrews has joined #openstack-meeting-alt21:07
Arkady_KanevskyI plan to attend21:07
leongRockyg, do you have anything from Huawei?21:08
RockygI've got yet another name to track down.  Office is about 1/2 hour from ops meetup site by car.  very round about.  I have to find out how big the office is and who's in charge.21:08
RockygBut, a little progress.21:09
*** skarthik has joined #openstack-meeting-alt21:09
Arkady_Kanevskyany chance we can have it all in one place with ops summit?21:09
*** AndyU has joined #openstack-meeting-alt21:09
leongi also prefer the same location as with Ops midcycle.... i remember the cost is about euro$300 per day21:10
leongfor a room21:10
RockygHmm.  Lemme run that by Anni....21:10
leongif anyone here can get a "sponsor", then we can be at the same place21:10
Arkady_Kanevskymeeting room or individual hotel room?21:10
*** tenobreg has joined #openstack-meeting-alt21:11
leongmeeting room21:11
Rockygso, is it two or three days?21:11
Arkady_KanevskyI rcealled Intel was also volunteering...21:11
leongmrhilsman: maybe if you can help us to validate if we can book a meeting room at the same location as Ops midcycle21:11
leongthe plan was two days PWG at Milan21:12
*** julim has quit IRC21:12
heidijoy^^Correct- plan is Mon/Tue preceding the Wed/Thur Ops Midcycle21:12
Rockygthanks.21:12
leongArkady_Kanevsky: i think u mix up with Aug one.. but Intel is not able to sponsor the Aug one either21:13
Arkady_Kanevskygot it21:13
leongLet's discuss the PWG Ops meetup again next week, we also need to make sure we have enough quorom to host the F2F meeting for PWG21:13
*** yamamoto has quit IRC21:14
RockygI texted Anni.  We'll see...21:14
*** shamail has joined #openstack-meeting-alt21:14
leonghi shamail21:14
Rockyghey, shamail21:14
leongwe were just talking about the mid-cycle location21:14
shamailHi Leong and everyone!  Sorry for being late, just landed.21:14
leongnot a problem..21:15
leongcan you confirm if IBM can host us? someone also suggest the same location as Ops21:15
shamailIBM can host us during midcycle but I am confirming the final details21:15
shamailIt's more than likely that we can find space but I can confirm next week.21:15
leonggreat.. thanks! let's follow up this again in next week meeting..21:15
shamailDid we find out if it would be possible to get space in the same venue as the ops meetup?21:15
leong#agreed: to follow-up the PWG mid-cycle planning next week21:16
shamailmrhillsman: ping21:16
*** gouthamr has joined #openstack-meeting-alt21:16
*** markvoelker has joined #openstack-meeting-alt21:17
leonglet's follow that up offline with mrhillsman.. :-)21:17
*** yamamoto has joined #openstack-meeting-alt21:17
leonglet's move on to next topic :)21:17
leong#topic "open" gerrit review21:17
*** openstack changes topic to ""open" gerrit review (Meeting topic: product_working_group)"21:17
leong#link gerrit: https://review.openstack.org/#/q/project:openstack/openstack-user-stories+status:open21:17
leongany one gerrit item that need our attention?21:18
*** markvoelker_ has quit IRC21:18
Arkady_Kanevskywe have some fairly old ones sitting without progress21:19
AndyUWe'll be discussing Improve Error Codes Story in LCOO meeting this week21:19
*** jprovazn_bbl has quit IRC21:19
leong+1 andyU21:19
mrhillsmansorry, had to step away21:19
*** markvoelker_ has joined #openstack-meeting-alt21:19
Arkady_Kanevskylike - https://review.openstack.org/25322821:19
RockygAlso tonight in Regional PWG21:19
leong+1 rockg :)21:20
Arkady_Kanevskywhat shoudl we do with the ones that are not being responded on?21:20
shamailNp mrhillsman, I was trying to find out if it would be possible to use the same venue as the ops meetup in Milan.  I'll follow up via email.21:20
shamailArkady_Kanevsky: I think we leave them alone for now unless the authors have made the necessary changes.  We can discuss further at midcycle to see if we need to abandon any.21:21
leongArkady_kanevsky, i will go through the list today and tomorrow and will reply on gerrit21:21
Rockygif we want movement on specific ones, someone should comment to get discussion happening again.21:21
leong+1 shamail21:21
mrhillsmanok shamail will keep an eye out21:21
kencjohnstonon gerrit, I had an item with a merge conflcit that I just resolved - https://review.openstack.org/#/c/352182/21:21
*** cleong has quit IRC21:21
shamailNice kencjohnston21:22
Arkady_KanevskyPropose that if a patch was review and have feedback and author is not updating it acroiss releases we abandon it.21:22
*** markvoelker has quit IRC21:22
leongthanks kencjohnston.. i will have a look after this meeting21:22
kencjohnstonAlso, we have a couple of "Abandon potentials" from Piet21:22
Arkady_KanevskyThanks Shamail and Leong.21:22
*** MarkBaker has quit IRC21:22
leongalso, as Carol retired, we need to get more core reviewer21:22
Arkady_KanevskyAgree <kencjohnston>21:22
shamailkencjohnston: +121:22
RockygI think we need to ping authors before we abandon.....21:22
kencjohnstonWithout new owners steppign forward I'm willing to get what is there merged, but not going to be able to own it for updates/scope additions.21:23
Arkady_KanevskyI am trying to dillegently review any pacthes that are updated.21:23
RockygAnd should come up with a policy on when to mark abandoned21:23
shamailkencjohnston: +121:23
Arkady_Kanevskynut will not comment on the ones that are already havce comments that are not being addressed21:23
shamailI think we can revisit what needs to be abandoned when we are all together at midcycle21:23
Rockyg++21:23
Arkady_Kanevsky+121:23
leong+1 shamail21:23
shamailRockyg: +1 on policy21:24
kencjohnstonshamail +121:24
Arkady_KanevskyI think that only chair can abandon pull request or the author21:24
RockygPolicy should go on midcycle agenda...21:24
*** tonanhngo has quit IRC21:24
shamailLeong can you make an action to review Ken's updated patch and agreement on reviewing old changes at midcycle21:24
leongi think "core" can abandon21:24
*** tonanhngo_ has joined #openstack-meeting-alt21:24
shamailCore is fair.21:25
Rockygleong, ++21:25
Arkady_KanevskyI am fine as long as we have formally defined process.21:25
* kencjohnston pulls out his "abandon" baseball bat.21:25
leong#agreed All review Kenny updated patch https://review.openstack.org/#/c/352182/21:25
shamaillol kencjohnston21:25
kencjohnstonThat patch was ready for merge, just hit a conflict that I took to long ot resolve.21:25
shamailYeah, saw that21:26
shamailShould be a quick workflow21:26
leong#agreed All will review the list of changes at gerrit and define abandon policy at Midcycle21:26
*** vAlexa has joined #openstack-meeting-alt21:26
*** vAlexa is now known as cerealkiller21:26
leongany thing else on this agenda? if not, shall we move on to next topic?21:27
*** david-lyle has joined #openstack-meeting-alt21:27
*** diazjf has left #openstack-meeting-alt21:27
leong#topic Updates on the proposal for PWG participation in Forum21:27
*** openstack changes topic to "Updates on the proposal for PWG participation in Forum (Meeting topic: product_working_group)"21:27
leong#link Proposal: https://docs.google.com/presentation/d/1jTlO4UdNjc5cOKboeCNhLDEdttazWWlDgNxxulUrPNg/edit21:28
leongWe will present the above proposal at next UC meeting...21:28
leongany feedback and comments?21:29
leongshamail, do you have anything to add21:29
leong?21:29
*** yamamoto has quit IRC21:29
shamailWe didn't present at the last UC meeting or did it get cancelled?21:29
shamail(I missed it)21:29
leongthe agenda wasn't added to last UC meeting21:30
leongand 2 out of 3 UC wasn't there21:30
shamailOh, okay.  Nothing add.. look forward to the team's feedback.  I should be able to attend the next UC meeting as well.21:30
shamail5 of us agreed to volunteer and continue this work until the Summit.21:31
leongyup21:31
*** KrishR has left #openstack-meeting-alt21:31
shamailI will send a doodle poll once we hear feedback from UC to continue that work.21:31
Arkady_Kanevskynice proposal21:31
leong5= shamail, leong, meganr, kencjohnston and geraldk21:31
shamailOthers are welcome to join, just respond to the doodle poll when you see it.21:31
shamailWe will also be reaching out more broadly than just PWG21:31
kencjohnstonleong shamail - If I can help with the UC presentation let me know21:32
leongit will be great to get everyone else in PWG to join!21:32
Arkady_Kanevskysuggest that we are responsible that there is a rep from each required WG to attend.21:32
shamailkencjohnston: absolutely21:32
Arkady_KanevskyI can help.21:32
shamailI think Leong and yourself volunteered to present, I'll just be there to help provide support and say "YES!"21:32
leonghaha :-)21:32
shamailI don't want to schedule the doodle poll though until we get feedback from UC21:33
leongshamail: agree21:33
kencjohnstonI have to juggle around my calendar to make the UC meetings so let me know once we get on the agenda and I'll make it a priority to attend.21:33
shamailSo that's probably the next step after the UC meeting21:33
shamailkencjohnston: +1, will do21:33
leongi will take the lead to present the proposal at UC meeting, with support from Shamail and Kencjohnston :-)21:33
shamailleong: do you want to pursue getting it added to agenda or do you want me to?21:34
leongit is already added to the UC next meeting agenda... i will double check again21:34
shamailOkay, thanks21:34
leong#action Leong to check the proposal is added to UC meeting agenda21:34
leongnext topic on the agenda is Session Submissions21:35
leong#topic Session Submissions21:35
*** openstack changes topic to "Session Submissions (Meeting topic: product_working_group)"21:35
Arkady_Kanevskyfor boston summit?21:35
leongyup boston summit21:35
leongI have submitted the PWG Working Session and Kenny has submitted the BoF21:35
leongthe deadline is today 11:59pm Pacific21:36
leongi believe Shamail also submitted a Roadmap session21:36
shamailI submitted the roadmap session and added Ken and Pete for now to ensure we made the deadline.  We can revisit the session/speakers if it's accepted21:36
leong+1 shamail21:37
RockygI'm trying to get a log WG session for Boston.  Work on error code stories, spec, etc.21:37
shamailkencjohnston I meant :)21:37
shamailRockyg: Forum sessions haven't opened yet21:37
RockygWg group session, not forum21:38
shamailAh21:38
leongrockyg: you mean a Logging Working Group? do we have that?21:38
Rockyglog wg is moribund, but looks like ther's enough interest to get it going again.21:39
Arkady_Kanevskyis it worth submitting something on Themes?21:39
shamailI have to leave, boarding next flight soon :). I'll catch up via log.  Ya21:39
shamailYa21:39
Rockygleong, yup.  I am co-chair, but it's not been meeting for a while21:39
shamailTake care!*21:39
leongtake care shamail21:39
*** jungleboyj has quit IRC21:39
*** shamail has quit IRC21:39
Arkady_KanevskySHould we submit one on status on non-disruptive upgrade user story?21:40
leongrockyg: got it ..21:40
Arkady_Kanevskyor is an example of roadmap submission?21:40
leongArkady_Kanevsky: i don't get you?21:41
Arkady_Kanevskyupgrade is the olde user story we were driving.21:41
*** sdague_ has joined #openstack-meeting-alt21:41
Arkady_Kanevskyshould we submit review of results of that work. And use Tracker for it21:42
leongdo you mean an agenda item in PWG WG session? or a separate discussion session at Forum21:42
*** adrian_otto has quit IRC21:43
leongthe Forum is not opening to accept submission yet.21:43
Arkady_Kanevskysubmission for bosotn summit21:43
Arkady_Kanevskydeadline it today21:43
leongAre referring to present a "user story update" presentation for Rolling Upgrade?21:44
Arkady_Kanevskyyes21:44
leongi'm not sure how much thing we can update on "rolling upgrade"? Kencjohnston?21:45
leongkei, andyu and I have submitted a session to "promote / explain" Product WG, we plan to use Baremetal as an example.21:46
Arkady_Kanevskymy concern that we as PWG are submitting very few things for a summit. so I am thinking what can we submit that are intersteding for community21:46
kencjohnstonHmm, I'd be included to leave the updates on progress to the developers, but I agree on Arkady_Kanevsky point.21:46
kencjohnstonArkady_Kanevsky +1, it would be interesting for the community, and provide visibility21:46
Arkady_Kanevsky<leong> - cool21:46
kencjohnstonI'm not sure I could get the submission together in time, I'll try and throw something together tonight.21:46
leongok.. thanks kencjohnston21:47
heidijoyAlso the PWG will be helping to guide the PTL project sessions with a presentation template.21:47
leong#info kei, andyu and leong have submitted a session to "promote / explain" Product WG, and plan to use Baremetal as an example.21:47
Arkady_Kanevskyfor tonight we only need a short blurb. real work will come later if accepetd21:47
kencjohnstonI have until 2am right?21:47
leong11:59pm Pacific :)21:47
Arkady_KanevskyKen, I will be happy wotk work with you on it.21:47
kencjohnstonleong Right, like I said, 2am for me21:47
kencjohnstonArkady_Kanevsky +1 thanks, I'll shoot you a note21:48
Arkady_Kanevsky+121:48
leong#info Kencjonston and Arkady_Kanevsky will work on an update for Rolling Upgrade user-story21:48
leonganything else on this agenda?21:48
leong#topic Simplifying User Story Submission21:49
*** openstack changes topic to "Simplifying User Story Submission (Meeting topic: product_working_group)"21:49
leong#link https://etherpad.openstack.org/p/PWG-story-submission-ideas21:49
Rockyg++21:49
leongi think we can discuss this at Midcycle as well on how to simplify user story submission?21:50
Arkady_Kanevsky+1 leong21:50
leongPlease continue to brainstorm and put your suggestion on the above etherpad21:50
leong#agreed Leong to include "Simplifying User Story Submission" in PWG Midcycle Agenda21:51
leong#topic Open21:51
*** openstack changes topic to "Open (Meeting topic: product_working_group)"21:51
AndyUIs the name going to possibly change? From "Story" to something higher level sounding?21:51
leongAndyU: someone brought up that point as well, can you add that into the etherpad?21:52
AndyUwill do21:52
Arkady_Kanevskywill comment on etherpad21:52
leongany open item for the remaining 8 mins21:52
leongi have one item for Open discussion...21:53
leongis about LCOO21:53
leongLCOO is a new WG that initiated by few large operators (AT&T, Orange, NTT, etc...)21:53
*** Swami has quit IRC21:54
leongthey are still in a planning phase.. and AndyU is a co-chair of LCOO roadmap team21:54
Arkady_KanevskyI saw that. do we really need a new group for it?21:54
Rockygleong, thanks for bringing this up.21:54
leongI was involved/engaged in recent conversation.. i think we, as in Product WG, can help to group to integrate with the community?21:55
leongLCOO is keen to adopt our PWG workflow21:55
*** dprince has quit IRC21:55
Arkady_KanevskyWhy is Telco group not sufficient for it?21:55
RockygIt would be great if they could just integrate into existing WGs21:55
heidijoyAdditional topic: FYI, I'm distributing roadmap survey request today to PTLs - 25 projects covered - for the Ocata cycle & beyond.21:55
RockygMight give the WGs some extra energy21:55
leongthe Telco group is a different function from LCOO21:55
leongthanks heidijoy21:55
*** ansmith has quit IRC21:56
Arkady_KanevskyLove it if they use our workflow21:56
leong#info Heidijoy is distributing roadmap survey request today to PTLs - 25 projects covered - for the Ocata cycle & beyond21:56
heidijoyThe foundation is looking to the PWG for help in prioritizing/highlighting Ocata features that support our "one platform" message.21:56
kencjohnstonheidijoy Where can we get more details on what we mean by "one platform"?21:57
heidijoyour “one platform” message—that OpenStack enables users to coordinate virtual machines, bare metal, containers and other emerging technologies from a single platform. If your team’s features support this effort, please explain how they do so on the survey so we can highlight your project.21:57
leongi am hoping that PWG members here can help to collaborate with LCOO... one example is the Logging feature21:57
Arkady_Kanevskyheidi what help do you envision from PWG?21:58
heidijoykencjohnston: I'll follow up for a better description21:58
kencjohnstonheidijoy No worries, that gets me started :)21:58
AndyULCOO is definitely seeking to collaborate with PWG21:58
heidijoyarkady_kanevsky: Looking for a few PWG folks to review the spreadsheet of answers and make notes (Google Sheets) on what has strong end-user benefit and/or significance for "one platform"21:59
*** dizquierdo has quit IRC21:59
Arkady_Kanevskyheidi - I will be happy to help21:59
leongany questions for LCOO?21:59
Arkady_Kanevskyare LCOO meeting at Milan?21:59
RockygWill anyone be attending tonight's PWG from LCOO?21:59
leongArkady, heidijoy, ken: will take note on that discussion with "one platform"22:00
Arkady_KanevskyIf yes, can we invite them to "joint: meetong?22:00
leongyes... AndyU from LCO is planning to22:00
RockygThanks122:00
AndyURockyG: not that I know of, but perhaps22:00
leongsorry... i refer to Milan meeting22:00
Rockyg10pm PST22:00
leongRockyg, i will discuss that in tonight regional meeting22:00
RockygLate for folks with farms22:00
AndyUYes, I'm hoping to join you in Milan. Not approved to travel yet though.22:01
mordredRockyg: people can stay up late on the farm too :)22:01
Arkady_Kanevskyneec to drop22:01
AndyURocky G; ha ha22:01
leongwe hit the hour..22:01
leongplease direct questions to mailing list if necessary22:01
leong#endmeeting22:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"22:01
openstackMeeting ended Mon Feb  6 22:01:57 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/product_working_group/2017/product_working_group.2017-02-06-21.00.html22:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/product_working_group/2017/product_working_group.2017-02-06-21.00.txt22:02
openstackLog:            http://eavesdrop.openstack.org/meetings/product_working_group/2017/product_working_group.2017-02-06-21.00.log.html22:02
jeblairhi zuul folks!22:02
*** MeganR has quit IRC22:02
fungimmm22:02
*** jamielennox has joined #openstack-meeting-alt22:02
adam_ghi there22:02
clarkbhello22:02
*** hichihara has quit IRC22:02
* mordred pours another glass of tea22:02
pabelangerhi22:02
*** heidijoy has quit IRC22:02
jeblair#startmeeting zuul22:03
openstackMeeting started Mon Feb  6 22:03:04 2017 UTC and is due to finish in 60 minutes.  The chair is jeblair. Information about MeetBot at http://wiki.debian.org/MeetBot.22:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.22:03
*** openstack changes topic to " (Meeting topic: zuul)"22:03
openstackThe meeting name has been set to 'zuul'22:03
jeblair#link agenda https://wiki.openstack.org/wiki/Meetings/Zuul22:03
*** AndyU has quit IRC22:03
jeblair#link previous meeting http://eavesdrop.openstack.org/meetings/zuul/2017/zuul.2017-01-30-22.00.html22:03
*** leong has quit IRC22:03
SpamapSo/22:03
*** jmckind has quit IRC22:03
jeblairi'd like to reserve at least the last 20 minutes for talk about the ptg22:04
jeblairso with that22:04
jeblair#topic Status updates: Nodepool Zookeeper work22:04
*** openstack changes topic to "Status updates: Nodepool Zookeeper work (Meeting topic: zuul)"22:04
jhesketho/22:04
jamielennoxo/22:05
*** AlanClark has quit IRC22:05
jeblairShrews is continuing work on having nodepool actually return nodes22:06
Shrews428428 makes our integration job pass22:06
fungithat would be useful22:06
pabelangerShrews: nice work22:07
jeblairShrews: now might be a good time for someone to jump in and update the nodepool cli commands to use zookeeper?  if you think so, and no one else does that soon, i may...22:07
morgan:)22:07
*** Arkady_Kanevsky has quit IRC22:08
Shrewsjeblair: i think someone could begin poking at that. i won't get to it anytime soon22:08
pabelangerIf we are ready to start using more zookeeper in nodepool, I don't mind poking into that again. It went quite well last time22:08
*** beslemon has quit IRC22:08
SpamapSjeblair: is there a story for that yet?22:08
* SpamapS can make one22:09
jeblairSpamapS: don't think so, and thanks22:09
* SpamapS makes it22:09
*** mfedosin has quit IRC22:09
*** matrohon has quit IRC22:10
jeblair#topic Status updates: Devstack-gate roles refactoring22:10
*** openstack changes topic to "Status updates: Devstack-gate roles refactoring (Meeting topic: zuul)"22:10
jeblairrcarrillocruz, clarkb: where you talking about that earlier?22:11
SpamapSFYI: https://storyboard.openstack.org/#!/story/200085622:11
clarkbjeblair: yes, I think the current patchset on the first change is good to go22:11
*** yamamoto has joined #openstack-meeting-alt22:11
rcarrillocruzyeah, passing tempest tests now in zuul22:11
rcarrillocruzjust needs a +A22:11
jeblair#link nodepool zk cli work can begin https://storyboard.openstack.org/#!/story/200085622:11
clarkbthe second still has a -1 from previous reviews that will need addressing (I think rcarrillocruz may be trying to reduce number of iterations and focus on one at a time)22:11
rcarrillocruzy22:11
*** Rockyg has quit IRC22:12
jeblairrcarrillocruz, clarkb: so 403732 is ready?22:12
clarkbyes I think so22:12
rcarrillocruzimho yeah22:13
jeblair#link devstack-gate roles change ready for approval https://review.openstack.org/40373222:13
*** dizquierdo has joined #openstack-meeting-alt22:13
jeblair#link next devstack-gate roles change https://review.openstack.org/40424322:13
jeblair#topic Status updates: Zuul test enablement22:14
*** openstack changes topic to "Status updates: Zuul test enablement (Meeting topic: zuul)"22:14
jeblaira bunch of those just showed up recently!  :)22:15
adam_gi've started to pick up some low hangers again between doing other things..22:15
*** dustins has quit IRC22:15
adam_gi noticed test_dependent_behind_dequeue, which was recently reenabled, doesnt seem to be too stable. i had to recheck against it a few times and noticed others had to as well22:15
jeblairalso -- reminder that we merged a change that requires a playbook for every test job now.  there's a make_playbooks.py script in zuul/tests to help automate that.22:15
pabelangerI've fixed my conflicts today, and started on the conflict project tests today22:16
jeblairadam_g: yeah, i recently made it more stable by extending the timeouts (it's a very busy test), but there have now been a few failures of it since then, so there's still something going on22:16
adam_gah22:17
jeblairwe also just merged a change which attaches full debug logs on test failures, so as long as it doesn't manifest as a timeout (which this one, unfortunately, often does) we can actually fix them.22:17
pabelangerhttps://review.openstack.org/#/c/393887/ is particularly easy :)22:17
*** gouthamr has quit IRC22:17
jeblair(the fact that it times out now is not likely because it's slow, but rather an error that just manifests as never reaching the stable condition)22:18
SpamapSjeblair: does our test zookeeper make use of tmpfs? That might help.22:18
SpamapSoh that22:19
jeblairSpamapS: good point; i don't think so.22:19
*** kfarr has quit IRC22:19
jeblairSpamapS: oh, but you know what, zk is usually pretty fast on tests in our cloud providers....22:19
SpamapSyeah22:19
SpamapSWith so much RAM22:19
SpamapSI'd expect it to mostly just buffer. Though ZK can be sync-happy22:20
SpamapSbecause journals22:20
jeblairyeah... maybe our clouds either have battery backed caches or just turn on data-eating.22:20
SpamapSprobably former for most.22:20
morgan hah22:20
jeblairand the latter for infra-cloud, iirc...22:20
morganyeah22:20
SpamapSeither way, we could look at io wait if we were concerned22:20
morganset value eat_data22:21
morgantrue22:21
SpamapSeatmydata is a thing you know :)22:21
mordredworld's best LD_PRELOAD library22:21
jeblairwe may want to collect the zk logs from tests...22:21
SpamapSI like to load it with libhostile and let them fight it out22:21
mordredjeblair: ++22:21
*** dizquierdo has quit IRC22:21
* fungi smells a new theme show in the making22:22
jeblair#topic Status updates: Zuul Ansible running22:22
*** openstack changes topic to "Status updates: Zuul Ansible running (Meeting topic: zuul)"22:22
jeblairmy patch series to enable pre and post playbooks is making its way in (i have some random test failures to debug -- see earlier topic :)22:22
jeblairmordred has a change built on that to start securing the insecure playbooks22:23
jeblair#link playbook security https://review.openstack.org/42879822:23
mordredyes. and then we found a whole new set of ways in which playbooks can be insecure22:23
* mordred glares at roles22:23
pabelangerfuntimes22:23
mordredyah22:23
jeblairbut also sketched out some solutions for that, yeah?22:23
mordredyah22:23
SpamapSohmy22:23
clarkbmordred: just reading the commit message on that seems like you'll have to audit and patch after every ansible release?22:24
SpamapSIs this where we ask how this happened and somebody goes <cough>tower</cough>22:24
mordredjeblair: it may be worth mentioning that due to security lockdown, we may also want to develop a stdlib role that knows how to run ansible on the remote host as if it was the local host job content22:24
mordredSpamapS: actually - not really, it's more that the idea of running untrusted ansible code isn't a use case they really focus on22:24
SpamapSOh, joy, this also means Zuul gets to be partially GPLv322:25
mordredyup. this, of course, causes me to have a warm and fuzzy feeling22:25
clarkbmordred: I'd worry about missing things and further complicating the ansible has pushed security update hurry and fix/upgrade22:25
pabelangeris it possible we could have the idea of secure / insecure zuul-launchers?  I know that doesn't scale well22:25
SpamapSmordred: would a simpler thing be to just run it in a throw-away container?22:25
jeblairmordred: you mean like push the inventory over and run something?  that sounds helpful.22:25
mordredso - yes, I agree with clarkb, although from ansible core we really only need to worry about new action plugins (not very likely) or entirely new types of plugins (also not very common)22:26
mordredwe don't have to look at every patch22:26
mordredSpamapS: ALSO looking at using some container tech here - but no, I do not think container == security yet22:26
pabelanger( I guess now, since our zuul-launchers are in the control plane)22:26
jeblairpabelanger: that's not really the problem here as much as the fact that jobs need to run some secure things and some insecure things.22:26
pabelangernot*22:26
pabelangerjeblair: ya22:26
mordredSpamapS: I think container + careful code can together be better than either one in isolation22:27
jeblairactual defense in depth :)22:27
mordredso specifically looking at giftwrap which allows for construction and execution of unprivileged containers - so that we don't have to escalate zuul-launcher to root before adding in the containment :)22:27
*** pvaneck has quit IRC22:27
jeblairmordred: bubble wrap?22:27
*** pvaneck has joined #openstack-meeting-alt22:28
mordredgah. bubblewrap. yes.22:28
mordredhttps://github.com/projectatomic/bubblewrap22:28
mordredit needs a fairly new kernel though - so the support for it will need to be opt-in for operators I think22:28
* mordred needs to write up some thoughts on this for folks22:28
pabelangeroh, new things to look at22:28
mordredjeblair: and yes to "push the inventory over and run something?" ... jlk was asking about using zuul to test ansible that relies on plugins that we don't allow people to run with22:29
pabelangermordred: that is a neat idea22:29
mordredjeblair: and that's _totally_ possible by writing a playbook that does a shell call to ansible22:29
mordredbut ... you know ... we can likely make that experience a little better :)22:29
clarkbmordred: mostly I don't want to replace one security issue with another via upgrade of ansible by ops that don't understand caveats here22:29
mordredclarkb: yup. it's definitely an area where we need WAY more prose about what's going on for all of us, and then make sure that we're happy with how we're covering it22:30
clarkbif the class of objects that are an issue is small maybe we can do terrible nasty python to intercept all dispatches to them and sanitize appropriately22:30
clarkbrather than having hard coded sanitization for known issues today22:31
mordredyah - so - there are 2 prongs we need to deal with22:31
jeblairclarkb: well, we don't use ansible as a library, so the solution has to be in ansible configuration...22:31
mordredone are ansible in-tree action-plugin based modules - these do execptional things like the copy module22:31
mordredand execute code on purpose on the calling host22:31
mordredbut there is a fixed set of them and it's easy to vet those22:31
mordredthe _other_ is that roles can ship with plugins (action plugins, filter plugins, etc) that will run python code on the calling machine22:32
jeblair(i'm going to call time on this at 22:35, btw)22:32
mordredin that case, the approach we've discussed so far is to scrub roles when we fetch them for plugin directories (known set of names)22:32
mordredand if a role has a plugin dir with content, just fail hard22:32
mordredso doing those two things AND adding in containment22:32
*** ijw has quit IRC22:33
SpamapScould also neuter ansible's plugin loading22:33
mordredshould hopefully get us fairly decent coverage ... we could also potentially talk to our friends at ansible and request they warn us if they're going ot release new local-execution action plugins22:33
mordredSpamapS: yah - bcoca talked a bit about that22:33
clarkbmordred: right my concern is ansible adds new actionmodule or changes one arbitrarily22:33
SpamapSJust have a plugin that literally overrides the plugin loader with a pass.22:33
jeblairyeah, so we're going to be as general as we can be (eg the plugins in roles), but we don't have a good general way to stop the in-tree plugins  atm.22:34
mordredSpamapS: and also mused about hte possibility of adding a neuter plugins option to ansible itself22:34
clarkbmordred: and then next zuul update and now you are vulnerable (and that would be a much larger target if/when people are using zuul with ansible)22:34
SpamapSOr an "splodey splode, no plugins allowed"22:34
jeblairclarkb: yes, i agree with your concern22:34
mordredclarkb: yah - that's one where we're going to need to connect with ansible release managmenet in addition to doing defensive coding on our part22:34
clarkbmordred: having contributed to one of those action modules recently I don't think its terribly hard to change the behavior of them in such ways (as people don't seem to grok how they work very well)22:34
mordredclarkb: definitely a concern22:34
fungii definitely hadn't thought of that, but i can see it as a possibility22:34
jeblairbut we're hoping that's a small load due to the rarity in adding such new modules.22:35
SpamapSclarkb: I share your concern, and think that one has to also wrap it up in a system level protection of some kind.22:35
mordred(but yeah, this is why I think adding container wrapping to the mix will give us buffer too)22:35
mordredyup22:35
mordredSpamapS: ++22:35
* SpamapS will look at bubblewrap22:35
*** xin9972 has quit IRC22:35
jeblairgreat segue22:35
mordredSpamapS: it needs yakkety on ubuntu, fwiw - needs new kernel22:35
mordredSpamapS: or, needs that to be able to run without sudo stuff22:35
jeblair#topic  Progress summary22:35
*** openstack changes topic to "Progress summary (Meeting topic: zuul)"22:35
* jeblair hands link baton to SpamapS 22:36
*** baoli has quit IRC22:36
*** dizquierdo has joined #openstack-meeting-alt22:37
*** strigazi_AFK has quit IRC22:37
*** xin9972 has joined #openstack-meeting-alt22:37
*** strigazi_AFK has joined #openstack-meeting-alt22:38
*** jheroux has quit IRC22:38
*** tonytan4ever has quit IRC22:38
SpamapSahoy22:40
SpamapSsorry I got alt-tabbed and tried to refresh and fell off the earth22:40
SpamapS#link https://storyboard.openstack.org/#!/board/4122:40
jeblairlet's come back to this if we have time at the end22:40
fungiflat earth will do that to you22:40
SpamapSNot much to say anyway22:40
SpamapSProgress continues.22:40
jeblairthat works out then :)22:40
jeblair#topic PTG prep (jeblair)22:40
*** openstack changes topic to "PTG prep (jeblair) (Meeting topic: zuul)"22:40
* fungi is a fan of progress22:40
jeblairso we've got a thing coming up soon22:41
fungilike, real soon22:41
jeblair2 weeks?22:41
fungiright at, yes22:41
pabelangeryay travel22:41
SpamapScrikey22:41
SpamapSso much travel :_P22:41
jeblairi think at this point, we probably have a good idea what's feasible22:41
mordred++22:42
jeblairwe should hopefully have nodepool at least able to hand out some nodes, even if it still doesn't do a lot of things22:42
jeblairand we should have zuul able to run some jobs, even if it doesn't do a lot of things22:42
jeblairso i think it's well within the realm of possibility that we can set up a v3 nodepool and zuul, and have them run some hello world jobs22:43
SpamapSI'd also like to have all tests re-enabled/refactored/done by the time I fly out Thursday night.22:43
fungiare our current puppet-zuul/puppet-nodepool modules up to the task of deploying what's in the feature branches yet?22:43
jeblairto that end, there are probably some things we can do to prepare for that22:43
SpamapS(while we focus on the pragmatic thing first, I want to make a real push while I have your brains in view)22:43
*** dizquierdo_ has joined #openstack-meeting-alt22:43
jeblairfungi: probably close, but probably not.22:43
fungijust curious if hello world is going to involve a lot of manual deployment22:43
jeblairSpamapS: i would support that as a very worthy secondary goal :)22:44
pabelangerwhat is left to do for nodepool zookeeper production? I am assuming mordred shim? (CLI commands?)22:44
fungior if we should try to work out the adjustments to puppet necessary to hello world it as part of the task22:44
SpamapSIt's a stretch goal for sure.22:44
*** eggmaster has quit IRC22:44
jeblairpabelanger: i don't think we need the shim for this22:44
pabelangerack22:44
jeblair(the shim is for zuul v2 -> nodepool v3)22:45
pabelangergot it22:45
*** EricGonczer_ has quit IRC22:45
Shrewspabelanger: actual node launches (not just record entries in ZK) needs to be completed22:45
fungibasically set up demo environment by hand and taking notes, vs deploying demo env using (patched) puppet modules so we can more directly translate that to the chnages we'll need to make22:45
pabelangerShrews: thanks for the info22:45
jeblair(fortunately, there's a body of code that does launches, so we're not starting from zero)22:45
Shrewsright22:46
jeblairfungi: we may well end up doing some manual deployment, but otoh, maybe in the intervening 2 weeks, we could do some puppet work and have at least some of that codified22:46
*** dizquierdo has quit IRC22:47
jeblairlet's start an etherpad: https://etherpad.openstack.org/p/pike-ptg-zuul22:47
fungijeblair: thanks, just wondering if anyone has a feel for where we can strike that balance of effort vs expediency22:47
pabelangerwe didn't need to change puppet-nodepool too much for zookeeper things first time. But agree, we should try to land patches at the same time22:47
fungii do want to make sure we can have something viable we can at least feel good about by the end of tuesday, so if that means config management changes get mostly punted to later i'm cool with that22:48
fungiwould be awesome to say "zuul v3 ran a job"22:48
mordred++22:48
jeblairyep22:49
pabelangerjeblair: the plan is to have nl01.o.o eventually? (nodepool-launcher)22:49
jeblairpabelanger: sounds reasonable22:49
Shrewsmaybe we can begin making notes for any documentation that may need written22:49
pabelangerk22:49
mordredShrews: ++22:49
jeblairokay, take a look at that etherpad and let me know if there is anything else we should prep beforehand to increase our chances of success22:50
jeblairobviously the first two are very important22:50
jeblairthe next few about deployment and setting up a server are things that would be really good to do ahead of time so we don't spend 2 days watching someone boot a server22:51
pabelanger++22:51
jeblairi'd love it if someone would volunteer to take the lead on prepping a platform for us to work from at the ptg22:51
pabelangerI can start doing some prep tomorrow for that22:51
jeblairi think pabelanger just volunteered for that :)  thanks22:51
fungi"platform" meaning server instances?22:51
jeblairyeah22:52
fungioh, and i guess a tenant/namespace/whatever for the test nodes22:52
jeblairso, new servers so that we don't touch any of the current system22:52
pabelanger++22:52
jeblairfungi: i think at our scale, we can just steal some quota from our current nodepool tenants22:52
jeblair(maybe bump the production quota down a little bit on one of them?)22:53
fungiwfm. we do have unique identifiers implemented for nodepool's alien cleanup instance metadata right?22:53
*** cdelatte has joined #openstack-meeting-alt22:53
fungii know we discussed having that so two could coexist on the same tenant was preferred but can't remember if it ever got implemented22:53
*** fnaval has quit IRC22:54
*** pradk has quit IRC22:54
clarkbfungi: ya nodepool should only delete leaks that it booted22:54
clarkb(and if it doesn't we should fix that too)22:54
fungijust want to make sure bringing up a demon nodepool pointed at one of our production tenants won't start sniping the production nodepool nodes22:54
jeblairlet's check on that22:54
Shrewsyep. won't delete an image unless the DIB is local22:54
fungis/demon/demo/ (fun typo though)22:54
jeblairfungi: oh, that probably won't happen because we probably won't have cleanup in v3 implemented22:54
jeblairfungi: i think the other direction is a possibility22:55
*** cdelatte has quit IRC22:55
fungiah, so worst case nodepool v0.x production might blow away our demon nodes before they run anything22:55
clarkbits certainly the intent of the laek cleanup code to only delete things that it once booted and knew about22:55
*** stingaci has joined #openstack-meeting-alt22:56
fungii thought we had talked about adding a config option where you could put a unique string for each nodepool scheduler so it could differentiate its own node metadata from someone else's22:56
jeblairthe last item i put on the list is something i'll volunteer for -- to write up what what we all need to know about the current and future state of both pieces of software in order to productively work on a hello-world job at the ptg22:56
Shrewsgrr, yeah nodes, not images. doubtful cleanup will be implemented by then22:56
fungiwow, i keep typing demon instead of demo. what is up with that finger memory?22:56
Shrewsfungi: i'm living proof brains break after 5pm22:57
jeblairmordred: it would probably be good if we have a handle on some of the security stuff by then, otherwise we may not be able to publish logs for our hello world job22:57
mordredjeblair: ++22:57
*** rockyg has joined #openstack-meeting-alt22:57
fungi"we ran a job, but its logs were too insecure to fit in this margin"22:57
jeblairbasically22:57
jeblairi put some names on the etherpad, if you would like names added or removed, let me know22:58
jeblairalso, if you think of anything else we need to do before then so we're not sitting on our thumbs at the ptg, add it / let me know22:58
jeblairfungi: think this is probably worth a mention at the infra meeting tomorrow?22:59
fungii think it's definitely worth mentioning, yes22:59
jeblair#link actions to prepare for pike ptg https://etherpad.openstack.org/p/pike-ptg-zuul22:59
jeblairwill do22:59
fungigiven the timing, we should spend a good chunk of tomorrow on ptg topics22:59
fungithanks!23:00
jeblairthanks everyone!23:00
jeblair#endmeeting23:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"23:00
openstackMeeting ended Mon Feb  6 23:00:12 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)23:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/zuul/2017/zuul.2017-02-06-22.03.html23:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/zuul/2017/zuul.2017-02-06-22.03.txt23:00
openstackLog:            http://eavesdrop.openstack.org/meetings/zuul/2017/zuul.2017-02-06-22.03.log.html23:00
*** Shrews has left #openstack-meeting-alt23:00
*** lpetrut has quit IRC23:02
*** jaugustine has quit IRC23:05
*** jamielennox has left #openstack-meeting-alt23:11
*** rockyg has quit IRC23:14
*** jkilpatr has quit IRC23:16
*** spzala has quit IRC23:17
*** dizquierdo_ has quit IRC23:22
*** ihrachys has quit IRC23:24
*** zhonghua2 has joined #openstack-meeting-alt23:24
*** hongbin_ has joined #openstack-meeting-alt23:25
*** salv-orl_ has joined #openstack-meeting-alt23:26
*** fzhadaev_ has joined #openstack-meeting-alt23:26
*** igormarnat__ has joined #openstack-meeting-alt23:27
*** iremizov_ has joined #openstack-meeting-alt23:27
*** boris-42_ has joined #openstack-meeting-alt23:27
*** xin99721 has joined #openstack-meeting-alt23:27
*** ildikov_ has joined #openstack-meeting-alt23:27
*** kozhukalov_ has joined #openstack-meeting-alt23:27
*** hrybacki_ has joined #openstack-meeting-alt23:27
*** evgenyl_ has joined #openstack-meeting-alt23:27
*** dasanind_ has joined #openstack-meeting-alt23:27
*** nikhil_ has joined #openstack-meeting-alt23:27
*** nikhil_ is now known as Guest449123:27
*** DuncanT_ has joined #openstack-meeting-alt23:28
*** sulo_ has joined #openstack-meeting-alt23:28
*** xyang1 has quit IRC23:28
*** zerick_ has joined #openstack-meeting-alt23:29
*** matbu_ has joined #openstack-meeting-alt23:29
*** dosaboy_ has joined #openstack-meeting-alt23:30
*** strigazi1AFK has joined #openstack-meeting-alt23:30
*** sdague has quit IRC23:30
*** eliqiao_ has joined #openstack-meeting-alt23:30
*** jrobinson has joined #openstack-meeting-alt23:31
*** sballe__ has joined #openstack-meeting-alt23:31
*** johnsom_ has joined #openstack-meeting-alt23:31
*** netapp_ has joined #openstack-meeting-alt23:31
*** krugg_ has joined #openstack-meeting-alt23:32
*** electrichead has joined #openstack-meeting-alt23:32
*** yantarou_ has joined #openstack-meeting-alt23:33
*** mickeys has joined #openstack-meeting-alt23:33
*** mmedvede_ has joined #openstack-meeting-alt23:33
*** shaohe_feng_ has joined #openstack-meeting-alt23:33
*** ddellav_ has joined #openstack-meeting-alt23:33
*** arunkant has left #openstack-meeting-alt23:33
*** strigazi_AFK has quit IRC23:34
*** xin9972 has quit IRC23:34
*** salv-orlando has quit IRC23:34
*** zhonghua has quit IRC23:34
*** hongbin has quit IRC23:34
*** neiljerram has quit IRC23:34
*** DuncanT has quit IRC23:34
*** shaohe_feng has quit IRC23:34
*** krugg has quit IRC23:34
*** matbu has quit IRC23:34
*** mordred has quit IRC23:34
*** saisriki has quit IRC23:34
*** samP has quit IRC23:34
*** ddellav has quit IRC23:34
*** IgorYozhikov has quit IRC23:34
*** dosaboy has quit IRC23:34
*** slunkad has quit IRC23:34
*** sankarshan has quit IRC23:34
*** eliqiao has quit IRC23:34
*** johnsom has quit IRC23:34
*** igormarnat_ has quit IRC23:34
*** nikhil has quit IRC23:34
*** iremizov has quit IRC23:34
*** dustymabe has quit IRC23:34
*** xgerman has quit IRC23:34
*** ildikov has quit IRC23:34
*** zerick has quit IRC23:34
*** fzhadaev has quit IRC23:34
*** evgenyl has quit IRC23:34
*** netapp has quit IRC23:34
*** mmedvede has quit IRC23:34
*** redrobot has quit IRC23:34
*** kozhukalov has quit IRC23:34
*** hrybacki has quit IRC23:34
*** sballe_ has quit IRC23:34
*** dasanind has quit IRC23:34
*** boris-42 has quit IRC23:34
*** sulo has quit IRC23:34
*** nibalizer has quit IRC23:34
*** yantarou has quit IRC23:34
*** netapp_ is now known as netapp23:34
*** krugg_ is now known as krugg23:34
*** shaohe_feng_ is now known as shaohe_feng23:34
*** yantarou_ is now known as yantarou23:34
*** iremizov_ is now known as iremizov23:34
*** fzhadaev_ is now known as fzhadaev23:34
*** igormarnat__ is now known as igormarnat_23:35
*** mmedvede_ is now known as mmedvede23:35
*** jkilpatr has joined #openstack-meeting-alt23:35
*** IgorYozhikov has joined #openstack-meeting-alt23:35
*** dasanind_ is now known as dasanind23:35
*** evgenyl_ is now known as evgenyl23:36
*** ildikov_ is now known as ildikov23:36
*** kozhukalov_ is now known as kozhukalov23:36
*** Guest4491 is now known as nikhil23:36
*** sballe__ is now known as sballe_23:36
*** DuncanT_ is now known as DuncanT23:36
*** hrybacki_ is now known as hrybacki23:37
*** boris-42_ is now known as boris-4223:37
*** johnsom_ is now known as johnsom23:37
*** adrian_otto has joined #openstack-meeting-alt23:39
*** dimtruck is now known as zz_dimtruck23:39
*** sdake has quit IRC23:39
*** mordred has joined #openstack-meeting-alt23:40
*** slunkad has joined #openstack-meeting-alt23:40
*** samP has joined #openstack-meeting-alt23:40
*** neiljerram has joined #openstack-meeting-alt23:40
*** nibalizer has joined #openstack-meeting-alt23:42
*** dustymabe has joined #openstack-meeting-alt23:42
*** mdong has quit IRC23:45
*** mdong has joined #openstack-meeting-alt23:45
*** ansmith has joined #openstack-meeting-alt23:50
*** gouthamr has joined #openstack-meeting-alt23:57
*** EricGonczer_ has joined #openstack-meeting-alt23:59

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