=== defunctzombie_zz is now known as defunctzombie === thumper is now known as thumper-afk === tasdomas_afk is now known as tasdomas === CyberJacob|Away is now known as CyberJacob === defunctzombie is now known as defunctzombie_zz === defunctzombie_zz is now known as defunctzombie === defunctzombie is now known as defunctzombie_zz [08:00] adam_g, if you are in today - https://code.launchpad.net/~james-page/charms/precise/keystone/fix-requested-roles/+merge/183580 [08:00] that's the cause of the openstack-dashboard lack of member role stuff that jpds hit last week [08:01] they are not using swift and the keystone identity-changed hook was not creating the role for services not registering endpoints.... [08:58] helle jamespage === thumper-afk is now known as thumper [13:04] kurt__: Is the unit in a dying state? RE: Before I file a bug, is it a known issue with the inability to destroy service in 1.12 with status showing stuck in "life: dying" ? [13:04] hazmat: pong [13:04] hi marcoceppi: I did file bug. Sorry have to run [13:06] kurt__: no worries [13:06] kurt__: is the unit in an error state* is what I meant to ask [13:07] I think so, yes [13:15] kurt__: cool, next time you want to kill them off, just run `juju resolved ` a few times [13:15] this is expected behaviour of juju === kentb-out is now known as kentb === kentb is now known as kentb-afk [13:50] If I'm receiving relation not found, when adding a relation between 2 charms. It means that the metadata from both doesn't match? [14:16] X-warrior: Is this in regards to your editing the metadata.yaml file after deployment? [14:17] jamespage: http://askubuntu.com/questions/340465/juju-ceph-deployment [14:20] jcastro, posted [14:20] its a bitch [14:20] second hit in three days on that one [14:20] nice! [14:21] jamespage: where else? should I post it somewhere? [14:21] jcastro, raywang pinged me about it as well [14:21] thats where I raised that bug from [14:21] * jcastro nods [14:21] I pulled back the point release to ensure it got included === kentb-afk is now known as kentb [14:41] marcoceppi: yes, I created a service but I forgot to add a 'relation joined' on it to provide the service address === freeflying is now known as freeflying_away === freeflying_away is now known as freeflying [14:46] marcoceppi, pong [14:46] hazmat: hey, just got your ping from a day ago [14:46] 2 days* [14:47] hmm.. that thought is paged to disk [14:47] oh.. [14:47] marcoceppi, i was wondering about getting juju-plugins up to snuff [14:47] hazmat: sure [14:47] i'm currently tossing tangentially related plugins into deployer [14:48] but some are not.. and i'm wondering if we should fold everything into something like juju-plugins [14:48] hazmat: I've got juju-plugins already, it's really light weight, but I'm happy to beef it up in terms of adding more plugins to it [14:48] some of the packaging dependencies might increase though depending on the plugin [14:49] hazmat: I was considering doing a package per plugin, with a "juju-plugins-all" package to install all plugins [14:49] marcoceppi, the juju-faststat plugin for example from the ml.. is a nice speed focused status replacement for the moment. [14:49] hazmat: just to keep the list of dependencies down for single plugins [14:49] marcoceppi, package per plugin sounds bad.. [14:49] er. overkill [14:50] hazmat: okay [14:50] well if [14:51] well it's a trade off then, lots of deps, or bunch 'o packages [14:51] I'm fine either way, whichever convention makes the most sense [14:56] hazmat: right now they're just all in one package [14:56] so we can just keep it that way [15:26] this is my 2 metadata.yaml ( http://pastebin.com/KbXLkQ4K ), if I would like to add a relation from service to authserver, where authserver will provide it ip address ... does the authserver needs a hooks/authserver-relation-joined and the service needs a hook hooks/authserver-relation-changed. And the commmand should be 'juju add-relation authserver service' [15:38] X-warrior`: Pretty much, you can get the IP address of a current running unit with `unit-get private-address` so your hooks/authserver-relation-joined hook would look like `relation set hostname=$(unit-get private-address)` and the authserver-relation-changed on the other service would havethe following `relation-get hostname` to recieve that value [15:38] X-warrior`: however, unless it truely implements the HTTP protocol (which requires both a port and hostname to be set) I'd recommend naming the interface something different [15:39] using the HTTP interface tells juju that your authserver could work with haproxy, varnish, etc. If that's not the case you'll want to use a different interface name [15:39] If that is the case you'll want to make sure you set both the hostname and the port options in the relation-set command [15:40] likewise, your service charm requring the http interface means it could connect to wordpress, mediawiki, and a majority of other charms and be able to handle that data properly. So, if that isn't the case, you'll want to do what I recommended above and create a new interface name (or find an existing interface that matches what you're trying to do) [15:40] Since the interface name is what juju uses to match charms with each other [15:43] marcoceppi: could I name it with any name as I want? [15:43] X-warrior`: yup! Anything that makes sense to what that interface is for [15:44] X-warrior`: so you could call it "authserver" as the interface, then the first metadata.yaml relation name could be server and the second one's relation name could client [15:44] X-warrior`: interface could be authserver for both, but you could name the relations in a way that makese sense of what the role of the relation is to the charm [15:44] * marcoceppi creates an example paste [15:45] X-warrior`: http://pastebin.com/iUVJb6Fk [15:46] X-warrior`: I wouldn't use such a generic name as "authserver", unless you can make the interface generic, If it's a particular authentication softare, like ldap, I'd name the interface ldap or something similar [15:46] X-warrior`: the interface should embody exactly it's purpose. So we have generic interfaces, like http, and specific ones, like mysql or pgsql [15:47] X-warrior`: while the name is up to you, we do prefer people to name them wisely, at least for the store. [15:47] If these are just for you, you can do whatever [15:47] FOr the store we'd prefer it to be more specific, but again it's up to you [15:48] for now I'm just running more tests to understand how it works [15:48] but I know what you mean [15:48] :D [15:55] marcoceppi: the test worked destroying the machines and redeploying... [15:55] X-warrior`: sweet! [15:55] ty [15:55] :D [16:16] What does the 'IDEMPOTENCY' means? I mean, let's say I have a hook to a db relation changed... and this hook add the options (login, pass, dbname, etc) to a file... if it is idempotent the login, pass, dbname will not be updated. So I'm not sure I understand what does the "# IDEMPOTENCY is very important in all charm hooks, even the install hook. " means from https://juju.ubuntu.com/docs/authors-charm-writing.html [16:17] it means it can run again with the same result. [16:17] where same result means it doesn't hurt either. [16:17] so I can run it 100 times and everything is still good. I don't have things like messed up config with 100 screwed up lines. [16:18] of course that is my bad interpretation of what it means. It has a much nicer computer science definition which you are free to google. [16:18] well the definition means it will be exactly the same. [16:19] But on a relation-changed event... if you do it, it will preserve the values that was there before it calls the hook... so it doesn't make sense to me [16:19] le [16:26] X-warrior`: idempotency means with the same set of parameters, the hook will produce the same results [16:26] marcoceppi: ty === tasdomas is now known as tasdomas_afk [16:41] bbcmicrocomputer: please mark reviews in progress when you start them this week [16:41] so we won't step on each others toes [16:41] fwereade: heya [16:42] or jam [16:43] m_3: ok, sure === TheRealMue is now known as TheMue === defunctzombie_zz is now known as defunctzombie === defunctzombie is now known as defunctzombie_zz [17:20] hi where does juju store ssh private-key? [17:22] nm got it === defunctzombie_zz is now known as defunctzombie [18:40] jcastro, heyhey [18:42] fwereade_: hey so I was wondering when we can default to the local provider [18:42] but I think we can do that at the distro level instead of upstream? [18:43] * jcastro needs to ask jamespage [18:43] jcastro, to be fair, I should not be trusted with anything distro-related [18:44] fair enough ... James Page it is! [19:03] jcastro, ? [19:04] jamespage: hey so I was thinking, we should default to local in juju in the distro [19:05] instead of "amazon" [19:05] so when someone apt-get install's juju [19:05] they can deploy right away without anything else [19:05] jcastro, is that not driven by their environments.yaml? [19:06] it is [19:06] but by default right now it's "amazon" [19:06] ah [19:06] hmm [19:06] jamespage: also, out of curiosity .. do we need all 61MBs of mongodb-clients? [19:07] seems like a rather heavy dep ... [19:07] jcastro, yeah - that does suck [19:07] I'll take a look [19:07] juju generate-config generates environments.yaml tho [19:08] jcastro: so I think thats a change in juju-core right? [19:08] we can Recommend: juju-local from juju which means by default you get the local provider [19:08] ok [19:08] I was unsure if this would be an upstream thing or a distro thing, the choosing of a default [19:09] I think I'll just ping thumper when he comes online and ask him to do it [19:25] jcastro, ack [19:28] jamespage: recommending juju-local means that by default you end up with a mongodb-server running on your local machine (even before "juju bootstrap") because of how the mongodb-server package works [19:28] which I *think* defaults to 3GB prealloc [19:28] jam: yep [19:28] ouch [19:28] OK - I won't do that [19:28] jcastro, that makes making local the default tricky [19:29] * jcastro nods [19:29] jamespage: I'm not positive about the 3GB prealloc, but I am sure that you end up with mongodb running on a port nobody will connect to. [19:29] hey so could we do it so if you install juju by itself [19:29] it does what it does now [19:29] jam: that rings a bell - I had issues with the DEP-8 tests I wrote because it won't start on a 2GB root [19:29] but if you install juju-local we do the right thing to make it spin up local with no config other than installing the package? [19:30] jamespage: I know you can configure with or without prealloc, I'm just not sure what the .deb default is today. [19:30] realloc [19:30] prealloc rather [19:30] jcastro, you still get a mongodb-server running in the background that no-one is actually using... [19:30] * jcastro nods [19:31] ah nuts ... :-/ [19:31] jcastro, if we had thought about this a bit harder I'd have split the binary into a monogodb-server-common package [19:31] and then just install the init script in the mongodb-server package [19:31] jamespage: so it's probably better to leave that an explicit decision by the user then? [19:31] jcastro, I think so yes [19:31] jamespage: is that something we can do post-13.10 bute pre-14.04 you think? [19:31] yes [19:32] ok .... /me PUNTS the ball [19:33] jamespage: it would be nice that if you "apt-get install juju-local" you would end up with an environments.yaml that points to local [19:33] jam: that involves a package manipulating user data != no go [19:33] jcastro: I think there is a bug about switching to local by default because we know you have those creds. And if bootstrap doesn't work we could tell you about the apt-get juju-local package. [19:34] jamespage: I did say "would be nice" but even if "juju init" does that bit [19:34] I remember filing a bug with thumper @ IOM, but I haven't been able to find it all day [19:39] Hey all; I'm entering the charm championship and I'm having trouble with Juju - I'm running 13.04 on the stable juju ppa. I'm running kvm and I was wondering if I could configure an environment to spin up a new VM in KVM when I run juju deploy? I've found docs for stuff like OpenStack, but that's a bit heavyweight for what I want :) [19:40] (unless it's not? I'm new to all this so I may have the wrong end of the stick :) ) === kentb is now known as kentb-afk [20:05] Googling suggests this isn't possible :s Can I add custom environment handlers? [20:09] jackweirdy: juju has support for LVM containers, we haven't yet implemented KVM support [20:10] you can install "juju-local" from the ppa, and then set up a "local" environment. [20:11] Ok; thanks anyhow :) [20:11] Does the local environment use lxc? [20:20] Hi charmers, login to manage.jujucharms.com is broken at the moment. Those already logged in can feature and QA charms. We expect a fix in a few hours === kentb-afk is now known as kentb [20:48] hazmat, darwin merged to lp:juju-deployer [21:14] jam: LVM is a type of volume/disk storage, it's not a container.... [21:14] jackweirdy: yeap local environment uses lxc. [21:18] morning [21:18] hi thumper === kentb is now known as kentb-out === defunctzombie is now known as defunctzombie_zz === defunctzombie_zz is now known as defunctzombie === freeflying is now known as freeflying_away