Commit 10538acb by Thomas Gambier

Update release candidate

2 parents d2baf849 8251f3dd
Generally things to be done with ``caddy-frontend``:
* README: cleanup the documentation, explain various specifics
* check the whole frontend slave snippet with ``caddy -validate`` during buildout run, and reject if does not pass validation
* (new) ``type:websocket`` slave
* ``type:eventsource``:
* **Jérome Perrin**: *For event source, if I understand https://github.com/mholt/caddy/issues/1355 correctly, we could use caddy as a proxy in front of nginx-push-stream . If we have a "central shared" caddy instance, can it handle keeping connections opens for many clients ?*
* ``check-error-on-caddy-log`` like ``check-error-on-apache-log``
* move out ``test/utils.py`` and use it from shared python distribution
* reduce the time of configuration validation (in ``instance-apache-frontend.cfg.in`` sections ``[configtest]``, ``[caddy-configuration]``), as it is not scalable on frontend with 2000+ slaves (takes few minutes instead of few, < 5, seconds), issue posted `upstream <https://github.com/mholt/caddy/issues/2220>`_
* drop ``6tunnel`` and use ``bind`` in Caddy configuration, as soon as multiple binds will be possible, tracked in upstream `bind: support multiple values <https://github.com/mholt/caddy/pull/2128>`_ and `ipv6: does not bind on ipv4 and ipv6 for sites that resolve to both <https://github.com/mholt/caddy/issues/864>`_
* use caddy-frontend in `standalone style playbooks <https://lab.nexedi.com/nexedi/slapos.package/tree/master/playbook/roles/standalone-shared>`_
* in ``templates/apache-custom-slave-list.cfg.in`` avoid repetetive ``part_list.append`` and use macro like in ERP5 SR (cf `Vincent's comment <https://lab.nexedi.com/nexedi/slapos/merge_requests/373#note_64362>`_)
* **Jérome Perrin**: consider privacy implications/GDPR compliance of https://caddyserver.com/docs/telemetry and decide if we should leave it enabled.
......@@ -159,10 +159,6 @@ zodburi = 2.3.0
ZEO = 4.3.1+SlapOSPatched001
# Required by:
# zodburi==2.0
mock = 2.0.0
# Required by:
# ZEO==4.3.1
zdaemon = 4.2.0
......
......@@ -473,6 +473,7 @@ eggs = ${neoppod:eggs}
Jinja2
jsonschema
mechanize
mock
objgraph
paramiko
ply
......@@ -482,6 +483,7 @@ eggs = ${neoppod:eggs}
python-memcached
pytz
requests
responses
threadframe
timerserver
urlnorm
......@@ -801,3 +803,15 @@ unidiff = 0.5.5
# deepdiff = 3.3.0
jsonpickle = 0.9.6
decorator = 4.3.0
mock = 3.0.4
# Required by:
# mock = 3.0.4
funcsigs = 1.0.2
responses = 0.10.6
# Required by:
# responses = 0.10.6
cookies = 2.2.1
......@@ -42,7 +42,7 @@ md5sum = d32417746fcf671d4e86a70379815039
[template-my-cnf]
filename = my.cnf.in
md5sum = 2e381fb10a7c024c99caa434036173c6
md5sum = af2113bbdeaf32096c4013fa73b45ced
[template-mariadb-initial-setup]
filename = mariadb_initial_setup.sql.in
......
......@@ -29,7 +29,7 @@ max_allowed_packet = 128M
query_cache_size = 32M
innodb_file_per_table = 0
plugin_load = ha_mroonga.so;handlersocket.so
plugin_load = ha_mroonga
# By default only 100 connections are allowed, when using zeo
# we may have much more connections
......
......@@ -135,7 +135,7 @@ pytz = 2016.10
requests = 2.13.0
six = 1.11.0
slapos.cookbook = 1.0.92
slapos.core = 1.4.22
slapos.core = 1.4.23
slapos.extension.strip = 0.4
slapos.extension.shared = 1.0
slapos.libnetworkcache = 0.16
......@@ -150,7 +150,7 @@ xml-marshaller = 0.9.7
paramiko = 2.1.3
# Required by:
# slapos.core==1.4.22
# slapos.core==1.4.23
Flask = 0.12
# Required by:
......@@ -222,7 +222,7 @@ jsonschema = 3.0.0a3
lockfile = 0.12.2
# Required by:
# slapos.core==1.4.22
# slapos.core==1.4.23
# XXX 'slapos node format' raises an exception with netifaces 0.10.5.
netifaces = 0.10.4
......@@ -255,7 +255,7 @@ python-dateutil = 2.7.3
rpdb = 0.1.5
# Required by:
# slapos.core==1.4.22
# slapos.core==1.4.23
supervisor = 3.3.3
# Required by:
......@@ -263,11 +263,11 @@ supervisor = 3.3.3
tzlocal = 1.5.1
# Required by:
# slapos.core==1.4.22
# slapos.core==1.4.23
uritemplate = 3.0.0
# Required by:
# slapos.core==1.4.22
# slapos.core==1.4.23
zope.interface = 4.3.3
[networkcache]
......
Styling with Markdown is supported
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!