[GitHub] metron issue #859: METRON-1345: Update EC2 README for custom Ansible tags

2017-12-14 Thread nickwallen
Github user nickwallen commented on the issue:

https://github.com/apache/metron/pull/859
  
+1 remains here.  Solid work.


---


[GitHub] metron issue #859: METRON-1345: Update EC2 README for custom Ansible tags

2017-12-14 Thread ottobackwards
Github user ottobackwards commented on the issue:

https://github.com/apache/metron/pull/859
  
+1


---


[GitHub] metron issue #859: METRON-1345: Update EC2 README for custom Ansible tags

2017-12-12 Thread nickwallen
Github user nickwallen commented on the issue:

https://github.com/apache/metron/pull/859
  
Nice.  I'm glad you uncovered the issue with the REST API.  Reaffirming +1


---


[GitHub] metron issue #859: METRON-1345: Update EC2 README for custom Ansible tags

2017-12-11 Thread mmiklavc
Github user mmiklavc commented on the issue:

https://github.com/apache/metron/pull/859
  
**Testing**
Run the EC2 deployment 
```
cd metron-deployment/amazon-ec2
./run.sh
```

The dev profile should now be set for the REST API. This is the same way we 
spin up full dev.


---


[GitHub] metron issue #859: METRON-1345: Update EC2 README for custom Ansible tags

2017-12-11 Thread mmiklavc
Github user mmiklavc commented on the issue:

https://github.com/apache/metron/pull/859
  
Just a heads up, I've added the spring profile to the ec2 blueprint.


---


[GitHub] metron issue #859: METRON-1345: Update EC2 README for custom Ansible tags

2017-12-08 Thread nickwallen
Github user nickwallen commented on the issue:

https://github.com/apache/metron/pull/859
  
Good catch @mmiklavc.  Would be nice to get that added to the blueprint so 
it just happens.


---


[GitHub] metron issue #859: METRON-1345: Update EC2 README for custom Ansible tags

2017-12-07 Thread mmiklavc
Github user mmiklavc commented on the issue:

https://github.com/apache/metron/pull/859
  
I just found another item when going through an AWS install. We don't setup 
users for the REST API. From what I can tell, we do this via blueprint when we 
install full-dev from a setting in single_node_vm.yml

```
  - metron-rest-env:
  metron_spring_profiles_active: "dev"
```

I'm wondering if we can/should configure this same setting in 
small_cluster.yml, which is used by the Amazon EC2 deployment. Any thoughts on 
this? At the very least I think this PR should include a doc change to indicate 
that we aren't setting up users unless you explicitly set a profile via Ambari 
or create them manually as a separate task.


---


[GitHub] metron issue #859: METRON-1345: Update EC2 README for custom Ansible tags

2017-12-06 Thread nickwallen
Github user nickwallen commented on the issue:

https://github.com/apache/metron/pull/859
  
+1 Thanks!


---