Open Stack

Hi Eugene, Iwamoto

> You are correct. Provider attribute will remain in the pool due to API
> compatibility reasons.
I agree with you.

I just wanted to make sure pools in a loadblancer can have
different providers or not. (I think it should be same.)

Thanks
Itsuto Ofa

On Mon, 2 Dec 2013 12:48:30 +0400
Eugene Nikanorov <enikanorov at mirantis.com> wrote:

> Hi Iwamoto,
> 
> You are correct. Provider attribute will remain in the pool due to API
> compatibility reasons.
> 
> Thanks,
> Eugene.
> 
> 
> On Mon, Dec 2, 2013 at 9:35 AM, IWAMOTO Toshihiro <iwamoto at valinux.co.jp>wrote:
> 
> > At Fri, 29 Nov 2013 07:25:54 +0900,
> > Itsuro ODA wrote:
> > >
> > > Hi Eugene,
> > >
> > > Thank you for the response.
> > >
> > > I have a comment.
> > > I think 'provider' attribute should be added to loadbalance resource
> > > and used rather than pool's 'provider' since I think using multiple
> > > driver within a loadbalancer does not make sense.
> >
> > There can be a 'provider' attribute in a loadbalancer resource, but,
> > to maintain API, the 'provider' attribute in pools should remain the
> > same.
> > Is there any other attribute planned for the loadbalancer resource?
> >
> > > What do you think ?
> > >
> > > I'm looking forward to your code up !
> > >
> > > Thanks.
> > > Itsuro Oda
> > >
> > > On Thu, 28 Nov 2013 16:58:40 +0400
> > > Eugene Nikanorov <enikanorov at mirantis.com> wrote:
> > >
> > > > Hi Itsuro,
> > > >
> > > > I've updated the wiki with some examples of cli workflow that
> > illustrate
> > > > proposed API.
> > > > Please see the updated page:
> > > >
> > https://wiki.openstack.org/wiki/Neutron/LBaaS/LoadbalancerInstance#API_change
> > > >
> > > > Thanks,
> > > > Eugene.
> >
> > --
> > IWAMOTO Toshihiro
> >
> > _______________________________________________
> > OpenStack-dev mailing list
> > OpenStack-dev at lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >

-- 
Itsuro ODA <oda at valinux.co.jp>