)]}'
{"specs/approved/physical-network-awareness.rst":[{"author":{"_account_id":14826,"name":"Mark Goddard","email":"markgoddard86@gmail.com","username":"mgoddard"},"change_message_id":"d04b27fe69953c3236655db578f0ae5f02db1a08","unresolved":false,"context_lines":[{"line_number":161,"context_line":"The physical network of a portgroup will be determined through the physical"},{"line_number":162,"context_line":"network of its constituent ports.  All ports in the portgroup must have the"},{"line_number":163,"context_line":"same physical network, and this will be enforced in the ironic API when"},{"line_number":164,"context_line":"creating and updating ports, and when creating portgroups."},{"line_number":165,"context_line":""},{"line_number":166,"context_line":"This has the unfortunate consequence of making it rather unwieldy to update the"},{"line_number":167,"context_line":"physical network of the ports in a portgroup, since the ports must be removed"}],"source_content_type":"text/x-rst","patch_set":1,"id":"1f013ff3_651c5e6a","line":164,"updated":"2017-05-15 14:41:43.000000000","message":"On reflection, there\u0027s no need to do anything when creating portgroups as there won\u0027t be any member ports at that time.","commit_id":"2ebcfdde860d0a087a870deccf566162683a3cf7"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"9f5310cc81b034cfb4ae06e260b8945d574f9518","unresolved":false,"context_lines":[{"line_number":168,"context_line":"from the portgroup while their physical network is updated.  This may be"},{"line_number":169,"context_line":"improved upon in future through the use of a virtual physical network field in"},{"line_number":170,"context_line":"the portgroups API that allows simultaneous update of the physical network"},{"line_number":171,"context_line":"field of all the ports in the group."},{"line_number":172,"context_line":""},{"line_number":173,"context_line":"Mapping Logical Ports to Physical Ports"},{"line_number":174,"context_line":"---------------------------------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"ff0f0b1f_83a0a4a7","line":171,"updated":"2017-05-17 12:41:02.000000000","message":"+1, this makes sense to me","commit_id":"043193e27fbff84c323033753d460f967e4396f2"},{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"91d35e056e23acde9d1e1bc73194f1e33c279324","unresolved":false,"context_lines":[{"line_number":180,"context_line":"port\u0027s network or as ``provider:physical_network`` on the port\u0027s network."},{"line_number":181,"context_line":""},{"line_number":182,"context_line":"The virtual interface attachment mapping algorithm will be modified to the"},{"line_number":183,"context_line":"use the following set of criteria listed in order of descending priority:"},{"line_number":184,"context_line":""},{"line_number":185,"context_line":"1. reject ports and portgroups with a non-null physical network that is"},{"line_number":186,"context_line":"   different than all of the network\u0027s physical networks"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1f013ff3_0b46a050","line":183,"updated":"2017-05-16 19:08:30.000000000","message":"nit s/to the use the/to use the/","commit_id":"043193e27fbff84c323033753d460f967e4396f2"},{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"91d35e056e23acde9d1e1bc73194f1e33c279324","unresolved":false,"context_lines":[{"line_number":251,"context_line":"of a portgroup, the API will enforce that all ports in the portgroup have the"},{"line_number":252,"context_line":"same value in their physical network field."},{"line_number":253,"context_line":""},{"line_number":254,"context_line":"Updates to the the physical network field of ports will be restricted in the"},{"line_number":255,"context_line":"same way as for other connectivity related fields (link local connection, etc.)"},{"line_number":256,"context_line":"- they will be restricted to nodes in the ``enroll``, ``inspecting`` and"},{"line_number":257,"context_line":"``manageable`` states."}],"source_content_type":"text/x-rst","patch_set":2,"id":"1f013ff3_cbec382b","line":254,"updated":"2017-05-16 19:08:30.000000000","message":"nit s/the the/the/","commit_id":"043193e27fbff84c323033753d460f967e4396f2"},{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"91d35e056e23acde9d1e1bc73194f1e33c279324","unresolved":false,"context_lines":[{"line_number":318,"context_line":"---------------------"},{"line_number":319,"context_line":""},{"line_number":320,"context_line":"In order to make use of this feature, deployers must tag ironic ports and"},{"line_number":321,"context_line":"portgroups with the physical network to which they are attached.  This implies"},{"line_number":322,"context_line":"that they must have a mechanism to correctly determine this information."},{"line_number":323,"context_line":""},{"line_number":324,"context_line":"Developer impact"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1f013ff3_ebd2545c","line":321,"updated":"2017-05-16 19:08:30.000000000","message":"s/and portgroups//","commit_id":"043193e27fbff84c323033753d460f967e4396f2"}]}