Items with tag softlayer_network_lbaas_loadbalancer



    • LBaaS Examples
      A variety of examples on how to interact with the Load Balancer as a Service offering


    • cancelLoadBalancer
      Cancel a load balancer with the given uuid. The billing system will execute the deletion of load balancer and all objects associated with it such as load balancer appliances, listeners, pools and members in the background.
    • enableOrDisableDataLogs
      When enabled, data log would be forwarded to logging service.
    • getAllObjects
      Return all existing load balancers
    • getAppliances
      Get the load balancer appliances for the given lb id.
    • getDatacenter
      Datacenter, where load balancer is located.
    • getHealthMonitors
      Health monitors for the backend members.
    • getL7Pools
      L7Pools for load balancer.
    • getListeners
      Listeners assigned to load balancer.
    • getListenerTimeSeriesData
      Return listener time series datapoints. The time series data is available for Throughput, ConnectionRate and ActiveConnections. Throughput is in bits per second. The values are an average over the time range. The time series data is available for 1hour, 6hours, 12hours, 1day, 1week or 2weeks.
    • getLoadBalancer
      Get the load balancer object with given uuid.
    • getLoadBalancerMemberHealth
      Return load balancer members health
    • getLoadBalancers
      Get the load balancer objects for the given user accounts.
    • getLoadBalancerStatistics
      Return load balancers statistics such as total number of current sessions and total number of accumulated connections.
    • getMembers
      Members assigned to load balancer.
    • getObject
      Retrieve a SoftLayer_Network_LBaaS_LoadBalancer record.
    • getSslCiphers
      list of preferred custom ciphers configured for the load balancer.
    • serviceDNS
    • serviceLoadBalancer
      Service function for a load balancer.
    • SoftLayer_Network_LBaaS_LoadBalancer
      The SoftLayer_Network_LBaaS_LoadBalancer type presents a structure containing attributes of a load balancer, and its related objects including listeners, pools and members.
    • SoftLayer_Network_LBaaS_LoadBalancer
      The SoftLayer_Network_LBaaS_LoadBalancer service allows customers to create, edit, delete, get details of a load balancer instance and retrieve all existing load balancer instances. The most common use case of a load balancer instance is to improve performance and high availability of customers application services by distributing the incoming requests across multiple servers. Thus, clients using customers application services will only need to know the load balancer instances host name respective IP address in order to submit their requests. Note that SoftLayer_Network_LBaaS_LoadBalancer provides the load balancing functionality only, while it is customers responsibility to implement their application services and deploy them to respective servers, typically virtual servers or bare metal systems hosted by IBM SoftLayer. Conceptually a load balancer instance consists of a set of listeners, also called frontends, pools, also called backends, and members (application servers). A listener (frontend) represents basically the network protocol and port for requests coming from clients applications and is always associated with a pool (backend) defined by a network protocol, port and load balancing algorithm. The pools network protocol and port specify how incoming requests will be forwarded to application servers, while the load balancing algorithm (round-robin, weighted round-robin or least connections) determines the distribution scheme of incoming requests among the members, ie application servers. Note that members of a load balancer instance are assigned implicitly to all pools (backends) of that load balancer.
    • updateLoadBalancer
      Update load balancer's description, and return the load balancer object containing all listeners, pools, members and datacenter.
    • updateSslCiphers
      Updates the load balancer with the new cipher list. All new connections going forward will use the new set of ciphers selected by the user.