[00:00] lifeless: cool thanks === TheRealMue is now known as TheMue === almaisan-away is now known as al-maisan [08:25] aujuju: How to SSH into local juju instance? [08:51] hi, anyone knows where I can find more documents on MAAS? like BIOS update, firmware upgrade... etc === mcclurmc_ is now known as mcclurmc [12:12] lifeless, i'm not really understanding what your looknig for re " so, what I'd really like is to be able to shove juju into an lxc and give it a single callback to a 127.0.0.1 only service to fire up more lxc's, that would let me run multiple juju environments" [13:22] hello all [13:22] I have a django app that I'm developing that I'd really like to get into a charm === al-maisan is now known as almaisan-away === zyga is now known as zyga-food [13:50] jml: mhall119 is working on a django charm generator thing [13:53] jcastro: ah thanks. I was sort of hoping to get something up today. noodles pointed me at his blog post (http://micknelson.wordpress.com/2011/11/22/a-generic-juju-charm-for-django-apps/) [13:53] I'll work from that and from the bug he linked me to (https://bugs.launchpad.net/charms/+bug/1012942) [13:53] <_mup_> Bug #1012942: Charm Needed: python-django (with WSGI container) < https://launchpad.net/bugs/1012942 > [13:53] http://mhall119.com/2012/06/charming-django-with-naguine/ [14:01] jml: IMO, a single django charm won't work, there's too many different ways to use and deploy django [14:01] it's more of a library than a service [14:03] mhall119: yeah, that makes sense to me [14:09] SpamapS: ping me when you're around pls [14:32] "1) It requires Puppet, which isn’t natural for a Python project" – hah. hah. hah. [14:32] jcastro: wassup [14:32] Hey is juju broken in quantal? [14:32] Shouldn't be [14:33] evidence? [14:33] I tried to deploy "ubuntu" but it couldn't find it in the cs:precise/ubuntu, then I realized I forgot I had moved the box to quantal [14:33] try "juju deploy ubuntu" [14:33] and juju says it can't find it in the store, it's in the browser though [14:33] oh that charm is broken in the charm store [14:33] We need to get access to the importer's logs [14:34] oh ok, so it's not just me, whew [14:35] SpamapS: ok so I am thinking we should link up mims' jenkins hotness in that "tools" menu on the charm browser [14:42] 'morning all [14:44] heya all [14:45] am playing with juju on lxc, with mysql<->wordpress<->haproxy and my haproxy isn't working [14:45] I did juju ssh haproxy/0, but I can't find where the haproxy logs are at? [14:46] bloodearnest: I don't think haproxy logs much. [14:46] SpamapS, right [14:46] bloodearnest: perhaps syslog? === zyga-food is now known as zyga [14:47] SpamapS, nothing in there [14:49] bloodearnest: I am no haproxy expet, I wrote the charm as a proof of concept.. perhaps the manual will hep in this case? [14:49] also, the juju-generated stanza for proxying to wordpress has this line: server localhost localhost:80 check [14:49] s/expet/expert/ [14:49] which seems odd [14:49] SpamapS, ok [14:49] I get a 503 with the default config [14:52] bloodearnest: yeah it looks like wordpress is using the wrong hostname [14:52] SpamapS, is that an lxc issue? [14:53] relation-set port=80 hostname=`hostname -f` [14:53] (i.e. juju on lxc) [14:53] no its a charm issue [14:53] hostname -f is forbidden ;) [14:53] should be `unit-get private-address` [14:53] bloodearnest: I'll fix that right now [14:53] SpamapS, sweet [14:53] even tho I think we're getting a totally rewritten wordpress charm this week :) [14:53] when will that be available? [14:53] SpamapS, right [14:54] FYI, canonical ISD is having a juju sprint this week, so you might get bugged a bit :) [14:55] COOL [14:55] * SpamapS shuttles the toddler off to preschool ... bbl [14:55] I'm with bloodearnest [14:55] bloodearnest: fixed in lp:charms/wordpress [14:56] SpamapS, legend, thanks [14:59] * mars <- afk, need another cup of tea [15:10] How do I know if I'm using an updated charm or not? [15:11] * newz2000 wants to tryout SpamapS's new wordpress charm [15:13] sorry, newbie questions. I've deployed 'python-moin' to lxc on my laptop. How do I get to it? [15:14] jml, you mean to the moin web interface? [15:15] james_w: I guess. [15:15] james_w: I really mean any actual proof of its upness [15:15] jml, juju status should show an ip address for the "machine" it is running on, hitting that in your browser might be fruitful [15:15] james_w: it does noet. [15:15] public-address: null [15:16] jml, what's the full juju status? [15:16] http://paste.ubuntu.com/1047479/ [15:17] jml, looks like it is still coming up [15:17] agent-state: not-started [15:17] agent-state: pending [15:18] oh wow, that does take a while [15:18] how can I see progress / get an eta [15:19] * jml has taken the garbage out, posted a bunch of thank you letters, cooked and eaten some lamb kebabs, made a request for clearer requirements and checked facebook about 6 times since running 'deploy' [15:20] jml, ps aux [15:20] | grep lxc [15:20] jml, or check the agent log [15:21] hazmat: what agent log? [15:21] 120 1232 0.0 0.0 25964 840 ? S Jun17 0:00 dnsmasq -u lxc-dnsmasq --strict-order --bind-interfaces --pid-file=/var/run/lxc/dnsmasq.pid --conf-file= --listen-address 10.0.3.1 --dhcp-range 10.0.3.2,10.0.3.254 --dhcp-lease-max=253 --dhcp-no-override --except-interface=lo --interface=lxcbr0 [15:21] root 27369 0.0 0.0 21156 1032 ? Ss 14:37 0:00 lxc-start -dn lpdev [15:21] jml, machine agent log [15:21] hazmat: doesn't exist. [15:21] hmm [15:25] * hazmat gets out of meeting [15:26] jml, so on a broadband connection it shouldn't take more than 15m [15:26] jml, wrt to logs their in the $data-dir specified in environments.yaml [15:26] jml, could you ps aux | grep juju | pastebinit [15:27] hazmat: http://paste.ubuntu.com/1047493/ [15:27] http://paste.ubuntu.com/1047492/ is the contents of my data-dir [15:28] jml, huh.. did you reboot it? the machine agent should be logging to /tmp/juju-local/jml-local/machine-agent.log [15:28] per its cli params [15:31] hazmat: "reboot it"? I don't know. When I ran 'juju bootstrap', that failed because the directory was owned by root. So I trashed the existing directory and ran 'juju bootstrap' again [15:31] jml, ah. [15:31] jml, you have to destroy-environment after first bootstrap failed.. [15:31] on the understanding that it didn't conform with the behaviour on CharmSchool so some local thing had probably happened to screw it up, and no one would have told me to store something important in /tmp/, would they? [15:32] hazmat: ok. do I do that now? or should I trash it again? [15:32] jml, yeah. pls destroy-environment, and boostrap again [15:33] it looks like the previous bootstrap (first) created the machine agent upstart job but never had a place to log to.. but its oddl... it shouldn't care about root perms, because it runs as root to startup the lxc [15:34] * jml shrugs. [15:37] Hmm, had a working config of Wordpress + MySQL, then destroyed everything and started over, now (2x) juju deploy mysql results in agent-state: start-error [15:38] any idea what's going on here? [15:38] by everything, I mean all the services, not the environment [15:38] newz2000, did you destro-environment [15:38] no [15:39] should I? [15:39] dunno :) [15:39] * newz2000 gives it a shot [15:42] ok. now I get an IP address in 'juju status', but I can't connect to it (and netstat shows no listening ports on that IP) [15:45] jcastro: hey, for my lxc experience should I just paste the backlog here? :P [15:45] I had a todo to do it this cycle [15:46] but seeing you today I decided to clear my schedule and just document all the things [15:48] hmm.. getting the docs reviews are proving difficult [15:49] it's always the easy ones [15:52] anyone know what getting ConnectionRefusedError in watch_machine_changes on the master is a symptom of? [15:52] [15:53] juju thinks it launched an instance, but actually didn't, and I don't see anything else of relevence in the juju logs [15:54] mgz is the service provider responding? [15:55] mgz, connection refused would imply it couldn't talk to the provider api endpoint [15:55] it might just be more borked routing in canonistack, I'll check [15:55] jcastro: thanks :) [15:56] mgz, just use something known working.. like hpcloud.. [15:57] special casing canonistack because it doesn't have enough working infrastructure to resemble an openstack deployment feels like its working around the wrong problems [15:58] SpamapS: I think there might have been a regression in the wordpress charm that was recently updated. Now when I start an instance I get "it works!" [15:59] bah, I know what it is... the routing actually works inside, but my local workaround is getting on to the provider and breaking it [15:59] SpamapS: oh, wait, i forgot to expose it [15:59] newz2000: That's the wp-config.php thing I mentioned. [15:59] fugue88: So, maybe a problem with the wordpress charm not expecting to have different hostnames passed into it. [15:59] SpamapS oh, that didn't change it. Still "it works!" [15:59] But not a problem with the haproxy charm. [16:00] fugue88: yes, but I'm just hitting the wordpress IP [16:00] not using haproxy or anything yet [16:00] hazmat: where does the conf get stored on the master? [16:01] mgz, conf? [16:04] hazmat: as in, it's not in /home/ubuntu/.juju/environments.yaml but was serialised and passed across somewhere [16:04] mgz its in zk [16:04] dammit :) [16:04] mgz /usr/share/zookeeper/bin/zkCli.sh [16:04] mgz interactive console ls / .. get /environment [16:05] ta, poking. [16:09] ping SpamapS [16:10] mhall119: why does naguine think my django project uses sqlite3? [16:12] * SpamapS is back [16:13] newz2000: the wordpress charm is broken w.r.t. hostnames [16:13] newz2000: I thought I had fixed it so the "default" host was wordpress tho [16:13] well this is daft, java.lang.NumberFormatException on setting any string with a space in it... [16:13] SpamapS: I see! I think this is somewhat inherited from the debian package [16:13] must be a way of passing content of a file [16:14] SpamapS I think I've foobar'd my juju setup so take my current feedback with a grain of salt. [16:15] newz2000: well when in doubt, destroy and re-deploy :) [16:15] SpamapS: I've just done that and now I can't successfully deploy mysql. Gonna do dist-upgrade and reboot. Then I'll test and get back to you. === salgado is now known as salgado-lunch [16:17] jcastro, fixed re docs in review queue [16:17] <3 [16:18] although the display could use some work [16:18] oh, those are core branches [16:19] jcastro, no their doc branches [16:19] just displayed badly [16:19] oh [16:19] oh nice, so really, more good targets then [16:20] ping SpamapS: I believe I am having an issue with https://bugs.launchpad.net/juju/+bug/920454 - is there currently a workaround of any sort? [16:20] <_mup_> Bug #920454: juju bootstrap hangs for local environment under precise on vmware < https://launchpad.net/bugs/920454 > [16:21] jcastro, fixed === almaisan-away is now known as al-maisan [16:52] sorry to everyone who's about to get a very large diff in email. [16:52] SpamapS, I think the issue w/wordpress is when putting haproxy in front - forwarded hostname is different so fails to find the right config in /etc/wordpress [16:53] bloodearnest: that is a known issue with the current charm [16:53] mgz, woot! [16:54] marcoceppi, k thanks, got a bug I can watch? [16:54] let me find it === salgado-lunch is now known as salgado [16:55] ooh happy, there's the openstack provider incoming, woo! [16:58] woot! [16:58] :) [16:58] marcoceppi: are you done w/ the new one yet? [16:58] SpamapS: not yet, should be done with it this week [16:58] marcoceppi: let me rephrase that. Does the new one work for even the most basic use case yet? [16:59] jml: does it say it uses sqlite in your settings.py? [16:59] marcoceppi: at this point, I'd rather have "not done but actually works sort of" over "thing that basically doesn't work at all" [16:59] SpamapS: It's not at the point where I'd feel comfortable having people used it. A lot of stuff is still being shuffled around in it [17:00] and the subordinate isn't even anywhere near operational yet [17:00] mhall119: oh right. I thought I'd blatted over that, but I was getting confused with a different project. [17:00] marcoceppi: mmk. :-/ [17:00] yeah [17:04] SpamapS, I think your earlier change fixed this bug - or at least it did for me https://bugs.launchpad.net/charms/+source/wordpress/+bug/903312 [17:04] <_mup_> Bug #903312: Inocorrect Server is specified in Haproxy when using haproxy with Local Provider < https://launchpad.net/bugs/903312 > [17:05] bloodearnest: right. Not sure if that will fix the haproxy issue [17:06] bloodearnest: if it does though, huzzah [17:07] SpamapS, the hazproxy works correctly, but the wordpress doesn't :) [17:08] right [17:09] man.. the old wordpress charm kind of sucks (no offense to the authors). I think it might have been *the first charm ever written* .. but.. we've learned so much since then [17:09] marcoceppi, is this the bug in question? https://bugs.launchpad.net/charms/+source/wordpress/+bug/958204 [17:09] <_mup_> Bug #958204: Apache doesn't know about the server's private address < https://launchpad.net/bugs/958204 > [17:09] bloodearnest: that's it [17:10] * SpamapS does a little cleaning up even tho marco is days away from fixes [17:10] SpamapS: did you happen to see the above question about Bug #920454? Switching away from vmware for the time being, just would love any input you may have. [17:10] <_mup_> Bug #920454: juju bootstrap hangs for local environment under precise on vmware < https://launchpad.net/bugs/920454 > [17:10] marcoceppi, kk, thx [17:11] SpamapS, is "what you've learned since then" documented anywhere? [17:11] :) [17:11] bloodearnest: there are a series of posts that outline what we've learned (and it was oh so much) but the best documentation is the next release of the charm [17:11] bloodearnest: sadly no, we have a lot of work to document those best practices [17:12] marcoceppi: I'm not even talking about that [17:12] just basic stuff [17:12] like what to do in install vs. config-changed [17:12] SpamapS: oh yeah, sadly there isn't a like charming 101 kind of post [17:12] marcoceppi, is the next version available for instruction purposes? [17:12] we don't need posts [17:13] we need books really [17:13] We should mirror the upstart cookbook [17:13] or rather, follow its model [17:13] the upstart cookbook is huge though [17:13] If I want to do X, do it this way. If I want to do Y, do it that way. [17:13] and I found it difficult to navigate btw [17:14] Hrm thats a bummer. [17:14] bloodearnest: it's really not ready yet (to the point that it doesn't run at all without lots of interventions) but that's because it's mid-refactor [17:14] SpamapS: I agree that there should be a resource for this though [17:15] I really like how Go does their intro to Go http://tour.golang.org/#1 [17:15] Not sure how it could be adapted to Charming though [17:16] marcoceppi, kk - we're going to be writing a bunch of charms in order to a) learn how to and b) hopefully charmify Ubuntu SSO/Pay so that kinda stuff (best practice, what to do where) would be useful [17:16] marcoceppi: a tour would actually be fantastic [17:16] We kind of do i for juju usage in all our talks [17:17] I think a tour for juju would be boss [17:17] s/ i / it / [17:17] hmmmm whats this then https://code.launchpad.net/~gz/juju/openstack_provider/+merge/110860 [17:17] but since charms are all so, unique - it's hard to be like HERE'S A TOUR OF CHARMING, but it's in bash - or it's all in python - or it's all in C# [17:17] SpamapS: Oh, hello there [17:18] marcoceppi: we're like construction workers who just saw Charlize Theron walk by in a sun dress.. ;) [17:19] * marcoceppi whistles loudly [17:31] * SpamapS gets tired of chasing local provider fail and goes back to EC2.. again [17:35] * avoine can't wait to test the new OpenStack provider [17:35] SpamapS: heh ... yeah [17:37] avoine: should be able to test it just by branching that [17:37] I'm looking at the diff now [17:37] I'll do that [17:40] negronjl: mira, around today? [17:41] jcastro: here ... working on the Structure/MaaS/Juju thing [17:41] SpamapS: hey so we were missing the docs submissions in the queue, hazmat fixed it, check out the review queue now! [17:41] negronjl: oh, so not a good time to ask about graphs then [17:41] /tmp/juju-createRVPUAG: line 28: /etc/resolvconf/run/resolv.conf: No such file or directory [17:41] jcastro: lol ... not yet ... [17:41] anybody else see this while trying to use local provider? [17:41] negronjl: we should G+ with m3 later today though, talk velocity? [17:42] oh wait, n/m .. needed latest juju [17:43] jcastro: sure ... [17:44] jcastro: let me know when .... I also have the Ubuntu Developer Contributor thing today in about 1 hour and 15 minutes or so [17:44] oh ok [17:45] we can punt to tomorrow if you want [17:45] jcastro: better === zyga is now known as zyga-afk [17:52] kees: FYI, just merged all of lp:~kees/charms/precise/mumble-server/trunk into lp:charms/mumble-server. Thanks for adding maintainer. :) [17:56] jcastro, there mouseovers for the origin branch name fwiw on the merges [17:56] argh. their [17:56] they're [17:56] * hazmat finds a new language [18:03] SpamapS: thanks! I've got an update for my 'sbuild' charm as well, if you want to snag that oo. [18:03] *too [18:04] kees: \o/ [18:04] I think we're down to 20 that need maintainers [18:04] * SpamapS needs to pick that torch back up.. [18:06] SpamapS: note that the sbuild charm is more than just maintainer addition -- it's a refresh for precise, and makes the confg control better. [18:08] kees: excellent. I tend to just accept anything from maintainers that doesn't introduce malware. :) [18:08] SpamapS: \o/ [18:09] I figure if you're willing to put your name on it, you are willing to hear from angry users :) [18:09] hehe [18:11] SpamapS: I did it as a normal bug rather than a merge request because I didn't realize the oneiric charms all got moved forward to precise [18:12] kees: yeah we're still figuring out how thats going to work long term anyway. [18:12] Looking more and more like it will work a lot like the distro, except with aggressive backporting for new stuff. [18:16] SpamapS: cool [18:18] hazmat: trying to test out local provider + proposed .. seems like juju-create is getting cached somewhere [18:18] hazmat: any ideas where that might be? [18:18] SpamapS, its the first container in the env [18:18] SpamapS, lxc-ls [18:18] hazmat: destroyed and bootstrapped.. should be gone right? [18:18] yes [18:37] SpamapS, hi there, so I'm playing a bit with juju, done the basic wordpress stuff bla bla [18:37] so next I added an haproxy in front of the wordpress instance (so I can later on add more units there) [18:37] and I know wordpress charm doesn't play very nicely along with the haproxy one [18:38] and I know you guys are about to rewrite everything , so this is not a support request :) [18:38] except for some help in understanding the charm [18:38] pindonga: sure, I'm looking at it right now also so.. :-P [18:38] I see haproxy requires the other service to provide a reverseproxy relation [18:38] which wordpress doesn't do [18:39] so I was trying to make wordpress expose such a relation [18:39] for that I just need to edit the metadata and provide a reverseproxy-relation-{joined,changed} hooks right? [18:39] in the wordpress charm [18:40] err [18:40] no you' have it backwards [18:40] ah :) [18:40] hence the question [18:40] haproxy requires the other service to have an *http* relation [18:40] which nearly all the webapps in the charm store do [18:40] the name, reverseproxy, is irrelevant outside the hooks dir [18:40] ah, and it names that http relation 'reverseproxy' [18:40] well irrelevant to the other side I should say [18:41] k [18:41] pindonga: haproxy names it reverseproxy. Most charms name the provider side 'website' [18:41] kk [18:41] that interface.. http.. is very "proof of concept" .. we need to work out something better [18:42] so, the idea I had was that when the relation gets established we just symlink /etc/wordpress/config-.php -> /etc/wordpress/config-.php [18:42] that would make it work (for my purposes) [18:42] so I need to add that to the "something"-relation-{joined,changed} hook on wordpress right? [18:43] pindonga: I believe there's a "default" possible as well [18:43] pindonga: which is what should be done [18:44] pindonga: but yes for your purposes.. I'd add that link wherever the main config-... is made [18:44] I am just checking [18:44] the main config is created during db-relation-changed [18:45] however that's not where this should happen [18:45] hazmat: I'm here if you want me to expand on what I said [18:45] the extra symlink would then happen when website-relation-changed probably [18:45] SpamapS, thanks, I'll try it out and let you know [18:46] pindonga: yes that would work [18:46] pindonga: website-relation-joined would be fine actually [18:46] pindonga: you'll have the public-address at that point [18:46] which is what you want [18:46] yep, [18:46] tho I think changed is "more correct" [18:46] since in the future, that may change [18:46] it needs to happen in both [18:46] probably [18:47] pindonga: changed is always called once after joined no matter what [18:47] so, just in changed is appropriate [18:47] ah, good to know [18:47] is that documents in the hooks page? [18:47] s/documents/documented/ [18:49] pindonga: https://juju.ubuntu.com/docs/charm.html#hooks [18:49] yep, thx [18:50] lifeless, awesome [18:50] lifeless, so i saw rabbitmq queues and pika clients to juju.. [18:50] hazmat: huh... ? [18:51] lifeless, sorry.. crossed the streams that was ted [18:51] lifeless, what are you trying to do? [18:52] me, I had a chat with m_3 and filed a bug as a result, about juju's degree of entanglement with my machine, for the 'local' provider. [18:52] its much more intrusive than I had anticipated [18:52] lifeless, the upstart job, and the libvirt network? [18:52] to the extent it won't work on half my machines here, and will duplicate basic functionality like my squid cache [18:52] hazmat: running apt-cacher-ng, running zookeeper [18:53] hazmat: the latter, AIUI, constraining me to one local environment at a time [18:53] lifeless, it doesn't [18:53] lifeless, we run each env's zk on an offset port [18:53] er. random port [18:53] listening on the bridge i believe [18:54] ah, well thats something; however my lxc bridge is bridged to my LAN :) [18:55] it uses the libvirt default network [18:55] not the lxcbr [18:56] sorry for being imprecise. [18:56] I have a grunty workstation. its what I run $stuff on. [18:57] to make getting at its kvms and lxcs easy, its libvirt bridge is my LAN. [18:57] yeah, thats a bug that needs fixing for sure.. should allow an option to override the default network [18:58] how is the traffic securing work coming? I presume its trusted-traffic at the moment still ? [18:59] lifeless, demo of multiple local envs.. fwiw http://paste.ubuntu.com/1047850/ [19:00] lifeless, so transport level nothing yet [19:00] lifeless, securing zk storage, i've hit a libzk issue, i need to debug, getting some deadlocks [19:01] re transport i don't see much outside of stunnel or a twisted tls proxy. [19:01] lifeless, that's wrt to zk communication.. machine level security we need to switch out to firewalls. etc [19:01] hah https://issues.apache.org/jira/browse/ZOOKEEPER-235 [19:01] hazmat: heh, figured out my proposed+local issue.. r542 incoming. ;) [19:01] :( sadface. [19:02] lifeless, yeah.. [19:02] lifeless, there are people who run it with stunnel over untrusted networks.. but its a serious issue. [19:02] and yay, dup : https://issues.apache.org/jira/browse/ZOOKEEPER-1000 [19:02] hazmat: I agree :> [19:02] lifeless, atm, most of the developer bodies are on gojuju [19:03] hazmat: so, what does juju bootstrap locally do - adds an upstart job which runs apt-cacher-ng + zk, creates a single seed lxc node ? [19:03] SpamapS, if you don't mind one more question, I'm trying to debug the relation-changed hook... I exported the environment settings (JUJU_UNIT_NAME, JUJU_RELATION, JUJU_REMOTE_UNIT) but it's saying JUJU_AGENT_SOCKET is not set... how can I debug the relation-changed hook? [19:03] lifeless, install apt-cacher-ng, upstart job for machine agent, and upstart job for a simple file storage [19:03] pindonga: juju debug-hooks servicename/# is the best way [19:04] SpamapS, I'm in there [19:04] hazmat: any way to tell it to shove off w.r.t. apt-cacher-ng ? I have caching already :) [19:04] lifeless, on adding the first service, it creates an lxc container that it customizes and uses as a template for deploying units [19:04] but now I went to where the hook is stored, and run it (following the tutorial) [19:04] however I get these errors [19:04] lifeless, atm no. [19:04] while it tries to run unit-get and relation-get [19:05] hazmat: and there is something that restarts units on laptop reboot, I believe? Where does that live ? [19:05] lifeless, there is not .. local envs are toast on restart [19:05] local provider has not seen much love [19:06] hazmat: toast == not running or toast == deleted ? [19:06] lifeless, not running [19:06] hazmat: how do you cleanup such an environment? [19:06] or restart it ? [19:06] pindonga: no you have to wait till the hook is executed, you can't just force it [19:06] lifeless, juju destroy-enviornment [19:06] pindonga: remove/add the relation [19:06] pindonga: you'll get a new tmux window per hook execution [19:06] hazmat: is it possible to restart it ? [19:06] SpamapS, so before I do that: I run debug-hooks and it opened the ssh session to my unit [19:06] that's ok? [19:06] SpamapS, now I remove/add the relation, yes? [19:06] pindonga: thatss exactly right [19:07] SpamapS, thx, sorry for the noise [19:07] :) [19:07] pindonga: no, thanks for the noise. :) [19:07] lifeless, you'd have to start zk, and the containers [19:07] the zk is not upstartified [19:07] neither are the env containers [19:08] SpamapS, didn't do anything afaict [19:08] just did juju remove-relation but it finished [19:08] same for add-relation [19:08] or do I have to run these from within the unit I got opened via debug-hooks? [19:08] so, the heart of my bug was, I guess, that we're special casing LXC more than we need to - doing a -tiny- cloud api for local use should be doable as a standalone project, and that would let 'local' have nothing special to do. [19:09] lifeless, agreed.. [19:09] Said cloud API could remember state like 'this lxc was running' as well. [19:09] lifeless, SpamapS made the original lxc provider that way [19:09] but it didn't fly for what are at this point histerical raisons [19:10] so local juju config would become, install lxc-cloud-api, create a user, put user details in environments.yaml, profit. Install a cache and configure that in environments.yaml if you need one. [19:10] the other delta for the local provider is that its too intimate with its customization of the container [19:10] it should use cloud init and cloud-images ala every other provider [19:10] that's what lp:~hazmat/juju/local-cloud-img is a start on (the latter) [19:10] yeah [19:10]