Research Business Technology Pfizer Enterprise Elastic HPC Mike Miller Pfizer Research Business Technology May 18 th Prism Meeting Stockholm Sweden

Research Business Technology How do we define HPC? 2 Simply summarized as the computational laboratory Consists of: Desktop/Services, integrated with Global high performance cached file system Centralized large capacity/capability compute resources Used by: Direct expert computational scientists in chemistry, biology, DMPK, stats, pharm sci & clin pharm Indirect >2000 lab scientists using desktop apps that utilize HPC compute

Research Business Technology The Evolution of HPC at Pfizer blades (300 cores) 2000 SGI Origins (128 cores) x3950 (520 cores) 2010 on-demand Amazon VPC

Research Business Technology 4 Intersection of “The Cloud” and HPC

Research Business Technology Pfizer VPC Overview The Pfizer Virtual Private Cloud (pilot effort) has been implemented an extension of our physical data center. Infrastructure as a service affords rapid provisioning without compromising on: –Security –Compatibility –Accessibility –Agility –Utility Implementation Groton DMZ Amazon Web Services Cloud Secure VPN Connection over the Internet Subnets Pfizer’s isolated VPC resources Router VPN Gateway AWS Virginia DC

Research Business Technology FeatureAWSInternal VM’s Data Center Required to be joined to the Pfizer network Security Monitoring Public Confidentiality $0 mid-10’s $ Low 1000’s $ Provisioning Costs AMI/Xen Xen VMWare Bare Metal Avail. Config. 1 hr 4 hrs 2-8 wks Provisioning SLA s10-100s1-10s Request Capacity/Wk low-10’s $high-10’s$ Low-100’s $ Runtime/Depreciation Support Model 8x5 7x24 Self / incident OS Configurations Solaris, AS 400 Windows server 2003/2008 Linux REHL 5.x Environment POC HPC Support SLAsNone 24 hr Immediate 1 hr.1 mo.6 mo.Min. Billable Period Controls Black Box System root level access Qualified / Validated Stand Alone Moderate Complexity Simple High Dev / Test Prod Computing Requirements come in Many forms low med high

Research Business Technology Security Amazon practices & security measures successfully met audit criteria for Research level use Pfizer employed the same security systems used internally –IP-sec tunnels in to AWS –Pfizer Global Active Directory Joining machines and managing permissions –Linux & Windows

Research Business Technology Compatibility To get the most benefit from the cloud it was necessary to align AWS resource offerings with existing internal systems: –AMI’s (VM)  Pfizer Qualified RHEL 5 image Centrify/AD provides identification/authorization Kerberos credentials via AD –File cache (storage)  OpenAFS volumes accessible –IP mappings  Pfizer DNS AMI’s have Pfizer network identities & are discoverable –Allows AMI’s to be part of our LSF cluster –Users can do development work accessing the full range of Pfizer resources e.g. Software licenses utilize the pfizer flexlm server

Research Business Technology Availability AD & DNS give us full range of access to internal systems –LSF for job scheduling –Oracle / mySQL instances for accessing structured data –AFS for secure access to unstructured data High performance via local caching –Access to licensed and internally developed software

Research Business Technology Agility The $50M decision –Required completion of a time sensitive chemoinformatics task Workload was diverted from internal resources so they could be dedicated. Within 30 min 64 cores were spun up and joined to LSF For 4 days >50,000 jobs were executed Total cost <$1,500 –Results were obtained on-time and the decision taken

Research Business Technology Utility Internal Application Development –Tomcat web applications –Nightly builds & regression testing HPC capacity –Over 250 apps are accessible –LSF uses resource specifications to determine suitability and schedules jobs accordingly Over 100,000 jobs run –QM, ab initio –Virtual screening –Systems biology

Research Business Technology Implementation From PoC  Production –Provisioning, exploring commercial solutions that enable: One-time actions –Integrate with our procurement system Move to a debit (pre-allocated funding) model –Standard configurations Repeatable actions –Start/ Stop instances via a user centric dashboard User’s manage / are accountable for the resources they use LSF –Custom code detect workload Start / Stop AMI’s Leverage accounting