From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>, Graeme Seaton <lists@graemes.com>
Subject: Re: [pbs-devel] Templates starting on backup
Date: Mon, 5 Oct 2020 16:40:18 +0200 [thread overview]
Message-ID: <fa4f0c2b-fbbc-3b76-6dae-8b9a956d0ff1@proxmox.com> (raw)
In-Reply-To: <5e238f85-d7b0-4cef-13d8-aa2e6012a61e@graemes.com>
On 05.10.20 16:21, Graeme Seaton wrote:
> On 05/10/2020 14:42, Thomas Lamprecht wrote:
>> What HW differences are talking here?
>
> In one case CPU type/Numa/hugepages. In others vmbr's.
Why not just leave it at the "OK" hosts, if you're using HA you could
add it to a group restricted to those hosts it is compatible with.
We may reduce the configuration of a template started fort backup a bit,
though.
cheers,
Thomas
next prev parent reply other threads:[~2020-10-05 14:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-05 12:15 Graeme Seaton
2020-10-05 13:42 ` Thomas Lamprecht
2020-10-05 14:21 ` Graeme Seaton
2020-10-05 14:40 ` Thomas Lamprecht [this message]
2020-10-05 16:49 ` Graeme Seaton
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=fa4f0c2b-fbbc-3b76-6dae-8b9a956d0ff1@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=lists@graemes.com \
--cc=pbs-devel@lists.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