Using SUSE Cloud to Orchestrate Multiple Hypervisors and Storage at ADP
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 2
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 Multiple Hypervisors Key Testing Requirements 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
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 8
Highlights of What's New in SUSE Cloud Improved networking and block storage adapter support Cisco Nexus, EMC, VMware NSX and others 9
10
SUSE Cloud Admin Server SUSE Cloud Administration 11
SUSE Cloud Controller PostgreSQL database Image Service (Glance) for managing virtual images Compute 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) 12
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 Compute Nodes nova nova nova nova 13
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 Storage Nodes 14
ADP and SUSE Cloud
POC/Pilot Target Objectives The ADP Cloud Multiple Hypervisors Key Testing Requirements 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
Mixed Hypervisor Support SUSE Cloud differentiator Advantages of running multiple hypervisors Workload optimization Licensing flexibility 17 17
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 18
19 SUSE Cloud VMware
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) 20
SUSE Cloud Hyper-V SUSE Cloud Admin Server Crowbar SLES SUSE Cloud Control Node Nova Database Message Queue SLES SUSE Cloud Compute for Hyper-V nova-compute neutron-hyperv-agent MS Hyper-V 2012, or MS Server 2012 SUSE Supported Microsoft Support 21
Requirements Windows Server 2012 or Hyper-V Server 2012 Samba Server running on Admin Server WinPE image (manually built via script) 22
POC/Pilot Target Objectives The ADP Cloud Multiple Hypervisors Key Testing Requirements 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
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 24
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 Compute Compute Node(s) Node Storage Node(s) Data exists even after instances have been terminated Object Storage Not used for block storage Stores objects that can be checked out and used 25
Storage for Compute Virtual 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 26
Unified Cloud Storage Ceph 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 27
28 VM Access to Storage
The Ecosystem
Integrated Workload Control Packaging with SUSE Studio 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 30
Integrated Workload Control Maintaining with SUSE Manager Centralized Management Point Patch, provision, configure, monitor Multiple Platforms Multiple hardware, multiple software Multiple Tenants Scalable to thousands of nodes 31
The Build
POC/Pilot Target Objectives The ADP Cloud Multiple Hypervisors Key Testing Requirements 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
Q & A Thank you. 35
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 Disclaimer This 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.