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

David M. Lyle commented on METRON-667:
--------------------------------------

1-6 have been completed.

> Reduce Reliance on Ansible for Deployment
> -----------------------------------------
>
>                 Key: METRON-667
>                 URL: https://issues.apache.org/jira/browse/METRON-667
>             Project: Metron
>          Issue Type: Improvement
>            Reporter: David M. Lyle
>            Assignee: David M. Lyle
>
> In our [Dev Guide and Committer Review Guide 
> additions|https://mail-archives.apache.org/mod_mbox/incubator-metron-dev/201701.mbox/%3ca4261414-c763-4b4f-a4c9-6dbb49609...@apache.org%3E]
>  discussion, we had
> a bit of a side discussion about reducing reliance (perhaps to zero) on
> Ansible for our installation.
> It seemed there was consensus around that idea (if not, please let me
> know), so I propose the following steps to get there:
> 1) Refactor existing Ansible deployment to use the Ambari MPack to install
> metron-common, metron-enrichments and metron-parsers.
> 2) Regenerate quick-dev to leverage the change.
> 3) Create rpm packages for all deployed components that don't currently
> have them.
>      - Sensor probes
>      - Sensor stubs
> 4) Create MPack service defs for the RPMs in (2).
> 5) Refactor existing Ansible deployment to use the Ambari MPack to install
> all services.
> 6) Regenerate quick-dev to leverage the change.
> 7) Plan iteration 2 to see if there are other opportunities to reduce our
> use of Ansible.
> One note: if we decide to go this direction, it'd be helpful if, during the
> transition, we stopped adding additional Ansible deployment code.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to