[09:45] <jamespage> gnuoy, can I get a review of https://code.launchpad.net/~james-page/charm-helpers/handle-called-process-exception-for-git/+merge/283583 ?
[09:45] <gnuoy> sure
[09:45] <jamespage> that's breaking odl-controller on a ch resync right now
[09:46] <gnuoy> jamespage, +1
[09:47] <jamespage> gnuoy, ta
[11:01] <philip_stoev> Hello. What would be the canonical way to determine that a given host is the first one in a set of peers within the install() hook. That is, as juju starts  N nodes concurrently, how can the install() hook be different for the first of those nodes ?
[11:20] <D4RKS1D3> Hi jamespage , I am trying to install odl, but always fail, could you help me?, thanks
[11:21] <jamespage> D4RKS1D3, can you check /var/log/juju/unit-odl-controller-0.log for an error pelase
[11:34] <D4RKS1D3> jamespage, this is my configfile http://paste.ubuntu.com/14597039/ and the error in unit-odl-controller is this. http://paste.ubuntu.com/14597058/
[11:34] <D4RKS1D3> Thanks for help me
[11:35] <jamespage> D4RKS1D3, the install-url is not accessible
[11:35] <jamespage> 2016-01-22 11:30:29 INFO install charmhelpers.fetch.UnhandledSource: No handler found for source https://nexus.opendaylight.org/content/groups/public/org/opendaylight/integration/distribution-karaf/0.3.3-Lithium-SR3/distribution-karaf-0.3.3-Lithium-SR3.tar.gz
[11:35] <jamespage> wait
[11:35] <jamespage> actually
[11:35] <D4RKS1D3> but this link works
[11:36] <jamespage> D4RKS1D3, where are you getting your charm from?
[11:36] <jamespage> I just fixed this bug this morning
[11:36] <D4RKS1D3> https://jujucharms.com/u/sdn-charmers/odl-controller/trusty/8
[11:36] <jamespage> D4RKS1D3, oh please don't use that one
[11:36] <jamespage> D4RKS1D3, that's old...
[11:37] <D4RKS1D3> Could you send me the link of the new charm?
[11:37] <jamespage> yes - one second
[11:37] <D4RKS1D3> Thanks
[11:38] <jamespage> D4RKS1D3, https://jujucharms.com/u/openstack-charmers-next/odl-controller/trusty
[11:38] <jamespage> thats the latest development goodness
[11:38] <D4RKS1D3> Thanks jamespage
[11:38] <D4RKS1D3> i am retry
[11:38] <jamespage> I have another branch in flight with some other features, but its not ready to land just yet
[11:39] <D4RKS1D3> Okey, thanks for help me
[12:58] <D4RKS1D3> jamespage, sorry for disturb, now i have a crc problem http://paste.ubuntu.com/14597388/
[12:58] <D4RKS1D3> this is the same error i received with the obsolet charm
[12:59] <D4RKS1D3> you know how to solved it?
[13:09] <icey> is it possible for a stop hook to be called in a context besides the destruction of the unit?
[13:31] <icey> can somebody help me with testing an action? my python fu is not strong enough apparently
[13:56] <jamespage> D4RKS1D3, that would indicate that the archive you are downloading is corrupt - are you going via a proxy?
[13:56] <jamespage> it might have a bad copy
[14:14] <nottrobin> would anyone have any idea why my juju might not be honouring $JUJU_REPOSITORY? http://pastebin.ubuntu.com/14597757/
[14:14] <nottrobin> oh never mind, I hadn't `export`ed it
[14:27] <D4RKS1D3> yes jamespage
[14:28] <D4RKS1D3> We are behind to a proxy
[14:28] <D4RKS1D3> but is a transparent proxy
[15:43] <icey> can anybody provide an example charm that tests actions? I've looked through a few of the openstack charms and, while they do have actions defined, they have no tests that perpform those actions
[15:44] <icey> ah, looks like swift-proxy actually tests actions
[15:52] <lazypower> icey : your findings on the topic would make an excellent blog post
[15:52] <icey> agreed lazypower, may take some time this afternoon to write up about adding actions with tests to a charm :)
[15:53] <icey> if I get to that, I'll send you a URL
[15:53] <icey> have a couple of posts to write now, layer charm being one :)
[15:53] <lazypower> \o/
[15:53] <lazypower> roll that beautiful blog footage icey
[15:53] <icey> haha lazypower
[16:35] <cory_fu_> jose: Hey, you around?
[16:58] <bdx> anyone else having issues with adding the lxd stable repo in xenial?
[17:00] <bdx> I'm hitting this: https://github.com/juju/docs/issues/820, I've already pinged the lxcontainers about this, just thought I would post here too ..
[17:20] <jose> cory_fu_: yes, what's up?
[17:22] <cory_fu_> jose: We were doing RQ and admcleod1 wanted to discuss your comment on https://code.launchpad.net/~talligent/charms/trusty/openbook/trunk/+merge/280525 but he went ahead and added his own comment because he had to EOD
[17:23] <cory_fu_> jose: The store seems to accept any tags, not just the ones on the list, though of course consistency is good
[17:23] <cory_fu_> And we weren't sure how big of a deal the literal mdash was
[17:23] <cory_fu_> Again, the charm store seems to render them ok
[17:24] <jose> hmm. from the wording on the docs it didn't seem like it and I didn't want to break anything. preferred to be safe than sorry
[17:25] <cory_fu_> Yeah, I agree that the wording on the docs implies that you should *only* use those tags, but that seems overly restrictive to me, and looking at https://jujucharms.com/u/talligent/openbook it seems to work ok
[17:25] <jose> hmmk
[17:25] <jose> thanks for letting me know
[17:26] <cory_fu_> We were leaning toward those two items being worth addressing, but not blocking the MP, but your +/-1 has more weight than admcleod1's since you're a ~charmer.  ;)
[18:16]  * lazypower snickers
[18:17] <lazypower> cory_fu_   - you sir, are awarded 15 internet points
[18:54] <bladernr_> Hey, can you guys point me to some documentation somewhere on how to bootstrap into a container locally BUT deploy services to metal elsewhere?  Basically, I want to bootstrap into an LXC container on a MAAS server, and then use MAAS to deploy nodes w/ services on it.
[18:55] <rick_h_> bladernr_: manual provider is all I can think of. We don't have cross provider in Juju currently
[18:59] <bdx> core, dev, charmers: whats up with this ---> https://bugs.launchpad.net/charm-helpers/+bug/1534819
[18:59] <mup> Bug #1534819: FetchHandler charmhelpers.fetch.giturl.GitUrlFetchHandler not found <Charm Helpers:New> <https://launchpad.net/bugs/1534819>
[19:13] <icey> lazypower: https://chrismacnaughton.com/blog/2016/01/22/adding-actions-to-a-juju-charm/
[19:13] <lazypower> Nice!
[19:15] <icey> lazypower: just for you :)
[19:15] <lazypower> will syndicate after daily :)
[19:19] <icey> syndicating on insights.ubuntu.com?
[19:27] <lazypower> icey - i dont have that level of authority
[19:27] <lazypower> but i'll tweet it out :)
[19:27] <icey> lazypower: apparently I don't either :-P
[19:27] <lazypower> icey do you have a twitter handle?
[19:28] <icey> https://twitter.com/ChrisMacN
[19:50] <arosales> bdx hello
[19:50] <arosales> bdx did you get past the xenial lxd issue -- thanks for updating the docs for all btw
[19:51] <arosales> bdx: re your bug 1534819 marcoceppi looks to be the author there and is currently at scale conf, but I am sure he will get this ping and comment in the bug when he is back at a computer
[19:51] <mup> Bug #1534819: FetchHandler charmhelpers.fetch.giturl.GitUrlFetchHandler not found <Charm Helpers:New> <https://launchpad.net/bugs/1534819>
[19:51] <arosales> thanks for submitting it. :-)
[19:56] <bdx> arosales: no, I haven't been able to find a way around it, other than grabbing the source from github and building locally
[19:58] <bdx> arosales: totally, thanks
[20:01] <arosales> bdx was that in reference to the lxd/xenial issue or the charm helper fetch issue?
[20:02] <bdx> arosales: the lxd issue ... I've got it figured out now
[20:02] <arosales> bdx cool, so just the charm helper fetch -- gotcha
[20:03] <arosales> marcoceppi: should catch that when he gets back in front of a computer thanks for logging it
[20:03] <bdx> perfect, thanks!
[21:39] <lazypower> > build: The top level layer expects a valid layer.yaml file  - is there ever a time when building that you wont have a layer.yaml file? as thats pretty much the map to the world of what you're trying to do.
[21:59] <cory_fu_> lazypower: That message should probably be changed to suggest that you're probably not building in the right directory or are missing an arg or something
[22:01] <lazypower> cory_fu_ yeah, it surprised me it was yellow, and didnt halt execution. Not being in the TLD makes sense why it would yellow and attempt to continue
[22:01] <lazypower> yellow = warn in my  mind.
[22:02] <cory_fu> ORLY, it wasn't fatal?  It definitely should be.
[22:02] <cory_fu> Though I could maybe see having it check up a dir or two for a layer.yaml
[22:04] <cory_fu> lazypower: Also, I think the "top level layer" bit is misleading and confusing.  It should just say something like, "Can't find layer.yaml; are you building from the correct directory?"
[22:18] <lazypower> heh yeah, i dropped into charmbox cory_fu and promptly started building a charm of my $HOME
[22:18] <cory_fu> ha
[22:19] <lazypower> it may have been still checking / and/or /home for layer.yaml when i nuked the process + container
[23:03] <tych0> lazypower: hi, i'm going to flip the script here and ask you a question (although you don't have to know the answer :)
[23:03] <lazypower> tych0 nice
[23:03] <tych0> but suppose i wanted to write a charm. i saw a lightning talk recently (don't remember where) that someone had implemented a thing where you could just put in the charm's config what series it was for, vs. having to have a trusty/ and xenial/ version of everything
[23:04] <tych0> is there some docs about where to use that feature?
[23:04] <tych0> or did i completely misunderstand the lightning talk?
[23:04] <lazypower> ah series in config
[23:04] <lazypower> nope, thats a new thing :D
[23:05] <lazypower> *series in metadata
[23:05] <jose> lazypower: ping
[23:05] <lazypower> jose: pong
[23:05] <tych0> lazypower: a new thing in that i'm crazy and it doesn't exist? or that i have to build from source? (i don't mind using a source build so long as i can figure out which config bits to put in)
[23:05] <jose> lazypower: hey, Matt tells me you have docs for layers but I can't find them on /docs, do you by chance have a link handy?
[23:06] <lazypower> jose jujucharms.com/docs/devel
[23:06] <jose> ah
[23:06] <jose> gotcha
[23:06] <jose> thanks
[23:08] <lazypower> np :)
[23:08] <lazypower> jose actually - the front page of the getting started guide tours you through layers - https://jujucharms.com/docs/devel/developer-getting-started
[23:09] <jose> just stumbled upon that one, thank you!
[23:09] <jose> I guess it's time to rewrite the owncloud charm to a layered one
[23:10] <lazypower> You'll enjoy it :)
[23:10] <lazypower> are you going to do a bash or a python layer jose?
[23:11] <lazypower> tych0 i'm looking btw - 1 sec
[23:11] <jose> lazypower: not even sure how these work, so I'm reading a bit first. I'd be more inclined to bash, but if I can do python I'll do it.
[23:11] <tych0> lazypower: cool, thanks, no worries
[23:11] <jose> I think the fact that the current charm is in bash makes it easier to port
[23:12] <lazypower> tych0 this is in 2.0-alpha1
[23:12] <lazypower> so its in -devel ppa
[23:13] <lazypower> tych0 https://lists.ubuntu.com/archives/juju/2016-January/006365.html if you want the release notes
[23:14] <lazypower> > Juju 2.0's new features and behaviours will confuse older Juju clients. - and that explains about the last 2 hours of my day
[23:14] <lazypower> whoops :P
[23:14] <tych0> :)
[23:14] <tych0> yeah, i was hitting that earlier today as well
[23:14] <lazypower> bindmount $JUJU_HOME in a container running 2.0
[23:15] <lazypower> then drop back in my native env w/ stable and it gets weeeeiiirrrdddd
[23:16] <tych0> ah, multi series charms
[23:16] <tych0> cool
[23:20] <tych0> lazypower: ok, here's another juju noob question. is there a way to alias machines somehow? so i can do juju ssh some-machine instead of juju ssh 1?
[23:20] <lazypower> only if there's a service on it
[23:20] <tych0> yeah, i think there will be
[23:20] <lazypower> juju deploy ubuntu/1
[23:21] <lazypower> s/deploy/ssh/
[23:21] <tych0> right, ok. but if all of the machines have the same service, it's the same
[23:21] <lazypower> each unit has an id, that is serially assigned
[23:21] <lazypower> juju ssh ubuntu/12
[23:22] <lazypower> but no, without a charm deployed on the machine, there is no other alias than the machine id
[23:22] <lazypower> :(
[23:23] <lazypower> jose in here please :)
[23:23] <tych0> ok, cool, np :)
[23:24] <jose> let me copy and paste
 so, I don't get it. I need to write an owncloud charm and include that alongside the http/mysql/basic layers?
[23:25] <lazypower> Good question. So you've got an existing owncloud charm right? Recall how you had to stand up apache, setup php, all that fun business befor eyou could even start modelling owncloud?
[23:25] <jose> eeeh not actually. I just did another iteration
[23:25] <jose> I'll have a read at the charm code first
[23:25] <lazypower> with layers you are correct, you pick up the HTTP interface for free, the Apache-PHP layer, and write your new layer which sits nicely on top of all that.
[23:26] <lazypower> the overall code of your charm will slim down to ~ 3 files, and maintenance becomes easier for you :)
[23:26] <jose> hmmk
[23:43] <jose> lazypower: ok, so I think I've got the basics. I'm gonna take a further look later in the night, need to run!
[23:43] <jose> I hope to have it done by later though
[23:44] <lazypower> cheers jose  o/