Openlmi Documentation Release Latest

Total Page:16

File Type:pdf, Size:1020Kb

Openlmi Documentation Release Latest OpenLMI Documentation Release latest OpenLMI authors October 08, 2014 Contents 1 Client components 3 1.1 LMI metacommand ............................................3 1.2 LMIShell .................................................3 2 Server components 5 3 Table of Contents 7 3.1 OpenLMI client components.......................................7 3.2 OpenLMI server components...................................... 194 Python Module Index 299 i ii OpenLMI Documentation, Release latest OpenLMI = Open Linux Management Infrastructure. OpenLMI is open-source project aiming to improve management of Linux systems using WBEM standards. We reuse many already available open-source WBEM components, adding the missing ones and integrating them into one system management solution. In short, WBEM can be described as a remote API for system management. See WBEM overview for details. Contents 1 OpenLMI Documentation, Release latest 2 Contents CHAPTER 1 Client components There are many already existing tools and libraries to manage WBEM-enabled hosts. see WBEM overview for details. OpenLMI project adds LMI metacommand and LMIShell. 1.1 LMI metacommand A command line utility to perform discovery and operations on remote managed systems. For example, it can start a printing service on remote system: /usr/bin/lmi -h my.server.org service start cups LMI metacommand users do not need to know anything about WBEM, all the complexity is hidden inside. 1.2 LMIShell A high-level python-based WBEM client, that can be used for scripting or as an interactive shell to manage remote systems. For example, one can write a script to start a service: c= connect("my.server.org","root","opensesame") cups=c.root.cimv2.LMI_Service.first_instance({"Name":"cups.service"}) cups.StartService() LMIShell users do not need to know anything about WBEM transport protocols, however some knowledge about the aforementioned remote API becomes necessary. In the example above, the script author must know that system ser- vices are exposed as instances of LMI_Service class with property Name (the service name) and method StartService() that starts the service. 3 OpenLMI Documentation, Release latest 4 Chapter 1. Client components CHAPTER 2 Server components OpenLMI focuses on implementation of missing providers for networking, storage, system services, packages and so on. 5 OpenLMI Documentation, Release latest 6 Chapter 2. Server components CHAPTER 3 Table of Contents 3.1 OpenLMI client components They consist of several client-side python utilities and libraries. We refer to them as OpenLMI Tools and ship them under obvious name openlmi-tools. Currently they contain LMI metacommand and LMIShell. 3.1.1 LMI metacommand Is a command line interface for OpenLMI Providers sitting on top of LMIShell. It provides an easy to use interface for system management through modular commands. These dynamically extend the functionality of LMI metacommand. Short example: $ lmi -h myhost.example.org storage fs create --label=opt-root ext4 /dev/vda5 Usage LMI metacommand is a command line utility build on top of client-side libraries. It can not do much on its own. Its functionality is extended by commands that are installed separately. Each command operates on a set of providers that need to be installed on managed machine. Commands can be invoked directly from shell or within interactive mode. Running from command line It can run single command given on command line like this: lmi -h ${hostname} service list --all Getting help For detailed help run: lmi --help To get a list of available commands with short descriptions: 7 OpenLMI Documentation, Release latest lmi help For help on a particular registered command: lmi help service Interactive mode Or it can be run in interactive mode when command is omitted: $ lmi -h ${hostname} lmi> help ... lmi> sw search django ... lmi> sw install python-django ... lmi> exit help command is always your good friend. Following two lines gets you the same help message: lmi> help storage raid ... lmi> storage raid --help ... Built-in commands Interactive mode comes with few special commands not available from command line. To get their list, type: lmi> : help They are prefixed with : and optional space. Currently only namespace nesting commands are supported. Those are :cd, :.. and :pwd. They work as expected: lmi> :pwd # top-level namespace /lmi lmi> :cd storage # you can do storage specific stuff here >storage> :pwd /lmi/storage >storage> :cd raid # we don’t care about anything but raid >>raid> :pwd /lmi/storage/raid >>raid> :cd /lmi/sw # let’s manage packages now >sw> :.. lmi> Static commands Aren’t prepended with : and except for help are again available only in interactive mode. EOF Same as hitting ^D. If some nested into some command’s namespace, it will map to :cd .. and parent namespace will become active. If the top-level namespace is active, program will exit. exit Exits immediately. It accepts optional exit code as an argument. help Lists available commands. Accepts command path as an optional argument. 8 Chapter 3. Table of Contents OpenLMI Documentation, Release latest Extending metacommand In order to make the LMI metacommand useful, you’ll need to install some commands. If you run Fedora, the easiest way to get them is with your favorite package manager: sudo dnf install ’openlmi-scripts-*’ Note: On RHEL you’ll need to add EPEL to your repositories before installing them with yum. They will be automatically discovered by LMI metacommand. You can ensure their presence with this simple test: $ lmi help Commands: file - File and directory management functions. group - POSIX group information and management. help - Print the list of supported commands with short description. hwinfo - Display hardware information. journald - Test for provider version requirements locale - System locale management. net - Networking service management. power - System power state management. service - System service management. sssd - SSSD system service management. storage - Basic storage device information. sw - System software management. system - Display general system information. user - POSIX user information and management. For more informations about particular command type: help <command> As Python eggs They may be installed on any distribution. Go for them also if you want to be more up to date. They are available for download from PyPI. The easiest way to install them is with pip (shipped with python-pip package): pip search openlmi-scripts pip install --user openlmi-scripts-{hardware,system,service,storage} Bleeding edge Commands are available from our git repository. Follow instructions there to install the most up to date versions. Documentation Check out documentation of currently implemented commands. • Account command line reference • Hardware command line reference • Journald command line reference • Locale command line reference • Logical File command line reference • Networking command line reference • Power Management command line reference • Realmd command line reference 3.1. OpenLMI client components 9 OpenLMI Documentation, Release latest • Service command line reference • Software command line reference • SSSD command line reference • Storage command line reference • System command line reference Configuration LMI metacommand has the main configuration file located in: /etc/openlmi/scripts/lmi.conf User can have his own configuration file taking precedence over anything in global one above: $HOME/.lmirc Configuration is written in INI-like configuration files. Please refer to ConfigParser‘s documentation for details. Follows a list of sections with their list of options. Most of the options listed here can be overridden with command line parameters. See also: configuration Section [Main] CommandNamespace [string] Python namespace, where command entry points will be searched for. Defaults to lmi.scripts.cmd. Trace [boolean] Whether the exceptions should be logged with tracebacks. Defaults to False. Can be overridden with --trace and --notrace options on command-line. Note: For most exceptions generated by scripts a Verbosity option needs to be highest as well for tracebacks to be printed. Verbosity: integer A number within range -1 to 2 saying, how verbose the output shall be. This differs from log_level, which controls the logging messages written to file. If logging to console is enabled it sets the minimum severity level. -1 Suppresses all messages except for errors. 0 shows warnings, 1 info messages and 2 enables debug messages. This option also affects the verbosity of commands, making them print more information to stdout. Defaults to 0. Can be overridden with -v and -q flags on command-line. Section [CIM] Namespace [string] Allows to override default CIM namespace, which will be passed to script library functions. Defaults to root/cimv2. 10 Chapter 3. Table of Contents OpenLMI Documentation, Release latest Section [SSL] VerifyServerCertificate [boolean] Whether to verify server-side certificate, when making secured connection over https. Defaults to True. Can be overridden with -n | --noverify flag on command-line. Section [Format] HumanFriendly [boolean] Whether to print values in human readable forms (e.g. with units). Defaults to False. Can be overridden with -H | --human-frienly flag on command-line. ListerFormat [one of {csv, table}] What format to use, when listing tabular data. csv format allows for easy machine parsing, the second one is more human friendly. Defaults to table. Can be overridden with -L | --lister-format option on command line. NoHeadings
Recommended publications
  • Red Hat Enterprise Linux 7 Technical Overview
    RED HAT ENTERPRISE LINUX 7 TECHNICAL OVERVIEW Ingo Börnig Senior Solutions Architect, Red Hat 2014-07-08 1 RED HAT ENTERPRISE LINUX 7 | JUNE 2014 AGENDA 1 RED HAT ENTERPRISE LINUX 7 INTRODUCTION 2 LIGHTWEIGHT APPLICATION ISOLATION 3 WINDOWS INTEROPERABILITY 4 FILE SYSTEMS AND STORAGE 5 OPTIMAL PERFORMANCE MANAGEMENT 6 INSTALLATION AND DEPLOYMENT 2 RED HAT ENTERPRISE LINUX 7 | JUNE 2014 AGENDA (cont.) 7 SYSTEM MANAGEMENT AND FEATURES 8 VIRTUALIZATION 9 DESKTOP AND DEVELOPER FEATURES 10 SUMMARY 3 RED HAT ENTERPRISE LINUX 7 | JUNE 2014 RED HAT ENTERPRISE LINUX 7 INTRODUCTION 4 RED HAT ENTERPRISE LINUX 7 | JUNE 2014 RED HAT ENTERPRISE LINUX 7 REDEFINING THE ENTERPRISE OS FLEXIBILITY to STABILITY to efficiently CERTAINTY of quickly adapt to meet challenges of mission-critical demands for datacenter virtualization reliability and business agility and cloud military-grade security 90% OF FORTUNE 500 COMPANIES TRUST RED HAT ENTERPRISE LINUX FOR THEIR CRITICAL BUSINESS INFRASTRUCTURE. 5 RED HAT CONFIDENTIAL | PLATFORM PRODUCT MARKETING RED HAT ENTERPRISE LINUX 7 BASICS ● Based on Fedora 19, the upstream kernel version 3.10 and over 4000 patches (additional features, bugfixes, security errata) ● Supported hardware architectures: ● Intel/AMD 64-bit (x86_64) ● IBM POWER ● IBM System z ● Support for 32-bit applications enabled via inclusion of 32-bit libraries (multilib). 6 RED HAT ENTERPRISE LINUX 7HIGHLIGHTS RED HAT 7 STABLE AND FLEXIBLE EFFICIENT CERTAINTY OF MISSION-CRITICAL RELIABILITY AND MILITARY-GRADE SECURITY MILITARY-GRADE AND RELIABILITY
    [Show full text]
  • Configure. Manage. Monitor
    OpenLMI Configure. Manage. Monitor. March 2013 Linux System Management Today Is this you? 2 Storage ●Done with local commands: ●parted ●pvcreate, lvcreate, vgcreate ●mdraid ●vgextend, resize2fs 3 Networking ●Edited /etc/sysconfig/networking scripts ●nmcli command line tool 4 Notice anything? 5 Notice anything? ●Both methods require a local shell ●The methods had an entirely unrelated user experience 6 Training Costs ●There is a completely isolated path to learning administration of either approach ●Learning either task does not help you learn the other 7 Training Costs ●System services ●Installing software and patches ●Firewall ●Performance tuning ●... 8 Research ●“The difficulty of managing these components is directly impacting our customers' ability to consume more Linux” -- 2011 Red Hat Customer Survey Results (paraphrased) 9 OpenLMI ●Provide a complete system for System Management ●Local and network-facing API ●Common interface for all subsystems ●Built on industry-standard protocols 10 Blivet ●Split from the Anaconda installer project ●Python library for manipulating storage at all levels 11 NetworkManager ●D-BUS API ●Consistency guarantees on changes 12 systemd ●D-BUS API for monitoring system services ●Journald API for log monitoring 13 DMTF-CIM ●Industry-standard model for system management ●Comprehensive object-oriented design addressing most aspects of system capabilities 14 What about simplicity? ●CIM is a complex model that many find intimidating 15 LMIShell ●Python-based scripting environment for OpenLMI/CIM ●Simplifies the
    [Show full text]
  • Configuration and Administration of Networking for Fedora 23
    Fedora 23 Networking Guide Configuration and Administration of Networking for Fedora 23 Stephen Wadeley Networking Guide Draft Fedora 23 Networking Guide Configuration and Administration of Networking for Fedora 23 Edition 1.0 Author Stephen Wadeley [email protected] Copyright © 2015 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.
    [Show full text]
  • Russell Doty Technology Product Manager, Red Hat Stephen Gallagher System Architect, Red Hat Mid Level Sysadmin
    Administer Production Servers Effectively with OpenLMI Russell Doty Technology Product Manager, Red Hat Stephen Gallagher System Architect, Red Hat Mid Level Sysadmin Routine, day to day tasks Experienced with Microsoft & VMware New to Linux Experienced Linux SysAdmin Big Bag 'O Scripts & ssh Powered by nmcli lvcreate HELP!mkfs.xfs yum parted systemctl Need to Automate! Prerequisite for the automated factory: Robots In other words: An infrastructure and foundation for automation. Client Python CLI Scripting Java C/C++ Remote Communications Abstraction API nmcli yum lvcreate Mkfs.xfs Parted systemctl We Can Build This! Why OpenLMI? Previous Open Source Remote Management Tools Lacked a Strong Foundation – A Management API What is OpenLMI? •A set of Management Agents • That can change the system •A Standardized Remote API •A Standard Communications Infrastructure • Built on XML over https •A Client Environment • Scripting built on Python • CLI • Other languages OpenLMI Providers - Heavy Lifting •Perform management operations •Provide standard API • Low level, functional API • Remote/Local API •Built on existing Linux tools and utilities (e.g. parted, lvcreate, Network Manager) Object Broker - OpenPegasus •Manages Providers • Commands – attributes & methods • Navigation & query • Events (Indications) •Manages Communications • WBEM – CIM/XML over https •Manages Authentication & Access Events - OpenLMI Indications •Notification of Asynchronous Events • e.g. job completion, drive failure, NIC changed state, password changed •Listener registers with CIMOM • Multiple Listeners per event •All registered Listeners notified when event occurs •Powerful tool for monitoring Client Interfaces •OpenLMI API • Low level functional API • Full coverage •LMIShell Modules (EPEL) • Task oriented Python modules • Subset of full API •LMI CLI (EPEL) • Task oriented, user friendly CLI • BASH shell friendly • Least coverage Sounds Interesting..
    [Show full text]
  • Configure, Manage, Monitor Linux Systems Russell Doty [email protected] Red Hat
    Server Management Configure, Manage, Monitor Linux Systems Russell Doty [email protected] Red Hat 1 Copyright © 2014 Red Hat Mid Level Sysadmin Routine, day to day tasks Experienced with Microsoft & VMware New to Linux 2 Copyright © 2014 Red Hat lvcreate nmcli mkfs.xfs HELP!yum parted systemctl 3 Copyright © 2014 Red Hat Experienced Linux Sysadmin Big Bag 'O Scripts & ssh Powered by 4 Copyright © 2014 Red Hat OpenLMI Project Goals ● Improve manageability of Linux systems ● Configuration of remote servers ● Main Initial Focus: configure storage, networks, and authentication ● Broader management support planned ● Reduce learning curve for new SysAdmins to perform common Linux administration tasks ● Provide a foundation for advanced automation and interfaces ● Build on open industry standards ● Open and extensible ● Including 3rd parties and customers 5 Copyright © 2014 Red Hat What Can You Do With OpenLMI? ● Example: Storage ● Determine what storage devices are connected to the system ● Friendly device names & persistent device names ● Partition, format, encrypt, create RAID sets, create logical volumes and volume groups, mount filesystems ● Local & remote block devices ● From programs, scripts or CLI ● CLI example: “lmi> storage raid create –name R1 5 sdb sdc sdd sde sdf” (creates 5 disk RAID 5 set called R1) ● More power and flexibility from LMIShell and OpenLMI API ● Query, configure, monitor and change storage 6 Copyright © 2014 Red Hat What is OpenLMI? ● A set of Management Agents ● That query, modify & monitor systems ● A Standardized
    [Show full text]
  • Oracle® Linux 7 Release Notes for Oracle Linux 7
    Oracle® Linux 7 Release Notes for Oracle Linux 7 E53499-20 March 2021 Oracle Legal Notices Copyright © 2011,2021 Oracle and/or its affiliates. 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 embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software" or "commercial computer software documentation" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.
    [Show full text]
  • Fedora 25 Networking Guide
    Fedora 25 Networking Guide Configuration and Administration of Networking for Fedora 25 Stephen Wadeley Networking Guide Draft Fedora 25 Networking Guide Configuration and Administration of Networking for Fedora 25 Edition 1 Author Stephen Wadeley [email protected] Copyright © 2016 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.
    [Show full text]
  • Red Hat Enterprise Linux Server for ARM 7.1 Release Notes
    Red Hat Enterprise Linux Server for ARM 7.1 Release Notes Release Notes for Red Hat Enterprise Linux Server for ARM Red Hat Customer Content Services Red Hat Enterprise Linux Server for ARM 7.1 Release Notes Release Notes for Red Hat Enterprise Linux Server for ARM Red Hat Customer Content Services Legal Notice Copyright © 2015 Red Hat, Inc. This document is licensed by Red Hat under the Creative Commons Attribution-ShareAlike 3.0 Unported License. If you distribute this document, or a modified version of it, you must provide attribution to Red Hat, Inc. and provide a link to the original. If the document is modified, all Red Hat trademarks must be removed. 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. 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. Node.js ® is an official trademark of Joyent. Red Hat Software Collections is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
    [Show full text]
  • Red Hat Enterprise Linux 7 7.8 Release Notes
    Red Hat Enterprise Linux 7 7.8 Release Notes Release Notes for Red Hat Enterprise Linux 7.8 Last Updated: 2021-03-02 Red Hat Enterprise Linux 7 7.8 Release Notes Release Notes for Red Hat Enterprise Linux 7.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. Node.js ® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
    [Show full text]
  • Empower 3 Service Release 4
    *716006210* *Ver.01* Empower 3 Service Release 4 Release Notes 716006210 Copyright © Waters Corporation 2020 Version 01 (previously released as Rev.A) All rights reserved General information Copyright notice © 2020 WATERS CORPORATION. PRINTED IN THE UNITED STATES OF AMERICA AND IN IRELAND. ALL RIGHTS RESERVED. THIS DOCUMENT OR PARTS THEREOF MAY NOT BE REPRODUCED IN ANY FORM WITHOUT THE WRITTEN PERMISSION OF THE PUBLISHER. The information in this document is subject to change without notice and should not be construed as a commitment by Waters Corporation. Waters Corporation assumes no responsibility for any errors that may appear in this document. This document is believed to be complete and accurate at the time of publication. In no event shall Waters Corporation be liable for incidental or consequential damages in connection with, or arising from, its use. For the most recent revision of this document, consult the Waters website (www.waters.com). Trademarks CitrixTM is a registered trademark of Citrix Systems, Inc. and/or one or more of its subsidiaries, and may be registered in the United States Patent and Trademark Office and in other countries. EmpowerTM is a trademark of Waters Corporation. LAC/ETM is a trademark of Waters Corporation. Linux® is a registered trademark of Linus Torvalds. Oracle® is a registered trademark of Oracle Corporation and/or its affiliates. Red Hat® is a registered trademark of Red Hat, Inc. THE SCIENCE OF WHAT'S POSSIBLETM is a trademark of Waters Corporation. WatersTM is a trademark of Waters Corporation. Windows® is a registered trademark of Microsoft Corporation in the US and/or other countries.
    [Show full text]
  • Redefining the Enterprise Os Red Hat Enterprise Linux 7
    REDEFINING THE ENTERPRISE OS RED HAT ENTERPRISE LINUX 7 Rodrigo Freire Sr. Technical Account Manager 29/Ago/2014 1 Rodrigo Freire / Ron Pacheco Roadmap At A Glance CY2010 CY2011 CY2012 CY2013 CY2014 RHEL 7 .0 RHEL 6 .0 .1 .2 .3 .4 .5 .6 RHEL 5 .5 .6 .7 .8 .9 .10 .11 Production 1 Production 2 Production 3 *All dates are approximate and subject to change 2> Rodrigo Freire / Ron Pacheco Application Isolation via Containers CONTAINERS ENABLE CONTINUOUS DELIVERY APP HOST OS SERVER LIBS CONTAINER CONTAINER APP LIBS HOST OS SERVER DEVELOPMENT FOCUS OPERATIONS FOCUS ● CODE ● HARDWARE ● APPLICATIONS ● OPERATING SYSTEM ● LIBRARIES AND OTHER ● NETWORKING DEPENDENCIES ● MONITORING ● DATA STORE 4 Rodrigo Freire / Ron Pacheco RHEL 7 Containers Architecture with Docker CLI Containers Containers Containers DOCKER CLI Docker Image SYSTEMD Unit File Cgroups Namespaces SELinux Drivers RHEL Kernel Hardware (Intel, AMD) 5 Rodrigo Freire / Ron Pacheco BENEFITS OF LINUX CONTAINERS 6 Rodrigo Freire / Ron Pacheco MORE EFFICIENT INSTALLATION AND DEPLOYMENT SPEED DEPLOYMENT IN-PLACE UPGRADES PRIORITIZE CRITICAL WITH SERVER PROFILES FROM 6.X TO 7 SERVICES AT START-UP EASILY CREATE CUSTOM SAFELY ROLL-BACK DRAMATICALLY SPEED INSTALL IMAGES DURING INSTALL START-UP TIMES 8 Rodrigo Freire / Ron Pacheco Create, Install, Deploy & Manage Custom Install Images using Live Media Creator Easier installation, deployment, and custom image creation/management across large-scale enterprises ● Spin custom installable images with the help of Live Media Creator Content Sources Custom
    [Show full text]
  • Fedora 24 Networking Guide
    Fedora 24 Networking Guide Configuration and Administration of Networking for Fedora 24 Stephen Wadeley Networking Guide Fedora 24 Networking Guide Configuration and Administration of Networking for Fedora 24 Edition 1.0 Author Stephen Wadeley [email protected] Copyright © 2016 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.
    [Show full text]