You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by Tejas Gadaria <re...@gmail.com> on 2014/06/26 19:25:34 UTC
Cloudstack MS failover
I want to setup HA of MS with HAproxy OR Keepalived.
I have MS1 & DB1 installed on 10.1.1.2 &
MS2 & DB2 installed on 10.1.1.3
also DB has master - master replication setup.
Need help on this how can i setup failover for MS.
Regards,
Tejas
Re: Cloudstack MS failover
Posted by sebgoa <ru...@gmail.com>.
On Jun 27, 2014, at 6:30 AM, Abhinandan Prateek <Ab...@citrix.com> wrote:
> http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.1.0/html/Instal
> lation_Guide/management-server-install-flow.html
You should use the new documentation:
http://docs.cloudstack.apache.org/projects/cloudstack-installation/en/latest/installation.html#management-server-installation
>
> Section 4.5.7 has instructions on adding additional MS.
>
> -abhi
>
> On 26/06/14 10:55 pm, "Tejas Gadaria" <re...@gmail.com> wrote:
>
>> I want to setup HA of MS with HAproxy OR Keepalived.
>>
>> I have MS1 & DB1 installed on 10.1.1.2 &
>> MS2 & DB2 installed on 10.1.1.3
>>
>> also DB has master - master replication setup.
>>
>> Need help on this how can i setup failover for MS.
>>
>> Regards,
>> Tejas
>
Re: Cloudstack MS failover
Posted by Abhinandan Prateek <Ab...@citrix.com>.
http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.1.0/html/Instal
lation_Guide/management-server-install-flow.html
Section 4.5.7 has instructions on adding additional MS.
-abhi
On 26/06/14 10:55 pm, "Tejas Gadaria" <re...@gmail.com> wrote:
>I want to setup HA of MS with HAproxy OR Keepalived.
>
>I have MS1 & DB1 installed on 10.1.1.2 &
>MS2 & DB2 installed on 10.1.1.3
>
>also DB has master - master replication setup.
>
>Need help on this how can i setup failover for MS.
>
>Regards,
>Tejas
Re: Cloudstack MS failover
Posted by "DATACOM - Marcelo.Veriato" <ma...@datacom.ind.br>.
yeap
--
Marcelo Veriato Lima
DATACOM
On 06/27/2014 12:06 AM, Tejas Gadaria wrote:
> Hi,
> Also on clodstack side in Globle configuration do I need to replace host ip
> with virtual ip ?
>
> Regards,
> Tejas
>
>
> On Fri, Jun 27, 2014 at 12:29 AM, DATACOM - Marcelo.Veriato <
> marcelo.veriato@datacom.ind.br> wrote:
>
>> My HA environment (active-standby) to MS is ok with keepalived. Just need
>> a floating IP address. My structure is two servers for MS and two for DB,
>> with acs 4.2 I use keepalived for database servers too, with 4.3 I use
>> native database HA ... https://cwiki.apache.org/confluence/pages/viewpage.
>> action?pageId=34838207 ... attention to bug 6892.
>>
>> ms01 keepalived.conf example
>>
>> # keepalived.conf is the configuration file which
>> # describes all the keepalived keywords. keywords are
>> # placed in hierachies of blocks (and subblocks), each
>> # layer being delimited by '{' and '}' pairs.
>>
>> # Comments start with '#' or '!' to the end of the
>> # line and can start anywhere in a line.
>>
>> # Global configuration
>> global_defs {
>> # To: to address that will be in header
>> notification_email {
>> cloudadmins@yourdomain.com
>> }
>> # From: from address that will be in header
>> notification_email_from root@ms01.yourdomain.com
>> # SMTP server IP or hostname
>> smtp_server localhost
>> # SMTP server timeout in seconds
>> smtp_connect_timeout 30
>> # String identifying the machine
>> router_id ms01
>> }
>>
>> # VRRP Script declaration
>> vrrp_script check_java {
>> # Script to run periodically
>> script "pidof java"
>> # Run the script this every seconds
>> interval 2
>> # Adjust priority by this weight
>> weight 10
>> }
>>
>> # VRRP instance declaration
>> vrrp_instance eth0 {
>> # Initial state, MASTER|BACKUP
>> # As soon as the other machine(s) come up,
>> # an election will be held and the machine
>> # with the highest "priority" will become MASTER.
>> # So the entry here doesn't matter a whole lot.
>> state master
>> # Interface for instance, bound by vrrp.
>> interface eth0
>> # Arbitary unique number 0..255
>> # Used to differentiate multiple instances of vrrpd
>> # running on the same NIC or VLAN(and hence same socket).
>> virtual_router_id <VRID>
>> # For electing MASTER, highest priority wins.
>> # to be MASTER, make 50 more than other machines.
>> priority 100
>> # VRRP Advert interval, in seconds.
>> advert_int 3
>> # Authentication block
>> authentication {
>> # PASS||AH
>> # PASS - Simple Passwd (suggested)
>> # AH - IPSEC (not recommended))
>> auth_type PASS
>> # Password for accessing vrrpd.
>> # should be the same for all machines.
>> # Only the first eight (8) characters are used.
>> auth_pass vrrpms123
>> }
>> # Script state we monitor
>> track_script {
>> check_java
>> }
>> # Addresses add|del on change to MASTER, to BACKUP.
>> # With the same entries on other machines,
>> # the opposite transition will be occuring.
>> virtual_ipaddress {
>> <VIRTUAL_IP> dev eth0 label eth0:vip
>> }
>> }
>>
>>
>> ms02 - keepalived.conf
>>
>> # keepalived.conf is the configuration file which
>> # describes all the keepalived keywords. keywords are
>> # placed in hierachies of blocks (and subblocks), each
>> # layer being delimited by '{' and '}' pairs.
>>
>> # Comments start with '#' or '!' to the end of the
>> # line and can start anywhere in a line.
>>
>> # Global configuration
>> global_defs {
>> # To: to address that will be in header
>> notification_email {
>> cloudadmins@yourdomain.com
>> }
>> # From: from address that will be in header
>> notification_email_from root@ms02.yourdomain.com
>> # SMTP server IP or hostname
>> smtp_server localhost
>> # SMTP server timeout in seconds
>> smtp_connect_timeout 30
>> # String identifying the machine
>> router_id ms02
>> }
>>
>> # VRRP instance declaration
>> vrrp_instance eth0 {
>> # Initial state, MASTER|BACKUP
>> # As soon as the other machine(s) come up,
>> # an election will be held and the machine
>> # with the highest "priority" will become MASTER.
>> # So the entry here doesn't matter a whole lot.
>> state backup
>> # Interface for instance, bound by vrrp.
>> interface eth0
>> # Arbitary unique number 0..255
>> # Used to differentiate multiple instances of vrrpd
>> # running on the same NIC or VLAN(and hence same socket).
>> virtual_router_id <VRID>
>> # For electing MASTER, highest priority wins.
>> # to be MASTER, make 50 more than other machines.
>> priority 105
>> # VRRP Advert interval, in seconds.
>> advert_int 3
>> # Authentication block
>> authentication {
>> # PASS||AH
>> # PASS - Simple Passwd (suggested)
>> # AH - IPSEC (not recommended))
>> auth_type PASS
>> # Password for accessing vrrpd.
>> # should be the same for all machines.
>> # Only the first eight (8) characters are used.
>> auth_pass vrrpms123
>> }
>> # Addresses add|del on change to MASTER, to BACKUP.
>> # With the same entries on other machines,
>> # the opposite transition will be occuring.
>> virtual_ipaddress {
>> <VIRTUAL_IP> dev eth0 label eth0:vip
>> }
>> }
>>
>> pay attention in virtual_router_id parameter not to conflict with another
>> vrrp instance.
>>
>> --
>> Marcelo Veriato Lima
>> DATACOM
>>
>>
>>
>> On 06/26/2014 02:25 PM, Tejas Gadaria wrote:
>>
>>> I want to setup HA of MS with HAproxy OR Keepalived.
>>>
>>> I have MS1 & DB1 installed on 10.1.1.2 &
>>> MS2 & DB2 installed on 10.1.1.3
>>>
>>> also DB has master - master replication setup.
>>>
>>> Need help on this how can i setup failover for MS.
>>>
>>> Regards,
>>> Tejas
>>>
>>>
Re: Cloudstack MS failover
Posted by Tejas Gadaria <re...@gmail.com>.
Hi,
Also on clodstack side in Globle configuration do I need to replace host ip
with virtual ip ?
Regards,
Tejas
On Fri, Jun 27, 2014 at 12:29 AM, DATACOM - Marcelo.Veriato <
marcelo.veriato@datacom.ind.br> wrote:
> My HA environment (active-standby) to MS is ok with keepalived. Just need
> a floating IP address. My structure is two servers for MS and two for DB,
> with acs 4.2 I use keepalived for database servers too, with 4.3 I use
> native database HA ... https://cwiki.apache.org/confluence/pages/viewpage.
> action?pageId=34838207 ... attention to bug 6892.
>
> ms01 keepalived.conf example
>
> # keepalived.conf is the configuration file which
> # describes all the keepalived keywords. keywords are
> # placed in hierachies of blocks (and subblocks), each
> # layer being delimited by '{' and '}' pairs.
>
> # Comments start with '#' or '!' to the end of the
> # line and can start anywhere in a line.
>
> # Global configuration
> global_defs {
> # To: to address that will be in header
> notification_email {
> cloudadmins@yourdomain.com
> }
> # From: from address that will be in header
> notification_email_from root@ms01.yourdomain.com
> # SMTP server IP or hostname
> smtp_server localhost
> # SMTP server timeout in seconds
> smtp_connect_timeout 30
> # String identifying the machine
> router_id ms01
> }
>
> # VRRP Script declaration
> vrrp_script check_java {
> # Script to run periodically
> script "pidof java"
> # Run the script this every seconds
> interval 2
> # Adjust priority by this weight
> weight 10
> }
>
> # VRRP instance declaration
> vrrp_instance eth0 {
> # Initial state, MASTER|BACKUP
> # As soon as the other machine(s) come up,
> # an election will be held and the machine
> # with the highest "priority" will become MASTER.
> # So the entry here doesn't matter a whole lot.
> state master
> # Interface for instance, bound by vrrp.
> interface eth0
> # Arbitary unique number 0..255
> # Used to differentiate multiple instances of vrrpd
> # running on the same NIC or VLAN(and hence same socket).
> virtual_router_id <VRID>
> # For electing MASTER, highest priority wins.
> # to be MASTER, make 50 more than other machines.
> priority 100
> # VRRP Advert interval, in seconds.
> advert_int 3
> # Authentication block
> authentication {
> # PASS||AH
> # PASS - Simple Passwd (suggested)
> # AH - IPSEC (not recommended))
> auth_type PASS
> # Password for accessing vrrpd.
> # should be the same for all machines.
> # Only the first eight (8) characters are used.
> auth_pass vrrpms123
> }
> # Script state we monitor
> track_script {
> check_java
> }
> # Addresses add|del on change to MASTER, to BACKUP.
> # With the same entries on other machines,
> # the opposite transition will be occuring.
> virtual_ipaddress {
> <VIRTUAL_IP> dev eth0 label eth0:vip
> }
> }
>
>
> ms02 - keepalived.conf
>
> # keepalived.conf is the configuration file which
> # describes all the keepalived keywords. keywords are
> # placed in hierachies of blocks (and subblocks), each
> # layer being delimited by '{' and '}' pairs.
>
> # Comments start with '#' or '!' to the end of the
> # line and can start anywhere in a line.
>
> # Global configuration
> global_defs {
> # To: to address that will be in header
> notification_email {
> cloudadmins@yourdomain.com
> }
> # From: from address that will be in header
> notification_email_from root@ms02.yourdomain.com
> # SMTP server IP or hostname
> smtp_server localhost
> # SMTP server timeout in seconds
> smtp_connect_timeout 30
> # String identifying the machine
> router_id ms02
> }
>
> # VRRP instance declaration
> vrrp_instance eth0 {
> # Initial state, MASTER|BACKUP
> # As soon as the other machine(s) come up,
> # an election will be held and the machine
> # with the highest "priority" will become MASTER.
> # So the entry here doesn't matter a whole lot.
> state backup
> # Interface for instance, bound by vrrp.
> interface eth0
> # Arbitary unique number 0..255
> # Used to differentiate multiple instances of vrrpd
> # running on the same NIC or VLAN(and hence same socket).
> virtual_router_id <VRID>
> # For electing MASTER, highest priority wins.
> # to be MASTER, make 50 more than other machines.
> priority 105
> # VRRP Advert interval, in seconds.
> advert_int 3
> # Authentication block
> authentication {
> # PASS||AH
> # PASS - Simple Passwd (suggested)
> # AH - IPSEC (not recommended))
> auth_type PASS
> # Password for accessing vrrpd.
> # should be the same for all machines.
> # Only the first eight (8) characters are used.
> auth_pass vrrpms123
> }
> # Addresses add|del on change to MASTER, to BACKUP.
> # With the same entries on other machines,
> # the opposite transition will be occuring.
> virtual_ipaddress {
> <VIRTUAL_IP> dev eth0 label eth0:vip
> }
> }
>
> pay attention in virtual_router_id parameter not to conflict with another
> vrrp instance.
>
> --
> Marcelo Veriato Lima
> DATACOM
>
>
>
> On 06/26/2014 02:25 PM, Tejas Gadaria wrote:
>
>> I want to setup HA of MS with HAproxy OR Keepalived.
>>
>> I have MS1 & DB1 installed on 10.1.1.2 &
>> MS2 & DB2 installed on 10.1.1.3
>>
>> also DB has master - master replication setup.
>>
>> Need help on this how can i setup failover for MS.
>>
>> Regards,
>> Tejas
>>
>>
>
Re: Cloudstack MS failover
Posted by "DATACOM - Marcelo.Veriato" <ma...@datacom.ind.br>.
My HA environment (active-standby) to MS is ok with keepalived. Just
need a floating IP address. My structure is two servers for MS and two
for DB, with acs 4.2 I use keepalived for database servers too, with 4.3
I use native database HA ...
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=34838207 ...
attention to bug 6892.
ms01 keepalived.conf example
# keepalived.conf is the configuration file which
# describes all the keepalived keywords. keywords are
# placed in hierachies of blocks (and subblocks), each
# layer being delimited by '{' and '}' pairs.
# Comments start with '#' or '!' to the end of the
# line and can start anywhere in a line.
# Global configuration
global_defs {
# To: to address that will be in header
notification_email {
cloudadmins@yourdomain.com
}
# From: from address that will be in header
notification_email_from root@ms01.yourdomain.com
# SMTP server IP or hostname
smtp_server localhost
# SMTP server timeout in seconds
smtp_connect_timeout 30
# String identifying the machine
router_id ms01
}
# VRRP Script declaration
vrrp_script check_java {
# Script to run periodically
script "pidof java"
# Run the script this every seconds
interval 2
# Adjust priority by this weight
weight 10
}
# VRRP instance declaration
vrrp_instance eth0 {
# Initial state, MASTER|BACKUP
# As soon as the other machine(s) come up,
# an election will be held and the machine
# with the highest "priority" will become MASTER.
# So the entry here doesn't matter a whole lot.
state master
# Interface for instance, bound by vrrp.
interface eth0
# Arbitary unique number 0..255
# Used to differentiate multiple instances of vrrpd
# running on the same NIC or VLAN(and hence same socket).
virtual_router_id <VRID>
# For electing MASTER, highest priority wins.
# to be MASTER, make 50 more than other machines.
priority 100
# VRRP Advert interval, in seconds.
advert_int 3
# Authentication block
authentication {
# PASS||AH
# PASS - Simple Passwd (suggested)
# AH - IPSEC (not recommended))
auth_type PASS
# Password for accessing vrrpd.
# should be the same for all machines.
# Only the first eight (8) characters are used.
auth_pass vrrpms123
}
# Script state we monitor
track_script {
check_java
}
# Addresses add|del on change to MASTER, to BACKUP.
# With the same entries on other machines,
# the opposite transition will be occuring.
virtual_ipaddress {
<VIRTUAL_IP> dev eth0 label eth0:vip
}
}
ms02 - keepalived.conf
# keepalived.conf is the configuration file which
# describes all the keepalived keywords. keywords are
# placed in hierachies of blocks (and subblocks), each
# layer being delimited by '{' and '}' pairs.
# Comments start with '#' or '!' to the end of the
# line and can start anywhere in a line.
# Global configuration
global_defs {
# To: to address that will be in header
notification_email {
cloudadmins@yourdomain.com
}
# From: from address that will be in header
notification_email_from root@ms02.yourdomain.com
# SMTP server IP or hostname
smtp_server localhost
# SMTP server timeout in seconds
smtp_connect_timeout 30
# String identifying the machine
router_id ms02
}
# VRRP instance declaration
vrrp_instance eth0 {
# Initial state, MASTER|BACKUP
# As soon as the other machine(s) come up,
# an election will be held and the machine
# with the highest "priority" will become MASTER.
# So the entry here doesn't matter a whole lot.
state backup
# Interface for instance, bound by vrrp.
interface eth0
# Arbitary unique number 0..255
# Used to differentiate multiple instances of vrrpd
# running on the same NIC or VLAN(and hence same socket).
virtual_router_id <VRID>
# For electing MASTER, highest priority wins.
# to be MASTER, make 50 more than other machines.
priority 105
# VRRP Advert interval, in seconds.
advert_int 3
# Authentication block
authentication {
# PASS||AH
# PASS - Simple Passwd (suggested)
# AH - IPSEC (not recommended))
auth_type PASS
# Password for accessing vrrpd.
# should be the same for all machines.
# Only the first eight (8) characters are used.
auth_pass vrrpms123
}
# Addresses add|del on change to MASTER, to BACKUP.
# With the same entries on other machines,
# the opposite transition will be occuring.
virtual_ipaddress {
<VIRTUAL_IP> dev eth0 label eth0:vip
}
}
pay attention in virtual_router_id parameter not to conflict with
another vrrp instance.
--
Marcelo Veriato Lima
DATACOM
On 06/26/2014 02:25 PM, Tejas Gadaria wrote:
> I want to setup HA of MS with HAproxy OR Keepalived.
>
> I have MS1 & DB1 installed on 10.1.1.2 &
> MS2 & DB2 installed on 10.1.1.3
>
> also DB has master - master replication setup.
>
> Need help on this how can i setup failover for MS.
>
> Regards,
> Tejas
>
Re: Cloudstack MS failover
Posted by Abhinandan Prateek <Ab...@citrix.com>.
http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.1.0/html/Instal
lation_Guide/management-server-install-flow.html
Section 4.5.7 has instructions on adding additional MS.
-abhi
On 26/06/14 10:55 pm, "Tejas Gadaria" <re...@gmail.com> wrote:
>I want to setup HA of MS with HAproxy OR Keepalived.
>
>I have MS1 & DB1 installed on 10.1.1.2 &
>MS2 & DB2 installed on 10.1.1.3
>
>also DB has master - master replication setup.
>
>Need help on this how can i setup failover for MS.
>
>Regards,
>Tejas