1. Josh Odom / josh.odom@rackspace.com / @jrodomUma Goring / uma.goring@rackspace.com Rackspace Hosting Project Atlas Load Balancing as a Service
2. Agenda Product Overview Architecture Overview Load Balancing API 1.0 / 1.1 Next Steps for the Project Demonstration Discussion and Q & A
3. Product Overview Designed to make it easy for users to add load balancing to their existing configuration without having to “roll your own”. Greater demand for customers wanting to move more complex applications to a cloud hosting environment, many see load balancing as a core infrastructure component.
4. Comparison to ELB * Many core features will become extensions in 1.1.
5. Architecture Overview API is implemented using a ReSTfulweb service interface. Apache CXF is used for input validation. Validated requests are sent to the Database Service layer built on top of JPA 2.0 and Spring Once the request is persisted (PUT, POST, DELETE) a response is send back to the request. An asynchronous call (Active MQ) is made to the Zeus backend via a pluggable Zeus driver, with values from the database.
6. Cloud Load Balancing Overview Public API Glassfish Application Server Pluggable Zeus Driver API Validation Service DB Service Routing Logic Active MQ Database Zeus Load Balancer
7. Load Balancing API 1.0 ReSTfulAPI allows for customized solutions to automate load balancer management. Static IP Address – Every load balancer is assigned a dedicated static IP address that can be selectively shared with other load balancers. Support for multiple protocols – HTTP, FTP, LDAP, SMTP, etc. Support for advanced algorithms – random, least connections, round robin. Session persistence - utilize HTTP cookie to ensure subsequent requests are directed to the same nodes. Health check for back-end nodes. Connection management simplify log management.
8. OpenStack and API 1.1 We are in the process of generalizing the 1.0 specification and introducing the concept of extensions in collaboration with Citrix. Once this process is complete, we intend to begin discussion of the specification in the open. Development of a fully open source load balancing reference implementation leveraging HAProxy. Citrix is currently working on a proof of concept.
9. Project Next Steps Deploy code into open code repository. Create developer and operator documentation. Focus on making the product easily deployable utilizing an OSS solution. Ratification of 1.1 specification and development. Development of Citrix NetScalar support.
