Skip to content

yeq71/proxmox-training

BranchesTags
 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

60 Commits
.github
.github
 
 
images
images
 
 
prometheus
prometheus
 
 
.editorconfig
.editorconfig
 
 
.gitignore
.gitignore
 
 
README.md
README.md
 
 

Repository files navigation

Ondrej Sika (sika.io) | ondrej@sika.io | go to course ->

Proxmox Training

2019 Ondrej Sika <ondrej@ondrejsika.com>
https://github.com/ondrejsika/proxmox-training

About Me - Ondrej Sika

DevOps Engineer, Consultant & Lecturer

Git, Gitlab, Gitlab CI, Docker, Kubernetes, Terraform, Prometheus, ELK / EFK

Star, Create Issues, Fork, and Contribute

Feel free to star this repository or fork it.

If you find a bug, create an issue or pull request.

Also, feel free to propose improvements by creating issues.

Live Chat

For sharing links & "secrets".

https://tlk.io/sika-proxmox

Course

Agenda

  • Introduction to Virtualization, KVM & Proxmox
  • Proxmox Node Setup
  • Cluster Setup
  • Storage
    • Local
    • NFS
    • ZFS
    • CEPH
  • Virtual Machines
    • Create VM
    • Cloud Init
    • Snapshots
    • Backup / Restore
    • Replication
    • Migrations between Nodes
  • LXC Containers
  • Datacenter
    • Scheduled Backups
    • HA
    • Permissions
  • Prometheus Monitoring
  • Beer!

Proxmox Features

  • KVM & LXC Virtualization
  • Web Interface, API, CLI & Terraform Support
  • HA, Multi-Master
  • Many storage plugins (NFS, CIFS, GlusterFS), built-in CEPH

KVM vs LXC

LXC stands for Linux Containers and KVM is an acronym for Kernel-Based Virtual Machine. The main difference here is that virtual machines require their kernel instance to run while containers share the same kernel. However, each container still acts as its separate environment with their respective file systems.

In other words, containers are virtualization at operating-system-level whereas VMs is virtualization at the hardware level.

source

Proxmox & Terraform

What is Terraform

Terraform is infrastructure as a code provider. You can define your infrastructure in HCL (pseudo JSON) and apply it. Terraform makes your desired state (described in the file) to actual. More about Terraform on my website https://ondrej-sika.cz/terraform (CS only yet).

Proxmox Provider

There is not official provider yet :'(

Demo Proxmox

Terminology

  • PVE - Proxmox Virtual Environment
  • Node - Physical node which runs Proxmox & KVM
  • VM - Virtual Machine
  • CT - LXC Container

Node Setup

  1. SSL
  2. Network
  3. NAT
  4. Port Forwarding

SSL

You have to set up Let's Encrypt certificates on GUI proxy on port 8006

Go to Node (demo) -> System -> Certificates, setup domains & LE account and generate certificates.

Network

You have to create the network for your VMs.

Go to Node (demo) -> System -> Network

Ensure static IP on default bridge (vmbr0) and bridged ports to an active network device (enp1s0).

Help:

# Get IP & Mask
ip a

# Get default route
ip route | grep default

Create a new bridge for VMs network.

Install the `ifup

NAT

If you have only one public IP address you have to set up NAT.

Create IP Tables rule on your node

iptables -t nat -A POSTROUTING -s '192.168.0.0/24' -o vmbr0 -j MASQUERADE
echo 1 > /proc/sys/net/ipv4/ip_forward

Port Forward

You can setup the SSH port forward into VMs

iptables -t nat -A PREROUTING -i vmbr0 -p tcp --dport 9900 -j DNAT --to 192.168.0.100:22
iptables -t nat -A PREROUTING -i vmbr0 -p tcp --dport 9901 -j DNAT --to 192.168.0.101:22
iptables -t nat -A PREROUTING -i vmbr0 -p tcp --dport 9902 -j DNAT --to 192.168.0.102:22
iptables -t nat -A PREROUTING -i vmbr0 -p tcp --dport 9903 -j DNAT --to 192.168.0.103:22
iptables -t nat -A PREROUTING -i vmbr0 -p tcp --dport 9904 -j DNAT --to 192.168.0.104:22
iptables -t nat -A PREROUTING -i vmbr0 -p tcp --dport 9905 -j DNAT --to 192.168.0.105:22
iptables -t nat -A PREROUTING -i vmbr0 -p tcp --dport 9906 -j DNAT --to 192.168.0.106:22
iptables -t nat -A PREROUTING -i vmbr0 -p tcp --dport 9907 -j DNAT --to 192.168.0.107:22
iptables -t nat -A PREROUTING -i vmbr0 -p tcp --dport 9908 -j DNAT --to 192.168.0.108:22
iptables -t nat -A PREROUTING -i vmbr0 -p tcp --dport 9909 -j DNAT --to 192.168.0.109:22

And Other ports, for example:

# HTTP & HTTPS to proxy VM (101)
iptables -t nat -A PREROUTING -i vmbr0 -p tcp --dport 80  -j DNAT --to 192.168.0.101:80
iptables -t nat -A PREROUTING -i vmbr0 -p tcp --dport 443 -j DNAT --to 192.168.0.101:443

# mail ports to mail VM (102)
iptables -t nat -A PREROUTING -i vmbr0 -p tcp --dport 25  -j DNAT --to 192.168.0.102:25
iptables -t nat -A PREROUTING -i vmbr0 -p tcp --dport 110 -j DNAT --to 192.168.0.102:110
iptables -t nat -A PREROUTING -i vmbr0 -p tcp --dport 143 -j DNAT --to 192.168.0.102:143
iptables -t nat -A PREROUTING -i vmbr0 -p tcp --dport 465 -j DNAT --to 192.168.0.102:465
iptables -t nat -A PREROUTING -i vmbr0 -p tcp --dport 587 -j DNAT --to 192.168.0.102:587
iptables -t nat -A PREROUTING -i vmbr0 -p tcp --dport 993 -j DNAT --to 192.168.0.102:993
iptables -t nat -A PREROUTING -i vmbr0 -p tcp --dport 995 -j DNAT --to 192.168.0.102:995

Cluster

You need Proxmox Cluster for:

  • CEPH
  • HA
  • Replication

Create Cluster

Copy Join Info

Join Cluster

Storage

Directory

A path on node's filesystem. You can store anything. You have to use qcow2 images for VM images.

NFS

Run NFS server, for example nfs.sikademo.com (Terraform Manifest)

Add NFS storage to storage configuration

Got to Datacenter -> Storage and add NFS.

Now, you can store CD Images, Disk Images & Backups on NFC.

Copy Local ISO Image to NFS storage

cp /var/lib/vz/template/iso/<iso_image> /mnt/pve/<storage_name>/template/iso/

Example

cp /var/lib/vz/template/iso/debian-10.2.0-amd64-netinst.iso /mnt/pve/nfs/template/iso/

ZFS

Supports only VM & Container images (storage), no ISO and backups. You have to use raw images on ZFS.

Why Proxmox with ZFS:

  • Replication between nodes (partial updates by zfs send)
  • Easy Migration between nodes

ZFS Features:

  • Snapshots
  • ZFS Sync

ZFS Resources:

Ceph

Why Proxmox with Ceph:

  • HA VMs
  • Build-in Ceph Custer (easy setup)

What is Ceph

Ceph is a open-source storage platform, implements object storage on a single distributed computer cluster, and provides interfaces for object-, block- and file-level storage. Ceph aims primarily for completely distributed operation without a single point of failure, and scalable to the exabyte level. -- wikipedia

Resources

Virtual Machines

Create VM

In CLI

qm create <vmid> [ARGS]

Example

qm create 104 --cdrom local:iso/debian-10.2.0-amd64-netinst.iso --name demo --net0 virtio,bridge=vmbr0 --virtio0 local:10,format=qcow2 --bootdisk virtio0 --ostype l26 --memory 1024 --onboot no --sockets 1

more

Install Qemu Agent

apt-get install qemu-guest-agent

Clone

qm clone <sourcevmid> <targetvmid>

Example

qm clone 100 105

Cloud Init

Why Cloud Init?

  • Configure your VM on start
  • Set root password
  • Add SSH key
  • Configure hostname & network

Use Cloud Init

You have to have cloud-init installed in your template

apt-get install cloud-init

If you have cloud init installed, it will automatically run on every VM start.

Snapshots

/usr/sbin/qm snapshot <vmid> <snapshot name>

Example

/usr/sbin/qm snapshot 101 Snapshot_$(date +"%Y_%m_%d_%H_%M_%S")

For automatic (cron) snapshots, you can use https://github.com/kvaps/pve-autosnap

Backup / Restore

Backup

3 levels of consistency

  • stop mode
  • suspend mode
  • snapshot mode
vzdump <vmid> [--mode <mode>] [--storage <storage>]

vzdump --all

Example

vzdump 100 --mode snapshot --storage nfs

Restore

qmrestore <file> <vmid>

Example

qmrestore 100 /mnt/pve/nfs/dump/vzdump-qemu-100-2019_11_29-06_29_48.vma

Migrate VM

Requirements:

  • Distributed (eg.: CEPH) storage or not replicated VM image - migration of replicated VMs is described below

Replication

Requirements:

  • Proxmox Cluster
  • ZFS Storage for VM image

Resources:

Migrate VM Between Replicated Nodes

mv /etc/pve/nodes/<node>/qemu-server/<vm_id>.conf /etc/pve/nodes/<new node>/qemu-server/<vm_id>.conf

Example

mv /etc/pve/nodes/pve0node0/qemu-server/102.conf /etc/pve/nodes/pve0node1/qemu-server/102.conf

Scheduled Backups

Go to Datacenter -> Backups

Create New Schedule Backup

LXC Containers

Download Templates

At first, you have to download the container template.

Go to Storage which supports Container Templates, for the example local or NFS.

Create Container

Go to Create CT

Permissions

Go to Datacenter -> Permissions

You can add permissions to other users, groups on VMs, Containers, Storage.

Resource Pools

You can use resource pools to assign permissions (user, grout) to some resources.

Workflow

  • Create a group
  • Create a pool
  • Configure pool permissions
  • Create users in Proxmox
  • Create users in Linux (adduser)
  • Add users to groups
  • Create a resource in pool / Add resource to pool

Prometheus Monitoring

Wakeful PVE Exporter

Install

wget -O /usr/local/bin/pve_exporter https://github.com/wakeful/pve_exporter/releases/download/0.1.6/pve_exporter-linux-amd64 && chmod +x /usr/local/bin/pve_exporter

Run on the node

pve_exporter -password <password>

Run on the other machine

pve_exporter -pve-url <pve_url> -password <password>

Listen on port 9090

Run Demo Prometheus

You need to have Prometheus installed

git clone https://github.com/ondrejsika/proxmox-training
cd proxmox-training

cd prometheus
# run Prometheus
prometheus

Go to http://127.0.0.1:9090/graph

Thank you! & Questions?

That's it. Do you have any questions? Let's go for a beer!

Ondrej Sika

Do you like the course? Write me a recommendation on Twitter (with handle @ondrejsika) and LinkedIn (add me /in/ondrejsika and I'll send you Request for the recommendation). Thanks.

Wanna go for a beer or do some work together? Just book me :)

Resources

About

Proxmox Training

Resources

Readme
Activity

Stars

1 star

Watchers

0 watching

Forks

0 forks
Report repository

Releases

No releases published

Packages

No packages published