Google logo

Google Earth Enterprise Documentation Home | Fusion administration

Manage Fusion disk space

Fusion writes all assets, projects, and databases to the asset root directory (typically named /gevol/assets). As a result, the asset root can fill up quickly.

You can put source data, such as raw images, in a different directory like /gevol/src, but the asset root can still fill up from processing source files. Cleaning assets, projects, and databases helps reduce the disk use in the asset root, but eventually the volume will fill up completely.

A good way to create free space in your asset root is to move your pyramid files to auxiliary storage. When you create and build a new imagery asset, pyramid (.pyr) files are also created, and are saved to the raster.kip and mask.kmp directories. Google delivers most of its data to customers in pyramid format. The pyramid files must always be available to the Fusion server, but after they're built, they don't change size. That makes them good candidates for moving to a separate storage location.

The result of moving your .pyr files is an asset that stores configuration files in the asset root, and large pyramid files in auxiliary storage. Besides creating space in your asset root, there are other advantages to moving your pyramid files:

Moving pyramid files

There are a few different ways to move pyramid files out of an asset root that is filling up:

To copy the pyramid files and re-create the asset:

After the raster.kip and mask.kmp directories are created and the asset is finished building, all of the information needed to copy and re-use the asset is inside these two directories. There are other files in the asset directory, but they are auxiliary and not needed. The basic strategy for managing disk space is:

  1. Locate the asset to be moved. It will be in a directory with a .kiasset extension.
     
  2. Locate the raster.kip and the mask.kmp directories under the asset directory:

    find $asset.kiasset -type d -name raster.kip
    find $asset.kiasset -type d -name mask.kmp

     
  3. Copy the raster.kip and mask.kmp directories to the auxiliary storage volume:

    cp -av $kip $new_location/$asset.kip
    cp -av $kmp $new_location/$asset.kmp

    Note: The auxiliary storage volume must be a defined Fusion volume. You can define the new volume with the geconfigurefusionvolume command. Volumes are presented to the server as NFS file systems, and those can't be nested. For example, NFS does not allow Volume1 and Volume2 to be mounted as /Volume1/Volume2.

  4. Rename the raster.kip and mask.kmp files so that they have the same name. The name should be descriptive of the asset. For example, if the asset is EastChicago.kiasset, the directories should be called EastChicago.kip and EastChicago.kmp.
     
  5. Modify the imagery asset with the gemodifyimageryasset command, using the same name that the asset was originally created with:

    gemodifyimageryasset -o imagery/EastChicago -havemask /gevol/newvolume/imagery/EastChicago.kip

    For more details about the commands to re-create the assets, see Importing Preprocessed Resources in the Google Earth Enterprise Reference Guide.

  6. Rebuild the imagery project and any database that contains the imagery project:

    gebuild imagery/EastChicago.

    The gemodifyimageryasset and gebuild commands will complete in seconds, because the heavy processing took place when the pyramid files were generated.

  7. Clean the imagery projects and databases using the Fusion UI:
    1. From the Asset Manager, right-click the project or database and select Asset Versions.
    2. Right-click the previous version and select Clean. Cleaning the project and database also cleans all the assets, removing the pyramid files from the asset root and freeing up quite a bit of space.
    3. Verify that each of the assets that were modified were cleaned, and that the pyramid files were removed from the asset root.

Note: The asset expects the pyramid files to remain in the same location you specified in the gemodifyimageryasset command. Don't move the pyramid files to a new location after you've copied them and then modified, built, and cleaned the asset.

Example script

The example below copies all the pyramid files from /gevol/assets/imagery to /gevol/volume1.

 # The commands are echoed to the terminal so you can review them before executing.
 # To enable the commands, uncomment the following line:
 # do_command=true

 asset_root=/gevol/assets
 asset_directory=Resources/Imagery
 new_location=/gevol/volume1

 cd $asset_root/$asset_directory
 for asset in `ls | grep kiasset | sed 's/\.kiasset//'`
 do

 # Find the raster.kip and mask.kmp under the asset directory
 kip=`find $asset.kiasset -type d -name raster.kip`
 kmp=`find $asset.kiasset -type d -name mask.kmp`


 # Copy the raster and mask directories to the new volume
 echo "cp -av $kip $new_location/$asset.kip"
 if [ "$do_command" == "true" ]; then cp -av $kip $new_location/$asset.kip; fi
 echo "cp -av $kmp $new_location/$asset.kmp"
 if [ "$do_command" == "true" ]; then cp -av $kmp $new_location/$asset.kmp; fi


 # modify and build each of the imagery assets
 echo "gemodifyimageryresource --havemask -o $asset_directory/$asset $new_location/$asset.kip"
 #if [ "$do_command" == "true" ]; then gemodifyimageryresource --havemask -o $asset_directory/$asset $new_location/$asset.kip; fi
 echo "gebuild $asset_directory/$asset"
 if [ "$do_command" == "true" ]; then gebuild $asset_directory/$asset; fi
done

 # Rebuild, then clean the imagery project and the database,
 # then verify that all the assets were cleaned.