RHEL 8.4 4.18.0-305.19.1.el8_4.x86_64
lspci -nnv |grep -i nvidia
e.g.
#!/usr/bin/python3 | |
# Written May 2019 by Ryan Sawhill Aroha <rsaw@redhat.com> | |
# For dealing with OCPv4's MachineConfigs (which use Ignition) | |
# Ref: https://github.com/openshift/machine-config-operator | |
# Requires python v3.6+ | |
import urllib.parse | |
import os.path | |
from sys import argv, stdin, stderr, exit as sysexit |
[![OpenShift Version][openshift311-redimage]][openshift311-url] [![OpenShift Version][openshift311-heximage1]][openshift311-url] [![OpenShift Version][openshift311-heximage2]][openshift311-url] [![OpenShift Version][openshift311-heximage3]][openshift311-url] [![OpenShift Version][openshift311-heximage4]][openshift311-url]
[![OpenShift Version][openshift39-heximage]][openshift39-url] [![OpenShift Version][openshift310-heximage]][openshift310-url]
[![OpenShift Version][openshift311-logo]][openshift311-url]
Prerequisites: Multus + NetworkAttachmentDefinition CRD installed.
In order to have DHCP working as an IPAM plugin -- you'll need to have the DHCP CNI binary running.
In this example, we'll run this (as a daemonset) from the dougbtv/dhcp
image, which is based on Tomo's dockerfile.
About my setup: In this setup, I use a macvlan plugin as the secondary interface for Multus. In my setup, I used an upstream Kubernetes running on KVM guests. The master device for macvlan is eth0
and that device is connected to a bridge in the 192.168.122.0/24
network space, and has an already running DHCP server available.
The RHPDS catalog item you provisioned is a single-node OpenShift environment that is backed by an Amazon P-type EC2 instance which has 1 NVIDIA GPU. It is a 100% vanilla/standard OpenShift Container Platform 3.10 installation. Post-install, there were a few additional things done consuming Ansible content from the https://github.com/redhat-performance/openshift-psap
Link to these links: https://git.io/vKSVZ
Module 1:
jenkins -jar jenkins.war
docker run -d \
--restart unless-stopped \
--name jenkins \
This is a short guide explaining how to deploy and manage custom SNI or "named" certificates via openshift-ansible. These custom certificates will be served for public facing console and API.
<!DOCTYPE html> | |
<html lang="en"> | |
<head> | |
<title>WebSocket Client</title> | |
<style> | |
#output { | |
border: solid 1px #000; | |
} | |
</style> | |
</head> |