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-7946) close down monitoring and monitoring2.
Date Tue, 24 Jun 2014 13:52:24 GMT

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

jan iversen commented on INFRA-7946:
------------------------------------

A very good argument.

but how does that compare with the fact that circonus-broker.a.o is inhouse, thats the software
that
- monitor all our internal stuff (ldap, svn etc.)
- communicate with #asfinfra
- update status.a.o

Maybe I should split brokercontroller in 2:
- a part which monitors internal services (and need private lan)
- a part that updates status.a.o and communicates with #asfinfra.

the last part should then run externally.


> 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)

Mime
View raw message