brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jose Carrasco (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BROOKLYN-263) Explicit ports are not open for BrooklynNode in cloud
Date Wed, 11 May 2016 16:43:12 GMT

    [ https://issues.apache.org/jira/browse/BROOKLYN-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15280402#comment-15280402
] 

Jose Carrasco commented on BROOKLYN-263:
----------------------------------------

I have added a PR which tries to solve this issue
[brooklyn-server#136|https://github.com/apache/brooklyn-server/pull/136]

> 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)

Mime
View raw message