/srv/irclogs.ubuntu.com/2017/08/30/#juju-dev.txt

wallyworldaxw: hml: babbageclunk: burton-aus: i'll be right back00:34
babbageclunkwallyworld: aw man, I didn't see that you'd requested the review on GH - I guess that's close enough to voluntelling. I'll have a look this afternoon once I get charms uploading.00:56
wallyworldbabbageclunk: no worries, you are busy, totally understand01:05
thumperFARK02:06
anastasiamacthumper: ?02:11
thumperjust trying to look at how mongo counts records in a collection02:17
thumperit is non-trivial02:17
babbageclunkthumper: Can we use stats instead of counting? Might be accurate enough and much faster.02:32
thumperwhat stats?02:32
thumperI have a theory on the count02:32
babbageclunkdb.<collection>.stats()02:32
thumperbut need access to a big controller to test02:33
babbageclunkhttps://docs.mongodb.com/manual/reference/method/db.collection.stats/02:33
thumperbabbageclunk: you would think that db.coll.find().count() would use that02:33
thumperbut perhaps it doesn't02:33
thumpercan we get access to the stats through mgo?02:34
babbageclunknot sure02:34
babbageclunkmmm, toasted sandwich for lunch02:34
wallyworldaxw: if you have a chance, here's a PR for review. sadly it doesn't reflect 2 file renames so counts the full contents towards the +/- count :-( https://github.com/juju/juju/pull/780802:35
thumpervar stats bson.D02:35
thumpersession.DB("mydb").Run(bson.D{{"collStats", "mycollection"}}, &stats)02:35
thumperfmt.Println("Stats:", stats)02:35
thumperso... maybe02:36
axwwallyworld: ok, looking02:38
wallyworldta02:38
axwwallyworld: is relationnetworks.go otherwise unchanged?02:39
wallyworldaxw: sadly not - there's some tweaks to accommodate the egress stuff - same core structs but with a direction attribute - "ingress" or "egress"02:40
wallyworldpita the renames aren't better handled02:40
wallyworldreviewboard did it better02:40
axwwallyworld: perhaps do the rename and change in separate commits next time. anyway, not too big, reviewing...02:42
wallyworldthat would have worked, yeah02:42
axwwallyworld: looks good02:49
wallyworldtyvm02:49
thumperanyone know what needs to be done to be able to run the mgo tests?03:00
babbageclunkthumper: I've never got them running locally, but I think I had them running in travis against my github fork03:25
babbageclunkthumper: that was pretty straightforward to set up03:35
babbageclunkwallyworld: approved03:57
wallyworldbabbageclunk: yay, ty03:57
babbageclunkaxw: just realised I need something from 2.2.3 in the upgrade juju2 tree (client side of the machine sanity check) - do you think I should just spot patch that in from 2.2.3, or update the tree to get it?05:07
babbageclunkaxw: While typing that up I think I decided, I'll just update that client.05:07
babbageclunkaxw: thanks for the help!05:08
axwbabbageclunk: hah :)  FWIW I was going to say the same05:47
babbageclunkha, lucky!05:47
babbageclunkaxw: Can you take a look at https://github.com/juju/1.25-upgrade/pull/20 please?05:59
axwbabbageclunk: ok. just finishing up a PR, then will take a look05:59
babbageclunkaxw: thanks - no rush, I'm close to end of day so I'll look at comments tomorrow.06:00
axwbabbageclunk: okey dokey06:00
=== frankban|afk is now known as frankban
axwjam: when you're free, can you please take a look at https://github.com/juju/juju/pull/7803?06:29
wallyworldjam: wpk: you free now for a HO? or soon?10:35
jamwallyworld: I was just about to make coffee and then I'm available, i'm not sure about wkp10:36
jamwpk10:36
wallyworldok, just ping whenever10:36
jamwallyworld: is it worth just you and I meeting? I feel like we're mostly in sync10:41
wallyworldjam: we are, we can do it again tomorrow with everyone10:42
jamI'm off tomorrow, but maybe I'll be around the house (local 'vacation')10:42
jamIts a national holiday, vs a planned vacation10:42
wallyworldor it can wait. we just need to ensure we're fully synced up and plan the next most important bit to do for nextwork-get10:43
wpkwallyworld: jam: sorry, I am now if you're available11:19
wallyworldi can be in 1011:20
wpkk11:20
wallyworldwpk: jam: i am free now if you guys are11:35
jamwallyworld: we're on the hangout that wpk linked on the other channel11:35
=== petevg_ is now known as petevg
=== frankban is now known as frankban|afk
hmlis there a way to get juju upgrade-juju —build-agent to work on a model other than controller?20:52
thumperhml: no20:55
thumperhml: you need to upgrade the controller first20:56
thumperthen specify the controller version for the hosted model20:56
thumperthe hosted model then gets the same version as the controller20:56
hmlthumper: how do i do the 2nd bit “specify the controller version for the hosted model”?20:58
thumperhml: ok, lets say you have upgraded the controller20:58
thumperand do a status on the controller20:58
thumperand it says version 2.2.3.2 say20:58
thumperyou then go20:58
thumperjuju upgrade-juju other-model --agent-version=2.2.3.220:58
thumperprobably a -m in there too20:59
hmlthumper: okay, i’ll give it a shot20:59
bdxI'm experiencing some odd behavior using JAAS + AWS + network spaces22:24
thumperbdx: what sort of odd behaviour?22:25
bdxat a high level, things work (charms deploy successfully) if deployed in the default vpc, with no juju spaces defined22:25
bdxon the other hand, if I create a model in the non default vpc, add some spaces, and deploy the exact same bundle except to the defined space I get odd failures throughout22:28
bdxgrabbing some material to support this omp22:28
bdxit might be specific to the charm, in this case, elasticsearch22:30
bdxok22:36
bdxthis is making me feel a bit crazy22:37
bdxbut its entirely reproducable22:37
bdxso22:37
bdxI don't know what to say .... I think it might be a charm specific thing though and not juju or network related ..... I just don't get it22:38
bdxusing upstream elasticsearch in the charmstore (cs:trusty/elasticsearch-19)22:38
bdxwhat happens is elasticsearch will be deployed and running on the machine deployed to the default vpc, and when elasticsearch deployed with a spaces constraint, the process just doesn't exist22:39
bdxall the dirs are there, the binary is ther22:40
bdxthis model https://pastebin.com/NaLcqBFy is configured to a default vpc, no spaces added, and no constraints used22:42
bdxfrom that elasticsearch node, http://paste.ubuntu.com/25434884/22:43
bdx <- `ps aux | grep elasticsearch`22:43
bdxwe can see that elasticsearch is running22:43
bdxnext, a model created with a non-default vpc and spaces added, and all the machines deployed to the spaces22:44
bdxhttp://paste.ubuntu.com/25434893/22:44
bdxhttp://paste.ubuntu.com/25434894/22:44
bdxheres the full yaml status http://paste.ubuntu.com/25434903/22:45
bdxand now, same as before, I'll ssh into elasticsearch box and ps aux22:45
bdxhttp://paste.ubuntu.com/25434906/22:46
bdxboom22:46
bdxjava process for elasticsearch exists22:46
bdxodd because the machine has elasticsearch and all the deps (java) installed22:47
bdxlol22:47
bdxI've been ramming my head on this for days now .... just thinking my fork of elasticsearch is borked22:47
bdxlol22:47
bdx^^ important correction s/java process for elasticsearch exists/java process for elasticsearch ceases to exist/22:49
bdxits quite baffling, really22:50
bdxthumper: ^that kind23:02
babbageclunkbdx: can you see logs for elasticsearch? It sounds like it might be trying to start and failing when you have space constraints.23:06
bdxbabbageclunk: I was just about to report back with that23:06
bdxbabbageclunk: the java process appears just for a second then disappears23:07
bdxthe logs are clean though23:08
bdxbecause it looks as if it actually does start23:08
bdxso there is no error being logged or anything23:09
bdxI have this juju log for the failing instance http://paste.ubuntu.com/23:10
bdxwow ... the logs are entirely different23:11
bdxand this log for the working instance 2017-08-30 22:19:45 INFO juju.cmd supercommand.go:63 running jujud [2.2.2 gc go1.8]23:12
bdx2017-08-30 22:19:45 DEBUG juju.cmd supercommand.go:64   args: []string{"/var/lib/juju/tools/unit-elasticsearch-0/jujud", "unit", "--data-dir", "/var/lib/juju", "--unit-name", "elasticsearch/0", "--debug"}23:12
bdx2017-08-30 22:19:45 DEBUG juju.agent agent.go:543 read agent config, format "2.0"23:12
bdx2017-08-30 22:19:45 INFO juju.jujud unit.go:151 unit agent unit-elasticsearch-0 start (2.2.2 [gc])23:12
bdx2017-08-30 22:19:45 DEBUG juju.worker runner.go:319 start "api"23:12
bdxoh no23:12
bdxmy bad - jeeze23:12
bdxand this log for the working instance http://paste.ubuntu.com/25435003/23:13
thumperweird23:13
bdxpossibly one of my models has different logging config23:15
bdxgeh23:16
bdxyep23:16
bdxlogging-config was turned up on the model with spaces/non-working one23:17

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