You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@metron.apache.org by "James Sirota (JIRA)" <ji...@apache.org> on 2016/01/11 20:19:39 UTC

[jira] [Commented] (METRON-10) Storm Flux

    [ https://issues.apache.org/jira/browse/METRON-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15092515#comment-15092515 ] 

James Sirota commented on METRON-10:
------------------------------------

Hi Guys, what is the status on this?  Ryan from Hortonworks is getting close to pushing out the automated deployment scripts for Metron (probably will be done late this week or early next week) and we would like to know if we need to incorporate Flux changes prior to releasing the scripts or if we should release the scripts first and then incorporate Flux later

> Storm Flux
> ----------
>
>                 Key: METRON-10
>                 URL: https://issues.apache.org/jira/browse/METRON-10
>             Project: Metron
>          Issue Type: Improvement
>            Reporter: Sean Schulte
>
> Switch to using Storm Flux for defining and running topologies.
> This simplifies configuration and makes it much more apparent which bolts are actually used in each topology, just by changing a yaml file.
> We'll end up with two yaml files for each topology (a "local" and "remote"), as well as an override file for shared environment values.
> This will also allow us to delete almost all of the Java code in the OpenSOC-Topologies that currently constructs and runs topologies.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)