)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"7dc66d8c7bb55200f028c97780b66bce22d1fdb8","unresolved":false,"context_lines":[{"line_number":10,"context_line":"provided by multiple physical NICs. A basic setup is a VM with multiple"},{"line_number":11,"context_line":"passthrough Virtual Funtions (VFs) that are backed by different"},{"line_number":12,"context_line":"Physical Funtions (PFs)."},{"line_number":13,"context_line":""},{"line_number":14,"context_line":"Change-Id: I52dfe87cf8cbffdeac559eac064ce41c13ce3fc1"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"3f79a3b5_1076b10c","line":13,"updated":"2018-12-19 00:25:24.000000000","message":"Add:\n\nSpec for blueprint sriov-bond","commit_id":"7a7f34a90181fa1807a459ac0863cc0355cca53b"},{"author":{"_account_id":30156,"name":"Igor D.C.","email":"igor.duarte.cardoso@intel.com","username":"igordc"},"change_message_id":"71e43f77e1cd998baaa81372c9eb0f0a857f27a0","unresolved":false,"context_lines":[{"line_number":8,"context_line":""},{"line_number":9,"context_line":"In NFV scenario, it is desirable to have redundant network connectivity"},{"line_number":10,"context_line":"provided by multiple physical NICs. A basic setup is a VM with multiple"},{"line_number":11,"context_line":"passthrough Virtual Funtions (VFs) that are backed by different"},{"line_number":12,"context_line":"Physical Funtions (PFs)."},{"line_number":13,"context_line":""},{"line_number":14,"context_line":"Implements: blueprint sriov-bond"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":8,"id":"3fce034c_e67ca9ec","line":11,"range":{"start_line":11,"start_character":20,"end_line":11,"end_character":28},"updated":"2019-04-17 18:54:39.000000000","message":"Functions","commit_id":"2faf62bf87f1ef7bd268e0fef37e3887a47da16f"},{"author":{"_account_id":30156,"name":"Igor D.C.","email":"igor.duarte.cardoso@intel.com","username":"igordc"},"change_message_id":"71e43f77e1cd998baaa81372c9eb0f0a857f27a0","unresolved":false,"context_lines":[{"line_number":9,"context_line":"In NFV scenario, it is desirable to have redundant network connectivity"},{"line_number":10,"context_line":"provided by multiple physical NICs. A basic setup is a VM with multiple"},{"line_number":11,"context_line":"passthrough Virtual Funtions (VFs) that are backed by different"},{"line_number":12,"context_line":"Physical Funtions (PFs)."},{"line_number":13,"context_line":""},{"line_number":14,"context_line":"Implements: blueprint sriov-bond"},{"line_number":15,"context_line":"Change-Id: I52dfe87cf8cbffdeac559eac064ce41c13ce3fc1"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":8,"id":"3fce034c_868365cc","line":12,"range":{"start_line":12,"start_character":9,"end_line":12,"end_character":17},"updated":"2019-04-17 18:54:39.000000000","message":"Functions","commit_id":"2faf62bf87f1ef7bd268e0fef37e3887a47da16f"}],"specs/stein/approved/schedule-vm-nics-to-different-pf.rst":[{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"7dc66d8c7bb55200f028c97780b66bce22d1fdb8","unresolved":false,"context_lines":[{"line_number":1,"context_line":".."},{"line_number":2,"context_line":" This work is licensed under a Creative Commons Attribution 3.0 Unported"},{"line_number":3,"context_line":" License."},{"line_number":4,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"3f79a3b5_9061613f","line":1,"updated":"2018-12-19 00:25:24.000000000","message":"The spec filename should match the blueprint name, so sriov-bond.rst.","commit_id":"7a7f34a90181fa1807a459ac0863cc0355cca53b"}],"specs/stein/approved/sriov-bond.rst":[{"author":{"_account_id":7730,"name":"Sahid Orentino Ferdjaoui","email":"sahid.ferdjaoui@industrialdiscipline.com","username":"sahid"},"change_message_id":"c0d61f2f73c5be54a8346e60cf8bbc8b2c72ccef","unresolved":false,"context_lines":[{"line_number":106,"context_line":"The first spec proposes to extend the ``passthrough_whitelist`` config option to"},{"line_number":107,"context_line":"group the VFs based on its PFs/NICs/Switch. The second spec also proposes a"},{"line_number":108,"context_line":"config-based approach to group the PCI devices."},{"line_number":109,"context_line":"In comparison, this spec proposes to use ``binding:profile`` in Neutron port"},{"line_number":110,"context_line":"to group the PCI devices, which is user-configurable and flexible."},{"line_number":111,"context_line":""},{"line_number":112,"context_line":"Data model impact"},{"line_number":113,"context_line":"-----------------"}],"source_content_type":"text/x-rst","patch_set":4,"id":"3f79a3b5_f3f4278c","line":110,"range":{"start_line":109,"start_character":0,"end_line":110,"end_character":66},"updated":"2018-12-21 10:17:17.000000000","message":"An other alternative instead of creating a new anti-affinity thing is to use physical network. Basically we could just pass the phynet to the binding profile, so it means we have to update devspec.py to accept matching by physical_network as-well as other tags.\n\nBut that means the operators will have to share names of physical network attached to the devices. Not sure whether that can be considered for security.","commit_id":"c3b3a96e630189d64b32a8c7b3b3ea726a407c7e"},{"author":{"_account_id":27654,"name":"Hongbin Lu","email":"kira034@163.com","username":"hongbin.lu"},"change_message_id":"55f5d2290e63e984fcd64393bb776eeef6888910","unresolved":false,"context_lines":[{"line_number":106,"context_line":"The first spec proposes to extend the ``passthrough_whitelist`` config option to"},{"line_number":107,"context_line":"group the VFs based on its PFs/NICs/Switch. The second spec also proposes a"},{"line_number":108,"context_line":"config-based approach to group the PCI devices."},{"line_number":109,"context_line":"In comparison, this spec proposes to use ``binding:profile`` in Neutron port"},{"line_number":110,"context_line":"to group the PCI devices, which is user-configurable and flexible."},{"line_number":111,"context_line":""},{"line_number":112,"context_line":"Data model impact"},{"line_number":113,"context_line":"-----------------"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1f769fc5_13e64cea","line":110,"range":{"start_line":109,"start_character":0,"end_line":110,"end_character":66},"in_reply_to":"3f79a3b5_f3f4278c","updated":"2018-12-22 00:07:21.000000000","message":"Added this option as an alternative.","commit_id":"c3b3a96e630189d64b32a8c7b3b3ea726a407c7e"},{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"e32d0aaed024e2cf0fd08eefaf17d5048c4c1e71","unresolved":false,"context_lines":[{"line_number":15,"context_line":"passthrough Virtual Funtions (VFs) that are backed by different"},{"line_number":16,"context_line":"Physical Funtions (PFs). Normally, users will configure bonding in the VM,"},{"line_number":17,"context_line":"which aggregates the two NICs into a single logical NIC so that"},{"line_number":18,"context_line":"the network is resilience to failure on any of the PFs."},{"line_number":19,"context_line":""},{"line_number":20,"context_line":"To enable these use cases, Nova needs to be able to find a host that"},{"line_number":21,"context_line":"has sufficient number of VFs to filfull the requirement of the VM and"}],"source_content_type":"text/x-rst","patch_set":6,"id":"1f769fc5_aa8a3718","line":18,"range":{"start_line":18,"start_character":15,"end_line":18,"end_character":25},"updated":"2019-01-02 14:17:15.000000000","message":"resilient","commit_id":"694f7f13aaf80fdd157710b6b85102cc19f4638e"},{"author":{"_account_id":27654,"name":"Hongbin Lu","email":"kira034@163.com","username":"hongbin.lu"},"change_message_id":"19501ad4050f12b86dc0ee525080ee72548c24e7","unresolved":false,"context_lines":[{"line_number":15,"context_line":"passthrough Virtual Funtions (VFs) that are backed by different"},{"line_number":16,"context_line":"Physical Funtions (PFs). Normally, users will configure bonding in the VM,"},{"line_number":17,"context_line":"which aggregates the two NICs into a single logical NIC so that"},{"line_number":18,"context_line":"the network is resilience to failure on any of the PFs."},{"line_number":19,"context_line":""},{"line_number":20,"context_line":"To enable these use cases, Nova needs to be able to find a host that"},{"line_number":21,"context_line":"has sufficient number of VFs to filfull the requirement of the VM and"}],"source_content_type":"text/x-rst","patch_set":6,"id":"dfd5e7cf_a494a545","line":18,"range":{"start_line":18,"start_character":15,"end_line":18,"end_character":25},"in_reply_to":"1f769fc5_aa8a3718","updated":"2019-01-09 00:08:02.000000000","message":"Done","commit_id":"694f7f13aaf80fdd157710b6b85102cc19f4638e"},{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"e32d0aaed024e2cf0fd08eefaf17d5048c4c1e71","unresolved":false,"context_lines":[{"line_number":83,"context_line":""},{"line_number":84,"context_line":"4. After the VM is created, users login to the VM and configure the bonding."},{"line_number":85,"context_line":""},{"line_number":86,"context_line":"Under the hook, Nova will call Neutron API to detect the anti-affinity"},{"line_number":87,"context_line":"between those two ports and pass that information to the scheduler."},{"line_number":88,"context_line":"The scheduler will schedule the VM based on the request and"},{"line_number":89,"context_line":"the PCI device information reported by each compute host."}],"source_content_type":"text/x-rst","patch_set":6,"id":"1f769fc5_0a732b4f","line":86,"range":{"start_line":86,"start_character":10,"end_line":86,"end_character":14},"updated":"2019-01-02 14:17:15.000000000","message":"hood","commit_id":"694f7f13aaf80fdd157710b6b85102cc19f4638e"},{"author":{"_account_id":27654,"name":"Hongbin Lu","email":"kira034@163.com","username":"hongbin.lu"},"change_message_id":"19501ad4050f12b86dc0ee525080ee72548c24e7","unresolved":false,"context_lines":[{"line_number":83,"context_line":""},{"line_number":84,"context_line":"4. After the VM is created, users login to the VM and configure the bonding."},{"line_number":85,"context_line":""},{"line_number":86,"context_line":"Under the hook, Nova will call Neutron API to detect the anti-affinity"},{"line_number":87,"context_line":"between those two ports and pass that information to the scheduler."},{"line_number":88,"context_line":"The scheduler will schedule the VM based on the request and"},{"line_number":89,"context_line":"the PCI device information reported by each compute host."}],"source_content_type":"text/x-rst","patch_set":6,"id":"dfd5e7cf_c491a954","line":86,"range":{"start_line":86,"start_character":10,"end_line":86,"end_character":14},"in_reply_to":"1f769fc5_0a732b4f","updated":"2019-01-09 00:08:02.000000000","message":"Done","commit_id":"694f7f13aaf80fdd157710b6b85102cc19f4638e"},{"author":{"_account_id":30156,"name":"Igor D.C.","email":"igor.duarte.cardoso@intel.com","username":"igordc"},"change_message_id":"71e43f77e1cd998baaa81372c9eb0f0a857f27a0","unresolved":false,"context_lines":[{"line_number":12,"context_line":""},{"line_number":13,"context_line":"In NFV scenario, it is desirable to have redundant network connectivity"},{"line_number":14,"context_line":"provided by more than one physical NICs. A basic setup is a VM with two"},{"line_number":15,"context_line":"passthrough Virtual Funtions (VFs) that are backed by different"},{"line_number":16,"context_line":"Physical Funtions (PFs). Normally, users will configure bonding in the VM,"},{"line_number":17,"context_line":"which aggregates the two NICs into a single logical NIC so that"},{"line_number":18,"context_line":"the network is resilient to failure on any of the PFs."}],"source_content_type":"text/x-rst","patch_set":8,"id":"3fce034c_a686a1da","line":15,"range":{"start_line":15,"start_character":20,"end_line":15,"end_character":28},"updated":"2019-04-17 18:54:39.000000000","message":"ditto","commit_id":"2faf62bf87f1ef7bd268e0fef37e3887a47da16f"},{"author":{"_account_id":30156,"name":"Igor D.C.","email":"igor.duarte.cardoso@intel.com","username":"igordc"},"change_message_id":"71e43f77e1cd998baaa81372c9eb0f0a857f27a0","unresolved":false,"context_lines":[{"line_number":13,"context_line":"In NFV scenario, it is desirable to have redundant network connectivity"},{"line_number":14,"context_line":"provided by more than one physical NICs. A basic setup is a VM with two"},{"line_number":15,"context_line":"passthrough Virtual Funtions (VFs) that are backed by different"},{"line_number":16,"context_line":"Physical Funtions (PFs). Normally, users will configure bonding in the VM,"},{"line_number":17,"context_line":"which aggregates the two NICs into a single logical NIC so that"},{"line_number":18,"context_line":"the network is resilient to failure on any of the PFs."},{"line_number":19,"context_line":""}],"source_content_type":"text/x-rst","patch_set":8,"id":"3fce034c_466d7d30","line":16,"range":{"start_line":16,"start_character":9,"end_line":16,"end_character":17},"updated":"2019-04-17 18:54:39.000000000","message":"ditto","commit_id":"2faf62bf87f1ef7bd268e0fef37e3887a47da16f"},{"author":{"_account_id":30156,"name":"Igor D.C.","email":"igor.duarte.cardoso@intel.com","username":"igordc"},"change_message_id":"71e43f77e1cd998baaa81372c9eb0f0a857f27a0","unresolved":false,"context_lines":[{"line_number":21,"context_line":"has sufficient number of VFs to filfull the requirement of the VM and"},{"line_number":22,"context_line":"ensure the selected VFs don\u0027t share the same PF."},{"line_number":23,"context_line":"The anti-affinity relationship between VFs is modeled by Neutron ports and"},{"line_number":24,"context_line":"users can leverage Neutron API to create or mutate this relationship."},{"line_number":25,"context_line":"During scheduling of VM, Nova will retrieve anti-affinity relationship"},{"line_number":26,"context_line":"from Neutron and feed the information into the scheduler, and the scheduler"},{"line_number":27,"context_line":"will place the VM to the right host. After the VM successfully boots,"}],"source_content_type":"text/x-rst","patch_set":8,"id":"3fce034c_e6658946","line":24,"range":{"start_line":24,"start_character":0,"end_line":24,"end_character":69},"updated":"2019-04-17 18:54:39.000000000","message":"+1","commit_id":"2faf62bf87f1ef7bd268e0fef37e3887a47da16f"},{"author":{"_account_id":30156,"name":"Igor D.C.","email":"igor.duarte.cardoso@intel.com","username":"igordc"},"change_message_id":"71e43f77e1cd998baaa81372c9eb0f0a857f27a0","unresolved":false,"context_lines":[{"line_number":25,"context_line":"During scheduling of VM, Nova will retrieve anti-affinity relationship"},{"line_number":26,"context_line":"from Neutron and feed the information into the scheduler, and the scheduler"},{"line_number":27,"context_line":"will place the VM to the right host. After the VM successfully boots,"},{"line_number":28,"context_line":"users can login to the VM and configure the SR-IOV bonding but this is not"},{"line_number":29,"context_line":"part of the Nova\u0027s responsibility."},{"line_number":30,"context_line":""},{"line_number":31,"context_line":"Problem description"},{"line_number":32,"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":8,"id":"3fce034c_865cc57e","line":29,"range":{"start_line":28,"start_character":10,"end_line":29,"end_character":33},"updated":"2019-04-17 18:54:39.000000000","message":"+1","commit_id":"2faf62bf87f1ef7bd268e0fef37e3887a47da16f"},{"author":{"_account_id":30156,"name":"Igor D.C.","email":"igor.duarte.cardoso@intel.com","username":"igordc"},"change_message_id":"71e43f77e1cd998baaa81372c9eb0f0a857f27a0","unresolved":false,"context_lines":[{"line_number":45,"context_line":"Use Cases"},{"line_number":46,"context_line":"---------"},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"NFV scenario that have strict requirement on network availability"},{"line_number":49,"context_line":"requires a VM to have two virtual NICs that belong to two physical NICs"},{"line_number":50,"context_line":"so that if one NIC fails, the VM can switch over to another NIC."},{"line_number":51,"context_line":""}],"source_content_type":"text/x-rst","patch_set":8,"id":"3fce034c_86d125d0","line":48,"range":{"start_line":48,"start_character":30,"end_line":48,"end_character":41},"updated":"2019-04-17 18:54:39.000000000","message":"requirements","commit_id":"2faf62bf87f1ef7bd268e0fef37e3887a47da16f"},{"author":{"_account_id":30156,"name":"Igor D.C.","email":"igor.duarte.cardoso@intel.com","username":"igordc"},"change_message_id":"71e43f77e1cd998baaa81372c9eb0f0a857f27a0","unresolved":false,"context_lines":[{"line_number":45,"context_line":"Use Cases"},{"line_number":46,"context_line":"---------"},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"NFV scenario that have strict requirement on network availability"},{"line_number":49,"context_line":"requires a VM to have two virtual NICs that belong to two physical NICs"},{"line_number":50,"context_line":"so that if one NIC fails, the VM can switch over to another NIC."},{"line_number":51,"context_line":""}],"source_content_type":"text/x-rst","patch_set":8,"id":"3fce034c_e6ca6918","line":48,"range":{"start_line":48,"start_character":4,"end_line":48,"end_character":12},"updated":"2019-04-17 18:54:39.000000000","message":"scenarios","commit_id":"2faf62bf87f1ef7bd268e0fef37e3887a47da16f"},{"author":{"_account_id":30156,"name":"Igor D.C.","email":"igor.duarte.cardoso@intel.com","username":"igordc"},"change_message_id":"71e43f77e1cd998baaa81372c9eb0f0a857f27a0","unresolved":false,"context_lines":[{"line_number":53,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":54,"context_line":""},{"line_number":55,"context_line":"The proposed change involves Nova and Neutron. This spec focus on Nova\u0027s change"},{"line_number":56,"context_line":"and the Neutron change is covered by another spec. In overall, the required"},{"line_number":57,"context_line":"changes are as following:"},{"line_number":58,"context_line":""},{"line_number":59,"context_line":"1. Enhance Neutron\u0027s API to support anti-affinity relationship between ports."}],"source_content_type":"text/x-rst","patch_set":8,"id":"3fce034c_46db3dec","line":56,"range":{"start_line":56,"start_character":8,"end_line":56,"end_character":49},"updated":"2019-04-17 18:54:39.000000000","message":"Coming soon?\nAlso see my comments about \"bond\" Neutron port.","commit_id":"2faf62bf87f1ef7bd268e0fef37e3887a47da16f"},{"author":{"_account_id":30156,"name":"Igor D.C.","email":"igor.duarte.cardoso@intel.com","username":"igordc"},"change_message_id":"71e43f77e1cd998baaa81372c9eb0f0a857f27a0","unresolved":false,"context_lines":[{"line_number":53,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":54,"context_line":""},{"line_number":55,"context_line":"The proposed change involves Nova and Neutron. This spec focus on Nova\u0027s change"},{"line_number":56,"context_line":"and the Neutron change is covered by another spec. In overall, the required"},{"line_number":57,"context_line":"changes are as following:"},{"line_number":58,"context_line":""},{"line_number":59,"context_line":"1. Enhance Neutron\u0027s API to support anti-affinity relationship between ports."}],"source_content_type":"text/x-rst","patch_set":8,"id":"3fce034c_06e535a8","line":56,"range":{"start_line":56,"start_character":51,"end_line":56,"end_character":61},"updated":"2019-04-17 18:54:39.000000000","message":"Overall,","commit_id":"2faf62bf87f1ef7bd268e0fef37e3887a47da16f"},{"author":{"_account_id":30156,"name":"Igor D.C.","email":"igor.duarte.cardoso@intel.com","username":"igordc"},"change_message_id":"71e43f77e1cd998baaa81372c9eb0f0a857f27a0","unresolved":false,"context_lines":[{"line_number":58,"context_line":""},{"line_number":59,"context_line":"1. Enhance Neutron\u0027s API to support anti-affinity relationship between ports."},{"line_number":60,"context_line":"   In particular, the ``binding:profile`` attribute in the ``port`` resource"},{"line_number":61,"context_line":"   will have a new key called ``anti_affinity_group`` whose value is a string"},{"line_number":62,"context_line":"   that serves as a unique identifier of the group."},{"line_number":63,"context_line":""},{"line_number":64,"context_line":"2. Extend Nova scheduler to support placing VMs according to the anti-affinity"},{"line_number":65,"context_line":"   requirement specified in the Neutron ports. For example, if a VM has"}],"source_content_type":"text/x-rst","patch_set":8,"id":"3fce034c_46b25d96","line":62,"range":{"start_line":61,"start_character":2,"end_line":62,"end_character":51},"updated":"2019-04-17 18:54:39.000000000","message":"These groups are dynamically created right? So, without ever adding them anywhere, including to any configuration file, if I create port1 with anti_affinity_group\u003d\"superha\" and then I create port2 with anti_affinity_group\u003d\"superha\" as well, then I am guaranteed that port1 will land on one VF from PF X and port2 will land on one VF from PF Y?","commit_id":"2faf62bf87f1ef7bd268e0fef37e3887a47da16f"},{"author":{"_account_id":30156,"name":"Igor D.C.","email":"igor.duarte.cardoso@intel.com","username":"igordc"},"change_message_id":"71e43f77e1cd998baaa81372c9eb0f0a857f27a0","unresolved":false,"context_lines":[{"line_number":91,"context_line":"to different PFs will be removed from the list."},{"line_number":92,"context_line":"Similarly, during resource claiming, Nova will allocate VFs to the VM based on"},{"line_number":93,"context_line":"the anti-affinity of ports as well."},{"line_number":94,"context_line":"During VIFs pluging, Nova will configure the same MAC address for both NICs,"},{"line_number":95,"context_line":"which ensures the bond port will pass the potential spoof checking."},{"line_number":96,"context_line":""},{"line_number":97,"context_line":"Alternatives"}],"source_content_type":"text/x-rst","patch_set":8,"id":"3fce034c_8646057c","line":94,"range":{"start_line":94,"start_character":12,"end_line":94,"end_character":19},"updated":"2019-04-17 18:54:39.000000000","message":"plugging","commit_id":"2faf62bf87f1ef7bd268e0fef37e3887a47da16f"},{"author":{"_account_id":30156,"name":"Igor D.C.","email":"igor.duarte.cardoso@intel.com","username":"igordc"},"change_message_id":"71e43f77e1cd998baaa81372c9eb0f0a857f27a0","unresolved":false,"context_lines":[{"line_number":91,"context_line":"to different PFs will be removed from the list."},{"line_number":92,"context_line":"Similarly, during resource claiming, Nova will allocate VFs to the VM based on"},{"line_number":93,"context_line":"the anti-affinity of ports as well."},{"line_number":94,"context_line":"During VIFs pluging, Nova will configure the same MAC address for both NICs,"},{"line_number":95,"context_line":"which ensures the bond port will pass the potential spoof checking."},{"line_number":96,"context_line":""},{"line_number":97,"context_line":"Alternatives"},{"line_number":98,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":8,"id":"3fce034c_c6316d0d","line":95,"range":{"start_line":94,"start_character":45,"end_line":95,"end_character":67},"updated":"2019-04-17 18:54:39.000000000","message":"So the Neutron ports should also have the same MAC address right? In fact, I\u0027d say that single MAC address should come from Neutron.. but how will this work when a Neutron port is (unless something big has changed in Neutron in the past couple of years) associated with a unique MAC address?","commit_id":"2faf62bf87f1ef7bd268e0fef37e3887a47da16f"},{"author":{"_account_id":30156,"name":"Igor D.C.","email":"igor.duarte.cardoso@intel.com","username":"igordc"},"change_message_id":"71e43f77e1cd998baaa81372c9eb0f0a857f27a0","unresolved":false,"context_lines":[{"line_number":100,"context_line":"To the best of the author\u0027s knowledge, there are two alternative approach"},{"line_number":101,"context_line":"available:"},{"line_number":102,"context_line":""},{"line_number":103,"context_line":"1. User controlled SR-IOV ports allocation: https://review.openstack.org/#/c/463526/"},{"line_number":104,"context_line":"2. SR-IOV-bond: https://review.openstack.org/#/c/463526/"},{"line_number":105,"context_line":""},{"line_number":106,"context_line":"The first spec proposes to extend the ``passthrough_whitelist`` config option"}],"source_content_type":"text/x-rst","patch_set":8,"id":"3fce034c_dc9cddc1","line":103,"range":{"start_line":103,"start_character":0,"end_line":103,"end_character":84},"updated":"2019-04-17 18:54:39.000000000","message":"I do prefer the \"one neutron port\" approach for the guest bond in the linked spec. After all, the bond is a logical port and is thus supposed to have one MAC address. Consequently it makes sense that a Neutron port (also a logical construct from API perspective) reflects that by being a \"bond\" Neutron port and being associated to a unique MAC address like before.","commit_id":"2faf62bf87f1ef7bd268e0fef37e3887a47da16f"},{"author":{"_account_id":30156,"name":"Igor D.C.","email":"igor.duarte.cardoso@intel.com","username":"igordc"},"change_message_id":"71e43f77e1cd998baaa81372c9eb0f0a857f27a0","unresolved":false,"context_lines":[{"line_number":101,"context_line":"available:"},{"line_number":102,"context_line":""},{"line_number":103,"context_line":"1. User controlled SR-IOV ports allocation: https://review.openstack.org/#/c/463526/"},{"line_number":104,"context_line":"2. SR-IOV-bond: https://review.openstack.org/#/c/463526/"},{"line_number":105,"context_line":""},{"line_number":106,"context_line":"The first spec proposes to extend the ``passthrough_whitelist`` config option"},{"line_number":107,"context_line":"to group the VFs based on its PFs/NICs/Switch. The second spec also proposes a"}],"source_content_type":"text/x-rst","patch_set":8,"id":"3fce034c_5cb0ed43","line":104,"range":{"start_line":104,"start_character":0,"end_line":104,"end_character":56},"updated":"2019-04-17 18:54:39.000000000","message":"You have linked the same spec twice.","commit_id":"2faf62bf87f1ef7bd268e0fef37e3887a47da16f"},{"author":{"_account_id":30156,"name":"Igor D.C.","email":"igor.duarte.cardoso@intel.com","username":"igordc"},"change_message_id":"71e43f77e1cd998baaa81372c9eb0f0a857f27a0","unresolved":false,"context_lines":[{"line_number":103,"context_line":"1. User controlled SR-IOV ports allocation: https://review.openstack.org/#/c/463526/"},{"line_number":104,"context_line":"2. SR-IOV-bond: https://review.openstack.org/#/c/463526/"},{"line_number":105,"context_line":""},{"line_number":106,"context_line":"The first spec proposes to extend the ``passthrough_whitelist`` config option"},{"line_number":107,"context_line":"to group the VFs based on its PFs/NICs/Switch. The second spec also proposes a"},{"line_number":108,"context_line":"config-based approach to group the PCI devices."},{"line_number":109,"context_line":"In comparison, this spec proposes to use ``binding:profile`` in Neutron port"},{"line_number":110,"context_line":"to group the PCI devices, which is user-configurable and flexible."}],"source_content_type":"text/x-rst","patch_set":8,"id":"3fce034c_7cdb697b","line":107,"range":{"start_line":106,"start_character":0,"end_line":107,"end_character":46},"updated":"2019-04-17 18:54:39.000000000","message":"This first spec is missing from above.","commit_id":"2faf62bf87f1ef7bd268e0fef37e3887a47da16f"},{"author":{"_account_id":30156,"name":"Igor D.C.","email":"igor.duarte.cardoso@intel.com","username":"igordc"},"change_message_id":"71e43f77e1cd998baaa81372c9eb0f0a857f27a0","unresolved":false,"context_lines":[{"line_number":106,"context_line":"The first spec proposes to extend the ``passthrough_whitelist`` config option"},{"line_number":107,"context_line":"to group the VFs based on its PFs/NICs/Switch. The second spec also proposes a"},{"line_number":108,"context_line":"config-based approach to group the PCI devices."},{"line_number":109,"context_line":"In comparison, this spec proposes to use ``binding:profile`` in Neutron port"},{"line_number":110,"context_line":"to group the PCI devices, which is user-configurable and flexible."},{"line_number":111,"context_line":""},{"line_number":112,"context_line":"Another alternative is to implicitly decide anti-affinity of ports based on"},{"line_number":113,"context_line":"their physical network."}],"source_content_type":"text/x-rst","patch_set":8,"id":"3fce034c_1cbd8501","line":110,"range":{"start_line":109,"start_character":0,"end_line":110,"end_character":66},"updated":"2019-04-17 18:54:39.000000000","message":"Maybe add this to the end of the Alternatives section.","commit_id":"2faf62bf87f1ef7bd268e0fef37e3887a47da16f"},{"author":{"_account_id":30156,"name":"Igor D.C.","email":"igor.duarte.cardoso@intel.com","username":"igordc"},"change_message_id":"71e43f77e1cd998baaa81372c9eb0f0a857f27a0","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":8,"id":"3fce034c_7c49292f","line":203,"updated":"2019-04-17 18:54:39.000000000","message":"https://bugs.launchpad.net/neutron/+bug/1809037","commit_id":"2faf62bf87f1ef7bd268e0fef37e3887a47da16f"}]}