DOCSLIB.ORG

Kiwi to Create Customized Pos Images

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Kiwi to Create Customized Pos Images Using Kiwi to Create Customized PoS Images Cleber Paiva de Souza / Gabriel Cavalcante {cleber,gabriel}@ssys.com.br S-SYS Systems and Solutions S-SYS and SUSE • S-SYS officially born Jan/2014 • SUSE partner since beginning • Formed by professionals with experience in SUSE products, Linux in general, training and software development • Acting together with SUSE engineers in pre- sales and project delivery 2 Scenario Retail customer profile • NDA (Non-disclosure agreement) in place • ~300 stores in Brazil • >1.5k Kiosks • 2Mbps connection between IT HQ and stores • Application developed in Java + Adobe Flash • OpenSUSE 11.2 was installed on all Kiosks 4 Kiosks Manufactures: • IBM • Toshiba • Itautec • OKI 5 Brazil size 6 Kiosk hardwares • Composed of old (>5 years) and new hardware. – VIA C7-D Processor 2000MHz, 384 MB RAM • Wifi USB dongle diversity, many unsupported on Suse Linux 11 by default. • PinPads • Barcode scanners • Printers • Touchscreen displays 7 Daily problems • Infeasible to keep one IT staff at each store. • New kiosk setup requires following a 12 pages manual by store manager with many IFs. • Store manager should look at the hardware and detect the device combination available. • A USB keyboard is required to perform installation. • More steps to configure the kiosk and deploy application. • Kiosk passwords are written on manual. • Constant file system corruption. There is only a power on/off switch key. 8 Plan Improvement plan • Migrate from OpenSUSE 10.2 to SLES 11 SP4 as the operating system base. • Reduce image size (JeOS concept). • Reduce distribution complexity (number of services, lighter window manager etc). • Support legacy hardware. • Detect and apply changes in the set of supported hardwares. • Develop a configuration utility to help non-IT staff in the deployment process at the store. 10 Desired Process 11 Solution Kiwi • Version 7. • Image build tool – Command line tool. – Multiple formats generation (iso, img, oem etc). – Use configuration files to guide the generation. – Very flexible workflow. – Possible to use standard and custom packages. – Enables the use of a root directory template. 13 Kiwi usage *.rpm / template config.xml 14 Kiwi – 2-step Image Creation Process • Create target root directory. • Install packages. • Apply the overlay tree. • Apply archives. • Execute user defined config.sh script. • Manage the new root tree. • Extra: – Execute user defined images.sh script. – Create requested image type (Live, CD, DVD, USB stick, Xen, KVM, Amazon etc). 15 Migration process • On kiwi migrate from OpenSUSE to SLES 11 required only setting: – boot="oemboot/suse-SLES11" • Required SLES 11 SP4 32 bits image due to legacy applications. • Cleanup image: – Remove unused packages – Disable unnecessary services – Remove documentation files – Remove info and man page files – Activate and configure essential services (NTP, SSH etc) 16 Migration process • Select a lightweight window manager (sorry GNOME). • Opted for Xfce, simple, lightweight and attends customer needs. – Problem 1: No official packages for Xfce on SLES 11. – Problem 2: No community Xfce package on Open Build Service (OBS). – Problem 3: Xfce latest version requires Gtk+ 2.20 and Glib 2.24, but SLES 11 SP4 provides Gtk+ 2.18 and Glib 2.11. • Xfce 4.8 was the latest version compatible with SLES 11 SP4. 17 XFCE • After 3 days working on OpenSUSE RPMs: – Compiling – Minor changes on code – Solving libraries conflicts • Xfce4 RPMs for Suse 11 SP4 (32 bits only): – http://www.ssys.com.br/susecon/cas20057 • Warning: Packages deployed with OpenSUSE trademarks and logomarks. • Apply customizations for Xfce in /etc/xdg/xfce4 (window manager, session, panel, desktop, background etc). 18 Wireless • Suse Kernel support a wide range of wifi devices – USB and PCI • However the devices variety keeps increasing. Probably hard to test all models for official releases. – Usually kiosk assemblers ship cheap wifi devices. – In our case, 3 out of 4 kiosk wifi devices were not supported by default SuSE kernel driver modules. – We compiled drivers from manufacturers and from backports. – To achieve this, we installed a preliminary image version into each kiosk to have a complete compilation environment. – We shipped all compiled drivers and firmwares in the final image. 19 Touchscreen display • Each kiosk have a different touchscreen display, each one with different ways for calibration. • On EloGraphics touchscreen serial devices, touchcal calibration utility was able to configure the device correctly. New to SLES 11 SP4. • On touchscreen USB devices, it was necessary to load ”usbhid” module to emulate touchscreen as a input device. • On another touchscreen USB, it was necessary to install and run a service to control the device. 20 Rules to create /dev shortcuts • The kiosk application uses devices directly from /dev for: – Barcode scanner – Printer – Pinpad • Kiosks had many variations of this set. • Devices were mapped in udev to provide meaningful devices: – /dev/BScanner – /dev/Printer – /dev/Ppad 21 Rules to create /dev shortcuts • For USB devices we could create udev rules: SUBSYSTEM=="usb",SUBSYSTEMS=="usb", ATTR{idVendor}=="0dd4", ATTR{idProduct}=="015d", SYMLINK+="Printer” ,GROUP="users", MODE="0660” • Serial devices are a little bit harder, but the kiosk manufacturer ships, for example, serial printers always in the same port (/dev/ttyS0, /dev/ttyS1 etc) • Sometimes manufacters provide tools for testing communication with serial devices. • Sometimes no, so we try on our own (pyserial). • Our setup detect the hardware model and hardcode serial device path on application configuration file. 22 Using configuration file templates • Preparing application • Devices configuration • Networking configuration (wireless) • Display configuration • Templates for store application – Store number – Kiosk number – Kiosk device configuration to application 23 Using configuration Templates • atm.printerPortType=usb atm.printerModel=VKP80II atm.printerFont=Courier 12 Pitch atm.printerFontSize=19 scope.modo=2 scope.empresa={{{COMPANY_NAME}} # four digit stored id scope.filial={{{STORE_ID}}} # three digit kiosk id scope.pdv={{{KIOSK_ID}}} • scope.dummyMode=false 24 Auto Install Image <type image="iso" bootloader="grub" bootpartition="true" bootpartsize="206" boottimeout="5" bootfilesystem="ext3" filesystem="ext3" checkprebuilt="false" boot="oemboot/suse-SLES11" bootkernel="std" installiso="true" devicepersistency="by-label" installboot="install" installprovidefailsafe="false" volid=“Installation" kernelcmdline="quiet rootflags=data=journal splash=silent"> <oemconfig> <oem-boot-title>SUSE 11.4 KIOSK</oem-boot-title> <oem-reboot>true</oem-reboot> <oem-bootwait>false</oem-bootwait> <oem-swap>true</oem-swap> <oem-swapsize>1024</oem-swapsize> <oem-unattended>true</oem-unattended> <oem-skip-verify>true</oem-skip-verify> <oem-kiwi-initrd>true</oem-kiwi-initrd> <oem-inplace-recovery>false</oem-inplace-recovery> </oemconfig> 25 Creating first boot configuration • The image is decompressed to the system, with all the templates. • Template files are filled with store and kiosk information. • Solution: – Build a configuration utility that ask some questions to the store manager. – Minimal information required: – store and kiosk id. – kiosk model and it devices (if we are not able to detect it automatically). – WIFI information. – *We could do better if network infrastructure helped. 26 Configuration Utility • Python using pydialog PROBLEM KIOSK DOESN’T HAVE KBD!!! 27 Add a Virtual KBD and lock windows • Create a autologin setup user in /etc/inittab. • Remove all startup code of Xfce. • Add lines to Xfce xinitrc setup startup: – /usr/bin/xterm -geometry 142x30+0+0 -uc +l -title "Setup Kiosk" /usr/bin/setup & – /usr/bin/xvkbd -compact -geometry 800x150+0-25 -secure -no-repeat -no-functionkey -window "Setup Company" & 28 Configuring kiosk • Simple but useful configuration screen: 29 Final reboot • After the configuration process, the system is ready to a final reboot. • Setup switches default user to application user. • On application user login some remediation are still necessary: – echo "079b 0028" > /sys/bus/usb- serial/drivers/cp210x/new_id • Start Xfce: – nohup startxfce4 >/dev/null 2>&1 • Run kiosk application using Xfce autostart. 30 Grub • By default kiwi add entry to boot from local hard disk: – Set: bootkernel="std” • By default kiwi sets --disk-start-sector to 2048. Does not work on some old hardware: – Set: --disk-start-sector 32 • Alternatively use syslinux: – Set: bootloader="grub” – /boot must be in FAT32. – No GFX boot menu. • rootflags=data=journal 31 Consideration • Read full documentation before starting. • Try an example from /usr/share/doc/packages/kiwi/examples. • Check Kiwi schema documentation for options and special parameters (some kiwi options and parameters are documented only on the schema documentation). • Be careful, some errors will raise only 20-30 minutes after Kiwi build process. 32 Can we do more? Possibilities • Centralize frequent builds and dispatch new images with PXE in each store (for non-wireless computers) • Self deploy environments • Images for store server • Insert pre-configured services in the image: – Monitoring – Configuration Management – Authentication – Auditing – etc 34 Drawing the process in Suse Studio Online Select Default Software 36 Upload a zip with custom RPMs 37 Add a tar.bz2 file with custom / 38 Add custom RPMs 39 Adjust startup parameters (post scripts) 40 Limitations • EULA Accept process (free version). • Accept
Load more

Recommended publications
  • SUSE Template V2
    Continuous Integration und DevOps mit dem Open Build Service SLAC 7.6.2013 Ralf Dannert Systems Engineer [email protected] Agenda • OBS Überblick • Nutzer/Anwendungsszenarien • osc - cmdline client • Source services • Ungewöhnliche Deliverables(Kiwi) • OBS Appliance • Continuous Integration/DevOps 2 OBS History • Created in 2005 as a rewrite of SUSE's internal autobuild system ‒ Goals: transparency, flexibility, openness ‒ First presented at FOSDEM 2006 • 2010: OBS-2.0 with features for the MeeGo project • 2011: OBS-2.1 with workflow features for openSUSE source handling • Current Release: OBS-2.4 3 4 Open Build Service (previously known as openSUSE Build Service) • Automated, repeatable and consistent : ‒ Clean chroot ‒ Handle build dependencies and autorebuild if needed ‒ Take care of publishing consistent repositories • Generate packages or full OS images / appliances 5 Development • Licensed under GPLv2 ‒ https://github.com/openSUSE/open-build-service/ • Lines of Code: > 150000 ‒ Perl/Python/Ruby • Mostly maintained by SUSE, but many contributions from community members & other companies 6 Numbers • Confirmed Users: >32000 • Package builds per day: > 51000 ‒ Build farm: 38 hosts, 310 workers • Storage: ‒ Sources: 3.3 Tbytes ‒ Binaries: 6.9 TBytes 7 Features • Multiple distributions, multiple architectures ‒ rpm, deb, archlinux, image creation • Sand-boxed builds (kvm/xen/lxc) on a build farm • Easy branching with automatic merges • Continuous Integration ‒ Automatic rebuilds on changes (both source and build packages), automatic ordering
    [Show full text]
  • Manjaro Linux
    MANJAROLINUX USERGUIDE THEMANJARODEVELOPMENTTEAM Copyright © 2018 the Manjaro Development Team. Licensed under the Attribution-ShareAlike 4.0 International Licence (the “Licence”); you may not use this file except in compliance with the License. You may obtain a copy of the Licence at: https://creativecommons.org/licenses/by-sa/4.0/legalcode Unless required by applicable law or agreed to in writing, software distributed under the Licence is distributed on an “as is” basis, without warranties or conditions of any kind, either express or implied. See the Licence for the specific language governing permissions and limitations under the Licence. The source code for this documentation can be downloaded from: https://github.com/manjaro/manjaro-user-guide/ user guide 5 The Manjaro Development Team Core Team Philip Müller Owner, Project Leader, Project Management and Co- ordination, Mirrors Manager, Server Manager, Packager, De- veloper, Web Developer Guillaume Benoit Developer, Moderation Ramon Buldó Developer, Packager Stefano Capitani Maintainer, Packager Bernhard Landauer Community Manager, Packager, Maintainer, Mod- eration, News Rob McCathie Maintainer Marcus Developer, Packager Teo Mrnjavac Developer Alexandre A. Arnt Developer, Moderation Ringo de Kroon Community Hugo Posnic Developer Artwork David Linares Designer Documentation Jonathon Fernyhough Editor of the User Guide 0.8.9-0.8.13, 15.09-15.12, Community Management, Cover art of the User Guide Sabras Wiki Manuel Barrette Editor of the User Guide 16.08-17.1, French transla- tion of the User Guide 17.0-17.1 Alumni Roland Singer Founder, Designer, Developer, Web Developer, Admin- istrator Carl Duff Community, Documentation and Wiki Management, Script- ing and Configuration Cumali Cinnamon and Gnome Community Editions Maintainer 6 manjaro linux Dan S.
    [Show full text]
  • Build Your Own Linux Distribution
    Build Your Own Linux Distribution . during lunch break Michal Hruˇseck´y openSUSE Community Multiplier Team [email protected] Creating a distribution Distributions characteristics What we need to create our own distribution: Installation wizard Configuration utilities Branding Default configuration Package management Packages and their settings ... 3/20 c Novell Inc. All Right Reserved How to create distribution We want it fast and we don't want to work hard Let's use the others !!! And let's start with LiveCD 4/20 c Novell Inc. All Right Reserved Work to do What can we skip: Installation wizard Configuration utilities Package management Not necessary for LiveCD. What we need: Branding Default configuration Packages and their settings 5/20 c Novell Inc. All Right Reserved Closer look Branding: Just a different default theme We need to adjust/add packages Default configuration: We need to adjust packages Packages and their settings. =) Everything is about packages 6/20 c Novell Inc. All Right Reserved Conclusion We need quite a lot packages but we don't want to work on them by ourself. =) Let's fork Here it comes, let's use work done by somebody else So we need to get a lot of packages, maintain them easily and to be able to collaborate with other packagers =) openSUSE Build Service And we need something to create our LiveCD from our packages =) SUSE Studio 7/20 c Novell Inc. All Right Reserved openSUSE Build Service Build Service To build and publish packages... free and open platform for building packages for various distributions like openSUSE, Fedora, Ubuntu,..
    [Show full text]
  • By the Power of Toolbox (Slides)
    Dario Faggioli “By The Power Of Virtualization SW. Eng. @ SUSE [email protected] Toolbox!” dariof @DarioFaggioli https://dariofaggioli.wordpress.com/ https://about.me/dario.faggioli About Me What I do ● Virtualization Specialist Sw. Eng. @ SUSE since 2018, working on Xen, KVM, QEMU, mostly about performance related stuff ● Daily activities ⇒ how and what for I use my workstation ○ Read and send emails (Evolution, git-send-email, stg mail, ...) ○ Write, build & test code (Xen, KVM, Libvirt, QEMU) ○ Work with the Open Build Service (OBS) ○ Browse Web ○ Test OSes in VMs ○ Meetings / Video calls / Online conferences ○ Chat, work and personal ○ Some 3D printing ○ Occasionally play games ○ Occasional video-editing ○ Maybe scan / print some document ● And all that, I do it with an openSUSE MicroOS, an immutable OS What is MicroOS ● Immutable single purpose OS, based on Tumbleweed ○ born as container host but not limited to that use case ■ https://microos.opensuse.org/ ■ https://en.opensuse.org/Portal:MicroOS ● Maybe, check this other talks (from yesterday): ○ An User & Developer Perspective on Immutable OSes ○ openSUSE MicroOS, a platform for everything from containers, to IoT, and even the desktop MicroOS: Your Immutable Desktop Single Purpose ⇒ Your Desktop / Workstation ● Rolling, but super stable ● Still early stage ~= ALPHA state ○ But usable already ○ (it’s actually what I’m using since a few months) ● Growing community of users ● Small community of developers ○ We need your help! :-) Psst… For now, right after install, remember to do this: ● # echo "<yourusername>:100000:65536" > /etc/subuid # echo "<yourusername>:100000:65536" > /etc/subgid Other Immutable Desktop OSes ● Fedora Silverblue https://silverblue.fedoraproject.org/ “[...] unlike other operating systems, Silverblue is immutable.
    [Show full text]
  • SUSE Studio: What's New and Where We Are Heading Building and Running Linux Appliances on the Web
    SUSE Studio: What's new and where we are heading Building and running Linux appliances on the web Jan Krupa – Operations Engineer [email protected] SUSE Studio Introduction 3 4 Supported formats • USB Stick / Hard Disk Image • Preload USB Image • Live CD / DVD (.iso) • Preload ISO (.iso) • VMware Workstation / VirtualBox (.vmdk) • OVF Virtual Machine / ESXi (.ovf) • Xen guest (.img) • Hyper-V Virtual Hard Disk (.vhd) • SUSE Cloud / OpenStack / KVM (.qcow2) • Amazon EC2 (.ami) • Microsoft Azure (.vhd) 5 6 Real life example Faulty hard drive Source: https://www.flickr.com/photos/alexmuse/307226463 8 New features New distributions • openSUSE releases • SUSE Linux Enterprise Server releases • SUSE Linux Enterprise Desktop releases 10 Cloud build targets • SUSE Cloud • OpenStack • Amazon EC2 • Microsoft Azure 11 HTTPS-only access Source: https://www.flickr.com/photos/bilal-kamoon/6958578902 12 Testdrive – Increased performance Source: https://www.flickr.com/photos/laserstars/908946494 13 API Source: https://www.flickr.com/photos/mutednarayan/2280385549 14 Webhooks Source: https://www.flickr.com/photos/leecullivan/934664620 15 Projects we work on KIWI openSUSE/kiwi 17 Open Build Service openSUSE/open-build-service 18 KVM 19 Contribute to the documentation Source: https://www.flickr.com/photos/nics_events/2350462608 susestudio/studio-help 20 Where to follow us • Mailing list ‒ http://susestudio.com/forum • Twitter ‒ https://twitter.com/susestudio • Google+ ‒ https://plus.google.com/+susestudio • Facebook ‒ https://www.facebook.com/susestudio 21 Questions? Join our growing community! susestudio.com Thank you..
    [Show full text]
  • Build Your Own Distro Tired of the Run-Of-The-Mill Stuff on Distrowatch? Why Not Heed Mayank Sharma and Create the Perfect Operating System for You?
    Build your own distro Tired of the run-of-the-mill stuff on Distrowatch? Why not heed Mayank Sharma and create the perfect operating system for you? few issues ago, [LXF171, 50 making it your own – by removing apps and Now traditional wisdom says that creating Distros Tested], we looked at drivers that you don’t need and adding the your own Linux system is a rather difficult the best Linux distributions for ones you do. You’ll also probably change the thing to do and shouldn’t be attempted by A all kinds of users. There were factory-fitted artwork that says more about anyone other than Linux veterans. distros that were designed with ease of use the distro vendor than you. We begin the feature with graphical point- in mind, some focused on productivity, Sure that’s one way to go about it. and-click tools. Yes, you read that right. All it while others catered to specialised use You tweak and customise the distro to suit takes is a couple of clicks to craft your very cases, such as security and privacy your requirements. But wouldn’t it be really own flavour of Linux that you can pass to conscious users. But we can guarantee great if you just create your very own, custom friends and family. We’ve got tools that’ll help that there wasn’t a distro designed Linux distribution? you create and distribute customised spins specifically and entirely for you! based on Ubuntu, Fedora and While most Linux users make do OpenSUSE – the three mainstream with one of the mainstream distros out “We’ve got tools that’ll Linux distributions that house there, there’s always something or the help you create and thousands of open source software in other that’s missing.
    [Show full text]
  • SUSE Linux Enterprise?
    Linux Day – 2010 Tour Today's Agenda • Why SUSE Linux Enterprise? • SUSE Linux Enterprise 11 Service Pack 1 • Build & Deploy • Secure • Manage • Availability & Disaster Recovery 2 © Novell, Inc. All rights reserved. Why SUSE Linux Enterprise? Why SUSE Linux Enterprise? • Linux Distributions Share 90 to 95% of the Same Components – Most technical differentiators are very short-lived... – ...though SUSE Linux has always been a technical leader • So How Do You Choose the Best Linux Distribution? – Corporate Strategy – Best of Breed Solution Stacks – Interoperability – Support – Partner Ecosystem & Application Certification – Market Trends 4 © Novell, Inc. All rights reserved. Intelligent Workload Management Intelligent Workload Management enables IT organizations to manage and optimize computing resources in a policy-driven, secure and compliant manner across physical, virtual and cloud environments to deliver business services for Intelligent end customers. WORKLOAD Management 5 © Novell, Inc. All rights reserved. A Desktop to Data Center Platform SUSE Linux Enterprise Desktop End User Thin Client Devices Desktop SUSE Linux Enterprise Retail Point of Service Kiosk/ATM Retail/POS Appliances SUSE Linux Enterprise Server Open Enterprise Server Proxy, File & Print Firewall, VPN Email WAP, VOIP Caching SUSE Linux Enterprise Server SUSE Linux ERP, SCM, Enterprise Real Time Cluster SAN Database Web Mainframe CRM, HR 6 © Novell, Inc. All rights reserved. Best of Breed Solution Stacks - Mixed-Source Approach • Novell has a large portfolio of Open Source and proprietary products – Able to provide complete Data Center solutions using best of breed technologies > SLE, ZLM, Virtualization, Workload Management, BSM – Better positioned to work with ISVs that sell proprietary software > Example: Microsoft • RedHat is a purely Open Source company – Limited solution offerings 7 © Novell, Inc.
    [Show full text]
  • Accelerating Development Cycles and Enabling Rapid Business Growth
    ISV Case Study IT Services and Solutions Accelerating Development Cycles and Enabling Rapid Business Growth To meet increasing client demands for customisation, Pfortner wanted to accelerate its development cycle. By adopting SUSE Studio™ to build and modify its secure connectivity appliances, Pfortner has reduced development time by a massive 60 percent, accelerating the delivery of new functionality to its clients and boosting operational efficiency. Overview difficult to split work effectively across teams SUSE Business Partner: Based in Centurion, South Africa, Pfortner of developers,” said Aubrey Swane poel, provides network perimeter security so­ Man aging Director of Pfortner. “As a result, lu tions as well as network encryption ap­ each developer tended to be re spon sible pli­­ances. The company is focused on the for the full stack of management and sup­ fi nancial services sector, for which it de­ port for their own product. This slowed livers secure end­to­end connectivity so­ down the development cycle and pre ­ Name of Company lutions. Pfortner is rapidly expanding its vented them from focusing fully on their Pfortner business throughout Africa, Europe and core competence.” South America, working closely with tech­ Industry and Location nology partners. By creating a more structured develop­ IT services and solutions, South Africa ment environment, Pfortner knew that Products and Services Challenge it could accelerate delivery, improve in­ SUSE Appliance Programme As a provider of secure connectivity solu­ ternal effi ciency and bring on new team members more rapidly. SUSE Studio tions and network appliances to the finan­ SUSE Linux Enterprise Server cial services sector, which does not tend to buy off­the­shelf software, Pfortner un­ Solution Results dertakes significant customisation work Pfortner became one of the first compa­ + Cut software development time by 60 percent for its clients.
    [Show full text]
  • Chrome Os Iso Download 2017 Chromixium
    chrome os iso download 2017 Chromixium. Web site: http://chromixium.org/ Origin: United Kingdom Category: Desktop Desktop environment: Openbox Architecture: x86, x86_64 Based on: Ubuntu Wikipedia: Media: Live DVD The last version | Released: 1.5 | July 18, 2015 Zobacz po polsku: Chromixium. Chromixium – a free and open source computer operating system designed to mimic the look and feel of Google’s Chrome OS but still retain the flexibility and power of Ubuntu Linux. The Chromixium goals are: – A modular approach to (re)building the Chrome/Chromium OS desktop allows us to keep the base system light whilst at the same time beautifully modern and flexible – Hardware support for a wide range of laptops, desktops, network, video and sound cards – Installable to a conventional hard drive or partition allowing access to local storage, USB devices, printers and network shares – Ability to create persistent USB installs for portability – Ability to install additional software locally eg LibreOffice, GIMP, media players (even web browsers!) using Ubuntu or 3rd party software repositories – Complete control over customization of your operating system – Background security updates for peace of mind and hassle-free computing. Cr OS Linux. Web site: getchrome.eu Origin: Category: Desktop Desktop environment: Cinnamon Architecture: x86 Based on: openSUSE Wikipedia: Media: Live DVD/USB The last version | Released: 2.4.1290 | December 9, 2012 Zobacz po polsku: Cr OS Linux. Cr OS Linux (previously: Chrome Linux and Chrome OS Linux) – a Linux distribution built around the revolutionary Chromium browser, using SUSE Studio. It provides a lightweight Linux distribution similar to Google Chrome OS for the best web browsing experience on any x86 PC, netbook or notebook.
    [Show full text]
  • SUSE Openstack Cloud Crowbar 8
    SUSE OpenStack Cloud Crowbar 8 Supplement to Administrator Guide and End User Guide Supplement to Administrator Guide and End User Guide SUSE OpenStack Cloud Crowbar 8 by Frank Sundermeyer and Tanja Roth Publication Date: July 29, 2021 SUSE LLC 1800 South Novell Place Provo, UT 84606 USA https://documentation.suse.com Copyright © 2006– 2021 SUSE LLC and contributors. All rights reserved. Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License : http://creativecommons.org/licenses/by/3.0/legalcode For SUSE trademarks, see http://www.suse.com/company/legal/ . All other third-party trademarks are the property of their respective owners. Trademark symbols (®, ™ etc.) denote trademarks of SUSE and its aliates. Asterisks (*) denote third-party trademarks. All information found in this book has been compiled with utmost attention to detail. However, this does not guarantee complete accuracy. Neither SUSE LLC, its aliates, the authors nor the translators shall be held liable for possible errors or the consequences thereof. Contents About This Guide v 1 Available Documentation v 2 Feedback vii 3 Documentation Conventions vii 4 About the Making of This Manual ix 1 Changing the SUSE OpenStack Cloud Dashboard Theme 1 2 Managing Images 2 2.1 Image Requirements 3 General Image Requirements 3 • Image Requirements Depending on Hypervisor 3 • Images for Use With Multiple Hypervisors 4 2.2 Building Images with SUSE Studio 5 2.3 Image Properties 5 2.4 Uploading Images 6 2.5 Modifying Image Properties 8 2.6 Using
    [Show full text]
  • 48X36 Poster Template
    Open Virtualization Format SVPC Working Group DMTF OVF Highlights OVF Technology & Tools OVF Pedigree •Initial draft submitted to DMTF in 2007 OVF XML Structure OVF is an International Standard Framework and •DMTF 1.0 standard in February 2009 Packaging format used in the creation, deployment and Section Locations Multiplicity management of Virtual Appliances (VAs) and Virtual •DMTF 1.1 standard in January 2010 Machines (VMs). DiskSection- Describes meta-information about all virtual disks in the package Envelope Zero or One •ANSI/INCITS 469-2010 Standard 2010 NetworkSection- Describes logical networks used in the package Envelope Zero or One •ISO/IEC 17203 standard in August 2011 OVF is a platform-independent, extensible, open, Specifies reservations, limits, and shares on a given VirtualSystemCollection Zero or One packaging and distribution format for virtual appliances. ResourceAllocationSection- •DMTF 2.0 work-in-progress resource, such as memory or CPU for a virtual machine collection OVF Version 2.0 Feature Overview OVF, as ‘metadata’, can be used in the full lifecycle of AnnotationSection- Specifies a free-form annotation on an entity VirtualSystem Zero or One any VA or VM. VirtualSystemCollection •Scaling at Deployment Time ProductSection- Specifies product-information for a package, such as product name and VirtualSystem Zero or more •Support for Basic Placement Policies OVF uses ‘XML’ for representing this metadata about version, along with a set of properties that can be configured VirtualSystemCollection •Encryption of OVF Packages VAs and VMs and their deployment and operating EulaSection- Specifies a license agreement for the software in the package VirtualSystem Zero or more •Disk Sharing at Runtime environments.
    [Show full text]
  • Open Build Service from Holism to Reductionism What Is Open Build Service? What Is the Open Build Service(OBS)?
    Open Build Service From Holism to Reductionism What is Open Build Service? What is the Open Build Service(OBS)? Source Package Image S B O OBS user submits source to OBS and gets a product 3 What Can OBS Create? • Package repositories Add-on packages Entire distributions Variations of packages or entire products • Installable Products • Appliances • Maintenance updates 4 OBS Inside of SUSE Support Developer Product Maintenance Updates Release Manager PTF Updates Reviewer 5 What is Supported by OBS? • Build formats ‒ rpm (spec) ‒ deb (dsc) ‒ kiwi (product & appliances) ‒ Debian Livebuild ‒ ArchLinux • Build process features ‒ Build in chroot, lxc, XEN or KVM (experimental: cloud) ‒ Architectures: ia32, ia64, x86_64, ppc*, hppa, mips, m68k, s390*, various Arm architectures ‒ Qemu can be used to emulate not existing hardware ‒ Repositories: rpm-md, yast, apt, maintenance channels 6 Faces of the Build Service • Build Software Packages ‒ Always clean (aka reproducable) build from one source ‒ Supports SUSE®, Fedora, Mandriva, Debian, Ubuntu, … package building • Build Products based on packages ‒ Respins of official openSUSE or SLE medias ‒ Build Add-On medias ‒ Build Live ISOs, OEM image, USB, XEN, ... media • Make development workflows transparent ‒ Submissions to distributions ‒ Run maintenance updates 7 Where is OBS Used at SUSE®? Public build.opensuse.org Partner OBS build.suse.com ● ● openSUSE distribution SLE Driver Update Medias ● openSUSE maintenance updates ● Development teams for openSUSE & SLE components openSUSE Community ● Packman
    [Show full text]