What's going on about Polly?

[moypray]

Hi,
I saw the polly project before, and do not come here for long time. I wonder if the project is going on ? I see the latest update is Aug 2016. Do you have any plan about storage scheduling? thanks.

[clintkitson]

Hello @moypray. Thanks for reaching out. The plan is to continue Polly as is until we bring the functionality directly to REX-Ray.

[moypray]

OK, got it, thanks for your reply.

[jxq8243]

Why moved the polly to the REX-Ray ? what's the purpose for this adjustment?

[clintkitson]

@jxq8243 Polly and REX-Ray both implement libStorage and fit the same operational characteristics. They both are services and optionally expose functionality to CLI tools. Polly includes a persistence layer for key-value storage which enables it to provide the "scheduling" mechanism. It does not include REX-Ray's interactive CLI which includes operations like attach/detach/mount/unmount. REX-Ray includes upstream interoperability interfaces to Docker, etc.

The goal is to get a single tool that focused on interoperability to other cloud native tools, which has both interactive capabilities but also an optional persistence layer. Hence the goal of rolling the same functionality into REX-Ray.

This could be done today by having REX-Ray make requests of Polly (they both speak libStorage API), but it would be ideal to have these things both in a single tool.