Monday, 2017-02-13

*** Leo_ has joined #openstack-meeting-alt00:01
*** jrobinson has quit IRC00:02
*** jrobinson has joined #openstack-meeting-alt00:04
*** caowei has quit IRC00:20
*** baoli has joined #openstack-meeting-alt00:22
*** baoli has quit IRC00:23
*** baoli has joined #openstack-meeting-alt00:23
*** ansiwen has quit IRC00:29
*** ansiwen has joined #openstack-meeting-alt00:30
*** EricGonczer_ has quit IRC00:31
*** baoli has quit IRC00:38
*** jkilpatr has quit IRC00:45
*** noslzzp has quit IRC00:54
*** julim has quit IRC00:55
*** dimtruck is now known as zz_dimtruck01:02
*** zz_dimtruck is now known as dimtruck01:13
*** ricolin has joined #openstack-meeting-alt01:16
*** nmagnezi has quit IRC01:18
*** sileht has quit IRC01:19
*** beekhof has quit IRC01:19
*** iberezovskiy_ has quit IRC01:20
*** nmagnezi has joined #openstack-meeting-alt01:20
*** iberezovskiy has joined #openstack-meeting-alt01:21
*** sileht has joined #openstack-meeting-alt01:23
*** salv-orlando has joined #openstack-meeting-alt01:23
*** hiro-kobayashi has joined #openstack-meeting-alt01:23
*** salv-orlando has quit IRC01:27
*** caowei has joined #openstack-meeting-alt01:39
*** tuanluong has joined #openstack-meeting-alt01:41
*** gongysh has joined #openstack-meeting-alt01:41
*** baoli has joined #openstack-meeting-alt02:04
*** julim has joined #openstack-meeting-alt02:10
*** edtubill has joined #openstack-meeting-alt02:25
*** xin9972 has joined #openstack-meeting-alt02:31
*** mixos has quit IRC02:33
*** baoli has quit IRC02:33
*** sdake has joined #openstack-meeting-alt02:35
*** armax has joined #openstack-meeting-alt02:35
*** sdake_ has joined #openstack-meeting-alt02:39
*** sdake has quit IRC02:43
*** tovin07 has joined #openstack-meeting-alt02:55
*** anilvenkata has joined #openstack-meeting-alt02:55
*** mickeys has joined #openstack-meeting-alt02:55
*** tovin07_ has joined #openstack-meeting-alt02:57
*** mickeys has quit IRC03:00
*** gouthamr has quit IRC03:03
*** liuyulong has joined #openstack-meeting-alt03:05
*** diablo_rojo has joined #openstack-meeting-alt03:11
*** EricGonczer_ has joined #openstack-meeting-alt03:14
*** sdake has joined #openstack-meeting-alt03:17
*** sdake_ has quit IRC03:18
*** armax has quit IRC03:21
*** salv-orlando has joined #openstack-meeting-alt03:24
*** salv-orlando has quit IRC03:28
*** gongysh has quit IRC03:39
*** sdake has quit IRC03:49
*** xin9972 has quit IRC03:49
*** julim has quit IRC03:55
*** julim has joined #openstack-meeting-alt03:57
*** janki has joined #openstack-meeting-alt03:59
*** julim has quit IRC04:01
*** mickeys has joined #openstack-meeting-alt04:01
*** julim has joined #openstack-meeting-alt04:04
*** EricGonczer_ has quit IRC04:08
*** diablo_rojo has quit IRC04:14
*** hiro-kobayashi has quit IRC04:23
*** hiro-kobayashi has joined #openstack-meeting-alt04:23
*** jrobinson is now known as jrobinson-afk04:40
*** ricolin has quit IRC04:48
*** skramaja has joined #openstack-meeting-alt04:51
*** salv-orlando has joined #openstack-meeting-alt04:54
*** salv-orlando has quit IRC04:59
*** adisky_ has joined #openstack-meeting-alt05:00
*** tonanhngo has joined #openstack-meeting-alt05:14
*** tonanhngo has quit IRC05:16
*** mtreinish has quit IRC05:20
*** mtreinish has joined #openstack-meeting-alt05:31
*** Rockyg has quit IRC05:32
*** amotoki has joined #openstack-meeting-alt05:33
*** amotoki has quit IRC05:36
*** trinaths has joined #openstack-meeting-alt05:39
*** amotoki has joined #openstack-meeting-alt05:48
*** janki has quit IRC05:50
*** jrobinson-afk is now known as jrobinson05:51
*** trinaths has left #openstack-meeting-alt05:55
*** salv-orlando has joined #openstack-meeting-alt05:55
*** salv-orlando has quit IRC06:00
*** janki has joined #openstack-meeting-alt06:00
*** gcb has joined #openstack-meeting-alt06:00
*** saneax-_-|AFK is now known as saneax06:02
*** mickeys has quit IRC06:04
*** jrist has joined #openstack-meeting-alt06:04
*** pgadiya has joined #openstack-meeting-alt06:07
*** amotoki has quit IRC06:10
*** edtubill has quit IRC06:18
*** edtubill has joined #openstack-meeting-alt06:19
*** lpetrut has joined #openstack-meeting-alt06:21
*** amotoki has joined #openstack-meeting-alt06:23
*** edtubill has quit IRC06:24
*** dsariel has joined #openstack-meeting-alt06:27
*** Leo_ has quit IRC06:40
*** dsariel_ has joined #openstack-meeting-alt06:41
*** salv-orlando has joined #openstack-meeting-alt06:43
*** beekhof has joined #openstack-meeting-alt06:49
*** hiro-kobayashi has quit IRC06:52
*** sridharg has joined #openstack-meeting-alt07:00
*** salv-orl_ has joined #openstack-meeting-alt07:00
*** liuyulong_ has joined #openstack-meeting-alt07:00
*** Leo_ has joined #openstack-meeting-alt07:00
*** liuyulong has quit IRC07:03
*** salv-orlando has quit IRC07:03
*** mickeys has joined #openstack-meeting-alt07:05
*** jrobinson has quit IRC07:07
*** mickeys has quit IRC07:10
*** nkrinner_afk is now known as nkrinner07:12
*** r-mibu has quit IRC07:15
*** rcernin has joined #openstack-meeting-alt07:15
*** lpetrut has quit IRC07:17
*** tremble has joined #openstack-meeting-alt07:18
*** tesseract has joined #openstack-meeting-alt07:28
*** tesseract is now known as tesseract-RH07:29
*** ircuser-1 has joined #openstack-meeting-alt07:30
*** yamamoto has quit IRC07:34
*** ijw has joined #openstack-meeting-alt07:38
*** nadya has joined #openstack-meeting-alt07:41
*** nadya has quit IRC07:42
*** nadya has joined #openstack-meeting-alt07:42
*** ralonsoh has joined #openstack-meeting-alt07:46
*** rarcea has joined #openstack-meeting-alt07:55
*** gcb has quit IRC07:57
*** mickeys has joined #openstack-meeting-alt08:07
*** pnavarro has joined #openstack-meeting-alt08:10
*** mickeys has quit IRC08:11
*** matrohon has joined #openstack-meeting-alt08:14
*** ricolin has joined #openstack-meeting-alt08:16
*** yamamoto has joined #openstack-meeting-alt08:17
*** yamamoto has quit IRC08:17
*** yamamoto has joined #openstack-meeting-alt08:18
*** r-mibu has joined #openstack-meeting-alt08:20
*** ltomasbo|away is now known as ltomasbo08:25
*** lpetrut has joined #openstack-meeting-alt08:35
*** liuyulong_ is now known as liuyulong08:37
*** jpena|away is now known as jpena08:39
*** hughhalf has quit IRC08:46
*** hughhalf has joined #openstack-meeting-alt08:47
*** ijw has quit IRC08:48
*** fzdarsky|afk has joined #openstack-meeting-alt08:48
*** mfedosin has joined #openstack-meeting-alt08:50
*** jpena is now known as jpena|away08:52
*** lpetrut has quit IRC08:56
*** itamaro has joined #openstack-meeting-alt08:57
*** radeks has joined #openstack-meeting-alt08:59
*** radeksmg has joined #openstack-meeting-alt08:59
*** jpena|away is now known as jpena08:59
*** bogdando has joined #openstack-meeting-alt09:01
*** sshnaidm|off is now known as sshnaidm09:02
*** rossella_s has joined #openstack-meeting-alt09:03
*** rossella_s has quit IRC09:04
*** radeks has quit IRC09:05
*** radeksmg has quit IRC09:05
*** rossella_s has joined #openstack-meeting-alt09:05
*** radeks has joined #openstack-meeting-alt09:05
*** radeks has quit IRC09:05
*** MarkBaker has joined #openstack-meeting-alt09:08
*** gongysh has joined #openstack-meeting-alt09:10
*** acabot has joined #openstack-meeting-alt09:16
*** shu-mutou is now known as shu-mutou-AWAY09:23
*** rfolco has joined #openstack-meeting-alt09:27
*** mickeys has joined #openstack-meeting-alt09:30
*** neiljerram has joined #openstack-meeting-alt09:31
*** derekh has joined #openstack-meeting-alt09:32
*** eliqiao has quit IRC09:37
*** eliqiao has joined #openstack-meeting-alt09:40
*** eliqiao has quit IRC09:40
*** panda|off is now known as panda09:44
*** neiljerram has quit IRC09:49
*** lpetrut has joined #openstack-meeting-alt09:57
*** mickeys has quit IRC09:58
*** amotoki has quit IRC09:59
*** bogdando has quit IRC10:00
*** amotoki has joined #openstack-meeting-alt10:01
*** tonanhngo has joined #openstack-meeting-alt10:03
*** nadya has quit IRC10:03
*** tonanhngo has quit IRC10:05
*** tovin07 has quit IRC10:06
*** sankarshan has joined #openstack-meeting-alt10:08
*** neiljerram has joined #openstack-meeting-alt10:12
*** dims_ has quit IRC10:16
*** rossella_s has quit IRC10:17
*** sdake has joined #openstack-meeting-alt10:18
*** rossella_s has joined #openstack-meeting-alt10:19
*** dims has joined #openstack-meeting-alt10:23
*** salv-orl_ has quit IRC10:24
*** salv-orlando has joined #openstack-meeting-alt10:25
*** karthiks has joined #openstack-meeting-alt10:27
*** ralonsoh_ has joined #openstack-meeting-alt10:30
*** ralonsoh_ has quit IRC10:32
*** ralonsoh_ has joined #openstack-meeting-alt10:32
*** ralonsoh has quit IRC10:33
*** dimtruck is now known as zz_dimtruck10:42
*** tuanluong has quit IRC10:49
*** rossella_s has quit IRC10:53
*** rossella_s has joined #openstack-meeting-alt10:53
*** ricolin has quit IRC10:54
*** nadya has joined #openstack-meeting-alt10:54
*** sambetts|afk is now known as sambetts10:58
*** dalgaaf has quit IRC10:58
*** ccamacho has quit IRC10:59
*** dalgaaf has joined #openstack-meeting-alt11:01
*** ccamacho has joined #openstack-meeting-alt11:02
*** hughhalf has quit IRC11:16
*** hughhalf has joined #openstack-meeting-alt11:18
*** sdague has joined #openstack-meeting-alt11:19
*** pgadiya has quit IRC11:31
*** jkilpatr has joined #openstack-meeting-alt11:51
*** gongysh has quit IRC11:52
*** ralonsoh__ has joined #openstack-meeting-alt11:52
*** sridharg has quit IRC11:52
*** ralonsoh_ has quit IRC11:55
*** janki has quit IRC11:56
*** sridharg has joined #openstack-meeting-alt11:57
*** ccamacho has quit IRC12:02
*** ccamacho has joined #openstack-meeting-alt12:03
*** dave-mccowan has joined #openstack-meeting-alt12:04
*** ansmith has joined #openstack-meeting-alt12:17
*** dims has quit IRC12:23
*** tellesnobrega has quit IRC12:24
*** dave-mcc_ has joined #openstack-meeting-alt12:28
*** dave-mccowan has quit IRC12:30
*** sdake_ has joined #openstack-meeting-alt12:36
*** sdake has quit IRC12:39
*** sdake_ is now known as sdake12:48
*** gcb has joined #openstack-meeting-alt12:50
*** caowei has quit IRC12:53
*** michapma_alt has joined #openstack-meeting-alt12:55
*** wiebalck has joined #openstack-meeting-alt12:57
*** gouthamr has joined #openstack-meeting-alt12:58
*** sridhargaddam has joined #openstack-meeting-alt13:00
*** EricGonczer_ has joined #openstack-meeting-alt13:03
*** sridharg has quit IRC13:03
*** dsariel has quit IRC13:04
*** dsariel_ has quit IRC13:04
*** jmckind has joined #openstack-meeting-alt13:04
*** jmckind has quit IRC13:07
*** jmckind has joined #openstack-meeting-alt13:08
*** armax has joined #openstack-meeting-alt13:08
*** bfernando has joined #openstack-meeting-alt13:10
*** ociuhandu has quit IRC13:13
*** tellesnobrega has joined #openstack-meeting-alt13:15
*** dprince has joined #openstack-meeting-alt13:15
*** dsariel has joined #openstack-meeting-alt13:16
*** dsariel_ has joined #openstack-meeting-alt13:18
*** rfolco has quit IRC13:18
*** jaypipes has joined #openstack-meeting-alt13:20
*** dims has joined #openstack-meeting-alt13:20
*** salv-orlando has quit IRC13:29
*** timothyb89_ has joined #openstack-meeting-alt13:29
*** mikal_ has joined #openstack-meeting-alt13:30
*** mikal has quit IRC13:32
*** dolphm has quit IRC13:32
*** hyakuhei has quit IRC13:32
*** timothyb89 has quit IRC13:32
*** kevinbenton has quit IRC13:32
*** dolphm_ has joined #openstack-meeting-alt13:32
*** hyakuhei has joined #openstack-meeting-alt13:32
*** hyakuhei has quit IRC13:32
*** hyakuhei has joined #openstack-meeting-alt13:32
*** hyakuhei has quit IRC13:32
*** hyakuhei has joined #openstack-meeting-alt13:32
*** rfolco has joined #openstack-meeting-alt13:32
*** dolphm_ is now known as dolphm13:33
*** jheroux has joined #openstack-meeting-alt13:34
*** dsariel has quit IRC13:34
*** kevinbenton has joined #openstack-meeting-alt13:35
*** dsariel_ has quit IRC13:35
*** yamamoto has quit IRC13:39
*** diga has joined #openstack-meeting-alt13:41
*** yamamoto has joined #openstack-meeting-alt13:41
*** ccamacho is now known as ccamacho|lunch13:42
*** dprince has quit IRC13:42
*** dustins has joined #openstack-meeting-alt13:43
*** dims_ has joined #openstack-meeting-alt13:43
*** dims has quit IRC13:45
*** yamamoto has quit IRC13:47
*** PagliaccisCloud has joined #openstack-meeting-alt13:48
*** nadya has quit IRC13:48
*** wiebalck has quit IRC13:48
*** salv-orlando has joined #openstack-meeting-alt13:49
*** mtanino has joined #openstack-meeting-alt13:49
*** jpena is now known as jpena|lunch13:50
*** ociuhandu has joined #openstack-meeting-alt13:51
*** dizquierdo has joined #openstack-meeting-alt13:52
*** ralonsoh__ is now known as ralonsoh13:57
*** ihrachys has joined #openstack-meeting-alt13:57
*** cdent has joined #openstack-meeting-alt13:59
*** amotoki has quit IRC13:59
edleafe#startmeeting nova_scheduler14:00
openstackMeeting started Mon Feb 13 14:00:18 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
*** gongysh has joined #openstack-meeting-alt14:00
cdento/14:00
macsz\o14:00
jrollmorning14:00
edleafeGood UGT morning, all!14:00
jaypipeso/14:01
digao/14:01
*** noslzzp has joined #openstack-meeting-alt14:01
edleafeShould be a rather quick meeting today, as there isn't anything on the agenda!14:02
edleafe:)14:02
edleafe#topic Specs and Reviews14:02
*** openstack changes topic to "Specs and Reviews (Meeting topic: nova_scheduler)"14:02
edleafeEven though they weren't on the agenda, I wanted to point out a few:14:03
* bauzas waves14:03
edleafeTraits spec:14:03
edleafe#link https://review.openstack.org/#/c/345138/14:03
edleafeTraits POC series, starting with:14:03
edleafe#link https://review.openstack.org/#/c/377381/14:03
*** dave-mcc_ has quit IRC14:03
edleafeNow that Pike is open, let's get some focus on these14:03
edleafeThere is also the Nested Resource Providers series, starting with:14:04
edleafe#link https://review.openstack.org/#/c/415920/14:04
edleafeI've been nursing those through several rebases, but more eyeballs on them as far as code correctness would be appreciated14:04
edleafeAnyone have any other specs/reviews to mention?14:05
*** beagles is now known as beagles-mtg14:05
*** tonanhngo has joined #openstack-meeting-alt14:05
jaypipesedleafe: dansmith and I had some chats about that on Friday. Likely that will need to be refactored (back to what it kind of looked like originally)14:05
cdent /o\14:05
edleafejaypipes: right. And without cries of YAGNI, please make sure that it works with a separate, independent placement service14:06
*** tonanhngo has quit IRC14:06
jaypipesedleafe: ?14:07
edleafeHaving Nova use classes defined in Placement can be tricky14:07
*** dave-mcc_ has joined #openstack-meeting-alt14:07
*** noslzzp has quit IRC14:07
edleafeE.g., Nova doesn't import Neutron classes to work with that serviec14:07
edleafeservice14:08
jaypipesedleafe: right, I don't think anyone disagrees with you on that? :)14:08
*** noslzzp has joined #openstack-meeting-alt14:08
*** ozamiatin has joined #openstack-meeting-alt14:08
*** amotoki has joined #openstack-meeting-alt14:08
edleafeI got the impression from dansmith that ResourceProvider classes and such belonged at the libvirt layer14:09
jaypipesedleafe: no. ProviderTree is not a ResourceProvider class.14:09
jrollwhat I got out of that conversation is that the virt layer should return a dict of resources, e.g. {VCPUS: 1, MEMORY_MB: 2, CUSTOM_FOO: 50}14:10
jaypipesedleafe: it's not a nova.objects object.14:10
*** dprince has joined #openstack-meeting-alt14:10
jroll(but maybe I'm on the wrong conversation)14:10
edleafejroll: I don't have a problem with a dict14:10
*** tellesnobrega has quit IRC14:11
jaypipesjroll: yes, that's the right conversation. The issue is that for nested providers, that dict isn't really something that can store the hierarchy of providers and inventory. So the design question is what thing (scheduler report client? resource tracker? something else?) should be responsible for building that hierarchy of information.14:11
jrolljaypipes: got it14:12
jrolljaypipes: I'm not up to speed enough on nested stuff to comment :)14:12
jaypipesjroll: edleafe argued on the first patch in that series that the virt layer should *not* be the thing that builds that tree of information. so I instead made the scheduler report client responsible for building that.14:12
jaypipesjroll: no worries :)14:13
edleafejaypipes: my concern was having the virt layer use Inventory objects and such14:13
jaypipesjroll: and dansmith was saying "why not have the virt layer build this information and return it to the resource tracker?"14:13
jaypipesjroll: which is what I had in the first patch in that series ;)14:13
jrolljaypipes: right, so I gathered the right idea, just not the how :)14:14
edleafeIOW, the virt layer should know what it has and report it. It shouldn't know how the placement service represents it internally14:14
jaypipesin any case, this is something that we should have a session about next week I think?14:14
edleafeby all means!14:14
jrollyep14:14
jaypipes:)14:14
jrollmakes sense14:14
*** EricGonczer_ has quit IRC14:14
* jaypipes getting way too hungry for this conversation right now :)14:15
edleafeAny other specs/reviews?14:15
jaypipesedleafe: well, the ironic inventory one :)14:15
* edleafe needs pot of coffee #2 right now14:15
jaypipesedleafe: needs some TLC today.14:15
edleafejaypipes: just rebasing TLC, or more?14:15
*** pradk has joined #openstack-meeting-alt14:15
jrolljaypipes: so, the ironic patch is the one that started the layering conversation, right?14:16
jaypipesedleafe: rebasing and reviewing.14:16
jrollIOW doesn't that depend a bit on the outcome of the previous conversation? or would you rather refactor later?14:17
edleafejaypipes: you need me to rebase, or do you have it?14:17
edleafejroll: I think it was the whole NUMA mess14:17
jrolledleafe: iirc, dan's argument was that if we fix the layering thing, we don't need all the "if ironic" junk in the RT layer14:18
jaypipesjroll: yes, it started the conversation. but dansmith's comments about layering in that patch led to the nested resource providers series being used as an example of what he might like to see instead..14:18
edleafejroll: ah, I see what you mean. Yes, that's true14:18
* jroll isn't sure if we want to block on that or not, just wanted to point it out14:18
*** zz_dimtruck is now known as dimtruck14:18
edleafejroll: well, the idea was that the 'if ironinc' crap was a stopgap for Ocata, but now that that ship has sailed...14:19
jaypipesheh, yeah.14:19
jroll:)14:20
edleafeLooks like we won't be bored next week :)14:20
edleafeLet's move on14:20
edleafe#topic Bugs14:20
*** openstack changes topic to "Bugs (Meeting topic: nova_scheduler)"14:20
jaypipesone thing I definitely do want to keep around from the Ironic inventory patch is the addition of that brand new shiny functional test for the resource tracker. :)14:20
edleafeAny new bugs to discuss?14:20
jaypipesglorious: https://review.openstack.org/#/c/404472/34/nova/tests/functional/compute/test_resource_tracker.py14:21
johnthetubaguyon the layering, is the long term plan that the resource tracker dies / only cares about keeping in sync with placement, but we have moved on for now14:21
*** cdelatte has joined #openstack-meeting-alt14:21
johnthetubaguyjaypipes: thats actually quite beautiful to see14:21
jaypipesjohnthetubaguy: I've gone through quite a few design iterations on the layering stuff :) there's good things and bad things for each approach. basically, just need to hammer this out in a session in ATL I think :(14:22
edleafejohnthetubaguy and jaypipes: that leads us to the actions from last week...14:22
edleafe#topic Open discussion14:22
*** openstack changes topic to "Open discussion (Meeting topic: nova_scheduler)"14:22
johnthetubaguyjaypipes: yeah, it feels that way14:22
jaypipesI can write up a quick email saying "here are the options". let's choose one.14:22
johnthetubaguyjaypipes: that sounds great to me14:22
jrolljaypipes: ++14:22
jaypipeskk14:22
cdentprepemail++14:22
edleafeLast week cdent and I had the action assigned to outline the functional tests that we feel are needed, so that others can respond and begin writing them14:23
jaypipesooh, look a see-dent.14:23
johnthetubaguyhaving slept on it before the PTG, will be no bad thing14:23
*** cknight has joined #openstack-meeting-alt14:23
edleafeWe created an etherpad:14:23
edleafe#link https://etherpad.openstack.org/p/nova-placement-functional14:23
*** ccamacho|lunch is now known as ccamacho14:23
jrolljaypipes: that test is amaze14:24
edleafeIt would be great to take that test and use it as the basis for lots more14:24
edleafeThe other action was for bauzas, diga and macsz to begin defining the goals for Pike14:25
edleafeIs there something for that?14:25
digaedleafe: we drafted some on etherpad14:25
diga#link- https://etherpad.openstack.org/p/nova-scheduler-pike14:25
edleafediga: link?14:25
edleafediga: beat me to it :)14:26
digaedleafe: :)14:26
edleafeSo these Pike goals are definitely something we should discuss at PTG14:26
digaedleafe: Yeah, we should14:27
digaBy the way, I am able to attend PTG14:27
edleafeA quick read of that page doesn't show too many concrete goals - more like brainstorming14:27
edleafediga: that's great!14:27
digaedleafe: sorry I am not able to attend PTG :( because travel support issue14:28
digatype mistake14:28
edleafeCan you guys maybe sum up the goals that you think are a) necessary to get done in Pike, and b) would be great but not critical for Pike14:28
edleafediga: :(14:29
digaedleafe: sure14:29
*** gongysh has quit IRC14:29
edleafediga: thanks14:30
digaedleafe: is there way to attend remotely for 1 session at least14:30
*** wiebalck has joined #openstack-meeting-alt14:30
edleafediga: usually it's tough, and with this being the first PTG, who knows?14:30
digaedleafe: okay, NP!14:30
*** beagles-mtg has quit IRC14:30
edleafediga: I also think ttx said that most rooms won't even have projectors14:30
digaedleafe: ohh.. i see14:31
edleafeIf anyone has opinions on what we should set as our Pike goals, please add your thoughts to that etherpad14:31
edleafeSo... anything else on your minds?14:32
* edleafe is ready to go make more coffee14:33
cdentI like coffee14:33
edleafeI should mention that we won't be meeting next week, due to PTG14:33
edleafeNext meeting in 2 weeks14:33
jrollwoo14:34
*** tonytan4ever has joined #openstack-meeting-alt14:34
edleafeOK, thanks for coming. Hope to see many of you in Atlanta!14:34
digaack14:34
edleafe#endmeeting14:34
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:34
openstackMeeting ended Mon Feb 13 14:34:46 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:34
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_scheduler/2017/nova_scheduler.2017-02-13-14.00.html14:34
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_scheduler/2017/nova_scheduler.2017-02-13-14.00.txt14:34
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_scheduler/2017/nova_scheduler.2017-02-13-14.00.log.html14:34
digabye14:34
jrollthanks edleafe14:35
*** amotoki has quit IRC14:37
*** dsariel has joined #openstack-meeting-alt14:39
*** Guest69121 has joined #openstack-meeting-alt14:39
*** dizquierdo has quit IRC14:40
*** sridhargaddam has quit IRC14:40
*** cdent_ has joined #openstack-meeting-alt14:44
*** fnaval has quit IRC14:44
*** yamamoto has joined #openstack-meeting-alt14:44
*** fnaval has joined #openstack-meeting-alt14:44
*** cdent has quit IRC14:45
*** cdent_ is now known as cdent14:45
*** vgnbkr has quit IRC14:45
*** HenryG has quit IRC14:46
*** vgnbkr has joined #openstack-meeting-alt14:48
*** fnaval has quit IRC14:48
*** yamamoto has quit IRC14:49
*** HenryG has joined #openstack-meeting-alt14:49
*** skramaja is now known as skramaja_afk14:51
*** jpena|lunch is now known as jpena14:52
*** nadya has joined #openstack-meeting-alt14:52
*** rossella_s has quit IRC14:53
*** baoli has joined #openstack-meeting-alt14:53
*** rossella_s has joined #openstack-meeting-alt14:53
*** tremble has left #openstack-meeting-alt14:53
*** zerick_ is now known as zerick14:56
*** jcoufal has joined #openstack-meeting-alt14:56
*** myoung|pto is now known as myoung14:56
*** korzen has joined #openstack-meeting-alt14:57
*** dave-mcc_ has quit IRC14:57
*** mfedosin has quit IRC14:59
*** anilvenkata has quit IRC15:00
*** jose-phillips has joined #openstack-meeting-alt15:00
*** mfedosin has joined #openstack-meeting-alt15:00
ihrachys#startmeeting neutron_upgrades15:00
openstackMeeting started Mon Feb 13 15:00:49 2017 UTC and is due to finish in 60 minutes.  The chair is ihrachys. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: neutron_upgrades)"15:00
openstackThe meeting name has been set to 'neutron_upgrades'15:00
korzenhello15:01
sindhuhi15:01
ihrachys#topic Announcements15:02
*** openstack changes topic to "Announcements (Meeting topic: neutron_upgrades)"15:02
ihrachys1. stable/ocata is created, master is open for merges15:02
*** tellesnobrega has joined #openstack-meeting-alt15:02
*** electrocucaracha has joined #openstack-meeting-alt15:02
ihrachys2. PTG is next week, the final agenda is currently in produce at https://etherpad.openstack.org/p/neutron-ptg-pike-final15:03
electrocucarachao/15:03
ihrachysthere is a section for upgrades at line 2715:03
*** cdent has left #openstack-meeting-alt15:03
ihrachyskevinbenton was going to check with the foundation about room setup, to see if we may/want to split discussions, or we will need to do everything serialized15:03
ihrachysI assume Kevin will update start of this week15:04
electrocucarachaihrachys: I added a couple of things in the korzen 's etherpad15:04
ihrachysyeah, I am meant to sync that back into the -final15:04
*** fnaval has joined #openstack-meeting-alt15:05
ihrachys#action ihrachys to sync -upgrades PTG etherpad back into -final15:05
ihrachys#topic Partial Multinode Grenade15:06
*** openstack changes topic to "Partial Multinode Grenade (Meeting topic: neutron_upgrades)"15:06
sindhuihrachys: Is there anyway people who are not attending PTG can participate remotely?15:06
*** dimtruck is now known as zz_dimtruck15:06
ihrachys#undo15:06
openstackRemoving item from minutes: #topic Partial Multinode Grenade15:06
ihrachyssindhu: practice shows not really. you may talk to PTL or organizers about your options though.15:07
manjeetso/15:07
sindhuihrachys: Okay, thanks :)15:07
ihrachys#topic Partial Multinode Grenade15:08
*** openstack changes topic to "Partial Multinode Grenade (Meeting topic: neutron_upgrades)"15:08
*** beekneemech is now known as bnemec15:08
ihrachyskorzen: any updates about your partial setup of newton vs. ocata on k8s?15:08
*** cgoncalves has quit IRC15:09
korzenihrachys, sad news fuel-ccp was not playing nice with me :( I was fixing new failures in the setup but I was not able to test the whole use case :(15:09
korzenI should be able to get you the info bu tomorrow15:10
korzenby*15:10
*** cgoncalves has joined #openstack-meeting-alt15:10
ihrachyshuh not up to the hype? ;)15:10
ihrachysok cool, thanks for pushing15:10
*** anilvenkata has joined #openstack-meeting-alt15:10
electrocucarachaihrachys: our goal is add support to rolling upgrades or zero-downtime? we were discussing the other day that the current implementation of grenade restart all the services which is not the desired way in zero-downtime15:10
korzenk8s is not up to the stability level :P15:10
ihrachyselectrocucaracha: it's both rolling upgrades and zero API downtime. we have some form of rolling upgrades.15:11
*** salv-orlando has quit IRC15:11
ihrachysrolling upgrade only means you can upgrade services one by one15:11
ihrachysinstead of bringing down the whole cluster15:11
*** dave-mccowan has joined #openstack-meeting-alt15:11
ihrachyswhich we have (you can upgrade server without agents)15:11
*** salv-orlando has joined #openstack-meeting-alt15:11
*** Guest69121 is now known as beagles15:11
electrocucarachabut we have to upgrade all the server nodes at the same time right?15:12
*** jcoufal_ has joined #openstack-meeting-alt15:12
manjeetsupgrading one instance of each service at once while keeping others running15:12
*** egallen has joined #openstack-meeting-alt15:12
ihrachysas far as grenade partial linuxbridge job, it's at this point at the same failure rate level as tempest one for the backend, and it's hard to understand if it's specific to grenade, or a general oom-killer/libvirt crashing thing that lingers our gates15:12
ihrachyselectrocucaracha: yes, we have to, but that's not part of the definition of rolling upgrades as documented by https://governance.openstack.org/tc/reference/tags/assert_supports-rolling-upgrade.html15:13
ihrachys"This does not require complete elimination of downtime during upgrades, but rather reducing the scope from “all services” to “some services at a time.” In other words, “restarting all API services together” is a reasonable restriction."15:14
electrocucarachaihrachys: gotcha, thanks15:15
* manjeets thought something like running multiple copies of neutron-server and updating one at a time while running other on old version 15:15
*** jcoufal has quit IRC15:15
ihrachysmanjeets: that's what https://governance.openstack.org/tc/reference/tags/assert_supports-zero-downtime-upgrade.html#tag-assert-supports-zero-downtime-upgrade is for15:15
ihrachys"this tag requires services to completely eliminate API downtime of the control plane during the upgrade. In other words, requiring operators to “restart all API services together” is not reasonable under this tag."15:16
ihrachyswhile we are at it, there is another one on top of it all, https://governance.openstack.org/tc/reference/tags/assert_supports-zero-impact-upgrade.html#tag-assert-supports-zero-impact-upgrade15:16
*** jose-phi_ has joined #openstack-meeting-alt15:16
ihrachysthat last one forbids even performance degradation during upgrade15:16
*** jose-phillips has quit IRC15:16
electrocucarachawhich nobody has achieved, isn't it?15:17
manjeetsnot even first ?15:17
ihrachysI think even zero-api-downtime is no one's achievement15:17
ihrachysbecause it assumes CI setup15:18
ihrachysand that I believe is waiting for dolphm to clear the gate framework for projects to adopt15:18
electrocucarachawell, afaik nova is working on that15:18
ihrachysspeaking of which, dolphm do you need any help with defining the framework? where is the work tracked?15:18
korzennova is working on CI, but are they changing the nova-conductor approach to support running different version of conductor at the same time?15:21
*** saneax is now known as saneax-_-|AFK15:21
ihrachysseems like we don't have dolphm around15:21
korzencurrently, nova is requiring to upgrade all of your conductors in the same time15:22
electrocucarachakorzen: even when they have OVO already implemented?15:22
korzenelectrocucaracha, their ovo approach is also different from what we should cosider15:23
korzenconsinder*15:23
korzentheir ovo approach is online data migration while save/get but they are also removing old data, marking it with null15:24
electrocucarachaihrachys: dolphm is not in his desk, not sure if he is going to work remotely15:24
ihrachyskorzen: how does nullifying work with old services reading from there?15:24
korzenihrachys, it doesn't15:24
*** zz_dimtruck is now known as dimtruck15:25
korzenthe assumption is that you are using only few format15:25
ihrachys*new you mean?15:25
korzenyea ;)15:25
ihrachysformat of what?15:25
korzenthe new place of data or new format15:26
korzenformat of data15:26
korzenblob version int/bool type15:26
korzenblob instead of int*15:26
korzenI'm working on some draft how we should consider online upgrades, I will publish it tomorrow15:27
ihrachysoh so you upgrade conductors and they all know the new format?15:27
korzenyes15:27
ihrachysmeh15:27
ihrachysthat's hitting the can :)15:27
ihrachysdown the road15:28
*** Akis_ has joined #openstack-meeting-alt15:28
ihrachysok let's move on to15:28
ihrachys#topic Object implementation15:28
*** openstack changes topic to "Object implementation (Meeting topic: neutron_upgrades)"15:28
ihrachyskorzen: you mentioned you woll work on a write-up15:28
ihrachysI wonder how electrocucaracha's https://review.openstack.org/#/c/432494/1/neutron/db/migration/alembic_migrations/versions/newton/online/__init__.py fits in15:28
korzenyes, electrocucaracha great stuff15:29
electrocucarachaI just tried to use the nova approach in our plans15:29
korzenthis is one part of the mechanism, the CLI tool15:29
korzenthe second part is how to manage old/new format in OVO15:29
*** dave-mccowan has quit IRC15:29
ihrachysyeah, I was only thinking that from code organization perspective, it would make sense to store the actual rules in object modules themselves.15:30
ihrachysand another consideration would be, whether we can reuse code between lazy migration (on object update) and this forced online migration15:31
*** Akis__ has quit IRC15:31
korzenin nova and cinder it is done in sql15:32
*** EricGonczer_ has joined #openstack-meeting-alt15:32
korzenone of the cinder example is doing the online data migration without OVO15:32
korzenthey are providing the CLI to do it, and some simple code in fetching method to port old data to new format15:33
*** dave-mccowan has joined #openstack-meeting-alt15:33
korzenin that simple example, they decided to add prefix to some ID15:33
ihrachysI guess we can look at code reuse between OVO update path and new migration path later, and stick to direct sql for now. as for code organization, I would think that maybe objects would register online migration functions through let's say stevedore, and then the CLI tool will consume those. that would allow external subprojects to plug into the system.15:35
korzenihrachys, that is also a good idea15:35
ihrachyselectrocucaracha: thanks for working on the patch, cool stuff15:36
*** Akis__ has joined #openstack-meeting-alt15:36
electrocucarachaihrachys: no problem, feel free to modify or completely change it15:36
ihrachyskorzen: what's the state of port binding OVO integration (https://review.openstack.org/#/c/407868/)? I see it passed most jobs, so it ready?15:37
korzenyes, but it still has some problems with tempest15:37
korzenand grenade multinode dvr15:38
korzenI'm not sure where is the issue there15:38
korzenthe whole problem seems to be with stale data15:38
korzenwe are updating the port binding in OVO, but port db data has stale info about the binding15:39
korzenI'm thinking if we should first work on port OVO adoption to fully address the issues with port binding15:39
*** Akis_ has quit IRC15:39
korzenso it is not so trivial as it may looked like15:40
ihrachysI see15:40
ihrachysok one other patch that I wanted to discuss is15:43
ihrachyshttps://review.openstack.org/#/c/41915215:43
ihrachysit adds support for pattern matching for get_* arguments15:43
ihrachysI am specifically looking at https://review.openstack.org/#/c/419152/8/neutron/objects/utils.py@3415:43
ihrachysand I am not sure if I get intent right15:43
ihrachysI thought that if we would expose a general pattern matching (%XXX%), then we could as well match against XXX% as well as %XXX?15:44
*** timothyb89_ is now known as timothyb8915:45
ihrachysI mean, exposing all three would make sense as long as we stick to the existing code in https://review.openstack.org/#/c/419152/8/neutron/db/common_db_mixin.py15:45
electrocucarachabut that only applies for strings :S15:45
ihrachysbut sqlalchemy exposes .like operator too, so why not sticking to it for all cases?15:46
ihrachystonytan4ever: ^15:46
ihrachyselectrocucaracha: elaborate15:46
*** jmckind_ has joined #openstack-meeting-alt15:47
tonytan4everihrachys: sqlalchemy supports pattern matching (%XXX%), XXX%  and %XXX as different query API though.15:47
electrocucarachawell, basically the idea that tonytan4ever  is doing is the implementation of more filters, in this case he is only covering the scenario for strings15:47
electrocucarachabut I wondering if we have something for filters of dates or strings15:48
*** jmckind has quit IRC15:49
electrocucarachaI've seen patches which also uses those special filters and they ended in classmethod15:49
ihrachystonytan4ever: but we have .like too?15:49
ihrachyssee e.g. http://docs.sqlalchemy.org/en/latest/core/sqlelement.html?highlight=like#sqlalchemy.sql.expression.ColumnElement.like15:50
*** anilvenkata has quit IRC15:50
tonytan4everihrachys:  .like could work, but it still expose the sql details to the user though. e.g:  you need to say .like(%foobar%)15:51
*** marst has quit IRC15:51
tonytan4everWhere if you use contains, you just need to say .contains("foobar")15:51
tonytan4everAlso ".like" covers the case for startswith and endswith, True that. startswith and endswith can provide short hand for some use case like:15:52
tonytan4everget all agents name starting with "zoneA-agent" though.15:53
*** salv-orlando has quit IRC15:54
ihrachysok I see where you come from15:54
ihrachysI don't particularly hate the %XXX% notation but I guess you can argue it suggests sql15:55
ihrachysok I will recheck the patch as it stands now15:55
tonytan4everThanks.15:56
ihrachysok there is little time, so a quick thing...15:56
*** jose-phi_ has quit IRC15:56
*** kgiusti has joined #openstack-meeting-alt15:56
ihrachys#topic Open discussion15:56
*** openstack changes topic to "Open discussion (Meeting topic: neutron_upgrades)"15:56
electrocucarachaihrachys: I added the topic of db prune rows for the ptg15:57
ihrachysI raised the point of memory consumption going nuts in gate before; folks are still looking at it, some data is collected, but we struggle to get it for spawned workers that are of more interest15:57
ihrachyselectrocucaracha: thanks15:58
ihrachysso re: memory, tl;dr is we are still waiting for results that we could work with15:58
korzenok15:58
ihrachysso far we saw lots of sqlalchemy and oslo.messaging objects15:58
* electrocucaracha is still waiting for johndperkins patch15:59
ihrachyselectrocucaracha: which exactly?15:59
*** yamahata has joined #openstack-meeting-alt15:59
electrocucarachaihrachys: he has something in mind that can help to reduce memory, more likely he has been busy doing other stuff16:00
ihrachysok we need to give the room back to openstack16:00
electrocucarachasure16:00
ihrachyslet's follow up in the team channel16:00
ihrachys#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
*** rloo has joined #openstack-meeting-alt16:00
openstackMeeting ended Mon Feb 13 16:00:26 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_upgrades/2017/neutron_upgrades.2017-02-13-15.00.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_upgrades/2017/neutron_upgrades.2017-02-13-15.00.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_upgrades/2017/neutron_upgrades.2017-02-13-15.00.log.html16:00
gcb#startmeeting  oslo16:00
openstackMeeting started Mon Feb 13 16:00:39 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
openstackThe meeting name has been set to 'oslo'16:00
johnsomo/16:00
electrocucarachahowdy16:00
*** jungleboyj has joined #openstack-meeting-alt16:00
gcbcourtesy ping for amotoki, amrith, bknudson, bnemec, dansmith, dhellmann, dims,dougwig, e0ne, electrocucaracha, flaper87, garyk, gcb, GheRivero,haypo, jd__, jecarey, johnsom, jungleboyj, kgiusti, kragniz,lifeless, lxsli, Nakato, ozamiatin, rbradfor, redrobot, rloo,rpodolyaka, sergmelikyan, sileht, spamaps, sreshetnyak, sreshetnyak, stevemar,therve, thinrichs, toabctl, viktors, zhiyan, zzzeek16:00
jungleboyjo/16:01
rpodolyakao/16:01
ozamiatino/16:01
jungleboyjHow was that for timing?16:01
rlooo/16:01
toabctlhi16:01
kgiustio/16:01
bknudsonhi16:01
gcbhello guys, welcome back to oslo :-)16:01
gcb#topic Red flags for/from liaisons16:01
*** openstack changes topic to "Red flags for/from liaisons (Meeting topic: oslo)"16:01
*** marst has joined #openstack-meeting-alt16:01
johnsomNothing from team Octavia16:02
jungleboyjgcb, No redflag but I do have a spec I should make you aware of.  Hold on.16:02
rloonothing i'm aware of from ironic16:02
gcbnova breaks due to remove config option verbose , and fix in   https://review.openstack.org/432253, please help review16:02
jungleboyjgcb, So we have this proposed for Cinder:  https://review.openstack.org/43249816:02
electrocucarachanothing from Neutron16:03
*** beslemon has joined #openstack-meeting-alt16:03
jungleboyjLooks like a good thing but it will have impacts on oslo.db16:03
rpodolyakajungleboyj: the only thing I saw so far was adding a new option ,that's not used anywhere16:03
gcbjungleboyj,  I think  oslo.db core reviewers have discussed this in ML16:03
rpodolyakato specify the mysql engine to be used16:04
rpodolyaka*storage16:04
gcb#link https://review.openstack.org/#/c/427970/16:04
*** egallen has quit IRC16:04
rpodolyakaI've starred the Cinder spec, will take a look16:04
*** Leom has joined #openstack-meeting-alt16:04
gcbSee http://lists.openstack.org/pipermail/openstack-dev/2017-February/111418.html for a bit more context16:04
jungleboyjSo, do you think this is something that oslo will support?16:04
rpodolyakawell, at this point I don't think this will need any specific support from oslo.db16:05
rpodolyakaexcept for adding of that new config option16:05
jungleboyjOk, we were hoping there would be a way to abstract some of the details into oslo.db to reduce the impact on Cinder.16:05
*** jcoufal_ has quit IRC16:05
rpodolyakabased on the discussion in the ML the consuming projects will need to update their DB schemas16:05
jungleboyjGuess we will need to discuss that further in the spec.16:05
*** Leo_ has quit IRC16:06
gcbzzzeek has some concern about MySQL cluster , and discussed in the ML16:06
jungleboyjOk, I will take a look at the ML thread and get caught up.16:06
*** harlowja_at_home has joined #openstack-meeting-alt16:06
*** jcoufal has joined #openstack-meeting-alt16:06
harlowja_at_home\o16:06
gcbhi harlowja_at_home16:06
jungleboyjThanks for the pointers.16:06
gcbjungleboyj, np16:07
harlowja_at_homegcb hi mr.newptl :)16:07
*** rarcea has quit IRC16:07
*** rarcea has joined #openstack-meeting-alt16:07
gcbharlowja,_at_home: you'r still my boss lol16:07
harlowja_at_homelol16:07
*** korzen has quit IRC16:08
gcbAny Red flags ?16:08
gcbplease help look at https://review.openstack.org/#/c/432253/ and then let's move on16:08
gcb#topic Releases for Pike16:09
*** openstack changes topic to "Releases for Pike (Meeting topic: oslo)"16:09
gcbjust talked with release team:  " master: we should be ready to open up for new master releases this week; I want to coordinate with the requirements team before we do     stable/ocata:  those will be held until after the ocata final, unless there is a critical bug"16:10
gcbso we don't plan to release this week until we are informed by release team16:10
harlowja_at_homegcb i can give u a demo of how to use my little release program (if u haven't tried it)16:11
harlowja_at_homejust remind me16:11
harlowja_at_homebasically https://github.com/openstack/releases/blob/master/openstack_releases/cmds/interactive_release.py16:11
*** wiebalck has quit IRC16:12
gcbharlowja_at_home, I didn't try it16:12
harlowja_at_homegcb it helps do the many releases :)16:12
harlowja_at_homeless manual editing of yaml :)16:12
gcbharlowja_at_home: cool , I did some by manual, will try and reach to you if I have questions16:13
harlowja_at_homek16:13
gcb#topic Daily work16:13
*** openstack changes topic to "Daily work (Meeting topic: oslo)"16:13
*** spzala has joined #openstack-meeting-alt16:13
gcb#link https://etherpad.openstack.org/p/oslo-pike-tracking16:13
*** ociuhandu has quit IRC16:14
gcbplease update information in section '1. Libraries and focus' if you would like to help16:14
*** xin9972 has joined #openstack-meeting-alt16:14
gcbabout bug triage: It seems a lot of open bugs, need volunteer to help triage16:16
ozamiatingcb, kgiusti: If this is appropriate topic to point on review please take a look  https://review.openstack.org/#/c/429639/16:16
kgiustiozamiatin: will do16:16
ozamiatinkgiusti: thanks!16:16
gcbwe have bug smash in PTG to help reduce number of bugs.16:17
gcbozamiatin, ack , will16:17
harlowja_at_homegcb i can do some triage this week16:17
harlowja_at_homeso count me in16:17
ozamiatinthanks gcb16:17
gcbharlowja_at_home: thanks16:17
gcbharlowja, nice guy16:17
harlowja_at_homeha16:18
harlowja_at_homesometimes :-P16:18
*** rcernin has quit IRC16:19
*** dims_ has quit IRC16:19
gcbwe discussed some about memory footprint growth in last weekly meeting16:19
gcbI didn't follow too much, only know we have try add some trace code to figure out the root cause16:20
harlowja_at_homeah16:20
gcbmtreinish: https://review.openstack.org/#/c/429844/ https://review.openstack.org/#/c/428220/16:20
harlowja_at_homeya, mtreinish and i are still slowly poking at the memory stuff16:20
gcbharlowja_at_home: you should know more details :-)16:20
harlowja_at_homeya, its a WIP as we try to figure out how to get the best data16:21
harlowja_at_homeWIP/research16:21
*** armax has quit IRC16:21
gcbharlowja_at_home, you prove you're a nice guy again , thanks16:22
gcb#topic Open discussion16:22
*** openstack changes topic to "Open discussion (Meeting topic: oslo)"16:22
*** iyamahat has joined #openstack-meeting-alt16:23
gcbI would raise that remove mox :  http://lists.openstack.org/pipermail/openstack-dev/2017-February/111774.html16:23
harlowja_at_homehttps://review.openstack.org/#/c/432253/ is funny :-P16:23
harlowja_at_homedamn, that option will never go away :-P16:24
*** dims has joined #openstack-meeting-alt16:24
gcbharlowja_at_home:  agree, will try my best to remove it in this cycle16:25
gcbalso need remove mox/mox3, then we can retire mox316:25
harlowja_at_homeya16:26
harlowja_at_homehopefully that's not super-hard16:26
*** diablo_rojo has joined #openstack-meeting-alt16:26
*** spzala has quit IRC16:26
*** snackewm has joined #openstack-meeting-alt16:26
gcbI think we'll skip next weekly meeting Feb 20 due to the PTG16:27
gcb#link https://etherpad.openstack.org/p/oslo-ptg-pike16:27
*** knangia has joined #openstack-meeting-alt16:27
jungleboyjWow, that is next week.16:27
gcbyeah, very close now16:27
gcbjust added item: Project updates in Boston Summit, need collect updates16:28
*** jcoufal_ has joined #openstack-meeting-alt16:28
gcbyou can find more details at the bottom of the etherpad16:28
* harlowja_at_home reminder i won't be there (family vacation) 16:29
*** beslemon has quit IRC16:29
gcbharlowja_at_home,  have a nice vacation16:30
harlowja_at_homethx :-P16:30
jungleboyjharlowja_at_home, Hope you are going somewhere fun.  :-)  Like Atlanta ... I mean, not like Atlanta.16:30
kgiustiharlowja_at_home: we can still assign you bugs, right?  ;)16:30
*** jcoufal has quit IRC16:30
gcblol16:31
harlowja_at_homekgiusti sureee16:31
harlowja_at_homejungleboyj http://www.revelstokemountainresort.com/16:31
harlowja_at_home^ that's where i'll be16:31
gcbI'm little worried about hosting the meeting and recording meeting minutes, need help from  native speaker :-)16:31
jungleboyjharlowja_at_home, Nice.16:32
*** matrohon has quit IRC16:32
harlowja_at_homegcb feel free to drag me in for native speaker (unless this is at PTG, then count me out)16:32
* kgiusti jealous...16:33
gcbharlowja_at_home: sure thanks16:33
harlowja_at_homekgiusti u can go up to Killington or something :-P16:33
kgiustiharlowja_at_home: can't.  Court order.  I'll explain later...16:34
kgiusti:)16:34
harlowja_at_home:-/16:34
harlowja_at_homelol16:34
*** jcoufal has joined #openstack-meeting-alt16:34
gcbanything others want to raise ?16:35
harlowja_at_homenope16:36
jungleboyjI am good.16:36
harlowja_at_homedo we all get oslo tshirts with the logo on it?16:36
harlowja_at_home*new logo16:36
jungleboyjOooh!  Logo wear!16:37
gcbwhen and where ?16:37
*** jcoufal_ has quit IRC16:37
harlowja_at_homei'm just wondering, not really sure what the foundation  is  going to do with the new  logos16:37
*** rarcea has quit IRC16:37
jungleboyjGiven what they are losing on the hotel at the PTG, probably nothing.16:38
*** rarcea has joined #openstack-meeting-alt16:38
*** rarcea has quit IRC16:38
*** rarcea has joined #openstack-meeting-alt16:39
*** rarcea has quit IRC16:39
*** nadya has quit IRC16:39
*** rarcea has joined #openstack-meeting-alt16:39
gcbShould we have a way to proposal this ?16:39
rloowhat do you mean, 'losing on the hotel'?16:39
harlowja_at_homegcb i'm not sure :)16:39
rloono oslo tshirts for folks not attending ptg harlowja_at_home! (guess that won't incenti-whtever you to go)16:40
harlowja_at_homelol16:40
harlowja_at_home:(16:40
harlowja_at_homebut but but16:40
harlowja_at_homeits not my fault they planned the PTG during the east coasts typical winter vacation :-P16:40
jungleboyjrloo, The unused rooms since so many people are staying at the cheaper Hilton.16:40
rloojungleboyj: oh, you mean openstack was subsidizing those expensive rooms? yikes.16:41
*** mdong has joined #openstack-meeting-alt16:41
*** ociuhandu has joined #openstack-meeting-alt16:41
jungleboyjYes, they have to pay for the unused ones.16:41
harlowja_at_homelol16:41
* rloo thinks that openstack organizers really don't know much about developers16:42
jungleboyjNo comment.16:42
rlooha ha16:42
* rloo wonders how much they are going to have to fork over...16:42
harlowja_at_home1 billion trillion16:43
*** beslemon has joined #openstack-meeting-alt16:47
gcbokay, let's call it a meeting16:47
gcb316:47
gcb216:47
gcb116:47
gcbthanks, everyone16:48
gcb#endmeeting16:48
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:48
openstackMeeting ended Mon Feb 13 16:48:50 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:48
openstackMinutes:        http://eavesdrop.openstack.org/meetings/oslo/2017/oslo.2017-02-13-16.00.html16:48
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/oslo/2017/oslo.2017-02-13-16.00.txt16:48
openstackLog:            http://eavesdrop.openstack.org/meetings/oslo/2017/oslo.2017-02-13-16.00.log.html16:48
*** beslemon_ has joined #openstack-meeting-alt16:49
*** dsariel has quit IRC16:50
jungleboyjThanks!16:50
gcbjungleboyj, :-)16:50
*** dims has quit IRC16:51
*** beslemon has quit IRC16:51
*** saneax-_-|AFK is now known as saneax16:52
*** jcoufal_ has joined #openstack-meeting-alt16:53
*** spzala has joined #openstack-meeting-alt16:54
*** annegentle has joined #openstack-meeting-alt16:54
*** egallen has joined #openstack-meeting-alt16:54
*** rloo has left #openstack-meeting-alt16:54
*** dims has joined #openstack-meeting-alt16:55
*** sdake_ has joined #openstack-meeting-alt16:55
*** electrocucaracha has left #openstack-meeting-alt16:55
*** tesseract-RH has quit IRC16:55
*** jcoufal has quit IRC16:56
*** annegentle has quit IRC16:56
*** annegentle has joined #openstack-meeting-alt16:56
*** harlowja_at_home has quit IRC16:57
*** sdake__ has joined #openstack-meeting-alt16:57
*** ltomasbo is now known as ltomasbo|away16:57
*** sdake has quit IRC16:59
*** sdake_ has quit IRC17:00
*** dims_ has joined #openstack-meeting-alt17:06
*** dims has quit IRC17:07
*** diga has quit IRC17:09
*** jcoufal__ has joined #openstack-meeting-alt17:09
*** jcoufal_ has quit IRC17:11
*** chhavi has joined #openstack-meeting-alt17:13
*** ltomasbo|away is now known as ltomasbo17:15
*** nkrinner is now known as nkrinner_afk17:18
*** nadya has joined #openstack-meeting-alt17:19
*** bnemec has quit IRC17:20
*** panda is now known as panda|bbl17:23
*** bnemec has joined #openstack-meeting-alt17:24
*** ihrachys_ has joined #openstack-meeting-alt17:26
*** ihrachys has quit IRC17:26
*** ltomasbo is now known as ltomasbo|away17:28
*** nadya has quit IRC17:37
*** ashcrack has joined #openstack-meeting-alt17:44
*** baoli has quit IRC17:44
*** baoli has joined #openstack-meeting-alt17:45
*** baoli has quit IRC17:45
*** iyamahat has quit IRC17:45
*** yamahata has quit IRC17:45
*** adrian_otto has joined #openstack-meeting-alt17:48
*** dprince has quit IRC17:49
*** armax has joined #openstack-meeting-alt17:51
*** derekh has quit IRC17:52
*** rarcea has quit IRC17:53
*** rarcea has joined #openstack-meeting-alt17:53
*** strigazi is now known as strigazi_AFK17:54
*** salv-orlando has joined #openstack-meeting-alt17:55
*** ralonsoh has quit IRC17:56
*** david-lyle has joined #openstack-meeting-alt17:58
*** armax has quit IRC17:59
*** armax has joined #openstack-meeting-alt18:00
*** kgiusti has quit IRC18:01
*** spzala has quit IRC18:01
*** armax has quit IRC18:02
*** nadya has joined #openstack-meeting-alt18:03
*** nadya has quit IRC18:04
*** nadya has joined #openstack-meeting-alt18:04
*** iyamahat has joined #openstack-meeting-alt18:05
*** lpetrut has quit IRC18:05
*** Swami has joined #openstack-meeting-alt18:06
*** chhavi has quit IRC18:06
*** hrybacki has quit IRC18:06
*** david-lyle_ has joined #openstack-meeting-alt18:08
*** david-lyle has quit IRC18:09
*** david-lyle_ is now known as david-lyle18:12
*** rarcea has quit IRC18:15
*** xin9972 has quit IRC18:16
*** rarcea has joined #openstack-meeting-alt18:16
*** wiebalck has joined #openstack-meeting-alt18:16
*** rarcea has quit IRC18:16
*** bfernando has quit IRC18:19
*** xin9972 has joined #openstack-meeting-alt18:19
*** ashcrack has quit IRC18:21
*** raliev has quit IRC18:21
*** baoli has joined #openstack-meeting-alt18:24
*** baoli has quit IRC18:25
*** yamahata has joined #openstack-meeting-alt18:25
*** baoli has joined #openstack-meeting-alt18:25
*** rossella_s has quit IRC18:26
*** gouthamr has quit IRC18:26
*** gouthamr has joined #openstack-meeting-alt18:27
*** rarcea has joined #openstack-meeting-alt18:28
*** ashcrack has joined #openstack-meeting-alt18:29
*** s3wong has joined #openstack-meeting-alt18:39
*** jpena is now known as jpena|away18:40
*** sdake has joined #openstack-meeting-alt18:42
*** sdake__ has quit IRC18:43
*** hrybacki has joined #openstack-meeting-alt18:45
*** sdake has quit IRC18:45
*** dustins has quit IRC18:46
*** rarcea has quit IRC18:46
*** sdake has joined #openstack-meeting-alt18:46
*** sdake has quit IRC18:47
*** baoli has quit IRC18:48
*** baoli has joined #openstack-meeting-alt18:48
*** Sukhdev has joined #openstack-meeting-alt18:51
*** jcoufal has joined #openstack-meeting-alt18:53
*** lpetrut has joined #openstack-meeting-alt18:53
*** saneax is now known as saneax-_-|AFK18:54
*** beslemon_ is now known as beslemon18:54
*** jcoufal__ has quit IRC18:56
*** rarcea has joined #openstack-meeting-alt18:58
*** salv-orl_ has joined #openstack-meeting-alt19:00
*** shamail has joined #openstack-meeting-alt19:02
*** salv-orlando has quit IRC19:03
*** tonanhngo has joined #openstack-meeting-alt19:09
*** xin99721 has joined #openstack-meeting-alt19:10
*** xin9972 has quit IRC19:11
*** ozamiatin has quit IRC19:11
*** tonanhngo_ has joined #openstack-meeting-alt19:12
*** ociuhandu has quit IRC19:13
*** tonanhngo has quit IRC19:13
*** pvaneck has joined #openstack-meeting-alt19:15
*** garloff has joined #openstack-meeting-alt19:16
*** tonanhngo_ has quit IRC19:16
*** tonanhngo has joined #openstack-meeting-alt19:17
*** rarcea has quit IRC19:19
*** salv-orl_ has quit IRC19:20
*** salv-orlando has joined #openstack-meeting-alt19:21
*** garloff has left #openstack-meeting-alt19:22
*** dprince has joined #openstack-meeting-alt19:26
*** ihrachys has joined #openstack-meeting-alt19:29
*** ihrachys_ has quit IRC19:31
*** ihrachys_ has joined #openstack-meeting-alt19:33
*** ihrachys has quit IRC19:34
*** jcoufal_ has joined #openstack-meeting-alt19:39
*** jcoufal has quit IRC19:39
*** gk-1wm-su has joined #openstack-meeting-alt19:41
*** matrohon has joined #openstack-meeting-alt19:41
*** gk-1wm-su has quit IRC19:42
*** rfolco has quit IRC19:44
*** panda|bbl is now known as panda19:45
*** dsariel has joined #openstack-meeting-alt19:47
*** baoli has quit IRC19:50
*** ociuhandu has joined #openstack-meeting-alt19:51
*** baoli has joined #openstack-meeting-alt19:51
*** korzen has joined #openstack-meeting-alt19:52
*** beslemon has quit IRC19:53
*** jcoufal_ has quit IRC19:54
*** kfarr has joined #openstack-meeting-alt19:54
*** ociuhandu has quit IRC19:56
*** shamail has quit IRC19:56
*** salv-orlando has quit IRC19:57
dave-mccowan#startmeeting barbican20:00
openstackMeeting started Mon Feb 13 20:00:11 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
dave-mccowan\o/20:00
reroboto/20:01
dave-mccowanhi rerobot20:02
rerobothi dave-mccowan !!!  Is it just you and me today?20:03
dave-mccowanmrhillsman ping20:03
kfarr\o/20:03
mrhillsmanhey20:03
dave-mccowanwe have a few barbicaneers around today.20:03
mrhillsmancool20:04
rerobotCourtesy ping for: alee diazjf woodster jaosorior hockeynut20:04
dave-mccowanthe agenda is in the usual spot:https://wiki.openstack.org/wiki/Meetings/Barbican20:04
dave-mccowan#topic PTG20:04
*** openstack changes topic to "PTG (Meeting topic: barbican)"20:04
dave-mccowanPTG is next week.  https://etherpad.openstack.org/p/ptg-barbican-pike20:04
dave-mccowanwe have a full agenda, but not many people travelling.20:05
dave-mccowanthe word is that most rooms won't have a projector.20:05
rerobot:-O20:05
dave-mccowanwe can use our laptops.20:05
dave-mccowanhow much time do you want to spend with us rerobot?20:06
dave-mccowanwe can leave google hangouts up all day if you want.20:07
rerobotdave-mccowan good question?  I figured maybe we can talk about the software crypto blueprint some... maybe a couple of hours?  I should be available to jump on hangouts.20:07
*** armax has joined #openstack-meeting-alt20:07
*** jcoufal has joined #openstack-meeting-alt20:08
dave-mccowanwhat time do you want to join us on wednesday?  then we can play it by ear after that.20:08
dave-mccowandoes anyone have questions about anything on the agenda?20:08
rerobotwhat time does barbican meetings start on Wed?20:08
rerobotmaybe we can sort the topics into specific hour blocks?20:09
kfarrWondering what the adopt-a-project is?  Heard people talking about it last week, but wasn't sure what that entails20:09
*** arunkant has joined #openstack-meeting-alt20:09
rerobotI was talking to somoene from OSIC ops/engineering the other day20:09
*** spzala has joined #openstack-meeting-alt20:09
rerobotsounds like they adopt a couple of projects every cycle to improve the ops side of it20:10
rerobotkfarr ^^20:10
*** beslemon has joined #openstack-meeting-alt20:10
dave-mccowanmrhillsman is our adopt-a-project rep.  he's in this meeting.20:10
mrhillsmanwe discussed potentially doing exactly that and got approval to do so20:10
mrhillsmanbarbican and ironic were identified as best to start with20:11
rerobotmrhillsman \o/20:11
dave-mccowanrerobot i haven't heard an official start time.  how early EST would you want to join us on Wednesday?20:11
mrhillsmanhttps://etherpad.openstack.org/p/ops-adopt-a-project-pike20:12
*** dimtruck is now known as zz_dimtruck20:12
*** ociuhandu has joined #openstack-meeting-alt20:12
mrhillsmanwe would really like to get you alls feedback20:12
dave-mccowan#topic adopt-a-project20:12
*** openstack changes topic to "adopt-a-project (Meeting topic: barbican)"20:12
mrhillsmanwe more or less are thinking about inserting ourselves in your meetings20:13
dave-mccowanmrhillsman we'd definitely like to hear operator feedback on what is needed in barbican.20:13
*** mfedosin has quit IRC20:13
mrhillsmanand being direct feedback loop for barbican20:13
rerobotdave-mccowan I can do 9 EST, though I might not have fully absorbed my caffeine for the day. :)20:13
mrhillsmanand getting more operators involved20:13
*** jungleboyj has quit IRC20:13
dave-mccowanwe've been stuck at a low adoption rate for a long time, and we're not sure exactly why. :-)20:13
mrhillsmancool20:14
* rerobot thinks not having an out-of-the-box software only driver may be one reason...20:14
mrhillsmanmaybe we can help identify the why and work together on resolving20:14
dave-mccowanit'd be especially nice if the operators' companies can offer code contribution as well, if need to meet the objectives.  our list of active contributors has been slowly declining.20:14
mrhillsmanwe can work together on identifying the why :)20:15
*** dsariel has quit IRC20:15
kfarrThis is exciting!20:15
mrhillsmanif we can get all your thoughts and ideas on the etherpad that would be great20:15
mrhillsmanwe have to have some measurables in place to please our superiors :)20:15
mrhillsmanso what we have there now is what we just think20:16
dave-mccowanmrhillsman you'd like us to add comments to this pad: https://etherpad.openstack.org/p/ops-adopt-a-project-pike20:16
mrhillsmanindeed20:16
mrhillsmani hope it makes sense20:16
mrhillsmanit can change, we just have ideas there20:17
dave-mccowangreat.  we'll do that.  and discuss more at PTG.  anything else to add on this topic?20:17
mrhillsmanawesome20:18
dave-mccowan#topic Ocata Status20:18
*** openstack changes topic to "Ocata Status (Meeting topic: barbican)"20:18
dave-mccowanRC1 has been out for 10 days now.20:18
dave-mccowanIs there anything we should check before declaring it final?20:18
dave-mccowanrerobot anything special to do at this point?  check with any particular distro managers?20:19
rerobothas anyone checked to make sure we can migrate the schema from Newton to Ocata?20:19
dave-mccowanthat's a good check.  (did we change the schema this release?)20:20
rerobotany bugs open that may need checking?20:20
*** ijw has joined #openstack-meeting-alt20:20
*** ociuhandu has quit IRC20:21
dave-mccowandoes anyone have extra cycles this week to do some sanity checking?20:21
rerobotI may be able to check it out if I get this ansible deployment working soon20:21
dave-mccowanrerobot using Kolla?20:22
rerobotdave-mccowan openstack-ansible20:22
dave-mccowanok.  i'll wait another day or two, until we get a chance to test a little bit more.  our changes were pretty small for this release, so I'm hopefull that we're good to go.20:23
dave-mccowan#topic Summit20:23
*** openstack changes topic to "Summit (Meeting topic: barbican)"20:24
dave-mccowanwe got an invitation to present "Barbican Project Update" as a slot in the PWG track.20:24
*** gouthamr has quit IRC20:24
*** jcoufal has quit IRC20:24
*** ijw has quit IRC20:25
dave-mccowanI gave myself, kfarr, and rerobot as the presenters (I was allowed to give PTL + two cores)20:25
*** gouthamr has joined #openstack-meeting-alt20:25
*** ijw has joined #openstack-meeting-alt20:25
rerobot:-O20:25
dave-mccowanwe have a couple other barbican related proposals submitted as well.  so, be on the lookout for when voting starts.20:26
*** adrian_otto has quit IRC20:26
dave-mccowanrerobot, kfarr... no obligation on the presentation... but you do get a free ticket. :-)20:26
kfarrThanks dave-mccowan!20:26
*** kong has joined #openstack-meeting-alt20:27
dave-mccowan#topic Tempest Testing20:27
*** openstack changes topic to "Tempest Testing (Meeting topic: barbican)"20:28
dave-mccowankfarr any news?20:28
dave-mccowani see there's a patch for barbican/glance interaction.20:28
kfarrDane has a glance image signing scenario test up20:28
kfarryeah!20:28
*** dsariel has joined #openstack-meeting-alt20:28
kfarrwe are trying to debug why there is not default image file20:28
kfarr(the error is found under the failing non-voting tempest gate)20:28
*** jcoufal has joined #openstack-meeting-alt20:28
dave-mccowanhmm... is that one of the things that devstack removed?20:29
kfarrmayyybeee20:29
*** rfolco has joined #openstack-meeting-alt20:29
dave-mccowanya, i think it went the way of the default flavors20:29
*** rfolco has quit IRC20:29
kfarrbut it seems there are other scenario tests in the main services that use that file, and they don't seem to be failing20:29
kfarrwe'll figure it out!20:30
dave-mccowan:-)20:30
dave-mccowan#topic Any other business?20:31
*** openstack changes topic to "Any other business? (Meeting topic: barbican)"20:31
*** ociuhandu has joined #openstack-meeting-alt20:32
rerobotI did submit a blueprint20:32
*** zz_dimtruck is now known as dimtruck20:32
rerobotbut I'm going to split it into two as hyakuhei suggested20:32
*** beslemon has quit IRC20:33
dave-mccowanrerobot thanks!  rob mentioned your blueprint at the security project irc last week, with the request for security people to review it.20:34
dave-mccowangood news... it got extra attention.20:34
rerobotyep, got some good feedback so far20:35
dave-mccowani'll plan to have this IRC next week too, even though the PTG will have started.20:36
*** tonytan4ever has quit IRC20:36
*** tonytan4ever has joined #openstack-meeting-alt20:36
*** ociuhandu has quit IRC20:36
dave-mccowani'll ping folks in the channel Tuesday and Wednesday before release Ocata.20:37
dave-mccowanSee ya later...20:37
dave-mccowan#endmeeting20:37
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:38
openstackMeeting ended Mon Feb 13 20:37:58 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:38
openstackMinutes:        http://eavesdrop.openstack.org/meetings/barbican/2017/barbican.2017-02-13-20.00.html20:38
*** rfolco has joined #openstack-meeting-alt20:38
*** rfolco has quit IRC20:38
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/barbican/2017/barbican.2017-02-13-20.00.txt20:38
openstackLog:            http://eavesdrop.openstack.org/meetings/barbican/2017/barbican.2017-02-13-20.00.log.html20:38
*** sdake has joined #openstack-meeting-alt20:41
*** arunkant has left #openstack-meeting-alt20:41
*** korzen has quit IRC20:42
*** ianychoi has quit IRC20:43
*** egallen has quit IRC20:43
*** cknight has quit IRC20:46
*** kfarr has quit IRC20:46
*** rarcea has joined #openstack-meeting-alt20:49
*** tobberydberg has joined #openstack-meeting-alt20:49
*** cknight has joined #openstack-meeting-alt20:49
*** ianychoi has joined #openstack-meeting-alt20:51
*** rarcea has quit IRC20:51
*** nadya has quit IRC20:51
*** rarcea has joined #openstack-meeting-alt20:52
*** rarcea has quit IRC20:53
*** rarcea has joined #openstack-meeting-alt20:53
*** leong has joined #openstack-meeting-alt20:53
*** jcoufal has quit IRC20:54
*** mikal_ is now known as mikal20:54
*** Swami has quit IRC20:55
*** Sukhdev has quit IRC20:56
*** Swami has joined #openstack-meeting-alt20:56
*** GeraldK has joined #openstack-meeting-alt20:57
*** jcoufal has joined #openstack-meeting-alt20:57
*** rarcea has quit IRC20:58
*** mickeys has joined #openstack-meeting-alt20:59
leonggoing to start Product WG irc meeting...21:00
leong#startmeeting product_working_group21:00
openstackMeeting started Mon Feb 13 21:00:53 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
*** shamail has joined #openstack-meeting-alt21:01
leong#topic rollcall21:01
shamailHi all21:01
*** openstack changes topic to "rollcall (Meeting topic: product_working_group)"21:01
leongwho is here for PWG meeting?21:01
*** Arkady_Kanevsky has joined #openstack-meeting-alt21:01
Arkady_Kanevskyhello all21:01
GeraldKhi21:02
leonghi arkady shamail21:02
leonghi geraldk21:02
leongtoday agenda can be found here21:02
*** heidijoy_ has joined #openstack-meeting-alt21:02
leong#link Agenda: https://wiki.openstack.org/wiki/Meetings/product-team21:02
leonghi heidijoy_21:02
heidijoy_Hello!21:03
*** mickeys has quit IRC21:03
leongif you have any item to discuss, feel free to raise up...21:04
Arkady_KanevskyKen and I submitted "update on upgrade story" to Boston summit. AI closed.21:04
leong#topic Action items from last meeting21:04
*** openstack changes topic to "Action items from last meeting (Meeting topic: product_working_group)"21:04
leong#info Ken and Arkady_Kanevsky submitted "update on upgrade story" to Boston summit.21:04
leong#link last week meeting logs: http://eavesdrop.openstack.org/meetings/product_working_group/2017/product_working_group.2017-02-06-21.00.html21:05
leongwe brought up the PWG Forum proposal in this morning UC meeting..21:05
leongit is suggested to discuss after the UC election is closed after this Friday...21:06
leong#info Shamail and Leong will follow up the PWG forum proposal after the UC election as there will be 2 new UC members21:06
Arkady_Kanevsky+121:07
leongany thing else from last week meeting?21:07
leong#topic "open" gerrit review21:08
*** openstack changes topic to ""open" gerrit review (Meeting topic: product_working_group)"21:08
Arkady_Kanevskynope. only mid-cycle planning which is a separate topic on agneda21:08
leongok..i set this as a regular topic.. anything that need attention to review user-stories?21:08
*** AndyU has joined #openstack-meeting-alt21:08
leong#link user-story review: https://review.openstack.org/#/q/project:openstack/openstack-user-stories+status:open21:08
Arkady_KanevskyI would like review for 2 of my tracking pull requests21:09
Arkady_Kanevskyhttps://review.openstack.org/#/c/426613/ and https://review.openstack.org/#/c/428571/21:09
leongarkady_kanevsky: are they still Work In Progress?21:09
Arkady_Kanevskysee good progress on others including pieters21:09
* shamail is slightly distracted while multi-tasking, sorry21:10
leongor are they ready to review?21:10
Arkady_Kanevskyyes WIP21:10
*** ihrachys_ is now known as ihrachys21:10
Arkady_Kanevskyworking on gap analysis. Tus, active on template for it21:10
leongnice21:10
*** shamail has quit IRC21:10
GeraldKwe need one more review for the template: https://review.openstack.org/#/c/426994/21:10
leongthat bring to the next item... need core to approve the first revision of gap-analysis template21:11
Arkady_Kanevskybut not all pieter's pull requests are moving forward...21:11
leongthanks GeraldK21:11
*** lpetrut has quit IRC21:11
*** shamail has joined #openstack-meeting-alt21:12
leong#link Gap-analysis template: https://review.openstack.org/#/c/426994/21:12
*** yamamoto has joined #openstack-meeting-alt21:12
Arkady_Kanevskywe need second +2 on Gerald's one21:12
kencjohnstonleong GeraldK I'm still not onboard with why we need gaps analysis as a separate document21:12
leonghi kencjohnston21:12
kencjohnstonI'm sorry if I missed the meeting when this was previously discussed21:12
shamailWhere would you include it otherwise kencjohnston? Curious21:13
Arkady_Kanevskyyou had not missed anything.21:13
kencjohnstonIt seems to me like gaps analysis should either happen in the user story, as we iterate on it, or in a cross project spec21:13
Arkady_Kanevskyall discussions are on pull request21:13
leongkencjohnston, if you look at existing workflow, there is this gap-analysis phase21:13
GeraldKuser story should IMHO not include gap analysis. different persons may work on it.21:13
leongthis document is for that phase21:13
kencjohnstonleong Agreed, but why a separate document?21:14
leonguser story only specify "requriements"21:14
kencjohnstonGeraldK Say more about that?21:14
Arkady_KanevskyKen, what happens when you have a gap that does not have any projects that can cover it?21:14
*** sambetts is now known as sambetts|afk21:14
leongi believe that was the discussion many months back that we want to take the "gap-analysis" out from the "user-requirements"21:14
kencjohnstonCross project spec, leave it in the user story?21:14
kencjohnstonDoes the development community/tc agree that we need to create another artifact that is out of bands of the ones they officially use?21:15
GeraldKthe user story might be written by someone with no / little technical background. the gap analysis needs very good knowledge of the different projects21:15
shamailkencjohnston: the gaps analysis is happening before the implantation so cross project spec would not exist yet.  It is to identify what are the areas we need to figure out an implementation plan for.  If we add it to the user story then we will be adding a lot of technical/implementation details into a document that is generally more concept oriented.21:15
AndyUIt would be really great for people like myself who are new to this, to have some side meetings or (?) to learn all of what you're doing to refine the process itself and where things are at. Also how to actively participate most effectively.21:15
leongkencjohnston: what do u mean "another artifact that is out of bands of the ones they officially use"21:15
kencjohnstonGeraldK +121:15
leongthis gap-analysis does not replace BP/SPEC/etc21:16
shamailI would advocate for the implementation plan and gaps analysis being a single doc since they both contain implementation/technical details.21:16
kencjohnstonleong Well the development community uses specs, blueprints and cross project specs21:16
Arkady_Kanevskygap analysis is idnetify what we need to create in cross-spec, individual projetcs or board.21:16
kencjohnstonWell this gap analysis woudl very easily duplicate specs and bueprints in the case where the gap is in an existing project21:16
AndyUIt would seem that the gap analysis and the implementation planning have mutual interdependencies and that neither can be done completely independently of the other21:16
kencjohnstonDid we create this gaps analysis solely for the cases where new projects are required?21:17
*** fzdarsky|afk has quit IRC21:17
kencjohnstonI thought our part was "define the need/use case" and then reference that in implementation/gaps documents like blueprints specs, etc21:17
Arkady_KanevskyKen, no. We create it so we can document analysis and discuss it in the group before going to cross functioal and projects21:17
shamailkencjohnston: the development effort would still use the existing artifacts.  This artifact is for our workflow and not needed for Dev workflow.  It is simply there to address the gap between "user story" --> specs/bps. (E.g. How do we define what needs to be done in Dev workflow artifacts to meet this user story)21:18
leongthis gap-analysis make sure that all "requirements" defined in user-story.rst are analysed and with actionable plan21:18
Arkady_KanevskyTo me is technicaly details for user story.21:18
Arkady_KanevskyLeong +121:18
kencjohnstonso the Rolling Upgrades user stry has a "gaps analysis"21:18
leong+1 shamail: address the gap between "user story" --> specs/bps.21:19
kencjohnstonthat doesn't include technical details21:19
kencjohnstonand should reference blueprints and specs21:19
kencjohnstonteh gap between userstory and blueprints and specs shouldn't have technical details right?21:19
*** adisky_ has quit IRC21:19
kencjohnstonthose should be saved for the specs?21:19
shamailkencjohnston: +1 but it will call out "resolve bug X", "add X feature in service", etc21:20
Arkady_Kanevskygap anal;ysis should have enouhg details so we as a group can agree what cross functional spec and projects blueprints we need to do21:20
kencjohnstonLet me take a step back, what we hear from teh development community is "I want to know what is important and what the use cases are." What we hear from operators is "I want to be able to communicate what is important and what the use cases are."21:20
shamailThe actual contents of what is "add X feature in service" should be a spec/np21:20
shamailbp*21:20
Arkady_KanevskyThe person who does gap analysis is not necessary the person how did user sotry or create BP, bugs and specs21:20
GeraldKkencjohnston: the gap analysis does not necessarily contain implementation details, however, someone needs to be familiar with bp and specs and probably even have some more insights into existing projects to be able to perform the gap analysis and identify related bp / specs21:21
AndyUWhat if the gap analysis reveals some existing's back that would potentially be in conflict with the bigger picture?21:21
*** pnavarro has quit IRC21:21
leongan example of gap-analysis doc is here21:21
leong#link gap-analysis for baremetal: https://etherpad.openstack.org/p/bare_metal_service_gap_and_overlap_analysis21:21
kencjohnstonSo should it contain implementation details or not?21:21
*** iyamahat has quit IRC21:22
Arkady_Kanevskyimpl details is not a requirement for it21:22
shamailI get what you are saying Kencjohnston too... I think it should remain an optional artifact (a template for those that want to create a gaps analysis is a plus) and it should contain details about the implementation plan based on requirements rather than technical details on the implementation details (that should be reserved for the actual cross project spec/bp/project spec)21:22
kencjohnstonFor the record, https://etherpad.openstack.org/p/bare_metal_service_gap_and_overlap_analysis, reads like a tracker document does it not?21:22
Arkady_KanevskyBut if it conflicts how some ohter feature in a project is implemented then we need that info21:22
GeraldKif we leave out the gap analysis phase we would need to re-consider the work flow defined earlier. there, the gap analysis phase is mandatory21:23
leongit is more to keep track of discussion and the output will goes into the tracker21:23
kencjohnstonleong So almost like an etherpad? :)21:23
leongif you don't have a discussion, where are you going to have the "output"21:23
leongit is an ether pad now, that's why we are moving into a gap-analysis template so that it can be formally tracked in repo21:24
kencjohnstonI think I now understand the need21:24
Arkady_Kanevskyif we want gap analysis to be more felxible doc we can have it etherpad.\21:24
*** jcoufal has quit IRC21:24
GeraldK#link https://etherpad.opnfv.org/p/promise_gap_analysis Capacity mgmt gap analysis draft21:25
Arkady_Kanevskyeasier to discuss and record discussions21:25
kencjohnstona bridge between the user story and the tracker, I completely sypathize with that need21:25
kencjohnstonI'd strongly recommend keeping these docs in an etherpad21:25
GeraldKfor the capacity mgmt gap analysis we followed the baremetal example21:25
kencjohnstonespecially given our teams general "time to merge" metrics21:25
kencjohnstonMaybe move the template to the wiki and point etherpad creators at it21:25
kencjohnston?21:25
Arkady_KanevskyBut we need to havea clear end of gap_analysis step on our workflow when we move to netx step21:25
*** mickeys has joined #openstack-meeting-alt21:25
kencjohnstonHow frequently would we expect to edit this document?21:26
GeraldKwe had used the etherpad to do the gap analysis. we could convert to RST once we finalized it.21:26
leonginformation on etherpad will easily get lost, i prefer a system to "version-control" it :)21:26
Arkady_KanevskyThe only concern with etherpad that they are not backed up and anybody can change it.21:26
Arkady_Kanevsky+1 ofr version control21:26
kencjohnstonArkady_Kanevsky "Anybody can change it" is a positive21:26
leongnot very often for editing once "agreed" on the completion of gap analysis21:27
Arkady_Kanevskynot aftre we are done.21:27
*** jcoufal has joined #openstack-meeting-alt21:27
kencjohnstonEverything from the gaps analysis eventually gets translated into the tracker right?21:27
GeraldKmy experience: the template was under review in Etherpad for 2 weeks -> almost no feedback. once we had moved it to RST, we had received many additional comments and trigger this discussion here....21:27
*** yamamoto has quit IRC21:27
Arkady_Kanevskyhard to refer to a doc tha tcan be chnage at anytime21:27
leongdepends.. a gap-analysis can say: this requirement need a new project or "completely out of scope"21:28
Arkady_Kanevskyagree with gerald. review forced dicipline21:28
*** shamail has quit IRC21:28
kencjohnstonSorry for the prolonged discussion, I'll +2 the gaps analysis template21:28
*** tobberydberg has quit IRC21:28
kencjohnstonBut it would be great to set some guidliens for reviewers of future gaps analysis submissions21:28
leongthat also help us to keep track of future AUC contribution, by the way :-)21:28
kencjohnstonbecause generally I'm going to be +2 everything I see right?21:28
Arkady_Kanevskyken it is a good discussion. If we have a better process let's consider it21:29
leonglol kencjohnston21:29
AndyU+1 to guidelines21:29
kencjohnstonleong I'm actually serious, I have no idea how to decide if this document is appropriate/sufficient/etc21:29
*** julim has quit IRC21:29
*** shamail has joined #openstack-meeting-alt21:30
*** julim has joined #openstack-meeting-alt21:30
leongi would suggest we go for this revision 1 and we can improve along the line21:30
Arkady_Kanevskymy approach is lets start somewhere and then improve as we go21:30
Arkady_Kanevskydo we want do have this topic for mid-cycle?21:30
AndyUneed a way to assess getting consensus of stakeholders who DO know if doc is appropriate/sufficient21:30
kencjohnstonto be clear, I'm not talkign about the template, I guess I can ensure the content is correct in the template's format.21:30
leongdefinitely can discuss that at mid-cycle21:31
*** beslemon has joined #openstack-meeting-alt21:31
kencjohnstonsounds good, sorry again for the prolonged convo. I feel smarter, hopefully you all don't feel dumber. :)21:31
leongthat's a good discussion to make everyone align :-)21:32
Arkady_Kanevsky+221:32
leongso let's get "core" to review the template21:32
leong#link Gap-analysis template: https://review.openstack.org/#/c/426994/21:32
*** fzdarsky|afk has joined #openstack-meeting-alt21:32
Arkady_Kanevskywe have 2 +2 on it now21:32
GeraldKkencjohnston: i understand your issue. very difficult for someone to review the gap analysis when you had not been part of the discussion on it or you are no core of the related projects21:32
*** jkilpatr has quit IRC21:32
leongthe user-story-owner /anyone else who drive the user-story will be "technically" to review the gap document21:33
GeraldKthanks. be prepared that we will submit the first example on the capacity mgmt very soon :)21:33
*** heidijoy_ has quit IRC21:33
*** dprince has quit IRC21:34
Arkady_Kanevskyi will follow suite21:34
*** beslemon has quit IRC21:34
leonglet's move on..21:34
leonganything else on existing user-story-to-review?21:34
leong#topic Midcycle planning21:34
*** openstack changes topic to "Midcycle planning (Meeting topic: product_working_group)"21:34
*** shamail has quit IRC21:34
leong#link PWG midcycle planning: https://etherpad.openstack.org/p/MIL-pwg-meetup21:35
*** jmckind_ has quit IRC21:35
*** shamail has joined #openstack-meeting-alt21:35
leongagain, please suggest agenda item on the etherpad and please indicate if you will be there for F2F midcycle21:35
leongi want to talk about the location...21:35
leongArkady_kanevsky.. did you say Dell can host us?21:36
Arkady_KanevskyArkady sent email for possible location at DellEMC21:36
shamailleong: when do we want to finalize the agenda by?  My recommendation would be by 2/27 so we have time to prepare materials if needed21:36
*** dave-mccowan has quit IRC21:36
shamailArkady_Kanevsky: thanks!21:36
leong+1 shamail21:36
Arkady_KanevskyYes. I send email with location nad rought distance from Wed-Th venue21:36
leongi am hoping to get some sense on the location then follow by finalizing the agenda21:37
*** johndperkins has quit IRC21:37
leongshall we agreed that to fiinalize the agenda by 2/27?21:37
Arkady_Kanevskysure.21:37
Arkady_KanevskyBut let's agree on location first.21:38
shamailSounds good.21:38
Arkady_Kanevskyneed to make reservations21:38
shamailArkady_Kanevsky: can we confirm that location? We seem to be having a hard time finding venues.21:38
leongif we can't get confirmation from members company, the other alternative is to "pay" for the room at coworking-login, which is the same place as ops-midcycle21:38
*** beslemon has joined #openstack-meeting-alt21:38
Arkady_KanevskyI have rooms reserved at Dell facility.21:39
shamailArkady_Kanevsky: Is DellEMC confirmed?21:39
shamailFor 3/13 & 3/14?21:39
Arkady_Kanevskyhad not aske for hotels near by or transporation to from airport21:39
leongdo you have the address?21:39
Arkady_Kanevskyyes Mon-Tu21:39
shamailThanks Arkady_Kanevsky21:39
Arkady_KanevskyDell - Viale Piero e Alberto Pirelli 6, Milano (conf room Vivaldi) - Monday21:40
leongfor a group of 10-15 people?21:40
Arkady_KanevskyDell - Viale Piero e Alberto Pirelli 6, Milano (conf room Verdi) - Tu21:40
Arkady_Kanevskysame location deiff room21:40
shamailEveryone okay with DellEMC as the host for our midcycle?21:40
leongis about 7 mins drive away from Ops location21:41
*** ashcrack has quit IRC21:41
leongi think we can car-pool21:41
Arkady_Kanevskyyes for 15 people. Oval table for 10 first day . bigger one for Tu21:41
shamailGreat location21:41
shamailleong: can you lock it in?21:41
leongi am fine with Dell location21:41
leong+121:41
Arkady_KanevskyI will let local team know21:41
leong#agreed PWG midcycle location will be at DellEMC office at Viale Piero e Alberto Pirelli 6, Milano21:42
*** Shrews has joined #openstack-meeting-alt21:42
leongarkady_kanevsky: please let us know if there anything we need for logistic, e.g. pre-register for entering the building21:42
leongthank arkady21:42
*** johndperkins has joined #openstack-meeting-alt21:43
leongnext..the agenda items21:43
Arkady_Kanevskywill find out and send email on it and will update etherpad21:43
leongshall we brainstorm here or do it offline and to review next week?21:43
leongi mean the agenda item for PWG midcycle21:43
shamailLeong: next week review is good, I would send a reminder on ML21:44
leongcool21:44
leong#agreed All to suggest PWG midcycle agenda and team will review in next meeting21:44
*** jaypipes has quit IRC21:44
Arkady_Kanevsky+121:45
leong#action shamail to email ML about the midcycle agenda item discussion21:45
shamailThanks leong21:45
leong#action leong and arkady_kanevsky to email ML on the midcycle location21:45
* leong time check 15 mins.. 21:45
Arkady_KanevskyI had updated etherpad already with location address21:46
leongone  more thing21:46
leongthe ops-midcycle, is there any session that PWG want to present/talk at Ops midcycle?21:46
*** salv-orlando has joined #openstack-meeting-alt21:46
leong#link Topics/sessions on Ops midcycle: https://etherpad.openstack.org/p/MIL-ops-meetup21:46
leongdo we need "lighting talk" to introduce PWG objective and the user-story-workflow to operator?21:47
shamailleong: +121:47
AndyU+1 to educating on user-story-workflow21:48
leong#action leong to propose a "PWG lighting talk" at Ops midcycle21:48
Arkady_KanevskyWhat about bringing user communities/workload together?21:48
Arkady_Kanevskylike HPC, big data, NFV, enterprise, ...21:48
Arkady_KanevskySome education needed on driving reqs thru PWG21:49
GeraldKarkady: +121:49
shamailA session (not PWG specific) on how are operators sharing their requirements and success/failures would be a good one.21:49
leong+1 shamail21:49
leongdo you want to propose that on the ops etherpad?21:50
*** sshnaidm is now known as sshnaidm|off21:51
shamailSure21:51
leong#action shamail to propose a session at ops midcycle on "how are operators sharing their requirements and success/failures"21:51
leongwe have 9 mins to the hour.... anything we want to discuss next?21:52
leongshamail/heidijoy_ do you want to provide a quick update on the "roadmap"?21:52
leong#topic Roadmap Update21:53
*** openstack changes topic to "Roadmap Update (Meeting topic: product_working_group)"21:53
shamailthanks leong, are you here heidijoy?21:53
GeraldKheidijoy has quit 20 mins ago21:53
shamailShe isn't here anymore21:53
*** jcoufal_ has joined #openstack-meeting-alt21:53
leonglooks like she dropped21:53
shamailHeidi Joy sent out a survey to the PTLs asking about their plans for Ocata and Pike21:54
shamailSo far we have a response from 13 PTLs21:54
shamailAnd we are reaching out to others as a follow-up21:54
leong#info a survey to the PTLs asking about their plans for Ocata and Pike was sent and so far received response from 13 PTLs21:54
*** jcoufal has quit IRC21:55
shamailFoundation has to do a marketing launch tomorrow and they have been working towards that.  We have not started on the multi-release roadmap yet.21:55
shamailThat's all I have so far21:55
leongi assume that the PWG members will need to help to collate the output after that?21:55
*** jcoufal_ has quit IRC21:56
leonglike what PWG has done previously for the community roadmap?21:56
leongshamail: do you need any help from the PWG members here?21:56
*** jheroux has quit IRC21:56
AndyUWhen future roadmap targets are given, is there any later status tracking/reporting?21:57
*** shamail has quit IRC21:58
leongthat's a good question andyu21:58
leongi don21:58
leongi don't remember there is a "status" tracking on previous roadmap deliverables21:58
*** shamail has joined #openstack-meeting-alt21:58
*** gouthamr has quit IRC21:59
leongexcept those proposed bp/spec are on tracked21:59
AndyUjust wondering... status tracking could be a daunting challenge21:59
* leong one mins to hit the bell21:59
shamailleong: I think we're good for now... next time we would need help is when processing21:59
leongsure!21:59
leongsorry the time fly....  i can't get into the next topic on "Collaboration with LCOO", feel free to reach out/discuss over ML and we can chat about in next meeting21:59
leongany question feel free to follow up on mailing list.22:00
*** shamail has quit IRC22:00
leong#endmeeting22:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"22:00
GeraldKbye everyone22:00
openstackMeeting ended Mon Feb 13 22:00:41 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/product_working_group/2017/product_working_group.2017-02-13-21.00.html22:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/product_working_group/2017/product_working_group.2017-02-13-21.00.txt22:00
openstackLog:            http://eavesdrop.openstack.org/meetings/product_working_group/2017/product_working_group.2017-02-13-21.00.log.html22:00
jeblairanyone around for a zuul meeting?22:01
fungii sure am22:01
mordredI love zuul meetings22:01
jeblairmordred: zuul meetings love you too22:01
jheskethYep :-)22:01
* fungi likes traffic lights22:01
ShrewsI only like zuul meetings as a friend22:01
jeblairfungi: traffic lights do not love you22:02
*** jamielennox has joined #openstack-meeting-alt22:02
*** Arkady_Kanevsky has quit IRC22:02
jeblairfungi: you may have noticed this22:02
jeblair#startmeeting zuul22:02
openstackMeeting started Mon Feb 13 22:02:40 2017 UTC and is due to finish in 60 minutes.  The chair is jeblair. Information about MeetBot at http://wiki.debian.org/MeetBot.22:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.22:02
*** openstack changes topic to " (Meeting topic: zuul)"22:02
openstackThe meeting name has been set to 'zuul'22:02
*** leong has left #openstack-meeting-alt22:02
jeblair#link agenda https://wiki.openstack.org/wiki/Meetings/Zuul22:02
jeblair#link previous meeting http://eavesdrop.openstack.org/meetings/zuul/2017/zuul.2017-02-06-22.03.html22:03
jeblairi conveniently did not alter the agenda from last week22:03
jeblairseeing as how it still seems relevant :)22:03
jeblair#topic Status updates: Nodepool Zookeeper work22:04
*** openstack changes topic to "Status updates: Nodepool Zookeeper work (Meeting topic: zuul)"22:04
jeblairShrews: iiuc, we're at "we can probably launch nodes at the ptg" yeah?22:04
SpamapSo/22:05
Shrewsjeblair: yes22:05
Shrewswe seem to be launching them in test scenarios, at least22:05
*** pvaneck_ has joined #openstack-meeting-alt22:05
*** AndyU has quit IRC22:05
* fungi takes that as a sign22:06
Shrewsand in the gate-dsvm-nodepool job (when i temporarily enabled it)22:06
Shrewshttp://logs.openstack.org/49/431649/6/check/gate-dsvm-nodepool/c796757/console.html#_2017-02-10_16_38_09_80611822:07
*** GeraldK has quit IRC22:07
Shrewswe can't re-enable that job until I get deletion working22:07
*** pvaneck has quit IRC22:08
pabelangero/22:08
pabelangerShrews: what about moving the exit below our nodepool delete syntax for now?22:09
Shrewspabelanger: we could do that22:09
*** wiebalck has quit IRC22:09
jeblairwe might have delete soon anyway... :)22:09
fungithat risks sticking around after we fix deletions22:09
jesusauro/22:09
Shrewsfungi: that was my worry  :)22:09
jeblairat least, if it's a choice, i'd rather we just forge on with deleting and then enable the job22:09
fungiunless we track undoing that workaround in the job22:10
pabelanger++22:10
jeblairpabelanger: how go the cli tools?22:10
pabelangergood so far, I'm re-enabling skipped tests at the moment.  I need to look into alien-list commands22:11
pabelangerI'll have more patches up for tomorrow22:11
pabelangerwill need some help with the job-create / job-delete tests, I don't think we have that in zookeeper yet22:12
*** yamamoto has joined #openstack-meeting-alt22:12
jeblairpabelanger: no; maybe we should defer those for a little longer?22:12
pabelangerya, if people are okay with that22:12
jeblairit's a fairly stand-alone feature that i don't think we need for the ptg, so maybe engergy better spent elsewhere for now22:13
pabelangerack22:13
*** jkilpatr has joined #openstack-meeting-alt22:13
jeblairfungi, mordred, Shrews: ^?22:14
Shrewswhat are the job-create/-delete tests?22:14
jeblairShrews: it's the auto-hold feature22:14
jeblairwe should probably see about renaming the commands to auto-hold too22:15
fungiyeah, i don't feel like we need that implemented before next week22:15
jeblairauto-hold a node when a specific job fails22:15
fungiit shouldn't prevent the planned exercise22:15
mordredI agree22:15
jeblairalso, erm, i don't think we can implement it in nodepool :)22:15
jeblairso even better, let's talk about where to put that at the ptg :)22:15
*** ihrachys has quit IRC22:16
Shrewsyeah, was just wondering how that would work22:16
jeblair(maybe it could become a zuul feature (to instruct nodepool to hold nodes))22:16
jeblair#agreed defer job-create/job-delete (auto-hold) related work until after the ptg22:16
fungiright, the context for that is primarily in zuul22:17
jeblairyeah, i'm happy that nodepool knows less and less about 'jobs'.  :)22:17
pabelanger+122:17
jeblairpabelanger, Shrews: anything else on this topic?22:18
ShrewsNope22:18
pabelangernothing here22:18
jeblair#topic Status updates: Devstack-gate roles refactoring22:18
*** openstack changes topic to "Status updates: Devstack-gate roles refactoring (Meeting topic: zuul)"22:18
jeblairrcarrillocruz sends his regrets as he can't make this meeting22:19
jeblairso unless anyone else wants to jump in here, i'll move on?22:19
jeblair#topic Status updates: Zuul test enablement22:20
*** openstack changes topic to "Status updates: Zuul test enablement (Meeting topic: zuul)"22:20
jeblairSpamapS and adam_g have been pushing on this recently22:20
SpamapSNot much to report22:21
SpamapSI have been distracted away from the main problem I hit Friday but hope to get back to it tomorrow.22:21
jeblairi'm about halfway through reviewing the current stack; if anyone else wants to review that would be appreciated22:21
adam_gi should have some more cycles to pick away at this starting soon22:21
*** beslemon has quit IRC22:21
jeblairadam_g: \o/22:21
SpamapSI believe there's a problem with the behind_dequeue test that manifests as a timeout waiting for settle (possibly a bug that makes it never settle)22:22
jheskethYep, I need to catch up on reviews and can focus on that22:22
jeblairSpamapS: indeed; i think if someone can sit down with that test and a full pot of coffee, we'd all be the better for it22:22
jeblairjhesketh: thanks!22:23
SpamapSjeblair: I will have about 3 hours to stare at it tomorrow. :)22:23
* jeblair guesses: SpamapS enjoy your flight!22:24
jeblair#Status updates: Zuul Ansible running22:25
jeblair#topic Status updates: Zuul Ansible running22:25
*** openstack changes topic to "Status updates: Zuul Ansible running (Meeting topic: zuul)"22:25
SpamapSjeblair: almost.. waiting for a shuttle from Reno -> Tahoe ;)22:25
jeblairoy22:25
jeblairi think my crazy playbook change finally merged22:26
jeblairso we're running playbooks and there's some semblance of rules around inheritance, etc now22:26
jeblairmordred: it looks like https://review.openstack.org/428798 is about ready22:26
jeblairjhesketh: ^ you might be interested in that one too22:26
jheskethcool :-)22:27
jeblairSpamapS has reservations about the approach there....22:27
*** beslemon has joined #openstack-meeting-alt22:27
jeblairi understand the hesitation there and agree with it22:27
mordredI do too22:27
pabelangerYay22:27
jeblairthe only thing i'd add is that we really do need to get that right, because without it, there's pretty much nothing standing between our army of contributors and compromising the credentials we protect our systems and openstack development with22:28
*** tellesnobrega has quit IRC22:28
jeblairi also think we should wear belts and suspenders22:28
SpamapSI think it's 100% worthwhile to pursue a playbook-friendly approach22:28
SpamapSrather22:28
mordredyah. I am of the opinion that neither containment nor ansible hacks are good enough by themselves - and we need to do as good a job as we can on both22:28
SpamapSplaybook-author-friendly22:28
jeblairbut i want to convey that if we fail at our 'best effort' there, it will be a *significant* failure.22:29
mordredyup22:29
SpamapSHowever, the zuul-operator-friendly approach is likely to provide a launcher containment mechanism.22:29
pabelangerYa, going to be a little scary the first time it happens :(22:29
SpamapSI wonder if we should work out a spec for what's required.22:29
jeblairit needs to not happen :)22:29
SpamapSyeah it shouldn't happen. We can think through this. :)22:29
SpamapSI mean, other than SSH'ing to boxes and reading local files, the launcher probably doesn't need to do much else.22:30
jeblairpart of why we stopped using jenkins is security related.  if we replace it with something worse, zomg.22:30
*** matrohon has quit IRC22:30
jeblairanyway, i don't think anyone disagrees with any of the facts on the ground.  i mostly wanted to emphasize that as a matter of approach.  :)22:31
mordred++22:31
SpamapSso feels like we could spec something pretty narrow out. Like, dib up a tarball with ansible in it, bind mount in the relevant data for the job, and execute ansible-playbook in a significantly hobbled container.22:31
SpamapSbut.. needs a spec and some time spent on it22:31
mordredagree. adding the container exceution shouldn't be terribly difficult, it just needs all of our skepticism pointed at it :)22:32
SpamapSalso somehow22:32
SpamapSwe have to write some piece22:32
SpamapSin Rust22:32
SpamapS;)22:32
* mordred tucks SpamapS back into his rust-hole22:32
* SpamapS sees a setuid Rust binary in our future22:32
jeblairanyway.... :)22:32
jeblairi still have roles and repo set up on my back-burner22:33
SpamapSactually I wonder if we could leverage privsep22:33
jeblairbut i'm switching gears to 'actually get daemons running' this week in prep for ptg, so not sure if they'll be there by then22:33
jeblairmordred: oh, the other thing is, what's the state (or what needs to be done) for telnet console log streaming of shell commands?22:34
*** tellesnobrega has joined #openstack-meeting-alt22:34
jesusaurjeblair: what needs to be done for repo set up? that sounds like it might be some long-hanging fruit i can pick22:34
mordredjeblair: thank you. I was tyring to remember what the next thing I needed to work on was22:34
jeblairjesusaur: implement the parts that pass through the "repos:" part of jobs to the launcher22:36
jeblairjesusaur: and yeah, that change probably isn't too extensive22:36
*** gouthamr has joined #openstack-meeting-alt22:37
jeblairbasically, add it to the parser and model, pass it through json to the launcher, and then make sure the launcher adds it to the merge stack (very similar to what i just did for playbook repo setup)22:37
jesusaurjeblair: cool, i'll take a stab at that this week22:37
jeblairjesusaur: sounds good.  i don't know if it has its own story yet22:38
jeblair#topic Progress summary22:38
*** openstack changes topic to "Progress summary (Meeting topic: zuul)"22:38
jeblairwhich brings us to.... :)22:38
*** tommylikehu_ has joined #openstack-meeting-alt22:39
jeblairSpamapS: i think we may have a couple of new stories we could add22:39
jeblairmordred: telnet shell console log streaming22:39
SpamapS#link https://storyboard.openstack.org/#!/board/4122:39
jeblairjesusaur: repo setup in launcher22:39
jeblairjeblair: roles setup in launcher22:40
SpamapSmordred: jesusaur I'll add those and assign the main task to you.22:40
mordred\o/22:40
jesusaurSpamapS: thanks22:40
jeblairat least, i don't think they already exist.  i'm working from memory22:40
SpamapSDoes anyone have any issue with the way storyboard is working out?22:41
SpamapSI feel like people are doing a good job of picking up tasks and stories for the bigger things, and I haven't seen much duplication other than accidental test dupes22:42
jeblairmy main issue is lack of time to work on boartty22:42
SpamapSjeblair: I'm searching first.. not finding them. :)22:42
ShrewsSpamapS: I still avoid it, but I'm probably the oddball22:42
SpamapSjeblair: I've been using boartty and I quite enjoy it, when it doesn't crash :)22:42
SpamapSShrews: we all seem to know your turf and don't step on it either :)22:42
jeblairlet's use the last 15m to finish checking in on ptg prep22:44
jeblair#topic PTG prep22:44
*** openstack changes topic to "PTG prep (Meeting topic: zuul)"22:44
jeblair#link https://etherpad.openstack.org/p/pike-ptg-zuul22:44
jeblairfungi: did you get a chance to poke at the nodepool metadata question?22:45
funginope, was hoping to look at it today22:45
jeblaircool22:45
fungii have a strong recollection it's greedy right now22:45
fungiand so may pose issues22:45
*** ansmith has quit IRC22:45
jeblairokay, it might be nice to fix that before the ptg if we can22:45
fungibut need to dig into the source code to confirm22:45
*** tonytan4ever has quit IRC22:46
*** ansmith has joined #openstack-meeting-alt22:46
jeblairif anyone wants to volunteer to pitch in on a nodepool v2+v3 thing, see fungi22:46
fungii want to say we punted on making it possible to have two nodepools coexist in a single tenant until we needed it to do so, which is i guess now :/22:46
jeblair(or nodepool v0+v3 i dunno)22:46
pabelangerI'm pretty much ready to bring nl01.o.o online starting tomorrow.22:47
*** panda is now known as panda|zZ22:47
fungipabelanger: awesome!22:47
jeblairpabelanger: cool, did all those patches get reviewed/merged?22:47
pabelangernot merged, still looking for some more eyes22:47
jeblairi think i reviewed them, but if i missed some pls ping me22:48
pabelangerzuulv3-dev.o.o is a little more complex, trying to get all the puppet things in place, but going to be a slow process.  I think for that, I'm going to launch a bare server, and slowly start moving things into puppet.22:48
jeblairpabelanger: that sounds good22:48
clarkbfungi: jeblair just really quickly reading the nodepool v2 code. if you use a different provider name then it will be ignored22:49
*** salv-orlando has quit IRC22:49
clarkbso call the new one rax-iad-v3-test or something and it should avoid being deleted by prod nodepool22:49
jeblairoh huh, interesting.22:49
clarkb(you'll need to check v3 also has that behavior)22:49
clarkbprovider_name is the metadata we attach to instances22:50
fungiclarkb: oh, if it's requiring the provider name to match then we can indeed work around that at least22:50
clarkband if the value there isn't in the current processes config it passes it over22:50
fungiv3 doesn22:50
fungi't have leak cleanup yet afaik22:50
jeblairindeed, it doesn't have cleanup yet.22:51
Shrewsfungi: it has NO cleanup yet, but will only delete nodes that are registered with ZK anyway22:51
Shrewswhen ready22:51
jeblairwe will probably want to add leak cleanup back in as well later on22:51
Shrewsyeah, but that won't be this week, i don't believe22:52
fungiright22:52
jeblairyeah, more of a 'before release' thing22:52
jeblairany other ptg-prep things we should be talking/thinking/doing?22:52
jeblairi sent out my 'zuulv3 primer' email22:53
jeblairhopefully that helps.  sorry it's long.22:53
jeblairi know some people read it at least :)22:53
clarkbI skimmed will have to read properly soon22:53
jesusaurwill there be a way for those of us not at the ptg in person to follow along from home?22:54
jeblairjesusaur: i don't know that we have firm plans, but we have more than one person asking that22:54
jheskethjeblair: it was a good email, thanks for putting that together22:54
jeblairknowing us, i'm guessing most of us will have an irc window open22:55
fungiyeah, worst case, someone in the room hanging in irc can pass along things to hack on22:55
jeblairmaybe we can have someone connect up to pbx.o.o22:55
jeblair(i'm partly being vague since this is our first one and i don't know what to expect; maybe others have more thoughts)22:56
jesusauri've never tried to use pbx.o.o, but imo irc is a fine plan22:56
clarkbpdx worked well when I listened into vancouver sessions22:57
pabelangersame for me for Japan22:57
jeblairjesusaur: i think you can help by making sure we know you're around and want to participate; we'll need to make sure we communicate scheduling to you and other remote folks so you know to do that :)22:57
clarkbwow nice typo on pbx clarkb22:58
jeblairjesusaur: hopefully the ethercalc thing will help with that; i don't know if we know what that will look like yet though...22:58
fungisomeone has airports on the brain22:58
jeblairclarkb: p[bd]x is awesome.  and weird.22:58
jeblairthanks everyone for all the ptg prep!  and all the other work!23:00
*** gk--1wm- has joined #openstack-meeting-alt23:00
*** gk--1wm- has left #openstack-meeting-alt23:00
jeblairsee you next week!23:00
fungithanks, jeblair!23:00
pabelanger++23:00
jeblair(possibly virtually)23:00
jesusaur++23:00
jeblair#endmeeting23:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"23:00
jhesketho/23:00
openstackMeeting ended Mon Feb 13 23:00:23 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-13-22.02.html23:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/zuul/2017/zuul.2017-02-13-22.02.txt23:00
openstackLog:            http://eavesdrop.openstack.org/meetings/zuul/2017/zuul.2017-02-13-22.02.log.html23:00
*** Shrews has left #openstack-meeting-alt23:00
*** saneax-_-|AFK is now known as saneax23:02
*** dhellmann has quit IRC23:05
*** dhellmann has joined #openstack-meeting-alt23:06
*** annegentle has quit IRC23:07
*** dsariel has quit IRC23:07
*** dizquierdo has joined #openstack-meeting-alt23:08
*** tommylikehu_ has quit IRC23:10
*** marst has quit IRC23:11
*** marst has joined #openstack-meeting-alt23:11
*** beslemon has quit IRC23:12
*** jamielennox is now known as jamielennox|away23:15
*** dizquierdo has quit IRC23:18
*** iyamahat has joined #openstack-meeting-alt23:18
*** jamielennox|away is now known as jamielennox23:20
*** marst has quit IRC23:21
*** annegentle has joined #openstack-meeting-alt23:21
*** spzala has quit IRC23:22
*** annegentle has quit IRC23:22
*** EricGonczer_ has quit IRC23:24
*** EricGonczer_ has joined #openstack-meeting-alt23:25
*** EricGonczer_ has quit IRC23:29
*** edleafe has quit IRC23:30
*** edleafe has joined #openstack-meeting-alt23:30
*** jrobinson has joined #openstack-meeting-alt23:30
*** jtomasek has quit IRC23:31
*** ihrachys has joined #openstack-meeting-alt23:31
*** ansmith has quit IRC23:32
*** rwsu has quit IRC23:33
*** dizquierdo has joined #openstack-meeting-alt23:34
*** edleafe has quit IRC23:34
*** jtomasek has joined #openstack-meeting-alt23:35
*** ihrachys has quit IRC23:36
*** Swami has quit IRC23:36
*** edleafe has joined #openstack-meeting-alt23:37
*** edleafe has quit IRC23:37
*** cknight has quit IRC23:39
*** edleafe has joined #openstack-meeting-alt23:40
*** fzdarsky|afk has quit IRC23:42
*** dimtruck is now known as zz_dimtruck23:42
*** zz_dimtruck is now known as dimtruck23:42
*** rerobot is now known as redrobot23:43
*** fnaval has quit IRC23:44
*** tonanhngo has quit IRC23:48
*** Swami has joined #openstack-meeting-alt23:49
*** spzala has joined #openstack-meeting-alt23:52
*** edleafe has quit IRC23:54
*** tonanhngo has joined #openstack-meeting-alt23:55
*** spzala has quit IRC23:56
*** edleafe has joined #openstack-meeting-alt23:57
*** tonanhngo has quit IRC23:59

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