[08:21] <dholbach> good morning
[08:44] <czajkowski> goood morning
[08:55] <dholbach> hi czajkowski
[09:00] <czajkowski> dholbach: hello how's things?
[09:00] <dholbach> good good :-)
[09:00] <dholbach> how are you?
[09:01] <czajkowski> good taking thursday and friday off this week as USA are off which means I can enjoy the quite time of no email over loading :)
[09:02] <dholbach> very nice
[09:02] <dholbach> we went to see Fat Freddy's Drop last night with a couple of friends - it was a great concert :)
[09:03] <dholbach> salut davidcalle
[09:04] <davidcalle> hey dholbach :) Solved, the main db issue this night with help from #webops, currently deploying
[09:04] <dholbach> woah
[09:04] <dholbach> what was it?
[09:04] <dholbach> great work davidcalle
[09:05] <davidcalle> dholbach, we have a storage volume and with each new deployment, juju attaches the db with this volume. Sometimes, metadata of the volume gets corrupted and juju can't find it.
[09:06] <dholbach> ugh
[09:06] <dholbach> is there a way we can prevent this corruption or do something about it?
[09:06] <dholbach> Or was this old metadata and it won't happen with the new shiny stuff we have now?
[09:07] <dholbach> davidcalle, looks like django cms upstream will very soon release a new major version........... :-)
[09:07] <davidcalle> dholbach, not really, it shouldn't happen, what we can do is detach the volume before each new deployment, but I haven't found clear steps on how to do this
[09:07] <dholbach> ah ok
[09:08] <davidcalle> dholbach, it's really not related to our stack, simply using juju+postgre+storage volumes
[09:08] <davidcalle> dholbach, our Django stack, I mean
[09:08] <dholbach> ok, yep, makes sense
[09:09] <davidcalle> dholbach, hum, no it's failing while doing syncdb : django.db.utils.ProgrammingError: no schema has been selected to create in
[09:09] <davidcalle> dholbach, I need to get some coffee :)
[09:09] <dholbach> more like running a2dissite and a2ensite before and after a deployment (or something)
[09:09] <davidcalle> now*
[09:09] <dholbach> didn't we have the same problem a few days ago?
[09:15] <dholbach> ... at least you said "I need to get some coffee" and not "I need a drink", which in this situation would have been absolutely understandable as well
[09:15] <dholbach> brb
[09:26] <dholbach> ok, looks like they plan to release today
[09:27] <dholbach> so there's probably a bunch more good fixes waiting for us :)
[09:35] <popey> hello!
[09:37] <popey> Who can fix the ubuntu on air calendar? I see a mis-match between the Q&A time today. It says 15:00 UTC but my calendar says 16:00 UTC
[09:53] <dholbach> jose probably
[09:59] <popey> PINGALING JOSE!
[09:59] <popey> :)
[09:59] <popey> dholbach, you and me for Q&A today?
[09:59] <dholbach> sounds good :)
[10:03] <popey> \o/
[10:04] <popey> I'll set it up.
[10:04] <popey> shall we do it at 16:00 UTC or 15:00 UTC dholbach ?
[10:04] <dholbach> 16 would be nice
[10:05] <dholbach> that's the EOD slot it was in before DST changes :)
[10:07] <popey> yeah, will do that
[10:07] <dholbach> awesome
[10:07] <popey> I still don't understand how it moved tbh
[10:07] <popey> oh, it's in jose's calendar, which probably doesn't do DST
[10:08] <dholbach> ah ok
[10:16] <dholbach> I'm going into an early lunch break which will likely consist of yelling at somebody who charged me twice, bbl.
[10:24] <popey> heh
[11:20] <davidcalle> dholbach, solved the db issue. We have a "resetdb" command on the spec that was not doing the right thing (it dropped/recreated the psql db, but forgot to set the right permissions afterwards). New deploy of r145 (the one that we have in prod) with all fingers crossed, then I'll attempt an upgrade...
[11:22]  * davidcalle braces for impact
[11:22] <davidcalle> (after lunch!)
[12:11] <popey> dholbach, when you get a moment, I just uploaded a new music app to the store which needs manual review.
[12:12] <czajkowski> popey: is that because your taste in music is bad :p
[12:12] <popey> OUTRAGE!
[12:12] <popey> Yes.
[12:13] <czajkowski> lol
[12:28] <dholbach> davidcalle, brilliant! thanks!
[12:29] <dholbach> popey, will do
[12:32] <popey> thanks
[12:33] <dholbach> done
[12:33] <popey> o\/
[12:33] <popey> er, \o/
[12:33] <popey> :D
[12:47] <dholbach> davidcalle, django cms 3.2 looks nice
[12:55] <davidcalle> dholbach, indeed :)
[12:56] <davidcalle> dholbach, another issue I've just discovered a change to the spec was making it impossible to select the prod branch revno, it was always pulling latest trunk regardless of what I was asking, leading to a lot of confusion (eg. watching some treebeard config log on 1.6)
[12:57] <dholbach> wow, good catch
[13:01] <dholbach> https://code.launchpad.net/~dholbach/developer-ubuntu-com/django-cms-update/+merge/278447
[13:48] <davidcalle> dholbach, I'm having some issues with prod revno150 (upgraded from 145). It's deployed, but the experience is not great. Can you poke it (try to create pages, etc.) ? https://developer.staging.ubuntu.com/en/
[13:50] <davidcalle> dholbach, since this is taking some time... maybe we should upgrade to 1.9 directly? At this deployment pace, 1.8 will be deprecated the day it reaches prod :D
[13:50] <dholbach> haha
[13:51] <dholbach> davidcalle, I tried to login, but that didn't seem to work
[13:51] <dholbach> "This page encountered an error, don't worry - we have been notified. Please accept our apologies."
[13:51] <davidcalle> dholbach, hmm, it works for me
[13:52] <dholbach> no, not for me - not even in a private window (without cookies)
[13:52] <dholbach> not with firefox either
[13:57] <dholbach> davidcalle, regarding 1.9 I'm a bit unsure as I saw a bunch of deprecation warnings around 1.9 :)
[13:57] <dholbach> so I'm not sure all the stuff we have will work :)
[13:57] <davidcalle> dholbach, right :)
[14:39] <marcoceppi> dpm: I don't know what you did, but it sounds glorious, wrt ubucon deployment
[14:46] <mhall119> dpm: how did you remove the Site objects?
[14:52] <dpm> morning :)
[14:54] <dpm> marcoceppi, mhall119, I went to the django admin, and I changed the Sites object domain from example.com to ubucon.org, as I've done before in other deployments. I must have not been too attentive and pressed Delete instead of Save, with which obviously it deleted it
[14:54] <marcoceppi> dpm: haha, interesting
[14:54] <dpm> live and learn :)
[14:55] <dpm> marcoceppi, I'm thinking rather than trying to fix it, the easiest thing would be a new deployment?
[14:55] <marcoceppi> dpm: yup
[14:55] <dpm> but as I said, I prefered not to do it untily you guys were up
[14:55] <marcoceppi> dpm: if you want to follow along I can show you in the terminal
[14:55] <dpm> marcoceppi, that'd be awesome
[14:57] <dpm> this is like watching TV
[14:58] <marcoceppi> dpm: could you make your terminal a bit wider?
[14:58] <marcoceppi> thanks
[14:58] <dpm> oh, didn't know it affected everyone else's width too
[14:59] <marcoceppi> dpm: yeah, a bit. tmux will resize to the smallest terminal connected to avoid clipping for that person
[14:59] <dpm> ack
[15:02] <marcoceppi> dpm: that's basically it
[15:02] <marcoceppi> dpm: just wait for ubucon/0 to say "ready"
[15:02] <dpm> excellent, thanks
[15:02] <marcoceppi> dpm: finally, the IP address will show up in the top window
[15:02] <dpm> gotcha
[15:04] <dpm> marcoceppi, so we're all set in terms of hosting too? I.e. do you still need to set up the AWS credentials from one of us, or are you using existing credentials from a Canonical account?
[15:04] <marcoceppi> dpm: I created aws credentials for you, this juju is using them
[15:05] <dpm> marcoceppi, ah, ok. I just thought it'd need me to do some action on my side to enable the credentials. Even better if it's transparent
[15:05] <dpm> or is there anything I need to know wrt those credentials?
[15:08] <marcoceppi> dpm: they're available in ~/.juju/environments.yaml but it's safe to ignore them
[15:08] <dpm> ah, gotcha
[15:08] <marcoceppi> dpm: looks like it's ready
[15:09] <dpm> awesome
[15:09] <marcoceppi> http://52.91.47.21/en/
[15:09] <dpm> marcoceppi, a couple of other questions: if I want to temporarily enable the django debug mode config option: is this possible at run time, or just at deploy time?
[15:09]  * dpm starts adding initial content
[15:10] <marcoceppi> dpm: it's a configuration option, but I don't think it works
[15:11] <dpm> marcoceppi, not an issue, I was just wondering why I couldn't make it work
[15:13] <dpm> marcoceppi, also for debugging purposes when working on the site's code, local deployments, etc, it was useful to start/stop gunicorn as it was set up as an upstart job. How can we do that with the new charm?
[15:14] <marcoceppi> dpm: I'll add an action for this, but you can for the time being just run `juju ssh ubucon/0 "sudo service circus restart"`
[15:15] <dpm> marcoceppi, ah, great. I tried all possible things, but didn't know what circus was. That helps!
[15:29] <popey> dholbach, want to pimp us, 30 mins before, now?
[15:33] <dpm> mhall119, call?
[15:33] <mhall119> coming
[15:38] <dholbach> popey, yes, will do
[15:42] <dholbach> done
[15:47] <popey> \o/
[16:00] <dpm> marcoceppi, it seems that on the latest deployment none of the apt-packages in there got installed, without which we cannot upload images. This worked on the deployment you did last week where we uploaded images during the hangout. Any ideas how to debug this?: http://bazaar.launchpad.net/~ubucon-site-developers/ubucon-site/ubucon-layer/view/head:/django.yaml
[16:08] <marcoceppi> dpm: the jusmpstation does not have the deployment
[16:08] <marcoceppi> the deployment is on amazon
[16:08] <marcoceppi> /var/logs/juju doesn't exist
[16:09] <marcoceppi> dpm: try now
[16:09] <dpm> marcoceppi, doh, just realised that, /me facepalms
[16:09] <dpm> thanks
[16:09] <marcoceppi> dpm: the issue was likely permissions
[16:09] <marcoceppi> not missing packages
[16:09] <mhall119> jose: did you get my GSoC notes email?
[16:09] <marcoceppi> dpm: you should bea ble to upload now
[16:09] <dpm> marcoceppi, let me try
[16:10] <dpm> marcoceppi, works perfectly now, thanks
[16:11] <marcoceppi> dpm: I'll fix the base layer
[16:11] <dpm> great, thanks!
[16:11] <mhall119> marcoceppi: what was the cause?
[16:11] <marcoceppi> mhall119: /srv/ubucon was owned by root and not djanog
[16:11] <marcoceppi> django*
[16:11] <mhall119> ah, ok
[16:12]  * dpm continues to add content now
[17:26] <dholbach> all rightie... I call it a day - see you all tomorrow!
[18:00] <jose> mhall119: yes, have them here! thanks!
[18:06] <popey> jose, could you please push the community team Q&A to 16:00 UTC? It's at the wrong time currently (15:00 UTC).
[18:06] <jose> popey: it's been fixed now
[18:06] <popey> ok, thanksQ!
[18:06] <popey> -Q
[19:47] <dpm> mhall119, jcastro, marcoceppi, http://ubucon.org :)
[19:47] <marcoceppi> dpm: sweet!
[19:47] <dpm> thanks so much for help making it possible guys
[19:48] <jcastro> beautiful!
[19:48] <marcoceppi> dpm: I'm going to blog about it if you don't mind (deploying ubucon.org using Django and charms)
[19:48] <mhall119> dpm: \o/
[19:49] <dpm> marcoceppi, absolutely! If you could just wait for tomorrow when we've got more content and we've done the site announcement, then we'll have a bigger reveal effect :)
[19:49] <dpm> I'm going for dinner now, but will be adding some of the content later on
[19:52] <mhall119> dpm: I've uploaded the sponsorship brochure to http://ubucon.org/media/cms_page_media/9/UbuCon_Summit_Sponsorship_Brochure.pdf
[19:52] <mhall119> there's currently a link on http://ubucon.org/en/events/ubucon-summit-us/?edit
[19:53] <mhall119> I wanted to make sure I could easily upload the file
[19:53] <dpm> mhall119, ok, cool, it means I won't have to remember the link, thanks :)
[19:54] <dpm> mhall119, could you follow up with nhaines wrt the meetup registration some time in your day? I pinged him in my afternoon on #ubuntu-locoteams, but he might not have been around yet
[20:01] <mhall119> sure, I'll see if he's available
[20:41] <balloons> jose, did you manage to contact all the flavors?
[21:21] <popey> balloons, jose added tvoss (as per his request) to mentors
[21:27] <balloons> popey, I saw :-) It seems the flavors haven't been asked yet
[21:27] <balloons> I'm happy to send off some emails, just curious
[21:27] <popey> I ased Ubuntu MATE
[21:28] <popey> Martin is considering some tasks, but hasn't committed to be a mentor, I'll keep pushing though :)
[21:28] <popey> *asked
[21:28] <balloons> popey, ;-) I try and remind that they don't have to really mentor the students the same way you'd think of something like GSOC. It's much much more low-key, especially for something like a documentation or outreach task
[21:28] <popey> right
[21:29] <popey> I will impress upon him the lightness of touch :)
[21:29] <balloons> popey, any news from didrocks btw?
[21:29] <popey> Yeah, he's updated the task list, but not complete. Once done I'll get them in the site