[GitHub] metron issue #916: METRON-1434 - Ability to deploy Metron full dev as a sing...
Github user as22323 commented on the issue: https://github.com/apache/metron/pull/916 Hello, Just wondering what the the /contrib is folder for? If the files in /contrib is not part of the core maintenance(continuous update for n+1) then perhaps we can make a reference to the Vagrant/AWS deployment method in this doc [metron-deployment/other-examples/README.md](PR 980) then store the code and the "notice that sets expectation" in the /contrib folder. Right now PR 980 points to the Vagrantfile at our github site (as apposed to putting it into /contrib folder within the Apache Metron project). The proposed update could look like this (see file path structure): The README.md here will list the Vagrant/AWS method. https://github.com/LTW-GCR-CSOC/metron/tree/master/metron-deployment/other-examples The readme.md in this path can refer to the "notice" and Vagrantfile in the /contrib folder: https://github.com/LTW-GCR-CSOC/metron/tree/master/metron-contrib/Metron-041SingleNodeEC2Vagrant/README.md https://github.com/LTW-GCR-CSOC/metron/tree/master/metron-contrib/Metron-041SingleNodeEC2Vagrant/Vagrantfile FYI I'm working on using Vagrant to deploy to 0.4.1 to ESXi. That could be posted at some point using the file structure above. ---
[GitHub] metron issue #916: METRON-1434 - Ability to deploy Metron full dev as a sing...
Github user ottobackwards commented on the issue: https://github.com/apache/metron/pull/916 @lvets Putting the vagrant file into a /contrib area with a notice that sets expectation correctly is the way to go then ---
[GitHub] metron issue #916: METRON-1434 - Ability to deploy Metron full dev as a sing...
Github user lvets commented on the issue: https://github.com/apache/metron/pull/916 @nickwallen, @ottobackwards , my 0.02$ :) > For example, with everything in Metron today, you can stand-up a single node in AWS and use the Mpack to install Metron. It is not as "push button" simple as your contribution here, but it is "good enough" considering the resources we have in the community today. Unfortunately, "push button" style setup is what most people want nowadays want to quickly set up a test environment and start playing around. I do understand that supporting different installation methods (including mine :p) adds a burden, but I think it is a burden we have to bear until Metron grows bigger. > We should also consider that running Metron on a single node is a recipe for a horrible user experience. It should only be run on a single node for development purposes, which is something that we already do support. I would not recommend that anyone run Metron on a single node for any other purpose. That's why AWS has a bunch of different VM types :) Maybe we should add a big fat warning somewhere saying "Your experience will be very bad if you not use at least an m5.4xlarge instance if you're going the single node way." I think having quick & easy ways to setup Metron on a single node to play around is necessary until the Metron community grows... Anyway, back to lurking mode for now. ---
[GitHub] metron issue #916: METRON-1434 - Ability to deploy Metron full dev as a sing...
Github user as22323 commented on the issue: https://github.com/apache/metron/pull/916 Thanks for the great feedback! Although I was hoping this would make it into the main build, I understand what you mean by the "Support Burden". I found a place in the Metron docs to refer to the AWS/Vagrantfile. I created the following pull request that updates a Metron Doc. https://github.com/apache/metron/pull/980 ---
[GitHub] metron issue #916: METRON-1434 - Ability to deploy Metron full dev as a sing...
Github user nickwallen commented on the issue: https://github.com/apache/metron/pull/916 I'd be perfectly happy to reference in Metron docs, external resources/projects like this that community members might find useful. Good idea @ottobackwards ---
[GitHub] metron issue #916: METRON-1434 - Ability to deploy Metron full dev as a sing...
Github user ottobackwards commented on the issue: https://github.com/apache/metron/pull/916 Why not add it to /contrib ? Or can we have a way to like to it from docs or site? ---
[GitHub] metron issue #916: METRON-1434 - Ability to deploy Metron full dev as a sing...
Github user nickwallen commented on the issue: https://github.com/apache/metron/pull/916 @as22323 Let me first say that this is a nice piece of work. You've followed all the existing patterns and your contribution looks solid. But ultimately I am +0 on this. I want others to speak up should they see value in this, but I'd argue that this should not be merged. Please let me explain my reasoning. **Support Burden** IMHO, the 'surface area' to support in Metron has always been too large. We as a community spend too much time supporting non-core functionality, which impedes our progress in delivering features targeted toward the cybersecurity use case. One key example of this are the multiple different deployment targets that we support. This has been a difficult and time consuming support task over the history of the project. I've done plenty of work on this myself. Coalescing Metron installation around the MPack was a major step forward for us. This was intended to help remove some of that support burden. With the MPack, much of that burden is shifted to Ambari. For example, with everything in Metron today, you can stand-up a single node in AWS and use the Mpack to install Metron. It is not as "push button" simple as your contribution here, but it is "good enough" considering the resources we have in the community today. **Uncommon Use Case** We should also considering that running Metron on a single node is a recipe for a horrible user experience. It should only be run on a single node for development purposes, which is something that we already do support. I would not recommend that anyone run Metron on a single node for any other purpose. -- I'd prefer not too add to our ongoing support burden by merging this PR. What you've done is a great contribution and I'd love to see you publicly share and support this as a separate project, outside of Apache Metron, going forward. If others agree or disagree with my reasoning, please do feel free to share. ---
