Hi John, Just to let you know, I have just filled in the blueprint here: https://blueprints.launchpad.net/nova/+spec/libvirt-vhostuser-vrouter-vif
Regards, Michal On 4 November 2015 at 12:20, John Garbutt <j...@johngarbutt.com> wrote: > In terms of adding this into master, we can go for a spec-less > blueprint in Nova. > > Reach out to me on IRC if I can help you through the process. > > Thanks, > johnthetubaguy > > PS > We are working on making this easier in the future, by using OS VIF Lib. > > On 4 November 2015 at 08:56, Michał Dubiel <m...@semihalf.com> wrote: > > Ok, I see. Thanks for all the answers. > > > > Regards, > > Michal > > > > On 3 November 2015 at 22:50, Matt Riedemann <mrie...@linux.vnet.ibm.com> > > wrote: > >> > >> > >> > >> On 11/3/2015 11:57 AM, Michał Dubiel wrote: > >>> > >>> Hi all, > >>> > >>> We have a simple patch allowing to use OpenContrail's vrouter with > >>> vhostuser vif types (currently only OVS has support for that). We would > >>> like to contribute it. > >>> > >>> However, We would like this change to land in the next maintenance > >>> release of Kilo. Is it possible? What should be the process for this? > >>> Should we prepare a blueprint and review request for the 'master' > branch > >>> first? It is small self contained change so I believe it does not need > a > >>> nova-spec. > >>> > >>> Regards, > >>> Michal > >>> > >>> > >>> > >>> > __________________________________________________________________________ > >>> OpenStack Development Mailing List (not for usage questions) > >>> Unsubscribe: > >>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >>> > >> > >> The short answer is 'no' to backporting features to stable branches. > >> > >> As the other reply said, feature changes are targeted to master. > >> > >> The full stable branch policy is here: > >> > >> https://wiki.openstack.org/wiki/StableBranch > >> > >> -- > >> > >> Thanks, > >> > >> Matt Riedemann > >> > >> > >> > >> > __________________________________________________________________________ > >> OpenStack Development Mailing List (not for usage questions) > >> Unsubscribe: > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > > > > > > __________________________________________________________________________ > > OpenStack Development Mailing List (not for usage questions) > > Unsubscribe: > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev