On Mon, Dec 8, 2014 at 6:35 PM, Eric Snow <eric.s...@canonical.com> wrote:
> The reaction I get most often from folks that aren't familiar with > juju and skim through the juju site is that it looks like a competitor > to the various configuration management tools out there like Puppet or > Salt. However, my experience is that while they have some overlap, > they sit at different layers. > > Agreed. I think the messaging on the sites messaging could use some work, I just went through the front page of juju.ubuntu.com and jujucharms.com and i couldn't tell you from those why its not a config management tool. The word orchestration doesn't in appear in the front page of either site!.... The new site is better but has gems like Why use juju -> 'Reduce workloads from days to minutes' what does that even mean, its a runtime workload accelerator? > Have I grown out of touch? Conceivably those projects have or are > working on juju-like functionality that I'm not aware of. They aren't, there's a whole new set of tools though that are working on orchestration features, though it may be a rather ambiguous term yet, they still advertise themselves as such. the growth of containers/docker has reinforced the value of orchesrtation tools since image delivery obviates most config management, ie. having a bunch of containers that don't talk to each across nodes other is obviously a problem in want of a a solution (discovery, connectivity, topology composition) aka orchestration. If not (or > even if so), what's the best way to educate people on what juju is and > how it will help them when they're already steeped in the lower-layer > config. management world? > Explain orchestration as a higher level construct which focuses on services management via iaas provisioning, service discovery, service automation (db creation, etc) in a reusable way. Coupled with an ecosystem of service definitions that offers user composed multi-node solutions. Try showing them a deployer config/bundle and ask them to compare to the comparable lower level tool config. > > Related to that, how can we help those same folks wrap all their > existing recipes, etc. in charms? It's got to be easy enough that > they can justify the effort. > michael's reply goes through the most cm tool used in charms, ansible. we've got production and example charms written with several different tools. nutshell using cm tools in solo single host with facts/vars fed in via config, and relations, and executed in place of hooks. cheers, Kapil
-- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
