No-Compromise Virtualization: Making Your Data Center Cloud Efficient, Scalable, and Flexible Michael Ramchand Platform Technical Director Oracle EMEA

No-Compromise Virtualization:Making Your Data Center Cloud Efficient, Scalable, and Flexible

Michael RamchandPlatform Technical DirectorOracle EMEA

Duncan HardiePrincipal Product ManagerOracle Solaris Product Management

October 2nd, 2014

Copyright © 2014, Oracle and/or its affiliates. All rights reserved. |

Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | Oracle Confidential – Internal/Restricted/Highly Restricted 3

Agenda

Designing a Consolidated Infrastructure

Characteristics of Virtualization Technologies

Evaluation of Oracle’s Virtualization Technologies

Advantages of a layered approach

Conclusion

1

2

3

4

5


Agenda





Conclusion

1

2

3

4

5


Where are you spending your IT Budget?

• Simply virtualizing reduces the H/W costs.

• (and it may increase or decrease the S/W costs depending on who you buy it from.)

How can we use Datacenter Consolidation to materially reduce the Implementation and Running Costs?

Hardware10%

Software12%

Facilities7%

Implementation31%

Running costs40%

5


Operational / Management

• Shrink your running costs by– Reducing the number of managed

objects– Simplified Management– Reduced Maintenance– Standardization of the stack– Single stack support

Hardware10%

Software12%

Facilities7%

Implementation31%

Running costs40%

6


Virtualization Increases Datacenter Efficiency Consolidate workloads on a flexible and scalable platform

Current Servers are too big for many existing workloads.Combining applications allows us to fully utilize these servers.Requires application isolation for performance and security.Ultimately, this is about reducing the cost of running those applications.

7


Oracle’s Virtualization Tools

• Application Multi-tenancy–Oracle DB, multiple instances, pluggable databases–Weblogic, multiple apps

• Oracle Solaris Zones–O/S level virtualization– Zero overhead

• Oracle VM Server for SPARC (formerly known as LDoms)– Industry's best consolidation ratios– Secure & flexible virtualization

• Physical Domains

8


Oracle’s Virtualization Tools (for SPARC)

• Application Multi-tenancy• Oracle Solaris Zones• Oracle VM Server for SPARC• Physical Domains

Which one should I use?

ALL OF THEM!

9


Oracle’s Virtualization Tools (for SPARC)

• Application Multi-tenancy• Oracle Solaris Zones• Oracle VM Server for SPARC• Physical Domains

Which one should I use first?

START AT THE TOP

10


A Consolidation Philosophy

• Maximize Operational Efficiency– Reduce the number of objects to be managed– Consolidate as high up the stack as possible

• Maximize Workload Efficiency– Avoid Virtualization overhead where possible– Increase your workload to payload ratio

11


Agenda





Conclusion

1

2

3

4

5


The Seven Characteristics of Virtualization

• Security Isolation• Resource Isolation• Efficiency• Availability• Serviceability• Flexibility• Agility

A method for comparing the qualities of different virtualization technologies



• Siloed environments relied on physical separation to enforce security• Shared environments require new mechanisms to

ensure security• Access control mechanisms and encryption play a

key part.• Existing Security policies may need to be re-written

1: Security Isolation



• Siloed environments used dedicated hardware to guarantee access to resource• Shared environments allow better use of spare

capacity• Workloads should still be guaranteed minimum

resource levels• Workloads should be constrained from exceeding

their maximum resource levels

2: Resource Isolation



Virtualization usually introduces overhead• Hypervisor Overhead• Virtualized Resource Overhead• O/S OverheadVirtualization is sometimes used to address scalability issues either at the Hardware, Operating System or Application level• SPARC, Solaris and most Oracle applications

demonstrate linear scalability

3: Workload Efficiency



• Consolidated workloads suffer a higher impact due to infrastructure failure• An individual workload within the pool may not

require High Availability (HA), but the combination of several workloads does• HA solutions usually provide tools that aid

manageability• Clustering of some type is required.• Live Migration is not a substitute for clustering.

4: Availability



• Consolidated workloads suffer a higher impact due to infrastructure maintenance• Negotiating a joint outage window across multiple

business owners can be extremely difficult• The number of service events that require an outage

should be as low as possible• In cases where an outage is unavoidable, workloads

should be able to be moved with the minimum of disruption

5: Serviceability



• Workloads typically have resource utilization patterns that vary over time. They may also grow or shrink over longer periods of time• It is therefore important to be able to alter the

resource allocation of these workloads• Ideally, these should be automatic, dynamic and

immediate, so that idle workloads do not reserve resources, and busy workloads can get them

6: Flexibility



• In a consolidated infrastructure is is often useful to move workloads between servers within a resource pool• Agility is a measure of workload migration between

physical servers and takes into account:– Ease/Simplicity of migration– Impact of migration– Speed of migration

7: Agility


Agenda





Conclusion

1

2

3

4

5


Oracle Virtualization Technologies

• Physical Domains– Electrically isolated domains

• Oracle VM Server for SPARC– Logically isolated domains, with several deployment models

• Solaris Zones–O/S based virtualization, with several zone types

All recognized as hard partitions for Oracle licensing purposes

SPARC/Solaris Based Technologies Native functionality at no additional

cost



PDoms enable electrically isolated server hardware, which means administrators can isolate hardware or security faults and constrain their exposure to each domain. The result is a superior level of system availability and security. This technology is available in the SPARC M5-32 and SPARC M6-32 servers Physical Domains

Physical Domains (PDoms)


Oracle Virtualization TechnologiesOracle VM Server for SPARC

Isolated OS and applications in each logical (or virtual) domain

Firmware-based hypervisor

Each logical domain runs in dedicated CPU threads and RAM for bare-metal CPU performance

SPARC Hypervisor

Optimized for

SPARC &

Oracle Solaris



This is the simplest deployment model, with a single control domain providing virtual I/O services to a number of guest domains. This allows for a large number of small but isolated domains. The guest domains rely on the control domain for all I/O.

Oracle VM Server for SPARC – Guest Domain Model



This builds on the guest domain model, by adding a service domain to provide redundant I/O services to the guest domains. This allows for a large number of small but isolated domains, with better availability at the cost of a little bit more “hypervisor overhead” and some complexity.

Oracle VM Server for SPARC – Redundant Guest Domain Model



We move back to a single control domain model, but remove the Virtualization I/O overhead by using techniques which allow the guest to talk directly to the I/O devices. The guest is, however, still dependent on the control domain which actually owns the I/O device, and Live Migration is not possible when non-virtualized I/O is used

Oracle VM Server for SPARC – SR-IOV or Direct I/O Domains Model



Domains of this type are given direct ownership of their I/O. These guests run at a bare-metal performance level and are fully independent of each other. The number of root complexes and PCIe slots available limits the number of domains of this type that can be created. Live Migration is not possible using this model.

Oracle VM Server for SPARC – Guest Root Domains Model

Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | 30

Oracle Solaris Zones• Used by almost every Solaris

customer• Direction: the “cloud space” is

moving towards OS virtualization• Highly efficient and scalable • Zero overhead virtualization• Extreme consolidation• Tightly integrated into every Solaris

component

Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | 31

• Next Generation Virtualization– Simple administration– Leverages Oracle Solaris resource

management and network virtualization– Seamless P2V and V2P– Locked-down root file system for both

guest and host– Forward compatibility– Recognized as a License Boundary

Solaris Kernel ZonesOS and Virtualization – Engineered Together

InfinibandFabric

10GbENetwork



Native Branded Zones makes direct use of the kernel running in the global zone and provides the lowest overhead. The performance of an application within a zone is no different from its performance running directly in the global zone, with the advantage of a private execution environment.

Oracle Solaris Zones – Native Branded Zones



Kernel zones run their own unique kernel. This provides the capability to run different updates of Oracle Solaris 11.2 on the system, and it allows the kernel zones to be updated independently, as well as provide greater isolation between workloads. The additional running kernel provides slightly more overhead than the traditional zones model

Oracle Solaris Zones – Kernel Zones



The term non-native branded zone is used to define zones that run an older Oracle Solaris version than the global zone. Oracle Solaris 10 supports Oracle Solaris 8 and Oracle Solaris 9 branded zones and Oracle Solaris 11 supports Oracle Solaris10 branded zones. These types of zones share the same characteristics as traditional zones

Oracle Solaris Zones – Non-Native Branded Zones


Oracle Virtualization Technologies• Each virtualization technology has

different characteristics• There is a natural mutual

exclusivity between flexibility and isolation• Only by understanding the

requirements of the workload can you make a choice of the most appropriate virtualization technology


Agenda





Conclusion

1

2

3

4

5



• What if you could have both flexibility AND isolation at the same time?• By combining different Oracle virtualization technologies, it is possible

to build an architectural model that delivers a no compromise consolidated infrastructure.• The following outlines just a few of the possible models

Why pick ONE?



• Many Oracle applications, particularly Oracle Database, have new optimizations for In-Memory computing• Creating a large numbers of Virtual Machines fragments the memory

into a number of smaller pools• To make best use of In-Memory options, it makes sense to keep

memory large and contiguous

Optimizing for In-Memory



We combine the availability and flexibility of the Redundant Guest Domains with the efficiency of Solaris Zones to provide an operationally simpler and more efficient architecture to manage.Smaller number of Domains allows good In-Memory usage.

Redundant Guest Domains and Oracle Solaris Zones



The model combines the zero virtualization overhead and high isolation of guest root domains with the flexibility and agility of Oracle Solaris Zones to provide the highest possible efficiency with the lowest level of overhead. Smaller number of Domains allows good In-Memory usage.

Guest Root Domains and Oracle Solaris Zones



We use the root domain model to create multiple independent I/O domains, but rather than run Zones as in the previous model, the root domains are used to host multiple SR-IOV Guest domains.

Root Domains and SR-IOV Domains


Advantages of a layered approachSummary of Characteristics

The combinations of Oracle virtualization technologies deliver higher scores across all the characteristics



None of these models are mutually exclusive. Depending on our workload requirements, there’s no reason why you couldn’t use all 3 within a single server:A: Redundant Guest Domains and Zones

B: Guest Root Domains and Oracle Solaris Zones

C: Root Domains and SR-IOV Domains

Hybrid Combination of all 3 models


Agenda





Conclusion

1

2

3

4

5


Conclusion

• Successful consolidation requires an understanding of the workload characteristics• Oracle virtualization technologies can be combined to perfectly match

a wide range of workload requirements• These technologies are flexible enough to accommodate changes in

workload requirements over time• Consolidation is about reducing cost. Your biggest costs are

operations and implementation. Focus on reducing those. • There is no additional cost to deploying these options, so you don’t

need to pick just one.

One size does not fit all


Conclusion

• Take the opportunity while re-platforming to do things differently–What can In-memory do to deliver real time enterprise features?– How would enabling your end-users with self service features change your

business?– How can you re-architect your Disaster Recovery and HA environments to be

simpler and more efficient?

• Consolidation Savings can usually build the business case for these changes, but significant additional business benefits can always be achieved as well

Don’t limit yourself to cost savings from consolidation alone


Conclusion

• Oracle’s Engineered Systems are designed and optimized to make use of these technologies• Oracle’s Optimized Solutions also make use of these technologies to

build best practice • Use these to get a head start

We’ve already done it for you


Conclusion

• http://www.oracle.com/technetwork/server-storage/solaris11/technologies/virtualization-306056.html

And, there’s a whitepaper:

Documents

No-Compromise Virtualization: Making Your Data Center Cloud Efficient, Scalable, and Flexible Michael Ramchand Platform Technical Director Oracle EMEA