Slides that I presented at the 2011 OpenStack design summit in Boston, discussing the Openstack work done within the Novell/Microsoft Joint Interoperability Lab.

1. OpenStack/HyperV Clouds
Peter Pouliot, CISSP
Microsoft New England Research and
Development Center: Joint Interoperability Lab
ppouliot@suse.com

2. Peter Pouliot
Who am I?
• Grew up in RI and lives in Stoneham, MA
• Husband and father of two boys.
• Likes to Fish
• Formally educated and Trade Certified
‒ RIC: Philosopy, BU: Telecom Security/Digital Forensics
‒ CISSP, MCSE+I, MCT, OCP, Network+
• Part of Ximian/Novell/SuSE since 2003
2

3. Discussion Overview
• Joint Interop Lab
• SLE/HyperV/LIS
• OpenStack Overview
• OpenStack/HyperV
‒ Overview
‒ History of JIL efforts
‒ Gap Analysis Overview
• Conclusions
• Questions
3

4. Novell/Microsoft
Joint Interopability Lab (JIL)
• Primary focus on virtualization technology and
systems management.
• Development and Testing of the Linux
Integration Services for HyperV
• Driver validation for partially paravirtualized
guests on multiple hypervisor platforms. Linux
on HyperV, Windows on Xen/KVM.
• Technological proof of concepts.
• Ongoing Samba core development
infrastructure resources.
4

5. Novell/Microsoft
Joint Interopability Lab (JIL)
• Commodity Servers, and Blade infrastructure
• Entry level SAN
• Enterprise Access network and Core Server
Network Fabric
• Usable block of public internet addresses.
• Delegated name space from Microsoft and
Novell
• Misc infrastructure workloads. 99% virtualized
last 4 years.
5

6. SUSE Linux
Enterprise Server
• Enterprise Linux Operating System
• Excels in HPC and High availability.
• The only Enterprise Linux to provide guest
ubiquity giving you choice in your virtualization
platform.
• First “Enterprise” Linux distribution packaged,
licensed, and supported within Amazon's EC2
infrastructure.
6

7. Microsoft HyperV
Linux Integration Services (LIS)
• HyperV is Microsoft’s “Enterprise” hypervisor
technology.
• Linux Integration Services (LIS): a series of
Linux kernel drivers and services to enable
partial paravirtualization or “enlightenment” of
Linux guests upon HyperV
• There have recently been major
improvements in the performance of Linux
Guests on HyperV.
7

8. OpenStack Explained
What is OpenStack?
• Global collaboration of developers and cloud
computing technologists.
• Ubiquitous open source cloud computing
platform for public and private clouds.
• Project aims to deliver solutions for all types
of clouds by being simple to implement,
massively scalable and feature rich.
• Technology consists of a series of
interrelated projects delivering various
components for a scalable IAAS solution
8

9. OpenStack Explained
OpenStack and its components
• OpenStack Compute Infrastructure ( Nova )
‒ Underlying cloud computing fabric controller to support all
activities needed for instances within the OpenStack Cloud
‒ Manages all compute resources, networking authorization and
scalability needs of the OpenStack Cloud
• OpenStack Storage Infrastructure ( Swift )
‒ Distributed object storage across commodity hardware.
‒ Provides scalability, redundancy and failover management
• OpenStack Imaging Service ( Glance )
‒ Lookup and retrieval system for virtual machine images
‒ Interface to multiple storage backends
9

10. OpenStack Explained
Functions and Features
• Functions and Features:
‒ Instance life cycle management
‒ Management of compute resources
‒ Networking and Authorization
‒ REST-based API
‒ Asynchronous eventually consistent communication
‒ Hypervisor agnostic : support for Xen, XenServer, KVM,UML,
VMware and Hyper-V
10

11. OpenStack Explained
OpenStack Cloud Fabric Components
• Nova Cloud Fabric is composed of the following major
components:
‒ API Server ( nova-api )
‒ Message Queue ( rabbit-mq server )
‒ Compute Workers ( nova-compute )
‒ Network Controller ( nova-network )
‒ Volume Worker ( nova-volume )
‒ Scheduler ( nova-scheduler )
11

12. OpenStack Explained
OpenStack Architecture Diagram
12

13. OpenStack/HyperV
Why?
• Goal: to use OpenStack as a framework to enable
large scale testing of the LIS across multiple linux
distributions
• OpenStack enables Windows compute clouds.
• Allows for “no touch” compute node management on
the Windows virtualization platform.
• Provides distributed implementation of HyperV as a
virtualization platform without the need of additional
Windows infrastructure.
13

14. OpenStack/HyperV
Required Parts
• Nova Compute: Provides the api infrastructure for the
control of virtual host resources and guests on the
hypervisor platform.
• Requires Mysql database and RabbitMQ
• Nova Network: provides networking services. Used
for internal IP management/switching/routing.
• Glance: provides api and infrastructure for VM
imaging and injection onto the compute node.
14

15. OpenStack/HyperV
JIL Cloud 0.01
• Dedicated physical SLE11SP1 server running nova-api,
mysqld, rabbitmq, and nova-scheduler.
• Dedicated physical SLES11SP1 server running nova-
network integrated into our existing network
infrastructure.
• Dedicated physical SLES11SP1 server running glance
api and hosting vm images on local filesystem
• 10 compute nodes (each with 16 cores, 32GB ram)
running W2k8R2 Datacenter (mix of server and core)
and nova-compute client.
• Utilized existing pxe infrastructure for automated
deployment of compute nodes.
15

16. OpenStack/HyperV
JIL History Part 1
• April, 2011
‒ Research cloud management platform that supports HyperV
‒ Begin deployment of OpenStack Controller and Network services.
‒ Begin asking questions within community around HyperV support.
‒ Begin testing and automation of OpenStack/HyperV components
• May, 2011
‒ Automated HyperV compute node down to pxe install and two mouse clicks.
‒ Worked with Chiradeep Vittal of Cloud.com to add and test Synthetic/Paravirt
Nic support to OpenStack HyperV code.
‒ Successful integration of nova-network into JIL network infrastructure
‒ Began discussions of integrating HyperV testing into Jenkins (build and testing)
infrastructure with OpenStack community members.
‒ Successfully deployed 90 virtual machines across 6 nodes of a 10 node
OpenStack HyperV compute cloud.
16

17. OpenStack/HyperV
JIL History Part 2
• June, 2011
‒ Introduced to Jordan Rinke and began discussion of
HyperV/OpenStack efforts
‒ Shared HyperV/Openstack automation with Jordan to enable him to
begin gap analysis of the OpenStack/HyperV functionality
‒ Asked to provide OpenStack/HyperV reference implementation for
“Freecloud” project.
• July, 2011
‒ Began redeployment of cloud using “Core” for all compute nodes
‒ Began discussion on “Freecloud” involvement.
‒ Questioned MS resources for information on virtual network
configuration of Server Core.
17

18. OpenStack/HyperV
JIL History Part 3
• August, 2011
‒ Received powershell/WMI assistance and scripts to generate
virtual network switch configuration on Server Core.
‒ Provisioned hardware resources for dedicated Jenkins slave
within JIL to support automated OpenStack/HyperV testing
‒ Coordinated Jenkins configuration with community members and
completed Jenkins slave configuration.
‒ Received results of Gap analysis
• September, 2011
‒ Begin redeployment of OpenStack Controller infrastructure to
support stable and development code.
‒ Deployed internal build service to support LIS testing initiatives
and OpenStack Packaging.
18

19. OpenStack/HyperV
Gap Analysis Highlights
• HyperV supports following OpenStack Features:
‒ Launch, Reboot, Terminate
‒ Flat Networking
• Code is not properly stubbed out in the HyperV compute driver,
i.e. calling a missing function could cause a stack trace and
possibly result in the code crashing
• Not a Windows Service
• No similar functionality of IPTables/Networking Shortcomings
• No mechanism for VM persistent block attached storage
• Complete feature comparison can be found:
http://wiki.openstack.org/HypervisorSupportMatrix
19

20. OpenStack Conclusions
Personal Opinion
• OpenStack is a Foundation with a Philosophy
• OpenStack changes the way you think about
Computing
• OpenStack is an opportunity for Microsoft
• OpenStack enables rapidly scaling computing
resources
• OpenStack enables HyperV virtualization in ways I
didn't think were possible
• Development contribution is necessary for the
success of HyperV within the OpenStack cloud
20

21. Contact Information
• Peter Pouliot, CISSP
‒ ppouliot@suse.com
• Alex Landman
‒ alandman@suse.com
• Hashir Abdi
‒ habdi@microsoft.com
21

22. Questions?

24. Corporate Headquarters +49 911 740 53 0 (Worldwide) Join us on:
Maxfeldstrasse 5 +www.suse.com www.opensuse.org
90409 Nuremberg
Germany
24

25. This document could include technical inaccuracies or typographical errors.
Changes are periodically made to the information herein. These changes may be
incorporated in new editions of this document. SUSE may make improvements in
or changes to the software described in this document at any time.
Copyright © 2011 Novell, Inc. All rights reserved.
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.