~tcuthbert/content-cache-charm:master

Branch merges

Propose for merging

Merged into content-cache-charm:master at revision 26a477fb2a192bc5685a9ec1d785c05b7ac731d6

Haw Loeung: Approve (+1) on 2021-02-01

Canonical IS Reviewers: Pending requested 2021-02-01

Diff: 13 lines (+1/-1)

1 file modified

reactive/content_cache.py (+1/-1)

api

Merged into content-cache-charm:master at revision 3ecd7146c13d23cbf38b4911a50a207baef2f652

Haw Loeung: Approve (+1) on 2021-01-28

Canonical IS Reviewers: Pending requested 2021-01-28

Diff: 12 lines (+1/-0)

1 file modified

reactive/content_cache.py (+1/-0)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related charm recipes

50a9262... by Thomas Cuthbert on 2021-02-01

Telegraf expects 'listener-address' rel key name

3ecd714... by Thomas Cuthbert on 2021-01-28

content-cache uses localhost for stats monitoring, tell telegraf that

Reviewed-on: https://code.launchpad.net/~tcuthbert/content-cache-charm/+git/content-cache-charm/+merge/396233
Reviewed-by: Haw Loeung <email address hidden>

6df5608... by Haw Loeung on 2021-01-27

Allow overriding Nginx' proxy_cache_lock

Reviewed-on: https://code.launchpad.net/~hloeung/content-cache-charm/+git/content-cache-charm/+merge/396969
Reviewed-by: Barry Price <email address hidden>

a0b35db... by Haw Loeung on 2021-01-27

Remove no-cache in HAProxy health checks

Reviewed-on: https://code.launchpad.net/~hloeung/content-cache-charm/+git/content-cache-charm/+merge/396968
Reviewed-by: Barry Price <email address hidden>

c2df82e... by Haw Loeung on 2021-01-27

Allow overriding Nginx' proxy_cache_lock

For large objects, it makes sense to enable so only one worker /
instance is fetching from the backend and populating the cache. It
doesn't make sense for sites serving just smaller objects as it can
introduce latency.

1d3bc17... by Haw Loeung on 2021-01-27

Remove no-cache in HAProxy health checks

There's no need to do a full end-to-check check, which is what will be
done with no-cache. Rather, we just want to check each layer, or the
next layer HAProxy is configured for.

This is helpful for when backends are experiencing issues, we still
want the caching layer to respond with something from the cache.

3774c25... by Haw Loeung on 2021-01-21

Fix indentation so it's consistent

Reviewed-on: https://code.launchpad.net/~hloeung/content-cache-charm/+git/content-cache-charm/+merge/396636
Reviewed-by: Barry Price <email address hidden>

51c5baf... by Haw Loeung on 2021-01-21

Fixed, go with spaces rather than tab per review

e17761a... by Haw Loeung on 2021-01-21

Also log unique request ID in HAProxy logs - LP:1895255

Reviewed-on: https://code.launchpad.net/~hloeung/content-cache-charm/+git/content-cache-charm/+merge/396635
Reviewed-by: Barry Price <email address hidden>

1194dd5... by Haw Loeung on 2021-01-21

Fix indentation so it's consistent