You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Gavin (JIRA)" <ji...@apache.org> on 2014/06/24 15:28:24 UTC

[jira] [Commented] (INFRA-7946) close down monitoring and monitoring2.

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

Gavin commented on INFRA-7946:
------------------------------

For Infrabot, no we shouldnt move him inhouse with our VMs, we need that external housed separation so he remains up and working when we have downtime of any of our services or infrastructure/datacenters etc.

I think therefore, that we do not close down the machine housing infrabot.

> close down monitoring and monitoring2.
> --------------------------------------
>
>                 Key: INFRA-7946
>                 URL: https://issues.apache.org/jira/browse/INFRA-7946
>             Project: Infrastructure
>          Issue Type: Task
>          Components: Website
>            Reporter: jan iversen
>            Priority: Minor
>
> With circonus in production, we  no longer need 
> monitoring.a.o and monitoring2.a.o
> However before they can be closed we have to
> - move infrabot
> - talk with pquerna about ckl
> - cleanup dns.
> both are hosted at bytemark, and we might consider reusing the vms for something else, like buildbot.



--
This message was sent by Atlassian JIRA
(v6.2#6252)