Blueprint changed by Juan L. Negron: 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 Manifests - External Node Classifier - Capistrano / Fabric - 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? --- User Stories: - Andrew has some nice solid working Chef recipes. He would like to take advantage of the work already done in Chef, and use Juju as a service orchestration mechanism. + Andrew has some nice solid working Chef recipes. He would like to take advantage of the work already done in Chef, and use Juju as a service orchestration mechanism. Nathan has some existing Puppet deployments that he would like to leverage in Juju's service deployment. Assumptions: n/a Test Plans: Test Chef, Puppet, Capistrano, CloudStack, and Facter integration points and charms in CharmTester. Release Notes: When available provide information on how Chef, Puppet, Capistrano, CloudStack, and Facter may be used in a Juju framework. + + -- juju facter integration -- + facter is a standalone command tool that can be used via Juju by just installing the package ( sudo apt-get install facter ). + With the addition of facter-customfacts-plugin, new custom "facts" can be added/modified/deleted/used with juju to maintain status of the different aspects of the system in use. + An example of this integration can be found in lp:~negronjl/+junk/hpcc
-- Juju Integration https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-integration -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
