Search results

Attaching files...

Well, a pseudo UUID would work also ;). my suggestion would be just to autogenerate the ID, I don't see a use case to define the pattern by the user. I'm just thinking about how to make it less possible to clash ("XX VNI is already used" or "VNET ID already used"). ID shouldn't be used as...

Given IDs are global, wouldn't make more sense to generate automatically an UUID for the VNET?, "inviting" the user to populate Alias parameter with what makes sense descriptively to the user?. Also, given VNIs are global, should de interface autogenerate one as proposal?, and the user would be...

I've tried this between two test nodes (not part of a cluster) and VXLAN, the traffic seems to pass through, but ping tests reports duplicated answers: Any hints?

Thanks @spirit for you work on the "Software Defined Network" module. On the current proposed plugin I would suggest: - At least for the VXLAN part, autogenerating internal IDs for the zones and networks, and adding a "friendly" name only visible to the tenant/user that has access to them...

Any update on this topic?

Never mind :)

I don't think that's a good thing. Client might start whining about "overloaded hosts" or some other ghosts

Hi!, anybody managed to achieve some kind of administrative delegation where a user can manage a subset of resources, access VM console and start/stop some the same VM ?. I've been looking around but the usual tools (ovirt, openqrm, cloudstack, opennebula, etc) don't seem to integrate with Proxmox.

Can ZFS be used in shared block device scenarios (cluster sharing a LUN)?

Anyone can comment if there's an option to install PVE on a multipath device ?

Hi!, is there any special option to use boot from SAN with PVE3?. I tried to install it on a LUN and it worked, but multipath was not used by the installer, only one path was chosen as boot disk.

Hi!, sorry for the delay. I had to split the bond and used vmbr0 and vmbr1 associated to each bond in order to go live. I posted the final configuration after making the changes, sorry about that. Currently I can't test that configuration again. It works but won't be able to use all the...

yup, I chose to name the management interface as br0, and the VM traffic bridge vmbr0

For the time being, had to split the bond and separate management traffic on a access mode port. The traffic works if I don't mix management with VMs bridge+trunking. This is the VM configuration:

Error: Configuration: Version:

Hi, I'm running PVE 3.0 and the VLAN creation fails at VM boot complaining that it already exists. I check before it's start and it doesn't exists, but after failed start the vlan is there!, so it seems to try to create it two times, anybody has seen this? eth0 \ eth1 -- bond0 -- vmbr0 eth2...