Summer'12 Device Program/Qt 5 Mobile Projects

2012-05-30T05:45:04Z

194.237.7.146: /* Submissions */

We are looking for brave & experienced developers willing to port or develop apps running on top of Qt 5 before its finally release. Currently [http://qt-project.org/wiki/Qt-5-Alpha Qt 5 alpha] is released, the beta version is expected during June and the final in August/September.

The main motivations for this activity are mixture of:
* Helping testing Qt 5 itself and providing feedback while it's alpha/beta.
* Helping testing the [http://qt-project.org/wiki/Qt-5-on-Nokia-N9 Qt 5 libraries for the Nokia N9].
* Getting stories of real apps ported from Qt 4 to Qt 5. Trivial? Horrible? What are the pain points? And what about Qt Creator and the documentation available?
* Getting developers to play with the new toys: Qt Quick 2, textures, transitions, graphics / video effects, raw OpenGL ES stuff, post-Mobility APIs, the new Qt WebKit, JSON DB, ongoing R&D on PhoneGap own JQuery based experiments...

This is the same motivation we have for the [http://qt-project.org/wiki/Category:QtonPi QtonPi] program, but for mobile development the N9 provides a touch display and many more sensors and hardware features that bare bones boards are missing.

== How to apply ==

Developers with a good Qt development track must apply to that thread pointing to any of these sources:
* Your Qt 4 applications, all the better if they are ready for mobile e.g. with QML UI.
* Your maemo.org profile, Qt DevNet profile, Ohloh profile or anything showing who are you and what have you done in terms of development and community involvement.

Questions and feedback about the submissions are welcome in [http://talk.maemo.org/showthread.php?t=84591 this forum thread].

== Submissions ==

Add yourself at the end of the queue and follow this template:

# '''[http://yourURL Project name]''', by [http://yourURL Name Surname] (nick) - Short description + other related links.
# '''[http://www.cmake.org CMake (cross compiling with Qt 5)]''' by [http://steveire.wordpress.com Stephen Kelly] (steveire) - Qt maintainer, KDE developer and Qt based library developer.
# '''[http://seguridad.cenditel.gob.ve/firmaxml FirmaXML (QML desktop app for BDOC digital signatures using cryptographic hardware)]''' by [https://qt-project.org/member/15801 Antonio Araujo Brett] (antonioaraujob) - Qt and information security developer with free and open source tools. Qt Ambassador.
# '''[http://store.ovi.com.cn/content/262170 MagicTag (Anylize song wave and tag it with the right tag)]''', by [https://qt-project.org/member/2885 Tong Zhang] (lovewilliam) - Experienced at qt development and embedded system. Had been contributed a lot of patches to the community. Qt Ambassador.
# '''[http://qt-apps.org/usermanager/search.php?username=embitel&action=contents Some free apps on Qt-apps]''', by [https://qt-project.org/member/4741 Manoj Agrawal] (manoj) - Nokia Certified Qt Specialist, Qt Ambassador and QtOnPi member. Created many complex GUI applications and Qt widgets on desktop and embedded systems. Also created a App Store kind of trial application for one client who proposed it to Nokia.
# '''[http://store.ovi.com/content/167633 fMobi (Qt/QML app for Facebook)]''', by [http://talk.maemo.org/member.php?u=47953 Juuso Kosonen] - [https://qt-project.org/member/4632 Qt Profile] (jkosonen) - Experienced at qt/qml development to mobile. I have plenty of apps already available from [http://store.ovi.com/publisher/JiiKoo Nokia Store]. Qt Ambassador.
# '''[https://projects.developer.nokia.com/gNewsReader gNewsReader]''', by [http://twitter.com/yogeshwarp Yogeshwar P] (yogeshwarp) - gNewsReader is fully featured Google reader client with easy and fast UI written in QML and utilizing QT-Components. also supports sharing links to Pocket/Instapaer/Facebook and Twitter. Related links [http://store.ovi.com/content/185552], [http://n9-apps.com/gnewsreader]. plan to port this to Qt 5
# '''[http://www.digitalfanatics.org/projects/qt_tutorial/ Tutorials and Docs]''', by [http://thelins.se/johan/blog Johan Thelin] (e8johan) - Qt5 and QML needs to be documented for it to gain a larger audience. I'm willing to do this.

OpenSuse Build Service/Installation

2010-07-07T12:22:39Z

194.237.7.146: /* Networking Overview */

= Maemo OBS Cluster Installation Notes =

== Introduction ==
Maemo OBS Clusters are divided into 3 instances:
* '''Frontend''' – Containing Webclient, OBS API, Mysql server
* '''Backend/Repository Server''' – Where OBS-Server, dispatcher, scheduler and repository server are installed
* '''Workers''' – Installation of obs-worker package

This Installation Notes covers OBS installation and setup for '''version 1.7'''. You can always refer to latest documentation also available on-line: http://gitorious.org/opensuse/build-service/blobs/raw/master/dist/README.SETUP

== Networking Overview ==

The Front End (fe) machine provides two major services:
* the webui on build.obs and
* the API on apo.obs;
It is also a useful holding point for the download service on download.obs

The Back End (be) machine provides the backend services including the schedulers, source server and repo server. The repo server (used by the workers to get required rpms) also doubles as the download server via a reverse-proxy on the fe.

<source lang="bash">
10.1.1.1 host.obs.maemo.org
10.1.1.10 fe.obs.maemo.org build.obs.maemo.org api.obs.maemo.org download.obs.maemo.org
10.1.1.11 be.obs.maemo.org src.obs.maemo.org repo.obs.maemo.org
10.1.1.51 w1.obs.maemo.org
10.1.1.52 w2.obs.maemo.org
10.1.1.53 w3.obs.maemo.org
10.1.1.54 w4.obs.maemo.org
10.1.1.55 w5.obs.maemo.org
10.1.1.56 w6.obs.maemo.org
10.1.1.57 w7.obs.maemo.org
10.1.1.58 w8.obs.maemo.org
10.1.1.59 w9.obs.maemo.org
10.1.1.60 w10.obs.maemo.org
10.1.1.61 w11.obs.maemo.org
10.1.1.62 w12.obs.maemo.org
</source>

<hr>

== Creating Xen VMs ==

Based on http://en.opensuse.org/Build_Service/KIWI/Cookbook
<source lang='bash'>
zypper ar http://download.opensuse.org/repositories/Virtualization:/Appliances/openSUSE_11.2/ Virtualization:Appliances
zypper refresh
zypper in kiwi kiwi-templates kiwi-desc-xenboot squashfs
</source>

Create some xen volumes
<source lang='bash'>
lvcreate -L 10G VG_data -n fe_root
lvcreate -L 2G VG_data -n fe_swap
mkswap /dev/VG_data/fe_swap

lvcreate -L 10G VG_data -n be_root
lvcreate -L 2G VG_data -n be_swap
mkswap /dev/VG_data/be_swap

lvcreate -L 10G VG_data -n w1_root
lvcreate -L 2G VG_data -n w1_swap
mkswap /dev/VG_data/w1_swap
</source>

Prepare an opensuse minimal image:
<source lang='bash'>
ROOTFS=/data/11.2min/image-root
mkdir /data/11.2min
kiwi --prepare suse-11.2-JeOS --root $ROOTFS --add-profile xenFlavour --add-package less --add-package iputils
</source>

Update the config & modules:
<source lang='bash'>
ROOTFS=/data/11.2min/image-root
cp -a /lib/modules/2.6.31.12-0.2-xen $ROOTFS/lib/modules/

echo default 10.1.1.1 > $ROOTFS/etc/sysconfig/network/routes
echo NETCONFIG_DNS_POLICY=\"\" >> $ROOTFS/etc/sysconfig/network/config
echo nameserver 8.8.8.8 > $ROOTFS/etc/resolv.conf
echo default 10.1.1.1 > $ROOTFS/etc/sysconfig/network/routes
cat << EOF >$ROOTFS/etc/sysconfig/network/ifcfg-eth0
BOOTPROTO='static'
BROADCAST=''
STARTMODE='onboot'
EOF
echo /dev/xvda1 swap swap defaults 0 0 >> $ROOTFS/etc/fstab
</source>

Copy to each of the VM root disks
<source lang='bash'>
mkfs -text3 /dev/VG_data/fe_root
mount /dev/VG_data/fe_root /mnt/lvm
rsync -HAXa /data/11.2min/image-root/ /mnt/lvm/
echo fe.obs.maemo.org > /mnt/lvm/etc/HOSTNAME
echo "IPADDR='10.1.1.10/24'" >> /mnt/lvm/etc/sysconfig/network/ifcfg-eth0
umount /mnt/lvm

mkfs -text3 /dev/VG_data/be_root
mount /dev/VG_data/be_root /mnt/lvm
rsync -HAXa /data/11.2min/image-root/ /mnt/lvm/
echo be.obs.maemo.org > /mnt/lvm/etc/HOSTNAME
echo "IPADDR='10.1.1.11/24'" >> /mnt/lvm/etc/sysconfig/network/ifcfg-eth0
umount /mnt/lvm

mkfs -text3 /dev/VG_data/w1_root
mount /dev/VG_data/w1_root /mnt/lvm
rsync -HAXa /data/11.2min/image-root/ /mnt/lvm/
echo w1.obs.maemo.org > /mnt/lvm/etc/HOSTNAME
echo "IPADDR='10.1.1.51/24'" >> /mnt/lvm/etc/sysconfig/network/ifcfg-eth0
umount /mnt/lvm
</source>

Configure some Xen VM configs
<source lang='bash'>
name='fe'
disk=['phy:/dev/VG_data/fe_root,xvda2,w', 'phy:/dev/VG_data/fe_swap,xvda1,w']
vif=['mac=0D:16:3E:40:B5:FE']
memory='1024'

root='/dev/xvda2 ro'
kernel='/boot/vmlinuz-2.6.31.12-0.2-xen'
ramdisk='/boot/initrd-2.6.31.12-0.2-xen'
extra='clocksource=jiffies console=hvc0 xencons=tty'

on_poweroff='destroy'
on_reboot='restart'
on_crash='restart'
</source>

And start them:
<source lang='bash'>
xm create /etc/xen/fe.cfg
xm create /etc/xen/be.cfg
xm create /etc/xen/w1.cfg
</source>

== Interim config ==
<source lang='bash'>
zypper in wget less iputils terminfo emacs
</source>

== Installing the Backend ==

On this host we need also to setup openSuse Tools repository:
<source lang='bash'>
cd /etc/zypp/repos.d/;
wget http://download.opensuse.org/repositories/openSUSE:/Tools/openSUSE_11.2/openSUSE:Tools.repo
zypper ref
# Accept the trust key
</source>

Install:
<source lang='bash'>
zypper in obs-server obs-signer obs-utils createrepo dpkg nfs-client
# obs-server brings these other packages as dependency. This is just for you to notice which packages are needed for Backend installation
# createrepo & dpkg are only reccomends
# nfs client is needed as we use an nfs share for host/be interchange
</source>
Configure Scheduler architectures
<source lang='bash'>
vi /etc/sysconfig/obs-server
OBS_SCHEDULER_ARCHITECTURES="i586 armv5el armv7el“
</source>

/usr/lib/obs/server/BSConfig.pm needs to point to correct server names corresponding to source server, where workers are going to download the source, and the repository server, where RPM repos are going to be shered to users.
<source lang='bash'>
vi /usr/lib/obs/server/BSConfig.pm
#add
$hostname="be.obs.maemo.org";

our $srcserver = "http://src.obs.maemo.org:5352";
our $reposerver = "http://repo.obs.maemo.org:5252";
our $repodownload = "http://$hostname/repositories";
</source>

Configure services as deamons
<source lang='bash'>
chkconfig --add obsrepserver obssrcserver obsscheduler obsdispatcher obspublisher obswarden obssigner

#Check them
chkconfig -l obsrepserver obssrcserver obsscheduler obsdispatcher obspublisher
</source>
Start Services
<source lang='bash'>
rcobsrepserver start
rcobssrcserver start
rcobsscheduler start
rcobsdispatcher start
rcobspublisher start
</source>
For version 1.7 there are a new services. You can start them as well:
* '''obswarden'''
It checks if build hosts are dieing and cleans up hanging builds
* '''obssigner'''
It is used to sign packages via the obs-sign daemon. You need to configure
it in BSConfig.pm before you can use it.
* '''obsservice'''
The is the source service daemon. OBS 1.7 just comes with a download
service so far. This feature is considered to be experimental so far,
but can be already extended with own services.

'''Install Lighttpd'''

lighttpd also needs to be available on backend server. This is required to provide directory listing on the repositories available on this server when an http/s request to maemo-repo is made through web ui.

<source lang='bash'>
zypper in lighttpd
</source>

Create a new file under /etc/lighttpd/vhosts.d/. It can be obs.conf as well, and add:
<source lang='bash'>
vi /etc/lighttpd/vhosts.d/obs.conf

$HTTP["host"] =~ "repo.obs.maemo.org" {
server.name = "repo.obs.maemo.org"

server.document-root = "/srv/obs/repos/"
dir-listing.activate = "enable"
}
</source>

To enable vhosts, remember to '''uncomment''' the following in the 'custom includes':

<source lang='bash'>
vi /etc/lighttpd/lighttpd.conf
##
## custom includes like vhosts.
##
#include "conf.d/config.conf"
# following line uncommented as per
# /usr/share/doc/packages/obs-api/README.SETUP
include_shell "cat vhosts.d/*.conf"
</source>

Start lighttpd
<source lang='bash'>
#first add it as deamon
chkconfig --add lighttpd
rclighttpd start
</source>

== Installing the Frontend (WebUI and API) ==

Start with a minimal Suse install and then add Tools repository where OBS 1.7 is available.
<source lang='bash'>
cd /etc/zypp/repos.d/;
wget http://download.opensuse.org/repositories/openSUSE:/Tools/openSUSE_11.2/openSUSE:Tools.repo
zypper ref
# Accept the trust key
</source>

Install obs-api (It's going to install lighttpd webserver by dependency for you).
<source lang='bash'>
zypper in obs-api memcached
</source>

'''Setup Mysql'''

Mysql server needs to be installed and configured to start as deamon
<source lang='bash'>
chkconfig --add mysql
rcmysql start
</source>
Setup a secure installation, if it's the first time starting mysql
<source lang='bash'>
/usr/bin/mysql_secure_installation
</source>
The frontend instance holds 2 applications, the api and the webui. Each one need a database created
<source lang='bash'>
mysql -u root -p
mysql> create database api_production;
mysql> create database webui_production;
</source>
Add obs user to handle these databases
<source lang='bash'>
GRANT all privileges
ON api_production.*
TO 'obs'@'%', 'obs'@'localhost' IDENTIFIED BY '************';
GRANT all privileges
ON webui_production.*
TO 'obs'@'%', 'obs'@'localhost' IDENTIFIED BY '************';
FLUSH PRIVILEGES;
</source>
Configure your MySQL user and password in the "production:" section of the api config:
<source lang='bash'>
vi /srv/www/obs/api/config/database.yml
#change the production section
production:
adapter: mysql
database: api_production
username: obs
password: ************
</source>
Do the same for the webui. It's configured, by default to use sqlite, but since we're configuring the cluster for production environment, let's bind it to mysql:

<source lang='bash'>
vi /srv/www/obs/webui/config/database.yml
#change the production section
production:
adapter: mysql
database: webui_production
username: obs
password: ************
</source>
Populate the database
<source lang='bash'>
cd /srv/www/obs/api/
RAILS_ENV="production" rake db:migrate

cd /srv/www/obs/webui/
RAILS_ENV="production" rake db:migrate
</source>
You can check the migration was successful verifying the “migrated” message at the end of each statement.

'''Setup and configure lighttpd for the api and webui'''

You need to setup the correct hostnames to where webui, api and repo server are going to point to
<source lang='bash'>
vi /etc/lighttpd/vhosts.d/obs.conf
$HTTP["host"] =~ "build" {
rails_app = "webui"
rails_root = "/srv/www/obs/webui"
rails_procs = 3
# production/development are typical values here
rails_mode = "production"

log_root = "/srv/www/obs/webui/log"

include "vhosts.d/rails.inc"
}
$HTTP["host"] =~ "api" {
rails_app = "api"
rails_root = "/srv/www/obs/api"
rails_procs = 3
# production/development are typical values here
rails_mode = "production"

log_root = "/srv/www/obs/api/log"

include "vhosts.d/rails.inc"
}
$HTTP["host"] =~ "download" {
# This should point to an rsync populated download repo
# server.name = "download.obs.maemo.org"
# server.document-root = "/srv/obs/repos/"

proxy.server = ( "" => ( (
"host" => "10.1.1.11",
"port" => 80
))
)
}
/source>

To enable these vhosts, make sure to '''uncomment''' the following in the 'custom includes' section at the bottom of /etc/lighttpd/lighttpd.conf:
<source lang='bash'>
vi /etc/lighttpd/lighttpd.conf
##
## custom includes like vhosts.
##
#include "conf.d/config.conf"
# following line uncommented as per
# /usr/share/doc/packages/obs-api/README.SETUP
include_shell "cat vhosts.d/*.conf"
</source>
Also, the modules "mod_magnet", "mod_rewrite" and fastcgi need to be enabled by uncommenting the corresponding lines in /etc/lighttpd/modules.conf:
<source lang='bash'>
vi /etc/lighttpd/modules.conf
server.modules = (
"mod_access",
# "mod_alias",
# "mod_auth",
# "mod_evasive",
# "mod_redirect",
"mod_rewrite",
# "mod_setenv",
# "mod_usertrack",
)

##
## mod_magnet
##
include "conf.d/magnet.conf"

##
## FastCGI (mod_fastcgi)
##
include "conf.d/fastcgi.conf"
</source>
You need also to configure /srv/www/obs/webui/config/environments/production.rb to point to correct server names:
<source lang='bash'>
vi /srv/www/obs/webui/config/environments/production.rb
FRONTEND_HOST = "api.obs.maemo.org"
FRONTEND_PORT = 80
EXTERNAL_FRONTEND_HOST = "api.obs.maemo.org"
BUGZILLA_HOST = "http://bugs.maemo.org/"
DOWNLOAD_URL = "http://downloads.obs.maemo.org"
</source>
Do the same for /srv/www/obs/api/config/environments/production.rb. As soon your backend is not on the same machine as the api (frontend), change the following:
<source lang='bash'>
vi /srv/www/obs/api/config/environments/production.rb
SOURCE_HOST = "src.obs.maemo.org"
SOURCE_PORT = 5352
</source>
Make sure TCP port 5352 is open on the firewall.
Ensure lighttpd and obs ui helpers start:
<source lang='bash'>
chkconfig --add memcached
chkconfig --add lighttpd
chkconfig --add obsapidelayed
chkconfig --add obswebuidelayed

rcmemcached start
rclighttpd start
rcobsapidelayed start
rcobswebuidelayed start
</source>

ligthttpd user and group need to be the onwer of api and webui dirs (as well as log and tmp):
<source lang='bash'>
chown -R lighttpd.lighttpd /srv/www/obs/{api,webui}
</source>

== Installing the Workers ==

The other 14 hosts on the cluster are reserved to be used as workers, where package builds are going to place.

The same openSuse Tools repository addition must be done for each worker.
<source lang='bash'>
cd /etc/zypp/repos.d/;
wget http://download.opensuse.org/repositories/openSUSE:/Tools/openSUSE_11.2/openSUSE:Tools.repo
zypper ref
# Accept the trust key
</source>

Install worker:
<source lang='bash'>
zypper in obs-worker quemu-svn mount-static bash-static
</source>
(mount-static and bash-static are needed on the worker for rpm cross-compile to work)

Edit the file /etc/sysconfig/obs-worker in order to point to correct repository server.
<source lang='bash'>
vi /etc/sysconfig/obs-worker
OBS_SRC_SERVER="src.obs.maemo.org:5352"
OBS_REPO_SERVERS="repo.obs.maemo.org:5252"
OBS_VM_TYPE="none"
</source>

Each worker has 16 CPUs, so 16 workers need to be started.

Start the worker service:
<source lang='bash'>
chkconfig --add obsworker

rcobsworker start
</source>

== Tuning ==
The lighttpd config was reduced to 3 api/webui child processes from 5.

== Revise VG setup ==

lvremove /dev/VG_data/w[8-12]_root
lvremove /dev/VG_data/w[8-12]_swap

pvmove /dev/dm-32
vgreduce VG_data /dev/dm-32
kpartx -av /dev/dm-32

add map 360060e8005478600000047860000398c_part1p1 (253:21): 0 97659072 linear /dev/dm-32 63
add map 360060e8005478600000047860000398c_part1p2 (253:22): 0 97659135 linear /dev/dm-32 97659135
add map 360060e8005478600000047860000398c_part1p3 (253:23): 0 97659135 linear /dev/dm-32 195318270
add map 360060e8005478600000047860000398c_part1p4 (253:24): 0 126431550 linear /dev/dm-32 292977405

(Worried these partitions may not come back at reboot time)

Now creat the OBS VG for the host xen worker:
pvcreate /dev/mapper/360060e8005478600000047860000398c_part1p1
vgcreate OBS /dev/mapper/360060e8005478600000047860000398c_part1p1

pvcreate /dev/mapper/360060e8005478600000047860000398c_part1p1
vgextend OBS /dev/mapper/360060e8005478600000047860000398c_part1p1

lvcreate -L 5G -n cache OBS
mkfs -text4 /dev/OBS/cache

for i in 1 2 3 4 5 6 7 8 9 10
do
lvcreate -L 4G -n worker_root$i OBS
mkfs -text4 /dev/OBS/worker_root$i
lvcreate -L 1G -n worker_swap$i OBS
mkswap /dev/OBS/worker_swap$i
done

Note in 1.7.3 obsstoragesetup makes /OBS.worker/root1/root but obsworker looks for /OBS.worker/root_1/root (root1 vs root_1)

Also ensure the host has :
obs-worker (1.7.3)
qemu-svn

In order to run arm binaries in the xen chroot we need to ensure the initrd inserts binfmt_misc
in /etc/sysconfig/kernel, set
DOMU_INITRD_MODULES="xennet xenblk binfmt_misc
then
mkinitrd -k vmlinuz-2.6.31.12-0.2-xen -i initrd-2.6.31.12-0.2-xen-binfmt -B

On the backend machine edit /usr/lib/build/xen.conf to use the correct initrd

[[Category:OpenSuse build service]]

Maemo Wiki Mirror - User contributions [en]

Summer'12 Device Program/Qt 5 Mobile Projects

OpenSuse Build Service/Installation