Skip to Content.
Sympa Menu

comanage-dev - [comanage-dev] soliciting use cases: metering, throttling and possibly auditing

Subject: COmanage Developers List

List archive

[comanage-dev] soliciting use cases: metering, throttling and possibly auditing


Chronological Thread 
  • From: heather flanagan <>
  • To: , CoMaNaGe-DeV List <>
  • Subject: [comanage-dev] soliciting use cases: metering, throttling and possibly auditing
  • Date: Wed, 9 Feb 2011 07:44:54 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=tCbwNhu8VaEVgVsNzC+ak0aCT/ZRj5+PI+8KB7sLNhWag1JXvDbhjovlkSePk7v+Vx jYnC14ZhdAMjAvjwk2Cxe56eeP+FsqXEsgjY6liIJGT7EFwNSU46QJE6uZsSeUguKfGj /ZARydJd+G56kLPXcQUMS9HaXbtBiFFx77XPw=

Hi all -

One of the VO we're working with has a request for the potential
inclusion of metering and throttling capabilities to a collaboration
management platform. Specifically, they are thinking of one place to
record the limits a person or a group might have on amount of data,
access to VM-type resources, data flow rates, etc. This may or may
not be a problem for the apps themselves. There is certainly an
argument for something to be recorded in a person or groups
information attributes? profile? about the details of the limits that
would then get pushed to the application to apply.

So, since we're hearing about this from just one VO, we're interested
in hearing if anyone else has a similar request or use case for this
kind of information. Feedback?

Thanks!
-heather f.



Archive powered by MHonArc 2.6.16.

Top of Page