The document introduces Clocker, a project that uses Apache Brooklyn and Docker to manage applications in the cloud. It discusses how Clocker allows defining application topologies and policies using Brooklyn blueprints, deploying applications into Docker containers on automated infrastructure provisioned using Brooklyn and Jclouds, and intelligently placing and orchestrating containers for auto-scaling and high availability. Examples of deploying simple and complex multi-tier applications using Clocker are also provided.
14. Complex Applications
• Service Composition
• Multiple Entities
• Linking via Attributes
• Clusters and Groups
• Enrichers and Policies
• Example
• Cassandra Multi-Region Deployment
• Global Three-Tier Webapp
• Apache Usergrid
• OpenGamma
26/06/2014Copyright 2014 by Cloudsoft Corporation Limited Page: 14
15. Placement
• Adding New Containers
• Choose Hosts Intelligently
• Placement Strategy
• Availability Zone
• Docker Host
• Choices
• Breadth First
• Depth First
• Minimum CPU Usage
• Affinity
• DSL or API
26/06/2014Copyright 2014 by Cloudsoft Corporation Limited Page: 15
16. Policy
• Data Based
• Autoscaling
• High Availability
• Entity Sensors
• Cluster Aggregates
• Windowed Rolling Average
• Too Hot or Cold
• Fixed Limits
• Time Based
• Follow The Sun
26/06/2014Copyright 2014 by Cloudsoft Corporation Limited Page: 16