[ironic] [infra] Making Glean work with IPA for static IP assignment

Dmitry Tantsur dtantsur at redhat.com
Tue Nov 24 10:54:55 UTC 2020

Hi Ian,

Given our timezone difference, I've decided to send you an email, adding
openstack-discuss in CC for greater exposure.

We're trying to make IPA (our agent ramdisk) to work without relying on
DHCP for cases like Edge deployments. We've settled on the
network_data.json format for the API side and wanted to use Glean on the
ramdisk to apply it. You can read more details in [1].

The problem is, I cannot make Glean work with any ramdisk I build. The crux
of the problem seems to be that NetworkManager (used by default in RHEL,
CentOS, Fedora and Debian at least) starts very early, creates the default
connection and ignores whatever files Glean happens to write afterwards. On
Debian running `systemctl restart networking` actually helped to pick the
new configuration, but I'm not sure we want to do that in Glean. I haven't
been able to make NetworkManager pick up the changes on RH systems so far.

I build ramdisks using IPA-builder [2] by adding the simple-init element.
I've tried removing dhcp-all-interfaces (which we depend on by default) to
no effect. I've tried disabling the DHCP server, ended up with no IP
connectivity at all. I haven't tried to shutdown and restart a connection
as recommended in [3] since it's not trivial to do via SSH.

Do you maybe have any hints how to proceed? I'd be curious to know how
static IP assignment works in the infra setup. Do you have images with
NetworkManager there? Do you use the simple-init element?

Any help is very appreciated.


[2] https://opendev.org/openstack/ironic-python-agent-builder

Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20201124/e83f04c8/attachment.html>

More information about the openstack-discuss mailing list