...

• Restricted: Two CU researchers' Cloud case-studies (Cornell NetID required; cited below, too)
• Ramping up and down cloud services to save money
  • http://www.docker.com/
  • http://agaveapi.co/reproducible-science-with-agave-and-docker/
• Cornell's own CAC’s RedCloud:
  • www.cac.cornell.edu/redcloud
• http://cloudcomputing.cornell.edu/Research.php (added 3/20/15)
  • This is sponsored by the Computer Science department. (Not tied to CIT or CAC.)
• http://itnews.cornell.edu/cloudification-services-will-offer-ramp-cloud-infrastructure (3/13/15 CIT article)
• A Cornell IT manager peer shared this nice digestible interview/talk with one of his favorite experts talking about cloud and IT for life sciences:
  • http://info.averesystems.com/blog-0/the-state-of-it-infrastructure-in-the-life-sciences
  • Note: Cross-posted in Yammer, <http://www.it.cornell.edu/services/yammer/>.

Chemistry "case study" of a web server, hosted using Amazon's Web Service (AWS)

• September 2016: CIT successfully packaged old NMR Scheduler's Python code and text files and moved it to contemporary OS and web server software running on AWS. They had been running on an old, not patched or maintained, Linux and Apache public web server.
  
  • http://nmrscheduler.chem.cornell.edu/
    • http://nmrscheduler.chem.cornell.edu/cgi-bin/login.pl
  • Cloud Support
• Automatic monthly billing via internal Cornell KFS. Over the past week (9/9/16), the NMR Scheduler AWS resources cost about $0.20/day Expect to see this rise a little when we release it. Still CIT folks would be very surprised if it was more than $0.50/day all told.
  • For 365 days/ year, that comes out to ~$73-183/year for a patched and otherwise maintained Linux and Apache public web server running custom, old Perl scripts. And one easily replicated, if necessary.
  • AWS Standard Tagging

Cornell "case study", using Amazon's Web Service (AWS)

...