cheryljalexisb: "cannot determine machine endpoint bindings: endpoint bindings00:01
cherylj      for "s#dummy-source" not found'"00:01
cheryljalexisb: not sure what that means in terms of their code change, though00:01
davecheney2016-02-02 00:47:47 ERROR juju.worker runner.go:229 exited "toolsversionchecker": cannot update tools information: cannot get latest version: cannot find available tools: cannot read product data, invalid URL "https://juju-dist.s3.amazonaws.com/tools/streams/v1/com.ubuntu.juju:released:tools.sjson" not found00:50
davecheney2016-02-02 00:47:55 ERROR juju.worker runner.go:229 exited "toolsversionchecker": cannot update tools information: cannot get latest version: cannot find available tools: cannot read product data, invalid URL "https://juju-dist.s3.amazonaws.com/tools/streams/v1/com.ubuntu.juju:released:tools.sjson" not found00:51
davecheneyis it _really_ necessary to poll for new tools every 8 seconds00:51
cheryljjuju has OCD00:55
davecheneyhonestly ,checking once and hour would be overkill01:17
davecheneythumper: https://github.com/juju/juju/pull/425901:40
davecheneypprof PR for review01:40
davecheneyi wish the juju deployer hadn't stopped working01:45
davecheneyi know people tell me that i'm using an outdated versin01:45
davecheneybut frankly, if we (juju) have to live in a world where we have to keep making the versino in trusty work for the next 3 years01:45
davecheneythen the same should apply to the deployer01:45
mwhudsonaxw: do you know things about azure?01:51
davecheney  File "/usr/lib/python2.7/dist-packages/deployer/env/go.py", line 96, in get_cli_status01:55
davecheney    status = super(GoEnvironment, self).get_cli_status()01:55
davecheneycherylj: thumper who changed the default juju status to be _not_ yaml01:56
davecheneythat has broken the juju-deployer shipped in trusty01:56
davecheneyyup, that's the problem01:58
davecheneycherylj: where should I log this bug ? against juju01:58
davecheneyor against the deployer that it needs to call juju status with an explicit formatter ?01:58
mupBug #1540697: Recent change to juju status has broken compatibility with trusty juju-deployer <juju-core:New> <https://launchpad.net/bugs/1540697>02:00
axwmwhudson: I do, sorry, missed your message02:05
mwhudsonaxw: heh you answered the thread anyway02:05
axwdavecheney: the (informal) plan for 2.0 is that anyone who needs structured output needs to explicitly specify the format02:07
axwdavecheney: otherwise you get tabular, and its format might change over time02:07
natefinchwallyworld, axw: git blame says you guys might know about the implementation of deploying bundles with juju core?02:08
axwso long as that holds, deployer needs to be changed02:08
axwnatefinch: I know some, I added storage support02:08
mwhudsoni guess deployer in trusty needs to be sru-ed then?02:08
wallyworldnatefinch: francesco did the work, we tweaked as needed02:08
natefinchwallyworld: is it me, or do we just drop all the flags (except storage) on the floor if you target a bundle?02:09
mupBug #1540697 opened: Recent change to juju status has broken compatibility with trusty juju-deployer <juju-core:New> <https://launchpad.net/bugs/1540697>02:09
wallyworlddavecheney: deployer in trusty will work with 1.2502:09
wallyworldtht is our mandate02:09
axwnatefinch: which flags?02:10
wallyworld2.0 will be co-installable with 1.25 andf 1.25 wil be supported for 2 years02:10
natefinchaxw: juju deploy flags02:10
wallyworld2.0 will not be backwards compatible02:10
wallyworldwe will support juju in trusty via 1.2502:10
natefinchaxw: like --constraints -n --networks etc ... looking at the code, it seems like we woudl totally let you 'juju deploy cs:/bundle/foo/bar --constraints=blah' and not complain, but completely ignore the constraints02:11
natefinchaxw: it's the "not complain" part that bothers me02:12
axwnatefinch: looks a bit like it. I'd say because it kind of changes the meaning of deploy entirely. not one service, but multiple02:12
axwnatefinch: yeah02:12
axwwe should error if you specify them02:12
natefinchaxw: exactly my thinking02:12
axwnatefinch: I added a bundle-specific syntax to the --storage command that allows you to specify for services in a bundle. we probably should do that for other things, but erroring would be a good start02:13
natefinchaxw: yep.  ok, just wanted to make sure I wasn't missing anything obvious before filing a bug02:14
davecheneywallyworld: ahh, ok02:25
davecheneythumper: http://paste.ubuntu.com/14854594/02:25
wallyworlddavecheney: we shoudl try and make deployer work though if possible i think. 2.0 has deployer built in but i don't think it is yet fully functionally complete02:26
davecheneythis is on a modest sized deployment02:26
davecheneywallyworld: it's a trivial chang to the deployer02:26
davecheneybut that has to be backported to trusty02:26
davecheneywhich is not trivial02:26
thumperdavecheney: nice02:26
wallyworlddavecheney: it is - my other concern is that in 2.0 old yaml fields like agent0state are gone02:26
davecheneythumper: i'm going to commit this and backport it02:26
davecheneyso we can investigate that failure02:26
wallyworldso deployer may need subsequent tweaking02:27
davecheneyprecise environments still have two mongodbs installed ...02:29
davecheneyroot@ip-10-250-24-28:/tmp# ps auxww | grep mongo02:29
davecheneymongodb   5462  0.6  0.9 372940 38264 ?        Ssl  01:48   0:15 /usr/bin/mongod --config /etc/mongodb.conf02:29
davecheneyroot      6410  3.2  1.2 3026932 46808 ?       Ssl  02:28   0:01 /usr/bin/mongod --auth --dbpath /var/lib/juju/db --sslOnNormalPorts --sslPEMKeyFile /var/lib/juju/server.pem --sslPEMKeyPassword xxxxxxx --port 37017 --noprealloc --syslog --smallfiles --journal --keyFile /var/lib/juju/shared-secret --replSet juju --ipv6 --oplogSize 51202:29
davecheneyroot      6511  0.0  0.0   8100   932 pts/1    S+   02:29   0:00 grep --color=auto mongo02:29
davecheneyour mongob does not restart if the process dies for any reason :(02:29
thumperisn't that what upstart or systemd does?02:30
davecheneykill 641002:30
davecheneyprocess does not restart02:30
davecheneyroot@ip-10-250-24-28:/tmp# initctl list | grep juju02:32
davecheneyjuju-db stop/waiting02:32
davecheneyjuju-clean-shutdown stop/waiting02:32
davecheneyjujud-machine-0 start/running, process 554802:32
davecheneyprocess does not restart02:32
mupBug #1512718 changed: Leader election fails with "leadership failure: leadership manager stopped" <arm64> <landscape> <sts> <juju-core:Triaged> <juju-core 1.24:Triaged> <juju-core 1.25:Incomplete> <https://launchpad.net/bugs/1512718>02:39
mupBug #1540697 changed: Recent change to juju status has broken compatibility with trusty juju-deployer <juju-core:Invalid> <juju-deployer:New> <https://launchpad.net/bugs/1540697>02:39
mupBug #1540701 opened: juju deploy <bundle> silently ignores most CLI flags <bundles> <deploy> <juju-core:New> <https://launchpad.net/bugs/1540701>02:39
thumperwallyworld: under which situation will a service not have a status doc?02:40
wallyworldthumper: never; there ws a bug in an early 1.24(?) release where that could have been the case02:40
thumperwallyworld: so I can assume that there will always be a status doc for services?02:41
thumperfor migration?02:41
wallyworldthe status doc is written first02:41
wallyworldin the []txn.Ops slice02:41
davecheneythumper: master is blocekd02:55
davecheneycan I have your permission to land this change ?02:55
davecheneythumper: and environment with 11 machines, has 51 firewall watchers running03:12
davecheneyno, sorry,03:12
davecheney20 @ 0x437c2a 0x446482 0x445472 0xa3f46f 0xa40234 0xd53b36 0x464e4103:12
davecheneywe do have 58 moingodb conections in use03:13
davecheneyit's just a bloodbatch03:13
davecheneyit's just a bloodbath03:13
davecheneyand this environment is idle03:13
thumperdavecheney: I've added my mark on the github PR03:15
thumperdavecheney: try to land it now03:16
davecheneycmd/pprof/pprof.go:61:2: cannot find package "runtime/trace" in any of: /usr/lib/go/src/pkg/runtime/trace (from $GOROOT) /mnt/jenkins/workspace/github-merge-juju/tmp.f4uCbWbBZu/RELEASE/src/runtime/trace (from $GOPATH)03:42
davecheneyshake's fist at Go 1.203:42
* davecheney deletes things til go 1.2 stops complaining03:43
mupBug #1540316 changed: provider/maas: bridgescript should support vlans <maas-provider> <juju-core:New> <https://launchpad.net/bugs/1540316>04:03
mupBug #1540316 opened: provider/maas: bridgescript should support vlans <maas-provider> <juju-core:New> <https://launchpad.net/bugs/1540316>04:06
mupBug #1540316 changed: provider/maas: bridgescript should support vlans <maas-provider> <juju-core:New> <https://launchpad.net/bugs/1540316>04:15
axwwallyworld: not quite as big as your diffs, but sorry all the same: http://reviews.vapour.ws/r/3698/diff/#04:25
wallyworldrevenge is sweet04:26
axwon a positive note, net reduction of ~1600 lines04:26
wallyworldaxw: reviewed, i love seeing code deleted04:49
axwwallyworld: thanks04:49
axwwallyworld: there's a card for creating the second model already, is a TODO necessary?04:53
davecheneythumper, each client of a 1.25 api server consumes 50 goroutines05:26
=== bradm_ is now known as bradm
axwwallyworld: how do you feel about this? https://github.com/juju/juju/compare/cloud-credentials...axw:cloud-credentials-detect-regions06:17
anastasiamacaxw: love the name! detector :D06:23
wallyworldaxw: looking06:24
wallyworldaxw: it does give a way to avoid having a personal clouds file for openstack, if standard env vars are set via sourcing a credentials file or whatever06:29
wallyworldi think it makes sense06:29
wallyworldand we can use an lxd env var for the lxd host06:29
axwwallyworld: might not even need to, you could list the remotes06:30
axwwallyworld: e.g. "lxc remote list"06:30
axwwallyworld: and report each of those as a region06:30
axwwallyworld: I'll tidy this up and propose then. it's a bit less hacky than what was there, and supports openstack. we can revisit if there's dissent06:31
voidspacedimitern: thanks for the review, I replied to all your comments.09:09
voidspacedimitern: is your WIP branch ready yet?09:10
dimiternvoidspace, it is ready - the ci run last night revealed the main issue, which I'm fixing now: don't assume bindings always exist09:11
dimiternvoidspace, so I'll be pushing a few more commits on top to fix that and re-enable the tests I disabled09:12
voidspacedimitern: cool09:12
dimiternvoidspace, responded to your replies09:28
voidspacedimitern: I think you're actually wrong about the test channel - the test really is the owner as it closes the channel.09:33
voidspacedimitern: and the "code path" is still the same.09:33
voidspacedimitern: the other two issues - ok.09:33
dimiternvoidspace, I don't mind that much if you leave the chan creation outside of the patched func09:35
frobwaredimitern, standup10:02
voidspacefrobware: dimitern: dooferlad: PR for merge of latest master changes back to maas-spaces. http://reviews.vapour.ws/r/3703/10:08
dimiternvoidspace, LGTM - you'll likely manage to land this before my branch which also includes it, so there shouldn't be a conflict10:12
mupBug #1540832 opened: Hard wired bridge prevents the use of the fan overlay network <juju-core:New> <https://launchpad.net/bugs/1540832>10:13
mupBug #1540832 changed: Hard wired bridge prevents the use of the fan overlay network <juju-core:New> <https://launchpad.net/bugs/1540832>10:16
mupBug #1540832 opened: Hard wired bridge prevents the use of the fan overlay network <juju-core:New> <https://launchpad.net/bugs/1540832>10:19
frobwaredimitern, dooferlad, voidspace, jam: the trusty/series issue we talked about in the standup is being tracked here atm: https://bugs.launchpad.net/juju-core/+bug/154077110:51
mupBug #1540771: Bootstrap fails with trusty is not a valid distro_series <bootstrap> <juju-core:Invalid> <juju-core maas-spaces:Triaged> <https://launchpad.net/bugs/1540771>10:51
frobwaremgz, looking for help with bug 1540771. dimitern plans to update his branch again (RSN) and we'll want another CI run but little point if we keep running into said bug.10:53
mupBug #1540771: Bootstrap fails with trusty is not a valid distro_series <bootstrap> <juju-core:Invalid> <juju-core maas-spaces:Triaged> <https://launchpad.net/bugs/1540771>10:53
dooferladfrobware/dimitern/voidspace: Updated bind syntax: http://reviews.vapour.ws/r/3569/diff11:22
dimiterndooferlad, cheers, looking11:23
dimiterndooferlad, reviewed11:34
dooferladdimitern: http://reviews.vapour.ws/r/3569 addressed those issues.12:07
dimiterndooferlad, thanks! let's get it in then I guess12:28
mupBug #1540900 opened: juju deploy ignores model default-series <juju-core:New> <https://launchpad.net/bugs/1540900>12:38
jamfwereade_: ping12:46
mupBug #1540900 changed: juju deploy ignores model default-series <juju-core:New> <https://launchpad.net/bugs/1540900>12:47
mfoordfrobware: what's the release notes link again please12:47
mfoordfrobware: never mind, found it12:48
frobwaremfoord, thought so as you show up as already viewing. :)12:48
mfoordfrobware: heh12:53
mupBug #1540900 opened: juju deploy ignores model default-series <juju-core:New> <https://launchpad.net/bugs/1540900>12:56
jamfwereade_: I had a question about "connects", and another one about some lxd configuration stuff12:56
fwereade_jam, heyhey13:17
voidspacecherylj:  dimitern:  frobware: alexisb: given that 2.0 is dropping maas 1.8 support we should probably not mention improved support for maas 1.8 in the release notes (there's a maas 1.8 compatibility section)14:01
voidspacebug 153463614:01
mupBug #1534636: Destroying a hosted model in the local provider leaves the controller unusable <juju-release-support> <juju-core:Triaged> <https://launchpad.net/bugs/1534636>14:01
frobwarejam: saw your doc, but punting until I get the maas-spaces unit tests to work on ppc6414:01
voidspacecherylj:  dimitern:  frobware: alexisb: we can probably also drop the mention of bug 1534636 as a known issue, as the local provider won't14:02
voidspace*won't be there in 2.014:02
* voidspace lunches14:02
* frobware follows suit14:02
dimiterncherylj, frobware, alexisb, voidspace, I think that section was copied from 1.25 rel. notes, so we should indeed drop it for the 2.0 notes14:06
jamfwereade_: hey, still around?14:16
fwereade_jam, ha, yes, but apparently notification-blind14:41
mattywjam, any reason why we shouldn't do $$merge$$ on this https://github.com/juju/juju/pull/4131 ?14:42
cheryljmattyw: yes, we are trying to get some branches landed and we'd rather not have master be a moving target14:44
mattywcherylj, ok cool thanks14:44
cheryljfrobware: I see now that maas-spaces has some new commits.  What's the expectation now for testing?  are we still testing dimitern's branch?14:45
mattywcherylj, ok - judging by the comment lxd provider is broken in xenail so it probably needs to land before the release - but I don't really know14:47
mattywcherylj, I'm not involved - I'm just an interested party14:47
cheryljmattyw: we can look at getting it into alpha2, but really, if it misses, alpha3 is next week14:48
mattywcherylj, ack14:48
frobwarecherylj, yes, new commits for blocking API and bootstrap whilst discovery taking place (this is the one we talked about last night). bind syntax change for '@' -> '=' which came out of CT. and merge current master into maas-spaces.14:59
frobwarecherylj, dimitern is updating and fixing tests based on the CI run.14:59
cheryljfrobware: is dimitern's branch up to date with maas-spaces again?14:59
frobwarecherylj, dimitern: do you plan to rebase maas-spaces onto your branch?14:59
cheryljotherwise we need to get a bless on dimitern's, then merge into maas-spaces, then get a bless on maas-spaces before it can all land in master15:00
frobwarecherylj, ack.15:00
frobwarecherylj, I would advocate that dimiter rebases so we only do test once15:00
cheryljfrobware: agreed15:01
cheryljand don't forget to pull in master too.  There were some changes that came in15:01
frobwarecherylj, we did yesterday - need to check if we're talking about the same change.15:01
cheryljfrobware: probably same one.  the pprof thing15:01
frobwarecherylj, yep15:02
frobwarecherylj, 3 things to fix in dimiter's branch: CI test failures surrounding bindings, skipped unit tests (though for expediency we could skip these), and ppc64 unit test failures.15:02
cheryljfrobware: wallyworld has a PR up for a different bug that's only been seen on his branch (although the underlying problem exists on master too).  I think it should go into his branch rather than master so we can demonstrate in CI that it fixes the problem15:02
cheryljfrobware: what's the confidence level in getting a bless on dimitern's branch today15:03
frobwarecherylj, ppc64 might still fail. looking at that now. need to hear from dimiter about progress on the other problems. also bug 1540771 might cause a cursed build again.15:05
mupBug #1540771: Bootstrap fails with trusty is not a valid distro_series <bootstrap> <juju-core:Invalid> <juju-core maas-spaces:Triaged> <https://launchpad.net/bugs/1540771>15:05
cheryljfrobware: is that bug a problem with the MAAS setup?  or a problem on the branch?15:06
frobwarecherylj, I would say MAAS setup and/or CI setup.15:07
cheryljfrobware: is there someone who can work with jog_ to track it down so we don't hit it again?15:07
frobwarecherylj, put me down, though I have a hard commitment 7:30pm.15:09
cheryljfrobware: ok, jog_ should be in before then15:11
frobwarecherylj, I'm not entirely sure how quick a CI run can be but I would advocate we have a stripped down run that initially only runs the failures; we need to iterate faster15:11
cheryljfrobware: yes, but your changes could cause some of the previously passing tests to fail, so we need to get a complete run before a merge.  We could see about doing some initial tests for verification before a complete run15:12
cheryljsinzui: is there a way we could just run selected tests for maas-spaces?15:12
cheryljmgz: ^^15:12
frobwarecherylj, agreed.15:12
frobwarecherylj, I just don't want to wait $N hours to find out we haven't fixed the existing failures15:13
cheryljfrobware: yeah, I understand15:14
sinzuicherylj: we can re-run selected tests for previously tested revisions. We cna do this beause we saved  the built packages and streams. We cannot run tests with a branch.15:18
frobwarecherylj, do you know if we have access to ppc64?15:21
frobwareI'm futzing trying to fix this unit test failure15:22
frobwareI have a qemu ppc64 running but it's not terribly efficient or productive.15:22
frobwareactually, I cannot build juju atm (on ppc64)15:22
cheryljmgz, sinzui, is it possible to get frobware access to the CI ppc machines?15:24
sinzuicherylj: yes, though I am informed that ports.ubuntu.com is down and that limits what we can do. No installs15:26
cheryljsinzui: should be okay, it's just a unit test run15:26
frobwaresinzui, cherylj: ah, that explains some of my problems over the last 20 mins.15:26
cheryljfrobware, dimitern, I've copied over the charms that CI uses for the basic deploy tests here:  https://private-fileshare.canonical.com/~cherylj/dummy-charms/15:34
cheryljthere's also a txt file with the steps used to deploy15:34
cheryljyou can start with testing on AWS, since that's failing on the maas-spaces-controller-space-config15:35
frobwaredooferlad, if you're between tasks please could you help out on the test failures ^^15:37
dooferladfrobware: I am not quite, but will be soon.15:37
natefinchericsnow: it occurs to me that we need to have the resource download code on the server regardless, to support the GUI15:40
ericsnownatefinch: I wasn't aware of any GUI-related requirements15:41
natefinchericsnow: I think rick_h__ would probably be upset if we couldn't deploy charms from the gui that used resources in the charmstore15:42
ericsnownatefinch: regardless, you make a good point about what the GUI might need15:42
natefinchericsnow: but you're right that there was nothing in the spec about it15:42
cheryljfwereade_: would you be able to review https://github.com/juju/juju/pull/4266 ?  It's related to that bug I talked to you about yesterday15:42
ericsnownatefinch: I can follow up with the GUI team15:42
=== jog_ is now known as jog
rick_h__natefinch: can you email the context there?15:45
natefinchrick_h__: sure15:47
ericsnowrick_h__, natefinch: I just send an email15:49
rick_h__natefinch: ty on my phobe aylt the conference and want to better follow what's up15:49
fwereade_cherylj, alexisb: ack15:51
ericsnownatefinch: let's get back together some time after lunch to put together the demo for last iteration15:53
natefinchericsnow: ok15:53
joghi frobware, I'm here if you have questions about bug 154077116:13
mupBug #1540771: Bootstrap fails with trusty is not a valid distro_series <bootstrap> <juju-core:Invalid> <juju-core maas-spaces:Triaged> <https://launchpad.net/bugs/1540771>16:13
frobwarejog, immediate question is if we run again will this just repeat. is this at related to not running against MAAS 1.7 or 1.8?16:15
jogfrobware, it failed several time in a row in the same way. Master had run before maas-spaces and passed. The bug is open for failures against MAAS 1.916:18
frobwarejog, but new against 1.9?16:19
jogfrobware, not sure what you mean?16:19
frobwarejog, trying to understand whether it is our branch that causes the failure or a separate 1.9 issue16:22
jogwell I just reran the last revision of master (1cb8f03) and don't see the failure there. I'm running the maas-spaces revision that failed again now, just to be sure there was no other issue.16:24
frobwaredimitern, ^^16:27
frobwarejog, thx - will keep an eye out for the result.16:28
frobwarejog, is your "reran" http://reports.vapour.ws/releases/356416:35
frobwarejog, because that show as cursed16:35
frobwarejog, ah, but only for ppc64.16:36
natefinchman, the function that actually does charm deployments from the client is a hairy mess17:01
natefinch100 lines of if statements17:02
perrito666how sad17:03
natefinchand weird implicit meanings to error values... good lord17:04
natefinchperrito666: https://github.com/juju/juju/blob/master/cmd/juju/commands/deploy.go#L24917:07
perrito666deploy charm Or bundle, just in case17:08
perrito666is there a reason why that is not the at least 3 methods it should be?17:08
natefinchperrito666: the problem is that our deploy command does way too much and has way too much encoded into the string we pass it17:09
perrito666"we might have been given a bundle" <-- that is one.  " if not a bundle then maybe a local charm" <- there is another,17:09
natefinchthe fact that this code is a nightmare is just an indication that the UX is a nightmare...17:10
natefinchI mean, the code could be better even given the bad UX17:10
perrito666that is not true, code can be bad and ux be decent17:10
perrito666I have  glanced at that function and already know it can be split17:11
perrito666I do have the "fresh pair of eyes" advantage17:11
natefinchyeah, it absolutely should be refactored17:11
perrito666but cmon, a bit of good will might make things better17:11
natefinchI think someone added bundles and just didn't want to refactor what was there17:11
perrito666well mcdonalds lunch is not the best alternative to stay awake after lunch17:12
natefinchoh how nice, we're throwing away an error and assuming we know what was in it17:24
natefinchoh hey, someone fixed it on master... ok, I gotta rebase.17:25
voidspacedimitern: we have 19 code branches checking for the AddressAllocation feature flag18:08
dimiternvoidspace, so next step is to prepare a PR that drops them I guess18:16
voidspacedimitern: did we ever get devices by default on master?18:24
voidspacedimitern: it looks to me, from skimming the code, that if we lose AddressAllocation we lose containers as devices too18:24
voidspacedimitern: and we go back to leaking DHCP leases18:25
dimiternvoidspace, that's ok - we'll redo it properly anyway18:53
=== StoneTable is now known as aisrael
=== TheRealMue is now known as TheMue
natefinchgah, why do we have a client api function that no one calls? (ServiceDeployWithNetworks)19:23
natefinch.....maybe we keep it so the tests can test the server's backwards compatibility19:25
natefinchhmm, in which case it should be in test code only.19:26
mupBug #1540469 changed: [ARM64][LXD Provider][2.0-alpha1-0ubuntu1~16.04.1~juju1] juju run command ERROR fork/exec /usr/bin/ssh: cannot allocate memory <run> <juju-core:New> <https://launchpad.net/bugs/1540469>19:27
mupBug #1540469 opened: [ARM64][LXD Provider][2.0-alpha1-0ubuntu1~16.04.1~juju1] juju run command ERROR fork/exec /usr/bin/ssh: cannot allocate memory <run> <juju-core:New> <https://launchpad.net/bugs/1540469>19:30
perrito666natefinch: are you sure no one calls it?19:32
natefinchperrito666: grep says it's only called in tests19:32
perrito666I do recall that there is a cascade of calls for service deploy19:32
perrito666ServiceDeploy -> serviceDeployWithX -> ServiceDeployWithY and so on19:32
perrito666natefinch: take a look a few versions back, perhaps its legacy and asking to go19:33
natefinchperrito666: yeah, almost certainly... like I said, my guess is that it needs to stick around for testing that we keep backwards compatibility with old clients... but that means it should be moved to test code, so it's more obviously something you should let rot in a corner19:34
perrito666actually, if you are working in 2, that is a death sentence19:34
mupBug #1540469 changed: [ARM64][LXD Provider][2.0-alpha1-0ubuntu1~16.04.1~juju1] juju run command ERROR fork/exec /usr/bin/ssh: cannot allocate memory <run> <juju-core:New> <https://launchpad.net/bugs/1540469>19:36
natefinchperrito666: *shrug* I'll file a bug19:38
mupBug #1540469 opened: [ARM64][LXD Provider][2.0-alpha1-0ubuntu1~16.04.1~juju1] juju run command ERROR fork/exec /usr/bin/ssh: cannot allocate memory <run> <juju-core:New> <https://launchpad.net/bugs/1540469>19:39
mupBug #1540469 changed: [ARM64][LXD Provider][2.0-alpha1-0ubuntu1~16.04.1~juju1] juju run command ERROR fork/exec /usr/bin/ssh: cannot allocate memory <run> <juju-core:New> <https://launchpad.net/bugs/1540469>19:42
=== natefinch_ is now known as natefinch
natefinchdammit... something is throttleing the hell out of my laptop lately20:03
perrito666natefinch: use htop?20:03
perrito666aghh, sms spam, just what I needed20:04
natefinchperrito666: htop is very pretty and I have no idea what it means20:05
perrito666natefinch: use the man page20:05
perrito666if the upper graphs for microprocessor are full (or the ram one) something is behaving wrongly, you can use f6 iirc to sort things by cpu or ram20:06
perrito666and that would put the culprit at the top20:06
natefinchperrito666: I'm running tests, and expect my processors to all be pegged, but they're all at like 50%, and my tests are taking a lot longer than usual to run20:09
perrito666natefinch: try iotop then20:10
perrito666perhaps something is hammering your hd20:10
natefinchhmm disk read is always 0, I presume that's a bug, or my computer would not be working ;)20:13
natefinchthat weird feeling when you change the signature of like 3 very important functions.... and no tests fail20:28
natefinch...I'm sure it's fine20:28
perrito666natefinch: http://www.quickmeme.com/img/a7/a7eb19ae524e1d066fae16e5e7c0438c86fa321468cd3e3d0764731cf86f869c.jpg20:29
natefinchlol indeed20:29
davechen1yno menn0 today ?21:04
davechen1ypaging the on call reviewer: http://reviews.vapour.ws/r/3700/21:04
davechen1yto the OR, STAT!21:04
perrito666that is me21:05
* perrito666 reviews21:05
natefinchperrito666: means "right now"21:06
natefinchperrito666: I believe it was backronymed to Sooner Than Already There21:06
* natefinch makes perrito666 google backronym instead of stat21:07
perrito666natefinch: its ok, for me davechen1y 's now is 11 hours away so technically I can pull it21:07
natefinchperrito666: https://www.youtube.com/watch?v=gNIwlRClHsQ21:09
natefinchericsnow: I gotta run a little early today (will be back later as usual).  Want to talk demo?21:13
ericsnownatefinch: sure21:14
ericsnownatefinch: moonstone21:14
perrito666davechen1y: there you got a bunch of fixmes :p and all more than 10 hours before your asked time21:18
menn0waigani: ship it on the auth worker PR21:18
waiganimenn0: thanks21:20
* perrito666 makes coffee before a long long review21:43
=== natefinch is now known as natefinch-afk
perrito666I wish we had un-shipit as an option22:21
menn0waigani: deployer review done22:53
=== mthaddon` is now known as mthaddon
menn0wallyworld: http://reviews.vapour.ws/r/3711/ doesn't need a review right?23:06
wallyworldmenn0: nope, is a straight merge of a feature branch23:07
wallyworlda huge one at that23:07
menn0wallyworld: I noticed so I'm glad to hear I don't need to review it :)23:07
wallyworldall the terminology changes etc23:08
wallyworldas per your earlier email to dev list23:08
wallyworldmodel model model23:08
wallyworldcherylj: i wonder if the add-machine "regression" is just a timebomb in 1.25 say, waiting to show up like the leadership issue did, and we just haven't seen it yet23:12
wallyworldyou'd think it would show up in more places23:13
perrito666menn0: tx for the rev23:13
rick_h__just dropping as an FYI: https://twitter.com/mitechie/status/69450656800034406423:18
rick_h__yea, really good attendance here at the summit23:20
* perrito666 wanted to go23:23
rick_h__we'll have to hit up the next one. We had a couple of core folks here23:24
davechen1ycherylj: when will the next 1.25 build come out ?23:29
davechen1yie, if I want to get my profiling stuff into a 1.25 build23:30
davechen1ywhat deadline should I focus on ?23:30
cheryljdavechen1y: I'm targeting late next week23:41
cheryljfor 1.25.423:41
cheryljhooray!  api-command-rename has LANDED!23:42
* rick_h__ does a giant happy dance23:43
cheryljmaster will stay blocked until we get a bless23:43
cheryljthen we shall open up the flood gates23:43

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