[node-devel] oVirt Node feature requests for 3.1 release

[Livnat Peer]

On 08/21/2013 09:41 AM, Bohai (ricky) wrote:
> 
>> -----Original Message-----
>> From: node-devel-bounces at ovirt.org [mailto:node-devel-bounces at ovirt.org]
>> On Behalf Of Mike Burns
>> Sent: Tuesday, August 20, 2013 10:26 PM
>> To: node-devel; arch
>> Subject: [node-devel] oVirt Node feature requests for 3.1 release
>>
>> Hi all,
>>
>> We're going into our initial planning cycle for oVirt Node 3.1 and are
>> looking for features that are interesting to people.  There are a number
>> of ideas that were proposed on our weekly meeting that are listed below.
>>   If you would really like to see one or more of the features below,
>> please let us know.  If you have an idea for another feature, please
>> also reply with a short abstract for that feature.
>>
>> Thanks
>>
>> Mike
>>
>> * Package Refactoring -- make it easier to build custom images for
>> different use cases without pulling in unnecessary functionality (I.E.,
>> virt capabilities when acting as a storage node only).
>> * re-writes of the storage and installer modules for easier testing
> +1
> 
>> * openvswitch support
> +1

+1

In addition we added in oVirt 3.3 integration with Neutron that is
currently only available on RHEL/fedora based nodes.
It would be great if we can look into what are the requirements to
support it on oVirt node as well.

> 
>> * live install of plugins (install on a running system, possibly with
>> push model)
>> * Some sort of announcement model where we identify who we are and what
>> we can do to a system (for registration purposes)
>> * kimchi plugin (http://github.com/kimchi-project/kimchi) for standalone
>> use cases
>> _______________________________________________
>> node-devel mailing list
>> node-devel at ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/node-devel
> _______________________________________________
> Arch mailing list
> Arch at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/arch
> 
>