Changes
/* State of the art */
* We can now combine these two existing scripts and create a wrapper (lets call it KVMBackup) which, in some way, adds some logic to the BackupKVMWrapper.pl. In fact the KVMBackup wrapper will generate the list of machines which need a backup.
The behaviour on our servers is as follows(c.f. Figure 2):# A The (decentralized) KVMBackup wrapper generates a list off all machines running on the current host.#* For each of these machines:#** Check if the machine is excluded from the backup, if yes, remove the machine from the list#** Check if the last backup was successful, if not, remove the machine from the list# Update the backup subtree for each machine in the list#* Remove the old backup leaf (the "yesterday-leaf"), and add a new one (the "today-leaf") #* After this step, the machines are ready to be backed up# Call the BackupKVMWrapper.pl script with the machines list as a parameter# Wait for the BackupKVMWrapper.pl script to finish# Go again through all machines and update the backup subtree a last time#* Check if the backup was successful, if yes, set sstProvisioningMode = finished (see also TBD) [[File:wrapper-interaction.png|500px|thumbnail|none|Figure 2: How the two wrapper interact with the LDAP backend]]
= Next steps =
[[Category: stoney conductor]]
