)]}'
{"specs/juno/ml2-ucs-manager-mechanism-driver.rst":[{"author":{"_account_id":490,"name":"Sumit Naiksatam","email":"sumitnaiksatam@gmail.com","username":"snaiksat"},"change_message_id":"7b48a137318b417202e4a21fd19710c4ef807451","unresolved":false,"context_lines":[{"line_number":5,"context_line":" http://creativecommons.org/licenses/by/3.0/legalcode"},{"line_number":6,"context_line":""},{"line_number":7,"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\u003d\u003d"},{"line_number":8,"context_line":"ML2 Mechanism Driver for Cisco UCS Manager"},{"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\u003d\u003d"},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"URL of your launchpad blueprint:"}],"source_content_type":"text/x-rst","patch_set":1,"id":"7adec928_e67967fd","line":8,"updated":"2014-05-23 18:59:28.000000000","message":"I feel a sense of deja vu! ;-)","commit_id":"99e500c69ed8a9f4e78c9d308ab2ebd9b0af5ecb"},{"author":{"_account_id":6697,"name":"Sandhya Dasu","email":"sandhya.openinfra@gmail.com","username":"sadasu"},"change_message_id":"92f7f07a5cd422fe45876e44822c176dc64721f8","unresolved":false,"context_lines":[{"line_number":5,"context_line":" http://creativecommons.org/licenses/by/3.0/legalcode"},{"line_number":6,"context_line":""},{"line_number":7,"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\u003d\u003d"},{"line_number":8,"context_line":"ML2 Mechanism Driver for Cisco UCS Manager"},{"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\u003d\u003d"},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"URL of your launchpad blueprint:"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3ae8d1ca_2bf53083","line":8,"in_reply_to":"7adec928_e67967fd","updated":"2014-05-30 18:43:12.000000000","message":"Yes :-) Your original plugin has taken on a diff avatar.","commit_id":"99e500c69ed8a9f4e78c9d308ab2ebd9b0af5ecb"},{"author":{"_account_id":490,"name":"Sumit Naiksatam","email":"sumitnaiksatam@gmail.com","username":"snaiksat"},"change_message_id":"7b48a137318b417202e4a21fd19710c4ef807451","unresolved":false,"context_lines":[{"line_number":14,"context_line":""},{"line_number":15,"context_line":"The purpose of this blueprint is to add support for Cisco UCS Manager into"},{"line_number":16,"context_line":"Openstack Neutron. This plugin for Cisco UCS Manager is implemented as a ML2"},{"line_number":17,"context_line":"plugin."},{"line_number":18,"context_line":""},{"line_number":19,"context_line":"Problem description"},{"line_number":20,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":1,"id":"7adec928_663f1726","line":17,"updated":"2014-05-23 18:59:28.000000000","message":"nit: plugin -\u003e mech driver?","commit_id":"99e500c69ed8a9f4e78c9d308ab2ebd9b0af5ecb"},{"author":{"_account_id":6697,"name":"Sandhya Dasu","email":"sandhya.openinfra@gmail.com","username":"sadasu"},"change_message_id":"92f7f07a5cd422fe45876e44822c176dc64721f8","unresolved":false,"context_lines":[{"line_number":14,"context_line":""},{"line_number":15,"context_line":"The purpose of this blueprint is to add support for Cisco UCS Manager into"},{"line_number":16,"context_line":"Openstack Neutron. This plugin for Cisco UCS Manager is implemented as a ML2"},{"line_number":17,"context_line":"plugin."},{"line_number":18,"context_line":""},{"line_number":19,"context_line":"Problem description"},{"line_number":20,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3ae8d1ca_6bef38b1","line":17,"in_reply_to":"7adec928_663f1726","updated":"2014-05-30 18:43:12.000000000","message":"Done","commit_id":"99e500c69ed8a9f4e78c9d308ab2ebd9b0af5ecb"},{"author":{"_account_id":490,"name":"Sumit Naiksatam","email":"sumitnaiksatam@gmail.com","username":"snaiksat"},"change_message_id":"7b48a137318b417202e4a21fd19710c4ef807451","unresolved":false,"context_lines":[{"line_number":21,"context_line":""},{"line_number":22,"context_line":"A detailed description of the problem:"},{"line_number":23,"context_line":""},{"line_number":24,"context_line":"1. Initially this mechanism driver will be used to configure Cisco Vm-Fex on"},{"line_number":25,"context_line":"   specific Cisco NICs while maintianing port profiles for these virtual"},{"line_number":26,"context_line":"   functions(VFs) on the UCS Manager."},{"line_number":27,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"7adec928_e6188786","line":24,"updated":"2014-05-23 18:59:28.000000000","message":"It might be a good idea to put a reference to VM-FEX here (to aid reviewers who may not be familiar).","commit_id":"99e500c69ed8a9f4e78c9d308ab2ebd9b0af5ecb"},{"author":{"_account_id":6697,"name":"Sandhya Dasu","email":"sandhya.openinfra@gmail.com","username":"sadasu"},"change_message_id":"92f7f07a5cd422fe45876e44822c176dc64721f8","unresolved":false,"context_lines":[{"line_number":21,"context_line":""},{"line_number":22,"context_line":"A detailed description of the problem:"},{"line_number":23,"context_line":""},{"line_number":24,"context_line":"1. Initially this mechanism driver will be used to configure Cisco Vm-Fex on"},{"line_number":25,"context_line":"   specific Cisco NICs while maintianing port profiles for these virtual"},{"line_number":26,"context_line":"   functions(VFs) on the UCS Manager."},{"line_number":27,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"3ae8d1ca_a994e837","line":24,"in_reply_to":"5adbc538_1cee0ced","updated":"2014-05-30 18:43:12.000000000","message":"Done","commit_id":"99e500c69ed8a9f4e78c9d308ab2ebd9b0af5ecb"},{"author":{"_account_id":6558,"name":"Sukhdev Kapur","email":"sukhdevkapur@gmail.com","username":"sukhdev-8"},"change_message_id":"efe5c5dfeeee54e18909e507e1aec2ec6b0ff3b2","unresolved":false,"context_lines":[{"line_number":21,"context_line":""},{"line_number":22,"context_line":"A detailed description of the problem:"},{"line_number":23,"context_line":""},{"line_number":24,"context_line":"1. Initially this mechanism driver will be used to configure Cisco Vm-Fex on"},{"line_number":25,"context_line":"   specific Cisco NICs while maintianing port profiles for these virtual"},{"line_number":26,"context_line":"   functions(VFs) on the UCS Manager."},{"line_number":27,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5adbc538_1cee0ced","line":24,"in_reply_to":"7adec928_e6188786","updated":"2014-05-25 18:00:21.000000000","message":"Agree...this will help some of us understand the context","commit_id":"99e500c69ed8a9f4e78c9d308ab2ebd9b0af5ecb"},{"author":{"_account_id":6697,"name":"Sandhya Dasu","email":"sandhya.openinfra@gmail.com","username":"sadasu"},"change_message_id":"92f7f07a5cd422fe45876e44822c176dc64721f8","unresolved":false,"context_lines":[{"line_number":21,"context_line":""},{"line_number":22,"context_line":"A detailed description of the problem:"},{"line_number":23,"context_line":""},{"line_number":24,"context_line":"1. Initially this mechanism driver will be used to configure Cisco Vm-Fex on"},{"line_number":25,"context_line":"   specific Cisco NICs while maintianing port profiles for these virtual"},{"line_number":26,"context_line":"   functions(VFs) on the UCS Manager."},{"line_number":27,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"3ae8d1ca_49760440","line":24,"in_reply_to":"7adec928_e6188786","updated":"2014-05-30 18:43:12.000000000","message":"Done","commit_id":"99e500c69ed8a9f4e78c9d308ab2ebd9b0af5ecb"},{"author":{"_account_id":6685,"name":"Baodong (Robert) Li","email":"baoli@cisco.com","username":"baoli"},"change_message_id":"00331f4e579bd66d87a7c7e9bebf62b126004487","unresolved":false,"context_lines":[{"line_number":33,"context_line":"   specific Cisco and Intel NICs (without using port profiles)."},{"line_number":34,"context_line":""},{"line_number":35,"context_line":"The ML2 based mechanism driver will interact with Cisco UCS Manager via"},{"line_number":36,"context_line":"UCS specific Python SDK."},{"line_number":37,"context_line":""},{"line_number":38,"context_line":"Proposed change"},{"line_number":39,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3ae8d1ca_5a613d38","line":36,"updated":"2014-05-28 15:04:55.000000000","message":"The above reads more like functionality statement. Can we approach it by describing what VMFEX and HWVEB are,  and the role of port profile/vlan, as well as the need of this info from nova?","commit_id":"99e500c69ed8a9f4e78c9d308ab2ebd9b0af5ecb"},{"author":{"_account_id":107,"name":"Arvind Somya","email":"arvind.somya@gmail.com","username":"asomya"},"change_message_id":"519380388ee8f685a174b2ddc063d98879d749f5","unresolved":false,"context_lines":[{"line_number":33,"context_line":"   specific Cisco and Intel NICs (without using port profiles)."},{"line_number":34,"context_line":""},{"line_number":35,"context_line":"The ML2 based mechanism driver will interact with Cisco UCS Manager via"},{"line_number":36,"context_line":"UCS specific Python SDK."},{"line_number":37,"context_line":""},{"line_number":38,"context_line":"Proposed change"},{"line_number":39,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3ae8d1ca_f3eda426","line":36,"in_reply_to":"3ae8d1ca_5a613d38","updated":"2014-05-29 17:56:23.000000000","message":"Agreed, the aforementioned section sounds like a function spec of the solution not the problem. Can you outline the problem i.e. why we need SRIOV and VMFex? Additionally i think this whole block belongs in the proposed change section.","commit_id":"99e500c69ed8a9f4e78c9d308ab2ebd9b0af5ecb"},{"author":{"_account_id":6697,"name":"Sandhya Dasu","email":"sandhya.openinfra@gmail.com","username":"sadasu"},"change_message_id":"92f7f07a5cd422fe45876e44822c176dc64721f8","unresolved":false,"context_lines":[{"line_number":33,"context_line":"   specific Cisco and Intel NICs (without using port profiles)."},{"line_number":34,"context_line":""},{"line_number":35,"context_line":"The ML2 based mechanism driver will interact with Cisco UCS Manager via"},{"line_number":36,"context_line":"UCS specific Python SDK."},{"line_number":37,"context_line":""},{"line_number":38,"context_line":"Proposed change"},{"line_number":39,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":1,"id":"1ae5cdf2_b9c18b30","line":36,"in_reply_to":"3ae8d1ca_5a613d38","updated":"2014-05-30 18:43:12.000000000","message":"Done","commit_id":"99e500c69ed8a9f4e78c9d308ab2ebd9b0af5ecb"},{"author":{"_account_id":6697,"name":"Sandhya Dasu","email":"sandhya.openinfra@gmail.com","username":"sadasu"},"change_message_id":"92f7f07a5cd422fe45876e44822c176dc64721f8","unresolved":false,"context_lines":[{"line_number":33,"context_line":"   specific Cisco and Intel NICs (without using port profiles)."},{"line_number":34,"context_line":""},{"line_number":35,"context_line":"The ML2 based mechanism driver will interact with Cisco UCS Manager via"},{"line_number":36,"context_line":"UCS specific Python SDK."},{"line_number":37,"context_line":""},{"line_number":38,"context_line":"Proposed change"},{"line_number":39,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":1,"id":"1ae5cdf2_99c4cf41","line":36,"in_reply_to":"3ae8d1ca_f3eda426","updated":"2014-05-30 18:43:12.000000000","message":"Done","commit_id":"99e500c69ed8a9f4e78c9d308ab2ebd9b0af5ecb"},{"author":{"_account_id":6685,"name":"Baodong (Robert) Li","email":"baoli@cisco.com","username":"baoli"},"change_message_id":"00331f4e579bd66d87a7c7e9bebf62b126004487","unresolved":false,"context_lines":[{"line_number":36,"context_line":"UCS specific Python SDK."},{"line_number":37,"context_line":""},{"line_number":38,"context_line":"Proposed change"},{"line_number":39,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":40,"context_line":""},{"line_number":41,"context_line":"PCI passthrough and SR-IOV ports do not have a corresponding entity on the hypervisor. So, it is important that no L2 agent binds these ports. This ml2 mechanism driver takes care of binding the above mentioned PCI passthrough and SR-IOV virtual functions (VFs)that belong to specific Cisco and Intel NICs."},{"line_number":42,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"3ae8d1ca_7d9fd3b4","line":39,"updated":"2014-05-28 15:04:55.000000000","message":"there should be less than 79 letters per line in this section and the entire spec.\n\nAlso can we approach this section by saying a MD will be developed to solve the above problem, and what this MD would do?","commit_id":"99e500c69ed8a9f4e78c9d308ab2ebd9b0af5ecb"},{"author":{"_account_id":6697,"name":"Sandhya Dasu","email":"sandhya.openinfra@gmail.com","username":"sadasu"},"change_message_id":"92f7f07a5cd422fe45876e44822c176dc64721f8","unresolved":false,"context_lines":[{"line_number":36,"context_line":"UCS specific Python SDK."},{"line_number":37,"context_line":""},{"line_number":38,"context_line":"Proposed change"},{"line_number":39,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":40,"context_line":""},{"line_number":41,"context_line":"PCI passthrough and SR-IOV ports do not have a corresponding entity on the hypervisor. So, it is important that no L2 agent binds these ports. This ml2 mechanism driver takes care of binding the above mentioned PCI passthrough and SR-IOV virtual functions (VFs)that belong to specific Cisco and Intel NICs."},{"line_number":42,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"1ae5cdf2_f9e233d4","line":39,"in_reply_to":"3ae8d1ca_7d9fd3b4","updated":"2014-05-30 18:43:12.000000000","message":"Done","commit_id":"99e500c69ed8a9f4e78c9d308ab2ebd9b0af5ecb"},{"author":{"_account_id":6685,"name":"Baodong (Robert) Li","email":"baoli@cisco.com","username":"baoli"},"change_message_id":"00331f4e579bd66d87a7c7e9bebf62b126004487","unresolved":false,"context_lines":[{"line_number":38,"context_line":"Proposed change"},{"line_number":39,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":40,"context_line":""},{"line_number":41,"context_line":"PCI passthrough and SR-IOV ports do not have a corresponding entity on the hypervisor. So, it is important that no L2 agent binds these ports. This ml2 mechanism driver takes care of binding the above mentioned PCI passthrough and SR-IOV virtual functions (VFs)that belong to specific Cisco and Intel NICs."},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"The mechanism driver is also responsible for configuring and maintaining Port"},{"line_number":44,"context_line":"Profiles for the Openstack virtual functions on the UCS manager. The port"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3ae8d1ca_ba16c153","line":41,"updated":"2014-05-28 15:04:55.000000000","message":"This is confusing. Do you mean to say that sr-iov ports are directly connected to the VMs, and therefore no l2 agent involvement in the data path establishment with cisco vNIC (as well as intel vNIC this MD supports)?\n\n binding in the MD involves information exchange between nova and neutron, which triggers  the l2 agent on the compute node to establish data path.","commit_id":"99e500c69ed8a9f4e78c9d308ab2ebd9b0af5ecb"},{"author":{"_account_id":6697,"name":"Sandhya Dasu","email":"sandhya.openinfra@gmail.com","username":"sadasu"},"change_message_id":"92f7f07a5cd422fe45876e44822c176dc64721f8","unresolved":false,"context_lines":[{"line_number":38,"context_line":"Proposed change"},{"line_number":39,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":40,"context_line":""},{"line_number":41,"context_line":"PCI passthrough and SR-IOV ports do not have a corresponding entity on the hypervisor. So, it is important that no L2 agent binds these ports. This ml2 mechanism driver takes care of binding the above mentioned PCI passthrough and SR-IOV virtual functions (VFs)that belong to specific Cisco and Intel NICs."},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"The mechanism driver is also responsible for configuring and maintaining Port"},{"line_number":44,"context_line":"Profiles for the Openstack virtual functions on the UCS manager. The port"}],"source_content_type":"text/x-rst","patch_set":1,"id":"1ae5cdf2_19e8bfb3","line":41,"in_reply_to":"3ae8d1ca_ba16c153","updated":"2014-05-30 18:43:12.000000000","message":"Reworded this. Hope it makes it clearer now.","commit_id":"99e500c69ed8a9f4e78c9d308ab2ebd9b0af5ecb"},{"author":{"_account_id":6558,"name":"Sukhdev Kapur","email":"sukhdevkapur@gmail.com","username":"sukhdev-8"},"change_message_id":"efe5c5dfeeee54e18909e507e1aec2ec6b0ff3b2","unresolved":false,"context_lines":[{"line_number":42,"context_line":""},{"line_number":43,"context_line":"The mechanism driver is also responsible for configuring and maintaining Port"},{"line_number":44,"context_line":"Profiles for the Openstack virtual functions on the UCS manager. The port"},{"line_number":45,"context_line":"profile is required to completely configure VMFex on Cisco NICs using UCS manager. However, we did not want the tenant to be exposed to this vendor specific concept. To take care of this situation, the ML2 driver creates or re-uses a port profile behind the scenes using relavant information from the network (vlan-id) on which the vm-fex port is configured."},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"Alternatives"},{"line_number":48,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5adbc538_9cb93cec","line":45,"updated":"2014-05-25 18:00:21.000000000","message":"you mention this MD creates and maintains port profiles. Do you store these on the Neutron Server (i.e. ML2 DB) or on the UCS manager?","commit_id":"99e500c69ed8a9f4e78c9d308ab2ebd9b0af5ecb"},{"author":{"_account_id":6697,"name":"Sandhya Dasu","email":"sandhya.openinfra@gmail.com","username":"sadasu"},"change_message_id":"92f7f07a5cd422fe45876e44822c176dc64721f8","unresolved":false,"context_lines":[{"line_number":42,"context_line":""},{"line_number":43,"context_line":"The mechanism driver is also responsible for configuring and maintaining Port"},{"line_number":44,"context_line":"Profiles for the Openstack virtual functions on the UCS manager. The port"},{"line_number":45,"context_line":"profile is required to completely configure VMFex on Cisco NICs using UCS manager. However, we did not want the tenant to be exposed to this vendor specific concept. To take care of this situation, the ML2 driver creates or re-uses a port profile behind the scenes using relavant information from the network (vlan-id) on which the vm-fex port is configured."},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"Alternatives"},{"line_number":48,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3ae8d1ca_c93bf4e9","line":45,"in_reply_to":"5adbc538_9cb93cec","updated":"2014-05-30 18:43:12.000000000","message":"This information is scattered throughout the spec, so specifically added this information at this point in the spec for clarity.","commit_id":"99e500c69ed8a9f4e78c9d308ab2ebd9b0af5ecb"},{"author":{"_account_id":107,"name":"Arvind Somya","email":"arvind.somya@gmail.com","username":"asomya"},"change_message_id":"519380388ee8f685a174b2ddc063d98879d749f5","unresolved":false,"context_lines":[{"line_number":43,"context_line":"The mechanism driver is also responsible for configuring and maintaining Port"},{"line_number":44,"context_line":"Profiles for the Openstack virtual functions on the UCS manager. The port"},{"line_number":45,"context_line":"profile is required to completely configure VMFex on Cisco NICs using UCS manager. However, we did not want the tenant to be exposed to this vendor specific concept. To take care of this situation, the ML2 driver creates or re-uses a port profile behind the scenes using relavant information from the network (vlan-id) on which the vm-fex port is configured."},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"Alternatives"},{"line_number":48,"context_line":"------------"},{"line_number":49,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"3ae8d1ca_b0e1529c","line":46,"updated":"2014-05-29 17:56:23.000000000","message":"A workflow diagram would be helpful here to see which API calls this driver will consume.","commit_id":"99e500c69ed8a9f4e78c9d308ab2ebd9b0af5ecb"},{"author":{"_account_id":107,"name":"Arvind Somya","email":"arvind.somya@gmail.com","username":"asomya"},"change_message_id":"519380388ee8f685a174b2ddc063d98879d749f5","unresolved":false,"context_lines":[{"line_number":47,"context_line":"Alternatives"},{"line_number":48,"context_line":"------------"},{"line_number":49,"context_line":""},{"line_number":50,"context_line":"ML2 mechanism drivers are preferred over monolithic plugins in Neutron."},{"line_number":51,"context_line":""},{"line_number":52,"context_line":"Data model impact"},{"line_number":53,"context_line":"-----------------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3ae8d1ca_90fd363d","line":50,"updated":"2014-05-29 17:56:23.000000000","message":"I think this section is for alternate approaches to solving this problem, not plugin/driver types. In this case this should be None.","commit_id":"99e500c69ed8a9f4e78c9d308ab2ebd9b0af5ecb"},{"author":{"_account_id":6697,"name":"Sandhya Dasu","email":"sandhya.openinfra@gmail.com","username":"sadasu"},"change_message_id":"92f7f07a5cd422fe45876e44822c176dc64721f8","unresolved":false,"context_lines":[{"line_number":47,"context_line":"Alternatives"},{"line_number":48,"context_line":"------------"},{"line_number":49,"context_line":""},{"line_number":50,"context_line":"ML2 mechanism drivers are preferred over monolithic plugins in Neutron."},{"line_number":51,"context_line":""},{"line_number":52,"context_line":"Data model impact"},{"line_number":53,"context_line":"-----------------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"1ae5cdf2_79ce235c","line":50,"in_reply_to":"3ae8d1ca_90fd363d","updated":"2014-05-30 18:43:12.000000000","message":"Done","commit_id":"99e500c69ed8a9f4e78c9d308ab2ebd9b0af5ecb"},{"author":{"_account_id":490,"name":"Sumit Naiksatam","email":"sumitnaiksatam@gmail.com","username":"snaiksat"},"change_message_id":"7b48a137318b417202e4a21fd19710c4ef807451","unresolved":false,"context_lines":[{"line_number":57,"context_line":"driver does not care about."},{"line_number":58,"context_line":""},{"line_number":59,"context_line":"PortProfile: Tracks the vlan-id associated with a given port profile and the"},{"line_number":60,"context_line":"VF that is currently configured with this PortProfile."},{"line_number":61,"context_line":""},{"line_number":62,"context_line":"REST API impact"},{"line_number":63,"context_line":"---------------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"7adec928_08a66110","line":60,"updated":"2014-05-23 18:59:28.000000000","message":"It will be helpful to know what attributes you plan to put here.","commit_id":"99e500c69ed8a9f4e78c9d308ab2ebd9b0af5ecb"},{"author":{"_account_id":6697,"name":"Sandhya Dasu","email":"sandhya.openinfra@gmail.com","username":"sadasu"},"change_message_id":"92f7f07a5cd422fe45876e44822c176dc64721f8","unresolved":false,"context_lines":[{"line_number":57,"context_line":"driver does not care about."},{"line_number":58,"context_line":""},{"line_number":59,"context_line":"PortProfile: Tracks the vlan-id associated with a given port profile and the"},{"line_number":60,"context_line":"VF that is currently configured with this PortProfile."},{"line_number":61,"context_line":""},{"line_number":62,"context_line":"REST API impact"},{"line_number":63,"context_line":"---------------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3ae8d1ca_c441190d","line":60,"in_reply_to":"7adec928_08a66110","updated":"2014-05-30 18:43:12.000000000","message":"The UCS Manager port profile supports QoS Policy as an attribute in addition to vlan-id. We are watching the Group Policy work to see how the UCS Manager port profiles can be translated into an generic group policy. That way above mentioned port profile can be exposed to/configured by the user as opposed to being hidden.","commit_id":"99e500c69ed8a9f4e78c9d308ab2ebd9b0af5ecb"},{"author":{"_account_id":107,"name":"Arvind Somya","email":"arvind.somya@gmail.com","username":"asomya"},"change_message_id":"519380388ee8f685a174b2ddc063d98879d749f5","unresolved":false,"context_lines":[{"line_number":58,"context_line":""},{"line_number":59,"context_line":"PortProfile: Tracks the vlan-id associated with a given port profile and the"},{"line_number":60,"context_line":"VF that is currently configured with this PortProfile."},{"line_number":61,"context_line":""},{"line_number":62,"context_line":"REST API impact"},{"line_number":63,"context_line":"---------------"},{"line_number":64,"context_line":"None."}],"source_content_type":"text/x-rst","patch_set":1,"id":"3ae8d1ca_933540dc","line":61,"updated":"2014-05-29 17:56:23.000000000","message":"Also add migration information here.","commit_id":"99e500c69ed8a9f4e78c9d308ab2ebd9b0af5ecb"},{"author":{"_account_id":490,"name":"Sumit Naiksatam","email":"sumitnaiksatam@gmail.com","username":"snaiksat"},"change_message_id":"7b48a137318b417202e4a21fd19710c4ef807451","unresolved":false,"context_lines":[{"line_number":66,"context_line":""},{"line_number":67,"context_line":"Security impact"},{"line_number":68,"context_line":"---------------"},{"line_number":69,"context_line":"None."},{"line_number":70,"context_line":""},{"line_number":71,"context_line":"Notifications impact"},{"line_number":72,"context_line":"--------------------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"7adec928_2845dd16","line":69,"updated":"2014-05-23 18:59:28.000000000","message":"Is the channel to the UCSM secure?","commit_id":"99e500c69ed8a9f4e78c9d308ab2ebd9b0af5ecb"},{"author":{"_account_id":6697,"name":"Sandhya Dasu","email":"sandhya.openinfra@gmail.com","username":"sadasu"},"change_message_id":"92f7f07a5cd422fe45876e44822c176dc64721f8","unresolved":false,"context_lines":[{"line_number":66,"context_line":""},{"line_number":67,"context_line":"Security impact"},{"line_number":68,"context_line":"---------------"},{"line_number":69,"context_line":"None."},{"line_number":70,"context_line":""},{"line_number":71,"context_line":"Notifications impact"},{"line_number":72,"context_line":"--------------------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3ae8d1ca_5ea68a54","line":69,"in_reply_to":"7adec928_2845dd16","updated":"2014-05-30 18:43:12.000000000","message":"Yes. The connection to the XML API layer on the UCS Manager is via HTTP/HTTPS.","commit_id":"99e500c69ed8a9f4e78c9d308ab2ebd9b0af5ecb"},{"author":{"_account_id":490,"name":"Sumit Naiksatam","email":"sumitnaiksatam@gmail.com","username":"snaiksat"},"change_message_id":"7b48a137318b417202e4a21fd19710c4ef807451","unresolved":false,"context_lines":[{"line_number":93,"context_line":""},{"line_number":94,"context_line":"1. IP address of UCS Manager"},{"line_number":95,"context_line":"2. Admin Username and password to log into UCS Manager."},{"line_number":96,"context_line":"3. Add \"cisco_ucsm\" as a ML2 driver to handle SR-IOV port configuration."},{"line_number":97,"context_line":""},{"line_number":98,"context_line":"Developer impact"},{"line_number":99,"context_line":"----------------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"7adec928_085901fe","line":96,"updated":"2014-05-23 18:59:28.000000000","message":"What type and/or additional mechanism drivers should be configured (or explicitly not be configured)?","commit_id":"99e500c69ed8a9f4e78c9d308ab2ebd9b0af5ecb"},{"author":{"_account_id":6697,"name":"Sandhya Dasu","email":"sandhya.openinfra@gmail.com","username":"sadasu"},"change_message_id":"92f7f07a5cd422fe45876e44822c176dc64721f8","unresolved":false,"context_lines":[{"line_number":93,"context_line":""},{"line_number":94,"context_line":"1. IP address of UCS Manager"},{"line_number":95,"context_line":"2. Admin Username and password to log into UCS Manager."},{"line_number":96,"context_line":"3. Add \"cisco_ucsm\" as a ML2 driver to handle SR-IOV port configuration."},{"line_number":97,"context_line":""},{"line_number":98,"context_line":"Developer impact"},{"line_number":99,"context_line":"----------------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3ae8d1ca_26ed5ec4","line":96,"in_reply_to":"7adec928_085901fe","updated":"2014-05-30 18:43:12.000000000","message":"Added information about the need to configure the VLAN type driver. No other mechanism driver is required to support SR-IOV ports on the Cisco UCS. But, since a cloud setup rarely is composed of only SR-IOV ports, the cloud admin will have to provision other mechanism drivers to handle non-SR-IOV ports or SR-IOV ports from other vendors. Hope this answers your question.","commit_id":"99e500c69ed8a9f4e78c9d308ab2ebd9b0af5ecb"},{"author":{"_account_id":490,"name":"Sumit Naiksatam","email":"sumitnaiksatam@gmail.com","username":"snaiksat"},"change_message_id":"7b48a137318b417202e4a21fd19710c4ef807451","unresolved":false,"context_lines":[{"line_number":123,"context_line":"https://github.com/CiscoUcs/UcsPythonSDK) to communicate with the UCS Manager."},{"line_number":124,"context_line":""},{"line_number":125,"context_line":"2. For SR-IOV ports to be actually scheduled and assigned to a VM, some non-vendor specific Nova code is required. This effort is tracked via:"},{"line_number":126,"context_line":"https://blueprints.launchpad.net/nova/+spec/pci-passthrough-sriov"},{"line_number":127,"context_line":""},{"line_number":128,"context_line":"Testing"},{"line_number":129,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":1,"id":"7adec928_a8b9ed16","line":126,"updated":"2014-05-23 18:59:28.000000000","message":"I would imagine that the same type of scheduling/assignment would need to be done for UCS port-profiles? How is that achieved?","commit_id":"99e500c69ed8a9f4e78c9d308ab2ebd9b0af5ecb"},{"author":{"_account_id":6697,"name":"Sandhya Dasu","email":"sandhya.openinfra@gmail.com","username":"sadasu"},"change_message_id":"92f7f07a5cd422fe45876e44822c176dc64721f8","unresolved":false,"context_lines":[{"line_number":123,"context_line":"https://github.com/CiscoUcs/UcsPythonSDK) to communicate with the UCS Manager."},{"line_number":124,"context_line":""},{"line_number":125,"context_line":"2. For SR-IOV ports to be actually scheduled and assigned to a VM, some non-vendor specific Nova code is required. This effort is tracked via:"},{"line_number":126,"context_line":"https://blueprints.launchpad.net/nova/+spec/pci-passthrough-sriov"},{"line_number":127,"context_line":""},{"line_number":128,"context_line":"Testing"},{"line_number":129,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3ae8d1ca_c6959ae5","line":126,"in_reply_to":"7adec928_a8b9ed16","updated":"2014-05-30 18:43:12.000000000","message":"I am not sure I understand this question. When a neutron port is created with the vnic_type as \"direct\" or \"macvtap\", a port profile for this port is created or re-used. Based on the Vlan-id of the network on which this port is created, the mech driver looks to see of a port profile with this Vlan-id already exists. If not, it creates one. At this point, the new or re-used port profile is associated with the neutron port.\n\nFor a VM looking to use this SR-IOV port, the above port_id is passed in as a parameter to the \"nova boot --nic port-id \u003c\u003e\" command. Multiple ports can be assigned to the VM via this command. Nova then schedules the VM based on the availability of a free SR-IOV port that satisfies the attributes of the port. Because of its association with a port right from the point of creation, it is not necessary to schedule the port profile separately.","commit_id":"99e500c69ed8a9f4e78c9d308ab2ebd9b0af5ecb"},{"author":{"_account_id":6685,"name":"Baodong (Robert) Li","email":"baoli@cisco.com","username":"baoli"},"change_message_id":"e70d97ee10a1dbf703001d8532f118d271543afd","unresolved":false,"context_lines":[{"line_number":19,"context_line":"Problem description"},{"line_number":20,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":21,"context_line":""},{"line_number":22,"context_line":"This section includes a brief introduction to the SR-IOV and Cisco VM-FEX "},{"line_number":23,"context_line":"technologies in addition to a detailed description of the problem:"},{"line_number":24,"context_line":""},{"line_number":25,"context_line":"1. This mechanism driver needs to be able to configure Cisco VM-FEX on specific"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1ae5cdf2_5caf2294","line":22,"updated":"2014-06-04 02:25:52.000000000","message":"remove the white space across the specs","commit_id":"2f1629e091c4910cb446601f5310ef11bf1eaa8e"},{"author":{"_account_id":6697,"name":"Sandhya Dasu","email":"sandhya.openinfra@gmail.com","username":"sadasu"},"change_message_id":"802245db8310dbe25e0044bdb1f2c9fa2a5e6cfc","unresolved":false,"context_lines":[{"line_number":19,"context_line":"Problem description"},{"line_number":20,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":21,"context_line":""},{"line_number":22,"context_line":"This section includes a brief introduction to the SR-IOV and Cisco VM-FEX "},{"line_number":23,"context_line":"technologies in addition to a detailed description of the problem:"},{"line_number":24,"context_line":""},{"line_number":25,"context_line":"1. This mechanism driver needs to be able to configure Cisco VM-FEX on specific"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1ae5cdf2_8d8f9a29","line":22,"in_reply_to":"1ae5cdf2_5caf2294","updated":"2014-06-04 20:24:12.000000000","message":"Done","commit_id":"2f1629e091c4910cb446601f5310ef11bf1eaa8e"},{"author":{"_account_id":6685,"name":"Baodong (Robert) Li","email":"baoli@cisco.com","username":"baoli"},"change_message_id":"e70d97ee10a1dbf703001d8532f118d271543afd","unresolved":false,"context_lines":[{"line_number":29,"context_line":"PCIe physical device (PF - physical function) to be divided into multiple "},{"line_number":30,"context_line":"logical devices (VF - virtual functions)."},{"line_number":31,"context_line":""},{"line_number":32,"context_line":"3. Each of these VFs can be configured to be in either the \"direct\" or "},{"line_number":33,"context_line":"\"macvtap\" modes. In the \"direct\" mode, the VF completely bypasses the hyper-"},{"line_number":34,"context_line":"visor and sends and received data directly to and from the upstream switch. "},{"line_number":35,"context_line":"This results in a significant increase in throughput on the VM and frees up CPU"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1ae5cdf2_fcc9ce26","line":32,"updated":"2014-06-04 02:25:52.000000000","message":"I think it\u0027s the VM\u0027s port that is either in direct or macvtap mode. The VM\u0027s port is connected to a VF either directly or via a macvtap device residing on the host.","commit_id":"2f1629e091c4910cb446601f5310ef11bf1eaa8e"},{"author":{"_account_id":6697,"name":"Sandhya Dasu","email":"sandhya.openinfra@gmail.com","username":"sadasu"},"change_message_id":"802245db8310dbe25e0044bdb1f2c9fa2a5e6cfc","unresolved":false,"context_lines":[{"line_number":29,"context_line":"PCIe physical device (PF - physical function) to be divided into multiple "},{"line_number":30,"context_line":"logical devices (VF - virtual functions)."},{"line_number":31,"context_line":""},{"line_number":32,"context_line":"3. Each of these VFs can be configured to be in either the \"direct\" or "},{"line_number":33,"context_line":"\"macvtap\" modes. In the \"direct\" mode, the VF completely bypasses the hyper-"},{"line_number":34,"context_line":"visor and sends and received data directly to and from the upstream switch. "},{"line_number":35,"context_line":"This results in a significant increase in throughput on the VM and frees up CPU"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1ae5cdf2_105d6447","line":32,"in_reply_to":"1ae5cdf2_fcc9ce26","updated":"2014-06-04 20:24:12.000000000","message":"Done","commit_id":"2f1629e091c4910cb446601f5310ef11bf1eaa8e"},{"author":{"_account_id":6685,"name":"Baodong (Robert) Li","email":"baoli@cisco.com","username":"baoli"},"change_message_id":"e70d97ee10a1dbf703001d8532f118d271543afd","unresolved":false,"context_lines":[{"line_number":30,"context_line":"logical devices (VF - virtual functions)."},{"line_number":31,"context_line":""},{"line_number":32,"context_line":"3. Each of these VFs can be configured to be in either the \"direct\" or "},{"line_number":33,"context_line":"\"macvtap\" modes. In the \"direct\" mode, the VF completely bypasses the hyper-"},{"line_number":34,"context_line":"visor and sends and received data directly to and from the upstream switch. "},{"line_number":35,"context_line":"This results in a significant increase in throughput on the VM and frees up CPU"},{"line_number":36,"context_line":"resources on the host OS to handle more VMs. Due to this direct connection with"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1ae5cdf2_1c903a49","line":33,"updated":"2014-06-04 02:25:52.000000000","message":"VM\u0027s traffic completely bypasses the hypervisor, sending and receiving data directly to and from the vNIC and thus the upstream switch.","commit_id":"2f1629e091c4910cb446601f5310ef11bf1eaa8e"},{"author":{"_account_id":6697,"name":"Sandhya Dasu","email":"sandhya.openinfra@gmail.com","username":"sadasu"},"change_message_id":"802245db8310dbe25e0044bdb1f2c9fa2a5e6cfc","unresolved":false,"context_lines":[{"line_number":30,"context_line":"logical devices (VF - virtual functions)."},{"line_number":31,"context_line":""},{"line_number":32,"context_line":"3. Each of these VFs can be configured to be in either the \"direct\" or "},{"line_number":33,"context_line":"\"macvtap\" modes. In the \"direct\" mode, the VF completely bypasses the hyper-"},{"line_number":34,"context_line":"visor and sends and received data directly to and from the upstream switch. "},{"line_number":35,"context_line":"This results in a significant increase in throughput on the VM and frees up CPU"},{"line_number":36,"context_line":"resources on the host OS to handle more VMs. Due to this direct connection with"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1ae5cdf2_ed03be3f","line":33,"in_reply_to":"1ae5cdf2_1c903a49","updated":"2014-06-04 20:24:12.000000000","message":"Done","commit_id":"2f1629e091c4910cb446601f5310ef11bf1eaa8e"},{"author":{"_account_id":1689,"name":"Robert Kukura","email":"rk@theep.net","username":"rkukura"},"change_message_id":"ab9d6957316f49676b56121139b4ee62fd73ffa3","unresolved":false,"context_lines":[{"line_number":69,"context_line":"uses the segmentation-id associated with the network to determine if a new"},{"line_number":70,"context_line":"port profile needs to be created. According to the DB maintained by the ML2"},{"line_number":71,"context_line":"driver, if a port profile with that vlan_id already exists, then it re-uses "},{"line_number":72,"context_line":"this port profile for the neutron port being created."},{"line_number":73,"context_line":""},{"line_number":74,"context_line":"3. If the ML2 driver determines that an existing port profile cannot be re-used"},{"line_number":75,"context_line":"it tries to create a new port profile on the UCS manager using the vlan_id"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1ae5cdf2_074d303e","line":72,"updated":"2014-06-04 15:07:33.000000000","message":"Consider creating port profiles as part of binding the port rather than when the port is initially created. There is no need to create profiles for ports that do not end up being bound using this mechanism driver, or for network segments that are not selected during port binding.","commit_id":"2f1629e091c4910cb446601f5310ef11bf1eaa8e"},{"author":{"_account_id":6697,"name":"Sandhya Dasu","email":"sandhya.openinfra@gmail.com","username":"sadasu"},"change_message_id":"802245db8310dbe25e0044bdb1f2c9fa2a5e6cfc","unresolved":false,"context_lines":[{"line_number":69,"context_line":"uses the segmentation-id associated with the network to determine if a new"},{"line_number":70,"context_line":"port profile needs to be created. According to the DB maintained by the ML2"},{"line_number":71,"context_line":"driver, if a port profile with that vlan_id already exists, then it re-uses "},{"line_number":72,"context_line":"this port profile for the neutron port being created."},{"line_number":73,"context_line":""},{"line_number":74,"context_line":"3. If the ML2 driver determines that an existing port profile cannot be re-used"},{"line_number":75,"context_line":"it tries to create a new port profile on the UCS manager using the vlan_id"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1ae5cdf2_3e5dca15","line":72,"in_reply_to":"1ae5cdf2_074d303e","updated":"2014-06-04 20:24:12.000000000","message":"Done","commit_id":"2f1629e091c4910cb446601f5310ef11bf1eaa8e"},{"author":{"_account_id":6685,"name":"Baodong (Robert) Li","email":"baoli@cisco.com","username":"baoli"},"change_message_id":"e70d97ee10a1dbf703001d8532f118d271543afd","unresolved":false,"context_lines":[{"line_number":77,"context_line":"want to expose this to the cloud admin or the tenant. So, port profiles are"},{"line_number":78,"context_line":"created and maintained completely behind the scenes by the ML2 driver."},{"line_number":79,"context_line":""},{"line_number":80,"context_line":"4. For VM-FEX and SR-IOV ports, there is no need for aa seprate L2 agent to "},{"line_number":81,"context_line":"setup datapath on the compute host. The ML2 mechanism driver takes care of "},{"line_number":82,"context_line":"binding the port if the pci vendor info in the binding:profile portbinding "},{"line_number":83,"context_line":"attribute matches the pci device attributes of the devices it can handle."}],"source_content_type":"text/x-rst","patch_set":2,"id":"1ae5cdf2_5cb482d0","line":80,"updated":"2014-06-04 02:25:52.000000000","message":"aa -- a\n\nseparate","commit_id":"2f1629e091c4910cb446601f5310ef11bf1eaa8e"},{"author":{"_account_id":6697,"name":"Sandhya Dasu","email":"sandhya.openinfra@gmail.com","username":"sadasu"},"change_message_id":"802245db8310dbe25e0044bdb1f2c9fa2a5e6cfc","unresolved":false,"context_lines":[{"line_number":77,"context_line":"want to expose this to the cloud admin or the tenant. So, port profiles are"},{"line_number":78,"context_line":"created and maintained completely behind the scenes by the ML2 driver."},{"line_number":79,"context_line":""},{"line_number":80,"context_line":"4. For VM-FEX and SR-IOV ports, there is no need for aa seprate L2 agent to "},{"line_number":81,"context_line":"setup datapath on the compute host. The ML2 mechanism driver takes care of "},{"line_number":82,"context_line":"binding the port if the pci vendor info in the binding:profile portbinding "},{"line_number":83,"context_line":"attribute matches the pci device attributes of the devices it can handle."}],"source_content_type":"text/x-rst","patch_set":2,"id":"1ae5cdf2_de6946bf","line":80,"in_reply_to":"1ae5cdf2_5cb482d0","updated":"2014-06-04 20:24:12.000000000","message":"Done","commit_id":"2f1629e091c4910cb446601f5310ef11bf1eaa8e"},{"author":{"_account_id":1689,"name":"Robert Kukura","email":"rk@theep.net","username":"rkukura"},"change_message_id":"ab9d6957316f49676b56121139b4ee62fd73ffa3","unresolved":false,"context_lines":[{"line_number":80,"context_line":"4. For VM-FEX and SR-IOV ports, there is no need for aa seprate L2 agent to "},{"line_number":81,"context_line":"setup datapath on the compute host. The ML2 mechanism driver takes care of "},{"line_number":82,"context_line":"binding the port if the pci vendor info in the binding:profile portbinding "},{"line_number":83,"context_line":"attribute matches the pci device attributes of the devices it can handle."},{"line_number":84,"context_line":""},{"line_number":85,"context_line":"5. Once the port profile is created on the UCS manager, the ML2 driver populates"},{"line_number":86,"context_line":"the profile:vif_details portbindings attribute with the profile_id (name of the"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1ae5cdf2_47749835","line":83,"updated":"2014-06-04 15:07:33.000000000","message":"Please clarify how the binding:profile or other information is used to determine which segment of a multi-segment network is chosen during port binding.","commit_id":"2f1629e091c4910cb446601f5310ef11bf1eaa8e"},{"author":{"_account_id":6697,"name":"Sandhya Dasu","email":"sandhya.openinfra@gmail.com","username":"sadasu"},"change_message_id":"802245db8310dbe25e0044bdb1f2c9fa2a5e6cfc","unresolved":false,"context_lines":[{"line_number":80,"context_line":"4. For VM-FEX and SR-IOV ports, there is no need for aa seprate L2 agent to "},{"line_number":81,"context_line":"setup datapath on the compute host. The ML2 mechanism driver takes care of "},{"line_number":82,"context_line":"binding the port if the pci vendor info in the binding:profile portbinding "},{"line_number":83,"context_line":"attribute matches the pci device attributes of the devices it can handle."},{"line_number":84,"context_line":""},{"line_number":85,"context_line":"5. Once the port profile is created on the UCS manager, the ML2 driver populates"},{"line_number":86,"context_line":"the profile:vif_details portbindings attribute with the profile_id (name of the"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1ae5cdf2_e0f90581","line":83,"in_reply_to":"1ae5cdf2_47749835","updated":"2014-06-04 20:24:12.000000000","message":"We are currently not supporting multi-segment networks.","commit_id":"2f1629e091c4910cb446601f5310ef11bf1eaa8e"},{"author":{"_account_id":490,"name":"Sumit Naiksatam","email":"sumitnaiksatam@gmail.com","username":"snaiksat"},"change_message_id":"91a6696f1cc01676e252fa88c0fcbba46261081a","unresolved":false,"context_lines":[{"line_number":80,"context_line":"4. For VM-FEX and SR-IOV ports, there is no need for aa seprate L2 agent to "},{"line_number":81,"context_line":"setup datapath on the compute host. The ML2 mechanism driver takes care of "},{"line_number":82,"context_line":"binding the port if the pci vendor info in the binding:profile portbinding "},{"line_number":83,"context_line":"attribute matches the pci device attributes of the devices it can handle."},{"line_number":84,"context_line":""},{"line_number":85,"context_line":"5. Once the port profile is created on the UCS manager, the ML2 driver populates"},{"line_number":86,"context_line":"the profile:vif_details portbindings attribute with the profile_id (name of the"}],"source_content_type":"text/x-rst","patch_set":2,"id":"baada198_f6f51983","line":83,"in_reply_to":"1ae5cdf2_e0f90581","updated":"2014-07-07 19:54:44.000000000","message":"I believe it might be instructive to mention this explicitly.","commit_id":"2f1629e091c4910cb446601f5310ef11bf1eaa8e"},{"author":{"_account_id":6697,"name":"Sandhya Dasu","email":"sandhya.openinfra@gmail.com","username":"sadasu"},"change_message_id":"9e5fcb71dfd5d40a1615e53dc079c06bd6bc7e1b","unresolved":false,"context_lines":[{"line_number":80,"context_line":"4. For VM-FEX and SR-IOV ports, there is no need for aa seprate L2 agent to "},{"line_number":81,"context_line":"setup datapath on the compute host. The ML2 mechanism driver takes care of "},{"line_number":82,"context_line":"binding the port if the pci vendor info in the binding:profile portbinding "},{"line_number":83,"context_line":"attribute matches the pci device attributes of the devices it can handle."},{"line_number":84,"context_line":""},{"line_number":85,"context_line":"5. Once the port profile is created on the UCS manager, the ML2 driver populates"},{"line_number":86,"context_line":"the profile:vif_details portbindings attribute with the profile_id (name of the"}],"source_content_type":"text/x-rst","patch_set":2,"id":"baada198_03f3df73","line":83,"in_reply_to":"baada198_f6f51983","updated":"2014-07-09 17:59:17.000000000","message":"Done","commit_id":"2f1629e091c4910cb446601f5310ef11bf1eaa8e"},{"author":{"_account_id":6685,"name":"Baodong (Robert) Li","email":"baoli@cisco.com","username":"baoli"},"change_message_id":"e70d97ee10a1dbf703001d8532f118d271543afd","unresolved":false,"context_lines":[{"line_number":85,"context_line":"5. Once the port profile is created on the UCS manager, the ML2 driver populates"},{"line_number":86,"context_line":"the profile:vif_details portbindings attribute with the profile_id (name of the"},{"line_number":87,"context_line":"port profile). Nova then uses Neutron V2 API to grab the profile_id and "},{"line_number":88,"context_line":"populates the VM\u0027s domain XML. With this the configuration of VM-FEX is "},{"line_number":89,"context_line":"complete."},{"line_number":90,"context_line":""},{"line_number":91,"context_line":"6. In the case of NICs that support SR-IOV and not VM-FEX (for example, the "}],"source_content_type":"text/x-rst","patch_set":2,"id":"1ae5cdf2_7c413ea8","line":88,"updated":"2014-06-04 02:25:52.000000000","message":"After the VM is successfully launched by libvirt, the configuration of VM-FEX is complete","commit_id":"2f1629e091c4910cb446601f5310ef11bf1eaa8e"},{"author":{"_account_id":6697,"name":"Sandhya Dasu","email":"sandhya.openinfra@gmail.com","username":"sadasu"},"change_message_id":"802245db8310dbe25e0044bdb1f2c9fa2a5e6cfc","unresolved":false,"context_lines":[{"line_number":85,"context_line":"5. Once the port profile is created on the UCS manager, the ML2 driver populates"},{"line_number":86,"context_line":"the profile:vif_details portbindings attribute with the profile_id (name of the"},{"line_number":87,"context_line":"port profile). Nova then uses Neutron V2 API to grab the profile_id and "},{"line_number":88,"context_line":"populates the VM\u0027s domain XML. With this the configuration of VM-FEX is "},{"line_number":89,"context_line":"complete."},{"line_number":90,"context_line":""},{"line_number":91,"context_line":"6. In the case of NICs that support SR-IOV and not VM-FEX (for example, the "}],"source_content_type":"text/x-rst","patch_set":2,"id":"1ae5cdf2_9e55fefb","line":88,"in_reply_to":"1ae5cdf2_7c413ea8","updated":"2014-06-04 20:24:12.000000000","message":"Done","commit_id":"2f1629e091c4910cb446601f5310ef11bf1eaa8e"},{"author":{"_account_id":1689,"name":"Robert Kukura","email":"rk@theep.net","username":"rkukura"},"change_message_id":"ab9d6957316f49676b56121139b4ee62fd73ffa3","unresolved":false,"context_lines":[{"line_number":115,"context_line":""},{"line_number":116,"context_line":"Security impact"},{"line_number":117,"context_line":"---------------"},{"line_number":118,"context_line":"None. The connection to the XML API layer on the UCS Manager is via HTTP/HTTPS."},{"line_number":119,"context_line":""},{"line_number":120,"context_line":"Notifications impact"},{"line_number":121,"context_line":"--------------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1ae5cdf2_27f78c8c","line":118,"updated":"2014-06-04 15:07:33.000000000","message":"Are security groups enforced when this mechanism driver binds a port? If not, the implications of this should be mentioned here.","commit_id":"2f1629e091c4910cb446601f5310ef11bf1eaa8e"},{"author":{"_account_id":6697,"name":"Sandhya Dasu","email":"sandhya.openinfra@gmail.com","username":"sadasu"},"change_message_id":"802245db8310dbe25e0044bdb1f2c9fa2a5e6cfc","unresolved":false,"context_lines":[{"line_number":115,"context_line":""},{"line_number":116,"context_line":"Security impact"},{"line_number":117,"context_line":"---------------"},{"line_number":118,"context_line":"None. The connection to the XML API layer on the UCS Manager is via HTTP/HTTPS."},{"line_number":119,"context_line":""},{"line_number":120,"context_line":"Notifications impact"},{"line_number":121,"context_line":"--------------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1ae5cdf2_3eeceaf2","line":118,"in_reply_to":"1ae5cdf2_27f78c8c","updated":"2014-06-04 20:24:12.000000000","message":"Since traffic from the VM bypasses the host and hypervisor completely, no security groups are enforced at the time of binding the port.","commit_id":"2f1629e091c4910cb446601f5310ef11bf1eaa8e"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"05fa4cc1b086f8f0c68ee5edf2a9e29933faed32","unresolved":false,"context_lines":[{"line_number":29,"context_line":"PCIe physical device (PF - physical function) to be divided into multiple"},{"line_number":30,"context_line":"logical devices (VF - virtual functions)."},{"line_number":31,"context_line":""},{"line_number":32,"context_line":"3. With SR-IOV and Cisco VM-FEX a VM\u0027s port can be configured in either the "},{"line_number":33,"context_line":"\"direct\" or \"macvtap\" modes. In the \"direct\" mode, the VM\u0027s port is connected"},{"line_number":34,"context_line":"directly to the VF and to a macvtap device on the host in the \"macvtap\" mode."},{"line_number":35,"context_line":"In both these modes, the VM\u0027s traffic completely bypasses the hypervisor,"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1ae5cdf2_7c66512b","line":32,"updated":"2014-06-05 20:50:26.000000000","message":"Nit: whitespace here and 72, 109, and 120. Please clean this up.","commit_id":"739a8b3c48c2fd75256e0db5a1d3221c6390dd03"},{"author":{"_account_id":6697,"name":"Sandhya Dasu","email":"sandhya.openinfra@gmail.com","username":"sadasu"},"change_message_id":"557352650be536d8def2f7e5cdaaf1a138bfa402","unresolved":false,"context_lines":[{"line_number":29,"context_line":"PCIe physical device (PF - physical function) to be divided into multiple"},{"line_number":30,"context_line":"logical devices (VF - virtual functions)."},{"line_number":31,"context_line":""},{"line_number":32,"context_line":"3. With SR-IOV and Cisco VM-FEX a VM\u0027s port can be configured in either the "},{"line_number":33,"context_line":"\"direct\" or \"macvtap\" modes. In the \"direct\" mode, the VM\u0027s port is connected"},{"line_number":34,"context_line":"directly to the VF and to a macvtap device on the host in the \"macvtap\" mode."},{"line_number":35,"context_line":"In both these modes, the VM\u0027s traffic completely bypasses the hypervisor,"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1ae5cdf2_c1c5a63e","line":32,"in_reply_to":"1ae5cdf2_7c66512b","updated":"2014-06-06 15:50:56.000000000","message":"Thought I had taken care of all of them during my previous commit but somehow a few of them sneaked back in.","commit_id":"739a8b3c48c2fd75256e0db5a1d3221c6390dd03"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"05fa4cc1b086f8f0c68ee5edf2a9e29933faed32","unresolved":false,"context_lines":[{"line_number":37,"context_line":"upstream switch. This results in a significant increase in throughput on the VM"},{"line_number":38,"context_line":"and frees up CPU resources on the host OS to handle more VMs. Due to this"},{"line_number":39,"context_line":"direct connection with the upstream switch, the \"direct\" mode does not support"},{"line_number":40,"context_line":"live migration of the VMs that it is attached to."},{"line_number":41,"context_line":""},{"line_number":42,"context_line":"4. Cisco VM-FEX technology is based on the 802.1qbh and works on top of the"},{"line_number":43,"context_line":"SR-IOV technology using the concept of port profiles. Port profiles are"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1ae5cdf2_3c80498a","line":40,"updated":"2014-06-05 20:50:26.000000000","message":"May be worth mentioning one other downside is the lack of ability to enforce security groups on the host.","commit_id":"739a8b3c48c2fd75256e0db5a1d3221c6390dd03"},{"author":{"_account_id":6697,"name":"Sandhya Dasu","email":"sandhya.openinfra@gmail.com","username":"sadasu"},"change_message_id":"557352650be536d8def2f7e5cdaaf1a138bfa402","unresolved":false,"context_lines":[{"line_number":37,"context_line":"upstream switch. This results in a significant increase in throughput on the VM"},{"line_number":38,"context_line":"and frees up CPU resources on the host OS to handle more VMs. Due to this"},{"line_number":39,"context_line":"direct connection with the upstream switch, the \"direct\" mode does not support"},{"line_number":40,"context_line":"live migration of the VMs that it is attached to."},{"line_number":41,"context_line":""},{"line_number":42,"context_line":"4. Cisco VM-FEX technology is based on the 802.1qbh and works on top of the"},{"line_number":43,"context_line":"SR-IOV technology using the concept of port profiles. Port profiles are"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1ae5cdf2_0f8fb5cd","line":40,"in_reply_to":"1ae5cdf2_3c80498a","updated":"2014-06-06 15:50:56.000000000","message":"Done","commit_id":"739a8b3c48c2fd75256e0db5a1d3221c6390dd03"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"05fa4cc1b086f8f0c68ee5edf2a9e29933faed32","unresolved":false,"context_lines":[{"line_number":39,"context_line":"direct connection with the upstream switch, the \"direct\" mode does not support"},{"line_number":40,"context_line":"live migration of the VMs that it is attached to."},{"line_number":41,"context_line":""},{"line_number":42,"context_line":"4. Cisco VM-FEX technology is based on the 802.1qbh and works on top of the"},{"line_number":43,"context_line":"SR-IOV technology using the concept of port profiles. Port profiles are"},{"line_number":44,"context_line":"configuration entities that specify additional config that needs to be applied"},{"line_number":45,"context_line":"on the VF. This config includes the vlan-id, QoS (not applicable in OS for now)"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1ae5cdf2_7c4d7199","line":42,"updated":"2014-06-05 20:50:26.000000000","message":"Didn\u0027t 802.1Qbg and 802.1Qbg merge into 802.1br?","commit_id":"739a8b3c48c2fd75256e0db5a1d3221c6390dd03"},{"author":{"_account_id":6697,"name":"Sandhya Dasu","email":"sandhya.openinfra@gmail.com","username":"sadasu"},"change_message_id":"557352650be536d8def2f7e5cdaaf1a138bfa402","unresolved":false,"context_lines":[{"line_number":39,"context_line":"direct connection with the upstream switch, the \"direct\" mode does not support"},{"line_number":40,"context_line":"live migration of the VMs that it is attached to."},{"line_number":41,"context_line":""},{"line_number":42,"context_line":"4. Cisco VM-FEX technology is based on the 802.1qbh and works on top of the"},{"line_number":43,"context_line":"SR-IOV technology using the concept of port profiles. Port profiles are"},{"line_number":44,"context_line":"configuration entities that specify additional config that needs to be applied"},{"line_number":45,"context_line":"on the VF. This config includes the vlan-id, QoS (not applicable in OS for now)"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1ae5cdf2_4a644b49","line":42,"in_reply_to":"1ae5cdf2_7c4d7199","updated":"2014-06-06 15:50:56.000000000","message":"I think so. Waiting to obtain some documentation to confirm that. Will update BP once I have that.","commit_id":"739a8b3c48c2fd75256e0db5a1d3221c6390dd03"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"05fa4cc1b086f8f0c68ee5edf2a9e29933faed32","unresolved":false,"context_lines":[{"line_number":71,"context_line":"4. The mechanism driver also expects to get the physical network information"},{"line_number":72,"context_line":"as part of port binding:profile at the time of bind port. "},{"line_number":73,"context_line":""},{"line_number":74,"context_line":"5. When a neutron port is being bound to a VM, the mechanism driver"},{"line_number":75,"context_line":"uses the segmentation-id associated with the network to determine if a new"},{"line_number":76,"context_line":"port profile needs to be created. According to the DB maintained by the ML2"},{"line_number":77,"context_line":"driver, if a port profile with that vlan_id already exists, then it re-uses"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1ae5cdf2_fc0ee139","line":74,"updated":"2014-06-05 20:50:26.000000000","message":"So will this driver not work with port-profiles configured in UCSM? It\u0027s creating them itself here?","commit_id":"739a8b3c48c2fd75256e0db5a1d3221c6390dd03"},{"author":{"_account_id":6697,"name":"Sandhya Dasu","email":"sandhya.openinfra@gmail.com","username":"sadasu"},"change_message_id":"557352650be536d8def2f7e5cdaaf1a138bfa402","unresolved":false,"context_lines":[{"line_number":71,"context_line":"4. The mechanism driver also expects to get the physical network information"},{"line_number":72,"context_line":"as part of port binding:profile at the time of bind port. "},{"line_number":73,"context_line":""},{"line_number":74,"context_line":"5. When a neutron port is being bound to a VM, the mechanism driver"},{"line_number":75,"context_line":"uses the segmentation-id associated with the network to determine if a new"},{"line_number":76,"context_line":"port profile needs to be created. According to the DB maintained by the ML2"},{"line_number":77,"context_line":"driver, if a port profile with that vlan_id already exists, then it re-uses"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1ae5cdf2_04ba3c0a","line":74,"in_reply_to":"1ae5cdf2_fc0ee139","updated":"2014-06-06 15:50:56.000000000","message":"For this driver to work with port-profiles already configured on UCSM, we thought these port profiles need to be exposed to the user/tenant in OS. Also, pre-existing port profiles could contain config like QoS that OS cannot handle today. Letting the user/tenant participate in creating or choosing pre-existing port profiles would mean exposing a vendor specific entity (port profiles) in OS which is not preferred. \n\nWe thought the way around it would be to create port profiles within the mech driver. That way we(mech driver) control what is configured within these port profiles while keeping it hidden from a OS tenant.\n\nDo you want me to add this reasoning to the BP itself?","commit_id":"739a8b3c48c2fd75256e0db5a1d3221c6390dd03"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"05fa4cc1b086f8f0c68ee5edf2a9e29933faed32","unresolved":false,"context_lines":[{"line_number":116,"context_line":"Security impact"},{"line_number":117,"context_line":"---------------"},{"line_number":118,"context_line":"None. The connection to the XML API layer on the UCS Manager is via HTTP/HTTPS."},{"line_number":119,"context_line":"Since, traffic from the VM completely bypasses the host, no security groups are"},{"line_number":120,"context_line":"enforced when this mechanism driver binds the port. "},{"line_number":121,"context_line":""},{"line_number":122,"context_line":"Notifications impact"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1ae5cdf2_b0a71d0a","line":119,"updated":"2014-06-05 20:50:26.000000000","message":"I would say the lack of security groups are a pretty big issue, and I\u0027d highlight that at the front of this section.\n\nAlternatively, is there anyway to enforce security groups in the Palo adapter itself? I thought they had some limited ACL support? Maybe, like the OVS security groups BP, we could enforce 80% of existing security groups?","commit_id":"739a8b3c48c2fd75256e0db5a1d3221c6390dd03"},{"author":{"_account_id":6697,"name":"Sandhya Dasu","email":"sandhya.openinfra@gmail.com","username":"sadasu"},"change_message_id":"557352650be536d8def2f7e5cdaaf1a138bfa402","unresolved":false,"context_lines":[{"line_number":116,"context_line":"Security impact"},{"line_number":117,"context_line":"---------------"},{"line_number":118,"context_line":"None. The connection to the XML API layer on the UCS Manager is via HTTP/HTTPS."},{"line_number":119,"context_line":"Since, traffic from the VM completely bypasses the host, no security groups are"},{"line_number":120,"context_line":"enforced when this mechanism driver binds the port. "},{"line_number":121,"context_line":""},{"line_number":122,"context_line":"Notifications impact"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1ae5cdf2_cf84edb3","line":119,"in_reply_to":"1ae5cdf2_b0a71d0a","updated":"2014-06-06 15:50:56.000000000","message":"ACLs can be configured on the VFs on the upstream switch. Will highlight this fact early on in the BP if that is preferred.\n\nI need to understand the OVS security groups BP before confirming applicability here. Even if it were feasible, I would like to take it up as a separate effort after watching their BP and implementation.","commit_id":"739a8b3c48c2fd75256e0db5a1d3221c6390dd03"},{"author":{"_account_id":6598,"name":"Berezovsky Irena","email":"irenab.dev@gmail.com","username":"irenab"},"change_message_id":"52ffeb642e4594ccbde2979f9f30019514078e3d","unresolved":false,"context_lines":[{"line_number":95,"context_line":""},{"line_number":96,"context_line":"8. In the case of NICs that support SR-IOV and not VM-FEX (for example, the"},{"line_number":97,"context_line":"Intel NIC), the portbinding profile:vif_details attribute is populated with"},{"line_number":98,"context_line":"the vlan_id. This vlan_id is then written into the VM\u0027s domain XML file by"},{"line_number":99,"context_line":"Nova\u0027s generic vif driver."},{"line_number":100,"context_line":""},{"line_number":101,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"1ae5cdf2_6f325d5f","line":98,"updated":"2014-06-11 20:51:46.000000000","message":"The Intel NIC case is covered by  ML2 Mechanism Driver for SR-IOV NIC switching","commit_id":"3827ad04e2eaf09f6c7cecc1d5d80fdc2e44e3bf"},{"author":{"_account_id":6598,"name":"Berezovsky Irena","email":"irenab.dev@gmail.com","username":"irenab"},"change_message_id":"1d5b252ead21b444c5f2719065c50844bf2279a8","unresolved":false,"context_lines":[{"line_number":95,"context_line":""},{"line_number":96,"context_line":"8. In the case of NICs that support SR-IOV and not VM-FEX (for example, the"},{"line_number":97,"context_line":"Intel NIC), the portbinding profile:vif_details attribute is populated with"},{"line_number":98,"context_line":"the vlan_id. This vlan_id is then written into the VM\u0027s domain XML file by"},{"line_number":99,"context_line":"Nova\u0027s generic vif driver."},{"line_number":100,"context_line":""},{"line_number":101,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"1ae5cdf2_ba916af3","line":98,"in_reply_to":"1ae5cdf2_3ed5cae4","updated":"2014-06-17 11:02:12.000000000","message":"My assumption was that Intel NIC that does not support VM-FEX has embedded switching cappabilities, so going with embedded switch ML2 Mech driver, will support VIF binding in the same way as it does for Mellanox NIC and agent will take care of port enable/disable. Agent is not required for port binding, just to handle port updates","commit_id":"3827ad04e2eaf09f6c7cecc1d5d80fdc2e44e3bf"},{"author":{"_account_id":6697,"name":"Sandhya Dasu","email":"sandhya.openinfra@gmail.com","username":"sadasu"},"change_message_id":"124684818b61956508b1541e6513e98f2e36e40e","unresolved":false,"context_lines":[{"line_number":95,"context_line":""},{"line_number":96,"context_line":"8. In the case of NICs that support SR-IOV and not VM-FEX (for example, the"},{"line_number":97,"context_line":"Intel NIC), the portbinding profile:vif_details attribute is populated with"},{"line_number":98,"context_line":"the vlan_id. This vlan_id is then written into the VM\u0027s domain XML file by"},{"line_number":99,"context_line":"Nova\u0027s generic vif driver."},{"line_number":100,"context_line":""},{"line_number":101,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"1ae5cdf2_3ed5cae4","line":98,"in_reply_to":"1ae5cdf2_6f325d5f","updated":"2014-06-13 16:01:46.000000000","message":"Couple of reasons why I decided to support this in the current mech driver:\n\n1. ML2 Mech driver for AR-IOV NIC switching may have a dependency on MLNX L2 agent. Not sure about this though.\n\n2. For completeness. In other words, this mech driver should be able to support all SR-IOV NICs that are currently supported by the UCS Manager subsystem.","commit_id":"3827ad04e2eaf09f6c7cecc1d5d80fdc2e44e3bf"},{"author":{"_account_id":6598,"name":"Berezovsky Irena","email":"irenab.dev@gmail.com","username":"irenab"},"change_message_id":"52ffeb642e4594ccbde2979f9f30019514078e3d","unresolved":false,"context_lines":[{"line_number":106,"context_line":"Data model impact"},{"line_number":107,"context_line":"-----------------"},{"line_number":108,"context_line":""},{"line_number":109,"context_line":"One new data model is created by this driver to keep track of port profiles"},{"line_number":110,"context_line":"created by Openstack. Other port profiles can exist on the UCS Manager that this"},{"line_number":111,"context_line":"driver does not care about."},{"line_number":112,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"1ae5cdf2_ef73cd13","line":109,"updated":"2014-06-11 20:51:46.000000000","message":"How port profiles are created?","commit_id":"3827ad04e2eaf09f6c7cecc1d5d80fdc2e44e3bf"},{"author":{"_account_id":6697,"name":"Sandhya Dasu","email":"sandhya.openinfra@gmail.com","username":"sadasu"},"change_message_id":"124684818b61956508b1541e6513e98f2e36e40e","unresolved":false,"context_lines":[{"line_number":106,"context_line":"Data model impact"},{"line_number":107,"context_line":"-----------------"},{"line_number":108,"context_line":""},{"line_number":109,"context_line":"One new data model is created by this driver to keep track of port profiles"},{"line_number":110,"context_line":"created by Openstack. Other port profiles can exist on the UCS Manager that this"},{"line_number":111,"context_line":"driver does not care about."},{"line_number":112,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"1ae5cdf2_10f53682","line":109,"in_reply_to":"1ae5cdf2_ef73cd13","updated":"2014-06-13 16:01:46.000000000","message":"Added this information to the \"Proposed Change\" section.","commit_id":"3827ad04e2eaf09f6c7cecc1d5d80fdc2e44e3bf"},{"author":{"_account_id":6598,"name":"Berezovsky Irena","email":"irenab.dev@gmail.com","username":"irenab"},"change_message_id":"52ffeb642e4594ccbde2979f9f30019514078e3d","unresolved":false,"context_lines":[{"line_number":111,"context_line":"driver does not care about."},{"line_number":112,"context_line":""},{"line_number":113,"context_line":"PortProfile: Tracks the vlan-id associated with a given port profile and the"},{"line_number":114,"context_line":"list of VFs and port ids that are currently configured with this PortProfile."},{"line_number":115,"context_line":""},{"line_number":116,"context_line":"REST API impact"},{"line_number":117,"context_line":"---------------"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1ae5cdf2_eff82d4c","line":114,"updated":"2014-06-11 20:51:46.000000000","message":"Why it\u0027s required to maintain the list of VFs for port profile? Port entry  contains this data.","commit_id":"3827ad04e2eaf09f6c7cecc1d5d80fdc2e44e3bf"},{"author":{"_account_id":6598,"name":"Berezovsky Irena","email":"irenab.dev@gmail.com","username":"irenab"},"change_message_id":"1d5b252ead21b444c5f2719065c50844bf2279a8","unresolved":false,"context_lines":[{"line_number":111,"context_line":"driver does not care about."},{"line_number":112,"context_line":""},{"line_number":113,"context_line":"PortProfile: Tracks the vlan-id associated with a given port profile and the"},{"line_number":114,"context_line":"list of VFs and port ids that are currently configured with this PortProfile."},{"line_number":115,"context_line":""},{"line_number":116,"context_line":"REST API impact"},{"line_number":117,"context_line":"---------------"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1ae5cdf2_fa2f72a5","line":114,"in_reply_to":"1ae5cdf2_d03caee3","updated":"2014-06-17 11:02:12.000000000","message":"I may miss something, but port is a core object in the neutron, so it is stored in the DB. Associated SR-IOV port pci_slot info is part of the port_profile and also persistent as part of the port entry. If you require new mapping table, just worth to define it columns.","commit_id":"3827ad04e2eaf09f6c7cecc1d5d80fdc2e44e3bf"},{"author":{"_account_id":6697,"name":"Sandhya Dasu","email":"sandhya.openinfra@gmail.com","username":"sadasu"},"change_message_id":"124684818b61956508b1541e6513e98f2e36e40e","unresolved":false,"context_lines":[{"line_number":111,"context_line":"driver does not care about."},{"line_number":112,"context_line":""},{"line_number":113,"context_line":"PortProfile: Tracks the vlan-id associated with a given port profile and the"},{"line_number":114,"context_line":"list of VFs and port ids that are currently configured with this PortProfile."},{"line_number":115,"context_line":""},{"line_number":116,"context_line":"REST API impact"},{"line_number":117,"context_line":"---------------"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1ae5cdf2_d03caee3","line":114,"in_reply_to":"1ae5cdf2_eff82d4c","updated":"2014-06-13 16:01:46.000000000","message":"Not sure if the port entry would be persistent across Neutron server reboots. In a future release when there is integration with Horizon, it will be useful for the mech driver to furnish details about which VF is using which port profile. But this is still TBD.","commit_id":"3827ad04e2eaf09f6c7cecc1d5d80fdc2e44e3bf"},{"author":{"_account_id":6697,"name":"Sandhya Dasu","email":"sandhya.openinfra@gmail.com","username":"sadasu"},"change_message_id":"752e71386c1a61ff417fc735483e8f7aaf83134a","unresolved":false,"context_lines":[{"line_number":111,"context_line":"driver does not care about."},{"line_number":112,"context_line":""},{"line_number":113,"context_line":"PortProfile: Tracks the vlan-id associated with a given port profile and the"},{"line_number":114,"context_line":"list of VFs and port ids that are currently configured with this PortProfile."},{"line_number":115,"context_line":""},{"line_number":116,"context_line":"REST API impact"},{"line_number":117,"context_line":"---------------"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1ae5cdf2_faa673aa","line":114,"in_reply_to":"1ae5cdf2_fa2f72a5","updated":"2014-06-17 18:09:08.000000000","message":"Not storing VFs in the db anymore. Please refer to the latest version of the doc.","commit_id":"3827ad04e2eaf09f6c7cecc1d5d80fdc2e44e3bf"},{"author":{"_account_id":6598,"name":"Berezovsky Irena","email":"irenab.dev@gmail.com","username":"irenab"},"change_message_id":"52ffeb642e4594ccbde2979f9f30019514078e3d","unresolved":false,"context_lines":[{"line_number":131,"context_line":"Other end user impact"},{"line_number":132,"context_line":"---------------------"},{"line_number":133,"context_line":"No user impact. As mentioned earlier, did not want to expose the port profile_id"},{"line_number":134,"context_line":"to the user since this is a verndor specific entity. Instead, managing"},{"line_number":135,"context_line":"allocation of port profiles internally within the driver."},{"line_number":136,"context_line":""},{"line_number":137,"context_line":"Performance Impact"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1ae5cdf2_8fa16948","line":134,"updated":"2014-06-11 20:51:46.000000000","message":"Typo: vendor","commit_id":"3827ad04e2eaf09f6c7cecc1d5d80fdc2e44e3bf"},{"author":{"_account_id":6697,"name":"Sandhya Dasu","email":"sandhya.openinfra@gmail.com","username":"sadasu"},"change_message_id":"124684818b61956508b1541e6513e98f2e36e40e","unresolved":false,"context_lines":[{"line_number":131,"context_line":"Other end user impact"},{"line_number":132,"context_line":"---------------------"},{"line_number":133,"context_line":"No user impact. As mentioned earlier, did not want to expose the port profile_id"},{"line_number":134,"context_line":"to the user since this is a verndor specific entity. Instead, managing"},{"line_number":135,"context_line":"allocation of port profiles internally within the driver."},{"line_number":136,"context_line":""},{"line_number":137,"context_line":"Performance Impact"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1ae5cdf2_5e2c5602","line":134,"in_reply_to":"1ae5cdf2_8fa16948","updated":"2014-06-13 16:01:46.000000000","message":"Done","commit_id":"3827ad04e2eaf09f6c7cecc1d5d80fdc2e44e3bf"},{"author":{"_account_id":6598,"name":"Berezovsky Irena","email":"irenab.dev@gmail.com","username":"irenab"},"change_message_id":"52ffeb642e4594ccbde2979f9f30019514078e3d","unresolved":false,"context_lines":[{"line_number":146,"context_line":"The deployer must provide the following in order to be able to connect to a UCS"},{"line_number":147,"context_line":"Manager and add support for SR-IOV ports."},{"line_number":148,"context_line":""},{"line_number":149,"context_line":"1. IP address of UCS Manager."},{"line_number":150,"context_line":"2. Admin Username and password to log into UCS Manager."},{"line_number":151,"context_line":"3. Add \"cisco_ucsm\" as a ML2 driver to handle SR-IOV port configuration."},{"line_number":152,"context_line":"4. Add the \"vlan\" type driver. Currently, this mechansim driver supports only"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1ae5cdf2_0f52b934","line":149,"updated":"2014-06-11 20:51:46.000000000","message":"Should it be defined in config file?","commit_id":"3827ad04e2eaf09f6c7cecc1d5d80fdc2e44e3bf"},{"author":{"_account_id":6697,"name":"Sandhya Dasu","email":"sandhya.openinfra@gmail.com","username":"sadasu"},"change_message_id":"124684818b61956508b1541e6513e98f2e36e40e","unresolved":false,"context_lines":[{"line_number":146,"context_line":"The deployer must provide the following in order to be able to connect to a UCS"},{"line_number":147,"context_line":"Manager and add support for SR-IOV ports."},{"line_number":148,"context_line":""},{"line_number":149,"context_line":"1. IP address of UCS Manager."},{"line_number":150,"context_line":"2. Admin Username and password to log into UCS Manager."},{"line_number":151,"context_line":"3. Add \"cisco_ucsm\" as a ML2 driver to handle SR-IOV port configuration."},{"line_number":152,"context_line":"4. Add the \"vlan\" type driver. Currently, this mechansim driver supports only"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1ae5cdf2_3b8e9379","line":149,"in_reply_to":"1ae5cdf2_0f52b934","updated":"2014-06-13 16:01:46.000000000","message":"Done","commit_id":"3827ad04e2eaf09f6c7cecc1d5d80fdc2e44e3bf"},{"author":{"_account_id":8645,"name":"Trinath Somanchi","email":"trinath.somanchi@freescale.com","username":"trinaths"},"change_message_id":"db3efc5d8de58c3a021b37dcafbd6594e5dc8270","unresolved":false,"context_lines":[{"line_number":14,"context_line":""},{"line_number":15,"context_line":"The purpose of this blueprint is to add support for Cisco UCS Manager into"},{"line_number":16,"context_line":"Openstack Neutron. This plugin for Cisco UCS Manager is implemented as a ML2"},{"line_number":17,"context_line":"mech driver."},{"line_number":18,"context_line":""},{"line_number":19,"context_line":"Problem description"},{"line_number":20,"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":5,"id":"1ae5cdf2_7bbc9bdc","line":17,"updated":"2014-06-13 16:24:14.000000000","message":"please change mech to mechanism","commit_id":"dccde81668767a13fbc2fff94b477809bf12de55"},{"author":{"_account_id":6697,"name":"Sandhya Dasu","email":"sandhya.openinfra@gmail.com","username":"sadasu"},"change_message_id":"fa2fc96038cdeab099da2a2675e8dae101a93ca7","unresolved":false,"context_lines":[{"line_number":14,"context_line":""},{"line_number":15,"context_line":"The purpose of this blueprint is to add support for Cisco UCS Manager into"},{"line_number":16,"context_line":"Openstack Neutron. This plugin for Cisco UCS Manager is implemented as a ML2"},{"line_number":17,"context_line":"mech driver."},{"line_number":18,"context_line":""},{"line_number":19,"context_line":"Problem description"},{"line_number":20,"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":5,"id":"1ae5cdf2_08406f06","line":17,"in_reply_to":"1ae5cdf2_7bbc9bdc","updated":"2014-06-17 18:09:23.000000000","message":"Done","commit_id":"dccde81668767a13fbc2fff94b477809bf12de55"},{"author":{"_account_id":8645,"name":"Trinath Somanchi","email":"trinath.somanchi@freescale.com","username":"trinaths"},"change_message_id":"db3efc5d8de58c3a021b37dcafbd6594e5dc8270","unresolved":false,"context_lines":[{"line_number":87,"context_line":"want to expose this to the cloud admin or the tenant. So, port profiles are"},{"line_number":88,"context_line":"created and maintained completely behind the scenes by the ML2 driver."},{"line_number":89,"context_line":""},{"line_number":90,"context_line":"7. Port profiles created by this mech driver will have the name OS-PP-\u003cvlan-id\u003e."},{"line_number":91,"context_line":"The process of creating a port profile on the UCS Manager involves:"},{"line_number":92,"context_line":"    1. Connecting to the UCS manager and starting a new transaction"},{"line_number":93,"context_line":"    2. Creating a Fabric Vlan managed object corresponding to the vlan-id"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1ae5cdf2_7bb81bc8","line":90,"updated":"2014-06-13 16:24:14.000000000","message":"mech \u003d mechanism","commit_id":"dccde81668767a13fbc2fff94b477809bf12de55"},{"author":{"_account_id":6697,"name":"Sandhya Dasu","email":"sandhya.openinfra@gmail.com","username":"sadasu"},"change_message_id":"fa2fc96038cdeab099da2a2675e8dae101a93ca7","unresolved":false,"context_lines":[{"line_number":87,"context_line":"want to expose this to the cloud admin or the tenant. So, port profiles are"},{"line_number":88,"context_line":"created and maintained completely behind the scenes by the ML2 driver."},{"line_number":89,"context_line":""},{"line_number":90,"context_line":"7. Port profiles created by this mech driver will have the name OS-PP-\u003cvlan-id\u003e."},{"line_number":91,"context_line":"The process of creating a port profile on the UCS Manager involves:"},{"line_number":92,"context_line":"    1. Connecting to the UCS manager and starting a new transaction"},{"line_number":93,"context_line":"    2. Creating a Fabric Vlan managed object corresponding to the vlan-id"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1ae5cdf2_d499bed1","line":90,"in_reply_to":"1ae5cdf2_7bb81bc8","updated":"2014-06-17 18:09:23.000000000","message":"Done","commit_id":"dccde81668767a13fbc2fff94b477809bf12de55"},{"author":{"_account_id":8645,"name":"Trinath Somanchi","email":"trinath.somanchi@freescale.com","username":"trinaths"},"change_message_id":"db3efc5d8de58c3a021b37dcafbd6594e5dc8270","unresolved":false,"context_lines":[{"line_number":107,"context_line":"Intel NIC), the portbinding profile:vif_details attribute is populated with"},{"line_number":108,"context_line":"the vlan_id. This vlan_id is then written into the VM\u0027s domain XML file by"},{"line_number":109,"context_line":"Nova\u0027s generic vif driver."},{"line_number":110,"context_line":""},{"line_number":111,"context_line":""},{"line_number":112,"context_line":"Alternatives"},{"line_number":113,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1ae5cdf2_dba04f44","line":110,"updated":"2014-06-13 16:24:14.000000000","message":"(if possible) can you provide a sequence diagram with the flow of events, it makes a clear picture on overall data flow.","commit_id":"dccde81668767a13fbc2fff94b477809bf12de55"},{"author":{"_account_id":6697,"name":"Sandhya Dasu","email":"sandhya.openinfra@gmail.com","username":"sadasu"},"change_message_id":"fa2fc96038cdeab099da2a2675e8dae101a93ca7","unresolved":false,"context_lines":[{"line_number":107,"context_line":"Intel NIC), the portbinding profile:vif_details attribute is populated with"},{"line_number":108,"context_line":"the vlan_id. This vlan_id is then written into the VM\u0027s domain XML file by"},{"line_number":109,"context_line":"Nova\u0027s generic vif driver."},{"line_number":110,"context_line":""},{"line_number":111,"context_line":""},{"line_number":112,"context_line":"Alternatives"},{"line_number":113,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1ae5cdf2_6891eef0","line":110,"in_reply_to":"1ae5cdf2_dba04f44","updated":"2014-06-17 18:09:23.000000000","message":"Working on one. Will post along with next update if the diagram is determined to add value.","commit_id":"dccde81668767a13fbc2fff94b477809bf12de55"},{"author":{"_account_id":8645,"name":"Trinath Somanchi","email":"trinath.somanchi@freescale.com","username":"trinaths"},"change_message_id":"db3efc5d8de58c3a021b37dcafbd6594e5dc8270","unresolved":false,"context_lines":[{"line_number":121,"context_line":"driver does not care about."},{"line_number":122,"context_line":""},{"line_number":123,"context_line":"PortProfile: Tracks the vlan-id associated with a given port profile and the"},{"line_number":124,"context_line":"list of VFs and port ids that are currently configured with this PortProfile."},{"line_number":125,"context_line":""},{"line_number":126,"context_line":"REST API impact"},{"line_number":127,"context_line":"---------------"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1ae5cdf2_3b75b3f9","line":124,"updated":"2014-06-13 16:24:14.000000000","message":"is PortProfile a DB table? please provide the column names and datatypes.","commit_id":"dccde81668767a13fbc2fff94b477809bf12de55"},{"author":{"_account_id":6697,"name":"Sandhya Dasu","email":"sandhya.openinfra@gmail.com","username":"sadasu"},"change_message_id":"fa2fc96038cdeab099da2a2675e8dae101a93ca7","unresolved":false,"context_lines":[{"line_number":121,"context_line":"driver does not care about."},{"line_number":122,"context_line":""},{"line_number":123,"context_line":"PortProfile: Tracks the vlan-id associated with a given port profile and the"},{"line_number":124,"context_line":"list of VFs and port ids that are currently configured with this PortProfile."},{"line_number":125,"context_line":""},{"line_number":126,"context_line":"REST API impact"},{"line_number":127,"context_line":"---------------"}],"source_content_type":"text/x-rst","patch_set":5,"id":"1ae5cdf2_a803f6bc","line":124,"in_reply_to":"1ae5cdf2_3b75b3f9","updated":"2014-06-17 18:09:23.000000000","message":"Done","commit_id":"dccde81668767a13fbc2fff94b477809bf12de55"},{"author":{"_account_id":8645,"name":"Trinath Somanchi","email":"trinath.somanchi@freescale.com","username":"trinaths"},"change_message_id":"db3efc5d8de58c3a021b37dcafbd6594e5dc8270","unresolved":false,"context_lines":[{"line_number":160,"context_line":"2. Admin Username and password to log into UCS Manager."},{"line_number":161,"context_line":"3. Add \"cisco_ucsm\" as a ML2 driver to handle SR-IOV port configuration."},{"line_number":162,"context_line":"4. Add the \"vlan\" type driver. Currently, this mechansim driver supports only"},{"line_number":163,"context_line":"   the VLAN type driver."},{"line_number":164,"context_line":""},{"line_number":165,"context_line":"These should be provided in /etc/neutron/plugins/ml2/ml2_conf_cisco.ini."},{"line_number":166,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"1ae5cdf2_9bc167e6","line":163,"updated":"2014-06-13 16:24:14.000000000","message":"please provide a sample section on how the new configuration looks like with possible default values.","commit_id":"dccde81668767a13fbc2fff94b477809bf12de55"},{"author":{"_account_id":6697,"name":"Sandhya Dasu","email":"sandhya.openinfra@gmail.com","username":"sadasu"},"change_message_id":"fa2fc96038cdeab099da2a2675e8dae101a93ca7","unresolved":false,"context_lines":[{"line_number":160,"context_line":"2. Admin Username and password to log into UCS Manager."},{"line_number":161,"context_line":"3. Add \"cisco_ucsm\" as a ML2 driver to handle SR-IOV port configuration."},{"line_number":162,"context_line":"4. Add the \"vlan\" type driver. Currently, this mechansim driver supports only"},{"line_number":163,"context_line":"   the VLAN type driver."},{"line_number":164,"context_line":""},{"line_number":165,"context_line":"These should be provided in /etc/neutron/plugins/ml2/ml2_conf_cisco.ini."},{"line_number":166,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"1ae5cdf2_88e55f3a","line":163,"in_reply_to":"1ae5cdf2_9bc167e6","updated":"2014-06-17 18:09:23.000000000","message":"Done","commit_id":"dccde81668767a13fbc2fff94b477809bf12de55"},{"author":{"_account_id":490,"name":"Sumit Naiksatam","email":"sumitnaiksatam@gmail.com","username":"snaiksat"},"change_message_id":"01d8efa3bf8f0a01573120a32e7bed9843ad1356","unresolved":false,"context_lines":[{"line_number":27,"context_line":""},{"line_number":28,"context_line":"2. Cisco VM-FEX technology is based on SR-IOV technology which allows a single"},{"line_number":29,"context_line":"PCIe physical device (PF - physical function) to be divided into multiple"},{"line_number":30,"context_line":"logical devices (VF - virtual functions)."},{"line_number":31,"context_line":""},{"line_number":32,"context_line":"3. With SR-IOV and Cisco VM-FEX a VM\u0027s port can be configured in either the"},{"line_number":33,"context_line":"\"direct\" or \"macvtap\" modes. In the \"direct\" mode, the VM\u0027s port is connected"}],"source_content_type":"text/x-rst","patch_set":6,"id":"baada198_73bcbbbb","line":30,"updated":"2014-07-07 19:54:31.000000000","message":"nit: It will be good to have a reference to a VM-FEX document/web-link here.","commit_id":"3c1d41fe71d6d09b912a3b45dacecbe79d3a43fb"},{"author":{"_account_id":6697,"name":"Sandhya Dasu","email":"sandhya.openinfra@gmail.com","username":"sadasu"},"change_message_id":"56a1db7544f10a18a036fedc60dd6ad8aa767f92","unresolved":false,"context_lines":[{"line_number":27,"context_line":""},{"line_number":28,"context_line":"2. Cisco VM-FEX technology is based on SR-IOV technology which allows a single"},{"line_number":29,"context_line":"PCIe physical device (PF - physical function) to be divided into multiple"},{"line_number":30,"context_line":"logical devices (VF - virtual functions)."},{"line_number":31,"context_line":""},{"line_number":32,"context_line":"3. With SR-IOV and Cisco VM-FEX a VM\u0027s port can be configured in either the"},{"line_number":33,"context_line":"\"direct\" or \"macvtap\" modes. In the \"direct\" mode, the VM\u0027s port is connected"}],"source_content_type":"text/x-rst","patch_set":6,"id":"baada198_bbbff3fb","line":30,"in_reply_to":"baada198_73bcbbbb","updated":"2014-07-08 11:59:31.000000000","message":"Done","commit_id":"3c1d41fe71d6d09b912a3b45dacecbe79d3a43fb"},{"author":{"_account_id":490,"name":"Sumit Naiksatam","email":"sumitnaiksatam@gmail.com","username":"snaiksat"},"change_message_id":"01d8efa3bf8f0a01573120a32e7bed9843ad1356","unresolved":false,"context_lines":[{"line_number":42,"context_line":"4. Cisco VM-FEX technology is based on the 802.1qbh and works on top of the"},{"line_number":43,"context_line":"SR-IOV technology using the concept of port profiles. Port profiles are"},{"line_number":44,"context_line":"configuration entities that specify additional config that needs to be applied"},{"line_number":45,"context_line":"on the VF. This config includes the vlan-id, QoS (not applicable in OS for now)"},{"line_number":46,"context_line":"and the mode (direct/macvtap)."},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"5. This mechanism driver needs to configure port profiles on the UCS Manager"}],"source_content_type":"text/x-rst","patch_set":6,"id":"baada198_13da9f16","line":45,"updated":"2014-07-07 19:54:31.000000000","message":"OS -\u003e OpenStack?","commit_id":"3c1d41fe71d6d09b912a3b45dacecbe79d3a43fb"},{"author":{"_account_id":6697,"name":"Sandhya Dasu","email":"sandhya.openinfra@gmail.com","username":"sadasu"},"change_message_id":"56a1db7544f10a18a036fedc60dd6ad8aa767f92","unresolved":false,"context_lines":[{"line_number":42,"context_line":"4. Cisco VM-FEX technology is based on the 802.1qbh and works on top of the"},{"line_number":43,"context_line":"SR-IOV technology using the concept of port profiles. Port profiles are"},{"line_number":44,"context_line":"configuration entities that specify additional config that needs to be applied"},{"line_number":45,"context_line":"on the VF. This config includes the vlan-id, QoS (not applicable in OS for now)"},{"line_number":46,"context_line":"and the mode (direct/macvtap)."},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"5. This mechanism driver needs to configure port profiles on the UCS Manager"}],"source_content_type":"text/x-rst","patch_set":6,"id":"baada198_3b3be39d","line":45,"in_reply_to":"baada198_13da9f16","updated":"2014-07-08 11:59:31.000000000","message":"Yes. Expanded for clarity.","commit_id":"3c1d41fe71d6d09b912a3b45dacecbe79d3a43fb"},{"author":{"_account_id":107,"name":"Arvind Somya","email":"arvind.somya@gmail.com","username":"asomya"},"change_message_id":"a3f341c756b67142d4bfa1915cf95fcbc752081f","unresolved":false,"context_lines":[{"line_number":57,"context_line":""},{"line_number":58,"context_line":"8. Security groups cannot be applied on the host for SR-IOV and VM-FEX ports."},{"line_number":59,"context_line":"Since the VFs appear as interfaces on the upstream switch, ACLs can be applied"},{"line_number":60,"context_line":"on the VFs at the upstream switch."},{"line_number":61,"context_line":""},{"line_number":62,"context_line":""},{"line_number":63,"context_line":"Proposed change"}],"source_content_type":"text/x-rst","patch_set":6,"id":"baada198_fd097431","line":60,"updated":"2014-07-07 22:29:10.000000000","message":"This problem doesn\u0027t have a corresponding solution in the Proposed Change section, Will that be a follow up patch? Would be good to mention that security group support will be coming in the future and this solution will basically require security groups to be turned off.","commit_id":"3c1d41fe71d6d09b912a3b45dacecbe79d3a43fb"},{"author":{"_account_id":6697,"name":"Sandhya Dasu","email":"sandhya.openinfra@gmail.com","username":"sadasu"},"change_message_id":"56a1db7544f10a18a036fedc60dd6ad8aa767f92","unresolved":false,"context_lines":[{"line_number":57,"context_line":""},{"line_number":58,"context_line":"8. Security groups cannot be applied on the host for SR-IOV and VM-FEX ports."},{"line_number":59,"context_line":"Since the VFs appear as interfaces on the upstream switch, ACLs can be applied"},{"line_number":60,"context_line":"on the VFs at the upstream switch."},{"line_number":61,"context_line":""},{"line_number":62,"context_line":""},{"line_number":63,"context_line":"Proposed change"}],"source_content_type":"text/x-rst","patch_set":6,"id":"baada198_becc4163","line":60,"in_reply_to":"baada198_4d3d4b8e","updated":"2014-07-08 11:59:31.000000000","message":"We are not considering this as optional. SR-IOV or VM-FEX ports are directly connected to the upstream switch where ACLs can be applied on their interfaces. This ML2 driver does not talk to the upstream switch. The ACLs have to be configured via the ML2 driver associated with that switch. Again will add more detailed explanation in the spec itself.","commit_id":"3c1d41fe71d6d09b912a3b45dacecbe79d3a43fb"},{"author":{"_account_id":6697,"name":"Sandhya Dasu","email":"sandhya.openinfra@gmail.com","username":"sadasu"},"change_message_id":"56a1db7544f10a18a036fedc60dd6ad8aa767f92","unresolved":false,"context_lines":[{"line_number":57,"context_line":""},{"line_number":58,"context_line":"8. Security groups cannot be applied on the host for SR-IOV and VM-FEX ports."},{"line_number":59,"context_line":"Since the VFs appear as interfaces on the upstream switch, ACLs can be applied"},{"line_number":60,"context_line":"on the VFs at the upstream switch."},{"line_number":61,"context_line":""},{"line_number":62,"context_line":""},{"line_number":63,"context_line":"Proposed change"}],"source_content_type":"text/x-rst","patch_set":6,"id":"baada198_fb8ecbcf","line":60,"in_reply_to":"baada198_fd097431","updated":"2014-07-08 11:59:31.000000000","message":"An Openstack cloud with VM-FEX and/or SR-IOV ports will almost always also have regular neutron virtual ports. We don\u0027t envision a solution where a cloud is comprised purely of VM-FEX/SR-IOV ports. For that reason, security groups should not be turned off and they can be applied to regular neutron ports as before. Will add more information about this in the spec.","commit_id":"3c1d41fe71d6d09b912a3b45dacecbe79d3a43fb"},{"author":{"_account_id":1923,"name":"Mohammad Banikazemi","email":"mbanikazemi@gmail.com","username":"mb-s"},"change_message_id":"a33713a3b95e3cc765efaf5b11f7ec3a676c8556","unresolved":false,"context_lines":[{"line_number":57,"context_line":""},{"line_number":58,"context_line":"8. Security groups cannot be applied on the host for SR-IOV and VM-FEX ports."},{"line_number":59,"context_line":"Since the VFs appear as interfaces on the upstream switch, ACLs can be applied"},{"line_number":60,"context_line":"on the VFs at the upstream switch."},{"line_number":61,"context_line":""},{"line_number":62,"context_line":""},{"line_number":63,"context_line":"Proposed change"}],"source_content_type":"text/x-rst","patch_set":6,"id":"baada198_4d3d4b8e","line":60,"in_reply_to":"baada198_fd097431","updated":"2014-07-08 03:42:17.000000000","message":"Yes, please clarify how the security group extension is dealt with. All ML2 plugins support security groups. This is not optional. Are you suggesting the noop firewall driver is to be used?","commit_id":"3c1d41fe71d6d09b912a3b45dacecbe79d3a43fb"},{"author":{"_account_id":107,"name":"Arvind Somya","email":"arvind.somya@gmail.com","username":"asomya"},"change_message_id":"a3f341c756b67142d4bfa1915cf95fcbc752081f","unresolved":false,"context_lines":[{"line_number":63,"context_line":"Proposed change"},{"line_number":64,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":65,"context_line":""},{"line_number":66,"context_line":"1. This ML2 mechanism driver communicates to the UCS manager via UCS Python SDK."},{"line_number":67,"context_line":""},{"line_number":68,"context_line":"2. There is no need for a L2 agent to be running on the compute host to"},{"line_number":69,"context_line":"configure the SR-IOV and VM-FEX ports."}],"source_content_type":"text/x-rst","patch_set":6,"id":"baada198_d8159e40","line":66,"updated":"2014-07-07 22:29:10.000000000","message":"Does this require the deployer to install an SDK, I thought it communicates with the UCSM using simple http/https requests? If it requires a separate SDK then please mention that and provide links in the deployer impact.","commit_id":"3c1d41fe71d6d09b912a3b45dacecbe79d3a43fb"},{"author":{"_account_id":6697,"name":"Sandhya Dasu","email":"sandhya.openinfra@gmail.com","username":"sadasu"},"change_message_id":"56a1db7544f10a18a036fedc60dd6ad8aa767f92","unresolved":false,"context_lines":[{"line_number":63,"context_line":"Proposed change"},{"line_number":64,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":65,"context_line":""},{"line_number":66,"context_line":"1. This ML2 mechanism driver communicates to the UCS manager via UCS Python SDK."},{"line_number":67,"context_line":""},{"line_number":68,"context_line":"2. There is no need for a L2 agent to be running on the compute host to"},{"line_number":69,"context_line":"configure the SR-IOV and VM-FEX ports."}],"source_content_type":"text/x-rst","patch_set":6,"id":"baada198_7ea3894f","line":66,"in_reply_to":"baada198_d8159e40","updated":"2014-07-08 11:59:31.000000000","message":"Yes, the deployer needs to install the UCS Python SDK. I have provided this information in the \"Dependencies\" section. Will move it to the \"Deployer Impact\" section since that seems to be a better location for this info.","commit_id":"3c1d41fe71d6d09b912a3b45dacecbe79d3a43fb"},{"author":{"_account_id":490,"name":"Sumit Naiksatam","email":"sumitnaiksatam@gmail.com","username":"snaiksat"},"change_message_id":"01d8efa3bf8f0a01573120a32e7bed9843ad1356","unresolved":false,"context_lines":[{"line_number":88,"context_line":"created and maintained completely behind the scenes by the ML2 driver."},{"line_number":89,"context_line":""},{"line_number":90,"context_line":"7. Port profiles created by this mechanism driver will have the name"},{"line_number":91,"context_line":"\"OS-PP-\u003cvlan-id\u003e\"."},{"line_number":92,"context_line":"The process of creating a port profile on the UCS Manager involves:"},{"line_number":93,"context_line":"A. Connecting to the UCS manager and starting a new transaction"},{"line_number":94,"context_line":"B. Creating a Fabric Vlan managed object corresponding to the vlan-id"}],"source_content_type":"text/x-rst","patch_set":6,"id":"baada198_3645d142","line":91,"updated":"2014-07-07 19:54:31.000000000","message":"Would the same UCS manager handle multiple OpenStack deployments? If so, would this name need to be made unique across them?","commit_id":"3c1d41fe71d6d09b912a3b45dacecbe79d3a43fb"},{"author":{"_account_id":6697,"name":"Sandhya Dasu","email":"sandhya.openinfra@gmail.com","username":"sadasu"},"change_message_id":"56a1db7544f10a18a036fedc60dd6ad8aa767f92","unresolved":false,"context_lines":[{"line_number":88,"context_line":"created and maintained completely behind the scenes by the ML2 driver."},{"line_number":89,"context_line":""},{"line_number":90,"context_line":"7. Port profiles created by this mechanism driver will have the name"},{"line_number":91,"context_line":"\"OS-PP-\u003cvlan-id\u003e\"."},{"line_number":92,"context_line":"The process of creating a port profile on the UCS Manager involves:"},{"line_number":93,"context_line":"A. Connecting to the UCS manager and starting a new transaction"},{"line_number":94,"context_line":"B. Creating a Fabric Vlan managed object corresponding to the vlan-id"}],"source_content_type":"text/x-rst","patch_set":6,"id":"baada198_c13598dc","line":91,"in_reply_to":"baada198_3645d142","updated":"2014-07-08 11:59:31.000000000","message":"Yes, the same UCS manager can handle multiple Openstack deployments. The same port profile can be re-used across these deployments as long as the Vlan-id matches.","commit_id":"3c1d41fe71d6d09b912a3b45dacecbe79d3a43fb"},{"author":{"_account_id":6598,"name":"Berezovsky Irena","email":"irenab.dev@gmail.com","username":"irenab"},"change_message_id":"ae4f5871de6b58d44244a02ea1eac598563bd5c4","unresolved":false,"context_lines":[{"line_number":107,"context_line":"9. In the case of NICs that support SR-IOV and not VM-FEX (for example, the"},{"line_number":108,"context_line":"Intel NIC), the portbinding profile:vif_details attribute is populated with"},{"line_number":109,"context_line":"the vlan_id. This vlan_id is then written into the VM\u0027s domain XML file by"},{"line_number":110,"context_line":"Nova\u0027s generic vif driver."},{"line_number":111,"context_line":""},{"line_number":112,"context_line":""},{"line_number":113,"context_line":"Alternatives"}],"source_content_type":"text/x-rst","patch_set":6,"id":"1ae5cdf2_92e45cad","line":110,"updated":"2014-06-18 05:31:17.000000000","message":"As we discussed at PCI meeting, this case is also covered by blueprint ml2-sriov-nic-switch. Would it be correct to say that  UCS Manager is not involved in port binding for Intel NIC? \nWe may want to consolidate and avoid code duplication though the code review.","commit_id":"3c1d41fe71d6d09b912a3b45dacecbe79d3a43fb"},{"author":{"_account_id":6598,"name":"Berezovsky Irena","email":"irenab.dev@gmail.com","username":"irenab"},"change_message_id":"9ecdfff7c03c50ca3f62f3db73badf0985bf1cb7","unresolved":false,"context_lines":[{"line_number":107,"context_line":"9. In the case of NICs that support SR-IOV and not VM-FEX (for example, the"},{"line_number":108,"context_line":"Intel NIC), the portbinding profile:vif_details attribute is populated with"},{"line_number":109,"context_line":"the vlan_id. This vlan_id is then written into the VM\u0027s domain XML file by"},{"line_number":110,"context_line":"Nova\u0027s generic vif driver."},{"line_number":111,"context_line":""},{"line_number":112,"context_line":""},{"line_number":113,"context_line":"Alternatives"}],"source_content_type":"text/x-rst","patch_set":6,"id":"1ae5cdf2_b2ff7401","line":110,"in_reply_to":"1ae5cdf2_57ce2f5b","updated":"2014-06-18 20:28:44.000000000","message":"I do not intend to hold this BP, especially not due to potential code duplication. If it is the use case for UCS manager, it should be supported. As long as several SR-IOV Mechanism Drivers are not deployed with regards to the same physical network and same compute nodes, I do not see any special problem here.","commit_id":"3c1d41fe71d6d09b912a3b45dacecbe79d3a43fb"},{"author":{"_account_id":6697,"name":"Sandhya Dasu","email":"sandhya.openinfra@gmail.com","username":"sadasu"},"change_message_id":"6c191973b0a326f687c272a1aa308457124de115","unresolved":false,"context_lines":[{"line_number":107,"context_line":"9. In the case of NICs that support SR-IOV and not VM-FEX (for example, the"},{"line_number":108,"context_line":"Intel NIC), the portbinding profile:vif_details attribute is populated with"},{"line_number":109,"context_line":"the vlan_id. This vlan_id is then written into the VM\u0027s domain XML file by"},{"line_number":110,"context_line":"Nova\u0027s generic vif driver."},{"line_number":111,"context_line":""},{"line_number":112,"context_line":""},{"line_number":113,"context_line":"Alternatives"}],"source_content_type":"text/x-rst","patch_set":6,"id":"1ae5cdf2_57ce2f5b","line":110,"in_reply_to":"1ae5cdf2_92e45cad","updated":"2014-06-18 15:28:32.000000000","message":"In the PCI meeting, we discussed the use case where all the servers are UCS and are being managed by a UCS manager. In that case, since this is a UCS Manager ML2 driver and not a VM-FEX specific ML2 driver, I think this driver should be able to configure all NICs that are supported on the UCS system.\n\nIntel NIC cards are supported on servers from several other vendors. When the cloud consists of the Intel NIC card on any of the other vendors that support it, they would include the generic SR-IOV NIC switch ML2 driver.\n\nWith regards, to your question regarding UCS Manager port binding Intel NIC, it actually does not bind both the Cisco NIC and Intel NIC. But, it will discover PFs and VFs in both NICs. Additional support is provided for VM-FEX in UCS Manager, which happens to be supported only on the Cisco NIC.\n\nAdding support for a particular NIC (in this case an Intel NIC) in 2 diff mech drivers is totally diff from code duplication. If you want to consolidate duplicate code, I am willing to work on that. I don\u0027t see why the BP should be held hostage for potential code duplication.","commit_id":"3c1d41fe71d6d09b912a3b45dacecbe79d3a43fb"},{"author":{"_account_id":6697,"name":"Sandhya Dasu","email":"sandhya.openinfra@gmail.com","username":"sadasu"},"change_message_id":"56a1db7544f10a18a036fedc60dd6ad8aa767f92","unresolved":false,"context_lines":[{"line_number":107,"context_line":"9. In the case of NICs that support SR-IOV and not VM-FEX (for example, the"},{"line_number":108,"context_line":"Intel NIC), the portbinding profile:vif_details attribute is populated with"},{"line_number":109,"context_line":"the vlan_id. This vlan_id is then written into the VM\u0027s domain XML file by"},{"line_number":110,"context_line":"Nova\u0027s generic vif driver."},{"line_number":111,"context_line":""},{"line_number":112,"context_line":""},{"line_number":113,"context_line":"Alternatives"}],"source_content_type":"text/x-rst","patch_set":6,"id":"baada198_21e81416","line":110,"in_reply_to":"1ae5cdf2_b2ff7401","updated":"2014-07-08 11:59:31.000000000","message":"Thanks. I understand your concern. The idea here is NOT to provide another implementation for the solution provided by the Sr-IOV NIC switch BP. I am trying my best to avoid code duplication in the implementation, but I am open to suggestions during code review.","commit_id":"3c1d41fe71d6d09b912a3b45dacecbe79d3a43fb"},{"author":{"_account_id":6685,"name":"Baodong (Robert) Li","email":"baoli@cisco.com","username":"baoli"},"change_message_id":"9ecf424ccceca1e38f6a99e19d4aa66f01697cd8","unresolved":false,"context_lines":[{"line_number":128,"context_line":""},{"line_number":129,"context_line":"profile_id \u003d sa.Column(sa.String(64), nullable\u003dFalse, primary_key\u003dTrue)"},{"line_number":130,"context_line":"vlan_id \u003d sa.Colum(sa.Integer(), nullable\u003dFalse)"},{"line_number":131,"context_line":"port_id \u003d sa.Column(sa.String(64), nullable\u003dTrue)"},{"line_number":132,"context_line":""},{"line_number":133,"context_line":"REST API impact"},{"line_number":134,"context_line":"---------------"}],"source_content_type":"text/x-rst","patch_set":6,"id":"1ae5cdf2_1d1446e8","line":131,"updated":"2014-06-23 11:23:36.000000000","message":"Does this MD only need to maintain mappings between profile_id and vlan_id? Given that a profile id is created algorithmically (OS-PP-\u003cvlan-id\u003e), all that needs to know is if a vlan is being used or not.\n\ndoes the vif_details maintain port_id to profile_id mapping already?","commit_id":"3c1d41fe71d6d09b912a3b45dacecbe79d3a43fb"},{"author":{"_account_id":6697,"name":"Sandhya Dasu","email":"sandhya.openinfra@gmail.com","username":"sadasu"},"change_message_id":"d2aa199c1a095f6972ef978c00d78e0ed7c4557f","unresolved":false,"context_lines":[{"line_number":128,"context_line":""},{"line_number":129,"context_line":"profile_id \u003d sa.Column(sa.String(64), nullable\u003dFalse, primary_key\u003dTrue)"},{"line_number":130,"context_line":"vlan_id \u003d sa.Colum(sa.Integer(), nullable\u003dFalse)"},{"line_number":131,"context_line":"port_id \u003d sa.Column(sa.String(64), nullable\u003dTrue)"},{"line_number":132,"context_line":""},{"line_number":133,"context_line":"REST API impact"},{"line_number":134,"context_line":"---------------"}],"source_content_type":"text/x-rst","patch_set":6,"id":"baada198_df5d1317","line":131,"in_reply_to":"1ae5cdf2_1d1446e8","updated":"2014-07-10 15:47:00.000000000","message":"Updated the spec to reflect the fact that port_id to profile_id mapping is available in the ml2_port_bindings table.","commit_id":"3c1d41fe71d6d09b912a3b45dacecbe79d3a43fb"},{"author":{"_account_id":6598,"name":"Berezovsky Irena","email":"irenab.dev@gmail.com","username":"irenab"},"change_message_id":"ae4f5871de6b58d44244a02ea1eac598563bd5c4","unresolved":false,"context_lines":[{"line_number":129,"context_line":"profile_id \u003d sa.Column(sa.String(64), nullable\u003dFalse, primary_key\u003dTrue)"},{"line_number":130,"context_line":"vlan_id \u003d sa.Colum(sa.Integer(), nullable\u003dFalse)"},{"line_number":131,"context_line":"port_id \u003d sa.Column(sa.String(64), nullable\u003dTrue)"},{"line_number":132,"context_line":""},{"line_number":133,"context_line":"REST API impact"},{"line_number":134,"context_line":"---------------"},{"line_number":135,"context_line":"None."}],"source_content_type":"text/x-rst","patch_set":6,"id":"1ae5cdf2_f29760e9","line":132,"updated":"2014-06-18 05:31:17.000000000","message":"Is there is some sort of synchronization mechanism between Neutron and UCS Manager to keep this table updated?","commit_id":"3c1d41fe71d6d09b912a3b45dacecbe79d3a43fb"},{"author":{"_account_id":6558,"name":"Sukhdev Kapur","email":"sukhdevkapur@gmail.com","username":"sukhdev-8"},"change_message_id":"991ba91bf0a3b6da0698c2876f0edc3f936e4d71","unresolved":false,"context_lines":[{"line_number":129,"context_line":"profile_id \u003d sa.Column(sa.String(64), nullable\u003dFalse, primary_key\u003dTrue)"},{"line_number":130,"context_line":"vlan_id \u003d sa.Colum(sa.Integer(), nullable\u003dFalse)"},{"line_number":131,"context_line":"port_id \u003d sa.Column(sa.String(64), nullable\u003dTrue)"},{"line_number":132,"context_line":""},{"line_number":133,"context_line":"REST API impact"},{"line_number":134,"context_line":"---------------"},{"line_number":135,"context_line":"None."}],"source_content_type":"text/x-rst","patch_set":6,"id":"1ae5cdf2_bba9a727","line":132,"in_reply_to":"1ae5cdf2_6aed02f0","updated":"2014-06-23 05:09:09.000000000","message":"Isn\u0027t port profile associated with port? You seem to imply it is associated with VLAN. Did I get you right?","commit_id":"3c1d41fe71d6d09b912a3b45dacecbe79d3a43fb"},{"author":{"_account_id":6697,"name":"Sandhya Dasu","email":"sandhya.openinfra@gmail.com","username":"sadasu"},"change_message_id":"dc6f57a2b940cd0e4e064a4923110d247e23fea1","unresolved":false,"context_lines":[{"line_number":129,"context_line":"profile_id \u003d sa.Column(sa.String(64), nullable\u003dFalse, primary_key\u003dTrue)"},{"line_number":130,"context_line":"vlan_id \u003d sa.Colum(sa.Integer(), nullable\u003dFalse)"},{"line_number":131,"context_line":"port_id \u003d sa.Column(sa.String(64), nullable\u003dTrue)"},{"line_number":132,"context_line":""},{"line_number":133,"context_line":"REST API impact"},{"line_number":134,"context_line":"---------------"},{"line_number":135,"context_line":"None."}],"source_content_type":"text/x-rst","patch_set":6,"id":"1ae5cdf2_4cc23d87","line":132,"in_reply_to":"1ae5cdf2_bba9a727","updated":"2014-06-25 15:33:19.000000000","message":"The vlan_id associated with a port profile would be applied on the interface that is created on the upstream switch. This interface on the upstream switch is connected to the the VF assigned to the VM and has to be able to send and receive traffic on this vlan_id.","commit_id":"3c1d41fe71d6d09b912a3b45dacecbe79d3a43fb"},{"author":{"_account_id":6697,"name":"Sandhya Dasu","email":"sandhya.openinfra@gmail.com","username":"sadasu"},"change_message_id":"6c191973b0a326f687c272a1aa308457124de115","unresolved":false,"context_lines":[{"line_number":129,"context_line":"profile_id \u003d sa.Column(sa.String(64), nullable\u003dFalse, primary_key\u003dTrue)"},{"line_number":130,"context_line":"vlan_id \u003d sa.Colum(sa.Integer(), nullable\u003dFalse)"},{"line_number":131,"context_line":"port_id \u003d sa.Column(sa.String(64), nullable\u003dTrue)"},{"line_number":132,"context_line":""},{"line_number":133,"context_line":"REST API impact"},{"line_number":134,"context_line":"---------------"},{"line_number":135,"context_line":"None."}],"source_content_type":"text/x-rst","patch_set":6,"id":"1ae5cdf2_6aed02f0","line":132,"in_reply_to":"1ae5cdf2_f29760e9","updated":"2014-06-18 15:28:32.000000000","message":"UCS Manager does not care which Neutron port-id is associated with which port profile. It only cares about:\n\n1. the Vlan-id which is associated with a port profile at creation time\n2. VM that is using this port profile, which is taken care of by the Cisco VM-FEX implementation.","commit_id":"3c1d41fe71d6d09b912a3b45dacecbe79d3a43fb"},{"author":{"_account_id":6558,"name":"Sukhdev Kapur","email":"sukhdevkapur@gmail.com","username":"sukhdev-8"},"change_message_id":"754db80802e3efd9db5957ddf9df108ce4383d8c","unresolved":false,"context_lines":[{"line_number":170,"context_line":"   the VLAN type driver."},{"line_number":171,"context_line":""},{"line_number":172,"context_line":"These should be provided in:"},{"line_number":173,"context_line":"/opt/stack/neutron/etc/neutron/plugins/ml2/ml2_conf_cisco.ini."},{"line_number":174,"context_line":""},{"line_number":175,"context_line":"Example:"},{"line_number":176,"context_line":"[ml2_cisco_ucsm]"}],"source_content_type":"text/x-rst","patch_set":6,"id":"1ae5cdf2_e97bfbf1","line":173,"updated":"2014-06-18 03:08:40.000000000","message":"This does not look right. Are you sure you are going to use the same file that is used by Nexus ML2 driver?  Can these two ML2 drivers run simultaneously? Or are you assuming that at a given time only one of these will run, and hence, both drivers will be configured form one config file.\n\nPlease clarify...","commit_id":"3c1d41fe71d6d09b912a3b45dacecbe79d3a43fb"},{"author":{"_account_id":6558,"name":"Sukhdev Kapur","email":"sukhdevkapur@gmail.com","username":"sukhdev-8"},"change_message_id":"991ba91bf0a3b6da0698c2876f0edc3f936e4d71","unresolved":false,"context_lines":[{"line_number":170,"context_line":"   the VLAN type driver."},{"line_number":171,"context_line":""},{"line_number":172,"context_line":"These should be provided in:"},{"line_number":173,"context_line":"/opt/stack/neutron/etc/neutron/plugins/ml2/ml2_conf_cisco.ini."},{"line_number":174,"context_line":""},{"line_number":175,"context_line":"Example:"},{"line_number":176,"context_line":"[ml2_cisco_ucsm]"}],"source_content_type":"text/x-rst","patch_set":6,"id":"1ae5cdf2_fbf5ef51","line":173,"in_reply_to":"1ae5cdf2_4a3cc62f","updated":"2014-06-23 05:09:09.000000000","message":"Got it. Thanks for clarifying. I wanted to make sure that you are not overlooking something.","commit_id":"3c1d41fe71d6d09b912a3b45dacecbe79d3a43fb"},{"author":{"_account_id":6697,"name":"Sandhya Dasu","email":"sandhya.openinfra@gmail.com","username":"sadasu"},"change_message_id":"6c191973b0a326f687c272a1aa308457124de115","unresolved":false,"context_lines":[{"line_number":170,"context_line":"   the VLAN type driver."},{"line_number":171,"context_line":""},{"line_number":172,"context_line":"These should be provided in:"},{"line_number":173,"context_line":"/opt/stack/neutron/etc/neutron/plugins/ml2/ml2_conf_cisco.ini."},{"line_number":174,"context_line":""},{"line_number":175,"context_line":"Example:"},{"line_number":176,"context_line":"[ml2_cisco_ucsm]"}],"source_content_type":"text/x-rst","patch_set":6,"id":"1ae5cdf2_4a3cc62f","line":173,"in_reply_to":"1ae5cdf2_e97bfbf1","updated":"2014-06-18 15:28:32.000000000","message":"Both drivers can run at the same time. Yes, multiple ML2 drivers can use the same .ini file. Their config is distinguished by having their own config section, specified inside [ ]. The name of this config section is provided to the mech driver in the config.py file.","commit_id":"3c1d41fe71d6d09b912a3b45dacecbe79d3a43fb"},{"author":{"_account_id":6558,"name":"Sukhdev Kapur","email":"sukhdevkapur@gmail.com","username":"sukhdev-8"},"change_message_id":"754db80802e3efd9db5957ddf9df108ce4383d8c","unresolved":false,"context_lines":[{"line_number":173,"context_line":"/opt/stack/neutron/etc/neutron/plugins/ml2/ml2_conf_cisco.ini."},{"line_number":174,"context_line":""},{"line_number":175,"context_line":"Example:"},{"line_number":176,"context_line":"[ml2_cisco_ucsm]"},{"line_number":177,"context_line":""},{"line_number":178,"context_line":"# Hostname for UCS Manager"},{"line_number":179,"context_line":"# ucsm_ip\u003d1.1.1.1"}],"source_content_type":"text/x-rst","patch_set":6,"id":"1ae5cdf2_69d52bb6","line":176,"updated":"2014-06-18 03:08:40.000000000","message":"The file you specify above uses [ml2_cisco]. But, here you are using different name. I believe you mean to have a separate file. If so, please fix this.","commit_id":"3c1d41fe71d6d09b912a3b45dacecbe79d3a43fb"},{"author":{"_account_id":6558,"name":"Sukhdev Kapur","email":"sukhdevkapur@gmail.com","username":"sukhdev-8"},"change_message_id":"991ba91bf0a3b6da0698c2876f0edc3f936e4d71","unresolved":false,"context_lines":[{"line_number":173,"context_line":"/opt/stack/neutron/etc/neutron/plugins/ml2/ml2_conf_cisco.ini."},{"line_number":174,"context_line":""},{"line_number":175,"context_line":"Example:"},{"line_number":176,"context_line":"[ml2_cisco_ucsm]"},{"line_number":177,"context_line":""},{"line_number":178,"context_line":"# Hostname for UCS Manager"},{"line_number":179,"context_line":"# ucsm_ip\u003d1.1.1.1"}],"source_content_type":"text/x-rst","patch_set":6,"id":"1ae5cdf2_3b9757ed","line":176,"in_reply_to":"1ae5cdf2_4ad846ef","updated":"2014-06-23 05:09:09.000000000","message":"Got it..","commit_id":"3c1d41fe71d6d09b912a3b45dacecbe79d3a43fb"},{"author":{"_account_id":6697,"name":"Sandhya Dasu","email":"sandhya.openinfra@gmail.com","username":"sadasu"},"change_message_id":"6c191973b0a326f687c272a1aa308457124de115","unresolved":false,"context_lines":[{"line_number":173,"context_line":"/opt/stack/neutron/etc/neutron/plugins/ml2/ml2_conf_cisco.ini."},{"line_number":174,"context_line":""},{"line_number":175,"context_line":"Example:"},{"line_number":176,"context_line":"[ml2_cisco_ucsm]"},{"line_number":177,"context_line":""},{"line_number":178,"context_line":"# Hostname for UCS Manager"},{"line_number":179,"context_line":"# ucsm_ip\u003d1.1.1.1"}],"source_content_type":"text/x-rst","patch_set":6,"id":"1ae5cdf2_4ad846ef","line":176,"in_reply_to":"1ae5cdf2_69d52bb6","updated":"2014-06-18 15:28:32.000000000","message":"[ml2_cisco] is the name of a config section as I mentioned as a response to your previous comment. This config section is being used by nexus as you rightly pointed out. This mech driver will have a new config section [ml2_cisco_ucsm]. \n\nBTW, the apic driver also shares the same file .ini file with a diff config section, I think. :-)","commit_id":"3c1d41fe71d6d09b912a3b45dacecbe79d3a43fb"},{"author":{"_account_id":490,"name":"Sumit Naiksatam","email":"sumitnaiksatam@gmail.com","username":"snaiksat"},"change_message_id":"359ce7a5cfc9334546c71d38a1e6d1a46cfbc295","unresolved":false,"context_lines":[{"line_number":61,"context_line":"be taken up in a different BP in the next iteration. (Since the VFs appear as"},{"line_number":62,"context_line":"interfaces on the upstream switch, ACLs can be applied on the VFs at the"},{"line_number":63,"context_line":"upstream switch.)"},{"line_number":64,"context_line":""},{"line_number":65,"context_line":"9. Multi-segment networks are also currently not supported by this BP. It will"},{"line_number":66,"context_line":"be added as part of a different BP in the next iteration."},{"line_number":67,"context_line":""}],"source_content_type":"text/x-rst","patch_set":8,"id":"baada198_f3ed6ef1","line":64,"updated":"2014-07-12 02:43:05.000000000","message":"The more that I think about it, it seems a little bit odd that in the configuration wherein only this UCS manager mechanism driver is configured, the Security Groups extension will be loaded but will not be honored. It will essentially be a no-op, however there would not be any feedback to the user that that the security group is in effect. Ideally if not implemented error is thrown in this case it will better. Is this feasible at all?","commit_id":"2f1d90090e3d2f0cf4e1b71d39187e6f05eb8f3c"},{"author":{"_account_id":6697,"name":"Sandhya Dasu","email":"sandhya.openinfra@gmail.com","username":"sadasu"},"change_message_id":"244a91935994f91444c8c469eaa077393590e691","unresolved":false,"context_lines":[{"line_number":61,"context_line":"be taken up in a different BP in the next iteration. (Since the VFs appear as"},{"line_number":62,"context_line":"interfaces on the upstream switch, ACLs can be applied on the VFs at the"},{"line_number":63,"context_line":"upstream switch.)"},{"line_number":64,"context_line":""},{"line_number":65,"context_line":"9. Multi-segment networks are also currently not supported by this BP. It will"},{"line_number":66,"context_line":"be added as part of a different BP in the next iteration."},{"line_number":67,"context_line":""}],"source_content_type":"text/x-rst","patch_set":8,"id":"baada198_9ce1e9fe","line":64,"in_reply_to":"baada198_f3ed6ef1","updated":"2014-07-17 14:46:23.000000000","message":"By feasible, are you asking if the error message is feasible? If so, yes and in addition a log msg can also be added.\n\nFew follow-up comments:\n\n1. At what point do you want this error msg to be raised?  When a sr-iov port is created in neutron, we can raise an error msg saying that security groups are not supported on a port of this type.\n\n2. When a nova VM is booted with an SR-IOV port, an error msg can be raised saying that this VM would not have security groups enabled.\n\n3. Documentation for this feature will explain why security groups cannot be applied at Neutron and they will have to configure ACLs at the upstream switch.\n\nI don\u0027t see why this BP should be stalled on this issue.","commit_id":"2f1d90090e3d2f0cf4e1b71d39187e6f05eb8f3c"}]}