Consider adding optional open-ended exercises to stories

[ljfranklin]

We've gotten feedback that some of the stories were a bit hand-holdy. One possible fix would be to add more open-ended exercises/tasks to stories to encourage exploration.

[dsabeti]

Some ideas:

• Set up an additional network by adding another terraform template to the bbl state directory.
• Stop certain instance groups and see how functionality changes.
• What other ways are there to specify the system_domain?
• What's the difference between --var-file and --vars-file?
• Use bosh instances --ps to understand what's happening on the VMs.
• Explore logs on an instance group. (Maybe a separate story?)
• Trace a change from the manifest all the way to the rendered config template on the instance. (Maybe a separate story?)
• Anything specific for TPMs?

[njbennett]

Sent an e-mail soliciting ideas

[njbennett]

Main feedback was that our thoughts so far are very BOSH focused

• Blue/green deploy
• Deploy a "real app" with a data service

At this point I think this issue could be broken up into three new issues:

• Compile a list of "questions to prompt exploration" independent of existing stories
• Write one (or more) exploration stories that flesh out one of the more complex exploration options (I'm thinking especially of "blue/green deploy", where we'd probably want to offer some guidelines for how to monitor uptime)
• Review existing stories for opportunities to add exploration ideas. This could be pretty time-consuming, so it would be good to get some specifics about which stories would benefit the most from this