X-Git-Url: http://git.annexia.org/?p=libguestfs.git;a=blobdiff_plain;f=TODO;h=398abdce9d3f8d3f0e023b4ff5b15fb9a2274a65;hp=a76fd2e10799331a7b765ae05c62bf106ba52bd8;hb=92dc3748b6c236f09e7c699d4f841459fff4851c;hpb=995674a44aa00b3c68d47d367a8e92b610ffc700 diff --git a/TODO b/TODO index a76fd2e..398abdc 100644 --- a/TODO +++ b/TODO @@ -510,3 +510,57 @@ would be some sort of modified attach method (see link above). The complexity here is that we would no longer have access to stdin/stdout (or we'd have to direct that somewhere else). + +GObject Introspection +--------------------- + +We periodically get asked to implement gobject-introspection (it's a +GNOME thing): + +http://live.gnome.org/GObjectIntrospection + +This would require a separate Gtk C API since the main guestfs handle +would have to be encapsulated in a GObject. However the main +difficulty is that the annotations supported to define types are not +very rich. Notably missing are support for optional arguments +(defined but not implemented), support for structs (unless mapped to +other objects). + +Also note that the libguestfs API is not "object oriented". + +libosinfo mappings for virt-inspector +------------------------------------- + +Return libosinfo mappings from inspection API. + +virt-sysprep ideas +------------------ + + - touch /.unconfigured ? + - smolt ID + - Spacewalk / RHN ID + - Kerberos keys + - Puppet registration + - user accounts + - Windows sysprep + (see: https://github.com/clalancette/oz/blob/e74ce83283d468fd987583d6837b441608e5f8f0/oz/Windows.py ) + - blue skies: change the background image + - (librarian suggests ...) + . install a firstboot script virt-sysprep --script=/tmp/foo.sh + . run an external shell script + . run external guestfish script virt-sysprep --fish=/tmp/foo.fish + - log files (thanks Steve Grubb) + . as well as the obvious log files, also + utmp/wtmp/btmp/tallylog and pam_faillock's data files + - RNG seed (Steve Grubb) + - homedirs/.ssh directory, especially /root/.ssh (Steve Grubb) + - if drives are encrypted, then dm-crypt key should be changed + and drives all re-encrypted + - /etc/pki + (Steve says ...) + Rpm uses nss. Nss sets up its crypto database in + /etc/pki. Depending on how long the machine ran before cloning, you + may have picked up some certificates or things. This is an area + that you would want to look into. + - secure erase of inodes etc using scrub (Steve Grubb) + - touch /.autorelabel if we create any new files (thanks Dan Berrange)