This is something that would be nice to fix. Right now, the auto deploy to EC2 is only intended for short-term testing of ephemeral clusters. Fixing this issue, along with increasing the default security settings, would make this way more functional.
I think manually "fixing" the hostnames after deployment is not going to work very well. There are just too many places that reference the external hostnames. Fixing this would require some changes to the code in "metron-deployment/amazon-ec2." I would specifically start with the settings in "conf/ec2.ini". https://github.com/apache/metron/blob/master/metron-deployment/amazon-ec2/conf/ec2.ini On Wed, Aug 30, 2017 at 11:58 AM Ahmed Shah <[email protected]> wrote: > Hello, > This question is with respect to the Amazon EC2 deployment of Metron. > I am wondering how to change the "hostnames" of the VMs (see pics as as > how they appear in Ambari) from public_dns_names to private ips or > private_dns_names. > > Issue: > In Amazon EC2 the public ip address and public_dns_names of deployed VMs > will change when VMs are stopped and then turned back on. > Since the configurations of Metron EC2 deployment seem to be tied to > public_dns_names restarting the VMs appear to break connections to > each-other. > > My thoughts for a possible solution are to change hostnames to > private_dns_names. > > Wondering if someone could point me in the right direction... (i.e. > After a deployment is done, change hostnames of each VM to > private_dns_name and reconnect the new hostnames appropriately. I'm not > sure where in Metron the links to hostnames are defined.) > > > > > -Ahmed > > > >
