[02:19] <mwhudson> hm
[02:19] <mwhudson> when using the manual provider, can you tell the added machines apart somehow?
[07:14] <sparkiegeek> tvansteenburgh: hi could you take a look at https://code.launchpad.net/~adam-collard/charms/precise/reviewboard/trunk/+merge/224041 it fixes a bug in installation and adds a bunch of unit tests
[10:11] <jamespage> niedbalski, around ? looking at the ceph-osd merge proposal you made
[12:15] <galebba> I am trying to colocate few openstack services in to a single maas node with lxc containers. however when i deploy them from juju, they always show up as agent pending in juju status. I can see all the containers are up and running. Any idea how to troubleshoot ?
[12:23] <lazypower> galebba: is there anything showing up in machine-0.log that provides a hint?
[13:03] <automatemecolema> can anyone tell me how I can upgrade my juju environment? I've tried juju upgrade-juju but it remains at 1.18.1
[13:03] <automatemecolema> I've add the juju/stable ppa and have done an apt-get update
[13:05] <jcastro> achiang, hey, I found this wrt. our last conversation: http://askubuntu.com/questions/262833/how-do-i-force-juju-to-deploy-a-fresh-charm-not-a-cached-one
[13:08] <automatemecolema> nevermind... didn't realize I can just update it from apt-get
[13:11] <automatemecolema> So I'm getting an error creating a blank charm here it is: https://gist.github.com/anonymous/fe34ed482cc45508de23 Not sure what to make of it
[13:12] <lazypower> automatemecolema: thats a known regression as of Friday in charm-tools. There's some new charm templating code to blame there.
[13:13] <automatemecolema> So what should I do about it?
[13:13] <automatemecolema> Not sure how I can roll back to an older version
[13:14] <marcoceppi> automatemecolema: there's a new release that fixes this coming out today
[13:15] <automatemecolema> fantastic
[13:15] <automatemecolema> :)
[13:15] <lazypower> automatemecolema: https://bugs.launchpad.net/charm-tools/+bug/1332664 - looks like it was fixed in trunk, its just not released.
[13:15] <lazypower> oh
[13:15] <lazypower> looks like marco's on it :)
[13:17] <automatemecolema> Until the fix is released can someone point me to where I can pull the bits from a previous working version?
[13:25] <automatemecolema> looks like I can download source files from launchpad, but only for 1.2.9 or 1.3.0, looks like tons of bugs in 1.3.0
[13:31] <tvansteenburgh> 1.2.9 should be fine
[13:33] <automatemecolema> Yep I just installed 1.2.9 from source
[13:34] <tvansteenburgh> automatemecolema: note that prior to 1.3 'charm create' can only create bash charms
[13:38] <automatemecolema> So what can charm create do in 1.3+
[13:38] <tvansteenburgh> python charms
[13:39] <automatemecolema> And that's why 1.3.1 is broken because it's trying to create symbolic links for some python hooks?
[13:39] <tvansteenburgh> and it adds a plugin system for charm templates so we can add more template, e.g. ansible-based charms
[13:39] <tvansteenburgh> there were several bugs, in your instance that's not the problem
[13:44] <jamespage> marcoceppi, around? wanted to chat about mysql and how we might make it more multi-network aware
[13:44] <marcoceppi> jamespage: I am around, but I'm a bit tied up at the moment. Give me an hour?
[13:44] <jamespage> marcoceppi, works for me
[13:55] <marcoceppi> tvansteenburgh: I've built a prelim release of 1.3.2, want to test it?
[13:55] <tvansteenburgh> yes
[13:55] <marcoceppi> it looks good on my system
[13:56] <tvansteenburgh> marcoceppi: how do i install it?
[13:56] <marcoceppi> tvansteenburgh: uploading the deb to my server, one sec
[13:56] <tvansteenburgh> k
[13:57] <marcoceppi> tvansteenburgh: http://marcanonical.com/charm-tools_1.3.2-0ubuntu1_all.deb
[13:57] <tvansteenburgh> thanks, testing
[14:06] <tvansteenburgh> marcoceppi: it's good
[14:06] <marcoceppi> tvansteenburgh: sweet, pressing now
[14:11] <marcoceppi> automatemecolema: new tools released, should be available in apt in 15-20 mins
[14:12] <automatemecolema> marcoceppi: thanks watching some of the charm school vids right now :/
[14:13] <marcoceppi> automatemecolema: cool, keep in mind if you want the same charm create template that was generated during those charm schools you'll need to use `charm create -t bash`
[14:13] <automatemecolema> So moving forward python is the wave of the future of hooks in a charm?
[14:15] <automatemecolema> is there some major lingering differences in 1.3+ that will require some new charm school vids to point out?
[14:19] <automatemecolema> Also, will the charm school live streaming be a normal scheduled event in the future, is this just something Canonical/Ubuntu is doing to get awareness out there about juju and charms?
[14:22] <marcoceppi> automatemecolema: we do it about every two weeks
[14:22] <marcoceppi> next one is this Friday, IIRC
[14:22] <sparkiegeek> marcoceppi: jcastro: hi guys! could you please give some review love to https://code.launchpad.net/~adam-collard/charms/precise/reviewboard/trunk/+merge/224041? It fixes a bug in installation which is a blocker (and also adds some lovely unit tests)
[14:23] <jcastro> ooooooh
[14:23] <marcoceppi> sparkiegeek: will do, thanks for the heads up!
[14:23] <sparkiegeek> marcoceppi: cheers!
[14:31] <dpb1> niedbalski: hey, did you see my review comments?  thoughts?  I'd like to get this merged up, if possible.
[14:36] <dpb1> btw: https://code.launchpad.net/~davidpbritton/charms/precise/apache2/avoid-regen-cert/+merge/221102
[14:57] <niedbalski> dpb1, answered, just minor observations.
[15:08] <automatemecolema> juju pulled down the bits for 1.3.2 . The template charm looks quite a bit different than from 1.2 versions
[15:13] <lazypower> automatemecolema: by default it now specs out a python charm
[15:13] <lazypower> automatemecolema: if you wish, you can pass -t bash and it will generate a bash charm template. We recommend python based charms as its easier to unit test and typically yields higher quailty charms.
[15:15] <automatemecolema> lazypower thanks for the explantation. We are planning on use puppet to build charms with, and wonder if using bash for now is the best route
[15:16] <lazypower> automatemecolema: Bash is a good option. There's a precise charm for puppetmaster that may have the template structure for you - i'm not real familiar with teh charm
[15:16] <automatemecolema> Does anyone have a charm that I can use as a template to see how others have codified their charms with config management toolsets like chef, puppet, ansible, etc etc.
[15:16] <lazypower> but if you find it to be of help/use - Let us know. We'd love to build a template for puppet charms as well.
[15:17] <automatemecolema> Yea we are wanting to leverage puppet enterprise, so it seems we might have to write new charms to work with PE
[15:17] <marcoceppi> automatemecolema: you need to use `charm create -t bash`, as I mentioned earlier, to follow along in the video
[15:17] <marcoceppi> why is my buffer not refreshing until I send a message
[15:17] <marcoceppi> stupid IRC client
[15:17] <lazypower> automatemecolema: a good chef example is the rails charm, puppet master for puppet - theres a branch for Elastic Search using ansible here: https://code.launchpad.net/~michael.nelson/charms/precise/elasticsearch/trunk
[15:19] <automatemecolema> lazypower thanks reviewing the code on launchpad now
[15:21] <automatemecolema> Is there documentation around the charm-helpers.yaml file? Not sure what all options are available to configure it with
[15:24] <automatemecolema> lazypower: looks like that example is using ansible? Same difference when using it as a reference for how others are building using config management
[15:25] <lazypower> automatemecolema: ah, i just pulled up puppet-master and its in bash. Not puppet - so yeah. Following the rails / elastic search charm pattern will help
[15:25] <lazypower> both of which call the external config management framework from bash hooks.
[15:28] <marcoceppi> lazypower automatemecolema there is a puppet charm somewhere, I just can't seem to find it
[15:29] <marcoceppi> mhall119: can  you comment on this when you get a chance? https://bugs.launchpad.net/charms/+bug/1317281
[15:29] <_mup_> Bug #1317281: New Charm: go-pronto <Juju Charms Collection:New> <https://launchpad.net/bugs/1317281>
[15:29] <lazypower> i remember seeing one too, but had the same results.
[15:35] <Guest97229> Hello. I have created containers for diffferent OpenStack services on one of the nodes. However I don't know the credentials to ssh into those lxc containers
[15:39] <dpb1> thanks niedbalski, if you agree, could you mark your review and LGTM?
[15:40] <dpb1> niedbalski: (I just replied, might take a sec to show up)
[15:40] <automatemecolema> Guest97229 juju ssh {machine #}
[15:44] <automatemecolema> Any good docs around configuring security for your juju environment?
[15:44] <automatemecolema> best practice for a prod deployment maybe?
[15:45] <automatemecolema> going to the exposed juju-gui service using the password found in the .jenv files seems fairly insecure
[15:53] <marcoceppi> automatemecolema: what is insecure about it to you?
[15:55] <mhall119> marcoceppi: commented
[16:02] <X-warrior> How could I add a config that it is the file path to a file?
[16:15] <danharibo> I'm not sure if I'm missing something here; how do I deploy a charm that uses git over ssh to retrieve the repository, I don't see how I would set up the SSH keys for this
[16:20] <automatemecolema> macroceppi: 1. Password is in clear text in a configuration file. 2. No way to delegate access rights to the juju environment (all or nothing scenario)
[16:53] <tvansteenburgh> automatemecolema: re: charm-helpers.yaml, this may be helpful -> https://pythonhosted.org/charmhelpers/getting-started.html#updating-charmhelpers-packages
[16:54] <wrale_> must all juju charm running nodes have direct access to the public internet, so that they may install from the charm store?  i'm trying to deploy juju-gui, but i'm on a private network... bootstrap worked when i did sync-tools.. now what?
[17:02] <tvansteenburgh> wrale_: most charms will try to install packages from apt, at a minimum
[17:03] <tvansteenburgh> wrale_: this may be useful: https://juju.ubuntu.com/docs/howto-proxies.html
[17:04] <wrale_> tvansteenburgh: thank you.. i'm using maas.. i was hoping its deb squid would take care of this for me.. thanks for the link.. will look
[17:09] <danharibo> I kepe running into "/etc/ansible/host_vars/localhost: Expecting property name: line 1 column 1 (char 1)" during the install of python-django
[17:09] <danharibo> is this charm broken or what?
[17:12] <automatemecolema> tvansteenburgh: thanks lots of good stuff on that site
[17:12] <tvansteenburgh> music to my ears :)
[17:12] <schegi> hi playing around with maas/juju for a couple of days. want to deploy openstack/ceph ha cluster. is there a way to customize network configuration of the ceph charm? like to have two networks public/cluster different from the public network used by juju itself. Additionall i like to have customized osd (journal device / data device)
[17:15] <schegi> osds should be easy. just deploying naked and add osds later. but changing the networks in a deployed ceph environment would mean to replace the monitors and i am not shure if this would reflect back to juju-relations
[17:15] <tvansteenburgh> danharibo: does it break in the install hook? can you pastebin the contents of /etc/ansible/host_vars/localhost ?
[17:15] <danharibo> https://gist.github.com/danharibo/0262671fa222564b1663
[17:16] <danharibo> yes, 'hook failed: "install"'
[17:16] <tvansteenburgh> danharibo: my guess is that charmhelpers for python-django need to be upgraded
[17:17] <tvansteenburgh> i recall a bug fix relevant to this issue
[17:17] <danharibo> this one? https://code.launchpad.net/~patrick-hetu/charms/precise/python-django/charmhelpers/+merge/216351
[17:17] <danharibo> that was one of things I found while searching but I wasn't sure how it related
[17:18] <tvansteenburgh> danharibo: no, let me see if i can find it
[17:19] <tvansteenburgh> danharibo: https://bugs.launchpad.net/charm-helpers/+bug/1318036
[17:19] <_mup_> Bug #1318036: ansible thinks /etc/ansible/host_vars/localhost format is json <Charm Helpers:Fix Committed> <https://launchpad.net/bugs/1318036>
[17:20] <tvansteenburgh> so this was fixed in charmhelpers but python-django doesn't have it yet
[17:21] <automatemecolema> I notice when build things on my juju environment bootstrapped to Amazon, it throws tons of security groups out there. Is there anyway of making sense of what security groups match what, and any way to tidy this up a bit?
[17:21] <danharibo> tvansteenburgh: according to the merge, commit 62 fixes the issue
[17:22] <tvansteenburgh> danharibo: link?
[17:22] <danharibo> https://code.launchpad.net/~patrick-hetu/charms/precise/python-django/charmhelpers/+merge/216351
[17:22] <tvansteenburgh> danharibo: ah, theory busted :(
[17:23] <tvansteenburgh> oh wait
[17:24] <tvansteenburgh> danharibo: i'm not sure these changes have made it into the charm store yet
[17:24] <danharibo> yeah that might be the issue
[17:30] <Delair_> how can i download the icehouse package for juju
[17:36] <automatemecolema> Delair_: you mean the icehouse charms?
[17:36] <danharibo> tvansteenburgh: you were right.
[17:36] <schegi> Delair you should go for the trusty packages as far as i know (juju charm get lp:trusty/XXX )
[17:37] <schegi> https://wiki.ubuntu.com/TrustyTahr/ReleaseNotes/OpenStackCharms
[17:38] <schegi> or set your series to trusty in the environments
[17:39] <schegi> but correct me if i am wrong also kind of new to juju and charms
[17:39] <Delair> SORRY I LOST CONNECTION.. I meant to say that when i deploy openstack using juju it deploys grizzly.. I know the dashboard of icehouse is different
[17:39] <sarnold> Delair: < schegi> or set your series to trusty in the environments < schegi> but correct me if i am wrong also kind of new to juju and charms
[17:40] <schegi> https://wiki.ubuntu.com/TrustyTahr/ReleaseNotes/OpenStackCharms
[17:41] <schegi> someone able to help a litte with the ceph charm? wondering if there is a way to customize network settings.
[17:42] <sarnold> Delair_: http://paste.ubuntu.com/7691406/
[17:42] <jamespage> schegi, what are you looking todo?
[17:44] <schegi> ok got juju bootstarped and it uses lets say eth0 an 1GBit interface. now i like to deploy ceph to three nodes and i want ceph to use two other interfaces as its public/custer network.
[17:48] <schegi> in a manual deployment you could pass the public network ="interface" and cluster network="interface" parameter to your ceph.conf. But the charm does not have any options to do this. Changing it after the deployment would mean to replace monitors and i have no idea how this affect juju and relations made to the ceph charm. just adding these parameters to the template in the charm breaks the deployment.
[17:50] <Delair> schegi: sure make sense.. Let me do the change from precious to trusty and test
[17:55] <schegi> jamespage found this http://askubuntu.com/questions/469013/how-can-i-configure-the-public-and-cluster-network-with-the-juju-ceph-charm  similar setting. doing it post deploy does not make sense. was wondering what to tweak in the pulled charm sources.
[17:59] <schegi> Delair under precise adding openstack-origin: cloud:precise-icehouse to the config.yaml and juju deploy -c config.yaml should to the trick. take a look at the link
[18:04]  * schegi 
[18:07] <jamespage> schegi, I've started work on making the ceph charms and their clients network aware - anything with a /network-splits suffix under https://code.launchpad.net/~james-page/ is relevant
[18:11] <schegi> jamespage looks like that would do the trick. thy i will give it a try.
[18:11] <jamespage> schegi, configuring the actual network interfaces themselves is outside the scope of the charm - but if configured, ceph will use them
[18:12] <schegi> thats enough, networks are already configured as long as it uses given networks (by ip) and later relations are working i am perfectly fine.
[18:13] <danharibo> hmm, I issued remove-service and now lxc is just chewing up CPU
[18:40] <kirkland> can someone tell me why my icon.svg isn't working?  https://jujucharms.com/~kirkland/precise/yo-3/?text=yo
[18:42] <marcoceppi> kirkland: personal branches don't have icons shown
[18:42] <marcoceppi> kirkland: ask all about it in #juju-gui
[18:42] <kirkland> marcoceppi: ah, okay, makes sense
[18:42] <kirkland> marcoceppi: I suppose you could put some rather interesting images in there ;-)
[18:43] <marcoceppi> kirkland: right, that's the idea for protecting the store
[18:43] <marcoceppi> kirkland: there might be a flag you can put, #juju-gui would know
[18:44] <kirkland> marcoceppi: makes sense
[18:51] <benji> k
[18:51]  * benji moves the mouse cursor slightly
[21:21] <automatemecolema> have sort of a problem... I deployed a local charm, but it's not showing up on the GUI. If I do a juju status everything shows ok
[21:23] <jose> marcoceppi: hey, is there a possibility that the Chamilo charm can be on the store before or on Wed? upstream is having an expo and they would mention Juju on the expo
[22:15] <marcoceppi> jose: not sure if it can be in the store, but it'll be reviewed by then
[22:15] <jose> well, we're hoping it works :)
[22:20] <Tug> hey guys, I'm thinking about writing an adapter for capistrano. What would you recommend, a juju plugin which parses `juju status`?
[22:20] <marcoceppi> Tug: that's one way
[22:21] <marcoceppi> Tug: you could use python-jujuclient which interacts with the websocket api directly
[22:21] <Tug> marcoceppi, ok let's have a look
[22:25] <Tug> marcoceppi, do you know if the default public key always added when bootstrapping an environment or should I try to get the juju-client-key somehow?
[22:29] <Tug> is 'ca-private-key' in .juju/environments/{current_env}.jenv the ssh private key I can use to connect to the machines ?
[22:46] <marcoceppi> Tug: it's your .ssh/id_{rsa,dsa} key
[22:52] <Tug> marcoceppi, yeah I saw my public key was added to the list of authorized keys, not just that was always the case
[22:53] <Tug> marcoceppi, thank you
[23:13] <jose> hazmat: ping