Search results

Ah that works yes! Thanks @d.oishi! I still feel it would also be logical to simply add a network bridge (a resource, much like a storage) to a resource pool, to make it available inside a pool. Anyway: this works, thanks again!

ah right?! I did not know that... I will try and report back!

We're not using the SDN framework, but the 'old style' the bridges, but thanks for the suggestion, both!

Hi, Wondering about resource pools, and resource separation. In our PoC, I created some test resource pools, added users, VMs and some storages to them. Now, when creating a new VM (as a resource pool member) I see correctly the available storages, but in the last step, I do not see any of the...

Hi Stefan, Thanks for the quick follow-up! Looking at your requested output qm config 3346, I noticed it myself: firewall=1 was missing for the net0 device. After turning it on, the firewall started behaving as expected! Apologies and thanks!

Note: input policy is set to DROP, on both the DC and the VM level. I have now even created an explicit VM-level DROP-rule for port tcp/5403, and the behaviour has not changed. It seems the firewall rules don't apply for VMs in the same subnet as the pve nodes? (IN DROP -source...

Hi, Trying to understand something. I created a VM for Qdevice , in the same /24 as my proxmox hypervisors: pve1: 192.168.33.44 pve2: 192.168.33.45 qdevice: 192.168.33.46 I understand from the docs that firewalling on the VM level should still apply, and I have only allowed specific (ssh...

Looking for the same...

Yeah, we reverted now to doing that as well. But vmbr names are now nice and descriptive, and bonds are just numbered. It would be nice to eliminate that restriction.

Great! I really hope the limitation will also be lifted for bridges! Thanks for the quick help! :-)

Thanks for checking and confirming back. Ok, that's a pity, we would have liked to use meaningful names, including a VLAN identifier. We will have to use the comment field instead. Does the same limitation apply to vmbr? I notice those DO get recognised as bridges in the pve GUI.

Yeah I added the bonds manually, not through the GUI. then later I edited something network through the GUI, and then all bond definitions were rewritten. (and broken, so after a reboot, the complete system was unreachable)

Hi, To our surprise we see that proxmox rewrites (parts of) the network/interfaces file from this working version: auto MNGT_bond0 iface MNGT_bond0 inet manual bond-miimon 100 bond-mode 802.3ad bond-xmit-hash-policy layer3+4 bond-slaves nic3 bond-lacp-rate fast to this...

Thanks, I will.

Thanks for all valuable input provided. Much appreciated.

Thanks for the replies, mir and bbgeek17, appreciated. The intention (specially for this upcoming PoC) is to use what we already have in place, so we're not going to buy anything, and need no support. If we go PRD, specially the support part will of course change. I will checkout regular LVM on...

Hi all, As many, we are also contemplating a move from broadcom/vmware to proxmox, and are starting with a PoC now. I ran proxmox in the past with ceph cluster, so I know how great that combination it, but ceph is (now) not going to happen where I work, so: no ceph. At the institute we have a...

Hi, We have a 5-node cluster, 1.2.3.192 - 1.2.3.196, using a 10G direct fibre connection between the five (called dev hsl) and the following /etc/network/interfaces on host pve3: root@pve3:/etc/network# cat interfaces # network interface settings; autogenerated # Please do NOT modify this...

Hi Gilou, Thanks for your response. Appreciated. It's "full mesh" for the first three of the five nodes, and the remaining two are not participating in the full mesh ceph replication, have no OSD's, but are in the same /24 ip range, and in the same pve cluster. They would have access to the...

Hi, We’ve reviewed the relevant wiki articles, and we’re looking for feedback on a networking strategy for our Proxmox and Ceph cluster setup. Specifically, we aim to avoid using multiple arbitrary IPs and would prefer to use a single /24 network for all traffic, including Ceph cluster traffic...