)]}'
{"specs/kilo/approved/api-specify-vnic-type.rst":[{"author":{"_account_id":6685,"name":"Baodong (Robert) Li","email":"baoli@cisco.com","username":"baoli"},"change_message_id":"4b6fa93418c41a42073d48d7fb2415ce72277f56","unresolved":false,"context_lines":[{"line_number":17,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":18,"context_line":""},{"line_number":19,"context_line":"To boot a VM with an SRIOV port the vnic_type of the port needs to be set to"},{"line_number":20,"context_line":"\"direct\". Currently to do that a Neutron port has to be precreated, vnic_type"},{"line_number":21,"context_line":"has to be set accordingly by the user and then port uuid is passed to nova"},{"line_number":22,"context_line":"boot. This is inconvenient and prevents the user from booting multiple VM\u0027s"},{"line_number":23,"context_line":"with SRIOV ports using :"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a961159_6d673526","line":20,"updated":"2014-12-09 13:41:20.000000000","message":"and \u0027macvtap\u0027","commit_id":"dadf2a11f8ae72e2f07d2e2212798678302a8103"},{"author":{"_account_id":11647,"name":"Przemyslaw Czesnowicz","email":"przemyslaw.czesnowicz@intel.com","username":"pczesno"},"change_message_id":"eb484800da69ab064bba83bc07acf32bfca2d5b5","unresolved":false,"context_lines":[{"line_number":17,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":18,"context_line":""},{"line_number":19,"context_line":"To boot a VM with an SRIOV port the vnic_type of the port needs to be set to"},{"line_number":20,"context_line":"\"direct\". Currently to do that a Neutron port has to be precreated, vnic_type"},{"line_number":21,"context_line":"has to be set accordingly by the user and then port uuid is passed to nova"},{"line_number":22,"context_line":"boot. This is inconvenient and prevents the user from booting multiple VM\u0027s"},{"line_number":23,"context_line":"with SRIOV ports using :"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a961159_84ba73be","line":20,"in_reply_to":"3a961159_6d673526","updated":"2014-12-09 16:14:49.000000000","message":"Done","commit_id":"dadf2a11f8ae72e2f07d2e2212798678302a8103"},{"author":{"_account_id":6685,"name":"Baodong (Robert) Li","email":"baoli@cisco.com","username":"baoli"},"change_message_id":"4b6fa93418c41a42073d48d7fb2415ce72277f56","unresolved":false,"context_lines":[{"line_number":46,"context_line":"Where \u003ctype\u003e is one of:"},{"line_number":47,"context_line":"normal"},{"line_number":48,"context_line":"direct"},{"line_number":49,"context_line":"macvtap"},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"Alternatives"},{"line_number":52,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a961159_935b9e86","line":49,"updated":"2014-12-09 13:41:20.000000000","message":"A little bit detail on how this will be implemented would be great, for example, how pci_request will be created, etc.","commit_id":"dadf2a11f8ae72e2f07d2e2212798678302a8103"},{"author":{"_account_id":11647,"name":"Przemyslaw Czesnowicz","email":"przemyslaw.czesnowicz@intel.com","username":"pczesno"},"change_message_id":"eb484800da69ab064bba83bc07acf32bfca2d5b5","unresolved":false,"context_lines":[{"line_number":46,"context_line":"Where \u003ctype\u003e is one of:"},{"line_number":47,"context_line":"normal"},{"line_number":48,"context_line":"direct"},{"line_number":49,"context_line":"macvtap"},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"Alternatives"},{"line_number":52,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a961159_5f685487","line":49,"in_reply_to":"3a961159_935b9e86","updated":"2014-12-09 16:14:49.000000000","message":"OK, will add more info.","commit_id":"dadf2a11f8ae72e2f07d2e2212798678302a8103"},{"author":{"_account_id":6685,"name":"Baodong (Robert) Li","email":"baoli@cisco.com","username":"baoli"},"change_message_id":"4b6fa93418c41a42073d48d7fb2415ce72277f56","unresolved":false,"context_lines":[{"line_number":60,"context_line":"* Using flavor extra_spec or image properties to store vnic_type."},{"line_number":61,"context_line":"  Both flavor and image approaches would be very inflexible as new"},{"line_number":62,"context_line":"  flavor or image would be needed to support different configurations"},{"line_number":63,"context_line":"  (i.e first nic uses direct and the second normal)"},{"line_number":64,"context_line":""},{"line_number":65,"context_line":""},{"line_number":66,"context_line":"Data model impact"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a961159_f8f3e19c","line":63,"updated":"2014-12-09 13:41:20.000000000","message":"Not sure if you are aware of this: https://wiki.openstack.org/wiki/PCI_passthrough_SRIOV_support.","commit_id":"dadf2a11f8ae72e2f07d2e2212798678302a8103"},{"author":{"_account_id":11647,"name":"Przemyslaw Czesnowicz","email":"przemyslaw.czesnowicz@intel.com","username":"pczesno"},"change_message_id":"eb484800da69ab064bba83bc07acf32bfca2d5b5","unresolved":false,"context_lines":[{"line_number":60,"context_line":"* Using flavor extra_spec or image properties to store vnic_type."},{"line_number":61,"context_line":"  Both flavor and image approaches would be very inflexible as new"},{"line_number":62,"context_line":"  flavor or image would be needed to support different configurations"},{"line_number":63,"context_line":"  (i.e first nic uses direct and the second normal)"},{"line_number":64,"context_line":""},{"line_number":65,"context_line":""},{"line_number":66,"context_line":"Data model impact"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a961159_64190788","line":63,"in_reply_to":"3a961159_f8f3e19c","updated":"2014-12-09 16:14:49.000000000","message":"Yes i saw that. I\u0027ll include in alternatives.","commit_id":"dadf2a11f8ae72e2f07d2e2212798678302a8103"},{"author":{"_account_id":6685,"name":"Baodong (Robert) Li","email":"baoli@cisco.com","username":"baoli"},"change_message_id":"4b6fa93418c41a42073d48d7fb2415ce72277f56","unresolved":false,"context_lines":[{"line_number":157,"context_line":""},{"line_number":158,"context_line":""},{"line_number":159,"context_line":"The second modification is to add optional parameter to"},{"line_number":160,"context_line":"attach network interface method."},{"line_number":161,"context_line":""},{"line_number":162,"context_line":"Method Type : POST"},{"line_number":163,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a961159_384569b3","line":160,"updated":"2014-12-09 13:41:20.000000000","message":"Yongli indicated that he will be working on the sriov hot plug/unplug. Wonder if he has done any work on this","commit_id":"dadf2a11f8ae72e2f07d2e2212798678302a8103"},{"author":{"_account_id":11647,"name":"Przemyslaw Czesnowicz","email":"przemyslaw.czesnowicz@intel.com","username":"pczesno"},"change_message_id":"eb484800da69ab064bba83bc07acf32bfca2d5b5","unresolved":false,"context_lines":[{"line_number":157,"context_line":""},{"line_number":158,"context_line":""},{"line_number":159,"context_line":"The second modification is to add optional parameter to"},{"line_number":160,"context_line":"attach network interface method."},{"line_number":161,"context_line":""},{"line_number":162,"context_line":"Method Type : POST"},{"line_number":163,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a961159_44024b0c","line":160,"in_reply_to":"3a961159_384569b3","updated":"2014-12-09 16:14:49.000000000","message":"I\u0027ll sync up with Yongli","commit_id":"dadf2a11f8ae72e2f07d2e2212798678302a8103"},{"author":{"_account_id":7543,"name":"Yongli He","email":"yongli.he@intel.com","username":"yongli.he"},"change_message_id":"0d0d29ace08d9cb9c19347a11543c8accb66edb7","unresolved":false,"context_lines":[{"line_number":10,"context_line":""},{"line_number":11,"context_line":"https://blueprints.launchpad.net/neutron/+spec/api-specify-vnic-type"},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"This specification proposes to extend the Nova v3 api to allow"},{"line_number":14,"context_line":"specifying vnic_type for nic\u0027s attached to the instance."},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"Problem description"}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a961159_52fac975","line":13,"updated":"2014-12-11 06:59:55.000000000","message":"does this conversion impact this feature?\nhttps://blueprints.launchpad.net/nova/+spec/v2-on-v3-api","commit_id":"c1e84fba66d8191c489b727d20dbcd8b5f10a11c"},{"author":{"_account_id":5754,"name":"Alex Xu","email":"hejie.xu@intel.com","username":"xuhj"},"change_message_id":"c6437fc486e345cb6feb5b07964b5a1c1ebe1b53","unresolved":false,"context_lines":[{"line_number":10,"context_line":""},{"line_number":11,"context_line":"https://blueprints.launchpad.net/neutron/+spec/api-specify-vnic-type"},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"This specification proposes to extend the Nova v3 api to allow"},{"line_number":14,"context_line":"specifying vnic_type for nic\u0027s attached to the instance."},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"Problem description"}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a961159_cd2d3e00","line":13,"in_reply_to":"3a961159_52fac975","updated":"2014-12-11 07:49:23.000000000","message":"we call v3 as v2.1 now. v2.1 already there. nothing impact.","commit_id":"c1e84fba66d8191c489b727d20dbcd8b5f10a11c"},{"author":{"_account_id":5754,"name":"Alex Xu","email":"hejie.xu@intel.com","username":"xuhj"},"change_message_id":"c6437fc486e345cb6feb5b07964b5a1c1ebe1b53","unresolved":false,"context_lines":[{"line_number":84,"context_line":""},{"line_number":85,"context_line":"Method Type : POST"},{"line_number":86,"context_line":""},{"line_number":87,"context_line":"URL : /v3/?{tenant_id}?/os_devices_boot"},{"line_number":88,"context_line":""},{"line_number":89,"context_line":"Description : Create server"},{"line_number":90,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a961159_cdc9be27","line":87,"updated":"2014-12-11 07:49:23.000000000","message":"just write \u0027/v2/....\u0027, v2.1 api also use \u0027v2\u0027 as prefix","commit_id":"c1e84fba66d8191c489b727d20dbcd8b5f10a11c"},{"author":{"_account_id":11647,"name":"Przemyslaw Czesnowicz","email":"przemyslaw.czesnowicz@intel.com","username":"pczesno"},"change_message_id":"5328db18bcc00ffedb19945132a3c890673aeaa8","unresolved":false,"context_lines":[{"line_number":84,"context_line":""},{"line_number":85,"context_line":"Method Type : POST"},{"line_number":86,"context_line":""},{"line_number":87,"context_line":"URL : /v3/?{tenant_id}?/os_devices_boot"},{"line_number":88,"context_line":""},{"line_number":89,"context_line":"Description : Create server"},{"line_number":90,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a961159_cb56fc29","line":87,"in_reply_to":"3a961159_cdc9be27","updated":"2014-12-11 14:19:51.000000000","message":"Done","commit_id":"c1e84fba66d8191c489b727d20dbcd8b5f10a11c"},{"author":{"_account_id":5754,"name":"Alex Xu","email":"hejie.xu@intel.com","username":"xuhj"},"change_message_id":"c6437fc486e345cb6feb5b07964b5a1c1ebe1b53","unresolved":false,"context_lines":[{"line_number":199,"context_line":""},{"line_number":200,"context_line":""},{"line_number":201,"context_line":"Primary assignee:"},{"line_number":202,"context_line":"\tpczesno"},{"line_number":203,"context_line":""},{"line_number":204,"context_line":""},{"line_number":205,"context_line":"Work Items"}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a961159_cd97feea","line":202,"updated":"2014-12-11 07:49:23.000000000","message":"there is \u0027tab\u0027, should use space stead of it.","commit_id":"c1e84fba66d8191c489b727d20dbcd8b5f10a11c"},{"author":{"_account_id":11647,"name":"Przemyslaw Czesnowicz","email":"przemyslaw.czesnowicz@intel.com","username":"pczesno"},"change_message_id":"5328db18bcc00ffedb19945132a3c890673aeaa8","unresolved":false,"context_lines":[{"line_number":199,"context_line":""},{"line_number":200,"context_line":""},{"line_number":201,"context_line":"Primary assignee:"},{"line_number":202,"context_line":"\tpczesno"},{"line_number":203,"context_line":""},{"line_number":204,"context_line":""},{"line_number":205,"context_line":"Work Items"}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a961159_2b3940f3","line":202,"in_reply_to":"3a961159_cd97feea","updated":"2014-12-11 14:19:51.000000000","message":"Done","commit_id":"c1e84fba66d8191c489b727d20dbcd8b5f10a11c"},{"author":{"_account_id":6598,"name":"Berezovsky Irena","email":"irenab.dev@gmail.com","username":"irenab"},"change_message_id":"b930522e647a42940b67352c28d2848207659a16","unresolved":false,"context_lines":[{"line_number":230,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":231,"context_line":""},{"line_number":232,"context_line":"* Setting default vnic_type for Neutron network"},{"line_number":233,"context_line":"  https://blueprints.launchpad.net/neutron/+spec/network-default-setting-ext"}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a961159_4bd04cc9","line":233,"updated":"2014-12-11 13:49:51.000000000","message":"please change the reference to this one\n https://blueprints.launchpad.net/openstack/?searchtext\u003dnetwork-settings-support-vnic-type","commit_id":"c1e84fba66d8191c489b727d20dbcd8b5f10a11c"},{"author":{"_account_id":11647,"name":"Przemyslaw Czesnowicz","email":"przemyslaw.czesnowicz@intel.com","username":"pczesno"},"change_message_id":"5328db18bcc00ffedb19945132a3c890673aeaa8","unresolved":false,"context_lines":[{"line_number":230,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":231,"context_line":""},{"line_number":232,"context_line":"* Setting default vnic_type for Neutron network"},{"line_number":233,"context_line":"  https://blueprints.launchpad.net/neutron/+spec/network-default-setting-ext"}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a961159_cb7fdca9","line":233,"in_reply_to":"3a961159_4bd04cc9","updated":"2014-12-11 14:19:51.000000000","message":"Done","commit_id":"c1e84fba66d8191c489b727d20dbcd8b5f10a11c"},{"author":{"_account_id":6598,"name":"Berezovsky Irena","email":"irenab.dev@gmail.com","username":"irenab"},"change_message_id":"8994e535a50125782f1bc415cf77d1e9c04b9533","unresolved":false,"context_lines":[{"line_number":8,"context_line":"Extend api to allow specifying vnic_type"},{"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\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/neutron/+spec/api-specify-vnic-type"},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"This specification proposes to extend the Nova v2.1 api to allow"},{"line_number":14,"context_line":"specifying vnic_type for nic\u0027s attached to the instance."}],"source_content_type":"text/x-rst","patch_set":5,"id":"3a961159_12557e4f","line":11,"updated":"2014-12-21 14:14:22.000000000","message":"Please update this link to point to the nova launchpad.","commit_id":"6c9ad1913418a33cb60a148f6625a721f5e1ba04"},{"author":{"_account_id":1779,"name":"Daniel Berrange","email":"berrange@redhat.com","username":"berrange"},"change_message_id":"1545a159fcf15c5eb732a96d33195cda09bece32","unresolved":false,"context_lines":[{"line_number":50,"context_line":"from the api. The setting vnic_type on a Neutron port will still be"},{"line_number":51,"context_line":"supported. In case when both api and Neutron port will have a vnic_type"},{"line_number":52,"context_line":"setting, the setting from api will take precedence."},{"line_number":53,"context_line":""},{"line_number":54,"context_line":"Alternatives"},{"line_number":55,"context_line":"------------"},{"line_number":56,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"3a961159_5a29cde4","line":53,"updated":"2014-12-12 13:57:48.000000000","message":"I\u0027m not really very comfortable with the idea of exposing vnic_type to the tenant user via the API or nova command line.\n\nI feel this is an internal implementation detail that tenants, at least, should never be exposed to when booting instances or attaching NICs to instances. I could perhaps see operators being exposed to it, but even then I think we should aim to avoid such a need.","commit_id":"6c9ad1913418a33cb60a148f6625a721f5e1ba04"},{"author":{"_account_id":6932,"name":"Adrian Hoban","email":"adrian.hoban@intel.com","username":"adrian-hoban"},"change_message_id":"1468e3e57fe967320b9b77325cd45f68fdcff025","unresolved":false,"context_lines":[{"line_number":50,"context_line":"from the api. The setting vnic_type on a Neutron port will still be"},{"line_number":51,"context_line":"supported. In case when both api and Neutron port will have a vnic_type"},{"line_number":52,"context_line":"setting, the setting from api will take precedence."},{"line_number":53,"context_line":""},{"line_number":54,"context_line":"Alternatives"},{"line_number":55,"context_line":"------------"},{"line_number":56,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"3a961159_5bcd4cb6","line":53,"in_reply_to":"3a961159_5a29cde4","updated":"2014-12-12 16:38:53.000000000","message":"The vnic_type is already exposed to the tenant via the Neutron API and as such this proposal does not aim to expose anything that could be considered new by the tenant. \n\nThere are network implications for the tenant if they use a direct or normal , vnic_type which why I think the Neutron community agreed to expose these at the API level. \n\nI think this proposal is really about helping to keep the Nova API in sync with the way this functionality has been agreed to in Neutron.","commit_id":"6c9ad1913418a33cb60a148f6625a721f5e1ba04"},{"author":{"_account_id":6598,"name":"Berezovsky Irena","email":"irenab.dev@gmail.com","username":"irenab"},"change_message_id":"2939640f188b34ac546acd95125db5fbd331f9bf","unresolved":false,"context_lines":[{"line_number":50,"context_line":"from the api. The setting vnic_type on a Neutron port will still be"},{"line_number":51,"context_line":"supported. In case when both api and Neutron port will have a vnic_type"},{"line_number":52,"context_line":"setting, the setting from api will take precedence."},{"line_number":53,"context_line":""},{"line_number":54,"context_line":"Alternatives"},{"line_number":55,"context_line":"------------"},{"line_number":56,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"3a961159_671410e9","line":53,"in_reply_to":"3a961159_5bcd4cb6","updated":"2014-12-14 15:53:03.000000000","message":"This proposal is about usability and simplified user experience. As it was discussed and agreed in neutron, vnic_type can be configured by network owner or admin. I think it is reasonable to follow the same policy in nova","commit_id":"6c9ad1913418a33cb60a148f6625a721f5e1ba04"},{"author":{"_account_id":1779,"name":"Daniel Berrange","email":"berrange@redhat.com","username":"berrange"},"change_message_id":"1545a159fcf15c5eb732a96d33195cda09bece32","unresolved":false,"context_lines":[{"line_number":59,"context_line":""},{"line_number":60,"context_line":"  This could mitigate the problem for networks that have the right vnic_type"},{"line_number":61,"context_line":"  set as default. But wouldn\u0027t help if the User had to override the default."},{"line_number":62,"context_line":""},{"line_number":63,"context_line":"* Using flavor extra_spec or image properties to store vnic_type."},{"line_number":64,"context_line":"  Both flavor and image approaches would be very inflexible as new"},{"line_number":65,"context_line":"  flavor or image would be needed to support different configurations"}],"source_content_type":"text/x-rst","patch_set":5,"id":"3a961159_7a6be91d","line":62,"updated":"2014-12-12 13:57:48.000000000","message":"I think this is a more compelling approach, because it only exposes the operator to this impl detail. I don\u0027t think tenant users should ever see this, so the fact that they can\u0027t override it with this approach is a positive to me.","commit_id":"6c9ad1913418a33cb60a148f6625a721f5e1ba04"},{"author":{"_account_id":11647,"name":"Przemyslaw Czesnowicz","email":"przemyslaw.czesnowicz@intel.com","username":"pczesno"},"change_message_id":"67547b20273b98e5ae0cecae394b5efe374c4e21","unresolved":false,"context_lines":[{"line_number":59,"context_line":""},{"line_number":60,"context_line":"  This could mitigate the problem for networks that have the right vnic_type"},{"line_number":61,"context_line":"  set as default. But wouldn\u0027t help if the User had to override the default."},{"line_number":62,"context_line":""},{"line_number":63,"context_line":"* Using flavor extra_spec or image properties to store vnic_type."},{"line_number":64,"context_line":"  Both flavor and image approaches would be very inflexible as new"},{"line_number":65,"context_line":"  flavor or image would be needed to support different configurations"}],"source_content_type":"text/x-rst","patch_set":5,"id":"3a961159_afad0aeb","line":62,"in_reply_to":"3a961159_7a6be91d","updated":"2014-12-12 17:47:25.000000000","message":"The bp above allows the tenant to set the vnic_type on the network level.\nIn a way it is a workaround for the fact that the tenant cannot set the vnic_type in nova api.","commit_id":"6c9ad1913418a33cb60a148f6625a721f5e1ba04"},{"author":{"_account_id":6598,"name":"Berezovsky Irena","email":"irenab.dev@gmail.com","username":"irenab"},"change_message_id":"2939640f188b34ac546acd95125db5fbd331f9bf","unresolved":false,"context_lines":[{"line_number":59,"context_line":""},{"line_number":60,"context_line":"  This could mitigate the problem for networks that have the right vnic_type"},{"line_number":61,"context_line":"  set as default. But wouldn\u0027t help if the User had to override the default."},{"line_number":62,"context_line":""},{"line_number":63,"context_line":"* Using flavor extra_spec or image properties to store vnic_type."},{"line_number":64,"context_line":"  Both flavor and image approaches would be very inflexible as new"},{"line_number":65,"context_line":"  flavor or image would be needed to support different configurations"}],"source_content_type":"text/x-rst","patch_set":5,"id":"3a961159_87d65c26","line":62,"in_reply_to":"3a961159_afad0aeb","updated":"2014-12-14 15:53:03.000000000","message":"And the above bp does not solve the case when different vnic_type should be supported on the same network","commit_id":"6c9ad1913418a33cb60a148f6625a721f5e1ba04"},{"author":{"_account_id":2750,"name":"Sean Dague","email":"sean@dague.net","username":"sdague"},"change_message_id":"61f403233f198d0231f520044f91ea369cb2627a","unresolved":false,"context_lines":[{"line_number":60,"context_line":"  This could mitigate the problem for networks that have the right vnic_type"},{"line_number":61,"context_line":"  set as default. But wouldn\u0027t help if the User had to override the default."},{"line_number":62,"context_line":""},{"line_number":63,"context_line":"* Using flavor extra_spec or image properties to store vnic_type."},{"line_number":64,"context_line":"  Both flavor and image approaches would be very inflexible as new"},{"line_number":65,"context_line":"  flavor or image would be needed to support different configurations"},{"line_number":66,"context_line":"  (i.e first nic uses direct and the second normal)"}],"source_content_type":"text/x-rst","patch_set":5,"id":"3a961159_74adc0e8","line":63,"updated":"2014-12-12 12:44:06.000000000","message":"Honestly, using flavors specs seems far more natural here. Exposing an API to the use to set this seems extremely odd.","commit_id":"6c9ad1913418a33cb60a148f6625a721f5e1ba04"},{"author":{"_account_id":6932,"name":"Adrian Hoban","email":"adrian.hoban@intel.com","username":"adrian-hoban"},"change_message_id":"1468e3e57fe967320b9b77325cd45f68fdcff025","unresolved":false,"context_lines":[{"line_number":60,"context_line":"  This could mitigate the problem for networks that have the right vnic_type"},{"line_number":61,"context_line":"  set as default. But wouldn\u0027t help if the User had to override the default."},{"line_number":62,"context_line":""},{"line_number":63,"context_line":"* Using flavor extra_spec or image properties to store vnic_type."},{"line_number":64,"context_line":"  Both flavor and image approaches would be very inflexible as new"},{"line_number":65,"context_line":"  flavor or image would be needed to support different configurations"},{"line_number":66,"context_line":"  (i.e first nic uses direct and the second normal)"}],"source_content_type":"text/x-rst","patch_set":5,"id":"3a961159_3b824000","line":63,"in_reply_to":"3a961159_3aaec198","updated":"2014-12-12 16:38:53.000000000","message":"Similar to my previous comment, the vnic_type is already exposed at the API. It just happens to be in Neutron API.\n\nAt some point, there may be a need for another change that allows the admin to apply a quota to the usage of direct or macvtap VNIC types, or perhaps the ability to disallow some or all tenants from using this capability, but I think that\u0027s a different work item.","commit_id":"6c9ad1913418a33cb60a148f6625a721f5e1ba04"},{"author":{"_account_id":6598,"name":"Berezovsky Irena","email":"irenab.dev@gmail.com","username":"irenab"},"change_message_id":"2939640f188b34ac546acd95125db5fbd331f9bf","unresolved":false,"context_lines":[{"line_number":60,"context_line":"  This could mitigate the problem for networks that have the right vnic_type"},{"line_number":61,"context_line":"  set as default. But wouldn\u0027t help if the User had to override the default."},{"line_number":62,"context_line":""},{"line_number":63,"context_line":"* Using flavor extra_spec or image properties to store vnic_type."},{"line_number":64,"context_line":"  Both flavor and image approaches would be very inflexible as new"},{"line_number":65,"context_line":"  flavor or image would be needed to support different configurations"},{"line_number":66,"context_line":"  (i.e first nic uses direct and the second normal)"}],"source_content_type":"text/x-rst","patch_set":5,"id":"3a961159_a7d99858","line":63,"in_reply_to":"3a961159_3b824000","updated":"2014-12-14 15:53:03.000000000","message":"vnic_type is an attribute of certain VM attachment to certain network. Do you think that flavor specs is a right way to deal with it?","commit_id":"6c9ad1913418a33cb60a148f6625a721f5e1ba04"},{"author":{"_account_id":11647,"name":"Przemyslaw Czesnowicz","email":"przemyslaw.czesnowicz@intel.com","username":"pczesno"},"change_message_id":"ef03a69079eef8e70db3affa1cf53739e99ca05c","unresolved":false,"context_lines":[{"line_number":60,"context_line":"  This could mitigate the problem for networks that have the right vnic_type"},{"line_number":61,"context_line":"  set as default. But wouldn\u0027t help if the User had to override the default."},{"line_number":62,"context_line":""},{"line_number":63,"context_line":"* Using flavor extra_spec or image properties to store vnic_type."},{"line_number":64,"context_line":"  Both flavor and image approaches would be very inflexible as new"},{"line_number":65,"context_line":"  flavor or image would be needed to support different configurations"},{"line_number":66,"context_line":"  (i.e first nic uses direct and the second normal)"}],"source_content_type":"text/x-rst","patch_set":5,"id":"3a961159_3aaec198","line":63,"in_reply_to":"3a961159_74adc0e8","updated":"2014-12-12 13:49:17.000000000","message":"I think using flavor extra specs would be even worse for the user  then what we have currently. Modification of flavor requires admin permissions. Currently users can  boot VM\u0027s with SRIOV port without requiring admin permissions. If we went the flavor extra spec route it would have little value.\n\nI think passing vnic_type is similar to passing bus\u003dlxc in nova boot --block-device","commit_id":"6c9ad1913418a33cb60a148f6625a721f5e1ba04"}],"specs/liberty/approved/api-specify-vnic-type.rst":[{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"92ed29a6f8cfc9241520b557f3de1d4fb18afc4f","unresolved":false,"context_lines":[{"line_number":208,"context_line":"* Implement api changes to support specifying vnic_type."},{"line_number":209,"context_line":"* Implement changes in Nova to build pci_request when \"direct\" or"},{"line_number":210,"context_line":"  \"macvtap\" vnic_type is passed from api"},{"line_number":211,"context_line":"* Implement changes in python-novaclient to use new api options."},{"line_number":212,"context_line":""},{"line_number":213,"context_line":"Dependencies"},{"line_number":214,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":7,"id":"3afb71cf_defe906a","line":211,"updated":"2015-06-08 13:44:58.000000000","message":"if vnic_type mapped to an abstract \"fast\" vs \"slow\" concept owned by neutron, and used when creating neutron ports, I think I would be happy with this addition, as its very close to what we do with volumes and the volume_type.\n\nBut in its current form its really expose implementation details to the users, which I really don\u0027t like, as that is not what our API is meant to be.","commit_id":"80fd3e9cdcdcdb71b776c5aced10b42280be8862"}]}