Add smoke-test errand to cf-deployment

[bsnchan]

Once cf is deployed, we'd like to be confident that cf is running correctly. Can we add the smoke-test bosh errand into the cf-deployment manifest?

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/133478823

The labels on this github issue will be updated when the story is started.

[dsabeti]

Hey @bsnchan seems reasonable that we should provide an easy way to smoke-test the deployment once you've bosh deployed. Does it need to be an errand? How would you and your team feel if we provided a concourse task instead?

[ryanmoran]

@dsabeti the smoke-tests are helpful to have as an errand so that they can be tested through BOSH, by folks who don't have a Concourse installation. Even though many teams within CF will probably benefit from a Concourse task, having an errand is still important because folks outside of CF want this without needing Concourse. Basically, as a minimum for what to expect from folks who run this, expect that they will have BOSH, but not Concourse.

[dsabeti]

@ryanmoran That makes sense. I'll prioritize the story.

[cppforlife]

@dsabeti @ryanmoran will be doing a round of polish on errands soon. planning to introduce a way to run errand off of existing service lifecycle machine.

[dsabeti]

This change is (finally) on master.