Cloud Foundry

SAP Cloud Platform Cloud Foundry - a PaaS environment for development and runtime

Buildpacks - defines a container for running an application by downloading dependencies while deploying the apps

Services - set of programs that are offered to all the different run-time via marketplace(Catalog of available services) for creating service instance.

Droplet - CF unit of execution for the app, created with cf push

Spaces are standard working area/environment for individual applications. It has dedicated allocation of resources(memory, routes, services) from global account.

Route - URL mapped to dedicated app

Application manifest - manifest.yml - used by the “cf push” command for setting up the environment when the app is deployed to CF

---

applications:

- name: my-app

  buildpack: nodejs_buildpack

  command: node app.js

  memory: 512M

  disk_quota: 512M

  instances: 2

  host: myapp-cf-nodejs

  services:

  -mymongodb_srv

-------------------------------------------------------------------------------------

Command Line Interface CLI - helps in managing apps on CF

http://cli.cloudfoundry.org - CLI reference guide

• Display CLI version installed

cf -v

• Login to cloud foundry account

cf login -a api.run.pivotal.io

cf login -a api.cf.eu10.hana.ondemand.com

• Push/deploy and start the application in CF ( creates Droplet)

cf push your_app

• Check the recent logs : Time | Category |

cf logs myapp --recent

cf logs myapp | grep -v RTR

• Check environment variable for the application

cf env <your_app>

• Set user provided variable for the application

cf set-env <your_app>

• Check the list of available buildpacks

cf buildpacks

Binding a Service Instance to an app

• List the available ElephantSQL service plans on marketplace

cf marketplace -s elephantsql

• Create a service instance with the free service plan - eg turtle

cf create-service <service> <plan> <my-service-instance>

• delete service instance with the free service plan - eg turtle

cf delete-service <my-service-instance>

• Bind the newly created service instance to the app. Once a service is bound to an app, env variable VCAP_SERVICES are stored that allow the app to connect to the service after a push, restage, or restart command.

cf bind-service <my-app> <my-service-instance>

• Restart the app

cf restart <cf-spring>

• Verify the new service is bound to the app

cf service <my-service-instance>

• Display all the services with name, plan and bound app details

cf services

cf services | grep <my-service-instance>

Bind a Service Instance to a Route

Binding a service instance to a route will cause application requests and responses to be proxied through the service instance, where it may be used to transform or intermediate requests.

cf bind-route-service shared-domain.example.com --hostname my-app my-service-instance

Vertical Scaling - Increasing the available disk space or memory can improve overall app performance.

• Increase the memory limit for each app instance:

cf scale cf-spring -m 1G

• Increase the disk limit for each app instance:

cf scale cf-spring -k 512M

Horizontal Scaling - Adding more instances allows your application to handle increased traffic( user load and concurrent requests) and demand.

• Increase the number of app instances from one to two:

cf scale cf-spring -i 2

• Check the status of the app and verify there are two instances running:

cf app cf-spring

Tools

• https://console.run.pivotal.io - sunilchandra007

Kibana - Open Source logging and data visualization platform - Provides dashboard