On Mon, 24 Feb 2014 10:45:09 +0100
Aurélien Bompard <gauret(a)free.fr> wrote:
> So, next steps:
> * Create some kind of test list on the prod instances.
> * Put in place aliases on collab03 -> mailman01/02 for smtp.
> I guess we need to point at one? Or do MXes?
> * Setup apache redirect for
> * Test a bunch. ;)
Alright, the two prod servers are setup, I've created a test list
which answers to test(a)lists.fedoraproject.org on them,
Amusingly, thats already the name of our qa list. ;)
Could you rename something like 'mailman3' or another random name thats
so we can now
put redirects in place from collab03 to mailman01, in SMTP and HTTP.
We can start with mailman01 only for HTTP, I just realized that the
full-text index is file-based, so it needs to be on a shared
filesystem for mailman02 to access it. But that does not prevent us
from testing the rest.
ok. We do now have a gluster role (thanks Ralph!) So we could spin up
gluster between them.
What all data needs to be shared again? Perhaps this is better a netapp
Can I just have access to collab03 to setup the redirects, or does
someone with a better knowledge of the whole picture want to setup
them? (it's prod, after all)
I'd be happy to help, but I also added you to sysadmin-tools a while
back so you should have sudo on collab03.
I guess we need to add aliases for the testing list that send it all on
to mailman01.vpn and then tweak apache config to redirect the web side?