moderator: jerry stabile

March 10, 2013 / Bentley Univesity / Boston MA

Virtualization

1

2 Topics

> Why Virtualization?

> What makes a good Virtual App?

> Cloud Computing Models

> Operating Environment

> Virtual Case Study

3 Intro of Presenters Team

Mike Picher Douglas Hubler Jerry Stabile

>Virtualization is a key building block to cloud computing

>Enabling technology that creates an intelligent abstraction layer which

hides the complexity of underlying hardware or software

>Drives the evolution of IT infrastructure to standardized compute platforms

4 Can RTC take advantage of virtualization

Why Virtualize?

Business Continuity

Infrastructure Consolidation

Rapid Deployment

Backup/Restoration

>Realtime processing

>Support flexible backup/restore

>Distributed vs monolithic

>Enhanced monitoring/right sizing

>Easy to install

Software architecture considerations

Criteria for running virtualized applications 5

>Optimized media service for RTC

>Redesigned backup/restore – CFEngine

>Enabled more distributed services

>Embedded monitor server

>Automated installer

>RPM based

>Environment agnostic

How R4.6 leverages virtualization

openUCTM release 4.6 readiness 6

P

Public, Private, Hybrid, Community Clouds?

Cloud Operating Environments 7

Private Cloud IT Managed Secure, available Heterogeneous Less scalable More expensive Office workers Confidential information Performance sensitive apps

Public Cloud Maximum flexibility Any device, any time, anywhere Third party provided Higher Risk – security, availability Monolithic Home workers Mobile workers

Hybrid clouds - partnership public and

private cloud computing and services providers

Cloud Services Cloud Computing

>Goals:

> Become virtual environment agnostic

> Leverage existing production environments

> Utilize environment specific management tools

> Enable enterprise application store

>What is this program about?

> Creating best practice implementation process and documentation

> Providing technical assistance and training

> Quality assurance through load testing automation and use case validation

> Network infrastructure readiness consulting

> Integration assistance for service provisioning and assurance

8 Communications as a service from the cloud

siopXecs/openUCTM Cloud Certification Program

9 How to optimize a SW application for virtualization – what to look for?

Operating environment requirements

>openUC / sipXecs 4.4 and earlier

> Could easily virtualize proxy/registrar servers.

> Not media services

>openUC / sipXecs 4.6

> Can virtualize entire system.

>Why?

> Red Hat / CentOS 6.x – Tickless Kernel

> New Timer Modules for FreeSWITCH (our media services)

What can we virtualize?

openUC / sipXecs 4.6 10

>Performance

> Estimate 10 to 20% less performance in Virtual Environment

>Host Servers

> Minimize interaction between High CPU / High Bandwidth need virtual servers and openUC on

same host.

> Dedicate processor and RAM when able.

11 openUC Virtualization Planning

>Minimal Configuration

> 1 Core, 3.7 GB of RAM, 50 GB HD (AWS m1.medium)

> Supports about 20 concurrent calls to media services (conf, vm)

> Up to ~ 100 users.

> Can make memory use less with some ‘tweaking’ of sipxconfig heap usage.

> SIP Capture takes significant disk space, turn off for small installations.

Bandwidth Utilization

> Peak ~ 200 Kbps / 10 users (1 of every 5 users on phone)

12 openUC Resource Footprint

>0 – 75 Users – 1 Core, 4 GB of RAM, 80 – 100 GB storage

>Up to 500 Users – 4 Cores, 8 GB of RAM, 200 – 300 GB storage

>Up to 5000 Users – 8 Cores, 32 GB of RAM, 1 TB

>Memory is more important than processor speed.

>Would you really run 5000 users on one server? No.

Recommended Resources 13

>eZuce

>5000 Concurrent User System

14 Case Study

>Runs in AWS

> m1.medium (1 core, 2 Amazon Compute Units, 3.7 GB RAM, 80 GB Storage)

>55 – 65 Concurrent Registrations

>Conference bridge good to ~ 22 Concurrent callers (mix of inside / outside)

eZuce’s Corporate System 15

eZuce’s System in AWS Cloud 16

>Proxy / Registrar / Config Server / SIP Capture Server (qty 1)

> 8 GB of RAM, 4 Cores, 200 GB

>Proxy / Registrar (qty 2)

> 8 GB of RAM, 4 Cores, 100 GB

>Voicemail / Conference Bridge (qty 2)

> 8 GB of RAM, 4 – 6 Cores, 300 GB

500 Users

Private Cloud Case Study 17

Customer running in VMWare Private Cloud 18