[01:51] <jose> lazyPower: ack
[01:52] <lazyPower> jose: its not a game changer, just noticed it when I was derping around after my desktop upgrade
[01:52] <jose> lazyPower: would you think it'd be good to remove the tests until I can get them fixed?
[01:53] <lazyPower> jose: beg pardon?
[01:53] <jose> owncloud
[01:53] <jose> tests are failing
[01:53] <lazyPower> i'd rather see them fixed vs just removed
[01:53] <jose> have tried to but can't
[01:55] <lazyPower> jose: ping me about it tomorrow and i'll take a look
[01:55] <jose> awesome then :)
[11:50] <exippy> hello everyone, I need to prevent juju from starting at boot but I can't figure out how to do this, can anyone help me?
[11:51] <jam> exippy: what is "juju starting at boot", you are running the local provider but don't want your instances to start? Or is there something else?
[11:51] <exippy> yes this is exactly it :)
[11:52] <exippy> i have some networking issues on the host, and i'd like to disable juju till i fix this
[11:52] <exippy> i might have tinkered a bit too much, resulting in some sort of conflict between the internal and external network
[11:53] <jam> exippy: IIRC jujud is started from /etc/init/juju-$USER-local.conf or something close to that
[11:53] <jam> if you are just trying to make the LXC instances not start
[11:53] <jam> I think there is a different flag in the LXC configuration about what should auto-start
[11:54] <jam> but I think you can play around with the LXC tools to find something about autostart. I'm not personally an expert on it.
[11:54] <exippy> i commented out the exec line in that script, but i still see the lxc instances starting in the logs
[11:54] <jam> but if it is an LXC thing, it would be "lxc-$SOMETHING" and tab completion should give some hints
[11:54] <jam> exippy: the LXC instances are started by LXC itself
[11:54] <jam> so you have to set them up as "no autostart"
[11:54] <exippy> ok
[11:54] <exippy> thank u jam, i'll see if i can find how to disable this
[11:55] <jam> exippy: this is how we enabled it: https://code.launchpad.net/~waigani/juju-core/lxc-trusty-autostart/+merge/202974
[11:56] <jam> exippy: so "/etc/lxc/auto" if you are on Trusty, otherwise it is "lxc.start.auto = 0" in the individual config files
[11:56] <exippy> ok i'll remove that file and see how that goes
[11:57] <jam> exippy: /etc/lxc/auto is a directory with symlinks in it to each container
[11:57] <jam> so remove the symlinks and not the dir itself
[11:58] <exippy> would this prevent the creation of lxc virtual network?
[11:59] <jam> exippy: I don't think touching these will affect lxcbr0
[12:00] <exippy> hmm is it normal that i don't see /etc/lxc/auto on trusty?
[12:01] <jam> exippy: given that you see the containers autostarting it seems strange to me
[12:02] <jam> can you do "sudo lxc-ls —fancy" and see what it says?
[12:02] <exippy> unfortunately i only have access to the file system
[12:02] <exippy> through a rescue kvm
[12:06] <exippy> well thank u anyway, at least i know what i'm looking for
[14:55] <tedg> lazyPower, hey, heard you are working on an owncloud bundle. Is it ready to use?
[15:08] <_mup_> Bug #1316185 was filed: juju bootstrap hangs on Azure <pyjuju:New> <https://launchpad.net/bugs/1316185>
[15:18] <d3lxa> is there a way to restart jujud or mongodb? juju status says timeout and it's due to overloaded mongodb thing it seems
[15:20] <jam> d3lxa: restarting mongodb would cause the jujud process to restart itself, though I don't know that it will actually help you
[15:21] <jam> there should be a "juju-db" service, IIRC
[15:21] <d3lxa> jam: maybe? I have multiple envs, just want to restart jujud for a specific env
[15:22] <jam> d3lxa: the service is running in your environment, not on your local machine (unless you are running multiple local environments)
[15:24] <gnuoy`> is the option to get juju status to create a dot file still a thing ? juju help status seems to suggest not
[15:26] <d3lxa> jam: so you mean on the cloud, I could restart mongodb or something?
[15:27] <jam> gnuoy`: juju status by itself cannot create dot output (afaik)
[15:27] <jam> d3lxa: right, on machine-0 on each environment
[15:27] <gnuoy`> jam, it used be a thing though didn't it (maybe pyjuju)? or am I going crazy ?
[15:27] <jam> gnuoy`: I don't know pyjuju very well, it could have been
[15:28] <gnuoy`> ack, thanks
[15:28] <d3lxa> jam: I could try to kill the mongodb instance there and restart with the same command line (the password is xxxxx, i doubt that…)?
[15:29] <d3lxa> I don't know if destroying the env would work then
[15:34] <d3lxa> ok… I'm stuck with juju I can't destroy the env
[15:41] <_benoit_> any juju dev here ? I want to implement a new EC2 compatible provider in juju and want to know If the patches would be welcome
[15:44] <rick_h_> _benoit_: new providers are always welcome. I lot of folks are away today catching up post sprint.
[15:44] <rick_h_> _benoit_: I think an email to the juju list would be a great start
[15:46] <_benoit_> rick_h_: thanks for the answer I will post to the list
[15:47] <rick_h_> _benoit_: awesome, I look forward to seeing the discussion on it
[18:06] <lazyPower> tedg: Its really close. There are some papercuts with it that jose has been working through.
[18:08] <tedg> lazyPower, Papercuts for the small instance case or the large instance case? I'm looking personal.
[18:08]  * tedg is a big guy, but likes small servers
[18:08] <lazyPower> tedg: it needs SSL Certificate generation. I'm running it on a $10 Digital Ocean instance
[18:08] <tedg> lazyPower, Ah, cool. If you could cut and paste that into the bip charm, that'd be cool too :-)
[18:11] <lazyPower> tedg: i've actually got a blog post covering the howto 1 sec
[18:12] <lazyPower> http://blog.dasroot.net/replacing-u1-with-owncloud-on-digital-ocean/
[18:16]  * tedg is reading
[18:23] <tedg> lazyPower, Are you using the $10 instance for the disk space or for the CPU/RAM ?
[18:23] <lazyPower> Both, im' hulk smashing everything on a single instance.
[18:23] <lazyPower> bootstrap + owncloud
[18:23] <sarnold> on a $10 instance? nice
[18:24] <tedg> K
[18:37] <lazyPower> tedg: if you follow that process, let me know how it works for you. i'm doing pretty well with the setup as a single user.
[18:37] <lazyPower> i wouldn't recommend that setup for multi-users though.
[18:37] <lazyPower> it gets a bit pokey when doing n changes on n machines. in my use case, several gb file changes, across 4 clients.
[18:38] <tedg> lazyPower, I'm looking more for shared calendars and addressbooks with my wife, so I'm not too worried about pokey. Don't think that'll be taxing.
[18:38] <lazyPower> yeah, the only downside is the fact you have to purchase caldav addons and carddav through the play store on android phones
[18:39] <lazyPower> i dont have an ios device to test with, so YMMV if you're an iphone user. however the entire stack as a whole works pretty well
[18:39] <tedg> lazyPower, I don't plan on using Android for long, if mhall119 would finish a mail program for me ;-)
[18:39] <lazyPower> heh :) nice
[18:51] <mhall119> tedg: I'm not writing anything :-P
[18:51] <mhall119> tedg: you can help us though, /join #trojita
[18:51]  * tedg gives up and buys a Blackberry phone
[18:51] <mhall119> that's a sound investment
[18:52] <tedg> It keeps me from getting distracted with apps.
[18:52] <mhall119> heh
[19:23] <cory_fu> jose: Hey, are you around?
[20:09] <jose> o/
[20:09] <jose> cory_fu: here I am!
[20:09] <jose> sorry, just got back from an exam
[20:18] <cory_fu> No worries.  Sorry I was less responsive last week, regarding the tracks merge proposal.  I was at a sprint.  :)
[20:18] <cory_fu> I was wondering if you had any ideas about resolving the upstream gem issue in the tracks MP?
[20:19] <cory_fu> I'd like to be able to +1 that, since your changes look fine, but I feel like I need to be able to deploy it to do so
[20:20] <jose> yeah, same here, I'd need to investigate what's really going on
[20:20] <jose> I have some time in like 15, I need to drop a package on the mail and maybe we can work on it?
[20:20] <cory_fu> Sure thing
[20:21] <jose> I'll leave everything bootstrapping and ready to debug
[20:58] <hackedbellini> hi guys
[20:58] <hackedbellini> anyone here knows how can I change the branch a service is using, lets say, from launchpad to a local one? I made some modifications on my postgresql charm and I want to make my service use my local fork without having to deploy it again
[20:59] <hackedbellini> not my postgresql charm, but the one here: https://manage.jujucharms.com/charms/precise/postgresql
[20:59] <hackedbellini> I forked it and did some modifications which I want to use
[21:01] <jose> hackedbellini: `juju deploy --repository=charms local:postgresql` where charms is the directory containing a folder called 'precise' and 'precise' contains the charm
[21:04] <hackedbellini> jose: I used that to deploy a local repository. By doing that, since the service already exists, will it override it in the way I said above (keep the units and just change the charm path to do upgrades)?
[21:04] <jose> hackedbellini: well, I don't think you can upgrade it - it would only pull changes from the repository it was originally created
[21:05] <jose> though you can leave that unit and rename the unit with the local branch deployment to psql maybe?
[21:05] <jose> just put 'psql' or whatever you want at the end (after local:postgresql)
[21:12] <hackedbellini> jose: hrmm, thanks. I'll give it a try :)
[21:12] <jose> np :)
[21:12] <jose> let us know how it went
[21:33] <jose> cory_fu: I have to do some stuff, but I think I'm about to fix the error. if I get to find it I'll push - otherwise I'll ping you tomorrow?
[21:39] <cory_fu> jose: Sounds good.  Thanks for looking into that.  :)
[21:39] <cory_fu> I would have tried my hand at it, but I know less than nothing about ruby.  :p
[22:26] <qhartman_too> I'm looking to consolidate my maas and juju machines into one host; two is overkill. Is there a clean way to bootstrap juju into an lxc, but have future juju instantiated instances be on MAAS bare metal?
[22:27] <qhartman_too> I've found some information on doing everything inside lxc containers, but not a blend, and I'm not super familiar with the guts of what's going on, so was hoping for some pointers to docs I may ahve missed