Browse Prior Art Database

Method for pruning OS demo images Disclosure Number: IPCOM000193823D
Publication Date: 2010-Mar-10
Document File: 3 page(s) / 74K

Publishing Venue

The Prior Art Database


A method is disclosed for reducing the disk space of computer machines according the specific business value. The main idea is to monitor the FileSystem access during the execution of the business required scenarios and to clean up the unused files. The method used on VM images gives the possibility reduce the required disk-footprint.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 52% of the total text.

Page 1 of 3

Method for pruning OS demo images

Generally computer machines are installed and configured to provide specific business services. To build these services the installation provides the entire operating system and many useless features and files that increase the disk usage without a required business value.

Existing solutions give the possibility to clean up the disk space removing temporary directories, the recycle bin, application caches and so on. Other solutions try to leverage the "Last Access Time" attribute to detect unused files. Anyway all of them have drawbacks and in general are not very reliable in identifying all the actual unused files
(i.e. the "Last Access Time "attribute is not always updated by the operating system; most of such applications just are able to identify temporary files and application cache files).

The proposed solution uses the following components (see Figure 1):

• Disk Cleaner Manager: the component is responsible for capturing reports of the file system access and for proposing to the user resources to be deleted. It is built with the following subsystems:
a) Cleaning Notification UI: It is used to propose to the user the files to delete.

b) FileSystem Filter Driver: It is responsible for retrieving information from the FileSystem Monitor Agent in order to filter resources to the FileSystem Analyser. This subsystem can be developed through plugging in order to accept reports from different FileSystem Monitor Agent types.

c) Policy Manager: It is used in order to create the policies adopted for the filtering process. It can be initialised with the required footprint (max size of the machine) and OS Kernel stuff. Example of policies should be:

Include resources not accessed for 6 months.

Exclude file list (list of files that must be excluded from the cleaning process).
d) FileSystem Analyser: It acquires input from the FileSystem Filter Driver and Policy Manager in order to create the delete actions and to propose them to the user through the Cleaning Notification UI.

• FileSystem Monitor Agent (third part component).

The component monitors the file system and provides reports of the process's access to the files.

• FileSystem (machine hardware component).

The FileSystem Monitor Agent monitors the FileSystem and captures information related to the access of processes to the files. The FileSystem Filter Driver retrieves this information and filters them. The FileSystem Analyser applies the policies defined in the Policy Manager and the input provided by the FileSystem Filter Driver in order to generate a list of resources that shou...