OpenStack/Hyper-VFOLSOM DEEP DIVE

Intro

Alessandro Pilotti

Cloudbase Solutions

apilotti@cloudbasesolutions.com

Peter Pouliot, CISSP

Microsoft

ppouliot@microsoft.com

OpenStack Essex Summit

Goals:

Organize a development community to support

and maintain the OpenStack/Hyper-V codebase

Re-Integrate Hyper-V codebase for Folsom Release

Make Hyper-V server the premier hypervisor for

OpenStack compute workloads

Folsom Success story

Established a community

5+ active members contributing

Hyper-V restored in Folsom

All code Integrated and maintained within the

active Nova-Compute codebase on Github

Original Functionality restored and greatly

improved

Hyper-V v3 Server 2012 released and ready for

OpenStack compute

Microsoft’s Hyper-V Server 2012Ready for you to try with OpenStack

Folsom!

Key Code Contributions

for Folsom

Alessandro Pilotti

Pause/Un-pause, Suspend/Resume,

Snapshot, Live Migration

Folsom integration, Hyper-V unit Testing Framework

Folsom Installer

Pedro Navarro Perez

Volume attach/Detach

Boot from volume

Jordan Rinke

Initial integration and Essex installer

Hyper-V 2012 and

OpenStack

Python Application installed as an

application/service on the Hyper-V node.

OpenStack compute utilizes key features baked

into the Hyper-V Virtualization Platform

Does not require windows clustering services

Does not require shared storage

Which Operating

Systems?

Operating Systems:

Windows Server / Hyper-V Server 2008 R2

Windows Server / Hyper-V Server 2012

Windows 8 (Testing / Development only)

OpenStack Quick

Reference

Hyper-V/Glance

Integration

Native glance client support on Windows.

Upload images directly from the windows

compute node

VHDx support planned for Grizzly

Volume Attach/Detach

Requirements

Windows iSCSI initiator service enabled and

running on hyper-v compute node.

Configuration can be scripted

Create, attach detach volumes using the

OpenStack Dashboard or Nova commands.

OS must be installed directly onto the created

volume for “boot from volume” instances

Live Migration

Requirements

Each compute node must have Active Directory

Domain Membership

Nova-compute service must be running under an

Active Directory Domain account.

Shared nothing live migration can be enabled via

simple powershell commands or from the Hyper-V

management GUI.

Live Migration initiated via nova live-migration

commands

MSI Installer

Features:

Independent Python environment to avoid conflicts

with existing applications

Installs and registers all the required dependencies

Generates dynamically a nova.conf file based on

the parameters provided by the user

Creates a new Hyper-V external switch if required

Registers Nova Compute as a service and starts it

Enables the Microsoft iSCSI Initiator service (optional)

MSI Installer Continued..

Enables and configures Hyper-V Live Migration

(optional )

FreeRDP for Hyper-V console access

Installs a command prompt shortcut in the

applications menu for a ready made OpenStack

prompt (optional)

Can be executed fully unattended and

automated

Grizzly is Coming

Planning for Grizzly now!

Quantum

RDP access to VM Consoles

Windows Guest Agent

Cinder

Get Involved!

How can you help?

Testing

Documentation

Find us to chat or ask questions

Email:

ppouliot@Microsoft.com

apilotti@cloudbasesolutions.com