Assaf Muller <assaf@...> wrote: Mike and Michel should raise it at the PTG for discussion. I know Mike will attend. thanks, -- Isaku Yamahata <isaku.yamahata@...>

Hello Michael. Again please go ahead! In short those are technical debt and low hanging fruit. I'm not sure about if you have a special meaning by 101%, though. (Does this 1% make big

Hello, The way NeutronCRUDInterfaces (called from AbstractNeutronNorthbound) is currently implemented, by dynamically looking-up INeutronCRUD implementations from the OSGi registry, every time, isn't

==> https://git.opendaylight.org/gerrit/#/c/68339/

Michael Vorburger <vorburger@...> wrote: Cool! Yeah. Let's merge it early Fluorine cycle. Yeah. install/uninstall the feature was enough/convenient for me. Thanks, -- Isaku Yamahata

I had a closer look at this based on what you wrote below, and with a bit of grep on finding which of these features are also referenced from other projects, it seems to me that there seems to be only

The code simply is inherited from beforex-blueprit era. i.e. Config Subsystem era. The way you propose would be good simplification. Thanks, Michael Vorburger <vorburger@...> wrote: --

Hello, I'm trying to understand what the point of NeutronTranscriberProvider is, but I cannot see any... may I propose a Gerrit which completely ditches that, and replaces it with simple

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

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

Hello Vivek. Will you(or someone on behalf of you) attend ONS or openstack PTG? N Vivekanandan <n.vivekanandan@...> wrote: There are two aspect. - journal thread thrashing - journal db

Hi Team, We were contemplating to use v2 Driver for production after noticing that it has huge improvements over the v1 Driver. Primarily in terms of its stability to use in HA active-active

An interesting exercise would be to add 'raise ValueError' type exceptions in various ODL ML2 mech driver flows and seeing which tests fail. Basically, if a test passes without the ODL mech driver

Dimple, upon re-reading your original email with "add logs for the operator level northbound request and response" I'm guessing you want to log the web requests? AFAIK Jetty (used in Karaf) can

Michael Vorburger <vorburger@...> wrote: Regarding to hooking rest request/response, it can be done without intrusive code modification to add filter and logger. web.xml can be updated to or

I'm not sure what you mean by "log handler", but why can't you just achieve this with tweaking the standard log configuration file? You should be able to just add an additional file logger thing for

Hi, We have a requirement to add logs for the operator level northbound request and response to a separate log file i.e., not to the default karaf log file. This would involve creating one more

This seems to "just" be a timeout related problem in the ITNeutronE2E.test, and probably won't happen again on the next run. But ultimately we need to find a better solution this, in general, not

Attention neutron-devs, Autorelease nitrogen failed to build integration-test from neutron in build 380. Attached is a snippet of the error message related to the failure that we were able to

Hi All, While migrating Vm instances, connection (ssh and ping) failed between the VM instances. PFB bug https://jira.opendaylight.org/browse/NETVIRT-1049 Bug reproduction