[openstack-dev] [fuel] Fuel plugins: lets have some rules

Dmitry Borodaenko dborodaenko at mirantis.com
Fri Feb 26 23:54:32 UTC 2016

On Thu, Feb 25, 2016 at 08:31:26AM +0100, Andreas Jaeger wrote:
> On 2016-02-03 03:27, Dmitry Borodaenko wrote:
> > [...]
> > Level 1. Plugin is actively supported by Fuel team
> > 
> > As we expand plugin capabilities and move more functionality from Fuel
> > core into plugins, we will inevitably get to the point where some
> > plugins are required to successfully complete even a basic deployment
> > (aka "pass BVT"). Even before that, we may decide that some plugins are
> > important enough for our reference architecture to allow the state of
> > these plugins to affect our release cycle: allow Critical bugs in them
> > to affect Fuel release, cover them in acceptance testing for Fuel
> > releases and maintenance updates, and so on.
> > Obviously, whole Fuel team is expected to support such plugins, and is
> > self-motivated to provide timely help to their maintainers to keep them
> > healthy. In addition to the expectations from the previous support
> > level, we should track the list of these release-critical plugins in the
> > policy section of fuel-specs [7].
> So, these are plugins that will be officially part of fuel team? You
> depend on it for successful installation...

Yes, they will officially become a part of Fuel project. First such
example is likely to be the Murano plugin [0], so we can use it a the
guinea pig to try out this process.

[0] https://review.openstack.org/269567

As described in the corresponding spec [1], we plan this plugin to
co-exist with the current non-plugin implementation for Mitaka, and then
let the legacy non-plugin implementation be superceded by
fuel-plugin-murano as soon as the latter reaches maturity (hopefully
early in Newton cycle).

[1] https://review.openstack.org/275124

Since this is not a straight-forward moving of existing code into its
own git repo (like we've recently done for fuel-virtualbox and fuel-ui),
I think it's too early to register the new plugin repo in
openstack/governance, but eventually (as soon as it's ready to become
the default way to deploy Murano with Fuel) we should add it there.

> Andreas
> > [7] https://git.openstack.org/cgit/openstack/fuel-specs/tree/policy
> > 
> > Thoughts, comments, objections?
> > 
> -- 
>  Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
>   SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
>    GF: Felix Imendörffer, Jane Smithard, Graham Norton,
>        HRB 21284 (AG Nürnberg)
>     GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
> __________________________________________________________________________
> 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

More information about the OpenStack-dev mailing list