tinyipa cannot boot OS of baremetal node

Ankele zhang ankelezhang at gmail.com
Tue Jan 5 03:22:52 UTC 2021


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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20210105/0eddb166/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 126537 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20210105/0eddb166/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 27968 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20210105/0eddb166/attachment-0003.png>


More information about the openstack-discuss mailing list