|
Re: global-jjb vs. packer vs. Jenkins jobs
On 03/02/2021 00:03, Anil Belur wrote: Greetings Robert: Hello Anil, lf-env.sh: Creates a virtual env and sets up the environment, while the
python-tools-install.sh Installs the python tools/utils during Job
runtime. Since releng/global-jjb is a repo of Generic JJB templates (can
be used by any of the CI management repositories), its up to the
$project/$job to install the dependencies required for running the job. Understood. At the end of the day, though, we have only a few classes of jobs and there is a ton of commonalities between them. We have discussed this in the past, installing PyPI dependencies during
packer image build time, comes with its own set of problems and added costs:
1. This requires maintaining a large number of packer images (if the
project needs to support multiple versions of python/PyPI deps). I do not believe this is the case for OpenDaylight jobs. For example each and every job I looked at performs two things: - python-tools-install.sh (70 seconds) - job-cost.sh (39 seconds) 2. All releng/global-jjb (templates) scripts do not require all of the
PyPi dependencies to be installed and are tied down to the $job or
$project, since this approach binding them all into the same env has a
risk of the deps being broken more frequently.
3. PyPi libs/modules are updated more frequently. While that is true, this line of reasoning completely ignores the failure mode and recovery. As it stands any of: - busted global-jjb - PyPi package updates - PyPi repository unavailability As we have seen in these past weeks, any such failure immediately propagates to all jobs and breaks them -- resulting in nothing working anymore, with no real avenue for recovery without help of LF IT. We actually went through exactly this discussion when we had Sigul failures -- and Sigul is now part of base images. It is deemed sufficient to update our cloud images once a month -- and that includes all sorts security fixes and similar. As a community we are free to decide when to spin new images and can do that completely without LF IT intervention. I am sorry, but I fail to see how Python packages special enough to inflict: - breakages occurring at completely random times - incur 2-5 minutes of infra install to *each and every job* we run[*] I am sorry to say that the world has changed in the past 5 years and we no longer have the attention of LF IT staff that made resolution of these failures a matter of hours -- it really is multiple days. That fact alone makes a huge difference when weighing pros and cons. Regards, Robert [*] Just take a good look at what https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/aaa-maven-verify-master-mvn35-openjdk11/3/console-timestamp.log.gzdid: Total job runtime: 9m56s Useful build time: 7m16s Setup/teardown time: 2m40s That's **27%** of the time spent on infra, amounting to **37%** overhead.
Thanks,
Anil
On Mon, Jan 25, 2021 at 7:44 PM Robert Varga <nite@...
<mailto:nite@...>> wrote:
Hello everyone,
as the (still current) failure to start Jenkins jobs shows, our current
way of integrating with external dependencies (global-jjb) is beyond
fragile.
The way our jobs work is that:
1) we have a base image, created by builder-packer-* jobs on a regular
basis and roll up distro upgrades plus some other things (like mininet,
etc.) that we need
2) the Jenkins job launches on that base image and call two scripts from
global-jjb, both of which end up installing more things:
a) python-tools-install.sh
b) lf-env.sh
3) the actual job runs
4) some more stuff invoking lf-env.sh to setup another Python
environment runs.
Now, it is clear that everything in 1) is invariant and updated in a
controlled way.
The problem is with 2), where again, everything is supposed to be
invariant for a particular version of global-jjb -- yet we reinstall
these things on every single job run.
Not only is this subject to random breakage (like now, or when pip
repositories are unavailable), etc.
It also takes around 3 minutes of each job execution, which does not
sound like much, but it is full 30%(!) of runtime of
yangtools-release-merge (which takes around 10 minutes).
We obviously can and must do better: global-jjb's environment-impacting
scripts must all be executed during builder-packer, so that they become
proper invariants.
For that, global-jjb needs to grow two things:
1) a way to install *all* of its dependencies without doing anything
else, for use in packer jobs
2) compatibility checks on the environment to ensure it is uptodate
enough to run a particular global-jjb version's scripts
With that, our jobs should be both faster and more reliable.
Does anybody see a problem why this would not work?
If not, I will be filing LFIT issues to get this done.
Regards,
Robert
|
|
|
Re: global-jjb vs. packer vs. Jenkins jobs
Greetings Robert:
lf-env.sh: Creates a virtual env and sets up the environment, while the python-tools-install.sh Installs the python tools/utils during Job runtime. Since releng/global-jjb is a repo of Generic JJB templates (can be used by any of the CI management repositories), its up to the $project/$job to install the dependencies required for running the job.
We have discussed this in the past, installing PyPI dependencies during packer image build time, comes with its own set of problems and added costs: 1. This requires maintaining a large number of packer images (if the project needs to support multiple versions of python/PyPI deps). 2. All releng/global-jjb (templates) scripts do not require all of the PyPi dependencies to be installed and are tied down to the $job or $project, since this approach binding them all into the same env has a risk of the deps being broken more frequently. 3. PyPi libs/modules are updated more frequently.
Thanks, Anil
On Mon, Jan 25, 2021 at 7:44 PM Robert Varga < nite@...> wrote: Hello everyone,
as the (still current) failure to start Jenkins jobs shows, our current
way of integrating with external dependencies (global-jjb) is beyond
fragile.
The way our jobs work is that:
1) we have a base image, created by builder-packer-* jobs on a regular
basis and roll up distro upgrades plus some other things (like mininet,
etc.) that we need
2) the Jenkins job launches on that base image and call two scripts from
global-jjb, both of which end up installing more things:
a) python-tools-install.sh
b) lf-env.sh
3) the actual job runs
4) some more stuff invoking lf-env.sh to setup another Python
environment runs.
Now, it is clear that everything in 1) is invariant and updated in a
controlled way.
The problem is with 2), where again, everything is supposed to be
invariant for a particular version of global-jjb -- yet we reinstall
these things on every single job run.
Not only is this subject to random breakage (like now, or when pip
repositories are unavailable), etc.
It also takes around 3 minutes of each job execution, which does not
sound like much, but it is full 30%(!) of runtime of
yangtools-release-merge (which takes around 10 minutes).
We obviously can and must do better: global-jjb's environment-impacting
scripts must all be executed during builder-packer, so that they become
proper invariants.
For that, global-jjb needs to grow two things:
1) a way to install *all* of its dependencies without doing anything
else, for use in packer jobs
2) compatibility checks on the environment to ensure it is uptodate
enough to run a particular global-jjb version's scripts
With that, our jobs should be both faster and more reliable.
Does anybody see a problem why this would not work?
If not, I will be filing LFIT issues to get this done.
Regards,
Robert
|
|
|
Re: [OpenDaylight TSC] [opendaylight-dev][release] OpenDaylight - Aluminium SR2 release status
toggle quoted messageShow quoted text
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.
|
|
|
Re: [OpenDaylight TSC] [opendaylight-dev][release] OpenDaylight - Aluminium SR2 release status
Daniel de la Rosa
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@...> 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:
BR/Luis
I agree with the suggestion to skip Al SR2. Best Regards Guillaume De : Luis Gomez [mailto:ecelgp@...]
Envoyé : jeudi 28 janvier 2021 22:11
À : Venkatrangan Govindarajan
Cc : Daniel de la Rosa; Oleksii Mozghovyi; THOUENON Gilles TGI/OLN; integration-dev@...; Anil Belur; Casey Cain; Jordan Conway; LAMBERT Guillaume TGI/OLN; Release; Robert Varga; TSC; 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@...> wrote: The problem occurs if the RFC8040 is used curl 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> 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@...> எழுதியது: Thanks Oleksii... IMHO, this issue is not a show stopper for Aluminium SR2 but please confirm 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: The thing is that {apiRoot}/restconf is managed by a different web initializer and doesn't have such an issue.
From: release@... <release@...> on behalf of Venkatrangan Govindarajan <gvrangan@...>
Sent: Thursday, January 28, 2021 8:01:59 PM
To: Luis Gomez
Cc: Daniel de la Rosa; THOUENON Gilles TGI/OLN; integration-dev@...; Anil Belur; Casey Cain; Jordan Conway; LAMBERT Guillaume TGI/OLN; Release; Robert Varga; TSC; 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... The GET seems to require authorization. Also used wrong password which was also blocked. வியா., 28 ஜன., 2021, பிற்பகல் 10:53 அன்று, Luis Gomez < ecelgp@...> எழுதியது: It seems like we have to stop the Aluminium SR2 release after hearing the authentication issue from Robert.
Thank you all.. @Luis Gomez please proceed with distribution at your earliest convenience Hello, I’ve proceeded to the TransportPCE release merge job for Aluminium SR2 which is tagged with version 2.2.0. Everything on our side seems ok. Tell us if additional action is required from our side. Best Regards, Gilles Thouénon Thanks Daniel. On TransportPCE side, our stable/aluminium branch is ready. We encountered the same issue as So, we are waiting for the resolution of Jenkins jobs failing issue. Best Regards, Gilles Thouenon Thanks Anil. TransportPCE team, please proceed at your earliest convenience. On Sun, Jan 24, 2021 at 7:43 PM Anil Belur < 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.
_________________________________________________________________________________________________________________________ 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.
|
|
|
Re: [OpenDaylight TSC] [opendaylight-dev][release] OpenDaylight - Aluminium SR2 release status
Oleksii Mozghovyi <Oleksii.Mozghovyi@...>
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
The thing is that {apiRoot}/restconf is managed by a different web initializer and doesn't have such an issue.
From: release@... <release@...> on behalf of Venkatrangan Govindarajan <gvrangan@...>
Sent: Thursday, January 28, 2021 8:01:59 PM
To: Luis Gomez
Cc: Daniel de la Rosa; THOUENON Gilles TGI/OLN; integration-dev@...; Anil Belur; Casey Cain; Jordan Conway; LAMBERT Guillaume TGI/OLN; Release; Robert Varga; TSC; 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...
******************
************
The GET seems to require authorization. Also used wrong password which was also blocked.
வியா., 28 ஜன., 2021, பிற்பகல் 10:53 அன்று, Luis Gomez < ecelgp@...> எழுதியது:
It seems like we have to stop the Aluminium SR2 release after hearing the authentication issue from Robert.
Thank you all.. @Luis Gomez please proceed with distribution at your earliest convenience
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 )
|
|
|
Thanks Andy :)
toggle quoted messageShow quoted text
On Jan 29, 2021, at 6:47 AM, Andrew Grimberg <agrimberg@...> wrote:
On 1/28/21 8:11 PM, Luis Gomez wrote:
FYI, not sure which jobs are impacted but shellcheck pre-commit is broken here:
https://jenkins.opendaylight.org/releng/job/builder-tox-verify-master/
BR/Luis The pre-commit project released 2.10.0 which seems to have introduced an
incompatibility with jumanjihouse/pre-commit-hooks and in particular the
shellcheck hook.
At this time we don't know if it was intentional or not, but we've taken
to pinning pre-commit to version 2.9.3 in our tox.ini for the time being.
This is a project by project change for projects that use shellcheck in
their .pre-commit-config.yaml file that would need to happen as it
doesn't come from global-jjb.
For releng/builder I've pushed up [0] that does this pinning.
-Andy-
[0] https://git.opendaylight.org/gerrit/c/releng/builder/+/94887
--
Andrew J Grimberg
Manager Release Engineering
The Linux Foundation
<OpenPGP_0x3360FFB703A9DA1F_and_old_rev.asc>
|
|
|
Andrew Grimberg
On 1/28/21 8:11 PM, Luis Gomez wrote: FYI, not sure which jobs are impacted but shellcheck pre-commit is broken here:
https://jenkins.opendaylight.org/releng/job/builder-tox-verify-master/
BR/Luis The pre-commit project released 2.10.0 which seems to have introduced an incompatibility with jumanjihouse/pre-commit-hooks and in particular the shellcheck hook. At this time we don't know if it was intentional or not, but we've taken to pinning pre-commit to version 2.9.3 in our tox.ini for the time being. This is a project by project change for projects that use shellcheck in their .pre-commit-config.yaml file that would need to happen as it doesn't come from global-jjb. For releng/builder I've pushed up [0] that does this pinning. -Andy- [0] https://git.opendaylight.org/gerrit/c/releng/builder/+/94887-- Andrew J Grimberg Manager Release Engineering The Linux Foundation
|
|
|
Re: [OpenDaylight TSC] [opendaylight-dev][release] OpenDaylight - Aluminium SR2 release status
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:
BR/Luis
I agree with the suggestion to skip Al SR2. Best Regards Guillaume De : Luis Gomez [mailto:ecelgp@...]
Envoyé : jeudi 28 janvier 2021 22:11
À : Venkatrangan Govindarajan
Cc : Daniel de la Rosa; Oleksii Mozghovyi; THOUENON Gilles TGI/OLN; integration-dev@...; Anil Belur; Casey Cain; Jordan Conway; LAMBERT Guillaume TGI/OLN; Release; Robert Varga; TSC; 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@...> wrote: The problem occurs if the RFC8040 is used curl 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> 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@...> எழுதியது: Thanks Oleksii... IMHO, this issue is not a show stopper for Aluminium SR2 but please confirm 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: The thing is that {apiRoot}/restconf is managed by a different web initializer and doesn't have such an issue.
From: release@... <release@...> on behalf of Venkatrangan Govindarajan <gvrangan@...>
Sent: Thursday, January 28, 2021 8:01:59 PM
To: Luis Gomez
Cc: Daniel de la Rosa; THOUENON Gilles TGI/OLN; integration-dev@...; Anil Belur; Casey Cain; Jordan Conway; LAMBERT Guillaume TGI/OLN; Release; Robert Varga; TSC; 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... The GET seems to require authorization. Also used wrong password which was also blocked. வியா., 28 ஜன., 2021, பிற்பகல் 10:53 அன்று, Luis Gomez < ecelgp@...> எழுதியது: It seems like we have to stop the Aluminium SR2 release after hearing the authentication issue from Robert.
Thank you all.. @Luis Gomez please proceed with distribution at your earliest convenience Hello, I’ve proceeded to the TransportPCE release merge job for Aluminium SR2 which is tagged with version 2.2.0. Everything on our side seems ok. Tell us if additional action is required from our side. Best Regards, Gilles Thouénon Thanks Daniel. On TransportPCE side, our stable/aluminium branch is ready. We encountered the same issue as So, we are waiting for the resolution of Jenkins jobs failing issue. Best Regards, Gilles Thouenon Thanks Anil. TransportPCE team, please proceed at your earliest convenience. On Sun, Jan 24, 2021 at 7:43 PM Anil Belur < 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.
_________________________________________________________________________________________________________________________ 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.
|
|
|
|
|
|
Re: [OpenDaylight TSC] [opendaylight-dev][release] OpenDaylight - Aluminium SR2 release status
I agree with the suggestion to skip Al SR2.
Best Regards
Guillaume
De : Luis Gomez [mailto:ecelgp@...]
Envoyé : jeudi 28 janvier 2021 22:11
À : Venkatrangan Govindarajan
Cc : Daniel de la Rosa; Oleksii Mozghovyi; THOUENON Gilles TGI/OLN; integration-dev@...; Anil Belur; Casey Cain; Jordan Conway; LAMBERT Guillaume TGI/OLN; Release; Robert Varga; TSC; 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?
toggle quoted messageShow quoted text
On Jan 28, 2021, at 10:33 AM, Venkatrangan Govindarajan < gvrangan@...> wrote:
The problem occurs if the RFC8040 is used
curl
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
> 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@...>
எழுதியது:
Thanks Oleksii... IMHO, this issue is not a show stopper for Aluminium SR2 but please confirm
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:
The thing is that {apiRoot}/restconf is managed by a different web initializer and doesn't have such an issue.
From:
release@... <release@...> on behalf of Venkatrangan Govindarajan <gvrangan@...>
Sent: Thursday, January 28, 2021 8:01:59 PM
To: Luis Gomez
Cc: Daniel de la Rosa; THOUENON Gilles TGI/OLN;
integration-dev@...; Anil Belur; Casey Cain; Jordan Conway; LAMBERT Guillaume TGI/OLN; Release; Robert Varga; TSC;
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...
The GET seems to require authorization. Also used wrong password which was also blocked.
வியா., 28
ஜன., 2021,
பிற்பகல் 10:53 அன்று, Luis Gomez <ecelgp@...>
எழுதியது:
It seems like we have to stop the Aluminium SR2 release after hearing the authentication issue from Robert.
Thank you all.. @Luis Gomez please proceed with distribution
at your earliest convenience
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.
|
|
|
Re: [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?
On Jan 28, 2021, at 10:33 AM, Venkatrangan Govindarajan < gvrangan@...> wrote:
The problem occurs if the RFC8040 is used
curl 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> 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@...> எழுதியது: Thanks Oleksii... IMHO, this issue is not a show stopper for Aluminium SR2 but please confirm
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:
The thing is that {apiRoot}/restconf is managed by a different web initializer and doesn't have such an issue.
From: release@... <release@...> on behalf of Venkatrangan Govindarajan <gvrangan@...>
Sent: Thursday, January 28, 2021 8:01:59 PM
To: Luis Gomez
Cc: Daniel de la Rosa; THOUENON Gilles TGI/OLN; integration-dev@...; Anil Belur; Casey Cain; Jordan Conway; LAMBERT Guillaume TGI/OLN; Release; Robert Varga; TSC; 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...
******************
************
The GET seems to require authorization. Also used wrong password which was also blocked.
வியா., 28 ஜன., 2021, பிற்பகல் 10:53 அன்று, Luis Gomez < ecelgp@...> எழுதியது:
It seems like we have to stop the Aluminium SR2 release after hearing the authentication issue from Robert.
Thank you all.. @Luis Gomez please proceed with distribution at your earliest convenience
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 )
|
|
|
Re: [OpenDaylight TSC] [opendaylight-dev][release] OpenDaylight - Aluminium SR2 release status
Venkatrangan Govindarajan
The problem occurs if the RFC8040 is used
curl 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> 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@...> எழுதியது:
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@...> 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:
The thing is that {apiRoot}/restconf is managed by a different web initializer and doesn't have such an issue.
From: release@... <release@...> on behalf of Venkatrangan Govindarajan <gvrangan@...>
Sent: Thursday, January 28, 2021 8:01:59 PM
To: Luis Gomez
Cc: Daniel de la Rosa; THOUENON Gilles TGI/OLN; integration-dev@...; Anil Belur; Casey Cain; Jordan Conway; LAMBERT Guillaume TGI/OLN; Release; Robert Varga; TSC; 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...
******************
************
The GET seems to require authorization. Also used wrong password which was also blocked.
வியா., 28 ஜன., 2021, பிற்பகல் 10:53 அன்று, Luis Gomez < ecelgp@...> எழுதியது:
It seems like we have to stop the Aluminium SR2 release after hearing the authentication issue from Robert.
Thank you all.. @Luis Gomez please proceed with distribution at your earliest convenience
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 )
|
|
|
Re: [OpenDaylight TSC] [opendaylight-dev][release] OpenDaylight - Aluminium SR2 release status
Daniel de la Rosa
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@...> 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:
The thing is that {apiRoot}/restconf is managed by a different web initializer and doesn't have such an issue.
From: release@... <release@...> on behalf of Venkatrangan Govindarajan <gvrangan@...>
Sent: Thursday, January 28, 2021 8:01:59 PM
To: Luis Gomez
Cc: Daniel de la Rosa; THOUENON Gilles TGI/OLN; integration-dev@...; Anil Belur; Casey Cain; Jordan Conway; LAMBERT Guillaume TGI/OLN; Release; Robert Varga; TSC; 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...
******************
************
The GET seems to require authorization. Also used wrong password which was also blocked.
வியா., 28 ஜன., 2021, பிற்பகல் 10:53 அன்று, Luis Gomez < ecelgp@...> எழுதியது:
It seems like we have to stop the Aluminium SR2 release after hearing the authentication issue from Robert.
Thank you all.. @Luis Gomez please proceed with distribution at your earliest convenience
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 )
|
|
|
Re: [OpenDaylight TSC] [opendaylight-dev][release] OpenDaylight - Aluminium SR2 release status
Venkatrangan Govindarajan
Just downloaded SR2 and installed some project that uses topology model and executed this...
****************** ************
The GET seems to require authorization. Also used wrong password which was also blocked.
வியா., 28 ஜன., 2021, பிற்பகல் 10:53 அன்று, Luis Gomez < ecelgp@...> எழுதியது:
It seems like we have to stop the Aluminium SR2 release after hearing the authentication issue from Robert.
Thank you all.. @Luis Gomez please proceed with distribution at your earliest convenience
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 )
|
|
|
Re: [OpenDaylight TSC] [opendaylight-dev][release] OpenDaylight - Aluminium SR2 release status
Daniel de la Rosa
As we agree, @Venkatrangan Govindarajan tested this issue NETCONF-753 and it seems to be resolved or not part of Aluminium SR2... @Luis Gomez please confirm that we can move forward with Aluminium SR2 whenever you have a chance
Thank you all
On Thu, Jan 28, 2021 at 9:23 AM Luis Gomez < ecelgp@...> wrote: It seems like we have to stop the Aluminium SR2 release after hearing the authentication issue from Robert.
Thank you all.. @Luis Gomez please proceed with distribution at your earliest convenience
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: [OpenDaylight TSC] [opendaylight-dev][release] OpenDaylight - Aluminium SR2 release status
It seems like we have to stop the Aluminium SR2 release after hearing the authentication issue from Robert.
Thank you all.. @Luis Gomez please proceed with distribution at your earliest convenience
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: [OpenDaylight TSC] [opendaylight-dev][release] OpenDaylight - Aluminium SR2 release status
Daniel de la Rosa
Thank you all.. @Luis Gomez please proceed with distribution at your earliest convenience
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: [OpenDaylight TSC] [opendaylight-dev][release] OpenDaylight - Aluminium SR2 release status
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/
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@...]
De la part de Gilles Thouenon via lists.opendaylight.org
Envoyé : lundi 25 janvier 2021 08:31
À : Daniel de la Rosa <ddelarosa0707@...>; Anil Belur <abelur@...>; Luis Gomez <ecelgp@...>; LAMBERT Guillaume TGI/OLN <guillaume.lambert@...>
Cc : 'integration-dev@...' (integration-dev@...) (integration-dev@...) <integration-dev@...>; Release <release@...>; TSC <tsc@...>; Jordan
Conway <jconway@...>; Casey Cain <ccain@...>; Robert Varga <nite@...>; Venkatrangan Govindarajan <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
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@...]
De la part de Daniel de la Rosa
Envoyé : lundi 25 janvier 2021 06:39
À : Anil Belur <abelur@...>; Luis Gomez <ecelgp@...>; LAMBERT Guillaume TGI/OLN <guillaume.lambert@...>
Cc : 'integration-dev@...' (integration-dev@...) (integration-dev@...) <integration-dev@...>;
Release <release@...>; TSC <tsc@...>; Jordan Conway <jconway@...>;
Casey Cain <ccain@...>; Robert Varga <nite@...>; Venkatrangan Govindarajan <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.
toggle quoted messageShow quoted text
On Sun, Jan 24, 2021 at 7:43 PM Anil Belur < 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.
_________________________________________________________________________________________________________________________
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: [OpenDaylight TSC] [opendaylight-dev][release] OpenDaylight - Aluminium SR2 release status
toggle quoted messageShow quoted text
On Sun, Jan 24, 2021 at 7:43 PM Anil Belur < 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.
_________________________________________________________________________________________________________________________
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.
|
|
|
global-jjb vs. packer vs. Jenkins jobs
Hello everyone,
as the (still current) failure to start Jenkins jobs shows, our current
way of integrating with external dependencies (global-jjb) is beyond
fragile.
The way our jobs work is that:
1) we have a base image, created by builder-packer-* jobs on a regular
basis and roll up distro upgrades plus some other things (like mininet,
etc.) that we need
2) the Jenkins job launches on that base image and call two scripts from
global-jjb, both of which end up installing more things:
a) python-tools-install.sh
b) lf-env.sh
3) the actual job runs
4) some more stuff invoking lf-env.sh to setup another Python
environment runs.
Now, it is clear that everything in 1) is invariant and updated in a
controlled way.
The problem is with 2), where again, everything is supposed to be
invariant for a particular version of global-jjb -- yet we reinstall
these things on every single job run.
Not only is this subject to random breakage (like now, or when pip
repositories are unavailable), etc.
It also takes around 3 minutes of each job execution, which does not
sound like much, but it is full 30%(!) of runtime of
yangtools-release-merge (which takes around 10 minutes).
We obviously can and must do better: global-jjb's environment-impacting
scripts must all be executed during builder-packer, so that they become
proper invariants.
For that, global-jjb needs to grow two things:
1) a way to install *all* of its dependencies without doing anything
else, for use in packer jobs
2) compatibility checks on the environment to ensure it is uptodate
enough to run a particular global-jjb version's scripts
With that, our jobs should be both faster and more reliable.
Does anybody see a problem why this would not work?
If not, I will be filing LFIT issues to get this done.
Regards,
Robert
|
|
|
