You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@qpid.apache.org by Bruno Matos <br...@paradigmaxis.pt> on 2010/07/08 15:10:25 UTC
QoS - broker
Hello,
Is it possible to control the broker's QoS for authenticated users, like
bandwidth or dequeue rate?
Thank you.
Regards,
Bruno Matos
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org
Re: QoS - broker
Posted by Bruno Matos <br...@paradigmaxis.pt>.
On Thu, 2010-07-08 at 14:16 +0100, Gordon Sim wrote:
> On 07/08/2010 02:15 PM, Carl Trieloff wrote:
> > On 07/08/2010 09:10 AM, Bruno Matos wrote:
> >> Hello,
> >>
> >> Is it possible to control the broker's QoS for authenticated users, like
> >> bandwidth or dequeue rate?
> >>
> >
> > yes,
> >
> > rate can be controlled by setting
> >
> > --max-session-rate MESSAGES/S (0) Sets the maximum message rate per
> > session (0=unlimited)
> >
> >
> > when you start qpidd.
>
> That imposes a fixed publish rate on all sessions, which I don't think
> is what Bruno was asking for.
>
Yes, I was talking about a limit for each specific user or, at least,
for a specific session.
The optimal solution, for me, was based on Kbps.
Thank you!
Regards,
Bruno Matos
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org
Re: QoS - broker
Posted by Gordon Sim <gs...@redhat.com>.
On 07/08/2010 02:22 PM, Carl Trieloff wrote:
> On 07/08/2010 09:16 AM, Gordon Sim wrote:
>> On 07/08/2010 02:15 PM, Carl Trieloff wrote:
>>> On 07/08/2010 09:10 AM, Bruno Matos wrote:
>>>> Hello,
>>>>
>>>> Is it possible to control the broker's QoS for authenticated users,
>>>> like
>>>> bandwidth or dequeue rate?
>>>>
>>>
>>> yes,
>>>
>>> rate can be controlled by setting
>>>
>>> --max-session-rate MESSAGES/S (0) Sets the maximum message rate per
>>> session (0=unlimited)
>>>
>>>
>>> when you start qpidd.
>>
>> That imposes a fixed publish rate on all sessions, which I don't think
>> is what Bruno was asking for.
>
>
> ack, but I don't see that it would be possible to have diff rate per
> session, as session names come and go.
Right, but the request was for rates set by authenticated user.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org
Re: QoS - broker
Posted by Rajith Attapattu <ra...@gmail.com>.
On Mon, Jul 12, 2010 at 4:32 AM, Bruno Matos
<br...@paradigmaxis.pt> wrote:
> On Fri, 2010-07-09 at 11:20 -0400, Carl Trieloff wrote:
>> On 07/09/2010 08:27 AM, Andrew Kennedy wrote:
>> > On 9 July 2010 12:50, Bruno Matos<br...@paradigmaxis.pt> wrote:
>> >
>> >> On Thu, 2010-07-08 at 09:22 -0400, Carl Trieloff wrote:
>> >>
>> >>> The only options would be what we have, or have an ACL policy that sets
>> >>> the rate for a specific user or
>> >>> group of users, (which we don't have). Best for Bruno to clarify
>> >>> requirements / question.
>> >>>
>> >>> Carl.
>> >>>
>> >> ACL policy sounds really good! Its possible to make some changes to ACL
>> >> plug-in to support rate control, in Kbps, without packet loss?
>> >>
>> > I'm not sure ACLs are the right place for this, as you end up
>> > conflating security (authorisation) policy with operational (resource
>> > usage) policy.
>> >
>> > Andrew.
>> >
>>
These are borderline use cases that can be argued either way.
I think some of the use cases around QoS/resource usage can
potentially be security risks.
Infact there are outstanding JIRA's for things like limiting the
number of queues created per users etc..
The JIRA requests these be added to the ACL.
I haven't really had the opportunity to consider all the pros and cons
of each approach to make up my mind.
So I'd refrain from arguing one over the other.
However another potential approach is for these two modules to
collaborate with each other in enforcing the resource usage/QoS.
I am hoping to touch on this issue in my ACL proposal that is yet to
see any day light :).
>> Could be debated either way. For example, can do ACL to set the max
>> queue size
>> a user can create, and what types of queues. Setting the rate of data he
>> can send
>> falls pretty much into the same category would be my view. what do
>> others think?
>>
>> Carl.
>>
>
> It's my opinion, but if ACL is just for access control, maybe could be a
> QoS component for the kind of things you are describing. If there are
> already some other functionality in that module, I think that doesn't
> hurt to give it a little more with a refactoring in mind for the near
> future.
>
> Kindly regards and, once again, thank you a lot!
> Bruno Matos
>
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:users-subscribe@qpid.apache.org
>
>
--
Regards,
Rajith Attapattu
Red Hat
http://rajith.2rlabs.com/
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org
Re: QoS - broker
Posted by Bruno Matos <br...@paradigmaxis.pt>.
On Fri, 2010-07-09 at 11:20 -0400, Carl Trieloff wrote:
> On 07/09/2010 08:27 AM, Andrew Kennedy wrote:
> > On 9 July 2010 12:50, Bruno Matos<br...@paradigmaxis.pt> wrote:
> >
> >> On Thu, 2010-07-08 at 09:22 -0400, Carl Trieloff wrote:
> >>
> >>> The only options would be what we have, or have an ACL policy that sets
> >>> the rate for a specific user or
> >>> group of users, (which we don't have). Best for Bruno to clarify
> >>> requirements / question.
> >>>
> >>> Carl.
> >>>
> >> ACL policy sounds really good! Its possible to make some changes to ACL
> >> plug-in to support rate control, in Kbps, without packet loss?
> >>
> > I'm not sure ACLs are the right place for this, as you end up
> > conflating security (authorisation) policy with operational (resource
> > usage) policy.
> >
> > Andrew.
> >
>
> Could be debated either way. For example, can do ACL to set the max
> queue size
> a user can create, and what types of queues. Setting the rate of data he
> can send
> falls pretty much into the same category would be my view. what do
> others think?
>
> Carl.
>
It's my opinion, but if ACL is just for access control, maybe could be a
QoS component for the kind of things you are describing. If there are
already some other functionality in that module, I think that doesn't
hurt to give it a little more with a refactoring in mind for the near
future.
Kindly regards and, once again, thank you a lot!
Bruno Matos
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org
Re: QoS - broker
Posted by Carl Trieloff <cc...@redhat.com>.
On 07/09/2010 08:27 AM, Andrew Kennedy wrote:
> On 9 July 2010 12:50, Bruno Matos<br...@paradigmaxis.pt> wrote:
>
>> On Thu, 2010-07-08 at 09:22 -0400, Carl Trieloff wrote:
>>
>>> The only options would be what we have, or have an ACL policy that sets
>>> the rate for a specific user or
>>> group of users, (which we don't have). Best for Bruno to clarify
>>> requirements / question.
>>>
>>> Carl.
>>>
>> ACL policy sounds really good! Its possible to make some changes to ACL
>> plug-in to support rate control, in Kbps, without packet loss?
>>
> I'm not sure ACLs are the right place for this, as you end up
> conflating security (authorisation) policy with operational (resource
> usage) policy.
>
> Andrew.
>
Could be debated either way. For example, can do ACL to set the max
queue size
a user can create, and what types of queues. Setting the rate of data he
can send
falls pretty much into the same category would be my view. what do
others think?
Carl.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org
Re: QoS - broker
Posted by Andrew Kennedy <an...@gmail.com>.
On 9 July 2010 12:50, Bruno Matos <br...@paradigmaxis.pt> wrote:
> On Thu, 2010-07-08 at 09:22 -0400, Carl Trieloff wrote:
>> The only options would be what we have, or have an ACL policy that sets
>> the rate for a specific user or
>> group of users, (which we don't have). Best for Bruno to clarify
>> requirements / question.
>>
>> Carl.
>
> ACL policy sounds really good! Its possible to make some changes to ACL
> plug-in to support rate control, in Kbps, without packet loss?
I'm not sure ACLs are the right place for this, as you end up
conflating security (authorisation) policy with operational (resource
usage) policy.
Andrew.
--
-- andrew d kennedy ? edinburgh : +44 7941 197 134
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org
Re: QoS - broker
Posted by Bruno Matos <br...@paradigmaxis.pt>.
On Thu, 2010-07-08 at 09:22 -0400, Carl Trieloff wrote:
> On 07/08/2010 09:16 AM, Gordon Sim wrote:
> > On 07/08/2010 02:15 PM, Carl Trieloff wrote:
> >> On 07/08/2010 09:10 AM, Bruno Matos wrote:
> >>> Hello,
> >>>
> >>> Is it possible to control the broker's QoS for authenticated users,
> >>> like
> >>> bandwidth or dequeue rate?
> >>>
> >>
> >> yes,
> >>
> >> rate can be controlled by setting
> >>
> >> --max-session-rate MESSAGES/S (0) Sets the maximum message rate per
> >> session (0=unlimited)
> >>
> >>
> >> when you start qpidd.
> >
> > That imposes a fixed publish rate on all sessions, which I don't think
> > is what Bruno was asking for.
>
>
> ack, but I don't see that it would be possible to have diff rate per
> session, as session names come and go.
>
> The only options would be what we have, or have an ACL policy that sets
> the rate for a specific user or
> group of users, (which we don't have). Best for Bruno to clarify
> requirements / question.
>
> Carl.
ACL policy sounds really good! Its possible to make some changes to ACL
plug-in to support rate control, in Kbps, without packet loss?
Thank you a lot!
Regards.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org
Re: QoS - broker
Posted by Carl Trieloff <cc...@redhat.com>.
On 07/08/2010 09:16 AM, Gordon Sim wrote:
> On 07/08/2010 02:15 PM, Carl Trieloff wrote:
>> On 07/08/2010 09:10 AM, Bruno Matos wrote:
>>> Hello,
>>>
>>> Is it possible to control the broker's QoS for authenticated users,
>>> like
>>> bandwidth or dequeue rate?
>>>
>>
>> yes,
>>
>> rate can be controlled by setting
>>
>> --max-session-rate MESSAGES/S (0) Sets the maximum message rate per
>> session (0=unlimited)
>>
>>
>> when you start qpidd.
>
> That imposes a fixed publish rate on all sessions, which I don't think
> is what Bruno was asking for.
ack, but I don't see that it would be possible to have diff rate per
session, as session names come and go.
The only options would be what we have, or have an ACL policy that sets
the rate for a specific user or
group of users, (which we don't have). Best for Bruno to clarify
requirements / question.
Carl.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org
Re: QoS - broker
Posted by Gordon Sim <gs...@redhat.com>.
On 07/08/2010 02:15 PM, Carl Trieloff wrote:
> On 07/08/2010 09:10 AM, Bruno Matos wrote:
>> Hello,
>>
>> Is it possible to control the broker's QoS for authenticated users, like
>> bandwidth or dequeue rate?
>>
>
> yes,
>
> rate can be controlled by setting
>
> --max-session-rate MESSAGES/S (0) Sets the maximum message rate per
> session (0=unlimited)
>
>
> when you start qpidd.
That imposes a fixed publish rate on all sessions, which I don't think
is what Bruno was asking for.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org
Re: QoS - broker
Posted by Carl Trieloff <cc...@redhat.com>.
On 07/08/2010 09:10 AM, Bruno Matos wrote:
> Hello,
>
> Is it possible to control the broker's QoS for authenticated users, like
> bandwidth or dequeue rate?
>
>
yes,
rate can be controlled by setting
--max-session-rate MESSAGES/S (0) Sets the maximum message rate per
session (0=unlimited)
when you start qpidd.
Carl.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org