Filter
Top Products
iPump 6420 User’s Manual
www.wegener.com 800070-01 Rev B Chapter 3, Page 78
Figure 3-16: Asset Healing in operation
Asset Folder on MPcm:
<asset root>\assets\
AssetName
File:
AssetName.ini
[SendChanges]
<address>=ObjName
File:
FirstMediaFile.mp2
File:
LastMediaFile.mp2
For this remote
address, ether a
serial number or
group...
…make sure this
asset, and it’s files,
are sync’d between
the iPumps at the
target address and
this uplink control
system.
Asset Folder on CSM:
/var/www/html/media/
AssetName
File:
AssetName.ini
[SendChanges]
<address>=ObjName
File:
FirstMediaFile.mp2
File:
LastMediaFile.mp2
File:
metadata.xml
STEP #1:
CSM finds all such “hot” assets,
and copies them over to the
CSM folder shown. Then it
creates this file in each asset
folder, which summarizes all
files currently in Asset at uplink.
Asset Folder on remote iPump
(one of N targeted by the
address in AssetName.ini):
<asset root>\assets\
AssetName
File:
AssetName.ini
[SendChanges]
<address>=ObjName
File:
FirstMediaFile.mp2
File:
MissingMediaFile.mp2
iPump, before resync...
File:
LastMediaFile.mp2
File:
ExtraMediaFile.mp2
File:
metadata.xml
iPump has extra files no
longer authorized for this
asset
iPump is missing files
which are still
authorized for this
asset
STEP #2:
CSM downloads the file “metadata.xml” to the target asset
folder in all iPumps at the address spec’d in the
“AssetName.ini” file. Included within that file are “Action
Tags” which requests the iPump implement the STORAGE
CONFIRM & STORAGE CLEANUP functions.
NOTE: If asset folder does exist on any addressed iPump,
then it is created and “metadata.xml” is copied therein.
WEGENER “Asset Healing”, an Overview
Rev
7/21/2009 5:05 PM
The Goal
STEP #3:
In response to the STORAGE
CONFIRM Action tag, the
iPump uses Return Path to
send a negative ACK to CSM
for each and every file spec’d
in “metadata.xml” which is
missing from this asset folder.
Asset Folder on remote iPump
(one of N targeted by the
address in AssetName.ini):
<asset root>\assets\
AssetName
File:
AssetName.ini
[SendChanges]
<address>=ObjName
File:
FirstMediaFile.mp2
File:
MissingMediaFile.mp2
iPump, after resync...
File:
LastMediaFile.mp2
File:
ExtraMediaFile.mp2
File:
Z_metadata.xml
STEP #4:
CSM re-downloads any file flagged
by a NACK to the target address in
“AssetName.ini” (which may include
a group in which this iPump is one
member).
STEP #5:
In response to the STORAGE
CLEANUP Action tag, the iPump
quietly deletes all files not specified
in “metadata.xml”.
Non-existent OR
deleted file
Existing file
File
Legend
}
}
ASSET HEALING:
Asset healing is initiated when the
“csm_fsync.pl” script is invoked (from an
FSYNC shell script called from “cron” on the
COMPEL/CSM machine). This causes the first
2 steps to be executed within CSM. The
response to the incoming file NACKs from field
iPumps is handled by the “mpcm_compel.cgi”
script. (Note that Step #5 shown does not
literally occur, in time, after steps #3 and 4. But
since the process of getting files re-downloaded
is not connected to the process of deleting the
“unauthorized files”, this is irrelevant to
understanding the steps involved.)
CSMMPcm
STEP #6:
When done, the iPump renames the
“metadata.xml” file to
“z_metadata.xml”, deleting any
previous version of
“z_metadata.xml”.