Public bug reported:
Binary package hint: haproxy
Availability:
Package has been in universe since Hardy.
Rationale:
* HAProxy is considered to be one of the best app level load balancers
available.
* MIR is marked as a requirement for maverick alpha2 in
https://blueprints.launchpad.net/ubuntu/+spec/server-maverick-uds-cloud-loadbalancing
Security:
* No CVE's or vulnerabilities listed in the usual place. Further searches turn
up no previous security problems.
* Disabled by default, must be enabled by editing /etc/default/haproxy.
* The ports opened in the default configuration are 10001 thru 10005, and
8443. On connecting to those ports, these attempt to connect to non-routable
IP's of backend servers that may or may not exist, so this config file may need
to be moved to an examples directory.
Quality assurance:
* There are no important bug reports against haproxy in Debian or Ubuntu
* The debian package has been well maintained and has stayed quite close to
upstream.
UI standards: (generally only for user-facing applications)
N/A
Dependencies:
* All are in main.
Standards compliance:
* Packaging is very straight forward and package appears to comply with
policy upon cursory examination.
Maintenance:
* Package produces a single binary package, that includes a single
binary, a daemon that uses a single config file.
Background information:
HAProxy is quite mature, as is its debian package.
** Affects: haproxy (Ubuntu)
Importance: Undecided
Status: New
--
[MIR] haproxy
https://bugs.launchpad.net/bugs/591006
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
