From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>,
Wolfgang Bumiller <w.bumiller@proxmox.com>
Subject: [pbs-devel] applied-series: [PATCH backup 0/7] hot-reload proxy certificates
Date: Tue, 11 May 2021 18:11:55 +0200 [thread overview]
Message-ID: <f2b29115-7363-efc0-bd27-642d437f227a@proxmox.com> (raw)
In-Reply-To: <20210511135400.32406-1-w.bumiller@proxmox.com>
On 11.05.21 15:53, Wolfgang Bumiller wrote:
> This adds the ability to tell a running proxy to just reload the TLS
> cert certificates via the command-socket.
>
> Starts off with some cleanup/refactoring to get rid of all that heavy
> indentation...
>
> Wolfgang Bumiller (7):
> proxy: factor out accept_connection
> proxy: "continue on error" for the accept call, too
> proxy: Arc usage cleanup
> proxy: factor out tls acceptor creation
> proxy: implement 'reload-certificate' command
> refactor send_command
> hot-reload proxy certificate when updating via the API
>
> src/api2/node/certificates.rs | 26 ++--
> src/bin/proxmox-backup-proxy.rs | 220 ++++++++++++++++++++------------
> src/config.rs | 17 +--
> src/server.rs | 9 ++
> src/server/command_socket.rs | 71 ++++++-----
> src/server/worker_task.rs | 4 +-
> 6 files changed, 204 insertions(+), 143 deletions(-)
>
applied whole series, thanks!
I followed this up with:
* fallback to "default" account on order (check commit message, was really confusing else)
* add UI task-description entries for acme related tasks, mostly based on the ones from
PVE, but as the worker type is spelled slightly different anyway here I took the chance
to use a slightly nicer version there too.
* set account name as worker ID so that they can be used in by the task-descriptions
- note: all account actions done before that commit miss it and will display "default",
even if the account was named something else, I ignored this as we did not really
rolled this out externally yet.
prev parent reply other threads:[~2021-05-11 16:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-11 13:53 [pbs-devel] " Wolfgang Bumiller
2021-05-11 13:53 ` [pbs-devel] [PATCH backup 1/7] proxy: factor out accept_connection Wolfgang Bumiller
2021-05-11 13:53 ` [pbs-devel] [PATCH backup 2/7] proxy: "continue on error" for the accept call, too Wolfgang Bumiller
2021-05-11 13:53 ` [pbs-devel] [PATCH backup 3/7] proxy: Arc usage cleanup Wolfgang Bumiller
2021-05-11 13:53 ` [pbs-devel] [PATCH backup 4/7] proxy: factor out tls acceptor creation Wolfgang Bumiller
2021-05-11 13:53 ` [pbs-devel] [PATCH backup 5/7] proxy: implement 'reload-certificate' command Wolfgang Bumiller
2021-05-11 13:53 ` [pbs-devel] [PATCH backup 6/7] refactor send_command Wolfgang Bumiller
2021-05-11 13:54 ` [pbs-devel] [PATCH backup 7/7] hot-reload proxy certificate when updating via the API Wolfgang Bumiller
2021-05-11 16:11 ` Thomas Lamprecht [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f2b29115-7363-efc0-bd27-642d437f227a@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
--cc=w.bumiller@proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox