Topology and Orchestration Specification for Cloud Applications (TOSCA) and Juju

[Johannes Wettinger]

On Fri, Aug 24, 2012 at 9:48 PM, Gustavo Niemeyer
<gustavo.niemeyer at canonical.com> wrote:
> Portability is not such a big deal, and can be introduced in a simple
> way that fits the rest of the system. I'll reserve that conversation
> for when we start to produce cross-platform content, though.

Is there a roadmap for the further development of Juju? I'm especially
interested in when cross-platform content will be a topic for Juju in
practice.

> Saying it's an optional thing doesn't take complexity away. People
> have to read the optional things, have to learn about them, and manage
> them. There's a good reason why our documentation doesn't include a
> 700 lines XML schema.

Agreed, but those optional things could also be brought in by Juju
add-ons (btw: for TOSCA, the problem is that a lot of stuff is part of
the core spec). Then, the documentation of the Juju core remains
simple and only if someone wants to do some more sophisticated stuff,
Juju add-ons can be used. It's nice to keep Juju's core as simple as
possible, but it's also nice to provide the possibility to include
add-ons for more complex use cases. Is there any kind of extension
interface planned for Juju that add-ons could use?

Johannes