Advanced Proxying
Good things to know - Any Zarafa server is an entry point for your multi-server environment - All requests are redirected ...
Why proxying? - Scales on the Application-Level, because: - With round-robin DNS it scales very well and overhead is very ...
Hardware SSL-Balancers - Yes, they work - They are a bit expensive, but if you can afford – go for it ;) - Be aware that t...
LVS (Linux Virtual Server) - Yes, they work as well - It is indeed a good approach, but requires higher skills and a speci...
Balancing with Apache 2.2 - Works out of the box with most Systems - Helps you scale to whatever you Want or to - Fully co...
Apache Proxying - You need SSL, at least only this makes sense - Sticky sessions by mod_rewrite <ul>  </ul>
Config (I) ### Cookie Handling RewriteEngine On # Cookie not set? Well then, here we go... RewriteCond %{HTTP_COOKIE} !BAL...
Config (II) ### Load-Balancing by the cookie value to internal zarafa-vhost ProxyPass / balancer://cluster/ lbmethod=byreq...
Proven Architecture <ul>  </ul>
Endless Possibilities - Secure your cluster with Pacemaker (following up) - Combine with zarafa-msr for direct (non-proxie...
Recommendations - Make sure you share your state-dir (z-push) like NFS - Think of clustered Mail delivery - Auto-Updater (...
Contact - Thank you very much for listening! - Don't hesitate to contact us for questions or support. Millenux GmbH Lilien...
Upcoming SlideShare
Loading in...5
×

20110701 zsc2011-advanced proxying-formatted

990

Published on

Presentation of Michael Kromer

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
990
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
8
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

20110701 zsc2011-advanced proxying-formatted

  1. 1. Advanced Proxying
  2. 2. Good things to know - Any Zarafa server is an entry point for your multi-server environment - All requests are redirected if they not belong to them - Zarafa does not act as a proxy - Your store-server has to be able to be reached by the client directly <ul> </ul>
  3. 3. Why proxying? - Scales on the Application-Level, because: - With round-robin DNS it scales very well and overhead is very small (redirection). - It can handle sticky sessions (stay on the same server) <ul> </ul>
  4. 4. Hardware SSL-Balancers - Yes, they work - They are a bit expensive, but if you can afford – go for it ;) - Be aware that they really only balance SSL, nothing else <ul> </ul>
  5. 5. LVS (Linux Virtual Server) - Yes, they work as well - It is indeed a good approach, but requires higher skills and a special setup to be maintained - keeping systems up to date is a bit more work - The combination of pacemaker and this solution outnumbers in scalability <ul> </ul>
  6. 6. Balancing with Apache 2.2 - Works out of the box with most Systems - Helps you scale to whatever you Want or to - Fully compatible with any service, so z-push, webaccess, zarafa, autoupdater all work <ul> </ul>
  7. 7. Apache Proxying - You need SSL, at least only this makes sense - Sticky sessions by mod_rewrite <ul> </ul>
  8. 8. Config (I) ### Cookie Handling RewriteEngine On # Cookie not set? Well then, here we go... RewriteCond %{HTTP_COOKIE} !BALANCEME RewriteRule .* - [CO=BALANCEME:balancer.server1:zarafa.com:15] # IMPORTANT – Renew the cookie! RewriteCond %{HTTP_COOKIE} BALANCEME=(balancer.server1) RewriteRule .* - [CO=BALANCEME:balancer.server1:zarafa.com:15] # Think of failover … covered later Include /etc/apache2/vhosts.d/00-zarafa-cookie-failover.inc <ul> </ul>
  9. 9. Config (II) ### Load-Balancing by the cookie value to internal zarafa-vhost ProxyPass / balancer://cluster/ lbmethod=byrequests stickysession=BALANCEME ProxyPassReverse / balancer://cluster/ <Proxy balancer://cluster> BalancerMember http://server1.zarafa.com route=server1 BalancerMember http://server2.zarafa.com route=server2 BalancerMember http://server3.zarafa.com route=server3 BalancerMember http://server4.zarafa.com route=server4 <Proxy> <ul> </ul>
  10. 10. Proven Architecture <ul> </ul>
  11. 11. Endless Possibilities - Secure your cluster with Pacemaker (following up) - Combine with zarafa-msr for direct (non-proxied) access to store <ul> </ul>
  12. 12. Recommendations - Make sure you share your state-dir (z-push) like NFS - Think of clustered Mail delivery - Auto-Updater (!) <ul> </ul>
  13. 13. Contact - Thank you very much for listening! - Don't hesitate to contact us for questions or support. Millenux GmbH Lilienthalstr. 2/1 70825 Korntal/Stuttgart Tel. +49 711 88770 300 Fax +49 711 88770 349 [email_address] www.millenux.com <ul> </ul>
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×