Hi Suriya, Great to hear you have had some success, and thanks for the feedback :)
Some comments inline ... On Tue, May 13, 2014 at 10:32 AM, Sathyasuriya Priya <[email protected]> wrote: > hi Chris, > > I am able to setup openstack+stratos using your scripts. > I tried it on my new linux machine with following changes. > > Since "4.0.0-incubating" build is having problem, I commented 'git checkout > ${STRATOS_SRC_VERSION}' line in checkout() in stratos/stratos.sh There is a file stratos_version.conf file that you can use to set the stratos version: $ cat stratos_version.conf # Example 'stratos_version.conf' file # the stratos version to check out and build # i.e. git checkout $STRATOS_SRC_VERSION export STRATOS_SRC_VERSION="4.0.0-incubating-rc3" > In stratos/stratos.sh, replaced /etc/puppet/manifests/nodes.pp with > /etc/puppet/manifests/nodejs.pp. I don't see the old file. So I replaced it > to this. I'm not sure why you needed to do this. > In tests/example_cartridge.json, removed the line '"deployment": {},' and > added '"maxInstanceLimit":"4",' under "iaasProvider". Looks like this has > changed in recently. good stuff. > tests/test_stratos.sh couldn't find any jar file in > /home/vagrant/stratos/apache-stratos-cli-4.0.0-SNAPSHOT/ I see the jar file > in > /home/vagrant/.m2/repository/org/apache/stratos/org.apache.stratos.cli/4.0.0-SNAPSHOT/org.apache.stratos.cli-4.0.0-SNAPSHOT.jar > and copied it manually. May be this changed recently as well. > I think this error was due to the "-bin" suffix that was getting added by mistake in the rc3 build. I have changed my scripts to be more tolerant of file name changes. > > I tried your .bat scripts in windows. But it was asking/waiting for user > inputs for a number of cases. Couldn't test it fully. > I'll try and fix them up. > > Thanks > Suriya > > > On Sun, May 4, 2014 at 11:13 PM, Sathyasuriya Priya <[email protected]> > wrote: >> >> Thanks Chris. will try. >> >> >> On Sun, May 4, 2014 at 11:05 PM, chris snow <[email protected]> wrote: >>> >>> Hi Sathyasuriya, thanks for trying the scripts. >>> >>> I've added some responses inline... >>> >>> On Mon, May 5, 2014 at 5:07 AM, Sathyasuriya Priya >>> <[email protected]> wrote: >>> > hi Chris, >>> > >>> > Just some clarification on how you run your setup. >>> > >>> > You create a VM with 5gb ram and follow the instructions (install >>> > vagrant+virtualbox, clone your repo, run-script) inside it. >>> >>> You don't create a VM. The 'vagrant up' command creates the VM for >>> you. Vagrant is basically an automation layer on top of Virtualbox. >>> >>> > Or your base OS in the laptop is linux and you follow the instructions >>> > directly. >>> >>> The base OS can be Windows, Mac OSX, Linux - basically any OS >>> supported by Vagrant and Virtualbox. >>> >>> > How much time does it take to finish all the steps. >>> >>> It will take quite a few hours depending on your connection speed and >>> CPU. >>> >>> > >>> > Some info on what I am trying: >>> > >>> > In my old laptop with linux, I try the direct method. But virtualbox is >>> > not >>> > able to run 64 bit VMs. >>> >>> From what I can tell, docker will need a 64 bit VM. My scripts >>> therefore also require a 64 bit VM. >>> >>> > I tried creating a server machine in Google Compute Engine(GCE), >>> > followed >>> > direct method. Again virtualbox is not able to run 64bit VMs. >>> >>> The host that runs virtualbox should not be a virtual machine. >>> >>> > >>> > I added 32bit VM [1] in Vagrantfile and hit couple of issues. >>> > >>> > I could use ~3584 for VM memory. Increasing beyond this, VM doesn't >>> > start. >>> > In stratos.sh fixed a typo in fix_git_tls_bug() "sudo apg-et update" >>> > In fix_git_tls_bug() changed git version to 1.8.* since my ubuntu13.10 >>> > version had that. >>> >>> Please try on a 64 bit machine. >>> >>> > Now the stratos.sh is taking lot of time(may be 3-4 hours) and still >>> > executing. I see logs getting appended to stratos.log. So it's not >>> > stuck. >>> > Can I install vagrant+virtualbox in my newer windows laptop and follow >>> > the >>> > instructions directly in windows ? >>> >>> Yes. Please try on a 64 bit host!! I've added some .bat scripts to >>> the github project (though I haven't tested them yet). >>> >>> > >>> > [1] >>> > >>> > http://opscode-vm-bento.s3.amazonaws.com/vagrant/virtualbox/opscode_ubuntu-13.10-i386_chef-provisionerless.box >>> > >>> > >>> > >>> > >>> > On Wed, Apr 30, 2014 at 1:12 PM, Nirmal Fernando >>> > <[email protected]> >>> > wrote: >>> >> >>> >> That's great! >>> >> >>> >> >>> >> On Thu, May 1, 2014 at 12:52 AM, chris snow <[email protected]> >>> >> wrote: >>> >>> >>> >>> Hi Nirmal, the whole environment runs in a single virtualbox guest >>> >>> that >>> >>> has 5gb memory, though it could probably run in 4gb. I'll check my >>> >>> CPU spec >>> >>> when I'm back at laptop. The laptop isn't anything special though. >>> >>> >>> >>> On 30 Apr 2014 19:49, "Nirmal Fernando" <[email protected]> >>> >>> wrote: >>> >>>> >>> >>>> Absolutely Chris.. What's the hardware spec one needs in order to >>> >>>> set >>> >>>> this up? >>> >>>> >>> >>>> >>> >>>> On Thu, May 1, 2014 at 12:01 AM, chris snow <[email protected]> >>> >>>> wrote: >>> >>>>> >>> >>>>> I've started adding docker support to the vagrant environment: >>> >>>>> >>> >>>>> https://github.com/snowch/stratos-vagrant-box - openstack-docker >>> >>>>> branch >>> >>>>> >>> >>>>> One script now automates this lifecyle >>> >>>>> >>> >>>>> - sets up ubuntu >>> >>>>> - sets up puppet >>> >>>>> - checks out, compiles and sets up stratos >>> >>>>> - sets up openstack with docker and creates a tomcat instance >>> >>>>> - provisions stratos with policies >>> >>>>> - subscribes and syncs to a cartridge >>> >>>>> - tests that stratos has spawned an instance >>> >>>>> >>> >>>>> Puppet agent isn't working properly in the instance yet, and some >>> >>>>> of >>> >>>>> my scripts are still quite hacky :) >>> >>>>> >>> >>>>> However, while working on this environment, it has occurred to me >>> >>>>> that >>> >>>>> we could use this for release testing? >>> >>>>> >>> >>>>> Cheers, >>> >>>>> >>> >>>>> Chris >>> >>>> >>> >>>> >>> >>>> >>> >>>> >>> >>>> -- >>> >>>> Best Regards, >>> >>>> Nirmal >>> >>>> >>> >>>> Nirmal Fernando. >>> >>>> PPMC Member & Committer of Apache Stratos, >>> >>>> Senior Software Engineer, WSO2 Inc. >>> >>>> >>> >>>> Blog: http://nirmalfdo.blogspot.com/ >>> >> >>> >> >>> >> >>> >> >>> >> -- >>> >> Best Regards, >>> >> Nirmal >>> >> >>> >> Nirmal Fernando. >>> >> PPMC Member & Committer of Apache Stratos, >>> >> Senior Software Engineer, WSO2 Inc. >>> >> >>> >> Blog: http://nirmalfdo.blogspot.com/ >>> > >>> > >>> >>> >>> >>> -- >>> Check out my professional profile and connect with me on LinkedIn. >>> http://lnkd.in/cw5k69 >> >> > -- Check out my professional profile and connect with me on LinkedIn. http://lnkd.in/cw5k69
