With ndslabs-1.0-alpha, stack data is stored in /<volumes>/projects/<volume UID> and the Volume UID is mapped into the stack spec. We are moving to the concept of "home directories" for user accounts. Volume information should be stored in a special user directory, similar to the "Application Data" directory used by an OS.

This includes the following changes:

• When a new account is created, a "home directory" is created for the user under /home/username.
• In the home directory, a new subdirectory is created, such as .appdata
• When the user configures a stack, a subdirectory is created for each stack service: /home/user/.appdata/<uid>
• This volume UID and directory are used in place of the current volume scheme.

Note: We might consider restructuring this to stack/service, for example: /home/user/.appdata/clowder/mongo. However, we will run into problems if there are multiple instances of the same service (e.g., clowder). This could be solved by using the stack name (sxxxx), but this would prevent re-use of data across stacks.