The migration is still in the early phases of being planned. As to if this actually helps with it, not directly. I'm in the early phases of figuring out how we're going to go about this but I do know the following:
1) A new Gerrit instance will have to be stood up that uses LFID as the backend 2) Projects will have to migrated from one Gerrit instance to the other, preferably using the importer plugin that became available in the last year 3) The importer plugin will copy over all changes (open, closed, abandoned - no idea about draft) from the old Gerrit to the new one, including creating the initial user information and most of their settings. The problem is in the rather unfortunate requirement to relink accounts. In some cases this is going to mean we need to actually change usernames in Gerrit if the persons LFID != their ODLID. Our issue lies in the fact that we currently have 5000+ user accounts in Gerrit, I'm pretty certain we don't have 5000+ active people. I strongly suspect that we have a lot of dead / dormant accounts related to long open changes. So, my intent with the auto-close is to have Gerrit clean-up a bunch of the open changes so that when we do start the migration then we're far more likely to be able to get a good idea of who we're going to have to talk to to get things reconnected and user names fixed where needed. Basically I'm trying to reduce the potential problem set as much as possible before we start the actual work as accounts that are part of relatively active changes are far more likely to be still connected to people that are active or likely reachable. -Andy- On 05/17/2017 12:50 PM, Colin Dixon wrote: > I'm not opposed to doing this, but does it help with migration in some > way I'm missing? > > --Colin > > > On Wed, May 17, 2017 at 3:11 PM, Andrew Grimberg > <[email protected] <mailto:[email protected]>> > wrote: > > Greetings folks, > > As I'm trying to figure out the logistics related to migrating ODL from > our current identity backend to The Linux Foundation Identity (LFID) > backend I've been investigating a lot of different things related to > Gerrit. One of the things I noticed is that we have a lot of changes > that are old and still open. > > We've got changes still open going all the way back to 2013! I would > like to put a proposal out that we auto-abandon changes that are >6 > months in age and in all honesty I would like to do it for any change > that is >6 weeks old but I figured that 6 months was a good starting > point. > > Please note that this is age of last activity, not age of initial change > or last patch update. So an old change that happens to have regular use > for some reason (such as trigger testing) via comments should not be > affected by this, even if they are, it's an abandon and not an actual > removal from the system so they won't disappear, they'll just be removed > from the status:open search. > > I'm proposing that this change happen after we finally get Carbon out > the door as it's going to require a restart to Gerrit to have the > configuration updated to start this. > > -Andy- > > -- > Andrew J Grimberg > Lead, IT Release Engineering > The Linux Foundation > > > _______________________________________________ > Discuss mailing list > [email protected] <mailto:[email protected]> > https://lists.opendaylight.org/mailman/listinfo/discuss > <https://lists.opendaylight.org/mailman/listinfo/discuss> > > -- Andrew J Grimberg Lead, IT Release Engineering The Linux Foundation
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Discuss mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/discuss
