Deploy to Red Hat Product Demo System using the following steps.
SSH into Equinix Metal baremetal
create /tmp/config.yml as lab-user
you can uae ansiblesafe to generate the content of this file
- link
Ansible Vault Secrets Documentation
$ vi /tmp/config.yml
rhsm_username: rheluser
rhsm_password: rhelpassword
rhsm_org: orgid
rhsm_activationkey: activationkey
admin_user_password: password # Change to the lab-user password
offline_token: offlinetoken
openshift_pull_secret: pullsecret
automation_hub_offline_token: automationhubtoken
freeipa_server_admin_password: password # Change to the lab-user password
xrdp_remote_user: remoteuser
xrdp_remote_user_password: password
aws_access_key: accesskey # optional used for aws credentials and route53
aws_secret_key: secretkey # optional used for aws credentials and route53
Add the following to .bashrc as lab-user when using /tmp/config.yml file
$ SSH_PASSWORD=DontForgetToChangeMe # Use the password of the lab-user
$ cat >notouch.env<<EOF
export SSH_USER=lab-user
export CICD_PIPELINE='true'
export ENV_USERNAME=lab-user
export CICD_ENVIORNMENT="gitlab" # or onedev change this vault for default cicd enviornment to deploy VMS
export DOMAIN=qubinodelab.io # Change to your domain if you want to use your own domain
export USE_HASHICORP_CLOUD='false'
export FORWARDER='1.1.1.1'
export ACTIVE_BRIDGE='false'
export INTERFACE=bond0
export USE_ROUTE53=true
export GIT_REPO=https://github.com/tosin2013/qubinode_navigator.git
export INVENTORY=rhel9-equinix
export SSH_PASSWORD=${SSH_PASSWORD}
EOF
$ vi notouch.env
Recommned option: Setting Up Variables in HashiCorp Cloud Platform (HCP) Vault Secrets Setting Up Variables in HashiCorp Cloud Platform (HCP) Vault Secrets
$ SSH_PASSWORD=DontForgetToChangeMe # Use the password of the lab-user
$ DOMAIN=sandbox000.opentlc.com
$ EMAIL=user@example.com # used for letsencrypt
$ GUID=your-guid
$ cat >notouch.env<<EOF
export SSH_USER=lab-user
export CICD_PIPELINE='true'
export ENV_USERNAME=lab-user
export CICD_ENVIORNMENT="gitlab" # or onedev change this vault for default cicd enviornment to deploy VMS
export DOMAIN=${DOMAIN} # Change to your domain if you want to use your own domain
export FORWARDER='$(awk '/^nameserver/ {print $2}' /etc/resolv.conf | head -1)'
export ACTIVE_BRIDGE='false'
export INTERFACE=bond0
export EMAIL=${EMAIL}
export GUID=$GUID
export USE_ROUTE53=true
export ZONE_NAME=${DOMAIN}
export USE_HASHICORP_CLOUD='true'
export GIT_REPO=https://github.com/tosin2013/qubinode_navigator.git
export INVENTORY=rhel9-equinix
export SSH_PASSWORD=${SSH_PASSWORD}
export HCP_CLIENT_ID="your-client-id"
export HCP_CLIENT_SECRET="your-client-secret"
export HCP_ORG_ID="your-org-id"
export HCP_PROJECT_ID="your-project-id"
export APP_NAME="appname"
export OLLAMA_WORKLOAD="false"
EOF
$ vi notouch.env
Run the following commands as lab-user
sudo dnf install -y tmux curl git vim
curl -OL https://raw.githubusercontent.com/tosin2013/qubinode_navigator/main/rhel9-linux-hypervisor.sh
chmod +x rhel9-linux-hypervisor.sh
tmux new-session -s rhel9-linux-hypervisor
source notouch.env && sudo -E ./rhel9-linux-hypervisor.sh
The install will fail on the first time to re-run un the following below
source notouch.env && sudo -E ./rhel9-linux-hypervisor.sh
ssh into vm and run the following
$ sudo kcli download image rhel8
$ sudo kcli download image rhel9
When the prompt below comes up follow the link and look for the corresponding rhel release. right click on the link and copy the link address
Once deployment is complete you can run kcli commands or go to kcli-pipelines repo to run vms.
$ kcli --help
To Access the Baremetal Node
Option 1: Access the VM via the console
Login to the VM using ssh or cockpit console. The endpoint will be https://SERVER_ADDRESS:9090
and the username and password are the same as the lab-user password you set in the config.yml file.
Option 2: RDP into Server on Red Hat Product Demo System
Login via RDP using the remote user and password you set in the config.yml file.
You can also use Remmina to login to the VM
Post Steps
- Configure Onedev for CI/CD - OneDev - Git Server with CI/CD, Kanban, and Packages
OneDev - Deploying Generic VMs
- Deploying Generic VMs: Guide for deploying generic VMs using OneDev.
OneDev - Agent Based Installer Pipelines
- External Deployment: Guide for deploying OpenShift using OneDev’s agent-based installer pipelines for external environments.
- Internal Deployment: Instructions for deploying OpenShift using OneDev’s agent-based installer pipelines for internal environments.
OneDev - kcli-openshift4-baremetal Pipelines
- Externally: Steps to deploy OpenShift 4 on baremetal using kcli pipelines for external environments.
- Internally: Steps to deploy OpenShift 4 on baremetal using kcli pipelines for internal environments.
Deploy Step CA Server using Kcli Pipelines
Detailed guide on deploying a Step CA server using Kcli pipelines.