IBM Power Cloud: PowerVC and Cloud alternatives Richmond and RTP Power User Groups. Overview and demo

Transcription

1 IBM Power Cloud: PowerVC and Cloud alternatives Richmond and RTP Power User Groups Overview and demo March 9-10, 2016 Bill Miller Power Systems Strategic Initiatives Technical Sales

2 Agenda ICM function highlights (4.1 and later) Power Cloud foundation Perspective and cloud basics Benefits Management stack OpenStack review and how it fits PowerVC What it is Image Management concepts Features Demo PowerVC and OpenStack cloud options What are VMware vrealize Automation and IBM Cloud Manager How they interact with PowerVC Using vra 3

3 IBM Power Cloud: Foundations 5

4 Some perspective providing computing services But what about computing requirements for today s applications? Find available hardware, or procure more Create the virtual machine Connect the infrastructure - Storage and network Setup for virtual machine install Install the virtual machine Customize the virtual machine Pay no attention to the man behind the curtain I m almost done I m waiting on IPs I don t have LUNs yet 6

5 Putting the wizard in the box But what about computing requirements for today s applications? Find available hardware, or procure more Create the virtual machine Connect the infrastructure - Storage and network Setup for virtual machine install Install the virtual machine Customize the virtual machine Pay no attention to the man behind the curtain 7 Enabling: Scale Simplicity and time-to-value Cloud (image and life-cycle management) I m almost done I m waiting on IPs I don t have LUNs yet

6 What s being said about cloud : One message According to a recent study by Forrester, 92 percent of enterprises expect to increase the role of on-premises cloud as part of their IT strategy, but cite operational expertise as their biggest challenge. ** ** Press release: IBM Delivers Local Cloud-as-a-Service With OpenStack- Powered Blue Box -- October // Blue Box 10

7 But then there s this problem: conflicting messages There's no future in on-premises IT -- it's time to move to the cloud - InfoWorld, 5/19/14* What does IBM offer? The Power Cloud solution (s) VMware vra IBM Cloud Manager * 11

8 Cloud??? What do we need to consider for Power Systems? What s provided? Who s managing it? Private On-premise Power Cloud Where s the hardware? 12

9 13

10 Cloud Alternatives: IBM Cloud Manager with OpenStack, v4.3 IBM Cloud Manager with OpenStack is an easy to deploy, simple to use Private and Hybrid cloud management software offering based on OpenStack with open cloud APIs. Importantly, we include IBM enhancements that feature improved ROI through superior resource scheduling and a self-service portal for workload provisioning, virtual image management, and monitoring. It's an innovative, cost-effective approach that also includes automation, metering and security. 15 Cloud solution supporting Heterogeneous Compute, Storage & Network Single point management across multiple domains & hypervisors x86, all IBM server architectures & major hypervisors supported Additional features enabling more efficient use of Cloud resources Dashboards show Cloud admin resource capacity & VM utilization Metering, Resource expiration & project approval policies, Network configuration & mapping Seamless Hybrid Enablement & Multi-cloud Federation Federation to multi instances of OpenStack and Hybrid Clouds Hybrid Clouds on and off premise options & SoftLayer support Accelerate Time to Market: Time to market improvement for new applications Integrated Management: Approvals, metering, billing, users and projects through a single pane of glass Flexible, modular design: Based upon OpenStack IaaS Access to OpenStack APIs Extensible via REST API allowing partners to easily customize the UI Open Simple Innovative

11 Cloud alternatives: VMware vrealize Automation Supports: OpenStack endpoint for PowerVC or ICM Data collection on VM resources and network states Creation of new LPARs based on existing image in PowerVC or ICM Deployment design via blueprint Customize deployments at request time Support for the endpoint in fabric groups and reservations Power lifecycle: on, off, restart PowerVC VMware vra 6.2 ICM (OpenStack) PowerVM zvm KVM on z Power KVM ** AIX RHEL SUSE RHEL RHEL SUSE SUSE SUSE Ubuntu *IBM i 16 * PowerKVM provisioning via PowerVC planned for 1Q 2016

12 IBM Power Systems Management Cloud Management IaaS with IBM Cloud Manager with OpenStack for Power End-user self-service provisioning with IBM ICM V4.x IBM Cloud Service catalog with virtual systems and applications Subscriber and account management (multi-tenancy) Hybrid Private Cloud with OpenStack and SoftLayer Virtualization Management PowerVC Advanced Virtualization Management with PowerVC Leadership solution for PowerVM and PowerKVM Virtual Image Management and Deployment Resource Pooling and Dynamic VM Placement Standard Edition: PowerVM or PowerKVM Platform Management HMC/K2 NovaLink libvirt/qemu PowerVM PowerVM PowerKVM Providing comprehensive and consistent management experience for Power Systems servers 19

13 HW Mgmt Platform Unique Virtualization Mgmt Management Platform Agnostic Cloud Admin Consumption Cloud Usage IBM Cloud: Think it. Build it. Tap into it. The Power Systems management continuum Cloud Services Cloud Manager Capability SelfServe UI PowerVC HMC Self-Service Portal x Service Catalog x Request VM Instance x Start/Stop VM Instance x x x Delete VM Instance x x x Tenant Management Cloud User Management Establish and Monitor Qutoas Manage IP Pools Approvals Chargeback Manage Service Catalogs x x x x x x x Cloud User Cloud Admin Virtualization Management PowerVC VM Image Management x x VM Image Deployment x x VM Image Capture x x Host Pools Management x Host and VM Monitoring x VM Placement x VM Availability Management x VM Performance Management x VM Isolation Management x IT Admin Platform Management HMC VM Lifecycle Management x x Hardware Configuration x Hardware Op Controls x Firmware Management x Service and Support x 21

14 IBM led the formation of the OpenStack Foundation, is a Platinum Sponsor and Board Member, and is a leading contributor to OpenStack Why is this good news for our clients? #1 Open, Modular Design Flexible architecture with open components enables options Platinum Sponsors Gold Sponsors #2 Vendor Interoperability High quality, multi-vendor & user community = freedom from lock-in #3 Rapid Innovation Large community effort enables faster developmental effort 23

15 PowerVC: PowerVM Virtualization Management OpenStack, Platform Computing and other IBM Value Added Components Security (KeyStone) Images PowerVC Virtualization Management Console OVF Scheduler OpenStack API Flavors Platform EGO Projects Quotas API Additions Monitoring VM Mgmt Virtualization Mgmt UI Simple and Intuitive Targeting the IT Admin New Management APIs Virtualization Management Monitoring & Events New Mgmt Capabilities Monitoring & Events More granular VM Mgmt Configuration Patterns AMQP DBMS Cinder Nova Neutron VIOS SSP VIOS vscsi EMC VNX/VMAX V7000/SVC/XIV/ DS8800 PowerVC Driver DB2 Network Drivers Platform EGO Provides Virtual Machine Placement Virtualization Drivers PowerVC Nova driver Leverage ecosystem to support broad range of IBM and non-ibm storage and network attached to Power Storage IBM and 3rd Party IBM Power Systems Network IBM and 3rd Party Packaging and Simplification Simplified Install and Configuration Intuitive Administration Model Focus on day 0/1 TTV

16 IBM Power Cloud: PowerVC foundation 30

17 What is PowerVC? Virtualization management for Power Systems PowerVM and PowerKVM Key Capabilities Advanced virtualization management for Power Systems Virtual machine capture and deployment Virtual machine relocation Policy based VM placement Optimization and rebalancing Quick setup and Time to Value Based on OpenStack Leverage open community Capabilities beyond OpenStack Simplified user interface Platform EGO scheduler Reliability and serviceability 31

18 Image management: PowerVC: A starting point Start with standard PowerVM infrastructure Add PowerVC in a RHEL 7.x instance somewhere in the enterprise Manage HMC Capture Deploy PowerVM depicted Not all steps shown, for simplicity Manage Disk(s) Storage* Deploy: Creates LPAR and LUNs Virtual Machine Capture Capture: Creates image LUNs Image 32 Block copy *NPIV, VIOS vscsi and SSP are all supported

19 PowerVC V1.3 Editions IBM PowerVC offers a lightweight, simple unified advanced virtualization management for Power workloads PowerVM or PowerKVM chosen at installation time New features in 1.3 Dynamic Resource Optimizer NovaLink integration More robust storage management Fabrics VIO adapter redundancy PowerVC Features HMC and NovaLink managed servers - NPIV (SVC/V7000/XIV/DS8800/EMC) - vscsi (VIOS SSP* or classic) Standard PowerVM Standard PowerKVM PowerLinux servers with PowerKVM - iscsi, local or NFS storage Managed Server Type All Servers Linux on Power Hardware POWER8 POWER7/7+ POWER6 Managed LPAR Type Managed From OS RHEL/SLES AIX IBM i RHEL 7.x (x>=1) Power (BE or LE) or x86 RHEL SLES Ubuntu Highly available VIOS configs n/a VM Placement by policy *SSP not supported with NovaLink 33

20 PowerVC features PowerVM LPAR and PowerKVM guest management as virtual machines Image management for fast and efficient workload creation Capture and deploy Policy-based placement Lifecycle management of virtual machines Start, stop, delete (with full cleanup) Suspend/Resume (PowerKVM) Maintenance Mode Resize (DLPAR) Migrate (LPM) Remote restart Volume and SAN management for autonomous storage management Zoning to facilitate VM creation SAN LUN creation, attach, detach, and deletion SSP LU creation, attach, detach, and deletion Other features Dual HMC support for availability Robust storage connectivity options Placement policies for efficient use of pooled resources, usage-based as an option Intuitive user interface simple to use 35

21 PowerVC V1.3 Requirements Standard Edition PowerVM Item Release License OpenStack EE Managed from Deployed Guests Power Systems Hardware Storage Description Sixth release of PowerVC now including NovaLink PowerVM Standalone or part of AIX Enterprise Edition Liberty release based Power Linux RHEL 7.x (LE or BE), x86 Linux RHEL 7.x, where x>=1 (RedHat license not provided) PowerVM Power Linux (RHEL 5.9, 5.10, 6.4, 6.5, 6.6, 7.1, 7.2) (SLES 11 SP3, SLES 12 (LE), Ubuntu 14, 15 (LE)) PowerVM AIX (AIX,6.1, AIX 7.1) RSCT version for Enhanced RMC communications with NovaLink PowerVM IBMi (7.1 TR8+, 7.2 TR1+) POWER6 / POWER6+ -> HMC-managed only POWER7 / POWER7+ -> HMC-managed only POWER8 -> HMC or NovaLink-managed SVC, VIOS SSP, vscsi, XIV (Gen3 or later), DS8800, EMC (VNX, VMAX) SAN Switch Brocade FC (fw 7.0 or later), Cisco FC (NX-OS 6.2) Network Switch No Ethernet Switch management Managed Through HMC or # of Managed Hosts 30 (HMC) and 200 (NovaLink) # of Managed VS 3000 (HMC) and 5000 (NovaLink) Virtual Machines total VIOS VIOS DB LDAP IPv4\IPv6 Provisioning method DB Enterprise Edition (version based on OSEE Liberty) OpenLDAP, Microsoft Active Directory Server IPv4, IPv6 (API Only) SAN storage based provisioning (NPIV), classic vscsi, and SSP (except NovaLink) using vscsi Browsers FireFox (Version ESR 31.x), Internet Explorer (Versions 9, 10, 11), Chrome (Version 40+) You might already have it at no charge Support often expands with each release 36

22 PowerVC V1.3 Requirements Standard Edition PowerKVM Item Description Release PowerVC Update for Standard Edition for PowerKVM (2.1. and 3.1) OpenStack EE Managed from Liberty release based Power Linux RHEL 7.x (LE or BE), x86 Linux RHEL 7.x, where x>=1 (RedHat license not provided) Deployed Guests PowerVM Power Linux (RHEL 6.4, 6.5, 6.6, 7), (SLES 11 SP3, 12), LE (Ubuntu 14.04, 15.04,15.10) Power Systems Hardware Storage SAN Switch Network Switch Managed Through POWER8 servers Local disk (boot), NFS (boot), iscsi (data) No SAN switch management No Ethernet Switch management Libvirt for PowerKVM # of Managed Hosts 30 # of Managed VS 3000 Virtual Servers total DB LDAP IPv4\IPv6 Provisioning method DB Enterprise Edition (version based on OSEE Liberty) OpenLDAP, Microsoft Active Directory Server IPv4, IPv6 (API Only) QCOW2 and ISO copies of images Browsers FireFox (Version ESR 24,x), Internet Explorer (Versions 9, 10, 11), Chrome (Version 25+) 37

23 PowerVC Placement Policies and VM Location Rules Placement Policy enabled per Host Group Migration, remote restart and maintenance mode relocations allowed only within Host Group Policy Description Placement Packing Pack workload on fewest physical servers Maximizes usable capacity, reduces fragmentation, reduce energy consumption YES Striping Spread workload across as many physical servers as possible Reduce impact of host failures, higher application performance YES CPU Balance Place VMs on the hosts with the least allocated CPU Higher application performance YES Memory Balance Place VMs on the hosts with the most available memory Improve application performance YES CPU Utilization Lowest CPU Utilization in the Host Group Averaged over the last 15 minutes YES 40

24 PowerVC Additional Relocation Rules Policy Description Initial Placement Migration or Remote Restart Affinity Affinity specifies that VMs should be placed on the same host or few hosts Useful for collocating VMs on the same host(s) No YES Anti- Affinity Do not place VMs on same host Useful for ensuring VMs are not collocated Availability cluster support (e.g. PowerHA) Higher application performance No YES 41

25 PowerVC Dynamic Resource Optimizer PowerVC Dynamic Resource Optimizer Policy-based automation to balance workloads PowerVC v1.3 Dynamic Resource Optimizer allows for automated rebalancing of workloads between servers Server workload can be automatically balanced two ways: Relocating Virtual Machines between servers Moving processor capacity between servers using Enterprise Capacity on Demand Works with AIX, IBM i or Linux VMs Move server Capacity with COD Relocate VM Relocate VM Host 1 Host 2 Host 3 42

26 Dynamic Resource Optimizer in action PowerVC Dynamic Resource Optimizer Set at Host Group level Advise or Active modes Exemptions are possible View in new DRO Events tab Entries for entering and exiting DRO condition Entries for success/failure of migration if in Active mode 43

27 Maintenance Mode Maint Mode Move VMs from designated host to others in the same Host Group Supported on both PowerVM and PowerKVM The host group policy determines destination locations Administratively driven operation, not automated, not designed for failure Can optionally NOT move, but disable the host as a target for deploy, migration and remote restart operations Requires functioning host and VMs in active state with OK health 44

28 Shared Processor Pool Support (V ) Images can be deployed to specific Shared Processor Pool AIX V7.1 AIX V6.1 Linux partitions IBM i Virtual I/O server ApplicationPool DefaultPool Virtual network & storage Hypervisor Virtual Network Virtual processors Virtual adapters Set as an attribute of the Compute Template; NOT at deploy time 45

29 PowerVC V1.3 Management Server Requirements 400 or fewer VMs VMs VMs VMs VMs Processing Units VPs Memory 10GB 12GB 20GB 28GB Disk 50GB 60GB 80GB 100GB 140 Always refer to latest docs, These numbers apply to Power-based and Intel-based RHEL 7.x VM (x>=1) running PowerVC, where Processing Units is physical cores for Intel 46

30 Considerations Dual HMC is supported, using the Change HMC feature. Failover is manual, not automatic. PowerVC must manage systems via NovaLink if the managed system is managed by both NovaLink and HMC PowerVC includes backup and restore commands for the PowerVC configuration and database. There is no highly-available server today, regular methods that provide HA for the PowerVC server operating system (VM) can be used. Loss of the PowerVC server does not affect running Hosts and VMs! PowerVC cannot manage FSM-managed PureFlex Power Nodes, but it can manage HMC-managed PureFlex Power Nodes. 48

31 Installation Installation script For download, must extract the contents of the compress tar archive (.tgz)./install -s [standard powerkvm] Runs pre-requisite checks and logs all output to logfile Location directory: /opt/ibm/powervc/log Length of installation time is based on disk speeds Approximately 15 minutes in testing Pulls in additional software packages from RHEL Yum repository already defined on the operating system. Other prerequisites Default network interface used is eth0 to modify, set environment variable: HOST_INTERFACE=ethX before running the installation script 49

32 Post-deploy customization with cloud-init How is each deploy customized uniquely? HMC Manage Disk(s) Storage* Deploy: Creates LPAR and LUNs Virtual Machine Capture Capture: Creates image LUNs Image Block copy 50

33 Cloud-init basics De-facto standard for early VM initialization and configuration in cloud deploys First release: 2010 Used extensively by AWS, and OpenStack clouds Most basic use is for hostname/ip/dns/gateway/ssh key Available in Linux distros since its inception (PowerVC support in 2014) Available starting in AIX 7.1 TL3 SP5 and 6.1 TL9 SP5 Default for AIX and Linux deploys in PowerVC Replaces Virtual Server Activation Engine (VSAE) IBM i uses VSAE cloud-init: Framework and tool written in Python to handle early initialization of a cloud instance. 51

34 Cloud-init configuration Driven by a combination of cloud.cfg file content and user-data (datasource) PowerVC uses ConfigDrive as its datasource ConfigDrive (mounted CD) is linked to Activation Input in PowerVC Modules (or directives) are used to perform customizations e.g., hostname, runcmd, Chef, Puppet, etc Four sections in cloud.cfg file modules to run Initial config: first steps user, ssh keys cloud_init_modules: during system init phase hostname, bootlist, reset rmc, /etc/hosts, non-rootvg imports, etc cloud_config_modules: later in boot process locale, timezone, package updates, chef, puppet, runcmd (shell) cloud_final_modules: after boot complete final message, reboot, scripts-per-* (once, instance, boot) 52

35 Cloud-init use Modules are called by specifying this string in Activation Input: #cloud-config Then specify the directive and its parameters Enter commands -- OR -- Choose file from browsing system Only used in legacy VSAE 53

36 Cloud-init examples Shell script invocation Begin with shebang, end with exit Modules are called by specifying this string in Activation Input, followed by its parameters #cloud-config users: - name: bill gecos: A user named Bill primary-group: system lock-passwd: false runcmd: - echo bill:abcd1234 chpasswd - echo Deployed as $(hostname), $(lparstat -i grep "Partition Name" tr -s ' '), at $(date "+%T on %D") >> /datafs/cloud_status 54

37 Cloud-init installation Linux Pretty straightforward AIX A little tricky Nigel s description for the AIX install: IBM i - continue to use Activation Engine (VSAE) 55

38 PowerVC Simplified Virtualization Management A graphical user interface targeting the IT administrator Simple, Intuitive and Appealing Progressive Disclosure of Details Tasks Tuned for Power Systems Simplified Setup Image Deployment and Capture Virtual Machine Management 56 56

39 Login The default authorized userid is root Operating system users authenticate to PowerVC Additional users can be added later 57

40 Initial PowerVC (PowerVM) Interface: Ready for customization 5 Help & Logout Required components for initial configuration

41 Main PowerVC (PowerVM) Interface: Customized Access & additional configuration Help & Logout Capacity Utilization Environment Verification 59

42 IBM Power Cloud: IBM Cloud Manager with OpenStack 100

43 IBM Cloud Manager with OpenStack delivers cloud usage benefits to administrators and users Easy to access, easy to use Service Request Catalog Hides underlying infrastructure from user, shifts focus to services delivered Enables the ability to provide standardized and lower cost services 102

44 The new ICM 4.3 UIs: Administrator Dashboard Not new, but enhanced, and now necessary 106

45 The new ICM 4.3 UIs: Self-service Portal New skin, inspired by BlueMix, on existing self-service code 107

46 IBM Power Cloud: VMware vrealize and Power Systems: Introduction vrealize Automation 110

47 VMware vrealize Automation offered as part of the vrealize Suite 111 The vrealize Suite Cloud Management Platform Unified and comprehensive management stack for IT services, physical infrastructure and external clouds Delivers vrealize Automation AND.. Intelligent Operations Manage infrastructure and applications in physical, virtual, and cloud environments with integrated capacity, performance, log, and configuration management. IT Business Management Align IT spending with business priorities by getting full transparency of infrastructure and application cost and service quality. Unified Management Use a common set of tools across private and public clouds with a consistent management experience and fast time to value Power and z Systems support is delivered as part of vrealize Automation only

48 How Does it Work? Public Clouds vrealize Automation PowerVM PowerVC IBM Cloud Manager z/vm PowerKVM KVM on z 112

49 How Does this Fit with IBM Systems Cloud Strategy? Chef JuJu Charms VMware vrealize Automation Cloud Orchestrator OpenStack Services HEAT Docker Puppet with Urban Code Deploy * z/vm KVM on IBM z x86 *Cloud Manager with OpenStack required to provision to PowerKVM until 1Q

50 Support and Requirements Platform VM Guest Post-deploy Actions PowerVM* AIX, IBM i, Linux Power On, Off, Destroy, Reboot PowerKVM Linux Power On, Off, Destroy, Reboot Pre-Requisites PowerVC 1.2.2** ICM 4.2 or 4.3 OpenStack Version Juno Juno/Kilo Required software licenses: PowerVM Standard or Enterprise RHEL for Power Systems or x86 (1 VM or LPAR for PowerVC, 2 CPUs) PowerVC Enterprise license for vrealize Automation + VM license packs **Testing/verification PowerVC is in process CPU, memory and disk requirements for vrealize Automation VMs: AF316A74AB6B.html VMware s Globally Unique Agent is required to be installed on image only for additional post-deploy processing and patterns Standard deployment network reconfiguration performed by clout-init 114

51 Blueprints, lifecycle management and Post-Deploy Action Options Images created in PowerVC are discovered by vra Anything specified with a PowerVC template (i.e. storage, compute, network), can be built into a vra blueprint by specifying the template id. Thus, entitlement, shared procs, etc. can be specified in vra vra supports passing in an Storage Connectivity Group id via the blueprint - thus, VSCSI, NPIV, storage domain, etc. are supported All life cycle operations, mobility, and self service are supported Platform VM Guest Post-deploy Actions PowerVM* AIX & Linux, IBM i Power On, Off, Destroy, Reboot PowerKVM Linux Power On, Off, Destroy, Reboot z/vm Linux Power On, Off, Destroy, Reboot KVM on IBM z Linux Power On, Off, Destroy, Reboot Pre-Requisites PowerVC ICM 4.2 ICM 4.2 ICM 4.3 OpenStack Version Juno Juno Juno Kilo Features included in the vrealize Automation Suite such as High Availability, live VM mobility, usage and accounting, capacity management, and monitoring are not currently supported for Power and z but will be considered for future releases 115

52 vra + Power Systems (the resources) Endpoints Blueprints 116

53 vra + Power Systems (creating and managing VMs) Image catalog (blueprints) Deploy VM Management 117

54 vra is sold by the Cloud Business Unit and/or VMware Power Systems boxes with OpenStack management (PowerVC and/or Cloud Manager with OpenStack) PowerVC for PowerVM Cloud Manager with OpenStack for PowerKVM PowerVC and Cloud Manager with OpenStack included in AIX EE IBM Systems Lab Services Quickly and confidently get PowerVC and VMware vrealize Automation provisioning and managing virtual AIX and Linux machines to PowerVM Cloud Builder Services (Cloud BU offering) Cloud Builder Services will deliver orchestration patterns to fully automate provisioning of customer workloads. Engage CloudBU seller to sell VMware vra and Cloud Builder Services 118

55 IBM Entry Demo 120

56 Thank You! 129

57 Legal Disclaimer IBM Corporation All Rights Reserved. The information contained in this publication is provided for informational purposes only. While efforts were made to verify the completeness and accuracy of the information contained in this publication, it is provided AS IS without warranty of any kind, express or implied. In addition, this information is based on IBM s current product plans and strategy, which are subject to change by IBM without notice. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, this publication or any other materials. Nothing contained in this publication is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software. References in this presentation to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and/or capabilities referenced in this presentation may change at any time at IBM s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product or feature availability in any way. Nothing contained in these materials is intended to, nor shall have the effect of, stating or implying that any activities undertaken by you will result in any specific sales, revenue growth or other results. If the text contains performance statistics or references to benchmarks, insert the following language; otherwise delete: Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will experience will vary depending upon many factors, including considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve results similar to those stated here. If the text includes any customer examples, please confirm we have prior written approval from such customer and insert the following language; otherwise delete: All customer examples described are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual environmental costs and performance characteristics may vary by customer. Please review text for proper trademark attribution of IBM products. At first use, each product name must be the full name and include appropriate trademark symbols (e.g., IBM Lotus Sametime Unyte ). Subsequent references can drop IBM but should include the proper branding (e.g., Lotus Sametime Gateway, or WebSphere Application Server). Please refer to for guidance on which trademarks require the or symbol. Do not use abbreviations for IBM product names in your presentation. All product names must be used as adjectives rather than nouns. Please list all of the trademarks that you use in your presentation as follows; delete any not included in your presentation. IBM, the IBM logo, Lotus, Lotus Notes, Notes, Domino, Quickr, Sametime, WebSphere, UC2, PartnerWorld and Lotusphere are trademarks of International Business Machines Corporation in the United States, other countries, or both. Unyte is a trademark of WebDialogs, Inc., in the United States, other countries, or both. If you reference Adobe in the text, please mark the first use and include the following; otherwise delete: Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries. If you reference Java in the text, please mark the first use and include the following; otherwise delete: Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. If you reference Microsoft and/or Windows in the text, please mark the first use and include the following, as applicable; otherwise delete: Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both. If you reference Intel and/or any of the following Intel products in the text, please mark the first use and include those that you use as follows; otherwise delete: Intel, Intel Centrino, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. If you reference UNIX in the text, please mark the first use and include the following; otherwise delete: UNIX is a registered trademark of The Open Group in the United States and other countries. If you reference Linux in your presentation, please mark the first use and include the following; otherwise delete: Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Other company, product, or service names may be trademarks or service marks of others. If the text/graphics include screenshots, no actual IBM employee names may be used (even your own), if your screenshots include fictitious company names (e.g., Renovations, Zeta Bank, Acme) please update and insert the following; otherwise delete: All references to [insert fictitious company name] refer to a fictitious company and are used for illustration purposes only. 130