Linux kiosk image based on opensuse and kiwi

W Toku Opublikowano Oct 10, 2014 Płatność przy odbiorze
W Toku Płatność przy odbiorze

The project involves the creation of a custom linux image based on Opensuse 13.1 and using the KIWI tool set.

[url removed, login to view]:KIWI

The scope is as follows:

1) - Custom splash png (you can add a placeholder image), also the 'green progress bar' after grub loads needs to be changed to red and instead of reading Opensuse 13.1, it should read Test_Appliance.

[url removed, login to view]:KIWI_Cookbook_Splash_Screen

2) Locale and keyboard automatically set to US English. Minimal image with no desktop (Gnome, KDE, etc) installed, basically a JeOS (Just enough OS) image.

3) Standard list of packages:

aaa_base, bison, cmake, dconf, dhcp-client, dialog, doxygen, ethtool, flex, fping, fuse, gcc, git, gnutls, grub, grub2, hwinfo, ipcalc, iputils, java-1_7_0-openjdk, java-1_7_0-openjdk-headless, kernel-default, libglib-2_0-0, libxslt1, libyui-ncurses-pkg5, lsof, make, nano, ncurses-utils, netcfg, openssh, pciutils, pkg-config, plymouth, plymouth-branding-openSUSE, polkit-default-privs, python, rpcbind, subversion, SuSEfirewall2, syslog-ng, systemd-presets-branding-openSUSE, timezone, vim, wget, yast2-firstboot, yast2-network, yum, yum-fastestmirror, zypper

4) Disk needs to be an LVM as to allow storage growth as needed

5) Very important, upon first boot (or after install from the .iso) the customer will be presented with a custom dialog menu (similar to the attached [url removed, login to view]).

This script needs to run once networking is up and before the login prompt (as customers won't have logging credentials to the appliance).

You'll need to amend the script/environment in order to make sure the client doesn't exit the menu and gain root access to the system. Up to you how to do it, but maybe create a user and give it rights to amend networking and little else.

6) As standard, KIWI supports output of the image in the following formats (may sound like lots but it is not):

a) Preload OAM ISO .iso for install in barebone servers. It shouldn't ask any questions and use all available space in an LVM. It should detect if the assigned storage is less than 2 GB and stop install in that case.

b) VM appliance with 2GB HDD, 1GB RAM and one NIC. The VM appliance to be produced in vmware and hyper-v formats

Vware .vmdk / ovf-ova

Hyper-V .vhd

c) Amazon EC2 (micro instance)

7 ) Hostname set to testappliance

DELIVERABLE:

It is expected that several iterations and further customization of the image will be required and made in-house.

Therefore, we'll need the relevant config files in order to replicate/modify the images ([url removed, login to view] [url removed, login to view], [url removed, login to view], etc).

======= PAYMENT =======

– 50% will be done once you can prove all the images work, I'll connect via teamviewer to whatever system you make available and I'll perform the following tasks:

1) Install [url removed, login to view] in a VM (virtualbox/vmware is fine)

2) Import the OVF file in virtualbox and run it

3) Import the vmdk/ovf-ova image in vmware ESXi (you can download a free copy from vmware) and run it.

4) Import the Hyper-V image in .vhd and run it

In all test cases, confirm the initial boot test script runs and the network can be configured through the script.

– 20% upon delivery of the config files, scripts and custom files required to re-build the images.

– 30% upon confirming the scripts and config files are genuine and the appliance could be rebuilt from those.

Good luck :)

Oprogramowanie wbudowane Linux

Numer ID Projektu: #6571405

O projekcie

2 ofert Zdalny projekt Aktywny Oct 11, 2014