critical orchestration and automation tasks in the carrier cloud

COPYRIGHT © 2012 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

CRITICAL ORCHESTRATION AND

AUTOMATION TASKS IN THE CARRIER CLOUD

Andreas Lemke June 21, 2012

2


AGENDA

1. Background

2. Orchestration

3. Automation

4. Conclusions

3


INTRODUCING THE

CARRIER CLOUD

AGILE

• End-to-end management

• Highly scalable and elastic

• On demand

• Open/dynamic

RELIABLE

• Meet or exceed “five nines”

• Fast fault recovery

• Secure

TRANSFORMATIVE

• Pay per use

• Application aware

• Fixed and mobile

• Analytics

CARRIER CLOUD

CAPACITY

DISTRIBUTED CLOUD NODES

COVERAGE

RESILIENCY

GOVERNANCE

SECURITY NETWORK

4


WHY SHOULD A SERVICE PROVIDER CARE?

ENTERPRISES WILL PAY PREMIUM FOR CARRIER CLOUD

• Carrier cloud has

a far greater revenue

potential (10 X)

• Carrier cloud is more

attractive (4 X) to

enterprises than existing

public cloud services

Source: Alcatel-Lucent Global Cloud IT Decision Maker Study | September 2011

Reven

ue p

er

pote

ntial

featu

re p

er

month

Latency guarantee

Bandwidth guarantee

Remediation

User-configured redundancy

Complex network topologies

Encrypted storage Rapid VM instantiation

Public cloud

premium VM

Carrier cloud

premium VM

5


CARRIER CLOUD

CLOUD

NETWORK

CHALLENGES FOR

CARRIER CLOUD PROVIDERS

• Bridging the gap between

networking and data centers

• Industrializing operations

• Integrated resource placement for

optimal allocation of resources

6


INTRODUCING CLOUD

ORCHESTRATION AND AUTOMATION

• Orchestration

Create higher level abstractions/actions

Predefined workflows for cloud

management tasks

Predefined error handling

Internal or external – using APIs

• Automation

Utilize computations algorithms

Trigger automatic actions ORCHESTRATION

AUTOMATION

7


THE CLOUD NETWORK

MANAGEMENT ARCHITECTURE

ORCHESTRATION AND AUTOMATION

CLOUD API

DATA CENTER NODE DRIVER CLOUD NETWORK DRIVER

CARRIER PaaS (service on-boarding/management)

PORTAL

Everything-as-a-Service Network Data Video Comms

Hybrid cloud Public cloud Network management cloud

BSS

• Product catalog

• CRM

• Billing

OSS

• Service catalog

• Inventory

• Order management

• Network activation

Internal

VIRTUAL TELCO SERVICES IT

8


ORCHESTRATION

PRIMITIVES

• Data Center

Based on industry standard

stack APIs

e.g. Open Stack, Cloud Stack,

Amazon AWS

• Network

Information: ALTO

Control: Typically vendor

specific

COMPUTE –

VIRTUAL

MACHINES

VIRTUAL

APPLIANCES VM IMAGES

STORAGE -

VOLUMES

SECURITY,

IDENTITY

NETWORK

CONNECTIVITY,

POLICY,

ADDRESSING

MONITORING,

ALERTS

9


TYPICAL CLOUD ORCHESTRATION

AND AUTOMATION TASKS

RACK INSTALLATION

SERVER

REPLACEMENT LAN MANAGEMENT

IMAGE MANAGEMENT

VIRTUAL APPLIANCE

MANAGEMENT

BACKUP

SECURITY

MANAGEMENT

SERVER LOAD

MANAGEMENT

INFRASTRUCTURE

MANAGEMENT

SERVICE

SCALE IN/OUT

APPLICATION TEMPLATE

INSTANTIATION

SELF HEALING

SERVICE CREATION

AND TERMINATION

SLA MONITORING

SERVICE RE-FARMING

MULTI-OPCO

V-TELCO

DEPLOYMENT

SERVICE AND

APPLICATION

MANAGEMENT

10


11


12


13


EXAMPLE: ORCHESTRATING THE

CREATION OF A CLOUD SERVICE

API ENGINE: AUTHENTICATE USER AND VALIDATE REQUEST

INITIATE WORKFLOW

AUTOMATION: GET RANKED CLOUD NODES

STATICALLY FIND MOST SUITED CLOUD NODE

ROLLBACK

OPTIONALLY CREATE VLAN

CREATE VM AND LOAD IMAGE

OPTIONALLY CONNECT VLAN TO WAN VPN AND SET WAN POLICY

FAILURE

ASSIGN IP ADDRESS AND SECURITY GROUP

NOTIFY OSS/BSS SYSTEMS

NOTIFY USER: ACTION COMPLETED

FIND MOST SUITED CLOUD NODE

ORCHESTRATION ENGINE

PORTAL: USER SPECIFIES SERVICE

14


ORCHESTRATION:

MULTI-OPCO APPLICATION DEPLOYMENT

• Deploy service provider applications

in a multi-opco private cloud

• Meet national constraints

• Flexibly centralize/decentralize apps

• Deployment templates

• Centralized software updates

• National configuration

15


COMPUTE AUTOMATION

COMPUTE RESOURCE PLACEMENT

• Placement of cloud resources in a legacy centralized cloud

Well understood problem with available commercial solutions

• Resource placement is more complex in networked cloud

More choices where a requested resource can be placed

More constraints to take into account

Geographic location preferences

Cost limits

Network distance and latency bounds

CONVENTIONAL

CLOUD

CARRIER

CLOUD

http://files.digitizor.com/wp-content/uploads/2011/05/microsoft-azure-logo.jpg

16


PLACEMENT AUTOMATION

NEEDS NETWORK AWARENESS

17


NETWORK AWARENESS IS KEY

IETF APPLICATION-LAYER TRAFFIC OPTIMIZATION (ALTO)

NETWORK MAP

SERVICE

COST MAP

SERVICE

MAP FILTERING

SERVICE

END POINT

PROPERTY SERVICE

END POINT

COST SERVICE

ALTO CONVEYS PROPERTIES ON NETWORK PARTITIONS AND PATHS BETWEEN THEM

CDN automation

Cloud automation ALTO server

…

ALTO

18


PLACING VIRTUAL MACHINES

WHY FINDING THE RIGHT LOCATION MATTERS

AVERAGE DELAY

REDUCED BY 33% POINTS!

0%

10%

20%

30%

40%

MAXIMUM LINK UTILIZATION

Random-

2DC

Random-

12DC

Proximity-

12DC

NetBalance-

12DC

5 MS MORE THAN OPTIMAL

0

20

40

60

ms

80

Random-

2DC

Random-

12DC

Proximity-

12DC

NetBalance-

12DC

19


CONCLUSIONS

BUILD THE CARRIER CLOUD

DATA CENTER

NETWORK

INDUSTRIALIZE

ORCHES- TRATION

AUTO- MATION

COLLECT THE BENEFITS

MORE CUSTOMER SATISFACTION

BETTER RESOURCE UTILIZATION

MORE REVENUE

critical orchestration and automation tasks in the carrier cloud

Technology

alcatellucent global

cloud stack

networked cloud

cloud service api engine

legacy centralized cloud

conclusions2 copyright

automation orchestration

multiopco private cloud