[03:16] <lazyPower> balboah: Yep. Considering MAAS has no idea how to communicate with the machines through a virtualbox's hypervisor. If you were testing with KVM you could setup the machines power management via virsh and it would properly start/stop the instances.
[03:17] <jose> it looks like someone's not partying this weekend
[03:21] <jose> lazyPower: checking how to implement that
[03:21] <lazyPower> eh i'm only around for a bit longer. Doing a Digital Ocean juju deployment of owncloud and documenting the process
[03:22] <lazyPower> we need to get SSL support on this charm before we can make it a suggested path forward
[03:22] <jose> that's what I meant, I'll check and see what can I do with the charm
[03:22] <lazyPower> also, i would nack your deb install - because you removed the option to install from source :(
[03:22] <lazyPower> it should be extended, with the deb being the default
[03:23] <jose> I haven't removed the option to install from source?
[03:23] <lazyPower> wat
[03:23] <lazyPower> let me double check, when i scanned the MP i saw red over the source installations
[03:24] <jose> sure
[03:24] <lazyPower> ok, thats what i get for not looking closer
[03:24] <lazyPower> you added the option. right on
[03:24] <jose> yeah :P
[03:25] <lazyPower> jose: i'll nack it just to make you ask questions, cuz i'm a spaz like that ;P
[03:25] <jose> :P
[03:27] <lazyPower> jose:  you dont remove the .migrating file in here after restoring the data.
[03:27] <lazyPower> looking athttp://bazaar.launchpad.net/~jose/charms/precise/owncloud/port-change+repo-support/view/head:/hooks/upgrade-charm
[03:28] <jose> oh, whoops, will fix that now
[03:31] <jose> fixed!
[03:32] <jose> lazyPower: a problem I find with SSL is the cert, but if you have to go I think we can discuss this on Monday
[03:32] <lazyPower> Certs are a solved problem
[03:32] <jose> huh?
[03:32] <jose> self-signed?
[03:32] <lazyPower> yep
[03:33] <lazyPower> Look at charm helpers SSL module
[03:33] <lazyPower> and other charms that have a ssl-everywhere branch. They use charmhelpers to build the self signed certs
[03:33] <lazyPower> i plugged the modification into Nagios about a month ago
[03:33] <jose> hmm, I'll check
[03:35] <jose> I should mention, charm-tools failed to build on the PPA
[03:43] <lazyPower> jose: charmhelpers != charm tools
[03:44] <jose> ack
[03:44] <jose> oh, do you have a minute to check on my amulet test?
[03:45] <jose> seems to be failing, no idea why
[03:45] <lazyPower> link to code + output?
[03:45] <jose> code is https://code.launchpad.net/~jose/charms/precise/subway/add-tests
[03:45] <jose> and I'm running the test now to get the output
[03:46] <lazyPower> haha, you took my approach of using splinter
[03:46] <lazyPower> awesome
[03:46] <lazyPower> theres one problem with this approach - it will fail CI consistently
[03:47] <lazyPower> for whatever reason teh dependencies never get loaded properly
[03:47] <jose> hmm, maybe that's the problem
[03:47] <jose> I remember something about a file not being found
[03:47] <lazyPower> I would just use python requests and parse the output for abs match's
[03:47] <lazyPower> eg: <title>Subway</title>
[03:48] <jose> hmm, ok, I'll investigate tha
[04:05] <lazyPower> hah cool
[04:05] <lazyPower> this seems to work pretty well
[04:05] <lazyPower> re: owncloud on DO with a 1GB memory provider and a single user
[04:10] <lazyPower> jose: did you add the desktop client and interface with this at all when you were testing?
[04:11] <jose> lazyPower: desktop client and interface? huh? what?
[04:11] <lazyPower> jose: there's a desktop client for owncloud, akin to the ubuntu1 desktop client for sync'ing content to owncloud
[04:11] <jose> I didn't test it with that
[04:11] <jose> I can test it now, though
[04:12] <lazyPower> http://i.imgur.com/LE4yd7F.jpg
[04:12] <lazyPower> i'm putting it through the ropes as we speak
[04:12] <lazyPower> syncing about 8gb worth of content
[04:13] <jose> \o/
[04:13] <jose> thank you
[04:13] <jose> my upload speed is 20KBps
[04:15] <lazyPower> jose: yeah i've got ya beat. this is with the sync in progress - http://www.speedtest.net/my-result/3450193516
[04:16] <jose> I want those speeds! :(
[04:20] <lazyPower> and, done
[04:20] <lazyPower> not bad
[04:21] <lazyPower> with a single client this setup works pretty well. I need to make some files collide
[04:21] <lazyPower> see how it handles it, but i'm pretty happy with the results of this
[04:21] <jose> awesome!
[04:21] <jose> I tried with two users on the same instance, but we didn't get to upload too many files
=== CyberJacob|Away is now known as CyberJacob
=== Ursinha is now known as Ursinha-afk
=== Ursinha-afk is now known as Ursinha
[20:29] <ghartmann> my juju local provider machines lock on pending state and never get delivered, I tried finding hints on the logs but I couldn't find anything
[20:34] <jose> ghartmann: it's a known bug (bug 1309805)
[20:34] <_mup_> Bug #1309805: LXC / Local provider machines do not boot in 1.18 / 1.19 series <juju-core:Confirmed> <https://launchpad.net/bugs/1309805>
[20:35] <jose> can you mark that it affects you, please?
[20:39] <ghartmann> I am using local providers to validate my charms
[20:40] <ghartmann> so it is a blocking issue
[20:40] <ghartmann> what alternatives do I have ?
[20:42] <ghartmann> do we have an older ppa that would point to an working version ?
[20:46] <jose> ghartmann: not exactly, you may use other providers such as EC2
[20:46] <jose> if you are new to EC2 I can help you configure it with juju for free usage for a year (they give a free tier)
[20:53] <ghartmann> I have used EC2 for a few years it's just that I am prototyping locally now
[20:54] <ghartmann> I was very happy on how quickly I could spin dbs and apps on my local server
[20:55] <ghartmann> so I moved from using vagrant+lxc to juju
[20:56] <jose> yeah, unfortunately that bug's preventing from deploying in local
[20:56] <jose> unless... let me try something
[21:00] <jose> nope, I don't know of a workaround
[21:01] <ghartmann> ah, well ...
[21:02] <ghartmann> it's go now right ?
=== Bing is now known as Guest32412
[21:02] <jose> what?
[21:02] <jose> you mean, the language juju-core is written in?
[21:03] <ghartmann> yes
[21:03] <jose> yes, golang
[21:03] <ghartmann> I will see if I can find out why it is getting in this state
[21:04] <jose> cool :)
[21:04] <jose> #juju-dev may have people who know about it more than myself
[21:04] <ghartmann> not so familiar with go though
[21:05] <ghartmann> ha thanks .. didn't knew about this channel