Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Sebastien goasguen cloud stack the next year
Similar to Sebastien goasguen cloud stack the next year (20)
More from ShapeBlue
More from ShapeBlue (20)
Recently uploaded
Recently uploaded (20)
Sebastien goasguen cloud stack the next year
- 1. CloudStack VP thoughts Sebastien Goasguen @sebgoa
- 2. Background • Citrix Open Source Architect • VP of Apache CloudStack • PMC of Apache libcloud • ASF member • O’Reilly author of the CloudStack and Docker cookbook • Dr. even Prof.
- 5. Community Plan “Cleaning the house” Engineering Roadmap
- 6. Cleaning the house http://s.apache.org/coS2 •Code and Infra •Ecosystem •Events / Marketing •Documentation •Website
- 7. Code -cleanup • Remove AWSAPI ( ~1M LOC) • IP clearance for EC2stack and GCEstack now officially Apache CloudStack subprojects • Static analysis and focus on code quality but removal of dead code. Future of CloudStack architecture in a Docker, Mesos, Kubernetes world
- 8. Infrastructure -cleanup • No more Review Board • All contributions come as GitHub pull request • Increased time and priorities on Travis • More and faster testing • Simulator automatically packaged as Docker image • New release management process
- 9. Ecosystem • CloudFoundry deployment • Cleanly publish all config management recipes • Get CloudStack Ansible module in core (e.g 2.0) • Expand Go client for better support in: – Terraform – Docker machine • Define “stack” catalog to easily provision Hadoop, Storm, Spark clusters
- 10. Events • CloudStack Days – Austin – Tokyo, June 2 – Seattle, August 20th • CloudStack European Conference – Dublin October 8th – 9th
- 11. Documentation
- 12. Documentation • New theme • Cleanup of old docs • Consolidation of wiki pages • Re-think the doc structure • Better multi-language support • All git based, mirrored on Github • Automatically built with Readthedocs.org
- 13. Website • Now moved to Git • Mirrored on GitHub and accepting pull requests • Using middleman instead of apache CMS Need an actual modern Design
- 15. Upgrade – e.g • Database upgrade tools • Schema versioning • Agent upgrades • SystemVM upgrades • Rollback • Docs uprade
- 16. Logging / Metrics – e.g • Better error handling • Log processing • MDC system (logback) • Correlation of resources in logs
- 17. Storage –e.g • Improve objet storage • Fix swift interface • Remove NFS dependency • Shared data disk • Snapshots on SAN • Migrate secondary storage
- 18. Networking – e.g • IPv6 • Network ACLs • Improve VR • API to VR • Extend VPC in physical nets • Reserved CIDR
- 19. UI, API – e.g • RBAC • 2 Factor auth • Annotations • SAML plugin • SSH key management in UI • Billing quota
- 20. QA – e.g • Better tests • Test environment • QA • Driver certification • Crowdsource of QA • Performance
- 21. Next • These bug fixes and feature request will go to the community as a proposed roadmap • Participating companies have already committed to solving some of those items
- 22. Architecture • Need for: – Better abstractions between all layers – Contractualized guarantees between these layers • To: – Coordinated access to resources with strong guarantees – Operational integrity – Higher feature velocity – Easily composable and configurable
- 23. Architecture -e.g • Refactor management core • Refactor API server • Use embedded jetty • Use a YAML based config like cassandra and elasticsearch • Persistence Layer – Remove DAO There is a proposal for first steps to take
- 24. Benefits • Simple configuration and Upgrade • Even easier installation • Clean plugin framework • Decoupling of the code to help development • Pluggable implementations (e.g database, network) • Abstraction of compute (e.g containers, VMs) • Use of external resource allocators (e.g Mesos)
- 25. Thank you … Contribute, Share … Sebastien Goasguen @sebgoa