I'm not sure on the packaging. I've just been used to rolling the RPMs since I began with a hardware test environment, thus I needed to distribute the software to three separate servers and am just used to a ./waf rpm. Haven't really switched over to doing much with Maven, It's pretty quick on SSD.
Honestly I figured everyone else had a better way, I suppose the DevCloud stuff works for non KVM specific code. But really this VM dev environment has worked out really well. On Mon, Nov 12, 2012 at 9:59 PM, Satoshi Kobayashi < satosh...@stratosphere.co.jp> wrote: > Hi Marcus, > > Thank you for the information! > I see. Packaging is required now. > I am the same environment as you. > > 2012/11/13 Marcus Sorensen <shadow...@gmail.com>: > > Yeah, that would be good. Currently I have a virtual machine on my > desktop > > that is a full blown cloudstack install. Agent, mgt server, > > primary/secondary storage. It works well for me, I can develop on it and > > launch nested VMs with decent performance. It takes about two minutes to > > build and package. Not the most efficient, but I do like being able to > run > > a real environment and develop against it. > > On Nov 12, 2012 8:41 PM, "Satoshi Kobayashi" < > satosh...@stratosphere.co.jp> > > wrote: > > > >> Hi all, > >> > >> I have some questions/issues about the development approach of KVM > Agent. > >> > >> 1. Is there any document written about it? > >> I could not find it in cwiki.apache.org. Or is it in other places? > >> > >> 2. How should it be developed (in future)? > >> I looked at the source code of KVM Agent. It can not be launched from > >> Maven. > >> (I found that just executing is not enough because KVM Agent requires > >> some configurations and scripts) > >> It seems to require packaging, whenever change is added to the code. > >> I think that it is probably inefficient. > >> > >> A task required to develop from Maven which I think is the following. > >> - Add a configuration of maven-exec-plugin for KVM Agent to pom.xml. > >> - Add a configuration for m2e plugin of Eclipse (like "mvn jetty:run") > >> - Skip some checks in the development environment (for example, > >> agent.properties) > >> - Add configurations and scripts to be used to the path (or from args) > >> - Add a tool to cleanup a KVM host (optional?) > >> > >> Do you have any ideas? > >> > >> Regards, > >> Satoshi > >> > > > > -- > Satoshi Kobayashi <satosh...@stratosphere.co.jp> >
