Tạo, Join cluster và quy trình Automation với Proxmox CLI

shell> pvecm create mycluster
Corosync Cluster Engine Authentication key generator.
Gathering 2048 bits for key from /dev/urandom.
Writing corosync key to /etc/corosync/authkey.
Writing corosync config to /etc/pve/corosync.conf
Restart corosync and cluster filesystem

shell> pvecm add 192.168.100.131
Please enter superuser (root) password for '192.168.100.131': *********
Establishing API connection with host '192.168.100.131'
The authenticity of host '192.168.100.131' can't be established.
X509 SHA256 key fingerprint is 51:34:EE:CE:7C:8B:37:4B:31:A6:8D:E0:B8:7E:04:B8:D2:19:C9:2B:8A:D8:50:8F:13:AD:E0:1C:07:F9:25:96.
Are you sure you want to continue connecting (yes/no)? yes
Login succeeded.
check cluster join API version
No cluster network links passed explicitly, fallback to local node IP '192.168.100.132'
Request addition of this node
Join request OK, finishing setup locally
stopping pve-cluster service
backup old database to '/var/lib/pve-cluster/backup/config-1727716517.sql.gz'
waiting for quorum...OK
(re)generate node files
generate new node certificate
merge authorized SSH keys and known hosts
generated new node certificate, restart pveproxy and pvedaemon services
successfully added node 'node2' to cluster.

shell> cat ~/.ssh/id_rsa.pub
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCuKm4/DV40iv8EzNMHNMRasHHc95JWwEAGB+PXkM1BhZIt07kQ21UlS7tsCUnWVicxpfbabkTsSRCIKUd84dC+gmXiW7axo6AH1NykXr1bxzBAHGX4CbCgiIrnLhmKIhu72605O+L4rMxHf2DwRrT9g7i1o9ONyZym3dPDqZmQD9vwRhmMBlAV/d4sRvRVSGc8m6XlGb58osguQglwvIM9VlM5Faj4KtMShl0RdtrwmFebj45XhVlVtEYDYcrrd1jASuEQXPuhcEXyN/3a5WZ9lpYq8MqxcsuVGEfWabxuRbdmGq7KBgSpjZ9owKao5I8nmxKUJizbyxf4zlf30e6L root@node3

shell> ssh-copy-id root@192.168.100.131
/usr/bin/ssh-copy-id: INFO: Source of key(s) to be installed: "/root/.ssh/id_rsa.pub"
The authenticity of host '192.168.100.131 (192.168.100.131)' can't be established.
ED25519 key fingerprint is SHA256:vtIyTa7zBsS0Ppd25vJcwh2BXSPJbCQNKqBQQp28uJ0.
This key is not known by any other names.
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
/usr/bin/ssh-copy-id: INFO: attempting to log in with the new key(s), to filter out any that are already installed

/usr/bin/ssh-copy-id: WARNING: All keys were skipped because they already exist on the remote system.
                (if you think this is a mistake, you may want to use -f option)

shell> ssh root@192.168.100.131
Linux node1 6.5.11-8-pve #1 SMP PREEMPT_DYNAMIC PMX 6.5.11-8 (2024-01-30T12:27Z) x86_64

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Tue Oct  1 00:12:21 2024

ssh -o StrictHostKeyChecking=no root@192.168.100.131

#!/usr/bin/expect

set timeout 10
set password "Password@123"

spawn ssh root@192.168.100.131 "pvecm add $(hostname -I | awk '{print $1}')"
expect "password:"
send "$password\r"
interact

shell> echo "Password@123" | openssl enc -aes-256-cbc -a -salt -pbkdf2 -pass pass:your_secret_key > encrypted_password.txt

shell> cat encrypted_password.txt
U2FsdGVkX18GnipYdHi/cGCzHxcfg1EOYHQFPxeW4C8=

password=$(openssl enc -aes-256-cbc -d -a -salt -pbkdf2 -pass pass:your_secret_key -in encrypted_password.txt)

shell> echo $password
Password@123

shell> sshpass -p "$password" ssh-copy-id -o StrictHostKeyChecking=no root@192.168.100.131
/usr/bin/ssh-copy-id: INFO: Source of key(s) to be installed: "/root/.ssh/id_rsa.pub"
/usr/bin/ssh-copy-id: INFO: attempting to log in with the new key(s), to filter out any that are already installed

/usr/bin/ssh-copy-id: WARNING: All keys were skipped because they already exist on the remote system.
                (if you think this is a mistake, you may want to use -f option)

export MY_PASSWORD='Password@123'

sshpass -p "$MY_PASSWORD" ssh-copy-id -o StrictHostKeyChecking=no root@192.168.100.131

ansible-vault encrypt_string 'Password@123' --name 'ansible_password'

apt-get install sshpass

sshpass -p 'Password@123' ssh-copy-id -o StrictHostKeyChecking=no root@192.168.100.131

shell> pvecm add 192.168.100.131 --use_ssh --link0 192.168.100.133
copy corosync auth key
stopping pve-cluster service
backup old database to '/var/lib/pve-cluster/backup/config-1727717575.sql.gz'
waiting for quorum...OK
(re)generate node files
generate new node certificate
merge authorized SSH keys and known hosts
generated new node certificate, restart pveproxy and pvedaemon services
successfully added node 'node3' to cluster.

#!/bin/bash
# This script is used to add a new node to the Proxmox cluster
apt install sshpass
echo "Password@123" | openssl enc -aes-256-cbc -a -salt -pbkdf2 -pass pass:your_secret_key > encrypted_password.txt
password=$(openssl enc -aes-256-cbc -d -a -salt -pbkdf2 -pass pass:your_secret_key -in encrypted_password.txt)

sshpass -p "$password" ssh-copy-id -o StrictHostKeyChecking=no root@192.168.100.131
pvecm add 192.168.100.131 --use_ssh --link0 192.168.100.134

chmod +x join_node4.sh

shell>./join_node4.sh
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
  sshpass
0 upgraded, 1 newly installed, 0 to remove and 34 not upgraded.
Need to get 13.0 kB of archives.
After this operation, 38.9 kB of additional disk space will be used.
Get:1 http://ftp.debian.org/debian bookworm/main amd64 sshpass amd64 1.09-1+b1 [13.0 kB]
Fetched 13.0 kB in 0s (68.0 kB/s)
Selecting previously unselected package sshpass.
(Reading database ... 45698 files and directories currently installed.)
Preparing to unpack .../sshpass_1.09-1+b1_amd64.deb ...
Unpacking sshpass (1.09-1+b1) ...
Setting up sshpass (1.09-1+b1) ...
Processing triggers for man-db (2.11.2-2) ...
/usr/bin/ssh-copy-id: INFO: Source of key(s) to be installed: "/root/.ssh/id_rsa.pub"
/usr/bin/ssh-copy-id: INFO: attempting to log in with the new key(s), to filter out any that are already installed

/usr/bin/ssh-copy-id: WARNING: All keys were skipped because they already exist on the remote system.
                (if you think this is a mistake, you may want to use -f option)

copy corosync auth key
stopping pve-cluster service
backup old database to '/var/lib/pve-cluster/backup/config-1727718705.sql.gz'
waiting for quorum...OK
(re)generate node files
generate new node certificate
merge authorized SSH keys and known hosts
generated new node certificate, restart pveproxy and pvedaemon services
successfully added node 'node4' to cluster.

shell> pvecm status
Cluster information
-------------------
Name:             mycluster
Config Version:   4
Transport:        knet
Secure auth:      on

Quorum information
------------------
Date:             Tue Oct  1 00:54:21 2024
Quorum provider:  corosync_votequorum
Nodes:            4
Node ID:          0x00000004
Ring ID:          1.11
Quorate:          Yes

Votequorum information
----------------------
Expected votes:   4
Highest expected: 4
Total votes:      4
Quorum:           3
Flags:            Quorate

Membership information
----------------------
    Nodeid      Votes Name
0x00000001          1 192.168.100.131
0x00000002          1 192.168.100.132
0x00000003          1 192.168.100.133
0x00000004          1 192.168.100.134 (local)