frameworks. • A platform that allows you to automatically provision resources. • Enables continuous integration/ continuous delivery. • Allows you to focus on writing cloud native applications.
a reference implementation of Cloud Foundry for the enterprise. • Open source software provides the basis for the Pivotal Cloud Foundry platform. • Pivotal offers additional commercial features, enterprise services, support, docs, certs, etc.
• Has nicer web GUI. • Additional features like auto-scaling, LDAP/AD (SAML) support, metrics server, notifications, Ops Metrics. • Many of the services come installed by default (MongoDB, Neo4J, RabbitMQ, Redis, etc). vs
‘cmd’) • cf -v (gets version) • cf help (gets list of commands) • cf help <command> • cf login -a api.run.pivotal.io • cf target (find out which server) • You will be prompted for your Email and Password.
/ local build artefacts are uploaded to CF (PWS). 2. Auto detection of type of apps you are deploying, appropriate buildpack is installed and a “droplet” (Cloud Foundry unit of execution) is build. 3. Droplet build in a staging area and stored in blob store. 4. Droplet is deployed to droplet execution agent and application is started (route is allotted).
application you are deploying. • It sets up the the proper execution environment on Cloud Foundry. • Only used during the build / staging time - not in the running app. • See available buildpacks: cf buildpacks
domain by default (eg. cfapps.io). • When we deploy an app, we also declare a hostname (eg. sp- miccheng-demo1). • The combo and hostname + domain = route • Hostname can be configured in CLI or manifest.yml. • You can also add custom routes manually to apps.
do with applications. • This includes everything from how many instances to create and how much memory to allocate to what services applications should use. • YAML format. • Online Generator: http://cfmanigen.mybluemix.net
CF runtime communicates with a deployed app about the environment. • cf env <app_name> • Use the manifest file to add environments. • You can also set using CLI: cf set-env OMG “oh my god”
details of a service: cf service <service_instance> • Bind service instance to app instances: • cf bind-service <app_name> <service_instance> • This will add env variables to the app instances.
linux container (LXC) • You can SSH into the container if you need to take a look at what’s going on (eg. troubleshooting, verify file version, etc) • cf ssh <app_name> -i <instance_number>
services that are not available in the marketplace with their applications running on Cloud Foundry. (Reference: http://docs.pivotal.io/pivotalcf/1-7/devguide/services/user-provided.html) • Managed Services for Cloud Foundry - services integrated with Cloud Foundry via APIs, and enable end users to provision reserved resources and credentials on demand. (Reference: http://docs.pivotal.io/pivotalcf/1-7/services/index.html)