Hi folks, I spent a bit of time going through the patches directory and working on license headers today.
Historically CloudStack has made a Debian-based systemvm template available for each hypervisor. However, my sense is that going forward we will not be able to do this because of licensing issues. However, the need for a systemvm will not be eliminated, so I'd like to come up with some ideas on how to mitigate this. My only initial thought is that we'd have only the body of code that the systemvm uses exclusively for CloudStack (and remove all of the other bits like vhdutil) and the config tree.) and that we would additionally provide some packaging around those bits so that a user could deploy that package to a debian or fedora-based system and have a working systemvm. Thoughts, comments, flames? --David
