jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCLOUDS-367) Second instance in a group has its inboundPorts ignored (Google Compute Engine)
Date Mon, 11 Nov 2013 11:47:17 GMT

    [ https://issues.apache.org/jira/browse/JCLOUDS-367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13818888#comment-13818888

ASF subversion and git services commented on JCLOUDS-367:

Commit b5cb29aa3e45490e38c51523ce072c67517f9ab2 in branch refs/heads/1.6.x from [~richardcloudsoft]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds-labs.git;h=b5cb29a ]

JCLOUDS-367: GCE nodes n>1 ignoring inboundPort

The inboundPort settings of the first node in the group dictated the firewall configuration.
Subsequent nodes added to the group had their inboundPort settings ignored.

GCE firewalls specify their "target" (VM instances) by means of tags - if a targetTag on a
firewall matches the tag on an instance, the firewall's rules are allowed for the instance.
This commit applies a tag for each requested inboundPort to new instances. Then, a firewall
is created for each tag (if one does not already exist) which has 'allow' rules for the port.

> Second instance in a group has its inboundPorts ignored (Google Compute Engine)
> -------------------------------------------------------------------------------
>                 Key: JCLOUDS-367
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-367
>             Project: jclouds
>          Issue Type: Bug
>          Components: jclouds-labs-google
>    Affects Versions: 1.6.3
>            Reporter: Richard Downer (Cloudsoft)
>             Fix For: 1.7.0, 1.6.3
>         Attachments: JCLOUDS-367-1.6.x.patch, JCLOUDS-367.tar.bz2
> Create the first instance with set of inbound ports A - works as expected.
> Create a second instance, with a different set of inbound ports B. This instance will
have set A, not set B.
> For example:
>             GoogleComputeEngineTemplateOptions options = computeService.templateOptions()
>                     .as(GoogleComputeEngineTemplateOptions.class)
>                     .inboundPorts(22)
>                     ;
>             Set<? extends NodeMetadata> nodes1 = computeService.createNodesInGroup(GROUP_NAME,
1, options);
>             nodes.addAll(nodes1);
>             options.inboundPorts(44);
>             Set<? extends NodeMetadata> nodes2 = computeService.createNodesInGroup(GROUP_NAME,
1, options);
>             nodes.addAll(nodes2);
> In this example, nodes2 instance will have port 22 open, but not port 44.
> Full test case to follow in a moment. I will investigate the cause and hope to propose
a fix soon!

This message was sent by Atlassian JIRA

View raw message