Server Move

[Owen Winkler]

I'm going to stop paying for the current habariproject.org server on the
31st. IT WILL CEASE TO EXIST.

There is already a new server configured, and most of the important
things are moved there and running properly (yes, including Mediawiki).

Things yet to do on the new server:

* Move SSL Certs
* One last database migration
* Setup of any automated builds
* JibbyBot?
* DNS re-aim

There are probably some things that can wait until they cause pain, but
at least the above would be ideal. I welcome questions generated by
this thread, however given the mid-holiday timeline, please have some
idea how to do or research the thing you want to help with yourself
before you volunteer. Hit me (or anyone else with access) up on #habari
for a login if you need one and don't have it.

Please help where you can, so there's no downtime!

Also, much thanks to moeffju for snatching up the habari.org domain for
us. Pretty awesome.

Thanks everybody!
Owen

[Matthias Bauer]

Here’s an idea to speed up the process: Give me the new IPs and I’ll just change the zone. I’ll put in a record for the old server so we can still access it.

I can also buy a new SSL cert for habari.org (RapidSSL or sth, ~$30/yr).

In my experience it’s easier to fix things that are broken on the new system than to change from one still-running system to another.

--
--
To post to this group, send email to habar...@googlegroups.com
To unsubscribe from this group, send email to habari-dev-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/habari-dev
--- You received this message because you are subscribed to the Google Groups "habari-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to habari-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Owen Winkler]

On 12/20/2013 9:03 AM, Matthias Bauer wrote:

Here�s an idea to speed up the process: Give me the new IPs and I�ll just change the zone. I�ll put in a record for the old server so we can still access it.

I can also buy a new SSL cert for habari.org (RapidSSL or sth, ~$30/yr).

In my experience it�s easier to fix things that are broken on the new system than to change from one still-running system to another.

Works for me.� New IP is 192.241.163.13

[Sean Coates]

On 12/20/2013 9:03 AM, Matthias Bauer wrote:

Here’s an idea to speed up the process: Give me the new IPs and I’ll just change the zone. I’ll put in a record for the old server so we can still access it.

I can also buy a new SSL cert for habari.org (RapidSSL or sth, ~$30/yr).

In my experience it’s easier to fix things that are broken on the new system than to change from one still-running system to another.

Works for me.  New IP is 192.241.163.13

FWIW, when doing a migration like this, I usually set up a reverse proxy on the old box (on HTTP and HTTPS) to forward to the new IP. DNS propagation can't be trusted to work in any sort of predictable way (ISPs ignore TTL, for example).

S

[Chris Meller]

The only problems I've had recently with TTLs being ignored are for less than intelligent bots (Baidu, namely) that I don't care in the slightest about anyway.

I can get the SSL certs moved over now, no problem. Getting the automated builds moved over is more of a problem, those cron jobs are nasty, but I'll take care of those as well.

I can also do the database migration when we're finally ready to pull the plug, but there's no point in doing that until the last minute or we'll just have to do it over again anyway.

I'm all for moving JibbyBot onto the new box. She needs a little TLC in her current state and mainly serves #habari anyway, so it just makes sense. As I've said, I'm also happy to host her if someone objects to her being on hp.o.

--
--
To post to this group, send email to habar...@googlegroups.com

To unsubscribe from this group, send email to habari-dev-...@googlegroups.com

For more options, visit this group at http://groups.google.com/group/habari-dev
---
You received this message because you are subscribed to the Google Groups "habari-dev" group.

To unsubscribe from this group and stop receiving emails from it, send an email to habari-dev+...@googlegroups.com.

[Owen Winkler]

On 12/20/2013 11:09 AM, Chris Meller wrote:
> The only problems I've had recently with TTLs being ignored are for
> less than intelligent bots (Baidu, namely) that I don't care in the
> slightest about anyway.

> I can also do the database migration when we're finally ready to pull
> the plug, but there's no point in doing that until the last minute or
> we'll just have to do it over again anyway.

This is one thing the proxy would serve -- not having to migrate data
multiple times.

One alternative thought I had was to have the old server's sites use the
new server's database, then migrate just once.

[Chris J. Davis]

Either of these would be acceptable I think. Option two would be the least amount of work I would expect.

[Chris Meller]

Setting up the reverse proxy isn't hard either, it just seems like an extra step to me. I'm not concerned about tons of people (as if we got tons of traffic) not having updated DNS, so setting up a reverse proxy for them, rather than just flipping the DNS switch, seems redundant effort.

In any event, we still have to do another database migration, so the timing of it is really academic. Does it matter if it's done before we turn on the reverse proxy or before we flip DNS? Not really...

[Sean Coates]

I'm not pushing for this—especially because I've been so hands-off—but if it's Apache and mod_proxy is installed, it's a pretty easy stanza (even easier if it's Nginx). But up to whoever's doing it, of course.

S

[Chris J. Davis]

Sure, this is just our usual process, no worries.

[Owen Winkler]

Green paint please. Forest green, only.

[Chris Meller]

If someone else wants to handle that, feel free. I'm saying *I* see no point in it, so I'm not particularly motivated in doing it myself.

On Fri, Dec 20, 2013 at 11:34 AM, Owen Winkler <epi...@gmail.com> wrote:

Green paint please.  Forest green, only.

--
--
To post to this group, send email to habar...@googlegroups.com

To unsubscribe from this group, send email to habari-dev-unsubscribe@googlegroups.com

For more options, visit this group at http://groups.google.com/group/habari-dev
--- You received this message because you are subscribed to the Google Groups "habari-dev" group.

To unsubscribe from this group and stop receiving emails from it, send an email to habari-dev+unsubscribe@googlegroups.com.

[Christopher Davis]

Why would you paint a she's green? It should obviously be red.

Sent from my iPhone

> On Dec 20, 2013, at 10:34 AM, Owen Winkler <epi...@gmail.com> wrote:
>
> Green paint please. Forest green, only.
>

[Matthias Bauer]

All the DNS zones are updating now.

On Fri, Dec 20, 2013 at 3:15 PM, Owen Winkler <epi...@gmail.com> wrote:

On 12/20/2013 9:03 AM, Matthias Bauer wrote:

Here’s an idea to speed up the process: Give me the new IPs and I’ll just change the zone. I’ll put in a record for the old server so we can still access it.

I can also buy a new SSL cert for habari.org (RapidSSL or sth, ~$30/yr).

In my experience it’s easier to fix things that are broken on the new system than to change from one still-running system to another.

Works for me.  New IP is 192.241.163.13

--
--
To post to this group, send email to habar...@googlegroups.com

To unsubscribe from this group, send email to habari-dev-...@googlegroups.com

For more options, visit this group at http://groups.google.com/group/habari-dev
---
You received this message because you are subscribed to the Google Groups "habari-dev" group.

To unsubscribe from this group and stop receiving emails from it, send an email to habari-dev+...@googlegroups.com.

[Matthias Bauer]

(It looks like the new server doesn’t have SSL running. That is something we might wanna fix sooner rather than later.)

[Chris Meller]

Yeah, we weren't really ready to switch that yet...

[Owen Winkler]

On 12/23/2013 3:08 PM, Matthias Bauer wrote:
> (It looks like the new server doesn�t have SSL running. That is

> something we might wanna fix sooner rather than later.)
>

SSL is working for me now that I just updated the configs.

Owen