DOCSLIB.ORG

Administration Guide Administration Guide SUSE Linux Enterprise High Availability Extension 12 SP4 by Tanja Roth and Thomas Schraitle

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Administration Guide Administration Guide SUSE Linux Enterprise High Availability Extension 12 SP4 by Tanja Roth and Thomas Schraitle SUSE Linux Enterprise High Availability Extension 12 SP4 Administration Guide Administration Guide SUSE Linux Enterprise High Availability Extension 12 SP4 by Tanja Roth and Thomas Schraitle This guide is intended for administrators who need to set up, congure, and maintain clusters with SUSE® Linux Enterprise High Availability Extension. For quick and ecient conguration and administration, the High Availability Extension includes both a graphical user interface (GUI) and a command line interface (CLI). For performing key tasks, both approaches (GUI and CLI) are covered in detail in this guide. Thus, administrators can choose the appropriate tool that matches their needs. Publication Date: September 10, 2021 SUSE LLC 1800 South Novell Place Provo, UT 84606 USA https://documentation.suse.com Copyright © 2006–2021 SUSE LLC and contributors. All rights reserved. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or (at your option) version 1.3; with the Invariant Section being this copyright notice and license. A copy of the license version 1.2 is included in the section entitled “GNU Free Documentation License”. For SUSE trademarks, see http://www.suse.com/company/legal/ . All other third-party trademarks are the property of their respective owners. Trademark symbols (®, ™ etc.) denote trademarks of SUSE and its aliates. Asterisks (*) denote third-party trademarks. All information found in this book has been compiled with utmost attention to detail. However, this does not guarantee complete accuracy. Neither SUSE LLC, its aliates, the authors nor the translators shall be held liable for possible errors or the consequences thereof. Contents About This Guide xv 1 Available Documentation xvi 2 Giving Feedback xvii 3 Documentation Conventions xviii 4 Product Life Cycle and Support xix Support Statement for SUSE Linux Enterprise High Availability Extension xx • Technology Previews xxi I INSTALLATION, SETUP AND UPGRADE 1 1 Product Overview 2 1.1 Availability as Extension 2 1.2 Key Features 3 Wide Range of Clustering Scenarios 3 • Flexibility 3 • Storage and Data Replication 4 • Support for Virtualized Environments 4 • Support of Local, Metro, and Geo Clusters 4 • Resource Agents 5 • User-friendly Administration Tools 5 1.3 Benefits 6 1.4 Cluster Configurations: Storage 9 1.5 Architecture 12 Architecture Layers 12 • Process Flow 15 2 System Requirements and Recommendations 16 2.1 Hardware Requirements 16 2.2 Software Requirements 17 2.3 Storage Requirements 17 iii Administration Guide 2.4 Other Requirements and Recommendations 18 3 Installing the High Availability Extension 20 3.1 Manual Installation 20 3.2 Mass Installation and Deployment with AutoYaST 20 4 Using the YaST Cluster Module 23 4.1 Definition of Terms 23 4.2 YaST Cluster Module 25 4.3 Defining the Communication Channels 27 4.4 Defining Authentication Settings 32 4.5 Transferring the Configuration to All Nodes 33 Configuring Csync2 with YaST 34 • Synchronizing Changes with Csync2 35 4.6 Synchronizing Connection Status Between Cluster Nodes 37 4.7 Configuring Services 38 4.8 Bringing the Cluster Online 40 5 Upgrading Your Cluster and Updating Software Packages 42 5.1 Terminology 42 5.2 Upgrading your Cluster to the Latest Product Version 43 Supported Upgrade Paths for SLE HA and SLE HA Geo 44 • Required Preparations Before Upgrading 46 • Cluster Offline Upgrade 47 • Cluster Rolling Upgrade 49 5.3 Updating Software Packages on Cluster Nodes 52 5.4 For More Information 53 iv Administration Guide II CONFIGURATION AND ADMINISTRATION 54 6 Configuration and Administration Basics 55 6.1 Use Case Scenarios 55 6.2 Quorum Determination 56 Global Cluster Options 57 • Global Option no-quorum- policy 57 • Global Option stonith-enabled 58 • Corosync Configuration for Two-Node Clusters 58 • Corosync Configuration for N- Node Clusters 59 6.3 Cluster Resources 60 Resource Management 60 • Supported Resource Agent Classes 61 • Types of Resources 63 • Resource Templates 63 • Advanced Resource Types 64 • Resource Options (Meta Attributes) 67 • Instance Attributes (Parameters) 70 • Resource Operations 72 • Timeout Values 74 6.4 Resource Monitoring 75 6.5 Resource Constraints 77 Types of Constraints 77 • Scores and Infinity 80 • Resource Templates and Constraints 81 • Failover Nodes 82 • Failback Nodes 83 • Placing Resources Based on Their Load Impact 84 • Grouping Resources by Using Tags 87 6.6 Managing Services on Remote Hosts 87 Monitoring Services on Remote Hosts with Monitoring Plug- ins 88 • Managing Services on Remote Nodes with pacemaker_remote 89 6.7 Monitoring System Health 90 6.8 For More Information 92 7 Configuring and Managing Cluster Resources with Hawk2 94 7.1 Hawk2 Requirements 94 7.2 Logging In 95 v Administration Guide 7.3 Hawk2 Overview: Main Elements 96 Left Navigation Bar 97 • Top-Level Row 98 7.4 Configuring Global Cluster Options 98 7.5 Configuring Cluster Resources 100 Showing the Current Cluster Configuration (CIB) 101 • Adding Resources with the Wizard 102 • Adding Simple Resources 103 • Adding Resource Templates 105 • Modifying Resources 105 • Adding STONITH Resources 107 • Adding Cluster Resource Groups 108 • Adding Clone Resources 110 • Adding Multi-state Resources 111 • Grouping Resources by Using Tags 112 • Configuring Resource Monitoring 113 7.6 Configuring Constraints 116 Adding Location Constraints 116 • Adding Colocation Constraints 117 • Adding Order Constraints 119 • Using Resource Sets for Constraints 121 • For More Information 122 • Specifying Resource Failover Nodes 123 • Specifying Resource Failback Nodes (Resource Stickiness) 124 • Configuring Placement of Resources Based on Load Impact 125 7.7 Managing Cluster Resources 127 Editing Resources and Groups 128 • Starting Resources 128 • Cleaning Up Resources 129 • Removing Cluster Resources 130 • Migrating Cluster Resources 130 7.8 Monitoring Clusters 132 Monitoring a Single Cluster 132 • Monitoring Multiple Clusters 133 7.9 Using the Batch Mode 136 7.10 Viewing the Cluster History 140 Viewing Recent Events of Nodes or Resources 140 • Using the History Explorer for Cluster Reports 141 • Viewing Transition Details in the History Explorer 143 7.11 Verifying Cluster Health 145 vi Administration Guide 8 Configuring and Managing Cluster Resources (Command Line) 146 8.1 crmsh—Overview 146 Getting Help 147 • Executing crmsh's Subcommands 148 • Displaying Information about OCF Resource Agents 150 • Using crmsh's Shell Scripts 151 • Using crmsh's Cluster Scripts 152 • Using Configuration Templates 155 • Testing with Shadow Configuration 157 • Debugging Your Configuration Changes 158 • Cluster Diagram 158 8.2 Managing Corosync Configuration 158 8.3 Configuring Global Cluster Options 160 8.4 Configuring Cluster Resources 160 Loading Cluster Resources from a File 161 • Creating Cluster Resources 161 • Creating Resource Templates 162 • Creating a STONITH Resource 163 • Configuring Resource Constraints 164 • Specifying Resource Failover Nodes 167 • Specifying Resource Failback Nodes (Resource Stickiness) 168 • Configuring Placement of Resources Based on Load Impact 168 • Configuring Resource Monitoring 171 • Configuring a Cluster Resource Group 171 • Configuring a Clone Resource 172 8.5 Managing Cluster Resources 173 Showing Cluster Resources 173 • Starting a New Cluster Resource 175 • Cleaning Up Resources 175 • Removing a Cluster Resource 176 • Migrating a Cluster Resource 176 • Grouping/Tagging Resources 177 • Getting Health Status 177 8.6 Setting Passwords Independent of cib.xml 178 8.7 Retrieving History Information 178 8.8 For More Information 180 9 Adding or Modifying Resource Agents 181 9.1 STONITH Agents 181 9.2 Writing OCF Resource Agents 181 9.3 OCF Return Codes and Failure Recovery 183 vii Administration Guide 10 Fencing and STONITH 185 10.1 Classes of Fencing 185 10.2 Node Level Fencing 186 STONITH Devices 186 • STONITH Implementation 187 10.3 STONITH Resources and Configuration 188 Example STONITH Resource Configurations 188 10.4 Monitoring Fencing Devices 191 10.5 Special Fencing Devices 192 10.6 Basic Recommendations 194 10.7 For More Information 195 11 Storage Protection and SBD 196 11.1 Conceptual Overview 196 11.2 Overview of Manually Setting Up SBD 198 11.3 Requirements 198 11.4 Number of SBD Devices 199 11.5 Calculation of Timeouts 200 11.6 Setting Up the Watchdog 201 Using a Hardware Watchdog 201 • Using the Software Watchdog (softdog) 203 11.7 Setting Up SBD with Devices 204 11.8 Setting Up Diskless SBD 209 11.9 Testing SBD and Fencing 211 11.10 Additional Mechanisms for Storage Protection 212 Configuring an sg_persist Resource 212 • Ensuring Exclusive Storage Activation with sfex 214 11.11 For More Information 216 viii Administration Guide 12 Access Control Lists 217 12.1 Requirements and Prerequisites 217 12.2 Enabling Use of ACLs in Your Cluster 218 12.3 The Basics of ACLs 219 Setting ACL Rules via XPath Expressions 219 • Setting ACL Rules via Abbreviations 221 12.4 Configuring ACLs with Hawk2 222 12.5 Configuring ACLs with crmsh 224 13 Network Device Bonding 225 13.1 Configuring Bonding Devices with YaST 225 13.2 Hotplugging of Bonding Slaves 228 13.3 For More Information 230 14 Load Balancing 231 14.1 Conceptual Overview 231 14.2 Configuring Load Balancing with Linux Virtual Server 233 Director 233 • User Space Controller and Daemons 233 • Packet Forwarding 234 • Scheduling Algorithms 234 • Setting Up IP Load Balancing with YaST 235 • Further Setup 241 14.3 Configuring Load Balancing with HAProxy 241
Load more

Recommended publications
  • Fault-Tolerant Components on AWS
    Fault-Tolerant Components on AWS November 2019 This paper has been archived For the latest technical information, see the AWS Whitepapers & Guides page: Archivedhttps://aws.amazon.com/whitepapers Notices Customers are responsible for making their own independent assessment of the information in this document. This document: (a) is for informational purposes only, (b) represents current AWS product offerings and practices, which are subject to change without notice, and (c) does not create any commitments or assurances from AWS and its affiliates, suppliers or licensors. AWS products or services are provided “as is” without warranties, representations, or conditions of any kind, whether express or implied. The responsibilities and liabilities of AWS to its customers are controlled by AWS agreements, and this document is not part of, nor does it modify, any agreement between AWS and its customers. © 2019 Amazon Web Services, Inc. or its affiliates. All rights reserved. Archived Contents Introduction .......................................................................................................................... 1 Failures Shouldn’t Be THAT Interesting ............................................................................. 1 Amazon Elastic Compute Cloud ...................................................................................... 1 Elastic Block Store ........................................................................................................... 3 Auto Scaling ....................................................................................................................
    [Show full text]
  • Vsphere Availability Vmware Vsphere 6.5 Vmware Esxi 6.5 Vcenter Server 6.5
    vSphere Availability VMware vSphere 6.5 VMware ESXi 6.5 vCenter Server 6.5 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent editions of this document, see http://www.vmware.com/support/pubs. EN-002085-01 vSphere Availability You can ®nd the most up-to-date technical documentation on the VMware Web site at: http://www.vmware.com/support/ The VMware Web site also provides the latest product updates. If you have comments about this documentation, submit your feedback to: [email protected] Copyright © 2009–2017 VMware, Inc. All rights reserved. Copyright and trademark information. VMware, Inc. 3401 Hillview Ave. Palo Alto, CA 94304 www.vmware.com 2 VMware, Inc. Contents About vSphere Availability 5 Updated Information for vSphere Availability 7 1 Business Continuity and Minimizing Downtime 9 Reducing Planned Downtime 9 Preventing Unplanned Downtime 10 vSphere HA Provides Rapid Recovery from Outages 10 vSphere Fault Tolerance Provides Continuous Availability 11 Protecting the vCenter Server Appliance with vCenter High Availability 12 Protecting vCenter Server with VMware Service Lifecycle Manager 12 2 Creating and Using vSphere HA Clusters 13 How vSphere HA Works 13 vSphere HA Admission Control 21 vSphere HA Interoperability 26 Creating a vSphere HA Cluster 29 Configuring vSphere Availability Settings 31 Best Practices for vSphere HA Clusters 39 3 Providing Fault Tolerance for Virtual Machines 43 How Fault Tolerance
    [Show full text]
  • Rethinking Database High Availability with RDMA Networks
    Rethinking Database High Availability with RDMA Networks Erfan Zamanian1, Xiangyao Yu2, Michael Stonebraker2, Tim Kraska2 1 Brown University 2 Massachusetts Institute of Technology [email protected], fyxy, stonebraker, [email protected] ABSTRACT copy propagate to all the backup copies synchronously such that Highly available database systems rely on data replication to tol- any failed primary server can be replaced by a backup server. erate machine failures. Both classes of existing replication algo- The conventional wisdom of distributed system design is that rithms, active-passive and active-active, were designed in a time the network is a severe performance bottleneck. Messaging over when network was the dominant performance bottleneck. In essence, a conventional 10-Gigabit Ethernet within the same data center, these techniques aim to minimize network communication between for example, delivers 2–3 orders of magnitude higher latency and replicas at the cost of incurring more processing redundancy; a lower bandwidth compared to accessing the local main memory of trade-off that suitably fitted the conventional wisdom of distributed a server [3]. Two dominant high availability approaches, active- database design. However, the emergence of next-generation net- passive and active-active, both adopt the optimization goal of min- works with high throughput and low latency calls for revisiting imizing network overhead. these assumptions. With the rise of the next-generation networks, however, conven- In this paper, we first make the case that in modern RDMA- tional high availability protocol designs are not appropriate any- enabled networks, the bottleneck has shifted to CPUs, and there- more, especially in a setting of Local Area Network (LAN).
    [Show full text]
  • Storm Clouds Platform: a Cloud Computing Platform for Smart City Applications
    RESEARCH ARTICLE Storm Clouds Platform: a cloud computing platform for smart city applications Marco Battarra, Marco Consonni*, Samuele De Domenico and Andrea Milani Hewlett Packard Italiana S.R.L., 9, Via Di Vittorio Giuseppe – 20063 Cernusco Sul Naviglio, Italy Abstract: This paper describes our work on STORM CLOUDS[1], a project with the main objective of migrating smart-city services, that Public Authorities (PAs) currently provided using traditional Information Technology, to a cloud-based environment. Our organization was in charge of finding the technical solutions, so we designed and im- plemented a cloud computing solution called Storm Clouds Platform (SCP), for that purpose. In principle, the applica- tions we ported could run on a public-cloud service, like Amazon Web ServicesTM[2] or Microsoft® Azure[3], that pro- vide computational resources on a pay-per-use paradigm. However, these solutions have disadvantages due to their proprietary nature: vendor lock-in is one of the issues but other serious problems are related to the lack of full control on how data and applications are processed in the cloud. As an example, when using a public cloud, the users of the cloud services have very little control on the location where applications run and data are stored, if there is any. This is identi- fied as one of the most important obstacles in cloud computing adoption, particularly in applications manage personal data and the application provider has legal obligation of preserving end user privacy[4]. This paper explains how we faced the problem and the solutions we found. We designed a cloud computing platform — completely based on open-software components — that can be used for either implementing private clouds or for porting applications to public clouds.
    [Show full text]
  • High Availability Guide 12C (12.2.1.1) E73182-01
    Oracle® Fusion Middleware High Availability Guide 12c (12.2.1.1) E73182-01 June 2016 Oracle Fusion Middleware High Availability Guide, 12c (12.2.1.1) E73182-01 Copyright © 2013, 2016, Oracle and/or its affiliates. All rights reserved. Primary Author: Christine Ford Contributing Authors: Michael Blevins, Suvendu Ray, Lingaraj Nayak, Maneesh Jain, Peter LaQuerre Contributors: Gururaj BS 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.
    [Show full text]
  • Web Application Hosting in the AWS Cloud AWS Whitepaper Web Application Hosting in the AWS Cloud AWS Whitepaper
    Web Application Hosting in the AWS Cloud AWS Whitepaper Web Application Hosting in the AWS Cloud AWS Whitepaper Web Application Hosting in the AWS Cloud: AWS Whitepaper Copyright © Amazon Web Services, Inc. and/or its affiliates. All rights reserved. Amazon's trademarks and trade dress may not be used in connection with any product or service that is not Amazon's, in any manner that is likely to cause confusion among customers, or in any manner that disparages or discredits Amazon. All other trademarks not owned by Amazon are the property of their respective owners, who may or may not be affiliated with, connected to, or sponsored by Amazon. Web Application Hosting in the AWS Cloud AWS Whitepaper Table of Contents Abstract ............................................................................................................................................ 1 Abstract .................................................................................................................................... 1 An overview of traditional web hosting ................................................................................................ 2 Web application hosting in the cloud using AWS .................................................................................... 3 How AWS can solve common web application hosting issues ........................................................... 3 A cost-effective alternative to oversized fleets needed to handle peaks ..................................... 3 A scalable solution to handling unexpected traffic
    [Show full text]
  • Oracle Database High Availability Overview, 10G Release 2 (10.2) B14210-02
    Oracle® Database High Availability Overview 10g Release 2 (10.2) B14210-02 July 2006 Oracle Database High Availability Overview, 10g Release 2 (10.2) B14210-02 Copyright © 2005, 2006, Oracle. All rights reserved. Primary Author: Immanuel Chan Contributors: Andrew Babb, Tammy Bednar, Barb Lundhild, Rahim Mau, Valarie Moore, Ashish Ray, Vivian Schupmann, Michael T. Smith, Lawrence To, Douglas Utzig, James Viscusi, Shari Yamaguchi The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited. The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose. If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.
    [Show full text]
  • Zero-Downtime Deployment in a High Availability Architecture - Controlled Experiment of Deployment Automation in a High Availability Architecture
    Bachelor Degree Project Zero-Downtime Deployment in a High Availability Architecture - Controlled experiment of deployment automation in a high availability architecture. Author: Axel Nilsson ​ Supervisor: Johan Hagelbäck ​ Semester. HT 2018 ​ Subject: Computer Science ​ Abstract Computer applications are no longer local installations on our computers. Many modern web applications and services rely on an internet connection to a centralized server to access the full functionality of the application. High availability architectures can be used to provide redundancy in case of failure to ensure customers always have access to the server. Due to the complexity of such systems and the need for stability, deployments are often avoided and new features and bug fixes cannot be delivered to the end user quickly. In this project, an automation system is proposed to allow for deployments to a high availability architecture while ensuring high availability. The purposed automation system is then tested in a controlled experiment to see if it can deliver what it promises. During low amounts of traffic, the deployment system showed it could make a deployment with a statistically insignificant change in error rate when compared to normal operations. Similar results were found during medium to high levels of traffic for successful deployments, but if the system had to recover from a failed deployment there was an increase in errors. However, the response time during the experiment showed that the system had a significant effect on the response time
    [Show full text]
  • AIT Haproxy.Key
    HEIG-VD | TIC – Technologies de l’Information et de la Communication HAProxy (C) 2015 Marcel Graf HEIG-VD | TIC – Technologies de l’Information et de la Communication HAProxy ■ HAProxy (High Availability Proxy) is a load balancer implemented in software ■ Available as Open Source (GPL/LGPL license) (http://www.haproxy.org) ■ Available as commercial product (http://www.haproxy.com) ■ Also available as appliance: ALOHA ■ Runs on FreeBSD, Linux, OpenBSD and Solaris ■ Written by Willy Tarreau in 2000 ■ Willy is the maintainer of the Linux 2.4 kernel ■ Lives in Fontenay aux Roses ■ Used by high-profile websites: GitHub, Bitbucket, Stack Overflow, Reddit, Tumblr, Twitter 2 Administration IT | HAProxy | Année 2015/16 (C) 2015 Marcel Graf HEIG-VD | TIC – Technologies de l’Information et de la Communication HAProxy Features ■ HAProxy can be used for ■ Load balancing on TCP layer and HTTP layer ■ Normalization / filtering of TCP and HTTP traffic ■ HTTP rewriting ■ SSL offloading ■ HTTP compression offloading ■ Traffic regulation ■ Protection against DDoS and service abuse ■ … 3 Administration IT | HAProxy | Année 2015/16 (C) 2015 Marcel Graf HEIG-VD | TIC – Technologies de l’Information et de la Communication HAProxy operations ■ Health checks ■ HAProxy periodically sends probes to servers to check if they are still operational. A probe can be superficial or go deeper: ■ ping to server’s IP address (TCP mode) ■ TCP connection to server’s HTTP port (TCP mode) ■ HTTP request to server (HTTP mode) ■ Based on health checks HAProxy sets a server’s state to UP or DOWN ■ Server administrative state ■ The administrator can set a server into one of three administrative states ■ READY — Server is in normal mode, accepting requests ■ DRAIN — Removes server from load balancing, but still allows it to be health-checked and accept new persistent connections.
    [Show full text]
  • Cloud Onload Haproxy Cookbook
    Cloud Onload® HAProxy Cookbook The information disclosed to you hereunder (the “Materials”) is provided solely for the selection and use of Xilinx products. To the maximum extent permitted by applicable law: (1) Materials are made available "AS IS" and with all faults, Xilinx hereby DISCLAIMS ALL WARRANTIES AND CONDITIONS, EXPRESS, IMPLIED, OR STATUTORY, INCLUDING BUT NOT LIMITED TO WARRANTIES OF MERCHANTABILITY, NON-INFRINGEMENT, OR FITNESS FOR ANY PARTICULAR PURPOSE; and (2) Xilinx shall not be liable (whether in contract or tort, including negligence, or under any other theory of liability) for any loss or damage of any kind or nature related to, arising under, or in connection with, the Materials (including your use of the Materials), including for any direct, indirect, special, incidental, or consequential loss or damage (including loss of data, profits, goodwill, or any type of loss or damage suffered as a result of any action brought by a third party) even if such damage or loss was reasonably foreseeable or Xilinx had been advised of the possibility of the same. Xilinx assumes no obligation to correct any errors contained in the Materials or to notify you of updates to the Materials or to product specifications. You may not reproduce, modify, distribute, or publicly display the Materials without prior written consent. Certain products are subject to the terms and conditions of Xilinx’s limited warranty, please refer to Xilinx’s Terms of Sale which can be viewed at https://www.xilinx.com/legal.htm#tos; IP cores may be subject to warranty and support terms contained in a license issued to you by Xilinx.
    [Show full text]
  • Updates from the Open Quantum Safe Project
    Updates from the Open Quantum Safe Project Open Quantum Safe core team: Michael Baentsch Vlad Gheorghiu, evolutionQ & University of Waterloo Basil Hess, IBM Research Christian Paquin, Microsoft Research John Schanck, University of Waterloo Douglas Stebila, University of Waterloo Goutam Tamvada, University of Waterloo April 23, 2021 Abstract The Open Quantum Safe (OQS) project is an open-source project that aims to support the development and prototyping of quantum-resistant cryptography. This short note provides an update on the tools OQS makes available. 1 Introduction The Open Quantum Safe (OQS) project1 is an open-source project that aims to support the develop- ment and prototyping (of applications) of quantum-resistant cryptography. OQS consists of the following main lines of work: liboqs, an open source C library for quantum- resistant cryptographic algorithms, and prototype integrations into protocols and applications, including a fork of the widely used OpenSSL library. These tools support research by ourselves and others. To reduce the hurdle for getting started and to aid the uptake and use of these components, our tools are also available as ready-to-use binaries in the form of Docker images and test servers. In this short note, we provide an update on the Open Quantum Safe project. 2 liboqs liboqs is an open source C library for quantum-safe cryptographic algorithms. liboqs makes accessible a collection of open-source implementations of quantum-safe key encapsulation mechanism (KEM) and digital signature algorithms through a common API. liboqs builds on Linux, macOS, and Windows, on Intel, AMD, and ARM platforms. Some of the implementations of these algorithms have been directly contributed to liboqs by members of the NIST submission teams; others are incorporated from the PQClean project.
    [Show full text]
  • Red Hat Codeready Containers 1.19 Getting Started Guide
    Red Hat CodeReady Containers 1.19 Getting Started Guide Quick-start guide to using and developing with CodeReady Containers Last Updated: 2020-12-04 Red Hat CodeReady Containers 1.19 Getting Started Guide Quick-start guide to using and developing with CodeReady Containers Kevin Owen [email protected] Legal Notice Copyright © 2020 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.
    [Show full text]