DOCSLIB.ORG

Building Linux Distribution Packages with Docker

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Building Linux Distribution Packages with Docker Building Linux distribution packages with Docker Bruno Cornec HPE EMEA EG Presales Strategist WW Linux Community Lead, HPE Open Source Pro ession !"#0 – October 20'( #$#A Custo%ers Solution Inno&ation Center Grenoble Ma)ing the ne+ style o ,T a reality # o » './ years o success, +orld +ide programs, including Cloud Center o Excellence, C Big Data Center o Excellence, Open Source Solutions ,nitiati!e, 0,SC to HP Intel Architecture Migrations, N ! Center o Excellence, EMEA Networking Customer 1isit Center and more » C Complete ,- 23$$/ systems, 4$$$/ net+ork ports, .$$/ -B storage5 o » Port olio o 3$/ ready to demo solutions +it* access to our ecosystem o Partners P » Complete test 6 !alidation en!ironment » Strategic partners*ip +it* Intel, '.7year long standing colla&oration » Strategic partners*ip +it* "ed Hat 87year colla&oration 2OSS,5 o % » e A uni9ue proo point in t*e industry +it* a pro!en ser!ice o:ering d e & i L Mission: Accelerate t*e adoption o new and inno!ati!e solutions &y creating simple and re+arding end7to7end customer experiences t*at &ene it our customers and partners, in a p o compelling and engaging colla&orative en!ironment. h s k …more information available at http://www.hpintelco.net r o ' Introducing m(sel) ● So t+are engineering and <nices since '=>>; – Mostly Con iguration Management Systems 2CMS5, Build systems, 9uality tools, on multiple commercial <nix systems – ?isco!ered Open Source 6 Linux 2OSL5 6 made irst contri&utions in '==4 – @ull time on OSL since '==5, irst as HP reseller t*en AHP ● Currently; – OSL -ec*nology Strategist, EMEA EG ,nno!ation Solution Center a)a HPB,ntel Solution Center, Greno&le – HP OSL Ad&ocate and Con!erged ,n rastructure A%bassador – WW Linux Community Lead or t*e HP Open Source Profession – POSS con erence, OpenStac)# r and A@<L board member# Con erences at WW le!el at LinuxCon, Linux#con #au, ### – Mondo0escue, Project7Builder#org, <<WL and P<SD Pro*ect Lead – LinuxCOE, mrepo, tellico, rinse, ossology, collectl, ,ronic contributor – @OSSBaEaarBSP?F and OSL +o&ernance ent*usiast – Mandri!a, Mageia, @edora packager ● And also; – Amateur singer 2Alto B -enor5, recorder player since '=8( and C*oir director since '=>8, C? collector 2($$$/5, Concerts, P*otograp*y 3 Change in • #xecutable code • Con)iguration • In)ra 0 en&iron%ent • Data De&Ops approach, • $onitoring Change in A continuous deli&er( pipeline • 1 • #xecutable code • Con)iguration • In)ra 0 en&iron%ent • Data • $onitoring • 1 ersion controlled Peer re&iewed Auto%ated tests -lots. Continuous Deliver( Pipeline /uul P N roCect7 odepool Builder#org Infrastructure as code Basics on packaging Linux Distribution , a pro*ect in itsel) Coherent packages set 2')74$)5 ta)en rom upstream proCects Package Manager Management tools Installation progra% Startup scripts Speci ic tools !unctional updates Security updates Community dri!en or Commercial 2HW certi ication, L-S, support5 10/17/16 Linux Distributions 2i%e line '=>3 % GN<B@SF ProCect 7 0# Stallman '==' 7 Linux '==2 % SLS – Peter Mc ?onald L# -or!alds '==3 % Slack+are % Patric) 1ol)erding '==3 % ?ebian Package '==4 – 0ed Hat Linux Marc E+ing '==( % SuSE 6 Hast % @lorian La 0oc*e '==7 – 0ed Hat Package Manager '==( % ?ebian GG<BLinux Ian Murdoc) Eri) -roan 6 Mar) E+ing '==8 – Ad!anced Packaging -ool Brian White "$$' – SLES "$$" – 0HEL "$$3 – @edora "$$3 % H<M 7 Set* 1idal Warren -ogami "$$. % OpenSUSE "$$3 % <&untu Mar) S*tuttlewort* "$'. – ?G@ "$'$ – Mageia Anne Gicolas 10/17/16 7 So%e definitions ● So)tware Package, ● Application stored +it* its metadata and &uild receipt in an arc*i!e ormat# ● Pro!ides dependency in ormation at &uild and install time ● Package for%at, ● Linux pro!ides multiple ormat; rpm, de&, tgz, ip)g,### ● Open, &ased on tool li)e cpio# ● Associated +it* distri&ution amilies. ● Package %anager, ● Automates pac)ages installation, upgrade, con iguration, and remo!al in a consistent manner# ● Manages pac)age dependencies to install easily rom top o tree ● Package repositor(, ● Storage location rom +*ic* so t+are pac)ages are retrie!ed or installationBupdate ● Manages repository metadata, including dependencies ● Continuous Packaging, ● E!ery so t+are component is managed using so t+are pac)ages ● Pac)age &uild is done on t*e ly, as t*e so t+are is de!eloped Wh( still using packages toda( ? ● tar4g5 ormat ad!antages: ● "PM0deb ormat ad!antages ● 0elati!ely easy to handle ● Sta&le ● Sta&le ● Binary and source formats a!aila&le w/ multiarc* support ● Only " tools needed (tar and gEip5 ● Gati!e support or LSBB@HS ● Can integrate some files for metadata ● Provides metadata, build procedure, patches and upstream content ● tar4gz format dra+&acks ; ● Manages installation, upgrade, remo!al ● Go repository management ● SignatureBChec)sum support and veri ication ● Go dependency management ● Deployment ser!er a!aila&ility % Scripted methods ● Go easy update mechanism ● Baseline support ● Go signature support ● 0PM places e!erything in the .spec file and supports ● Limited chec)sum support su&pac)ages ● Go pac)age data&ase ● 0PM Package data&ase a!aila&le to query metadata ● "PM0deb ormat dra+&ac)s ● 0e9uire appropriate tools but in distro ● Porta&ility across OSes Building packages and repositories (rp% world. ● rp%build ● Build src#rpm and arc*#rpm pac)ages rom t*e SPEC ile ● -a)e in account con ig iles, cron jo&s, init scripts, log rotation, shell con ig ● rpmbuild -ba pkg.spec ● DO NOT BUILD AS root ● ● Signing RP$s ● Ensures aut*enticity o t*e pro!ider and pac)age integrity ● 0e9uires GPG con iguration and macros in JHOMEB#rpmmacros ● rpm --addsign pkg.src.rpm pkg.arch.rpm ● rp%lint ● Chec) rpm pac)age common errors +rt distri&ution policies ● rpmlint pkg.src.rpm pkg.arch.rpm ● createrepo ● Separate command 2not a yum option5 ● Create a yum repository rom a directory +it* pac)ages ● createrepo . Packaging best practices ●Ha&e a working installation procedure ● Use con igure i possi&le or language &uild tools 2setup#py, Ma)e ile#PL, ###5 ● Ha!e a ile &ased install +or)ing targeting BusrBlocal ● Use !aria&les or all target directories 2Betc, BusrBs*are, BusrB&in, BusrBli&, ###5 ● Script t*e &uild and install p*ases i necessary to share &et+een !arious tools ● ● 7now your package deli&erables ● Dno+ +*at you +ant to deli!er and +*ere, +*at is optional# Pac)age accordingly ● Dno+ your external dependencies ● Go source components should *a!e t*eir o+n separated pac)ages ● A!oid including ot*er projects code inline# Use dependency or re7pac)age separately i or) needed# ● Generate repositories to ease your consumers' li e ● ?ecide on a license ●A deli&er( is a tree o) packages ● ,ncreasing num&er o pac)ages reduces &uild time on t*e long run ● ,ncrease complexity at pac)age de inition, not at install time, t*an)s to pac)age managers ● ?ecide +*et*er you +ant meta7pac)ages 2prC7all, prC7net, prC7tape, prC7data, ###5 Basics on Docker containers Linux Containers OS Virt OS Virtualization (LXC / Docker containers) – Applications in a Eone are isolated rom t*e ot*ers 2c*root on steroLds5 • Security 2as secure as your )ernel5 • Gamespaces 2root, <,?, G,?, net+or), P,?, ,PC, mount points, *ostnameButs5 • Cgroup Granularity • Single OS image manages HW accesses • Per ormance 6 transparency neit*er emulation nor ull !irtualiEation • Get ilter or net+ork isolation 2GA- and port +d5 • AuFS o!erlays isolated ile systems on top o a p*ysical ile system – Ot*er tec*nos a!aila&le • 17Ser!er • VirtuoEEo • Open1M *ttps;BB&log.doc)er#com/+p7contentBuploadsB"$'3B$4Bdoc)er7execdriver7diagram.png Docker In Brief • ision, Build, S*ip, and 0un Any App Any+*ere • Both, a company and an open source ecosystem 2under t*e Apac*e license 1"#$ since "$'45 • Docker is a tool chain written in Go t*at simpli ies t*e creation and management of containers# • Paradig% shi)t; Nne+” pac)aging model or deploying applications and services using Linux containers 2Google *as &een doing t*is or yearsP " &illion B +ee)5 • Containers, A sel 7contained porta&le en!ironment or pac)aging, deploying, and executing applications and services# Contains all execution dependencies or a service 2single process 7Q single container5 • alue prop • Better resource utili5ation, 1Ms !irtualiEe t*e CP<, – 0elia&le deployment containers !irtualiEe process2es5 (lightweight5 – More e:icient deployment • Si%pli)ied Application Li)ec(cle $anage%ent; – 0educed deployment latency – Build and con igure once 2integrated ?e!Ops5 – ?eploy any+*ere 2laptop, ser!er, cloud, R5 – More e:icient use o system resources – ,- ocuses on managing t*e &ase in rastructure 'hat is Docker value8add ? Goal: run applications in containers in a neutral, lightweig*t and porta&le +ay Bundle, E!erything pac)ed together La(ers; ,mages 2ro5 6 containers 2r+5 using a union FS "egistry; pu&lic/private registry of s*ared images Dockerfile; descriptive &uild of an image olumes; loop&ack mounting host FS into container Ports; expose container services port to the host Portable; created once, run e!erywhere 2Linux &ased5 $anagement; 0ES- AP,BCLI Solomon Hy)es, Doc)er Inc# A la(ered approach I%ages Local or remote re erence content to initiate a container Multiple images can be layered adding content at each time using Copy on Write FS Cache to speed up repeated operations Containers Last layer providing rw access to t*e cumulated set o images 1 application + its deps == 1 container Building packages with Docker 'h( building distribution packages with Containers vs V$s3 Container like V$s brings isolation Go pollution of your running environment Easily scratch and redo i problems Easier refinement & automation o t*e &uild environment with the Docker file Containers like V$s brings multi8distribution support Easy to build or anot*er distri&ution than yours <se ul also for your o+n distro: not e!erybody uses an unsta&le distro Containers can use nati&el( your ho%e director( Allo+ sharing of your pac)age sources for local and in container build Allo+ sharing of your .rpmmacros, .rpmrc files, Mageia SSH keys or Fedora certs $s are mandator( is you need a di9erent kernel Basic Docker workflow to build distribution packages Images Mageia Cauldron Mageia 5 ..
Load more

Recommended publications
  • Red Hat Enterprise Linux 8 Installing, Managing, and Removing User-Space Components
    Red Hat Enterprise Linux 8 Installing, managing, and removing user-space components An introduction to AppStream and BaseOS in Red Hat Enterprise Linux 8 Last Updated: 2021-06-25 Red Hat Enterprise Linux 8 Installing, managing, and removing user-space components An introduction to AppStream and BaseOS in Red Hat Enterprise Linux 8 Legal Notice Copyright © 2021 Red Hat, Inc. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/ . In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates. XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
    [Show full text]
  • Using the Mysql Yum Repository Abstract
    Using the MySQL Yum Repository Abstract This document provides some basic instructions for using the MySQL Yum Repository to install and upgrade MySQL. It is excerpted from the MySQL 5.6 Reference Manual. For legal information, see the Legal Notices. For help with using MySQL, please visit the MySQL Forums, where you can discuss your issues with other MySQL users. Document generated on: 2021-09-23 (revision: 70881) Table of Contents Preface and Legal Notices ............................................................................................................ v 1 Installing MySQL on Linux Using the MySQL Yum Repository ..................................................... 1 2 Replacing a Third-Party Distribution of MySQL Using the MySQL Yum Repository ........................ 5 3 Upgrading MySQL with the MySQL Yum Repository ................................................................... 9 iii iv Preface and Legal Notices This document provides some basic instructions for using the MySQL Yum Repository to install and upgrade MySQL. It is excerpted from the MySQL 5.6 Reference Manual. Licensing information—MySQL 5.6. This product may include third-party software, used under license. If you are using a Commercial release of MySQL 5.6, see the MySQL 5.6 Commercial Release License Information User Manual for licensing information, including licensing information relating to third-party software that may be included in this Commercial release. If you are using a Community release of MySQL 5.6, see the MySQL 5.6 Community Release License Information User Manual for licensing information, including licensing information relating to third-party software that may be included in this Community release. Licensing information—MySQL NDB Cluster 7.3. This product may include third-party software, used under license. If you are using a Commercial release of NDB Cluster 7.3, see the MySQL NDB Cluster 7.3 Commercial Release License Information User Manual for licensing information relating to third-party software that may be included in this Commercial release.
    [Show full text]
  • Linux at 25 PETERHISTORY H
    Linux at 25 PETERHISTORY H. SALUS Peter H. Salus is the author of A n June 1991, at the USENIX conference in Nashville, BSD NET-2 was Quarter Century of UNIX (1994), announced. Two months later, on August 25, Linus Torvalds announced Casting the Net (1995), and The his new operating system on comp.os.minix. Today, Android, Google’s Daemon, the Gnu and the Penguin I (2008). [email protected] version of Linux, is used on over two billion smartphones and other appli- ances. In this article, I provide some history about the early years of Linux. Linus was born into the Swedish minority of Finland (about 5% of the five million Finns). He was a “math guy” throughout his schooling. Early on, he “inherited” a Commodore VIC- 20 (released in June 1980) from his grandfather; in 1987 he spent his savings on a Sinclair QL (released in January 1984, the “Quantum Leap,” with a Motorola 68008 running at 7.5 MHz and 128 kB of RAM, was intended for small businesses and the serious hobbyist). It ran Q-DOS, and it was what got Linus involved: One of the things I hated about the QL was that it had a read-only operating system. You couldn’t change things ... I bought a new assembler ... and an editor.... Both ... worked fine, but they were on the microdrives and couldn’t be put on the EEPROM. So I wrote my own editor and assembler and used them for all my programming. Both were written in assembly language, which is incredibly stupid by today’s standards.
    [Show full text]
  • Ubuntu Unleashed 2013 Edition: Covering 12.10 and 13.04
    Matthew Helmke with Andrew Hudson and Paul Hudson Ubuntu UNLEASHED 2013 Edition 800 East 96th Street, Indianapolis, Indiana 46240 USA Ubuntu Unleashed 2013 Edition Editor-in-Chief Copyright © 2013 by Pearson Education, Inc. Mark Taub All rights reserved. No part of this book shall be reproduced, stored in a retrieval Acquisitions Editor system, or transmitted by any means, electronic, mechanical, photocopying, record- Debra Williams ing, or otherwise, without written permission from the publisher. No patent liability is assumed with respect to the use of the information contained herein. Although every Cauley precaution has been taken in the preparation of this book, the publisher and author Development Editor assume no responsibility for errors or omissions. Nor is any liability assumed for damages resulting from the use of the information contained herein. Michael Thurston ISBN-13: 978-0-672-33624-9 Managing Editor ISBN-10: 0-672-33624-3 Kristy Hart Project Editor The Library of Congress cataloging-in-publication data is on file. Jovana Shirley Printed in the United States of America Copy Editor First Printing December 2012 Charlotte Kughen Trademarks Indexer All terms mentioned in this book that are known to be trademarks or service marks have Angie Martin been appropriately capitalized. Sams Publishing cannot attest to the accuracy of this information. Use of a term in this book should not be regarded as affecting the validity Proofreader of any trademark or service mark. Language Logistics Warning and Disclaimer Technical Editors Every effort has been made to make this book as complete and as accurate as Chris Johnston possible, but no warranty or fitness is implied.
    [Show full text]
  • Managing Software with Yum
    Fedora Core 4 Managing software with yum Stuart Ellis Edited by Paul W. Frields Copyright © 2005 Red Hat, Inc. and others. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. The original authors of this document, and Red Hat, designate the Fedora Project as the "Attribution Party" for purposes of CC-BY-SA. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. For guidelines on the permitted uses of the Fedora trademarks, refer to https:// fedoraproject.org/wiki/Legal:Trademark_guidelines. Linux® is the registered trademark of Linus Torvalds in the United States and other countries. Java® is a registered trademark of Oracle and/or its affiliates. XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. All other trademarks are the property of their respective owners. 1. Introduction ............................................................................................................................. 2 1.1. Purpose ....................................................................................................................... 2 1.2. Audience ....................................................................................................................
    [Show full text]
  • Openbsd Gaming Resource
    OPENBSD GAMING RESOURCE A continually updated resource for playing video games on OpenBSD. Mr. Satterly Updated August 7, 2021 P11U17A3B8 III Title: OpenBSD Gaming Resource Author: Mr. Satterly Publisher: Mr. Satterly Date: Updated August 7, 2021 Copyright: Creative Commons Zero 1.0 Universal Email: [email protected] Website: https://MrSatterly.com/ Contents 1 Introduction1 2 Ways to play the games2 2.1 Base system........................ 2 2.2 Ports/Editors........................ 3 2.3 Ports/Emulators...................... 3 Arcade emulation..................... 4 Computer emulation................... 4 Game console emulation................. 4 Operating system emulation .............. 7 2.4 Ports/Games........................ 8 Game engines....................... 8 Interactive fiction..................... 9 2.5 Ports/Math......................... 10 2.6 Ports/Net.......................... 10 2.7 Ports/Shells ........................ 12 2.8 Ports/WWW ........................ 12 3 Notable games 14 3.1 Free games ........................ 14 A-I.............................. 14 J-R.............................. 22 S-Z.............................. 26 3.2 Non-free games...................... 31 4 Getting the games 33 4.1 Games............................ 33 5 Former ways to play games 37 6 What next? 38 Appendices 39 A Clones, models, and variants 39 Index 51 IV 1 Introduction I use this document to help organize my thoughts, files, and links on how to play games on OpenBSD. It helps me to remember what I have gone through while finding new games. The biggest reason to read or at least skim this document is because how can you search for something you do not know exists? I will show you ways to play games, what free and non-free games are available, and give links to help you get started on downloading them.
    [Show full text]
  • Red Hat Developer Toolset 9 User Guide
    Red Hat Developer Toolset 9 User Guide Installing and Using Red Hat Developer Toolset Last Updated: 2020-08-07 Red Hat Developer Toolset 9 User Guide Installing and Using Red Hat Developer Toolset Zuzana Zoubková Red Hat Customer Content Services Olga Tikhomirova Red Hat Customer Content Services [email protected] Supriya Takkhi Red Hat Customer Content Services Jaromír Hradílek Red Hat Customer Content Services Matt Newsome Red Hat Software Engineering Robert Krátký Red Hat Customer Content Services Vladimír Slávik Red Hat Customer Content Services Legal Notice Copyright © 2020 Red Hat, Inc. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/ . In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates. XFS ® is a trademark of Silicon Graphics International Corp.
    [Show full text]
  • Urpmi.Addmedia
    Todo lo que siempre quisiste saber sobre urpmi pero nunca te atreviste a preguntarlo Todo lo que siempre quisiste saber sobre urpmi pero nunca te atreviste a preguntarlo Traducido por Willy Walker de http://mandrake.vmlinuz.ca/bin/view/Main/UsingUrpmi Descargalo en PDF Otros recursos para aprender sobre urpmi Urpmi es una importante herramienta para todos los usuarios de Mandriva. Tomate tiempo para aprender utilizarlo. Esta página te da una descripción de las opciones más comúnmente usadas. Debajo están otros recursos con una información más detallada sobre urpmi: ● http://www.urpmi.org/ : Página de buena documentación de urpmi en Francés y en Inglés. ● Páginas man: comprueba las páginas man para todas las opciones. Ésas son la fuente más actualizada de información. Junto a una introducción muy básica, esta página intenta cubrir lo qué no se cubre en las dos fuentes antedichas de información. Asumimos que sabes utilizar una página man y que has leído la página antedicha. Una vez que lo hayas hecho así, vuelve a esta página: hay más información sobre problemas no tan obvios que puede no funcionarte. Usando urpmi Lista rápida de tareas comunes Comando Que te dice urpmq -i xxx.rpm Información del programa urpmq -il xxx.rpm Información y los archivos que instala urpmq --changelog xxx.rpm changelog (cambios) urpmq -R xxx.rpm Que requiere este rpm urpmf ruta/a/archivo Que rpm proporciona este archivo rpm -q --whatprovides ruta/a/ similar a urpmf, pero trabaja con ambos hdlist.cz y synthesis.hdlist.cz archivo urpmi.update updates Actualizaciones disponibles desde sus fuentes de actualización Actualizaciones disponibles desde todas las fuentes urpmi (puede urpmc necesitar urpmi a urpmc primero) urpmq --list-media Lista los repositorios que tienes Todo lo que siempre quisiste saber sobre urpmi pero nunca te atreviste a preguntarlo Comando Que hace urpme xxxx Elimina el rpm (y dependencias) Muestra todos los rpms que coinciden con esta cadena.
    [Show full text]
  • Continuous Control with a Combination of Supervised and Reinforcement Learning
    ORE Open Research Exeter TITLE Continuous Control with a Combination of Supervised and Reinforcement Learning AUTHORS Kangin, D; Pugeault, N JOURNAL Proceedings of the International Joint Conference on Neural Networks DEPOSITED IN ORE 23 April 2018 This version available at http://hdl.handle.net/10871/32566 COPYRIGHT AND REUSE Open Research Exeter makes this work available in accordance with publisher policies. A NOTE ON VERSIONS The version presented here may differ from the published version. If citing, you are advised to consult the published version for pagination, volume/issue and date of publication Continuous Control with a Combination of Supervised and Reinforcement Learning Dmitry Kangin and Nicolas Pugeault Computer Science Department, University of Exeter Exeter EX4 4QF, UK fd.kangin, [email protected] Abstract—Reinforcement learning methods have recently sures: for example, by the average speed, time for completing achieved impressive results on a wide range of control problems. a lap in a race, or other appropriate criteria. This situation is However, especially with complex inputs, they still require an the same for other control problems connected with robotics, extensive amount of training data in order to converge to a meaningful solution. This limits their applicability to complex including walking [9] and balancing [10] robots, as well as in input spaces such as video signals, and makes them impractical many others [11]. In these problems, also usually exist some for use in complex real world problems, including many of those criteria for assessment (for example, time spent to pass the for video based control. Supervised learning, on the contrary, is challenge), which would help to assess how desirable these capable of learning on a relatively limited number of samples, control actions are.
    [Show full text]
  • Secure and Private Sensing for Driver Authentication and Transportation Safety
    University Transportation Research Center - Region 2 Final Report Secure and Private Sensing for Driver Authentication and Transportation Safety Performing Organization: New York Institute of Technology August 2017 Sponsor: University Transportation Research Center - Region 2 University Transportation Research Center - Region 2 Project No(s): 49198-33-27 The Region 2 University Transportation Research Center (UTRC) is one of ten original University Transportation Centers established in 1987 by the U.S. Congress. These Centers were established UTRC/RF Grant No: with the recognition that transportation plays a key role in the nation's economy and the quality Project Date: of life of its citizens. University faculty members provide a critical link in resolving our national and regional transportation problems while training the professionals who address our transpor- Project Title: August 2017 tation systems and their customers on a daily basis. Authentication and Transportation Safety Secure and Private Sensing for Driver The UTRC was established in order to support research, education and the transfer of technology Project’s Website: in the �ield of transportation. The theme of the Center is "Planning and Managing Regional - Transportation Systems in a Changing World." Presently, under the direction of Dr. Camille Kamga, private-sensing-driver-authentication the UTRC represents USDOT Region II, including New York, New Jersey, Puerto Rico and the U.S. http://www.utrc2.org/research/projects/secure-and Virgin Islands. Functioning as a consortium of twelve major Universities throughout the region, UTRC is located at the CUNY Institute for Transportation Systems at The City College of New York, Principal Investigator(s): theme.the lead UTRC’s institution three of main the goalsconsortium.
    [Show full text]
  • Get Smart Get Smart
    KNOW-HOW Smart Package Manager The fast and sensible Smart package manager GETGET SMARTSMART The package manager is one of the central components on any Linux system. If you have a system with unre- liable package management – such as Suse Linux 10.1 – you may want to consider the Smart alternative. BY MARCEL HILZINGER he true test of a package manager important focus of the Smart project -- means for adding new package and re- is how the tool resolves depen- and an important reason why the Smart pository formats. Tdencies. Smart is one of the best developers believe their tool is different. package managers around for navigating When it comes to dependencies, Smart Installation through dependency issues. The Smart does not just use the easiest and most The easiest way to install Smart is to use package manager does not depend on obvious solution but actually weighs your existing package manager, assum- any specific distribution, and it can han- every possible option using a policy- ing you have an Internet connection. dle more than ten repository formats. based priority system. In some cases, the Ubuntu users can run the sudo apt-get Smart comes with the smart command “best” solution may depend upon the install smartpm command to install the line tool, the Smart shell (smart -shell), goal. For instance, if you are performing package from the Universe repository. and a graphical user interface (Figure 1), an upgrade, Smart may not choose the Users with Fedora Core 5 will find Smart which you can launch by entering smart most recent version of a package if an in- in the extras repository; just type yum --gui.
    [Show full text]
  • Ixchariot® Performance Endpoints
    IxChariot® Performance Endpoints Release 7.10 913-0951 Rev. A December 2009 Copyright © 2009 Ixia. All rights reserved. This publication may not be copied, in whole or in part, without Ixia’s consent. RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the U.S. Government is subject to the restrictions set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 and FAR 52.227- 19. Ixia, the Ixia logo, and all Ixia brand names and product names in this document are either trademarks or registered trademarks of Ixia in the United States and/or other countries. All other trademarks belong to their respective owners. The information herein is furnished for informational use only, is subject to change by Ixia without notice, and should not be con- strued as a commitment by Ixia. Ixia assumes no responsibility or liability for any errors or inaccuracies contained in this publica- tion. Corporate Ixia Worldwide Headquarters Web site: www.ixiacom.com Headquarters 26601 W. Agoura Rd. General: [email protected] Calabasas, CA 91302 Investor Relations: [email protected] USA Training: [email protected] +1 877 FOR IXIA (877 367 4942) Support: [email protected] +1 818 871 1800 (International) +1 818 595 2599 (FAX) +1 818 871 1805 For the online support form, go to: [email protected] http://www.ixiacom.com/support/inquiry/ EMEA Ixia Europe Limited Support: [email protected] One Globeside, Fieldhouse Lane +44 1628 405797 Marlow, SL7 1HZ For the online support form, go to: United
    [Show full text]