Issue 22: File type not mentioned in the policy file
Reported by postri...@gmail.com, Dec 28, 2008
What if the administrator does not provide tier information about any 
particular file type, user or group ?

This is a very common scenario. The administator cannot predict the file 
types any user may create at the time of configuration.

We can provide three solutions to it:
	-> We can allow the file to be placed on any tier. The default 
inode and block allocation strategy of the file system will be used in this 
case.

	-> We can ask the adminstrator to assign a particular tier where 
those files will be placed. The OHSM inode and block allocater will return 
error if there is no space on the specified tier.

	-> we can ask the administrator to assign a sequence of tiers where 
the OHSM inode and block allocater will try to allocate the file. The OHSM 
inode and block allocater will then try to assign space to the file in a 
sequential manner and will return error only when there is no space on all 
the tiers specified.

The final solution: 
	-> We will follow the first solution as it is more suitable. 

	-> The second solution is discarded because a user should not be 
disallowed to make files just because the administrator could not predict 
the file type.

	-> The third solution can be seen as a future enhancement

Dec 28, 2008
Project Member #1 sneha.hendre@gmail.com
Here we can do one thing ....
We can set a flag i.e the tiers will be assigned in ascending or descending order...
i.e.
If the allocation on the specified tier fail due to some reason.
Then user will specify for ascending priority or descending priority...
If its ascending priority then we will look for hot tiers.
If it is descending then we would look for cold tiers....

Wat say mainting one flag is not a big deal as I think.....
Dec 28, 2008
Project Member #2 imreckless@gmail.com
If admin is not aware of file types of a user then he can simply apply
UID policy.

i.e the admin is aware of the importance of the users,
he can specify a high cost disk for a developer while
a lower cost disk for a store manager.

So i suggest that we have already provided provision 
for situations like this, that's why we have different
policies, right, and the admin should be aware of 
the file types that users are working on,
so its for the admin to decide which policy he would enforce.
Jan 2, 2009
Project Member #3 checkout...@gmail.com
well Rishi, i think we should go for the first solution.

If the user fails to specify the tier_id for particular file then let the file be
allocated by normal ext2 allocation i.e. the file can be allocated to any tier within
the span of file system.
Status: Review-Req
Jan 14, 2009
Project Member #4 sandeepksinha
Well, close the issue if its nor relevant.

Atleast update it !!!
Jan 14, 2009
Project Member #5 sandeepksinha
(No comment was entered for this change.)
Cc: -fscops -sandeepksinha -rohitvashist2kk3 -imreckless -sneha.hendre -postrishi -checkout.vineet
Jan 14, 2009
#6 postri...@gmail.com
We are going by the first solution i.e. if the file does not qualify under any policy
then normal ext2 allocation algorithm will be applied
Status: Done
Cc: fscops sandeepksinha imreckless checkout.vineet sneha.hendre bharati.alatgi rohitvashist2kk3
Labels: -Type-Other Type-Info