/srv/irclogs.ubuntu.com/2016/06/15/#juju-dev.txt

menn0thumper: next MM PR: http://reviews.vapour.ws/r/5057/00:19
menn0sorry that it's a bit large00:19
* thumper looks00:23
davecheneythumper: https://github.com/juju/juju/pull/556400:45
davecheney^ pinger fixes from the last two days00:45
davecheneyminus the removal of the recover() in ping.ping00:45
davecheneythat'll live another day00:45
thumperok, I'll look shortly00:47
* thumper afk for a walk00:47
mupBug #1592609 opened: Unit stuck in allocating with juju 1.25.5 <canonical-bootstack> <juju-core:New> <https://launchpad.net/bugs/1592609>00:52
wallyworldaxw: the CloudCredential attributes on BootstrapParams appear unsed in master right now, correct?00:53
axwwallyworld: yeah, one of the issues I found when validating :)00:55
wallyworldaxw: cause restore is broken - i am fixing it by adding cloud and region info to bootstrap params when we restore with -b, but credential info is not at hand00:56
axwwallyworld: doh, sorry00:56
wallyworldaxw: i can propose and land this fix and you can then take alook?00:56
axwwallyworld: sure00:56
wallyworldok, will push when i check tests00:56
axwwallyworld: it's fixed in the validation branch, but I can't land that until the add-model bits are done00:56
axwwallyworld: I can pull it out if it's pressing00:57
wallyworldok, let me propose this and we'll take a view00:57
mupBug #1592613 opened: juju status reports incorrect number of cores for arm64 machines <juju-core:New> <https://launchpad.net/bugs/1592613>01:17
=== natefinch-afk is now known as natefinch
natefinchwallyworld: in the 1:1 when you're ready.01:31
wallyworldbe right there01:31
axwwallyworld: I think I'm going to add a cloud facade anyway, need to be able to determine the cloud type for a controller in order to finalize credentials01:48
axwwe should probably be exposing the credentials schema over the API, rather than relying on the providers, but that will have to come later01:49
wallyworldaxw: ok, otp, will still aim to push a restore pr fix soon as i can01:50
thumperdavecheney: just one question on the PR02:21
=== akhavr1 is now known as akhavr
wallyworldaxw: a quick restore fix http://reviews.vapour.ws/r/5059/02:45
axwwallyworld: responded02:58
wallyworldta02:58
wallyworldaxw: returning *config.Config and jujuclient.BootstrapConfig is no good because BootstrapConfig doesn't contain a Credential struct.  so i needed to cobble together a new struct that had everything03:05
wallyworldmaybe i can rework a bit03:05
axwwallyworld: I think the second option I suggested would work?03:05
axwwallyworld: that would give you enough to construct the *config.Config, and the the names to pass in03:06
wallyworldyeah probs, i guess i was trying to avoid return 2 structs instead of one, but the name of the franken struct does suck03:06
axwwallyworld: I've gtg out for a little while, will take another look when I return03:07
wallyworldnp ty03:08
davecheneythumper: w.Wait() is not a channel03:11
davecheney:(03:11
natefinchthumper: heard you're working on the fslock stuff... anything you need help with?03:28
thumpernatefinch: perhaps when i get to CreateMutexEx :)03:34
thumperthe docs are pretty clear03:34
thumperand I have a win machine here03:35
thumperbut it isn't set up for go03:35
natefinchthumper: setting up for go is pretty easy03:36
davecheneythumper: http://stackoverflow.com/a/233286804:34
davecheney^ name spitballing04:34
davecheneymutex fits our use case04:34
mupBug #1570368 changed: juju commands timeout while a bootstrap is in process <conjure> <juju-core:Expired> <https://launchpad.net/bugs/1570368>04:44
axwwallyworld: sorry was out for longer than expected. LGTM05:04
wallyworldno worries ty05:04
cmarsperrito666, rofl05:59
=== akhavr1 is now known as akhavr
=== Makyo|away is now known as Makyo
axwwallyworld: what incantations do I need to make to register a facade? I've got a RegisterStandardFacade call, updated allfacades, updated the client facadeversions.go...06:55
thumperaxw: got two minutes?06:57
axwthumper: yup?06:57
thumperaxw: priv msg hangout link06:58
axwwallyworld: never mind, I was missing the "restrctedRootNames" bit07:16
wallyworldaxw: ah sorry, had popped out to get coffee, was an emergency07:17
axwno worries07:17
axwwallyworld: do you think it would be reasonable to move authorized-keys out of model config? and have it stored separately in state? we already manage them specially07:52
axwI'd rather like to not see long lines of authorized keys in model config07:52
wallyworldaxw: i think so - a lot of stuff in model config schema only exsits there so we can collect it all up when bootstrapping07:53
axwwallyworld: I've got a new facade for managing creds now, need to add auth and write tests07:54
wallyworldyay07:54
axwwallyworld: just live tested with AWS successfully, specifying a cred that doesn't exist in the controller auto uploads07:54
axwand tells the user07:54
wallyworldawesome07:54
babbageclunkIf I've got a juju model with a lxd container running on it, how can I ssh into the container? The container doesn't have a public address, so I need to ssh from the host machine, but that doesn't have the juju ssh key on it (I think). Is the right thing just to scp the private key to the host machine and ssh from there to ubuntu@<lxd-ip>? Or is there a better way of doing this?08:04
dimiternbabbageclunk: I'd use sshuttle or (if just for a simple test), ssh -L2222:<lxd-ip>:22 <host-ip> and then ssh -i ~/.local/share/juju/ssh/juju_id_rsa ubuntu@localhost -p 222208:07
babbageclunkdimitern: Oh, I keep forgetting about sshuttle! Thanks dimitern. Copying the key around definitely felt wrong.08:08
dimiternbabbageclunk: :) it should08:08
babbageclunkfwereade_: ping?09:27
fwereade_babbageclunk, heyhey09:32
babbageclunkfwereade_: So, about workload version - I think you're right it should be done at unit level.09:34
babbageclunkfwereade_: Should I just keep doing that now? I don't really follow what Rick was suggesting - I'm not very familiar with resources. And I'm not very clear on what jam was suggesting - the status stuff is a bit more involved and I'm not sure how to add version info into it.09:37
babbageclunkfwereade_: So I've t09:37
babbageclunkfwereade_: oops. I've parked my application.SetWorkloadVersion branch and done a unit.SetWorkloadVersion branch instead, but I should probably understand rick_h_ and jam's suggestions better before going too far with it. I didn't see a response from thumper - have you heard anything from him?09:39
fwereade_babbageclunk, sorry, processing09:41
babbageclunkfwereade_: :)09:41
axwwallyworld: problem. we've renamed the "--service" flag to "--application" in the status-set hook tool. that's going to break a bunch of charms09:45
axwwallyworld: I think we should probably alias that.09:45
wallyworldaxw: yep, fair point09:45
axwI'll file a bug09:45
axwjust tried deploying cassandra, and it blew up09:45
wallyworldit may be a blocker for brta909:45
wallyworldaxw: i had to tweak the dummy provider to not break with no controller id on Open(), running more tests now, can look at bug after that09:46
babbageclunkaxw, wallyworld: minor but related thing - I see a traceback with "KeyError: 'services'" when tab completing in the juju command (specifically juju scp). Already known? Should I raise a bug?09:47
wallyworldbabbageclunk: not known to me, raise abug and the tab completion fairies will need to fix it09:48
babbageclunkwallyworld: ok cool09:48
fwereade_babbageclunk, based on conversation, I'm not entirely certain I understand what problem we're solving; added another comment but I think I too need guidance from rick_h_ and/or jam10:02
babbageclunkwallyworld: I dug a bit more, looks like it was already fixed, I just hadn't installed it since the change.10:02
wallyworldah cool10:02
mupBug #1592733 opened: rename of status-set --service flag to --application breaks charms <juju-core:Triaged> <https://launchpad.net/bugs/1592733>10:03
jambabbageclunk: I'm heading back to the hangout now. if fwereade_ wants to join us that would be fine with me10:04
babbageclunkfwereade_: joooooooooin ussssssssss10:04
* dimitern needs to step out for ~30m10:10
wallyworldaxw: http://reviews.vapour.ws/r/5062/10:20
jambabbageclunk: you mentioned in your email a while back that "juju deploy foo --to lxd" didn't work11:21
jamdid you try "juju deploy foo --to lxd:" ?11:21
jamor is the point of that email "why do I need to type the colon" ?11:21
babbageclunkjam: yeah, I did - that didn't work.11:22
dimiternjam: with the colon it fails11:22
dimiternsomewhat surprising.11:22
babbageclunkjam: The point of the email was actually "this works now" - so maybe it didn't work!11:22
babbageclunkjam: (The email I mean.)11:23
jamdimitern: are you interested in chatting soon?11:42
dimiternjam: let's do it now if you can?11:42
jamk, just need a quick stop and brt, see you in standup11:43
dimiternok11:43
babbageclunkfwereade_: just to check again having familiarised myself with the status code - you're saying store workload version as a status but with a different global key to the unit global key (probably the unit global key with #wlversion in it somewhere). Sound right?11:47
fwereade_babbageclunk, yeah, sgtm11:48
babbageclunkfwereade_: <thumbs-up emoji>11:48
fwereade_babbageclunk, cheers11:48
fwereade_babbageclunk, #<something> tacked on the end, anyway: a disambiguating namespace like '#sat#workload-version' might be a good idea (sat[ellite], bad name; still, dyswim?)11:51
babbageclunkfwereade_: yeah, that makes sense.11:51
fwereade_babbageclunk, ta11:51
wallyworlddimitern: i'd love a small review to allow old charms to work with new set-status for beta 9 http://reviews.vapour.ws/r/5062/12:08
voidspacedimitern: ping12:18
voidspacedimitern: in order to validate LinkLayerDevices I need to validate ParentName references a real device on a real machine12:18
voidspacedimitern: which means I need to parse ParentName as a global key (potentially)12:19
voidspacedimitern: do you think I should duplicate or move (or make public) the parsing code?12:19
voidspacedimitern: core/description doesn't yet depend on state - so making it public and adding a dependency seems like a bad idea12:20
voidspacedimitern: it's only string parsing, and not much code, so duplicating it seems best12:20
dimiternvoidspace: pong; sorry, otp so will respond as I can12:29
voidspacedimitern: ok12:29
voidspacedimitern: I've duplicated for the moment - only a few lines of code12:29
dimiternvoidspace: I don't think we should export the parsing code, as it's an implementation detail12:30
dimiternvoidspace: and as fwereade_ correctly pointed out, ParentName being a global key should have never be allowed to escape the state package12:30
voidspacedimitern: right12:31
voidspacedimitern: I still need to parse it for the moment, so I'll duplicate the code until we solve the problem (add ParentMachineID maybe)12:32
dimiternvoidspace: what would've been better is to have a ParentName() always returning plain names, and add a ParentMachineID() to return a non-empty id in the case currently handled with ParentName as global key12:32
dimiternvoidspace: +112:32
voidspace:-)12:32
voidspacethose global keys are pretty ugly12:32
mupBug #1592811 opened: 2.0 beta8: networking broken for dense deployment and vsphere as provider <oil> <vsphere> <juju-core:New> <https://launchpad.net/bugs/1592811>13:01
wallyworldfwereade_: i'd love a small review for beta 9 http://reviews.vapour.ws/r/5062/13:05
katcofwereade_: could also use a follow-up on http://reviews.vapour.ws/r/5006/ :)13:10
* katco disappears again for a bit13:10
fwereade_ha13:43
fwereade_I had not looked at irc for a while, and had somehow psychically gone to look at both those reviews :)13:43
fwereade_wallyworld, lgtm; katco, looking13:44
wallyworldty13:44
frankbanwallyworld: hey, do you know about any recent change in API server facades that wuld break the GUI? like we are getting "unknown object type "Client"13:50
rick_h_gsamfira: ping, around? We've got a user in #juju working with windows and asking about example windows subordinates and such13:51
rick_h_gsamfira: curious if you'd be interested in asking someone to chat with him and might have some samples or fodder to help the user along?13:51
wallyworldfrankban: um, some of the serialisation names for the params was changed but that shouldn't affect the ability to find a facade. what facade version are you using for client?13:51
frankbanwallyworld: no version sent, so 013:52
frankbanwallyworld: ah maybe that's the issue13:52
wallyworldshould be 1 i think13:52
perrito666fwereade_: could you go to your regular nickname so I dont have to open another window? :p13:52
frankbanwallyworld: yeah Login returns 113:53
frankbanwallyworld: so the lower-cased-api-fields-geddon has been merged? will be in beta9?13:53
wallyworldfrankban: yeah. i hope it won't affect too much13:54
alexisb_rick_h_, mail might be good or bogdanteleaga may be able ot help13:57
rick_h_alexisb_: rgr ty13:57
mupBug #1592832 opened: enable-ha embeds ModelCommand but should be controller-specific <juju-core:New> <https://launchpad.net/bugs/1592832>14:01
mupBug #1592837 opened: juju upgrade-gui is a model command but operates on controllers only <juju-core:New> <https://launchpad.net/bugs/1592837>14:01
mupBug #1592832 changed: enable-ha embeds ModelCommand but should be controller-specific <juju-core:New> <https://launchpad.net/bugs/1592832>14:04
mupBug #1592837 changed: juju upgrade-gui is a model command but operates on controllers only <juju-core:New> <https://launchpad.net/bugs/1592837>14:04
* frobware discovers the tp-link switch CLI does NOT save the config by default. Grrr.14:04
mupBug #1592832 opened: enable-ha embeds ModelCommand but should be controller-specific <juju-core:New> <https://launchpad.net/bugs/1592832>14:13
mupBug #1592837 opened: juju upgrade-gui is a model command but operates on controllers only <juju-core:New> <https://launchpad.net/bugs/1592837>14:13
=== fwereade_ is now known as fwereade
fwereadeperrito666, sorrt14:15
frankbanwallyworld: we'll fix the gui for that change, thanks for confirming. fyi, the embedded gui will be broken in beta914:27
wallyworldthat's ok, we'll have a beta 10 next week14:28
frankbanwallyworld: cool14:30
dimiternalexisb_: ping15:03
alexisb_dimitern, heya15:05
alexisb_I am on the hangout15:05
dimiternalexisb_: sorry, I was chatting with frobware just now - omw15:07
mupBug #1592872 opened: juju status not showing correct output when specifying a sepcific service/application <juju-core:New> <https://launchpad.net/bugs/1592872>15:43
fwereadekatco, sorry, wall of issues, but I think mostly very minor16:00
katcofwereade: tal, and no worries16:01
katcofwereade: ta for the review16:01
fwereadekatco, np :)16:01
mupBug #1592887 opened: juju destroy-service deletes openstack volumes <juju-core:New> <https://launchpad.net/bugs/1592887>16:25
perrito666this channel is unusually slient today19:18
katcoperrito666: oh way to ruin it perrito666. jees... we had a streak going.19:19
katcoperrito666: this is why we can't have nice quiet things.19:20
perrito666I am south american, we are loud19:20
alexisb_katco, perrito666: can I get one of you to give a second +1 on this revert so we can merge please: http://reviews.vapour.ws/r/5066/19:26
perrito666alexisb_: looking19:26
katcoalexisb_: ditto19:26
katcoalexisb_: cherylj: i don't understand the commit message... we are reversing changes made in commit Y by reverting commit X?19:30
perrito666alexisb_: looks like a revert :) and gtm, but why is this revert?19:30
perrito666ie, code looks good dunno about the reason19:30
alexisb_perrito666, there were facade changes without version bump and fair warning to api users19:31
alexisb_everyone is horrible broken as a result19:31
perrito666do we fair warn in master?19:31
alexisb_perrito666, yes we should always update those we know are using our api's before breaking changes like this19:32
alexisb_we did not in this case, and we also should always keep to api versioning19:32
perrito666alexisb_: lgtm, need an official stamp?19:32
perrito666agree re api vers19:33
alexisb_perrito666, yes please19:33
perrito666done19:34
alexisb_katco, not sure why the lxd bug fix is mentioned in the commit message, cheryljwhat have to provide clarity, my guess is that there were revisions to that bug fix due to it using an updated facade19:36
katcoalexisb_: ok; pursuant to our recent discussion about commit history, it might be worth clarifying19:37
alexisb_:)19:37
alexisb_agreed19:37
alexisb_thanks for looking katco and perrito666, I will follow-up with cherylj when she is back from lunch19:38
katcoalexisb_: i know she's busy, and this was probably done in 5m between people bothering her ;)19:38
alexisb_yes yes it was19:38
alexisb_and it is not like she is running an induction sprint atm19:39
katcoalexisb_: yeah, seriously. laziest lady i know...19:40
cheryljkatco: The commit message was just what git spit out.  I think it's just saying that it's reverting the change applied on top of that lxd commit19:40
cheryljthat lxd commit was the last merge before the one I reverted19:40
katcocherylj: ah that makes sense19:41
katcocherylj: probably not worth changing if it's idiomatic git19:41
cheryljok19:41
katcocherylj: in that case, i just need to update my understanding :)19:41
cheryljheh19:41
alexisb_cherylj, you are good to merge with bz2 and perrito666 +119:44
cheryljok, merging19:45
alexisb_thumper, when you have a minute I could use a moment of your time20:20
thumperalexisb_: I'm free for the next 8 minutes :)20:21
alexisb_good enough20:21
alexisb_meet you in our 1x1 HO20:21
katcodoes anyone have an opinion on this?20:25
katcowe only log information about API requests if the loggo level is <= loggo.DEBUG20:25
katcobut we log ALL API connection open/close regardless of logging level20:25
thumperyes, I have opinions20:25
katcothumper: the right man for the job!20:26
katcoit would make my life much easier if we would consistently log API information (i.e. joins/parts as well as misc. API info) rather than treating joins/parts as something different20:26
katcois there a reason to do so?20:26
thumpersecrets20:27
thumperthey were the reason20:27
thumperthere was no consistent way to remove secrets from the details20:27
thumpersoon we hope there will be when all providers describe config using the more descriptive way20:27
thumperbut until then20:27
thumperthis is what we have20:27
katcothumper: ah... can i discontinue logging joins/parts if the loggo level is <= DEBUG?20:28
thumperjoins/parts?20:28
katcothumper: sorry... connects/disconnects20:28
katcothumper: https://github.com/juju/juju/blob/master/apiserver/apiserver.go#L561-L56720:29
katcothumper: i want to get rid of that and say we either log all API events, or none, depending on the loggo level20:29
thumperI think we should always have the notifier20:31
alexisb_thumper, ping20:32
katcothumper: i seem to remember mark complaining about log spam?20:32
thumperbabbageclunk: with you shortly20:32
babbageclunkthumper: cool cool20:32
thumperbabbageclunk: having many parallel conversations just now20:32
thumperalexisb_: ya?20:32
katcothumper: better throw a fslock in there20:32
thumperkatco: I don't even...20:33
alexisb_thumper, nevermind20:33
thumperwe've logged api calls at debug for so long, if we want to only do that on trace, we should tell people on juju-dev20:33
katcothumper: i'm good with that, as long as it passes your smell check as something sane to do20:34
katcothumper: however it looks like we ALWAYS log requests: https://github.com/juju/juju/blob/master/apiserver/apiserver.go#L541-L54320:35
katcothumper: so, sorry: that's really what i'm asking; can the logging of connects/disconnects safely be tucked away under debug rather than always on?20:36
thumperyeah, don't see why not20:37
katcothumper: you have just made me very happy.20:37
mupBug #1531719 opened: Runaway memory allocation in jujud unit agent <2.0-count> <sts-needs-review> <juju-core:Triaged> <https://launchpad.net/bugs/1531719>20:38
stokachuthumper: how long do you think before your revert makes it into master?20:42
thumperstokachu: it is trying to land now20:43
stokachuthumper: ok cool20:43
mupBug #1592981 opened: LXD and manual provider shouldn't require auth type <juju-core:New> <https://launchpad.net/bugs/1592981>21:08
mupBug #1592987 opened: Cannot bootstrap MAAS: missing CloudRegion not valid <blocker> <bootstrap> <maas-provider> <juju-core:Triaged> <https://launchpad.net/bugs/1592987>21:35
thumper\o/ flock impl works22:12
perrito666\o/22:13
thumpernow on to windows22:14
perrito666have fun22:14
alexisb_wallyworld, ping22:30
wallyworldalexisb_: hey, trying to get in, there's no video link22:31
alexisb_https://hangouts.google.com/hangouts/_/canonical.com/core-leads-call22:31
anastasiamacaxw: wallyworld: m looking at agent config file version bug 157579422:40
mupBug #1575794: Agent config format version should be changed for 2.0 <juju-release-support> <rc1> <tech-debt> <juju-core:Triaged by anastasia-macmood> <https://launchpad.net/bugs/1575794>22:40
wallyworldgreat ty22:41
anastasiamacaxw: wallyworld: m tempted to rename our format-1.18 file to just be format :D and change the variable that puts version number to 2.022:41
anastasiamacis there any repricussion m missing?22:42
wallyworldnot sure, otp, so can't devote brain space to it22:42
axwanastasiamac: should be fine22:42
axwanastasiamac: I'd call it format-2.0, since it may change again22:43
anastasiamacaxw: the problem is that this file has already been updated to contain 2.0 changes. it's no longer just 1.18 :)22:44
axwanastasiamac: that's a problem regardless of the name. and if we don't include the version in the name, people will be *more* likely to change it in incompatible ways without bumping the version22:45
anastasiamacaxw: k. I'll rename and change the variable name and its value, adding comments to not alter contents but creating new file for next format version \o/22:46
=== jcsackett_ is now known as jcsackett
=== meetingology` is now known as meetingology
=== StoneTable is now known as aisrael

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