public inbox for pve-user@lists.proxmox.com
 help / color / mirror / Atom feed
* Re: [PVE-User] 2 node cluster
       [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
  0 siblings, 1 reply; 2+ messages in thread
From: Ivan Dimitrov @ 2020-09-15 10:50 UTC (permalink / raw)
  To: Proxmox VE user list; +Cc: PVE User List, tinfoil-hat

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
>


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [PVE-User] 2 node cluster
  2020-09-15 10:50 ` [PVE-User] 2 node cluster Ivan Dimitrov
@ 2020-09-16 18:48   ` Rutger Verhoeven
  0 siblings, 0 replies; 2+ messages in thread
From: Rutger Verhoeven @ 2020-09-16 18:48 UTC (permalink / raw)
  To: Proxmox VE user list

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
>
>


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2020-09-16 18:49 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <mailman.347.1598805038.464.pve-user@lists.proxmox.com>
2020-09-15 10:50 ` [PVE-User] 2 node cluster Ivan Dimitrov
2020-09-16 18:48   ` Rutger Verhoeven

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal