)]}'
{"specs/liberty/approved/neutron-binding-simplified-forms.rst":[{"author":{"_account_id":13734,"name":"Nell Jerram","email":"nell@tigera.io","username":"neiljerram"},"change_message_id":"bf85ed667218be1f4b4c3483b4ffec8562ff34d3","unresolved":false,"context_lines":[{"line_number":12,"context_line":""},{"line_number":13,"context_line":"This proposes adding a set of binding types that have simple code"},{"line_number":14,"context_line":"on Nova\u0027s side, with all the complexity in Neutron, and making them"},{"line_number":15,"context_line":"preferentially selected via the binding negotiation.."},{"line_number":16,"context_line":""},{"line_number":17,"context_line":"Problem description"},{"line_number":18,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":1,"id":"1af86dd1_2a40fb55","line":15,"updated":"2015-06-12 16:14:38.000000000","message":"Nit: two full stops here.","commit_id":"3739e2059a4c79e1a0541343434ff5e411bb8d62"},{"author":{"_account_id":13734,"name":"Nell Jerram","email":"nell@tigera.io","username":"neiljerram"},"change_message_id":"bf85ed667218be1f4b4c3483b4ffec8562ff34d3","unresolved":false,"context_lines":[{"line_number":20,"context_line":"The binding types are frequently quite complex in the operations they"},{"line_number":21,"context_line":"require of Nova.  Specifically:"},{"line_number":22,"context_line":""},{"line_number":23,"context_line":"    - Nova phsyically predicts the naming conventions of TAP interfaces"},{"line_number":24,"context_line":"    - Nova knows what the integration bridge is called, via config"},{"line_number":25,"context_line":"    - Some binding types require onerous setup on Nova\u0027s part"},{"line_number":26,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"1af86dd1_2a17db52","line":23,"updated":"2015-06-12 16:14:38.000000000","message":"Nit: physically","commit_id":"3739e2059a4c79e1a0541343434ff5e411bb8d62"},{"author":{"_account_id":13734,"name":"Nell Jerram","email":"nell@tigera.io","username":"neiljerram"},"change_message_id":"bf85ed667218be1f4b4c3483b4ffec8562ff34d3","unresolved":false,"context_lines":[{"line_number":68,"context_line":"------------"},{"line_number":69,"context_line":""},{"line_number":70,"context_line":"Do nothing.  Live with complex VIF plugging code forever."},{"line_number":71,"context_line":""},{"line_number":72,"context_line":"Data model impact"},{"line_number":73,"context_line":"-----------------"},{"line_number":74,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"1af86dd1_0dde796d","line":71,"updated":"2015-06-12 16:14:38.000000000","message":"I think there is a serious alternative in the form of https://review.openstack.org/#/c/162468/ - especially as it is now (possibly) being evolved so as to have no built-in plug/unplug code at all in Nova...","commit_id":"3739e2059a4c79e1a0541343434ff5e411bb8d62"},{"author":{"_account_id":3217,"name":"Ian Wells","username":"ijw-ubuntu"},"change_message_id":"5a9f1213827aad326b45d1ccb9136e984a7c205a","unresolved":false,"context_lines":[{"line_number":68,"context_line":"------------"},{"line_number":69,"context_line":""},{"line_number":70,"context_line":"Do nothing.  Live with complex VIF plugging code forever."},{"line_number":71,"context_line":""},{"line_number":72,"context_line":"Data model impact"},{"line_number":73,"context_line":"-----------------"},{"line_number":74,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"1af86dd1_9b04df7e","line":71,"in_reply_to":"1af86dd1_0dde796d","updated":"2015-06-12 17:12:06.000000000","message":"There is always plug/unplug code in Nova.  The code writes config into the libvirt xml file, as an example.  Whatever is used there has to be created by something.  If Neutron wants to change that - and it may well - it can\u0027t in your model.  \n\nAlso, that code is irrevocably tied to Nova, it\u0027s not something that Neutron can know independently or that is necessarily consistent between Nova versions.  You are effectively saying \u0027Nova will have VIF plugging types that Nova determines and can\u0027t be added to that have a defined interface, and the plugging script can rely on them\u0027 - but that still doesn\u0027t address the shortcoming we had when you wanted to, for instance, introduce VIF_TYPE_TAP in the first place.  If you don\u0027t cover every eventuality - and you can\u0027t, someone will modify qemu and want a new attachment type - then the script can\u0027t fix the shortcomings.","commit_id":"3739e2059a4c79e1a0541343434ff5e411bb8d62"}]}