| 2018-05-12 19:20:45 |
james beedy |
bug |
|
|
added bug |
| 2018-05-12 19:42:07 |
james beedy |
summary |
haproxy should wait to write out a front end and backend until they are configured by relating service |
haproxy should wait to write out a front end and backend until they are configured by relating service OR allow configuration of the default haproxy_service |
|
| 2018-05-12 19:43:23 |
james beedy |
summary |
haproxy should wait to write out a front end and backend until they are configured by relating service OR allow configuration of the default haproxy_service |
haproxy should wait to write out a front end and backend until they are configured by relating service OR allow configuration of the default frontend/backend |
|
| 2018-05-12 19:44:27 |
james beedy |
description |
Haproxy writes out a default front end and backend that binds to port 80.
This is a blocker for charms that want to specify custom service relations to haproxy that bind to port 80.
Can we not write out a frontend/backend just for the heck of it, and wait until relations specify what they want to bind to?\
thanks |
Haproxy writes out a default front end and backend that binds to port 80.
This is a blocker for charms that want to specify custom service relations to haproxy that bind to port 80.
Can we not write out a frontend/backend just for the heck of it, and wait until relations specify what they want to bind to?
OR
Allow configuration of the default frontend/backend? |
|
| 2018-05-14 01:48:03 |
james beedy |
description |
Haproxy writes out a default front end and backend that binds to port 80.
This is a blocker for charms that want to specify custom service relations to haproxy that bind to port 80.
Can we not write out a frontend/backend just for the heck of it, and wait until relations specify what they want to bind to?
OR
Allow configuration of the default frontend/backend? |
The haproxy charm writes out a default front end and backend that bind to port 80.
This is a blocker for charms that want to specify custom service relations to haproxy that bind to port 80.
Can we not write out a frontend/backend just for the heck of it, and wait until relations specify what they want to bind to?
OR
Allow configuration of the default frontend/backend? |
|
| 2019-06-06 11:44:40 |
Junien F |
charm-haproxy: status |
New |
Triaged |
|
| 2019-06-06 11:44:44 |
Junien F |
charm-haproxy: importance |
Undecided |
Medium |
|
