Hello David (and dear Operators!),

You are 100% correct, this topic could be interesting for operators.

Here is food for thoughts on “How do you haproxy for openstack-ansible?”:
https://etherpad.openstack.org/p/openstack-ansible-haproxy-improvements

Feel free to comment there!

Best regards,
Jean-Philippe Evrard (evrardjp)


From: David Moreau Simard <d...@redhat.com>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
<openstack-...@lists.openstack.org>
Date: Friday, 11 November 2016 at 12:40
To: "OpenStack Development Mailing List (not for usage questions)" 
<openstack-...@lists.openstack.org>
Subject: Re: [openstack-dev] [openstack-ansible] How do you haproxy?


I feel like you might get valuable feedback by cross-posting this to 
openstack-operators.

David Moreau Simard
Senior Software Engineer | Openstack RDO

dmsimard = [irc, github, twitter]

On Nov 10, 2016 7:40 AM, "Jean-Philippe Evrard" 
<jean-philippe.evr...@rackspace.co.uk<mailto:jean-philippe.evr...@rackspace.co.uk>>
 wrote:
Hello,

In openstack-ansible, we are using haproxy (and keepalived) as load balancer 
mechanism.
We’ve been recommending to use hardware load balancers for a while, but I think 
it’s time to improve haproxy configuration flexibility and testing.

I’m gathering requirements of what you’d like to see in haproxy.

I have an etherpad set up, and I’d be happy if you could fill your comments 
there:
https://etherpad.openstack.org/p/openstack-ansible-haproxy-improvements

Thank you in advance.

Best regards,
Jean-Philippe Evrard (evrardjp)

________________________________
Rackspace Limited is a company registered in England & Wales (company 
registered number 03897010) whose registered office is at 5 Millington Road, 
Hyde Park Hayes, Middlesex UB3 4AZ. Rackspace Limited privacy policy can be 
viewed at 
www.rackspace.co.uk/legal/privacy-policy<http://www.rackspace.co.uk/legal/privacy-policy>
 - This e-mail message may contain confidential or privileged information 
intended for the recipient. Any dissemination, distribution or copying of the 
enclosed material is prohibited. If you receive this transmission in error, 
please notify us immediately by e-mail at 
ab...@rackspace.com<mailto:ab...@rackspace.com> and delete the original 
message. Your cooperation is appreciated.

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Reply via email to