Re: [openstack-dev] [Neutron][LBaaS] L7 - Update L7Policy
Hi, It matters, as someone might need to debug the backend setup and the name, if exists, can add details. This obviously a vendor's choice if they wish to push this back to backend but the API should not remove this as a choice. -Sam. From: Eugene Nikanorov [mailto:enikano...@mirantis.com] Sent: Monday, February 17, 2014 12:24 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Neutron][LBaaS] L7 - Update L7Policy Folks, I wonder why using names on the backend could be needed? For the code there is no much difference between name and the id. Thanks, Eugene. On Mon, Feb 17, 2014 at 1:57 PM, Samuel Bercovici samu...@radware.commailto:samu...@radware.com wrote: Hi, My concern is that if from some reason the driver implementer would like to reflect the name also in the backend device, than an update should also be calling the driver. Using readable names also makes sense on the back-end device. -Sam. From: Oleg Bondarev [mailto:obonda...@mirantis.commailto:obonda...@mirantis.com] Sent: Monday, February 17, 2014 11:30 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Neutron][LBaaS] L7 - Update L7Policy Hi, On Mon, Feb 17, 2014 at 1:23 PM, Eugene Nikanorov enikano...@mirantis.commailto:enikano...@mirantis.com wrote: Hi Avishay, 1) I think name might be useful. Consider user forms a list of rules which route requests to a pool with static images or static pages, it may make sense to give those policy a name 'static-iamges', 'static-pages', rather then operate on ids. +1 2) I think updating the name is useful as well, but just on DB level, so there is no point in calling the driver and communicating with the backend. +1 Thanks, Eugene. On Mon, Feb 17, 2014 at 12:58 PM, Avishay Balderman avish...@radware.commailto:avish...@radware.com wrote: Hi L7Policy holds a list of L7rules plus 1 attribute: name . Questions: 1) Do we need to have this name attribute? 2) Do we want to allow update operation of the name attribute? Do we need to invoke the driver when such update occurred? Thanks Avishay ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.orgmailto:OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.orgmailto:OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.orgmailto:OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron][LBaaS] L7 - Update L7Policy
Hi! On Tue, Feb 18, 2014 at 12:18 AM, Samuel Bercovici samu...@radware.comwrote: Hi, It matters, as someone might need to “debug” the backend setup and the name, if exists, can add details. This obviously a vendor’s choice if they wish to push this back to backend but the API should not remove this as a choice. +1 -Sam. -- Stephen Balukoff Blue Box Group, LLC (800)613-4305 x807 ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron][LBaaS] L7 - Update L7Policy
Hi folks, I see little value in being able to debug such things because it is for developers only. However given that such choice doesn't affect workflow and public API, we can add corresponding calls to the driver API. Thanks, Eugene. On Wed, Feb 19, 2014 at 12:20 AM, Stephen Balukoff sbaluk...@bluebox.netwrote: Hi! On Tue, Feb 18, 2014 at 12:18 AM, Samuel Bercovici samu...@radware.comwrote: Hi, It matters, as someone might need to debug the backend setup and the name, if exists, can add details. This obviously a vendor's choice if they wish to push this back to backend but the API should not remove this as a choice. +1 -Sam. -- Stephen Balukoff Blue Box Group, LLC (800)613-4305 x807 ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron][LBaaS] L7 - Update L7Policy
Hi Avishay, 1) I think name might be useful. Consider user forms a list of rules which route requests to a pool with static images or static pages, it may make sense to give those policy a name 'static-iamges', 'static-pages', rather then operate on ids. 2) I think updating the name is useful as well, but just on DB level, so there is no point in calling the driver and communicating with the backend. Thanks, Eugene. On Mon, Feb 17, 2014 at 12:58 PM, Avishay Balderman avish...@radware.comwrote: Hi L7Policy holds a list of L7rules plus 1 attribute: name . Questions: 1) Do we need to have this name attribute? 2) Do we want to allow update operation of the name attribute? Do we need to invoke the driver when such update occurred? Thanks Avishay ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron][LBaaS] L7 - Update L7Policy
Hi, On Mon, Feb 17, 2014 at 1:23 PM, Eugene Nikanorov enikano...@mirantis.comwrote: Hi Avishay, 1) I think name might be useful. Consider user forms a list of rules which route requests to a pool with static images or static pages, it may make sense to give those policy a name 'static-iamges', 'static-pages', rather then operate on ids. +1 2) I think updating the name is useful as well, but just on DB level, so there is no point in calling the driver and communicating with the backend. +1 Thanks, Eugene. On Mon, Feb 17, 2014 at 12:58 PM, Avishay Balderman avish...@radware.comwrote: Hi L7Policy holds a list of L7rules plus 1 attribute: name . Questions: 1) Do we need to have this name attribute? 2) Do we want to allow update operation of the name attribute? Do we need to invoke the driver when such update occurred? Thanks Avishay ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron][LBaaS] L7 - Update L7Policy
Hi, My concern is that if from some reason the driver implementer would like to reflect the name also in the backend device, than an update should also be calling the driver. Using readable names also makes sense on the back-end device. -Sam. From: Oleg Bondarev [mailto:obonda...@mirantis.com] Sent: Monday, February 17, 2014 11:30 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Neutron][LBaaS] L7 - Update L7Policy Hi, On Mon, Feb 17, 2014 at 1:23 PM, Eugene Nikanorov enikano...@mirantis.commailto:enikano...@mirantis.com wrote: Hi Avishay, 1) I think name might be useful. Consider user forms a list of rules which route requests to a pool with static images or static pages, it may make sense to give those policy a name 'static-iamges', 'static-pages', rather then operate on ids. +1 2) I think updating the name is useful as well, but just on DB level, so there is no point in calling the driver and communicating with the backend. +1 Thanks, Eugene. On Mon, Feb 17, 2014 at 12:58 PM, Avishay Balderman avish...@radware.commailto:avish...@radware.com wrote: Hi L7Policy holds a list of L7rules plus 1 attribute: name . Questions: 1) Do we need to have this name attribute? 2) Do we want to allow update operation of the name attribute? Do we need to invoke the driver when such update occurred? Thanks Avishay ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.orgmailto:OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.orgmailto:OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron][LBaaS] L7 - Update L7Policy
I agree with #1 I am not sure I understand #2... Let's assume that the user created a policy named static-images. The policy was associated with a vip and it contains rules. When we have created the VipL7PolicyAssoc the driver used the L7Policy name attribute in its backend. Now we modify this name to be static-images1 - why not to tell the driver about it? Thanks Avishay From: Oleg Bondarev [mailto:obonda...@mirantis.com] Sent: Monday, February 17, 2014 11:30 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Neutron][LBaaS] L7 - Update L7Policy Hi, On Mon, Feb 17, 2014 at 1:23 PM, Eugene Nikanorov enikano...@mirantis.commailto:enikano...@mirantis.com wrote: Hi Avishay, 1) I think name might be useful. Consider user forms a list of rules which route requests to a pool with static images or static pages, it may make sense to give those policy a name 'static-iamges', 'static-pages', rather then operate on ids. +1 2) I think updating the name is useful as well, but just on DB level, so there is no point in calling the driver and communicating with the backend. +1 Thanks, Eugene. On Mon, Feb 17, 2014 at 12:58 PM, Avishay Balderman avish...@radware.commailto:avish...@radware.com wrote: Hi L7Policy holds a list of L7rules plus 1 attribute: name . Questions: 1) Do we need to have this name attribute? 2) Do we want to allow update operation of the name attribute? Do we need to invoke the driver when such update occurred? Thanks Avishay ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.orgmailto:OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.orgmailto:OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron][LBaaS] L7 - Update L7Policy
Folks, I wonder why using names on the backend could be needed? For the code there is no much difference between name and the id. Thanks, Eugene. On Mon, Feb 17, 2014 at 1:57 PM, Samuel Bercovici samu...@radware.comwrote: Hi, My concern is that if from some reason the driver implementer would like to reflect the name also in the backend device, than an update should also be calling the driver. Using readable names also makes sense on the back-end device. -Sam. *From:* Oleg Bondarev [mailto:obonda...@mirantis.com] *Sent:* Monday, February 17, 2014 11:30 AM *To:* OpenStack Development Mailing List (not for usage questions) *Subject:* Re: [openstack-dev] [Neutron][LBaaS] L7 - Update L7Policy Hi, On Mon, Feb 17, 2014 at 1:23 PM, Eugene Nikanorov enikano...@mirantis.com wrote: Hi Avishay, 1) I think name might be useful. Consider user forms a list of rules which route requests to a pool with static images or static pages, it may make sense to give those policy a name 'static-iamges', 'static-pages', rather then operate on ids. +1 2) I think updating the name is useful as well, but just on DB level, so there is no point in calling the driver and communicating with the backend. +1 Thanks, Eugene. On Mon, Feb 17, 2014 at 12:58 PM, Avishay Balderman avish...@radware.com wrote: Hi L7Policy holds a list of L7rules plus 1 attribute: name . Questions: 1) Do we need to have this name attribute? 2) Do we want to allow update operation of the name attribute? Do we need to invoke the driver when such update occurred? Thanks Avishay ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
