| davecheney | q: how long does it take to run zero juju tests | 00:23 |
|---|---|---|
| davecheney | real 26m57.934s | 00:23 |
| davecheney | user 76m59.990s | 00:24 |
| davecheney | sys 9m22.711s | 00:24 |
| davecheney | 26 minutes to test nothing!! | 00:24 |
| davecheney | go test -i ./... && time go test ./... | 00:24 |
| perrito666 | davecheney: that cannot be the build time of the test suite | 00:31 |
| davecheney | that is the time to run all the tests, excluding actually running tests | 00:35 |
| davecheney | sorry, hang on | 00:35 |
| davecheney | i posted the rwong numbers | 00:35 |
| * perrito666 is expectant | 00:35 | |
| anastasiamac | blahdeblah: \o/ thank yuo. I saw :D | 00:59 |
| blahdeblah | Looks like it's some sort of leadership election strangeness | 01:00 |
| anastasiamac | blahdeblah: m working on 1.25 and the bug 's on the radar. cannot tell u right now when it'll get some love but should happen \o/ | 01:02 |
| davecheney | real 15m30.976s | 01:02 |
| davecheney | user 56m52.867s | 01:02 |
| davecheney | sys 2m50.591s | 01:02 |
| davecheney | lucky(~/src/github.com/juju/juju) % go test -i ./... && time go test ./... -run=XXX | 01:02 |
| blahdeblah | anastasiamac: cool - thanks | 01:02 |
| davecheney | 15:30 to build and run zero tests | 01:02 |
| blahdeblah | I should document my workaround on that bug | 01:03 |
| anastasiamac | blahdeblah: tha would b fantastic! | 01:03 |
| blahdeblah | anastasiamac: Not really; it's just "restart all the things" :-\ | 01:03 |
| anastasiamac | blahdeblah: :D | 01:04 |
| wallyworld | thumper: it seems that the share model functionality does not support setting readonly = true. there is a read only flag but it's always false. is that your recollection? and we never access the flag anyway | 01:04 |
| anastasiamac | blahdeblah: it would be great to isolate the bug, i.e. minimum setup and steps to reproduce :D | 01:04 |
| thumper | wallyworld: hey | 01:05 |
| thumper | wallyworld: yes, very much so, but cmars's team is taking that on | 01:05 |
| thumper | I wrote the bit that made read only possible | 01:05 |
| wallyworld | ah, righto, thanks | 01:05 |
| thumper | but we don't yet support it at the cli, or client api | 01:05 |
| blahdeblah | anastasiamac: I just deployed my env & waited. Yesterday morning I was working on it just fine; came back yesterday evening and it was broken. | 01:05 |
| thumper | to set / get / list | 01:05 |
| wallyworld | yep | 01:05 |
| thumper | wallyworld: was there another question about that? | 01:06 |
| wallyworld | thumper: there's been discussion about create-model and who should be allowed to do it etc, as if i can create a model in your controller using your creds, i can cost you money. so i'm just seeing what's been done in that area | 01:07 |
| thumper | nothing | 01:07 |
| thumper | the current expectations are that creds are passed up explicitly | 01:08 |
| thumper | since that is to change | 01:08 |
| wallyworld | yes, in a --config file | 01:08 |
| thumper | there needs to be discussion | 01:08 |
| wallyworld | yup. i think it should be if you are the admin user of a controller you can create a model using teh saem creds | 01:09 |
| wallyworld | otherwise you need to supply them | 01:09 |
| === pmatulis_ is now known as pmatulis | ||
| mup | Bug #1544847 changed: configSuite.TestNewModelConfig test failure lxd <ci> <lxd> <regression> <test-failure> <unit-tests> <juju-core:Fix Released> <juju-core lxd-container-type:Fix Released> <https://launchpad.net/bugs/1544847> | 03:15 |
| mup | Bug #1548799 changed: bootstrap from windows fails with no such file <ci> <regression> <windows> <juju-core:Fix Released by axwalk> <https://launchpad.net/bugs/1548799> | 03:15 |
| mup | Bug #1550810 changed: TestDetectCredentialsKnownLocationWindows missing region <ci> <regression> <test-failure> <windows> <juju-core:Fix Released by wallyworld> <https://launchpad.net/bugs/1550810> | 03:15 |
| mup | Bug #1544847 opened: configSuite.TestNewModelConfig test failure lxd <ci> <lxd> <regression> <test-failure> <unit-tests> <juju-core:Fix Released> <juju-core lxd-container-type:Fix Released> <https://launchpad.net/bugs/1544847> | 03:21 |
| mup | Bug #1548799 opened: bootstrap from windows fails with no such file <ci> <regression> <windows> <juju-core:Fix Released by axwalk> <https://launchpad.net/bugs/1548799> | 03:21 |
| mup | Bug #1550810 opened: TestDetectCredentialsKnownLocationWindows missing region <ci> <regression> <test-failure> <windows> <juju-core:Fix Released by wallyworld> <https://launchpad.net/bugs/1550810> | 03:21 |
| mup | Bug #1544847 changed: configSuite.TestNewModelConfig test failure lxd <ci> <lxd> <regression> <test-failure> <unit-tests> <juju-core:Fix Released> <juju-core lxd-container-type:Fix Released> <https://launchpad.net/bugs/1544847> | 03:33 |
| mup | Bug #1548799 changed: bootstrap from windows fails with no such file <ci> <regression> <windows> <juju-core:Fix Released by axwalk> <https://launchpad.net/bugs/1548799> | 03:33 |
| mup | Bug #1550810 changed: TestDetectCredentialsKnownLocationWindows missing region <ci> <regression> <test-failure> <windows> <juju-core:Fix Released by wallyworld> <https://launchpad.net/bugs/1550810> | 03:33 |
| davecheney | thumper: the apiserver/client package imports juju/agent just to get one constant, which brings in the entire api client ... | 03:51 |
| thumper | what's the constant? | 03:51 |
| davecheney | const SystemIdentity = "system-identity" | 03:51 |
| thumper | why does the apiserver want that constant? | 03:52 |
| davecheney | for reasons that I do not understand | 03:52 |
| davecheney | the apiserver has a client | 03:52 |
| davecheney | and that client does things, on remote machines ?!?! | 03:52 |
| davecheney | i have NFI why the apiserver has a client | 03:52 |
| davecheney | and why that client is juju/api | 03:52 |
| davecheney | https://github.com/davecheney/prdeps | 03:53 |
| davecheney | wrote a simple tool to print out dep graphs | 03:53 |
| davecheney | the shit it's turning up is making my hair turn white | 03:53 |
| thumper | the server has a client??? | 03:53 |
| davecheney | yes | 03:54 |
| davecheney | apiserver/client | 03:54 |
| thumper | um... | 03:54 |
| thumper | that is the implementation of the client facade is it not? | 03:54 |
| thumper | it isn't an api client | 03:54 |
| davecheney | but it imports the api client | 03:54 |
| davecheney | and then uses the api client to do stuff | 03:55 |
| davecheney | O_o! | 03:55 |
| thumper | oof | 03:59 |
| wallyworld | anastasiamac: if you get a moment sometime, could you please look at http://reviews.vapour.ws/r/3999/ | 05:41 |
| anastasiamac | wallyworld: | 05:51 |
| anastasiamac | looking :D | 05:51 |
| frobware | jam: ping, 1:1 today? | 09:05 |
| jam | frobware: sorry. I'm omw | 09:09 |
| dimitern | frobware, morning | 09:11 |
| frobware | dimitern: morning | 09:11 |
| dimitern | frobware, I have figured out how to do the multi-nic containers backed by devices | 09:11 |
| dimitern | frobware, I have 2 machines running - each with 2 nics, first disabled, the other one with 4 vlans | 09:12 |
| dimitern | frobware, and on each of these nodes, I have 2 containers running with 5 nics each, using the respective br-eth1[.xx] bridges | 09:12 |
| dimitern | pinging works, connecting with nc shows correct source and destination addresses | 09:13 |
| dimitern | so we need to make devices with physical nics, generated macs, and linked to the correct maas vlan and subnet | 09:14 |
| dimitern | can't do vlan interfaces on devices, but it wasn't necessary | 09:14 |
| mup | Bug #1551141 opened: Juju bootstrap local - cannot get replset config: not authorized for query on local.system.replset <juju-core:New> <https://launchpad.net/bugs/1551141> | 09:40 |
| mup | Bug #1551141 changed: Juju bootstrap local - cannot get replset config: not authorized for query on local.system.replset <juju-core:New> <https://launchpad.net/bugs/1551141> | 09:43 |
| dimitern | frobware, FYI, I've updated the spike card assigned to me with all the relevant info | 09:43 |
| mup | Bug #1551141 opened: Juju bootstrap local - cannot get replset config: not authorized for query on local.system.replset <juju-core:New> <https://launchpad.net/bugs/1551141> | 09:52 |
| dooferlad_ | frobware: hangout time | 10:01 |
| === dooferlad_ is now known as dooferlad | ||
| voidspace | dooferlad: frobware: dimitern: http://reviews.vapour.ws/r/4000/ | 12:05 |
| voidspace | all tests pass and manual testing works | 12:05 |
| dimitern | voidspace, reviewed | 12:19 |
| frobware | voidspace: I had one question | 12:20 |
| voidspace | frobware: we still do name translation because maas can still use names with spaces (etc) | 12:21 |
| voidspace | frobware: once maas is fixed we can remove name translation | 12:21 |
| voidspace | dimitern: thanks | 12:21 |
| voidspace | frobware: we will kill it with fire as soon as possible :-) | 12:22 |
| frobware | voidspace: ok, gotcha | 12:23 |
| voidspace | frobware: ping | 12:36 |
| frobware | voidspace: pong | 12:40 |
| * dimitern whew ... ok vlans work across hosts and containers - tagged traffic gets untagged before reaching the container | 12:41 | |
| voidspace | dimitern: :-) | 12:46 |
| perrito666 | morning | 13:48 |
| === lazypower is now known as lazyPower | ||
| dooferlad | voidspace, dimitern, frobware: http://reviews.vapour.ws/r/4002 -- The API server + mongo space change is ready for review. | 14:43 |
| natefinch | ericsnow: you around? | 14:43 |
| frobware | dooferlad: will look in a bit, just finishing up a review too. | 14:45 |
| dimitern | dooferlad, cheers, will look at it soon | 14:45 |
| dooferlad | frobware, dimitern: thanks. It looks big, but there is a huge name change in one of the test files that takes up a big chunk of it - don't be put off! | 14:46 |
| mup | Bug #1551276 opened: 2.0-beta2 stabilization <blocker> <juju-core:Triaged> <https://launchpad.net/bugs/1551276> | 15:26 |
| mup | Bug #1551276 changed: 2.0-beta2 stabilization <blocker> <juju-core:Triaged> <https://launchpad.net/bugs/1551276> | 15:32 |
| mup | Bug #1551276 opened: 2.0-beta2 stabilization <blocker> <juju-core:Triaged> <https://launchpad.net/bugs/1551276> | 15:38 |
| natefinch | ericsnow: ping? | 16:25 |
| ericsnow | natefinch: hey | 16:25 |
| natefinch | ericsnow: hey... I'm working on that upgrade charm, pull metadata from charmstore card | 16:26 |
| natefinch | ericsnow: there's a task that says "Set available field in resource doc." ... is that out of date? | 16:26 |
| ericsnow | natefinch: yep | 16:26 |
| ericsnow | natefinch: really, I'd expect that we'd be doing exactly the same thing as deploy for this | 16:27 |
| ericsnow | natefinch: along with an extra step to release the stored resource blob, if necessary | 16:29 |
| natefinch | ericsnow: well, serverside, I don't think we added anything for deploy about the charmstore at all | 16:30 |
| natefinch | ericsnow: there's just NewResolvePendingResourcesOps | 16:30 |
| ericsnow | natefinch: that's what I'm talking about | 16:30 |
| natefinch | ericsnow: ok, so we're relying on the client to push up the new resource metadata? | 16:30 |
| ericsnow | natefinch: ah | 16:31 |
| ericsnow | natefinch: given that we now have --resources (like deploy), we should follow suit | 16:32 |
| natefinch | ericsnow: ok, that's easy enough (and in fact I've already done that part). The talk about hooking into the same machinery as resource poller threw me off | 16:32 |
| natefinch | ericsnow: I'm worried that this will break if you upgrade using the GUI, though | 16:33 |
| ericsnow | natefinch: yeah, this was before --resources | 16:33 |
| ericsnow | natefinch: we have the same problem with deploy though, no? | 16:33 |
| natefinch | ericsnow: then we should fix it for both, right? :) | 16:35 |
| natefinch | ericsnow: I was thinking of just adding a charmstore.ListResources and Resources.SetCharmStoreResources in the state code that does deploy and upgrade-charm | 16:36 |
| natefinch | ericsnow: (for charmstore charms) | 16:36 |
| ericsnow | natefinch: if I recall correctly, for resources we chose to follow the precedent of charm handling for deploy | 16:37 |
| ericsnow | natefinch: ergo, pull info on client-side | 16:38 |
| ericsnow | (from charm store) | 16:39 |
| natefinch | ok.. maybe we can discuss with katherine when she gets back later... we obviously need clientside support for --resources, but it would be nice to also have serverside support for clients that don't do that. | 16:40 |
| ericsnow | natefinch: k, though I expect we'll punt on it for 2.0 :) | 16:43 |
| voidspace | frobware: dimitern: note that Jay is out today and the networking hangout is not on (according to the calendar anyway) | 16:50 |
| frobware | voidspace: ack | 16:51 |
| voidspace | frobware: I've completed my self review (written it anyway) | 16:52 |
| voidspace | frobware: would you like to see it and comment before I submit it, or shall I just submit? | 16:52 |
| natefinch | katco: let ericsnow and I know when you're back. We need to discuss some scope issues around my current task | 18:34 |
| natefinch | ericsnow: I was going to skip uploading metadata for resources whose revision hasn't changed... but that requires an extra round trip to the charmstore... do you think it's worth it? | 19:00 |
| ericsnow | natefinch: nope | 19:01 |
| natefinch | ericsnow: well, good :) | 19:05 |
| katco | natefinch: ericsnow: o/ | 19:35 |
| natefinch | katco, ericsnow: moonstone? Just want to clarify some questions | 19:36 |
| katco | natefinch: sure | 19:36 |
| katco | natefinch: standup | 21:31 |
| cmars` | should i be able to bootstrap lxd on xenial now, with juju built from master? | 21:35 |
| rick_h__ | cmars`: Makyo mentioned that he got it running today | 21:36 |
| Makyo | Wellll. | 21:36 |
| Makyo | It wiped out my /etc/sudoers and now I can't do anything. | 21:36 |
| rick_h__ | ohhh | 21:36 |
| cmars` | what?!! that sounds bad. for me, it seems to hang during bootstrap, and i wondered if anyone else had seen it | 21:37 |
| cmars` | hangs after this: https://paste.ubuntu.com/15247197/ | 21:37 |
| rick_h__ | rumor is master + lxd stable ppa is supposed to work? | 21:37 |
| Makyo | cmars`: same problem, then times out after 10 minutes | 21:37 |
| cmars` | which is weird, i can lxc exec into the container and it's just run cloud-init | 21:37 |
| cmars` | Makyo: you're more patient than me :) | 21:37 |
| cmars` | but good to know | 21:38 |
| cmars` | Makyo: using lxd with zfs? | 21:38 |
| cmars` | i almost wondered if it was so fast, we hit a race? :) | 21:38 |
| Makyo | cmars`: ext4 | 21:39 |
| Makyo | + encrypted home | 21:39 |
| Makyo | Er... whole disk encryped, I guess. | 21:39 |
| cmars` | Makyo: same here (LVM, ecryptfs), but i'm using the zfs block storage for lxd, just a big file, I think. it really does help -- though i bet it'd be even faster if it was native | 21:40 |
| cmars` | well, i'm going to open a bug then | 21:42 |
| Makyo | I'll add my head | 21:42 |
| rick_h__ | cmars`: that sounds like the image problem that serge is working with Tom Barber on in the list | 22:02 |
| rick_h__ | cmars`: have a chance to poke at this ? https://lists.ubuntu.com/archives/juju/2016-February/006699.html | 22:04 |
| rick_h__ | or Makyo it soudns like? | 22:05 |
| Makyo | Sure | 22:05 |
| mup | Bug #1551440 opened: Can't bootstrap LXD on Xenial <juju-core:New> <https://launchpad.net/bugs/1551440> | 22:09 |
| cmars` | rick_h__: yep, i think that explains it | 22:12 |
| cmars` | thanks | 22:12 |
| mup | Bug #1551440 changed: Can't bootstrap LXD on Xenial <juju-core:New> <https://launchpad.net/bugs/1551440> | 22:18 |
| ericsnow | katco: FYI, the new cards are up | 22:48 |
| katco | ericsnow: tyvm | 22:48 |
| Makyo | rick_h__: cmars` the problem I ran into with sudoers was due to permissions installing lxd images. Disregard it. | 23:56 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!