We have detected a need for DSL integration in Juju, this would mean that any of the current configuration management applications available.

Advantages
Faster implementation of juju on running platforms
Faster testing of juju on individual nodes
* Complements the amazing capabilities of juju with some node specific templating

For all this we need to talk about:
Ways to export through a RESTful interface metadata from Juju
Ways to implement this so Juju can action on this without problem
* Finding ways around the SPOFs

Juju roadmap right now has priority on colocation
Colocation can be used in colocation mode as well
Colocated service has access to filesystem services (whichever they are) and can establish master/slave relationships with the master unit
Juju charms can trigger an update of the facter information since it's always stateful, it can be a "trigger" on the update hook
So far the best action would be to query the CLI (juju status) and its a very effective way to recover information from juju in a quick (albeit slightly dirty) way

ACTIONS
[lynxman] write puppet external node classifier for juju status -> puppet: TODO
[clint-fewbar] Start project for recovering useful information out of juju status: TODO
[juju] after colocation investigate cli interface for local / arbitrary unit / relation info: TODO