[08:59] <NicolasRaoul> for some reason I can't edit the wiki. I can log in, but then I get logged out when I go to another page
[09:00] <NicolasRaoul> anyway, here is the thing I wanted to edit on the wiki:
[09:01] <NicolasRaoul> at https://help.ubuntu.com/community/VirtualBox/Networking the following sentence should be removed because the link is 404 and the info there was not up-to-date anyway: "For more information on the process up to this point, please visit Bridged Networking with VirtualBox on Linux Hosts"
[09:01] <NicolasRaoul> any good samaritan can do the edit? thanks a lot!
[14:17] <head_victim> FYI, I just make the wiki edit requested above.
[18:15] <mhall119> cjohnston: I'm here
[18:15] <m_3> cjohnston: yo
[18:15] <cjohnston> hey..
[18:15] <cjohnston> the dates are 28-31
[18:16] <m_3> is that a gentle rampup or spike on the 28th?
[18:16] <cjohnston> mhall119: would it be possible to run two summit instances on one db
[18:16] <cjohnston> m_3: I would assume a rampup that spikes
[18:16] <mhall119> cjohnston: technically yes
[18:16] <m_3> ok, starting pretty much now?
[18:16] <cjohnston> I would expect the week before people to be looking at what they want to attend, and then the day the conf starts the spike
[18:16] <mhall119> cjohnston: but you might have race conditions if they are both trying to read/write to the same data
[18:16] <cjohnston> m_3: ^
[18:17] <m_3> mhall119: also, separate question... what about a dark spare that's pretty much ready to attach to the db and can fail over to pick up the load?
[18:17] <m_3> mhall119: or is that just too much configuration risk for the reward?
[18:17] <mhall119> m_3: are we talking summit or plumbers?
[18:17] <cjohnston> mhall119: summit for plumbers and the setup
[18:18] <mhall119> for plumbers, if you're using the juju charm with separate instances for django and postgres, it's just a matter of deploying another instance of summit
[18:18] <mhall119> for summit, you'd have to work with IS
[18:19] <cjohnston> we are strictly speaking the plumbers instance
[18:19] <m_3> mhall119: right... I was thinking of attaching the elastic-ip to a proxy in front of django
[18:19] <m_3> mhall119: configure it as a balancer that just has a failover
[18:19] <m_3> (not balancing, so no race conditions)
[18:19] <m_3> but that might be just complicating things with no benefit
[18:20] <mhall119> m_3: yeah, I'm not too familiar with that kind of stuff
[18:20] <m_3> mhall119: ok, thanks
[18:21] <mhall119> m_3: amazon provides some of that, but I don't know how automated the failover can be
[18:21] <m_3> cjohnston: ok, well lets walk through the juju mgmt process in a spare/scratch environment... sometime this week or next?
[18:22] <cjohnston> m_3: for me, Friday of this week or nextweek
[18:22] <m_3> mhall119: oh, wasn't thinking of alb svcs... I was thinking of haproxy or varnish
[18:22] <m_3> cjohnston: cool
[18:23] <m_3> sorry s/alb/elb/
[18:25] <cjohnston> m_3: if we could set something up (can change) but a planned time, that would be helpful
[18:26] <m_3> cjohnston: yeah, was just gonna look at cal
[18:26] <m_3> cjohnston: what TZ you in?
[18:26] <cjohnston> EST
[18:42] <m_3> ok, scheduled... reschedule at will... I'm meeting-free otherwise
[19:02] <cjohnston> Thanks
[23:36] <daker> cjohnston: do you have any LTP db ?
[23:37] <cjohnston> I think so
[23:37] <cjohnston> dont know how old it is
[23:37] <cjohnston> http://ubuntuone.com/2xpQW5q06Yp26f47lboHmb
[23:38] <daker> 404
[23:39] <cjohnston> http://ubuntuone.com/2xpQW5q06Yp26f47lboHmb
[23:39] <cjohnston> I copied and pasted again
[23:39] <cjohnston> same thing
[23:40] <daker> maybe you need to make it public ?
[23:40] <cjohnston> i did
[23:40] <cjohnston> it works for me
[23:40] <daker> ah i know
[23:41] <cjohnston> figure it out?
[23:41] <daker> yes
[23:41] <daker> i use the HTTPS Everywhere extension
[23:42] <daker> so when the link is converted to https it gives 404
[23:42] <cjohnston> ahh
[23:42] <daker> the converted link is https://one.ubuntu.com/2xpQW5q06Yp26f47lboHmb