Cf summit2014 roadmap

3,062 views

Published on

Published in: Technology

Cf summit2014 roadmap

  1. 1. ©2014
  2. 2. Cloud Foundry Roadmap and Vision James Bayer Cloud Foundry Product Team @jambay
  3. 3. MISSION AND VISION
  4. 4. • 34 member companies • Will result in more … – Contributors – Communication – Coordination • Evolving development process for more participation while continuing the fast momentum Cloud Foundry Foundation
  5. 5. • Global industry standard and scale • Open Source PaaS • Thriving ecosystem • Continuous delivery • Agile experience for contributors • Cloud-native apps and software Mission Statement Key Phrases
  6. 6. Cloud Foundry Vision • Instant Dynamic Routing • Log Streams & Aggregation • Metrics and Telemetry • Access Controls & Policy • 4 Layers of High Availability • App-Instance • Availability Zone • Process • Virtual Machine Operational Benefits for each Application Deploy, Operate Update, Scale Platform on Any IaaS ….and more Built-in and Ecosystem Services Extensible Service Broker Architecture • Auto-detect frameworks • “Push and it works” • .WAR • Dockerfile • .NET • Simple service binding • Agile micro-services Simple, Developer Friendly Commands & API Extensible Framework “Buildpack” Architecture • RDBMS (MySQL/Maria HA) • Blob (RiakCS) • Notifications • User-Provided Services • Services Ecosystem (Pivotal, Bluemix, Logsearch.io, OSS)
  7. 7. • Enterprise – Secure, Scalable, and Reliable • Portable – Run on any IaaS - Apps and Services are portable • Open … – Open Source – Open Governance – Open for Extension Core Platform Attributes
  8. 8. ROADMAP
  9. 9. Warning: Agile Roadmaps have a shelf life Image credit to robin24 on flickr Days / Weeks Image credit to thomasjwoods-com on flickr
  10. 10. Open Proposals and Backlogs Step 1 Step 2
  11. 11. • Applications • Services • Platform Key Areas Cloud Foundry Elastic Runtime Cloud Foundry Services Cloud Foundry BOSH
  12. 12. Non-Goals For Now • Multi-region - features baked directly into the CF API and Management – Active/Active – Cloud Bursting – See Cloud Credo blog on Comic Relief • Designing for legacy apps
  13. 13. • 12 factor Linux apps current target – Java, Ruby, Node.js, Go, Python and PHP • Users want more – Dockerfile support for apps – .NET on Windows stack – Persistent file system option for apps • E.g. Active State Stackato FSaaS using ssh-fs Application Types
  14. 14. • Policy • Routing • App Runtime • Logs, Metrics and Telemetry • Identity and Security Application Feature Areas
  15. 15. • Outbound Access Policy (in progress) – Application Security Groups applied to App Containers • Placement Pools – Placing apps on a pool of system components for either network & resource isolation or capability reasons • Buildpack Policy scoped to Organizations • Inbound Access Policy – Router enforcement • Long-term RFE – Tags / Values for CF Models Application Policy
  16. 16. • A/B app routing % controlled via API – Sticky attribute for routes • CF Route custom maintenance / error pages • CF Route access authorization policy • Shared routing table (etcd instead of NATS for example) • Long-term RFEs – Static Route Option – no heart beats required – SNI for Multiple SSL Certificate Management – Multiple routable ports per app – Inbound TCP - likely requires routing aaS per tenant – SSL to Apps Routing
  17. 17. • Diego Project • Zero-downtime and Near-Zero downtime deploys • App Processes from one codebase (web, worker, etc) • Dockerfile push • .NET Buildpack / Windows Stack via Iron Foundry • Ongoing customizable App Healthchecks • SSH access to App Containers • Lifecycle hooks for SCM/CI/Others Application Runtime
  18. 18. Application Lifecycle
  19. 19. • Loggregator was a major leap forward • Use Loggregator for system logs • Add app/system metrics to the transport • Pluggable sources and destinations Logs and Metrics
  20. 20. Logs and Metrics End State • Multitenant • System and Apps • Metrics, Logs, Telemetry • Pluggable Inputs • Pluggable Outputs
  21. 21. Metrics in the Logs Prototype
  22. 22. Metrics Pluggable Output Prototype
  23. 23. • LDAP/AD Groups mapped to OAuth Scopes • Deeper OpenStack Keystone Integration • Audit trail for all APIs • Long-term Considerations – Orgs/Spaces to UAA? – Authorizations – Custom Roles with Permission Mappings Identity and Security
  24. 24. • Sample v2 Service Broker (Github repo aaS) • Database cleanup tool for deleted brokers • Migration path for v1->v2 brokers • Service Dashboard SSO • Service Usage Events • Blob Service (s3 compatible RiakCS) Services 2014 Review
  25. 25. • MariaDB with Galera HA • Notification API and Service Broker • Lifecycle – change plan • Async APIs • Service Audit Events • Custom Metering • Service ACLs with Public/Private Plans scoped to Orgs/Spaces • Custom Plan Parameters • Blob Service (RiakCS, s3, SWIFT) Services Roadmap
  26. 26. • Flexible Versioning • Bring your own CPI • SDN Awareness • Simplify the UX • Shared System Infrastructure – Process Runtime - Evaluate Diego/Docker for packaging / running – Blob – both BOSH and Runtime need blob storage – Databases – Logs, Metrics and Telemetry – Notifications • Backup and Restore of Deployments BOSH
  27. 27. • Applications – Cloud Foundry Elastic Runtime • Services – Cloud Foundry Services • Platform – Cloud Foundry BOSH Key Areas
  28. 28. Cloud Foundry Roadmap and Vision James Bayer Cloud Foundry Product Team @jambay

×