How AppFog Brought PHP to CloudFoundry

CloudFoundry Community Update

How Appfog contributed PHP support to CloudFoundry.

Transcript

1. How AppFog Brought PHP to CloudFoundry Jeremy Voorhis Senior Engineer, AppFog Inc jeremy@appfog.com @jvoorhis http://www.appfog.com Wednesday, January 18, 12
2. Part I Building PaaS From Scratch, Choosing CloudFoundry Wednesday, January 18, 12
3. The Three Layers of PaaS • User Experience • Application Lifecycle • Infrastructure Orchestration Wednesday, January 18, 12
4. User Developer Experience • Support • Plans, pricing and billing • User interface (web, mobile) • Tools (CLI, version control) • Add-ons Wednesday, January 18, 12
5. Application Lifecycle • HTTP Pipeline • Runtime and Framework Support • Deployments • Services (Relational Database, Message Broker, etc.) • App Configuration (Env. Vars, Service Connections, URLs) Wednesday, January 18, 12
6. Infrastructure Orchestration • Scale infrastructure to meet demand • Configuration management • Monitoring • Log correlation / retention Wednesday, January 18, 12
7. What is ? • PaaS tailored specifically for PHP developers • Apache, MySQL, Varnish, Git • Private Git hosting, Git deployments • App Console • Add-on Program • Built all 3 layers ourselves! Wednesday, January 18, 12
8. is our eponymous, open PaaS • Exchanged our app lifecycle tier for CloudFoundry • 7 pull requests plus customization • Multi-lang, multi-service • Git agnostic (deploy from Maven, Eclipse, Github or Dropbox!) Wednesday, January 18, 12
9. Why build our new PaaS on CloudFoundry? • Path to adding languages and services • Commitment to open source • Vibrant community • Focus more effort on UX and Infrastructure Orchestration • Support AWS, Rackspace, Joyent, HP Public Clouds Wednesday, January 18, 12
10. PHP Fog / CloudFoundry Comparison Wednesday, January 18, 12
11. Similarities • N-tier architecture • Isolates apps in multi-tenant environments • Scales on demand • Manages configuration Wednesday, January 18, 12
12. PHP Fog Innovations • Best in class UX • HTTP caching (Varnish) • Wildcard subdomains, HTTPS termination for custom domains • Git deployments Wednesday, January 18, 12
13. CloudFoundry Benefits • Simplifies adding runtimes, frameworks, services • Orchestration-agnostic • Excellent code quality Wednesday, January 18, 12
14. Build or embrace? Wednesday, January 18, 12
15. IT’S DANGEROUS TO GO ALONE! TAKE THIS... Wednesday, January 18, 12
16. Part II How We Extended CloudFoundry to Support PHP Wednesday, January 18, 12
17. Our PHP Stack • Apache 2 • PHP 5.3 • Popular PHP modules • Varnish cache Wednesday, January 18, 12
18. Seven Accepted Pull Requests and Counting! • vmc • vcap • vcap-tests • nats Wednesday, January 18, 12
19. State of OSS PHP Support in CloudFoundry • PHP stack installed by vcap_dev_setup • PHP apps automatically detected by vmc • Apache2 runs single app in foreground • Integrates with CloudFoundry secure user pool • Available now from Github Wednesday, January 18, 12
20. Work in Progress • Varnish cache invalidation for vcap • Custom DEA supports secure multi-tenant Apache2 • Orchestrate single tenant DEA • Available now in AppFog Private Beta Wednesday, January 18, 12
21. Future of CloudFoundry • Improve documentation! • Fix CloudFoundry.com vs CloudFoundry.org confusion • Independent governance can provide extra peace of mind Wednesday, January 18, 12
22. Thank you CloudFoundry team! • Was a joy to work with CF dev team • Thank you Derek Collison! • Thank you James Watters! Wednesday, January 18, 12
23. Thank you! Jeremy Voorhis Senior Engineer, AppFog Inc jeremy@appfog.com @jvoorhis http://www.appfog.com Wednesday, January 18, 12