Monday, 2018-03-26

*** gus has left #openstack-meeting-alt00:23
*** yangyapeng has quit IRC00:26
*** gouthamr has joined #openstack-meeting-alt00:27
*** jaypipes has quit IRC00:34
*** caowei has joined #openstack-meeting-alt00:34
*** zhurong has joined #openstack-meeting-alt00:37
*** yamahata has joined #openstack-meeting-alt00:38
*** zhurong has quit IRC01:01
*** chkumar246 has quit IRC01:04
*** tovin07_ has joined #openstack-meeting-alt01:09
*** yangyapeng has joined #openstack-meeting-alt01:10
*** hongbin has joined #openstack-meeting-alt01:12
*** yangyapeng has quit IRC01:14
*** yangyapeng has joined #openstack-meeting-alt01:19
*** chandankumar has joined #openstack-meeting-alt01:22
*** salv-orl_ has joined #openstack-meeting-alt01:30
*** fanzhang has quit IRC01:31
*** fanzhang has joined #openstack-meeting-alt01:32
*** salv-orlando has quit IRC01:33
*** fnaval has quit IRC01:38
*** ayoung has quit IRC01:51
*** _pewp_ has quit IRC01:56
*** _pewp_ has joined #openstack-meeting-alt01:59
*** david-lyle has joined #openstack-meeting-alt02:08
*** _pewp_ has quit IRC02:17
*** dalgaaf has quit IRC02:39
*** dalgaaf has joined #openstack-meeting-alt02:41
*** kmalloc has quit IRC02:46
*** david-lyle has quit IRC03:01
*** yamamoto has joined #openstack-meeting-alt03:27
*** jroll has quit IRC03:28
*** ianychoi has joined #openstack-meeting-alt03:29
*** gouthamr has quit IRC03:29
*** jroll has joined #openstack-meeting-alt03:31
*** yamamoto has quit IRC03:31
*** dave-mccowan has quit IRC03:34
*** _pewp_ has joined #openstack-meeting-alt03:35
*** zhurong has joined #openstack-meeting-alt03:37
*** hongbin has quit IRC03:45
*** rcernin has quit IRC03:55
*** rcernin has joined #openstack-meeting-alt03:55
*** _pewp_ has quit IRC04:07
*** _pewp_ has joined #openstack-meeting-alt04:08
*** yamamoto has joined #openstack-meeting-alt04:28
*** armaan has joined #openstack-meeting-alt04:29
*** armaan has quit IRC04:30
*** zhurong has quit IRC04:42
*** ethfci has quit IRC04:44
*** chhagarw has joined #openstack-meeting-alt04:48
*** dsariel has quit IRC04:50
*** anilvenkata has joined #openstack-meeting-alt05:18
*** lpetrut has joined #openstack-meeting-alt05:21
*** lpetrut has quit IRC05:32
*** lpetrut has joined #openstack-meeting-alt05:32
*** HeOS has joined #openstack-meeting-alt05:42
*** marios has joined #openstack-meeting-alt05:45
*** pgadiya has joined #openstack-meeting-alt05:53
*** zhongjun_ has quit IRC06:15
*** kmalloc has joined #openstack-meeting-alt06:17
*** links has joined #openstack-meeting-alt06:19
*** ianychoi_ has joined #openstack-meeting-alt06:26
*** ianychoi has quit IRC06:29
*** toabctl has joined #openstack-meeting-alt06:32
*** armaan has joined #openstack-meeting-alt06:42
*** jtomasek has joined #openstack-meeting-alt06:43
*** jtomasek has quit IRC06:45
*** jtomasek has joined #openstack-meeting-alt06:46
*** lpetrut has quit IRC06:58
*** rcernin has quit IRC07:10
*** tesseract has joined #openstack-meeting-alt07:23
*** adam_g has quit IRC07:39
*** markmcclain has quit IRC07:40
*** dhellmann has quit IRC07:41
*** fanzhang has quit IRC07:42
*** fanzhang has joined #openstack-meeting-alt07:42
*** tosky has joined #openstack-meeting-alt07:46
*** dsariel has joined #openstack-meeting-alt07:50
*** toscalix_ has joined #openstack-meeting-alt07:56
*** matrohon has joined #openstack-meeting-alt07:57
*** vds has joined #openstack-meeting-alt07:58
*** kopecmartin has joined #openstack-meeting-alt08:04
*** egallen has joined #openstack-meeting-alt08:08
*** bauwser is now known as bauzas08:12
*** radeks has joined #openstack-meeting-alt08:13
*** bfernando has joined #openstack-meeting-alt08:15
*** panda|off is now known as panda08:16
*** danpawlik has joined #openstack-meeting-alt08:17
*** sususuryashines has joined #openstack-meeting-alt08:18
*** sususuryashines is now known as tssurya08:18
*** derekh has joined #openstack-meeting-alt08:23
*** bhavik1 has joined #openstack-meeting-alt08:25
*** armaan has quit IRC08:34
*** lpetrut has joined #openstack-meeting-alt08:35
*** alexchadin has joined #openstack-meeting-alt08:40
*** rasta-rocket has joined #openstack-meeting-alt08:42
*** bfernando has quit IRC08:45
*** armaan has joined #openstack-meeting-alt08:47
*** armaan has quit IRC08:52
*** pgadiya has quit IRC08:59
*** chhagarw has quit IRC09:02
*** chhavi__ has joined #openstack-meeting-alt09:02
*** pgadiya has joined #openstack-meeting-alt09:02
*** finucannot is now known as stephenfin09:03
*** armaan has joined #openstack-meeting-alt09:05
*** bhavik1 has quit IRC09:07
*** toscalix_ has quit IRC09:10
*** toscalix has joined #openstack-meeting-alt09:11
*** egallen has quit IRC09:18
*** HeOS has quit IRC09:25
*** dhellmann has joined #openstack-meeting-alt09:31
*** markmcclain has joined #openstack-meeting-alt09:32
*** adam_g has joined #openstack-meeting-alt09:32
*** zhurong has joined #openstack-meeting-alt09:37
*** giblet is now known as gibi09:39
*** armaan_ has joined #openstack-meeting-alt09:45
*** armaan has quit IRC09:48
*** toscalix has quit IRC09:54
*** mjura has joined #openstack-meeting-alt09:55
*** sambetts|afk is now known as sambetts09:57
*** alexchadin has quit IRC10:03
*** toscalix has joined #openstack-meeting-alt10:07
*** HeOS has joined #openstack-meeting-alt10:08
*** tovin07_ has quit IRC10:18
*** egallen has joined #openstack-meeting-alt10:22
*** lpetrut has quit IRC10:22
*** lpetrut has joined #openstack-meeting-alt10:23
*** ddmitriev has left #openstack-meeting-alt10:28
*** armaan_ has quit IRC10:30
*** armaan has joined #openstack-meeting-alt10:30
*** egallen has quit IRC10:38
*** pbourke has quit IRC10:44
*** pbourke has joined #openstack-meeting-alt10:44
*** egallen has joined #openstack-meeting-alt10:46
*** alexchadin has joined #openstack-meeting-alt10:50
*** egallen has quit IRC10:53
*** alexchad_ has joined #openstack-meeting-alt10:56
*** alexchadin has quit IRC10:56
*** egallen has joined #openstack-meeting-alt10:59
*** caowei has quit IRC11:01
*** marios has quit IRC11:05
*** marios has joined #openstack-meeting-alt11:06
*** egallen has quit IRC11:08
*** egallen has joined #openstack-meeting-alt11:12
*** dizquierdo has joined #openstack-meeting-alt11:18
*** egallen has quit IRC11:20
*** egallen has joined #openstack-meeting-alt11:24
*** egallen has quit IRC11:24
*** egallen has joined #openstack-meeting-alt11:27
*** yamamoto has quit IRC11:27
*** zhurong has quit IRC11:27
*** slagle has joined #openstack-meeting-alt11:30
*** egallen has quit IRC11:33
*** yamamoto has joined #openstack-meeting-alt11:36
*** egallen has joined #openstack-meeting-alt11:41
*** yamamoto has quit IRC11:45
*** rmart04 has joined #openstack-meeting-alt11:47
*** egallen has quit IRC11:47
*** julim has quit IRC11:49
*** julim has joined #openstack-meeting-alt11:50
*** julim has quit IRC11:50
*** pgadiya has quit IRC11:52
*** egallen has joined #openstack-meeting-alt11:56
*** armaan has quit IRC11:57
*** armaan has joined #openstack-meeting-alt11:57
*** rfolco|off is now known as rfolco|ruck11:59
*** dave-mccowan has joined #openstack-meeting-alt12:03
*** dprince has joined #openstack-meeting-alt12:03
*** raildo has joined #openstack-meeting-alt12:04
*** egallen has quit IRC12:04
*** yamamoto has joined #openstack-meeting-alt12:05
*** alexchad_ has quit IRC12:07
*** egallen has joined #openstack-meeting-alt12:07
*** panda is now known as panda|lunch12:11
*** edmondsw has joined #openstack-meeting-alt12:13
*** toscalix has quit IRC12:16
*** chhavi__ has quit IRC12:16
*** armaan has quit IRC12:18
*** armaan has joined #openstack-meeting-alt12:18
*** egallen has quit IRC12:21
*** ethfci has joined #openstack-meeting-alt12:26
*** belmoreira has joined #openstack-meeting-alt12:28
*** jcoufal has joined #openstack-meeting-alt12:29
*** toscalix_ has joined #openstack-meeting-alt12:30
*** yamamoto has quit IRC12:30
*** egallen has joined #openstack-meeting-alt12:35
*** tpsilva has joined #openstack-meeting-alt12:39
*** toscalix_ has quit IRC12:40
*** egallen has quit IRC12:44
*** egallen has joined #openstack-meeting-alt12:54
*** caowei has joined #openstack-meeting-alt12:58
*** egallen has quit IRC13:01
*** dustins has joined #openstack-meeting-alt13:02
*** panda|lunch is now known as panda13:03
*** julim has joined #openstack-meeting-alt13:07
*** egallen has joined #openstack-meeting-alt13:07
*** dsariel has quit IRC13:08
*** chhagarw has joined #openstack-meeting-alt13:13
*** egallen has quit IRC13:16
*** ttsiouts_ has joined #openstack-meeting-alt13:18
*** yamamoto has joined #openstack-meeting-alt13:20
*** yamamoto has quit IRC13:20
*** yamamoto has joined #openstack-meeting-alt13:20
*** egallen has joined #openstack-meeting-alt13:20
*** kumarmn has quit IRC13:21
*** kumarmn has joined #openstack-meeting-alt13:22
*** gouthamr has joined #openstack-meeting-alt13:23
*** kumarmn has quit IRC13:27
*** jroll has quit IRC13:27
*** egallen has quit IRC13:27
*** jroll has joined #openstack-meeting-alt13:27
*** cloudrancher has quit IRC13:28
*** tosky__ has joined #openstack-meeting-alt13:29
*** cloudrancher has joined #openstack-meeting-alt13:29
*** yangyapeng has quit IRC13:31
*** tosky has quit IRC13:31
*** belmorei_ has joined #openstack-meeting-alt13:32
*** belmoreira has quit IRC13:33
*** egallen has joined #openstack-meeting-alt13:34
*** jaypipes has joined #openstack-meeting-alt13:35
*** kumarmn has joined #openstack-meeting-alt13:38
*** egallen has quit IRC13:40
*** mriedem has joined #openstack-meeting-alt13:41
*** lpetrut_ has joined #openstack-meeting-alt13:48
*** cdent has joined #openstack-meeting-alt13:52
*** fnaval has joined #openstack-meeting-alt13:52
*** lpetrut has quit IRC13:52
*** egallen has joined #openstack-meeting-alt13:52
*** dsariel has joined #openstack-meeting-alt13:54
*** yangyapeng has joined #openstack-meeting-alt13:54
*** hongbin has joined #openstack-meeting-alt13:55
*** egallen has quit IRC13:59
bauzas*cough cough*14:00
bauzasedleafe: ^14:00
gibi:)14:00
* efried pats bauzas on the back14:00
edleafe#startmeeting nova_scheduler14:00
openstackMeeting started Mon Mar 26 14:00:43 2018 UTC and is due to finish in 60 minutes.  The chair is edleafe. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: nova_scheduler)"14:00
openstackThe meeting name has been set to 'nova_scheduler'14:00
mriedemo/14:00
tssuryao/14:00
bauzas\o14:00
efried@/14:00
gibio/14:00
edleafegeez, everyone's in a rush today!14:01
* bauzas notes that he'll be only available for the next 20 mins14:01
efriedactually more like รถ/ today (new haircut)14:01
* bauzas greets daylight saving14:01
cdentoh hai14:01
efriedeff dst14:01
edleafe#link Agenda: https://wiki.openstack.org/wiki/Meetings/NovaScheduler14:02
edleafeI like DST - I hate having to go back to standard time in the winter14:02
efriedFine, then let's stick to that one.  But this switching back and forth is for the birds.14:03
*** yamamoto has quit IRC14:03
jaypipeso/14:03
* bauzas likes DST because for 6 months, my oven has the right time14:03
*** beekneemech is now known as bnemec14:03
edleafe#topic Specs14:03
*** openstack changes topic to "Specs (Meeting topic: nova_scheduler)"14:03
*** Zames has joined #openstack-meeting-alt14:04
bauzasI have a big question on NUMA thingy14:04
edleafeHere's the current list from the agenda:14:04
edleafe#link VMware: place instances on resource pool (using update_provider_tree) https://review.openstack.org/#/c/549067/14:04
edleafe#link Provide error codes for placement API https://review.openstack.org/#/c/418393/14:04
edleafe#link Mirror nova host aggregates to placement API https://review.openstack.org/#/c/545057/14:04
edleafe#link Network bandwidth resource provider https://review.openstack.org/#/c/502306/14:04
edleafe#link Default Allocation Ratios https://review.openstack.org/#/c/552105/14:04
edleafe#link Proposes NUMA topology with RPs https://review.openstack.org/#/c/552924/14:04
edleafe#link Spec for isolating configuration of placement database https://review.openstack.org/#/c/552927/14:04
edleafe#link Account for host agg allocation ratio in placement https://review.openstack.org/#/c/544683/14:04
edleafe#link Spec on preemptible servers https://review.openstack.org/#/c/438640/14:04
edleafego for it bauzas14:04
jaypipesbauzas: we only accept small questions on NUMA things. big questions are right out.14:05
bauzaslooks like we have an agreement on providing resources like CPU and RAM on NUMA nodes directly if the operator wants to14:05
jaypipesbauzas: Also, I request that you split your question into granular request groups.14:05
efriedappropriately namespaced14:05
jaypipes++14:05
bauzascrazy question : could the operator want to tell which specific resource classes it wants NUMA-based ?14:06
bauzaslike, could I as an operator care about VCPU but not MEMORY_MB ?14:06
jaypipesbauzas: not following you... could you elaborate?14:06
jaypipesbauzas: sure, I see no reason why not.14:06
bauzasokay, so it would be defined per class, roger.14:06
*** brault has joined #openstack-meeting-alt14:07
*** Zames has quit IRC14:07
edleafejaypipes: wouldn't that be done in libvirt?14:07
jaypipesbauzas: you mean have the dedicated CPU and shared CPU (VCPU) tracked as inventory on each NUMA node and have MEMORY_MB tracked as inventory on the root compute node provider, yes?14:07
edleafeIOW, either account for NUMA, or don't14:07
bauzasjaypipes: exactly14:07
bauzasjaypipes: or the contrary14:07
efriedseems reasonable to me.14:07
bauzaslike, memory-bound applications could care about MEMORY allocations14:07
bauzasbut wouldn't care about CPUs14:08
jaypipeswell, let's keep in mind that memory pages != MEMORY_MB...14:08
efriedI mean, doable.  I won't speak to reasonable.14:08
bauzasjaypipes: memory pages are a different feature, I just wrote an example for it in my to-be-uploaded spec14:08
jaypipesbauzas: memory pages are not the same thing as MEMORY_MB... memory pages are atomic units of a thing. MEMORY_MB's atomic "unit" is just a MB of RAM somewhere.14:08
efriedbauzas: IMO, we haven't yet landed on a workable way for the op to represent a desire for NUMA affinity.14:08
jaypipesbauzas: ok, cool. just wanted to clarify that14:08
efriedSo at this point, sky's the limit.14:08
bauzasefried: yup, that's in my spec14:09
efriedack14:09
* efried has a pretty big backlog of spec reviews to catch up on.14:09
bauzasokay, so I'll provide a revision  foir https://review.openstack.org/#/c/552924/ about optionally-NUMA-able resource classes14:09
edleafes/efried/everyone14:09
bauzasyeah I'm under the water too14:10
*** Zames has joined #openstack-meeting-alt14:10
bauzasanyway, I'm done with questions14:10
bauzasthanks14:10
edleafeAny other questions / discussion about specs?14:10
jaypipesI want to make sure edleafe gets his question answerted.14:10
jaypipesabout libvirt being responsible for tracking NUMA14:10
edleafewell, libvirt "owns" resources on the hypervisor, no?14:11
jaypipesedleafe: currently, the "tracking" of NUMA resources isn't really done in libvirt, but rather it's done in the nova/virt/hardware.py module looking at CONF options like vcpu_pin_set.14:11
edleafejaypipes: yeah, but with the move to placement, I thought libvirt would be authoritative on all resources for a compute node14:12
jaypipesedleafe: as well as flavor/image properties to do "allocations" of virtual NUMA topologies on top of host NUMA topology.14:12
bauzasjaypipes: edleafe: what I'd like is to get a consensus on a model for NUMA resources that virt drivers would implement14:12
cdents/thought/hoped/ ?14:12
*** Zames has quit IRC14:12
edleafecdent: no, it was what I've gleaned from the various discussions14:12
bauzasif Xen starts to implement NUMA topologies, all cool with me provided they model things the same way14:12
jaypipesedleafe: the virt driver will be, yes, but there will still need to be a way for the ops to signal to libvirt how (or even if) to utilize NUMA-related topology on the host.14:13
bauzasthe virt driver is responsible for generating the tree, but ideally trees wouldn't be virt-specific14:13
edleafejaypipes: zactly14:13
bauzasjaypipes: that has to be addressed in https://review.openstack.org/#/c/552924/14:13
bauzashence my question about tunability14:13
jaypipesright, no disagreement from me :)14:13
edleafejaypipes: it was the "do some NUMA, but not all" that seemed to not align14:13
bauzaslet's be clear14:13
bauzasif we go for a config-managed way to provide resources thru the virt driver, that doesn't mean that conf opt will be in the libvirt namespace14:14
*** rasta-rocket has quit IRC14:14
jaypipesbauzas: agreed.14:14
bauzasactually, I was thinking on a way for libvirt to pass the NUMA topology to a non-virt specific module that would translate into placement RPs14:14
bauzasafter all, a NUMA topology is just an architecture14:15
bauzasbut I'm overengineering the implementation14:16
bauzaskeep in mind a specific module out of virt.libvirt that libvirt would consume for generating the tree14:16
edleafebauzas: my concern is just that: making the solution overly complex in order to solve a 2% edge case14:16
bauzasand that specific module would have config options related to it14:16
bauzasedleafe: configability is 2% I agree14:17
edleafeAssuming that this is an edge case, and not what most deployments would need14:17
bauzasedleafe: having an ubiquitous interface for describing NUMA resources across all drivers isn't a 2% concern14:17
efriedBut trying to make it ubiquitous might be a 98% effort.14:17
jaypipesedleafe: hahahahah you said "edge"14:18
edleafebauzas: ok, it just felt like we started going down the rabbit hole on this14:18
*** felipemonteiro has joined #openstack-meeting-alt14:18
edleafejaypipes: edge case, not edge computing  :)14:18
bauzasedleafe: my biggest fear is that we go down too-libvirt specific14:18
*** toscalix_ has joined #openstack-meeting-alt14:18
efried+++14:18
bauzasedleafe: keeping the code responsible for generating the tree out of libvirt is crucial to me, if we want that to be non-virt specifci14:19
*** toscalix_ has quit IRC14:19
edleafeOh, I see mriedem has added another spec:14:19
edleafe#link Complex (Anti)-Affinity Policies https://review.openstack.org/#/c/546925/14:19
jaypipesbauzas: there's no disagreement with you.14:19
mriedemedleafe: you can ignore for now, it needs an update14:19
edleafemriedem: sure, just including for completeness14:19
jaypipes#action everyone ignore mriedem14:19
*** felipemonteiro_ has joined #openstack-meeting-alt14:20
bauzasjaypipes: thanks, I don't feel I had an argument, just wanted to clarify the 2%-concern14:20
bauzasI'll have to leave soon-ish14:21
cdentSo, I actually think we should move all the numa stuff into the virt drivers and not try to genericize14:21
bauzasmoving on ?14:21
bauzashah14:21
cdentbecause there's not very much overlap14:21
bauzascdent: any reasons why the contrary, mr. vmware ? :p14:21
cdentI take offense at being slapped with mr vmware. They pay me, but that's about it.14:22
bauzascdent: the problem is that as of now, only libvirt provided NUMA features, right?14:22
bauzascdent: oh sorry, I apologize if you feel offended14:22
cdentIf we want ProviderTrees to be "true", then that needs to happen in driver14:22
bauzasit wasn't the intent, rather an explicit way of considering your opinion as good because you have other virt driver in mind14:23
cdentI tend to leave the employer at the door to IRC14:23
*** felipemonteiro has quit IRC14:23
edleafe You have a door on your IRC?14:23
cdentbut understand where you were coming from, so offense untaken.14:23
efriedIf I can paraphrase what I think cdent is saying (or at least convey my own opinion couched in terms of agreeing with cdent :)14:24
bauzassorry folks, I'll have to drop in a very few and don't want to drop mic14:24
edleafeefried: paraphrase away!14:24
efriedWe want the virt driver to be responsible for modeling, and the operator can do *something* in the flavor that represents the NUMA topology in a generic way (i.e. designating affinities, not specific NUMA nodes).  But beyond that, there's no involvement of the scheduler, conductor, etc. other than the usual translating flavor-ness to placement-ness etc.14:24
bauzascdent: so, could you please explain why you consider the definition of the tree to be virt-specific ?14:24
efriedbut on the other hand - and here's where I think I'm entering bauzas-land - we'd like to be able to "advise" the modeling such that the op experience is as similar as possible for whatever virt driver.14:25
bauzasmy main worries are coming from the fact that there could be high chances that a tree could differ between a libvirt implementation and a, let's say, hyper-v14:25
cdentIs that a bad thing? We want the tree to represent the truth, yes?14:26
efriedbauzas: Perhaps cdent is saying that's going to be unavoidable, and we should butt out and let it happen.14:26
mriedemis it unavoidable?14:26
bauzascdent: from a placement perspective, I feel it could be a pain if the trees differ for explaining the same architecture14:26
jaypipescdent: ++14:26
mriedemwe try to have a consistent compute REST API across various virt drivers right?14:26
cdentIf the architectures are different, then what is represented should be different.14:27
mriedemi.e. we don't want to add more things like 'agent builds' that are only implemented by one virt driver anymore14:27
jaypipesbauzas: from a placement perspective, placement doesn't really care :)14:27
bauzascdent: I don't disagree with that14:27
bauzascdent: if architectures are differnt14:27
cdentSo if hyperv "sees" something different from libvirt, it should be different in the provider tree(s)14:27
bauzascdent: but if the same architecture, then placement should see the same thing14:27
bauzascdent: again, I don't disagree with that14:27
efriedIt's the op experience we'd like to try to smooth.  But yeah, not at the cost of wedging e.g. a square libvirt peg into a round hyperv hole.14:28
jaypipesbauzas: placement is charged with determining the allocation requests against resource providers that meet the required resource and trait constraints. It's not in charge of determining whether the structure of the resource providers being created by its clients are "correct" or not.14:28
bauzasanyway, I need to leave14:28
bauzasI'll pound that concern14:28
bauzasactually, generating a new module and describing an interface is a bit of work for me14:28
*** rasta-rocket has joined #openstack-meeting-alt14:29
bauzasso, if consensus is, "meh, let's wait other virt drivers to implement their own NUMA features"', I'm fine keeping the description in libvirt for the moment14:29
bauzasless work, yeepeee14:29
* bauzas rushes ou(t14:29
edleafeok, bauzas is gone, so let's start gossiping about him14:29
edleafe:)14:29
edleafeAnything else on specs?14:30
jaypipesok, next topic?14:30
gibiregarding #link Network bandwidth resource provider https://review.openstack.org/#/c/502306/14:30
gibiStarting this Friday I will dissapear for two weeks (honeymoon) so I'd like to settle all the remaining crazyness in the spec this week if possible.14:30
gibiThe related neturon spec work will continue without interruption.14:30
cdentwoot, congrats14:31
jaypipesWAIT! WHAT!?14:31
gibicdent: thanks :)14:31
jaypipesindeed, congrats giblet! :)14:31
* edleafe likes the way gibi snuck that in14:31
gibiso I will bug you guys this week for review14:31
jaypipesgibi: agreed, then on finalizing the spec.14:31
jaypipesgibi: np14:31
edleafereviews will be your wedding present14:32
jaypipeshahah14:32
gibiedleafe: :)14:32
*** links has quit IRC14:32
gibiI think we can move to the next topic :)14:33
edleafe#topic Reviews14:33
*** openstack changes topic to "Reviews (Meeting topic: nova_scheduler)"14:33
edleafeHere's a dump of what is on the agenda:14:33
edleafe#link Update Provider Tree https://review.openstack.org/#/q/topic:bp/update-provider-tree14:33
edleafe#link Request Filters https://review.openstack.org/#/q/topic:bp/placement-req-filter14:33
edleafe#link Nested providers in allocation candidates https://review.openstack.org/#/q/topic:bp/nested-resource-providers https://review.openstack.org/#/q/topic:bp/nested-resource-providers-allocation-candidates14:33
edleafe#link Mirror nova host aggregates to placement https://review.openstack.org/#/q/topic:bp/placement-mirror-host-aggregates14:33
edleafe#link Forbidden Traits https://review.openstack.org/#/q/topic:bp/placement-forbidden-traits14:33
edleafe#link Consumer Generations Just started; no patches posted yet.14:34
*** markvoelker_ has joined #openstack-meeting-alt14:34
edleafe#link Extraction https://review.openstack.org/#/q/topic:bp/placement-extract14:34
edleafeAnyone have a question/concern about any of these?14:34
jaypipesnope.14:34
*** markvoelker has quit IRC14:35
cdentI have a query about reviewing in general in a world of runways: Is _all_ of placement non runway oriented? How are we wanting that to work?14:35
jaypipescdent: good question. no idea.14:35
edleafeMy understanding was that runways were for non-priority things14:35
efriedIt was originally14:36
edleafeY'know, to give them some attention14:36
*** armaan has quit IRC14:36
edleafeefried: ...and it changed?14:36
efriedbut I think we're shifting from that to making it more of a generalized queue for "this is ready, let's get focus on it"14:36
cdentWhat I'm trying to figure out is which of the placement stuff needs to go in the queue, and which doesn't14:36
cdentIf it's all, that's cool (and I think I'd actually prefer that for sake of one rule to bind them)14:36
efriedright; IMO, KISS and queue stuff up for a runway when it meets the other criteria.14:37
*** markvoelker has joined #openstack-meeting-alt14:37
efriedThere seemed to be some agreement on that, though we never like voted or anything.14:37
dansmitheverything goes into runways14:37
dansmithblueprints go into runways, so a placement blueprint would get a slot for a while14:37
jaypipesare we doing the runways stuff already or were we waiting for the spec review day (tomorrow) to be done?14:37
dansmithlike anything else14:37
cdentstarts day after spec day14:37
dansmithjaypipes: starting after tomorrow14:38
*** ttsiouts_ has quit IRC14:38
jaypipesk14:38
jaypipesI have no issues with dealing with placement like anything else.14:38
*** markvoelker_ has quit IRC14:39
cdentcool14:39
edleafeSo... nothing more regarding reviews?14:39
mriedemi guess i have something14:40
mriedemremember the ironic flavor / trait migration?14:40
edleafeyeah14:40
mriedemhttps://review.openstack.org/#/c/527541/ i've been pushing that since queens, and meant to backport to pike14:40
mriedemkind of want to know if i should just abandon that14:40
mriedemi don't think we should do a hard drop of that migratoin code in the driver until nova-status supports it,14:41
mriedembut there doesn't seem to be much interest14:41
jaypipesmriedem: I just wasn't aware of that. I can review today. seems important to me.14:42
edleafehuh, I thought that merged a while ago14:42
cdentsuspect it just fell off radar14:42
edleafeput it on a runway!14:42
mriedemit's not a bp14:42
mriedembut thanks14:42
edleafeAny other reviews to discuss?14:43
edleafeGuess not14:45
edleafe#topic Bugs14:45
*** openstack changes topic to "Bugs (Meeting topic: nova_scheduler)"14:45
edleafe#link Placement bugs  https://bugs.launchpad.net/nova/+bugs?field.tag=placement&orderby=-id14:45
mriedemthere is a bug re placement we've talked about in gibi's bw provider spec,14:45
mriedembut not sure we actually opened a bug to track it,14:45
mriedemhas to do with cleaning up allocations when deleting an instance but the compute service it's running on is down14:45
*** cloudrancher has quit IRC14:46
mriedemif no one remembers opening a bug for that i can circle back14:46
gibimriedem: I haven't opened it14:46
*** cloudrancher has joined #openstack-meeting-alt14:46
cdentthat's something different from 'local delete'?14:46
gibicdent: local delete + decomission compute host14:47
cdenthttps://bugs.launchpad.net/nova/+bug/167975014:47
openstackLaunchpad bug 1679750 in OpenStack Compute (nova) pike "Allocations are not cleaned up in placement for instance 'local delete' case" [Medium,Confirmed]14:47
*** cloudrancher has quit IRC14:47
mriedemthat's the one14:47
* mriedem thanks his past self14:47
cdentyour past self is clever14:47
*** cloudrancher has joined #openstack-meeting-alt14:47
*** yamahata has quit IRC14:49
cdentwe done with bugs?14:49
edleafeAnything more on bugs?14:49
* cdent blinks14:49
edleafe#topic Open discussion14:50
*** openstack changes topic to "Open discussion (Meeting topic: nova_scheduler)"14:50
edleafeSo... what's on your collective minds?14:50
cdentThis is not a priority, but I'd like to get some feedback on https://review.openstack.org/#/c/552927/ , which is the spec for optional db setting in placement.14:50
cdentIt allows ... options ... when working with placement that are handy14:50
cdentBut if you don't do anything different, it all works the same as it does now14:51
*** mjura has quit IRC14:51
*** cloudrancher has quit IRC14:51
edleafeIf it makes the eventual separation of placement from nova go more smoothly for operators, ++14:51
cdentthere's some discussion in the spec about how it is but one of several options14:52
cdentbut also some of why I think it is the better one14:52
*** felipemonteiro_ has quit IRC14:53
*** felipemonteiro__ has joined #openstack-meeting-alt14:53
*** gcb has joined #openstack-meeting-alt14:54
* bauzas is back for 6 mins, yay14:54
edleafecdent: ok, I'll re-review14:55
cdentthanks14:55
edleafeAnything else for today?14:55
edleafeOK, thanks everyone!14:56
edleafe#endmeeting14:56
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"14:56
openstackMeeting ended Mon Mar 26 14:56:25 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:56
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_scheduler/2018/nova_scheduler.2018-03-26-14.00.html14:56
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_scheduler/2018/nova_scheduler.2018-03-26-14.00.txt14:56
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_scheduler/2018/nova_scheduler.2018-03-26-14.00.log.html14:56
*** cdent has left #openstack-meeting-alt14:56
*** tosky__ has left #openstack-meeting-alt14:58
bauzass/likes/hates14:58
bauzasDST14:58
*** leifmadsen has quit IRC15:02
*** yamamoto has joined #openstack-meeting-alt15:03
*** leifmadsen has joined #openstack-meeting-alt15:04
*** dmsimard is now known as dmsimard|cave15:05
*** mriedem has left #openstack-meeting-alt15:05
*** chandankumar has quit IRC15:06
*** mguiney has quit IRC15:08
*** chyka has joined #openstack-meeting-alt15:10
*** danpawlik has quit IRC15:12
*** caowei has quit IRC15:13
*** manjeet has joined #openstack-meeting-alt15:13
*** yamamoto has quit IRC15:15
*** kmalloc has quit IRC15:16
*** derekh has quit IRC15:19
*** chkumar246 has joined #openstack-meeting-alt15:23
*** matrohon has quit IRC15:24
*** manjeet has quit IRC15:26
*** david-lyle has joined #openstack-meeting-alt15:29
*** cloudrancher has joined #openstack-meeting-alt15:39
*** david-lyle has quit IRC15:42
*** david-lyle has joined #openstack-meeting-alt15:46
*** julim_ has joined #openstack-meeting-alt15:47
*** jcoufal_ has joined #openstack-meeting-alt15:48
*** dizquierdo has quit IRC15:48
*** julim has quit IRC15:49
*** jcoufal has quit IRC15:49
*** jcoufal_ has quit IRC15:53
*** jcoufal has joined #openstack-meeting-alt15:53
*** yamahata has joined #openstack-meeting-alt15:53
*** rnoriega has quit IRC15:56
*** pabelanger has quit IRC15:56
*** rnoriega has joined #openstack-meeting-alt15:57
*** weshay has quit IRC15:57
*** belmorei_ has quit IRC15:59
*** pabelanger has joined #openstack-meeting-alt16:00
*** marios has quit IRC16:01
*** manjeet has joined #openstack-meeting-alt16:01
*** manjeet has quit IRC16:01
*** manjeet has joined #openstack-meeting-alt16:02
*** manjeet has quit IRC16:02
*** weshay has joined #openstack-meeting-alt16:02
*** manjeet has joined #openstack-meeting-alt16:03
*** gcb has quit IRC16:03
*** felipemonteiro__ has quit IRC16:09
*** yangyapeng has quit IRC16:10
*** yangyapeng has joined #openstack-meeting-alt16:11
*** yamahata has quit IRC16:14
*** david-lyle has quit IRC16:14
*** salv-orl_ has quit IRC16:25
*** salv-orlando has joined #openstack-meeting-alt16:26
*** sambetts is now known as sambetts|afk16:26
*** gyee has joined #openstack-meeting-alt16:27
*** manjeet has quit IRC16:29
*** salv-orlando has quit IRC16:30
*** julim has joined #openstack-meeting-alt16:30
*** dsariel has quit IRC16:32
*** cloudrancher has quit IRC16:32
*** julim_ has quit IRC16:32
*** cloudrancher has joined #openstack-meeting-alt16:34
*** radeks has quit IRC16:41
*** rasta-rocket has quit IRC16:42
*** dklyle has joined #openstack-meeting-alt16:47
*** Leo_m has joined #openstack-meeting-alt16:47
*** dklyle has quit IRC16:49
*** david-lyle has joined #openstack-meeting-alt16:49
*** cloudrancher has quit IRC16:51
*** yangyapeng has quit IRC16:52
*** kmalloc has joined #openstack-meeting-alt16:52
*** chhagarw has quit IRC16:53
*** rasta-rocket has joined #openstack-meeting-alt16:54
*** lpetrut_ has quit IRC16:54
*** david-lyle has quit IRC16:55
*** tssurya has quit IRC16:56
*** rmart04 has quit IRC16:59
*** manjeet has joined #openstack-meeting-alt17:03
*** manjeet has quit IRC17:08
*** dsariel has joined #openstack-meeting-alt17:10
*** panda is now known as panda|off17:14
*** kopecmartin has quit IRC17:18
*** david-lyle has joined #openstack-meeting-alt17:18
*** david-lyle has quit IRC17:25
*** lpetrut_ has joined #openstack-meeting-alt17:25
*** szaher has joined #openstack-meeting-alt17:25
*** salv-orlando has joined #openstack-meeting-alt17:26
*** salv-orlando has quit IRC17:31
*** dsariel has quit IRC17:31
*** manjeet has joined #openstack-meeting-alt17:32
*** manjeet has quit IRC17:45
*** AlanClark has joined #openstack-meeting-alt17:47
*** felipemonteiro has joined #openstack-meeting-alt17:53
*** felipemonteiro_ has joined #openstack-meeting-alt17:54
*** felipemonteiro has quit IRC17:58
*** salv-orlando has joined #openstack-meeting-alt18:02
*** tesseract has quit IRC18:10
*** AlanClark_ has joined #openstack-meeting-alt18:15
*** yamahata has joined #openstack-meeting-alt18:16
*** lpetrut_ has quit IRC18:18
*** AlanClark has quit IRC18:18
*** haleyb has quit IRC18:20
*** manjeet has joined #openstack-meeting-alt18:23
*** fnaval has quit IRC18:23
*** tobiash has joined #openstack-meeting-alt18:26
*** fnaval has joined #openstack-meeting-alt18:26
*** vipul has quit IRC18:32
*** mahe has joined #openstack-meeting-alt18:33
*** macermak has joined #openstack-meeting-alt18:39
*** yamahata has quit IRC18:39
*** jcoufal has quit IRC18:40
*** manjeet has quit IRC18:40
*** mhen has joined #openstack-meeting-alt18:46
*** matrohon has joined #openstack-meeting-alt18:50
*** cloudrancher has joined #openstack-meeting-alt18:50
*** mahe has left #openstack-meeting-alt18:54
*** marius1 has joined #openstack-meeting-alt18:57
*** haleyb has joined #openstack-meeting-alt18:58
*** yangyapeng has joined #openstack-meeting-alt19:02
*** HeOS has quit IRC19:06
*** markstur has joined #openstack-meeting-alt19:06
*** yangyapeng has quit IRC19:07
*** cloudrancher has quit IRC19:15
*** salv-orlando has quit IRC19:31
*** markstur has quit IRC19:31
*** salv-orlando has joined #openstack-meeting-alt19:31
*** salv-orlando has quit IRC19:37
*** harlowja has joined #openstack-meeting-alt19:37
*** jtomasek has quit IRC19:39
*** yamamoto has joined #openstack-meeting-alt19:45
*** salv-orlando has joined #openstack-meeting-alt19:46
*** raildo has quit IRC19:47
*** yamamoto has quit IRC19:50
*** danpawlik has joined #openstack-meeting-alt19:51
*** EmilienM has quit IRC19:57
*** EmilienM has joined #openstack-meeting-alt19:57
*** dprince has quit IRC20:06
*** macermak has quit IRC20:08
*** manjeet has joined #openstack-meeting-alt20:15
*** felipemonteiro__ has joined #openstack-meeting-alt20:16
*** felipemonteiro_ has quit IRC20:16
*** edmondsw has quit IRC20:21
*** manjeet has quit IRC20:26
*** manjeet has joined #openstack-meeting-alt20:31
*** gouthamr has quit IRC20:33
*** Leo_m_ has joined #openstack-meeting-alt20:36
*** Leo_m has quit IRC20:39
*** vipul has joined #openstack-meeting-alt20:39
*** Leo_m_ has quit IRC20:41
*** dprince has joined #openstack-meeting-alt20:41
*** julim has quit IRC20:42
*** manjeet has quit IRC20:46
*** edmondsw has joined #openstack-meeting-alt20:47
*** vipul has quit IRC20:48
*** Shrews has joined #openstack-meeting-alt20:50
*** vipul has joined #openstack-meeting-alt20:51
*** yamahata has joined #openstack-meeting-alt20:52
*** ttsiouts_ has joined #openstack-meeting-alt20:54
*** vipul has quit IRC20:58
*** AlanClark has joined #openstack-meeting-alt20:59
*** jaypipes has quit IRC21:01
*** AlanClark_ has quit IRC21:02
*** dprince has quit IRC21:02
*** vipul has joined #openstack-meeting-alt21:03
*** edmondsw has quit IRC21:05
*** edmondsw has joined #openstack-meeting-alt21:08
*** dprince has joined #openstack-meeting-alt21:11
*** matrohon has quit IRC21:12
*** manjeet has joined #openstack-meeting-alt21:13
*** AlanClark has quit IRC21:18
*** dprince has quit IRC21:21
*** edmondsw has quit IRC21:26
*** dave-mccowan has quit IRC21:27
*** dustins_ has joined #openstack-meeting-alt21:27
*** dsariel has joined #openstack-meeting-alt21:29
*** vipul has quit IRC21:29
*** manjeet has quit IRC21:30
*** dustins has quit IRC21:30
*** yamahata has quit IRC21:33
*** manjeet has joined #openstack-meeting-alt21:34
*** vipul has joined #openstack-meeting-alt21:34
*** vipul has quit IRC21:36
*** rasta-rocket has quit IRC21:36
*** vipul has joined #openstack-meeting-alt21:42
*** gouthamr has joined #openstack-meeting-alt21:45
*** ttsiouts_ has quit IRC21:46
*** felipemonteiro_ has joined #openstack-meeting-alt21:49
*** dustins_ has quit IRC21:52
*** felipemonteiro__ has quit IRC21:53
*** rfolco|ruck is now known as rfolco|off21:55
*** dsariel has quit IRC21:57
corvushowdy zuul folks?22:00
clarkbhello (though I'm only sort of here)22:00
fungimmm, yep22:00
corvusoh good.  howdy zuul folks!22:00
pabelangerhello22:01
* Shrews taps mic22:01
kittenshi22:01
*** prometheanfire has joined #openstack-meeting-alt22:01
fungialoha22:01
corvus#startmeeting zuul22:01
openstackMeeting started Mon Mar 26 22:01:54 2018 UTC and is due to finish in 60 minutes.  The chair is corvus. 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
corvus#link agenda https://wiki.openstack.org/wiki/Meetings/Zuul22:02
corvus#link previous meeting http://eavesdrop.openstack.org/meetings/zuul/2018/zuul.2018-03-19-22.03.html22:02
corvus#topic Action items22:02
*** openstack changes topic to "Action items (Meeting topic: zuul)"22:02
corvuscorvus attempt to help with storyboard private story notification fix22:02
corvusso i haven't gotten very far with that22:02
Shrewswe didn't encourage you enough22:02
corvuser, i should clarify22:02
corvusi tried again really hard22:02
corvusand still didn't get anywhere22:02
jlko/22:03
corvusthe test infrastructure around this in storyboard is not functioning the way i expect, and i'm at a loss for how to fix it22:03
jlk(only half paying attention, please ping me if I'm needed)22:03
corvusso we need to decide if we're okay living with the fact that we won't get email about critical security bugs22:04
corvusor if we want to do something else22:04
fungithat's depressing. i'd like it to not be the case, but am dealing with my own "why did tests not catch this?" moment in sb now as well22:04
*** dprince has joined #openstack-meeting-alt22:04
corvusyeah, i'd also love to have the time to work on a systemic fix to the issue i'm running into, but it would be a *large* change22:04
corvusi know how to do that, but don't have time.  i do have time to make a small change, but don't know how.22:05
*** felipemonteiro_ has quit IRC22:05
Shrewswhat's our other option? or is there none?22:06
corvuswe could try to peridocally poll storyboard with a cron.  however, in pure coincidence, the cron i have running for the zuulv3 dashboard just started timing out.  i don't know if the same would be true for a query for private stories.22:06
corvusi could try it and see.22:06
corvusthat's one option.  another might be to create a mailing list for folks to send security bug reports to.  either the entire report, or just a notification after they create a bug.22:06
corvushonestly, if we can work around this with a cron job, that's *probably* the slightly safer/friendler path.22:06
corvus(for reporters)22:07
corvusit's probably a bit more work on our part to make sure the cronjob doesn't bitrot22:07
corvus(also, could be a periodic job in zuul, doesn't need to be cron ;)22:07
fungii'm wondering if the recent api slowness is limited to searches by story tag since that's where i've mainly noticed it so far. more of a topic for #storyboard but it may mean that searching on other criteria is not currently slow22:07
corvusfungi: good point22:08
corvusso maybe i should try writing an automated query for this and report back?22:08
fungihowever, i also haven't looked to determine whether you can query by private-ness22:08
corvusfungi: hopefully 'list all zuul stories' doesn't become prohibitively expensive :)22:08
pabelangercrontab seems like a good next step22:09
corvus#action corvus write automated query for private zuul stories (to find security issues)22:09
corvusthe other action item from last week is: corvus create some remote tests for zuul-stream22:09
corvusi did that.  i think they merged!22:09
corvus#topic  Why not tagging the current master, e.g. release early, release often? (tristanC)22:10
fungifair, if zuul has _that_ many stories before sb performance improves, then maybe we're doing something wrong ;)22:10
*** openstack changes topic to "Why not tagging the current master, e.g. release early, release often? (tristanC) (Meeting topic: zuul)"22:10
corvustristanC is not here22:10
corvusbut i guess the topic is self-explanatory :)22:10
clarkba beta release wouldn't be the worst thing imo (especially if github thing is fixable at this point)22:11
corvusmy straightforward answer to that question is that as soon as we are able to release, we will.22:11
clarkbbut ya I realize ^22:11
fungicould do zuul 3.0.0.0rc1 or something i suppose22:12
corvusi know of two issues:22:12
corvus1) javascript -- mordred has some changes that he thinks we should merge now because otherwise, migrating folks later will be painful/impossible22:12
corvus(as in, we've got at least one more case where we must merge a change then go do manual things to make it work)22:13
corvuswe don't want to be landing those kinds of changes in the future22:13
* mordred hopes to have that in shape for folks by tomorrow morning22:13
* mordred currently on very bad in0-flight wifi22:13
corvus2) github3.py -- we're still in the position where if we get a working release of this before item #1 clears, great!  otherwise, we need to vendor it before release.22:14
corvuseither way, i think those both preclude releasing master at this point22:14
pabelangerwfm22:14
clarkbcorvus: it was mentioned by tobiash that the github3.py issue for license api thing is fixed? I guess it just needs a release now?22:15
corvushowever, once we do release, we need to do one more thing, then we can return to our pattern of releasing frequently.  like, maybe every few weeks.22:15
corvusclarkb: oh i missed that!22:15
corvusmaybe it's time to ping jlk :)22:15
clarkbjlk can probably confirm22:15
jlkSo.22:15
jlkI think we fixed at least some of the issue tobiash found, but maybe not all22:15
corvus#info release is blocked by some pending javascript patches (mordred to prepare ASAP)22:16
jlkand I've been really bad about being able to set up something to validate, so it'd be helpful if we could get a fresh attempt by tobiash22:16
corvus#action mordred propose release-blocking javascript patches22:16
jlkThere hasn't been a release, so he'd have to test from develop branch. If we can confirm, I can do the work to make a release happen22:16
corvus#action tobiash test most recent github3.py to see if it's ready to release22:16
corvussweet!  hopefully, with the magic of timezones, he can do that while i'm asleep :)22:17
jlkThere have been other GitHub Enterprise folks testing and they've found at least one other issue that has an open PR, so I'm not sure if that effects tobiash or not22:18
corvus#info ping jlk with github3.py test results to make release22:18
corvusjlk: have a link handy?22:18
jlkdigging itup22:19
jlkhttps://github.com/sigmavirus24/github3.py/pull/813 is the pr22:19
jlkhttps://github.com/sigmavirus24/github3.py/issues/794 is the (closed perhaps too early) issue22:20
fungigood ol' sigmavirus2422:20
* prometheanfire misses sigmavirus22:20
corvus#link https://github.com/sigmavirus24/github3.py/issues/794 closed github enterprise issue22:20
*** rcernin has joined #openstack-meeting-alt22:20
corvus#link https://github.com/sigmavirus24/github3.py/pull/813 potential github enterprise issue?22:20
fungielectrofelix reported that issue?22:20
fungismall world22:21
corvusboth in fact :)22:21
pabelangernice22:22
*** salv-orlando has quit IRC22:22
*** salv-orlando has joined #openstack-meeting-alt22:23
corvusi think that's it for this subject...22:23
corvus#topic Open Discussion22:23
*** openstack changes topic to "Open Discussion (Meeting topic: zuul)"22:23
jlkDo we know electrofelix?22:23
corvusjlk: oh, yes, he's a contributor to jenkins-job-builder, and some other openstack-infra-related projects22:24
corvusthat's his nick in irc; can often be found in #openstack-infra or #zuul22:24
fungia.k.a. pelix22:25
corvusoh that name is new to me22:25
fungijjb core reviewer22:25
fungihe was pelix for a while beforee electrofelix22:26
corvusin other news, i think i'm pretty close to getting git.zuul-ci.org up and running22:26
pabelangerI have an awkward patch up for ipv6 support in zuul: https://review.openstack.org/556327/ would love to discuss that this week.22:26
corvusit will be especially nice to be able to tell people to use "https://git.zuul-ci.org/zuul-jobs"22:27
*** salv-orlando has quit IRC22:27
pabelangeryah, that would be good22:27
pabelangerand cool22:27
Shrewspabelanger: is there an equivalent patch for nodepool?22:27
jlkcorvus: oh! I wonder then if he's another zuul + github user22:28
pabelangerShrews: yah, that merged this morning https://review.openstack.org/556209/22:28
Shrewsah, ok. missed that22:28
fungithough biggest impact for zuul-{base-,}jobs since it goes in everyone's config if they want to cd our stdlib22:29
*** dave-mccowan has joined #openstack-meeting-alt22:29
corvusjlk: if not currently, i'm given to understand, he'd like to be :)22:29
corvusi missed that too22:29
corvusi'd really like it if we stopped merging changes without docs22:30
corvusin fact, i'm going to propose a revert of that22:30
corvuswe have past the point where we should merge a change without tests and docs22:30
clarkbthats awkward that statsd has to have an explicit ipv6 flag22:31
corvusyeah, i assume it's because it's udp?22:31
clarkbmaybe instead of a flag we just detect if it is an ipv4 addr or ipv6 and do the right thing?22:31
Shrewsclarkb++22:31
pabelangerwe can do that, but no way to stop statsd from then detecting it again22:31
corvusclarkb: we'd need to know if the ipv6 address is routable from us, right?22:32
clarkbcorvus: yes, I think assuming it is if you have global ipv6 address is mostly safe22:32
pabelangerhttps://github.com/jsocol/pystatsd/blob/master/statsd/client.py#L152 is how it works today in statsd. If we want to propose a change, I'm okay witht hat22:32
clarkb(this seems to be behavior of most applications)22:32
corvusclarkb: yeah, i'd prefer that approach too22:33
fungiyeah, if both are global then fine, otherwise that's not entirely trivial to determine22:33
corvusso basically, do a lookup of the host, see if it has a global ipv6 address, if so, see if we do, if so, set the ipv6 flag...22:33
corvus(why doesn't py-statsd do that?)22:33
fungiand "happy eyeballs" approaches don't work so well for connectionless datagrams22:34
corvusif someone had an internal (not global) statsd server only on ipv6, this scheme wouldn't work for them.  they'd need a flag.22:35
corvusoh, there's one more thing related to releases i should mention --22:36
clarkbits unfortunate that is even a thing considering ipv6's available address space being there to avoid that problem entirely22:36
fungibut yeah, if you're hoping to take a non-global route to a v6 destination they can't reach via v4, then maybe the onus is on them to make dns only resolve the thing they can reach or use an address literal?22:36
corvusfungi: yeah, that might be enough of a workaround22:37
corvusafter we do release 3.0.0, and before we release 3.0.1 -- we should land support for reno.  i don't want to do it before 3.0.0 (because i don't want to even pretend we can write those release notes).  but going forward, i'd like zuul and nodepool to have real release notes.22:37
corvusso that basically means that's the first post 3.0.0 thing we need to land22:37
pabelangerso, use socket.getaddrinfo() again to detect if ipv6, then setup flag on statsd client. wfm22:38
corvuspabelanger: yeah, let's give that a shot.  because i think we all agree this option is weird. :)22:38
pabelangerindeed22:39
fungipabelanger: not quite as simple as all that, need to check that you have a global route i think? but basically yes22:39
corvusfungi: check the route, or check to see if we have a global ipv6 address?22:40
pabelangerfungi: okay, I was going to use the same logic for fingergw we did for ipv6, I don't think we checked global route there22:41
fungiwell one or the other should work, just pointing out it's not sufficient to check that socket.getaddrinfo() works via v622:41
pabelangerfungi: okay, maybe after meeting we can look at https://review.openstack.org/551015/ and see if we'd have the same issue22:43
fungiyep, we can hash it out outside the meeting for sure22:43
corvusi had an action item a while back to follow up on the meeting time change.  i did not do that last week, but have started doing it this week.22:44
corvusi don't think there's a way we can make everyone happy, so i'll probably end up making an executive decision one way or the other.  however, there's another alternative i'd like us to consider:22:44
corvusend the practice of regular meetings and focus more on mailing list discussions for wide dissemination/collection of information, and ad-hoc irc discussions for when that's not practical22:45
corvusas the folks who randomly showed up to today's meeting, what do you think about that? :)22:45
Shrewswfm22:46
pabelangerI admit, i like the structure IRC meetings, but happy to try something new if people would like22:46
fungias a completely non-representative sample, i think it would be nice to venture headlong into this new governance unencumbered by the baggage of weekly meetings22:46
clarkbI know monty struggles with mailing lists based on some recent conversations. But I imagine ad hoc conversations can get him pointed to relevant threads as needed22:47
fungiculturally the openstack community has used scheduled meetings as a crutch to avoid discussing over mailing lists22:47
fungiwould be nice to see if not having scheduled meetings reduced that tendency22:48
clarkbI also have a really hard time with threads that get outlooked, but maybe I just need a better tactic for dealing with those22:48
*** dprince has quit IRC22:49
corvusit's really hard to get to a decision on a mailing list.  so it will require we develop some different skills.22:49
fungigo from "i should add that to the agenda for some upcoming meeting which may be a week away and might already be too overbooked to get to my topic" to "i'll post to the mailing list about this now"22:49
corvusand yeah, meetings provide a structure, timeboxed by their nature, which we will have to be cognizant of.  (bi-?)weekly summaries may help with that.22:49
jlkI'm pretty bad about email for this project, but I can respond to random channel pings for data22:49
*** fnaval has quit IRC22:50
clarkbcorvus: re making decisions and lack of time boxes maybe once a thread has had reasonable conversation we set a N day timer on completing the decision making22:50
pabelangeryah, summaries might help with that22:50
corvusalso, we have a dedicated mailing list, which may make it a bit easier for folks to deal with than, for instance, openstack-dev.22:50
clarkbsimilar to specs I uess22:50
pabelanger+1 to trying MLs22:51
corvusokay, maybe i'll reply to the ml thread about the meeting time with the suggestion we consider terminating it.22:51
corvusi'll indicate in this meeting, at least, we saw some value to the meeting, but there wasn't widespread revolt22:52
fungii don't find the meetings useless, but concede they may be an antipattern22:53
corvusprobably the biggest thing is that it's an hour where we all actually plan on talking about zuul.  for those of us with multiple hats, that can be surprisingly important.22:53
corvus                         ^ (for me)22:53
fungifair!22:53
pabelanger++22:54
corvusbut it's an hour that several other people plan on being asleep during, so... there you have it :)22:54
*** prometheanfire has left #openstack-meeting-alt22:54
corvusanything else, or should we wrap it up?22:55
fungii'm good22:55
Shrewsfwiw, ML discussions have been extremely valuable (e.g., the zk retry stuff), but was surprisingly lacking on much participation. not sure if an IRC meeting would be much better (or worse)22:56
Shrewsjust more food (mmmm, food) for thought22:57
ianwpersonally i like the meetings, as someone quite remote it's often very vaulable to get decisions made in them22:57
*** chkumar246 has quit IRC22:57
*** hongbin has quit IRC22:58
corvusianw: if we do keep it, maybe we could be more strict about the agenda (so people can more reliably anticipate if they should attend), and cancel it if there's nothing on it.22:58
corvusianw: otoh, we could ping the folks active on an email thread and say "hey, so how about we decide on that thing we were emailing about"22:59
corvusthanks all!23:00
corvus#endmeeting23:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"23:00
openstackMeeting ended Mon Mar 26 23:00:12 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)23:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/zuul/2018/zuul.2018-03-26-22.01.html23:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/zuul/2018/zuul.2018-03-26-22.01.txt23:00
openstackLog:            http://eavesdrop.openstack.org/meetings/zuul/2018/zuul.2018-03-26-22.01.log.html23:00
*** Shrews has left #openstack-meeting-alt23:00
*** pabelanger has quit IRC23:01
*** pabelanger has joined #openstack-meeting-alt23:01
*** fnaval has joined #openstack-meeting-alt23:01
*** manjeet has quit IRC23:02
*** kumarmn has quit IRC23:05
*** yangyapeng has joined #openstack-meeting-alt23:09
*** chandankumar has joined #openstack-meeting-alt23:14
*** yangyapeng has quit IRC23:14
*** danpawlik has quit IRC23:16
*** gouthamr has quit IRC23:18
*** kumarmn has joined #openstack-meeting-alt23:22
*** salv-orlando has joined #openstack-meeting-alt23:23
*** marius1 has quit IRC23:25
*** yangyapeng has joined #openstack-meeting-alt23:25
*** kumarmn has quit IRC23:27
*** salv-orlando has quit IRC23:28
*** yangyapeng has quit IRC23:31
*** HeOS has joined #openstack-meeting-alt23:42
*** tpsilva has quit IRC23:47
*** manjeet has joined #openstack-meeting-alt23:51
*** chandankumar has quit IRC23:53
*** vipul has quit IRC23:55

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