That's definitely difficult to encapsulate. You can get a mixing of
Apache conventions, your OS of choice conventions, and vendor conventions.

The thing that I usually see is applications installed under /usr/lib
(e.g. /usr/lib/accumulo), the relevant executables linked to /usr/bin to
get them on the $PATH, /usr/lib/accumulo/conf linked to
/etc/accumulo/conf (with indirection for your configuration mgmt tool of
choice -- e.g. alternatives on RHEL-based systems), and
/usr/lib/accumulo/logs linked to /var/log/accumulo.

Typically you would want all of that chown'ed by the accumulo user. Be
sure to chmod /etc/accumulo/conf and /var/log/accumulo 700 to not
inadvertently leak any sensitive configuration or log messages. The rest
of /usr/lib/accumulo can probably just be 755/644 for dirs/files,

This also can map well to development machines if you use /usr/local/lib
for installations and avoid symlink'ing out to /etc and /var.

On 3/19/14, 2:32 PM, Benjamin Parrish wrote:
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB