Blueprint changed by Jorge O. Castro: Whiteboard changed: Juju will not live in isolation https://launchpad.net/juju-jitsu exists to enable these use cases Potential integration points: - Existing Puppet Deployments - - Existing puppet subordinate charm promulgated yesterday + - Existing puppet subordinate charm promulgated yesterday - Existing Puppet Manifests - External Node Classifier - Capistrano / Fabric - - jitsu capfile -> emits a capfile - - capistrano subordinate? + - jitsu capfile -> emits a capfile + - capistrano subordinate? - Chef - SaltStack - + Solutions - REST API (lp:jrapi) other ways to integrate puppetforge cookbooks on github how do you make a charm out of any of these? - - - Work Items: - [mark-mims] charm to deploy chef-server (maybe w sub like clint's puppet sub) - [mark-mims] charms that call chef solo recipes - "jujustrano" - [negronjl] go to town on clint's puppet sub ( puppetforge? ) ( add charm create option for puppet recipes ) - define ways that capistrano would need to call Capistrano - [negronjl] jrapi as juju-jitsu subcommand... 'jitsu api' - [hazmat] export/import environment into juju-jitsu - use-cases for integration - how to make charms out of puppetforge modules / github cookbooks - plugin for chef-search to interface with juju (possibly just chef sub) - testing against euca and cloudstack - jenkins plugins for juju (anything other than charm-runner?) - vagrant integration to support local development story on osx - [mike-mcclurg] cloudstack integration - [imbrandon] investigate enstratus integration - - related - best practices for juju at scale
-- Juju Integration https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-integration -- Ubuntu-server-bugs mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
