Embed Size (px)
Citation preview
CloudFoundry Summit 2016Review
June 2016
Enikö TörökHead of App Cloud OperationsSwisscom (Schweiz) AG
CloudFoundry Progress 2016 Success Stories Review Highlights of the CF Summit Talks Route Services BOSH 2.0 Application Monitoring in a cloud-native age
Links Q&A
Agenda
CloudFoundry Progress 2016
CloudFoundry Progress 2016
Success Stories
Success Stories
Springer Nature: «from weeks to minutes»
Route Services
Route Services
API’s are contracts
What goes into a modern API? Http(s), JSON, TLS, Oauth, JSON
The Gap: scaling adoption of software is hard
Route Services
scale adoption of Apps with API’s
Route Services
Why route services? Enable developers to automatically insert services into
request path for their application and configure them for their needs
Marketplace integration via service broker Increasing developer velocity trough automated, self-
service integrations
Route Services
What is routing? In CF, the process by which requests to apps are being
forwarded to their destination
CF may move app instances around DEVs manage the URLs their applications receive
requests for
Route Services
3 Major use cases for CF Route Services Performance/reliability Real-time analytics, metering Compliance, security, audit
How Route Services work
Route Services
Route Services
API Management API Management helps scalable adoption:
visibility/analytics, security, development Apigee Management API can be integrated through CF
route services
Youtube DEMO
BOSH 2.0
BOSH 2.0
«cf create-service» Deploy dedicated resources
Managing stateful services is hard!
BOSH 2.0
BOSH 2.0
cf create-service = bosh deploy
BOSH 2.0
BOSH 2.0
BOSH 1.0 manifest generation challenges CPI-specific resource definitions Static IP management Manually create multi-AZ deployments via multiple BOSH
jobs
BOSH 2.0
New features Dynamic IP management Global Cloud Config 1st class support for multi-AZ job striping Manifest enhancements
Operational Challanges Potential for lots of BOSH deployments Resource usage monitoring
IaaS limits? How much control to give app developers?
Is my App still up? Application Monitoring in the cloud native age
Application Monitoring in the cloudnative age
What does it mean to be cloud-native? Container packaged Dynamically managed Microservices oriented
Why do we monitor? To catch problems before they become major/unrepairable Sleep like a Boss
Application Monitoring in the cloudnative age
What do we monitor? Latency, Bounce rate, Errors
How do we monitor? Request tracing (e.g. Zipkin, http://zipkin.io) Binding monitoring services -> DynaTrace, NewRelic, AppDynamics Log output (e.g. logalyzer cf plugin) Monitoring java apps via JMX (e.g. expose JMX via ssh) Monitoring Go via pprof Monitor everywhere (not only prod, also dev/test/others)
Alerting -> Leverage your monitoring data
Links
Links
Event website: https://www.cloudfoundry.org/community/summits/program/about/?summitId=10016
Schedule: https://cfsummit2016.sched.org/
Videos & Slides: https://www.youtube.com/playlist?list=PLhuMOCWn4P9gGrKEtCBKYpEl5BXGBCsQZ
https://cfsummit16.scapp.io/slides.md#/
DevOps
(DevOps) PaaS Operations Engineerhttps://direktlink.prospective.ch/?view=6FF25316-735E-4C5A-9ED1373B883686F7&showOld=1
We are hiring…
Enikö TörökHead of App Cloud OperationsSwisscom (Schweiz) [email protected]#eni0706
Thank you!
Any Questions?
