[
https://issues.apache.org/jira/browse/ACE-152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Angelo van der Sijpt resolved ACE-152.
--------------------------------------
Resolution: Fixed
Turns out there is no way to influence jclouds in which directory to use (in
1.0-beta9). In stead, I added a 'cd ~' to the node bootstrap script.
> Move jclouds storage location out of /tmp
> -----------------------------------------
>
> Key: ACE-152
> URL: https://issues.apache.org/jira/browse/ACE-152
> Project: Ace
> Issue Type: Task
> Affects Versions: 0.8.0
> Reporter: Angelo van der Sijpt
> Assignee: Angelo van der Sijpt
>
> The targets that are set up by the current AmazonNodeLauncher will run from
> the system's /tmp; the standard Amazon images have a cron job that runs
> tmpwatch on /tmp and removes all files that haven't been touched in the last
> 10 days. We don't want this to happen to our frameworks.
> We should probably use Amazon's EBS for our storage, and think about a way of
> 'moving them around' among instances (i.e., keeping the notion of target on a
> single EBS, not worrying about the compute hardware on which it runs.
> For now, we can just move out of the /tmp, and run somewhere else on the
> instance storage.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
