Does juju support 'named' interfaces?
Sidnei da Silva
sidnei.da.silva at canonical.com
Tue Jun 26 12:50:36 UTC 2012
On Tue, Jun 26, 2012 at 2:10 AM, Gustavo Niemeyer
<gustavo.niemeyer at canonical.com> wrote:
> On Mon, Jun 25, 2012 at 6:05 PM, Sidnei da Silva
> <sidnei.da.silva at canonical.com> wrote:
>> I can see someone working around this by forking the pgsql charm as
>> 'pgsql-shard[0-N]' and each of those charms only providing the
>> specific interface, and having the app require 'pgsql-shard[0-N]'
>> instead of a generic 'pgsql' charm, but clearly this would cause an
>> unnecessary interface explosion.
> Yeah, this sounds bad.
> Have you thought about having the shard name as a configuration
> property instead, so you have a single interface that provides the
> shard name? That should be straightforward.
Sounds simple enough that it could work. The only issue I see is that
there's no way to know externally which names are required for the app
to properly function. Maybe something like this could be formalized,
such that a charm could specify 'requires: pgsql [shard0, shard1, ..,
shardN]', such that the requirements were more explicit.
Make the most of Ubuntu with Ubuntu One
More information about the Juju