HI, I encounter the same problem. It seems that after pulling to latest stable/beryllium my ~/.m2/settings.xml was got corrupted which cause this error. The workaround that I used was to

Hi All - Your response to below query is much appreciated. thanks in advance pramod On Thursday, March 31, 2016 9:59 PM, Robert Varga <nite@...> wrote: +openflowplugin-dev

Hi all, My stable/beryllium distribution build throws the following warning [WARNING] Could not transfer metadata org.opendaylight.openflowplugin:test-common:0.2.2-SNAPSHOT/maven-metadata.xml

sorry. [0] https://jenkins.opendaylight.org/releng/view/autorelease/job/autorelease-release-boron/lastSuccessfulBuild/artifact/dependencies.log

Here is a dependency log [0] that our autorelease project creates which may be of interest. From that, you can see some 22 projects have openflowplugin as a dependency. However, some of them might

We have the list here: https://wiki.opendaylight.org/view/OpenDaylight_OpenFlow_Plugin:Beryllium:Design:Coexistance#Projects_Affected and

Hi Abhijit, guys one question, I have searched on our wiki and related docs, but I wasn't be able to find any information about downstream projects. Do we have some list of it, or can we create any?

Thank you everyone, lets hope for the brighter tomorrows and even better plugin :) Jozef

Congrats Jozef! Looking forward for even more from you! ---------- Forwarded message ---------- From: Colin Dixon <colin@...> Date: Thu, Mar 31, 2016 at 10:19 AM Subject: Re: [OpenDaylight TSC] [VOTE]

Hi guys, can you give us feedback about bug 4925, it is waiting for review, but no response, if its still doing or if its now ok. We merged latest changes in beryllium and master today, so it would be

+openflowplugin-dev

I started a vote on the mailing list here: https://lists.opendaylight.org/pipermail/tsc/2016-March/004961.html --Colin

Aniruddha, Thanks for putting things into context with the VNFFG link. Its all much clearer now. Regarding communication between VNFs, keeping these definitions from section

Aniruddha, thank you for pointing out this, I’ll check them further. Now I got you point J, you expect SF can reuse tenant VM’s VxLAN port, but it is impossible, that is also why VxLAN-gpe is

Replies inline, please check.

Hello TSC, We (OpenFlow plugin project) would like you to vote to approve Jozef Bacigal as a committer for the OpenFlow Plugin project. We have 5 out of 7 votes from the OpenFlow plugin committers (5

Hi Yi, Thanks for replying. The reason why I am thinking of service-plane as overlay inside a tenant network is because the way ETSI NFV standards have defined VNFFG (VNF-Forwarding-Graphs). Please

Hi Yi Yang, Thanks for the presentation. I have a pair of questions: 1. Slide 6 says “Intel owned ovs nsh support and changed ovs to support push&pop nshð actions, but they are not

On Mar 29, 2016 9:47 AM, "Aniruddha Atale" <Aniruddha.Atale@...> wrote: > > Hi Yi, > Thanks for response. Let me provide some background on the question. Each port of the VM in openstack is part of a

Replies inline, please check.