[openstack-dev] [fuel][plugins] Should we maintain example plugins?
mmosesohn at mirantis.com
Thu Mar 3 14:19:13 UTC 2016
I would like to bring your attention a dilemma we have here. It seems
that there is a dispute as to whether we should maintain the releases
list for example plugins. In this case, this is for adding version
9.0 to the list.
Right now, we run a swarm test that tries to install the example
plugin and do a deployment, but it's failing only for this reason. I
should add that this is the only automated daily test that will verify
that our plugin framework actually works. During the Mitaka
development cycle, we already had an extended period where plugins
were broken. Removing this test (or leaving it permanently red,
which is effectively the same), would raise the risk to any member of
the Fuel community who depends on plugins actually working.
The other impact of abandoning maintenance of example plugins is that
it means that a given interested Fuel Plugin developer would not be
able to easily get started with plugin development. It might not be
inherently obvious to add the current Fuel release to the
metadata.yaml file and it would likely discourage such a user. In this
case, I would propose that we remove example plugins from fuel-plugins
GIT repo if they are not maintained. Non-functioning code is worse
than deleted code in my opinion.
Please share your opinions and let's decide which way to go with this bug
More information about the OpenStack-dev