dice-project / dice-deployment-service Goto Github PK

Cassandra Monitoring introduced some changes to the way the dmon-agent has to be installed:

• requires GenericJMX and Java Plugins from collectd (by default they are installed)
  There is a known bug for the java plugin that hardcodes the JDK location in collectd to a specific version. There are two possibilities to fix this:

  • Create a simlink from the actual JDK location to the one needed by collectd (I prefer this quick and dirty hack :) )

  • Compile collectd from the sources
    We had to extend collectd metric type definition database to encompass the new metrics
    We created dice.db which has to be copied to /usr/share/collectd/

• The hardcoding is in /usr/lib/collectd/java.so. The desired location can be listed using:

strings /usr/lib/collectd/java.so | grep jre

• the new dice.db metrics definition has to be copied from <AGENT_HOME>/templates/dice.db to /usr/share/collectd/dice.db

The introduction of MongoDB introduced some new requirements for the installation of the dmon-agent.

• we might require a specific user for monitoring mongodb
  it’s not mandatory but it is recommended for security reasons

• We use the python plugin for collectd which loads from dmon-agent home directory the file called mongodb.py the deployment service only doesn’t have to do anything special as long as the latest version of dmon-agent is used, all new python modules have been upgraded in the requirements.txt

• the new dice.db metrics definition has to be copied from <AGENT_HOME>/templates/dice.db to /usr/share/collectd/dice.db

During the third year we will create a distributed management system for DMON.

It will be able to:

• Scale logstash and elasticsearch instances
• change configuration options

Because of the need to potentially provision additional VMs could we use the Deployment service to
enact these changes?

We will provide the YAML and Chef recipes. Do you think it is feasible?