Rohit, I've spent quite a bit of time fixing all the veewee and vagrant configs in tools devcloud, and also re-rewirting the puppet stuff. I understand that you create the image yourself because it's a hassle to do so yourself. My work has alleviated that problem.
RIght now the fruit of my labor is a fully ready configured vm, I just need instructions on how to deploy the build to it. There is nothing on http://rohityadav.in/logs/devcloud that mentnions how to do so. - James On Fri, Nov 30, 2012 at 2:51 AM, Rohit Yadav <rohit.ya...@citrix.com> wrote: > James, I see your point, this will probably be fixed later on. We need to fix > the veewee and vagrant configs in tools/devcloud. > Right now I created only the image as most people would not want to create > their own. If you're looking to create your own, checkout diy section of > http://rohityadav.in/logs/devcloud > The problem is I've used Debian Wheezy, configuring the vagrant box was > tricky also some packages like mkisofs and maven3 will have to fetched as > they are not on distro's repos. > Any help in fixing these scripts would be great. > > Regards. > > ________________________________________ > From: James Martin [jmar...@basho.com] > Sent: Friday, November 30, 2012 1:10 PM > To: cloudstack-dev@incubator.apache.org > Subject: Re: back in the game, deploying to devcloud > > Just to clear things up -- I'm not using an image at all. I'm working > on the stuff that builds devcloud. I'd like devcloud to be part of > the source tree, not something external that you download. I feel > this makes for a cleaner development experience and forces the > creation of the devcloud image to remain in the core codebase. > > The goal is to be able, from the cloudstack project root: > > cd tools/devcloud > vagrant up > vagrant ssh > > In order for this to work it requires a vagrant basebox, and a vagrant > xenbox. Currently in my fork these are built cleanly with veewee, > vagrant, and puppet via a shell script by simply: > > cd tools/devcloud/deps > ./boxer.sh -b all > > And you end up with: > > vagrant box list > devcloudbase (virtualbox) > devcloudbase-xen (virtualbox) > > Once those vagrant boxes are completed you'd run, > > cd ../ > vagrant up > vagrant ssh > > vagrant ssh > Welcome to Ubuntu 12.04.1 LTS (GNU/Linux 3.2.0-29-generic-pae i686) > > * Documentation: https://help.ubuntu.com/ > Last login: Fri Nov 30 05:29:32 2012 from 10.0.2.2 > devcloud@devcloud:~$ ls /opt/cloudstack/ > apache-tomcat-6.0.32 apache-tomcat-6.0.32.zip incubator-cloudstack > startdevcloud.sh > > and now you have an clean devcloud vagrant install. If you ever screw > up the system, > you simply: > vagrant destroy > vagrant up > > to start fresh > > I have all of that completed. I just want to be able to install a > build to this blank vm. It seems like I should follow these steps: > > https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+devcloud+environment+setup > > but I receive an error here: > > mvn -P developer -pl developer,tools/devcloud -Ddeploydb > [INFO] Scanning for projects... > [INFO] > ------------------------------------------------------------------------ > [INFO] Reactor Build Order: > [INFO] > [INFO] Apache CloudStack Developer Tools > [INFO] Apache CloudStack Developer Tools > [INFO] > [INFO] > ------------------------------------------------------------------------ > [INFO] Building Apache CloudStack Developer Tools 4.1.0-SNAPSHOT > [INFO] > ------------------------------------------------------------------------ > [INFO] > [INFO] --- properties-maven-plugin:1.0-alpha-2:read-project-properties > (default) @ cloud-developer --- > [WARNING] Ignoring missing properties file: > /Users/jmartin/work/code/basho-cloudstack/utils/conf/db.properties.override > [INFO] > [INFO] --- maven-remote-resources-plugin:1.3:process (default) @ > cloud-developer --- > [INFO] > [INFO] --- maven-antrun-plugin:1.7:run (default) @ cloud-developer --- > [INFO] Executing tasks > > main: > [copy] Copying 60 files to > /Users/jmartin/work/code/basho-cloudstack/developer/target/db > [copy] Copying 9 files to > /Users/jmartin/work/code/basho-cloudstack/developer/target/db > [INFO] Executed tasks > [INFO] > [INFO] --- sql-maven-plugin:1.5:execute (drop-database) @ cloud-developer --- > [INFO] > ------------------------------------------------------------------------ > [INFO] Reactor Summary: > [INFO] > [INFO] Apache CloudStack Developer Tools ................. FAILURE [2.025s] > [INFO] Apache CloudStack Developer Tools ................. SKIPPED > [INFO] > ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] > ------------------------------------------------------------------------ > [INFO] Total time: 2.947s > [INFO] Finished at: Fri Nov 30 02:15:39 EST 2012 > [INFO] Final Memory: 12M/81M > [INFO] > ------------------------------------------------------------------------ > [ERROR] Failed to execute goal > org.codehaus.mojo:sql-maven-plugin:1.5:execute (drop-database) on > project cloud-developer: Communications link failure > [ERROR] > [ERROR] The last packet sent successfully to the server was 0 > milliseconds ago. The driver has not received any packets from the > server. Can not read response from server. Expected to read 4 bytes, > read 0 bytes before connection was unexpectedly lost. > [ERROR] -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with > the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, > please read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException > > > I don't believe that it's connecting to the vagrant vm I have running > and doing the proper deploys. How can we fix this? > > Thanks! > > James > > > > On Thu, Nov 29, 2012 at 7:12 PM, Rohit Yadav <rohit.ya...@citrix.com> wrote: >> Irrespective of whatever cloudstack version you're on, you don't have >> different workflows for 4.0 and asf master, just build, deploydb and run the >> mgmt server as you have on your laptop, using the new devcloud image: >> http://people.apache.org/~bhaisaab/cloudstack/devcloud/devcloud2.ova >> >> And make sure to set these global settings and restart mgmt server, before >> you deploy a basic zone: >> >> host = 192.168.56.1 >> system.vm.use.local.storage = true >> management.network.cidr = 192.168.56.0/24 >> secstorage.allowed.internal.sites = 192.168.56.0/8 >> >> If you're want to build inside use host ip equal to 192.168.56.10. Checkout >> instructions on working with ASF master and the new devcloud in the DevCloud >> 2.0 section: http://rohityadav.in/logs/devcloud/ >> >> Hope this helps, >> Rohit >> >> On 29-Nov-2012, at 3:54 PM, Prasanna Santhanam <t...@apache.org> wrote: >> >>> On Thu, Nov 29, 2012 at 06:43:29PM -0500, James Martin wrote: >>>> Sorry folks, had to take a long hiatus from my cloudstack work, but >>>> I'm back in the game and determined to get my devcloud work ready for >>>> a patch and submitted. Right now the problem I'm running into is >>>> deploying the build: >>>> >>>> mvn clean install -P developer -D skipTests ; ant build-all rdeploy >>>> rdeploydb -Dport=7222 >>>> >>>> >>>> [sshexec] >>>> [sshexec] >>>> [sshexec] deploydb: >>>> [sshexec] >>>> [sshexec] >>>> [sshexec] deploycddb: >>>> [sshexec] >>>> [sshexec] [exec] failed to init cloudev >>>> dbdeploy-db-clouddev.sh: line 20: clouddev.sql: No such file or >>>> directory >>>> >>> >>> Just wondering which image of devloud you were using. Rohit released >>> a new Debian Wheezy based image recently which works against master. >>> >>> Are you running this for 4.0? >>> >>> >>> -- >>> Prasanna., >>
