Set up and migrate to the new server

Registered by Данило Шеган

We want to migrate the to a new server hosted by Linaro (in ec2 most likely, but Philip Colmer has a final say on that).
We should use RhodeCode as the web interface, and make sure we can easily update the code.

We need to migrate all the private repositories and users as well, and a structure needs to be planned for this.

Blueprint information

Alan Bennett
Milo Casagrande
Georgy Redkozubov
Series goal:
Accepted for trunk
Milestone target:
milestone icon 2013.05
Started by
Milo Casagrande
Completed by
Milo Casagrande

Related branches



Headline: Migrate to a rhodecode-based server hosted by Linaro.
Acceptance: There is a new server to take over from Canonical-hosted and all automated jobs have been migrated to it. As much compatibility (like URLs) should be preserved.
Roadmap id: CARD-148

[danilo, 2013-01-16] Gesha's deployment notes:
[danilo, 2013-01-23] Make sure we use SSH keys for authorization.
[danilo, 2013-02-12] We won't get to this before Connect, post-pone.
[milo, 2013-03-12] Started discussion with Philip on setting up new EC2 instance for migration.
[gesha, 2013-04-26] Implementation of this BP was blocked by bug 1167379
[milo, 2013-04-29] Creating new thread with Philip and gesha to launch a new instance for the migration.
[gesha, 2013-04-30] Tested updates to http-alternates on staging server
[gesha, 2013-05-29] More likely there will not be new server for and current will be switched to the production when all issues will be resolved.


Work Items

Work items:
[milo] Start discussion with Philip about preparing EC2 instance for migration: DONE
[milo] Create new large EC2 instance for new production git server: DONE
Instsall Rhodecode on new EC2 instance: DONE
Setup SSL sertificates on new EC2 instance: DONE
Setup LDAP, create (sync) users/groups: DONE
Clone (rsync) repositories from existing DONE
Enable dumb HTTP protocol to be used by default: DONE
Update repositories to latest state from existing TODO
Stop existing and sync latest data to the new server: TODO
Update http-alternates for repositories: DONE
Switch DNS to use new server as TODO

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.


No subscribers.