Hi,
On 18.04.2014 08:24, Willy Tarreau wrote:
On Thu, Apr 17, 2014 at 10:30:45AM -0500, Ryan O'Hara wrote:
On Wed, Apr 16, 2014 at 11:12:07PM +0100, Kobus Bensch wrote:
I use haproxy on centos. So I build a RPM i then use in spacewalk to
first roll out to test, then post testing to
Hi List
I use haproxy on centos. I regularly build a RPM I then use in spacewalk
to first roll out to test, then post testing to production.
This process works great as if we need to roll back we can do that very
easily.
Kobus
On 17/04/2014 08:10, Vincent Bernat wrote:
❦ 16 avril 2014
On Wed, Apr 16, 2014 at 11:12:07PM +0100, Kobus Bensch wrote:
I use haproxy on centos. So I build a RPM i then use in spacewalk to
first roll out to test, then post testing to production.
I can add el6 to my copr build if you need an rpm build. Currently I'm
only building 1.5-dev22 in copr for
Hi Jonathan,
On 22:27 Mon 14 Apr , Jonathan Matthews wrote:
Hi all -
I've been running 1.4 for a number of years, but am pondering moving
some as-yet-unreleased apps to 1.5, for SSL and ACL-ish reasons.
I'd like to ask how you, 1.5 sysadmins and devs, track the development
version,
Hi Apollon,
On Wed, Apr 16, 2014 at 11:33:37AM +0300, Apollon Oikonomopoulos wrote:
(...)
We run a -dev version - not necessarily the latest one, just one that is
running stable and has no security issues. In general I follow the list
on a daily basis (not reading through every mail though)
Am 16.04.2014 17:40 schrieb Willy Tarreau:
I think you summarized very well how to carefully use a development
version in prod. That requires a bit of care, but with that you can
get both nice features and quick fixes.
Indeed :)
After 1.5 is released, I'd like to switch to a faster and more
An official Ubuntu dev repo will also make testing easier.
It's much easier to use a apt-get than building from source and figuring
out command line options.
On Wed, Apr 16, 2014 at 7:05 PM, Philipp
e1c1bac6253dc54a1e89ddc046585...@posteo.net wrote:
Am 16.04.2014 17:40 schrieb Willy Tarreau:
On Wed, Apr 16, 2014 at 07:14:31PM +0300, pablo platt wrote:
An official Ubuntu dev repo will also make testing easier.
It's much easier to use a apt-get than building from source and figuring
out command line options.
I think we're getting close to a release so we should not harrass distro
(Cc'ing the Debian maintainers as well)
Hi all,
On 19:28 Wed 16 Apr , Willy Tarreau wrote:
On Wed, Apr 16, 2014 at 07:14:31PM +0300, pablo platt wrote:
An official Ubuntu dev repo will also make testing easier.
It's much easier to use a apt-get than building from source and figuring
Hi Apollon,
On Wed, Apr 16, 2014 at 09:22:56PM +0300, Apollon Oikonomopoulos wrote:
(Cc'ing the Debian maintainers as well)
Hi all,
On 19:28 Wed 16 Apr , Willy Tarreau wrote:
On Wed, Apr 16, 2014 at 07:14:31PM +0300, pablo platt wrote:
An official Ubuntu dev repo will also make
The Ubuntu PPA is great but it is not 'official' and I couldn't find Ubuntu
14.04 package.
https://launchpad.net/~vbernat/+archive/haproxy-1.5https://launchpad.net/%7Evbernat/+archive/haproxy-1.5
Ubuntu 14.04 LTS will be out tomorrow which means that haproxy-1.5 will be
included only in the next
It's easy to build your own packages with the files from the PPA which
is what we do. BTW, thanks Vincent for doing the groundwork.
Simplest method might be:
- Decide which archs you need to target. Follow a how-to for setting up
a environment to build deb packages. I recommend dedicating a
So I only need to setup a VM, download a file from a personal PPA, add
the source code and learn how to build a deb package...
And every user need to do the same...
Easy :)
On Wed, Apr 16, 2014 at 11:12 PM, Ramin K ramin-l...@badapple.net wrote:
It's easy to build your own packages
Nothing stopping you from using the PPA as originally suggested. :-)
In regards to easy there are hundreds of how-to webpages for building
deb packages. I'd grade it slightly more complicated than building RPMs
correctly. When you're done you can use the same infrastructure to build
I use haproxy on centos. So I build a RPM i then use in spacewalk to
first roll out to test, then post testing to production.
On 16/04/2014 17:14, pablo platt wrote:
An official Ubuntu dev repo will also make testing easier.
It's much easier to use a apt-get than building from source and
Missed the reply-to :)
Originalnachricht
Thanks for the data point, Philipp. If you resend your reply to the
list, that might be useful for people other than just me :-)
J
On 15 April 2014 09:26, Philipp
e1c1bac6253dc54a1e89ddc046585...@posteo.net wrote:
Am 14.04.2014 23:27
Hi,
key is certainly to do some fair amount of testing, don't use a release
with a lot of very recent activity, but let it cool down a few days,
or better, 1 - 3 weeks (and then check fixed bugs 'git log --oneline \
v1.5-devXY..master | grep BUG' to see if anything is relevant for you).
You
Andy Walker schreef op 15/04/14 01:19:
That's pretty close to our method as well. We've been using haproxy
for just over a year, and started with 1.5 because of the built-in SSL
capabilities... specifically, version 1.5-dev17. We actually did a
fairly minimal amount of testing, and just
Hi all -
I've been running 1.4 for a number of years, but am pondering moving
some as-yet-unreleased apps to 1.5, for SSL and ACL-ish reasons.
I'd like to ask how you, 1.5 sysadmins and devs, track the development
version, and how you decide which version to run in production.
Do you just run
On 4/14/2014 2:27 PM, Jonathan Matthews wrote:
Hi all -
I've been running 1.4 for a number of years, but am pondering moving
some as-yet-unreleased apps to 1.5, for SSL and ACL-ish reasons.
I'd like to ask how you, 1.5 sysadmins and devs, track the development
version, and how you decide which
That's pretty close to our method as well. We've been using haproxy for
just over a year, and started with 1.5 because of the built-in SSL
capabilities... specifically, version 1.5-dev17. We actually did a fairly
minimal amount of testing, and just started by moving a low amount of
production
21 matches
Mail list logo
