Spin up machine
Run ansible scripts
Activate maintenance mode on old server
Export Fedora data (in sufia 6 instance)
Run audit script (takes 4 or 5 mins)
RAILS_ENV=production bundle exec sufia_survey -v
Make sure you have the latest deployment
- Make sure tmp/export is empty
Run json export (takes < 10 mins)
$ RAILS_ENV=production bundle exec sufia_export --models GenericFile=Chf::Export::GenericFileConverter,Collection=Chf::Export::CollectionConverter
Open up fedora port to the other server so it can grab the binaries
Change all the 127.0.0.1 URIs to reflect internal IPs, e.g.
$ find tmp/export -type f -name "*.json" -print0 | xargs -0 sed -i "s/127\.0\.0\.1/[internal_ip_of_prod]/g"
- The internal IP of prod is: 172.31.48.168
- The internal IP of staging is: 172.31.58.101
- Move the resulting directory full of exported data from tmp/export to the new server's tmp/import (or wherever desired; this can be provided to the import script)
- $ cd tmp; tar -czf json_export_201611141510.tgz export
- Then from your own machine:
- $ scp -3 -i ~/.ssh/test.pem hydep@staging:/opt/sufia-project/current/tmp/json_export_201612141435.tgz hydep@new_box_ip:~/.
Migrate postgres
- Run the following to generate the export.
pg_dump -U postgres chf_hydra -Fp > chf_hydra_dump.sql
Copy the file to the new machine
scp -3 -i ~/.ssh/test.pem ubuntu@production_ip:~/chf_hydra_dump.sql ubuntu@new_box_ip:~
Import the file
psql -U postgres chf_hydra < chf_hydra_dump.sql
- Run the following to generate the export.
Deploy chf-sufia to new server
Create Drives
In the AWS visual interface, go to EC2
Go to Volumes
Select Create Volumes
Make two volumes with the following features:
General Purpose SSD
150 GB
Availability Zone b
Once each one is made, select it and under Actions choose Attach Volume. Type the name or id of the machine and attach the volume.
ssh into the box
sudo fdisk -l
You should see /dev/vxdg and /dev/xvdh
If not, check if the volumes are attached
Create the filesystem for each disk
sudo mkfs.xfs /dev/xvdg
sudo mkfs.xfs /dev/xvdh
Edit the fstab file to retain these mounts
sudo vi /etc/fstab
/dev/xvdg /opt/fedora-data xfs defaults 0 0
/dev/xvdh /opt/sufia-project/releases/XXXX/tmp xfs defaults 0 0
- mount the disks
- sudo mount -a
Change the owner of the two mount locations
sudo chown -R tomcat7:tomcat7 /opt/fedora-data
sudo chown -R hydep:deploy /opt/sufia-project/releases/XXXX/tmp
Restart Solr
If this is the first time sufia has been deployed, Solr now runs outside of tomcat and needs to be restarted after deployment.
sudo service solr restart
Ensure apache is off on new server
We don't want anyone doing stuff before we're ready.
Restart Tomcat on new server
- sudo service tomcat7 restart
Move over minter statefile
- On Production
- sudo cp /var/sufia/minter-state ~
- sudo chown ubuntu:ubuntu minter-state
- Then copy the file
scp -3 -i ~/.ssh/test.pem ubuntu@production_ip:~/minter-state ubuntu@new_box_ip:~
- On New Box
- sudo mv minter-state /var/sufia
- sudo chown hydep:deploy /var/sufia/minter-state
- On Production
Import Fedora data (in sufia 7 instance)
Become hydep
Unpack the exported json files
cd /opt/sufia-project/current/tmp/
cp ~/json_export_201612141435.tgz .
tar -xzf json_export_201612141435.tgz
mv export import
configure sufia6_user and sufia6_password in config/application
run the import
$ RAILS_ENV=production bundle exec sufia_import -d tmp/import --json_mapping Chf::Import::GenericFileTranslator=generic_file_,Sufia::Import::CollectionTranslator=collection_
run (currently nonexistent) verification job
migrate dump.rdb
Reindex solr
How to check the statefile
There are 3 parts to the state: sequence, counters, and seed. You need the correct combination of all three in order to have the right state. However, if you know you have two valid state files with the same origin you can do a rough comparison of their equivalence just by checking the sequence. To check sequence in our 7.2-based application:
$ cd /opt/sufia-project/current$ bin/rails c production> sf = ActiveFedora::Noid::Minter::File.new> state = sf.read> state[:seq]
To check in our 6.7-based application:
$ cd /opt/sufia-project/current$ bin/rails c production> sm = ActiveFedora::Noid::SynchronizedMinter.new> state = {}> ::File.open(sm.statefile, ::File::RDWR|::File::CREAT, 0644) do |f|> f.flock(::File::LOCK_EX)> state = sm.send(:state_for, f)> end> state[:seq]
To check sequence on a file that's not in the default location, pass the template and the filename when you create the object with 'new', e.g:
> sm = ActiveFedora::Noid::SynchronizedMinter.new(".reeddeeddk", "/var/sufia/minter-state")
Misc.
Postgres
You can get a list of all tables and fields with the command:
SELECT * FROM information_schema.columns WHERE table_schema = 'public'
Cleanup
To clean up a server for a new migration test, take the following steps.
- Stop Tomcat and Solr
- Remove all the folders in /opt/fedora-data.
- Remove all the files in /var/solr/data/collection1/data/index/, and /var/sufia/derivatives
- Remove all the upload files in the tmp directory of the version of sufia used.
- Enter into postgres (psql -U postgres)
- Drop the fcrepo database (DROP DATABASE fcrepo;)
- Build a new fcrepo database (CREATE DATABASE fcrepo;)
- Grant the fcrepo user (currently tribly until we get a better user) all privileges on fcrepo. (grant all privileges on fcrepo to tribly;)
- Restart tomcat and sol