You mean I don't have to write a BOSH release?
•Download as PPTX, PDF•
2 likes•315 views
Lightning Talk by Mikey Boldt at SpringOne Platform 2017
More Related Content
Similar to You mean I don't have to write a BOSH release?
Similar to You mean I don't have to write a BOSH release? (20)
More from VMware Tanzu
More from VMware Tanzu (20)
Recently uploaded
Recently uploaded (20)
You mean I don't have to write a BOSH release?
- 1. You Mean I Don’t Have To Write A BOSH Release? MIKEY BOLDT
- 2. You Mean I Don’t Have to Write a BOSH Release? Services on Container Runtime Mikey Boldt, Pivotal CF Platform Eng. @mwboldt
- 4. App App App cf create-service ... cf bind-service ... Service Software Service Broker
- 5. We
- 6. Partners From “7 Stages of BOSH”: http://7-stages-of-bosh.engineerbetter.com/#/6
- 8. Handle complex apps Shareable Configurable Update / Rollback
- 9. App App App cf create-service ... cf bind-service ... Service Software Service Broker
- 10. Kibosh Kibosh: Framework for Helm Services ● OSBAPI Service Broker. ● On-demand deployments. ● Flexible tenancy model. ● Service admin interface. ● Familiar experience for all.
- 11. Marketplace Kibosh (configured for service) Catalog Service Conf UI Service Admin App Dev Provision, Bind App App App Credentials Helm install, Kubernetes API Operator Deploy Plans
- 12. Kibosh (configured for service) Service Conf UI Operator Deploy Plans bosh deploy
- 13. Kibosh (configured for service) Service Conf UI Service Admin Plans
- 14. Marketplace Kibosh (configured for service) Catalog Service Conf UI App Dev Provision, Bind App App App Plans cf create-service ... cf bind-service ...
- 15. Kibosh (configured for service) Service Conf UI Plans Helm install, Kubernetes API
- 16. Kibosh (configured for service) Service Conf UI App App App Credentials Plans Helm install, Kubernetes API
- 17. Marketplace Kibosh (configured for service) Catalog Service Conf UI Service Admin App Dev Provision, Bind App App App Credentials Helm install, Kubernetes API Operator Deploy Plans
- 18. Kibosh: Current Status ● Developed a Helm-chart-configurable Service Broker. ● Offers a single default plan. ● Uses a dedicated Kubernetes cluster for all service instances.
- 19. Kibosh: Yet to Validate ● Explore service configuration UI. ○ Can we auto-generate a UI from Helm chart? ● Automatically get credentials. ○ Do we need explicit configuration?
- 20. But Wait --- There’s More! ● Hsobik: Consume OSBAPI services in Container Runtime (Service Catalog). ● Can we auto-discover Kubernetes services? Expose in Marketplace?
- 21. && not ||
Editor's Notes
- Our team at Pivotal, Cloud Foundry Platform Engineering, has spent the last few years focused on building our ecosystem of partner services. We now have over 60 partner products our customers can download and use.
- A common pattern: package up software as a BOSH release, put an OSBAPI service broker in front of it. Gives operators and developers familiar experience.
- We love BOSH. Does great things for the software lifecycle and operations. It is the shoulders upon which CF stands.
- Partners struggle with BOSH. They typically haven’t used it before. Steep learning curve makes it high cost. Not widely used outside of CF makes it low reward.
- Container Runtime opens up a new opportunity. K8s more widely used, simpler, software vendors often already have a deployment ready.
- Helm charts provide easy, shareable, customizable k8s deployment.
- So if we use Helm for the service software deployment, all we need now is a service broker. Wouldn’t it be nice if we could make that easier too?
- Kibosh: a generic service broker for helm charts. Goal: no code!
- To be fair, this is our vision, WIP.
- Partners will package up Kibosh configured for their service software. With Pivotal CF, an Ops Manager tile. With open source Application Runtime, they could provide a BOSH deployment. These are familiar ways for operators to deploy services.
- For the service administrator, we will present a Service Configuration interface. Here, the admin can define plans, manage data, etc. We envision either a generated UI, based on helm chart configuration options, or a custom UI provided by a partner.
- Application developers don’t care that the services are running in Kubernetes. They just use the familiar `cf create-service` and `cf bind-service` commands to use the service in their apps.
- To create a service instance, the developer chooses a plan and the target Kubernetes cluster. Kibosh performs a `helm install` of the service.
- On binding, Kibosh will expose the Kubernetes secrets from the service instance to the bound app. It will also provide the endpoint of the service per the Kubernetes Service objects.
- So, that’s our grand vision for services on Container Runtime. We’ve started in on implementing a PoC, and it’s gone well so far.