I added an index and reorganized the readme to be more streamlined. Im not sure how to contribute via a pull request so heres the markdown, hope this helps (Keep up the great work here):
Click "Clone a repository from the Internet" and enter "rdbreak/rhce8env" and choose a location then "Clone".
You are also able to easily pull changes when they're made available.
Downloading the Environment Prep
git clone https://github.com/rdbreak/rhce8env.git && cd rhcsa8env
CentOS/RHEL7/Manjaro/Arch (Continue below for RHEL 8 specific script and Virtualbox Extension Pack)
systemctl stop packagekit; yum install -y epel-release && yum install -y git binutils gcc make patch libgomp glibc-headers glibc-devel kernel-headers kernel-devel dkms libvirt libvirt-devel ruby-devel libxslt-devel libxml2-devel libguestfs-tools-c ; mkdir ~/Vagrant ; cd ~/Vagrant ; curl -o vagrant_2.2.6_x86_64.rpm https://releases.hashicorp.com/vagrant/2.2.6/vagrant_2.2.6_x86_64.rpm && yum install -y vagrant_2.2.6_x86_64.rpm && vagrant plugin install vagrant-guest_ansible ; vagrant plugin install vagrant-guest-ansible ; wget -O /etc/yum.repos.d/virtualbox.repo wget http://download.virtualbox.org/virtualbox/rpm/rhel/virtualbox.repo ; yum install -y VirtualBox-6.0 && systemctl start packagekit
*_NOTE* - If it's been awhile since you've run yum update, do that first. Reboot if the kernel was updated. There may be some dependencies errors but don't be alarmed as this won't stop the environment from working._
*_NOTE2* - If you receive an error for an ansible guest vagrant plugin, DO NOT worry, as there are two different plugins related to Ansible and only one needs to be installed._
Then install the following vagrant plugin via PowerShell as Administrator vagrant plugin install vagrant-guest_ansible
vagrant up
macOS
Gatekeeper will block virtualbox from installing. All you have to do is go into Security & Privacy of System Preferences and click Allow under the General tab and rerun installation.
Virtual Box Extension PackAlso, don't be spooked by any scary red font during the setup process. There are known issues that won't have a negative affect on the environment.
Now the deployment should be up and running!
Starting-Accessing the Environment
Access example (Needs sudo) - vagrant ssh control or ssh user@192.168.55.201
Notable Vagrant Commands to control the environment:
ansible-playbook playbooks/reset.yml - Used for resetting the environment after attempting the practice exam in the Red Hat Certs Slack workspace practice exam channel.
vagrant up - Boots and provisions the environment
vagrant destroy -f - Shuts down and destroys the environment
vagrant halt - Only shuts down the environment VMs (can be booted up with vagrant up)
vagrant suspend - Puts the VMs in a suspended state
vagrant resume - Takes VMs out of a suspended state
Included systems hosts:
repo.ansi.example.com
control.ansi.example.com
node1.ansi.example.com
node2.ansi.example.com
node3.ansi.example.com
node4.ansi.example.com
System Details:
control
192.168.55.200
Gateway - 192.168.55.1
DNS - 8.8.8.8
node1
192.168.55.201
Gateway - 192.168.55.1
DNS - 8.8.8.8
node2
192.168.55.202
Gateway - 192.168.55.1
DNS - 8.8.8.8
node3
192.168.55.203
Gateway - 192.168.55.1
DNS - 8.8.8.8
node4
192.168.55.204
Gateway - 192.168.55.1
DNS - 8.8.8.8
There is a Repo/AppStream available to use from http://repo.ansi.example.com/BaseOS and http://repo.ansi.example.com/AppStream
Remember to add the IP addresses to your local host file if you want to connect to the guest systems with the hostname.
Username - user or root
Password - password
Other Useful Information
You can also use the VirtualBox console to interact with the VMs or through a terminal. If you need to reset the root password, you would need to use the console. I'm constantly making upgrades to the environments, so every once and awhile run git pull in the repo directory to pull down changes. If you're using Windows, it's recommended to use Github Desktop so you can easily pull changes that are made to the environment. The first time you run the vagrant up command, it will download the OS images for later use. In other words, it will take longest the first time around but will be faster when it is deployed again. You can run vagrant destroy -f to destroy your environment at anytime. This will erase everything. This environment is meant to be reuseable, If you run the vagrant up command after destroying the environment, the OS image will already be downloaded and environment will deploy faster. Deployment should take around 15 minutes depending on your computer. You shouldn't need to access the IPA server during your practice exams. Everything should be provided that you would normally need during an actual exam. Hope this helps in your studies!
Known Issues
Running the 'vagrant up' environment build will fail If HyperV is installed on the Windows VirtualBox host.
Error is usually "VT-x is not available. (VERR_VMX_NO_VMX)" or similar, when the script attempts to boot the first VM.
Resolution seems to be either remove HyperV, or preventing its hypervisor from starting with the command:
bcdedit /set hypervisorlaunchtype off, followed by a reboot.
Submitting a Bug Report
If you're having problems with the environment, please submit an issue by going to the ISSUES tab at the top. If you have more questions, looking for practice exams to use against this environment, or just looking for a fantastic Red Hat community to join to get your questions answered, check out the Red Hat Certs Slack Workspace. You can find the invite link at the top of this page next to the description.
Hello,
I added an index and reorganized the readme to be more streamlined. Im not sure how to contribute via a pull request so heres the markdown, hope this helps (Keep up the great work here):
RHCE 8 Automated Practice Deployment
Powered by Ansible and Vagrant
Getting Started
Setting up the Environment
(Recommended) Install Github Desktop to make pulling down changes easier
NOTE this requires a free Github account
Downloading the Environment Prep
git clone https://github.com/rdbreak/rhce8env.git && cd rhcsa8envCentOS/RHEL7/Manjaro/Arch (Continue below for RHEL 8 specific script and Virtualbox Extension Pack)
If you're using RHEL 8, use the script below:
Fedora
dnf update -yto update your system, then run the script below as root to install everything at once:Windows
vagrant plugin install vagrant-guest_ansiblevagrant upmacOS
Gatekeeper will block virtualbox from installing. All you have to do is go into Security & Privacy of System Preferences and click Allow under the General tab and rerun installation.
Install all at once with the command below:
Alternatively, you can install everything individually below.
brew cask install vagrant)vagrant plugin install vagrant-guest_ansiblebrew cask install VirtualBox)brew cask install virtualbox-extension-pack)Debian
Also, install the Virtualbox extension pack below
Now the deployment should be up and running!
Starting-Accessing the Environment
Access example (Needs sudo) -
vagrant ssh controlorssh user@192.168.55.201Notable Vagrant Commands to control the environment:
ansible-playbook playbooks/reset.yml- Used for resetting the environment after attempting the practice exam in the Red Hat Certs Slack workspace practice exam channel.vagrant up- Boots and provisions the environmentvagrant destroy -f- Shuts down and destroys the environmentvagrant halt- Only shuts down the environment VMs (can be booted up withvagrant up)vagrant suspend- Puts the VMs in a suspended statevagrant resume- Takes VMs out of a suspended stateIncluded systems hosts:
System Details:
There is a Repo/AppStream available to use from
http://repo.ansi.example.com/BaseOSandhttp://repo.ansi.example.com/AppStreamRemember to add the IP addresses to your local host file if you want to connect to the guest systems with the hostname. Username - user or root Password - password
Other Useful Information
You can also use the VirtualBox console to interact with the VMs or through a terminal. If you need to reset the root password, you would need to use the console. I'm constantly making upgrades to the environments, so every once and awhile run
git pullin the repo directory to pull down changes. If you're using Windows, it's recommended to use Github Desktop so you can easily pull changes that are made to the environment. The first time you run the vagrant up command, it will download the OS images for later use. In other words, it will take longest the first time around but will be faster when it is deployed again. You can runvagrant destroy -fto destroy your environment at anytime. This will erase everything. This environment is meant to be reuseable, If you run thevagrant upcommand after destroying the environment, the OS image will already be downloaded and environment will deploy faster. Deployment should take around 15 minutes depending on your computer. You shouldn't need to access the IPA server during your practice exams. Everything should be provided that you would normally need during an actual exam. Hope this helps in your studies!Known Issues
Running the 'vagrant up' environment build will fail If HyperV is installed on the Windows VirtualBox host. Error is usually "VT-x is not available. (VERR_VMX_NO_VMX)" or similar, when the script attempts to boot the first VM.
Resolution seems to be either remove HyperV, or preventing its hypervisor from starting with the command: bcdedit /set hypervisorlaunchtype off, followed by a reboot.
Submitting a Bug Report
If you're having problems with the environment, please submit an issue by going to the
ISSUEStab at the top. If you have more questions, looking for practice exams to use against this environment, or just looking for a fantastic Red Hat community to join to get your questions answered, check out the Red Hat Certs Slack Workspace. You can find the invite link at the top of this page next to the description.