)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":8124,"name":"cbrandily","email":"zzelle@gmail.com","username":"cbrandily"},"change_message_id":"3986d88f5dbf64cb5495cae581710c849b605837","unresolved":false,"context_lines":[{"line_number":7,"context_line":"Invert device_owner to avoid filtering too much"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"In an earlier change[1], a filter was added to avoid Linuxbridge races.  This"},{"line_number":10,"context_line":"filter breaks external systems which use device owners other than"},{"line_number":11,"context_line":"n(eutron|etwork):."},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"[1] https://review.openstack.org/#/c/193485/"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":4,"id":"7a740942_da24010e","line":10,"updated":"2015-12-08 20:53:13.000000000","message":"Which external system?\n\nIMO, \"external systems\" should align them to neutron naming conventions not the opposite","commit_id":"862bca837b02c2b5f21a3cdc3d386a3df6e185ab"},{"author":{"_account_id":10980,"name":"Doug Wiegley","email":"dougwig@parkside.io","username":"dougw"},"change_message_id":"7240628a552f5e8c5f6c0864251b40312e75826f","unresolved":false,"context_lines":[{"line_number":7,"context_line":"Invert device_owner to avoid filtering too much"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"In an earlier change[1], a filter was added to avoid Linuxbridge races.  This"},{"line_number":10,"context_line":"filter breaks external systems which use device owners other than"},{"line_number":11,"context_line":"n(eutron|etwork):."},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"[1] https://review.openstack.org/#/c/193485/"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":4,"id":"5a710552_0018ab83","line":10,"in_reply_to":"5a710552_47e252a1","updated":"2015-12-14 22:12:11.000000000","message":"Interesting points here. Either we make it easy for infrastructure ports to be added by other owners, or non-infrastructure ports. Seems like that mechanism is fundamentally overloaded and broken.","commit_id":"862bca837b02c2b5f21a3cdc3d386a3df6e185ab"},{"author":{"_account_id":8124,"name":"cbrandily","email":"zzelle@gmail.com","username":"cbrandily"},"change_message_id":"8ff5006a9dccdaef64afdde26cbc1762690ad22a","unresolved":false,"context_lines":[{"line_number":7,"context_line":"Invert device_owner to avoid filtering too much"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"In an earlier change[1], a filter was added to avoid Linuxbridge races.  This"},{"line_number":10,"context_line":"filter breaks external systems which use device owners other than"},{"line_number":11,"context_line":"n(eutron|etwork):."},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"[1] https://review.openstack.org/#/c/193485/"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":4,"id":"7a740942_dfbd4bd8","line":10,"in_reply_to":"7a740942_0a2b9795","updated":"2015-12-10 22:08:31.000000000","message":"This regex is used to decide whether a device is managed by neutron (and Co) or not.\n\nIMO, using \"network:|neutron:\" to filter neutron-managed ports constraints services/drivers/plugins which are strongly coupled to neutron (ie: network related services like astara) where using \"compute:\" to filter external ports constraints services which are loosely cpouled to neutron (ie: nova, ironic, ...).\n\nShould we constraint strongly or loosely coupled ones?","commit_id":"862bca837b02c2b5f21a3cdc3d386a3df6e185ab"},{"author":{"_account_id":2592,"name":"Mark McClain","email":"mark@mcclain.xyz","username":"markmcclain"},"change_message_id":"11e73a6f270fd65e8db3034426df382c9d98d309","unresolved":false,"context_lines":[{"line_number":7,"context_line":"Invert device_owner to avoid filtering too much"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"In an earlier change[1], a filter was added to avoid Linuxbridge races.  This"},{"line_number":10,"context_line":"filter breaks external systems which use device owners other than"},{"line_number":11,"context_line":"n(eutron|etwork):."},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"[1] https://review.openstack.org/#/c/193485/"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":4,"id":"7a740942_0a2b9795","line":10,"in_reply_to":"7a740942_da24010e","updated":"2015-12-10 19:49:39.000000000","message":"We really any consumer of Neutron.  Astara names the ports it creates as astara:foo for example.  There are others too.  The original purpose of this field was to be an opaque token that did not mean anything to Neutron.  We\u0027ve now reversed it and made it meaningful breaking the long time API contract.  I know of other internal tooling where operators will list the ports they created for on networks so that they\u0027re easy to identify.","commit_id":"862bca837b02c2b5f21a3cdc3d386a3df6e185ab"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"7f2ac90c5db4f1309298ccafd337cbb83cbb8e1d","unresolved":false,"context_lines":[{"line_number":7,"context_line":"Invert device_owner to avoid filtering too much"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"In an earlier change[1], a filter was added to avoid Linuxbridge races.  This"},{"line_number":10,"context_line":"filter breaks external systems which use device owners other than"},{"line_number":11,"context_line":"n(eutron|etwork):."},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"[1] https://review.openstack.org/#/c/193485/"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":4,"id":"5a710552_47e252a1","line":10,"in_reply_to":"7a740942_dfbd4bd8","updated":"2015-12-14 19:30:51.000000000","message":"device owner has only given us grief since the time it was conceived. I am not sure it was ever meant to be opaque as Neutron uses it extensively to mark ports that belongs to it (dhcp, routers, etc)!\n\nHave you considered marking the astara ports as \u0027neutron:astara:foo\u0027\n\nThe way I understand this change is that you want astara ports to be handled by LB and get wired, correct?\n\nHaving said that, I think your integration strategy is problematic, because later on the wiring might not be appropriate for your platform and what happens then? You\u0027re relying on an implementation specific that is not meant to be public, and for your own sake it\u0027d be best if you didn\u0027t rely on it.\n\nOr am I barking up at the wrong tree?","commit_id":"862bca837b02c2b5f21a3cdc3d386a3df6e185ab"}]}
