iblindu
commented
2 years ago Hi @marcelbrueckner,
Thank you a lot for opening this topic since this should be documented properly. The strategy would be the following (here being the docs examples changed according to your needs):
1. First create NIC A and NIC B under LAN1 with different IPs. Create the ip_failover on LAN 1 with NIC A and failover IP of NIC A
``` hcl
... datacenter here ...
resource "ionoscloud_ipblock" "example" {
location = "us/las"
size = 2
name = "IP Block Example"
}
resource "ionoscloud_lan" "example" {
datacenter_id = ionoscloud_datacenter.example.id
public = true
name = "Lan Example"
}
resource "ionoscloud_server" "example" {
count = 2
... server config ...
nic {
lan = ionoscloud_lan.example.id
dhcp = true
firewall_active = true
ips = [ ionoscloud_ipblock.example.ips[count.index] ]
}
}
resource "ionoscloud_ipfailover" "example" {
depends_on = [ ionoscloud_lan.example ]
datacenter_id = ionoscloud_datacenter.example.id
lan_id = ionoscloud_lan.example.id
ip = ionoscloud_ipblock.example.ips[0]
nicuuid = ionoscloud_server.example[0].primary_nic
}
```
2. Update NIC B IP to be failover IP
``` hcl
... datacenter here ...
resource "ionoscloud_ipblock" "example" {
location = "us/las"
size = 2
name = "IP Block Example"
}
resource "ionoscloud_lan" "example" {
datacenter_id = ionoscloud_datacenter.example.id
public = true
name = "Lan Example"
}
resource "ionoscloud_server" "example" {
count = 2
... server config ...
nic {
lan = ionoscloud_lan.example.id
dhcp = true
firewall_active = true
ips = [ ionoscloud_ipblock.example.ips[0] ]
}
}
resource "ionoscloud_ipfailover" "example" {
depends_on = [ ionoscloud_lan.example ]
datacenter_id = ionoscloud_datacenter.example.id
lan_id = ionoscloud_lan.example.id
ip = ionoscloud_ipblock.example.ips[0]
nicuuid = ionoscloud_server.example[0].primary_nic
}
```
3. After this, you can create NIC C, NIC D and so on, with the ip being the failover ip, with no problems!
We will add this steps in our documentation. Thanks again for raising this issue and please let me know if it works for you!
P.S. We will also enable discussions on our repositories for this kind of topics.
marcelbrueckner
jbuchhammer
Description
Not sure if a bug, but as discussions aren't enabled for this repo, I'm creating this issue. If what I want to achieve is generally not yet possible with the Terraform provider, consider this as a feature request.
I'm wrapping my head around IP failover configuration for my servers and can't find a way to get it working the way it does in DCD.
Expected behavior
Two servers that are part of the same public network should share a floating IP. For this, they should be member of the same IP failover group and the failover IP should appear on all servers as it appears when adding a failover group via UI.
Screenshots
  Environment
Terraform version:
Tested with the following provider version:
OS:
Configuration Files
I've only set
IONOS_TOKEN.How to Reproduce
Looking at the Data Center Designer UI, a failover group contains of a list of public NICs. The ionoscloud_ipfailover documentation however wants a string.
My first thought was to just add the failover twice via
count = 2, using each serversnicuuid.Maybe I need to add the floating IP to the servers upfront. Seems reasonable. Nothing easier than that I thought (Hint: not easy).
Next, I assigned the floating IP only to the first of my frontend servers. This lets Terraform complete successfully. But it doesn't look like I'm used to in the DCD WebUI.
Lastly, I created the failover IP group manually in the web UI and imported it into Terraform to see how it should look like.
When looking at the plan, you can see that both of my frontend servers have the floating IP assigned (something that's not possible using Terraform looking at my second attempt). Of course
terraform planalso tries to remove that IP from the second server. When assigning the floating IP to both servers in my config, I can refresh my state without any changes.