IaaS will remain relevant for delivering traditional third-party applications. The OpenStack project aims to produce an open source cloud computing platform that is easy to use, simple to implement, and interoperable. As cloud services evolve, OpenStack should consider developing constructs to better support services like PaaS and SaaS as tenants, while still minimizing non-core dependencies and ensuring basic interoperability and oversight. Open standards could help abstract service APIs and facilitate integration with the OpenStack core over time.

1. Why IaaS will remain
relevant
How can we support the Cloud of the future?

2. • Evolution of cloud
• Should/how can OpenStack support this evolution?
• Open Service Broker Framework
• UKCloud dataservices

3. Evolution of cloud

4. The OpenStack Mission: to produce a ubiquitous Open Source Cloud Computing platform
that is easy to use, simple to implement, interoperable between deployments, works well
at all scales, and meets the needs of users and operators of both public and private clouds.
Developers shouldn’t
care about applications
that don’t drive direct
value for their
application
IaaS is really well
understood for
delivering traditional
third party applications.
OpenStack is AWESOME
at IaaS!
BaaS
IaaS
PaaS

6. Do you align with
the OpenStack
mission?
Do you follow the
OpenStack way?
• Open source license
• Open community (leaderhsip etc)
• Open development (using gerrit etc)
• Open design (maillists etc)
Do you ensure basic
interoperability?
• e.g. keystone support?
Have you submitted to
the technical committee
for oversight?

7. Most services follow the same make-up
• Generally a similar architecture with some form of control plane and
user space
• Deployment orchestration
• Handling failover
• Handling updates and upgrades
• Handling backups and restores
• Provide a UI/API interface to operate

8. A separate set of as-a-service governance
• It’s basically just SaaS, treat it like a tenant?
• Maybe OpenStack should develop a special service tenancy construct?
• Build on the OpenStack core and try to minimise non-core
interdependencies
• Track interdependencies as a marker for integration to core
• Abstract service API’s behind an open standard for operating cloud
• Offer project due-diligence (number of contributors, lifecycle etc)
• Maybe over time a set of libraries for common tasks can be
developed

9. Open Service Broker

10. Data services
Architecture

11. Demo

12. Resources
• https://www.openstack.org/videos/vancouver-2015/the-big-tent-a-
look-at-the-new-openstack-projects-governance
• https://www.anynines.com