)]}'
{"specs/kilo/network-provider.rst":[{"author":{"_account_id":10342,"name":"Jay Faulkner","display_name":"JayF","email":"jay@jvf.cc","username":"JayF","status":"youtube.com/@oss-gr / podcast.gr-oss.io"},"change_message_id":"0e998143083c4cd281e7b8552bfefc6d95cbc452","unresolved":false,"context_lines":[{"line_number":8,"context_line":"Pluggable network providers"},{"line_number":9,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"https://blueprints.launchpad.net/ironic/+spec/network-provider"},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"Today, Ironic provisions servers on the same (flat) network that tenants run"},{"line_number":14,"context_line":"on. Ironic should have the ability to logically separate provisioning and"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3a961159_5303f675","line":11,"updated":"2014-12-30 19:40:32.000000000","message":"This URL 404s.","commit_id":"33ab6b3fa2879f6fc45c3d476bd6bddc49f903a0"},{"author":{"_account_id":10343,"name":"Jim Rollenhagen","email":"jim@jimrollenhagen.com","username":"jimrollenhagen"},"change_message_id":"66906d170dc22441b5811f3d288a8aad25073677","unresolved":false,"context_lines":[{"line_number":8,"context_line":"Pluggable network providers"},{"line_number":9,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"https://blueprints.launchpad.net/ironic/+spec/network-provider"},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"Today, Ironic provisions servers on the same (flat) network that tenants run"},{"line_number":14,"context_line":"on. Ironic should have the ability to logically separate provisioning and"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3a961159_5a767407","line":11,"in_reply_to":"3a961159_5303f675","updated":"2015-01-05 15:31:28.000000000","message":"Done","commit_id":"33ab6b3fa2879f6fc45c3d476bd6bddc49f903a0"},{"author":{"_account_id":10342,"name":"Jay Faulkner","display_name":"JayF","email":"jay@jvf.cc","username":"JayF","status":"youtube.com/@oss-gr / podcast.gr-oss.io"},"change_message_id":"0e998143083c4cd281e7b8552bfefc6d95cbc452","unresolved":false,"context_lines":[{"line_number":66,"context_line":"Switch port mappings (switch hostname and port ID) will need to be stored in"},{"line_number":67,"context_line":"order to interact with the Neutron plugin. This spec proposes that this data"},{"line_number":68,"context_line":"should be stored in the ``extra`` field for the Port object representing the"},{"line_number":69,"context_line":"connected NIC. # TODO(jroll) make separate columns for this?"},{"line_number":70,"context_line":""},{"line_number":71,"context_line":"REST API impact"},{"line_number":72,"context_line":"---------------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3a961159_f3fb0246","line":69,"updated":"2014-12-30 19:40:32.000000000","message":"I think we should specifically add fields. One for switch and one for switchport. I don\u0027t have a strong preference either way, but we should resolve it to be rid of the #TODO()","commit_id":"33ab6b3fa2879f6fc45c3d476bd6bddc49f903a0"},{"author":{"_account_id":10343,"name":"Jim Rollenhagen","email":"jim@jimrollenhagen.com","username":"jimrollenhagen"},"change_message_id":"66906d170dc22441b5811f3d288a8aad25073677","unresolved":false,"context_lines":[{"line_number":66,"context_line":"Switch port mappings (switch hostname and port ID) will need to be stored in"},{"line_number":67,"context_line":"order to interact with the Neutron plugin. This spec proposes that this data"},{"line_number":68,"context_line":"should be stored in the ``extra`` field for the Port object representing the"},{"line_number":69,"context_line":"connected NIC. # TODO(jroll) make separate columns for this?"},{"line_number":70,"context_line":""},{"line_number":71,"context_line":"REST API impact"},{"line_number":72,"context_line":"---------------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3a961159_dae7c4aa","line":69,"in_reply_to":"3a961159_f3fb0246","updated":"2015-01-05 15:31:28.000000000","message":"I think I\u0027ll just remove the TODO. I imagine there may be some provider down the road that needs different info, e.g. something in a blade? Not sure.\n\nAt any rate, I don\u0027t love adding columns for a specific plugin.","commit_id":"33ab6b3fa2879f6fc45c3d476bd6bddc49f903a0"},{"author":{"_account_id":10202,"name":"Wan-yen Hsu","email":"wanyenhsu@gmail.com"},"change_message_id":"8626d420369f8491dd8471cb4873bea0d5c48cdc","unresolved":false,"context_lines":[{"line_number":58,"context_line":"------------"},{"line_number":59,"context_line":""},{"line_number":60,"context_line":"Alternatively, Ironic could continue to prescribe that operators run Ironic"},{"line_number":61,"context_line":"on a single flat network shared between tenants and the control plane."},{"line_number":62,"context_line":""},{"line_number":63,"context_line":"Data model impact"},{"line_number":64,"context_line":"-----------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3a961159_f0c79c96","line":61,"updated":"2015-01-12 06:24:48.000000000","message":"One alternative is to use a seperate management network to run deploy ramdisk (e.g., via virtual media) and management functions out-of-band.  This approach is hardware specific.","commit_id":"253f2140f43157e2648cd762c3e3ce27c7259789"},{"author":{"_account_id":10343,"name":"Jim Rollenhagen","email":"jim@jimrollenhagen.com","username":"jimrollenhagen"},"change_message_id":"1f60af382506e35102f34d11cb7230b9ba8e2af9","unresolved":false,"context_lines":[{"line_number":58,"context_line":"------------"},{"line_number":59,"context_line":""},{"line_number":60,"context_line":"Alternatively, Ironic could continue to prescribe that operators run Ironic"},{"line_number":61,"context_line":"on a single flat network shared between tenants and the control plane."},{"line_number":62,"context_line":""},{"line_number":63,"context_line":"Data model impact"},{"line_number":64,"context_line":"-----------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3a961159_76a36b00","line":61,"in_reply_to":"3a961159_f0c79c96","updated":"2015-01-13 15:41:34.000000000","message":"This would still require switching the node\u0027s main NICs between networks as the deploy ramdisk needs to talk to Ironic.","commit_id":"253f2140f43157e2648cd762c3e3ce27c7259789"},{"author":{"_account_id":10202,"name":"Wan-yen Hsu","email":"wanyenhsu@gmail.com"},"change_message_id":"8626d420369f8491dd8471cb4873bea0d5c48cdc","unresolved":false,"context_lines":[{"line_number":147,"context_line":""},{"line_number":148,"context_line":"* Implement the Neutron plugin provider."},{"line_number":149,"context_line":""},{"line_number":150,"context_line":"* Instrument each deploy driver with calls to this interface."},{"line_number":151,"context_line":""},{"line_number":152,"context_line":""},{"line_number":153,"context_line":"Dependencies"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3a961159_30f684d9","line":150,"updated":"2015-01-12 06:24:48.000000000","message":"Will virtual media driver need to make this call?","commit_id":"253f2140f43157e2648cd762c3e3ce27c7259789"},{"author":{"_account_id":10375,"name":"Om Kumar","email":"om.kumar@hpe.com","username":"lazy_prince"},"change_message_id":"abac0dab3714fdbec90f53737ae70cb0c521fece","unresolved":false,"context_lines":[{"line_number":147,"context_line":""},{"line_number":148,"context_line":"* Implement the Neutron plugin provider."},{"line_number":149,"context_line":""},{"line_number":150,"context_line":"* Instrument each deploy driver with calls to this interface."},{"line_number":151,"context_line":""},{"line_number":152,"context_line":""},{"line_number":153,"context_line":"Dependencies"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3a961159_907bb8bd","line":150,"in_reply_to":"3a961159_30f684d9","updated":"2015-01-12 07:12:46.000000000","message":"I think, it will need to. As node needs to be in correct network during each provisioning steps.","commit_id":"253f2140f43157e2648cd762c3e3ce27c7259789"},{"author":{"_account_id":10343,"name":"Jim Rollenhagen","email":"jim@jimrollenhagen.com","username":"jimrollenhagen"},"change_message_id":"1f60af382506e35102f34d11cb7230b9ba8e2af9","unresolved":false,"context_lines":[{"line_number":147,"context_line":""},{"line_number":148,"context_line":"* Implement the Neutron plugin provider."},{"line_number":149,"context_line":""},{"line_number":150,"context_line":"* Instrument each deploy driver with calls to this interface."},{"line_number":151,"context_line":""},{"line_number":152,"context_line":""},{"line_number":153,"context_line":"Dependencies"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3a961159_96a6170e","line":150,"in_reply_to":"3a961159_907bb8bd","updated":"2015-01-13 15:41:34.000000000","message":"Yes, all drivers will need to.","commit_id":"253f2140f43157e2648cd762c3e3ce27c7259789"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"73d70902a85ea3271a0e10e10d3879e92b12266a","unresolved":false,"context_lines":[{"line_number":45,"context_line":"arbitrary tenant networks."},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"A pluggable interface for doing these tasks should be implemented. A \"none\""},{"line_number":48,"context_line":"provider that no-ops each task should be implemented for compatibility."},{"line_number":49,"context_line":""},{"line_number":50,"context_line":"A second provider that talks to Rackspace\u0027s Neutron plugin for Ironic[0]"},{"line_number":51,"context_line":"should be implemented. This plugin is the only known Neutron plugin that"}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a961159_3615bf9a","line":48,"updated":"2015-01-19 09:26:30.000000000","message":"could you formally specify, how this interface is going to look API-wise?","commit_id":"9bfe9b7c3db64ba2f34267d03b20a436d530c321"},{"author":{"_account_id":10343,"name":"Jim Rollenhagen","email":"jim@jimrollenhagen.com","username":"jimrollenhagen"},"change_message_id":"b289e59ce488105a520267a21120a5ac8ad1778f","unresolved":false,"context_lines":[{"line_number":45,"context_line":"arbitrary tenant networks."},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"A pluggable interface for doing these tasks should be implemented. A \"none\""},{"line_number":48,"context_line":"provider that no-ops each task should be implemented for compatibility."},{"line_number":49,"context_line":""},{"line_number":50,"context_line":"A second provider that talks to Rackspace\u0027s Neutron plugin for Ironic[0]"},{"line_number":51,"context_line":"should be implemented. This plugin is the only known Neutron plugin that"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a930d6b_e5010c6b","line":48,"in_reply_to":"1a930d6b_9ffff5a9","updated":"2015-01-26 16:44:57.000000000","message":"The tenant networks are added to neutron by nova, it can be default networks in nova or specified with \u0027nova boot --nic\u0027. So ironic is just telling neutron to configure those networks at this point. However Ironic tells neutron to create/delete the provisioning network, Nova knows nothing about that.\n\nNeutron stores all the info about which ports are connected/configured/etc along with the ironic node ID.","commit_id":"9bfe9b7c3db64ba2f34267d03b20a436d530c321"},{"author":{"_account_id":10343,"name":"Jim Rollenhagen","email":"jim@jimrollenhagen.com","username":"jimrollenhagen"},"change_message_id":"e3d61f3ef1b1121ff1fd19426f6a1e0b5fae3e58","unresolved":false,"context_lines":[{"line_number":45,"context_line":"arbitrary tenant networks."},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"A pluggable interface for doing these tasks should be implemented. A \"none\""},{"line_number":48,"context_line":"provider that no-ops each task should be implemented for compatibility."},{"line_number":49,"context_line":""},{"line_number":50,"context_line":"A second provider that talks to Rackspace\u0027s Neutron plugin for Ironic[0]"},{"line_number":51,"context_line":"should be implemented. This plugin is the only known Neutron plugin that"}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a961159_ef68a024","line":48,"in_reply_to":"3a961159_3615bf9a","updated":"2015-01-20 04:32:52.000000000","message":"Yes, will push a new rev. In the meantime I\u0027ve put up a WIP patch with the interface: https://review.openstack.org/#/c/139687/","commit_id":"9bfe9b7c3db64ba2f34267d03b20a436d530c321"},{"author":{"_account_id":6773,"name":"Lucas Alvares Gomes","email":"lucasagomes@gmail.com","username":"lucasagomes"},"change_message_id":"72f064754bf73fe099eb8f7894ec2f5554b20898","unresolved":false,"context_lines":[{"line_number":45,"context_line":"arbitrary tenant networks."},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"A pluggable interface for doing these tasks should be implemented. A \"none\""},{"line_number":48,"context_line":"provider that no-ops each task should be implemented for compatibility."},{"line_number":49,"context_line":""},{"line_number":50,"context_line":"A second provider that talks to Rackspace\u0027s Neutron plugin for Ironic[0]"},{"line_number":51,"context_line":"should be implemented. This plugin is the only known Neutron plugin that"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a930d6b_9ffff5a9","line":48,"in_reply_to":"3a961159_5f707bda","updated":"2015-01-23 14:08:55.000000000","message":"Yeah a bit of implementation detail would be good.\n\nDoesn\u0027t need to be very very code specific, but things like how one define which Port (in Ironic, the port resource) is plugged to the provisioning network or the production one?\n\nIs it a new attribute to the Port resource? Are we going to use the extra field to define it? Or it\u0027s complete out of the Port resource and it should live in the external service (say neutron) and it will be linked to the port in Ironic using the mac address, etc...","commit_id":"9bfe9b7c3db64ba2f34267d03b20a436d530c321"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"69be4a204866b1681c26a935bac09faa7b7f62b6","unresolved":false,"context_lines":[{"line_number":45,"context_line":"arbitrary tenant networks."},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"A pluggable interface for doing these tasks should be implemented. A \"none\""},{"line_number":48,"context_line":"provider that no-ops each task should be implemented for compatibility."},{"line_number":49,"context_line":""},{"line_number":50,"context_line":"A second provider that talks to Rackspace\u0027s Neutron plugin for Ironic[0]"},{"line_number":51,"context_line":"should be implemented. This plugin is the only known Neutron plugin that"}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a961159_5f707bda","line":48,"in_reply_to":"3a961159_ef68a024","updated":"2015-01-20 10:03:52.000000000","message":"not sure I understand why add_provisioning_network but configure_tenant_networks? Aren\u0027t they doing something similar essentially?","commit_id":"9bfe9b7c3db64ba2f34267d03b20a436d530c321"},{"author":{"_account_id":10202,"name":"Wan-yen Hsu","email":"wanyenhsu@gmail.com"},"change_message_id":"a501b418c14cef06bd21fdc6a3a398b0e25ada5e","unresolved":false,"context_lines":[{"line_number":50,"context_line":"A second provider that talks to Rackspace\u0027s Neutron plugin for Ironic[0]"},{"line_number":51,"context_line":"should be implemented. This plugin is the only known Neutron plugin that"},{"line_number":52,"context_line":"can configure real switches."},{"line_number":53,"context_line":""},{"line_number":54,"context_line":"Deploy drivers should call to this interface at proper times to switch between"},{"line_number":55,"context_line":"networks. For example, a driver completing a deploy should power off the node,"},{"line_number":56,"context_line":"switch to the instance networks, and power on the node. This will ensure that"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a930d6b_31483f2d","line":53,"updated":"2015-01-21 20:50:43.000000000","message":"Do you know the status of neutron exteranl attachment point spec https://blueprints.launchpad.net/neutron/+spec/neutron-external-attachment-points?   I thought it was supposed to be a neutron plugin that can be used by Ironic to configure and assign physical switch port.","commit_id":"9bfe9b7c3db64ba2f34267d03b20a436d530c321"},{"author":{"_account_id":10343,"name":"Jim Rollenhagen","email":"jim@jimrollenhagen.com","username":"jimrollenhagen"},"change_message_id":"b289e59ce488105a520267a21120a5ac8ad1778f","unresolved":false,"context_lines":[{"line_number":50,"context_line":"A second provider that talks to Rackspace\u0027s Neutron plugin for Ironic[0]"},{"line_number":51,"context_line":"should be implemented. This plugin is the only known Neutron plugin that"},{"line_number":52,"context_line":"can configure real switches."},{"line_number":53,"context_line":""},{"line_number":54,"context_line":"Deploy drivers should call to this interface at proper times to switch between"},{"line_number":55,"context_line":"networks. For example, a driver completing a deploy should power off the node,"},{"line_number":56,"context_line":"switch to the instance networks, and power on the node. This will ensure that"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a930d6b_058b78c3","line":53,"in_reply_to":"1a930d6b_31483f2d","updated":"2015-01-26 16:44:57.000000000","message":"I don\u0027t think any work has been done, I would love to see it happen, though.","commit_id":"9bfe9b7c3db64ba2f34267d03b20a436d530c321"},{"author":{"_account_id":8106,"name":"Haomeng,Wang","email":"wanghaomeng@gmail.com","username":"whaom"},"change_message_id":"c7530f2db238872665a702a63ce07fec6b4436a8","unresolved":false,"context_lines":[{"line_number":53,"context_line":""},{"line_number":54,"context_line":"Deploy drivers should call to this interface at proper times to switch between"},{"line_number":55,"context_line":"networks. For example, a driver completing a deploy should power off the node,"},{"line_number":56,"context_line":"switch to the instance networks, and power on the node. This will ensure that"},{"line_number":57,"context_line":"the deploy ramdisk never runs on the instance network, and the instance image"},{"line_number":58,"context_line":"never runs on the provisioning network."},{"line_number":59,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a930d6b_f61ac47b","line":56,"updated":"2015-01-25 01:15:39.000000000","message":"I understand this network-provider can not support pxe_ipmitool and pxe_ipminative drivers, because these iscsi drivers have to run pxe to boot local root paration after the image is \u0027dd\u0027 into local harddisk, so agree below Lucas comment that we can continue to support iscsi drivers.","commit_id":"9bfe9b7c3db64ba2f34267d03b20a436d530c321"},{"author":{"_account_id":10343,"name":"Jim Rollenhagen","email":"jim@jimrollenhagen.com","username":"jimrollenhagen"},"change_message_id":"b289e59ce488105a520267a21120a5ac8ad1778f","unresolved":false,"context_lines":[{"line_number":53,"context_line":""},{"line_number":54,"context_line":"Deploy drivers should call to this interface at proper times to switch between"},{"line_number":55,"context_line":"networks. For example, a driver completing a deploy should power off the node,"},{"line_number":56,"context_line":"switch to the instance networks, and power on the node. This will ensure that"},{"line_number":57,"context_line":"the deploy ramdisk never runs on the instance network, and the instance image"},{"line_number":58,"context_line":"never runs on the provisioning network."},{"line_number":59,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a930d6b_85be8863","line":56,"in_reply_to":"1a930d6b_f61ac47b","updated":"2015-01-26 16:44:57.000000000","message":"We can\u0027t pxe boot if we aren\u0027t on the provisioning network, this will have to be for local boot only.","commit_id":"9bfe9b7c3db64ba2f34267d03b20a436d530c321"},{"author":{"_account_id":6773,"name":"Lucas Alvares Gomes","email":"lucasagomes@gmail.com","username":"lucasagomes"},"change_message_id":"72f064754bf73fe099eb8f7894ec2f5554b20898","unresolved":false,"context_lines":[{"line_number":55,"context_line":"networks. For example, a driver completing a deploy should power off the node,"},{"line_number":56,"context_line":"switch to the instance networks, and power on the node. This will ensure that"},{"line_number":57,"context_line":"the deploy ramdisk never runs on the instance network, and the instance image"},{"line_number":58,"context_line":"never runs on the provisioning network."},{"line_number":59,"context_line":""},{"line_number":60,"context_line":"Alternatives"},{"line_number":61,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a930d6b_ff6f19c3","line":58,"updated":"2015-01-23 14:08:55.000000000","message":"The default PXE/iSCSI ramdisk reboots itself after the image is copied onto the disk by the Ironic conductor. It basically exports the disk via iscsi and pass it to the conductor; The conductor then copies the image onto that disk and signalize the ramdisk back[1] saying it\u0027s finished; Then ramdisk then do whatever it needs to do pos-image is copied and reboots.\n\nSo to this work we may need to change a little that behavior, which I think is easy. I believe we need to add another vendor_passthru() call to pxe_* drivers to signilize that the deploy ramdisk completed the deployment and the node can now be powered off/on.\n\n[1] https://github.com/openstack/ironic/blob/master/ironic/drivers/modules/deploy_utils.py#L505-L512","commit_id":"9bfe9b7c3db64ba2f34267d03b20a436d530c321"},{"author":{"_account_id":10343,"name":"Jim Rollenhagen","email":"jim@jimrollenhagen.com","username":"jimrollenhagen"},"change_message_id":"b289e59ce488105a520267a21120a5ac8ad1778f","unresolved":false,"context_lines":[{"line_number":55,"context_line":"networks. For example, a driver completing a deploy should power off the node,"},{"line_number":56,"context_line":"switch to the instance networks, and power on the node. This will ensure that"},{"line_number":57,"context_line":"the deploy ramdisk never runs on the instance network, and the instance image"},{"line_number":58,"context_line":"never runs on the provisioning network."},{"line_number":59,"context_line":""},{"line_number":60,"context_line":"Alternatives"},{"line_number":61,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a930d6b_8565a81f","line":58,"in_reply_to":"1a930d6b_ff6f19c3","updated":"2015-01-26 16:44:57.000000000","message":"Talked about this in IRC; this feature is useful outside of this spec and will be dealt with somewhere else.","commit_id":"9bfe9b7c3db64ba2f34267d03b20a436d530c321"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"73d70902a85ea3271a0e10e10d3879e92b12266a","unresolved":false,"context_lines":[{"line_number":68,"context_line":""},{"line_number":69,"context_line":"Switch port mappings (switch hostname and port ID) will need to be stored in"},{"line_number":70,"context_line":"order to interact with the Neutron plugin. This spec proposes that this data"},{"line_number":71,"context_line":"should be stored in the ``extra`` field for the Port object representing the"},{"line_number":72,"context_line":"connected NIC."},{"line_number":73,"context_line":""},{"line_number":74,"context_line":"REST API impact"}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a961159_963e7327","line":71,"updated":"2015-01-19 09:26:30.000000000","message":"/me lacks driver_info on Port :(","commit_id":"9bfe9b7c3db64ba2f34267d03b20a436d530c321"},{"author":{"_account_id":10343,"name":"Jim Rollenhagen","email":"jim@jimrollenhagen.com","username":"jimrollenhagen"},"change_message_id":"b289e59ce488105a520267a21120a5ac8ad1778f","unresolved":false,"context_lines":[{"line_number":68,"context_line":""},{"line_number":69,"context_line":"Switch port mappings (switch hostname and port ID) will need to be stored in"},{"line_number":70,"context_line":"order to interact with the Neutron plugin. This spec proposes that this data"},{"line_number":71,"context_line":"should be stored in the ``extra`` field for the Port object representing the"},{"line_number":72,"context_line":"connected NIC."},{"line_number":73,"context_line":""},{"line_number":74,"context_line":"REST API impact"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a930d6b_a56aa4eb","line":71,"in_reply_to":"3a961159_3fac8f36","updated":"2015-01-26 16:44:57.000000000","message":"Ok, will add it.","commit_id":"9bfe9b7c3db64ba2f34267d03b20a436d530c321"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"69be4a204866b1681c26a935bac09faa7b7f62b6","unresolved":false,"context_lines":[{"line_number":68,"context_line":""},{"line_number":69,"context_line":"Switch port mappings (switch hostname and port ID) will need to be stored in"},{"line_number":70,"context_line":"order to interact with the Neutron plugin. This spec proposes that this data"},{"line_number":71,"context_line":"should be stored in the ``extra`` field for the Port object representing the"},{"line_number":72,"context_line":"connected NIC."},{"line_number":73,"context_line":""},{"line_number":74,"context_line":"REST API impact"}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a961159_3fac8f36","line":71,"in_reply_to":"3a961159_8f2c7c03","updated":"2015-01-20 10:03:52.000000000","message":"I don\u0027t insist, but we decided that extra is for operators... and I think it\u0027s not too hard to do anyway.","commit_id":"9bfe9b7c3db64ba2f34267d03b20a436d530c321"},{"author":{"_account_id":10343,"name":"Jim Rollenhagen","email":"jim@jimrollenhagen.com","username":"jimrollenhagen"},"change_message_id":"e3d61f3ef1b1121ff1fd19426f6a1e0b5fae3e58","unresolved":false,"context_lines":[{"line_number":68,"context_line":""},{"line_number":69,"context_line":"Switch port mappings (switch hostname and port ID) will need to be stored in"},{"line_number":70,"context_line":"order to interact with the Neutron plugin. This spec proposes that this data"},{"line_number":71,"context_line":"should be stored in the ``extra`` field for the Port object representing the"},{"line_number":72,"context_line":"connected NIC."},{"line_number":73,"context_line":""},{"line_number":74,"context_line":"REST API impact"}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a961159_8f2c7c03","line":71,"in_reply_to":"3a961159_963e7327","updated":"2015-01-20 04:32:52.000000000","message":"Yeah... we could make it, I\u0027m open to it. Thoughts?","commit_id":"9bfe9b7c3db64ba2f34267d03b20a436d530c321"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"73d70902a85ea3271a0e10e10d3879e92b12266a","unresolved":false,"context_lines":[{"line_number":125,"context_line":""},{"line_number":126,"context_line":"* ``CONF.network_provider`` specifies the network provider to be used."},{"line_number":127,"context_line":""},{"line_number":128,"context_line":"* ``CONF.provisioning_network`` specifies the ID of the provisioning network."},{"line_number":129,"context_line":""},{"line_number":130,"context_line":"Developer impact"},{"line_number":131,"context_line":"----------------"}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a961159_7634a748","line":128,"updated":"2015-01-19 09:26:30.000000000","message":"likely stupid question, but: do we need to specify production_network as well? If not helpful for your plugin, can it be helpful for (theoretical) other?","commit_id":"9bfe9b7c3db64ba2f34267d03b20a436d530c321"},{"author":{"_account_id":10343,"name":"Jim Rollenhagen","email":"jim@jimrollenhagen.com","username":"jimrollenhagen"},"change_message_id":"b289e59ce488105a520267a21120a5ac8ad1778f","unresolved":false,"context_lines":[{"line_number":125,"context_line":""},{"line_number":126,"context_line":"* ``CONF.network_provider`` specifies the network provider to be used."},{"line_number":127,"context_line":""},{"line_number":128,"context_line":"* ``CONF.provisioning_network`` specifies the ID of the provisioning network."},{"line_number":129,"context_line":""},{"line_number":130,"context_line":"Developer impact"},{"line_number":131,"context_line":"----------------"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a930d6b_457f40ab","line":128,"in_reply_to":"3a961159_2fee28b6","updated":"2015-01-26 16:44:57.000000000","message":"Additionally, this should be able to be specified by the user as private networks are a thing.","commit_id":"9bfe9b7c3db64ba2f34267d03b20a436d530c321"},{"author":{"_account_id":10343,"name":"Jim Rollenhagen","email":"jim@jimrollenhagen.com","username":"jimrollenhagen"},"change_message_id":"e3d61f3ef1b1121ff1fd19426f6a1e0b5fae3e58","unresolved":false,"context_lines":[{"line_number":125,"context_line":""},{"line_number":126,"context_line":"* ``CONF.network_provider`` specifies the network provider to be used."},{"line_number":127,"context_line":""},{"line_number":128,"context_line":"* ``CONF.provisioning_network`` specifies the ID of the provisioning network."},{"line_number":129,"context_line":""},{"line_number":130,"context_line":"Developer impact"},{"line_number":131,"context_line":"----------------"}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a961159_2fee28b6","line":128,"in_reply_to":"3a961159_7634a748","updated":"2015-01-20 04:32:52.000000000","message":"This would typically be provided by nova, either through defaults or via --nic. It might be helpful for other plugins, however I tend to think they could add that option as the need arises.","commit_id":"9bfe9b7c3db64ba2f34267d03b20a436d530c321"}]}