It does feel like a good fit for resources, with the one caveat that he wants to maintain a lock-step version of the resource across services. There is slightly more work with the current designs for resources, in that each charm will think about its version of the resource independently. But we will have the fingerprint information to allow for users to compare and be confident that both services are using the same resource.
John =:-> On Wed, Jan 20, 2016 at 8:53 PM, Mark Shuttleworth <[email protected]> wrote: > On 20/01/16 14:24, Merlijn Sebrechts wrote: > > So my question is: Is there a way to send large binary files between > > Charms? Or is this problem better solved by using a subordinate > > kafka-plugin Charm like the Hadoop Charms do? > > It sounds like you want the new "Resources" capability coming in Juju 2.0 > :) > > For shared large blobs (like a JVM or a big ball of libraries) the charm > can ask the state server to cache the blob and distribute it to all the > units. There are mechanisms for users to supply the blob if needed, too. > > Mark > > -- > Juju mailing list > [email protected] > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju >
-- Juju mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
