[tc] [ironic] Promoting ironic to a top-level opendev project?

Doug Hellmann doug at doughellmann.com
Mon Apr 6 14:59:38 UTC 2020

> On Apr 6, 2020, at 7:14 AM, Dmitry Tantsur <dtantsur at redhat.com> wrote:
> On Mon, Apr 6, 2020 at 1:03 PM Sean Mooney <smooney at redhat.com <mailto:smooney at redhat.com>> wrote:
> On Mon, 2020-04-06 at 10:10 +0200, Dmitry Tantsur wrote:
> > The problem is that oslo libraries are OpenStack-specific. Imagine metal3,
> > for example. When building our images, we can pull (most of) regular Python
> > packages from the base OS, but everything with "oslo" in its name is on us.
> > It's a maintenance burden.
> what distros dont ship oslo libs?
> RHEL ships them via the OSP repos
> As part of OpenStack, right.
> CentOS ship it via RDO
> Ubunutu has them in the cloud archive
> SUSE also shiped them via there openstack product although sicne they are nolonger
> maintaining that goign forward and moveing the k8s based cloud offerings it might be
> a valid concern there.
> All the same here: oslo libs are parts of OpenStack distributions/offerings. Meaning that to install Ironic you need to at least enable OpenStack repositories, even if you package Ironic yourself.

This issue is internal to Red Hat and our choices in how we manage our resources to package things for distribution. I don’t think moving Ironic out of OpenStack at the community level is going to make the problem go away.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20200406/a782464e/attachment.html>

More information about the openstack-discuss mailing list