|
Re: [opendaylight-dev][release] OpenDaylight - Silicon SR1 release status
The release notes are ready. However, the verify job is not going through.
Thanks Luis. Anil, I believe the release notes are ready and we just have to update the downloads page after that.
Daniel de la Rosa ODL Release Manager On Tue, Jun 8, 2021 at 10:52 PM Luis Gomez < ecelgp@...> wrote: OK, here is the distribution release:
We can proceed with the post-release actions.
BR/Luis
Thank you Gilles. Luis, I think we can proceed with the official distribution of Silicon SR1
_________________________________________________________________________________________________________________________
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: [opendaylight-dev][release] OpenDaylight - Aluminium SR4 release status
Daniel de la Rosa
Thanks Anil. Guillaume, please let us when TransportPCE plans to release in Aluminium SR4
Daniel de la Rosa ODL Release Manager
On Tue, Jun 8, 2021 at 2:50 PM Anil Belur < abelur@...> wrote: Hello All, OpenDaylight Aluminium SR4 version bump is complete and the staging repository is been promoted. The 'stable/aluminum' branch is locked and ready for development.
|
|
|
Re: [opendaylight-dev][release] OpenDaylight - Silicon SR1 release status
Daniel de la Rosa
Thanks Luis. Anil, I believe the release notes are ready and we just have to update the downloads page after that.
Daniel de la Rosa ODL Release Manager
On Tue, Jun 8, 2021 at 10:52 PM Luis Gomez < ecelgp@...> wrote: OK, here is the distribution release:
We can proceed with the post-release actions.
BR/Luis
Thank you Gilles. Luis, I think we can proceed with the official distribution of Silicon SR1
_________________________________________________________________________________________________________________________
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: Triggering rtd-merge job after release-merge?
Greetings Robert:
I checked the JJB code for the controller rtd-merge-master, the Gerrit triggers seem to work as expected triggering the required jobs. Ex: Job #4 was triggered from a merge from the change request 94725. From what I understand, the release merge job are responsible for promoting the staging repo, which should create a new version ex: 3.0.6 in RTD.org/$project. Every new release on the self-managed projects would require activating the new version on RTD (as admin). That should trigger a new build to update the docs for the $project.
I am not sure if triggering rtd-merge as a downstream job on every release merge would be the right way for this. Will need to dig in a bit and get back to you.
+docs folks on any suggestions.
Cheers, Anil
|
|
|
Triggering rtd-merge job after release-merge?
|
|
|
Re: [opendaylight-dev][release] OpenDaylight - Silicon SR1 release status
OK, here is the distribution release:
We can proceed with the post-release actions.
BR/Luis
Thank you Gilles. Luis, I think we can proceed with the official distribution of Silicon SR1
_________________________________________________________________________________________________________________________
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.
|
|
|
[opendaylight-dev][release] OpenDaylight - Aluminium SR4 release status
Hello All, OpenDaylight Aluminium SR4 version bump is complete and the staging repository is been promoted. The 'stable/aluminum' branch is locked and ready for development.
|
|
|
Re: [opendaylight-dev][release] OpenDaylight - Silicon SR1 release status
Daniel de la Rosa
Thank you Gilles. Luis, I think we can proceed with the official distribution of Silicon SR1
_________________________________________________________________________________________________________________________
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: [opendaylight-dev][release] OpenDaylight - Silicon SR1 release status
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-dev@... [mailto:integration-dev@...]
De la part de Anil Belur
Envoyé : jeudi 3 juin 2021 09:11
À : Release <release@...>; 'integration-dev@...' (integration-dev@...) (integration-dev@...) <integration-dev@...>; OpenDaylight Discuss <discuss@...>;
TSC <tsc@...>
Cc : Casey Cain <ccain@...>; Daniel de la Rosa <ddelarosa0707@...>; Brandon Wick <bwick@...>; Andrew Grimberg <agrimberg@...>
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
_________________________________________________________________________________________________________________________
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.
|
|
|
[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/+/964214. 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
|
|
|
Re: [app-dev] [release] [integration-dev] [OpenDaylight TSC] $PROJECT Termination review (based on inactivity)
+1
The changes to purge the repos is on releng/builder repo for nearly a week. Appreciate any reviews.
Cheers, Anil
On Thu, May 20, 2021 at 2:17 AM Venkatrangan Govindarajan < gvrangan@...> wrote: +1 to archive
Hello
Here is my +1 to archive
BR
Guillaume
De : app-dev@... [mailto:app-dev@...]
De la part de Anil Belur
Envoyé : mercredi 19 mai 2021 14:55
À : Luis Gomez
Cc : TSC; app-dev@...; Release; integration-dev@...; Casey Cain; Daniel de la Rosa; navid.ghazisaidi@...; Andrew Grimberg
Objet : Re: [app-dev] [release] [integration-dev] [OpenDaylight TSC] $PROJECT Termination review (based on inactivity)
Hi TSC Team, Can we get more votes here. Then we can proceed to remove the Jobs and clean up the infrastructure.
On Sat, May 15, 2021 at 1:28 PM Luis Gomez <ecelgp@...> wrote:
+1 to archive
On May 13, 2021, at 11:37 PM, Anil Belur <abelur@...> wrote:
As discussed on the TSC call today, archive proposals for each $project in the list is created in the link below. Minor nit with the ordering/hierarchy needs to be fixed.
TSC members, Please vote here.
On Tue, Apr 27, 2021 at 1:11 PM Anil Belur <abelur@...> wrote:
As discussed with Casey in today's call, it would be more appropriate to consider any $projects that have not contributed to a code change in the last 8 months (ignoring
the INFO.yaml changes submitted to the project by the Releng team). Now taking that into consideration, we have the following candidates ready for archival:
I am bouncing this email again on the app-dev lists to make sure anyone in the community is interested in maintaining the $project going forward.
TSC please vote on $project list (once approved the repositories will be marked "inactive", all CI Jobs and resources from the infrastructure will be removed).
Hello TSC team:
As per section TSC Charter 2.3.5 [1.], the TSC is initiating a termination review for lack of activity (no commits in the last 18 months).
The list of ODL $PROJECT's that are candidates for archival, with the commit date for the last commit.
1. usc:
Total 3674 (delta 0), reused 3674 (delta 0)
* master - 56eca9d - Merge "Remove obsolete Maven Site configuration" - A H (2 years, 11 months ago)
2. packetcable:
* master - 71996a6 - Bump to odlparent 3.1.0 and yangtools 2.0.3 - Stephen Kitt (3 years ago)
3. opflex:
* master - 46b19e9 - Fix issues with config directory watching - Rob Adams (3 years, 1 month ago)
Once the review is approved by the TSC:
1. All jobs for the $PROJECT would be purged from Jenkins releng/builder repo.
2. The $PROJECT will be set to an inactive state on Gerrit.
3. The $PROJECT will be renamed/prefixed as "archived-$PROJECT" on Github/Gerrit.
Please add if I missed any projects, refer to the logs attached.
[1.] https://www.opendaylight.org/about/lifecycle-releases
Regards,
Anil
_________________________________________________________________________________________________________________________
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.
--
Venkatrangan Govindarajan
( When there is no wind...Row )
|
|
|
Re: [app-dev] [release] [integration-dev] [OpenDaylight TSC] $PROJECT Termination review (based on inactivity)
Venkatrangan Govindarajan
toggle quoted message
Show quoted text
Hello
Here is my +1 to archive
BR
Guillaume
De : app-dev@... [mailto:app-dev@...]
De la part de Anil Belur
Envoyé : mercredi 19 mai 2021 14:55
À : Luis Gomez
Cc : TSC; app-dev@...; Release; integration-dev@...; Casey Cain; Daniel de la Rosa; navid.ghazisaidi@...; Andrew Grimberg
Objet : Re: [app-dev] [release] [integration-dev] [OpenDaylight TSC] $PROJECT Termination review (based on inactivity)
Hi TSC Team, Can we get more votes here. Then we can proceed to remove the Jobs and clean up the infrastructure.
On Sat, May 15, 2021 at 1:28 PM Luis Gomez <ecelgp@...> wrote:
+1 to archive
On May 13, 2021, at 11:37 PM, Anil Belur <abelur@...> wrote:
As discussed on the TSC call today, archive proposals for each $project in the list is created in the link below. Minor nit with the ordering/hierarchy needs to be fixed.
TSC members, Please vote here.
On Tue, Apr 27, 2021 at 1:11 PM Anil Belur <abelur@...> wrote:
As discussed with Casey in today's call, it would be more appropriate to consider any $projects that have not contributed to a code change in the last 8 months (ignoring
the INFO.yaml changes submitted to the project by the Releng team). Now taking that into consideration, we have the following candidates ready for archival:
I am bouncing this email again on the app-dev lists to make sure anyone in the community is interested in maintaining the $project going forward.
TSC please vote on $project list (once approved the repositories will be marked "inactive", all CI Jobs and resources from the infrastructure will be removed).
Hello TSC team:
As per section TSC Charter 2.3.5 [1.], the TSC is initiating a termination review for lack of activity (no commits in the last 18 months).
The list of ODL $PROJECT's that are candidates for archival, with the commit date for the last commit.
1. usc:
Total 3674 (delta 0), reused 3674 (delta 0)
* master - 56eca9d - Merge "Remove obsolete Maven Site configuration" - A H (2 years, 11 months ago)
2. packetcable:
* master - 71996a6 - Bump to odlparent 3.1.0 and yangtools 2.0.3 - Stephen Kitt (3 years ago)
3. opflex:
* master - 46b19e9 - Fix issues with config directory watching - Rob Adams (3 years, 1 month ago)
Once the review is approved by the TSC:
1. All jobs for the $PROJECT would be purged from Jenkins releng/builder repo.
2. The $PROJECT will be set to an inactive state on Gerrit.
3. The $PROJECT will be renamed/prefixed as "archived-$PROJECT" on Github/Gerrit.
Please add if I missed any projects, refer to the logs attached.
[1.] https://www.opendaylight.org/about/lifecycle-releases
Regards,
Anil
_________________________________________________________________________________________________________________________
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.
-- Venkatrangan Govindarajan
( When there is no wind...Row )
|
|
|
Re: [app-dev] [release] [integration-dev] [OpenDaylight TSC] $PROJECT Termination review (based on inactivity)
Hello
Here is my +1 to archive
BR
Guillaume
De : app-dev@... [mailto:app-dev@...]
De la part de Anil Belur
Envoyé : mercredi 19 mai 2021 14:55
À : Luis Gomez
Cc : TSC; app-dev@...; Release; integration-dev@...; Casey Cain; Daniel de la Rosa; navid.ghazisaidi@...; Andrew Grimberg
Objet : Re: [app-dev] [release] [integration-dev] [OpenDaylight TSC] $PROJECT Termination review (based on inactivity)
Hi TSC Team, Can we get more votes here. Then we can proceed to remove the Jobs and clean up the infrastructure.
toggle quoted message
Show quoted text
On Sat, May 15, 2021 at 1:28 PM Luis Gomez < ecelgp@...> wrote:
+1 to archive
On May 13, 2021, at 11:37 PM, Anil Belur <abelur@...> wrote:
As discussed on the TSC call today, archive proposals for each $project in the list is created in the link below. Minor nit with the ordering/hierarchy needs to be fixed.
TSC members, Please vote here.
On Tue, Apr 27, 2021 at 1:11 PM Anil Belur <abelur@...> wrote:
As discussed with Casey in today's call, it would be more appropriate to consider any $projects that have not contributed to a code change in the last 8 months (ignoring
the INFO.yaml changes submitted to the project by the Releng team). Now taking that into consideration, we have the following candidates ready for archival:
I am bouncing this email again on the app-dev lists to make sure anyone in the community is interested in maintaining the $project going forward.
TSC please vote on $project list (once approved the repositories will be marked "inactive", all CI Jobs and resources from the infrastructure will be removed).
Hello TSC team:
As per section TSC Charter 2.3.5 [1.], the TSC is initiating a termination review for lack of activity (no commits in the last 18 months).
The list of ODL $PROJECT's that are candidates for archival, with the commit date for the last commit.
1. usc:
Total 3674 (delta 0), reused 3674 (delta 0)
* master - 56eca9d - Merge "Remove obsolete Maven Site configuration" - A H (2 years, 11 months ago)
2. packetcable:
* master - 71996a6 - Bump to odlparent 3.1.0 and yangtools 2.0.3 - Stephen Kitt (3 years ago)
3. opflex:
* master - 46b19e9 - Fix issues with config directory watching - Rob Adams (3 years, 1 month ago)
Once the review is approved by the TSC:
1. All jobs for the $PROJECT would be purged from Jenkins releng/builder repo.
2. The $PROJECT will be set to an inactive state on Gerrit.
3. The $PROJECT will be renamed/prefixed as "archived-$PROJECT" on Github/Gerrit.
Please add if I missed any projects, refer to the logs attached.
[1.] https://www.opendaylight.org/about/lifecycle-releases
Regards,
Anil
_________________________________________________________________________________________________________________________
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: [release] [integration-dev] [OpenDaylight TSC] $PROJECT Termination review (based on inactivity)
Hi TSC Team, Can we get more votes here. Then we can proceed to remove the Jobs and clean up the infrastructure.
Cheers
On Sat, May 15, 2021 at 1:28 PM Luis Gomez < ecelgp@...> wrote: +1 to archive On May 13, 2021, at 11:37 PM, Anil Belur < abelur@...> wrote:
As discussed on the TSC call today, archive proposals for each $project in the list is created in the link below. Minor nit with the ordering/hierarchy needs to be fixed.
TSC members, Please vote here.
On Tue, Apr 27, 2021 at 1:11 PM Anil Belur < abelur@...> wrote: As discussed with Casey in today's call, it would be more appropriate to consider any $projects that have not contributed to a code change in the last 8 months (ignoring the INFO.yaml changes submitted to the project by the Releng team). Now taking that into consideration, we have the following candidates ready for archival:
* alt-datastores * bier * coe * detnet * dluxapps * groupbasedpolicy * nemo * honeycomb/vbd * of-config * opflex * packetcable * sfc * snmp4sdn * snmp * telemetry * tsdr * usc
I am bouncing this email again on the app-dev lists to make sure anyone in the community is interested in maintaining the $project going forward.
TSC please vote on $project list (once approved the repositories will be marked "inactive", all CI Jobs and resources from the infrastructure will be removed).
Regards, Anil
Hello TSC team: As per section TSC Charter 2.3.5 [1.], the TSC is initiating a termination review for lack of activity (no commits in the last 18 months). The list of ODL $PROJECT's that are candidates for archival, with the commit date for the last commit. 1. usc: Total 3674 (delta 0), reused 3674 (delta 0) * master - 56eca9d - Merge "Remove obsolete Maven Site configuration" - A H (2 years, 11 months ago) 2. packetcable: * master - 71996a6 - Bump to odlparent 3.1.0 and yangtools 2.0.3 - Stephen Kitt (3 years ago) 3. opflex: * master - 46b19e9 - Fix issues with config directory watching - Rob Adams (3 years, 1 month ago) Once the review is approved by the TSC: 1. All jobs for the $PROJECT would be purged from Jenkins releng/builder repo. 2. The $PROJECT will be set to an inactive state on Gerrit. 3. The $PROJECT will be renamed/prefixed as "archived-$PROJECT" on Github/Gerrit. Please add if I missed any projects, refer to the logs attached. [1.] https://www.opendaylight.org/about/lifecycle-releasesRegards, Anil
|
|
|
Re: Research student - Testing of OpenDaylight controller
Rekha Jayaram <rekhajayaram20@...>
Hello Luis,
Thanks a lot for your response and for guiding me in the right direction.
I will start working on the information you gave and will get back to you for further queries.
Regards,
Rekha Jayaram
On Fri, May 14, 2021 at 11:15 AM Luis Gomez < ecelgp@...> wrote: Hi Rekha,
Welcome to OpenDaylight.
Our system test that we also use for regression is in this repo folder:
We use robot framework so if you are familiar with it, it should not be that hard to understand the tests in there.
Apart from robot code, we have some framework to define test suites and how they run, the information is collected here:
Finally you can see all system test we are running in this Jenkins tab:
Let me know if you have further questions.
BR/Luis
Hello,
I am a research student working on Combinatorial testing of Software Defined Networks.
I am currently looking for test plans of OpenDaylight controller (regression test suites).
Request you to kindly guide me to the corresponding repositories or any other contacts for the same.
---------- Thank you,
Rekha Jayaram
|
|
|
Re: [release] [integration-dev] [OpenDaylight TSC] $PROJECT Termination review (based on inactivity)
toggle quoted message
Show quoted text
On May 13, 2021, at 11:37 PM, Anil Belur < abelur@...> wrote:
As discussed on the TSC call today, archive proposals for each $project in the list is created in the link below. Minor nit with the ordering/hierarchy needs to be fixed.
TSC members, Please vote here.
On Tue, Apr 27, 2021 at 1:11 PM Anil Belur < abelur@...> wrote: As discussed with Casey in today's call, it would be more appropriate to consider any $projects that have not contributed to a code change in the last 8 months (ignoring the INFO.yaml changes submitted to the project by the Releng team). Now taking that into consideration, we have the following candidates ready for archival:
* alt-datastores * bier * coe * detnet * dluxapps * groupbasedpolicy * nemo * honeycomb/vbd * of-config * opflex * packetcable * sfc * snmp4sdn * snmp * telemetry * tsdr * usc
I am bouncing this email again on the app-dev lists to make sure anyone in the community is interested in maintaining the $project going forward.
TSC please vote on $project list (once approved the repositories will be marked "inactive", all CI Jobs and resources from the infrastructure will be removed).
Regards, Anil
Hello TSC team: As per section TSC Charter 2.3.5 [1.], the TSC is initiating a termination review for lack of activity (no commits in the last 18 months). The list of ODL $PROJECT's that are candidates for archival, with the commit date for the last commit. 1. usc: Total 3674 (delta 0), reused 3674 (delta 0) * master - 56eca9d - Merge "Remove obsolete Maven Site configuration" - A H (2 years, 11 months ago) 2. packetcable: * master - 71996a6 - Bump to odlparent 3.1.0 and yangtools 2.0.3 - Stephen Kitt (3 years ago) 3. opflex: * master - 46b19e9 - Fix issues with config directory watching - Rob Adams (3 years, 1 month ago) Once the review is approved by the TSC: 1. All jobs for the $PROJECT would be purged from Jenkins releng/builder repo. 2. The $PROJECT will be set to an inactive state on Gerrit. 3. The $PROJECT will be renamed/prefixed as "archived-$PROJECT" on Github/Gerrit. Please add if I missed any projects, refer to the logs attached. [1.] https://www.opendaylight.org/about/lifecycle-releasesRegards, Anil
|
|
|
Re: [OpenDaylight TSC] $PROJECT Termination review (based on inactivity)
As discussed on the TSC call today, archive proposals for each $project in the list is created in the link below. Minor nit with the ordering/hierarchy needs to be fixed.
TSC members, Please vote here.
On Tue, Apr 27, 2021 at 1:11 PM Anil Belur < abelur@...> wrote: As discussed with Casey in today's call, it would be more appropriate to consider any $projects that have not contributed to a code change in the last 8 months (ignoring the INFO.yaml changes submitted to the project by the Releng team). Now taking that into consideration, we have the following candidates ready for archival:
* alt-datastores * bier * coe * detnet * dluxapps * groupbasedpolicy * nemo * honeycomb/vbd * of-config * opflex * packetcable * sfc * snmp4sdn * snmp * telemetry * tsdr * usc
I am bouncing this email again on the app-dev lists to make sure anyone in the community is interested in maintaining the $project going forward.
TSC please vote on $project list (once approved the repositories will be marked "inactive", all CI Jobs and resources from the infrastructure will be removed).
Regards, Anil
Hello TSC team: As per section TSC Charter 2.3.5 [1.], the TSC is initiating a termination review for lack of activity (no commits in the last 18 months). The list of ODL $PROJECT's that are candidates for archival, with the commit date for the last commit. 1. usc: Total 3674 (delta 0), reused 3674 (delta 0) * master - 56eca9d - Merge "Remove obsolete Maven Site configuration" - A H (2 years, 11 months ago) 2. packetcable: * master - 71996a6 - Bump to odlparent 3.1.0 and yangtools 2.0.3 - Stephen Kitt (3 years ago) 3. opflex: * master - 46b19e9 - Fix issues with config directory watching - Rob Adams (3 years, 1 month ago) Once the review is approved by the TSC: 1. All jobs for the $PROJECT would be purged from Jenkins releng/builder repo. 2. The $PROJECT will be set to an inactive state on Gerrit. 3. The $PROJECT will be renamed/prefixed as "archived-$PROJECT" on Github/Gerrit. Please add if I missed any projects, refer to the logs attached. [1.] https://www.opendaylight.org/about/lifecycle-releasesRegards, Anil
|
|
|
Re: Research student - Testing of OpenDaylight controller
Hi Rekha,
Welcome to OpenDaylight.
Our system test that we also use for regression is in this repo folder:
We use robot framework so if you are familiar with it, it should not be that hard to understand the tests in there.
Apart from robot code, we have some framework to define test suites and how they run, the information is collected here:
Finally you can see all system test we are running in this Jenkins tab:
Let me know if you have further questions.
BR/Luis
Hello,
I am a research student working on Combinatorial testing of Software Defined Networks.
I am currently looking for test plans of OpenDaylight controller (regression test suites).
Request you to kindly guide me to the corresponding repositories or any other contacts for the same.
---------- Thank you,
Rekha Jayaram
|
|
|
Research student - Testing of OpenDaylight controller
Rekha Jayaram <rekhajayaram20@...>
Hello,
I am a research student working on Combinatorial testing of Software Defined Networks.
I am currently looking for test plans of OpenDaylight controller (regression test suites).
Request you to kindly guide me to the corresponding repositories or any other contacts for the same.
---------- Thank you,
Rekha Jayaram
|
|
|
Re: [release] [OpenDaylight TSC] Decommision SonarQube service (sonar.opendaylight.org)
Hi Guillaume:
These are the default values configured for the quality gates for all ODL $projects. If required we can create custom gates and configure them to a list of $projects. I don't see your GH id added to the projects members list. I am not sure if you can create/modify quality gates as non-admin user (we can give it a try). Please open a helpdesk ticket along with your Github account id and the project details. :-)
Cheers, Anil
Thanks Anil for your feedback at the TSC meeting.
As discussed, I’ve got a concern about the thresholds now configured in the quality gate.
They are currently configured to these values: >80% of Junit coverage and <3% of Duplication code.
In my opinion, this default setting is not adapted to every project.
Is there a way to modify it and/or allow a per-project specific configuration ?
https://sonarcloud.io/organizations/opendaylight/quality_gates/show/6825
The interface at this URL seems to be the right place but is locked.
Best Regards
Guillaume
De : release@... [mailto:release@...]
De la part de Anil Belur
Envoyé : jeudi 22 avril 2021 07:33
À : TSC; 'integration-dev@...' (integration-dev@...) (integration-dev@...); Release
Cc : Andrew Grimberg; Ryan Day; Jordan Conway; Casey Cain
Objet : [release] [OpenDaylight TSC] Decommision SonarQube service (sonar.opendaylight.org)
SonarQube service [1.] has been transitioned to a cloud-based Sonarcloud service [2.]. Since the scans were done during August 2020, the SonarQube service [1.] will be decommissioned going forward.
All Jenkins jobs are migrated to work with Sonarcloud.io [2.] and the relevant changes are already merged on releng/builder repo. Going forward please use SonarCloud.io service [2.].
Regards,
_________________________________________________________________________________________________________________________
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.
|
|
|
