The injection of the ambari cluster in the ambari server didn't work

[fotto1]

I tried to get the demo (http://www.cloudsoftcorp.com/blog/2015/04/deploying-an-hadoop-stack-to-a-cloud-using-brooklyn-and-ambari/) running on aws.

The creation of the instances goes successfully but there is no "Cluster1" in the ambari server web interface.

I use the apache brooklyn version 0.7.0-SNAPSHOT and the ambari brooklyn version given in the example.

I also try it with the current version of incubator-brooklyn and brooklyn-ambari from git hub today, with the same result.

[duncangrant]

@fotto1 Sorry for the slow response.
There's definitely a bug with the blueprint in that it doesn't cope with errors coming from ambari when it tries to deploy the cluster so, as you've seen, it looks like it is up and running even when it has failed.
Having said that if I use the yaml from the blog it works for me. I notice that only one agent has been deployed so I assume you've modified the example yaml. Could you post the yaml that you used - minus identity and credentials.

regards

Duncan

[fotto1]

Hello Duncan,

I use the following blueprint:

name: hadoop_deployment
description: Hadoop on Ambari Deployment
location: 
  jclouds:aws-ec2:
    region: eu-west-1
    identity: <aws-identity>
    credential: <aws-credential>
    osFamily: ubuntu
    osVersionRegex: 12.*
    minRam: 8192
services:
- type: io.brooklyn.ambari.AmbariCluster
  brooklyn.config:
    securityGroup: <aws-security-group>
    initialSize: 1
    services:
    - GANGLIA
    - HDFS
    - MAPREDUCE2
    - NAGIOS
    - YARN
    - ZOOKEEPER

I also try this with the initialSize 3 but with the same result.

Best Regards,
Felix

[fotto1]

Hello Duncan,

the problem was the security group. The ports which the ambari agent use to communicate with the ambari server was not open. Can you please add a notice for the default configuration of the aws security groups to the readme file?

Best Regards,
Felix

[duncangrant]

Felix,

thanks for your time on this. I've created a PR with a small change here: #11

If you could have a look and see whether you think this is clear enough that would be appreciated.

The next release should handle this stuff behind the scenes and make it all a bit easier.

thanks

Duncan

[fotto1]

Hello Duncan,

there are more ports to open, you can see them in the ambari-agent.ini

For the default configuration:

• 8080 - Ambari Server Webinterface
• 8440 - Ambari Agent URL Port
• 8441 - Ambari Agent Secured URL Port
• 8670 - Ambari Agent Ping Port

Best Regards,
Felix

[duncangrant]

Felix,

I think those ports are only used within the Ambari cluster. As the cluster shares a single security group then they should not need to be opened. Only the ports that brooklyn uses to connect to the cluster need to be open. In this case 22 and 8080. Brooklyn will open port 22 when it creates the VMs.

Could this be an issue with ipTables or something similar rather than security groups?

Duncan

[fotto1]

Hello Duncan,

I have try it with the following configuration:

following error on the AmbariAgent appears:

After I open the other ports all works fine.

Best Regards,
Felix