Re: [openstack-dev] [octavia] enabling new topologies

2016-06-13 Thread Stephen Balukoff
Hey Sergey, In-line comments below: On Sun, Jun 5, 2016 at 8:07 AM, Sergey Guenender wrote: > > Hi Stephen, please find my reply next to your points below. > > Thank you, > -Sergey. > > > On 01/06/2016 20:23, Stephen Balukoff wrote: > > Hey Sergey-- > > > > Apologies for the

Re: [openstack-dev] [octavia] enabling new topologies

2016-06-05 Thread Sergey Guenender
> Hi Sergey, Welcome to working on Octavia! Thanks, glad to be joining! :^) Please read a further explanation of my proposal down below. > I'm not sure I fully understand your proposals, but I can give my > thoughts/opinion on the challenge for Active/Active. > > In general I agree with

Re: [openstack-dev] [octavia] enabling new topologies

2016-06-05 Thread Sergey Guenender
Hi Stephen, please find my reply next to your points below. Thank you, -Sergey. On 01/06/2016 20:23, Stephen Balukoff wrote: > Hey Sergey-- > > Apologies for the delay in my response. I'm still wrapping my head > around your option 2 suggestion and the implications it might have for > the

[openstack-dev] [octavia] enabling new topologies

2016-06-02 Thread Sergey Guenender
Stephen, Michael, thank you for having a look. I'll respond to every issue you mentioned when I get to work on Sunday. Until then, in case you don't mind inspecting a small diff, just to clarify my point, please have a look at a rather straightforward change, which 1. exemplifies pretty much

Re: [openstack-dev] [octavia] enabling new topologies

2016-06-02 Thread Michael Johnson
Hi Sergey, Welcome to working on Octavia! I'm not sure I fully understand your proposals, but I can give my thoughts/opinion on the challenge for Active/Active. In general I agree with Stephen. The intention of using TaskFlow is to facilitate code reuse across similar but different code flows.

Re: [openstack-dev] [octavia] enabling new topologies

2016-06-01 Thread Stephen Balukoff
Hey Sergey-- Apologies for the delay in my response. I'm still wrapping my head around your option 2 suggestion and the implications it might have for the code base moving forward. I think, though, that I'm against your option 2 proposal and in favor of option 1 (which, yes, is more work

[openstack-dev] [octavia] enabling new topologies

2016-05-29 Thread Sergey Guenender
I'm working with the IBM team implementing the Active-Active N+1 topology [1]. I've been commissioned with the task to help integrate the code supporting the new topology while a) making as few code changes and b) reusing as much code as possible. To make sure the changes to existing code are