Downloaded 62 times
Uploaded byJames Bayer
Cf summit2014 roadmap
The document outlines the roadmap and vision for Cloud Foundry, including: - The mission is to create an open source PaaS with a thriving ecosystem that allows for continuous delivery and an agile experience. - The vision includes features like instant routing, log aggregation, metrics/telemetry, access controls, high availability, and extensibility. - Key areas of focus are applications, services, and the platform (BOSH). This includes features for application policy, routing, runtime, logs/metrics, and identity/security. - The roadmap is agile but focuses on areas like the Diego project, Docker support, .NET runtime, loggregator improvements, and service
More Related Content
Similar to Cf summit2014 roadmap
Cf summit2014 roadmap
- 1.
- 2. Cloud Foundry Roadmapand Vision James Bayer Cloud Foundry Product Team @jambay
- 3.
- 4. • 34 membercompanies • Will result in more … – Contributors – Communication – Coordination • Evolving development process for more participation while continuing the fast momentum Cloud Foundry Foundation
- 5. • Global industrystandard and scale • Open Source PaaS • Thriving ecosystem • Continuous delivery • Agile experience for contributors • Cloud-native apps and software Mission Statement Key Phrases
- 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. • 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.
- 9. Warning: Agile Roadmaps havea shelf life Image credit to robin24 on flickr Days / Weeks Image credit to thomasjwoods-com on flickr
- 10. Open Proposals andBacklogs Step 1 Step 2
- 11. • Applications • Services •Platform Key Areas Cloud Foundry Elastic Runtime Cloud Foundry Services Cloud Foundry BOSH
- 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. • 12 factorLinux 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. • Policy • Routing •App Runtime • Logs, Metrics and Telemetry • Identity and Security Application Feature Areas
- 15. • Outbound AccessPolicy (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. • A/B approuting % 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. • 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.
- 19. • Loggregator wasa major leap forward • Use Loggregator for system logs • Add app/system metrics to the transport • Pluggable sources and destinations Logs and Metrics
- 20. Logs and Metrics EndState • Multitenant • System and Apps • Metrics, Logs, Telemetry • Pluggable Inputs • Pluggable Outputs
- 21. Metrics in theLogs Prototype
- 22. Metrics Pluggable OutputPrototype
- 23. • LDAP/AD Groupsmapped 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. • Sample v2Service 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. • MariaDB withGalera 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. • 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. • Applications –Cloud Foundry Elastic Runtime • Services – Cloud Foundry Services • Platform – Cloud Foundry BOSH Key Areas
- 28. Cloud Foundry Roadmapand Vision James Bayer Cloud Foundry Product Team @jambay