<div dir="ltr">Squeak 5.1 was released with the OpenSmalltalkVM <span style="white-space:pre-wrap">201608171728 which is Cog moved to GitHub and which was built on 17th Aug 2016.</span><div><span style="white-space:pre-wrap">You can find the Linux VM at <a href="http://files.squeak.org/base/Squeak-5.1/vm-linux.zip">http://files.squeak.org/base/Squeak-5.1/vm-linux.zip</a></span></div><div><span style="white-space:pre-wrap"><br></span></div><div><span style="white-space:pre-wrap">Fabio</span></div><div><span style="white-space:pre-wrap"><br></span><div class="GmSign">-- <br></div><br><div class="gmail_quote"><div dir="ltr">On Wed, Aug 31, 2016 at 11:11 PM Chris Muller <<a href="mailto:ma.chris.m@gmail.com">ma.chris.m@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">3732 is the VM in Eliot's "latest":<br>
<br>
<a href="http://www.mirandabanda.org/files/Cog/VM/latest/" rel="noreferrer" target="_blank">http://www.mirandabanda.org/files/Cog/VM/latest/</a><br>
<br>
I think 5.1 was released with 3397, a rather old VM.<br>
<br>
On Wed, Aug 31, 2016 at 2:35 PM, Levente Uzonyi <<a href="mailto:leves@caesar.elte.hu" target="_blank">leves@caesar.elte.hu</a>> wrote:<br>
> Hi Chris,<br>
><br>
> I just noticed that the VM is rather old (3732). We should definitely use a<br>
> newer one. E.g. the one 5.1 was relased with.<br>
><br>
> Levente<br>
><br>
><br>
> On Mon, 29 Aug 2016, Chris Muller wrote:<br>
><br>
>> Thanks for clarifying the way forward, Dave.<br>
>><br>
>> The server is now up and running under daemontools as user<br>
>> "squeaksource" on port 9092, and I can view the image in Remmina on<br>
>> port 6192 after creating the SSH tunnel per Levente's advice.<br>
>><br>
>> <a href="http://box4.squeak.org:9092/" rel="noreferrer" target="_blank">http://box4.squeak.org:9092/</a><br>
>><br>
>> The only changes I've made to existing production are to the ownership<br>
>> and permissions of its "ss" directory. There is insufficient disk<br>
>> space to make a full copy of the directory, and not really necessary<br>
>> anyway, so I simply soft-linked to it. The group permission was<br>
>> changed from "davidlewis" to "squeaksource" so the new image can write<br>
>> "data.obj" to that directory. I made a backup of the old "data.obj"<br>
>> file, which is more than a year old.<br>
>><br>
>> Every start of the image initiates SqueakSource's background recovery<br>
>> process, which ensures all .mcz files are in the SSRepository domain<br>
>> object, saved as "data.obj" and now, also indexed in the "ss.magma"<br>
>> database. Since the Magma DB was initially empty, this background<br>
>> recovery process will continue to run probably for a few days until<br>
>> Magma is fully populated.<br>
>><br>
>> I'll be spot monitoring this process until its done -- we're currently<br>
>> at 250M diskspace, 750M of RAM, and 91% CPU.<br>
>><br>
>> - Chris<br>
>><br>
>> On Fri, Aug 26, 2016 at 9:31 PM, David T. Lewis <<a href="mailto:lewis@mail.msen.com" target="_blank">lewis@mail.msen.com</a>><br>
>> wrote:<br>
>>><br>
>>> That sounds right to me also. Assuming that we have enough disk space<br>
>>> (I think there is just barely enough on box4), here are a few other<br>
>>> suggestions:<br>
>>><br>
>>> - Keep the current <a href="http://source.squeak.org" rel="noreferrer" target="_blank">source.squeak.org</a> service running exactly as it is,<br>
>>> with no modifications to the supervise scripts or to anything in the<br>
>>> current directory. This service runs on port 9090, with nginx handling<br>
>>> the connections to the service on 9090.<br>
>>><br>
>>> - Bring up the new <a href="http://source.squeak.org" rel="noreferrer" target="_blank">source.squeak.org</a> on its own new port number, say<br>
>>> 9092 (SqueakMap is using 9091, so don't use that). Set it up completely<br>
>>> in whatever account and home directory we are going to use, and set<br>
>>> up the supervise scripts to start the service. This should be a<br>
>>> production-ready service in every respect, except that it has not<br>
>>> yet been made visible by nginx.<br>
>>><br>
>>> - Run both the old (port 9090) and new (port 9092) services in parallel<br>
>>> for some period of time (maybe a couple of days), until we are<br>
>>> comfortable that it runs reliably, does its image backups on schedule,<br>
>>> and that it will automatically restart following a server reboot.<br>
>>><br>
>>> - While running in parallel mode, we (and everyone on queak-dev)<br>
>>> can help with testing by connecting to the new service on<br>
>>> <a href="http://box4.squeak.org:9092" rel="noreferrer" target="_blank">box4.squeak.org:9092</a> and making sure that the repositories work<br>
>>> properly.<br>
>>><br>
>>> - Depending on how long we run in parallel mode, it may be necessary<br>
>>> to do a final update of "data.obj" before the final switch over to<br>
>>> the new service.<br>
>>><br>
>>> - When all is working as expected, do the nginx update to switch<br>
>>> <a href="http://source.squeak.org" rel="noreferrer" target="_blank">http://source.squeak.org</a> to point to the new service on 9092.<br>
>>><br>
>>> - In the event of problems, the rollback plan is to update nginx<br>
>>> to point back to the original service, which will still be running<br>
>>> on port 9090.<br>
>>><br>
>>> - Wait a few days, then shut down the old service on 9090. Take a<br>
>>> good backup, then remove the old repository.<br>
>>><br>
>>> Dave<br>
>>><br>
>>><br>
>>> On Sat, Aug 27, 2016 at 02:16:06AM +0200, Levente Uzonyi wrote:<br>
>>>><br>
>>>> Hi Chris,<br>
>>>><br>
>>>> I haven't checked the new zip file yet, but I suggest you set up the<br>
>>>> image<br>
>>>> on the server (make sure it has RFB installed). Once it's done, we can<br>
>>>> create the new nginx configuration on a test subdomain, and if it works<br>
>>>> well, we can switch over.<br>
>>>><br>
>>>> Levente<br>
>>>><br>
>>>> On Fri, 26 Aug 2016, Chris Muller wrote:<br>
>>>><br>
>>>>> Hi all, I've committed the code intended to run our <a href="http://source.squeak.org" rel="noreferrer" target="_blank">source.squeak.org</a><br>
>>>>> server to host the repository [<a href="http://source.squeak.org/ss" rel="noreferrer" target="_blank">http://source.squeak.org/ss</a>], and<br>
>>>>> invited the community to use it to set up their own Personal<br>
>>>>> SqueakSource repositories.<br>
>>>>><br>
>>>>> Currently, our production [<a href="http://source.squeak.org" rel="noreferrer" target="_blank">source.squeak.org</a>] repository is hosted by<br>
>>>>> a stripped "Squeak-3.11-8824" image with lots of notes, workspaces and<br>
>>>>> dirty packages, running on the interpreter VM in the chroot<br>
>>>>> environment. It is not an easy process to extract the SSRepository<br>
>>>>> domain object out of that image and into something the new 5.1 image<br>
>>>>> running under Spur. I did accomplish that, and have the "data.obj"<br>
>>>>> file ready, but if someone else joins [<a href="http://source.squeak.org" rel="noreferrer" target="_blank">source.squeak.org</a>] before we<br>
>>>>> can deploy it, they'd have to rejoin afterward. Hence, my desire to<br>
>>>>> get the exported data.obj deployed relatively soonish.<br>
>>>>><br>
>>>>> However, I really don't feel comfortable attempting to do it on my own<br>
>>>>> without at least getting y'all in the loop so that, in case you would<br>
>>>>> arrive to work to find it down the next morning, you'd know why. :-/<br>
>>>>><br>
>>>>> I've created a deployment .zip file and uploaded it to<br>
>>>>> box4.squeak.org:/home/chrismuller/webserver.zip. That zip contains<br>
>>>>> the new 5.1 image ready to be the server running the latest code from<br>
>>>>> the "ss" repository, as well as the converted "data.obj" file (the<br>
>>>>> serialized SSRepository domain object which has all our usernames,<br>
>>>>> etc.). Also included are the scripts whose contents are the commands<br>
>>>>> I would run to do the actual deployment.<br>
>>>>><br>
>>>>> The "squeaksource" user under which the server will run is already<br>
>>>>> created. I guess there are just two issues I'm still not sure about:<br>
>>>>><br>
>>>>> - the nginx configuration changes needed, if any.<br>
>>>>> - the automated emails. The email address is in the SSRepository<br>
>>>>> object, but I'm not sure if any special configurations are needed.<br>
>>>>><br>
>>>>> Any advice or support toward completing this would be greatly<br>
>>>>> appreciated.<br>
>>>>><br>
>>>>> Best,<br>
>>>>> Chris<br>
>>>>><br>
>><br>
><br>
</blockquote></div></div></div>