brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ahgittin <...@git.apache.org>
Subject [GitHub] brooklyn-docs pull request: Describe SoftLayerSameVlanLocationCust...
Date Thu, 24 Mar 2016 11:43:23 GMT
Github user ahgittin commented on a diff in the pull request:

    https://github.com/apache/brooklyn-docs/pull/31#discussion_r57305606
  
    --- Diff: guide/ops/locations/more-clouds.md ---
    @@ -172,4 +172,86 @@ For example, for dev/demo purposes an "everything" network could
be created that
     || Source IP Ranges            || 0.0.0.0/0                   |
     || 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:
    +
    +```YAML
    +location:
    +  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.
    +
    +If you are deploying a new application, then you can customise the
    +location with ` `JcloudsLocationCustomizer` class, and we provide an
    +implementation that ensures all machines in a particular scope will
    +use the same VLAN. By default, the scope used is the application ID
    +for the blueprint being deployed, but this can be changed if you need
    +multiple applications to share the same VLAN.
    --- End diff --
    
    ```
    The second method tells Brooklyn to discover VLAN information automatically:
    it will provision one VM first, and use the VLAN information from it when provisioning
subsequent machines.
    This ensures that all VMs are on the same subnet without requiring any manual VLAN referencing,
    making it very easy for end-users.
    ```
    
    (also note extra backtick in line 199)


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message