DOCSLIB.ORG

Setting up a Highly Available Red Hat Enterprise Virtualization Manager (RHEV 3.0) Author Names: Brandon Perkins, Chris Negus 05/4/2012

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Setting up a Highly Available Red Hat Enterprise Virtualization Manager (RHEV 3.0) Author Names: Brandon Perkins, Chris Negus 05/4/2012 Setting Up a Highly Available Red Hat Enterprise Virtualization Manager (RHEV 3.0) Author Names: Brandon Perkins, Chris Negus 05/4/2012 INTRODUCTION This tech brief describes how to configure Red Hat Enterprise Virtualization Manager (RHEV-M) in a two- node, Red Hat Cluster Suite (RHCS) highly available (HA) cluster. To make your RHEV-M highly available, you can configure it to run as a service in a HA cluster. RHCS High availability clusters eliminate single points of failure, so if the node on which a service (in this case the RHEV-M) is running should become inoperative, the service can start up again (fail over) to another cluster node without interruption or data loss. Configuring a Red Hat Enterprise Linux Cluster is described in the RHEL 6 Cluster Administration Guide. Refer to that guide for help extending or modifying your cluster: http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Cluster_Administration/index.html NOTE: Although not strictly required, it is generally better to run at least a three node cluster. Besides offering extra resources, the additional node makes it less likely you will end up in a "split-brain" condition, where both nodes believe they control the cluster. NOTE: The procedures in this tech brief contain several long, complex commands. Consider copying this document, or plain text copies of it, to the cluster nodes so you can copy and paste commands into the shell. UNDERSTANDING SYSTEM REQUIREMENTS There are many different ways of setting up a high availability RHEV-M cluster. In our example, we used the following components: • Two cluster nodes. Install two machines with Red Hat Enterprise Linux to act as cluster nodes. • A cluster web user interface. A Red Hat Enterprise Linux system (not on either of the cluster nodes) running the luci Web-based high-availability administration application. You want this running on a third system, so if either node goes down, you can still manage the cluster from another system. • Network storage. Shared network storage is required. This procedure shows how to use HA LVM from a RHEL 6 system, which is backed by iSCSI storage. (Fibre channel and NFS are other technologies you could use instead of iSCSI.) • Red Hat products. This procedure combines components from Red Hat Enterprise Linux, Red Hat Cluster Suite, and Red Hat Enterprise Virtualization. Using this information, set up two physical systems as cluster nodes (running ricci), another physical system that holds the cluster manager web user interface (running luci), and a final system that contains the HA LVM storage. Figure 1 shows the basic layout of the systems used to test this procedure: Setting up a Highly Available RHEV-M 3.0 | Perkins, Negus 1 Figure 1: Example RHEV-M on HA cluster configuration For our example, we used two NICS on the cluster nodes. We used a 192.168.99.0 network for communication within the cluster and 192.168.100.0 for the network facing the RHEV environment. We used a SAN and create a high-availability LVM with multiple logical volumes that are shared by the cluster. The procedures that follow describe how to set up the cluster nodes, cluster web user interface, HA LVM storage, and the clustered service running the RHEV-M. INSTALLING THE TWO CLUSTER NODES (RICCI) In this example, the two Red Hat Enterprise Linux 6.2 cluster nodes must: • Registration: Be registered with RHN. • Entitlements: Have Red Hat Enterprise Linux, Red Hat Enterprise Virtualization and Red Hat Cluster Suite entitlements. • Channels: Be subscribed to the Red Hat Enterprise Linux Server (v. 6 for 64-bit x86_64) base/parent channel, the RHEL Server Supplementary (v. 6 64-bit x86_64) child channel (which provides both the java-1.6.0-sun and java-1.6.0-sun-devel packages), and the RHEL Server High Availability (v. 6 for 64- bit x86_64) child channel (which provides ricci and all supporting clustering packages). • Security: Run with SELinux in Enforcing mode, using the targeted processes protected policy, and Setting up a Highly Available RHEV-M 3.0 | Perkins, Negus 2 have iptables packet filtering started and persisted. (Recommended) • Storage: Have some form of shared block device, such as fibre channel or iSCSI, between the two nodes. For our example, we assume a shared iSCSI device that appears as /dev/sdb is configured on both nodes before configuring the storage portion of the cluster. Here are the basic steps you need to run to install both cluster node systems: 1. Install RHEL. On both cluster nodes, install a Red Hat Enterprise Linux 6 Server system (a base install is all that is needed at this point). In testing, we used a RHEL 6.2 Basic Server installation. Because these systems must run the Red Hat Enterprise Virtualization Manager (RHEV-M), it must meet the hardware and software requirements described in the RHEV Installation Guide (http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Virtualization/3.0/html- single/Installation_Guide/index.html#chap-Installation_Guide- Installing_the_RHEV_Manager-Manager). Running rhevm-setup and related procedures (such as setting up firewall rules) is covered later in the chapter. 2. Configure networking. How you set up networking is up to you and your environment. In our example, to make sure application traffic doesn't interfere with cluster traffic, we put the cluster on a separate network with static IP addresses (eth0). On the RHEV network, we assume there is a properly configured DHCP server (eth1). Here's what our network configuration files look like: • On both cluster nodes (node1 and node2) we added these lines to the /etc/hosts file: 192.168.99.1 node1.example.com 192.168.99.2 node2.example.com 192.168.99.3 luci.example.com • On node1, we set the hostname, a static IP address for eth0 and dhcp for eth1 interfaces in several files, as noted below: /etc/sysconfig/network HOSTNAME=node1.example.com /etc/sysconfig/network-scripts/ifcfg-eth0 DEVICE=eth0 HWADDR=??:??:??:??:??:?? NM_CONTROLLED=no ONBOOT=yes BOOTPROTO=dhcp TYPE=Ethernet /etc/sysconfig/network-scripts/ifcfg-eth1 DEVICE=eth1 HWADDR=??:??:??:??:??:?? NM_CONTROLLED=no ONBOOT=yes BOOTPROTO=none TYPE=Ethernet IPADDR=192.168.99.1 NETMASK=255.255.255.0 • On node2, we also set the hostname, a static IP address for eth0 and dhcp for eth1 interfaces in several files, as noted below: Setting up a Highly Available RHEV-M 3.0 | Perkins, Negus 3 Copyright © 2012 Red Hat, Inc. “Red Hat,” Red Hat Linux, the Red Hat “Shadowman” logo, and the products www.redhat.com listed are trademarks of Red Hat, Inc., registered in the U.S. and other countries. Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries. /etc/sysconfig/network HOSTNAME=node2.example.com /etc/sysconfig/network-scripts/ifcfg-eth0 DEVICE=eth0 HWADDR=??:??:??:??:??:?? NM_CONTROLLED=no ONBOOT=yes BOOTPROTO=dhcp TYPE=Ethernet /etc/sysconfig/network-scripts/ifcfg-eth1 DEVICE=eth1 HWADDR=??:??:??:??:??:?? NM_CONTROLLED=no ONBOOT=yes BOOTPROTO=none TYPE=Ethernet IPADDR=192.168.99.2 NETMASK=255.255.255.0 With that configured, we started the network service: # service NetworkManager stop # chkconfig NetworkManager off # service network start # chkconfig network on 3. Register RHEL. Register all systems with Red Hat Network. Here's one way to do that: # rhnreg_ks --activationkey="your_activation_key" 4. Add channels to each node. On both cluster nodes, for each required channel (High Availability, Supplementary, RHEVM, and JBoss channels), run the rhn-channel command to add the necessary channels. For example: # rhn-channel --add --channel=rhel-x86_64-server-supplementary-6 # rhn-channel --add --channel=rhel-x86_64-server-ha-6 # rhn-channel --add --channel=rhel-x86_64-server-6-rhevm-3 # rhn-channel --add --channel=jbappplatform-5-x86_64-server-6-rpm 5. Install ricci. On both cluster nodes, install the ricci RPMs on each node. # yum -y install ricci 6. Update packages. On both cluster nodes, run yum update to make sure that all your packages are up to date. Reboot if there is a new kernel. # yum update # reboot 7. Open firewall: On both cluster nodes, open up the necessary ports in iptables. Assuming your firewall is currently configured, with the proper rules installed in the running kernel, run these commands to create a custom chain of firewall rules (called RHCS) and save those changes permanently: Setting up a Highly Available RHEV-M 3.0 | Perkins, Negus 4 # iptables -N RHCS # iptables -I INPUT 1 -j RHCS # iptables -A RHCS -p udp --dst 224.0.0.0/4 -j ACCEPT # iptables -A RHCS -p igmp -j ACCEPT # iptables -A RHCS -m state --state NEW -m multiport -p tcp --dports \ 40040,40042,41040,41966,41967,41968,41969,14567,16851,11111,21064,50006,\ 50008,50009,8084 -j ACCEPT # iptables -A RHCS -m state --state NEW -m multiport -p udp --dports \ 6809,50007,5404,5405 -j ACCEPT # service iptables save iptables: Saving firewall rules to /etc/sysconfig/iptables:[ OK ] 8. Start ricci. On both cluster nodes, start the ricci daemon on both nodes and configure it to start on boot: # chkconfig ricci on # service ricci start Starting oddjobd: [ OK ] generating SSL certificates... done Generating NSS database... done Starting ricci: [ OK ] 9. Set password. On both cluster nodes, set the ricci user password: # passwd ricci Changing password for user ricci. New password: ********** Retype new password: ********** passwd: all authentication tokens updated successfully. At this point both cluster nodes should be running the ricci servers and be ready to be managed by the cluster web user interface (luci), as described in the next section. INSTALLING THE CLUSTER WEB USER INTERFACE (LUCI) On the RHEL system you have chosen to run the cluster web user interface (luci), enable the same channels you did for the cluster nodes.
Load more

Recommended publications
  • Red Hat GFS 6.0 Administrator's Guide
    Red Hat GFS 6.0 Administrator's Guide Red Hat GFS 6.0: Administrator's Guide Copyright © 2004 and 2005 Red Hat, Inc. Red Hat, Inc. 1801 Varsity Drive Raleigh NC 27606-2072 USA Phone: +1 919 754 3700 Phone: 888 733 4281 Fax: +1 919 754 3701 PO Box 13588 Research Triangle Park NC 27709 USA rh-gfsg(EN)-6.0-Print-RHI (2005-08-02T11:07-0400) Copyright © 2005 by Red Hat, Inc. This material may be distributed only subject to the terms and conditions set forth in the Open Publication License, V1.0 or later (the latest version is presently available at http://www.opencontent.org/openpub/). Distribution of substantively modified versions of this document is prohibited without the explicit permission of the copyright holder. Distribution of the work or derivative of the work in any standard (paper) book form for commercial purposes is prohibited unless prior permission is obtained from the copyright holder. Red Hat and the Red Hat "Shadow Man" logo are registered trademarks of Red Hat, Inc. in the United States and other countries. All other trademarks referenced herein are the property of their respective owners. The GPG fingerprint of the [email protected] key is: CA 20 86 86 2B D6 9D FC 65 F6 EC C4 21 91 80 CD DB 42 A6 0E Table of Contents Introduction.......................................................................................................................................... i 1. Audience ................................................................................................................................ i 2. Document
    [Show full text]
  • Product Appendix 1 Software and Support Subscriptions 产品附录1 软件和支持订阅
    PRODUCT APPENDIX 1 产品附录 1 SOFTWARE AND SUPPORT 软件和支持订阅 SUBSCRIPTIONS This Product Appendix (which includes Exhibits applicable to specific 本产品附录（包括具体红帽产品所适用的附件）包含参数描述条款及 Red Hat Products) contains terms that describe the parameters and govern your use of Software Subscriptions and Support 贵方使用软件订阅和支持订阅所适用的条款。红帽托管或在线订阅商 Subscriptions. This Product Appendix does not apply to Red Hat 品/服务不适用本产品附录。我们在本产品附录中使用但未在本产品 hosted or on-line subscription offerings. When we use a capitalized term in this Product Appendix without defining it in this Product 附 录 中 定 义 的 术 语 ， 具有本产 品 附 录 适 用 的 协 议 （ 如 Appendix, the term has the meaning defined in the Agreement to http://www.redhat.com/agreements 上规定的红帽企业协议，或客户 which this Product Appendix applies, either the Red Hat Enterprise Agreement set forth at http://www.redhat.com/agreements or, if 与红帽之间共同签署的协议（如适用））中定义的含义。如果本产品 applicable, a mutually signed agreement between Client and Red 附录与本产品附录的附件有冲突、不一致或差异，以附件的条款 Hat. In the event of a conflict, inconsistency or difference between this Product Appendix and an Exhibit to this Product Appendix, the 为准。 terms of the Exhibit control. Red Hat may modify or update this Product Appendix either by 红帽可通过在 http://www.redhat.com/agreements 发布本产品附录 posting a revised version of this Product Appendix at http://www.redhat.com/agreements, or by providing notice using 的修订版或以其他合理的方式提供通知，对本产品附录进行修改或 other reasonable means. If you do not agree to the revised version 更新。如果贵方不同意经修改的版本，则 (a) 截至更新日期贵方已购 then, (a) the existing Product Appendix will continue to apply to Red Hat Products you have purchased as of the date of the update for the 买的红帽产品，将在当时的订阅期的剩余期限内继续适用现有的产 remainder of the then-current Subscription term(s); and (b) the 品附录；且 (b) 在经修改的版本的生效日期之后对红帽产品的任何新 revised version will apply to any new purchases or renewals of Red Hat Products made after the effective date of the revised version.
    [Show full text]
  • FORM 10−K RED HAT INC − RHT Filed: April 30, 2007 (Period: February 28, 2007)
    FORM 10−K RED HAT INC − RHT Filed: April 30, 2007 (period: February 28, 2007) Annual report which provides a comprehensive overview of the company for the past year Table of Contents PART I Item 1. Business 3 PART I ITEM 1. BUSINESS ITEM 1A. RISK FACTORS ITEM 1B. UNRESOLVED STAFF COMMENTS ITEM 2. PROPERTIES ITEM 3. LEGAL PROCEEDINGS ITEM 4. SUBMISSION OF MATTERS TO A VOTE OF SECURITY HOLDERS PART II ITEM 5. MARKET FOR REGISTRANT S COMMON EQUITY, RELATED STOCKHOLDER MATTERS AND ISSUER PURCHASES OF E ITEM 6. SELECTED FINANCIAL DATA ITEM 7. MANAGEMENT S DISCUSSION AND ANALYSIS OF FINANCIAL CONDITION AND RESULTS OF OPERATIONS ITEM 7A. QUANTITATIVE AND QUALITATIVE DISCLOSURES ABOUT MARKET RISK ITEM 8. FINANCIAL STATEMENTS AND SUPPLEMENTARY DATA ITEM 9. CHANGES IN AND DISAGREEMENTS WITH ACCOUNTANTS ON ACCOUNTING AND FINANCIAL DISCLOSURE ITEM 9A. CONTROLS AND PROCEDURES ITEM 9B. OTHER INFORMATION Part III ITEM 10. DIRECTORS, EXECUTIVE OFFICERS AND CORPORATE GOVERNANCE ITEM 11. EXECUTIVE COMPENSATION ITEM 12. SECURITY OWNERSHIP OF CERTAIN BENEFICIAL OWNERS AND MANAGEMENT AND RELATED STOCKHOLDER MATT ITEM 13. CERTAIN RELATIONSHIPS AND RELATED TRANSACTIONS, AND DIRECTOR INDEPENDENCE ITEM 14. PRINCIPAL ACCOUNTANT FEES AND SERVICES PART IV ITEM 15. EXHIBITS, FINANCIAL STATEMENT SCHEDULES SIGNATURES EX−21.1 (SUBSIDIARIES OF RED HAT) EX−23.1 (CONSENT PF PRICEWATERHOUSECOOPERS LLP) EX−31.1 (CERTIFICATION) EX−31.2 (CERTIFICATION) EX−32.1 (CERTIFICATION) Table of Contents UNITED STATES SECURITIES AND EXCHANGE COMMISSION Washington, D.C. 20549 FORM 10−K Annual Report Pursuant to Sections 13 or 15(d) of the Securities Exchange Act of 1934 (Mark One) x Annual Report Pursuant to Section 13 or 15(d) of the Securities Exchange Act of 1934 For the fiscal year ended February 28, 2007 OR ¨ Transition Report Pursuant to Section 13 or 15(d) of the Securities Exchange Act of 1934 For the transition period from to .
    [Show full text]
  • Red Hat Enterprise Linux 6 High Availability Add-On Overview 1 Red Hat Enterprise Linux 6
    Red Hat Enterprise Linux 6 High Availability Add-On Overview 1 Red Hat Enterprise Linux 6 High Availability Add-On Overview Overview of the High Availability Add-On for Red Hat Enterprise Linux Edition 2 2 Legal Notice Legal Notice Copyright © 2011 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/. 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. 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. All other trademarks are the property of their respective owners. 1801 Varsity Drive Raleigh, NC 27606-2072 USA Phone: +1 919 754 3700 Phone: 888 733 4281 Fax: +1 919 754 3701 Red Hat Enterprise Linux 6 High Availability Add-On Overview 3 Abstract High Availability Add-On Overview provides an overview of the High Availability Add-On for Red Hat Enterprise Linux 6.
    [Show full text]
  • Red Hat Enterprise Linux 5 Overview and Technology Roadmap
    Red Hat Enterprise Linux 5 Overview and Technology Roadmap Seung-Do Yang, RHCA [email protected] Sales Engineer Red Hat Korea Agenda Red Hat Enterprise Linux Overview Market Overview Red Hat Linux Roadmap Update Red Hat Enterprise Linux 5 Q&A 2 What is the Market doing? Linux vs. Unix Linux vs. Unix - Installed Base (000's) Linux vs. Unix - Shipments (000's) 6,000 1,800 5,500 1,600 5,000 1,400 4,500 4,000 1,200 3,500 Linux 1,000 Linux 3,000 Unix Unix 800 2,500 2,000 600 1,500 400 1,000 200 500 0 0 2002 2003 2004 2005 2006 2007 2008 2009 2004 2005 2006 2007 2008 2009 Source: IDC: Worldwide Operating Environments Forecast, Source: IDC: Worldwide New License Revenue Shipments (SOE), December 2005, #34599 Forecast (SOE), December 2005, #34599 3 How is Linux being used? N-Tier Computational Management Clusters Infrastructures Applications Support Infrastructure Database Utility Infrastructure 4 TCO by the Numbers Average Saves ● Linux vs. Unix (37%) Examples ● Linux Web Server (54%) ● Linux Application Server (16-40%) ● Linux Database Server (12-67%) Proprietary Web Server $20.9K Proprietary v. $42.0K O! Servlet Container wer TC 40% Lo Proprietary Database Data Data 5 Top 200 Red Hat customers Transportation Services 1.0% Education 1.0% Pharmaceuticals Energy and Utilities 1.5% PhTaEdrramnuascpcaoetruiottnaic ta io lsn &S 1eM.r0ev%diciceasl 11..00%% & Medical 1.0% EneOOrttghye r a 2n2.0d.0% %Ut ilit ies 1.5% Financial Services 19.0% Retail & Distribution 3.5% Media 4.0% Manufacturing 4.5% Internet 5.0% Professional Services 6.5% High Tech
    [Show full text]
  • Cluster Suite Overview
    Red Hat Enterprise Linux 4 Cluster Suite Overview Red Hat Cluster Suite for Red Hat Enterprise Linux Edition 1.0 Last Updated: 2020-03-08 Red Hat Enterprise Linux 4 Cluster Suite Overview Red Hat Cluster Suite for Red Hat Enterprise Linux Edition 1.0 Landmann [email protected] Legal Notice Copyright © 2009 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, 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]
  • Product Appendix 1
    PRODUCT APPENDIX 1 PRODUKTANHANG 1 SOFTWARE AND SUPPORT SOFTWARE UND SUPPORT SUBSCRIPTIONS SUBSCRIPTIONS This Product Appendix (which includes Exhibits applicable to Dieser Produktanhang (der Anlagen für besondere Produkte von specific Red Hat Products) contains terms that describe the Red Hat beinhaltet) enthält Bestimmungen, die den allgemeinen parameters and govern your use of Software Subscriptions and Rahmen festlegen und Ihre Nutzung der Software Subscriptions Support Subscriptions. This Product Appendix does not apply to und Support Subscriptions regeln. Dieser Produktanhang gilt nicht Red Hat hosted or on-line subscription offerings. When we use a für von Red Hat gehostete oder für Online-Subscription-Angebote. capitalized term in this Product Appendix without defining it, the Wenn wir in diesem Produktanhang [in der englischen Fassung] term has the meaning define d in the Agreement to which this einen großgeschriebenen Begriff verwenden, ohne diesen zu Product Appendix applies, such as the Red Hat Enterprise definieren, hat der Begriff die Bedeutung, die in dem Vertrag, zu Agreement. In the event of a conflict, inconsistency or difference dem der Produktanhang gehör t (zum Beispiel dem between this Product Appendix and an Exhibit to this Product Geschäftskunden vertrag von Red Hat), festgelegt ist. Im Fall eines Appendix, the terms of the Exhibit control. Konflikts, einer Inkonsistenz oder eines Unterschieds zwischen diesem Produktanhang und einer Anlage zu diesem Produktanhang sind die Bedingungen der Anlage maßgebend. Red Hat may modify or update this Product Appendix either by Red Hat kann diesen Anhang ändern bzw. aktualisieren, indem es posting a revised version of this Product Appendix at eine revidierte Fassung dieses Produktanh angs auf seine Website http://www.redhat.com/agreements , and/or by providing notice http://www.redhat.com/agreements stellt oder die Änderungen using oth er reasonable means.
    [Show full text]
  • Red Hat Order Form and Appendices
    PRODUCT APPENDIX 1 APPENDICE AL PRODOTTO 1 SOFTWARE AND SUPPORT SOFTWARE E ABBONAMENTI SUBSCRIPTIONS DI SUPPORTO This Product Appendix (which includes Exhibits applicable to La presente Appendice al Prodotto (che include gli Allegati specific Red Hat Products) contains terms that describe the applicabili agli specifici Prodotti Red Hat) contiene i termini che parameters and govern your use of Software Subscriptions and descrivono i parametri e regolano il Vostro uso degli Abbonamenti Support Subscriptions. This Product Appendix does not apply to al Software e degli Abbonamenti di Supporto. La presente Red Hat hosted or on-line subscription offerings. When we use a Appendice non si applica alle offerte presentate da Red Hat o alle capitalized term in this Product Appendix without defining it in this offerte di abbonamento online. Quando nella presente Appendice Product Appendix, the term has the meaning defined in the del Prodotto viene utilizzato un termine con lettera maiuscola privo Agreement to which this Product Appendix applies, either the Red di definizione nell’Appendice stessa, quel termine ha il significato Hat Enterprise Agreement set forth at definito nell'Accordo cui questa Appendice del Prodotto si riferisce, http://www.redhat.com/agreements or, if applicable, a mutually o nell'Accordo per Red Hat Enterprise disponibile all’indirizzo signed agreement between Client and Red Hat. In the event of a http://www.redhat.com/agreements o, se applicabile, in un accordo conflict, inconsistency or difference between this Product sottoscritto dal Cliente e da Red Hat. Nell'eventualità di conflitti, Appendix and an Exhibit to this Product Appendix, the terms of incongruenze o differenze tra la presente Appendice e un Allegato the Exhibit control.
    [Show full text]
  • How to Update a Red Hat Enterprise Linux Cluster While Minimizing Downtime Authors: Adam Drew and Eva Schaller Editor: Allison Pranger 11/25/2010
    How to Update a Red Hat Enterprise Linux Cluster while Minimizing Downtime Authors: Adam Drew and Eva Schaller Editor: Allison Pranger 11/25/2010 OVERVIEW A rolling upgrade is the process of taking a running cluster and updating packages either from one minor version of Red Hat Enterprise Linux to another (for example, updating a Red Hat Enterprise Linux 5.4 cluster to Red Hat Enterprise Linux 5.5) or updating to the latest errata packages in the same minor release (for example, updating a Red Hat Enterprise Linux 5.5 cluster with the latest Red Hat Enterprise Linux 5.5.z release). NOTE: Rolling upgrades between minor releases of Red Hat Enterprise Linux are fully supported, but rolling upgrades between major releases of Red Hat Enterprise Linux are not supported at this time. This document describes how to perform a rolling upgrade to update software on every node of a cluster while minimizing downtime. Environment • Red Hat Cluster Suite • Red Hat Enterprise Linux 5+ Advanced Platform (Clustering and GFS/GFS2) RECOMMENDATIONS During the upgrade process, the cluster will be running some nodes at one software revision level and other nodes at a higher software revision. It is best practice to minimize the amount of time that the cluster is running with a heterogeneous software configuration. There is no set time limit for how long a cluster may run in this mode, but returning all nodes to the same software versions as quickly as possible is recommended. The specific process you should follow depends on how many nodes are in your cluster and how many versions you are moving between.
    [Show full text]
  • LINUX JOURNAL | Issue 284 | March 2018
    What’s New Shell Scripting Raspberry Pi in Qubes 4 Security Alternatives Since 1994: The original magazine of the Linux community DEEP DIVE BLOCKCHAIN PLUS POSTGRESQL 10 The Latest and Most Interesting Features BITCOIN AND TAXES Cryptocurrency and Uncle Sam LINUXBOOT FOSS Project Spotlight ISSUE 284 | MARCH 2018 www.linuxjournal.com MARCH 2018 CONTENTS ISSUE 284 DEEP DIVE: Blockchain 95 Blockchain, Part I: Introduction and Cryptocurrency by Petros Koutoupis What makes both bitcoin and blockchain so exciting? What do they provide? Why is everyone talking about this? And, what does the future hold? 105 Blockchain, Part II: Configuring a Blockchain Network and Leveraging the Technology by Petros Koutoupis How to set up a private etherium blockchain using open-source tools and a look at some markets and industries where blockchain technologies can add value. 2 | March 2018 | http://www.linuxjournal.com CONTENTS 6 From the Editor—Doc Searls Help Us Cure Online Publishing of Its Addiction to Personal Data UPFRONT 18 FOSS Project Spotlight: LinuxBoot by David Hendricks, Ron Minnich, Chris Koch and Andrea Barberio 24 Readers’ Choice Awards 26 Shorter Commands by Kyle Rankin 29 For Open-Source Software, the Developers Are All of Us by Derek Zimmer 32 Taking Python to the Next Level by Joey Bernard 37 Learning IT Fundamentals by Kyle Rankin 40 Introducing Zero-K, a Real-Time Strategy Game for Linux by Oflameo 45 News Briefs COLUMNS 46 Kyle Rankin’s Hack and / What’s New in Qubes 4 52 Reuven M. Lerner’s At the Forge PostgreSQL 10: a Great New Version for a Great Database 64 Shawn Powers’ The Open-Source Classroom Cryptocurrency and the IRS 72 Zack Brown’s diff -u What’s New in Kernel Development 76 Susan Sons’ Under the Sink Security: 17 Things 86 Dave Taylor’s Work the Shell Shell Scripting and Security 178 Glyn Moody’s Open Sauce Looking Back: What Was Happening Ten Years Ago? LINUX JOURNAL (ISSN 1075-3583) is published monthly by Linux Journal, LLC.
    [Show full text]
  • Global File System 2
    Red Hat Enterprise Linux 6 Global File System 2 Red Hat Global File System 2 Last Updated: 2018-11-01 Red Hat Enterprise Linux 6 Global File System 2 Red Hat Global File System 2 Steven Levine Red Hat Customer Content Services [email protected] Legal Notice Copyright © 2017 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, 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 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 Agreement Emea
    RED HAT ENTERPRISE AGREEMENT EME A This Red Hat Enterprise Agreement, including all referenced appendices and documents located at URLs (the " Agreement "), is between Red Hat Limited (" Red Hat ") and the purchaser or user of Red Hat software and services who accepts the terms of this Agreement (“ Client ”). The effective date of this Agreement (“ Effective Date ”) is the earlier of the date that Client signs or accepts this Agreement or the date that Client uses Red Hat's software or services. 1. Scope of Agreement 1.1 Framework. This Agreement establishes a framework that will enable Red Hat to provide Software and Services to Client. “Software” means Red Hat Enterprise Linux, JBoss Enterprise Middleware and other software programs branded by Red Hat, its Affiliates and/or third parties including all modifications, additions or further enhancements delivered by Red Hat. The specific services (the “Services”) and/or Software that Red Hat will provide to Client will be described in an Order Form, signed by the parties or otherwise accepted by Red Hat, which may consist of (a) one or more mutually agreed order forms, statements of work, work orders or similar transaction documents, or (b) an order placed by Client through Red Hat's online store accessible from a Red Hat website. The parties agree that the terms of this Agreement will govern all purchases and use by Client of Software and Services unless otherwise agreed by the parties in writing. 1.2 Affiliates. Red Hat and Client agree that Affiliates of Client may acquire Software and Services from Red Hat or its Affiliates by entering an Order Form with Red Hat (or a Red Hat Affiliate) that incorporates the terms and conditions of this Agreement.
    [Show full text]