Static IPv4 addresses not being migrated to OpenStack

[banchoff]

Hi,
I've done some tests using static IPv4 addresses and I found that the corresponding ports in OpenStack are created correctly (same network and MAC address), but the IP address is not the same.

So, for example, if I have a VM (with VMware tools installed and working) and this network configuration:

Nic1:

• IPv4 address: 172.16.5.55/24
• MAC address: 00:50:56:b7:55:55
  Nic2:
• IPv4 address: 172.16.6.66/24
• MAC address: 00:50:56:b7:55:66

The migration process creates these files:

nics.json

[{"vlan": "whitecloud-net-5", "mac": "00:50:56:b7:55:55"}, {"vlan": "whitecloud-net-6", "mac": "00:50:56:b7:55:66"}]

network_info.json

[
    {
        "addresstype": "manual",
        "ipaddresses": [
            "172.16.5.55",
            "fe80::250:56ff:feb7:5555"
        ],
        "label": "Network adapter 1",
        "macaddress": "00:50:56:b7:55:55",
        "macaddress_dash": "00-50-56-b7-55-55",
        "portgroup_key": null,
        "portgroup_portkey": null,
        "summary": "net5"
    },
    {
        "addresstype": "manual",
        "ipaddresses": [
            "172.16.6.66",
            "fe80::250:56ff:feb7:5566"
        ],
        "label": "Network adapter 2",
        "macaddress": "00:50:56:b7:55:66",
        "macaddress_dash": "00-50-56-b7-55-66",
        "portgroup_key": null,
        "portgroup_portkey": null,
        "summary": "net6"
    }
]

The network mapping flag is in true:

used_mapped_networks: true

Is there any way to pass the IP addresses as arguments when ports are created in OpenStack?

---

The ports are created in the correct network with the correct MAC, but IPv4 addresses were not migrated:

This is the netplan for this VM:

[matbu]

Hi,

Yes, we can set a static IP with neutron port creation but we didn't implement this option in the collection yet.
Our goal was to preserve the mac addresses but not the IPs because for a lot of users, the migration to a new ecosystem means new networks, ips & so on.
But we can definitively support the migration of the fixed IPs if needed. The Gophercloud package has this option already (https://github.com/gophercloud/gophercloud/blob/main/openstack/networking/v2/ports/requests.go#L46C2-L46C10) we just need to expose it in the create_network_port.go module and enable it with an Ansible variable (like migrate_fixed_ips: true/false)

I'm setting this issue as a feature and we will prioritized that asap.

Thank you !
Mathieu

[matbu]

It should be addressed by: #187

[banchoff]

Hi!
I've tested the fixed_ips enhancement, but I couldn't make it work.

I my vars file I added:

use_fixed_ips: true

But when I run the migration, I get the error:

fatal: [192.168.1.101]: FAILED! => {"changed": false, "msg": "Failed to create port: Expected HTTP response code [201 202] when accessing [POST http://xxx.xxx.xxx.xxx:9696/v2.0/ports], but got 400 instead: {\"NeutronError\": {\"type\": \"HTTPBadRequest\", \"message\": \"Invalid input for fixed_ips. Reason: '' is not a valid UUID.\", \"detail\": \"\"}}", "ports": null}

I see the IP addresses in the auxiliary files:

File nics.json:

[
 {"vlan": "mycloud-net-6", "mac": "00:50:56:b7:55:55", "ipaddresses": ["172.16.6.166", "fe80::250:56ff:feb7:5555"]},
 {"vlan": "mycloud-net-7", "mac": "00:50:56:b7:55:66", "ipaddresses": ["172.16.7.55", "fe80::250:56ff:feb7:5566"]}
]

File network_info.json:

[
    {
        "addresstype": "manual",
        "ipaddresses": [
            "172.16.6.166",
            "fe80::250:56ff:feb7:5555"
        ],
        "label": "Network adapter 1",
        "macaddress": "00:50:56:b7:55:55",
        "macaddress_dash": "00-50-56-b7-55-55",
        "portgroup_key": null,
        "portgroup_portkey": null,
        "summary": "net6"
    },
    {
        "addresstype": "manual",
        "ipaddresses": [
            "172.16.7.55",
            "fe80::250:56ff:feb7:5566"
        ],
        "label": "Network adapter 2",
        "macaddress": "00:50:56:b7:55:66",
        "macaddress_dash": "00-50-56-b7-55-66",
        "portgroup_key": null,
        "portgroup_portkey": null,
        "summary": "net7"
    }
]

Might the message '' is not a valid UUID refer to the lack of a SubnetId? (https://github.com/gophercloud/gophercloud/blob/main/openstack/networking/v2/ports/doc.go#L38).

[matbu]

Hi,

Thank you for the feedback.
Yes the subnet was a problem so we decided to map the subnet with network_map (https://github.com/os-migrate/vmware-migration-kit/blob/main/vars.yaml#L41).
In case of non mapped network, we consider only one subnet since we only use one network, so you can define the subnet here: https://github.com/os-migrate/vmware-migration-kit/blob/main/vars.yaml#L31-L32
We will have to find a better mapping, maybe change the vms_list to have the general parameters specific to each vms by getting a vms_list as a dict instead of a basic list.

So the port creation should work now.
Feel free to get feedback about the usage when you have multiple nics + fixed ip.

[banchoff]

Hi!
I've tested the migration of a VM with static IPs and had only one problem: if the origin VM has both, IPv4 and IPv6 addresses, the migration fails with this message:

I disabled IPv6 in the origin VM to perform the migration, and it worked right. It was a link-local address.

This is the configuration I used:

use_fixed_ips: true
used_mapped_networks: true
network_map:
  VM Network: "Private,e8b301c2-8b26-4fa3-98cf-ed467c08d0c7"
  net1: "mycloud-net-1,9fc017f5-a5e1-43d7-97dc-47f263f5b82f"
  net2: "mycloud-net-2,22a711d0-3482-472b-a096-2ba7619fa8df"
  net3: "mycloud-net-3,31e5f160-f5c5-453b-828c-4452a3b82a12"
  net4: "mycloud-net-4,6ca66b31-9e0e-4825-a89d-d52d51de67b0"
  net5: "mycloud-net-5,a026b3d2-23f0-409f-bda8-e5fb9e5f9480"
  net6: "mycloud-net-6,942bcf04-e7a2-4d7c-9a78-23245e6d1300"
  net7: "mycloud-net-7,e73267ea-3308-4920-b61b-b26e85c95229"
  net8: "mycloud-net-8,ff6e6e08-f1ec-4d73-9b81-4c1c7443d5dc"

And the VM had 3 NICs:

Nic1:
  172.16.1.11/24
  MAC: 00:50:56:b7:11:11
  Vmware net1

Nic2:
 172.16.2.22/24
 MAC 00:50:56:b7:22:22
 Vmware net2

Nic 3:
  172.16.3.33/24
  00:50:56:b7:33:33
  Vmware net3

Since the matching is by Subnet, I cannot configure something like:

  net5: "mycloud-net-5,subnet_ipv6_id,subnet_ipv4_id"

or

  net5: "mycloud-net-5,subnet_ipv6_id"
  net5: "mycloud-net-5,subnet_ipv4_id"

Or, if the match is by IPv4, could it be possible to create the port using a supporting IPv4 subnet and the link-local IPv6 address configured as an allowd address?