[02:03] <jose> lazyPower: do you have some time to review the charm now?
[02:03] <lazyPower> going over it as we speak
[02:03] <jose> my brain is burnt from homework and it needs some relaxing
[02:03] <jose> cool
[02:03] <lazyPower> have you started classes already?
[02:03] <lazyPower> i thought you weren't headed back until next month
[02:03] <jose> yeah, 8 days ago
[02:03] <lazyPower> right on
[02:19] <jose> lazyPower: any updates?
[02:20] <lazyPower> jose: i'm a little concerned that we are version locking the deployment
[02:20] <jose> hmm, let me check something and I'll be back in a minute
[02:20] <jose> (possible answer to that)
[02:21] <jose> KABOOM!
[02:22] <jose> owncloud-latest is the same as the latest version, not only for upgrades
[02:22] <jose> let me fix that part of the charm (or see if I can do it)
[02:25] <jose> looks like a simple fix
[02:29] <lazyPower> jose: md5 checking as well, so what i think we need to do is either pull it from the source tree and provide git tag/branch checkout
[02:30] <lazyPower> or we need to defalt to from source and provide ppa installation options since there is a suse build tree
[02:30] <lazyPower> this will help "future proof" the charm
[02:30] <lazyPower> and we can work on the plugin manifests getting disabled from there
[02:30] <jose> hmm, I was thinking on pulling both owncloud-latest.tar.bz2 and owncloud-latest.tar.bz2.md5 to get the latest version on install
[02:33] <lazyPower> hmm...
[02:33] <lazyPower> ok i'll allow it
[02:33]  * lazyPower does the juju blessing on jose's efforts
[02:33] <jose> :P
[02:34] <jose> ok, let's test-deploy
[02:35] <lazyPower> jose: link me the diff
[02:35] <lazyPower> i've got a 4.x already populuated with plugins and data ready to test teh migration
[02:35] <jose> lazyPower: if you do upgrade-charm it should be good to go
[02:36] <jose> the only move I'm doing from the branch pushed is the install hook
[02:36] <lazyPower> so you're only changing the package names in the source?
[02:36] <jose> on the install hook, yes
[02:36] <lazyPower> ah ok, got it
[02:36] <lazyPower> just re-merged and i saw the change
[02:37] <jose> cool!
[02:39] <lazyPower> jose: have you noticed that after you deploy the unit, and set a username, you're still prompted to create a user on first run?
[02:39] <jose> lazyPower: yep, I think those variables should be eliminated
[02:40] <lazyPower> we have to keep them around due to backwords compatibility. There's either a) a way to fix them, or b) we need to udpate the config.yaml to note they are depreciated
[02:40] <lazyPower> my inclination is towards a)
[02:41] <jose> ok, let me check that before I do the deploy
[02:41] <lazyPower> jose: awesome. validated the upgrade is non destructive
[02:42] <lazyPower> and looking at the plugin manifests, they change from version to version, so the re-enablement of the plugins is a non-issue from what i can see. i'm still nosing about
[02:43] <lazyPower> and your charm upgrades are compliant with: http://doc.owncloud.org/server/6.0/admin_manual/maintenance/update.html
[02:43]  * lazyPower thumbs up
[02:43] <jose> cool
[02:43] <jose> now I'm checking that username/password thing
[02:44] <lazyPower> let me try again with a multi-user install, and validate we aren't going to hurt anyone thats got more than one user, since thats the last thing i can think of as an edge case
[02:45] <jose> lazyPower: did you do the deploy as a standalone instance or with mysql?
[02:45] <lazyPower> both
[02:46] <jose> because as far as I can see here, the admin and pass config options only work with mysql, they're called for on the db-relation-changed hook
[02:46] <lazyPower> right
[02:46] <lazyPower> its called out in the README
[02:47] <lazyPower> tbh i had not reviewed the readme this go-around. Thats why it wasn't nacked on the first review.
[02:47] <lazyPower> so, disregard the instructions above
[02:49] <jose> ok, no touching user/pass!
[02:49] <jose> deploying a fresh instance with the charm
[02:52] <jose> lazyPower: a bit offtopic, do you know how to make 'juju stauts' an alias for 'juju stauts'? :P
[02:53] <lazyPower> not with the space no, but i have however set an alias as js='juju status'
[02:55] <jose> juju stauts is a common typo of mine
[02:57] <lazyPower> i'd just alias it toi something shorter to type
[02:57] <lazyPower> all my common commands are shortened like that in a ~/.bash_aliases file i version
[02:57] <jose> yep, js may be a good idea
[03:03] <lazyPower> allright, i've valided with nfs, mysql, and standalone options from -current to your proposed MP
[03:03] <lazyPower> everything seems to be in order
[03:03] <jose> houston, we have a problem
[03:03] <lazyPower> what'd you find?
[03:03] <jose> yesterday I found a bug on owncloud itself, the -latest.tar.bz2.md5 hash is not updates, which would cause an endless loop in the md5 check
[03:04] <jose> we would need to hardcode the md5 until they fix it
[03:04] <lazyPower> leave it as the orig tarball
[03:04] <lazyPower> i'll have another charmer check in the morning, and once it's acked i'll merge it
[03:04] <jose> like 6.0.2 instead of latest?
[03:04] <lazyPower> yeah, you said 6.0.2 is the same as latest at present
[03:04] <jose> yep
[03:05] <jose> I'd need to change that in both install and upgrade-charm then
[03:05] <lazyPower> you can revert the patch that applies the -latest
[03:05] <jose> oh, there isn't, I did everything in one shot
[03:06] <jose> I'll just push
[03:07] <jose> let me do a final test
[03:11] <lazyPower> i just left a comment that it looks good to me. I dont want to merge this as its 11:10, and i'm pretty tired. I may have missed something but i checked it with all the configurable relationship options
[03:11] <lazyPower> i'm confident this is a high quality patch adn will have no problems being merged
[03:11] <jose> it's good :)
[03:11] <lazyPower> great work Jose
[03:11] <jose> thanks lazyPower :)
[03:12] <lazyPower> allright man, thats me.
[03:12] <lazyPower> i'm out
[03:12] <jose> you have a good night!
[08:49] <gep> !list
[11:51] <manuel_> hello, i'm trying  to get the LXC Provider to work for me. I have had some trouble with lxc but everything seemed to work, until! i reboot the machine (latop). I then can not connect to my cloud anymore. If i destroy and bootstrap the environment again it works. but, shouldn't that environment survice reboots? The error i get after reboot of Host Machine  http://dpaste.com/1776409/
[12:04] <will1> hi all, I'm trying to install the Vagrant image with Juju pre-installed : precise-server-cloudimg-amd64-juju-vagrant-disk1.box from https://juju.ubuntu.com/docs/config-vagrant.html but it looks like they're no longer available. Has the link changed?
[12:07] <manuel_> will1: i was having the same problem. I'm trying the ones for raring now: http://cloud-images.ubuntu.com/vagrant/raring/current/raring-server-cloudimg-amd64-juju-vagrant-disk1.box
[12:09] <will1> manuel_: I thought I looked in the raring directory. but that's cool, raring will work for me. many thanks, much appreciated :-)
[13:45] <jcastro> jose, while we finish up the review, you want to do the honors blogging the announcement of the updated owncloud charm?
[13:52] <jcastro> jose, lazyPower: hey the owncloud guys publish ubuntu packages
[13:53] <jcastro> that means we could use those instead of the tarballs, so we don't have to update the charm on every owncloud release
[13:53] <jcastro> I'll file a bug
[13:54] <lazyPower> jcastro: yeah from the suse build service right?
[13:54] <lazyPower> i was looking for a PPA
[13:54] <jcastro> yeah
[13:55] <jcastro> https://bugs.launchpad.net/charms/+source/owncloud
[13:55] <jcastro> we can resolve some of these bugs
[13:59] <jose> jcastro: I'd love to, but I'm at university now, if you give me a couple hours I'll be happy to do it
[13:59] <jcastro> jose, I mean eventually!
[16:24] <X-warrior> What could be the reason that a juju status shows all agent-state as down on my machines?
[16:44] <cjohnston> I'm trying to use juju-local.. my bootstrap works, but then when I try to run juju-deployer it tries to deploy, but I get stuck with juju status looking like http://paste.ubuntu.com/7235656/
[16:44] <cjohnston> any ideas?
[16:49] <jose> I'm back home, blogging now
[16:49] <avoine> cjohnston: it looks like lxc can't starts virtual machines, do you have your cgroup mounted and all depdendencies installed?
[16:51] <avoine> cjohnston: maybe you could try with this command: sudo lxc-create -t ubuntu
[16:51] <avoine> to see if lxc is wokring
[16:51] <avoine> *working
[16:51] <cjohnston> avoine: I installed juju-local.. I do have other containers that I have created and they work
[16:51] <gnuoy> cjohnston, is this a trust host deploying precise ?
[16:51] <cjohnston> gnuoy: yes
[16:51] <gnuoy> cjohnston, I raised https://bugs.launchpad.net/juju-core/+bug/1306537 this morning
[16:52] <_mup_> Bug #1306537: LXC provider fails to provision precise instances from a trusty host <juju-core:New> <https://launchpad.net/bugs/1306537>
[16:52] <cjohnston> gnuoy: ack.. things are working for ev and vila, I guess I'm the unlucky one
[16:53] <gnuoy> cjohnston, well, if you get a fix I'd love to hear about it
[16:53] <cjohnston> avoine: I don't see any docs about other deps or cgroups or anything like that?
[16:54] <gnuoy> cjohnston, have you tried deploying a trusty unit out of interest?
[16:55] <cjohnston> gnuoy: just the bootstrap
[16:55] <gnuoy> I can fire up cs:trusty/ubuntu no problem
[16:55] <cjohnston> let me see if I can get trusty to wrok
[16:55] <cjohnston> work
[16:57] <gnuoy> fwiw this is what my lxc env looks like having deployed a trusty and precise service http://pastebin.ubuntu.com/7235731/
[16:57] <cjohnston> #2 is exactly what mine was looking like
[17:02] <cjohnston> gnuoy: how long did it take for cs:trusty/ubuntu to come up?
[17:04] <cjohnston> gnuoy: it came up.. :-/
[17:04] <gnuoy> pretty much instant
[17:12] <cjohnston> gnuoy: did things work for you two days ago?
[17:12] <jose> jcastro, lazyPower: would http://software.opensuse.org/download/package?project=isv:ownCloud:community&package=owncloud work good for replacing the tarball on the owncloud charm?
[17:13] <gnuoy> cjohnston, I couldn't say exactly when it broke but it was pretty recent
[17:13] <lazyPower> jose: it could
[17:13] <lazyPower> and probably should. Offer it as an option
[17:13] <cjohnston> gnuoy: there were a few lxc related changes that landed yesterday
[17:13] <lazyPower> to use the PPA or to use Source
[17:13] <jose> lazyPower: got it!
[17:13] <lazyPower> there are going to be nuance diferences in the packages
[17:13] <lazyPower> i believe the ppa will install it to /usr and symlink, i may be wrong.
[17:14] <cjohnston> gnuoy: sorry.. a few days ago
[17:16] <jose> I'll check how it works and then modify the charm if it seems appropriate
[17:18] <jcastro> jose, yeah that's what I was thinking
[17:18] <jose> cool, I'm deploying an ubuntu instance and will check how it behaves
[18:02] <lazyPower> Woo, looks like we have changes on the vagrant images
[18:02] <jcastro> Reminder, charm school in ~60 minutes
[18:03] <jose> 'how to approve an MP jose is about to submit'
[18:29] <lazyPower> hey jcastro, i think our charm school is going to need to be cancelled. I've run into a blocker. Do we have another idea we can sub in?
[18:30] <jcastro> do we have a mac available?
[18:30] <jcastro> so hey basically, the juju-specific box went away
[18:30] <jcastro> so our docs don't even link to the right boxes right now (fix is in a PR, just added it)
[18:31] <jcastro> lazyPower, can you resolve your issue in the next 15 minutes?
[18:31] <marcoceppi> But those boxes don't have juju installed and bootstrapped already
[18:31] <lazyPower> jcastro: actively trying to do so
[18:31] <jcastro> it's installed, just not bootstrapped
[18:32] <jcastro> marcoceppi, the boxes disappeared, I don't think Ben is working today so I have no idea where they're supposed to be
[18:32] <lazyPower> i'm getting lxc container errors on this box when i attempt to boot services. this is eminating from both the precise64 and trusty64 box
[18:32] <lazyPower> let me fetch a 32box and see if they exhibit the same behavior
[18:34] <jcastro> man, the entire vagrant page in the docs is depending on the juju boxes existing
[18:35] <jcastro> I wonder how long they have been missing and we didn't notice. :-/
[18:36] <jcastro> I'd like to punt this to next friday, we need to get these images back from ben
[18:36] <jcastro> I mean, we could do it with the vanilla image, but we'd end up doing port forwarding config and a bunch of metawork before we even get started
[18:37] <lazyPower> jcastro: that's not going to be awesome
[18:37] <lazyPower> jcastro: the containers on precise32 are forever pending... still waiting to see if there's a change
[18:37] <lazyPower> but its not looking good
[18:37] <jcastro> ok so let's punt one week, I'd rather not suck.
[18:38] <lazyPower> i'm game for that idea. We can even do a how to macguyver your own juju dev environment
[18:38] <lazyPower> which i wouldn't mind doing
[18:38] <lazyPower> its fun
[18:39] <lazyPower> ok we have a machine up. the boot time was 8 minutes on this vagrant image with 2gb of ram allocated
[18:41] <jcastro> hey so, idea
[18:41] <jcastro> is there a place we can run a test that returns every link in j.u.c/docs that 404's?
[18:42] <jose> jcastro: just on time before the tweet went off
[18:43] <jose> for that you mean, every link on that page or also on the subpages?
[18:44] <jcastro> I mean every link in the docs, all of them.
[18:44] <jcastro> so that when something moves or breaks, we know about it
[18:44] <jose> oh, automatically
[18:44] <jose> I could've used a link checker manually
[18:45] <lazyPower> jcastro: i have a utility i wrote
[18:45] <lazyPower> let me fish that up after i'm out of this meeting
[18:47] <jcastro> yeah it just needs to be automatic and on a production box, not some VPS, etc.
[18:48] <jcastro> maybe on the same box that builds the docs
[18:48] <jcastro> evilnickveitch, what do you think?
[18:48] <lazyPower> jcastro: its a ruby script, so it'll probably get nacked
[18:49] <jcastro> yup
[18:49] <jcastro> I'll ask around, maybe someone on webops can recommend something, surely we can't be the only ones with broken URLs
[18:54] <evilnickveitch> jcastro, yes, I think I mentioned this months ago. There is a lint.py tool in the tools dir that checks for bug refs
[18:54] <evilnickveitch> ideally we should add it to that
[18:54] <jcastro> ah! Perfect
[18:54] <jcastro> I'll file a bug
[18:55] <evilnickveitch> jcastro, ok
[19:18] <evilnickveitch> jcastro, cool - I just discovered the footer has a load of broken links
[19:18] <jcastro> nice!
[19:37] <mhall119> jcastro: marcoceppi: can either of you help me with swift?
[19:37] <mhall119> I'm trying to learn how to setup a bucket on canonistack
[19:37]  * jcastro is dumb wrt. swift
[20:23] <cory_fu2> I'm getting a connection refused error whenever I try to juju status or juju destroy-environment on my local env
[20:23] <cory_fu2> Should I manually delete .juju/local and .juju/environments/local.jenv?
[20:37] <arosales> lazyPower: do you have a pointer to your "clean up local provider files"
[20:38] <lazyPower> @cory_fu2 first off do a lxc ls
[20:39] <lazyPower> make sure there are no running containers left behind. The script we wrote was pretty destructive on active environments and didn't segregate against anyone doing work with another platform like docker.
[20:40] <lazyPower> cory_fu2: aside from that, you manually delete some files and there's an AU post on it let me fish that up
[20:40] <lazyPower> http://askubuntu.com/questions/403618/how-do-i-clean-up-a-machine-after-using-the-local-provider
[20:41] <lazyPower> @cory_fu2 ^
[22:34] <themonk> after update in juju 1.18 and clean local bootstrap i tried to deploy apache2 but geting this error in machine 1 "agent-state-info: '(error: container failed to start)'"
[22:34] <themonk> marcoceppi: after update in juju 1.18 and clean local bootstrap i tried to deploy apache2 but geting this error in machine 1 "agent-state-info: '(error: container failed to start)'"
[23:23] <marcoceppi> themonk: 1.18.1 was just released
[23:24] <marcoceppi> try that and see if it's still broken
[23:36] <jose> lazyPower: have a second?
[23:50] <jose> marcoceppi: ping