1.
The vswitch calss used vswitch::params::provider to determine which class should be included but we don't have vswitch::ovs_redhat so this class does NEVER work in CentOS/RHEL.
(This is an independent problem, though)
2.
Currently we have multiple provider implementations for vs_port but these implementations are NEVER automatically selected but the first one(ovs.rb) is always used. That's why Alfredo experienced that ovs provider was used.
We need to add a new option to that ovs_port type to switch provider.
(I'm still looking for the way to implement this properly)
So what we need here is to fix 2 and add a new provider implementation relying on network manager...
So... I think there are many problems now...
1. :params: :provider to determine which class should be included but we don't have vswitch::ovs_redhat so this class does NEVER work in CentOS/RHEL.
The vswitch calss used vswitch:
(This is an independent problem, though)
2.
Currently we have multiple provider implementations for vs_port but these implementations are NEVER automatically selected but the first one(ovs.rb) is always used. That's why Alfredo experienced that ovs provider was used.
We need to add a new option to that ovs_port type to switch provider.
(I'm still looking for the way to implement this properly)
So what we need here is to fix 2 and add a new provider implementation relying on network manager...