On 11/11/14 10:28, John McEleney wrote: > From the perspective of someone using the charms, these changes seem > to have come out of the blue, and the built-in Charm documentation > (readme, config etc.) doesn't provide an overview of how this new > multi-NIC HA is supposed to work. > > Maybe it's just bad Google-fu on my part that I can't find the > answers. Where should I go to find answers to these questions?
I think you've hit on one of the weaknesses of the charm ecosystem, which is that one needs to "know how to use them" if one wants to get beyond one-service-unit-per-machine. We can either encourage charmers to invest in better documentation (a good place to start) or we can encourage the charmers to bake more of this sort of operating intelligence into bundles (we have some preliminary examples of that in cloud foundry, where the bundle becomes "intelligent" and does this sort of thing for you) or we can identify some common patterns and socialise those across charmers so that one only has to stub one's toe on this sort of problem once. Bit early to know *exactly* which way it will pan out. I'm inclined to try to have more intelligence in the charms so that we can keep focused on creating a world where you don't want or need to know, it "just works" and it "just works brilliantly", where "brilliantly" means it's reliable, secure, adaptable to different hardware / environments, and so on. Mark -- Juju mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
