Open Stack

The short answer is: Yes, with the appropriate configuration and artifacts.

The longer answer:

You do not need to deploy a dedicated conductor node, but:

1) Your conductor configuration will need to be aware of the bootloader to
utilize by architecture. See[0], look for settings ending with "by_arch".
2) These settings will need to point to the appropriate architecture
bootloader, and potentially templates. GRUB has been reported to work
fairly well, and a number of folks have reported utilizing iPXE. The
downside is iPXE aarch64 binaries are sometimes not in every aarch64
distribution. iPXE.org does publish binaries you can at least test with if
you so desire.[1]
3) You will need to create the nodes in ironic so they are labeled with
their architecture. This is covered in our installation documentation[2],
and can be set on the command line[3] with the key value of "cpu_arch".

If you run into any weird issues, please reply to the mailing list. I know
some of the Ironic operators who run large arm hardware labs are on this
mailing list, and may be able to offer additional insight if needed.

-Julia

[0]:
https://docs.openstack.org/ironic/latest/configuration/sample-config.html
[1]: https://boot.ipxe.org/arm64-efi/
[2]:
https://files.openstack.org/docs/ironic/victoria/install/configure-pxe.html#pxe-multi-architecture-setup
[3]:
https://docs.openstack.org/python-ironicclient/latest/cli/osc/v1/index.html#cmdoption-openstack-baremetal-node-set-property

On Thu, Feb 2, 2023 at 8:35 AM 韩光宇 <hanguangyu2 at gmail.com> wrote:

> Hi,
>
> I deploy ironic in x86 env, could I use it to deploy arm bare metal node?
>
> My concern is mainly whether the files transferred in the tftp phase
> of PXE cannot be cross-architecture.
>
> Do I need to deploy a dedicated arm-architecture ironic-conductor node
> for arm-architecture bare metal nodes?
>
> Thanks
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.openstack.org/pipermail/openstack-discuss/attachments/20230202/263f5434/attachment.htm>