<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Apr 6, 2020, at 7:14 AM, Dmitry Tantsur <<a href="mailto:dtantsur@redhat.com" class="">dtantsur@redhat.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div dir="ltr" class=""><br class=""></div><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Apr 6, 2020 at 1:03 PM Sean Mooney <<a href="mailto:smooney@redhat.com" class="">smooney@redhat.com</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Mon, 2020-04-06 at 10:10 +0200, Dmitry Tantsur wrote:<br class="">
> The problem is that oslo libraries are OpenStack-specific. Imagine metal3,<br class="">
> for example. When building our images, we can pull (most of) regular Python<br class="">
> packages from the base OS, but everything with "oslo" in its name is on us.<br class="">
> It's a maintenance burden.<br class="">
<br class="">
what distros dont ship oslo libs?<br class="">
<br class="">
RHEL ships them via the OSP repos<br class=""></blockquote><div class=""><br class=""></div><div class="">As part of OpenStack, right.<br class=""></div><div class=""> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
CentOS ship it via RDO<br class="">
Ubunutu has them in the cloud archive<br class="">
SUSE also shiped them via there openstack product although sicne they are nolonger<br class="">
maintaining that goign forward and moveing the k8s based cloud offerings it might be<br class="">
a valid concern there.<br class=""></blockquote><div class=""><br class=""></div><div class="">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.<br class=""></div></div></div></div></blockquote><div><br class=""></div><div>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.</div><div><br class=""></div><div>Doug</div><div><br class=""></div></div></body></html>