IBM Research Report

Total Page:16

File Type:pdf, Size:1020Kb

IBM Research Report RC25675 (WAT1803-107) March 29, 2018 Computer Science IBM Research Report ConfEx: An Analytics Framework for Text-Based Software Configurations in the Cloud Ozan Tuncer1, Nilton Bila2, Canturk Isci2, Ayse K. Coskun1 1Boston University Boston, MA 02215 USA 2IBM Research Division Thomas J. Watson Research Center P.O. Box 218 Yorktown Heights, NY 10598 USA Research Division Almaden – Austin – Beijing – Brazil – Cambridge – Dublin – Haifa – India – Kenya – Melbourne – T.J. Watson – Tokyo – Zurich ConfEx: An Analytics Framework for Text-based Software Configurations in the Cloud Ozan Tuncer Nilton Bila Canturk Isci Ayse K. Coskun Boston University IBM Research IBM Research Boston University Boston, MA 02215 Yorktown Heights, NY 10598 Yorktown Heights, NY 10598 Boston, MA 02215 Email: [email protected] Email: [email protected] Email: [email protected] Email: [email protected] Abstract—Modern cloud applications are designed in a highly Configurations are traditionally validated by applications configurable way to provide increased reusability and portability. during startup. However, recent work has shown that 14-93% With the growing complexity of these applications, configuration of configuration parameters in today’s cloud software do not errors (i.e., misconfigurations) have become major sources of service outages and disruptions. While some research has so far have any special code for checking their correctness during ap- focused on automatically detecting errors on configurations that plication initialization [11]. To detect misconfigurations before are represented as well-structured key-value pairs, discovering deployment, researchers have developed various tools to auto- and extracting configurations remain a challenge for a wide range matically check for errors in application configurations (e.g., of cloud applications that store their configurations in loosely- [12], [13]). Among such tools, statistical and learning-based structured text files. This paper proposes ConfEx, a framework that enables dis- techniques (e.g., [14], [15], [16]) have gained popularity as covery and analysis of text-based configurations in multi-tenant low overhead configuration checkers that can be applied in an cloud platforms and cloud image repositories. Our framework application-agnostic manner. Statistical configuration checkers uses a novel vocabulary-based discovery technique to identify train on a corpus of configurations and learn common patterns. text-based configuration files in cloud system instances with These methods can then identify configurations that deviate unlabeled content. We show that, even for labeled configuration files, widely-used and expert-maintained configuration parsing from the norm as potential errors. Such statistical methods tools lack the consistency and robustness needed for meaning- are powerful in practice because they do not require intrusive ful statistical analysis of configurations. We introduce a novel static/dynamic analysis or application instrumentation. disambiguation technique that resolves the inconsistencies in the In order to perform statistical and learning-based config- configuration-related data extracted by existing parsers. When uration analysis in multi-tenant cloud platforms, it is essen- tested on 4581 popular Docker Hub images, ConfEx achieves over 98% precision and recall in identifying configuration files, tial to extract configuration information from cloud system and consistently improves the efficacy of misconfiguration detec- instances (i.e., images, VMs, and containers) without losing tion through outlier analysis as well as syntactic configuration any information that is crucial for detecting errors. This validation. is challenging because cloud instance contents are largely unlabeled. One needs to discover which files are configuration I. INTRODUCTION files and also figure out to which applications these files be- Cloud software is complex and highly customizable. To long. Furthermore, cloud software configurations are typically function correctly, securely, and with high performance, cloud stored in loosely-structured text files where each software has applications often depend on precise tuning of hundreds of its own custom configuration syntax. For effective statistical configuration parameters [1]. In typical cloud services that analysis, the information extracted from these files needs to consist of multi-tiered software stacks, ensuring the desired be represented in a consistent format that allows comparison operation often requires correctly configuring thousands of of individual configuration parameters across a large number parameters [2]. of cloud instances. Errors in software configurations have been reported as In this work, we propose ConfEx, a novel software con- causes of service disruptions and outages at Facebook [3], figuration analytics framework that enables robust analysis LinkedIn [4], Microsoft Azure [5], Amazon EC2 [6], and of loosely-structured text-based configurations in multi-tenant Google [7]. Moreover, the affordability offered by the cloud cloud platforms and image repositories. ConfEx discovers and the prevalence of open-source software have enabled new configuration files of known applications in cloud instances levels of agility, where small teams of developers can deliver and parses these files to produce consistent configuration data new cloud services and functionality in short periods of time. for corpus-based analysis. We demonstrate two use cases of This newfound agility has led to a trend where service devel- ConfEx on a corpus of 4581 popular Docker Hub images: (1) opers and operators may lack the expertise needed to precisely detecting injected misconfigurations through outlier analysis tune all software components of a multi-tier architecture. As a and (2) syntactic configuration validation. Our contributions result, misconfigurations have become one of the lead causes can be summarized as follows: of cloud software failures [8], [9], [10]. • We design and implement ConfEx, a configuration an- TABLE I alytics framework that enables discovery and extraction COMMON CONFIGURATION ERROR TYPES AND EXAMPLE CONSTRAINTS of consistent configuration data and robust configuration THAT LEAD TO ERRORS UPON VIOLATION. analysis in multi-tenant cloud platforms. We demonstrate that ConfEx enables the use of existing configuration Error type Example configuration constraint analysis tools, which are designed for key-value pairs, In PostgreSQL, parameter values that are not simple with text-based software configurations in the cloud. Illegal entries identifiers or numbers must be single-quoted. • As part of our framework, we develop a vocabulary-based Variables must be in certain types (e.g., float). configuration file discovery technique to identify text- In PHP, mysql.max_persistent must be no based software configuration files in cloud instances with larger than the max_connections in MySQL. unlabeled content. Our approach can identify application Inconsistent In Cloudshare, service’s redis.host entry entries configuration files with over 98% precision and recall. (an IP address) must be a substring of Nginx’s • We show that the outputs of existing configuration file upstream.msg.server entry (IP address:port). parsers often lack the consistency and robustness needed Invalid When using PHP in Apache, recode.so must for statistical analysis, and introduce a disambiguation ordering be defined before mysql.so. technique for parser outputs to resolve this problem. In MySQL, maximum allowed table size must be The rest of this work starts with an overview of configura- smaller than the memory available in the system tion analysis and management techniques in the cloud. Sec. II Environmental inconsistency In httpd, Apache user permissions must be set provides a background on configuration files and common correctly to enable file uploads for website visitors. misconfigurations. Section III gives the details of our proposed ConfEx framework. Section IV explains our experimental Missing In OpenLDAP, a configuration entry must include parameter ppolicy.schema to enable password policy. methodology, and Section V presents our experimental find- MySQL’s Autocommit parameter must be set to ings. Finally, we conclude in Section VII. Valid entries False to avoid poor performance under “insert” that cause intensive workloads. II. BACKGROUND ON TEXT-BASED CONFIGURATIONS performance In this section, we explain how cloud applications and ser- or security Debug-level logging must be disabled to avoid issues performance degradation. vices typically store their configurations. Then, we categorize common configuration errors to give some insight on the type of information required for effective configuration analysis. statement. While parsing these lines, one needs to retain the A. Text-based Configurations relational information between the parameters defined within Most cloud applications and system services store their the conditional statement, indicating that User and Group configurations in human-readable text files or in configuration belong to the IfModule unixd_module section. stores such as etcd and Windows registry. We focus on text In some configuration files, the file schema is not embedded file based configurations as this type of storage is prevalent in the file itself and requires domain knowledge to understand. for many of the building blocks of cloud applications (e.g., One such example is the Linux filesystem configuration file MySQL, Nginx, and Redis). (/etc/fstab), which defines available filesystems and their Figure 1 shows a snippet from an Apache
Recommended publications
  • Configuration File Manipulation with Configuration Management Tools
    Configuration File Manipulation with Configuration Management Tools Student Paper for 185.307 Seminar aus Programmiersprachen, SS2016 Bernhard Denner, 0626746 Email: [email protected] Abstract—Manipulating and defining content of configuration popular CM-Tool in these days and offers a huge variety of files is one of the central tasks of configuration management configuration manipulation methods. But we will also take a tools. This is important to ensure a desired and correct behavior look at other CM-Tools to explore their view of configuration of computer systems. However, often considered very simple, this file handling. task can turn out to be very challenging. Configuration manage- ment tools provide different strategies for content manipulation In Section II an introduction will be given about CM- of files, hence an administrator should think twice to choose the Tools, examining which ones are established in the community best strategy for a specific task. This paper will explore different and how they work. Before we dive into file manipulation approaches of automatic configuration file manipulation with the strategies, Section III will give some introduction in configu- help of configuration management tools. We will take a close look at the configuration management tool Puppet, as is offers various ration stores. Section IV will describe different configuration different approaches to tackle content manipulation. We will also manipulation strategies of Puppet, whereas Section V will explore similarities and differences of approaches by comparing look at approaches of other CM-Tools. Section VI will show it with other configuration management tools. This should aid some scientific papers about CM-Tools.
    [Show full text]
  • Confex: a Framework for Automating Text-Based Software Configuration
    1 ConfEx: A Framework for Automating Text-based Software Configuration Analysis in the Cloud Ozan Tuncer, Anthony Byrne, Nilton Bila, Sastry Duri, Canturk Isci, and Ayse K. Coskun Abstract—Modern cloud services have complex architectures, often comprising many software components, and depend on hundreds of configurations parameters to function correctly, securely, and with high performance. Due to the prevalence of open-source software, developers can easily deploy services using third-party software without mastering the configurations of that software. As a result, configuration errors (i.e., misconfigurations) are among the leading causes of service disruptions and outages. While existing cloud automation tools ease the process of service deployment and management, support for detecting misconfigurations in the cloud has not been addressed thoroughly, likely due to the lack of frameworks suitable for consistent parsing of unstandardized configuration files. This paper introduces ConfEx, a framework that enables discovery and extraction of text-based software configurations in the cloud. ConfEx uses a novel vocabulary-based technique to identify configuration files in cloud system instances with unlabeled content. To extract the information in these files, ConfEx leverages existing configuration parsers and post-processes the extracted data for analysis. We show that ConfEx achieves over 99% precision and 100% recall in identifying configuration files on 7805 popular Docker Hub images. Using two applied examples, we demonstrate that ConfEx also enables detecting misconfigurations in the cloud via existing tools that are designed for configurations represented as key-value pairs, revealing 184 errors in public Docker Hub images. Index Terms—Software configuration, cloud, misconfiguration diagnosis. F 1 INTRODUCTION LOUD applications are designed in a highly config- Existing failure avoidance and mitigation mechanisms in C urable way to ensure high levels of reusability and the cloud (e.g., redundancy or recovery) are insufficient to portability.
    [Show full text]
  • Bidirectional Programming Languages
    University of Pennsylvania ScholarlyCommons Publicly Accessible Penn Dissertations Winter 2009 Bidirectional Programming Languages John Nathan Foster University of Pennsylvania, [email protected] Follow this and additional works at: https://repository.upenn.edu/edissertations Part of the Databases and Information Systems Commons, and the Programming Languages and Compilers Commons Recommended Citation Foster, John Nathan, "Bidirectional Programming Languages" (2009). Publicly Accessible Penn Dissertations. 56. https://repository.upenn.edu/edissertations/56 This paper is posted at ScholarlyCommons. https://repository.upenn.edu/edissertations/56 For more information, please contact [email protected]. Bidirectional Programming Languages Abstract The need to edit source data through a view arises in a host of applications across many different areas of computing. Unfortunately, few existing systems provide support for updatable views. In practice, when they are needed, updatable views are usually implemented using two separate programs: one that computes the view from the source and another that handles updates. This rudimentary design is tedious for programmers, difficult to reason about, and a nightmare to maintain. This dissertation presents bidirectional programming languages, which provide an elegant and effective mechanism for describing updatable views. Unlike programs written in an ordinary language, which only work in one direction, programs in a bidirectional language can be run both forwards and backwards: from left to right, they describe functions that map sources to views, and from right to left, they describe functions that map updated views back to updated sources. Besides eliminating redundancy, these languages can be designed to ensure correctness, guaranteeing by construction that the two functions work well together. Starting from the foundations, we define a general semantic space of well-behaved bidirectional transformations called lenses.
    [Show full text]
  • Zentrale Verwaltung Mit Facter, Puppet Und Augeas
    System-Management-Trio Zentrale Verwaltung mit facter, puppet und augeas Verwaltung mit facter, puppet und augeas © SpeedPartner GmbH Seite: 1 / 34 GUUG Frühjahrsfachgespräch, 01.03.2012 Über den Vortrag Aufbau / Ziele: ● Einführung / Überblick ● Begriffsklärung ● Aufbau / Arbeitsweise von Manifests ● Templates, Klassen, Typen, Module ● Facter: Umgebungsparameter ermitteln ● Augeas: Konfigurationen bearbeiten ● Client-Server-Betrieb ● Arbeit mit mehreren Umgebungen ● Links / Hilfen Verwaltung mit facter, puppet und augeas © SpeedPartner GmbH Seite: 2 / 34 GUUG Frühjahrsfachgespräch, 01.03.2012 Über mich ● Stefan Neufeind ● Mit-Geschäftsführer der SpeedPartner GmbH aus Neuss ein Internet-Service-Provider (ISP) ● Individuelle TYPO3-Entwicklungen ● Hosting, Housing, Managed Services ● Domains / Domain-Services ● IPv6, DNSSEC, ... ● Aktive Mitarbeit im Community-Umfeld (PHP/PEAR, TYPO3, Linux) ● Freier Autor für z.B. t3n, iX, Internet World, ... Verwaltung mit facter, puppet und augeas © SpeedPartner GmbH Seite: 3 / 34 GUUG Frühjahrsfachgespräch, 01.03.2012 Aufgabenstellung Alltägliche Administrationsaufgaben für ein (Server-)System Basisinstallation Fehler bei Ausführung von Zugänge „Standard-Aufgaben“? Backup Monitoring Fehlersuche / Einrichtung / Fehlerkorrektur Konzeptfehler? Konfiguration Netzwerk Fehler durch die Systemstatistiken „Sonderlösungen“? Architektur Virtuell? Individuelle Anpassungen Aufgaben RAID? Verwaltung mit facter, puppet und augeas © SpeedPartner GmbH Seite: 4 / 34 GUUG Frühjahrsfachgespräch, 01.03.2012 Aufgabenstellung
    [Show full text]
  • Rehearsal: a Configuration Verification Tool for Puppet
    Rehearsal: A Configuration Verification Tool for Puppet t* Rian Shambaugh Aaron Weiss Arjun Guha ac AE f Comp C i * let t nt e e * r t is W s University of Massachusetts Amherst, United States e n A l o l D C * * o * c I u e E s frian,aaronweiss,[email protected] m u D e e v n R L t e o a t d P y * s a E l u * a d t e Abstract 1. Introduction Large-scale data centers and cloud computing have turned Consider the role of a system administrator at any organi- system configuration into a challenging problem. Several zation, from a large company to a small computer science widely-publicized outages have been blamed not on soft- department. Their job is to maintain computing infrastruc- ware bugs, but on configuration bugs. To cope, thousands of ture for everyone else. When a new software system, such as organizations use system configuration languages to manage a Web service, needs to be deployed, it is their job to pro- their computing infrastructure. Of these, Puppet is the most vision new servers, configure the firewall, and ensure that widely used with thousands of paying customers and many data is automatically backed up. If the Web service receives more open-source users. The heart of Puppet is a domain- a sudden spike in traffic, they must quickly deploy additional specific language that describes the state of a system. Pup- machines to handle the load. When a security vulnerability pet already performs some basic static checks, but they only is disclosed, they must patch and restart machines if neces- prevent a narrow range of errors.
    [Show full text]
  • SM User Guide
    Oracle® Communications Tekelec Virtual Operating Environment Licensing Information User Manual Release 3.5 E93070-01 November 2017 Copyright ©2010, 2017 Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S.
    [Show full text]
  • Linuxtag 2012: System-Management-Trio Facter, Puppet Und Augeas
    System-Management-Trio Zentrale Verwaltung mit facter, puppet und augeas Verwaltung mit facter, puppet und augeas © SpeedPartner GmbH Seite: 1 / 33 LinuxTag, 23.05.2012 Über den Vortrag Aufbau / Ziele: ● Einführung / Überblick ● Begriffsklärung ● Aufbau / Arbeitsweise von Manifests ● Templates, Klassen, Typen, Module ● Facter: Umgebungsparameter ermitteln ● Augeas: Konfigurationen bearbeiten ● Client-Server-Betrieb ● Arbeit mit mehreren Umgebungen ● Links / Hilfen Verwaltung mit facter, puppet und augeas © SpeedPartner GmbH Seite: 2 / 33 LinuxTag, 23.05.2012 Über mich ● Stefan Neufeind ● Mit-Geschäftsführer der SpeedPartner GmbH aus Neuss ein Internet-Service-Provider (ISP) ● Individuelle TYPO3-Entwicklungen ● Hosting, Housing, Managed Services ● Domains / Domain-Services ● IPv6, DNSSEC, ... ● Aktive Mitarbeit im Community-Umfeld (PHP/PEAR, TYPO3, Linux) ● Freier Autor für z.B. t3n, iX, Internet World, ... Verwaltung mit facter, puppet und augeas © SpeedPartner GmbH Seite: 3 / 33 LinuxTag, 23.05.2012 Aufgabenstellung Alltägliche Administrationsaufgaben für ein (Server-)System Basisinstallation Fehler bei Ausführung von Zugänge „Standard-Aufgaben“? Backup Monitoring Fehlersuche / Einrichtung / Fehlerkorrektur Konzeptfehler? Konfiguration Netzwerk Fehler durch die Systemstatistiken „Sonderlösungen“? Architektur Virtuell? Individuelle Anpassungen Aufgaben RAID? Verwaltung mit facter, puppet und augeas © SpeedPartner GmbH Seite: 4 / 33 LinuxTag, 23.05.2012 Aufgabenstellung Herausforderungen bei Administration mehrerer Systeme ● Einsparungen
    [Show full text]
  • AUGEAS—A Configuration
    AUGEAS—a configuration API David Lutterkort Red Hat, Inc. [email protected] Abstract changing configuration files in a way that abstracts away the formatting details that are irrelevant to program- One of the many things that makes Linux configura- matic configuration changes. While formatting details tion management the minefield we all love is the lack may be irrelevant in this context, they are still impor- of a local configuration API. The main culprit for this tant, and AUGEAS goes through a lot of trouble to pre- situation, that configuration data is generally stored in serve comments, whitespace, etc. text files in a wide variety of formats, is both an impor- tant part of the Linux culture and valuable when humans Logic for configuration changes is embedded in many need to make configuration changes manually. tools, and the same logic is reinvented multiple times, often for no other reason than a difference in imple- AUGEAS provides a local configuration API that mentation language. As an example, Webmin [?] can presents configuration data as a tree. The tree is backed edit a wide variety of configuration files; that editing directly by the various config files as they exist today; logic, and the hard work for writing and maintaining it, modifications to the tree correspond directly to changes is of no use to other configuration tools like Puppet, in the underlying files. AUGEAS takes great care to pre- Bcfg2, or cfengine, since none of them is written in serve comments and other formatting details across edit- Perl. The prospect of reimplementing large parts of this ing operations.
    [Show full text]
  • NVIDIA Mellanox Onyx Software: End-User Agreement
    NVIDIA Mellanox Onyx Software: End-User Agreement NVIDIA Mellanox Onyx Software: End-User Agreement PLEASE READ THE FOLLOWING TERMS AND CONDITIONS OF THIS MELLANOX END USER LICENSE AGREEMENT (THIS "AGREEMENT") BEFORE INSTALLING OR USING THE NVDIA MELLANOX SOFTWARE. THE MELLANOX SOFTWARE, WHICH INCLUDES ALL COMPUTER SOFTWARE IN BINARY FORM THAT IS DELIVERED TO LICENSEE, GENERALLY DESCRIBED AS THE NVIDIA MELLANOX SWITCH ONYX SOFTWARE, AND ALL INTELLECTUAL PROPERTY RIGHTS THEREIN OR THERETO AND ANY ASSOCIATED MEDIA AND PRINTED MATERIALS, AND ANY "ONLINE" OR ELECTRONIC DOCUMENTATION, IS REFERRED TO HEREIN AS THE "SOFTWARE". INSTALLATION OR USAGE OF THE SOFTWARE INDICATES YOUR ACCEPTANCE OF THE TERMS OF THIS AGREEMENT, AND CREATES A LEGAL AND BINDING AGREEMENT BETWEEN YOU (EITHER AN INDIVIDUAL OR AN ENTITY) ("YOU" OR "LICENSEE") AND MELLANOX TECHNOLOGIES LTD. AND ITS AFFILIATES ("MELLANOX"). IF YOU DO NOT AGREE WITH THE TERMS AND CONDITIONS OF THIS AGREEMENT, YOU SHALL NOT USE OR COPY THIS SOFTWARE PRODUCT AND YOU MUST PROMPTLY RETURN THIS PACKAGE TO MELLANOX. 1 General Each copy of the Software is intended for use only in conjunction with NVIDIA Mellanox's managed switch products ("Mellanox Products") and is subject to the terms of this Agreement. 2 Grant of License Subject to the terms and conditions of this Agreement, Mellanox grants you a personal, non-exclusive, non- transferable license to use the Software in binary form for your internal business purposes solely in connection with Mellanox Products and not for further distribution. 2.1 Archive. You may use software back-up utilities to make one back-up copy of the Software Product.
    [Show full text]
  • Continuous Delivery of Continuous Delivery
    CONTINUOUS DELIVERY OF CONTINUOUS DELIVERY Gerd Aschemann TUTORIAL / SCHULUNG Gerd Aschemann [email protected] http://aschemann.net twitter: @GerdAschemann Slack: https://jvm­german.slack.com/ (Channel: #build- systems) AGENDA Vagrant-Setup! Stufe 0: Motivation/Setup/Architektur… (45 Min) Stufe 1: Von der eigenen VagrantBox zum Build-Server und zurück (60 + 30 Min) Stufe 2: Aufbau Jenkins (60 Minuten) Stufe 3: Automatisierung Jobs (90 Minuten) Stufe 4: Miniprojekt mit SCM-Manager und Maven Release (60 Minuten) Abschluß: Diskussion/Kleinere Ergänzungen/Ausblick/Feedback (15 Minuten) Ein großer Teil der Umsetzung wird im Laufe des Tutorials als Git- Repository bereitgestellt! MOTIVATION Einführung/Vorstellungsrunde, 10 Min.) Setup (Vagrant, 10 Min.) Continuous Delivery (5 Min.) Architektur (20 Min.) SETUP (VAGRANT + VIRTUALBOX) Details folgen später! Vagrant Install Vagrant Init Vagrant Start Vagrant SSH Vagrant Destroy VAGRANT INSTALL Download (Vagrant + VirtualBox) + Installation gemäß Anleitung(en) https://www.vagrantup.com/downloads.html https://www.virtualbox.org/wiki/Downloads Alternative: Installation über Package Manager Debian/Ubuntu: [sudo] apt-get install vagrant virtualbox VAGRANT INIT Arbeitsverzeichnis anlegen, z.B. demo, und Vagrant initialisieren $ mkdir demo $ cd demo $ vagrant init -f bento/ubuntu-16.04 lädt Image und erzeugt eine Datei Vagrantfile # -*- mode: ruby -*- # vi: set ft=ruby : # All Vagrant configuration is done below. The "2" in Vagrant.configure ... Vagrant.configure(2) do |config| # ... config.vm.box = "bento/ubuntu-16.04" ... VAGRANT START Vagrant wird gestartet mit $ vagrant up Erzeugt zahlreiche Ausgaben: Bringing machine 'default' up with 'virtualbox' provider... ==> default: Importing base box 'bento/ubuntu-16.04'... ... ==> default: Machine booted and ready! ==> default: Checking for guest additions in VM... ... ==> default: Mounting shared folders..
    [Show full text]
  • Xutools: Unix Commands for Processing Next-Generation Structured Text
    Submitted for publication. Author Copy - do not redistribute. XUTools: Unix Commands for Processing Next-Generation Structured Text Gabriel A. Weaver Sean W. Smith Dartmouth College Dartmouth College Keywords: Text processing, Configuration Management, de meaningful structures via nested blocks. Natural- Change Management, Automation, Tools, Unix language documents may be divided up into chapters, paragraphs, and sentences. Sentences themselves may be Abstract further parsed. Configuration files and programming lan- guages, similarly, may be divided up into blocks of code. Traditional Unix tools operate on sequences of chara- For example, Cisco IOS interface blocks or C function cters, bytes, fields, lines, and files. However, modern blocks are information units that network administrators practitioners often want to manipulate files in terms of and developers reference daily. a variety of language-specific constructs—C functions, The prevalence of multi-line, nested-block-structured Cisco IOS interface blocks, and XML elements, to na- formats has left a capability gap for traditional tools. To- me a few. These language-specific structures quite often day, if practitioners want to extract interfaces from a Ci- lie beyond the regular languages upon which Unix text- sco IOS router configuration file, they must craft an invo- processing tools can practically compute. In this paper, cation for sed(1) we propose eXtended Unix text-processing tools (xuto- sed -n ’/ˆinterface ols) and present implementations that enable practitio- ATM0/,/ˆ!/\{/ˆ\!d;p;\}’ ners to extract (xugrep), count (xuwc), and compare (xudiff) texts in terms of language-specific structures. Using our xutools, practitioners need only type We motivate, design, and evaluate our tools around real- world use cases from network and system administrators, xugrep ’//ios:interface’ security consultants, and software engineers from a va- We designed and built eXtended Unix text-processing riety of domains including the power grid, healthcare, tools (xutools) so that practitioners could process files in and education.
    [Show full text]
  • Building Pipelines at Scale
    Jenkins User Conference Europe . Building Pipelines at Scale Julien Pivotto inuits.eu 25th June 2014 #jenkinsconf . Jenkins User Conference Europe . Building Pipelines at Scale . Introduction Who’s who Pipelines Puppet Why How Conclusion Plugins Why How Conclusion #jenkinsconf . Jenkins User Conference Europe . #jenkinsconf Julien Pivotto . Open-Source Consultant at inuits.eu Linux Systems Administrator FOSS Defender for many years DevOps Puppet user since 2011 Doing also some Ruby & Python Introduction/Who’s who . Jenkins User Conference Europe . #jenkinsconf inuits . Open-Source Consultancy company 50+ people in 4 countries (.be, .ua, .nl & .cz) Doing both Development & Systems Administration A lot of domains: Linux, Web, Databases, Monitoring… Early DevOps practitioners Introduction/Who’s who . Jenkins User Conference Europe . #jenkinsconf MediaMosa . Drupal-based Digital Asset Management system Open-source Store assets Transcode videos Create, extract and manage metadata using open standards: Dublin Core, Qualified DC, IEEE/LOM, CZP Webservice oriented Introduction/Who’s who . Jenkins User Conference Europe . #jenkinsconf MediaSalsa: MediaMosa As a Service . A turn-key MediaMosa solution A few environments: Dev/Uat/Prod environments Customer-specific environments One backend per environment Multiple frontends per backend = A lot of Drupal sites Introduction/Who’s who . Pipeline vs large (or independent) jobs: Separation between different tasks Overview of tests, etc… Deployment depends on testing Jenkins User Conference Europe . #jenkinsconf Definition of pipelines . A pipeline is a chain of Jenkins jobs that are run to fetch, compile, package, run tests and deploy an application (build pipeline plugin). Introduction/Pipelines . Jenkins User Conference Europe . #jenkinsconf Definition of pipelines . A pipeline is a chain of Jenkins jobs that are run to fetch, compile, package, run tests and deploy an application (build pipeline plugin).
    [Show full text]