Re: [controller-dev] [mdsal-dev] Serialize/Deserialize DTOs to JSON

Hi Robert, In this case, the CONSUMER *is cognizant* of what Clazz (NetworkTopology.class in below case) to use to get the NN(NormalizedNode) converted into corresponding BA. DataObject obj = BindingNormalizedNodeCodecRegistry.fromNormalizedNode(YangInstanceIdentifier.of(BindingReflections.f

Re: [controller-dev] etc/jetty.xml port 8080 and 8181

On Wednesday, August 31, 2016, Luis Gomez wrote: > In any case it would be good to clarify in documentation or somewhere > which port should be primarily used in ODL as I think many people > (including me) thought it was 8181 as I can see in many user guides and > even in our system test. > I wa

Re: [controller-dev] etc/jetty.xml port 8080 and 8181

Thanks for checking and encouraging me to check :) Ed On Wed, Aug 31, 2016 at 3:50 PM, Luis Gomez wrote: > Correction, you are right both ports are open :) > > On Aug 31, 2016, at 3:30 PM, Luis Gomez wrote: > > OK, then something happened after because today 8181 is the port everybody > uses a

Re: [controller-dev] etc/jetty.xml port 8080 and 8181

Luis, 8080 is on by default in Boron RC2: https://nexus.opendaylight.org/content/repositories/autorelease-1455/org/opendaylight/integration/distribution-karaf/0.5.0-Boron-RC2/distribution-karaf-0.5.0-Boron-RC2.tar.gz (I just tried it) I know some projects (like netvirt) disable it for various r

Re: [controller-dev] etc/jetty.xml port 8080 and 8181

right, CSIT uses 8181 exclusively I think: https://github.com/opendaylight/integration-test/blob/master/csit/variables/Variables.py#L185 JamO On 08/31/2016 04:07 PM, Luis Gomez wrote: In any case it would be good to clarify in documentation or somewhere which port should be primarily used in

Re: [controller-dev] etc/jetty.xml port 8080 and 8181

In any case it would be good to clarify in documentation or somewhere which port should be primarily used in ODL as I think many people (including me) thought it was 8181 as I can see in many user guides and even in our system test. BR/Luis > On Aug 31, 2016, at 3:50 PM, Luis Gomez wrote: >

Re: [controller-dev] [mdsal-dev] Serialize/Deserialize DTOs to JSON

On 08/24/2016 01:21 PM, Sela, Guy wrote: > The only way it is working for me now, is the following (Some of it is > pseudo-code): > " > PRODUCER CODE: > I have a > org.opendaylight.yang.gen.v1.urn.tbd.params.xml.ns.yang.network.topology.rev131021.network.topology.topology.Node > in my hands (Got

Re: [controller-dev] etc/jetty.xml port 8080 and 8181

Correction, you are right both ports are open :) > On Aug 31, 2016, at 3:30 PM, Luis Gomez wrote: > > OK, then something happened after because today 8181 is the port everybody > uses and 8080 is not even open. > > >> On Aug 31, 2016, at 12:18 PM, Edward Warnicke >

Re: [controller-dev] etc/jetty.xml port 8080 and 8181

OK, then something happened after because today 8181 is the port everybody uses and 8080 is not even open. > On Aug 31, 2016, at 12:18 PM, Edward Warnicke wrote: > > It did :) > > https://github.com/opendaylight/odlparent/blob/master/karaf/opendaylight-karaf-resources/src/main/resources/etc

Re: [controller-dev] [mdsal-dev] Conceptual Data Tree questions

On 08/31/2016 04:51 PM, Sela, Guy wrote: > Thanks, > Inline > > On 08/31/2016 01:09 PM, Sela, Guy wrote: >> Hi, >> >> I've being reading this document: >> >> https://github.com/opendaylight/mdsal/blob/master/src/site/asciidoc/co >> nceptual-data-tree.adoc >> >> >> >> I have a few questions. >> >

Re: [controller-dev] Boron Blocker Bugs

It is a blocker. Per my comments I have submitted a patch awaiting review. However I am struggling to get jenkins +1 due to infra issues. The patch is in master but will CP as soon as I get +1 jenkins and review. On Wed, Aug 31, 2016 at 4:10 PM, An Ho wrote: > Is this still a blocker bug for Bor

[controller-dev] Boron Blocker Bugs

Is this still a blocker bug for Boron? If it has been fixed, please mark the bug as fixed and resolved (STATUS=RESOLVED). If the bug will not be fixed in Boron, please retarget the bug for Carbon (ODL SR TARGET MILESTONE=CARBON). If this bug is still a blocker bug for Boron, please provide an

Re: [controller-dev] etc/jetty.xml port 8080 and 8181

It did :) https://github.com/opendaylight/odlparent/blob/master/karaf/opendaylight-karaf-resources/src/main/resources/etc/jetty.xml#L58 I know... I'm the one who did it: https://git.opendaylight.org/gerrit/#/c/13546/ (a lot of work actually went into moving RESTCONF to 8080, because for backward

Re: [controller-dev] etc/jetty.xml port 8080 and 8181

If the plan was to shift RESTCONF back to 8080, I do not think that ever happened :) > On Aug 31, 2016, at 11:52 AM, Edward Warnicke wrote: > > Huh... I remember slightly differently... because the 8080 for the old ADSAL > couldn't coexist with the RESTCONF, which is why RESTCONF originally we

Re: [controller-dev] etc/jetty.xml port 8080 and 8181

Huh... I remember slightly differently... because the 8080 for the old ADSAL couldn't coexist with the RESTCONF, which is why RESTCONF originally went on 8181... once ADSAL was deprecated, *then* RESTCONF shifted to the 8080 port, with 8181 retained for backward compatibility (I *think* I was the o

Re: [controller-dev] etc/jetty.xml port 8080 and 8181

I think it is the other way around: 8181 is the "official" RESTCONF port and 8080 was used before in ADSAL and kept for API backwards compatibility reasons. > On Aug 31, 2016, at 5:57 AM, Edward Warnicke wrote: > > 8080 is the primary port... 8181 was a historical artifact. > > Ed > > On Wed,

Re: [controller-dev] [mdsal-dev] Conceptual Data Tree questions

Thanks, Inline On 08/31/2016 01:09 PM, Sela, Guy wrote: > Hi, > > I've being reading this document: > > https://github.com/opendaylight/mdsal/blob/master/src/site/asciidoc/co > nceptual-data-tree.adoc > > > > I have a few questions. > > > > 1) > > Very general question: > > Is the Conc

Re: [controller-dev] [mdsal-dev] Conceptual Data Tree questions

On 08/31/2016 01:09 PM, Sela, Guy wrote: > Hi, > > I’ve being reading this document: > > https://github.com/opendaylight/mdsal/blob/master/src/site/asciidoc/conceptual-data-tree.adoc > > > > I have a few questions. > > > > 1) > > Very general question: > > Is the Conceptual Data Tree

Re: [controller-dev] etc/jetty.xml port 8080 and 8181

Navin, That's completely cool. 8080 is the primary port for *most* java based web services, so collisions are not uncommon (among any such system) and so folks often change the port of one or the other system. Its part of why its so easy to do :) Ed On Wed, Aug 31, 2016 at 6:05 AM, navin.kukr.

Re: [controller-dev] etc/jetty.xml port 8080 and 8181

Thanks Edward. Unfortunately, I can't change the other service I am running on port 8080. I'll use port 8181 as primary port. Regards, Navin On Aug 31 2016, at 2:59 pm, Edward Warnicke wrote: > 8080 is the primary port... 8181 was a historical artifact. > > > > Ed > > >

Re: [controller-dev] etc/jetty.xml port 8080 and 8181

8080 is the primary port... 8181 was a historical artifact. Ed On Wed, Aug 31, 2016 at 3:18 AM, navin.kukr...@suse.com < navin.kukr...@suse.com> wrote: > Hi, > > Why do we have two ports in etc/jetty.xml file? > > I installed Beryllium on a server but I am running another service on port > 8080

Re: [controller-dev] [mdsal-dev] Serialize/Deserialize DTOs to JSON

Thanks. I dismissed the attempt to work with the Binding Aware objects due to the Proxy complications and some entities that hold transient InstanceIdentifier as fields. Instead of continuing the struggle just for a demo sake, I moved to working with the Binding Independent layer, as Robert sugg

[controller-dev] Conceptual Data Tree questions

Hi, I've being reading this document: https://github.com/opendaylight/mdsal/blob/master/src/site/asciidoc/conceptual-data-tree.adoc I have a few questions. 1) Very general question: Is the Conceptual Data Tree something new that is planned to get into ODL, or is it just an explanation of how the

[controller-dev] etc/jetty.xml port 8080 and 8181

Hi, Why do we have two ports in etc/jetty.xml file? I installed Beryllium on a server but I am running another service on port 8080 and when I load dlux feature, it stays in graceperiod because port 8080 is unavailable. I completely removed 'addConnector' section for port 8080 from etc/je