As the end-user of NDS Labs, I should be able to configure a new stack in as few keystrokes/clicks as possible. We currently assist the user in choosing a name to some degree, but there can be issues when collisions arise.

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

I strongly believe that this bug is caused by the current way in which we assign "default names" to stacks and volumes via the config wizard. More discussion/investigation is needed as to how we might avoid such collisions, specifically surrounding our discussion with the LoadBalancer and how that might use the stack names.

This story is complete when we have a new JIRA ticket outlining the changes necessary to remove the possibility of a collision occurring. This will likely need to be done after we decide how, if at all, we plan to use stack/volume names within the LoadBalancer setup.