Uploaded image for project: 'jclouds'
  1. jclouds
  2. JCLOUDS-1290

Inconsistency in IpPermission.groupId()

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 2.0.1
    • Fix Version/s: None
    • Component/s: jclouds-compute
    • Labels:

      Description

      When trying to add IpPermission allowing access from an existing SecurityGroup how should we initialise the IpPermission.groupId field from the SecurityGroup fields so it works across clouds?

      Using IpPermission.groupId == SecurityGroup.id() works for:

      • OpenStack (Bluebox)
      • Azure ARM

      Doesn't work for:

      • Amazon (Invalid id: "eu-west-1/sg-eb0a4292" (expecting "sg-..."))

      Using IpPermission.groupId == SecurityGroup.providerId() works for:

      • Amazon
      • Azure ARM

      Doesn't work for:

      • OpenStack (Bluebox) (id must be in format regionId/id)

      My understanding is that it should always work with SecurityGroup.id()

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              svet Svetoslav Neykov
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: