Plone Deployment WPD2009
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

Plone Deployment WPD2009

on

  • 2,340 views

Presentation of the different deployments of Plone in different conditions and the ability of Plone to scale. From classic deployment to multiserver with Relstorage. Deployment on cloud also featured. ...

Presentation of the different deployments of Plone in different conditions and the ability of Plone to scale. From classic deployment to multiserver with Relstorage. Deployment on cloud also featured. Please feel free to use the diagrams or to ask the source code of the slides. Presentation made at the World Plone Day 2009 by Federico Guizzardi, system administration manager in Reflab.

Statistics

Views

Total Views
2,340
Views on SlideShare
2,339
Embed Views
1

Actions

Likes
4
Downloads
22
Comments
0

1 Embed 1

http://www.slideshare.net 1

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Plone Deployment WPD2009 Presentation Transcript

  • 1. Plone Deployment Plone Conference 2009 – Federico C. Guizzardi – 21 Aprile 2009 1
  • 2. Introduction • Different scenarios – Different page types – Page composition • Hard to estimate – Many variables: hardware, bandwidth, ... – Multiple benchmarks Plone Conference 2009 – Federico C. Guizzardi – 21 Aprile 2009 2
  • 3. Zope • Is the application server • It does the low level management • It is completely integrated Plone Conference 2009 – Federico C. Guizzardi – 21 Aprile 2009 3
  • 4. Vanilla Plone + Apache Internet • “Classic” • Practical (ports, statistics, etc.) Webserver • Configuration – Virtualhost – Advanced solutions – etc. Plone Conference 2009 – Federico C. Guizzardi – 21 Aprile 2009 4
  • 5. Vanilla Plone + Apache • Yes, if • No, if – Few, well – Multicore server distributed – Stable contents contents – Hi concurrency – Limited users levels – For development Plone Conference 2009 – Federico C. Guizzardi – 21 Aprile 2009 5
  • 6. Plone + Varnish + Apache Internet • Reduced response time • More user load Webserver • Lower machine Cache Sys load Plone Conference 2009 – Federico C. Guizzardi – 21 Aprile 2009 6
  • 7. Plone + Varnish + Apache • Yes, if • No, if – Stable contents – Multicore server – Limited server – Development resources – High number of – ... in general the users suggested – High number of deployment editors Plone Conference 2009 – Federico C. Guizzardi – 21 Aprile 2009 7
  • 8. Architecture on multicore server Internet Webserver Cache Sys Load Balancer Plone Conference 2009 – Federico C. Guizzardi – 21 Aprile 2009 8
  • 9. Architecture on multicore server • Yes, if • Maybe not if – Multicore (>2) – Variable user load – Hi number of users – Pages composed by a high number of sources Plone Conference 2009 – Federico C. Guizzardi – 21 Aprile 2009 9
  • 10. Distributed Architecture Internet s2 Webserver Cache Sys s3 Load Balancer s1 s4 s5 Plone Conference 2009 – Federico C. Guizzardi – 21 Aprile 2009 10
  • 11. Distributed Architecture: pros • Dynamic System – Only the necessary servers are turned on • Fault tollerance – Zope/Plone servers are redundant – ZEO can be “distributed” • Maintenance similar to that of a single instance – Backup, updates... Plone Conference 2009 – Federico C. Guizzardi – 21 Aprile 2009 11
  • 12. With Relstorage Internet s2 Webserver Oracle / Postgres s3 Cache Sys Load Balancer s1 s4 Plone Conference 2009 – Federico C. Guizzardi – 21 Aprile 2009 12
  • 13. Relstorage: pros DBMS Support: - Backup and restore - Redundancy and fault tolerance - Authenticated access to the DB data - Tools of the chosen DBMS - Speed improvements* Plone Conference 2009 – Federico C. Guizzardi – 21 Aprile 2009 13
  • 14. Distributed Architecture: when? Always if possible. Plone Conference 2009 – Federico C. Guizzardi – 21 Aprile 2009 14
  • 15. Plone in the Cloud • Amazon Web Services (AWS) – EC2: Elastic Cloud Computing – S3: Simple Storage Service in practice: a solution for hosting based on virtual servers (XEN) following the principle: "pay only for what you use, as you use it”. Plone Conference 2009 – Federico C. Guizzardi – 21 Aprile 2009 15
  • 16. Plone on Cloud II • Immediate startup – To start working with EC2 (<15 min) – To start a new server (<1 min) • Complete autonomy of management – Turn on a new server when needed – Turn off a server if not needed – Different machine options Plone Conference 2009 – Federico C. Guizzardi – 21 Aprile 2009 16
  • 17. Plone on Cloud III Back to Plone again: It’s possible then to activate or turn off an arbitrary number of instances cloning the same server, implementing a dynamic farm. In particular on AWS: •Elastic load balancing •Autoscaling Plone Conference 2009 – Federico C. Guizzardi – 21 Aprile 2009 17
  • 18. Case1: Logcluster • www.logcluster.org • 3 Zope/Plone + ZEO • Daily updates • 20k requests a day Plone Conference 2009 – Federico C. Guizzardi – 21 Aprile 2009 18
  • 19. Case2: EOL • www.eol.ucar.edu • 5 Zope/Plone + ZEO • 2k pages a day • 32k pages in the first month Thanks to Kelly Craig for the material for this case study. Plone Conference 2009 – Federico C. Guizzardi – 21 Aprile 2009 19
  • 20. Questions? Data on performances and different setups available on request federico.guizzardi@reflab.com Plone Conference 2009 – Federico C. Guizzardi – 21 Aprile 2009 20