[
https://issues.apache.org/jira/browse/JCLOUDS-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14901414#comment-14901414
]
Andrew Kennedy commented on JCLOUDS-1003:
-----------------------------------------
No, the OpenStack rules actually allow you to specify arbitrary IP protocols by
number (protocol 94 = IPIP is the one I was interested in enabling, for the
calico SDN) or just any IP protocol, i.e. all 256 of them. In fact, AWS with
VPCs also allows this, and perhaps other clouds, I'm not sure. For OpenStack
and IpProtocol.ANY the data should be null for the 'ip_protocol' field, but
this is causing NPEs in jclouds, when it tries to generate the JSON for the
REST call.
> IpProtocol.ANY does not work on OpenStack
> -----------------------------------------
>
> Key: JCLOUDS-1003
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1003
> Project: jclouds
> Issue Type: Bug
> Environment: OpenStack Nova on BlueBox Cloud
> Reporter: Andrew Kennedy
>
> Trying to add IpPermissions.permitAnyProtocol() or any IpPermission using
> IpProtocol.ANY fails with the following error:
> 2015-09-21 07:03:57,972 DEBUG o.j.h.i.JavaUrlHttpCommandExecutorService
> [brooklyn-execmanager-L0pLKIH7-132]: Sending request 193768812: POST
> https://cloudsoft-sjc.openstack.blueboxgrid.com:8777/v2/bba97b44a7dd40b1ad8a0b90510129f7/os-security-group-rules
> HTTP/1.1
> 2015-09-21 07:03:57,972 DEBUG jclouds.wire
> [brooklyn-execmanager-L0pLKIH7-132]: >>
> "{"security_group_rule":{"parent_group_id":"1d958f15-aeef-4ee8-a527-71f7fcae9864","cidr":"0.0.0.0/0","ip_protocol":"-1","from_port":"1","to_port":"65535"}}"
> 2015-09-21 07:03:58,793 DEBUG jclouds.wire
> [brooklyn-execmanager-L0pLKIH7-132]: << "{"badRequest": {"message": "Invalid
> IP protocol -1.", "code": 400}}"
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
