Re: [openstack-dev] [Neutron][policy] Group Based Policy - Renaming
Like the policy-group naming. The policy-target is better than policy-point, but still feel there's some little confusing, as the target is usually meaning what it's for, but not what it's on. Hence, the policy-endpoint might be more exact. On Fri, Aug 8, 2014 at 11:43 PM, Jay Pipes jaypi...@gmail.com wrote: On 08/07/2014 01:17 PM, Ronak Shah wrote: Hi, Following a very interesting and vocal thread on GBP for last couple of days and the GBP meeting today, GBP sub-team proposes following name changes to the resource. policy-point for endpoint policy-group for endpointgroup (epg) Please reply if you feel that it is not ok with reason and suggestion. Thanks Ronak and Sumit for sharing. I, too, wasn't able to attend the meeting (was in other meetings yesterday and today). I'm very happy with the change from endpoint-group - policy-group. policy-point is better than endpoint, for sure. The only other suggestion I might have would be to use policy-target instead of policy-point, since the former clearly delineates what the object is used for (a target for a policy). But... I won't raise a stink about this. Sorry for sparking long and tangential discussions on GBP topics earlier this week. And thanks to the folks who persevered and didn't take too much offense to my questioning. Best, -jay ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Best wishes! Baohua ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron][policy] Group Based Policy - Renaming
On 08/07/2014 01:17 PM, Ronak Shah wrote: Hi, Following a very interesting and vocal thread on GBP for last couple of days and the GBP meeting today, GBP sub-team proposes following name changes to the resource. policy-point for endpoint policy-group for endpointgroup (epg) Please reply if you feel that it is not ok with reason and suggestion. Thanks Ronak and Sumit for sharing. I, too, wasn't able to attend the meeting (was in other meetings yesterday and today). I'm very happy with the change from endpoint-group - policy-group. policy-point is better than endpoint, for sure. The only other suggestion I might have would be to use policy-target instead of policy-point, since the former clearly delineates what the object is used for (a target for a policy). But... I won't raise a stink about this. Sorry for sparking long and tangential discussions on GBP topics earlier this week. And thanks to the folks who persevered and didn't take too much offense to my questioning. Best, -jay ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron][policy] Group Based Policy - Renaming
Thanks Jay for your constructive feedback on this. I personally think that 'policy-target' is a good option. I am not sure what the rest of the team thinks, perhaps they can chime in. On Fri, Aug 8, 2014 at 8:43 AM, Jay Pipes jaypi...@gmail.com wrote: On 08/07/2014 01:17 PM, Ronak Shah wrote: Hi, Following a very interesting and vocal thread on GBP for last couple of days and the GBP meeting today, GBP sub-team proposes following name changes to the resource. policy-point for endpoint policy-group for endpointgroup (epg) Please reply if you feel that it is not ok with reason and suggestion. Thanks Ronak and Sumit for sharing. I, too, wasn't able to attend the meeting (was in other meetings yesterday and today). I'm very happy with the change from endpoint-group - policy-group. policy-point is better than endpoint, for sure. The only other suggestion I might have would be to use policy-target instead of policy-point, since the former clearly delineates what the object is used for (a target for a policy). But... I won't raise a stink about this. Sorry for sparking long and tangential discussions on GBP topics earlier this week. And thanks to the folks who persevered and didn't take too much offense to my questioning. Best, -jay ___ 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][policy] Group Based Policy - Renaming
+1 Sumit Naiksatam sumitnaiksa...@gmail.com wrote on 08/08/2014 02:44:55 PM: From: Sumit Naiksatam sumitnaiksa...@gmail.com To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Date: 08/08/2014 02:45 PM Subject: Re: [openstack-dev] [Neutron][policy] Group Based Policy - Renaming Thanks Jay for your constructive feedback on this. I personally think that 'policy-target' is a good option. I am not sure what the rest of the team thinks, perhaps they can chime in.___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron][policy] Group Based Policy - Renaming
policy target sounds good. +1 On Fri, Aug 8, 2014 at 12:44 PM, Sumit Naiksatam sumitnaiksa...@gmail.com wrote: Thanks Jay for your constructive feedback on this. I personally think that 'policy-target' is a good option. I am not sure what the rest of the team thinks, perhaps they can chime in. On Fri, Aug 8, 2014 at 8:43 AM, Jay Pipes jaypi...@gmail.com wrote: On 08/07/2014 01:17 PM, Ronak Shah wrote: Hi, Following a very interesting and vocal thread on GBP for last couple of days and the GBP meeting today, GBP sub-team proposes following name changes to the resource. policy-point for endpoint policy-group for endpointgroup (epg) Please reply if you feel that it is not ok with reason and suggestion. Thanks Ronak and Sumit for sharing. I, too, wasn't able to attend the meeting (was in other meetings yesterday and today). I'm very happy with the change from endpoint-group - policy-group. policy-point is better than endpoint, for sure. The only other suggestion I might have would be to use policy-target instead of policy-point, since the former clearly delineates what the object is used for (a target for a policy). But... I won't raise a stink about this. Sorry for sparking long and tangential discussions on GBP topics earlier this week. And thanks to the folks who persevered and didn't take too much offense to my questioning. Best, -jay ___ 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][policy] Group Based Policy - Renaming
That's ok for me as well! +1 On Aug 8, 2014 10:04 PM, Prasad Vellanki prasad.vella...@oneconvergence.com wrote: It sounds good +1 On Fri, Aug 8, 2014 at 12:44 PM, Sumit Naiksatam sumitnaiksa...@gmail.com wrote: Thanks Jay for your constructive feedback on this. I personally think that 'policy-target' is a good option. I am not sure what the rest of the team thinks, perhaps they can chime in. On Fri, Aug 8, 2014 at 8:43 AM, Jay Pipes jaypi...@gmail.com wrote: On 08/07/2014 01:17 PM, Ronak Shah wrote: Hi, Following a very interesting and vocal thread on GBP for last couple of days and the GBP meeting today, GBP sub-team proposes following name changes to the resource. policy-point for endpoint policy-group for endpointgroup (epg) Please reply if you feel that it is not ok with reason and suggestion. Thanks Ronak and Sumit for sharing. I, too, wasn't able to attend the meeting (was in other meetings yesterday and today). I'm very happy with the change from endpoint-group - policy-group. policy-point is better than endpoint, for sure. The only other suggestion I might have would be to use policy-target instead of policy-point, since the former clearly delineates what the object is used for (a target for a policy). But... I won't raise a stink about this. Sorry for sparking long and tangential discussions on GBP topics earlier this week. And thanks to the folks who persevered and didn't take too much offense to my questioning. Best, -jay ___ 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
Re: [openstack-dev] [Neutron][policy] Group Based Policy - Renaming
+1 for policy-target -Original Message- From: Sumit Naiksatam [mailto:sumitnaiksa...@gmail.com] Sent: Friday, August 08, 2014 12:45 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Neutron][policy] Group Based Policy - Renaming Thanks Jay for your constructive feedback on this. I personally think that 'policy-target' is a good option. I am not sure what the rest of the team thinks, perhaps they can chime in. On Fri, Aug 8, 2014 at 8:43 AM, Jay Pipes jaypi...@gmail.com wrote: On 08/07/2014 01:17 PM, Ronak Shah wrote: Hi, Following a very interesting and vocal thread on GBP for last couple of days and the GBP meeting today, GBP sub-team proposes following name changes to the resource. policy-point for endpoint policy-group for endpointgroup (epg) Please reply if you feel that it is not ok with reason and suggestion. Thanks Ronak and Sumit for sharing. I, too, wasn't able to attend the meeting (was in other meetings yesterday and today). I'm very happy with the change from endpoint-group - policy-group. policy-point is better than endpoint, for sure. The only other suggestion I might have would be to use policy-target instead of policy-point, since the former clearly delineates what the object is used for (a target for a policy). But... I won't raise a stink about this. Sorry for sparking long and tangential discussions on GBP topics earlier this week. And thanks to the folks who persevered and didn't take too much offense to my questioning. Best, -jay ___ 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][policy] Group Based Policy - Renaming
Can you include the definition/description of what each is here as well? I think there was a description in the 100+ thread of doom, but I don't want to go back there :) On Thu, Aug 7, 2014 at 3:17 PM, Ronak Shah ronak.malav.s...@gmail.com wrote: Hi, Following a very interesting and vocal thread on GBP for last couple of days and the GBP meeting today, GBP sub-team proposes following name changes to the resource. policy-point for endpoint policy-group for endpointgroup (epg) Please reply if you feel that it is not ok with reason and suggestion. I hope that it wont be another 150 messages thread :) Ronak ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Andrew Mann DivvyCloud Inc. www.divvycloud.com ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron][policy] Group Based Policy - Renaming
I am sorry that I could not attend the GBP meeting. Is there any reason why the IEFT standard is not considered? http://tools.ietf.org/html/rfc3198 I would like to understand the argument why we are creating new names instead of using the standard ones. Edgar From: Ronak Shah ronak.malav.s...@gmail.commailto:ronak.malav.s...@gmail.com Reply-To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org Date: Thursday, August 7, 2014 at 1:17 PM To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org Subject: [openstack-dev] [Neutron][policy] Group Based Policy - Renaming Hi, Following a very interesting and vocal thread on GBP for last couple of days and the GBP meeting today, GBP sub-team proposes following name changes to the resource. policy-point for endpoint policy-group for endpointgroup (epg) Please reply if you feel that it is not ok with reason and suggestion. I hope that it wont be another 150 messages thread :) Ronak ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron][policy] Group Based Policy - Renaming
Edgar- I can't speak for anyone else, but in my mind at least (and having been involved in the work that led up to 3198), the members of the groups being discussed here are not PEPs. As 3198 states, being a PEP implies running COPS and I don't see that as necessary for membership in GBP groups. Ryan Moats Edgar Magana edgar.mag...@workday.com wrote on 08/07/2014 04:02:43 PM: From: Edgar Magana edgar.mag...@workday.com To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Date: 08/07/2014 04:03 PM Subject: Re: [openstack-dev] [Neutron][policy] Group Based Policy - Renaming I am sorry that I could not attend the GBP meeting. Is there any reason why the IEFT standard is not considered? http://tools.ietf.org/html/rfc3198 I would like to understand the argument why we are creating new names instead of using the standard ones. Edgar From: Ronak Shah ronak.malav.s...@gmail.com Reply-To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Date: Thursday, August 7, 2014 at 1:17 PM To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Subject: [openstack-dev] [Neutron][policy] Group Based Policy - Renaming Hi, Following a very interesting and vocal thread on GBP for last couple of days and the GBP meeting today, GBP sub-team proposes following name changes to the resource. policy-point for endpoint policy-group for endpointgroup (epg) Please reply if you feel that it is not ok with reason and suggestion. I hope that it wont be another 150 messages thread :) Ronak___ 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][policy] Group Based Policy - Renaming
Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Date: 08/07/2014 04:03 PM Subject: Re: [openstack-dev] [Neutron][policy] Group Based Policy - Renaming I am sorry that I could not attend the GBP meeting. Is there any reason why the IEFT standard is not considered? http://tools.ietf.org/html/rfc3198 I would like to understand the argument why we are creating new names instead of using the standard ones. Edgar From: Ronak Shah ronak.malav.s...@gmail.com Reply-To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Date: Thursday, August 7, 2014 at 1:17 PM To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Subject: [openstack-dev] [Neutron][policy] Group Based Policy - Renaming Hi, Following a very interesting and vocal thread on GBP for last couple of days and the GBP meeting today, GBP sub-team proposes following name changes to the resource. policy-point for endpoint policy-group for endpointgroup (epg) Please reply if you feel that it is not ok with reason and suggestion. I hope that it wont be another 150 messages thread :) Ronak___ 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][policy] Group Based Policy - Renaming
Ryan, COPS implies a common protocol to communicate with PEPs, which implies the same communication mechanism basically. So, you are implying that endpoints in GBP will use different protocol to communicate with decisions entities? It that is the case.. Well it sounds very complex for a simple GBP initial project. Then, the discussion will be in a different level. Edgar From: Ryan Moats rmo...@us.ibm.commailto:rmo...@us.ibm.com Reply-To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org Date: Thursday, August 7, 2014 at 2:18 PM To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [Neutron][policy] Group Based Policy - Renaming Edgar- I can't speak for anyone else, but in my mind at least (and having been involved in the work that led up to 3198), the members of the groups being discussed here are not PEPs. As 3198 states, being a PEP implies running COPS and I don't see that as necessary for membership in GBP groups. Ryan Moats Edgar Magana edgar.mag...@workday.commailto:edgar.mag...@workday.com wrote on 08/07/2014 04:02:43 PM: From: Edgar Magana edgar.mag...@workday.commailto:edgar.mag...@workday.com To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org Date: 08/07/2014 04:03 PM Subject: Re: [openstack-dev] [Neutron][policy] Group Based Policy - Renaming I am sorry that I could not attend the GBP meeting. Is there any reason why the IEFT standard is not considered? http://tools.ietf.org/html/rfc3198 I would like to understand the argument why we are creating new names instead of using the standard ones. Edgar From: Ronak Shah ronak.malav.s...@gmail.commailto:ronak.malav.s...@gmail.com Reply-To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org Date: Thursday, August 7, 2014 at 1:17 PM To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org Subject: [openstack-dev] [Neutron][policy] Group Based Policy - Renaming Hi, Following a very interesting and vocal thread on GBP for last couple of days and the GBP meeting today, GBP sub-team proposes following name changes to the resource. policy-point for endpoint policy-group for endpointgroup (epg) Please reply if you feel that it is not ok with reason and suggestion. I hope that it wont be another 150 messages thread :) Ronak___ 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][policy] Group Based Policy - Renaming
are not PEPs. As 3198 states, being a PEP implies running COPS and I don't see that as necessary for membership in GBP groups. Ryan Moats Edgar Magana edgar.mag...@workday.com wrote on 08/07/2014 04:02:43 PM: From: Edgar Magana edgar.mag...@workday.com To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Date: 08/07/2014 04:03 PM Subject: Re: [openstack-dev] [Neutron][policy] Group Based Policy - Renaming I am sorry that I could not attend the GBP meeting. Is there any reason why the IEFT standard is not considered? http://tools.ietf.org/html/rfc3198 I would like to understand the argument why we are creating new names instead of using the standard ones. Edgar From: Ronak Shah ronak.malav.s...@gmail.com Reply-To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Date: Thursday, August 7, 2014 at 1:17 PM To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Subject: [openstack-dev] [Neutron][policy] Group Based Policy - Renaming Hi, Following a very interesting and vocal thread on GBP for last couple of days and the GBP meeting today, GBP sub-team proposes following name changes to the resource. policy-point for endpoint policy-group for endpointgroup (epg) Please reply if you feel that it is not ok with reason and suggestion. I hope that it wont be another 150 messages thread :) Ronak___ 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
Re: [openstack-dev] [Neutron][policy] Group Based Policy - Renaming
Edgar Magana edgar.mag...@workday.com wrote on 08/07/2014 04:37:39 PM: From: Edgar Magana edgar.mag...@workday.com To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Date: 08/07/2014 04:40 PM Subject: Re: [openstack-dev] [Neutron][policy] Group Based Policy - Renaming Ryan, COPS implies a common protocol to communicate with PEPs, which implies the same communication mechanism basically. So, you are implying that “endpoints” in GBP will use “different” protocol to communicate with “decisions” entities? Nope, I'm saying that the members of groups are not *required* to do enforcement. They *could* (based on the implementation), but calling them PEPs means they would *have* to. Ryan___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron][policy] Group Based Policy - Renaming
That I understand it! Thanks for the clarification. Edgar From: Ryan Moats rmo...@us.ibm.commailto:rmo...@us.ibm.com Reply-To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org Date: Thursday, August 7, 2014 at 2:45 PM To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [Neutron][policy] Group Based Policy - Renaming Edgar Magana edgar.mag...@workday.commailto:edgar.mag...@workday.com wrote on 08/07/2014 04:37:39 PM: From: Edgar Magana edgar.mag...@workday.commailto:edgar.mag...@workday.com To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org Date: 08/07/2014 04:40 PM Subject: Re: [openstack-dev] [Neutron][policy] Group Based Policy - Renaming Ryan, COPS implies a common protocol to communicate with PEPs, which implies the same communication mechanism basically. So, you are implying that endpoints in GBP will use different protocol to communicate with decisions entities? Nope, I'm saying that the members of groups are not *required* to do enforcement. They *could* (based on the implementation), but calling them PEPs means they would *have* to. Ryan ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
