|
Daniel de la Rosa
Team,
Friendly reminder to review Sodium SR1 tracking sheet so we can release it on time.
-- Daniel de la Rosa
Customer Support Manager ( ODL release manager )
Lumina Networks Inc.
e: ddelarosa@...
m: +1 408 7728120
|
|
|
Srinivas,
Please look into the CSIT jobs for failures. Please take help from Karthika if required. I’m in parallel onboarding myself with the overall Netvirt CSIT. Let’s discuss and get this moving.
I see 20 CSIT jobs for NetVirt. We may want to eliminate the unnecessary jobs as well.
Regards,
Abhinav
toggle quoted message
Show quoted text
From: Daniel De La Rosa <ddelarosa@...>
Sent: Tuesday, October 22, 2019 1:49 AM
To: JamO Luhrsen <jluhrsen@...>; Abhinav Gupta <abhinav.gupta@...>
Cc: Release <release@...>; tsc@...; integration-dev@...; netvirt-dev@...; Bgpcep-Dev <bgpcep-dev@...>; controller-dev@...; lispflowmapping-dev@...;
netconf-dev@...; openflowplugin-dev@...
Subject: Re: [integration-dev] Sodium SR1 release candidate
Team,
Friendly reminder to review Sodium SR1 tracking sheet so we can release it on time.
--
Daniel de la Rosa
Customer Support Manager ( ODL release manager )
Lumina Networks Inc.
e: ddelarosa@...
m: +1 408 7728120
|
|
|
We need to get netvirt under control at this point. They have a
lot of jobs,
and were never fully healthy but without maintenance they are
going to create
a lot of work every release cycle.
I spent some time today going through our sodium sr1 failures and
made progress
on the sheet:
https://docs.google.com/spreadsheets/d/1CN-ACdIekRKMYRIuREIRALl6S8az7quAcQlRb3KeMJ8/edit?pli=1#gid=1864238939
there are three jobs with a basic netvirt failure that was ignored
in
the original sodium release (openstack instance not getting an ip
address)
which seems like a fundamental failure. The original sodium
release let
it through under the assumption that it was a test code problem. I
don't
think it is. I marked those as BLOCKER.
Should we mark the DCGW jobs as ignore? I don't have time to debug
them
and they are saw-tooth failures and inconsistent. No idea if they
are
regressions or not.
beyond netvirt, I'm following up on one openflowplugin job and
once those
are understood we will only be left with netvirt to be done.
Thanks,
JamO
On 10/21/19 11:41 PM, Abhinav Gupta
wrote:
toggle quoted message
Show quoted text
|
|
|
@Srinivas,
@R M Mishra: Please focus on the 3 rows JamO has already analyzed (thanks!) and pointed to as BLOCKERs.
Regards,
Abhinav
toggle quoted message
Show quoted text
From: TSC@... <TSC@...>
On Behalf Of JamO Luhrsen via Lists.Opendaylight.Org
Sent: Thursday, October 24, 2019 2:24 AM
To: Abhinav Gupta <abhinav.gupta@...>; Daniel De La Rosa <ddelarosa@...>; Srinivas Rachakonda <srinivas.rachakonda@...>
Cc: TSC@...
Subject: Re: [OpenDaylight TSC] [integration-dev] Sodium SR1 release candidate
We need to get netvirt under control at this point. They have a lot of jobs,
and were never fully healthy but without maintenance they are going to create
a lot of work every release cycle.
I spent some time today going through our sodium sr1 failures and made progress
on the sheet:
https://docs.google.com/spreadsheets/d/1CN-ACdIekRKMYRIuREIRALl6S8az7quAcQlRb3KeMJ8/edit?pli=1#gid=1864238939
there are three jobs with a basic netvirt failure that was ignored in
the original sodium release (openstack instance not getting an ip address)
which seems like a fundamental failure. The original sodium release let
it through under the assumption that it was a test code problem. I don't
think it is. I marked those as BLOCKER.
Should we mark the DCGW jobs as ignore? I don't have time to debug them
and they are saw-tooth failures and inconsistent. No idea if they are
regressions or not.
beyond netvirt, I'm following up on one openflowplugin job and once those
are understood we will only be left with netvirt to be done.
Thanks,
JamO
On 10/21/19 11:41 PM, Abhinav Gupta wrote:
Srinivas,
Please look into the CSIT jobs for failures. Please take help from Karthika if required. I’m in parallel onboarding myself with the overall Netvirt CSIT. Let’s discuss and get this moving.
I see 20 CSIT jobs for NetVirt. We may want to eliminate the unnecessary jobs as well.
Regards,
Abhinav
From: Daniel De La Rosa
<ddelarosa@...>
Sent: Tuesday, October 22, 2019 1:49 AM
To: JamO Luhrsen <jluhrsen@...>; Abhinav Gupta
<abhinav.gupta@...>
Cc: Release <release@...>;
tsc@...;
integration-dev@...;
netvirt-dev@...; Bgpcep-Dev
<bgpcep-dev@...>;
controller-dev@...;
lispflowmapping-dev@...;
netconf-dev@...;
openflowplugin-dev@...
Subject: Re: [integration-dev] Sodium SR1 release candidate
Team,
Friendly reminder to review Sodium SR1 tracking sheet so we can release it on time.
--
Daniel de la Rosa
Customer Support Manager ( ODL release manager )
Lumina Networks Inc.
e: ddelarosa@...
m: +1 408 7728120
|
|
|
toggle quoted message
Show quoted text
@Srinivas,
@R
M Mishra: Please focus on the 3 rows JamO has
already analyzed (thanks!) and pointed to as BLOCKERs.
Regards,
Abhinav
We need to get netvirt under
control at this point. They have a lot of jobs,
and were never fully healthy but without maintenance
they are going to create
a lot of work every release cycle.
I spent some time today going through our sodium sr1
failures and made progress
on the sheet:
https://docs.google.com/spreadsheets/d/1CN-ACdIekRKMYRIuREIRALl6S8az7quAcQlRb3KeMJ8/edit?pli=1#gid=1864238939
there are three jobs with a basic netvirt failure that
was ignored in
the original sodium release (openstack instance not
getting an ip address)
which seems like a fundamental failure. The original
sodium release let
it through under the assumption that it was a test code
problem. I don't
think it is. I marked those as BLOCKER.
Should we mark the DCGW jobs as ignore? I don't have
time to debug them
and they are saw-tooth failures and inconsistent. No
idea if they are
regressions or not.
beyond netvirt, I'm following up on one openflowplugin
job and once those
are understood we will only be left with netvirt to be
done.
Thanks,
JamO
On 10/21/19 11:41 PM, Abhinav Gupta
wrote:
Srinivas,
Please look into the CSIT jobs for failures. Please take
help from Karthika if required. I’m in parallel onboarding
myself with the overall Netvirt CSIT. Let’s discuss and get
this moving.
I see 20 CSIT jobs for NetVirt. We may want to eliminate the
unnecessary jobs as well.
Regards,
Abhinav
From: Daniel De La Rosa
<ddelarosa@...>
Sent: Tuesday, October 22, 2019 1:49 AM
To: JamO Luhrsen <jluhrsen@...>;
Abhinav Gupta
<abhinav.gupta@...>
Cc: Release <release@...>;
tsc@...;
integration-dev@...;
netvirt-dev@...; Bgpcep-Dev
<bgpcep-dev@...>;
controller-dev@...;
lispflowmapping-dev@...;
netconf-dev@...;
openflowplugin-dev@...
Subject: Re: [integration-dev] Sodium SR1 release
candidate
Team,
Friendly reminder to review Sodium
SR1 tracking sheet so we can release it on time.
--
Daniel
de la Rosa
Customer Support Manager ( ODL release manager )
Lumina Networks Inc.
e: ddelarosa@...
m: +1 408 7728120
|
|
|
Daniel de la Rosa
Team. Any updates on this?
On Thu, Oct 24, 2019 at 8:20 AM Jamo Luhrsen < jluhrsen@...> wrote:
On 10/24/19 4:21 AM, Abhinav Gupta
wrote:
@Srinivas,
@R
M Mishra: Please focus on the 3 rows JamO has
already analyzed (thanks!) and pointed to as BLOCKERs.
Regards,
Abhinav
We need to get netvirt under
control at this point. They have a lot of jobs,
and were never fully healthy but without maintenance
they are going to create
a lot of work every release cycle.
I spent some time today going through our sodium sr1
failures and made progress
on the sheet:
https://docs.google.com/spreadsheets/d/1CN-ACdIekRKMYRIuREIRALl6S8az7quAcQlRb3KeMJ8/edit?pli=1#gid=1864238939
there are three jobs with a basic netvirt failure that
was ignored in
the original sodium release (openstack instance not
getting an ip address)
which seems like a fundamental failure. The original
sodium release let
it through under the assumption that it was a test code
problem. I don't
think it is. I marked those as BLOCKER.
Should we mark the DCGW jobs as ignore? I don't have
time to debug them
and they are saw-tooth failures and inconsistent. No
idea if they are
regressions or not.
beyond netvirt, I'm following up on one openflowplugin
job and once those
are understood we will only be left with netvirt to be
done.
Thanks,
JamO
On 10/21/19 11:41 PM, Abhinav Gupta
wrote:
Srinivas,
Please look into the CSIT jobs for failures. Please take
help from Karthika if required. I’m in parallel onboarding
myself with the overall Netvirt CSIT. Let’s discuss and get
this moving.
I see 20 CSIT jobs for NetVirt. We may want to eliminate the
unnecessary jobs as well.
Regards,
Abhinav
From: Daniel De La Rosa
<ddelarosa@...>
Sent: Tuesday, October 22, 2019 1:49 AM
To: JamO Luhrsen <jluhrsen@...>;
Abhinav Gupta
<abhinav.gupta@...>
Cc: Release <release@...>;
tsc@...;
integration-dev@...;
netvirt-dev@...; Bgpcep-Dev
<bgpcep-dev@...>;
controller-dev@...;
lispflowmapping-dev@...;
netconf-dev@...;
openflowplugin-dev@...
Subject: Re: [integration-dev] Sodium SR1 release
candidate
Team,
Friendly reminder to review Sodium
SR1 tracking sheet so we can release it on time.
--
Daniel
de la Rosa
Customer Support Manager ( ODL release manager )
Lumina Networks Inc.
e: ddelarosa@...
m: +1 408 7728120
-- Daniel de la Rosa Customer Support Manager Lumina Networks Inc. e: ddelarosa@...m: +1 408 7728120
|
|
|
Do we want to block the release because of new exceptions
coming? We need
someone to see if those exceptions are an indication of some
regression
in functionality between the first sodium release and this SR1
candidate.
Also, we still need someone to look at the other 3 jobs I marked
as blockers
because those do look like a netvirt functionality breakage. I
just don't
know if the same problem was there in the original sodium release
or not.
Thanks,
JamO
toggle quoted message
Show quoted text
Hi
Daniel/Jamo,
I
have raised the JIRA bug:
https://jira.opendaylight.org/browse/NETVIRT-1634:
Exceptions seen
during deletion of BGP RD
Also
updated the same in the spreadsheet as blocker as
its continuously failing with the same exceptions.
Thanks,
Srinivas
+91-9243478719
From: Daniel De La Rosa
<ddelarosa@...>
Sent: 26 October 2019 02:49
To: Jamo Luhrsen <jluhrsen@...>
Cc: Abhinav Gupta <abhinav.gupta@...>;
R M Mishra <r.m.mishra@...>; Srinivas
Rachakonda <srinivas.rachakonda@...>;
TSC@...
Subject: Re: [OpenDaylight TSC] [integration-dev]
Sodium SR1 release candidate
Team. Any updates on this?
On Thu, Oct 24, 2019 at 8:20 AM Jamo
Luhrsen <jluhrsen@...>
wrote:
On 10/24/19 4:21 AM, Abhinav
Gupta wrote:
@Srinivas,
@R M Mishra:
Please focus on the 3 rows JamO has already
analyzed (thanks!) and pointed to as BLOCKERs.
Regards,
Abhinav
We need to get
netvirt under control at this point. They have
a lot of jobs,
and were never
fully healthy but without maintenance they are
going to create
a lot of work
every release cycle.
I spent some
time today going through our sodium sr1
failures and made progress
on the sheet:
https://docs.google.com/spreadsheets/d/1CN-ACdIekRKMYRIuREIRALl6S8az7quAcQlRb3KeMJ8/edit?pli=1#gid=1864238939
there are three
jobs with a basic netvirt failure that was
ignored in
the original
sodium release (openstack instance not getting
an ip address)
which seems
like a fundamental failure. The original
sodium release let
it through
under the assumption that it was a test code
problem. I don't
think it is. I
marked those as BLOCKER.
Should we mark
the DCGW jobs as ignore? I don't have time to
debug them
and they are
saw-tooth failures and inconsistent. No idea
if they are
regressions or
not.
beyond netvirt,
I'm following up on one openflowplugin job and
once those
are understood
we will only be left with netvirt to be done.
Thanks,
JamO
On
10/21/19 11:41 PM, Abhinav Gupta wrote:
Srinivas,
Please look into the CSIT jobs for failures.
Please take help from Karthika if required. I’m
in parallel onboarding myself with the overall
Netvirt CSIT. Let’s discuss and get this moving.
I see 20 CSIT jobs for NetVirt. We may want to
eliminate the unnecessary jobs as well.
Regards,
Abhinav
From:
Daniel De La Rosa <ddelarosa@...>
Sent: Tuesday, October 22, 2019 1:49 AM
To: JamO Luhrsen <jluhrsen@...>;
Abhinav Gupta <abhinav.gupta@...>
Cc: Release <release@...>;
tsc@...;
integration-dev@...;
netvirt-dev@...;
Bgpcep-Dev <bgpcep-dev@...>;
controller-dev@...;
lispflowmapping-dev@...;
netconf-dev@...;
openflowplugin-dev@...
Subject: Re: [integration-dev] Sodium SR1
release candidate
Team,
Friendly
reminder to review Sodium SR1
tracking sheet so we can release it on
time.
--
Daniel
de la Rosa
Customer Support Manager ( ODL
release manager )
Lumina Networks Inc.
e: ddelarosa@...
m: +1 408 7728120
--
Daniel de la Rosa
Customer Support Manager
Lumina Networks Inc.
e: ddelarosa@...
m: +1 408 7728120
|
|
|
Daniel de la Rosa
toggle quoted message
Show quoted text
On Mon, Oct 28, 2019 at 10:43 AM Jamo Luhrsen < jluhrsen@...> wrote:
Do we want to block the release because of new exceptions
coming? We need
someone to see if those exceptions are an indication of some
regression
in functionality between the first sodium release and this SR1
candidate.
Also, we still need someone to look at the other 3 jobs I marked
as blockers
because those do look like a netvirt functionality breakage. I
just don't
know if the same problem was there in the original sodium release
or not.
Thanks,
JamO
Hi
Daniel/Jamo,
I
have raised the JIRA bug:
https://jira.opendaylight.org/browse/NETVIRT-1634:
Exceptions seen
during deletion of BGP RD
Also
updated the same in the spreadsheet as blocker as
its continuously failing with the same exceptions.
Thanks,
Srinivas
+91-9243478719
From: Daniel De La Rosa
<ddelarosa@...>
Sent: 26 October 2019 02:49
To: Jamo Luhrsen <jluhrsen@...>
Cc: Abhinav Gupta <abhinav.gupta@...>;
R M Mishra <r.m.mishra@...>; Srinivas
Rachakonda <srinivas.rachakonda@...>;
TSC@...
Subject: Re: [OpenDaylight TSC] [integration-dev]
Sodium SR1 release candidate
Team. Any updates on this?
On Thu, Oct 24, 2019 at 8:20 AM Jamo
Luhrsen <jluhrsen@...>
wrote:
On 10/24/19 4:21 AM, Abhinav
Gupta wrote:
@Srinivas,
@R M Mishra:
Please focus on the 3 rows JamO has already
analyzed (thanks!) and pointed to as BLOCKERs.
Regards,
Abhinav
We need to get
netvirt under control at this point. They have
a lot of jobs,
and were never
fully healthy but without maintenance they are
going to create
a lot of work
every release cycle.
I spent some
time today going through our sodium sr1
failures and made progress
on the sheet:
https://docs.google.com/spreadsheets/d/1CN-ACdIekRKMYRIuREIRALl6S8az7quAcQlRb3KeMJ8/edit?pli=1#gid=1864238939
there are three
jobs with a basic netvirt failure that was
ignored in
the original
sodium release (openstack instance not getting
an ip address)
which seems
like a fundamental failure. The original
sodium release let
it through
under the assumption that it was a test code
problem. I don't
think it is. I
marked those as BLOCKER.
Should we mark
the DCGW jobs as ignore? I don't have time to
debug them
and they are
saw-tooth failures and inconsistent. No idea
if they are
regressions or
not.
beyond netvirt,
I'm following up on one openflowplugin job and
once those
are understood
we will only be left with netvirt to be done.
Thanks,
JamO
On
10/21/19 11:41 PM, Abhinav Gupta wrote:
Srinivas,
Please look into the CSIT jobs for failures.
Please take help from Karthika if required. I’m
in parallel onboarding myself with the overall
Netvirt CSIT. Let’s discuss and get this moving.
I see 20 CSIT jobs for NetVirt. We may want to
eliminate the unnecessary jobs as well.
Regards,
Abhinav
From:
Daniel De La Rosa <ddelarosa@...>
Sent: Tuesday, October 22, 2019 1:49 AM
To: JamO Luhrsen <jluhrsen@...>;
Abhinav Gupta <abhinav.gupta@...>
Cc: Release <release@...>;
tsc@...;
integration-dev@...;
netvirt-dev@...;
Bgpcep-Dev <bgpcep-dev@...>;
controller-dev@...;
lispflowmapping-dev@...;
netconf-dev@...;
openflowplugin-dev@...
Subject: Re: [integration-dev] Sodium SR1
release candidate
Team,
Friendly
reminder to review Sodium SR1
tracking sheet so we can release it on
time.
--
Daniel
de la Rosa
Customer Support Manager ( ODL
release manager )
Lumina Networks Inc.
e: ddelarosa@...
m: +1 408 7728120
--
Daniel de la Rosa
Customer Support Manager
Lumina Networks Inc.
e: ddelarosa@...
m: +1 408 7728120
-- Daniel de la Rosa
Customer Support Manager
Lumina Networks Inc.
e: ddelarosa@...
m: +1 408 7728120
|
|
|
Hi Daniel/Jamo, I have raised the JIRA bug: https://jira.opendaylight.org/browse/NETVIRT-1634: Exceptions seen during deletion of BGP RD Also updated the same in the spreadsheet as blocker as its continuously failing with the same exceptions. Thanks, Srinivas +91-9243478719
From: Daniel De La Rosa <ddelarosa@...>
Sent: 26 October 2019 02:49
To: Jamo Luhrsen <jluhrsen@...>
Cc: Abhinav Gupta <abhinav.gupta@...>; R M Mishra <r.m.mishra@...>; Srinivas Rachakonda <srinivas.rachakonda@...>; TSC@...
Subject: Re: [OpenDaylight TSC] [integration-dev] Sodium SR1 release candidate Team. Any updates on this? On Thu, Oct 24, 2019 at 8:20 AM Jamo Luhrsen <jluhrsen@...> wrote: On 10/24/19 4:21 AM, Abhinav Gupta wrote: @Srinivas, @R M Mishra: Please focus on the 3 rows JamO has already analyzed (thanks!) and pointed to as BLOCKERs.
Regards,
Abhinav We need to get netvirt under control at this point. They have a lot of jobs,
and were never fully healthy but without maintenance they are going to create
a lot of work every release cycle.
I spent some time today going through our sodium sr1 failures and made progress
on the sheet:
https://docs.google.com/spreadsheets/d/1CN-ACdIekRKMYRIuREIRALl6S8az7quAcQlRb3KeMJ8/edit?pli=1#gid=1864238939
there are three jobs with a basic netvirt failure that was ignored in
the original sodium release (openstack instance not getting an ip address)
which seems like a fundamental failure. The original sodium release let
it through under the assumption that it was a test code problem. I don't
think it is. I marked those as BLOCKER.
Should we mark the DCGW jobs as ignore? I don't have time to debug them
and they are saw-tooth failures and inconsistent. No idea if they are
regressions or not.
beyond netvirt, I'm following up on one openflowplugin job and once those
are understood we will only be left with netvirt to be done.
Thanks,
JamO On 10/21/19 11:41 PM, Abhinav Gupta wrote: Srinivas,
Please look into the CSIT jobs for failures. Please take help from Karthika if required. I’m in parallel onboarding myself with the overall Netvirt CSIT. Let’s discuss and get this moving.
I see 20 CSIT jobs for NetVirt. We may want to eliminate the unnecessary jobs as well. Regards,
Abhinav From: Daniel De La Rosa <ddelarosa@...>
Sent: Tuesday, October 22, 2019 1:49 AM
To: JamO Luhrsen <jluhrsen@...>; Abhinav Gupta <abhinav.gupta@...>
Cc: Release <release@...>; tsc@...; integration-dev@...; netvirt-dev@...; Bgpcep-Dev <bgpcep-dev@...>; controller-dev@...; lispflowmapping-dev@...; netconf-dev@...; openflowplugin-dev@...
Subject: Re: [integration-dev] Sodium SR1 release candidate Team, Friendly reminder to review Sodium SR1 tracking sheet so we can release it on time.
-- Daniel de la Rosa
Customer Support Manager ( ODL release manager )
Lumina Networks Inc.
e: ddelarosa@...
m: +1 408 7728120
-- Daniel de la Rosa
Customer Support Manager
Lumina Networks Inc.
e: ddelarosa@...
m: +1 408 7728120
|
|
|
toggle quoted message
Show quoted text
From: Daniel De La Rosa <ddelarosa@...>
Sent: 28 October 2019 23:25
To: Jamo Luhrsen <jluhrsen@...>; netvirt-dev@...
Cc: Srinivas Rachakonda <srinivas.rachakonda@...>; Abhinav Gupta <abhinav.gupta@...>; R M Mishra <r.m.mishra@...>; <tsc@...> <TSC@...>
Subject: Re: [OpenDaylight TSC] [integration-dev] Sodium SR1 release candidate On Mon, Oct 28, 2019 at 10:43 AM Jamo Luhrsen <jluhrsen@...> wrote: Do we want to block the release because of new exceptions coming? We need
someone to see if those exceptions are an indication of some regression
in functionality between the first sodium release and this SR1 candidate.
Also, we still need someone to look at the other 3 jobs I marked as blockers
because those do look like a netvirt functionality breakage. I just don't
know if the same problem was there in the original sodium release or not.
Thanks,
JamO Hi Daniel/Jamo, I have raised the JIRA bug: https://jira.opendaylight.org/browse/NETVIRT-1634: Exceptions seen during deletion of BGP RD Also updated the same in the spreadsheet as blocker as its continuously failing with the same exceptions. Thanks, Srinivas +91-9243478719 From: Daniel De La Rosa <ddelarosa@...>
Sent: 26 October 2019 02:49
To: Jamo Luhrsen <jluhrsen@...>
Cc: Abhinav Gupta <abhinav.gupta@...>; R M Mishra <r.m.mishra@...>; Srinivas Rachakonda <srinivas.rachakonda@...>; TSC@...
Subject: Re: [OpenDaylight TSC] [integration-dev] Sodium SR1 release candidate Team. Any updates on this? On Thu, Oct 24, 2019 at 8:20 AM Jamo Luhrsen <jluhrsen@...> wrote: On 10/24/19 4:21 AM, Abhinav Gupta wrote: @Srinivas, @R M Mishra: Please focus on the 3 rows JamO has already analyzed (thanks!) and pointed to as BLOCKERs.
Regards,
Abhinav We need to get netvirt under control at this point. They have a lot of jobs,
and were never fully healthy but without maintenance they are going to create
a lot of work every release cycle.
I spent some time today going through our sodium sr1 failures and made progress
on the sheet:
https://docs.google.com/spreadsheets/d/1CN-ACdIekRKMYRIuREIRALl6S8az7quAcQlRb3KeMJ8/edit?pli=1#gid=1864238939
there are three jobs with a basic netvirt failure that was ignored in
the original sodium release (openstack instance not getting an ip address)
which seems like a fundamental failure. The original sodium release let
it through under the assumption that it was a test code problem. I don't
think it is. I marked those as BLOCKER.
Should we mark the DCGW jobs as ignore? I don't have time to debug them
and they are saw-tooth failures and inconsistent. No idea if they are
regressions or not.
beyond netvirt, I'm following up on one openflowplugin job and once those
are understood we will only be left with netvirt to be done.
Thanks,
JamO On 10/21/19 11:41 PM, Abhinav Gupta wrote: Srinivas,
Please look into the CSIT jobs for failures. Please take help from Karthika if required. I’m in parallel onboarding myself with the overall Netvirt CSIT. Let’s discuss and get this moving.
I see 20 CSIT jobs for NetVirt. We may want to eliminate the unnecessary jobs as well. Regards,
Abhinav From: Daniel De La Rosa <ddelarosa@...>
Sent: Tuesday, October 22, 2019 1:49 AM
To: JamO Luhrsen <jluhrsen@...>; Abhinav Gupta <abhinav.gupta@...>
Cc: Release <release@...>; tsc@...; integration-dev@...; netvirt-dev@...; Bgpcep-Dev <bgpcep-dev@...>; controller-dev@...; lispflowmapping-dev@...; netconf-dev@...; openflowplugin-dev@...
Subject: Re: [integration-dev] Sodium SR1 release candidate Team, Friendly reminder to review Sodium SR1 tracking sheet so we can release it on time.
-- Daniel de la Rosa
Customer Support Manager ( ODL release manager )
Lumina Networks Inc.
e: ddelarosa@...
m: +1 408 7728120
-- Daniel de la Rosa
Customer Support Manager
Lumina Networks Inc.
e: ddelarosa@...
m: +1 408 7728120
-- Daniel de la Rosa
Customer Support Manager
Lumina Networks Inc.
e: ddelarosa@...
m: +1 408 7728120
|
|
|
Daniel de la Rosa
Let me add +<tsc@...> since we need to make a decision on whether to keep holding Sodium SR1 or to move forward with all these issues documented in the release notes
On Tue, Oct 29, 2019 at 10:05 AM Jamo Luhrsen < jluhrsen@...> wrote:
Hey guys,
at this point, blocker bugs are "blocking" an already late
release.
We need to get them resolved asap.
1) are they true regressions and issues that did not exist with
the
original Sodium release?
2) ignoring 1) above, are the bugs truly "blocker" in nature in
that
the netvirt functionality is broken and cannot be used?
Thanks,
JamO
On 10/29/19 12:02 AM, Jaya
Priyadarshini wrote:
Hi
Abhinav/Srinivas,
The above 3
jobs when run witj 0cmb-1ctl-2cmp cases have 100% pass
result and have 2 failures with 1cmb-0ctl-0cmb cases.
Not test
code issue but odl code issue.
Can anyone
have a look?
Regards
Jaya
We need to get netvirt under
control at this point. They have a lot of jobs,
and were never fully healthy but without maintenance
they are going to create
a lot of work every release cycle.
I spent some time today going through our sodium sr1
failures and made progress
on the sheet:
https://docs.google.com/spreadsheets/d/1CN-ACdIekRKMYRIuREIRALl6S8az7quAcQlRb3KeMJ8/edit?pli=1#gid=1864238939
there are three jobs with a basic netvirt failure that
was ignored in
the original sodium release (openstack instance not
getting an ip address)
which seems like a fundamental failure. The original
sodium release let
it through under the assumption that it was a test code
problem. I don't
think it is. I marked those as BLOCKER.
Should we mark the DCGW jobs as ignore? I don't have
time to debug them
and they are saw-tooth failures and inconsistent. No
idea if they are
regressions or not.
beyond netvirt, I'm following up on one openflowplugin
job and once those
are understood we will only be left with netvirt to be
done.
Thanks,
JamO
On 10/21/19 11:41 PM, Abhinav Gupta
wrote:
Srinivas,
Please look into the CSIT jobs for failures. Please take
help from Karthika if required. I’m in parallel onboarding
myself with the overall Netvirt CSIT. Let’s discuss and get
this moving.
I see 20 CSIT jobs for NetVirt. We may want to eliminate the
unnecessary jobs as well.
Regards,
Abhinav
From: Daniel De La Rosa
<ddelarosa@...>
Sent: Tuesday, October 22, 2019 1:49 AM
To: JamO Luhrsen <jluhrsen@...>;
Abhinav Gupta
<abhinav.gupta@...>
Cc: Release <release@...>;
tsc@...;
integration-dev@...;
netvirt-dev@...; Bgpcep-Dev
<bgpcep-dev@...>;
controller-dev@...;
lispflowmapping-dev@...;
netconf-dev@...;
openflowplugin-dev@...
Subject: Re: [integration-dev] Sodium SR1 release
candidate
Team,
Friendly reminder to review Sodium
SR1 tracking sheet so we can release it on time.
--
Daniel
de la Rosa
Customer Support Manager ( ODL release manager )
Lumina Networks Inc.
e: ddelarosa@...
m: +1 408 7728120
-- Daniel de la Rosa
Customer Support Manager
Lumina Networks Inc.
e: ddelarosa@...
m: +1 408 7728120
|
|
|
