Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Configure F5 and SRX.
    1. Refer to Juniper SRX config information and F5 Device Installation Instructions.
  2. Add SRX and F5 to CloudStack's one zone.
    1. Check "inline mode" checkbox when adding F5.
    2. Choose "per zone" source NAT when adding SRX.
    3. Uncheck "dedicated" when adding F5.
  3. Enable these devices.
  4. Create a network offering(e.g. named "SRX-F5-inline") using SRX as provider for Firewall, PortForwarding, SourceNat, StaticNat; using F5 for Load Balancing; using VirtualRouter for DNS, DHCP, user data. VPN is not supported in this combination.
    1. And SELECT INLINE mode option for network offering.
  5. Start a new VM with the new network offering.
  6. Add Firewall rule and load balancing rule as usual.

...

  • When user add a new load balancing rule, CS would:
    1. Find a unused guest ip from existing guest ip pool for this network.
    2. Create an static NAT rule on the firewall, make every traffic go to the public ip(which is used for load balancing) redirect to this guest ip.
    3. Create an load balancing rule on the load balancer, using the guest ip above as the source ip(instead of public ip in the side-by-side mode).
    4. Thus all the traffic goes to the public ip, would be redirect to the load balancer's internal guest ip, finally reach the guest vms through load balancing policy on the load balancer.
  • When user add a firewall rule(for the load balancing rules)
    1. Since the public ip is not used by load balancer in this mode, we can configure firewall rule on the firewall(which own the public ip) without any trouble.
  • This design would result in every load balancing rule consuming one public ip and one guest ip.
  • The static nat rule connect firewall and load balancer won't show in the firewall table of CS, it's considered a part of implementation of load balancing rule itself.
  • The "inline mode" is a property of external load balancera property of network offering now. One F5 device can be used in "inline" network and "side-by-side" network at the same time.

web services APIs

list changes to existing web services APIs and new APIs introduced with signatures and throughout documentation

...