Some of my recent work with charming Cloud Foundry has led us towards a slightly different understanding of bundles. In the case of something like cloud foundry the topology will change between releases of their code, in version 'b' they might add a new service that 'a' didn't have and in 'c' they might replace two existing components with a new one that subsumes them. In cases like this being able to preserve identity in the runtime is a very interesting feature of 1st class bundle support. Right now a bundle IsA topology but in our depiction it HasA topology. While I have no proof that service spanning identity that survives mutation is general enough to inform these requirements it really is something we want to deal with.
I also understand that in some world views a bundle would represent a supportable collection of services and this might imply the topology is fixed but any complex system that evolves is likely to have some topology mutation. While we can manage this without first class support it would be difficult to expect the GUI to the the 'right' thing for our project unless bundles include this idea. Thanks, -Ben On Thu, Jun 19, 2014 at 6:28 AM, roger peppe <[email protected]> wrote: > We (mostly myself and Francesco Banconi, with some useful > input from Brad Crittenden) have put together a proposal for moving > towards making bundles a first-class citizen in Juju. > > Please let us know what you think. > > > https://docs.google.com/a/canonical.com/document/d/1SF8hTBi6oVbki8V__beNij6wnQU-5cm6PZsy5gf0j_Y/edit > > cheers, > rog. > > -- > Juju-dev mailing list > [email protected] > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju-dev >
-- Juju-dev mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
