Regarding Gerrit server migration from physical machine to AWS EC2-version 2.14.5

[Kushal Chaudhary]

Hello Everyone,

I am a new member of this group and new to Gerrit too.May I request some assistance from you on the below mentioned scenario-->

We have a TeamForge server(TF 17.11.455) which is connected to 14 Gerrit instances.The TeamForge is an application server having its own DB hosted on the same server as TF.
The Gerrit is at 2.14.5.1-101. The Gerrit server is making use of Postgressql and ReviewDB which is stored on the same server as each Gerrit server.
The authentication is handled by MS Active Directory via the Teamforge server and not the Gerrit Server.
Out of these 14 instances there are only a couple of instances(may be 2-3) which are containing the XYZ project repos along with some other project Repos.
These Gerrit servers(especially the ones for XYZ project) are rarely used and there are very less number of users involved.


We plan to migrate to another brand new Gerrit Server(only a single server hosted on AWS EC2 instance)which will be containing only the XYZ project repos.Everything will be kept at the same version as before.The only purpose of such a migration task is because the team wants to have access to the historic code reviews and comments.

So below are some queries that I have:

1) Do I need to compulsorily install Teamforge server in AWS and hook it up to the new Gerrit server(dedicated to XYZ project repos)so that all the users/groups are available to this new Gerrit server via the TEAMForge authentication which is done via MS Active Directory or can this new Gerrit server be directlt connected to the MS AD without the use of TeamForge?

2) Will the importer plugin takecare of the repository movement(along with code review and commits data) from existing Gerrit to the brand new Gerrit server without having the new Gerrit server connected to the LDAP server?


Kindly provide your expert opinion on this which will help me move ahead on this.


Thanks & Regards,
Kushal Chaudhary 

[Matthias Sohn]

On Thu, Jul 28, 2022 at 8:11 PM Kushal Chaudhary <meetkush...@gmail.com> wrote:

Hello Everyone,

I am a new member of this group and new to Gerrit too.May I request some assistance from you on the below mentioned scenario-->

We have a TeamForge server(TF 17.11.455) which is connected to 14 Gerrit instances.The TeamForge is an application server having its own DB hosted on the same server as TF.
The Gerrit is at 2.14.5.1-101. The Gerrit server is making use of Postgressql and ReviewDB which is stored on the same server as each Gerrit server.

AFAIK TeamForge is a commercial product. Contact the vendor for support.

If you want to use the open source version of Gerrit you should consider upgrading to a supported version 3.4.5 or higher.

The open source Gerrit 2.14 is EOL from May 2019. See https://www.gerritcodereview.com/support.html

 

The authentication is handled by MS Active Directory via the Teamforge server and not the Gerrit Server.
Out of these 14 instances there are only a couple of instances(may be 2-3) which are containing the XYZ project repos along with some other project Repos.
These Gerrit servers(especially the ones for XYZ project) are rarely used and there are very less number of users involved.


We plan to migrate to another brand new Gerrit Server(only a single server hosted on AWS EC2 instance)which will be containing only the XYZ project repos.Everything will be kept at the same version as before.The only purpose of such a migration task is because the team wants to have access to the historic code reviews and comments.

So below are some queries that I have:

1) Do I need to compulsorily install Teamforge server in AWS and hook it up to the new Gerrit server(dedicated to XYZ project repos)so that all the users/groups are available to this new Gerrit server via the TEAMForge authentication which is done via MS Active Directory or can this new Gerrit server be directlt connected to the MS AD without the use of TeamForge? 

2) Will the importer plugin takecare of the repository movement(along with code review and commits data) from existing Gerrit to the brand new Gerrit server without having the new Gerrit server connected to the LDAP server?


Kindly provide your expert opinion on this which will help me move ahead on this.


Thanks & Regards,
Kushal Chaudhary 

--
--
To unsubscribe, email repo-discuss...@googlegroups.com
More info at http://groups.google.com/group/repo-discuss?hl=en

---
You received this message because you are subscribed to the Google Groups "Repo and Gerrit Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to repo-discuss...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/repo-discuss/ccd8cec5-c93f-4b67-8dc9-7fc6c5695180n%40googlegroups.com.

[Kushal Chaudhary]

Hello Matthias,

Thanks for responding to my queries.

We are not considering migration to different version because this Gerrit server(v2.14) is going to be kept only because the dev teams wants to have access to the historical change reviews/comments and they are not planning to use it actively.
So basically its just moving the existing Gerrit to EC2 on AWS. May I have some guidance on this pls?