1. TSC
  2. Messages

Re: Transitioning Controller to being MRI

Faseela K <k.faseela@...>
 

Robert,

   While I see that you have done almost all work needed for the transition, including the consumer projects, do we have to consider any breakage window when these are getting merged, as we are trying to estimate for the other task for migrating from controller APIs? Both the activities have to be done at the same window, and hence the question.


On Thu, 26 Mar 2020 at 22:34, Robert Varga <nite@...> wrote:
On 25/03/2020 23:25, Robert Varga wrote:
> Hello everyone,

Hello again,

> The process involves three steps:
>
> 1) transition all of controller's downstreams to use Magnesium version
> of controller artifacts
> 2) remove controller from autorelease
> 3) remove controller's distcheck jobs
> 4) perform a normal MRI bump during the Aluminium MRI Integration Window
>
> I have staged the patches for 1 through 3 here:
> https://git.opendaylight.org/gerrit/q/topic:"controller-mri"
>
> Multipatch-test is running here:
> https://jenkins.opendaylight.org/releng/view/integration/job/integration-multipatch-test-aluminium/1
>
> Once that job succeeds, I will be asking for supercommitter rights to
> get those patches merged, after which controller's master will become
> disconnected from MSI projects participating in Aluminium SimRel.

This has been discussed at today's TSC call and approved. I have raised
the ticket for the rights to merge up the patches.

I plan to execute this tomorrow morning CET and the disruption should be
pretty much the same as for any MRI bump -- so around 6 hours, perhaps
less now that it involves fewer projects.

If you have objects, please yell now.

Thanks,
Robert




--
Faseela.K
Cisco, Bengaluru
MEC 2k10
Join TSC@lists.opendaylight.org to automatically receive all group messages.