Hi Edison, > 2. package agent from plugins/hypervisors/kvm/target/kvm-agent.zip
Do you have any more information on how to do this? >From a previous mail on the list, I saw: >> Using "ant package-agent", which will create agent.zip under dist/, then >> copy and unzip agent.zip on kvm host or inside system vm. >> Modify conf/agent.properties, if it's kvm agent, resource = >> *LibvirtResource*, if it's secondary agent, resource = *NfsSecondary* >> Execute './run.sh', will start agent. >> But I remember there has bug in run.sh though, the some jar files are >> missing. However, there seem to be several further steps which would be needed in order to install the agent on a machine, e.g.: * Add jars (e.g. jna) to the system, and add the jar to the classpath in run.sh * Move cloudutils python packages to python site-libs dir * Create init scripts in /etc/init.d/ These are just the steps off the top of my head - it seems like a lot of fiddly manual work, so I'm guessing I must be missing something. Assuming a vanilla Ubuntu 12.04 install, and assuming that you have kvm-agent.zip, are the steps for install listed in a wiki / doc anywhere? Thanks, Dave. On Tue, Nov 6, 2012 at 12:20 PM, Edison Su <edison...@citrix.com> wrote: > > > > -----Original Message----- > > From: Dave Cahill [mailto:dcah...@midokura.jp] > > Sent: Monday, November 05, 2012 7:06 PM > > To: cloudstack-dev@incubator.apache.org > > Subject: Re: Proposed fixes for debian package building process > > > > Hi Edison, > > > > Understood - sounds like .deb package building is not supposed to work on > > master. > > > > Do you know if anyone is working on making .deb building work using maven > > on master? From the first thread you linked [1], it sounded like Noa > Resare at > > Spotify might start working on it, but I don't see any activity after > that. The > > wiki mentions this branch in relation to getting debs / maven working, > but it > > doesn't seem to have been updated in a month: > > https://github.com/bhaisaab/incubator-cloudstack/tree/debs-maven > > > > If no-one is working on .deb package building, is there an alternative > way to > > keep developing on master with debian / Ubuntu? I can easily run the > > management server from source ("mvn -pl :cloud-client-ui jetty:run"), but > > running the agent from source is a bit messier, as the management server > > needs to SSH into the host and run the agent via the init script ("sudo > service > > cloud-agent start"). > > The temporary solution: > 1. package mgt server from > client/target/cloud-client-ui-4.1.0-SNAPSHOT.war. > John has problem about deploy war in tomcat( > http://markmail.org/message/3p7qyvzj5tg5w7tx) > 2. package agent from plugins/hypervisors/kvm/target/kvm-agent.zip > > > > > I should also mention that by fixing the "mvn -P deps -pl deps" issue I > > mentioned above, I was able to run dpkg-buildpackage successfully, > install > > the resultant .debs successfully on an Ubuntu 12.04 machine, and get a > basic > > CloudStack setup (2 guest VMs, basic networking) working that way. If > > building that way results in .debs which shouldn't work, should we remove > > some of the broken options (e.g. the maven "deps" profile) from master to > > avoid confusion? > > > > Any input appreciated. > > > > Thanks, > > Dave. > > > > > > [1] http://markmail.org/message/lsjigqvnbkjtbl4y > > > > > > > > > > > > > > On Tue, Nov 6, 2012 at 3:59 AM, Edison Su <edison...@citrix.com> wrote: > > > > > I don't the deb build on master will work, as we moved build system > > > from ant to maven, the artifacts build by maven is quite different > > > from ant(regarding to the path). You can find the discussion about the > > > build system in the following the mail threads: > > > http://markmail.org/message/lsjigqvnbkjtbl4y > > > http://markmail.org/message/utce4esqjl7xhwr4 > > > > > > -----Original Message----- > > > From: Dave Cahill [mailto:dcah...@midokura.jp] > > > Sent: Monday, November 05, 2012 1:13 AM > > > To: cloudstack-dev@incubator.apache.org > > > Subject: Proposed fixes for debian package building process > > > > > > Hi, > > > > > > There appear to be some errors in the debian package building process; > > > I'd like to double-check my approach for fixing them. > > > > > > The wiki [1] gives the procedure for building debian packages as: > > > mvn install -P deps && dpkg-buildpackage > > > > > > However, mvn install -P deps fails with: > > > > > > [ERROR] Failed to execute goal on project cloud-deps: Could not > > > resolve dependencies for project > > > org.apache.cloudstack:cloud-deps:jar:4.1.0-SNAPSHOT: Could not find > > > artifact org.apache.cloudstack:cloud-awsapi:jar:4.1.0-SNAPSHOT in > > > apache.snapshots (http://repository.apache.org/snapshots) -> [Help 1] > > > > > > The reason for this failure seems to be this section of deps/pom.xml: > > > <dependency> > > > <groupId>org.apache.cloudstack</groupId> > > > <artifactId>cloud-awsapi</artifactId> > > > <version>${project.version}</version> > > > </dependency> > > > > > > ${project.version} is 4.1.0-SNAPSHOT, however looking at > > > > > https://repository.apache.org/content/groups/snapshots/org/apache/clou > > > dstack/cloud-awsapi/ > > > , > > > I only see 4.0.0-SNAPSHOT. > > > > > > If I replace ${project.version} for cloud-awsapi in deps/pom.xml with > > > a hardcoded "4.0.0-SNAPSHOT", mvn -P deps succeeds. An alternative fix > > > would be if 4.1.0-SNAPSHOT version of cloud-awsapi was available on > > > repository.apache.org. > > > > > > I also found that in order for dpkg-buildpackage to succeed, I needed > > > to run "mvn install -P deps -pl deps" rather than just "mvn install -P > deps". > > > > > > For reference, if you run dpkg-buildpackages without running "mvn -P > > > deps", the error returned is: > > > /PATH/incubator-cloudstack/build/build-aws-api.xml:34: taskdef class > > > org.apache.axis2.tool.ant.AntCodegenTask cannot be found > > > > > > Lastly, I would have expected "mvn clean" to remove the .jars in the > > > deps folder, however it does not - this made debugging "interesting"! > > > > > > Proposed changes: > > > * Hardcode 4.0.0-SNAPSHOT as the version of cloud-awsapi in > > > deps/poms.xml > > > * Change the wiki to reflect the fact that "mvn install -P deps -pl > deps" > > > needs to be run when building debian packages > > > * Change mvn clean to remove the jars from the deps folder > > > > > > Please let me know if those changes make sense, or if I'm missing > > > something. If they look OK, I'll create a patch and submit. > > > > > > Thanks, > > > Dave. > > > > > > [1] > > > > > > > > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Building+with+M > > > aven#BuildingwithMaven-BuildingCloudStack > > > > > > > > > > > -- > > Thanks, > > Dave. > -- Thanks, Dave.
