Open Stack

Hi

So adding a deprecation warning but saying the “the code is there but not tested” in Liberty isn’t really doing it right.  The deprecation warning should come in a release where the code is still tested and working (so there is no danger in breaking customers), but they are warned that they need to change what they are doing by a certain release, or it may no longer work.

Henry
> On 4 Aug 2015, at 16:28, Alessandro Pilotti <apilotti at cloudbasesolutions.com> wrote:
> 
>> 
>> On 04 Aug 2015, at 17:56, Daniel P. Berrange <berrange at redhat.com> wrote:
>> 
>> On Tue, Aug 04, 2015 at 02:34:19PM +0000, Alessandro Pilotti wrote:
>>> Hi guys,
>>> 
>>> Just a quick note on the Windows editions support matrix updates for the Nova
>>> Hyper-V driver and Neutron networking-hyperv ML2 agent:  
>>> 
>>> We are planning to drop legacy Windows Server / Hyper-V Server 2008 R2 support
>>> starting with Liberty.
>>> 
>>> Windows Server / Hyper-V Server 2012 and above will continue to be supported.
>> 
>> What do you mean precisely by drop support here ?  Are you merely no longer
>> testing it, or is Nova actually broken with Hyper-V 2k8 R2  in Liberty ?
>> 
>> Generally if we intend to drop a hypervisor platform we'd expect to have a
>> deprecation period for 1 cycle where Nova would print out a warning message
>> on startup to alert administrators if using the platform that is intended
>> to be dropped. This gives them time to plan a move to a newer platform
>> before we drop the support.
> 
> The plan is to move the Hyper-V specific code to a new Oslo project during the
> early M cycle and as part of the move the 2008 R2 specific code will be dropped.
> This refers to the OS specific interaction layer (the *utils modules)
> which are mostly shared across multiple projects (nova, cinder,
> networking-hyperv, ceilometer, etc).
> 
> Contextually the corresponding code will be proposed for removal in Nova,
> replacing it with the new oslo dependency.
> 
> The 2008 R2 code will still be available in Liberty, although untested.
> A deprecation warning can surely be added to the logs.
> 
> Alessandro
> 
>> 
>> Regards,
>> Daniel
>> -- 
>> |: http://berrange.com <http://berrange.com/>      -o-    http://www.flickr.com/photos/dberrange/ <http://www.flickr.com/photos/dberrange/> :|
>> |: http://libvirt.org <http://libvirt.org/>              -o-             http://virt-manager.org <http://virt-manager.org/> :|
>> |: http://autobuild.org <http://autobuild.org/>       -o-         http://search.cpan.org/~danberr/ <http://search.cpan.org/~danberr/> :|
>> |: http://entangle-photo.org <http://entangle-photo.org/>       -o-       http://live.gnome.org/gtk-vnc <http://live.gnome.org/gtk-vnc> :|
>> 
>> __________________________________________________________________________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: OpenStack-dev-request at lists.openstack.org <mailto:OpenStack-dev-request at lists.openstack.org>?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>
> 
> 
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org <mailto:OpenStack-dev-request at lists.openstack.org>?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150809/5cad53e8/attachment.html>