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 59: Implementation details of OHSM
1 person starred this issue and may be notified of changes. Back to list
Status:  Done
Owner:  postri...@gmail.com
Closed:  Feb 2009


 
Reported by postri...@gmail.com, Feb 1, 2009
The implementation details of the OHSM code flow are as follows:
	ohsm -e (enabling)
	-> validate wether device mentioned is actually mounted on the specified
mountpoint or not (1.0.1)
	-> wether the device is an ext2 FS or not ( 1.0.1)
	-> wether all the files have been entered (1.0.0)
	-> parse, validate and verify device tier file (1.0.0)
	-> parse, validate and verify the allocation policy file (1.0.0)
	-> parse, validate and verify the relocation policy file (1.0.0)
	-> send the policy files using ioctl
	-> the admin makes the data structure in the kernel spce
	-> the admin makes the ohsm_enabled flag SET

	ohsm -r 1 2 3(relocate)
	-> Display a "are you sure " message (1.0.0)
	-> check wether ohsm is enabled or not (1.0.0)
	-> check the underlying policy file for relocation (1.0.1)
	-> check wether rules enetered is correct ot not (1.0.1)	
	-> start the relocation (1.0.0)

	ohsm -s (stop)
	-> Display a "are you sure " message (1.0.0)
	-> UNSET the ohsm_enabled flag

Feb 2, 2009
Project Member #1 sandeepksinha
This is a duplicate of a some previous issue ?

Kindly verify and close any one !!!!!!!!!!!!!!
Feb 2, 2009
#2 postri...@gmail.com
This is not the duplicate 

I talks about the impementation details 
Feb 2, 2009
#3 postri...@gmail.com
Our proof of concept takes care of all the points marked as 1.0.0
Status: Done

Powered by Google Project Hosting