[Glass] Utility for creating / starting / stopping stones?

[Norbert Hartl]

Am 08.01.2014 um 21:36 schrieb Mariano Martinez Peck <marianopeck at gmail.com>:

> Hi guys, 
> 
> I was happily searching into the installGemstone.sh to see how the seaside stone was being generated...but then I realized that the zip of GemStone already comes with it :(
> It is a pity because it would be really really cool to have a script to autogenerate that with some arguments passed around. 
> 
> I noticed Norbert Halt already provided something: https://github.com/noha/stone-creator
> I was trying it but it does not work out of the box in OSX. I will try it in my server later. Also, it was done for GemStone 2.4.4.1 so I wonder if it still works for latest release. Of course that if I make progress with this script I will share with you my changes. 
> 
The scripts are mostly independent of the gemstone version. I use them with 3.0.1. It might be there are some issues but I would expect few. I didn’t check on OS X because I don’t use it there. If you find anything I would be happy to receive pull requests.

> Anyway...I wonder if anybody else has any other type of script/utility for this. Since this script is 3 years old maybe someone came with something more over the years. 

Gemstone/GLASS does not change that much on the outside over the years. So my 3 year old updates do still fit :)

And I’m happy you brought this up. To be honest I don’t know if anyone is using my stuff. I never got any email about that. So the scripts are pretty tight to my needs.

I would like if a few people that are interested could talk about the wishes and improvements in that area. My view on the management is this:

The installation of GemStone is downloading a zip file, extract it and you’re done. That is nice but for me as a unix admin soul I have problems with that. I don’t find it easy to find things in the huge bunch of files and I’m reluctant to change things inside the installation directory because I think it is not clean and making failures on upgrading or cloning the installation.

That was the reason for stone-creator. It prepares a small directory skeleton for a stone to live within. It provides an „env“ script that initializes the necessary environment and init scripts that you can use to make the stone start and stop automatically on operating system start and stop. The directory skeleton is also the place to put your .topazini file so you can do „. ./env && topaz -l“ followed by „login“ to log into the stone the fastest possible way. I have several other scripts for starting web gems, doing garbage collection and such but they are not in the repository because they are not generic enough at this time. 

In gsbuilder [1] I use the scripts for jenkins builds. For every build in jenkins it spawns a new installation of GemStone using the stone-creator and loads code, runs tests,…

Finally I have the virtual gemstone project [2] that produces a virtualbox image containing linux, a GemStone installation and everything else that is needed. The installation part inside that project is done with chef [3]. The GemStone scripts in there should also be useful when used standalone. The scripts installs GemStone, use stone-creator to spawn an instance and ...

There is some overlap in all these projects and it might be a good idea to join forces in order to make something more consistent. 

@all: How do install GemStone and how do you integrate it in your environment? I mean what is your process in achieving something like stone-creator does or what are your different requirements? Does anyone see some sense in creating a little suite together where we can put in the stuff that seems to be useful for a broader use?

Norbert


[1] https://github.com/noha/gsbuilder 
[2] https://github.com/noha/virtual-gemstone
[3] http://www.getchef.com/chef/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/private/glass/attachments/20140109/fc0534d5/attachment.html>