Items with tag softlayer_network_pod

    java

    python

    reference

    • getAllObjects
      Filtering is supported for ``datacenterName`` and ``capabilities``. When filtering on capabilities, use the ``in`` operation. Pods fulfilling all capabilities provided will be returned. ``datacenterName`` represents an operation against ``SoftLayer_Location_Datacenter.name`, such as dal05 when referring to Dallas 5. ```Examples:``` List Pods in a specific datacenter. <pre> datacenterName.operation = 'dal06' </pre> List Pods in a geographical area. <pre> datacenterName.operation = '^= dal' </pre> List Pods in a region fulfilling capabilities. <pre> datacenterName.operation = '^= dal' capabilities.operation = 'in' capabilities.options = [ { name = data, value = [SOME_CAPABILITY, ANOTHER_CAPABILITY] } ] </pre>
    • getCapabilities
      Provides the list of capabilities a Pod fulfills. See [SoftLayer_Network_Pod::listCapabilities](/reference/services/SoftLayer_Network_Pod/listCapabilities) for more information on capabilities.
    • getObject
      Set the initialization parameter to the ``name`` of the Pod to retrieve.
    • listCapabilities
      A capability is simply a string literal that denotes the availability of a feature. Capabilities are generally self describing, but any additional details concerning the implications of a capability will be documented elsewhere; usually by the Service or Operation related to it.
    • SoftLayer_Network_Pod
      SoftLayer_Network_Pod refers to a portion of a data center that share a Backend Customer Router (BCR) and usually a front-end counterpart known as a Frontend Customer Router (FCR). A Pod primarily denotes a logical location within the network and the physical aspects that support networks. This is in contrast to representing a specific physical location. A ``Pod`` is identified by a ``name``, which is unique. A Pod name follows the format 'dddnn.podii', where 'ddd' is a data center code, 'nn' is the data center number, 'pod' is a literal string and 'ii' is a two digit, left-zero- padded number which corresponds to a Backend Customer Router (BCR) of the desired data center. Examples: <ul> <li>dal09.pod01 = Dallas 9, Pod 1 (ie. bcr01)</li> <li>sjc01.pod04 = San Jose 1, Pod 4 (ie. bcr04)</li> <li>ams01.pod01 = Amsterdam 1, Pod 1 (ie. bcr01)</li> </ul>
    • SoftLayer_Network_Pod
      SoftLayer_Network_Pod refers to a portion of a data center that share a Backend Customer Router (BCR) and usually a front-end counterpart known as a Frontend Customer Router (FCR). A Pod primarily denotes a logical location within the network and the physical aspects that support networks. This is in contrast to representing a specific physical location. A ``Pod`` is identified by a ``name``, which is unique. A Pod name follows the format 'dddnn.podii', where 'ddd' is a data center code, 'nn' is the data center number, 'pod' is a literal string and 'ii' is a two digit, left-zero- padded number which corresponds to a Backend Customer Router (BCR) of the desired data center. Examples: <ul> <li>dal09.pod01 = Dallas 9, Pod 1 (ie. bcr01)</li> <li>sjc01.pod04 = San Jose 1, Pod 4 (ie. bcr04)</li> <li>ams01.pod01 = Amsterdam 1, Pod 1 (ie. bcr01)</li> </ul>