If the following below are all true:
1) many folks (users/integration tests) are thinking that it is 8181
2) our documented port is 8181 (this may not be true in all the places as
Ed pointed out one place)
3) 8080 is more likely than 8181 to have clashes with user's non-ODL web
services

Then would it be better to keep 8181 as the default enabled port (8080
disabled)? Of course keep the option to enable 8080 or any other port if
needed.

On Wed, Aug 31, 2016 at 6:52 PM, Alexis de Talhouët <adetalho...@inocybe.com
> wrote:

>
>
> On Wednesday, August 31, 2016, Luis Gomez <ece...@gmail.com> 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 was among those person as well.
> Thanks for the clarification and for bringing it up.
>
>
>>
>> BR/Luis
>>
>>
>> On Aug 31, 2016, at 3:50 PM, Luis Gomez <ece...@gmail.com> wrote:
>>
>> Correction, you are right both ports are open :)
>>
>> On Aug 31, 2016, at 3:30 PM, Luis Gomez <ece...@gmail.com> 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 <hagb...@gmail.com> wrote:
>>
>> 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 compatibility it also meant making neutron work with jetty.xml,
>> because neutron northbound wasn't being deprecated :) ).
>>
>> Ed
>>
>> On Wed, Aug 31, 2016 at 12:06 PM, Luis Gomez <ece...@gmail.com> wrote:
>>
>>> 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 <hagb...@gmail.com> wrote:
>>>
>>> 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 one to do all that work... but its a bit murky in my mind).
>>>
>>> Ed
>>>
>>> On Wed, Aug 31, 2016 at 11:39 AM, Luis Gomez <ece...@gmail.com> wrote:
>>>
>>>> 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 <hagb...@gmail.com> wrote:
>>>>
>>>> 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 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/jetty.xml  file and it worked.
>>>>>
>>>>> Is port 8080 just a abckup port for web portal?
>>>>>
>>>>> Regards,
>>>>> Navin
>>>>>
>>>>> _______________________________________________
>>>>> controller-dev mailing list
>>>>> controller-dev@lists.opendaylight.org
>>>>> https://lists.opendaylight.org/mailman/listinfo/controller-dev
>>>>>
>>>>>
>>>> _______________________________________________
>>>> controller-dev mailing list
>>>> controller-dev@lists.opendaylight.org
>>>> https://lists.opendaylight.org/mailman/listinfo/controller-dev
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>>
>>
> _______________________________________________
> controller-dev mailing list
> controller-dev@lists.opendaylight.org
> https://lists.opendaylight.org/mailman/listinfo/controller-dev
>
>
_______________________________________________
controller-dev mailing list
controller-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/controller-dev

Reply via email to