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
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.
> /bugs.launchpad .net/bugs/ 829420 /bugs.launchpad .net/ensemble/ +bug/829420/ +subscriptions
> --
> You received this bug notification because you are a member of Ensemble
> Team, which is the registrant for Ensemble.
> https:/
>
> 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:/