If floating IP is missing in customer network

[m1093782566]

If floating IP is missing in customer network

[yudai]

For your information, the OpenStack CPI and the AWS CPI employed the solution (1).

I think that the solution (2) is a kind behaviour for users, however, it's hard to implement this plan at this moment because the CloudStack API for acquiring a floating IP address doesn't provide a mechanism to specify an exact IP address to be created. I therefore think implementing the (1) is our only possible approach.

[m1093782566]

Solved by solution (1).

[gberche-orange]

@yudai can you please clarify the floating ip / vip limitation ?

https://github.com/cloudfoundry-community/bosh-cloudstack-cpi#describe-manifest describes advanced zone support

    # Only for Advanced zone users
      # You can set floating addresses to jobs
      # Acquire Public IP addresses on your Web UI before deploying
      # (Don't remove `default` network above even if `floating` is added)
      - name: floating
        static_ips:
          - <IP address for Router>

whereas https://github.com/cloudfoundry-community/bosh-cloudstack-cpi#sample-templates mentions Currently the CloudStack CPI does not support VIP networks and Floating IPs.

I guess this latter comment it outdated?

Besides, is the current CPI able to assign predetermined static private IP mentionned in the manifest (which seems the current practice in the cf-release spiff templates) ?

If not does this imply that the usual spiff templates provided by cf-release that specify IPs for connect jobs together, always have to be patched to use instead FQDN resolved by micro-bosh/full-bosh ?