Moving some tools to different sections

[timurb]

trafficstars

Hi,

I feel some of the tools are not in correct sections:

• Zookeeper, Noah, Doozer and Etcd should be in separate section, something like "Configuration discovery"
• Not sure that facter (of puppet) and ohai (of chef) should be here at all. Or probably they should be in the same section as the previous ones (zookeeper and so on), like "Configuration discovery".
• Salt should be in "Configuration management" section
• ElasticSearch might not be kept here as it does not store logs itself but act as a backend for Logstash etc.
• ossec is here in 2 sections: "Log Files" and "Security", not sure which is correct

What do you think about that?

[silopolis]

• Zookeeper, Noah, Doozer and Etcd could also (better ?) be filed in "Configuration Sharing" or maybe even "CMDB" as AFAIU, discovery comes from the fact that they implement a unified, common configuration repository
• Agreed about facter and ohai as they really discover/collect configuration information
• Salt should indeed be in "Configuration management" section... but is also an orchestrator, as Ansible does, which in turn doesn't appear in this section. We are here touching the limits of a such a hierarchical classification with single entry per project. Maybe a table could give us an axis more of freedom, while tagging could free us completely.
• I too see ElasticSearch as a backend solution having no place here
• About OSSEC, I have it filed in Security/IDS in my bookmark, but stubled again on it yesterday while browsing about logs management so...
• Finally, I've lately discovered this much inspiring presentation https://speakerdeck.com/obfuscurity/the-state-of-open-source-monitoring from which the monitoring section could be adequately subdivided

[timurb]

Ok, I've created #16 for CMDB section then. Not sure how we should handle the rest or leave that as is for now.