Ihar and Kevin, As our potential future PTLs, I would like to draw your attention to one of the critical issue regarding Neutron as "the" networking service in OpenStack.
I keep hearing off and on that Neutron is not flexible to address many networking use cases and hence a new (or additional) networking project is needed. For example, to address the use cases around NFV (rigid resource inter-dependencies). Another one keeps popping up is that it is very hard/difficult to add/enhance Neutron API - hence, I picked this one goal called out in Ihar's candidacy. I would really like us to discuss this issue head-on and see what is missing in Neutron APIs and what would take to make them extensible so that vendors do not run around trying to figure out alternative solutions.... cheers.. -Sukhdev > * Explore alternative ways to evolve Neutron API. Piling up > extensions and allowing third parties to completely change core > resource behaviour is not ideal, and now that api-ref and API > consolidation effort in neutron-lib are closer to completion, we may > have better answers to outstanding questions than during previous > attempts to crack the nut. I would like to restart the discussion some > time during Pike. > > > Thanks for attention, > Ihar > > __________________________________________________________________________ > 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
