Mailing-List: contact ace-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ace-dev@incubator.apache.org
Date: Tue, 21 Jun 2011 09:28:48 +0000 (UTC)
From: "Angelo van der Sijpt (JIRA)" <jira@apache.org>
To: ace-dev@incubator.apache.org
Message-ID: 
 <1181110859.23813.1308648528662.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (ACE-152) Move jclouds storage location out of
 /tmp
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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