DOCSLIB.ORG

Routinator User Manual

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Routinator User Manual Routinator User Manual NLnet Labs Sep 20, 2021 GETTING STARTED 1 Installation 3 1.1 System Requirements..........................................3 1.2 Quick Start................................................3 1.3 Updating.................................................5 1.4 Installing Specific Versions.......................................6 1.5 Installing From Source..........................................7 1.6 Notes...................................................8 2 Installation Notes 9 2.1 Using Native TLS Instead of Rustls...................................9 2.2 Statically Linked Routinator.......................................9 2.3 Platform Specific Instructions...................................... 10 3 Initialisation 15 3.1 Trust Anchor Locators.......................................... 15 3.2 Performing a Test Run.......................................... 17 4 Data Processing 19 4.1 Fetching................................................. 19 4.2 Validating................................................. 20 4.3 Storing.................................................. 21 5 VRP Output Formats 23 6 Configuration 27 7 Local Exceptions 29 8 Logging 31 8.1 Interactive Mode............................................. 31 8.2 Detached Server Mode.......................................... 31 9 Running Interactively 33 10 Validity Checker 35 10.1 Reading Input From a File........................................ 36 11 Dumping Stored Data 39 12 Running as a Daemon 41 i 13 RTR Service 43 13.1 Secure Transports............................................ 43 14 HTTP Service 47 15 User Interface 49 15.1 Prefix Check............................................... 49 15.2 Reverse Proxy with NGINX....................................... 52 16 API Endpoints 53 17 Monitoring 55 17.1 Metrics.................................................. 55 17.2 Grafana.................................................. 56 18 Manual Page 57 18.1 Description................................................ 57 18.2 Options.................................................. 57 18.3 Commands................................................ 60 18.4 Trust Anchor Locators.......................................... 66 18.5 Configuration File............................................ 66 18.6 HTTP Service.............................................. 69 18.7 Logging.................................................. 70 18.8 Validation................................................. 70 18.9 Relaxed Decoding............................................ 71 18.10 Signals.................................................. 71 18.11 Exit Status................................................ 71 19 JSON Metrics 73 19.1 Publication Metrics............................................ 74 19.2 Rsync Update Metrics.......................................... 75 19.3 RRDP Update Metrics.......................................... 75 19.4 RTR Server Metrics........................................... 76 19.5 HTTP Server Metrics.......................................... 76 20 Prometheus Metrics 77 20.1 Publication Metrics............................................ 77 20.2 Rsync Update Metrics.......................................... 78 20.3 RRDP Update Metrics.......................................... 78 20.4 RTR Server Metrics........................................... 79 20.5 HTTP Server Metrics.......................................... 79 21 Glossary 81 Index 83 ii Routinator User Manual Routinator 3000 is free, open source RPKI (Resource Public Key Infrastructure) Relying Party software written by NLnet Labs in the Rust programming language. The application is designed to be secure and have great portability. It is a lightweight implementation that can run effortlessly on almost any operating system using minimalist hardware. Routinator connects to the Trust Anchors of the five Regional Internet Registries (RIRs) — APNIC, AFRINIC, ARIN, LACNIC and RIPE NCC — downloads all of the certificates and ROAS (Route Origin Attestations) in the various repositories, verifies the signatures and makes the result available for use in your BGP workflow. It is a full featured software package that can perform RPKI validation as a one-time operation and store the result on disk in formats such as CSV and JSON, or run as a service that periodically downloads and verifies RPKI data. Routers can connect to Routinator to fetch verified data via the RPKI-RTR (RPKI-to-Router) protocol. The built-in HTTP server offers a user interface and endpoints for the various file formats, as well as logging, status and Prometheus monitoring. If you run into a problem with Routinator or you have a feature request, please create an issue on Github. We are also happy to accept your pull requests. For general discussion and exchanging operational experiences we provide a mailing list and a Discord server. You can follow the adventures of Routinator on Twitter and listen to its favourite songs on Spotify. Tip: To learn more about Resource Public Key Infrastructure, please refer to the RPKI Community Documentation. GETTING STARTED 1 Routinator User Manual 2 GETTING STARTED CHAPTER ONE INSTALLATION 1.1 System Requirements Routinator has minimal system requirements. When choosing a system, make sure you have 1GB of available memory and 4GB of disk space for the application. This will give you ample margin for the RPKI repositories to grow over time, as adoption increases. A powerful CPU is not required. As new RPKI repositories can emerge in any IP address range and on any domain name, outbound traffic must not be blocked based on IP or DNS in any way. Routinator only needs to establish outbound connections via HTTPS and rsync, on ports 443 and 873, respectively. 1.2 Quick Start New in version 0.9: RPM packages Getting started with Routinator is really easy by either installing a binary package for Debian and Ubuntu or for Red Hat Enterprise Linux and CentOS. You can also run with Docker or build from Cargo, Rust’s build system and package manager. Debian Packages RPM Packages Docker Cargo If you have a machine with an amd64/x86_64 architecture running a recent Debian or Ubuntu distribution, you can install Routinator from our software package repository. To use this repository, add the line below that corresponds to your operating system to your /etc/apt/sources. list or /etc/apt/sources.list.d/: deb [arch=amd64] https://packages.nlnetlabs.nl/linux/debian/ stretch main deb [arch=amd64] https://packages.nlnetlabs.nl/linux/debian/ buster main deb [arch=amd64] https://packages.nlnetlabs.nl/linux/debian/ bullseye main deb [arch=amd64] https://packages.nlnetlabs.nl/linux/ubuntu/ xenial main deb [arch=amd64] https://packages.nlnetlabs.nl/linux/ubuntu/ bionic main deb [arch=amd64] https://packages.nlnetlabs.nl/linux/ubuntu/ focal main Then run the following commands to add the public key and update the repository list: wget -qO- https://packages.nlnetlabs.nl/aptkey.asc | sudo apt-key add - sudo apt update 3 Routinator User Manual You can then install, initialise, enable and start Routinator by running these commands. Note that routinator-init is slightly different than the command used with Cargo: sudo apt install routinator sudo routinator-init # Follow instructions provided sudo systemctl enable --now routinator By default, Routinator will start the RTR server on port 3323 and the HTTP server on port 8323. These, and other values can be changed in the configuration file located in /etc/routinator/routinator.conf. You can check the status of Routinator with: sudo systemctl status routinator You can view the logs with: sudo journalctl --unit=routinator If you have a machine with an amd64/x86_64 architecture running a RHEL (Red Hat Enterprise Linux)/CentOS 7 or 8 distribution, or a compatible OS such as Rocky Linux, you can install Routinator from our software package repository. To use this repository, create a file named /etc/yum.repos.d/nlnetlabs.repo, enter this configuration and save it: [nlnetlabs] name=NLnet Labs baseurl=https://packages.nlnetlabs.nl/linux/centos/$releasever/main/$basearch enabled=1 Then run the following command to add the public key: sudo rpm --import https://packages.nlnetlabs.nl/aptkey.asc You can then install, initialise, enable and start Routinator by running these commands. Note that routinator-init is slightly different than the command used with Cargo: sudo yum install -y routinator sudo routinator-init # Follow instructions provided sudo systemctl enable --now routinator By default, Routinator will start the RTR server on port 3323 and the HTTP server on port 8323. These, and other values can be changed in the configuration file located in /etc/routinator/routinator.conf. You can check the status of Routinator with: sudo systemctl status routinator You can view the logs with: sudo journalctl --unit=routinator Due to the impracticality of complying with the ARIN TAL distribution terms in an unsupervised Docker environment, before launching the container it is necessary to first review and agree to the ARIN Relying Party Agreement (RPA). If you agree to the terms, you can let the Routinator Docker image install the TALs into a mounted volume that is later reused for the server: 4 Chapter 1. Installation Routinator User Manual # Create a Docker volume to persist TALs in sudo docker volume create routinator-tals # Review the ARIN terms. # Run a disposable container to install TALs. sudo docker run --rm -v routinator-tals:/home/routinator/.rpki-cache/tals \ nlnetlabs/routinator init -f --accept-arin-rpa
Load more

Recommended publications
  • Technology Overview New Features Backupedge
    Technology Overview - BackupEDGE™ Introduction to the New Features in BackupEDGE 3.x Technology Overview BackupEDGE has a long history of providing reliable data protection for New Features many thousands of users. As operating systems, storage devices and BackupEDGE 3.x usage needs and tendencies have changed over the years, it has continuously met the challenge of providing inexpensive, stable backup and disaster recovery on a variety of UNIX and Linux platforms. Clients routinely find new and clever ways to utilize products. Storage devices have taken on new and exciting features, and incredible capacities. Products designed years ago had built-in limits that were thought to be beyond comprehension. Today, these limits are routinely exceeded. The need for data security is even more apparent. We’re constantly asking our To continue to meet the evolving needs of our clients, we are always clients what tools our asking what features of our products they find most useful, what products need to serve them improvements we can make, and what new requirements they have. better. We’ve used this knowledge to map out new product strategies designed to anticipate the needs of the next generation of users, systems and storage products. This has resulted in the creation of BackupEDGE 3.x, with a combination of internal improvements, new features and enhanced infrastructure designed to become the backbone of a new generation of storage software. Summary of Major Changes and Additions BackupEDGE 3.x features include: • Improvements to partition sizing, UEFI table cleanup after DR, and SharpDrive debugging (03.04.01 build 3). • Support for Rocky Linux 8.4 and AlmaLinux 8.4 (03.04.01 build 2).
    [Show full text]
  • Guest OS Compatibility Guide
    Guest OS Compatibility Guide Guest OS Compatibility Guide Last Updated: September 29, 2021 For more information go to vmware.com. Introduction VMware provides the widest virtualization support for guest operating systems in the industry to enable your environments and maximize your investments. The VMware Compatibility Guide shows the certification status of operating system releases for use as a Guest OS by the following VMware products: • VMware ESXi/ESX Server 3.0 and later • VMware Workstation 6.0 and later • VMware Fusion 2.0 and later • VMware ACE 2.0 and later • VMware Server 2.0 and later VMware Certification and Support Levels VMware product support for operating system releases can vary depending upon the specific VMware product release or update and can also be subject to: • Installation of specific patches to VMware products • Installation of specific operating system patches • Adherence to guidance and recommendations that are documented in knowledge base articles VMware attempts to provide timely support for new operating system update releases and where possible, certification of new update releases will be added to existing VMware product releases in the VMware Compatibility Guide based upon the results of compatibility testing. Tech Preview Operating system releases that are shown with the Tech Preview level of support are planned for future support by the VMware product but are not certified for use as a Guest OS for one or more of the of the following reasons: • The operating system vendor has not announced the general availability of the OS release. • Not all blocking issues have been resolved by the operating system vendor.
    [Show full text]
  • Centos and OS Support
    CentOS and OS support Antoine Delvaux ・ PSNC / GÉANT project ・ [email protected] Mark Feit ・ Internet2 ・ [email protected] nd 2 European perfSONAR User Workshop 14-15 April 2021 perfSONAR is developed by a partnership of ©2021 The perfSONAR Project and its Contributors ・ Licensed CC BY-SA 4.0 ・ https://www.perfsonar.net perfSONAR is running on different OSes ● CentOS ○ And some Red Hat derivatives, but you’re on your own ● Debian and Ubuntu ○ And some other Debian derivatives, but you’re on your own ● The times, they are a-changing... 2 CentOS 3 CentOS 7 ● End of life is June 30, 2024. ● perfSONAR support will continue until then. 4 CentOS 8 ● July, 2019 IBM closes Red Hat acquisition ● December, 2020 New CentOS 8 EOL December, 2021 Eight years ahead of originally-scheduled 2029 5 CentOS Stream • What Was: Fedora → Red Hat Enterprise Linux → CentOS CentOS derived from very-stable EL code Infrequent releases • What Is: Fedora → CentOS Stream → Red Hat Enterprise Linux CentOS derived from Fedora ahead of EL development Rolling releases Welcome to the EL beta program! • Not what people running production systems want. 6 CentOS 8 Alternatives Based on In General Community Distribution Free Stable Code Release Development Red Hat Enterprise Linux ✔ ✔ CentOS Stream ✔ ✔ Oracle Linux ✔ ✔ ✔ Rocky Linux ✔ ✔ ✔ Alma Linux ✔ ✔ ✔ ✔ 7 Alma Linux Checks All the Boxes • Free • Based on stable code • In general release • March 31,2021 • Community development • Non-profit foundation • $1M annual sponsorship from CloudLinux, Inc. • Deployed on Internet2 Next-Generation Infrastructure PoP systems • Two perfSONAR nodes (in Docker containers) • Internal network management applications 8 Future Development on EL-Derived Linux • CentOS is our primary development platform.
    [Show full text]
  • Future Linux Distribution Scenarios
    Future Linux Distribution Scenarios Tim Bell IT-CM IT Management Meeting 14.12.2020 CentOS 7/8 (was 2019, now out of date) ● Within the (previous commitment) release ● Full support (enhancements etc.) first 5 years ● Maintenance support next 5 years ● Extended support later available only RHEL($$) CentOS Governance ● Rebuild mandate as community open source Linux, binary compatible with Red Hat Enterprise Linux ● Red Hat employed all of the community members in 2014 ● And IBM purchased Red Hat in 2019 for 34B USD ● Board structure has 11 members with 3 non-Red Hat including CERN and Fermilab employees ● CERN has hosted and participated in community events ● e.g. CentOS dojos at CERN - 2018, 2017 ● FOSDEM CERN situation before Dec 8th 2020 ● Production ● CERN CentOS 7 – 40K hosts - Majority of OS build work done upstream ● WLCG physics workloads ● Online ● Services (prior to C8 availability Q2 2020) ● CentOS 8 – 4K hosts – OS release from upstream build only, local automation ● New services starting with this ● Would become default towards the end of Run 3 in 2024 ● Retired (Nov 2020) ● Scientific Linux 6 ● No further updates available Previous Red Hat model FEDORA XX-1 FEDORA XX FEDORA XX+1 RHEL X RHEL X.0 RHEL X.1 RHEL X.Y alpha, beta GA CentOS X.0 CentOS X.1 CentOS X.Y Open development 10 years cycle Closed development Credit: Thomas Oulevey, BE-CSS Previous CentOS schedule Release Beta avail Production Maintenance End of Life CentOS 7 2014-07 2019-07 2024-06 CentOS 8 rebuild 2019-09 2024-08 2029-05 CentOS 8 stream 2019-09 2024-08 2029-08 CentOS 9 (est.) 2021 2023 2028 ● CentOS stream is a distro derived from the very latest patches for RHEL (i.e.
    [Show full text]
  • How to Download Red Hat Linux Iso for Vmware Vmware Workstation 3.2
    how to download red hat linux iso for vmware VMware Workstation 3.2. The easiest method of installing Red Hat Linux 6.x in a virtual machine is to use the standard Red Hat distribution CD. The notes below describe an installation using the standard distribution CD; however, installing Red Hat Linux 6.x via the boot floppy/network method is supported as well. Before installing the operating system, be sure that you have already created a directory for the new virtual machine and configured it using the VMware Workstation New Virtual Machine Wizard (on Windows hosts) or Configuration Wizard (on Linux hosts). Caution: Red Hat Linux 6.2 does not run on Pentium 4 processors. It also does not run on Xeon processors that are branded Xeon, with no qualifier, or Xeon-MP (Pentium III Xeon processors are OK). Note: Due to VGA performance issues installing Red Hat 6.1 and 6.2 with the graphics mode installer, we highly recommend you install the operating system with the text mode installer. At the Red Hat 6.1 or 6.2 CD boot prompt, you are offered the following choices: To install or upgrade a system . in graphical mode . To install or upgrade a system . in text mode, type: text <ENTER>. To enable expert mode, . Use the function keys listed below . Choose the text mode installer by typing text followed by Enter. Note: D uring the Red Hat Linux 6.x installation, a standard VGA16 X server (without support for the VMware Workstation X server) is installed. To get an accelerated SVGA X server running inside the virtual machine, you should install the VMware Tools package immediately after installing Red Hat Linux 6.x.
    [Show full text]
  • Future Linux Distribution Scenarios
    Future Linux Distribution Scenarios Tim Bell [email protected] CERN IT-CM Grid Deployment Board 12.01.2021 CentOS 7/8 (was 2019, now out of date) ● Within the (previous commitment) release ● Full support (enhancements etc.) first 5 years ● Maintenance support next 5 years ● Extended support later available only RHEL($) CentOS Governance ● Rebuild mandate as community open source Linux, binary compatible with Red Hat Enterprise Linux ● Red Hat employed all of the community members in 2014 ● And IBM purchased Red Hat in 2019 for 34B USD ● Board structure has 11 members with 3 non-Red Hat including CERN and Fermilab employees ● CERN has hosted and participated in community events ● e.g. CentOS dojos at CERN - 2018, 2017 ● FOSDEM CERN situation before Dec 8th 2020 ● Production ● CERN CentOS 7 – 40K hosts - Majority of OS build work done upstream ● WLCG physics workloads ● Online ● Services (prior to C8 availability Q2 2020) ● CentOS 8 – 4K hosts – OS release from upstream build only, local automation ● New services starting with this ● Would become default towards the end of Run 3 in 2024 ● Retired (Nov 2020) ● Scientific Linux 6 ● No further updates available Previous Red Hat model FEDORA XX-1 FEDORA XX FEDORA XX+1 RHEL X RHEL X.0 RHEL X.1 RHEL X.Y alpha, beta GA CentOS X.0 CentOS X.1 CentOS X.Y Open development 10 years cycle Closed development Credit: Thomas Oulevey, BE-CSS Previous CentOS schedule Release Beta avail Production Maintenance End of Life CentOS 7 2014-07 2019-07 2024-06 CentOS 8 rebuild 2019-09 2024-08 2029-05 CentOS 8 stream 2019-09 2024-08 2029-08 CentOS 9 (est.) 2021 2023 2028 ● CentOS stream is a distro derived from the very latest patches for RHEL (i.e.
    [Show full text]
  • IBM: Latest on Fedora 34 and Alternative to Centos, Almalinux
    Published on Tux Machines (http://www.tuxmachines.org) Home > content > IBM: Latest on Fedora 34 and Alternative to CentOS, AlmaLinux IBM: Latest on Fedora 34 and Alternative to CentOS, AlmaLinux By Roy Schestowitz Created 13/01/2021 - 8:49pm Submitted by Roy Schestowitz on Wednesday 13th of January 2021 08:49:05 PM Filed under Red Hat [1] Fedora 34 To Ship An ISO With The i3 Window Manager - Phoronix [2] While the i3 window manager has been around for more than a decade, it's taken until now for an i3 window manager spin of Fedora to be solicited and approved. Following the creation of a Fedora i3 special interest group last year, approved this week is providing an official Fedora spin with the i3 window manager in place of other desktop environments / window managers. This is the first Fedora release image to make use of a tiling window manager. Fedora Looks To Overhaul Its Community Outreach - Phoronix [3] In addition to pursuing many technical changes for its Linux distribution like systemd-oomd by default, Btrfs Zstd compression, and standalone XWayland releases, the Fedora project is also looking to overhaul its community outreach this year. Fedora's "Community Outreach Revamp" is to focus on existing outreach teams within Fedora that are "struggling to function" or need greater support for success. Open Mainframe Tessia Makes It Easy To Run Linux On Mainframe [4] Open Mainframe Project recently announced a new project called Tessia that?s designed to automate all the processes involving installation and configuration of Linux on Z systems.
    [Show full text]
  • Centos and OS Support
    CentOS and OS support Antoine Delvaux ・ PSNC / GÉANT project ・ [email protected] Mark Feit ・ Internet2 ・ [email protected] nd 2 European perfSONAR User Workshop 14-15 April 2021 perfSONAR is developed by a partnership of ©2021 The perfSONAR Project and its Contributors ・ Licensed CC BY-SA 4.0 ・ https://www.perfsonar.net perfSONAR is running on different OSes ● CentOS ○ And some Red Hat derivatives, but you’re on your own ● Debian and Ubuntu ○ And some other Debian derivatives, but you’re on your own ● The times, they are a-changing... 2 CentOS 3 CentOS 7 ● End of life is June 30, 2024. ● perfSONAR support will continue until then. 4 CentOS 8 ● July, 2019 IBM closes Red Hat acquisition ● December, 2020 New CentOS 8 EOL December, 2021 Eight years ahead of originally-scheduled 2029 5 CentOS Stream • What Was: Fedora → Red Hat Enterprise Linux → CentOS CentOS derived from very-stable EL code Infrequent releases • What Is: Fedora → CentOS Stream → Red Hat Enterprise Linux CentOS derived from Fedora ahead of EL development Rolling releases Welcome to the EL beta program! • Not what people running production systems want. 6 CentOS 8 Alternatives Based on In General Community Distribution Free Stable Code Release Development Red Hat Enterprise Linux ✔ ✔ CentOS Stream ✔ ✔ Oracle Linux ✔ ✔ ✔ Rocky Linux ✔ ✔ ✔ Alma Linux ✔ ✔ ✔ ✔ 7 Alma Linux Checks All the Boxes • Free • Based on stable code • In general release • March 31,2021 • Community development • Non-profit foundation • $1M annual sponsorship from CloudLinux, Inc. • Deployed on Internet2 Next-Generation Infrastructure PoP systems • Two perfSONAR nodes (in Docker containers) • Internal network management applications 8 Future Development on EL-Derived Linux • CentOS is our primary development platform.
    [Show full text]
  • Moving from Centos Linux to Pop! OS by Rex Djere Of
    Moving from CentOS Linux to Pop!_OS by Rex Djere of https://saxtalk.com/ Summary In 2020, I decided that I wanted to add some light gaming to my repertoire. I bought the most popular Logitech game controller on Amazon (the Logitech Gamepad F310), and I assumed that since it was so popular, it would work in CentOS 8 with no problems. When the gamepad arrived, I fired up Extreme Tux Racer, but the gamepad wasn’t recognized. In this article, I will describe why this lack of Logitech F310 gamepad support in CentOS 8 motivated me to switch from CentOS 8 to Pop!_OS 20.10. From Fedora to CentOS to Pop!_OS I spent almost 20 years in the Red Hat/CentOS/Fedora ecosystem, starting with Fedora 1. I ran every Fedora Linux from Fedora 1 to Fedora 30, but in 2019, I decided that I wanted to focus on desktop computer stability, so I switched to the rock solid Linux distribution known as CentOS 8. I absolutely loved CentOS 8 for the year that I ran it: it never crashed, and it was the most stable computer operating system that I have ever used. However, I decided in 2020 that I wanted to start playing games on my desktop computer to keep my mind sharp. I remembered how much I loved playing Tux Racer back in the day. I went onto Amazon.com looking for a good, well-reviewed, and affordable game controller, and the Logitech F310 wired gamepad kept coming up in my Amazon searches. The price was very reasonable.
    [Show full text]
  • Beyond the End of Centos
    Beyond the End of CentOS As if web hosting providers didn’t have enough on their plates, here comes yet another bump in the road, albeit one that will require some serious infrastructure updates. I’m talking about the EOL (end of life) of CentOS Project as we know it. That’s right, CentOS, the operating system of choice for hundreds of web hosting providers across the globe is being tossed in lieu of CentOS Stream. CentOS is a fork of Red Hat Enterprise Linus (RHEL) and has for years been the popular choice for web hosting providers to deploy on its production servers. Why? It’s always been rock solid in stability and compatibility. The new CentOS Stream will track just ahead of current RHEL releases. Going forward, CentOS Stream will serve as the upstream (development) branch of Red Hat Enterprise Linux. CentOS Linux 7 will be produced through the remainder of the RHEL 7 life cycle (four years). CentOS Linux 8 as a rebuild of RHEL , will end at the end of 2021. Per CentOS: “CentOS Stream will also be the centerpiece of a major shift in collaboration among the CentOS Special Interest Groups (SIGs). This ensures SIGs are developing and testing against what becomes the next version of RHEL. This also provides SIGs a clear single goal, rather than having to build and test for two releases. It gives the CentOS contributor community a great deal of influence in the future of RHEL. And it removes confusion around what “CentOS” means in the Linux distribution ecosystem.” They go on to recommend: “When CentOS Linux 8 (the rebuild of RHEL8) ends, your best option will be to migrate to CentOS Stream 8, which is a small delta from CentOS Linux 8, and has regular updates like traditional CentOS Linux releases.
    [Show full text]
  • Download Latest Version of Cups for Centos Download Latest Version of Cups for Centos
    download latest version of cups for centos Download latest version of cups for centos. Completing the CAPTCHA proves you are a human and gives you temporary access to the web property. What can I do to prevent this in the future? If you are on a personal connection, like at home, you can run an anti-virus scan on your device to make sure it is not infected with malware. If you are at an office or shared network, you can ask the network administrator to run a scan across the network looking for misconfigured or infected devices. Another way to prevent getting this page in the future is to use Privacy Pass. You may need to download version 2.0 now from the Chrome Web Store. Cloudflare Ray ID: 66a6f5b83ee516a1 • Your IP : 188.246.226.140 • Performance & security by Cloudflare. Linux downloads (Red Hat family) PostgreSQL is available on these platforms by default. However, each version of the platform normally "snapshots" a specific version of PostgreSQL that is then supported throughout the lifetime of this platform. Since this can often mean a different version than preferred, the PostgreSQL project provides a repository of packages of all supported versions for the most common distributions. PostgreSQL Yum Repository. The PostgreSQL Yum Repository will integrate with your normal systems and patch management, and provide automatic updates for all supported versions of PostgreSQL throughout the support lifetime of PostgreSQL. The PostgreSQL Yum Repository currently supports: Red Hat Enterprise Linux Rocky Linux CentOS Scientific Linux Oracle Linux Fedora * * Note : due to the shorter support cycle on Fedora, all supported versions of PostgreSQL are not available on this platform.
    [Show full text]
  • IBM Spectrum Scale Frequently Asked Questions and Answers
    IBM Spectrum Scale Frequently Asked Questions and Answers IBM Spectrum Scale Overview IBM Spectrum® Scale, based on technology from IBM® General Parallel File System (hereinafter referred to as IBM Spectrum Scale or GPFS), is a high performance shared-disk file management solution that provides fast, reliable access to data from multiple servers. Applications can readily access files using standard file system interfaces, and the same file can be accessed concurrently from multiple servers and protocols. IBM Spectrum Scale is designed to provide high availability through advanced clustering technologies, dynamic file system management, and data replication. IBM Spectrum Scale can continue to provide data access even when the cluster experiences storage or server malfunctions. IBM Spectrum Scale scalability and performance are designed for data intensive applications such as cloud storage engineering design, digital media, data mining, relational databases, financial analytics, seismic data processing, scientific research and scalable file serving. IBM Spectrum Scale is supported on AIX®, Linux®, and Windows Server operating systems. It is supported on IBM POWER®, Intel or AMD Opteron based servers, and IBM Z®. For more information on the capabilities of IBM Spectrum Scale and its applicability to your environment, see the IBM Spectrum Scale: Concepts, Planning, and Installation Guide. Important References • List of Q&As • IBM Spectrum Scale functional support information • Supported Upgrade Paths on page 11 • Software Version Recommendation Preventive Service Planning IBM Spectrum Scale FAQ These IBM Spectrum Scale Frequently Asked Questions and Answers provides you the most up-to-date information on topics including ordering IBM Spectrum Scale, supported platforms, and supported configuration sizes and capacities.
    [Show full text]