DOCSLIB.ORG

Building Appliances Locally with KIWI

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Building Appliances Locally with KIWI TUT 8118 SUSE® Studio Onsite in the Datacenter Andreas Thomas Ralf Dannert Designated Support Engineer Systems Engineer [email protected] [email protected] Agenda • Overview SUSE Studio • SUSE Studio and SUSE Manager Integration • SUSE Studio POCs in Datacenter environments ‒ Challenges in Build Environment ‒ Challenges in Deployment ‒ More Troubleshooting • Q&A 2 Overview SUSE Studio SUSE Studio Onsite: Key Features • Supported Linux in Minutes • Integrated Testing(testdrive) • Multiple Platforms ‒ Live CD/DVD, preload ISO/USB, HDD, PXE, Xen, vmdk, OVF, Amazon EC2) • Supportability Analyzer • Automated Dependency Discovery • Multi-Host Staged Delivery • SUSE Gallery 4 SUSE Studio Onsite (I/II) ‒ Behind the firewall, on-premise, installable and fully supported version ‒ similar core functionalities as SUSE Studio Online ‒ Delivered as software appliance, requires bare metal server to install ‒ Shipped as raw disk image and a bootable CD containing the raw disk image ‒ SUSE Studio is proprietary software and delivered based on a software licensing model 5 SUSE Studio Onsite (II/II) • SUSE Studio needs access to the following types of repositories used to build the appliance: ‒ Installation repositories: Pool repositories ‒ Update repositories: ‒ directly from NCC/SCC ‒ use Subscription Management Tool (SMT) for SLE 11 SP3 to mirror the update repositories from NCC • create appliances using the following base Operating Systems: ‒ SLE{DS} 10 SP4 x86 and x86_64 ‒ SLE{DS} 11 SP1,SP2,SP3 x86 and x86_64 ‒ SLE{DS} 12 with Maintenance Update after SLE 12 Release 6 Challenges Addressed by SUSE Studio Onsite • Reduced Image footprint – JeOS • Standardization and Documentation • Fast iterative development process of a custom distribution ‒ Import changed files from testdrive ‒ Overlay files • Use KIWI for additional functionality later 7 SUSE Studio Architecture 9 SUSE Studio and SUSE Manager Integration SUSE Manager ✔ Optimize ✔ Control ✔ Innovate 11 Background: SUSE Manager Staging ‒ SUSE Manager: move channels errata into the next stage/environment for ongoing phased testing/rollout ‒ natural progression from DEV to QA to PROD ‒ Formerly: spacewalk-clone-by-date ‒ now: spacewalk-channel-patch-lifecycle ‒ spacewalk-manage-channel-lifecycle --promote --phases=DEV,QA,PROD -c sles11-sp3-pool-x86_64 12 SUSE Manager Integration Build appliances from stages Dev/Test/Prod/ ‒ cobbler used as installation source for a distribution ‒ Prerequisite: distribution exists and child channels available ‒ SUSE Manager: ‒ Systems → Autoinstallation → Distributions → lable ‒ parent channel of child channel must be assigned to the distribution ‒ SUSE Studio: use these channels as repositories ‒ http://<susemanager>/ks/dist/child/<childchannel-label>/<dist-label> ‒ Admin User →Advanced → Add Repository ‒ Usecases: ‒ Easy (de)provisioning of repositories possible ‒ Snapshotted, reproducible builds 13 SUSE Manager Integration Troubleshoot ‒ URLs to integrate with SUSE Manager are not “normal URLs” ‒ "grep /ks *" in /etc/apache2/conf.d reveals that /ks/dist gets re-routed to "/rhn/common/DownloadFile.do" ‒ zz-spacewalk-www.conf:RewriteRule ^/ks/dist(.*)$ ‒ /rhn/common/DownloadFile.do?url=/ks/dist$ ‒ every URL starting with /rhn is passed to tomcat as of this rule: ‒ zz-spacewalk-www.conf:RewriteRule ^/rhn(.*) ajp://localhost:8009/rhn$1 [P] 14 Challenges in Build Environment SUSE Studio and Datacenter • Differences between datacenter and “old” purpose of studio usage • Benefits of image deployment vs autoyast ‒ speed up of deploment (less reboots / no hardware probing) ‒ Faster development process (e.g. test drives, overlay files) ‒ Ideally: base image for deployment and customizing via software management stack 16 Using Your Own Repository(I) 17 Using Your Own Repository(II) 18 Using Your Own Repository(III) Declaring Pattern 19 Using Your Own Repository(IV) Updating Repository Data Now we've got a reposory providing “our” RPMs and “our” software patterns 20 Include and Use it in SUSE Studio 21 Challenges in Deployment Challenges in Deployment • Disk-less Servers (boot from SAN, discovery of disks) • Different Network Adapters / IP Address advertising • Struggeling “unknown” Networks (blade center) • Multipathing / host-based mirror requirements • Use of “own” Patterns and custom RPMs • Kiwi version in Studio / Containment ‒ Upstream kiwi with fixes / features not yet in Studio ‒ Awareness of Product Management to update kiwi version in products ‒ There's always more than one way to do it (pxe, initrd, kiwi) 23 Disk-less Server / Boot from SAN • Only plain SCSI disks are being detected / supported out of the box • Need support for /dev/disk/by-*/scsi-XXXX • Solution: ‒ Current Kiwi version ‒ Upcoming Maintenance Update 24 Solving Software Dependencies ‒ Solving dependencies in Studio is based on zypper mechanics ‒ Repositories based on zypper ‒ Refresh of repositories ‒ Priorities of repositories ‒ Custom change in Studio (use old version of RPM as default) ‒ Self created repositories (using createrepo) ‒ Custom templates as FATE 25 Choose Non-default rpm Versions ‒ choose a specific software version from another repository manually ‒ visible in Build → Configuration → Selected software ‒ if version attached to name → have been manually selected ‒ lower priority of repository in /srv/studio/options.yml ‒ add repos_with_lower_priority: according to ‒ Changing Repository Order from the SUSE Studio Onsite Deployment And Administration Guide ‒ example: Add OBS repository ‒ Admin User → Repositories →Add repository ‒ Name: python ‒ URL: http://download.opensuse.org/repositories/devel:/languages:/python/SLE_1 1_SP3/ 26 Software Management • Adjustments in post build script (strip down) • firstboot_script • Adding repositories during bootup/firstboot • Limitations of 3rd party rpms ‒ Scripts in RPMs (e.g. add users/permissions/acls) ‒ Boot-related rpm (missing bootloader file) ‒ Custom templates as FATE 27 RPMs Break Build Process WHY? • Scripts in 3rd party RPMs may use acls ‒ Fixes in the meantime • Scripts in RPMs might require boot-related files ‒ /boot/grub/menu.lst, /etc/fstab etc. Solutions: ‒ Fix RPM script (if possible) ‒ Install after deployment (firstboot script) ‒ Using “wrapper RPMs” if not network accessible (e.g. test drive) ‒ add a repository using “zypper ar” during firstboot and install afterwards 28 No Network... No PXE Deployment • Root cause: Stripping of unnecessary packages after build • Solution: Include kernel-firmware package in bootrequired, specify dedicated 29 ...And Strange Behaviours • First DHCP request is taken for Network configuration • BUT: Some blade centers run their own DHCP server • 169.X.X.X is not routed to “our” TFTP for image rollouts • Possible Solutions: ‒ 1. specify MAC/NIC assingments as append parameter ‒ 2. build initrd having a recent KIWI build environment ‒ 3. Edit initrd (see custom initrd) to limit NICs used for discovery 30 ...Just Specify to Your Demands DEFAULT KIWI-Boot LABEL KIWI-Boot kernel boot/kernel_new append initrd=boot/initrd_new vga=0x314 kiwiserver=4.239.87.130 PXE_IFACE=eth0 lang=de_DE insmod=bnx2 netwait=90 netretry=5 prefer_iface=eth0 BOOTIF=eth0 IPAPPEND 1 31 Building a Custom Image • How to include ‒ Required firmware (e.g. include kernel-firmware package) • Troubleshooting tools (less, vim, util-linux, sshd) • troubeshooting initrd vs roll-out initrd • Use of hooks to extend initrd • Business as usual, integration in process is the key 32 Export – Adapt – Build – Deploy (0) 33 Building Appliances Locally with KIWI ‒ Build tab, scroll down and select Export your appliance's KIWI configuration ‒ have latest version from the Open Build Service repository Virtualization: Appliances ‒ sudo ./create_appliance.sh ‒ specify repository URL for internal (non-public) repositories ‒ <repository type='rpm-md'> ‒ <source path='{SLES 11 SP3 Updates i386}'/> ‒ </repository> ‒ README for Kiwi source from SUSE Studio 34 Export – Adapt – Build – Deploy (I) 35 Export – Adapt – Build – Deploy (II) Kiwi Hooks 36 Export – Adapt – Build – Deploy (III) config.xml for PXE 37 Export – Adapt – Build – Deploy (IV) Pattern in Kiwi 38 Export – Adapt – Build – Deploy (V) toolchain in bootincludes 39 Export – Adapt – Build – Deploy (VI) Adapt Repositories 40 Export – Adapt – Build – Deploy (VII) Kiwi Hooks ‒ RAID 1 (mirror) supported out of the box ‒ Multipath and DM support in recent kiwi ‒ Need to use hook functions for enablement 41 Export – Adapt – Build – Deploy (VIII) ● Copy output to tftp 42 Export – Adapt – Build – Deploy (IX) tftp 43 Export – Adapt – Build – Deploy (X) PXE 44 Export – Adapt – Build – Deploy (XI) 45 Export – Adapt – Build – Deploy (13) 46 More Troubleshooting Some Hints • Use kiwidebug=1 parameter in PXE configuration ‒ Emergency shell ‒ Detailed log in /var/log/boot.kiwi • Build a debug initrd with “your” tools • Use KIWI_FORBID_HOOKS=1 to eleminate “your bugs” • env output helps you to verify what went wrong • /include helps you to understand systems behaviour 48 How to Debug a Containment(I) • What is a containment • %description ‒ Containment appliance to build studio images secured by a VM layer ‒ tar -cjf $RPM_SOURCE_DIR/$NAME-$VERSION- $RELEASE-vmx.tar.bz2 $SOURCE metadata ‒ rpmbuild -ba $FILES_DIR/image.spec ‒ https://github.com/openSUSE/containment-rpm 49 How to Debug a Containment(II) ‒ minor debugging session in containment: ‒ in kiwi-job/lib/containment.rb, set self.debug to 1 ‒ start the build. roughly after 'downloading packages', you'll see something like: ‒ Containment running
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]