> >> I want to understand if there is a possibility of exposing these as
> >> different modules that we can mix and match, using options.
It’s not only possible, but it’s easier than you might think. If an
option is set (cluster.nsr IIRC) then we replace cluster/afr with
cluster/nsr-client and
On 10/29/2015 02:06 AM, Pranith Kumar Karampuri wrote:
hi,
I want to understand how are you guys planning to integrate
NSR volumes to the existing CLIs. Here are some thoughts I had, wanted
to know your thoughts:
At the heart of both the replication/ec schemes we have
1)
On Thu, Oct 29, 2015 at 05:38:28PM +0530, Bipin Kunal wrote:
> Hello Niels/Humble,
>
> I would like to help you here and by this I can even start collaborating in
> upstream.
>
> I will try to send first pull request very soon, late by next week.
Great, thanks! Let us know if you have any
On 10/27/2015 11:12 PM, Sankarshan Mukhopadhyay wrote:
On Mon, Oct 26, 2015 at 7:04 PM, Shyam wrote:
Older idea on this was, to consume the logs and filter based on the message
IDs for those situations that can be remedied. The logs are hence the point
where the event for
Hello Niels/Humble,
I would like to help you here and by this I can even start collaborating in
upstream.
I will try to send first pull request very soon, late by next week.
Thanks,
Bipin Kunal
On Wed, Oct 28, 2015 at 5:04 PM, Niels de Vos wrote:
> On Wed, Oct 28, 2015 at
On 10/29/2015 01:42 AM, Avra Sengupta wrote:
My 2 cents on this:
The decision we take on this should have certain rationale, and I see
two key things affecting that decision.
1. How much of the code we are planning to write now, is going to make
it to the final product. If we are sure that a
On Mon, Oct 26, 2015 at 08:42:34AM -0400, Kaleb S. KEITHLEY wrote:
> On 10/26/2015 05:14 AM, Niels de Vos wrote:
> > On Wed, Oct 21, 2015 at 05:22:49AM -0400, Nagaprasad Sathyanarayana wrote:
> >> I came across the following BZs which are still open in mainline. But
> >> they are fixed and made
On 10/29/2015 07:29 PM, Jeff Darcy wrote:
On October 29, 2015 at 9:12:46 AM, Shyam (srang...@redhat.com) wrote:
Will code that NSR puts up in master be ready to ship when 3.8 is
branched?
Do we know when 3.8 will be branched?
This is an example not absolute, what I mean is when the next
On October 29, 2015 at 9:12:46 AM, Shyam (srang...@redhat.com) wrote:
> Will code that NSR puts up in master be ready to ship when 3.8 is
> branched?
Do we know when 3.8 will be branched?
> I ask the above, as I think we need a *process*, and not an open ended
> "put it where you want option",
hi,
I want to understand how are you guys planning to integrate
NSR volumes to the existing CLIs. Here are some thoughts I had, wanted
to know your thoughts:
At the heart of both the replication/ec schemes we have
1) synchronization mechanisms
a) afr,ec does it using locks
On Thu, Oct 29, 2015 at 11:36 AM, Pranith Kumar Karampuri
wrote:
> hi,
> I want to understand how are you guys planning to integrate NSR
> volumes to the existing CLIs. Here are some thoughts I had, wanted to know
> your thoughts:
> At the heart of both the
On 10/29/2015 12:18 PM, Venky Shankar wrote:
On Thu, Oct 29, 2015 at 11:36 AM, Pranith Kumar Karampuri
wrote:
hi,
I want to understand how are you guys planning to integrate NSR
volumes to the existing CLIs. Here are some thoughts I had, wanted to know
your
On October 29, 2015 at 8:42:50 PM, Shyam (srang...@redhat.com) wrote:
> I assume this is about infra changes (as the first 2 points are for
> some reason squashed in my reader). I think what you state is infra
> (or other non-experimental) code impact due to changes by
> experimental/inprogress
13 matches
Mail list logo