[
https://ovirt-jira.atlassian.net/browse/OVIRT-725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20500#comment-20500
]
Marc Dequènes (Duck) commented on OVIRT-725:
--------------------------------------------
As for the MX2, counting on Linode is irrelevant because there is JIRA task
OVIRT-424 about stopping use of Linode services. So the MM3 VM is to take over
the MX1 role and is in PHX, we should find another place for it.
For better redundancy having it on another location in the world would be
better (electric outage happen from time to time in a datacenter, networking
problems also). I'm not sure of the resources in the oVirt project. Seems
Alterway was used, but no more. We may ask IT to do this function. Also, inside
the Community Cage project, the OSAS team wants to provide basic services like
this to community projects, so this may also be an option.
> install secondary MX server
> ---------------------------
>
> Key: OVIRT-725
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-725
> Project: oVirt - virtualization made easy
> Issue Type: Task
> Components: Mailing lists (Mailman)
> Reporter: Evgheni Dereveanchin
> Assignee: infra
>
> We currently just have a single MX record and mail server. For better
> reliability it's a good idea to set up a secondary MX that would act as a
> relay. This can help during primary MX maintenance as mail will be
> accumulated on the secondary MX and flushed to the primary once that comes up.
--
This message was sent by Atlassian JIRA
(v1000.319.1#100012)
_______________________________________________
Infra mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/infra
