www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "jan iversen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-6562) SpamAssassin Project needs to replace the aging zone/zones2 Solaris-based boxes
Date Thu, 24 Apr 2014 16:20:28 GMT

    [ https://issues.apache.org/jira/browse/INFRA-6562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13979899#comment-13979899

jan iversen commented on INFRA-6562:

Wrong assumption, as a general rule it is left to the project to inform infra if there is
a need for backup of dynamic data, likewise the project must secure static (configuration)
data in svn. I have just asked and we do not have any backups from the zones, we have a filesystem
that is highly ruined, so picking single files is no fun.

Thanks for the IP information, I will install the original IP from spamassassin.zones.apache.org
( as an alias, and convert the DNS entry to a service entry (no change seen
from the outside).

I will still try to get it done later today or a.s.a.p.

> SpamAssassin Project needs to replace the aging zone/zones2 Solaris-based boxes
> -------------------------------------------------------------------------------
>                 Key: INFRA-6562
>                 URL: https://issues.apache.org/jira/browse/INFRA-6562
>             Project: Infrastructure
>          Issue Type: New Feature
>      Security Level: public(Regular issues) 
>          Components: Zones/Jails
>            Reporter: Kevin A. McGrail
>            Assignee: jan iversen
>            Priority: Blocker
> We are running out of swap or memory on zones/zones2 for SA project ruleQA.  We also
know that the solaris zones are EOL.
> Therefore, the project requests a new zone running CentOS 6.5 with 128GB of diskspace
and 16GB of RAM to replace those zones.  NOTE: Our processes in the past were considered fairly
high on IO and CPU needs.  I don't know if you have notes on the zones/zones2 and why 2 zones
were created but my plan is to consolidate these back to one box to lower administrative headaches
if possible.

This message was sent by Atlassian JIRA

View raw message