[
https://issues.apache.org/jira/browse/METRON-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Leet updated METRON-349:
-------------------------------
Description:
Metron services are typically run under the storm user (e.g. spinning up
topologies). The mpack deploy creates a Metron user and group. This install
should be updated to be running and deploying as the metron user.
In addition, many of the files are created or owned by users like the storm
user (e.g. in HDFS). These files should also be owned by the metron user, and
permissions restricted from 775.
Notably, METRON-796 resulted from a partial fix to this. This ticket is the
more complete solution to the ownership problem (796 is intended only to get
things back in working order, and will actually revert ownership from
metron:metron to metron:hadoop to allow storm user to write)
was:Currently, Metron services are run under the root user- change this to
run under a Metron user.
Summary: Switch ownership of topologies and files to metron user and
update perms (was: Switch Metron User from root to metron)
Updated this ticket to be more complete per discussion on:
https://github.com/apache/incubator-metron/pull/488
The original intent is still valid, but a bit outdated and incomplete, so this
ticket title and description is updated appropriately.
> Switch ownership of topologies and files to metron user and update perms
> ------------------------------------------------------------------------
>
> Key: METRON-349
> URL: https://issues.apache.org/jira/browse/METRON-349
> Project: Metron
> Issue Type: Improvement
> Reporter: David M. Lyle
> Labels: deployment, platform
>
> Metron services are typically run under the storm user (e.g. spinning up
> topologies). The mpack deploy creates a Metron user and group. This install
> should be updated to be running and deploying as the metron user.
> In addition, many of the files are created or owned by users like the storm
> user (e.g. in HDFS). These files should also be owned by the metron user,
> and permissions restricted from 775.
> Notably, METRON-796 resulted from a partial fix to this. This ticket is the
> more complete solution to the ownership problem (796 is intended only to get
> things back in working order, and will actually revert ownership from
> metron:metron to metron:hadoop to allow storm user to write)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
