From 327932fb41d1b8d47ca59e83cae48285e714fd76 Mon Sep 17 00:00:00 2001 From: keaty Date: Fri, 21 Apr 2017 15:08:18 -0400 Subject: [PATCH] Update local stories to match new gcp development backlog where necessary --- concourse.prolific | 4 +++- deploy_local.prolific | 28 +++------------------------- 2 files changed, 6 insertions(+), 26 deletions(-) diff --git a/concourse.prolific b/concourse.prolific index af1c703..825c566 100644 --- a/concourse.prolific +++ b/concourse.prolific @@ -5,7 +5,9 @@ Okay, the training wheels are coming **off**. This Concourse deployment is gonna Concourse is a Pivotal-sponsored, pipeline-based, continuous integration and deployment (CI/CD) system. The "pipelines" are a collection of [three core concepts (jobs, tasks, and resources)](http://concourse.ci/concepts.html) that you'll learn more about in upcoming stories. While CI may call to mind test automation, Pivotal teams use it for so much more than that. Take a stroll around the office and check out the jobs up on the CI screens to get a general idea of how broadly we use it to automate all that is automate-able. ### How? -You already have a BOSH Director, a cloud-config, and at least one stemcell, so all that's left is to prepare your deployment manifest. You can follow **[these instructions](https://github.com/cloudfoundry/bosh-bootloader/blob/master/docs/concourse.md)** to set it up and BOSH deploy, but as per the yooj there are a few changes... +If you've been doing the Local Development track, spin up a local Concourse VM with Vagrant **[by following these instructions](http://concourse.ci/vagrant.html)**. + +If you're been doing the GCP Development track then you already have a BOSH Director, a cloud-config, and at least one stemcell, so to spin up a full Concourse deployment all you have to do is prepare your deployent manifest. You can follow **[these instructions](https://github.com/cloudfoundry/bosh-bootloader/blob/master/docs/concourse.md)** to set it up and BOSH deploy, but as per the yooj there are a few changes... 1. `bbl` only supports one load balancer at a time so you'll have to delete your CF load balancer before continuing. Bye bye, CF! 1. You'll need to create a new domain and TLS cert following the same instructions as you did when deploying Cloud Foundry. diff --git a/deploy_local.prolific b/deploy_local.prolific index 7dfe046..b9b8ff3 100644 --- a/deploy_local.prolific +++ b/deploy_local.prolific @@ -44,9 +44,9 @@ L: core tools --- Install PCF Dev ### What? -[PCF Dev](https://pivotal.io/pcf-dev) is a slimmed down Pivotal Cloud Foundry that is able to run on a developer machine. This is the quickest way to play with Cloud Foundry to test your applications in the cloud. +[PCF Dev](https://pivotal.io/pcf-dev) is a slimmed down Pivotal Cloud Foundry that is able to run on a developer machine. This is the quickest way to play with Cloud Foundry or test your applications for the cloud. -#### How? +### How? Download PCF Dev from **[Pivotal Network](https://network.pivotal.io/products/pcfdev)** (you'll need a [Pivotal Network Account](https://network.pivotal.io/registrations/new) if you don't have one already). This zip file is not actually PCF Dev, but a script that installs the PCF Dev plugin for the cf cli. It only downloads the PCF Dev image from S3 when you first run `cf dev start`. Get further instructions **[here](https://github.com/pivotal-cf/pcfdev#install)** if you need help! @@ -68,26 +68,4 @@ Successfully logged in to api.local.pcfdev.io as user. **Also PCF Dev:** [pivotal-cf/pcfdev-cli](https://github.com/pivotal-cf/pcfdev-cli) L: core tools --- -Push a Spring app -### What? -Cloud Foundry applications are deployed by `cf push`-ing your code or some compiled artifact. When you push an app, you can optionally include an [application manifest.yml](https://docs.cloudfoundry.org/devguide/deploy-apps/manifest.html) that contains properties about your application's deployment. - -The appropriate [buildpack](https://docs.cloudfoundry.org/buildpacks/) will be selected for you by detect scripts and a 'droplet' will be produced that contains all your application dependencies. This droplet will be uploaded to the cells that run your application instances. - -### How? -1. Run `git clone https://github.com/cloudfoundry-samples/spring-music.git` -1. Navigate to `./spring-music` -1. In the `manifest.yml`, delete the line `random-route: true` -1. Set the disk quota to 1024M -1. Set the number of instances to 2 -1. `cf push` your app - -### Expected Result -`cf app spring-music` will print the app's status, including the URL. Visiting the URL in the browser should show you a list of albums. - -### Resources -[Cf Buildpacks](https://docs.cloudfoundry.org/buildpacks/) -[CF application manifests](https://docs.cloudfoundry.org/devguide/deploy-apps/manifest.html) -L: app-dev, cloud foundry ---- -[RELEASE] Set up local development environment and push app with PCF Dev ⇧ +[RELEASE] Set up local development environment with PCF Dev ⇧