SHARPn Cloud Computing Resource Lab

1. SHARPn Cloud ComputingResource Lab June 11, 2012 Troy Bleeker

2. Agenda • Participants will learn • A cloud computing recap. • What is our cloud like and why do we have it? • Lab: • VPN, IDs, shared file server, tool install and configuration • Launch an instance, attach volumes • Test application on an instance

3. Cloud Computing (recap) 21 physical machines 200 CPUs 1.8TB of RAM 36.3TB of storage 22 NICs Gigabit Ethernet Virtual is dependant on the Actual Actual versus Virtual

4. Cloud Computing Benefits • Remove the cost of acquisition, install, and configuration Right machine Right person Right skills Right time

5. More Benefits Image • Flexibility of Volumes (for example) • Can move to bigger instance • Backs up only the pertinent data • DO NOT USE system volumes for critical data • /dev/sda1 or /dev/sda2 Launch Instance Instance

6. What is our cloud? Cirrusmatic Server Persistence Storage Cloud Controller Walrus Controller Image Storage Cluster Controller Storage Controller • Infrastructure as a Service (IAAS) • Ubuntu Enterprise Cloud (UEC) is Ubuntu's Eucalyptus-powered cloud Private Switch Node Server 1 Node Server 2 Node Controller Node Controller VM VM VM VM VM VM Admin Client Interface Build/Backup Server VPN/LAN To Manage Cloud Node Server 11 Node Server 3 … User Node Controller Node Controller Cirrusdata Server VM VM VM VM VM VM Samba file server To Connect To Instances

7. Purpose • The cloud environment exists to fulfill the mission of SHARPn and other related projects at Mayo Clinic. …will enhance patient safety and improve patient medical outcomes through the use of an electronic health record. … We propose research that will generate a framework of open-source services that can be dynamically configured to transform EHR data into standards-conforming, comparable information suitable for large-scale analysis, inferencing, and integration of disparate health data.…to enable the use of EHR data for secondary purposes, such as clinical research and public health. By creating tangible, scalable, and open-source tools, services and software for large-scale health record data sharing, this project will ultimately help improve the quality and efficiency of patient care through the use of an electronic health care record.

8. Setting Expectations • Our cloud is a protected, non-public resource • Government regulations • Mayo Clinic security policies • Our cloud is a research system not a production system • The cloud is not monitored 24x7 • Maintenance is completed during business hours • Users setting up instances must have Linux know-how and some system administration skills • Data backup is available but must be set up by the user • Help is available if needed

9. Security • File share is separate,but still protected • VPN thru Firewall • Encryption • Key pairs • User IDs • No PHI File shares C. Cloud Machine Image setup B. SHARP file share Images (VMs) Images (VMs) Images (VMs) Launch A. VPN D. Instance D. Instance D. Instance Cloud users Institutional VPN account, share with your group (password reset <=180 days) Common SHARP file server, user ID for each person (does not expire) Start/stop/manage cloud machine images/instances, user ID for each person (does not expire) Default, root user ID in a running Instance is “ubuntu” (does not expire)Creator of the instance can create other user IDs

10. 200 CPUs 1.8TB of RAM 36.3TB of storage Content Virtual Instance Types

11. Hurdles • Simultaneous access to the cloud and work • Skills required for software on images • Need for speed will send doctors to the cloud:http://www.healthcareitnews.com/news/need-speed-will-send-doctors-cloud-experts-say • Cloud Security: Public versus Privatehttp://www.healthdatamanagement.com/news/private-public-cloud-computing-data-security-44566-1.html Articles

12. http://informatics.mayo.edu/cirruswiki/index.php/Cloud_Resource_Labhttp://informatics.mayo.edu/cirruswiki/index.php/Cloud_Resource_Lab • VPN must be successful before moving on • IDs and Passwords are CASE SENSITIVE