|
Magnesium CSIT check for SR3
All the reds here: https://jenkins.opendaylight.org/releng/job/integration-distribution-test-magnesium/451/ are infra failure: 03:48:16 WARN: Failed to initialize stack. Reason: Resource CREATE failed
All the reds here: https://jenkins.opendaylight.org/releng/job/integration-distribution-test-magnesium/451/ are infra failure: 03:48:16 WARN: Failed to initialize stack. Reason: Resource CREATE failed
|
By
Luis Gomez
· #13349
·
|
|
[release] Aluminium Release Notes
Can we just merge this for the time being? https://git.opendaylight.org/gerrit/c/docs/+/93572 BR/Luis
Can we just merge this for the time being? https://git.opendaylight.org/gerrit/c/docs/+/93572 BR/Luis
|
By
Luis Gomez
· #13326
·
|
|
CSIT jobs failing
FYI the issue should be fixed now, let me know if otherwise.
FYI the issue should be fixed now, let me know if otherwise.
|
By
Luis Gomez
· #13305
·
|
|
CSIT jobs failing
FYI, CSIT jobs are failing since Oct 9th https://jenkins.opendaylight.org/releng/view/openflowplugin/job/openflowplugin-csit-3node-clustering-only-aluminium/ The reason seems to be some VM quota: 02:5
FYI, CSIT jobs are failing since Oct 9th https://jenkins.opendaylight.org/releng/view/openflowplugin/job/openflowplugin-csit-3node-clustering-only-aluminium/ The reason seems to be some VM quota: 02:5
|
By
Luis Gomez
· #13304
·
|
|
[release] [app-dev] Silicon MRI Version Bump happening now
FYI, here are the patches to move netvirt project to SM: https://git.opendaylight.org/gerrit/q/topic:netvirt-sm We might need to expedite these patches if netvirt project keeps blocking the distributi
FYI, here are the patches to move netvirt project to SM: https://git.opendaylight.org/gerrit/q/topic:netvirt-sm We might need to expedite these patches if netvirt project keeps blocking the distributi
|
By
Luis Gomez
· #13284
·
|
|
Governance Discussion
I do not have objections to this proposal. Also starting the first elections right away seems better than waiting.
I do not have objections to this proposal. Also starting the first elections right away seems better than waiting.
|
By
Luis Gomez
· #13282
·
|
|
Governance Discussion
Fair enough, what if we just start an "open" thread before the official nomination period to see who has intention to self-nominate? although this is not final, it can give us a faster feedback than w
Fair enough, what if we just start an "open" thread before the official nomination period to see who has intention to self-nominate? although this is not final, it can give us a faster feedback than w
|
By
Luis Gomez
· #13277
·
|
|
Governance Discussion
I thought from previous conversation we could reach 5 seats easily (e.g. Robert, Guillaume, Rangan, Anil and myself), but if not, lets go for 3. BR/Luis
I thought from previous conversation we could reach 5 seats easily (e.g. Robert, Guillaume, Rangan, Anil and myself), but if not, lets go for 3. BR/Luis
|
By
Luis Gomez
· #13275
·
|
|
Governance Discussion
Please continue the governance discussion here so we can reach concrete proposals for TSC vote. I personally do not see difference between "5 seats now + 2 seats later" vs "5 seats now and new TSC wil
Please continue the governance discussion here so we can reach concrete proposals for TSC vote. I personally do not see difference between "5 seats now + 2 seats later" vs "5 seats now and new TSC wil
|
By
Luis Gomez
· #13273
·
|
|
[release] ODL release model
I think this could be done just before a release milestone (e.g. for a RC) but difficult to achieve in a continuous way like in AR today, specially when projects will have freedom for updating their u
I think this could be done just before a release milestone (e.g. for a RC) but difficult to achieve in a continuous way like in AR today, specially when projects will have freedom for updating their u
|
By
Luis Gomez
· #13242
·
|
|
[release] ODL release model
I also do not think TSC can obligate a project to release but I think we have to set some rules for functioning together, for example Platform projects should define a set of release versions for Plug
I also do not think TSC can obligate a project to release but I think we have to set some rules for functioning together, for example Platform projects should define a set of release versions for Plug
|
By
Luis Gomez
· #13240
·
|
|
ODL release model
Hi all, I personally found very interesting the ODL release model conversation we held in DDF. In particular I would like to see if the current project classification and release model: MRI, MSI, SM c
Hi all, I personally found very interesting the ODL release model conversation we held in DDF. In particular I would like to see if the current project classification and release model: MRI, MSI, SM c
|
By
Luis Gomez
· #13238
·
|
|
Governance Discussion
+1, the simpler, the better.
+1, the simpler, the better.
|
By
Luis Gomez
· #13229
·
|
|
[app-dev] [release] ODL Silicon release - Neutron Northbound plans
The way things work in ODL, it is not possible to have a Managed project depending on an SM project. So if lispflowmapping project wants to continue as Managed project, it should either: - Remove neut
The way things work in ODL, it is not possible to have a Managed project depending on an SM project. So if lispflowmapping project wants to continue as Managed project, it should either: - Remove neut
|
By
Luis Gomez
· #13200
·
|
|
[release] Aluminium Release Notes
Thanh, Anil, couple of things: - I see lot of issues with the docs linkcheck (multiple rechecks required to pass a build), would it be possible to relax or maybe remove this check? - Can we switch the
Thanh, Anil, couple of things: - I see lot of issues with the docs linkcheck (multiple rechecks required to pass a build), would it be possible to relax or maybe remove this check? - Can we switch the
|
By
Luis Gomez
· #13189
·
|
|
[ODL Discuss] Invitation: ODL TSC US/Pacific Meeting @ Every 2 weeks from 09:00 to 10:00 on Thursday (PDT) (discuss@...)
Casey, I do not see an invite for IST friendly bi-weekly meetings. If these require passcode, please send invite for these too.
Casey, I do not see an invite for IST friendly bi-weekly meetings. If these require passcode, please send invite for these too.
|
By
Luis Gomez
· #13183
·
|
|
[app-dev] [release][OpenDaylight TSC] OpenDaylight Aluminum Status
Fine with me.
By
Luis Gomez
· #13182
·
|
|
[app-dev] [release][OpenDaylight TSC] OpenDaylight Aluminum Status
Thanks Brandon, I just recalled Lumina used ODL based controller in this interop effort: http://www.eantc.de/fileadmin/eantc/downloads/events/MPLS2020/EANTC-MPLSSDNNFV2020-WhitePaper.pdf (it is also m
Thanks Brandon, I just recalled Lumina used ODL based controller in this interop effort: http://www.eantc.de/fileadmin/eantc/downloads/events/MPLS2020/EANTC-MPLSSDNNFV2020-WhitePaper.pdf (it is also m
|
By
Luis Gomez
· #13180
·
|
|
[app-dev] [release][OpenDaylight TSC] OpenDaylight Aluminum Status
Tejas/Prem/Allan, any plan to release odlmicro/odlsaf/plastic for Aluminum release? If so we could add some messaging in the Aluminum press release. FYI, to release an SM project you normally have to
Tejas/Prem/Allan, any plan to release odlmicro/odlsaf/plastic for Aluminum release? If so we could add some messaging in the Aluminum press release. FYI, to release an SM project you normally have to
|
By
Luis Gomez
· #13164
·
|
|
[release][OpenDaylight TSC] OpenDaylight Aluminum Status
I do not see anyone else joining the common karaf distribution so I went ahead and released it: https://nexus.opendaylight.org/content/repositories/opendaylight.release/org/opendaylight/integration/op
I do not see anyone else joining the common karaf distribution so I went ahead and released it: https://nexus.opendaylight.org/content/repositories/opendaylight.release/org/opendaylight/integration/op
|
By
Luis Gomez
· #13163
·
|