feature request: support virtual services

[Adam Stokes]

Not sure to what extent this has been discussed but creating a feature request for tracking. Would like to see virtual services implemented so that users can tie juju deployments in with their existing environment.

A use case that was brought to my attention would be to utilize an existing ceph cluster while allowing juju to deploy the rest of an OpenStack cloud.

[james beedy (jamesbeedy)]

This is a HUGE concern for us here at Dark Horse Comics seeing as we want to utilize/integrate juju with our existing storage/infrastructure but currently can't due to restrictions inherent to the juju environment framework itself.

[james beedy (jamesbeedy)]

Looking forward we are trying to utilize our ceph cluster as a backend for multiple separate openstack deployments, it would be nice to see the wheels start spinning in this ^ direction!

[Curtis Hovey (sinzui)]

This appears to me more of a charm issue than a juju issue. The I think a variant of the ceph charm is needed to ensure it doesn't install/destroy the existing service.

We can manually add any machine to an juju env to deploy services too (or a charm that uses the existing service). There are some awkward network issues when adding machines from other clouds/networks, but the juju-qa-team has a helper script to deal with the issue. I wrote an explanation of the solution:
    http://curtis.hovey.name/2014/06/10/building-trans-cloud-environments-with-juju/

If a charm is idempotent (it should, be not not all are) you can deploy a charm to a machine with the service already there. I do this with the jenkins charms to move machines between juju envs.

[Canonical Juju QA Bot (juju-qa-bot)]

This bug has not been updated in 5 years, so we're marking it Expired. If you believe this is incorrect, please update the status.