From: Rutger Verhoeven <rutger.verhoeven@gmail.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] 2 node cluster
Date: Wed, 16 Sep 2020 20:48:51 +0200 [thread overview]
Message-ID: <CAOekgU43RYfAproJKr23UZmr6ioHS5Yi40VHU769JLDjEQ0LmA@mail.gmail.com> (raw)
In-Reply-To: <CACPKT4VHi+s9-O+Mhyzi3_OgcgyFC0S8YqMouTJHOm4+i4aCAA@mail.gmail.com>
Thnx for this explanation!
On Tue, Sep 15, 2020, 12:51 Ivan Dimitrov <hipantcii@gmail.com> wrote:
> Hi,
>
> It is possible but not recommended ;)
> Option 1 is to use a Raspberry Pi or something similar to create a 3-rd
> node in the cluster.
> Option 2 I have the same setup and requirements as you so here is what I am
> doing - assign the "master" node 2 votes and expect a total of 3. In this
> case you always have quorum.
> You can do this by:
> - follow the guidelines in ProxMox wiki how to edit the corosync
> configuration (stop the services, etc.)
> - edit the configuration
> - bump the configuration version
> - restart the services
>
> Of course this is not supported and you should be careful with the VM ids
> on both nodes but for homelab it works perfectly.
>
> With Best Regards,
> Ivan Dimitrov
>
>
> On Sun, 30 Aug 2020 at 18:30, tinfoil-hat via pve-user <
> pve-user@lists.proxmox.com> wrote:
>
> >
> >
> >
> > ---------- Forwarded message ----------
> > From: tinfoil-hat <list-sub@tinfoil-hat.net>
> > To: pve-user@pve.proxmox.com
> > Cc:
> > Bcc:
> > Date: Sun, 30 Aug 2020 18:24:58 +0200
> > Subject: 2 node cluster
> > Hi Folks,
> >
> > I wanted to ask if it's possible and a proper solution to create a 2 node
> > cluster with one noede powered off and just use as fallback when the
> other
> > node needs maintainance. It's just a small home environment, but I plan
> to
> > deploy a pfsense solution and a local dns / dhcp ldap and monitoring. So
> I
> > wouldn't be able to access the Internet when I need to maintain the main
> > host. So I tought, I cramp up an old desktop pc which will serve as
> > fallback, that gets powered on, when I need to migrate my virtualised
> > infrastructure. I am open to alternative suggestions. I would like to do
> it
> > to teach myself in compsci, and I figured the best way was to adopt my
> > homenetwork. I don't have other persons relying on the network, so I
> would
> > just need to eat my own brewn soup.
> >
> >
> >
> > ---------- Forwarded message ----------
> > From: tinfoil-hat via pve-user <pve-user@lists.proxmox.com>
> > To: pve-user@pve.proxmox.com
> > Cc: tinfoil-hat <list-sub@tinfoil-hat.net>
> > Bcc:
> > Date: Sun, 30 Aug 2020 18:24:58 +0200
> > Subject: [PVE-User] 2 node cluster
> > _______________________________________________
> > pve-user mailing list
> > pve-user@lists.proxmox.com
> > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
> >
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
>
prev parent reply other threads:[~2020-09-16 18:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.347.1598805038.464.pve-user@lists.proxmox.com>
2020-09-15 10:50 ` Ivan Dimitrov
2020-09-16 18:48 ` Rutger Verhoeven [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=CAOekgU43RYfAproJKr23UZmr6ioHS5Yi40VHU769JLDjEQ0LmA@mail.gmail.com \
--to=rutger.verhoeven@gmail.com \
--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