Secara umum, cluster server pada Proxmox versi 2.x tidak jauh berbeda dengan cluster server pada Proxmox 1.x. Letak perbedaanya adalah pada Proxmox versi 1.x menggunakan perintah pveca, sedangkan pada Proxmox versi 2.x kita dapat menggunakan perintah pvecm. Pada tulisan ini saya menggunakan Proxmox versi terbaru, yaitu Proxmox 2.1.
Adapun beberapa keuntungan dari cluster server Proxmox ini antara lain :
Sebelum kita membuat Proxmox Cluster server ada beberapa hal yang perlu diperhatikan antara lain, :
Berikut adalah langkah-langkahnya
root@pve1:~# pvecm create cluster1 Generating public/private rsa key pair. Your identification has been saved in /root/.ssh/id_rsa. Your public key has been saved in /root/.ssh/id_rsa.pub. The key fingerprint is: a7:5d:af:35:08:a0:39:20:0a:21:c4:74:ad:de:30:74 root@pve1.excellent.co.id The key's randomart image is: +--[ RSA 2048]----+ |*o .. | |.o.. E | |. o + . | |.. = . o . | |. . + + S o . | | . . . + o o | | . . . + | | o . | | . | +-----------------+ Restarting pve cluster filesystem: pve-cluster[dcdb] notice: wrote new cluster config '/etc/cluster/cluster.conf' . Starting cluster: Checking if cluster has been disabled at boot... [ OK ] Checking Network Manager... [ OK ] Global setup... [ OK ] Loading kernel modules... [ OK ] Mounting configfs... [ OK ] Starting cman... [ OK ] Waiting for quorum... [ OK ] Starting fenced... [ OK ] Starting dlm_controld... [ OK ] Unfencing self... [ OK ] root@pve1:~#
root@pve2:~# pvecm add 10.10.10.2 Generating public/private rsa key pair. Your identification has been saved in /root/.ssh/id_rsa. Your public key has been saved in /root/.ssh/id_rsa.pub. The key fingerprint is: ec:87:63:33:1f:35:cc:8f:f9:a8:25:6b:cb:97:d3:62 root@pve2 The key's randomart image is: +--[ RSA 2048]----+ | | | | | | | . o | | S = | | . . . = | | B + +o. | | . B.=Eo. | | .*=.o. | +-----------------+ The authenticity of host '10.10.10.2 (10.10.10.2)' can't be established. RSA key fingerprint is 67:5a:04:3e:f4:e4:ea:e3:aa:90:c9:f1:a6:9b:5e:68. Are you sure you want to continue connecting (yes/no)? yes root@10.10.10.2's password: copy corosync auth key stopping pve-cluster service Stopping pve cluster filesystem: pve-cluster. backup old database Starting pve cluster filesystem : pve-cluster. Starting cluster: Checking if cluster has been disabled at boot... [ OK ] Checking Network Manager... [ OK ] Global setup... [ OK ] Loading kernel modules... [ OK ] Mounting configfs... [ OK ] Starting cman... [ OK ] Waiting for quorum... [ OK ] Starting fenced... [ OK ] Starting dlm_controld... [ OK ] Unfencing self... [ OK ] waiting for quorum...OK generating node certificates merge known_hosts file restart services Restarting PVE Daemon: pvedaemon. Restarting web server: apache2 ... waiting . successfully added node 'pve2' to cluster. root@pve2:~#
Cek status cluster dengan perintah
root@pve1:~# pvecm nodes Node Sts Inc Joined Name 1 M 4 2012-07-03 08:54:12 pve1 2 M 8 2012-07-03 08:54:53 pve2 root@pve1:~#
Login ke web console pve1 yang memiliki ip 10.10.10.2 dan login seperti biasa. Jika tidak ada masalah harusnya tampilan pada web console akan seperti gambar dibawah ini.
Jika kita menggunakan SAN storage ataupun NFS storage untuk menyimpan data atau harddisk virtual dari VM yang kita miliki, kita dapat menggunakan feature live migration pada Proxmox seperti halnya vMotion pada VMware vSphere.
Semoga bermanfaat
Print This Post
Berikutnya kita lakukan konfigurasi heartbeat yang kaan mengatur failover sistem, alamat IP virtual, Apache, dan MySQL jika terjadi gagal booting salah satu sistem. Pada node1, tentukan cluster yang disertakan dalam file /etc/heartbeat/ha.cf. Contoh /etc/heartbeat/ha.cf: Logfacility local0 keepalive 2 deadtime 30 warntime 10 initdead 120 bcast eth0 bcast eth0 node node1 node node2 Catatan: nilai yang [...]
Pingback: Membuat Cluster Server pada Proxmox 2.1 – Defcone