So, I haven't been involved directly in a lot of the discussion, but my 2c is:
+1 to juju ensure-ha Users don't give a f*ck about how Juju achieves HA, they just want to know their data will survive a node outage. What Juju does under the covers to make that happen, what jobs are run on what nodes etc - that's for Juju to care about. +1 to high level, namespaced services (juju:api, juju:db etc) This is a step above ensure-ha for more advanced users, but one which still presents the solution space in terms any IS person involved in managing things like scalable web services understands. ie there's the concept of services which process requests and those which store data, and those which <insert role here>. If the volume of incoming requests are such that the load on the api servers is high while the database is still coping ok, "juju add-unit juju:api -n 3" can be used to solve that efficiently, and vice versa. So it's all about mapping what Juju does to terms and concepts already understood, and getting the level of abstraction correct so the solution is usable by the target audience. Anything that involves exposing things like jobs etc is not the right way of looking at it IMO. -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
