In addition to the creation time (ctime) and modification time (mtime) in the Cobbler 1.3. XMLRPC API, there is now a Universal Identifier (UID) that can be used to identify objects if manipulating them from another application, so that if the name of the object changes, the original identity of the object can still be tracked. This will not be displayed anywhere in the application.
A new UID is generated on a copy, but not on an edit or rename.
For example, here's a trivial copy(where we don't actually change the values of any fields):
cobbler image copy --name=i1 --newname=i2
1. diff /var/lib/cobbler/config/images.d/i /var/lib/cobbler/config/images.d/i2 2. 9,10c9,10 3. < mtime: 1227045053.86 4. < name: i 5. --- 6. > mtime: 1227567387.23 7. > name: i2
This works the same as with API calls.
Perhaps of limited interest, though I wanted to point as I won't likely advertise it heavily later :)
Cobbler still uses the object name as it's "key", so there is really no behavior in Cobbler that uses the UID, but it's there for other API using applications that might want to know if an object is renamed.
--Michael
cobbler@lists.fedorahosted.org