Abhi
If your state objects are relatively simple (beans etc), you can set
them as config or sensors on an entity and this information will be
persisted automatically, restored when the entities are brought back
up. It works for complex types too but it can be a bit brittle if you
change fields so we tend not to do that.
Best
Alex
On 10/12/2015 09:07, Andrea Turli wrote:
Ops I think I missed [3]:
https://github.com/jclouds/jclouds-examples/tree/master/blobstore-scala-filesystem
On 10 December 2015 at 10:06, Andrea Turli <andrea.tu...@cloudsoftcorp.com>
wrote:
Hi Abni,
I think you could take a look at [1], which implements the jclouds'
BlobStore abstraction using your local filesystem.
Hopefully, [2] and [3] may be useful for getting the idea of that `api`
and see if it is useful for you.
Best,
Andrea
[1]:
https://github.com/jclouds/jclouds/tree/f832ad00a72ac8442e25686d14f55d0e310475c4/apis/filesystem
[2]:
https://github.com/jclouds/jclouds-examples/tree/master/blobstore-basics
On 10 December 2015 at 03:00, Abhishek Sharma <abhisharm...@gmail.com>
wrote:
Hey folks,
*Context:*
After having used brooklyn extensively and also reading the persistence
documentation, I see that based on brooklyn.properties or CLI parameters
brooklyn can either persist its state to localhost or to the cloud (using
jclouds).
*Question:*
I want to emulate the same behavior is my application (which is built on
brooklyn).
Implying that I want my app to either persist my custom state either on
localhost or on the cloud based on config. This would avoid me from having
to write a bunch of if....else against the configuration. I want my app's
custom state management to be exactly similar to brooklyn's. Can someone
point me to the code or guide me to find out how brooklyn does this ?
To re-phrase my question: What I want is almost like if jclouds supported
a
provider called "localhost" and did all the persistence locally.
Thanks in advance,
Abhi
