Skeleton directories

[mikery]

Placeholder for a feature I need to add.

When a snapshot is not found (i.e. first time an instance is booted), a local directory on an already-mounted file system should be used to populate the new volume, rather than formatting it and leaving it empty.

• create the files in the skeleton dir, build AMI
• launch the instance
• no snapshot will be found, so data will be copied from skeleton dir
• < backup is taken, machine is rebooted >
• now that snapshots exist, they are used instead of the skeleton data

Changes:

• add a skeleton_dir attribute to volume class
• cp contents of this dir to volume mount location

[tschellenbach]

Think the signals already allow you to do this quite easily. What do u
think?
On May 19, 2013 2:16 PM, "Mike Ryan" [email protected] wrote:

Placeholder for a feature I need to add.

When a snapshot is not found (i.e. first time an instance is booted), a
local directory on an already-mounted file system should be used to
populate the new volume, rather than formatting it and leaving it empty.

• create the files in the skeleton dir, build AMI
• launch the instance
• no snapshot will be found, so data will be copied from skeleton dir
• < backup is taken, machine is rebooted >
• now that snapshots exist, they are used instead of the skeleton data

Changes:

• add a skeleton_dir attribute to volume class
• cp contents of this dir to volume mount location

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/21
.

[mikery]

post_mount doesn't know if a snapshot was found or not, so it can't know
whether it needs to load the skeleton dir or not. It could check if the
mounted dir is empty, but... yeah :)

I think the cleanest place to add this would be after doing the format:
https://github.com/tschellenbach/Snaptastic/blob/master/snaptastic/snapshotter.py#L184

Thierry Schellenbach wrote:

Think the signals already allow you to do this quite easily. What do u
think?
On May 19, 2013 2:16 PM, "Mike Ryan" [email protected] wrote:

Placeholder for a feature I need to add.

When a snapshot is not found (i.e. first time an instance is booted), a
local directory on an already-mounted file system should be used to
populate the new volume, rather than formatting it and leaving it
empty.

• create the files in the skeleton dir, build AMI
• launch the instance
• no snapshot will be found, so data will be copied from skeleton dir
• < backup is taken, machine is rebooted >
• now that snapshots exist, they are used instead of the skeleton data

Changes:

• add a skeleton_dir attribute to volume class
• cp contents of this dir to volume mount location

—
Reply to this email directly or view it on
GitHubhttps://github.com//issues/21
.

—
Reply to this email directly or view it on GitHub
#21 (comment).