Using SUSE® Cloud to Orchestrate Multiple Hypervisors and Storage at ADP

2

Agenda

ADP Cloud Vision and Requirements

Introduction to SUSE® Cloud

Overview

Whats New

VMWare intergration

HyperV intergration

ADP and SUSE Cloud

The Build

Q&A

ADP's Cloud Vision and Requirements

Vision and Benefits – The ADP Cloud

Our Vision

Provide for ADP an Agile Cloud environment that allows for the rapid deployment of

Infrastructure as a Service (IaaS) Phase I & Defined Platform as a Service (PaaS) Services

Phase II that provides provisioning agility, resource consumption visibility , is vendor,

hardware, software & hypervisor agnostic and marshals capacity on demand without any IT

intervention while providing support, measured services and transparency for financial

processes and Business Owners

POC/Pilot Target Objectives – The ADP Cloud

Overall High Level Objectives

Success Criteria

• Prove The ADP Cloud Concept:

• Provisioning agility, elasticity and capacity on demand for compute, memory, storage, and networking delegated to

User Community to consume on demand through intuitive self service portal from one pane of glass

• On Demand Self Service Portal across multiple hypervisor selections.

• Project Level Compute, Memory, Storage, Networking and OS Allocations Made Easy for our Consumers

• Measured services and transparency for financial processes

• Vendor agnostic for both hardware and software selections

POC/Pilot Target Objectives – The ADP Cloud

Key Testing Requirements• Multiple Hypervisors

• KVM & vSphere an absolute must have, Hyper-V nice to have, Xen if time permits• Target SLES® VMs on KVM for initial deploy• Target vSphere workloads on ESX an absolute must have

• Prove Neutron functionality • Prove “live migrations” of VMs (KVM and vSphere) • Prove SUSE® Cloud 4 New features – Ceph and High Availability .• AD intergration• IBM XIV block storage integration• Prove API, GUI and Command Line functionality, ease of use, and ability to maintain• Prove ADP standard OS builds can seamlessly and flawlessly run without I&O intervention

Introduction to SUSE® Cloud

8

SUSE® Cloud

Enterprise OpenStack distribution that rapidly deploys and easily manages highly available, mixed hypervisor IaaS Clouds

• Increase business agility

• Economically scale IT capabilities

• Easily deliver future innovations

9

Highlights of What's New in SUSE® Cloud•

•

•

•

‒ Improved networking and block storage adapter support‒ Cisco Nexus, EMC, VMware NSX and others

10

11

SUSE® Cloud Admin Server

SUSE Cloud Administration

12

SUSE® Cloud Controller

Compute• PostgreSQL database

• Image Service (Glance) for managing virtual images

• Identity (Keystone), providing authentication and authorization for all SUSE Cloud services

• Dashboard (Horizon), providing the Dashboard, which is a user Web interface for the SUSE Cloud services

• Nova API and scheduler

• Message broker (RabbitMQ)

13

SUSE® Cloud Compute Nodes

• Pool of machines where instances run

• Equipped with RAM and CPU

• SUSE Cloud Compute (nova) service

‒ Setting up, starting, stopping, migration of VM's

ComputeNodes

nova

nova

nova

nova

14

SUSE® Cloud Storage Nodes

• Pool of machines providing storage

• Object storage provided by swift or Ceph‒ Optional

• Block storage provided by Nova Volume‒ Multiple backends

StorageNodes

ADP and SUSE® Cloud

POC/Pilot Target Objectives – The ADP Cloud

Key Testing Requirements• Multiple Hypervisors

• KVM & vSphere an absolute must have, Hyper-V nice to have, Xen if time permits• Target SLES VMs on KVM for initial deploy• Target vSphere workloads on ESX an absolute must have

• Prove Neutron functionality • Prove “live migrations” of VMs (KVM and vSphere) • Prove SUSE Cloud 4 New features – Ceph and High Availability .• AD intergration• IBM XIV block storage integration• Prove API, GUI and Command Line functionality, ease of use, and ability to maintain• Prove ADP standard OS builds can seamlessly and flawlessly run without I&O intervention

17

Mixed Hypervisor Support• SUSE® Cloud differentiator • Advantages of running multiple hypervisors

‒ Workload optimization‒ Licensing flexibility

•

17

18

SUSE® Cloud 4 Hypervisor Support

• Linux hypervisors included with SUSE Cloud 4:‒ KVM‒ Xen

• Microsoft Hyper-V• VMware vSphere • Mixed hypervisor support: different hypervisors in the

same cloud• Baremetal install via Crowbar of nodes – incl. KVM,

Xen, Hyper-V compute nodes

19

SUSE® Cloud VMware

20

Requirements

• VMware:‒ VMware vSphere vCenter 5.1 or newer‒ VMware vSphere ESXi nodes 5.1

• Note: OpenStack sees VMware cluster as single node• One compute node needed to interact with VMware

vSphere:‒ Interact with one vSphere cluster‒ Interact with one datastore per cluster

• Support of vMotion, High Availability and Dynamic Resource Scheduler (DRS)

21

SUSE® Cloud Hyper-V

SUSE Cloud Compute for Hyper-V

• nova-compute• neutron-hyperv-agent

• MS Hyper-V 2012, or• MS Server 2012

SUSE CloudAdmin Server

• Crowbar• SLES

SUSE Supported

Microsoft SupportSUSE CloudControl Node

• Nova• Database• Message Queue• SLES

22

Requirements

• Windows Server 2012 or Hyper-V Server 2012

• Samba Server running on Admin Server

• WinPE image (manually built – via script)

POC/Pilot Target Objectives – The ADP Cloud

Key Testing Requirements• Multiple Hypervisors

• KVM & vSphere an absolute must have, Hyper-V nice to have, Xen if time permits• Target SLES VMs on KVM for initial deploy• Target vSphere workloads on ESX an absolute must have

• Prove Neutron functionality • Prove “live migrations” of VMs (KVM and vSphere) • Prove SUSE Cloud 4 New features – Ceph and High Availability .• AD intergration• IBM XIV block storage integration• Prove API, GUI and Command Line functionality, ease of use, and ability to maintain• Prove ADP standard OS builds can seamlessly and flawlessly run without I&O intervention

24

High Availability for SUSE® Cloud

• Clusters the SUSE Cloud control nodes using SLE HAE

• Ensures ongoing access to cloud services

• Cloud administrators can deliver enterprise SLAs

• Increasing business speed requires availability

24

25

Ephemeral vs Volume vs Object Storage

• Ephemeral Storage (Block Storage)‒ Temporary in nature‒ Workload instance disk images‒ Data exist only as long as the workload instance exists

• Volume Storage (Block Storage)‒ Perisistent in nature‒ Created a volumes that can be attached to instances‒ Data exists even after instances have been terminated

• Object Storage‒ Not used for block storage‒ Stores “objects” that can be checked out and usedStorage

NodeStorageNode(s)StorageNode(s)

Compute NodeCompute NodeComputeNode(s)

26

Storage for ComputeVirtual block devices (Cinder)

• Persistent storage for VMs‒ Defined and managed through user dashboard‒ Used for adding additional persistent storage to a VM‒ Size defined by user, up to quota limits‒ Provides snapshot management

• Attached to any VM‒ Accessed as a block device, which can be partitioned

formatted and mounted. ‒ Only accessible from within a VM

• Supports external storage through vendor provided plug-ins – IBM XIV

27

Unified Cloud StorageCeph Integration

• Ceph Overview‒ Object and block in a single system‒ Integrates with OpenStack

‒ Cinder backend

‒ Glance support for images

‒ Integrates with Nova for provisioning‒ ReSTful API

‒ S3 or Swift protocols supported

• SUSE Cloud and Ceph‒ Integrated deployment and configuration‒ Fully supported in SUSE Cloud 4

28

VM Access to Storage

The Ecosystem

30

Package OS and Apps‒ Avoid conflicts and user install hassles‒ Use of approved repositories

Build for Multiple Hypervisors‒ Perfect for hybrid environments

Integrated with Cloud and Management Solutions‒ Automatic connection for security and patching‒ Ensures compliance

Integrated Workload ControlPackaging with SUSE Studio™

31

Centralized Management Point‒ Patch, provision, configure, monitor

Multiple Platforms‒ Multiple hardware, multiple software

Multiple Tenants‒ Scalable to thousands of nodes

Integrated Workload ControlMaintaining with SUSE® Manager

The Build

POC/Pilot Target Objectives – The ADP Cloud

Key Testing Requirements• Multiple Hypervisors

• KVM & vSphere an absolute must have, Hyper-V nice to have, Xen if time permits• Target SLES® VMs on KVM for initial deploy• Target vSphere workloads on ESX an absolute must have

• Prove Neutron functionality • Prove “live migrations” of VMs (KVM and vSphere) • Prove SUSE® Cloud 4 New features – Ceph and High Availability .• AD intergration• IBM XIV block storage integration• Prove API, GUI and Command Line functionality, ease of use, and ability to maintain• Prove ADP standard OS builds can seamlessly and flawlessly run without I&O intervention

34

Thank you.

35

Q & A

36

Unpublished Work of SUSE LLC. All Rights Reserved.This work is an unpublished work and contains confidential, proprietary and trade secret information of SUSE LLC. 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.