[
https://issues.apache.org/jira/browse/WHIRR-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13002661#comment-13002661
]
David Alves commented on WHIRR-246:
-----------------------------------
{quote}When you say local files, do you mean local to the machines in the
cluster?{quote}
I'm pretty sure Tom meant local files as they are now (stored locally in the
command-issuing machine).
I envision at least three alternatives, storing them locally, storing them in a
blobstore (e.g. S3) storing them in the nodes themselves (the ssh-based
blob-store).
I think we could start by introducing indirection and the local storage
facilities and introduce blobstore and/or node storage later on when required.
{quote}One idea that occurred to me was to implement this as a Service wrapper.
Could this work/is it desirable?{quote}
What do you mean by this Tom?
> 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
