DOCSLIB.ORG

Get Smart Get Smart

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read 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. termediate version provides a better re- install smart to install. Readers with sult for the complete system. Smart algo- Suse Linux will need to add the Guru re- How Smart? rithms also consider efficiency factors, pository [2] as an installation source. The goal of the Smart project is to create choosing the combination of packages You can then install Smart with YaST. “smart and portable algorithms for solv- that leads to the fastest and most reliable The project page [1] has details on Smart ing adequately the problem of managing installation. repositories for other distributions. software upgrade and installation.” Smart can manage DEB, RPM, and To install from the source code, you There is a reason why this description Slackware packages, and Smart supports must have the developer packages for from the the Smart developers empha- APT, YUM, and URPMI repositories. The the RPM or Deb system and a number of sizes the algorithms. Algorithms are an Smart architecture even provides a Python packages. Once you have these 48 ISSUE 73 DECEMBER 2006 WWW.LINUX - MAGAZINE.COM Smart Package Manager KNOW-HOW line by entering smart channel --add. The box labeled “Smart Commands” gives you an example for Ubuntu 6.06. You select the required format in the dialog shown in Figure 3. This is typi- cally APT-DEB Repository for Ubuntu and RPM MetaData for Fedora Core and Suse Linux. The ability to manage YaST in- stallation sources was added in version 0.42. The RPM Installed Packages and DPKG Installed Packages entries tell Smart to parse the installed packages, and this gives the tool the ability to de- lete installed software. After opting for a format, enter the re- quired information in the Edit Channel dialog (Figure 4). As an Alias, select a short and intuitive name. You can add a more detailed description in the Name box. The Manual updates checkbox lets you specify whether Smart should parse Figure 1: The Smart GUI gives administrators a convenient search function. The URLs tab the channel when launched. If you en- additionally shows you the repository from which a package originated. able the checkbox, the tool will leave this step out for the current source. This in place, just enter make in the source party repositories, and very few lists are is useful for static package sources, such code directory to launch the build, then available. To add a new channel to the as RPM directories on CD, or for local re- become root and enter make install to GUI, select Edit | Channel | New, and positories. install the software. then opt for one of the five suggested Checking Disabled tells Smart not to After completing the install, you can methods at the next step (Figure 2). install any packages from this channel. opt to use the command line package To add a channel manually, select Pro- This is practical if you need to disable a manager, as in smart install amarok for vide Channel Information. To read the channel temporarily without removing example, or give the smart --gui com- RPM packages in a local directory, select the corresponding entry. The Removable mand to launch the front-end. The soft- the last item. The other three items read option tells Smart that the channel is lo- ware will also support combinations of existing channel information. The rest of cated on an external medium (CD/ DVD). the two. You need administrative privi- this article explains how to manually set If necessary, the package manager will leges to install or remove software. up a repository via Provide Channel In- then prompt you to insert the disk. formation. As an alternative, you can You can use the Priority value to Setting up Repositories add package sources in the command weight channels. The higher the value, Depending on your distribution and the the more likely it is that Smart will in- package provider, Smart may have a Smart Commands stall a package from this source. You can channel list that suits your needs. Chan- theoretically assign priorities between Install package smart install package nels in the Smart sense of the word are -100000 and 100000, although a two-fig- name> smart install /local/path/package any kind of package source or repository. ure value should be high enough in most name For example, the Suse packages from cases. Channels default to a priority of 0. Find package smart search package Guru [3] automatically set up channels Specify the download address in the name for Packman and Guru. Other distribu- Base URL box. An existing configuration tions do not make heavy use of third Update package list (run automatically file, such as source.list on Ubuntu/ prior to installation) smart update Debian, or yum.conf, is the best source Add channel smart channel --add of this information. Users with Fedora channel file smart channel --add Core will need to add entries such as Aliasname name="detailed description" $basearch (i386 for example). type=apt-deb distribution=dapper baseurl=http://archive.ubuntu.com/ ubuntu components="universe" Tip Manage mirror servers smart mirror It makes sense to assign highest priori- --add ftp://mainserver.url/path http:// ties to your distributor’s official package mirror.url/path/ smart mirror --show sources, rather than choosing a third- Figure 2: Smart gives you five different Set priorities smart channel --set party provider. This avoids issues methods of integrating a new package Aliasname priority=50 caused by mixing packages. source. WWW.LINUX - MAGAZINE.COM ISSUE 73 DECEMBER 2006 49 KNOW-HOW Smart Package Manager If you are familiar with Synaptic, you Tolerant Search should have no trouble using Smart. Clicking a box to the left of the package 01 kim:~ # apt-get install name tags the software for installation. realplay And you can click to select installed 02 Reading package list... done packages for deletion. Yellow stars tell 03 Creating dependency tree... you that updates are available for the done packages in question. Right-clicking 04 E: Couldn't find realplay drops down a menu with advanced func- package tions, such as reinstalling packages, pro- 05 tecting individual packages against up- dating (Lock this version), or setting 06 kim:~ # smart install realplay package priorities. 07 Loading cache... To install a package, click the cog- 08 Updating cache... wheel icon, select File | Execute Changes, ########### [100%] or press [Ctrl]+[C]. Smart will attempt a 09 ERROR!: 'realplay' does not parallel download of the selected pack- match a package: suggest: ages, accessing various mirrors to do so. 10 ERROR!: The tool remembers the fastest and most RealPlayer-10.0.7-10@i586 reliable mirrors and uses them by prefer- 11 Saving cache... ence for future downloads. To add a new mirror, select Edit | Mirror, select the Figure 3: Smart supports a large number of main server, and then click New. Check package instead. If Smart starts to down- package source formats. out the “Smart Commands” box to find grade packages, you can assume that out how to add mirrors. you have forgotten some priorities along The other fields depend on the se- the way. To remedy this, select Edit | lected format. The program will ask you Tips and Tricks Priorities in the GUI. for the Distribution and Components for Smart can also handle local packages. By default, Smart will delete down- Apt-Deb sources. After making changes, The smart install ~/*.rpm command in- loaded package archives after installa- make sure you quit Smart by selecting stalls all the RPM packages, as well as tion. If you would prefer to keep the ar- File | Quit. In our lab, the program some- the required channel files. in your home chives to reuse them, run the package times forgot about new channels if we directories. If you would like to convert manager at the command line, setting failed to do so. your sources.list into a Smart channel the -o remove-packages=false when you file, see the scripts at [4]. do. The downloaded packages will be Using Smart Priorities can be assigned to packages stored in /var/lib/smart/packages/, and You can press [Ctrl]+[F] or click the besides channels.
Load more

Recommended publications
  • 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]
  • Happy Birthday Linux
    25 Jahre Linux! Am Anfang war der Quellcode Entstehungsgeschichte und Werdegang von Linux Entwicklung und Diversifizierung der Distributionen Der Wert von Linux oder: „Wat nix kost, dat is och nix.“ Andreas Klein ORR 2016 1 Am Anfang war der Quellcode (70er) ● 1969, Ken Thompson u. Dennis Ritchie erstellen die erste Version von Unix in Assembler. ● Von 1969-1971 entwickeln sie gemeinsam die Programmiersprache B. ● Ab 1971 erweiterte in erster Linie Dennis Ritchie B, um weitere Elemente und nannte sie Anfangs NB (new B). ● 1973 waren die Erweiterungen soweit gediehen, das er die stark verbesserte Sprache C nannte (Brian W. Kernighan hat ebenfalls maßgeblich dazu beigetragen). //Unix=25 PCs ● Bis 1974 war das gesamte Betriebssystem UNIX vollständig in C implementiert und wurde mit einem C-Compiler kostenfrei an verschiedene Universitäten verteilt. ● 1978 wurden bereits über 600 Computer mit dem UNIX-Betriebssystemen betrieben. ● Das aufblühende Zeitalter der Computerisierung der 70er Jahre war geprägt vom regen und freien Austausch von Programmen und dessen zugrunde liegenden Ideen. Sinnvoller Weise tauschte man diese als Quellcode untereinander aus. ● 1979 wurde von AT&T die letzte UNIX-Version 7, mit freiem Quellcode veröffentlicht. Andreas Klein ORR 2016 2 Am Anfang war der Quellcode (80er) ● 1980 – 1983 AT&T sowie zahlreiche andere Unternehmen beginnen mit der Kommerzialisierung von UNIX, durch Koppelung an stark beschränkenden Lizenzen und Geheimhaltung des zugrunde liegenden Quelltextes. ● Richard Stallman kündigt am 27. September 1983 in den Newsgroups net.unix-wizards und net.usoft das GNU-Projekt an. ● Am 5. Januar 1984 begann Stallman offiziell mit der Arbeit am GNU-Projekt, nachdem er seine Stelle am MIT gekündigt hatte.
    [Show full text]
  • CIT 470: Advanced Network and System Administration Slide #1 CIT 470: Advanced Network and System Administration Slide #2
    Topics 1. The Problem of Software Installation 2. Package Management Systems CIT 470: Advanced Network and 3. Using RPM System Administration 4. Finding RPMs Package Management 5. Building RPMs CIT 470: Advanced Network and System Administration Slide #1 CIT 470: Advanced Network and System Administration Slide #2 Software Installation What’s the problem? 1. Customization What prerequisites does your software have? Select options like language. What prereqs do your prereq packages have? Select file set. How do you handle conflicts? What if two programs install/modify same file? 2. Install new files in appropriate locations. Does your install work on every type of computer? 3. Modify existing configuration files. How do you handle upgrades? 4. Make software available to user. What if user has customized configuration? Shell configuration (PATH, etc.) What if ownerships/permissions have changed? GUI configuration (menu, icons, etc.) What if user needs old and new versions? How do you uninstall software? CIT 470: Advanced Network and System Administration Slide #3 CIT 470: Advanced Network and System Administration Slide #4 Package Manager Features UNIX Package Management Systems • Build management. deb: Debian system uses dpkg and APT. • Dependency tracking. pkgadd: Solaris packaging system. • Querying. portage: Gentoo uses with emerge. • Reversibility. ports: BSD ports system. • Verification. RPM: Redhat packaging system. • Version control. tgz: Tarballs used by Slackware. CIT 470: Advanced Network and System Administration Slide #5 CIT 470: Advanced Network and System Administration Slide #6 1 RPM RPM Package Names RPM Package Manager <name>-<version>-<release>.<arch>.rpm – Originally stood for Red Hat Package Manager – Came with Red Hat Linux 2.0 in 1995.
    [Show full text]
  • Software Packages (Not Only) in Linux
    Software Packages (not only) in Linux Michal Hruˇseck´y openSUSE Team @ SUSE May 13, 2013 1 of 28 Introduction Who am I? • used to maintain build of distribution from OpenEmbedded • maintainer of MySQL packages in openSUSE/SLE • Gentoo developer ) package maintainer for past seven years for various distributions What is the talk about? • packaging and software packages - what, why and how 1 of 28 Software Packages - what and why 2 of 28 What is software package? • archive with files to be installed • metadata for package manager • most common are .rpm and .deb Usual metadata: • description • license • dependencies • extra installation instructions • checksums 2 of 28 Why do we need them? Convenience • easy installation • easy update • clean uninstall • easy distribution of software Security • avoid development tools on production machines • detect tempering 3 of 28 Life without packages • Get a tarball • Find out dependencies • Build and install dependencies • Build and install package itself ◦ ./configure --prefix=/usr --enable-this n --disable-that --with-lib=there ◦ make ◦ fix what is broken ◦ make install ◦ try it ◦ make uninstall ◦ clean up left-overs 4 of 28 Life with packages • pkg-manager install pkg • pkg-manager remove pkg 5 of 28 RPM 6 of 28 Basic information • one of the oldest in Linux world • created in 1997 for RedHat • used by various distributions ◦ RedHat/Fedora and derivates ◦ openSUSE/SLE, Mandriva/Mageia, Meego, . • several frontends to make operations easier ◦ yum - used by RedHat/Fedora and derivates ◦ zypper - used by openSUSE/SLE and Meego ◦ urpmi - used by Mandriva/Mageia 6 of 28 File format • 32 bytes lead (magic, rpm version, type of package, architecture) • signature • header ◦ name, version and release ◦ license ◦ summary ◦ description ◦ changelog ◦ requires and provides ◦ file list with rights, md5s and more • archive ◦ cpio, compressed by gzip, bzip2, xz, .
    [Show full text]
  • Ocrmypdf Documentation Release 11.0.1 James R. Barlow
    ocrmypdf Documentation Release 11.0.1 James R. Barlow 2020-08-18 Contents 1 Introduction 3 2 Release notes 7 3 Installing OCRmyPDF 41 4 PDF optimization 53 5 Installing additional language packs 55 6 Installing the JBIG2 encoder 57 7 Cookbook 59 8 OCRmyPDF Docker image 65 9 Advanced features 69 10 Batch processing 75 11 Performance 83 12 PDF security issues 85 13 Common error messages 89 14 Using the OCRmyPDF API 91 15 Plugins 95 16 API Reference 103 17 Contributing guidelines 109 18 Indices and tables 111 Python Module Index 113 Index 115 i ii ocrmypdf Documentation, Release 11.0.1 OCRmyPDF adds an optical charcter recognition (OCR) text layer to scanned PDF files, allowing them to be searched. PDF is the best format for storing and exchanging scanned documents. Unfortunately, PDFs can be difficult to modify. OCRmyPDF makes it easy to apply image processing and OCR to existing PDFs. Contents 1 ocrmypdf Documentation, Release 11.0.1 2 Contents CHAPTER 1 Introduction OCRmyPDF is a Python 3 application and library that adds OCR layers to PDFs. 1.1 About OCR Optical character recognition is technology that converts images of typed or handwritten text, such as in a scanned document, to computer text that can be selected, searched and copied. OCRmyPDF uses Tesseract, the best available open source OCR engine, to perform OCR. 1.2 About PDFs PDFs are page description files that attempts to preserve a layout exactly. They contain vector graphics that can contain raster objects such as scanned images. Because PDFs can contain multiple pages (unlike many image formats) and can contain fonts and text, it is a good formats for exchanging scanned documents.
    [Show full text]
  • Oracle VM Virtualbox User Manual
    Oracle VM VirtualBox R User Manual Version 4.0.26 c 2004-2014 Oracle Corporation http://www.virtualbox.org Contents 1 First steps 9 1.1 Why is virtualization useful?............................. 10 1.2 Some terminology................................... 10 1.3 Features overview................................... 11 1.4 Supported host operating systems.......................... 13 1.5 Installing VirtualBox and extension packs...................... 14 1.6 Starting VirtualBox.................................. 15 1.7 Creating your first virtual machine......................... 16 1.8 Running your virtual machine............................ 19 1.8.1 Starting a new VM for the first time.................... 19 1.8.2 Capturing and releasing keyboard and mouse.............. 19 1.8.3 Typing special characters.......................... 21 1.8.4 Changing removable media......................... 21 1.8.5 Resizing the machine’s window...................... 22 1.8.6 Saving the state of the machine...................... 22 1.9 Snapshots....................................... 23 1.9.1 Taking, restoring and deleting snapshots................. 23 1.9.2 Snapshot contents.............................. 25 1.10 Virtual machine configuration............................ 26 1.11 Removing virtual machines.............................. 26 1.12 Importing and exporting virtual machines..................... 26 1.13 Alternative front-ends................................. 28 2 Installation details 29 2.1 Installing on Windows hosts............................. 29 2.1.1
    [Show 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; –
    [Show full text]
  • A Look in the Mirror: Attacks on Package Managers
    See discussions, stats, and author profiles for this publication at: https://www.researchgate.net/publication/221609207 A look in the mirror: Attacks on package managers Conference Paper · January 2008 DOI: 10.1145/1455770.1455841 · Source: DBLP CITATIONS READS 18 107 4 authors, including: John H. Hartman The University of Arizona 61 PUBLICATIONS 1,992 CITATIONS SEE PROFILE Some of the authors of this publication are also working on these related projects: Diffuse optical imaging for breast-cancer detection View project All content following this page was uploaded by John H. Hartman on 05 February 2015. The user has requested enhancement of the downloaded file. A Look In the Mirror: Attacks on Package Managers Justin Cappos Justin Samuel Scott Baker John H. Hartman Department of Computer Science, University of Arizona Tucson, AZ 85721, U.S.A. {justin, jsamuel, bakers, jhh}@cs.arizona.edu ABSTRACT systems [1, 2, 3, 21, 22, 25, 26, 28, 31, 32]. Package managers This work studies the security of ten popular package man- provide a privileged, central mechanism for the management agers. These package managers use different security mech- of software on a computer system. As packages are installed anisms that provide varying levels of usability and resilience by the superuser (root), their security is essential to the to attack. We find that, despite their existing security mech- overall security of the computer. anisms, all of these package managers have vulnerabilities This paper evaluates the security of the eight most popu- that can be exploited by a man-in-the-middle or a malicious lar [9, 19] package managers in use on Linux: APT [1], APT- mirror.
    [Show full text]
  • Package Management Security
    Package Management Security Justin Cappos, Justin Samuel, Scott Baker, John H. Hartman University of Arizona Computer Science Department {justin, jsamuel, bakers, jhh}@cs.arizona.edu Abstract Package management is the task of determining which packages should be installed on a host and then downloading and installing those packages. This paper examines the popular package managers APT and YUM and presents nine feasible attacks on them. There are attacks that install malicious packages, deny users package updates, or cause the host to crash. This work identifies three rules of package management security: don’t trust the repository, the trusted entity with the most information should be the one who signs, and don’t install untrusted packages. The violation of these rules leads to the described vulnerabilities. Unfortunately, many of the flaws are architectural in nature, so repair requires more than patches to APT and YUM. While the rules of package management security argue that the design of existing package managers is insufficient, they do not prescribe how to provide security. This led to the development of three de- sign principles for building a secure package manager: selective trust delegation, customized repository views, and explicitly treating the repository as untrusted. These principles were used to construct a pack- age manager Stork which is not vulnerable to the attacks identified for YUM and APT. Stork has been in use for four years and has managed over half a million clients. 1 Introduction Package managers are a popular way to distribute software (bundled into archives called packages) for modern operating systems [4, 11, 37].
    [Show full text]
  • Introduction to Linux
    Introduction to Linux A Hands on Guide Machtelt Garrels CoreSequence.com <[email protected]> Version 1.8 Last updated 20030916 Edition Introduction to Linux Table of Contents Introduction.........................................................................................................................................................1 1. Why this guide?...................................................................................................................................1 2. Who should read this book?.................................................................................................................1 3. New versions of this guide...................................................................................................................1 4. Revision History..................................................................................................................................1 5. Contributions.......................................................................................................................................2 6. Feedback..............................................................................................................................................2 7. Copyright information.........................................................................................................................3 8. What do you need?...............................................................................................................................3 9. Conventions used
    [Show full text]
  • Tpos-14-Installerdesapplications.Pdf
    Système d' exploitation Sommaire Introduction.............................................................................................3 Objectif..........................................................................................................3 Manipulations.................................................................................................3 Installer des applications.........................................................................4 Introduction...................................................................................................4 Installation à partir d©une archive..................................................................4 Installer à partir d©un paquetage RPM...........................................................5 Installer à partir d©un paquetage DEB...........................................................6 Manipulations..........................................................................................7 1 Travaux Pratiques tpOS-14-InstallerDesApplications.odt ♦ 27/08/2010 rev.10 [email protected] Copyright 2010 tv <[email protected]> Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; with no Invariant Sections, with no Front-Cover Texts, and with no Back-Cover. You can obtain a copy of the GNU General Public License : write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307
    [Show full text]
  • Ansible Documentation Release 1.7
    Ansible Documentation Release 1.7 Ansible July 14, 2014 CONTENTS i ii CHAPTER ONE ABOUT ANSIBLE Welcome to the Ansible documentation! Ansible is an IT automation tool. It can configure systems, deploy software, and orchestrate more advanced IT tasks such as continuous deployments or zero downtime rolling updates. Ansible’s goals are foremost those of simplicity and maximum ease of use. It also has a strong focus on security and reliability, featuring a minimum of moving parts, usage of OpenSSH for transport (with an accelerated socket mode and pull modes as alternatives), and a language that is designed around auditability by humans – even those not familiar with the program. We believe simplicity is relevant to all sizes of environments and design for busy users of all types – whether this means developers, sysadmins, release engineers, IT managers, and everywhere in between. Ansible is appropriate for managing small setups with a handful of instances as well as enterprise environments with many thousands. Ansible manages machines in an agentless manner. There is never a question of how to upgrade remote daemons or the problem of not being able to manage systems because daemons are uninstalled. As OpenSSH is one of the most peer reviewed open source components, the security exposure of using the tool is greatly reduced. Ansible is decentralized – it relies on your existing OS credentials to control access to remote machines; if needed it can easily connect with Kerberos, LDAP, and other centralized authentication management systems. This documentation covers the current released version of Ansible (1.5.3) and also some development version features (1.6).
    [Show full text]