Description of problem: Support for private virtual local area networks (PVLAN) allowing to 'sub-partition' a VLAN by restricting switch ports to only communicate with a given 'uplink' - avoiding 'per-to per' communication (extension to the VLAN standard). Private VLAN works when assigning IP to interface directly on RHEL KVM hypervisor server...but when creating a bridge using same interface and assign network to VM..it does not work.
RFE: Red Hat Virtualization Manager Administration portal Existing: Navigate to any network N under a datacenter. Open the associated vNIC profile. The 'Network Filter' shows a drop down list of only the built-in network filters. Requirement: A way to create a new network filter and associate it with a vNIC profile from the administration portal.
(In reply to fnanushr from comment #18) > RFE: > > A way to create a new network filter and associate it with a vNIC profile > from the administration portal. bug 1544666 is all about letting Engine select a non-built-in nwfilter, that is already deployed to all hosts. Here you request a way to deploy nwfilter to all hosts, which I believe is better done by Ansible, possibly triggered by ovirt-host-deploy. If you think differently, please file an independent RFE.
We will look to add the network filter into libvirt and gateway option in RHV to enable this use case.
We agreed to remove RFEs component from Bugzilla, if you feel the component has been renamed incorrectly please reach out.
Upstream patch is going well and we will ask to add the filter to a coming RHEL release.
Please add to cluster level 4.2, too. We can add a release note that only folks with el7.6 can actually opt in and choose this new filter.
Verified on - 4.3.0-0.0.master.20180902070649.gita860c9c.el7 vdsm-4.30.0-554.git4594d97.el7.x86_64 kernel 3.10.0-940.el7.x86_64 Red Hat Enterprise Linux Server release 7.6 Beta (Maipo) libvirt-4.5.0-7.el7.x86_64 libvirt-daemon-4.5.0-7.el7.x86_64 rhel 7.5 guests(VMs) For test flow see BZ 1610979#26
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2019:1085