Migrating to Community-driven Infrastructure

please somebody does a major rework of this page, to a new wiki page like "community maemo.org infra - at IPHH" and clean out all the history data that doesn't give any useful info anymore. Also splitting off the autobuilder stuff into a separate page might help --joerg_rw 15:20, 4 June 2013 (UTC)

Started to move stuff



Please use Categories below for any future pages of this topic


--sixwheeledbeast 20:46, 5 June 2013 (UTC)

Suggest maintainers should be removed an Maemo.org_team page should be updated

--sixwheeledbeast 20:50, 5 June 2013 (UTC)


[edit] Introduction

[2013-11-07] migration to our own servers at IPHH accomplished since ~6 months now, below info is for historical documentation.

[up to date as of 2013-02-08]

Albeit Nokia's plans about discontinuation of maemo support been known since spring 2012, Nokia gave "Go" to Nemein (service provider on behalf of Nokia) for the real migration work not earlier than 2 weeks before christmas 2012.

As of January, 18th 2013 the *.maemo.org infrastructure has been consolidated from a 20+ physical servers (aka "irons") to current config and completely migrated to new locations independant of Nokia servers. This task been accomplished by Nemein. Talk.maemo.org forum been integrated with the other infra, many thanks to Nemein for donating the VM for that. Also many thanks to Nemein for this incredible piece of work done during times when others (as well as the guys there) usually are already away for winter holidays.

The current setup (see below) consists of around 10 Virtual Machines hosted by Nemein on their xen-grid. This is an interim solution. Nokia paid Nemein for this consolidation/migration and hosting until end of February.

Handing over control of servers still pending, right now (2013-01-30) it's still Nemein and affiliates to control that infra.

Transfer of control over (*.)maemo.org DNS entries ("the domain") is still being negotiated between Nokia and HiFo, all DNS changes done so far been done by Nokia dnsmaster on Nemein's request

The plans of council and HiFo board so far are: kindly ask Nemein to have *.maemo.org nicely bundled. We hope for this setup to be free of major known bugs (I.E. autobuilder working, repository working albeit maybe slow) when Nemein hands us the package.

[2013-02-08] Negotiations about direct migration to one of our 3 options (see below) are ongoing.

[edit] further plans, state of migration

(obsolete. thus deleted. See wiki history if interested in what happened when)

This page is intended as a central place where status and other operational information can be gathered.

[edit] Plan for migration / Timeline [2013-03-15]

  • Friday, 22.2. (falk)
    • Rack Hardware @ IPHH - Hardware is racked
    • Install base system (CentOS 6.3 with patches from xes)
  • Saturday, 23.2. (xes/falk)
    • Start migrating repository.m.o
    • Start migrating VMs with static data
  • ... (hidden DNS master set up)
    • sync databases, switch DNS entries
    • DNS switched [Nokia] to new IPs on 2013-03-14 1700UTC. Final sync established 1900. since then machines up and running on *new*

VMs we need to migrate:

Name Disk Size Location of act. instance _migrated? _Comments on *new* instance
static 30G nemein synced+up works
wiki 20G nemein synced+up works
repository 900G nemein synced+up We need to check the disk size, this might be too big for current hw, maybe split tablets-dev off.
mail 20G nemein synced+up also has lists
scratchbox 100G iphh setup! will be setup new
vcs 50G nemein synced+up has NFS mounts from garage and repository (copying)
garage 100G nemein synced+up has NFS mounts from stage and vcs (copied, seems to work)
db 100G nemein synced+up works, needs tuning
builder 50G nemein copied+up still needs fixing several aspects
talk  20G nemein  synced+up  up since 2013-03-13, via HTTP-forward
dns  ?? ipph setup! dns records/serial incomplete, bind inactive

[edit] State of final migration

all VMs got migrated to IPHH server, DNS still owned and managed by Nokia [2013-05-29]

[edit] Tips & Tricks for migration


Create an image on vmhost

fallocate -l 200g image.img

or, in case fallocate is unavailable

dd if=/dev/zero of=image.img bs=1 count=1 seek=200G

Attach as loop-device

losetup -f image.img
(find the loop-device and create a filesystem on it)

Copy stuff

tar --create -p -j --one-file-system . | pv -br | ssh root@host 'cd /mountpoint  ; tar xpj '
cd / ; rsync -arvSxz . root@host:/mount/point

[edit] Stuff to do [2013-03-15]

  • Implement a proper service monitoring for all machines and applications - nagios pending, http://monitor.maemo.org/ganglia/
  • Setup a common policy for root/user accounts and sudo permissions
  • Change root-passwords - done
  • Make SSH root-login key-only - done?
  • Find out, what to sync for final migration - done
  • Configure internal DNS server in /etc/resolv.conf
  • Coordinate DNS setup with Nokia - partially done
  • Consolidate Databases - WIP
  • Add disks to system - done, 4TB on blade-a
  • Setup bugtracking system for infrastructure - done: roundup?
  • fix NFS mounts - WIP
  • update VMs to 3.2.0-38

[edit] Problems we walked into

[edit] Machines throwing their network away

Apparently, XEN has issues if a vm sends too many/too large network packets.

http://lists.xen.org/archives/html/xen-devel/2013-01/msg00198.html has an interesting read about that problem.


 xenbr1: port 8(vif51.0) entered forwarding state
 vif vif-51-0 vif51.0: Too many frags
 vif vif-51-0 vif51.0: fatal error; disabling device
 xenbr1: port 8(vif51.0) entered disabled state

in dmesg

Temporary fix: Disable all offloading on eth0

 for i in rx tx sg tso gso gro lro; do
         ethtool -K eth0 $i off

Source of this problem:


We fixed that problem on our machines by ensuring dom0 and domU use same MAX_SKB_FRAGS

[edit] Inventory

As a first step we gathered information about the former infrastructure at *.maemo.org. This "inventory" provided an overview about all components of the infrastructure as well as information that would later on aid during the migration.

The following topics were considered important for the migration:

  • Legal Issues (Names, Trademarks, Domain Names, etc.)
  • Infrastructure (Web Site, Forum, Wiki, Autobuilder, Mailinglists, Garage, etc.)

[edit] Legal Issues

[edit] What is the state about the name "Maemo"?

"... Maemo is currently a registered trademark of Nokia and the domain name is owned by Nokia.

[edit] Who owns "maemo.org"?

Negotiations about domain ownership still ongoing between Hildon Foundation board and Nokia (2013-01-20), if community can't get control over the DNS, we might revert to maemocommunity.org.

Domain ID:D105692361-LROR
Domain Name:MAEMO.ORG
Created On:07-Feb-2005 16:26:32 UTC
Last Updated On:07-Jan-2013 10:25:55 UTC
Expiration Date:07-Feb-2014 16:26:32 UTC
Sponsoring Registrar:MarkMonitor Inc. (R37-LROR)
Registrant ID:mmr-31461
Registrant Name:Nokia Corporation
Registrant Organization:Nokia Corporation
Registrant Street1:P.O.Box 226
Registrant Street2:Nokia Group
Registrant Postal Code:00045
Registrant Country:FI
Registrant Phone:+358.718008000
Registrant FAX:+358.718034496
Registrant Email:dnsauthority@nokia.com

We're planning to ask Nokia to allow a hidden primary [1] for maemo.org, that we will host on a persistent VM (dns) sponsored by Nemein (thanks Eero! :-D ). The purpose is to allow swift changes of IPs under maemo.org without bothering Nokia's DNSmaster, as long as the domain still belongs to Nokia. Once the domain will get transferred to HiFo, this will become less useful but also not exactly any problem. in 6 months or so we can consider tearing down the hidden primary and manage our domain directly.

[edit] What is needed for the community to run maemo.org?

TMO forums donated to Hildon Foundation: http://maemo.org/community/board/tmo_forums_donated_to_hildon_foundation/

[edit] What are the costs?

Nokia paid for hosting until end of February. Current (2013-01-30) interim config (VM on Nemein's xen-grid) will cost 1300EUR/month for the VM, plus 2200EUR/month for the maintenance. For the colocation rackspace, traffic, energy etc of the iron(s) Nokia donates to community there will be another 500+EUR/month. All excl VAT.

At end of February we hope to drop the xen-grid VM since they shall run in a virtualization on our iron by then.

If you're willing to donate, please visit http://hildonfoundation.org/support/

[edit] What about the personal information of the users?

Please refer to the privacy policy posted on the website. If you want info about what's the data stored about you inside *maemo.org, or want this data / your account getting permanently deleted, please contact council@maemo.org

[edit] Operational Platform

[2013-03-20] All of maemo.org is running on our supermicro server colocated at IPHH

List of hardware Nokia will donate to HiFo, according to Nemein's plans. [2013-02-08]

ID Hostname Mgmt IP Address OOB Mgmt IP Address Type (Virtual / Baremetal) System Admin HW Vendor HW Model Form Factor CPU Memory Disk Acquisition Date Warranty Services Comment
01 blade-a.maemo.org Baremetal Falk(warfare) Supermicro http://www.supermicro.nl/products/system/2u/2027/SYS-2027TR-HTRF.cfm?parts=SHOW 2U 19" Rackmount Intel® Xeon® processor E5-2620 32GB (raid1:2*)1TB, 2*2TB=4TB aux. 3 years Falk (for HH CoLo) only 2 of the 4 blades populated
02 blade-b.maemo.org Baremetal Intel® Xeon® processor E5-2620 32GB (raid1:2*)1TB


[edit] OS and virtulization on community iron (planning, discussion)

Please don't forget to tag your contributions with your nick!

[edit] Server OS

[edit] alternative A


[edit] alternative B
[edit] alternative C

[edit] Virtualization

[edit] alternative A

XEN (with OS blabla of above)

[edit] alternative B


[edit] alternative C

[edit] Services

The following table is intended to give a concise and easily perceivable overview of the *.maemo.org services. Please use the next sub-section for providing more detailed information.

Resource URL (If Applicable) Migration Status (DONE/WIP/NST) Service Maintainer System Admin Software Name Software Version Software License Known Issues Last status update
Maemo Main Web Site http://www.maemo.org 1 BUGS  ? Nemein orphaned links/404s: http://maemo.org/community/council/system_operator_needed/; Login doesn't work 2013-01-25
Maemo Forums http://talk.maemo.org 1 DONE chemist, Reggie Falk, chemist vBulletin Unlimited duration, no upgrades included, acquired on 2012-20-12 Captcha image issues 2013-02-10
Maemo Wiki http://wiki.maemo.org 1 BUGS  ? Nemein (Watch) Email not working; random connection timeouts 2013-01-25
Repositories http://repository.maemo.org 1 BUGS X-Fade, Merlin1981 Nemein former akamai serverfarm, now points to stage.m.o VM master of farm. Hashsum errors legacy 2013-02-20
Blog aggregator http://planet.maemo.org 1 DONE  ? Nemein login flawed? 2013-02-10
Maemo Garage https://garage.maemo.org/ 1 DONE  ?, Woody Nemein 2013-01-25
Maemo Autobuilder 1 NST X-Fade Nemein OFFLINE, x-fade working on it 2013-02-20
Maemo Nameservers 1 WIP Merlin, Falk Nokia Still using Nokia Nameservers; following hidden primary plan til domain transfer to HiFo established 2013-01-25
Drop http://drop.maemo.org 1 WIP X-Fade Nemein 2013-02-10
VCS http://vcs.maemo.org 1 WIP Nemein 2013-02-10
Listserv https://lists.maemo.org 1 BUGS Nemein occasional lockups resp interface down 2013-02-20
Static http://static.maemo.org 1 WIP Nemein temporary fix via NAT port81 redir, instable? 2013-02-20
Stage http://stage.maemo.org obsolete X-Fade Nemein VM got assigned to repository.m.o 2013-02-20
Bugs http://bugs.maemo.org 1 DONE Andre Nemein - 2013-01-25
Scratchbox http://scratchbox.org/ 1 WIP thedead1440 Nemein, thedead1440, Logica Finland Oy, migration pending 2013-02-20
Voting Infrastructure  ? 1 WIP woody14619  ?  ? 2013-02-20

[edit] More Detailed Information

this is based on what we got/found on Nemein temporary infra - it's NOT related/applicable to new IPHH infra. For IPHH new infra IPs Maemo.org_Infrastructure In this sub section more detailed information about the entries in the table can be placed. The intent is to keep the table concise while still being able to have all relevant information at hand.

List of VMs and their associated IPs:

IP adresses      test.maemo.org
# www.maemo.org      maemo.org      www.maemo.org      planet.maemo.org      static.maemo.org      drop.maemo.org      garage.maemo.org      lists.maemo.org      wiki.maemo.org      bugs.maemo.org
#      repository.maemo.org  scrubbed      stage.maemo.org  repository.maemo.org (reassigned)      vcs.maemo.org

List of internal IP/VM  MaemoTemplate   maemo static maintenance   wiki bugs   stage repository   mail smtp lists   scratchbox   dns
#   repository   vcs drop  garage  db backup  builder fw

Cpu Cores, RAM (in MB), storage (DISK, in GB), of the VMs

Current VMs actually in use (some more were reserved originally since it
was not certain what services could be merged)

Name    C   RAM     DISK
MaemoFW 1   1024    10
Builder 1   4096    150
garage  2   8192    100
test    2   2048    30
wikib   2   2048    50
www     2   6144    70
vcs     2   8192    200
db      2   8192    260
mail    2   2048    30
stage   2   2048    870
talk    2   4096    15
        20  48128   1785

sb      2   2048    30
dns     2   2048    30
        25  52224   1845

[edit] Forum (talk.maemo.org)

Unlike the other services, talk.maemo.org is not behind the endian firewall. Maintenence access is not via test jumpserver.

Software: vBulletin
licence: Unlimited duration, no upgrades included, acquired on 2012-20-12

[edit] Scratchbox

Scratchbox is also sponsored by Nokia. (Please verify?) Scratchbox is required for running the Fremantle and Harmattan SDK.

Currently there's a VM on Nemein's xen-grid named "scratchbox", but state of the case is unclear.

[edit] Tracker for Sysops and Maintainers

This tracker is meant for maemo staff and affiliated only

web frontend: roundup.fourecks.de/maemo/
mail access (read docs!): maemo-issue AT fourecks.de

[edit] Service Maintainers (please update/augment/fix)

(please don't usually pester maintainers directly! First try to contact council@maemo.org, we'll forward)

These are the Service Maintainers (in spe), for services like forum (tmo), wiki, bugs, etc. They are (generally) not sysops of the machines their service is running on.

From Nick Full Name E-Mail Services Maintained Status Comments
Nemein mashiara Rambo Eero af Heurlin eero.afheurlin at <to be disclosed by owner> (sysop) [leaving?]
Nemein x-fade Niels Breet Niels<at>maemo.org (mail, IRC, builder, ???...) [leaving?]
Nemein ferenc Ferenc Szekely ferenc<at>maemo.org (mail, sysop, ???...) [leaving?]
maemo warfare Falk Stern falk<at>fourecks.de (maemo master sysop)
maemo chemist Ruediger Schiller webmaster<at>talk.m.o Talk
maemo merlin1991 Christian Ratzenhofer <at> Repos [preliminary accepted]
 ??? andre_ Andre Klapper  ???<at>??? Bugs [???]
 ??? (wiki)

[edit] Unsorted Hints

[edit] ssh access

All legacy accounts got ported to new infra.

Access to any VM is via plain direct ssh:

ssh <user>@<VM>.maemo.org

[edit] backup

we're doing backups to the 4TB auxiliary storage on blade-a, using backupPC:

ssh -L8088:localhost:80 blade-a
konqueror http://localhost:8088

backup-master is Falk

talk VM sysop (chem|st) has access to it and control over own backups, via ssh confic on blade-a:

command="sleep 1d",permitopen=""  <ssh-pubkey>

[edit] Steering

council is in charge of any steering.

Joerg Reisenweber got appointed for "maemo.org infra administration coordinator" and thus is the single point of coordination for any detail questions.

If you got any questions, suggestions, critics, whatever, please contact Joerg (DocScrutinizer) or any other of council members via IRC. or send a mail to council AT maemo.org. We're just community's proxies acting in best intention to do what's probably community's best interest. If you don't agree with what we do or have suggestions how we could do better, please holler. Best place: Friday 1800UTC IRC:(freenode.net)#maemo-meeting

[edit] More