Thanks James thats a great summary.
Some of it I want to boil down, some I have some further questions…
Juju is not some contrived cfgmgmt tool. This gets Juju out of the space of being compared to the chef/puppet/ansible
Okay first up. I’ve used puppet on and off over the years so I kinda know what you’re getting at here. But the first question a Chef/Puppet user will be, how is it not a configmgt tool?
I know we’ve laboured this point over the years, so I’m dumbing the conversation down a little, but if someone is stood in front of you and says, “how is it not a cfgmgmt tool?”, whats the two sentence answer?
Point 2 I fully get. 100% true.
Point 3 is great, if we could boil that down into a nugget to take away I think it would be really useful.
Point 4 CDK, Openstack, Big data to a point I get, but it brings me back onto some of the original post.
How do you get developers and open source communities to want to commit charms, be it K8S style or traditional? From a non SysOps point of view, how do you sell it as a worthwhile cause?
I’m a developer who commits charms back, so the question is reasonably rhetorical, but from an evangelism point of view, I’m trying to figure out how to get more open source communities involved in maintaining the charms.
Regarding your last paragraph, I tried to dig out a screencap of Mark’s talk the other day where I could swear he’d moved the Juju stack from Orchestration to Modelling and stuck other stuff in Orchestration… but the stream wasn’t online when he showed it… so I can’t 
But thats another point. Is it modelling, is it orchestration, is it both, is it neither? Does it do baremetal, does it do K8S? Does it do too much?
Cheers
Tom