Skip to content

Instantly share code, notes, and snippets.

@tingletech

tingletech/dsc_migration.md

Last active August 29, 2015 14:06
Show Gist options
  • Save tingletech/93bd746e77e202d18619 to your computer and use it in GitHub Desktop.
Save tingletech/93bd746e77e202d18619 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
dsc_migration.md

Amazon migration for dsc.cdlib.org

current production environment retires 2015-Dec-15

dsc.cdlib.org was designed to merge many Veritas VCS clusters into one virtual machine, for migration from solaris to vmware. Migrating to AWS, we are going to split things up some again.

XTF based websites

During the VCS (fail-over clustering) on big solaris boxes era, it was easy to maintain high application available through a patch cycle at the OS level. Our VMware architecture fails to provide the same level of availability. Moving to Amazon gives us the opportunity to architect the application so that high use resources (OAC and Calisphere) can remain available during routine maintenance and automatically scale out given higher load.

Keep XTF data and index on amazon s3

S3 buckets will use versioning, data maintained by voro

  • /dsc/data/xtf/data static files served by cloudfront

  • /dsc/indexes/xtf.backup.tar prebuilt index unpacked on web tier workers

Elastic Beanstalk for tomcat

Elastic Beanstalk automatically handles the deployment details of capacity provisioning, load balancing, auto-scaling, and application health monitoring without you having to specify anything regarding the size or type of these resources, and notifies you once the environment has been launched. You can also deploy a different application version to a running environment if, for example, you have a newer version of your code you wish to deploy, or if you want to roll back to a previous version. http://aws.amazon.com/elasticbeanstalk/details/

Will create a script to deploy XTF to elastic beanstalk. Instances will pull indexes from S3. Cloudfront CDN added in front of beanstalk.

voro

  • Single instance EC2/EBS with shell access to operators and webDAV access to contributors.
  • maintains/builds master S3 buckets, XTF indexes, and xtf.war files for the access tier.
  • use elastic beanstalk for wsgi/django? Docker on beanstalk?
  • Voro's mysql database will be migrated to multi AZ RDS.

timeline

before the end of 2015 Q1

  • establish sync from current dsc.cdlib.org codebase to s3
  • tweak current cloudfront origins to point to s3
  • set up beanstalk project for XTF backend
  • turn rewrite rules to point to amazon backend
  • migrate dsc rewrite rules for oac and calisphere to AWS (Docker on beanstalk?)
  • cloudfront in front of all public pages in AWS; bulk of voro still at kaiser

before the end of 2015 Q3

  • mySQL migrated to RDS
  • dsc.cdlib.org (back to voro.cdlib.org ?) running on AWS

before the end of 2015 Q4

  • imgzoom.cdlib.org
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment