Open Stack

As no objections were recorded, I'm proceeding with the plan.

Governance change for ironic-python-agent-builder: 
https://review.openstack.org/476900.

On 05/22/2017 04:59 PM, Dmitry Tantsur wrote:
> On 05/22/2017 03:10 PM, Sam Betts (sambetts) wrote:
>> 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.
> 
> +1, I like this one as well.
> 
>>
>> 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.
> 
> Ok, will create after today's meeting (I submitted this thread as a topic there).

https://bugs.launchpad.net/ironic/+bug/1700071

> 
>>
>> Sam
>>
>> 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.
>>      P.S.
>>      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
>>      http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>> __________________________________________________________________________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
> 
> 
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev