[09:34] <chenxiongfei> juju
[09:47] <_benoit_> Hi
[09:48] <_benoit_> wanabee contributor question: I want to add support for an EC2 compatible provider to juju. Will the patches be wellcome ?
[13:10] <avoine> _benoit_: which one? (note that I'm just curious and I'm not in the juju dev team)
[13:12] <cargill> what to do when a charm in the store needs to be obsoleted?
[13:26] <avoine> fill a bug I guess
[14:00] <_benoit_> avoine: Outscale cloud
[14:00] <_benoit_> avoine: there si two compagny Outscale INC and Outscale SAS who are providing a high performance cloud
[14:03] <_benoit_> avoine: If you are looking for an european EC2 alternative Outscale is  a good option
[15:22] <mister_zombie> Hi, does Juju have a REST api of some kind?
[15:23] <mister_zombie> I found stuff in launchpad that suggest it does, but I didn't find any documentation about it. I did google words that I thought were appropriate, but the results were not what I was looking for.
[15:30] <marcoceppi> mister_zombie: yes, it does
[15:30] <marcoceppi> mister_zombie: not quite a RESTful API, but it's an API
[15:31] <marcoceppi> mister_zombie: there's a package, jujuclient, in python for communicating with the bootstrap node
[15:37] <mister_zombie> marcoceppi: Thanks, will look at that.
[15:40] <mister_zombie> marcoceppi: It's using a websocket?
[15:40] <marcoceppi> mister_zombie: yes
[15:41] <mister_zombie> Oh, cool. I wanted to build some kind of client that could fire up/shut down instances of services from some web interface I'd build.
[15:42] <mister_zombie> Which seems redundant to the web ui but yeah.
[15:52] <marcoceppi> mister_zombie: cool, yeah, that's available to do
[16:04] <magicrobotmonkey> can you make bootstrap leave the node up for debugging?
[16:06] <marcoceppi> magicrobotmonkey: can you elaborate?
[16:07] <magicrobotmonkey> well i ran juju bootstrap and it died on cannot resolve streams.canonical.com
[16:07] <magicrobotmonkey> and then shut the node down
[16:07] <magicrobotmonkey> befofe i could get on it and investigate dns
[16:07] <magicrobotmonkey> (my nodes do not have internet access so things are running through proxies. hopefully)
[16:22] <marcoceppi> magicrobotmonkey: ah, yes, if a bootstrap fails during bootstrap it does a clean up
[16:22] <marcoceppi> magicrobotmonkey: I have no idea how to get around that though, possibly with the --debug flag during bootstrap
[17:05] <magicrobotmonkey> is nova-volume called something different in trusty?
[17:49] <whit> lazyPower, heyo
[17:49] <lazyPower> whit: https://juju.ubuntu.com/docs/reference-reviewers.html
[17:49] <lazyPower> o/
[17:50] <whit> lazyPower, danke
[17:50] <lazyPower> Ihr Willkommen
[18:09] <lazyPower> jose: new version of owncloud has been released
[18:10] <lazyPower> 0.6.3
[18:20] <jose> lazyPower: ack, should be an easy fix, but can I get the other MP off the way?
[18:20] <jose> that way I can test that it actually works with the SSL integration stuff once it's updated
[18:21] <lazyPower> jose: ack. sprinting so you know the drill. Will get to it asap
[18:21] <jose> yep, thanks!
[18:24] <mhall119> jose: lp:~mhall119/+junk/go-pronto-charm has my start charm
[18:24]  * jose checks
[18:24] <mhall119> with a go-pronto binary for i386 in files/
[18:25] <jose> so what theda c mentioned is that $CHARM_DIR/files/go-pronto would be the path to look for if you want to run the binary
[18:27] <mhall119> or copy the binary somewhere else on install/upgrade-charm
[18:27] <mhall119> which was what I was going to do
[18:27] <jose> that could work, yes
[18:27] <jose> it's going to be 'go get' if 64bits else binary?
[18:28] <mhall119> I can probably just call it from the start hook and push it to a background process...but that seems hackish
[18:28] <mhall119> no, I was going ot just ship the binary, no go-getting
[18:28] <jose> then it needs to fail if the machine is 64bits
[18:28] <mhall119> it could run the 32bit binary on amd64, couldn't it?
[18:28] <mhall119> it'd just have to fail on arm
[18:29] <jose> hmm, not sure
[18:30] <jose> now, for the upstart job you can just copy what's in http://bazaar.launchpad.net/~jose/charms/precise/communitycast-server/trunk/files/head:/data/
[18:30] <jose> http://bazaar.launchpad.net/~jose/charms/precise/communitycast-server/trunk/view/head:/data/communitycast-server.conf specifically
[18:35] <mhall119> is that all there is to an upstart job?
[18:42] <jose> mhall119: yep, at least I got it that way for communitycast-server
[18:42] <jose> oh, and you need to copy that to...
[18:42] <jose> /etc/init/job-name.conf
[18:43] <jose> to start it's `start job-name` and to stop `stop job-name`
[18:45] <mhall119> thanks jose
[18:45] <jose> np :)
[18:45] <jose> let me know if you need a hand with anything
[18:57] <mhall119> will do
[19:18] <magicrobotmonkey> im having trouble with my keystone charm because localhost requests are getting sent through my proxy
[19:19] <magicrobotmonkey> the only place i see the proxy set is in /etc/apt/apt.conf.d/42-juju-proxy-settings
[19:19] <magicrobotmonkey> is there any way to add excpetions or anything in there?
[19:29] <lazyPower> magicrobotmonkey: http://askubuntu.com/questions/92764/disable-proxy-server-for-one-apt-repository
[20:21] <mhall119> marcoceppi: jose: I'm getting a strange error from my go-pronto charm:
[20:21] <mhall119> 2014-04-30 20:16:38 INFO juju-log Creating pronto settings in /etc/go-pronto/config
[20:21] <mhall119> 2014-04-30 20:16:38 INFO config-changed + '[' '!' -d /etc/go-pronto ']'
[20:21] <mhall119> 2014-04-30 20:16:38 INFO config-changed + cat
[20:21] <mhall119> 2014-04-30 20:16:38 ERROR juju.worker.uniter.charm git.go:211 git command failed: exit status 128
[20:21] <mhall119> path: /var/lib/juju/agents/unit-go-pronto-0/state/deployer/update-20140430-161638997305812
[20:21] <mhall119> args: []string{"commit", "--allow-empty", "-m", "Imported charm \"local:trusty/go-pronto-7\"."}
[20:22] <mhall119> my charm isn't calling git anywhere....so why is it failing due to git?
[20:24] <lazyPower> mhall119: are you on 1.19.1 or on 1.18.x? the 1.18 series of juju still uses git as an internal versioning tool
[20:25] <lazyPower> this was removed as of 1.19.1
[20:25] <mhall119> $ juju --version
[20:25] <mhall119> 1.18.1-trusty-i386
[20:27] <mhall119> is 1.19.1 being backported?
[20:31] <mhall119> woot! success!
[20:53] <gdey> hello everyone.
[20:53] <marcoceppi> gdey: o/
[20:54] <marcoceppi> mhall119: 1.19 series is bascially the RC for 1.20
[20:54] <marcoceppi> mhall119: 1.ODD are dev releases
[20:54] <gdey> Anyone one have a small tutorial or any documentation on how to create a provider for juju in go?
[20:56] <marcoceppi> gdey: you should ping mgz
[20:56] <marcoceppi> gdey: there's an example provider in the code base, but not really any documentation outside of the doc
[20:58] <gdey> marcoceppi: k
[20:59] <gdey> marcoceppi: Just making sure, in the juju-core code base; correct.
[21:02] <marcoceppi> gdey: correct, under providers I believe
[21:22] <qhartman> I've gotten my openstack setup working with Juju, with only a little bit of manual tweaking
[21:22] <qhartman> one thing I'm having to do is add config-flags to the nova-compute config options
[21:23] <qhartman> I've applied them in the gui, and they've appeared in the running config on one of my compute nodes that I have going, but not the other
[21:23] <qhartman> how long should it take to juju to propagate these changes to all node?
[22:02] <tvansteenburgh> jose: ping
[22:03] <jose> tvansteenburgh: quick-pong
[22:05] <tvansteenburgh> jose: nevermind, i'll email you
[22:27] <mbruzek> jose are you there
[22:28] <mbruzek> I have a question about your owncloud charm.
[22:51] <mgz> jcastro: <http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/InstanceStorage.html#Using_AddingDefaultLocalInstanceStorageToAMI>
[22:51] <mgz> "For M3 instances, you must specify instance store volumes in the block device mapping for the instance. When you launch an M3 instance, we ignore any instance store volumes specified in the block device mapping for the AMI."
[22:51] <mgz> so, *if* he was switched to m3 instances from m1 instances by the pricing drop, he may well no longer be getting instance store when our images previously included it