Monday, 2017-10-23

*** salv-orlando has quit IRC00:07
*** salv-orlando has joined #openstack-meeting-alt00:08
*** yangyape_ has quit IRC00:17
*** yangyapeng has joined #openstack-meeting-alt00:18
*** yangyapeng has quit IRC00:22
*** noslzzp has joined #openstack-meeting-alt00:37
*** hieulq has joined #openstack-meeting-alt00:43
*** hiro-kobayashi has joined #openstack-meeting-alt00:48
*** cloudrancher has quit IRC00:51
*** cloudrancher has joined #openstack-meeting-alt00:52
*** nguyentrihai has joined #openstack-meeting-alt01:03
*** salv-orl_ has joined #openstack-meeting-alt01:07
*** salv-orlando has quit IRC01:10
*** yangyapeng has joined #openstack-meeting-alt01:20
*** hongbin has joined #openstack-meeting-alt01:26
*** tovin07_ has joined #openstack-meeting-alt01:27
*** noslzzp has quit IRC01:29
*** noslzzp has joined #openstack-meeting-alt01:30
*** markstur has joined #openstack-meeting-alt01:31
*** markstur has quit IRC01:36
*** d0ugal has quit IRC01:36
*** efried has joined #openstack-meeting-alt01:37
*** trungnv has joined #openstack-meeting-alt01:40
*** d0ugal has joined #openstack-meeting-alt02:00
*** caowei has joined #openstack-meeting-alt02:02
*** gcb has joined #openstack-meeting-alt02:15
*** dalgaaf has quit IRC02:16
*** dalgaaf has joined #openstack-meeting-alt02:16
*** bzhao has quit IRC02:22
*** bzhao has joined #openstack-meeting-alt02:23
*** salv-orl_ has quit IRC02:25
*** salv-orlando has joined #openstack-meeting-alt02:25
*** salv-orlando has quit IRC02:43
*** markstur has joined #openstack-meeting-alt02:44
*** salv-orlando has joined #openstack-meeting-alt02:44
*** chyka has joined #openstack-meeting-alt02:45
*** markstur has quit IRC02:48
*** hiro-kobayashi has quit IRC03:02
*** dave-mccowan has quit IRC03:05
*** chyka has quit IRC03:11
*** hieulq has quit IRC03:23
*** hieulq has joined #openstack-meeting-alt03:23
*** kumarmn has joined #openstack-meeting-alt03:39
*** kumarmn has quit IRC03:44
*** macermak has joined #openstack-meeting-alt04:05
*** hongbin has quit IRC04:12
*** yamamoto has joined #openstack-meeting-alt04:16
*** anilvenkata has joined #openstack-meeting-alt04:18
*** janki has joined #openstack-meeting-alt04:22
*** achadha has joined #openstack-meeting-alt04:26
*** skramaja has joined #openstack-meeting-alt04:39
*** bhavik1 has joined #openstack-meeting-alt04:42
*** sridharg has joined #openstack-meeting-alt05:31
*** yangyapeng has quit IRC05:36
*** yangyapeng has joined #openstack-meeting-alt05:36
*** achadha has quit IRC05:39
*** achadha has joined #openstack-meeting-alt05:39
*** yangyapeng has quit IRC05:41
*** achadha has quit IRC05:43
*** mjura has joined #openstack-meeting-alt05:48
*** spectr has joined #openstack-meeting-alt05:52
*** macermak has quit IRC06:13
*** macermak has joined #openstack-meeting-alt06:13
*** jprovazn has joined #openstack-meeting-alt06:16
*** tace has joined #openstack-meeting-alt06:21
*** bhavik1 has quit IRC06:21
*** pgadiya has joined #openstack-meeting-alt06:23
*** yamamoto has quit IRC06:33
*** jprovazn has quit IRC06:42
*** jprovazn has joined #openstack-meeting-alt06:49
*** yamamoto has joined #openstack-meeting-alt06:52
*** karthiks has joined #openstack-meeting-alt06:53
*** jtomasek has joined #openstack-meeting-alt07:01
*** ircuser-1 has joined #openstack-meeting-alt07:10
*** yamamoto_ has joined #openstack-meeting-alt07:11
*** yamamoto has quit IRC07:13
*** jtomasek has quit IRC07:14
*** marios has joined #openstack-meeting-alt07:16
*** ccamacho has joined #openstack-meeting-alt07:18
*** tesseract has joined #openstack-meeting-alt07:27
*** yamamoto_ has quit IRC07:29
*** yamamoto has joined #openstack-meeting-alt07:29
*** kumarmn has joined #openstack-meeting-alt07:40
*** jpena|off is now known as jpena07:43
*** yamamoto has quit IRC07:43
*** kumarmn has quit IRC07:44
*** salv-orlando has quit IRC07:50
*** salv-orlando has joined #openstack-meeting-alt07:50
*** jtomasek has joined #openstack-meeting-alt07:54
*** salv-orl_ has joined #openstack-meeting-alt07:55
*** jprovazn has quit IRC07:55
*** yamamoto has joined #openstack-meeting-alt07:57
*** jprovazn has joined #openstack-meeting-alt07:58
*** salv-orlando has quit IRC07:58
*** yamamoto has quit IRC08:03
*** number80 has joined #openstack-meeting-alt08:09
*** oidgar has joined #openstack-meeting-alt08:10
*** MarkBaker has joined #openstack-meeting-alt08:14
*** ralonsoh has joined #openstack-meeting-alt08:22
*** finucannot is now known as stephenfin08:23
*** derekh has joined #openstack-meeting-alt08:32
*** spectr has quit IRC08:35
*** yamamoto has joined #openstack-meeting-alt08:36
*** yamamoto has quit IRC08:38
*** bfernando has joined #openstack-meeting-alt08:42
*** ushkalim has joined #openstack-meeting-alt08:49
*** spectr has joined #openstack-meeting-alt08:49
*** yamamoto has joined #openstack-meeting-alt08:50
*** bbzhao has joined #openstack-meeting-alt08:57
*** bzhao has quit IRC09:00
*** bbzhao has quit IRC09:01
*** bbzhao has joined #openstack-meeting-alt09:01
*** yamamoto has quit IRC09:03
*** derekh has quit IRC09:11
*** yamamoto has joined #openstack-meeting-alt09:13
*** derekh has joined #openstack-meeting-alt09:13
*** sambetts|afk is now known as sambetts09:15
*** arxcruz|off is now known as arxcruz09:19
*** dsariel has joined #openstack-meeting-alt09:21
*** janki has quit IRC09:21
*** beekhof has quit IRC09:22
*** spectr has quit IRC09:31
*** spectr has joined #openstack-meeting-alt09:31
*** salv-orl_ has quit IRC09:36
*** salv-orlando has joined #openstack-meeting-alt09:37
*** salv-orlando has quit IRC09:41
*** sdague has joined #openstack-meeting-alt09:44
*** rossella_s has joined #openstack-meeting-alt09:51
*** bsilverman_5 has quit IRC09:53
*** bsilverman_ has joined #openstack-meeting-alt09:54
*** gcb has quit IRC09:56
*** yamamoto has quit IRC09:58
*** yamamoto has joined #openstack-meeting-alt09:59
*** gcb has joined #openstack-meeting-alt10:00
*** vds has joined #openstack-meeting-alt10:03
*** spectr has quit IRC10:04
*** beekhof has joined #openstack-meeting-alt10:06
*** yamamoto has quit IRC10:06
*** yamamoto has joined #openstack-meeting-alt10:06
*** tovin07_ has quit IRC10:12
*** caowei has quit IRC10:20
*** spectr has joined #openstack-meeting-alt10:21
*** rossella_s has quit IRC10:21
*** pbourke has quit IRC10:37
*** yamamoto_ has joined #openstack-meeting-alt10:37
*** pbourke has joined #openstack-meeting-alt10:38
*** yangyapeng has joined #openstack-meeting-alt10:38
*** janki has joined #openstack-meeting-alt10:40
*** yamamoto has quit IRC10:40
*** yangyapeng has quit IRC10:43
*** yangyapeng has joined #openstack-meeting-alt10:44
*** spectr has quit IRC10:45
*** spectr has joined #openstack-meeting-alt10:47
*** yamamoto_ has quit IRC10:48
*** yamamoto has joined #openstack-meeting-alt10:50
*** yamamoto has quit IRC10:55
*** yamamoto has joined #openstack-meeting-alt10:55
*** gcb has quit IRC10:58
*** dave-mccowan has joined #openstack-meeting-alt11:04
*** tpsilva has joined #openstack-meeting-alt11:14
*** jkilpatr has joined #openstack-meeting-alt11:19
*** yamamoto_ has joined #openstack-meeting-alt11:30
*** yamamoto_ has quit IRC11:31
*** yamamoto has quit IRC11:32
*** yamamoto has joined #openstack-meeting-alt11:32
*** jpena is now known as jpena|lunch11:36
*** pgadiya has quit IRC11:38
*** lpetrut has joined #openstack-meeting-alt11:39
*** jtomasek has quit IRC11:39
*** erlon has joined #openstack-meeting-alt11:42
*** janki has quit IRC11:44
*** yamamoto has quit IRC11:52
*** yamamoto has joined #openstack-meeting-alt11:53
*** julim has quit IRC11:56
*** yamamoto has quit IRC11:58
*** bzhao has joined #openstack-meeting-alt12:01
*** cgoncalves has quit IRC12:01
*** fzdarsky has joined #openstack-meeting-alt12:03
*** bbzhao has quit IRC12:03
*** cgoncalves has joined #openstack-meeting-alt12:04
*** salv-orlando has joined #openstack-meeting-alt12:04
*** jtomasek has joined #openstack-meeting-alt12:08
*** rossella_s has joined #openstack-meeting-alt12:12
*** raildo has joined #openstack-meeting-alt12:13
*** raildo has quit IRC12:13
*** dhellmann has quit IRC12:15
*** dhellmann has joined #openstack-meeting-alt12:16
*** felipemonteiro has joined #openstack-meeting-alt12:16
*** felipemonteiro_ has quit IRC12:17
*** weshay|bbiab is now known as weshay|ruck12:18
*** raildo has joined #openstack-meeting-alt12:20
*** egallen has joined #openstack-meeting-alt12:20
*** dprince has joined #openstack-meeting-alt12:21
*** bbzhao has joined #openstack-meeting-alt12:25
*** bzhao has quit IRC12:27
*** yamamoto has joined #openstack-meeting-alt12:36
*** jpena|lunch is now known as jpena12:40
*** yamamoto has quit IRC12:46
*** chyka has joined #openstack-meeting-alt12:57
*** lennyb has quit IRC12:59
*** chyka has quit IRC13:01
*** yamamoto has joined #openstack-meeting-alt13:02
*** oidgar has quit IRC13:03
*** jtomasek has quit IRC13:05
*** lennyb has joined #openstack-meeting-alt13:05
*** jtomasek has joined #openstack-meeting-alt13:11
*** macermak has quit IRC13:12
*** julim has joined #openstack-meeting-alt13:14
*** salv-orl_ has joined #openstack-meeting-alt13:15
*** salv-orlando has quit IRC13:16
*** salv-orl_ has quit IRC13:17
*** salv-orlando has joined #openstack-meeting-alt13:18
*** oidgar has joined #openstack-meeting-alt13:20
*** lennyb has quit IRC13:23
*** xyang1 has joined #openstack-meeting-alt13:24
*** baoli has joined #openstack-meeting-alt13:25
*** gcb has joined #openstack-meeting-alt13:25
*** lennyb has joined #openstack-meeting-alt13:27
*** oidgar has quit IRC13:29
*** oidgar has joined #openstack-meeting-alt13:31
*** jcoufal has joined #openstack-meeting-alt13:34
*** kylek3h has joined #openstack-meeting-alt13:35
*** bbzhao has quit IRC13:43
*** mriedem has joined #openstack-meeting-alt13:44
*** salv-orl_ has joined #openstack-meeting-alt13:44
*** salv-orlando has quit IRC13:45
*** kumarmn has joined #openstack-meeting-alt13:48
*** yangyapeng has quit IRC13:50
*** yangyapeng has joined #openstack-meeting-alt13:51
*** takashin has joined #openstack-meeting-alt13:53
*** kumarmn has quit IRC13:54
*** jaypipes has joined #openstack-meeting-alt13:55
*** yangyapeng has quit IRC13:55
*** skramaja has quit IRC13:56
*** hongbin has joined #openstack-meeting-alt13:56
*** gcb has quit IRC13:58
*** gcb has joined #openstack-meeting-alt13:58
edleafe#startmeeting nova_scheduler14:00
openstackMeeting started Mon Oct 23 14:00:12 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
edleafe#link Agenda for this meeting https://wiki.openstack.org/wiki/Meetings/NovaScheduler#Agenda_for_next_meeting14: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
edleafeWho's here?14:00
alex_xuo/14:00
mriedemo/14:00
takashin\o14:00
efried\o14:00
*** cdent_ has joined #openstack-meeting-alt14:00
jaypipeso/ for fifteen minutes14:01
edleafejaypipes: Do you have anything you need to discuss? We can do that first14:01
cdent_o/14:02
jaypipesedleafe: just to say I will be pretty useless the next couple days. :( I'm mostly in meetings in Buffalo and doing new-hire things.14:02
edleafeah, ok14:03
jaypipesedleafe: and learning how to hate^Wuse this fucking Mac.14:03
* bauzas waves super-busy14:03
edleafe"Why won't it work like it isn't a Mac????"14:03
edleafeLet's get started then14:04
edleafe#startmeeting nova_scheduler14:04
openstackedleafe: Error: Can't start another meeting, one is in progress.  Use #endmeeting first.14:04
edleafe#link Agenda for this meeting https://wiki.openstack.org/wiki/Meetings/NovaScheduler#Agenda_for_next_meeting14:04
edleafeoops bad copy/paste14:04
cdent_jaypipes: did you end up with one with a touchbar? worst mac yet, I reckon.14:04
edleafe#undo14:04
openstackRemoving item from minutes: #link https://wiki.openstack.org/wiki/Meetings/NovaScheduler#Agenda_for_next_meeting14:04
edleafe#topic Specs14:04
edleafeOnly one spec remaining spec - is this pushed to Rocky?14:04
edleafe#link Add spec for symmetric GET and PUT of allocations https://review.openstack.org/#/c/508164/14:04
*** openstack changes topic to "Specs (Meeting topic: nova_scheduler)"14:04
mriedemon ^,14:04
cdent_talked about that last week, it’s got a this cycle dependency14:04
mriedemcdent asked about that last week,14:04
cdent_jinx14:04
*** cdent_ is now known as cdent14:05
mriedemyeah the POST allocations one right?14:05
cdentyeah14:05
mriedemand the migration uuid stuff depends on that14:05
cdents/depends on/desires/14:05
edleafeIs there a blocker?14:06
mriedemok - yeah, but i think that one gets a pass14:06
cdentedleafe: just lack of reviews as far as I can tell14:06
edleafeAnything else for Specs?14:07
edleafe#topic Reviews14:07
*** openstack changes topic to "Reviews (Meeting topic: nova_scheduler)"14:07
edleafe#link Nested RP series starting with: https://review.openstack.org/#/c/415921/14:07
edleafeSaw that one merged last week14:07
edleafeLooks like this series is moving ahead14:07
edleafejaypipes: any issues for that?14:08
jaypipesedleafe: nothing other than to say I will not be getting to any new revisions until Wednesday14:08
bauzasedleafe: well, mostly the de-orm stuff merged14:08
edleaferoger that14:08
*** jtomasek has quit IRC14:08
edleafenext up14:09
edleafe#link Add traits to GET /allocation_candidates https://review.openstack.org/47977614:09
edleafealex_xu: is that on hold pending the other traits patches?14:09
*** jtomasek has joined #openstack-meeting-alt14:09
alex_xuno14:10
efriedSorry, back to the NRP series, jaypipes do you want me to marshal any minor issues until you're back in play?14:10
efriedto keep the series moving?14:10
jaypipesefried: I'll let you know later. Need to read any reviews from the latest revisions.14:10
efriedjaypipes ack14:10
alex_xuI rewrite all the patches again. Try to refactor the AllocationCandidates.get_by_filters14:11
edleafealex_xu: ok14:11
edleafenext14:11
edleafe#link Allow _set_allocations to delete allocations https://review.openstack.org/#/c/501051/14:11
edleafeThat had a +2 before rebase. Just needs some more reviews14:11
mriedemdoes ^ change api behavior at all?14:12
cdentnot yet, no, that’s higher in the stack14:13
edleafemriedem: it adds a new microversion14:13
edleafeopps14:13
edleafethat's the next patch14:13
mriedemok because i remember we put a minLength of 1 on PUT allocations14:13
* edleafe is getting ahead of himself14:13
mriedembecause of some bug at one point14:13
cdentthe functionality is for POST, and _not_ for PUT14:13
mriedembug 167322714:13
openstackbug 1673227 in OpenStack Compute (nova) ocata "placement apis for inventory and allocations use insufficiently robust jsonschema" [Medium,Confirmed] https://launchpad.net/bugs/167322714:13
mriedemah ok14:14
cdentbut changes are present in that stack for GET, PUT, POST, because the representations are all intwined14:14
cdentso at somem point later in the stack a POST schema is made which make minLength 014:14
edleafeThis is the one that adds a microversion:14:15
edleafe#link POST /allocations for >1 consumer https://review.openstack.org/#/c/500073/14:15
edleafe^ that's important for migrations, right?14:15
mriedemyes,14:15
cdentyes, that’s the top of the stack we just talking about, and is the thing “desired” by migrations14:15
mriedembecause we move the allocation from the source node provider and the instance to the migration uuid14:16
mriedemand put the instance uuid allocatoin on the dest node provider14:16
edleafeI'll re-review it later today14:18
edleafenext up14:18
edleafe#link Use ksa adapter for placement https://review.openstack.org/#/c/492247/14:18
*** felipemonteiro_ has joined #openstack-meeting-alt14:18
edleafeno controversy there14:18
edleafenext up:14:19
edleafe#link Alternate hosts: series starting with https://review.openstack.org/#/c/486215/14:19
*** felipemonteiro__ has joined #openstack-meeting-alt14:19
edleafeThanks to mriedem for updating that late on a Friday14:19
mriedemi think that's ready to go,14:19
mriedemdan was going to look it over again14:19
mriedemi put a comment for discussion on the selections object patch,14:20
mriedemabout the limits field assuming only integer values,14:20
*** cloudrancher has quit IRC14:20
*** gouthamr has joined #openstack-meeting-alt14:20
mriedembut then kind of doubted myself in my same comment, so didn't -114:20
*** salv-orl_ has quit IRC14:20
mriedemnot sure if you wanted to discuss that now or not14:20
edleafeYeah, I'm unclear on how that is (mis)used in the field14:20
*** salv-orlando has joined #openstack-meeting-alt14:20
mriedemwell, it's assuming in-tree filters that put stuff in the limits dict14:20
*** david-lyle has joined #openstack-meeting-alt14:21
mriedemwhich is numatopologyfilter (which you have a separate field for that limit),14:21
*** cloudrancher has joined #openstack-meeting-alt14:21
mriedemand ram/core/disk filters which do just set an int value for limits,14:21
mriedemmy concern was out of tree filters,14:21
mriedemhowever, any out of tree filter putting stuff in limits must also have out of tree code in the claim/resource tracker code to deal with that limit,14:21
cdentjaypipes: option down arrow14:21
mriedemand while we support out of tree filters, we don't support extending the resource tracker / claims code14:21
mriedemala ERT14:21
jaypipesmriedem: out of tree filters are fundamentally broken with the new resource claiming in placement/scheduler14:22
mriedemjaypipes: not really14:22
mriedemthere are still things we don't claim in the scheduler14:22
mriedemlike numa14:22
jaypipesmriedem: well, they essentially mean we can never get rid of claiming stuff on the compute node.14:22
mriedemand not all out of tree filters would put stuff into the limits dict,14:22
mriedemi'm hoping that most don't14:22
bauzaslimits are useless for out-of-tree filters14:23
jaypipesmriedem: didn't you say huawei did custom out of tree filters?14:23
mriedemand my point is, like i said above, we support out of tree filters, but not extending the RT14:23
*** felipemonteiro_ has quit IRC14:23
bauzasbecause we don't have a custom RT :)14:23
mriedemlots of people use out of tree filters14:23
mriedemand yes huawei has some too14:23
mriedemi don't think they have any that put stuff in the limits dict though14:23
mriedembut it got me thinking about thta14:23
mriedem*that14:23
mriedemagain - we don't have an extendable RT,14:23
mriedemso i think it's a moot point14:24
mriedemlike bauzas reiterated14:24
jaypipesmriedem: all depends on whether you are essentially asking us to make the limits dict-packing thing part of the "API" for custom filters.14:24
jaypipesmriedem: if you are, then we will forever have to live with claims in the compute node.14:24
mriedemi don't think i am now14:24
bauzasin general, people use out-of-tree filters for things they don't *consume*14:24
bauzasbut rather just checking whether the host support *this* or *that*14:24
mriedemi just wanted to make sure i brought it up14:24
jaypipesbauzas: example pls14:25
bauzasjaypipes: just a boolean condition whether HostState has this or that14:25
bauzasnot something saying "I want to consume X foos"14:25
bauzassince we don't have a custom R14:25
bauzasRT14:25
jaypipesbauzas: gotcha. yes, I'm not concerned about those types of filters. I'm concerned about filters that store stuff in limits dict14:26
bauzasjaypipes: like I said, I never saw that because we don't have a modular resource tracking14:26
bauzaspeople use some other way for tracking14:26
bauzaslike an external agent14:26
jaypipesand last I read, mriedemwas concerned about the caching scheduler using the core filters which store stuff in the limits dict for things like cpu, ram, etc14:26
bauzasin that case, they don't care about limits - and tbh, only a very few of them know what are those "limits"14:27
*** jtomasek has quit IRC14:27
mriedemjaypipes: yeah we're good for the caching scheduler now,14:27
mriedemthe limits dict in the selection object will handle the basic in-tree filters we have that put stuff in the limits dict14:27
bauzashonestly, I just feel we should just wait for some usecase if that presents14:27
bauzasand just consider that we only support in-tree limits14:28
bauzaswhich is, tbh, only the NUMA limits IMHO14:28
bauzasbecause CPU, RAM and disk are now accounted differently14:28
jaypipesmriedem: ok, I didn't realize we were doing the limits int dict thing in the Selection object. thought we were only doing the numa_limits specialized field. but ok14:28
mriedembauzas: not if you're using the caching scheduler14:28
mriedemjaypipes: new as of last week at some point14:28
bauzasah meh good point14:28
mriedemwe can move on now i think14:29
bauzasso, 4 limits, that's i(14:29
bauzasyeah14:29
edleafejaypipes: while you were gone they had me add the non-numa limits back in14:29
*** gcb has quit IRC14:29
edleafeOK, moving on.14:29
bauzasmagics of the children vacations, I don't have to leave now and can still hassle you guys for a few more mins :p14:29
edleafe#link Numbered grouping of traits https://review.openstack.org/#/c/514091/14:29
edleafeThat's still WIP, so please chime in with comments14:30
* bauzas should give a medal to the grand-parents14:30
efriedwas talking to alex_xu about this earlier14:30
efriedIt's going to completely change the format of the 'filters' param we're currently using in AllocationCandidates.get_by_filters.14:31
efriedSo, for microversion purposes, I was going to write a get_by_filters_grouped (next patch in the series)14:31
efriedWelcoming comments on that approach.14:31
efriedThat's it.14:31
jaypipeswill try to review that today, efried14:31
edleafeI don't know if I'll have time today (meetings, meetings, etc) but will dig into that patch ASAP14:32
edleafeAnything other reviews to discuss?14:32
*** ccamacho has quit IRC14:32
cdentyeah14:32
cdenthttps://review.openstack.org/#/c/513526/ is Enable limiting GET /allocation_candidates14:33
cdentit’s mostly ready for review, except that efried had one of his usual insights14:33
cdentsuggesting a change, in the comments, that should probably be done, but worth getting some additional input14:33
cdentwhich is if we are randomzing when limit is set, we should also randomize when not14:34
cdent(see the review for details, just want to draw your attention)14:34
edleafe#link Enable limiting GET /allocation_candidates https://review.openstack.org/#/c/513526/14:34
edleafeThanks cdent14:34
edleafe#topic Bugs14:34
*** openstack changes topic to "Bugs (Meeting topic: nova_scheduler)"14:34
edleafe#link Placement bugs https://bugs.launchpad.net/nova/+bugs?field.tag=placement14:34
edleafeA few new ones this week14:34
*** Guest88264 has quit IRC14:35
edleafethe ironic CUSTOM_CUSTOM_FOO one surprised me14:35
edleafeI thought we had normalized the name, instead of always adding CUSTOM_ to what was sent14:35
mriedemi seem to remember bringing this up during impl in the driver14:36
mriedemyeah the assumption was always that you wouldn't use the CUSTOM_ prefix in ironic,14:37
mriedemwhich was probably the wrong assumption14:37
mriedemand nova would just blindly slap it on14:37
edleafeWe didn't want to make operators add CUSTOM_ to their classes, IIRC14:37
mriedemwe don't have to make them,14:38
mriedembut we can check to see if they did anyway14:38
edleafeLooks like johnthetubaguy is on it14:38
mriedemi could see someone thinking things should be consistent in the 3 places14:38
mriedemyeah, reviewing the fix14:38
*** jaypipes has quit IRC14:38
edleafeAnything else for bugs?14:38
johnthetubaguyyeah, it confused me them not being the same in the three places14:38
efriedWe could talk about splitting RCs across RPs in an aggregate.  Or, you know, not.14:39
edleafeefried: is there a bug for that?14:39
*** fnaval has joined #openstack-meeting-alt14:39
efriedbug #1724613 and bug #172463314:39
openstackbug 1724613 in OpenStack Compute (nova) "AllocationCandidates.get_by_filters ignores shared RPs when the RC exists in both places" [Undecided,New] https://launchpad.net/bugs/172461314:39
openstackbug 1724633 in OpenStack Compute (nova) "AllocationCandidates.get_by_filters hits incorrectly when traits are split across the main RP and aggregates" [Undecided,New] https://launchpad.net/bugs/172463314:39
*** jaypipes has joined #openstack-meeting-alt14:40
edleafeWell, discuss away!14:40
efriedIf someone can tell me that there's no actual code anywhere in existence today that makes *use* of the implementation for placement aggregates, I'll be happy with deferring the discussion.14:40
*** chyka has joined #openstack-meeting-alt14:41
*** baoli has quit IRC14:41
efriedBut the existing code in AllocationCandidates.get_by_filters is subject to that first bug right now; and will be subject to the second once alex_xu's traits series is done.14:41
jaypipesdansmith probably remembers the CUSTOM_CUSTOM_FOO discussion14:42
* cdent contacts his omniscience as a service service14:42
dansmithyes14:42
*** baoli has joined #openstack-meeting-alt14:42
efriedTL;DR: if my compute has a RC that is also in an aggregate, things go awry.  E.g. my compute has local disk and is also associated with a shared storage pool.14:42
cdentefried: I think the thing you can be confident of is that spwaning a compute node does not use aggregates yet14:43
efriedGood.  Does anything else?14:43
cdentthere may be unkown uses of aggregates out there, but not any that involve booting an instance14:43
jaypipescdent is correct 100%14:43
efriedIt's a matter of getting allocation candidates, not just booting instances.  But that makes me feel a lot better.14:44
efriedSo I'm happy to leave those bugs out there and defer the discussion.  They have test case code proposed that demonstrates them, which we can merge any time too.14:44
cdentefried: yes, that’s why I qualified myself. GET /allocation_candidates has the bug.14:44
efriedhttps://review.openstack.org/51314914:45
cdentwhether it will be exercised is a different question14:45
* alex_xu just found his refactor doesn't fix that bug also14:45
efriedalex_xu Thanks for testing that.  /me not surprised :)14:45
efriedWe can move on14:46
alex_xunot surprised on the bug of allocation, that is right thing :)14:46
edleafe#topic Open discussion14:46
*** openstack changes topic to "Open discussion (Meeting topic: nova_scheduler)"14:46
edleafeOne item on the agenda:14:47
edleafe#link Should we forbid removing traits from an RP with allocations?  http://eavesdrop.openstack.org/irclogs/%23openstack-nova/%23openstack-nova.2017-10-20.log.html#t2017-10-20T21:34:4414:47
*** anilvenkata has quit IRC14:47
efriedjohnthetubaguy ^14:47
efriedSo my vote is no.  This goes along with what we talked about in Denver wrt inventories being modified downward to the point where they're less than what's already been allocated.14:48
efriedIt's allowed, but you won't get any more allocations until you're back out of the red.14:48
edleafeefried: how does changing an RP's trait affect that?14:49
efriedSame thing with the traits.  You can remove a trait from a RP that's already part of an allocation that may have required that trait, but you won't get scheduled to that RP hereafter if you require that trait (unless it gets re-added)14:49
jaypipesefried: I'd like to hear from operators on that question.14:49
efriededleafe Not a direct relationship, just a similar example.14:49
jaypipesefried: it's a similar conundrum to the instance group member modifications/delete14:49
johnthetubaguycomparing the resource class changes and traits changes in ironic pushes me down that line14:49
cdentyeah, I think “no” is the right thing as well. From the change on, no new placements will happen and we don’t want to remove existing, so...14:49
jaypipesefried: since changing the member set of an instance group affects whether a new or existing instance still is constrained by the placement policy in use at the time of initial scheduling14:50
efriedjaypipes Does the instance grouping affect anything after the deploy, though?14:50
efriedIn the case of traits, that answer is no.14:50
efriedIt's a one-and-done kind of thing.14:51
johnthetubaguythe next live-migration could be odd, no possible hosts as the trait has gone?14:51
jaypipesfwiw, k8s attitude towards this problem is "oh well, shit changed. sorry, go ahead and reschedule if you want"14:51
*** jtomasek has joined #openstack-meeting-alt14:52
jaypipesefried: if I add or remove a member from the affinity group, we do a check on the compute node to ensure that the constraints around affinity are kept for existing members of the group, tyes.14:52
efriedjohnthetubaguy How about this as more concrete example: if you want to shuffle around which nodes are in CUSTOM_GENERAL_USE vs. CUSTOM_PROJECT_B.  Should you have to clear out existing deployments before you can do that, or is it okay if they just take effect "the next time"?14:52
mriedemi've heard people talk about using traits from external systems to dynamically flag if something is available, or not if something failed,14:53
mriedemlike something in the hardware failed and that component is no longer available, remove the trait so things that require that trait don't get scheduled there14:53
jaypipesmriedem: pls no... traits are not for state/status information14:53
efriedThat's still a capability statement.14:53
jaypipesno it's not.14:54
alex_xujaypipes: traits are not for that, but it works14:54
mriedemtraits are going to be used for dynamic scheduling14:54
mriedemwhether we intended them to be or not14:54
jaypipesefried: that is a different thing. whether or not I am capable of chewing gum and patting my head simultaneously is not the same thing as whether or not I am chewing gum and patting my head currently.14:54
efriedjaypipes Totally agree - been discussing same on the ML.14:55
jaypipesmriedem: if that's the case, we might as well give up and just reinstate the ERT, undo all of placement API and just use kubernetes.14:55
efriedjaypipes What we're talking about here is, if I cut off both your hands, you're no longer capable of doing that, so that trait should be removed from you.14:55
jaypipesefried: sure, but what mriedem is talking about is some external agent that is constantly cutting off my hands and reattaching them when, say, a NIC state link goes up or down.14:56
johnthetubaguyefried: I want to be able to fix things right away, myself14:56
jaypipesjohnthetubaguy: what do you mean by "fix things right away:"?14:57
johnthetubaguyI don't want to have to wait for a node to be free before I define how/who/what it gets used for next time14:57
efriedjaypipes Which seems reasonable to me, tbh.  I don't know about link state specifically, how fast that can flip on and off, but if someone trips over a cable, I don't want to deploy new instances there until they plug it back in.14:57
edleafeTwo minutes left14:58
jaypipesjohnthetubaguy: I don't see how that is relevant here? if we only use traits for capabilities (and not for state information) then you don't have that problem.'14:58
jaypipesefried: ugh.14:58
jaypipesefried: that is NOT a capability. that is a state/status link.14:58
*** yamahata has joined #openstack-meeting-alt14:58
*** cloudrancher has quit IRC14:58
jaypipesefried: see the nic-state-aware-scheduling spec/blueprint for a lengthy discussion of where this leads to...14:58
cdentwhatever we want people to do with these things, we have to be aware of what people _will_ do14:59
johnthetubaguyjaypipes: so its the only way we have to do non-capability things right now, so that's what is getting used14:59
edleafeSounds like this can be summed up as: can the capabilities of a "thing" change?14:59
*** cloudrancher has joined #openstack-meeting-alt14:59
edleafeOK, thanks everyone!15:00
edleafeContinue this in -nova15:00
edleafe#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:00
openstackMeeting ended Mon Oct 23 15:00:08 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-10-23-14.00.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_scheduler/2017/nova_scheduler.2017-10-23-14.00.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_scheduler/2017/nova_scheduler.2017-10-23-14.00.log.html15:00
jaypipesefried: we ALREADY check the service group API during every single scheduling loop, removing any services that are down/disabled from the scheduling decisions. The recommended approach for things like NIC-state aware scheduling was to have an external agent call nova-manage service disable when a link goes down15:00
*** takashin has left #openstack-meeting-alt15:00
*** mriedem has left #openstack-meeting-alt15:01
*** ccamacho has joined #openstack-meeting-alt15:01
*** markstur has joined #openstack-meeting-alt15:02
*** yangyapeng has joined #openstack-meeting-alt15:03
*** yangyapeng has quit IRC15:04
*** yangyapeng has joined #openstack-meeting-alt15:04
*** jaypipes has quit IRC15:11
*** kumarmn has joined #openstack-meeting-alt15:12
*** jaypipes has joined #openstack-meeting-alt15:12
*** baoli has quit IRC15:13
*** jaypipes has quit IRC15:14
*** jaypipes has joined #openstack-meeting-alt15:16
*** jaypipes has quit IRC15:18
*** salv-orlando has quit IRC15:19
*** salv-orlando has joined #openstack-meeting-alt15:20
*** cdent has quit IRC15:20
*** mjura has quit IRC15:23
*** baoli has joined #openstack-meeting-alt15:24
*** ushkalim has quit IRC15:24
*** kumarmn has quit IRC15:26
*** dsariel has quit IRC15:33
*** kumarmn has joined #openstack-meeting-alt15:36
*** ccamacho has quit IRC15:36
*** marios has quit IRC15:37
*** kumarmn_ has joined #openstack-meeting-alt15:37
*** gyee has joined #openstack-meeting-alt15:37
*** jpena is now known as jpena|brb15:40
*** kumarmn has quit IRC15:41
*** kumarmn_ has quit IRC15:42
*** rmart04 has joined #openstack-meeting-alt15:49
*** dsariel has joined #openstack-meeting-alt15:49
*** cdent has joined #openstack-meeting-alt15:52
*** jkilpatr has quit IRC15:55
*** cloudrancher has quit IRC16:04
*** cloudrancher has joined #openstack-meeting-alt16:05
*** markstur_ has joined #openstack-meeting-alt16:08
*** oidgar has quit IRC16:09
*** markstur has quit IRC16:11
*** jpena|brb is now known as jpena16:19
*** egallen has quit IRC16:19
*** cdent has left #openstack-meeting-alt16:23
*** yamahata has quit IRC16:25
*** lpetrut has quit IRC16:30
*** achadha has joined #openstack-meeting-alt16:30
*** achadha has quit IRC16:31
*** achadha has joined #openstack-meeting-alt16:31
*** jkilpatr has joined #openstack-meeting-alt16:32
*** derekh has quit IRC16:45
*** rmart04 has quit IRC16:49
*** diablo_rojo has joined #openstack-meeting-alt16:50
*** dsariel has quit IRC16:51
*** rossella_s has quit IRC16:51
*** ralonsoh has quit IRC16:57
*** jcoufal has quit IRC17:05
*** diablo_rojo has quit IRC17:07
*** yamahata has joined #openstack-meeting-alt17:08
*** salv-orlando has quit IRC17:09
*** salv-orlando has joined #openstack-meeting-alt17:10
*** salv-orlando has quit IRC17:14
*** bfernando has quit IRC17:15
*** jpena is now known as jpena|off17:16
*** katyafervent_awa has quit IRC17:16
*** meow-nofer_ has quit IRC17:16
*** pashkin has quit IRC17:16
*** rakhmerov has quit IRC17:17
*** dprince has quit IRC17:17
*** diablo_rojo has joined #openstack-meeting-alt17:17
*** IgorYozhikov has quit IRC17:17
*** akuznetsova has quit IRC17:17
*** asilenkov has quit IRC17:17
*** lpetrut has joined #openstack-meeting-alt17:18
*** tesseract has quit IRC17:18
*** rakhmerov has joined #openstack-meeting-alt17:21
*** pashkin has joined #openstack-meeting-alt17:21
*** IgorYozhikov has joined #openstack-meeting-alt17:22
*** akuznetsova has joined #openstack-meeting-alt17:22
*** sambetts is now known as sambetts|afk17:23
*** katyafervent_awa has joined #openstack-meeting-alt17:23
*** meow-nofer_ has joined #openstack-meeting-alt17:24
*** asilenkov has joined #openstack-meeting-alt17:24
*** rmascena has joined #openstack-meeting-alt17:28
*** lpetrut has quit IRC17:29
*** raildo has quit IRC17:30
*** cloudrancher has quit IRC17:36
*** cloudrancher has joined #openstack-meeting-alt17:36
*** ijw has joined #openstack-meeting-alt17:36
*** cloudrancher has quit IRC17:37
*** cloudrancher has joined #openstack-meeting-alt17:37
*** egallen has joined #openstack-meeting-alt17:38
*** dprince has joined #openstack-meeting-alt17:39
*** egallen has quit IRC17:46
*** sridharg has quit IRC17:49
*** ijw has quit IRC17:50
*** kylek3h has quit IRC17:56
*** kylek3h has joined #openstack-meeting-alt17:56
*** baoli has quit IRC18:11
*** baoli has joined #openstack-meeting-alt18:12
*** baoli has quit IRC18:12
*** baoli has joined #openstack-meeting-alt18:18
*** jcoufal_ has joined #openstack-meeting-alt18:21
*** achadha has quit IRC18:24
*** achadha has joined #openstack-meeting-alt18:24
*** rwsu has quit IRC18:29
*** rmcallis has joined #openstack-meeting-alt18:38
*** harlowja has joined #openstack-meeting-alt18:53
*** arxcruz- has joined #openstack-meeting-alt19:05
*** achadha_ has joined #openstack-meeting-alt19:06
*** achadha has quit IRC19:08
*** jgriffith has joined #openstack-meeting-alt19:10
*** achadha_ has quit IRC19:10
*** jgriffith has quit IRC19:11
*** jgriffith has joined #openstack-meeting-alt19:11
*** jgriffith has quit IRC19:11
*** slaweq has joined #openstack-meeting-alt19:12
*** jgriffith has joined #openstack-meeting-alt19:15
*** jgriffith has quit IRC19:37
*** jgriffith has joined #openstack-meeting-alt19:38
*** MarkBaker has quit IRC19:42
*** MarkBaker has joined #openstack-meeting-alt19:44
*** achadha has joined #openstack-meeting-alt20:13
*** achadha has quit IRC20:18
*** salv-orlando has joined #openstack-meeting-alt20:33
*** salv-orlando has quit IRC20:37
*** salv-orlando has joined #openstack-meeting-alt20:37
*** dprince has quit IRC20:37
*** baoli has quit IRC20:44
*** lpetrut has joined #openstack-meeting-alt20:45
*** rmascena has quit IRC20:50
*** baoli has joined #openstack-meeting-alt20:50
*** baoli has quit IRC20:50
*** ijw has joined #openstack-meeting-alt20:54
*** MeganR has joined #openstack-meeting-alt20:55
*** jprovazn has quit IRC20:55
*** Arkady_Kanevsky has joined #openstack-meeting-alt20:57
*** jgriffith has quit IRC20:59
Arkady_Kanevsky#startmeeting product_working_group21:00
openstackMeeting started Mon Oct 23 21:00:05 2017 UTC and is due to finish in 60 minutes.  The chair is Arkady_Kanevsky. 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
Arkady_Kanevsky#chair Arkady21:00
openstackWarning: Nick not in channel: Arkady21:00
openstackCurrent chairs: Arkady Arkady_Kanevsky21:00
*** jgriffith has joined #openstack-meeting-alt21:00
*** baoli has joined #openstack-meeting-alt21:00
Arkady_Kanevsky#topic rollcall21:00
*** openstack changes topic to "rollcall (Meeting topic: product_working_group)"21:00
Arkady_Kanevskywho from PWG is here?21:01
MeganRo/21:01
Arkady_KanevskyHi Megan21:01
MeganRHi, how are you doing this week?21:01
*** jcoufal_ has quit IRC21:01
Arkady_Kanevskybusry getting ready for summit.21:02
Arkady_Kanevskywhat about you?21:02
MeganRBusy - was traveling last week, and still feel like I am playing catch-up  :)21:03
Arkady_Kanevskyusual. Coming to Sydney?21:03
MeganRNo, unfortunately not :(21:03
Arkady_Kanevskyunderstand.21:04
Arkady_Kanevsky#topic Review action items from previous meeting21:04
*** openstack changes topic to "Review action items from previous meeting (Meeting topic: product_working_group)"21:04
Arkady_KanevskyAgenda at https://wiki.openstack.org/wiki/Meetings/product-team21:04
MeganRdo we have enough people for a meeting?21:04
Arkady_Kanevskylast week AIs are at http://eavesdrop.openstack.org/meetings/product_working_group/2017/product_working_group.2017-10-16-21.01.html21:04
Arkady_KanevskyNo progress on the first - Arkady_Kanevsky and shamail to work on updated development proposal workflow to be used in Sydne21:05
Arkady_KanevskyI cannot access https://docs.google.com/presentation/d/1nU1DnyFxVlck3lvR7GrXI8tjQaMMIy0GFLPsYzne7ag/edit#slide=id.g1f441c5038_0_18921:05
Arkady_KanevskySend request to SHamail on it21:05
Arkady_Kanevskysecond - All - Please add items to be discussed at working session in Sydney to the working session etherpad21:06
Arkady_KanevskyMegan, had you had a chance to review it and add items for Sydney?21:06
MeganRI have not, will add it to my list for this week21:07
Arkady_KanevskyOK.21:07
Arkady_Kanevskythird - Leong will create draft presentation for BoF session. - done21:07
Arkady_KanevskyLeong sent pointer to slidedeck https://docs.google.com/presentation/d/1QIrak-jK-jok9fShAqtMMD4F_Yk3GNhXPjg3YqOsKHY/edit?ts=59ee4348#slide=id.g2709aae4ca_0_26421:07
Arkady_KanevskyNobody had a chance to review since he sent it only today.21:08
Arkady_KanevskyAnything else on AIs fomr last week?21:08
Arkady_Kanevskyhereing none - lets move on21:09
Arkady_Kanevsky#topic Sydney Plan Working Session21:09
*** openstack changes topic to "Sydney Plan Working Session (Meeting topic: product_working_group)"21:09
Arkady_Kanevskyschedule - https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20411/product-working-group-wg21:09
*** julim has quit IRC21:09
Arkady_KanevskyEtherpad for it - https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20411/product-working-group-wg21:09
Arkady_KanevskyAIs from last meeting stands to add more agenda topics21:10
Arkady_KanevskyMegan, anything else for Working group session?21:11
MeganRI don't have anything21:11
Arkady_KanevskyOK.21:11
Arkady_KanevskyNext one is BOF21:11
Arkady_Kanevsky#topic Sydney Plan BOF21:12
*** ijw has quit IRC21:12
*** openstack changes topic to "Sydney Plan BOF (Meeting topic: product_working_group)"21:12
Arkady_KanevskySchedule - https://www.openstack.org/summit/sydney-2017/summit-schedule/events/20412/product-working-group-bof21:12
Arkady_KanevskyLeong sent a draft presentation - https://docs.google.com/presentation/d/1QIrak-jK-jok9fShAqtMMD4F_Yk3GNhXPjg3YqOsKHY/edit21:12
Arkady_KanevskyAI: Please, review it and comment.21:13
MeganRok21:13
Arkady_Kanevsky#topic Sydney summit SIG/WG/UC meeting21:14
*** openstack changes topic to "Sydney summit SIG/WG/UC meeting (Meeting topic: product_working_group)"21:14
*** slaweq has quit IRC21:14
Arkady_KanevskyThat is sync up meteing with SIG.21:14
Arkady_KanevskyInclude 2 presentation from us requirement review and on progress tracking.21:15
Arkady_KanevskyAI: Arkady to draft slide deck for both21:15
*** slaweq has joined #openstack-meeting-alt21:15
Arkady_Kanevsky#topic opne items21:15
*** openstack changes topic to "opne items (Meeting topic: product_working_group)"21:15
Arkady_KanevskyMegan, any open issues?21:15
MeganRno, nothing for open21:16
Arkady_KanevskyOK.21:17
Arkady_KanevskySummarizing AIs.21:17
Arkady_Kanevsky#action All review forum session agenda21:17
*** achadha has joined #openstack-meeting-alt21:17
Arkady_Kanevsky#action All review BOF presentation21:17
Arkady_Kanevsky#action Arkady Workflow presentation draft for SIG/WG/UC meeting21:18
Arkady_Kanevsky#action Arkady Requirement progress tracking presentation draft for SIG/WG/UC meeting21:18
Arkady_KanevskyHave a great day.21:18
Arkady_Kanevsky#endmeeting21:19
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:19
openstackMeeting ended Mon Oct 23 21:19:03 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:19
openstackMinutes:        http://eavesdrop.openstack.org/meetings/product_working_group/2017/product_working_group.2017-10-23-21.00.html21:19
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/product_working_group/2017/product_working_group.2017-10-23-21.00.txt21:19
openstackLog:            http://eavesdrop.openstack.org/meetings/product_working_group/2017/product_working_group.2017-10-23-21.00.log.html21:19
*** MeganR has quit IRC21:19
*** slaweq has quit IRC21:20
*** ijw has joined #openstack-meeting-alt21:22
*** xyang1 has quit IRC21:26
*** ijw has quit IRC21:27
*** dave-mccowan has quit IRC21:28
*** iyamahat has joined #openstack-meeting-alt21:28
*** iyamahat_ has joined #openstack-meeting-alt21:28
*** ijw has joined #openstack-meeting-alt21:42
*** Shrews has joined #openstack-meeting-alt21:42
*** achadha_ has joined #openstack-meeting-alt21:43
*** tpsilva has quit IRC21:44
*** achadha has quit IRC21:44
*** slaweq has joined #openstack-meeting-alt21:45
*** achadha_ has quit IRC21:48
*** ijw has quit IRC21:49
*** jgriffith has quit IRC21:50
*** lpetrut has quit IRC21:55
*** jgriffith has joined #openstack-meeting-alt21:58
jeblairanyone around for a zuul meeting?22:00
* fungi is wandering around these parts22:00
Shrewso/22:00
pabelangerhello22:01
jeblair#startmeeting zuul22:01
openstackMeeting started Mon Oct 23 22:01:31 2017 UTC and is due to finish in 60 minutes.  The chair is jeblair. Information about MeetBot at http://wiki.debian.org/MeetBot.22:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.22:01
*** openstack changes topic to " (Meeting topic: zuul)"22:01
openstackThe meeting name has been set to 'zuul'22:01
jeblairthere is no agenda for this meeting -- so let's start by asking if there's anything folks want to talk about :)22:02
jeblairi'd like to give folks a quick heads up on some branch-related issues i've started digging into22:03
fungipoint of order: zuul v3 is awesome22:03
pabelangeryes it is!22:03
Shrewsi have a topic22:03
jeblairShrews: what's that?22:04
jeblairand maybe we should give the issues etherpad a quick once-over?22:04
Shrewsi've been working on migrating the nodepool jobs (https://review.openstack.org/#/q/topic:nodepool-migration+status:open). all of those (except the WIP) could use reviews22:04
jeblairShrews: very meta!22:04
Shrewsso i need some nodepool core's to get active there22:04
jeblairokay, if you have other topics, let me know and we'll wing it22:05
jeblair#topic zuulv3 issues22:05
*** openstack changes topic to "zuulv3 issues (Meeting topic: zuul)"22:05
Shrewsjeblair: it's all been very confuzzling trying to get everything in all the projects in the right order, so i sympathize with our users22:05
jeblairShrews: good! we're supposed to do that :)22:06
jeblairso first thing, i guess: is that we're still in firefighting mode22:06
jeblair#link https://etherpad.openstack.org/p/zuulv3-issues22:07
jeblairthat etherpad is active22:07
jeblairif you have time to jump on issues there, please do so22:07
jeblairi think most of the issues under zuul are being worked in some form or other22:08
*** iyamahat_ has quit IRC22:08
jeblairanyone have any questions about those?22:08
*** iyamahat has quit IRC22:08
jeblairfungi: i left a comment on your sqlreporter patch22:08
*** ijw has joined #openstack-meeting-alt22:08
fungithanks!22:08
fungiit may be the comment to which i already responded22:09
jeblairfungi: briefly: i think we can merge that as a quick fix, but there's a slightly larger patch that we should write soon -- before we have tristanC's dashboard22:09
dmsimard\o sorry I'm late22:09
fungijeblair: yep, i'm good either way and happy to work on the more correct solution, just looking for pointers from someone with a deeper knowledge of the orm bits22:10
jeblairfungi: ah yeah, so i think we'll want a migration to allow nulls22:10
jeblairbasically, if we do it now, all we need to do is change the column; if we do it later, we'll need to 'update buildset set change=null where change=0' or something.  not too big of a deal.22:10
fungii also added a related issue to the pad22:11
*** ijw has quit IRC22:11
dmsimardI guess we will need to unfreeze the v2 files to let https://review.openstack.org/#/c/507180/ merge22:12
fungimay be helpful if one reporter breaking doesn't cause zuul to skip other reporters22:12
jeblairfungi: and yeah, i don't think there's any work in progress to make the reporters more idempotent.22:12
jeblairi think the only trick there is what to do if gerrit fails to merge the change.  if we make them idempotent, does that impact any of the subsequent reporters?22:13
jeblair(currently, if gerrit fails to merge, no other reporters run)22:13
*** ijw has joined #openstack-meeting-alt22:13
jeblairmy inclination would be to make them idempotent.  we can't do a two-phase commit across them, so no use pretending we do.  :)22:13
* clarkb wanders by late22:14
fungiahh, yeah, seems like reporters which also merge changes are a slightly different class than those which just provide data22:14
jeblairfungi: is the failing proposal a zuul issue or job issue?22:14
*** Arkady_Kanevsky has quit IRC22:14
fungii put it under zuul since the patch will be to zuul's codebase22:15
fungioh, wait, failing proposals22:15
jeblairhttp://logs.openstack.org/periodic/git.openstack.org/openstack/requirements/stable/newton/propose-updates/a515bba/job-output.txt.gz22:15
jeblairthat link ^22:15
fungiwe've switched subtopics, sorry ;)22:15
fungii saw that on the pad and am trying to regain my former context there22:15
clarkbthats a job issue using ZUUL_REFNAME right?22:16
clarkb(which is not something we'll continue to provide in v3)22:16
fungioh, right, this issue got somehow split from the refname details22:17
jeblairclarkb: i think zuul_refname is sometimes provided by the legacy filter22:17
*** iyamahat has joined #openstack-meeting-alt22:17
clarkbiirc the comment in the filter says it is intentionally ommitted but unsure if 100% of the time22:18
*** slaweq has quit IRC22:18
jeblairclarkb: that's zuul_ref.  refname should be there for non-change items.22:18
clarkboh right22:18
clarkbthis is the thing where we had to set refname explicitly on old v2 periodic jobs22:19
*** ijw has quit IRC22:19
fungiso... for periodic pipeline jobs i don't think v2 provided one at all22:19
clarkbfungi: correct, it was hardcoded on the job before iirc since we had a job per branch22:19
fungiand, yeah, i think this has since been solved?22:19
clarkbbut I want to say that was lost in the conversion process. And ya I want to say the job was updated ?22:19
clarkbto just use what the checkout is rather than try and checkout in the job body itself?22:19
jeblair"propose-updates" should, by virtue of not having the word legacy in it, not be using ZUUL_ vars22:20
jeblairso hopefully things are as clarkb says22:20
clarkbjeblair: ya its in the script it runs so the jjb bits didn't but then the script in jenkins/scripts did/does22:20
pabelangeryah, are they using parent: base?22:20
* clarkb looks to see if that was cleaned22:20
fungiright, the issue was within the scripts it runs, which to retain backward-compat in case of a rollback (we hadn't decided no rollback yet at that point) it was retained in the script22:20
clarkb# Zuul v3 adds refs/heads, remove that to get the branch22:21
clarkbthen22:21
clarkbZUUL_REFNAME=${ZUUL_REFNAME#refs/heads/}22:21
*** kumarmn has joined #openstack-meeting-alt22:22
clarkbya I think this was addressed based on the git log22:22
fungithe job is getting past that point now, so i think it can be updated to whatever the new failure reason is or moved to the fixed list and a new issue added for the new failure mode22:22
fungi#link http://logs.openstack.org/periodic/git.openstack.org/openstack/requirements/stable/newton/propose-updates/35f37e8/job-output.txt.gz22:22
fungithat's from today's run22:23
jeblairoh. it's an old job masquerading as a new one.22:23
clarkbfungi: yup I agree22:23
pabelangerya, propose-update jobs parents to base, we should likey change that to legacy-base if still using zuul-cloner22:23
*** ijw has joined #openstack-meeting-alt22:23
jeblairif it's not using legacy-base, how's it getting ZUUL_REFNAME?22:23
clarkbjeblair: it is populatign it itself22:23
jeblairfrom?22:24
fungialso, and perhaps related (or perhaps not?) this looks like the job to generate constraints updates, but we're not supposed to run that for any branch besides master because we freeze constraints on stable branches22:24
jeblairfungi: i think AJaeger had a patch to fix that today22:24
clarkbjeblair: not sure yet  but where I am reading it it is passed as a cli arg to the script22:24
clarkbplaybooks/proposal/propose-updates.yaml:      command: "{{ ansible_user_dir }}/scripts/propose_update.sh {{ update_target }} {{zuul.branch}}"22:25
fungi#link http://git.openstack.org/cgit/openstack-infra/project-config/tree/jenkins/scripts/propose_update.sh#n9122:25
fungipasses it in there22:25
jeblairah, ok.22:25
jeblairso yeah, that should be pretty v3-safe.22:25
pabelangercool22:25
jeblairand now that we've decided to stop maintaining backwards compat, we can remove the ZUUL_REFNAME references from the script22:26
pabelangermy main concern is when we move forward with https://review.openstack.org/513506/ if that jobs was still using zuul-cloner too22:26
pabelangerbut, looks to be okay also22:26
fungijeblair: agreed22:26
jeblairpabelanger: we should probably only merge that change after we remove zuul-cloner from images22:26
clarkbfungi: and ya current issue looks like update-constraints has moved on from newton and grown some new flags that we should just avoid using against stable branches22:27
jeblairpabelanger: otherwise, i think it will have the opposite effect (zuul-cloner will work "better" because it doesn't "need required-projects" any more) :)22:27
pabelangersure, I'm trying to avoid having jobs move to parent: base while using zuul-cloner22:28
*** slaweq has joined #openstack-meeting-alt22:28
jeblairpabelanger: i understand.  that change won't stop that until we remove zuul-cloner from images.22:28
pabelangerwhen do you think we'd remove zuul-cloner22:28
pabelanger(from images)22:28
jeblairpabelanger: as soon as someone writes that change, i would think.  now that we've decided not to roll back.22:29
dmsimardThe shim?22:29
pabelangerjeblair: ack22:29
clarkbdmsimard: the actual installation that the shim then goes in over the top of22:29
dmsimardAh, okay.22:29
jeblairso if you're a legacy job, you still get the shim.  if you're not, there is no zuul-cloner.22:30
jeblaironly zuul.22:30
dmsimard:)22:30
pabelanger++22:30
fungi;)22:30
jeblairokay, anything else from the etherpad jump out at anyone?22:30
*** baoli has quit IRC22:30
jeblair#topic nodepool jobs22:31
clarkbdo we still need to restart executors for latest ssl fix?22:31
*** openstack changes topic to "nodepool jobs (Meeting topic: zuul)"22:31
jeblair#undo22:31
openstackRemoving item from minutes: #topic nodepool jobs22:31
dmsimardOn my end, mostly the ara wsgi thing. I think that would easily allow us to have 1) ara reports all the time 2) at a much lower cost22:31
fungiclarkb: yes, i can probably knock out some new executor restarts this evening if that has merged now22:31
jeblairclarkb: i think we do, yes.22:31
clarkbok let me know if I can help with those22:31
*** iyamahat has quit IRC22:32
*** iyamahat_ has joined #openstack-meeting-alt22:32
fungiyou can most certainly help. i'm merely volunteering ;)22:32
fungiwe can split them up or whatever22:32
clarkbI'e ended up down the bwrap rabbit hole today due to that too fwiw :P22:32
jeblairdmsimard: do we need any new ara releases for that?22:32
dmsimardjeblair: nope. Just a wsgi script which, pending a new release, is in-tree in puppet-openstackci22:32
fungii'm still helping hammer on the release jobs (latest fun is tag-releases can't auth to lp when it wants to add bug comments)22:32
dmsimardThe wsgi script will be bundled in ara on the next release so we can just stop carrying it.22:33
dmsimardOh, on that note, Ansible 2.4.1 should be out this Wednesday.22:34
dmsimardAlong with the new release of ara to support 2.4.1 properly.22:34
*** salv-orlando has quit IRC22:34
jeblairdmsimard: cool.  i'm somewhat inclined to defer that until after we manage to release openstack.  we have delayed the release, and it may be best to avoid risking further disruption for something not immediately on fire right now.22:34
jeblairdmsimard: hopefully that's not long though.  :)22:34
*** salv-orlando has joined #openstack-meeting-alt22:34
dmsimardSure22:34
dmsimardreviews in the meantime are appreciated, even if we don't deploy it yet22:35
jeblair(i totally want ara back though, i have missed it.  :)22:35
clarkb++ re getting release working first22:35
jeblair#topic nodepool jobs22:36
*** openstack changes topic to "nodepool jobs (Meeting topic: zuul)"22:36
jeblair#link please review https://review.openstack.org/#/q/topic:nodepool-migration+status:open22:37
jeblairShrews: what issues did you run into when doing that?22:37
Shrewsjeblair: first and foremost was understanding the PTI policy and the reasoning behind it. but i understand that now22:38
jeblaircool.  i think there are maybe some grey areas there still... i was thinking of bringing it up at tomorrow's infra meeting.22:39
*** salv-orlando has quit IRC22:39
Shrewsjeblair: the other was understanding the job variants and disabling a template job for certain branches.22:39
Shrewsjeblair: yeah, i've seen others have the same confusion in #-infra22:40
*** chyka has quit IRC22:40
*** chyka has joined #openstack-meeting-alt22:40
jeblairyeah, i think that's squarely in the grey area.  basically: where should a project disable or alter a PTI job.22:40
*** achadha has joined #openstack-meeting-alt22:41
*** achadha has quit IRC22:42
Shrewsthanks to pabelanger, all changes to project-config to remove the problematic templates have merged22:43
*** achadha has joined #openstack-meeting-alt22:43
Shrewshttps://review.openstack.org/512637 implements the py27 jobs directly22:43
*** ijw has quit IRC22:43
Shrewshttps://review.openstack.org/513766 is for the feature/zuulv3 branch (and py35 jobs)22:43
Shrewswe should get those merged ASAP to have py27 and py35 jobs running22:44
*** ijw has joined #openstack-meeting-alt22:44
jeblairwe should probably dust off the zuul-nodepool integration job when we have a few mins too.22:44
Shrewsjeblair: yeah. i want to move to the non-legacy devstack job too. but first things first22:45
clarkbare no jobs running now because we are in an in between state?22:45
jeblairShrews: ++22:45
Shrewsclarkb: dsvm jobs are, but yeah22:45
* clarkb makes note to review those after the meeting22:45
Shrewsclarkb: many thanks!22:45
jeblair#topic stable branch issues22:46
*** openstack changes topic to "stable branch issues (Meeting topic: zuul)"22:46
jeblairin tracking down some of the issues on the etherpad, i realized there are some issues with zuul's configuration system and stable branches22:47
jeblairat the end of last week, i wasn't even in a position to articulate what the issues were22:47
jeblairbut i took a moleskine with me on a hike this weekend to try to work through it22:48
*** achadha has quit IRC22:48
*** achadha has joined #openstack-meeting-alt22:48
* dmsimard googles moleskine22:48
*** kumarmn has quit IRC22:48
jeblairand i think i've got a handle on them.  i think there are 5 related problems, and they all pretty much need to be solved simultaneously.22:49
fungidead-tree notebook22:49
*** dave-mccowan has joined #openstack-meeting-alt22:49
jeblairi think i also just about have solutions to them as well22:49
Shrewsdmsimard: jeblair is old school. you should ask to see his camera sometime  :)22:49
jeblairor at least, a first pass at a solution22:49
dmsimardShrews: it's alright, no problem with that. English is not my first language so sometimes there's one of those new words... :)22:50
* Shrews hopes jeblair got some good photos on the hike22:50
jeblairmy hope is to finish working through this, and then describe the problems along with some proposed solutions22:50
dmsimardYou're keeping us in suspense22:51
jeblairi've dug into this now, because i think as soon as people really try to use some of the branch stuff in earnest, we're going to hit problems that don't currently have good solutions.22:51
dmsimardTelling us there's a problem, that you have a solution but no details :(22:52
jeblairi don't have a solution.  i think i'm close to having a solution.22:52
jeblairi could describe everything now, but i feel like i'd be wasting people's time.22:52
dmsimardOk, so, anything to look out for ?22:53
*** achadha has quit IRC22:53
jeblairbasically, i think i should at least be able to describe the problems fully before i waste anyone else's time.22:53
*** markstur_ has quit IRC22:53
jeblairbut i wanted to mention it so that folks know there's some undesirable behavior around stable branches22:54
jeblairand if you see any issues related to that, send them to me22:54
dmsimardAck.22:54
Shrewsi was not aware of issues in that area, but will keep an eye out now. thx for the info22:54
*** ijw has quit IRC22:54
jeblairi'm hoping i'll be able to write up my findings by tomorrow.22:55
*** achadha has joined #openstack-meeting-alt22:55
*** ijw has joined #openstack-meeting-alt22:55
jeblairin like, legible electronic form.  not what's in the moleskine.22:55
fungithe margin of your moleskine is too narrow to contain the solution?22:55
pabelangerwould be interesting to see them however :)22:55
clarkbyou could send copies via snail mail22:55
jeblairaddressed to clark boylan, c/o convention center, sydney, nsw, australia22:56
clarkbbetter send it air mail22:57
jeblair#topic even more open discussion22:57
*** openstack changes topic to "even more open discussion (Meeting topic: zuul)"22:57
jeblairanything else?22:57
*** janki has joined #openstack-meeting-alt22:57
clarkbI'm gonna pop out for a bit after meeting then will be back to review nodepool job changes and help with executor restarts22:57
pabelangerwas going to ask about powering down zuulv2 servers, but maybe that is for tomorrow infra meeting22:57
jeblairpabelanger: yeah, let's check in then22:58
fungii missed an opportunity to exercise my latin: hanc marginis exiguitas non caperet22:58
pabelanger++22:58
*** sdague has quit IRC22:58
dmsimardoh, open floor22:58
*** julim has joined #openstack-meeting-alt22:58
dmsimardpabelanger and I this morning hosted an informal Q&A/ask me anything on TripleO and Zuul v3 with about two dozen developers involved in TripleO and it's CI22:59
jeblairdmsimard: nice!  you seem to have survived?22:59
dmsimardhappy to report that we got a good turn out and I think we managed to fend out some worries/frustrations with v3 and told them it was awesome22:59
*** achadha has quit IRC22:59
dmsimardit was recorded (red hat bluejeans) and shared with the folks that couldn't attend22:59
clarkbwould it be helpful to properly bubble that feedback upstream?23:00
*** fnaval has quit IRC23:00
jeblairyeah, even if it's stuff we know, would still be good to know what the initial roadblocks are for folks.23:00
dmsimardthere's an unorganized etherpad https://etherpad.openstack.org/p/migrating-tripleo-zuulv323:00
clarkb(storyboard stories or whatever)23:00
dmsimardIt was more about education than missing features or blockers, most of them had not even been interested in v3 at all23:00
*** ijw has quit IRC23:00
fungiwhich makes sense if they were also not especially interested in v223:01
jeblairgeneral interest in zuulv3 is a recent phenomenon.  :)23:01
*** slaweq has quit IRC23:01
dmsimardThe topic of artifacts did come up and I very briefly discussed that with jeblair23:01
*** jgriffith has quit IRC23:01
*** janki has quit IRC23:02
dmsimardI think the moment we were able to convince them that v3 is able to make their lives better and easier, you could see the sparkles in their eyes23:02
*** ijw has joined #openstack-meeting-alt23:02
fungi"artifacts" as in being able to pass build artifacts from one job to another?23:02
dmsimardfungi: yes23:02
pabelangerYah, could be turned into a FAQ for sure23:02
fungicool23:02
jeblairdmsimard: nice! thanks.  i'll give the etherpad a once over.23:02
jeblairi think we're a bit over time...23:02
jeblairso let's23:02
jeblair#endmeeting23:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"23:02
openstackMeeting ended Mon Oct 23 23:02:38 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)23:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/zuul/2017/zuul.2017-10-23-22.01.html23:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/zuul/2017/zuul.2017-10-23-22.01.txt23:02
openstackLog:            http://eavesdrop.openstack.org/meetings/zuul/2017/zuul.2017-10-23-22.01.log.html23:02
fungithanks jeblair!23:02
jeblairthanks all!23:02
pabelangero/23:02
*** iyamahat_ has quit IRC23:02
dmsimardthanks, see ya23:03
*** iyamahat has joined #openstack-meeting-alt23:03
*** slaweq has joined #openstack-meeting-alt23:10
*** ssathaye has quit IRC23:12
*** ssathaye has joined #openstack-meeting-alt23:13
*** felipemonteiro__ has quit IRC23:13
*** achadha has joined #openstack-meeting-alt23:14
*** achadha_ has joined #openstack-meeting-alt23:17
*** achadha has quit IRC23:19
*** ijw has quit IRC23:21
*** achadha_ has quit IRC23:21
*** dave-mccowan has quit IRC23:27
*** cloudrancher has quit IRC23:32
*** cloudrancher has joined #openstack-meeting-alt23:32
*** hongbin has quit IRC23:39
*** slaweq has quit IRC23:43
*** kumarmn has joined #openstack-meeting-alt23:45
*** slaweq has joined #openstack-meeting-alt23:52
*** kumarmn has quit IRC23:55

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