As the end-user of NDS Labs, I should be able to add an optional service to an existing stack, so long as the stack is in a "stopped" state. Currently when adding a new service that should require the user to configure volumes or passwords, no facility is given to gather that information.

The user should be able to specify (at the very least) volumes and basic/advanced config options if they need to when adding an optional services. The purpose of this story is to discover all potential needs of an arbitrary optional service and decide on a way for the user to specify these parameters when adding a new service to an existing stack.

See https://github.com/nds-org/ndslabs/issues/25 for more information

This story is complete when we have a new JIRA ticket listing of any details that an optional service would need to collect before being added to the stack, and outlining a scenario for collecting such details.

For extra credit: think of a way to reuse/share logic between this new prompt and the configWizard.