Daniel de la Rosa
Ok :) So i can start with Aluminium SR3 ahead of schedule, if that's what's needed here...
On Tue, Feb 2, 2021 at 1:11 PM Robert Varga < nite@...> wrote: We are not.
We are picking candidates for SR3 -- and
https://jenkins.opendaylight.org/releng/job/autorelease-release-aluminium-mvn35-openjdk11/360/
is good as any :)
Regards,
Robert
On 02/02/2021 15:58, Daniel de la Rosa wrote:
> Thanks Luis. So we are not updating the downloads page for Aluminium SR2
> right? we have release notes though
>
> On Thu, Jan 28, 2021 at 9:40 PM Luis Gomez <ecelgp@...
> <mailto:ecelgp@...>> wrote:
>
> OK, although we are not going to officially release Aluminium SR2, I
> went ahead and released the distribution for completeness and also
> in case someone wants to use this release for testing purposes:
>
> https://nexus.opendaylight.org/content/repositories/opendaylight.release/org/opendaylight/integration/opendaylight/0.13.2/
> <https://nexus.opendaylight.org/content/repositories/opendaylight.release/org/opendaylight/integration/opendaylight/0.13.2/>
>
> BR/Luis
>
>
>> On Jan 28, 2021, at 2:37 PM, <guillaume.lambert@...
>> <mailto:guillaume.lambert@...>>
>> <guillaume.lambert@...
>> <mailto:guillaume.lambert@...>> wrote:
>>
>> I agree with the suggestion to skip Al SR2.____
>> __ __
>> Best Regards____
>> Guillaume____
>> __ __
>> *De :* Luis Gomez [mailto:ecelgp@... <mailto:ecelgp@...>]
>> *Envoyé :* jeudi 28 janvier 2021 22:11
>> *À :* Venkatrangan Govindarajan
>> *Cc :* Daniel de la Rosa; Oleksii Mozghovyi; THOUENON Gilles
>> TGI/OLN; integration-dev@...
>> <mailto:integration-dev@...>; Anil Belur; Casey
>> Cain; Jordan Conway; LAMBERT Guillaume TGI/OLN; Release; Robert
>> Varga; TSC; Transportpce-dev@...
>> <mailto:Transportpce-dev@...>
>> *Objet :* Re: [integration-dev] [OpenDaylight TSC]
>> [opendaylight-dev][release] OpenDaylight - Aluminium SR2 release
>> status____
>> __ __
>> Well, since the odl-restconf feature includes both draft and
>> RFC8040 API, I believe this bug is effectively a security hole
>> with a non trivial workaround even for the draft users (e.g.
>> repack the restconf feature to skip RFC8040).____
>> __ __
>> So my suggest is to skip Aluminium SR2 official release. Other TSC
>> (or not TSC) opinions?____
>> __ __
>> BR/Luis____
>>
>>
>> ____
>> On Jan 28, 2021, at 10:33 AM, Venkatrangan Govindarajan
>> <gvrangan@... <mailto:gvrangan@...>> wrote:____
>> __ __
>> The problem occurs if the RFC8040 is used____
>> __ __
>> curl http://127.0.0.1:8181/rests/data/network-topology:network-topology
>> <http://127.0.0.1:8181/rests/data/network-topology:network-topology> -v
>> * Trying 127.0.0.1...
>> * Connected to 127.0.0.1 (127.0.0.1) port 8181 (#0)
>> > GET /rests/data/network-topology:network-topology HTTP/1.1
>> > Host: 127.0.0.1:8181 <http://127.0.0.1:8181/>
>> > User-Agent: curl/7.47.0
>> > Accept: */*
>> >
>> < HTTP/1.1 200 OK
>> < ETag: "2013-10-21-network-topology"
>> < Last-Modified: 2021-Jan-28 18:31:25
>> < Content-Type: application/yang-data+json
>> < Content-Length: 133
>> <
>> * Connection #0 to host 127.0.0.1 left intact
>> {"network-topology:net____
>> __ __
>> __ __
>> It does not require authorization. The issue seems to be
>> recreated.____
>> __ __
>> வியா., 28 ஜன., 2021, பிற்பகல் 11:46 அன்று, Daniel de la Rosa
>> <ddelarosa0707@...
>> <mailto:ddelarosa0707@...>> எழுதியது:____
>>
>> Thanks Oleksii... IMHO, this issue is not a show stopper for
>> Aluminium SR2 but please confirm____
>> __ __
>> On Thu, Jan 28, 2021 at 10:09 AM Oleksii Mozghovyi
>> <Oleksii.Mozghovyi@...
>> <mailto:Oleksii.Mozghovyi@...>> wrote:____
>>
>> __ __
>> Hello everyone,____
>> __ __
>> This issue is related only to the RFC8040 implementation
>> of the RESTconf, so you have to use a proper endpoint for
>> the testing, for example:____
>> http://127.0.0.1:8181/rests/data
>> <http://127.0.0.1:8181/rests/data>____
>> __ __
>> The thing is that {apiRoot}/restconf is managed by a
>> different web initializer and doesn't have such an issue.____
>> __ __
>> ------------------------------------------------------------------------
>> *From:* release@...
>> <mailto:release@...> <release@...
>> <mailto:release@...>> on behalf of
>> Venkatrangan Govindarajan <gvrangan@...
>> <mailto:gvrangan@...>>
>> *Sent:* Thursday, January 28, 2021 8:01:59 PM
>> *To:* Luis Gomez
>> *Cc:* Daniel de la Rosa; THOUENON Gilles
>> TGI/OLN; integration-dev@...
>> <mailto:integration-dev@...>; Anil
>> Belur; Casey Cain; Jordan Conway; LAMBERT Guillaume
>> TGI/OLN; Release; Robert Varga;
>> TSC; Transportpce-dev@...
>> <mailto:Transportpce-dev@...>
>> *Subject:* Re: [integration-dev] [OpenDaylight TSC]
>> [opendaylight-dev][release] OpenDaylight - Aluminium SR2
>> release status____
>> ____
>> Just downloaded SR2 and installed some project that uses
>> topology model and executed this...____
>> __ __
>> ******************____
>> curl http://127.0.0.1:8181/restconf/operational/network-topology:network-topology
>> <http://127.0.0.1:8181/restconf/operational/network-topology:network-topology> -v
>> * Trying 127.0.0.1...
>> * Connected to 127.0.0.1 (127.0.0.1) port 8181 (#0)
>> > GET
>> /restconf/operational/network-topology:network-topology
>> HTTP/1.1
>> > Host: 127.0.0.1:8181 <http://127.0.0.1:8181/>
>> > User-Agent: curl/7.47.0
>> > Accept: */*
>> >
>> < HTTP/1.1 401 Unauthorized
>> < WWW-Authenticate: BASIC realm="application"
>> < Content-Length: 0
>> <
>> * Connection #0 to host 127.0.0.1 left intact
>> gvrangan@gvrangan-Latitude-3490:~\>
>> curl http://127.0.0.1:8181/restconf/operational/network-topology:network-topology
>> <http://127.0.0.1:8181/restconf/operational/network-topology:network-topology> --user
>> 'admin:admin;
>> > ^C
>> gvrangan@gvrangan-Latitude-3490:~\>
>> curl http://127.0.0.1:8181/restconf/operational/network-topology:network-topology
>> <http://127.0.0.1:8181/restconf/operational/network-topology:network-topology> --user
>> 'admin:admin'
>> {"network-topology":{"topology":[{"topology-id":"hwvtep:1"},{"topology-id":"ovsdb:1"},{"topology-id":"netvirt:1"}]}}gvrangan@gvrangan-Latitude-3490:~\>
>> gvrangan@gvrangan-Latitude-3490:~\>
>> gvrangan@gvrangan-Latitude-3490:~\>
>> gvrangan@gvrangan-Latitude-3490:~\>
>> gvrangan@gvrangan-Latitude-3490:~\>
>> curl http://127.0.0.1:8181/restconf/operational/network-topology:network-topology
>> <http://127.0.0.1:8181/restconf/operational/network-topology:network-topology> --user
>> 'admin:admin'
>> {"network-topology":{"topology":[{"topology-id":"hwvtep:1"},{"topology-id":"ovsdb:1"},{"topology-id":"netvirt:1"}]}}gvrangan@gvrangan-Latitude-3490:~\>
>> gvrangan@gvrangan-Latitude-3490:~\>
>> gvrangan@gvrangan-Latitude-3490:~\>
>> curl http://127.0.0.1:8181/restconf/operational/network-topology:network-topology
>> <http://127.0.0.1:8181/restconf/operational/network-topology:network-topology> --user
>> 'admin:admin'
>> {"network-topology":{"topology":[{"topology-id":"hwvtep:1"},{"topology-id":"ovsdb:1"},{"topology-id":"netvirt:1"}]}}____
>> ************____
>> __ __
>> The GET seems to require authorization. Also used wrong
>> password which was also blocked.____
>> __ __
>> __ __
>> __ __
>> __ __
>> __ __
>> வியா., 28 ஜன., 2021, பிற்பகல் 10:53 அன்று, Luis Gomez
>> <ecelgp@... <mailto:ecelgp@...>> எழுதியது:____
>>
>> It seems like we have to stop the Aluminium SR2
>> release after hearing the authentication issue from
>> Robert.____
>>
>>
>> ____
>> On Jan 27, 2021, at 4:32 PM, Daniel de la Rosa
>> <ddelarosa0707@...
>> <mailto:ddelarosa0707@...>> wrote:____
>> __ __
>> Thank you all.. @Luis Gomez
>> <mailto:ecelgp@...> please proceed with
>> distribution at your earliest convenience____
>> __ __
>> On Mon, Jan 25, 2021 at 10:25 AM
>> <gilles.thouenon@...
>> <mailto:gilles.thouenon@...>> wrote:____
>>
>> Hello,____
>> ____
>> I’ve proceeded to the TransportPCE release merge
>> job for Aluminium SR2 which is tagged with version
>> 2.2.0.____
>> https://jenkins.opendaylight.org/releng/view/transportpce/job/transportpce-release-merge/lastBuild/
>> <https://jenkins.opendaylight.org/releng/view/transportpce/job/transportpce-release-merge/lastBuild/>____
>> Everything on our side seems ok.____
>> Tell us if additional action is required from our
>> side.____
>> ____
>> Best Regards,____
>> ____
>> Gilles Thouénon____
>> ____
>> *De :* release@...
>> <mailto:release@...> [mailto:release@...
>> <mailto:release@...>] *De la
>> part de* Gilles Thouenon
>> via lists.opendaylight.org
>> <http://lists.opendaylight.org/>
>> *Envoyé :* lundi 25 janvier 2021 08:31
>> *À :* Daniel de la Rosa <ddelarosa0707@...
>> <mailto:ddelarosa0707@...>>; Anil Belur
>> <abelur@...
>> <mailto:abelur@...>>; Luis Gomez
>> <ecelgp@... <mailto:ecelgp@...>>;
>> LAMBERT Guillaume TGI/OLN
>> <guillaume.lambert@...
>> <mailto:guillaume.lambert@...>>
>> *Cc :* 'integration-dev@...
>> <mailto:integration-dev@...>'
>> (integration-dev@...
>> <mailto:integration-dev@...>)
>> (integration-dev@...
>> <mailto:integration-dev@...>)
>> <integration-dev@...
>> <mailto:integration-dev@...>>;
>> Release <release@...
>> <mailto:release@...>>; TSC
>> <tsc@...
>> <mailto:tsc@...>>; Jordan
>> Conway <jconway@...
>> <mailto:jconway@...>>; Casey Cain
>> <ccain@...
>> <mailto:ccain@...>>; Robert Varga
>> <nite@... <mailto:nite@...>>; Venkatrangan
>> Govindarajan <gvrangan@...
>> <mailto:gvrangan@...>>
>> *Objet :* Re: [integration-dev] [OpenDaylight TSC]
>> [opendaylight-dev][release] OpenDaylight -
>> Aluminium SR2 release status____
>> ____
>> Thanks Daniel.____
>> On TransportPCE side, our stable/aluminium branch
>> is ready. We encountered the same issue as ____
>> https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/IT-21406
>> <https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/IT-21406>
>> to stage the release.____
>> So, we are waiting for the resolution of Jenkins
>> jobs failing issue.____
>> Best Regards,____
>> ____
>> Gilles Thouenon____
>> ____
>> *De :* integration-dev@...
>> <mailto:integration-dev@...> [mailto:integration-dev@...
>> <mailto:integration-dev@...>] *De
>> la part de* Daniel de la Rosa
>> *Envoyé :* lundi 25 janvier 2021 06:39
>> *À :* Anil Belur <abelur@...
>> <mailto:abelur@...>>; Luis Gomez
>> <ecelgp@... <mailto:ecelgp@...>>;
>> LAMBERT Guillaume TGI/OLN
>> <guillaume.lambert@...
>> <mailto:guillaume.lambert@...>>
>> *Cc :* 'integration-dev@...
>> <mailto:integration-dev@...>'
>> (integration-dev@...
>> <mailto:integration-dev@...>)
>> (integration-dev@...
>> <mailto:integration-dev@...>)
>> <integration-dev@...
>> <mailto:integration-dev@...>>;
>> Release <release@...
>> <mailto:release@...>>; TSC
>> <tsc@...
>> <mailto:tsc@...>>; Jordan
>> Conway <jconway@...
>> <mailto:jconway@...>>; Casey Cain
>> <ccain@...
>> <mailto:ccain@...>>; Robert Varga
>> <nite@... <mailto:nite@...>>; Venkatrangan
>> Govindarajan <gvrangan@...
>> <mailto:gvrangan@...>>
>> *Objet :* Re: [integration-dev] [OpenDaylight TSC]
>> [opendaylight-dev][release] OpenDaylight -
>> Aluminium SR2 release status____
>> ____
>> Thanks Anil. TransportPCE team, please proceed at
>> your earliest convenience.____
>> ____
>> ____
>> ____
>> On Sun, Jan 24, 2021 at 7:43 PM Anil Belur
>> <abelur@...
>> <mailto:abelur@...>> wrote:____
>>
>> Hello All,
>>
>> OpenDaylight Aluminium SR2 version bump is
>> complete and the staging repository is been
>> promoted. The 'stable/aluminum' branch is
>> unlocked and ready for development.____
>>
>> Pending activities that need to be completed
>> for the release:
>> 1. Self-managed projects release of Aluminum SR2.
>> 2. Release Distribution once the 1. is complete.
>> 3. Release notes - to be merged CR [1.]
>> 4. Update ODL downloads page [1.].
>>
>> Thanks to everyone who contributed to the release.
>>
>> Regards,
>> Anil Belur
>>
>> [0.] https://docs.opendaylight.org/en/latest/downloads.html
>> <https://docs.opendaylight.org/en/latest/downloads.html>
>> [1.] https://git.opendaylight.org/gerrit/c/docs/+/94758
>> <https://git.opendaylight.org/gerrit/c/docs/+/94758>____
>>
>> ____
>>
>> _____________________________________________________________________________________________________________________________
>>
>> ____
>>
>> 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.____
>>
>> __ __
>>
>>
>> ____
>> __ __
>> -- ____
>> Venkatrangan Govindarajan
>> ( When there is no wind...Row )____
>>
>>
>> ____
>> __ __
>> -- ____
>> Venkatrangan Govindarajan
>> ( When there is no wind...Row )____
>> __ __
>> _________________________________________________________________________________________________________________________
>>
>> 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.
>
>
>
>
>
|
