Github user mmiklavc commented on the issue:
https://github.com/apache/metron/pull/1261
@ottobackwards thanks for the submission. Per recent community comments, it
sounds like we could use some improvements to how our build/deploy dep versions
interact with other tooling that may require other versions of things.
Is this the correct dependency listings for each host/container?
The Docker container will be pre-configured with:
- Java 8
- Ansible 2.4.0+
- Python 2.7
- Maven 3.3.9
- C++11 compliant compiler, like GCC
And the developer host machine would now need to manage versions of:
- Vagrant 2.0+
- Vagrant Hostmanager Plugin
- Virtualbox 5.0+
- Docker
The deployment goes through these steps:
1. You mount m2 repo and your code dir in the Docker instance.
2. build_and_run optionally spins up Vagrant in VirtualBox.
3. build_and_run optionally creates Docker instance with pre-reqs for
building and deploying Metron.
4. build_and_run runs the build and then calls the Ansible deployment
scripts from within Docker.
At the end, you have an ephemeral Docker instance + Vagrant instance that
has the running Metron instance?
---
