[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Doubt
Hi Srikanth,
I'm cc-ing the response to hrac submitters mail list so that they can
participate in answering your questions too.
>
> Hi Konstantin,
>
> Had another doubt; This is regarding PolicyName that is used in
> the PolicyEvaluator.
>
> Suppose there is only one PolicyEvaluator for the whole system (It
> understands and can evaluate all the policies). Now, for each
> ResourceName there could potentially be (though there will not be) a
> unique Policy. So will there be a PolicyName for each unique Policy
> which would lead to a very large (ResourceName-PolicyName) list? I
> hope you understand the question ?
It's correct. If for each resource name, there is a unique policy then the list
that maps a resource name into a policy is proportional to number of resource
names. However, if your policies are such that a group of resource names is
associated with the same policy, then (but not with the current version of
PolicyEvaluatorAdmin) some grouping mechanisms, such as regular expressions or
assumptions about tree-like organization of resource names, could be used to
reduce the mapping list size.
The question here, and it's more to the submitters than to you, is if
PolicyEvaluatorAdmin should have the capability to manipulate with groups of
resource names.
>
> Also in the PolicyEvaluatorAdmin Interface, there is a method
>
> replace_policy (
> in PolicyName policy_name
> in ResourceName resource_name);
>
> shouldn't it be PolicyNameList instead of PolicyName since
> add_policy has the same arguments ??
no because add_policy takes only one policy. I do not see a mistake here.
Thanks for your questions.
Konstantin
----------------
Broadcast message to hrac-rfp from Konstantin Beznosov <beznosov@baptisthealth.net>.
Go to http://cadse.cs.fiu.edu/omg/hrac-rfp to browse the mail list archive.
- Follow-Ups:
- Re: Doubt
- From: Srikanth Kotha <kotha@cse.Buffalo.EDU>