Labs Eqiad Migration
Tools to use during migration (well, one tool at least) are documented here: Labs_Eqiad_Migration_Tools
Steps
- Set up 2nd openstack infra in labs Done
- Ensure OpenStackManager works properly with two zones Done
- Try the upstream OpenStack modules (Nope!)
- Investigate neutron (Nope!)
- Set up eqiad, using havana nova-network (Andrew)
- Set up keystone Done
- Set up glance, migrate images from pmtpa Done
- Set up nova services Done
- Update eqiad labs network config Done
- Set up /public/keys shared volume in eqiad nfs Done
- Create new eqiad bastion cluster
- Set up wikitech mediawiki mirror on virt1000
- Rewrite the instance wikistatus code to work with havana Done
- Test Done
- Migrate shared storage
- Make region-specific puppet changes so instances can move from tampa to eqiad Done
- Update OpenStackManager on wikitech to be aware of both datacenters Done
- Set up new service group schema to support nfs on eqiad Done
- Move some test instances from a project (begin week of 2014-01-27) (mostly Andrew): Done
- Creating test instances in pmtpa
- Creating instances with the same name in eqiad
- Shut down the instances in eqiad and pmtpa
- Transfer the images from pmtpa to eqiad
- Start the instances in eqiad and ensure a puppet run makes the system work properly
- Delete the instances in pmtpa
- Get deployment-prep and tools to start moving (begin week of 2014-02-03)
- Start moving projects, scheduling each one
Timeline
- 2012-02-21: Internal test migrations. Requires use of wikitech and virt1000.
- 2012-02-24: Tools, Deployment-prep migration begins (carefully). Wikitech exposes access to both datacenters.
- 2012-03-03: Public migration period begins. New instance creation and IP allocation disabled in pmtpa.
- 2012-03-18: Deadline for self-migration. After this, labs staff starts to shutdown and transfer remaining instances, where they will remain in SHUTOFF state until a specific request is made.
Relevant RT tickets
Relevant Bugzilla tickets
All open Labs related bugs in Bugzilla
Meeting notes and other pages
- Labs Eqiad Migration/2014-01-29
- Labs Eqiad Migration/2014-02-05
- Labs Eqiad Migration/2014-02-12
- Labs Eqiad Migration/2014-02-19
- Labs Eqiad Migration/2014-02-26
- Labs Eqiad Migration/2014-03-05
- Labs Eqiad Migration/Fallback
- Labs Eqiad Migration/Howto
- Labs Eqiad Migration/Progress
- Labs Eqiad Migration/Progress/Editor-engagement
- Labs Eqiad Migration/Tools
project migration example (gluster)
- Eqiad already knows about all the projects in pmtpa. So nothing needs to be done regarding project creation, security groups, or service groups.
- Migrate shared storage (home) by rsyncing from labstore2:
root@labstore2:/tmp# mkdir -p /tmp/testlabs/home root@labstore2:/tmp# mount -t glusterfs localhost:/testlabs-home /tmp/testlabs/home root@labstore2:/tmp# rsync -S -av /tmp/testlabs/home labstore1001.eqiad.wmnet:/srv/project/testlabs/ root@labstore2:/tmp# umount /tmp/testlabs/home root@labstore2:/tmp# rmdir /tmp/testlabs/home
- Migrate shared storage (project)
root@labstore2:/tmp# mkdir -p /tmp/testlabs/project root@labstore2:/tmp# mount -t glusterfs localhost:/testlabs-project /tmp/testlabs/project root@labstore2:/tmp# rsync -S -av /tmp/testlabs/project labstore1001.eqiad.wmnet:/srv/project/testlabs/ root@labstore2:/tmp# umount /tmp/testlabs/project root@labstore2:/tmp# rmdir /tmp/testlabs/project
- Alternately, with tar (from NFS):
root@labstore1001:~# ssh labstore4.pmtpa.wmnet tar cf - -C /srv deployment-prep | tar xf - -C /srv/project