2. • Portals ran on large, beefy,
expensive machines
• Developed Deployment
Anti-patterns
3. • Involves Install Cookbooks
• Boring and Repetitive = Errors
• Requires a Jedi Master to Debug
– Don’t Get Hit by a Bus Anti-Pattern
• Not a Good Use of Resources
4. • Assume Development Environment is
the Same as Production.
• Assumptions = Killer
5. • Servers have Personalities
• Manual Configuration / Debugging
• Changes are not Propagated
• Unable to Reproduce Errors
6. • Mass produce “Servers”
• Problem of Sprawl
– 125% year increase in servers
• How do you deal with configuration
differences between dev, test, stage,
prod?
7. • Empower our Portal Teams
• Reduce Errors
• Lower Stress
• Flexibility
• Everyone can Deploy Quickly
8. • Continuous Integration
– Prove your software works with each commit
• Benefits
– Build is Repeatable
– Early Warning of Problems
– Wiring and Configuration that Works
– Effective Teams
• Use Continuous Integration with Portal and
Portlets
9. • An Application is composed of
Binaries, Data and Configuration.
• Artifact Repositories
– Maven
– Yum (rpm)