[01:04] how long does it take for a namespaced bundle to show up on my account? [01:04] it's been 3 hours [01:15] stokachu: you may need to file a bug, we had issues last week where bundles weren't getting ingested [01:16] ah ok [01:16] is that jujucharms.com? [01:16] Yep [01:23] stokachu - I am in no way prepared for whats coming in 7 minutes :D [01:23] haha [01:23] we could wing it [01:23] Always do [01:23] the magic is in post anyway ;) [01:23] :D [01:24] https://plus.google.com/hangouts/_/canonical.com/stokesisawizardandweregoingtoshowyouhow [09:39] hi all, i have returned with my question about deploy bundle from juju gui. i have checked it again and my services are not exposed after bundle deploy. is it known issue? === rogpeppe1 is now known as rogpeppe [12:52] hi all [12:53] I pushed some changes to https://code.launchpad.net/~jean-deruelle/charms/trusty/mobicents-restcomm-charm/trunk [12:53] but I don't see the charm updated on https://jujucharms.com/u/jean-deruelle/mobicents-restcomm-charm/trusty/#revisions [12:54] while the changes to https://code.launchpad.net/~jean-deruelle/charms/bundles/mobicents-restcomm-mysql-bundle/bundle [12:54] were taken https://jujucharms.com/u/jean-deruelle/mobicents-restcomm-mysql-bundle/bundle/5/ [12:55] does anyone have any clue on why this may be happenin ? === rcj` is now known as rcj [14:20] tvansteenburgh, morning - quick question for you regards use of specific branches from git repositories in juju-deployer [14:21] I'm trying todo: [14:21] openstack-dashboard: [14:21] branch: https://github.com/openstack-charmers/charm-openstack-dashboard@stable [14:21] but right now that's not working so great - is that the right syntax? [14:23] jamespage: looking... [14:24] tvansteenburgh, http://paste.ubuntu.com/13124372/ [14:25] hi all [14:25] I pushed some changes to https://code.launchpad.net/~jean-deruelle/charms/trusty/mobicents-restcomm-charm/trunk [14:25] but I don't see the charm updated on https://jujucharms.com/u/jean-deruelle/mobicents-restcomm-charm/trusty/#revisions [14:25] while the changes to https://code.launchpad.net/~jean-deruelle/charms/bundles/mobicents-restcomm-mysql-bundle/bundle [14:25] were taken https://jujucharms.com/u/jean-deruelle/mobicents-restcomm-mysql-bundle/bundle/5/ [14:25] does anyone have any clue on why this may be happenin ? [14:28] jamespage: try it with a commit hash [15:03] tvansteenburgh, hmm ok - but I really need to be able to track a branch as it changes [15:03] jamespage: right, i think that would be a new feature. was just curious if it works with a sha [15:08] tvansteenburgh, no cigar with an sha either... [15:10] tvansteenburgh, I think you're correct in that its a new feature [15:10] tvansteenburgh, any thoughts on syntax in the bundle? [15:11] jamespage: there are test cases for the path@rev syntax using both a sha and a tag :/ [15:11] odd [15:11] jamespage: i'd stick with that syntax. not sure what's broken [15:12] jeand, if you charm update has any charm proof errors, it won't injest into the charm store - that might be why [15:16] jamespage: i think it's b/c the git clone uses --depth 1, so when it tries to update to the specified rev, it's not there [15:17] tvansteenburgh, you may well be right [15:17] tvansteenburgh, fwiw - git clone -b stable --depth 1 https://github.com/openstack-charmers/charm-ceilometer [15:17] does the right thing ... [15:39] ddellav: hey - when do you think you might have the port security MP up for review? [15:39] I'd like to get that landed asap [15:48] jamespage, juju charm proof ./ worked [15:48] correctly [15:49] jean@jean-XPS13-9333:~/workspaces/juju-charms/mobicents-restcomm-charm/trusty/mobicents-restcomm$ juju charm proof ./ [15:49] jean@jean-XPS13-9333:~/workspaces/juju-charms/mobicents-restcomm-charm/trusty/mobicents-restcomm$ [17:09] jamespage, any other clues ? [17:12] jeand, urm sorry no [17:13] what's the proper way to get more insights on this ? [17:14] is there a juju charm store support channel ? [17:15] jeand - there is, 1 second let me fish up a link for you [17:16] jeand - you'll file a bug with the details you outlined above and someone will take a look to see why its not ingesting [17:16] ah great [17:16] thx lazypower [17:16] jeand - https://github.com/CanonicalLtd/jujucharms.com/issues [17:29] hi all, i have returned with my question about deploy bundle from juju gui. i have checked it again and my services are not exposed after bundle deploy. is it known issue? it's my bundle to reproduce issue - https://jujucharms.com/u/tads2015dataart/#bundles [17:31] gennadiy - looking at your bundle here: http://bazaar.launchpad.net/~tads2015dataart/charms/bundles/tads2015-demo/bundle/view/head:/bundle.yaml [17:31] you have an incorrect key. THe proper key is 'exposed: true' - its past tense [17:31] gennadiy: update that key, give it another go and let me know if you run into the same behavior [17:33] oh. i copied it from exported from juju-gui bundle. [17:33] there are `expose: true` [17:34] gennadiy: if that fixes you up i'll file a bug against juju-gui to take a look [17:34] i will try [17:34] just a moment [17:34] it may be an artifact/missing test coverage, etc. [17:35] but when i deploy this budnle from juju deployer services are exposed [17:37] gennadiy - yeah, thats definately a bug [17:37] if its exporting a syntax it doesn't handle [17:37] 1 sec and i'll pass along a bug reporting link for you [17:37] gennadiy https://bugs.launchpad.net/juju-gui/+filebug [18:51] is m3.medium the new default instance for ec2 as stated here: https://bugs.launchpad.net/juju-core/+bug/1373516/comments/7 by natefinch [18:51] Bug #1373516: Switch default instance type from m1.small to t2.small/m3.medium for EC2 provider

[18:52] amz: yes [18:52] how to list current ec2 environments settings for default instance ? [18:53] amz: it's totally based on juju version. if you're on 1.25 or higher, it's m3.medium, if you're on 1.24.x or lower, it's m1.small [18:54] natefinch: it would be good to document new default on https://jujucharms.com/docs/stable/config-aws [18:54] amz: absolutely a good idea. [18:55] natefinch: how to check current settings? is it really only related to version and no way to list current settings? [19:00] amz: version is the only way. It's not an exposed configuration value, per se. You can override the default by specifying an instance-type or other constraint at bootstrap time, or by setting an environment-wide constraint after bootstrap. [20:44] thanks natefinch [20:45] amz: no problem :) [20:48] lazypower: is bin/ exposed in the PATH for reactive charms? [20:48] cory_fu - I'm pretty sure this landed recently, but pinging cory to confirm [20:48] /var/lib/juju/agents/unit-hai2u-1/charm/bin <- [20:50] stokachu: I don't think the dir is automatically added to the path, no [20:50] cory_fu: ok i was trying to decide whether to put scripts in its own scripts/ dir or use bin/ [20:50] but bin may overwrite that [20:51] welp, i was wrong [20:51] * lazypower hattips and ice skates away [20:51] Files put in there won't overwrite your scripts unless the filenames conflict, which I highly doubt they will [20:52] ok cool [21:08] $CHARM_DIR/bin ;)