Tuesday, 2018-09-25

*** zigo has quit IRC00:05
pabelangerin nodepool, I am not sure how best to accomplish the following. Say I have 1st pool called 4core with max-server: 2 but and 2nd pool is 1core with max-server: 8. I don't want to launch 10 max-servers, because quota will only support a totally of 8 cores.  If I set the quota on cloud side, I think I'll be fine since nodepool knows there is only 8cores from openstack, but guess I cannot cap it in nodepool.yaml00:08
pabelangerif quota is unlimited00:08
pabelangerI hope that made sense00:09
clarkbpabelanger: correct00:14
*** annabelleB has joined #zuul00:21
pabelangerclarkb: thanks, that's what I figured.00:23
clarkbnodepool relies on the quota info to figure out how much room it has in the mixed lable cases00:25
clarkbs/lable/flavor/00:25
pabelangeryah, I'll know more tomorrow. Going to try mixed flavors with vexxhost, eg: 1G / 1C for linter jobs00:26
*** annabelleB has quit IRC00:42
*** hashar has joined #zuul05:41
*** pcaruana has joined #zuul05:41
*** chkumar|off is now known as chkumar|ruck05:42
*** quique|rover|off is now known as quiquell|rover05:45
openstackgerritMerged openstack-infra/zuul-jobs master: Block twine 1.12.0 when we install it  https://review.openstack.org/60486206:05
openstackgerritMarkus Hosch proposed openstack-infra/zuul master: Add support for authentication/STARTTLS to SMTP  https://review.openstack.org/60383306:48
openstackgerritIan Wienand proposed openstack-infra/zuul-sphinx master: Add attr_overview directive  https://review.openstack.org/60498006:49
ianwcorvus: ^ ok ... there's my attempt; i think it will be useful on the big config pages like nodepool06:50
openstackgerritIan Wienand proposed openstack-infra/nodepool master: Add overview of config options  https://review.openstack.org/60498407:01
*** quiquell|rover is now known as quique|rover|brb07:10
quique|rover|brbianw, pabelanger: Do you know if zuuls build API have argument to get buils since a date ?07:14
ianwtristanC: ^ ? i usually just use the build info page :)07:26
ianw#status log graphite.o.o removed, puppet has run and config file looks ok07:32
openstackstatusianw: finished logging07:32
*** quique|rover|brb is now known as quiquell|rover07:42
*** jpena|off is now known as jpena07:53
*** bhavikdbavishi has joined #zuul08:14
*** chmouel_ has joined #zuul08:23
*** chmouel_ is now known as chmouel08:37
*** panda|off is now known as panda09:01
*** sshnaidm has joined #zuul09:07
*** bhavikdbavishi1 has joined #zuul09:29
*** sshnaidm is now known as sshnaidm|afk09:29
*** bhavikdbavishi has quit IRC09:29
*** bhavikdbavishi1 is now known as bhavikdbavishi09:29
*** sshnaidm|afk is now known as sshnaidm|off09:37
*** sshnaidm|off has quit IRC09:42
*** bhavikdbavishi has quit IRC09:54
*** electrofelix has joined #zuul10:00
*** bhavikdbavishi has joined #zuul10:23
tobiashmordred, corvus: we're experiencing random segfaults of ansible-playbook on fedora based nodes (alpine based image)11:06
*** pcaruana has quit IRC11:15
*** panda is now known as panda|afk11:19
mordredtobiash: oh excellent11:26
tobiashnow the question is will a kernel upgrade from 4.17 to 4.18 fix it or a switch to ubuntu bionic as base image...11:26
tobiashon centos based nodes there are no segfaults btw11:27
mordredtobiash: the alpine image is running on a fedora host? or it's segfaulting when it's running against a remote fedora host?11:27
tobiashour openshift is running on centos atomic and fedora atomic (mixed nodes currently)11:27
mordredgotcha11:27
mordredtobiash: when we had some pbrx issues week before last that we originally thought were due to alpine releasing a bug but which wound up being a pbrx bug ... it made me wonder if we shouldn't switch to the normal python:minimal debian-based base image11:29
tobiashand the executors running on a fedora hosts produce these segfaults11:29
mordredbecause alpine is awesome - but it is a bit different with musl-libc and whatnot11:29
mordredtobiash: so I'll be interested to learn if a switch of base image has any impact11:30
tobiashlet's see11:30
mordredtobiash: also - on a different topic - your request last week for better parallelism in openstacksdk has actually led to a complete redesign of the parallelism system :)11:32
tobiashinteresting :)11:32
tobiashwill that be compatible with nodepool?11:33
*** jpena is now known as jpena|lunch11:38
*** quiquell|rover is now known as quique|rover|lch11:49
*** hashar is now known as hasharAway11:50
*** bhavikdbavishi1 has joined #zuul11:51
*** bhavikdbavishi has quit IRC11:53
*** bhavikdbavishi1 is now known as bhavikdbavishi11:53
tristanCquique|rover|lch: ianw: btw, i sugested chkumar|ruck to have a look at adding date filter to the builds API12:04
*** bhavikdbavishi has quit IRC12:07
*** AJaeger_ is now known as AJaeger12:13
*** jpena|lunch is now known as jpena12:40
*** panda|afk is now known as panda12:49
*** samccann has joined #zuul12:50
*** ssbarnea has quit IRC12:56
*** ssbarnea has joined #zuul13:06
*** quique|rover|lch is now known as quiquell|rover13:09
quiquell|rovertristanC: I have resolve it using skip, to go to the past13:12
quiquell|rovertristanC: But would be nice to have a since or the like13:12
*** hasharAway has quit IRC13:37
tobiashmordred: I'm not sure but I think there might be a side effect of the openstacksdk parallelization in nodepool that causes failed requests when doing config reloads in nodepool13:41
tobiashwhen that is done the manager is stopped, the inflight request fails and nodepool does all remaining retries within a few milliseconds against the old stopped manager13:41
tobiashor maybe it's caused because now it's just fast13:45
tobiashmordred: forget the reference to openstacksdk, I think I just ignored this problem13:57
tobiashI think this is inherent to single cloud use cases where a config reload breaks every inflight node launch and thus fails the request with only one provider13:59
openstackgerritTobias Henkel proposed openstack-infra/nodepool master: WIP: Try to fix single cloud config reload  https://review.openstack.org/60508614:13
tobiashmordred, Shrews, corvus: what do you think about this idea to fix the single cloud config reload? ^14:14
tobiashthere is no implementation yet, I just layed out the idea directly in the code14:14
Shrewstobiash: why would we need to detach existing nodes from the request?14:20
*** quiquell|rover is now known as quique|rover|off14:20
Shrewsjust because the manager was restarted doesn't make those invalid14:21
tobiashShrews: we don't know which provider would take it on the next try so I think that would be the safest14:21
tobiashin a single cloud usecase this is the same restarted provider, but in a multi cloud usecase we probably don't know14:21
Shrewsi don't understand. why would another provider take it? the same provider should simply try another launch14:21
Shrewsshould be similar to the case above it. abort the node, try another launch14:22
tobiashShrews: if the config change is to move a label from provider a to provider b then the restarted provider a is not allowed to do a retry14:22
tobiashShrews: yes, that was my first hunch, but then I thought about ^14:23
tobiashwhich complicates that case so I think the best we can safely do is to do a complete rollback of that request and pretend it was never worked on14:23
mordredtobiash: ah- so, the thing I'm working on in sdk should make that problem go away14:24
mordredtobiash: beaus there will be no manager to stop/start14:24
Shrewsmordred: well, there are 2 things here. restart during launch, and label change during request handling14:25
tobiashyes, the second cannot be fixed in the sdk14:25
Shrewsthe last being a *very* edge case, but still possible i suppose14:25
mordredyah14:25
Shrewsbut if we no longer restart the manager on a config change, we won't be able to identify the 2nd thing14:26
Shrewsso that probably needs more thought given mordred's upcoming changes to sdk14:26
tobiashhrm14:27
tobiashI'm not sure I wanted to hear that ;)14:27
mordredtobiash: https://review.openstack.org/604926 <-- not finished - needs testing and whatnot - but that's the idea14:27
mordredalso - https://review.openstack.org/604521 adds the ability to configure the concurrency number - instead of it just being 5 :)14:28
mordredso - in the new model, each nodepool thread that is making an api call to the cloud just makes the call itself, but the semaphore in the adapter ensures that we can reduce the concurrency so that it's not just 1000 threads all slamming the cloud at the same time14:29
mordredbut no need for a TaskManager thread, or a pool of executor threads14:29
tobiashmaybe we can just ignore case two and say if the request is taken by a provider it's immutable to config changes (as it is now)14:31
*** dmsimard has quit IRC14:31
tobiashin this case the new concurrency model would just fix it14:32
*** dmsimard has joined #zuul14:32
mordredyeah - I think that's the easiest thing to reason about14:32
tobiashas a config change cannot really be real time critical this might be just ok14:32
*** bhavikdbavishi has joined #zuul14:33
tobiashmordred: so this is a breaking change in the sdk (as it removes the taskmanager completely)?14:34
*** annabelleB has joined #zuul14:36
tobiashShrews, mordred: so is it worth to work on 605086 until 604926 is merged and released?14:37
mordredtobiash: technically yes - however I believe that nodepool is the only consumer of the taskmanager interface, so I think as long as we land it carefully (so as not to break ourselves) we should be fine - or at least that's how I'm thinking about it14:38
tobiashok14:39
corvusso is the idea to let the provider keep handling requests even after it's stopped?  (even though there's no taskmanager to stop, there's still the idea of the internal nodepool provider which will have been stopped)14:42
corvusthat may cause configuration changes to appear not to take effect immediately14:43
tobiashcorvus: yes, the provider would finish all requests it already locked14:43
corvushttp://git.zuul-ci.org/cgit/nodepool/tree/nodepool/driver/openstack/provider.py#n62  <-- currently the openstack provider uses the taskmanager to cause requests to abort14:44
tobiashcorvus: so the idea in 605086 would also undo the requests, but whith this openstacksdk change that would get difficult14:45
corvusif we wanted to maintain + fix current behavior (where config changes have immediate effect), we could still probably tell openstacksdk to remove the adapter or something and then still implement something like 60508614:45
corvusor, if we wanted to try the "existing requests use old configuration" approach for a while, i guess we could14:46
openstackgerritMatthieu Huin proposed openstack-infra/zuul master: Proposed spec: tenant-scoped admin web API  https://review.openstack.org/56232114:50
tobiashare there use cases that require an immediate effect of config changes?14:51
tobiashif yes, it's clear that we need to maintain and fix the current behavior14:51
clarkbprobably the biggest thing is max-servers being set to 0 to either accomodate a provider request or prevent nodes from being scheduled in a "broken" region14:55
clarkbunsure if that will take effect immediately or not14:55
tobiashcurrently it does14:55
*** hwoarang has quit IRC14:56
mordredyah - if we just let things play out rather than doing an immediate stop, it would mean the existing requests would continue (continuing to fail) until they were done and no new ones would be created after the config change, yeah?14:56
dmsimardIt'd be great to have a way to disable a provider other than setting max-servers to zero14:57
dmsimardlike, I dunno, on the CLI nodepool disable <provider>14:58
pabelangerdmsimard: I think the idea of max-server: 0, along with code review myself.  Helps create an audit trail15:01
dmsimardpabelanger: sure, but that's probably not mutually exclusive with a convenient and simple way of doing it15:01
pabelangerdmsimard: agree, that required more things to be in place to accomplish15:02
*** hwoarang has joined #zuul15:06
*** hwoarang has quit IRC15:17
*** chkumar|ruck is now known as chkumar|off15:17
*** chmouel has left #zuul15:25
*** hwoarang has joined #zuul15:26
*** hwoarang has quit IRC15:36
*** bbayszczak has joined #zuul15:37
*** che-arne has quit IRC15:41
*** hwoarang has joined #zuul15:47
*** bbayszczak has quit IRC15:52
*** sshnaidm|off has joined #zuul16:02
openstackgerritMatthieu Huin proposed openstack-infra/zuul master: web: add tenant and project scoped, JWT-protected actions  https://review.openstack.org/57690716:04
*** sshnaidm|off has quit IRC16:06
*** sshnaidm has joined #zuul16:06
*** hwoarang has left #zuul16:07
*** pcaruana has joined #zuul16:07
corvusmordred: the builds page performs a slow query, probably because it's doing a full table scan to check the tenant (also because there's no limit applied, but that's a separate problem).  do you think it will be sufficient to index the tenant column as-is to speed that up?  here's the info: http://paste.openstack.org/show/730735/16:25
Shrewscorvus: been a while since my query opt days, but i don't think that will help much16:27
Shrewsnot enough variation across tenants16:27
Shrews(i'm suspecting... could be wrong since i only just peeked at what you have)16:28
Shrewsmaybe a zuul_buildset key composed of (buildset_id, tenant) might be more beneficial?16:30
corvusShrews: yeah, i'm not sure what helps there....16:30
*** annabelleB has quit IRC16:36
tobiashMaybe the missing limit is the bigger problem16:36
mordredcorvus: looking (and reading what Shrews is saying)16:37
Shrewscorvus: a key that contains both the join key AND the filter key might work actually16:37
mordredtobiash: limit gets applied after the query - so the initial poor scan still has to happen16:38
mordredcorvus: this is the list-of-builds page, yeah?16:38
mordredhrm.16:41
mordredso - yeah, what Shrews said - tenant is going to have super low cardinality so won't be helpful - other than it should be in the index for final filtering16:42
mordredyes - I believe a buildset_id, tenant index will help16:43
mordredor, actually, an index on builds with id, buildset_id, then an index on buildsets on id, tenant - SHOULD maybe getit to do an index scan on builds followed by index lookups for the join and where condition16:45
* Shrews hands mordred a box of Sakila memberberries16:45
Shrewsthey're either Sakila branded, or Sakila flavored.16:47
*** annabelleB has joined #zuul16:47
mordredmmm. candied dolphin16:48
*** panda is now known as panda|off16:52
corvusShrews, mordred: i'll grab a local copy of the db and try that.17:00
mordredcorvus: I suppose I could also do that too - when you grab a dump, let me know where it is17:01
corvusmordred: zuul01:~root/zuul.sql.gz17:02
openstackgerritFabien Boucher proposed openstack-infra/zuul master: WIP - Pagure driver  https://review.openstack.org/60440417:03
mordredcorvus: cool, thanks17:09
corvusmordred: also /tmp to make scp easier :)17:09
mordredyay that's better17:10
mordredfbo: you're just having all the fun :)17:14
*** jpena is now known as jpena|off17:29
mordredcorvus: those didn't work - I'm trying other more weird things17:30
*** panda|off has quit IRC17:41
mordredcorvus: I got it better using 2 subqueries and a manual limit17:41
corvusmanual limit?17:41
mordredexplain SELECT zuul_buildset.id FROM zuul_buildset INNER JOIN zuul_build ON zuul_buildset.id = zuul_build.buildset_id where zuul_build.id in (select a.id from zuul_build as a where a.id > (select max(b.id) - 1000 from zuul_build as b) ORDER BY a.id DESC);17:41
corvusoh i think i understand manual limit :)17:42
mordred:)17:42
mordredyou can't use limits in subqueries ... I can't find a way to get the optimizer to do what we're wanting in a more simpler way yet17:42
*** jimi_|ansible has joined #zuul17:43
*** panda has joined #zuul17:45
*** panda is now known as panda|off17:47
*** annabelleB has quit IRC17:52
*** annabelleB has joined #zuul17:54
corvusmordred: i think i got something close to your original idea to work, but i had to delete the buildset_id index on zuul_build.  but maybe we can get it to work by forcing the use of certain indexes?17:54
corvusi'll paste17:54
corvusmordred: http://paste.openstack.org/show/730737/17:56
corvusmordred: if i understand the explain -- it *only* used the primary keys?17:57
corvusmordred: yeah, if i drop all the new indexes it still does the same thing17:59
Shrews20 rows? did you delete some data?18:00
*** bhavikdbavishi has quit IRC18:04
Shrewsnm. didn't notice the type of "index" there. i guess that's an indication that, yeah, it worked18:07
corvusShrews: yeah, i guess it's flipped the order -- it's scanning build first instead of buildset18:10
corvushow it can do that and apply the limit given the where clause i dunno -- i guess it can do the join and filter together, up to the limit, then it's done?18:11
Shrewswhy do i not see a where clause in that paste?18:14
corvushuh i don't know, it's in my history.  maybe a mispaste.  i'll redo18:16
corvusi guess that's an earlier version i did without the where.  with the where it's similar but the row estimates are a bit larger: http://paste.openstack.org/show/730740/18:18
SpamapScorvus: the trouble with explains in modern mysql is that they *do* consider the size of indexes, so it might actually work differently when there are 20000 rows.18:22
SpamapSFROM zuul_build INNER JOIN zuul_buildset ON zuul_buildset.id = zuul  <-- is that just cut off?18:23
SpamapSmust be18:23
SpamapS= zuul_build.buildset_id is what I'd expect to see there.18:23
SpamapSI don't see any indexes that would be usable for that join btw18:24
SpamapShard to know w/o seeing the full WHERE18:25
SpamapSbut generally this kind of index isn't as useful as you'd think: KEY `idx_test1` (`id`,`buildset_id`)18:25
SpamapSBecause id, the PK, is *already* a component of every index, and having it there may actually prevent the index's usage.18:25
SpamapSI'd suggest adding an index in that is just buildset_id and trying the explain again.18:26
* SpamapS goes back to making slides for AnsibleFest18:27
mordredSpamapS: amusingly enough - there was originally one of those and its presence made mysql do bad things18:30
Shrewsi think the obvious solution is to switch to postgres, a real database with transactions18:32
* Shrews hides18:33
* mordred throws a Shrews at Shrews18:33
clarkbwhy stop there, mssql runs on linux now18:33
* clarkb has had his fun for the day now18:33
mordredcorvus: I see you also explored an int tenant id column too18:33
corvusmordred: yeah, it seemed to have no effect18:34
corvusgah yeah the paste is getting cut off18:34
corvushttp://paste.openstack.org/show/730741/18:35
corvusthat's reformatted with the complete line18:36
corvusfwiw, with the original schema, this works:  FROM zuul_build force index (PRIMARY) INNER JOIN zuul_buildset force index(PRIMARY) ON zuul_buildset.id = zuul_build.buildset_id18:37
fungianybody have any ideas for zuul-oriented things we would like to bring up for discussion/feedback at the forum in berlin in a couple months? http://lists.zuul-ci.org/pipermail/zuul-discuss/2018-September/000546.html18:39
corvusactually that can be reduced to: FROM zuul_build force index (PRIMARY) INNER JOIN zuul_buildset ON zuul_buildset.id = zuul_build.buildset_id18:40
corvusso basically the buildset index  (KEY `buildset_id` (`buildset_id`)) on zuul_build was throwing it off.18:41
mordredyah - I think because it's a smaller index?18:41
corvustobiash, tristanC, SpamapS, clarkb, pabelanger: ^ see msg from fungi18:42
clarkbcorvus: fungi maybe a session on job reusability18:43
clarkbseems like that is consistently somethign we run into corner cases with18:43
corvusyeah, that may be a good idea -- we're still trying to figure out how to do that, and we may have enough non-openstack-upstream users there to talk about it18:44
fungireusability as in the discussion about openstack's ironic project wanting to provide in-repository parent jobs for its third-party ci ecosystem to derive from?18:44
fungithat could be interesting18:44
clarkbfungi: that, but also constructing zuul-jobs in a way that allows spamaps to use them without importing all of openstack (its actually not zuul-jobs that has that problem)18:44
tobiashcorvus, fungi: my collegues are working on something that makes reusability of zuul jobs and roles easier for the user like some kind of market place18:45
tobiashwe call that zubbi (zuul building block index)18:45
Shrewslol18:45
tobiashwould that be a useful topic there18:45
tobiash?18:45
clarkbtobiash: ya I think the method of communicating shareable bits is likely also worth discussing in that forum (pun intended)18:46
tobiash(most parts of it will be open source hopefully soon)18:46
corvusyes that sounds like a great thing to talk about18:47
clarkbone of the ideas that came up at the ptg was optional namespacing18:48
clarkbso that you clearly specify when something had to be specific, but otherwise leaving other items globally overrideable18:48
corvusclarkb, tobiash: if you can submit each of those topics via https://www.openstack.org/summit-login/login?BackURL=%2Fsummit%2Fberlin-2018%2Fcall-for-presentations that would probably be best.  if needed, we can combine them, or have a double session, etc.18:48
clarkbok I'll put a submission in after the infra meeting18:48
fungii also like the name "zubbi" ;)18:50
openstackgerritMatthieu Huin proposed openstack-infra/zuul master: Proposed spec: tenant-scoped admin web API  https://review.openstack.org/56232118:51
fungiand yeah, i just wanted to remind people about forum submissions since the official deadline for those is at the "end" of tomorrow (not sure what "end" of a day is in that context, though likely no earlier than utc midnight)18:51
tobiashcorvus: I'll ask them if that's ok (swest and Felix plan to join the Summit as well)18:52
*** gouthamr has quit IRC18:52
*** dmellado has quit IRC18:53
corvustobiash, swest: thanks.  the forum is for users/ops/devs to get together and discuss things.  so it's not a presentation, more of a venue where we can all talk about the need, the development you're doing, and how we can facilitate it or incorporate it.18:54
tobiashzubbi is basically an index of zuul jobs, roles and playbooks and makes it easy to search and view the documentation (using the standardized documentation like in zuul-jobs) without needing to look into various repos18:55
tobiashI think it will be very useful especially for non-day-to-day job authors18:56
tobiashbut my collegues can explain that much better as they developed it18:56
corvustobiash: sounds great!  we talked about having some of that in the zuul web ui too, so it'll be good to talk about how they fit together18:57
openstackgerritMatthieu Huin proposed openstack-infra/zuul master: web: add tenant and project scoped, JWT-protected actions  https://review.openstack.org/57690718:59
openstackgerritJames E. Blair proposed openstack-infra/zuul master: Speed up build list query under mysql  https://review.openstack.org/60517019:05
*** toabctl has quit IRC19:05
corvusShrews, tristanC, mordred, SpamapS: ^ i think that should do it.  that should get openstack's build query from 20 seconds down to 0.19:06
corvus(also, it turns out it is including the limit in the query, i just missed it earlier, so that should be fine)19:07
*** toabctl has joined #zuul19:07
mordredcorvus: woot!19:07
mordredcorvus: +A19:07
corvussadly that's a scheduler restart so it'll be quite some time before we see if it works19:08
pabelangerNot sure what budget for summit looks like, haven't discussed with new manager yet19:11
*** gouthamr has joined #zuul19:12
*** ssbarnea|bkp has quit IRC19:14
*** ssbarnea|bkp has joined #zuul19:15
*** electrofelix has quit IRC19:32
*** jlk has quit IRC19:44
*** jlk has joined #zuul19:50
*** gouthamr_ has joined #zuul20:05
*** dmellado has joined #zuul20:07
SpamapSmordred: orly? I'd love to see the original explain20:17
SpamapSjust for my own curiosity20:17
mordredSpamapS: http://paste.openstack.org/raw/730735/20:18
mordredSpamapS: but I think you were spot-on about part of it20:19
SpamapSyowza wow that's bad mysql20:19
mordredI thinkn it was ignoring the compound key because it was a larger key, then looking at the buildset_id key, deciding it didn't have enough fields and then just giving up and table scaning20:20
mordredSpamapS: https://review.openstack.org/605170 wound up working20:20
*** annabelleB has quit IRC20:28
SpamapSmordred: I see also now where it might have worked to add that id+buildset_id if you could work it as a range query for the ORDER BY20:35
mordredSpamapS: did you see my fancy double-sub-query version?20:36
mordred(it was not the correct choice)20:37
*** gouthamr has quit IRC20:38
*** gouthamr_ is now known as gouthamr20:39
SpamapSmordred: no, but I also would love to see how a newer mysql handles20:40
SpamapS5.7 and 8.0 are supposed to have some big leaps in optimizers.20:40
*** pcaruana has quit IRC20:43
mordredSpamapS: oh - I did the same explain in 5.7 and it had the same result :)20:46
mordredSpamapS: mordred | explain SELECT zuul_buildset.id FROM zuul_buildset INNER JOIN zuul_build ON zuul_buildset.id =20:46
mordred                          | zuul_build.buildset_id where zuul_build.id in (select a.id from zuul_build as a where a.id > (select20:46
mordred                          | max(b.id) - 1000 from zuul_build as b) ORDER BY a.id DESC);20:47
*** annabelleB has joined #zuul20:48
pabelangerclarkb: thanks to help from mnaser, setting up the quota on nodepool side worked as you said yesterday. Now to keep testing with more flavors20:50
pabelangerit is alittle awkward at first, but we now have centos-7-1vcpu / centos-7-4vcpu nodesets20:52
pabelangernot sure if it would work, or how it would look, but maybe a nodeset could also accept a flavor-id / flavor-name setting. So, a single centos-7 nodeset could use both flavors by default (if not added) or specific if added20:54
pabelangerbut for now, using unique labels works20:54
*** samccann has quit IRC20:58
openstackgerritIan Wienand proposed openstack-infra/nodepool master: Add overview of config options  https://review.openstack.org/60498421:09
ianwcorvus: ^ from prior run (that just fixes a blockquote i didn't want), but i think you're idea of using that object list works out ok to create summaries of attributes -> http://logs.openstack.org/84/604984/1/check/tox-docs/74dabc8/html/configuration.html#configuration21:14
corvusianw: i wonder how we could get it to match the order... maybe we could make that an ordereddict?21:16
corvusianw: (i was momentarily confused because 'providers' is at the top of the list, but 'webapp' appears first)21:17
ianwhrm, yeah.  i dunno, i'll take a look21:18
corvusianw: we won't be guaranteed of the order of attributes in different files, but within the same file, i think the order would be preserved, so it should work well enough for this i think21:18
ianwcorvus: ahh, i see them ordered locally, and probably that's because i'm building with a later python that has ordered dictionaries by default21:23
corvusianw: yay the future :)21:23
clarkbwas that 3.5 or 3.6?21:24
ianw3.621:24
corvusthough it's not clear to me why that used to be insecure but now isn't :)21:25
clarkbI think it had to do with generating collisions. If they've fixed the collision aspect of it then the denial of service concerns go away as do the timing attacks (against lookup times)21:27
corvusah, since it's a new impl, maybe that's so21:27
corvuslooks like the behavior is in 3.6 and guaranteed in 3.7, so effectively 3.6+21:27
corvusah, here's original security info: https://mail.python.org/pipermail/python-announce-list/2012-March/009394.html21:28
ianwit's a bit annoying that "basepython=python3" is really a misnomer, because in this and other respects, if you're testing with a version not in production you've got problems21:32
openstackgerritIan Wienand proposed openstack-infra/zuul-sphinx master: Add example and type options to attributes  https://review.openstack.org/60426721:34
openstackgerritIan Wienand proposed openstack-infra/zuul-sphinx master: Add attr_overview directive  https://review.openstack.org/60498021:34
openstackgerritIan Wienand proposed openstack-infra/zuul-sphinx master: Use OrderedDict for object tracking  https://review.openstack.org/60524021:34
ianwcorvus: ^ a local build with python3.5 and that gets the ordering right21:34
openstackgerritIan Wienand proposed openstack-infra/nodepool master: Add overview of config options  https://review.openstack.org/60498421:37
*** dkehn has quit IRC21:41
*** dkehn has joined #zuul21:43
*** jimi_|ansible has quit IRC21:47
openstackgerritJames E. Blair proposed openstack-infra/zuul master: Web: don't update the status cache more than once  https://review.openstack.org/60524321:58
clarkbhow does https://etherpad.openstack.org/p/qyli9cYnhg look for short and to the point forum session proposal22:32
* clarkb goes with it under the assumption that it can be edited later (not sure if this assumption is valid)22:37
clarkbok submitted with the info on the etherpad. It looks like I can edit it if necesary22:42
corvustobiash: ^ fyi22:52

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