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

Dmitry Tantsur dtantsur at redhat.com
Tue Apr 14 09:45:16 UTC 2020

On Thu, Apr 9, 2020 at 7:26 PM Jeremy Stanley <fungi at yuggoth.org> wrote:

> On 2020-04-08 10:04:25 +0200 (+0200), Dmitry Tantsur wrote:
> > On Tue, Apr 7, 2020 at 4:37 PM Jeremy Stanley <fungi at yuggoth.org> wrote:
> [...]
> > > Why *can't* OpenShift include OpenStack projects? I haven't seen
> > > this adequately explained.
> >
> > It's less of a technical issue, but more of misunderstanding that
> > including an OpenStack project does not involve literally
> > installing OpenStack. And no matter what we think, for a lot of
> > people OpenStack==Nova (another marketing issue to address?).
> [...]
> I don't understand why that would make a difference in this case,
> unless you're saying that the people who make architectural
> decisions about what's included in OpenShift have no actual
> familiarity with Ironic and OpenStack. If you know anyone who works
> at that company, can you help them understand the difference?

Let's de-focus on OpenShift please. People who just need a bare metal
management solution don't need to understand what OpenStack is. What would
they assume from a quick search? The first link I've got by googling in a
private window is our web site with:

OpenStack software controls large pools of compute, storage, and networking
resources throughout a datacenter, managed through a dashboard or via the
OpenStack API. OpenStack works with popular enterprise and open source
technologies making it ideal for heterogeneous infrastructure.

Is it so unexpected they assume Ironic needs virtual machines to operate?

> > On one hand, large distributions want us to have stable branches
> > every year or two. Even what we have is too much.
> >
> > On the other - we have small consumers who could benefit from just
> > pulling the latest(ish) release and knowing that if a serous bug
> > is found there, they won't have to update to the next feature (and
> > potentially major) release.
> [...]
> This sounds like a problem shared by, well, basically every other
> project in OpenStack too. Perhaps it's an opportunity to collaborate
> on finding solutions.

+1000 although I'm not sure if all projects are interested in intermediate
releases. Given how many follow the cycle-with-rc model, I doubt it.


> --
> Jeremy Stanley
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20200414/c59cc481/attachment.html>

More information about the openstack-discuss mailing list