Monday, 2015-04-13

mordredhowever, I'm going to call bs on anyone being confused by the "put requirements in requirements.txt" part00:00
lifelessAnd as dstufft says, having a clear and straightward description of how to translate can be done even before that nirvana is reached00:00
mordredit's a clear and simple delta00:00
mordred"put what you put in setup.py into setup.cfg except for requirements which you put in requirements.txt"00:00
mordreddone00:00
lifelessexcept extras00:00
lifelessand setup requires00:01
mordrednobody00:01
mordredNOBODY00:01
mordredunderstand those00:01
dstufftI do!00:01
mordredexcept liek 4 of you00:01
dstufft:D00:01
mordreddstufft: you don't count00:01
lifelessactually00:01
lifelessthere's a fair whack of packages using them00:01
lifelessI noticed that when I was writing my map-reduce over pyPI for setup-requires usage00:01
mordredthere's also a fair whack fo packages compiling C00:01
mordreddoesnt' mean I want to join their crazy00:01
mordredso - let's constrain the conversation real quick00:02
mordredbecause I tink I am understanding your POV better00:02
mordredthe semantics of an existing requirements.txt in the absence of install_requires in setup.cfg CANNOT change00:02
mordredthat's non-negotiable00:02
mordredbecause of backwards compat00:02
lifelessagreed - I specified for that in my email00:02
mordredyah - just being clear here in channel00:03
lifelessthere's about a dozen existing files covered by that statement00:03
mordredmoving forward - putting requirements into setup.cfg is totally doable00:03
mordredand I have no personal problem with it - nor do I think it will be particularly confusing to people00:03
lifeless(all the-PYN ones,and the alternative paths)00:03
mordredlifeless: tangent - we should remove *-requires from teh docs but not the code)00:04
mordred we support them for history - but really don't want to add new ones00:04
mordredor something00:04
mordredmark the in the docs as historical abberations00:05
mordredfrom the same people who brought us "rpms" vs. "apts" :)00:05
*** achanda has quit IRC00:05
lifelessyeah00:05
lifelessy00:05
mordredlifeless: do you feel strongly that you want to advocate for a behavior other than unsupported in the presence of both requirements.txt and install_requires ?00:06
lifelesshell no00:06
mordredgreat00:06
*** jamielennox|away is now known as jamielennox00:06
*** davideagnello has joined #openstack-infra00:06
mordredthen I think we have no real problems00:06
lifelessI want both to mean 'use setup.cg and ignore requirements.txt.'00:06
lifelessbut if other people feel strongly I'd be ok with00:06
lifeless'error'00:07
mordredI think I'd like to just not let that condition exist in openstack00:07
lifelessso lets look at that00:07
mordredand if the impl is "setup.cfg overrides requirements.txt"00:07
mordredit won't really matter, since we'll have no repos in that state00:07
lifelessif we have something we're deploying, and we want a requirements.txt for the deploy - to pass to pip specifically.00:07
lifelesswhat would we do ?00:07
lifelesse.g. nodepool.00:08
mordredI do not understand why they would be different00:08
mordredi.e. I reject the premise that that's useful00:08
mordrednodepool will have its deps list in setup.cfg and pip install nodepool will be how you install nodepool00:08
mordredif that doesn't work, then something is wrong with the model00:09
lifelesssay there's a new release of a dep that breaks nodepool.. Would you commit an exclusion to nodepool, or would you override at install time00:09
tchaypoin the discussion about stable branches, one case that was mentioned was if one of nodepool’s dependencies has had a bug introduced in a minor release00:09
mordredyes00:09
mordredI would commit an exclusino00:09
lifelessthats where AIUI requirements.txt is intended to exist.00:09
mordredbeacuse otherwise nodepool is broken00:09
mordredit is quite literally a bug in a nodepool install if that situation exists00:09
tchaypowe might catch it later in CI, but someone doing “pip install nodepool” has no way of knowing what versions we tested in CI00:09
tchaypounless we record it somewhere (I’m not convinced requirements.txt is the right place to record that though)00:10
mordredtchaypo: that's why I've been arguing for == pins for everytihng - but I keep losing00:10
mordredtchaypo: because python breaks things on minors more often than is sane00:10
mordredand what I _can_ assert is that I have tested versions X, Y and Z00:10
tchaypomordred: great, I know who to point the finger of blame at, which is nice - but what I really want is a way to get a running system *now* with a tested-and-working version00:10
lifelessso thats the thing - the split dstufft argues for is that a requirements.txt can have such pins00:10
mordredtchaypo: right00:10
mordredlifeless: but where does the requirements.txt come from?00:11
mordredhow does it solve the problem any better?00:11
dstuffthopefully we can change that by pushing people to use ~= (and maybe a future ^=) and convince people to maintain some semblence of compataiblity00:11
tchayposee my email for a spec..00:11
fungiit's also worth remembering how we got to pbr too (tools/pip-requires files getting preinstalled into virtualenvs). pbr, while perhaps suboptimal, is an evolution of that00:11
*** amitgandhinz has quit IRC00:11
mordredif something breaks nodepool, we'd need to update the requirements.txt00:11
mordredso that users would know about it00:11
mordredwhy not just update setup.cfg?00:11
mordredlike, why keep a separate list?00:11
*** davideagnello has quit IRC00:11
tchaypomordred: for people doing downstream distributions, who might need to consider dependencies for things other than openstack00:12
mordredtchaypo: they're already covered00:12
tchaypohow?00:12
mordredtchaypo: pbr doesn't handled depends at all if you're doing debian packaging00:12
mordredtchaypo: because it's understood that the distro will00:12
jamielennoxthis might be what we are discussing now - but is there a fix for the ceilometerclient cap problem in juno branch?00:12
mordredjamielennox: it's not at all00:12
mordredand i have no idea00:12
*** tiswanso has joined #openstack-infra00:13
tchaypojamielennox: I’ve been thinking about that over the weekend, and I think the solution there is to make the stable jobs non-voting for now00:13
mordredtchaypo: so - yeah - the downstream distros thing in your email is a red herring00:13
tchaypoas I don’t think there’s any way we can ever get consistency with the current jobs00:13
mordredtchaypo: pbr should not be doing anything with versions, tight or not, for downstream distributors00:14
mordredtchaypo: http://docs.openstack.org/developer/pbr/packagers.html00:14
lifelessmordred: requirements.txt is a better thing to edit that install_requires when you're installing a local version of a dep.00:14
mordredlifeless: let me reask the question00:14
mordredlifeless: why would we, as nodepool upstream, put a requirements.txt file into our repo?00:15
jamielennoxgrand scheme there are venvs and such that we could do to make it work, but it doesn't solve the issue of packaging (which i'm generally staying out of)00:15
fungijamielennox: tchaypo: a bunch of lib/client reqs were capped in global-requirements.txt using <=(latest tag) which doesn't work when trying to test proposed changes on top of those stable branches since the'll get (latest tag).postN00:15
lifelessmordred: nodepool is in the special case of00:15
lifelessmordred: 'we write and CD it ourselves'00:15
lifelessmordred: its why I picked it00:15
mordredlifeless: I'm really trying to understand a concrete example of when a requirements.txt would want to go into a git repo00:15
fungijamielennox: tchaypo: simple fix is to change those caps to strictly <(next semver release).000:15
lifelessmordred: so maybe it would go into system-config00:15
mordredlifeless: that's what I'd do for something I was deploying I didn't write00:16
dstufftgenerally upstream doesn't have a requirements.txt unless the expected way of installing something is "git clone and pip install -r requirements.txt"00:16
mordredand I'd expect other fokls to do similar00:16
jamielennoxfungi: the one i'm getting now is pkg_resources.ContextualVersionConflict: (python-keystoneclient 1.3.0.post18 (/opt/stack/new/python-keystoneclient), Requirement.parse('python-keystoneclient<=1.1.0,>=0.10.0'), set(['ceilometer']))00:16
mordreddstufft: if that is the expected way to install it, I'm not likely going to be installing it00:16
lifelessmordred: so if the fix for a nodepool issue was to install a local patched dep; how would you do that today?00:16
fungijamielennox: yep, that's it00:17
* SpamapS tries desperately to catch up to the conversation.00:17
mordredlifeless: system-config00:17
mordredlifeless: although, I'd likely look in to dropping that depend00:17
jamielennoxfungi: i had thought it was a ceilometerclient thing, but that might have been another i saw - i know bknudson was looking at something with keystoneclient caps00:17
lifelessmordred: so if we're willing to say that thats how we keep doing it, then we can say we don't ever need a pip-style requirements.txt in nodepool00:17
fungijamielennox: oh, for that one i think cielometerclient may also have a src-juno job being tested on master. it should stop running that00:17
lifelessmordred: and then we're resolved on this subthread.00:18
tchaypofungi: so that one should be python-keystoneclient<1.2.0 ?00:18
mordredlifeless: cool00:18
fungijamielennox: what's the job name and the branch of the failing change?00:18
*** yamada-h has joined #openstack-infra00:18
dstufftgotta run to the store real quick00:18
mordredlifeless: I believe there is almost no work needed on pbr to support this00:18
bknudsonjamielennox: I was looking at that in stable/juno... haven't had a chance to look a master lately.00:18
jamielennoxfungi: that one is https://review.openstack.org/#/c/171462/ gate-tempest-dsvm-neutron-src-python-keystoneclient-juno00:18
mordredlifeless: it'll mostly be work to update.py in o/r00:18
bknudsonjamielennox: that job should be gone now.00:18
tchaypofungi: there’a thread with subject "novaclient 'stable-compat-jobs-{name}’ broken” with other examples00:18
lifelessmordred: its a shallow patch yes00:19
mordredlifeless: and documentation00:19
tchaypogate-tempest-dsvm-neutron-src-python-novaclient-icehouse00:19
tchaypogate-tempest-dsvm-neutron-src-python-novaclient-juno00:19
jamielennoxbknudson: ah - ok, i rechecked it yesterday and just got around to looking now00:19
mordredlifeless: I believe we already support requires-dist - yeah?00:19
lifelessmordred: I started teh conversation so that if it turned out to be thorny we could make time in vancouver00:19
mordrednod00:19
fungijamielennox: so, .*-src-python-keystoneclient-juno is the "juno backwards-compatibility integration testing for python-keystoneclient"00:19
*** baoli has joined #openstack-infra00:19
mordredlifeless: have brainspace for more pbr chatting while you're here?00:19
lifelessmordred: except everyone hates that key, so there's other work to support that :)00:19
lifelessmordred: I can sure00:19
mordredlifeless: ++00:19
mordredlifeless: it's the one thing we can ALL agree on :)00:19
bknudsonjamielennox: https://review.openstack.org/#/c/172662/ -- it's not gone yet.00:20
fungijamielennox: now that python-keystoneclient has an actual stable/juno branch, we shouldn't run that job any longer00:20
mordredlifeless: the current thinking around the semver patches it to move them to a feature branch and make the stable/0.10 branch master again so that we can have a releasable master branch00:20
fungijamielennox: instead we should just run normal non-backward-compat integration test jobs on all the python-keystoneclient branches00:21
SpamapSI'm really not understanding why any of this is an issue or what we're actually arguing about.00:21
tchaypofrom a brief look at https://review.openstack.org/#/c/166703/ I think it’s also running icehouse/juno tests against master00:21
mordredSpamapS: I think we needed to make sure we all agreed00:21
SpamapSSome people don't like requirements.txt seems like the only thing that might matter?00:21
lifelessmordred: please no; has anyone *tried* to do the minor change needed that I laid out in response to doug00:21
lifelesss mail ?00:21
*** woodster_ has joined #openstack-infra00:22
mordredlifeless: I believe at least two of us have looked at it and it was not minor for our brains00:22
lifelessSpamapS: if you don't care, close eyes and walk on bye. If you do have a specific concern with what we resolved, cool, lets discuss it.00:22
lifelessSpamapS: but please don't reopen it in a vague way :)00:22
*** yamada-h has quit IRC00:22
lifelessmordred: ok, then I'll get this autobuilding wheel patch back passing again for dstufft to review, and do the pbr patch.00:23
SpamapSlifeless: I have concern that there's a massive wall of text here with no clear problem statement beyond "We're doing things that upstream pip considers wrong." .. but I may have missed something important.00:23
jamielennoxfungi, bknudson: so what is keystoneclient's stable/juno branch then?00:23
lifelessSpamapS: that *is* the problem statement.00:23
mordredlifeless: thanks! that would be much happier making- I don't _Really_ want to effectively revert that branch, but it's been blocked for ages00:23
lifelessSpamapS: the wall of text is examining the consequences.00:23
fungijamielennox: i don't understand your question. keystoneclient's stable/juno branch is called "stable/juno"00:23
mordredSpamapS: tl;dr - requirements.txt carries a connotation elsewhere that is different than it does here00:24
bknudsonjamielennox: if we need to backport a security fix we do it to the stable/juno branch00:24
SpamapSlifeless: ok, and right or wrong requires a test, so is the debate around the content of the test, or the relevance of the test (I see points toward both)00:24
bknudsonjamielennox: it's off 1.1.0, so when we fix it's 1.1.100:24
mordredSpamapS: I think it's more "we've diverged from the herd, and there is a low-cost way to re-converge"00:24
fungijamielennox: it's used in exactly the same way as the branch of the same name for all other projects00:24
jamielennoxfungi, bknudson: oh, ok. we are back to tagging clients against the OS release00:24
jamielennoxi saw that on the ML and didn't realize it was decided00:25
bknudsonjamielennox: we decided to cap requirements in stable/branches.00:25
lifelessSpamapS: there is no debate now00:25
SpamapSAh, ok, so test content clarified (pointer perhaps?) and relevance agreed upon?00:25
jamielennoxbknudson: and we're using minor versions for backporting things to stable branches?00:25
lifelessSpamapS: I am so confused. Read the wall of text :).00:26
jamielennoxbknudson: ah micro - the third number00:26
tchaypofungi: when you say " we should just run normal non-backward-compat integration test jobs on all the python-keystoneclient branches” - I think you mean that the normal jobs will notice they’re running on an icehouse branch, so they’ll pull icehouse versions of everything else, so there’s no need to have special jobs for specific branches?00:26
bknudsonjamielennox: y, it'll be the micro increases, since there's already a 1.2.000:26
fungijamielennox: yes, because otherwise we can't fix, say, a keystoneclient bug which affects stable/juno servers using it as a means of communicating with one another00:26
*** wenlock has quit IRC00:26
fungitchaypo: correct, just like they do for all projects with stable branches00:26
jamielennoxfungi: yep, understood00:26
lifelessmordred: are you familiar with https://review.openstack.org/#/c/161047/4/specs/stable-requirements.rst ?00:26
*** salv-orlando has quit IRC00:26
SpamapSlifeless: I'll state it more succinctly, sorry. I don't like using right or wrong without a clear idea of what sort of test I need to apply to decide which space anything is in.00:27
mordredlifeless: I did -1 it :)00:27
tchaypofungi: so in the case of https://review.openstack.org/#/c/166703/ we should be taking those jobs out of python-novaclient as well?00:27
lifelessSpamapS: I don't think right or wrong are useful concepts in the discussion we just had00:27
lifelessSpamapS: I am confused about your use of them here00:28
tchaypoI was only planning to make them non-voting for now, not needing them at all sounds even better00:28
SpamapSlifeless: so if there is a set of rules that upstream or "the herd" has established, that would be helpful to me to understand a) if we're actually doing it wrong, and b) how we can fix it, and finally c) what priority we should commit to fixing it.00:28
fungitchaypo: if the stable/X branches have been created for novaclient already, then yes00:28
lifelesswe're doing it differently. See my mail to openstack-dev for details. And for b). As for c), its tech debt, vs breaking-things-daily.00:29
tchaypofungi: but also, we should be fixing the pins in global-requirements.txt to use <X.Y+1.0 rather than <=X.Y.Z, right?00:29
jamielennoxfungi, bknudson: has the same change been proposed for the other clients? i rechecked https://review.openstack.org/#/c/141994/ but it's essentially failing on the same problem00:29
fungitchaypo: yes00:29
lifelessmordred: so you and jamespage are in disagreement there.00:29
jamielennoxpkg_resources.ContextualVersionConflict: (python-glanceclient 0.17.0.post17 (/opt/stack/new/python-glanceclient), Requirement.parse('python-glanceclient<=0.15.0,>=0.14.0'), set(['ceilometer']))00:29
*** sdake has joined #openstack-infra00:29
tchaypofungi: mrmm. no branches for python-novaclient yet.00:29
bknudsonjamielennox: I looked at updating all the clients but it failed jenkins :(00:30
lifelessmordred: I think that that spec may well have a useful reason for having a requirements.txt that is like pip expects.00:30
fungijamielennox: i am unsure if anyone has been incrementally proposing/fixing those when creating the stable branches for the clients00:30
lifelessmordred: all the transitive requirements flattened out and tied down tightly.00:30
bknudsonjamielennox: see https://review.openstack.org/#/c/172719/00:30
*** tiswanso has quit IRC00:30
fungitchaypo: bknudson: jamielennox: i've not really been involved. i believe ttx has been working with the various ptls on this00:30
lifelessmordred: I don't think we need to reach consensus on that now - but I do think we need to agree that *if* you get convinced on that spec, that the transitive thing wouldn't end up in setup.cfg.00:31
bknudsonjamielennox: I think it's best for other projects to propose these themselves since they know what's going on with their libs.00:31
SpamapSlifeless: mmmk. We have a lot of debt, but I think the thing that causes us to break things all the time is probably the most important facing OpenStack deployers (especially CD), so I'll take your word for it that paying this debt down will lead to less instability in that area.00:31
bknudsonjamielennox: I think it failed because some of the libs didn't do semver right and have reqs updates in their minor update.00:31
lifelessSpamapS: I've made no such claim00:31
jamielennoxbknudson: right, that glanceclient is way outside the restriction even you set and i have no idea what it should be00:31
mordredlifeless: I find it HIGHLY unlikely that I will be convinced that the needs of the gate should be put into a file that pip will ignore00:32
bknudsonjamielennox: in the case of keystoneclient we're using 1.1.0, so the cap should be <1.2.000:32
bknudsonjamielennox: so that we can release a 1.1.100:32
lifelessmordred: sure. But if you are convinced, just not setup.cfg.00:32
mordredlifeless: jamespage has also invoked the strawman redherring00:32
lifelessmordred: thats all I want :)00:32
mordredlifeless: his argument is specious and wrong and factually inaccruate00:32
*** koolhead17 has joined #openstack-infra00:32
bknudsonjamielennox: glanceclient needs to work the same way, otherwise they can't really do this anyways.00:33
jamielennoxbknudson: yea, one of the project (can't remember which) continually bumped the micro only which made it impossible00:33
mordredlifeless: as I explained to tchaypo  just a little bit ago00:33
mordredlifeless: the pining of requirements ONLY affects pip installation00:33
mordredand I feel very strongly that we should not ship things that are known to be broken00:33
SpamapSmordred: What about putting the result of  pip freeze from the gate -- somewhere that woudl be tied to each commit. ?00:33
mordredSpamapS: I feel very strongly that we should not ship artifacts that are different than what we tested00:33
mordredI think that's very rude00:33
tchaypofungi: 7bf16e596d3d672b0454cd33243dddaa3b569a26 seems to have quite a few errant <=s in00:33
mordredand highly confusing00:34
*** sdake_ has quit IRC00:34
mordredespecially since we have the ability to do the other thing00:34
tchaypomordred: I think we all agree on that00:34
mordredand it's not hard00:34
mordredtchaypo: woot!00:34
lifelessmordred: so this means you think we should start specifying the transitive requirements in install_requires?00:34
lifelessmordred: I thought you were very much against that?00:34
SpamapSmrodden: Not suggesting that. Suggesting that each commit would ship the freezes that worked, in addition to whatever we tried to use pass the gate.00:35
SpamapSdoh00:35
fungijamielennox: bknudson: there is a workaround where we invalidate the bad micro bumps with != matches in the requirements lists of the appropriate branches, and then tag new non-micro versions far enough apart on those branches00:35
SpamapSmrodden: sorry, mordred ^^00:35
mordredlifeless: I think that if a transitive depend is so broken taht we cannot pass the gate without pinning it directly in some way00:35
mordredlifeless: then we should put it into install_requires00:35
mordredlifeless: I'm just saying - I do not want a generated set of pins used in the gate _different_ than what a user would get from pip install00:36
mordredif we need to pin in the gate, we need to communicate that we know that to the user00:36
mordredand we need to make the communication of that eh default thing they get00:36
mordredif they want to override it, it's SUPER easy to00:36
mordredsince pip does not actually enforce depends00:36
lifelessah00:37
lifelessit does00:37
lifelessand its getting better at it00:37
mordredneat. pbr also has a SKIP_PIP_INSTALL mode00:37
mordredI'm just sayin00:37
jamielennoxfungi: out of interest can't we force the version bump, could the global requirements bot make commit messages that mean you always force at least a minor version bump if you change reqs00:37
SpamapSBut it doesn't tell you when you're about to violate an existing package's depends, right?00:37
mordredif the software doesn't work without a pin00:37
lifelessit matters somewhat now, it's going to matter more in future00:37
mordredwe should pin00:37
mordredif you feel strongly that you want to override what we've told you is broken00:37
mordredthat's on you00:37
mordredand you can figure it out00:37
lifelessso I'm confused again00:38
mordredbut the burden should be on the person who thinks they know better tahn the gate00:38
lifelesssince you seem to be arguing something that noone proposed00:38
SpamapSAlso do we have a sense of how much of "The way upstream works" has to do with how often people deploy in isolation via virtualenv/containers/etc?00:38
tchaypo"I think that if a transitive depend is so broken taht we cannot pass the gate without pinning it directly in some way” - that’s a reactive situation, where we see something *did* break and we need to communicate that users should *not* install that version as it’s known bad00:38
mordredlifeless: have yuo read the sepc?00:38
lifelessAIUI the proposal for the gate is to reduce unexpected churn00:38
mordredlifeless: have you read my -1?00:38
mordredno00:38
lifelessmordred: I have00:38
mordredthe proposal is to not do that00:38
mordredit's to have the gate produce a file that is not what is shipped with the software but which is what the gate will pin on00:38
tchaypobut this doesn’t seem to have space for a pro-active notification where we tell users “we expect that all sub-versions of X.Y should work, unless noted otherwise"00:38
mordredand I am categorically opposed to that00:38
lifelessmordred: thats the mechanism, not the reason00:39
mordredlifeless: I am opposed to the mechanism00:39
mordredmy -1 says that00:39
mordredI think the proposal in genereal is fine00:39
mordredthe mechanism here is highly important00:40
mordredit's the entire subject of our conversation00:40
lifelessmordred: it also says in the summary that the intent is to capture the information so folk can use it later00:40
mordredwhy would you not capture it in the default instructions for machine installation of the software?00:40
mordredthe idea that people should need to opt-in to a good installation is bonghits00:40
tchaypowould you be less opposed if we reversed it - put the broad requirements in requirements.gate, and had the gate generate a requirements.txt that exactly matches what was tested?00:41
mordredwhy would we have two lists?00:41
mordredwhat does it help or solve?00:41
lifelesstchaypo: the gate is too late though, the commit has already been made00:41
mordredour requirements should be as broad as they _Can_ be00:41
*** amitgandhinz has joined #openstack-infra00:42
mordredso - publishing the list of what specific versions we used is a good idea00:43
mordredand we do it00:43
mordredalready00:43
mordredhaving a different file that is not used by the installation of te software be used in devstack00:43
mordredleads us to a place where we are shipping softare that is different than what we are testing - which benefits literally no humans00:44
*** sdake_ has joined #openstack-infra00:46
tchaypolifeless: I was thinking of gating to changes on the global-requirements repo, but I think you’re right - I think you mean we really want something that catches the versions on the repo being tested00:47
tchaypomordred: where do we publish the list of specific versions that went through CI?00:47
bknudsontchaypo: most of the jobs have the pip freeze output.00:48
bknudsonbtw - it would be great if we could run the tests with the min versions of all the packages, too.00:49
*** sdake has quit IRC00:49
tchaypoHow does someone installing or distributing the package get access to that though?00:51
*** koolhead_ has joined #openstack-infra00:52
*** sdake has joined #openstack-infra00:52
bknudsonwe don't... we look at requirements.txt files00:52
tchaypoIf I was to do it, I think I’d have to figure out the last check on the last review that landed before the release, then grovel through the output00:52
tchaypoTo me that doesn’t sound like something we “published” - especially since iirc the logs for the gate checks get rotated out after a few months00:53
mordredtchaypo: right. that's why I have been advocating hard-pins of all our stable braches for several years now00:54
bknudsonprobably the way to do it is to pin the stable/ requirements.txt on release.00:54
mordredbknudson: ++00:54
mordredthe only argument agains that is "some upstream python library might release a bugfix"00:55
mordredwhich has categorically been proven nothing but untrue00:55
fungibknudson: the trick is identifying "minimum versions of our requirements"00:55
*** koolhead17 has quit IRC00:55
fungibknudson: we have a tool which can install "the highest version matching a given set of constraints" and that tool is called pip00:55
mordredthat this is so complex should make it clear that anything other than hard-pins on stable is crazy00:55
lifelessok, commented on the spec00:55
mordredwhy do we care about lowest versions?00:56
mordredit is not useful00:56
*** sdake_ has quit IRC00:56
mordredthe only thing that is useful is "_this_ will install and work"00:56
mordredif other people want to look at other combinations of stuff - awesome00:56
fungii agree. the only reason i can see for testing declared minimums is to see of they're actually legitimate00:56
lifelessmordred: so the compat thing is that we have a dozen projects00:56
lifelessthey all need to be mutually installable today00:57
bknudsonI don't think the current mins are legitimate.00:57
fungii'm quite sure they're not00:57
bknudsonat least the keystoneclient tests don't work.00:57
mordredlifeless: yup00:57
tchaypoand we have downstream people preparing distributions of openstack+other things, and we need openstack to be mutually installable with those things00:57
mordredlifeless: that has been echoed by the operators, btw, not just the distros00:57
lifelessthats why install_requires *must* be as broad as it can00:57
mordredI disagree00:57
mordredthat's why install_requires must be as strict as possible00:57
lifelesswe can't change a dozen projects atomically00:57
mordredas strict _As_ _possible_00:57
fungitchaypo: we also publish a robust testsuite which downstreams can use to find out of the versions of things they already have packaged work with what we're releasing, without us needing to check that for them00:58
fungier, find out if01:01
tchaypoand if a downstream wants to start their testing by reproducing exactly what we tested - how do they do that?01:01
lifelessmordred: we get that strictness wrong a lot IME01:02
lifelessmordred: such as failing to bump lower versions during dev cycles01:02
lifelessmordred: before using features.01:03
lifelessmordred: I don't know what the answer is here.01:03
dstufftmordred: it's not just bug fixes, if you're strict you make it hard (or impossible) to actually isntall your thing01:03
dstufftalongside other things I mean01:03
dstufftyou're basically promising dependency hell unless you stick every single top level thing in it's own virtualenv01:04
*** Longgeek has joined #openstack-infra01:04
jamielennoxbknudson: with your change or after?01:06
mordreddstufft: I do not believe we're suggesting that installing our thing alongside somethign else is a feasible thing01:07
fungitchaypo: they can look at the pip freeze output from our tests, if they're trying to reproduce an explicit set of our test results. that's why we include pip freeze output in the logs01:07
bknudsonjamielennox: what's the question about?01:07
dstufftmordred: what's the "thing" in question? For the python clients it's absolutely a feasible thing01:07
dstufftif it's not you might as well jsut rm -rf them01:07
*** baoli has quit IRC01:07
mordreddstufft: the python clients purpose in life is intra-service communication01:07
jamielennoxbknudson: oh, mentioning ksc highlighted your last message, didn't realize it wasn't directed at me - nevermind01:07
mordreddstufft: they are not written to be use facing01:08
mordreduser01:08
mordreddstufft: so, yes, you might as well rm -rf them01:08
mordredthey are a part of the servers - and outside of that you probably need to install them into venvs01:08
bknudsonjamielennox: see https://review.openstack.org/#/c/172655/01:08
bknudsonjamielennox: we were talking about that the other day... I tried using mock before.01:08
dstufftmordred: so nobody else is supposed to depend on them or use them?01:08
mordreddstufft: we're talking about stable branches here01:09
mordredso no01:09
mordredend users should use the latest release of a client lib01:09
mordredwhich should not be aggressively pinned01:09
mordredbecause it is the thing that will work with everything01:09
jamielennoxbknudson: yep, i remember - nice that it doesn't use mock, scary that we have code that doesn't care what the cookie is, just that something has been set01:09
lifelessmordred: now, I think we're making progress. I've realised a source of cognitive dissonance.01:10
fungidstufft: server x imports a "client library" corresponding to server y and then uses it to communicate with server y01:10
lifelessmordred: see the list :)01:10
mordredhowever, with a juno release, what nova needs to know is that the copy of keystoneclient it installs on its bo will work01:10
mordredlifeless: looking01:10
dstufftmordred: maybe I'm confused, I thought that python-novaclient was like boto for AWS, except just for nova, where you'd use it in your own application01:10
lifelessdstufft: we thought that for ages01:11
lifelessdstufft: and some of the projects do think of their library like that.01:11
fungidstufft: so the version of the library that existed at the time those servers were released should be able to work with that release version of those servers as far as their needs for communicating with one another is concerned01:11
lifelessdstufft: but01:11
lifelessdstufft: tere is now a specific UI one - openstackclient01:11
mordredlifeless: my main concerns is that python libraries all suck01:11
dstuffts/python //01:11
mordreddstufft: ++01:11
lifelessmordred: yes they do01:11
mordredlifeless: and they break things CONSTANTLY01:11
lifelessmordred: and you are right about that01:11
lifelessmordred: BUT01:12
mordredlifeless: so, what I want to make sure we don't do01:12
mordredfor our _stable_ branches01:12
mordredis test one thing and ship another01:12
mordredin the name of "flexibility"01:12
lifelessmordred: flexability isn't the cause here01:12
lifelessmordred: I can state the problem without that strawman - I think I did in fact01:12
mordredlifeless: I would like you to try again, because I don't think you did :)01:12
fungidstufft: essentially, if debian packages nova and glance, and nova is using python-glanceclient to communicate with glance, the version of python-glanceclient they'll have packaged will be comtemporary with the versions of nova and glance they packaged. we're doing similar things on our stable branches of python-glanceclient to support that use case (as opposed to the end-user/app-developer needs to01:13
fungicommunicate with a cloud service use case)01:13
dstufftfungi: so my point was really that if you expect random end users who want to interact with an openstack cloud to install these things, you can't use == inside of python-*client (or any of their dependencies)01:14
mordreddstufft: right. but that's the thing01:14
mordreddstufft: we cannot use that in the python-*clent we expect users to install01:14
mordreddstufft: 100% agree01:14
lifelessmordred: https://etherpad.openstack.org/p/stable-omg-deps01:14
tchaypofungi: *thinks* for someone looking at the source, that’s probably easier than for someone getting the package - they can at least look at the git log, find the last commit sha, look that up on gerrit, find the last set of gate checks on the review..01:15
fungidstufft: this is the use case of the library being installed onto a server where these services are also running, for communicating with one another01:15
mordreddstufft: pinned versions of client libs are not expected to be installed by users01:15
*** unicell has quit IRC01:15
mordreddstufft: I am 100% against them doing that01:15
tchaypofungi: but am I wrong in thinking that the pip-freeze output is eventually going to go away as the logs get rotated out?01:15
dstufftmordred: does openstack support mix and match versions of the server libraries?01:15
dstuffts/libraries/processes/01:15
lifelessmordred: thats a problem statement01:15
dstufftlike can you have nova from version X and swift from version Y01:16
lifelessmordred: based on what I believe you want us to achieve01:16
lifelessdstufft: ish01:16
fungithe servers are unfortunately too tightly-coupled to one another and to their use of those libraries for intercommunication, such that they can't well replace the version which was available when they released with a much newer version of the library and still talk to each other, so we need to have multiple release branches for the libraries01:16
lifelessdstufft: swift releases outside the 6-month cycle01:16
dstufftlifeless: well I just pciked a random two names that first poped into my head01:16
lifelessdstufft: so some skew is expected. The rest of the project only test skew during upgrades, not for regular use01:16
mordreddstufft: nova needs to know which version of the python library it is going to use01:16
dstufftreplace swift with glance or wahtever01:16
mordreddstufft: that version of the client libary will support more than just that version of other servers it's going to talk to01:16
dstufft== would mandate that you upgrade everything in lock step if you install two servers into the same environment of different versions01:17
mordreddstufft: so, the client libraries have a decent range of support for remote rest protocol01:17
*** yamahata has joined #openstack-infra01:17
*** unicell has joined #openstack-infra01:17
lifelessfungi: we could try to actually fix that coupling :) Or bundle all our things into one release rather than 4 billion permutations. But thats a different near-rant.01:17
mordreddstufft: but if nova stable/juno depends on python-novaclient==2.12.20 - that's about the _python_ interface it needs01:17
lifelessmordred: did you do the ++ in the etherpad ?01:17
mordredlifeless: yes01:17
fungilifeless: i think we _should_ fix that, but i doubt we could get all the projects to just stop doing anything else until we get there01:17
lifelessfungi: if we didn't work around that... anyhow. tangent.01:18
dstufftmordred: sure, buit what you want to also install barbican unstable/wahtever which maybe depends on python-novaclient==2.15?01:18
lifelessok so we have a problem statement01:18
mordreddstufft: you can't do that01:18
mordreddstufft: it's completely unsupported and always will be01:18
dstufftmordred: ore ven beyond that, what about a 2nd release from the stable branch with an updated requirement01:18
fungiyou get to keep both pieces, as they say01:18
dstufftso if you have 2015.4.0 and 2015.4.101:19
mordreddstufft: that 2nd release from the stable branch will need to correspond with making sure that nova also has a release01:19
*** yamada-h has joined #openstack-infra01:19
mordreddstufft: or that the release is compatable with the stable nova that exists01:19
*** dimsum_ has quit IRC01:19
mordreddstufft: doing that is tractable and we can make sure it works01:19
dstufftmordred: right, but you're going to force deployers to upgrade _everything_ in lock step in that scenario instead of being able to do it one server process at a time01:19
mordreddstufft: including unstable barbican on the same box installed via pip without virtualenvs is not01:19
mordreddstufft: most deployers arent' installing via pip01:19
mordreddstufft: most are making their own distro packages01:20
mordreddstufft: the ones who are installing via pip are insatlling into virtualenvs and/or containers01:20
fungiin general the x.y.* versions for one project are expected to work with the a.b.* versions of another project which released in the same timeframe and which use the same branch names01:20
lifelessI'm now brainstorming solutions on that etherpad.01:21
tchaypolifeless: mordred: I understand that rpm/deb installers don’t use pip; but my understanding is that the distro toolchains will use pip’s idea of what needs to be installed as the basis for the OS package’s list of dependencies01:21
*** achanda has joined #openstack-infra01:21
*** baoli has joined #openstack-infra01:21
dstufftmordred: btw, how do you even test this? Doesn't this require that you can merge a patch to update the pinned version across all projects at once? You can't land it in one, run it through CI, thne land it in another01:22
tchaypoif our list is too tight, it requires manual work from the maintainers to find something that fits with the rest of the release; if we can be looser (but still tight enough that they have confidence about what’s tested and expected to work) it reduces the manual work they have to do01:22
tchaypobut I have never been an upstream distro maintainer so I could be very wrong, again..01:22
fungitchaypo: i think the distros are going to want to use the versions of things they've already packaged if possible, plus the newest versions of things we claim to support which they haven't yet packaged. seems like any other expectation is pathological01:22
tchaypofungi: sounds reasonable01:23
*** yamada-h has quit IRC01:23
fungiwe also provide tools they can use to test those things together and double-check whether they'll work01:23
mordreddstufft: we do an override sync with teh global requirements in our integration tests01:23
dstufftmordred: do you do that in a way that it gets piped into isntall_requires?01:24
mordreddstufft: yes01:24
dstufftok01:24
*** liusheng has quit IRC01:24
*** amotoki has joined #openstack-infra01:25
*** liusheng has joined #openstack-infra01:28
*** dimsum_ has joined #openstack-infra01:28
tchaypodoes that mean that the requirements.txt in individual project repos actually don’t represent the input to the CI system?01:30
*** mriedem has quit IRC01:30
*** mriedem has joined #openstack-infra01:31
lifelessdstufft: but we don't have to. We could equally use a separate file. We *don't capture the override contents today*' - at least AFAIK01:31
lifelessI need to grab food. You folk not on etherpad should peek :).01:34
*** baoli has quit IRC01:35
*** dimsum_ has quit IRC01:35
*** otter768 has joined #openstack-infra01:35
* tchaypo hunts for etherpad link01:36
fungitchaypo: they're used in most single-repo jobs, e.g. for unit tests, but devstack-gate integration testing jobs specifically have a routine which overwrites them with what's in the corresponding openstack/requirements branch so that it has a consistent set when co-installing all of them01:36
mordredfungi, tchaypo: just had some fairly complete thoughts about test metadata annotation post-commit into git notes on openstack/openstack01:41
fungiwe sort of capture the requirements used, insofar as we checkout a specific ref from the openstack/requirements repo in an integration test and that is logged01:41
tchayposo both sets of requirements count as “tested in ci” because they’re tested in different checks?01:41
fungiright01:42
fungiwe would like to always test what is actually declared in individual repos, but for the sake of single-env integration between multiple repos that's just not tractable, hence the rewriting we perform01:43
mordredfungi, tchaypo, jeblair (when around): https://etherpad.openstack.org/p/stable-omg-deps - starting aroudn line 2701:43
mordredwe could record dpkg-get-selections that way too01:44
mordredso that deployers and folks could dig back through and find out exactly what was going on01:44
mordredok. with that -I need to eat some food01:45
tchaypoit’s 11:45am, so I should probably get that breakfast I’ve been putting off as well01:45
tchaypoDo we want pip installs of stable releases to be possible as well?01:46
tchaypoI’ll speculatlively add something and we can remove it if it’s wrong01:46
mordredtchaypo: I think so, yes01:46
clarkbwhats the issue here?01:49
clarkbthe problem statement is false01:51
clarkbyou CAN reproduce based on the freeze capture01:51
tchaypoclarkb: if you can find the freeze capture.01:52
clarkbits in every job log...01:52
tchaypoif that log hasn’t been wiped01:52
tchaypoI just did “pip install nova” and I expect pip to reproduce what CI did - how should pip go about finding the freeze capture that’s related to the package I’m installing?01:52
clarkbhow is that different than anything else?01:53
clarkbyes if you delete the data its gone01:53
tchaypowhich changes your statement from “you CAN reproduce” to “you MAY be able to reproduce"01:53
clarkbtcgaypo you go get it01:53
clarkbno its just as CAN as any other option01:53
tchaypoI’d like it to be more CAN01:53
lifelesstchaypo: pip install nova can't reproduce what CI did for two reasons.01:54
clarkbI thibk my concern is that we will spend so much time fixing a broken pip system with more hacks01:54
clarkbwhen we really need to just fix pip01:54
lifelessclarkb: we are fixing pip01:54
lifelessclarkb: I'm trying to get rid of our local hacks. Its what provoked this discussion at all.01:55
lifelessclarkb: mordred has been focused on making our install_requires provide as close a match to what CI tested as possible.01:55
tchaypo+1 for fixing the problem in pip if possible01:55
tchaypobut I think part of that is going to be giving pip better data to use01:55
lifelessclarkb: this doesn't work - we know it doesn't work because we don't actually use our install_requires at all anyway. We override it!01:56
clarkblifeless I do not see make pip resolve deps properly on the etherpad01:56
clarkbanything else is not fixing pip01:56
lifelessclarkb: it doesn't need to give better reproducability.01:56
clarkbit does01:56
clarkbbecause install resolution can change over time01:56
clarkbbecause it doesnt resolve sanely01:56
lifelessclarkb: no, it doesn't. https://github.com/pypa/pip/issues/988 1a.01:56
lifelessclarkb: a requirements.txt file (*not* what pbr does) will win, assuming everything else is compatible.01:57
lifelessclarkb: which it will be, because it was at the point in time CI ran.01:57
clarkborder matters here and its depth first iirc01:57
clarkbrequirements.txt doesnt always win today01:58
lifelessclarkb: order matters, which is why everything will be there.01:58
lifelessclarkb: what happens today is pbr, so install_requires, *not* -r.01:58
clarkbbut order can change transitively01:58
lifelessno, it can't.01:58
clarkbwhy not?01:58
*** mriedem has quit IRC01:58
lifelessbecause we're giving pip everything up front. All the actual discovery is going to happen after that.01:58
clarkbyou are going to list every transitive dep? how do you do that?01:58
lifelesspip freeze01:59
clarkbok so the pypi mirror hack01:59
lifelesshuh?01:59
clarkbinstall everything01:59
clarkbthen check01:59
lifelessThat seems like a non sequitor01:59
clarkbthen do it again01:59
lifelessno01:59
lifelesswe do CI01:59
fungie.g. give up on using pip like a package manager which can find transitive dependencies and just use it as a "install this list of things i don't care of they depend on other things i worked it out for you already"01:59
lifelessusing what we do today.01:59
lifelessAnd we capture the end result for other folk to use to reproduce what we used.02:00
lifelessThats the problem statement.02:00
clarkbwe already do that...02:00
lifelessfungi: for the specific case of 'reproduce what CI did'02:00
clarkbI really dint understand what needs to change. maybe where the pip freeze is stored?02:00
fungioh, and then have a different list for people who just want to `pip install python-novaclient` or whatever?02:00
clarkbalso phone keyboard is terribad02:00
lifelessfungi: right. pip install python-novaclient does not need to reproduce CI exactly. It can't ever.02:01
fungiyeah, typing from bed is not much better02:01
lifelessfungi: so we decouple the problem, and do a near-perfect job for reproducing what CI had - including dpkg package lists and so on.02:01
tchaypoI feel like we need to remind a bunch of you that “This is sunday, you should be doing something fun"02:02
dstufftreproducing an enivornment is basically what requirements is for02:02
fungilifeless: so i think part of "make a simple way to reproduce _the_one_environment_ in which this commit was tested" presupposes that we first solve making all jobs which test that commit use an identical environment?02:02
lifelessfungi: and let pip install python-novaclient do what its designed to do, which is to exclude everything known not to work02:02
tchaypoexcept that you might actually think this is fun02:02
dstufftora t least one of the things02:02
fungior do you expect to have multiples of these recorded?02:02
lifelessfungi: I'd start by recording one per environment - name it after the job02:02
fungik02:03
clarkblifeless we literally already do that02:03
clarkbits one per env based on the job02:03
fungiwell, except for multi-virtualenv jobs02:03
fungie.g. tempest02:03
*** weshay has quit IRC02:03
lifelessclarkb: we don't record it persistently.02:04
fungithat seems like a different problem which we can tackle easily enough02:05
fungirecord that to a different file with a different retention period02:05
lifelessclarkb: we also don't tie it back to the commit very well02:05
fungisome additional indexing can help there?02:05
lifelessclarkb: I think both of those things need to be solved to make this as convenient as I think it needs to be for mordred to relax his death grip on 'pip install'02:05
lifelesswe have 1000 developers02:05
clarkblifeless sure we can make it better02:06
clarkbI just dont understand what we are solving02:06
clarkbfrom what I read it is already done02:06
lifelessI'll let you and mordred debate that02:06
fungilots of different somewhat-interrelated things from what i can gather02:06
clarkbwe have apt/yum listings and pip freezes02:06
lifelessIf it was already 'done', I don't think he'd care nearly so much about install_requires being reconstruction of CI02:06
lifelessclarkb: if you're referring to whats in the job logs... there's an awful lot of knowledge needed to use that to make nova head work.02:07
clarkbyes it is a job log02:07
clarkbwe can publish a known set somewhere02:08
clarkbbut the source is always a job log because thats what it is02:08
fungimaybe going up another level would help. what sort of command would you want to run, and what sort of specific outcome would you want from that command? that would be a start toward being able to design the tools and data sources to support it02:08
lifelessright02:09
*** koolhead17 has joined #openstack-infra02:09
tchaypoI’d like for the published set to be stored close to the package/repo that’s going to be used to do the install02:09
lifelessmordreds example is 'pip install git+..../nova.git'02:09
tchaypoI’d like to avoid getting in a situation where we still have the source but can’t reproduce the install because $WEB_SERVICE is down, or lost data02:09
lifelesswhich I do not believe can ever work that literally, because of incompatible constraints02:10
clarkblifeless there is a chickenand egg there02:10
clarkbcant have a commit with known deps until it merges02:10
clarkbso yes02:10
lifelessI think we could sensibly do 'bindep install git+..../openstack/openstack.git/nova';'pip install -r git+.../openstack/openstack.git/nova-requirements.txt' or something like that02:11
*** sdake_ has joined #openstack-infra02:11
fungilifeless: and he would want `pip install git+..../nova.git` to specifically install the nova dependencies with which that particular commit was tested (forgetting for a moment that there are different dependency sets used for different test jobs)?02:11
*** koolhead_ has quit IRC02:11
lifelessfungi: "On 13 April 2015 at 12:53, Monty Taylor <mordred@inaugust.com> wrote:02:12
lifeless> What we have in the gate is the thing that produces the artifacts that02:12
lifeless> someone installing using the pip tool would get. Shipping anything with02:12
lifeless> those artifacts other that a direct communication of what we tested is02:12
lifeless> just mean to our end users.02:12
lifeless"02:12
fungiokay, so specifically recreating the environment in which python setup.py sdist was run in the tarball/wheel jobs02:12
*** yamamoto has joined #openstack-infra02:13
lifelessfungi: I read that differently. I read it as recreating the environment in which tempest passed.02:14
fungias those are the only artifacts i can think of our "gate" (really it's not happening in the "gate" pipeline, but whatever) produces which people then install02:14
lifelessfungi: as far as dependency and code goes, not configuration.02:14
*** sdake has quit IRC02:14
lifelessfungi: yes, the language was terrible. The intent was, I think, clear. Users should get what we know works.02:14
clarkb1) you need to figure out which set(s) your users want 2) if sets disagree what is resolution?02:15
fungihrm. i still think we're a long way from having "a consistent thing we know works" that we could even communicate to them02:15
*** salv-orlando has joined #openstack-infra02:15
lifelesssets?02:15
clarkbright I think ^ is problem to solve first02:15
clarkbthen worry about publishing02:15
clarkblifeless we test on at least 2 operating systens with multiple python versions and mutliple input requirement seeds02:16
fungiwhat "works" is currently a nebulous set of different kinds of tests run in all sorts of different kinds of environments02:16
clarkbthis all produces differebt outputs that are known to work02:16
lifelessclarkb: yes, thus my proposing we capture each02:16
clarkblifless but if I pip install locally I only want 102:17
clarkbso we need to filter/distill the one thing02:17
fungistep 1: capture information on all our different job environments, step 2: ..., step 3: profit!02:17
tchaypoI think we also have multiple sets of users  - deployers vs distributors at least?02:17
lifelessclarkb: huh, the example I gave - a requirements.txt file - lets you choose.02:17
tchaypobut probably they can use much the same set of information for their purposes02:17
lifelessclarkb: the example of pip install git+.../nova.git is problematic, but thats yet another reason trying to cram it into install_requires won't work.02:18
openstackgerritJoshua Hesketh proposed openstack-infra/os-loganalyze: Tidy up generators into contained objects  https://review.openstack.org/17271102:18
openstackgerritJoshua Hesketh proposed openstack-infra/os-loganalyze: Add support for non-text files  https://review.openstack.org/10726702:18
*** baoli has joined #openstack-infra02:18
fungiright, as you say we could make is so they could choose to install the environment in which tempest was known to pass, or the environment in which nova python 2.7 unit tests were known to pass, or ... or ...02:18
*** salv-orl_ has joined #openstack-infra02:18
lifelessI don't think unit tests are a candidate here. But if its no harder to capture that, sure.02:19
lifelesscapture == massage into easy to use fashion.02:19
*** yamada-h has joined #openstack-infra02:19
fungithough tempest is still a bad (or perhaps important?) example because it uses multiple environments to run one job (so that it can potentially install multiple versions of the same thing on one server)02:19
*** yamahata has quit IRC02:20
*** salv-orlando has quit IRC02:20
lifelessclarkb: how did you go with ovs?02:21
*** zz_dimtruck is now known as dimtruck02:21
clarkbI am not sure that dumping all that info is any more helpful than the info dumo we do today02:21
clarkblifeless terrible02:21
lifelessclarkb: now is clearly not the time. Tomorrow I can help you if you like. After C's swimming lesson in the morning, that is.02:21
clarkbit doesnt work, fungi and markmcclain were going to lend tgeir eyeballs too02:21
clarkblifeless sure ping me when you have time02:21
fungii haven't made any modifications to those held workers yet02:22
clarkbok I can hold more too02:22
*** yamada-h has quit IRC02:24
clarkbI wonder if it would be easier to start with much more control of the input env02:25
clarkband just advertise what that is ( though with pip likely not )02:25
lifelessclarkb: how do you mean?02:27
clarkbhave a single versioned env02:27
clarkbso we tested on foodistro version X02:27
clarkbthen say 2016.1.1 is compat with ^02:28
tchayposo that would eliminate things like differences in underlying C libraries between ubuntu and fedora, for instance?02:28
clarkbright02:28
clarkbnot surr it helps the pip install case though02:29
lifelessits an aspect of the same issue02:29
tchaypowell, not eliminiate the differences - but eliminiate the problem where a given set of our packages are tested/working on fedora but broken on ubuntu02:29
fungiyeah, i'm still a little iffy on, for example, bindep caring about package versions explicitly. it's _rare_ that someone has multiple versions of a single distro package name available to them on a particular distro release02:32
fungisaying "if you're running ubuntu 14.04.* install this package name" makes sense02:33
fungiincluding the versions of distro packages present on the system in what we list for this purpose is of course fine, since it's useful for comparing environments and trying to work out if a bug was introduced in a distro backport patch or something02:34
fungibut having bindep magically figure out how to get that exact version of a distro package seems like a lot of work for very little gain02:34
fungianyway, i'm out for the night. later all02:35
*** dimsum_ has joined #openstack-infra02:35
*** Longgeek has quit IRC02:38
*** ricolin has quit IRC02:39
*** Longgeek has joined #openstack-infra02:40
*** dimsum_ has quit IRC02:41
*** achanda has quit IRC02:44
*** achanda has joined #openstack-infra02:48
*** salv-orl_ has quit IRC02:49
*** oomichi has quit IRC02:55
*** amitgandhinz has quit IRC02:55
openstackgerritMerged openstack-infra/project-config: Make a check experiemtal bandit for for python-magnumclient  https://review.openstack.org/17246002:56
*** achanda has quit IRC02:59
*** amitgandhinz has joined #openstack-infra02:59
*** pal has joined #openstack-infra03:00
openstackgerritMerged openstack-infra/project-config: Fix Python 3 issues  https://review.openstack.org/17223903:08
*** subscope_ has joined #openstack-infra03:12
*** amitgandhinz has quit IRC03:12
*** baoli has quit IRC03:15
*** dkehn has joined #openstack-infra03:18
*** woodster_ has quit IRC03:20
*** dhritishikhar has joined #openstack-infra03:22
*** asettle is now known as asettle-lunch03:22
*** yamamoto has quit IRC03:23
*** yamamoto has joined #openstack-infra03:23
*** koolhead17 has quit IRC03:24
*** dkehn has quit IRC03:25
*** sdake_ has quit IRC03:25
*** unicell1 has joined #openstack-infra03:35
*** unicell has quit IRC03:37
*** salv-orlando has joined #openstack-infra03:39
*** woodster_ has joined #openstack-infra03:47
*** gpocentek has joined #openstack-infra03:48
*** gpocentek has quit IRC03:48
*** gpocentek has joined #openstack-infra03:48
*** ajmiller has quit IRC03:50
*** dhritishikhar has quit IRC03:51
*** otter768 has quit IRC03:54
*** crc32 has joined #openstack-infra03:54
*** amitgandhinz has joined #openstack-infra03:56
*** dhritishikhar has joined #openstack-infra03:57
*** crc32 has quit IRC03:58
*** achanda has joined #openstack-infra03:59
*** amitgandhinz has quit IRC04:01
*** salv-orlando has quit IRC04:02
*** achanda has quit IRC04:05
*** asettle-lunch is now known as asettle04:08
openstackgerritMerged openstack-infra/project-config: Add check-tempest-dsvm-f21 to experimental queue for openstack/nova  https://review.openstack.org/17179504:10
*** unicell1 has quit IRC04:11
*** unicell has joined #openstack-infra04:12
openstackgerritMerged openstack-infra/project-config: keystone bandit job on check  https://review.openstack.org/17056904:13
openstackgerritMerged openstack-infra/project-config: Make a check experimental bandit job for Magnum  https://review.openstack.org/17195404:15
*** rm_work|away is now known as rm_work04:17
*** koolhead17 has joined #openstack-infra04:19
*** yamada-h has joined #openstack-infra04:21
*** yamada-h has quit IRC04:26
*** kaisers has joined #openstack-infra04:27
*** BharatK has joined #openstack-infra04:29
openstackgerritMerged openstack-infra/project-config: Add a job to build Gerrit javamelody plugin ver 2.10  https://review.openstack.org/17269204:30
openstackgerritMerged openstack-infra/project-config: Publish shade docs to docs.openstack.org/infra  https://review.openstack.org/17022304:35
*** tiswanso has joined #openstack-infra04:35
*** mrmartin has joined #openstack-infra04:37
*** deepakcs has joined #openstack-infra04:39
*** subscope_ has quit IRC04:43
*** tiswanso has quit IRC04:49
*** amitgandhinz has joined #openstack-infra04:57
*** sabeen has quit IRC05:04
*** liusheng has quit IRC05:06
*** liusheng has joined #openstack-infra05:06
*** yfried has quit IRC05:12
*** sks has joined #openstack-infra05:14
*** btully has joined #openstack-infra05:18
*** yamada-h has joined #openstack-infra05:22
*** dimtruck is now known as zz_dimtruck05:24
*** yamada-h has quit IRC05:26
*** dhritishikhar has quit IRC05:46
*** koolhead17 has quit IRC05:46
*** dhritishikhar has joined #openstack-infra05:48
*** ildikov has quit IRC05:53
*** achanda has joined #openstack-infra05:53
*** otter768 has joined #openstack-infra05:55
*** dhritishikhar has quit IRC05:55
*** dhritishikhar has joined #openstack-infra05:56
*** sushilkm has joined #openstack-infra05:57
*** sushilkm has left #openstack-infra05:57
*** amitgandhinz has quit IRC05:58
*** otter768 has quit IRC05:59
*** AJaeger has joined #openstack-infra06:02
*** koolhead17 has joined #openstack-infra06:06
*** aswadr has joined #openstack-infra06:08
*** afazekas has joined #openstack-infra06:08
*** mrmartin has quit IRC06:12
*** Guest49005 has quit IRC06:13
*** mrunge has joined #openstack-infra06:13
*** Longgeek has quit IRC06:14
*** Longgeek has joined #openstack-infra06:14
*** yfried has joined #openstack-infra06:15
*** mrunge has quit IRC06:16
*** mrunge has joined #openstack-infra06:17
*** mrunge has quit IRC06:17
AJaegerttx, please ping me regarding translations when you're awake and have a few minutes06:17
*** sushilkm has joined #openstack-infra06:20
*** sushilkm has left #openstack-infra06:21
*** Ala has joined #openstack-infra06:21
*** yamada-h has joined #openstack-infra06:23
*** koolhead17 has quit IRC06:25
*** jcoufal has joined #openstack-infra06:26
*** yamada-h has quit IRC06:27
openstackgerritJamie Lennox proposed openstack-infra/project-config: Add django-openstack-auth-kerberos project  https://review.openstack.org/17280306:29
*** tnovacik has joined #openstack-infra06:32
*** rwsu has joined #openstack-infra06:34
*** scheuran has joined #openstack-infra06:37
*** yfried is now known as yfried|afk06:38
*** yfried|afk is now known as yfried06:39
GheRiveromorning all06:40
*** mpaolino has joined #openstack-infra06:41
*** e0ne has joined #openstack-infra06:41
*** ibiris_away is now known as ibiris06:41
*** e0ne has quit IRC06:42
*** yamahata has joined #openstack-infra06:42
*** mrunge has joined #openstack-infra06:46
*** devvesa has joined #openstack-infra06:48
*** yfried is now known as yfried|afk06:49
openstackgerritMerged openstack-infra/project-config: Stop running gate-tempest-dsvm-neutron-src-python-keystoneclient-juno  https://review.openstack.org/17266206:53
*** soren has joined #openstack-infra06:55
*** yfried|afk is now known as yfried06:56
*** _nadya_ has joined #openstack-infra06:57
*** markus_z has joined #openstack-infra06:57
*** hdd has joined #openstack-infra06:58
*** ajo has joined #openstack-infra06:59
ttxAJaeger: I'm here07:00
AJaegermorning, ttx!07:00
AJaegerI've run a script over all server projects to check current translation status of files.07:00
AJaegerOUtput is http://paste.openstack.org/show/203412/07:00
ttxlooking07:00
AJaegerThe number is just percentages07:00
*** hdd has quit IRC07:01
ttxSo the question is... how much is enough for us to keep them ?07:02
*** ajo has quit IRC07:02
AJaegerright now our proposal script imports new translations when they have at least 70 % translated - and removes them again if they have less than 20 %.07:03
AJaegerlet me check whether Daisy is around...07:03
ttxFrankly, I'm fine with merging anything the translations team is comfortable with, so I'm happy deferring the % thresholds decisions to you all :)07:04
ttxAlthough I'd say that keeping a translation that is only 25% just because it once was in...07:05
ttxsounds counterproductive07:05
AJaegerExactly, I also think it's time for spring cleaning ;)07:05
*** Daisy has joined #openstack-infra07:05
ttxSo I'm fine with raising the low threshold07:05
DaisyHi07:05
ttx70/50 sounds fair07:05
AJaegerHi Daisy, thanks for joining!07:05
Daisy:)07:05
ttxAt 51 a translation still bring marginal value I suspect07:06
ttxDaisy: Hi!07:06
AJaegerttx and myself are currently looking at translated files for server projects - and we exclude Horizon here.07:06
*** asilenkov_ has quit IRC07:06
*** dteselkin has quit IRC07:06
*** rakhmerov has quit IRC07:06
*** asilenkov has quit IRC07:06
*** HeOS_ has quit IRC07:06
*** katyafervent has quit IRC07:06
*** tsufiev has quit IRC07:06
*** asilenkov has joined #openstack-infra07:06
Daisyok.07:06
AJaegerI've run a script over all server projects to check current translation status of files, output is http://paste.openstack.org/show/203412/07:06
openstackgerritJamie Lennox proposed openstack-infra/project-config: Add django-openstack-auth-kerberos project  https://review.openstack.org/17280307:06
ttxOr you keep using 70/20 on the proposal script, but we use.. 66% or something as a release threshold07:07
AJaegerRight now we import new files from transifex once 70 % are translated and propose removing them again once less than 20 % are translated07:07
ttxI don't remember what we used for Juno... 70% ?07:07
*** HeOS_ has joined #openstack-infra07:07
*** katyafervent has joined #openstack-infra07:07
AJaegerDaisy, so, what shall we do for release time now?  Change the proposal bot to go with a higher number and let it remove those? Or do a one-time cleanup?07:07
*** tsufiev has joined #openstack-infra07:07
AJaegerttx, I don't remember, let me check...07:08
Daisy70% means the completion rate of a single resource ? or a language for a project ?07:08
AJaeger70 % of single resource07:08
ttxAJaeger: given we now are on proposed/* branches, it's probably more productive to do one-time cleanups07:08
openstackgerritJamie Lennox proposed openstack-infra/project-config: Add django-openstack-auth-kerberos project  https://review.openstack.org/17280307:09
DaisyAJaeger: you want to do a one-time cleanups ?07:09
ttxsince that lets us merge last-minute updates as well07:09
DaisyI don't have strong opinions to 70% and 20%.  I think, they are acceptable.07:09
AJaegerDaisy, I'm wondering whether a 20 % translated resource has any benefit to users, so would raise this for the release07:10
Daisyok.07:10
AJaegerttx, Daisy : It's 75 % not 70 %07:10
ttxok07:11
AJaegerttx, amotiki is taking care of horizon, so I explictely ignore that one...07:11
AJaegerthere they even go for complete translation AFAIR07:11
*** jamielennox is now known as jamielennox|away07:11
DaisyI think 20% translated resources don't have much benefit.07:11
*** HeOS has joined #openstack-infra07:12
*** rakhmerov has joined #openstack-infra07:12
DaisyEven less than 50% translated resources don't have much benefit. That's my opinion.07:12
AJaegerDaisy, agreed. So, which ones should we delete for the release? Less than 50 % ? Less than 75 %?07:12
ttxYes. For release threshold I'd say 66% is the bare minimum07:12
Daisy:)07:12
AJaeger66 it is ;)07:13
DaisyThere is no specific number.07:13
DaisyI  like 66%07:13
AJaegerttx, so I have to propose patches for the proposed branches only - or also for master?07:13
ttxI think that lats translations that lost a bit of steam (down from 75%) still get in release07:13
ttxlets*07:13
ttxAJaeger: proposed/kilo only07:13
AJaegerttx, agreed, having something less than 75 % is nice07:13
*** dteselkin has joined #openstack-infra07:14
ttxLet's keep partial translations in master07:14
*** ildikov has joined #openstack-infra07:14
AJaegerttx, ok, will do directly...07:14
ttxAJaeger: last time, didn't we also catch up with the latest translations within the same script ?07:14
ttxAJaeger: in which case, it would be idea to run the script and propose the translation release cleanup just before the projects RC2s07:15
ttx(i.e. later this week)07:15
*** juggler has quit IRC07:15
AJaegerttx, let me do one test patch for review and then I'll do it later this week...07:15
ttxIf we don't update any string (and just clean up stale stuff) then now is as good as anytime07:16
*** dizquierdo has joined #openstack-infra07:16
ttxAJaeger: do we already have the script uploaded somewhere ?07:16
ttxAJaeger: if not, feel free to propose it to release-tools07:16
AJaegerThe one for generating the numbers?07:16
AJaegerOr the one for importing?07:16
ttxThe one for importing / cleaning up on proposed branches07:17
AJaegerI don't think it's uploaded - was done manually last time. Let me propose to release-tools...07:17
ttxcool, thx*07:17
*** achanda has quit IRC07:21
*** ihrachyshka has joined #openstack-infra07:22
*** achanda has joined #openstack-infra07:22
*** _nadya_ has quit IRC07:22
*** yamada-h has joined #openstack-infra07:23
*** jistr has joined #openstack-infra07:24
*** yamahata has quit IRC07:24
*** chlong has quit IRC07:25
*** sergsh has joined #openstack-infra07:27
*** yamada-h has quit IRC07:28
*** ihrachyshka has quit IRC07:28
*** ihrachyshka has joined #openstack-infra07:30
*** hashar has joined #openstack-infra07:30
AJaegerone further question:07:31
AJaegerttx and Daisy, what shall we do with projects that have only the po (Source file) but no translations. Should we update that one as well?07:31
*** mrda is now known as mrda-away07:32
AJaegerI meant pot files07:32
DaisyWhich projects ?07:32
DaisyMaybe they don't in Transifex.07:32
AJaegersahara for example has no translations at all (at least none more than 20 % )07:33
*** arxcruz has joined #openstack-infra07:33
AJaegerSo, should we update the pot file in the repository so that it reflects current status? I think we should...07:33
DaisyI think, pot should be included in the project. It's a part of the source codes.07:34
AJaegerThey are included but not updated - so I will update them as part of the import, even for those that have no translations.07:34
Daisyupdate local pot while importing from Transifex ?07:35
AJaegerThat's what we normally do - but if there's nothing to import, we don't update.07:35
Daisyok.07:35
AJaegerSo, my proposed patch will just update the local pot07:35
Daisyok.07:36
Daisyagree.07:36
*** markus_z has quit IRC07:37
*** mpavone has joined #openstack-infra07:37
*** Hal has joined #openstack-infra07:39
*** fhubik has joined #openstack-infra07:40
*** Hal is now known as Guest8332707:40
*** mpaolino has quit IRC07:40
*** woodster_ has quit IRC07:40
*** markus_z has joined #openstack-infra07:41
*** amitgandhinz has joined #openstack-infra07:43
*** jlanoux has joined #openstack-infra07:47
*** MaxV has joined #openstack-infra07:50
*** btully has quit IRC07:54
*** otter768 has joined #openstack-infra07:55
AJaegerttx, Daisy please review https://review.openstack.org/17282407:55
*** jlibosva has joined #openstack-infra07:56
ttxAJaeger: lgtm07:57
DaisyAJaeger: I'm OK with the patch. Just one concern: there is no auto import script ? You have to import one project by one project manually ?07:57
AJaegerttx: Commit message clear as well?07:57
AJaegerDaisy, yes, manually for proposed/kilo07:57
AJaegerThe autoimport only works on master07:57
Daisyoh. OK.07:57
AJaegerBut I have a script for it now ;)07:57
ttxAJaeger: yep07:58
Daisyok.07:58
ttxDaisy: It's a one time thing07:58
Daisyok. got it.07:58
AJaegerttx, so what day shall I do the imports?08:00
*** otter768 has quit IRC08:01
amotokiAJaeger:just /FYI/ I have a script for Horoizon translation import https://github.com/amotoki/horizon-i18n-tools/blob/master/propose-trans.sh   I think you are testing a similar script08:01
ttxAJaeger: that will depend based on project. I'd like to do the import once we open a RC2 window for that project08:01
AJaegerttx, please ping me - and if I do not ack, send an email...08:01
ttxI'd say at first That should happen between Thursday this week and Thursday next week08:01
ttxat first glance*08:01
AJaegeramotoki, yeah...08:03
openstackgerritAndreas Jaeger proposed openstack-infra/release-tools: Add script to cleanup of translations  https://review.openstack.org/17282708:05
AJaegerttx, amotoki, here's ^ my script08:05
AJaegerttx, ok, waiting on Thursday for your first pings ;)08:06
*** sergsh has quit IRC08:07
*** e0ne has joined #openstack-infra08:08
*** e0ne has quit IRC08:10
*** _nadya_ has joined #openstack-infra08:11
*** andreykurilin has joined #openstack-infra08:11
*** dtantsur|afk is now known as dtantsur08:14
*** e0ne has joined #openstack-infra08:14
*** pblaho has joined #openstack-infra08:14
tchaypojeblair: so I’ve just added all the python-*client repos to gertty. The UI freezes for ~10s when adding a new subscription, but aside from that it’s working fine. It’s still slow to process the queue, but the queue is currently sitting at 115 and gradually changing rather than consistently increasing.08:14
openstackgerritAndreas Jaeger proposed openstack-infra/release-tools: Add script to cleanup of translations  https://review.openstack.org/17282708:14
*** ihrachyshka has quit IRC08:15
*** fhubik is now known as fhubik_afk08:16
*** AJaeger has quit IRC08:17
*** sergsh has joined #openstack-infra08:19
*** e0ne has quit IRC08:19
*** fhubik_afk is now known as fhubik08:19
*** achanda has quit IRC08:22
*** notnownikki has joined #openstack-infra08:28
*** fhubik is now known as fhubik_afk08:28
*** pal has quit IRC08:28
*** pal has joined #openstack-infra08:30
*** AJaeger has joined #openstack-infra08:30
openstackgerritFabien Boucher proposed openstack-infra/infra-specs: Specification proposal about system-config testing using containers  https://review.openstack.org/17283308:31
*** derekh has joined #openstack-infra08:32
*** _nadya_ has quit IRC08:32
*** tjones1 has joined #openstack-infra08:34
*** Ala has quit IRC08:34
*** zz_johnthetubagu is now known as johnthetubaguy08:36
*** Ala has joined #openstack-infra08:39
*** fhubik_afk is now known as fhubik08:42
*** Guest83327 has quit IRC08:43
*** Hal has joined #openstack-infra08:43
*** Hal is now known as Guest7603008:44
*** dizquierdo has quit IRC08:46
*** jlanoux has quit IRC08:52
*** pelix has joined #openstack-infra08:53
*** hichihara has quit IRC08:54
*** mwhudson has quit IRC08:54
*** dguitarbite has quit IRC08:56
*** dhritishikhar has quit IRC08:57
*** ssam2 has joined #openstack-infra08:57
*** jlanoux has joined #openstack-infra08:58
*** mwhudson has joined #openstack-infra08:59
*** yamamoto has quit IRC09:01
*** jamielennox|away is now known as jamielennox09:02
*** dguitarbite has joined #openstack-infra09:03
*** ildikov has quit IRC09:04
*** salv-orlando has joined #openstack-infra09:04
*** jlibosva has quit IRC09:05
*** Guest76030 has quit IRC09:07
*** salv-orlando has quit IRC09:07
*** jlibosva has joined #openstack-infra09:07
*** ihrachyshka has joined #openstack-infra09:07
*** btully has joined #openstack-infra09:09
*** belmoreira has joined #openstack-infra09:10
*** aswadr has quit IRC09:14
*** btully has quit IRC09:14
*** andymaier has joined #openstack-infra09:17
*** SotK_ has joined #openstack-infra09:20
*** doude has quit IRC09:21
*** doude has joined #openstack-infra09:22
*** doude has quit IRC09:22
*** doude has joined #openstack-infra09:22
*** sergsh has quit IRC09:23
*** SotK has quit IRC09:24
*** SotK_ is now known as SotK09:25
*** _nadya_ has joined #openstack-infra09:25
*** jlibosva has quit IRC09:32
*** freerunner has joined #openstack-infra09:33
*** sergsh has joined #openstack-infra09:37
*** Daisy has quit IRC09:38
*** ZZelle has quit IRC09:43
*** ZZelle has joined #openstack-infra09:44
*** fhubik is now known as fhubik_afk09:46
openstackgerritRicardo Carrillo Cruz proposed openstack-infra/system-config: Decouple server class from nodepool service class  https://review.openstack.org/17285909:47
*** _1_Nah has joined #openstack-infra09:47
_1_Nahhello09:47
*** fhubik_afk is now known as fhubik09:48
*** _1_Nah has quit IRC09:55
*** e0ne has joined #openstack-infra09:55
*** otter768 has joined #openstack-infra09:56
*** e0ne has quit IRC09:56
*** dizquierdo has joined #openstack-infra09:58
*** markvoelker has joined #openstack-infra09:59
*** otter768 has quit IRC10:01
*** yfried is now known as yfried|afk10:02
openstackgerritBoris Pavlovic proposed openstack-infra/project-config: Move Rally to OpenStack  https://review.openstack.org/17270110:03
*** nithyag_ has joined #openstack-infra10:05
*** nithyag__ has quit IRC10:07
*** isviridov_away has joined #openstack-infra10:09
*** sdake has joined #openstack-infra10:09
*** pal has quit IRC10:10
*** isviridov_away is now known as isviridov10:12
*** amitpp has joined #openstack-infra10:14
*** markvoelker has quit IRC10:16
*** e0ne has joined #openstack-infra10:17
*** cdent has joined #openstack-infra10:18
*** yfried|afk is now known as yfried10:18
*** markvoelker has joined #openstack-infra10:18
*** fhubik has quit IRC10:19
*** tjones1 has left #openstack-infra10:19
*** fhubik has joined #openstack-infra10:20
*** Ala has quit IRC10:21
*** amitpp has quit IRC10:22
*** isviridov is now known as isviridov_away10:23
*** yamada-h has joined #openstack-infra10:25
*** Ala has joined #openstack-infra10:27
*** marcusvrn has joined #openstack-infra10:27
openstackgerritRicardo Carrillo Cruz proposed openstack-infra/system-config: Decouple openstack_project::server from puppetdb class  https://review.openstack.org/17287110:27
*** mrmartin has joined #openstack-infra10:27
*** fhubik_afk has joined #openstack-infra10:27
*** fhubik_afk has joined #openstack-infra10:27
*** fhubik_afk is now known as fhubik_10:27
*** sdake_ has joined #openstack-infra10:28
*** fhubik has quit IRC10:28
*** markvoelker has quit IRC10:29
*** gillllliard is now known as gilliard10:29
*** yamada-h has quit IRC10:30
*** jlibosva has joined #openstack-infra10:30
*** sdake has quit IRC10:31
openstackgerritRicardo Carrillo Cruz proposed openstack-infra/system-config: Decouple openstack_project::server from puppetdb class  https://review.openstack.org/17287110:31
*** e0ne has quit IRC10:35
*** salv-orlando has joined #openstack-infra10:35
*** e0ne has joined #openstack-infra10:37
openstackgerritMerged openstack-infra/storyboard-webclient: Support for tags  https://review.openstack.org/16684710:38
*** fhubik_ is now known as fhubik10:38
*** dimsum_ has joined #openstack-infra10:39
openstackgerritRicardo Carrillo Cruz proposed openstack-infra/system-config: Decouple server class from nodepool service class  https://review.openstack.org/17285910:40
*** e0ne has quit IRC10:41
*** andreykurilin has quit IRC10:43
*** sdake_ has quit IRC10:53
*** teran has joined #openstack-infra10:55
*** mwagner_lap has quit IRC10:57
openstackgerritgaryk proposed openstack-infra/project-config: VMware: add ability to create and manage branches  https://review.openstack.org/17287911:04
*** garyk has joined #openstack-infra11:04
garykAJaeger: hi, are you around?11:04
garykare there cores around? i have a few question about creating branches - https://review.openstack.org/#/c/172879/11:05
openstackgerritMarton Kiss proposed openstack-infra/system-config: Initial commit of ask-staging.o.o site  https://review.openstack.org/17288011:11
*** yfried is now known as yfried|afk11:14
*** koolhead17 has joined #openstack-infra11:14
*** dhritishikhar has joined #openstack-infra11:22
*** yfried|afk is now known as yfried11:22
*** fhubik is now known as fhubik_afk11:25
*** _nadya_ has quit IRC11:26
*** tiswanso has joined #openstack-infra11:31
openstackgerritFabien Boucher proposed openstack-infra/system-config: Allow passing puppetmaster_server param for jenkins manifests  https://review.openstack.org/17048711:32
*** tiswanso has quit IRC11:36
*** yfried is now known as yfried|afk11:40
*** ldnunes has joined #openstack-infra11:40
*** hashar is now known as hasharNap11:41
AJaegergaryk, now I am...11:43
AJaegergaryk, your patch looks fine...11:43
*** yfried|afk is now known as yfried11:44
*** liusheng has quit IRC11:44
kirHi all, have a problem with https://review.openstack.org/#/c/157816/ - no verified -1 inside, but when I look at the list of outgoing reviews - I see V=-1 for this patch. What's wrong?11:45
*** samueldmq has joined #openstack-infra11:45
*** amotoki has quit IRC11:45
*** weshay has joined #openstack-infra11:47
AJaegerkir, where do you see V=-1 ?11:47
*** spredzy is now known as spredzy|afk11:47
*** ttx has quit IRC11:48
*** ttx has joined #openstack-infra11:48
*** ttx has quit IRC11:49
*** ttx has joined #openstack-infra11:49
*** kir_ has joined #openstack-infra11:49
kir_AJaeger: on the list of my outgoing reviews11:50
garykAJaeger: thanks. Would it be possible to add me to the vmware-nsx-release team (not sure who controls that)11:50
openstackgerritMatthieu Huin proposed openstack-infra/infra-specs: Allow reviewstats to be used with any issue tracker  https://review.openstack.org/17288611:50
*** kir has quit IRC11:51
kir_AJaeger: and also here https://review.openstack.org/#/q/owner:kshileev,n,z11:52
AJaegergaryk, you control it yourself, check https://review.openstack.org/#/admin/projects/stackforge/vmware-nsx,access11:52
AJaegerAnd then click on nsx-release team - that'S you, isn't it?11:52
*** dimsum_ has quit IRC11:52
garykAJaeger: thanks.11:52
*** _nadya_ has joined #openstack-infra11:53
AJaegerkir_, that looks strange indeed, seems there's a mismatch. I can't help further, let's wait until infra admins like fungi or clarkb show up and can tell you why 157816 has everything green but your overview not11:53
*** yamamoto has joined #openstack-infra11:55
*** fhubik_afk is now known as fhubik11:57
*** otter768 has joined #openstack-infra11:57
*** andreykurilin has joined #openstack-infra11:58
*** kir__ has joined #openstack-infra11:58
*** kir_ has quit IRC11:58
kir__AJaeger: ok thnks11:58
*** andreykurilin has quit IRC11:59
*** sdake has joined #openstack-infra12:00
*** andreykurilin has joined #openstack-infra12:00
*** kgiusti has joined #openstack-infra12:00
*** sdake_ has joined #openstack-infra12:01
openstackgerritFilip Blaha proposed openstack-infra/project-config: Pylint job for Murano project  https://review.openstack.org/17288712:01
*** mwagner_lap has joined #openstack-infra12:02
*** otter768 has quit IRC12:02
*** sdake has quit IRC12:04
openstackgerritFilip Blaha proposed openstack-infra/project-config: Pylint job for Murano project  https://review.openstack.org/17288712:05
*** yamamoto has quit IRC12:10
*** Ala has quit IRC12:10
*** Ala has joined #openstack-infra12:12
*** jamielennox is now known as jamielennox|away12:12
*** Daisy has joined #openstack-infra12:13
*** hdd has joined #openstack-infra12:15
*** Hal has joined #openstack-infra12:16
*** maurosr is now known as maurosr_12:16
*** Hal is now known as Guest1166812:16
*** dboik has quit IRC12:18
*** EmilienM|afk is now known as EmilienM12:19
*** rfolco has joined #openstack-infra12:19
*** salv-orl_ has joined #openstack-infra12:20
*** zz_jgrimm has quit IRC12:22
*** zz_ja has quit IRC12:22
*** maurosr_ has quit IRC12:22
*** zz_jgrimm has joined #openstack-infra12:24
*** salv-orlando has quit IRC12:24
*** Guest11668 has quit IRC12:24
openstackgerritJaume Devesa proposed openstack-infra/project-config: Use gerrit reference to clone networking-midonet  https://review.openstack.org/17289712:25
*** dtantsur is now known as dtantsur|brb12:25
*** zz_ja has joined #openstack-infra12:25
*** sdake_ has quit IRC12:25
*** sdake has joined #openstack-infra12:25
*** maurosr_ has joined #openstack-infra12:25
*** maurosr_ is now known as maurosr12:26
*** dprince has joined #openstack-infra12:26
*** sdake_ has joined #openstack-infra12:27
openstackgerritMatthieu Huin proposed openstack-infra/infra-specs: Allow reviewstats to be used with any issue tracker  https://review.openstack.org/17288612:28
*** spredzy|afk is now known as spredzy12:28
*** samueldmq_ has joined #openstack-infra12:29
samueldmqhi, do we still need to keep python26 jobs ?12:29
mordredsamueldmq: we're very close to being able to get rid of them12:30
samueldmqmordred, yeah, I was looking at this (https://github.com/openstack-infra/project-config/blob/master/zuul/layout.yaml#L312-L313)12:30
samueldmqmordred, and was wondering if that time already had come :)12:31
*** sdake has quit IRC12:31
*** hdd has quit IRC12:32
*** yamamoto has joined #openstack-infra12:33
AJaegersamueldmq, juno supports python 2.6 - so once it retires, we can remove them12:33
mordredyeah - but - I believe now that juno is cut, we can stop running them on a majority of things12:34
*** BharatK has quit IRC12:34
*** fhubik is now known as fhubik_afk12:35
fungiAJaeger: kir__: i believe it's from citrix xenserver ci which was de-authorized from voting on tempest late last week after it left a -1. it seems that causes its vote to be hidden in the normal review screen but not in the dashboard view12:35
BobBallIs there a nice tool / way that I can remove all -1 votes for the past 2 weeks using the XenServer CI account?12:35
*** rlandy has joined #openstack-infra12:36
AJaegerfungi, so, one way would be to workaround this would be to upload a new change, correct?12:37
*** adalbas has joined #openstack-infra12:37
AJaegerUnless BobBall and you figure out something nicely ;)12:37
AJaegerfungi, thanks!12:37
samueldmqAJaeger, k thanks .. but when J is officially retired ?12:38
fungiBobBall: if it's a new-style account created via openid login, you can manually delete the entries silently from the reviewer table in the webui. it might also be possible to do something similar via the api12:38
*** deepakcs has quit IRC12:38
fungisamueldmq: not yet identified--it'll likely be discussed at the next summit as usual. my guess is ~9 months12:38
BobBallIt's been an account for quite some time now (1.5 years?) so I guess it's not a new style... Shame.12:38
fungicould be as few as 5-6 months i guess12:38
*** amitgandhinz has quit IRC12:39
samueldmqfungi - ah ok, thanks12:39
*** andreykurilin has quit IRC12:39
fungithough it's worth noting, now that we're capping and branching stable versions of all the clients and libraries, we could look at dropping py26 testing from kilo/master of all those12:40
*** Daisy has quit IRC12:40
*** dboik has joined #openstack-infra12:40
*** _nadya_ has quit IRC12:41
*** kmartin has quit IRC12:43
*** fhubik_afk is now known as fhubik12:43
*** ttx has quit IRC12:45
*** ttx has joined #openstack-infra12:45
*** ttx has quit IRC12:46
*** ttx has joined #openstack-infra12:46
mordredfungi: ++12:48
dstufftdown with python 2.612:49
*** eharney has joined #openstack-infra12:50
*** aysyd has joined #openstack-infra12:50
*** jroll has quit IRC12:50
*** jroll has joined #openstack-infra12:50
mordreddstufft: yeah, tell me about it12:51
dstufftalso down with python 2.7, or python 3, either way12:51
dstufftI just want one python again12:51
*** bknudson has quit IRC12:51
*** gordc has joined #openstack-infra12:51
mordredI think that once we can use python3, we should drop support for 2.7 too12:51
mordredbecaue there is no need for both at that point12:51
samueldmqmordred, ++12:52
mordredI mean, other than client libraries12:52
dstufftopenstack would probably become the first thing that's really all in on python3 at that point12:52
dstufftwhich is kinda cool12:52
mordredyah.12:52
dstufftwell the first major thing12:52
*** zz_dimtruck is now known as dimtruck12:52
samueldmqfungi, if we want to do that (dropping py26 testing from kilo/master), how to do so?12:52
*** markvoelker has joined #openstack-infra12:52
samueldmqfungi, removing py26 jobs from all projects on zuul/layout.yaml12:52
samueldmq?12:52
mordredsamueldmq: we'll need to do it with a regex match in the jobs section12:53
mordredsamueldmq: because we still need to run 2.6 on stable/juno12:53
*** dimsum_ has joined #openstack-infra12:53
mordredactually - this might be a job for one of the plugins, yeah fungi ?12:53
samueldmqmordred, hmm, add a regex at python26-jobs (https://github.com/openstack-infra/project-config/blob/master/zuul/layout.yaml#L314-L324)12:54
mordredsamueldmq: http://git.openstack.org/cgit/openstack-infra/project-config/tree/zuul/openstack_functions.py12:54
*** markvoelker_ has joined #openstack-infra12:54
mordredsamueldmq: it's too complex for a simple regex I think12:54
fungimordred: speaking of just using python 3, http://python-future.org/12:54
*** aysyd has quit IRC12:55
AJaegerthere're some stackforge projects that want to have python26 tested on master, like the fuel projects AFAIR, we should not restrict them. We told them they can test basically until Juno end-of-life.12:55
AJaegerBut for OpenStack projects I'm not aware of any special requests12:55
samueldmqmordred, k I will take a look (still getting familiar with this proj) :p12:55
samueldmq(too big)12:55
*** aysyd has joined #openstack-infra12:55
mordredfungi: how is that better/worse than six? any idea?12:55
*** baoli has joined #openstack-infra12:55
fungisamueldmq: basically, we already do that for the api servers. they run their python 3.6 jobs today on stable/icehouse and stable/juno12:56
samueldmqfungi, python 3.6? oO12:56
fungimordred: better in that you write python 3 and this makes it also run on python 2.6/2.7. six tries to introduce support for python back to 2.4 and attempts to provide you with "a way" for your code to run on both 2.x and 3.x12:56
AJaegerfungi, samueldmq indeed, it's only libraries and clients (and yes 3.6->2.6)12:56
mordredfungi: ah - nod12:57
*** _nadya_ has joined #openstack-infra12:57
mordredfungi: I think that's nice12:57
fungisamueldmq: typo. 2.612:57
*** dustins has joined #openstack-infra12:57
samueldmq:)12:57
mordreddhellmann: ^^ have you looked at python-future.org?12:57
fungimordred: their faq also discusses python-future vs six and the pros/cons12:57
*** markvoelker has quit IRC12:58
*** dimsum_ has quit IRC12:58
samueldmqfungi, mordred so basically six code does an if/else to check the python version and then decide the syntax to use ?12:59
*** Krinkle|detached is now known as Krinkle13:00
*** jlibosva has quit IRC13:00
*** openstackgerrit has quit IRC13:00
dstufftsamueldmq: sometimes13:00
*** miqui has joined #openstack-infra13:01
dstufftoften times really13:01
fungiit's more like six wants you to write in a special python dialect that, with it's help, will run on 2.x and 3.x interpreters. futures seems to be geared more toward letting you write plan python 3.3+ and get it to also run on 2.6/2.713:01
mordredfungi: well, I know dhellmann is planning on making a concerted effort towards 3 this cycle13:01
fungis/plan/plain/13:02
*** jlibosva has joined #openstack-infra13:02
*** dkranz has joined #openstack-infra13:02
dstufftI haven't used python-future at all, it does some stuff where it installs different things based on python version, which is a no-go for pip  D:13:02
dstufftI just use six most of the time13:02
*** openstackgerrit has joined #openstack-infra13:03
openstackgerritMatthieu Huin proposed openstack-infra/infra-specs: Allow reviewstats to be used with any issue tracker  https://review.openstack.org/17288613:03
*** krtaylor has quit IRC13:03
*** hasharNap is now known as hashar13:04
*** doug-fish has left #openstack-infra13:04
mordreddstufft: oh gross13:05
dstufftmordred: it more or less dynamically builds up a list of packages (in the import sense) to instal based on py2 or py313:06
*** spzala has joined #openstack-infra13:07
openstackgerritSamuel de Medeiros Queiroz proposed openstack-infra/project-config: Fix typo on the description of check-tripleo job  https://review.openstack.org/17290413:07
samueldmqeasy review (nit fix) ^13:08
mordredsamueldmq: thanks, looks good - however, we don't normally do patches to only fix nits in infra ... too many other patches to deal with13:09
mordredsamueldmq: btw - where in brazil are you?13:09
samueldmqmordred, ah sorry, still not familiar on how things work on infra :)13:10
samueldmqmordred, I am on the Northeast13:10
samueldmqmordred, Campina Grande (City), Paraíba (State)13:10
samueldmqmordred, actually I am part of a team at an university here13:11
*** ricky1 has joined #openstack-infra13:11
mordredsamueldmq: cool! I haven't been to the northeast yet, although a good friend of mine is from Recife and tells me I should visit13:13
mordredsamueldmq: I usually make it down to Sao Paulo about once a year though13:13
samueldmqmordred, so you still dont know the best part of Brazil :)13:14
*** bknudson has joined #openstack-infra13:14
samueldmqmordred, we have amazing beaches on the northeast13:14
*** Hal has joined #openstack-infra13:14
*** isviridov_away is now known as isviridov13:14
*** Hal is now known as Guest9628513:15
*** erlon has joined #openstack-infra13:15
*** ayoung has joined #openstack-infra13:15
*** isviridov is now known as isviridov_away13:16
*** isviridov_away is now known as isviridov13:17
*** dimtruck is now known as zz_dimtruck13:17
*** radez_g0n3 is now known as radez13:18
dhellmannmordred: python-future.org looks interesting, I'll dig into that more13:18
fungiit seems to be _on_ pypi at least, though i haven't tried to pip install and play around with it13:18
*** isviridov is now known as isviridov_away13:19
*** smccully has joined #openstack-infra13:19
fungilooks like they only have sdist tarballs for it, no wheels13:19
*** koolhead17 has quit IRC13:19
dhellmannmordred, fungi, dstufft : there's also https://pypi.python.org/pypi/modernize which I need to look at more13:19
*** isviridov_away is now known as isviridov13:20
dhellmannbut at this point i'm really thinking more about surrounding tools than I am the application code itself (how do we make devstack do the right thing, for example)13:20
ricky1folks, why i keep getting "Could not set 'present' on ensure: Could not locate the pip command" on my puppet agent runs, when the puppet-pip is available as a module on the puppetmaster and that module installs pip package13:20
fungifuture seems to have something called "futurize" which does similar things to modernize13:20
ricky1anyone hit this kind of problem recently?13:20
*** dhritishikhar has quit IRC13:20
ricky1haven't deployed infra servers lately, never had this problem before13:20
*** isviridov is now known as isviridov_away13:21
fungiricky1: doesn't sound familiar, but we use http://git.openstack.org/cgit/openstack-infra/system-config/tree/install_puppet.sh to install puppet, and it preinstalls pip for us before running puppet at all13:22
fungiricky1: so we likely wouldn't run into that upstream13:22
openstackgerritMerged openstack-infra/project-config: Fix typo on the description of check-tripleo job  https://review.openstack.org/17290413:24
ricky1fungi: so the puppet you install on the nodes are from install_puppet, regardless of being a puppetmaster or other services?13:24
ricky1following doc from http://ci.openstack.org/puppet.html#id2 seems outdated then13:24
fungiricky1: yes13:24
fungiricky1: what specifically is out of date there?13:25
ricky1that docs says that a node that will join the puppetmaster you have to install puppet with 'sudo apt-get install puppet'13:26
ricky1but per your statement earlier, it seems you use install_puppet for all ndoes13:26
ricky1puppetmaster and other services13:26
ricky1?13:26
ricky1I mean the 'Adding a node' section13:26
fungiricky1: ahh, yeah the "adding a node" section is probably in need of updating. we don't really perform the steps listed there. we use http://git.openstack.org/cgit/openstack-infra/system-config/tree/launch/README when adding new nodes13:27
ricky1gah13:27
ricky1o-k13:27
ricky1thanks fungi13:27
fungiricky1: what's in that section is an okay general example, but assumes you can work out the missing bits yourself13:28
fungiinstead we've just scripted new server deployments entirely13:28
fungii'll propose an update to that document now13:28
*** peristeri has joined #openstack-infra13:29
openstackgerritJan Provaznik proposed openstack-infra/project-config: Set proper group for for core reviews and release  https://review.openstack.org/17291613:30
*** amitgandhinz has joined #openstack-infra13:30
*** andreykurilin has joined #openstack-infra13:30
mesteryGood morning infra! Question for you: For all the stackforge/networking-* branches, how do we create stable branches to map to kilo? My google-fu is failing me. :)13:31
*** tiswanso has joined #openstack-infra13:32
*** vdo has quit IRC13:32
*** samueldmq_ has quit IRC13:32
*** sks has quit IRC13:32
*** dhritishikhar has joined #openstack-infra13:33
*** woodster_ has joined #openstack-infra13:33
fungimestery: the .*-release teams for those projects should be able to go to, for example, https://review.openstack.org/#/admin/projects/stackforge/networking-odl,branches (substitute the correct repo name as needed) and create them there13:33
mesteryfungi: Thank you! Looking now.13:34
*** baoli has quit IRC13:34
mesteryfungi: So, if I don't see a create buitton there, I must not be in the release team? Fixing that now.13:34
*** amitgandhinz has quit IRC13:34
fungimestery: either that or the acl for that project doesn't have "create" permission on refs/heads/* for that group13:35
mesteryfungi: That must be it! Looking now.13:35
*** kgiusti has quit IRC13:35
ricky1fungi: sure, i'm automating the deploy an infra from scratch, so i'm biting those bits frequently and pushing changes as I find them13:35
openstackgerritMarton Kiss proposed openstack-infra/system-config: Add backup scripts to ask.o.o site  https://review.openstack.org/16926013:36
ricky1fungi: it's ok, i can work on that doc change13:36
ricky1leave it with me13:36
*** baoli has joined #openstack-infra13:37
fungiricky1: okay, i'll discard my commit. have at it13:37
fungiand thanks!13:37
openstackgerritKyle Mestery proposed openstack-infra/project-config: Add create acls for networking-[odl,ovn]  https://review.openstack.org/17291913:37
fungimestery: yep, you'll need that13:38
mesteryfungi: thanks :)13:38
mesteryfungi: IF you have a moment, this one has been sitting for a while too: https://review.openstack.org/#/c/170927/13:39
mesteryfungi: Creates a check job for networking-ovn13:39
fungimestery: yep, lgtm13:40
*** ihrachyshka has quit IRC13:42
*** annegentle has joined #openstack-infra13:44
*** ajo has joined #openstack-infra13:45
*** markvoelker_ has quit IRC13:46
*** mjturek1 has joined #openstack-infra13:46
garykfungi: could you please take a look at https://review.openstack.org/172879 - we would like to be able to create a prosed stable branch to be in sync with neutron...13:47
*** ihrachyshka has joined #openstack-infra13:47
*** mjturek1 has left #openstack-infra13:47
mesteryfungi: cool, thanks!13:48
fungigaryk: yep, that looks right13:48
openstackgerritMerged openstack-infra/project-config: Enable a check job for networking-ovn  https://review.openstack.org/17092713:48
*** Kiall has quit IRC13:50
mrmartiner, fungi: I resolved the merge conflict of ask.o.o backup patch, so need to review from scratch again: https://review.openstack.org/#/c/169260/13:51
*** Kiall has joined #openstack-infra13:51
*** mjturek1 has joined #openstack-infra13:51
*** yamamoto has quit IRC13:51
samueldmqwas that possible to create a kind of meta-infra to run infra changes against it and avoiding changes to break the gate, etc13:53
samueldmqsetting up infra with the change and doing some tests, as infra does for other OpenStack projects13:54
samueldmqfungi ^13:54
*** zz_dimtruck is now known as dimtruck13:54
*** dtantsur|brb is now known as dtantsur13:56
fungisamueldmq: we do a poor pass of that by applying all the classes with --noop since they can't all be co-installed at the moment13:57
*** loquacities has quit IRC13:57
fungisamueldmq: there's been some discussion of trying to do real installs of all the classes as a more thorough integration test, but it's not a trivial problem to solve so progress in that direction will be slow13:57
*** otter768 has joined #openstack-infra13:58
*** sdake has joined #openstack-infra13:59
samueldmqfungi, yeah I see, but challenging and nice to have :)13:59
*** fhubik is now known as fhubik_afk13:59
*** loquacities has joined #openstack-infra13:59
fungisamueldmq: well, there's no shortage of other challenging problems to solve here, so it's a matter of prioritizing them13:59
samueldmqfungi, where can I find them ? is there a specs repo ?14:01
*** ssam2 has quit IRC14:01
samueldmqfungi, openstack-infra/infra-specs :)14:01
*** ssam2 has joined #openstack-infra14:01
fungisamueldmq: http://specs.openstack.org/openstack-infra/infra-specs/ and https://review.openstack.org/#/q/status:open+project:openstack-infra/infra-specs,n,z and https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting14:02
*** superdan is now known as dansmith14:02
*** sdake_ has quit IRC14:02
samueldmqfungi, thanks14:03
*** otter768 has quit IRC14:03
*** shashankhegde has joined #openstack-infra14:04
openstackgerritMatthieu Huin proposed openstack-infra/infra-specs: Allow reviewstats to be used with any issue tracker  https://review.openstack.org/17288614:04
*** dboik_ has joined #openstack-infra14:05
*** sabeen has joined #openstack-infra14:06
*** dboik has quit IRC14:08
*** lascii is now known as alaski14:09
*** jerryz has joined #openstack-infra14:10
*** dimsum_ has joined #openstack-infra14:10
*** unicell1 has joined #openstack-infra14:10
*** unicell has quit IRC14:11
*** ajmiller has joined #openstack-infra14:15
*** sdake_ has joined #openstack-infra14:18
*** mattfarina has joined #openstack-infra14:19
*** krtaylor has joined #openstack-infra14:20
*** fhubik_afk is now known as fhubik14:20
*** sdake has quit IRC14:21
ayoungfungi, what is the definition of rc1-ness for gating purposes?  Does it just assume that all the projects have that tag, and use the tag upon checkout when running check/gate against it?14:23
openstackgerritRicardo Carrillo Cruz proposed openstack-infra/system-config: New nodes should install puppet from install_puppet.sh  https://review.openstack.org/17293614:23
fungiayoung: nah, it's that there's a proposed/kilo branch created on the project14:25
fungiayoung: and then further proposed/kilo changes for that project are integration tested against the proposed/kilo or stable/kilo branches of other projects14:25
fungiayoung: and at that point master of that repo starts working toward liberty14:26
ricky1fungi: ^ doc change per previous conversation14:26
fungiricky1: thanks!14:26
ricky1for some reason i thought that doc was in infra-manual14:26
ayoungfungi, so a RDO needs to do the same thing, just match the branch name on each project?14:26
ricky1and was giving rounds and rounds14:26
ricky1should've checked first obvious thing and look in system-config14:26
fungiricky1: aha, you're rcarrillocruz too14:26
ricky1yes, i'm at my parents'14:26
ricky1rcarrillocruz is my bouncer at my home14:27
*** yamamoto has joined #openstack-infra14:27
fungii need to figure out how to clone myself too. two of me would get so much more work done than one14:27
ricky1hah14:27
openstackgerritMerged openstack-infra/project-config: Add create acls for networking-[odl,ovn]  https://review.openstack.org/17291914:29
*** tiswanso has quit IRC14:29
*** jistr is now known as jistr|mtg14:29
*** dboik_ has quit IRC14:30
openstackgerritMerged openstack-infra/system-config: Add backup scripts to ask.o.o site  https://review.openstack.org/16926014:30
*** dboik has joined #openstack-infra14:30
*** achanda has joined #openstack-infra14:31
*** mrmartin has quit IRC14:31
*** wenlock has joined #openstack-infra14:32
*** wenlock1 has joined #openstack-infra14:33
*** dimsum_ is now known as dims14:39
*** achanda has quit IRC14:41
*** yfried has quit IRC14:42
*** tiswanso has joined #openstack-infra14:42
anteayaI really think there should be a devices-in-public mode that disables _all_ startup/login/ringing sounds, similar to airplane mode14:43
*** tiswanso has quit IRC14:43
*** tiswanso has joined #openstack-infra14:44
*** eantyshev has joined #openstack-infra14:44
*** Longgeek has quit IRC14:45
*** _nadya_ has quit IRC14:45
*** Longgeek has joined #openstack-infra14:46
*** markvoelker has joined #openstack-infra14:47
*** sdake has joined #openstack-infra14:47
*** pkarikh has joined #openstack-infra14:47
*** markvoelker_ has joined #openstack-infra14:48
pkarikhHi folks! Could anyone take a look at this patch, please? It already has one +2. https://review.openstack.org/#/c/171117/14:49
*** rkukura has quit IRC14:50
*** sdake_ has quit IRC14:50
*** yamamoto has quit IRC14:51
*** cference_ has joined #openstack-infra14:51
*** markvoelker has quit IRC14:52
cference_Hi guys, I'm having a server error when I try to update my mailing address on review.openstack.org, anyone have any idea as to why?14:52
*** eantyshev has left #openstack-infra14:52
*** markvoelker has joined #openstack-infra14:52
*** markvoelker_ has quit IRC14:52
anteayacference_: can you share the error? paste.openstack.org14:52
fungicference_: also see https://ask.openstack.org/question/5672014:53
cference_anteaya, http://paste.openstack.org/show/203594/14:53
openstackgerritMerged openstack-infra/project-config: VMware: add ability to create and manage branches  https://review.openstack.org/17287914:54
*** fhubik has quit IRC14:54
anteayacference_: yup, follow fungi's link14:54
anteaya<-- not a guy14:54
*** rwsu has quit IRC14:54
*** rwsu has joined #openstack-infra14:54
*** fhubik has joined #openstack-infra14:55
*** shashankhegde has quit IRC14:55
cference_thanks, I'll try that14:55
*** fhubik_afk has joined #openstack-infra14:55
*** mriedem has joined #openstack-infra14:55
anteayak14:55
*** markvoelker has quit IRC14:58
*** amitgandhinz has joined #openstack-infra14:59
openstackgerritTimur Nurlygayanov proposed openstack-infra/project-config: Add pep8 check for haos project  https://review.openstack.org/17294814:59
*** asselin has joined #openstack-infra14:59
*** mriedem has quit IRC14:59
*** deepakcs has joined #openstack-infra15:00
cference_fungi, anteaya, I wasn't using the correct email between the foundation website and gerrit, thanks for the help!15:00
anteayacference_: ah, glad you found the issue15:01
*** hdd has joined #openstack-infra15:02
*** dboik_ has joined #openstack-infra15:03
*** kmartin has joined #openstack-infra15:03
*** mriedem has joined #openstack-infra15:03
*** dboik has quit IRC15:07
*** stevemar has joined #openstack-infra15:07
*** jistr|mtg is now known as jistr15:07
*** jerryz has quit IRC15:07
*** sdake_ has joined #openstack-infra15:07
*** jlibosva has quit IRC15:10
*** hdd has quit IRC15:10
*** trey has quit IRC15:11
openstackgerritDavid Shrewsbury proposed openstack-infra/shade: Add API method create_subnet()  https://review.openstack.org/17021715:11
*** garyk has quit IRC15:12
*** annegentle has quit IRC15:12
openstackgerritDavid Shrewsbury proposed openstack-infra/shade: Add API method create_subnet()  https://review.openstack.org/17021715:12
*** harlowja_at_home has joined #openstack-infra15:12
*** annegentle has joined #openstack-infra15:13
*** sdake has quit IRC15:13
openstackgerritDavid Shrewsbury proposed openstack-infra/shade: Add API method delete_subnet()  https://review.openstack.org/17047715:14
openstackgerritDavid Shrewsbury proposed openstack-infra/shade: Add API method update_subnet()  https://review.openstack.org/17051615:14
openstackgerritJulia Kreger proposed openstack-infra/shade: Add update_machine method and operator unit test substrate  https://review.openstack.org/17116515:14
*** zz_jgrimm is now known as jgrimm15:15
*** trey has joined #openstack-infra15:16
*** dimtruck is now known as zz_dimtruck15:17
openstackgerritDavid Shrewsbury proposed openstack-infra/shade: Add API method create_subnet()  https://review.openstack.org/17021715:17
openstackgerritDavid Shrewsbury proposed openstack-infra/shade: Add API method delete_subnet()  https://review.openstack.org/17047715:18
*** kgiusti has joined #openstack-infra15:18
*** afazekas has quit IRC15:18
*** koolhead17 has joined #openstack-infra15:18
openstackgerritDavid Shrewsbury proposed openstack-infra/shade: Add API method update_subnet()  https://review.openstack.org/17051615:19
openstackgerritDavid Shrewsbury proposed openstack-infra/shade: Add API method update_subnet()  https://review.openstack.org/17051615:21
*** koolhead17 has quit IRC15:21
openstackgerritDavid Shrewsbury proposed openstack-infra/shade: Add get_subnet() method  https://review.openstack.org/17176015:22
*** dhritishikhar has quit IRC15:22
*** annegentle has quit IRC15:23
*** arxcruz has quit IRC15:24
*** Kiall has quit IRC15:26
*** Kiall has joined #openstack-infra15:26
*** dangers_away is now known as dangers15:27
*** koolhead17 has joined #openstack-infra15:27
*** hashar has quit IRC15:29
*** stevemar has quit IRC15:30
*** dhritishikhar has joined #openstack-infra15:30
*** stevemar has joined #openstack-infra15:30
*** russellb has quit IRC15:30
*** Ala has quit IRC15:30
*** yamahata has joined #openstack-infra15:30
openstackgerritTimur Nurlygayanov proposed openstack-infra/project-config: Add pep8 check for haos project  https://review.openstack.org/17294815:32
*** dizquierdo has quit IRC15:32
*** mtanino has joined #openstack-infra15:32
*** aysyd has quit IRC15:33
*** russellb has joined #openstack-infra15:33
*** ZZelle_ has joined #openstack-infra15:35
*** soren has quit IRC15:35
*** koolhead_ has joined #openstack-infra15:36
*** koolhead17 has quit IRC15:36
*** mjturek1 has left #openstack-infra15:37
*** dannywilson has joined #openstack-infra15:37
openstackgerritRicardo Carrillo Cruz proposed openstack-infra/system-config: New nodes should install puppet from install_puppet.sh  https://review.openstack.org/17293615:37
*** koolhead17 has joined #openstack-infra15:37
*** aysyd has joined #openstack-infra15:37
*** doug-fish has joined #openstack-infra15:40
*** koolhead_ has quit IRC15:40
anteayaasselin_: thanks15:40
anteayafungi: all tied up, thanks for being my backup15:41
*** scheuran has quit IRC15:41
fungianteaya: no worries--glad is worked out!15:41
fungier, it15:41
anteaya:)15:41
*** gyee has joined #openstack-infra15:41
openstackgerritMerged openstack-infra/project-config: Update jobs for Merlin  https://review.openstack.org/17111715:41
*** spredzy is now known as spredzy|afk15:42
*** rkukura has joined #openstack-infra15:42
*** claudiub has joined #openstack-infra15:42
*** dannywilson has quit IRC15:42
*** mdenny has joined #openstack-infra15:43
*** GheRivero_ has quit IRC15:43
*** dannywilson has joined #openstack-infra15:43
*** garyk has joined #openstack-infra15:43
*** jlibosva has joined #openstack-infra15:44
*** jistr has quit IRC15:45
*** asselin has quit IRC15:49
*** yamahata has quit IRC15:49
*** aricg has left #openstack-infra15:51
*** dannywilson has quit IRC15:53
*** markvoelker_ has joined #openstack-infra15:53
cineramahi folks15:54
zaromorning15:55
anteayahi cinerama15:56
anteayamorning zaro15:56
*** ttx has quit IRC15:57
*** ttx has joined #openstack-infra15:57
*** markus_z has quit IRC15:57
*** otter768 has joined #openstack-infra15:59
*** markvoelker_ has quit IRC15:59
mordredmorning cinerama16:00
*** annegentle has joined #openstack-infra16:00
anteayamorning mordred16:00
openstackgerritKhai Do proposed openstack-infra/puppet-gerrit: Update bouncy castle libs for Gerrit 2.10  https://review.openstack.org/17253416:00
*** dboik_ has quit IRC16:01
cineramais there someone who can do Things™ on translate-dev for me?16:01
mordredfungi, clarkb: when you get a chance, eyeballs on 172600 would be helpful - it's getting a bit long and I'd like to land it16:01
mordredanteaya: morning!16:01
fungimordred: sure thing. i could use a break from wrestling with restructuredtext16:02
anteayazaro: how goes the standing up of 2.10? is there hope?16:02
*** dboik has joined #openstack-infra16:02
anteayacinerama: I am unable to do anything on the translate-dev server, sorry16:02
zaroanteaya: looking good.  review-dev.o.o is already running 2.1016:03
*** jlibosva has quit IRC16:03
anteayazaro: nice work16:03
zaroanteaya: it also has the close connection command16:03
mordredfungi: I'll warn you - there are decorators and function attributes16:03
* anteaya goes to check out review-dev16:03
fungii'll live16:03
*** stevemar has quit IRC16:03
anteayazaro: oh yay!16:03
mordredcinerama: what sort of Things do you need?16:03
anteaya\o/16:03
*** otter768 has quit IRC16:03
*** teran_ has joined #openstack-infra16:04
*** stevemar has joined #openstack-infra16:04
*** Swami has joined #openstack-infra16:04
cineramamordred: well, first i need to get https://review.openstack.org/#/c/172578/ landed. then applied. and i may need manual mysql intervention16:04
*** zz_dimtruck is now known as dimtruck16:04
*** jlanoux has quit IRC16:04
zaroanteaya: new screen works well in 2.10 if you want to give it a go16:05
*** ttx has quit IRC16:05
*** ttx has joined #openstack-infra16:05
anteayaohhhh16:05
fungimordred: ooh, that's quite a deep change stack. i'll see how far i get16:05
* anteaya tries new screen16:05
mordredfungi: I recommend a skim-through read first16:05
anteayazaro: it appears to default to new screen16:06
fungiindeed16:06
mordredfungi: it's all essnetially smallish changes to get to a sane state - but reading each out of context may be mind bending16:06
*** sushilkm has joined #openstack-infra16:06
*** sushilkm has left #openstack-infra16:06
*** fhubik_afk has quit IRC16:06
fungistarting from the bottom of the stack, we'll see if it causes me to break for lunch instead ;)16:06
mordredcinerama: landed. let's wait for it apply16:07
zaroanteaya: hmm, the preferences menu says default is the old screen16:07
*** teran has quit IRC16:08
*** tiswanso_ has joined #openstack-infra16:08
zarofungi: ^ would you like to see what you get?16:08
anteayazaro: really? that does not match my experience16:09
zaroanteaya: look in settings->preferences->change view16:09
fungianteaya: i wonder if you'd previously adjusted your preference for your account on review-dev when testing the new change screen at some point in the past?16:09
openstackgerritClark Boylan proposed openstack-infra/devstack-gate: WIP: Make multinode first class with ansible  https://review.openstack.org/17261416:09
*** unicell1 has quit IRC16:09
anteayafungi: worth wondering, it is possible, though unlikely as I don't like the new screen, but I can't say for sure16:10
anteayaas I can't remember the last time I was in settings on review-dev16:10
fungiyeah, my preferences are set to "Server Default (Old Screen)" and i'm also seeing the old change screen when browsing around16:10
*** afazekas has joined #openstack-infra16:10
anteayahowever if your expierence matches, zaro's, then perhaps it is just me16:10
anteayaokay, just me16:10
clarkbdansmith: https://review.openstack.org/172614 runs the multihost setup in parallel16:10
anteayathanks for confirming16:10
anteayahey clarkb16:10
clarkbgood morning16:11
dansmithclarkb: ooh nice16:11
anteayazaro: http://imgur.com/ZTHXR3q16:11
anteayazaro: so I have a question about athe pull option16:11
anteayazaro: should we be looking for a way to disable pull?16:11
anteayaor just leave it?16:11
*** tiswanso has quit IRC16:11
zaroanteaya: why do you think we should disable?16:13
openstackgerritKyle Mestery proposed openstack-infra/project-config: Add neutron-release as branch creation group  https://review.openstack.org/17298216:13
* clarkb points out that 160155 still has unaddressed comments from ps116:13
clarkbmordred: ^16:13
anteayazaro: well pull isn't really in our workflow, will that mess up some devs if they choose to pull?16:14
* anteaya thinks backto draft16:14
zaroanteaya: i do pull all the time :)16:15
clarkbthe potential problem with pull is it does an implicit merge by default16:15
mordredclarkb: yah - I've been ignoring that one until it fixes its merge conflict state16:15
clarkbmordred: ya I am just being cranky that we are trying to push through a giant stack when an ancient change has been ignored instead16:15
openstackgerritMerged openstack-infra/system-config: Add default from address  https://review.openstack.org/17257816:16
mordredanteaya, zaro; I REALLY wish it was possible to configure pull to use --ff-only by default16:16
clarkb(all of which add tests)16:16
anteayaclarkb: yes, thanks that was the issue I was thinking of but couldn't articulate16:16
mordredclarkb: would it help your cranky if I abandoned that change?16:16
openstackgerritMatthew Treinish proposed openstack/os-testr: Add support for having comments in the exclude file  https://review.openstack.org/17298416:16
mordredbecause we've already added create_server unittests in a different patch16:17
anteayazaro: is it possible to configure pull to use --ff-only by default?16:17
*** smccully has quit IRC16:17
clarkbmordred: if it has been superceded then yes we should likely abandon it16:17
mroddeni think you can get it to --rebase by default...16:17
*** smccully has joined #openstack-infra16:17
mordredclarkb: done16:17
anteayamordred: would pull --rebase by default be acceptable for pull?16:18
clarkbthe pull implicit merge is by the way one of the reasons why I think people think git review does a rebase autoamtically even when not necessary16:18
*** Longgeek has quit IRC16:18
anteayaclarkb: oh16:18
clarkbanteaya: mordred ^ and because of that I don't think any side effecting behavior of pull is desirable16:18
*** belmoreira has quit IRC16:18
clarkbrebase vs ff only doesn't matter, it still causes confusion and people yell at us to fix bugs that don't exist16:19
mordredclarkb: yah. agree16:19
anteayaclarkb: what would you like to see? right now we have: http://imgur.com/ZTHXR3q16:19
mordredclarkb: I didn't mean for our docs16:19
mordredI mean that I personally wish I could set that locally16:19
fungiwe should probably make checkout the default option anyway16:19
*** tqtran has joined #openstack-infra16:19
*** ayoung is now known as dreadadminrobert16:19
mordred++16:19
*** dreadadminrobert is now known as ayoung16:19
*** dhritishikhar has quit IRC16:19
*** tiswanso_ has quit IRC16:19
clarkbanteaya: I am a fan of checkout, it is what I use locally16:19
mordredthe two things I do the most are checkout and reset --hard16:20
anteayame too16:20
*** btully has joined #openstack-infra16:20
anteayathe think I'm think is any lever we expose gets used16:20
*** carl_baldwin_ has joined #openstack-infra16:20
*** tiswanso has joined #openstack-infra16:20
mordredyup - which means if we can turn pull off, that's awesome16:20
clarkbyes the other git review trouble maker is git review -x16:20
anteayaso should we try to unexpose the levers we don't want to fix afterthey are used?16:20
mordredI use git review -x CONSTANTLY16:20
*** ricky1 has quit IRC16:20
clarkbmordred: yes but you understand git16:20
mordredclarkb: yup16:20
clarkbmordred: most people odn't understand that you get a new sha1 every time you use it16:21
mordredsigh16:21
mordredwell, I could live without it16:21
clarkbmordred: this results in two problems. 1) gerrit rejects pushes because there are no changes16:21
mtreinishclarkb: wait, really? sigh...16:21
clarkb2) it looks like git review did an implicit rebase for you when reall you just cherry picked rewriting all history yourself16:21
mordredmaybe we should make an expert edition of git review16:21
*** Somay has joined #openstack-infra16:21
anteayaoh great, more levels16:22
*** dboik has quit IRC16:22
mordredbecause clarkb makes a good point - it confuses people ... otoh, it's super helpful if you know what you're doing16:22
zaroyou mean just remove pull from UI right?16:22
mordredzaro: yah16:22
clarkbmordred: also fwiw I never use git review -x16:23
clarkbits usually just as easy/hard to git review -d then rebase16:23
mordredclarkb: sometimes I'm not rebasing16:23
zaroif that's not an option in Gerrit core, then you can probably do the javascript thing after page render16:23
mtreinishI use it all the time, too16:23
clarkbbut ^ comes with the added benefit of git holding my hand16:23
mordredclarkb: this comes back to the thing that we still don't have good support for16:23
mordredclarkb: which is constructing a local repo state from several unrealted upstream changesets16:24
clarkbmordred: sure, and rebase can do that for you16:24
*** Sukhdev has joined #openstack-infra16:24
mordredclarkb: I actually gave up and started using merge in a throwaway branch16:24
fungii use git review -x when i'm adding various commits to add dependency relationships which did not previously exist. i could use git review -d instead and then rebase -i and add pick lines16:24
* anteaya thinks she needs to see clarkb's tutorial16:24
clarkbthe main reason I use rebase is due to conflict handling16:24
clarkbdealing with conflicts when not in a merge/rebase is weird16:24
mordredclarkb: but the dancing I have to do currently to deal with and test the dib-nodepool stuff is BANANAS16:24
*** dannywilson has joined #openstack-infra16:25
*** dannywilson has quit IRC16:25
* anteaya would like to see mordred dancing16:25
clarkbfungi: right you just fetch the refs then rebase onto master and pick sha1s :)16:25
mordredbecasue there are multiple outstanding changes across multiple repos that all need to be present for anything to work16:25
zarohere you can customize that download mneu: https://gerrit.googlesource.com/plugins/download-commands/+doc/master/src/main/resources/Documentation/config.md16:25
fungithe version of git i use makes merge conflict resolution effectively the same for cherry-pick as for merge or rebase. i don't really see a difference where that's concerned16:25
clarkbfungi: which is effectivel the same work as git review -x sha116:25
*** dannywilson has joined #openstack-infra16:25
clarkbfungi: a cherry pick is an all or nothing state, its not a stack like a rebease16:26
krotscheckCan some infra cores go through the storyboard specifications and start weighing in? Some of these date from January.16:26
clarkbthe end resutls are the same but rebase has a few more tools16:26
*** hdd has joined #openstack-infra16:26
fungithere's an incomplete cherry-pick state. you fix and add your conflict resolution, then --continue16:26
fungiseems basically the same to me16:26
*** vhoward has left #openstack-infra16:26
anteayazaro: nice, so removing pull is easy16:26
mordredfungi: git add /git commit - not continue - but yes - I also do not find it confusing16:26
clarkbfungi: hrm is that new? I don't think git that was in precise had that16:26
*** dboik has joined #openstack-infra16:26
anteayazaro: what is format patch?16:27
zaroyep. just a gerrit.config setting16:27
clarkbfungi: it was either commit or reset --hard16:27
harlowja_at_homecould i get some folks to look @ https://review.openstack.org/#/c/171393/ + dependents that add tests (a release would be cool to) so that i can merge some other code that needs to be able to shutdown that thread for testing....16:27
fungimordred: huh... i use git cherry-pick --continue all the time16:27
mordredfungi: REALLY? neat16:27
zaroanteaya: no idea, never used that command16:28
openstackgerritMerged openstack-infra/shade: Add tests for caching  https://review.openstack.org/17179816:28
clarkbhrm I must be thinking of stash not cherry pick16:28
anteayazaro: me ethier, any objection to removing that too? we can add it bak if we need it16:28
mordredzaro, anteaya: I believe we also do not want format-patch16:28
mordredit's somethign people use for email-based workflows16:28
anteayamordred: oh good16:29
zaroanteaya: i think this is it https://git-scm.herokuapp.com/docs/git-format-patch16:29
anteayaah16:29
mordredwe also probably don't want "repo download"16:29
*** MaxV has quit IRC16:29
fungiclarkb: yeah, stash/stash pop is definitely a little stranger16:29
mordredconflicts on stash pop are fun16:29
* anteaya is being forced by the train people to eat lunch now16:29
*** afazekas has quit IRC16:30
*** tiswanso has quit IRC16:30
zaroanteaya: i don't see 'repo download'16:31
*** baoli has quit IRC16:31
*** tiswanso_ has joined #openstack-infra16:32
andreafgerrit question: if I hit +A by mistake in gerrit, and it triggers gate, will it still merge even if I removed the +A? Or do I have to -A or -2?16:32
mordredzaro:16:32
andreafhttps://review.openstack.org/#/c/146535 ^^^16:32
mordred  scheme = repo_download16:32
clarkbandreaf: it will merge if tests pass and it has a +2 code review +1 workflow and no -2s16:32
clarkbandreaf: so if you remove your +1 workflow and there are no other +1 workflows it will not merge16:32
andreafok, so dropping the +1 on workflow is enough16:33
andreafclarkb: thanks16:33
*** baoli_ has joined #openstack-infra16:33
*** pblaho has quit IRC16:33
*** sandywalsh has quit IRC16:34
zaroandreaf: i see, that's already off by default16:34
*** dougwig has quit IRC16:35
*** hogepodge has quit IRC16:35
*** sandywalsh has joined #openstack-infra16:35
*** dougwig has joined #openstack-infra16:35
*** sergsh has quit IRC16:36
*** patrickeast has joined #openstack-infra16:37
*** MaxV has joined #openstack-infra16:37
clarkbdansmith: btw live migration tests seem to fail in a tempest check. mtreinish looked at it briefly on friday and saw something in the nova compute log that he thought might be related16:39
*** aysyd has quit IRC16:39
dansmithclarkb: okay, all of them or just some of them?16:39
clarkbdansmith: it seems to be consistent16:40
clarkbdansmith: let me get you a link to the logs16:40
dansmithokay16:40
*** sputnik13 has joined #openstack-infra16:40
clarkbdansmith: http://logs.openstack.org/14/172614/13/experimental/check-tempest-dsvm-aiopcpu-full/599095f/console.html#_2015-04-11_19_32_43_33916:40
*** bknudson has quit IRC16:40
*** dhritishikhar has joined #openstack-infra16:41
*** subscope_ has joined #openstack-infra16:41
dansmithclarkb: ah, yeah, the console log failure16:42
dansmithhmm16:42
*** dannywilson has quit IRC16:42
*** aysyd has joined #openstack-infra16:42
*** koolhead17 has quit IRC16:43
*** unicell has joined #openstack-infra16:43
*** Guest96285 has quit IRC16:43
*** mpavone has quit IRC16:44
*** devvesa has quit IRC16:45
zaroanybody know anything about mime-type?  like why would Gerrit recognize 'text/x-yaml' but not 'text/yaml' ?16:46
*** unicell has quit IRC16:46
*** unicell has joined #openstack-infra16:46
*** harlowja_at_home has quit IRC16:46
anteayazaro: I do not know the answer to your question16:46
*** kgiusti has quit IRC16:47
openstackgerritAmaury Medeiros proposed openstack-infra/release-tools: Use fill method to simplify string wrapping  https://review.openstack.org/17299316:47
sdaguezaro: text/yaml might not have an IANNL registration - http://www.iana.org/assignments/media-types/media-types.xhtml16:47
anteayazaro: the 'Open All' button appears to open all the separate files in the patch in new tabs, is this the expected behaviour?16:48
*** ricky1 has joined #openstack-infra16:49
zaroanteaya: yeah, it's a bad featuer16:49
anteayaagreed, as long is it isn't a bug16:50
zaroit should be open all files in one page -> single page review16:50
anteayayes, that would be a good feature16:50
zarosdague: thanks16:50
*** shashankhegde has joined #openstack-infra16:50
mordredzaro: someone has been working on that recently, yeah?16:50
mordredzaro: I thought I saw you reviewing their patches at one point16:50
openstackgerritMerged openstack-infra/shade: Refactor caching to allow per-method invalidate  https://review.openstack.org/17145616:50
*** ivar-lazzaro has joined #openstack-infra16:51
anteaya'Toggle CI' button is working as expected for me16:51
zaromordred: yeah, it was me but it died because old screen got ripped out.16:51
mordredsigh16:52
mordredwow, I'm SO GLAD effort was put towards old screen and not towards single-page-diff16:52
anteayain expanding comments, I see one button 'Expand All', which becomes 'Collapse All' when expanded16:52
*** ricky1 has quit IRC16:52
mordreds/old/new/16:52
anteayaI'm not seeing a 'Expand Recent' button or feature16:52
*** afazekas has joined #openstack-infra16:53
reedcan I please get a review of this request for a mailing list for coordination of internships? https://review.openstack.org/#/c/167458/16:54
*** tonytan4ever has joined #openstack-infra16:55
* anteaya wonders if this should be one of the things she cares about or doesn't care about anymore16:55
anteayareferencing 16745816:56
*** vhoward has joined #openstack-infra16:57
reedanteaya, it's mainly for GSoC and Outreachy at this moment, for mentors and administrators to coordinate16:57
*** derekh has quit IRC16:57
*** yamahata has joined #openstack-infra16:57
*** dtantsur is now known as dtantsur|afk16:57
anteayayeah I see that16:58
*** dimtruck is now known as zz_dimtruck17:00
*** armax has joined #openstack-infra17:00
*** HeOS has quit IRC17:00
openstackgerritMerged openstack-infra/storyboard: Add tools to run integration tests  https://review.openstack.org/15597517:00
*** ihrachyshka has quit IRC17:00
*** dustins has quit IRC17:01
*** dkranz has quit IRC17:01
*** dustins has joined #openstack-infra17:02
*** Somay has quit IRC17:02
*** marun has joined #openstack-infra17:03
clarkbspeaking of internships, I need to finish prep for my capstone thing17:03
*** BharatK has joined #openstack-infra17:03
clarkbgreghaynes: ^ maybe work on that tomorrow?17:03
*** flaper87 has quit IRC17:03
BharatKHi, Please suggest me the way to skip tempest test cases through job definition17:04
BharatKI want to skip "test_volume_boot_pattern" test cases17:04
anteayaBharatK: I suggest you have a chat with cinder folks about skipping tests17:05
anteayaBharatK: they may have some opinions about it17:05
anteayaand if they do, it is a good idea if you know what they are17:05
*** andymaier has quit IRC17:06
BharatKanteaya: Actuall I sent a patch https://review.openstack.org/#/c/172841/17:06
anteayaBharatK: well #openstack-qa is the channel tempest developers are present in17:06
*** marun has quit IRC17:06
BharatKanteaya: Okay I will ask there thanks.17:06
anteayaBharatK: if you want to discuss your above patch, that is a good place to chat17:06
anteayawelcome17:07
*** imcsk8 is now known as imcsk8|afk17:07
*** subscope_ has quit IRC17:08
*** sputnik13 has quit IRC17:08
*** AJaeger_ has joined #openstack-infra17:08
*** dhritishikhar_ has joined #openstack-infra17:08
*** afazekas has quit IRC17:09
*** dhritishikhar has quit IRC17:09
zaromordred: hadn't realized that gerrit doesn't support  syntax highlighting for puppet :(17:09
*** annegentle has quit IRC17:10
SpamapSbummer17:10
openstackgerritMerged openstack-infra/shade: Allow passing config into shade.openstack_cloud  https://review.openstack.org/17185717:10
SpamapSsyntax highlighting is like A/C for me. Can I live without it? Yes. Will I be happy? NO.17:11
greghaynesclarkb: ++17:11
SpamapS(Air conditioning, not alternating current, though same words apply)17:11
yolandamordred, do you have a sec? i have a pair of points to raise with you17:12
*** BobBall is now known as BobBall_AWOL17:12
yolanda1. my mentee will start working likely on https://review.openstack.org/155305 , is that fine?17:12
yolandanot a spec with +A , but with general approval17:12
*** ssam2 has quit IRC17:13
yolanda2. that needs some attention: https://review.openstack.org/17078817:13
*** ibiris is now known as ibiris_away17:13
med_"mentee" like it.17:13
med_never seen it used before, albeit real word.17:14
med_(yes, yolanda has a better command of English than I do.)17:14
yolandawell, i used google translate for that17:14
yolanda:)17:14
yolandanice to see you around, med, how are things? :)17:16
med_very well, thanks yolanda. And you?17:16
*** flaper87 has joined #openstack-infra17:16
*** tonytan4ever has quit IRC17:16
yolandanice, quite busy all time, but i love the things i'm involved on17:17
med_xlnt.17:17
*** fesp has joined #openstack-infra17:18
mordredyolanda: looking17:18
*** achanda has joined #openstack-infra17:18
*** MaxV has quit IRC17:18
*** davideagnello has joined #openstack-infra17:18
*** MaxV has joined #openstack-infra17:19
mordredyolanda: yes - that is a good thing- although keep in mind it might be something that wants to be added to shade and exposed in a sane way to nodepool17:19
mordredyolanda: or it might be pure nodepool17:19
mordred*waves hands*17:19
mordredhi med_ !17:19
yolandamordred, well, it should be moved to shade, yes17:19
yolandaah, code changes faster than specs17:19
yolandaso i shall rewrite some bits of that before she starts putting hands on it17:20
mordredyolanda: maybe a good idea?17:20
* med_ nods at mordred whom he barely knows17:20
yolandayes, it is :)17:20
*** fesp has quit IRC17:21
mordredyolanda: for the second one - I think jeblair wanted to wait on landing that for a bit and see how it works for you locally in gozer land ... but we should wait for him to get back online17:21
*** deepakcs_ has joined #openstack-infra17:21
yolandaah man, mordred, so you want that we land this in Gozer prior to upstream?  :)17:21
yolandai kept that running on my nodepool account for 2 days, but on a testing account17:22
*** deepakcs has quit IRC17:22
*** deepakcs_ is now known as deepakcs17:22
*** dkranz has joined #openstack-infra17:23
yolandawhen is jeblair coming back?17:23
*** dhritishikhar_ has quit IRC17:23
*** MaxV has quit IRC17:23
*** hogepodge has joined #openstack-infra17:23
anteayayolanda: when he lands I expect17:23
*** deepakcs has quit IRC17:24
*** tonytan4ever has joined #openstack-infra17:24
yolandai'd like to have his opinion prior to testing in Gozer really, makes sense to wait a bit17:25
openstackgerritStuart McLaren proposed openstack-infra/project-config: Stop running gate-tempest-dsvm-neutron-src-python-glanceclient-juno  https://review.openstack.org/17299917:25
*** adalbas has quit IRC17:25
anteayayolanda: I wouldn't be surprised to see him in a few hours, if not then probably tomorrow17:26
yolandai won't be online for much longer today, but i'd lke to catch up with him tomorrow17:26
*** jcoufal has quit IRC17:26
openstackgerritStuart McLaren proposed openstack-infra/project-config: Stop running gate-tempest-dsvm-neutron-src-python-glanceclient-juno  https://review.openstack.org/17299917:27
*** crainte has joined #openstack-infra17:27
openstackgerritMerged openstack-infra/shade: Test volume list caching  https://review.openstack.org/17258617:27
openstackgerritClark Boylan proposed openstack-infra/devstack-gate: WIP: Make multinode first class with ansible  https://review.openstack.org/17261417:27
*** dizquierdo has joined #openstack-infra17:27
fungiSpamapS: did you have a rebuttal for Shrews's concern on https://review.openstack.org/172587 ?17:27
Shrewsfungi: it's all good. i understand it now17:28
fungik17:28
*** SumitNaiksatam has joined #openstack-infra17:28
anteayayolanda: yeah, I don't see that waiting will get you much, better trying tomorrow17:28
fungiShrews: aha, you had already re-commented. i'm slow ;)17:29
kragnizsome reviews on https://review.openstack.org/172999 would be nice17:31
kragnizglanceclient gate currently borked17:31
*** baoli_ has quit IRC17:32
*** afazekas has joined #openstack-infra17:34
SpamapSfungi: it's not that you're slow, it's just that we're _so damn fast_ ;)17:36
*** johnthetubaguy is now known as zz_johnthetubagu17:36
*** tiswanso_ has quit IRC17:36
fungiyes. yes you are17:37
*** harlowja_away is now known as harlowja17:37
*** baoli_ has joined #openstack-infra17:37
*** tiswanso_ has joined #openstack-infra17:37
bswartzhello infra!17:40
bswartzI just realized that there is no manila-stable-maint team in gerrit17:40
fungibswartz: does it need one? do you (expect to) have separate people doing stable maint for manila?17:41
bswartzwho should I be talking to about setting one up?17:41
bswartzfungi: well no17:41
bswartzideally the stable branch would be managed by the same core team17:41
*** dboik has quit IRC17:41
bswartzwith help from the stable-maint core team17:42
fungibswartz: that's what it looks like your acl allows currently17:42
bswartzoh, excellent17:42
bswartzIn the past I've had problems +2ing stuff to the stable/juno branch17:42
*** dboik has joined #openstack-infra17:42
fungibswartz: have you tried in the past couple months since we decentralized control over stable branches?17:42
anteayahttp://git.openstack.org/cgit/openstack-infra/project-config/tree/gerrit/acls/openstack/manila.config17:42
bswartzfungi: no17:42
fungii think you should be fine now, but if not let me know what's missing17:43
bswartzokay this looks like an improvement then since last I checked17:43
bswartzthanks17:43
fungiyep. moar tent17:43
fungis/tent/yurt/17:43
* fungi keeps forgetting17:43
*** tonytan_brb has joined #openstack-infra17:43
anteayais it yurt now?17:43
* anteaya updates17:44
bswartzdo yurts scale better than tents?17:44
fungieverywhere except at the circus17:45
*** tonytan4ever has quit IRC17:45
*** marun has joined #openstack-infra17:45
*** teran_ has quit IRC17:45
*** teran has joined #openstack-infra17:45
*** dhritishikhar_ has joined #openstack-infra17:47
anteayathe hard part with the yurt is building the stabilizing circle for the roof17:47
anteayathe wall are easy17:47
anteayawalls17:47
*** bknudson has joined #openstack-infra17:48
*** BharatK has quit IRC17:49
*** r-daneel has joined #openstack-infra17:51
*** aysyd has quit IRC17:51
openstackgerritMerged openstack-infra/shade: Unsteady state in volume list should prevent cache  https://review.openstack.org/17258717:52
*** dizquierdo has quit IRC17:52
*** zz_dimtruck is now known as dimtruck17:52
*** dizquierdo has joined #openstack-infra17:52
*** aysyd has joined #openstack-infra17:53
openstackgerritClint 'SpamapS' Byrum proposed openstack-infra/shade: Add test for invalidation after delete  https://review.openstack.org/17260017:54
*** dboik_ has joined #openstack-infra17:55
*** markvoelker has joined #openstack-infra17:56
*** afazekas has quit IRC17:57
mgagne_I have a change with a -1 but no reviewer/CI with -1 in the reviewer list: https://review.openstack.org/#/c/171847/ can someone look into it?17:58
*** mgagne_ is now known as mgagne17:58
*** dboik has quit IRC17:58
openstackgerritJeremy Stanley proposed openstack-infra/reviewstats: Sync infra projects to governance repo list  https://review.openstack.org/17302117:59
*** vinkman has left #openstack-infra17:59
*** annegentle has joined #openstack-infra17:59
*** otter768 has joined #openstack-infra18:00
*** pelix has quit IRC18:00
*** markvoelker has quit IRC18:01
zaromgagne: are you seeing -1 from rest request?18:01
mgagnezaro: I haven't debugged at this level =)18:02
zaromgagne: where are you seeing the -1? i don't see it18:03
fungimgagne: there was probably a verify -1 vote from a third-party ci which was later disabled from voting on that repo's changes, which causes the vote to no longer appear in the reviewers table of the change view but potentially leaves it in the dashboard list view18:03
*** otter768 has quit IRC18:05
mgagnefungi: how can this be fixed? my concern is that my change will now NOT be reviewed due to people filtering out changes with -1, all because a CI was voting -1 due to unrelated problems.18:05
mgagnefungi: getting something reviewed in Nova in a timely fashion is hard enough, now a defective CI made it even harder18:05
AJaeger_mgagne: upload a new version, e.g. update the commit message18:05
mgagneAJaeger_: this shouldn't be the solution, shall I not asked here, I would have waited forever for a review18:06
*** SumitNaiksatam has quit IRC18:07
fungimgagne: agreed. reviewers should not be skipping patches just because some random ci has left a -1 verify vote. if they do, it's that behavior which should be fixed18:07
*** dangers is now known as dangers_away18:07
*** yfried has joined #openstack-infra18:07
mgagnefungi: if a CI is disabled, can their votes be removed?18:07
*** dangers_away is now known as dangers18:07
*** dangers is now known as dangers_away18:08
fungimgagne: not without the operators of that ci doing it themselves, or having a gerrit administrator spend time doing it manually (or using some tool which afaik does not yet exist)18:09
mgagnefungi: afaik, each project can disable a CI in a self-service way so I'm not sure if votes can programmatically be removed at the same time18:09
fungizaro: is that ^ something someone has written for gerrit? (a tool which can delete votes when an account is removed from a group which would not have permitted them to leave that vote?)18:10
mgagnefungi: right. IMO, this should somehow be fixed as it leaves a very bad experience for the change owner18:10
clarkbso fwiw this is a bug in gerrit18:10
fungimgagne: sounds like a great feature request, i agree https://code.google.com/p/gerrit/issues/list18:10
clarkbgerrit does attempt to remove the votes automagically18:10
clarkbit just fails at doing it properly18:10
fungiwell, it attempts to hide them. it doesn't actually remove them from the database18:11
*** dboik_ has quit IRC18:11
fungiif the account's permissions are restored, any votes those permissions would have allowed them to leave will reappear18:11
clarkbsure, but more importantly it doesn't take them into account for merge calculations18:11
mgagneit sure does a great job at hiding them but still showing them in the review list18:11
fungiexactly. that part is definitely a gerrit bug18:11
mgagnethere, I rebased...18:12
zarofungi, mgagne : there's a change pending to remove reviewer votes: https://gerrit-review.googlesource.com/#/c/62410/18:13
*** sabeen has quit IRC18:13
mkj_wkI see that there was discussion of dropping py26 testing -- would git-review be a special case, since the "py26" test is also testing that it works with git 1.7?18:13
fungimkj_wk: we would probably keep that job around for as long as we keep centos6 as a job runner platform. that job is less a py26 test specifically, and more of a "does this work for centos/rhel 6.x test18:14
mkj_wkexactly18:14
*** sushilkm has joined #openstack-infra18:14
mkj_wkgood to hear, even though the py26 job was the one that gave me the most grief :)18:14
*** sushilkm has left #openstack-infra18:14
mkj_wk(for that exact reason)18:15
fungimkj_wk: the py26 dropping discussion was around libraries/clients which we were previously only releasing on their master branch but are now growing stable branches corresponding to our integrated release cycles18:15
fungifor those we can _potentially_ stop running py26 jobs on branches where py26 is no longer relevant for other projects18:16
mkj_wkyeah, just wanted to make sure git-review didn't suffer from a template change18:16
mkj_wkmakes perfect sense18:16
fungithough that's still iffy for the clients themselves i think, and perhaps any of our libraries that those clients use18:16
fungidepends on whether we want to continue confirming that people can run latest python-novaclient on rhel/centos 6.x machines for example18:17
clarkba redhat employee specifically writing using the non employee perspective said we should all stop making py2.6 work fwiw18:18
clarkbI think its fine to say git-review 1.x is the last release supporting py2.6 and stop testing py2.6 today18:18
fungirhel/centos 7.x are a thing and have been for a while, after all18:18
clarkbthen release 2.0 next release18:18
fungiwhich reminds me, we're overdue for another git-review release probably18:18
*** sputnik13 has joined #openstack-infra18:19
mkj_wkfungi: I'm just hoping my patch is integrated first :)18:19
mkj_wkfungi: folks here would like it18:19
mkj_wkmost usage here is on py3 I think18:19
*** cdent has quit IRC18:20
fungimkj_wk: yep, after some pretty rigorous manual testing that change seems to work fine for me (e.g. not break our cross-branch and cross-repo change-id duplicate workflows)18:21
*** tlbr has quit IRC18:22
*** HeOS has joined #openstack-infra18:22
*** Sukhdev has quit IRC18:23
*** kgiusti has joined #openstack-infra18:23
*** teran has quit IRC18:24
*** AJaeger_ has quit IRC18:25
*** coolsvap|afk is now known as coolsvap18:26
*** aysyd has quit IRC18:28
*** aysyd has joined #openstack-infra18:28
*** isviridov has joined #openstack-infra18:28
*** ajmiller_ has joined #openstack-infra18:29
*** MaxV has joined #openstack-infra18:29
mkj_wkmordred: if you are satisfied, a +2 on https://review.openstack.org/#/c/158877/ probably won't hurt.  (I'm counting your rebasing on top of it as at least a small vote of confidence... ☺)18:31
*** isviridov has quit IRC18:31
*** SlickNik has quit IRC18:31
*** SumitNaiksatam has joined #openstack-infra18:31
*** SlickNik has joined #openstack-infra18:31
mordredmkj_wk: done!18:31
*** isviridov_away is now known as isviridov18:32
mkj_wkmordred: thanks! Do I need to do anything in the workflow to cause it to be merged?18:32
*** annegentle has quit IRC18:33
*** ajmiller has quit IRC18:33
mordredfungi: you good with me +Aing it?18:33
fungimordred: yep18:33
*** MaxV has quit IRC18:33
mordrednow I just have to get around to finsihing off my push-url patch18:35
*** coolsvap is now known as coolsvap|afk18:36
*** tonytan_brb is now known as tonytan4ever18:36
mkj_wk18:37
*** tqtran has quit IRC18:38
openstackgerritClark Boylan proposed openstack-infra/devstack-gate: Make multinode first class with ansible  https://review.openstack.org/17261418:38
*** tqtran has joined #openstack-infra18:38
clarkbfungi: sdague jeblair mordred et al ^ should be ready for review now18:38
*** dizquierdo has quit IRC18:38
openstackgerritJeremy Stanley proposed openstack-infra/project-config: Update gerritbot #openstack-infra from governance  https://review.openstack.org/17303218:38
clarkbthe best part is it removes more code than it adds :)18:39
fungiclarkb: that's neat18:39
fungiwhat sort of speedup are you getting there?18:40
clarkbfungi: for the aiopcpu jobs is ~25 minutes18:40
clarkbmaybe a little less than that18:40
*** dboik has joined #openstack-infra18:40
fungithat helps. how long does that get them down to now?18:40
clarkbfungi: its the same as non aiopcpu, ~40 minuts18:40
*** armax has quit IRC18:40
fungiahh, okay18:41
funginot bad!18:41
clarkbya it has worked surprisingly well18:41
clarkbalso, it resulted in some general d-g refactoring that I like, will probably do that if we decide not to ansible18:42
*** ashleighfarnham has joined #openstack-infra18:42
*** armax has joined #openstack-infra18:42
clarkbthe big open question is whether or not openstack itself can handle being set up in parallel. Looks like the n-net job can, but I haven't confirmed that neutron can18:42
clarkbBUT if openstack can't I think we merge the changes then go fix openstack18:42
openstackgerritMerged openstack-infra/git-review: Choose tracked branch for rebase when submitting  https://review.openstack.org/15887718:43
mordredclarkb: yeah - we can definitely make that a playbook or more playbook-like - but I agree, for right now just ansible commands in the shell script is the right choice18:43
*** dprince has quit IRC18:43
clarkbmordred: I have a few concerns so far with going more ansible like.18:43
clarkbmordred: the first is control flow. I think it works better in shell like this18:44
clarkbmordred: the second is ansible file manipulation is actually pretty :(18:44
clarkbmordred: you can't fetch a dir recursively for example, or reliably chown a dir recursively18:44
mordredclarkb: yah.18:44
clarkbmordred: or update a file by appending to it18:44
mordredclarkb: I agree18:44
mordredclarkb: this is why I've been happy about teh ansible/puppet split18:44
anteayaclarkb: you can update a file by appending to it18:45
mordredclarkb: ansible is not any cleaner than puppet once you get into config-management complexity sthings18:45
clarkbanteaya: how?18:45
anteayaor maybe not, this just ensures a line is in the file: http://docs.ansible.com/lineinfile_module.html18:45
rcarrillocruzinsertafter EOF18:46
rcarrillocruziirc18:46
clarkbrcarrillocruz: anteaya ya thats just a single line at a time18:46
clarkbwhat I want is to say take file X from src and append it to dest18:46
clarkbyou can kinda do that with a template though18:47
fungiclarkb: nibalizer: did you have follow-up guidance for mrmartin on your comments in https://review.openstack.org/171600 ?18:47
anteayathe syncronize modules uses rsync under the hood18:47
rcarrillocruzhttp://docs.ansible.com/assemble_module.html ?18:47
clarkbfungi: mrmartin just copy the file?18:47
anteayaif you have a src file somewhere you can sync it to a dest18:47
clarkbrcarrillocruz: assemble is broken too18:47
rcarrillocruzuse command: cat :P18:48
clarkbrcarrillocruz: because you have to have all the sourec files in one dir, and aiui you can't specify order18:48
clarkbrcarrillocruz: yes thats what I am saying, there is a lot of stuff that has to stay in bash18:48
rcarrillocruzyes18:48
mordredclarkb: you know, another thing we may want to play with is that ansible modules don't ahve to be in python - they can also be in shell or whatever18:48
*** tkelsey has joined #openstack-infra18:48
rcarrillocruzlineinfile is o-k for some stuff18:48
mordredclarkb: and ansible will handle copying them over and running them in that context18:48
rcarrillocruzi usually resort to templates18:48
greghaynesmordred: downside to that is youll have to mess with jq or something similar18:49
clarkbanyways if anyone wants to fix the related todays in my change feel free to push followup changes18:49
mordredgreghaynes: only if you need to handle input params18:49
clarkbI think you will find that using bash is the simplest thing for many of them18:49
* anteaya has to disembark the train soon18:49
mordredclarkb: I'm not sure it's the right choice for anything - but it might be worth us making a synthetic example of using that mechanism so that we understand it18:49
mordredclarkb: ++18:49
mordredI think using bash for shell scripting is a great choice18:49
greghaynesheh18:49
clarkbmy biggest gripe is I can't fetch a dir18:49
greghaynesclarkb: synchronize?18:49
mordredand it we can use ansible help us stich that stuff together for cross-host execution in a m ore sane manner, sweet18:50
clarkbgreghaynes: I think thats only ansible host -> rmote18:50
clarkbgreghaynes: I need remote -> ansible host18:50
greghaynesI dont think so, its supposed to be all manner of direction18:50
* clarkb goes to read more docs then18:50
greghaynesthers a param to reverse direction IIRC18:50
rcarrillocruzmy biggest gripe so far is the ssh agent forwarding with sudo18:51
clarkbgreghaynes: gah its the dumbest param name ever "mode"18:51
rcarrillocruzyou have to do some hackery to make it work18:51
greghaynesclarkb: haha, I was just scanning the docs thinking "I could have sworn there was one..."18:51
greghaynesso yes, name fail18:51
nibalizerfungi: looking18:51
clarkbgreghaynes: thanks, i can use that18:51
*** dhritishikhar_ has quit IRC18:52
fungiclarkb: yeah, not sure whether you and nibalizer and mrmartin are talking past each other or not on that change. i'll dig into what the corresponding part of the solr module is doing to make that file available in the first place18:52
clarkbfungi: the problem is mrmartins change does not work18:52
clarkbfungi: so not sure why it is controversial to -118:52
clarkbwe need to do something else, my suggestion is just a suggestion18:52
fungiafter another reread of the commit message i think i see what he's trying to do. i'll see if i can test an alternative18:54
*** adalbas has joined #openstack-infra18:54
nibalizerfungi: cool that would be great18:56
*** dannywilson has joined #openstack-infra18:57
fungiwondering if it can just have the require on that file resource changed to the solr module (assuming it properly makes that source file present once it does all its things)18:57
*** sayalilunkad has joined #openstack-infra18:57
*** hockeynut_ has quit IRC18:57
*** Rockyg has joined #openstack-infra18:58
*** hockeynut has joined #openstack-infra18:58
*** hashar has joined #openstack-infra18:59
*** dprince has joined #openstack-infra18:59
clarkbmordred: oh the other ansible problem is environment18:59
*** dboik has quit IRC19:00
clarkbmordred: using the env in ansible is clunky at best. Probbaly not an issue once we zuulv3 since zuul can just pass in a json blob19:00
openstackgerritDavid Shrewsbury proposed openstack-infra/shade: Add get_subnet() method  https://review.openstack.org/17176019:00
*** ajmiller_ has quit IRC19:00
clarkbbut until we get there this practice of -m shell -a "source foo.sh && run thing executable=bash" is actually probably the simplest way to pass env around19:00
clarkbalso the choice of /bin/sh as the shell executable is :(19:01
mordredclarkb: yah - passing env around from calling context is not really the intended mode of operation19:01
*** Hal has joined #openstack-infra19:02
clarkbmordred: which is unfortunate because this is the second time I have wanted it19:02
clarkbmordred: which makes me think either I am crazy or ansible is neglecting an important use case19:02
mordredclarkb: I think taht's because you need wanting to avoid writing things in python19:02
*** Hal is now known as Guest9781219:02
mordredclarkb: I think it's doing what it's doing very much on purpose19:02
mordredand not on accident19:02
rcarrillocruzis it a known issue gate-infra-puppet-apply-precise test failing on exim upstart?19:02
clarkbmordred: I do not agree, writing python has little to do with this19:02
clarkbmordred: we want to execute shell on a remote host. Shells have environments19:03
*** shashankhegde has quit IRC19:03
clarkbansible should be aware of that19:03
mordredno - it should very much not19:03
rcarrillocruzi keep on getting that error despite rechecks on https://review.openstack.org/#/c/172871/19:03
mordredansible is a tool for doing remote exec, it should NOT randomly pass the environment of the calling host to the remote host19:03
mordredthat would be bonghits crazy in almost every case19:03
clarkbmordred: I don't want it to be random19:03
clarkbmordred: but there should be a method to do t19:04
*** mrunge has quit IRC19:04
clarkbmordred: one simple way is how puppet/facter do it. Prefix with FACTER_19:04
clarkbmordred: anything with that prefix is essentially passed through19:04
*** e0ne has joined #openstack-infra19:04
mordredright - but the thing is that you're inventing a new way of doing complex action that is different from their method of complex action19:04
clarkbmordred: but their method of complex action for shells is terrible19:05
mordredinstead of using the mechanism they have of chaining sets of actions together19:05
clarkbmordred: because it ignores the environment19:05
mordrednope19:05
mordredthat's why I mentioned python19:05
clarkbrcarrillocruz: I do not think that is the error19:05
*** sayalilunkad has quit IRC19:06
*** patrickeast_ has joined #openstack-infra19:06
rcarrillocruzhmm19:06
clarkbrcarrillocruz: http://logs.openstack.org/71/172871/2/check/gate-infra-puppet-apply-precise/110b99d/console.html#_2015-04-13_11_27_30_171 I think that is the error19:06
rcarrillocruzfirst errors are puppet modules related19:06
*** patrickeast has quit IRC19:06
*** patrickeast_ is now known as patrickeast19:06
clarkbmordred: so to do anything with shell involving the env you think I as a user should write python?19:06
fungircarrillocruz: http://logs.openstack.org/71/172871/2/check/gate-infra-puppet-apply-precise/110b99d/console.html#_2015-04-13_11_27_30_17119:06
fungier, yep i agree with clarkb19:06
rcarrillocruzbleh19:07
*** ajmiller has joined #openstack-infra19:07
rcarrillocruzis it normal to have those upstart errors tho?19:07
rcarrillocruzkind of annoying to find a needle in a haystack19:07
fungircarrillocruz: the exim errors are because this is running in --noop and puppet is complaining that it can't restart things19:07
clarkbrcarrillocruz: yes, its running in noop mode so those init scripts don't make it onto the machine19:07
rcarrillocruzk, good to know19:07
rcarrillocruzthanks a bunch !19:07
clarkbmordred: anyways, I think that any execution tool for unix running remote or not should have some env awareness19:08
clarkbmordred: because that is how processes on unix work19:08
*** baoli_ has quit IRC19:09
bknudsonmaybe this has been dealt with before? somebody has a pull request in github so somebody else proposes it to openstack? is that legal?19:09
clarkbthey have an argv and and env and 3 sockets opened for them19:09
fungircarrillocruz: my guess is removing the instantiation of openstack_project::server in puppetdb.pp is causing your issue19:09
clarkbs/sockets/file descriptors/19:09
clarkbbknudson: the answer is it depends19:09
fungiit's legal murky water19:10
bknudsonseems like it.19:10
clarkbbknudson: whether or not its derivative, whether or not the submitter might actually own the code, whether or not the submitter has signed a CLA just submitted to the wrong place, etc all play into it19:10
fungigenerally we try to encourage them to agree to the icla and propose the change themselves, or at least agree to the icla and let someone else propose the change19:10
bswartzfungi: there might be a problem with manila acls19:10
bswartzhttp://git.openstack.org/cgit/openstack-infra/project-config/tree/gerrit/acls/openstack/manila.config19:11
bswartzI see no mention of the proposed branch19:11
bswartzjust stable19:11
fungibswartz: did you create a branch?19:11
mordredclarkb: no - I think to do complex stuff you probably want to write python, and when you write complex things in python you probably want to parameterize it so that you can pass parameters in that make sense19:11
bswartzttx created like an hour ago19:11
fungibswartz: are you unable to do things on it? unspecified branches just inherit from refs/heads/*19:11
mordredclarkb:  I think right now we're using it as a form of ssh, whcih is fine - but ssh doesn't pass invoking env do remote subprocesses19:11
bswartzno I haven't tried yet -- if it inherits then I foresee no issues19:12
clarkbmordred: actually :) I think it does19:12
bswartzjust trying to avoid a fire drill if a backport should become necessary19:12
clarkbmordred: in some capacity, that is where the silly bash vulnerability from a while back got crazy19:12
*** patrickeast has quit IRC19:12
clarkbor maybe the network exposure was not via ssh? I thought ssh was involved19:13
fungibswartz: usually the only reason to have a separate refs/heads/proposed/* section in the acl is if you're going to have a manila-milestone group with exclusive permissions on it19:13
bswartzI'll just test it to make sure19:13
mordredmordred@camelot:~$ ssh scylla.inaugust.com 'echo $DBUS_SESSION_BUS_ADDRESS'19:13
mordredthat is empty19:13
mordredbecause ssh does not pass my local environment to the remote hose19:13
mordredhost19:13
mordredI mean- I know what you want to do19:13
clarkbmordred: ah its configurable19:13
mordredbut I thin you're trying to get one tool to seamlessly work with another tool when you're using one of them only halfway19:14
clarkbmordred: you need to PermitUserEnvironment sshd side then client side select which to pass through19:14
mordredyah19:14
clarkbmordred: and really something like ^ is all I ask ansible to do19:14
mordredand if you select which things to pass through19:14
*** e0ne has quit IRC19:14
mordredit HAS that19:14
clarkbmordred: HOW?19:14
mordredit's call passing parameters to a module19:14
fungibswartz: for that matter the refs/heads/stable/* section in there is redundant now that it's been redelegated to manila-core. if that section were omitted it would just inherit the same things from refs/heads/* now that we no longer have a refs/heads/stable/* in the All-Projects global acl with exclusive group permissions for the stable branch managers19:14
clarkbmordred: but how do they get into the module from the remote side?19:14
mordredyou pass them in as parameters at the invoking side19:15
mordredand they are passed over the module invocation interface19:15
clarkbmordred: but how do I get the info from the remote side?19:15
mordredwhat?19:15
clarkbmordred: I need the env on $HOSTOVERTHERE19:15
clarkbmordred: but I am runnin ansible of localhost19:15
mordredyou want to read the env of HOSTOVERTHERE19:16
clarkbmordred: yes19:16
mordredthat's easy19:16
mordredall of yoru scripts are running on that host19:16
mordredso, they can just read the envionment19:16
clarkbmordred: right so my current workaround is to do that19:16
clarkbmordred: but its clunky19:16
mordredof course its clunky19:16
mordredyou're not really using the tool the way it's designed19:16
mordredso one might assume some clunk :)19:16
clarkbI guess I don't understand how its designed if not to remotely run code19:17
clarkbremotely run code needs an env19:17
mordredit's not designed to do complex actions through ad-hoc command line invocations19:17
clarkbbecause processes on unix have environments19:17
mordredwait - can you describe your problem again19:17
*** e0ne has joined #openstack-infra19:17
mordredI think I'm COMPLETELY missing what's bothering you19:17
mordredyou have host and target, and each has an env, host-env and target-env19:18
mordredwhat is where that you are missing from where?19:18
clarkbmordred: the problem is that I want ansible to be aware of remote execution environments when it runs. So that I don't have to do -m shell -a "source foo.sh && do something executable=bash""19:18
mordredclarkb: what's in foo.sh and why is it there?19:18
clarkbmordred: I want to do -m command -a "do stuff env=somehowdescribeenv"19:18
clarkbmordred: that is what defines the remote env19:18
mordredclarkb: what created the contents of it?19:18
clarkbmordred: in this case devstack-gate19:18
mordredright19:19
mordredso - this is what I was saying earlier19:19
mordredyou have a set of parameters in d-g on tehe host side19:19
mordredand you want to get some of those to -a "do stuff"19:19
clarkbmordred: its not just host side19:19
clarkbmordred: its host and remote side both19:19
mordredyou have two different environments and you want to mix them19:19
clarkbyes19:19
*** marun has quit IRC19:20
mordredhow do you expect ansible to know which env vars to pass from host to target?19:20
clarkbeven the puppet method of FACTER_ prefixed env vars would work just fine19:20
*** marun has joined #openstack-infra19:20
mordredyou could do that just fine19:20
mordredbut I'm really trying to undersatnd specifically what you want because it makes no sense to me and I want it to19:20
mordredthen I can help suggest how to do it - or a patch to upstream :)19:21
clarkbmordred: I want to avoid the shell module for two reasons, its less secure and harder to reason about as a result and its only useful if I override the shell executable to be bash19:21
*** coolsvap|afk is now known as coolsvap19:21
clarkbmordred: instead I should be able to use the command module, except that unix commands needs environments to operate properly and ansible fails at this19:21
mordredAH19:21
mordredso - you want to not run things in a subshell, but you also want for unix environments to work19:22
clarkbyes19:22
mordredI think literally no tool is ever going to do that for you transparently - but I will work on a follow up patch to yoru patch for a sake-of-argument maybe-this-is-closer-to-what-you-want19:22
mordredI believe I grok the thing you want now19:23
clarkbit doesn't need to be transparent19:23
mordredsure19:23
mordredno - I get it19:23
mordredlet me take some code stabs19:23
clarkbif I can say pass through all of the DEVSTACK_GATE vars from host to remote and read remote env X19:23
clarkbthat would work fine19:23
*** carl_baldwin_ has quit IRC19:24
clarkbmordred: you will notice that I have decided to do all variable interpolation on the local ansible machine19:24
clarkbmordred: this is an incomplete attempt at making the use of shell not super terrible19:25
clarkbits not properly escaping everything so could be used to do weirdness on the remote side19:25
clarkbbut at least it should be logged properly on the localhost side that its doing so before it does that19:25
clarkbwe will not be able to do ^ that in zuulv319:26
clarkbzuulv3 will need remote resolution of environment to work sanely19:27
*** sabeen has joined #openstack-infra19:27
*** sabeen has quit IRC19:27
*** dboik has joined #openstack-infra19:28
*** Sukhdev has joined #openstack-infra19:28
clarkbor we can not use command and instead use shell whenever we need to construct an environment19:29
mordredI believe that is what you need to do19:29
mordredcommand explicitly does not construct an environment19:30
openstackgerritKhai Do proposed openstack-infra/system-config: update Gerrit javamelody plugin on review-dev.o.o  https://review.openstack.org/17305019:30
sdagueclarkb: so, stack.sh in parallel is not recommended19:31
*** soren has joined #openstack-infra19:31
sdaguereed: https://review.openstack.org/#/c/172614/1619:31
clarkbsdague: can you expand on that?19:31
clarkbsdague: because stack.sh shouldn't care19:31
sdaguewell, it means you can get a nova-compute up on a node before rabbit is working, for instance19:32
mordredclarkb: but I'll hack up some options that hopefully suck less19:32
clarkbsdague: yes, that is the case, but nova compute handles that fine19:32
sdaguesome times19:32
*** kmartin has quit IRC19:33
sdagueit means the service check in for nova compute on boot isn't going to happen, which might mean goofiness with the scheduler19:33
sdagueanyway, there are a lot of potential gotchas here19:33
*** xyang1 has joined #openstack-infra19:33
fungiclarkb: nibalizer: so after playing around some more with 171600 i see the problem. the source for that file is short-lived, and puppet expects it to stick around. we want to make sure the file is copied to where the application expects it if it doesn't exist yet, but not bank on the source of the file sticking around forever19:33
clarkbsdague: would it be better to run in parallel and cut 20 minutes off these jobs and fix the problems as we find them or run in serial and be made at devstack for being so slow?19:33
fungiclarkb: nibalizer: and we don't control the module which has chosen /tmp as the place to unpact that file19:34
clarkbsdague: /me is trying to figure out where I should best focus my energy19:34
fungier, unpack19:34
sdagueclarkb: subnode setup is 20 minutes?19:34
clarkbsdague: yes19:34
sdaguecan you point me to that fact?19:34
clarkbsdague: its about 5 minutes for workspace setup and 15 for devstack19:34
openstackgerritKhai Do proposed openstack-infra/system-config: update Gerrit javamelody plugin on review.o.o  https://review.openstack.org/17305219:34
clarkbsdague: ya I can get logs to compare19:35
fungiclarkb: nibalizer: i suppose an alternative is to manually fix it up by copying that source file back so that puppet stops complaining, and then disable the tmpreaper on the server or at least whitelist the directory where solr unpacks itself?19:35
sdaguelike logs, because total devstack setup is about 15 minutes, but 4 of that is keystone starting and making accounts19:35
*** hdd has quit IRC19:35
sdaguewhich is no way should be in the subnode19:35
sdagueI did look at that, especially around the osc overhead (see ML post this morning)19:35
clarkbsdague: http://logs.openstack.org/65/172465/2/check/check-tempest-dsvm-aiopcpu-full/6f4611e/console.html thats a serial run19:36
clarkbtook ~61 minutes19:37
clarkbsdague: http://logs.openstack.org/14/172614/13/experimental/check-tempest-dsvm-aiopcpu-full/599095f/console.html parallel run took ~43 minutes19:37
sdagueclarkb: right, subnode stack.sh is 3 minutes - http://logs.openstack.org/65/172465/2/check/check-tempest-dsvm-aiopcpu-full/6f4611e//logs/10.209.67.74-subnode/devstacklog.txt.gz19:38
clarkbhrm how is the parallel run so much faster then?19:39
*** teran has joined #openstack-infra19:39
clarkbwe only save ~5 minutes in host setup and workspace setup19:40
clarkb~3 minutes from stack.sh so thats a total of 8 minutes. Currently about 10 minutes short19:40
*** bradjones has quit IRC19:40
clarkblooks like the normal stack.sh on the serial run took almost 4 minutes longer19:41
clarkbso that may just be skew19:41
clarkbsdague: also can you explain "the service check in for nova compute on boot isn't going to happen"19:41
sdagueclarkb: tempest took an extra 5 minutes in the longer one (all of tempest ran slower it looks like), not sure wwy19:41
*** flashgordon has quit IRC19:42
clarkbwe don't reboot any of these nodes, so no sure what boot time checks we would be making19:43
sdaguenova compute does a lot of things in init that assume the rest of the services are up. There is a reason we start the nova services in a specific order19:43
*** isviridov is now known as isviridov_away19:43
clarkbsdague: and we don't consider that a bug with nova? we have to restart all computes if the controller node is rebooted?19:44
clarkbanyways new patch coming shortly that splits out stack.sh runs19:44
sdaguethe restart case is different, because some of this is first time data initialization in the database19:44
*** emagana has joined #openstack-infra19:46
*** shashankhegde has joined #openstack-infra19:47
openstackgerritClark Boylan proposed openstack-infra/devstack-gate: Make multinode first class with ansible  https://review.openstack.org/17261419:47
openstackgerritDoug Hellmann proposed openstack-infra/project-config: Add python3 jobs to oslo.messaging  https://review.openstack.org/17305619:47
*** dboik has quit IRC19:48
*** cdent has joined #openstack-infra19:48
*** coolsvap is now known as coolsvap|afk19:48
sdagueit also eventually heals on the periodic jobs, but eventually might not be good enough here. So I'd rather play it a little safe here, especially as the time cost is only 3 minutes.19:49
clarkbsdague: fwiw I think openstack services like nova compute, neutron l3, neutron agent, etc, basically anything expected to run off controller should be able to come up without distress before the controller19:49
sdagueclarkb: they can, it doesn't mean they'll be in the cluster19:50
clarkbright, openstack should fix that19:50
sdaguelike I said, it heals eventually in periodic19:50
sdagueit's eventually consistent, which is fine for most cases19:50
clarkbmaybe sighup to reconnect to cluster19:51
sdagueit really is kind of an edge case though, it's like saying "you should totally be able to start api servers with no db"19:52
fungidhellmann: does https://review.openstack.org/173056 mean that the bug with oslo.messaging unit tests on the python 3.4 in ubuntu trusty is no longer a problem?19:53
*** sdake has joined #openstack-infra19:53
clarkbsdague: I don't think its an edge case, losing your control plane is something that happens frequently19:53
sdagueit's not about losing the control plane19:54
*** patrickeast has joined #openstack-infra19:54
sdagueit's about it never existing19:54
clarkbsdague: ok, I guess I still don't understand then19:54
sdaguenova-compute comes up19:54
clarkbsdague: these are not effectively the same issue? either its not there or it is there19:54
*** kmartin has joined #openstack-infra19:54
clarkband whether or not it previously existed shouldn't affect that19:55
sdagueso... what's the mechanism for a nova-compute to tell the cluster it exists?19:55
clarkbsdague: rabbit19:55
sdaguebefore that19:55
sdaguewhen does nova-compute tell the world it exists?19:55
sdaguewhat event causes that to happen19:55
clarkbsdague: when it comes up, then it tries again on a poll and hopefully on a sighup19:55
nibalizerfungi: so i think the real solution is to use this: https://github.com/nanliu/puppet-archive#resources19:56
sdaguewell, the answer is, when it boots, and on a periodic cycle19:56
nibalizerthat puppet extension allows you to say 'put this file here, but get it out of a tarball from $HTTP_URL'19:56
clarkbsdague: sure so that seems fine19:56
*** sdake_ has quit IRC19:56
nibalizernow honestly, i've not had time to bang on this particular issue and we'd have to patch heavily the upstream solr module, or roll our own19:56
*** achanda has quit IRC19:57
funginibalizer: use it where? the module which is retrieving and extracting that tarball is one we didn't write19:57
mordrednibalizer: isn't there a puppet module that's being used in the storyboard modules to do a similar thing?19:57
*** coolsvap has joined #openstack-infra19:57
sdaguebut the "when it boots" doesn't just hang until there is an answer, it tries, and moves on figuring it can be consistent later (IIRC)19:57
funginibalizer: though i guess we could guess at the location where it stashes the tarball (if it keeps it somewhere better than /tmp hopefully?) and then reextract it to get that file out even though we don't need it because we already have it in the right destination19:57
sdagueso my concern is you end up trying to do test work in the gate between booting/ failing to declare itself, and the first periodic checkin after19:58
clarkbsdague: right which is why I suggest a sighup19:58
clarkb(or similar mechanism)19:58
sdagueok, well that's code that doesn't exist today19:58
clarkbbecuse we hopefully aren't the only people that want to make sure their cluster synchronizes after a reboot19:58
openstackgerritKhai Do proposed openstack-infra/puppet-gerrit: Update bouncy castle libs for Gerrit 2.10  https://review.openstack.org/17253419:59
openstackgerritKhai Do proposed openstack-infra/puppet-gerrit: Update bouncy castle libs for Gerrit 2.10  https://review.openstack.org/17253419:59
sdagueclarkb: it does after a reboot, because nova-compute ran init_host again19:59
nibalizermordred: there is 'example42/puppi' in the metadata.json19:59
*** annegentle has joined #openstack-infra19:59
nibalizeri dont see it actually used though19:59
nibalizeri try to stay far far away from anything example42 writes19:59
sdagueit's about the record ever existing in the first place19:59
clarkbsdague: but only if you reboot the compute side19:59
sdagueclarkb: no no no no no20:00
nibalizerfungi: yea we'd have to send that patch upstream, and they may or may not be amenable to that20:00
clarkbsdague: then how does compute side know to recheck back in outside of poll interval otherwise?20:00
sdagueclarkb: it doesn't, and it's not important20:00
openstackgerritTimo Tijhof proposed openstack-infra/zuul: Status: Don't raise "abort" as error to the user  https://review.openstack.org/17224120:00
clarkbsdague: ok then I am missing what the problem is still20:00
sdaguebecause it registered itself into the nova service list once20:00
*** dboik has joined #openstack-infra20:01
sdagueso the scheduler will account for it assuming it's up20:01
*** otter768 has joined #openstack-infra20:01
dhellmannfungi: oh, no, it means I forgot about that. :-/20:01
sdagueand if it finds out later it's down, then it will mark it down until the compute tells it it's back up20:01
funginibalizer: well, part of the trick is i think that we're wanting something out of the tarball which that other puppet module isn't installing. better would be to just upstream a patch to add an option to tell it to install that additional file from its tarball20:01
sdaguebut you are starting from a blank world20:01
nibalizerfungi: yes if the tarball is stored in a permament location we could do what you're saying20:01
nibalizerfungi: well 'better'20:01
clarkbsdague: but blank state is effectively down too20:01
nibalizercertainly the patch you describe would be easier to land20:02
dhellmannfungi: well, it worked here on my box, too. Is there some relatively easy way to reproduce that failure?20:02
clarkbsdague: so in both cases you just need something that tells nova to say "I'm up"20:02
*** Guest97812 has quit IRC20:02
fungidhellmann: i can try to 'tox -e py27' in a recent checkout on an up to date ubuntu trusty vm20:02
nibalizerbut i've been here before with puppet + tarballs + wget + execs and it never gets better it just grows in complexity until its unmanagable/super racy and you throw it in the trash20:02
sdagueyep, and it's called starting the nova service ... or waiting 10 minutes20:02
clarkbsdague: it only waits 10 seconds fwiw20:02
dhellmannfungi: ok, I did that on my dev box but it may not be up to date20:02
dhellmannfungi: I'll be more explicit20:02
clarkboh hrm wait20:02
sdagueclarkb: I was pretty sure we tuned that down20:03
clarkbsdague: so nova does two polls, the rabbit poll is every 5 seconds. The conductor poll is every 10 seconds then it does a backoff20:03
clarkbthats not confusing at all :/20:03
*** cdent has quit IRC20:03
sdagueclarkb: yeh, but neither of those is actually the thing20:03
fungidhellmann: it's bug 136790720:03
openstackbug 1367907 in python3.4 (Ubuntu Trusty) "Segfault in gc with cyclic trash" [Undecided,Triaged] https://launchpad.net/bugs/136790720:03
mordrednibalizer, fungi: AFS20:04
clarkbsdague: according to the logs that is what kicks off the config portion of nova compute20:04
dhellmannfungi: thanks20:04
clarkbsdague: once it can check in with conductor the service starts running20:04
sdagueclarkb: ok, if it polls forever, that's probably fine. I didnt' realize it did that20:04
clarkbsdague: then once config is read in it does the registration you are worried about20:04
sdagueI thought we stopped after some period of time20:05
dhellmannwho is the gerrit acl file expert? I have a question about configuring the oslo acls to allow core teams to be the same as stable teams without maintaining separate groups in gerrit20:05
fungidhellmann: deleting the refs/heads/stable/* section from your acls ought to do it20:05
*** imcsk8|afk is now known as imcsk820:05
clarkbsdague: I am looking at http://logs.openstack.org/14/172614/13/experimental/check-tempest-dsvm-aiopcpu-full/599095f/logs/10.209.0.151-subnode/screen-n-cpu.txt.gz fwiw20:05
dhellmannfungi: excellent, that's much easier than what I was doing :-)20:05
*** otter768 has quit IRC20:05
fungidhellmann: alternatively you could have those separate teams just include the core team and the stable maint team20:06
fungidhellmann: that is if you want openstack stable maint to also be pitching in as core reviewers on those20:06
sdagueclarkb: ok, I didn't realize we'd block until then20:07
sdagueI thought it gave up at some point20:07
dhellmannfungi: oh, hrm, that's a fair point20:07
*** e0ne has quit IRC20:08
dhellmannfungi: right now we just have oslo-stable-maint with one or two exceptions, I think20:08
fungidhellmann: we could also tweak it so that the refs/heads/stable/* section doesn't have an exclusiveGroupPermissions line, and then add the stable maint team in place of the core team there, and let it be additive to what it inherits from refs/heads/*20:08
clarkbsdague: anyways its only 3 minutes. I am happy to use the latest patchset which always brings up controller first then subnodes. Then later we can worry about correctness of removing that 3 minute cost20:08
sdagueclarkb: ok, cool20:08
*** dannywilson has quit IRC20:08
clarkbit does do all subnodes in parallel so that if we run on >2 nodes we see a cost savings20:09
openstackgerritMichael Krotscheck proposed openstack-infra/puppet-storyboard: Cron configuration renamed to [scheduler]  https://review.openstack.org/17306320:09
openstackgerritMichael Krotscheck proposed openstack-infra/puppet-storyboard: Enabled Cron Token Scheduler  https://review.openstack.org/17306420:09
sdagueyeh, subnodes in parallel makes total sense to me20:09
*** annegentle has quit IRC20:10
sdagueI'm also a little concerned that even though it functionally recovers, it leaves all those errors (which are correct errors) which are going to mask out them showing up in actual failures20:10
dhellmannfungi: and the stable maint team is "stable-maint"?20:10
dhellmannno, stable-maint-core20:11
fungidhellmann: yep, the latter https://review.openstack.org/#/admin/groups/530,members20:11
dhellmannfungi: ok, that sounds like what I want then, I'll do that. Thanks!20:11
*** asettle is now known as asettle-gym20:11
*** hdd has joined #openstack-infra20:13
dhellmannfungi: haypo pointed out that my py3 patch was a dupe of https://review.openstack.org/#/c/172221/20:13
*** tlbr has joined #openstack-infra20:14
fungidhellmann: aha, excellent, and it also links to the change to make it work20:15
fungii'll manually confirm it since i've held a machine for that purpose anyway20:15
clarkbvivid has 3.4.3 in it, how do we find out if trusty is going to get that?20:15
fungiclarkb: we rattle cages at canonical again apparently20:16
fungidhellmann: even without https://review.openstack.org/172135 i'm no longer getting a failure for tox -e py34 on a held bare-trusty worker now20:17
fungiso something else may have caused that bug to go back into hiding20:17
mtreinishclarkb: ooh 3.4.3, finally the same version my boxes default too20:19
dhellmannfungi: yay? :-)20:22
fungidhellmann: i'm retrying a few more times just to be sure, but seems that way20:23
dhellmannfungi: excellent20:24
fungiworrisome. the bugs that hide are much more aggravating that those which dangle right in front of you20:25
fungioh, neat, seems there's a race in mox though20:25
*** achanda has joined #openstack-infra20:25
*** ftersin has joined #openstack-infra20:28
mordredclarkb: wendar was going to poke doko at pycon about 3.4.320:29
mordredclarkb: or at least about unbreaking 3.420:29
*** dizquierdo has joined #openstack-infra20:31
*** yfried is now known as yfried|afk20:32
*** jgrimm is now known as zz_jgrimm20:33
*** HenryG has quit IRC20:33
*** kmartin has quit IRC20:34
*** dkranz has quit IRC20:35
*** yfried|afk is now known as yfried20:37
*** HenryG has joined #openstack-infra20:37
openstackgerritDoug Hellmann proposed openstack-infra/project-config: Use Oslo core teams for stable maint, too  https://review.openstack.org/17307520:38
*** baoli has joined #openstack-infra20:38
dhellmannfungi: I wanted to include some comments in ^^ but I can't find any examples of a comment syntax in acl files.20:38
*** hdd has quit IRC20:38
openstackgerritJulia Kreger proposed openstack-infra/shade: Add update_machine method and operator unit test substrate  https://review.openstack.org/17116520:41
openstackgerritJulia Kreger proposed openstack-infra/shade: Update register_machine to use tasks  https://review.openstack.org/17132420:41
openstackgerritJulia Kreger proposed openstack-infra/shade: Update unregister_machine to use tasks  https://review.openstack.org/17132520:41
*** e0ne has joined #openstack-infra20:41
*** radez is now known as radez_g0n320:41
*** nbernard has joined #openstack-infra20:42
*** baoli_ has joined #openstack-infra20:45
*** unicell has quit IRC20:45
clarkbmordred: yay!20:45
*** peristeri has quit IRC20:46
*** yfried is now known as yfried|afk20:47
*** dkranz has joined #openstack-infra20:47
*** baoli has quit IRC20:47
wendarmordred: we've got a debian python bof with doko tomorrow at sprints, will poke him then20:48
wendarmordred: (had dinner with him last night, but seemed like a topic that needs a laptop)20:49
openstackgerritMerged openstack-infra/shade: Rename auth_plugin to auth_type  https://review.openstack.org/17143220:50
*** ashleighfarnham has quit IRC20:50
*** ajo has quit IRC20:51
*** kmartin has joined #openstack-infra20:51
openstackgerritClark Boylan proposed openstack-infra/system-config: Ensure latest on etherpad vcsrepo  https://review.openstack.org/16432320:52
clarkbmordred: fungi ^20:52
*** cference_ has quit IRC20:52
clarkbI will do a db dump prior to that getting applied so either let me know if you are going to approve it or just +2 and I can approve20:52
*** sdake_ has joined #openstack-infra20:53
openstackgerritJulia Kreger proposed openstack-infra/shade: Add test of OperatorCloud auth_type=None  https://review.openstack.org/17216520:54
*** tiswanso_ has quit IRC20:54
*** andreykurilin has quit IRC20:55
*** rbradfor_ has joined #openstack-infra20:56
*** hichihara has joined #openstack-infra20:56
*** sdake has quit IRC20:57
krotscheckgreghaynes: Hey, did that pymysql oslo.db error ever get fixed?20:57
krotscheckgreghaynes: i.e. is it in a newer version of oslo.db?20:58
clarkbkrotscheck: I think it did https://review.openstack.org/#/c/155574/ that merged back in february and oslo.db has been released since then20:58
*** Rockyg has quit IRC20:58
* clarkb is double checking on release time20:58
krotscheckclarkb: neat20:58
*** markvoelker has joined #openstack-infra20:59
clarkb1.7.1 was in march and we just had a release today20:59
*** marcusvrn has quit IRC20:59
openstackgerritJulia Kreger proposed openstack-infra/shade: Add test of OperatorCloud auth_type=None  https://review.openstack.org/17216521:00
krotscheckclarkb: grazie, that's what I needed.21:01
*** dimtruck is now known as zz_dimtruck21:01
*** tkelsey has quit IRC21:02
*** hdd has joined #openstack-infra21:03
greghayneskrotscheck: yep21:03
greghaynesah, clarkb go tit21:03
*** gmurphy has left #openstack-infra21:03
*** markvoelker has quit IRC21:03
fungidhellmann: close, just one more simplification you can make there21:04
*** aysyd has quit IRC21:07
fungiclarkb: what does ensure latest do with a specific revision in vcsrepo? those seem somewhat contradictory21:08
clarkbfungi: hopefully I explained that in the commit message21:08
clarkbfungi: if you don't ensure latest the vcsrepo doesn't update anything21:08
fungiyou know what? you totally did and i went straight to the diff :/21:08
clarkbits ok, gerrit makes that too easy :)21:08
fungiindeed21:08
*** annegentle has joined #openstack-infra21:09
*** cdent has joined #openstack-infra21:09
fungiclarkb: lgtm21:09
krotscheckgreghaynes: Just for sanity's sake, if I pull these except catches out of the codebase, the unit tests should pick up errors in an older version of oslo, yes?21:10
*** mmedvede has quit IRC21:11
fungidhellmann: i'm not getting that mox failure on oslo.messaging py34 again. seems to maybe be somewhat rare. i got it on my second run but not in the several since21:11
*** aysyd has joined #openstack-infra21:11
funginot sure if that's py3k-specific or just so rare you're not noticing it on 2.x either21:12
dhellmannfungi: sounds like a race, so it's probably not related to python 3, unless there's some difference in behavior when eventlet is not used21:12
dhellmannyep21:12
greghayneskrotscheck: where in the code?21:13
*** stevemar has quit IRC21:13
hasharfungi: you might want to tag a new version of nodepool  since https://review.openstack.org/#/c/170289/  changed the mysql module being used :)21:13
krotscheckgreghaynes: http://git.openstack.org/cgit/openstack-infra/storyboard/tree/storyboard/db/api/base.py#n28721:14
krotscheckgreghaynes: There's two more in there.21:14
*** ZZelle_ has quit IRC21:14
*** dizquierdo has quit IRC21:15
fungihashar: sure, can do. do we need a 0.0.2 just before the dependency change and then a 0.0.3 after?21:15
*** ldnunes has quit IRC21:15
fungihashar: or should i tag that commit 0.0.2?21:15
fungithe couple of commits which have merged since seem benign enough to just wrap up into 0.0.2 if you're not particularly picky21:16
*** hdd has quit IRC21:16
greghayneskrotscheck: ah, yes. that is a gross workaround21:17
greghaynesthat I wrote21:17
fungihashar: i can put it on the meeting agenda for tomorrow and then take care of it once others have a chance to object to tagging a new release for it21:17
krotscheckgreghaynes: Right, but the awesome fix you put in oslo_db is now available, so I'm trying to figure out how to roll back that hack.21:17
greghayneskrotscheck: You could just remove that last except block, the issue is that techincally you wouldnt support the versions of oslo.db you have in your requirements then21:18
krotscheckgreghaynes: That's part of a different pathc21:19
*** tnovacik has quit IRC21:19
krotscheckgreghaynes: I'll add you to the review when it goes up.21:19
krotscheckgreghaynes: It looks like you removed a DBReferenceError catch earlier.21:19
greghaynesok21:20
*** andreykurilin has joined #openstack-infra21:20
clarkbmordred: can I get a review on 164323 again? if you +2 I can approve and babysit21:20
clarkbmordred: I want to do a mysqldump before the upgrade21:20
clarkbalso going to wait for neutron meeting to end as they appear to be actively using etherpad for tracking stuff right now21:21
*** gmurphy has joined #openstack-infra21:21
openstackgerritMichael Krotscheck proposed openstack-infra/storyboard: Updated oslo_db.  https://review.openstack.org/17308321:22
openstackgerritMichael Krotscheck proposed openstack-infra/storyboard: Removed hack.  https://review.openstack.org/17308421:22
*** mattfarina has quit IRC21:23
krotscheckgreghaynes: ^^ There ya go21:24
*** dustins has quit IRC21:25
greghayneskrotscheck: oh, does storyboard not use global-reqs?21:25
krotscheckgreghaynes: Nope21:26
krotscheckgreghaynes: We're not really openstack21:26
krotscheckgreghaynes: Well, that's not really true. We're a bit of a special snowflake.21:26
clarkbits not that special, all of infra is that way21:26
krotscheckclarkb: shaddup. we're a special snowflake.21:26
krotscheckSPECIAL I SAY21:27
clarkbthere is a difference between deploying cloud software and running developer tooling on a cloud21:27
openstackgerritKhai Do proposed openstack-infra/puppet-gerrit: Add properties, md and css files to direct download list  https://review.openstack.org/17308721:27
greghaynesyea, I dont think its a bad thing, just a TIL21:27
clarkbzaro: can you make sure that the bouncy castle upgrade from gerrit 2.10 ends up on the meeting agenda tomorrow?21:27
* krotscheck blinks.21:28
krotscheckbouncy castle?21:28
clarkbkrotscheck: yes, it is unfortunately not as awesome as the name might imply https://www.bouncycastle.org/java.html21:28
*** Sukhdev has quit IRC21:28
*** fedexo has joined #openstack-infra21:28
krotscheckclarkb: Huhn. i dunno, I kindof feel that a non-US-export-restricted version of crypto tools is awesome.21:29
krotscheckBut then I'm an anarchist :D21:29
* krotscheck isn't really an anarchst21:30
clarkbkrotscheck: oh sure, we have plenty of those. This particular one appeas to release backward incompatible changes that force us to upgrade out of band with our distros which is a giant headache21:30
krotscheckclarkb: Bring them under the openstack banner.21:30
krotscheckclarkb: :)21:30
zaroclarkb: well, it's on the actions list for me to test gerrit 2.10 upgrade.  so we should hit it.21:30
clarkbzaro: awesome21:30
*** isviridov_away is now known as isviridov21:31
hasharfungi: not sure whaqt is the best to tag :)21:31
*** mmedvede has joined #openstack-infra21:32
fungihashar: i think i'll probably just push to do the branch tip21:32
hasharfungi: but I am surely actively working on the Debian packaging :D  I will post on your list once I have something worth sharing21:32
*** gyee has quit IRC21:32
clarkbcinerama: how are we doing with zanata-dev? anything I can do while I wait for reviews myself?21:32
fungihashar: that's awesome--thanks!!!21:32
hasharfungi: and we have almost all our CI using a Zuul debian package :D21:32
hasharfungi: i am migrating the scheduler this week.;  Then will have to catch up with 3 or 4 months of your changes21:32
*** mrda-away is now known as mrda21:33
greghayneskrotscheck: I think your oslo.db version hasnt been synced to mirrors yet21:33
*** mjturek1 has joined #openstack-infra21:34
krotscheckgreghaynes: Likely21:34
krotscheckI'll recheck later21:34
*** asettle-gym is now known as asettle21:34
*** dizquierdo has joined #openstack-infra21:34
*** dizquierdo has quit IRC21:34
*** dizquierdo has joined #openstack-infra21:34
fungikrotscheck: greghaynes: weird. we only got the wheel not the sdist tarball http://pypi.dfw.openstack.org/simple/oslo.db/21:35
fungioh, that's because pypi only got the wheel https://pypi.python.org/pypi/oslo.db21:35
fungidhellmann: ^21:35
fungii'm checking the upload logs now21:36
*** frickler_ has joined #openstack-infra21:36
dhellmannfungi: hrm21:36
* dhellmann notes that pypi started showing dependencies at some point when he wasn't looking21:36
fungiick! http://logs.openstack.org/62/6235b7ed3957eb98e67f02bf761535af37d23123/release/oslo.db-pypi-both-upload/1e75289/console.html21:37
fungiHTTPError: 503 Server Error: backend read error21:37
clarkbpypi said "NO"21:37
greghayneswomp womp21:37
fungidstufft: ^ is it safe to retry twine when that happens?21:37
*** frickler has quit IRC21:38
* krotscheck feels like the canary in the coalmine :)21:38
*** miqui has quit IRC21:38
openstackgerritMichael Krotscheck proposed openstack-infra/storyboard: Updated oslo_log  https://review.openstack.org/17309321:38
openstackgerritMichael Krotscheck proposed openstack-infra/storyboard: Updated all oslo versions.  https://review.openstack.org/17309421:38
*** fedexo has quit IRC21:39
dstufftfungi: probably21:41
fungidstufft: strangely, it seems to have uploaded that file, but returned a 50321:41
*** Rockyg has joined #openstack-infra21:42
*** kgiusti has left #openstack-infra21:42
dstufftfungi: 503 backend read error means "the internet between fastly and PyPI went sideways during the request"21:42
*** mriedem is now known as mriedem_away21:42
fungiwondermous21:42
dstufftso it could happen during the process of uploading21:42
dstufftor it could happen after that before fastly can read the response21:42
dstufftand techincally it looks like Fastly Edge -> Fastly Shield -> PyPI, so it could happen between Fastly Edge and Fastly Shield, and the request to Fastly Shield -> Fastly PyPI still happens21:43
*** e0ne has quit IRC21:43
dstuffttl;dr it depends21:43
fungilooks like the md5sum of whay i downloaded from pypi matches what twine tried to upload, so it's complete21:44
*** isviridov is now known as isviridov_away21:44
*** cody-somerville has joined #openstack-infra21:45
*** gordc has quit IRC21:45
fungidhellmann: okay, i've manually rerun the upload steps for the tarball and it's showing at https://pypi.python.org/pypi/oslo.db now21:48
fungishould end up on our mirrors in moments21:49
*** rtom has joined #openstack-infra21:49
*** rtom has quit IRC21:49
dhellmannfungi: thank you. I'd like to send email about the issue. Is it safe to say something like "The upload job failed for the sdist so some installations might have failed. The missing file has been restored and should appear in our mirror shortly."21:49
clarkbhrm so are mordred jeblair pleia2 all afk right now?21:50
clarkbjhesketh: awake yet? :)21:50
fungidhellmann: it may not have even been noticed by anyone, the wheel got uploaded fine so anyone using a new enough pip to grab wheels got the new release and everyone else got the previous release tarball still21:50
dhellmannfungi: ok, how did we notice then?21:50
fungidhellmann: greghaynes and krotscheck were manually checking for a new behavior they were expecting from the latest release, and weren't seeing it, sounds like21:51
*** fedexo has joined #openstack-infra21:51
fungianyway, it's showing up on our mirrors now too21:52
dhellmannfungi: ok, thanks21:52
*** notnownikki has quit IRC21:53
*** dkranz has quit IRC21:53
greghaynesdhellmann: fungi yep - there was a version bump on the storyboard req's so a workaround for a bug could be removed and we werent able to find the package21:57
krotscheckdhellmann fungi: Thanks, rechecking the patch.21:57
krotscheckFor reference: https://review.openstack.org/#/c/173083/21:58
krotscheckI love working on email. It always starts with: Oh, these other things broke in the meantime.21:59
*** markvoelker_ has joined #openstack-infra22:00
*** dizquierdo has quit IRC22:00
*** otter768 has joined #openstack-infra22:02
*** crainte has quit IRC22:02
openstackgerritDoug Hellmann proposed openstack-infra/project-config: Use Oslo core teams for stable maint, too  https://review.openstack.org/17307522:03
lifelessclarkb: oh hai22:05
reeddoes anybody know how to diagnose a bounce in mailman?22:05
pleia2clarkb: I just landed at my hotel and have a little while before the conference opening social, need me to look at something?22:05
clarkblifeless: hello22:05
*** unicell has joined #openstack-infra22:05
*** andreykurilin has quit IRC22:05
clarkbpleia2: https://review.openstack.org/#/c/164323/ no need to approve. I want to mysqldump first, just looking for review22:05
fungireed: sort of. what specifically are you looking for?22:05
reedevery now and then there is someone whose "membership in the mailing list Openstack has been disabled due to excessive bounces"22:05
* pleia2 has a look22:05
reedfungi, how to trace back why that address was disabled?22:06
lifelessclarkb: hows te ovs issue?22:06
krotscheckI love version kickoff week. All my builds go to the top of the queue22:06
clarkblifeless: I havne't looked at it today, but as far as I know nothing has changed since22:06
*** otter768 has quit IRC22:06
fungireed: most frequent cause i've seen is subscribers with dmarc-enforcing gateways causing them to get unsubscribed because they received a message through the list from someone at a dmarc-enabled domain22:06
clarkblifeless: if you point me at an ssh pubkey I can give you access to the held env22:06
*** tonytan4ever has quit IRC22:07
lifelessclarkb: the one on gerrit is fine22:07
lifelessclarkb: or /query22:07
reedfungi, but there is no way to find out after the fact?22:07
reedi see in bounce.log there is only the count, not the reason22:07
fungireed: so the list tries to deliver the message to them and their mailserver refuses it because the dmarc signature is invalid, and after something like 5 times of that it unsubscribes them22:08
fungireed: the actual rejections are in the exim logs i think. have a specific subscriber you need checked?22:08
reedfungi, I'll check the exim logs, I want to learn how to do this22:08
reedfungi, it looks like an aggressive symantec filter22:10
reed553-Message filtered. Refer to the Troubleshooting page at\n553-http://www.symanteccloud.com/troubleshooting for more\n553 information.22:10
fungireed: quite possible22:10
*** mwagner_lap has quit IRC22:10
*** soren has quit IRC22:11
fungithe user should suggest their mailserver administrators whitelist e-mail coming from our lists.openstack.org server22:12
reedyep, thanks22:13
lifelessclarkb: should I ask q's here or query ?22:13
clarkb lifeless here is fine22:13
*** adalbas has quit IRC22:14
clarkblifeless: as long as we don't interrupt too much other conversation but its been pretty quiet22:14
lifelessclarkb: ok, so this is a nova-network config ?22:14
clarkblifeless: correct22:14
cineramaclarkb: hey, i was having lunch22:14
lifelessbr_pub is the shared virtual L2?22:15
clarkblifeless: one of them yes. br_flat is another22:15
lifelesswhy are there two ?22:15
clarkblifeless: br_pub is the L2 intended to carry the tempest to floating IP traffic though and is the one that doesn't work22:15
clarkblifeless: because nova ebtables breaks if you carry flat traffic and public traffic over the same l222:16
lifelessok22:16
lifelessso flat is internal l222:16
clarkbyup22:16
lifelesspub is external l222:16
clarkbyup22:16
lifelessand pub is broke22:16
clarkbyes, if you try to ping 172.24.4.2 from 172.24.4.1 the arp who has will hit br_pub then ovs will drop it22:16
clarkbit hits br_pub on 172.24.4.1, no who has crosses gre22:17
cineramaclarkb: so assuming the last merge got applied to translate-dev...would be good to see the /var/log/wildfly/console.log & might need my account tweaked in the database22:17
*** asettle has quit IRC22:19
*** amitgandhinz has quit IRC22:19
lifelessclarkb: there's no access port22:21
clarkbcinerama: I still see the from email exception, I probably have to restart the service?22:21
lifelessclarkb: is that deliberate?22:21
clarkblifeless: semi, I did that because thats how neutron wants br-ex defined. But when tested with a veth pair one end attached to br_pub it fails the same way22:21
*** dboik has quit IRC22:21
cineramaclarkb: huh. wildfly should've restarted with the new config if puppet got run22:21
clarkblifeless: at least it appeared to via tempest22:21
clarkbcinerama: let me double check how long the process has been running22:22
lifelessclarkb: well, neutron must not touch these ports22:22
lifelessclarkb: and bridges - br-ex is going to have to be layered as a port on top of br_pub22:22
clarkbcinerama: appears to be running since april 10th22:22
*** dboik has joined #openstack-infra22:22
clarkblifeless: not quite, instead of calling it br_pub we just make an L2 called br-ex22:22
lifelessclarkb: otherwise neutron will mess things up, vs fix it :)22:22
clarkblifeless: then neutron uses that and is mostly happy22:22
cineramaclarkb: hmm sounds like puppet hasn't run there yet...do we need to run it manually there?22:23
*** MaxV has joined #openstack-infra22:23
clarkblifeless: I also tried connecting br-ex to our existing brctl made linux bridge using gre and that did not work but I didn't spend much time debugging that22:23
clarkbcinerama: oh I bet I know why, absible isn't likely able to ssh in22:23
lifelessclarkb: depends on what you're doing with Neutron I suspect. VLAN testing will need the CI infra to bring up the L2 fully. Still - you've tested, I shall not argue :)22:24
lifelessclarkb: can I fiddle here with a free hand?22:24
clarkbpleia2: cinerama should I make it so ansible can puppet that node? I will run puppet manually right now22:24
clarkblifeless: yup, I can always rebuild a new pair of nodes in that state22:24
clarkblifeless: so feel free22:24
cineramaclarkb: i don't see why not, i would defer to pleia2 here but i think she is busy22:24
pleia2clarkb, cinerama wfm22:25
cineramabut not *that* busy :)22:25
clarkbcinerama: pleia2 puppet run by hand and wildfly restarted22:26
clarkbI do not see exceptions now22:27
clarkbcinerama: do you need to test something to determine if db needs updating?22:27
cineramaclarkb: i'll try logging in. it'll give *me* a vague error message but there'll be something in the logs22:27
clarkbcinerama: kk22:27
clarkbfungi: are you around?22:27
clarkbfungi: I am going to make an etherpad db dump now, then approve the upgrade change22:28
*** Rockyg has quit IRC22:29
clarkbfungi: I know its getting late for you, but hoping to have at least one core/root around before I upgrade22:29
*** annegentle has quit IRC22:29
fungiclarkb: totally here, just taking out the trash22:30
*** cschwede has quit IRC22:30
cineramaclarkb: i'm going to need a console log on that guy. we were going so well...22:31
cineramaclarkb: /var/log/wildfly/console.log22:31
clarkbcinerama: lots of could not prepare statement db errors22:32
*** tiswanso has joined #openstack-infra22:32
*** baoli_ has quit IRC22:32
*** cschwede has joined #openstack-infra22:33
cineramaclarkb: i haven't seen that before. i might need a bit more detail if possible.22:33
lifelessclarkb: ok so I know whats wrong22:33
lifelessclarkb: you need to have just one gre l2 bridge22:34
clarkbfungi: ok backup taken and is in /root/clarkb-db-dumps22:34
clarkbfungi: I am approving the change now22:34
fungiclarkb: thanks, noted22:34
lifelessclarkb: and then wrap one or both of _pub and _flat with VLAN tags.22:34
clarkblifeless: thats silly22:34
lifelessclarkb: no its not22:35
clarkblifeless: they are two "physically" separated bridged22:35
lifelessclarkb: not right now they aren't22:35
clarkblifeless: you don't need vlan tagging in that case22:35
clarkblifeless: really? what is bridging them?22:35
lifelessclarkb: you have two gre tunnels on the same IP address at both end22:35
clarkboh hrm does ovs not let us distinguish those as different tunnels like the ip made gre interfaces?22:36
*** gyee has joined #openstack-infra22:36
lifelessclarkb: write down the expected packet headers from each tunnel - src ip, dst ip, ip proto22:36
lifelessclarkb: then tell me which bridge its for22:36
*** rm_work is now known as rm_work|away22:37
clarkblifeless: https://git.openstack.org/cgit/openstack-infra/devstack-gate/tree/functions.sh#n825 note the key22:37
clarkblifeless: this should be doable, but ovs either can't do it or has incomplete configuration22:37
*** tiswanso has quit IRC22:38
lifelessGRE tunnel keys are what ovs maps traffic tags to22:38
*** marun has quit IRC22:38
clarkblifeless: it would be amazing if ovs documented that anywhere22:38
fungias opposed to the interface ids22:39
fungisurprising, but i can see reasons for that choice22:40
clarkbalso it would be nice if it let arp through instead of dropping it wihtout a reason22:40
lifelessthis is going off of memory, but i'm fairly sure.. can test by adding a vlan access port to the working bridge22:41
lifelessclarkb: I think its blocked everything off from some sanity check somewhere22:41
lifelessgive me a minute to experiment22:41
clarkblifeless: psuedo spanning tree?22:41
*** MaxV has quit IRC22:41
lifelesshuh, no22:42
clarkbcinerama: working on getting a paste that isn't too crazy for you22:42
clarkbcinerama: I think i have found where the interesting stuff starts22:43
cineramaclarkb: cool, thanks.22:43
openstackgerritMerged openstack-infra/system-config: Ensure latest on etherpad vcsrepo  https://review.openstack.org/16432322:43
fungiso basically one gre tunnel with two (or later more if we want) 802.1q encapsulated vlans, one for flat and one for pub?22:44
*** zz_dimtruck is now known as dimtruck22:44
clarkbfungi: well lifless just said "huh, no" so maybe not :)22:45
clarkbfungi: but if that is indeed the issue yes, we would set it up that way22:45
fungihuh, ok ;)22:45
clarkbcinerama: its about 1k lines22:45
lifelessyeah, default port is trunk22:45
lifelessthought so22:45
fungiyeah, it'll cost us a handful of additional bytes out of the mtu, but we're there regardless with gre22:45
cineramaclarkb: bring it ooooon. there shouldn't be anything too heinous in there22:45
lifelessbtw ovs-vswitchd.conf.db is where a lot of stuff is documented22:45
cineramaclarkb: it's java. they love their verbose errors22:46
lifelessclarkb: from readingthat in_key and out_key can be used to control the tunnel key analogous to the ip commands22:47
clarkbcinerama: http://paste.openstack.org/show/203776/ I actually trimmed it down a bit more, realized you likely don't need to see all the startup stuff22:47
lifelessclarkb: but, I think it matches the reality better to think of the tunnel as a trunk port in a dc22:47
clarkblifeless: I don't22:47
clarkblifeless: its a point to point tunnel22:47
clarkblifeless: saying it matches reality better to carry tagged traffic isn't more or less correct that using multiple point to points22:48
clarkblifeless: just like you can connect two devices in a DC on different ports without tagging or you can use a single port with tagging22:48
lifelessclarkb: there is no physical separation, so if one is used in tests with VLANs, that overlap a manually chosen key, it *will* conflict.22:48
lifelessclarkb: this is precisely the behaviour of a trunk port in a DC22:48
clarkbboth are equally valid realities22:48
fungitrunk ports rarely have ip addresses on them22:49
cineramaclarkb: Caused by: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure22:49
fungion their endpoints i mean22:49
lifelessif there were multiple points, I would agree with you22:49
lifelessget another public IP for the VM, and what you are describing would make sense22:49
lifelessclarkb: I give up22:49
lifelessclarkb: I'll check this works, and hand back to you22:49
clarkblifeless: I just don't want to make decisions based on arbitrary things that don't matter22:50
clarkblifeless: both are correct. We can use either. Lets not say one is better because data center22:50
fungion the other hand "this works, the other doesn't" is far from arbitrary. but yes the analogies aren't critical to the solution22:50
lifelessthey aren't both correct, we can't use either unless one of them is not being used as a raw L222:51
cineramaclarkb: wondering if the trove is ok22:51
clarkblifeless: I thought you said we could either use vlan tagging our in_key and out_key?22:51
lifelessfrom the docs22:51
clarkbs/our/or/22:51
lifelessEach   tunnel   must   be   uniquely   identified  by  the  combination  of  type,  options:remote_ip,22:51
lifeless       options:local_ip, and options:in_key.22:51
*** mtanino has quit IRC22:51
*** coolsvap has quit IRC22:51
lifelessclarkb: I said *as long as* we're not putting tagged traffic on *either* of them22:51
clarkbcinerama: I can give it a go in a moment22:51
fungithis reminds me more of how some switch-router platforms handle l2 vpn id keys directly in their bridge tables22:51
fungii'm glaring at you, screenos22:52
lifelessclarkb: there are both neutron and nova-net configurations that will do that, and that will break with one config in mysterious ways, but not in the other.22:52
cineramaclarkb: thanks, just when you're free22:52
clarkblifeless: I guess I still don't follow, why can't we use in_key on both of them with different keys?22:53
lifelessIFF all the ports are access ports, VLANs prohibited, because the underlying substrate is acting like a trunk port22:54
clarkblifeless: but the substrates are independent22:54
lifelessthey are not22:54
clarkblifeless: br_pub is one switch with its own flows and br_flat is another22:54
lifelessthey are not the substrates22:54
lifelessGRE is the subtrate22:54
openstackgerritClint 'SpamapS' Byrum proposed openstack-infra/shade: Add test for invalidation after delete  https://review.openstack.org/17260022:55
openstackgerritClint 'SpamapS' Byrum proposed openstack-infra/shade: Deprecate use of cache in list_volumes  https://review.openstack.org/17259922:55
openstackgerritClint 'SpamapS' Byrum proposed openstack-infra/shade: Invalidate volume list cache when creating  https://review.openstack.org/17259522:55
openstackgerritClint 'SpamapS' Byrum proposed openstack-infra/shade: Make cache key generator ignore cache argument  https://review.openstack.org/17310922:55
clarkblifeless: but both would be uniquely identified by different keys22:55
lifelessas long as ovs knows everything is access ports22:56
lifelessbut you're fighting the way ovs is designed22:56
clarkbI am?22:56
clarkball I wanted was two logical l2s completely separated from each other in a manner that brctl supports22:56
*** dprince has quit IRC22:56
reedcan someone please review these two? a little more documentation would be good https://review.openstack.org/#/c/104951/ https://review.openstack.org/#/c/138195/22:56
clarkbif ovs wants to be different it should document that so that its poor users can figure these different design decisions22:57
jheskethMorning22:57
clarkbif I have to use vlan tagging thats fine, but none of the documentation/man pages/blog posts I could find mentioned that22:57
lifelessclarkb: it is documented - see the man page I referenced above22:57
lifelessclarkb: or I may be wrong, it may be that all the things I've looked at before were misunderstood22:58
lifelessclarkb: *anyway*, using in_key and out_key should work until VLANs are being tested, and then it may or may not work22:59
lifelessright now it can't work because there are two identical tunnel definitions and that is documented as being illegal22:59
clarkblifeless: reading the man page you pointed out does not explain anything about access ports vs other ports22:59
lifelessline 177523:00
lifelessand around line 76823:00
lifelessthe key thing needed to match the ip commands is to set in_key and out_key23:00
lifelessthatwill make the tunnels unique23:01
openstackgerritClint 'SpamapS' Byrum proposed openstack-infra/shade: MonkeyPatch time.sleep in unit tests to avoid wait  https://review.openstack.org/17311023:01
lifelessin_key:flow is what does flow -> key mapping23:01
lifelessclarkb: ^ that is where I think we've been talking at cross purpose23:01
*** bknudson has quit IRC23:02
*** hashar has quit IRC23:02
lifelessclarkb: so - to fix your patchset, you need to set in_key and out_key on both those bridges to unique values23:02
clarkbyes tahts exactly what I said and you said I needed to do vlan tagging23:02
lifelessclarkb: yes, I was used to flow based keys23:02
lifelessclarkb: I didn't realise that that was optional23:03
*** dims_ has joined #openstack-infra23:03
*** cdent has quit IRC23:03
*** ftersin has quit IRC23:03
lifelessregardless, the issue is clearly diagnosed - yes?23:03
clarkbI think so, about to push a patchset up to confirm23:03
lifelessthe (gre, remote_ip, local_ip, in_key) tuple must be unique23:03
*** dims has quit IRC23:04
*** mtanino has joined #openstack-infra23:04
lifelessand in_key on one must match out_key on the other23:04
clarkbup and you can use key as a shortcut to make them both match23:04
lifelessyup23:04
fungithis almost smells like juniper had a hand in the openvswitch specification23:05
lifelessclarkb: so - tl;dr: problem diagnosed, solution proposed, and I'm sorry I was a grumpy f*ing bear23:05
*** shashankhegde has quit IRC23:05
clarkblifeless: thank you for looking.23:06
openstackgerritClint 'SpamapS' Byrum proposed openstack-infra/shade: MonkeyPatch time.sleep in unit tests to avoid wait  https://review.openstack.org/17311023:06
clarkbI just need to figure out how to supply multiple options now23:07
SpamapSShrews: Ran 23 tests in 0.113s (+0.006s)23:07
* SpamapS just can't stand tests that time.sleep ;)23:07
*** dimtruck is now known as zz_dimtruck23:07
*** shashankhegde has joined #openstack-infra23:07
*** Krinkle is now known as Krinkle|detached23:08
*** cody-somerville has quit IRC23:09
*** dannywilson has joined #openstack-infra23:09
lifelessclarkb: I'm all logged out of those machines now23:10
clarkblifeless: kk, I will clean them up as soon as I get results back from the patch I am about to push23:10
clarkblifeless: any idea how to pass multiple options when using ovs-vsctl? ovs-vsctl man page does not seem to cover this (or I skimmed too fast)23:11
clarkblooks like its options:key=val options:key=val repeated23:12
clarkbthank you pica823:13
lifelessclarkb: what options are you setting23:13
lifelessyah23:13
clarkblifeless: remote_ip and key23:13
*** dannywilson has quit IRC23:13
*** rbradfor_ has quit IRC23:13
clarkbso options:remote_ip=x.x.x.x options:key=X seems to do the trick23:13
*** chlong has joined #openstack-infra23:15
lifelesscool23:15
lifelessmight be an idea to also set local_ip23:15
lifelessto avoid sending the traffic out the wrong port in the event of eth1 going down or some such23:15
openstackgerritClark Boylan proposed openstack-infra/devstack-gate: DO NOT MERGE testing overlay network options  https://review.openstack.org/17171423:15
clarkboh, well we can try that if ^ still has trouble23:15
lifelessoh, Im' suggesting it as belts-n-bracers, since it won't be needed on any happy-path occasion23:16
clarkbgotcha23:16
lifelesshmm, pbr tests failure on 2.723:17
lifelessalso - hope everyone saw the shiny shiny news that pip now autobuilds wheels :)23:17
clarkbfungi: looks like puppet updated git but didn't restart the service for etherpad23:18
clarkbfungi: http://puppetboard.openstack.org/report/etherpad.openstack.org/1235f7bf8e3ce87f7fe90e48e1f91932a2305410 I am going to restart it now23:18
fungik23:18
clarkb ok should be up now23:20
clarkbplease test23:20
fungidoing23:20
clarkbok first thing I notice is I need a hard refresh otherwise not all needed js ends up in my browser23:21
clarkbso yay caches23:21
clarkbhttps://etherpad.openstack.org/p/clarkb-test can be our test pad23:21
fungilgtm so far. i didn't have any pads open/cached23:21
*** jamielennox|away is now known as jamielennox23:22
*** dboik_ has joined #openstack-infra23:22
*** dboik_ has quit IRC23:22
fungihad just restarted my browser because of fat fingers (ctrl-w to delete the last word is dangerously close to ctrl-q on a qwerty board)23:22
clarkbok I will send a note to the dev list now saying we updated it and if you see errors please hard refresh to invalidate any cached javascript23:22
*** dboik_ has joined #openstack-infra23:22
mtreinishmy red looks brighter than usual to me23:23
mtreinishbut it's probably all in my head23:23
*** rlandy has quit IRC23:23
clarkbcinerama: ok I am almost back to where I can help with translate dev23:24
clarkbcinerama: give me a few more minutes (haven't forgotten about you)23:24
*** rbradfor_ has joined #openstack-infra23:24
*** rbradfor_ has quit IRC23:24
clarkbfungi: have a list of CVEs I can attribute the update to?23:24
fungiclarkb: so far just one, because mitre is being slow23:24
clarkbI will take that one :)23:25
fungiclarkb: CVE-2015-329723:25
*** dboik has quit IRC23:25
ShrewsSpamapS: awesome. good catch23:27
*** cody-somerville has joined #openstack-infra23:27
clarkbfungi: mail sent to the -dev list thanks for your help23:29
fungiclarkb: thank you!23:29
clarkbhrm I think I sent it, don't see it yet. That'll learn me to use a silly mua23:30
clarkbhttp://lists.openstack.org/pipermail/openstack-dev/2015-April/061393.html there it is23:30
mtreinishmordred: man that migration we wrote is really slow. I've been running it on a much smaller dataset in my test db on hp cloud and it's been going for > 3hrs already23:30
mtreinishmordred: although now that I think about it, it's probably hp cloud just being slow23:30
*** amitgandhinz has joined #openstack-infra23:30
*** wenlock1 has quit IRC23:32
*** wenlock has quit IRC23:33
clarkbcinerama: I am able to connect to the db using the zanata user and supplied passwd23:34
clarkbcinerama: maybe the url connection string is wrong?23:34
*** amitgandhinz has quit IRC23:35
*** mwagner_lap has joined #openstack-infra23:35
cineramaclarkb: that's interesting. can you have a look at /opt/wildfly/standalone/configuration/standalone.xml?23:35
clarkbcinerama: thats where I took the connection info from23:35
clarkbcinerama: but I used mysql client not jdbc to connect so had to map things23:36
*** marun has joined #openstack-infra23:36
cineramaclarkb: right, the username and password are in the <security> section under  <subsystem xmlns="urn:jboss:domain:datasources:2.0">23:37
clarkbyup23:37
clarkbcinerama: I am wondering if the connection url is wrong though23:37
clarkbcinerama: its jdbc:mysql://host:3306/zanata?characterEncoding=UTF-823:37
cineramaclarkb: is "host" a bowdlerization of the actual host?23:38
clarkbcinerama: yes23:38
clarkbcinerama: the hostname is also correct23:39
clarkbI used it verbatim from the config to connect with mysql client23:39
*** SergeyLukjanov has quit IRC23:39
cineramaclarkb that should be OK. we haven't changed that bit of the template in many revs.23:39
*** nbernard has quit IRC23:39
*** asettle has joined #openstack-infra23:40
asettleGood morning again!23:40
*** SergeyLukjanov has joined #openstack-infra23:40
*** asettle has left #openstack-infra23:41
*** Swami has quit IRC23:41
cineramaclarkb: and now i'm in. weird23:41
clarkbcinerama: you're into the db or into zanata?23:41
clarkblooks like zanata (looking at logs)23:42
cineramaclarkb: yes, i've logged in..the only downside is i typoed my username so i don't have admin powerz23:42
clarkbwell I am tailing the log now  will let you know if I see db issues again23:42
*** r-daneel has quit IRC23:43
clarkbthere the go23:45
clarkbI wonder if this is realted to the issue review had with trove23:45
clarkbthe db times out too fast23:45
clarkbpleia2: did you apply the config to the db and restart the db?23:45
clarkbcinerama: I will poke at trove settings in a bit23:46
*** rlucio_ has quit IRC23:46
cineramaclarkb: it's also not lvoing my login23:47
*** marun has quit IRC23:47
*** markvoelker has joined #openstack-infra23:49
*** zz_dimtruck is now known as dimtruck23:49
*** markvoelker_ has quit IRC23:51
*** weshay has quit IRC23:52
*** markvoelker_ has joined #openstack-infra23:53
*** markvoelker_ has quit IRC23:54
openstackgerritMatthew Treinish proposed openstack-infra/subunit2sql: Add db api methods to delete old runs and test_runs  https://review.openstack.org/17219023:55
openstackgerritMatthew Treinish proposed openstack-infra/subunit2sql: Add a cli subcommand for deleting old rows  https://review.openstack.org/17220023:55
openstackgerritJamie Lennox proposed openstack-infra/project-config: Add django-openstack-auth-kerberos project  https://review.openstack.org/17280323:55
*** dboik_ has quit IRC23:55
*** dboik has joined #openstack-infra23:56
*** markvoelker has quit IRC23:56
*** salv-orl_ has quit IRC23:57
clarkbcinerama: it did not have the sanity config applied, I applied it an am restarting the db now23:58

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