One of the things I think is important about Mer is that "code is not enough" so I thought it may be useful/interesting to let people know a little bit about some of the more hidden work that happens to keep Mer running. So take this email more as a blog-post :)
There's a fair bit more to delivering products than the source to run on a device. Crucial to operational success are our various support systems: * Mer CI OBS (frontend, backend, download and workers) * Mer/MeeGo Community OBS (frontend, backend, download and workers) * Bugzilla (2 installations for Nemo and Mer) * IMG server and workers * BOSS server and processes * MDS * Gerrit and gitweb * email and mailing lists * Wiki (external and internal sysadmin one) * Icinga monitoring system * Website Then there are things like DNS, internal and public LDAP, shell systems, dcp auditing, puppet, ntp etc etc. Oh, all this is run on a collection of physical hosts with transparent vpn bridging to permit secure and transparent scaling out. Clearly handling all this is a fair bit of work and I'm very keen on automation, documentation and efficiency. So ... that's what started me off: I setup a couple of new dual-core physical hosts today and went through the deployment process. I found out that OpenSuse 11.4 wasn't in the available list anymore so used 12.1 to see how it went. All went smoothly until it came to puppet. Error 400 on SERVER: No support for http method POST ??? ... well, google tells me : "Ensure that you are not running a v2.7 client against a v2.6 master. We suggest downgrading the client in this case to v2.6 as v2.7 can introduce changes in behaviour that are best dealt with as part of a planned upgrade" *sigh* - here goes with a puppet upgrade. David -- "Don't worry, you'll be fine; I saw it work in a cartoon once..."
