vdsm networking changes proposal

[Mike Kolesnik]

Hi Antoni,

Regarding 'Bond' how is it logical to have VLANs as slaves?
Is it something we would like to support, or just be able to represent, if we ever come across this odd combination?

Also, can bond slaves have ipConfig set?

Regarding 'VLAN' is it possible to have the VLAN over bridge as you written?
I'm not sure if that's something supported currently, but is there a plan to support this mode?

Generally seems like these entities have a lot in common that can be in a common 'interface' entity.

Also for OVS I don't understand if the current model will be extensible to support for example GRE tunnels, which aren't necessarily supported in other configurers.

Regards,
Mike

----- Original Message -----
> Hi fellow oVirters!
> 
> The network team and a few others have toyed in the past with several
> important
> changes like using open vSwitch, talking D-BUS to NM, making the
> network
> non-persistent, etc.
> 
> It is with some of this changes in mind that we (special thanks go to
> Livnat
> Peer, Dan Kenigsberg and Igor Lvovsky) have worked in a proposal for
> a new architecture for vdsm's networking part. This proposal is
> intended to
> make our software more adaptable to new components and use cases,
> eliminate
> distro dependancies as much as possible and improve the
> responsiveness and
> scalability of the networking operations.
> 
> To do so, it proposes an object oriented representation of the
> different
> elements that come into play in our networking use cases.
> 
> But enough of introduction, please go to the feature page that we
> have put
> together and help us with your feedback, questions proposals and
> extensions.
> 
> http://www.ovirt.org/Feature/NetworkReloaded
> 
> 
> Best regards,
> 
> Toni
> _______________________________________________
> Arch mailing list
> Arch at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/arch
>