LivePerson Openstack case study:
From 0% to 100% in 1 year

Koby Holzer | November 5th, 2013
Today’s Programme

Who is LivePerson?

The story: How was it in the old days and today?
What’s Cooking in the LAB?

Tips a...
@KobyHolzer
class KobyHolzer::service {

service {“LivePerson":
name => “Koby",
ensure => running,
enable => true,
has_sta...
LivePerson is…

Mission

Customers

Creating Meaningful
Customer Connections

8,500
customers

Technology

SaaS pioneer si...
Data @ LP

13
VOLUME

TB
per month

20

M
Engagements per month

1.8

B
Visits per month
Liveperson Infrastructure in a Nutshell

Web Layer
App Layer

Data Store
The Use Case – Our minimal requirements

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

tier and the App tie...
The Story: Once Upon a Time
Operations

OR

New service
The story - Today

Infrastructure as a Building Block
Easy, Accessible and Fast
Rest API

Physical
VMware

Openstack
Jump in – Components And Architecture

HORIZON

Identity
(Keystone)

GLANCE

RabbitMQ

NovaCompute

Quantum
(Open
Vswitch)...
Infrastructure As a Building Block

Commonly used
Infrastructure As a Building Block

Commonly used for
Apache, Jboss & Tomcat

Used for IIS Web
servers
Some Numbers

13

1.5 years in Production and Growing like Crazy
1600

1500 Instances

1400
1200

1400
1230

1000
800
Open...
Our physical node

1 U server
2 sockets with 6 cores each - E5-2630
128GB RAM
8 X 600GB 6G SAS 10K 2.5in – raid 10
2 X 10G...
What’s Cooking in our LAB – Operations and Control

Provisioning
API
NOC will provision new
VM’s, install physical
servers...
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 a...
Tips and Tools
Summary

Openstack is running the Core business of LivePerson
100% of services in LP have 1 or more
component running on O...
What did we learn so far?

I will not deploy my new app on a physical server again
I will not deploy my new app on a physi...
Thank You
We are hiring
Koby Holzer – kobyh@liveperson.com

il.linkedin.com/in/kobiholtzer/
Upcoming SlideShare
Loading in …5
×

Liveperson on OpenStack Case Study Koby Holzer, Liveperson

573 views
404 views

Published on

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

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
573
On SlideShare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
16
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Liveperson on OpenStack Case Study Koby Holzer, Liveperson

  1. 1. LivePerson Openstack case study: From 0% to 100% in 1 year Koby Holzer | November 5th, 2013
  2. 2. 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
  3. 3. @KobyHolzer class 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"
  4. 4. LivePerson is… Mission Customers Creating Meaningful Customer Connections 8,500 customers Technology SaaS pioneer since 1998
  5. 5. Data @ LP 13 VOLUME TB per month 20 M Engagements per month 1.8 B Visits per month
  6. 6. Liveperson Infrastructure in a Nutshell Web Layer App Layer Data Store
  7. 7. The Use Case – Our minimal requirements 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.
  8. 8. The Story: Once Upon a Time Operations OR New service
  9. 9. The story - Today Infrastructure as a Building Block Easy, Accessible and Fast Rest API Physical VMware Openstack
  10. 10. Jump in – Components And Architecture HORIZON Identity (Keystone) GLANCE RabbitMQ NovaCompute Quantum (Open Vswitch) Sequential DB (Mysql) Hypervisor (KVM) Local disks for storage on each HOST UBUNTU based All mastered and managed with 4 production DC’s 1 Staging and 1 Dev&QA
  11. 11. Infrastructure As a Building Block Commonly used
  12. 12. Infrastructure As a Building Block Commonly used for Apache, Jboss & Tomcat Used for IIS Web servers
  13. 13. Some Numbers 13 1.5 years in Production and Growing like Crazy 1600 1500 Instances 1400 1200 1400 1230 1000 800 Openstack VM's 600 Openstack Hosts 524 400 420 200 0 250 219 5 25 58 176 80
  14. 14. Our physical node 1 U server 2 sockets with 6 cores each - E5-2630 128GB RAM 8 X 600GB 6G SAS 10K 2.5in – raid 10 2 X 10G nics
  15. 15. What’s Cooking in our LAB – Operations and Control Provisioning API NOC will provision new VM’s, install physical servers, deploy new services and upgrade existing ones & Ceilometer 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.
  16. 16. 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 RnD’s code is automatically delivered to production – Not yet deployed & HIERA & Gerrit
  17. 17. Tips and Tools
  18. 18. 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
  19. 19. What did we learn so far? I will not deploy my new app on a physical server again I will not deploy my new app on a physical server again I will not deploy my new app on a physical server again I will not deploy my new app on a physical server again I will not deploy my new app on a physical server agai I will not deploy my new app on a physical server aga I will not deploy my new app on a physical server a
  20. 20. Thank You We are hiring Koby Holzer – kobyh@liveperson.com il.linkedin.com/in/kobiholtzer/

×