Re: Simplify Neutron's Karaf features


Isaku Yamahata
 

Hello Michael.

Personally I just followed what existed and didn't do any improvement.
Please go ahead.
The reason for odl-neutron-logger is that it's very verbose only
for developer so that log file is very bloated with neutron logger.
So it needs to be optional.

I think following features are needed.

- yang models: several backend developers use only yang model(+ restconf)
without Neutron REST API.
- neutron REST API related: several existing features can be consolidated
into one feature.
- neutron logger: to be optional
- hostconfig-ovs: to be optional
- hostconfig-vpp: to be optional
- integration test related one

thanks,

On Thu, Feb 15, 2018 at 06:51:41PM +0100,
Michael Vorburger <vorburger@...> wrote:

Hello,

is there a real reason why there are so many small features in Neutron -
practically one for each bundle?

Karaf features, the way I understand it (please do scream if you disagree!)
are units for dependencies from other projects, and installation. I
obviously still don't fully understand Neutron, but somehow doubt a little
that there is a real need to ever depend on or install say only the
odl-neutron-logger feature?

What are the minimal odl-neutron-* Karaf features that project Neutron
really needs to publish?

I'm willing to work on simplifying this a little.

Tx,
M.
--
Michael Vorburger, Red Hat
vorburger@... | IRC: vorburger @freenode | ~ = http://vorburger.ch
_______________________________________________
neutron-dev mailing list
neutron-dev@...
https://lists.opendaylight.org/mailman/listinfo/neutron-dev

--
Isaku Yamahata <isaku.yamahata@...>

Join z.archive.neutron-dev@lists.opendaylight.org to automatically receive all group messages.