Monday, 2017-04-17

*** funzo has joined #openstack-meeting-alt00:09
*** ircuser-1 has quit IRC00:12
*** funzo has quit IRC00:13
*** zz_dimtruck is now known as dimtruck00:16
*** fnaval_ has joined #openstack-meeting-alt00:24
*** fnaval has quit IRC00:27
*** amotoki has joined #openstack-meeting-alt00:35
*** dave-mccowan has quit IRC00:39
*** zhurong has joined #openstack-meeting-alt00:41
*** fnaval_ has quit IRC00:43
*** tuanluong has joined #openstack-meeting-alt00:44
*** fnaval has joined #openstack-meeting-alt00:44
*** yamahata has joined #openstack-meeting-alt00:45
*** tovin07_ has joined #openstack-meeting-alt00:47
*** baoli has joined #openstack-meeting-alt00:48
*** fnaval_ has joined #openstack-meeting-alt00:49
*** fnaval has quit IRC00:52
*** tonanhngo has joined #openstack-meeting-alt01:00
*** tonanhngo has quit IRC01:01
*** diablo_rojo has joined #openstack-meeting-alt01:03
*** funzo has joined #openstack-meeting-alt01:10
*** funzo has quit IRC01:14
*** gcb has joined #openstack-meeting-alt01:16
*** Kuwagata has joined #openstack-meeting-alt01:18
*** shuyingya has joined #openstack-meeting-alt01:18
*** Kuwagata has quit IRC01:22
*** zhurong has quit IRC01:30
*** shuyingy_ has joined #openstack-meeting-alt01:37
*** shuyingya has quit IRC01:37
*** fnaval_ has quit IRC01:38
*** fnaval has joined #openstack-meeting-alt01:41
*** tonanhngo has joined #openstack-meeting-alt01:42
*** tonanhngo has quit IRC01:42
*** amotoki has quit IRC01:42
*** amotoki has joined #openstack-meeting-alt01:43
*** fnaval has quit IRC01:43
*** fnaval has joined #openstack-meeting-alt01:43
*** yamamoto has joined #openstack-meeting-alt01:45
*** amotoki has quit IRC01:47
*** reedip_ has joined #openstack-meeting-alt01:50
*** amotoki has joined #openstack-meeting-alt01:54
*** tovin07 has joined #openstack-meeting-alt01:59
*** shuyingy_ has quit IRC02:02
*** shuyingya has joined #openstack-meeting-alt02:02
*** zhurong has joined #openstack-meeting-alt02:03
*** gongysh has joined #openstack-meeting-alt02:03
*** Zhongjun__ is now known as Zhongjun02:05
*** Zhongjun is now known as zhongjun02:05
*** shuyingy_ has joined #openstack-meeting-alt02:11
*** shuyingya has quit IRC02:11
*** cknight has quit IRC02:13
*** gcb has quit IRC02:23
*** yamamoto has quit IRC02:23
*** yamamoto has joined #openstack-meeting-alt02:30
*** reedip_ has quit IRC02:36
*** chyka has joined #openstack-meeting-alt02:36
*** gcb has joined #openstack-meeting-alt02:37
*** chyka has quit IRC02:38
*** reedip_ has joined #openstack-meeting-alt02:43
*** tonanhngo has joined #openstack-meeting-alt02:44
*** tonanhngo has quit IRC02:44
*** shu-mutou-AWAY is now known as shu-mutou02:44
*** reedip_ has quit IRC02:52
*** hongbin has joined #openstack-meeting-alt02:52
*** baoli has quit IRC02:53
*** yamamoto has quit IRC02:56
*** amotoki has quit IRC02:58
*** amotoki has joined #openstack-meeting-alt03:00
*** ijw has joined #openstack-meeting-alt03:00
*** ijw has quit IRC03:04
*** ijw has joined #openstack-meeting-alt03:04
*** ijw_ has joined #openstack-meeting-alt03:05
*** ijw has quit IRC03:08
*** pgadiya has joined #openstack-meeting-alt03:10
*** funzo has joined #openstack-meeting-alt03:11
*** amotoki has quit IRC03:11
*** caowei has joined #openstack-meeting-alt03:14
*** funzo has quit IRC03:15
*** ijw has joined #openstack-meeting-alt03:16
*** Kuwagata has joined #openstack-meeting-alt03:19
*** ijw_ has quit IRC03:19
*** amotoki has joined #openstack-meeting-alt03:23
*** Kuwagata has quit IRC03:23
*** david-lyle has quit IRC03:42
*** amotoki_ has joined #openstack-meeting-alt03:43
*** yamamoto has joined #openstack-meeting-alt03:45
*** tonanhngo has joined #openstack-meeting-alt03:45
*** tonanhngo has quit IRC03:46
*** amotoki has quit IRC03:46
*** tovin07 has quit IRC03:50
*** amotoki_ has quit IRC03:53
*** amotoki has joined #openstack-meeting-alt03:53
*** ijw has quit IRC03:58
*** zhurong has quit IRC03:59
*** ijw has joined #openstack-meeting-alt04:01
*** ijw_ has joined #openstack-meeting-alt04:01
*** gouthamr has quit IRC04:02
*** ijw__ has joined #openstack-meeting-alt04:03
*** ijw has quit IRC04:05
*** ijw_ has quit IRC04:06
*** houming has joined #openstack-meeting-alt04:07
*** houming has quit IRC04:07
*** funzo has joined #openstack-meeting-alt04:11
*** funzo has quit IRC04:16
*** zhurong has joined #openstack-meeting-alt04:20
*** hongbin has quit IRC04:20
*** trinaths has joined #openstack-meeting-alt04:23
*** anilvenkata has joined #openstack-meeting-alt04:35
*** chhavi has joined #openstack-meeting-alt04:42
*** adisky_ has joined #openstack-meeting-alt04:45
*** nadya has joined #openstack-meeting-alt04:55
*** caowei has quit IRC05:06
*** diablo_rojo has quit IRC05:06
*** rcernin has joined #openstack-meeting-alt05:12
*** links has joined #openstack-meeting-alt05:12
*** funzo has joined #openstack-meeting-alt05:12
*** funzo has quit IRC05:17
*** sridharg has joined #openstack-meeting-alt05:18
*** Kuwagata has joined #openstack-meeting-alt05:20
*** Kuwagata has quit IRC05:24
*** tamilhce has joined #openstack-meeting-alt05:26
*** tamilhce has quit IRC05:26
*** pgadiya has quit IRC05:28
*** nadya has quit IRC05:30
*** tamilhce has joined #openstack-meeting-alt05:30
*** tamilhce has quit IRC05:41
*** yamahata has quit IRC05:43
*** caowei has joined #openstack-meeting-alt05:47
*** vds has joined #openstack-meeting-alt05:54
*** nadya has joined #openstack-meeting-alt05:57
*** kzaitsev_ws has joined #openstack-meeting-alt06:08
*** sridharg has quit IRC06:16
*** janki has joined #openstack-meeting-alt06:17
*** JudeC has joined #openstack-meeting-alt06:20
*** links has quit IRC06:21
*** JudeC has quit IRC06:22
*** amotoki has quit IRC06:30
*** nadya has quit IRC06:30
*** tuanluong has quit IRC06:30
*** amotoki has joined #openstack-meeting-alt06:35
*** shuyingya has joined #openstack-meeting-alt06:45
*** shuyingy_ has quit IRC06:45
*** amotoki has quit IRC06:47
*** amotoki has joined #openstack-meeting-alt06:52
*** amotoki_ has joined #openstack-meeting-alt06:55
*** rarcea has joined #openstack-meeting-alt06:56
*** amotoki has quit IRC06:58
*** tesseract has joined #openstack-meeting-alt07:01
*** ijw has joined #openstack-meeting-alt07:03
*** ijw_ has joined #openstack-meeting-alt07:06
*** ijw__ has quit IRC07:07
*** ijw_ has quit IRC07:07
*** ijw has quit IRC07:08
*** funzo has joined #openstack-meeting-alt07:14
*** mickeys has quit IRC07:18
*** funzo has quit IRC07:18
*** Kuwagata has joined #openstack-meeting-alt07:20
*** Kuwagata has quit IRC07:25
*** egallen has joined #openstack-meeting-alt07:30
*** yonglihe has joined #openstack-meeting-alt07:40
*** eliqiao has joined #openstack-meeting-alt07:41
*** heyongli has joined #openstack-meeting-alt07:48
*** dizquierdo has joined #openstack-meeting-alt07:50
*** sridharg has joined #openstack-meeting-alt07:56
*** nadya has joined #openstack-meeting-alt07:56
*** nadya has quit IRC08:02
*** nadya has joined #openstack-meeting-alt08:02
*** funzo has joined #openstack-meeting-alt08:14
*** alexchadin has joined #openstack-meeting-alt08:18
*** mickeys has joined #openstack-meeting-alt08:19
*** funzo has quit IRC08:19
*** jtomasek has joined #openstack-meeting-alt08:21
*** mickeys has quit IRC08:23
*** dsariel has joined #openstack-meeting-alt08:33
*** jchhatbar has joined #openstack-meeting-alt08:38
*** janki has quit IRC08:41
*** rcernin has quit IRC08:45
*** rcernin has joined #openstack-meeting-alt08:48
*** zhurong has quit IRC08:54
*** jchhatbar_ has joined #openstack-meeting-alt08:59
*** rcernin has quit IRC08:59
*** rcernin has joined #openstack-meeting-alt08:59
*** cloudrancher has quit IRC09:01
*** jchhatbar has quit IRC09:02
*** amotoki_ has quit IRC09:04
*** r-mibu has quit IRC09:07
*** egallen_ has joined #openstack-meeting-alt09:09
*** egallen has quit IRC09:09
*** egallen_ is now known as egallen09:09
*** kzaitsev_ws has quit IRC09:11
*** kzaitsev_ws has joined #openstack-meeting-alt09:11
*** amotoki has joined #openstack-meeting-alt09:11
*** r-mibu has joined #openstack-meeting-alt09:12
*** tuanluong has joined #openstack-meeting-alt09:14
*** jtomasek has quit IRC09:15
*** funzo has joined #openstack-meeting-alt09:15
*** amotoki has quit IRC09:19
*** mickeys has joined #openstack-meeting-alt09:20
*** funzo has quit IRC09:20
*** egallen has quit IRC09:21
*** Kuwagata has joined #openstack-meeting-alt09:21
*** eliqiao has quit IRC09:21
*** egallen has joined #openstack-meeting-alt09:22
*** mickeys has quit IRC09:24
*** amotoki has joined #openstack-meeting-alt09:24
*** Kuwagata has quit IRC09:25
*** egallen has quit IRC09:27
*** pgadiya has joined #openstack-meeting-alt09:29
*** egallen has joined #openstack-meeting-alt09:29
*** alexchad_ has joined #openstack-meeting-alt09:31
*** alexchadin has quit IRC09:33
*** dalgaaf has quit IRC09:40
*** dalgaaf has joined #openstack-meeting-alt09:40
*** alexchad_ is now known as alexchadin09:43
*** dizquierdo has quit IRC09:45
*** ralonsoh has joined #openstack-meeting-alt09:46
*** amotoki has quit IRC09:48
*** pgadiya has quit IRC09:56
*** lhinds has quit IRC09:56
*** gchamoul has quit IRC09:57
*** rnoriega has quit IRC09:57
*** myoung has quit IRC09:57
*** nadya has quit IRC09:59
*** rnoriega has joined #openstack-meeting-alt10:03
*** myoung has joined #openstack-meeting-alt10:03
*** gchamoul has joined #openstack-meeting-alt10:04
*** lhinds has joined #openstack-meeting-alt10:05
*** tovin07_ has quit IRC10:05
*** cloudrancher has joined #openstack-meeting-alt10:07
*** cloudrancher has quit IRC10:12
*** alexchadin has quit IRC10:15
*** funzo has joined #openstack-meeting-alt10:16
*** cloudrancher has joined #openstack-meeting-alt10:17
*** funzo has quit IRC10:20
*** mickeys has joined #openstack-meeting-alt10:21
*** shu-mutou is now known as shu-mutou-AWAY10:25
*** cloudrancher has quit IRC10:25
*** mickeys has quit IRC10:26
*** kobis has quit IRC10:26
*** nadya has joined #openstack-meeting-alt10:29
*** jchhatbar has joined #openstack-meeting-alt10:31
*** vds has quit IRC10:32
*** jchhatbar_ has quit IRC10:33
*** tuanluong has quit IRC10:33
*** jchhatbar_ has joined #openstack-meeting-alt10:34
*** jkilpatr has quit IRC10:36
*** jchhatbar has quit IRC10:36
*** nadya has quit IRC10:42
*** nadya has joined #openstack-meeting-alt10:42
*** janki has joined #openstack-meeting-alt10:42
*** jchhatbar_ has quit IRC10:42
*** HeOS has joined #openstack-meeting-alt10:45
*** jchhatbar has joined #openstack-meeting-alt10:46
*** ganso has joined #openstack-meeting-alt10:48
*** janki has quit IRC10:48
*** zhurong has joined #openstack-meeting-alt10:50
*** jkilpatr has joined #openstack-meeting-alt10:52
*** sdague has joined #openstack-meeting-alt10:58
*** chhavi has quit IRC11:01
*** caowei has quit IRC11:02
*** zhurong has quit IRC11:05
*** gongysh has quit IRC11:05
*** zhurong has joined #openstack-meeting-alt11:10
*** dave-mccowan has joined #openstack-meeting-alt11:10
*** rcernin has quit IRC11:14
*** trinaths has left #openstack-meeting-alt11:16
*** funzo has joined #openstack-meeting-alt11:17
*** thrash|g0ne is now known as thrash11:21
*** funzo has quit IRC11:22
*** Kuwagata has joined #openstack-meeting-alt11:22
*** reedip is now known as reedip_afk11:26
*** Kuwagata has quit IRC11:26
*** rcernin has joined #openstack-meeting-alt11:29
*** jchhatbar has quit IRC11:32
*** jchhatbar has joined #openstack-meeting-alt11:33
*** tkelsey has joined #openstack-meeting-alt11:46
*** tkelsey has quit IRC11:47
*** dprince has joined #openstack-meeting-alt11:55
*** rfolco has joined #openstack-meeting-alt12:08
*** dsariel has quit IRC12:11
*** mickeys_ has joined #openstack-meeting-alt12:12
*** alexchadin has joined #openstack-meeting-alt12:13
*** mickeys_ has quit IRC12:16
*** funzo has joined #openstack-meeting-alt12:18
*** funzo_ has joined #openstack-meeting-alt12:20
*** funzo has quit IRC12:20
*** iceyao_ has joined #openstack-meeting-alt12:22
*** zhurong has quit IRC12:24
*** gouthamr has joined #openstack-meeting-alt12:25
*** ansmith has joined #openstack-meeting-alt12:28
*** rarcea has quit IRC12:28
*** iceyao_ has quit IRC12:37
*** shuyingya has quit IRC12:45
*** tellesnobrega has joined #openstack-meeting-alt12:45
*** shuyingya has joined #openstack-meeting-alt12:45
*** shuyingya has quit IRC12:50
*** mikal has quit IRC12:50
*** mikal has joined #openstack-meeting-alt13:00
*** xyang1 has joined #openstack-meeting-alt13:00
*** jianghuaw_ has joined #openstack-meeting-alt13:02
*** baoli has joined #openstack-meeting-alt13:03
*** dustins has joined #openstack-meeting-alt13:08
*** jaypipes has joined #openstack-meeting-alt13:09
*** shuyingya has joined #openstack-meeting-alt13:10
*** vds has joined #openstack-meeting-alt13:15
*** gcb has quit IRC13:16
*** EricGonczer_ has joined #openstack-meeting-alt13:19
*** mariannelm has joined #openstack-meeting-alt13:19
*** haleyb has joined #openstack-meeting-alt13:21
*** dizquierdo has joined #openstack-meeting-alt13:21
*** egallen has quit IRC13:22
*** egallen has joined #openstack-meeting-alt13:22
*** egallen has quit IRC13:23
*** Kuwagata has joined #openstack-meeting-alt13:23
*** shuyingy_ has joined #openstack-meeting-alt13:24
*** felipemonteiro has joined #openstack-meeting-alt13:25
*** kobis has joined #openstack-meeting-alt13:25
*** shuyingya has quit IRC13:27
*** Kuwagata has quit IRC13:28
*** ralonsoh has quit IRC13:30
*** karthiks has quit IRC13:35
*** gcb has joined #openstack-meeting-alt13:35
*** kobis has quit IRC13:38
*** mriedem has joined #openstack-meeting-alt13:45
*** dave-mccowan has quit IRC13:46
*** dave-mccowan has joined #openstack-meeting-alt13:47
*** dimtruck is now known as zz_dimtruck13:53
*** lei-zh has joined #openstack-meeting-alt13:56
*** nadya has quit IRC13:56
*** cdent has joined #openstack-meeting-alt14:00
cdentare we having a scheduler meeting or are we calling it a holiday?14:01
edleafe#startmeeting nova_scheduler14:01
openstackMeeting started Mon Apr 17 14:01:21 2017 UTC and is due to finish in 60 minutes.  The chair is edleafe. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: nova_scheduler)"14:01
openstackThe meeting name has been set to 'nova_scheduler'14:01
mriedemo/14:01
cdentI'll take that as a yes14:01
edleafeSorry, I was making coffee :)14:01
alex_xuo/14:01
jaypipeso/14:01
* jaypipes also making coffee...14:02
lei-zho/14:02
edleafe#topic Specs & Reviews14:03
*** openstack changes topic to "Specs & Reviews (Meeting topic: nova_scheduler)"14:03
*** hongbin has joined #openstack-meeting-alt14:03
edleafeGood to see that the Traits stuff has merged \o/14:03
edleafeStill one bit left:14:03
edleafe#link os-traits sync to DB https://review.openstack.org/#/c/450125/14:03
jaypipesedleafe: I think the claims one is the biggie.14:03
alex_xu\o/14:03
jaypipesedleafe: as far as specs go.14:03
mriedemclaims is the only scheduler related spec outstanding that i care about at this point14:04
edleafejaypipes: yep, getting to that14:04
*** alexchadin has quit IRC14:04
*** gcb has quit IRC14:04
edleafeAlso some work on adding to os-traits, and re-organizing14:04
edleafeos-traits14:04
edleafe#link os-traits reorg: https://review.openstack.org/#/c/448282/14:04
edleafeIf there's nothing about any of those, we can move on to the claims stuff14:05
edleafeok then14:06
*** diga has joined #openstack-meeting-alt14:06
edleafe#link WIP placement doing claims: https://review.openstack.org/43742414:06
edleafe#link Forum session proposed for claims in the scheduler: http://forumtopics.openstack.org/cfp/details/6314:06
edleafeSo let14:06
edleafeugh14:06
edleafelet's talk about claims14:06
*** ganso has left #openstack-meeting-alt14:06
jaypipesworst 80s song ever.14:08
mriedemi haven't looked at the latest since our hangout14:08
mriedemjaypipes: salt n pepa were pressured by their management to do it anyway14:08
jaypipesmriedem: cdent has concerns about sending the allocation list object over RPC. to summarize, he believes it is better/simpler to just have the compute node do GET /allocations14:08
*** zz_dimtruck is now known as dimtruck14:09
mriedemand of course i can't find the etherpad from the hangout session now14:09
edleafeFor me it's not a concern about load or reliability as much as it seems to go against the design14:09
mriedemso conductor would PUT the allocations, compute would GET the allocations and if they don't exist yet, compute does the old style thing, right?14:10
mriedemis the idea14:10
jaypipesmriedem: right.14:10
mriedemwhereas,14:10
mriedemif conductor passed the allocations to compute, compute can just key off that to know if it needs to do the old style thing14:11
*** gcb has joined #openstack-meeting-alt14:11
jaypipesmriedem: and frankly, I agree with edleafe and cdent that the PUT then GET is cleaner.14:11
*** fnaval has quit IRC14:11
jaypipesmriedem: yes, but passing allocations to compute introduces significantly more complexity to the code.14:11
cdentmriedem: the "can just key off" part is the part that's concerning/misleading. the behavior is not complex, but the code changes and commitments are14:11
mriedemyeah i agree it's cleaner, it's a bit redundant, and it takes some control away from the controller layer, which is something dansmith mentioned when we talked about it14:11
jaypipesmriedem: mostly because we will now need to use versioned objects for the communication14:11
mriedemjaypipes: why?14:12
mriedemwe said we weren't going to stuff the allocations in the request spec14:12
jaypipesmriedem: we still would send the AllocationList as a param over RPC, no?14:12
mriedemyes14:12
jaypipesmriedem: so therefore that param would need to be an ovo, no?14:13
mriedemyes14:13
mriedemwell, doesn't need to be, but it would be14:13
dansmithand those ovo definitions are "owned" by placement,14:13
mriedemto link back to the resource provider object14:13
dansmithwhich is to be kicked out14:13
jaypipesmriedem: and we don't use versioned objects for placement/resource providers stuff on the compute node.14:13
mriedemdansmith: so you've come around to the idea of pulling the allocations from the compute rather than pushing them there?14:14
dansmithmriedem: I don't need to come around, I was saying there are good attributes about both approaches14:14
mriedemto be clear, i'm fine with the compute pulling them14:14
mriedemi think we mostly picked a side during the hangout because we were ratholing14:14
mriedemand needed to move on14:14
jaypipestru14:14
mriedembut yeah keeping the placement objects out of nova would be great14:15
mriedemand then the compute is just another client working with the dict responses14:15
*** dizquierdo has quit IRC14:15
mriedemanyone have that etherpad link handy?14:16
jaypipeshttps://etherpad.openstack.org/p/nova-pike-claims-in-scheduler14:16
* edleafe was too slow14:17
jaypipesmriedem: see line 37 :)14:17
mriedemone question in there was, "The compute could fail the HTTP call to Placement and then what do we do?"14:17
cdentisn't that the same as "the RPC call could fail and then what?"14:18
jaypipesmriedem: if the compute can reach the conductor, then set the instance to ERROR, I would say.14:18
mriedemjaypipes: it can't in multi-cell with super conductor14:18
mriedemcdent: good point14:18
jaypipesmriedem: why not?14:19
mriedemcdent: in that case, we delete the allocations when we delete the instance, or whatever hand wavey thing we said we'd do about cleaning up allocations14:19
*** EricGonczer_ has quit IRC14:19
mriedemjaypipes: that's the same as the retry issue,14:19
mriedemwith super-conductor the compute can't rpc cast back to conductor to retry a build14:19
jaypipesmriedem: wouldn't it call Instance.save(), which would communicate with the local conductor and set the instance's vm_state to ERROR... we could have the audit job look for an ERROR'd instances and dselete allocations from placement.14:20
mriedemso once we claim and pick a host, it builds on that host or fails14:20
mriedemi was thinking we put the instance in ERROR state yeah14:20
mriedembut,14:20
mriedemhow do we know the GET /allocations fail is a new style thing and not the old style fallback, maybe that does'nt matter14:20
mriedemi.e. how does the compute know allocations have already been made for it?14:21
mriedemso it should error if it can't get them14:21
jaypipesmriedem: well there's a difference between not getting allocations from the placement API and not being able to communicate with the placement API...14:22
*** EricGonczer_ has joined #openstack-meeting-alt14:22
jaypipesmriedem: in the former case, the compute would just proceed with its local claim process as normal. in the latter, it would set the instance to ERROR.14:22
mriedemmight be overthinking this of course, if we assume the control plane is upgraded before computes and it's making allocations for the compute, then we wouldn't have any fallback in the compute if GET /allocations fails14:22
jaypipesmriedem: assuming it can contact the local conductor of course.14:22
mriedem*fails or is an empty response14:22
mriedemjaypipes: but i'm not sure it should proceed with the local claim process14:23
mriedemis what i'm getting at14:23
jaypipesmriedem: well, a 404 is perfectly valid, right?14:23
mriedembecause we could then be double-claiming14:23
mriedemright?14:23
jaypipesmriedem: if it gets a 404, that means "hey, not all compute nodes are upgraded to understand the new claims in placement yet, so I should proceed as per the old way"14:23
edleafeGET /allocations/{instance_id} should return an empty list if there aren't any14:24
mriedemyes that would be true if you have ocata computes and conductor isn't claiming yet14:24
edleafeNOt 40414:24
jaypipesedleafe: if there's been no allocations for an instance, it returns an empty list?14:25
edleafeThat's what I thought. cdent?14:25
mriedemi'm asking about the case that all computes are pike, conductor is claiming, and the compute does a GET /allocations/{instance_id} and it's empty or 404, then what? i'm thinking we just put the instance into error state - but how to know if we should do that is tricky14:25
* edleafe is rebuilding his laptop and currently without his dev environment14:25
*** mdong_ has joined #openstack-meeting-alt14:26
mriedemgranted, it shouldn't be empty or 40414:26
*** dprince has quit IRC14:26
jaypipesmriedem: why would you put the instance into error state instead of just trying the local claim?14:26
mriedemjaypipes: because then you are double claiming14:26
edleafemriedem: how is that possible?14:26
cdentsorry, my network is being very lame14:26
edleafeif there are allocations against that instance, how could it return an empty list?14:26
mriedemwould the local claim just overwrite the existing allocations that conductor created?14:27
cdentget allocations for consumer returns an empty result, not a 40414:27
jaypipescdent: ok14:27
edleafeAnd if there are allocations, but the compute gets back an empty list, we have much bigger problems14:27
mriedemedleafe: i agree with that14:27
jaypipesmriedem: I think for at least one release, we should have the compute node try the old local claim process.14:27
jaypipesmriedem: and then remove all that code in, say "R".14:28
edleafejaypipes: that sounds reasonable14:28
jaypipesmriedem: after removing that code, the default brhaviour would be put in error state.14:28
*** dizquierdo has joined #openstack-meeting-alt14:28
mriedemdoes anyone know if the local claim would overwrite the existing allocations? or is there a generation id or something that would make that a conflict?14:28
jaypipesmriedem: checking, one sec.14:29
jaypipesmriedem: pretty sure there is a check, but hold up.14:29
edleafeit's a PUT, right?14:29
* edleafe feels extra dumb without code available14:30
jaypipesmriedem: the AllocationList.set_allocations() would fail with a ConcurrentUpdateDetected and return a 409 to the client.14:30
cdentiirc: when we set allocations we don't check any generation that is provided, but we do check the generation internally14:30
cdentjaypipes: you looking at set_allocations in the handler code?14:31
jaypipescdent: the rp.generation(s) are passed to the placement REST API./14:31
* cdent re-looks14:31
cdentjaypipes: look at the gabbits14:31
jaypipessigh14:32
cdentthis is something we talked about way back then, and for some reason decided it wasn't necessary14:32
alex_xuI thought the scheduler will upgrade first, and after compute node upgrade also, why the upgrade compute node needs to fallback to old claim?14:32
mriedemalex_xu: conductor will only do the new style claim if all computes are upgraded14:32
*** annegentle has joined #openstack-meeting-alt14:33
mriedembecause ocata computes would always be doing a local claim14:33
alex_xumriedem: ah, yea, right14:33
jaypipeswhy on earth didn't we include rp.generation in the request payload... :(14:33
cdentfor reference14:34
cdent#link allocations with no gen: https://github.com/openstack/nova/blob/05a25d7e2a6aa9d5eb7327c91509178f95186e17/nova/tests/functional/api/openstack/placement/gabbits/allocations.yaml#L13614:34
mriedemjaypipes: cdent: so i think it's reasonable to assume that if conductor makes the allocations, compute should be able to get them, and if for whatever reason it doesn't, then it does the local claim which could try and do it's own PUT /allocations - if that failed with a 409, then idk, error?14:34
jaypipesthat really should be added.14:34
jaypipesmriedem: yes.14:34
jaypipescdent: that's really a bug. I'll log one and fix it.14:34
*** mickeys has joined #openstack-meeting-alt14:34
mriedemwe'll sort out weirdo edge cases once we start rolling out code i guess14:35
mriedemso to summarize:14:35
jaypipesk14:35
cdentjaypipes: okay, but I wish I could remember what you told me when I questioned it in the first place, because that would be useful context14:35
mriedem1. conductor won't do anything until all computes are upgraded,14:35
mriedem2. once all computes are upgraded, conductor makes the claim (creates allocations)14:35
jaypipescdent: all I remember is rejecting the original request payload that had the allocations structured as a dict keyed by rp.uuid, saying that we may need other fields in the resource provider object in the future.14:35
mriedem3. conductor doesn't pass anything to compute during build, the compute will look for allocations and if they exist, it doesn't do a local claim, otherwise it attempts to (for a release or two)14:36
*** rcernin has quit IRC14:36
jaypipesmriedem: yes, ++14:36
mriedem4. when we hit some crazy edge case we didn't anticipate with ironic, we'll hack a fix as usual14:37
jaypipescdent: more than likely we said "well, generation doesn't matter until we're doing claims in the scheduler" and left it out.14:37
edleafeCan anyone remind me why we have conductor doing the claim and not the scheduler?14:37
cdentmriedem: step 4 is like steps 4-math.inf14:37
jaypipescdent: since right now, the compute node holds a semaphore on the compute node record and therefore there's no danger of concurrent updates.14:37
cdentjaypipes: perhaps. I guess we just fix it and that's fine.14:38
jaypipesya14:38
mriedemedleafe: i can't remember exactly14:38
edleafeIt would seem that if there was a race and the claim failed, the scheduler could move to its next choice and try claiming that14:38
mriedemedleafe: as could conductor14:38
*** mickeys has quit IRC14:39
mriedemdansmith: do you remember why we said conductor would create the allocations rather than scheduler?14:39
dansmithmriedem: because that's where we do that kind of thing14:39
edleafemriedem: conductor doesn't have the list of filtered/weighed hosts14:39
mriedemedleafe: yes it does14:39
mriedembut i'll check for sure14:40
edleafemriedem: if conductor claim fails, it has to re-do the whole scheduler filter/weigh process all over again14:40
mriedemhttps://github.com/openstack/nova/blob/master/nova/conductor/manager.py#L91414:40
dansmithmriedem: not sure why we'd want the scheduler doing that14:40
*** kobis has joined #openstack-meeting-alt14:40
*** nadya has joined #openstack-meeting-alt14:41
mriedemedleafe: if i'm reading that correctly, conductor has a list of filtered and weighed hosts14:41
jaypipes#link https://bugs.launchpad.net/nova/+bug/168337714:41
openstackLaunchpad bug 1683377 in OpenStack Compute (nova) "[placement] PUT /allocations should include resource provider generations" [Medium,Triaged] - Assigned to Jay Pipes (jaypipes)14:41
jaypipesmriedem: the reason we said conductor instead of scheduler was because conductor handles retries.14:42
edleafemriedem: no, the scheduler gets that list from placement, runs its additional filters, sorts, and returns its one selected host14:42
mriedemedleafe: so you're saying the "hosts" variable here is a single entry? https://github.com/openstack/nova/blob/master/nova/conductor/manager.py#L63814:42
dansmithmriedem: it is if we have subset =114:43
dansmither, subset_size=114:43
edleafemriedem: it can be more than one if we are building several VMs at once14:43
dansmithIIRC14:43
edleafemriedem: https://github.com/openstack/nova/blob/master/nova/scheduler/filter_scheduler.py#L10214:43
edleafedansmith: isn't it spec_obj.num_instances?14:44
*** diablo_rojo has joined #openstack-meeting-alt14:44
dansmithedleafe: I think subset_size also means we get back more than one, right? maybe that is stripped off before that..14:44
*** rcernin has joined #openstack-meeting-alt14:44
dansmithedleafe: we need at least num_instances there, yes14:44
edleafedansmith: that's a trick we use to reduce races14:44
edleafewe pick a random host from the top N, where N == subset_size14:45
edleafethat could go away if the scheduler could claim directly14:45
*** beslemon has joined #openstack-meeting-alt14:46
mriedemok so i thought conductor had the list of possible hosts to build a single instance, i guess that was wrong14:47
mriedemif the claim in conductor fails, is it worth it to redo the host filtering in the scheduler anyway?14:47
mriedemit could be expensive if nothing else changed but that one host you hit14:48
edleafemriedem: yeah, it would be expensive14:48
edleafegetting the list of hosts is better now that we do some weeding out in the placement call14:48
edleafebut it's still wasteful to repeat if not needed14:48
*** ijw has joined #openstack-meeting-alt14:49
edleafeIf the scheduler were to make the claim, the flow when a race happens would look like:14:49
edleafeScheduler has a list of acceptable hosts. Makes claim - if it fails, move on to #2, then #3.14:49
edleafeIf it succeeds... PROFIT!14:50
mriedemyes that's what i originally expected, but i thought conductor could do the same, but i guess not14:50
edleafeThe original idea was to have the scheduler do it14:51
edleafeThe spec's commit message even says that14:51
edleafe"Proposal to have scheduler posting allocations instead of computes"14:51
edleafeSomewhere it got changed, and I couldn't remember the reason14:52
mriedemdoing claims in the conductor makes things work for caching scheduler too...but we want to deprecate that after claims in controller, and even if only the filter scheduler did the claim, the computes would have the fallback14:52
mriedemi think the thinking changed during the hangout14:52
*** fnaval has joined #openstack-meeting-alt14:52
mriedemwhen dansmith said it would be conductor making the claim14:52
mriedembut as noted, i thought conductor had the list of filtered hosts14:52
dansmithedleafe: speaking for me at least, I always meant "claims in the scheduling phase" when we said that14:52
edleafeFYI: 8 minutes left14:52
edleafedansmith: ok, but is there a reason why it needs to be in the conductor?14:53
mriedemi'd like to not have to get the hosts again and filter them if the claim on the first one fails14:53
mriedemespecially since that could happen with packing right?14:53
dansmithedleafe: well, I'm not sure it makes as much sense if we made the scheduler a library, but maybe14:53
mriedemtoday we deal with packing conflicts with retries, which we won't have with super-conductor and claims in the scheduler/conductor14:54
dansmithedleafe: however, it also puts a blocking http call in the middle of a single-threaded thing14:54
dansmithmriedem: the claim would fail because something has changed anyway, right? why wouldn't we reschedule to get a freshened idea of the world?14:54
mriedemdansmith: that's what i said above,14:55
dansmithyeah14:55
mriedemi.e. is it a good idea to redo the scheduling anyway14:55
jaypipesmriedem: dansmith is correct. we don't eliminate retries. we eliminate retries *happening from the compute nodes*.14:55
dansmithright14:55
edleafedansmith: in a typical race where there are two requests for essentially the same VM, the only thing that changed is the first one used up some of the host14:55
dansmithmuch faster turnaround14:55
*** gcb has quit IRC14:56
mriedemedleafe: but if that host still has some inventory, the 2nd claim might still fit right?14:56
mriedemand if it doesn't, then that host is out of the running for that vm and we need to find another host14:56
edleafeSure, in which case it would succeed14:56
edleafeWe're talking about where the second one fails14:56
edleafeIn that case, it's best to pick host #2 from its weighed list14:56
alex_xujaypipes: we will move that retries inside placement in the future, right? when we can claim directly14:56
jaypipesalex_xu: possibly, yes. but we're a ways away from the placement service having all the required information in order to make that full determination.14:57
*** lei-zh has quit IRC14:57
edleafeI'm doing a terrible job of time boxing14:57
edleafeBut this is an important discussion14:57
edleafeWe can continue it in -nova in 2 minutes14:58
*** markstur has joined #openstack-meeting-alt14:58
edleafe#topic Opens14:58
*** openstack changes topic to "Opens (Meeting topic: nova_scheduler)"14:58
mriedemreally without some poc code both ways with performance testing of collisions it's hard to make a decision on this14:58
edleafeAnyone want to add something before we adjourn?14:58
*** yamahata has joined #openstack-meeting-alt14:58
mriedeme.g. with 1000 nodes,14:58
* edleafe feels bad for anyone who hung around waiting for Open discussion14:59
*** annegentle has quit IRC14:59
mriedemhow long does it take to get the filtered / weighed list of hosts14:59
*** ihrachys has joined #openstack-meeting-alt14:59
mriedembecause that's how long it's going to take per retry if we fail to claim in conductor14:59
edleafeOK, we have to move this to -nova now15:00
edleafe#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:00
openstackMeeting ended Mon Apr 17 15:00:04 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_scheduler/2017/nova_scheduler.2017-04-17-14.01.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_scheduler/2017/nova_scheduler.2017-04-17-14.01.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_scheduler/2017/nova_scheduler.2017-04-17-14.01.log.html15:00
*** annegentle has joined #openstack-meeting-alt15:00
ihrachysanyone present for the neutron upgrades meeting?15:00
*** cdent has left #openstack-meeting-alt15:01
*** dizquierdo has quit IRC15:01
*** mdong__ has joined #openstack-meeting-alt15:01
*** jchhatbar has quit IRC15:01
ihrachysdoesn't seem like it, but I will hold for another 2 minutes before bailing out of the channel.15:02
*** mdong_ has quit IRC15:02
ihrachysafter late OSIC layoff, we may not have decent presentation for the meeting to make it worth it, so I will also consider killing the meeting if we can't hold one for like two weeks.15:02
manjeetso/15:03
ihrachysmanjeets, hi!15:03
ihrachysnow we are two15:03
ihrachysok let's hold one very very quick for logging purposes if nothing else15:04
ihrachys#startmeeting neutron_upgrades15:04
openstackMeeting started Mon Apr 17 15:04:28 2017 UTC and is due to finish in 60 minutes.  The chair is ihrachys. Information about MeetBot at http://wiki.debian.org/MeetBot.15:04
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:04
*** openstack changes topic to " (Meeting topic: neutron_upgrades)"15:04
openstackThe meeting name has been set to 'neutron_upgrades'15:04
ihrachyshi to those still alive15:04
ihrachysFYI late OSIC layoff hit the team hard15:04
ihrachysit's not clear who is still with us15:05
ihrachysmanjeets, you have an idea?15:05
manjeetsihrachys, it will take some time I have not idea15:05
ihrachysmanjeets, I think it may have affected you too rihgt?15:05
*** mriedem has left #openstack-meeting-alt15:05
manjeetsihrachys, i talked my manager he said Im not impacted15:05
manjeetsi wasn't osic15:05
ihrachysoh that's good to hear15:05
sshankI am here to get updates.15:06
ihrachyssshank, hi! you are not OSIC either?15:06
sshankihrachys, I am OSIC.15:06
ihrachyssshank, and are you affected?15:06
sshankihrachys, Yes.15:07
sshankihrachys, I just wanna be in touch with the community irrespective.15:07
ihrachysoh ok I see, nice to hear.15:07
ihrachysso we will see how it goes.15:07
ihrachyslet's just look through our review queues to see what we can do with the situation15:08
ihrachysbtw we started landing some patches up for review that were from OSIC so that they are not bitrot before getting a chance for merge.15:09
ihrachyswe landed NetworkSegment switch which is a nice one, since it's probably one of those more complex objects that never happened15:09
ihrachysok let's get to a more formal business15:10
ihrachys#topic Objects implementation15:10
*** openstack changes topic to "Objects implementation (Meeting topic: neutron_upgrades)"15:10
ihrachys#link https://review.openstack.org/#/q/status:open+project:openstack/neutron+branch:master+topic:bp/adopt-oslo-versioned-objects-for-db15:10
ihrachyswe are landing RouterExtAttrs: https://review.openstack.org/381209 and also Victor's UT refactoring: https://review.openstack.org/42580015:11
*** diga has quit IRC15:11
ihrachysin the latter, we were hit by https://launchpad.net/bugs/1683369 but that doesn't seem like an issue of the patch in question15:11
openstackLaunchpad bug 1683369 in neutron "TagDbObjectTestCase.test_objects_exist_validate_filters_false may fail because of non-unique id for standardattributes" [High,Confirmed]15:11
ihrachysoh and the patch is in merge conflict now, so I will rebase after the meeting15:12
ihrachys#action ihrachys to rebase and push https://review.openstack.org/#/c/425800/15:12
*** EricGonczer_ has quit IRC15:12
ihrachyswe also tried to merge https://review.openstack.org/#/c/304873/ (dvr mac address object) yesterday but it seems to have an issue15:13
ihrachysin functional tests15:13
ihrachysthe patch is on tonytan_brb15:13
* ihrachys wonders if Tony was affected15:13
tonytan_brbihrachys: Yes, I am. but I will continue with the Patch.15:13
*** EricGonczer_ has joined #openstack-meeting-alt15:13
ihrachysok, thanks for following up on it15:14
ihrachystonytan_brb, you also have LIKE support: https://review.openstack.org/419152 will you follow up on that one too?15:14
tonytan_brbYes, I will15:15
ihrachysok thanks a bunch15:15
*** ijw_ has joined #openstack-meeting-alt15:15
ihrachysin other news, I updated update_objects patch: https://review.openstack.org/#/c/452266/ with the logic that I suggested (using the new update-in-place pattern only when there are no standard attributes)15:16
ihrachyssshank, but it doesn't seem to solve the test failures that we see with "sqlalchemy.exc.InvalidRequestError: Could not evaluate current criteria in Python. Specify 'fetch' or False for the synchronize_session parameter."15:16
ihrachysso it's probably a different thing15:16
ihrachyssshank, do you plan to follow up on the patch, or I should take over?15:17
sshankihrachys, you can take over.15:17
ihrachysok, thanks for your work.15:18
ihrachys#action ihrachys to take over update_objects15:18
*** ijw has quit IRC15:18
sshankihrachys, One question regarding get_objects, does it not support None filter?15:19
ihrachyssshank, what do you mean?15:20
ihrachyssshank, if you don't want to filter, you don't pass kwargs15:20
ihrachysthen you get all objects15:20
ihrachysor isn't it what you ask15:20
sshankihrachys, example: https://review.openstack.org/#/c/396351/16/neutron/db/l3_db.py@140115:21
ihrachysoh you mean passing a None value15:21
sshankyes.15:22
ihrachysdo you have a traceback handy?15:22
sshankNo. It was while back, but just wanted to ask you when Kevin mentioned it there.15:22
ihrachysI think we should make it work if it's not already15:22
ihrachysso a bug/traceback would help to understand what happens15:22
ihrachyssshank, are you going to report a bug for that?15:24
*** Kuwagata has joined #openstack-meeting-alt15:24
sshankihrachys, I can do it. But I need to test it again once.15:24
ihrachyscool15:24
ihrachys#action sshank to investigate why None filter don't work and/or report a bug15:25
*** rarcea has joined #openstack-meeting-alt15:25
*** marst has joined #openstack-meeting-alt15:25
*** sridharg has quit IRC15:26
ihrachysin other news, we still need to revive neutron-db-manage data migration command: https://review.openstack.org/43249415:27
ihrachyssince Victor now left, someone needs to take it over15:27
ihrachysI will probably take that one unless someone strongly feels like15:27
manjeetsihrachys, I can take a look today and let you know by EOD ?15:28
ihrachysmanjeets, ok please do15:28
ihrachys#action manjeets to take over new CLI command: https://review.openstack.org/43249415:28
*** shuyingy_ has quit IRC15:30
ihrachys#topic Other patches15:30
*** openstack changes topic to "Other patches (Meeting topic: neutron_upgrades)"15:30
*** shuyingya has joined #openstack-meeting-alt15:30
ihrachys#link https://review.openstack.org/#/q/status:open+message:%22UpgradeImpact%22+project:openstack/neutron15:30
ihrachysthe only patch of interest is https://review.openstack.org/#/c/456419/ and it's already in gate15:30
*** kfarr has joined #openstack-meeting-alt15:30
ihrachysit just tunes default oslo.db behaviour in neutron, nothing of major impact15:31
ihrachysany other patches to raise?15:31
*** kobis has quit IRC15:31
manjeetsnot any from me atm15:31
ihrachysok15:32
ihrachys#topic Open discussion15:32
*** openstack changes topic to "Open discussion (Meeting topic: neutron_upgrades)"15:32
ihrachysI just want to say to all folks who are affected (or not) by recent events that I appreciate all the work already done and in the queue, and it is and was a pleasure to work with everyone. I am also happy to see people plan to stick with us even if obviously priorities may shift.15:33
*** armstrong has joined #openstack-meeting-alt15:34
ihrachysok that's all I have for now. we'll meet next week as usual. review priorities are still the same since we haven't made much progress lately (and I understand why)15:35
ihrachyscu!15:35
ihrachys#endmeeting15:35
manjeetscu thanks15:35
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:35
openstackMeeting ended Mon Apr 17 15:35:20 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:35
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_upgrades/2017/neutron_upgrades.2017-04-17-15.04.html15:35
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_upgrades/2017/neutron_upgrades.2017-04-17-15.04.txt15:35
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_upgrades/2017/neutron_upgrades.2017-04-17-15.04.log.html15:35
*** rcernin has quit IRC15:37
*** armstrong has quit IRC15:38
*** armstrong has joined #openstack-meeting-alt15:39
*** chyka has joined #openstack-meeting-alt15:39
*** armstrong has quit IRC15:39
*** tellesnobrega has quit IRC15:39
*** armstrong has joined #openstack-meeting-alt15:40
*** trinaths has joined #openstack-meeting-alt15:40
*** kzaitsev_ws has quit IRC15:44
*** jaugustine has joined #openstack-meeting-alt15:44
*** nadya has quit IRC15:44
*** iyamahat has joined #openstack-meeting-alt15:44
armstrongmsg NickServ identify msg NickServ identify15:44
*** dprince has joined #openstack-meeting-alt15:48
*** annegentle has quit IRC15:49
*** shuyingya has quit IRC15:49
*** shuyingy_ has joined #openstack-meeting-alt15:50
*** gyee has joined #openstack-meeting-alt15:51
*** annegentle has joined #openstack-meeting-alt15:54
*** ijw_ has quit IRC15:54
*** armstrong has quit IRC15:55
*** ijw has joined #openstack-meeting-alt15:56
*** shuyingy_ has quit IRC16:06
*** beslemon has quit IRC16:10
*** corvus is now known as jeblair16:12
*** mdong__ is now known as mcdong16:14
*** mcdong is now known as mdong_16:15
*** mickeys has joined #openstack-meeting-alt16:20
*** nadya has joined #openstack-meeting-alt16:20
*** rcernin has joined #openstack-meeting-alt16:22
*** mickeys has quit IRC16:25
*** Swami has joined #openstack-meeting-alt16:25
*** jaugustine has quit IRC16:26
*** EricGonczer_ has quit IRC16:30
*** nadya has quit IRC16:37
*** HeOS has quit IRC16:41
*** kobis has joined #openstack-meeting-alt16:45
*** yamahata has quit IRC16:48
*** iyamahat has quit IRC16:48
*** diablo_rojo has quit IRC16:49
*** harlowja has quit IRC16:49
*** ircuser-1 has joined #openstack-meeting-alt16:52
*** harlowja has joined #openstack-meeting-alt16:52
*** amotoki has joined #openstack-meeting-alt16:55
*** manjeets has quit IRC16:57
*** krtaylor has joined #openstack-meeting-alt16:59
*** vishwanathj has quit IRC16:59
*** fnaval has quit IRC17:01
*** ijw has quit IRC17:02
*** iyamahat has joined #openstack-meeting-alt17:05
*** yamahata has joined #openstack-meeting-alt17:10
*** kiall has quit IRC17:11
*** egallen has joined #openstack-meeting-alt17:11
*** melwitt has quit IRC17:17
*** melwitt has joined #openstack-meeting-alt17:17
*** melwitt is now known as Guest5593117:17
*** tonanhngo has joined #openstack-meeting-alt17:22
*** nadya has joined #openstack-meeting-alt17:24
*** jaugustine has joined #openstack-meeting-alt17:24
*** amotoki has quit IRC17:25
*** jkilpatr has quit IRC17:26
*** tonanhngo has quit IRC17:26
*** jkilpatr has joined #openstack-meeting-alt17:27
*** tonanhngo has joined #openstack-meeting-alt17:27
*** kobis has quit IRC17:28
*** Guest55931 is now known as melwitt17:32
*** nadya has quit IRC17:38
*** JudeC has joined #openstack-meeting-alt17:41
*** dustins has quit IRC17:45
*** manjeets has joined #openstack-meeting-alt17:51
*** thrash is now known as thrash|biab17:54
*** mickeys_ has joined #openstack-meeting-alt17:58
*** ijw has joined #openstack-meeting-alt18:05
*** kobis has joined #openstack-meeting-alt18:05
*** armstrong has joined #openstack-meeting-alt18:05
*** cloudrancher has joined #openstack-meeting-alt18:05
*** armstrong has quit IRC18:07
*** trinaths has left #openstack-meeting-alt18:07
*** s3wong has joined #openstack-meeting-alt18:09
*** krtaylor has quit IRC18:09
*** EricGonczer_ has joined #openstack-meeting-alt18:09
*** EricGonczer_ has quit IRC18:10
*** tesseract has quit IRC18:10
*** EricGonczer_ has joined #openstack-meeting-alt18:11
*** jaugustine has quit IRC18:13
*** david-lyle has joined #openstack-meeting-alt18:16
*** tellesnobrega has joined #openstack-meeting-alt18:17
*** kjw3 has joined #openstack-meeting-alt18:18
*** noslzzp has joined #openstack-meeting-alt18:19
*** ijw has quit IRC18:21
*** ijw has joined #openstack-meeting-alt18:26
*** rcernin has quit IRC18:27
*** cloudrancher has quit IRC18:28
*** nadya has joined #openstack-meeting-alt18:30
*** nadya has quit IRC18:31
*** cloudrancher has joined #openstack-meeting-alt18:33
*** lpetrut has joined #openstack-meeting-alt18:34
*** dtrainor has quit IRC18:35
*** dtrainor has joined #openstack-meeting-alt18:35
*** cloudrancher has quit IRC18:37
*** vishwanathj has joined #openstack-meeting-alt18:40
*** dsariel has joined #openstack-meeting-alt18:43
*** thrash|biab is now known as thrash18:44
*** krtaylor has joined #openstack-meeting-alt18:48
*** adisky_ has quit IRC18:49
*** jaugustine has joined #openstack-meeting-alt18:50
*** lpetrut has quit IRC18:57
*** HeOS has joined #openstack-meeting-alt19:06
*** kjw3 has quit IRC19:08
*** egallen has quit IRC19:09
*** egallen has joined #openstack-meeting-alt19:14
*** kjw3 has joined #openstack-meeting-alt19:22
*** lifeless_ is now known as lifeless19:25
*** yamahata has quit IRC19:29
*** yamahata has joined #openstack-meeting-alt19:30
*** number80 has joined #openstack-meeting-alt19:31
*** egallen has quit IRC19:31
*** egallen has joined #openstack-meeting-alt19:32
*** Kuwagata has quit IRC19:35
*** pbourke has quit IRC19:35
*** pbourke has joined #openstack-meeting-alt19:36
*** Kuwagata has joined #openstack-meeting-alt19:42
*** tellesnobrega has quit IRC19:45
*** kobis has quit IRC19:56
*** kobis has joined #openstack-meeting-alt19:56
*** kobis has quit IRC19:57
*** kobis has joined #openstack-meeting-alt19:57
*** kobis has quit IRC19:57
dave-mccowan#startmeeting barbican20:00
openstackMeeting started Mon Apr 17 20:00:01 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
kfarr\o/20:01
dave-mccowanhi kfarr!20:01
kfarrhey dave-mccowan !20:02
dave-mccowanthanks for chairing last week20:02
kfarrno problem20:02
dave-mccowan#topic roll call20:02
*** openstack changes topic to "roll call (Meeting topic: barbican)"20:02
kfarro/20:02
dave-mccowani'm out of practice20:02
dave-mccowansmall group so far.  hopefully more will join soon.20:04
dave-mccowanthe agenda: https://wiki.openstack.org/wiki/Meetings/Barbican#Agenda20:04
*** diazjf has joined #openstack-meeting-alt20:04
dave-mccowan#topic pike status20:04
*** openstack changes topic to "pike status (Meeting topic: barbican)"20:04
diazjfo/20:04
dave-mccowanhi diazjf!20:04
diazjfhey dave-mccowan! It's been a busy day!20:05
dave-mccowanlet's skip to tempest testing with py3.5, while we wait for anyone else joining soon.20:05
dave-mccowankfarr i added a py35 version of the tempest testing and a few tests fail.20:05
kfarrdave-mccowan ohhh20:06
dave-mccowando you think any APLers would be able to take a look?20:06
kfarrProbably!  It's just an experimental gate for now?20:06
dave-mccowanyes20:07
dave-mccowanprobably pretty straight forward fixes... adding b'' in a few places20:07
*** alee has joined #openstack-meeting-alt20:07
aleeo/20:07
*** jkilpatr has quit IRC20:07
dave-mccowanhi alee!20:07
aleedave-mccowan, hey there20:07
*** jkilpatr has joined #openstack-meeting-alt20:07
*** felipemonteiro_ has joined #openstack-meeting-alt20:08
dave-mccowanlet's look the pike tracker: https://etherpad.openstack.org/p/barbican-tracker-pike20:08
*** david-lyle has quit IRC20:08
dave-mccowanwe're 1/3 through Pike now.  we fixed a good number of bugs in milestone 1, but haven't made much progress on our blueprints20:08
*** annegentle has quit IRC20:09
dave-mccowanalee do you have any predictions of the future for WSGI deployment or IPA vault?20:09
aleedave-mccowan, no - no predictions.20:10
aleedave-mccowan, I've been tied up on other things, but I may get freed up for at least some time20:10
aleedave-mccowan, more liekly than noy, ipa vault will be deferred20:10
*** felipemonteiro has quit IRC20:11
aleedave-mccowan, whats the wgsi deployemnt thing?20:11
dave-mccowanit's a community goal, and something said that OOO needed too.  i guess deploy behind httpd is the most popular way to do it.20:12
dave-mccowanwe want to make it the default for devstack20:12
aleedave-mccowan, oh ok - yeah we do20:12
alee(we already do in triple-o20:12
dave-mccowansweet.  easy cut-n-paste then. :-)20:13
aleedave-mccowan, so yeah its still doable. just gotta find time to do it20:13
dave-mccowancool.  still plenty of time, but it'll go fast with summit in the middle of the release.20:14
dave-mccowankfarr what about list filters?  i know you have a bunch of patches out for this.  do they need reviews?20:14
kfarrYes!20:14
kfarrredrobot already implemented the backend feature20:15
kfarrIt just needs to be exposed in python-barbicanclient (and castellan)20:15
kfarrHere's python-barbicanclient: https://review.openstack.org/#/c/400370/20:15
kfarrand castellan (dependent on the above patch): https://review.openstack.org/#/c/418019/20:16
dave-mccowanis all the code done for it then?  just waiting on reviews and merges?20:16
kfarrYup!20:16
dave-mccowancool!20:16
*** EricGonczer_ has quit IRC20:17
dave-mccowanfor Python 3.5, the community goal is to have functional and tempest gate jobs running with py35.20:17
dave-mccowani have most of the functional tests running.  just about 20 failing tests left to fix.20:17
dave-mccowanthere's also an experimental gate job for tempest that has a few failures too.20:18
dave-mccowanhopefully we'll get all of those cleared up soon20:18
dave-mccowandiazjf what's up with deprecation?20:18
diazjfdave-mccowan, I'm setting up some time to get it done this week20:19
dave-mccowangreat!20:19
diazjf#action diazjf to submit patches to remove certificates api.20:20
dave-mccowanif anyone has an item schedule for pike-1, please update it to p2, p3, or future based on your plans.20:20
dave-mccowan#action diazjf to submit patches to remove certificates api.20:20
dave-mccowanany database gurus here?20:21
*** stingaci has joined #openstack-meeting-alt20:21
dave-mccowanjeremy has a weird db issue where it's working differently with centos than for ubuntu.20:21
dave-mccowanhttps://bugs.launchpad.net/barbican/+bug/168198820:21
openstackLaunchpad bug 1681988 in Barbican "py27 UT fails on centos7.2.1511" [Undecided,New]20:21
dave-mccowanthat's all i have for Pike20:22
dave-mccowanmoving on....20:22
dave-mccowan#topic Summit20:22
*** openstack changes topic to "Summit (Meeting topic: barbican)"20:22
dave-mccowanalee i saw you had some updates last week for the workshop20:23
dave-mccowananything else new, or urgent?20:23
aleedave-mccowan, yeah - I'd like to get a meeting scheduled for the workshop presenters this week20:23
aleekfarr, and I were thinking tommorow morning perhaps?20:23
alee11 am EST?20:23
dave-mccowan+1 for me20:23
kfarr+120:23
aleeredrobot, diazjf , dave-mccowan ?20:24
redroboto/20:24
dave-mccowanredrobot \o/20:24
*** kobis has joined #openstack-meeting-alt20:24
diazjfalee, redrobot, wotks for me.20:25
redrobotsorry I'm late guys20:25
redrobotIt's been a fun few days at the rack20:25
aleeredrobot, can you meet tomorow at 11 am EST?20:25
aleefor the workshop ..20:25
*** rcernin has joined #openstack-meeting-alt20:25
redrobotalee yes, should be good.20:25
*** dprince has quit IRC20:25
aleedave-mccowan, ??20:25
dave-mccowanyes for me20:26
aleeexcellent -- kfarr can you set it up?20:26
kfarrAh yes20:26
kfarrMeeting invite ?20:26
aleeyup20:26
aleegoogle hangout20:26
aleewe can do updates then20:27
dave-mccowanredrobot we should set another time to start planning the vault presentation20:27
dave-mccowanhttps://etherpad.openstack.org/p/barbican-pike-summit20:28
dave-mccowanbarbicaneers are busy this summit.  feel free to add anything you to share to that etherpad20:29
dave-mccowananything else for summit?20:29
dave-mccowan#topic pike status revist20:30
*** openstack changes topic to "pike status revist (Meeting topic: barbican)"20:30
dave-mccowanredrobot do you have an update for any pike blueprint items?20:30
dave-mccowan(do you need help or review or anything?)20:30
*** kobis has quit IRC20:30
dave-mccowanhttps://etherpad.openstack.org/p/barbican-tracker-pike20:30
dave-mccowanyou signed up for 4 at the PTG.20:31
redrobotwell, not sure if y'all saw the news already but OSIC was cancelled20:32
redrobotso no Intel folks will be joining20:32
dave-mccowan:-(20:33
kfarryeah :(20:33
diazjf:(20:33
redrobotand I'm only working on Barbican for this week and next, and hopefully find a new job shortly after that.20:33
kfarr!!20:33
openstackkfarr: Error: "!" is not a valid command.20:33
redrobotI'm still going to Boston on my own dime20:33
redrobotand will definitely work on the presentations20:33
kfarr:( :(20:34
dave-mccowanredrobot I hope everything works out.  definitely apply for travel assistance.20:34
redrobotalso if anyone is hiring, let me know!  I've got a freshly updated resume I can send your way :)20:34
redrobotdave-mccowan yep, I've been frantically email lots of folks, and I still have speaker support on my list of to-dos20:35
redrobot*emailing20:35
diazjfredrobot, good luck my dude!20:35
*** mdong_ has quit IRC20:35
redrobotdiazjf thanks m820:35
redrobotdave-mccowan yeah, let's sync up some time tomorrow for the Vault talk20:36
dave-mccowanredrobot tomorrow is good for me.20:36
dave-mccowan#topic any other business20:36
*** openstack changes topic to "any other business (Meeting topic: barbican)"20:36
dave-mccowanthanks everyone!  we'll talk tomorrow on summit prep!20:38
dave-mccowan#endmeeting20:38
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:38
openstackMeeting ended Mon Apr 17 20:38:22 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-04-17-20.00.html20:38
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/barbican/2017/barbican.2017-04-17-20.00.txt20:38
openstackLog:            http://eavesdrop.openstack.org/meetings/barbican/2017/barbican.2017-04-17-20.00.log.html20:38
diazjfthanks!20:38
*** diazjf has quit IRC20:38
*** ijw has quit IRC20:43
*** diazjf has joined #openstack-meeting-alt20:43
*** ijw has joined #openstack-meeting-alt20:44
*** ijw has quit IRC20:49
*** ansmith has quit IRC20:49
*** hichihara has joined #openstack-meeting-alt20:55
*** rcernin has quit IRC20:56
*** MeganR has joined #openstack-meeting-alt20:56
*** diazjf has quit IRC20:57
*** dimtruck is now known as zz_dimtruck20:58
*** MeganR has quit IRC21:05
*** sdague has quit IRC21:05
*** matrohon has joined #openstack-meeting-alt21:05
*** Arkady_Kanevsky has joined #openstack-meeting-alt21:07
Arkady_Kanevskyhello21:07
*** jose-phillips has quit IRC21:07
Arkady_KanevskyPWG meeting today?21:08
*** krtaylor has quit IRC21:08
*** Arkady_Kanevsky has quit IRC21:15
*** marst has quit IRC21:17
*** marst has joined #openstack-meeting-alt21:17
*** zz_dimtruck is now known as dimtruck21:26
*** matrohon has quit IRC21:38
*** baoli has quit IRC21:43
*** dave-mcc_ has joined #openstack-meeting-alt21:43
*** dave-mccowan has quit IRC21:44
*** shobhar has joined #openstack-meeting-alt21:46
*** shobhar_ has joined #openstack-meeting-alt21:46
*** kfarr has quit IRC21:47
*** diazjf has joined #openstack-meeting-alt21:47
*** dave-mccowan has joined #openstack-meeting-alt21:47
*** dave-mcc_ has quit IRC21:50
*** jamielennox has joined #openstack-meeting-alt21:50
*** Shrews has joined #openstack-meeting-alt21:51
*** felipemonteiro_ has quit IRC21:51
*** rarcea has quit IRC21:52
*** annegentle has joined #openstack-meeting-alt21:53
*** diazjf has quit IRC21:54
*** jlk has joined #openstack-meeting-alt21:57
*** vishwanathj has quit IRC21:57
*** shobhar has quit IRC21:59
*** shobhar_ has quit IRC21:59
*** rfolco has quit IRC22:00
fungizuuuuuul22:01
jeblairare other zuul folks around?22:01
clarkbo/22:02
jlko/22:02
fungii guess today there is no pwg, only zuul22:02
pabelangerhello22:02
SpamapSo/22:02
jamielennoxo/22:02
jeblair#startmeeting zuul22:03
openstackMeeting started Mon Apr 17 22:03:03 2017 UTC and is due to finish in 60 minutes.  The chair is jeblair. Information about MeetBot at http://wiki.debian.org/MeetBot.22:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.22:03
*** openstack changes topic to " (Meeting topic: zuul)"22:03
openstackThe meeting name has been set to 'zuul'22:03
jeblair#link agenda https://wiki.openstack.org/wiki/Meetings/Zuul#Agenda_for_next_meeting22:03
*** noslzzp has quit IRC22:03
jeblair#link previous meetig http://eavesdrop.openstack.org/meetings/zuul/2017/zuul.2017-04-03-22.03.html22:03
jeblair#topic Actions from last meeting22:04
*** openstack changes topic to "Actions from last meeting (Meeting topic: zuul)"22:04
jeblairmordred add custom path-blocking lookup plugin22:04
jeblairthat happened!22:04
jeblairtests for that are in-progress22:04
jlktwas a good bit of usefulness.22:05
*** annegentle has quit IRC22:05
jeblair++22:05
jeblair#topic  Status updates (Zuul test enablement)22:05
*** openstack changes topic to "Status updates (Zuul test enablement) (Meeting topic: zuul)"22:05
mordredjeblair: (fwiw, I have not made any progress in the car on more tests - but I may stil lbefore you wake up in the morning)22:05
* mordred is not really here22:05
jeblairmordred: cool, thanks.  i'll sleep in to increase your chances.  :)22:06
*** haleyb has quit IRC22:06
jeblairi'm not fully caught up yet; are there any new test fixes that are waiting on reviews or anything?22:06
SpamapSI believe we're good on the ones done22:07
*** EricGonczer_ has joined #openstack-meeting-alt22:07
SpamapSI have one that I don't really understand regarding timer+sshkey things...22:07
SpamapSbut that's ongoing22:07
SpamapSand then there are a few less-trivial ones left to pick up22:08
*** marst has quit IRC22:08
SpamapSoverall I think we're in the home stretch. :)22:08
*** marst_ has joined #openstack-meeting-alt22:08
jeblairSpamapS: cool, maybe we can poke at the timer+sshkey stuff later this week22:10
jeblair#topic Status updates (Zuul sample jobs)22:11
*** openstack changes topic to "Status updates (Zuul sample jobs) (Meeting topic: zuul)"22:11
*** hichihara has quit IRC22:12
*** ihrachys has quit IRC22:13
*** thrash is now known as thrash|g0ne22:13
jeblairpabelanger: what's the status here?22:13
pabelangerI think we might be ready to split out some of the playbooks in zuul playbooks folder into another git repo, then start on some stdlib things22:14
pabelangerright now, it is somewhat confusing what is stdlib and what is openstack-infra22:14
pabelangerwe also discussed bringing nodepool project online too22:14
*** marst_ has quit IRC22:15
clarkbwhen you say stdlib, do you mean things that would live in zuul proper?22:15
jamielennoxpabelanger: i'm fairly interested in what we define as stdlib here if you want help/discussion on that22:15
pabelangerclarkb: right22:15
pabelangerhttps://review.openstack.org/#/c/441617/ is the context22:16
jlkditto what jamielennox said22:16
fungial la python's stdlib. which batteries we're including with zuul basically22:16
pabelangerright now, to me, everything in our playbooks folder today, is very openstack-infra specific22:16
pabelangerwhich, is okay for now, because it allows faster iteration22:16
*** ijw has joined #openstack-meeting-alt22:17
jeblairyeah, i think there may be three levels here: 1) something so fundamental it shuld go inside of the zuul repo itself and be automatically available to every zuul installation (eg, copy git repos).  2) generally useful things that should maybe iterate faster than the dev cycle for zuul itself (eg, tox).  3) purely local things that should be in openstack-infra/project-config (eg, infra mirror setup).22:18
fungiif we want to draw a distinction at 2 for faster iteration, i think putting the zuul stdlib in a separate repo (covering 1 and 2) which is considered tightly coupled with zuul makes some sense22:20
fungithere's not much about zuul's design which necessitates the stdlib being included _in_ the same git repo, i don't think?22:21
fungiso can sort of have our cake and eat it to22:21
jeblairfungi: no, i just wanted to broach the possibility that if it takes extra effort to install the stdlib, we can consider putting things that are very fundamental in zuul itself.22:22
jeblairbut if we solve "make stdlib easily available", then we don't have to.22:22
clarkbcould potentially just be an install dep22:22
clarkbwhcih gets updated more often than zuul (potentially)22:23
fungithpigh i do think whatever we consider "stdlib" needs some fairly tight api/behavior contracts22:23
fungis/thpigh/though/22:23
pabelangerI don't think we need a new git repo for now, we could start prefixing roles with zuul.foobar or stdlib.foobar, until we decide that step. That allows things to live zuul/playbooks for a while longer22:23
fungistarting in the zuul repo now and splitting them later seems fine to me too22:24
fungi(splitting them later if we decide it's warranted, i mean)22:24
fungibut i do think any playbooks we consider distributed "with" zuul as a stdlib, we need to be fairly certain we can keep their behaviors consistent or provide backward-compatibility when we need to alter them22:25
jeblairpabelanger: yeah.  i know in review we've discussed things which make sense for stdlib and things which are local.  so maybe we should take the step you suggest and start namespacing them so that's clear.  then we can defer making the new repo for just a little bit longer.22:26
*** annegentle has joined #openstack-meeting-alt22:26
pabelangersure, I'm happy to do that22:26
*** xyang1 has quit IRC22:26
clarkbit will also help make it concrete with low effort so we can paint the bikeshed more easily :)22:26
pabelangeroh, I imagine stdlib will be many colors22:27
fungiplaid22:27
*** diazjf has joined #openstack-meeting-alt22:29
jeblair#agreed start namespacing roles in zuul to help with transition to stdlib22:29
*** spotz_ has joined #openstack-meeting-alt22:29
jeblair#topic Progress summary22:30
*** openstack changes topic to "Progress summary (Meeting topic: zuul)"22:30
*** spotz_ has quit IRC22:30
jeblairSpamapS: how's the board look?22:30
SpamapSTo be honest I did not look at it the entire last week.22:30
*** kjw3 has quit IRC22:30
jeblairneither did i.  but i did see a bear.22:30
SpamapS#link https://storyboard.openstack.org/#!/board/4122:31
SpamapSI saw bear _tracks_ in the snow in Mammoth. ;)22:31
*** jaugustine has quit IRC22:31
jeblairSpamapS: oh, we should drop the swift task22:31
SpamapSjeblair: we had talked about splitting up tags22:31
SpamapSjeblair: right that's a post playbook now, yes?22:32
SpamapSso we should change that one to delete the test22:32
jeblairSpamapS: or will be, yes.22:32
jeblairSpamapS: do we have enough zuulv3.1 stories to warrant a new tag/board?22:33
SpamapSI think it would help with visualizing where we're at if we start pushing things that aren't critical to infra's use of zuulv3 off to another tag.22:33
*** diazjf has quit IRC22:33
*** spotz_ has joined #openstack-meeting-alt22:34
SpamapSjeblair: I'm not sure if it's a lot22:34
SpamapSseems worth it to just go through them, so I can take that as an action22:34
*** baoli has joined #openstack-meeting-alt22:34
jeblairSpamapS: okay.  though it seems there's some overlap with 'backlog' there.22:34
*** krtaylor has joined #openstack-meeting-alt22:35
jeblairit's a grey area.  something to consider at least.  :)22:35
SpamapSwell my current thinking had been that all of these things had to be doen before we call v3 done22:36
SpamapSincludin backlog (backlog is just "we know we have to , we don't know when yet")22:36
jeblairSpamapS: yeah, though many of the things in backlog aren't actually critical to openstack-infra v3.22:36
jeblairso i think there may be overlapping subsets.  :)22:37
SpamapSwe could avoid a new tag, and just make the backlog column mean "stuff we know we need to do because we're changing things" and todo can mean "all the things we need to do to use zuul"22:37
jeblairyeah, or maybe even add another column or two?22:37
SpamapSyeah that's another option22:37
SpamapSthe whole point of the board is to allow people to see what to do next22:38
jeblairSpamapS: i'll defer to you on how to structure and stand ready to help sort.22:38
SpamapS(and to see what is thought of, but not next)22:38
SpamapSjeblair: I think we should just make todo "stuff we have to do to use zuulv3 in infra"22:38
*** annegentle has quit IRC22:39
*** baoli has quit IRC22:39
SpamapSif it gets too big22:39
SpamapSwe can retag some things out of backlog22:39
jeblairSpamapS: okay, let's work on that in channel this week22:40
*** jkilpatr has quit IRC22:40
SpamapSyeah22:40
jeblair#topic Where should image username go? (jamielennox)22:40
*** openstack changes topic to "Where should image username go? (jamielennox) (Meeting topic: zuul)"22:40
*** knangia has quit IRC22:41
jamielennoxso yea, simple enough problem that we are building images that use a different username22:41
jamielennoxpreviously this was controlled in zuul.conf, but it was brought up by jhesketh that maybe this should be controlled by nodepool22:41
jamielennoxi think that's probably right, but we just removed the username option from nodepool because it doesn't ssh any more22:41
clarkbwould it be terrible to just require a zuul user?22:42
clarkb(I'm not sure if this needs to be configurable end of day?)22:42
jamielennoxboth options have reviews up but it just requires consensus on an approach22:42
pabelangerUnless we want images to have different usernames in a provider, I think zuul.conf is fine, right?22:43
jeblairit's easy enough to make it configurable in zuul.conf, so even if we wanted to "hard code" it, i'd say we could *at least* do that.  however, there's a pretty good argument to be made that when you tell nodepool to build an image, that's a good place to put the information "this is the username to use to log into the image".22:43
*** egallen has quit IRC22:44
*** knangia has joined #openstack-meeting-alt22:44
*** egallen has joined #openstack-meeting-alt22:44
jamielennoxi'm also ok with completely punting on this until we have a hard case we can't get around, it was an option we used in 2.5 that is no longer available in v3 that i tried to add back22:45
jamielennoxbut in general i think its useful and might help the nodepool outside zuul case22:45
jeblairi think 'add to zuul.conf' is also fairly future-proof.  in that if we add something either to nodepool or zuul's own node definitions later, that just becomes "default username" instead of "username".22:45
pabelangerssh username in nodepool might also makes sense if we every added snapshot images back to nodepool-launcher?22:46
pabelangernodepool-builder*22:46
*** kjw3 has joined #openstack-meeting-alt22:46
jeblairpabelanger: well, the snapshot image build process may not use the same user as the final image, so i don't think that's a given.22:47
clarkbmy concern with putting it in nodepool is we'd maybe want to have nodepool config affect dib elements somehow to set the user that way you don't set username: foo then wonder why you can't log in as foo?22:47
jamielennoxjeblair: agreed, at the moment the default of zuul comes from the user zuul is running as, not actually in code anywhere so it is a useful default22:47
jeblairclarkb: good point22:47
clarkbwhere as if its just "make sure there is a zuul user" that seems to be a straighforward requirement  for setup22:47
Shrewsif we choose nodepool, do we REALLY have to store the username in the ImageBuild, ImageUpload, AND Node objects?22:47
jeblairjamielennox: oops, i think 'default to current running user' is a mistake.  :)22:47
Shrewsthat seems excessive22:47
jamielennoxShrews: it was the only way i could see to pass it from build through to ready22:48
pabelangerclarkb: I know off-topic, but the removal of ssh from nodepool makes that a little more difficult to troubleshoot, since zuul needs to now be involved22:48
jeblaircould maybe skip imageupload since it references imagebuild22:48
fungiyeah, i think we're unintentionally getting the ssh client implementation's default, so being explicit even about what our default is seems preferable22:49
jeblair(you could also skip node, but then that would require zuul to look up the imagebuild, which it doesn't have to now)22:49
*** HeOS has quit IRC22:49
jeblairpabelanger: i'd like to follow up on how that's more complex after the meeting22:49
jeblairso i'm reading lukewarm support for addition to nodepool -- for now at least; and more support for zuul.conf.22:50
*** ansmith has joined #openstack-meeting-alt22:50
pabelangerthink so22:50
jeblairanyone disagree with that ^?22:51
jamielennoxi think it's good to have a default there anyway and we can deal with nodepool if/when required22:51
jlkI agree, I do not disagree22:51
Shrewsi agree with jlk's not disagreeing22:52
jeblair#agreed configure zuul ansible ssh user in zuul.conf for now; revisit adding to nodepool/zk as needed later.22:53
jeblairjamielennox: thanks for pushing that through!22:54
jeblair#topic Executor security spec: https://review.openstack.org/44449522:54
*** openstack changes topic to "Executor security spec: https://review.openstack.org/444495 (Meeting topic: zuul)"22:54
jeblairi put this on the agenda at fungi's suggestion earlier22:54
*** jrobinson has joined #openstack-meeting-alt22:54
jeblairwe chatted about it at length in channel22:54
fungii don't know whether any further discussion is warranted after we talked in here a few hours ago, but it's coming up on last call for dissent22:55
*** kjw3 has quit IRC22:55
SpamapSI'm personally comfortable running with it for BonnyCI22:55
fungiso just wanted to be sure since clarkb felt pretty strongly about some of it22:55
SpamapSwhich is an attempt to make a Zuul-aaS for all github projects22:55
SpamapSwhich is likely to have a really nasty set of horrible bad actors22:56
SpamapSso..22:56
jlkI'm deferring to SpamapS on the wrapper around the thing22:56
jlkI've focused more on the thing, and the bad things the thing can be coaxed into doing22:56
SpamapSbubblewrap is some of the simplest, easiest to read C I've looked at22:56
SpamapSI highly recommend taking the tour22:56
jamielennox"the least painful open would i've ever had"22:56
jamielennoxwound22:57
SpamapSI have tried treating the wound with liberal application of Rust... https://github.com/SpamapS/rubble ;-)22:57
jeblairi also think this is reasonable for openstack-infra.22:57
fungii'm confident at this point that if particularly concerned zuul admins wanted to limit things to only running trusted playbooks on the executor and chaining to running untrusted ansible playbooks on the test nodes, that they can basically ignore the sandboxing (but it does help protect the system from their trusted playbooks, even then)22:57
*** EricGonczer_ has quit IRC22:57
SpamapSwe could also make the wrapper libvirt ... nested VMs are so much fun22:58
clarkbfungi: I think you'd need to modify zuul a bit for that, but agreed it would be simple to do if necessary22:58
jeblairfungi: strictly speaking, "trusted" playbooks in zuulv3-speak would run outside of the sandbox, but your scenario is adding another layer, so maybe that's what you meant (the playbooks they trust will run as untrusted zuul playbooks and would then run something else on a test node)22:59
fungiweighing the features this allows against the risks, i'm in favor of supporting it, personally22:59
fungioh, yep, s/trusted/tightly-controlled/22:59
jeblairfungi: then yes, agreed.  :)22:59
fungisorry, overloading terminology there22:59
jeblairi only brought up the nitpick in case it exposed some misunderstanding, but i don't think so.23:00
jlkoverloading terminology that's actively being changed :)23:00
fungifun for the whole family23:00
jeblairjlk: "this statement may contain future-looking terminology"23:00
fungithanks for following up on this!23:00
jlkhah!23:00
fungii have what we need to move forward on the spec review23:01
jeblairfungi: thanks!23:01
jeblairlooks like this should end up on tomorrow's infra meeting agenda23:01
jeblairthanks all!23:01
jeblair#endmeeting23:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"23:01
openstackMeeting ended Mon Apr 17 23:01:34 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)23:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/zuul/2017/zuul.2017-04-17-22.03.html23:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/zuul/2017/zuul.2017-04-17-22.03.txt23:01
openstackLog:            http://eavesdrop.openstack.org/meetings/zuul/2017/zuul.2017-04-17-22.03.log.html23:01
*** kjw3 has joined #openstack-meeting-alt23:03
*** mickeys_ has quit IRC23:03
*** stingaci has quit IRC23:17
*** kjw3 has quit IRC23:17
*** jkilpatr has joined #openstack-meeting-alt23:18
*** cloudrancher has joined #openstack-meeting-alt23:18
*** gongysh has joined #openstack-meeting-alt23:22
*** gongysh has quit IRC23:22
*** armstrong has joined #openstack-meeting-alt23:23
*** chyka has quit IRC23:30
*** gouthamr has quit IRC23:32
*** rfolco has joined #openstack-meeting-alt23:41
*** rfolco has quit IRC23:41
*** rfolco has joined #openstack-meeting-alt23:41
*** rfolco has quit IRC23:41
*** stingaci has joined #openstack-meeting-alt23:43
*** gouthamr has joined #openstack-meeting-alt23:54
*** jianghuaw_ has quit IRC23:56
*** ijw has quit IRC23:59
*** noslzzp has joined #openstack-meeting-alt23:59

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