GitHub user dlyle65535 opened a pull request:
https://github.com/apache/incubator-metron/pull/499
METRON-196: Deployment Fails Without Ansible 2.0.0.2
## Contributor Comments
This changeset allows deployment with Ansible 2.0.0.2 and 2.2.2.0.
I also added a version check as a pre-task to the top of the two entry
playbooks, so deployment will now fail with a clearer error message if it is
run on untested Ansible versions.
@JonZeolla - this is the branch that (I hope) takes care of your issue.
Please update Ansible to 2.2.2.0 and give it a whirl when you can. I setup a
virtualenv to test it out, I'd recommend you do the same.
**Testing**
For those wishing to remain on 2.0.0.2, nothing should change, simply run
the deployment of your choice.
For those wishing to test on 2.2.2.0, do the following:
1. Setup virtual environment for testing.
```
pip install virtualenv
cd ~
virtualenv -p /usr/bin/python2.7 test_ansible
source ~/test_ansible/bin/activate
pip install ansible
pip install boto
```
After this, your prompt will begin with (test_ansible) indicating you're in
the virtual Python environment.
2. Run deployment of your choosing.
3. Type _deactivate_ to return to your normal Python environment.
## Pull Request Checklist
Thank you for submitting a contribution to Apache Metron (Incubating).
Please refer to our [Development
Guidelines](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61332235)
for the complete guide to follow for contributions.
Please refer also to our [Build Verification
Guidelines](https://cwiki.apache.org/confluence/display/METRON/Verifying+Builds?show-miniview)
for complete smoke testing guides.
In order to streamline the review of the contribution we ask you follow
these guidelines and ask you to double check the following:
### For all changes:
- [X] Is there a JIRA ticket associated with this PR? If not one needs to
be created at [Metron
Jira](https://issues.apache.org/jira/browse/METRON/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel).
- [X] Does your PR title start with METRON-XXXX where XXXX is the JIRA
number you are trying to resolve? Pay particular attention to the hyphen "-"
character.
- [X] Has your PR been rebased against the latest commit within the target
branch (typically master)?
### For code changes:
- [N/A] Have you included steps to reproduce the behavior or problem that
is being changed or addressed.
- [X] Have you included steps or a guide to how the change may be verified
and tested manually?
- [X] Have you ensured that the full suite of tests and checks have been
executed in the root incubating-metron folder via:
```
mvn -q clean integration-test install && build_utils/verify_licenses.sh
```
- [N/A] Have you written or updated unit tests and or integration tests to
verify your changes?
- [N/A] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [X] Have you verified the basic functionality of the build by building
and running locally with Vagrant full-dev environment or the equivalent? (Full
Dev and EC2)
### For documentation related changes:
- [X] Have you ensured that format looks appropriate for the output in
which it is rendered by building and verifying the site-book? If not then run
the following commands and the verify changes via
`site-book/target/site/index.html`:
```
cd site-book
bin/generate-md.sh
mvn site:site
```
#### Note:
Please ensure that once the PR is submitted, you check travis-ci for build
issues and submit an update to your PR as soon as possible.
It is also recommended that [travis-ci](https://travis-ci.org) is set up
for your personal repository such that your branches are built there before
submitting a pull request.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dlyle65535/incubator-metron METRON-196
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-metron/pull/499.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #499
----
commit 75aa5091d0bbf1d0e3e912477e2d05fb755c4610
Author: David Lyle <dlyle65...@gmail.com>
Date: 2017-03-30T01:45:42Z
METRON-196: Deployment Fails Without Ansible 2.0.0.2
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
