fuel-dev team mailing list archive

[Nikolay Markov <nmarkov@xxxxxxxxxxxx>]

Hello everybody!

We had a meeting on Fuel (mostly Nailgun) plugins architecture. So, there
were multiple topics to discuss, we didn't really achieve an agreement, but
made some really helpful notes.

1. We should provide infrastructure for plugins, which means making most of
Nailgun entities abstract/default, allowing plugins to override them and
implement their own business logic on top. This may include multiple levels
(usually two), like Neutron plugin and NSX plugin for Neutron plugin.
2. There will be some core plugins, which will be installed together with
Nailgun and can't be deleted without ruining an important functionality.
3. In some cases plugins will override behaviour of default Nailgun HTTP
handlers, but in this case they will follow some certain guides on
formatting.
4. We leave existing hooks as is and add it when needed, it's too hard for
now to determine certain places which may be overrided. Also, we already
need some infrastructure for third-party developers to jump from.
5. Some documentation on how plugins should be provided and tested. As for
now, it looks like each plugin or group of plugins will have it's own repo
and will be provided as a bunch of RPM packages to install into Docker
containers.

Any additions, colleagues?

Also, we're planning to organize a meeting in English tomorrow together
with guys from Poland and maybe other places. Which time is the most
appropriate for you?

-- 
Best regards,
Nick Markov