...

Spin up machine

Run ansible scripts

Create 2 new drives

a. If mounting drives for fedora-data or for the tmp directory for migration, make sure to change the owner to tomcat7 (sudo chown tomcat7:tomcat7 folder) for fedora-data and hydep:deploy for the tmp directory (sudo chown hydep:deploy folder)

Box Build changes

The current build scripts in Ansible have problems with a few changes we need.

...

1. In the AWS visual interface, go to EC2
2. Go to Volumes
3. Select Create Volumes
4. Make sure the volume is
   1. General Purpose SSD
   2. 150 GB
   3. Availability Zone b
5. Create 2 of these
6. 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.
7. ssh into the box
8. Run sudo fdisk -l
   1. You should see /dev/vxdg and /dev/xvdh
   2. If not, check if the volumes are attached
9. Create the filesystem for each disk
   1. sudo mkfs.xfs /dev/xvdg
   2. sudo mkfs.xfs /dev/xvdh
10. Mount each disk
    1. sudo mount /dev/xvdg /opt/fedora-data
    2. sudo mount /dev/xvdh /opt/sufia-project/releases/XXXX/tmp
11. Edit the fstab file to retain these mounts
    1. sudo vi /etc/fstab

       1. /dev/xvdg /opt/fedora-data xfs defaults 0 0

       2. /dev/xvdh /opt/sufia-project/releases/XXXX/tmp xfs defaults 0 0
12. Change the owner of the two mount locations
    1.  sudo chown -R tomcat7:tomcat7 /opt/fedora-data
    2. sudo chown -R hydep:deploy /opt/sufia-project/releases/XXXX/tmp

Solr

1. If this is the first time sufia has been deployed, Solr now runs outside of tomcat and needs to be restarted after deployment.
2. sudo service solr restart

...