You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whirr.apache.org by "Andrei Savu (JIRA)" <ji...@apache.org> on 2011/03/04 09:16:36 UTC
[jira] Commented: (WHIRR-246) Single place to store/load cluster
state
[ https://issues.apache.org/jira/browse/WHIRR-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13002501#comment-13002501 ]
Andrei Savu commented on WHIRR-246:
-----------------------------------
I like the idea of moving the logic for state persistence in a single place. How about storing this info outside the local machine by using the BlobStore API and displaying it as output for ./bin/whirr list-cluster? Should we rename ClusterStore to ClusterState? (more self-explanatory to me)
> Single place to store/load cluster state
> ----------------------------------------
>
> Key: WHIRR-246
> URL: https://issues.apache.org/jira/browse/WHIRR-246
> Project: Whirr
> Issue Type: Improvement
> Reporter: David Alves
> Priority: Minor
> Attachments: WHIRR-246.patch
>
>
> Right now cluster state is written and read from the ~/.whirr/cluster-name/instances file and logic to write and update it is spread between the Service and DestroyInstanceCommand (that I know of).
> Since for WHIRR-214 the file must be updated (in another class) and for WHIRR-238 an altogether different method of storing cluster state will be required I think it might be time to move the read/write state logic to its own file (or factory in the future).
> I'll attach a very preliminary patch just to get some feedback.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira