Libguestfs - Jul 2009 - virt-v2v

I've attached v2v/STATUS. There's still a bit to do. I'm not yet 
proposing this for inclusion, just discussion.

Apart from the tool itself, I think there's mileage in considering how 
the functionality of Sys::Guestfs::Lib could be given more structure. I 
think there's considerable mileage in moving much of Sys::Guestfs::Lib 
into Sys::Guestfs::GuestOS.

I haven't tried to code anything for Debian in what's here. However, the
intention is that a Sys::Guestfs::GuestOS::Debian module would implement 
this. Much of the functionality in Sys::Guestfs::GuestOS::RedHat should 
be common with Debian, so I'd expect common code to be stripped out of 
it, maybe into Sys::Guestfs::GuestOS::Linux.

The best way to read the code is to start from 'Start of processing' in 
virt-v2v.pl. Everything above that is trivia to do with command line 
parsing. The main body is only a single page, and shows what order 
things are called into, and how they fit together.

Matt
-- 
Matthew Booth, RHCA, RHCSS
Red Hat Engineering, Virtualisation Team

M:       +44 (0)7977 267231
GPG ID:  D33C3490
GPG FPR: 3733 612D 2D05 5458 8A8A 1600 3441 EA19 D33C 3490
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: STATUS
URL:
<http://listman.redhat.com/archives/libguestfs/attachments/20090724/93c1bfe9/attachment.ksh>

On Fri, Jul 24, 2009 at 10:45:43PM +0100, Matthew Booth
wrote:
> I've attached v2v/STATUS. There's still a bit to do. I'm not
yet
> proposing this for inclusion, just discussion.
Status/doc files there are fine, as long as they are kept up to date
or removed as soon as they are no longer necessary.  So this file
should be committed, or if you prefer, integrated into the top-level
TODO file.
> Apart from the tool itself, I think there's mileage in considering how
> the functionality of Sys::Guestfs::Lib could be given more structure. I  
> think there's considerable mileage in moving much of Sys::Guestfs::Lib
> into Sys::Guestfs::GuestOS.
Agreed, in fact necessary.  Having duplicate code is a terrible idea.
> POD everywhere
Documentation is very important - and unfortunately tends not to get
written if the code goes in first.  So I propose that we don't allow
any contributions to go upstream unless they have full POD.
> Online help for module specific options
What are you proposing for this?  Most stuff is documented by manual
pages, which I think is perfectly sufficient.  Also the manpages get
copied to the website (if that was what you meant by "Online").

Rich.

-- 
Richard Jones, Emerging Technologies, Red Hat  http://et.redhat.com/~rjones
virt-df lists disk usage of guests without needing to install any
software inside the virtual machine.  Supports Linux and Windows.
http://et.redhat.com/~rjones/virt-df/