Re: [DISCUSS] Metron installation and management - deprecating Ambari support

2019-09-12 Thread Michael Miklavcic
Otto - Also, in reference to the Slack channel note about Ansible - the installation/commands would not be managed by Ansible. We'd likely only use it as needed to do very basic calls out to the install/setup scripts that we would provide for Metron. There's probably some difference between how

Re: [DISCUSS] Metron installation and management - deprecating Ambari support

2019-09-12 Thread Michael Miklavcic
> There is no equivalent usable ‘Metron’ application. That is absolutely part of the problem here. We are a platform on a platform, whereas many of the other projects in the Hadoop stack have very loose coupling/integrations with the other projects. HDF, which NiFi is a part of, would perhaps be

Re: [DISCUSS] Metron installation and management - deprecating Ambari support

2019-09-12 Thread Otto Fowler
I need a little while to think about this, but I would just like to say that NiFi is a really bad example to compare Metron too. Nifi can be deployed as a single zip file and run from wherever it is unzipped. It is more of an application that can be clustered with other instances of that

[DISCUSS] Metron installation and management - deprecating Ambari support

2019-09-12 Thread Michael Miklavcic
I'd like to discuss Metron's installation and management. We have used Ambari for some time now, with and without an MPack for Metron (and Elasticsearch). While this mechanism has proved useful to the project, it is not without cost. This makes us an outlier among Apache projects in terms of what