Interesting. Have you thought about packaging everything together? I mean,
incorporating the whole plugin in ACS. Then, ACS manage the ES via one new
system VM type (OSVM – Object store system virtual machine), and another
system VM could be used to run the standalone service, which could execute
Hi, Rafael. Second option. ES is configured beforehand, then, when plugin
is deployed, only endpoint is specified in ES, but actual VMs don't
interact with ES directly, they interact with API server which is deployed
in docker container. So, basically three components: ES, CS plugin
(authorized
That is interesting Ivan. You answer create another question.
You say that the plugin uses an Elasticsearch instance and that a clustered
ES is supported as
well. Is the plugin going to manage (install this ES) or you (the operator)
will have to deploy and manage the ES and only configure/point
Hello, Daan, Rafael.
Ok, let's discover some points.
Rafael:
All the stuff is managed in Elasticsearch, clustered ES is supported as
well. As for now, value datatype is 'keyword' and doesn't fit well for
blobs. But, actually, there are no practical limitations except we don't
want press the CS
sounds nice Ivan, Do you have a whitepaper on it? I strugle to see a clear
usecase for this plugin. maybe you have a casus or two!?!
On Wed, Sep 19, 2018 at 9:02 AM Ivan Kudryavtsev
wrote:
> Hello, community.
>
> We glad to announce a new Open Source plug-in for Apache CloudStack which
> helps
Hello, community.
We glad to announce a new Open Source plug-in for Apache CloudStack which
helps to maintain generic key-value storages. There are three types are
supported right now:
- temporary KV with TTL (many per account);
- persistent KV bound to VM (one per VM);
- persistent KV bound to
