However downloads, planet and wiki are still slow. Meaning that they are all on the old hardware. There is an issue with load balancing, https negotiation and separate domain names. Sigh. That issue needs to be addressed to get everything on the new hardware. And preferably fast, as Downloads is one of the key parts of the site.

I also have noticed that viewing the pages with https (logged in) is significantly slower than with bare http (not logged in). I think there should be a difference, but not one I can see and feel. Need to look for the reason to that too, might be just my slow laptop.

So the next step is to get downloads (and planet) to the new hardware. Let’s see how that works out. No promises on schedule, but I hope soon.

Other things that are on the map are possibly updating Gforge (the next release would have a git plug-in, but we are running a modified version which makes upgrading more difficult), then the Midgard upgrade (when the next release will be ready and out, so upgrade might be sometime during the winter) and moving more of the services to new hardware.

And for these future tasks I need feedback. What services should be moved first? I.e. which ones are most in need of a boost? Downloads is already first in line.

So the main maemo.org web-server upgrade did not make it in time for the Summit. Tough, I would have liked to have it done by now, but things didn’t go as smoothly as in movies.

The upcoming maintenance break is to do the upgrade. Couldn’t really have it during the summit, as virtually every involved is in Berlin.

Anyway, what I wanted to do is say a couple of words on the hardware and services we run.

Currently the site consists of quite a lot of services. There is Midgard, GForge, SQL servers, LDAP, mail server and a bunch of other stuff running to have the site functional.

All that requires hardware to run. And as the community has grown the requirements for the hardware have grown as well. However all parts of the hardware haven’t grown as fast.

Moving the maemo.org main servers is the first step on the path to upgrading most, if not all, of the hardware. The intent is to make the hardware invisible. That is in a good way, removing the long load times and hickups in the service.

It’s a week and a day since I started as the project manager for maemo.org.

It’s been quite interesting to get into the things that are going on in the community. Because that’s basically what this job is about. I need to get a feel for what kind of things would be considered beneficial by the community.

My tasks for the immediate future are quite centered on the Maemo Summit in Berlin next week. The new servers for maemo.org need to be brought on-line before that. The to-do list for that is luckily getting shorter, but still a couple of things to be done. I really hope that will take care of the performance issues for a while so I can get to my actual job.

Which in the long run is to see that the services available on maemo.org are suitable and good for the community. That’s something I’ll be looking at during the Autumn and Winter. Any ideas and suggestions are welcome.

And this probably is the right place to say a big thank you to the people who have been managing the site tasks on top of their normal workload.

Tero

P.S. As you can see, I am also reviving the maemo team blog. And hoping to get some more people inside Nokia to contribute here too 🙂