Re: [ODL Discuss] ODL distribution naming

[Luis Gomez]

Makes sense, I will take a look at your patches.

> On May 4, 2023, at 1:18 AM, Ivan Hrasko  wrote:
> 
> Thanks, Luis,
> 
> IMO it looks to be quite a huge change to use opendaylight instead of karaf 
> in test and potentially in builder projects.
> Thus I decided for option #2 for now: 
> https://jira.opendaylight.org/browse/INTDIST-117 
> .
> 
> Best,
> 
> -- 
> Ivan Hraško
> 
> Senior Software Engineer
> 
>  
> PANTHEON .tech
> 
> Mlynské Nivy 56, 821 05 Bratislava
> 
> Slovakia
> 
> Tel / +421 220 665 111
> 
>  
> MAIL / ivan.hra...@pantheon.team
> 
> WEB / https://pantheon.tech 
> 



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#8973): https://lists.opendaylight.org/g/Discuss/message/8973
Mute This Topic: https://lists.opendaylight.org/mt/98664079/21656
Group Owner: discuss+ow...@lists.opendaylight.org
Unsubscribe: 
https://lists.opendaylight.org/g/Discuss/leave/4219721/21656/1056093597/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [ODL Discuss] ODL distribution naming

[Luis Gomez]

Hi Ivan,

Here are my thoughts on this topic:

- I agree opendaylight is better name than karaf for the opendaylight karaf 
distribution artifact.
- So far the karaf artifact = managed distribution generated by autorelease 
project vs the opendaylight artifact = self managed distribution manually 
generated when TPCE released.
- Going forward there is no point to maintain separated self managed 
distribution so this is why we reverted to use karaf artifact.
- The idea of simply renaming the karaf artifact to opendaylight seems straight 
forward except for the fact that the system test framework (JJB + robot) uses 
karaf artifact by default.

So in order to have opendaylight named distribution, I would do one of these:

1) Simply rename the karaf artifact as you say but make sure CSIT is ready for 
the new name. I believe there is some framework to use opendaylight vs karaf in 
CSIT but it needs to be tested:

see (karaf-version: odl) in this example: 
https://git.opendaylight.org/gerrit/gitweb?p=releng/builder.git;a=blob;f=jjb/integration/integration-test-jobs.yaml#l96
 


2) If the above does not work or it is hard to change CSIT to use opendaylight 
name, I would keep karaf artifact for system test and I would generate extra 
opendaylight artifact in AR by simply moving the opendaylight module to the 
managed profile here:

https://git.opendaylight.org/gerrit/gitweb?p=integration/distribution.git;a=blob;f=pom.xml#l59
 


Also in either case, if you want AR to produce the opendaylight distribution, 
you have to use original version schema: 0.X.Y vs X.Y.0 because AR only deals 
with the first AFAIR.

Let me know if you have questions.

BR/Luis




> On May 3, 2023, at 8:16 AM, Ivan Hrasko  wrote:
> 
> Hello,
> 
> Some time ago - ODL distributions were called opendaylight-, now 
> they are karaf-.
> This change is effective since transportpce is no longer a self-managed 
> project.
> For this I have prepared: 
> https://git.opendaylight.org/gerrit/c/integration/distribution/+/105774 
> .
> 
> In order to call them opendaylight again we have to run a build in 
> "opendaylight" project.
> For this I have bumped its version here: 
> https://git.opendaylight.org/gerrit/c/integration/distribution/+/105775 
> .
> 
> In addition, IMO we could potentially remove the "opendaylight" project 
> (there are no more self-managed projects) and rename the "karaf" project to 
> "opendaylight".
> Just to have a distro called opendaylight- again :D.
> 
> What do you think?
> 
> -- 
> Ivan Hraško
> 
> Senior Software Engineer
> 
>  
> PANTHEON .tech
> 
> Mlynské Nivy 56, 821 05 Bratislava
> 
> Slovakia
> 
> Tel / +421 220 665 111
> 
>  
> MAIL / ivan.hra...@pantheon.team
> 
> WEB / https://pantheon.tech 
> 



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#8970): https://lists.opendaylight.org/g/Discuss/message/8970
Mute This Topic: https://lists.opendaylight.org/mt/98664079/21656
Group Owner: discuss+ow...@lists.opendaylight.org
Unsubscribe: 
https://lists.opendaylight.org/g/Discuss/leave/4219721/21656/1056093597/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [ODL Discuss] [opendaylight-dev][release] OpenDaylight - Phosphorus SR3 release status

[Luis Gomez]

OK, here it is :

https://nexus.opendaylight.org/content/repositories/opendaylight.release/org/opendaylight/integration/opendaylight/15.3.0/

Thanks everyone for this new release :)

BR/Luis


> On Jul 1, 2022, at 2:53 PM, Daniel de la Rosa  wrote:
> 
> Hello Anil and all. 
> 
> TransportPCE has released their artifacts 
> https://git.opendaylight.org/gerrit/c/transportpce/+/101159 
> . 
> 
> So Luis, please proceed with the distribution 
> 
> Thanks 
> 
> On Thu, Jun 2, 2022 at 12:47 AM Anil Shashikumar Belur 
> mailto:abe...@linuxfoundation.org>> wrote:
> Hello All,
> 
> OpenDaylight Phosphorus SR3 version bump is complete and the staging 
> repository has been promoted. The 'stable/phosphorus' branch remains unlocked 
> and ready for development.
> 
> Pending activities required to be complete for the release:
> 1. Self-managed projects to release artifacts for Phosphorus SR3.
> 2. Release Distribution once the 1. is complete.
> 3. Release notes - https://git.opendaylight.org/gerrit/c/docs/+/101432 
> .
> 4. Update ODL downloads page [1.].
> 
> Many thanks to everyone who contributed to the Phosphorus SR3 release.
> 
> Regards,
> Anil Belur
> 
> [0.] https://docs.opendaylight.org/en/latest/downloads.html 
> 
> 
> -- 
> Daniel de la Rosa
> ODL Release Manager
> 



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#8910): https://lists.opendaylight.org/g/Discuss/message/8910
Mute This Topic: https://lists.opendaylight.org/mt/91495185/21656
Group Owner: discuss+ow...@lists.opendaylight.org
Unsubscribe: https://lists.opendaylight.org/g/Discuss/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [ODL Discuss] [opendaylight-dev][release] OpenDaylight - Sulfur release status

[Luis Gomez]

Here it is :

https://nexus.opendaylight.org/content/repositories/opendaylight.release/org/opendaylight/integration/opendaylight/16.0.0/
 
<https://nexus.opendaylight.org/content/repositories/opendaylight.release/org/opendaylight/integration/opendaylight/16.0.0/>

Thanks to everyone that contributed to this release :)

BR/Luis

> On May 12, 2022, at 10:56 AM, Daniel de la Rosa  
> wrote:
> 
> Thanks Luis and Anil, So can we get a distribution now ? 
> 
> On Sun, May 8, 2022 at 5:40 PM Luis Gomez  <mailto:ece...@gmail.com>> wrote:
> Also, it looks like distribution jobs missed stable/sulfur update, I will 
> need this merged in order to produce a release:
> 
> https://git.opendaylight.org/gerrit/c/releng/builder/+/101005 
> <https://git.opendaylight.org/gerrit/c/releng/builder/+/101005>
> 
> BR/Luis
> 
>> On May 7, 2022, at 12:43 PM, Daniel de la Rosa > <mailto:ddelarosa0...@gmail.com>> wrote:
>> 
>> Thanks for the update.  If that's the case, @Luis Gomez 
>> <mailto:ece...@gmail.com>  please proceed to release Sulfur distribution at 
>> your earliest convenience 
>> 
>> On Thu, May 5, 2022 at 1:33 AM > <mailto:gilles.thoue...@orange.com>> wrote:
>> Hello Daniel,
>> 
>>  
>> 
>> I believe that we can reasonably consider that TransportPCE will not be able 
>> to integrate the GA distribution of Sulfur. We could not complete the 
>> project migration due to many issues we are facing and that are still under 
>> investigation.
>> 
>> The bottom line is that a rather important number of our functional tests 
>> are still failing, and so it is not possible to release with so many 
>> functional regressions.
>> 
>>  
>> 
>> On the other hand, if TransportPCE cannot integrate the GA, will it still be 
>> possible to integrate Sulfur SR1 or SR2 when problems have been resolved?
>> 
>>  
>> 
>> If I try to summarize the situation and issues that are still open:
>> 
>> Openroadm models compilation (assembling issue - see my email of 2022-04-27)
>> Link augmentation writing in openroadm-topology (see my email of 2022-05-02; 
>> under investigation)
>> Feature odl-transportpce-swagger no longer effective (would have an issue 
>> with our GNPy yang models?)
>> Run time issue to run some Junit tests (see 
>> networkmodel/src/test/java/org/opendaylight/transportpce/networkmodel/service/FrequenciesServiceTest.java,
>>  
>> pce/src/test/java/org/opendaylight/transportpce/pce/gnpy/GnpyUtilitiesImplTest.java
>>  in change https://git.opendaylight.org/gerrit/c/transportpce/+/100646 
>> <https://git.opendaylight.org/gerrit/c/transportpce/+/100646>)
>> Possible other failures on functional tests not investigated yet due to the 
>> blocking issue mentioned above…
>>  
>> 
>> Best regards,
>> 
>> Gilles
>> 
>>  
>> 
>>  
>> 
>>  
>> 
>> Orange Restricted
>> De : rele...@lists.opendaylight.org <mailto:rele...@lists.opendaylight.org> 
>> mailto:rele...@lists.opendaylight.org>> De 
>> la part de Guillaume Lambert via lists.opendaylight.org 
>> <http://lists.opendaylight.org/>
>> Envoyé : mercredi 4 mai 2022 17:14
>> À : Daniel de la Rosa > <mailto:ddelarosa0...@gmail.com>>; Anil Shashikumar Belur 
>> mailto:abe...@linuxfoundation.org>>; THOUENON 
>> Gilles INNOV/NET > <mailto:gilles.thoue...@orange.com>>
>> Cc : 'integration-...@lists.opendaylight.org 
>> <mailto:integration-...@lists.opendaylight.org>' 
>> (integration-...@lists.opendaylight.org 
>> <mailto:integration-...@lists.opendaylight.org>) 
>> (integration-...@lists.opendaylight.org 
>> <mailto:integration-...@lists.opendaylight.org>) 
>> > <mailto:integration-...@lists.opendaylight.org>>; Release 
>> mailto:rele...@lists.opendaylight.org>>; 
>> OpenDaylight Discuss > <mailto:discuss@lists.opendaylight.org>>; TSC > <mailto:t...@lists.opendaylight.org>>; Casey Cain > <mailto:cc...@linuxfoundation.org>>; Andrew Grimberg 
>> mailto:agrimb...@linuxfoundation.org>>; Luis 
>> Gomez mailto:ece...@gmail.com>>
>> Objet : Re: [opendaylight-dev][release] OpenDaylight - Sulfur release status
>> 
>>  
>> 
>> Hi Daniel
>> 
>>  
>> 
>> I let Gilles answer the question since he is in charge of this TPCE release.
>> 
>> We can put that at the TSC agenda tomorrow.
>> 
>>  
>> 
>> BR
>> 
>> Guillaume
>

Re: [ODL Discuss] [opendaylight-dev][release] OpenDaylight - Sulfur release status

[Luis Gomez]

Also, it looks like distribution jobs missed stable/sulfur update, I will need 
this merged in order to produce a release:

https://git.opendaylight.org/gerrit/c/releng/builder/+/101005 
<https://git.opendaylight.org/gerrit/c/releng/builder/+/101005>

BR/Luis

> On May 7, 2022, at 12:43 PM, Daniel de la Rosa  
> wrote:
> 
> Thanks for the update.  If that's the case, @Luis Gomez 
> <mailto:ece...@gmail.com>  please proceed to release Sulfur distribution at 
> your earliest convenience 
> 
> On Thu, May 5, 2022 at 1:33 AM  <mailto:gilles.thoue...@orange.com>> wrote:
> Hello Daniel,
> 
>  
> 
> I believe that we can reasonably consider that TransportPCE will not be able 
> to integrate the GA distribution of Sulfur. We could not complete the project 
> migration due to many issues we are facing and that are still under 
> investigation.
> 
> The bottom line is that a rather important number of our functional tests are 
> still failing, and so it is not possible to release with so many functional 
> regressions.
> 
>  
> 
> On the other hand, if TransportPCE cannot integrate the GA, will it still be 
> possible to integrate Sulfur SR1 or SR2 when problems have been resolved?
> 
>  
> 
> If I try to summarize the situation and issues that are still open:
> 
> Openroadm models compilation (assembling issue - see my email of 2022-04-27)
> Link augmentation writing in openroadm-topology (see my email of 2022-05-02; 
> under investigation)
> Feature odl-transportpce-swagger no longer effective (would have an issue 
> with our GNPy yang models?)
> Run time issue to run some Junit tests (see 
> networkmodel/src/test/java/org/opendaylight/transportpce/networkmodel/service/FrequenciesServiceTest.java,
>  
> pce/src/test/java/org/opendaylight/transportpce/pce/gnpy/GnpyUtilitiesImplTest.java
>  in change https://git.opendaylight.org/gerrit/c/transportpce/+/100646 
> <https://git.opendaylight.org/gerrit/c/transportpce/+/100646>)
> Possible other failures on functional tests not investigated yet due to the 
> blocking issue mentioned above…
>  
> 
> Best regards,
> 
> Gilles
> 
>  
> 
>  
> 
>  
> 
> Orange Restricted
> De : rele...@lists.opendaylight.org <mailto:rele...@lists.opendaylight.org> 
> mailto:rele...@lists.opendaylight.org>> De 
> la part de Guillaume Lambert via lists.opendaylight.org 
> <http://lists.opendaylight.org/>
> Envoyé : mercredi 4 mai 2022 17:14
> À : Daniel de la Rosa  <mailto:ddelarosa0...@gmail.com>>; Anil Shashikumar Belur 
> mailto:abe...@linuxfoundation.org>>; THOUENON 
> Gilles INNOV/NET  <mailto:gilles.thoue...@orange.com>>
> Cc : 'integration-...@lists.opendaylight.org 
> <mailto:integration-...@lists.opendaylight.org>' 
> (integration-...@lists.opendaylight.org 
> <mailto:integration-...@lists.opendaylight.org>) 
> (integration-...@lists.opendaylight.org 
> <mailto:integration-...@lists.opendaylight.org>) 
>  <mailto:integration-...@lists.opendaylight.org>>; Release 
> mailto:rele...@lists.opendaylight.org>>; 
> OpenDaylight Discuss  <mailto:discuss@lists.opendaylight.org>>; TSC  <mailto:t...@lists.opendaylight.org>>; Casey Cain  <mailto:cc...@linuxfoundation.org>>; Andrew Grimberg 
> mailto:agrimb...@linuxfoundation.org>>; Luis 
> Gomez mailto:ece...@gmail.com>>
> Objet : Re: [opendaylight-dev][release] OpenDaylight - Sulfur release status
> 
>  
> 
> Hi Daniel
> 
>  
> 
> I let Gilles answer the question since he is in charge of this TPCE release.
> 
> We can put that at the TSC agenda tomorrow.
> 
>  
> 
> BR
> 
> Guillaume
> 
>  
> 
> De : Daniel de la Rosa  <mailto:ddelarosa0...@gmail.com>> 
> Envoyé : mercredi 4 mai 2022 16:41
> À : Anil Shashikumar Belur  <mailto:abe...@linuxfoundation.org>>; LAMBERT Guillaume INNOV/NET 
> mailto:guillaume.lamb...@orange.com>>
> Cc : 'integration-...@lists.opendaylight.org 
> <mailto:integration-...@lists.opendaylight.org>' 
> (integration-...@lists.opendaylight.org 
> <mailto:integration-...@lists.opendaylight.org>) 
> (integration-...@lists.opendaylight.org 
> <mailto:integration-...@lists.opendaylight.org>) 
>  <mailto:integration-...@lists.opendaylight.org>>; Release 
> mailto:rele...@lists.opendaylight.org>>; 
> OpenDaylight Discuss  <mailto:discuss@lists.opendaylight.org>>; TSC  <mailto:t...@lists.opendaylight.org>>; Casey Cain  <mailto:cc...@linuxfoundation.org>>; Andrew Grimberg 
> mailto:agrimb...@linuxfoundation.org>>; Luis 
> Gomez mailto:ece...@gmail.

Re: [ODL Discuss] [opendaylight-dev][release] OpenDaylight - Sulfur release status

[Luis Gomez]

TPCE can integrate in the ODL distribution any time they wish to do so.

I am curious: are all these issues due to changes in TPCE, changes in Kernel or 
both?

BR/Luis

> On May 7, 2022, at 12:43 PM, Daniel de la Rosa  
> wrote:
> 
> Thanks for the update.  If that's the case, @Luis Gomez 
> <mailto:ece...@gmail.com>  please proceed to release Sulfur distribution at 
> your earliest convenience 
> 
> On Thu, May 5, 2022 at 1:33 AM  <mailto:gilles.thoue...@orange.com>> wrote:
> Hello Daniel,
> 
>  
> 
> I believe that we can reasonably consider that TransportPCE will not be able 
> to integrate the GA distribution of Sulfur. We could not complete the project 
> migration due to many issues we are facing and that are still under 
> investigation.
> 
> The bottom line is that a rather important number of our functional tests are 
> still failing, and so it is not possible to release with so many functional 
> regressions.
> 
>  
> 
> On the other hand, if TransportPCE cannot integrate the GA, will it still be 
> possible to integrate Sulfur SR1 or SR2 when problems have been resolved?
> 
>  
> 
> If I try to summarize the situation and issues that are still open:
> 
> Openroadm models compilation (assembling issue - see my email of 2022-04-27)
> Link augmentation writing in openroadm-topology (see my email of 2022-05-02; 
> under investigation)
> Feature odl-transportpce-swagger no longer effective (would have an issue 
> with our GNPy yang models?)
> Run time issue to run some Junit tests (see 
> networkmodel/src/test/java/org/opendaylight/transportpce/networkmodel/service/FrequenciesServiceTest.java,
>  
> pce/src/test/java/org/opendaylight/transportpce/pce/gnpy/GnpyUtilitiesImplTest.java
>  in change https://git.opendaylight.org/gerrit/c/transportpce/+/100646 
> <https://git.opendaylight.org/gerrit/c/transportpce/+/100646>)
> Possible other failures on functional tests not investigated yet due to the 
> blocking issue mentioned above…
>  
> 
> Best regards,
> 
> Gilles
> 
>  
> 
>  
> 
>  
> 
> Orange Restricted
> De : rele...@lists.opendaylight.org <mailto:rele...@lists.opendaylight.org> 
> mailto:rele...@lists.opendaylight.org>> De 
> la part de Guillaume Lambert via lists.opendaylight.org 
> <http://lists.opendaylight.org/>
> Envoyé : mercredi 4 mai 2022 17:14
> À : Daniel de la Rosa  <mailto:ddelarosa0...@gmail.com>>; Anil Shashikumar Belur 
> mailto:abe...@linuxfoundation.org>>; THOUENON 
> Gilles INNOV/NET  <mailto:gilles.thoue...@orange.com>>
> Cc : 'integration-...@lists.opendaylight.org 
> <mailto:integration-...@lists.opendaylight.org>' 
> (integration-...@lists.opendaylight.org 
> <mailto:integration-...@lists.opendaylight.org>) 
> (integration-...@lists.opendaylight.org 
> <mailto:integration-...@lists.opendaylight.org>) 
>  <mailto:integration-...@lists.opendaylight.org>>; Release 
> mailto:rele...@lists.opendaylight.org>>; 
> OpenDaylight Discuss  <mailto:discuss@lists.opendaylight.org>>; TSC  <mailto:t...@lists.opendaylight.org>>; Casey Cain  <mailto:cc...@linuxfoundation.org>>; Andrew Grimberg 
> mailto:agrimb...@linuxfoundation.org>>; Luis 
> Gomez mailto:ece...@gmail.com>>
> Objet : Re: [opendaylight-dev][release] OpenDaylight - Sulfur release status
> 
>  
> 
> Hi Daniel
> 
>  
> 
> I let Gilles answer the question since he is in charge of this TPCE release.
> 
> We can put that at the TSC agenda tomorrow.
> 
>  
> 
> BR
> 
> Guillaume
> 
>  
> 
> De : Daniel de la Rosa  <mailto:ddelarosa0...@gmail.com>> 
> Envoyé : mercredi 4 mai 2022 16:41
> À : Anil Shashikumar Belur  <mailto:abe...@linuxfoundation.org>>; LAMBERT Guillaume INNOV/NET 
> mailto:guillaume.lamb...@orange.com>>
> Cc : 'integration-...@lists.opendaylight.org 
> <mailto:integration-...@lists.opendaylight.org>' 
> (integration-...@lists.opendaylight.org 
> <mailto:integration-...@lists.opendaylight.org>) 
> (integration-...@lists.opendaylight.org 
> <mailto:integration-...@lists.opendaylight.org>) 
>  <mailto:integration-...@lists.opendaylight.org>>; Release 
> mailto:rele...@lists.opendaylight.org>>; 
> OpenDaylight Discuss  <mailto:discuss@lists.opendaylight.org>>; TSC  <mailto:t...@lists.opendaylight.org>>; Casey Cain  <mailto:cc...@linuxfoundation.org>>; Andrew Grimberg 
> mailto:agrimb...@linuxfoundation.org>>; Luis 
> Gomez mailto:ece...@gmail.com>>
> Objet : Re: [opendaylight-dev][release] OpenDaylight - Sulfur release status
> 
> 

Re: [ODL Discuss] [integration-dev] [opendaylight-dev][release] OpenDaylight - Silicon SR3 release status

[Luis Gomez]

Thanks everyone, here is the distribution release: 
https://nexus.opendaylight.org/content/repositories/opendaylight.release/org/opendaylight/integration/opendaylight/14.3.0/
 
<https://nexus.opendaylight.org/content/repositories/opendaylight.release/org/opendaylight/integration/opendaylight/14.3.0/>

BR/Luis

> On Nov 9, 2021, at 9:44 PM, Daniel de la Rosa  wrote:
> 
> Thanks Luis, and in that case, please proceed to release Silicon SR3 at your 
> earliest convenience
> 
> Thank you all
> 
> On Tue, Nov 9, 2021 at 7:12 PM Luis Gomez  <mailto:ece...@gmail.com>> wrote:
> The release actually happened before the other projects because TPCE does not 
> depend anymore on MSI projects. For future, I would still recommend TPCE to 
> wait for the TSC release approval, otherwise there is risk of having to 
> repeat the release if for a example a bug in the kernel is found.
> 
> BR/Luis
>  
> 
>> On Nov 9, 2021, at 5:47 PM, Daniel de la Rosa > <mailto:ddelarosa0...@gmail.com>> wrote:
>> 
>> HI Gilles, 
>> 
>> This is from the other email thread The logs you show below are for a 
>> normal merge job that does not publish release artifacts but SNAPSHOT. So in 
>> short, you have bumped TPCE to use Silicon SR3 but the actual TPCE Silicon 
>> SR3 release does not happen until 1) Silicon SR3 release artifacts for all 
>> managed projects are published in nexus and 2) you execute this release 
>> merge job: 
>> https://jenkins.opendaylight.org/releng/view/transportpce/job/transportpce-release-merge
>>  
>> <https://jenkins.opendaylight.org/releng/view/transportpce/job/transportpce-release-merge>
>> 
>> thanks
>> 
>> On Tue, Nov 9, 2021 at 7:09 AM > <mailto:gilles.thoue...@orange.com>> wrote:
>> Hi Daniel,
>> 
>>  
>> 
>> Shweta released TransportPCE SR3 last week.
>> 
>> Please see the following log : 
>> https://s3-logs.opendaylight.org/logs/releng/vex-yul-odl-jenkins-1/transportpce-release-merge/23/
>>  
>> <https://s3-logs.opendaylight.org/logs/releng/vex-yul-odl-jenkins-1/transportpce-release-merge/23/>
>> At first sight it seems OK.
>> 
>> Please tell us if there is any other action required from our side (still 
>> the release note to update)
>> 
>>  
>> 
>> Gilles
>> 
>>  
>> 
>>  
>> 
>> De : integration-...@lists.opendaylight.org 
>> <mailto:integration-...@lists.opendaylight.org> 
>> [mailto:integration-...@lists.opendaylight.org 
>> <mailto:integration-...@lists.opendaylight.org>] De la part de Daniel de la 
>> Rosa
>> Envoyé : mardi 9 novembre 2021 15:53
>> À : Anil Belur > <mailto:abe...@linuxfoundation.org>>; LAMBERT Guillaume INNOV/NET 
>> mailto:guillaume.lamb...@orange.com>>; 
>> VACHHANI, SHWETA (sv1...@att.com <mailto:sv1...@att.com>) > <mailto:sv1...@att.com>>
>> Cc : 'integration-...@lists.opendaylight.org 
>> <mailto:integration-...@lists.opendaylight.org>' 
>> (integration-...@lists.opendaylight.org 
>> <mailto:integration-...@lists.opendaylight.org>) 
>> (integration-...@lists.opendaylight.org 
>> <mailto:integration-...@lists.opendaylight.org>) 
>> > <mailto:integration-...@lists.opendaylight.org>>; Andrew Grimberg 
>> mailto:agrimb...@linuxfoundation.org>>; 
>> Casey Cain mailto:cc...@linuxfoundation.org>>; 
>> OpenDaylight Discuss > <mailto:discuss@lists.opendaylight.org>>; Release 
>> mailto:rele...@lists.opendaylight.org>>; 
>> navid.ghazisa...@verizon.com <mailto:navid.ghazisa...@verizon.com>
>> Objet : Re: [integration-dev] [opendaylight-dev][release] OpenDaylight - 
>> Silicon SR3 release status
>> 
>>  
>> 
>> Thank you for the update. Guillaume and/or Shweta, please proceed at your 
>> earliest convenience
>> 
>>  
>> 
>> On Sun, Nov 7, 2021 at 4:09 PM Anil Belur > <mailto:abe...@linuxfoundation.org>> wrote:
>> 
>> Hello All,
>> 
>> OpenDaylight Silicon SR3 version bump is complete and the staging repository 
>> is being promoted. The 'stable/silicon' branch is unlocked.
>> 
>> Pending activities required to be complete for the release:
>> 1. Self-managed projects to release artifacts for Silicon SR3.
>> 2. Release Distribution once step 1. is complete.
>> 3. Release notes merge CR. 
>> https://git.opendaylight.org/gerrit/c/docs/+/98347 
>> <https://git.opendaylight.org/gerrit/c/docs/+/98347>
>> 4. Update ODL downloads page 

Re: [ODL Discuss] [integration-dev] [opendaylight-dev][release] OpenDaylight - Silicon SR3 release status

[Luis Gomez]

The release actually happened before the other projects because TPCE does not 
depend anymore on MSI projects. For future, I would still recommend TPCE to 
wait for the TSC release approval, otherwise there is risk of having to repeat 
the release if for a example a bug in the kernel is found.

BR/Luis
 

> On Nov 9, 2021, at 5:47 PM, Daniel de la Rosa  wrote:
> 
> HI Gilles, 
> 
> This is from the other email thread The logs you show below are for a 
> normal merge job that does not publish release artifacts but SNAPSHOT. So in 
> short, you have bumped TPCE to use Silicon SR3 but the actual TPCE Silicon 
> SR3 release does not happen until 1) Silicon SR3 release artifacts for all 
> managed projects are published in nexus and 2) you execute this release merge 
> job: 
> https://jenkins.opendaylight.org/releng/view/transportpce/job/transportpce-release-merge
>  
> 
> 
> thanks
> 
> On Tue, Nov 9, 2021 at 7:09 AM  > wrote:
> Hi Daniel,
> 
>  
> 
> Shweta released TransportPCE SR3 last week.
> 
> Please see the following log : 
> https://s3-logs.opendaylight.org/logs/releng/vex-yul-odl-jenkins-1/transportpce-release-merge/23/
>  
> 
> At first sight it seems OK.
> 
> Please tell us if there is any other action required from our side (still the 
> release note to update)
> 
>  
> 
> Gilles
> 
>  
> 
>  
> 
> De : integration-...@lists.opendaylight.org 
>  
> [mailto:integration-...@lists.opendaylight.org 
> ] De la part de Daniel de la 
> Rosa
> Envoyé : mardi 9 novembre 2021 15:53
> À : Anil Belur  >; LAMBERT Guillaume INNOV/NET 
> mailto:guillaume.lamb...@orange.com>>; 
> VACHHANI, SHWETA (sv1...@att.com )  >
> Cc : 'integration-...@lists.opendaylight.org 
> ' 
> (integration-...@lists.opendaylight.org 
> ) 
> (integration-...@lists.opendaylight.org 
> ) 
>  >; Andrew Grimberg 
> mailto:agrimb...@linuxfoundation.org>>; Casey 
> Cain mailto:cc...@linuxfoundation.org>>; 
> OpenDaylight Discuss  >; Release 
> mailto:rele...@lists.opendaylight.org>>; 
> navid.ghazisa...@verizon.com 
> Objet : Re: [integration-dev] [opendaylight-dev][release] OpenDaylight - 
> Silicon SR3 release status
> 
>  
> 
> Thank you for the update. Guillaume and/or Shweta, please proceed at your 
> earliest convenience
> 
>  
> 
> On Sun, Nov 7, 2021 at 4:09 PM Anil Belur  > wrote:
> 
> Hello All,
> 
> OpenDaylight Silicon SR3 version bump is complete and the staging repository 
> is being promoted. The 'stable/silicon' branch is unlocked.
> 
> Pending activities required to be complete for the release:
> 1. Self-managed projects to release artifacts for Silicon SR3.
> 2. Release Distribution once step 1. is complete.
> 3. Release notes merge CR. https://git.opendaylight.org/gerrit/c/docs/+/98347 
> 
> 4. Update ODL downloads page [1.].
> 
> Thanks to everyone who contributed to the Silicon SR3 release.
> 
> Regards,
> Anil Belur
> 
> [0.] https://docs.opendaylight.org/en/latest/downloads.html 
> 
> [1.] https://wiki.opendaylight.org/display/ODL/Silicon+SR3+Release+Approval 
> 
> --
> 
> Daniel de la Rosa
> 
> ODL Release Manager
> 
>  
> 
> _
> 
> Ce message et ses pieces jointes peuvent contenir des informations 
> confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu 
> ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
> electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou 
> falsifie. Merci.
> 
> This message and its attachments may contain confidential or privileged 
> information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete 
> this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been 
> modified, changed or falsified.
> Thank you.
> 



-=-=-=-=-=-=

Re: [ODL Discuss] [opendaylight-dev][release] OpenDaylight - Phosphorus release status

[Luis Gomez]

FYI Phosphorus distribution has been released:

https://nexus.opendaylight.org/content/repositories/opendaylight.release/org/opendaylight/integration/opendaylight/15.0.0/
 


BR/Luis

> On Oct 13, 2021, at 12:32 AM, Guillaume Lambert via lists.opendaylight.org 
>  wrote:
> 
> Hello
> 
> You're welcome Daniel.
> yes it was still blocking last monday but as stated by Anil and Gilles, it 
> did pass yesterday.
> Also integration/distribution was updated accordingly and merged by Luis.
> So apart documentation aspects, I think we should be done now.
> 
> Hope this helps
> BR
> Guillaume
> 
> De : Daniel de la Rosa [ddelarosa0...@gmail.com 
> ]
> Envoyé : lundi 11 octobre 2021 20:55
> À : LAMBERT Guillaume INNOV/NET
> Cc : Andrew Grimberg; Anil Belur; Casey Cain; OpenDaylight Discuss; Release; 
> THOUENON Gilles INNOV/NET; TSC; integration-...@lists.opendaylight.org 
> ; navid.ghazisa...@verizon.com 
> 
> Objet : Re: [opendaylight-dev][release] OpenDaylight - Phosphorus release 
> status
> 
> Thanks Guillaume. So I’m assuming the jenkine are still blocking you ? 
> 
> On Thu, Oct 7, 2021 at 5:47 AM  > wrote:
> Hello
> 
> I confirm  we are in the process of releasing with Gilles at the wheel.
> Though, jenkins outtage are braking us.
> 
> After a succesfull build, the stage release job failed this morning with a 
> weird message
> ERROR: I/O error: NSPR connection reset
> https://jenkins.opendaylight.org/releng/job/transportpce-maven-stage-phosphorus/1/console
>  
> 
> 
> BR
> Guillaume
> 
> De : Daniel de la Rosa [ddelarosa0...@gmail.com 
> ]
> Envoyé : jeudi 7 octobre 2021 00:08
> À : Anil Belur; LAMBERT Guillaume INNOV/NET
> Cc : Andrew Grimberg; Casey Cain; OpenDaylight Discuss; Release; TSC; 
> integration-...@lists.opendaylight.org 
> ; navid.ghazisa...@verizon.com 
> 
> Objet : Re: [opendaylight-dev][release] OpenDaylight - Phosphorus release 
> status
> 
> Thanks for the update. I believe TransportPCE is in the process of releasing 
> in phosphorus  but I’m going to let Guillaume confirm this. 
> 
> On Mon, Oct 4, 2021 at 4:40 PM Anil Belur  > wrote:
> Hello All,
> 
> OpenDaylight Phosphorus version bump is complete and the staging repository 
> has been promoted. The 'stable/phosphorus' branch is unlocked and ready for 
> development.
> 
> Pending activities required to be complete for the release:
> 1. Self-managed projects to release artifacts for Phosphorus.
> 2. Release Distribution once the 1. is complete.
> 3. Release notes - $Project PTL's to submit release notes to Opendaylight 
> docs.
> 4. Update ODL downloads page [1.].
> 
> Many thanks to everyone who contributed to the Phosphorus release.
> 
> Regards,
> Anil Belur
> 
> [0.] https://docs.opendaylight.org/en/latest/downloads.html 
> 
> -- 
> Daniel de la Rosa
> ODL Release Manager
> 
> _
> 
> Ce message et ses pieces jointes peuvent contenir des informations 
> confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu 
> ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
> electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou 
> falsifie. Merci.
> 
> This message and its attachments may contain confidential or privileged 
> information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete 
> this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been 
> modified, changed or falsified.
> Thank you.
> -- 
> Daniel de la Rosa
> ODL Release Manager
> 
> _
> 
> Ce message et ses pieces jointes peuvent contenir des informations 
> confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu 
> ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
> electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si 

Re: [ODL Discuss] LFx OpenDaylight Chat beta

[Luis Gomez]

FYI I installed the recommended app and did not work either. We probably need 
Casey to show how this works tomorrow.

> On Sep 15, 2021, at 10:55 AM, manoj chokka  wrote:
> 
> Hi All, 
> 
> Same for me too. Failed to join room No known server.
> 
> BR
> Manoj
> 
> On Tue, Sep 14, 2021 at 3:37 PM Guillaume Lambert via lists.opendaylight.org 
>  
>  > wrote:
> Hi all
> 
> I did try joining from my web browser with app.element.io 
> 
> but I got the error message " Failed to join room - No known servers"
> Is anyone experimenting the same issue ?
> 
> BR
> Guillaume
> 
> De : Discuss@lists.opendaylight.org  
> [Discuss@lists.opendaylight.org ] de 
> la part de Casey Cain [cc...@linuxfoundation.org 
> ]
> Envoyé : vendredi 27 août 2021 22:04
> À : discuss; TSC
> Objet : [ODL Discuss] LFx OpenDaylight Chat beta
> 
> Hello everyone,
> 
> I'm exited to announce that the OpenDaylight community now has access to the 
> LFx Chat service that is currently in beta.  This service is still under 
> active development and is provided without support until Q1 2022.
> 
> For those of you who wish to participate, please join the OpenDaylight 
> channel here:
> https://matrix.to/#/!pTWzAoMhafnfLCtFPN:chat.lfx.linuxfoundation.org?via=chat.lfx.linuxfoundation.org
>  
> 
> 
> Questions and feedback can be sent to me.
> 
> Best,
> Casey Cain
> Senior Technical Community Architect
> Linux Foundation
> _
> WeChat: okaru6
> WhatsApp: +1.503.779.4519
> Book a Meeting w/ Casey 
> 
> Sent via Superhuman 
> _
> 
> Ce message et ses pieces jointes peuvent contenir des informations 
> confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu 
> ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
> electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou 
> falsifie. Merci.
> 
> This message and its attachments may contain confidential or privileged 
> information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete 
> this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been 
> modified, changed or falsified.
> Thank you.
> 
> 
> 
> 
> 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#8781): https://lists.opendaylight.org/g/Discuss/message/8781
Mute This Topic: https://lists.opendaylight.org/mt/85195013/21656
Group Owner: discuss+ow...@lists.opendaylight.org
Unsubscribe: https://lists.opendaylight.org/g/Discuss/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [ODL Discuss] how to configure switch-configure-timeout #help #opendaylight

[Luis Gomez]

OpenFlow topology only shows when switches are connected to the controller, 
that is expected behavior is this is what your question is about.

BR/Luis


> On Sep 12, 2021, at 8:17 PM, hj2913 via lists.opendaylight.org 
>  wrote:
> 
> hi, i'm one of the student using opendaylight controller.
> 
> i'm doing some project. and simulation stop and resume often.
> but when the simulation stops, i can't see the topology on web-page(dlux 
> topology) and can't get topology information using REST API.
> 
> in my opinion, this is because when i stop the simulation there is no packet 
> exchange so controller disconnect connection.
> 
> so i tried to change switch-idle-timeout option in xml files. default 
> 15seconds to 0( permanent). but it doesn't work.
> 
> these are what i have done. can anybody help me ? 
> 
> 1.modify value of the  tag in files
> 
> i explore the folder and changed the value of the  tag.
> these are file list and example code.
> {folder}/etc/opendaylight/karaf/42-openflowplugin-Li.xml 
> {folder}/system/org/opendaylight/openflowplugin/openflowplugin-controller-config-Li/HE.xml
> 
> 
> 
> 2. added  tag in the files
> 
> solution 1 doesn't seem to work. so i added  tag and 
> value into the file which is related with switch-connection.
> these are file list and example code.
> {folder}/etc/opendaylight/datastor/initial/defalut-openflow-connection-config.xml
> {folder}/etc/opendaylight/datastor/initial/legacy-openflow-connection-config.xml
> {folder}/system/org/opendaylight/openflowjava-openflowjava-blueprint-config/0.9.4-Carbon/openflowjava-blueprint-config-0.9.4-Carbon-config.xml
> {folder}/system/org/opendaylight/openflowjava-openflowjava-blueprint-config/0.9.4-Carbon/openflowjava-blueprint-config-0.9.4-Carbon-legacyconfig.xml
> 
> 
> 
> but i think these things doesn't affect to the connection. 
> is there anyone who can help me ? 
> 
> 
> 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#8779): https://lists.opendaylight.org/g/Discuss/message/8779
Mute This Topic: https://lists.opendaylight.org/mt/85567192/21656
Mute 
#opendaylight:https://lists.opendaylight.org/g/Discuss/mutehashtag/opendaylight
Mute #help:https://lists.opendaylight.org/g/Discuss/mutehashtag/help
Group Owner: discuss+ow...@lists.opendaylight.org
Unsubscribe: https://lists.opendaylight.org/g/Discuss/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [ODL Discuss] L2switch rule for sending everything to the controller

[Luis Gomez]

I am not sure you checked this already, but l2switch have config options to 
disable/enable all flow types in the application:

https://docs.opendaylight.org/en/stable-oxygen/user-guide/l2switch-user-guide.html
 


BR/Luis

> On Jul 14, 2021, at 3:05 AM, sudhanshu naithani 
>  wrote:
> 
> Hello All,
> 
> I am trying to change a dropAll rule in l2switch and would like to change it 
> so everything goes to the controller. For it I am trying to build 
> EthernetMatchBuilder as following:-
> 
> EthernetMatchBuilder ethernetMatchBuilder = new 
> EthernetMatchBuilder().setEthernetType(new EthernetTypeBuilder().setType(new 
> EtherType(Long.valueOf(KnownEtherType.X.getIntValue(.build());
> 
> Here I would like to know what should be in place of X for sending 
> anything to the controller? Like for sending  ARP to the controller we 
> replace X with Arp.
> 
> Could anyone please help me with this?
> 
> Thank you.
> 
> Warm Regards-
> Sudhanshu Naithani
>
> 
> 
> 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#8768): https://lists.opendaylight.org/g/Discuss/message/8768
Mute This Topic: https://lists.opendaylight.org/mt/84198147/21656
Group Owner: discuss+ow...@lists.opendaylight.org
Unsubscribe: https://lists.opendaylight.org/g/Discuss/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [ODL Discuss] Regarding forwarding decisions in L2switch in Sodium-SR4

[Luis Gomez]

Hi Sudhanshu,

Unfortunately this project is not supported so it is hard to reach the people 
that originally wrote this application. AFAIR l2switch uses very simple 
approach of sending incoming packets to all available ports (except the ingress 
port) and then it uses the loop remover to block ports in the topology and 
therefore avoid packet loops, similar to the Spanning Tree protocol.

BR/Luis

> On Jul 8, 2021, at 7:15 AM, sudhanshu naithani 
>  wrote:
> 
> Hi Everyone,
> 
> I am trying to figure out how forwarding decisions are being made in l2switch 
> for Sodium-SR4 at https://github.com/opendaylight/l2switch 
> . I can see NetworkGraphService in 
> the loop remover section but I'm not entirely sure.
> 
> Could anyone please help me to understand it?
> 
> Thank you.
> 
> Warm regards
> Sudhanshu Naithani
> 
> 
> 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#8767): https://lists.opendaylight.org/g/Discuss/message/8767
Mute This Topic: https://lists.opendaylight.org/mt/84068517/21656
Group Owner: discuss+ow...@lists.opendaylight.org
Unsubscribe: https://lists.opendaylight.org/g/Discuss/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [ODL Discuss] [integration-dev] [opendaylight-dev][release] OpenDaylight - Silicon SR1 release status

[Luis Gomez]

OK, here is the distribution release:

https://nexus.opendaylight.org/content/repositories/opendaylight.release/org/opendaylight/integration/opendaylight/14.1.0/
 


We can proceed with the post-release actions.

BR/Luis


> On Jun 6, 2021, at 10:22 PM, Daniel de la Rosa  
> wrote:
> 
> Thank you Gilles. Luis, I think we can proceed with the official distribution 
> of Silicon SR1
> 
> 
> On Fri, Jun 4, 2021 at 2:54 AM  > wrote:
> Hello,
> 
>  
> 
> I’ve released the TransportPCE artifacts in version 3.1.0 for Silicon SR1 
> (see 
> https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/transportpce-release-merge/18/
>  
> ).
> 
> Everything looks ok. However, let me know if you see anything wrong.
> 
>  
> 
> Best Regards,
> 
>  
> 
> Gilles Thouenon
> 
>  
> 
> De : integration-...@lists.opendaylight.org 
>  
> [mailto:integration-...@lists.opendaylight.org 
> ] De la part de Anil Belur
> Envoyé : jeudi 3 juin 2021 09:11
> À : Release  >; 
> 'integration-...@lists.opendaylight.org 
> ' 
> (integration-...@lists.opendaylight.org 
> ) 
> (integration-...@lists.opendaylight.org 
> ) 
>  >; OpenDaylight Discuss 
> mailto:discuss@lists.opendaylight.org>>; TSC 
> mailto:t...@lists.opendaylight.org>>
> Cc : Casey Cain  >; Daniel de la Rosa 
> mailto:ddelarosa0...@gmail.com>>; Brandon Wick 
> mailto:bw...@linuxfoundation.org>>; Andrew 
> Grimberg  >
> Objet : [integration-dev] [opendaylight-dev][release] OpenDaylight - Silicon 
> SR1 release status
> 
>  
> 
> Hello All,
> 
> OpenDaylight Silicon SR1 version bump is complete and the staging repository 
> is being promoted. The 'stable/silicon' branch is unlocked and ready for 
> development.
> 
> Pending activities required to be complete for the release:
> 1. Self-managed projects to release artifacts for Silicon SR1.
> 2. Release Distribution once step 1. is complete.
> 3. Release notes merge CR: https://git.opendaylight.org/gerrit/c/docs/+/96421 
> 
> 4. Update ODL downloads page [1.].
> 
> Thanks to everyone who contributed to the Silicon SR1 release.
> 
> Regards,
> Anil Belur
> 
> [0.] https://docs.opendaylight.org/en/latest/downloads.html 
> 
> [1.] https://wiki.opendaylight.org/display/ODL/Silicon+SR1+Release+Approval 
> 
> _
> 
> Ce message et ses pieces jointes peuvent contenir des informations 
> confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu 
> ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
> electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou 
> falsifie. Merci.
> 
> This message and its attachments may contain confidential or privileged 
> information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete 
> this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been 
> modified, changed or falsified.
> Thank you.


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#8748): https://lists.opendaylight.org/g/Discuss/message/8748
Mute This Topic: https://lists.opendaylight.org/mt/83305017/21656
Group Owner: discuss+ow...@lists.opendaylight.org
Unsubscribe: https://lists.opendaylight.org/g/Discuss/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [ODL Discuss] [OpenDaylight TSC] ODL Developer Event topics due 5/14

[Luis Gomez]

Here is one:

https://wiki.lfnetworking.org/display/LN/2021-06-DD+-+ODL%3A+Docker+and+Helm 


BR/Luis

> On May 13, 2021, at 12:11 PM, Casey Cain  wrote:
> 
> Hello, everyone 
> 
> I would like to remind everyone that the Developer & Testing Form topic 
> submission deadline is tomorrow, Friday the 14th of June.  Currently, we do 
> not have any submitted topics.  Please ensure that you submit your proposed 
> topics as soon as possible.
> 
> Event Details:
> June 7-10
> 5am PT - 9:30am PT (Noon UTC - 16:30 UTC)
> Registration (free, but required) 
> 
> Topic Proposals 
> 
> Thanks,
> Casey Cain
> Technical Program Manager / Community Architect
> Linux Foundation
> _
> IRC: CaseyLF
> WeChat: okaru6
> Voice: +1.408.641.0193
> Book a Meeting w/ Casey
>  
> 
> 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#8735): https://lists.opendaylight.org/g/Discuss/message/8735
Mute This Topic: https://lists.opendaylight.org/mt/82817670/21656
Group Owner: discuss+ow...@lists.opendaylight.org
Unsubscribe: https://lists.opendaylight.org/g/Discuss/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [ODL Discuss] [opendaylight-dev] Lab setup: OpenDayLight (Aluminium) with mininet

[Luis Gomez]

Hi Rathinam,

FYI l2switch application last release was Oxygen.

Later ODL releases still support OpenFlow plugin but without l2switch you have 
to configure the flows in the controller.

BR/Luis


> On Apr 27, 2021, at 4:42 AM, Rathinam Trainers Rathinam Trainers 
>  wrote:
> 
> I am setting up SDN lab using Open Daylight (Aluminum) and mininet.
> 
> Installed features-openflowplugin in ODL.
> Started mininet (default topology: 1 switch with 2 hosts)
> sudo mn --controller=remote,ip=192.168.122.11
> Ping is failing.
> 
> mininet> pingall
> *** Ping: testing ping reachability
> h1 -> X
> h2 -> X
> *** Results: 100% dropped (0/2 received)
> ODL didn't populate any flows in OVS switch s1.
> 
> $ sudo ovs-ofctl -O OpenFlow13 dump-flows s1
>  cookie=0xa, duration=1297.951s, table=0, n_packets=29, n_bytes=1958, 
> send_flow_rem priority=0 actions=CONTROLLER:65535
> In ODL (Aluminum), I don't see l2switch plugin. What is the way to make ODL 
> to auto-populate the flow rules so that hosts (h1 & h2) can communicate with 
> eachother?
> 
> 
> 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#8730): https://lists.opendaylight.org/g/Discuss/message/8730
Mute This Topic: https://lists.opendaylight.org/mt/82500879/21656
Group Owner: discuss+ow...@lists.opendaylight.org
Unsubscribe: https://lists.opendaylight.org/g/Discuss/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [ODL Discuss] Aluminium SR2 RFC8040 SSE support

[Luis Gomez]

I think this jira explains how to use the feature:

https://jira.opendaylight.org/browse/NETCONF-679 


And there is also this test in robot:

https://git.opendaylight.org/gerrit/gitweb?p=integration/test.git;a=blob;f=csit/suites/netconf/notifications/notifications_basic.robot

Let us know if you have further questions.

BR/Luis

> On Apr 19, 2021, at 11:42 PM, Zsolt Krenak  wrote:
> 
> Hi Everyone,
> 
> This question is still valid, can someone give me a definitive answer? Thanks 
> in advance!
> 
> Br,
> 
> Zsolt
> 
> 
> 
> 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#8725): https://lists.opendaylight.org/g/Discuss/message/8725
Mute This Topic: https://lists.opendaylight.org/mt/81717028/21656
Group Owner: discuss+ow...@lists.opendaylight.org
Unsubscribe: https://lists.opendaylight.org/g/Discuss/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [ODL Discuss] [OpenDaylight TSC] ODL Helm chart

[Luis Gomez]

Hi Dan, thanks for the pointer :)


> On Apr 8, 2021, at 9:51 AM, TIMONEY, DAN  wrote:
> 
> Luis, Anil:
>  
> ONAP also creates a base OpenDaylight docker container, based on the 
> ONAP-specific ODL tarball.  Here’s a link to the code that creates the 
> Aluminum version of that docker:
>  
> https://github.com/onap/ccsdk-distribution/tree/master/opendaylight/aluminum/aluminum-alpine
>  
> <https://github.com/onap/ccsdk-distribution/tree/master/opendaylight/aluminum/aluminum-alpine>
>  
> Dan
>  
> -- 
> Dan Timoney
> dtimo...@att.com <mailto:dtimo...@att.com>
> Lead Member of Tech Staff
> ONAP Project Technical Lead : CCSDK and SDNC projects
>  
>  
> From:  on behalf of Luis Gomez 
> Date: Sunday, April 4, 2021 at 7:02 PM
> To: Anil Belur 
> Cc: discuss , TSC 
> 
> Subject: Re: [OpenDaylight TSC] ODL Helm chart
>  
> OK, thanks for the ONAP pointers, I have explored them and I figured the 
> following:
>  
> Docker:
>  
> 1) ONAP projects use maven to build docker:
> https://github.com/onap/aai-aai-common/blob/master/aai-common-docker/aai-common-images/pom.xml
>  
> <https://urldefense.com/v3/__https:/github.com/onap/aai-aai-common/blob/master/aai-common-docker/aai-common-images/pom.xml__;!!BhdT!19CRV5B87kwzj2BejylPOzDGjQJ6WKtT4gidQvLqO1aJwKWhJyxSeAGNUHrH$>
>  
> 2) LFN global-jjb has templates for docker build and publish:
> https://github.com/lfit/releng-global-jjb/blob/master/jjb/lf-maven-jobs.yaml#L998
>  
> <https://urldefense.com/v3/__https:/github.com/lfit/releng-global-jjb/blob/master/jjb/lf-maven-jobs.yaml*L998__;Iw!!BhdT!19CRV5B87kwzj2BejylPOzDGjQJ6WKtT4gidQvLqO1aJwKWhJyxSePS17-4G$>
>  
> 3) ONAP publishes docker images in Nexus:
> https://nexus3.onap.org/#browse/search/docker 
> <https://urldefense.com/v3/__https:/nexus3.onap.org/*browse/search/docker__;Iw!!BhdT!19CRV5B87kwzj2BejylPOzDGjQJ6WKtT4gidQvLqO1aJwKWhJyxSeJKoL1Bs$>
>  
> Helm:
>  
> 1) ONAP projects define their charts in a common repo called OOM:
> https://github.com/onap/oom/tree/master/kubernetes/aai 
> <https://urldefense.com/v3/__https:/github.com/onap/oom/tree/master/kubernetes/aai__;!!BhdT!19CRV5B87kwzj2BejylPOzDGjQJ6WKtT4gidQvLqO1aJwKWhJyxSeMNQgILU$>
>  
> 2) Helm job are in ONAP ci-management repo whilst build Makefiles are in OOM:
> https://github.com/onap/ci-management/blob/master/jjb/oom/oom-helm.yaml 
> <https://urldefense.com/v3/__https:/github.com/onap/ci-management/blob/master/jjb/oom/oom-helm.yaml__;!!BhdT!19CRV5B87kwzj2BejylPOzDGjQJ6WKtT4gidQvLqO1aJwKWhJyxSeETKZ8RI$>
> https://github.com/onap/oom/blob/master/kubernetes/aai/Makefile 
> <https://urldefense.com/v3/__https:/github.com/onap/oom/blob/master/kubernetes/aai/Makefile__;!!BhdT!19CRV5B87kwzj2BejylPOzDGjQJ6WKtT4gidQvLqO1aJwKWhJyxSeIlMprw2$>
>  
> 3) ONAP publishes helm packages in Nexus:
> https://nexus.onap.org/content/sites/oom-helm-release/3.0.0-ONAP/ 
> <https://urldefense.com/v3/__https:/nexus.onap.org/content/sites/oom-helm-release/3.0.0-ONAP/__;!!BhdT!19CRV5B87kwzj2BejylPOzDGjQJ6WKtT4gidQvLqO1aJwKWhJyxSeKxFiVLK$>
>  
> So in general I think we can leverage a lot of work from above but before 
> doing that I have a couple of question:
>  
> 1) Does current Centos builder image support docker?
> 2) Does ODL have a docker repo like 
> https://nexus3.onap.org/#browse/search/docker? 
> <https://urldefense.com/v3/__https:/nexus3.onap.org/*browse/search/docker?__;Iw!!BhdT!19CRV5B87kwzj2BejylPOzDGjQJ6WKtT4gidQvLqO1aJwKWhJyxSeL3A0mS1$>
>  
> Thanks/Luis
>  
>  
> 
> 
>> On Mar 25, 2021, at 10:06 PM, Anil Belur > <mailto:abe...@linuxfoundation.org>> wrote:
>>  
>> Hello Luis: 
>>  
>> ONAP has a few jobs that publish helm charts onto Nexus, and we have some 
>> scripts in place that can be reused. 
>> Some examples below:
>>  
>> https://nexus.onap.org/content/sites/oom-helm-staging/master/ 
>> <https://urldefense.com/v3/__https:/nexus.onap.org/content/sites/oom-helm-staging/master/__;!!BhdT!19CRV5B87kwzj2BejylPOzDGjQJ6WKtT4gidQvLqO1aJwKWhJyxSeFrE3B6C$>
>> https://jenkins.onap.org/job/aai-oom-guilin-merge-external-helm/ 
>> <https://urldefense.com/v3/__https:/jenkins.onap.org/job/aai-oom-guilin-merge-external-helm/__;!!BhdT!19CRV5B87kwzj2BejylPOzDGjQJ6WKtT4gidQvLqO1aJwKWhJyxSeLxDrlyX$>
>>  
>> If ODL requires a similar jobs/setup, I can make a generic version of these 
>> jobs and move them into global-jjb repo. 
>> However we'll also need additional Ubuntu 18.04 images that installs helm.
>>  
>> https://github.com/onap/ci-management/blob/master/jjb/global-template-helm.yaml
>>  
>> <https://urldefense.com/v3/__https:/githu

[ODL Discuss] ODL Helm chart group

[Luis Gomez]

Hi everyone,

We are trying to organize some work for creating docker images and helm charts 
for ODL. In order to kick-off this work, schedule a call, etc, I would like to 
know who would be interested in contributing. Please reply to this mail or 
unicast to me if you prefer.

Thanks/Luis 
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#8717): https://lists.opendaylight.org/g/Discuss/message/8717
Mute This Topic: https://lists.opendaylight.org/mt/81947086/21656
Group Owner: discuss+ow...@lists.opendaylight.org
Unsubscribe: https://lists.opendaylight.org/g/Discuss/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [ODL Discuss] ODL Helm chart

[Luis Gomez]

I would think the netconf project, being the most popular out-of-the-box 
application, would be the perfect candidate to create a helm chart. Still we 
have to figure the best place for docker and helm code (centralized vs 
distributed).

BR/Luis

> On Apr 5, 2021, at 5:38 PM, Anil Belur  wrote:
> 
> 
> On Mon, Apr 5, 2021 at 9:02 AM Luis Gomez  <mailto:ece...@gmail.com>> wrote:
> OK, thanks for the ONAP pointers, I have explored them and I figured the 
> following:
> 
> Docker:
> 
> 1) ONAP projects use maven to build docker:
> https://github.com/onap/aai-aai-common/blob/master/aai-common-docker/aai-common-images/pom.xml
>  
> <https://github.com/onap/aai-aai-common/blob/master/aai-common-docker/aai-common-images/pom.xml>
> 
> 2) LFN global-jjb has templates for docker build and publish:
> https://github.com/lfit/releng-global-jjb/blob/master/jjb/lf-maven-jobs.yaml#L998
>  
> <https://github.com/lfit/releng-global-jjb/blob/master/jjb/lf-maven-jobs.yaml#L998>
> 
> 3) ONAP publishes docker images in Nexus:
> https://nexus3.onap.org/#browse/search/docker 
> <https://nexus3.onap.org/#browse/search/docker>
> 
> Helm:
> 
> 1) ONAP projects define their charts in a common repo called OOM:
> https://github.com/onap/oom/tree/master/kubernetes/aai 
> <https://github.com/onap/oom/tree/master/kubernetes/aai>
> 
> 2) Helm job are in ONAP ci-management repo whilst build Makefiles are in OOM:
> https://github.com/onap/ci-management/blob/master/jjb/oom/oom-helm.yaml 
> <https://github.com/onap/ci-management/blob/master/jjb/oom/oom-helm.yaml>
> https://github.com/onap/oom/blob/master/kubernetes/aai/Makefile 
> <https://github.com/onap/oom/blob/master/kubernetes/aai/Makefile>
> 
> 3) ONAP publishes helm packages in Nexus:
> https://nexus.onap.org/content/sites/oom-helm-release/3.0.0-ONAP/ 
> <https://nexus.onap.org/content/sites/oom-helm-release/3.0.0-ONAP/>
> 
> So in general I think we can leverage a lot of work from above but before 
> doing that I have a couple of question:
> 
> 1) Does current Centos builder image support docker?
> 2) Does ODL have a docker repo like 
> https://nexus3.onap.org/#browse/search/docker? 
> <https://nexus3.onap.org/#browse/search/docker?>
> 
> 
>  
> 1. We already have a CentOS docker image, which can be used.
> 2. The docker image requires to be pushed to Nexus3, which is already 
> available for ODL, while the Helm charts are pushed onto Nexus2. We'll only 
> need to roll out the repo config for the required projects.
> 
> Do we have a use-case as to what $projects would be using these jobs & if 
> these are existing/newer projects? 
> 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#8716): https://lists.opendaylight.org/g/Discuss/message/8716
Mute This Topic: https://lists.opendaylight.org/mt/81610658/21656
Group Owner: discuss+ow...@lists.opendaylight.org
Unsubscribe: https://lists.opendaylight.org/g/Discuss/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [ODL Discuss] #opendaylight-help-openflow #opendaylight #help

[Luis Gomez]

It is all in the docs link I sent, you need a REST client and then pass the 
URL, headers and body as described. Let me know if you have specific questions.

> On Apr 8, 2021, at 7:31 AM, abercrombiepayme...@gmail.com wrote:
> 
> Hi Luis,
> 
> Apologies, I am very new to this.
> 
> Could you provide specific instructions on how I could delete an entire 
> openflow table from a switch? How can I use the xml example from the website?
> 
> 
> Thanks. 
> 
> 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#8714): https://lists.opendaylight.org/g/Discuss/message/8714
Mute This Topic: https://lists.opendaylight.org/mt/81914131/21656
Mute 
#opendaylight:https://lists.opendaylight.org/g/Discuss/mutehashtag/opendaylight
Mute 
#opendaylight-help-openflow:https://lists.opendaylight.org/g/Discuss/mutehashtag/opendaylight-help-openflow
Mute #help:https://lists.opendaylight.org/g/Discuss/mutehashtag/help
Group Owner: discuss+ow...@lists.opendaylight.org
Unsubscribe: https://lists.opendaylight.org/g/Discuss/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [ODL Discuss] #opendaylight-help-openflow #opendaylight #help

[Luis Gomez]

For flows not pushed by user, you have to use RPCs:

- To delete an individual flow you can do 
this:https://docs.opendaylight.org/projects/openflowplugin/en/stable-aluminium/users/operation.html#deleting-flows-from-switch-using-rpc-operation
 

- To delete all flows for a given table you can use a body like this:

{
"input": {
  
"opendaylight-flow-service:node":"/opendaylight-inventory:nodes/opendaylight-inventory:node[opendaylight-inventory:id='openflow:18097231385380982899']",
  "table_id": 255
 }
}

In the same document you can see RPCs to modify flows.

BR/Luis

> On Apr 7, 2021, at 5:30 AM, abercrombiepayme...@gmail.com wrote:
> 
> [Edited Message Follows]
> 
> I am using Opendaylight Carbon (also tried Oxygen) with Mininet. I created a 
> small network which conects to the remote ODL Controller using OpenFlow 1.3 
> using Virtual machines (Ubuntu 18.04) on the same subnet and the mininet 
> hosts can ping each other as expected.
> 
> When connecting to the controller using a browser, I can login with default 
> credentials and view the topoogy and Nodes using a web UI. Yang shows various 
> properties of which very few gives a response from the controller.
> 
> Problem: When sending the GET request: 
> http://ip_address:8181/restconf/config/opendaylight-inventory:nodes/ I get an 
> error message:
> 
> "Request could not be completed because the relevant data model content does 
> not exist"
> 
> 
> My objectives are to:
> 
> 1) get the controller to send a message to the switches to clear their flow 
> tables
> 2) get the controller to send a message to the switches to modify their flow 
> tables
> 
> 
> Any advice will be really appreciated.
> 
> 
> 
> 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#8712): https://lists.opendaylight.org/g/Discuss/message/8712
Mute This Topic: https://lists.opendaylight.org/mt/81914131/21656
Mute 
#opendaylight:https://lists.opendaylight.org/g/Discuss/mutehashtag/opendaylight
Mute 
#opendaylight-help-openflow:https://lists.opendaylight.org/g/Discuss/mutehashtag/opendaylight-help-openflow
Mute #help:https://lists.opendaylight.org/g/Discuss/mutehashtag/help
Group Owner: discuss+ow...@lists.opendaylight.org
Unsubscribe: https://lists.opendaylight.org/g/Discuss/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [ODL Discuss] #opendaylight-help-openflow #opendaylight #help

[Luis Gomez]

See inline:

> On Apr 7, 2021, at 5:30 AM, abercrombiepayme...@gmail.com wrote:
> 
> I am using Opendaylight Carbon (also tried Oxygen) with Mininet. I created a 
> small network which conects to the remote ODL Controller using OpenFlow 1.3 
> using Virtual machines (Ubuntu 18.04) on the same subnet and the mininet 
> hosts can ping each other as expected.
> 
> When connecting to the controller using a browser, I can login with default 
> credentials and view the topoogy and Nodes using a web UI. Yang shows various 
> properties of which very few gives a response from the controller.
> 
> Problem: When sending the GET request: 
> http://ip_address:8181/restconf/config/opendaylight-inventory:nodes/ I get an 
> error message
> 
> 

This request will only show the flows/groups pushed by the user via REST API, 
therefore it is expected no content, try operational vs config to see switch 
flows/groups.
> 
> "Request could not be completed because the relevant data model content does 
> not exist"
> 
> Note: I also get this error message on the switch when trying to view the 
> flow table: mininet> sh ovs-ofctl dump-flows s1 
> 2021-04-07T01:02:40Z|1|vconn|WARN|unix:/var/run/openvswitch/s1.mgmt: 
> version negotiation failed (we support version 0x01, peer supports version 
> 0x04) ovs-ofctl: s1: failed to connect to socket (Broken pipe)
> 
> 

The right command for OF13 protocol is: sh ovs-ofctl dump-flows s1 -O OpenFlow13
> 
> However, I am getting this message with both ODL and RYU, so I am not sure if 
> they are related.
> 
> I need this to work in order to write a Python program to clear flow tables.
> 
> Any advice will be appreciated.
> 
> 
> 
> 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#8710): https://lists.opendaylight.org/g/Discuss/message/8710
Mute This Topic: https://lists.opendaylight.org/mt/81914131/21656
Mute 
#opendaylight:https://lists.opendaylight.org/g/Discuss/mutehashtag/opendaylight
Mute 
#opendaylight-help-openflow:https://lists.opendaylight.org/g/Discuss/mutehashtag/opendaylight-help-openflow
Mute #help:https://lists.opendaylight.org/g/Discuss/mutehashtag/help
Group Owner: discuss+ow...@lists.opendaylight.org
Unsubscribe: https://lists.opendaylight.org/g/Discuss/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [ODL Discuss] ODL Helm chart

[Luis Gomez]

OK, thanks for the ONAP pointers, I have explored them and I figured the 
following:

Docker:

1) ONAP projects use maven to build docker:
https://github.com/onap/aai-aai-common/blob/master/aai-common-docker/aai-common-images/pom.xml

2) LFN global-jjb has templates for docker build and publish:
https://github.com/lfit/releng-global-jjb/blob/master/jjb/lf-maven-jobs.yaml#L998

3) ONAP publishes docker images in Nexus:
https://nexus3.onap.org/#browse/search/docker

Helm:

1) ONAP projects define their charts in a common repo called OOM:
https://github.com/onap/oom/tree/master/kubernetes/aai 
<https://github.com/onap/oom/tree/master/kubernetes/aai>

2) Helm job are in ONAP ci-management repo whilst build Makefiles are in OOM:
https://github.com/onap/ci-management/blob/master/jjb/oom/oom-helm.yaml
https://github.com/onap/oom/blob/master/kubernetes/aai/Makefile

3) ONAP publishes helm packages in Nexus:
https://nexus.onap.org/content/sites/oom-helm-release/3.0.0-ONAP/ 
<https://nexus.onap.org/content/sites/oom-helm-release/3.0.0-ONAP/>

So in general I think we can leverage a lot of work from above but before doing 
that I have a couple of question:

1) Does current Centos builder image support docker?
2) Does ODL have a docker repo like 
https://nexus3.onap.org/#browse/search/docker? 
<https://nexus3.onap.org/#browse/search/docker?>

Thanks/Luis



> On Mar 25, 2021, at 10:06 PM, Anil Belur  wrote:
> 
> Hello Luis: 
> 
> ONAP has a few jobs that publish helm charts onto Nexus, and we have some 
> scripts in place that can be reused. 
> Some examples below:
> 
> https://nexus.onap.org/content/sites/oom-helm-staging/master/ 
> <https://nexus.onap.org/content/sites/oom-helm-staging/master/>
> https://jenkins.onap.org/job/aai-oom-guilin-merge-external-helm/ 
> <https://jenkins.onap.org/job/aai-oom-guilin-merge-external-helm/>
> 
> If ODL requires a similar jobs/setup, I can make a generic version of these 
> jobs and move them into global-jjb repo. 
> However we'll also need additional Ubuntu 18.04 images that installs helm.
> 
> https://github.com/onap/ci-management/blob/master/jjb/global-template-helm.yaml
>  
> <https://github.com/onap/ci-management/blob/master/jjb/global-template-helm.yaml>
>  (stage-helm job)
> https://github.com/onap/ci-management/blob/master/shell/helm2-verify.sh 
> <https://github.com/onap/ci-management/blob/master/shell/helm2-verify.sh>
> https://github.com/onap/ci-management/blob/master/shell/helm-repo-init.sh 
> <https://github.com/onap/ci-management/blob/master/shell/helm-repo-init.sh>
> https://github.com/onap/ci-management/blob/master/shell/publish_helm_charts.sh
>  
> <https://github.com/onap/ci-management/blob/master/shell/publish_helm_charts.sh>
> 
> PS let me know if these bits can be reused. I can setup time to discuss the 
> details of usecase for ODL
> and get an understanding of which of the ODL $projects would require helm 
> charts.
> 
> Regards,
> Anil
> 
> 
> On Fri, Mar 26, 2021 at 4:51 AM Luis Gomez  <mailto:ece...@gmail.com>> wrote:
> As I brought in today's TSC meeting, any decent IT app nowadays has a helm 
> chart to quickly install in K8s.
> 
> Looking at some open source example:
> 
> https://github.com/prometheus-community/helm-charts/tree/main/charts/prometheus
>  
> <https://github.com/prometheus-community/helm-charts/tree/main/charts/prometheus>
> 
> It seems like we need to hold some helm definitions in our code repo for 
> folks to perform:
> 
> helm repo add odl https://opendaylight.github.io/helm-charts 
> <https://opendaylight.github.io/helm-charts>
> 
> Also we need to publish docker containers somewhere so they can be used in a 
> K8s Deployment file like this:
> 
> spec:
>   containers:
>   - name: odl
> image: quay.io/opendaylight/netconf:v0.13.0 
> <http://quay.io/opendaylight/netconf:v0.13.0>
> ...
> 
> I am not an expert in K8s so let me know if I miss anything.
> 
> Anil, do you see any problem in existing ODL infra to achieve the above?
> 
> BR/Luis


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#8705): https://lists.opendaylight.org/g/Discuss/message/8705
Mute This Topic: https://lists.opendaylight.org/mt/81610658/21656
Group Owner: discuss+ow...@lists.opendaylight.org
Unsubscribe: https://lists.opendaylight.org/g/Discuss/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [ODL Discuss] Removal of opendaylight-topology.yang

[Luis Gomez]

I think OFP still uses these models:

https://git.opendaylight.org/gerrit/gitweb?p=openflowplugin.git;a=blob;f=applications/topology-manager/pom.xml;h=d7e0d2151ea6e35955651195373439409e146651;hb=refs/heads/master#l42
 


Maybe we should move them to OFP project.

BR/Luis


> On Mar 26, 2021, at 4:06 AM, Robert Varga  wrote:
> 
> Hello everyone,
> 
> as we are ramping out changes which will go into the Phosphorus MRI
> window (and thus be part of Phosphorus Simultaneous Release ~6 months
> from now), there is one major removal.
> 
> It concerns OpenDaylight-specific models:
> - opendaylight-topology.yang
> - opendaylight-topology-inventory.yang
> - opendaylight-topology-view.yang
> 
> These models go back to 2013 and are the first cut at modeling a network
> of devices and interacting with it in the context of a model-driven
> controller.
> 
> The concepts introduced here have been gradually superseded by RFC7950's
> (YANG 1.1) introduction of 'action' as well as the work done under the
> auspices of IETF's I2RS Working Group
> (https://datatracker.ietf.org/wg/i2rs/documents/).
> 
> Since the last user of these models, controller's equally-obsolete
> 'messagebus', is going away in this release, so are these models. This
> work item is tracked here:
> https://jira.opendaylight.org/browse/CONTROLLER-1978.
> 
> Regards,
> Robert
> 
> 
> 
> 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#8701): https://lists.opendaylight.org/g/Discuss/message/8701
Mute This Topic: https://lists.opendaylight.org/mt/81625190/21656
Group Owner: discuss+ow...@lists.opendaylight.org
Unsubscribe: https://lists.opendaylight.org/g/Discuss/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[ODL Discuss] ODL Helm chart

[Luis Gomez]

As I brought in today's TSC meeting, any decent IT app nowadays has a helm 
chart to quickly install in K8s.

Looking at some open source example:

https://github.com/prometheus-community/helm-charts/tree/main/charts/prometheus

It seems like we need to hold some helm definitions in our code repo for folks 
to perform:

helm repo add odl https://opendaylight.github.io/helm-charts

Also we need to publish docker containers somewhere so they can be used in a 
K8s Deployment file like this:

spec:
  containers:
  - name: odl
image: quay.io/opendaylight/netconf:v0.13.0
...

I am not an expert in K8s so let me know if I miss anything.

Anil, do you see any problem in existing ODL infra to achieve the above?

BR/Luis
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#8697): https://lists.opendaylight.org/g/Discuss/message/8697
Mute This Topic: https://lists.opendaylight.org/mt/81610658/21656
Group Owner: discuss+ow...@lists.opendaylight.org
Unsubscribe: https://lists.opendaylight.org/g/Discuss/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [ODL Discuss] Unable to connect Opendaylight: Aluminium with Mininet

[Luis Gomez]

I would suggest to read this (if not done yet):

- OFP installation: 
https://docs.opendaylight.org/projects/openflowplugin/en/stable-aluminium/users/installation.html
 

- OFP usage: 
https://docs.opendaylight.org/projects/openflowplugin/en/stable-aluminium/users/operation.html
 


Let me know if you have questions.

BR/Luis

> On Mar 3, 2021, at 1:32 AM, Aqeem Nasir  wrote:
> 
> Good evening,
> 
> I recently installed Opendaylight:Aluminium for a SDN project. But, I am 
> unable to connect the controller with Mininet. Is there any tutorial 
> regarding this that I can follow? Your help is much appreciated.
> 
> Thank you
> 
> 
> 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#8690): https://lists.opendaylight.org/g/Discuss/message/8690
Mute This Topic: https://lists.opendaylight.org/mt/81059412/21656
Group Owner: discuss+ow...@lists.opendaylight.org
Unsubscribe: https://lists.opendaylight.org/g/Discuss/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [ODL Discuss] Docs meeting

[Luis Gomez]

It looks iike we reached an agreement, Tuesday 7:30-8:00 PST.

Casey, can you please set up the call? Lets start weekly and move to bi-weekly 
when we have less things to discuss.

BR/Luis


> On Feb 18, 2021, at 11:18 PM, Luis Gomez  wrote:
> 
> Hi everyone,
> 
> FYI I started this doodle to see which time suits best for a weekly/bi-weekly 
> docs meeting:
> 
> https://doodle.com/poll/dqk2pxn594f5cby8 
> <https://doodle.com/poll/dqk2pxn594f5cby8>
> 
> BR/Luis
> 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#8688): https://lists.opendaylight.org/g/Discuss/message/8688
Mute This Topic: https://lists.opendaylight.org/mt/80750498/21656
Group Owner: discuss+ow...@lists.opendaylight.org
Unsubscribe: https://lists.opendaylight.org/g/Discuss/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[ODL Discuss] Docs meeting

[Luis Gomez]

Hi everyone,

FYI I started this doodle to see which time suits best for a weekly/bi-weekly 
docs meeting:

https://doodle.com/poll/dqk2pxn594f5cby8 


BR/Luis


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#8686): https://lists.opendaylight.org/g/Discuss/message/8686
Mute This Topic: https://lists.opendaylight.org/mt/80750498/21656
Group Owner: discuss+ow...@lists.opendaylight.org
Unsubscribe: https://lists.opendaylight.org/g/Discuss/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [ODL Discuss] [lfn-odl-onap-collab] Reminder: ONAP/ODL Integration Sync @ 10am to 11am Pacific Tuesday, July 21

[Luis Gomez]

Thanks for the feedback, I personally cannot make the meeting today (have a 
conflict) but maybe others can.

BR/Luis

> On Feb 16, 2021, at 6:18 AM, TIMONEY, DAN  wrote:
> 
> All,
>
> Are we still having this call today?  Just checking because I thought I 
> remembered an earlier email thread when we said perhaps this call was no 
> longer needed.
>
> To share our plans for ONAP – our current release (Honolulu) is now based on 
> Aluminum SR1.  We had planned to upgrade to SR2, but then thought better of 
> it when we saw a discussion on the opendaylight mailing lists regarding a 
> potential security vulnerability in the restconf project in SR2.  
> Unfortunately, I’m not sure that SR3 will be available in time for us to use 
> (our release signoff for Honolulu is scheduled for 4/1).  However, if this is 
> a vulnerability that is already present in SR1, then we would probably look 
> to upgrade to SR3 in a subsequent Honolulu maintenance release.
>
> Our next release (Istanbul) will be based on Silicon.  When we get closer to 
> the dates (we don’t have a schedule yet for Istanbul), I’ll be in a better 
> position to say which service release we plan to align with.
>
> Dan
>
> -- 
> Dan Timoney
> dtimo...@att.com 
> Lead Member of Tech Staff
> ONAP Project Technical Lead : CCSDK and SDNC projects
>
>
> From: cc...@linuxfoundation.org 
> When: 1:00 PM - 2:00 PM February 16, 2021 
> Subject: [lfn-odl-onap-collab] Reminder: ONAP/ODL Integration Sync @ 10am to 
> 11am Pacific Tuesday, July 21
> Location: Zoom
>
>
> Please remember the ONAP-ODL sync meeting at 10 am Pacific later today 
> (Tuesday, July 21):
>
> https://zoom.us/j/91654497219 
> 
>
>
> -- Forwarded message -
> From: Casey Cain  >
> Date: Thu, Jun 4, 2020 at 9:53 AM
> Subject: Updated invitation: ONAP/ODL Integration Sync @ Monthly from 10am to 
> 11am on the third Tuesday (PDT) 
>
> This event has been changed.
> ONAP/ODL Integration Sync
> When
> Changed: Monthly from 10am to 11am on the third Tuesday Pacific Time - Los 
> Angeles
> Where
> Zoom (map 
> )
> Calendar
> abhijitk...@gmail.com   
> Who
> •
>
> more details » 
> 
> 
> ---
> Video Conferencing:
> https://zoom.us/j/91654497219 
> 
> +1 3462487799 (US Houston toll)
> +1 6465588656 (US New York toll)
> +1 6699006833 (US San Jose toll)
> +1 2532158782 (US Tacoma toll)
> +1 3017158592 (US Germantown toll)
> +1 3126266799 (US Chicago toll)
> +1 8773690926 (US tollfree)
> +1 8558801246 (US tollfree)
> +1 5873281099 (Canada toll)
> +1 6473744685 (Canada toll)
> +1 6475580588 (Canada toll)
> +1 7789072071 (Canada toll)
> +1 4388097799 (Canada toll)
> +1 8557038985 (Canada tollfree)
> 
> Created with DOODLE
> Going (abhijitk...@gmail.com )?   All events in 
> this series:   Yes 
> 
>  - Maybe 
> 

[ODL Discuss] ODL & Yang slides

[Luis Gomez]

Please find session slides here:

https://wiki.lfnetworking.org/display/LN/2021-02-02+-+OpenDaylight+and+YANG

BR/Luis


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#8683): https://lists.opendaylight.org/g/Discuss/message/8683
Mute This Topic: https://lists.opendaylight.org/mt/80316218/21656
Group Owner: discuss+ow...@lists.opendaylight.org
Unsubscribe: https://lists.opendaylight.org/g/Discuss/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[ODL Discuss] old wiki down

[Luis Gomez]

FYI the old ODL wiki is down:

https://wiki-archive.opendaylight.org/

I opened ticket here:

https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/IT-21459

BR/Luis


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#8681): https://lists.opendaylight.org/g/Discuss/message/8681
Mute This Topic: https://lists.opendaylight.org/mt/80224358/21656
Group Owner: discuss+ow...@lists.opendaylight.org
Unsubscribe: https://lists.opendaylight.org/g/Discuss/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [ODL Discuss] Invitation: ODL TSC US/Pacific Meeting @ Every 2 weeks from 09:00 to 10:00 on Thursday (PDT) (discuss@lists.opendaylight.org)

[Luis Gomez]

Casey, I do not see an invite for IST friendly bi-weekly meetings. If these 
require passcode, please send invite for these too.

> On Sep 24, 2020, at 9:08 AM, Casey Cain  wrote:
> 
> You have been invited to the following event.
> ODL TSC US/Pacific Meeting
> When
> Every 2 weeks from 09:00 to 10:00 on Thursday Pacific Time - Los Angeles
> Where
> https://zoom.us/j/219174946?pwd=aW9uSXl0KzJpcjRXY3l1bWIwdG9KZz09 (map 
> )
> Calendar
> discuss@lists.opendaylight.org
> Who
> •
> Casey Cain - creator
> •
> k.fase...@gmail.com
> •
> lorand.ja...@gmail.com
> •
> vishnoia...@gmail.com
> •
> jluhr...@gmail.com
> •
> tejas.nevre...@gmail.com
> •
> abe...@linuxfoundation.org
> •
> zxi...@gmail.com
> •
> discuss@lists.opendaylight.org
> •
> t...@lists.opendaylight.org
> •
> ddelarosa0...@gmail.com
>  more details » 
> 
> OpenDaylight Community is inviting you to a scheduled Zoom meeting.
> Topic: ODL TSC US/Pacific Meeting
> Time: This is a recurring meeting Meet anytime
> 
> Join Zoom Meeting
> https://zoom.us/j/219174946?pwd=aW9uSXl0KzJpcjRXY3l1bWIwdG9KZz09 
> 
> Meeting ID: 219 174 946
> Passcode: 559387
> One tap mobile
> +16699006833,,219174946# US (San Jose)
> +12532158782,,219174946# US (Tacoma)
> 
> Dial by your location
> +1 669 900 6833 US (San Jose)
> +1 253 215 8782 US (Tacoma)
> +1 346 248 7799 US (Houston)
> +1 646 558 8656 US (New York)
> +1 301 715 8592 US (Germantown)
> +1 312 626 6799 US (Chicago)
> 855 880 1246 US Toll-free
> 877 369 0926 US Toll-free
> +1 587 328 1099 Canada
> +1 647 374 4685 Canada
> +1 647 558 0588 Canada
> +1 778 907 2071 Canada
> +1 204 272 7920 Canada
> +1 438 809 7799 Canada
> 855 703 8985 Canada Toll-free
> Meeting ID: 219 174 946
> Find your local number: https://zoom.us/u/dxjWHo5gv 
> 
> Going (discuss@lists.opendaylight.org)?   All events in this series:   Yes 
> 
>  - Maybe 
> 
>  - No 
> 
> more options » 
> 
> Invitation from Google Calendar 
> You are receiving this courtesy email at the account 
> discuss@lists.opendaylight.org because you are an attendee of this event.
> 
> To stop receiving future updates for this event, decline this event. 
> Alternatively you can sign up for a Google account at 
> https://www.google.com/calendar/ and control your notification settings for 
> your entire calendar.
> 
> Forwarding this invitation could allow any recipient to send a response to 
> the organizer and be added to the guest list, or invite others regardless of 
> their own invitation status, or to modify your RSVP. Learn More 
> .
> 
> 
> 
> 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#8651): https://lists.opendaylight.org/g/Discu

Re: [ODL Discuss] ODL deployment survey

[Luis Gomez]

Hi Ahmed,

I see some of the questions also apply to non DC use cases so maybe we can 
structure the questions as follows:

Do you use SDN?
If No, what is the reason for not adopting SDN? (add Other to the list)
If Yes:
What type of SDN your operators is adopt? (add Other to the list)
Is your SDN based in Open Source or Vendor commercial product?
If Open Source, which SDN you deploy?
If vendor product, which SDN you deploy?
Which are the biggest pain points for SDN (add Other to the list)
What is the most important feature you are looking from an Open source 
SDN Controller?

Do you use SDN in DCs?
If Yes:
Is Separate SDN for Fabric and Overlay an acceptable solution?
Do you require SDN to extend across DC’s i.e towards the Edge?
What are the deployment models for for SDN in DC?
Which are the biggest pain points for DC SDN? (add Other to the list)
What type of SDN you are using for Kubernetes

Also, would it be possible to ask ODL related questions like the ones Tejas 
shared:

Do you use ODL in any of your SDN deployments?
If Yes:
For how long is ODL being used in the Lab? (dates, years)
For how long is ODL being used in the Production? (dates, years)
What are your future plans on the usage of ODL?
Will you be willing to contribute any local fixes to upstream?
How often do you update your production to the latest release community 
version? - Once a year, twice a year

BR/Luis
 


> On Sep 10, 2020, at 12:23 PM, Ahmed Sawaf  wrote:
> 
> Hello Gents
>
> Kindly find the initial draft for SDN survey , it more focus on DC SDN , so 
> please check and if you can support in whatever can help us it will great
>
> It will great to have your feedback by next Tuesday 15th September
>
>
>
> From: Casey Cain [mailto:cc...@linuxfoundation.org] 
> Sent: Friday, August 28, 2020 1:09 AM
> To: discuss ; TSC 
> 
> Cc: Ahmed Sawaf 
> Subject: ODL deployment survey
>
> Hello, everyone.
>
> On today's TSC meeting we had a guest, Amed Sawaf from the LFN End User 
> Advisory Group.  We discussed a community survey.
> At a high level, we identified some initial goals for the community survey:
>   • Need to identify users
>   • Need to identify use cases and which are being actively used
>   • How is ODL being consumed
>   • Which Projects and which release is being used?
>   • Is there a fork of the code that is being maintained? What 
> version is being used?
>   • Will Operators be willing to have DevOps teams contribute to the 
> upstream community?
> The TSC would like to collect additional feedback from the community to see 
> if we can refine the survey questions even further.
>
> Best,
> Casey Cain
> Technical Program Manager / Community Architect
> Linux Foundation
> _
> IRC: CaseyLF
> WeChat: okaru6
> Voice: +1.408.641.0193
> Book a Meeting w/ Casey
> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#8637): https://lists.opendaylight.org/g/Discuss/message/8637
Mute This Topic: https://lists.opendaylight.org/mt/76463613/21656
Group Owner: discuss+ow...@lists.opendaylight.org
Unsubscribe: https://lists.opendaylight.org/g/Discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [ODL Discuss] [OpenDaylight TSC] TWS Knowledge Session for Monday Aug 27, 2020

[Luis Gomez]

BTW tomorrow I have kids doctor appointment at 8AM, I should be done by 9AM, 
but if I am late Jamo can start with int/test Q&As.

BR/Luis


> On Aug 27, 2020, at 2:09 PM, Abhijit Kumbhare  wrote:
> 
> Yes - of course. As is in the case of most developer knowledge sessions, 
> there is no preparation is expected even for the int/dist portion as well. 
> For int/dist, it will be a Q & A and screen sharing walk through of the 
> project (mostly pointing out where to look for things). 
> 
> On Thu, Aug 27, 2020 at 1:14 PM Jamo Luhrsen  > wrote:
> FYI, the int/test portion of the TWS is QA only (think office hours). I will 
> not have
> anything prepared as a "presentation".
> 
> Thanks,
> JamO
> 
> On 8/27/20 10:19 AM, Abhijit Kumbhare wrote:
>> Hi folks,
>> 
>> Luis/Jamo/Rangan will do a TWS session on Monday to talk about integration 
>> distribution (int/dist) & test (int/test). 
>> 
>> The TWS meeting info is here:
>> 
>> https://wiki.opendaylight.org/x/vQUF 
>> 
>> Or in short:
>> Meeting time: Mondays:  9:00am Pacific. 6 pm Central European Summer Time 
>> (CEST), 9:30 pm India
>> 
>> Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/522266747 
>> 
>> 
>> Thanks,
>> Abhijit
>> 
>> 
>> 
> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#8632): https://lists.opendaylight.org/g/Discuss/message/8632
Mute This Topic: https://lists.opendaylight.org/mt/76460304/21656
Group Owner: discuss+ow...@lists.opendaylight.org
Unsubscribe: https://lists.opendaylight.org/g/Discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [ODL Discuss] How can I change my topology using RESTCONF commands?

[Luis Gomez]

Just want to clarify that OFP project only provides operational topology:  
/restconf/operational/network-topology:network-topology/topology/flow:1 that 
BTW cannot be modified by user because this is discovered using LLDP packets as 
described in the docs. I am not sure what is the purpose of reading/writting in 
the config topology: 
/restconf/configuration/network-topology:network-topology/topology/flow:1, but 
whatever it is, it is not implemented in ODL.

BR/Luis


> On Jul 23, 2020, at 10:27 AM, Tejas Nevrekar  wrote:
> 
> Hi Carlos,
> 
> Note that the topology is always discovered from mininet and hence will 
> always be in /restconf/operational. More details on how this works is 
> https://docs.opendaylight.org/projects/openflowplugin/en/latest/users/operation.html
>  
> 
> 
> Quick answer is there is no easy way by which you can update what's in 
> /restconf/operational by writing to /restconf/config/
> 
> However, you can write to the 
> /restconf/config/network-topology:network-topology/topology/flow:1 by 
> constructing the full payload containing nodes/links. A simple way to do that 
> is to do a GET  
> /restconf/operational/network-topology:network-topology/topology/flow:1 and 
> provide the output of that in a PUT to  
> /restconf/config/network-topology:network-topology/topology/flow:1.
> 
> Please let us know if this helped.
> 
> Regards,
> 
> -Tejas.
>
> 
> On Thu, Jul 23, 2020 at 10:42 AM Carlos Martins via lists.opendaylight.org 
>   > wrote:
> Hello everyone!!!
> 
> I need your help about MDSAL. 
> 
> I am creating a college project with ODL(Oxygen - karaf 0.8.0) + MININET 
> (2.2.1) and I have installed the features:
> 
> 1) odl-restconf-all, odl-dluxapps-topology, odl-l2switch-switch-ui,  and 
> odl-netconf-connector-all
> 
> 2) running the mininet like mn --topo linear,3 
> --controller=remote,ip=,port=6633 --switch ovs
> 
> However, I am unable to get the config data store to put or delete links of 
> the topology.
> 
> For example:
> 
> The link 
> 
> 1) GET  
> http://localhost:8181/restconf/operational/network-topology:network-topology 
> 
>  -> Works, return all topology
> 2) GET 
> http://localhost:8181/restconf/operational/network-topology:network-topology/topology/flow:1/link/openflow:2:3
>  
> 
>  ->  Works, return my link openflow:2:3 
> 
> But 
> 
> 3) GET 
> http://localhost:8181/restconf/config/network-topology:network-topology/topology/flow:1/link/openflow:2:3
>  
> 
>   - > Does not work, return error 
> 
> error-message": "Request could not be completed because the relevant data 
> model content does not exist "
> 
> and 
> 
> 4) DELETE 
> http://localhost:8181/restconf/config/network-topology:network-topology/topology/flow:1/link/openflow:2:3
>  
> 
>  ->  Does not work, return error
>
>  "error-message": "Data does not exist for path: 
> /(urn:TBD:params:xml:ns:yang:network-topology?revision=2013-10-21)network-topology/topology/topology[{(urn:TBD:params:xml:ns:yang:network-topology?revision=2013-10-21)topology-id=flow:1}]/link/link[{(urn:TBD:params:xml:ns:yang:network-topology?revision=2013-10-21)link-id=openflow:2:3}]"
>
>
> OBS: 
>
> 1) My topology is created by MININET and odl-l2switch-switch-ui inside DLUX 
> UI;
> 2) Anyone link in the config path in RESTCONF does not work ( 
> http://localhost:8181/restconf/config/* 
> );
> 3) I am using curl commands like;
> 
> curl -H "Content-Type: application/xml" -u admin:admin -X DELETE 
> http://localhost:8181/restconf/config/network-topology:network-topology/topology/flow:1/link/openflow:2:3
>  
> 
>
> So, how can I change my topology using RESTCONF commands?
> 
> Thanks !!!
> 
> 
> --- 
> Carlos Martins
> 
> carlosmartins...@yahoo.com.br 
> 
> ---
> 
> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#8618): https://lists.opendaylight.org/g/Discuss/message/8618
Mute This Topic: https://lists.opendaylight.org/mt/75740317/21656
Group Owner: discuss+ow...@lists.opendaylight.org
Unsubscribe: https://lists.opendaylight.org/g/Discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [ODL Discuss] [release] Action for PTLs & projects: Project Wiki Pages

[Luis Gomez]

As I said in this morning TSC, we have ODL interns helping moving content from 
old wiki to new wiki. If PTLs just fix the project landing page links to point 
to the right old wiki links, the interns can easily pick up and move old wiki 
links content to confluence.

BR/Luis


> On Jul 2, 2020, at 4:44 PM, Abhijit Kumbhare  wrote:
> 
> Removed announce and added discuss.
> 
> Please note there are copied over project pages on Confluence currently - 
> however they have stale links. You will need to create sub-pages and copy 
> over those sub-pages from mediawiki.
> 
> On Thu, Jul 2, 2020 at 10:50 AM Abhijit Kumbhare  > wrote:
> Deadline: 16 July, 2020
> Project Wiki Pages
> OpenDaylight wiki was updated earlier in the year from using mediawiki to 
> using Confluence. The old mediawiki is still available at 
> https://wiki-archive.opendaylight.org 
> , but https://wiki.opendaylight.org 
>  now points to Confluence.   
> However individual Project Wikis have not been updated in Confluence - these 
> need to be done by the projects themselves. We need the PTLs and the projects 
> to copy over content from the mediawiki.  If this is not done it is extremely 
> hard to locate project specific information for both the old and the new 
> users.
> We had already talked about this and actioned the projects in the past - but 
> this has not been done so far.
> What projects need to do:
> Locate your old project page from 
> https://wiki-archive.opendaylight.org/view/Project_list 
> 
> Locate your new project page from https://wiki.opendaylight.org/x/-QUF 
>  (Projects 
> ). 
> Make sure the relevant and still valid content from the old project page has 
> been copied over to the new project page. If it has not been copied over 
> cleanly - make sure it has been copied over. It is likely Casey Cain 
>  has copied over the basic 
> stuff.
> You will need to create a new page for each of the sub pages of the project 
> and link it to your project main page.
> Overall this process is usually a matter of copy-paste but may involve some 
> more editing, creating new pages as well as fixing links.
> We need this to be done ASAP. We will keep a deadline for this as 16 Jul 2020 
> - which will give projects 2 weeks to finish this.
> Daniel De La Rosa  
> will be adding & tracking this requirement as part of the Aluminum release.
> 
> Please note the above from the TSC meeting minutes 
> (https://wiki.opendaylight.org/x/dg0F ) 
> from today. Two weeks is a reasonable deadline - we really need this to be 
> done. If you are on a vacation or have a reason which makes it hard to finish 
> by July 16 - please let Daniel & me know when you can finish it as soon as 
> you are back from your vacation.
> 
> Thanks,
> Abhijit
> 
> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#8597): https://lists.opendaylight.org/g/Discuss/message/8597
Mute This Topic: https://lists.opendaylight.org/mt/75270668/21656
Group Owner: discuss+ow...@lists.opendaylight.org
Unsubscribe: https://lists.opendaylight.org/g/Discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [ODL Discuss] [OpenDaylight Discuss] ODL Got Link/Nodes information updated in real time

[Luis Gomez]

Just to clarify: dlux provided graphical information of nodes and links for an 
OpenFlow network. AFAIK there is no application in ODL to measure delay & 
jitter, mostly because these kind of application usually run in the network 
devices themselves, not in the controller.

BR/Luis



> On Mar 24, 2020, at 8:38 PM, Daniel de la Rosa  
> wrote:
> 
> Hello Lei
> 
> I think that monitoring link/nodes for delay and jitter was possible with ODL 
> and DLUX but that is no longer available. Please let us know if you can 
> contribute to get this capability on ODL again.
> 
> Thanks
> 
> On Fri, Mar 20, 2020 at 9:22 AM LEI WANG  > wrote:
> Hi Everyone,
> 
> I have a question about odl controller monitoring link/nodes. I want to know 
> is it possible for controller to get information updated from every link/node 
> of link delay/jitter/bandwidth in real time?
> 
> Kind regards
> 
> Lei
> 
> 
> 
> 
> -- 
> Daniel de la Rosa
> Customer Support Manager
> Lumina Networks Inc.
> e: ddelar...@luminanetworks.com 
> m:  +1 408 7728120
> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#8555): https://lists.opendaylight.org/g/Discuss/message/8555
Mute This Topic: https://lists.opendaylight.org/mt/72534347/21656
Group Owner: discuss+ow...@lists.opendaylight.org
Unsubscribe: https://lists.opendaylight.org/g/Discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [ODL Discuss] [OpenDaylight Discuss] sodium restconf auth method

[Luis Gomez]

Hi Michael,

I do not think there is any plan for replacing the removed oauth/token 
interface. Please feel free to contribute this to ODL.

BR/Luis


> On Mar 23, 2020, at 9:44 AM, Michael Dürre 
>  wrote:
> 
> Hi,
> 
> I already ask to aaa-...@lists.opendaylight.org 
>  but without any response.
> 
> I'm trying to find out which new interfaces for login are available since 
> sodium release, because I see you removed the oauth/token interface. 
> https://jira.opendaylight.org/browse/AAA-173 
>  but it is still part of the 
> documentation 
> (https://docs.opendaylight.org/projects/aaa/en/latest/user-guide.html 
> ). 
> Because we do not want to use basicAuth for our GUI. Is there maybe planned 
> to have or even already implemented JWT (jsonwebtoken) or something else? I 
> already tried to implemented this into neon-SR1 but with medium success. That 
> means it worked (so login and verify) but at the same time disabled basicAuth.
> 
> I'm thankful for every hint I can get.
> Thanks in advance.
> 
> Kind regards,
> Michael
> -- 
> Michael Dürre
> Software Engineer
>
> highstreet technologies GmbH
> Hähnelstraße 6
> 12159 Berlin
> Skype: michael.due...@highstreet-technologies.com 
> 
> E-Mail: michael.due...@highstreet-technologies.com 
> 
> Web: http://www.highstreet-technologies.com 
> 
>
> Geschäftsführer: Dipl.-Ing. (FH) Alfons Mittermaier
> Handelsregister: Amtsgericht Charlottenburg, HRB 114905 B
> Firmensitz: Berlin
> USt-IdNr.: DE261090513
>
>
> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#8553): https://lists.opendaylight.org/g/Discuss/message/8553
Mute This Topic: https://lists.opendaylight.org/mt/72527374/21656
Group Owner: discuss+ow...@lists.opendaylight.org
Unsubscribe: https://lists.opendaylight.org/g/Discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OpenDaylight Discuss] [opendaylight-dev] [release] [OpenDaylight TSC] Action Requested - Magnesium Updates

[Luis Gomez]

FYI I just added the ONAP distribution we do for CCSDK project.

> On Mar 18, 2020, at 12:23 PM, Ajay Lele  wrote:
> 
> Updated for bgpcep and daexim
> 
> On Wed, Mar 18, 2020 at 8:46 AM Abhijit Kumbhare  > wrote:
> Thanks!
> 
> On Wed, Mar 18, 2020 at 5:14 AM  > wrote:
> Hi
> 
> Martin and Olivier have confirmed it's OK for them.
> You can consider our section is ready.
> 
> Guillaume
> 
> De : LAMBERT Guillaume TGI/OLN
> Envoyé : mardi 17 mars 2020 17:36
> À : Abhijit Kumbhare; Casey Cain
> Cc : ODLDEV; TSC; Release; discuss; Brandon Wick; RENAIS Olivier TGI/OLN; 
> transportpce-...@lists.opendaylight.org 
> ; mb4...@att.com 
> 
> Objet : RE: [release] [OpenDaylight TSC] Action Requested - Magnesium Updates
> 
> Hi all
> 
>
> I’ve added a section for TransportPCE with a short descriptions and a 
> detailed list of features and enhancement.
> 
> I put Olivier and Martin in CC so that they can confirm us by tomorrow it is 
> OK on their side.
> 
>
> Hope this helps
> 
> Guillaume
> 
>
> NB: since TransportPCE is a SM project working in best effort, we haven’t 
> declared an accurate plan for the release with a JIRA ticket.
> 
>
>
>
> De : rele...@lists.opendaylight.org  
> [mailto:rele...@lists.opendaylight.org 
> ] De la part de Abhijit Kumbhare
> Envoyé : lundi 16 mars 2020 17:41
> À : Casey Cain
> Cc : ODLDEV; TSC; Release; discuss; Brandon Wick
> Objet : Re: [release] [OpenDaylight TSC] Action Requested - Magnesium Updates
> 
>
> PTLs,
> 
>
> You should have this info in your project release plans for Magnesium - just 
> make sure they are updated and copy over that information in the table linked 
> by Casey:
> 
>
>    <>
> Thanks,
> 
> Abhijit
> 
>
> 
> 
> 
> On Mar 16, 2020, at 9:27 AM, Casey Cain  > wrote:
> 
>
> Hello, everyone.
> 
>
> We need to update the OpenDaylight messaging to reflect the current state of 
> the project. PTLs, please update the wiki with a brief update on what has 
> changed with your project and what benefit this provides to users (2-4 
> sentences should suffice). 
> 
> Please make your updates no later than Wednesday, March 18th, and let us know 
> if you have any questions. 
> 
>   https://wiki.lfnetworking.org/display/ODL/Magnesium+Release 
> 
> 
>
> Thanks,
> 
> Casey Cain
> 
> Technical Program Manager / Community Architect
> 
> Linux Foundation
> 
> _
> 
> IRC - CaseyLF
> 
> WeChat - okaru6
> 
> Book a Meeting w/ Casey 
>
>
> _
> 
> Ce message et ses pieces jointes peuvent contenir des informations 
> confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu 
> ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
> electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou 
> falsifie. Merci.
> 
> This message and its attachments may contain confidential or privileged 
> information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete 
> this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been 
> modified, changed or falsified.
> Thank you.
> 
> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#8547): https://lists.opendaylight.org/g/Discuss/message/8547
Mute This Topic: https://lists.opendaylight.org/mt/72057699/21656
Group Owner: discuss+ow...@lists.opendaylight.org
Unsubscribe: https://lists.opendaylight.org/g/Discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OpenDaylight Discuss] About setting VxLAN through ODL/Netconf

[Luis Gomez]

Hi Hitoshi,

Unfortunately I do not know the details for VxLAN configuration in Juniper. 
However if you configure VxLAN via CLI and after you receive the router 
configuration via REST:

GET 
http://{{controller}}:8181/restconf/config/network-topology:network-topology/topology/topology-netconf/node/VMX-01/yang-ext:mount/

You should be able to figure out the URL and body you are asking for. If not 
please send the output of the above request and I will provide my best guess.

BR/Luis

> On Feb 20, 2020, at 8:05 PM, Hitoshi Kaneko  
> wrote:
> 
> Luis Gomez-san, 
> CC: opendaylight personnel
> 
> This is Hitoshi in NTT labs.
> 
> Did you have a chance to see the below email I sent you day after yesterday ?
> 
> I hope to know whether ODL implement control over VxLAN.
> 
> I'll happy to receive information about it, anything is fine.
> 
> 
> Thank you.
> Regards,
> Hitoshi Kaneko
> E-mail: Hitoshi Kaneko 
> 
> -Original Message-
> From: Hitoshi Kaneko  
> Sent: Wednesday, February 19, 2020 7:09 PM
> To: 'Luis Gomez' 
> Cc: 'netconf-...@lists.opendaylight.org' 
> Subject: About setting VxLAN through ODL/Netconf
> 
> Luis Gomez-san, 
> 
> This is Hitoshi in NTT labs.
> 
> Thank you for helping me about how to set NIC-IP-address to vMX from ODL 
> other day recently at below mail.
> 
> Now, I want to evaluate VxLAN-control from ODL/Netconf to JUNOS(vMX).
> 
> I have been able to set VxLAN to vMX from command-line.
> 
> I'm very happy if you advise me about it, for example, giving related URLs, 
> anything is fine.
> 
> Thank you.
> Regards,
> Hitoshi Kaneko
> E-mail: Hitoshi Kaneko 
> 
> -Original Message-
> From: netconf-...@lists.opendaylight.org  
> On Behalf Of Luis Gomez
> Sent: Monday, November 4, 2019 4:50 AM
> To: Hitoshi Kaneko 
> Cc: netconf-...@lists.opendaylight.org
> Subject: Re: [netconf-dev] about setting NIC-IP-address through ODL/Netconf
> 
> Hi Hitoshi,
> 
> See my comments in-line:
> 
> 
> 
>   On Oct 31, 2019, at 1:45 AM, Hitoshi Kaneko 
> mailto:hitoshi.kaneko...@hco.ntt.co.jp> > 
> wrote:
> 
>   Luis Gomez-san, 
>   
>   This is Hitoshi.
>   Thank you for your answer and kindness.
>   
>   
> 
>   enough CPU (4 CPUs) and RAM (8GB) and you setup the 
> java heap to -Xmx8G.
>   
> 
> 
>   I show my machine conditions with below LOGs. 
>   Is it enough?
>   
> 
> 
> It seems very sufficient, so I do not think the problem you are hitting is 
> due to the controller system resources.
> 
> 
>   As the problem of ‘not responding in several minutes’ has persisted 
> with above machine conditions,
>   I have tried two actions below.
>   
>   1) I have demanded Juniper, Ltd to send me Junos 18.1.(now, 17.2R1)
>   2) I have been increasing yang schema files that is specified when node 
> is created,
>   because I have specified only 2 schema files till now, as there are 
> many schema files for Junos 17.2R1.
>   
>   
> 
> 
> No comments, just try with updated JUNOS and let us know if that works better 
> for you.
> 
> 
>   Please advise me if you have comments above actions.
>   
>   
>   Thank you.
>   Regards,
>   Hitoshi Kaneko
>   E-mail: Hitoshi Kaneko  <mailto:hitoshi.kaneko...@hco.ntt.co.jp> >
>   
>   
>   --- LOGs ---
>   【CPU cores, etc.】
>   kaneko@kaneko-PowerEdge-T130-3:~$ cat /proc/cpuinfo | grep "cpu cores"
>   cpu cores : 4
>   cpu cores : 4
>   cpu cores : 4
>   cpu cores : 4
>   cpu cores : 4
>   cpu cores : 4
>   cpu cores : 4
>   cpu cores : 4
>   kaneko@kaneko-PowerEdge-T130-3:~$ cat /proc/cpuinfo | grep "physical id"
>   physical id : 0
>   physical id : 0
>   physical id : 0
>   physical id : 0
>   physical id : 0
>   physical id : 0
>   physical id : 0
>   physical id : 0
>   kaneko@kaneko-PowerEdge-T130-3:~$ cat /proc/cpuinfo | grep processor
>   processor : 0
>   processor : 1
>   processor : 2
>   processor : 3
>   processor : 4
>   processor : 5
>   processor : 6
>   processor : 7
>   kaneko@kaneko-PowerEdge-T130-3:~$ 
>   
>   
> 
> 
> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#8530): https://lists.opendaylight.org/g/Discuss/message/8530
Mute This Topic: https://lists.opendaylight.org/mt/71444650/21656
Group Owner: discuss+ow...@lists.opendaylight.org
Unsubscribe: https://lists.opendaylight.org/g/Discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OpenDaylight Discuss] [release] TWS on Security

[Luis Gomez]

Robert, you are the only one left from the original security team, so we need 
you. Let us know when we can schedule this or if you prefer to use another slot.

BR/Luis


> On Feb 5, 2020, at 11:15 AM, Abhijit Kumbhare  wrote:
> 
> Sounds a good idea.
> 
> On Wed, Feb 5, 2020 at 10:00 AM Luis Gomez  <mailto:ece...@gmail.com>> wrote:
> Hello everyone,
> 
> During last Kernel call there were questions about ODL Security process. In 
> addition, KKS (Lumina security member) is trying to catch up with the process.
> 
> So I just wonder, can we do a TWS session to inform people and address some 
> of the Security questions, like for example:
> 
> - What is current process for reporting, analyzing and addressing and 
> documenting security vulnerabilities (PSIRT).
> - What are the tools used to find vulnerabilities? how to access these tools?
> - Can we do dynamic scanning in ODL?
> - Which security information is public vs private
> - How do we track security tickets? is it possible to use Jira?
> - How does security team sync up (call, mail, etc) 
> 
> BR/Luis
> 
> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#8523): https://lists.opendaylight.org/g/Discuss/message/8523
Mute This Topic: https://lists.opendaylight.org/mt/71003489/21656
Group Owner: discuss+ow...@lists.opendaylight.org
Unsubscribe: https://lists.opendaylight.org/g/Discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OpenDaylight Discuss] TWS on Security

[Luis Gomez]

Hello everyone,

During last Kernel call there were questions about ODL Security process. In 
addition, KKS (Lumina security member) is trying to catch up with the process.

So I just wonder, can we do a TWS session to inform people and address some of 
the Security questions, like for example:

- What is current process for reporting, analyzing and addressing and 
documenting security vulnerabilities (PSIRT).
- What are the tools used to find vulnerabilities? how to access these tools?
- Can we do dynamic scanning in ODL?
- Which security information is public vs private
- How do we track security tickets? is it possible to use Jira?
- How does security team sync up (call, mail, etc) 

BR/Luis

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#8521): https://lists.opendaylight.org/g/Discuss/message/8521
Mute This Topic: https://lists.opendaylight.org/mt/71001653/21656
Group Owner: discuss+ow...@lists.opendaylight.org
Unsubscribe: https://lists.opendaylight.org/g/Discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OpenDaylight Discuss] [OpenDaylight TSC] Micro-distribution: Follow Up from TWS

[Luis Gomez]

I missed Monday call, but I still have hard time to understand why we have not 
made any progress in this topic in Magnesium: first reason "not clear scope/use 
case" was addressed by just targeting Netconf micro-distribution in this 
release, second reason "lack of people" is not valid as there are enough folks 
interested that even put their names in the Lighty proposal, third reason "lack 
of driving", Tejas volunteered to drive the effort. So I wonder: what is next 
reason or excuse for not starting this effort?

BR/Luis


> On Jan 22, 2020, at 10:34 AM, Tejas Nevrekar  wrote:
> 
> Hi all,
> 
> Just bringing here the discussion we had in the TWS this Monday. 
> 
> Robert, as some of us were proposing in the TWS we would like to do a POC 
> level effort to create a netconf micro-distribution using lighty as a first 
> step in using lighty in ODL. I would like to know from the Lighty team if 
> there are any known gaps in the proposed lighty modules given here 
> (https://wiki.opendaylight.org/view/Project_Proposals:Lighty 
> ) that will make 
> it hard/unfeasible to realize a netconf micro-distribution.
> 
> Also when it comes to use cases, in the Mg DDF Luis and I had outlined a few 
> use cases that we wanted to eventually solve with this solution - 
> https://wiki.lfnetworking.org/download/attachments/19006711/ODL-Scale%20Mg.pdf?version=1&modificationDate=1569500298000&api=v2
>  
> 
> 
> Thanks,
> 
> Tejas. S. Nevrekar
> Mobile: +91-99805 31339
> Bangalore, INDIA.
> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#8514): https://lists.opendaylight.org/g/Discuss/message/8514
Mute This Topic: https://lists.opendaylight.org/mt/69998017/21656
Group Owner: discuss+ow...@lists.opendaylight.org
Unsubscribe: https://lists.opendaylight.org/g/Discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OpenDaylight Discuss] Help in Opendaylight Sodium setup

[Luis Gomez]

Hi Lucas,

Last release of l2switch was oxygen, after that there were no contributors to 
maintain the project so no more releases were produced.

If you or anybody is interested in this project, please read this mail thread, 
it is not that hard to get it back:

https://lists.opendaylight.org/g/Discuss/topic/l2switch_flow_removal/34547216 


BR/Luis


> On Nov 4, 2019, at 7:43 PM, Lucas Ruchel  wrote:
> 
> Hello everyone,
> 
> I am performing the tests using the mininet simulator, in older versions of 
> OpendayLight I was able to do the tests without problems. But in newer 
> versions I can't get two hosts to communicate.
> 
> I read in a forum that the l2switch module is no longer being included in 
> OpendayLight distributions. Is there any other package or way to provide 
> host-to-host communication.
> 
> Thanks for the help
> 
> -- 
>  Lucas Ruchel
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> 
> View/Reply Online (#8475): 
> https://lists.opendaylight.org/g/Discuss/message/8475
> Mute This Topic: https://lists.opendaylight.org/mt/44260566/1217165
> Group Owner: discuss+ow...@lists.opendaylight.org
> Unsubscribe: https://lists.opendaylight.org/g/Discuss/unsub  
> [ece...@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#8479): https://lists.opendaylight.org/g/Discuss/message/8479
Mute This Topic: https://lists.opendaylight.org/mt/44260566/21656
Group Owner: discuss+ow...@lists.opendaylight.org
Unsubscribe: https://lists.opendaylight.org/g/Discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OpenDaylight Discuss] [opendaylight-dev] Access to web GUI Setting up SD-WAN

[Luis Gomez]

Yes, it is correct, last dlux release was oxygen. After that there were not 
contributors for the framework so no more releases were produced.

FYI we have an intern (Rohan) trying to build and eventually release the 
project for Neon:

https://git.opendaylight.org/gerrit/#/c/dlux/+/85039/ 


But this is only temporal work (internship ends in 1 month), if you or anyone 
wants to continue and maintain dlux project in ODL please go ahead.

As you well say, dlux is the only GUI in ODL.

BR/Luis



> On Nov 6, 2019, at 6:09 PM, Kumar Udaya  wrote:
> 
> 
> I have done the same research and investigation few weeks ago.
> 
> I see that oxygen is the last release, where web GUI(dlux) is supported.
> After that, Web GUI support was dropped.
> 
> Here is the message reiterating that.
> https://lists.opendaylight.org/g/Discuss/message/8370 
> 
> 
> My understanding is that, controller(sodium) only provides rest APIs
> Other experts can correct me, if I am wrong. 
> 
> Thanks
> ..Kumar
> 
> 
> On Wed, Nov 6, 2019 at 7:23 AM Zak Haasbroek  > wrote:
> 
> To Whom it may concern.
> 
>  
> 
> We as  are new to  ODL and SD-WAN.
> 
>  
> 
> I have installed  the Sodium release on a Centos 8 VM.
> 
>  
> 
> All the guides I have found online mention the installation of the *dlux 
> packages to enable the web GUI.
> 
> When I do a features:list  while in the console this is all the features I 
> see  Please follow this link  https://justpaste.it/5sni5 
> .
> 
> I do not see any packages pertaining to the gui  it seems a lot of the 
> features have been re-named.
> 
>  
> 
> After  experimentation and some research I still stuck trying to figure out 
> if ODL is supports SD-WAN natively through one of its managed project 
> https://docs.opendaylight.org/en/stable-sodium/#getting-started-with-opendaylight
>  
> ,
>  or does it just provide an API for other SD-WAN providers to make use of the 
> tools provided.
> 
> Please provide guidance on how to procede.
> 
>  
> 
> Regards
> 
>  
> 
>  
> 
>  
> 
> 
> 
> 
> Zak Haasbroek
> Linux Engineer
> 
> Office VoIP:  087 353 6576
> Email:supp...@implyit.co.za 
> Web:  www.implyit.co.za 
> 
> Durban | Gauteng | Cape Town
>  
>    
> 
> 
> This e-mail and it's contents is subject to our privacy and security policy. 
> For more information, please click on the following link - ImplyIT Privacy & 
> Security Policy 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> 
> View/Reply Online (#5680): https://lists.opendaylight.org/g/dev/message/5680 
> 
> Mute This Topic: https://lists.opendaylight.org/mt/44213962/2612056 
> 
> Group Owner: dev+ow...@lists.opendaylight.org 
> 
> Unsubscribe: https://lists.opendaylight.org/g/dev/unsub 
>   [kumarudaya1...@gmail.com 
> ]
> -=-=-=-=-=-=-=-=-=-=-=-
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> 
> View/Reply Online (#5682): https://lists.opendaylight.org/g/dev/message/5682
> Mute This Topic: https://lists.opendaylight.org/mt/44213962/1217165
> Group Owner: dev+ow...@lists.opendaylight.org
> Unsubscribe: https://lists.opendaylight.org/g/dev/unsub  [ece...@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#8478): https://lists.opendaylight.org/g/Discuss/message/8478
Mute This Topic: https://lists.opendaylight.org/mt/45258793/21656
Group Owner: discuss+ow...@lists.opendaylight.org
Unsubscribe: https://lists.opendaylight.org/g/Discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OpenDaylight Discuss] [release] ODL Technical Advisory Council Representative Election

[Luis Gomez]

OK, then it is fine.

> On Nov 5, 2019, at 3:40 PM, Abhijit Kumbhare  wrote:
> 
> No - we did not vote on that. However the election plan was that the 3 
> elections would be held in parallel. Also all the LFN projects now seem to 
> have the 3 different elections.
> 
> 
> On Tue, Nov 5, 2019 at 3:30 PM Luis Gomez  <mailto:ece...@gmail.com>> wrote:
> Did not we say that going forward TSC/TAC/SPC could be the same person to 
> simplify the process?
> 
>> On Nov 5, 2019, at 3:02 PM, Abhijit Kumbhare > <mailto:abhijitk...@gmail.com>> wrote:
>> 
>> Hi Casey,
>> 
>> Can you please align all the three elections to have the same timeline? TSC 
>> Chair, TAC and the SPC?
>> 
>> Currently the TSC Chair election nomination period & voting period is 3 days 
>> before the TAC & the SPC elections. It will be great if you can just extend 
>> the self nomination period of the TSC Chair election to align with the TAC & 
>> SPC elections.
>> 
>> Thanks,
>> Abhijit
>> 
>> 
>> On Tue, Nov 5, 2019 at 9:37 AM Casey Cain > <mailto:cc...@linuxfoundation.org>> wrote:
>> Hello, everyone.
>> 
>> The role of the Technical Advisory Council is to facilitate communication 
>> and collaboration among the Technical Projects in the LFN.  All OpenDaylight 
>> Committers are eligible. 
>> 
>> TAC Representative Responsibilities
>> Coordinating collaboration across technical projects
>> Making recommendations to the Finance Committee of resource priorities for 
>> Technical Projects
>> Electing TAC representative to the governing board
>> Setting processes/procedures for the election of "committer representative" 
>> to the LFN Governing Board
>> Other matters related to the technical role of the TAC that may be 
>> communicated to the TAC by the LFN Governing Board
>> Nominations will close November 18th, 2019.  If you would like to 
>> self-nominate, please do so here:
>> https://wiki.lfnetworking.org/x/FACDAQ 
>> <https://wiki.lfnetworking.org/x/FACDAQ>
>> 
>> Best,
>> Casey Cain
>> Technical Program Manager / Community Architect
>> Linux Foundation
>> _
>> IRC - CaseyLF
>> WeChat - okaru6
>> -=-=-=-=-=-=-=-=-=-=-=-
>> Links: You receive all messages sent to this group.
>> 
>> View/Reply Online (#18296): 
>> https://lists.opendaylight.org/g/release/message/18296 
>> <https://lists.opendaylight.org/g/release/message/18296>
>> Mute This Topic: https://lists.opendaylight.org/mt/42296121/675589 
>> <https://lists.opendaylight.org/mt/42296121/675589>
>> Group Owner: release+ow...@lists.opendaylight.org 
>> <mailto:release%2bow...@lists.opendaylight.org>
>> Unsubscribe: https://lists.opendaylight.org/g/release/unsub 
>> <https://lists.opendaylight.org/g/release/unsub>  [abhijitk...@gmail.com 
>> <mailto:abhijitk...@gmail.com>]
>> -=-=-=-=-=-=-=-=-=-=-=-
>> -=-=-=-=-=-=-=-=-=-=-=-
>> Links: You receive all messages sent to this group.
>> 
>> View/Reply Online (#18298): 
>> https://lists.opendaylight.org/g/release/message/18298 
>> <https://lists.opendaylight.org/g/release/message/18298>
>> Mute This Topic: https://lists.opendaylight.org/mt/42296121/1217165 
>> <https://lists.opendaylight.org/mt/42296121/1217165>
>> Group Owner: release+ow...@lists.opendaylight.org 
>> <mailto:release+ow...@lists.opendaylight.org>
>> Unsubscribe: https://lists.opendaylight.org/g/release/unsub 
>> <https://lists.opendaylight.org/g/release/unsub>  [ece...@gmail.com 
>> <mailto:ece...@gmail.com>]
>> -=-=-=-=-=-=-=-=-=-=-=-
> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#8474): https://lists.opendaylight.org/g/Discuss/message/8474
Mute This Topic: https://lists.opendaylight.org/mt/42708832/21656
Group Owner: discuss+ow...@lists.opendaylight.org
Unsubscribe: https://lists.opendaylight.org/g/Discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OpenDaylight Discuss] [release] ODL Technical Advisory Council Representative Election

[Luis Gomez]

Did not we say that going forward TSC/TAC/SPC could be the same person to 
simplify the process?

> On Nov 5, 2019, at 3:02 PM, Abhijit Kumbhare  wrote:
> 
> Hi Casey,
> 
> Can you please align all the three elections to have the same timeline? TSC 
> Chair, TAC and the SPC?
> 
> Currently the TSC Chair election nomination period & voting period is 3 days 
> before the TAC & the SPC elections. It will be great if you can just extend 
> the self nomination period of the TSC Chair election to align with the TAC & 
> SPC elections.
> 
> Thanks,
> Abhijit
> 
> 
> On Tue, Nov 5, 2019 at 9:37 AM Casey Cain  > wrote:
> Hello, everyone.
> 
> The role of the Technical Advisory Council is to facilitate communication and 
> collaboration among the Technical Projects in the LFN.  All OpenDaylight 
> Committers are eligible. 
> 
> TAC Representative Responsibilities
> Coordinating collaboration across technical projects
> Making recommendations to the Finance Committee of resource priorities for 
> Technical Projects
> Electing TAC representative to the governing board
> Setting processes/procedures for the election of "committer representative" 
> to the LFN Governing Board
> Other matters related to the technical role of the TAC that may be 
> communicated to the TAC by the LFN Governing Board
> Nominations will close November 18th, 2019.  If you would like to 
> self-nominate, please do so here:
> https://wiki.lfnetworking.org/x/FACDAQ 
> 
> 
> Best,
> Casey Cain
> Technical Program Manager / Community Architect
> Linux Foundation
> _
> IRC - CaseyLF
> WeChat - okaru6
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> 
> View/Reply Online (#18296): 
> https://lists.opendaylight.org/g/release/message/18296 
> 
> Mute This Topic: https://lists.opendaylight.org/mt/42296121/675589 
> 
> Group Owner: release+ow...@lists.opendaylight.org 
> 
> Unsubscribe: https://lists.opendaylight.org/g/release/unsub 
>   [abhijitk...@gmail.com 
> ]
> -=-=-=-=-=-=-=-=-=-=-=-
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> 
> View/Reply Online (#18298): 
> https://lists.opendaylight.org/g/release/message/18298 
> 
> Mute This Topic: https://lists.opendaylight.org/mt/42296121/1217165 
> 
> Group Owner: release+ow...@lists.opendaylight.org 
> 
> Unsubscribe: https://lists.opendaylight.org/g/release/unsub 
>   [ece...@gmail.com 
> ]
> -=-=-=-=-=-=-=-=-=-=-=-

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#8472): https://lists.opendaylight.org/g/Discuss/message/8472
Mute This Topic: https://lists.opendaylight.org/mt/42708832/21656
Group Owner: discuss+ow...@lists.opendaylight.org
Unsubscribe: https://lists.opendaylight.org/g/Discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OpenDaylight Discuss] about setting NIC-IP-address through ODL/Netconf(there have been progress)

[Luis Gomez]

Hi Hitoshi,

See my answers below:

> On Oct 18, 2019, at 4:56 AM, Hitoshi Kaneko  
> wrote:
> 
> Luis Gomez-san, 
> 
> This is Hitoshi.
> 
> Thank you for your answer and kindness.
> 
> I have tried to use “POST Method”, describing below.
> Is my command correct?

It seems correct but have you also tried the PUT with the original body and the 
modified URL I suggested?

> However, it has error ended.
> May it be problems of ODL?

If you get HTTP 500, there is surely some logging in the kara.log that can be 
used to troubleshoot further.

> Do I have better use new version of ODL?

We push lot of fixes in every release, so yes I would suggest to use a newest 
version from this page: 
https://docs.opendaylight.org/en/stable-sodium/downloads.html 
<https://docs.opendaylight.org/en/stable-sodium/downloads.html>

Also make sure the JUNOS is 17.4X or more updated version. I heard previous 
versions have some problems with ODL.

BR/Luis


> 
> 
> Thank you.
> Regards,
> Hitoshi Kaneko
> E-mail: Hitoshi Kaneko 
> 
> =-
> kaneko@kaneko-PowerEdge-T130-3:~$ curl -v -k -u admin:admin -H "Content-Type: 
> application/json" -X POST 
> http://localhost:8181/restconf/config/network-topology:network-topology/topology/topology-netconf/node/Juniper-tst02/yang-ext:mount/configuration:configuration/interfaces/interface/ge-0%2F0%2F2/
>  -d '
>> {
>>  "unit": [
>>{
>>  "name": "0",
>>  "family": {
>>"inet": {
>>  "address": [
>>{
>>  "name": "192.168.30.2/24"
>>}
>>  ]
>>}
>>  }
>>}
>>  ]
>> }' | jq .
> Note: Unnecessary use of -X or --request, POST is already inferred.
>  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
> Dload  Upload   Total   SpentLeft  Speed
>  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
> 0*   Trying 127.0.0.1...
> * Connected to localhost (127.0.0.1) port 8181 (#0)
> * Server auth using Basic with user 'admin'
>> POST 
>> /restconf/config/network-topology:network-topology/topology/topology-netconf/node/Juniper-tst02/yang-ext:mount/configuration:configuration/interfaces/interface/ge-0%2F0%2F2/
>>  HTTP/1.1
>> Host: localhost:8181
>> Authorization: Basic YWRtaW46YWRtaW4=
>> User-Agent: curl/7.47.0
>> Accept: */*
>> Content-Type: application/json
>> Content-Length: 208
>> 
> } [208 bytes data]
> * upload completely sent off: 208 out of 208 bytes
> < HTTP/1.1 500 Server Error
> < Set-Cookie: JSESSIONID=1orv2m1ta3ng1na395yrbtz9k;Path=/restconf
> < Set-Cookie: rememberMe=deleteMe; Path=/restconf; Max-Age=0; Expires=Thu, 
> 17-Oct-2019 20:39:27 GMT
> < Content-Type: text/html;charset=ISO-8859-1
> < Cache-Control: must-revalidate,no-cache,no-store
> < Content-Length: 2832
> < Server: Jetty(8.1.19.v20160209)
> < 
> { [2832 bytes data]
> 100  3040  100  2832  100   208   474k  35677 --:--:-- --:--:-- --:--:--  553k
> * Connection #0 to host localhost left intact
> parse error: Invalid numeric literal at line 2, column 0
> kaneko@kaneko-PowerEdge-T130-3:~$ 
> 
> 
> -Original Message-
> From: Luis Gomez  
> Sent: Friday, October 18, 2019 3:38 PM
> To: Hitoshi Kaneko 
> Cc: discuss ; netconf-dev 
> 
> Subject: Re: [OpenDaylight Discuss] about setting NIC-IP-address through 
> ODL/Netconf(there have been progress)
> 
> Hi Hitoshi,
> 
> 0.5.3-Boron-SR3, may I ask why you are using so old version of ODL? this 
> version is long time not supported in ODL :(
> 
> Regarding the ERROR, I think you are using wrong method here:
> 
> if you use PUT you have to specify the interface in the URL, something like 
> this:
> 
> curl -v -k -u admin:admin -H "Content-Type: application/json" -X PUT 
> http://localhost:8181/restconf/config/network-topology:network-topology/topology/topology-netconf/node/Juniper-tst02/yang-ext:mount/configuration:configuration/interfaces/interface/ge-0%2F0%2F2
>  -d '
> {
> "interface": [
>   {
> "name": "ge-0/0/2",
> "unit": [
>   {
> "name": "0",
> "family": {
>   "inet": {
> "address": [
>   {
> "name": "192.168.30.5/24"
>   }
> ]
>   }
> }
>   }
> ]
&g

Re: [OpenDaylight Discuss] about setting NIC-IP-address through ODL/Netconf(there have been progress)

[Luis Gomez]

Hi Hitoshi,

0.5.3-Boron-SR3, may I ask why you are using so old version of ODL? this 
version is long time not supported in ODL :(

Regarding the ERROR, I think you are using wrong method here:

if you use PUT you have to specify the interface in the URL, something like 
this:

curl -v -k -u admin:admin -H "Content-Type: application/json" -X PUT 
http://localhost:8181/restconf/config/network-topology:network-topology/topology/topology-netconf/node/Juniper-tst02/yang-ext:mount/configuration:configuration/interfaces/interface/ge-0%2F0%2F2
 -d '
{
 "interface": [
   {
 "name": "ge-0/0/2",
 "unit": [
   {
 "name": "0",
 "family": {
   "inet": {
 "address": [
   {
 "name": "192.168.30.5/24"
   }
 ]
   }
 }
   }
 ]
   }
 ]
}'

If you do not want to specify interface in URL, then you can use POST vs PUT.

BR/Luis


> On Oct 17, 2019, at 10:47 PM, Hitoshi Kaneko 
>  wrote:
> 
> Hello, my name is Hitoshi Kaneko.
> I belong to NTT Laboratories.
> Although I have queried about above title the other day, as there have been 
> progress, I am sorry but please let me query again.
> Our state is below.
> (Target machine is Juniper vMX, ODL version is 0.5.3-Boron-SR3 )
> (1)   "Getting NIC-IP-address through ODL/Netconf" was normal ended (below 
> log㈰)
> (2)   "Changing NIC-IP-address through ODL/Netconf" was normal ended (below 
> log㈪)
> (3)   "Deleting NIC-IP-address through ODL/Netconf" was normal ended(below 
> log㈫)
> But, 
> (4)   "Creating NIC-IP-address through ODL/Netconf" was error ended(below 
> log㈬)
> About (4), Where is there my mistake?
> Or, Is feature if "Creating NIC-IP-address through ODL/Netconf" supported by 
> ODL ?
> I am happy if you send comment for my question.
> Thank you.
> Regards,
> Hitoshi Kaneko
> E-mail: Hitoshi Kaneko 
> 
> = LOGS ===
> ㈰kaneko@kaneko-PowerEdge-T130-3:~$ curl -v -k -u admin:admin -H 
> "Content-Type: application/xml" -X GET
> http://localhost:8181/restconf/config/network-topology:network-topology/topology/topology-netconf/node/Juniper-tst02/yang-ext:mount/
> configuration:configuration/interfaces/interface/ge-0%2F0%2F2 | jq .
> Note: Unnecessary use of -X or --request, GET is already inferred.
>  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
> Dload  Upload   Total   SpentLeft  Speed
>  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
> 0*   Trying 127.0.0.1...
> * Connected to localhost (127.0.0.1) port 8181 (#0)
> * Server auth using Basic with user 'admin'
>> GET
> /restconf/config/network-topology:network-topology/topology/topology-netconf/node/Juniper-tst02/yang-ext:mount/configuration:configu
> ration/interfaces/interface/ge-0%2F0%2F2 HTTP/1.1
>> Host: localhost:8181
>> Authorization: Basic YWRtaW46YWRtaW4=
>> User-Agent: curl/7.47.0
>> Accept: */*
>> Content-Type: application/xml
>> 
> < HTTP/1.1 200 OK
> < Set-Cookie: JSESSIONID=jireinjf2qxd1cpw6tiy59zjm;Path=/restconf
> < Expires: Thu, 01 Jan 1970 00:00:00 GMT
> < Set-Cookie: rememberMe=deleteMe; Path=/restconf; Max-Age=0; Expires=Thu, 
> 17-Oct-2019 14:25:24 GMT
> < Content-Type: application/yang.data+json
> < Vary: Accept-Encoding, User-Agent
> < Transfer-Encoding: chunked
> < Server: Jetty(8.1.19.v20160209)
> < 
> { [127 bytes data]
> 100   1160   1160 0   8705  0 --:--:-- --:--:-- --:--:--  8923
> * Connection #0 to host localhost left intact
> {
>  "interface": [
>{
>  "name": "ge-0/0/2",
>  "unit": [
>{
>  "name": "0",
>  "family": {
>"inet": {
>  "address": [
>{
>  "name": "192.168.30.2/24"
>}
>  ]
>}
>  }
>}
>  ]
>}
>  ]
> }
> 
> 
> ㈪kaneko@kaneko-PowerEdge-T130-3:~$ curl -v -k -u admin:admin -H 
> "Content-Type: application/json" -X PUT
> http://localhost:8181/restconf/config/network-topology:network-topology/topology/topology-netconf/node/Juniper-tst02/yang-ext:mount/
> configuration:configuration/interfaces/interface/ge-0%2F0%2F2/ -d '
>> {
>>  "interface": [
>>{
>>  "name": "ge-0/0/2",
>>  "unit": [
>>{
>>  "name": "0",
>>  "family": {
>>"inet": {
>>  "address": [
>>{
>>  "name": "192.168.30.5/24"
>>}
>>  ]
>>}
>>  }
>>}
>>  ]
>>}
>>  ]
>> }' | jq .
>  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
> Dload  Upload   Total   SpentLeft  Speed
>  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
> 0*   Trying 127.0.0.1...
> * Connected to localhost (127.0.0.1) port 8181 (#0)
> * Server auth using Basic with user 'admin'
>> PUT
> /restconf/config/n

Re: [OpenDaylight Discuss] l2switch flow removal

[Luis Gomez]

It is mostly a matter of bandwidth, expertise is not that important here. If 
you think you can spare some time in the ODL community, first updating the code 
to recent release (e.g. sodium), and second adding some features and fixing 
some bugs at your discretion, I would really encourage you to do so. When you 
are decided, please send a mail to the ODL TSC mail list 
(t...@lists.opendaylight.org) describing your plans for the project and asking 
how to proceed. AFAIR there is no established process to revive a project in 
OpenDaylight but the TSC should be able to come up with one.

Also if you need more information on how things work in ODL, I can definitely 
help you with that.

BR/Luis



> On Oct 17, 2019, at 11:01 AM, M. Ranganathan  wrote:
> 
> Hello Luis,
> 
> I've tinkered with l2switch a bit and I found it to be an excellent
> example. It is a tragedy that it is no longer alive.
> 
> Another useful addition could be adding vlan tagging. I have some
> ideas for that and have experimented with the old code base.  I can
> help out if you want to bring the project back to life.
> 
> Fair warning: My level of expertise is limited despite a good couple
> of years tinkering with application building using OpenDaylight.
> 
> Regards,
> 
> Ranga
> 
> 
> On Tue, Oct 15, 2019 at 12:38 PM Luis Gomez  wrote:
>> 
>> FYI l2switch project is not maintained anymore (e.g. no committers left) so 
>> if you or anyone is interested in contributing to this project, I would 
>> recommend to consider becoming a maintainer for this project.
>> 
>>> On Oct 15, 2019, at 6:23 AM, asnake  wrote:
>>> 
>>> hi there, recently i have modified the l2switch code which combined 
>>> reactive and proactive lke hybrid, the want to to remove some proactive 
>>> flows based on packet statistics or bytes usage at some interval how do i 
>>> do that?
>>> best regards, only hint is appreciated.
>>> -=-=-=-=-=-=-=-=-=-=-=-
>>> Links: You receive all messages sent to this group.
>>> 
>>> View/Reply Online (#8444): 
>>> https://lists.opendaylight.org/g/Discuss/message/8444
>>> Mute This Topic: https://lists.opendaylight.org/mt/34547216/1217165
>>> Group Owner: discuss+ow...@lists.opendaylight.org
>>> Unsubscribe: https://lists.opendaylight.org/g/Discuss/unsub  
>>> [ece...@gmail.com]
>>> -=-=-=-=-=-=-=-=-=-=-=-
>> 
>> -=-=-=-=-=-=-=-=-=-=-=-
>> Links: You receive all messages sent to this group.
>> 
>> View/Reply Online (#8446): 
>> https://lists.opendaylight.org/g/Discuss/message/8446
>> Mute This Topic: https://lists.opendaylight.org/mt/34547216/1964675
>> Group Owner: discuss+ow...@lists.opendaylight.org
>> Unsubscribe: https://lists.opendaylight.org/g/Discuss/unsub  
>> [mra...@gmail.com]
>> -=-=-=-=-=-=-=-=-=-=-=-
> 
> 
> 
> -- 
> M. Ranganathan

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#8452): https://lists.opendaylight.org/g/Discuss/message/8452
Mute This Topic: https://lists.opendaylight.org/mt/34547216/21656
Group Owner: discuss+ow...@lists.opendaylight.org
Unsubscribe: https://lists.opendaylight.org/g/Discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OpenDaylight Discuss] l2switch flow removal

[Luis Gomez]

FYI l2switch project is not maintained anymore (e.g. no committers left) so if 
you or anyone is interested in contributing to this project, I would recommend 
to consider becoming a maintainer for this project.

> On Oct 15, 2019, at 6:23 AM, asnake  wrote:
> 
> hi there, recently i have modified the l2switch code which combined reactive 
> and proactive lke hybrid, the want to to remove some proactive flows based on 
> packet statistics or bytes usage at some interval how do i do that?
> best regards, only hint is appreciated.
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> 
> View/Reply Online (#8444): 
> https://lists.opendaylight.org/g/Discuss/message/8444
> Mute This Topic: https://lists.opendaylight.org/mt/34547216/1217165
> Group Owner: discuss+ow...@lists.opendaylight.org
> Unsubscribe: https://lists.opendaylight.org/g/Discuss/unsub  
> [ece...@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#8446): https://lists.opendaylight.org/g/Discuss/message/8446
Mute This Topic: https://lists.opendaylight.org/mt/34547216/21656
Group Owner: discuss+ow...@lists.opendaylight.org
Unsubscribe: https://lists.opendaylight.org/g/Discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OpenDaylight Discuss] Noob question about Writing an Application for Open Day Light

[Luis Gomez]

Hi Dadepo, see my answers in-line:


> On Sep 30, 2019, at 6:18 AM, Dadepo Aderemi  wrote:
> 
> Hi,
> 
> I am working on a project related to SDN for a university project, and I am 
> new to Opendaylight in particular, and OpenFlow/SDN in general. So I need to 
> wrap my head around some fundamentals.
> 
> The first couple of questions I need help wrapping my head around is:
> 
> 1. How do I develop a controller application and integrate it with 
> OpenDayLight Controller?

You can see some examples of ODL applications in ODL git (most of the projects 
are SDN applications): https://git.opendaylight.org/gerrit/#/admin/projects/ 


You can see a description of every project here (note the projects in the upper 
diagram are fully active in ODL): 
https://wiki.opendaylight.org/view/Project_list 


Also to write new application you can check the archetype: 
https://docs.opendaylight.org/en/stable-sodium/developer-guide/developing-apps-on-the-opendaylight-controller.html
 

> 
> 2. How do I then set up the controller to communicate with a switch.
> 
> I found this link: "Developing Apps on the OpenDaylight controller": 
> https://docs.opendaylight.org/en/latest/developer-guide/developing-apps-on-the-opendaylight-controller.html
>  
> 
> 
> But it looks like the article is about how to have what seems like an 
> endpoint...and nothing about how to write application code, that learn from 
> the network and updates the flow tables.
> 
> Can anyone be kind enough to point me in the right direction? This will be 
> appreciated! Thanks!

Right, this is how to write an app from scratch in ODL, if you want to work on 
existing one (e.g. openflowplugin) I would recommend to contact the mail list 
for the project.

> 
>  
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> 
> View/Reply Online (#8443): 
> https://lists.opendaylight.org/g/Discuss/message/8443
> Mute This Topic: https://lists.opendaylight.org/mt/34479402/1217165
> Group Owner: discuss+ow...@lists.opendaylight.org
> Unsubscribe: https://lists.opendaylight.org/g/Discuss/unsub  
> [ece...@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#8445): https://lists.opendaylight.org/g/Discuss/message/8445
Mute This Topic: https://lists.opendaylight.org/mt/34479402/21656
Group Owner: discuss+ow...@lists.opendaylight.org
Unsubscribe: https://lists.opendaylight.org/g/Discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OpenDaylight Discuss] [release] OpenDaylight Mailing List Migration and Outage today

[Luis Gomez]

> On Sep 6, 2019, at 10:20 AM, Casey Cain  wrote:
> 
> Greetings, everyone!
> 
> This is a reminder that we are planning to migrate the existing mailing list 
> archives and user lists to Groups.io today at 14:00 Pacific Standard Time and 
> will conclude by 16:00. Please be aware pending memberships or posts (and 
> similar pending moderation actions) in Mailman will not be preserved in this 
> migration. We recommend re-checking for any such pending decisions and taking 
> action on them within Mailman one hour prior to the start of the migration 
> window.
> 
> During the migration window you will still be able to access the archives, 
> however the delivery of messages sent to the mailing lists during this window 
> will be delayed until after the migration of the archives and list members 
> are complete. We will turn off new list signups during the migration window, 
> then this functionality will be restored once it is complete.
> 
> * Note that to be subscribed to any project-specific lists such as the TSC, 
> discuss, dev, etc, you will need to be subscribed to the "Main" or annouce@ 
> mailing list.  The Main list will for community announcements only.

I guess this is for new subscription as existing are kept in the new tool. BTW 
is there written instructions on how to join a list or should we look in 
groups.io  portal?

> 
> If you’d like to learn more about using Groups.io, please reference their 
> help documentation. If you need assistance with Groups.io, please contact 
> support.linuxfoundation.org  → IT 
> Project Services
> 
> Regards,
> Casey Cain
> Technical Program Manager
> Linux Foundation
> _
> IRC - CaseyLF
> WeChat - okaru6
> ___
> release mailing list
> rele...@lists.opendaylight.org
> https://lists.opendaylight.org/mailman/listinfo/release

___
Discuss mailing list
Discuss@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/discuss

Re: [OpenDaylight Discuss] support | [REPORT] Review report_opendaylight_19-Q2.pdf (#57)

[Luis Gomez]

Luis Gomez commented:


Thanks for the report :)

-- 
Reply to this email directly or view it on GitLab: 
https://gitlab.com/Bitergia/c/OpenDayLight/support/issues/57#note_213639632
You're receiving this email because of your account on gitlab.com.


___
Discuss mailing list
Discuss@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/discuss

Re: [OpenDaylight Discuss] [controller-dev] Migrating inventory/topology models

[Luis Gomez]

I think in the case of OFP the work can be split in 2:

- Update topology model to last RFC (same as other projects in ODL). To me the 
sooner we can do this the better. This also may have reduced impact in OFP apps 
because the topology model contains very few data (e.g. no specific OFP 
extensions were added to original topology model)

- Migrate OFP inventory to topology. This will be more work and have more 
impact for sure because most (if not all) OFP apps look at the inventory for 
anything to do with OpenFlow. Now I am not sure what is the hurry here because 
inventory model is only used by OFP in ODL so at least there is no ODL 
integration concern AFAICT.

BR/Luis


> On Sep 5, 2019, at 11:19 AM, Robert Varga  wrote:
> 
> [+ discuss, mdsal-dev]
> 
> On 05/09/2019 19:24, Anil Vishnoi wrote:
>>As for the next steps, I think we need to migrate these models to
>>openflowplugin, where they can be maintained, as that world is the only
>>place that really uses them.
>> 
>> As far as upstream OpenDaylight is concern this make sense to me, but we
>> need to be careful about the downstream consumer. Downstream user who
>> just use core ODL projects (Controller, yangtools, mdsal,aaa) to develop
>> their standalone application might be using these models, so this
>> movement will break them and to solve this they will have to put
>> dependency on openflowpluing, which they might not want. 
> 
> That is a valid concern, yes.
> 
> The answer really lies in packaging, as if you are using karaf, you will
> have openflowplugin-features added to you distribution. Those would not
> be installed, but will bloat the distro & confuse the users.
> 
> On the other hand, every feature we build is a separate repository, so
> while you'd depend on openflowplugin-artifacts, you do not have to
> depend on openflowplugin-features -- I think.
> 
> Without Karaf, you depend on whatever you like, so yeah, you get tied up
> with OFP release cycle, but other than that there should not be a problem.
> 
> As far as those models are concerned, platform (mdsal/controller/netc)
> position on them can be summed up as:
> 
> Migrate to using ietf-network(-topology), which are shipped from MD-SAL
> for a year now. There are RFC8345 standard and are not expected to make
> in the foreseeable future.
> As a further note, while performing that migration, also move away from
> using yang-ext.yang routed RPCs by switching to YANG 1.1 actions. Such
> models are not supported by legacy RESTCONF (which itself is
> deprecated), but are fully supported by RFC8040 RESTCONF (which is the
> only actively supported version).
> 
> On a related note, this discussion will also be coming up with relation to:
> 
> ietf-packet-fields
> ietf-access-control-list
> ietf-lisp-address-types
> ietf-ted
> ietf-topology
> ietf-topology-isis
> ietf-topology-l3-unicast-igp
> ietf-topology-ospf
> 
> as MD-SAL will be gradually dropping at least those, which have been
> superseded by RFCs.
> 
> Regards,
> Robert
> 
> ___
> Discuss mailing list
> Discuss@lists.opendaylight.org
> https://lists.opendaylight.org/mailman/listinfo/discuss

___
Discuss mailing list
Discuss@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/discuss

Re: [OpenDaylight Discuss] [release] [OpenDaylight Marketing] Seeking LFN Booth Demo Ideas for ONS Europe: ODL Marketing

[Luis Gomez]

Sorry I did not find the time to explain this demo in detail. Anyway and FYI 
the demo has not been selected, I really hope other demos will show ODL at ONS 
Europe.

BR/Luis


> On Jul 25, 2019, at 8:51 AM, Luis Gomez  wrote:
> 
> Hi all,
> 
> We talked about this and we are ready to submit this demo for the ODL booth. 
> I can explain the demo idea in today's TSC or in another call if required.
> 
> BR/Luis
> 
> 
> 
> 
> 
> 
> 
>> On Jul 17, 2019, at 7:59 PM, Abhijit Kumbhare > <mailto:abhijitk...@gmail.com>> wrote:
>> 
>> Fyi.
>> 
>> -- Forwarded message -
>> From: Brandon Wick > <mailto:bw...@linuxfoundation.org>>
>> Date: Thu, Jul 11, 2019 at 8:39 AM
>> Subject: [OpenDaylight Marketing] Seeking LFN Booth Demo Ideas for ONS 
>> Europe: ODL Marketing
>> To: > <mailto:market...@lists.opendaylight.org>>
>> 
>> 
>> LFN Community:
>> 
>> We hope that you are planning to attend ONS Europe, September 23-25, in 
>> Antwerp, Belgium 
>> <https://events.linuxfoundation.org/events/open-networking-summit-europe-2019/>.
>>  Those in attendance at the last three ONS events will recall that we hosted 
>> an LF Networking Booth that showcased 8-10 compelling, community-driven 
>> demos from the LFN technical projects. See this blog post 
>> <https://www.linuxfoundation.org/blog/2019/03/community-demos-at-ons-to-highlight-lfn-project-harmonization-and-more/>
>>  from ONS North America last April to learn more about the opportunity. 
>> 
>> We wanted to reach out now to each of the LFN project communities to let you 
>> know that there will be space for 8-10 networking demos inside the LFN booth 
>> again at ONS Europe and we are seeking demoideas using the same process. Our 
>> goal is to show compelling uses of LFN networking project technology to 
>> solve real world industry challenges.
>> 
>> Demos that show cross-project elements (e.g. between LFN projects and other 
>> networking projects), that map to a specific industry use case, or are 
>> endorsed by a service provider are preferred. That said, we have some room 
>> for demos that highlight the good work and value-add from projects that 
>> don't necessarily meet these criteria. At least one demo slot will be made 
>> available for each LFN project (FD.io <http://fd.io/>, ONAP, ODL, OPNFV, 
>> PNDA, SNAS, Tungsten Fabric) that submits a quality idea.  
>> 
>> Demos stations will again have storage space, a counter, backdrop, monitor, 
>> power, and Wi-Fi internet provided. There is no cost to host a standard demo 
>> in the LFN booth although additional power, internet, space, etc. may incur 
>> a cost. 
>> 
>> Here are the key dates to keep in mind:
>> July 10: Demo idea solicitation email sent to community lists
>> July 31: Demo ideas submissions due
>> August 14: Demos ideas reviewed, chosen, and notifications sent
>> September 23-25: Demos shown at ONS
>> To submit your demo idea for consideration, please collect and provide the 
>> following information:
>> Demo title (10 words max)
>> Brief demo description (200 words max)
>> List of demo manager(s) with contact information 
>> List of open source projects involved
>> List of companies involved
>> Any extra requirements or special considerations
>> Demo manager responsibilities include:
>> Creating the demo concept and actual demo to be shown
>> Responding promptly to requests for information
>> Meeting all demo preparation deadlines
>> Setting up and testing the demo pre-show and taking down post-show
>> Staffing the demo during ONS expo hours (along with other designated team 
>> members to help share the load)
>> Being willing to participate in media activities, e.g. photos, videos
>> ONS sponsor companies are of course welcome to host demos in their booths on 
>> the show floor as well. Please check with your ONS sponsorship manager to 
>> explore these opportunities. 
>> 
>> Submit your demo ideas by July 31st by sending an email to 
>> bw...@linuxfoundation.org <mailto:bw...@linuxfoundation.org>. LFN staff 
>> leadership (Heather, Arpit) will then review the submissions, get back to 
>> submitters with questions/suggestions if needed, and recommend a final demo 
>> roster by August 14th. Send any questions you may have to 
>> bw...@linuxfoundation.org <mailto:bw...@linuxfoundation.org>.
>> 
>> We look forward to seeing your demo ideas.
>> 
>> Best,
>> 
>> Brandon Wick
>> Senior Integrated Ma

Re: [OpenDaylight Discuss] [release] [OpenDaylight Marketing] Seeking LFN Booth Demo Ideas for ONS Europe: ODL Marketing

[Luis Gomez]

I guess the file was to big, here is a link to the google doc: 
https://docs.google.com/presentation/d/1Mrvp5c0nyNYBXlpnbG4bP4risfNyjlZwYYwi7G9ldFM
 
<https://docs.google.com/presentation/d/1Mrvp5c0nyNYBXlpnbG4bP4risfNyjlZwYYwi7G9ldFM>


> On Jul 25, 2019, at 8:51 AM, Luis Gomez  wrote:
> 
> Hi all,
> 
> We talked about this and we are ready to submit this demo for the ODL booth. 
> I can explain the demo idea in today's TSC or in another call if required.
> 
> BR/Luis
> 
> 
> 
> 
> 
> 
> 
>> On Jul 17, 2019, at 7:59 PM, Abhijit Kumbhare > <mailto:abhijitk...@gmail.com>> wrote:
>> 
>> Fyi.
>> 
>> -- Forwarded message -
>> From: Brandon Wick > <mailto:bw...@linuxfoundation.org>>
>> Date: Thu, Jul 11, 2019 at 8:39 AM
>> Subject: [OpenDaylight Marketing] Seeking LFN Booth Demo Ideas for ONS 
>> Europe: ODL Marketing
>> To: > <mailto:market...@lists.opendaylight.org>>
>> 
>> 
>> LFN Community:
>> 
>> We hope that you are planning to attend ONS Europe, September 23-25, in 
>> Antwerp, Belgium 
>> <https://events.linuxfoundation.org/events/open-networking-summit-europe-2019/>.
>>  Those in attendance at the last three ONS events will recall that we hosted 
>> an LF Networking Booth that showcased 8-10 compelling, community-driven 
>> demos from the LFN technical projects. See this blog post 
>> <https://www.linuxfoundation.org/blog/2019/03/community-demos-at-ons-to-highlight-lfn-project-harmonization-and-more/>
>>  from ONS North America last April to learn more about the opportunity. 
>> 
>> We wanted to reach out now to each of the LFN project communities to let you 
>> know that there will be space for 8-10 networking demos inside the LFN booth 
>> again at ONS Europe and we are seeking demoideas using the same process. Our 
>> goal is to show compelling uses of LFN networking project technology to 
>> solve real world industry challenges.
>> 
>> Demos that show cross-project elements (e.g. between LFN projects and other 
>> networking projects), that map to a specific industry use case, or are 
>> endorsed by a service provider are preferred. That said, we have some room 
>> for demos that highlight the good work and value-add from projects that 
>> don't necessarily meet these criteria. At least one demo slot will be made 
>> available for each LFN project (FD.io <http://fd.io/>, ONAP, ODL, OPNFV, 
>> PNDA, SNAS, Tungsten Fabric) that submits a quality idea.  
>> 
>> Demos stations will again have storage space, a counter, backdrop, monitor, 
>> power, and Wi-Fi internet provided. There is no cost to host a standard demo 
>> in the LFN booth although additional power, internet, space, etc. may incur 
>> a cost. 
>> 
>> Here are the key dates to keep in mind:
>> July 10: Demo idea solicitation email sent to community lists
>> July 31: Demo ideas submissions due
>> August 14: Demos ideas reviewed, chosen, and notifications sent
>> September 23-25: Demos shown at ONS
>> To submit your demo idea for consideration, please collect and provide the 
>> following information:
>> Demo title (10 words max)
>> Brief demo description (200 words max)
>> List of demo manager(s) with contact information 
>> List of open source projects involved
>> List of companies involved
>> Any extra requirements or special considerations
>> Demo manager responsibilities include:
>> Creating the demo concept and actual demo to be shown
>> Responding promptly to requests for information
>> Meeting all demo preparation deadlines
>> Setting up and testing the demo pre-show and taking down post-show
>> Staffing the demo during ONS expo hours (along with other designated team 
>> members to help share the load)
>> Being willing to participate in media activities, e.g. photos, videos
>> ONS sponsor companies are of course welcome to host demos in their booths on 
>> the show floor as well. Please check with your ONS sponsorship manager to 
>> explore these opportunities. 
>> 
>> Submit your demo ideas by July 31st by sending an email to 
>> bw...@linuxfoundation.org <mailto:bw...@linuxfoundation.org>. LFN staff 
>> leadership (Heather, Arpit) will then review the submissions, get back to 
>> submitters with questions/suggestions if needed, and recommend a final demo 
>> roster by August 14th. Send any questions you may have to 
>> bw...@linuxfoundation.org <mailto:bw...@linuxfoundation.org>.
>> 
>> We look forward to seeing your demo ideas.
>> 
&

Re: [OpenDaylight Discuss] Future OpenDaylight Developer Forms

[Luis Gomez]

Actually that is a good point, provided these 2 events are separated 5 months I 
do not see problem in attending to both, the conflict will be between 
ONAP/OPNFV in February and ONS NA in March(?) next year.

BR/Luis


> On Jun 22, 2019, at 2:00 AM, Robert Varga  wrote:
> 
> Both, each with different primary focus (given the timeframe rel. SR):
> 
> - ONS EU: Magnesium deliverables, project-wide activities syncup
> - other: Feb 2020 Magnesium final push/post-mortem, Aluminium project
> planning
> 
> I would also like to see if we can get hackathons during these...
> 
> Regards,
> Robert
> 
> 
> On 20/06/2019 18:32, Casey Cain wrote:
>> Hello, everyone.
>> 
>> OpenDaylight is trying to finalize our plans for the next Developer
>> Design Forum.  We are currently faced with 3 options.
>> 
>> 1. At ONS EU
>> 1. Antwerp, Belgium 
>> 2. 26th - 27th (Thrus/Fri), September 2019.
>> 2. Jointly with ONAP/OPNFV
>> 1. Currently unknown location
>> 2. January / February 2020 time frame
>> 3. Both.
>> 
>> We need to urgently come to a decision so that organizations can plan
>> their travel budgets.  Please reply with your comments and vote as soon
>> as possible.
>> 
>> Best, 
>> Casey Cain
>> Technical Program Manager
>> Linux Foundation
>> _
>> IRC - CaseyLF
>> WeChat - okaru6
>> 
>> ___
>> Discuss mailing list
>> Discuss@lists.opendaylight.org
>> https://lists.opendaylight.org/mailman/listinfo/discuss
>> 
> 
> ___
> Discuss mailing list
> Discuss@lists.opendaylight.org 
> https://lists.opendaylight.org/mailman/listinfo/discuss 
> 
___
Discuss mailing list
Discuss@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/discuss

Re: [OpenDaylight Discuss] #OpenDaylight-help-openflow

[Luis Gomez]

Hi Santiago,

It would help if you post the controller OpenFlow REST request + the switch 
flow dump + explain why the behavior is not the expected.

BR/Luis


> On Jun 10, 2019, at 7:08 AM, Santiago Bentancur 
>  wrote:
> 
> Hello 
> 
>  I am a student of the Udelar engineering faculty, who is studying 
> Opendaylight. I am trying to configure the flow tables of some switches 
> created with mininet. After using put requests, I was able to configure the 
> switches, for that I used the command dpctl dump-flows -O OpenFlow13 and they 
> were actually configured, however they do not do what was configured. I do 
> not know what the problem may be, maybe you had a similar problem.
> Regards,
> Santiago
> ___
> Discuss mailing list
> Discuss@lists.opendaylight.org
> https://lists.opendaylight.org/mailman/listinfo/discuss

___
Discuss mailing list
Discuss@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/discuss

Re: [OpenDaylight Discuss] [opendaylight-dev] TSC Meeting Minutes April 18, 2019

[Luis Gomez]

As discussed in the meeting I have updated internship page with a total of 3 
projects for Sodium release:

https://wiki.opendaylight.org/view/Interns/Projects 


Any interested mentor please add your project too.

BR/Luis

> On Apr 18, 2019, at 4:06 PM, Abhijit Kumbhare  wrote:
> 
> 
> https://meetings.opendaylight.org/opendaylight-meeting/2019/tsc/opendaylight-meeting-tsc.2019-04-18-16.01.html
>  
> 
> 
> 
> ___
> dev mailing list
> d...@lists.opendaylight.org
> https://lists.opendaylight.org/mailman/listinfo/dev

___
Discuss mailing list
Discuss@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/discuss

Re: [OpenDaylight Discuss] [Aaa-dev] Removal of IdP component from AAA

[Luis Gomez]

Hi Robert,

Can you please explain the impact of this? e.g. can we for instance change the 
default user admin/admin or use token authentication after this change?

BR/Luis


> On Mar 21, 2019, at 4:50 AM, Robert Varga  wrote:
> 
> Hello everyone,
> 
> as part of keeping OpenDaylight infrastructure secure and relevant, we
> will be removing OAuth2 Identity Provider component from the AAA project.
> 
> There are three technical drivers behind this decision:
> 
> 1) current implementation is based on Apache Oltu, which has been
> terminated on March 21st, 2018 and moved to Attic:
> https://attic.apache.org/projects/oltu.html
> 
> 2) Oltu depends on org.json/json, which has a problematic license
> (https://www.json.org/license.html)
> 
> 3) we do not strive to be an IdP, as there are plenty solutions
> available out there.
> 
> The details are in the tracker issue,
> https://jira.opendaylight.org/browse/AAA-173, and in the removal patch,
> https://git.opendaylight.org/gerrit/72022.
> 
> Should there be interest in having this functionality present, we will
> gladly accept an alternative implementation, provided it comes with at
> least a minimal commitment to support it.
> 
> Regards,
> Robert
> 
> ___
> aaa-dev mailing list
> aaa-...@lists.opendaylight.org
> https://lists.opendaylight.org/mailman/listinfo/aaa-dev

___
Discuss mailing list
Discuss@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/discuss

Re: [OpenDaylight Discuss] [release] Can't do merge in snmp4sdn stable/neon branch

[Luis Gomez]

Hi Anil, AFAIR Self-Managed projects are not affected by milestones, so I think 
it should be OK to open the branch.

> On Feb 18, 2019, at 4:58 AM, Anil Belur  wrote:
> 
> Hi Christine: 
> 
> 'stable/neon' branch is locked for the upcoming release. Any changes that 
> need to be merged must be approved by TSC and release manager.
> 
> Thanks,
> Anil
> 
> On Mon, Feb 18, 2019 at 9:24 PM  > wrote:
> Hi,
> 
>  
> 
> For snmp4sdn stable/neon branch, the gerrit 
> https://git.opendaylight.org/gerrit/#/c/80277/ 
>  has been built successfully, 
> but no “merge” button appears. Does the branch been frozen??
> 
>  
> 
> Thanks!
> 
> Best regards,
> 
> Christine
> 
>  
> 
> 
> 
> --
> 本信件可能包含工研院機密資訊，非指定之收件者，請勿使用或揭露本信件內容，並請銷毀此信件。 This email may contain 
> confidential information. Please do not use or disclose it in any way and 
> delete it if you are not the intended recipient.
> ___
> release mailing list
> rele...@lists.opendaylight.org 
> https://lists.opendaylight.org/mailman/listinfo/release 
> 
> ___
> Discuss mailing list
> Discuss@lists.opendaylight.org
> https://lists.opendaylight.org/mailman/listinfo/discuss

___
Discuss mailing list
Discuss@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/discuss

Re: [OpenDaylight Discuss] Remote Netopeer2-server configuration

[Luis Gomez]

Hi Masoud,

Best list for this question is: netconf-...@lists.opendaylight.org

Please try with Fluorine SR2 candidate: 
https://nexus.opendaylight.org/content/repositories//autorelease-2686/org/opendaylight/integration/karaf/0.9.2/karaf-0.9.2.zip
 as I think the issue you describe may be fixed there.

BR/Luis



> On Feb 5, 2019, at 1:59 AM, Masoud Hemmatpour (mhemmatp)  
> wrote:
> 
> Hello,
> 
> I appreciate if you consider my question. If I am posting to the wrong 
> mailing list please let mew know. 
> 
> Something that I noticed from my issues is that the ODL remove the nested 
> namespaces from my xml body. 
> 
> Please, let me know how can I solve this issue.
> 
> Kind Regards,
> Thanks,
> 
>> On 31 Jan 2019, at 13:14, Masoud Hemmatpour (mhemmatp)  
>> wrote:
>> 
>> Hello all,
>> 
>>  I am a newbie to OpenDaylight. I am going to configure an interface through 
>> the RESTAPI. Here it is my following API:
>> 
>> http://localhost:8181/restconf/operations/network-topology:network-topology/topology/topology-netconf/node/new-netconf-device/yang-ext:mount/ietf-netconf:edit-config
>> 
>> And here it is my xml body:
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> host-vpp1out
>> Ethernet
>> > xmlns:ianaift="urn:ietf:params:xml:ns:yang:iana-if-type">ianaift:ethernetCsmacd
>> 
>> true
>>   
>> 172.16.137.165
>> 24
>>   
>> 
>>   
>> 
>> 
>> 
>> 
>> I receive an error from netopeer2-server in which Request could not be 
>> completed because the requested operation is not supported by this 
>> implementation.  
>> 
>> Thank you,
>> Kind Regards,
> 
> ___
> Discuss mailing list
> Discuss@lists.opendaylight.org
> https://lists.opendaylight.org/mailman/listinfo/discuss

___
Discuss mailing list
Discuss@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/discuss

Re: [OpenDaylight Discuss] [OpenDaylight TSC] Fwd: [OpenDaylight Marketing] Seeking LFN Booth Demo Ideas for ONS North America

[Luis Gomez]

Sounds good to me, just to be clear this process does not prevent an individual 
contributor or company to submit its own idea directly to LFN, but at least by 
doing this we can secure one ODL broad community coming proposal.

> On Jan 18, 2019, at 11:24 AM, Abhijit Kumbhare  wrote:
> 
> Yes - I was also thinking we should have a meeting about this or discuss it 
> in the TSC meeting. We can have the following:
> Step 1) a quick discussion on this in next week TSC meeting (Jan 24)
> Step 2) let folks go back to think about demo ideas, send their proposals to 
> the TSC/release mailing lists (and have a wiki or google doc for each 
> proposal) and have folks present their demo ideas in the TWS session on Feb 
> 4th - and also collaborate
> Step 3) If there are multiple ideas - we can rank them from the ODL 
> perspective in the TSC meeting on Feb 7. 
> Step 4) Further fine tuning discussion/collaboration in the TWS of Feb 11 & 
> then the TSC actually submit ALL the proposals (with ODL ranking/priority) to 
> Brandon Wick of LF Marketing before the deadline of Feb 13 
> 
> That way we have good demo proposals from OpenDaylight - and its coming from 
> the overall OpenDaylight community rather than individual contributors. I 
> think we should send all the proposals - but as a community we should also 
> rank them if possible.
> 
> Does that sound like a fair approach? 
> 
> On Fri, Jan 18, 2019 at 11:04 AM Luis Gomez  <mailto:ece...@gmail.com>> wrote:
> I remember last time there was some last minute miss-coordination for the ODL 
> booth demo. So for this time: can we come up with a joint proposal from the 
> ODL partners? If not can we at least know in advance which ODL partners plan 
> to submit demo idea?
> 
> 
>> On Jan 18, 2019, at 9:37 AM, Abhijit Kumbhare > <mailto:abhijitk...@gmail.com>> wrote:
>> 
>> 
>> 
>> -- Forwarded message -
>> From: Brandon Wick > <mailto:bw...@linuxfoundation.org>>
>> Date: Wed, Jan 16, 2019 at 10:57 PM
>> Subject: [OpenDaylight Marketing] Seeking LFN Booth Demo Ideas for ONS North 
>> America
>> To: 
>> 
>> 
>> LFN Community:
>> 
>> Those in attendance at OSN North America in Los Angeles last March and ONS 
>> Europe in Amsterdam last September will recall that we hosted an LF 
>> Networking Booth that showcased 8-10 compelling, community-driven demos from 
>> the LFN technical projects. See this blog post 
>> <https://www.linuxfoundation.org/blog/rubber-meet-road-x-project-collaboration-demos-ons/>
>>  for a description of the ONS North America booth demos, and this blog post 
>> <https://www.linuxfoundation.org/blog/2018/08/building-in-the-open-ons-europe-demos-highlight-networking-industry-collaboration/>
>>  for the ONS Europe demos.
>> 
>> We wanted to reach out now to each of the LFN project communities to let you 
>> know that there will be space for 8-10 networking demos inside the LFN booth 
>> again at ONS North America (San Jose, April 4-6) and we are seeking demo 
>> ideas using the same process. Our goal is to show compelling uses of LFN 
>> networking project technology to solve real world industry challenges.
>> 
>> Demos that show cross-project elements (e.g. between LFN projects and other 
>> networking projects), that map to a specific industry use case, or are 
>> endorsed by a service provider are preferred. That said, we have some room 
>> for demos that highlight the good work and value-add from projects that 
>> don't necessarily meet these criteria. At least one demo slot will be made 
>> available for each LFN project (FD.io <http://fd.io/>, ONAP, ODL, OPNFV, 
>> PNDA, SNAS, Tungsten Fabric) that submits a quality idea.  
>> 
>> Demos stations will again have storage space, a counter, backdrop, monitor, 
>> power, and Wi-Fi internet provided. There is no cost to host a demo in the 
>> LFN booth although additional power, internet, space, etc. may incur a cost. 
>> 
>> Here are the key dates to keep in mind:
>> Jan 16: Demo idea solicitation email sent to community lists
>> Feb 13: Demo ideas submissions due
>> Feb 27: Demos ideas reviewed, chosen, and notifications sent
>> April 4-6: Demos shown
>> To submit your demo idea for consideration, please collect and provide the 
>> following information:
>> Demo title (10 words max)
>> Brief demo description (200 words max)
>> List of demo manager(s) with contact information 
>> List of open source projects involved
>> List of companies involved
>> Any extra requirements or special considerations
>> Demo manager resp

Re: [OpenDaylight Discuss] [OpenDaylight TSC] Fwd: [OpenDaylight Marketing] Seeking LFN Booth Demo Ideas for ONS North America

[Luis Gomez]

I remember last time there was some last minute miss-coordination for the ODL 
booth demo. So for this time: can we come up with a joint proposal from the ODL 
partners? If not can we at least know in advance which ODL partners plan to 
submit demo idea?


> On Jan 18, 2019, at 9:37 AM, Abhijit Kumbhare  wrote:
> 
> 
> 
> -- Forwarded message -
> From: Brandon Wick  >
> Date: Wed, Jan 16, 2019 at 10:57 PM
> Subject: [OpenDaylight Marketing] Seeking LFN Booth Demo Ideas for ONS North 
> America
> To: 
> 
> 
> LFN Community:
> 
> Those in attendance at OSN North America in Los Angeles last March and ONS 
> Europe in Amsterdam last September will recall that we hosted an LF 
> Networking Booth that showcased 8-10 compelling, community-driven demos from 
> the LFN technical projects. See this blog post 
> 
>  for a description of the ONS North America booth demos, and this blog post 
> 
>  for the ONS Europe demos.
> 
> We wanted to reach out now to each of the LFN project communities to let you 
> know that there will be space for 8-10 networking demos inside the LFN booth 
> again at ONS North America (San Jose, April 4-6) and we are seeking demo 
> ideas using the same process. Our goal is to show compelling uses of LFN 
> networking project technology to solve real world industry challenges.
> 
> Demos that show cross-project elements (e.g. between LFN projects and other 
> networking projects), that map to a specific industry use case, or are 
> endorsed by a service provider are preferred. That said, we have some room 
> for demos that highlight the good work and value-add from projects that don't 
> necessarily meet these criteria. At least one demo slot will be made 
> available for each LFN project (FD.io, ONAP, ODL, OPNFV, PNDA, SNAS, Tungsten 
> Fabric) that submits a quality idea.  
> 
> Demos stations will again have storage space, a counter, backdrop, monitor, 
> power, and Wi-Fi internet provided. There is no cost to host a demo in the 
> LFN booth although additional power, internet, space, etc. may incur a cost. 
> 
> Here are the key dates to keep in mind:
> Jan 16: Demo idea solicitation email sent to community lists
> Feb 13: Demo ideas submissions due
> Feb 27: Demos ideas reviewed, chosen, and notifications sent
> April 4-6: Demos shown
> To submit your demo idea for consideration, please collect and provide the 
> following information:
> Demo title (10 words max)
> Brief demo description (200 words max)
> List of demo manager(s) with contact information 
> List of open source projects involved
> List of companies involved
> Any extra requirements or special considerations
> Demo manager responsibilities include:
> Creating the demo concept and actual demo to be shown
> Responding promptly to requests for information
> Meeting all demo preparation deadlines
> Setting up and testing the demo pre-show and taking down post-show
> Staffing the demo during ONS expo hours (along with other designated team 
> members to help share the load)
> Being willing to participate in media activities, e.g. photos, videos
> ONS sponsor companies are of course welcome to host demos in their booths on 
> the show floor as well. Please check with your ONS sponsorship manager to 
> explore these opportunities. 
> 
> Submit your demo ideas by February 13 by sending an email to 
> bw...@linuxfoundation.org . LFN staff 
> leadership (Heather, Phil, Arpit) will then review the submissions, get back 
> to submitters with questions, suggestions, and recommend a final demo roster 
> by Feb 27th. Send any questions you may have to bw...@linuxfoundation.org 
> .
> 
> We look forward to seeing your demo ideas.
> 
> Best,
> 
> Brandon Wick
> Senior Integrated Marketing Manager
> The Linux Foundation
> bw...@linuxfoundation.org 
> +1.917.282.0960
> 
> ___
> marketing mailing list
> market...@lists.opendaylight.org 
> https://lists.opendaylight.org/mailman/listinfo/marketing 
> 
> ___
> TSC mailing list
> t...@lists.opendaylight.org
> https://lists.opendaylight.org/mailman/listinfo/tsc

___
Discuss mailing list
Discuss@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/discuss

Re: [OpenDaylight Discuss] Performance test with Cbench

[Luis Gomez]

Hi Vinod, for datastore flow push test we use different application called 
bulkomatic:

https://github.com/opendaylight/openflowplugin/blob/master/applications/bulk-o-matic/src/site/asciidoc/bulk-o-matic.adoc

Some tests running this:

https://jenkins.opendaylight.org/releng/view/openflowplugin/job/openflowplugin-csit-1node-perf-bulkomatic-only-fluorine/plot/Java%20Performance/
 

https://jenkins.opendaylight.org/releng/view/openflowplugin/job/openflowplugin-csit-3node-clustering-perf-bulkomatic-only-fluorine/plot/Java%20Performance/
 


BR/Luis

> On Dec 11, 2018, at 6:12 AM, Vinod Ramachandra  
> wrote:
> 
> Hello All,
> I hope this is the right place to ask about a query of mine related to usage 
> of ODL with Cbench.  
> 
> Issue:
> ODL drop-test app is generating very few FLOW_MODs per second(~30 Flow_Mod 
> per second)
> 
> Setup: 
> I'm running Opendaylight against Cbench. After going thorugh many of the 
> previous posts on cbench, I have insatlled the following features on ODL.
> Features:
> 1. "odl-openflowplugin-southbound",
> 2. "odl-openflowplugin-flow-services",
> 3. "odl-openflowplugin-app-table-miss-enforcer",
> 4. "odl-openflowplugin-app-forwardingrules-sync",
> 5. "odl-openflowplugin-drop-test",
> 
> I have set dropallpackets on. Cbench is run in latency mode. ODL is able to 
> respond to very few Packet_Ins per second(~30 packet_in per sec). The 
> Integration_Group's Performance_Tests#Known_Issues indicate that 
> dropallpackets doesnot work well and flows get hung after a while. However it 
> seems to be old report of Performance tests. 
> Could someone please confirm if the issue of dropallpackets still exists? Or 
> Please share some more setup information related to above scenario.
> 
> 
> 
> P.S: I understand that dropallpacketsrpc on could be used to bypass the 
> datastore and get the FLOW_MODs. I have tested this and dropallpacketsrpc is 
> working fine. However i would like to get the datastore involved while 
> responding to PACKET_INs. 
> 
> 
> Thanks,
> Vinod
> ___
> Discuss mailing list
> Discuss@lists.opendaylight.org
> https://lists.opendaylight.org/mailman/listinfo/discuss

___
Discuss mailing list
Discuss@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/discuss

Re: [OpenDaylight Discuss] ODL l2switch flow entries - reactive flows

[Luis Gomez]

Hi Thushar, see my answers below...

> On Dec 2, 2018, at 10:20 PM, Thushar Prakash  
> wrote:
> 
> Hi,
> 
> I am new to ODL and I couldn't find a users mailing list. I hope this is the 
> right one.
>   
> I was trying to do an experiment with the ODL controller and mininet. I 
> needed reactive flows and since l2switch was not included in the latest 
> fluorine release I used Carbon instead, for now.

FYI oxygen is last release with l2switch.

> This is the topology that I am using for my experiment.
> 
> <02-hostsfound.png>
> But the flow table entries for the  OVS switch in mininet was (for switch 
> OpenFlow:1):
> 
> 
> NXST_FLOW reply (xid=0x4):
>  cookie=0x2b02, duration=30.63s, table=0, n_packets=0, n_bytes=0, 
> idle_age=30, priority=2,in_port=3 actions=output:2,output:1   
>  
>  cookie=0x2b01, duration=30.633s, table=0, n_packets=0, 
> n_bytes=0, idle_age=30, priority=2,in_port=1 
> actions=output:2,output:3,CONTROLLER:65535  
>  cookie=0x2b00, duration=30.636s, table=0, n_packets=0, 
> n_bytes=0, idle_age=30, priority=2,in_port=2 actions=output:1,output:3
>
>  cookie=0x2b04, duration=36.03s, table=0, n_packets=14, 
> n_bytes=1190, idle_age=4, priority=100,dl_type=0x88cc 
> actions=CONTROLLER:65535   
>  cookie=0x2b04, duration=36.03s, table=0, n_packets=0, n_bytes=0, 
> idle_age=36, priority=0 actions=drop
> 
> It seems that the packets are being flooded to all the other ports all the 
> time. At first, I thought it was for LLDP packets, but the flow entries are 
> not changing even after sending traffic between the hosts and even after 
> removing one of the paths from host1 to host2.

Flood flows are installed by default to broadcast any incoming traffic to all 
ports and controller (to discover hosts). Once hosts are discovered you should 
see MAC-to-MAC flows on top of the existing flood flows. This behavior is very 
similar to a real switch where known MAC traffic gets unicast forwarded ed 
while BUM traffic is broadcasted.


> The main requirement for me is that we get a traffic matrix and that the 
> connectivity retains even after links are switched off. But here the traffic 
> through all the other ports will be the same for a  switch and thus can't 
> find the way traffic is behaving. 

If something does not work after link/node goes down, this may be a bug or some 
limitation in the l2switch.

> 
>  Am I doing something wrong or is there some configuration in the l2switch 
> feature that I need to change? 
I do not think you are doing wrong, anyway here is the l2switch config setting 
for reference: 
https://docs.opendaylight.org/en/stable-oxygen/user-guide/l2switch-user-guide.html

> ODL being a well-known controller is there any other way by which we can 
> achieve reactive flows (other than using l2switch).
You can try the VTN project: 
https://docs.opendaylight.org/en/stable-oxygen/user-guide/virtual-tenant-network-(vtn).html

> PS: Where do I begin if I wanted to get involved in the development and get 
> the l2switch feature for a later release of ODL.  

Today the l2switch project is abandoned, if you really have cycles to revive it 
I would suggest to submit a proposal in 
https://wiki.opendaylight.org/view/Project_Proposals:Main 
 so once it gets 
approved you can get committers rights to push code.

> 
> ___
> Discuss mailing list
> Discuss@lists.opendaylight.org
> https://lists.opendaylight.org/mailman/listinfo/discuss

___
Discuss mailing list
Discuss@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/discuss

Re: [OpenDaylight Discuss] Is there something that can replace yangman?

[Luis Gomez]

Hi Wang,

FYI yangman, dlux and some other projects are discontinued because lack of 
community support. If you or anyone is interested in contributing in this 
please feel free to do so.

Regarding the issue with apidocs, do you mind open a bug in our jira system 
(project=netconf)?

Thanks/Luis

> On Sep 29, 2018, at 11:57 PM,  
>  wrote:
> 
> 
> 
> Hi, all
>  As far as I know the yangman has been discarded after Oxygen release, is 
> there anything else to replace it, 
> or now only use apidocs? By the way, I find the apidocs also no longer 
> provide input body template functionality 
> after Oxygen(That is, the model schema function that we only need to change 
> the value on the page.), so it is not 
> easy to use at all.
> 
> 
> 
> 
> Best Regards!
> 
> Wang Senxiao
> 
> 
> ___
> Discuss mailing list
> Discuss@lists.opendaylight.org
> https://lists.opendaylight.org/mailman/listinfo/discuss

___
Discuss mailing list
Discuss@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/discuss

Re: [OpenDaylight Discuss] [opendaylight-dev][release] OpenDaylight Fluorine released

[Luis Gomez]

Thanks Anil :)

> On Aug 30, 2018, at 7:11 PM, Anil Belur  wrote:
> 
> On Friday 31 August 2018 12:25 AM, Anil Belur wrote:
>> Hello All,
>> 
>> OpenDaylight Fluorine is released and will be available at the URL's
>> provided here [0].
>> 
>> Nexus is still copying files over but should appear in the next few hours.
>> 
>> We are working on Version Bumping of the stable/fluorine and will update
>> again once that completes.
>> 
>> Thanks to everyone for contributing to the release.
>> 
>> Regards,
>> Anil Belur
>> 
>> [0.] https://docs.opendaylight.org/en/latest/downloads.html
>> 
> Tagging and version Bumping of the OpenDaylight Fluorine release is
> complete. Please resume development on the 'stable/fluorine' branch,
> the branch is now unlocked.
> 
> - Anil
> 
> ___
> Discuss mailing list
> Discuss@lists.opendaylight.org 
> https://lists.opendaylight.org/mailman/listinfo/discuss 
> 
___
Discuss mailing list
Discuss@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/discuss

Re: [OpenDaylight Discuss] ODL in Reactive Mode

[Luis Gomez]

Hi Eray,

See my answer on 
https://stackoverflow.com/questions/51484495/how-to-run-opendaylight-in-reactive-mode/
 


BR/Luis


> On Jul 24, 2018, at 5:34 AM, Eray Guven  wrote:
> 
> I use Opendaylight Nitrogen and it runs in proactive mode as default. Yet, 
> somehow I couldnt find a clue for how to make it work in reactive mode.I 
> think probably I need to edit some l2switch maven repos such as arphandler. 
> Is it possible to make a RESTCONF request to disable proactive mode of L2 
> Switch ?
> 
> The reason to do is I try to capture FLOW_MOD messages after seeing 
> PACKET_IN. 
> 
> I appreciate any kind of help. Thank you.
> 
> 
> ___
> Discuss mailing list
> Discuss@lists.opendaylight.org
> https://lists.opendaylight.org/mailman/listinfo/discuss

___
Discuss mailing list
Discuss@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/discuss

Re: [OpenDaylight Discuss] [controller-dev] Sprint to talk at today's TWS

[Luis Gomez]

Hi Lyle,

Just 1 question: I remember you mentioned something about controller 
performance being the issue or bottleneck in your use case, if that is correct 
did you perform any java profiling? and if so can you share which thread/s used 
most of CPU cycles?

BR/Luis

> On Jul 9, 2018, at 12:23 PM, Bertz, Lyle T [CTO]  
> wrote:
> 
> We took a look at HoneyComb but wanted to give ODL the benefit of the doubt 
> so we attempted to use all of it. However, after ~4 implementations of the 
> FPC Agent we have arrived to the same conclusion as Honeycomb with the only 
> difference being persistence and upgraded transport (and the 
> application/service in question of course!).
>  
>  
>  
>  
>  
> From: Luis Gomez [mailto:ece...@gmail.com <mailto:ece...@gmail.com>] 
> Sent: Monday, July 09, 2018 2:08 PM
> To: Casey Cain  <mailto:cc...@linuxfoundation.org>>; Bertz, Lyle T [CTO] 
> mailto:lyle.t.be...@sprint.com>>
> Cc: discuss  <mailto:discuss@lists.opendaylight.org>>; TSC  <mailto:t...@lists.opendaylight.org>>; controller-dev 
>  <mailto:controller-...@lists.opendaylight.org>>; dev 
> mailto:d...@lists.opendaylight.org>>
> Subject: Re: [controller-dev] Sprint to talk at today's TWS
>  
> CAUTION: This email originated from outside of the organization. Do not click 
> links or open attachments unless you recognize the sender and know the 
> content is safe.
>  
> Hi, 
>  
> It just occurred to me after the presentation today, the FPC agent use case 
> may have some resemblance with the Honeycomb agent running in fd.io 
> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Ffd.io&data=02%7C01%7Clyle.t.bertz%40sprint.com%7C0f8091d2f8b14b49f8ad08d5e5cf45c5%7C4f8bc0acbd784bf5b55f1b31301d9adf%7C0%7C0%7C636667600750516825&sdata=sTYFgphd7IFnMNpVD3LHJi9m%2B8mDBy7XotbGx%2B4Zkhg%3D&reserved=0>:
>  
> https://wiki.fd.io/view/Honeycomb 
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.fd.io%2Fview%2FHoneycomb&data=02%7C01%7Clyle.t.bertz%40sprint.com%7C0f8091d2f8b14b49f8ad08d5e5cf45c5%7C4f8bc0acbd784bf5b55f1b31301d9adf%7C0%7C0%7C636667600750526829&sdata=yuwthFF8SOEQ6r4%2BnVCkbW4IfdCfOtSQ9nPzdkUAAT4%3D&reserved=0>
>  
> So I just leave the link in case Sprint is interested in looking at this too.
>  
> BR/Luis
>  
> 
> 
> On Jul 9, 2018, at 7:55 AM, Casey Cain  <mailto:cc...@linuxfoundation.org>> wrote:
>  
> Hello, everyone! 
>  
> Lyle from Sprint has agreed to speak to the ODL Community today about the 
> constraints that they are facing as well as optimization and successes.
>  
> Please join us at 10am this morning to participate.
>  
> Description:Join from PC, Mac, Linux, iOS or Android: 
> https://zoom.us/j/522266747 
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fzoom.us%2Fj%2F522266747&data=02%7C01%7Clyle.t.bertz%40sprint.com%7C0f8091d2f8b14b49f8ad08d5e5cf45c5%7C4f8bc0acbd784bf5b55f1b31301d9adf%7C0%7C0%7C636667600750526829&sdata=LO4JumdGEfXUhbP7WDizaivZF4vi1BcHvkjQJjvVwtw%3D&reserved=0>
>  Or iPhone one-tap (US Toll): +14086380968,522266747# or 
> +16465588656,522266747# Or Telephone: Dial: +1 408 638 0968 (US Toll) or +1 
> 646 558 8656 (US Toll) Meeting ID: 522 266 747 International numbers 
> available:https://zoom.us/zoomconference?m=IzwLtNv42ypJwZc_2xGhUMhFaAUbegBa 
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fzoom.us%2Fzoomconference%3Fm%3DIzwLtNv42ypJwZc_2xGhUMhFaAUbegBa&data=02%7C01%7Clyle.t.bertz%40sprint.com%7C0f8091d2f8b14b49f8ad08d5e5cf45c5%7C4f8bc0acbd784bf5b55f1b31301d9adf%7C0%7C0%7C636667600750536839&sdata=T2l84PkcPXBRxFwFJq4VmIi1pbyfNTHGjptC3pWU940%3D&reserved=0>
>  
>  
> Best,
> Casey Cain 
> Technical Program Manager
> Linux Foundation
> _
> IRC - CaseyLF
> Skype - wrathwolfk
> WeChat - okaru6
> ___
> controller-dev mailing list
> controller-...@lists.opendaylight.org 
> <mailto:controller-...@lists.opendaylight.org>
> https://lists.opendaylight.org/mailman/listinfo/controller-dev 
> <https://lists.opendaylight.org/mailman/listinfo/controller-dev>
>  
> 
> 
> This e-mail may contain Sprint proprietary information intended for the sole 
> use of the recipient(s). Any use by others is prohibited. If you are not the 
> intended recipient, please contact the sender and delete all copies of the 
> message.

___
Discuss mailing list
Discuss@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/discuss

Re: [OpenDaylight Discuss] Features required for L2 Switch OpenFlow Control

[Luis Gomez]

Welcome back David :)

For l2switch application I would recommend to install odl-l2switch-switch-rest 
or odl-l2switch-switch-ui (if you want GUI).

Here is the user guide:

https://docs.opendaylight.org/en/stable-oxygen/user-guide/l2switch-user-guide.html

BR/Luis

> On Jul 12, 2018, at 9:36 AM, David Bainbridge  
> wrote:
> 
> Given I have ODL up and running, which features do I need to install in order 
> to get basic L2 OF switch control using REST (inventory + flows)?
> 
> avèk respè,
> /david
> ___
> Discuss mailing list
> Discuss@lists.opendaylight.org
> https://lists.opendaylight.org/mailman/listinfo/discuss

___
Discuss mailing list
Discuss@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/discuss

Re: [OpenDaylight Discuss] [controller-dev] Sprint to talk at today's TWS

[Luis Gomez]

Hi,

It just occurred to me after the presentation today, the FPC agent use case may 
have some resemblance with the Honeycomb agent running in fd.io :

https://wiki.fd.io/view/Honeycomb 

So I just leave the link in case Sprint is interested in looking at this too.

BR/Luis


> On Jul 9, 2018, at 7:55 AM, Casey Cain  wrote:
> 
> Hello, everyone!
> 
> Lyle from Sprint has agreed to speak to the ODL Community today about the 
> constraints that they are facing as well as optimization and successes.
> 
> Please join us at 10am this morning to participate.
> 
> Description:Join from PC, Mac, Linux, iOS or Android: 
> https://zoom.us/j/522266747 
> 
> Or iPhone one-tap (US Toll):  +14086380968,522266747# or 
> +16465588656,522266747#
> 
> Or Telephone:
> Dial: +1 408 638 0968 (US Toll) or +1 646 558 8656 (US Toll)
> Meeting ID: 522 266 747
> International numbers available: 
> https://zoom.us/zoomconference?m=IzwLtNv42ypJwZc_2xGhUMhFaAUbegBa 
>  
> 
> Best,
> Casey Cain
> Technical Program Manager
> Linux Foundation
> _
> IRC - CaseyLF
> Skype - wrathwolfk
> WeChat - okaru6
> ___
> controller-dev mailing list
> controller-...@lists.opendaylight.org
> https://lists.opendaylight.org/mailman/listinfo/controller-dev

___
Discuss mailing list
Discuss@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/discuss

Re: [OpenDaylight Discuss] [integration-dev] TSC meetings time doodle poll results - and new meeting time

[Luis Gomez]

Swap works for me too.

> On May 24, 2018, at 2:36 PM, Jamo Luhrsen  wrote:
> 
> just swap it with the TSC please.
> 
> JamO
> 
> On 5/24/18 2:35 PM, Abhijit Kumbhare wrote:
>> Forgot to mention: unfortunately the new timeslot clashes with the current 
>> timeslot for the integration test meeting. Apologize for having to move your 
>> meeting to some other timeslot. Hopefully you (integration test team) can 
>> manage the meeting time transition smoothly.
>> On Thu, May 24, 2018 at 2:32 PM, Abhijit Kumbhare >  > >> wrote:
>>Hi folks,
>>The TSC meeting doodle poll results are in - with a clear majority 
>> favoring the Thursdays 9 am Pacific time slot.
>>Out of the 13 TSC members, 12 members voted. Out of those 10 TSC members 
>> voted for this option (9 am P), 8 voted for
>>the original 10 am P option while 7 voted for 8:30 am P. Also most of the 
>> others were OK with the time slot. These
>>included required participants: the release manager, the MSI/MRI PTLs, 
>> TAC representative & program manager (Casey).
>>Hence - let us move to start using this time slot from the next TSC 
>> meeting onwards - which is May 31st. I will
>>request Casey to update the Zoom meeting info.
>>Details from the vote:
>>For the 2 TSC members who were not OK with the slot - Lori and An Ho - I 
>> hope you are able to make it to the changed
>>timeslot.
>>Hopefully this changed timeslot enables at least a few folks who were 
>> previously unable to attend to attend -
>>without losing too many from the current attendees.
>>Thanks,
>>Abhijit
>>On Sun, May 20, 2018 at 2:41 PM, Abhijit Kumbhare > > >> wrote:
>>https://doodle.com/poll/5fi657n95dgz8xqb 
>>  
>> > >
>>On Sun, May 20, 2018 at 2:39 PM, Abhijit Kumbhare 
>> > > >> wrote:
>>Added doodle poll for this. I know folks have voted over this 
>> thread - but please vote again on the doodle poll:
>>https://doodle.com/poll/5fi657n95dgz8xqb 
>>  
>> > >
>>On Sun, May 20, 2018 at 10:29 AM, Thanh Ha 
>> mailto:thanh...@linuxfoundation.org>
>>> >> wrote:
>>On Thu, May 17, 2018 at 7:00 PM, Abhijit Kumbhare 
>> > > >>
>>wrote:
>>Hi folks,
>>During the TSC meeting today one of the topics discussed 
>> was the meeting time. Some folks were of
>>the opinion that it maybe useful for folks in Europe and 
>> India if the meeting was moved earlier by
>>an hour or an hour and half - i.e. Thursdays 8:30 am or 9 
>> am Pacific instead of 10 am Pacific.
>>Can folks who attend the meeting and the folks who 
>> currently do not attend but would attend if it
>>was moved please respond with your preferred time out of 
>> the following choices (Thursdays):
>>  * 8:30 am Pacific
>>  * 9 am Pacific
>>  * 10 am Pacific
>>  * 0 (either 8:30, 9 or 10 am Pacific)
>>  * -1 (neither 8:30, 9 or 10 am Pacific)
>>For the "-1" voters - for now we will not have the choice 
>> of the time - we will discuss this option
>>only if there are sufficient number of folks going for 
>> this option.
>>I have kept the vote open for everyone - but at the 
>> minimum, the TSC members, the MRI/MSI PTLs & LFN
>>staff (Casey/Phil) should vote.
>>Please note that if we move the meeting - we will need to 
>> move the integration call as well.
>>Regards,
>>Abhijit
>>I am +1 for all the proposed times.
>>(I think a doodle poll would be better for this)
>>Regards,
>>Thanh
>> ___
>> Discuss mailing list
>> Discuss@lists.opendaylight.org
>> https://lists.opendaylight.org/mailman/listinfo/discuss
> ___
> integration-dev mailing list
> integration-...@lists.opendaylight.org 
> 
> https://lists.opendaylight.org/mailman/listinfo/integration-dev 
> 

Re: [OpenDaylight Discuss] [OpenDaylight TSC] OpenDaylight 2018 Internships

[Luis Gomez]

I was doubting but finally I added an entry to push the dashboard work we 
started last internship.


> On Apr 16, 2018, at 10:35 AM, Casey Cain  wrote:
> 
> Timelines for Internships is outlined here:
> https://wiki.lfnetworking.org/display/LN/LF+Networking+Internships 
> 
> 
> 
> 
> On Mon, Apr 16, 2018 at 8:33 AM, Abhijit Kumbhare  > wrote:
> I think discussing here is fine.
> 
> On Mon, Apr 16, 2018 at 8:26 AM, Michael Vorburger  > wrote:
> Casey,
> 
> On Thu, Apr 12, 2018 at 6:14 PM, Casey Cain  > wrote:
> Hello, everyone.
> 
> This is a reminder that we are seeking Mentors for the 2018 Internships.  If 
> you are willing to be a mentor and you have a project you would like an 
> Intern to work on, please submit your Project Proposal here:
> https://wiki.opendaylight.org/view/Interns/Projects 
> 
> 
> I've added a project (Gradle), and already had 1 possible student contact me 
> on private email. 
> 
> He's asked about the dates / timelines are, and I'm not clear about this 
> myself; could we add this somewhere? Like I'm guessing there is a phase 
> during which we solicit interest, then a (short) phase were we chooose 
> students and projects? From my own experience having been a Google Summer of 
> Code mentor in a previous life, it's best to choose and match students and 
> projects after seeing interest, in function of your available slots.
> 
> Do we have a particular mailing list for any intership related discussions, 
> or just here is fine?
>  
> Regards,
> Casey Cain
> Technical Program Manager
> Linux Foundation
> _
> IRC - CaseyODL
> Skype - wrathwolfk
> WeChat - okaru6
> 
> ___
> Discuss mailing list
> Discuss@lists.opendaylight.org 
> https://lists.opendaylight.org/mailman/listinfo/discuss 
> 
> 
> 
> 
> ___
> TSC mailing list
> t...@lists.opendaylight.org 
> https://lists.opendaylight.org/mailman/listinfo/tsc 
> 
> 
> 
> 
> 
> 
> -- 
> Casey Cain
> Technical Program Manager
> Linux Foundation
> _
> IRC - CaseyODL
> Skype - wrathwolfk
> WeChat - okaru6
> ___
> TSC mailing list
> t...@lists.opendaylight.org 
> https://lists.opendaylight.org/mailman/listinfo/tsc 
> 
___
Discuss mailing list
Discuss@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/discuss

Re: [OpenDaylight Discuss] Multiple Controller implementation

[Luis Gomez]

> On Feb 7, 2018, at 5:11 PM, Mohamed Abdel Metaal  
> wrote:
> 
> Luis,
>  
> This could not be possible as all controllers in this case will connect to 
> the same openflow ports, RESTCONF, Jolokia ports 8081 and 8080 along with 
> other ports too, so the other 2 controllers will address ports which is 
> already being addressed by the first controller. It would only be possible to 
> work if these ports are changed in each of the other controllers so they 
> don’t collide using the same ports, eg. Openflow ports 6633 / 6653. Just to 
> clarify, as I have forgot, I am implementing this using my Ubuntu machine 
> without the use of virtual machines. That’s another question, could this be 
> implemented using only my local machine without virtual machines and tweaking 
> the ports in each OpenDaylight folder (for each controller)?

I do not think you can bring more than one controller instance in same machine 
unless you use VMs or docker. on both options you do not need to modify 
controller ports.

>  
> Jamo,
>  
> I am currently implementing the controllers in one machine so they have the 
> same address to address the controllers (which is the loopback address in my 
> case). So the controllers in my mininet script have the same ip address but 
> different openflow ports 6653, 7753 and 8853. Again, probably the same 
> question arises, is multiple controllers only possible to implement using 
> different virtual machines per controller?
>  
> Thanks 😊
>  
> P.S. I have implemented the same implementation before using Floodlight and 
> there was a certain number of ports, including openflow ports, that needs to 
> be changed. All using my local machine without the need for virtual machines.
> If this is possible then it could be also a great idea to benchmark 
> OpenDaylight with other SDN controllers for behavior using a physically 
> distributed control plane.
>  
>  
> From: Jamo Luhrsen <mailto:jluhr...@gmail.com>
> Sent: Thursday, February 8, 2018 1:53
> To: Luis Gomez <mailto:ece...@gmail.com>; Mohamed Abdel Metaal 
> <mailto:m.alaa...@hotmail.com>
> Cc: discuss@lists.opendaylight.org <mailto:discuss@lists.opendaylight.org>; 
> openflowplugin-dev <mailto:openflowplugin-...@lists.opendaylight.org>
> Subject: Re: [OpenDaylight Discuss] Multiple Controller implementation
>  
> 
> 
> On 2/7/18 4:24 PM, Luis Gomez wrote:
> > 
> >> On Feb 7, 2018, at 4:09 PM, Mohamed Abdel Metaal  >> <mailto:m.alaa...@hotmail.com><mailto:m.alaa...@hotmail.com 
> >> <mailto:m.alaa...@hotmail.com>>> wrote:
> >>
> >> Hello Jamo,
> >>
> >> Yes exactly, I have one instance of mininet running that should be 
> >> connected to 3 opendaylight controllers. In my
> >> mininet python script i have defined that controllers should connect on 
> >> 6653, 7753 and 8853 openflow ports. This
> >> should be somehow configured also in my opendaylight controllers for it to 
> >> connect. I have tried changing port numbers
> >> in default(and legacy)-openflow-connection-config.xml for the 3 different 
> >> opendaylight controllers and ports 8081/8080
> >> for jetty.xml so they don’t collide but still I get the errors and the 2 
> >> other controllers cannot connect to my
> >> mininet instance.
> 
> Luis,
> 
> is there a config we can tweak to tell OFP which port to listen on?
> 
> Mohamed
> 
> can you tweak your mininet python script to use the actual ip addresses of 
> your
> controllers? seems that those would be different. In that case, why can't they
> all be listening on 6633?
> 
> Thanks,
> JamO
> 
> 
> >> As a brief example just to make sure that my idea is clear: i run a 
> >> mininet instance of 6 switches where each
> >> controller should only see/monitor/connect to 2 of the switches.
> > 
> > I am not sure I full follow here: is this as simple as connect 2 switches 
> > to a first controller, the next 2 switches to
> > a second controller and finally the last 2 switches to a third controller? 
> > if so there is nothing to do in controller,
> > juts need to set mininet or OVS to do this, right?
> > 
> >>
> >> Thank you for your response.
> >>
> >> 
> >> *From:* Jamo Luhrsen mailto:jluhr...@gmail.com> 
> >> <mailto:jluhr...@gmail.com <mailto:jluhr...@gmail.com>>>
> >> *Sent:* Thursday, February 8, 2018 12:57:26 AM
> >> *To:* Mohamed Abdel Metaal; discuss@lis

Re: [OpenDaylight Discuss] Multiple Controller implementation

[Luis Gomez]

> On Feb 7, 2018, at 4:09 PM, Mohamed Abdel Metaal  
> wrote:
> 
> Hello Jamo,
> 
> Yes exactly, I have one instance of mininet running that should be connected 
> to 3 opendaylight controllers. In my mininet python script i have defined 
> that controllers should connect on 6653, 7753 and 8853 openflow ports. This 
> should be somehow configured also in my opendaylight controllers for it to 
> connect. I have tried changing port numbers in default(and 
> legacy)-openflow-connection-config.xml for the 3 different opendaylight 
> controllers and ports 8081/8080 for jetty.xml so they don’t collide but still 
> I get the errors and the 2 other controllers cannot connect to my mininet 
> instance.
> 
> As a brief example just to make sure that my idea is clear: i run a mininet 
> instance of 6 switches where each controller should only see/monitor/connect 
> to 2 of the switches.

I am not sure I full follow here: is this as simple as connect 2 switches to a 
first controller, the next 2 switches to a second controller and finally the 
last 2 switches to a third controller? if so there is nothing to do in 
controller, juts need to set mininet or OVS to do this, right?

> 
> Thank you for your response.
> 
> From: Jamo Luhrsen mailto:jluhr...@gmail.com>>
> Sent: Thursday, February 8, 2018 12:57:26 AM
> To: Mohamed Abdel Metaal; discuss@lists.opendaylight.org 
> ; openflowplugin-dev
> Subject: Re: [OpenDaylight Discuss] Multiple Controller implementation
>  
> adding the openflowplugin-dev list here as well.
> 
> Mohamed,
> 
> I don't get the impression that your OpenDaylight controllers are in a 
> clustering
> setup. Is that correct?
> 
> I'm not totally following what you are trying to accomplish. You have just one
> mininet instance connecting to a single IP address, but you want the switches
> in that single mininet instance to somehow be distributed across multiple (3)
> OpenDaylight controllers?
> 
> Can you elaborate a little more please?
> 
> Thanks,
> JamO
> 
> 
> On 2/7/18 3:38 PM, Mohamed Abdel Metaal wrote:
> > I have a question regarding the implementation of multiple controllers 
> > using OpenDaylight.
> > If I want to implement 3 controllers, each responsible for a certain number 
> > of nodes in the topology (so we have 3
> > domains) which are not overlapping, how can this be implemented? I have 
> > experience with Floodlight controllers and I
> > could implement this by changing openflow port number along with other 
> > ports in some properties file but in OpenDaylight
> > I always get errors when I run 3 instances of controllers and only the 
> > first one gets connected to Mininet topology that
> > I implement with the controllers defined.
> > 
> > ___
> > Discuss mailing list
> > Discuss@lists.opendaylight.org 
> > https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.opendaylight.org%2Fmailman%2Flistinfo%2Fdiscuss&data=02%7C01%7C%7C78feb80f3d6445ffa54e08d56e868b68%7C84df9e7fe9f640afb435%7C1%7C0%7C636536446494956220&sdata=YmTHBgBPJ%2FwVvUGrRMBJQOV5NeQME55c%2B2%2B11K873Vs%3D&reserved=0
> >  
> > 
> > 
> ___
> Discuss mailing list
> Discuss@lists.opendaylight.org 
> https://lists.opendaylight.org/mailman/listinfo/discuss 
> 

___
Discuss mailing list
Discuss@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/discuss

Re: [OpenDaylight Discuss] [release] [OpenDaylight TSC] ONS Developer Event

[Luis Gomez]

+1, can we have someone from LF events or with some authority on this to join 
the next TSC call?


> On Jan 23, 2018, at 3:48 PM, Daniel Farrell  wrote:
> 
> I'm hoping this claim that we'd have to pay to attend our own DDF at ONS gets 
> revised. I've asked Casey/Phil/events-list to have the events staff join this 
> conversation directly vs having everything proxied through Casey.
> 
> With my Committer Board Member hat on, I'm also quite disappointed about how 
> this is going. We were told ONS would be the future for ODL's Summits, with 
> cost savings and collaboration goodness added by making it part of a big 
> umbrella. ODL contributed a huge amount of cash to LFN. We've been very clear 
> that we want to have a DDF at ONS for quite some time. It seems like we 
> should at least be able to get a free room for a few days at our own ~Summit.
> 
> Hoping we can find a good/clear conclusion soon,
> Daniel
> 
> On Wed, Jan 24, 2018 at 12:31 AM George Zhao  <mailto:george.y.z...@huawei.com>> wrote:
> Given current situation, will day pass option for Tue or Wed work for DDF? It 
> will be even better if there is a developer discount for DDF.
> 
>  
> 
> Thanks,
> 
> George
> 
>  
> 
>  
> 
> From: release-boun...@lists.opendaylight.org 
> <mailto:release-boun...@lists.opendaylight.org> 
> [mailto:release-boun...@lists.opendaylight.org 
> <mailto:release-boun...@lists.opendaylight.org>] On Behalf Of Anil Vishnoi
> Sent: Tuesday, January 23, 2018 3:06 PM
> To: Brady Johnson
> Cc: OpenDaylight Discuss; Raymond Paik; TSC; rele...@lists.opendaylight.org 
> <mailto:rele...@lists.opendaylight.org>
> Subject: Re: [release] [OpenDaylight TSC] [OpenDaylight Discuss] ONS 
> Developer Event
> 
>  
> 
> For the open source technical community, no other event is as important as 
> DDF, so if they have to pay for getting together to get the work done and 
> plan the future of the project, i think it's disappointing :(.
> 
>  
> 
> Thanks
> 
> Anil
> 
>  
> 
> On Tue, Jan 23, 2018 at 2:12 PM, Brady Johnson  <mailto:bjohn...@inocybe.ca>> wrote:
> 
> Casey confirmed to me in a private thread that those attending the ODL DDF on 
> Monday and Tuesday will have to register for the ONS event. That's a deal 
> breaker for me, I won't be attending the DDF if I'm forced to pay the 
> ridiculously expensive ONS registration fee.
> 
>  
> 
> Needless to say, I'm very disappointed in how this had been handled and 
> organized.
> 
>  
> 
> Regards,
> 
>  
> 
> Brady
> 
>  
> 
>  
> 
>  
> 
> On Jan 23, 2018 14:48, "Abhijit Kumbhare"  <mailto:abhijitk...@gmail.com>> wrote:
> 
> I have asked Phil this question on his email thread.
> 
>  
> 
> On Tue, Jan 23, 2018 at 12:38 PM, Anil Vishnoi  <mailto:vishnoia...@gmail.com>> wrote:
> 
> If that's the case, then probably Option 1 is not really an option :).
> 
>  
> 
> On Tue, Jan 23, 2018 at 12:29 PM, Luis Gomez  <mailto:ece...@gmail.com>> wrote:
> 
> I guess the only concern with option 1) is the one Brady brought: the high 
> price (1.8K$?) people just interested in ODL DDF will have to pay if there is 
> no free/reduced pass for ODL DDF. This can imo lower the DDF attendance so 
> better get some clarification on this too.
> 
>  
> 
>  
> 
> On Jan 23, 2018, at 11:59 AM, Anil Vishnoi  <mailto:vishnoia...@gmail.com>> wrote:
> 
>  
> 
> From Phil's mail, I personally would prefer option 1 or 2, because these 
> options are way better than asking folks to travel on Saturday to attend one 
> day event on Sunday and waste Monday again in travel. I believe common set of 
> people who wants to attend ODL DDF and ONS event (paid registration) is very 
> small, so we need to consider the remaining bigger set of people who are just 
> looking for attending ODL DDF, because from ODL DDF perspective that's more 
> important. From that perspective i think option 1 is better and if that 
> doesn't work than option 2 seems like an alternate, but not sure that will 
> work well for the folks travelling international. So seems like Option 1 is 
> the only option we have as of now, which i think is not a bad option.
> 
>  
> 
> Anil
> 
>  
> 
> On Tue, Jan 23, 2018 at 11:46 AM, Thanh Ha  <mailto:thanh...@linuxfoundation.org>> wrote:
> 
> On Tue, Jan 23, 2018 at 1:09 PM, Abhijit Kumbhare  <mailto:abhijitk...@gmail.com>> wrote:
> 
> I think we have the following constraints (based on discussions at the TSC 
> and another separate chat I had las

Re: [OpenDaylight Discuss] [OpenDaylight TSC] TSC Meeting time vote: Clarifying the plan for developer gathering at ONS

[Luis Gomez]

+1

> On Jan 23, 2018, at 3:07 PM, An Ho  wrote:
> 
> +1
>  
> Best Regards,
> An Ho
>  
> From: tsc-boun...@lists.opendaylight.org 
> [mailto:tsc-boun...@lists.opendaylight.org] On Behalf Of Thanh Ha
> Sent: Tuesday, January 23, 2018 2:41 PM
> To: Anil Vishnoi 
> Cc: tsc ; discuss@lists.opendaylight.org
> Subject: Re: [OpenDaylight TSC] [OpenDaylight Discuss] TSC Meeting time vote: 
> Clarifying the plan for developer gathering at ONS
>  
> +1
>  
> Thanh
>  
> On Tue, Jan 23, 2018 at 5:12 PM, Anil Vishnoi  > wrote:
> +1
>  
> On Tue, Jan 23, 2018 at 1:46 PM, Abhijit Kumbhare  > wrote:
> Since we have a lot to discuss this TSC meeting & historically we have had a 
> fairly low attendance during the APAC timezone TSC meeting - shall we move 
> tomorrow's APAC timezone TSC meeting to the normal TSC meeting time (Thursday 
> 10 am Pacific)?
>  
> I think we should vote: -1, 0, +1.
>  
> +1 from my side to move it this week.
>  
>  
> On Tue, Jan 23, 2018 at 1:05 PM, Casey Cain  > wrote:
> We can discuss in more detail our options during the TSC meeting tomorrow.  
> However, I've been informed that attendance to the Monday / Tuesday event 
> will require registration for ONS.
>  
> Regards,
> Casey
>  
> On Tue, Jan 23, 2018 at 1:02 PM, Daniel Farrell  > wrote:
> Thanks for helping to clarify things Phil. In addition to Abhijit's question 
> about cost, a few more questions:
>  
> 1. Will the XCI event still be held Sunday?
>  
> 2. It seems like the Monday/Tuesday event will only be 1.5 days. I'm 
> concerned that's insufficient for an ODL DDF by itself, and especially 
> doesn't allow time for cross-project talks (which I think are increasingly 
> important). Maybe we can have a room for continuing DDF talks during ONS? Or 
> I suppose we can just informally conquer a public space. We have a 
> substantial number of devs who would want to be home before Good Friday, but 
> missing the tail end isn't so bad, and we're balancing tough options.
> 
> 3. Especially if we do something during ONS, is there any way we can imagine 
> to make the cost more reasonable for developers? Like a Dev Pass that only 
> lets you into a small subset of the rooms? Or $5-10 voucher per-patch? As it 
> stands it doesn't seem like many of our devs will attend ONS-proper, which is 
> a shame and bad for ODL/LFN.
>  
> Thanks,
> Daniel
>  
> On Tue, Jan 23, 2018, 7:43 PM Phil Robb  > wrote:
> Hello OpenDaylight developers and TSC members:
>  
> I wanted to provide some clarity on the activities and timeframe we have to 
> gather during ONS.
>  
> The developer event during ONS week will be from 8:00am to 6:00pm on Monday, 
> March 26th, and 8:00am to 12:00 noon on Tuesday, March 27th.  From requests 
> we have received we had also been investigating the possibility to extend the 
> event into the proceeding Sunday, but we've determined that such an extension 
> is not going to be possible.  That said, we still have the Monday/Tuesday 
> time for formal presentations, as well as break out rooms and a developer 
> lounge for continued meetings, discussions, and hacking at ONS during the 
> rest of the week.
>  
> As we've mentioned before, we would like to take advantage of the fact that 
> the communities from the different projects will be in the same place at the 
> same time.  As such, we encourage you to propose sessions that can further 
> cross-collaboration among the LFN projects.  We also recognize that there are 
> plenty of project-specific topics that need to be discussed.  Please also 
> propose those sessions for this event.  
>  
> With the LFN formally announced today, we are working to get the LFN wiki 
> site up and running as quickly as possible.  One of the first uses for this 
> site will be the location for submitting your proposed talks and 
> presentations for the developer event at ONS.  We apologize that it is not up 
> quite yet but it will be up within the next 2 or 3 days.
>  
> Once the site is up, Ray Paik (cc-ed) will send out an email to all 
> communities on where to find it along with a call-for-presentations for you 
> to post your discussion and presentation topics.  Between February 9th and 
> February 15th, we will convene the TAC representatives from the LFN projects 
> to review the submissions and to form an outline/framework for the developer 
> event, giving time for cross-project discussions, project-specific sessions, 
> and a TAC meeting.  From there, we will work with each project TSC to 
> prioritize project-specific sessions during the event.
>  
> For OpenDaylight in particular, I know we've been trying to fit the Florine 
> DDF on that proceeding Sunday.  However, this won't be possible.  Given this, 
> we have a number of alternatives:
> 1) We could hold the DDF during the Monday and Tuesday of ONS.  I know that 
> we had said w

Re: [OpenDaylight Discuss] [release] [OpenDaylight TSC] ONS Developer Event

[Luis Gomez]

I guess the only concern with option 1) is the one Brady brought: the high 
price (1.8K$?) people just interested in ODL DDF will have to pay if there is 
no free/reduced pass for ODL DDF. This can imo lower the DDF attendance so 
better get some clarification on this too.


> On Jan 23, 2018, at 11:59 AM, Anil Vishnoi  wrote:
> 
> From Phil's mail, I personally would prefer option 1 or 2, because these 
> options are way better than asking folks to travel on Saturday to attend one 
> day event on Sunday and waste Monday again in travel. I believe common set of 
> people who wants to attend ODL DDF and ONS event (paid registration) is very 
> small, so we need to consider the remaining bigger set of people who are just 
> looking for attending ODL DDF, because from ODL DDF perspective that's more 
> important. From that perspective i think option 1 is better and if that 
> doesn't work than option 2 seems like an alternate, but not sure that will 
> work well for the folks travelling international. So seems like Option 1 is 
> the only option we have as of now, which i think is not a bad option.
> 
> Anil
> 
> On Tue, Jan 23, 2018 at 11:46 AM, Thanh Ha  > wrote:
> On Tue, Jan 23, 2018 at 1:09 PM, Abhijit Kumbhare  > wrote:
> I think we have the following constraints (based on discussions at the TSC 
> and another separate chat I had last Wednesday with Ray Paik and Casey):
> 
> We cannot have just following the ONS due to Passover Friday March 30 to 
> Saturday April 7 during which some members cannot attend. Also Friday March 
> 30 is not available at the venue.
> We cannot have DDF during the Monday-Tuesday of the ONS week - due to the LFN 
> cross collaboration 
> Sunday March 25 is available and LFN would be able to arrange rooms for the 
> DDF
> Other days like Daniel's suggestion Thursday-Friday March 18-19 in Los 
> Angeles or somewhere else 
> an appropriate venue at appropriate price would need to be found
> Folks traveling from abroad may not have the approval for an over the weekend 
> stay. 
> Also folks coming for ONS as well may find it hard to stay from Thursday 
> March 18 to Thursday March 29
> Given these constraints - do we still want to pursue another option 
> (Thursday-Friday March 18-19) compared to Sunday March 25?
> 
> Please voice your opinions soon. Otherwise the original decision of Sunday 
> March 25 would stand. As Luis mentioned - we would need to start booking 
> travel. 
> 
> Phil's email [0] seems to throw a wrench into this whole thing. Sounds like 
> Sunday is no longer available to us but Monday/Tuesday is. Or we will have to 
> do it on another date and place.
> 
> Thanh
> 
> [0] https://lists.opendaylight.org/pipermail/tsc/2018-January/008679.html 
> 
> ___
> release mailing list
> rele...@lists.opendaylight.org 
> https://lists.opendaylight.org/mailman/listinfo/release 
> 
> 
> 
> 
> 
> -- 
> Thanks
> Anil
> ___
> release mailing list
> rele...@lists.opendaylight.org
> https://lists.opendaylight.org/mailman/listinfo/release

___
Discuss mailing list
Discuss@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/discuss

Re: [OpenDaylight Discuss] [OpenDaylight TSC] [release] ONS Developer Event

[Luis Gomez]

Do we have an ETA for LF to communicate final plan and price for ONS? I guess 
we need that prior to booking trips.

BR/Luis

> On Jan 23, 2018, at 7:00 AM, Daniel Farrell  wrote:
> 
> Yeah, I remember #agreeing that, but I think it was because Casey had 
> basically told us It Must Be So. I meant to point out that since everything 
> seems so up-in-the-air, and the community seems to prefer other options, we 
> may want to keep them on the table. In particular I'm concerned about low 
> attendance if we have a Sunday DDF and must to pay for the Monday/Tuesday 
> event. For folks traveling internationally, it's a hard sell. Something like 
> Thursday/Friday DDF + weekend in LA + free Sunday XCI + free Mon/Tues 
> cross-community + costly/optional ONS Thurs/Fri seems much more appealing.
> 
> Daniel
> 
> On Tue, Jan 23, 2018 at 3:43 PM Brady Johnson  > wrote:
> Dan,
> 
> I was under the impression that we agreed on Sunday in the last TSC call. The 
> following was posted in the meeting minutes:
> 
> AGREED: ODL DDF will be on Sunday March 25, 2018 (abhijitkumbhare, 19:04:10)
> 
> And later summarized as follows by Abhijit in his email about the meeting 
> minutes:
> 
> The Fluorine DDF will be on March 25, 2018 - which is unfortunately on a 
> Sunday but that is the best choice in the current circumstances. It will be 
> at the same venue as the ONS. There will be possibilities to have smaller 
> breakout sessions on Monday and Tuesday during the LFN developer event.
> 
> I agree that the ONS event is ridiculously expensive, and consequently I wont 
> be attending it. Im making the trip just to attend the DDF, which I feel is 
> worth it. I was able to reserve at the event hotel for the nights of Saturday 
> and Sunday (March 24, 25) for the same rate of $259/night. 
> 
> I hope we can also have breakout sessions on Monday without having to pay to 
> get into the ONS for the day. I hope Phil and Casey will work this out for 
> us. If ONS insists on being so expensive and charging for ridiculous things 
> like an ODL breakout session, then they should be worried about facing the 
> same fate as the SDN world congress, who tried to do the same thing and 
> nobody attends that anymore.
> 
> 
> Regards,
> 
> Brady Johnson
> bjohn...@inocybe.ca 
> 
> 
>      
> 
>   
> 
> 
> On Tue, Jan 23, 2018 at 7:35 AM, Daniel Farrell  > wrote:
> Bumping this thread to summarize where we're at and what we need to know.
> 
> Mentally running a raked-preference algorithm on the votes we saw, it looks 
> like the community prefers 3 (Thurs/Fri), then 1 (Mon/Tues), then a distant 2 
> (Sunday). However, Casey's follow-up makes it seem like we don't have much of 
> an option, must do 2/Sunday.
> 
> Regarding costs, there seems to be ongoing confusion. Casey mentioned above 
> and on the TSC that the Monday/Tuesday cross-community event would be free 
> for DDF participants, but told a few of us on yesterday's TWS that he's now 
> hearing it will not be free. I've also heard quite a bit of off-list concern 
> that the DDF is at risk of not being well-attended since it's a single 
> weekend day and ONS is so expensive ($1195 early bird). A number of us also 
> sent talks to ONS that now seem like they should be part of the 
> cross-community event (track details sent after CFP closed), so we're not 
> sure if we will get speaker passes.
> 
> We've also asked for the hotel discount to start on Saturday since the DDF 
> will be Sunday but haven't heard back.
> 
> We really need to get some clarity here ASAP as folks are trying to figure 
> out budgets and flights will start going up in price soon.
> 
> Thanks,
> Daniel
> 
> On Sat, Jan 20, 2018 at 7:11 AM Anil Belur  > wrote:
> On Thu, Jan 18, 2018 at 1:05 AM, Daniel Farrell  > wrote:
> Bumping this thread because we really need to get to a resolution ASAP, folks 
> need to book travel.
> 
> The options I've seen:
> 
> 1. DDF on Thursday/Friday before ONS. Very long trip, but no conflicts.
> 2. DDF on Sunday before ONS. Conflicts with XCI event, working on the weekend 
> sucks.
> 3. DDF during Mon/Tue of ONS. Conflicts with cross-community collaboration 
> event. Unclear if cross-community event has two full days of relevant 
> content. Maybe possible to time-slice in a way that minimizes conflict (DDF 
> in the morning, cross-community events involving ODL in the afternoon).
> 4. Have a virtual DDF. Likely not as productive, little support voiced so far.
> 
> I prefer 1 or 3, since the XCI event is critical for me.
> 
> 
> +1 for 1 or 3
> 
> ___

Re: [OpenDaylight Discuss] L2switch errors since bump

[Luis Gomez]

Please be aware that the bump migration is not completed yet, this could be 
just a side effect of the topology model issue found here:

https://lists.opendaylight.org/pipermail/openflowplugin-dev/2018-January/007912.html
 


BR/Luis


> On Jan 18, 2018, at 6:53 AM, Michael Vorburger  wrote:
> 
> On Thu, Jan 18, 2018 at 3:18 PM, Jacob Steadman  > wrote:
> Hi,
> 
>  
> 
> I’m developing a new feature, building upon some of the functionality within 
> the l2switch project.
> 
> 
> +l2switch-dev list:
>  
> 
> It was all working fine before the bump yangtools & ODLparent bump… Now when 
> it is executing  I am getting the following errors about the 
> PacketProcessingService and SalFlowService…
> 
> 
>  
> 
> 2018-01-18 14:00:10,210 | WARN  | tures-1-thread-1 | RpcServiceMetadata   
> | 191 - org.opendaylight.controller.blueprint - 0.8.0.SNAPSHOT | 
> org.opendaylight.l2switch.myFeature.impl (packetHandlerService): interface 
> interface 
> org.opendaylight.yang.gen.v1.urn.opendaylight.packet.service.rev130709.PacketProcessingService
>  has no accptable entries, assuming it is satisfied
> 
> 2018-01-18 14:00:10,220 | WARN  | tures-1-thread-1 | RpcServiceMetadata   
> | 191 - org.opendaylight.controller.blueprint - 0.8.0.SNAPSHOT | 
> org.opendaylight.l2switch.myFeature.impl (salFlowService): interface 
> interface 
> org.opendaylight.yang.gen.v1.urn.opendaylight.flow.service.rev130819.SalFlowService
>  has no accptable entries, assuming it is satisfied
> 
>  
> 
>  
> 
> As well as this it is giving out an error message for several of the existing 
> features  (the first is arphandler but there are multiple)...
> 
>  
> 
>  
> 
> 2018-01-18 14:00:09,823 | ERROR | 74e-11e3804cbdfe | BlueprintContainerImpl   
> | 77 - org.apache.aries.blueprint.core - 1.8.3 | Unable to start 
> blueprint container for bundle 
> org.opendaylight.l2switch.arphandler.impl/0.7.0.SNAPSHOT
> 
> 
> the ODLError.txt you have attached seem to indicate some Blueprint wiring 
> problem / mismatch for some ArpHandlerProvider bean... note "Unable to find a 
> matching constructor on class". Someone from the l2switch project more 
> familiar with internals should probably have a closer look at the BP XML?
>  
> 
> (FULL ERROR ATTACHED)
> 
>  
> 
>  
> 
> Any help would be greatly appreciated.
> 
>  
> 
> Thanks,
> 
> Jacob
> 
>  
> 
>  
> 
> 
> ___
> Discuss mailing list
> Discuss@lists.opendaylight.org 
> https://lists.opendaylight.org/mailman/listinfo/discuss 
> 
> 
> 
> ___
> Discuss mailing list
> Discuss@lists.opendaylight.org 
> https://lists.opendaylight.org/mailman/listinfo/discuss 
> 
___
Discuss mailing list
Discuss@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/discuss

Re: [OpenDaylight Discuss] [release] [OpenDaylight TSC] odlparent 3 / yangtools 2 migration

[Luis Gomez]

For those projects that are part of the oxygen distribution and want to check 
the bump locally, here is the link to download:

https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/karaf/0.8.0-SNAPSHOT/karaf-0.8.0-20180117.101056-1263.zip
 
<https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/karaf/0.8.0-SNAPSHOT/karaf-0.8.0-20180117.101056-1263.zip>

BR/Luis

> On Jan 17, 2018, at 9:49 AM, Luis Gomez  wrote:
> 
> 
> 
>> On Jan 17, 2018, at 7:52 AM, Faseela K  wrote:
>> 
>> Yes Sam.
>> We are not going to merge anything till the builds pass, and tests pass.
>> Luis’ mail had pointers that we will be able to soon build distribution, as 
>> we are planning to remove projects pending the bump patches.
> 
> I did already that in int/distribution so that we can at least get something 
> tested in CSIT. I think logical next step is:
> 
> - For all projects that have not successfully merged the bump patch yet [1], 
> work on that and report any problem.
> - For all projects that have already merged the bump patch and are part of 
> the distribution (the remaining projects), check CSIT results of next 
> distribution test [2] and report any issue you notice.
> 
> For the second expect the following known issues:
> 
> - Topology model version problem: 
> https://lists.opendaylight.org/pipermail/openflowplugin-dev/2018-January/007912.html
> - Change of karaf prompt can make test very slow: 
> https://lists.opendaylight.org/pipermail/release/2018-January/013412.html
> - Error booting some feature: it could be because of this: 
> https://git.opendaylight.org/gerrit/#/c/67229/
> 
> [1] alto, eman, faas, gbp, memo, nic, of-config, p4plugin, packetcable, 
> snmp4sdn, tsdr, unimgr, usc, vtn
> [2] 
> https://jenkins.opendaylight.org/releng/view/distribution/job/integration-distribution-test-oxygen/115
> 
> BR/Luis
> 
> 
>> 
>> Thanks,
>> Faseela
>> 
>> From: Sam Hague [mailto:sha...@redhat.com] 
>> Sent: Wednesday, January 17, 2018 6:54 PM
>> To: Faseela K 
>> Cc: Luis Gomez ; Abhijit Kumbhare ; 
>>  ; Brady 
>> Johnson ; Release (rele...@lists.opendaylight.org) 
>> ; Dayavanti Gopal Kamath 
>> ; TSC ; 
>> Stephen Kitt ; N Vivekanandan 
>> Subject: Re: [release] [OpenDaylight Discuss] [OpenDaylight TSC] odlparent 3 
>> / yangtools 2 migration
>> 
>> Please hold off on merging non bump patches until the issues are fixed.
>> 
>> Would like to reiterate that csit is failing horribly in many cases so 
>> projects should hold off on merging any non bump patches. We don't want to 
>> introduce further instability. This could all still be reverted if the 
>> underlying issues can't be fixed as we are past our deadline for the 
>> activity. 
>> 
>> On Jan 17, 2018 5:43 AM, "Faseela K"  wrote:
>> Thanks Luiz!
>> This should help us to get our pending patches in.
>> 
>> Thanks,
>> Faseela
>> 
>> From: Luis Gomez [mailto:ece...@gmail.com] 
>> Sent: Wednesday, January 17, 2018 3:46 PM
>> To: Abhijit Kumbhare 
>> Cc: Brady Johnson ; Kitt, Stephen ; 
>> tsc ; OpenDaylight Discuss 
>> ; Release (rele...@lists.opendaylight.org) 
>> ; Faseela K 
>> Subject: Re: [OpenDaylight Discuss] [release] [OpenDaylight TSC] odlparent 3 
>> / yangtools 2 migration
>> 
>> FYI, we are now building distribution with all projects except those pending 
>> the bump patch: alto, eman, faas, gbp, memo, nic, of-config, p4plugin, 
>> packetcable, snmp4sdn, tsdr, unimgr, usc and vtn:
>> 
>> https://jenkins.opendaylight.org/releng/view/distribution/job/distribution-merge-oxygen/1569/
>> 
>> - Distribution-check should work after 
>> https://git.opendaylight.org/gerrit/#/c/67229/
>> - Autorelease-validate should work after removing above projects from 
>> autorelease.
>> 
>> BR/Luis
>> 
>> 
>> On Jan 16, 2018, at 11:26 PM, Abhijit Kumbhare  wrote:
>> 
>> Thanks for all the work on this folks (too many to name: Stephen, Michael, 
>> Luis, Jamo, Tom, Robert, Sam, Brady, Faseela, etc.). About the original 
>> question Stephen from your email:
>> 
>> "So the question now is what do we do. Following the agreed plan, we
>> should start reverting the patches (hopefully without messing up the
>> follow-up fixes). We could formulate alternative plans, but I’m not
>> sure what the community feels about that!"
>> 
>> Do you guys (particularly Stephen & Michael since they may have been 
>> involved on this

Re: [OpenDaylight Discuss] [release] [OpenDaylight TSC] odlparent 3 / yangtools 2 migration

[Luis Gomez]

> On Jan 17, 2018, at 7:52 AM, Faseela K  wrote:
> 
> Yes Sam.
> We are not going to merge anything till the builds pass, and tests pass.
> Luis’ mail had pointers that we will be able to soon build distribution, as 
> we are planning to remove projects pending the bump patches.

I did already that in int/distribution so that we can at least get something 
tested in CSIT. I think logical next step is:

- For all projects that have not successfully merged the bump patch yet [1], 
work on that and report any problem.
- For all projects that have already merged the bump patch and are part of the 
distribution (the remaining projects), check CSIT results of next distribution 
test [2] and report any issue you notice.

For the second expect the following known issues:

- Topology model version problem: 
https://lists.opendaylight.org/pipermail/openflowplugin-dev/2018-January/007912.html
- Change of karaf prompt can make test very slow: 
https://lists.opendaylight.org/pipermail/release/2018-January/013412.html
- Error booting some feature: it could be because of this: 
https://git.opendaylight.org/gerrit/#/c/67229/

[1] alto, eman, faas, gbp, memo, nic, of-config, p4plugin, packetcable, 
snmp4sdn, tsdr, unimgr, usc, vtn
[2] 
https://jenkins.opendaylight.org/releng/view/distribution/job/integration-distribution-test-oxygen/115

BR/Luis


>  
> Thanks,
> Faseela
>  
> From: Sam Hague [mailto:sha...@redhat.com] 
> Sent: Wednesday, January 17, 2018 6:54 PM
> To: Faseela K 
> Cc: Luis Gomez ; Abhijit Kumbhare ; 
>  ; Brady 
> Johnson ; Release (rele...@lists.opendaylight.org) 
> ; Dayavanti Gopal Kamath 
> ; TSC ; 
> Stephen Kitt ; N Vivekanandan 
> Subject: Re: [release] [OpenDaylight Discuss] [OpenDaylight TSC] odlparent 3 
> / yangtools 2 migration
>  
> Please hold off on merging non bump patches until the issues are fixed.
>  
> Would like to reiterate that csit is failing horribly in many cases so 
> projects should hold off on merging any non bump patches. We don't want to 
> introduce further instability. This could all still be reverted if the 
> underlying issues can't be fixed as we are past our deadline for the 
> activity. 
>  
> On Jan 17, 2018 5:43 AM, "Faseela K"  wrote:
> Thanks Luiz!
> This should help us to get our pending patches in.
>  
> Thanks,
> Faseela
>  
> From: Luis Gomez [mailto:ece...@gmail.com] 
> Sent: Wednesday, January 17, 2018 3:46 PM
> To: Abhijit Kumbhare 
> Cc: Brady Johnson ; Kitt, Stephen ; 
> tsc ; OpenDaylight Discuss 
> ; Release (rele...@lists.opendaylight.org) 
> ; Faseela K 
> Subject: Re: [OpenDaylight Discuss] [release] [OpenDaylight TSC] odlparent 3 
> / yangtools 2 migration
>  
> FYI, we are now building distribution with all projects except those pending 
> the bump patch: alto, eman, faas, gbp, memo, nic, of-config, p4plugin, 
> packetcable, snmp4sdn, tsdr, unimgr, usc and vtn:
>  
> https://jenkins.opendaylight.org/releng/view/distribution/job/distribution-merge-oxygen/1569/
>  
> - Distribution-check should work after 
> https://git.opendaylight.org/gerrit/#/c/67229/
> - Autorelease-validate should work after removing above projects from 
> autorelease.
>  
> BR/Luis
>  
>  
> On Jan 16, 2018, at 11:26 PM, Abhijit Kumbhare  wrote:
>  
> Thanks for all the work on this folks (too many to name: Stephen, Michael, 
> Luis, Jamo, Tom, Robert, Sam, Brady, Faseela, etc.). About the original 
> question Stephen from your email:
>  
> "So the question now is what do we do. Following the agreed plan, we
> should start reverting the patches (hopefully without messing up the
> follow-up fixes). We could formulate alternative plans, but I’m not
> sure what the community feels about that!"
>  
> Do you guys (particularly Stephen & Michael since they may have been involved 
> on this the most) feel that we should decide this over the email thread or 
> does it make sense to wait till the TSC meeting? Of course a few folks like 
> Michael & Faseela may not be able to attend the TSC meeting - and can 
> continue to provide their response over this thread. 
>  
> On Tue, Jan 16, 2018 at 8:44 PM, Brady Johnson  wrote:
> The SFC patch has merged successfully, so now the Netvirt version bump patch 
> can be merged.
>  
> Regards,
>  
> Brady
>  
>  
> On Jan 16, 2018 21:32, "Luis Gomez"  wrote:
>  
> On Jan 16, 2018, at 4:35 PM, Faseela K  wrote:
>  
> Hi,
> If there was an option to do such major impact changes on a different 
> branch, and then get it merged to main branch when things are stable 
> enough.(given that such a version bump-up is happening almost at the same 
> time as we are going to do a branch cut), would have been far better.

Re: [OpenDaylight Discuss] [OpenDaylight TSC] [release] ONS Developer Event

[Luis Gomez]

I am also 1>3>2>4

> On Jan 17, 2018, at 7:29 AM, Thanh Ha  wrote:
> 
> On Wed, Jan 17, 2018 at 10:05 AM, Daniel Farrell  > wrote:
> Bumping this thread because we really need to get to a resolution ASAP, folks 
> need to book travel.
> 
> The options I've seen:
> 
> 1. DDF on Thursday/Friday before ONS. Very long trip, but no conflicts.
> 2. DDF on Sunday before ONS. Conflicts with XCI event, working on the weekend 
> sucks.
> 3. DDF during Mon/Tue of ONS. Conflicts with cross-community collaboration 
> event. Unclear if cross-community event has two full days of relevant 
> content. Maybe possible to time-slice in a way that minimizes conflict (DDF 
> in the morning, cross-community events involving ODL in the afternoon).
> 4. Have a virtual DDF. Likely not as productive, little support voiced so far.
> 
> I prefer 1 or 3, since the XCI event is critical for me.
> 
> Personally I prefer options 1 and 3 as well (with a slightly higher 
> preference for 1 but am happy with either). I do not think a virtual DDFs 
> will be very productive, the main benefit of the DDF imo is a the random 
> hallway conversations which we won't be able to get from a virtual meeting.
> 
> Regards,
> Thanh
> 
> ___
> TSC mailing list
> t...@lists.opendaylight.org
> https://lists.opendaylight.org/mailman/listinfo/tsc

___
Discuss mailing list
Discuss@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/discuss

Re: [OpenDaylight Discuss] [release] [OpenDaylight TSC] odlparent 3 / yangtools 2 migration

[Luis Gomez]

FYI, we are now building distribution with all projects except those pending 
the bump patch: alto, eman, faas, gbp, memo, nic, of-config, p4plugin, 
packetcable, snmp4sdn, tsdr, unimgr, usc and vtn:

https://jenkins.opendaylight.org/releng/view/distribution/job/distribution-merge-oxygen/1569/
 
<https://jenkins.opendaylight.org/releng/view/distribution/job/distribution-merge-oxygen/1569/>

- Distribution-check should work after 
https://git.opendaylight.org/gerrit/#/c/67229/ 
<https://git.opendaylight.org/gerrit/#/c/67229/>
- Autorelease-validate should work after removing above projects from 
autorelease.

BR/Luis


> On Jan 16, 2018, at 11:26 PM, Abhijit Kumbhare  wrote:
> 
> Thanks for all the work on this folks (too many to name: Stephen, Michael, 
> Luis, Jamo, Tom, Robert, Sam, Brady, Faseela, etc.). About the original 
> question Stephen from your email:
> 
> "So the question now is what do we do. Following the agreed plan, we
> should start reverting the patches (hopefully without messing up the
> follow-up fixes). We could formulate alternative plans, but I’m not
> sure what the community feels about that!"
> 
> Do you guys (particularly Stephen & Michael since they may have been involved 
> on this the most) feel that we should decide this over the email thread or 
> does it make sense to wait till the TSC meeting? Of course a few folks like 
> Michael & Faseela may not be able to attend the TSC meeting - and can 
> continue to provide their response over this thread. 
> 
> On Tue, Jan 16, 2018 at 8:44 PM, Brady Johnson  <mailto:bjohn...@inocybe.ca>> wrote:
> The SFC patch has merged successfully, so now the Netvirt version bump patch 
> can be merged.
> 
> Regards,
> 
> Brady
> 
> 
> On Jan 16, 2018 21:32, "Luis Gomez"  <mailto:ece...@gmail.com>> wrote:
> 
>> On Jan 16, 2018, at 4:35 PM, Faseela K > <mailto:faseel...@ericsson.com>> wrote:
>> 
>> Hi,
>> If there was an option to do such major impact changes on a different 
>> branch, and then get it merged to main branch when things are stable 
>> enough.(given that such a version bump-up is happening almost at the same 
>> time as we are going to do a branch cut), would have been far better.  
> 
> I am not sure how a development branch would have helped here. In general to 
> catch issues related to upstream bump before projects perform the bump we can:
> 
> - Prepare patches for everybody and use recheck with patch dependency: this 
> worked pretty well for me and helped identifying some issues. Problem is 
> someone has to prepare the patches and this method does not generate a 
> distribution to test.
> - Prepare patches for everybody and use multi-patch job: It is similar to the 
> above but builds in a different way, because of that it cannot be used for a 
> major bump change as it is today but this is fixable and this job does 
> actually generate a distribution and trigger CSIT if required.
> - Have an automatic upstream bump job 
> (https://jira.opendaylight.org/projects/RELENG/issues/RELENG-69 
> <https://jira.opendaylight.org/projects/RELENG/issues/RELENG-69>): This is 
> not there yet but I believe it is very feasible once we have an streamlined 
> distribution with stable autorelease build.
> 
> Now I have to say that nothing of the above really works if all projects 
> involved in the change are not actively looking at the issues exposed by the 
> above methods, fixing them and reporting them to upstream when they cannot. I 
> think this last is what is really failing today and explains why upstream and 
> ultimately TSC decided to break everybody for a while rather than going 
> through the painful (and slow) process of asking one by one all projects to 
> check the bump change. 
> 
> BR/Luis
> 
> 
>>But would like to tell that some of the issues we had with the previous 
>> versions seem to go off once we got a stable genius distribution(eg : ssh 
>> related problems as sshd got upgraded). 
>> Thanks,
>> Faseela
>>  
>> From: release-boun...@lists.opendaylight.org 
>> <mailto:release-boun...@lists.opendaylight.org> 
>> [mailto:release-boun...@lists.opendaylight.org 
>> <mailto:release-boun...@lists.opendaylight.org>] On Behalf Of Luis Gomez
>> Sent: Wednesday, January 17, 2018 5:58 AM
>> To: Jamo Luhrsen mailto:jluhr...@gmail.com>>
>> Cc: Stephen Kitt mailto:sk...@redhat.com>>; OpenDaylight 
>> Discuss > <mailto:discuss@lists.opendaylight.org>>; Release 
>> (rele...@lists.opendaylight.org <mailto:rele...@lists.opendaylight.org>) 
>> mailto:rele...@lists.opendaylight.org>>; 
>> tsc mailt

Re: [OpenDaylight Discuss] [release] [OpenDaylight TSC] odlparent 3 / yangtools 2 migration

[Luis Gomez]

On the other hand if odlparent and yangtools were in SR like before, it would 
make sense for them to use a developer branch that would be merged in a 
controlled way to produce minimal impact in downstream. In fact if these 
projects were still in SR: 1) their patches or branches could be easier 
verified in the downstream using existing tools, 2) there would be no need for 
other projects to wait for next available release to get bug fixes, and 3)  
there would be no need for other projects to bump versions during the release 
cycle (this has become painful even for small bumps). So today I do not see 
much gain in separating these projects but it could be that we are in a 
transition phase and things will get better in 1 or 2 releases from now.

BR/Luis

> On Jan 16, 2018, at 7:32 PM, Luis Gomez  wrote:
> 
> 
>> On Jan 16, 2018, at 4:35 PM, Faseela K > <mailto:faseel...@ericsson.com>> wrote:
>> 
>> Hi,
>> If there was an option to do such major impact changes on a different 
>> branch, and then get it merged to main branch when things are stable 
>> enough.(given that such a version bump-up is happening almost at the same 
>> time as we are going to do a branch cut), would have been far better.  
> 
> I am not sure how a development branch would have helped here. In general to 
> catch issues related to upstream bump before projects perform the bump we can:
> 
> - Prepare patches for everybody and use recheck with patch dependency: this 
> worked pretty well for me and helped identifying some issues. Problem is 
> someone has to prepare the patches and this method does not generate a 
> distribution to test.
> - Prepare patches for everybody and use multi-patch job: It is similar to the 
> above but builds in a different way, because of that it cannot be used for a 
> major bump change as it is today but this is fixable and this job does 
> actually generate a distribution and trigger CSIT if required.
> - Have an automatic upstream bump job 
> (https://jira.opendaylight.org/projects/RELENG/issues/RELENG-69 
> <https://jira.opendaylight.org/projects/RELENG/issues/RELENG-69>): This is 
> not there yet but I believe it is very feasible once we have an streamlined 
> distribution with stable autorelease build.
> 
> Now I have to say that nothing of the above really works if all projects 
> involved in the change are not actively looking at the issues exposed by the 
> above methods, fixing them and reporting them to upstream when they cannot. I 
> think this last is what is really failing today and explains why upstream and 
> ultimately TSC decided to break everybody for a while rather than going 
> through the painful (and slow) process of asking one by one all projects to 
> check the bump change. 
> 
> BR/Luis
> 
> 
>>But would like to tell that some of the issues we had with the previous 
>> versions seem to go off once we got a stable genius distribution(eg : ssh 
>> related problems as sshd got upgraded). 
>> Thanks,
>> Faseela
>>  
>> From: release-boun...@lists.opendaylight.org 
>> <mailto:release-boun...@lists.opendaylight.org> 
>> [mailto:release-boun...@lists.opendaylight.org 
>> <mailto:release-boun...@lists.opendaylight.org>] On Behalf Of Luis Gomez
>> Sent: Wednesday, January 17, 2018 5:58 AM
>> To: Jamo Luhrsen mailto:jluhr...@gmail.com>>
>> Cc: Stephen Kitt mailto:sk...@redhat.com>>; OpenDaylight 
>> Discuss > <mailto:discuss@lists.opendaylight.org>>; Release 
>> (rele...@lists.opendaylight.org <mailto:rele...@lists.opendaylight.org>) 
>> mailto:rele...@lists.opendaylight.org>>; 
>> tsc mailto:t...@lists.opendaylight.org>>
>> Subject: Re: [release] [OpenDaylight TSC] odlparent 3 / yangtools 2 migration
>>  
>> FYI I am trying this patch in sandbox for the issue you observed in CSIT:
>>  
>> https://git.opendaylight.org/gerrit/#/c/67224/ 
>> <https://git.opendaylight.org/gerrit/#/c/67224/>
>>  
>> BR/Luis
>>  
>>  
>> On Jan 16, 2018, at 1:56 PM, Jamo Luhrsen > <mailto:jluhr...@gmail.com>> wrote:
>>  
>> good idea Sam. I'll try that.
>> 
>> btw, you could do a curl on restconf/modules and get a 200 right?
>> 
>> JamO
>> 
>> On 01/16/2018 01:55 PM, Sam Hague wrote:
>> 
>> I loaded that distro locally and did feature:install odl-netvirt-openstack. 
>> That worked fine. Maybe we can use the patch you
>> added recently to not use the bootfeatures?
>> 
>> On Jan 16, 2018 4:02 PM, "Jamo Luhrsen" > <mailto:jluhr...@gmail.com><mailto:jluhr...@gmail.com 
>> <mailto:jluhr...@gmail.com&

Re: [OpenDaylight Discuss] [release] [OpenDaylight TSC] odlparent 3 / yangtools 2 migration

[Luis Gomez]

> On Jan 16, 2018, at 4:35 PM, Faseela K  wrote:
> 
> Hi,
> If there was an option to do such major impact changes on a different 
> branch, and then get it merged to main branch when things are stable 
> enough.(given that such a version bump-up is happening almost at the same 
> time as we are going to do a branch cut), would have been far better.  

I am not sure how a development branch would have helped here. In general to 
catch issues related to upstream bump before projects perform the bump we can:

- Prepare patches for everybody and use recheck with patch dependency: this 
worked pretty well for me and helped identifying some issues. Problem is 
someone has to prepare the patches and this method does not generate a 
distribution to test.
- Prepare patches for everybody and use multi-patch job: It is similar to the 
above but builds in a different way, because of that it cannot be used for a 
major bump change as it is today but this is fixable and this job does actually 
generate a distribution and trigger CSIT if required.
- Have an automatic upstream bump job 
(https://jira.opendaylight.org/projects/RELENG/issues/RELENG-69): This is not 
there yet but I believe it is very feasible once we have an streamlined 
distribution with stable autorelease build.

Now I have to say that nothing of the above really works if all projects 
involved in the change are not actively looking at the issues exposed by the 
above methods, fixing them and reporting them to upstream when they cannot. I 
think this last is what is really failing today and explains why upstream and 
ultimately TSC decided to break everybody for a while rather than going through 
the painful (and slow) process of asking one by one all projects to check the 
bump change. 

BR/Luis


>But would like to tell that some of the issues we had with the previous 
> versions seem to go off once we got a stable genius distribution(eg : ssh 
> related problems as sshd got upgraded). 
> Thanks,
> Faseela
>  
> From: release-boun...@lists.opendaylight.org 
> [mailto:release-boun...@lists.opendaylight.org] On Behalf Of Luis Gomez
> Sent: Wednesday, January 17, 2018 5:58 AM
> To: Jamo Luhrsen 
> Cc: Stephen Kitt ; OpenDaylight Discuss 
> ; Release (rele...@lists.opendaylight.org) 
> ; tsc 
> Subject: Re: [release] [OpenDaylight TSC] odlparent 3 / yangtools 2 migration
>  
> FYI I am trying this patch in sandbox for the issue you observed in CSIT:
>  
> https://git.opendaylight.org/gerrit/#/c/67224/ 
> <https://git.opendaylight.org/gerrit/#/c/67224/>
>  
> BR/Luis
>  
>  
> On Jan 16, 2018, at 1:56 PM, Jamo Luhrsen  <mailto:jluhr...@gmail.com>> wrote:
>  
> good idea Sam. I'll try that.
> 
> btw, you could do a curl on restconf/modules and get a 200 right?
> 
> JamO
> 
> On 01/16/2018 01:55 PM, Sam Hague wrote:
> 
> I loaded that distro locally and did feature:install odl-netvirt-openstack. 
> That worked fine. Maybe we can use the patch you
> added recently to not use the bootfeatures?
> 
> On Jan 16, 2018 4:02 PM, "Jamo Luhrsen"  <mailto:jluhr...@gmail.com><mailto:jluhr...@gmail.com 
> <mailto:jluhr...@gmail.com>>> wrote:
> 
>Thanks Luis,
> 
>that fixed it, and I ran new jobs already. ODL did not come "UP", so we 
> have something to fix still.
> 
>I'll be debugging, but something weird ended up in the features cfg file.
>there is an UUID in the featuresBoot and featuresRepositories lines
> 
>
> https://jenkins.opendaylight.org/releng/user/jluhrsen/my-views/view/netvirt%20csit/job/netvirt-csit-1node-openstack-ocata-gate-stateful-oxygen/638/
>  
> <https://jenkins.opendaylight.org/releng/user/jluhrsen/my-views/view/netvirt%20csit/job/netvirt-csit-1node-openstack-ocata-gate-stateful-oxygen/638/>
>
> <https://jenkins.opendaylight.org/releng/user/jluhrsen/my-views/view/netvirt%20csit/job/netvirt-csit-1node-openstack-ocata-gate-stateful-oxygen/638/
>  
> <https://jenkins.opendaylight.org/releng/user/jluhrsen/my-views/view/netvirt%20csit/job/netvirt-csit-1node-openstack-ocata-gate-stateful-oxygen/638/>>
> 
>JamO
> 
> 
> 
>On 01/16/2018 12:38 PM, Luis Gomez wrote:
> 
> I mean the format of the URL so that script can take it :)
> 
> Just add 2 folders (/karaf/0.8.0-SNAPSHOT) in you HTTP server and it should 
> work, for example:
>
> http://www.luhrsenlounge.net/odl/karaf/0.8.0-SNAPSHOT/karaf-0.8.0-SNAPSHOT.zip
>  
> <http://www.luhrsenlounge.net/odl/karaf/0.8.0-SNAPSHOT/karaf-0.8.0-SNAPSHOT.zip>
>
> <http://www.luhrsenlounge.net/odl/karaf/0.8.0-SNAPSHOT/karaf-0.8.0-SNAPSHOT.zip
>  
> <http://www.luhrsenlounge.net/odl/karaf/0.8.0-SNAPSHOT/karaf-0.8.0-SNAPSHOT.zip>

Re: [OpenDaylight Discuss] [OpenDaylight TSC] [release] odlparent 3 / yangtools 2 migration

[Luis Gomez]

FYI I am trying this patch in sandbox for the issue you observed in CSIT:

https://git.opendaylight.org/gerrit/#/c/67224/ 
<https://git.opendaylight.org/gerrit/#/c/67224/>

BR/Luis


> On Jan 16, 2018, at 1:56 PM, Jamo Luhrsen  wrote:
> 
> good idea Sam. I'll try that.
> 
> btw, you could do a curl on restconf/modules and get a 200 right?
> 
> JamO
> 
> On 01/16/2018 01:55 PM, Sam Hague wrote:
>> I loaded that distro locally and did feature:install odl-netvirt-openstack. 
>> That worked fine. Maybe we can use the patch you
>> added recently to not use the bootfeatures?
>> 
>> On Jan 16, 2018 4:02 PM, "Jamo Luhrsen" > <mailto:jluhr...@gmail.com>> wrote:
>> 
>>Thanks Luis,
>> 
>>that fixed it, and I ran new jobs already. ODL did not come "UP", so we 
>> have something to fix still.
>> 
>>I'll be debugging, but something weird ended up in the features cfg file.
>>there is an UUID in the featuresBoot and featuresRepositories lines
>> 
>>
>> https://jenkins.opendaylight.org/releng/user/jluhrsen/my-views/view/netvirt%20csit/job/netvirt-csit-1node-openstack-ocata-gate-stateful-oxygen/638/
>>
>> <https://jenkins.opendaylight.org/releng/user/jluhrsen/my-views/view/netvirt%20csit/job/netvirt-csit-1node-openstack-ocata-gate-stateful-oxygen/638/>
>> 
>>JamO
>> 
>> 
>> 
>>On 01/16/2018 12:38 PM, Luis Gomez wrote:
>>> I mean the format of the URL so that script can take it :)
>>> 
>>> Just add 2 folders (/karaf/0.8.0-SNAPSHOT) in you HTTP server and it should 
>>> work, for example:
>>
>> http://www.luhrsenlounge.net/odl/karaf/0.8.0-SNAPSHOT/karaf-0.8.0-SNAPSHOT.zip
>>
>> <http://www.luhrsenlounge.net/odl/karaf/0.8.0-SNAPSHOT/karaf-0.8.0-SNAPSHOT.zip>
>>> 
>>>> On Jan 16, 2018, at 12:35 PM, Jamo Luhrsen >>> <mailto:jluhr...@gmail.com>> wrote:
>>>> 
>>>> 
>>>> 
>>>> On 01/16/2018 12:27 PM, Luis Gomez wrote:
>>>>> I think you have to use something like this in the
>>>>> BUNDLE_URL: 
>>>>> http://www.luhrsenlounge.net/odl/*karaf/0.8.0-SNAPSHOT*/karaf-0.8.0-SNAPSHOT.zip
>>
>> <http://www.luhrsenlounge.net/odl/*karaf/0.8.0-SNAPSHOT*/karaf-0.8.0-SNAPSHOT.zip>
>>>> 
>>>> hmmm... the BUNDLE_URL is right, but our deployment script is having 
>>>> trouble using
>>>> it. I'm looking.
>>>> 
>>>>>> On Jan 16, 2018, at 11:51 AM, Jamo Luhrsen >>>>> <mailto:jluhr...@gmail.com>
>><mailto:jluhr...@gmail.com <mailto:jluhr...@gmail.com>>> wrote:
>>>>>> 
>>>>>> Sam built a local distro with the remaining unmerged patches
>>>>>> and I am trying some netvirt CSIT with that:
>>>>>> 
>>>>>> 
>>
>> https://jenkins.opendaylight.org/releng/user/jluhrsen/my-views/view/netvirt%20csit/job/netvirt-csit-1node-openstack-ocata-gate-stateful-oxygen/637
>>
>> <https://jenkins.opendaylight.org/releng/user/jluhrsen/my-views/view/netvirt%20csit/job/netvirt-csit-1node-openstack-ocata-gate-stateful-oxygen/637>
>>>>>> 
>>>>>> 
>>
>> https://jenkins.opendaylight.org/releng/user/jluhrsen/my-views/view/netvirt%20csit/job/netvirt-csit-1node-openstack-ocata-gate-stateful-snat-conntrack-oxygen/38
>>
>> <https://jenkins.opendaylight.org/releng/user/jluhrsen/my-views/view/netvirt%20csit/job/netvirt-csit-1node-openstack-ocata-gate-stateful-snat-conntrack-oxygen/38>
>>>>>> 
>>>>>> 
>>>>>> JamO
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> On 01/16/2018 11:07 AM, Michael Vorburger wrote:
>>>>>>> On Tue, Jan 16, 2018 at 7:29 PM, Brady Johnson >>>>>> <mailto:bjohn...@inocybe.ca>
>><mailto:bjohn...@inocybe.ca <mailto:bjohn...@inocybe.ca>>> wrote:
>>>>>>> 
>>>>>>> We have indeed made good progress and it looks like we're close. 
>>>>>>> Should we at least give it until the end of the
>>day today?
>>>>>>> 
>>>>>>> Related to this, since the merges started I havent been able to 
>>>>>>> build SFC since Friday when I sent this email
>>[0] and I
>>>>>>> still cant today. So this is something we need to resolve soo

Re: [OpenDaylight Discuss] [OpenDaylight TSC] [release] odlparent 3 / yangtools 2 migration

[Luis Gomez]

Yeah, thats another thing, we may have to change current CSIT scripts to 
accommodate new features boot file format.

> On Jan 16, 2018, at 1:02 PM, Jamo Luhrsen  wrote:
> 
> Thanks Luis,
> 
> that fixed it, and I ran new jobs already. ODL did not come "UP", so we have 
> something to fix still.
> 
> I'll be debugging, but something weird ended up in the features cfg file.
> there is an UUID in the featuresBoot and featuresRepositories lines
> 
> https://jenkins.opendaylight.org/releng/user/jluhrsen/my-views/view/netvirt%20csit/job/netvirt-csit-1node-openstack-ocata-gate-stateful-oxygen/638/
> 
> JamO
> 
> 
> 
> On 01/16/2018 12:38 PM, Luis Gomez wrote:
>> I mean the format of the URL so that script can take it :)
>> 
>> Just add 2 folders (/karaf/0.8.0-SNAPSHOT) in you HTTP server and it should 
>> work, for example: 
>> http://www.luhrsenlounge.net/odl/karaf/0.8.0-SNAPSHOT/karaf-0.8.0-SNAPSHOT.zip
>> 
>>> On Jan 16, 2018, at 12:35 PM, Jamo Luhrsen  wrote:
>>> 
>>> 
>>> 
>>> On 01/16/2018 12:27 PM, Luis Gomez wrote:
>>>> I think you have to use something like this in the
>>>> BUNDLE_URL: 
>>>> http://www.luhrsenlounge.net/odl/*karaf/0.8.0-SNAPSHOT*/karaf-0.8.0-SNAPSHOT.zip
>>> 
>>> hmmm... the BUNDLE_URL is right, but our deployment script is having 
>>> trouble using
>>> it. I'm looking.
>>> 
>>>>> On Jan 16, 2018, at 11:51 AM, Jamo Luhrsen >>>> <mailto:jluhr...@gmail.com>> wrote:
>>>>> 
>>>>> Sam built a local distro with the remaining unmerged patches
>>>>> and I am trying some netvirt CSIT with that:
>>>>> 
>>>>> https://jenkins.opendaylight.org/releng/user/jluhrsen/my-views/view/netvirt%20csit/job/netvirt-csit-1node-openstack-ocata-gate-stateful-oxygen/637
>>>>> 
>>>>> https://jenkins.opendaylight.org/releng/user/jluhrsen/my-views/view/netvirt%20csit/job/netvirt-csit-1node-openstack-ocata-gate-stateful-snat-conntrack-oxygen/38
>>>>> 
>>>>> 
>>>>> JamO
>>>>> 
>>>>> 
>>>>> 
>>>>> On 01/16/2018 11:07 AM, Michael Vorburger wrote:
>>>>>> On Tue, Jan 16, 2018 at 7:29 PM, Brady Johnson >>>>> <mailto:bjohn...@inocybe.ca>> wrote:
>>>>>> 
>>>>>>   We have indeed made good progress and it looks like we're close. 
>>>>>> Should we at least give it until the end of the day today?
>>>>>> 
>>>>>>   Related to this, since the merges started I havent been able to build 
>>>>>> SFC since Friday when I sent this email [0] and I
>>>>>>   still cant today. So this is something we need to resolve soon to 
>>>>>> avoid schedule slips.
>>>>>> 
>>>>>>   [0] 
>>>>>> https://lists.opendaylight.org/pipermail/release/2018-January/013337.html
>>>>>>   
>>>>>> <https://lists.opendaylight.org/pipermail/release/2018-January/013337.html>
>>>>>> 
>>>>>> 
>>>>>>   Regards,
>>>>>> 
>>>>>>   *Brady Johnson*
>>>>>>   bjohn...@inocybe.ca <mailto:bjohn...@inocybe.ca>
>>>>>> 
>>>>>>   
>>>>>> <https://twitter.com/inocybetech><http://www.inocybe.com/><https://www.linkedin.com/company/2661537?trk=tyah&trkInfo=clickedVertical%3Acompany%2CclickedEntityId%3A2661537%2Cidx%3A1-1-1%2CtarId%3A1441300264767%2Ctas%3Ainocybe>Screenshot
>>>>>>   2017-02-14 at 10.43.55 AM.png 
>>>>>> <https://www.youtube.com/channel/UC9uUWABdPR0Je9Du_15FCkw>
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>>   On Tue, Jan 16, 2018 at 8:31 AM, Stephen Kitt >>>>> <mailto:sk...@redhat.com>> wrote:
>>>>>> 
>>>>>>   Hi,
>>>>>> 
>>>>>>   In last week’s TSC call we agreed to move forward with merging the
>>>>>>   odlparent 3 / yangtools 2 migration patches, with a timebox — we 
>>>>>> were
>>>>>>   supposed to be able to run NetVirt CSIT yesterday. Obviously that
>>>>>>   deadline has gone whizzing past and we’re still some way away from
>>>>>>   running NetVirt CSIT; I’m not sure how far away... Strictly 
>>>>>> speaking

Re: [OpenDaylight Discuss] [OpenDaylight TSC] [release] odlparent 3 / yangtools 2 migration

[Luis Gomez]

I mean the format of the URL so that script can take it :)

Just add 2 folders (/karaf/0.8.0-SNAPSHOT) in you HTTP server and it should 
work, for example: 
http://www.luhrsenlounge.net/odl/karaf/0.8.0-SNAPSHOT/karaf-0.8.0-SNAPSHOT.zip

> On Jan 16, 2018, at 12:35 PM, Jamo Luhrsen  wrote:
> 
> 
> 
> On 01/16/2018 12:27 PM, Luis Gomez wrote:
>> I think you have to use something like this in the
>> BUNDLE_URL: 
>> http://www.luhrsenlounge.net/odl/*karaf/0.8.0-SNAPSHOT*/karaf-0.8.0-SNAPSHOT.zip
> 
> hmmm... the BUNDLE_URL is right, but our deployment script is having trouble 
> using
> it. I'm looking.
> 
>>> On Jan 16, 2018, at 11:51 AM, Jamo Luhrsen >> <mailto:jluhr...@gmail.com>> wrote:
>>> 
>>> Sam built a local distro with the remaining unmerged patches
>>> and I am trying some netvirt CSIT with that:
>>> 
>>> https://jenkins.opendaylight.org/releng/user/jluhrsen/my-views/view/netvirt%20csit/job/netvirt-csit-1node-openstack-ocata-gate-stateful-oxygen/637
>>> 
>>> https://jenkins.opendaylight.org/releng/user/jluhrsen/my-views/view/netvirt%20csit/job/netvirt-csit-1node-openstack-ocata-gate-stateful-snat-conntrack-oxygen/38
>>> 
>>> 
>>> JamO
>>> 
>>> 
>>> 
>>> On 01/16/2018 11:07 AM, Michael Vorburger wrote:
>>>> On Tue, Jan 16, 2018 at 7:29 PM, Brady Johnson >>> <mailto:bjohn...@inocybe.ca>> wrote:
>>>> 
>>>>We have indeed made good progress and it looks like we're close. Should 
>>>> we at least give it until the end of the day today?
>>>> 
>>>>Related to this, since the merges started I havent been able to build 
>>>> SFC since Friday when I sent this email [0] and I
>>>>still cant today. So this is something we need to resolve soon to avoid 
>>>> schedule slips.
>>>> 
>>>>[0] 
>>>> https://lists.opendaylight.org/pipermail/release/2018-January/013337.html
>>>>
>>>> <https://lists.opendaylight.org/pipermail/release/2018-January/013337.html>
>>>> 
>>>> 
>>>>Regards,
>>>> 
>>>>*Brady Johnson*
>>>>bjohn...@inocybe.ca <mailto:bjohn...@inocybe.ca>
>>>> 
>>>>
>>>> <https://twitter.com/inocybetech><http://www.inocybe.com/><https://www.linkedin.com/company/2661537?trk=tyah&trkInfo=clickedVertical%3Acompany%2CclickedEntityId%3A2661537%2Cidx%3A1-1-1%2CtarId%3A1441300264767%2Ctas%3Ainocybe>Screenshot
>>>>2017-02-14 at 10.43.55 AM.png 
>>>> <https://www.youtube.com/channel/UC9uUWABdPR0Je9Du_15FCkw>
>>>> 
>>>> 
>>>> 
>>>>On Tue, Jan 16, 2018 at 8:31 AM, Stephen Kitt >>> <mailto:sk...@redhat.com>> wrote:
>>>> 
>>>>Hi,
>>>> 
>>>>In last week’s TSC call we agreed to move forward with merging the
>>>>odlparent 3 / yangtools 2 migration patches, with a timebox — we 
>>>> were
>>>>supposed to be able to run NetVirt CSIT yesterday. Obviously that
>>>>deadline has gone whizzing past and we’re still some way away from
>>>>running NetVirt CSIT; I’m not sure how far away... Strictly 
>>>> speaking,
>>>>all the NetVirt dependencies now pass verify (thanks to lots of 
>>>> work by
>>>>Tom, Robert and Michael on Neutron in particular), so we could give 
>>>> it
>>>>a shot once the patches are merged, but I also knows that OVSDB 
>>>> fails
>>>>its IT so I expect NetVirt CSIT won’t pass.
>>>> 
>>>>So the question now is what do we do. Following the agreed plan, we
>>>>should start reverting the patches (hopefully without messing up the
>>>>follow-up fixes). We could formulate alternative plans, but I’m not
>>>>sure what the community feels about that!
>>>> 
>>>>Anyway, I’m not trying to suggest a concrete solution with this 
>>>> email,
>>>>I want to start the discussion.
>>>> 
>>>> 
>>>> my personal view is that the sane thing to do would be to revert and 
>>>> finish this up on a branch in parallel, to unblock
>>>> folks, because the timeline proposed in 
>>>> https://lists.opendaylight.org/pipermail/release/

Re: [OpenDaylight Discuss] [OpenDaylight TSC] [release] odlparent 3 / yangtools 2 migration

[Luis Gomez]

I think you have to use something like this in the BUNDLE_URL: 
http://www.luhrsenlounge.net/odl/karaf/0.8.0-SNAPSHOT/karaf-0.8.0-SNAPSHOT.zip

> On Jan 16, 2018, at 11:51 AM, Jamo Luhrsen  wrote:
> 
> Sam built a local distro with the remaining unmerged patches
> and I am trying some netvirt CSIT with that:
> 
> https://jenkins.opendaylight.org/releng/user/jluhrsen/my-views/view/netvirt%20csit/job/netvirt-csit-1node-openstack-ocata-gate-stateful-oxygen/637
> 
> https://jenkins.opendaylight.org/releng/user/jluhrsen/my-views/view/netvirt%20csit/job/netvirt-csit-1node-openstack-ocata-gate-stateful-snat-conntrack-oxygen/38
> 
> 
> JamO
> 
> 
> 
> On 01/16/2018 11:07 AM, Michael Vorburger wrote:
>> On Tue, Jan 16, 2018 at 7:29 PM, Brady Johnson > > wrote:
>> 
>>We have indeed made good progress and it looks like we're close. Should 
>> we at least give it until the end of the day today?
>> 
>>Related to this, since the merges started I havent been able to build SFC 
>> since Friday when I sent this email [0] and I
>>still cant today. So this is something we need to resolve soon to avoid 
>> schedule slips.
>> 
>>[0] 
>> https://lists.opendaylight.org/pipermail/release/2018-January/013337.html
>>
>> 
>> 
>> 
>>Regards,
>> 
>>*Brady Johnson*
>>bjohn...@inocybe.ca 
>> 
>>
>> Screenshot
>>2017-02-14 at 10.43.55 AM.png 
>> 
>> 
>> 
>> 
>>On Tue, Jan 16, 2018 at 8:31 AM, Stephen Kitt > > wrote:
>> 
>>Hi,
>> 
>>In last week’s TSC call we agreed to move forward with merging the
>>odlparent 3 / yangtools 2 migration patches, with a timebox — we were
>>supposed to be able to run NetVirt CSIT yesterday. Obviously that
>>deadline has gone whizzing past and we’re still some way away from
>>running NetVirt CSIT; I’m not sure how far away... Strictly speaking,
>>all the NetVirt dependencies now pass verify (thanks to lots of work 
>> by
>>Tom, Robert and Michael on Neutron in particular), so we could give it
>>a shot once the patches are merged, but I also knows that OVSDB fails
>>its IT so I expect NetVirt CSIT won’t pass.
>> 
>>So the question now is what do we do. Following the agreed plan, we
>>should start reverting the patches (hopefully without messing up the
>>follow-up fixes). We could formulate alternative plans, but I’m not
>>sure what the community feels about that!
>> 
>>Anyway, I’m not trying to suggest a concrete solution with this email,
>>I want to start the discussion.
>> 
>> 
>> my personal view is that the sane thing to do would be to revert and finish 
>> this up on a branch in parallel, to unblock
>> folks, because the timeline proposed in 
>> https://lists.opendaylight.org/pipermail/release/2018-January/013336.html 
>> was missed,
>> and IMHO it's likely at least several more days until things fully 
>> stabilize. Through all the various 3rd party upgrades and
>> yangtools changes etc. that went into this big bump, as of right there still 
>> has never been a full netvirt CSIT successfully
>> run proving non-regression, yet; that's going to happen in the coming days.
>> 
>> But I believe this view is not widely shared... ;-) Part of the reasons for 
>> that seem to include issues such as that the
>> multipatch job apparently doesn't work, so it is hard to test change accross 
>> projects easily. I'm not sure that "let's just
>> merge and figure it out as we go along" is the best answer to that problem.. 
>> but if others don't have a problem with the
>> "broken world" for a number of days, then so be it!
>>  
>> 
>>Regards,
>> 
>>--
>>Stephen Kitt
>>Principal Software Engineer, Office of the CTO
>>Red Hat
>> 
>>___
>>release mailing list
>>rele...@lists.opendaylight.org 
>>https://lists.opendaylight.org/mailman/listinfo/release 
>> 
>> 
>> 
>> 
>>___
>>TSC mailing list
>>t...@lists.opendaylight.org 
>>https://lists.opendaylight.org/mailman/listinfo/tsc 
>> 
>> 
>> 
>> 
>> 
>> ___
>> release mailing list
>> rele...@lists.opendaylight.org
>> https://lists.opendaylight.org/mailman/listinfo/release
>> 
> _

Re: [OpenDaylight Discuss] [OpenDaylight TSC] ONS Developer Event

[Luis Gomez]

Original mail from Casey seems to infer there is an overlap between ODL DDF and 
Mon-Tue collaborative developer forum between the Linux Foundation Networking 
projects. Casey, can you elaborate on the plan for the second and why there is 
a potential overlap with ODL DDF?

On the other hand I think we discussed this topic in the past and I remember we 
said keynotes and conference can be compatible with DDF because a contributor 
can always walk out for a conference he/she needs to give, and for other talks 
we can just watch the after event videos.

BR/Luis


> On Jan 5, 2018, at 11:59 AM, Tom Pantelis  wrote:
> 
> 
> 
> On Fri, Jan 5, 2018 at 2:35 PM, Abhijit Kumbhare  > wrote:
> That sounds a good plan to me - a parallel track. I understand that the first 
> two days are dedicated to a collaborative developer forum between the Linux 
> Foundation Networking projects and the next two days for keynotes and 
> conference tracks. But a dedicated room either on Monday-Tuesday or on 
> Wednesday-Thursday does not seem like a big ask. Also I doubt all the ODL (or 
> ONAP, FD.io , etc.) developers would be wanting to be part of 
> the collaborative developer forum all the time - we can have one or a half 
> day collaborative between projects & one day dedicated for ODL specific 
> topics. Alternately - we can have the developer track during the 
> keynotes/conference tracks.
> 
> If that simply cannot work - then my vote would be for Sunday or Friday. But 
> we will miss on attracting/recruiting some folks who have come to the ONS 
> anyway or currently working on other communities. Also many people find it 
> hard to attend for 5 full days of an event due to other commitments. 
> 
> +1. I'd suggest Mon or Tue in case some devs aren't staying for the keynotes 
> on Wed/Thu.  
>  
> 
> On Fri, Jan 5, 2018 at 10:56 AM, FREEMAN, BRIAN D  > wrote:
> Or what Tom P says :)
> 
>  
> 
> From: Tom Pantelis [mailto:tompante...@gmail.com 
> ] 
> Sent: Friday, January 05, 2018 1:44 PM
> To: FREEMAN, BRIAN D mailto:bf1...@att.com>>
> Cc: Anil Vishnoi mailto:vishnoia...@gmail.com>>; Ryan 
> Goulding mailto:ryandgould...@gmail.com>>; TSC 
> mailto:t...@lists.opendaylight.org>>; Release 
> mailto:rele...@lists.opendaylight.org>>; 
> discuss  >
> 
> 
> Subject: Re: [OpenDaylight Discuss] [OpenDaylight TSC] ONS Developer Event
> 
>  
> 
>  
> 
>  
> 
> On Fri, Jan 5, 2018 at 1:31 PM, FREEMAN, BRIAN D  > wrote:
> 
> Why dont we run a parallel track on thu/fri even if its afternoon only – LF 
> can get a room – I’m sure for a fee that is possible.
> 
>  
> 
> Why can't we do it Mon, Tue or Wed during the conference?
> 
>  
> 
>  
> 
> Brian
> 
>  
> 
>  
> 
> From: discuss-boun...@lists.opendaylight.org 
>  
> [mailto:discuss-boun...@lists.opendaylight.org 
> ] On Behalf Of Anil Vishnoi
> Sent: Friday, January 05, 2018 12:43 PM
> To: Ryan Goulding mailto:ryandgould...@gmail.com>>
> Cc: TSC mailto:t...@lists.opendaylight.org>>; 
> Release  >; discuss 
> mailto:discuss@lists.opendaylight.org>>
> Subject: Re: [OpenDaylight Discuss] [OpenDaylight TSC] ONS Developer Event
> 
>  
> 
> I share the same feeling, but i am not sure if we have any better alternative 
> here. 
> 
>  
> 
> Another option i was thinking of having the DDF the way we did last time at 
> Ericsson office but we can schedule it just after the ONS (Monday/Tuesday).
> 
>  
> 
> On Fri, Jan 5, 2018 at 8:41 AM, Ryan Goulding  > wrote:
> 
> I believe getting people to show up to work on a weekend, possibly from half 
> way across the globe, might be a little difficult.  My $0.02.
> 
>  
> 
> Can we not schedule a room during the week long event?  Seems depressing that 
> we are reduced to hosting this during a weekend or virtually, especially 
> considering the blowouts we have done in the past...
> 
> 
> 
> Regards,
> 
> Ryan Goulding
> 
>  
> 
> On Fri, Jan 5, 2018 at 10:37 AM, Thanh Ha  > wrote:
> 
> On Thu, Jan 4, 2018 at 8:09 PM, Casey Cain  > wrote:
> 
> The next developer event is rapidly approaching. The first two days of the 
> Open Networking Summit (link 
> 
>  March 26-29th) will be dedicated to a collaborative developer form between 
> the Linux Foundation Networking projects.  This will likely not allow for 
> enough time for the development community to focus on the Florine rel

Re: [OpenDaylight Discuss] [release] [it-infrastructure-alerts][notice] ODL maintenance window at 2:00p Wed, Dec 20 2017 - 4:30p Wed, Dec 20 2017 PST (10:00p Wed, Dec 20 - 12:30a Thu, Dec 21 UTC)

[Luis Gomez]

I am not sure other people but I cannot get any log from sandbox:

https://logs.opendaylight.org/sandbox/vex-yul-odl-jenkins-2/openflowplugin-csit-1node-cbench-only-nitrogen/4
 


It says: You don't have permission to access 
/sandbox/vex-yul-odl-jenkins-2/openflowplugin-csit-1node-cbench-only-nitrogen/4 
on this server.

> On Dec 20, 2017, at 5:01 PM, Andrew Grimberg  
> wrote:
> 
> This work has been completed.
> 
> A couple of notes:
> 
> 1) The Jenkins logs have not been fully synced from the old server. If
> you're looking for old logs, they may not be fully available. You can
> get around this by modifying your /etc/hosts file with the following
> entry to get to _old_ logs:
> 
> 72.3.167.142 logs.opendaylight.org 
> 
> 2) We forgot to lower the TTL on the DNS entry related to logs and
> javadocs so those entries are going to stick around for up to an hour
> before switching to the new location. As such, logs for jobs up until
> the maintenance may be visible to you while we're still syncing but
> _new_ stored logs may not be. This will correct itself as DNS expires in
> which case you'll be in the same situation as stated above.
> 
> -Andy-
> 
> On 12/20/2017 02:01 PM, Andrew Grimberg wrote:
>> Note: This work will be starting shortly.
>> 
>> -Andy-
>> 
>> On 12/19/2017 05:16 PM, Anil Belur wrote:
>>> What: LF will perform maintenance on ODL infrastructure to implement
>>> switch over to a git mirror and nexus.
>>> 
>>> When: 2:00p Wed, Dec 20 2017 - 4:30p Wed, Dec 20 2017 PST (10:00p Wed,
>>> Dec 20 - 12:30a Thu, Dec 21 UTC)
>>> 
>>> Why: LF will implement a switch over to a git mirror and an nexus
>>> instance (tentative if the data sync is complete) which should decrease
>>> any lag in accessing resources within the CI environment.
>>>  
>>> Impact: All ODL servers (Gerrit, Jenkins (sandbox/releng), Nexus,
>>> Spectrometer, Sonar, CLM) may be inaccessible during this time and
>>> Jenkins will be put in shutdown mode before the window starts and any
>>> long running Jenkins jobs _will_ be canceled if they don't complete
>>> before the start of the window.
>>> 
>>> Notices will be posted to the mailing lists and in #opendaylight on
>>> Freenode at the start and end of the maintenance.
>>> 
>>> https://www.worldtimebuddy.com/?qm=1&lid=100,2174003,8,5746545&h=8&date=2017-12-20&sln=14-16.5
>>> 
>> 
> 
> -- 
> Andrew J Grimberg
> Lead, IT Release Engineering
> The Linux Foundation
> 
> ___
> release mailing list
> rele...@lists.opendaylight.org 
> https://lists.opendaylight.org/mailman/listinfo/release 
> 
___
Discuss mailing list
Discuss@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/discuss

Re: [OpenDaylight Discuss] [OpenDaylight TSC] [release] OpenDaylight Nitrogen-SR1 released

[Luis Gomez]

+1, thanks anybody that made this possible.

> On Nov 28, 2017, at 11:44 AM, Anil Vishnoi  wrote:
> 
> Big thanks for the release team
> 
> On Tue, Nov 28, 2017 at 1:25 AM, Lori Jakab  > wrote:
> Awesome, thanks Anil!!
> 
> -Lori
> 
> On Tue, Nov 28, 2017 at 11:22 AM, Anil Belur  > wrote:
> >
> > On Tuesday 28 November 2017 06:42 PM, Anil Belur wrote:
> >> Hello all,
> >>
> >> OpenDaylight Nitrogen SR1 is now available in the Nexus release repo.
> >> The artifacts can be downloaded from Nexus at this URL:
> >>
> >> https://nexus.opendaylight.org/content/repositories/public/org/opendaylight/integration/karaf/0.7.1/
> >>  
> >> 
> >>
> >> OpFlex artifacts are available here:
> >>
> >> https://nexus.opendaylight.org/content/repositories/public/org/opendaylight/opflex/
> >>  
> >> 
> >>
> >> VTN Coordinator artifacts are available here:
> >>
> >> https://nexus.opendaylight.org/content/repositories/public/org/opendaylight/vtn/distribution.vtn-coordinator/6.5.1/
> >>  
> >> 
> >>
> >> We are working on version bumping the 'stable/nitrogen' branch and will
> >> update once the task is completed.
> >>
> >> Thanks,
> >> Anil
> >>
> >
> > Hello all,
> >
> > Tagging and version bumping is now complete.
> >
> > Please resume your development work on stable/nitrogen again.
> >
> > Thanks,
> > Anil
> >
> >
> >
> > ___
> > TSC mailing list
> > t...@lists.opendaylight.org 
> > https://lists.opendaylight.org/mailman/listinfo/tsc 
> > 
> >
> ___
> Discuss mailing list
> Discuss@lists.opendaylight.org 
> https://lists.opendaylight.org/mailman/listinfo/discuss 
> 
> 
> 
> 
> -- 
> Thanks
> Anil
> ___
> TSC mailing list
> t...@lists.opendaylight.org
> https://lists.opendaylight.org/mailman/listinfo/tsc

___
Discuss mailing list
Discuss@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/discuss

Re: [OpenDaylight Discuss] Karaf 4 (Nitrogen) behavior

[Luis Gomez]

t.restconf.utils.mapping.RestconfMappingNodeUtil.fillMapByModules(RestconfMappingNodeUtil.java:135)
> at 
> org.opendaylight.restconf.utils.mapping.RestconfMappingNodeUtil.mapModulesByIetfYangLibraryYang(RestconfMappingNodeUtil.java:93)
> at 
> org.opendaylight.restconf.handlers.SchemaContextHandler.onGlobalContextUpdated(SchemaContextHandler.java:63)
> at 
> org.opendaylight.mdsal.dom.broker.osgi.OsgiBundleScanningSchemaService.registerSchemaContextListener(OsgiBundleScanningSchemaService.java:148)
> at 
> org.opendaylight.controller.sal.schema.service.impl.GlobalBundleScanningSchemaServiceImpl.registerSchemaContextListener(GlobalBundleScanningSchemaServiceImpl.java:80)
> at 
> Proxy617c7f6d_e2b5_4492_bda2_f6381d0ec0e9.registerSchemaContextListener(Unknown
>  Source)
> at 
> Proxy2561774b_7fac_49ed_910b_308feba881f6.registerSchemaContextListener(Unknown
>  Source)
> at 
> org.opendaylight.restconf.RestConnectorProvider.start(RestConnectorProvider.java:90)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at 
> org.apache.aries.blueprint.utils.ReflectionUtils.invoke(ReflectionUtils.java:299)
>     at 
> org.apache.aries.blueprint.container.BeanRecipe.invoke(BeanRecipe.java:980)
> at 
> org.apache.aries.blueprint.container.BeanRecipe.runBeanProcInit(BeanRecipe.java:736)
> ... 29 more
>  
>  
> What name doesn’t exists? Did I miss something in configuration?
>  
> Thanks,
> Yevgeny
>  
> From: Luis Gomez [mailto:ece...@gmail.com] 
> Sent: Thursday, October 12, 2017 7:38 PM
> To: Shakhnovich, Yevgeny 
> Cc: discuss@lists.opendaylight.org
> Subject: Re: [OpenDaylight Discuss] Karaf 4 (Nitrogen) behavior
>  
> I think this is karaf 4 side effect, try to either list all your features in 
> the config boot file or execute all features at once in console, for example:
>  
> feature:install odl-restconf odl-netconf-mdsal odl-mdsal-apidocs 
> odl-clustering-test-app odl-netconf-topology
>  
> otherwise bundles may be restarted when you do successive installs. This 
> behavior cannot be changed AFAIK.
>  
> BR/Luis
>  
>  
> On Oct 12, 2017, at 11:58 AM, yevgeny.shakhnov...@us.fujitsu.com wrote:
>  
> Hi,
> I need your help. I am porting our project to Nitrogen and have serious 
> problems with Karaf 4 features. There is something that I don’t understand 
> there.
> On clean Karaf, I first install ODL feature odl-mdsal-apidocs:
>  
> >feature:install odl-mdsal-apidocs
>  
> >list | grep -i -v active
> START LEVEL 100 , List Threshold: 50
> ID | State| Lvl | Version | Name
> ---
> 31 | Resolved |  80 | 4.0.9   | Apache Karaf :: 
> Diagnostic :: Boot
> 183 | Resolved |  80 | 0.7.0   | 
> config-persister-directory-xml-adapter, Hosts: 185
> 184 | Resolved |  80 | 0.7.0   | 
> config-persister-file-xml-adapter, Hosts: 185
>  
>  
> No problems. Then I want to install a third party bundle 
> org.apache.mina/mina-core/2.0.9 . If I install it as a bundle, I still don’t 
> see any problem.
>  
> >bundle:install –s mvn:org.apache.mina/mina-core/2.0.9
>  
> >list | grep -i -v active
> START LEVEL 100 , List Threshold: 50
> ID | State| Lvl | Version | Name
> ---
> 31 | Resolved |  80 | 4.0.9   | Apache Karaf :: 
> Diagnostic :: Boot
> 183 | Resolved |  80 | 0.7.0   | 
> config-persister-directory-xml-adapter, Hosts: 185
> 184 | Resolved |  80 | 0.7.0   | 
> config-persister-file-xml-adapter, Hosts: 185
>  
>  
> However, if I wrap it in  a feature, I get absolutely different behavior.
>  
>  
> >feature:install -v my-feature
> Adding features: my-feature/[5.0.1.SNAPSHOT, 5.0.1.SNAPSHOT]
> Changes to perform:
>   Region: root
> Bundles to install:
>   mvn:org.apache.mina/mina-core/2.0.9
> Installing bundles:
> 

Re: [OpenDaylight Discuss] [release] OpenDaylight Carbon-SR2 released

[Luis Gomez]

+1, thanks Anil and to everyone contributing to this release.

> On Oct 16, 2017, at 11:43 PM, Anil Belur  wrote:
> 
> 
> Greetings all,
> 
> I am pleased to announce that OpenDaylight Carbon-SR2 is now available
> in the Nexus release repo. The artifacts can be downloaded from Nexus at
> this URL:
> 
> https://nexus.opendaylight.org/content/repositories/public/org/opendaylight/integration/distribution-karaf/0.6.2-Carbon/
> 
> For those interested in NeXt UI toolkit the artifacts are available here:
> 
> https://nexus.opendaylight.org/content/repositories/public/org/opendaylight/next/next/0.11.1-Carbon/
> 
> For those interested in OpFlex the artifacts are available here:
> 
> https://nexus.opendaylight.org/content/repositories/opendaylight.release/org/opendaylight/opflex/
> 
> For those interested in VTN coordinator the artifacts are available here:
> 
> https://nexus.opendaylight.org/content/repositories/public/org/opendaylight/vtn/distribution.vtn-coordinator/6.4.2-Carbon/
> 
> Tagging and version bumping is now completed. Please resume your
> development work on stable/carbon again.
> 
> Thanks to all the folks for assisting with the Carbon-SR2 release.
> 
> Regards,
> Anil Belur
> 
> ___
> release mailing list
> rele...@lists.opendaylight.org
> https://lists.opendaylight.org/mailman/listinfo/release

___
Discuss mailing list
Discuss@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/discuss

Re: [OpenDaylight Discuss] Karaf 4 (Nitrogen) behavior

[Luis Gomez]

I think this is karaf 4 side effect, try to either list all your features in 
the config boot file or execute all features at once in console, for example:

feature:install odl-restconf odl-netconf-mdsal odl-mdsal-apidocs 
odl-clustering-test-app odl-netconf-topology

otherwise bundles may be restarted when you do successive installs. This 
behavior cannot be changed AFAIK.

BR/Luis


> On Oct 12, 2017, at 11:58 AM, yevgeny.shakhnov...@us.fujitsu.com wrote:
> 
> Hi,
> I need your help. I am porting our project to Nitrogen and have serious 
> problems with Karaf 4 features. There is something that I don’t understand 
> there.
> On clean Karaf, I first install ODL feature odl-mdsal-apidocs:
>  
> >feature:install odl-mdsal-apidocs
>  
> >list | grep -i -v active
> START LEVEL 100 , List Threshold: 50
> ID | State| Lvl | Version | Name
> ---
> 31 | Resolved |  80 | 4.0.9   | Apache Karaf :: 
> Diagnostic :: Boot
> 183 | Resolved |  80 | 0.7.0   | 
> config-persister-directory-xml-adapter, Hosts: 185
> 184 | Resolved |  80 | 0.7.0   | 
> config-persister-file-xml-adapter, Hosts: 185
>  
>  
> No problems. Then I want to install a third party bundle 
> org.apache.mina/mina-core/2.0.9 . If I install it as a bundle, I still don’t 
> see any problem.
>  
> >bundle:install –s mvn:org.apache.mina/mina-core/2.0.9
>  
> >list | grep -i -v active
> START LEVEL 100 , List Threshold: 50
> ID | State| Lvl | Version | Name
> ---
> 31 | Resolved |  80 | 4.0.9   | Apache Karaf :: 
> Diagnostic :: Boot
> 183 | Resolved |  80 | 0.7.0   | 
> config-persister-directory-xml-adapter, Hosts: 185
> 184 | Resolved |  80 | 0.7.0   | 
> config-persister-file-xml-adapter, Hosts: 185
>  
>  
> However, if I wrap it in  a feature, I get absolutely different behavior.
>  
>  
> >feature:install -v my-feature
> Adding features: my-feature/[5.0.1.SNAPSHOT, 5.0.1.SNAPSHOT]
> Changes to perform:
>   Region: root
> Bundles to install:
>   mvn:org.apache.mina/mina-core/2.0.9
> Installing bundles:
>   mvn:org.apache.mina/mina-core/2.0.9
> Stopping bundles:
>   org.opendaylight.netconf.sal-rest-docgen/1.6.0
>   org.opendaylight.netconf.sal-rest-connector/1.6.0
>   org.opendaylight.aaa.shiro-act/0.6.0
>   org.opendaylight.aaa.shiro/0.6.0
>   org.opendaylight.aaa.idmlight/0.6.0
>   org.opendaylight.aaa.cert/0.6.0
>   org.opendaylight.aaa.encrypt-service/0.6.0
>   org.apache.sshd.core/0.14.0
>   org.apache.karaf.shell.ssh/4.0.9
> Refreshing bundles:
> org.apache.karaf.shell.ssh/4.0.9 (Wired to org.apache.sshd.core/0.14.0 
> which is being refreshed)
> org.apache.sshd.core/0.14.0 (Should be wired to: 
> org.apache.mina.core/2.0.9 (through [org.apache.sshd.core/0.14.0] 
> osgi.wiring.package; 
> filter:="(&(osgi.wiring.package=org.apache.mina.core.buffer)(version>=2.0.0)(!(version>=3.0.0)))";
>  resolution:=optional))
> org.opendaylight.aaa.cert/0.6.0 (Wired to 
> org.opendaylight.aaa.encrypt-service/0.6.0 which is being refreshed)
> org.opendaylight.aaa.encrypt-service/0.6.0 (Wired to 
> org.apache.sshd.core/0.14.0 which is being refreshed)
> org.opendaylight.aaa.idmlight/0.6.0 (Wired to 
> org.opendaylight.aaa.shiro/0.6.0 which is being refreshed)
> org.opendaylight.aaa.shiro/0.6.0 (Wired to 
> org.opendaylight.aaa.cert/0.6.0 which is being refreshed)
> org.opendaylight.aaa.shiro-act/0.6.0 (Wired to 
> org.opendaylight.aaa.shiro/0.6.0 which is being refreshed)
> org.opendaylight.netconf.sal-rest-connector/1.6.0 (Wired to 
> org.opendaylight.aaa.shiro/0.6.0 which is being refreshed)
> org.opendaylight.netconf.sal-rest-docgen/1.6.0 (Wired to 
> org.opendaylight.aaa.shiro/0.6.0 which is being refreshed)
> Starting bundles:
>   org.apache.mina.core/2.0.9
> Done.
>  
> >list | grep -i -v active
> START LEVEL 100 , List Threshold: 50
> ID | State   | Lvl | Version | Name
> --
> 31 | Resolved|  80 | 4.0.9   | Apache Karaf 
> :: Diagnostic :: Boot
> 167 | GracePeriod |  80 | 0.6.0   | ODL :: aaa :: 
> aaa-cert
> 168 | Failure |  80 | 0.6.

Re: [OpenDaylight Discuss] [controller-dev] TWS Call on Monday 7/17

[Luis Gomez]

Jesus, can you please add me to the bug group and send me over bug link?


> On Jul 18, 2017, at 9:06 AM, Thanh Ha  wrote:
> 
> On Tue, Jul 18, 2017 at 11:24 AM, Luis Gomez  <mailto:ece...@gmail.com>> wrote:
> Thanks this is clear, we need the JSON file structured by projects. Thanh, 
> will you file this bug or you want me to do it?
> 
> Please do and cc me on the bug.
> 
> Thanks,
> Thanh
>  

___
Discuss mailing list
Discuss@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/discuss