My favorites | Sign in
Project Home Downloads Wiki Issues Source
READ-ONLY: This project has been archived. For more information see this post.
Search
for
  Advanced search   Search tips   Subscriptions
Issue 91: Limit on number of policies
1 person starred this issue and may be notified of changes. Back to list
Status:  WontFix
Owner:  rishi.b....@gmail.com
Closed:  Jul 2009


 
Reported by rishi.b....@gmail.com, Jul 17, 2009
Hello All,

In the new code I see that we have added a limit of 100 policies in
allocation policy whereas the older code was supporting any number of policies.

Will we go ahead with the limit or some solution has to be found out for this
??
Jul 17, 2009
Project Member #1 sandeepksinha
Agree with your point, but if you try and be realistic. Do you feel you will have 100
allocation and 100 relocation policies. 

Rather, I would frame it this way that a lot of space would be wasted if the number
of policies are less than 100. 
The reason why I made the allocation static was that there was a complete rewrite and
the code was getting complex. So, hence in order to keep it simple I wrote it that way.

Now as the code is stable and functional. We could simply go ahead and make the
allocation dynamic. But remember it will have a couple of implications too.

For allocation/relocation policy, this looks perfectly fine. But as far as the device
info is concerned, lets have this static.

The problem is that we don't know the number of underlying PV's within the LV.
We only come to know about it, after traversing it. Hence, keeping that as static
would be OK.

Or having a single pass there to get the count will still be ok, as its just a one
time operation.

Comments please? 
Jul 20, 2009
#2 rishi.b....@gmail.com
Making the priority as low and closing the issue as the code will work fine without
this enhancement
Status: WontFix
Labels: -Priority-Medium Priority-Low

Powered by Google Project Hosting