How do the panelists feel about neutron and the trend toward creating a new "X-as-a-service" to recreate every physical network device. Shouldn't we be finding a way to simplify those down and let the network vendors figure out what to do with the packet?
@Beaker says LMATFY @furrier Meh as a service. Networking in Neutron is too f'ing complex, feature incomplete & prone to landgrabs that lead to lock-in.
Can the panel discuss the set of network services and resources supported now in Neutron and what they see coming in the near term? What is missing today in their opinions?
With the introduction of SPB (IEEE 801.1aq) and the push to layer 2 WAN networks, will be Neutron adopting these methodologies technologies in terms of an API?
@randybias, how many of these new Neutron features are realistically going to be used by a tenant? Or are they mainly geared for the deployment operator? (i.e. BGPaas???) App devs I know can't spell BGP.
How does the complexity and diversity of Neutron configurations affect the testability of the rest of OpenStack. Running Tempest against DevStack with a flat network doesn't really cut it, does it?
