[
https://issues.apache.org/jira/browse/METRON-214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15378329#comment-15378329
]
ASF GitHub Bot commented on METRON-214:
---------------------------------------
Github user cestella commented on the issue:
https://github.com/apache/incubator-metron/pull/191
Why do we not have a separate PR per JIRA?
It appears that the various tasks have various authors, wouldn't it be
better to have each author submit their own JIRA so that they can be listed on
the commit?
Also, this isn't the complete set of tasks for METRON-214, so when we close
this JIRA, it won't be the complete body of work for METRON-214, just a portion.
> Build RPM Packages for Deployment
> ---------------------------------
>
> Key: METRON-214
> URL: https://issues.apache.org/jira/browse/METRON-214
> Project: Metron
> Issue Type: Improvement
> Reporter: David M. Lyle
> Assignee: David M. Lyle
> Labels: 0.2.1BETA
> Fix For: 0.2.1BETA
>
>
> In order to allow yum install of core Metron functionality, create a RPM to
> package the build artifacts required to install "Metron Core".
> Parser Topologies
> Enrichment Topology
> Writer Topologies
> Metron Helper Scripts (initd/systemd, zk loaders, etc)
> Streaming Enrichment Topologies
> PCAP Service
> RPM install scripts will handle configuration and start up of deployed
> components.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
