Declare and consume external services

[Nick Barcet]

The notion of external servicesis needed to allow for consumption of service which are external to a given ensemble environment.

Example of this are:
  * linking to a SaaS provided service such as DB as a service, or logging as a service
  * Linking multiple OpenStack zones on deiffrent network to a common top level management set of services (keystone, api, etc...)

[Gustavo Niemeyer (niemeyer)]

Agreed, this is something we want to address with good first-class support.

Meanwhile, though, you don't have to wait for us. You can simply create a dummy service representing the external entity so that you can establish relations with it.

[Adam Gandelman (gandelman-a)]

The workaround is not viable for bare-metal installations. Dedicating an entire machine to the task of proxying Ensemble relations for a single external service isn't really an option.

[Clint Byrum (clint-fewbar)]

Excerpts from Adam Gandelman's message of Tue Aug 23 16:52:22 UTC 2011:
> The workaround is not viable for bare-metal installations. Dedicating
> an entire machine to the task of proxying Ensemble relations for a
> single external service isn't really an option.

You can deploy it with --placement=local and it will be placed on the
bootstrap host.

>
> --
> You received this bug notification because you are a member of Ensemble
> Team, which is the registrant for Ensemble.
> https://bugs.launchpad.net/bugs/829420
>
> Title:
> Declare and consume external services
>
> Status in Ensemble:
> Confirmed
>
> Bug description:
> The notion of external servicesis needed to allow for consumption of
> service which are external to a given ensemble environment.
>
> Example of this are:
> * linking to a SaaS provided service such as DB as a service, or logging as a service
> * Linking multiple OpenStack zones on deiffrent network to a common top level management set of services (keystone, api, etc...)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ensemble/+bug/829420/+subscriptions

[Clint Byrum (clint-fewbar)]

I think this can be handled by subordinate charms.. as there can be a subordinate which simply deploys the client side of the external service.

[Nick Barcet (nijaba)]

On 04/10/2012 12:56 AM, Clint Byrum wrote:
> I think this can be handled by subordinate charms.. as there can be a
> subordinate which simply deploys the client side of the external
> service.

+1 on trying to build a couple example, and if it succeeds, marking this
bug as fix released.