Hi all,
I go on with my wishlist, derived from both solitary mumblings and community 
talks at the the first Italian oVirt Meetup.

I offer to help in coding (work/family schedules permitting) but keep in mind 
that I'm a sysadmin with mainly C and bash-scripting skills (but hoping to 
improve my less-than-newbie Python too...)

I've sent separate wishlist messages for oVirt Node and Engine.

VDSM:

*) allow VDSM to configure/manage Samba, CTDB and Ganesha (specifically, I'm 
thinking of the GlusterFS integration); there are related wishlist items on 
configuring/managing Samba/CTDB/Ganesha on the Engine and on oVirt Node

*) add Open vSwitch direct support (not Neutron-mediated); there are related 
wishlist items on configuring/managing Open vSwitch on oVirt Node and on the 
Engine

*) add DRBD9 as a supported Storage Domain type; there are related wishlist 
items on configuring/managing DRBD9 on the Engine and on oVirt Node

*) allow VDSM to configure/manage containers (maybe extend it by use of the LXC 
libvirt driver, similarly to the experimental work that has been put up to 
allow Xen vm management); there are related wishlist items on 
configuring/managing containers on the Engine and on oVirt Node

*) add a VDSM_remote mode (for lack of a better name, but mainly inspired by 
pacemaker_remote) to be used inside a guest by the above mentioned container 
support (giving to the Engine the required visibility on the managed 
containers, but excluding the "virtual node" from power management and other 
unsuitable actions)

Regards,
Giuseppe

_______________________________________________
Users mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/users

Reply via email to