mndambuki

Requirements

There are 18 questions in total. You will need five RHEL 8 (or CentOS 😎 virtual machines to be able to successfully complete all questions.

Optional Automatic Exam Setup Available

Here is an automated exam environment deployment for Mac/Linux/Windows that deploys the practice exam environment for you, including IPA server/client installation and configuration. You can also use your own lab environment. Navigate to the respective repo you wish to use for this practice exam and follow the README instructions:

https://github.com/rdbreak/rhce8env, https://github.com/rdbreak/ansible27env, https://github.com/rdbreak/ansible8env.

to inform a different ssh key; limit hosts; etc

ansible -b -i ec2.py all \
 --limit '!x.y.z.w' \
 --key-file '~/.ssh/aws_ec2' \
 -m shell -a 'subscription-manager list --pool-only --consumed'

more tips&tricks here: https://ansible-tips-and-tricks.readthedocs.io/en/latest/ansible/commands/

My Openshift Cheatsheet

Openshift build secrets for cloning git repos using SSH Keys

To create ssh secret:

oc create secret generic sshsecret \
    --from-file=ssh-privatekey=$HOME/.ssh/id_rsa

Overview: running crc on a remote server

This document shows how to deploy an OpenShift instance on a server using CodeReady Containers (crc) that can be accessed remotely from one or more client machines (sometimes called a "headless" instance). This provides a low-cost test and development platform that can be shared by developers. Deploying this way also allows a user to create an instance that uses more cpu and memory resources than may be available on his or her laptop.

While there are benefits to this type of deployment, please note that the primary use case for crc is to deploy a local OpenShift instance on a workstation or laptop and access it directly from the same machine. The headless setup is configured completely outside of crc itself, and supporting a headless setup is beyond the mission of the crc development team. Please do not ask for changes to crc to support this type of deployment, it will only cost the team time as they politely decline :)

The instructions here were tested with F

	version: 2
	services:
	wallabag:
	image: wallabag/wallabag
	environment:
	- MYSQL_ROOT_PASSWORD=wallaroot
	- SYMFONY__ENV__DATABASE_DRIVER=pdo_mysql
	- SYMFONY__ENV__DATABASE_HOST=db
	- SYMFONY__ENV__DATABASE_PORT=3306
	- SYMFONY__ENV__DATABASE_NAME=wallabag

	kind: Pod
	apiVersion: v1
	metadata:
	name: pod-debug
	labels:
	app: debug
	deploymentconfig: debug
	spec:
	restartPolicy: Always
	serviceAccountName: default

	Put this in your `local-configure.yml` file, add as many users as you need:

	users:
	- name: fulvio
	sudoer: yes
	auth_key: ssh-rsa blahblahblahsomekey this is actually the public key in cleartext
	- name: plone_buildout
	group: plone_group
	sudoer: no
	auth_key: ssh-rsa blahblahblah ansible-generated on default

	1) Download cntlm rpm package from http://sourceforge.net/projects/cntlm/files/cntlm/

	2) Login as root

	3) Run command:
	$ rpm -ivh cntlm-*.rpm

	4a) Obtain password hash for the configuration file in step 4b (do not put plaintext password in configuration)
	$ cntlm -H -d <domain> -u <username>

	# ============================================================================== START HTACCESS VARIATIONS

	#Options +FollowSymLinks
	#Options -Indexes
	#DirectoryIndex index.php
	#RewriteEngine on
	#RewriteCond $1 !^(index.php\|robots.txt\|file\|favicon.ico)
	#RewriteCond %{REQUEST_FILENAME} !-d
	#RewriteCond %{REQUEST_FILENAME} !-f
	#RewriteRule ^(.*)$ index.php/$1 [L,QSA]

	@echo off
	title Activate Microsoft Office 2019 !
	cls
	echo ============================================================================
	echo #Project: Activating Microsoft software products
	echo ============================================================================
	echo.
	echo #Supported products:
	echo - Microsoft Office Standard 2019
	echo - Microsoft Office Professional Plus 2019