osdir.com


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


Hi,

On Mon, Apr 6, 2020 at 4:45 PM Mohammed Naser <mnaser at vexxhost.com> wrote:

> Hi Dmitry,
>
> Thank you for raising this.  I think what you're looking for makes
> sense, I don't think splitting outside OpenStack is the right solution
> for this.  There are many logistical issues in doing this.
>

I do agree with this.


>
> First of all, it promotes even more bureaucracy within our community
> which is something that we're trying to split.   "Ironic" and
> "OpenStack" becoming two separate pieces means that we've failed as a
> community to be able to deliver what OpenStack is.  If we do this, we
> further promote the separation of our communities and that is not
> sustainable.  With a dwindling contributor base, we'll find power in
> standing together in big groups, not by isolating ourselves to small
> islands.
>

This sounds a bit like the "us vs them" mentality, which I think may be
hurting OpenStack now. I think we should be more open to the things that
happen outside of our control. This also goes back to my points about Oslo
and the bigger Python world.


>
> Arguably, you would say that "well, Ironic is picking up outside
> OpenStack and we want to capitalize on that".  I agree with you on
> that, I think we should absolutely do that.  However, I think simply
> just becoming a top-level project is not the way to go about this.  It
> will introduce a lot more work to our (already overwhelmed) OSF staff,
> it means maintaining a new identity, it means applying to be a pilot
> project and going through the whole process.  It means that all
> existing developer may need to have to revise the way they do work
> because they have signed the CCLA for OpenStack and not "Ironic".
>

I fully agree, this is unfortunate.


> We're adding a whole lot of bureaucray when the problem is messaging.
>
> I've gone over your points below about what you think this will do and
> strongly suggest those alternatives.
>
> Regards,
> Mohammed
>
> On Wed, Apr 1, 2020 at 1:07 PM Dmitry Tantsur <dtantsur at redhat.com> wrote:
> >
> > Hi everyone!
> >
> > This topic should not come as a huge surprise for many, since it has
> been raised numerous times in the past years. I have a feeling that the end
> of Ussuri, now that weâ??ve re-acquired our PTL and are on the verge of
> selecting new TC members, may be a good time to propose it for a formal
> discussion.
> >
> > TL;DR Iâ??m proposing to make Ironic a top-level project under opendev.org
> and the OpenStack Foundation, following the same model as Zuul. I donâ??t
> propose severing current relationships with other OpenStack projects, nor
> making substantial changes in how the project is operated.
> >
> > (And no, itâ??s not an April 1st joke)
> >
> > Background
> > =========
> >
> > Ironic was born as a Nova plugin, but has grown way beyond this single
> case since then. The first commit in Bifrost dates to February 2015. During
> these 5 years (hey, we forgot to celebrate!) it has developed into a
> commonly used data center management tool - and still based on standalone
> Ironic! The Metal3 project uses standalone Ironic as its hardware
> management backend. We havenâ??t been â??justâ?? a component of OpenStack for a
> while now, I think itâ??s time to officially recognize it.
> >
> > And before you ask: in no case do I suggest scaling down our invaluable
> integration with Nova. Weâ??re observing a solid growth of deployments using
> Ironic as an addition to their OpenStack clouds, and this proposal doesnâ??t
> try to devalue this use case. The intention is to accept publicly and
> officially that itâ??s not the only or the main use case, but one of the main
> use cases. I donâ??t think it comes as a surprise to the Nova team.
> >
> > Okay, so why?
> > ===========
> >
> > The first and the main reason is the ambiguity in our positioning. We do
> see prospective operators and users confused by the perception that Ironic
> is a part of OpenStack, especially when it comes to the standalone use
> case. â??But what if I donâ??t need OpenStackâ?? is a question that I hear in
> most of these conversations. Changing from â??a part of OpenStackâ?? to â??a FOSS
> tool that can integrate with OpenStackâ?? is critical for our project to keep
> growing into new fields. To me personally it feels in line with how OpenDev
> itself is reaching into new areas beyond just the traditional IaaS. The
> next OpenDev even will apparently have a bare metal management track, so
> why not a top-level project for it?
> >
> > Another reason is release cadence. We have repeatedly expressed the
> desire to release Ironic and its sub-projects more often than we do now.
> Granted, *technically* we can release often even now. We can even abandon
> the current release model and switch to â??independentâ??, but it doesnâ??t
> entirely solve the issue at hand. First, we donâ??t want to lose the notion
> of stable branches. One way or another, we need to support consumers with
> bug fix releases. Second, to become truly â??independentâ?? weâ??ll need to
> remove any tight coupling with any projects that do integrated releases.
> Which is, essentially, what Iâ??m proposing here.
> >
> > Finally, I believe that our independence (can I call it â??Irexitâ??
> please?) has already happened in reality, we just shy away from recognizing
> it. Look:
> > 1. All integration points with other OpenStack projects are optional.
> > 2. We can work fully standalone and even provide a project for that.
> > 3. Many new features (RAID, BIOS to name a few) are exposed to
> standalone users much earlier than to those going through Nova.
> > 4. We even have our own mini-scheduler (although its intention is not
> and has not been to replace the Placement service).
> > 5. We make releases more often than the â??coreâ?? OpenStack projects (but
> see above).
> >
> > What we will do
> > ============
> >
> > This proposal involves in the short term:
> > * Creating a new git namespace: opendev.org/ironic
>
> We could totally do this for all existing projects honestly.  I think
> the TC could probably be okay with this.
>

That's an interesting thought, actually. Maybe rather than one "openstack"
namespace we can have a namespace per program? Like opendev.org/compute/nova,
etc? This may also solve a part of the problem with oslo libraries adoption
outside of OpenStack. opendev.org/libs/stevedore doesn't suggest that it
belongs to openstack the same way as opendev.org/openstack/stevedore. And
it will provide an obvious link between code names and purposes! Who can we
talk to to make this happen?


>
> > * Creating a new website (name TBD, bare metal puns are welcome).
> >    * If we can have https://docs.opendev.org/ironic/, it may be just
> fine though.
>
> Who's going to work on this website?  It's important to not only have
> a website but keep it maintained, add more content, update it.


We do realize this, and we're already doing it, to some extent, with
docs.o.o/ironic. It's unfortunate that we don't have dedicated designers
and technical writers, but it's already our reality.

Note that I don't suggest a highly dynamic web site. More of a
consumer-oriented landing page like http://metal3.io/ and an
umbrella-neutral hosting for documentation like http://tripleo.org/. I do
agree with Thierry that it's doable without the actual split, but then it
needs cooperation from the Foundation and the TC.


> The
> website will have absolutely zero traction initially and we'll miss
> out on all the "traffic" that OpenStack.org gets.  I think what we
> should actually do is redesign OpenStack.org so that it's a focused
> about the OpenStack projects and move all the foundation stuff to
> osf.dev -- In there, we can nail down the messaging of "you don't need
> all of OpenStack".
>

I don't think keeping ironic on openstack.org will help you nail it down.


>
> > * Keeping the same governance model, only adjusted to the necessary
> extent.
>
> This is not easy, you'll have to come up with a whole governance, run
> elections, manage people.  We already have volunteers that help do
> this inside OpenStack, why add all that extra layer?
>
> > * Keeping the same policies (reviews, CI, stable).
>
> That seems reasonable to me
>
> > * Defining a new release cadence and stable branch support schedule.
>
> If there is anything in the current model that doesn't suit you,
> please bring it up, and let's revise it.  I've heard this repeated a
> lot as a complaint from the Ironic team and I've unfortunately not
> seen any proposal about an ideal alternative.  We need to hear things
> to change things.
>

There is no ideal alternative, this is why most of these discussions get
stuck. We may need to look at the Swift model since it seems closer to what
we're aiming at. Which are:
1) More frequent releases with a possibility of bug-fix support for them
(i.e. short-lived stable branches) and upgrades (time to ditch grenade?).
2) Stop release-to-release matching for interactions with other services
(largely achieved by microversioning).
3) Support for non-coordinated releases in installation tools (okay, this
one is fun, I'm not sure how to approach it).


>
> > In the long term we will consider (not necessary do):
> > * Reshaping our CI to rely less on devstack and grenade (only use them
> for jobs involving OpenStack).
>
> That seems reasonable to have more Ironic "standalone" jobs.  It is
> important that _the_ biggest consumers *are* the OpenStack ones, let's
> not alienate them so we end up in a world of nothing new.
>

I'm not sure I get your proposal. If you suggest that we keep most of our
testing on devstack/grenade/tempest with the whole OpenStack, this is
something we're moving away from, no matter if split or not. The current
approach to CI testing simply doesn't scale well enough to cover our
feature set.


>
> > * Reducing or removing reliance on oslo libraries.
>
> Why?
>

I've left some thoughts in my previous replies, but I don't quite like the
way we're creating silos in OpenStack. Everyone is depending on oslo.utils,
sometimes for one tiny helper (bool_from_string anyone?). Couldn't we move
it to Python stdlib? I think the existence of our semi-private libraries
discourages reaching out to the whole infrastructure. Everything depends on
oslo.i18n, cannot we use the built-in gettext instead? Why is everything
pulling in Babel even though nothing imports it? Sorry, this is turning
into a rant, the essence of which is that we're taking a too easy approach
to requirements.


>
> > * Stopping using rabbitmq for messaging (weâ??ve already made it optional).
>
> Please.  Please.  Whatever you replace it with, just update
> oslo.messaging and make all of us happy to stop using it.  It's hell.
>

I'd be happy to, but I think the oslo.messaging API is designed around the
AMQP pattern too much. I'm getting back to my rant above: do all projects
really need a messaging queue? When I asked this question in Ironic, we
realized that we don't. We simply introduced JSON RPC support instead.

Dmitry


>
> > * Integrating with non-OpenStack services (kubernetes?) and providing
> lighter alternatives (think, built-in authentication).
>
> I support this, and I think there's nothing stopping you from doing
> that today.  If there is, let's bring it up.
>
> > What we will NOT do
> > ================
> >
> > At least this proposal does NOT involve:
> > * Stopping maintaining the Ironic virt driver in Nova.
> >    * Stopping running voting CI jobs with OpenStack services.
> > * Dropping optional integration with OpenStack services.
> > * Leaving OpenDev completely.
> >
> > What do you think?
> > ===============
> >
> > Please let us know what you think about this proposal. Any hints on how
> to proceed with it, in case we reach a consensus, are also welcome.
> >
> > Cheers,
> > Dmitry
>
>
>
> --
> Mohammed Naser â?? vexxhost
> -----------------------------------------------------
> D. 514-316-8872
> D. 800-910-1726 ext. 200
> E. mnaser at vexxhost.com
> W. https://vexxhost.com
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20200407/8a523cf4/attachment-0001.html>