A quick update on this. As suggested by members of the community, I created a 
nova blueprint 
https://blueprints.launchpad.net/nova/+spec/expose-vlan-trunking, and posted a 
spec for Queens here: https://review.openstack.org/471815. Sean Mooney 
suggested in his review that automatic vlan subinterface configuration in the 
guest should be enabled/disabled on per trunk basis. I think that it’s a good 
idea. But to do that requires API and database schema changes. If it’s 
something that the community would like to go with, then I’d think it requires 
a RFE from the neutron side. We need reviews and feedbacks to move this forward.

Thanks,
Robert

On 6/7/17, 12:36 PM, "Robert Li (baoli)" <[email protected]> wrote:

    Hi Bence,
    
    Thanks for the pointers. I was aware of this 
https://bugs.launchpad.net/neutron/+bug/1631371, but not the blueprint you 
wrote. 
    
    As suggested by Matt in https://bugs.launchpad.net/nova/+bug/1693535, I 
wrote a blueprint 
https://blueprints.launchpad.net/nova/+spec/expose-vlan-trunking, trying to 
tackle it in a simple manner.
    
    --Robert
    
    
    On 6/6/17, 7:35 AM, "Bence Romsics" <[email protected]> wrote:
    
        Hi Robert,
        
        I'm late to this thread, but let me add a bit. There was an attempt
        for trunk support in nova metadata on the Pike PTG:
        
        https://review.openstack.org/399076
        
        But that was abandoned right after the PTG, because the agreement
        seemed to be in favor of putting the trunk details into the upcoming
        os-vif object. The os-vif object was supposed to be described in a new
        patch set to this change:
        
        https://review.openstack.org/390513
        
        Unfortunately there's not much happening there since. Looking back now
        it seems to me that turning the os-vif object into a prerequisite made
        this work too big to ever happen. I definitely didn't have the time to
        take that on.
        
        But anyway I hope the abandoned spec may provide relevant input to you.
        
        Cheers,
        Bence
        
        
__________________________________________________________________________
        OpenStack Development Mailing List (not for usage questions)
        Unsubscribe: 
[email protected]?subject:unsubscribe
        http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
        
    
    __________________________________________________________________________
    OpenStack Development Mailing List (not for usage questions)
    Unsubscribe: [email protected]?subject:unsubscribe
    http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
    

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to