Hello Devendra,

In the spirit of assisting, further to Pavlos' insights, you might want to 
check 

Baptiste Assman's blog on 1.5 vs. 1.6 below.  It is our understanding that the 
new features in 1.6 have been mostly carried over to 1.7 as well.
https://www.haproxy.com/blog/whats-new-in-haproxy-1-6/ 
Examples include bind <IP>:<port>, environmental variables

Willy Tarreau's note during general release of 1.6:  
https://www.mail-archive.com/haproxy@formilux.org/msg19877.html
1.7: https://www.mail-archive.com/haproxy@formilux.org/msg24244.html 

Thank you.

Sincerely,

Hemant K. Sabat
 
Coscend Communications Solutions
www.Coscend.com 
------------------------------------------------------------------
Real-time, Interactive Video Collaboration, Tele-healthcare, Tele-education, 
Telepresence Services, on the fly…
------------------------------------------------------------------
CONFIDENTIALITY NOTICE: See 'Confidentiality Notice Regarding E-mail Messages 
from Coscend Communications Solutions' posted at: 
http://www.Coscend.com/Terms_and_Conditions.html 



-----Original Message-----
From: Pavlos Parissis [mailto:pavlos.paris...@gmail.com] 
Sent: Thursday, June 8, 2017 2:53 AM
To: Devendra Joshi <devendra.jo...@naaptol.com>; haproxy@formilux.org
Subject: Re: Regarding migration on version haproxy-1.7.3

On 06/08/2017 07:31 AM, Devendra Joshi wrote:
> Hi,
> currently we are using haproxy-1.5.14 & now we want to migrate on 
> haproxy-1.7.3 
> <https://www.mail-archive.com/search?l=haproxy@formilux.org&q=subject:
> %22%5C%5BANNOUNCE%5C%5D+haproxy%5C-1.7.3%22&o=newest>
> 
> is there any config changes or need to do some setting.
> 

You should always test a software before you push it to production.
In most of the cases I have seen the upgrade is very smooth, but it depends on 
the configuration.
Some people never change the config they created with 1.4 version and get in 
troubles when they upgrade to 1.6 or 1.7 version.

Just build a test machine, load the config, check for errors and then test it 
with some traffic.
In case of troubles in production after the upgrade, you can easily roll back 
by downgrading the package.

1.7.6 version is coming soon, so you may want to wait few days for that one to 
be released before you upgrade production.

Cheers,
Pavlos



Reply via email to