On Mon, Jun 10, 2013 at 03:52:19PM +0800, Ryan Lei wrote: > CloudStack 4.1 has been released, but I see two "versions" of instructions > in setting up the oss development environment. > > (1) From the official website: > http://cloudstack.apache.org/develop/environment.html > > # Compile > $ mvn -P developer clean install > # Deploy both the management server and the database > $ mvn -P developer -pl developer,tools/devcloud -Ddeploydb > # Deploy the database again (??, devcloud involved?) > $ mvn -P developer -pl tools/devcloud -Ddeploysvr > # Start the Jetty server > $ mvn -pl :cloud-client-ui jetty:run > > (2) From INSTALL.md in the source code: > > # Compile > $ mvn clean install -P systemvm,developer > # Deploy both the management server and the database > $ mvn -P developer -pl developer -Ddeploydb > # Export this if using remote debugging > $ export MAVEN_OPTS="-Xmx1024m -XX:MaxPermSize=500m -Xdebug > -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n" > # Start the Jetty server > $ mvn -pl :cloud-client-ui jetty:run > > I'm using a physical host for XCP/XenServer, not devcloud, with CloudStack > + MySQL running on a separate CentOS VM. > I previously used version (2) to compile git 4.1 branch, but I used > "-DskipTests=true" in the compile step to save time. Is this the right way? > What does the "-P systemvm" actually mean in the command?
(2) will work against 4.1. The systemvm profile builds the systemvm.iso which is used to patch scripts on the systemVMs. To use an external host, you can skip deploysvr step and add your hosts from the UI. In build/replace.properties you will need to specify the DBHOST to point to your mysql instance. Or else deploydb assumes you are running the db on localhost. In (1) the order of steps are wrong. One should do jetty:run before doing -Ddeploysvr. HTH -- Prasanna., ------------------------ Powered by BigRock.com
