[
https://issues.apache.org/jira/browse/METRON-214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15375202#comment-15375202
]
David M. Lyle commented on METRON-214:
--------------------------------------
Currently, it looks like this will be broken down into a series of PRs that
will come in the following order.
1) METRON-306 - Docker Container for rpmbuild and a readme.
2) METRON-299 - Parser RPM, METRON-300 - Enrichment RPM, METRON-302 - Metron
Common RPM
3) The rest of the RPMs
4) Automation scripting of RPM builds
5) Automatic deployment of RPM to hosted environment (we'll need to figure out
where this is)
6) Refactor of Ansible scripts to use RPMs
The notion is to push out the RPMs as quickly as possible without introducing
breaking changes in the deployment scripts. Happy to hear alternative
approaches.
> 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)
