DOCSLIB.ORG

Rudder 4.1 - User Manual I

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Rudder 4.1 - User Manual I Rudder 4.1 - User Manual i Rudder 4.1 - User Manual Rudder 4.1 - User Manual ii Copyright © 2011-2016 Normation SAS Rudder User Documentation by Normation is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License. Permissions beyond the scope of this license may be available at normation.com. Rudder 4.1 - User Manual iii COLLABORATORS TITLE : Rudder 4.1 - User Manual ACTION NAME DATE SIGNATURE WRITTEN BY Jonathan Clarke, Sep 2016 Nicolas Charles, Fabrice Flore-Thebault, Matthieu Cerda, Nicolas Perron, Arthur Anglade, Vincent Membré, and François Armand REVISION HISTORY NUMBER DATE DESCRIPTION NAME 4.1 Sep 2016 N Rudder 4.1 - User Manual iv Contents 1 Online version 1 2 Introduction 2 2.1 What is Rudder? . .2 2.1.1 Made for production environments . .3 2.1.2 Different roles for a better accessibility . .4 2.1.3 Universality . .5 2.2 Key Features . .6 2.2.1 OS independent target configuration state definition . .6 2.2.2 Centralize and aggregate real configuration states . .7 2.2.3 Automatic inventory . .8 2.2.4 REST API . .8 2.2.5 Audit trace and Change Requests . .8 2.2.6 Centralized authentication (LDAP, Active Directory, plugins) . .9 2.2.7 Extensibilty . 10 2.3 Technical architecture and software dependencies . 11 2.3.1 Functional architecture of Rudder . 11 2.3.2 Network architecture in client/server mode . 12 2.3.3 Agents . 13 3 Installation 14 3.1 Quick installation . 14 3.2 Requirements . 15 3.2.1 Networking . 15 3.2.1.1 Mandatory flows . 15 3.2.1.2 Optional flows . 15 3.2.1.3 DNS - Name resolution . 15 3.2.2 Fully supported Operating Systems . 15 3.2.2.1 For Rudder Nodes . 16 3.2.2.2 For Rudder Root Server . 16 3.2.3 Partially supported Operating Systems . 16 Rudder 4.1 - User Manual v 3.2.3.1 For Rudder Nodes . 17 3.2.3.2 For Rudder Root Server . 17 3.2.4 Cloud compatibility . 17 3.2.5 Hardware specifications for Rudder Agent . 17 3.2.6 Hardware specifications and sizing for Rudder Root Server . 17 3.2.6.1 Memory . 18 3.2.6.2 Disk . 18 3.3 Install Rudder Server . 18 3.3.1 Install Rudder Root server on Debian or Ubuntu . 19 3.3.1.1 Add the Rudder packages repository . 19 3.3.1.2 Install your Rudder Root Server . 20 3.3.2 Initial configuration of your Rudder Root Server . 20 3.3.3 Validate the installation . 20 3.3.4 Install Rudder Root server on SLES . 20 3.3.4.1 Configure the package manager . 20 3.3.4.2 Add the Rudder packages repository . 21 3.3.4.3 Install your Rudder Root Server . 21 3.3.5 Initial configuration of your Rudder Root Server . 22 3.3.6 Validate the installation . 22 3.3.7 Install Rudder Root server on RHEL-like systems . 22 3.3.7.1 Add the Rudder packages repository . 22 3.3.7.2 Install your Rudder Root Server . 23 3.3.8 Initial configuration of your Rudder Root Server . 23 3.3.9 Validate the installation . 24 3.4 Install Rudder Agent . 24 3.4.1 Install Rudder Agent on Debian or Ubuntu . 24 3.4.2 Install Rudder Agent on RHEL-like systems . 25 3.4.3 Install Rudder Agent on SLES . 26 3.4.4 Configure and validate . 27 3.4.4.1 Configure Rudder Agent . 27 3.4.4.2 Validate new Node . 27 3.5 Install Rudder Relay (optional) . 27 3.5.1 On the relay . 28 3.5.2 On the root server . 28 3.5.3 Validation . 28 3.5.4 Adding nodes to a relay server . 29 Rudder 4.1 - User Manual vi 4 Upgrade 30 4.1 Upgrade notes . 30 4.1.1 Upgrade from Rudder 3.0 or older . 30 4.1.2 Upgrade from Rudder 3.1, 3.2 or 4.0 . 30 4.1.3 Compatibility between Rudder agent 4.1 and older server versions . 31 4.1.3.1 4.0.x servers . 31 4.1.3.2 3.1.x and 3.2.x servers . 31 4.1.4 Compatibility between Rudder server 4.1 and older agent versions . 31 4.1.4.1 4.0.x agents . 31 4.1.4.2 3.1.x and 3.2.x agents . 31 4.1.4.3 3.0.x or older . 31 4.1.5 Protocol for reporting . 31 4.1.6 Upgrade manually installed relays (installed before 3.0) . 32 4.1.7 Known issues . 32 4.2 On Debian or Ubuntu . 32 4.3 On RHEL or CentOS . ..
Load more

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]
  • Guide to Open Source Solutions
    White paper ___________________________ Guide to open source solutions “Guide to open source by Smile ” Page 2 PREAMBLE SMILE Smile is a company of engineers specialising in the implementing of open source solutions OM and the integrating of systems relying on open source. Smile is member of APRIL, the C . association for the promotion and defence of free software, Alliance Libre, PLOSS, and PLOSS RA, which are regional cluster associations of free software companies. OSS Smile has 600 throughout the World which makes it the largest company in Europe - specialising in open source. Since approximately 2000, Smile has been actively supervising developments in technology which enables it to discover the most promising open source products, to qualify and assess them so as to offer its clients the most accomplished, robust and sustainable products. SMILE . This approach has led to a range of white papers covering various fields of application: Content management (2004), portals (2005), business intelligence (2006), PHP frameworks (2007), virtualisation (2007), and electronic document management (2008), as well as PGIs/ERPs (2008). Among the works published in 2009, we would also cite “open source VPN’s”, “Firewall open source flow control”, and “Middleware”, within the framework of the WWW “System and Infrastructure” collection. Each of these works presents a selection of best open source solutions for the domain in question, their respective qualities as well as operational feedback. As open source solutions continue to acquire new domains, Smile will be there to help its clients benefit from these in a risk-free way. Smile is present in the European IT landscape as the integration architect of choice to support the largest companies in the adoption of the best open source solutions.
    [Show full text]
  • A System Engineer's Guide to Host Configuration and Maintenance
    0001.cover_er:cee 5/18/07 12:03 PM Pe 1 THE USENIX SIG FOR Short Topics in 1 6 16 System Administration M Jane-Ellen Long, Series Editor a r k B SYSADMINS u r g e s s & A System Engineer’s Guide to Æ l e e n Host Configuration and F r i s c h Maintenance Using Cfengine A Mark Burgess and S y s Æleen Frisch t e m E n g i n e e r ’ s G u i d e t o C f e n g i n e ISBN-13: 978-19319715221492 ISBN-10: 1931971528498 9 0 0 0 0 THE USENIX SIG FOR SYSADMINS 9 781931 97154292 Short Topics in 16 System Administration Jane-Ellen Long, Series Editor A System Engineer’s Guide to Host Configuration and Maintenance Using Cfengine Mark Burgess and Æleen Frisch Published by the USENIX Association 2007 About SAGE SAGE is a Special Interest Group of the USENIX Association. Its goal is to serve the system administration community by: I Offering conferences and training to enhance the technical and managerial capabilities of members of the profession I Promoting activities that advance the state of the art or the community I Providing tools, information, and services to assist system administrators and their organizations I Establishing standards of professional excellence and recognizing those who attain them SAGE offers its members professional and technical information through a variety of programs. Please see http://www.sage.org for more information. © Copyright 2007 by the USENIX Association. All rights reserved.
    [Show full text]
  • Devops Interview Questions
    By OnlineInterviewQuestions.com Devops Interview Questions What is DevOps? DevOps is a one-stop solution for all software engineering. From creating the software to implementing it in real-time, DevOps does all. This creates an infinite demand for excellent DevOps developers in the market. Since the platform is quite fast and effective, it is attracting the attention of many organizations that are looking to develop a software solution for their own business. Thus, here are a few DevOps interview questions that can help you crack an interview in your dream organization and grow your career. Q1. What is DevOps ? DevOps is the term derived from Development and Operations. It is used in software engineering culture. It helps to perform the software operations and software developments. It provides a step-by-step process of software development. DevOps gives the clear process of software creation, testing, implementation and much more. It enhances the development frequency, makes short development cycle, and other for business activities. Q2. What are the advantages of DevOps ? There are various advantages that are offered by DevOps platform. The people gain many advantages with it. It reduces the risk of the problem and provides the possible solution in a simple way. It is more stable in the operating environments. It produces standard software delivery and adds value to the business. Q3. What are the anti-patterns of DevOps ? The pattern is the common practice followed by the organization. When others commonly adopt a pattern, it does not work for your business if you blindly follow it. Thus, it is necessary to look for anti-pattern.
    [Show full text]
  • Because Sustainability
    Change Making Simplified Addressing technology- business transformation in the COVID-era Contents Foreword 03 Thriving on Data 36 Applying TechnoVision 73 Leveraging data and algorithms as an asset to Introduction 04 increase the "Corporate IQ". A Few More Things 84 TechnoVision and COVID-19 06 Process on the Fly 43 TechnoVision 2020 Team 88 Building, managing, and running processes that Simplify 11 match the dynamics of the digital outside world. About Capgemini 90 You Experience 50 Being Architects of Positive Futures 15 Creating seamless user experiences for decisive, Overview of TechnoVision 18 magical moments. We Collaborate 57 Invisible Infostructure 22 Tapping into the power of the connected and Evolving the IT Infrastructure into the simple, collaborative "everything". pluggable utility it was always supposed to be. Design for Digital 64 Applications Unleashed 29 Overarching design principles to be followed and Liberating the legacy application landscape and checked throughout the journey of becoming a unleashing the next generation of powerful, agile, Technology Business. cloud-based apps. Invisible Infostructure Applications Unleashed Thriving on Data Process on the Fly You Experience We Collaborate Design for Digital Applying TechnoVision Special Foreword Patrick Nicolet Group Executive Board Member and Group CTO “Future Thinking, Change Making” businesses to operate, retailers to sell and companies to deliver. While The theme of this edition is ‘Simplify’ because, in a world where data the value of traditional ‘safe’ commodities has dropped exponentially, seems to overwhelm us all, we recognize that technology should It’s a sobering thought that, only a few months ago, when we were the popularity of technology and technological companies has soared aim to make the lives of consumers, colleagues and citizens easier.
    [Show full text]
  • Fujitsu and Red Hat's Integrated Solution to Enable Hybrid Cloud and Digital Transformation
    IDC Partner Spotlight Sponsored by: Red Hat Authors: Michael Ceroici Archana Venkatraman Fujitsu and Red Hat's Integrated Solution to Enable Hybrid Cloud and Digital Transformation January 2020 IDC Opinion Digital Transformation (DX) is crucial for survival in an age when customer experiences can make or break brands. Enterprises are executing on digital business initiatives to enhance customer insights, improve business processes or launch new services – all with an aim to improve customer satisfaction. DX strategy must be supported with a mature, agnostic, software-defined yet hardware-assisted and agile infrastructure. Such a future-ready architecture will not just make DX initiatives cost-effective and reliable, but also help enterprises limit the risks of proprietary lock-in and give them the flexibility to move data and applications as their business or governance needs demand. In our opinion, integrated systems, particularly with an open source ethos, can help enterprises to build a hybrid cloud and eliminate many complexities through a single support contract and a validated, unified infrastructure. Already, Linux and an accompanying stack of open source infrastructure software is emerging as the future of compute infrastructure, particularly for public cloud (growing at 13.9% CAGR to 2020). Most of the hyperscale datacenters or the largest public cloud infrastructure are built on a foundation of Linux. At the same time, paid Linux is steadily gaining a foothold in commercial accounts. Linux is becoming the de facto standard for a substantial portion — potentially the majority — of cloud native applications that will be built in the next decade. We believe that integrated, software-defined cloud solutions with mature open source integration will further grow in popularity as a foundation for DX.
    [Show full text]
  • Cfengine V2 Reference Edition 2.2.10 for Version 2.2.10
    cfengine v2 reference Edition 2.2.10 for version 2.2.10 Mark Burgess Faculty of Engineering, Oslo University College, Norway Copyright c 2008 Mark Burgess This manual corresponds to CFENGINE Edition 2.2.10 for version 2.2.10 as last updated 21 January 2009. Chapter 1: Introduction to reference manual 1 1 Introduction to reference manual The purpose of the cfengine reference manual is to collect together and document the raw facts about the different components of cfengine. Once you have become proficient in the use of cfengine, you will no longer have need of the tutorial. The reference manual, on the other hand, changes with each version of cfengine. You will be able to use it online, or in printed form to find out the details you require to implement configurations in practice. 1.1 Installation In order to install cfengine, you should first ensure that the following packages are installed. OpenSSL Open source Secure Sockets Layer for encryption. URL: http://www.openssl.org BerkeleyDB (version 3.2 or later) Light-weight flat-file database system. URL: http://www.oracle.com/technology/products/berkeley-db/index.html The preferred method of installation is then tar zxf cfengine-x.x.x.tar.gz cd cfengine-x.x.x ./configure make make install This results in binaries being installed in `/usr/local/sbin'. Since this is not necessarily a local file system on all hosts, users are encouraged to keep local copies of the binaries on each host, inside the cfengine trusted work directory. 1.2 Work directory In order to achieve the desired simplifications, it was decided to reserve a private work area for the cfengine tool-set.
    [Show full text]
  • Infrastructure As Code Handbook
    THE INFRASTRUCTURE AS CODE HANDBOOK Best practices, tools, and AWS CloudFormation scripts you can use to implement IaC for your organization www.thorntech.com Copyright © 2018 | THORN TECHNOLOGIES All Rights Reserved. No part of this publication may be reproduced, stored in a retrieval system or transmitted in any form or by any means, electronic, mechanical, photocopying, recording or otherwise, without the prior written permission of the publisher. THE INFRASTRUCTURE AS CODE HANDBOOK Contents 1 FIVE REASONS WHY YOU SHOULD IMPLEMENT INFRASTRUCTURE AS CODE NOW 2 SIX BEST PRACTICES TO GET THE MOST OUT OF IAC 3 FIFTEEN IAC TOOLS YOU CAN USE TO AUTOMATE YOUR DEPLOYMENTS 4 WHAT IS AWS CLOUDFORMATION AND HOW CAN IT HELP YOUR IAC EFFORTS? 5 HOW AWS CLOUDFORMATION WORKS AND HOW TO CREATE A VIRTUAL PRIVATE CLOUD WITH IT 6 HOW TO INCORPORATE S3, EC2, AND IAM IN A CLOUDFORMATION TEMPLATE 7 HOW TO CREATE A REDSHIFT STACK WITH AWS CLOUDFORMATION 3 www.thorntech.com [email protected] THE INFRASTRUCTURE AS CODE HANDBOOK 5 reasons why you should implement infrastructure as code now INFRASTRUCTURE AS CODE CAN HELP AVOID CLOUD DEPLOYMENT INCONSISTENCIES, INCREASE DEVELOPER PRODUCTIVITY, AND LOWER COSTS There’s no doubt that cloud computing has had a major impact on how companies build, scale, and maintain technology products. The ability to click a few buttons to provision servers, databases, and other infrastructure has led to an increase in developer productivity we’ve never seen before. While it’s easy to spin up simple cloud architectures, mistakes can easily be made provisioning complex ones. Human error will always be present, especially when you can launch cloud infrastructure by clicking buttons on a web app.
    [Show full text]
  • 27Th Large Installation System Administration Conference (LISA '13)
    conference proceedings Proceedings of the 27th Large Installation System Administration Conference 27th Large Installation System Administration Conference (LISA ’13) Washington, D.C., USA November 3–8, 2013 Washington, D.C., USA November 3–8, 2013 Sponsored by In cooperation with LOPSA Thanks to Our LISA ’13 Sponsors Thanks to Our USENIX and LISA SIG Supporters Gold Sponsors USENIX Patrons Google InfoSys Microsoft Research NetApp VMware USENIX Benefactors Akamai EMC Hewlett-Packard Linux Journal Linux Pro Magazine Puppet Labs Silver Sponsors USENIX and LISA SIG Partners Cambridge Computer Google USENIX Partners Bronze Sponsors Meraki Nutanix Media Sponsors and Industry Partners ACM Queue IEEE Security & Privacy LXer ADMIN IEEE Software No Starch Press CiSE InfoSec News O’Reilly Media Computer IT/Dev Connections Open Source Data Center Conference Distributed Management Task Force IT Professional (OSDC) (DMTF) Linux Foundation Server Fault Free Software Magazine Linux Journal The Data Center Journal HPCwire Linux Pro Magazine Userfriendly.org IEEE Pervasive © 2013 by The USENIX Association All Rights Reserved This volume is published as a collective work. Rights to individual papers remain with the author or the author’s employer. Permission is granted for the noncommercial reproduction of the complete work for educational or research purposes. Permission is granted to print, primarily for one person’s exclusive use, a single copy of these Proceedings. USENIX acknowledges all trademarks herein. ISBN 978-1-931971-05-8 USENIX Association Proceedings of the 27th Large Installation System Administration Conference November 3–8, 2013 Washington, D.C. Conference Organizers Program Co-Chairs David Nalley, Apache Cloudstack Narayan Desai, Argonne National Laboratory Adele Shakal, Metacloud, Inc.
    [Show full text]
  • The Forrester Wave™: Configuration Management Software for Infrastructure Automation, Q4 2018
    LICENSED FOR INDIVIDUAL USE ONLY The Forrester Wave™: Configuration Management Software For Infrastructure Automation, Q4 2018 The Seven Providers That Matter Most And How They Stack Up by Chris Gardner November 7, 2018 Why Read This Report Key Takeaways In our 27-criterion evaluation of configuration Puppet And Chef Lead The Market management providers, we identified the seven Forrester’s research uncovered a market in which most significant — Canonical, Chef, Microsoft, Puppet and Chef rank as Leaders; Microsoft, Red Northern.tech, Puppet, Red Hat, and SaltStack — Hat, and SaltStack are Strong Performers; and and researched, analyzed, and scored them. We Northern.tech and Canonical are Contenders. focused on core features, including deployment, Configuration Management Tools Form Part Of configuration modeling, automation, monitoring A Greater Automation Whole and governance, and community support, as well The greater landscape in this market consists as on each vendor’s ability to match a strategy of service, software, and element domains. to these features. This report helps infrastructure Within the element domain are provisioning and and operations (I&O) professionals make the control subdomains. The vendors and tools we right choice when looking for configuration evaluated in this Forrester Wave® straddle these management solutions for their DevOps and subdomains and are sometimes involved with infrastructure-as-code (IaC) automation. release management as well. This PDF is only licensed for individual use when downloaded from forrester.com
    [Show full text]
  • Cfengine Nova Technical Supplement Cfengine Enterprise Documentation for Version 2.0
    CFEngine Nova Technical Supplement CFEngine Enterprise Documentation for version 2.0 CFEngine Copyright c 2010 CFEngine AS. The features described herein are in provided for user convenience and imply no warranty whatsoever to the extent of applicable law. i Table of Contents 1 Introduction to CFEngine Nova:::::::::::::::::::::::::::::::: 1 1.1 What are enterprise versions of CFEngine? ::::::::::::::::::::::::::::: 1 1.2 What's new in Nova 2.0? :::::::::::::::::::::::::::::::::::::::::::::: 1 1.3 About the CFEngine architecture :::::::::::::::::::::::::::::::::::::: 2 1.3.1 CFEngine is agent based software::::::::::::::::::::::::::::::::: 2 1.3.2 Single point of coordination :::::::::::::::::::::::::::::::::::::: 2 1.3.3 Requirements and scalability of CFEngine Nova ::::::::::::::::::: 4 1.3.4 Phases of the server life-cycle :::::::::::::::::::::::::::::::::::: 4 1.4 Nova Commercial Enhancements :::::::::::::::::::::::::::::::::::::: 5 1.4.1 Productivity enhancements ::::::::::::::::::::::::::::::::::::::: 5 1.4.2 Functional enhancements::::::::::::::::::::::::::::::::::::::::: 6 1.4.3 Reporting enhancements ::::::::::::::::::::::::::::::::::::::::: 6 1.4.4 Documentation enhancements :::::::::::::::::::::::::::::::::::: 7 1.4.5 Knowledge Management in Nova ::::::::::::::::::::::::::::::::: 7 2 Installing CFEngine Nova:::::::::::::::::::::::::::::::::::::: 9 2.1 Operating system support ::::::::::::::::::::::::::::::::::::::::::::: 9 2.2 Installing the software on a new host ::::::::::::::::::::::::::::::::::: 9 2.3 Upgrading Nova::::::::::::::::::::::::::::::::::::::::::::::::::::::
    [Show full text]
  • Rudder 4.3 - User Manual I
    Rudder 4.3 - User Manual i Rudder 4.3 - User Manual Rudder 4.3 - User Manual ii Copyright © 2011-2016 Normation SAS Rudder User Documentation by Normation is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License. Permissions beyond the scope of this license may be available at normation.com. Rudder 4.3 - User Manual iii COLLABORATORS TITLE : Rudder 4.3 - User Manual ACTION NAME DATE SIGNATURE WRITTEN BY Jonathan Clarke, Jan 2018 Nicolas Charles, Fabrice Flore-Thebault, Matthieu Cerda, Nicolas Perron, Arthur Anglade, Vincent Membré, and François Armand REVISION HISTORY NUMBER DATE DESCRIPTION NAME 4.3 Jan 2018 N Rudder 4.3 - User Manual iv Contents 1 Online version 1 2 Introduction 2 2.1 What is Rudder? . .2 2.1.1 Made for production environments . .3 2.1.2 Different roles for a better accessibility . .4 2.1.3 Universality . .5 2.2 Key Features . .6 2.2.1 OS independent target configuration state definition . .6 2.2.2 Centralize and aggregate real configuration states . .7 2.2.3 Automatic inventory . .8 2.2.4 REST API . .8 2.2.5 Audit trace and Change Requests . .8 2.2.6 Centralized authentication (LDAP, Active Directory, plugins) . .9 2.2.7 Extensibilty . 10 2.3 Technical architecture and software dependencies . 11 2.3.1 Functional architecture of Rudder . 11 2.3.2 Network architecture in client/server mode . 12 2.3.3 Agents . 13 3 Installation 14 3.1 Quick installation . 14 3.2 Requirements . 15 3.2.1 Networking . 15 3.2.1.1 DNS - Name resolution .
    [Show full text]