[vdsm] policycoreutils - karma needed

2013-02-10 Thread Douglas Landgraf

Hello,

On F17, there is a bug [1] affecting the installation of VDSM, we cannot 
modify the selinux booleans.


The new policycoreutils package under testing repository resolves the 
problem. To promote it to a updates repo, we need 3 positive karmas [2] 
of tests, if you can help testing, please follow:

https://bugzilla.redhat.com/show_bug.cgi?id=908773#c3

[1] https://bugzilla.redhat.com/show_bug.cgi?id=908773
[2] http://fedoraproject.org/wiki/Bodhi#Karma

Thanks!

--
Cheers
Douglas
___
vdsm-devel mailing list
vdsm-devel@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel


Re: [vdsm] vdsm networking changes proposal

2013-02-10 Thread 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
 a...@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/arch
 
___
vdsm-devel mailing list
vdsm-devel@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel