feat(opennebula): support ETHx_ALIASn_IP/MASK for anycast addresses

[mcanevet]

Proposed Commit Message

```
feat(opennebula): support ETHx_ALIASn_IP/MASK for anycast addresses

OpenNebula's context-linux package supports per-NIC alias addresses
(ETHx_ALIAS0_IP, ETHx_ALIAS1_IP, …) used for anycast IPs. Add
get_alias_addresses() to OpenNebulaNetwork and wire it into gen_conf()
so alias addresses appear in the Netplan v2 output alongside the
primary address. Missing MASK defaults to /32.
```

Additional Context

OpenNebula allows attaching multiple IP addresses to a single NIC via
ETH<x>_ALIAS<n>_IP / ETH<x>_ALIAS<n>_MASK context variables. These
are typically used for anycast or VIP addresses. Previously cloud-init
ignored them, leaving the addresses unconfigured on the guest.

Test Steps

1. In OpenNebula, add alias addresses to a NIC context:
   ```
   ETH0_ALIAS0_IP = "192.168.1.10"
   ETH0_ALIAS0_MASK = "255.255.255.0"
   ETH0_ALIAS1_IP = "192.168.1.11"
   ```
2. Boot a cloud-init enabled VM using that context.
3. Verify the alias addresses appear on the interface:
   ```
   ip addr show eth0

   expected: 192.168.1.10/24 and 192.168.1.11/32 present

   ```
4. Verify a NIC without aliases is unaffected.

Merge type

• Squash merge using "Proposed Commit Message"
• Rebase and merge unique commits. Requires commit messages per-commit each referencing the pull request number (#<PR_NUM>)

[Copilot]

Pull request overview

This PR extends the OpenNebula datasource’s network configuration generation to include per-NIC alias (anycast/VIP) IPv4 addresses defined via ETH<x>_ALIAS<n>_IP / ETH<x>_ALIAS<n>_MASK, so they appear in the Netplan v2 addresses list alongside the primary address (defaulting missing masks to /32).

Changes:

• Add OpenNebulaNetwork.get_alias_addresses() to collect alias IPv4 addresses from context.
• Extend OpenNebulaNetwork.gen_conf() to append alias addresses into Netplan addresses.
• Add unit tests and update OpenNebula datasource documentation for the new context variables.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
cloudinit/sources/DataSourceOpenNebula.py	Implements alias address parsing and includes aliases in generated Netplan output.
tests/unittests/sources/test_opennebula.py	Adds unit tests covering alias parsing and integration into gen_conf().
doc/rtd/reference/datasources/opennebula.rst	Documents ETH<x>_ALIAS<n>_IP/MASK behavior and default mask handling.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[blackboxsw]

Thank you again @mcanevet for this proposal. I think we might want a bit more logging verbosity when cloud-init ignores potential invalid config values such as gap ranges in aliases. Silently ignoring potential config is not ideal.

Can you please provide the representative /etc/netplan/50-cloud-init.yaml created and cloud-init status --format=yaml on a vm with this context provided if possible?

[blackboxsw]

Thanks for this PR, I can confirm the documented behavior and contextualization switches documented in opennebula 7.2 operations guide](https://docs.opennebula.io/7.2/product/operation_references/configuration_references/template/#template-context)

[mcanevet]

@blackboxsw fixed

[blackboxsw]

Thank you for the swift updates @mcanevet. I'm wondering if these is a better way to simplify the separate ordered looping when detecting gaps. Can we consolidate some of that looping somehow? Given that you are using a regex below, that regex could help in a for loop instead of just using a while loop and an incrementing idx to encounter a a gap in self.context.

[blackboxsw]

gap doesn't provide enough context in the message. Let's be a bit more explicit about the problem.

Ignoring network config keys %s due to missing %s

[blackboxsw]

It feels a bit like we are processing the data in self.context twice through two separate loops which makes it a teeny bit harder to maintain when we look at this in the future.

Could we instead try processing these keys once?
something like (completely untested):

key_re = re.compile(rf"^{c_dev.upper()}_ALIAS(?P<alias_idx>\d+)_IP$" % re.escape(prefix))
for key, value  in sorted(self.content.items()):
    match = key_re.match(key)
    if not match
        continue
    if int(match['alias_idx']) == idx:
        idx += 1
        mask_key = self.context.get(key.replace("IP", "MASK"))
        mask = self.context.key(mask_key) or "255.255.255.255"
        aliases.append(f"{value}/{mask}")
    else:
        skipped.append(key)