Recent content by Astraea

I am unsure if it would work with an SDN setup but I have used OVS and OVSIntPorts to create IP addresses for the Proxmox host on various VLANS though the VLAN tag is specified in the IntPort. I did try using SDN but because my primary VLAN is not tagged it would not work for me unless I redid...

My current practice is to set any VMs i will jeep running during maintenance to "ignored" in the HA manager and then I stop any VMs that will not be kept running. I then put all the nodes into maintenance mode and then I manually move the running VMs as needed while completing any maintenance...

As of Proxmox 8.3.1 it will show which nodes are in maintenance mode on the UI however you still need to use the CMD line to move them in and out of maintenance mode.

I would also like to see the ability to use both tagged and untagged VLANs with the SDN as well as the expansion of the DHCP system not just simple networks.

You would need 5 servers to handle a 2 server failure.

I was able to update the system that I held packages on and now Proxmox is running the latest/fixed version from the no subscription repo.

Just tried the first half on one of my non important machines to test while I leave my production machines for a fix. It worked without any issues. I'll report back on the second half once the issues have been fixed.

I have been testing/using native zfs encryption on my root pool on a single node install and is has been working flawlessly. Though I did not setup remote unlock on this install as it is a laptop with a DE also installed so I have a built in keyboard, mouse and monitor for unlocking the boot...

Have you looked into something like Veracrypt, I have not used it for a network share before but have used it before on external SSDs

I run 2 Ceph clusters in my home environment and while not setup both hardware and network wise to production standards, does meet my needs. My first cluster is 7 nodes with 2 1Gb links and 2 SSD OSDs per node. It won't win any speed contests but it offers simular performance from either...

Also once you have your repositories setup for the no subscription repository. Remember don't use "apt upgrade" use "apt dist-upgrade" instead.

The traffic is split out on various physical and virtual networks.

After reading the issues with network interfaces changing on the upgrade to 8.2 I went through the 7 nodes I upgraded yesterday and used the instructions HERE to override the device names to eth# and each name is associated to the interface's MAC address which is a consistent value. It also...

I have VMs that connect to mutiple VLANs and I have a single bridge that they all connect to and if I do not specify a VLAN on the VMs interface they get the untagged VLAN for that bridge and if I specify one on the interface they then used the tagged VLAN. For each VM that needs to be connected...

I just finished the first batch of updates and had no issues on any of the systems I updated. With the possible issue around interface renaming, I did do the assign network naming changes that have been mentioned before and rebooted after applying those changes before doing the update. So far...