[ironic]About the OS supported by Diskimage-builder
To whom it may concern. My name is Junya Noguchi. I have some questions about the supported OS for Diskimage-builder operation. Please respond. References https://docs.openstack.org/ironic-python-agent-builder/latest/admin/dib.html Does it mean that the OS that says "work but receive only limited testing and support" works but is not supported? References https://docs.openstack.org/diskimage-builder/latest/ This document describes RHEL and other operating systems that are not supported in the previous question. Are these operating systems supported? Also, are there any plans to support more operating systems in the future? Best regards, Junya Noguchi
Hi Junya, The comment on IPA-builder means that the corresponding CI jobs are not voting, and we may remove the support if it gets broken and we cannot fix it easily. DIB itself may support more operating systems than IPA-builder since the latter is built on top of the former. Since we support Stream 9, chances are high that RHEL 9 also works. We cannot test that in the upstream CI though, so we cannot commit to it. We will support more operating systems if there are people willing to maintain their support long term. I hope that helps. Dmitry On 4/10/24 03:33, Junya Noguchi (Fujitsu) wrote:
To whom it may concern.
My name is Junya Noguchi.
I have some questions about the supported OS for Diskimage-builder operation. Please respond.
References https://docs.openstack.org/ironic-python-agent-builder/latest/admin/dib.html Does it mean that the OS that says "work but receive only limited testing and support" works but is not supported?
References https://docs.openstack.org/diskimage-builder/latest/ This document describes RHEL and other operating systems that are not supported in the previous question. Are these operating systems supported? Also, are there any plans to support more operating systems in the future?
Best regards, Junya Noguchi
Hi Junya, We are using AlmaLinux9 (so this reinforces Dmitry's probability message). HTH, Arne ________________________________________ From: Dmitry Tantsur <dtantsur@protonmail.com> Sent: Thursday, 11 April 2024 18:29 To: openstack-discuss@lists.openstack.org Subject: Re: [ironic]About the OS supported by Diskimage-builder Hi Junya, The comment on IPA-builder means that the corresponding CI jobs are not voting, and we may remove the support if it gets broken and we cannot fix it easily. DIB itself may support more operating systems than IPA-builder since the latter is built on top of the former. Since we support Stream 9, chances are high that RHEL 9 also works. We cannot test that in the upstream CI though, so we cannot commit to it. We will support more operating systems if there are people willing to maintain their support long term. I hope that helps. Dmitry On 4/10/24 03:33, Junya Noguchi (Fujitsu) wrote:
To whom it may concern.
My name is Junya Noguchi.
I have some questions about the supported OS for Diskimage-builder operation. Please respond.
References https://docs.openstack.org/ironic-python-agent-builder/latest/admin/dib.html Does it mean that the OS that says "work but receive only limited testing and support" works but is not supported?
References https://docs.openstack.org/diskimage-builder/latest/ This document describes RHEL and other operating systems that are not supported in the previous question. Are these operating systems supported? Also, are there any plans to support more operating systems in the future?
Best regards, Junya Noguchi
RHEL should be working fine -- we build Rocky Linux images in DIB and they're used in several projects including OSA and Kolla and I maintain them (by defacto ownership). Its worth noting that (especially in an openstack context), Stream 9 and RHEL 9 are not guaranteed to be compatible. It's for this reason I maintain RHEL-compatible rebuilds for open switch and ovn (and probably more in the future). Im always welcoming more contributions to this space. For example I know there is also a change to support AlmaLinux nodes in DIB. --Neil On Thu, Apr 11, 2024, 12:38 Dmitry Tantsur <dtantsur@protonmail.com> wrote:
Hi Junya,
The comment on IPA-builder means that the corresponding CI jobs are not voting, and we may remove the support if it gets broken and we cannot fix it easily.
DIB itself may support more operating systems than IPA-builder since the latter is built on top of the former. Since we support Stream 9, chances are high that RHEL 9 also works. We cannot test that in the upstream CI though, so we cannot commit to it.
We will support more operating systems if there are people willing to maintain their support long term.
I hope that helps.
Dmitry
On 4/10/24 03:33, Junya Noguchi (Fujitsu) wrote:
To whom it may concern.
My name is Junya Noguchi.
I have some questions about the supported OS for Diskimage-builder operation. Please respond.
References
https://docs.openstack.org/ironic-python-agent-builder/latest/admin/dib.html
Does it mean that the OS that says "work but receive only limited testing and support" works but is not supported?
References https://docs.openstack.org/diskimage-builder/latest/ This document describes RHEL and other operating systems that are not supported in the previous question. Are these operating systems supported? Also, are there any plans to support more operating systems in the future?
Best regards, Junya Noguchi
Dear Mr. Hanlon
RHEL should be working fine -- we build Rocky Linux images in DIB and they're used in several projects including OSA and Kolla and I maintain them (by defacto ownership). Could you please provide the command you used? Also, can I use the image built by this method in bare metal?
I built the Rocky Linux OS image with the following command. $ disk-image-create rocky-container vm dhcp-all-interfaces block-device-efi openssh-server cloud-init -a arm64 -o rocky_ironic When I deployed a VM with OpenStack using the OS image created with this command, the root volume was allocated only 1.2GB of space. This problem also occurred when deploying baremetal in Ironic. -------------------------------------------------------------------------------- Filesystem Size Used Avail Use% Mounted on devtmpfs 4.0M 0 4.0M 0% /dev tmpfs 126G 0 126G 0% /dev/shm tmpfs 51G 19M 51G 1% /run /dev/sdb3 1.2G 857M 232M 79% / /dev/sdb1 549M 7.3M 542M 2% /boot/efi tmpfs 26G 0 26G 0% /run/user/1000 -------------------------------------------------------------------------------- If you know the cause of this problem, please let me know. Best regards, Junya Noguchi
On Wed, Jan 22, 2025, at 1:53 AM, Junya Noguchi (Fujitsu) wrote:
Dear Mr. Hanlon
RHEL should be working fine -- we build Rocky Linux images in DIB and they're used in several projects including OSA and Kolla and I maintain them (by defacto ownership). Could you please provide the command you used? Also, can I use the image built by this method in bare metal?
I built the Rocky Linux OS image with the following command. $ disk-image-create rocky-container vm dhcp-all-interfaces block-device-efi openssh-server cloud-init -a arm64 -o rocky_ironic When I deployed a VM with OpenStack using the OS image created with this command, the root volume was allocated only 1.2GB of space. This problem also occurred when deploying baremetal in Ironic. -------------------------------------------------------------------------------- Filesystem Size Used Avail Use% Mounted on devtmpfs 4.0M 0 4.0M 0% /dev tmpfs 126G 0 126G 0% /dev/shm tmpfs 51G 19M 51G 1% /run /dev/sdb3 1.2G 857M 232M 79% / /dev/sdb1 549M 7.3M 542M 2% /boot/efi tmpfs 26G 0 26G 0% /run/user/1000 --------------------------------------------------------------------------------
If you know the cause of this problem, please let me know.
You either need to include the growroot element [0] which will install tooling to dynamically grow the rootfs on first boot or use explicit disk layout configuration [1] to produce an image with all of the filesystems in the sizes you expect them to be. The second option will produce larger images and you'll be more limited in where you can boot them. [0] https://docs.openstack.org/diskimage-builder/latest/elements/growroot/README... [1] https://docs.openstack.org/diskimage-builder/latest/user_guide/building_an_i...
Best regards, Junya Noguchi
Dear Mr. Boylan Thank you for your answer. All disk space is now available using an image built with the addition of a growroot element. -----Original Message----- On Wed, Jan 22, 2025, at 1:53 AM, Junya Noguchi (Fujitsu) wrote:
Dear Mr. Hanlon
RHEL should be working fine -- we build Rocky Linux images in DIB and they're used in several projects including OSA and Kolla and I maintain them (by defacto ownership). Could you please provide the command you used? Also, can I use the image built by this method in bare metal?
I built the Rocky Linux OS image with the following command. $ disk-image-create rocky-container vm dhcp-all-interfaces block-device-efi openssh-server cloud-init -a arm64 -o rocky_ironic When I deployed a VM with OpenStack using the OS image created with this command, the root volume was allocated only 1.2GB of space. This problem also occurred when deploying baremetal in Ironic. -------------------------------------------------------------------------------- Filesystem Size Used Avail Use% Mounted on devtmpfs 4.0M 0 4.0M 0% /dev tmpfs 126G 0 126G 0% /dev/shm tmpfs 51G 19M 51G 1% /run /dev/sdb3 1.2G 857M 232M 79% / /dev/sdb1 549M 7.3M 542M 2% /boot/efi tmpfs 26G 0 26G 0% /run/user/1000 ---------------------------------------------------------------------- ----------
If you know the cause of this problem, please let me know.
You either need to include the growroot element [0] which will install tooling to dynamically grow the rootfs on first boot or use explicit disk layout configuration [1] to produce an image with all of the filesystems in the sizes you expect them to be. The second option will produce larger images and you'll be more limited in where you can boot them. [0] https://docs.openstack.org/diskimage-builder/latest/elements/growroot/README... [1] https://docs.openstack.org/diskimage-builder/latest/user_guide/building_an_i...
Best regards, Junya Noguchi
To whom it may concern I would like to include the build command for RockyLinux images by Diskimage-builder in the Ironic documentation, but does the documentation need that information? https://docs.openstack.org/ironic/latest/user/creating-images.html With the following command, I successfully built an OS image of RockyLinux for Ironic. $ disk-image-create rocky-container vm dhcp-all-interfaces block-device-efi openssh-server cloud-init growroot -a arm64 -o rocky_ironic If the documentation requires the command, then I will write the command in the documentation. Best regards, Junya Noguchi -----Original Message----- From: Noguchi, Junya/野口 惇矢 Sent: Tuesday, January 28, 2025 7:12 PM To: 'Clark Boylan' <cboylan@sapwetik.org>; 'neil@shrug.pw' <neil@shrug.pw>; 'openstack-discuss@lists.openstack.org' <openstack-discuss@lists.openstack.org> Subject: RE: [ironic]About the OS supported by Diskimage-builder Dear Mr. Boylan Thank you for your answer. All disk space is now available using an image built with the addition of a growroot element. -----Original Message----- On Wed, Jan 22, 2025, at 1:53 AM, Junya Noguchi (Fujitsu) wrote:
Dear Mr. Hanlon
RHEL should be working fine -- we build Rocky Linux images in DIB and they're used in several projects including OSA and Kolla and I maintain them (by defacto ownership). Could you please provide the command you used? Also, can I use the image built by this method in bare metal?
I built the Rocky Linux OS image with the following command. $ disk-image-create rocky-container vm dhcp-all-interfaces block-device-efi openssh-server cloud-init -a arm64 -o rocky_ironic When I deployed a VM with OpenStack using the OS image created with this command, the root volume was allocated only 1.2GB of space. This problem also occurred when deploying baremetal in Ironic. -------------------------------------------------------------------------------- Filesystem Size Used Avail Use% Mounted on devtmpfs 4.0M 0 4.0M 0% /dev tmpfs 126G 0 126G 0% /dev/shm tmpfs 51G 19M 51G 1% /run /dev/sdb3 1.2G 857M 232M 79% / /dev/sdb1 549M 7.3M 542M 2% /boot/efi tmpfs 26G 0 26G 0% /run/user/1000 ---------------------------------------------------------------------- ----------
If you know the cause of this problem, please let me know.
You either need to include the growroot element [0] which will install tooling to dynamically grow the rootfs on first boot or use explicit disk layout configuration [1] to produce an image with all of the filesystems in the sizes you expect them to be. The second option will produce larger images and you'll be more limited in where you can boot them. [0] https://docs.openstack.org/diskimage-builder/latest/elements/growroot/README... [1] https://docs.openstack.org/diskimage-builder/latest/user_guide/building_an_i...
Best regards, Junya Noguchi
participants (5)
-
Arne Wiebalck
-
Clark Boylan
-
Dmitry Tantsur
-
Junya Noguchi (Fujitsu)
-
Neil Hanlon