meta data for this page
  •  

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
vm:proxmox:cluster [2020/04/26 18:52] – niziakvm:proxmox:cluster [2020/09/14 07:42] – niziak
Line 4: Line 4:
  
 Cluster is using ONE shared content of ''/etc/pve''. Content of this directory is synchronized on all cluster nodes. Cluster is using ONE shared content of ''/etc/pve''. Content of this directory is synchronized on all cluster nodes.
-IMPACT: +**IMPACT**: 
   * storage configuration is one for whole cluster. To create local node storage, storage should be limited only own node.   * storage configuration is one for whole cluster. To create local node storage, storage should be limited only own node.
-  * Joining pure Debian based node (BTRFS FS) to cluster will result with "local-zfs" storage visible on Debian BTRFS node with ''?'' sign.  +  * Joining pure Debian based node (BTRFS FS) to cluster will result with "local-zfs" storage visible on Debian BTRFS node with ''?'' sign. To prevent creation unusable storage, storage can be limited to some nodes. Please edit storage and limit it to own node. 
-To prevent creation unusable storage, storage can be limited to some nodes. Please edit storage and limit it to own node. +  * Custom storage config on nodes can disappear because only one shared config is used
-  * Some custom storages config on nodes can disappear because only one shared config is used+
      * Storage removed due to cluster joining can be added manually under another name and then restricted to specific node.      * Storage removed due to cluster joining can be added manually under another name and then restricted to specific node.
 +     * [[vm:proxmox:zfs#create_local-zfs|create "local-zfs"]]
 +**NOTE**: make copy of ''/etc/pve/storage.cfg'' from each node before joining to cluster.
 +
 +==== local-ZFS replication ====
 +
 +It is possible to schedule replication of containers/VMs to another node. It makes periodic snapshot on remote local storage. 
 +It gives data redundancy and reduces downtime when container is moved between local storage on each node.
  
-NOTE: make copy of ''/etc/pve/storage.cfg'' from each node before joining to cluster. 
  
 ==== shared storage ==== ==== shared storage ====
Line 53: Line 58:
 Joining process will be waiting infinitely until iSCSI device will be connected. During this time it is possible to disable CHAP authentication in remote iSCSI target, or provide common credentials for Target Portal Group. Joining process will be waiting infinitely until iSCSI device will be connected. During this time it is possible to disable CHAP authentication in remote iSCSI target, or provide common credentials for Target Portal Group.
  
-==== iSCSI issue with CHAP ====+===== Remove failed node ===== 
 +<code bash> 
 +pvecm status
  
-When CHAP is used for iSCSI (manually configured from Debian console), joined node wants to connect to the same iSCSI target using own initiator name and own local configuration. Of coruse NAS326 is configured with only one CHAP login and passwod, so joining is not possible.+Highest expected: 4 
 +</code> 
 +<code bash> 
 +pvecm delnode <hostname>
  
-Is it possible to add new acl for target on NAS326 using ''targetcli'' command, or disable CHAP.+Killing node 2 
 +</code> 
 +<code bash> 
 +pvecm status
  
 +Highest expected: 3
 +</code>
 +And reload WebUI to refresh cluster nodes.
  
 +==== iSCSI issue with CHAP ====
  
-====== CEPH ====== +When CHAP is used for iSCSI (manually configured from Debian console), joined node wants to connect to the same iSCSI target using own initiator name and own local configuration. Of coruse NAS326 is configured with only one CHAP login and passwod, so joining is not possible.
- +
-===== Installation ===== +
- +
-  * On one of node: +
-    * Datacenter --> Cepth --> Install Ceph-nautilus +
-    * Configuration tab +
-    * First Ceph monitor - set to current node. NOTE. Not possible to use other nodes now because there is no Ceph installed on it +
-  * Repeat installation on each node. Configuration will be detected automatically. +
-  * On each node - add additional monitors: +
-    * Select node --> Ceph --> Monitor +
-      * "Create" button in Monitor section, and select available nodes. +
- +
-===== create OSD ===== +
- +
-Create Object Storage Daemon +
  
 +Is it possible to add new acl for target on NAS326 using ''targetcli'' command, or disable CHAP.
  
  
-