ibm activitydowibm nload 9

Slide 1PowerVM AIX 6 Workload Partitions Manager - Live Application Mobility
Live Application Mobility and Live Partition Mobility Usage Scenarios
© 2008 IBM Corporation
i5/OS V6R1 on a blade
System p 550
A logical representation of resources not constrained by physical limitations
Create many virtual resources within a single physical device
Reach beyond the box—see and manage many virtual resources as one
Dynamically change and adjust across the infrastructure
What is virtualization?
Virtualization is a logical representation of resources not constrained by physical limitations.
One way of looking at virtualization is to visualize taking something large, carving it up and making it look like many small things. Think of that as partitioning an Intel server using technologies like the VMware.
Another way of looking at it is making many small things work in concert as one large thing. A good example of that is storage virtualization, where we can have multiple storage arrays from different vendors, work in concert as if they were one large single storage pool.
And, finally, it’s being able to dynamically change and adjust these resources across the infrastructure. Think of that as being able to do what we could do in the mainframe for years, being able to extend that capability across a heterogeneous distributed enterprise.
Utilization
Reduce total cost of ownership and make better use of IT assets by significantly improving server utilization
Simplify the management of IT infrastructure by making workloads independent of hardware resources, thereby enabling customers to make business-driven policies to deliver resources based on time, cost and service-level requirements
Improve business responsiveness and operational speed by dynamically re-allocating resources to applications as needed -- to better match changing business cycles or handle unexpected surge in demand
What is PowerVM?
Logical Partitioning
Hardware and software that delivers industry-leading virtualization on IBM POWER processor-based processors for UNIX, Linux and i5/OS customers
Linux on x86 binaries
IBM develops hypervisor that would become VM on the mainframe
IBM announces first machines to do physical partitioning
IBM announces LPAR on the mainframe
IBM announces LPAR on POWER
1967
1973
1987
IBM intro’s POWER Hypervisor ™ for System p and System i™
IBM announces PowerVM
client quote source: Brakes India case study published at http://www.ibm.com/software/success/cssdb.nsf/CS/STRD-76DHWE?OpenDocument&Site=eserverpseries&cty=en_us
“[PowerVM] ensures that we are making the best possible use of hardware resources across our entire environment.”
- T N Rangarajan, VP of IT, Brakes India
August 2007
2008
IBM announces POWER6™, the first UNIX servers with Live Partition Mobility
A 40 year tradition culminates with PowerVM
IBM has a long history of leadership in the area of virtualization. This is not a new technology – it has been around since 1967 on the mainframe, and was first developed for the POWER processor back in 1997. Since then we have been refining the technology to make it more reliable, scalable and better server your business needs.
1967 IBM develops hypervisor that would eventually become VM on the mainframe
1973 IBM announces S/370 model 158 and model 168, the first two machines to do physical partitioning
1987 PR/SM is announced (LPAR on the mainframe)
1990 ES/9000 family is announced. This is the last IBM mainframe to support physical partitioning
1997 POWER LPAR design begins
1999 System i LPAR announced
2001 System i ships sub-processor LPAR support / System p ships whole processor LPAR support
2001 LPAR introduced in POWER4™ with AIX 5L™ V5.1
2004 MicroPartitioning LPAR and Virtual I/O with POWER5™ and AIX 5L V5.3
one or more servers
Sys1
Sys2
Sys3
more costs
more headaches
Application A
Application B
Application C
As you show these next animated charts, do not try to follow the animation. Just talk to the business value, and let the animation tell the technology story!
At the heart of a system is processing power—but to complete the system you also need adapters, storage, power, cooling, etc.
Today, most organizations run a single application on a single server or more and opt to buy more processing power than they need—just in case.
There are three costs associated with this approach—redundancy, complexity and a lack of flexibility
- Redundancy
Spend more on hw than you need to in the first place
Wasteful--opportunity cost of underutilized capacity
- Complexity
Spend more to configure, maintain and support your OE than is necessary
Requires expertise you may not have in-house
Adds time to everything you want to do
- Lack of flexibility
Unable to exploit opportunities requiring quick response
1973 IBM announces S/370 model 158 and model 168, the first two machines to do physical partitioning…
Sys1
Sys2
Sys3
And does not enable you to respond
to changing requirements of an
on demand business
SLIDE ANIMATES AUTOMATICALLY
In this scenario, you still have to manage each virtual server.
Each virtual server still requires its own I/O, and each server is defined and limited by the physical boundaries.
IT CANNOT ADAPT TO MEET THE NEEDS OF AN EVER-CHANGING on demand WORLD,
System z and POWER Hypervisors are designed to provide business-critical availability
Integrated server firmware is optimized for hypervisor role - "lean and mean"
Intelligent machine check processing
Machine check interrupts are used to localize hardware failures to individual partitions
CPU GardTM
If the rate of soft failures on a given processor crosses a threshold, then a spare (COD) processor is substituted transparently or the failing processor is taken offline
Mature and field-proven technology
PR/SM widely used since 1988; POWER Hypervisor based on System i hypervisor, since 1999
AIX
POWER5™
Server
POWER
Hypervisor
Linux
i5/OS
z/OS™
PR/SM
Hypervisor
Linux
z/VM
z/990
Server
System z: The Virtualization
and Availability Gold Standard
8 CPU
8 CPU
In 2002: Dynamic Logical Partitioning, enabled dynamic reassignment of workloads
Micro-Partitioning: Minimum 1/10 of a CPU
2 CPU
4 CPU
8 CPU
16 CPU
8 CPU
Logical partitioning enables a more flexible system with partition granularity to 1 CPU
This granularity allows the consolidation to a smaller system vs the hardware partitioning example
Bring in the dynamic logical partitioning capability and you have a system that can support changing computing needs
Hardware Partitioning, like Sun’s Dynamic Domains and HP’s nPars provides a basis for server consolidation.
However, it has limited flexibility (not dynamically reconfigurable), and it doesn’t improve the utilization of the asset
IBM gives you more power with Micro-Partitioning
Designed so you can manage more work with a single system than ever
before and do it . . .
Building on Dynamic LPAR, micro-partitioning takes the partition granularity to 1/10th of a processor
This makes it economical to consider consolidating workloads from smaller under-utilized systems that don’t require a full processor, especially not a full POWER5 processor
By consolidating these workloads, customers can reduce the number of systems and simplify their environment and reduce their management headaches
Saves money over small servers
Enables responsible adaptation to changing workload demands and priorities
And does so automatically, so you don’t have to hire an army of system engineers to monitor and manage it!
At this point, a customer will usually ask about the system management overhead of so many op system images. Be sure to refer them back to the VE suite, which includes Provisioning and System management to automate many of the tasks associated with creating and managing a server image.
— drive higher system utilization
Designed to support both server consolidation and a mixed workload
Mixed Workload
Server 1
Server 2
Server 3
Server 4
Server 5
Server 6
Server 7
Server 8
Server 9
Server 10
Server 11
Server 12
ANIMATION FOR MIXED WORKLOAD ONLY OCCURS ON YOUR ‘CLICK’
Micro-Partitioning provides value in two types of scenarios to drive up utilization and create a more flexible environment
Server consolidation of small underutilized servers
10% CPU slice micro-partitions
Virtualized I/O – shared Ethernet and Fiber Channel Adapters and Virtualized disks
Responsive shared processor LPARs with high system utilization rates
OLTP or high priority workloads can get resources as needed to address unpredictable events with low reaction time – 10s of msecs
Allows for lower priority or batch types of workloads to execute in other LPARs
Mix of OLTP or high priority workloads with batch or lower priority workloads results in high system utilization rates
single physical server
How can I better utilize the servers I have?
For decades, IBM has been using virtualization in the mainframe, which still holds the gold standard. IBM virtualization capabilities can help you greatly simplify the physical infrastructure, increasing asset utilization and flexibility. Thanks to Java and Linux, applications are no longer tethered to specific platforms—they can be rehosted on scale out (blades) or scale up (System i, System z, System p) servers. Important to note that we can not only consolidate similar applications onto larger systems (for example, multiple instances of a database or web server) but also actually collapse whole layers of the physical infrastructure itself—virtualizing the network as well as the servers. This is enabled by the fact that the virtualization technologies in our systems is mature, stable and secure enough to allow you to confidently deploy mixed workloads onto a single system (batch plus transactional; development and production; web facing and core data). This is not something that you can do on Sun, HP, or x86.
IBM’s unique partitioning capabilities enable you to to carve a large server into many small virtual servers, better utilizing resources and reducing cost. We’ve taken the technology that was born on the mainframe and are now exploiting it in our mid-range servers. For instance, in a POWER5 System p, a slice as small as 1/10th of a processor may be allocated to a virtual system.
Virtual LANs and Virtual I/O further break the constraints of physical resources. Network and I/O connections are no longer limited to the number of physical connections or adaptors. This allows you to add connections much more dynamically. Performance can also be improved by using “networks in a box”. When applications communicate between partitions, the network calls remain in the server reducing network latency. And clustering adds many options for high availability.
The net result is substantially higher utilization rates (because mixing workloads allows you to take advantage of the peaks/valleys of different applications), substantially improved performance (because networks are virtualized and communication is at memory speeds), significant reduction in infrastructure complexity, and a large reduction in administrative overhead (fewer things to manage, fewer consoles and tools).
Segue:
Let’s look a little closer at IBM Hypervisor technology
Today…
CPU
resources
Memory
resources
I/O
resources
Hypervisor
Optimize server resources within a single server: CPU, memory, I/O
Drive up utilization, make better use of IT assets: CPU utilization from 5-10%1 to 80-90%; reduce the number of dedicated I/O adapters
Break down functional silos by facilitating workload consolidation and sharing of compute resources
1 Based on IBM Project Scorpion; more information on IBM Project Scorpion can be found at http://www.ibm.com/servers/library/pdf/scorpion.pdf
Key scenarios:
Workload Growth - Growing SMP server workload must be moved to a more powerful SMP server
Server Repair/Upgrade - SMP server needs to be shut down for service or upgrade
Server Consolidation - Two or more operating system instances will be combined onto one SMP server
Workload Balancing - Need to redistribute workloads to optimize QoS and resource utilization
Complete Virtualization
Reach beyond the box—see and manage many virtual resources as one
Dynamically change and adjust across the infrastructure
Workload Growth scenario: Move active micro-partitions to a more powerful SMP server - Live Partition Mobility*
Production
LPARs
Move running UNIX and Linux operating system workloads
from one POWER6 processor server to another!
Reduce impact of planned outages
Relocate workloads to enable growth
Provision new technology with no disruption to service
* All statements regarding IBM future directions and intent are subject to change or withdrawal without notice and represent goals and objectives only. Any reliance on these Statements of General Direction is at the relying party's sole risk and will not create liability or obligation for IBM.
LPAR 1
LPAR 2
LPAR 3
CUOD
Active Partition Migration is the actual movement of a running LPAR from one physical machine to another without disrupting* the operation of the OS and applications running in that LPAR.
* Networked applications may see a short (~2 second) network blip.
Continuous Application Availability
With Live Partition Mobility and Live Application Mobility, planned outages for hardware and firmware maintenance and upgrades can be a thing of the past
Relocate all partitions from one server to another when performing maintenance. Move the partitions back when maintenance is complete
Saves labor
As computing needs spike, redistribute workloads onto multiple physical servers without service interruption
As one server gets overtaxed from a spike in demand, relocate partitions to other servers
Improves QoS delivery
Increases hardware utilization
During non-peak hours, consolidate workloads and power off excess servers
Move partitions off of underutilized servers and then power them off to save electricity using Live Partition Mobility and Live Application Mobility
Reduces datacenter power consumption
IBM APV Benefits
Can help lower the cost of existing infrastructure by up to 72%4
Can increase business flexibility and reduce the complexity to grow your infrastructure
Deployed in production
PowerVM for POWER6
1) Advanced POWER Virtualization (APV) is an optionally orderable feature on IBM System p, 3) All statements regarding IBM future directions and intent are subject to change or withdrawal without notice and represent goals and objectives only. Any reliance on these Statements of General Direction is at the relying party's sole risk and will not create liability or obligation for IBM. 4) “Impact of IBM System p Server Virtualization,” Transforming the IT Value Equation with POWER6 Architecture. International Technology Group, 05/2007. Study methodology: Companies in financial services, manufacturing and retail with $15 Billion+ revenues focusing on UNIX large enterprise environments with multiple, broad-ranging applications. Study compared the cost of the company's workloads running on multiple vendor servers and employing minimal virtualization to the cost of the company's workloads running on p570 (POWER6 processor-based) as well as POWER5+ processor-based servers – all using Advanced POWER Virtualization [APV]. APV is standard on System p5 590 and 595. Other System p servers have the option to add APV except the System p5 185. This cost analysis was performed for financial services, manufacturing and retail example environments with an overall average savings of up to 72% in TCO savings by virtualizing and consolidating on the System p servers. Total Cost of Ownership may not be reduced in each consolidation case. TCO depends on the specific client environment, the existing environments and staff, and the consolidation potential. 5) IBM sales Statistics
PowerVM1
Micro
•
•
Virtual I/O Server
Channel disks
Live Partition Mobility 20073
Move a running partition from one POWER6 processor-based server to another with no downtime
Linux on POWER
Virtualization is a critical requirement and key decision factor for most clients
Nearly 40 years after IBM pioneered virtualization on the mainframe, we continue to expand the reach of virtualization across our systems, including our UNIX and Linux System p servers
IBM delivers real Advanced POWER Virtualization capabilities today that competitors cannot match
1) Mature and field-proven technology: Advanced POWER Virtualization is deployed on 40% of all System p5 CPUs -- it is used by companies large and small for business critical applications in both production and test environments
2) Numerous client case studies as well as research from external analysts has shown reduced TCO of up to 62% by deploying System p Virtualization
3) POWER LPAR development started back in 1997, and has been refined ever since.
4) APV makes it easier to grow your infrastructure to meet changing business needs -- new "virtual" servers can be deployed in a matter of minutes.
Advanced POWER Virtualization (APV) is an optionally orderable feature which includes:
Micro-PartitioningTM – shared resource pools, highly granular partitions
Virtual LAN – high-speed inter-partition communication
Virtual I/O – shared network, storage, fiber channel adapters
POWER Hypervisor™ – mainframe-inspired, enterprise RAS/availability [COMES STANDARD on all System p systems]
Multi-OS Support – AIX 5L, RHEL4, SLES9, i5/OS3
----------------------------------
Up to 10 partitions per physical processor
Up to 254 partitions active at the same time
TWO MAJOR DEPLOYMENT MODELS
Responsive OS images in Shared Processor LPARs with higher utilization
Historically, needed to set aside capacity for unexpected peaks; run at low utilization rates
Rapid increase in capacity (10ms) - high priority workloads get resources when needed; lower priority/batch workloads consume all unused resources
Server consolidation of small underutilized servers using multiple sub-CPU micro-partition
Micro-partitioning allows for multiple partitions to share one physical processor.
A partition may be defined with a processor capacity as small as 10 processor units. This represents 1/10 of a physical processor. Each processor can be shared by up to 10 shared processor partitions. The shared processor partitions are dispatched and time-sliced on the physical processors under control of the POWER Hypervisor.
Micro-partitioning is supported across the entire POWER5 product line from the entry to the high-end systems.
Shared processor partitions still need dedicated memory, but the partitions I/O requirements can be supported through Virtual Ethernet and Virtual SCSI Server. Utilizing all virtualization features support for up to 254 shared processor partitions is possible.
The shared processor partitions are created and managed by the HMC. When you start creating a partition, you have to choose between a shared processor partition and a dedicated processor partition.
When setting up a partition, you have to define the resources that belong to the partition like memory and IO resources. For shared processor partitions, you have to specify the following partition attributes that are used to define the dimensions and performance characteristics of shared partitions:
Minimum, desired, and maximum processor capacity
Minimum, desired, and maximum number of virtual processors
Capped or uncapped
Variable capacity weight
Supported on AIX 5L™ 5.3 and 5.21
Supported on POWER4™ and POWER5™ systems
Workload manager now supports automatically switching resource polices based on time of day - reducing administrator workload and helping to maximize system utilization.
Workload manager can enforce per process cpu, I/O and connect time limits by warning and killing processes that exceed these limits- protecting the system against errant or malicious processes. Also, the administrator can set up per class limits on the number of threads, processes or logins. The administrator can be automatically notified if these thresholds are reached.
"Processor Sets" allow the administrator to specify which physical processors are assigned to a process or class, Memory affinity provides the same function for memory - insuring maximum performance for high performance computing workloads that need to minimize memory latency. Note that processor sets are only applicable to SMP environments, not LPAR.
Additional WLM resources were added to broaden the capabilities to manage diverse workloads.
The dynamic LPAR and CUoD strengthens our total workload management capabilities which includes WLM and LPAR technology.
The LPAR support delivered with the Regatta p690 server last December, offered much greater resource partitioning granularity than partitioning competitive implementations, with minimum partition resources allocations to the single processor or I/O adapter.
In AIX 5.2, dynamic LPAR support will provide the capability to dynamically add/delete partition resources including processors, memory, and I/O adapters without even requiring a reboot. AIX is also enabled for up to 32 partitions but no hardware supports that configuration as of the announce date.
The dynamic reconfiguration APIs provide applications with the ability to detect and adjust to changes in resources available in a partition. For example - Oracle plans to take advantage of this feature in 2003.
Dynamic Capacity on Demand allows the client to "turn on" unused processors as there workload increases. This provides non-disruptive (no ipl reqd.) capacity upgrades.
Note: CUoD only supports processors in 5.2 - memory will be added later.
Hot Sparing -For clients using CUoD, they get addition reliability capability though having the system automatically substitute an unlicensed processor for on that is failing.
LPARs share a pool of physical processors
each LPAR is given a "share"of the physical processing power within a pool
software fault isolation is maintained for shared-processor LPARS
more than 100 shared-processor LPARs in a single system
Supports the efficient use of resources
LPARs (AIX images) yield idle processor cycles
no need to reserve dedicated resource to deal with spikes in capacity requirements
LPAR spikes can be dealt with from the shared pool
Dedicated processor partitions continue to be supported
Virtual Ethernet
supports in-memory network connections between LPARs
reduces the need for physical Ethernet adapters for some LPARs, except for external connections
Virtual Disk
reduces the need for dedicated physical disk resources
essential for shared processor LPAR support where there may be lots of LPARs
hosted through separate VIO AIX LPARs
------------------------------------
Virtual Ethernet
The Virtual Ethernet enables inter-partition communication without the need for physical network adapters in each partition. The Virtual Ethernet allows the administrator to define in-memory point to point connections between partitions. These connections exhibit similar characteristics, as high bandwidth Ethernet connections supports multiple protocols (IPv4, IPv6, and ICMP). Virtual Ethernet requires a POWER5 system with either AIX 5L V5.3 or the appropriate level of Linux and a Hardware Management Console (HMC) to define the Virtual Ethernet devices. Virtual Ethernet does not require the purchase of any additional features or software, such as the Advanced Virtualization Feature.
Virtual Ethernet is also called Virtual LAN or even VLAN, which can be confusing, because these terms are also used in network topology topics. But the Virtual Ethernet, which uses virtual devices, has nothing to do with the VLAN known from Network-Topology, which divides a LAN in further Sub-LANs.
Enables inter-partition communication.
Physical network adapters are not needed.
Similar to high-bandwidth Ethernet connections.
Supports multiple protocols (IPv4, IPv6, and ICMP).
No Advanced POWER Virtualization feature required.
POWER5™ Systems
Hardware management console (HMC)
Virtual SCSI
Virtual SCSI is based on a client/server relationship. The virtual I/O server owns the physical resources and acts as the server. The logical partitions access the virtual I/O resources provided by the virtual I/O server as the clients. The virtual I/O resources are assigned using an HMC.
Often the virtual I/O server partition is also referred to as hosting partition and the client partitions as hosted partitions.
Virtual SCSI enables sharing of adapters as well as disk devices.
To make a physical or a logical volume available to a client partition, it is assigned to a virtual SCSI server adapter in the virtual I/O server partition.
The client partition accesses its assigned disks through a virtual SCSI client adapter. It sees standard SCSI devices and LUNs through this virtual adapter.
Virtual SCSI resources can be assigned and removed dynamically. On the HMC, virtual SCSI target and server adapters can be assigned and removed from a partition using dynamic logical partitioning. The mapping between physical and virtual resources on the virtual I/O server can also be done dynamically.
This chart shows an example where one physical disk is split up into two logical volumes inside the virtual I/O server. Each of the two client partitions is assigned one logical volume, which it accesses through a virtual I/O adapter (vSCSI Client Adapter). Inside the partition, the disk is seen as normal hdisk.
Live Partition Mobility
Power6 System #2
Power6 System #1
Finish the migration and remove the original LPAR definitions
Once enough memory pages have been moved, suspend the source system
Start migrating memory pages
Create virtual SCSI devices
Validate environment for appropriate resources
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
Storage
Subsystem
A
HMC
A
vscsi0
en0
(if)
ent1
en0
(if)
ent1
Each Workload Partition obtains a regulated share of system resources
Each Workload Partition can have unique network, filesystems and security
Two types of Workload Partitions
System Partitions
Application Partitions
Each Workload Partition is a separate administrative and security domain
Shared system resources
Workload
Partition
Application
Server
Workload
Partition
Web
Server
Workload
Partition
Billing
Workload
Partition
Test
Workload
Partition
BI
Improved administrative efficiency by reducing the number of AIX images to maintain
Virtualization with fewer AIX images
Leverage a single AIX image for multiple workloads
Simple to use
Improved server efficiency through consolidation
Good resource isolation – sufficient for many workloads
Separate security control for each WPAR
WPARs improves benefits of consolidating workloads by reducing administration expenses for excess AIX images.
Application mobility offers new workload management and outage avoidance capabilities
WPARs are part of the System p Virtualization solution
Complements existing Virtualization offerings and can be used in combination with LPAR and VIOS
Runs on reliable, high performance IBM System p servers
AIX reliability, availability and serviceability features are a superior operating system platform for software virtualization solutions like WPARs
LPARs and AIX Workload Partitions are complementary technologies and can be used together
LPAR
Asia
LPAR
LPAR
EMEA
LPAR
Americas
VIO
Server
Billing
This slide shows the use of Workload Partitions within Dedicated LPARs and MicroPartitions. The leverages the best
capabilities of each technology.
For example, the Finance LPAR needs the highest degree of isolation and the workload demands
a dedicated set of processor resources.
The Planning workload also requires a dedicated number of processors, but there are two main work areas within the Planning
function (perhaps Strategic Planning and Operations Management) that we would like to combine within the same system image
using AIX Partitions to keep the performance resources and administration separate.
Each WPAR within each Logical Partition offers separate administration, security and management.
Reduced AIX System Administration
Reduces install and updating of AIX, monitoring, backup, recovery etc.
Application Encapsulation, monitoring and control
Treated Application/WPAR as an isolated unit
Control create/remove, start/stop, checkpoint/resume
Monitoring at application level plus backup/recovered
Duplicated application for test, dev, rollout and scale out (multiple copies of same app)
Rapid environment creation of a new application
Creation takes few SysAdmin seconds + a few minutes of machine time
Separated System Admin/Security at applications level
Global SysAdmin can hand-off to Application Admin many System Admin tasks
Yet maintain global level security via WPARs and integrated Role Base Access Control
Simple to move an application to a different machine
For performance balancing across machines
For reduced time to move an application, near-zero downtime
RBAC: Role Base Access Control
Workload
Partition
QA
Move a running Workload Partition from one server to another
for outage avoidance and multi-system workload balancing
Workload
Partition
e-mail
Works on any hardware supported by AIX 6 including POWER5
Workload
Partitions
Manager
Policy
Workload
Partition
Billing
Application Mobility is an optional capability that will allow an administrator to move a running WPAR from one system to another using
advanced checkpoint restart capabilities that will make the movement transparent to the end user.
Application Mobility – How?
Checkpoint
”Photo snapshot’’ of a running application in a WPAR into a “statefile” on disk
Restart
Captures the entire state
IPC
Network
NFS Server
Live Application Mobility – move a running AIX 6 application …
… From one server to another
Workload Isolation
Resource Flexibility
Workload
Partitions
or later
Live Application Mobility
Live Partition Mobility
IBM provides a broad range of flexible resource management options for our clients. With different trade-offs between
each approach.
Individual systems (not shown) provides the highest degree of Isolation but each system must be managed separately and there is no easy way to adjust the amount of resources dedicated to the workload
Workload manager provide for a high degree of flexibility for workloads consolidated within a single system, and leverages a single operating system image, but requires a high degree of skill from the administrator to implement.
Dedicated processor partitions provide the most isolation and is easier to implement than Workload Manager type solutions, but while adjusting processor resources is relatively easy (compared to standalone systems), it is largely an manual process
MicroPartition LPARs automates adjusting the processor resources to the workload but requires each LPAR has a separate AIX instance to manage.
AIX Workload Partitions offers the easiest administration since a common AIX operating system can support many AIX Partitions, but the level of isolation is lower than with MicroPartitions or Dedicated Process LPARs
Regular H/W Change
Active partition Mobility
Active Application Mobility
Inactive Application Mobility
Simplified
Scale-up
IBM
IBM
Build on world-class hardware availability and focus on improving OS/application availability
Predict and reduce unplanned outages with mainframe-inspired system enhancements
Maintenance eliminate/reduce planned outages by enhancing concurrent HW and OS
Enable HA while reduce cost
Combine HA and Test
Foundation
App 1
App 2
App 3
App 1
App 2
App 3
How Dual UNIX Enterprise Systems scale up and adopt new tech
Shared
Disk
Upgrade production system (p5-595) to larger system (p5-595+ or POWER6)…
App 1-T
/ AP LPARs
Test 1
Test 3
Test 2
HA 6
HA 4
HA 5
App 5
App 6
Business Grows
Workload full
Business Grows and workload full
Test 1
Test 2
Test 3
App 4
Test 1
Test 3
Test 2
App 1
Dispersed locations
New and existing applications
24/7 demand for access
: IT
Databases
Applications
Web
IBM
IBM
Virtualization capability
Partition mobility
Supports movement of running applications for mission-critical workloads
System scalability
Helps improve TCO by consolidating more workloads
Dynamic Logical Partitioning
Security/fault isolation
CAPP/EAL 4+
Support for dedicated I/O
Capacity on Demand integration
Add capacity when/where needed, turn it off when not required
Partitions per CPU
Management flexibility
So – let’s talk more about how different consolidation and virtualization is from IBM than other UNIX platforms.
We are the only platform that supports all critical consolidation requirements with ONE virtualization technology. You don’t have to select a different solution for specific requirements. Advanced POWER Virtualization works for all of these specific requirements – and all on the same server!
IBM PowerVM
[1] Based on IBM Study. The virtualized system count and energy savings were derived from several factors: A performance factor of 2.79X was applied to the virtualization scenario based on SPEC® results source: www.spec.org. System p 570 (16-core, 8 chips, 2 cores per chip, 4.7 GHz) SPECint_rate2006: 466, as of 8/20/2007; HP Integrity rx7640 (16-core, 8 chips, 2 chips per core, 1.6 GHz) SPECint_rate2006: 167 as of 8/20/2007. A virtualization factor of 3X was applied to the virtualization scenario using utilizations derived from studies conducted by Alinean available at http://www-935.ibm.com/services/us/cio/optimize/opt_wp_ibm_systemp.pdf. A factor of 2X was used to represent the ability to install two 16-core System p 570 systems in a single rack. Power consumption figures of 5600 W for the IBM System p570 and 2128 W for the HP rx7640 were based on the maximum rates published by IBM and HP, respectively. The HP document with the rx7640 power requirement is “QuickSpecs HP Integrity rx7640 Server” dated August, 2007. I t can be found at http://h18000.www1.hp.com/products/quickspecs/12470_div/12470_div.pdf. Air conditioning power requirement estimated at 50% of system power requirement. Energy cost of $.0928 per kWh is based on 2007 YTD US Average Retail price to commercial customers per US DOE at http://www.eia.doe.gov/cneaf/electricity/epm/table5_6_b.html as of 8/20/2007. Datacenter floor space cost was estimated as of 8/20/2007 based on Alinean, Inc.’s ROI Analyst software. The reduction in floor space, power, cooling and software costs depends on the specific customer, environment, application requirements, and the consolidation potential. Actual numbers of virtualized systems supported will depend on workload levels for each replaced system.[2] Numerous case studies for clients who have achieved these results are available at http://www.ibm.com/software/success/cssdb.nsf/advancedsearchVW?SearchView&Query=(Virtualization)+AND
+[WebSiteProfileListTX]=eserverpseries&site=eserverpseries&frompage=ts&Start=1&Count=30&cty=en_us [3] “Impact of IBM System p Server Virtualization,” Transforming the IT Value Equation with POWER6 Architecture. International Technology Group, 05/2007. Study methodology: Companies in financial services, manufacturing and retail with $15 Billion+ revenues focusing on UNIX® large enterprise environments with multiple, broad-ranging applications. Study compared the cost of the company's workloads running on multiple vendor servers and employing minimal virtualization to the cost of the company's workloads running on System p 570 (POWER6 processor-based) as well as POWER5+ processor-based servers - all using Advanced POWER Virtualization [APV]. APV is standard on System p5 590 and 595. Other System p servers have the option to add APV except the System p5 185. This cost analysis was performed for financial services, manufacturing and retail example environments with an overall average savings of up to 72% in TCO savings by virtualizing and consolidating on the System p servers. Total Cost of Ownership may not be reduced in each consolidation case. TCO depends on the specific client environment, the existing environments and staff, and the consolidation potential.
The leading virtualization platform for UNIX, Linux and i5/OS clients
Go Green & Save
Potentially cut energy costs by up to 65%1 through server consolidation
Manage Growth, Complexity & Risk
Reduce server sprawl and administration costs while improving availability and application performance2
Realize Innovation
Potentially reduce operational costs by up to 72%3 and put your savings into new business opportunities
Slide is self-explanatory.
Core Intel Itanium 2) 8842169.1 71.4
Hewlett-Packard Company
Core Intel Itanium 2) 1616821174 181
processor X5365) 8824162.8 78.2
processor X7350) 1616441106 116
98.7
Sun Microsystems Sun SPARC Enterprise M4000 16842267.2 70.9
Sun Microsystems Sun SPARC Enterprise M5000 3216822133 140
Sun Microsystems Sun SPARC Enterprise T5220 63818857.9 62.3
Test Sponsor System Name
Core Intel Itanium 2) 8842194.7 102
Core Intel Itanium 2) 1616821186 201
processor X5460) 88241112 137
processor X7350) 1616441175 209
Sun Microsystems Sun Fire X4600 M2 1616821131 157
Sun Microsystems Sun SPARC Enterprise M4000 16842268.6 81.6
Sun Microsystems Sun SPARC Enterprise M5000 3216822134 158
Sun Microsystems Sun SPARC Enterprise T5220 63818873.0 78.5
0
20
40
60
80
100
X2200
M2
rx2660DL185p520T5120X4150rx6600DL360DL585
SPECfp_rate2006
ProLiant DL185 G5 (3.0 GHz AMD Opteron 2222) 4422155.0 61
HP Integrity rx2660 (1.66GHz/18MB Dual-Core Intel Itanium) 4422258.1 62.8
IBM System p 520 422290.4
Sun Fire V490 8842171.7 78
Sun SPARC Enterprise T5120 63818873.0 78.5
HP Integrity rx6600 (1.6GHz/24MB Dual-Core Intel Itanium 2) 8842194.7 102
Sun Fire X4150 8824191.3 102
Proliant DL585 G2 (AMD Opteron 8222SE) 8842196.1 108
ProLiant DL360 G5 (3.16 GHz, Intel Xeon processor X5460) 88241112 138
System Name CopiesCoresChips
HP Integrity rx2660 (1.66GHz/18MB Dual-Core Intel Itanium) 4422254.5 55.8
ProLiant DL185 G5 (3.0 GHz AMD Opteron 2222) 4422151.9 56
IBM System p 520 4222 79
Sun SPARC Enterprise T5120 63818857.9 62.3
Sun Fire X4150 8824158.8 63.1
HP Integrity rx6600 (1.6GHz/24MB Dual-Core Intel Itanium 2) 8842169.1 71.4
ProLiant DL360 G5 (3.16 GHz, Intel Xeon processor X5460) 8824170.3 78.5
Proliant DL585 G2 (AMD Opteron 8222SE) 8842192.6 98.7

ibm activitydowibm nload 9

Documents