[00:18] <balloons> sebas5384, hey, finally back again :-)
[00:19] <balloons> glad you got my message earlier and we'll chat tomorrow
[00:42] <sebas5384> hey balloons
[00:43] <sebas5384> np balloons, it happens
[00:43] <sebas5384> :)
[01:06] <lazyPower> tvansteenburgh: https://code.launchpad.net/~lazypower/charm-tools/fix_1389454/+merge/240666
[13:19] <skay> shiny https://jujucharms.com/
[13:19] <wesleymason> Anyone using the openstack provider having trouble bootstrapping today? Looks like a regression in the v1 stream having 1.21-alpha1 in it again (https://bugs.launchpad.net/juju-core/+bug/1367987) and my installed 1.18 borking on it
[13:19] <mup> Bug #1367987: juju 1.18 and 1.20 cannot parse simplestreams containing version "1.21-alpha1" <hs-arm64> <landscape> <ubuntu-engineering> <juju-core:Fix Released by wallyworld> <juju-core 1.20:Won't Fix by axwalk> <juju-release-tools:Fix Released by sinzui> <https://launchpad.net/bugs/1367987>
[16:16] <themonk> lazyPower, hi
[16:17] <lazyPower> hey themonk
[16:18] <themonk> lazyPower, one of may charm has chrooted env so it conflict with lxc container in local but its ok in cloud service
[16:20] <themonk> i want my charm to be pushed in juju charm store, will charm store accept this limitation?
[16:20] <themonk> lazyPower, ^
[16:21] <lazyPower> themonk: you can get 'in the store' in your personal namespace without any fuss - if your charm has a limitation on the local provider it will need to be *clearly* documented in the readme so the reviewer understands this is expected behavior.
[16:21] <lazyPower> themonk: https://juju.ubuntu.com/docs/authors-charm-store.html#name-space-charms
[16:22] <themonk> lazyPower, ok
[16:22] <lazyPower> i did a write up on this as well if the documentation makes you go cross eyed: http://blog.dasroot.net/the-power-of-community-charming/
[17:58] <tvansteenburgh> noodles775: just ran charmguardian on your fire_wall optional branch, all tests pass on AWS
[17:59] <tvansteenburgh> noodles775: i'm about to update jenkins, then i'll kick off a build to run them on the other substrates
[18:37] <lazyPower> wait, noodles775 made ufw optional?
[18:37] <lazyPower> awesome, i implemented that locally lastnight. i should have looked.
[19:33] <noodles775> tvansteenburgh: Excellent, thanks.
[19:35] <noodles775> lazyPower: Yeah, I did. I'm still interested to know why you'd want to switch it off though? (unless it's just for testig locally, but even then, you can `juju run --unit myservice/0 "curl ..."`
[19:35] <lazyPower> local deployments, testing scenarios
[19:36]  * noodles775 nods
[20:07] <themonk> lazyPower, are you there?
[20:08] <lazyPower> themonk: in a meeting
[20:08] <lazyPower> whats up?
[20:09] <themonk> how long it takes a charm review process, in genarel
[20:14] <lazyPower> themonk: depends on a few factors - 1) how ready is your charm for the review so it gets expedited after first touch, 2) how many charms are in the queue before you
[20:15] <lazyPower> themonk: i'll re-iterate, if you puiblish to your namespace, it wont be subject to a ~charmer review, and will be available at the next ingest (which happens ~ every 30 minutes)
[20:16] <lazyPower> themonk: but if you want to due your due dilligence in preparation for ~charmer review - this is the criteria in which we evaluate charms:  https://juju.ubuntu.com/docs/authors-charm-policy.html
[20:19] <themonk> lazyPower, i was reading this doc i have made a check list :)
[20:19] <themonk> lazyPower, thanks :)
[20:21] <lazyPower> no problem
[20:54] <tvansteenburgh> noodles775: http://reports.vapour.ws/charm-tests/charm-bundle-test-5034-results
[20:54] <tvansteenburgh> noodles775: dunno why the timeouts happen, trying to figure that out now
[20:59] <jrwren> what is the correct url for agent-metadata-url for 1.21-alpha2? i had been using https://streams.canonical.com/juju/devel/tools but that is not working
[21:01] <jrwren> http://streams.canonical.com/juju/tools/streams/v2/ ?
[21:01] <tvansteenburgh> jrwren, tools-metadata-url:  https://streams.canonical.com/juju/devel/tools is what i have
[21:01] <jrwren> tvansteenburgh: have you bootstrapped with that today?
[21:02] <tvansteenburgh> yes
[21:02] <jrwren> tvansteenburgh: thanks. now I know its me.
[21:02] <tvansteenburgh> jrwren, note tools vs agent
[21:03] <jrwren> tvansteenburgh: 1.21-alpha2 tells me to use agent- not tools-
[21:03] <tvansteenburgh> hrm, ok
[21:03] <jrwren> i just tried it with tools same fail for me.
[21:04] <tvansteenburgh> oh you're right, tools- was replaced with agent-
[21:20] <tvansteenburgh> jrwren: see sinzui's email from 4 minutes ago (if you haven't yet)
[21:24] <sinzui> tvansteenburgh, jrwren tools-metadata-url was renamed to agents-metadata-url in alpha2...the later will continue to work for as long as we support trusty
[21:25] <sinzui> jrwren, are you using  a public cloud or a private cloud
[21:26] <jose> lazyPower: hey, I had that one locked!
[21:26] <lazyPower> jose: i'm sorry i'm not sorry ;)
[21:26] <jose> :P
[21:36] <noodles775> Thanks tvansteenburgh
[21:38] <jrwren> sinzui: public
[21:41] <sinzui> jrwren, I see the issue, the mirror file is pointing to the official location in the CPC, which lists only stable agents
[21:42] <sinzui> jrwren, the fix is to directly set the agent-metadata-url for the cloud or to switch to alpha2 and set agent-stream
[21:42] <sinzui> jrwren, which approach do you prefer?
[21:42] <jrwren> i'll try alpha3 if it is in dev ppa
[21:43] <sinzui> jrwren, okay, I cam provide the metadata-url for eahc cloud. in the meantime, I will report a bug about the deprecated mirror files. I think we can get those fixes quickly
[21:44] <marcoceppi> jose: lazyPower has a habit of ignoring the lock
[21:44]  * marcoceppi plans on ways to mess with him as a result
[21:44] <jose> I guess I just noticed :P
[21:48] <lazyPower> jose: gonna do it to you again
[21:48] <jose> hey!
[21:48] <lazyPower> just wrapped up looking @ terracotta
[21:48] <jrwren> I think https://launchpad.net/~juju/+archive/ubuntu/devel the description here should be updated for alpha3
[21:55] <jrwren> yay! i can bootstrap