suse roadmap lecture - novellcopying all or part of this manual, or dist ributing such copies, is...

www.novel l .comNovell Training Services

AT T L I V E 2 0 1 2 L A S V E G A S

SUSE RoadmapLecture

S U S 2 2

Novell, Inc. Copyright 2012-ATT LIVE-1-HARDCOPY PERMITTED. NO OTHER PRINTING, COPYING, OR DISTRIBUTION ALLOWED.

Copying all or part of this manual, or distributing such copies, is strictly prohibited.To report suspected copying, please call 1-800-PIRATES.

Version 12

Legal Notices

Novell, Inc., makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc., reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes.

Further, Novell, Inc., makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc., reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.

Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries. You agree to comply with all export control regulations and to obtain any required licenses or classification to export, re-export or import deliverables. You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. See the Novell International Trade Services Web page (http://www.novell.com/info/exports/) for more information on exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export approvals.

Copyright © 2012 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher.

Novell, Inc., has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed on the Novell Legal Patents Web page (http://www.novell.com/company/legal/patents/) and one or more additional patents or pending patent applications in the U.S. and in other countries.

Novell, Inc.

404 Wyman Street, Suite 500

Waltham, MA 02451

U.S.A.

www.novell.com

Online Documentation: To access the latest online documentation for this and other Novell products, see the Novell Documentation Web page (http://www.novell.com/documentation).

Novell Trademarks

For Novell trademarks, see the Novell Trademark and Service Mark list (http://www.novell.com/company/legal/trademarks/tmlist.html).

Third-Party Materials

All third-party trademarks are the property of their respective owners.


Copying all or part of this manual, or distributing such copies, is strictly prohibited. To report suspected copying, please call 1-800-PIRATES

Contents

SECTION 1: Introduction to SUSE Linux Enterprise 11 SP2 4

SECTION 2: SUSE Linux Enterprise 11 SP2 Feature Areas 29

SECTION 3: SUSE Linux Enterprise 11 SP2 Features 53

Table of Contents


4

SUS22: New Features of SUSE Linux Enterprise 11 SP2


SUS22: New Features ofSUSE Linux Enterprise 11 SP2Section 1: Introduction to SUSE Linux Enterprise 11 SP2


5



Objectives

• SUSE Linux Enterprise 11• Development Process• Lifecycle• New Maintenance Model




6

SUSE Linux Enterprise 11

Objective 1


7



SUSE Linux Enterprise

The most interoperable platform for mission-critical computing, both physical and virtual—from the desktop to the data center

Let's do a brief level set on the SUSE Linux Enterprise (SLE) platform, so that you have some context for the following roadmap discussion.Novell's recommended software infrastructure platform is SLE 11. We believe SLE 11 is the most interoperable platform for mission critical computing, suitable for both physical and virtual environments, spanning the desktop to the data center.Companies today are looking for cost-effective IT infrastructure solutions, including versatile platforms that can run both today's and tomorrow's mission critical workloads. SLE offers UNIX-like performance, reliability and scalability, at a Linux-like price. In addition, SLE offers the innovation and investment protection of a relevant, growing Tier 1 platform – one designed and brought to market through an open, transparent development process.More and more companies today are choosing to standardize on SLE as their enterprise Linux platform. Why? Because it is simply the most practical choice for them. It is specifically designed for their needs, with ubiquity, interoperability and mission critical computing in mind.

First ubiquity. SLE is designed for ubiquity – to run virtually anywhere – from the desktop to the data center. Enterprises want the flexibility to run their workloads on the hardware they choose (or have), even virtual hardware, and on different form factors, so that they can optimize their data center resources.

● SLE runs on 5 different processor architectures (x86 32 and 64 bit, Itanium, Power, and s390x), so that you can match workloads to hardware that is particularly suited for that workload.

● SLE is also designed for virtual environments – optimized to work with leading third party hypervisors – so that you can use mixed physical and virtual resources

● SLE is designed for emerging cloud environments, and can be customized for appliances.


8



Second interoperability. SLE is designed for maximum interoperability for today's heterogeneous IT environments (mix of classical UNIX, Linux, Windows server and desktop, Mainframe systems, etc.)

● SLE is designed (e.g. standards, interfaces) to just plug into your existing environment, to help you get the most out of your existing investments, without having to rip and replace whole sections of your data center.

● We work with partners like Microsoft to maximize interoperability between your Linux and Windows systems. As a result of our technical collaboration, SLE is the “Linux that works with Windows.” Microsoft endorses SLE, and recommends it to their customers that want to use Linux.

Finally mission critical computing. SLE is designed for for mission critical workloads – things like ERP systems and databases, as well as mission critical platforms – like the mainframe.

● Over 4000 applications are certified and supported today on SLE - more than on any other Linux platform.

● We work with partners like SAP and IBM to not only ensure our platform supports their ERP applications and mainframe hardware, we make sure it works well. As a result, 75% of SAP running on Linux today runs on SLE, and SAP recommends SLE to their customers that use Linux. Approx. 80% of all Linux running on the mainframe today is SLE.


9



SUSE® Linux Enterprise

Product Lines and Products

Server Product Line• SUSE Linux Enterprise Server• SUSE Linux Enterprise Server

for System z• SUSE Linux Enterprise High

Availability Extension• SUSE Linux Enterprise Real

Time Extension• SUSE Linux Enterprise Mono

Extension• SUSE Linux Enterprise Point

of Service

• SUSE Linux Enterprise Server for SAP Applications

SUSE Manager

Desktop Product Line• SUSE Linux Enterprise Desktop• LibreOffice

Virtualization Product Line• SUSE Linux Enterprise Server

Appliance Product Line• SUSE Studio Online

• SUSE Appliance Toolkit

Specialized Support Offers• SUSE Linux Enterprise Server

Subscription with Expanded Support (for Red Hat migrations)

• SUSE Linux Enterprise Server Priority Support for SAP

The following chart lists all the products that are associated with SUSE Linux Enterprise Server, including the core server operating system products, appliance operating systems, server extensions, and specialized support offerings.

For code 11, we there are some notable changes in our product strategy. First, SUSE Linux Enterprise Server for Itanium and Power have been decoupled from the x86 SKU. The pricing model for Itanium and Power also departs from x86 in that they are priced on a per CPU socket basis, rather than per server.

For code 11, we also formalized our strategy of offering optional extensions to our base server operating system for those customers that want additional capabilities. Two new extensions are introduced with Code 11 – a high availability extension, and a mono extension, and join SUSE Linux Enterprise Real Time. These extensions provide additional capabilities to only those customers that want and need them. Customers that will not use these capabilities are not forced to pay for things they do not need.


10



Certified Applications: SUSE® Linux Enterprise

(v9+) vs Red Hat Enterprise Linux (v4+) by quarter

March 2011 count: 1575 ISVs and 6812 applicationsNovell ISV catalog: www.novell.com/partner/isvRed Hat ISV catalog: www.redhat.com/apps/isv_catalog/browse_by_vendor.htm

About Red Hat Catalog's Apparent Growth

RHEL catalog netted 415 RHEL 4+ applications between October 2010 and January 2011. What's up with that?

● Main reason: 870 IBM applications were posted in past 3 months (!)● In fact, without IBM's help, RHEL app count would have decreased by 455

Other signs of trouble in paradise● RHEL 4+ ISV count decreased by 257 (lost 330 ISVs, added 73)● 330 ISVs deposted 635 applications as they opted out of catalog

● Strangely, defected ISVs include Reuters and SEP AG● RH has a mere 737 RHEL 4+ ISVs, meaning that we now have twice as many SLE 9+ apps as

their RHEL 4+ apps

About RHEL 6● No signs of RHEL 6 in their catalog yet● Give RH benefit of the doubt? Their catalog's negative activity could reflect effort to “clean house”

in preparation for RHEL 6 postings




11

Development Process

Objective 1


12



The SUSE® Build Service* Advantage

• Reduces production problems• Consolidates IT skills across disparate systems• Delivers critical updates in hours – not days or weeks* SUSE Build Service is the internal entity of the openSUSE® BuildService

infrastructure

Package Selection and Integration

Open Source Projects

Enterprise-Class Software

Quality TestingBuild Service

AMD/Intel x86_64

Itanium

POWER

System z

FeatureTest

ManualRegression

AutomatedRegression

Novell®

System Test

SUSE LinuxEnterprise

Contribution

Intel/AMD x86

Notes:


13




Common Code Base

• Foundation for SUSE Linux Enterprise products

• Fully supported core system: L3 support commitment

SUSE Linux Enterprise platform

SLES SLED SLE SDK SLE HA

Binary Code Base

Common (Open Source) Code Base

JeOS &Appliances

open source* technologyfully supportedbasis for all SUSE Linux Enterprise products

Note: There is a separate box for Real Time (RT) in the binary code layer to represent that SLERT uses a very different kernel configuration than the other SLE products. Although there are several kernel configurations in SLE (e.g., Xen, VMI), the RT kernel is a much different one. However, we do not consider it a separate kernel (with respect to security certifications (CC), etc.), just a different configuration of the same kernel from the underlying common code base.


14




Architecture Support

Choose the right architecture for your workload

• Intel/AMD 32bit

• AMD64/Intel64 64bit● Intel Nehalem-EX CPUs, support for the new AES instruction set

(AES-NI), to improve crypto operations● All recent and upcoming AMD CPUs and Chipsets● SGI Altix UV scales Intel64 to 4096 CPUs & 16TiB RAM

• IBM System z ● including extended floating point capabilities

• IBM POWER

• Intel Itanium

Notes:




15

Lifecycle

Objective 1


16




Standard Platform Lifecycle

General Support Extended Support

Year 1 Year 2 Year 3 Year 4 Year 5 Year 6 Year 7 Year 8 Year 9 Year 10

GA

SP1 Long Term Service Pack Support

SP2

SP3

SP4

Long Term Service Pack Support



• 10-year lifecycle (7 years General Support, 3 years Extended Support)

• Major releases every ~4years, service packs every 16-18 months

• Six month upgrade window• Long Term Service Pack Support – extend upgrade window or extend

major release lifecycle

Let's first review Novell's standard platform lifecycle policy.Customers have told us that they want longer product lifecycles so that they can build, test and deploy stable, more durable solution stacks, especially for their mission critical workloads. For this reason, the typical lifecycle for a Novell Linux platform product spans 10 years.

● We provide general support for our Linux platform products for seven full years after their initial release.

● For 3 years after that, we continue to make available all our support content – things like technical informations documents (TIDs), briefs, and guides – in our customer facing support knowledge base

During the seven year general support period for a particular platform product, Novell will typically release 4 services packs, on average about 1 every 16-18 months.

● Typically contains all of the patches, fixes and updates issued since the previous release of the product

● Also includes product enhancements and drivers to support new hardware.Novell strongly encourages its customers to upgrade to the most current service pack available, so that they are using what we know to be the most reliable, secure and best performing version for their enterprise.

● Novell provides an overlapping 6 month support period – a support window when the latest service pack, as well as its prior release, are both simultaneously supported.

● After this six month window, customers calling Novell about a particular support issue will typically be asked to apply all of the patches, fixes and updates required to bring them up to the current release, in order to efficiently and effectively diagnose and resolve their support issue.

Because some customers require more time than 6 months to upgrade to the latest service pack, Novell offers optional long term service pack support options.

● For an additional fee, Novell will extend the overlapping support window by an additional year, allowing customers a full 18 months to upgrade.


17




Current Platform Lifecycle

2009 2010 2011 2012 2013 2014 Notes

SLE 9

SLE10 x x

SLE 11 x x

SLE 12

CR: SLE 9 SP4 (2007) EOGS: Q3 2011 EOSS: Q3 2014



SP4

GA SP2 SP3

GA

SP3

SP1

• SUSE announces Service Pack releases and development and product schedules to customers and partners

• Dependable release timing• Predictability for planning rollouts and migrations

With that overview, let's review the present lifecycle status for SUSE Linux Enterprise (SLE). ● As a reminder - these milestones are our current planned dates, and subject to change. ● This is our best information at this time, and we provide you with these estimates so that you can

make better informed plans and roll-out decisions. Because Novell typically releases a major version of SLE every 3-4 years, at any given point in time, there may be 2 or 3 generally available and supported versions of the platform in the market.

● In fact today, customers with a valid subscription can choose to deploy SLE 11, 10 or 9, or any combination of the three,

● And they are are entitled to receive support for all of the versions they deploy. (You should relate that to the information regarding the service packs the page before!! Supported version if updated to the latest service pack)

SLE 9 was first released in Aug 2004● General support for SLE 9 is currently scheduled to end 7 years after its GA date, in July 2011.● The current release of this platform is Service Pack 4 (SP4). Another service pack for version 9 is

not planned. {note: many customers are using SLES 9 SP4, released in Dec 2007}● Support information for this platform is scheduled to remain in our knowledge base until July 2014.

SLE 10 was first released in July 2006● General support for version 10 will be offered until July 2013. ● SUSE Linux Enterprise 10 Service Pack 3 (SLE 10 SP3) was recently released in Oct 2009, and

Service Pack 4 (SP4) is planned to be released in the first half of 2011. {note: many customers are using SLES 10 SP2, released in May 2008}


18



SLE 11 is our most current enterprise Linux platform, and was launched in Mar 2009. ● It is our most versatile, interoperable platform for mission critical computing, and represents the

cumulative experience and combined expertise of our in-house engineers and extended community of open source developers.

● Development is presently underway on SUSE Linux Enterprise 11 Service Pack 1 (SLE 11 SP1), and is scheduled to be released later this year.

● SLE 11 is the platform where we will be concentrating the majority of our development efforts. Customers currently using version 9 or 10 should consider upgrading to SLE 11 SP1, to get maximum reliability, security, performance and innovation.


19




PLDP / Partner Linux Driver Process• What?● Allow Partners to package and provide open source kernel

device drivers for SUSE Linux Enterprise independent of SUSE's maintenance and release cycles

● Fully supported due to mutual support agreements● PLDP2 (openSUSE Buildservice based)

• Why?● quick hardware enablement

• How?● provide build infrastructure, download area

http://drivers.suse.com/, developer support

• When?● TODAY!

Notes:


20




Maintenance & Support Process

Ma

inte

nan

ce

Pro

cess

Su

pp

ort

Pro

ces

s

ProvidePatch

MaintenanceQA

CertifiedPatches

DeliveryVia NCC

ReceiveRequests

L1 and L2Escalation

L3Resolution

PTFVia NCC

AutoBuild is unique to Novell● A system for automating the SUSE LINUX build process from a common code base● Builds each platform● Integrates all test suites ● Assures that all SUSE LINUX products work together perfectly

Why is this important? For the customer it . . .● Reduces production problems● Improves operations● Consolidates skill sets● Expedites IT solutions

For ISVs, it makes it easy to build software which supports multiple architecutres. The results: broader market opportunity, faster time-to-market, increased competitive advantage.


21



SUSE Linux Enterprise 11 SP2

New Maintenance Model:

• more flexibility for customers while retaining full control

Compete with Solaris● Filesystem level: btrfs with “Copy on Write”, data checksums and

snapshotting● LXC delivers container support based on Control Groups● Enhance tracing capabilities, by delivering LTTng / Linux Trace

Toolkit (separate Extension)

Snapshot / Rollback for package updates:

• YaST2 + ZYPP + btrfs

Hardware enablement / incl. RAS features

Notes:




22

New Maintenance Model

Objective 1


23




Benefits – Customers

1. Improve Customer Satisfaction by● making Service Packs more lightweight● easier to test and deploy ("consume")

2. Improve Customer Satisfaction by● allowing for staying with older versions● and remaining supported for the full system

3. Answer market needs in between Service Packs by● allowing more Updates in the GU repository● delivering selective Enhancements

(mitigates the longer distance between SPs)

Notes:


24




Implementation

• One primary repository per major version● For SUSE Linux Enterprise 11 we start with the SP1 updates

repository● you may hear “GU” (General Update repository) here.

Keep in mind: GU repo = existing SP1 updates repo

• Service Pack repositories contain dependencies that are strictly bound together “patch sets” each with its own repository

• Updates are released when they are ready

• Quality for the enterprise – test entire service pack

Notes:


25




New Maintenance Model

• Service Pack● Dependencies – ABI/API and other● Major impact changes with high configuration QA requirement● Examples: intrusive kernel changes; invasive hardware updates• GU + Previous Service Pack(s) ● Service pack independent updates● Examples: Firefox● No delay on features and updates

SLES 11 General Updates (GU)SP1

SP2

SP3

Service Pack repositories typically contain everything bound to hardware enablement, e.g. a new kernel and X server for SLE 11 SP 2


26



SLES 9 Flexibility

SLES 10 Control

SLES 11 General Updates (GU) Flexibility + Control


Maintenance Delivery Evolution

SP1

SP1

SP2 SP3

SP2

GA

GA

SP3

SP1

SP3

SP2

6 months overlap

Notes:


27




Q1: Where do SP packages end up?

• Final decision by SUSE Release Managers and Maintenance Team depending on technical feasibility

• General Rules:● Independent new package or fully compatible update,

bugfixes or improvements with minor impact→ SLE 11 SP1 repository = GU Repository

● New package or fully compatible update, bugfixes or improvements with major impact or high QA need→ SLE 11 SP1 repository together with Service Pack

● Change which might affect compatibility or where (new or existing) package depends on other packages in an SP→ SLE 11 SP(n) repository together with Service Pack

Notes:


28




Q2: Pick and Choose• Customers can choose to remain on an arbitrary

version of a package in the GU repository

• NTS will support them, i.e.● accept a Service Request on those versions● analyze with the customer if his issue is already fixed● trigger fixing of an obvious issue● try to minimize the need of customers to upgrade

• Fixes to the package will only be delivered on top of the latest version

• If the latest version is in a Service Pack repository, customer either must migrate to that Service Packor buy LTSS

Notes:


29



SUS22: New Features ofSUSE Linux Enterprise 11 SP2Section 2: SUSE Linux Enterprise 11 SP2 Feature Areas


30



Feature Areas● Scalability● Virtualization● Appliances and Cloud● Reliability, Availability, Serviceability (RAS)● Systems Management● Interoperability● Security and Certifications

SUSE Linux Enterprise 11 SP2

Notes:




31

Scalability

Objective 1


32



SUSE® Linux Enterprise 11 Service Pack 1

Scalability TodayThe only enterprise Linux operating system that helps customers• manage several workloads within one Linux instance in a

lightweight manner by providing Kernel Resource Management with Control Groups

• scale with their hardware by supporting 4096 CPUs on Intel64, 1024 CPUs on POWER, 4096 CPUs on Itanium

• compute huge amounts of data in memory, e.g. in ERP and data-warehouse systems, by supporting 16TiB RAM (and beyond) on certified hardware

• deploy huge amounts of data by supporting SGI's XFS for filesystem and file sizes up to 8 EiB in the 4th generation of the OS

Notes:


33




Scalability Tomorrow

• With the increasing number of cores per system, improvements in power management and scheduling are key to control costs in physical and virtualized environments

• Maintain and expand local storage capabilities ‒ maintain existing capabilities (e.g. XFS)

‒ introduce btrfs as a supported solution, to improve manageability and give customers a maximum of flexibility

• Expand network filesystem capabilities (NFSv4.x/pNFS)‒ improve performance, reliability and security of filesystems across

datacenter networks

‒ pNFS client support will be available in SLES 11 SP2, pNFS server support might be available in a later version of SLE HA 11

Notes:




34

Virtualization

Objective 1


35




Virtualization Today

• Leading open source hypervisors in the platform:both Xen and KVM are fully supported

• Perfect Guest strategy, operating system tuned to run great as a guest on all major hypervisors, including VMware ESX, Microsoft Hyper-V or Citrix XenServer

• SUSE Appliance Program and SUSE Studio for easy building, testing, distribution and management of software stacks

• Unique cost efficiency – unlimited number of virtual machines per physical server with one subscription

Virtualization hostImprove interoperability and establish virtual machine migration between Xen and KVM to give customers full choice and smooth migration pathsKVM hypervisor leverages power saving capabilities and scalability improvements of the Linux Kernel

Perfect guest Tuning according to hypervisorContainer TechnologyMore detailed control and tuning for single processes and process groups


36



And what are the upcoming features and enhancements to cross-platform virtualization in SLES 11 SP1?SLES 11 already included support and optimizations for leading open source and proprietary hypervisor technologies, like Xen, VMware ESX and MSFT Hyper-V. With SLES 11 SP1, increased deployment options will be possible with an updated Xen hypervisor.

● In some cases, the relative performance degradation associated with virtual systems has limited their production use. With Xen 4.0, enterprises can expect improved performance for virtual systems running on a SLE host through support for single root I/O virtualization and address translation services. By taking advantage of virtualization-aware hardware and bypassing the hypervisor to communicate directly with network or storage devices, significant performance gains can be expected, especially for I/O intensive workloads.

● With SLES 11 SP1 we will be adding commercial support for KVM, an emerging open source hypervisor. x86 server virtualization is increasingly being deployed by mainstream enterprises for server consolidation and improved business agility. And Novell has a history of providing support for leading hypervisor technologies with SLES. This tradition continues in SP1 with the addition of KVM to Xen, VMware ESX and MSFT Hyper-V as supported virtualization deployment options. While KVM is limited in that it does not support older operating systems, requires the use of virtualization enabled hardware, and is not quite as feature-rich as Xen, in certain use cases, its smaller footprint and ability to more easily scale and manage power can make it an appropriate hypervisor technology choice.

We also expect to deliver with SLE 11 SP1 an updated set of paravirtualized drivers for Xen, ESX, Hyper-V and KVM, to improve the performance of virtualized guest operating systems on a SLES Xen or KVM host, as well as vice versa, improve the performance of SLES as a virtual guest on a Xen, ESX or Hyper-V, or KVM server.

● A number of 32 and 64 bit drivers for SLES and Windows OS's are planned, including new and/or improved paravirtualized drivers for SLES 10, 11, OES 2, Netware, MSFT Windows XP, Vista, 2003, 2008, and Windows 7.


37




Virtualization (1/2)

Xen updated to version 4.1• Latency improvements, flexible partitioning

• Better fault handling, improved scalability and performance

KVM updated to version 0.15• I/O improvements, storage and network device hotplugging

• Microsoft Windows support

Paravirtualized drivers / Virtual Machine Driver Pack • Increase performance, improve reliability and stability

Improved guest support for: • Microsoft Hyper-V,

• VMware ESX

• SUSE Linux Enterprise Server with Xen & KVM

Xen 4.1Re-architected XL toolstack, providing stable and robust APINew scheduler, better suitable for latency sensitive workloads and large number of CPUsCPU Pools for flexible partitioning and VM allocationEnablement of new hardware features for increased performance and scalabilityEnablement of Advanced Vector Extension (AVX)New memory access API for better fault handling

KVM 0.15Virtualization I/O performance improvementsExtended Page Table for smarter memory allocation choicesKernel SamePage Merging for memory deduplicationBlock device resizing and easier handlingMSI-X support for enhanced networking performanceStorage and network device hot plugging

Virtual Machine Driver Pack / Paravirtualized Driver Full KVM support out of a boxUpdated Xen drivers for better scalabilityEnhanced SCSI layer to support multiple adaptersUnified driver set for both Xen and KVM allowing for easy virtual machine migrationStability, reliability and performance improvements


38




Virtualization (2/2)

Container Technology (Soft Partitioning)

• Kernel Resource Management (control groups, LXC):create lightweight virtualization-like separations forbetter load management

Xen 4.1Re-architected XL toolstack, providing stable and robust APINew scheduler, better suitable for latency sensitive workloads and large number of CPUsCPU Pools for flexible partitioning and VM allocationEnablement of new hardware features for increased performance and scalabilityEnablement of Advanced Vector Extension (AVX)New memory access API for better fault handling

KVM 0.15Virtualization I/O performance improvementsExtended Page Table for smarter memory allocation choicesKernel SamePage Merging for memory deduplicationBlock device resizing and easier handlingMSI-X support for enhanced networking performanceStorage and network device hot plugging

Virtual Machine Driver Pack / Paravirtualized Driver Full KVM support out of a boxUpdated Xen drivers for better scalabilityEnhanced SCSI layer to support multiple adaptersUnified driver set for both Xen and KVM allowing for easy virtual machine migrationStability, reliability and performance improvements




39

Appliances and Cloud

Objective 1


40




Ready for Appliances and Cloud

Buy packaged appliances from Independent Software Vendors (ISVs):

Or build custom OS images and turnkey appliances yourself:

SUSE Studio

SUSE® Studio Onsite

WebYaST SUSE Lifecycle Management

Server

Notes:


41




Ready for the Cloud

Amazon EC2• Full support for SUSE Linux Enterprise Server 10 and 11

• Cost effective cloud pricing model

• Deploy Appliances from SUSE Studio directly to EC2

• Seamless integration with existing EC2 features, like EBS, CloudWatch, Load-Balancing or Elastic IPs

• Available in all zones in all regions

Notes:




42

Reliability, Availability, Serviceability(RAS)

Objective 1


43




Reliability Today

Reliability – Availability – Serviceability (RAS)• Strong cooperation with IBM on providing a Linux OS optimized

for mission critical workloads on System z

• Support hardware RAS features bringing AMD64/Intel64 systems on par with traditional RISC systems

• Large blade centers benefit from swap over NFS capabilities to centralize swap space and improve availability of the datacenter

• Cost savings by using built-in device-mapper MultiPath I/O (MPIO) replacing expensive commercial solutions.

• Increased redundancy through support of RAID 6, RAID 10

• Scheduler optimizations and support for new floating point features improve performance and save costs

Notes:


44




Reliability Tomorrow

Improve support for hardware based RAS capabilities• All architectures, but specifically:

> Intel “SandyBridge”

> IBM System z

Support for the btrfs filesystem• Reduce cost of storage management by providing an integration

of logical volume management and filesystem

• Checksums on data and metadata ensure data integrity

LTTng (Linux Trace Toolkit Next Generation)

• SUSE Labs contributing to LTTng technology

• Availability of base functionality for SLE 11 SP2(as part of an Extension)

Questions regarding LTTng

Question: will this be in the "-default" kernel or in the "-trace" flavour?

Answer: “-trace” only, so far. It has a small, but measurable performance impact. The -trace flavor has identical compile options to -default, only with tracing added.

Question: will we take LTTng in any case (accepting deviation from upstream) or will we only take what has been accepted upstream by mid next year?

Answer: We'll take the out-of-tree LTTng running on whatever is already merged upstream. So we take both parts, but hope the out-of-tree part to be rather small at that time, and definitely smaller than today.




45

Systems Management

Objective 1


46




Systems Management

Snapshot-Rollback for package updates • With ZYPP and btrfs

• Rollback changes to the system, which have been unwanted (administrator error) or did show unwanted results or side effects

Improve WebYaST • More configuration options

• Better remote management and cloud integration

Unattended migration from SUSE Linux Enterprise 10 • Reduces administration cost and downtime

Notes:




47

Interoperability

Objective 1


48




Interoperability (1/2)

Integration with Active Directory• Graphical / YaST2 integration into windows domain

authentications at install time

• Integration with native SUSE Linux Enterprise systems management stack and security capabilities (e.g. PAM)

Samba version 3.6• SMB2 support

• Support for Windows 7 domain logon

Remote Desktop Protocol RDP (used in Windows environments)

• Support xrdp (open source RDP server) on SLES x86_64

• Introduce FreeRDP client: better performance and Interoperability

Improve CIFS kernel module

Notes:


49




Interoperability (2/2)

Improved interoperability with next-generation network infrastructure and filesystems (NFSv4.1 + IPv6)

• UNIX systems such as Solaris

IPv6• Improve DHCP server and client (ISC dhcp)

• IPv6 support in NFS

• IPv6 capable Squid proxy (most other network daemons are IPv6 ready since SLE 10 times)

• Ensure IPV6 capabiliites with UEFI network boot

Notes:




50

Security and Certifications

Objective 1


51




Security and Certifications (1/2)

System Hardening• YaST Security Center

• Application confinement with AppArmor

• Basic Enablement for “SE Linux”

• Check integrity of systems on file level with AIDE

• Protect systems and data using encryption on three levels:“Full Disk” – Volume – Filesystem (eCryptFS)

• Filesystem POSIX capabilities to allow more finegrained control of access to files and running executables

Notes:


52




Security and Certifications (2/2)

Certifications• Carrier Grade Linux 4.0 registration: validated for telecommunication

• IPv6 (refresh)

• Common criteria certification in Evaluation Assurance Level 4 with augmentation according to the BSI OSPP (CC/OSPP EAL 4+)

• FIPS 140-2 certification for selected modules

Trusted Platform Modules (TPM) – Trusted Computing• Provide a cryptographically signed statement about the state of the system

when it has booted

Trusted Execution Technology (TXT)• Enhances Trusted Computing with processor-based separation functions on a

page-level in memory

• Helps to keep systems in consistent and proven (“measured”) states

• in virtual environments and cloud

Notes:


53



SUS22: New Features ofSUSE Linux Enterprise 11 SP2Section 3: SUSE Linux Enterprise 11 SP2 Features


54



Objectives

• Automated Upgrade from SLE10 to SLE11-SP2• Remote Desktop Protocol• btrfs• Linux Containers




55

Automated Upgradefrom SLE10 to SLE11-SP2


56



56

Unattended Upgrade

Upgrade SLES 10 SP3 to SLES 11 SP1

• Allows to easily upgrade many servers automatically

• Decision to upgrade automatically depends on‒ Number of servers

Automatic upgrade recommended from 20 servers on up

‒ Number of different server configurations

If you have many different configurations, a manual interactive upgrade might be preferred

SUSE Linux Enterprise Server also comes with innovative capabilities that deliver added convenience to IT professionals that administer large server farms. One such feature is Unattended Upgrade, which allows groupsof servers to be automatically upgraded,in addition to manually upgrading individual servers. Using UnattendedUpgrade, system administrators can quickly and easily upgrade their SUSE Linux Enterpriseserver operating systems, reducing downtime, lowering administrative costs and improving quality.

This feature is not available withRed Hat* Enterprise Linux.

The decision to upgrade automatically or manually, in an unattended or attended fashion, depends on several factors. Enterprises with many servers, good server configuration management control and staff comfortable using automated procedures will find the Unattended Upgrade feature in SUSE Linux Enterprise Server useful.


57



57

Three Easy Steps to Unattended Upgrade

1. Configure Booting into the Upgrade mode

2. Prepare the AutoYast Profile

3. Run the Automated Upgrade




58

Remote Desktop Protocol


59



Configure RDP Remote Administration (1/3)

Install Packages

Notes:


60




Launch YaST Module

Notes:


61




Enable RemoteAdministration

Notes:


62



RDP Remote Administration

Log In

RDP Remote Desktop

Notes:




63

btrfs


64




The btrfs (better fs) filesystem

• Integrated Volume Management• Support for copy on write• Powerful snapshot capabilities• Scalability• Other Capabilities:‒ Compression

‒ Data integrity (checksums)

‒ Desktops: SSD optimization (MeeGo has chosen btrfs as default)

• Technology preview in SLE 11 SP1,supported in SLE 11 SP2, default in SLE 12.

Notes:


65




The btrfs (better fs) filesystem (cont.)

• Rising star in the open source filesystem universe

• Btrfs builds the foundation for the Ceph distributed filesystem and its RADOS object store layer → Cloud

• Community is very active and hungry for additional support

• Support for offline in-place migration from ext2+ to btrfs

Btrfs is the 'rising star' in the open source file system universe. It summarizes ides from the ext series of file systems *ext2, ext3, ext4) as well as the Reiser file system, the XFS file system and the HP aufs file system.Btrfs implements the same concepts as the Sun/Oracle ZFS but does so in a much more open ended manner that will allow for much more headroom for development. Its architecture is much more scalable than ZFS. Btrfs was built with scalability and extensibility in mind.

Btrfs is very actively developed and greater stability, performance and new features are being added at a tremendous pace.


66



Btrfs Snapshots

• Btrfs snapshots:‒ are COW (Copy On Write)

‒ are writable

‒ can be snapshoted again

‒ are performed at the subvolume level

Notes:


67



SUSE Linux Enterprisebtrfs and Snapshot / Rollback

• SUSE Toolchain co-developed for openSUSE and SUSE Linux Enterprise

• “snapper” command line tool

• YaST2 integration for snapshot rollback

• Unique functionality: selective rollback

http://lizards.opensuse.org/2011/04/01/introducing-snapper/

Notes:


68



Snapper

• CLI Utility for file system snapshot management

• snapper can:‒ Create snapshots

‒ delete snapshots

‒ compare changes between snapshots

‒ undo changes between snapshots

• For each subvolume being snapshotted, a snapper configuration file must exist for that subvolume‒ created by the snapper create-config command

• snapper distinguishes 3 types of snapshots:‒ pre / post

‒ single

Snapper Snapshot Types:

pre / postPre / post snapshots always come in a pair. A pre snapshot is performed before a change to the system takes palace and then a post snapshot is performed immediately after the change takes place. These two snapshots can then be compared to sow exactly what changed in the file system.

singleSingle snapshots are standalone and have no relationship to other snapshots




69

Linux Containers


70



What are Linux Containers (LXC)

• Operating System level virtualization

• Run multiple isolated server installs on a single host

• Does not provide virtual machines but rather virtual environments similar to chroot

• Provides more isolation than chroot

• Can leverage Linux Control groups for container isolation and resource and process limits

Notes:


71



Physical HardwareIO & Platform Devices

(Disk, LAN, USB, BMC, IPMI, ACPI, etc.)Memory & CPU

(x86, x86-64, EM64T)

Container Based Virtualization Architecture

Physical Drivers

Linux Kernel

Applications

LXC Container

Applications

LXC Container

Applications

LXC Container

HardwareLayer

VirtualMachine

Layer

VirtualizationLayer cgroups

IOPath

With container based virtualization, no hypervisor is involved. The “Host” OS (in this case Linux) provides all OS services to each virtual container.Only a single kernel (Linux) can run on the hardware at a time with container based virtualization.


72



Physical HardwareIO & Platform Devices

(Disk, LAN, USB, BMC, IPMI, ACPI, etc.)Memory & CPU

(x86, x86-64, EM64T)

Hypervisior Based Virtualization Architecture (KVM)

Linux OS Kernel / Host OS

Hypervisor Management(qemu-kvm)

Virtualized Hardware(qemu-dm/virtio)

Physical Drivers

Applications

Kernel

IO System

Virt

ual

Driv

er

Virt

ual

Driv

er

Applications

Kernel

IO System

Virt

ual

Driv

er

Virt

ual

Driv

er

VM Management(libvirt)

IOPath KVM Hypervisor Kernel Module

vHo

st

HardwareLayer

VirtualMachine

Layer

VirtualizationLayer

Multiple Kernels

Hypervisor

With KVM (or the Kernel Virtual Machine), a kernel module is loaded into the Linux kernel that turns it into a hypervisor. KVM would essentially be a Type I Hypervisor because it is running directly on top of the hardware.With KVM, the Linux kernel becomes a “fat” hypervisor because it not only mediates access to the underlying hardware but also loads physical drivers and shares access to the underlying hardware devises with virtual drivers.Device emulation and VM management are handled by a modified version of QEmu running in user space.Because KVM is a hypervisor based virtualization architecture multiple kernels can run on the hardware at the same time. These kernels can be virtualy anu operating system, not just linux.


73

Course Titile



74

Course Titile


Unpublished Work of SUSE. All Rights Reserved.This work is an unpublished work and contains confidential, proprietary, and trade secret information of SUSE. Access to this work is restricted to SUSE employees who have a need to know to perform tasks within the scope of their assignments. No part of this work may be practiced, performed, copied, distributed, revised, modified, translated, abridged, condensed, expanded, collected, or adapted without the prior written consent of SUSE. Any use or exploitation of this work without authorization could subject the perpetrator to criminal and civil liability.General DisclaimerThis document is not to be construed as a promise by any participating company to develop, deliver, or market a product. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. SUSE makes no representations or warranties with respect to the contents of this document, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. The development, release, and timing of features or functionality described for SUSE products remains at the sole discretion of SUSE. Further, SUSE reserves the right to revise this document and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. All SUSE marks referenced in this presentation are trademarks or registered trademarks of Novell, Inc. in the United States and other countries. All third-party trademarks are the property of their respective owners.


suse roadmap lecture - novellcopying all or part of this manual, or dist ributing such copies, is...

Documents