liveperson on openstack case study koby holzer, liveperson

20
LivePerson Openstack case study: From 0% to 100% in 1 year Koby Holzer | November 5 th , 2013

Upload: eliza-croen

Post on 12-May-2015

248 views

Category:

Technology


3 download

DESCRIPTION

Started in mid 2012 and today we are with 100% of our services running on Openstack in production. Who is Liveperson? * Liveperson infrastructure in a nutshell * Components And Architecture * The use case * The story: once upon a time * The story: today * How we've our infrastructure to a PAAS style * 1.5 years in Production and Growing like Crazy * Why is Openstack so Dear to our RnD & QA? * What’s Cooking in our LAB - Operations, Control and autoscaling

TRANSCRIPT

Page 1: Liveperson on OpenStack Case Study  Koby Holzer, Liveperson

LivePerson Openstack case study:

From 0% to 100% in 1 year

Koby Holzer | November 5th, 2013

Page 2: Liveperson on OpenStack Case Study  Koby Holzer, Liveperson

Today’s Programme

Who is LivePerson?

The story: How was it in the old days and today?

What’s Cooking in the LAB?

Tips and tools

Page 3: Liveperson on OpenStack Case Study  Koby Holzer, Liveperson

@KobyHolzerclass KobyHolzer::service {

service {“LivePerson": name => “Koby", ensure => running, enable => true, has_started_career => in 1999,

In_LP => Since 01/2012 do_in_LP => Lead the DevOps group personal => Married +3 picture =>

subscribe => [File[“virtualization"],File[“Automation"],File[“Bigdata"], require => [Class[“Openstack::install"],Class[“puppet::config"],Class[“Hadoop”],

include => [“Beer”], }}

$ puppet apply –-verbose --modulepath=/etc/puppet/modules -e "include kobyholzer::service"

Page 4: Liveperson on OpenStack Case Study  Koby Holzer, Liveperson

8,500

customers

Creating Meaningful Customer Connections

LivePerson is…

SaaS pioneer since 1998

Mission

Customers

Technology

Page 5: Liveperson on OpenStack Case Study  Koby Holzer, Liveperson

Data @ LP

13 TBper month 20M

Engagements per month 1.8 BVisits per month

VOLUME

Page 6: Liveperson on OpenStack Case Study  Koby Holzer, Liveperson

Liveperson Infrastructure in a Nutshell

Web Layer

App Layer

Data Store

Page 7: Liveperson on OpenStack Case Study  Koby Holzer, Liveperson

A solution for our NON-persistent servers, such as the Web-

tier and the App tier

Be able to scale to thousands of VMs with commodity servers

and in a cost efficient manner

Transform our infrastructure to PAAS style.

The Use Case – Our minimal requirements

Page 8: Liveperson on OpenStack Case Study  Koby Holzer, Liveperson

The Story: Once Upon a Time

Operations

OR

New service

Page 9: Liveperson on OpenStack Case Study  Koby Holzer, Liveperson

The story - Today

Infrastructure as a Building BlockEasy, Accessible and Fast

Rest API

Physical

VMware

Openstack

Physical

VMware

Openstack

Page 10: Liveperson on OpenStack Case Study  Koby Holzer, Liveperson

Jump in – Components And Architecture

4 production DC’s1 Staging and 1 Dev&QA

All mastered and managed with

HORIZON

Identity(Keystone)

GLANCE

Quantum (Open

Vswitch)

RabbitMQ

Sequential DB

(Mysql)

Nova-Compute

Hypervisor(KVM)

Local disks for storage on each HOST

UBUNTU based

Page 11: Liveperson on OpenStack Case Study  Koby Holzer, Liveperson

Infrastructure As a Building Block

Commonly used

Page 12: Liveperson on OpenStack Case Study  Koby Holzer, Liveperson

Infrastructure As a Building Block

Used for IIS Web servers

Commonly used for Apache, Jboss & Tomcat

Page 13: Liveperson on OpenStack Case Study  Koby Holzer, Liveperson

7/26

/201

2

8/10

/201

2

8/25

/201

2

9/9/

2012

9/24

/201

2

10/9

/201

2

10/2

4/20

12

11/8

/201

2

11/2

3/20

12

12/8

/201

2

12/2

3/20

12

1/7/

2013

1/22

/201

3

2/6/

2013

2/21

/201

3

3/8/

2013

3/23

/201

3

4/7/

2013

4/22

/201

3

5/7/

2013

5/22

/201

3

6/6/

2013

6/21

/201

3

7/6/

2013

7/21

/201

3

8/5/

2013

8/20

/201

3

9/4/

2013

9/19

/201

30

200

400

600

800

1000

1200

1400

1600

25 58

219

420

524

1230

1400

580

176250

Openstack VM's

Openstack Hosts

Some Numbers 13

1.5 years in Production and Growing like Crazy

1500 Instances

Page 14: Liveperson on OpenStack Case Study  Koby Holzer, Liveperson

Our physical node

1 U server2 sockets with 6 cores each - E5-2630128GB RAM8 X 600GB 6G SAS 10K 2.5in – raid 102 X 10G nics

Page 15: Liveperson on OpenStack Case Study  Koby Holzer, Liveperson

What’s Cooking in our LAB – Operations and Control

Provisioning

Deployment

MCollective Clusters Orchestration and DC management

API

NOC will provision new VM’s, install physical servers, deploy

new services and upgrade existing ones

Auto scaling

With the help of HEAT and Ceilometer we’ll be able to apply auto-scaling to many of our clusters on the WEB and APP tier.&

Ceilometer

Page 16: Liveperson on OpenStack Case Study  Koby Holzer, Liveperson

CI

RnD’s code is automatically delivered to

production – Not yet deployed

Continuous Delivery

&HIERA

& Gerrit

Why is Openstack so Dear to Our RnD & QA?

Get thier own quota to provision VM’s

Can set thier own private LBs

Same keys and meta data deployed to all servers

No need for big budgets and settling for fewer VMs

Production compliant

Page 17: Liveperson on OpenStack Case Study  Koby Holzer, Liveperson

Tips and Tools

Filter Scheduler and soft provisioning

Getting management and the organization to support you

& MCollective

Page 18: Liveperson on OpenStack Case Study  Koby Holzer, Liveperson

Summary

Openstack is running the Core business of LivePerson

100% of services in LP have 1 or more component running on Openstack

Openstack is being used in our staging, Dev and QA environments

Page 19: Liveperson on OpenStack Case Study  Koby Holzer, Liveperson

What did we learn so far?

I will not deploy my new app on a physical server againI will not deploy my new app on a physical server againI will not deploy my new app on a physical server againI will not deploy my new app on a physical server againI will not deploy my new app on a physical server agaiI will not deploy my new app on a physical server agaI will not deploy my new app on a physical server a