mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 15. Managing project quotas 15.1. Configuring project quotas OpenStack Networking (neutron) supports the use of quotas to constrain the number of resources created by tenants/projects. Procedure You can set project quotas for various network components in the /var/lib/config-data/puppet-generated/neutron/etc/neutron/neutron.conf file. For example, to limit the number of routers that a project can create, change the quota_router value: In this example, each project is limited to a maximum of 10 routers. For a listing of the quota settings, see sections that immediately follow. 15.2. L3 quota options Here are quota options available for layer 3 (L3) networking: quota_floatingip - The number of floating IPs available to a project. quota_network - The number of networks available to a project. quota_port - The number of ports available to a project. quota_router - The number of routers available to a project. quota_subnet - The number of subnets available to a project. quota_vip - The number of virtual IP addresses available to a project. 15.3. Firewall quota options Here are quota options available for managing firewalls for projects: quota_firewall - The number of firewalls available to a project. quota_firewall_policy - The number of firewall policies available to a project. quota_firewall_rule - The number of firewall rules available to a project. 15.4. Security group quota options The Networking service quota engine manages security groups and security group rules, and it is not possible to set all quotas to zero before creating the default security group (and the two default security group rules that accepts all egress traffic for IPv4 and IPv6). When you create a new project, the Networking service does not create the default security group until a network or a port is created, or until you list the security group or the security group rules. Here are quota options available for managing the number of security groups that projects can create: quota_security_group - The number of security groups available to a project. quota_security_group_rule - The number of security group rules available to a project. 15.5. Management quota options Here are additional options available to administrators for managing quotas for projects: default_quota * - The default number of resources available to a project. quota_health_monitor * - The number of health monitors available to a project. Health monitors do not consume resources, however the quota option is available because OpenStack Networking considers health monitors as resource consumers. quota_member - The number of pool members available to a project. Pool members do not consume resources, however the quota option is available because OpenStack Networking considers pool members as resource consumers. quota_pool - The number of pools available to a project.

Commands:
quota_router = 10
21.4. Enable JMX for Cache Instances At the Cache level, JMX statistics can be enabled either declaratively or programmatically, as follows. Enable JMX Declaratively at the Cache Level Add the following snippet within either the <default> element for the default cache instance, or under the target <namedCache> element for a specific named cache: Enable JMX Programmatically at the Cache Level Add the following code to programmatically enable JMX at the cache level: Report a bug

Commands:
<jmxStatistics enabled="true"/>
Configuration configuration = new ConfigurationBuilder().jmxStatistics().enable().build();
Chapter 1. Management CLI Overview The management command-line interface (CLI) is a command-line administration tool for JBoss EAP. Use the management CLI to start and stop servers, deploy and undeploy applications, configure system settings, and perform other administrative tasks. Operations can be performed in batch mode, allowing multiple tasks to be run as a group. Many common terminal commands are available, such as ls , cd , and pwd . The management CLI also supports tab completion.

Commands:
8.245. trousers 8.245.1. RHSA-2014:1507 - Low: trousers security, bug fix, and enhancement update Updated trousers packages that fix one security issue, several bugs, and add various enhancements are now available for Red Hat Enterprise Linux 6. Red Hat Product Security has rated this update as having Low security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section. TrouSerS is an implementation of the Trusted Computing Group's Software Stack (TSS) specification. You can use TrouSerS to write applications that make use of your TPM hardware. TPM hardware can create, store and use RSA keys securely (without ever being exposed in memory), verify a platform's software state using cryptographic hashes and more. Security Fix CVE-2012-0698 A flaw was found in the way tcsd, the daemon that manages Trusted Computing resources, processed incoming TCP packets. A remote attacker could send a specially crafted TCP packet that, when processed by tcsd, could cause the daemon to crash. Note that by default tcsd accepts requests on localhost only. Red Hat would like to thank Andrew Lutomirski for reporting this issue. The trousers package has been upgraded to upstream version 0.3.13, which provides a number of bug fixes and enhancements over the version, including corrected internal symbol names to avoid collisions with other applications, fixed memory leaks, added IPv6 support, fixed buffer handling in tcsd, as well as changed the license to BSD. (BZ#633584, BZ#1074634) All trousers users are advised to upgrade to these updated packages, which correct these issues and add these enhancements.

Commands:
Chapter 10. Setting up to Develop Web Applications Red Hat Enterprise Linux supports development of web applications by being the platform for their deployment. The topic of web development is too broad to be captured with a few simple instructions. This section offers only the best supported paths for the development of web applications on Red Hat Enterprise Linux. To set up your environment for developing traditional web applications, install the Apache web server, PHP runtime, and MariaDB database server and tools. Alternatively, more recent versions of these applications are available as components of Red Hat Software Collections. Additional Resources Red Hat Software Collections Red Hat Developer portal Cheat Sheet - Advanced Linux Commands Cheat Sheet (setting up a LAMP stack)

Commands:
yum install httpd mariadb-server php-mysql php
yum install httpd24 rh-mariadb102 rh-php73
Chapter 67. Defining a test scenario After creating a test scenario template you have to define the test scenario . The rows of the test scenario table define the individual test scenarios. A test scenario has a unique index number, description, set of input values (the Given values), and a set of output values (the Expect values). Prerequisites The test scenario template has been created for the selected test scenario. Procedure Open the test scenario in the test scenarios designer. Enter a description of the test scenario and fill in required values in each cell of the row. Use the contextual menu to add or remove rows as required. Double click a cell to start inline editing. To skip a particular cell from test evaluation, leave it empty. After defining the test scenario, you can run the test .

Commands:
7.3.2. The XFS File System XFS is a robust and highly-scalable single host 64-bit journaling file system. It is entirely extent-based, so it supports very large file and file system sizes. The maximum supported file system size in Red Hat Enterprise Linux 6.8 and later is 300 TB. The maximum supported XFS file system size in Red Hat Enterprise Linux 6.7 and earlier is 100 TB. The number of files an XFS system can hold is limited only by the space available in the file system. XFS supports metadata journaling, which facilitates quicker crash recovery. The XFS file system can also be defragmented and enlarged while mounted and active. In addition, Red Hat Enterprise Linux 6 supports backup and restore utilities specific to XFS. XFS uses extent-based allocation, and features a number of allocation schemes such as delayed allocation and explicit pre-allocation. Extent-based allocation provides a more compact and efficient method of tracking used space in a file system, and improves large file performance by reducing fragmentation and the space consumed by metadata. Delayed allocation improves the chance that a file will be written in a contiguous group of blocks, reducing fragmentation and improving performance. Pre-allocation can be used to prevent fragmentation entirely in cases where the application knows the amount of data it needs to write ahead of time. XFS provides excellent I/O scalability by using b-trees to index all user data and metadata. Object counts grow as all operations on indexes inherit the logarithmic scalability characteristics of the underlying b-trees. Some of the tuning options XFS provides at mkfs time vary the width of the b-trees, which changes the scalability characteristics of different subsystems. 7.3.2.1. Basic tuning for XFS In general, the default XFS format and mount options are optimal for most workloads; Red Hat recommends that the default values are used unless specific configuration changes are expected to benefit the workload of the file system. If software RAID is in use, the mkfs.xfs command automatically configures itself with the correct stripe unit and width to align with the hardware. This may need to be manually configured if hardware RAID is in use. The inode64 mount option is highly recommended for multi-terabyte file systems, except where the file system is exported via NFS and legacy 32-bit NFS clients require access to the file system. The logbsize mount option is recommended for file systems that are modified frequently, or in bursts. The default value is MAX (32 KB, log stripe unit), and the maximum size is 256 KB. A value of 256 KB is recommended for file systems that undergo heavy modifications.

Commands:
Chapter 7. Overcommitting with KVM 7.1. Introduction The KVM hypervisor automatically overcommits CPUs and memory. This means that more virtualized CPUs and memory can be allocated to virtual machines than there are physical resources on the system. This is possible because most processes do not access 100% of their allocated resources all the time. As a result, under-utilized virtualized servers or desktops can run on fewer hosts, which saves a number of system resources, with the net effect of less power, cooling, and investment in server hardware.

Commands:
Chapter 2. Compatibility matrix for Red Hat Ceph Storage 4.1 The following tables list products and their versions compatible with Red Hat Ceph Storage (RHCS) 4.1. Host Operating System Version Notes Red Hat Enterprise Linux 7.8, 7.9, 8.2, and 8.3 Included in the product Important All nodes in the cluster and their clients must use the supported OS version(s) to ensure that the version of the ceph package is the same on all nodes. Using different versions of the ceph package is not supported. Important Red Hat no longer supports using Ubuntu as a host operating system to deploy Red Hat Ceph Storage. Product Version Notes Ansible 2.9 Included in the product Red Hat OpenShift 3.0 and later 3.x versions The RBD driver is supported starting with version 3.0 and Cinder driver is supported starting with version 3.1. Red Hat OpenShift 4 is not supported. Red Hat OpenStack Platform 13, 15 and 16 Red Hat OpenStack Platform 11, 12 and 14 is not supported. Red Hat OpenStack Platform 10 and Red Hat Ceph Storage 4 are not a tested combination.Director 13 deployed Red Hat Ceph Storage 3.1+ also supports external Red Hat Ceph Storage 4. Director 16 deployed Red Hat Ceph Storage 4.1 also supports external Red Hat Ceph Storage 5. Red Hat Satellite 6.x Only registering with the Content Delivery Network (CDN) is supported. Registering with Red Hat Network (RHN) is deprecated and not supported. Red Hat OpenShift Container Storage 4.5 Red Hat Ceph Storage 4.1.1 and later versions are supported for Red Hat OpenShift Storage 4.5 external mode. Client Connector Version Notes S3A 2.8.x, 3.2.x, and trunk Red Hat Enterprise Linux iSCSI Initiator The latest versions of the iscsi-initiator-utils and device-mapper-multipath packages RHCS as a backup target Version Notes CommVault Cloud Data Management v11 IBM Spectrum Protect Plus 10.1.5 IBM Spectrum Protect server 8.1.8 NetApp AltaVault 4.3.2 and 4.4 Rubrik Cloud Data Management (CDM) 3.2 and later Trilio, TrilioVault 3.0 S3 target Veeam (object storage) Veeam Availability Suite 9.5 Update 4 Supported on Red Hat Ceph Storage object storage with the S3 protocol Veritas NetBackup for Symantec OpenStorage (OST) cloud backup 7.7 and 8.0 Independent Software vendors Version Notes IBM Spectrum Discover 2.0.3

Commands:
20.4. CPU Allocation <domain> ... <vcpu placement='static' cpuset="1-4,^3,6" current="1">2</vcpu> ... </domain> Figure 20.6. CPU allocation The <cpu> element defines the maximum number of virtual CPUs (vCPUs) allocated for the guest virtual machine operating system, which must be between 1 and the maximum supported by the hypervisor. This element can contain an optional cpuset attribute, which is a comma-separated list of physical CPU numbers that domain processes and virtual CPUs can be pinned to by default. Note that the pinning policy of domain processes and virtual CPUs can be specified separately by using the cputune attribute. If the emulatorpin attribute is specified in <cputune> , the cpuset value specified by <vcpu> will be ignored. Similarly, virtual CPUs that have set a value for vcpupin cause cpuset settings to be ignored. Virtual CPUs where vcpupin is not specified will be pinned to the physical CPUs specified by cpuset . Each element in the cpuset list is either a single CPU number, a range of CPU numbers, or a caret (^) followed by a CPU number to be excluded from a range. The attribute current can be used to specify whether fewer than the maximum number of virtual CPUs should be enabled. The optional attribute placement can be used to specify the CPU placement mode for the domain process. placement can be set as either static or auto . If you set <vcpu placement='auto'> , the system will query numad and use the settings specified in the <numatune> tag, and ignore any other settings in <vcpu> . If you set <vcpu placement='static'> , the system will use the settings specified in the <vcpu placement> tag instead of the settings in <numatune> .

Commands:
<domain> <vcpu placement='static' cpuset="1-4,^3,6" current="1">2</vcpu> </domain>
5.6.2. Anonymous Access The presence of the /var/ftp/ directory activates the anonymous account. The easiest way to create this directory is to install the vsftpd package. This package sets a directory tree up for anonymous users and configures the permissions on directories to read-only for anonymous users. By default the anonymous user cannot write to any directories. Warning If enabling anonymous access to an FTP server, be aware of where sensitive data is stored. 5.6.2.1. Anonymous Upload To allow anonymous users to upload, it is recommended that a write-only directory be created within /var/ftp/pub/ . To do this, type: change the permissions so that anonymous users cannot see what is within the directory by typing: A long format listing of the directory should look like this: Warning Administrators who allow anonymous users to read and write in directories often find that their servers become a repository of stolen software. Additionally, under vsftpd , add the following line to the /etc/vsftpd/vsftpd.conf file:

Commands:
mkdir /var/ftp/pub/upload
chmod 730 /var/ftp/pub/upload
drwx-wx--- 2 root ftp 4096 Feb 13 20:05 upload
anon_upload_enable=YES
8.2.4. Alias and Clone Files Two lesser-used types of interface configuration files are alias and clone files. Alias interface configuration files, which are used to bind multiple addresses to a single interface, use the ifcfg- <if-name> : <alias-value> naming scheme. For example, an ifcfg-eth0:0 file could be configured to specify DEVICE=eth0:0 and a static IP address of 10.0.0.2, serving as an alias of an Ethernet interface already configured to receive its IP information via DHCP in ifcfg-eth0 . Under this configuration, eth0 is bound to a dynamic IP address, but the same physical network card can receive request via the fixed, 10.0.0.2 IP address. Warning Alias interfaces do not support DHCP. A clone interface configuration file should use the following naming convention: ifcfg- <if-name> - <clone-name> . While an alias file allows multiple addresses for an existing interface, a clone file is used to specify additional options for an interface. For example, a standard DHCP Ethernet interface called eth0 , may look similar to this: Since the default value for the USERCTL directive is no if it is not specified, users cannot bring this interface up and down. To give users the ability to control the interface, create a clone by copying ifcfg-eth0 to ifcfg-eth0-user and add the following line to ifcfg-eth0-user : This way a user can bring up the eth0 interface using the /sbin/ifup eth0-user command because the configuration options from ifcfg-eth0 and ifcfg-eth0-user are combined. While this is a very basic example, this method can be used with a variety of options and interfaces. The easiest way to create alias and clone interface configuration files is to use the graphical Network Administration Tool . For more on using this tool, refer to the chapter called Network Configuration in the System Administrators Guide .

Commands:
DEVICE=eth0 ONBOOT=yes BOOTPROTO=dhcp
USERCTL=yes
4.227. php-pear 4.227.1. RHSA-2011:1741 - Low: php-pear security and bug fix update An updated php-pear package that fixes one security issue and multiple bugs is now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having low security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) associated with each description below. The php-pear package contains the PHP Extension and Application Repository (PEAR), a framework and distribution system for reusable PHP components. Security Fix CVE-2011-1072 It was found that the "pear" command created temporary files in an insecure way when installing packages. A malicious, local user could use this flaw to conduct a symbolic link attack, allowing them to overwrite the contents of arbitrary files accessible to the victim running the "pear install" command. Bug Fixes BZ# 651897 The php-pear package has been upgraded to version 1.9.4, which provides a number of bug fixes over the version. BZ# 747361 Prior to this update, php-pear created a cache in the "/var/cache/php-pear/" directory when attempting to list all packages. As a consequence, php-pear failed to create or update the cache file as a regular user without sufficient file permissions and could not list all packages. With this update, php-pear no longer fails if writing to the cache directory is not permitted. Now, all packages are listed as expected. All users of php-pear are advised to upgrade to this updated package, which corrects these issues.

Commands:
Chapter 12. Locating the images you created by using Insights image builder By accessing the Insights image builder dashboard, you are able to locate the images built for you. 12.1. Locating your customized images in the Insights image builder dashboard After your customized images are uploaded to the cloud or clouds, you can still locate these images and, if they are still valid, you have the option to copy them and also launch them directly from the dashboard. To locate your images in the image builder dashboard, complete the following steps: Prerequisites You have an account on Red Hat Customer Portal with an Insights subscription. You have access to the Insights image builder dashboard . You created images by using Insights image builder. Procedure Access the Insights image builder dashboard. You are redirected to the Insights image builder dashboard and can see all the images that were built for you. Locate your image by name. Type your image name in the search bar on the top left menu. If your image exists, image details appear, showing: the Image name, Creation date, Release version, cloud Target , and image Status . You can also see information about any customizations applied to the image, such as packages and file system configuration. Under Uploads , you can find the uploaded images. For Amazon Web Services images: After the image status is marked as Ready , click the Launch instance link. You are redirected to the image on AWS from where you can launch the instance. See Launching your customized RHEL system image for AWS from your AWS EC2 . For Google Cloud Platform images: After the image status is marked as Ready , click the copy symbol. You can create a Virtual Machine (VM) instance using the GCE image. See Creating a VM instance using your GCE image . For Microsoft Azure images: After the image status is marked as Ready , click the View uploaded image link. You are redirected to the image on Microsoft Azure from where you can view the uploaded image from your Microsoft Azure account. See Creating a VM from the customized RHEL system image you shared with the Microsoft Azure account . For VMware images: After the image status is marked as Ready , click the Download .vmdk link. The image is saved to your system and is ready for deployment. See Deploying VMDK images to vSphere by using the GUI . For Guest images images: After the image status is marked as Ready , click the Download .qcow2 image. The image is saved to your system and is ready for deployment. See Creating a Virtual Machine from the customized RHEL Guest system image . For Bare metal images images: After the image status is marked as Ready , click the Download .iso image. The image is saved to your system and is ready for deployment. See Installing the customized RHEL ISO system image to a bare metal system . Note The image artifacts for public clouds, such as GCP, and AWS are saved for 14 days and expire after that. Ensure to transfer the image to your account to avoid losing it. The private clouds images, such as VMware, Guest-image, and Installer images are available for 6 hours and expire after that. Ensure to download the image to avoid losing it.

Commands:
5.2.18. /proc/mdstat This file contains the current information for multiple-disk, RAID configurations. If the system does not contain such a configuration, then /proc/mdstat looks similar to the following: This file remains in the same state as seen above unless a software RAID or md device is present. In that case, view /proc/mdstat to find the current status of md X RAID devices. The /proc/mdstat file below shows a system with its md0 configured as a RAID 1 device, while it is currently re-syncing the disks:

Commands:
Personalities : read_ahead not set unused devices: <none>
Personalities : [linear] [raid1] read_ahead 1024 sectors md0: active raid1 sda2[1] sdb2[0] 9940 blocks [2/2] [UU] resync=1% finish=12.3min algorithm 2 [3/3] [UUU] unused devices: <none>