If I understand what DabbleDB does, they essentially give each user their own squeak process to run in. When a session is first established, they start up a new image. Upgrading would be a matter of dropping a new image somewhere and as old sessions expire and new ones created, users are migrated over to the new code. With hydraVM, a scheme like that might be doable with just a small bit of session management in the main image.<br>
<br>(with <a href="http://swiki.net">swiki.net</a>, I used to VNC in (I ran squeak headful in a regular VNC session...at the time, the squeak VNC server didn't exist), fix bugs or load code on the fly, but I was always a bit nervous about a slip of the mouse or a mistake taking the whole thing down...I would make changes in a way that they were captured and repeatable (using change sets (this was pre-MC)) and then re-apply the changes to a clean image on disk...I didn't like snapshotting with all the session related state bloating the image)<br>
<br>- Stephen<br><br><div class="gmail_quote">On Wed, Apr 2, 2008 at 9:23 PM, Andreas Raab <<a href="mailto:andreas.raab@gmx.de">andreas.raab@gmx.de</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Excellent links, thanks a lot (and to Ramon for writing the blog). Interestingly, the issue of configuration management was one of the ones that I've been thinking about recently too ;-)<br>
<br>
Cheers,<br>
- Andreas<br>
<br>
Rajeev Lochan wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="Ih2E3d">
Hi,<br>
Check out Ramon's Blog post, which can guide you, though I havent used them.<br>
<br>
<a href="http://onsmalltalk.com/programming/smalltalk/upgrading-a-running-squeak-image/" target="_blank">http://onsmalltalk.com/programming/smalltalk/upgrading-a-running-squeak-image/</a><br>
<br>
<a href="http://onsmalltalk.com/programming/smalltalk/simple-file-based-application-configuration/" target="_blank">http://onsmalltalk.com/programming/smalltalk/simple-file-based-application-configuration/</a><br>
<br>
HTH,<br>
Rajeev<br>
<br></div><div class="Ih2E3d">
On Wed, Apr 2, 2008 at 10:29 PM, Ken Causey <<a href="mailto:ken@kencausey.com" target="_blank">ken@kencausey.com</a> <mailto:<a href="mailto:ken@kencausey.com" target="_blank">ken@kencausey.com</a>>> wrote:<br>
<br>
Well, I can only say that I've updated (without restarting) a handful of<br>
images that were running either Seaside or something else using Kom and<br>
have not had any troubles. In most cases these were images that were<br>
probably not getting but a few hits a minute, but I believe in at least<br>
one case we made changes to Swiki (yes, <a href="http://wiki.squeak.org" target="_blank">wiki.squeak.org</a><br></div>
<<a href="http://wiki.squeak.org" target="_blank">http://wiki.squeak.org</a>>) and had no<div><div></div><div class="Wj3C7c"><br>
trouble. Those were very minor changes though if I remember correctly<br>
(just a method or two).<br>
<br>
Ken<br>
<br>
On Wed, 2008-04-02 at 09:28 -0700, Andreas Raab wrote:<br>
> Hi -<br>
><br>
> [Apologies for the cross-post but there may be answers to this<br>
question<br>
> coming from people who are subscribed to Seaside but not Squeak-dev]<br>
><br>
> What are the best practices for upgrading portions of your running<br>
> server? I'm not talking about replacing the main business logic<br>
of your<br>
> server application but rather relatively small things like an<br>
improved<br>
> log module, or an administrative report function etc. Basically parts<br>
> that you can assume aren't used while you upgrade them.<br>
><br>
> I was quite surprised that I wasn't able to find any<br>
recommendations on<br>
> how to do that. And I can't imagine that this problem hasn't come<br>
up in<br>
> Seaside or other Squeak or Smalltalk server deployments. So what do<br>
> people do in such a situation? Fire up VNC and load the latest MC<br>
> package? Is that feasible when you have hundreds of users<br>
pounding the<br>
> server? Any other (semi- or fully-) automated variants? Alternative<br>
> recommendations?<br>
><br>
> Thanks for any insights you can share.<br>
><br>
> Cheers,<br>
> - Andreas<br>
><br>
><br>
<br>
_______________________________________________<br>
seaside mailing list<br>
<a href="mailto:seaside@lists.squeakfoundation.org" target="_blank">seaside@lists.squeakfoundation.org</a><br></div></div>
<mailto:<a href="mailto:seaside@lists.squeakfoundation.org" target="_blank">seaside@lists.squeakfoundation.org</a>><div class="Ih2E3d"><br>
<a href="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside" target="_blank">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</a><br>
<br>
<br>
<br>
<br>
-- <br>
Rajeev Lochan<br>
<br>
Co-founder, AR-CAD.com<br>
<br>
<a href="http://www.ar-cad.com" target="_blank">http://www.ar-cad.com</a><br>
+91 9243468076 (Bangalore)<br>
080 65355873<br>
</div></blockquote>
<br>
</blockquote></div><br>