Juju: Configuration Management for Juju
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
Blueprint information
- Status:
- Complete
- Approver:
- Antonio Rosales
- Priority:
- Low
- Drafter:
- Ubuntu Server
- Direction:
- Approved
- Assignee:
- Marc Cluet
- Definition:
- Approved
- Series goal:
- Accepted for precise
- Implementation:
-
Implemented
- Milestone target:
-
ubuntu-12.04
- Started by
- Marc Cluet
- Completed by
- Clint Byrum
Whiteboard
Work Items:
[lynxman] write puppet external node classifier for juju status -> puppet: POSTPONED
[lynxman] write puppet facter integration out of juju status information: POSTPONED
[clint-fewbar] Start project for recovering useful information out of juju status ( https:/
[juju] after colocation investigate cli interface for local / arbitrary unit / relation info (relation-ids command landed): DONE
[clint-fewbar] write puppet subordinate charm: DONE
Session notes:
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
TALKING POINTS
* What can DSL integration provide to juju
- How it can complement the juju ecosystem
* Ways to export through a RESTful interface metadata from Juju
- Ensure freshfulness statefulness of data
* Ways to implement this so Juju can action on this without problem
- Charm integration
- Ways of informing back to juju about provides from DSL systems
* Finding ways around the SPOFs
- How to survive in case of miscommunication or recoverable failure
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
[clint-fewbar] Start project for recovering useful information out of juju status
[juju] after colocation investigate cli interface for local / arbitrary unit / relation info
Work Items
Dependency tree
* Blueprints in grey have been implemented.
