tinyipa cannot boot OS of baremetal node
Hi~ My Rocky OpenStack platform deployed with official documents, includes Keystone/Cinder/Neutron/Nova and Ironic. I used to boot my baremetal nodes by CoreOS downloaded on https://tarballs.opendev.org/openstack/ironic-python-agent/coreos/files/ <https://tarballs.opendev.org/openstack/ironic-python-agent/coreos/files/coreos_production_pxe.vmlinuz> Since I want to customize my own HardwareManager for configuring RAID, I have build TinyIPA image tinyipa.tar.gz and tinyipa.vmlinuz with ironic-python-agent-builder(master branch) and ironic-python-agent(rocky branch). Here are all the products of the build process. [image: image.png] Then I used these two images to create the baremetal node, and boot nova server, but I didn't get the results I wanted, it couldn't enter the ramdisk and always in 'wait call-back' state. as following [image: image.png] I got nothing in /var/log/ironic/ironig-conductor.log and /var/log/nova/nova-compute.log I don't know if these two image (tinyipa.tar.gz and tinyipa.vmlinuz) are valid for Ironic. If not, how can I customize HardwareManager? Looking forward to hearing from you. Ankele
Hello Ankele, if you're using ironic on production servers I suggest you to build and use ironic-python-agent images based on diskimage-builder as explained here: https://docs.openstack.org/ironic-python-agent-builder/latest/admin/dib.html The tinyipa image is best suited for testing and development and not recommended for production usage. Thanks, Riccardo On Tue, Jan 5, 2021 at 5:45 PM Ankele zhang <ankelezhang@gmail.com> wrote:
Hi~
My Rocky OpenStack platform deployed with official documents, includes Keystone/Cinder/Neutron/Nova and Ironic.
I used to boot my baremetal nodes by CoreOS downloaded on https://tarballs.opendev.org/openstack/ironic-python-agent/coreos/files/ <https://tarballs.opendev.org/openstack/ironic-python-agent/coreos/files/coreos_production_pxe.vmlinuz>
Since I want to customize my own HardwareManager for configuring RAID, I have build TinyIPA image tinyipa.tar.gz and tinyipa.vmlinuz with ironic-python-agent-builder(master branch) and ironic-python-agent(rocky branch). Here are all the products of the build process. [image: image.png] Then I used these two images to create the baremetal node, and boot nova server, but I didn't get the results I wanted, it couldn't enter the ramdisk and always in 'wait call-back' state. as following
[image: image.png] I got nothing in /var/log/ironic/ironig-conductor.log and /var/log/nova/nova-compute.log
I don't know if these two image (tinyipa.tar.gz and tinyipa.vmlinuz) are valid for Ironic. If not, how can I customize HardwareManager?
Looking forward to hearing from you.
Ankele
Thanks for the tip! I have make images based on dib of ironic-python-agent-builder, and it's really useful. Ankele Riccardo Pittau <elfosardo@gmail.com> 于2021年1月6日周三 下午5:10写道：
Hello Ankele,
if you're using ironic on production servers I suggest you to build and use ironic-python-agent images based on diskimage-builder as explained here:
https://docs.openstack.org/ironic-python-agent-builder/latest/admin/dib.html
The tinyipa image is best suited for testing and development and not recommended for production usage.
Thanks,
Riccardo
On Tue, Jan 5, 2021 at 5:45 PM Ankele zhang <ankelezhang@gmail.com> wrote:
Hi~
My Rocky OpenStack platform deployed with official documents, includes Keystone/Cinder/Neutron/Nova and Ironic.
I used to boot my baremetal nodes by CoreOS downloaded on https://tarballs.opendev.org/openstack/ironic-python-agent/coreos/files/ <https://tarballs.opendev.org/openstack/ironic-python-agent/coreos/files/coreos_production_pxe.vmlinuz>
Since I want to customize my own HardwareManager for configuring RAID, I have build TinyIPA image tinyipa.tar.gz and tinyipa.vmlinuz with ironic-python-agent-builder(master branch) and ironic-python-agent(rocky branch). Here are all the products of the build process. [image: image.png] Then I used these two images to create the baremetal node, and boot nova server, but I didn't get the results I wanted, it couldn't enter the ramdisk and always in 'wait call-back' state. as following
[image: image.png] I got nothing in /var/log/ironic/ironig-conductor.log and /var/log/nova/nova-compute.log
I don't know if these two image (tinyipa.tar.gz and tinyipa.vmlinuz) are valid for Ironic. If not, how can I customize HardwareManager?
Looking forward to hearing from you.
Ankele
Hi, TinyIPA may not work for real hardware, you need to either build a custom CoreOS image or a DIB-based image. Dmitry On Tue, Jan 5, 2021 at 5:39 PM Ankele zhang <ankelezhang@gmail.com> wrote:
Hi~
My Rocky OpenStack platform deployed with official documents, includes Keystone/Cinder/Neutron/Nova and Ironic.
I used to boot my baremetal nodes by CoreOS downloaded on https://tarballs.opendev.org/openstack/ironic-python-agent/coreos/files/ <https://tarballs.opendev.org/openstack/ironic-python-agent/coreos/files/coreos_production_pxe.vmlinuz>
Since I want to customize my own HardwareManager for configuring RAID, I have build TinyIPA image tinyipa.tar.gz and tinyipa.vmlinuz with ironic-python-agent-builder(master branch) and ironic-python-agent(rocky branch). Here are all the products of the build process. [image: image.png] Then I used these two images to create the baremetal node, and boot nova server, but I didn't get the results I wanted, it couldn't enter the ramdisk and always in 'wait call-back' state. as following
[image: image.png] I got nothing in /var/log/ironic/ironig-conductor.log and /var/log/nova/nova-compute.log
I don't know if these two image (tinyipa.tar.gz and tinyipa.vmlinuz) are valid for Ironic. If not, how can I customize HardwareManager?
Looking forward to hearing from you.
Ankele
-- 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 O'Neill
participants (3)
-
Ankele zhang
-
Dmitry Tantsur
-
Riccardo Pittau