From: duluxoz <duluxoz@gmail.com>
To: Alwin Antreich <alwin@antreich.com>,
Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] Negative VM Groups In Proxmox?
Date: Tue, 27 Aug 2024 14:47:16 +1000 [thread overview]
Message-ID: <ae4efe2a-002d-470d-9e1e-973b7594e90a@gmail.com> (raw)
In-Reply-To: <367e9f538b4019892d17146a63042a312a97d5ec@antreich.com>
Hi All,
Just a follow-up to this thread if anyone else stumbles across it.
So I just stumbled across ProxLB (https://proxlb.de/ and
https://github.com/gyptazy/ProxLB) which does provide the functionality
I was looking for - as well as a whole bunch of other stuff I was also
looking for.
I hope this also helps others
And thanks Alwin :-)
Cheers
Dulux-Oz
On 26/8/24 02:40, Alwin Antreich wrote:
> Hi,
>
> August 25, 2024 at 11:55 AM, "duluxoz" <duluxoz@gmail.com
> <mailto:duluxoz@gmail.com?to=%22duluxoz%22%20%3Cduluxoz%40gmail.com%3E>>
> wrote:
>
> Hi All,
>
>
> As I've said previously, I'm coming over to Proxmox from an oVirt
> Environment.
>
>
> In oVirt there is a concept of a "Negative Group", which is where
> you specify that a certain group of VMs *not* exist/run on the
> same oVirt Node, as opposed to a "Positive Group" where you want
> the grouped VMs to run on the *same* oVirt Node.
>
>
> Positive Groups seem to exist in Proxmox (as per the
> documentation), but I can't see how to create Negative Groups. Is
> this something I've simply missed how to set up, or does this
> functionality not exist in a PVE?
>
> Not that I know of. The issue on the bug tracker [0] touches the same
> corner as your request. It helps to add your feature request on this
> issue as well to give it more visibility. To me this sounds like a
> good feature to have. :)
>
> Cheers,
> Alwin
>
> [0] - https://bugzilla.proxmox.com/show_bug.cgi?id=4699
>
--
PEREGRINE IT Pty Ltd Signature
*Matthew J BLACK*
M.Inf.Tech.(Data Comms)
MBA
B.Sc.
MACS (Snr), CP, IP3P
When you want it done /right/ ‒ the first time!
Phone: +61 4 0411 0089
Email: matthew@peregrineit.net <mailto:matthew@peregrineit.net>
Web: www.peregrineit.net <http://www.peregrineit.net>
View Matthew J BLACK's profile on LinkedIn
<http://au.linkedin.com/in/mjblack>
This Email is intended only for the addressee. Its use is limited to
that intended by the author at the time and it is not to be distributed
without the author’s consent. You must not use or disclose the contents
of this Email, or add the sender’s Email address to any database, list,
or mailing list unless you are expressly authorised to do so. Unless
otherwise stated, PEREGRINE I.T. Pty Ltd accepts no liability for the
contents of this Email except where subsequently confirmed in writing.
The opinions expressed in this Email are those of the author and do not
necessarily represent the views of PEREGRINE I.T. Pty Ltd. This Email is
confidential and may be subject to a claim of legal privilege.
If you have received this Email in error, please notify the author and
delete this message immediately.
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
prev parent reply other threads:[~2024-08-27 4:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-25 9:55 duluxoz
2024-08-25 16:40 ` Alwin Antreich via pve-user
[not found] ` <367e9f538b4019892d17146a63042a312a97d5ec@antreich.com>
2024-08-27 4:47 ` duluxoz [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=ae4efe2a-002d-470d-9e1e-973b7594e90a@gmail.com \
--to=duluxoz@gmail.com \
--cc=alwin@antreich.com \
--cc=matthew@peregrineit.net \
--cc=pve-user@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