| 2024-04-17 13:26:32 |
Björn Tillenius |
description |
MAAS 3.5 added the possibility to deploy non-Ubuntu images to memory.
If you deploy an Ubuntu image to memory, things work as expected and the requested network configuration
gets applied.
However, if you try to deploy a non-Ubuntu image to memory, you'll see that the network configuration doesn't get applied. Instead, each interface on the machine tries to get an IP via DHCP.
The problem is that MAAS currently relies on netplan for configuring the networking.
What we want to do is to use cloud-init to configure the networking, which would work with most distros. However, at the time, the MAAS provider in cloud-init didn't support it. This has now been fixed, and with cloud-init 24.1.4, we should be able to make it work.
What we have to do in MAAS is change the way the the initial cloud-config is generated. We need to look at the cloud-init version. If it's 24.1.4 or greater, we should include a "network" section, and not try to execute netplan. |
MAAS 3.5 added the possibility to deploy non-Ubuntu images to memory.
If you deploy an Ubuntu image to memory, things work as expected and the requested network configuration
gets applied.
However, if you try to deploy a non-Ubuntu image to memory, you'll see that the network configuration doesn't get applied. Instead, each interface on the machine tries to get an IP via DHCP.
The problem is that MAAS currently relies on netplan for configuring the networking.
What we want to do is to use cloud-init to configure the networking, which would work with most distros. However, at the time, the MAAS provider in cloud-init didn't support it. This has now been fixed, and with cloud-init 24.1.3, we should be able to make it work.
What we have to do in MAAS is change the way the the initial cloud-config is generated. We need to look at the cloud-init version. If it's 24.1.4 or greater, we should include a "network" section, and not try to execute netplan. |
|
