You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "jan iversen (JIRA)" <ji...@apache.org> on 2013/04/22 00:35:15 UTC
[jira] [Closed] (INFRA-6136) create centOS vm, to run circonus
private agent
[ https://issues.apache.org/jira/browse/INFRA-6136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
jan iversen closed INFRA-6136.
------------------------------
Resolution: Fixed
circonus-broker is up and running, the api seems to work.
> create centOS vm, to run circonus private agent
> -----------------------------------------------
>
> Key: INFRA-6136
> URL: https://issues.apache.org/jira/browse/INFRA-6136
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: LDAP, Puppet, VMWare
> Environment: centOS vm, no special needs for large disks or memory at this point.
> Reporter: jan iversen
> Priority: Minor
>
> As agreed with pctony, I will setup a centOS vm for circonus (alongside with some other tasks).
> I do not have karma to create a new vm, or install OS on a fresh vm, I will however make the setup when I have ssh/sudo access. Alternatively I need some advice on how I can setup a fresh OS.
> The vm (centOS), need to have ldap configured (for login, but also so the circonus agent can check e.g. ldap sync), and puppet to administer the packages.
> Since circonus is going to replace nagios at some future time, the vm placement might be important (apart from the fact that it can be moved later).
> This is not a time critical task, there are plenty of other work on circonus.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira