Installing VM
AHD VM is the deployment solution for on-premises environments or single node cloud deployments.
To install VM follow these steps:
- Download Live DVD ISO from the official Fedora CoreOS website (
stable
stream)⚠️ Use only the ISO file (and not OVA, vhdx, etc.)
- Import the ISO file in your Hypervisor of choice
- Create a new virtual machine in your Hypervisor, starting from the ISO file
- Boot up the VM and connect to its terminal
- Take note of the name of the main storage device. Based on the underlying hardware, it can be
/dev/sd*
,/dev/nvme*
,...To find out the name, run the
lsblk
command - Run the following command in the terminal, replacing
/dev/sda
with the device name you saved in the previous step.
warning
The keyboard layout will be en-US
for this command only. Once the setup is completed, it will be it-IT
If you're using an it-IT
layout for your keyboard, follow these tips to properly type the special characters you'll find in the following command:
- Slash ( / ) is
-
- Dash ( - ) is
'
- Colon ( : ) is
ç
(shift + ò) - Dot ( . ) is unchanged
sudo coreos-installer install /dev/sda -n --ignition-url https://smartkit-vm.smeup.cloud
-
Wait for the end of the installation process.
-
Once the installation process is over, shutdown the VM with the following command:
sudo shutdown now
- In the Hypervisor console, unmount the CD/DVD device containing the ISO file
- Boot up the VM
- Through the Hypervisor terminal, login into the VM with the username
smeup
and passwordsmeup
- To proceed, you will be prompted to setup a new password
- Run the script
initial-setup.sh
from the home directory of the smeup user with the following command
bash initial-setup.sh
- Reload the shell variables by either logging out and logging in or by running the following command:
source /home/smeup/.bashrc
- Validate the installation by running preflight checks through the following command:
kubectl preflight https://smartkit-vm.smeup.cloud/preflight.yaml
Verify that the preflight checks output is positive. If there are warnings or errors, fix them before running the preflight check again.