6. Solutions! (1)
• Manual configuration
• Error-prone
• Time consuming
• Works until you have to deal with a several dozens
of servers on a daily basis
7. Solutions! (2)
• Golden images
• Quite heavy
• Hard to transfer between various autonomous
systems
• Hard to modify seamlessly
• Hidden (and most probably undocumented)
configuration details
8. Solutions! (3)
• Configuration management
• It’s all about the state of your servers/services
• Treat your infrastructure as code
• Define policy once, reuse everywhere
• Reduce complexity
• Reconstruct business from code repository, data
backup and compute resources
22. Why you should care?
• Never hear 'works on my machine' again
• Keep track of your CQ servers
• Ability to recreate your infrastructure from
scratch anytime you need it
• Helps you scale horizontally
• Rapid package deployments
• Improved development workflow
23. Current status
• Only CQ 5.6.x is supported
• Full CQ installation
• CQ JVM tuning
• Run CQ as Linux daemon
• User management
• CRX package management
24. Roadmap
• CQ users improvements (groups support)
• New resources
• cq_agent (replication & flush)
• cq_bundle (OSGi configuration)
• CQ 5.5 support
• More automated tests
• Public release within the next few weeks!