Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Cyborg)
  • No Skin
Collapse
Brand Logo

CIRCLE WITH A DOT

  1. Home
  2. Uncategorized
  3. I'm back to a three-node #Proxmox cluster.

I'm back to a three-node #Proxmox cluster.

Scheduled Pinned Locked Moved Uncategorized
proxmoxdiynashomelabselfhostedslelfhosting
13 Posts 6 Posters 18 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • yehor@mastodon.glitchy.socialY yehor@mastodon.glitchy.social

    The only thing my #homelab lacks is a shared storage for #Proxmox cluster guest disks, and I still haven't figured out a simple solution for that. Maybe there are none.

    #Ceph is complex and sounds like an overhead.

    For #nfs / #cifs, my network is too slow.

    #HomeServer #Selfhosted #selfhosting #selfHost

    mjturner@indieweb.socialM This user is from outside of this forum
    mjturner@indieweb.socialM This user is from outside of this forum
    mjturner@indieweb.social
    wrote last edited by
    #3

    @yehor Do you need shared storage? #ZFS replication works very well, even with gigabit Ethernet. It can be a little hard on SSDs but even decent consumer drives should be fine (enterprise drives with PLP are first prize though). It's the option I've gone for with my three node ThinkCentre cluster.

    Another option is #MooseFS, which I have heard works well, although you do need to install and manage it outside Proxmox. https://moosefs.com/

    #proxmox

    yehor@mastodon.glitchy.socialY 2 Replies Last reply
    0
    • yehor@mastodon.glitchy.socialY yehor@mastodon.glitchy.social

      The only thing my #homelab lacks is a shared storage for #Proxmox cluster guest disks, and I still haven't figured out a simple solution for that. Maybe there are none.

      #Ceph is complex and sounds like an overhead.

      For #nfs / #cifs, my network is too slow.

      #HomeServer #Selfhosted #selfhosting #selfHost

      V This user is from outside of this forum
      V This user is from outside of this forum
      viper539@social.cologne
      wrote last edited by
      #4

      @yehor regarding "my network is too slow for ceph"...
      My OSD is a 2TB USB Stick and my Network is 1Gbit. It takes nearly a day to rebuild. It saved my ass more than one time. Extend and migrate Storage was never that easy. Ask me in a week how the upgrade to Proxmox 9 was going. ๐Ÿ˜‰

      1 Reply Last reply
      0
      • mjturner@indieweb.socialM mjturner@indieweb.social

        @yehor Do you need shared storage? #ZFS replication works very well, even with gigabit Ethernet. It can be a little hard on SSDs but even decent consumer drives should be fine (enterprise drives with PLP are first prize though). It's the option I've gone for with my three node ThinkCentre cluster.

        Another option is #MooseFS, which I have heard works well, although you do need to install and manage it outside Proxmox. https://moosefs.com/

        #proxmox

        yehor@mastodon.glitchy.socialY This user is from outside of this forum
        yehor@mastodon.glitchy.socialY This user is from outside of this forum
        yehor@mastodon.glitchy.social
        wrote last edited by
        #5

        @mjturner Well, I'm currently using replication, but my concern is that when the node fails, migrated guets could be as old as the replication period. For example, I'm replicating the Matrix instance every 15 minutes. And if the node with the Matrix server fails, HA will migrate the last replicated copy of it. And for the chat server, going back 15 minutes could not be good.

        mjturner@indieweb.socialM 1 Reply Last reply
        0
        • mjturner@indieweb.socialM mjturner@indieweb.social

          @yehor Do you need shared storage? #ZFS replication works very well, even with gigabit Ethernet. It can be a little hard on SSDs but even decent consumer drives should be fine (enterprise drives with PLP are first prize though). It's the option I've gone for with my three node ThinkCentre cluster.

          Another option is #MooseFS, which I have heard works well, although you do need to install and manage it outside Proxmox. https://moosefs.com/

          #proxmox

          yehor@mastodon.glitchy.socialY This user is from outside of this forum
          yehor@mastodon.glitchy.socialY This user is from outside of this forum
          yehor@mastodon.glitchy.social
          wrote last edited by
          #6

          @mjturner MoosFS is interesting, thanks!

          1 Reply Last reply
          0
          • yehor@mastodon.glitchy.socialY yehor@mastodon.glitchy.social

            @mjturner Well, I'm currently using replication, but my concern is that when the node fails, migrated guets could be as old as the replication period. For example, I'm replicating the Matrix instance every 15 minutes. And if the node with the Matrix server fails, HA will migrate the last replicated copy of it. And for the chat server, going back 15 minutes could not be good.

            mjturner@indieweb.socialM This user is from outside of this forum
            mjturner@indieweb.socialM This user is from outside of this forum
            mjturner@indieweb.social
            wrote last edited by
            #7

            @yehor Yes, that is always a concern. I'm still tweaking my setup, but I've seen that some people use very high replication frequencies (eg, 1 minute, even 30s). But even 1 minute lost would be bad for Matrix.

            That said, does Matrix support application-level HA? For example, could you have two instances and fail over from one to the other? In some cases, if the application supports HA that's a better option that doing it via the hypervisor.

            1 Reply Last reply
            0
            • yehor@mastodon.glitchy.socialY yehor@mastodon.glitchy.social

              The only thing my #homelab lacks is a shared storage for #Proxmox cluster guest disks, and I still haven't figured out a simple solution for that. Maybe there are none.

              #Ceph is complex and sounds like an overhead.

              For #nfs / #cifs, my network is too slow.

              #HomeServer #Selfhosted #selfhosting #selfHost

              alex@masto.inkA This user is from outside of this forum
              alex@masto.inkA This user is from outside of this forum
              alex@masto.ink
              wrote last edited by
              #8

              @yehor I use S3 solution in most cases if supported by service ๐ŸŒš

              yehor@mastodon.glitchy.socialY 1 Reply Last reply
              0
              • alex@masto.inkA alex@masto.ink

                @yehor I use S3 solution in most cases if supported by service ๐ŸŒš

                yehor@mastodon.glitchy.socialY This user is from outside of this forum
                yehor@mastodon.glitchy.socialY This user is from outside of this forum
                yehor@mastodon.glitchy.social
                wrote last edited by
                #9

                @alex itโ€™s not for service itself. Itโ€™s for virtual guest machines inside Proxmox cluster for seamless migrations and high availability. S3 is not suitable for this.

                1 Reply Last reply
                0
                • yehor@mastodon.glitchy.socialY yehor@mastodon.glitchy.social

                  The only thing my #homelab lacks is a shared storage for #Proxmox cluster guest disks, and I still haven't figured out a simple solution for that. Maybe there are none.

                  #Ceph is complex and sounds like an overhead.

                  For #nfs / #cifs, my network is too slow.

                  #HomeServer #Selfhosted #selfhosting #selfHost

                  fritzadalis@infosec.exchangeF This user is from outside of this forum
                  fritzadalis@infosec.exchangeF This user is from outside of this forum
                  fritzadalis@infosec.exchange
                  wrote last edited by
                  #10

                  @yehor
                  How slow is your network?

                  yehor@mastodon.glitchy.socialY 1 Reply Last reply
                  0
                  • yehor@mastodon.glitchy.socialY yehor@mastodon.glitchy.social

                    The only thing my #homelab lacks is a shared storage for #Proxmox cluster guest disks, and I still haven't figured out a simple solution for that. Maybe there are none.

                    #Ceph is complex and sounds like an overhead.

                    For #nfs / #cifs, my network is too slow.

                    #HomeServer #Selfhosted #selfhosting #selfHost

                    erikbussink@vmst.ioE This user is from outside of this forum
                    erikbussink@vmst.ioE This user is from outside of this forum
                    erikbussink@vmst.io
                    wrote last edited by
                    #11

                    @yehor How about a #Mikrotik #RDS2216 ?

                    1 Reply Last reply
                    0
                    • fritzadalis@infosec.exchangeF fritzadalis@infosec.exchange

                      @yehor
                      How slow is your network?

                      yehor@mastodon.glitchy.socialY This user is from outside of this forum
                      yehor@mastodon.glitchy.socialY This user is from outside of this forum
                      yehor@mastodon.glitchy.social
                      wrote last edited by
                      #12

                      @FritzAdalis 1 Gbps

                      fritzadalis@infosec.exchangeF 1 Reply Last reply
                      0
                      • yehor@mastodon.glitchy.socialY yehor@mastodon.glitchy.social

                        @FritzAdalis 1 Gbps

                        fritzadalis@infosec.exchangeF This user is from outside of this forum
                        fritzadalis@infosec.exchangeF This user is from outside of this forum
                        fritzadalis@infosec.exchange
                        wrote last edited by
                        #13

                        @yehor
                        That's not all that slow, you may find it's plenty fast enough for disk I/O. If you have spinning disks you're going to need a lot of them to saturate a gig link.

                        1 Reply Last reply
                        1
                        0
                        • R relay@relay.infosec.exchange shared this topic
                        Reply
                        • Reply as topic
                        Log in to reply
                        • Oldest to Newest
                        • Newest to Oldest
                        • Most Votes


                        • Login

                        • Login or register to search.
                        • First post
                          Last post
                        0
                        • Categories
                        • Recent
                        • Tags
                        • Popular
                        • World
                        • Users
                        • Groups