b7bfee5d27
We use the same technique that is used for kubernetes clusters, with a custom heat resource that provides either a floating IP, or OS::Heat::None when disabled. We also add coverage tests for swarm-mode. Change-Id: I3b5877bcd89fc2436776f49e479ffadf72c00ea3 Story: 1772433 Task: 21662 Task: 22102 Co-authored-by: Mark Goddard <mark@stackhpc.com> |
||
|---|---|---|
| .. | ||
| disable_floating_ip.yaml | ||
| disable_lb_floating_ip.yaml | ||
| enable_floating_ip.yaml | ||
| enable_lb_floating_ip.yaml | ||
| no_etcd_volume.yaml | ||
| no_master_lb.yaml | ||
| no_private_network.yaml | ||
| no_volume.yaml | ||
| with_etcd_volume.yaml | ||
| with_master_lb.yaml | ||
| with_master_lb_octavia.yaml | ||
| with_private_network.yaml | ||
| with_volume.yaml | ||