Josh Thompson wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I'm hoping to get an RC artifact out for a vote early next week. We've been going through a test install to make sure the code is good and the installation notes are clear.

Here is a wiki page I have that's my checklist of what is left:

http://cwiki.apache.org/confluence/display/VCL/Release+2.1+checklist

I haven't crossed off the CHANGELOG part because I want to generate a new one right before making the svn tag.

Is there anything else we need to do before making the artifact and calling a vote?


I noticed on http://cwiki.apache.org/confluence/display/VCL/VCL+2.1+goals that one of the goals is 'Modularize OS code'. Is there a timeline for when (or what revision) that goal is to be met by?

The way the OS code is modularized out today has greatly improved from when I first started looking at the VCL code. However, I did a quick search for 'linux' and found the following subroutines with linux-specific code (I may have missed a few):

utils.pm:
setstaticaddress()
getdynamicaddress()
check_connect()
isconnected()
add_user()
del_user()

inuse.pm:
_notify_user_disconnect()

new.pm:
reserve_computer()

reclaim.pm:
process()

reserved.pm:
process()

As well as some code in the provisioning modules.


In addition, I think moving away from having a predefined windows, blade, lab, etc identity key and instead have determining which key to use being part of the OS module go go a long ways towards this modularization. Or better yet, move all the ssh calls into OS-specific modules so that someone can add support for an OS that doesn't require ssh (ie an alternate windows module).

Reply via email to