“Virtualization and Grids: What’s Next?” · Virtualization and Grids • Increasingly being used with respect to multiple platforms • Still some “seamless” interoperability

“Virtualization and Grids: What’s Next?”

10/17/2007

J.S. Hurley, Ph.D., Sr. ManagerD. Shaw, Lead Grid Architect

Distributed Software and Systems Integration

OGF21October 2007BOEING is a trademark of Boeing Management Company.

Copyright © 2007 Boeing. All rights reserved.

Engineering, Operations & Technology | Phantom Works E&IT | Mathematics and Computing Technology

Agenda

• Overview & Premise

• Dilemma

• IT View (Boeing Perspective)

• Virtualization and Grids

• Infrastructure Ecosystem

• Advantage: Parallel Apps

• Limitations/Benefits

• Conclusion


Overview

Ongoing progress in Grid technologies have enabled organizations to share and manage their resources beyond the earlier expectations of IT and user groups.

The growth and evolution of Virtualization has enabled organizations to consolidate resources, especially in data center domains producing in some cases quite noticeable cost savings.


Premise

As we continue to see improvements in processing, networking, information management and middleware, the relationships and roles of Grids and Virtualization become increasingly blurred.

In this presentation, we will discuss possibilities of convergence between the two technological areas and suggest possibilities for the future.


Dilemma

• Grids and Virtualization share much in common, including:• Continuing struggles with definitions. Largely a matter of perspective

and audience• Both seem to have noteworthy possibilities especially within an

organizational or enterprise context

• Grid solutions may likely incorporate virtualization to address aspects of resource utilization

• Within Grids workload management can be virtualized • Clearly they highly complement each other in addressing

critical infrastructure needs of the enterprise (especially within a global context)

• However,….• In spite of the similarities, its OK not to equate them


The “IT” View (Boeing Perspective)

• Must “seamlessly” connect our sites, suppliers and partners around the world. • Share resources• Unified management and monitoring• Single source for reporting and accounting• Dynamic information and data transactions

– (Time zone differences no excuse)

• Misconceptions...• Restricted to a particular class of applications (R&D, Production,

Operations, etc. )• Bandwidth and Resource unlimited• All infrastructure investments are costly – Grids dispel this one!• Resource ownership – “This is mine and you can’t touch it!”• Single, static monolithic solution is best• “Throw more hardware at it, that will solve it”• “We must have Common processes and resources”


Virtualization and Grids

• Increasingly being used with respect to multiple platforms• Still some “seamless” interoperability issues to be resolved, but

definite progress in the right direction

• Virtualization• Open source and flexible adaptation

(i.e., multiple platforms) emphasis is very welcomed by broad user communities.

• Increases resource utilization • Enable strategic deployment of resources• Can potentially save cost of porting applications across diverse

platforms– Hardware, storage, data, etc.

• Data and storage aspects and issues of increasing interest• High level applications (e.g., ontology-based) can require more

abstraction layers


Infrastructure Ecosystem

• Hardware• Clusters/Mainframes/Processors/Storage• Racked for departmental and 1u’s for budget conscious• Blades in datacenter for effective

power management • High availability and redundancy for

critical mission applications and services• Multi-core may increase performance / cost

• Middleware• Provides load balancing for even workload distribution

• License server can enhance resource distribution and ensure regulatory compliance

• Grid middleware fosters user and site collaborations while accommodating nuances of diverse and broad application base

• Networking• Latency and Real-time interactions directly related to BW capacity

• Critical in Network – centric approaches


Advantage: Parallel Applications

• Grids and Virtualization can significantly improve performance by providing an advanced infrastructure that promotes parallel workload distribution

• “Parallelizing” apps can significantly increase performance for legacy applications with minimal code modification

• Virtual machines and interpreters provide built-in parallelism to high level applications or services

• A service-based or oriented approach is a natural progression in middleware development which takes advantage of a parallel , distributed approach

• Many advancements in development tools and MPI stacks have enhanced ease-of-use and performance


Limitations vs. Benefits

PerformanceSecurityDenial of ServiceDeploymentReduced TCOScalabilityService-orientedDynamicHeterogeneous PlatformsHigh Availability/High Reliability/High ThroughputWorkload balancingCommodity limitedSpecialized Requirements


Conclusion

• Grids and Virtualization can provide significant inroads to building the viable global enterprise infrastructure necessary to accommodate diverse user needs and demands.

• Much of the reluctance and hesitance is associated with cultural misconceptions and hard line philosophies.

• The Grid and Virtualization communities, however, must bear a large part of the responsibility because there remains a lack of clarity in key technology areas and the rationale for using its solutions

• A more synergistic approach between the communities would well serve us and the broad user community in desperate need of solutions

• We must move beyond definitions and “siloed” approaches to the benefit of the diverse user community around the globe


Acknowledgements

• M. Linesch, HP

• S. Crumb, OGF

• C. Doninger, SAS

• The Boeing Company

• R. Benson

• D. Dell

Copyright © 2007 Boeing. All rights reserved. 12


13Copyright © 2007 Boeing. All rights reserved.

Documents

“Virtualization and Grids: What’s Next?” · Virtualization and Grids • Increasingly being used with respect to multiple platforms • Still some “seamless” interoperability