← Back to team overview

cf-charmers team mailing list archive

Fwd: [vcap-dev] More on Juju for CF and bosh positionning ?

 

FYI.

It wold be great if some of the Juju experts can provide some feedback.
https://groups.google.com/a/cloudfoundry.org/forum/#!topic/vcap-dev/VShgtXuL6to

We can also contribute. I think this should be planned.

Begin forwarded message:

> From: Guillaume Berche <bercheg@xxxxxxxxx>
> Subject: [vcap-dev] More on Juju for CF and bosh positionning ?
> Date: May 12, 2014 at 2:20:51 PM GMT-3
> To: <vcap-dev@xxxxxxxxxxxxxxxx>
> Reply-To: <vcap-dev@xxxxxxxxxxxxxxxx>
> 
> Hello,
> 
> I wonder if there is some news/feedback on the effort of producing Juju charms for CF that was mentionned on the march CAB [1]. I see there are some charms being actively worked on [0]
> 
> I wonder whether this collaboration brought some ideas on the use-cases where each tools respectively make more sense, or better, ideas on how to combine best of both tools.
> 
> It seems some concepts in Juju would be quite useful to bosh such as:
> - charms interfaces and relations [2] and [3] as a great flexible way to connect jobs together (avoiding needs to generate manifests through spiff, or use DNS implicit entries associated to jobs)
> - making jobs/bundle easier to reuse through metadata, builtin tests in manifests [4]...
> 
> Likewise, some concepts in Bosh seem beneficial to Juju:
> - stronger persistent data handling through disk attach/detach leveraging IaaS support rather than only leveraging backup jobs [5]
> - canaries deployments
> - health manager
> - wider supported CPIs
> - wider OS/stemcell support
> 
> I understand both tools are adressing the same needs with similar solutions. Is there diverging requirements ? Is there an opportunity for collaboration among the two tools?
> 
> Leveraging the charms Store for CF services could be a great opportunity to grow the CF service ecosystem. One possiblity would be to have service gateways charms that leverage existing charms to dynamically provision nodes. Such approach would however probably benefits from the points above (e.g. concerning persistent data handling).
> 
> Thanks in advance,
> 
> Guillaume.
> 
> [0] http://manage.jujucharms.com/~cf-charmers/trusty/cf-uaa and http://manage.jujucharms.com/~lomov-as/trusty/cf-uaa
> [1] http://www.activestate.com/blog/2014/03/cloud-foundry-advisory-board-meeting-2014-march
> [2] https://juju.ubuntu.com/docs/authors-charm-interfaces.html 
> [3] https://juju.ubuntu.com/docs/authors-hook-environment.html
> [4] https://juju.ubuntu.com/docs/authors-testing.html
> [5] https://juju.ubuntu.com/docs/authors-charm-quality.html#data-handling
> 
> 
> To unsubscribe from this group and stop receiving emails from it, send an email to vcap-dev+unsubscribe@xxxxxxxxxxxxxxxx.