Feature pages for 3.2

[Livnat Peer]

On 23/10/12 17:11, Steve Gordon wrote:
> ----- Original Message -----
>> From: "Mike Burns" <mburns at redhat.com>
>> To: "Itamar Heim" <iheim at redhat.com>, "Dan Kenigsberg" <danken at redhat.com>, "Ayal Baron" <abaron at redhat.com>, "Livnat
>> Peer" <lpeer at redhat.com>, "Doron Fediuck" <dfediuck at redhat.com>
>> Cc: "arch" <arch at ovirt.org>
>> Sent: Sunday, October 14, 2012 10:12:11 PM
>> Subject: Feature pages for 3.2
>>
>> The 3.2 Release page[1] has a list of features targeted for 3.2.  The
>> majority of the listed features either lack a feature page
>> completely,
>> or a link is missing.  If you are responsible for the component the
>> includes the feature, can you either create or have someone create a
>> feature page?  A template page is available[2].
>>
>> Thanks
>>
>> Mike
>>
>> [1] http://wiki.ovirt.org/wiki/OVirt_3.2_release-management#Features
>> [2] http://wiki.ovirt.org/wiki/Feature_template
> 
> I have been through the list of feature pages and just have a few comments to make:
> 
> - Port mirroring was listed in the 3.1 release notes as supported, it is still in this list so does this mean it didn't actually make it or is this a further improvement to that functionality?

Port mirroring did not actually work in 3.1. We fixed it and now it
should be fine.


> 
> - Some of the feature pages for gluster functionality are pretty light on detail. In particular:
>   http://wiki.ovirt.org/wiki/Features/Gluster_Geo_Replication
>   http://wiki.ovirt.org/wiki/Features/Gluster_Volume_Asynchronous_Tasks_Management
>   http://wiki.ovirt.org/wiki/Features/Gluster_Volume_Performance_Statistics
> 
> - Still missing pages for:
>   * Bootstrap improvements
>   * VM creation base on pre-defined profiles (instance types)
>   * libvdsm preview 
>   * webadmin: allow column resizing & sorting in grid (bz 767924) 
>   * user level api
>   * automatic storage domain upgrade
>   * Japanese localization 
>   * full plugin support including example plugins (snmp, cim) 
>   Granted I already have a fair idea what some of these relate to, but let's make sure we have specific feature pages defining the desired scope for each of these.
> 
> Thanks,
> 
> Steve
>