Date   

integration meeting at 8:30am tomorrow (9/2/2020)

JamO Luhrsen
 

Hi All,

I'll be on the zoom tomorrow morning at 8:30 for our weekly integration
call (instead of the 9pm PST).

Thanks,
JamO


Re: [release][OpenDaylight TSC] OpenDaylight Sodium SR4 Status

Abhijit Kumbhare
 

Thanks Thanh, Luis, Daniel, Guillaume, Anil and others!


On Fri, Aug 28, 2020 at 12:37 PM Thanh ha <zxiiro@...> wrote:
I updated the downloads pages related to sodium.

Regards,
Thanh

On Fri, Aug 28, 2020 at 3:21 PM Luis Gomez <ecelgp@...> wrote:
Sodium SR4 common distribution is released here: https://nexus.opendaylight.org/content/repositories/opendaylight.release/org/opendaylight/integration/opendaylight/0.11.4/

Please proceed with post-release tasks.

BR/Luis


On Aug 28, 2020, at 9:42 AM, Daniel de la Rosa <ddelarosa0707@...> wrote:

Thank you very much Guillaume. 

Luis, we can now proceed with sodium sr4 distribution. 

Thank you all 

On Fri, Aug 28, 2020 at 6:01 AM <guillaume.lambert@...> wrote:
















Hi all



 



FYI, I successfully released old-transportpce 0.4.5 for Sodium SR4 this morning.



https://jenkins.opendaylight.org/releng/view/transportpce/job/transportpce-release-merge/lastBuild/



 



 



BR



Guillaume



 







De : LAMBERT Guillaume TGI/OLN




Envoyé : vendredi 28 août 2020 08:38


À : 'Luis Gomez'


Cc : Daniel de la Rosa; Anil Belur; TSC; Release; integration-dev@...; Casey Cain; Daniel De La Rosa; transportpce-dev@...; jsonrpc-dev@...


Objet : RE: [integration-dev] [release][OpenDaylight TSC] OpenDaylight Sodium SR4 Status







 



Hi Luis,



 



Thanks for the feedback. If so, I’ll take care of that today.



 



Guillaume



 







De : TSC@... [mailto:TSC@...]

De la part de Luis Gomez


Envoyé : jeudi 27 août 2020 17:44


À : LAMBERT Guillaume TGI/OLN


Cc : Daniel de la Rosa; Anil Belur; TSC; Release; integration-dev@...; Casey Cain; Daniel De La Rosa; transportpce-dev@...; jsonrpc-dev@...


Objet : Re: [integration-dev] [release][OpenDaylight TSC] OpenDaylight Sodium SR4 Status







 



Hi Guillaume,





 







Even if there is no changes in TPCE between Sodium SR3 and SR4, if you do not produce a release for Sodium SR4, any downstream picking ODL Sodium SR4 (e.g. ONAP) will not be able to run TPCE. TPCE 0.4.4 was compiled towards Sodium SR3 and

would only work in that version. 







 







BR/Luis 





 





On Aug 27, 2020, at 7:40 AM, Guillaume Lambert via

lists.opendaylight.org
<guillaume.lambert=orange.com@...> wrote:





 







Hi all







 







I raised the topic on our weekly meeting today and everybody agreed there is nothing more we can backport from our master and Magnesium branches

to Sodium SR4.







Though we can release new TPCE sodium SR4 artifacts with nothing more, I suspect there is no point to do it if our Sodium SR3 artifacts can also

be consumed in this new distribution.







If you don’t think so, let me know and I will take care of it.







 







Guillaume







 







De : TSC@... [mailto:TSC@...] De

la part de
 Daniel de la Rosa


Envoyé : mercredi 26 août 2020 17:52


À : Anil Belur


Cc : TSC; Release; 'integration-dev@...' (integration-dev@...)

(integration-dev@...); Casey Cain; Daniel De La Rosa; transportpce-dev@...; jsonrpc-dev@...


Objet : Re: [integration-dev] [release][OpenDaylight TSC] OpenDaylight Sodium SR4 Status







 









Hello All









 











SM projects, please let us know if you are done releasing on Sodium SR4, so we can move forward with the general distribution. and downloads page











 











 











Thanks











 











On Fri, Aug 21, 2020 at 3:18 AM Anil Belur <abelur@...> wrote:











Hello All,





OpenDaylight Sodium SR4 version bump is complete while the staging repository is still being promoted. Note: 'stable/sodium' branch is locked.







Pending activities for the release:


1. Release self-managed projects of Sodium SR4.


2. Release Distribution.


3. Merge release notes change [1.]. 


4. Update ODL downloads page.





[1.] https://git.opendaylight.org/gerrit/c/docs/+/92233














Thanks to everyone who contributed to the release.





Regards,


Anil Belur











 









_________________________________________________________________________________________________________________________


 


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.


 







 







_________________________________________________________________________________________________________________________



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][OpenDaylight TSC] OpenDaylight Sodium SR4 Status

Thanh ha <zxiiro@...>
 

I updated the downloads pages related to sodium.

Regards,
Thanh


On Fri, Aug 28, 2020 at 3:21 PM Luis Gomez <ecelgp@...> wrote:
Sodium SR4 common distribution is released here: https://nexus.opendaylight.org/content/repositories/opendaylight.release/org/opendaylight/integration/opendaylight/0.11.4/

Please proceed with post-release tasks.

BR/Luis


On Aug 28, 2020, at 9:42 AM, Daniel de la Rosa <ddelarosa0707@...> wrote:

Thank you very much Guillaume. 

Luis, we can now proceed with sodium sr4 distribution. 

Thank you all 

On Fri, Aug 28, 2020 at 6:01 AM <guillaume.lambert@...> wrote:
















Hi all



 



FYI, I successfully released old-transportpce 0.4.5 for Sodium SR4 this morning.



https://jenkins.opendaylight.org/releng/view/transportpce/job/transportpce-release-merge/lastBuild/



 



 



BR



Guillaume



 







De : LAMBERT Guillaume TGI/OLN




Envoyé : vendredi 28 août 2020 08:38


À : 'Luis Gomez'


Cc : Daniel de la Rosa; Anil Belur; TSC; Release; integration-dev@...; Casey Cain; Daniel De La Rosa; transportpce-dev@...; jsonrpc-dev@...


Objet : RE: [integration-dev] [release][OpenDaylight TSC] OpenDaylight Sodium SR4 Status







 



Hi Luis,



 



Thanks for the feedback. If so, I’ll take care of that today.



 



Guillaume



 







De : TSC@... [mailto:TSC@...]

De la part de Luis Gomez


Envoyé : jeudi 27 août 2020 17:44


À : LAMBERT Guillaume TGI/OLN


Cc : Daniel de la Rosa; Anil Belur; TSC; Release; integration-dev@...; Casey Cain; Daniel De La Rosa; transportpce-dev@...; jsonrpc-dev@...


Objet : Re: [integration-dev] [release][OpenDaylight TSC] OpenDaylight Sodium SR4 Status







 



Hi Guillaume,





 







Even if there is no changes in TPCE between Sodium SR3 and SR4, if you do not produce a release for Sodium SR4, any downstream picking ODL Sodium SR4 (e.g. ONAP) will not be able to run TPCE. TPCE 0.4.4 was compiled towards Sodium SR3 and

would only work in that version. 







 







BR/Luis 





 





On Aug 27, 2020, at 7:40 AM, Guillaume Lambert via

lists.opendaylight.org
<guillaume.lambert=orange.com@...> wrote:





 







Hi all







 







I raised the topic on our weekly meeting today and everybody agreed there is nothing more we can backport from our master and Magnesium branches

to Sodium SR4.







Though we can release new TPCE sodium SR4 artifacts with nothing more, I suspect there is no point to do it if our Sodium SR3 artifacts can also

be consumed in this new distribution.







If you don’t think so, let me know and I will take care of it.







 







Guillaume







 







De : TSC@... [mailto:TSC@...] De

la part de
 Daniel de la Rosa


Envoyé : mercredi 26 août 2020 17:52


À : Anil Belur


Cc : TSC; Release; 'integration-dev@...' (integration-dev@...)

(integration-dev@...); Casey Cain; Daniel De La Rosa; transportpce-dev@...; jsonrpc-dev@...


Objet : Re: [integration-dev] [release][OpenDaylight TSC] OpenDaylight Sodium SR4 Status







 









Hello All









 











SM projects, please let us know if you are done releasing on Sodium SR4, so we can move forward with the general distribution. and downloads page











 











 











Thanks











 











On Fri, Aug 21, 2020 at 3:18 AM Anil Belur <abelur@...> wrote:











Hello All,





OpenDaylight Sodium SR4 version bump is complete while the staging repository is still being promoted. Note: 'stable/sodium' branch is locked.







Pending activities for the release:


1. Release self-managed projects of Sodium SR4.


2. Release Distribution.


3. Merge release notes change [1.]. 


4. Update ODL downloads page.





[1.] https://git.opendaylight.org/gerrit/c/docs/+/92233














Thanks to everyone who contributed to the release.





Regards,


Anil Belur











 









_________________________________________________________________________________________________________________________


 


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.


 







 







_________________________________________________________________________________________________________________________



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][OpenDaylight TSC] OpenDaylight Sodium SR4 Status

Luis Gomez
 

Sodium SR4 common distribution is released here: https://nexus.opendaylight.org/content/repositories/opendaylight.release/org/opendaylight/integration/opendaylight/0.11.4/

Please proceed with post-release tasks.

BR/Luis


On Aug 28, 2020, at 9:42 AM, Daniel de la Rosa <ddelarosa0707@...> wrote:

Thank you very much Guillaume. 

Luis, we can now proceed with sodium sr4 distribution. 

Thank you all 

On Fri, Aug 28, 2020 at 6:01 AM <guillaume.lambert@...> wrote:
















Hi all



 



FYI, I successfully released old-transportpce 0.4.5 for Sodium SR4 this morning.



https://jenkins.opendaylight.org/releng/view/transportpce/job/transportpce-release-merge/lastBuild/



 



 



BR



Guillaume



 







De : LAMBERT Guillaume TGI/OLN




Envoyé : vendredi 28 août 2020 08:38


À : 'Luis Gomez'


Cc : Daniel de la Rosa; Anil Belur; TSC; Release; integration-dev@...; Casey Cain; Daniel De La Rosa; transportpce-dev@...; jsonrpc-dev@...


Objet : RE: [integration-dev] [release][OpenDaylight TSC] OpenDaylight Sodium SR4 Status







 



Hi Luis,



 



Thanks for the feedback. If so, I’ll take care of that today.



 



Guillaume



 







De : TSC@... [mailto:TSC@...]

De la part de Luis Gomez


Envoyé : jeudi 27 août 2020 17:44


À : LAMBERT Guillaume TGI/OLN


Cc : Daniel de la Rosa; Anil Belur; TSC; Release; integration-dev@...; Casey Cain; Daniel De La Rosa; transportpce-dev@...; jsonrpc-dev@...


Objet : Re: [integration-dev] [release][OpenDaylight TSC] OpenDaylight Sodium SR4 Status







 



Hi Guillaume,





 







Even if there is no changes in TPCE between Sodium SR3 and SR4, if you do not produce a release for Sodium SR4, any downstream picking ODL Sodium SR4 (e.g. ONAP) will not be able to run TPCE. TPCE 0.4.4 was compiled towards Sodium SR3 and

would only work in that version. 







 







BR/Luis 





 





On Aug 27, 2020, at 7:40 AM, Guillaume Lambert via

lists.opendaylight.org
<guillaume.lambert=orange.com@...> wrote:





 







Hi all







 







I raised the topic on our weekly meeting today and everybody agreed there is nothing more we can backport from our master and Magnesium branches

to Sodium SR4.







Though we can release new TPCE sodium SR4 artifacts with nothing more, I suspect there is no point to do it if our Sodium SR3 artifacts can also

be consumed in this new distribution.







If you don’t think so, let me know and I will take care of it.







 







Guillaume







 







De : TSC@... [mailto:TSC@...] De

la part de
 Daniel de la Rosa


Envoyé : mercredi 26 août 2020 17:52


À : Anil Belur


Cc : TSC; Release; 'integration-dev@...' (integration-dev@...)

(integration-dev@...); Casey Cain; Daniel De La Rosa; transportpce-dev@...; jsonrpc-dev@...


Objet : Re: [integration-dev] [release][OpenDaylight TSC] OpenDaylight Sodium SR4 Status







 









Hello All









 











SM projects, please let us know if you are done releasing on Sodium SR4, so we can move forward with the general distribution. and downloads page











 











 











Thanks











 











On Fri, Aug 21, 2020 at 3:18 AM Anil Belur <abelur@...> wrote:











Hello All,





OpenDaylight Sodium SR4 version bump is complete while the staging repository is still being promoted. Note: 'stable/sodium' branch is locked.







Pending activities for the release:


1. Release self-managed projects of Sodium SR4.


2. Release Distribution.


3. Merge release notes change [1.]. 


4. Update ODL downloads page.





[1.] https://git.opendaylight.org/gerrit/c/docs/+/92233














Thanks to everyone who contributed to the release.





Regards,


Anil Belur











 









_________________________________________________________________________________________________________________________


 


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.


 







 







_________________________________________________________________________________________________________________________



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][OpenDaylight TSC] OpenDaylight Sodium SR4 Status

Daniel de la Rosa
 

Thank you very much Guillaume. 

Luis, we can now proceed with sodium sr4 distribution. 

Thank you all 

On Fri, Aug 28, 2020 at 6:01 AM <guillaume.lambert@...> wrote:
















Hi all



 



FYI, I successfully released old-transportpce 0.4.5 for Sodium SR4 this morning.



https://jenkins.opendaylight.org/releng/view/transportpce/job/transportpce-release-merge/lastBuild/



 



 



BR



Guillaume



 







De : LAMBERT Guillaume TGI/OLN




Envoyé : vendredi 28 août 2020 08:38


À : 'Luis Gomez'


Cc : Daniel de la Rosa; Anil Belur; TSC; Release; integration-dev@...; Casey Cain; Daniel De La Rosa; transportpce-dev@...; jsonrpc-dev@...


Objet : RE: [integration-dev] [release][OpenDaylight TSC] OpenDaylight Sodium SR4 Status







 



Hi Luis,



 



Thanks for the feedback. If so, I’ll take care of that today.



 



Guillaume



 







De : TSC@... [mailto:TSC@...]

De la part de Luis Gomez


Envoyé : jeudi 27 août 2020 17:44


À : LAMBERT Guillaume TGI/OLN


Cc : Daniel de la Rosa; Anil Belur; TSC; Release; integration-dev@...; Casey Cain; Daniel De La Rosa; transportpce-dev@...; jsonrpc-dev@...


Objet : Re: [integration-dev] [release][OpenDaylight TSC] OpenDaylight Sodium SR4 Status







 



Hi Guillaume,





 







Even if there is no changes in TPCE between Sodium SR3 and SR4, if you do not produce a release for Sodium SR4, any downstream picking ODL Sodium SR4 (e.g. ONAP) will not be able to run TPCE. TPCE 0.4.4 was compiled towards Sodium SR3 and

would only work in that version. 







 







BR/Luis 





 





On Aug 27, 2020, at 7:40 AM, Guillaume Lambert via

lists.opendaylight.org
<guillaume.lambert=orange.com@...> wrote:





 







Hi all







 







I raised the topic on our weekly meeting today and everybody agreed there is nothing more we can backport from our master and Magnesium branches

to Sodium SR4.







Though we can release new TPCE sodium SR4 artifacts with nothing more, I suspect there is no point to do it if our Sodium SR3 artifacts can also

be consumed in this new distribution.







If you don’t think so, let me know and I will take care of it.







 







Guillaume







 







De : TSC@... [mailto:TSC@...] De

la part de
 Daniel de la Rosa


Envoyé : mercredi 26 août 2020 17:52


À : Anil Belur


Cc : TSC; Release; 'integration-dev@...' (integration-dev@...)

(integration-dev@...); Casey Cain; Daniel De La Rosa; transportpce-dev@...; jsonrpc-dev@...


Objet : Re: [integration-dev] [release][OpenDaylight TSC] OpenDaylight Sodium SR4 Status







 









Hello All









 











SM projects, please let us know if you are done releasing on Sodium SR4, so we can move forward with the general distribution. and downloads page











 











 











Thanks











 











On Fri, Aug 21, 2020 at 3:18 AM Anil Belur <abelur@...> wrote:











Hello All,





OpenDaylight Sodium SR4 version bump is complete while the staging repository is still being promoted. Note: 'stable/sodium' branch is locked.







Pending activities for the release:


1. Release self-managed projects of Sodium SR4.


2. Release Distribution.


3. Merge release notes change [1.]. 


4. Update ODL downloads page.





[1.] https://git.opendaylight.org/gerrit/c/docs/+/92233














Thanks to everyone who contributed to the release.





Regards,


Anil Belur











 









_________________________________________________________________________________________________________________________


 


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.


 







 







_________________________________________________________________________________________________________________________



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][OpenDaylight TSC] OpenDaylight Sodium SR4 Status

Guillaume Lambert
 

Hi all

 

FYI, I successfully released old-transportpce 0.4.5 for Sodium SR4 this morning.

https://jenkins.opendaylight.org/releng/view/transportpce/job/transportpce-release-merge/lastBuild/

 

 

BR

Guillaume

 

De : LAMBERT Guillaume TGI/OLN
Envoyé : vendredi 28 août 2020 08:38
À : 'Luis Gomez'
Cc : Daniel de la Rosa; Anil Belur; TSC; Release; integration-dev@...; Casey Cain; Daniel De La Rosa; transportpce-dev@...; jsonrpc-dev@...
Objet : RE: [integration-dev] [release][OpenDaylight TSC] OpenDaylight Sodium SR4 Status

 

Hi Luis,

 

Thanks for the feedback. If so, I’ll take care of that today.

 

Guillaume

 

De : TSC@... [mailto:TSC@...] De la part de Luis Gomez
Envoyé : jeudi 27 août 2020 17:44
À : LAMBERT Guillaume TGI/OLN
Cc : Daniel de la Rosa; Anil Belur; TSC; Release; integration-dev@...; Casey Cain; Daniel De La Rosa; transportpce-dev@...; jsonrpc-dev@...
Objet : Re: [integration-dev] [release][OpenDaylight TSC] OpenDaylight Sodium SR4 Status

 

Hi Guillaume,

 

Even if there is no changes in TPCE between Sodium SR3 and SR4, if you do not produce a release for Sodium SR4, any downstream picking ODL Sodium SR4 (e.g. ONAP) will not be able to run TPCE. TPCE 0.4.4 was compiled towards Sodium SR3 and would only work in that version. 

 

BR/Luis 

 

On Aug 27, 2020, at 7:40 AM, Guillaume Lambert via lists.opendaylight.org <guillaume.lambert=orange.com@...> wrote:

 

Hi all

 

I raised the topic on our weekly meeting today and everybody agreed there is nothing more we can backport from our master and Magnesium branches to Sodium SR4.

Though we can release new TPCE sodium SR4 artifacts with nothing more, I suspect there is no point to do it if our Sodium SR3 artifacts can also be consumed in this new distribution.

If you don’t think so, let me know and I will take care of it.

 

Guillaume

 

De : TSC@... [mailto:TSC@...] De la part de Daniel de la Rosa
Envoyé : mercredi 26 août 2020 17:52
À : Anil Belur
Cc : TSC; Release; 'integration-dev@...' (integration-dev@...) (integration-dev@...); Casey Cain; Daniel De La Rosa; transportpce-dev@...; jsonrpc-dev@...
Objet : Re: [integration-dev] [release][OpenDaylight TSC] OpenDaylight Sodium SR4 Status

 

Hello All

 

SM projects, please let us know if you are done releasing on Sodium SR4, so we can move forward with the general distribution. and downloads page

 

 

Thanks

 

On Fri, Aug 21, 2020 at 3:18 AM Anil Belur <abelur@...> wrote:

Hello All,

OpenDaylight Sodium SR4 version bump is complete while the staging repository is still being promoted. Note: 'stable/sodium' branch is locked.

Pending activities for the release:
1. Release self-managed projects of Sodium SR4.
2. Release Distribution.
3. Merge release notes change [1.]. 
4. Update ODL downloads page.

[1.] https://git.opendaylight.org/gerrit/c/docs/+/92233


Thanks to everyone who contributed to the release.

Regards,
Anil Belur

 

_________________________________________________________________________________________________________________________
 
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.

 

 

_________________________________________________________________________________________________________________________

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][OpenDaylight TSC] OpenDaylight Sodium SR4 Status

Guillaume Lambert
 

Hi Luis,

 

Thanks for the feedback. If so, I’ll take care of that today.

 

Guillaume

 

De : TSC@... [mailto:TSC@...] De la part de Luis Gomez
Envoyé : jeudi 27 août 2020 17:44
À : LAMBERT Guillaume TGI/OLN
Cc : Daniel de la Rosa; Anil Belur; TSC; Release; integration-dev@...; Casey Cain; Daniel De La Rosa; transportpce-dev@...; jsonrpc-dev@...
Objet : Re: [integration-dev] [release][OpenDaylight TSC] OpenDaylight Sodium SR4 Status

 

Hi Guillaume,

 

Even if there is no changes in TPCE between Sodium SR3 and SR4, if you do not produce a release for Sodium SR4, any downstream picking ODL Sodium SR4 (e.g. ONAP) will not be able to run TPCE. TPCE 0.4.4 was compiled towards Sodium SR3 and would only work in that version. 

 

BR/Luis 



On Aug 27, 2020, at 7:40 AM, Guillaume Lambert via lists.opendaylight.org <guillaume.lambert=orange.com@...> wrote:

 

Hi all

 

I raised the topic on our weekly meeting today and everybody agreed there is nothing more we can backport from our master and Magnesium branches to Sodium SR4.

Though we can release new TPCE sodium SR4 artifacts with nothing more, I suspect there is no point to do it if our Sodium SR3 artifacts can also be consumed in this new distribution.

If you don’t think so, let me know and I will take care of it.

 

Guillaume

 

De : TSC@... [mailto:TSC@...] De la part de Daniel de la Rosa
Envoyé : mercredi 26 août 2020 17:52
À : Anil Belur
Cc : TSC; Release; 'integration-dev@...' (integration-dev@...) (integration-dev@...); Casey Cain; Daniel De La Rosa; transportpce-dev@...; jsonrpc-dev@...
Objet : Re: [integration-dev] [release][OpenDaylight TSC] OpenDaylight Sodium SR4 Status

 

Hello All

 

SM projects, please let us know if you are done releasing on Sodium SR4, so we can move forward with the general distribution. and downloads page

 

 

Thanks

 

On Fri, Aug 21, 2020 at 3:18 AM Anil Belur <abelur@...> wrote:

Hello All,

OpenDaylight Sodium SR4 version bump is complete while the staging repository is still being promoted. Note: 'stable/sodium' branch is locked.

Pending activities for the release:
1. Release self-managed projects of Sodium SR4.
2. Release Distribution.
3. Merge release notes change [1.]. 
4. Update ODL downloads page.

[1.] https://git.opendaylight.org/gerrit/c/docs/+/92233


Thanks to everyone who contributed to the release.

Regards,
Anil Belur

 

_________________________________________________________________________________________________________________________
 
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.

 

 

_________________________________________________________________________________________________________________________

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][OpenDaylight TSC] OpenDaylight Sodium SR4 Status

Luis Gomez
 

Hi Guillaume,

Even if there is no changes in TPCE between Sodium SR3 and SR4, if you do not produce a release for Sodium SR4, any downstream picking ODL Sodium SR4 (e.g. ONAP) will not be able to run TPCE. TPCE 0.4.4 was compiled towards Sodium SR3 and would only work in that version. 

BR/Luis 

On Aug 27, 2020, at 7:40 AM, Guillaume Lambert via lists.opendaylight.org <guillaume.lambert=orange.com@...> wrote:

Hi all
 
I raised the topic on our weekly meeting today and everybody agreed there is nothing more we can backport from our master and Magnesium branches to Sodium SR4.
Though we can release new TPCE sodium SR4 artifacts with nothing more, I suspect there is no point to do it if our Sodium SR3 artifacts can also be consumed in this new distribution.
If you don’t think so, let me know and I will take care of it.
 
Guillaume
 
De : TSC@... [mailto:TSC@...] De la part de Daniel de la Rosa
Envoyé : mercredi 26 août 2020 17:52
À : Anil Belur
Cc : TSC; Release; 'integration-dev@...' (integration-dev@...) (integration-dev@...); Casey Cain; Daniel De La Rosa; transportpce-dev@...; jsonrpc-dev@...
Objet : Re: [integration-dev] [release][OpenDaylight TSC] OpenDaylight Sodium SR4 Status
 
Hello All
 
SM projects, please let us know if you are done releasing on Sodium SR4, so we can move forward with the general distribution. and downloads page
 
 
Thanks
 
On Fri, Aug 21, 2020 at 3:18 AM Anil Belur <abelur@...> wrote:

Hello All,

OpenDaylight Sodium SR4 version bump is complete while the staging repository is still being promoted. Note: 'stable/sodium' branch is locked.

Pending activities for the release:
1. Release self-managed projects of Sodium SR4.
2. Release Distribution.
3. Merge release notes change [1.]. 
4. Update ODL downloads page.

[1.] https://git.opendaylight.org/gerrit/c/docs/+/92233

Thanks to everyone who contributed to the release.

Regards,
Anil Belur
 
_________________________________________________________________________________________________________________________

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][OpenDaylight TSC] OpenDaylight Sodium SR4 Status

Guillaume Lambert
 

Hi all

 

I raised the topic on our weekly meeting today and everybody agreed there is nothing more we can backport from our master and Magnesium branches to Sodium SR4.

Though we can release new TPCE sodium SR4 artifacts with nothing more, I suspect there is no point to do it if our Sodium SR3 artifacts can also be consumed in this new distribution.

If you don’t think so, let me know and I will take care of it.

 

Guillaume

 

De : TSC@... [mailto:TSC@...] De la part de Daniel de la Rosa
Envoyé : mercredi 26 août 2020 17:52
À : Anil Belur
Cc : TSC; Release; 'integration-dev@...' (integration-dev@...) (integration-dev@...); Casey Cain; Daniel De La Rosa; transportpce-dev@...; jsonrpc-dev@...
Objet : Re: [integration-dev] [release][OpenDaylight TSC] OpenDaylight Sodium SR4 Status

 

Hello All

 

SM projects, please let us know if you are done releasing on Sodium SR4, so we can move forward with the general distribution. and downloads page

 

 

Thanks

 

On Fri, Aug 21, 2020 at 3:18 AM Anil Belur <abelur@...> wrote:

Hello All,

OpenDaylight Sodium SR4 version bump is complete while the staging repository is still being promoted. Note: 'stable/sodium' branch is locked.

Pending activities for the release:
1. Release self-managed projects of Sodium SR4.
2. Release Distribution.
3. Merge release notes change [1.]. 
4. Update ODL downloads page.

[1.] https://git.opendaylight.org/gerrit/c/docs/+/92233


Thanks to everyone who contributed to the release.

Regards,
Anil Belur

 

_________________________________________________________________________________________________________________________

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][OpenDaylight TSC] OpenDaylight Sodium SR4 Status

Richard Kosegi
 

Hi folks,

On Wed, Aug 26, 2020 at 3:52 PM Daniel de la Rosa <ddelarosa0707@...> wrote:
Hello All

SM projects, please let us know if you are done releasing on Sodium SR4, so we can move forward with the general distribution. and downloads page


jsonrpc 1.7.4 released.

Regards,
Richard.
 

Thanks

On Fri, Aug 21, 2020 at 3:18 AM Anil Belur <abelur@...> wrote:
Hello All,

OpenDaylight Sodium SR4 version bump is complete while the staging repository is still being promoted. Note: 'stable/sodium' branch is locked.

Pending activities for the release:
1. Release self-managed projects of Sodium SR4.
2. Release Distribution.
3. Merge release notes change [1.]. 
4. Update ODL downloads page.

[1.] https://git.opendaylight.org/gerrit/c/docs/+/92233

Thanks to everyone who contributed to the release.

Regards,
Anil Belur



Re: [release][OpenDaylight TSC] OpenDaylight Sodium SR4 Status

Daniel de la Rosa
 

Hello All

SM projects, please let us know if you are done releasing on Sodium SR4, so we can move forward with the general distribution. and downloads page


Thanks

On Fri, Aug 21, 2020 at 3:18 AM Anil Belur <abelur@...> wrote:
Hello All,

OpenDaylight Sodium SR4 version bump is complete while the staging repository is still being promoted. Note: 'stable/sodium' branch is locked.

Pending activities for the release:
1. Release self-managed projects of Sodium SR4.
2. Release Distribution.
3. Merge release notes change [1.]. 
4. Update ODL downloads page.

[1.] https://git.opendaylight.org/gerrit/c/docs/+/92233

Thanks to everyone who contributed to the release.

Regards,
Anil Belur


[release][OpenDaylight TSC] OpenDaylight Sodium SR4 Status

Anil Belur
 

Hello All,

OpenDaylight Sodium SR4 version bump is complete while the staging repository is still being promoted. Note: 'stable/sodium' branch is locked.

Pending activities for the release:
1. Release self-managed projects of Sodium SR4.
2. Release Distribution.
3. Merge release notes change [1.]. 
4. Update ODL downloads page.

[1.] https://git.opendaylight.org/gerrit/c/docs/+/92233

Thanks to everyone who contributed to the release.

Regards,
Anil Belur


integration meeting minutes (8/19/2020)

JamO Luhrsen
 


Re: netvirt jobs aborting.

Srinivas <srinivas.rachakonda@...>
 

Hi Jamo,

 

I am looking into it now.

 

Thanks,

Srinivas

+91-9243478719

 

From: Jamo Luhrsen <jluhrsen@...>
Sent: 18 August 2020 20:48
To: integration-dev@...; srinivas.rachakonda@...
Subject: netvirt jobs aborting.

 

Srinivas,

Looks like some (maybe all?) netvirt jobs are aborting due to some
python package issue. Here is a snippet from the stacking log:

Ignoring typed-ast: markers 'python_version == "3.6"' don't match your environment
Obtaining file:///opt/stack/keystone
    Complete output from command python setup.py egg_info:
    Marker evaluation failed, see the following error.  For more information see: http://docs.openstack.org/pbr/latest/user/using.html#environment-markers
    ERROR:root:Error parsing
    Traceback (most recent call last):
      File "/usr/lib/python2.7/site-packages/pbr/core.py", line 96, in pbr
        attrs = util.cfg_to_args(path, dist.script_args)
      File "/usr/lib/python2.7/site-packages/pbr/util.py", line 258, in cfg_to_args
        kwargs = setup_cfg_to_setup_kwargs(config, script_args)
      File "/usr/lib/python2.7/site-packages/pbr/util.py", line 456, in setup_cfg_to_setup_kwargs
        if pkg_resources.evaluate_marker('(%s)' % env_marker):
      File "/usr/lib/python2.7/site-packages/pkg_resources.py", line 1364, in evaluate_marker
        return interpret(parser.expr(text).totuple(1)[1])
      File "/usr/lib/python2.7/site-packages/pkg_resources.py", line 1342, in interpret
        return op(nodelist)
      File "/usr/lib/python2.7/site-packages/pkg_resources.py", line 1307, in atom
        return interpret(nodelist[2])
      File "/usr/lib/python2.7/site-packages/pkg_resources.py", line 1342, in interpret
        return op(nodelist)
      File "/usr/lib/python2.7/site-packages/pkg_resources.py", line 1324, in comparison
        raise SyntaxError(repr(cop)+" operator not allowed in environment markers")
    SyntaxError: '>=' operator not allowed in environment markers
    error in setup command: Error parsing /opt/stack/keystone/setup.cfg: SyntaxError: '>=' operator not allowed in environment markers
 
 
Thanks,
JamO


integration meeting 8:30am PST tomorrow (8/19/2020)

JamO Luhrsen
 

Just fyi that I moved the meeting for tomorrow. We'll hold the call at
8:30am PST.

Thanks,
JamO


netvirt jobs aborting.

JamO Luhrsen
 

Srinivas,

Looks like some (maybe all?) netvirt jobs are aborting due to some
python package issue. Here is a snippet from the stacking log:

Ignoring typed-ast: markers 'python_version == "3.6"' don't match your environment
Obtaining file:///opt/stack/keystone
    Complete output from command python setup.py egg_info:
    Marker evaluation failed, see the following error.  For more information see: http://docs.openstack.org/pbr/latest/user/using.html#environment-markers
    ERROR:root:Error parsing
    Traceback (most recent call last):
      File "/usr/lib/python2.7/site-packages/pbr/core.py", line 96, in pbr
        attrs = util.cfg_to_args(path, dist.script_args)
      File "/usr/lib/python2.7/site-packages/pbr/util.py", line 258, in cfg_to_args
        kwargs = setup_cfg_to_setup_kwargs(config, script_args)
      File "/usr/lib/python2.7/site-packages/pbr/util.py", line 456, in setup_cfg_to_setup_kwargs
        if pkg_resources.evaluate_marker('(%s)' % env_marker):
      File "/usr/lib/python2.7/site-packages/pkg_resources.py", line 1364, in evaluate_marker
        return interpret(parser.expr(text).totuple(1)[1])
      File "/usr/lib/python2.7/site-packages/pkg_resources.py", line 1342, in interpret
        return op(nodelist)
      File "/usr/lib/python2.7/site-packages/pkg_resources.py", line 1307, in atom
        return interpret(nodelist[2])
      File "/usr/lib/python2.7/site-packages/pkg_resources.py", line 1342, in interpret
        return op(nodelist)
      File "/usr/lib/python2.7/site-packages/pkg_resources.py", line 1324, in comparison
        raise SyntaxError(repr(cop)+" operator not allowed in environment markers")
    SyntaxError: '>=' operator not allowed in environment markers
    error in setup command: Error parsing /opt/stack/keystone/setup.cfg: SyntaxError: '>=' operator not allowed in environment markers
 

Thanks,
JamO


Re: [app-dev] [integration-dev] OFP docs changes

Dhiraj Sharma
 

Hello all,

 The whole documentation is updated now  https://git.opendaylight.org/gerrit/c/openflowplugin/+/90565
I faced some issues while updating the docs in sphinx which I had solved and a successful build is ready now.

On Wed, Aug 12, 2020 at 12:10 PM Dhiraj Sharma via lists.opendaylight.org <dhiraj.8.sharma=gmail.com@...> wrote:
Hello all, 

I had rebased it yesterday.

If the changes in OPF looks good should I apply it elsewhere in the documentation.

On Aug 11, 2020 05:26, "Luis Gomez" <ecelgp@...> wrote:
Hi Dhiraj, I think you have to rebase your patch after this version bump:


BR/Luis


On Aug 8, 2020, at 10:53 AM, Dhiraj Sharma <dhiraj.8.sharma@...> wrote:

Hello all,

 Please review my latest change at https://git.opendaylight.org/gerrit/c/openflowplugin/+/90565/6/docs/users/flow-examples.rst and I will apply it elsewhere and will push the whole documentation change elsewhere.


Thank You
Dhiraj Sharma

On Mon, Jul 27, 2020 at 9:24 PM Dhiraj Sharma via lists.opendaylight.org<dhiraj.8.sharma=gmail.com@...> wrote:
Oh, Great news for me sir.

I will keep up with my work in this week.



Thank You
Dhiraj Sharma

On Jul 27, 2020 21:18, "Luis Gomez" <ecelgp@...> wrote:
Hi Dhiraj,

FYI your patch for operations.rst is merged, please continue with the other files.

BR/Luis

On Jul 23, 2020, at 8:20 AM, Dhiraj Sharma <dhiraj.8.sharma@...> wrote:

Awesome, I will apply the changes sir.



Thank You
Dhiraj Sharma

On Jul 23, 2020 20:39, "Luis Gomez" <ecelgp@...> wrote:
Yes Dhiraj, it looks good now.

Can you please extend the tab example in this patch: https://git.opendaylight.org/gerrit/c/openflowplugin/+/90547 to all the REST bodies in the same file?

After that, we can +1 the patch and send for approval/merge. Once the patch is merged, you can continue working in other REST bodies in other files.

BR/Luis


On Jul 23, 2020, at 6:00 AM, Dhiraj Sharma <dhiraj.8.sharma@...> wrote:

Respected Sir,

 Are new changes in OPF documentation good.
Should I apply it on all the required fields?


Thank You
Dhiraj Sharma

On Jul 17, 2020 10:26, "Dhiraj Sharma via lists.opendaylight.org" <dhiraj.8.sharma=gmail.com@...> wrote:
Got the point sir, I will push once the UI looks correct.
As of now the changes didn't look same as we expected.

On Jul 17, 2020 08:26, "Luis Gomez" <ecelgp@...> wrote:
According to this: https://github.com/djungelorm/sphinx-tabs, you have to use code-tabs. Also when you use code-tabs, make sure you use same indent as in the examples in this github, otherwise the table will not look good.

BR/Luis

> On Jul 16, 2020, at 7:05 PM, Dhiraj Sharma <dhiraj.8.sharma@...> wrote:
> 
> Hello sir, with code-tab it was working you can check the previous patch.
> 
> But in this new patch with tab it is giving errors as extra line spaces are required at each node and termination as it is XML and JSON codes which are providing issues.
> I used tab as per Tejas sir reviews.
> 
> 
> ThaK You
> Dhiraj
> 
> On Jul 17, 2020 6:56 AM, "Luis Gomez" <ecelgp@...> wrote:
> Hi Dhiraj,
> 
> The patch failed, are you facing more issues?
> 
>> On Jul 14, 2020, at 8:33 PM, Dhiraj Sharma <dhiraj.8.sharma@...> wrote:
>> 
>> Hello Sir,
>> 
>> I have updated the patch now  https://git.opendaylight.org/gerrit/c/openflowplugin/+/90547
>> 
>> 
>> 
>> On Tue, Jul 14, 2020 at 10:30 PM Tejas Nevrekar <tejas.nevrekar@...> wrote:
>> Dhiraj, can you please check this example https://github.com/djungelorm/sphinx-tabs/blob/master/example/index.rst? 
>> 
>> I think you need to use tab and not code-tab for the json and xml.
>> 
>> On Tue, Jul 14, 2020, 4:09 PM Dhiraj Sharma <dhiraj.8.sharma@...> wrote:
>> Sorry for being late please check the changes at first payload as a demo and you can review that part where I will apply changes subsequently to other payloads likewise.Both in flow-examples and operation.rst files.
>> 
>> https://git.opendaylight.org/gerrit/c/openflowplugin/+/90547 
>> 
>> 
>> 
>> Thank You
>> Dhiraj 
>> 
>> On Tue, Jul 14, 2020 at 10:33 AM Dhiraj Sharma <dhiraj.8.sharma@...> wrote:
>> Yes sure, I will push changes asap.
>> 
>> On Jul 14, 2020 10:07 AM, "Luis Gomez" <ecelgp@...> wrote:
>> Dhiraj, can you please push the change to gerrit and share the link so we can take a look?
>> 
>>> On Jul 13, 2020, at 9:14 PM, Dhiraj Sharma <dhiraj.8.sharma@...> wrote:
>>> 
>>> 
>>> So are you saying current version of sphinx in ODL Jenkins (3.0.4) is not compatible with the tabs plugin? do you have a jenkins rtd job failing for this reason? if so can you share the link?
>>> 
>>> BR/Luis
>>> 
>>> Hello Sir, 
>>>  I thought that rtdd jenkins may fail, if I use sphinx tabs as locally tox was emitting error. But the problem was with cached ".tox" which after deletion worked fine but UI is not as expected.
>>> 
>>> 
>>> Works just fine with the sphinx-tabs basic example from their site. Here was my quick test with the odl documentation project:
>>> 
>>> https://git.opendaylight.org/gerrit/c/docs/+/91311/1/docs/documentation.rst
>>> 
>>> (Although our current bootstrap theme does not appear to render the tabs in a nice way, but it works.)
>>> 
>>> Dhiraj,
>>> 
>>> If you already ran docs builds _before_ sphinx-tabs support was merged (tox -e docs) then you need to clear your cache by deleting the .tox directory in the repo. Otherwise it might use the old cached requirements and may not pick up the new tabs support.
>>> 
>>> Regards,
>>> Thanh
>>> 
>>> Thank You for the example sir, I worked similarly.The problem was with the stored cached directory of ".tox" which I used to build earlier.
>>> After deleting and then again testing yields the output but the UI is not the same as expected.
>>> 
>>> Please check below attached screenshots where I tried https://git.opendaylight.org/gerrit/c/docs/+/91311/1/docs/documentation.rst#23 too.
>>> The "code-tab" is also not showing the JSON tab in the below screenshot.
>>> So, even if the UI is not that same should I push the changes?
>>> 
>>> Thank You
>>> Dhiraj Sharma
>>> <Screenshot (462).png><Screenshot (463).png>
>> 
> 














Re: passing jobs being marked unstable

Thanh ha <zxiiro@...>
 

On Thu, Aug 13, 2020 at 6:48 PM Thanh Ha <zxiiro@...> wrote:
On Thu, Aug 13, 2020 at 6:40 PM JamO Luhrsen <jluhrsen@...> wrote:
Here is the ticket:
https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/IT-20419#

This is preventing patches from being verified at the very least.

I updated with my analysis, looks like a configuration file the lf-infra-ship-logs macro is looking for has gone missing. It needs to be restored so that the publisher doesn't set the build to UNSTABLE.

Okay after looking at this more closely, my original analysis is incorrect. Looks like it's an SSL certificate issue with Vexxhost. The job-costs.sh script is running this curl command:

curl 'https://pricing.vexxhost.net/v1/pricing/odl-highcpu-2/cost?seconds=246'
19:27:47 curl: (51) Unable to communicate securely with peer: requested domain name does not match the server's certificate.

Regards,
Thanh


Re: passing jobs being marked unstable

Thanh ha <zxiiro@...>
 

On Thu, Aug 13, 2020 at 6:40 PM JamO Luhrsen <jluhrsen@...> wrote:
Here is the ticket:
https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/IT-20419#

This is preventing patches from being verified at the very least.

I updated with my analysis, looks like a configuration file the lf-infra-ship-logs macro is looking for has gone missing. It needs to be restored so that the publisher doesn't set the build to UNSTABLE.

Regards,
Thanh
 


passing jobs being marked unstable

JamO Luhrsen
 

Here is the ticket:
https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/IT-20419#

This is preventing patches from being verified at the very least.

Thanks,
JamO

321 - 340 of 14635