brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ahgittin <>
Subject [GitHub] brooklyn-docs pull request: Describe SoftLayerSameVlanLocationCust...
Date Thu, 24 Mar 2016 11:40:16 GMT
Github user ahgittin commented on a diff in the pull request:
    --- Diff: guide/ops/locations/ ---
    @@ -172,4 +172,86 @@ For example, for dev/demo purposes an "everything" network could
be created that
     || Source IP Ranges            ||                   |
     || Allowed protocols and ports || tcp:0-65535 and udp:0-65535 |
    +## IBM SoftLayer
    +### VLAN Selection
    +For some applications it is important that All VMs use the same VLAN. On
    +SoftLayer this can be done by setting the `SoftLayerTemplateOptions`
    +fields `primaryNetworkComponentNetworkVlanId` and
    +`primaryBackendNetworkComponentNetworkVlanId` when specifying the
    +location being used in the blueprint, as follows:
    +  jclouds:softlayer:
    +    region: ams01
    +    templateOptions:
    +      # Enter your preferred network IDs
    +      primaryNetworkComponentNetworkVlanId: 1153481
    +      primaryBackendNetworkComponentNetworkVlanId: 1153483
    +This will only work if you already have a VM configured using the same
    +VLAN, and can copy the IDs from the SoftLayer console UI.
    --- End diff --
    This method requires that a VM already exist and you look up the IDs of its VLANs, for
example in the SoftLayer console UI, and that subsequently at least one VM in that VLAN is
kept around.  If all VMs on a VLAN are destroyed SoftLayer may destroy the VLAN.  Creating
VLANs directly and then specifying them as IDs here may not work.

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message