cf-charmers team mailing list archive

[prismakov@xxxxxxxxx]

Thank you Kapil, it is my fault. Got it.

-A.P.

On May 30, 2014, at 18:14, Kapil Thangavelu <kapil.thangavelu@xxxxxxxxxxxxx> wrote:

> your relation name is not related to the interface that is used, your charm (broker) is specifying the 'mysql' interface not the 'mysql-root' interface so that's what you'll get. 
> 
> juju cli and deployer will fail if there are multiple compatible relations possible (its ambigious) between charms.  you resolve the ambiguity by explicitly specifying it via "service_name:relation_name" syntax.
> 
> 
> On Fri, May 30, 2014 at 10:59 AM, Alex Prismakov <prismakov@xxxxxxxxx> wrote:
> Hi guys,
> 
> could you please help me understand is it a bug of juju-deployer or not?
> 
> in metadata.yaml of cf-mysql-broker charm:
> requires:
>   db-admin:
>     interface: mysql
>     gets: [host, database, user, password, slave]
> in bundles.yaml relations defined as:
> - [mysql, [cc, broker]] 
> 
> So I expect for cf-mysql-broker 'db-admin' relation but what actually I get is 'db'...
> CC requires 'db' connection and it gets it. But why 'db' instaed of 'db-admin' for the broker?!
> 
> $juju status mysql
> environment: local
> .....
> services:
>   mysql:
>     charm: local:trusty/mysql-311
>     exposed: false
>     relations:
>       cluster:
>       - mysql
>       db:
>       - broker
>       - cc
>     units:
>       mysql/0:
>         agent-state: started
>         agent-version: 1.19.2.1
>         machine: "5"
>         public-address: 192.168.122.130
> 
> Thank you in advance,
> 
> -Alex Prismakov | Altoros
>