[01:09] is it possible to destroy a subordinate hacluster unit in dying state === axw_ is now known as axw === axw__ is now known as axw [03:24] thumper, if we wanna to destroy a service properly, and its has relation with others, what shall we do exactly [03:25] remove relation firstly and then destroy service? [03:34] freeflying: I think with the fix that landed on friday, just destroying the service should work, but for now, best to be safe and remove the relations first [03:34] freeflying: the fix won't be released until 1.17 i think [03:35] thumper, so remove-relation works in 1.16.0? [03:36] freeflying: I hope so... seems pretty fundamental [03:39] thumper, :) === axw_ is now known as axw === thumper is now known as thumper-afk === freeflying is now known as freeflying_away === freeflying_away is now known as freeflying [05:21] what is an easy to test charms? I have a charm written but now need to debug it. Is there a tool to do this? Or do you just have to deploy it and see what happens? [06:46] sbbrtn: you can use the local provider and deploy there, it uses lxc locally [06:47] I'm not able to ssh into the local provider [06:49] sbbrtn, do you have ssh key pair [06:49] yeah. I created an ssh key like the tutorial said [06:50] maybe I am running the wrong command... [06:51] i run "juju ssh 1" and it gives me an error. [06:51] sbbrtn: that should work [06:51] sorry [06:51] no it won't [06:51] use 'juju ssh unit-name/n' [06:51] it has to do with limitations I've not yet fixed [06:51] alternatively [06:51] all the log files are local [06:52] by default in ~/.juju/local/log === thumper-afk is now known as thumper [06:52] * thumper goes to do a few dishes [06:52] ahh. thanks! [06:52] that works [07:07] I destroy-service, is it normal that the machine hasn't been released from maas? [07:19] freeflying: yes, the machine isn't destroyed automatically (yet) [07:19] freeflying: we are looking to change the default behaviour back to what pyjuju did [07:20] freeflying: right now, when the last unit is removed from a machine, the machine is still around [07:20] freeflying: we want to change this (soonish) [07:21] thumper, I just did it :) [07:21] freeflying: just did what? [07:21] thumper, destroy services and then destroy machines [07:21] then get the machine released from maas [07:22] * thumper goes to roll his calves [07:24] :) === CyberJacob|Away is now known as CyberJacob [08:01] Ceph did not deploy to machine 0 why? | http://askubuntu.com/q/375321 === CyberJacob is now known as CyberJacob|Away [09:27] Hey when i run 'juju bootstrap -e azure'. My memory completely fills (16GB + 8 GB swap) to the point my box crashes. I need to file a bug for this, is there any specific logs you would need included with the bug report? [09:47] DanChapman: I can't think of anything off the top of my head. I'd say just file it, and when someone looks at it they may ask for more info. [09:48] axw, thanks I will do that then :-) [09:48] DanChapman: do you have any non-default parameters in your environments.yaml? apart from the credentials [09:48] perhaps list them [09:49] DanChapman: also, the version of juju [09:50] axw all I changed were the credential: subscription-id, storage-account, cert path and location. I've included the juju version I'll add some info about the .yaml file [09:51] cool, thanks! [09:54] after destroy a service, some relation stays in dying, how can I get them removed? [09:56] freeflying: can you please pastebin a "juju status" for me? === freeflying is now known as freeflying_away [11:33] heya all, 2 simple questions: [11:34] 1) is there a standard way to get a file path friendly version JUJU_REMOTE_UNIT? I see a lot charms implementing their own sanitizing functions [11:35] (am using charm-helpers, but can't see one in there) [11:36] 2) is there a standard solution to subordinate charms possibly fighting with it's main charm over apt locks if their install hook execution overlaps? Does it indeed overlap? Is hook execution serialized per-unit? [11:55] bloodearnest: no, everyone has implemented their own. It is probably worth adding to charm-helpers if you can think of a good name for it. [11:56] bloodearnest: 2) is interesting - could be worth adding locking to the charm-helpers helper? [11:56] bloodearnest: I don't know what the current serialisation guarantees are with hooks [11:59] stub: I'm seeing code in gunicorn subordinate charm to retry in a loop, which I've gone with. Just thought it was error prone if subordiante charm authors have to remember to do it [12:00] bloodearnest: yeah, that sounds like a hack to me. [12:01] as for names: urlsafe_juju_unit? [12:02] I guess. Or sanitized_juju_unit if it is generic enough [12:02] I mainly needed it for filesystem safe names [12:03] oh - and sql safe for database names, usernames etc. [12:05] good point [12:07] (think the last version I coded allowed only a-zA-Z0-9_ ?) [12:07] (And now I think of it, it probably explodes if the service name starts with a number) === freeflying_away is now known as freeflying [13:09] How to make my nodes online in maas? | http://askubuntu.com/q/375412 [13:34] bloodearnest, you should not hit 2) - within a container hook execution is serialized [13:34] if you have that's a bug [13:35] jamespage: ack, good to know. Not hit it, just working on a charm that has code to handle it, wasn't sure it was needed [13:35] jamespage: I'll remove it [13:35] bloodearnest, it used to be a problem [13:35] but then someone saw sense in that juju was much better positioned to resolve that sort of thing [13:35] yep [16:38] jamespage: adam_g would you guys be opposed to me assigning reviews for openstack charms to ~openstack-charmers and having ~charmers abstain? In order to get them out of the queue? [16:39] Or do you guys use the queue? [16:39] I did one like that a few nights ago, then thought I should ask you all first [16:41] sbbrtn: local provider caveats have been documented https://juju.ubuntu.com/docs/config-local.html#caveats [16:41] marcoceppi, should we move the official branches over to that team as well? [16:43] jamespage: you're more than welcome to, it makes no difference to us at this point, though it might break a lot of existing deployer files. I know CTS explicitly uses lp:~charmers branches for their deployers [16:44] ok [16:44] I just didn't want to break your review workflow [16:44] and I didn't want new charmers to start reviewing stuff since it might be in flux with the openstack charms [17:23] hi, could I inderest someone into taking a look at a one-liner MP against the apache2 charm? https://code.launchpad.net/~ahasenack/charms/precise/apache2/apache2-no-failing-juju-log/+merge/194403 [17:30] MP ? [17:31] must be a bzr/lp term [17:59] MP means Merge Proposal [18:35] Juju with GUI Installation | http://askubuntu.com/q/375570 === CyberJacob|Away is now known as CyberJacob [21:25] Unable to install juju-gui locally? | http://askubuntu.com/q/375635 [22:14] bac: lol at dual post answering [22:15] and <3 jcastro for editing === freeflying is now known as freeflying_away === freeflying_away is now known as freeflying === CyberJacob is now known as CyberJacob|Away