(→How do I run OBS light server appliance on my Desktop ?) |
(→How do I run OBS light server appliance on my Desktop ?) |
||
| Line 12: | Line 12: | ||
You can overcome that limit with the addition of an obsworker appliance on a separate server. OBS Light project provides one pre-configured to work with and OBS Light server appliance. <br> | You can overcome that limit with the addition of an obsworker appliance on a separate server. OBS Light project provides one pre-configured to work with and OBS Light server appliance. <br> | ||
If you are not in NAT, external OBS work appliance will be detected and used automatically (NAT more would require a complex configuration). The Worker can be running on a more powerfull unit and speed the preparation work before for example leaving the office with a complete fully built project on a laptop. | If you are not in NAT, external OBS work appliance will be detected and used automatically (NAT more would require a complex configuration). The Worker can be running on a more powerfull unit and speed the preparation work before for example leaving the office with a complete fully built project on a laptop. | ||
| - | You can stop the worker on the laptop by the command '''rcobsworker stop''' ''(need to be root)''<br> | + | You can stop the worker on the laptop by the command '''rcobsworker stop''' ''(need to be root)''. You can check that your OBS Worker appliance can see your OBS Kight Server Appliance with the command '''slptool findsrvs obs.source_server'''<br> |
As a general rule using the bridge mode is advisable. Note ''this is '''not''' the default option of VirtualBox''. | As a general rule using the bridge mode is advisable. Note ''this is '''not''' the default option of VirtualBox''. | ||
The NAT mode is interesting to run an OBS Light server via a VPN or for unconnected demos. In that case you will need to declare NAT rules in your Vitual Machine Manager redirecting the ports 80, 81 and 82 from your local host to your OBS appliance internal NAT address ''(with VitualBox under Linux rerouting port bellow 1000 is reserved for root only)''.<br> | The NAT mode is interesting to run an OBS Light server via a VPN or for unconnected demos. In that case you will need to declare NAT rules in your Vitual Machine Manager redirecting the ports 80, 81 and 82 from your local host to your OBS appliance internal NAT address ''(with VitualBox under Linux rerouting port bellow 1000 is reserved for root only)''.<br> | ||
All data is stored in ~/OBSLight and subdirectories.
Configuration file is ~/OBSLight/obslightConfig.
While running an OBS Light appliance is simple and easy and just requires 1GB of RAM allocated to the virtual machine, running an OBS server appliance can be much more demanding but running the OBS server server appliance on your desktop or laptop (a minimum 4GB of RAM is mandatory) via a virtual machine can be very handy during evaluation tests.
The main advantage is that you do not need a special authorisation from your IT department to start playing but you need to allocate at least 2GB to the appliance and as many CPU cores that you can spare. You need to patch on the OBS server appliance (need to be root) the file /etc/sysconfig/obs-worker to set the variable OBS_WORKER_INSTANCES to 1 (default is zero) to limit the RAM resources requires by your appliance during build process.
If you plan to build large packages such as Chromium you will need more than 2GB of RAM allocated (actually on my desktop I have 16GB).
You can overcome that limit with the addition of an obsworker appliance on a separate server. OBS Light project provides one pre-configured to work with and OBS Light server appliance.
If you are not in NAT, external OBS work appliance will be detected and used automatically (NAT more would require a complex configuration). The Worker can be running on a more powerfull unit and speed the preparation work before for example leaving the office with a complete fully built project on a laptop.
You can stop the worker on the laptop by the command rcobsworker stop (need to be root). You can check that your OBS Worker appliance can see your OBS Kight Server Appliance with the command slptool findsrvs obs.source_server
As a general rule using the bridge mode is advisable. Note this is not the default option of VirtualBox.
The NAT mode is interesting to run an OBS Light server via a VPN or for unconnected demos. In that case you will need to declare NAT rules in your Vitual Machine Manager redirecting the ports 80, 81 and 82 from your local host to your OBS appliance internal NAT address (with VitualBox under Linux rerouting port bellow 1000 is reserved for root only).
Do not forget to add a host name "obslightserver" in your workstation pointing to the OBS Light server appliance IP address or localhost in the case of a NAT configuration.
The kernel package has flags to prevent builds on ARM. To compile an ARM kernel, you must use another package, for example the kernel-adaptation-n900 package.
If the project on your OBS doesn’t provide some dependencies and you must add a repository to your chroot's zypper configuration, you have two choices:
obslight addRepoInChRoot --projectLocalName MeeGo_1.2_oss --url http://download.meego.com/live/MeeGo:/1.2:/non-oss/MeeGo_1.2/ --alias "MeeGo_non-oss"
obslight addRepoInChRoot --projectLocalName MeeGo_1.2_oss --fromProject $ProjectName
Bugs are centralized on MeeGo's bugzilla.