Erinevus lehekülje "Proxmox VE 3.x" redaktsioonide vahel
| 12. rida: | 12. rida: | ||
[[Pilt:Screen-Add-HA-managed VM-CT.png]] | [[Pilt:Screen-Add-HA-managed VM-CT.png]] | ||
| − | # pveperf | + | # pveperf |
| − | CPU BOGOMIPS: | + | CPU BOGOMIPS: 127992.00 |
| − | REGEX/SECOND: | + | REGEX/SECOND: 1026892 |
| − | HD SIZE: | + | HD SIZE: 9.17 GB (/dev/sda5) |
| − | BUFFERED READS: | + | BUFFERED READS: 106.64 MB/sec |
| − | AVERAGE SEEK TIME: | + | AVERAGE SEEK TIME: 6.47 ms |
| − | FSYNCS/SECOND: | + | FSYNCS/SECOND: 2806.00 |
| − | DNS EXT: | + | DNS EXT: 64.95 ms |
| − | DNS INT: | + | DNS INT: 0.96 ms (eenet.ee) |
===Install=== | ===Install=== | ||
Redaktsioon: 10. jaanuar 2013, kell 22:48
TODO
Võrreldes varasema versiooniga on kasutajaliides põhjalikult ümber kirjutatud-disainitud.
- Kõik clustri noded on VÕRDSED. Pole enam master-slave tüüpi clustrit.
- Backup-restore haldusliidesest lihtsam
- haila-vaila (HA), ehk kui üks masin jukerdab starditakse virtuaalmasinat automaatselt teisel.
- kasutajate haldus, võimalik luua erinevate ligipääsuõigustega kasutajaid
- rrdtooliga genereeritud koormusgraafikud iga virtuaalmasina kohta
- Proxmoxi API virtuaalmasinate loomiseks
# pveperf CPU BOGOMIPS: 127992.00 REGEX/SECOND: 1026892 HD SIZE: 9.17 GB (/dev/sda5) BUFFERED READS: 106.64 MB/sec AVERAGE SEEK TIME: 6.47 ms FSYNCS/SECOND: 2806.00 DNS EXT: 64.95 ms DNS INT: 0.96 ms (eenet.ee)
Install
Check your sources.list file, should look like this:
deb http://http.at.debian.org/debian squeeze main contrib # PVE packages provided by proxmox.com deb http://download.proxmox.com/debian squeeze pve # security updates deb http://security.debian.org/ squeeze/updates main contrib
# aptitude install proxmox-ve-2.6.32
Cluster
Meil on kaks masinat 10.40.0.6 ja 10.40.0.7 ning tahame nad panna koos tööle. PS: Manual soovitab veidra käitumise vältimiseks kasutada vähemalt 3me nodet, kuid on võimalik panna tööle ka 2 masinat clustris. Lähemalt http://pve.proxmox.com/wiki/Two-Node_High_Availability_Cluster
Logime üle SSH esimesse clustri nodesse (10.0.0.6) ja anname käsu
# pvecm create YOUR-CLUSTER-NAME
To check the state of cluster:
# pvecm status
Seejärel logime teise clustri nodesse (10.40.0.7) ja anname seal käsu
# pvecm add 10.0.0.6 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 'jagaja' to cluster.
Konfiguratsioon /etc/pve/cluster.conf
<?xml version="1.0"?>
<cluster config_version="3" name="hailavaila">
<cman keyfile="/var/lib/pve-cluster/corosync.authkey"/>
<clusternodes>
<clusternode name="koguja" nodeid="1" votes="1"/>
<clusternode name="jagaja" nodeid="2" votes="1"/>
</clusternodes>
</cluster>
To be able to create and manage a two-node cluster, edit the cman configuration part to include this:
<cman two_node="1" expected_votes="1"> </cman>
Now, add the available fencing devices to the config files by adding this lines (it is ok right after </clusternodes>):
<fencedevices>
<fencedevice agent="fence_ilo" hostname="nodeA.your.domain" login="hpilologin" name="fenceNodeA" passwd="hpilopword"/>
<fencedevice agent="fence_ilo" hostname="nodeB.your.domain" login="hpilologin" name="fenceNodeB" passwd="hpilologin"/>
</fencedevices>
Näiteks sedamoodi
<?xml version="1.0"?>
<cluster config_version="4" name="hailavaila">
<cman keyfile="/var/lib/pve-cluster/corosync.authkey" two_node="1" expected_votes="1"/>
<clusternodes>
<clusternode name="koguja" nodeid="1" votes="1"/>
<clusternode name="jagaja" nodeid="2" votes="1"/>
</clusternodes>
<rm>
<pvevm autostart="1" vmid="104"/>
</rm>
<fencedevices>
<fencedevice agent="fence_ilo" hostname="10.0.1.6" login="admin" name="jagaja" passwd="parool"/>
<fencedevice agent="fence_ilo" hostname="10.0.1.7" login="admin" name="koguja" passwd="parool"/>
</fencedevices>
</cluster>
order to get fencing active, you also need to join each node to the fencing domain. To the following on all your cluster nodes. Enable fencing in /etc/default/redhat-cluster-pve (Just uncomment the last line, see below):
/etc/default/redhat-cluster-pve
# CLUSTERNAME="" # NODENAME="" # USE_CCS="yes" # CLUSTER_JOIN_TIMEOUT=300 # CLUSTER_JOIN_OPTIONS="" # CLUSTER_SHUTDOWN_TIMEOUT=60 # RGMGR_OPTIONS="" FENCE_JOIN="yes"
Lisaks tuleb mõlemas nodes käivitada käsk:
# fence_tool join
Staatust saab vaadata:
# fence_tool ls fence domain member count 2 victim count 0 victim now 0 master nodeid 2 wait state none members 1 2
Be sure to increase the number "config_version" each time you plan to apply new configurations as this is the internal mechanism used by the cluster configuration tools to detect new changes.
Clustri node hooldus
If you need to reboot a node, e.g. because of a kernel update you need to stop rgmanager. By doing this, all resources are stopped and moved to other nodes. All KVM guests will get a ACPI shutdown request (if this does not work due to VM internal setting just a 'stop'). You can stop the rgmanager service via GUI or just run:
#/etc/init.d/rgmanager stop
Kui midagi läs ikkagi viltu siis saab kõigi nodede konfiguratsiooni nullida ära järgmiste käskudega
service cman stop service pve-cluster stop rm /etc/cluster/cluster.conf rm /var/lib/pve-cluster/* service pve-cluster start service cman start
Probleemide korral kontrollida kas /etc/hosts failis on mõlemas masinas info korrektne, on proxmoxi versioon identne ning kellaajad süngis.
- permission denied - invalid ticket (401)
# pvecm updatecerts --force
I guess you need to restart pvedaemon and apache2 (or simply reboot).
Päris bugivaba see uus proxmox pole. HA optsiooni lisamisega läks miskipärast katki võimalus migreerida omatahtmist mööda virtuaalmasinaid
Executing HA migrate for VM 109 to node jagaja Trying to migrate pvevm:109 to jagaja...Target node dead / nonexistent TASK ERROR: command 'clusvcadm -M pvevm:109 -m jagaja' failed: exit code 244
Paistab teistelgi sarnaseid jamasid
Peab kaevama.
Ubuntus java paikaseadmine
How to switch Firefox Java plugin to Sun Java on Ubuntu Linux
Open Synaptic and go to Settings -> Repositories -> Other Software and activate the Canonical partner repo. Now close Synaptic, fire up a terminal and run the following commands in order, selecting Sun Java (java-6-sun) where appropriate:
sudo apt-get update sudo apt-get install sun-java6-bin sun-java6-fonts sun-java6-jdk sun-java6-plugin sudo update-alternatives --config java
The tricky part is: even when you have Sun's Java runtime installed, Firefox will still default to the open source IcedTea plugin, unless you tell it not to. Run the following command and select Sun's Java web browser plugin:
sudo update-alternatives --config mozilla-javaplugin.so
