[ 
https://issues.apache.org/jira/browse/WHIRR-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13141450#comment-13141450
 ] 

Paul Baclace commented on WHIRR-424:
------------------------------------

When I use Whirr, I compose whirr.config (common stuff + variable stuff + 
derived stuff) where derived stuff is calculated from variable stuff like type 
of machine.  

During post-processing when Whirr finishes, I "cp -r" the directory Whirr 
created and copy the composed whirr.config into it so I can keep notes about a 
run. 

It would be nice to have this built-in ("keep instead of remove after 
terminated").  I also have a snapshot mechanism that captures a tar-gz of a 
list of files relative to / to capture config files "as built".  That way I can 
examine them after the ensemble is terminated.

As mentioned in another jira item the instances file generated by Whirr can be 
used for reference and to avoid expensive ec2 api (or other provider equiv) 
calls.

Log output of Whirr is best kept in the directory it generates. 

Whirr cluster destroy can touch a file "_Terminated" after termination.


                
> Persist the cluster spec as part of the cluster state
> -----------------------------------------------------
>
>                 Key: WHIRR-424
>                 URL: https://issues.apache.org/jira/browse/WHIRR-424
>             Project: Whirr
>          Issue Type: Sub-task
>          Components: core
>            Reporter: Andrei Savu
>             Fix For: 0.8.0
>
>
> I think we should persist the cluster spec .properties (or .yaml later) file 
> as cluster state information. This is going to be really useful when trying 
> to find the differences between the the currently running cluster and the one 
> describe by the configuration file. This should allow us to have a nice 
> implementation for a "converge" action. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to