[openstack-dev] [ironic] [tripleo] [dib] RFC: moving/transitioning the ironic-agent element to the ironic-python-agent tree

Sam Betts (sambetts) sambetts at cisco.com
Mon May 22 13:10:10 UTC 2017

I would like to suggest that we create a new repo for housing the tools required to build ironic python agent images: ironic-python-agent-builder(tooling). This would include, the DIB element, the existing coreos and tinyipa methods and hopefully in the future the buildroot method for creating IPA images.

The reason I propose a separation of tooling and IPA itself is that the tooling is mostly detached from which version of IPA is being built into the image, and often when we make changes to the tooling that change should be included in images built for all versions of IPA which involves us having to backport these changes to all currently maintained versions of IPA.

Hopefully having this as a separate repo will also simplify packaging for distros as they won’t need to include IPA itself with the tooling to build it.

I’m happy with the name ironic-python-agent for the element, I think that is more intuitive anyway.

An RFE or multiple might be useful for tracking this work.


On 22/05/2017, 13:40, "Dmitry Tantsur" <dtantsur at redhat.com> wrote:

    Hi all!
    Some time ago we discussed moving ironic-agent element that is used to build IPA 
    to IPA tree itself. It got stuck, and I'd like to restart the discussion.
    The reason for this move is to make the DIB element in question one of 
    *official* ways to build IPA. This includes gating on both IPA and the element 
    changes, which we currently don't do.
    The primary concern IIRC was elements name clash. We can solve it by just 
    renaming the element. The new one will be called "ironic-python-agent".
     From the packaging perspective, we'll create a new subpackage 
    openstack-ironic-python-agent-elements (the RDO name, may differ for other 
    distribution) that will only ship /usr/share/ironic-python-agent-elements with 
    the ironic-python-agent element within it. To pick the new element, the 
    consumers will have to add /usr/share/ironic-python-agent-elements to the 
    ELEMENTS_PATH, and change the element name from ironic-agent to ironic-python-agent.
    Please let me know what you think about the approach. If there are no objects, 
    I'll work on this move in the coming weeks.
    Do we need an Ironic RFE for that?
    OpenStack Development Mailing List (not for usage questions)
    Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe

More information about the OpenStack-dev mailing list