Custom Tile Generation in PCF
Download as PPTX, PDF0 likes849 views
The document outlines the process of custom tile generation in Pivotal Cloud Foundry, focusing on the memory-based autoscaler application. Key steps include creating a service broker, implementing endpoints, and managing dependencies such as databases and buildpacks. The document also provides links to relevant tools and resources for further information.
Custom Tile Generation in PCF
- 1. • Tom Collings Cloud Architect, ECSTeam @tomcollings303 tcollings@ecsteam.com • Dustin Ruehle Cloud Architect, ECSTeam @dustinruehle druehle@ecsteam.com Custom Tile Generation in PCF
- 2. What are you going to see?
- 3. What are you going to see?
- 4. What are you going to see?
- 5. Feedback control– Memory based auto-scaling memory-based-autoscaler nozzle firehose Pivotal Cloud Foundry misbehaving memory app
- 6. Feedback control– Memory based auto-scaling memory-based-autoscaler nozzle firehose Pivotal Cloud Foundry misbehaving memory app
- 7. Feedback control– Memory based auto-scaling memory-based-autoscaler nozzle firehose Pivotal Cloud Foundry misbehaving memory app
- 8. Feedback control– Memory based auto-scaling memory-based-autoscaler nozzle firehose Pivotal Cloud Foundry misbehaving memory app
- 9. What does this nozzle app do?
- 10. Turn app into service broker
- 11. Turn app into service broker
- 12. Step 1: Turn into a Service Broker • Had to implement the five endpoints
- 13. • Need a dashboard to start/stop scaling, set parameters • Need endpoint in the app to provide/update that data • Need a way to link to that dashboard from PCF ecosystem Step 1: Dashboard
- 14. Step 1: Attaching to Apps Console • Return a specific field in the JSON on the create service instance method: {“dashboard_url”:”http://memory-based-autoscaler-web.apps.labb.ecsteam.io/{service instance guid}/{app name}”} • This links the dashboard to the apps console “Manage” link
- 15. • With single-tenant, app failures not a problem • With multi-tenant, need to protect against app failures, updates, etc… • My-sql database • Need to create tables if they don’t exist • Initialize app based on state in db • New dependency for broker Step 1: Persistence
- 16. So why not just a Service Broker?
- 17. Tile Definition • .pivotal file • A zip containing the executables and bosh manifest • Self-Contained functionality • Can include • Bosh-managed VMs • Applications • Service brokers • Buildpacks • Combination of all • Managed through Ops Manager console • Configured, deployed, upgraded, etc…
- 18. When to Develop a Custom Tile • Need to provision services for the system • Self-contained custom functionality • May have a different lifecycle than applications • May have different use permissions than other applications • Integrate third-party functionality • Databases, message brokers, etc… • New VMs inside the foundation • bosh can manage these
- 19. Current method of generating a tile • Generate a bosh manifest • Create a product template • Add lifecycle errands (more bosh) • Package up applications, manifests, etc… into .pivotal tile • (optional) migration file
- 20. • bosh • Very manual, difficult to automate • No syntax checking, have to deploy to find errors Issues with Current Method Learning curves of popular technologies Skill Time Java Spring Spring Boot Bosh
- 21. Tile-Generator
- 22. Step 2: begin tile generation • Install tile utility • pip install –r requirements.txt • May need to install pip • bosh cli is also a requirement • tile init – create shell tile.yml file • Modify tile.yml
- 23. Step 2: Header # The high-level description of your tile. # Replace these properties with real values. # name: memory-based-autoscaler # By convention lowercase with dashes icon_file: resources/icon.jpeg label: Memory Based Autoscaler description: Performs an automatic scaling of apps based on the memory usage of a bound application.
- 24. Step 2: Orgs and Spaces org: p-scaling-org org_quota: 4096 space: p-scaling-space apply_open_security_group: true
- 25. Step 2: packages packages: - name: memory-based-autoscaler type: app-broker manifest: path: memory-based-autoscaler.zip command: memory-based-autoscaler memory: 512M buildpack: https://github.com/cloudfoundry/go-buildpack.git needs_cf_credentials: true auto_services: - name: p-mysql plan: 100mb-dev enable_global_access_to_plans: true
- 26. Packages notes • Several types of packages are available: • app • app-broker • external-broker • buildpack • docker-bosh • docker-app • docker-app-broker • blob • bosh-release
- 27. Step 2: stemcell stemcell_criteria: os: ubuntu-trusty requires_cpi: false version: '3232'
- 28. Step 2: properties properties: - name: example_property type: string default: specify a value label: Label for the field on the GUI description: Longer description of the field's purpose
- 29. Step 2: forms forms: - name: security label: Security description: Connection Security Parameters properties: - name: skip_ssl_validation type: boolean default: false label: Skip SSL Validation for self-signed certificates when connecting to the firehose description: Skip SSL Validation for self-signed certificates when connecting to the firehose
- 30. Step 2: dependencies requires_product_versions: - name: p-mysql version: '~> 1.7'
- 31. Step 3: build the tile tile build • Creates the .pivotal file • Updates tile-version.yml
- 32. Step 4: Upload, configure, and apply changes • What happens: • Org and space get created • New admin user gets created • Application gets deployed • p-mysql service gets created and bound to the app • App is registered as a service broker and enabled for all orgs, putting it in the marketplace • Environment variables (including admin user/password) are bound to the application • Now apps can bind to instantiated services
- 33. Demo – Create a tile
- 34. Demo – Use the tile
- 35. Where to go for more info • Our sample https://github.com/ECSTeam/memory-based-autoscaler https://github.com/ECSTeam/memoryautoscaler-web • Tile Generator https://github.com/cf-platform-eng/tile-generator • Pivotal Ecosystem https://network.pivotal.io/ecosystem
- 36. Questions?
Editor's Notes
- #13: App originally was only able to scale one app at a time Store key/instance values in a map Follow the autoscaler approach with explicit start/stop scaling operations
- #14: Old, single-tenant scaler was based on env variables for the single app
- #17: Deployment/management of a service broker is somewhat manual Gets even more manual when dependent services (mySQL, Rabbit) are involved Lifecycle (including deletion of services) gets even trickier to manage
- #22: New utility from pivotal https://github.com/cf-platform-eng/tile-generator Takes a lot of the manual steps out of the equation Makes pipelining easier