Download zGryphon RAS - Enterprise Computing Community

Systems and Technology Group
The New zEnterprise™ Systems & Testing
Paul A. Wojciak
Mike Duron
Nancy Finn
© 2012 IBM Corporation
Systems and Technology Group
Agenda
 zEnterprise Value Proposition and Testing Challenge
 zEnterprise z196 and z BladeCenter® Extension (zBX) Overview
 Test Approach and Challenges
 In Summary
2
© 2012 IBM Corporation
Systems and Technology Group
System zEnterprise Testing Challenge
zEnterprise™ and zEnterprise BladeCenter Extension bring
together:
– Traditional mainframe compute resources
– Distributed cost optimized compute engines
 Mainframe quality of service and RAS expectations
– Reliable
– 24x7 solution availability
– Service and maintenance concurrent to system operation
zEnterprise
3
© 2012 IBM Corporation
Systems and Technology Group
zEnterprise z196 and z BladeCenter Extension Overview
 z196 and z114 zEnterprise systems
 Unified Resource Manager (zManager)
 z BladeCenter Extension with:
– POWER7® Blades running AIX®
– System x® Blades running Linux® and Windows®
– Websphere® DataPower® Integration Appliance XI50 for zEnterprise
Comprise an ensemble with associated CPCs, zBXs, network and
storage infrastructure
 z operations management purview of heterogeneous multi-tier compute
solution resources
 Workload concept facilitates visualization and actions against virtualized
compute resources aligned with business objectives
 zManager driven performance and energy monitoring and management
4
© 2012 IBM Corporation
Systems and Technology Group
System z Hosts
Linux
Linux
z/TPF
on
on
z/OS z/VSETM
System
z
System
z
AIX on
POWER7
Windows
on
System x
z/VM
Blade Virtualization
Blade Virtualization
Linux
on
System x
Future Offering
Select IBM Blades and Optimizers
DataPower
with Unified Resource Manager
System z Hardware Management Console (HMC)
zEnterprise and zBX Hierarchical View
Blade
Virtualization
System z PR/SM™
z HW Resources
Blade HW Resources
Support Element
zBX
Private data network (IEDN)
Unified Resource
Manager
Customer Network
5
Private Management Network INMN
Private High Speed Data Network IEDN
Customer Network
© 2012 IBM Corporation
Systems and Technology Group
Test Approach – zEnterprise zBX Test Teams by Discipline
Team
Ensembles
Largest Ensemble
Core Functions
z114
z196
Solution
Test
Networking
z196
z196
• IEDN functional stress
z114
• Operating System functional stress
z196
• Comm Server
• Dynamic I/O
• eBoD, Crypto/Security, Coupling
• FICON, FCP, STP
Install &
Upgrades
• Virtualization boundaries
• Multiple Sysplexes
• Customer modeled workloads
• Performance Management
z196
eHMC
z196
Performance
z196
RAS
z114
HMC
• Installation and entitlement
• Upgrades
• Mfg kit testing
6
z196
• zManager core
functions and stress
• Change Management
• Error injection, error
handling, reporting, and
end to end service
z196
• Capacity, throughput
analysis – speeds and
feeds
© 2012 IBM Corporation
Systems and Technology Group
Test Approach – Schools of Software Testing
Those followed by Test Teams during zEnterprise Project
 Analytic School
– Sees testing as rigorous and technical with many proponents in academia.
– Requires detailed specifications for test plan generation. Asks: What techniques should we use?
 Standard School
– Sees testing as a way to measure progress with emphasis on cost and repeatable standards.
– Test plans based on covering requirements and mid-test plan changes are resisted.
– Asks: How can we measure whether we’re making progress? How do we know when we’re done?
 Quality School
– Emphasizes process, policing developers with test acting as the gatekeeper. Requirements based test
plans preferring quality assurance over testing.
– Asks: Are we following a good process?
 Context-Driven School
– Emphasizes people, seeking bugs that stakeholders care about. Test plans adapt based on results.
Exploratory testing.
– Asks: What testing would be most valuable right now?
 Agile School
– Uses testing to prove that development is complete; emphasizes automated testing.
– Asks: Is the story done?
7
Source: B. Pettichord, Schools of Software Testing (2007), www.pettichord.com,
Available at:
http://www.prismnet.com/~wazmo/papers/four_schools.pdf Accessed: May 30, 2012.
© 2012 IBM Corporation
Systems and Technology Group
Test Approach – zEnterprise and zBX Test Selection
 Functional test selection based on product specification (Black Box method)
–
–
–
–
–
Test cases across all test disciplines
Reflect all use cases
Build the biggest, test the boundaries
Run the environment as a customer
Presumption of predictable behavior for inherited components (Implicitly tested)
 Structural test selection based on knowledge of product internals (White Box method)
–
–
–
–
Installation and entitlement sequences
Change management – firmware update variations
zManager acquisition of virtualized resource state for rendering on user interface
Energy management state interrogation and control
 Exploratory test execution by subject matter experts
– z/VM interaction with zManager, SMAPI command usage, setup and debug message clarity
– DataPower integration into zManager interface, user roles and security
 Solution test
– Bring all aspects of the product set together with operating systems, middleware, and multi-tier
applications modeled on customer environments
8
© 2012 IBM Corporation
Systems and Technology Group
IBM zEnterprise System – RAS Testing To Meet Customer Requirements
A test team, test process, and test environments to verify fault tolerance
Monitor, Control, with Integrated RAS:
zEnterprise Unified Resource Manager
Rock Solid, Availability
Measured in Decades:
IBM zEnterprise™ 196
(z196)




9
Reliability focused from
wafer test through final
system fulfillment
Availability verified with
fault injection for errors
throughout all
hardware components
and layers of the
software stack
Customer modeled
environments backing
all RAS tests
Serviceability, proven
fully concurrent, endto-end
 Testing management of resources, verifying
IBM System z® qualities of service across
workloads
 Assuring reliable recognition, isolation,
reporting and repair of ensemble resources by
zManager
Mainframe Test Approach:
IBM zEnterprise
BladeCenter® Extension
(zBX)
 Application of RAS test
techniques to IBM
POWER7®, IBM x86
blades under a variety of
AIX®, Linux , and
Windows® applications
 DataPower® integration
and resilience testing
 Verification of SAN, LAN,
power, cooling redundancy
for workload availability
eHMC
Websphere®
DataPower®
 Error handling, service and
code update management
through System z
infrastructure
© 2012 IBM Corporation
Systems and Technology Group
Test Approach – zBX RAS Tests and Methods
zBX Design Area
Specification Derived RAS Tests
Test Technique Examples
IEMN, IEDN, SAN
Verify redundancy keeps networks alive
during errors, code update, and repair.
Cable pulls, soft error injection for
error simulation, use defective
devices, bouncing TCP/IP
stacks
Chassis Power and Cooling
Verify redundancy keeps BladeServers
alive with no thermal events.
Verify that repairs are concurrent.
Stop fan rotation, disconnect AC
input, use defective components
BladeServer – POWER7,
x86, DataPower
Verify error handling, reporting, and
repair.
Verify availability provided by redundant
BladeServers within a workload.
Soft error injection for error
simulation, use defective
components
Support Processors and
ensemble Hardware
Master Console (eHMC)
Verify redundancy provides availability
during error handling and code
updates.
Manually reset support processor,
create loss of connectivity,
failover to Alternate HMC
Hypervisors (PowerVM,
KVM, z/VM)
Assure error recognition, isolation,
reporting, and diagnostic data collect.
Manual reset of hypervisors,
overlay private store, virtual
guest and device errors
zManager
Test inherent reliability, fault recognition,
and messaging for range of services.
System resources stressed to
implemented limits while
programming errors simulated
10
© 2012 IBM Corporation
Systems and Technology Group
Test Approach – zBX Solution Test Mission and Benefits
 Solution test
– Bring all aspects of the product set together with operating systems, middleware, and multi-tier
applications modeled on customer environments
 High Level Checklist
– Scaling the virtual environment towards the defined limits
– Evaluating the integration of all hardware and code components
– Deploying real workloads modeled after production environments
 Workloads with DB2 serving on z
– Daytrader - benchmark application simulating an online stock trading system.
– Bookstore - internal IBM workload that simulates a multi-tier online Book Retail environment.
– z Platform Evaluation Test online transaction processing workloads exploiting: CICS, DB2, IMS, IRLM,
MQ, RLS, and WebSphere Application Server which are all Parallel Sysplex data sharing.
11
© 2012 IBM Corporation
Systems and Technology Group
Test Approach – zBX Solution Test Environment
Logical depiction of virtual servers.
Actual CPC and zBX ensemble
memberships shown.
12
© 2012 IBM Corporation
Systems and Technology Group
Test Challenges

Needed test addressing breadth of zManager capabilities  Solution Test
– Assembling skills across the test organization

Commodity component behavior predictability
1.
2.
3.
4.

Reliable messaging between zBX management modules (HW) and system z support element
Certainty of firmware update (Multiple methods, inconsistent results)
BladeServer installation (Dependent on 1 and 2)
SAN error isolation and diagnostics
Overlapping test phases
– Sequential development model (Design Code Unit Test Function Test System/Solution Test)
– Late deliveries, incomplete prior test phases
– System and solution testers run function tests first

How to train product deployment teams?
– Bring folks to Poughkeepsie, NY test lab
– Perform repeated mock installations
– Deploy zEnterprise and zBX in internal IBM production locations
13
© 2012 IBM Corporation
Systems and Technology Group
In Summary
zEnterprise brings System z management thoroughness to cost optimized compute
resources
 Test Mentality - 24x7 Enterprise Customers
 Test approach based on combination of recognized methods
 RAS focus pervasive throughout
 Solution Test environment to push the boundaries and insure customer modeled
behaviors
 Early internal production account experience
 Result: zEnterprise and BladeCenter Extension Product rollout quality objectives
met
14
© 2012 IBM Corporation
Systems and Technology Group
Thank you for your time today
For more information:




http://www-03.ibm.com/systems/z/hardware/zenterprise/z196.html
http://www-03.ibm.com/systems/z/hardware/zenterprise/zbx.html
http://www-03.ibm.com/systems/services/platformtest/servers/systemz_mission.html
http://www-304.ibm.com/support/docview.wss?uid=isg2b86a60368d4c054c852576c600736dca
References:



P. Jorgensen, Software Testing A Craftsman’s Approach, 3rd ed., Auerbach, 2008, pp.7-9, 353
B. Beizer, Software Test Techniques, 2nd ed., Van Nostrand Reinhold, 1990.
B. Pettichord, Schools of Software Testing (2007), www.pettichord.com, Available at:
http://www.prismnet.com/~wazmo/papers/four_schools.pdf Accessed: May 30, 2012.
Contact:
 Paul Wojciak
 845 435 7064
 [email protected]
15
© 2012 IBM Corporation
Systems and Technology Group
Trademarks and notes
IBM Corporation 2012
 IBM, the IBM logo and ibm.com are registered trademarks, and other company, product or service names
may be trademarks or service marks of International Business Machines Corporation in the United States,
other countries, or both. A current list of IBM trademarks is available on the Web at “Copyright and
trademark information” at www.ibm.com/legal/copytrade.shtml
 Adobe, the Adobe logo, PostScript, the PostScript logo, Cell Broadband Engine, Intel, the Intel logo, Intel
Inside, the Intel Inside logo, Intel Centrino, the Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep,
Itanium, IT Infrastructure Library, ITIL, Java and all Java-based trademarks, Linux, Microsoft, Windows,
Windows NT, the Windows logo, and UNIX are trademarks or service marks of others as described under
“Special attributions” at: http://www.ibm.com/legal/copytrade.shtml#section-special
 Other company, product and service names may be trademarks or service marks of others.
 References in this publication to IBM products or services do not imply that IBM intends to make them
available in all countries in which IBM operates.
16
© 2012 IBM Corporation