Merge Healthcare Virtualization CUSTOMER Merge Healthcare 900 Walnut Ridge Drive Hartland, WI 53029 USA
2014 Merge Healthcare. The information contained herein is confidential and is the sole property of Merge Healthcare. None of the information may be reproduced, copied, and/or re-distributed electronically, manually, or otherwise to any person without advance written permission from Merge Healthcare, except as may be expressly authorized by contracts or other agreements between Merge Healthcare and its customer. Merge Healthcare and AMICAS are registered trademarks and VERICIS, RadSuite, Abraxas, and iconnect are also trademarks of Merge Healthcare. Other trademarks or service marks referred to herein are the property of their respective owners. For application support or to report issues with user documentation, contact Customer Support: In North America: call toll-free 1-877-741-5369 Outside of North America: +31.40.299.0773 Email: support@merge.com Doc # Revision Date Description CVM-3/CAD 15.1 8/27/14 This document is a subset of CVM-3 with the parts specific to CADstream 2 2
vmware infrastructure design Contents Contents... 3 Summary... 3 VMware Infrastructure Design... 4 Merge Healthcare VMware Design Principles... 7 Merge Healthcare Virtualization Requirements... 8 Product Installation... 9 VMware Benchmarking... 10 End-User Performance Tests... 12 Worksheet... 13 Summary 3 Supported Merge Healthcare products can be deployed in many ways in a VMware vsphere 5.x environment. Merge Healthcare recommends specific guidelines for the deployment of these products. Following these guidelines will maximize the ease of use and performance of these products in your environment. Merge Healthcare has documented a number of techniques that are most likely to result in a highly successful deployment. These techniques are described in this document. Audience Merge Healthcare Sales and customer IT personnel Definitions Business Continuity [BC]: IT systems (networking and physical machines) designed to failover from one physical location to another in order to allow business to continue in the case of a catastrophic failure. Soft Business Continuity Event: An orderly Business Continuity failover to a redundant site. Hard Business Continuity Event: An unplanned, immediate, and abrupt Business Continuity failover due to catastrophic systems failure or Force Majeure. 3
vmware infrastructure design VMFS: The VMware File System. A high-performance, dedicated file system, capable of simultaneous access by multiple ESX Server systems, and on which virtual disks for virtual machines are stored as files. Datastore: VMware terminology for a disk subsystem (partition, or physical disk/lun) formatted as VMFS on which VM configurations and data files exist. OVF: Open Virtual Machine Format is a virtual machine distribution format that supports sharing virtual machines between products and organizations. Applicability Merge CADstream v6.0 VMware Infrastructure Design The following infrastructure design is only a recommendation, unless specified. Whether the recommendation is followed does not affect system support; some recommendations may not apply to your circumstances. It is strongly advised that you adhere to the following recommendations for your environment. To ensure proper performance and reliability, Merge Healthcare advises that a test infrastructure adheres to the same recommendations. VMware Application Structure 4 Merge Healthcare requires using VMware vsphere 5.x. All Merge Healthcare documentation and supported configurations assume this VMware software level. Merge Healthcare recommends using VMware vcenter 5.x. VMware vsphere and vcenter 4.x is End of General Support, and no longer supported by Merge Healthcare. Merge Healthcare recommends a separate cluster definition within the VMware vcenter including separate physical servers dedicated to Merge Healthcare VM systems for VMware HA configurations. Merge Healthcare supports integration into existing VM clusters. However, performance cannot be guaranteed. Network Structure The customer is required to provide a redundant physical networking layer to all VMware ESXi hosts which run production Merge Healthcare VM systems. Storage Structure Merge Healthcare recommends using dedicated storage systems for production Merge Healthcare 4
VM systems. vmware infrastructure design Merge Healthcare recommends the use of VMware High Availability (HA) which requires VMware vcenter and a shared disk implementation (iscsi or Fibre Channel). VMware disk performance can vary depending on VM system load and the shared storage subsystem. It is the customer's responsibility to monitor the VMware environment including the network, server, and storage system to provide adequate resources to support the Merge Healthcare VM systems. 5 5
vmware infrastructure design Business Continuity Merge Healthcare recommends using Business Continuity (hard or soft failover) which requires replicated SAN storage and proper bandwidth allocated to meet the SLA requirements of the customer. In High Availability (HA) configurations, the customer is required to provide a SAN disk infrastructure (iscsi or Fibre Channel) and redundant paths to all VMware ESXi servers which host Merge Healthcare VM systems, appropriately configuring VMware ESXi to have access to the redundant paths. The SAN must be configured such that all VMware ESXi systems which can host the Merge Healthcare VM systems have access to all the datastores on which Merge Healthcare VM systems reside. VMware HA requires VMware vcenter and a shared disk implementation using a SAN. The customer is solely responsible for providing the appropriate hardware, VMware licensing, and networking requirements. 6 Business Continuity Example 6
merge healthcare virtualization requirements (software only) Merge Healthcare VMware Design Principles Merge Healthcare supports several deployment methods into a customer s VMware environment, depending on the product. The deployment method for CADstream will be software only. Merge Healthcare will provide general instructions of VM system configurations within a VMware vcenter or direct VMware ESXi configuration. The Merge Healthcare VMware product solutions will consist of the following items for each Merge Healthcare VM system: Software only Virtual Machine Network Configuration requirements Virtual Machine Operating System License (SLES or Windows Server) Merge Healthcare does not provide the operating system license unless purchased through Merge Healthcare. Virtual Machine Third Party Applications Licenses (if required for the Client) Virtual Machine Documentation Package Virtual Machine Media Kit Merge Healthcare will provide implementation services for all production Merge Healthcare VM Systems where applicable. 7 Merge Healthcare will support the following VMware virtual disk format for Merge Healthcare VM systems: Production: Thick Provision Lazy Zeroed or Eager Zeroed (recommended) Test: Thin Provision Merge Healthcare VM systems may have separate VM disks for the OS, Application, Database, and DICOM storage. Merge Healthcare supports installation of VMware Tools on all systems. Merge Healthcare supports upgrading of VMware Virtual Machine Hardware Version on all systems. No oversubscription should occur for Production systems such as resources like CPU, memory, and storage on the VMware host in order to meet the target performance. Merge Healthcare recommends that the customer follow all VMware and hardware vendor best practices for infrastructure planning and design. 7
merge healthcare virtualization requirements (software only) Merge Healthcare Virtualization Requirements (Software Only) Merge CADstream The following are Merge Healthcare virtual machine settings, and required resources. Virtual Hardware Operating System vcpus (vsockets * vcores) Memory Disk Controller Network Card Total Video Memory Virtual Disk 0 Virtual Disk 1 Requirements Windows Server 2008 R2 Standard Windows 7 Professional 64-bit see table below see table below LSI Logic SAS Minimum: E1000 Recommended: VMXNET 3 8MB (1280 x 1024 pixels) Minimum: 300GB (OS, Application, DB) Average of 100 Studies in the Database (working set) at 1.7GB/Study Optional CADalog 8 drive for long term storage of compressed data. See Additional Storage section below. Concurrent Users 1 5 8 Minimum vcpus (vsockets * vcores) 3 (1*3) 6 (2*3) 8 (2*4) Minimum Memory 4 GB 8 GB 8 GB A physical DVD-RW is required to be attached to the physical host that will be hosting the virtual machine in order to burn studies to DVD. The virtual machine requires passthrough access to the DVD-RW. 8
product installation Additional Storage The following table is a guideline to determine additional CADalog storage that may be required to support annual growth for the number of labs and studies. Number of Annual Studies Space Required for Annual Studies a 1,000 800GB 3,000 2.4TB 10,000 8TB a. Value is estimated per site and year: - CADalog (compressed): 800MB per study Product Installation Supported VMware Releases Merge Healthcare products only support the following VMware software releases: VMware vcenter Server, 5.x VMware ESXi, 5.x Deployment and Configuration Responsibilities 9 The Merge Healthcare installation team may not have direct access to the customer's VMware environment; assistance may be needed from the site's IT staff. The following high-level chronological steps separate responsibility to either the customer or Merge Healthcare. Software Only Deployment 1. Install the required Operating System version per Merge Healthcare requirements. Merge applications may require different Windows configuration after OS installation. Contact your Merge Healthcare Project Manager to verify application requirements. (customer) 2. Install all relevant Operating System patches that Microsoft has posted on the security web site. (customer) 9
vmware benchmarking 3. Install helper applications (anti-virus, etc). (customer) 4. System Configuration a. Virtual MAC address (customer) b. Host name (Merge Healthcare or Distributor) c. Network Information (Merge Healthcare or Distributor) 5. Application Installation refer to Installation Guide CAD-12332 (Merge Healthcare or Distributor) 6. Application Configuration (Merge Healthcare or Distributor) Software Only Installation Preparing for Software Only Deploying Merge Healthcare assumes the following before application installation The virtual machines resources are allocated based of the virtualization requirements. The virtual machine has the required operating system installed. Merge Healthcare support has established connectivity to the operating system; contact your Merge Healthcare Project Manager to establish/verify connectivity. Deployment of Software Only 10 Contact the Merge Healthcare installation team to schedule application installation and system configuration. Merge Healthcare Product Configuration Supported Merge Healthcare products need to be individually configured to support custom configurations. The Merge Healthcare installation team will take over the completion of the installation and configuration for each desired product. Merge Healthcare requires a manually entered MAC address for each virtual machine; Merge Healthcare licensing is assigned to the MAC address. If the MAC address changes due to Business Continuity, the application may no longer be operational. Merge Healthcare requires unique system names for each device. VMware Benchmarking The Merge Healthcare installation team may perform a series of benchmarking tests on the system to ensure minimum performance of the applications is met. These tests will cover a range of system inputs and outputs, network response, and study performance. Any restriction must be resolved before the 10
system is available for use. vmware benchmarking Application I/O Benchmarking One or more application I/O benchmarking tests may be performed by Merge Healthcare personnel, depending upon the application. 11 11
end-user performance tests Application Study Benchmarking Merge Healthcare personnel may use a variety of image formats, compression levels, and response times to determine application performance depending upon the application. End-User Performance Tests The following tests constitute an end-user focused test procedure intended to be used for systems running under VMware. This procedure should be performed by the customer at system checkout time and also when the customer feels performance is degraded. A log should be kept for each time the testing is performed. Tests that are found to be out of clinical bounds will likely necessitate further testing (performed with lower level tools) to be done by support personnel to help the customer find the area of their VMware system that has degraded performance. The specified rates/durations are considered absolute minimum values for clinical usage. The performance observed on systems running on native hardware (non-virtualized) is significantly greater. CADstream If there is a CADstream server that is running under VMware perform the following tests. 12 No other user shall be logged in during this procedure. Locate a study that meets the following specification: MR Breast study 6 dynamic series with 88 slices (512x512 matrix size) each 1. Time how long it takes for CADstream to import the MR Breast study from files on the local hard drive. Record the time_ It should take less than 60 seconds. 2. Time how long it takes to completely export the original data from the MR Breast study to local hard drive as DICOMDIR Record the time_ It should take less than 60 seconds. 3. Time how long it takes to completely process or re-process the MR Breast study Record the time_ It should take less than 4 minutes. 4. The average scrolling time for 88 images series for each client. Record the time_ It should take less than 30 seconds. 5. Each client shall be able to perform Live MIP rotations with an update rate of 4 frame per second or better (min of 3 clients). 12
worksheet Worksheet The following worksheet is a helpful tool in developing an understanding of the virtual infrastructure. The worksheet is not required to be completed pre or post implementation, but maybe required in troubleshooting performance issues. Virtualization Software Hypervisor Vendor, Product, Version and Build Datacenter Management Software Vendor, Product, Version, and Build Server Hardware Is the Host Shared with non-merge Healthcare VMs? Number of Hosts: Uniform Hosts [yes/no]: Server Manufacture and Model Processor Vendor and Model 13 Processor Speed (GHz) Total Sockets/Total Cores/Total Threads BIOS Version Memory Size (in GB, Number of DIMMs) Memory Type and Speed Number of Disk Controllers Disk Controller Vendors and Models Number of Host Bus Adapters Host Bus Adapters Vendors and Models Number of Network Controllers Network Controller Vendors and Models 13
worksheet Network Switches Network Switch Vendors and Models Network Switch Vendor and Models Uplink Network Speed Fabric Switches Network Switch Vendors and Models Fabric Switch Vendors and Models Network Speed Storage Hardware Is the Storage Shared with non-merge Healthcare VMs? Array Vendors, Models, and Firmware Versions Controller IO Cards (per controller) 14 Disk Space Used Array Cache Size Total Number of Physical Disks Used Total Number of Enclosures/Pods/ Shelves Used Number of Physical Disks Used per Enclosure/Pod/Shelf Total Number of Storage Groups Used RAID Type Number of members per RAID Set Disk Vendors, Models and Speeds 14