On 28 November 2017 at 20:22, Tilman Baumann
wrote:
> That would be quite nice actually. Backup and snapshot could be two
> different actions even.
> Snapshot is a little low-level as it is per-node. But it makes for fast
> recovery if a node hickups.
> Full backup
On 28.11.2017 00:38, Stuart Bishop wrote:
> On 23 November 2017 at 21:37, Tilman Baumann
> wrote:
>> I didn't want to talk about it before it's usable. I think I might be
>> working on something similar.
>>
>>
On 23 November 2017 at 21:37, Tilman Baumann
wrote:
> On 22.11.2017 23:26, Haw Loeung wrote:
>> Hi Tilman,
>>
>> On Wed, Nov 22, 2017 at 04:02:08PM +0100, Tilman Baumann wrote:
>>> However, that doesn't seem to work. Juju complains the relation doesn't
>>> exist.
>>>
My apologies. I had done a bunch of local updates and had not yet pushed
them back to github.
There should be quite a bit of changes, including a lot more of the values
and changing interfaces.yaml, etc.
John
=:->
On Fri, Nov 24, 2017 at 6:24 PM, Tilman Baumann <
tilman.baum...@canonical.com>
Hey John, apart from those fields missing. (BTW check usage section of
https://jujucharms.com/cassandra/36 for a list of fields)
interface.yaml calls this interface elasticsearch. I was able to use
this after I changed that.
;-)
Cheers
Tilman
On 23.11.2017 11:39, Tilman Baumann wrote:
>
On 22.11.2017 18:51, Cory Johns wrote:
> However, I see that you also want to retrieve relation data that the
> cassandra charm provides using the "cassandra" interface protocol. Here
> it becomes important to note that whether a relation is subordinate or
> not is independent of the interface
On 22.11.2017 23:26, Haw Loeung wrote:
> Hi Tilman,
>
> On Wed, Nov 22, 2017 at 04:02:08PM +0100, Tilman Baumann wrote:
>> However, that doesn't seem to work. Juju complains the relation doesn't
>> exist.
>> $ juju add-relation cassandra-backup:database cassandra:database
>> ERROR no relations
Cool. Thanks
The two fields I was interested in, username and password are mising
though. :D
But I'm thinking right now if I even want to go that route...
On 23.11.2017 04:01, John Meinel wrote:
> I did start working on a Cassandra interface for something I was working
> on. I don't know that it
On 22.11.2017 23:26, Haw Loeung wrote:
> Hi Tilman,
>
> On Wed, Nov 22, 2017 at 04:02:08PM +0100, Tilman Baumann wrote:
>> However, that doesn't seem to work. Juju complains the relation doesn't
>> exist.
>> $ juju add-relation cassandra-backup:database cassandra:database
>> ERROR no relations
I did start working on a Cassandra interface for something I was working
on. I don't know that it is complete but
https://github.com/jameinel/interface-cassandra
Was my attempt at it.
John
=:->
On Nov 23, 2017 02:26, "Haw Loeung" wrote:
> Hi Tilman,
>
> On Wed, Nov
Hi Tilman,
On Wed, Nov 22, 2017 at 04:02:08PM +0100, Tilman Baumann wrote:
> However, that doesn't seem to work. Juju complains the relation doesn't
> exist.
> $ juju add-relation cassandra-backup:database cassandra:database
> ERROR no relations found
>
> So, is there a interface that I can
Also:
"scope: global" vs "scope: container" in metadata.yaml are Juju-level
per-relation concepts.
Regardless of reactive or non-reactive charms, when you do
juju add-relation :
:
relation data will flow only between primary and subordinate units on a
given logical machine (machine or
You can use the "juju-info" interface type for subordinates, but I'm not
sure that this is the correct thing for your case.
You're trying to attach the non-subordinate "database" endpoint (of
interface protocol "juju-info") on your charm to the "database" endpoint
(of interface protocol
I'm writing a reactive subordinate charm for cassandra.
I can not find a interface for cassandra. But that's ok, since I don't
really need a full blown database connection client.
Easy I thought and just re-used the juju-info interface for fun and profit.
requires:
host-system:
interface:
14 matches
Mail list logo