Open Stack

ironic-python-agent-builder is a small wrapper around diskimage-builder --
you can check diskimage-builder documentation for how to setup support.

If you're using a redhat-like distribution, you can likely use the existing
redhat distro support element to try and make it work for your similar
distribution.

Good luck,
Jay





On Sun, Feb 19, 2023 at 5:22 AM 韩光宇 <hanguangyu2 at gmail.com> wrote:

> Hi,
>
> The OS which we want to mirror the randisk for is not supported by
> ironic-python-agent-builder and diskimage-builder.（It references
> Fedora and CentOS a lot for the rpm packages building. So somewhat it
> can be treated as a redhat family distro）
>
> So we need to compare the workload of manual production or adding new
> OS support for ironic-python-agent-builder. We are new to this field,
> is there any recommended reference for making manual ramdisk（possible
> interim measures） or adding os support for
> ironic-python-agent-builder（Definitely a better solution in the long
> run）
>
> Appreciate any kind of guidance or help.
>
> Han
>
> Jay Faulkner <jay at gr-oss.io> 于2023年2月18日周六 02:28写道：
> >
> > Hey,
> >
> > I strongly suggest using ironic-python-agent-builder to create your
> ramdisks and then mirror them separately. Customizing the image comes with
> several benefits:
> > * Ability to customize cleaning of bespoke hardware using hardware
> managers + custom tooling
> https://docs.openstack.org/ironic-python-agent/latest/contributor/hardware_managers.html
> > * Ability to choose the distribution you use (note: we only test a
> couple in CI)
> > * Ability to add in extra pieces specific to your environment, such as
> credentials. I've even been in a case where I needed to inject an iptables
> configuration in order to receive security approval for a deployment.
> >
> > There is a giant downside to building your own images: the images in the
> linked locations in tarballs.opendev.org are only published when those
> specific commits were passing CI. This gives you a stronger behavior
> guarantee than you get when you build your own.
> >
> > As for mirroring; our opendev partners may have anintegration they might
> offer but frankly, if I were doing it myself, I'd probably use a tool such
> as httrack to sync the files down periodically.
> >
> > Good luck, let me know if you have any additional questions.
> >
> > -
> > Jay Faulkner
> > Ironic PTL
> >
> > On Fri, Feb 17, 2023 at 9:56 AM 任亮 <renliang at uniontech.com> wrote:
> >>
> >> Hi
> >>
> >> The.kernel and.initramfs images contained in ramdisk are used to use
> bare metal services.
> >> The open source address provides centos ramdisk mirroring.
> >> https://tarballs.opendev.org/openstack/ironic-python-agent/dib/files/
> >>
> https://tarballs.opendev.org/openstack/ironic-python-agent-builder/dib/files/
> >>
> >> I want to build our own ramdisk mirror, and I would like to ask whether
> there is a way to manually make ramdisk mirror. If so, how to add the
> ironic python agent service to it? Or use the ironic-python-agent-builder
> tool to support other system construction methods.
> >> ________________________________
> >> 发自我的企业微信
> >>
> >>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.openstack.org/pipermail/openstack-discuss/attachments/20230220/776bd723/attachment-0001.htm>