[
https://issues.apache.org/jira/browse/BROOKLYN-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15272268#comment-15272268
]
Jose Carrasco commented on BROOKLYN-263:
----------------------------------------
As [~andreaturli] suggested me, the expected HTTP_PORT for a BrooklynNode can
be forced to be opened using the provision.properties.
{code:}
name: BrooklynNode
location: aws-ec2:us-west-2
services:
- type: org.apache.brooklyn.entity.brooklynnode.BrooklynNode
id: deployer
name: Deployer
brooklyn.config:
onExistingProperties: do_not_use
brooklynnode.webconsole.nosecurity: true
brooklynnode.webconsole.httpPort: 8082
provisioning.properties:
required.ports:
- 8082
{code}
But, probably this does not solve the issue. Because if you modify the
brooklynnode.webconsole.httpPort, required.ports should be modified too.
> Explicit ports are not open for BrooklynNode in cloud
> -----------------------------------------------------
>
> Key: BROOKLYN-263
> URL: https://issues.apache.org/jira/browse/BROOKLYN-263
> Project: Brooklyn
> Issue Type: Bug
> Affects Versions: 0.9.0, 0.10.0
> Reporter: Jose Carrasco
> Priority: Minor
> Labels: easyfix
>
> I tried to deploy a BrooklynNode entity with an explicit web console port
> (8082) over a AWS VM machine. Using the following plan:
> {code:title=BluePrint|borderStyle=solid}
> name: BrooklynNode
> location: aws-ec2:us-west-2
> services:
> - type: org.apache.brooklyn.entity.brooklynnode.BrooklynNode
> id: brooklynNode
> brooklyn.config:
> onExistingProperties: do_not_use
> brooklynnode.webconsole.nosecurity: true
> brooklynnode.webconsole.httpPort: 8082
> {code}
> However I found an error because the entity did not look to be up (SERVICE_UP
> retrieved false). Then, I tried to figure out a bit. The BrooklynNode
> instance was installed and executed correctly but the VM’s security group did
> not have any rule to enable the 8082 port.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
