Difference between revisions of "Hedvig : High Availability Proxies configurations"

From Define Wiki
Jump to navigation Jump to search
(Created page with "== Proxies set in HA == * Hedvig recommends to set the proxies in High Availability configuration. * Setting up HA over proxies in Virtual environment will require another cvm...")
 
 
Line 4: Line 4:
 
* This second machine should have be on same network as of other proxy.
 
* This second machine should have be on same network as of other proxy.
 
* While creation of the hedvig cluster edit tgt nodes file as follows.
 
* While creation of the hedvig cluster edit tgt nodes file as follows.
* Specify storage proxy entries in one of the formats in the sample configuration,
+
* Specify storage proxy entries in one of the formats in the sample configuration,depending on whether you are doing auto or manual routing.  
  depending on whether you are doing auto or manual routing.  
 
 
* Storage proxies require a VIP on the public network
 
* Storage proxies require a VIP on the public network
+
 
 
  <nowiki>
 
  <nowiki>
 
# Enter list of iscsi/nfs nodes below     
 
# Enter list of iscsi/nfs nodes below     

Latest revision as of 18:07, 27 July 2016

Proxies set in HA

  • Hedvig recommends to set the proxies in High Availability configuration.
  • Setting up HA over proxies in Virtual environment will require another cvm.ova to be deployed in ESXI.
  • This second machine should have be on same network as of other proxy.
  • While creation of the hedvig cluster edit tgt nodes file as follows.
  • Specify storage proxy entries in one of the formats in the sample configuration,depending on whether you are doing auto or manual routing.
  • Storage proxies require a VIP on the public network
# Enter list of iscsi/nfs nodes below    
# ----    
# sample config(standalone): host1    
#                            host2    
#    
# sample config(HA): host1,host2,vip=192.168.108.30,privatenet=172.22.22.0    
#                    host3,host4,vip=192.168.108.31,privatenet=172.22.22.0    
#    
# sample config(HA): host1,host2,vipname=host-vip,privatenet=172.22.22.0    
#                    host3,host4,vipname=host2-vip,privatenet=172.22.22.0    
#    
# supported attributes - for HA:    
#   vip        = virtual ip to be used with HA    
#   vipname    = virtual hostname to be used with HA    
#   privatenet = private network to be used with HA    
#   ssh_port   = port for mgmt to communicate with targets    
#   ----    
# primary,secondary,vip=<vip>,privatenet=<privatenet>    
# ----    

proxy1,proxy2,vip=172.22.28.243,privatenet=172.22.22.0