)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"8d2e0af72cecbbef0d1af83a0bc446418acc0894","unresolved":false,"context_lines":[{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Add cross-pod L2 Networking spec file"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"In the Tricircle, the networking is established before the physical"},{"line_number":10,"context_line":"server is plugged into. The simplest way to stretch one L2 network"},{"line_number":11,"context_line":"across multiple OpenStack instances is to use a same VLAN network,"},{"line_number":12,"context_line":"but there is a lot of limitation: the number of VLAN segment is"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":12,"id":"dab17558_73c78f12","line":9,"range":{"start_line":9,"start_character":22,"end_line":9,"end_character":32},"updated":"2016-05-14 04:03:41.000000000","message":"cross pod(OpenStack) L2 networking automation","commit_id":"d072a51488c3755bc43a893a823f39f6c01780a4"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"9c1d102c4ab05a54a93b7df0f2807b45c22e7c9f","unresolved":false,"context_lines":[{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Add cross-pod L2 Networking spec file"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"In the Tricircle, the networking is established before the physical"},{"line_number":10,"context_line":"server is plugged into. The simplest way to stretch one L2 network"},{"line_number":11,"context_line":"across multiple OpenStack instances is to use a same VLAN network,"},{"line_number":12,"context_line":"but there is a lot of limitation: the number of VLAN segment is"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":12,"id":"dab17558_5931c90a","line":9,"range":{"start_line":9,"start_character":22,"end_line":9,"end_character":32},"in_reply_to":"dab17558_73c78f12","updated":"2016-05-14 09:45:52.000000000","message":"Let\u0027s discuss how we define:\n\n \"cross pod (OpenStack instance) L2 networking automation\n\nWe *must* have specific definition about any kind of terms which we use.","commit_id":"d072a51488c3755bc43a893a823f39f6c01780a4"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"8d2e0af72cecbbef0d1af83a0bc446418acc0894","unresolved":false,"context_lines":[{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Add cross-pod L2 Networking spec file"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"In the Tricircle, the networking is established before the physical"},{"line_number":10,"context_line":"server is plugged into. The simplest way to stretch one L2 network"},{"line_number":11,"context_line":"across multiple OpenStack instances is to use a same VLAN network,"},{"line_number":12,"context_line":"but there is a lot of limitation: the number of VLAN segment is"},{"line_number":13,"context_line":"limited, the VLAN network itself is not good to spread across multiple"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":12,"id":"dab17558_d34f5bbc","line":10,"range":{"start_line":9,"start_character":48,"end_line":10,"end_character":6},"updated":"2016-05-14 04:03:41.000000000","message":"after the virtual machine is plugged into","commit_id":"d072a51488c3755bc43a893a823f39f6c01780a4"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"9c1d102c4ab05a54a93b7df0f2807b45c22e7c9f","unresolved":false,"context_lines":[{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Add cross-pod L2 Networking spec file"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"In the Tricircle, the networking is established before the physical"},{"line_number":10,"context_line":"server is plugged into. The simplest way to stretch one L2 network"},{"line_number":11,"context_line":"across multiple OpenStack instances is to use a same VLAN network,"},{"line_number":12,"context_line":"but there is a lot of limitation: the number of VLAN segment is"},{"line_number":13,"context_line":"limited, the VLAN network itself is not good to spread across multiple"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":12,"id":"dab17558_1982a194","line":10,"range":{"start_line":9,"start_character":48,"end_line":10,"end_character":6},"in_reply_to":"dab17558_d34f5bbc","updated":"2016-05-14 09:45:52.000000000","message":"Yeah, in theory that\u0027s right but I think this would be more proper expression:\n\n after the instance is launched (or spawned)\n\nWhat do you think?","commit_id":"d072a51488c3755bc43a893a823f39f6c01780a4"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"8d2e0af72cecbbef0d1af83a0bc446418acc0894","unresolved":false,"context_lines":[{"line_number":11,"context_line":"across multiple OpenStack instances is to use a same VLAN network,"},{"line_number":12,"context_line":"but there is a lot of limitation: the number of VLAN segment is"},{"line_number":13,"context_line":"limited, the VLAN network itself is not good to spread across multiple"},{"line_number":14,"context_line":"sites, although you can use some gateways to do so. So flexible tenant"},{"line_number":15,"context_line":"level L2 networking across multiple OpenStack instances in one site or"},{"line_number":16,"context_line":"in multiple sites is needed."},{"line_number":17,"context_line":""}],"source_content_type":"text/x-gerrit-commit-message","patch_set":12,"id":"dab17558_33e6a7b4","line":14,"range":{"start_line":14,"start_character":52,"end_line":14,"end_character":54},"updated":"2016-05-14 04:03:41.000000000","message":"But there are so many tenants in the cloud, and new tenants could be added into the cloud dynamically, fixed physical network configuration for dynamic tenant networking is hard to manage, so flexible...","commit_id":"d072a51488c3755bc43a893a823f39f6c01780a4"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"8d2e0af72cecbbef0d1af83a0bc446418acc0894","unresolved":false,"context_lines":[{"line_number":12,"context_line":"but there is a lot of limitation: the number of VLAN segment is"},{"line_number":13,"context_line":"limited, the VLAN network itself is not good to spread across multiple"},{"line_number":14,"context_line":"sites, although you can use some gateways to do so. So flexible tenant"},{"line_number":15,"context_line":"level L2 networking across multiple OpenStack instances in one site or"},{"line_number":16,"context_line":"in multiple sites is needed."},{"line_number":17,"context_line":""},{"line_number":18,"context_line":"This spec deal with how the networking can supports more than one"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":12,"id":"dab17558_b3d1f7cf","line":15,"range":{"start_line":15,"start_character":19,"end_line":15,"end_character":20},"updated":"2016-05-14 04:03:41.000000000","message":"L2 networking automation","commit_id":"d072a51488c3755bc43a893a823f39f6c01780a4"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"8d2e0af72cecbbef0d1af83a0bc446418acc0894","unresolved":false,"context_lines":[{"line_number":15,"context_line":"level L2 networking across multiple OpenStack instances in one site or"},{"line_number":16,"context_line":"in multiple sites is needed."},{"line_number":17,"context_line":""},{"line_number":18,"context_line":"This spec deal with how the networking can supports more than one"},{"line_number":19,"context_line":"bottom pods in AZ or multiple AZs in Tricircle."},{"line_number":20,"context_line":""},{"line_number":21,"context_line":"Change-Id: I616048c13d03f48aa16d9ff48572b0d5a49d6fb4"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":12,"id":"dab17558_13e1e39a","line":18,"range":{"start_line":18,"start_character":28,"end_line":18,"end_character":38},"updated":"2016-05-14 04:03:41.000000000","message":"networking automation","commit_id":"d072a51488c3755bc43a893a823f39f6c01780a4"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"5a9ca2494e08de0b197159dfbbb3bb0b63a3cbe9","unresolved":false,"context_lines":[{"line_number":21,"context_line":"This spec deal with how the networking automation can supports more than"},{"line_number":22,"context_line":"one bottom pods in AZ or multiple AZs in Tricircle."},{"line_number":23,"context_line":""},{"line_number":24,"context_line":"Change-Id: I616048c13d03f48aa16d9ff48572b0d5a49d6fb4"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":13,"id":"dab17558_27bdbcd7","line":24,"range":{"start_line":24,"start_character":0,"end_line":24,"end_character":6},"updated":"2016-05-16 02:57:55.000000000","message":"add link to the BP here:\nLaunchpad BP: https://blueprints.launchpad.net/tricircle/+spec/cross-site-connectivity","commit_id":"3d9f8469aaf229397d54eae34a3b70db095feeb3"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"4efe21caa774909cd7b53e151044be8a932a01ed","unresolved":false,"context_lines":[{"line_number":7,"context_line":"Add cross-pod L2 Networking spec file"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"In the Tricircle, the cross pod (OpenStack) L2 networking automation is"},{"line_number":10,"context_line":"established after the virtual machine is plugged into. The simplest way"},{"line_number":11,"context_line":"to stretch one L2 network across multiple OpenStack instances is to use"},{"line_number":12,"context_line":"a same VLAN network, but there is a lot of limitation: the number of VLAN"},{"line_number":13,"context_line":"segment is limited, the VLAN network itself is not good to spread across"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":22,"id":"9abb7d3a_d0665a28","line":10,"range":{"start_line":10,"start_character":38,"end_line":10,"end_character":53},"updated":"2016-05-30 05:15:52.000000000","message":"plugged into the bottom OpenStack instances","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"}],"specs/cross-pod-l2-networking.rst":[{"author":{"_account_id":20405,"name":"liuhaixia","email":"liuhaixia315@huawei.com","username":"liuhaixia"},"change_message_id":"1474553f664e370a1ce3cd96a66a085a13596db7","unresolved":false,"context_lines":[{"line_number":5,"context_line":"Problem description"},{"line_number":6,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":7,"context_line":""},{"line_number":8,"context_line":"Currently,the ``Tricircle`` just supports the cross-pod L3 networking and one"},{"line_number":9,"context_line":"network in top pod can only locate in one bottom pod,tenant network is bound"},{"line_number":10,"context_line":"to bottom pod.Otherwise we cannot correctly configure extra route since for"},{"line_number":11,"context_line":"one destination ``CIDR``,we have more than one possible nexthop addresses."}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_83782ac6","line":8,"range":{"start_line":8,"start_character":25,"end_line":8,"end_character":27},"updated":"2016-04-13 03:02:16.000000000","message":"\"","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"8167600fefc797003f84fb660476ed1945b3c4ca","unresolved":false,"context_lines":[{"line_number":5,"context_line":"Problem description"},{"line_number":6,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":7,"context_line":""},{"line_number":8,"context_line":"Currently,the ``Tricircle`` just supports the cross-pod L3 networking and one"},{"line_number":9,"context_line":"network in top pod can only locate in one bottom pod,tenant network is bound"},{"line_number":10,"context_line":"to bottom pod.Otherwise we cannot correctly configure extra route since for"},{"line_number":11,"context_line":"one destination ``CIDR``,we have more than one possible nexthop addresses."}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_2345d616","line":8,"range":{"start_line":8,"start_character":69,"end_line":8,"end_character":70},"updated":"2016-04-13 02:52:47.000000000","message":"add \", \"","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"df1a08f75f71fd3aa71568d8f9d5e9056bd3f59a","unresolved":false,"context_lines":[{"line_number":5,"context_line":"Problem description"},{"line_number":6,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":7,"context_line":""},{"line_number":8,"context_line":"Currently,the ``Tricircle`` just supports the cross-pod L3 networking and one"},{"line_number":9,"context_line":"network in top pod can only locate in one bottom pod,tenant network is bound"},{"line_number":10,"context_line":"to bottom pod.Otherwise we cannot correctly configure extra route since for"},{"line_number":11,"context_line":"one destination ``CIDR``,we have more than one possible nexthop addresses."}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_0038909f","line":8,"range":{"start_line":8,"start_character":9,"end_line":8,"end_character":11},"updated":"2016-04-13 02:22:15.000000000","message":"add space","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":5,"context_line":"Problem description"},{"line_number":6,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":7,"context_line":""},{"line_number":8,"context_line":"Currently,the ``Tricircle`` just supports the cross-pod L3 networking and one"},{"line_number":9,"context_line":"network in top pod can only locate in one bottom pod,tenant network is bound"},{"line_number":10,"context_line":"to bottom pod.Otherwise we cannot correctly configure extra route since for"},{"line_number":11,"context_line":"one destination ``CIDR``,we have more than one possible nexthop addresses."}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_d0513dda","line":8,"range":{"start_line":8,"start_character":9,"end_line":8,"end_character":11},"in_reply_to":"5a18252c_0038909f","updated":"2016-04-13 09:25:41.000000000","message":"Done","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":5,"context_line":"Problem description"},{"line_number":6,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":7,"context_line":""},{"line_number":8,"context_line":"Currently,the ``Tricircle`` just supports the cross-pod L3 networking and one"},{"line_number":9,"context_line":"network in top pod can only locate in one bottom pod,tenant network is bound"},{"line_number":10,"context_line":"to bottom pod.Otherwise we cannot correctly configure extra route since for"},{"line_number":11,"context_line":"one destination ``CIDR``,we have more than one possible nexthop addresses."}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_106295ad","line":8,"range":{"start_line":8,"start_character":69,"end_line":8,"end_character":70},"in_reply_to":"5a18252c_2345d616","updated":"2016-04-13 09:25:41.000000000","message":"Done","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":5,"context_line":"Problem description"},{"line_number":6,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":7,"context_line":""},{"line_number":8,"context_line":"Currently,the ``Tricircle`` just supports the cross-pod L3 networking and one"},{"line_number":9,"context_line":"network in top pod can only locate in one bottom pod,tenant network is bound"},{"line_number":10,"context_line":"to bottom pod.Otherwise we cannot correctly configure extra route since for"},{"line_number":11,"context_line":"one destination ``CIDR``,we have more than one possible nexthop addresses."}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_505c0ded","line":8,"range":{"start_line":8,"start_character":25,"end_line":8,"end_character":27},"in_reply_to":"5a18252c_83782ac6","updated":"2016-04-13 09:25:41.000000000","message":"Done","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"8167600fefc797003f84fb660476ed1945b3c4ca","unresolved":false,"context_lines":[{"line_number":6,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":7,"context_line":""},{"line_number":8,"context_line":"Currently,the ``Tricircle`` just supports the cross-pod L3 networking and one"},{"line_number":9,"context_line":"network in top pod can only locate in one bottom pod,tenant network is bound"},{"line_number":10,"context_line":"to bottom pod.Otherwise we cannot correctly configure extra route since for"},{"line_number":11,"context_line":"one destination ``CIDR``,we have more than one possible nexthop addresses."},{"line_number":12,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_a351e6da","line":9,"range":{"start_line":9,"start_character":8,"end_line":9,"end_character":19},"updated":"2016-04-13 02:52:47.000000000","message":"- \"in top pod\"","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21067,"name":"lige","email":"eros.lige@gmail.com","username":"lige"},"change_message_id":"82505468ec383401c60fb5499c09b1a66599c644","unresolved":false,"context_lines":[{"line_number":5,"context_line":"Problem description"},{"line_number":6,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":7,"context_line":""},{"line_number":8,"context_line":"Currently,the ``Tricircle`` just supports the cross-pod L3 networking and one"},{"line_number":9,"context_line":"network in top pod can only locate in one bottom pod,tenant network is bound"},{"line_number":10,"context_line":"to bottom pod.Otherwise we cannot correctly configure extra route since for"},{"line_number":11,"context_line":"one destination ``CIDR``,we have more than one possible nexthop addresses."},{"line_number":12,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_6b24855f","line":9,"range":{"start_line":8,"start_character":74,"end_line":9,"end_character":7},"updated":"2016-04-14 02:50:53.000000000","message":"- \"one network\"  + \"one overlay network \"","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"8167600fefc797003f84fb660476ed1945b3c4ca","unresolved":false,"context_lines":[{"line_number":6,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":7,"context_line":""},{"line_number":8,"context_line":"Currently,the ``Tricircle`` just supports the cross-pod L3 networking and one"},{"line_number":9,"context_line":"network in top pod can only locate in one bottom pod,tenant network is bound"},{"line_number":10,"context_line":"to bottom pod.Otherwise we cannot correctly configure extra route since for"},{"line_number":11,"context_line":"one destination ``CIDR``,we have more than one possible nexthop addresses."},{"line_number":12,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_83faeabb","line":9,"range":{"start_line":9,"start_character":42,"end_line":9,"end_character":52},"updated":"2016-04-13 02:52:47.000000000","message":"AZ, for currently the network will be bound to one AZ if az speficied in the AZ_Hint of the network, other cases are not supported yet","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"df1a08f75f71fd3aa71568d8f9d5e9056bd3f59a","unresolved":false,"context_lines":[{"line_number":6,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":7,"context_line":""},{"line_number":8,"context_line":"Currently,the ``Tricircle`` just supports the cross-pod L3 networking and one"},{"line_number":9,"context_line":"network in top pod can only locate in one bottom pod,tenant network is bound"},{"line_number":10,"context_line":"to bottom pod.Otherwise we cannot correctly configure extra route since for"},{"line_number":11,"context_line":"one destination ``CIDR``,we have more than one possible nexthop addresses."},{"line_number":12,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_80730080","line":9,"range":{"start_line":9,"start_character":52,"end_line":9,"end_character":54},"updated":"2016-04-13 02:22:15.000000000","message":"add space","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":6,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":7,"context_line":""},{"line_number":8,"context_line":"Currently,the ``Tricircle`` just supports the cross-pod L3 networking and one"},{"line_number":9,"context_line":"network in top pod can only locate in one bottom pod,tenant network is bound"},{"line_number":10,"context_line":"to bottom pod.Otherwise we cannot correctly configure extra route since for"},{"line_number":11,"context_line":"one destination ``CIDR``,we have more than one possible nexthop addresses."},{"line_number":12,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_b073e17f","line":9,"range":{"start_line":9,"start_character":52,"end_line":9,"end_character":54},"in_reply_to":"5a18252c_80730080","updated":"2016-04-13 09:25:41.000000000","message":"Done","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":6,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":7,"context_line":""},{"line_number":8,"context_line":"Currently,the ``Tricircle`` just supports the cross-pod L3 networking and one"},{"line_number":9,"context_line":"network in top pod can only locate in one bottom pod,tenant network is bound"},{"line_number":10,"context_line":"to bottom pod.Otherwise we cannot correctly configure extra route since for"},{"line_number":11,"context_line":"one destination ``CIDR``,we have more than one possible nexthop addresses."},{"line_number":12,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_906ea594","line":9,"range":{"start_line":9,"start_character":42,"end_line":9,"end_character":52},"in_reply_to":"5a18252c_83faeabb","updated":"2016-04-13 09:25:41.000000000","message":"Done","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":6,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":7,"context_line":""},{"line_number":8,"context_line":"Currently,the ``Tricircle`` just supports the cross-pod L3 networking and one"},{"line_number":9,"context_line":"network in top pod can only locate in one bottom pod,tenant network is bound"},{"line_number":10,"context_line":"to bottom pod.Otherwise we cannot correctly configure extra route since for"},{"line_number":11,"context_line":"one destination ``CIDR``,we have more than one possible nexthop addresses."},{"line_number":12,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_f06d5999","line":9,"range":{"start_line":9,"start_character":8,"end_line":9,"end_character":19},"in_reply_to":"5a18252c_a351e6da","updated":"2016-04-13 09:25:41.000000000","message":"Done","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"df1a08f75f71fd3aa71568d8f9d5e9056bd3f59a","unresolved":false,"context_lines":[{"line_number":7,"context_line":""},{"line_number":8,"context_line":"Currently,the ``Tricircle`` just supports the cross-pod L3 networking and one"},{"line_number":9,"context_line":"network in top pod can only locate in one bottom pod,tenant network is bound"},{"line_number":10,"context_line":"to bottom pod.Otherwise we cannot correctly configure extra route since for"},{"line_number":11,"context_line":"one destination ``CIDR``,we have more than one possible nexthop addresses."},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"The scenarios of cross-pod L2 networking can be divided into three types,"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_c06df899","line":10,"range":{"start_line":10,"start_character":13,"end_line":10,"end_character":15},"updated":"2016-04-13 02:22:15.000000000","message":"add space","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":7,"context_line":""},{"line_number":8,"context_line":"Currently,the ``Tricircle`` just supports the cross-pod L3 networking and one"},{"line_number":9,"context_line":"network in top pod can only locate in one bottom pod,tenant network is bound"},{"line_number":10,"context_line":"to bottom pod.Otherwise we cannot correctly configure extra route since for"},{"line_number":11,"context_line":"one destination ``CIDR``,we have more than one possible nexthop addresses."},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"The scenarios of cross-pod L2 networking can be divided into three types,"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_d0681d8a","line":10,"range":{"start_line":10,"start_character":13,"end_line":10,"end_character":15},"in_reply_to":"5a18252c_c06df899","updated":"2016-04-13 09:25:41.000000000","message":"Done","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"df1a08f75f71fd3aa71568d8f9d5e9056bd3f59a","unresolved":false,"context_lines":[{"line_number":8,"context_line":"Currently,the ``Tricircle`` just supports the cross-pod L3 networking and one"},{"line_number":9,"context_line":"network in top pod can only locate in one bottom pod,tenant network is bound"},{"line_number":10,"context_line":"to bottom pod.Otherwise we cannot correctly configure extra route since for"},{"line_number":11,"context_line":"one destination ``CIDR``,we have more than one possible nexthop addresses."},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"The scenarios of cross-pod L2 networking can be divided into three types,"},{"line_number":14,"context_line":"``shared VLAN``, ``shared VxLan`` and ``mixed VLAN/VxLan``.for shared VLAN type"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_e008f4db","line":11,"range":{"start_line":11,"start_character":24,"end_line":11,"end_character":26},"updated":"2016-04-13 02:22:15.000000000","message":"add space","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":8,"context_line":"Currently,the ``Tricircle`` just supports the cross-pod L3 networking and one"},{"line_number":9,"context_line":"network in top pod can only locate in one bottom pod,tenant network is bound"},{"line_number":10,"context_line":"to bottom pod.Otherwise we cannot correctly configure extra route since for"},{"line_number":11,"context_line":"one destination ``CIDR``,we have more than one possible nexthop addresses."},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"The scenarios of cross-pod L2 networking can be divided into three types,"},{"line_number":14,"context_line":"``shared VLAN``, ``shared VxLan`` and ``mixed VLAN/VxLan``.for shared VLAN type"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_1009f5dd","line":11,"range":{"start_line":11,"start_character":24,"end_line":11,"end_character":26},"in_reply_to":"5a18252c_e008f4db","updated":"2016-04-13 09:25:41.000000000","message":"Done","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"346604c3992b6ead6767b236251e52626e883fb6","unresolved":false,"context_lines":[{"line_number":11,"context_line":"one destination ``CIDR``,we have more than one possible nexthop addresses."},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"The scenarios of cross-pod L2 networking can be divided into three types,"},{"line_number":14,"context_line":"``shared VLAN``, ``shared VxLan`` and ``mixed VLAN/VxLan``.for shared VLAN type"},{"line_number":15,"context_line":",network in each bottom OpenStack is VLAN type and has the same VLAN ID.For"},{"line_number":16,"context_line":"shared VxLAN type,network in each bottom OpenStack is VxLAN type and has the"},{"line_number":17,"context_line":"same VxLan ID.For mixed VLAN/VxLAN type,network in each bottom OpenStack may "}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_248e8578","line":14,"updated":"2016-04-12 22:56:40.000000000","message":"- VxLan\n+ VxLAN\nfor consistency","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"df1a08f75f71fd3aa71568d8f9d5e9056bd3f59a","unresolved":false,"context_lines":[{"line_number":11,"context_line":"one destination ``CIDR``,we have more than one possible nexthop addresses."},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"The scenarios of cross-pod L2 networking can be divided into three types,"},{"line_number":14,"context_line":"``shared VLAN``, ``shared VxLan`` and ``mixed VLAN/VxLan``.for shared VLAN type"},{"line_number":15,"context_line":",network in each bottom OpenStack is VLAN type and has the same VLAN ID.For"},{"line_number":16,"context_line":"shared VxLAN type,network in each bottom OpenStack is VxLAN type and has the"},{"line_number":17,"context_line":"same VxLan ID.For mixed VLAN/VxLAN type,network in each bottom OpenStack may "}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_00d4101e","line":14,"range":{"start_line":14,"start_character":58,"end_line":14,"end_character":60},"updated":"2016-04-13 02:22:15.000000000","message":"add space; \"f\" uppercase. Please check the following space-missing typo yourself :)","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"8ef5c97d6d8c38b40c159923db7ad854b9011120","unresolved":false,"context_lines":[{"line_number":11,"context_line":"one destination ``CIDR``,we have more than one possible nexthop addresses."},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"The scenarios of cross-pod L2 networking can be divided into three types,"},{"line_number":14,"context_line":"``shared VLAN``, ``shared VxLan`` and ``mixed VLAN/VxLan``.for shared VLAN type"},{"line_number":15,"context_line":",network in each bottom OpenStack is VLAN type and has the same VLAN ID.For"},{"line_number":16,"context_line":"shared VxLAN type,network in each bottom OpenStack is VxLAN type and has the"},{"line_number":17,"context_line":"same VxLan ID.For mixed VLAN/VxLAN type,network in each bottom OpenStack may "}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_5fdd6713","line":14,"range":{"start_line":14,"start_character":19,"end_line":14,"end_character":56},"updated":"2016-04-13 07:28:18.000000000","message":"shared VxLAN and mixed VLAN/VxLAN","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":11,"context_line":"one destination ``CIDR``,we have more than one possible nexthop addresses."},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"The scenarios of cross-pod L2 networking can be divided into three types,"},{"line_number":14,"context_line":"``shared VLAN``, ``shared VxLan`` and ``mixed VLAN/VxLan``.for shared VLAN type"},{"line_number":15,"context_line":",network in each bottom OpenStack is VLAN type and has the same VLAN ID.For"},{"line_number":16,"context_line":"shared VxLAN type,network in each bottom OpenStack is VxLAN type and has the"},{"line_number":17,"context_line":"same VxLan ID.For mixed VLAN/VxLAN type,network in each bottom OpenStack may "}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_b0fac1bb","line":14,"range":{"start_line":14,"start_character":58,"end_line":14,"end_character":60},"in_reply_to":"5a18252c_00d4101e","updated":"2016-04-13 09:25:41.000000000","message":"Done","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21033,"name":"XiongQiu Long","email":"longxiongqiu123@163.com","username":"XiongQiu"},"change_message_id":"743c79bb093d9ad0a705bc561add7de158bc8578","unresolved":false,"context_lines":[{"line_number":11,"context_line":"one destination ``CIDR``,we have more than one possible nexthop addresses."},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"The scenarios of cross-pod L2 networking can be divided into three types,"},{"line_number":14,"context_line":"``shared VLAN``, ``shared VxLan`` and ``mixed VLAN/VxLan``.for shared VLAN type"},{"line_number":15,"context_line":",network in each bottom OpenStack is VLAN type and has the same VLAN ID.For"},{"line_number":16,"context_line":"shared VxLAN type,network in each bottom OpenStack is VxLAN type and has the"},{"line_number":17,"context_line":"same VxLan ID.For mixed VLAN/VxLAN type,network in each bottom OpenStack may "}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_e959f85b","line":14,"range":{"start_line":14,"start_character":58,"end_line":14,"end_character":60},"in_reply_to":"5a18252c_00d4101e","updated":"2016-04-13 07:48:19.000000000","message":"i will check  all space-missing typo and other format error and fix it in new patch set.","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":11,"context_line":"one destination ``CIDR``,we have more than one possible nexthop addresses."},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"The scenarios of cross-pod L2 networking can be divided into three types,"},{"line_number":14,"context_line":"``shared VLAN``, ``shared VxLan`` and ``mixed VLAN/VxLan``.for shared VLAN type"},{"line_number":15,"context_line":",network in each bottom OpenStack is VLAN type and has the same VLAN ID.For"},{"line_number":16,"context_line":"shared VxLAN type,network in each bottom OpenStack is VxLAN type and has the"},{"line_number":17,"context_line":"same VxLan ID.For mixed VLAN/VxLAN type,network in each bottom OpenStack may "}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_50136d0d","line":14,"in_reply_to":"5a18252c_248e8578","updated":"2016-04-13 09:25:41.000000000","message":"Done","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":11,"context_line":"one destination ``CIDR``,we have more than one possible nexthop addresses."},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"The scenarios of cross-pod L2 networking can be divided into three types,"},{"line_number":14,"context_line":"``shared VLAN``, ``shared VxLan`` and ``mixed VLAN/VxLan``.for shared VLAN type"},{"line_number":15,"context_line":",network in each bottom OpenStack is VLAN type and has the same VLAN ID.For"},{"line_number":16,"context_line":"shared VxLAN type,network in each bottom OpenStack is VxLAN type and has the"},{"line_number":17,"context_line":"same VxLan ID.For mixed VLAN/VxLAN type,network in each bottom OpenStack may "}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_f00439c1","line":14,"range":{"start_line":14,"start_character":19,"end_line":14,"end_character":56},"in_reply_to":"5a18252c_5fdd6713","updated":"2016-04-13 09:25:41.000000000","message":"Done","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"346604c3992b6ead6767b236251e52626e883fb6","unresolved":false,"context_lines":[{"line_number":14,"context_line":"``shared VLAN``, ``shared VxLan`` and ``mixed VLAN/VxLan``.for shared VLAN type"},{"line_number":15,"context_line":",network in each bottom OpenStack is VLAN type and has the same VLAN ID.For"},{"line_number":16,"context_line":"shared VxLAN type,network in each bottom OpenStack is VxLAN type and has the"},{"line_number":17,"context_line":"same VxLan ID.For mixed VLAN/VxLAN type,network in each bottom OpenStack may "},{"line_number":18,"context_line":"have different types or have different segmentation ID."},{"line_number":19,"context_line":""},{"line_number":20,"context_line":"To achieve cross-pod L2 networking,L2GW will be used to connect L2 network in"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_e4dacd77","line":17,"updated":"2016-04-12 22:56:40.000000000","message":"- VxLan\n+ VxLAN","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"df1a08f75f71fd3aa71568d8f9d5e9056bd3f59a","unresolved":false,"context_lines":[{"line_number":14,"context_line":"``shared VLAN``, ``shared VxLan`` and ``mixed VLAN/VxLan``.for shared VLAN type"},{"line_number":15,"context_line":",network in each bottom OpenStack is VLAN type and has the same VLAN ID.For"},{"line_number":16,"context_line":"shared VxLAN type,network in each bottom OpenStack is VxLAN type and has the"},{"line_number":17,"context_line":"same VxLan ID.For mixed VLAN/VxLAN type,network in each bottom OpenStack may "},{"line_number":18,"context_line":"have different types or have different segmentation ID."},{"line_number":19,"context_line":""},{"line_number":20,"context_line":"To achieve cross-pod L2 networking,L2GW will be used to connect L2 network in"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_20eb0cb2","line":17,"range":{"start_line":17,"start_character":76,"end_line":17,"end_character":77},"updated":"2016-04-13 02:22:15.000000000","message":"remove trailing space","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":20405,"name":"liuhaixia","email":"liuhaixia315@huawei.com","username":"liuhaixia"},"change_message_id":"1474553f664e370a1ce3cd96a66a085a13596db7","unresolved":false,"context_lines":[{"line_number":14,"context_line":"``shared VLAN``, ``shared VxLan`` and ``mixed VLAN/VxLan``.for shared VLAN type"},{"line_number":15,"context_line":",network in each bottom OpenStack is VLAN type and has the same VLAN ID.For"},{"line_number":16,"context_line":"shared VxLAN type,network in each bottom OpenStack is VxLAN type and has the"},{"line_number":17,"context_line":"same VxLan ID.For mixed VLAN/VxLAN type,network in each bottom OpenStack may "},{"line_number":18,"context_line":"have different types or have different segmentation ID."},{"line_number":19,"context_line":""},{"line_number":20,"context_line":"To achieve cross-pod L2 networking,L2GW will be used to connect L2 network in"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_03325a10","line":17,"range":{"start_line":17,"start_character":5,"end_line":17,"end_character":14},"updated":"2016-04-13 03:02:16.000000000","message":"segment id","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":14,"context_line":"``shared VLAN``, ``shared VxLan`` and ``mixed VLAN/VxLan``.for shared VLAN type"},{"line_number":15,"context_line":",network in each bottom OpenStack is VLAN type and has the same VLAN ID.For"},{"line_number":16,"context_line":"shared VxLAN type,network in each bottom OpenStack is VxLAN type and has the"},{"line_number":17,"context_line":"same VxLan ID.For mixed VLAN/VxLAN type,network in each bottom OpenStack may "},{"line_number":18,"context_line":"have different types or have different segmentation ID."},{"line_number":19,"context_line":""},{"line_number":20,"context_line":"To achieve cross-pod L2 networking,L2GW will be used to connect L2 network in"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_70278964","line":17,"range":{"start_line":17,"start_character":5,"end_line":17,"end_character":14},"in_reply_to":"5a18252c_03325a10","updated":"2016-04-13 09:25:41.000000000","message":"Done","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":14,"context_line":"``shared VLAN``, ``shared VxLan`` and ``mixed VLAN/VxLan``.for shared VLAN type"},{"line_number":15,"context_line":",network in each bottom OpenStack is VLAN type and has the same VLAN ID.For"},{"line_number":16,"context_line":"shared VxLAN type,network in each bottom OpenStack is VxLAN type and has the"},{"line_number":17,"context_line":"same VxLan ID.For mixed VLAN/VxLAN type,network in each bottom OpenStack may "},{"line_number":18,"context_line":"have different types or have different segmentation ID."},{"line_number":19,"context_line":""},{"line_number":20,"context_line":"To achieve cross-pod L2 networking,L2GW will be used to connect L2 network in"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_1030d59d","line":17,"range":{"start_line":17,"start_character":76,"end_line":17,"end_character":77},"in_reply_to":"5a18252c_20eb0cb2","updated":"2016-04-13 09:25:41.000000000","message":"Done","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":14,"context_line":"``shared VLAN``, ``shared VxLan`` and ``mixed VLAN/VxLan``.for shared VLAN type"},{"line_number":15,"context_line":",network in each bottom OpenStack is VLAN type and has the same VLAN ID.For"},{"line_number":16,"context_line":"shared VxLAN type,network in each bottom OpenStack is VxLAN type and has the"},{"line_number":17,"context_line":"same VxLan ID.For mixed VLAN/VxLAN type,network in each bottom OpenStack may "},{"line_number":18,"context_line":"have different types or have different segmentation ID."},{"line_number":19,"context_line":""},{"line_number":20,"context_line":"To achieve cross-pod L2 networking,L2GW will be used to connect L2 network in"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_302d1147","line":17,"in_reply_to":"5a18252c_e4dacd77","updated":"2016-04-13 09:25:41.000000000","message":"Done","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"346604c3992b6ead6767b236251e52626e883fb6","unresolved":false,"context_lines":[{"line_number":15,"context_line":",network in each bottom OpenStack is VLAN type and has the same VLAN ID.For"},{"line_number":16,"context_line":"shared VxLAN type,network in each bottom OpenStack is VxLAN type and has the"},{"line_number":17,"context_line":"same VxLan ID.For mixed VLAN/VxLAN type,network in each bottom OpenStack may "},{"line_number":18,"context_line":"have different types or have different segmentation ID."},{"line_number":19,"context_line":""},{"line_number":20,"context_line":"To achieve cross-pod L2 networking,L2GW will be used to connect L2 network in"},{"line_number":21,"context_line":"differnt pods.No extra route is required to connect L2 network.ALL L3 traffic"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_e4c12d82","line":18,"updated":"2016-04-12 22:56:40.000000000","message":"- ID\n+ IDs","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":15,"context_line":",network in each bottom OpenStack is VLAN type and has the same VLAN ID.For"},{"line_number":16,"context_line":"shared VxLAN type,network in each bottom OpenStack is VxLAN type and has the"},{"line_number":17,"context_line":"same VxLan ID.For mixed VLAN/VxLAN type,network in each bottom OpenStack may "},{"line_number":18,"context_line":"have different types or have different segmentation ID."},{"line_number":19,"context_line":""},{"line_number":20,"context_line":"To achieve cross-pod L2 networking,L2GW will be used to connect L2 network in"},{"line_number":21,"context_line":"differnt pods.No extra route is required to connect L2 network.ALL L3 traffic"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_502a4d2d","line":18,"in_reply_to":"5a18252c_e4c12d82","updated":"2016-04-13 09:25:41.000000000","message":"Done","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"8167600fefc797003f84fb660476ed1945b3c4ca","unresolved":false,"context_lines":[{"line_number":17,"context_line":"same VxLan ID.For mixed VLAN/VxLAN type,network in each bottom OpenStack may "},{"line_number":18,"context_line":"have different types or have different segmentation ID."},{"line_number":19,"context_line":""},{"line_number":20,"context_line":"To achieve cross-pod L2 networking,L2GW will be used to connect L2 network in"},{"line_number":21,"context_line":"differnt pods.No extra route is required to connect L2 network.ALL L3 traffic"},{"line_number":22,"context_line":"will be forwarded to the local L2 network,then go to the server in another pod"},{"line_number":23,"context_line":"via the L2GW."}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_e3bd9ed8","line":20,"range":{"start_line":20,"start_character":35,"end_line":20,"end_character":39},"updated":"2016-04-13 02:52:47.000000000","message":"Shared VLAN needs no L2GW","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"df1a08f75f71fd3aa71568d8f9d5e9056bd3f59a","unresolved":false,"context_lines":[{"line_number":17,"context_line":"same VxLan ID.For mixed VLAN/VxLAN type,network in each bottom OpenStack may "},{"line_number":18,"context_line":"have different types or have different segmentation ID."},{"line_number":19,"context_line":""},{"line_number":20,"context_line":"To achieve cross-pod L2 networking,L2GW will be used to connect L2 network in"},{"line_number":21,"context_line":"differnt pods.No extra route is required to connect L2 network.ALL L3 traffic"},{"line_number":22,"context_line":"will be forwarded to the local L2 network,then go to the server in another pod"},{"line_number":23,"context_line":"via the L2GW."}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_c0f3389d","line":20,"range":{"start_line":20,"start_character":35,"end_line":20,"end_character":74},"updated":"2016-04-13 02:22:15.000000000","message":"not sure we need to use L2GW for all cases, waiting for Joe\u0027s comment","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"8ef5c97d6d8c38b40c159923db7ad854b9011120","unresolved":false,"context_lines":[{"line_number":17,"context_line":"same VxLan ID.For mixed VLAN/VxLAN type,network in each bottom OpenStack may "},{"line_number":18,"context_line":"have different types or have different segmentation ID."},{"line_number":19,"context_line":""},{"line_number":20,"context_line":"To achieve cross-pod L2 networking,L2GW will be used to connect L2 network in"},{"line_number":21,"context_line":"differnt pods.No extra route is required to connect L2 network.ALL L3 traffic"},{"line_number":22,"context_line":"will be forwarded to the local L2 network,then go to the server in another pod"},{"line_number":23,"context_line":"via the L2GW."}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_e64c8772","line":20,"range":{"start_line":20,"start_character":35,"end_line":20,"end_character":74},"in_reply_to":"5a18252c_c0f3389d","updated":"2016-04-13 07:28:18.000000000","message":"it is described in the \"Cross-pod L3 networking with DevStack\" of README. Whether we need to do the corresponding adjustment?","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"8167600fefc797003f84fb660476ed1945b3c4ca","unresolved":false,"context_lines":[{"line_number":18,"context_line":"have different types or have different segmentation ID."},{"line_number":19,"context_line":""},{"line_number":20,"context_line":"To achieve cross-pod L2 networking,L2GW will be used to connect L2 network in"},{"line_number":21,"context_line":"differnt pods.No extra route is required to connect L2 network.ALL L3 traffic"},{"line_number":22,"context_line":"will be forwarded to the local L2 network,then go to the server in another pod"},{"line_number":23,"context_line":"via the L2GW."},{"line_number":24,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_83d2eafe","line":21,"range":{"start_line":21,"start_character":14,"end_line":21,"end_character":63},"updated":"2016-04-13 02:52:47.000000000","message":"One assumption here:\n\nFor a network inside one AZ, it should be cross Pod L2 network if more then one pod in one AZ. For a Network specified with more more than one AZ in AZ_Hint, or without any AZ in AZ_HINT,then this network is cross AZ network, the difference is that if no any AZ specified in AZ_Hint, it means the network could span to any pod in any AZ, if several AZs in the AZ_Hint, then only spanning the Network to these specified AZs.","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":18,"context_line":"have different types or have different segmentation ID."},{"line_number":19,"context_line":""},{"line_number":20,"context_line":"To achieve cross-pod L2 networking,L2GW will be used to connect L2 network in"},{"line_number":21,"context_line":"differnt pods.No extra route is required to connect L2 network.ALL L3 traffic"},{"line_number":22,"context_line":"will be forwarded to the local L2 network,then go to the server in another pod"},{"line_number":23,"context_line":"via the L2GW."},{"line_number":24,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_bfb57232","line":21,"range":{"start_line":21,"start_character":14,"end_line":21,"end_character":63},"in_reply_to":"5a18252c_83d2eafe","updated":"2016-04-13 09:25:41.000000000","message":"should we waitting for the Joe\u0027s comment, then complete this paragraph and adding this assumption in \u0027Use Cases\u0027.","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"346604c3992b6ead6767b236251e52626e883fb6","unresolved":false,"context_lines":[{"line_number":27,"context_line":""},{"line_number":28,"context_line":"**Use case for shared VLAN:**"},{"line_number":29,"context_line":""},{"line_number":30,"context_line":"A user create network Net1,plugin check the configuration,if"},{"line_number":31,"context_line":"``tenant_network_type`` equals shared_vlan,it will invoke shared vlan dirver."},{"line_number":32,"context_line":"Shared VLAN driver will allocate ``segment``,and assgin ``network_type`` with"},{"line_number":33,"context_line":"vlan,and update network with ``segment`` and ``network_type`` to DB."}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_a45d75eb","line":30,"updated":"2016-04-12 22:56:40.000000000","message":"- create\n+ creates\n\n- check\n+ checks","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":27,"context_line":""},{"line_number":28,"context_line":"**Use case for shared VLAN:**"},{"line_number":29,"context_line":""},{"line_number":30,"context_line":"A user create network Net1,plugin check the configuration,if"},{"line_number":31,"context_line":"``tenant_network_type`` equals shared_vlan,it will invoke shared vlan dirver."},{"line_number":32,"context_line":"Shared VLAN driver will allocate ``segment``,and assgin ``network_type`` with"},{"line_number":33,"context_line":"vlan,and update network with ``segment`` and ``network_type`` to DB."}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_10d73524","line":30,"in_reply_to":"5a18252c_a45d75eb","updated":"2016-04-13 09:25:41.000000000","message":"Done","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"df1a08f75f71fd3aa71568d8f9d5e9056bd3f59a","unresolved":false,"context_lines":[{"line_number":28,"context_line":"**Use case for shared VLAN:**"},{"line_number":29,"context_line":""},{"line_number":30,"context_line":"A user create network Net1,plugin check the configuration,if"},{"line_number":31,"context_line":"``tenant_network_type`` equals shared_vlan,it will invoke shared vlan dirver."},{"line_number":32,"context_line":"Shared VLAN driver will allocate ``segment``,and assgin ``network_type`` with"},{"line_number":33,"context_line":"vlan,and update network with ``segment`` and ``network_type`` to DB."},{"line_number":34,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_40360853","line":31,"range":{"start_line":31,"start_character":65,"end_line":31,"end_character":69},"updated":"2016-04-13 02:22:15.000000000","message":"\"vlan\" uppercase to keep consistent","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"346604c3992b6ead6767b236251e52626e883fb6","unresolved":false,"context_lines":[{"line_number":28,"context_line":"**Use case for shared VLAN:**"},{"line_number":29,"context_line":""},{"line_number":30,"context_line":"A user create network Net1,plugin check the configuration,if"},{"line_number":31,"context_line":"``tenant_network_type`` equals shared_vlan,it will invoke shared vlan dirver."},{"line_number":32,"context_line":"Shared VLAN driver will allocate ``segment``,and assgin ``network_type`` with"},{"line_number":33,"context_line":"vlan,and update network with ``segment`` and ``network_type`` to DB."},{"line_number":34,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_446d8197","line":31,"updated":"2016-04-12 22:56:40.000000000","message":"- equals\n+ equals to","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":28,"context_line":"**Use case for shared VLAN:**"},{"line_number":29,"context_line":""},{"line_number":30,"context_line":"A user create network Net1,plugin check the configuration,if"},{"line_number":31,"context_line":"``tenant_network_type`` equals shared_vlan,it will invoke shared vlan dirver."},{"line_number":32,"context_line":"Shared VLAN driver will allocate ``segment``,and assgin ``network_type`` with"},{"line_number":33,"context_line":"vlan,and update network with ``segment`` and ``network_type`` to DB."},{"line_number":34,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_90e34505","line":31,"range":{"start_line":31,"start_character":65,"end_line":31,"end_character":69},"in_reply_to":"5a18252c_40360853","updated":"2016-04-13 09:25:41.000000000","message":"Done","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":28,"context_line":"**Use case for shared VLAN:**"},{"line_number":29,"context_line":""},{"line_number":30,"context_line":"A user create network Net1,plugin check the configuration,if"},{"line_number":31,"context_line":"``tenant_network_type`` equals shared_vlan,it will invoke shared vlan dirver."},{"line_number":32,"context_line":"Shared VLAN driver will allocate ``segment``,and assgin ``network_type`` with"},{"line_number":33,"context_line":"vlan,and update network with ``segment`` and ``network_type`` to DB."},{"line_number":34,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_50e1adfd","line":31,"in_reply_to":"5a18252c_446d8197","updated":"2016-04-13 09:25:41.000000000","message":"Done","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"346604c3992b6ead6767b236251e52626e883fb6","unresolved":false,"context_lines":[{"line_number":29,"context_line":""},{"line_number":30,"context_line":"A user create network Net1,plugin check the configuration,if"},{"line_number":31,"context_line":"``tenant_network_type`` equals shared_vlan,it will invoke shared vlan dirver."},{"line_number":32,"context_line":"Shared VLAN driver will allocate ``segment``,and assgin ``network_type`` with"},{"line_number":33,"context_line":"vlan,and update network with ``segment`` and ``network_type`` to DB."},{"line_number":34,"context_line":""},{"line_number":35,"context_line":"A user create VM1 in AZ1,and connect to network Net1.If vm will be booted in"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_240165af","line":32,"updated":"2016-04-12 22:56:40.000000000","message":"- assgin\n+ assign","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":29,"context_line":""},{"line_number":30,"context_line":"A user create network Net1,plugin check the configuration,if"},{"line_number":31,"context_line":"``tenant_network_type`` equals shared_vlan,it will invoke shared vlan dirver."},{"line_number":32,"context_line":"Shared VLAN driver will allocate ``segment``,and assgin ``network_type`` with"},{"line_number":33,"context_line":"vlan,and update network with ``segment`` and ``network_type`` to DB."},{"line_number":34,"context_line":""},{"line_number":35,"context_line":"A user create VM1 in AZ1,and connect to network Net1.If vm will be booted in"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_d0edbdf0","line":32,"in_reply_to":"5a18252c_240165af","updated":"2016-04-13 09:25:41.000000000","message":"Done","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":20405,"name":"liuhaixia","email":"liuhaixia315@huawei.com","username":"liuhaixia"},"change_message_id":"1474553f664e370a1ce3cd96a66a085a13596db7","unresolved":false,"context_lines":[{"line_number":30,"context_line":"A user create network Net1,plugin check the configuration,if"},{"line_number":31,"context_line":"``tenant_network_type`` equals shared_vlan,it will invoke shared vlan dirver."},{"line_number":32,"context_line":"Shared VLAN driver will allocate ``segment``,and assgin ``network_type`` with"},{"line_number":33,"context_line":"vlan,and update network with ``segment`` and ``network_type`` to DB."},{"line_number":34,"context_line":""},{"line_number":35,"context_line":"A user create VM1 in AZ1,and connect to network Net1.If vm will be booted in"},{"line_number":36,"context_line":"POD1,tricircle will send create network message to POD1.Create network message"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_63218eb4","line":33,"range":{"start_line":33,"start_character":16,"end_line":33,"end_character":39},"updated":"2016-04-13 03:02:16.000000000","message":"As I know, for vlan network, physical_network is required.","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":30,"context_line":"A user create network Net1,plugin check the configuration,if"},{"line_number":31,"context_line":"``tenant_network_type`` equals shared_vlan,it will invoke shared vlan dirver."},{"line_number":32,"context_line":"Shared VLAN driver will allocate ``segment``,and assgin ``network_type`` with"},{"line_number":33,"context_line":"vlan,and update network with ``segment`` and ``network_type`` to DB."},{"line_number":34,"context_line":""},{"line_number":35,"context_line":"A user create VM1 in AZ1,and connect to network Net1.If vm will be booted in"},{"line_number":36,"context_line":"POD1,tricircle will send create network message to POD1.Create network message"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_9fa4f6a6","line":33,"range":{"start_line":33,"start_character":16,"end_line":33,"end_character":39},"in_reply_to":"5a18252c_63218eb4","updated":"2016-04-13 09:25:41.000000000","message":"update network with \"segment\", \"physical_network\" and \"network_type\".","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"346604c3992b6ead6767b236251e52626e883fb6","unresolved":false,"context_lines":[{"line_number":32,"context_line":"Shared VLAN driver will allocate ``segment``,and assgin ``network_type`` with"},{"line_number":33,"context_line":"vlan,and update network with ``segment`` and ``network_type`` to DB."},{"line_number":34,"context_line":""},{"line_number":35,"context_line":"A user create VM1 in AZ1,and connect to network Net1.If vm will be booted in"},{"line_number":36,"context_line":"POD1,tricircle will send create network message to POD1.Create network message"},{"line_number":37,"context_line":"includes ``network_type`` and ``segment``."},{"line_number":38,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_e4e48d0e","line":35,"updated":"2016-04-12 22:56:40.000000000","message":"- create\n+ creates\n\n- connect to\n+ connects it to","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21067,"name":"lige","email":"eros.lige@gmail.com","username":"lige"},"change_message_id":"82505468ec383401c60fb5499c09b1a66599c644","unresolved":false,"context_lines":[{"line_number":32,"context_line":"Shared VLAN driver will allocate ``segment``,and assgin ``network_type`` with"},{"line_number":33,"context_line":"vlan,and update network with ``segment`` and ``network_type`` to DB."},{"line_number":34,"context_line":""},{"line_number":35,"context_line":"A user create VM1 in AZ1,and connect to network Net1.If vm will be booted in"},{"line_number":36,"context_line":"POD1,tricircle will send create network message to POD1.Create network message"},{"line_number":37,"context_line":"includes ``network_type`` and ``segment``."},{"line_number":38,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_cb9af96d","line":35,"range":{"start_line":35,"start_character":56,"end_line":35,"end_character":58},"updated":"2016-04-14 02:50:53.000000000","message":"-\"vm\" +\"VM1\"","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":20405,"name":"liuhaixia","email":"liuhaixia315@huawei.com","username":"liuhaixia"},"change_message_id":"1474553f664e370a1ce3cd96a66a085a13596db7","unresolved":false,"context_lines":[{"line_number":32,"context_line":"Shared VLAN driver will allocate ``segment``,and assgin ``network_type`` with"},{"line_number":33,"context_line":"vlan,and update network with ``segment`` and ``network_type`` to DB."},{"line_number":34,"context_line":""},{"line_number":35,"context_line":"A user create VM1 in AZ1,and connect to network Net1.If vm will be booted in"},{"line_number":36,"context_line":"POD1,tricircle will send create network message to POD1.Create network message"},{"line_number":37,"context_line":"includes ``network_type`` and ``segment``."},{"line_number":38,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_c3306204","line":35,"range":{"start_line":35,"start_character":51,"end_line":35,"end_character":53},"updated":"2016-04-13 03:02:16.000000000","message":"space","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":32,"context_line":"Shared VLAN driver will allocate ``segment``,and assgin ``network_type`` with"},{"line_number":33,"context_line":"vlan,and update network with ``segment`` and ``network_type`` to DB."},{"line_number":34,"context_line":""},{"line_number":35,"context_line":"A user create VM1 in AZ1,and connect to network Net1.If vm will be booted in"},{"line_number":36,"context_line":"POD1,tricircle will send create network message to POD1.Create network message"},{"line_number":37,"context_line":"includes ``network_type`` and ``segment``."},{"line_number":38,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_10be15d4","line":35,"range":{"start_line":35,"start_character":51,"end_line":35,"end_character":53},"in_reply_to":"5a18252c_c3306204","updated":"2016-04-13 09:25:41.000000000","message":"Done","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":32,"context_line":"Shared VLAN driver will allocate ``segment``,and assgin ``network_type`` with"},{"line_number":33,"context_line":"vlan,and update network with ``segment`` and ``network_type`` to DB."},{"line_number":34,"context_line":""},{"line_number":35,"context_line":"A user create VM1 in AZ1,and connect to network Net1.If vm will be booted in"},{"line_number":36,"context_line":"POD1,tricircle will send create network message to POD1.Create network message"},{"line_number":37,"context_line":"includes ``network_type`` and ``segment``."},{"line_number":38,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_30bb51e7","line":35,"in_reply_to":"5a18252c_e4e48d0e","updated":"2016-04-13 09:25:41.000000000","message":"Done","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":20405,"name":"liuhaixia","email":"liuhaixia315@huawei.com","username":"liuhaixia"},"change_message_id":"1474553f664e370a1ce3cd96a66a085a13596db7","unresolved":false,"context_lines":[{"line_number":34,"context_line":""},{"line_number":35,"context_line":"A user create VM1 in AZ1,and connect to network Net1.If vm will be booted in"},{"line_number":36,"context_line":"POD1,tricircle will send create network message to POD1.Create network message"},{"line_number":37,"context_line":"includes ``network_type`` and ``segment``."},{"line_number":38,"context_line":""},{"line_number":39,"context_line":"Then user create VM2 in AZ2,and connect to network Net1.If vm will be booted"},{"line_number":40,"context_line":"in POD2,``tricircle``(``Nova-APIGW`` need to get the network info)will send"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_a32ba693","line":37,"range":{"start_line":37,"start_character":33,"end_line":37,"end_character":42},"updated":"2016-04-13 03:02:16.000000000","message":"As above","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":34,"context_line":""},{"line_number":35,"context_line":"A user create VM1 in AZ1,and connect to network Net1.If vm will be booted in"},{"line_number":36,"context_line":"POD1,tricircle will send create network message to POD1.Create network message"},{"line_number":37,"context_line":"includes ``network_type`` and ``segment``."},{"line_number":38,"context_line":""},{"line_number":39,"context_line":"Then user create VM2 in AZ2,and connect to network Net1.If vm will be booted"},{"line_number":40,"context_line":"in POD2,``tricircle``(``Nova-APIGW`` need to get the network info)will send"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_7f22ba02","line":37,"range":{"start_line":37,"start_character":33,"end_line":37,"end_character":42},"in_reply_to":"5a18252c_a32ba693","updated":"2016-04-13 09:25:41.000000000","message":"includes \"network_type\", \"segment\" and \"physical_network\".","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"346604c3992b6ead6767b236251e52626e883fb6","unresolved":false,"context_lines":[{"line_number":36,"context_line":"POD1,tricircle will send create network message to POD1.Create network message"},{"line_number":37,"context_line":"includes ``network_type`` and ``segment``."},{"line_number":38,"context_line":""},{"line_number":39,"context_line":"Then user create VM2 in AZ2,and connect to network Net1.If vm will be booted"},{"line_number":40,"context_line":"in POD2,``tricircle``(``Nova-APIGW`` need to get the network info)will send"},{"line_number":41,"context_line":"create network message to POD2.Create network message includes ``network_type``"},{"line_number":42,"context_line":"and ``segment``."}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_c4b4f1f3","line":39,"updated":"2016-04-12 22:56:40.000000000","message":"- create\n+ creates\n\n- connect\n+ connects it to","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21067,"name":"lige","email":"eros.lige@gmail.com","username":"lige"},"change_message_id":"82505468ec383401c60fb5499c09b1a66599c644","unresolved":false,"context_lines":[{"line_number":36,"context_line":"POD1,tricircle will send create network message to POD1.Create network message"},{"line_number":37,"context_line":"includes ``network_type`` and ``segment``."},{"line_number":38,"context_line":""},{"line_number":39,"context_line":"Then user create VM2 in AZ2,and connect to network Net1.If vm will be booted"},{"line_number":40,"context_line":"in POD2,``tricircle``(``Nova-APIGW`` need to get the network info)will send"},{"line_number":41,"context_line":"create network message to POD2.Create network message includes ``network_type``"},{"line_number":42,"context_line":"and ``segment``."}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_e87ffba8","line":39,"range":{"start_line":39,"start_character":4,"end_line":39,"end_character":9},"updated":"2016-04-14 02:50:53.000000000","message":"add \"the\" in front of \"user\"","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":36,"context_line":"POD1,tricircle will send create network message to POD1.Create network message"},{"line_number":37,"context_line":"includes ``network_type`` and ``segment``."},{"line_number":38,"context_line":""},{"line_number":39,"context_line":"Then user create VM2 in AZ2,and connect to network Net1.If vm will be booted"},{"line_number":40,"context_line":"in POD2,``tricircle``(``Nova-APIGW`` need to get the network info)will send"},{"line_number":41,"context_line":"create network message to POD2.Create network message includes ``network_type``"},{"line_number":42,"context_line":"and ``segment``."}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_70b5c9ec","line":39,"in_reply_to":"5a18252c_c4b4f1f3","updated":"2016-04-13 09:25:41.000000000","message":"Done","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"346604c3992b6ead6767b236251e52626e883fb6","unresolved":false,"context_lines":[{"line_number":37,"context_line":"includes ``network_type`` and ``segment``."},{"line_number":38,"context_line":""},{"line_number":39,"context_line":"Then user create VM2 in AZ2,and connect to network Net1.If vm will be booted"},{"line_number":40,"context_line":"in POD2,``tricircle``(``Nova-APIGW`` need to get the network info)will send"},{"line_number":41,"context_line":"create network message to POD2.Create network message includes ``network_type``"},{"line_number":42,"context_line":"and ``segment``."},{"line_number":43,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_44c90178","line":40,"updated":"2016-04-12 22:56:40.000000000","message":"- need\n+ needs","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":37,"context_line":"includes ``network_type`` and ``segment``."},{"line_number":38,"context_line":""},{"line_number":39,"context_line":"Then user create VM2 in AZ2,and connect to network Net1.If vm will be booted"},{"line_number":40,"context_line":"in POD2,``tricircle``(``Nova-APIGW`` need to get the network info)will send"},{"line_number":41,"context_line":"create network message to POD2.Create network message includes ``network_type``"},{"line_number":42,"context_line":"and ``segment``."},{"line_number":43,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_50b88de5","line":40,"in_reply_to":"5a18252c_44c90178","updated":"2016-04-13 09:25:41.000000000","message":"Done","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":38,"context_line":""},{"line_number":39,"context_line":"Then user create VM2 in AZ2,and connect to network Net1.If vm will be booted"},{"line_number":40,"context_line":"in POD2,``tricircle``(``Nova-APIGW`` need to get the network info)will send"},{"line_number":41,"context_line":"create network message to POD2.Create network message includes ``network_type``"},{"line_number":42,"context_line":"and ``segment``."},{"line_number":43,"context_line":""},{"line_number":44,"context_line":"**Use case for different VLAN:**"},{"line_number":45,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_5fe9be7f","line":42,"range":{"start_line":41,"start_character":54,"end_line":42,"end_character":16},"updated":"2016-04-13 09:25:41.000000000","message":"includes \"network_type\", \"segment\" and \"physical_network\".","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"346604c3992b6ead6767b236251e52626e883fb6","unresolved":false,"context_lines":[{"line_number":43,"context_line":""},{"line_number":44,"context_line":"**Use case for different VLAN:**"},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"A user create network Net1,plugin check the configuration,if"},{"line_number":47,"context_line":"``tenant_network_type`` equals multi_vlan,it will invoke multi vlan driver."},{"line_number":48,"context_line":"Multi vlan dirver need to do nothing(if segment is allocated in bottom)."},{"line_number":49,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_c4ab5188","line":46,"updated":"2016-04-12 22:56:40.000000000","message":"- create\n+ creates\n\n- check\n+ checks","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":43,"context_line":""},{"line_number":44,"context_line":"**Use case for different VLAN:**"},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"A user create network Net1,plugin check the configuration,if"},{"line_number":47,"context_line":"``tenant_network_type`` equals multi_vlan,it will invoke multi vlan driver."},{"line_number":48,"context_line":"Multi vlan dirver need to do nothing(if segment is allocated in bottom)."},{"line_number":49,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_b0cf617e","line":46,"in_reply_to":"5a18252c_c4ab5188","updated":"2016-04-13 09:25:41.000000000","message":"Done","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"346604c3992b6ead6767b236251e52626e883fb6","unresolved":false,"context_lines":[{"line_number":44,"context_line":"**Use case for different VLAN:**"},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"A user create network Net1,plugin check the configuration,if"},{"line_number":47,"context_line":"``tenant_network_type`` equals multi_vlan,it will invoke multi vlan driver."},{"line_number":48,"context_line":"Multi vlan dirver need to do nothing(if segment is allocated in bottom)."},{"line_number":49,"context_line":""},{"line_number":50,"context_line":"A user create VM1 in AZ1,and connect to the network Net1,the VM is booted in"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_e492cd56","line":47,"updated":"2016-04-12 22:56:40.000000000","message":"- equals\n+ equals to","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":44,"context_line":"**Use case for different VLAN:**"},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"A user create network Net1,plugin check the configuration,if"},{"line_number":47,"context_line":"``tenant_network_type`` equals multi_vlan,it will invoke multi vlan driver."},{"line_number":48,"context_line":"Multi vlan dirver need to do nothing(if segment is allocated in bottom)."},{"line_number":49,"context_line":""},{"line_number":50,"context_line":"A user create VM1 in AZ1,and connect to the network Net1,the VM is booted in"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_90ca256d","line":47,"in_reply_to":"5a18252c_e492cd56","updated":"2016-04-13 09:25:41.000000000","message":"Done","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"346604c3992b6ead6767b236251e52626e883fb6","unresolved":false,"context_lines":[{"line_number":45,"context_line":""},{"line_number":46,"context_line":"A user create network Net1,plugin check the configuration,if"},{"line_number":47,"context_line":"``tenant_network_type`` equals multi_vlan,it will invoke multi vlan driver."},{"line_number":48,"context_line":"Multi vlan dirver need to do nothing(if segment is allocated in bottom)."},{"line_number":49,"context_line":""},{"line_number":50,"context_line":"A user create VM1 in AZ1,and connect to the network Net1,the VM is booted in"},{"line_number":51,"context_line":"bottom POD1,and ``Nova-APIGW`` create network in POD1,then ``Nova-APIGW`` query"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_648d1d31","line":48,"updated":"2016-04-12 22:56:40.000000000","message":"- need\n+ needs","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"8167600fefc797003f84fb660476ed1945b3c4ca","unresolved":false,"context_lines":[{"line_number":45,"context_line":""},{"line_number":46,"context_line":"A user create network Net1,plugin check the configuration,if"},{"line_number":47,"context_line":"``tenant_network_type`` equals multi_vlan,it will invoke multi vlan driver."},{"line_number":48,"context_line":"Multi vlan dirver need to do nothing(if segment is allocated in bottom)."},{"line_number":49,"context_line":""},{"line_number":50,"context_line":"A user create VM1 in AZ1,and connect to the network Net1,the VM is booted in"},{"line_number":51,"context_line":"bottom POD1,and ``Nova-APIGW`` create network in POD1,then ``Nova-APIGW`` query"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_e3159e9b","line":48,"range":{"start_line":48,"start_character":37,"end_line":48,"end_character":39},"updated":"2016-04-13 02:52:47.000000000","message":"if -\u003e for","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":45,"context_line":""},{"line_number":46,"context_line":"A user create network Net1,plugin check the configuration,if"},{"line_number":47,"context_line":"``tenant_network_type`` equals multi_vlan,it will invoke multi vlan driver."},{"line_number":48,"context_line":"Multi vlan dirver need to do nothing(if segment is allocated in bottom)."},{"line_number":49,"context_line":""},{"line_number":50,"context_line":"A user create VM1 in AZ1,and connect to the network Net1,the VM is booted in"},{"line_number":51,"context_line":"bottom POD1,and ``Nova-APIGW`` create network in POD1,then ``Nova-APIGW`` query"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_30a231af","line":48,"in_reply_to":"5a18252c_648d1d31","updated":"2016-04-13 09:25:41.000000000","message":"Done","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":45,"context_line":""},{"line_number":46,"context_line":"A user create network Net1,plugin check the configuration,if"},{"line_number":47,"context_line":"``tenant_network_type`` equals multi_vlan,it will invoke multi vlan driver."},{"line_number":48,"context_line":"Multi vlan dirver need to do nothing(if segment is allocated in bottom)."},{"line_number":49,"context_line":""},{"line_number":50,"context_line":"A user create VM1 in AZ1,and connect to the network Net1,the VM is booted in"},{"line_number":51,"context_line":"bottom POD1,and ``Nova-APIGW`` create network in POD1,then ``Nova-APIGW`` query"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_10a575b4","line":48,"range":{"start_line":48,"start_character":37,"end_line":48,"end_character":39},"in_reply_to":"5a18252c_e3159e9b","updated":"2016-04-13 09:25:41.000000000","message":"Done","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"346604c3992b6ead6767b236251e52626e883fb6","unresolved":false,"context_lines":[{"line_number":47,"context_line":"``tenant_network_type`` equals multi_vlan,it will invoke multi vlan driver."},{"line_number":48,"context_line":"Multi vlan dirver need to do nothing(if segment is allocated in bottom)."},{"line_number":49,"context_line":""},{"line_number":50,"context_line":"A user create VM1 in AZ1,and connect to the network Net1,the VM is booted in"},{"line_number":51,"context_line":"bottom POD1,and ``Nova-APIGW`` create network in POD1,then ``Nova-APIGW`` query"},{"line_number":52,"context_line":"the network detail information(using admin role),and get network type,segment"},{"line_number":53,"context_line":"id,the ``Nova-APIGW`` update the segment infomation to ``Neutron``,call"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_a49e1554","line":50,"updated":"2016-04-12 22:56:40.000000000","message":"- create\n+ creates\n\n- connect to\n+ connects it to","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":47,"context_line":"``tenant_network_type`` equals multi_vlan,it will invoke multi vlan driver."},{"line_number":48,"context_line":"Multi vlan dirver need to do nothing(if segment is allocated in bottom)."},{"line_number":49,"context_line":""},{"line_number":50,"context_line":"A user create VM1 in AZ1,and connect to the network Net1,the VM is booted in"},{"line_number":51,"context_line":"bottom POD1,and ``Nova-APIGW`` create network in POD1,then ``Nova-APIGW`` query"},{"line_number":52,"context_line":"the network detail information(using admin role),and get network type,segment"},{"line_number":53,"context_line":"id,the ``Nova-APIGW`` update the segment infomation to ``Neutron``,call"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_50afed93","line":50,"in_reply_to":"5a18252c_a49e1554","updated":"2016-04-13 09:25:41.000000000","message":"Done","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"346604c3992b6ead6767b236251e52626e883fb6","unresolved":false,"context_lines":[{"line_number":48,"context_line":"Multi vlan dirver need to do nothing(if segment is allocated in bottom)."},{"line_number":49,"context_line":""},{"line_number":50,"context_line":"A user create VM1 in AZ1,and connect to the network Net1,the VM is booted in"},{"line_number":51,"context_line":"bottom POD1,and ``Nova-APIGW`` create network in POD1,then ``Nova-APIGW`` query"},{"line_number":52,"context_line":"the network detail information(using admin role),and get network type,segment"},{"line_number":53,"context_line":"id,the ``Nova-APIGW`` update the segment infomation to ``Neutron``,call"},{"line_number":54,"context_line":"``neutron`` update network with the new segment information."}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_84b679da","line":51,"updated":"2016-04-12 22:56:40.000000000","message":"- create\n+ creates\n\n- query\n+ queries","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":48,"context_line":"Multi vlan dirver need to do nothing(if segment is allocated in bottom)."},{"line_number":49,"context_line":""},{"line_number":50,"context_line":"A user create VM1 in AZ1,and connect to the network Net1,the VM is booted in"},{"line_number":51,"context_line":"bottom POD1,and ``Nova-APIGW`` create network in POD1,then ``Nova-APIGW`` query"},{"line_number":52,"context_line":"the network detail information(using admin role),and get network type,segment"},{"line_number":53,"context_line":"id,the ``Nova-APIGW`` update the segment infomation to ``Neutron``,call"},{"line_number":54,"context_line":"``neutron`` update network with the new segment information."}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_90918555","line":51,"in_reply_to":"5a18252c_84b679da","updated":"2016-04-13 09:25:41.000000000","message":"Done","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"346604c3992b6ead6767b236251e52626e883fb6","unresolved":false,"context_lines":[{"line_number":49,"context_line":""},{"line_number":50,"context_line":"A user create VM1 in AZ1,and connect to the network Net1,the VM is booted in"},{"line_number":51,"context_line":"bottom POD1,and ``Nova-APIGW`` create network in POD1,then ``Nova-APIGW`` query"},{"line_number":52,"context_line":"the network detail information(using admin role),and get network type,segment"},{"line_number":53,"context_line":"id,the ``Nova-APIGW`` update the segment infomation to ``Neutron``,call"},{"line_number":54,"context_line":"``neutron`` update network with the new segment information."},{"line_number":55,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_c4e7d1e2","line":52,"updated":"2016-04-12 22:56:40.000000000","message":"- get\n+ gets","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":49,"context_line":""},{"line_number":50,"context_line":"A user create VM1 in AZ1,and connect to the network Net1,the VM is booted in"},{"line_number":51,"context_line":"bottom POD1,and ``Nova-APIGW`` create network in POD1,then ``Nova-APIGW`` query"},{"line_number":52,"context_line":"the network detail information(using admin role),and get network type,segment"},{"line_number":53,"context_line":"id,the ``Nova-APIGW`` update the segment infomation to ``Neutron``,call"},{"line_number":54,"context_line":"``neutron`` update network with the new segment information."},{"line_number":55,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_f0a0b9a1","line":52,"in_reply_to":"5a18252c_c4e7d1e2","updated":"2016-04-13 09:25:41.000000000","message":"Done","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"346604c3992b6ead6767b236251e52626e883fb6","unresolved":false,"context_lines":[{"line_number":50,"context_line":"A user create VM1 in AZ1,and connect to the network Net1,the VM is booted in"},{"line_number":51,"context_line":"bottom POD1,and ``Nova-APIGW`` create network in POD1,then ``Nova-APIGW`` query"},{"line_number":52,"context_line":"the network detail information(using admin role),and get network type,segment"},{"line_number":53,"context_line":"id,the ``Nova-APIGW`` update the segment infomation to ``Neutron``,call"},{"line_number":54,"context_line":"``neutron`` update network with the new segment information."},{"line_number":55,"context_line":""},{"line_number":56,"context_line":"Then the user create another VM2,and with az info AZ2,then the VM should be"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_8404b97e","line":53,"updated":"2016-04-12 22:56:40.000000000","message":"- update\n+ updates","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":50,"context_line":"A user create VM1 in AZ1,and connect to the network Net1,the VM is booted in"},{"line_number":51,"context_line":"bottom POD1,and ``Nova-APIGW`` create network in POD1,then ``Nova-APIGW`` query"},{"line_number":52,"context_line":"the network detail information(using admin role),and get network type,segment"},{"line_number":53,"context_line":"id,the ``Nova-APIGW`` update the segment infomation to ``Neutron``,call"},{"line_number":54,"context_line":"``neutron`` update network with the new segment information."},{"line_number":55,"context_line":""},{"line_number":56,"context_line":"Then the user create another VM2,and with az info AZ2,then the VM should be"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_30899127","line":53,"in_reply_to":"5a18252c_8404b97e","updated":"2016-04-13 09:25:41.000000000","message":"Done","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"8167600fefc797003f84fb660476ed1945b3c4ca","unresolved":false,"context_lines":[{"line_number":51,"context_line":"bottom POD1,and ``Nova-APIGW`` create network in POD1,then ``Nova-APIGW`` query"},{"line_number":52,"context_line":"the network detail information(using admin role),and get network type,segment"},{"line_number":53,"context_line":"id,the ``Nova-APIGW`` update the segment infomation to ``Neutron``,call"},{"line_number":54,"context_line":"``neutron`` update network with the new segment information."},{"line_number":55,"context_line":""},{"line_number":56,"context_line":"Then the user create another VM2,and with az info AZ2,then the VM should be"},{"line_number":57,"context_line":"booted in bottom pod2 which is located in AZ2,And when VM2 should be booted in"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_03c89a21","line":54,"range":{"start_line":54,"start_character":36,"end_line":54,"end_character":39},"updated":"2016-04-13 02:52:47.000000000","message":"Then the driver need to to call DCI SDN controller, or L2GW or other controller to pass this new segment to one network. The format could be ( network-id, added segment info, deleted segment info).","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":51,"context_line":"bottom POD1,and ``Nova-APIGW`` create network in POD1,then ``Nova-APIGW`` query"},{"line_number":52,"context_line":"the network detail information(using admin role),and get network type,segment"},{"line_number":53,"context_line":"id,the ``Nova-APIGW`` update the segment infomation to ``Neutron``,call"},{"line_number":54,"context_line":"``neutron`` update network with the new segment information."},{"line_number":55,"context_line":""},{"line_number":56,"context_line":"Then the user create another VM2,and with az info AZ2,then the VM should be"},{"line_number":57,"context_line":"booted in bottom pod2 which is located in AZ2,And when VM2 should be booted in"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_5086cd13","line":54,"range":{"start_line":54,"start_character":36,"end_line":54,"end_character":39},"in_reply_to":"5a18252c_03c89a21","updated":"2016-04-13 09:25:41.000000000","message":"Done","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"346604c3992b6ead6767b236251e52626e883fb6","unresolved":false,"context_lines":[{"line_number":53,"context_line":"id,the ``Nova-APIGW`` update the segment infomation to ``Neutron``,call"},{"line_number":54,"context_line":"``neutron`` update network with the new segment information."},{"line_number":55,"context_line":""},{"line_number":56,"context_line":"Then the user create another VM2,and with az info AZ2,then the VM should be"},{"line_number":57,"context_line":"booted in bottom pod2 which is located in AZ2,And when VM2 should be booted in"},{"line_number":58,"context_line":"AZ2,``Nova-APIGW`` also create a network in pod2,and query the network"},{"line_number":59,"context_line":"information including segment and network type,update this new segment to the"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_8412f9b2","line":56,"updated":"2016-04-12 22:56:40.000000000","message":"- create\n+ creates\n\n- should be\n+ should be able to be","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21067,"name":"lige","email":"eros.lige@gmail.com","username":"lige"},"change_message_id":"82505468ec383401c60fb5499c09b1a66599c644","unresolved":false,"context_lines":[{"line_number":53,"context_line":"id,the ``Nova-APIGW`` update the segment infomation to ``Neutron``,call"},{"line_number":54,"context_line":"``neutron`` update network with the new segment information."},{"line_number":55,"context_line":""},{"line_number":56,"context_line":"Then the user create another VM2,and with az info AZ2,then the VM should be"},{"line_number":57,"context_line":"booted in bottom pod2 which is located in AZ2,And when VM2 should be booted in"},{"line_number":58,"context_line":"AZ2,``Nova-APIGW`` also create a network in pod2,and query the network"},{"line_number":59,"context_line":"information including segment and network type,update this new segment to the"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_cba8397a","line":56,"range":{"start_line":56,"start_character":63,"end_line":56,"end_character":65},"updated":"2016-04-14 02:50:53.000000000","message":"-\"VM\" +\"VM2\"","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":53,"context_line":"id,the ``Nova-APIGW`` update the segment infomation to ``Neutron``,call"},{"line_number":54,"context_line":"``neutron`` update network with the new segment information."},{"line_number":55,"context_line":""},{"line_number":56,"context_line":"Then the user create another VM2,and with az info AZ2,then the VM should be"},{"line_number":57,"context_line":"booted in bottom pod2 which is located in AZ2,And when VM2 should be booted in"},{"line_number":58,"context_line":"AZ2,``Nova-APIGW`` also create a network in pod2,and query the network"},{"line_number":59,"context_line":"information including segment and network type,update this new segment to the"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_b07da11e","line":56,"in_reply_to":"5a18252c_8412f9b2","updated":"2016-04-13 09:25:41.000000000","message":"Done","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21067,"name":"lige","email":"eros.lige@gmail.com","username":"lige"},"change_message_id":"82505468ec383401c60fb5499c09b1a66599c644","unresolved":false,"context_lines":[{"line_number":54,"context_line":"``neutron`` update network with the new segment information."},{"line_number":55,"context_line":""},{"line_number":56,"context_line":"Then the user create another VM2,and with az info AZ2,then the VM should be"},{"line_number":57,"context_line":"booted in bottom pod2 which is located in AZ2,And when VM2 should be booted in"},{"line_number":58,"context_line":"AZ2,``Nova-APIGW`` also create a network in pod2,and query the network"},{"line_number":59,"context_line":"information including segment and network type,update this new segment to the"},{"line_number":60,"context_line":"network in ``Neutron``."}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_e8e37ba2","line":57,"range":{"start_line":57,"start_character":46,"end_line":57,"end_character":49},"updated":"2016-04-14 02:50:53.000000000","message":"- And + and","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"346604c3992b6ead6767b236251e52626e883fb6","unresolved":false,"context_lines":[{"line_number":54,"context_line":"``neutron`` update network with the new segment information."},{"line_number":55,"context_line":""},{"line_number":56,"context_line":"Then the user create another VM2,and with az info AZ2,then the VM should be"},{"line_number":57,"context_line":"booted in bottom pod2 which is located in AZ2,And when VM2 should be booted in"},{"line_number":58,"context_line":"AZ2,``Nova-APIGW`` also create a network in pod2,and query the network"},{"line_number":59,"context_line":"information including segment and network type,update this new segment to the"},{"line_number":60,"context_line":"network in ``Neutron``."}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_647ebde5","line":57,"updated":"2016-04-12 22:56:40.000000000","message":"- should be \n+ should be able to be","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":54,"context_line":"``neutron`` update network with the new segment information."},{"line_number":55,"context_line":""},{"line_number":56,"context_line":"Then the user create another VM2,and with az info AZ2,then the VM should be"},{"line_number":57,"context_line":"booted in bottom pod2 which is located in AZ2,And when VM2 should be booted in"},{"line_number":58,"context_line":"AZ2,``Nova-APIGW`` also create a network in pod2,and query the network"},{"line_number":59,"context_line":"information including segment and network type,update this new segment to the"},{"line_number":60,"context_line":"network in ``Neutron``."}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_9078652d","line":57,"in_reply_to":"5a18252c_647ebde5","updated":"2016-04-13 09:25:41.000000000","message":"Done","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"346604c3992b6ead6767b236251e52626e883fb6","unresolved":false,"context_lines":[{"line_number":55,"context_line":""},{"line_number":56,"context_line":"Then the user create another VM2,and with az info AZ2,then the VM should be"},{"line_number":57,"context_line":"booted in bottom pod2 which is located in AZ2,And when VM2 should be booted in"},{"line_number":58,"context_line":"AZ2,``Nova-APIGW`` also create a network in pod2,and query the network"},{"line_number":59,"context_line":"information including segment and network type,update this new segment to the"},{"line_number":60,"context_line":"network in ``Neutron``."},{"line_number":61,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_4478e1f2","line":58,"updated":"2016-04-12 22:56:40.000000000","message":"- create\n+ creates\n\n- query\n+ queries","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":55,"context_line":""},{"line_number":56,"context_line":"Then the user create another VM2,and with az info AZ2,then the VM should be"},{"line_number":57,"context_line":"booted in bottom pod2 which is located in AZ2,And when VM2 should be booted in"},{"line_number":58,"context_line":"AZ2,``Nova-APIGW`` also create a network in pod2,and query the network"},{"line_number":59,"context_line":"information including segment and network type,update this new segment to the"},{"line_number":60,"context_line":"network in ``Neutron``."},{"line_number":61,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_f0771938","line":58,"in_reply_to":"5a18252c_4478e1f2","updated":"2016-04-13 09:25:41.000000000","message":"Done","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"346604c3992b6ead6767b236251e52626e883fb6","unresolved":false,"context_lines":[{"line_number":56,"context_line":"Then the user create another VM2,and with az info AZ2,then the VM should be"},{"line_number":57,"context_line":"booted in bottom pod2 which is located in AZ2,And when VM2 should be booted in"},{"line_number":58,"context_line":"AZ2,``Nova-APIGW`` also create a network in pod2,and query the network"},{"line_number":59,"context_line":"information including segment and network type,update this new segment to the"},{"line_number":60,"context_line":"network in ``Neutron``."},{"line_number":61,"context_line":""},{"line_number":62,"context_line":"Proposed change"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_64651d44","line":59,"updated":"2016-04-12 22:56:40.000000000","message":"- update\n+ updates","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":56,"context_line":"Then the user create another VM2,and with az info AZ2,then the VM should be"},{"line_number":57,"context_line":"booted in bottom pod2 which is located in AZ2,And when VM2 should be booted in"},{"line_number":58,"context_line":"AZ2,``Nova-APIGW`` also create a network in pod2,and query the network"},{"line_number":59,"context_line":"information including segment and network type,update this new segment to the"},{"line_number":60,"context_line":"network in ``Neutron``."},{"line_number":61,"context_line":""},{"line_number":62,"context_line":"Proposed change"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_d072dd48","line":59,"in_reply_to":"5a18252c_64651d44","updated":"2016-04-13 09:25:41.000000000","message":"Done","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"8167600fefc797003f84fb660476ed1945b3c4ca","unresolved":false,"context_lines":[{"line_number":57,"context_line":"booted in bottom pod2 which is located in AZ2,And when VM2 should be booted in"},{"line_number":58,"context_line":"AZ2,``Nova-APIGW`` also create a network in pod2,and query the network"},{"line_number":59,"context_line":"information including segment and network type,update this new segment to the"},{"line_number":60,"context_line":"network in ``Neutron``."},{"line_number":61,"context_line":""},{"line_number":62,"context_line":"Proposed change"},{"line_number":63,"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":"5a18252c_43d292d3","line":60,"range":{"start_line":60,"start_character":20,"end_line":60,"end_character":23},"updated":"2016-04-13 02:52:47.000000000","message":"Then the driver need to to call DCI SDN controller or L2GW or other controller to pass this new segment to one network. The format could be ( network-id, added segment info, deleted segment info).","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":57,"context_line":"booted in bottom pod2 which is located in AZ2,And when VM2 should be booted in"},{"line_number":58,"context_line":"AZ2,``Nova-APIGW`` also create a network in pod2,and query the network"},{"line_number":59,"context_line":"information including segment and network type,update this new segment to the"},{"line_number":60,"context_line":"network in ``Neutron``."},{"line_number":61,"context_line":""},{"line_number":62,"context_line":"Proposed change"},{"line_number":63,"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":"5a18252c_30907143","line":60,"range":{"start_line":60,"start_character":20,"end_line":60,"end_character":23},"in_reply_to":"5a18252c_43d292d3","updated":"2016-04-13 09:25:41.000000000","message":"Done","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"8167600fefc797003f84fb660476ed1945b3c4ca","unresolved":false,"context_lines":[{"line_number":59,"context_line":"information including segment and network type,update this new segment to the"},{"line_number":60,"context_line":"network in ``Neutron``."},{"line_number":61,"context_line":""},{"line_number":62,"context_line":"Proposed change"},{"line_number":63,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":64,"context_line":""},{"line_number":65,"context_line":"Difference between L2 networking for tenant\u0027s VM and for L3 bridging"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_03effa87","line":62,"range":{"start_line":62,"start_character":0,"end_line":62,"end_character":8},"updated":"2016-04-13 02:52:47.000000000","message":"Missing use cases of Shared VxLAN and Mixed VxLAN, Mixed VxLAN - VLAN","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"346604c3992b6ead6767b236251e52626e883fb6","unresolved":false,"context_lines":[{"line_number":62,"context_line":"Proposed change"},{"line_number":63,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":64,"context_line":""},{"line_number":65,"context_line":"Difference between L2 networking for tenant\u0027s VM and for L3 bridging"},{"line_number":66,"context_line":"network:"},{"line_number":67,"context_line":""},{"line_number":68,"context_line":"* A special bridge network is create and connect the routers in different"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_e4512d64","line":65,"updated":"2016-04-12 22:56:40.000000000","message":"- L2 networking\n+ each L2 networking","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":62,"context_line":"Proposed change"},{"line_number":63,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":64,"context_line":""},{"line_number":65,"context_line":"Difference between L2 networking for tenant\u0027s VM and for L3 bridging"},{"line_number":66,"context_line":"network:"},{"line_number":67,"context_line":""},{"line_number":68,"context_line":"* A special bridge network is create and connect the routers in different"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_709ae964","line":65,"in_reply_to":"5a18252c_e4512d64","updated":"2016-04-13 09:25:41.000000000","message":"Done","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"346604c3992b6ead6767b236251e52626e883fb6","unresolved":false,"context_lines":[{"line_number":65,"context_line":"Difference between L2 networking for tenant\u0027s VM and for L3 bridging"},{"line_number":66,"context_line":"network:"},{"line_number":67,"context_line":""},{"line_number":68,"context_line":"* A special bridge network is create and connect the routers in different"},{"line_number":69,"context_line":"  bottom OpenStack.We configure the extra routes of the routers to route the"},{"line_number":70,"context_line":"  packets from one OpenStack to another.In current implementation,we create"},{"line_number":71,"context_line":"  this special bridge network in each bottom OpenStack with the same"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_c4d191cf","line":68,"updated":"2016-04-12 22:56:40.000000000","message":"- create and connect\n+ created and connected to","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":65,"context_line":"Difference between L2 networking for tenant\u0027s VM and for L3 bridging"},{"line_number":66,"context_line":"network:"},{"line_number":67,"context_line":""},{"line_number":68,"context_line":"* A special bridge network is create and connect the routers in different"},{"line_number":69,"context_line":"  bottom OpenStack.We configure the extra routes of the routers to route the"},{"line_number":70,"context_line":"  packets from one OpenStack to another.In current implementation,we create"},{"line_number":71,"context_line":"  this special bridge network in each bottom OpenStack with the same"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_509d2d58","line":68,"in_reply_to":"5a18252c_c4d191cf","updated":"2016-04-13 09:25:41.000000000","message":"Done","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"346604c3992b6ead6767b236251e52626e883fb6","unresolved":false,"context_lines":[{"line_number":69,"context_line":"  bottom OpenStack.We configure the extra routes of the routers to route the"},{"line_number":70,"context_line":"  packets from one OpenStack to another.In current implementation,we create"},{"line_number":71,"context_line":"  this special bridge network in each bottom OpenStack with the same"},{"line_number":72,"context_line":"  ``VLAN ID``,so we have a L2 network to connect the routers."},{"line_number":73,"context_line":"* The creation of bridge network is triggered when attaching router interface"},{"line_number":74,"context_line":"  and adding router external gateway."},{"line_number":75,"context_line":"* The L2 network for VM is triggered by ``Nova-APIGW`` when a VM is to be"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_e4ff6d32","line":72,"updated":"2016-04-12 22:56:40.000000000","message":"- a L2\n+ an L2","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":69,"context_line":"  bottom OpenStack.We configure the extra routes of the routers to route the"},{"line_number":70,"context_line":"  packets from one OpenStack to another.In current implementation,we create"},{"line_number":71,"context_line":"  this special bridge network in each bottom OpenStack with the same"},{"line_number":72,"context_line":"  ``VLAN ID``,so we have a L2 network to connect the routers."},{"line_number":73,"context_line":"* The creation of bridge network is triggered when attaching router interface"},{"line_number":74,"context_line":"  and adding router external gateway."},{"line_number":75,"context_line":"* The L2 network for VM is triggered by ``Nova-APIGW`` when a VM is to be"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_b0a481a6","line":72,"in_reply_to":"5a18252c_e4ff6d32","updated":"2016-04-13 09:25:41.000000000","message":"Done","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"346604c3992b6ead6767b236251e52626e883fb6","unresolved":false,"context_lines":[{"line_number":70,"context_line":"  packets from one OpenStack to another.In current implementation,we create"},{"line_number":71,"context_line":"  this special bridge network in each bottom OpenStack with the same"},{"line_number":72,"context_line":"  ``VLAN ID``,so we have a L2 network to connect the routers."},{"line_number":73,"context_line":"* The creation of bridge network is triggered when attaching router interface"},{"line_number":74,"context_line":"  and adding router external gateway."},{"line_number":75,"context_line":"* The L2 network for VM is triggered by ``Nova-APIGW`` when a VM is to be"},{"line_number":76,"context_line":"  created in one pod, and find that there is no network there, then the"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_a4a45557","line":73,"updated":"2016-04-12 22:56:40.000000000","message":"- when\n+ during","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":70,"context_line":"  packets from one OpenStack to another.In current implementation,we create"},{"line_number":71,"context_line":"  this special bridge network in each bottom OpenStack with the same"},{"line_number":72,"context_line":"  ``VLAN ID``,so we have a L2 network to connect the routers."},{"line_number":73,"context_line":"* The creation of bridge network is triggered when attaching router interface"},{"line_number":74,"context_line":"  and adding router external gateway."},{"line_number":75,"context_line":"* The L2 network for VM is triggered by ``Nova-APIGW`` when a VM is to be"},{"line_number":76,"context_line":"  created in one pod, and find that there is no network there, then the"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_f0aef983","line":73,"in_reply_to":"5a18252c_a4a45557","updated":"2016-04-13 09:25:41.000000000","message":"Done","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"346604c3992b6ead6767b236251e52626e883fb6","unresolved":false,"context_lines":[{"line_number":72,"context_line":"  ``VLAN ID``,so we have a L2 network to connect the routers."},{"line_number":73,"context_line":"* The creation of bridge network is triggered when attaching router interface"},{"line_number":74,"context_line":"  and adding router external gateway."},{"line_number":75,"context_line":"* The L2 network for VM is triggered by ``Nova-APIGW`` when a VM is to be"},{"line_number":76,"context_line":"  created in one pod, and find that there is no network there, then the"},{"line_number":77,"context_line":"  network will be created before the VM is booted, for VM booting needs"},{"line_number":78,"context_line":"  parameter network or port."}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_4482a195","line":75,"updated":"2016-04-12 22:56:40.000000000","message":"- is to be\n+ is to be being\n    or\n+ is being","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":72,"context_line":"  ``VLAN ID``,so we have a L2 network to connect the routers."},{"line_number":73,"context_line":"* The creation of bridge network is triggered when attaching router interface"},{"line_number":74,"context_line":"  and adding router external gateway."},{"line_number":75,"context_line":"* The L2 network for VM is triggered by ``Nova-APIGW`` when a VM is to be"},{"line_number":76,"context_line":"  created in one pod, and find that there is no network there, then the"},{"line_number":77,"context_line":"  network will be created before the VM is booted, for VM booting needs"},{"line_number":78,"context_line":"  parameter network or port."}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_d0a93d7d","line":75,"in_reply_to":"5a18252c_4482a195","updated":"2016-04-13 09:25:41.000000000","message":"Done","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"346604c3992b6ead6767b236251e52626e883fb6","unresolved":false,"context_lines":[{"line_number":73,"context_line":"* The creation of bridge network is triggered when attaching router interface"},{"line_number":74,"context_line":"  and adding router external gateway."},{"line_number":75,"context_line":"* The L2 network for VM is triggered by ``Nova-APIGW`` when a VM is to be"},{"line_number":76,"context_line":"  created in one pod, and find that there is no network there, then the"},{"line_number":77,"context_line":"  network will be created before the VM is booted, for VM booting needs"},{"line_number":78,"context_line":"  parameter network or port."},{"line_number":79,"context_line":"* The IP/Mac for VM is allocated in the ``Tricircle``, top layer to avoid"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_c444f175","line":76,"updated":"2016-04-12 22:56:40.000000000","message":"- find that there is no network there\n+ finds that there is no network","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":73,"context_line":"* The creation of bridge network is triggered when attaching router interface"},{"line_number":74,"context_line":"  and adding router external gateway."},{"line_number":75,"context_line":"* The L2 network for VM is triggered by ``Nova-APIGW`` when a VM is to be"},{"line_number":76,"context_line":"  created in one pod, and find that there is no network there, then the"},{"line_number":77,"context_line":"  network will be created before the VM is booted, for VM booting needs"},{"line_number":78,"context_line":"  parameter network or port."},{"line_number":79,"context_line":"* The IP/Mac for VM is allocated in the ``Tricircle``, top layer to avoid"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_70b149e1","line":76,"in_reply_to":"5a18252c_c444f175","updated":"2016-04-13 09:25:41.000000000","message":"Done","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"346604c3992b6ead6767b236251e52626e883fb6","unresolved":false,"context_lines":[{"line_number":74,"context_line":"  and adding router external gateway."},{"line_number":75,"context_line":"* The L2 network for VM is triggered by ``Nova-APIGW`` when a VM is to be"},{"line_number":76,"context_line":"  created in one pod, and find that there is no network there, then the"},{"line_number":77,"context_line":"  network will be created before the VM is booted, for VM booting needs"},{"line_number":78,"context_line":"  parameter network or port."},{"line_number":79,"context_line":"* The IP/Mac for VM is allocated in the ``Tricircle``, top layer to avoid"},{"line_number":80,"context_line":"  IP/mac collision if allocate them seperately in bottom pods."},{"line_number":81,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_242de5a7","line":78,"range":{"start_line":77,"start_character":0,"end_line":78,"end_character":28},"updated":"2016-04-12 22:56:40.000000000","message":"- for VM booting needs parameter network or port\n+ network or port parameter is required to boot VM","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":74,"context_line":"  and adding router external gateway."},{"line_number":75,"context_line":"* The L2 network for VM is triggered by ``Nova-APIGW`` when a VM is to be"},{"line_number":76,"context_line":"  created in one pod, and find that there is no network there, then the"},{"line_number":77,"context_line":"  network will be created before the VM is booted, for VM booting needs"},{"line_number":78,"context_line":"  parameter network or port."},{"line_number":79,"context_line":"* The IP/Mac for VM is allocated in the ``Tricircle``, top layer to avoid"},{"line_number":80,"context_line":"  IP/mac collision if allocate them seperately in bottom pods."},{"line_number":81,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_d5300feb","line":78,"range":{"start_line":77,"start_character":0,"end_line":78,"end_character":28},"in_reply_to":"5a18252c_242de5a7","updated":"2016-04-13 09:25:41.000000000","message":"Done","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"346604c3992b6ead6767b236251e52626e883fb6","unresolved":false,"context_lines":[{"line_number":77,"context_line":"  network will be created before the VM is booted, for VM booting needs"},{"line_number":78,"context_line":"  parameter network or port."},{"line_number":79,"context_line":"* The IP/Mac for VM is allocated in the ``Tricircle``, top layer to avoid"},{"line_number":80,"context_line":"  IP/mac collision if allocate them seperately in bottom pods."},{"line_number":81,"context_line":""},{"line_number":82,"context_line":"Pluggable L2 networking framework:"},{"line_number":83,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_bf09002f","line":80,"updated":"2016-04-12 22:56:40.000000000","message":"- IP/mac collision if allocate them seperately\n+ IP/Mac collision if they are allocated separately","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":77,"context_line":"  network will be created before the VM is booted, for VM booting needs"},{"line_number":78,"context_line":"  parameter network or port."},{"line_number":79,"context_line":"* The IP/Mac for VM is allocated in the ``Tricircle``, top layer to avoid"},{"line_number":80,"context_line":"  IP/mac collision if allocate them seperately in bottom pods."},{"line_number":81,"context_line":""},{"line_number":82,"context_line":"Pluggable L2 networking framework:"},{"line_number":83,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_b56913c1","line":80,"in_reply_to":"5a18252c_bf09002f","updated":"2016-04-13 09:25:41.000000000","message":"Done","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"df1a08f75f71fd3aa71568d8f9d5e9056bd3f59a","unresolved":false,"context_lines":[{"line_number":81,"context_line":""},{"line_number":82,"context_line":"Pluggable L2 networking framework:"},{"line_number":83,"context_line":""},{"line_number":84,"context_line":"* Because ``tricircle`` top do not use ``ml2`` mechanism, so we can use it for"},{"line_number":85,"context_line":"  L2 networking accross openstack. We need to implement different type driver."},{"line_number":86,"context_line":"* Frist, config ``tenant_network_types \u003d shared_vlan`` for ex,"},{"line_number":87,"context_line":"  ``vlan_range\u003d1-3000``."}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_20a30c51","line":84,"range":{"start_line":84,"start_character":28,"end_line":84,"end_character":30},"updated":"2016-04-13 02:22:15.000000000","message":"does","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":81,"context_line":""},{"line_number":82,"context_line":"Pluggable L2 networking framework:"},{"line_number":83,"context_line":""},{"line_number":84,"context_line":"* Because ``tricircle`` top do not use ``ml2`` mechanism, so we can use it for"},{"line_number":85,"context_line":"  L2 networking accross openstack. We need to implement different type driver."},{"line_number":86,"context_line":"* Frist, config ``tenant_network_types \u003d shared_vlan`` for ex,"},{"line_number":87,"context_line":"  ``vlan_range\u003d1-3000``."}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_55807f46","line":84,"range":{"start_line":84,"start_character":28,"end_line":84,"end_character":30},"in_reply_to":"5a18252c_20a30c51","updated":"2016-04-13 09:25:41.000000000","message":"Done","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"df1a08f75f71fd3aa71568d8f9d5e9056bd3f59a","unresolved":false,"context_lines":[{"line_number":82,"context_line":"Pluggable L2 networking framework:"},{"line_number":83,"context_line":""},{"line_number":84,"context_line":"* Because ``tricircle`` top do not use ``ml2`` mechanism, so we can use it for"},{"line_number":85,"context_line":"  L2 networking accross openstack. We need to implement different type driver."},{"line_number":86,"context_line":"* Frist, config ``tenant_network_types \u003d shared_vlan`` for ex,"},{"line_number":87,"context_line":"  ``vlan_range\u003d1-3000``."},{"line_number":88,"context_line":"* Second, when tenant create network, ``Tricircle plugin`` invoke the"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_c094d8e3","line":85,"range":{"start_line":85,"start_character":71,"end_line":85,"end_character":77},"updated":"2016-04-13 02:22:15.000000000","message":"drivers","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":82,"context_line":"Pluggable L2 networking framework:"},{"line_number":83,"context_line":""},{"line_number":84,"context_line":"* Because ``tricircle`` top do not use ``ml2`` mechanism, so we can use it for"},{"line_number":85,"context_line":"  L2 networking accross openstack. We need to implement different type driver."},{"line_number":86,"context_line":"* Frist, config ``tenant_network_types \u003d shared_vlan`` for ex,"},{"line_number":87,"context_line":"  ``vlan_range\u003d1-3000``."},{"line_number":88,"context_line":"* Second, when tenant create network, ``Tricircle plugin`` invoke the"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_95221700","line":85,"range":{"start_line":85,"start_character":71,"end_line":85,"end_character":77},"in_reply_to":"5a18252c_c094d8e3","updated":"2016-04-13 09:25:41.000000000","message":"Done","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"df1a08f75f71fd3aa71568d8f9d5e9056bd3f59a","unresolved":false,"context_lines":[{"line_number":83,"context_line":""},{"line_number":84,"context_line":"* Because ``tricircle`` top do not use ``ml2`` mechanism, so we can use it for"},{"line_number":85,"context_line":"  L2 networking accross openstack. We need to implement different type driver."},{"line_number":86,"context_line":"* Frist, config ``tenant_network_types \u003d shared_vlan`` for ex,"},{"line_number":87,"context_line":"  ``vlan_range\u003d1-3000``."},{"line_number":88,"context_line":"* Second, when tenant create network, ``Tricircle plugin`` invoke the"},{"line_number":89,"context_line":"  corresponding type driver, like ``Shared_vlan_Driver``. And driver allocates"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_20714ce1","line":86,"range":{"start_line":86,"start_character":2,"end_line":86,"end_character":15},"updated":"2016-04-13 02:22:15.000000000","message":"First, configure","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":20405,"name":"liuhaixia","email":"liuhaixia315@huawei.com","username":"liuhaixia"},"change_message_id":"1474553f664e370a1ce3cd96a66a085a13596db7","unresolved":false,"context_lines":[{"line_number":83,"context_line":""},{"line_number":84,"context_line":"* Because ``tricircle`` top do not use ``ml2`` mechanism, so we can use it for"},{"line_number":85,"context_line":"  L2 networking accross openstack. We need to implement different type driver."},{"line_number":86,"context_line":"* Frist, config ``tenant_network_types \u003d shared_vlan`` for ex,"},{"line_number":87,"context_line":"  ``vlan_range\u003d1-3000``."},{"line_number":88,"context_line":"* Second, when tenant create network, ``Tricircle plugin`` invoke the"},{"line_number":89,"context_line":"  corresponding type driver, like ``Shared_vlan_Driver``. And driver allocates"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_c64cf072","line":86,"range":{"start_line":86,"start_character":16,"end_line":86,"end_character":18},"updated":"2016-04-13 03:02:16.000000000","message":"I think \"\" is better","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"df1a08f75f71fd3aa71568d8f9d5e9056bd3f59a","unresolved":false,"context_lines":[{"line_number":83,"context_line":""},{"line_number":84,"context_line":"* Because ``tricircle`` top do not use ``ml2`` mechanism, so we can use it for"},{"line_number":85,"context_line":"  L2 networking accross openstack. We need to implement different type driver."},{"line_number":86,"context_line":"* Frist, config ``tenant_network_types \u003d shared_vlan`` for ex,"},{"line_number":87,"context_line":"  ``vlan_range\u003d1-3000``."},{"line_number":88,"context_line":"* Second, when tenant create network, ``Tricircle plugin`` invoke the"},{"line_number":89,"context_line":"  corresponding type driver, like ``Shared_vlan_Driver``. And driver allocates"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_004b7088","line":86,"range":{"start_line":86,"start_character":55,"end_line":86,"end_character":61},"updated":"2016-04-13 02:22:15.000000000","message":"do you mean \"for example\"?","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":83,"context_line":""},{"line_number":84,"context_line":"* Because ``tricircle`` top do not use ``ml2`` mechanism, so we can use it for"},{"line_number":85,"context_line":"  L2 networking accross openstack. We need to implement different type driver."},{"line_number":86,"context_line":"* Frist, config ``tenant_network_types \u003d shared_vlan`` for ex,"},{"line_number":87,"context_line":"  ``vlan_range\u003d1-3000``."},{"line_number":88,"context_line":"* Second, when tenant create network, ``Tricircle plugin`` invoke the"},{"line_number":89,"context_line":"  corresponding type driver, like ``Shared_vlan_Driver``. And driver allocates"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_b5275311","line":86,"range":{"start_line":86,"start_character":55,"end_line":86,"end_character":61},"in_reply_to":"5a18252c_004b7088","updated":"2016-04-13 09:25:41.000000000","message":"Done","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":83,"context_line":""},{"line_number":84,"context_line":"* Because ``tricircle`` top do not use ``ml2`` mechanism, so we can use it for"},{"line_number":85,"context_line":"  L2 networking accross openstack. We need to implement different type driver."},{"line_number":86,"context_line":"* Frist, config ``tenant_network_types \u003d shared_vlan`` for ex,"},{"line_number":87,"context_line":"  ``vlan_range\u003d1-3000``."},{"line_number":88,"context_line":"* Second, when tenant create network, ``Tricircle plugin`` invoke the"},{"line_number":89,"context_line":"  corresponding type driver, like ``Shared_vlan_Driver``. And driver allocates"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_750dbb8f","line":86,"range":{"start_line":86,"start_character":2,"end_line":86,"end_character":15},"in_reply_to":"5a18252c_20714ce1","updated":"2016-04-13 09:25:41.000000000","message":"Done","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":83,"context_line":""},{"line_number":84,"context_line":"* Because ``tricircle`` top do not use ``ml2`` mechanism, so we can use it for"},{"line_number":85,"context_line":"  L2 networking accross openstack. We need to implement different type driver."},{"line_number":86,"context_line":"* Frist, config ``tenant_network_types \u003d shared_vlan`` for ex,"},{"line_number":87,"context_line":"  ``vlan_range\u003d1-3000``."},{"line_number":88,"context_line":"* Second, when tenant create network, ``Tricircle plugin`` invoke the"},{"line_number":89,"context_line":"  corresponding type driver, like ``Shared_vlan_Driver``. And driver allocates"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_151607a7","line":86,"range":{"start_line":86,"start_character":16,"end_line":86,"end_character":18},"in_reply_to":"5a18252c_c64cf072","updated":"2016-04-13 09:25:41.000000000","message":"Done","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"346604c3992b6ead6767b236251e52626e883fb6","unresolved":false,"context_lines":[{"line_number":85,"context_line":"  L2 networking accross openstack. We need to implement different type driver."},{"line_number":86,"context_line":"* Frist, config ``tenant_network_types \u003d shared_vlan`` for ex,"},{"line_number":87,"context_line":"  ``vlan_range\u003d1-3000``."},{"line_number":88,"context_line":"* Second, when tenant create network, ``Tricircle plugin`` invoke the"},{"line_number":89,"context_line":"  corresponding type driver, like ``Shared_vlan_Driver``. And driver allocates"},{"line_number":90,"context_line":"  segment and assign ``network_type`` with vlan, update the info to DB."},{"line_number":91,"context_line":"* When create vm, if top needs to send create network to bottom, it send"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_3f1e9063","line":88,"updated":"2016-04-12 22:56:40.000000000","message":"- create\n+ creates\n\n- invoke\n+ invokes","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":85,"context_line":"  L2 networking accross openstack. We need to implement different type driver."},{"line_number":86,"context_line":"* Frist, config ``tenant_network_types \u003d shared_vlan`` for ex,"},{"line_number":87,"context_line":"  ``vlan_range\u003d1-3000``."},{"line_number":88,"context_line":"* Second, when tenant create network, ``Tricircle plugin`` invoke the"},{"line_number":89,"context_line":"  corresponding type driver, like ``Shared_vlan_Driver``. And driver allocates"},{"line_number":90,"context_line":"  segment and assign ``network_type`` with vlan, update the info to DB."},{"line_number":91,"context_line":"* When create vm, if top needs to send create network to bottom, it send"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_351343ba","line":88,"in_reply_to":"5a18252c_3f1e9063","updated":"2016-04-13 09:25:41.000000000","message":"Done","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"346604c3992b6ead6767b236251e52626e883fb6","unresolved":false,"context_lines":[{"line_number":87,"context_line":"  ``vlan_range\u003d1-3000``."},{"line_number":88,"context_line":"* Second, when tenant create network, ``Tricircle plugin`` invoke the"},{"line_number":89,"context_line":"  corresponding type driver, like ``Shared_vlan_Driver``. And driver allocates"},{"line_number":90,"context_line":"  segment and assign ``network_type`` with vlan, update the info to DB."},{"line_number":91,"context_line":"* When create vm, if top needs to send create network to bottom, it send"},{"line_number":92,"context_line":"  message inclueds ``network_type \u003d vlan``, ``physical_network \u003d p1``,"},{"line_number":93,"context_line":"  ``segmentation \u003d vlan 1`` to bottom."}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_7f4da871","line":90,"updated":"2016-04-12 22:56:40.000000000","message":"- assign\n+ assigns \n\n- update the info to DB\n+ updates the DB","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":87,"context_line":"  ``vlan_range\u003d1-3000``."},{"line_number":88,"context_line":"* Second, when tenant create network, ``Tricircle plugin`` invoke the"},{"line_number":89,"context_line":"  corresponding type driver, like ``Shared_vlan_Driver``. And driver allocates"},{"line_number":90,"context_line":"  segment and assign ``network_type`` with vlan, update the info to DB."},{"line_number":91,"context_line":"* When create vm, if top needs to send create network to bottom, it send"},{"line_number":92,"context_line":"  message inclueds ``network_type \u003d vlan``, ``physical_network \u003d p1``,"},{"line_number":93,"context_line":"  ``segmentation \u003d vlan 1`` to bottom."}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_953b3738","line":90,"in_reply_to":"5a18252c_7f4da871","updated":"2016-04-13 09:25:41.000000000","message":"Done","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"346604c3992b6ead6767b236251e52626e883fb6","unresolved":false,"context_lines":[{"line_number":88,"context_line":"* Second, when tenant create network, ``Tricircle plugin`` invoke the"},{"line_number":89,"context_line":"  corresponding type driver, like ``Shared_vlan_Driver``. And driver allocates"},{"line_number":90,"context_line":"  segment and assign ``network_type`` with vlan, update the info to DB."},{"line_number":91,"context_line":"* When create vm, if top needs to send create network to bottom, it send"},{"line_number":92,"context_line":"  message inclueds ``network_type \u003d vlan``, ``physical_network \u003d p1``,"},{"line_number":93,"context_line":"  ``segmentation \u003d vlan 1`` to bottom."},{"line_number":94,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_df3e7cb7","line":91,"updated":"2016-04-12 22:56:40.000000000","message":"- When create vm, if top needs to send create network, it send\n+ When VM is created, if top needs to send create network message, it sends","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":88,"context_line":"* Second, when tenant create network, ``Tricircle plugin`` invoke the"},{"line_number":89,"context_line":"  corresponding type driver, like ``Shared_vlan_Driver``. And driver allocates"},{"line_number":90,"context_line":"  segment and assign ``network_type`` with vlan, update the info to DB."},{"line_number":91,"context_line":"* When create vm, if top needs to send create network to bottom, it send"},{"line_number":92,"context_line":"  message inclueds ``network_type \u003d vlan``, ``physical_network \u003d p1``,"},{"line_number":93,"context_line":"  ``segmentation \u003d vlan 1`` to bottom."},{"line_number":94,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_55399f40","line":91,"in_reply_to":"5a18252c_df3e7cb7","updated":"2016-04-13 09:25:41.000000000","message":"Done","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"346604c3992b6ead6767b236251e52626e883fb6","unresolved":false,"context_lines":[{"line_number":89,"context_line":"  corresponding type driver, like ``Shared_vlan_Driver``. And driver allocates"},{"line_number":90,"context_line":"  segment and assign ``network_type`` with vlan, update the info to DB."},{"line_number":91,"context_line":"* When create vm, if top needs to send create network to bottom, it send"},{"line_number":92,"context_line":"  message inclueds ``network_type \u003d vlan``, ``physical_network \u003d p1``,"},{"line_number":93,"context_line":"  ``segmentation \u003d vlan 1`` to bottom."},{"line_number":94,"context_line":""},{"line_number":95,"context_line":"Data model impact"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_3f4cd06f","line":92,"updated":"2016-04-12 22:56:40.000000000","message":"- includes\n+ including","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":89,"context_line":"  corresponding type driver, like ``Shared_vlan_Driver``. And driver allocates"},{"line_number":90,"context_line":"  segment and assign ``network_type`` with vlan, update the info to DB."},{"line_number":91,"context_line":"* When create vm, if top needs to send create network to bottom, it send"},{"line_number":92,"context_line":"  message inclueds ``network_type \u003d vlan``, ``physical_network \u003d p1``,"},{"line_number":93,"context_line":"  ``segmentation \u003d vlan 1`` to bottom."},{"line_number":94,"context_line":""},{"line_number":95,"context_line":"Data model impact"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_75365b53","line":92,"in_reply_to":"5a18252c_3f4cd06f","updated":"2016-04-13 09:25:41.000000000","message":"Done","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"8167600fefc797003f84fb660476ed1945b3c4ca","unresolved":false,"context_lines":[{"line_number":90,"context_line":"  segment and assign ``network_type`` with vlan, update the info to DB."},{"line_number":91,"context_line":"* When create vm, if top needs to send create network to bottom, it send"},{"line_number":92,"context_line":"  message inclueds ``network_type \u003d vlan``, ``physical_network \u003d p1``,"},{"line_number":93,"context_line":"  ``segmentation \u003d vlan 1`` to bottom."},{"line_number":94,"context_line":""},{"line_number":95,"context_line":"Data model impact"},{"line_number":96,"context_line":"-----------------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_e3663e28","line":93,"range":{"start_line":93,"start_character":37,"end_line":93,"end_character":38},"updated":"2016-04-13 02:52:47.000000000","message":"Missing the framework for mixed VLAN/VxLAN how to update the segmentation info and passing these info to L2GW or SDN controller","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"346604c3992b6ead6767b236251e52626e883fb6","unresolved":false,"context_lines":[{"line_number":95,"context_line":"Data model impact"},{"line_number":96,"context_line":"-----------------"},{"line_number":97,"context_line":""},{"line_number":98,"context_line":"In database, we are considering setting physical_network in top OpenStack as"},{"line_number":99,"context_line":"``bottom_physical_network#bottom_pod_id`` to distinguish segmentation"},{"line_number":100,"context_line":"information in different bottom OpenStack."},{"line_number":101,"context_line":""},{"line_number":102,"context_line":"REST API impact"},{"line_number":103,"context_line":"---------------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_7f82c853","line":100,"range":{"start_line":98,"start_character":0,"end_line":100,"end_character":42},"updated":"2016-04-12 22:56:40.000000000","message":"Are we thinking of ``bottom_physical_network#bottom_pod_id`` as new configuration for physical_network setting alternatively on top OpenStack instance?","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"df1a08f75f71fd3aa71568d8f9d5e9056bd3f59a","unresolved":false,"context_lines":[{"line_number":95,"context_line":"Data model impact"},{"line_number":96,"context_line":"-----------------"},{"line_number":97,"context_line":""},{"line_number":98,"context_line":"In database, we are considering setting physical_network in top OpenStack as"},{"line_number":99,"context_line":"``bottom_physical_network#bottom_pod_id`` to distinguish segmentation"},{"line_number":100,"context_line":"information in different bottom OpenStack."},{"line_number":101,"context_line":""},{"line_number":102,"context_line":"REST API impact"},{"line_number":103,"context_line":"---------------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_c36342db","line":100,"range":{"start_line":98,"start_character":0,"end_line":100,"end_character":42},"in_reply_to":"5a18252c_7f82c853","updated":"2016-04-13 02:22:15.000000000","message":"I think this is just a way to inject \"bottom_pod_id\" into \"segments\" table. We need a place to save which segment belongs to which bottom pod since one network on top will be mapped to networks in different bottom pods, but \"segments\" table only has \"network_id\", \"network_type\", \"physical_network\", \"segmentation_id\" fields.","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"346604c3992b6ead6767b236251e52626e883fb6","unresolved":false,"context_lines":[{"line_number":138,"context_line":"Implementation"},{"line_number":139,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":140,"context_line":""},{"line_number":141,"context_line":"When admin user creates network, he/she specifies the network type as one of"},{"line_number":142,"context_line":"the network type discussed above. In the phase of creating network in top"},{"line_number":143,"context_line":"OpenStack, only one record is saved in the database, no network will be"},{"line_number":144,"context_line":"created in bottom OpenStack."}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_7fd00854","line":141,"updated":"2016-04-12 22:56:40.000000000","message":"Does he / she *need* to specify manually? Or the network type is specified automatically?","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"8167600fefc797003f84fb660476ed1945b3c4ca","unresolved":false,"context_lines":[{"line_number":138,"context_line":"Implementation"},{"line_number":139,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":140,"context_line":""},{"line_number":141,"context_line":"When admin user creates network, he/she specifies the network type as one of"},{"line_number":142,"context_line":"the network type discussed above. In the phase of creating network in top"},{"line_number":143,"context_line":"OpenStack, only one record is saved in the database, no network will be"},{"line_number":144,"context_line":"created in bottom OpenStack."}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_a3544621","line":141,"range":{"start_line":141,"start_character":16,"end_line":141,"end_character":23},"updated":"2016-04-13 02:52:47.000000000","message":"In tricircle, network could be created by tenant or admin. For tenant, no way to specifiy the network type and segment id, then default network type will be used instead.","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"df1a08f75f71fd3aa71568d8f9d5e9056bd3f59a","unresolved":false,"context_lines":[{"line_number":138,"context_line":"Implementation"},{"line_number":139,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":140,"context_line":""},{"line_number":141,"context_line":"When admin user creates network, he/she specifies the network type as one of"},{"line_number":142,"context_line":"the network type discussed above. In the phase of creating network in top"},{"line_number":143,"context_line":"OpenStack, only one record is saved in the database, no network will be"},{"line_number":144,"context_line":"created in bottom OpenStack."}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_437d726d","line":141,"in_reply_to":"5a18252c_7fd00854","updated":"2016-04-13 02:22:15.000000000","message":"Admin user can specify network type. Normal users cannot specify network type. A pre-configured network type will be used.","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":138,"context_line":"Implementation"},{"line_number":139,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":140,"context_line":""},{"line_number":141,"context_line":"When admin user creates network, he/she specifies the network type as one of"},{"line_number":142,"context_line":"the network type discussed above. In the phase of creating network in top"},{"line_number":143,"context_line":"OpenStack, only one record is saved in the database, no network will be"},{"line_number":144,"context_line":"created in bottom OpenStack."}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_f0f3999c","line":141,"range":{"start_line":141,"start_character":16,"end_line":141,"end_character":23},"in_reply_to":"5a18252c_a3544621","updated":"2016-04-13 09:25:41.000000000","message":"Done","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"346604c3992b6ead6767b236251e52626e883fb6","unresolved":false,"context_lines":[{"line_number":139,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":140,"context_line":""},{"line_number":141,"context_line":"When admin user creates network, he/she specifies the network type as one of"},{"line_number":142,"context_line":"the network type discussed above. In the phase of creating network in top"},{"line_number":143,"context_line":"OpenStack, only one record is saved in the database, no network will be"},{"line_number":144,"context_line":"created in bottom OpenStack."},{"line_number":145,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_1f8e3478","line":142,"updated":"2016-04-12 22:56:40.000000000","message":"- discussed\n+ as discussed","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":139,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":140,"context_line":""},{"line_number":141,"context_line":"When admin user creates network, he/she specifies the network type as one of"},{"line_number":142,"context_line":"the network type discussed above. In the phase of creating network in top"},{"line_number":143,"context_line":"OpenStack, only one record is saved in the database, no network will be"},{"line_number":144,"context_line":"created in bottom OpenStack."},{"line_number":145,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_b503d341","line":142,"in_reply_to":"5a18252c_1f8e3478","updated":"2016-04-13 09:25:41.000000000","message":"Done","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":143,"context_line":"OpenStack, only one record is saved in the database, no network will be"},{"line_number":144,"context_line":"created in bottom OpenStack."},{"line_number":145,"context_line":""},{"line_number":146,"context_line":"When user uses the network created by admin (how about tenant created network)"},{"line_number":147,"context_line":"to boot a VM, Nova API gateway checks the network type. For shared VLAN and"},{"line_number":148,"context_line":"shared VxLAN network, Nova API gateway directly uses the segmentation ID"},{"line_number":149,"context_line":"allocated by top Neutron to create network in bottom OpenStack. For mxied"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_4b13bc0d","line":146,"range":{"start_line":146,"start_character":0,"end_line":146,"end_character":43},"updated":"2016-04-13 09:25:41.000000000","message":"In tricircle, network could be created by tenant or admin. For tenant, no way to specifiy the network type and segment id, then default network type will be used instead. When user uses the network that created by admin.","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"346604c3992b6ead6767b236251e52626e883fb6","unresolved":false,"context_lines":[{"line_number":143,"context_line":"OpenStack, only one record is saved in the database, no network will be"},{"line_number":144,"context_line":"created in bottom OpenStack."},{"line_number":145,"context_line":""},{"line_number":146,"context_line":"When user uses the network created by admin (how about tenant created network)"},{"line_number":147,"context_line":"to boot a VM, Nova API gateway checks the network type. For shared VLAN and"},{"line_number":148,"context_line":"shared VxLAN network, Nova API gateway directly uses the segmentation ID"},{"line_number":149,"context_line":"allocated by top Neutron to create network in bottom OpenStack. For mxied"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_ff4b7829","line":146,"range":{"start_line":146,"start_character":45,"end_line":146,"end_character":77},"updated":"2016-04-12 22:56:40.000000000","message":"This sentence could confuse someone who reads this spec file.","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":143,"context_line":"OpenStack, only one record is saved in the database, no network will be"},{"line_number":144,"context_line":"created in bottom OpenStack."},{"line_number":145,"context_line":""},{"line_number":146,"context_line":"When user uses the network created by admin (how about tenant created network)"},{"line_number":147,"context_line":"to boot a VM, Nova API gateway checks the network type. For shared VLAN and"},{"line_number":148,"context_line":"shared VxLAN network, Nova API gateway directly uses the segmentation ID"},{"line_number":149,"context_line":"allocated by top Neutron to create network in bottom OpenStack. For mxied"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_55487f87","line":146,"range":{"start_line":146,"start_character":45,"end_line":146,"end_character":77},"in_reply_to":"5a18252c_ff4b7829","updated":"2016-04-13 09:25:41.000000000","message":"Done","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"346604c3992b6ead6767b236251e52626e883fb6","unresolved":false,"context_lines":[{"line_number":144,"context_line":"created in bottom OpenStack."},{"line_number":145,"context_line":""},{"line_number":146,"context_line":"When user uses the network created by admin (how about tenant created network)"},{"line_number":147,"context_line":"to boot a VM, Nova API gateway checks the network type. For shared VLAN and"},{"line_number":148,"context_line":"shared VxLAN network, Nova API gateway directly uses the segmentation ID"},{"line_number":149,"context_line":"allocated by top Neutron to create network in bottom OpenStack. For mxied"},{"line_number":150,"context_line":"VLAN/VxLAN network, Nova API gateway first creates network in bottom OpenStack"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_5f638cb1","line":147,"updated":"2016-04-12 22:56:40.000000000","message":"- Nova API gateway\n+ ``Nova-APIGW``\n\nfor consistency of description","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":144,"context_line":"created in bottom OpenStack."},{"line_number":145,"context_line":""},{"line_number":146,"context_line":"When user uses the network created by admin (how about tenant created network)"},{"line_number":147,"context_line":"to boot a VM, Nova API gateway checks the network type. For shared VLAN and"},{"line_number":148,"context_line":"shared VxLAN network, Nova API gateway directly uses the segmentation ID"},{"line_number":149,"context_line":"allocated by top Neutron to create network in bottom OpenStack. For mxied"},{"line_number":150,"context_line":"VLAN/VxLAN network, Nova API gateway first creates network in bottom OpenStack"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_1051f50e","line":147,"in_reply_to":"5a18252c_5f638cb1","updated":"2016-04-13 09:25:41.000000000","message":"Done","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"346604c3992b6ead6767b236251e52626e883fb6","unresolved":false,"context_lines":[{"line_number":145,"context_line":""},{"line_number":146,"context_line":"When user uses the network created by admin (how about tenant created network)"},{"line_number":147,"context_line":"to boot a VM, Nova API gateway checks the network type. For shared VLAN and"},{"line_number":148,"context_line":"shared VxLAN network, Nova API gateway directly uses the segmentation ID"},{"line_number":149,"context_line":"allocated by top Neutron to create network in bottom OpenStack. For mxied"},{"line_number":150,"context_line":"VLAN/VxLAN network, Nova API gateway first creates network in bottom OpenStack"},{"line_number":151,"context_line":"without specifying network type and segmentation ID, then update the top"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_df6f9c90","line":148,"updated":"2016-04-12 22:56:40.000000000","message":"- Nova API gateway\n+ ``Nova-APIGW``","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":145,"context_line":""},{"line_number":146,"context_line":"When user uses the network created by admin (how about tenant created network)"},{"line_number":147,"context_line":"to boot a VM, Nova API gateway checks the network type. For shared VLAN and"},{"line_number":148,"context_line":"shared VxLAN network, Nova API gateway directly uses the segmentation ID"},{"line_number":149,"context_line":"allocated by top Neutron to create network in bottom OpenStack. For mxied"},{"line_number":150,"context_line":"VLAN/VxLAN network, Nova API gateway first creates network in bottom OpenStack"},{"line_number":151,"context_line":"without specifying network type and segmentation ID, then update the top"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_7021499f","line":148,"range":{"start_line":148,"start_character":57,"end_line":148,"end_character":72},"updated":"2016-04-13 09:25:41.000000000","message":"segment ID","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":145,"context_line":""},{"line_number":146,"context_line":"When user uses the network created by admin (how about tenant created network)"},{"line_number":147,"context_line":"to boot a VM, Nova API gateway checks the network type. For shared VLAN and"},{"line_number":148,"context_line":"shared VxLAN network, Nova API gateway directly uses the segmentation ID"},{"line_number":149,"context_line":"allocated by top Neutron to create network in bottom OpenStack. For mxied"},{"line_number":150,"context_line":"VLAN/VxLAN network, Nova API gateway first creates network in bottom OpenStack"},{"line_number":151,"context_line":"without specifying network type and segmentation ID, then update the top"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_304eb16f","line":148,"in_reply_to":"5a18252c_df6f9c90","updated":"2016-04-13 09:25:41.000000000","message":"Done","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"346604c3992b6ead6767b236251e52626e883fb6","unresolved":false,"context_lines":[{"line_number":146,"context_line":"When user uses the network created by admin (how about tenant created network)"},{"line_number":147,"context_line":"to boot a VM, Nova API gateway checks the network type. For shared VLAN and"},{"line_number":148,"context_line":"shared VxLAN network, Nova API gateway directly uses the segmentation ID"},{"line_number":149,"context_line":"allocated by top Neutron to create network in bottom OpenStack. For mxied"},{"line_number":150,"context_line":"VLAN/VxLAN network, Nova API gateway first creates network in bottom OpenStack"},{"line_number":151,"context_line":"without specifying network type and segmentation ID, then update the top"},{"line_number":152,"context_line":"network with bottom network segmenation information returned by bottom"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_5f0a6cd3","line":149,"updated":"2016-04-12 22:56:40.000000000","message":"- top Neutron\n+ Neutron in top OpenStack","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":146,"context_line":"When user uses the network created by admin (how about tenant created network)"},{"line_number":147,"context_line":"to boot a VM, Nova API gateway checks the network type. For shared VLAN and"},{"line_number":148,"context_line":"shared VxLAN network, Nova API gateway directly uses the segmentation ID"},{"line_number":149,"context_line":"allocated by top Neutron to create network in bottom OpenStack. For mxied"},{"line_number":150,"context_line":"VLAN/VxLAN network, Nova API gateway first creates network in bottom OpenStack"},{"line_number":151,"context_line":"without specifying network type and segmentation ID, then update the top"},{"line_number":152,"context_line":"network with bottom network segmenation information returned by bottom"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_302cf101","line":149,"in_reply_to":"5a18252c_5f0a6cd3","updated":"2016-04-13 09:25:41.000000000","message":"Done","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"346604c3992b6ead6767b236251e52626e883fb6","unresolved":false,"context_lines":[{"line_number":147,"context_line":"to boot a VM, Nova API gateway checks the network type. For shared VLAN and"},{"line_number":148,"context_line":"shared VxLAN network, Nova API gateway directly uses the segmentation ID"},{"line_number":149,"context_line":"allocated by top Neutron to create network in bottom OpenStack. For mxied"},{"line_number":150,"context_line":"VLAN/VxLAN network, Nova API gateway first creates network in bottom OpenStack"},{"line_number":151,"context_line":"without specifying network type and segmentation ID, then update the top"},{"line_number":152,"context_line":"network with bottom network segmenation information returned by bottom"},{"line_number":153,"context_line":"OpenStack."}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_3f04d0be","line":150,"updated":"2016-04-12 22:56:40.000000000","message":"- Nova API gateway\n+ ``Nova-APIGW``","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":147,"context_line":"to boot a VM, Nova API gateway checks the network type. For shared VLAN and"},{"line_number":148,"context_line":"shared VxLAN network, Nova API gateway directly uses the segmentation ID"},{"line_number":149,"context_line":"allocated by top Neutron to create network in bottom OpenStack. For mxied"},{"line_number":150,"context_line":"VLAN/VxLAN network, Nova API gateway first creates network in bottom OpenStack"},{"line_number":151,"context_line":"without specifying network type and segmentation ID, then update the top"},{"line_number":152,"context_line":"network with bottom network segmenation information returned by bottom"},{"line_number":153,"context_line":"OpenStack."}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_70366953","line":150,"in_reply_to":"5a18252c_3f04d0be","updated":"2016-04-13 09:25:41.000000000","message":"Done","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"346604c3992b6ead6767b236251e52626e883fb6","unresolved":false,"context_lines":[{"line_number":148,"context_line":"shared VxLAN network, Nova API gateway directly uses the segmentation ID"},{"line_number":149,"context_line":"allocated by top Neutron to create network in bottom OpenStack. For mxied"},{"line_number":150,"context_line":"VLAN/VxLAN network, Nova API gateway first creates network in bottom OpenStack"},{"line_number":151,"context_line":"without specifying network type and segmentation ID, then update the top"},{"line_number":152,"context_line":"network with bottom network segmenation information returned by bottom"},{"line_number":153,"context_line":"OpenStack."},{"line_number":154,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_bf262066","line":151,"updated":"2016-04-12 22:56:40.000000000","message":"- update\n+ updates","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"b8c725038d714345eb331028ce727693cadfdf0b","unresolved":false,"context_lines":[{"line_number":148,"context_line":"shared VxLAN network, Nova API gateway directly uses the segmentation ID"},{"line_number":149,"context_line":"allocated by top Neutron to create network in bottom OpenStack. For mxied"},{"line_number":150,"context_line":"VLAN/VxLAN network, Nova API gateway first creates network in bottom OpenStack"},{"line_number":151,"context_line":"without specifying network type and segmentation ID, then update the top"},{"line_number":152,"context_line":"network with bottom network segmenation information returned by bottom"},{"line_number":153,"context_line":"OpenStack."},{"line_number":154,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_5039ad40","line":151,"in_reply_to":"5a18252c_bf262066","updated":"2016-04-13 09:25:41.000000000","message":"Done","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"346604c3992b6ead6767b236251e52626e883fb6","unresolved":false,"context_lines":[{"line_number":156,"context_line":"made up of multiple segments with different details, so we can associate a top"},{"line_number":157,"context_line":"network with segmentation information in different bottom OpenStack. In"},{"line_number":158,"context_line":"database, Network Segment model has the following fields: ``network_id``,"},{"line_number":159,"context_line":"``network_type``,``physical_network``,``is_dynamic`` and ``segment_index``, we are"},{"line_number":160,"context_line":"considering setting physical_network in top OpenStack as"},{"line_number":161,"context_line":"``bottom_physical_network#bottom_pod_id`` to distinguish segmentation"},{"line_number":162,"context_line":"information in different bottom OpenStack."},{"line_number":163,"context_line":""},{"line_number":164,"context_line":"Segmentation information is passed to drivers to handle different scenarios."},{"line_number":165,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a18252c_3ff210d3","line":162,"range":{"start_line":159,"start_character":76,"end_line":162,"end_character":42},"updated":"2016-04-12 22:56:40.000000000","message":"Are we thinking of ``bottom_physical_network#bottom_pod_id`` as new configuration for physical_network setting alternatively on top OpenStack instance?","commit_id":"9c8f707e98ae4bec51aa6106bd99b09da58e1ec7"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"64b50b4e94835d33ff05038c388e95ae469eb7f1","unresolved":false,"context_lines":[{"line_number":17,"context_line":"same VxLan ID.For mixed VLAN/VxLAN type,network in each bottom OpenStack may "},{"line_number":18,"context_line":"have different types or have different segmentation ID."},{"line_number":19,"context_line":""},{"line_number":20,"context_line":"To achieve cross-pod L2 networking,L2GW will be used to connect L2 network in"},{"line_number":21,"context_line":"differnt pods.No extra route is required to connect L2 network.ALL L3 traffic"},{"line_number":22,"context_line":"will be forwarded to the local L2 network,then go to the server in another pod"},{"line_number":23,"context_line":"via the L2GW."}],"source_content_type":"text/x-rst","patch_set":2,"id":"5a18252c_ae418bab","line":20,"range":{"start_line":20,"start_character":35,"end_line":20,"end_character":39},"updated":"2016-04-14 03:26:32.000000000","message":"What does L2GW mean? I can guess but I would like to know what you are intending to here.","commit_id":"7a17065e8a754b39c16f950bb8da165d94879bc2"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"04b2c53f63994cb435116893275198d8c887df7f","unresolved":false,"context_lines":[{"line_number":17,"context_line":"same VxLan ID.For mixed VLAN/VxLAN type,network in each bottom OpenStack may "},{"line_number":18,"context_line":"have different types or have different segmentation ID."},{"line_number":19,"context_line":""},{"line_number":20,"context_line":"To achieve cross-pod L2 networking,L2GW will be used to connect L2 network in"},{"line_number":21,"context_line":"differnt pods.No extra route is required to connect L2 network.ALL L3 traffic"},{"line_number":22,"context_line":"will be forwarded to the local L2 network,then go to the server in another pod"},{"line_number":23,"context_line":"via the L2GW."}],"source_content_type":"text/x-rst","patch_set":2,"id":"5a18252c_34b82ec8","line":20,"range":{"start_line":20,"start_character":35,"end_line":20,"end_character":39},"in_reply_to":"5a18252c_ae418bab","updated":"2016-04-14 05:08:54.000000000","message":"L2GW project: https://launchpad.net/networking-l2gw\nYou can refer to this patch for cross site L2 networking:\nhttps://bugs.launchpad.net/networking-l2gw/+bug/1529863\nhttps://review.openstack.org/#/c/270786/","commit_id":"7a17065e8a754b39c16f950bb8da165d94879bc2"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"85a2aaa9d93a167009a2327548c83cb291879352","unresolved":false,"context_lines":[{"line_number":13,"context_line":"\"CIDR\", we have more than one possible nexthop addresses."},{"line_number":14,"context_line":""},{"line_number":15,"context_line":"The scenarios of cross-pod L2 networking can be divided into three types,"},{"line_number":16,"context_line":"``shared VLAN``, ``shared VxLAN`` and ``mixed VLAN+VxLAN``. For shared VLAN"},{"line_number":17,"context_line":"type, network in each bottom OpenStack is VLAN type and has the same VLAN ID."},{"line_number":18,"context_line":"For shared VxLAN type, network in each bottom OpenStack is VxLAN type and has"},{"line_number":19,"context_line":"the same VxLAN ID. For mixed VLAN+VxLAN type, network in each bottom OpenStack"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1a122d0e_3eab3776","line":16,"range":{"start_line":16,"start_character":40,"end_line":16,"end_character":45},"updated":"2016-04-18 03:06:03.000000000","message":"Need further classification for driver to use L2GW or use SDN controller to control the L2 networking","commit_id":"a97da41f8ac8777aee96a1a8a2f228928c507c6a"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"c92173a346666adba9ab37f4dea51bca3472270b","unresolved":false,"context_lines":[{"line_number":13,"context_line":"\"CIDR\", we have more than one possible nexthop addresses."},{"line_number":14,"context_line":""},{"line_number":15,"context_line":"The scenarios of cross-pod L2 networking can be divided into three types,"},{"line_number":16,"context_line":"``shared VLAN``, ``shared VxLAN`` and ``mixed VLAN+VxLAN``. For shared VLAN"},{"line_number":17,"context_line":"type, network in each bottom OpenStack is VLAN type and has the same VLAN ID."},{"line_number":18,"context_line":"For shared VxLAN type, network in each bottom OpenStack is VxLAN type and has"},{"line_number":19,"context_line":"the same VxLAN ID. For mixed VLAN+VxLAN type, network in each bottom OpenStack"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1a122d0e_cf753ccd","line":16,"range":{"start_line":16,"start_character":40,"end_line":16,"end_character":45},"in_reply_to":"1a122d0e_3eab3776","updated":"2016-05-03 02:52:45.000000000","message":"After discussion with L2GW, no need to use SDN controller for multi-segment L2 networking. That means using L2GW should work for all mixed VLAN+VxLAN scenario. When L2GW connected with local network in the same OpenStack instance, no matter it\u0027s VLAN or VxLAN or GRE, the L2GW should be able to connect the local network, and because L2GW is extention of Neutron, so only network UUID should be enough for L2GW to connect the local network.","commit_id":"a97da41f8ac8777aee96a1a8a2f228928c507c6a"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"85a2aaa9d93a167009a2327548c83cb291879352","unresolved":false,"context_lines":[{"line_number":19,"context_line":"the same VxLAN ID. For mixed VLAN+VxLAN type, network in each bottom OpenStack"},{"line_number":20,"context_line":"may have different types or have different segment IDs."},{"line_number":21,"context_line":""},{"line_number":22,"context_line":"To achieve cross-pod L2 networking, L2GW will be used to connect L2 network in"},{"line_number":23,"context_line":"differnt pods. No extra route is required to connect L2 network. ALL L3 traffic"},{"line_number":24,"context_line":"will be forwarded to the local L2 network, then go to the server in another pod"},{"line_number":25,"context_line":"via the L2GW."}],"source_content_type":"text/x-rst","patch_set":3,"id":"1a122d0e_9ea1abac","line":22,"range":{"start_line":22,"start_character":48,"end_line":22,"end_character":49},"updated":"2016-04-18 03:06:03.000000000","message":"L2-GW is not used for all scenario, only for VxLAN. Shared VLAN and multi-segment VLAN no need to use L2GW. This is implementation, should not be listed in problem section","commit_id":"a97da41f8ac8777aee96a1a8a2f228928c507c6a"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"c92173a346666adba9ab37f4dea51bca3472270b","unresolved":false,"context_lines":[{"line_number":19,"context_line":"the same VxLAN ID. For mixed VLAN+VxLAN type, network in each bottom OpenStack"},{"line_number":20,"context_line":"may have different types or have different segment IDs."},{"line_number":21,"context_line":""},{"line_number":22,"context_line":"To achieve cross-pod L2 networking, L2GW will be used to connect L2 network in"},{"line_number":23,"context_line":"differnt pods. No extra route is required to connect L2 network. ALL L3 traffic"},{"line_number":24,"context_line":"will be forwarded to the local L2 network, then go to the server in another pod"},{"line_number":25,"context_line":"via the L2GW."}],"source_content_type":"text/x-rst","patch_set":3,"id":"1a122d0e_ca752acd","line":22,"range":{"start_line":22,"start_character":48,"end_line":22,"end_character":49},"in_reply_to":"1a122d0e_9ea1abac","updated":"2016-05-03 02:52:45.000000000","message":"In problem section, we need to focus on the description of that no L2 networking across OpenStack instances in one AZ or cross AZ","commit_id":"a97da41f8ac8777aee96a1a8a2f228928c507c6a"},{"author":{"_account_id":21033,"name":"XiongQiu Long","email":"longxiongqiu123@163.com","username":"XiongQiu"},"change_message_id":"94e2454dba742929d744d840ea87b321cbb87c61","unresolved":false,"context_lines":[{"line_number":19,"context_line":"the same VxLAN ID. For mixed VLAN+VxLAN type, network in each bottom OpenStack"},{"line_number":20,"context_line":"may have different types or have different segment IDs."},{"line_number":21,"context_line":""},{"line_number":22,"context_line":"To achieve cross-pod L2 networking, L2GW will be used to connect L2 network in"},{"line_number":23,"context_line":"differnt pods. No extra route is required to connect L2 network. ALL L3 traffic"},{"line_number":24,"context_line":"will be forwarded to the local L2 network, then go to the server in another pod"},{"line_number":25,"context_line":"via the L2GW."}],"source_content_type":"text/x-rst","patch_set":3,"id":"1a122d0e_ea72a610","line":22,"range":{"start_line":22,"start_character":48,"end_line":22,"end_character":49},"in_reply_to":"1a122d0e_9ea1abac","updated":"2016-05-03 02:32:26.000000000","message":"L2GW support shared VxLAN and multi-segment VxLAN and VxLAN+VLAN,is it right?","commit_id":"a97da41f8ac8777aee96a1a8a2f228928c507c6a"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"88f405e60aba00a69c2e6e19e56dd2e1bfde00e1","unresolved":false,"context_lines":[{"line_number":20,"context_line":"may have different types or have different segment IDs."},{"line_number":21,"context_line":""},{"line_number":22,"context_line":"To achieve cross-pod L2 networking, L2GW will be used to connect L2 network in"},{"line_number":23,"context_line":"differnt pods. No extra route is required to connect L2 network. ALL L3 traffic"},{"line_number":24,"context_line":"will be forwarded to the local L2 network, then go to the server in another pod"},{"line_number":25,"context_line":"via the L2GW."},{"line_number":26,"context_line":""},{"line_number":27,"context_line":"Use Cases"},{"line_number":28,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1a122d0e_92951fe6","line":25,"range":{"start_line":23,"start_character":0,"end_line":25,"end_character":13},"updated":"2016-04-18 03:51:55.000000000","message":"+ Communication between each POD will be established via VxLAN gateway.\n\n\nWe don\u0027t need to mention about any L3 networking here, if this section is about L2GW, I think.\n\nIn fact there are some scenarios regarding to VxLAN over L3 networking though.\n\nWhat do you think?","commit_id":"a97da41f8ac8777aee96a1a8a2f228928c507c6a"},{"author":{"_account_id":21033,"name":"XiongQiu Long","email":"longxiongqiu123@163.com","username":"XiongQiu"},"change_message_id":"94e2454dba742929d744d840ea87b321cbb87c61","unresolved":false,"context_lines":[{"line_number":20,"context_line":"may have different types or have different segment IDs."},{"line_number":21,"context_line":""},{"line_number":22,"context_line":"To achieve cross-pod L2 networking, L2GW will be used to connect L2 network in"},{"line_number":23,"context_line":"differnt pods. No extra route is required to connect L2 network. ALL L3 traffic"},{"line_number":24,"context_line":"will be forwarded to the local L2 network, then go to the server in another pod"},{"line_number":25,"context_line":"via the L2GW."},{"line_number":26,"context_line":""},{"line_number":27,"context_line":"Use Cases"},{"line_number":28,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1a122d0e_4a5e3a7a","line":25,"range":{"start_line":23,"start_character":0,"end_line":25,"end_character":13},"in_reply_to":"1a122d0e_92951fe6","updated":"2016-05-03 02:32:26.000000000","message":"Yes,I agree with you.","commit_id":"a97da41f8ac8777aee96a1a8a2f228928c507c6a"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"c92173a346666adba9ab37f4dea51bca3472270b","unresolved":false,"context_lines":[{"line_number":27,"context_line":"Use Cases"},{"line_number":28,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":29,"context_line":""},{"line_number":30,"context_line":"**Use case for shared VLAN:**"},{"line_number":31,"context_line":""},{"line_number":32,"context_line":"A user creates network Net1, plugin check the configuration, if"},{"line_number":33,"context_line":"``tenant_network_type`` equals shared_vlan, it will invoke shared VLAN dirver."}],"source_content_type":"text/x-rst","patch_set":3,"id":"1a122d0e_4a48fa8a","line":30,"range":{"start_line":30,"start_character":5,"end_line":30,"end_character":6},"updated":"2016-05-03 02:52:45.000000000","message":"In use case section, mainly focus on the description of why L2 networking across OpenStack instances is needed in different scenario, for example, 7.4.0 in https://docs.google.com/document/d/18kZZ1snMOCD9IQvUKI5NVDzSASpw-QKj7l2zNqMEd3g/edit#heading\u003dh.hd947yodrdmh give the L2 networking use cases","commit_id":"a97da41f8ac8777aee96a1a8a2f228928c507c6a"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"85a2aaa9d93a167009a2327548c83cb291879352","unresolved":false,"context_lines":[{"line_number":38,"context_line":"booted in POD1, tricircle will send create network message to POD1. Create"},{"line_number":39,"context_line":"network message includes ``network_type`` and ``segment``."},{"line_number":40,"context_line":""},{"line_number":41,"context_line":"Then the user creates VM2 in AZ2, and connects it to network Net1. If VM will"},{"line_number":42,"context_line":"be booted in POD2, ``tricircle`` (``Nova-APIGW`` needs to get the network"},{"line_number":43,"context_line":"information) will send create network message to POD2. Create network message"},{"line_number":44,"context_line":"includes ``network_type`` and ``segment`` and ``physical_network``."}],"source_content_type":"text/x-rst","patch_set":3,"id":"1a122d0e_3ea8571f","line":41,"range":{"start_line":41,"start_character":9,"end_line":41,"end_character":13},"updated":"2016-04-18 03:06:03.000000000","message":"Use case is use case, implementation is implementation, please describe with correct logical description","commit_id":"a97da41f8ac8777aee96a1a8a2f228928c507c6a"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"85a2aaa9d93a167009a2327548c83cb291879352","unresolved":false,"context_lines":[{"line_number":43,"context_line":"information) will send create network message to POD2. Create network message"},{"line_number":44,"context_line":"includes ``network_type`` and ``segment`` and ``physical_network``."},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"**Use case for different VLAN:**"},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"A user creates network Net1, plugin check the configuration, if"},{"line_number":49,"context_line":"``tenant_network_type`` equals multi_vlan, it will invoke multi VLAN driver."}],"source_content_type":"text/x-rst","patch_set":3,"id":"1a122d0e_de9fa301","line":46,"range":{"start_line":46,"start_character":29,"end_line":46,"end_character":32},"updated":"2016-04-18 03:06:03.000000000","message":"Why only use cases of shared VLAN and different VLAN? There are many use cases or scenario when in discussion","commit_id":"a97da41f8ac8777aee96a1a8a2f228928c507c6a"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"c92173a346666adba9ab37f4dea51bca3472270b","unresolved":false,"context_lines":[{"line_number":43,"context_line":"information) will send create network message to POD2. Create network message"},{"line_number":44,"context_line":"includes ``network_type`` and ``segment`` and ``physical_network``."},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"**Use case for different VLAN:**"},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"A user creates network Net1, plugin check the configuration, if"},{"line_number":49,"context_line":"``tenant_network_type`` equals multi_vlan, it will invoke multi VLAN driver."}],"source_content_type":"text/x-rst","patch_set":3,"id":"1a122d0e_8507a517","line":46,"range":{"start_line":46,"start_character":29,"end_line":46,"end_character":32},"in_reply_to":"1a122d0e_de9fa301","updated":"2016-05-03 02:52:45.000000000","message":"See above comment for use cases description","commit_id":"a97da41f8ac8777aee96a1a8a2f228928c507c6a"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"85a2aaa9d93a167009a2327548c83cb291879352","unresolved":false,"context_lines":[{"line_number":70,"context_line":"Proposed change"},{"line_number":71,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":72,"context_line":""},{"line_number":73,"context_line":"Difference between each L2 networking for tenant\u0027s VM and for L3 bridging"},{"line_number":74,"context_line":"network:"},{"line_number":75,"context_line":""},{"line_number":76,"context_line":"* A special bridge network is created and connected to the routers in different"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1a122d0e_be72a7e3","line":73,"range":{"start_line":73,"start_character":18,"end_line":73,"end_character":19},"updated":"2016-04-18 03:06:03.000000000","message":"proposed change is to describe what should be changed in the source code","commit_id":"a97da41f8ac8777aee96a1a8a2f228928c507c6a"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"85a2aaa9d93a167009a2327548c83cb291879352","unresolved":false,"context_lines":[{"line_number":71,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":72,"context_line":""},{"line_number":73,"context_line":"Difference between each L2 networking for tenant\u0027s VM and for L3 bridging"},{"line_number":74,"context_line":"network:"},{"line_number":75,"context_line":""},{"line_number":76,"context_line":"* A special bridge network is created and connected to the routers in different"},{"line_number":77,"context_line":"  bottom OpenStack. We configure the extra routes of the routers to route the"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1a122d0e_9e188b86","line":74,"range":{"start_line":74,"start_character":7,"end_line":74,"end_character":8},"updated":"2016-04-18 03:06:03.000000000","message":"need to describe what\u0027s the change in L3 bridging network operation for L3 networking","commit_id":"a97da41f8ac8777aee96a1a8a2f228928c507c6a"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"85a2aaa9d93a167009a2327548c83cb291879352","unresolved":false,"context_lines":[{"line_number":166,"context_line":"made up of multiple segments with different details, so we can associate a top"},{"line_number":167,"context_line":"network with segmentation information in different bottom OpenStack. In"},{"line_number":168,"context_line":"database, Network Segment model has the following fields: ``network_id``,"},{"line_number":169,"context_line":"``network_type``, ``physical_network``, ``is_dynamic`` and ``segment_index``,"},{"line_number":170,"context_line":"we are considering setting physical_network in top OpenStack as"},{"line_number":171,"context_line":"``bottom_physical_network#bottom_pod_id`` to distinguish segmentation"},{"line_number":172,"context_line":"information in different bottom OpenStack."}],"source_content_type":"text/x-rst","patch_set":3,"id":"1a122d0e_521b871b","line":169,"range":{"start_line":169,"start_character":41,"end_line":169,"end_character":56},"updated":"2016-04-18 03:06:03.000000000","message":"no this field","commit_id":"a97da41f8ac8777aee96a1a8a2f228928c507c6a"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"85a2aaa9d93a167009a2327548c83cb291879352","unresolved":false,"context_lines":[{"line_number":166,"context_line":"made up of multiple segments with different details, so we can associate a top"},{"line_number":167,"context_line":"network with segmentation information in different bottom OpenStack. In"},{"line_number":168,"context_line":"database, Network Segment model has the following fields: ``network_id``,"},{"line_number":169,"context_line":"``network_type``, ``physical_network``, ``is_dynamic`` and ``segment_index``,"},{"line_number":170,"context_line":"we are considering setting physical_network in top OpenStack as"},{"line_number":171,"context_line":"``bottom_physical_network#bottom_pod_id`` to distinguish segmentation"},{"line_number":172,"context_line":"information in different bottom OpenStack."}],"source_content_type":"text/x-rst","patch_set":3,"id":"1a122d0e_f2e4530e","line":169,"range":{"start_line":169,"start_character":61,"end_line":169,"end_character":74},"updated":"2016-04-18 03:06:03.000000000","message":"provider:segmentation_id. Need to align with OpenStack API","commit_id":"a97da41f8ac8777aee96a1a8a2f228928c507c6a"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"85a2aaa9d93a167009a2327548c83cb291879352","unresolved":false,"context_lines":[{"line_number":173,"context_line":""},{"line_number":174,"context_line":"Segmentation information is passed to drivers to handle different scenarios."},{"line_number":175,"context_line":""},{"line_number":176,"context_line":".. _`Neutron multi-segment network API`: https://blueprints.launchpad.net/neutron/+spec/ml2-multi-segment-api"},{"line_number":177,"context_line":""},{"line_number":178,"context_line":"Assignee(s)"},{"line_number":179,"context_line":"-----------"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1a122d0e_12cf4f80","line":176,"range":{"start_line":176,"start_character":2,"end_line":176,"end_character":3},"updated":"2016-04-18 03:06:03.000000000","message":"Driver interface and how driver will work is not described here.","commit_id":"a97da41f8ac8777aee96a1a8a2f228928c507c6a"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"c92173a346666adba9ab37f4dea51bca3472270b","unresolved":false,"context_lines":[{"line_number":185,"context_line":""},{"line_number":186,"context_line":""},{"line_number":187,"context_line":"Work Items"},{"line_number":188,"context_line":"----------"},{"line_number":189,"context_line":""},{"line_number":190,"context_line":""},{"line_number":191,"context_line":"Dependencies"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1a122d0e_454bcd5f","line":188,"range":{"start_line":188,"start_character":0,"end_line":188,"end_character":10},"updated":"2016-05-03 02:52:45.000000000","message":"break down the spec into several patches","commit_id":"a97da41f8ac8777aee96a1a8a2f228928c507c6a"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"8ff8ab3b4a44b840da076e164ba4baf8c1e0e14d","unresolved":false,"context_lines":[{"line_number":1,"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"},{"line_number":2,"context_line":" Tricircle cross pod L2 networking"},{"line_number":3,"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"},{"line_number":4,"context_line":""},{"line_number":5,"context_line":"Problem description"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a122d0e_3d8f6f24","line":2,"range":{"start_line":2,"start_character":1,"end_line":2,"end_character":10},"updated":"2016-05-04 22:29:56.000000000","message":"-Tricircle\n+The Tricircle","commit_id":"61a6b9f6018f12118330293c427d40cad1153b57"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"8ff8ab3b4a44b840da076e164ba4baf8c1e0e14d","unresolved":false,"context_lines":[{"line_number":2,"context_line":" Tricircle cross pod L2 networking"},{"line_number":3,"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"},{"line_number":4,"context_line":""},{"line_number":5,"context_line":"Problem description"},{"line_number":6,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":7,"context_line":""},{"line_number":8,"context_line":"Usually a tenant\u0027s network will be presented in one bottom OpenStack, that"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a122d0e_1d6393b2","line":5,"range":{"start_line":5,"start_character":8,"end_line":5,"end_character":19},"updated":"2016-05-04 22:29:56.000000000","message":"-description\n+Description","commit_id":"61a6b9f6018f12118330293c427d40cad1153b57"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"8ff8ab3b4a44b840da076e164ba4baf8c1e0e14d","unresolved":false,"context_lines":[{"line_number":8,"context_line":"Usually a tenant\u0027s network will be presented in one bottom OpenStack, that"},{"line_number":9,"context_line":"means all VMs connected to the network will be located inside one bottom"},{"line_number":10,"context_line":"OpenStack. As one tenant adds more and more VMs, these VMs are connected to"},{"line_number":11,"context_line":"one network may be spread into multiple bottom OpenStack instances, then cross"},{"line_number":12,"context_line":"pod L2 networking is needed."},{"line_number":13,"context_line":""},{"line_number":14,"context_line":"Use Cases"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a122d0e_fdedf7f0","line":11,"range":{"start_line":11,"start_character":40,"end_line":11,"end_character":67},"updated":"2016-05-04 22:29:56.000000000","message":"-bottom OpenStack instances,\n+bottom OpenStack instances.","commit_id":"61a6b9f6018f12118330293c427d40cad1153b57"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"8ff8ab3b4a44b840da076e164ba4baf8c1e0e14d","unresolved":false,"context_lines":[{"line_number":8,"context_line":"Usually a tenant\u0027s network will be presented in one bottom OpenStack, that"},{"line_number":9,"context_line":"means all VMs connected to the network will be located inside one bottom"},{"line_number":10,"context_line":"OpenStack. As one tenant adds more and more VMs, these VMs are connected to"},{"line_number":11,"context_line":"one network may be spread into multiple bottom OpenStack instances, then cross"},{"line_number":12,"context_line":"pod L2 networking is needed."},{"line_number":13,"context_line":""},{"line_number":14,"context_line":"Use Cases"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a122d0e_1dbf13d1","line":11,"range":{"start_line":11,"start_character":68,"end_line":11,"end_character":72},"updated":"2016-05-04 22:29:56.000000000","message":"-then\n+Because of this,","commit_id":"61a6b9f6018f12118330293c427d40cad1153b57"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"8ff8ab3b4a44b840da076e164ba4baf8c1e0e14d","unresolved":false,"context_lines":[{"line_number":7,"context_line":""},{"line_number":8,"context_line":"Usually a tenant\u0027s network will be presented in one bottom OpenStack, that"},{"line_number":9,"context_line":"means all VMs connected to the network will be located inside one bottom"},{"line_number":10,"context_line":"OpenStack. As one tenant adds more and more VMs, these VMs are connected to"},{"line_number":11,"context_line":"one network may be spread into multiple bottom OpenStack instances, then cross"},{"line_number":12,"context_line":"pod L2 networking is needed."},{"line_number":13,"context_line":""},{"line_number":14,"context_line":"Use Cases"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a122d0e_fd1697f0","line":11,"range":{"start_line":10,"start_character":49,"end_line":11,"end_character":11},"updated":"2016-05-04 22:29:56.000000000","message":"-these VMs are connected to one network\n+these VMs connected to one network","commit_id":"61a6b9f6018f12118330293c427d40cad1153b57"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"8ff8ab3b4a44b840da076e164ba4baf8c1e0e14d","unresolved":false,"context_lines":[{"line_number":14,"context_line":"Use Cases"},{"line_number":15,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":16,"context_line":""},{"line_number":17,"context_line":"* Capacity expansion: as tenants add more and more VMs, the capacity of one"},{"line_number":18,"context_line":"  OpenStack may be not enough, then new OpenStack instance has to be added"},{"line_number":19,"context_line":"  to the cloud. The tenants still want to add VMs on the existing network,"},{"line_number":20,"context_line":"  and don\u0027t want to add new network/router/FW/Security Group configuration."}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a122d0e_bd953f41","line":17,"range":{"start_line":17,"start_character":33,"end_line":17,"end_character":54},"updated":"2016-05-04 22:29:56.000000000","message":"-add more and more VMs\n+add VMs more and more","commit_id":"61a6b9f6018f12118330293c427d40cad1153b57"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"8ff8ab3b4a44b840da076e164ba4baf8c1e0e14d","unresolved":false,"context_lines":[{"line_number":17,"context_line":"* Capacity expansion: as tenants add more and more VMs, the capacity of one"},{"line_number":18,"context_line":"  OpenStack may be not enough, then new OpenStack instance has to be added"},{"line_number":19,"context_line":"  to the cloud. The tenants still want to add VMs on the existing network,"},{"line_number":20,"context_line":"  and don\u0027t want to add new network/router/FW/Security Group configuration."},{"line_number":21,"context_line":"* Cross OpenStack network service chaining. Service chaining is based on"},{"line_number":22,"context_line":"  the port-pairs. Leveraging the cross pod L2 networking capability which "},{"line_number":23,"context_line":"  provided by Tricircle, the service could also be done across sites. "}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a122d0e_9d796332","line":20,"range":{"start_line":20,"start_character":24,"end_line":20,"end_character":27},"updated":"2016-05-04 22:29:56.000000000","message":"-new\n+any new","commit_id":"61a6b9f6018f12118330293c427d40cad1153b57"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"8ff8ab3b4a44b840da076e164ba4baf8c1e0e14d","unresolved":false,"context_lines":[{"line_number":20,"context_line":"  and don\u0027t want to add new network/router/FW/Security Group configuration."},{"line_number":21,"context_line":"* Cross OpenStack network service chaining. Service chaining is based on"},{"line_number":22,"context_line":"  the port-pairs. Leveraging the cross pod L2 networking capability which "},{"line_number":23,"context_line":"  provided by Tricircle, the service could also be done across sites. "},{"line_number":24,"context_line":"  For example, vRouter1 in site1, but vRouter2 in site2, these two VMs "},{"line_number":25,"context_line":"  could be chained."},{"line_number":26,"context_line":"* In hybrid cloud, there is cross L2 networking requirement between the"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a122d0e_7d956730","line":23,"range":{"start_line":23,"start_character":14,"end_line":23,"end_character":23},"updated":"2016-05-04 22:29:56.000000000","message":"-Tricircle\n+the Tricircle","commit_id":"61a6b9f6018f12118330293c427d40cad1153b57"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"8ff8ab3b4a44b840da076e164ba4baf8c1e0e14d","unresolved":false,"context_lines":[{"line_number":20,"context_line":"  and don\u0027t want to add new network/router/FW/Security Group configuration."},{"line_number":21,"context_line":"* Cross OpenStack network service chaining. Service chaining is based on"},{"line_number":22,"context_line":"  the port-pairs. Leveraging the cross pod L2 networking capability which "},{"line_number":23,"context_line":"  provided by Tricircle, the service could also be done across sites. "},{"line_number":24,"context_line":"  For example, vRouter1 in site1, but vRouter2 in site2, these two VMs "},{"line_number":25,"context_line":"  could be chained."},{"line_number":26,"context_line":"* In hybrid cloud, there is cross L2 networking requirement between the"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a122d0e_5dffcb65","line":23,"range":{"start_line":23,"start_character":25,"end_line":23,"end_character":68},"updated":"2016-05-04 22:29:56.000000000","message":"-the service could also be done across sites\n+the service could also be done by across sites\n\nMore consideration and elaboration are required.\nThis sentence is not correct grammatically speaking.\n\nEven this, ``the service could also be done by across sites``, description sounds strange.","commit_id":"61a6b9f6018f12118330293c427d40cad1153b57"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"8ff8ab3b4a44b840da076e164ba4baf8c1e0e14d","unresolved":false,"context_lines":[{"line_number":21,"context_line":"* Cross OpenStack network service chaining. Service chaining is based on"},{"line_number":22,"context_line":"  the port-pairs. Leveraging the cross pod L2 networking capability which "},{"line_number":23,"context_line":"  provided by Tricircle, the service could also be done across sites. "},{"line_number":24,"context_line":"  For example, vRouter1 in site1, but vRouter2 in site2, these two VMs "},{"line_number":25,"context_line":"  could be chained."},{"line_number":26,"context_line":"* In hybrid cloud, there is cross L2 networking requirement between the"},{"line_number":27,"context_line":"  private OpenStack and the public OpenStack like AWS. Cross pod L2 "}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a122d0e_dd42bbaa","line":24,"range":{"start_line":24,"start_character":15,"end_line":24,"end_character":55},"updated":"2016-05-04 22:29:56.000000000","message":"It would be better to describe definition of vRouter, or add any kind of pointer.","commit_id":"61a6b9f6018f12118330293c427d40cad1153b57"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"8ff8ab3b4a44b840da076e164ba4baf8c1e0e14d","unresolved":false,"context_lines":[{"line_number":23,"context_line":"  provided by Tricircle, the service could also be done across sites. "},{"line_number":24,"context_line":"  For example, vRouter1 in site1, but vRouter2 in site2, these two VMs "},{"line_number":25,"context_line":"  could be chained."},{"line_number":26,"context_line":"* In hybrid cloud, there is cross L2 networking requirement between the"},{"line_number":27,"context_line":"  private OpenStack and the public OpenStack like AWS. Cross pod L2 "},{"line_number":28,"context_line":"  networking will help the VMs migration for this case, it don\u0027t need to "},{"line_number":29,"context_line":"  change the IP/MAC/Security group configuration."}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a122d0e_7d08c780","line":26,"range":{"start_line":26,"start_character":5,"end_line":26,"end_character":17},"updated":"2016-05-04 22:29:56.000000000","message":"How do we define ``hybrid cloud``?","commit_id":"61a6b9f6018f12118330293c427d40cad1153b57"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"8ff8ab3b4a44b840da076e164ba4baf8c1e0e14d","unresolved":false,"context_lines":[{"line_number":25,"context_line":"  could be chained."},{"line_number":26,"context_line":"* In hybrid cloud, there is cross L2 networking requirement between the"},{"line_number":27,"context_line":"  private OpenStack and the public OpenStack like AWS. Cross pod L2 "},{"line_number":28,"context_line":"  networking will help the VMs migration for this case, it don\u0027t need to "},{"line_number":29,"context_line":"  change the IP/MAC/Security group configuration."},{"line_number":30,"context_line":""},{"line_number":31,"context_line":"Proposed change"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a122d0e_3d792ffd","line":28,"range":{"start_line":28,"start_character":59,"end_line":28,"end_character":64},"updated":"2016-05-04 22:29:56.000000000","message":"-don\u0027t\n+doesn\u0027t","commit_id":"61a6b9f6018f12118330293c427d40cad1153b57"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"8ff8ab3b4a44b840da076e164ba4baf8c1e0e14d","unresolved":false,"context_lines":[{"line_number":26,"context_line":"* In hybrid cloud, there is cross L2 networking requirement between the"},{"line_number":27,"context_line":"  private OpenStack and the public OpenStack like AWS. Cross pod L2 "},{"line_number":28,"context_line":"  networking will help the VMs migration for this case, it don\u0027t need to "},{"line_number":29,"context_line":"  change the IP/MAC/Security group configuration."},{"line_number":30,"context_line":""},{"line_number":31,"context_line":"Proposed change"},{"line_number":32,"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":4,"id":"1a122d0e_5d5b4b86","line":29,"range":{"start_line":29,"start_character":29,"end_line":29,"end_character":34},"updated":"2016-05-04 22:29:56.000000000","message":"-group\n+Group","commit_id":"61a6b9f6018f12118330293c427d40cad1153b57"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"8ff8ab3b4a44b840da076e164ba4baf8c1e0e14d","unresolved":false,"context_lines":[{"line_number":28,"context_line":"  networking will help the VMs migration for this case, it don\u0027t need to "},{"line_number":29,"context_line":"  change the IP/MAC/Security group configuration."},{"line_number":30,"context_line":""},{"line_number":31,"context_line":"Proposed change"},{"line_number":32,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":33,"context_line":""},{"line_number":34,"context_line":"Difference between each L2 networking for tenant\u0027s VM and for L3 bridging"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a122d0e_bdcedf80","line":31,"range":{"start_line":31,"start_character":9,"end_line":31,"end_character":15},"updated":"2016-05-04 22:29:56.000000000","message":"-change\n+Change","commit_id":"61a6b9f6018f12118330293c427d40cad1153b57"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"8ff8ab3b4a44b840da076e164ba4baf8c1e0e14d","unresolved":false,"context_lines":[{"line_number":35,"context_line":"network:"},{"line_number":36,"context_line":""},{"line_number":37,"context_line":"* A special bridge network is created and connected to the routers in different"},{"line_number":38,"context_line":"  bottom OpenStack. We configure the extra routes of the routers to route the"},{"line_number":39,"context_line":"  packets from one OpenStack to another. In current implementation, we create"},{"line_number":40,"context_line":"  this special bridge network in each bottom OpenStack with the same"},{"line_number":41,"context_line":"  ``VLAN ID``, so we have an L2 network to connect the routers."}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a122d0e_9dffa333","line":38,"range":{"start_line":38,"start_character":9,"end_line":38,"end_character":18},"updated":"2016-05-04 22:29:56.000000000","message":"-OpenStack\n+OpenStack instances","commit_id":"61a6b9f6018f12118330293c427d40cad1153b57"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"8ff8ab3b4a44b840da076e164ba4baf8c1e0e14d","unresolved":false,"context_lines":[{"line_number":35,"context_line":"network:"},{"line_number":36,"context_line":""},{"line_number":37,"context_line":"* A special bridge network is created and connected to the routers in different"},{"line_number":38,"context_line":"  bottom OpenStack. We configure the extra routes of the routers to route the"},{"line_number":39,"context_line":"  packets from one OpenStack to another. In current implementation, we create"},{"line_number":40,"context_line":"  this special bridge network in each bottom OpenStack with the same"},{"line_number":41,"context_line":"  ``VLAN ID``, so we have an L2 network to connect the routers."}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a122d0e_9d74c3cf","line":38,"range":{"start_line":38,"start_character":50,"end_line":38,"end_character":64},"updated":"2016-05-04 22:29:56.000000000","message":"-of the routers\n+for the each router","commit_id":"61a6b9f6018f12118330293c427d40cad1153b57"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"8ff8ab3b4a44b840da076e164ba4baf8c1e0e14d","unresolved":false,"context_lines":[{"line_number":36,"context_line":""},{"line_number":37,"context_line":"* A special bridge network is created and connected to the routers in different"},{"line_number":38,"context_line":"  bottom OpenStack. We configure the extra routes of the routers to route the"},{"line_number":39,"context_line":"  packets from one OpenStack to another. In current implementation, we create"},{"line_number":40,"context_line":"  this special bridge network in each bottom OpenStack with the same"},{"line_number":41,"context_line":"  ``VLAN ID``, so we have an L2 network to connect the routers."},{"line_number":42,"context_line":"* The creation of bridge network is triggered during attaching router interface"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a122d0e_1d36f302","line":39,"range":{"start_line":39,"start_character":19,"end_line":39,"end_character":28},"updated":"2016-05-04 22:29:56.000000000","message":"-OpenStack\n+OpenStack instance","commit_id":"61a6b9f6018f12118330293c427d40cad1153b57"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"8ff8ab3b4a44b840da076e164ba4baf8c1e0e14d","unresolved":false,"context_lines":[{"line_number":37,"context_line":"* A special bridge network is created and connected to the routers in different"},{"line_number":38,"context_line":"  bottom OpenStack. We configure the extra routes of the routers to route the"},{"line_number":39,"context_line":"  packets from one OpenStack to another. In current implementation, we create"},{"line_number":40,"context_line":"  this special bridge network in each bottom OpenStack with the same"},{"line_number":41,"context_line":"  ``VLAN ID``, so we have an L2 network to connect the routers."},{"line_number":42,"context_line":"* The creation of bridge network is triggered during attaching router interface"},{"line_number":43,"context_line":"  and adding router external gateway."}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a122d0e_18044113","line":40,"range":{"start_line":40,"start_character":45,"end_line":40,"end_character":54},"updated":"2016-05-04 22:29:56.000000000","message":"-OpenStack\n+OpenStack instance","commit_id":"61a6b9f6018f12118330293c427d40cad1153b57"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"8ff8ab3b4a44b840da076e164ba4baf8c1e0e14d","unresolved":false,"context_lines":[{"line_number":38,"context_line":"  bottom OpenStack. We configure the extra routes of the routers to route the"},{"line_number":39,"context_line":"  packets from one OpenStack to another. In current implementation, we create"},{"line_number":40,"context_line":"  this special bridge network in each bottom OpenStack with the same"},{"line_number":41,"context_line":"  ``VLAN ID``, so we have an L2 network to connect the routers."},{"line_number":42,"context_line":"* The creation of bridge network is triggered during attaching router interface"},{"line_number":43,"context_line":"  and adding router external gateway."},{"line_number":44,"context_line":"* The L2 network for VM is triggered by ``Nova-APIGW`` when a VM is to being"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a122d0e_b8138d5b","line":41,"range":{"start_line":41,"start_character":43,"end_line":41,"end_character":62},"updated":"2016-05-04 22:29:56.000000000","message":"Where the routers are connected to?","commit_id":"61a6b9f6018f12118330293c427d40cad1153b57"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"8ff8ab3b4a44b840da076e164ba4baf8c1e0e14d","unresolved":false,"context_lines":[{"line_number":39,"context_line":"  packets from one OpenStack to another. In current implementation, we create"},{"line_number":40,"context_line":"  this special bridge network in each bottom OpenStack with the same"},{"line_number":41,"context_line":"  ``VLAN ID``, so we have an L2 network to connect the routers."},{"line_number":42,"context_line":"* The creation of bridge network is triggered during attaching router interface"},{"line_number":43,"context_line":"  and adding router external gateway."},{"line_number":44,"context_line":"* The L2 network for VM is triggered by ``Nova-APIGW`` when a VM is to being"},{"line_number":45,"context_line":"  created in one pod, and finds that there is no network, then the"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a122d0e_b83a6dcb","line":42,"range":{"start_line":42,"start_character":53,"end_line":42,"end_character":79},"updated":"2016-05-04 22:29:56.000000000","message":"``attaching router interface`` to where?","commit_id":"61a6b9f6018f12118330293c427d40cad1153b57"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"8ff8ab3b4a44b840da076e164ba4baf8c1e0e14d","unresolved":false,"context_lines":[{"line_number":39,"context_line":"  packets from one OpenStack to another. In current implementation, we create"},{"line_number":40,"context_line":"  this special bridge network in each bottom OpenStack with the same"},{"line_number":41,"context_line":"  ``VLAN ID``, so we have an L2 network to connect the routers."},{"line_number":42,"context_line":"* The creation of bridge network is triggered during attaching router interface"},{"line_number":43,"context_line":"  and adding router external gateway."},{"line_number":44,"context_line":"* The L2 network for VM is triggered by ``Nova-APIGW`` when a VM is to being"},{"line_number":45,"context_line":"  created in one pod, and finds that there is no network, then the"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a122d0e_d82da990","line":42,"range":{"start_line":42,"start_character":33,"end_line":42,"end_character":45},"updated":"2016-05-04 22:29:56.000000000","message":"``is triggered`` by what?","commit_id":"61a6b9f6018f12118330293c427d40cad1153b57"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"8ff8ab3b4a44b840da076e164ba4baf8c1e0e14d","unresolved":false,"context_lines":[{"line_number":40,"context_line":"  this special bridge network in each bottom OpenStack with the same"},{"line_number":41,"context_line":"  ``VLAN ID``, so we have an L2 network to connect the routers."},{"line_number":42,"context_line":"* The creation of bridge network is triggered during attaching router interface"},{"line_number":43,"context_line":"  and adding router external gateway."},{"line_number":44,"context_line":"* The L2 network for VM is triggered by ``Nova-APIGW`` when a VM is to being"},{"line_number":45,"context_line":"  created in one pod, and finds that there is no network, then the"},{"line_number":46,"context_line":"  network will be created before the VM is booted, network or port parameter is"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a122d0e_384dbd72","line":43,"range":{"start_line":43,"start_character":6,"end_line":43,"end_character":36},"updated":"2016-05-04 22:29:56.000000000","message":"``adding router external gateway`` to where?","commit_id":"61a6b9f6018f12118330293c427d40cad1153b57"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"8ff8ab3b4a44b840da076e164ba4baf8c1e0e14d","unresolved":false,"context_lines":[{"line_number":41,"context_line":"  ``VLAN ID``, so we have an L2 network to connect the routers."},{"line_number":42,"context_line":"* The creation of bridge network is triggered during attaching router interface"},{"line_number":43,"context_line":"  and adding router external gateway."},{"line_number":44,"context_line":"* The L2 network for VM is triggered by ``Nova-APIGW`` when a VM is to being"},{"line_number":45,"context_line":"  created in one pod, and finds that there is no network, then the"},{"line_number":46,"context_line":"  network will be created before the VM is booted, network or port parameter is"},{"line_number":47,"context_line":"  required to boot VM."}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a122d0e_78ef351d","line":44,"range":{"start_line":44,"start_character":2,"end_line":44,"end_character":16},"updated":"2016-05-04 22:29:56.000000000","message":"-The L2 network\n+The L2 network creation\n  or\n+Creation of the L2 network","commit_id":"61a6b9f6018f12118330293c427d40cad1153b57"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"8ff8ab3b4a44b840da076e164ba4baf8c1e0e14d","unresolved":false,"context_lines":[{"line_number":41,"context_line":"  ``VLAN ID``, so we have an L2 network to connect the routers."},{"line_number":42,"context_line":"* The creation of bridge network is triggered during attaching router interface"},{"line_number":43,"context_line":"  and adding router external gateway."},{"line_number":44,"context_line":"* The L2 network for VM is triggered by ``Nova-APIGW`` when a VM is to being"},{"line_number":45,"context_line":"  created in one pod, and finds that there is no network, then the"},{"line_number":46,"context_line":"  network will be created before the VM is booted, network or port parameter is"},{"line_number":47,"context_line":"  required to boot VM."},{"line_number":48,"context_line":"* The IP/Mac for VM is allocated in the ``Tricircle``, top layer to avoid"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a122d0e_38749d9a","line":45,"range":{"start_line":44,"start_character":60,"end_line":45,"end_character":9},"updated":"2016-05-04 22:29:56.000000000","message":"-a VM is to being created\n+a VM is being created","commit_id":"61a6b9f6018f12118330293c427d40cad1153b57"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"8ff8ab3b4a44b840da076e164ba4baf8c1e0e14d","unresolved":false,"context_lines":[{"line_number":42,"context_line":"* The creation of bridge network is triggered during attaching router interface"},{"line_number":43,"context_line":"  and adding router external gateway."},{"line_number":44,"context_line":"* The L2 network for VM is triggered by ``Nova-APIGW`` when a VM is to being"},{"line_number":45,"context_line":"  created in one pod, and finds that there is no network, then the"},{"line_number":46,"context_line":"  network will be created before the VM is booted, network or port parameter is"},{"line_number":47,"context_line":"  required to boot VM."},{"line_number":48,"context_line":"* The IP/Mac for VM is allocated in the ``Tricircle``, top layer to avoid"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a122d0e_98da1177","line":45,"range":{"start_line":45,"start_character":49,"end_line":45,"end_character":57},"updated":"2016-05-04 22:29:56.000000000","message":"-network,\n+network.","commit_id":"61a6b9f6018f12118330293c427d40cad1153b57"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"8ff8ab3b4a44b840da076e164ba4baf8c1e0e14d","unresolved":false,"context_lines":[{"line_number":42,"context_line":"* The creation of bridge network is triggered during attaching router interface"},{"line_number":43,"context_line":"  and adding router external gateway."},{"line_number":44,"context_line":"* The L2 network for VM is triggered by ``Nova-APIGW`` when a VM is to being"},{"line_number":45,"context_line":"  created in one pod, and finds that there is no network, then the"},{"line_number":46,"context_line":"  network will be created before the VM is booted, network or port parameter is"},{"line_number":47,"context_line":"  required to boot VM."},{"line_number":48,"context_line":"* The IP/Mac for VM is allocated in the ``Tricircle``, top layer to avoid"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a122d0e_58a6b90f","line":45,"range":{"start_line":45,"start_character":26,"end_line":45,"end_character":31},"updated":"2016-05-04 22:29:56.000000000","message":"Who ``finds``?","commit_id":"61a6b9f6018f12118330293c427d40cad1153b57"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"8ff8ab3b4a44b840da076e164ba4baf8c1e0e14d","unresolved":false,"context_lines":[{"line_number":42,"context_line":"* The creation of bridge network is triggered during attaching router interface"},{"line_number":43,"context_line":"  and adding router external gateway."},{"line_number":44,"context_line":"* The L2 network for VM is triggered by ``Nova-APIGW`` when a VM is to being"},{"line_number":45,"context_line":"  created in one pod, and finds that there is no network, then the"},{"line_number":46,"context_line":"  network will be created before the VM is booted, network or port parameter is"},{"line_number":47,"context_line":"  required to boot VM."},{"line_number":48,"context_line":"* The IP/Mac for VM is allocated in the ``Tricircle``, top layer to avoid"},{"line_number":49,"context_line":"  IP/mac collision if they are allocated seperately in bottom pods."},{"line_number":50,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a122d0e_d8fc89b7","line":47,"range":{"start_line":45,"start_character":58,"end_line":47,"end_character":21},"updated":"2016-05-04 22:29:56.000000000","message":"- then the network will be created before the VM is booted, network or port parameter is required to boot VM.\n\n+ Since it\u0027s required to create the network port attached to VM, the network will be created before booting VM.","commit_id":"61a6b9f6018f12118330293c427d40cad1153b57"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"8ff8ab3b4a44b840da076e164ba4baf8c1e0e14d","unresolved":false,"context_lines":[{"line_number":45,"context_line":"  created in one pod, and finds that there is no network, then the"},{"line_number":46,"context_line":"  network will be created before the VM is booted, network or port parameter is"},{"line_number":47,"context_line":"  required to boot VM."},{"line_number":48,"context_line":"* The IP/Mac for VM is allocated in the ``Tricircle``, top layer to avoid"},{"line_number":49,"context_line":"  IP/mac collision if they are allocated seperately in bottom pods."},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"Pluggable L2 networking framework:"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a122d0e_b8954d41","line":48,"range":{"start_line":48,"start_character":53,"end_line":48,"end_character":54},"updated":"2016-05-04 22:29:56.000000000","message":"-,\n+.","commit_id":"61a6b9f6018f12118330293c427d40cad1153b57"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"8ff8ab3b4a44b840da076e164ba4baf8c1e0e14d","unresolved":false,"context_lines":[{"line_number":45,"context_line":"  created in one pod, and finds that there is no network, then the"},{"line_number":46,"context_line":"  network will be created before the VM is booted, network or port parameter is"},{"line_number":47,"context_line":"  required to boot VM."},{"line_number":48,"context_line":"* The IP/Mac for VM is allocated in the ``Tricircle``, top layer to avoid"},{"line_number":49,"context_line":"  IP/mac collision if they are allocated seperately in bottom pods."},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"Pluggable L2 networking framework:"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a122d0e_98e4d10d","line":48,"range":{"start_line":48,"start_character":6,"end_line":48,"end_character":12},"updated":"2016-05-04 22:29:56.000000000","message":"-IP/Mac\n+IP/Mac addresses","commit_id":"61a6b9f6018f12118330293c427d40cad1153b57"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"8ff8ab3b4a44b840da076e164ba4baf8c1e0e14d","unresolved":false,"context_lines":[{"line_number":45,"context_line":"  created in one pod, and finds that there is no network, then the"},{"line_number":46,"context_line":"  network will be created before the VM is booted, network or port parameter is"},{"line_number":47,"context_line":"  required to boot VM."},{"line_number":48,"context_line":"* The IP/Mac for VM is allocated in the ``Tricircle``, top layer to avoid"},{"line_number":49,"context_line":"  IP/mac collision if they are allocated seperately in bottom pods."},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"Pluggable L2 networking framework:"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a122d0e_78b0d5fd","line":48,"range":{"start_line":48,"start_character":33,"end_line":48,"end_character":35},"updated":"2016-05-04 22:29:56.000000000","message":"Maybe not ``in`` but ``by``.","commit_id":"61a6b9f6018f12118330293c427d40cad1153b57"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"8ff8ab3b4a44b840da076e164ba4baf8c1e0e14d","unresolved":false,"context_lines":[{"line_number":45,"context_line":"  created in one pod, and finds that there is no network, then the"},{"line_number":46,"context_line":"  network will be created before the VM is booted, network or port parameter is"},{"line_number":47,"context_line":"  required to boot VM."},{"line_number":48,"context_line":"* The IP/Mac for VM is allocated in the ``Tricircle``, top layer to avoid"},{"line_number":49,"context_line":"  IP/mac collision if they are allocated seperately in bottom pods."},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"Pluggable L2 networking framework:"},{"line_number":52,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a122d0e_98ce9158","line":49,"range":{"start_line":48,"start_character":55,"end_line":49,"end_character":67},"updated":"2016-05-04 22:29:56.000000000","message":"``top layer to avoid IP/mac collision if they are allocated seperately in bottom pods.``\n\nIt would be better to re-consider this sentence.\nWho avoids collision?","commit_id":"61a6b9f6018f12118330293c427d40cad1153b57"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"8ff8ab3b4a44b840da076e164ba4baf8c1e0e14d","unresolved":false,"context_lines":[{"line_number":50,"context_line":""},{"line_number":51,"context_line":"Pluggable L2 networking framework:"},{"line_number":52,"context_line":""},{"line_number":53,"context_line":"* Because ``tricircle`` top does not use ``ml2`` mechanism, so we can use it"},{"line_number":54,"context_line":"  for L2 networking accross openstack. We need to implement different type"},{"line_number":55,"context_line":"  drivers."},{"line_number":56,"context_line":"* Frist, configure ``tenant_network_types \u003d shared_vlan`` for example,"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a122d0e_58ffd965","line":53,"range":{"start_line":53,"start_character":2,"end_line":53,"end_character":23},"updated":"2016-05-04 22:29:56.000000000","message":"-Because ``tricircle``\n+Because the ``Tricircle``","commit_id":"61a6b9f6018f12118330293c427d40cad1153b57"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"8ff8ab3b4a44b840da076e164ba4baf8c1e0e14d","unresolved":false,"context_lines":[{"line_number":50,"context_line":""},{"line_number":51,"context_line":"Pluggable L2 networking framework:"},{"line_number":52,"context_line":""},{"line_number":53,"context_line":"* Because ``tricircle`` top does not use ``ml2`` mechanism, so we can use it"},{"line_number":54,"context_line":"  for L2 networking accross openstack. We need to implement different type"},{"line_number":55,"context_line":"  drivers."},{"line_number":56,"context_line":"* Frist, configure ``tenant_network_types \u003d shared_vlan`` for example,"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a122d0e_d84769a1","line":53,"range":{"start_line":53,"start_character":41,"end_line":53,"end_character":58},"updated":"2016-05-04 22:29:56.000000000","message":"-``ml2`` mechanis\n+``the modular layer 2 (ml2) plugin``","commit_id":"61a6b9f6018f12118330293c427d40cad1153b57"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"8ff8ab3b4a44b840da076e164ba4baf8c1e0e14d","unresolved":false,"context_lines":[{"line_number":50,"context_line":""},{"line_number":51,"context_line":"Pluggable L2 networking framework:"},{"line_number":52,"context_line":""},{"line_number":53,"context_line":"* Because ``tricircle`` top does not use ``ml2`` mechanism, so we can use it"},{"line_number":54,"context_line":"  for L2 networking accross openstack. We need to implement different type"},{"line_number":55,"context_line":"  drivers."},{"line_number":56,"context_line":"* Frist, configure ``tenant_network_types \u003d shared_vlan`` for example,"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a122d0e_b83f0d24","line":53,"range":{"start_line":53,"start_character":24,"end_line":53,"end_character":27},"updated":"2016-05-04 22:29:56.000000000","message":"-top\n+\n\nNo ``top`` description is necessary.","commit_id":"61a6b9f6018f12118330293c427d40cad1153b57"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"8ff8ab3b4a44b840da076e164ba4baf8c1e0e14d","unresolved":false,"context_lines":[{"line_number":51,"context_line":"Pluggable L2 networking framework:"},{"line_number":52,"context_line":""},{"line_number":53,"context_line":"* Because ``tricircle`` top does not use ``ml2`` mechanism, so we can use it"},{"line_number":54,"context_line":"  for L2 networking accross openstack. We need to implement different type"},{"line_number":55,"context_line":"  drivers."},{"line_number":56,"context_line":"* Frist, configure ``tenant_network_types \u003d shared_vlan`` for example,"},{"line_number":57,"context_line":"  ``vlan_range\u003d1-3000``."}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a122d0e_d8de49d9","line":54,"range":{"start_line":54,"start_character":28,"end_line":54,"end_character":37},"updated":"2016-05-04 22:29:56.000000000","message":"-openstack\n+OpenStack instances","commit_id":"61a6b9f6018f12118330293c427d40cad1153b57"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"8ff8ab3b4a44b840da076e164ba4baf8c1e0e14d","unresolved":false,"context_lines":[{"line_number":51,"context_line":"Pluggable L2 networking framework:"},{"line_number":52,"context_line":""},{"line_number":53,"context_line":"* Because ``tricircle`` top does not use ``ml2`` mechanism, so we can use it"},{"line_number":54,"context_line":"  for L2 networking accross openstack. We need to implement different type"},{"line_number":55,"context_line":"  drivers."},{"line_number":56,"context_line":"* Frist, configure ``tenant_network_types \u003d shared_vlan`` for example,"},{"line_number":57,"context_line":"  ``vlan_range\u003d1-3000``."}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a122d0e_f8f8654c","line":54,"range":{"start_line":54,"start_character":70,"end_line":54,"end_character":74},"updated":"2016-05-04 22:29:56.000000000","message":"-type\n+type of","commit_id":"61a6b9f6018f12118330293c427d40cad1153b57"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"8ff8ab3b4a44b840da076e164ba4baf8c1e0e14d","unresolved":false,"context_lines":[{"line_number":53,"context_line":"* Because ``tricircle`` top does not use ``ml2`` mechanism, so we can use it"},{"line_number":54,"context_line":"  for L2 networking accross openstack. We need to implement different type"},{"line_number":55,"context_line":"  drivers."},{"line_number":56,"context_line":"* Frist, configure ``tenant_network_types \u003d shared_vlan`` for example,"},{"line_number":57,"context_line":"  ``vlan_range\u003d1-3000``."},{"line_number":58,"context_line":"* Second, when tenant creates network, ``Tricircle plugin`` invokes the"},{"line_number":59,"context_line":"  corresponding type driver, like ``Shared_vlan_Driver``. And driver allocates"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a122d0e_38bc9d6b","line":56,"range":{"start_line":56,"start_character":19,"end_line":56,"end_character":69},"updated":"2016-05-04 22:29:56.000000000","message":"-``tenant_network_types \u003d shared_vlan`` for example\n+``tenant_network_types \u003d shared_vlan``. For example","commit_id":"61a6b9f6018f12118330293c427d40cad1153b57"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"8ff8ab3b4a44b840da076e164ba4baf8c1e0e14d","unresolved":false,"context_lines":[{"line_number":58,"context_line":"* Second, when tenant creates network, ``Tricircle plugin`` invokes the"},{"line_number":59,"context_line":"  corresponding type driver, like ``Shared_vlan_Driver``. And driver allocates"},{"line_number":60,"context_line":"  segment and assigns ``network_type`` with VLAN, updates DB."},{"line_number":61,"context_line":"* When VM is created, if top needs to send create network message to bottom,"},{"line_number":62,"context_line":"  it sends message inclueds ``network_type \u003d vlan``,"},{"line_number":63,"context_line":"  ``physical_network \u003d p1``, ``segmentation \u003d vlan 1`` to bottom."},{"line_number":64,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a122d0e_b85eed42","line":61,"range":{"start_line":61,"start_character":43,"end_line":61,"end_character":57},"updated":"2016-05-04 22:29:56.000000000","message":"-create network\n+network creation","commit_id":"61a6b9f6018f12118330293c427d40cad1153b57"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"8ff8ab3b4a44b840da076e164ba4baf8c1e0e14d","unresolved":false,"context_lines":[{"line_number":59,"context_line":"  corresponding type driver, like ``Shared_vlan_Driver``. And driver allocates"},{"line_number":60,"context_line":"  segment and assigns ``network_type`` with VLAN, updates DB."},{"line_number":61,"context_line":"* When VM is created, if top needs to send create network message to bottom,"},{"line_number":62,"context_line":"  it sends message inclueds ``network_type \u003d vlan``,"},{"line_number":63,"context_line":"  ``physical_network \u003d p1``, ``segmentation \u003d vlan 1`` to bottom."},{"line_number":64,"context_line":""},{"line_number":65,"context_line":"Data model impact"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a122d0e_38313d0c","line":62,"range":{"start_line":62,"start_character":19,"end_line":62,"end_character":27},"updated":"2016-05-04 22:29:56.000000000","message":"-inclueds\n+inclueding\n  or\n+with","commit_id":"61a6b9f6018f12118330293c427d40cad1153b57"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"8ff8ab3b4a44b840da076e164ba4baf8c1e0e14d","unresolved":false,"context_lines":[{"line_number":65,"context_line":"Data model impact"},{"line_number":66,"context_line":"-----------------"},{"line_number":67,"context_line":""},{"line_number":68,"context_line":"In database, we are considering setting physical_network in top OpenStack as"},{"line_number":69,"context_line":"``bottom_physical_network#bottom_pod_id`` to distinguish segmentation"},{"line_number":70,"context_line":"information in different bottom OpenStack."},{"line_number":71,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a122d0e_982211b8","line":68,"range":{"start_line":68,"start_character":64,"end_line":68,"end_character":73},"updated":"2016-05-04 22:29:56.000000000","message":"-OpenStack\n+OpenStack instance","commit_id":"61a6b9f6018f12118330293c427d40cad1153b57"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"8ff8ab3b4a44b840da076e164ba4baf8c1e0e14d","unresolved":false,"context_lines":[{"line_number":67,"context_line":""},{"line_number":68,"context_line":"In database, we are considering setting physical_network in top OpenStack as"},{"line_number":69,"context_line":"``bottom_physical_network#bottom_pod_id`` to distinguish segmentation"},{"line_number":70,"context_line":"information in different bottom OpenStack."},{"line_number":71,"context_line":""},{"line_number":72,"context_line":"REST API impact"},{"line_number":73,"context_line":"---------------"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a122d0e_d828099a","line":70,"range":{"start_line":70,"start_character":32,"end_line":70,"end_character":41},"updated":"2016-05-04 22:29:56.000000000","message":"-OpenStack\n+OpenStack instances","commit_id":"61a6b9f6018f12118330293c427d40cad1153b57"},{"author":{"_account_id":20971,"name":"Feng Pan","email":"fpan@redhat.com","username":"fpan"},"change_message_id":"933adb9a60965b2b4b86b2b084e5a1542c7abe99","unresolved":false,"context_lines":[{"line_number":11,"context_line":"L2 network and its automation in one site or multiple sites."},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"The simplest way to stretch one L2 network across multiple OpenStack instances"},{"line_number":14,"context_line":"is to use a same VLAN network, but there is a lot of limitation: the number"},{"line_number":15,"context_line":"of VLAN segment is limited, the VLAN network itself is not good to spread"},{"line_number":16,"context_line":"across multiple sites, although you can use some gateways to do so."},{"line_number":17,"context_line":""},{"line_number":18,"context_line":"So flexible tenant level L2 networking across multiple OpenStack instances in"}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_b2775e39","line":15,"range":{"start_line":14,"start_character":65,"end_line":15,"end_character":26},"updated":"2016-05-07 21:29:20.000000000","message":"How is stretching a L2 network limited by number of VLAN segments?","commit_id":"6be0ce36bc2135a9ee18b2dc1602243ddc53934e"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"1791201d75e322cb40481fc525625cbdd3f9f81d","unresolved":false,"context_lines":[{"line_number":11,"context_line":"L2 network and its automation in one site or multiple sites."},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"The simplest way to stretch one L2 network across multiple OpenStack instances"},{"line_number":14,"context_line":"is to use a same VLAN network, but there is a lot of limitation: the number"},{"line_number":15,"context_line":"of VLAN segment is limited, the VLAN network itself is not good to spread"},{"line_number":16,"context_line":"across multiple sites, although you can use some gateways to do so."},{"line_number":17,"context_line":""},{"line_number":18,"context_line":"So flexible tenant level L2 networking across multiple OpenStack instances in"}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_30bdef68","line":15,"range":{"start_line":14,"start_character":65,"end_line":15,"end_character":26},"in_reply_to":"dab17558_b2775e39","updated":"2016-05-10 03:19:44.000000000","message":"VLAN ID scope 0~4095. Of course the number could be larger if hierarchical-port-binding is used,https://specs.openstack.org/openstack/neutron-specs/specs/kilo/ml2-hierarchical-port-binding.html . But there is still lack cross OpenStack VLAN networking automation by other controllers when a VM is provisioned.","commit_id":"6be0ce36bc2135a9ee18b2dc1602243ddc53934e"},{"author":{"_account_id":20971,"name":"Feng Pan","email":"fpan@redhat.com","username":"fpan"},"change_message_id":"933adb9a60965b2b4b86b2b084e5a1542c7abe99","unresolved":false,"context_lines":[{"line_number":12,"context_line":""},{"line_number":13,"context_line":"The simplest way to stretch one L2 network across multiple OpenStack instances"},{"line_number":14,"context_line":"is to use a same VLAN network, but there is a lot of limitation: the number"},{"line_number":15,"context_line":"of VLAN segment is limited, the VLAN network itself is not good to spread"},{"line_number":16,"context_line":"across multiple sites, although you can use some gateways to do so."},{"line_number":17,"context_line":""},{"line_number":18,"context_line":"So flexible tenant level L2 networking across multiple OpenStack instances in"},{"line_number":19,"context_line":"one site or in multiple sites is needed."}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_92721a48","line":16,"range":{"start_line":15,"start_character":28,"end_line":16,"end_character":21},"updated":"2016-05-07 21:29:20.000000000","message":"What does this mean? Might want to expand a bit.","commit_id":"6be0ce36bc2135a9ee18b2dc1602243ddc53934e"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"1791201d75e322cb40481fc525625cbdd3f9f81d","unresolved":false,"context_lines":[{"line_number":12,"context_line":""},{"line_number":13,"context_line":"The simplest way to stretch one L2 network across multiple OpenStack instances"},{"line_number":14,"context_line":"is to use a same VLAN network, but there is a lot of limitation: the number"},{"line_number":15,"context_line":"of VLAN segment is limited, the VLAN network itself is not good to spread"},{"line_number":16,"context_line":"across multiple sites, although you can use some gateways to do so."},{"line_number":17,"context_line":""},{"line_number":18,"context_line":"So flexible tenant level L2 networking across multiple OpenStack instances in"},{"line_number":19,"context_line":"one site or in multiple sites is needed."}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_10354bf6","line":16,"range":{"start_line":15,"start_character":28,"end_line":16,"end_character":21},"in_reply_to":"dab17558_92721a48","updated":"2016-05-10 03:19:44.000000000","message":"Streching a VLAN network to multiple sites, you have to use gateway with tunneling, i.e, L2 over L3. But the configuration for gateways in different sites needs to be done manually or by SDN controller, but the automation is not aware of VM provisioning, so it\u0027s still some work outside  the cloud, and not flexible, one to one mapping in multiple sites","commit_id":"6be0ce36bc2135a9ee18b2dc1602243ddc53934e"},{"author":{"_account_id":20971,"name":"Feng Pan","email":"fpan@redhat.com","username":"fpan"},"change_message_id":"933adb9a60965b2b4b86b2b084e5a1542c7abe99","unresolved":false,"context_lines":[{"line_number":18,"context_line":"So flexible tenant level L2 networking across multiple OpenStack instances in"},{"line_number":19,"context_line":"one site or in multiple sites is needed."},{"line_number":20,"context_line":""},{"line_number":21,"context_line":"One bottom OpenStack managed by Tricircle is also called one pod in short."},{"line_number":22,"context_line":""},{"line_number":23,"context_line":"Use Cases"},{"line_number":24,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_d2b942cd","line":21,"range":{"start_line":21,"start_character":0,"end_line":21,"end_character":74},"updated":"2016-05-07 21:29:20.000000000","message":"This sentence doesn\u0027t seem to belong to \"problem description\"","commit_id":"6be0ce36bc2135a9ee18b2dc1602243ddc53934e"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"1791201d75e322cb40481fc525625cbdd3f9f81d","unresolved":false,"context_lines":[{"line_number":18,"context_line":"So flexible tenant level L2 networking across multiple OpenStack instances in"},{"line_number":19,"context_line":"one site or in multiple sites is needed."},{"line_number":20,"context_line":""},{"line_number":21,"context_line":"One bottom OpenStack managed by Tricircle is also called one pod in short."},{"line_number":22,"context_line":""},{"line_number":23,"context_line":"Use Cases"},{"line_number":24,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_90913b55","line":21,"range":{"start_line":21,"start_character":0,"end_line":21,"end_character":74},"in_reply_to":"dab17558_d2b942cd","updated":"2016-05-10 03:19:44.000000000","message":"Done","commit_id":"6be0ce36bc2135a9ee18b2dc1602243ddc53934e"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"5386eba062bee375052aed7d9c4f40b135acfd4f","unresolved":false,"context_lines":[{"line_number":223,"context_line":""},{"line_number":224,"context_line":"**Local Network implementation:**"},{"line_number":225,"context_line":""},{"line_number":226,"context_line":"For Local Network, L2GW is not required. In this scenario, no cross pod L2/L3"},{"line_number":227,"context_line":"networking is required, even L3 will be local into some specified pod."},{"line_number":228,"context_line":""},{"line_number":229,"context_line":"A user creates network Net1, Tricircle plugin check the configuration, if"}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_6ed07454","line":226,"range":{"start_line":226,"start_character":4,"end_line":226,"end_character":17},"updated":"2016-05-07 09:08:19.000000000","message":"We have a specific definition for \"Local Network\":\nPlease refer to:\n\n7.4.2 L2 Networking ( local network )\n\nin our blueprint.","commit_id":"6be0ce36bc2135a9ee18b2dc1602243ddc53934e"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"1791201d75e322cb40481fc525625cbdd3f9f81d","unresolved":false,"context_lines":[{"line_number":223,"context_line":""},{"line_number":224,"context_line":"**Local Network implementation:**"},{"line_number":225,"context_line":""},{"line_number":226,"context_line":"For Local Network, L2GW is not required. In this scenario, no cross pod L2/L3"},{"line_number":227,"context_line":"networking is required, even L3 will be local into some specified pod."},{"line_number":228,"context_line":""},{"line_number":229,"context_line":"A user creates network Net1, Tricircle plugin check the configuration, if"}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_ab420e3c","line":226,"range":{"start_line":226,"start_character":4,"end_line":226,"end_character":17},"in_reply_to":"dab17558_6ed07454","updated":"2016-05-10 03:19:44.000000000","message":"Done","commit_id":"6be0ce36bc2135a9ee18b2dc1602243ddc53934e"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"5386eba062bee375052aed7d9c4f40b135acfd4f","unresolved":false,"context_lines":[{"line_number":224,"context_line":"**Local Network implementation:**"},{"line_number":225,"context_line":""},{"line_number":226,"context_line":"For Local Network, L2GW is not required. In this scenario, no cross pod L2/L3"},{"line_number":227,"context_line":"networking is required, even L3 will be local into some specified pod."},{"line_number":228,"context_line":""},{"line_number":229,"context_line":"A user creates network Net1, Tricircle plugin check the configuration, if"},{"line_number":230,"context_line":"``tenant_network_type`` equals “lcoal_network”, it will invoke Local Network"}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_4ed5b041","line":227,"range":{"start_line":227,"start_character":14,"end_line":227,"end_character":23},"updated":"2016-05-07 09:08:19.000000000","message":"-required,\n+required.","commit_id":"6be0ce36bc2135a9ee18b2dc1602243ddc53934e"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"5386eba062bee375052aed7d9c4f40b135acfd4f","unresolved":false,"context_lines":[{"line_number":224,"context_line":"**Local Network implementation:**"},{"line_number":225,"context_line":""},{"line_number":226,"context_line":"For Local Network, L2GW is not required. In this scenario, no cross pod L2/L3"},{"line_number":227,"context_line":"networking is required, even L3 will be local into some specified pod."},{"line_number":228,"context_line":""},{"line_number":229,"context_line":"A user creates network Net1, Tricircle plugin check the configuration, if"},{"line_number":230,"context_line":"``tenant_network_type`` equals “lcoal_network”, it will invoke Local Network"}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_2ebf8cfc","line":227,"range":{"start_line":227,"start_character":24,"end_line":227,"end_character":70},"updated":"2016-05-07 09:08:19.000000000","message":"This sentence should be idenpendent:\n\n-even L3 will be local into some specified pod.\n\nCurrent one does not mean anything.\nPlease consider what we would really like to tell people with this sentence.","commit_id":"6be0ce36bc2135a9ee18b2dc1602243ddc53934e"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"1791201d75e322cb40481fc525625cbdd3f9f81d","unresolved":false,"context_lines":[{"line_number":224,"context_line":"**Local Network implementation:**"},{"line_number":225,"context_line":""},{"line_number":226,"context_line":"For Local Network, L2GW is not required. In this scenario, no cross pod L2/L3"},{"line_number":227,"context_line":"networking is required, even L3 will be local into some specified pod."},{"line_number":228,"context_line":""},{"line_number":229,"context_line":"A user creates network Net1, Tricircle plugin check the configuration, if"},{"line_number":230,"context_line":"``tenant_network_type`` equals “lcoal_network”, it will invoke Local Network"}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_cbb5d231","line":227,"range":{"start_line":227,"start_character":24,"end_line":227,"end_character":70},"in_reply_to":"dab17558_2ebf8cfc","updated":"2016-05-10 03:19:44.000000000","message":"Agree. This sentence needs to be removed","commit_id":"6be0ce36bc2135a9ee18b2dc1602243ddc53934e"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"5386eba062bee375052aed7d9c4f40b135acfd4f","unresolved":false,"context_lines":[{"line_number":226,"context_line":"For Local Network, L2GW is not required. In this scenario, no cross pod L2/L3"},{"line_number":227,"context_line":"networking is required, even L3 will be local into some specified pod."},{"line_number":228,"context_line":""},{"line_number":229,"context_line":"A user creates network Net1, Tricircle plugin check the configuration, if"},{"line_number":230,"context_line":"``tenant_network_type`` equals “lcoal_network”, it will invoke Local Network"},{"line_number":231,"context_line":"type driver. Local Network driver and update network with ``network_type``"},{"line_number":232,"context_line":"to DB."}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_ae41bc0d","line":229,"range":{"start_line":229,"start_character":29,"end_line":229,"end_character":38},"updated":"2016-05-07 09:08:19.000000000","message":"-Tricircle\n+the Tricircle","commit_id":"6be0ce36bc2135a9ee18b2dc1602243ddc53934e"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"5386eba062bee375052aed7d9c4f40b135acfd4f","unresolved":false,"context_lines":[{"line_number":226,"context_line":"For Local Network, L2GW is not required. In this scenario, no cross pod L2/L3"},{"line_number":227,"context_line":"networking is required, even L3 will be local into some specified pod."},{"line_number":228,"context_line":""},{"line_number":229,"context_line":"A user creates network Net1, Tricircle plugin check the configuration, if"},{"line_number":230,"context_line":"``tenant_network_type`` equals “lcoal_network”, it will invoke Local Network"},{"line_number":231,"context_line":"type driver. Local Network driver and update network with ``network_type``"},{"line_number":232,"context_line":"to DB."}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_ee4bc429","line":229,"range":{"start_line":229,"start_character":46,"end_line":229,"end_character":51},"updated":"2016-05-07 09:08:19.000000000","message":"-check\n+checks","commit_id":"6be0ce36bc2135a9ee18b2dc1602243ddc53934e"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"1791201d75e322cb40481fc525625cbdd3f9f81d","unresolved":false,"context_lines":[{"line_number":226,"context_line":"For Local Network, L2GW is not required. In this scenario, no cross pod L2/L3"},{"line_number":227,"context_line":"networking is required, even L3 will be local into some specified pod."},{"line_number":228,"context_line":""},{"line_number":229,"context_line":"A user creates network Net1, Tricircle plugin check the configuration, if"},{"line_number":230,"context_line":"``tenant_network_type`` equals “lcoal_network”, it will invoke Local Network"},{"line_number":231,"context_line":"type driver. Local Network driver and update network with ``network_type``"},{"line_number":232,"context_line":"to DB."}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_0b86ba64","line":229,"range":{"start_line":229,"start_character":46,"end_line":229,"end_character":51},"in_reply_to":"dab17558_ee4bc429","updated":"2016-05-10 03:19:44.000000000","message":"Done","commit_id":"6be0ce36bc2135a9ee18b2dc1602243ddc53934e"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"5386eba062bee375052aed7d9c4f40b135acfd4f","unresolved":false,"context_lines":[{"line_number":228,"context_line":""},{"line_number":229,"context_line":"A user creates network Net1, Tricircle plugin check the configuration, if"},{"line_number":230,"context_line":"``tenant_network_type`` equals “lcoal_network”, it will invoke Local Network"},{"line_number":231,"context_line":"type driver. Local Network driver and update network with ``network_type``"},{"line_number":232,"context_line":"to DB."},{"line_number":233,"context_line":""},{"line_number":234,"context_line":"A user creates VM1 in AZ1, and connects it to network Net1. If VM will be"}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_ce6fe090","line":231,"range":{"start_line":231,"start_character":13,"end_line":231,"end_character":33},"updated":"2016-05-07 09:08:19.000000000","message":"\"Local network driver\" is what?","commit_id":"6be0ce36bc2135a9ee18b2dc1602243ddc53934e"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"5386eba062bee375052aed7d9c4f40b135acfd4f","unresolved":false,"context_lines":[{"line_number":228,"context_line":""},{"line_number":229,"context_line":"A user creates network Net1, Tricircle plugin check the configuration, if"},{"line_number":230,"context_line":"``tenant_network_type`` equals “lcoal_network”, it will invoke Local Network"},{"line_number":231,"context_line":"type driver. Local Network driver and update network with ``network_type``"},{"line_number":232,"context_line":"to DB."},{"line_number":233,"context_line":""},{"line_number":234,"context_line":"A user creates VM1 in AZ1, and connects it to network Net1. If VM will be"}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_6e0514c1","line":231,"range":{"start_line":231,"start_character":38,"end_line":231,"end_character":52},"updated":"2016-05-07 09:08:19.000000000","message":"What \"update network\"? Subject is missing.","commit_id":"6be0ce36bc2135a9ee18b2dc1602243ddc53934e"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"1791201d75e322cb40481fc525625cbdd3f9f81d","unresolved":false,"context_lines":[{"line_number":228,"context_line":""},{"line_number":229,"context_line":"A user creates network Net1, Tricircle plugin check the configuration, if"},{"line_number":230,"context_line":"``tenant_network_type`` equals “lcoal_network”, it will invoke Local Network"},{"line_number":231,"context_line":"type driver. Local Network driver and update network with ``network_type``"},{"line_number":232,"context_line":"to DB."},{"line_number":233,"context_line":""},{"line_number":234,"context_line":"A user creates VM1 in AZ1, and connects it to network Net1. If VM will be"}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_2bea9e0f","line":231,"range":{"start_line":231,"start_character":13,"end_line":231,"end_character":33},"in_reply_to":"dab17558_ce6fe090","updated":"2016-05-10 03:19:44.000000000","message":"Changed to:  Local_Network driver under the Tricircle plugin will update network with ``network_type`` to DB.","commit_id":"6be0ce36bc2135a9ee18b2dc1602243ddc53934e"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"5386eba062bee375052aed7d9c4f40b135acfd4f","unresolved":false,"context_lines":[{"line_number":231,"context_line":"type driver. Local Network driver and update network with ``network_type``"},{"line_number":232,"context_line":"to DB."},{"line_number":233,"context_line":""},{"line_number":234,"context_line":"A user creates VM1 in AZ1, and connects it to network Net1. If VM will be"},{"line_number":235,"context_line":"booted in POD1 (it should only one pod in AZ1), ``Nova-APIGW`` will send"},{"line_number":236,"context_line":"create network message to POD1. So a regarding logical network will be"},{"line_number":237,"context_line":"created in POD1."}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_4ed81054","line":234,"range":{"start_line":234,"start_character":66,"end_line":234,"end_character":73},"updated":"2016-05-07 09:08:19.000000000","message":"-will be\n+is","commit_id":"6be0ce36bc2135a9ee18b2dc1602243ddc53934e"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"5386eba062bee375052aed7d9c4f40b135acfd4f","unresolved":false,"context_lines":[{"line_number":231,"context_line":"type driver. Local Network driver and update network with ``network_type``"},{"line_number":232,"context_line":"to DB."},{"line_number":233,"context_line":""},{"line_number":234,"context_line":"A user creates VM1 in AZ1, and connects it to network Net1. If VM will be"},{"line_number":235,"context_line":"booted in POD1 (it should only one pod in AZ1), ``Nova-APIGW`` will send"},{"line_number":236,"context_line":"create network message to POD1. So a regarding logical network will be"},{"line_number":237,"context_line":"created in POD1."}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_4e3130a2","line":234,"range":{"start_line":234,"start_character":0,"end_line":234,"end_character":59},"updated":"2016-05-07 09:08:19.000000000","message":"It\u0027s better to start this sentence from \"For example\" or \"For instance\", isn\u0027t it?","commit_id":"6be0ce36bc2135a9ee18b2dc1602243ddc53934e"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"1791201d75e322cb40481fc525625cbdd3f9f81d","unresolved":false,"context_lines":[{"line_number":231,"context_line":"type driver. Local Network driver and update network with ``network_type``"},{"line_number":232,"context_line":"to DB."},{"line_number":233,"context_line":""},{"line_number":234,"context_line":"A user creates VM1 in AZ1, and connects it to network Net1. If VM will be"},{"line_number":235,"context_line":"booted in POD1 (it should only one pod in AZ1), ``Nova-APIGW`` will send"},{"line_number":236,"context_line":"create network message to POD1. So a regarding logical network will be"},{"line_number":237,"context_line":"created in POD1."}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_abde8e6a","line":234,"range":{"start_line":234,"start_character":0,"end_line":234,"end_character":59},"in_reply_to":"dab17558_4e3130a2","updated":"2016-05-10 03:19:44.000000000","message":"Done","commit_id":"6be0ce36bc2135a9ee18b2dc1602243ddc53934e"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"1791201d75e322cb40481fc525625cbdd3f9f81d","unresolved":false,"context_lines":[{"line_number":231,"context_line":"type driver. Local Network driver and update network with ``network_type``"},{"line_number":232,"context_line":"to DB."},{"line_number":233,"context_line":""},{"line_number":234,"context_line":"A user creates VM1 in AZ1, and connects it to network Net1. If VM will be"},{"line_number":235,"context_line":"booted in POD1 (it should only one pod in AZ1), ``Nova-APIGW`` will send"},{"line_number":236,"context_line":"create network message to POD1. So a regarding logical network will be"},{"line_number":237,"context_line":"created in POD1."}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_8bd90a86","line":234,"range":{"start_line":234,"start_character":66,"end_line":234,"end_character":73},"in_reply_to":"dab17558_4ed81054","updated":"2016-05-10 03:19:44.000000000","message":"Done","commit_id":"6be0ce36bc2135a9ee18b2dc1602243ddc53934e"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"5386eba062bee375052aed7d9c4f40b135acfd4f","unresolved":false,"context_lines":[{"line_number":232,"context_line":"to DB."},{"line_number":233,"context_line":""},{"line_number":234,"context_line":"A user creates VM1 in AZ1, and connects it to network Net1. If VM will be"},{"line_number":235,"context_line":"booted in POD1 (it should only one pod in AZ1), ``Nova-APIGW`` will send"},{"line_number":236,"context_line":"create network message to POD1. So a regarding logical network will be"},{"line_number":237,"context_line":"created in POD1."},{"line_number":238,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_cee4000f","line":235,"range":{"start_line":235,"start_character":14,"end_line":235,"end_character":15},"updated":"2016-05-07 09:08:19.000000000","message":"+by a user","commit_id":"6be0ce36bc2135a9ee18b2dc1602243ddc53934e"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"5386eba062bee375052aed7d9c4f40b135acfd4f","unresolved":false,"context_lines":[{"line_number":232,"context_line":"to DB."},{"line_number":233,"context_line":""},{"line_number":234,"context_line":"A user creates VM1 in AZ1, and connects it to network Net1. If VM will be"},{"line_number":235,"context_line":"booted in POD1 (it should only one pod in AZ1), ``Nova-APIGW`` will send"},{"line_number":236,"context_line":"create network message to POD1. So a regarding logical network will be"},{"line_number":237,"context_line":"created in POD1."},{"line_number":238,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_0eef28e9","line":235,"range":{"start_line":235,"start_character":19,"end_line":235,"end_character":25},"updated":"2016-05-07 09:08:19.000000000","message":"-should\n+should be\n\nPlus:\n\nWhat is \"it\"?","commit_id":"6be0ce36bc2135a9ee18b2dc1602243ddc53934e"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"1791201d75e322cb40481fc525625cbdd3f9f81d","unresolved":false,"context_lines":[{"line_number":232,"context_line":"to DB."},{"line_number":233,"context_line":""},{"line_number":234,"context_line":"A user creates VM1 in AZ1, and connects it to network Net1. If VM will be"},{"line_number":235,"context_line":"booted in POD1 (it should only one pod in AZ1), ``Nova-APIGW`` will send"},{"line_number":236,"context_line":"create network message to POD1. So a regarding logical network will be"},{"line_number":237,"context_line":"created in POD1."},{"line_number":238,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_6bcb06a6","line":235,"range":{"start_line":235,"start_character":19,"end_line":235,"end_character":25},"in_reply_to":"dab17558_0eef28e9","updated":"2016-05-10 03:19:44.000000000","message":"Change to: There should be only one pod in AZ1","commit_id":"6be0ce36bc2135a9ee18b2dc1602243ddc53934e"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"1791201d75e322cb40481fc525625cbdd3f9f81d","unresolved":false,"context_lines":[{"line_number":232,"context_line":"to DB."},{"line_number":233,"context_line":""},{"line_number":234,"context_line":"A user creates VM1 in AZ1, and connects it to network Net1. If VM will be"},{"line_number":235,"context_line":"booted in POD1 (it should only one pod in AZ1), ``Nova-APIGW`` will send"},{"line_number":236,"context_line":"create network message to POD1. So a regarding logical network will be"},{"line_number":237,"context_line":"created in POD1."},{"line_number":238,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_4b456215","line":235,"range":{"start_line":235,"start_character":14,"end_line":235,"end_character":15},"in_reply_to":"dab17558_cee4000f","updated":"2016-05-10 03:19:44.000000000","message":"it\u0027s by Tricircle, so no need to add \u0027by a user\u0027","commit_id":"6be0ce36bc2135a9ee18b2dc1602243ddc53934e"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"5386eba062bee375052aed7d9c4f40b135acfd4f","unresolved":false,"context_lines":[{"line_number":233,"context_line":""},{"line_number":234,"context_line":"A user creates VM1 in AZ1, and connects it to network Net1. If VM will be"},{"line_number":235,"context_line":"booted in POD1 (it should only one pod in AZ1), ``Nova-APIGW`` will send"},{"line_number":236,"context_line":"create network message to POD1. So a regarding logical network will be"},{"line_number":237,"context_line":"created in POD1."},{"line_number":238,"context_line":""},{"line_number":239,"context_line":"Then the user creates VM2 in AZ2 or POD2 in AZ1, and connects it to network"}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_eece2482","line":236,"range":{"start_line":236,"start_character":32,"end_line":236,"end_character":67},"updated":"2016-05-07 09:08:19.000000000","message":"-So a regarding logical network will\n+ Regarding to logical network, it will","commit_id":"6be0ce36bc2135a9ee18b2dc1602243ddc53934e"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"5386eba062bee375052aed7d9c4f40b135acfd4f","unresolved":false,"context_lines":[{"line_number":233,"context_line":""},{"line_number":234,"context_line":"A user creates VM1 in AZ1, and connects it to network Net1. If VM will be"},{"line_number":235,"context_line":"booted in POD1 (it should only one pod in AZ1), ``Nova-APIGW`` will send"},{"line_number":236,"context_line":"create network message to POD1. So a regarding logical network will be"},{"line_number":237,"context_line":"created in POD1."},{"line_number":238,"context_line":""},{"line_number":239,"context_line":"Then the user creates VM2 in AZ2 or POD2 in AZ1, and connects it to network"}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_4ebf70d0","line":236,"range":{"start_line":236,"start_character":0,"end_line":236,"end_character":22},"updated":"2016-05-07 09:08:19.000000000","message":"-create network message\n+network creation message","commit_id":"6be0ce36bc2135a9ee18b2dc1602243ddc53934e"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"1791201d75e322cb40481fc525625cbdd3f9f81d","unresolved":false,"context_lines":[{"line_number":233,"context_line":""},{"line_number":234,"context_line":"A user creates VM1 in AZ1, and connects it to network Net1. If VM will be"},{"line_number":235,"context_line":"booted in POD1 (it should only one pod in AZ1), ``Nova-APIGW`` will send"},{"line_number":236,"context_line":"create network message to POD1. So a regarding logical network will be"},{"line_number":237,"context_line":"created in POD1."},{"line_number":238,"context_line":""},{"line_number":239,"context_line":"Then the user creates VM2 in AZ2 or POD2 in AZ1, and connects it to network"}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_4b5c42ed","line":236,"range":{"start_line":236,"start_character":0,"end_line":236,"end_character":22},"in_reply_to":"dab17558_4ebf70d0","updated":"2016-05-10 03:19:44.000000000","message":"Done","commit_id":"6be0ce36bc2135a9ee18b2dc1602243ddc53934e"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"1791201d75e322cb40481fc525625cbdd3f9f81d","unresolved":false,"context_lines":[{"line_number":233,"context_line":""},{"line_number":234,"context_line":"A user creates VM1 in AZ1, and connects it to network Net1. If VM will be"},{"line_number":235,"context_line":"booted in POD1 (it should only one pod in AZ1), ``Nova-APIGW`` will send"},{"line_number":236,"context_line":"create network message to POD1. So a regarding logical network will be"},{"line_number":237,"context_line":"created in POD1."},{"line_number":238,"context_line":""},{"line_number":239,"context_line":"Then the user creates VM2 in AZ2 or POD2 in AZ1, and connects it to network"}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_0b099add","line":236,"range":{"start_line":236,"start_character":32,"end_line":236,"end_character":67},"in_reply_to":"dab17558_eece2482","updated":"2016-05-10 03:19:44.000000000","message":"Regarding network will be created in POD1. May be better, what do you think","commit_id":"6be0ce36bc2135a9ee18b2dc1602243ddc53934e"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"5386eba062bee375052aed7d9c4f40b135acfd4f","unresolved":false,"context_lines":[{"line_number":236,"context_line":"create network message to POD1. So a regarding logical network will be"},{"line_number":237,"context_line":"created in POD1."},{"line_number":238,"context_line":""},{"line_number":239,"context_line":"Then the user creates VM2 in AZ2 or POD2 in AZ1, and connects it to network"},{"line_number":240,"context_line":"Net1. It should be failed."},{"line_number":241,"context_line":""},{"line_number":242,"context_line":"**Shared VLAN implementation:**"}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_cecb6071","line":239,"range":{"start_line":239,"start_character":5,"end_line":239,"end_character":13},"updated":"2016-05-07 09:08:19.000000000","message":"-the user\n+a user","commit_id":"6be0ce36bc2135a9ee18b2dc1602243ddc53934e"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"5386eba062bee375052aed7d9c4f40b135acfd4f","unresolved":false,"context_lines":[{"line_number":236,"context_line":"create network message to POD1. So a regarding logical network will be"},{"line_number":237,"context_line":"created in POD1."},{"line_number":238,"context_line":""},{"line_number":239,"context_line":"Then the user creates VM2 in AZ2 or POD2 in AZ1, and connects it to network"},{"line_number":240,"context_line":"Net1. It should be failed."},{"line_number":241,"context_line":""},{"line_number":242,"context_line":"**Shared VLAN implementation:**"}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_4ea650c2","line":239,"range":{"start_line":239,"start_character":14,"end_line":239,"end_character":21},"updated":"2016-05-07 09:08:19.000000000","message":"Maybe \"can create\" is better?\nWhat is your intention of this sentence?","commit_id":"6be0ce36bc2135a9ee18b2dc1602243ddc53934e"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"1791201d75e322cb40481fc525625cbdd3f9f81d","unresolved":false,"context_lines":[{"line_number":236,"context_line":"create network message to POD1. So a regarding logical network will be"},{"line_number":237,"context_line":"created in POD1."},{"line_number":238,"context_line":""},{"line_number":239,"context_line":"Then the user creates VM2 in AZ2 or POD2 in AZ1, and connects it to network"},{"line_number":240,"context_line":"Net1. It should be failed."},{"line_number":241,"context_line":""},{"line_number":242,"context_line":"**Shared VLAN implementation:**"}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_8b1c6a14","line":239,"range":{"start_line":239,"start_character":14,"end_line":239,"end_character":21},"in_reply_to":"dab17558_4ea650c2","updated":"2016-05-10 03:19:44.000000000","message":"If the user wants to create VM2 in AZ2 or POD2 in AZ1, and connects it to\nnetwork Net1 in Tricircle. It should be failed, for the Net1 local_network type,\nand is limited to present in POD1 in AZ1 only.","commit_id":"6be0ce36bc2135a9ee18b2dc1602243ddc53934e"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"1791201d75e322cb40481fc525625cbdd3f9f81d","unresolved":false,"context_lines":[{"line_number":236,"context_line":"create network message to POD1. So a regarding logical network will be"},{"line_number":237,"context_line":"created in POD1."},{"line_number":238,"context_line":""},{"line_number":239,"context_line":"Then the user creates VM2 in AZ2 or POD2 in AZ1, and connects it to network"},{"line_number":240,"context_line":"Net1. It should be failed."},{"line_number":241,"context_line":""},{"line_number":242,"context_line":"**Shared VLAN implementation:**"}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_eb1b7619","line":239,"range":{"start_line":239,"start_character":5,"end_line":239,"end_character":13},"in_reply_to":"dab17558_cecb6071","updated":"2016-05-10 03:19:44.000000000","message":"Done","commit_id":"6be0ce36bc2135a9ee18b2dc1602243ddc53934e"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"5386eba062bee375052aed7d9c4f40b135acfd4f","unresolved":false,"context_lines":[{"line_number":236,"context_line":"create network message to POD1. So a regarding logical network will be"},{"line_number":237,"context_line":"created in POD1."},{"line_number":238,"context_line":""},{"line_number":239,"context_line":"Then the user creates VM2 in AZ2 or POD2 in AZ1, and connects it to network"},{"line_number":240,"context_line":"Net1. It should be failed."},{"line_number":241,"context_line":""},{"line_number":242,"context_line":"**Shared VLAN implementation:**"},{"line_number":243,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_ee958440","line":240,"range":{"start_line":239,"start_character":68,"end_line":240,"end_character":4},"updated":"2016-05-07 09:08:19.000000000","message":"-network Net1\n+network called Net1\n or\n+Net1\n\nI guess that Net1 is simple. But it\u0027s up to you, of course.","commit_id":"6be0ce36bc2135a9ee18b2dc1602243ddc53934e"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"5386eba062bee375052aed7d9c4f40b135acfd4f","unresolved":false,"context_lines":[{"line_number":237,"context_line":"created in POD1."},{"line_number":238,"context_line":""},{"line_number":239,"context_line":"Then the user creates VM2 in AZ2 or POD2 in AZ1, and connects it to network"},{"line_number":240,"context_line":"Net1. It should be failed."},{"line_number":241,"context_line":""},{"line_number":242,"context_line":"**Shared VLAN implementation:**"},{"line_number":243,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_0e744833","line":240,"range":{"start_line":240,"start_character":6,"end_line":240,"end_character":25},"updated":"2016-05-07 09:08:19.000000000","message":"I really do not understand this sentence.\nPlease elaborate on this sentence more?\n\nWhat is \"it\"?\nWhy should it be failed?\n\nI believe that you have some intention about the description becaue you are *the author* of this RST.","commit_id":"6be0ce36bc2135a9ee18b2dc1602243ddc53934e"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"1791201d75e322cb40481fc525625cbdd3f9f81d","unresolved":false,"context_lines":[{"line_number":236,"context_line":"create network message to POD1. So a regarding logical network will be"},{"line_number":237,"context_line":"created in POD1."},{"line_number":238,"context_line":""},{"line_number":239,"context_line":"Then the user creates VM2 in AZ2 or POD2 in AZ1, and connects it to network"},{"line_number":240,"context_line":"Net1. It should be failed."},{"line_number":241,"context_line":""},{"line_number":242,"context_line":"**Shared VLAN implementation:**"},{"line_number":243,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_4be1e2fd","line":240,"range":{"start_line":239,"start_character":68,"end_line":240,"end_character":4},"in_reply_to":"dab17558_ee958440","updated":"2016-05-10 03:19:44.000000000","message":"Change to: If a user wants to create VM2 in AZ2 or POD2 in AZ1, and connects it to\nnetwork Net1 in Tricircle. It should be failed, for the Net1 is local_network\ntype network, and it is limited to present in POD1 in AZ1 only.","commit_id":"6be0ce36bc2135a9ee18b2dc1602243ddc53934e"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"1c422a0a23371e18b82d97148b55979a39c4710a","unresolved":false,"context_lines":[{"line_number":265,"context_line":"Implementation"},{"line_number":266,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":267,"context_line":""},{"line_number":268,"context_line":"**Local Network implementation:**"},{"line_number":269,"context_line":""},{"line_number":270,"context_line":"For Local Network, L2GW is not required. In this scenario, no cross pod L2/L3"},{"line_number":271,"context_line":"networking is required."}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_6c8a8465","line":268,"range":{"start_line":268,"start_character":16,"end_line":268,"end_character":30},"updated":"2016-05-12 03:12:32.000000000","message":"-Implementation\n+Implementation","commit_id":"9f8ff6a059f9fca206ebc6b417786fb548bcc37f"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"1c422a0a23371e18b82d97148b55979a39c4710a","unresolved":false,"context_lines":[{"line_number":273,"context_line":"A user creates network Net1 with single AZ1 in az_hint, the Tricircle plugin"},{"line_number":274,"context_line":"checks the configuration, if ``tenant_network_type`` equals “lcoal_network”,"},{"line_number":275,"context_line":"it will invoke Local Network type driver. Local_Network driver under the"},{"line_number":276,"context_line":"Tricircle plugin will update network with ``network_type`` to DB."},{"line_number":277,"context_line":""},{"line_number":278,"context_line":"For exmaple, a user creates VM1 in AZ1, and connects it to network Net1. If"},{"line_number":279,"context_line":"VM is booted in POD1 in AZ1 (There should be only one pod in AZ1), "}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_4c4ea03b","line":276,"range":{"start_line":276,"start_character":22,"end_line":276,"end_character":64},"updated":"2016-05-12 03:12:32.000000000","message":"Where does this update happen?","commit_id":"9f8ff6a059f9fca206ebc6b417786fb548bcc37f"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"1c422a0a23371e18b82d97148b55979a39c4710a","unresolved":false,"context_lines":[{"line_number":276,"context_line":"Tricircle plugin will update network with ``network_type`` to DB."},{"line_number":277,"context_line":""},{"line_number":278,"context_line":"For exmaple, a user creates VM1 in AZ1, and connects it to network Net1. If"},{"line_number":279,"context_line":"VM is booted in POD1 in AZ1 (There should be only one pod in AZ1), "},{"line_number":280,"context_line":"``Nova API-GW`` will send network creation message to POD1. Regarding network"},{"line_number":281,"context_line":"will be created in POD1."},{"line_number":282,"context_line":""}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_4c7fc014","line":279,"range":{"start_line":279,"start_character":0,"end_line":279,"end_character":12},"updated":"2016-05-12 03:12:32.000000000","message":"*During VM is being booted, *\n\n``Nova API-GW`` will send network creation message to POD1?\n\nOtherwise dependencies is not correctly explained in this sentence.","commit_id":"9f8ff6a059f9fca206ebc6b417786fb548bcc37f"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"1c422a0a23371e18b82d97148b55979a39c4710a","unresolved":false,"context_lines":[{"line_number":277,"context_line":""},{"line_number":278,"context_line":"For exmaple, a user creates VM1 in AZ1, and connects it to network Net1. If"},{"line_number":279,"context_line":"VM is booted in POD1 in AZ1 (There should be only one pod in AZ1), "},{"line_number":280,"context_line":"``Nova API-GW`` will send network creation message to POD1. Regarding network"},{"line_number":281,"context_line":"will be created in POD1."},{"line_number":282,"context_line":""},{"line_number":283,"context_line":"If a user wants to create VM2 in AZ2 or POD2 in AZ1, and connects it to"},{"line_number":284,"context_line":"network Net1 in Tricircle. It should be failed, for the Net1 is local_network"}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_aca62cbe","line":281,"range":{"start_line":280,"start_character":60,"end_line":281,"end_character":24},"updated":"2016-05-12 03:12:32.000000000","message":"-Regarding network will be created in POD1.\n-Network will be created in POD1.\n\nOtherwise subject is missing in this sentence.","commit_id":"9f8ff6a059f9fca206ebc6b417786fb548bcc37f"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"1c422a0a23371e18b82d97148b55979a39c4710a","unresolved":false,"context_lines":[{"line_number":280,"context_line":"``Nova API-GW`` will send network creation message to POD1. Regarding network"},{"line_number":281,"context_line":"will be created in POD1."},{"line_number":282,"context_line":""},{"line_number":283,"context_line":"If a user wants to create VM2 in AZ2 or POD2 in AZ1, and connects it to"},{"line_number":284,"context_line":"network Net1 in Tricircle. It should be failed, for the Net1 is local_network"},{"line_number":285,"context_line":"type network, and it is limited to present in POD1 in AZ1 only."},{"line_number":286,"context_line":""}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_2ca19c94","line":283,"range":{"start_line":283,"start_character":57,"end_line":283,"end_character":65},"updated":"2016-05-12 03:12:32.000000000","message":"-connects\n+connect\n\nBecause I\u0027m expecting \"a user wants to create..., and connect\"","commit_id":"9f8ff6a059f9fca206ebc6b417786fb548bcc37f"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"1c422a0a23371e18b82d97148b55979a39c4710a","unresolved":false,"context_lines":[{"line_number":281,"context_line":"will be created in POD1."},{"line_number":282,"context_line":""},{"line_number":283,"context_line":"If a user wants to create VM2 in AZ2 or POD2 in AZ1, and connects it to"},{"line_number":284,"context_line":"network Net1 in Tricircle. It should be failed, for the Net1 is local_network"},{"line_number":285,"context_line":"type network, and it is limited to present in POD1 in AZ1 only."},{"line_number":286,"context_line":""},{"line_number":287,"context_line":"**Shared VLAN implementation:**"}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_ac946c36","line":284,"range":{"start_line":284,"start_character":16,"end_line":284,"end_character":25},"updated":"2016-05-12 03:12:32.000000000","message":"-Tricircle\n+the Tricircle","commit_id":"9f8ff6a059f9fca206ebc6b417786fb548bcc37f"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"1c422a0a23371e18b82d97148b55979a39c4710a","unresolved":false,"context_lines":[{"line_number":281,"context_line":"will be created in POD1."},{"line_number":282,"context_line":""},{"line_number":283,"context_line":"If a user wants to create VM2 in AZ2 or POD2 in AZ1, and connects it to"},{"line_number":284,"context_line":"network Net1 in Tricircle. It should be failed, for the Net1 is local_network"},{"line_number":285,"context_line":"type network, and it is limited to present in POD1 in AZ1 only."},{"line_number":286,"context_line":""},{"line_number":287,"context_line":"**Shared VLAN implementation:**"}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_2ccfdc56","line":284,"range":{"start_line":284,"start_character":47,"end_line":284,"end_character":77},"updated":"2016-05-12 03:12:32.000000000","message":"Subject is missing.","commit_id":"9f8ff6a059f9fca206ebc6b417786fb548bcc37f"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"1c422a0a23371e18b82d97148b55979a39c4710a","unresolved":false,"context_lines":[{"line_number":282,"context_line":""},{"line_number":283,"context_line":"If a user wants to create VM2 in AZ2 or POD2 in AZ1, and connects it to"},{"line_number":284,"context_line":"network Net1 in Tricircle. It should be failed, for the Net1 is local_network"},{"line_number":285,"context_line":"type network, and it is limited to present in POD1 in AZ1 only."},{"line_number":286,"context_line":""},{"line_number":287,"context_line":"**Shared VLAN implementation:**"},{"line_number":288,"context_line":""}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_ecff9463","line":285,"range":{"start_line":285,"start_character":18,"end_line":285,"end_character":62},"updated":"2016-05-12 03:12:32.000000000","message":"Can you elaborate on this sentence.\n\nWhat is \"it\"?\nWhat does \"limited\" mean?","commit_id":"9f8ff6a059f9fca206ebc6b417786fb548bcc37f"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"1c422a0a23371e18b82d97148b55979a39c4710a","unresolved":false,"context_lines":[{"line_number":284,"context_line":"network Net1 in Tricircle. It should be failed, for the Net1 is local_network"},{"line_number":285,"context_line":"type network, and it is limited to present in POD1 in AZ1 only."},{"line_number":286,"context_line":""},{"line_number":287,"context_line":"**Shared VLAN implementation:**"},{"line_number":288,"context_line":""},{"line_number":289,"context_line":"For Shared VLAN, L2GW is not required. This is the most simplified cross pod"},{"line_number":290,"context_line":"L2 networking, using in limited scenario, for example, very limited number of"}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_8cf1a897","line":287,"range":{"start_line":287,"start_character":14,"end_line":287,"end_character":28},"updated":"2016-05-12 03:12:32.000000000","message":"-implementation\n+Implementation","commit_id":"9f8ff6a059f9fca206ebc6b417786fb548bcc37f"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"1c422a0a23371e18b82d97148b55979a39c4710a","unresolved":false,"context_lines":[{"line_number":286,"context_line":""},{"line_number":287,"context_line":"**Shared VLAN implementation:**"},{"line_number":288,"context_line":""},{"line_number":289,"context_line":"For Shared VLAN, L2GW is not required. This is the most simplified cross pod"},{"line_number":290,"context_line":"L2 networking, using in limited scenario, for example, very limited number of"},{"line_number":291,"context_line":"network, VLAN are extended through physical gateway to support cross site VLAN"},{"line_number":292,"context_line":"networking, or all pods under same core switch with same visible VLAN ranges."}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_85f05bca","line":289,"range":{"start_line":289,"start_character":56,"end_line":289,"end_character":66},"updated":"2016-05-12 03:12:32.000000000","message":"-simplified\n+simplest","commit_id":"9f8ff6a059f9fca206ebc6b417786fb548bcc37f"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"1c422a0a23371e18b82d97148b55979a39c4710a","unresolved":false,"context_lines":[{"line_number":287,"context_line":"**Shared VLAN implementation:**"},{"line_number":288,"context_line":""},{"line_number":289,"context_line":"For Shared VLAN, L2GW is not required. This is the most simplified cross pod"},{"line_number":290,"context_line":"L2 networking, using in limited scenario, for example, very limited number of"},{"line_number":291,"context_line":"network, VLAN are extended through physical gateway to support cross site VLAN"},{"line_number":292,"context_line":"networking, or all pods under same core switch with same visible VLAN ranges."},{"line_number":293,"context_line":""}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_a5a63fbe","line":290,"range":{"start_line":290,"start_character":40,"end_line":290,"end_character":41},"updated":"2016-05-12 03:12:32.000000000","message":"-,\n+.","commit_id":"9f8ff6a059f9fca206ebc6b417786fb548bcc37f"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"1c422a0a23371e18b82d97148b55979a39c4710a","unresolved":false,"context_lines":[{"line_number":287,"context_line":"**Shared VLAN implementation:**"},{"line_number":288,"context_line":""},{"line_number":289,"context_line":"For Shared VLAN, L2GW is not required. This is the most simplified cross pod"},{"line_number":290,"context_line":"L2 networking, using in limited scenario, for example, very limited number of"},{"line_number":291,"context_line":"network, VLAN are extended through physical gateway to support cross site VLAN"},{"line_number":292,"context_line":"networking, or all pods under same core switch with same visible VLAN ranges."},{"line_number":293,"context_line":""}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_45d15322","line":290,"range":{"start_line":290,"start_character":13,"end_line":290,"end_character":23},"updated":"2016-05-12 03:12:32.000000000","message":"-, using in\n+for","commit_id":"9f8ff6a059f9fca206ebc6b417786fb548bcc37f"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"1c422a0a23371e18b82d97148b55979a39c4710a","unresolved":false,"context_lines":[{"line_number":287,"context_line":"**Shared VLAN implementation:**"},{"line_number":288,"context_line":""},{"line_number":289,"context_line":"For Shared VLAN, L2GW is not required. This is the most simplified cross pod"},{"line_number":290,"context_line":"L2 networking, using in limited scenario, for example, very limited number of"},{"line_number":291,"context_line":"network, VLAN are extended through physical gateway to support cross site VLAN"},{"line_number":292,"context_line":"networking, or all pods under same core switch with same visible VLAN ranges."},{"line_number":293,"context_line":""},{"line_number":294,"context_line":"A user creates network Net1, Tricircle plugin check the configuration, if"}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_452953e5","line":291,"range":{"start_line":290,"start_character":42,"end_line":291,"end_character":13},"updated":"2016-05-12 03:12:32.000000000","message":"For example, with a small number of networks, all VLANs","commit_id":"9f8ff6a059f9fca206ebc6b417786fb548bcc37f"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"1c422a0a23371e18b82d97148b55979a39c4710a","unresolved":false,"context_lines":[{"line_number":288,"context_line":""},{"line_number":289,"context_line":"For Shared VLAN, L2GW is not required. This is the most simplified cross pod"},{"line_number":290,"context_line":"L2 networking, using in limited scenario, for example, very limited number of"},{"line_number":291,"context_line":"network, VLAN are extended through physical gateway to support cross site VLAN"},{"line_number":292,"context_line":"networking, or all pods under same core switch with same visible VLAN ranges."},{"line_number":293,"context_line":""},{"line_number":294,"context_line":"A user creates network Net1, Tricircle plugin check the configuration, if"}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_a57e3fe1","line":291,"range":{"start_line":291,"start_character":35,"end_line":291,"end_character":51},"updated":"2016-05-12 03:12:32.000000000","message":"How many gateway are expected in this sentence?","commit_id":"9f8ff6a059f9fca206ebc6b417786fb548bcc37f"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"1c422a0a23371e18b82d97148b55979a39c4710a","unresolved":false,"context_lines":[{"line_number":289,"context_line":"For Shared VLAN, L2GW is not required. This is the most simplified cross pod"},{"line_number":290,"context_line":"L2 networking, using in limited scenario, for example, very limited number of"},{"line_number":291,"context_line":"network, VLAN are extended through physical gateway to support cross site VLAN"},{"line_number":292,"context_line":"networking, or all pods under same core switch with same visible VLAN ranges."},{"line_number":293,"context_line":""},{"line_number":294,"context_line":"A user creates network Net1, Tricircle plugin check the configuration, if"},{"line_number":295,"context_line":"``tenant_network_type`` equals “shared_vlan”, it will invoke shared VLAN type"}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_45579357","line":292,"range":{"start_line":292,"start_character":52,"end_line":292,"end_character":76},"updated":"2016-05-12 03:12:32.000000000","message":"Can you elaborate on this description a bit more?","commit_id":"9f8ff6a059f9fca206ebc6b417786fb548bcc37f"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"1c422a0a23371e18b82d97148b55979a39c4710a","unresolved":false,"context_lines":[{"line_number":291,"context_line":"network, VLAN are extended through physical gateway to support cross site VLAN"},{"line_number":292,"context_line":"networking, or all pods under same core switch with same visible VLAN ranges."},{"line_number":293,"context_line":""},{"line_number":294,"context_line":"A user creates network Net1, Tricircle plugin check the configuration, if"},{"line_number":295,"context_line":"``tenant_network_type`` equals “shared_vlan”, it will invoke shared VLAN type"},{"line_number":296,"context_line":"driver. Shared VLAN driver will allocate ``segment``, and assign"},{"line_number":297,"context_line":"``network_type`` with VLAN, and update network with ``segment`` and"}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_e5e96780","line":294,"range":{"start_line":294,"start_character":0,"end_line":294,"end_character":1},"updated":"2016-05-12 03:12:32.000000000","message":"-A\n+When a","commit_id":"9f8ff6a059f9fca206ebc6b417786fb548bcc37f"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"1c422a0a23371e18b82d97148b55979a39c4710a","unresolved":false,"context_lines":[{"line_number":291,"context_line":"network, VLAN are extended through physical gateway to support cross site VLAN"},{"line_number":292,"context_line":"networking, or all pods under same core switch with same visible VLAN ranges."},{"line_number":293,"context_line":""},{"line_number":294,"context_line":"A user creates network Net1, Tricircle plugin check the configuration, if"},{"line_number":295,"context_line":"``tenant_network_type`` equals “shared_vlan”, it will invoke shared VLAN type"},{"line_number":296,"context_line":"driver. Shared VLAN driver will allocate ``segment``, and assign"},{"line_number":297,"context_line":"``network_type`` with VLAN, and update network with ``segment`` and"}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_a5cc7f35","line":294,"range":{"start_line":294,"start_character":23,"end_line":294,"end_character":27},"updated":"2016-05-12 03:12:32.000000000","message":"-Net1\n+called Net1","commit_id":"9f8ff6a059f9fca206ebc6b417786fb548bcc37f"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"1c422a0a23371e18b82d97148b55979a39c4710a","unresolved":false,"context_lines":[{"line_number":291,"context_line":"network, VLAN are extended through physical gateway to support cross site VLAN"},{"line_number":292,"context_line":"networking, or all pods under same core switch with same visible VLAN ranges."},{"line_number":293,"context_line":""},{"line_number":294,"context_line":"A user creates network Net1, Tricircle plugin check the configuration, if"},{"line_number":295,"context_line":"``tenant_network_type`` equals “shared_vlan”, it will invoke shared VLAN type"},{"line_number":296,"context_line":"driver. Shared VLAN driver will allocate ``segment``, and assign"},{"line_number":297,"context_line":"``network_type`` with VLAN, and update network with ``segment`` and"}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_25d9aff3","line":294,"range":{"start_line":294,"start_character":29,"end_line":294,"end_character":38},"updated":"2016-05-12 03:12:32.000000000","message":"-Tricircle\n+the Tricircle","commit_id":"9f8ff6a059f9fca206ebc6b417786fb548bcc37f"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"1c422a0a23371e18b82d97148b55979a39c4710a","unresolved":false,"context_lines":[{"line_number":291,"context_line":"network, VLAN are extended through physical gateway to support cross site VLAN"},{"line_number":292,"context_line":"networking, or all pods under same core switch with same visible VLAN ranges."},{"line_number":293,"context_line":""},{"line_number":294,"context_line":"A user creates network Net1, Tricircle plugin check the configuration, if"},{"line_number":295,"context_line":"``tenant_network_type`` equals “shared_vlan”, it will invoke shared VLAN type"},{"line_number":296,"context_line":"driver. Shared VLAN driver will allocate ``segment``, and assign"},{"line_number":297,"context_line":"``network_type`` with VLAN, and update network with ``segment`` and"}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_65df37d6","line":294,"range":{"start_line":294,"start_character":46,"end_line":294,"end_character":51},"updated":"2016-05-12 03:12:32.000000000","message":"-check\n+checks","commit_id":"9f8ff6a059f9fca206ebc6b417786fb548bcc37f"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"1c422a0a23371e18b82d97148b55979a39c4710a","unresolved":false,"context_lines":[{"line_number":292,"context_line":"networking, or all pods under same core switch with same visible VLAN ranges."},{"line_number":293,"context_line":""},{"line_number":294,"context_line":"A user creates network Net1, Tricircle plugin check the configuration, if"},{"line_number":295,"context_line":"``tenant_network_type`` equals “shared_vlan”, it will invoke shared VLAN type"},{"line_number":296,"context_line":"driver. Shared VLAN driver will allocate ``segment``, and assign"},{"line_number":297,"context_line":"``network_type`` with VLAN, and update network with ``segment`` and"},{"line_number":298,"context_line":"``network_type`` and ``physical_network`` to DB."}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_25008f33","line":295,"range":{"start_line":295,"start_character":46,"end_line":295,"end_character":48},"updated":"2016-05-12 03:12:32.000000000","message":"What is \"it\"?","commit_id":"9f8ff6a059f9fca206ebc6b417786fb548bcc37f"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"1c422a0a23371e18b82d97148b55979a39c4710a","unresolved":false,"context_lines":[{"line_number":293,"context_line":""},{"line_number":294,"context_line":"A user creates network Net1, Tricircle plugin check the configuration, if"},{"line_number":295,"context_line":"``tenant_network_type`` equals “shared_vlan”, it will invoke shared VLAN type"},{"line_number":296,"context_line":"driver. Shared VLAN driver will allocate ``segment``, and assign"},{"line_number":297,"context_line":"``network_type`` with VLAN, and update network with ``segment`` and"},{"line_number":298,"context_line":"``network_type`` and ``physical_network`` to DB."},{"line_number":299,"context_line":""}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_2587efb5","line":296,"range":{"start_line":296,"start_character":32,"end_line":296,"end_character":40},"updated":"2016-05-12 03:12:32.000000000","message":"Maybe \"create\" is better in this context, I guess.\nWhat do you think?","commit_id":"9f8ff6a059f9fca206ebc6b417786fb548bcc37f"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"1c422a0a23371e18b82d97148b55979a39c4710a","unresolved":false,"context_lines":[{"line_number":294,"context_line":"A user creates network Net1, Tricircle plugin check the configuration, if"},{"line_number":295,"context_line":"``tenant_network_type`` equals “shared_vlan”, it will invoke shared VLAN type"},{"line_number":296,"context_line":"driver. Shared VLAN driver will allocate ``segment``, and assign"},{"line_number":297,"context_line":"``network_type`` with VLAN, and update network with ``segment`` and"},{"line_number":298,"context_line":"``network_type`` and ``physical_network`` to DB."},{"line_number":299,"context_line":""},{"line_number":300,"context_line":"A user creates VM1 in AZ1, and connects it to network Net1. If VM will be"}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_a54f5f90","line":297,"range":{"start_line":297,"start_character":32,"end_line":297,"end_character":38},"updated":"2016-05-12 03:12:32.000000000","message":"Where does this \"update\" happen?","commit_id":"9f8ff6a059f9fca206ebc6b417786fb548bcc37f"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"1c422a0a23371e18b82d97148b55979a39c4710a","unresolved":false,"context_lines":[{"line_number":294,"context_line":"A user creates network Net1, Tricircle plugin check the configuration, if"},{"line_number":295,"context_line":"``tenant_network_type`` equals “shared_vlan”, it will invoke shared VLAN type"},{"line_number":296,"context_line":"driver. Shared VLAN driver will allocate ``segment``, and assign"},{"line_number":297,"context_line":"``network_type`` with VLAN, and update network with ``segment`` and"},{"line_number":298,"context_line":"``network_type`` and ``physical_network`` to DB."},{"line_number":299,"context_line":""},{"line_number":300,"context_line":"A user creates VM1 in AZ1, and connects it to network Net1. If VM will be"},{"line_number":301,"context_line":"booted in POD1, ``Nova API-GW`` needs to get the network"}],"source_content_type":"text/x-rst","patch_set":9,"id":"dab17558_25752fca","line":298,"range":{"start_line":297,"start_character":32,"end_line":298,"end_character":48},"updated":"2016-05-12 03:12:32.000000000","message":"update ``segment`` and ``network_type`` and ``physical_network`` in DB.","commit_id":"9f8ff6a059f9fca206ebc6b417786fb548bcc37f"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"7c11728e249930b471f6ce4e3b6b066e1656d82f","unresolved":false,"context_lines":[{"line_number":20,"context_line":"* Admin API"},{"line_number":21,"context_line":"* XJob"},{"line_number":22,"context_line":"* DB"},{"line_number":23,"context_line":""},{"line_number":24,"context_line":"Please refer to the Tricircle design blueprint[1], especially from"},{"line_number":25,"context_line":"\u00277. Stateless Architecture Proposal\u0027 for the detail description of each"},{"line_number":26,"context_line":"components."}],"source_content_type":"text/x-rst","patch_set":11,"id":"dab17558_131755ee","line":23,"range":{"start_line":23,"start_character":0,"end_line":23,"end_character":0},"updated":"2016-05-13 06:49:21.000000000","message":"Add some short summary of these components here: Nova APIGW is the networking automation trigger for Nova APIGW is able to know exactly when a new VM is being provisioned, and then Neutron Tricircle plug-in is responsible for cross OpenStack L2/L3 networking immediately for the new provisioned VM. Cinder APIGW and Nova APIGW will make sure the volumes for the same VM will co-locate in same OpenStack instances.","commit_id":"20d60dc7f364139ead141038e610964c7f6313da"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"2216b04dc88b6f5d96d9c1348af84cf8c0b93954","unresolved":false,"context_lines":[{"line_number":271,"context_line":"networking is required."},{"line_number":272,"context_line":""},{"line_number":273,"context_line":"A user creates network Net1 with single AZ1 in az_hint, the Tricircle plugin"},{"line_number":274,"context_line":"checks the configuration, if ``tenant_network_type`` equals ``lcoal_network``,"},{"line_number":275,"context_line":"it will invoke Local Network type driver. Local_Network driver under the"},{"line_number":276,"context_line":"Tricircle plugin will update network with ``network_type`` to DB."},{"line_number":277,"context_line":""}],"source_content_type":"text/x-rst","patch_set":11,"id":"dab17558_d32e96f9","line":274,"range":{"start_line":274,"start_character":60,"end_line":274,"end_character":76},"updated":"2016-05-12 12:39:52.000000000","message":"``local_network``","commit_id":"20d60dc7f364139ead141038e610964c7f6313da"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"aa179670c513a8042952b8c6f5efe36c6eb760dd","unresolved":false,"context_lines":[{"line_number":4,"context_line":""},{"line_number":5,"context_line":"Background"},{"line_number":6,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":7,"context_line":"Tricircle provides an OpenStack API gateway and networking automation to allow"},{"line_number":8,"context_line":"multiple OpenStack instances, spanning in one site or multiple sites, to be"},{"line_number":9,"context_line":"managed as a single OpenStack cloud."},{"line_number":10,"context_line":""}],"source_content_type":"text/x-rst","patch_set":12,"id":"dab17558_b33c56c0","line":7,"range":{"start_line":7,"start_character":0,"end_line":7,"end_character":9},"updated":"2016-05-14 04:58:09.000000000","message":"The Tricircle","commit_id":"d072a51488c3755bc43a893a823f39f6c01780a4"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"2a1793bf3b818a426d69eee0e41bfa8bb1477642","unresolved":false,"context_lines":[{"line_number":4,"context_line":""},{"line_number":5,"context_line":"Background"},{"line_number":6,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":7,"context_line":"Tricircle provides an OpenStack API gateway and networking automation to allow"},{"line_number":8,"context_line":"multiple OpenStack instances, spanning in one site or multiple sites, to be"},{"line_number":9,"context_line":"managed as a single OpenStack cloud."},{"line_number":10,"context_line":""}],"source_content_type":"text/x-rst","patch_set":12,"id":"dab17558_19f3c19f","line":7,"range":{"start_line":7,"start_character":0,"end_line":7,"end_character":9},"in_reply_to":"dab17558_b33c56c0","updated":"2016-05-14 09:35:10.000000000","message":"Done","commit_id":"d072a51488c3755bc43a893a823f39f6c01780a4"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"aa179670c513a8042952b8c6f5efe36c6eb760dd","unresolved":false,"context_lines":[{"line_number":5,"context_line":"Background"},{"line_number":6,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":7,"context_line":"Tricircle provides an OpenStack API gateway and networking automation to allow"},{"line_number":8,"context_line":"multiple OpenStack instances, spanning in one site or multiple sites, to be"},{"line_number":9,"context_line":"managed as a single OpenStack cloud."},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"Each bottom OpenStack which is managed by Tricircle is also called a pod in"}],"source_content_type":"text/x-rst","patch_set":12,"id":"dab17558_936e72c7","line":8,"range":{"start_line":8,"start_character":28,"end_line":8,"end_character":38},"updated":"2016-05-14 04:58:09.000000000","message":"running","commit_id":"d072a51488c3755bc43a893a823f39f6c01780a4"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"2a1793bf3b818a426d69eee0e41bfa8bb1477642","unresolved":false,"context_lines":[{"line_number":5,"context_line":"Background"},{"line_number":6,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":7,"context_line":"Tricircle provides an OpenStack API gateway and networking automation to allow"},{"line_number":8,"context_line":"multiple OpenStack instances, spanning in one site or multiple sites, to be"},{"line_number":9,"context_line":"managed as a single OpenStack cloud."},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"Each bottom OpenStack which is managed by Tricircle is also called a pod in"}],"source_content_type":"text/x-rst","patch_set":12,"id":"dab17558_592b89eb","line":8,"range":{"start_line":8,"start_character":28,"end_line":8,"end_character":38},"in_reply_to":"dab17558_936e72c7","updated":"2016-05-14 09:35:10.000000000","message":"Done","commit_id":"d072a51488c3755bc43a893a823f39f6c01780a4"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"aa179670c513a8042952b8c6f5efe36c6eb760dd","unresolved":false,"context_lines":[{"line_number":8,"context_line":"multiple OpenStack instances, spanning in one site or multiple sites, to be"},{"line_number":9,"context_line":"managed as a single OpenStack cloud."},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"Each bottom OpenStack which is managed by Tricircle is also called a pod in"},{"line_number":12,"context_line":"short. So cross pod L2 networking is the same meaning of cross OpenStack L2"},{"line_number":13,"context_line":""},{"line_number":14,"context_line":""}],"source_content_type":"text/x-rst","patch_set":12,"id":"dab17558_d368fabc","line":11,"range":{"start_line":11,"start_character":42,"end_line":11,"end_character":51},"updated":"2016-05-14 04:58:09.000000000","message":"the Tricircle","commit_id":"d072a51488c3755bc43a893a823f39f6c01780a4"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"2a1793bf3b818a426d69eee0e41bfa8bb1477642","unresolved":false,"context_lines":[{"line_number":8,"context_line":"multiple OpenStack instances, spanning in one site or multiple sites, to be"},{"line_number":9,"context_line":"managed as a single OpenStack cloud."},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"Each bottom OpenStack which is managed by Tricircle is also called a pod in"},{"line_number":12,"context_line":"short. So cross pod L2 networking is the same meaning of cross OpenStack L2"},{"line_number":13,"context_line":""},{"line_number":14,"context_line":""}],"source_content_type":"text/x-rst","patch_set":12,"id":"dab17558_392e85fa","line":11,"range":{"start_line":11,"start_character":42,"end_line":11,"end_character":51},"in_reply_to":"dab17558_d368fabc","updated":"2016-05-14 09:35:10.000000000","message":"Done","commit_id":"d072a51488c3755bc43a893a823f39f6c01780a4"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"aa179670c513a8042952b8c6f5efe36c6eb760dd","unresolved":false,"context_lines":[{"line_number":8,"context_line":"multiple OpenStack instances, spanning in one site or multiple sites, to be"},{"line_number":9,"context_line":"managed as a single OpenStack cloud."},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"Each bottom OpenStack which is managed by Tricircle is also called a pod in"},{"line_number":12,"context_line":"short. So cross pod L2 networking is the same meaning of cross OpenStack L2"},{"line_number":13,"context_line":""},{"line_number":14,"context_line":""},{"line_number":15,"context_line":"Tricircle includes componenents as following:"}],"source_content_type":"text/x-rst","patch_set":12,"id":"dab17558_339ea6b8","line":12,"range":{"start_line":11,"start_character":72,"end_line":12,"end_character":5},"updated":"2016-05-14 04:58:09.000000000","message":"Please delete.","commit_id":"d072a51488c3755bc43a893a823f39f6c01780a4"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"aa179670c513a8042952b8c6f5efe36c6eb760dd","unresolved":false,"context_lines":[{"line_number":9,"context_line":"managed as a single OpenStack cloud."},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"Each bottom OpenStack which is managed by Tricircle is also called a pod in"},{"line_number":12,"context_line":"short. So cross pod L2 networking is the same meaning of cross OpenStack L2"},{"line_number":13,"context_line":""},{"line_number":14,"context_line":""},{"line_number":15,"context_line":"Tricircle includes componenents as following:"}],"source_content_type":"text/x-rst","patch_set":12,"id":"dab17558_b36d769b","line":12,"range":{"start_line":12,"start_character":7,"end_line":12,"end_character":75},"updated":"2016-05-14 04:58:09.000000000","message":"There is no relationship between this sentence and before.\nLet\u0027s define what \"cross pod l2 networking\" is first.\n\nAfter that, we can say, \"cross pod L2 networking is the same meanings of cross OpenStack L2\"\n\nBut I think that this sentence could confuse readers.\n\nWhat do you think?","commit_id":"d072a51488c3755bc43a893a823f39f6c01780a4"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"2a1793bf3b818a426d69eee0e41bfa8bb1477642","unresolved":false,"context_lines":[{"line_number":9,"context_line":"managed as a single OpenStack cloud."},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"Each bottom OpenStack which is managed by Tricircle is also called a pod in"},{"line_number":12,"context_line":"short. So cross pod L2 networking is the same meaning of cross OpenStack L2"},{"line_number":13,"context_line":""},{"line_number":14,"context_line":""},{"line_number":15,"context_line":"Tricircle includes componenents as following:"}],"source_content_type":"text/x-rst","patch_set":12,"id":"dab17558_3915e59a","line":12,"range":{"start_line":12,"start_character":7,"end_line":12,"end_character":75},"in_reply_to":"dab17558_b36d769b","updated":"2016-05-14 09:35:10.000000000","message":"I think we should delete this sentence","commit_id":"d072a51488c3755bc43a893a823f39f6c01780a4"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"aa179670c513a8042952b8c6f5efe36c6eb760dd","unresolved":false,"context_lines":[{"line_number":12,"context_line":"short. So cross pod L2 networking is the same meaning of cross OpenStack L2"},{"line_number":13,"context_line":""},{"line_number":14,"context_line":""},{"line_number":15,"context_line":"Tricircle includes componenents as following:"},{"line_number":16,"context_line":""},{"line_number":17,"context_line":"* Nova API-GW"},{"line_number":18,"context_line":"* Cinder API-GW"}],"source_content_type":"text/x-rst","patch_set":12,"id":"dab17558_53052ac0","line":15,"range":{"start_line":15,"start_character":0,"end_line":15,"end_character":45},"updated":"2016-05-14 04:58:09.000000000","message":"The Tricircle has the following components.","commit_id":"d072a51488c3755bc43a893a823f39f6c01780a4"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"aa179670c513a8042952b8c6f5efe36c6eb760dd","unresolved":false,"context_lines":[{"line_number":21,"context_line":"* XJob"},{"line_number":22,"context_line":"* DB"},{"line_number":23,"context_line":""},{"line_number":24,"context_line":"Nova APIGW is the networking automation trigger for Nova APIGW is able to know"},{"line_number":25,"context_line":"exactly when a new VM is being provisioned, and then Neutron Tricircle plug-in"},{"line_number":26,"context_line":"is responsible for cross OpenStack L2/L3 networking immediately for the new"},{"line_number":27,"context_line":"provisioned VM. Cinder APIGW and Nova APIGW will make sure the volumes for the"},{"line_number":28,"context_line":"same VM will co-locate in same OpenStack instances."}],"source_content_type":"text/x-rst","patch_set":12,"id":"dab17558_f3153ee5","line":25,"range":{"start_line":24,"start_character":0,"end_line":25,"end_character":43},"updated":"2016-05-14 04:58:09.000000000","message":"Nova APIGW is the functionality to trigger automatic networking creation when new VMs are being provisioned.","commit_id":"d072a51488c3755bc43a893a823f39f6c01780a4"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"2a1793bf3b818a426d69eee0e41bfa8bb1477642","unresolved":false,"context_lines":[{"line_number":21,"context_line":"* XJob"},{"line_number":22,"context_line":"* DB"},{"line_number":23,"context_line":""},{"line_number":24,"context_line":"Nova APIGW is the networking automation trigger for Nova APIGW is able to know"},{"line_number":25,"context_line":"exactly when a new VM is being provisioned, and then Neutron Tricircle plug-in"},{"line_number":26,"context_line":"is responsible for cross OpenStack L2/L3 networking immediately for the new"},{"line_number":27,"context_line":"provisioned VM. Cinder APIGW and Nova APIGW will make sure the volumes for the"},{"line_number":28,"context_line":"same VM will co-locate in same OpenStack instances."}],"source_content_type":"text/x-rst","patch_set":12,"id":"dab17558_790f6d88","line":25,"range":{"start_line":24,"start_character":0,"end_line":25,"end_character":43},"in_reply_to":"dab17558_f3153ee5","updated":"2016-05-14 09:35:10.000000000","message":"Done","commit_id":"d072a51488c3755bc43a893a823f39f6c01780a4"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"aa179670c513a8042952b8c6f5efe36c6eb760dd","unresolved":false,"context_lines":[{"line_number":22,"context_line":"* DB"},{"line_number":23,"context_line":""},{"line_number":24,"context_line":"Nova APIGW is the networking automation trigger for Nova APIGW is able to know"},{"line_number":25,"context_line":"exactly when a new VM is being provisioned, and then Neutron Tricircle plug-in"},{"line_number":26,"context_line":"is responsible for cross OpenStack L2/L3 networking immediately for the new"},{"line_number":27,"context_line":"provisioned VM. Cinder APIGW and Nova APIGW will make sure the volumes for the"},{"line_number":28,"context_line":"same VM will co-locate in same OpenStack instances."},{"line_number":29,"context_line":""},{"line_number":30,"context_line":"Please refer to the Tricircle design blueprint[1], especially from"}],"source_content_type":"text/x-rst","patch_set":12,"id":"dab17558_13f282d2","line":27,"range":{"start_line":25,"start_character":44,"end_line":27,"end_character":15},"updated":"2016-05-14 04:58:09.000000000","message":"Neutron Tricircle plug-in is the functionality to create cross OpenStack L2/L3 networking for new VMs.","commit_id":"d072a51488c3755bc43a893a823f39f6c01780a4"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"2a1793bf3b818a426d69eee0e41bfa8bb1477642","unresolved":false,"context_lines":[{"line_number":22,"context_line":"* DB"},{"line_number":23,"context_line":""},{"line_number":24,"context_line":"Nova APIGW is the networking automation trigger for Nova APIGW is able to know"},{"line_number":25,"context_line":"exactly when a new VM is being provisioned, and then Neutron Tricircle plug-in"},{"line_number":26,"context_line":"is responsible for cross OpenStack L2/L3 networking immediately for the new"},{"line_number":27,"context_line":"provisioned VM. Cinder APIGW and Nova APIGW will make sure the volumes for the"},{"line_number":28,"context_line":"same VM will co-locate in same OpenStack instances."},{"line_number":29,"context_line":""},{"line_number":30,"context_line":"Please refer to the Tricircle design blueprint[1], especially from"}],"source_content_type":"text/x-rst","patch_set":12,"id":"dab17558_d9265915","line":27,"range":{"start_line":25,"start_character":44,"end_line":27,"end_character":15},"in_reply_to":"dab17558_13f282d2","updated":"2016-05-14 09:35:10.000000000","message":"Done","commit_id":"d072a51488c3755bc43a893a823f39f6c01780a4"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"aa179670c513a8042952b8c6f5efe36c6eb760dd","unresolved":false,"context_lines":[{"line_number":24,"context_line":"Nova APIGW is the networking automation trigger for Nova APIGW is able to know"},{"line_number":25,"context_line":"exactly when a new VM is being provisioned, and then Neutron Tricircle plug-in"},{"line_number":26,"context_line":"is responsible for cross OpenStack L2/L3 networking immediately for the new"},{"line_number":27,"context_line":"provisioned VM. Cinder APIGW and Nova APIGW will make sure the volumes for the"},{"line_number":28,"context_line":"same VM will co-locate in same OpenStack instances."},{"line_number":29,"context_line":""},{"line_number":30,"context_line":"Please refer to the Tricircle design blueprint[1], especially from"},{"line_number":31,"context_line":"\u00277. Stateless Architecture Proposal\u0027 for the detail description of each"}],"source_content_type":"text/x-rst","patch_set":12,"id":"dab17558_93b4b2f2","line":28,"range":{"start_line":27,"start_character":16,"end_line":28,"end_character":51},"updated":"2016-05-14 04:58:09.000000000","message":"Please modify this sentence properly with considering before sentences, Nova APIGW and Neutron Tricircle plug-in.\n\nPlease refer to blueprint for proper modification.\n\nhttps://docs.google.com/document/d/18kZZ1snMOCD9IQvUKI5NVDzSASpw-QKj7l2zNqMEd3g/edit#\n\nI think that you are getting better understandings, which is great progress for us!!","commit_id":"d072a51488c3755bc43a893a823f39f6c01780a4"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"2a1793bf3b818a426d69eee0e41bfa8bb1477642","unresolved":false,"context_lines":[{"line_number":24,"context_line":"Nova APIGW is the networking automation trigger for Nova APIGW is able to know"},{"line_number":25,"context_line":"exactly when a new VM is being provisioned, and then Neutron Tricircle plug-in"},{"line_number":26,"context_line":"is responsible for cross OpenStack L2/L3 networking immediately for the new"},{"line_number":27,"context_line":"provisioned VM. Cinder APIGW and Nova APIGW will make sure the volumes for the"},{"line_number":28,"context_line":"same VM will co-locate in same OpenStack instances."},{"line_number":29,"context_line":""},{"line_number":30,"context_line":"Please refer to the Tricircle design blueprint[1], especially from"},{"line_number":31,"context_line":"\u00277. Stateless Architecture Proposal\u0027 for the detail description of each"}],"source_content_type":"text/x-rst","patch_set":12,"id":"dab17558_b9f3959e","line":28,"range":{"start_line":27,"start_character":16,"end_line":28,"end_character":51},"in_reply_to":"dab17558_93b4b2f2","updated":"2016-05-14 09:35:10.000000000","message":"Can we describe this sentence like this \"Cinder APIGW and Nova APIGW route the cinder or nova api request to appropriate bottom OpenStack according to tenant ID and pod binding.\"?","commit_id":"d072a51488c3755bc43a893a823f39f6c01780a4"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"18479a219928189485ea15816df1252a69cb757b","unresolved":false,"context_lines":[{"line_number":24,"context_line":"Nova APIGW is the networking automation trigger for Nova APIGW is able to know"},{"line_number":25,"context_line":"exactly when a new VM is being provisioned, and then Neutron Tricircle plug-in"},{"line_number":26,"context_line":"is responsible for cross OpenStack L2/L3 networking immediately for the new"},{"line_number":27,"context_line":"provisioned VM. Cinder APIGW and Nova APIGW will make sure the volumes for the"},{"line_number":28,"context_line":"same VM will co-locate in same OpenStack instances."},{"line_number":29,"context_line":""},{"line_number":30,"context_line":"Please refer to the Tricircle design blueprint[1], especially from"},{"line_number":31,"context_line":"\u00277. Stateless Architecture Proposal\u0027 for the detail description of each"}],"source_content_type":"text/x-rst","patch_set":12,"id":"dab17558_f9019d07","line":28,"range":{"start_line":27,"start_character":16,"end_line":28,"end_character":51},"in_reply_to":"dab17558_b9f3959e","updated":"2016-05-14 09:55:20.000000000","message":"Good question!\nWhy do you think:\n\n\"request to appropriate bottom instance\"\n  depends on\n\"tenant id and pod binding\"?\n\n---\n\"according to\" almost equals to \"based on\".\n\"based on\" equals to \" depend on\".\n---","commit_id":"d072a51488c3755bc43a893a823f39f6c01780a4"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"c8bf82c163acf1ee84b3ab78042e31924032273f","unresolved":false,"context_lines":[{"line_number":24,"context_line":"Nova APIGW is the networking automation trigger for Nova APIGW is able to know"},{"line_number":25,"context_line":"exactly when a new VM is being provisioned, and then Neutron Tricircle plug-in"},{"line_number":26,"context_line":"is responsible for cross OpenStack L2/L3 networking immediately for the new"},{"line_number":27,"context_line":"provisioned VM. Cinder APIGW and Nova APIGW will make sure the volumes for the"},{"line_number":28,"context_line":"same VM will co-locate in same OpenStack instances."},{"line_number":29,"context_line":""},{"line_number":30,"context_line":"Please refer to the Tricircle design blueprint[1], especially from"},{"line_number":31,"context_line":"\u00277. Stateless Architecture Proposal\u0027 for the detail description of each"}],"source_content_type":"text/x-rst","patch_set":12,"id":"dab17558_bcf423cf","line":28,"range":{"start_line":27,"start_character":16,"end_line":28,"end_character":51},"in_reply_to":"dab17558_bc91c39c","updated":"2016-05-14 10:41:56.000000000","message":"In theory, you\u0027re right. We can move forward to next step with you, I think.","commit_id":"d072a51488c3755bc43a893a823f39f6c01780a4"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"70c949cfbe136b4db28582fecb748798b3b3d2f8","unresolved":false,"context_lines":[{"line_number":24,"context_line":"Nova APIGW is the networking automation trigger for Nova APIGW is able to know"},{"line_number":25,"context_line":"exactly when a new VM is being provisioned, and then Neutron Tricircle plug-in"},{"line_number":26,"context_line":"is responsible for cross OpenStack L2/L3 networking immediately for the new"},{"line_number":27,"context_line":"provisioned VM. Cinder APIGW and Nova APIGW will make sure the volumes for the"},{"line_number":28,"context_line":"same VM will co-locate in same OpenStack instances."},{"line_number":29,"context_line":""},{"line_number":30,"context_line":"Please refer to the Tricircle design blueprint[1], especially from"},{"line_number":31,"context_line":"\u00277. Stateless Architecture Proposal\u0027 for the detail description of each"}],"source_content_type":"text/x-rst","patch_set":12,"id":"dab17558_bc91c39c","line":28,"range":{"start_line":27,"start_character":16,"end_line":28,"end_character":51},"in_reply_to":"dab17558_f9019d07","updated":"2016-05-14 10:19:08.000000000","message":"My understanding is ：If more than one pod in one Availability Zone, the direction of request will depend on the tenant ID and pod binding. And L2 networking can connect the VMs and volumes in one Zone. \n---\nSo this sentence can be describe like this ：After the Tricircle achieved the tenant ID and completed the pod binding. Cinder APIGW and Nova APIGW will route the cinder api or nova api request to appropriate bottom OpenStack.\n\nWhat do you think?","commit_id":"d072a51488c3755bc43a893a823f39f6c01780a4"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"aa179670c513a8042952b8c6f5efe36c6eb760dd","unresolved":false,"context_lines":[{"line_number":273,"context_line":""},{"line_number":274,"context_line":"**Local Network Implementation:**"},{"line_number":275,"context_line":""},{"line_number":276,"context_line":"For Local Network, L2GW is not required. In this scenario, no cross pod L2/L3"},{"line_number":277,"context_line":"networking is required."},{"line_number":278,"context_line":""},{"line_number":279,"context_line":"A user creates network Net1 with single AZ1 in az_hint, the Tricircle plugin"},{"line_number":280,"context_line":"checks the configuration, if ``tenant_network_type`` equals ``local_network``,"}],"source_content_type":"text/x-rst","patch_set":12,"id":"dab17558_02786fc3","line":277,"range":{"start_line":276,"start_character":72,"end_line":277,"end_character":10},"updated":"2016-05-14 04:58:09.000000000","message":"How do we define ``L2 networking`` in this context. Does it mean L2GW?\n\nIt may be better for us to be careful a bit more regarding to ``L2 networking`` since no ``L2 networking`` means no ip address.\n\nWhat do you think?","commit_id":"d072a51488c3755bc43a893a823f39f6c01780a4"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"2a1793bf3b818a426d69eee0e41bfa8bb1477642","unresolved":false,"context_lines":[{"line_number":273,"context_line":""},{"line_number":274,"context_line":"**Local Network Implementation:**"},{"line_number":275,"context_line":""},{"line_number":276,"context_line":"For Local Network, L2GW is not required. In this scenario, no cross pod L2/L3"},{"line_number":277,"context_line":"networking is required."},{"line_number":278,"context_line":""},{"line_number":279,"context_line":"A user creates network Net1 with single AZ1 in az_hint, the Tricircle plugin"},{"line_number":280,"context_line":"checks the configuration, if ``tenant_network_type`` equals ``local_network``,"}],"source_content_type":"text/x-rst","patch_set":12,"id":"dab17558_f9f7dd56","line":277,"range":{"start_line":276,"start_character":72,"end_line":277,"end_character":10},"in_reply_to":"dab17558_02786fc3","updated":"2016-05-14 09:35:10.000000000","message":"Should we delete this sentence \"no cross pod L2/L3 networking is required\"?","commit_id":"d072a51488c3755bc43a893a823f39f6c01780a4"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"aa179670c513a8042952b8c6f5efe36c6eb760dd","unresolved":false,"context_lines":[{"line_number":314,"context_line":"send create network message to POD2. Create network message includes"},{"line_number":315,"context_line":"``network_type`` and ``segment`` and ``physical_network``."},{"line_number":316,"context_line":""},{"line_number":317,"context_line":"**Shared VxLAN implementation:**"},{"line_number":318,"context_line":""},{"line_number":319,"context_line":"A user creates network Net1, Tricircle plugin check the configuration, if"},{"line_number":320,"context_line":"``tenant_network_type`` equals “shared_vxlan”, it will invoke shared VxLAN"}],"source_content_type":"text/x-rst","patch_set":12,"id":"dab17558_02034f43","line":317,"range":{"start_line":317,"start_character":15,"end_line":317,"end_character":29},"updated":"2016-05-14 04:58:09.000000000","message":"-implementation\n+Implementation","commit_id":"d072a51488c3755bc43a893a823f39f6c01780a4"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"2a1793bf3b818a426d69eee0e41bfa8bb1477642","unresolved":false,"context_lines":[{"line_number":314,"context_line":"send create network message to POD2. Create network message includes"},{"line_number":315,"context_line":"``network_type`` and ``segment`` and ``physical_network``."},{"line_number":316,"context_line":""},{"line_number":317,"context_line":"**Shared VxLAN implementation:**"},{"line_number":318,"context_line":""},{"line_number":319,"context_line":"A user creates network Net1, Tricircle plugin check the configuration, if"},{"line_number":320,"context_line":"``tenant_network_type`` equals “shared_vxlan”, it will invoke shared VxLAN"}],"source_content_type":"text/x-rst","patch_set":12,"id":"dab17558_3998451b","line":317,"range":{"start_line":317,"start_character":15,"end_line":317,"end_character":29},"in_reply_to":"dab17558_02034f43","updated":"2016-05-14 09:35:10.000000000","message":"Done","commit_id":"d072a51488c3755bc43a893a823f39f6c01780a4"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"576c76cb0849052ebc1d8d9ed94cbb1d8ef97358","unresolved":false,"context_lines":[{"line_number":4,"context_line":""},{"line_number":5,"context_line":"Background"},{"line_number":6,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":7,"context_line":"The Tricircle provides an OpenStack API gateway and networking automation to"},{"line_number":8,"context_line":"allow multiple OpenStack instances running in one site or multiple sites, to"},{"line_number":9,"context_line":"be managed as a single OpenStack cloud."},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"Each bottom OpenStack which is managed by the Tricircle is also called a pod"},{"line_number":12,"context_line":"in short. "}],"source_content_type":"text/x-rst","patch_set":13,"id":"dab17558_df46344e","line":9,"range":{"start_line":7,"start_character":0,"end_line":9,"end_character":39},"updated":"2016-05-15 03:57:05.000000000","message":"From my point of view, this sentence is really really important. Because every single concept is compressed in this sentence. And it\u0027s going to be perfect because of you!\n\nSince that, I would like to devide this sentence into two sentences with more words.\n\n------------\n1st sentence\n------------\nThe Tricircle provides unified OpenStack API gateway and networking automation functionality.\n\n------------\n2nd sentence\n------------\nThose main functionalities allow cloud operators to manage multiple OpenStack instances which are running in one site or multiple sites as a single OpenStack cloud.\n\n\nThere will be more enhanced functionalities which I\u0027m thinking of in the future.\n\nBut the basic concept of this project will never be changed.","commit_id":"3d9f8469aaf229397d54eae34a3b70db095feeb3"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"576c76cb0849052ebc1d8d9ed94cbb1d8ef97358","unresolved":false,"context_lines":[{"line_number":9,"context_line":"be managed as a single OpenStack cloud."},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"Each bottom OpenStack which is managed by the Tricircle is also called a pod"},{"line_number":12,"context_line":"in short. "},{"line_number":13,"context_line":""},{"line_number":14,"context_line":"The Tricircle has the following components:"},{"line_number":15,"context_line":""}],"source_content_type":"text/x-rst","patch_set":13,"id":"dab17558_5f0c043b","line":12,"range":{"start_line":12,"start_character":0,"end_line":12,"end_character":8},"updated":"2016-05-15 03:57:05.000000000","message":"\"in short\" is not necessary.","commit_id":"3d9f8469aaf229397d54eae34a3b70db095feeb3"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"576c76cb0849052ebc1d8d9ed94cbb1d8ef97358","unresolved":false,"context_lines":[{"line_number":21,"context_line":"* DB"},{"line_number":22,"context_line":""},{"line_number":23,"context_line":"Nova APIGW is the functionality to trigger automatic networking creation when"},{"line_number":24,"context_line":"new VMs are being provisioned.Neutron Tricircle plug-in is the functionality"},{"line_number":25,"context_line":"to create cross OpenStack L2/L3 networking for new VMs. After the Tricircle"},{"line_number":26,"context_line":"achieved the tenant ID and completed the pod binding. Cinder APIGW and Nova"},{"line_number":27,"context_line":"APIGW will route the cinder api or nova api request to appropriate bottom"}],"source_content_type":"text/x-rst","patch_set":13,"id":"dab17558_bf13705b","line":24,"range":{"start_line":24,"start_character":18,"end_line":24,"end_character":37},"updated":"2016-05-15 03:57:05.000000000","message":"-provisioned.Neutron\n+provisioned. Neutron","commit_id":"3d9f8469aaf229397d54eae34a3b70db095feeb3"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"576c76cb0849052ebc1d8d9ed94cbb1d8ef97358","unresolved":false,"context_lines":[{"line_number":23,"context_line":"Nova APIGW is the functionality to trigger automatic networking creation when"},{"line_number":24,"context_line":"new VMs are being provisioned.Neutron Tricircle plug-in is the functionality"},{"line_number":25,"context_line":"to create cross OpenStack L2/L3 networking for new VMs. After the Tricircle"},{"line_number":26,"context_line":"achieved the tenant ID and completed the pod binding. Cinder APIGW and Nova"},{"line_number":27,"context_line":"APIGW will route the cinder api or nova api request to appropriate bottom"},{"line_number":28,"context_line":"OpenStack."},{"line_number":29,"context_line":""}],"source_content_type":"text/x-rst","patch_set":13,"id":"dab17558_df18f477","line":26,"range":{"start_line":26,"start_character":0,"end_line":26,"end_character":8},"updated":"2016-05-15 03:57:05.000000000","message":"-achieved\n+create","commit_id":"3d9f8469aaf229397d54eae34a3b70db095feeb3"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"576c76cb0849052ebc1d8d9ed94cbb1d8ef97358","unresolved":false,"context_lines":[{"line_number":23,"context_line":"Nova APIGW is the functionality to trigger automatic networking creation when"},{"line_number":24,"context_line":"new VMs are being provisioned.Neutron Tricircle plug-in is the functionality"},{"line_number":25,"context_line":"to create cross OpenStack L2/L3 networking for new VMs. After the Tricircle"},{"line_number":26,"context_line":"achieved the tenant ID and completed the pod binding. Cinder APIGW and Nova"},{"line_number":27,"context_line":"APIGW will route the cinder api or nova api request to appropriate bottom"},{"line_number":28,"context_line":"OpenStack."},{"line_number":29,"context_line":""}],"source_content_type":"text/x-rst","patch_set":13,"id":"dab17558_3f2660ba","line":26,"range":{"start_line":26,"start_character":27,"end_line":26,"end_character":36},"updated":"2016-05-15 03:57:05.000000000","message":"-completed\n+complete","commit_id":"3d9f8469aaf229397d54eae34a3b70db095feeb3"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"576c76cb0849052ebc1d8d9ed94cbb1d8ef97358","unresolved":false,"context_lines":[{"line_number":24,"context_line":"new VMs are being provisioned.Neutron Tricircle plug-in is the functionality"},{"line_number":25,"context_line":"to create cross OpenStack L2/L3 networking for new VMs. After the Tricircle"},{"line_number":26,"context_line":"achieved the tenant ID and completed the pod binding. Cinder APIGW and Nova"},{"line_number":27,"context_line":"APIGW will route the cinder api or nova api request to appropriate bottom"},{"line_number":28,"context_line":"OpenStack."},{"line_number":29,"context_line":""},{"line_number":30,"context_line":"Please refer to the Tricircle design blueprint[1], especially from"}],"source_content_type":"text/x-rst","patch_set":13,"id":"dab17558_5f2364a7","line":27,"range":{"start_line":27,"start_character":11,"end_line":27,"end_character":16},"updated":"2016-05-15 03:57:05.000000000","message":"I think that \"pass\" is a bit more appropreate.\nWhat do you think?","commit_id":"3d9f8469aaf229397d54eae34a3b70db095feeb3"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"ef11fff2aca9c66a73eacdb2605b5b5ba837b7c9","unresolved":false,"context_lines":[{"line_number":34,"context_line":""},{"line_number":35,"context_line":"Problem Description"},{"line_number":36,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":37,"context_line":"When an user wants to create a network in Neutron API Server, the user can"},{"line_number":38,"context_line":"specify the \u0027availability_zone_hints\u0027(AZ or az will be used for short for"},{"line_number":39,"context_line":"availability zone) in network creation, in Tricircle, the \u0027az_hints\u0027 means"},{"line_number":40,"context_line":"which AZ the network should be spreaded into. It\u0027s a little different"}],"source_content_type":"text/x-rst","patch_set":13,"id":"dab17558_e7528634","line":37,"range":{"start_line":37,"start_character":62,"end_line":37,"end_character":70},"updated":"2016-05-15 23:29:34.000000000","message":"-the user\n+a user","commit_id":"3d9f8469aaf229397d54eae34a3b70db095feeb3"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"ef11fff2aca9c66a73eacdb2605b5b5ba837b7c9","unresolved":false,"context_lines":[{"line_number":35,"context_line":"Problem Description"},{"line_number":36,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":37,"context_line":"When an user wants to create a network in Neutron API Server, the user can"},{"line_number":38,"context_line":"specify the \u0027availability_zone_hints\u0027(AZ or az will be used for short for"},{"line_number":39,"context_line":"availability zone) in network creation, in Tricircle, the \u0027az_hints\u0027 means"},{"line_number":40,"context_line":"which AZ the network should be spreaded into. It\u0027s a little different"},{"line_number":41,"context_line":"from [4] in Neutron. If no \u0027az_hints\u0027 was specified in network creation,"}],"source_content_type":"text/x-rst","patch_set":13,"id":"dab17558_8738daef","line":38,"range":{"start_line":38,"start_character":38,"end_line":38,"end_character":46},"updated":"2016-05-15 23:29:34.000000000","message":"Az or az ??","commit_id":"3d9f8469aaf229397d54eae34a3b70db095feeb3"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"ef11fff2aca9c66a73eacdb2605b5b5ba837b7c9","unresolved":false,"context_lines":[{"line_number":35,"context_line":"Problem Description"},{"line_number":36,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":37,"context_line":"When an user wants to create a network in Neutron API Server, the user can"},{"line_number":38,"context_line":"specify the \u0027availability_zone_hints\u0027(AZ or az will be used for short for"},{"line_number":39,"context_line":"availability zone) in network creation, in Tricircle, the \u0027az_hints\u0027 means"},{"line_number":40,"context_line":"which AZ the network should be spreaded into. It\u0027s a little different"},{"line_number":41,"context_line":"from [4] in Neutron. If no \u0027az_hints\u0027 was specified in network creation,"}],"source_content_type":"text/x-rst","patch_set":13,"id":"dab17558_673df6dc","line":38,"range":{"start_line":38,"start_character":60,"end_line":38,"end_character":69},"updated":"2016-05-15 23:29:34.000000000","message":"for short ??\nMaybe it\u0027s not necessary.","commit_id":"3d9f8469aaf229397d54eae34a3b70db095feeb3"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"5a9ca2494e08de0b197159dfbbb3bb0b63a3cbe9","unresolved":false,"context_lines":[{"line_number":35,"context_line":"Problem Description"},{"line_number":36,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":37,"context_line":"When an user wants to create a network in Neutron API Server, the user can"},{"line_number":38,"context_line":"specify the \u0027availability_zone_hints\u0027(AZ or az will be used for short for"},{"line_number":39,"context_line":"availability zone) in network creation, in Tricircle, the \u0027az_hints\u0027 means"},{"line_number":40,"context_line":"which AZ the network should be spreaded into. It\u0027s a little different"},{"line_number":41,"context_line":"from [4] in Neutron. If no \u0027az_hints\u0027 was specified in network creation,"}],"source_content_type":"text/x-rst","patch_set":13,"id":"dab17558_154c14c7","line":38,"range":{"start_line":38,"start_character":38,"end_line":38,"end_character":46},"in_reply_to":"dab17558_8738daef","updated":"2016-05-16 02:57:55.000000000","message":"both will be used as abbreviation","commit_id":"3d9f8469aaf229397d54eae34a3b70db095feeb3"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"ef11fff2aca9c66a73eacdb2605b5b5ba837b7c9","unresolved":false,"context_lines":[{"line_number":34,"context_line":""},{"line_number":35,"context_line":"Problem Description"},{"line_number":36,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":37,"context_line":"When an user wants to create a network in Neutron API Server, the user can"},{"line_number":38,"context_line":"specify the \u0027availability_zone_hints\u0027(AZ or az will be used for short for"},{"line_number":39,"context_line":"availability zone) in network creation, in Tricircle, the \u0027az_hints\u0027 means"},{"line_number":40,"context_line":"which AZ the network should be spreaded into. It\u0027s a little different"},{"line_number":41,"context_line":"from [4] in Neutron. If no \u0027az_hints\u0027 was specified in network creation,"},{"line_number":42,"context_line":"then this network can be spreaded into any AZ. If there are a list of"}],"source_content_type":"text/x-rst","patch_set":13,"id":"dab17558_a7235ebc","line":39,"range":{"start_line":37,"start_character":0,"end_line":39,"end_character":39},"updated":"2016-05-15 23:29:34.000000000","message":"This sentence may be expected to explain how \"availability_zone_hints\" works.\n\nCould you please re-write up this sentence again from availability_zone_hints point of view.","commit_id":"3d9f8469aaf229397d54eae34a3b70db095feeb3"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"5a9ca2494e08de0b197159dfbbb3bb0b63a3cbe9","unresolved":false,"context_lines":[{"line_number":34,"context_line":""},{"line_number":35,"context_line":"Problem Description"},{"line_number":36,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":37,"context_line":"When an user wants to create a network in Neutron API Server, the user can"},{"line_number":38,"context_line":"specify the \u0027availability_zone_hints\u0027(AZ or az will be used for short for"},{"line_number":39,"context_line":"availability zone) in network creation, in Tricircle, the \u0027az_hints\u0027 means"},{"line_number":40,"context_line":"which AZ the network should be spreaded into. It\u0027s a little different"},{"line_number":41,"context_line":"from [4] in Neutron. If no \u0027az_hints\u0027 was specified in network creation,"},{"line_number":42,"context_line":"then this network can be spreaded into any AZ. If there are a list of"}],"source_content_type":"text/x-rst","patch_set":13,"id":"dab17558_55969cf0","line":39,"range":{"start_line":37,"start_character":0,"end_line":39,"end_character":39},"in_reply_to":"dab17558_a7235ebc","updated":"2016-05-16 02:57:55.000000000","message":"How about to add reference here: http://docs.openstack.org/mitaka/networking-guide/adv-config-availability-zone.html","commit_id":"3d9f8469aaf229397d54eae34a3b70db095feeb3"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"ef11fff2aca9c66a73eacdb2605b5b5ba837b7c9","unresolved":false,"context_lines":[{"line_number":39,"context_line":"availability zone) in network creation, in Tricircle, the \u0027az_hints\u0027 means"},{"line_number":40,"context_line":"which AZ the network should be spreaded into. It\u0027s a little different"},{"line_number":41,"context_line":"from [4] in Neutron. If no \u0027az_hints\u0027 was specified in network creation,"},{"line_number":42,"context_line":"then this network can be spreaded into any AZ. If there are a list of"},{"line_number":43,"context_line":"\u0027az_hints\u0027 in the network creation, that means the network should be able"},{"line_number":44,"context_line":"to spread into these AZs."},{"line_number":45,"context_line":""}],"source_content_type":"text/x-rst","patch_set":13,"id":"dab17558_6714d64c","line":42,"range":{"start_line":42,"start_character":5,"end_line":42,"end_character":45},"updated":"2016-05-15 23:29:34.000000000","message":"Could you please double-check this description?","commit_id":"3d9f8469aaf229397d54eae34a3b70db095feeb3"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"ef11fff2aca9c66a73eacdb2605b5b5ba837b7c9","unresolved":false,"context_lines":[{"line_number":41,"context_line":"from [4] in Neutron. If no \u0027az_hints\u0027 was specified in network creation,"},{"line_number":42,"context_line":"then this network can be spreaded into any AZ. If there are a list of"},{"line_number":43,"context_line":"\u0027az_hints\u0027 in the network creation, that means the network should be able"},{"line_number":44,"context_line":"to spread into these AZs."},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"When an user created VM or Volume, there is also one parameter called"},{"line_number":47,"context_line":"availability zone. The AZ parameter is used for Volume and VM co-location, so"}],"source_content_type":"text/x-rst","patch_set":13,"id":"dab17558_c70dc23f","line":44,"range":{"start_line":44,"start_character":0,"end_line":44,"end_character":9},"updated":"2016-05-15 23:29:34.000000000","message":"-to spread\n+to be spread","commit_id":"3d9f8469aaf229397d54eae34a3b70db095feeb3"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"ef11fff2aca9c66a73eacdb2605b5b5ba837b7c9","unresolved":false,"context_lines":[{"line_number":43,"context_line":"\u0027az_hints\u0027 in the network creation, that means the network should be able"},{"line_number":44,"context_line":"to spread into these AZs."},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"When an user created VM or Volume, there is also one parameter called"},{"line_number":47,"context_line":"availability zone. The AZ parameter is used for Volume and VM co-location, so"},{"line_number":48,"context_line":"that the Volume and VM will be created into same bottom OpenStack instance."},{"line_number":49,"context_line":""}],"source_content_type":"text/x-rst","patch_set":13,"id":"dab17558_0704ea15","line":46,"range":{"start_line":46,"start_character":13,"end_line":46,"end_character":20},"updated":"2016-05-15 23:29:34.000000000","message":"-created\n+creates","commit_id":"3d9f8469aaf229397d54eae34a3b70db095feeb3"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"ef11fff2aca9c66a73eacdb2605b5b5ba837b7c9","unresolved":false,"context_lines":[{"line_number":44,"context_line":"to spread into these AZs."},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"When an user created VM or Volume, there is also one parameter called"},{"line_number":47,"context_line":"availability zone. The AZ parameter is used for Volume and VM co-location, so"},{"line_number":48,"context_line":"that the Volume and VM will be created into same bottom OpenStack instance."},{"line_number":49,"context_line":""},{"line_number":50,"context_line":"When a VM is attached to a network, Tricircle will check whether the VM\u0027s AZ"}],"source_content_type":"text/x-rst","patch_set":13,"id":"dab17558_2a057310","line":47,"range":{"start_line":47,"start_character":19,"end_line":47,"end_character":35},"updated":"2016-05-15 23:29:34.000000000","message":"Which is better, \"The AZ parameter\" or \"availability zone\" or \"that parameter\"?","commit_id":"3d9f8469aaf229397d54eae34a3b70db095feeb3"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"5a9ca2494e08de0b197159dfbbb3bb0b63a3cbe9","unresolved":false,"context_lines":[{"line_number":44,"context_line":"to spread into these AZs."},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"When an user created VM or Volume, there is also one parameter called"},{"line_number":47,"context_line":"availability zone. The AZ parameter is used for Volume and VM co-location, so"},{"line_number":48,"context_line":"that the Volume and VM will be created into same bottom OpenStack instance."},{"line_number":49,"context_line":""},{"line_number":50,"context_line":"When a VM is attached to a network, Tricircle will check whether the VM\u0027s AZ"}],"source_content_type":"text/x-rst","patch_set":13,"id":"dab17558_75d3e0d5","line":47,"range":{"start_line":47,"start_character":19,"end_line":47,"end_character":35},"in_reply_to":"dab17558_2a057310","updated":"2016-05-16 02:57:55.000000000","message":"\"availability zone\"?","commit_id":"3d9f8469aaf229397d54eae34a3b70db095feeb3"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"ef11fff2aca9c66a73eacdb2605b5b5ba837b7c9","unresolved":false,"context_lines":[{"line_number":47,"context_line":"availability zone. The AZ parameter is used for Volume and VM co-location, so"},{"line_number":48,"context_line":"that the Volume and VM will be created into same bottom OpenStack instance."},{"line_number":49,"context_line":""},{"line_number":50,"context_line":"When a VM is attached to a network, Tricircle will check whether the VM\u0027s AZ"},{"line_number":51,"context_line":"is inside in the network\u0027s AZs scope. If the VM is not in the network\u0027s AZs"},{"line_number":52,"context_line":"scope, the VM creation will be rejected."},{"line_number":53,"context_line":""}],"source_content_type":"text/x-rst","patch_set":13,"id":"dab17558_8a061f1a","line":50,"range":{"start_line":50,"start_character":36,"end_line":50,"end_character":45},"updated":"2016-05-15 23:29:34.000000000","message":"-Tricircle\n+the Tricircle","commit_id":"3d9f8469aaf229397d54eae34a3b70db095feeb3"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"ef11fff2aca9c66a73eacdb2605b5b5ba837b7c9","unresolved":false,"context_lines":[{"line_number":47,"context_line":"availability zone. The AZ parameter is used for Volume and VM co-location, so"},{"line_number":48,"context_line":"that the Volume and VM will be created into same bottom OpenStack instance."},{"line_number":49,"context_line":""},{"line_number":50,"context_line":"When a VM is attached to a network, Tricircle will check whether the VM\u0027s AZ"},{"line_number":51,"context_line":"is inside in the network\u0027s AZs scope. If the VM is not in the network\u0027s AZs"},{"line_number":52,"context_line":"scope, the VM creation will be rejected."},{"line_number":53,"context_line":""}],"source_content_type":"text/x-rst","patch_set":13,"id":"dab17558_aa116354","line":50,"range":{"start_line":50,"start_character":69,"end_line":50,"end_character":76},"updated":"2016-05-15 23:29:34.000000000","message":"VM itself does not have availability zone but availability zone does...","commit_id":"3d9f8469aaf229397d54eae34a3b70db095feeb3"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"5a9ca2494e08de0b197159dfbbb3bb0b63a3cbe9","unresolved":false,"context_lines":[{"line_number":47,"context_line":"availability zone. The AZ parameter is used for Volume and VM co-location, so"},{"line_number":48,"context_line":"that the Volume and VM will be created into same bottom OpenStack instance."},{"line_number":49,"context_line":""},{"line_number":50,"context_line":"When a VM is attached to a network, Tricircle will check whether the VM\u0027s AZ"},{"line_number":51,"context_line":"is inside in the network\u0027s AZs scope. If the VM is not in the network\u0027s AZs"},{"line_number":52,"context_line":"scope, the VM creation will be rejected."},{"line_number":53,"context_line":""}],"source_content_type":"text/x-rst","patch_set":13,"id":"dab17558_35f4b859","line":50,"range":{"start_line":50,"start_character":69,"end_line":50,"end_character":76},"in_reply_to":"dab17558_aa116354","updated":"2016-05-16 02:57:55.000000000","message":"VM and network are in same AZ  scope.","commit_id":"3d9f8469aaf229397d54eae34a3b70db095feeb3"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"ef11fff2aca9c66a73eacdb2605b5b5ba837b7c9","unresolved":false,"context_lines":[{"line_number":51,"context_line":"is inside in the network\u0027s AZs scope. If the VM is not in the network\u0027s AZs"},{"line_number":52,"context_line":"scope, the VM creation will be rejected."},{"line_number":53,"context_line":""},{"line_number":54,"context_line":"Currently, Tricircle only supports one pod in one AZ. And only supports a"},{"line_number":55,"context_line":"network associated with one AZ. That means currently a tenant\u0027s network will"},{"line_number":56,"context_line":"be presented only in one bottom OpenStack, that also means all VMs connected"},{"line_number":57,"context_line":"to the network will be located inside one bottom OpenStack."}],"source_content_type":"text/x-rst","patch_set":13,"id":"dab17558_ea17eb42","line":54,"range":{"start_line":54,"start_character":11,"end_line":54,"end_character":20},"updated":"2016-05-15 23:29:34.000000000","message":"-Tricircle\n+the Tricircle","commit_id":"3d9f8469aaf229397d54eae34a3b70db095feeb3"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"ef11fff2aca9c66a73eacdb2605b5b5ba837b7c9","unresolved":false,"context_lines":[{"line_number":51,"context_line":"is inside in the network\u0027s AZs scope. If the VM is not in the network\u0027s AZs"},{"line_number":52,"context_line":"scope, the VM creation will be rejected."},{"line_number":53,"context_line":""},{"line_number":54,"context_line":"Currently, Tricircle only supports one pod in one AZ. And only supports a"},{"line_number":55,"context_line":"network associated with one AZ. That means currently a tenant\u0027s network will"},{"line_number":56,"context_line":"be presented only in one bottom OpenStack, that also means all VMs connected"},{"line_number":57,"context_line":"to the network will be located inside one bottom OpenStack."}],"source_content_type":"text/x-rst","patch_set":13,"id":"dab17558_6a22dba4","line":54,"range":{"start_line":54,"start_character":63,"end_line":54,"end_character":71},"updated":"2016-05-15 23:29:34.000000000","message":"Who \"supports\"?","commit_id":"3d9f8469aaf229397d54eae34a3b70db095feeb3"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"8dfc4b504ee084c9dd2044857ede557f30f7532f","unresolved":false,"context_lines":[{"line_number":22,"context_line":""},{"line_number":23,"context_line":"Nova APIGW is the functionality to trigger automatic networking creation when"},{"line_number":24,"context_line":"new VMs are being provisioned. Neutron Tricircle plug-in is the functionality"},{"line_number":25,"context_line":"to create cross OpenStack L2/L3 networking for new VMs. After the Tricircle"},{"line_number":26,"context_line":"create the tenant ID and complete the pod binding. Cinder APIGW and Nova"},{"line_number":27,"context_line":"APIGW will pass the cinder api or nova api request to appropriate bottom"},{"line_number":28,"context_line":"OpenStack."},{"line_number":29,"context_line":""}],"source_content_type":"text/x-rst","patch_set":14,"id":"dab17558_7e038642","line":26,"range":{"start_line":25,"start_character":56,"end_line":26,"end_character":51},"updated":"2016-05-17 01:34:12.000000000","message":"Tenant ID is not created in Tricircle, it\u0027s created in KeyStone, so the sentence should be update as \u0027After the binding of tenant-id and pod finished in the Tricircle, \u0027","commit_id":"5518e229373f4365e620b9feed7ebb5d075f1ace"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"8dfc4b504ee084c9dd2044857ede557f30f7532f","unresolved":false,"context_lines":[{"line_number":188,"context_line":""},{"line_number":189,"context_line":"* Shared VLAN"},{"line_number":190,"context_line":"  Nova API-GW creates network in bottom pod where the VM will reside with the"},{"line_number":191,"context_line":"  VLAN segment id, network name and network type."},{"line_number":192,"context_line":""},{"line_number":193,"context_line":"* Shared VxLAN"},{"line_number":194,"context_line":"  Nova API-GW creates network in bottom pod where the VM will reside with the"}],"source_content_type":"text/x-rst","patch_set":14,"id":"dab17558_391d9862","line":191,"range":{"start_line":191,"start_character":44,"end_line":191,"end_character":48},"updated":"2016-05-17 01:34:12.000000000","message":"retrieved from the Neutron API server in the Tricircle","commit_id":"5518e229373f4365e620b9feed7ebb5d075f1ace"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"8dfc4b504ee084c9dd2044857ede557f30f7532f","unresolved":false,"context_lines":[{"line_number":200,"context_line":"* Mixed VLAN/VxLAN"},{"line_number":201,"context_line":"  Nova API-GW creates network in bottom pod where the VM will reside."},{"line_number":202,"context_line":""},{"line_number":203,"context_line":"After the network in the bottom created successfully, need to retrieve the"},{"line_number":204,"context_line":"network information like segment id, network name and network type, and make"},{"line_number":205,"context_line":"this network in the bottom pod as one of the segments in the network in"},{"line_number":206,"context_line":"Tricircle."},{"line_number":207,"context_line":""},{"line_number":208,"context_line":"3. L2GW driver under Tricircle Plugin in Neutron API server"},{"line_number":209,"context_line":"Tricircle plugin needs to support multi-segment network extension[3]."}],"source_content_type":"text/x-rst","patch_set":14,"id":"dab17558_59adfce7","line":206,"range":{"start_line":203,"start_character":0,"end_line":206,"end_character":10},"updated":"2016-05-17 01:34:12.000000000","message":"align this paragraph with last one, it should be the part of the content of Mixed VLAN/VxLAN","commit_id":"5518e229373f4365e620b9feed7ebb5d075f1ace"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"8dfc4b504ee084c9dd2044857ede557f30f7532f","unresolved":false,"context_lines":[{"line_number":460,"context_line":"Net2 in Pod2 -\u003e Router1 in Pod2 -\u003e Net1 in Pod2 -\u003e L2GW in Pod2 ---\u003e L2GW in"},{"line_number":461,"context_line":"Pod1 -\u003e Net1 in Pod1."},{"line_number":462,"context_line":""},{"line_number":463,"context_line":"If Net2 is a cross pod L2 network, and can be expanded to Pod1 too, then will"},{"line_number":464,"context_line":"just expand Net2 to Pod1. After the Net2 expansion(just like cross pod L2"},{"line_number":465,"context_line":"networking to spread one network in multiple pods ), it’ll look like"},{"line_number":466,"context_line":"(Net2, Net1, Router1) in Pod1,  (Net1, Net2, Router1) in Pod2, In Pod1,"}],"source_content_type":"text/x-rst","patch_set":14,"id":"dab17558_b9c5085d","line":463,"range":{"start_line":463,"start_character":0,"end_line":463,"end_character":2},"updated":"2016-05-17 01:34:12.000000000","message":"Add note here: The traffic for Net1 in Pod2 to Net1 in Pod1 can bypass the L2GW in Pod2, that means outbound traffic can bypass the L2GW, but inbound traffic can\u0027t bypass. It\u0027s up to the L2GW implementation. With the inbound traffic through L2GW, the inbound traffic to the VM will not be impacted by the VM migration from one host to another.","commit_id":"5518e229373f4365e620b9feed7ebb5d075f1ace"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"8dfc4b504ee084c9dd2044857ede557f30f7532f","unresolved":false,"context_lines":[{"line_number":470,"context_line":"Net1 in Pod1 -\u003e Router1 in Pod1 -\u003e Net2 in Pod1 -\u003e L2GW in Pod1 ---\u003e L2GW in"},{"line_number":471,"context_line":"Pod2 -\u003e Net2 in Pod2."},{"line_number":472,"context_line":""},{"line_number":473,"context_line":"To limit the complexity, one network’s az_hint can only be created with"},{"line_number":474,"context_line":"network, and no update is allowed, if az_hint need to be updated, you have to"},{"line_number":475,"context_line":"delete the network and create again."},{"line_number":476,"context_line":""}],"source_content_type":"text/x-rst","patch_set":14,"id":"dab17558_7996004d","line":473,"range":{"start_line":473,"start_character":0,"end_line":473,"end_character":2},"updated":"2016-05-17 01:34:12.000000000","message":"The traffic for Net2 in Pod1 to Net2 in Pod2 can bypass the L2GW in Pod1, that means outbound traffic can bypass the L2GW, but inbound traffic can\u0027t bypass. It\u0027s up to the L2GW implementation. With the inbound traffic through L2GW, the inbound traffic to the VM will not be impacted by the VM migration from one host to another.","commit_id":"5518e229373f4365e620b9feed7ebb5d075f1ace"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"8dfc4b504ee084c9dd2044857ede557f30f7532f","unresolved":false,"context_lines":[{"line_number":520,"context_line":"[4] http://developer.openstack.org/api-ref-networking-v2-ext.html#networks-multi-provider-ext"},{"line_number":521,"context_line":"[5] http://docs.openstack.org/mitaka/networking-guide/adv-config-availability-zone.html"},{"line_number":522,"context_line":"[6] https://review.openstack.org/#/c/306224/"},{"line_number":523,"context_line":"[7] http://docs.openstack.org/mitaka/networking-guide/adv-config-availability-zone.html"}],"source_content_type":"text/x-rst","patch_set":14,"id":"dab17558_19841409","line":523,"range":{"start_line":523,"start_character":83,"end_line":523,"end_character":87},"updated":"2016-05-17 01:34:12.000000000","message":"duplicated with [5]","commit_id":"5518e229373f4365e620b9feed7ebb5d075f1ace"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"453236d7ef815749243e1f853710f8f988dca27e","unresolved":false,"context_lines":[{"line_number":174,"context_line":"* Type driver for Local Network only updating ``network_type`` for the"},{"line_number":175,"context_line":"  network to DB."},{"line_number":176,"context_line":""},{"line_number":177,"context_line":"When create a network request is received in Neutron API Server in Tricircle,"},{"line_number":178,"context_line":"the type driver will be called according to the configured network type."},{"line_number":179,"context_line":""},{"line_number":180,"context_line":"2. Nova API-GW to trigger the bottom networking automation"}],"source_content_type":"text/x-rst","patch_set":15,"id":"bab6814e_d6545b22","line":177,"range":{"start_line":177,"start_character":5,"end_line":177,"end_character":29},"updated":"2016-05-19 22:34:03.000000000","message":"change to \"a network creation request\"","commit_id":"80beb849db0dfcb638aee1ee247fd4aa08c2f908"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"453236d7ef815749243e1f853710f8f988dca27e","unresolved":false,"context_lines":[{"line_number":177,"context_line":"When create a network request is received in Neutron API Server in Tricircle,"},{"line_number":178,"context_line":"the type driver will be called according to the configured network type."},{"line_number":179,"context_line":""},{"line_number":180,"context_line":"2. Nova API-GW to trigger the bottom networking automation"},{"line_number":181,"context_line":"Nova API-GW can be aware of when a new VM is provisioned if boot VM api request"},{"line_number":182,"context_line":"received, therefore Nova API-GW is responsible for the network creation in the"},{"line_number":183,"context_line":"bottom OpenStack instances."},{"line_number":184,"context_line":""}],"source_content_type":"text/x-rst","patch_set":15,"id":"bab6814e_5616ab55","line":181,"range":{"start_line":180,"start_character":0,"end_line":181,"end_character":14},"updated":"2016-05-19 22:34:03.000000000","message":"add empty line","commit_id":"80beb849db0dfcb638aee1ee247fd4aa08c2f908"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"453236d7ef815749243e1f853710f8f988dca27e","unresolved":false,"context_lines":[{"line_number":179,"context_line":""},{"line_number":180,"context_line":"2. Nova API-GW to trigger the bottom networking automation"},{"line_number":181,"context_line":"Nova API-GW can be aware of when a new VM is provisioned if boot VM api request"},{"line_number":182,"context_line":"received, therefore Nova API-GW is responsible for the network creation in the"},{"line_number":183,"context_line":"bottom OpenStack instances."},{"line_number":184,"context_line":""},{"line_number":185,"context_line":"Nova API-GW needs to get the network type from Neutron API server in Tricircle,"}],"source_content_type":"text/x-rst","patch_set":15,"id":"bab6814e_b169e1c0","line":182,"range":{"start_line":182,"start_character":0,"end_line":182,"end_character":8},"updated":"2016-05-19 22:34:03.000000000","message":"is received","commit_id":"80beb849db0dfcb638aee1ee247fd4aa08c2f908"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"453236d7ef815749243e1f853710f8f988dca27e","unresolved":false,"context_lines":[{"line_number":193,"context_line":"* Shared VxLAN"},{"line_number":194,"context_line":"  Nova API-GW creates network in bottom pod where the VM will reside with the"},{"line_number":195,"context_line":"  VxLAN segment id, network name and network type which is retrieved from"},{"line_number":196,"context_line":"  Tricricle Neutron API server.After the network in the bottom created"},{"line_number":197,"context_line":"  successfully, need to make this network in the bottom pod as one of the"},{"line_number":198,"context_line":"  segments in the network in Tricircle."},{"line_number":199,"context_line":""}],"source_content_type":"text/x-rst","patch_set":15,"id":"bab6814e_b1c5618f","line":196,"range":{"start_line":196,"start_character":28,"end_line":196,"end_character":33},"updated":"2016-05-19 22:34:03.000000000","message":"add space","commit_id":"80beb849db0dfcb638aee1ee247fd4aa08c2f908"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"453236d7ef815749243e1f853710f8f988dca27e","unresolved":false,"context_lines":[{"line_number":193,"context_line":"* Shared VxLAN"},{"line_number":194,"context_line":"  Nova API-GW creates network in bottom pod where the VM will reside with the"},{"line_number":195,"context_line":"  VxLAN segment id, network name and network type which is retrieved from"},{"line_number":196,"context_line":"  Tricricle Neutron API server.After the network in the bottom created"},{"line_number":197,"context_line":"  successfully, need to make this network in the bottom pod as one of the"},{"line_number":198,"context_line":"  segments in the network in Tricircle."},{"line_number":199,"context_line":""}],"source_content_type":"text/x-rst","patch_set":15,"id":"bab6814e_d15105da","line":196,"range":{"start_line":196,"start_character":59,"end_line":196,"end_character":68},"updated":"2016-05-19 22:34:03.000000000","message":"is created","commit_id":"80beb849db0dfcb638aee1ee247fd4aa08c2f908"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"453236d7ef815749243e1f853710f8f988dca27e","unresolved":false,"context_lines":[{"line_number":197,"context_line":"  successfully, need to make this network in the bottom pod as one of the"},{"line_number":198,"context_line":"  segments in the network in Tricircle."},{"line_number":199,"context_line":""},{"line_number":200,"context_line":"* Mixed VLAN/VxLAN"},{"line_number":201,"context_line":"  Nova API-GW creates network in bottom pod where the VM will reside."},{"line_number":202,"context_line":""},{"line_number":203,"context_line":"3. L2GW driver under Tricircle Plugin in Neutron API server"}],"source_content_type":"text/x-rst","patch_set":15,"id":"bab6814e_b1cf217e","line":200,"range":{"start_line":200,"start_character":2,"end_line":200,"end_character":18},"updated":"2016-05-19 22:34:03.000000000","message":"this case also requires to update network in top with the segmentation information of bottom networks","commit_id":"80beb849db0dfcb638aee1ee247fd4aa08c2f908"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"453236d7ef815749243e1f853710f8f988dca27e","unresolved":false,"context_lines":[{"line_number":200,"context_line":"* Mixed VLAN/VxLAN"},{"line_number":201,"context_line":"  Nova API-GW creates network in bottom pod where the VM will reside."},{"line_number":202,"context_line":""},{"line_number":203,"context_line":"3. L2GW driver under Tricircle Plugin in Neutron API server"},{"line_number":204,"context_line":"Tricircle plugin needs to support multi-segment network extension[3]."},{"line_number":205,"context_line":""},{"line_number":206,"context_line":"For Shared VxLAN or Mixed VLAN/VxLAN L2 network type, it’ll be a multi-segment"},{"line_number":207,"context_line":"network in Neutron API server in Tiricircle. Each network in the bottom"}],"source_content_type":"text/x-rst","patch_set":15,"id":"bab6814e_71ac99a0","line":204,"range":{"start_line":203,"start_character":2,"end_line":204,"end_character":5},"updated":"2016-05-19 22:34:03.000000000","message":"add empty line","commit_id":"80beb849db0dfcb638aee1ee247fd4aa08c2f908"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"453236d7ef815749243e1f853710f8f988dca27e","unresolved":false,"context_lines":[{"line_number":211,"context_line":"responsible to call Neutron server api to update the network in Tricircle"},{"line_number":212,"context_line":"with a new segment from the network in the bottom pod."},{"line_number":213,"context_line":""},{"line_number":214,"context_line":"If the  network in the bottom was removed successfully, Nova API-GW is"},{"line_number":215,"context_line":"responsible to call Neutron server api to remove the segment in the bottom"},{"line_number":216,"context_line":"pod from network in Tricircle."},{"line_number":217,"context_line":""}],"source_content_type":"text/x-rst","patch_set":15,"id":"bab6814e_b17d611e","line":214,"range":{"start_line":214,"start_character":6,"end_line":214,"end_character":9},"updated":"2016-05-19 22:34:03.000000000","message":"remove one space","commit_id":"80beb849db0dfcb638aee1ee247fd4aa08c2f908"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"453236d7ef815749243e1f853710f8f988dca27e","unresolved":false,"context_lines":[{"line_number":215,"context_line":"responsible to call Neutron server api to remove the segment in the bottom"},{"line_number":216,"context_line":"pod from network in Tricircle."},{"line_number":217,"context_line":""},{"line_number":218,"context_line":"When L2GW driver under Tricircle Plugin in Neutron API server receive the"},{"line_number":219,"context_line":"segment update request, L2GW driver is responsible to start async job to"},{"line_number":220,"context_line":"orchestrate L2GW api for L2 networking automation[1][2]."},{"line_number":221,"context_line":""}],"source_content_type":"text/x-rst","patch_set":15,"id":"bab6814e_11938d50","line":218,"range":{"start_line":218,"start_character":62,"end_line":218,"end_character":69},"updated":"2016-05-19 22:34:03.000000000","message":"s/receive/receives","commit_id":"80beb849db0dfcb638aee1ee247fd4aa08c2f908"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"453236d7ef815749243e1f853710f8f988dca27e","unresolved":false,"context_lines":[{"line_number":276,"context_line":"it will invoke Local Network type driver. Local_Network driver under the"},{"line_number":277,"context_line":"Tricircle plugin will update network with ``network_type`` to DB."},{"line_number":278,"context_line":""},{"line_number":279,"context_line":"For exmaple, a user creates VM1 in AZ1, and connects it to network Net1."},{"line_number":280,"context_line":"``Nova API-GW`` will send network creation message to POD1 and the VM will be"},{"line_number":281,"context_line":"booted in AZ1 (There should be only one pod in AZ1). Network will be created"},{"line_number":282,"context_line":"in POD1."}],"source_content_type":"text/x-rst","patch_set":15,"id":"bab6814e_716e5902","line":279,"range":{"start_line":279,"start_character":35,"end_line":279,"end_character":38},"updated":"2016-05-19 22:34:03.000000000","message":"add \"which has only one pod POD1\"","commit_id":"80beb849db0dfcb638aee1ee247fd4aa08c2f908"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"453236d7ef815749243e1f853710f8f988dca27e","unresolved":false,"context_lines":[{"line_number":282,"context_line":"in POD1."},{"line_number":283,"context_line":""},{"line_number":284,"context_line":"If a user wants to create VM2 in AZ2 or POD2 in AZ1, and connect it to"},{"line_number":285,"context_line":"network Net1 in the Tricircle, it would be to fail. Because the Net1 is"},{"line_number":286,"context_line":"local_network type network and it is limited to present in POD1 in AZ1 only."},{"line_number":287,"context_line":""},{"line_number":288,"context_line":"**Shared VLAN Implementation:**"}],"source_content_type":"text/x-rst","patch_set":15,"id":"bab6814e_b10d6140","line":285,"range":{"start_line":285,"start_character":31,"end_line":285,"end_character":50},"updated":"2016-05-19 22:34:03.000000000","message":"I think \"it would be failed\" is better.","commit_id":"80beb849db0dfcb638aee1ee247fd4aa08c2f908"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"453236d7ef815749243e1f853710f8f988dca27e","unresolved":false,"context_lines":[{"line_number":301,"context_line":""},{"line_number":302,"context_line":"A user creates VM1 in AZ1, and connects it to network Net1. If VM will be"},{"line_number":303,"context_line":"booted in POD1, ``Nova API-GW`` needs to get the network information and"},{"line_number":304,"context_line":"send create network message to POD1. Create network message includes"},{"line_number":305,"context_line":" ``network_type`` and ``segment`` and ``physical_network``."},{"line_number":306,"context_line":""},{"line_number":307,"context_line":"Then the user creates VM2 in AZ2, and connects it to network Net1. If VM will"}],"source_content_type":"text/x-rst","patch_set":15,"id":"bab6814e_acc50a8f","line":304,"range":{"start_line":304,"start_character":37,"end_line":304,"end_character":51},"updated":"2016-05-19 22:34:03.000000000","message":"change to \"Network creation\"","commit_id":"80beb849db0dfcb638aee1ee247fd4aa08c2f908"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"453236d7ef815749243e1f853710f8f988dca27e","unresolved":false,"context_lines":[{"line_number":311,"context_line":""},{"line_number":312,"context_line":"**Shared VxLAN Implementation:**"},{"line_number":313,"context_line":""},{"line_number":314,"context_line":"A user creates network Net1, Tricircle plugin check the configuration, if"},{"line_number":315,"context_line":"``tenant_network_type`` equals “shared_vxlan”, it will invoke shared VxLAN"},{"line_number":316,"context_line":"driver. Shared VxLAN driver will allocate ``segment``, and assign"},{"line_number":317,"context_line":"``network_type`` with VxLAN, and update network with ``segment`` and"}],"source_content_type":"text/x-rst","patch_set":15,"id":"bab6814e_ccedeef0","line":314,"range":{"start_line":314,"start_character":46,"end_line":314,"end_character":51},"updated":"2016-05-19 22:34:03.000000000","message":"s/check/checks","commit_id":"80beb849db0dfcb638aee1ee247fd4aa08c2f908"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"453236d7ef815749243e1f853710f8f988dca27e","unresolved":false,"context_lines":[{"line_number":318,"context_line":"``network_type`` to DB."},{"line_number":319,"context_line":""},{"line_number":320,"context_line":"A user creates VM1 in AZ1, and connects it to network Net1. If VM will be"},{"line_number":321,"context_line":"booted in POD1,  ``Nova API-GW`` needs to get the network information and send"},{"line_number":322,"context_line":"create network message to POD1, create network message includes"},{"line_number":323,"context_line":"``network_type`` and ``segment``."},{"line_number":324,"context_line":""}],"source_content_type":"text/x-rst","patch_set":15,"id":"bab6814e_07350ff6","line":321,"range":{"start_line":321,"start_character":15,"end_line":321,"end_character":17},"updated":"2016-05-19 22:34:03.000000000","message":"remove one space","commit_id":"80beb849db0dfcb638aee1ee247fd4aa08c2f908"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"453236d7ef815749243e1f853710f8f988dca27e","unresolved":false,"context_lines":[{"line_number":323,"context_line":"``network_type`` and ``segment``."},{"line_number":324,"context_line":""},{"line_number":325,"context_line":"``Nova API-GW`` should update Net1 in Tricircle with the segment information"},{"line_number":326,"context_line":"get from POD1."},{"line_number":327,"context_line":""},{"line_number":328,"context_line":"Then the user creates VM2 in AZ2, and connects it to network Net1. If VM will"},{"line_number":329,"context_line":"be booted in POD2,  ``Nova API-GW`` needs to get the network information and"}],"source_content_type":"text/x-rst","patch_set":15,"id":"bab6814e_8721ffb6","line":326,"range":{"start_line":326,"start_character":0,"end_line":326,"end_character":3},"updated":"2016-05-19 22:34:03.000000000","message":"s/get/got","commit_id":"80beb849db0dfcb638aee1ee247fd4aa08c2f908"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"453236d7ef815749243e1f853710f8f988dca27e","unresolved":false,"context_lines":[{"line_number":331,"context_line":"``network_type`` and ``segment``."},{"line_number":332,"context_line":""},{"line_number":333,"context_line":"``Nova API-GW`` should update Net1 in Tricircle with the segment information"},{"line_number":334,"context_line":"get from POD1."},{"line_number":335,"context_line":""},{"line_number":336,"context_line":"The Tricircle plugin detected that the network includes more than one segment"},{"line_number":337,"context_line":"network, call L2GW driver to start async job for cross pod networking for"}],"source_content_type":"text/x-rst","patch_set":15,"id":"bab6814e_420d4536","line":334,"range":{"start_line":334,"start_character":9,"end_line":334,"end_character":13},"updated":"2016-05-19 22:34:03.000000000","message":"should be \"POD2\"","commit_id":"80beb849db0dfcb638aee1ee247fd4aa08c2f908"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"453236d7ef815749243e1f853710f8f988dca27e","unresolved":false,"context_lines":[{"line_number":333,"context_line":"``Nova API-GW`` should update Net1 in Tricircle with the segment information"},{"line_number":334,"context_line":"get from POD1."},{"line_number":335,"context_line":""},{"line_number":336,"context_line":"The Tricircle plugin detected that the network includes more than one segment"},{"line_number":337,"context_line":"network, call L2GW driver to start async job for cross pod networking for"},{"line_number":338,"context_line":"Net1. The L2GW driver will create L2GW1 in POD1 and L2GW2 in POD2. In POD1,"},{"line_number":339,"context_line":"L2GW1 will connect the local Net1 and create L2GW remote connection to L2GW2,"}],"source_content_type":"text/x-rst","patch_set":15,"id":"bab6814e_427265ae","line":336,"range":{"start_line":336,"start_character":21,"end_line":336,"end_character":29},"updated":"2016-05-19 22:34:03.000000000","message":"detects","commit_id":"80beb849db0dfcb638aee1ee247fd4aa08c2f908"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"453236d7ef815749243e1f853710f8f988dca27e","unresolved":false,"context_lines":[{"line_number":334,"context_line":"get from POD1."},{"line_number":335,"context_line":""},{"line_number":336,"context_line":"The Tricircle plugin detected that the network includes more than one segment"},{"line_number":337,"context_line":"network, call L2GW driver to start async job for cross pod networking for"},{"line_number":338,"context_line":"Net1. The L2GW driver will create L2GW1 in POD1 and L2GW2 in POD2. In POD1,"},{"line_number":339,"context_line":"L2GW1 will connect the local Net1 and create L2GW remote connection to L2GW2,"},{"line_number":340,"context_line":"then populate MAC/IP which resides in POD2 information in L2GW1. In POD2,"}],"source_content_type":"text/x-rst","patch_set":15,"id":"bab6814e_029fbdb4","line":337,"range":{"start_line":337,"start_character":9,"end_line":337,"end_character":13},"updated":"2016-05-19 22:34:03.000000000","message":"calls","commit_id":"80beb849db0dfcb638aee1ee247fd4aa08c2f908"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"453236d7ef815749243e1f853710f8f988dca27e","unresolved":false,"context_lines":[{"line_number":337,"context_line":"network, call L2GW driver to start async job for cross pod networking for"},{"line_number":338,"context_line":"Net1. The L2GW driver will create L2GW1 in POD1 and L2GW2 in POD2. In POD1,"},{"line_number":339,"context_line":"L2GW1 will connect the local Net1 and create L2GW remote connection to L2GW2,"},{"line_number":340,"context_line":"then populate MAC/IP which resides in POD2 information in L2GW1. In POD2,"},{"line_number":341,"context_line":"L2GW2 will connect the local Net1 and create L2GW remote connection to L2GW1,"},{"line_number":342,"context_line":"then populate remote MAC/IP information which resides in POD1 in L2GW2."},{"line_number":343,"context_line":""}],"source_content_type":"text/x-rst","patch_set":15,"id":"bab6814e_e291d99a","line":340,"range":{"start_line":340,"start_character":14,"end_line":340,"end_character":55},"updated":"2016-05-19 22:34:03.000000000","message":"the information of MAC/IP which resides","commit_id":"80beb849db0dfcb638aee1ee247fd4aa08c2f908"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"453236d7ef815749243e1f853710f8f988dca27e","unresolved":false,"context_lines":[{"line_number":347,"context_line":"then needs to refresh the L2GW1 MAC/IP information."},{"line_number":348,"context_line":""},{"line_number":349,"context_line":"Whether to populate MAC/IP information should be configurable according to"},{"line_number":350,"context_line":"L2GW capability. And only populate MAC/IP information for the ports are not"},{"line_number":351,"context_line":"resides in the same pod."},{"line_number":352,"context_line":""},{"line_number":353,"context_line":"**Mixed VLAN/VxLAN:**"}],"source_content_type":"text/x-rst","patch_set":15,"id":"bab6814e_e221d9fc","line":350,"range":{"start_line":350,"start_character":62,"end_line":350,"end_character":71},"updated":"2016-05-19 22:34:03.000000000","message":"ports that are not","commit_id":"80beb849db0dfcb638aee1ee247fd4aa08c2f908"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"453236d7ef815749243e1f853710f8f988dca27e","unresolved":false,"context_lines":[{"line_number":372,"context_line":"Tricircle."},{"line_number":373,"context_line":""},{"line_number":374,"context_line":"In Tricircle, network could be created by tenant or admin. For tenant, no way"},{"line_number":375,"context_line":"to specifies the network type and segment id, then default network type will"},{"line_number":376,"context_line":"be used instead. When user uses the network to boot a VM, ``Nova API-GW``"},{"line_number":377,"context_line":"checks the network type. For Mixed VLAN/VxLAN network, ``Nova API-GW`` first"},{"line_number":378,"context_line":"creates network in bottom OpenStack without specifying network type and segment"}],"source_content_type":"text/x-rst","patch_set":15,"id":"bab6814e_42e1c5fd","line":375,"range":{"start_line":375,"start_character":3,"end_line":375,"end_character":12},"updated":"2016-05-19 22:34:03.000000000","message":"specify","commit_id":"80beb849db0dfcb638aee1ee247fd4aa08c2f908"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"453236d7ef815749243e1f853710f8f988dca27e","unresolved":false,"context_lines":[{"line_number":379,"context_line":"ID, then updates the top network with bottom network segmentation information"},{"line_number":380,"context_line":"returned by bottom OpenStack."},{"line_number":381,"context_line":""},{"line_number":382,"context_line":"A user creates network Net1, plugin check the configuration, if"},{"line_number":383,"context_line":"``tenant_network_type`` equals “mixed_vlan_vxlan”, it will invoke mixed VLAN"},{"line_number":384,"context_line":"and VxLAN driver. The driver needs to do nothing for segment is allocated"},{"line_number":385,"context_line":"in bottom."}],"source_content_type":"text/x-rst","patch_set":15,"id":"bab6814e_22bbe1e6","line":382,"range":{"start_line":382,"start_character":36,"end_line":382,"end_character":41},"updated":"2016-05-19 22:34:03.000000000","message":"checks","commit_id":"80beb849db0dfcb638aee1ee247fd4aa08c2f908"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"453236d7ef815749243e1f853710f8f988dca27e","unresolved":false,"context_lines":[{"line_number":381,"context_line":""},{"line_number":382,"context_line":"A user creates network Net1, plugin check the configuration, if"},{"line_number":383,"context_line":"``tenant_network_type`` equals “mixed_vlan_vxlan”, it will invoke mixed VLAN"},{"line_number":384,"context_line":"and VxLAN driver. The driver needs to do nothing for segment is allocated"},{"line_number":385,"context_line":"in bottom."},{"line_number":386,"context_line":""},{"line_number":387,"context_line":"A user creates VM1 in AZ1, and connects it to the network Net1, the VM is"}],"source_content_type":"text/x-rst","patch_set":15,"id":"bab6814e_82ca8d6c","line":384,"range":{"start_line":384,"start_character":49,"end_line":384,"end_character":52},"updated":"2016-05-19 22:34:03.000000000","message":"since","commit_id":"80beb849db0dfcb638aee1ee247fd4aa08c2f908"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"453236d7ef815749243e1f853710f8f988dca27e","unresolved":false,"context_lines":[{"line_number":396,"context_line":"and queries the network information including segment and network type,"},{"line_number":397,"context_line":"updates this new segment to the Net1 in Tricircle ``Neutron API Server``."},{"line_number":398,"context_line":""},{"line_number":399,"context_line":"The Tricircle plugin detected that the Net1 includes more than one segment"},{"line_number":400,"context_line":"network, call L2GW driver to start async job for cross pod networking for"},{"line_number":401,"context_line":"Net1. The L2GW driver will create L2GW1 in POD1 and L2GW2 in POD2. In POD1,"},{"line_number":402,"context_line":"L2GW1 will connect the local Net1 and create L2GW remote connection to L2GW2,"}],"source_content_type":"text/x-rst","patch_set":15,"id":"bab6814e_22900143","line":399,"range":{"start_line":399,"start_character":21,"end_line":399,"end_character":29},"updated":"2016-05-19 22:34:03.000000000","message":"detects","commit_id":"80beb849db0dfcb638aee1ee247fd4aa08c2f908"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"453236d7ef815749243e1f853710f8f988dca27e","unresolved":false,"context_lines":[{"line_number":397,"context_line":"updates this new segment to the Net1 in Tricircle ``Neutron API Server``."},{"line_number":398,"context_line":""},{"line_number":399,"context_line":"The Tricircle plugin detected that the Net1 includes more than one segment"},{"line_number":400,"context_line":"network, call L2GW driver to start async job for cross pod networking for"},{"line_number":401,"context_line":"Net1. The L2GW driver will create L2GW1 in POD1 and L2GW2 in POD2. In POD1,"},{"line_number":402,"context_line":"L2GW1 will connect the local Net1 and create L2GW remote connection to L2GW2,"},{"line_number":403,"context_line":"then populate MAC/IP which resides in POD2 information in L2GW1. In POD2,"}],"source_content_type":"text/x-rst","patch_set":15,"id":"bab6814e_02ba1dc0","line":400,"range":{"start_line":400,"start_character":9,"end_line":400,"end_character":13},"updated":"2016-05-19 22:34:03.000000000","message":"calls","commit_id":"80beb849db0dfcb638aee1ee247fd4aa08c2f908"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"453236d7ef815749243e1f853710f8f988dca27e","unresolved":false,"context_lines":[{"line_number":396,"context_line":"and queries the network information including segment and network type,"},{"line_number":397,"context_line":"updates this new segment to the Net1 in Tricircle ``Neutron API Server``."},{"line_number":398,"context_line":""},{"line_number":399,"context_line":"The Tricircle plugin detected that the Net1 includes more than one segment"},{"line_number":400,"context_line":"network, call L2GW driver to start async job for cross pod networking for"},{"line_number":401,"context_line":"Net1. The L2GW driver will create L2GW1 in POD1 and L2GW2 in POD2. In POD1,"},{"line_number":402,"context_line":"L2GW1 will connect the local Net1 and create L2GW remote connection to L2GW2,"},{"line_number":403,"context_line":"then populate MAC/IP which resides in POD2 information in L2GW1. In POD2,"}],"source_content_type":"text/x-rst","patch_set":15,"id":"bab6814e_c2a9357d","line":400,"range":{"start_line":399,"start_character":67,"end_line":400,"end_character":7},"updated":"2016-05-19 22:34:03.000000000","message":"network segments","commit_id":"80beb849db0dfcb638aee1ee247fd4aa08c2f908"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"453236d7ef815749243e1f853710f8f988dca27e","unresolved":false,"context_lines":[{"line_number":400,"context_line":"network, call L2GW driver to start async job for cross pod networking for"},{"line_number":401,"context_line":"Net1. The L2GW driver will create L2GW1 in POD1 and L2GW2 in POD2. In POD1,"},{"line_number":402,"context_line":"L2GW1 will connect the local Net1 and create L2GW remote connection to L2GW2,"},{"line_number":403,"context_line":"then populate MAC/IP which resides in POD2 information in L2GW1. In POD2,"},{"line_number":404,"context_line":"L2GW2 will connect the local Net1 and create L2GW remote connection to L2GW1,"},{"line_number":405,"context_line":"then populate remote MAC/IP information which resides in POD1 in L2GW2."},{"line_number":406,"context_line":""}],"source_content_type":"text/x-rst","patch_set":15,"id":"bab6814e_a2d231fe","line":403,"range":{"start_line":403,"start_character":14,"end_line":403,"end_character":53},"updated":"2016-05-19 22:34:03.000000000","message":"information of MAC/IP which resides in POD2","commit_id":"80beb849db0dfcb638aee1ee247fd4aa08c2f908"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"453236d7ef815749243e1f853710f8f988dca27e","unresolved":false,"context_lines":[{"line_number":410,"context_line":"then needs to refresh the L2GW1 MAC/IP information,"},{"line_number":411,"context_line":""},{"line_number":412,"context_line":"Whether to populate MAC/IP information should be configurable according to"},{"line_number":413,"context_line":"L2GW capability. And only populate MAC/IP information for the ports are not"},{"line_number":414,"context_line":"resides in the same pod."},{"line_number":415,"context_line":""},{"line_number":416,"context_line":"**L3 bridge network:**"}],"source_content_type":"text/x-rst","patch_set":15,"id":"bab6814e_027dfde6","line":413,"range":{"start_line":413,"start_character":62,"end_line":413,"end_character":75},"updated":"2016-05-19 22:34:03.000000000","message":"ports that are not","commit_id":"80beb849db0dfcb638aee1ee247fd4aa08c2f908"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"453236d7ef815749243e1f853710f8f988dca27e","unresolved":false,"context_lines":[{"line_number":415,"context_line":""},{"line_number":416,"context_line":"**L3 bridge network:**"},{"line_number":417,"context_line":""},{"line_number":418,"context_line":"Current implementation  without cross pod L2 networking."},{"line_number":419,"context_line":"* A special bridge network is created and connected to the routers in"},{"line_number":420,"context_line":"  different bottom OpenStack. We configure the extra routes of the routers to"},{"line_number":421,"context_line":"  route the packets from one OpenStack to another. In current implementation,"}],"source_content_type":"text/x-rst","patch_set":15,"id":"bab6814e_428705d7","line":418,"range":{"start_line":418,"start_character":21,"end_line":418,"end_character":24},"updated":"2016-05-19 22:34:03.000000000","message":"remove one space","commit_id":"80beb849db0dfcb638aee1ee247fd4aa08c2f908"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"453236d7ef815749243e1f853710f8f988dca27e","unresolved":false,"context_lines":[{"line_number":427,"context_line":"* The creation of bridge network is triggered during attaching router"},{"line_number":428,"context_line":"  interface and adding router external gateway."},{"line_number":429,"context_line":""},{"line_number":430,"context_line":"* The L2 network for VM is triggered by ``Nova API-GW`` when a VM is to being"},{"line_number":431,"context_line":"  created in one pod, and finds that there is no network, then the network will"},{"line_number":432,"context_line":"  be created before the VM is booted, network or port parameter is required to"},{"line_number":433,"context_line":"  boot VM. The IP/Mac for VM is allocated in the ``Tricircle``, top layer to"}],"source_content_type":"text/x-rst","patch_set":15,"id":"bab6814e_8250cd5f","line":430,"range":{"start_line":430,"start_character":72,"end_line":430,"end_character":77},"updated":"2016-05-19 22:34:03.000000000","message":"be","commit_id":"80beb849db0dfcb638aee1ee247fd4aa08c2f908"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"453236d7ef815749243e1f853710f8f988dca27e","unresolved":false,"context_lines":[{"line_number":452,"context_line":"a cross pod L2 network, and can be expanded to Pod2, then will just expand"},{"line_number":453,"context_line":"Net1 to Pod2. After the Net1 expansion ( just like cross pod L2 networking"},{"line_number":454,"context_line":"to spread one network in multiple pods ), it’ll look like (Net1, Router1)"},{"line_number":455,"context_line":"in Pod1,  (Net1, Net2, Router1) in Pod2, In Pod2, no VM in Net1, only for"},{"line_number":456,"context_line":"E-W traffic. Now the E-W traffic will look like this:"},{"line_number":457,"context_line":""},{"line_number":458,"context_line":"from Net2 to Net1:"}],"source_content_type":"text/x-rst","patch_set":15,"id":"bab6814e_82ac4d36","line":455,"range":{"start_line":455,"start_character":8,"end_line":455,"end_character":10},"updated":"2016-05-19 22:34:03.000000000","message":"remove one space","commit_id":"80beb849db0dfcb638aee1ee247fd4aa08c2f908"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"453236d7ef815749243e1f853710f8f988dca27e","unresolved":false,"context_lines":[{"line_number":460,"context_line":"Net2 in Pod2 -\u003e Router1 in Pod2 -\u003e Net1 in Pod2 -\u003e L2GW in Pod2 ---\u003e L2GW in"},{"line_number":461,"context_line":"Pod1 -\u003e Net1 in Pod1."},{"line_number":462,"context_line":""},{"line_number":463,"context_line":"Note: The traffic for Net1 in Pod2 to Net1 in Pod1 can bypass the L2GW in Pod2,"},{"line_number":464,"context_line":"that means outbound traffic can bypass the L2GW, but inbound traffic can\u0027t"},{"line_number":465,"context_line":"bypass. It\u0027s up to the L2GW implementation. With the inbound traffic through"},{"line_number":466,"context_line":"L2GW, the inbound traffic to the VM will not be impacted by the VM migration"},{"line_number":467,"context_line":"from one host to another."},{"line_number":468,"context_line":""}],"source_content_type":"text/x-rst","patch_set":15,"id":"bab6814e_605b22f7","line":465,"range":{"start_line":463,"start_character":6,"end_line":465,"end_character":7},"updated":"2016-05-19 22:34:03.000000000","message":"outbound traffic bypass L2GW? do you mean \"pass L2GW\"? this outbound traffic means traffict out of one pod, right?","commit_id":"80beb849db0dfcb638aee1ee247fd4aa08c2f908"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"453236d7ef815749243e1f853710f8f988dca27e","unresolved":false,"context_lines":[{"line_number":476,"context_line":"Net1 in Pod1 -\u003e Router1 in Pod1 -\u003e Net2 in Pod1 -\u003e L2GW in Pod1 ---\u003e L2GW in"},{"line_number":477,"context_line":"Pod2 -\u003e Net2 in Pod2."},{"line_number":478,"context_line":""},{"line_number":479,"context_line":"To limit the complexity, one network’s az_hint can only be created with"},{"line_number":480,"context_line":"network, and no update is allowed, if az_hint need to be updated, you have to"},{"line_number":481,"context_line":"delete the network and create again."},{"line_number":482,"context_line":""},{"line_number":483,"context_line":"If the network can’t be expanded, then E-W bridge network is needed. For"}],"source_content_type":"text/x-rst","patch_set":15,"id":"bab6814e_20063a1d","line":480,"range":{"start_line":479,"start_character":59,"end_line":480,"end_character":7},"updated":"2016-05-19 22:34:03.000000000","message":"specified when creating","commit_id":"80beb849db0dfcb638aee1ee247fd4aa08c2f908"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"453236d7ef815749243e1f853710f8f988dca27e","unresolved":false,"context_lines":[{"line_number":484,"context_line":"example, Net1(AZ1, AZ2,AZ3), Router1; Net2(AZ4, AZ5, AZ6), Router1. Then"},{"line_number":485,"context_line":"a cross pod L2 bridge network has to be established:"},{"line_number":486,"context_line":""},{"line_number":487,"context_line":"Net1(AZ1, AZ2,AZ3), Router1 --\u003e E-W bridge network ---\u003e Router1,"},{"line_number":488,"context_line":"Net2(AZ4, AZ5, AZ6)."},{"line_number":489,"context_line":""},{"line_number":490,"context_line":"Assignee(s)"}],"source_content_type":"text/x-rst","patch_set":15,"id":"bab6814e_600cc23b","line":487,"range":{"start_line":487,"start_character":12,"end_line":487,"end_character":15},"updated":"2016-05-19 22:34:03.000000000","message":"add space","commit_id":"80beb849db0dfcb638aee1ee247fd4aa08c2f908"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"df18e00b834840e6d09f3c4fce50fe2f08d50ed2","unresolved":false,"context_lines":[{"line_number":470,"context_line":"Pod1 -\u003e Net1 in Pod1."},{"line_number":471,"context_line":""},{"line_number":472,"context_line":"Note: The traffic for Net1 in Pod2 to Net1 in Pod1 can bypass the L2GW in Pod2,"},{"line_number":473,"context_line":"that means outbound traffic can bypass the L2GW if the remove VTEP of L2GW is "},{"line_number":474,"context_line":"known to the local compute node and the packet from the local compute node with"},{"line_number":475,"context_line":"VxLAN encapsulation cloud be routed to remote L2GW directly. It\u0027s up to the"},{"line_number":476,"context_line":"L2GW implementation. With the inbound traffic through L2GW, the inbound traffic"}],"source_content_type":"text/x-rst","patch_set":20,"id":"bab6814e_6d659543","line":473,"range":{"start_line":473,"start_character":55,"end_line":473,"end_character":61},"updated":"2016-05-27 01:10:36.000000000","message":"remote, but not remove","commit_id":"3c812ebdc566c6d287f1bd17d1f4f2715873379b"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"df18e00b834840e6d09f3c4fce50fe2f08d50ed2","unresolved":false,"context_lines":[{"line_number":470,"context_line":"Pod1 -\u003e Net1 in Pod1."},{"line_number":471,"context_line":""},{"line_number":472,"context_line":"Note: The traffic for Net1 in Pod2 to Net1 in Pod1 can bypass the L2GW in Pod2,"},{"line_number":473,"context_line":"that means outbound traffic can bypass the L2GW if the remove VTEP of L2GW is "},{"line_number":474,"context_line":"known to the local compute node and the packet from the local compute node with"},{"line_number":475,"context_line":"VxLAN encapsulation cloud be routed to remote L2GW directly. It\u0027s up to the"},{"line_number":476,"context_line":"L2GW implementation. With the inbound traffic through L2GW, the inbound traffic"}],"source_content_type":"text/x-rst","patch_set":20,"id":"bab6814e_2df6ed5c","line":473,"range":{"start_line":473,"start_character":42,"end_line":473,"end_character":43},"updated":"2016-05-27 01:10:36.000000000","message":"the local L2GW","commit_id":"3c812ebdc566c6d287f1bd17d1f4f2715873379b"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"5b388c90b40f590010ff73ae556f438802e66de2","unresolved":false,"context_lines":[{"line_number":21,"context_line":"* XJob"},{"line_number":22,"context_line":"* DB"},{"line_number":23,"context_line":""},{"line_number":24,"context_line":"Please refer to the Tricircle design blueprint[1], especially from"},{"line_number":25,"context_line":"\u00277. Stateless Architecture Proposal\u0027 for the detail description of each"},{"line_number":26,"context_line":"components."},{"line_number":27,"context_line":""}],"source_content_type":"text/x-rst","patch_set":21,"id":"9abb7d3a_3d1eb1ba","line":24,"range":{"start_line":24,"start_character":0,"end_line":24,"end_character":6},"updated":"2016-05-28 05:13:06.000000000","message":"Why the short introduction of these components are removed,  it\u0027s difficult to understand the following processing of cross pod L2 networking without the context:\n\nNova APIGW is the functionality to trigger automatic networking creation when\nnew VMs are being provisioned. Neutron Tricircle plug-in is the functionality\nto create cross OpenStack L2/L3 networking for new VMs. After the binding of\ntenant-id and pod finished in the Tricircle, Cinder APIGW and Nova APIGW will\npass the cinder api or nova api request to appropriate bottom OpenStack.","commit_id":"6f4855a3d3dd4e4655e568965a3da5f4c77ed457"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"5b388c90b40f590010ff73ae556f438802e66de2","unresolved":false,"context_lines":[{"line_number":32,"context_line":"specify the \u0027availability_zone_hints\u0027(AZ or az will be used for short for"},{"line_number":33,"context_line":"availability zone) in network creation, in Tricircle, the"},{"line_number":34,"context_line":"\u0027az_hints\u0027 means which AZ the network should be spreaded into. It\u0027s a little"},{"line_number":35,"context_line":"different from [4] in Neutron. If no \u0027az_hints\u0027 was specified in network"},{"line_number":36,"context_line":"creation, then this network can be spreaded into any AZ. If there are a list"},{"line_number":37,"context_line":"of \u0027az_hints\u0027 in the network creation, that means the network should be able"},{"line_number":38,"context_line":"to spread into these AZs."}],"source_content_type":"text/x-rst","patch_set":21,"id":"9abb7d3a_bd88e1e8","line":35,"range":{"start_line":35,"start_character":18,"end_line":35,"end_character":19},"updated":"2016-05-28 05:13:06.000000000","message":"I find that all reference has been removed in this patch, reference should be provided","commit_id":"6f4855a3d3dd4e4655e568965a3da5f4c77ed457"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"5b388c90b40f590010ff73ae556f438802e66de2","unresolved":false,"context_lines":[{"line_number":77,"context_line":"* When a tenant\u0027s VMs are provisioned in different OpenStack instances, there"},{"line_number":78,"context_line":"  is E-W traffic for these VMs, the E-W traffic should be only visible to the"},{"line_number":79,"context_line":"  tenant, and isolation is needed. If the traffic goes through N-S via tenant"},{"line_number":80,"context_line":"  level VPN, then overhead is too much, and the orchestration for multiple"},{"line_number":81,"context_line":""},{"line_number":82,"context_line":"* When a tenant\u0027s VMs are provisioned in different OpenStack instances, there"},{"line_number":83,"context_line":"  is E-W traffic for these VMs, the E-W traffic should be only visible to the"}],"source_content_type":"text/x-rst","patch_set":21,"id":"9abb7d3a_fd6a6919","line":80,"range":{"start_line":80,"start_character":66,"end_line":80,"end_character":74},"updated":"2016-05-28 05:13:06.000000000","message":"what\u0027s missed after multiple ? This sentence is not complete","commit_id":"6f4855a3d3dd4e4655e568965a3da5f4c77ed457"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"5b388c90b40f590010ff73ae556f438802e66de2","unresolved":false,"context_lines":[{"line_number":160,"context_line":""},{"line_number":161,"context_line":"1.Type Driver under Tricircle Plugin in Neutron API server"},{"line_number":162,"context_line":""},{"line_number":163,"context_line":"* Type driver to distinguish different type of cross pod L2 networking. So"},{"line_number":164,"context_line":"* Type driver to allocate VxLAN segment id for shared VxLAN L2 networking."},{"line_number":165,"context_line":""},{"line_number":166,"context_line":"* Type driver for mixed VLAN/VxLAN to allocate VxLAN segment id for the"}],"source_content_type":"text/x-rst","patch_set":21,"id":"9abb7d3a_bd5f4171","line":163,"range":{"start_line":163,"start_character":72,"end_line":163,"end_character":74},"updated":"2016-05-28 05:13:06.000000000","message":"What\u0027s missing after the So? The sentence is not complete. Please go through the whole spec before you submit a patch.","commit_id":"6f4855a3d3dd4e4655e568965a3da5f4c77ed457"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"5b388c90b40f590010ff73ae556f438802e66de2","unresolved":false,"context_lines":[{"line_number":169,"context_line":"* Type driver for Local Network only updating ``network_type`` for the"},{"line_number":170,"context_line":"  network to DB."},{"line_number":171,"context_line":""},{"line_number":172,"context_line":"When create a network request is received in Neutron API Server in Tricircle,"},{"line_number":173,"context_line":"the type driver will be called according to the configured network type."},{"line_number":174,"context_line":""},{"line_number":175,"context_line":"2. Nova API-GW to trigger the bottom networking automation"}],"source_content_type":"text/x-rst","patch_set":21,"id":"9abb7d3a_5d4f35bd","line":172,"range":{"start_line":172,"start_character":6,"end_line":172,"end_character":21},"updated":"2016-05-28 05:13:06.000000000","message":"the last update \"a network creation\" is restored to the old version \"create a network\". The last one is better.","commit_id":"6f4855a3d3dd4e4655e568965a3da5f4c77ed457"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"5b388c90b40f590010ff73ae556f438802e66de2","unresolved":false,"context_lines":[{"line_number":182,"context_line":""},{"line_number":183,"context_line":"* Shared VLAN"},{"line_number":184,"context_line":"  Nova API-GW creates network in bottom pod where the VM will reside with the"},{"line_number":185,"context_line":"  VLAN segment id, network name and network type."},{"line_number":186,"context_line":""},{"line_number":187,"context_line":"* Shared VxLAN"},{"line_number":188,"context_line":"  Nova API-GW creates network in bottom pod where the VM will reside with the"}],"source_content_type":"text/x-rst","patch_set":21,"id":"9abb7d3a_1d03ed43","line":185,"range":{"start_line":185,"start_character":48,"end_line":185,"end_character":49},"updated":"2016-05-28 05:13:06.000000000","message":"I guess \"that retrieved from the Neutron\n  API server in the Tricircle.\" was removed unintentionly?","commit_id":"6f4855a3d3dd4e4655e568965a3da5f4c77ed457"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"5b388c90b40f590010ff73ae556f438802e66de2","unresolved":false,"context_lines":[{"line_number":187,"context_line":"* Shared VxLAN"},{"line_number":188,"context_line":"  Nova API-GW creates network in bottom pod where the VM will reside with the"},{"line_number":189,"context_line":"  VxLAN segment id, network name and network type which is retrieved from"},{"line_number":190,"context_line":"  Tricricle Neutron API server.After the network in the bottom created"},{"line_number":191,"context_line":"  successfully, need to make this network in the bottom pod as one of the"},{"line_number":192,"context_line":"  segments in the network in Tricircle."},{"line_number":193,"context_line":""}],"source_content_type":"text/x-rst","patch_set":21,"id":"9abb7d3a_fdff0932","line":190,"range":{"start_line":190,"start_character":31,"end_line":190,"end_character":36},"updated":"2016-05-28 05:13:06.000000000","message":"There was adding one blank space here last time, but now the space was removed.","commit_id":"6f4855a3d3dd4e4655e568965a3da5f4c77ed457"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"5b388c90b40f590010ff73ae556f438802e66de2","unresolved":false,"context_lines":[{"line_number":197,"context_line":"After the network in the bottom created successfully, need to retrieve the"},{"line_number":198,"context_line":"network information like segment id, network name and network type, and make"},{"line_number":199,"context_line":"this network in the bottom pod as one of the segments in the network in"},{"line_number":200,"context_line":"Tricircle."},{"line_number":201,"context_line":""},{"line_number":202,"context_line":"3. L2GW driver under Tricircle Plugin in Neutron API server"},{"line_number":203,"context_line":"Tricircle plugin needs to support multi-segment network extension[3]."}],"source_content_type":"text/x-rst","patch_set":21,"id":"9abb7d3a_bdd621c3","line":200,"range":{"start_line":200,"start_character":9,"end_line":200,"end_character":10},"updated":"2016-05-28 05:13:06.000000000","message":"The last patch is described as following with alignment, I guess you update with a wrong version of the patch. A lot of update was lost.\n\n  Nova API-GW creates network in different bottom pods where the VM will reside \n  with the VLAN or VxLAN segment id respectively, network name and network type\n  which is retrieved from Tricricle Neutron API server. After the network in the\n  bottom is created successfully, need to update network in top with the\n  segmentation information of bottom netwoks.","commit_id":"6f4855a3d3dd4e4655e568965a3da5f4c77ed457"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"5b388c90b40f590010ff73ae556f438802e66de2","unresolved":false,"context_lines":[{"line_number":514,"context_line":"Dependencies"},{"line_number":515,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":516,"context_line":""},{"line_number":517,"context_line":"None"}],"source_content_type":"text/x-rst","patch_set":21,"id":"9abb7d3a_9deebd89","line":517,"range":{"start_line":517,"start_character":0,"end_line":517,"end_character":4},"updated":"2016-05-28 05:13:06.000000000","message":"all reference has gone.... This patch need to update based latest one, but not wrong verison.","commit_id":"6f4855a3d3dd4e4655e568965a3da5f4c77ed457"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":9,"context_line":"multiple OpenStack instances which are running in one site or multiple sites"},{"line_number":10,"context_line":"as a single OpenStack cloud."},{"line_number":11,"context_line":""},{"line_number":12,"context_line":"Each bottom OpenStack which is managed by the Tricircle is also called a pod."},{"line_number":13,"context_line":""},{"line_number":14,"context_line":"The Tricircle has the following components:"},{"line_number":15,"context_line":""}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_120d943e","line":12,"range":{"start_line":12,"start_character":12,"end_line":12,"end_character":21},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: OpenStack instance","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":20,"context_line":"* XJob"},{"line_number":21,"context_line":"* DB"},{"line_number":22,"context_line":""},{"line_number":23,"context_line":"Nova APIGW is the functionality to trigger automatic networking creation when"},{"line_number":24,"context_line":"new VMs are being provisioned. Neutron Tricircle plug-in is the functionality"},{"line_number":25,"context_line":"to create cross OpenStack L2/L3 networking for new VMs. After the binding of"},{"line_number":26,"context_line":"tenant-id and pod finished in the Tricircle. Cinder APIGW and Nova APIGW will"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_726860f6","line":23,"range":{"start_line":23,"start_character":5,"end_line":23,"end_character":10},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: API-GW","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":23,"context_line":"Nova APIGW is the functionality to trigger automatic networking creation when"},{"line_number":24,"context_line":"new VMs are being provisioned. Neutron Tricircle plug-in is the functionality"},{"line_number":25,"context_line":"to create cross OpenStack L2/L3 networking for new VMs. After the binding of"},{"line_number":26,"context_line":"tenant-id and pod finished in the Tricircle. Cinder APIGW and Nova APIGW will"},{"line_number":27,"context_line":"pass the cinder api or nova api request to appropriate bottom OpenStack."},{"line_number":28,"context_line":""},{"line_number":29,"context_line":"Please refer to the Tricircle design blueprint[1], especially from"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_1278f4c3","line":26,"range":{"start_line":26,"start_character":67,"end_line":26,"end_character":72},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: API-GW","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":23,"context_line":"Nova APIGW is the functionality to trigger automatic networking creation when"},{"line_number":24,"context_line":"new VMs are being provisioned. Neutron Tricircle plug-in is the functionality"},{"line_number":25,"context_line":"to create cross OpenStack L2/L3 networking for new VMs. After the binding of"},{"line_number":26,"context_line":"tenant-id and pod finished in the Tricircle. Cinder APIGW and Nova APIGW will"},{"line_number":27,"context_line":"pass the cinder api or nova api request to appropriate bottom OpenStack."},{"line_number":28,"context_line":""},{"line_number":29,"context_line":"Please refer to the Tricircle design blueprint[1], especially from"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_b272c8e3","line":26,"range":{"start_line":26,"start_character":52,"end_line":26,"end_character":57},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: API-GW","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":24,"context_line":"new VMs are being provisioned. Neutron Tricircle plug-in is the functionality"},{"line_number":25,"context_line":"to create cross OpenStack L2/L3 networking for new VMs. After the binding of"},{"line_number":26,"context_line":"tenant-id and pod finished in the Tricircle. Cinder APIGW and Nova APIGW will"},{"line_number":27,"context_line":"pass the cinder api or nova api request to appropriate bottom OpenStack."},{"line_number":28,"context_line":""},{"line_number":29,"context_line":"Please refer to the Tricircle design blueprint[1], especially from"},{"line_number":30,"context_line":"\u00277. Stateless Architecture Proposal\u0027 for the detail description of each"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_f209f032","line":27,"range":{"start_line":27,"start_character":62,"end_line":27,"end_character":71},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: OpenStack instance","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":33,"context_line":""},{"line_number":34,"context_line":"Problem Description"},{"line_number":35,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":36,"context_line":"When an user wants to create a network in Neutron API Server, a user can"},{"line_number":37,"context_line":"specify the \u0027availability_zone_hints\u0027(AZ or az will be used for short for"},{"line_number":38,"context_line":"availability zone) in network creation[7], in Tricircle, the \u0027az_hints\u0027 means"},{"line_number":39,"context_line":"which AZ the network should be spreaded into. It\u0027s a little different"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_f27450d0","line":36,"range":{"start_line":36,"start_character":5,"end_line":36,"end_character":7},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: a","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19960,"name":"newypei","email":"newypei@gmail.com","username":"newypei"},"change_message_id":"273ac79bb078d93de52c5dbedff9b7710209ae95","unresolved":false,"context_lines":[{"line_number":33,"context_line":""},{"line_number":34,"context_line":"Problem Description"},{"line_number":35,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":36,"context_line":"When an user wants to create a network in Neutron API Server, a user can"},{"line_number":37,"context_line":"specify the \u0027availability_zone_hints\u0027(AZ or az will be used for short for"},{"line_number":38,"context_line":"availability zone) in network creation[7], in Tricircle, the \u0027az_hints\u0027 means"},{"line_number":39,"context_line":"which AZ the network should be spreaded into. It\u0027s a little different"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_56d9c282","line":36,"range":{"start_line":36,"start_character":62,"end_line":36,"end_character":63},"updated":"2016-05-30 03:45:29.000000000","message":"the","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":35,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":36,"context_line":"When an user wants to create a network in Neutron API Server, a user can"},{"line_number":37,"context_line":"specify the \u0027availability_zone_hints\u0027(AZ or az will be used for short for"},{"line_number":38,"context_line":"availability zone) in network creation[7], in Tricircle, the \u0027az_hints\u0027 means"},{"line_number":39,"context_line":"which AZ the network should be spreaded into. It\u0027s a little different"},{"line_number":40,"context_line":"from[4] in Neutron. If no \u0027az_hints\u0027 was specified in network creation,"},{"line_number":41,"context_line":"then this network can be spreaded into any AZ. If there are a list of"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_327ff8ab","line":38,"range":{"start_line":38,"start_character":19,"end_line":38,"end_character":21},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: during","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":35,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":36,"context_line":"When an user wants to create a network in Neutron API Server, a user can"},{"line_number":37,"context_line":"specify the \u0027availability_zone_hints\u0027(AZ or az will be used for short for"},{"line_number":38,"context_line":"availability zone) in network creation[7], in Tricircle, the \u0027az_hints\u0027 means"},{"line_number":39,"context_line":"which AZ the network should be spreaded into. It\u0027s a little different"},{"line_number":40,"context_line":"from[4] in Neutron. If no \u0027az_hints\u0027 was specified in network creation,"},{"line_number":41,"context_line":"then this network can be spreaded into any AZ. If there are a list of"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_924a2482","line":38,"range":{"start_line":38,"start_character":46,"end_line":38,"end_character":55},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: the Tricircle","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":34,"context_line":"Problem Description"},{"line_number":35,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":36,"context_line":"When an user wants to create a network in Neutron API Server, a user can"},{"line_number":37,"context_line":"specify the \u0027availability_zone_hints\u0027(AZ or az will be used for short for"},{"line_number":38,"context_line":"availability zone) in network creation[7], in Tricircle, the \u0027az_hints\u0027 means"},{"line_number":39,"context_line":"which AZ the network should be spreaded into. It\u0027s a little different"},{"line_number":40,"context_line":"from[4] in Neutron. If no \u0027az_hints\u0027 was specified in network creation,"},{"line_number":41,"context_line":"then this network can be spreaded into any AZ. If there are a list of"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_52827c95","line":38,"range":{"start_line":37,"start_character":37,"end_line":38,"end_character":18},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: which will be used for decision of availability zone.","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"4efe21caa774909cd7b53e151044be8a932a01ed","unresolved":false,"context_lines":[{"line_number":34,"context_line":"Problem Description"},{"line_number":35,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":36,"context_line":"When an user wants to create a network in Neutron API Server, a user can"},{"line_number":37,"context_line":"specify the \u0027availability_zone_hints\u0027(AZ or az will be used for short for"},{"line_number":38,"context_line":"availability zone) in network creation[7], in Tricircle, the \u0027az_hints\u0027 means"},{"line_number":39,"context_line":"which AZ the network should be spreaded into. It\u0027s a little different"},{"line_number":40,"context_line":"from[4] in Neutron. If no \u0027az_hints\u0027 was specified in network creation,"},{"line_number":41,"context_line":"then this network can be spreaded into any AZ. If there are a list of"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_fc7c2222","line":38,"range":{"start_line":37,"start_character":37,"end_line":38,"end_character":18},"in_reply_to":"9abb7d3a_52827c95","updated":"2016-05-30 05:15:52.000000000","message":"I think the best describe is AZ.","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":37,"context_line":"specify the \u0027availability_zone_hints\u0027(AZ or az will be used for short for"},{"line_number":38,"context_line":"availability zone) in network creation[7], in Tricircle, the \u0027az_hints\u0027 means"},{"line_number":39,"context_line":"which AZ the network should be spreaded into. It\u0027s a little different"},{"line_number":40,"context_line":"from[4] in Neutron. If no \u0027az_hints\u0027 was specified in network creation,"},{"line_number":41,"context_line":"then this network can be spreaded into any AZ. If there are a list of"},{"line_number":42,"context_line":"\u0027az_hints\u0027 in the network creation, that means the network should be able"},{"line_number":43,"context_line":"to be spread into these AZs."}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_d244ac75","line":40,"range":{"start_line":40,"start_character":51,"end_line":40,"end_character":53},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: during","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":36,"context_line":"When an user wants to create a network in Neutron API Server, a user can"},{"line_number":37,"context_line":"specify the \u0027availability_zone_hints\u0027(AZ or az will be used for short for"},{"line_number":38,"context_line":"availability zone) in network creation[7], in Tricircle, the \u0027az_hints\u0027 means"},{"line_number":39,"context_line":"which AZ the network should be spreaded into. It\u0027s a little different"},{"line_number":40,"context_line":"from[4] in Neutron. If no \u0027az_hints\u0027 was specified in network creation,"},{"line_number":41,"context_line":"then this network can be spreaded into any AZ. If there are a list of"},{"line_number":42,"context_line":"\u0027az_hints\u0027 in the network creation, that means the network should be able"},{"line_number":43,"context_line":"to be spread into these AZs."}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_724fc092","line":40,"range":{"start_line":39,"start_character":60,"end_line":40,"end_character":4},"updated":"2016-05-29 01:49:51.000000000","message":"different from \u0027what\u0027?\nIt would be better to describe this using specific words.\n\nTo show \u0027[4]\u0027 without anything is not good practice.","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"4efe21caa774909cd7b53e151044be8a932a01ed","unresolved":false,"context_lines":[{"line_number":36,"context_line":"When an user wants to create a network in Neutron API Server, a user can"},{"line_number":37,"context_line":"specify the \u0027availability_zone_hints\u0027(AZ or az will be used for short for"},{"line_number":38,"context_line":"availability zone) in network creation[7], in Tricircle, the \u0027az_hints\u0027 means"},{"line_number":39,"context_line":"which AZ the network should be spreaded into. It\u0027s a little different"},{"line_number":40,"context_line":"from[4] in Neutron. If no \u0027az_hints\u0027 was specified in network creation,"},{"line_number":41,"context_line":"then this network can be spreaded into any AZ. If there are a list of"},{"line_number":42,"context_line":"\u0027az_hints\u0027 in the network creation, that means the network should be able"},{"line_number":43,"context_line":"to be spread into these AZs."}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_9c9eb654","line":40,"range":{"start_line":39,"start_character":60,"end_line":40,"end_character":4},"in_reply_to":"9abb7d3a_724fc092","updated":"2016-05-30 05:15:52.000000000","message":"Can we describe like this：\n\ndifferent from the network multiple provider extension[4] in Neutron","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":38,"context_line":"availability zone) in network creation[7], in Tricircle, the \u0027az_hints\u0027 means"},{"line_number":39,"context_line":"which AZ the network should be spreaded into. It\u0027s a little different"},{"line_number":40,"context_line":"from[4] in Neutron. If no \u0027az_hints\u0027 was specified in network creation,"},{"line_number":41,"context_line":"then this network can be spreaded into any AZ. If there are a list of"},{"line_number":42,"context_line":"\u0027az_hints\u0027 in the network creation, that means the network should be able"},{"line_number":43,"context_line":"to be spread into these AZs."},{"line_number":44,"context_line":""}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_125f5442","line":41,"range":{"start_line":41,"start_character":5,"end_line":41,"end_character":45},"updated":"2016-05-29 01:49:51.000000000","message":"Considering context in \u0027If\u0027, this sentence is a bit hard to understand for readers.","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":38,"context_line":"availability zone) in network creation[7], in Tricircle, the \u0027az_hints\u0027 means"},{"line_number":39,"context_line":"which AZ the network should be spreaded into. It\u0027s a little different"},{"line_number":40,"context_line":"from[4] in Neutron. If no \u0027az_hints\u0027 was specified in network creation,"},{"line_number":41,"context_line":"then this network can be spreaded into any AZ. If there are a list of"},{"line_number":42,"context_line":"\u0027az_hints\u0027 in the network creation, that means the network should be able"},{"line_number":43,"context_line":"to be spread into these AZs."},{"line_number":44,"context_line":""}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_b249288e","line":41,"range":{"start_line":41,"start_character":0,"end_line":41,"end_character":4},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: delete \u0027then\u0027","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":38,"context_line":"availability zone) in network creation[7], in Tricircle, the \u0027az_hints\u0027 means"},{"line_number":39,"context_line":"which AZ the network should be spreaded into. It\u0027s a little different"},{"line_number":40,"context_line":"from[4] in Neutron. If no \u0027az_hints\u0027 was specified in network creation,"},{"line_number":41,"context_line":"then this network can be spreaded into any AZ. If there are a list of"},{"line_number":42,"context_line":"\u0027az_hints\u0027 in the network creation, that means the network should be able"},{"line_number":43,"context_line":"to be spread into these AZs."},{"line_number":44,"context_line":""}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_f25bb052","line":41,"range":{"start_line":41,"start_character":56,"end_line":41,"end_character":59},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: is","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"4efe21caa774909cd7b53e151044be8a932a01ed","unresolved":false,"context_lines":[{"line_number":38,"context_line":"availability zone) in network creation[7], in Tricircle, the \u0027az_hints\u0027 means"},{"line_number":39,"context_line":"which AZ the network should be spreaded into. It\u0027s a little different"},{"line_number":40,"context_line":"from[4] in Neutron. If no \u0027az_hints\u0027 was specified in network creation,"},{"line_number":41,"context_line":"then this network can be spreaded into any AZ. If there are a list of"},{"line_number":42,"context_line":"\u0027az_hints\u0027 in the network creation, that means the network should be able"},{"line_number":43,"context_line":"to be spread into these AZs."},{"line_number":44,"context_line":""}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_dc795e31","line":41,"range":{"start_line":41,"start_character":5,"end_line":41,"end_character":45},"in_reply_to":"9abb7d3a_125f5442","updated":"2016-05-30 05:15:52.000000000","message":"should we change this sentence like this:\n\nIf no \u0027az_hints\u0027 was specified during network creation，this created network will be spreaded into any AZ","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":39,"context_line":"which AZ the network should be spreaded into. It\u0027s a little different"},{"line_number":40,"context_line":"from[4] in Neutron. If no \u0027az_hints\u0027 was specified in network creation,"},{"line_number":41,"context_line":"then this network can be spreaded into any AZ. If there are a list of"},{"line_number":42,"context_line":"\u0027az_hints\u0027 in the network creation, that means the network should be able"},{"line_number":43,"context_line":"to be spread into these AZs."},{"line_number":44,"context_line":""},{"line_number":45,"context_line":"When an user creates VM or Volume, there is also one parameter called"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_5259dc59","line":42,"range":{"start_line":42,"start_character":11,"end_line":42,"end_character":13},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: during","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":40,"context_line":"from[4] in Neutron. If no \u0027az_hints\u0027 was specified in network creation,"},{"line_number":41,"context_line":"then this network can be spreaded into any AZ. If there are a list of"},{"line_number":42,"context_line":"\u0027az_hints\u0027 in the network creation, that means the network should be able"},{"line_number":43,"context_line":"to be spread into these AZs."},{"line_number":44,"context_line":""},{"line_number":45,"context_line":"When an user creates VM or Volume, there is also one parameter called"},{"line_number":46,"context_line":"availability zone. The AZ parameter is used for Volume and VM co-location, so"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_3256d829","line":43,"range":{"start_line":43,"start_character":18,"end_line":43,"end_character":27},"updated":"2016-05-29 01:49:51.000000000","message":"Where is it pointing to?\nIt would be probably better to add more explanation using \u0027which\u0027.\n\ne.g.,\n... to be spread into these AZs which are suggested by a list of az_hints.","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19960,"name":"newypei","email":"newypei@gmail.com","username":"newypei"},"change_message_id":"273ac79bb078d93de52c5dbedff9b7710209ae95","unresolved":false,"context_lines":[{"line_number":40,"context_line":"from[4] in Neutron. If no \u0027az_hints\u0027 was specified in network creation,"},{"line_number":41,"context_line":"then this network can be spreaded into any AZ. If there are a list of"},{"line_number":42,"context_line":"\u0027az_hints\u0027 in the network creation, that means the network should be able"},{"line_number":43,"context_line":"to be spread into these AZs."},{"line_number":44,"context_line":""},{"line_number":45,"context_line":"When an user creates VM or Volume, there is also one parameter called"},{"line_number":46,"context_line":"availability zone. The AZ parameter is used for Volume and VM co-location, so"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_b6e8ee11","line":43,"range":{"start_line":43,"start_character":6,"end_line":43,"end_character":12},"updated":"2016-05-30 03:45:29.000000000","message":"spreaded","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"4efe21caa774909cd7b53e151044be8a932a01ed","unresolved":false,"context_lines":[{"line_number":40,"context_line":"from[4] in Neutron. If no \u0027az_hints\u0027 was specified in network creation,"},{"line_number":41,"context_line":"then this network can be spreaded into any AZ. If there are a list of"},{"line_number":42,"context_line":"\u0027az_hints\u0027 in the network creation, that means the network should be able"},{"line_number":43,"context_line":"to be spread into these AZs."},{"line_number":44,"context_line":""},{"line_number":45,"context_line":"When an user creates VM or Volume, there is also one parameter called"},{"line_number":46,"context_line":"availability zone. The AZ parameter is used for Volume and VM co-location, so"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_3cc50a3c","line":43,"range":{"start_line":43,"start_character":18,"end_line":43,"end_character":27},"in_reply_to":"9abb7d3a_3256d829","updated":"2016-05-30 05:15:52.000000000","message":"OK！ i will change this sentence.","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"8596770f3e4c9c59e9c58a1652c0e690e838f986","unresolved":false,"context_lines":[{"line_number":40,"context_line":"from[4] in Neutron. If no \u0027az_hints\u0027 was specified in network creation,"},{"line_number":41,"context_line":"then this network can be spreaded into any AZ. If there are a list of"},{"line_number":42,"context_line":"\u0027az_hints\u0027 in the network creation, that means the network should be able"},{"line_number":43,"context_line":"to be spread into these AZs."},{"line_number":44,"context_line":""},{"line_number":45,"context_line":"When an user creates VM or Volume, there is also one parameter called"},{"line_number":46,"context_line":"availability zone. The AZ parameter is used for Volume and VM co-location, so"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_d6a492ba","line":43,"range":{"start_line":43,"start_character":6,"end_line":43,"end_character":12},"in_reply_to":"9abb7d3a_b6e8ee11","updated":"2016-05-30 03:52:42.000000000","message":"\u0027spread\u0027 is fine.\n\nhttp://www.thefreedictionary.com/spread","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":42,"context_line":"\u0027az_hints\u0027 in the network creation, that means the network should be able"},{"line_number":43,"context_line":"to be spread into these AZs."},{"line_number":44,"context_line":""},{"line_number":45,"context_line":"When an user creates VM or Volume, there is also one parameter called"},{"line_number":46,"context_line":"availability zone. The AZ parameter is used for Volume and VM co-location, so"},{"line_number":47,"context_line":"that the Volume and VM will be created into same bottom OpenStack instance."},{"line_number":48,"context_line":""}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_122634ce","line":45,"range":{"start_line":45,"start_character":5,"end_line":45,"end_character":7},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: a","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":46,"context_line":"availability zone. The AZ parameter is used for Volume and VM co-location, so"},{"line_number":47,"context_line":"that the Volume and VM will be created into same bottom OpenStack instance."},{"line_number":48,"context_line":""},{"line_number":49,"context_line":"When a VM is attached to a network, the Tricircle will check whether the VM\u0027s"},{"line_number":50,"context_line":"AZ is inside in the network\u0027s AZs scope. If the VM is not in the network\u0027s AZs"},{"line_number":51,"context_line":"scope, the VM creation will be rejected."},{"line_number":52,"context_line":""}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_86ff8900","line":49,"range":{"start_line":49,"start_character":5,"end_line":49,"end_character":21},"updated":"2016-05-29 01:49:51.000000000","message":"I have to be honest here.\n\u0027a VM is being attached\u0027 is more precise.","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":46,"context_line":"availability zone. The AZ parameter is used for Volume and VM co-location, so"},{"line_number":47,"context_line":"that the Volume and VM will be created into same bottom OpenStack instance."},{"line_number":48,"context_line":""},{"line_number":49,"context_line":"When a VM is attached to a network, the Tricircle will check whether the VM\u0027s"},{"line_number":50,"context_line":"AZ is inside in the network\u0027s AZs scope. If the VM is not in the network\u0027s AZs"},{"line_number":51,"context_line":"scope, the VM creation will be rejected."},{"line_number":52,"context_line":""}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_c609912e","line":49,"range":{"start_line":49,"start_character":69,"end_line":49,"end_character":72},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: a","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":47,"context_line":"that the Volume and VM will be created into same bottom OpenStack instance."},{"line_number":48,"context_line":""},{"line_number":49,"context_line":"When a VM is attached to a network, the Tricircle will check whether the VM\u0027s"},{"line_number":50,"context_line":"AZ is inside in the network\u0027s AZs scope. If the VM is not in the network\u0027s AZs"},{"line_number":51,"context_line":"scope, the VM creation will be rejected."},{"line_number":52,"context_line":""},{"line_number":53,"context_line":"Currently, the Tricircle only supports one pod in one AZ. And only supports a"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_66042515","line":50,"range":{"start_line":50,"start_character":44,"end_line":50,"end_character":47},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: a","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":52,"context_line":""},{"line_number":53,"context_line":"Currently, the Tricircle only supports one pod in one AZ. And only supports a"},{"line_number":54,"context_line":"network associated with one AZ. That means currently a tenant\u0027s network will"},{"line_number":55,"context_line":"be presented only in one bottom OpenStack, that also means all VMs connected"},{"line_number":56,"context_line":"to the network will be located inside one bottom OpenStack."},{"line_number":57,"context_line":""},{"line_number":58,"context_line":"But there are lots of use cases need a network being able to spread into"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_06143942","line":55,"range":{"start_line":55,"start_character":32,"end_line":55,"end_character":41},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: OpenStack instance","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":53,"context_line":"Currently, the Tricircle only supports one pod in one AZ. And only supports a"},{"line_number":54,"context_line":"network associated with one AZ. That means currently a tenant\u0027s network will"},{"line_number":55,"context_line":"be presented only in one bottom OpenStack, that also means all VMs connected"},{"line_number":56,"context_line":"to the network will be located inside one bottom OpenStack."},{"line_number":57,"context_line":""},{"line_number":58,"context_line":"But there are lots of use cases need a network being able to spread into"},{"line_number":59,"context_line":"multiple bottom pods in one AZ or multiple AZs."}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_e6101551","line":56,"range":{"start_line":56,"start_character":49,"end_line":56,"end_character":58},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: OpenStack instance","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":53,"context_line":"Currently, the Tricircle only supports one pod in one AZ. And only supports a"},{"line_number":54,"context_line":"network associated with one AZ. That means currently a tenant\u0027s network will"},{"line_number":55,"context_line":"be presented only in one bottom OpenStack, that also means all VMs connected"},{"line_number":56,"context_line":"to the network will be located inside one bottom OpenStack."},{"line_number":57,"context_line":""},{"line_number":58,"context_line":"But there are lots of use cases need a network being able to spread into"},{"line_number":59,"context_line":"multiple bottom pods in one AZ or multiple AZs."}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_461e4164","line":56,"range":{"start_line":56,"start_character":31,"end_line":56,"end_character":37},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: at","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":55,"context_line":"be presented only in one bottom OpenStack, that also means all VMs connected"},{"line_number":56,"context_line":"to the network will be located inside one bottom OpenStack."},{"line_number":57,"context_line":""},{"line_number":58,"context_line":"But there are lots of use cases need a network being able to spread into"},{"line_number":59,"context_line":"multiple bottom pods in one AZ or multiple AZs."},{"line_number":60,"context_line":""},{"line_number":61,"context_line":"* Capacity expansion: as tenants add VMs more and more, the capacity of one"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_261b3d74","line":58,"range":{"start_line":58,"start_character":58,"end_line":58,"end_character":67},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: to be spread out","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19960,"name":"newypei","email":"newypei@gmail.com","username":"newypei"},"change_message_id":"273ac79bb078d93de52c5dbedff9b7710209ae95","unresolved":false,"context_lines":[{"line_number":55,"context_line":"be presented only in one bottom OpenStack, that also means all VMs connected"},{"line_number":56,"context_line":"to the network will be located inside one bottom OpenStack."},{"line_number":57,"context_line":""},{"line_number":58,"context_line":"But there are lots of use cases need a network being able to spread into"},{"line_number":59,"context_line":"multiple bottom pods in one AZ or multiple AZs."},{"line_number":60,"context_line":""},{"line_number":61,"context_line":"* Capacity expansion: as tenants add VMs more and more, the capacity of one"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_96e32a33","line":58,"range":{"start_line":58,"start_character":31,"end_line":58,"end_character":37},"updated":"2016-05-30 03:45:29.000000000","message":"where a tenant needs","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":56,"context_line":"to the network will be located inside one bottom OpenStack."},{"line_number":57,"context_line":""},{"line_number":58,"context_line":"But there are lots of use cases need a network being able to spread into"},{"line_number":59,"context_line":"multiple bottom pods in one AZ or multiple AZs."},{"line_number":60,"context_line":""},{"line_number":61,"context_line":"* Capacity expansion: as tenants add VMs more and more, the capacity of one"},{"line_number":62,"context_line":"  OpenStack may be not enough, then new OpenStack instance has to be added"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_862669b8","line":59,"range":{"start_line":59,"start_character":16,"end_line":59,"end_character":20},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: OpenStack instances","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":58,"context_line":"But there are lots of use cases need a network being able to spread into"},{"line_number":59,"context_line":"multiple bottom pods in one AZ or multiple AZs."},{"line_number":60,"context_line":""},{"line_number":61,"context_line":"* Capacity expansion: as tenants add VMs more and more, the capacity of one"},{"line_number":62,"context_line":"  OpenStack may be not enough, then new OpenStack instance has to be added"},{"line_number":63,"context_line":"  to the cloud. The tenants still want to attach VMs to the existing network."},{"line_number":64,"context_line":""}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_662b8583","line":61,"range":{"start_line":61,"start_character":22,"end_line":61,"end_character":24},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: delete \u0027as\u0027\nor\nAdd subject before \u0027add\u0027","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":59,"context_line":"multiple bottom pods in one AZ or multiple AZs."},{"line_number":60,"context_line":""},{"line_number":61,"context_line":"* Capacity expansion: as tenants add VMs more and more, the capacity of one"},{"line_number":62,"context_line":"  OpenStack may be not enough, then new OpenStack instance has to be added"},{"line_number":63,"context_line":"  to the cloud. The tenants still want to attach VMs to the existing network."},{"line_number":64,"context_line":""},{"line_number":65,"context_line":"* Cross OpenStack network service chaining. Service chaining is based on"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_a6256dac","line":62,"range":{"start_line":62,"start_character":36,"end_line":62,"end_character":39},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: a new","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":59,"context_line":"multiple bottom pods in one AZ or multiple AZs."},{"line_number":60,"context_line":""},{"line_number":61,"context_line":"* Capacity expansion: as tenants add VMs more and more, the capacity of one"},{"line_number":62,"context_line":"  OpenStack may be not enough, then new OpenStack instance has to be added"},{"line_number":63,"context_line":"  to the cloud. The tenants still want to attach VMs to the existing network."},{"line_number":64,"context_line":""},{"line_number":65,"context_line":"* Cross OpenStack network service chaining. Service chaining is based on"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_c620719e","line":62,"range":{"start_line":62,"start_character":16,"end_line":62,"end_character":22},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: not be","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":60,"context_line":""},{"line_number":61,"context_line":"* Capacity expansion: as tenants add VMs more and more, the capacity of one"},{"line_number":62,"context_line":"  OpenStack may be not enough, then new OpenStack instance has to be added"},{"line_number":63,"context_line":"  to the cloud. The tenants still want to attach VMs to the existing network."},{"line_number":64,"context_line":""},{"line_number":65,"context_line":"* Cross OpenStack network service chaining. Service chaining is based on"},{"line_number":66,"context_line":"  the port-pairs. Leveraging the cross pod L2 networking capability which"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_063b99d2","line":63,"range":{"start_line":63,"start_character":16,"end_line":63,"end_character":77},"updated":"2016-05-29 01:49:51.000000000","message":"Probably this sentence would not be necessary here.\nBecause we are talking about VM creation in this context.","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":64,"context_line":""},{"line_number":65,"context_line":"* Cross OpenStack network service chaining. Service chaining is based on"},{"line_number":66,"context_line":"  the port-pairs. Leveraging the cross pod L2 networking capability which"},{"line_number":67,"context_line":"  provided by the Tricircle, the chaining could also be done by across sites."},{"line_number":68,"context_line":"  For example, vRouter1 in pod1, but vRouter2 in pod2, these two VMs"},{"line_number":69,"context_line":"  could be chained."},{"line_number":70,"context_line":""}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_e63775e1","line":67,"range":{"start_line":67,"start_character":2,"end_line":67,"end_character":10},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: is provided","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":64,"context_line":""},{"line_number":65,"context_line":"* Cross OpenStack network service chaining. Service chaining is based on"},{"line_number":66,"context_line":"  the port-pairs. Leveraging the cross pod L2 networking capability which"},{"line_number":67,"context_line":"  provided by the Tricircle, the chaining could also be done by across sites."},{"line_number":68,"context_line":"  For example, vRouter1 in pod1, but vRouter2 in pod2, these two VMs"},{"line_number":69,"context_line":"  could be chained."},{"line_number":70,"context_line":""}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_26321df2","line":67,"range":{"start_line":67,"start_character":71,"end_line":67,"end_character":76},"updated":"2016-05-29 01:49:51.000000000","message":"sites?\n\nHow do we define this word?","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"4efe21caa774909cd7b53e151044be8a932a01ed","unresolved":false,"context_lines":[{"line_number":64,"context_line":""},{"line_number":65,"context_line":"* Cross OpenStack network service chaining. Service chaining is based on"},{"line_number":66,"context_line":"  the port-pairs. Leveraging the cross pod L2 networking capability which"},{"line_number":67,"context_line":"  provided by the Tricircle, the chaining could also be done by across sites."},{"line_number":68,"context_line":"  For example, vRouter1 in pod1, but vRouter2 in pod2, these two VMs"},{"line_number":69,"context_line":"  could be chained."},{"line_number":70,"context_line":""}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_ba445a74","line":67,"range":{"start_line":67,"start_character":71,"end_line":67,"end_character":76},"in_reply_to":"9abb7d3a_26321df2","updated":"2016-05-30 05:15:52.000000000","message":"The definition of site can refers the definition of geo-location in Wiki.","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":65,"context_line":"* Cross OpenStack network service chaining. Service chaining is based on"},{"line_number":66,"context_line":"  the port-pairs. Leveraging the cross pod L2 networking capability which"},{"line_number":67,"context_line":"  provided by the Tricircle, the chaining could also be done by across sites."},{"line_number":68,"context_line":"  For example, vRouter1 in pod1, but vRouter2 in pod2, these two VMs"},{"line_number":69,"context_line":"  could be chained."},{"line_number":70,"context_line":""},{"line_number":71,"context_line":"* Applications are often encouraged to run in different availability zones to"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_66526515","line":68,"range":{"start_line":68,"start_character":15,"end_line":68,"end_character":23},"updated":"2016-05-29 01:49:51.000000000","message":"vRouter?\n\nHow do we define this word?","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"4efe21caa774909cd7b53e151044be8a932a01ed","unresolved":false,"context_lines":[{"line_number":65,"context_line":"* Cross OpenStack network service chaining. Service chaining is based on"},{"line_number":66,"context_line":"  the port-pairs. Leveraging the cross pod L2 networking capability which"},{"line_number":67,"context_line":"  provided by the Tricircle, the chaining could also be done by across sites."},{"line_number":68,"context_line":"  For example, vRouter1 in pod1, but vRouter2 in pod2, these two VMs"},{"line_number":69,"context_line":"  could be chained."},{"line_number":70,"context_line":""},{"line_number":71,"context_line":"* Applications are often encouraged to run in different availability zones to"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_5a68cef5","line":68,"range":{"start_line":68,"start_character":15,"end_line":68,"end_character":23},"in_reply_to":"9abb7d3a_66526515","updated":"2016-05-30 05:15:52.000000000","message":"virtualized router","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19960,"name":"newypei","email":"newypei@gmail.com","username":"newypei"},"change_message_id":"273ac79bb078d93de52c5dbedff9b7710209ae95","unresolved":false,"context_lines":[{"line_number":66,"context_line":"  the port-pairs. Leveraging the cross pod L2 networking capability which"},{"line_number":67,"context_line":"  provided by the Tricircle, the chaining could also be done by across sites."},{"line_number":68,"context_line":"  For example, vRouter1 in pod1, but vRouter2 in pod2, these two VMs"},{"line_number":69,"context_line":"  could be chained."},{"line_number":70,"context_line":""},{"line_number":71,"context_line":"* Applications are often encouraged to run in different availability zones to"},{"line_number":72,"context_line":"  achieve higher reliability. Application may (already) be designed as"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_f6d0b655","line":69,"range":{"start_line":69,"start_character":11,"end_line":69,"end_character":18},"updated":"2016-05-30 03:45:29.000000000","message":"what is service chain? like VNF chain?","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":68,"context_line":"  For example, vRouter1 in pod1, but vRouter2 in pod2, these two VMs"},{"line_number":69,"context_line":"  could be chained."},{"line_number":70,"context_line":""},{"line_number":71,"context_line":"* Applications are often encouraged to run in different availability zones to"},{"line_number":72,"context_line":"  achieve higher reliability. Application may (already) be designed as"},{"line_number":73,"context_line":"  Active-Standby/Active-Active/N-Way to achieve high availability, and some"},{"line_number":74,"context_line":"  components inside one application are designed to work as distributed"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_e63e55b7","line":71,"range":{"start_line":71,"start_character":25,"end_line":71,"end_character":35},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: required","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":69,"context_line":"  could be chained."},{"line_number":70,"context_line":""},{"line_number":71,"context_line":"* Applications are often encouraged to run in different availability zones to"},{"line_number":72,"context_line":"  achieve higher reliability. Application may (already) be designed as"},{"line_number":73,"context_line":"  Active-Standby/Active-Active/N-Way to achieve high availability, and some"},{"line_number":74,"context_line":"  components inside one application are designed to work as distributed"},{"line_number":75,"context_line":"  cluster, this design typically leads to state replication or heart"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_464c8170","line":72,"range":{"start_line":72,"start_character":10,"end_line":72,"end_character":28},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: high availability","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":69,"context_line":"  could be chained."},{"line_number":70,"context_line":""},{"line_number":71,"context_line":"* Applications are often encouraged to run in different availability zones to"},{"line_number":72,"context_line":"  achieve higher reliability. Application may (already) be designed as"},{"line_number":73,"context_line":"  Active-Standby/Active-Active/N-Way to achieve high availability, and some"},{"line_number":74,"context_line":"  components inside one application are designed to work as distributed"},{"line_number":75,"context_line":"  cluster, this design typically leads to state replication or heart"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_8674a99c","line":72,"range":{"start_line":72,"start_character":42,"end_line":72,"end_character":55},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: needs to","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":70,"context_line":""},{"line_number":71,"context_line":"* Applications are often encouraged to run in different availability zones to"},{"line_number":72,"context_line":"  achieve higher reliability. Application may (already) be designed as"},{"line_number":73,"context_line":"  Active-Standby/Active-Active/N-Way to achieve high availability, and some"},{"line_number":74,"context_line":"  components inside one application are designed to work as distributed"},{"line_number":75,"context_line":"  cluster, this design typically leads to state replication or heart"},{"line_number":76,"context_line":"  beat among application components (directly or via replicated database"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_6679c593","line":73,"range":{"start_line":73,"start_character":31,"end_line":73,"end_character":36},"updated":"2016-05-29 01:49:51.000000000","message":"How do we define \"N-Way\"?\nI updated blueprint because this description is not describing precisely.","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":70,"context_line":""},{"line_number":71,"context_line":"* Applications are often encouraged to run in different availability zones to"},{"line_number":72,"context_line":"  achieve higher reliability. Application may (already) be designed as"},{"line_number":73,"context_line":"  Active-Standby/Active-Active/N-Way to achieve high availability, and some"},{"line_number":74,"context_line":"  components inside one application are designed to work as distributed"},{"line_number":75,"context_line":"  cluster, this design typically leads to state replication or heart"},{"line_number":76,"context_line":"  beat among application components (directly or via replicated database"},{"line_number":77,"context_line":"  services, or via private designed message format). When this kind of"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_c66eb1c8","line":74,"range":{"start_line":73,"start_character":71,"end_line":74,"end_character":35},"updated":"2016-05-29 01:49:51.000000000","message":"Can we describe this description more elaborately?","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"4efe21caa774909cd7b53e151044be8a932a01ed","unresolved":false,"context_lines":[{"line_number":70,"context_line":""},{"line_number":71,"context_line":"* Applications are often encouraged to run in different availability zones to"},{"line_number":72,"context_line":"  achieve higher reliability. Application may (already) be designed as"},{"line_number":73,"context_line":"  Active-Standby/Active-Active/N-Way to achieve high availability, and some"},{"line_number":74,"context_line":"  components inside one application are designed to work as distributed"},{"line_number":75,"context_line":"  cluster, this design typically leads to state replication or heart"},{"line_number":76,"context_line":"  beat among application components (directly or via replicated database"},{"line_number":77,"context_line":"  services, or via private designed message format). When this kind of"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_35ba3d24","line":74,"range":{"start_line":73,"start_character":71,"end_line":74,"end_character":35},"in_reply_to":"9abb7d3a_c66eb1c8","updated":"2016-05-30 05:15:52.000000000","message":"can we describe this description like this:\n\nthis kind of application usually contains some components which are designed to work as distributed cluster and allocated to different zone.","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":72,"context_line":"  achieve higher reliability. Application may (already) be designed as"},{"line_number":73,"context_line":"  Active-Standby/Active-Active/N-Way to achieve high availability, and some"},{"line_number":74,"context_line":"  components inside one application are designed to work as distributed"},{"line_number":75,"context_line":"  cluster, this design typically leads to state replication or heart"},{"line_number":76,"context_line":"  beat among application components (directly or via replicated database"},{"line_number":77,"context_line":"  services, or via private designed message format). When this kind of"},{"line_number":78,"context_line":"  applications are distributedly deployed into multiple OpenStack instances,"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_a673adb0","line":75,"range":{"start_line":75,"start_character":2,"end_line":75,"end_character":9},"updated":"2016-05-29 01:49:51.000000000","message":"cluster?\n\nHow do we define this wold?","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":72,"context_line":"  achieve higher reliability. Application may (already) be designed as"},{"line_number":73,"context_line":"  Active-Standby/Active-Active/N-Way to achieve high availability, and some"},{"line_number":74,"context_line":"  components inside one application are designed to work as distributed"},{"line_number":75,"context_line":"  cluster, this design typically leads to state replication or heart"},{"line_number":76,"context_line":"  beat among application components (directly or via replicated database"},{"line_number":77,"context_line":"  services, or via private designed message format). When this kind of"},{"line_number":78,"context_line":"  applications are distributedly deployed into multiple OpenStack instances,"},{"line_number":79,"context_line":"  cross OpenStack L2 networking is needed to support heart beat"},{"line_number":80,"context_line":"  or state replication."},{"line_number":81,"context_line":""},{"line_number":82,"context_line":"* When a tenant\u0027s VMs are provisioned in different OpenStack instances, there"},{"line_number":83,"context_line":"  is E-W traffic for these VMs, the E-W traffic should be only visible to the"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_e665b5e1","line":80,"range":{"start_line":75,"start_character":11,"end_line":80,"end_character":22},"updated":"2016-05-29 01:49:51.000000000","message":"Let\u0027s reconsider this sentence.\nWe can write this up more simply.","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":80,"context_line":"  or state replication."},{"line_number":81,"context_line":""},{"line_number":82,"context_line":"* When a tenant\u0027s VMs are provisioned in different OpenStack instances, there"},{"line_number":83,"context_line":"  is E-W traffic for these VMs, the E-W traffic should be only visible to the"},{"line_number":84,"context_line":"  tenant, and isolation is needed. If the traffic goes through N-S via tenant"},{"line_number":85,"context_line":"  level VPN, then overhead is too much, and the orchestration for multiple"},{"line_number":86,"context_line":"  site to site VPN establishment is also complicated. Therefore cross"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_26605dce","line":83,"range":{"start_line":83,"start_character":5,"end_line":83,"end_character":8},"updated":"2016-05-29 01:49:51.000000000","message":"How do we define \u0027E-W\u0027?","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"4efe21caa774909cd7b53e151044be8a932a01ed","unresolved":false,"context_lines":[{"line_number":80,"context_line":"  or state replication."},{"line_number":81,"context_line":""},{"line_number":82,"context_line":"* When a tenant\u0027s VMs are provisioned in different OpenStack instances, there"},{"line_number":83,"context_line":"  is E-W traffic for these VMs, the E-W traffic should be only visible to the"},{"line_number":84,"context_line":"  tenant, and isolation is needed. If the traffic goes through N-S via tenant"},{"line_number":85,"context_line":"  level VPN, then overhead is too much, and the orchestration for multiple"},{"line_number":86,"context_line":"  site to site VPN establishment is also complicated. Therefore cross"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_3a07ca1d","line":83,"range":{"start_line":83,"start_character":5,"end_line":83,"end_character":8},"in_reply_to":"9abb7d3a_26605dce","updated":"2016-05-30 05:15:52.000000000","message":"East-west","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":81,"context_line":""},{"line_number":82,"context_line":"* When a tenant\u0027s VMs are provisioned in different OpenStack instances, there"},{"line_number":83,"context_line":"  is E-W traffic for these VMs, the E-W traffic should be only visible to the"},{"line_number":84,"context_line":"  tenant, and isolation is needed. If the traffic goes through N-S via tenant"},{"line_number":85,"context_line":"  level VPN, then overhead is too much, and the orchestration for multiple"},{"line_number":86,"context_line":"  site to site VPN establishment is also complicated. Therefore cross"},{"line_number":87,"context_line":"  OpenStack L2 network to bridge the tenant\u0027s routers in different OpenStack"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_c6a51105","line":84,"range":{"start_line":84,"start_character":63,"end_line":84,"end_character":66},"updated":"2016-05-29 01:49:51.000000000","message":"How do we define \u0027N-S\u0027?","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"4efe21caa774909cd7b53e151044be8a932a01ed","unresolved":false,"context_lines":[{"line_number":81,"context_line":""},{"line_number":82,"context_line":"* When a tenant\u0027s VMs are provisioned in different OpenStack instances, there"},{"line_number":83,"context_line":"  is E-W traffic for these VMs, the E-W traffic should be only visible to the"},{"line_number":84,"context_line":"  tenant, and isolation is needed. If the traffic goes through N-S via tenant"},{"line_number":85,"context_line":"  level VPN, then overhead is too much, and the orchestration for multiple"},{"line_number":86,"context_line":"  site to site VPN establishment is also complicated. Therefore cross"},{"line_number":87,"context_line":"  OpenStack L2 network to bridge the tenant\u0027s routers in different OpenStack"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_b5f3cd09","line":84,"range":{"start_line":84,"start_character":63,"end_line":84,"end_character":66},"in_reply_to":"9abb7d3a_c6a51105","updated":"2016-05-30 05:15:52.000000000","message":"North-south","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":82,"context_line":"* When a tenant\u0027s VMs are provisioned in different OpenStack instances, there"},{"line_number":83,"context_line":"  is E-W traffic for these VMs, the E-W traffic should be only visible to the"},{"line_number":84,"context_line":"  tenant, and isolation is needed. If the traffic goes through N-S via tenant"},{"line_number":85,"context_line":"  level VPN, then overhead is too much, and the orchestration for multiple"},{"line_number":86,"context_line":"  site to site VPN establishment is also complicated. Therefore cross"},{"line_number":87,"context_line":"  OpenStack L2 network to bridge the tenant\u0027s routers in different OpenStack"},{"line_number":88,"context_line":"  instances can provide more light weight isolation."}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_a6aa8dd2","line":85,"range":{"start_line":85,"start_character":13,"end_line":85,"end_character":17},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: delete \u0027then\u0027","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":83,"context_line":"  is E-W traffic for these VMs, the E-W traffic should be only visible to the"},{"line_number":84,"context_line":"  tenant, and isolation is needed. If the traffic goes through N-S via tenant"},{"line_number":85,"context_line":"  level VPN, then overhead is too much, and the orchestration for multiple"},{"line_number":86,"context_line":"  site to site VPN establishment is also complicated. Therefore cross"},{"line_number":87,"context_line":"  OpenStack L2 network to bridge the tenant\u0027s routers in different OpenStack"},{"line_number":88,"context_line":"  instances can provide more light weight isolation."},{"line_number":89,"context_line":""}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_06b0b942","line":86,"range":{"start_line":86,"start_character":19,"end_line":86,"end_character":32},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: connection","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":84,"context_line":"  tenant, and isolation is needed. If the traffic goes through N-S via tenant"},{"line_number":85,"context_line":"  level VPN, then overhead is too much, and the orchestration for multiple"},{"line_number":86,"context_line":"  site to site VPN establishment is also complicated. Therefore cross"},{"line_number":87,"context_line":"  OpenStack L2 network to bridge the tenant\u0027s routers in different OpenStack"},{"line_number":88,"context_line":"  instances can provide more light weight isolation."},{"line_number":89,"context_line":""},{"line_number":90,"context_line":"* In hybrid cloud, there is cross L2 networking requirement between the"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_26b7bd3a","line":87,"range":{"start_line":87,"start_character":15,"end_line":87,"end_character":22},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: networking","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":89,"context_line":""},{"line_number":90,"context_line":"* In hybrid cloud, there is cross L2 networking requirement between the"},{"line_number":91,"context_line":"  private OpenStack and the public OpenStack. Cross pod L2"},{"line_number":92,"context_line":"  networking will help the VMs migration for this case, and no need to"},{"line_number":93,"context_line":"  change the IP/MAC/Security Group configuration when migrating VM."},{"line_number":94,"context_line":""},{"line_number":95,"context_line":"The spec[5] is to deal with how one AZ can support more than one pod, and how"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_c67cf174","line":92,"range":{"start_line":92,"start_character":56,"end_line":92,"end_character":70},"updated":"2016-05-29 01:49:51.000000000","message":"And it\u0027s not necessary","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":89,"context_line":""},{"line_number":90,"context_line":"* In hybrid cloud, there is cross L2 networking requirement between the"},{"line_number":91,"context_line":"  private OpenStack and the public OpenStack. Cross pod L2"},{"line_number":92,"context_line":"  networking will help the VMs migration for this case, and no need to"},{"line_number":93,"context_line":"  change the IP/MAC/Security Group configuration when migrating VM."},{"line_number":94,"context_line":""},{"line_number":95,"context_line":"The spec[5] is to deal with how one AZ can support more than one pod, and how"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_66870562","line":92,"range":{"start_line":92,"start_character":54,"end_line":92,"end_character":55},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: delete \u0027,\u0027","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":89,"context_line":""},{"line_number":90,"context_line":"* In hybrid cloud, there is cross L2 networking requirement between the"},{"line_number":91,"context_line":"  private OpenStack and the public OpenStack. Cross pod L2"},{"line_number":92,"context_line":"  networking will help the VMs migration for this case, and no need to"},{"line_number":93,"context_line":"  change the IP/MAC/Security Group configuration when migrating VM."},{"line_number":94,"context_line":""},{"line_number":95,"context_line":"The spec[5] is to deal with how one AZ can support more than one pod, and how"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_8682e950","line":92,"range":{"start_line":92,"start_character":41,"end_line":92,"end_character":44},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: in","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":90,"context_line":"* In hybrid cloud, there is cross L2 networking requirement between the"},{"line_number":91,"context_line":"  private OpenStack and the public OpenStack. Cross pod L2"},{"line_number":92,"context_line":"  networking will help the VMs migration for this case, and no need to"},{"line_number":93,"context_line":"  change the IP/MAC/Security Group configuration when migrating VM."},{"line_number":94,"context_line":""},{"line_number":95,"context_line":"The spec[5] is to deal with how one AZ can support more than one pod, and how"},{"line_number":96,"context_line":"to schedule a proper pod during VM or Volume creation."}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_e693f5a1","line":93,"range":{"start_line":93,"start_character":49,"end_line":93,"end_character":66},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: during VM migration","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":92,"context_line":"  networking will help the VMs migration for this case, and no need to"},{"line_number":93,"context_line":"  change the IP/MAC/Security Group configuration when migrating VM."},{"line_number":94,"context_line":""},{"line_number":95,"context_line":"The spec[5] is to deal with how one AZ can support more than one pod, and how"},{"line_number":96,"context_line":"to schedule a proper pod during VM or Volume creation."},{"line_number":97,"context_line":""},{"line_number":98,"context_line":"And this spec is to deal with the cross OpenStack L2 networking automation in"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_46912199","line":95,"range":{"start_line":95,"start_character":18,"end_line":95,"end_character":27},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: explain","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":99,"context_line":"the Tricircle."},{"line_number":100,"context_line":""},{"line_number":101,"context_line":"The simplest way to stretch one L2 network across multiple OpenStack instances"},{"line_number":102,"context_line":"is to use a same VLAN network, but there is a lot of limitation: the number"},{"line_number":103,"context_line":"of VLAN segment is limited, the VLAN network itself is not good to spread"},{"line_number":104,"context_line":"across multiple sites, although you can use some gateways to do so."},{"line_number":105,"context_line":""}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_e6dad577","line":102,"range":{"start_line":102,"start_character":65,"end_line":102,"end_character":68},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: A","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":99,"context_line":"the Tricircle."},{"line_number":100,"context_line":""},{"line_number":101,"context_line":"The simplest way to stretch one L2 network across multiple OpenStack instances"},{"line_number":102,"context_line":"is to use a same VLAN network, but there is a lot of limitation: the number"},{"line_number":103,"context_line":"of VLAN segment is limited, the VLAN network itself is not good to spread"},{"line_number":104,"context_line":"across multiple sites, although you can use some gateways to do so."},{"line_number":105,"context_line":""}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_86e9491d","line":102,"range":{"start_line":102,"start_character":31,"end_line":102,"end_character":34},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: But","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":99,"context_line":"the Tricircle."},{"line_number":100,"context_line":""},{"line_number":101,"context_line":"The simplest way to stretch one L2 network across multiple OpenStack instances"},{"line_number":102,"context_line":"is to use a same VLAN network, but there is a lot of limitation: the number"},{"line_number":103,"context_line":"of VLAN segment is limited, the VLAN network itself is not good to spread"},{"line_number":104,"context_line":"across multiple sites, although you can use some gateways to do so."},{"line_number":105,"context_line":""}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_268e9d78","line":102,"range":{"start_line":102,"start_character":29,"end_line":102,"end_character":30},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: delete \u0027,\u0027","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":99,"context_line":"the Tricircle."},{"line_number":100,"context_line":""},{"line_number":101,"context_line":"The simplest way to stretch one L2 network across multiple OpenStack instances"},{"line_number":102,"context_line":"is to use a same VLAN network, but there is a lot of limitation: the number"},{"line_number":103,"context_line":"of VLAN segment is limited, the VLAN network itself is not good to spread"},{"line_number":104,"context_line":"across multiple sites, although you can use some gateways to do so."},{"line_number":105,"context_line":""}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_66eee523","line":102,"range":{"start_line":102,"start_character":53,"end_line":102,"end_character":63},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: limitations","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":99,"context_line":"the Tricircle."},{"line_number":100,"context_line":""},{"line_number":101,"context_line":"The simplest way to stretch one L2 network across multiple OpenStack instances"},{"line_number":102,"context_line":"is to use a same VLAN network, but there is a lot of limitation: the number"},{"line_number":103,"context_line":"of VLAN segment is limited, the VLAN network itself is not good to spread"},{"line_number":104,"context_line":"across multiple sites, although you can use some gateways to do so."},{"line_number":105,"context_line":""}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_a6f8cde6","line":102,"range":{"start_line":102,"start_character":63,"end_line":102,"end_character":64},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: replace \u0027:\u0027 with \u0027.\u0027","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":101,"context_line":"The simplest way to stretch one L2 network across multiple OpenStack instances"},{"line_number":102,"context_line":"is to use a same VLAN network, but there is a lot of limitation: the number"},{"line_number":103,"context_line":"of VLAN segment is limited, the VLAN network itself is not good to spread"},{"line_number":104,"context_line":"across multiple sites, although you can use some gateways to do so."},{"line_number":105,"context_line":""},{"line_number":106,"context_line":"So flexible tenant level L2 networking across multiple OpenStack instances in"},{"line_number":107,"context_line":"one site or in multiple sites is needed."}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_86d02955","line":104,"range":{"start_line":104,"start_character":0,"end_line":104,"end_character":6},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: out","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":101,"context_line":"The simplest way to stretch one L2 network across multiple OpenStack instances"},{"line_number":102,"context_line":"is to use a same VLAN network, but there is a lot of limitation: the number"},{"line_number":103,"context_line":"of VLAN segment is limited, the VLAN network itself is not good to spread"},{"line_number":104,"context_line":"across multiple sites, although you can use some gateways to do so."},{"line_number":105,"context_line":""},{"line_number":106,"context_line":"So flexible tenant level L2 networking across multiple OpenStack instances in"},{"line_number":107,"context_line":"one site or in multiple sites is needed."}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_c6ca31a1","line":104,"range":{"start_line":104,"start_character":16,"end_line":104,"end_character":21},"updated":"2016-05-29 01:49:51.000000000","message":"sites?\n\nHow do we define this word?","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":101,"context_line":"The simplest way to stretch one L2 network across multiple OpenStack instances"},{"line_number":102,"context_line":"is to use a same VLAN network, but there is a lot of limitation: the number"},{"line_number":103,"context_line":"of VLAN segment is limited, the VLAN network itself is not good to spread"},{"line_number":104,"context_line":"across multiple sites, although you can use some gateways to do so."},{"line_number":105,"context_line":""},{"line_number":106,"context_line":"So flexible tenant level L2 networking across multiple OpenStack instances in"},{"line_number":107,"context_line":"one site or in multiple sites is needed."}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_06c5598d","line":104,"range":{"start_line":104,"start_character":64,"end_line":104,"end_character":66},"updated":"2016-05-29 01:49:51.000000000","message":"so?\nto do \u0027what\u0027?","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":106,"context_line":"So flexible tenant level L2 networking across multiple OpenStack instances in"},{"line_number":107,"context_line":"one site or in multiple sites is needed."},{"line_number":108,"context_line":""},{"line_number":109,"context_line":"Proposed change"},{"line_number":110,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":111,"context_line":""},{"line_number":112,"context_line":"Cross pod L2 networking can be divided into three categories,"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_e6c13582","line":109,"range":{"start_line":109,"start_character":9,"end_line":109,"end_character":15},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: Change","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":110,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":111,"context_line":""},{"line_number":112,"context_line":"Cross pod L2 networking can be divided into three categories,"},{"line_number":113,"context_line":"``shared VLAN``, ``shared VxLAN`` and ``mixed VLAN/VxLAN``."},{"line_number":114,"context_line":""},{"line_number":115,"context_line":"* Shared VLAN"},{"line_number":116,"context_line":"  Network in each bottom OpenStack is VLAN type and has the same VLAN ID."}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_c641910d","line":113,"range":{"start_line":113,"start_character":40,"end_line":113,"end_character":45},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: Mixed","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":110,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":111,"context_line":""},{"line_number":112,"context_line":"Cross pod L2 networking can be divided into three categories,"},{"line_number":113,"context_line":"``shared VLAN``, ``shared VxLAN`` and ``mixed VLAN/VxLAN``."},{"line_number":114,"context_line":""},{"line_number":115,"context_line":"* Shared VLAN"},{"line_number":116,"context_line":"  Network in each bottom OpenStack is VLAN type and has the same VLAN ID."}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_663c2594","line":113,"range":{"start_line":113,"start_character":19,"end_line":113,"end_character":25},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: Shared","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":110,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":111,"context_line":""},{"line_number":112,"context_line":"Cross pod L2 networking can be divided into three categories,"},{"line_number":113,"context_line":"``shared VLAN``, ``shared VxLAN`` and ``mixed VLAN/VxLAN``."},{"line_number":114,"context_line":""},{"line_number":115,"context_line":"* Shared VLAN"},{"line_number":116,"context_line":"  Network in each bottom OpenStack is VLAN type and has the same VLAN ID."}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_863789af","line":113,"range":{"start_line":113,"start_character":2,"end_line":113,"end_character":8},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: Shared","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":114,"context_line":""},{"line_number":115,"context_line":"* Shared VLAN"},{"line_number":116,"context_line":"  Network in each bottom OpenStack is VLAN type and has the same VLAN ID."},{"line_number":117,"context_line":"  If we want shared VLAN L2 network to work in multi-site scenario, i.e."},{"line_number":118,"context_line":"  multiple OpenStack instances in multiple sites, then physical gateway needs"},{"line_number":119,"context_line":"  to be manually configured to make one VLAN network be extended to other"},{"line_number":120,"context_line":"  sites."}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_a6460d21","line":117,"range":{"start_line":117,"start_character":28,"end_line":117,"end_character":35},"updated":"2016-05-29 01:49:51.000000000","message":"networking","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":115,"context_line":"* Shared VLAN"},{"line_number":116,"context_line":"  Network in each bottom OpenStack is VLAN type and has the same VLAN ID."},{"line_number":117,"context_line":"  If we want shared VLAN L2 network to work in multi-site scenario, i.e."},{"line_number":118,"context_line":"  multiple OpenStack instances in multiple sites, then physical gateway needs"},{"line_number":119,"context_line":"  to be manually configured to make one VLAN network be extended to other"},{"line_number":120,"context_line":"  sites."},{"line_number":121,"context_line":""}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_26533de3","line":118,"range":{"start_line":118,"start_character":50,"end_line":118,"end_character":54},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: delete \u0027then\u0027","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":114,"context_line":""},{"line_number":115,"context_line":"* Shared VLAN"},{"line_number":116,"context_line":"  Network in each bottom OpenStack is VLAN type and has the same VLAN ID."},{"line_number":117,"context_line":"  If we want shared VLAN L2 network to work in multi-site scenario, i.e."},{"line_number":118,"context_line":"  multiple OpenStack instances in multiple sites, then physical gateway needs"},{"line_number":119,"context_line":"  to be manually configured to make one VLAN network be extended to other"},{"line_number":120,"context_line":"  sites."},{"line_number":121,"context_line":""}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_e6481530","line":118,"range":{"start_line":117,"start_character":58,"end_line":118,"end_character":30},"updated":"2016-05-29 01:49:51.000000000","message":"scenario.\ni.e.,\nMultiple OpenStack instances ...","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":119,"context_line":"  to be manually configured to make one VLAN network be extended to other"},{"line_number":120,"context_line":"  sites."},{"line_number":121,"context_line":""},{"line_number":122,"context_line":"  How to manually setup physical gateway is out of the scope of this spec."},{"line_number":123,"context_line":""},{"line_number":124,"context_line":"* Shared VxLAN"},{"line_number":125,"context_line":"  Network in each bottom OpenStack is VxLAN type and has the same VxLAN ID."}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_c65871fd","line":122,"range":{"start_line":122,"start_character":2,"end_line":122,"end_character":74},"updated":"2016-05-29 01:49:51.000000000","message":"* Manual setup physical gateway is out of scope of this spec.\n\nAdd 2 space and astarisc \u0027*\u0027 + description.","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":122,"context_line":"  How to manually setup physical gateway is out of the scope of this spec."},{"line_number":123,"context_line":""},{"line_number":124,"context_line":"* Shared VxLAN"},{"line_number":125,"context_line":"  Network in each bottom OpenStack is VxLAN type and has the same VxLAN ID."},{"line_number":126,"context_line":"  Leverage L2GW[1][2] to implement this type of L2 networking."},{"line_number":127,"context_line":""},{"line_number":128,"context_line":"* Mixed VLAN/VxLAN"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_06739981","line":125,"range":{"start_line":125,"start_character":25,"end_line":125,"end_character":34},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: OpenStack instance","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":130,"context_line":"  different segment IDs."},{"line_number":131,"context_line":"  Leverage L2GW[1][2] to implement this type of L2 networking"},{"line_number":132,"context_line":""},{"line_number":133,"context_line":"There is another network type called “Local Network”, for “Local Network”,"},{"line_number":134,"context_line":"the network will be only presented in one bottom pod, never across different"},{"line_number":135,"context_line":"pods. If VMs in another pod tries to attach to the “Local Network”, it should"},{"line_number":136,"context_line":"be failed. This use case is quite useful for the scenario where cross pod L2"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_266a1d81","line":133,"range":{"start_line":133,"start_character":54,"end_line":133,"end_character":57},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: For","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":130,"context_line":"  different segment IDs."},{"line_number":131,"context_line":"  Leverage L2GW[1][2] to implement this type of L2 networking"},{"line_number":132,"context_line":""},{"line_number":133,"context_line":"There is another network type called “Local Network”, for “Local Network”,"},{"line_number":134,"context_line":"the network will be only presented in one bottom pod, never across different"},{"line_number":135,"context_line":"pods. If VMs in another pod tries to attach to the “Local Network”, it should"},{"line_number":136,"context_line":"be failed. This use case is quite useful for the scenario where cross pod L2"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_466da197","line":133,"range":{"start_line":133,"start_character":52,"end_line":133,"end_character":53},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: replace \u0027,\u0027 with \u0027.\u0027","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":131,"context_line":"  Leverage L2GW[1][2] to implement this type of L2 networking"},{"line_number":132,"context_line":""},{"line_number":133,"context_line":"There is another network type called “Local Network”, for “Local Network”,"},{"line_number":134,"context_line":"the network will be only presented in one bottom pod, never across different"},{"line_number":135,"context_line":"pods. If VMs in another pod tries to attach to the “Local Network”, it should"},{"line_number":136,"context_line":"be failed. This use case is quite useful for the scenario where cross pod L2"},{"line_number":137,"context_line":"networking is not required, and one AZ will not include more than one pod."}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_660a65d4","line":134,"range":{"start_line":134,"start_character":49,"end_line":134,"end_character":52},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: OpenStack instance","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":131,"context_line":"  Leverage L2GW[1][2] to implement this type of L2 networking"},{"line_number":132,"context_line":""},{"line_number":133,"context_line":"There is another network type called “Local Network”, for “Local Network”,"},{"line_number":134,"context_line":"the network will be only presented in one bottom pod, never across different"},{"line_number":135,"context_line":"pods. If VMs in another pod tries to attach to the “Local Network”, it should"},{"line_number":136,"context_line":"be failed. This use case is quite useful for the scenario where cross pod L2"},{"line_number":137,"context_line":"networking is not required, and one AZ will not include more than one pod."}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_a6144df5","line":134,"range":{"start_line":134,"start_character":52,"end_line":134,"end_character":53},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: replace \u0027,\u0027 with \u0027.\u0027","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":131,"context_line":"  Leverage L2GW[1][2] to implement this type of L2 networking"},{"line_number":132,"context_line":""},{"line_number":133,"context_line":"There is another network type called “Local Network”, for “Local Network”,"},{"line_number":134,"context_line":"the network will be only presented in one bottom pod, never across different"},{"line_number":135,"context_line":"pods. If VMs in another pod tries to attach to the “Local Network”, it should"},{"line_number":136,"context_line":"be failed. This use case is quite useful for the scenario where cross pod L2"},{"line_number":137,"context_line":"networking is not required, and one AZ will not include more than one pod."},{"line_number":138,"context_line":""}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_e6f655d6","line":135,"range":{"start_line":134,"start_character":54,"end_line":135,"end_character":5},"updated":"2016-05-29 01:49:51.000000000","message":"And the network won\u0027t be presented in different bottom OpenStack instances.","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":132,"context_line":""},{"line_number":133,"context_line":"There is another network type called “Local Network”, for “Local Network”,"},{"line_number":134,"context_line":"the network will be only presented in one bottom pod, never across different"},{"line_number":135,"context_line":"pods. If VMs in another pod tries to attach to the “Local Network”, it should"},{"line_number":136,"context_line":"be failed. This use case is quite useful for the scenario where cross pod L2"},{"line_number":137,"context_line":"networking is not required, and one AZ will not include more than one pod."},{"line_number":138,"context_line":""}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_26017daf","line":135,"range":{"start_line":135,"start_character":9,"end_line":135,"end_character":12},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: a VM","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":133,"context_line":"There is another network type called “Local Network”, for “Local Network”,"},{"line_number":134,"context_line":"the network will be only presented in one bottom pod, never across different"},{"line_number":135,"context_line":"pods. If VMs in another pod tries to attach to the “Local Network”, it should"},{"line_number":136,"context_line":"be failed. This use case is quite useful for the scenario where cross pod L2"},{"line_number":137,"context_line":"networking is not required, and one AZ will not include more than one pod."},{"line_number":138,"context_line":""},{"line_number":139,"context_line":"Cross pod L2 networking will be established dynamically as tenant’s VM is"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_862ca94b","line":136,"range":{"start_line":136,"start_character":58,"end_line":136,"end_character":63},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: in which","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":134,"context_line":"the network will be only presented in one bottom pod, never across different"},{"line_number":135,"context_line":"pods. If VMs in another pod tries to attach to the “Local Network”, it should"},{"line_number":136,"context_line":"be failed. This use case is quite useful for the scenario where cross pod L2"},{"line_number":137,"context_line":"networking is not required, and one AZ will not include more than one pod."},{"line_number":138,"context_line":""},{"line_number":139,"context_line":"Cross pod L2 networking will be established dynamically as tenant’s VM is"},{"line_number":140,"context_line":"provisioned."}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_6631c5a2","line":137,"range":{"start_line":137,"start_character":70,"end_line":137,"end_character":73},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: bottom OpenStack instance","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":136,"context_line":"be failed. This use case is quite useful for the scenario where cross pod L2"},{"line_number":137,"context_line":"networking is not required, and one AZ will not include more than one pod."},{"line_number":138,"context_line":""},{"line_number":139,"context_line":"Cross pod L2 networking will be established dynamically as tenant’s VM is"},{"line_number":140,"context_line":"provisioned."},{"line_number":141,"context_line":""},{"line_number":142,"context_line":"There is assumption here that only one category of L2 networking will work"},{"line_number":143,"context_line":"in one cloud deployment."}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_c626b167","line":140,"range":{"start_line":139,"start_character":0,"end_line":140,"end_character":12},"updated":"2016-05-29 01:49:51.000000000","message":"Cross pod L2 networking will be able to be established dynamically during tenant\u0027s VM is being provisioned.","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":139,"context_line":"Cross pod L2 networking will be established dynamically as tenant’s VM is"},{"line_number":140,"context_line":"provisioned."},{"line_number":141,"context_line":""},{"line_number":142,"context_line":"There is assumption here that only one category of L2 networking will work"},{"line_number":143,"context_line":"in one cloud deployment."},{"line_number":144,"context_line":""},{"line_number":145,"context_line":"How to create a cross pod L2 network?"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_a62bad2f","line":142,"range":{"start_line":142,"start_character":39,"end_line":142,"end_character":47},"updated":"2016-05-29 01:49:51.000000000","message":"category?","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":142,"context_line":"There is assumption here that only one category of L2 networking will work"},{"line_number":143,"context_line":"in one cloud deployment."},{"line_number":144,"context_line":""},{"line_number":145,"context_line":"How to create a cross pod L2 network?"},{"line_number":146,"context_line":"The way to create a cross pod L2 network is through the az_hint attribute of"},{"line_number":147,"context_line":"the network. If az_hint includes one AZ or more AZs, then the network will be"},{"line_number":148,"context_line":"presented only in this AZ or these AZs, if no AZ in az_hint, then means the"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_86d30938","line":145,"range":{"start_line":145,"start_character":0,"end_line":145,"end_character":37},"updated":"2016-05-29 01:49:51.000000000","message":"------------------------------------------------\nA Cross Pod L2 Networking Creation\n------------------------------------------------","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":143,"context_line":"in one cloud deployment."},{"line_number":144,"context_line":""},{"line_number":145,"context_line":"How to create a cross pod L2 network?"},{"line_number":146,"context_line":"The way to create a cross pod L2 network is through the az_hint attribute of"},{"line_number":147,"context_line":"the network. If az_hint includes one AZ or more AZs, then the network will be"},{"line_number":148,"context_line":"presented only in this AZ or these AZs, if no AZ in az_hint, then means the"},{"line_number":149,"context_line":"network can be extended to any bottom OpenStack."},{"line_number":150,"context_line":""}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_a6e28d01","line":147,"range":{"start_line":146,"start_character":0,"end_line":147,"end_character":12},"updated":"2016-05-29 01:49:51.000000000","message":"A cross pod L2 networking creation will be able to be done with the az_hint attribute of the network.","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":144,"context_line":""},{"line_number":145,"context_line":"How to create a cross pod L2 network?"},{"line_number":146,"context_line":"The way to create a cross pod L2 network is through the az_hint attribute of"},{"line_number":147,"context_line":"the network. If az_hint includes one AZ or more AZs, then the network will be"},{"line_number":148,"context_line":"presented only in this AZ or these AZs, if no AZ in az_hint, then means the"},{"line_number":149,"context_line":"network can be extended to any bottom OpenStack."},{"line_number":150,"context_line":""}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_e6e4950e","line":147,"range":{"start_line":147,"start_character":53,"end_line":147,"end_character":57},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: delete \u0027then\u0027","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":145,"context_line":"How to create a cross pod L2 network?"},{"line_number":146,"context_line":"The way to create a cross pod L2 network is through the az_hint attribute of"},{"line_number":147,"context_line":"the network. If az_hint includes one AZ or more AZs, then the network will be"},{"line_number":148,"context_line":"presented only in this AZ or these AZs, if no AZ in az_hint, then means the"},{"line_number":149,"context_line":"network can be extended to any bottom OpenStack."},{"line_number":150,"context_line":""},{"line_number":151,"context_line":"There is a special use case for external network creation. For external"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_26efbde9","line":148,"range":{"start_line":148,"start_character":61,"end_line":148,"end_character":65},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: delete \u0027then\u0027","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":145,"context_line":"How to create a cross pod L2 network?"},{"line_number":146,"context_line":"The way to create a cross pod L2 network is through the az_hint attribute of"},{"line_number":147,"context_line":"the network. If az_hint includes one AZ or more AZs, then the network will be"},{"line_number":148,"context_line":"presented only in this AZ or these AZs, if no AZ in az_hint, then means the"},{"line_number":149,"context_line":"network can be extended to any bottom OpenStack."},{"line_number":150,"context_line":""},{"line_number":151,"context_line":"There is a special use case for external network creation. For external"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_86bae9df","line":148,"range":{"start_line":148,"start_character":66,"end_line":148,"end_character":71},"updated":"2016-05-29 01:49:51.000000000","message":"it means that","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":145,"context_line":"How to create a cross pod L2 network?"},{"line_number":146,"context_line":"The way to create a cross pod L2 network is through the az_hint attribute of"},{"line_number":147,"context_line":"the network. If az_hint includes one AZ or more AZs, then the network will be"},{"line_number":148,"context_line":"presented only in this AZ or these AZs, if no AZ in az_hint, then means the"},{"line_number":149,"context_line":"network can be extended to any bottom OpenStack."},{"line_number":150,"context_line":""},{"line_number":151,"context_line":"There is a special use case for external network creation. For external"},{"line_number":152,"context_line":"network creation, you need to specify the pod_id but not AZ in the az_hint,"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_a6b9edeb","line":149,"range":{"start_line":148,"start_character":61,"end_line":149,"end_character":48},"updated":"2016-05-29 01:49:51.000000000","message":"What are you going to tell readers with this sentence?","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":149,"context_line":"network can be extended to any bottom OpenStack."},{"line_number":150,"context_line":""},{"line_number":151,"context_line":"There is a special use case for external network creation. For external"},{"line_number":152,"context_line":"network creation, you need to specify the pod_id but not AZ in the az_hint,"},{"line_number":153,"context_line":"so that the external network will be only created in one specified pod per AZ."},{"line_number":154,"context_line":"To support external network in multiple pods in one AZ should be in the scope"},{"line_number":155,"context_line":"of another spec."}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_06cf1980","line":152,"range":{"start_line":152,"start_character":74,"end_line":152,"end_character":75},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: delete \u0027,\u0027","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":151,"context_line":"There is a special use case for external network creation. For external"},{"line_number":152,"context_line":"network creation, you need to specify the pod_id but not AZ in the az_hint,"},{"line_number":153,"context_line":"so that the external network will be only created in one specified pod per AZ."},{"line_number":154,"context_line":"To support external network in multiple pods in one AZ should be in the scope"},{"line_number":155,"context_line":"of another spec."},{"line_number":156,"context_line":""},{"line_number":157,"context_line":"Pluggable L2 networking framework is proposed to deal with three kinds of"},{"line_number":158,"context_line":"L2 cross pod networking, and it should be compatible with the"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_269dfd65","line":155,"range":{"start_line":154,"start_character":0,"end_line":155,"end_character":16},"updated":"2016-05-29 01:49:51.000000000","message":"* Support of External network in multiple OpenStack instances in one AZ is out of scope of this spec.\n\nAdd 2 space and astarisc \u0027*\u0027 + description.","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":154,"context_line":"To support external network in multiple pods in one AZ should be in the scope"},{"line_number":155,"context_line":"of another spec."},{"line_number":156,"context_line":""},{"line_number":157,"context_line":"Pluggable L2 networking framework is proposed to deal with three kinds of"},{"line_number":158,"context_line":"L2 cross pod networking, and it should be compatible with the"},{"line_number":159,"context_line":"``Local Network``:"},{"line_number":160,"context_line":""}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_668d4531","line":157,"range":{"start_line":157,"start_character":65,"end_line":157,"end_character":70},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: types","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":156,"context_line":""},{"line_number":157,"context_line":"Pluggable L2 networking framework is proposed to deal with three kinds of"},{"line_number":158,"context_line":"L2 cross pod networking, and it should be compatible with the"},{"line_number":159,"context_line":"``Local Network``:"},{"line_number":160,"context_line":""},{"line_number":161,"context_line":"1.Type Driver under Tricircle Plugin in Neutron API server"},{"line_number":162,"context_line":""}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_067d591c","line":159,"range":{"start_line":159,"start_character":17,"end_line":159,"end_character":18},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: replace \u0027:\u0027 with \u0027.\u0027","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":161,"context_line":"1.Type Driver under Tricircle Plugin in Neutron API server"},{"line_number":162,"context_line":""},{"line_number":163,"context_line":"* Type driver to distinguish different type of cross pod L2 networking. So"},{"line_number":164,"context_line":"  Tricircle plugin need to load type driver according to the configuration,"},{"line_number":165,"context_line":"  can reuse the type driver of ML2 with update."},{"line_number":166,"context_line":""},{"line_number":167,"context_line":"* Type driver to allocate VLAN segment id for shared VLAN L2 networking."}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_2674dd33","line":164,"range":{"start_line":164,"start_character":74,"end_line":164,"end_character":75},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: replace \u0027,\u0027 with \u0027.\u0027","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":162,"context_line":""},{"line_number":163,"context_line":"* Type driver to distinguish different type of cross pod L2 networking. So"},{"line_number":164,"context_line":"  Tricircle plugin need to load type driver according to the configuration,"},{"line_number":165,"context_line":"  can reuse the type driver of ML2 with update."},{"line_number":166,"context_line":""},{"line_number":167,"context_line":"* Type driver to allocate VLAN segment id for shared VLAN L2 networking."},{"line_number":168,"context_line":""}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_868f8922","line":165,"range":{"start_line":165,"start_character":2,"end_line":165,"end_character":47},"updated":"2016-05-29 01:49:51.000000000","message":"Add subject","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":169,"context_line":"* Type driver to allocate VxLAN segment id for shared VxLAN L2 networking."},{"line_number":170,"context_line":""},{"line_number":171,"context_line":"* Type driver for mixed VLAN/VxLAN to allocate VxLAN segment id for the"},{"line_number":172,"context_line":"  network connecting L2GWs[1][2]"},{"line_number":173,"context_line":""},{"line_number":174,"context_line":"* Type driver for Local Network only updating ``network_type`` for the"},{"line_number":175,"context_line":"  network to DB."}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_46ae4186","line":172,"updated":"2016-05-29 01:49:51.000000000","message":"Minor: add \u0027.\u0027\n\nL2GWs. [1][2]","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":172,"context_line":"  network connecting L2GWs[1][2]"},{"line_number":173,"context_line":""},{"line_number":174,"context_line":"* Type driver for Local Network only updating ``network_type`` for the"},{"line_number":175,"context_line":"  network to DB."},{"line_number":176,"context_line":""},{"line_number":177,"context_line":"When a network creation request is received in Neutron API Server in Tricircle,"},{"line_number":178,"context_line":"the type driver will be called according to the configured network type."}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_c6b071e0","line":175,"range":{"start_line":175,"start_character":10,"end_line":175,"end_character":12},"updated":"2016-05-29 01:49:51.000000000","message":"We define that DB is one components of the Tricircle above.\nIt would be better to use \u0027by\u0027 instead \u0027to\u0027.","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":174,"context_line":"* Type driver for Local Network only updating ``network_type`` for the"},{"line_number":175,"context_line":"  network to DB."},{"line_number":176,"context_line":""},{"line_number":177,"context_line":"When a network creation request is received in Neutron API Server in Tricircle,"},{"line_number":178,"context_line":"the type driver will be called according to the configured network type."},{"line_number":179,"context_line":""},{"line_number":180,"context_line":"2. Nova API-GW to trigger the bottom networking automation"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_26d97d22","line":177,"range":{"start_line":177,"start_character":69,"end_line":177,"end_character":78},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: the Tricircle","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":175,"context_line":"  network to DB."},{"line_number":176,"context_line":""},{"line_number":177,"context_line":"When a network creation request is received in Neutron API Server in Tricircle,"},{"line_number":178,"context_line":"the type driver will be called according to the configured network type."},{"line_number":179,"context_line":""},{"line_number":180,"context_line":"2. Nova API-GW to trigger the bottom networking automation"},{"line_number":181,"context_line":""}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_8604a97e","line":178,"range":{"start_line":178,"start_character":31,"end_line":178,"end_character":43},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: based on","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":177,"context_line":"When a network creation request is received in Neutron API Server in Tricircle,"},{"line_number":178,"context_line":"the type driver will be called according to the configured network type."},{"line_number":179,"context_line":""},{"line_number":180,"context_line":"2. Nova API-GW to trigger the bottom networking automation"},{"line_number":181,"context_line":""},{"line_number":182,"context_line":"Nova API-GW can be aware of when a new VM is provisioned if boot VM api request"},{"line_number":183,"context_line":"is received, therefore Nova API-GW is responsible for the network creation in"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_06f9d980","line":180,"range":{"start_line":180,"start_character":3,"end_line":180,"end_character":58},"updated":"2016-05-29 01:49:51.000000000","message":"How do we define:\n\nbottom networking automation\n\nI am not asking you about process. I am asking you about definition of \u0027bottom networking automation\u0027 itself.","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"4efe21caa774909cd7b53e151044be8a932a01ed","unresolved":false,"context_lines":[{"line_number":177,"context_line":"When a network creation request is received in Neutron API Server in Tricircle,"},{"line_number":178,"context_line":"the type driver will be called according to the configured network type."},{"line_number":179,"context_line":""},{"line_number":180,"context_line":"2. Nova API-GW to trigger the bottom networking automation"},{"line_number":181,"context_line":""},{"line_number":182,"context_line":"Nova API-GW can be aware of when a new VM is provisioned if boot VM api request"},{"line_number":183,"context_line":"is received, therefore Nova API-GW is responsible for the network creation in"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_bb4c5771","line":180,"range":{"start_line":180,"start_character":3,"end_line":180,"end_character":58},"in_reply_to":"9abb7d3a_06f9d980","updated":"2016-05-30 05:15:52.000000000","message":"just networking automation in bottom OpenStack. no new concept","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":179,"context_line":""},{"line_number":180,"context_line":"2. Nova API-GW to trigger the bottom networking automation"},{"line_number":181,"context_line":""},{"line_number":182,"context_line":"Nova API-GW can be aware of when a new VM is provisioned if boot VM api request"},{"line_number":183,"context_line":"is received, therefore Nova API-GW is responsible for the network creation in"},{"line_number":184,"context_line":"the bottom OpenStack instances."},{"line_number":185,"context_line":""}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_26f05d90","line":182,"range":{"start_line":182,"start_character":19,"end_line":182,"end_character":27},"updated":"2016-05-29 01:49:51.000000000","message":"aware of \u0027what\u0027?","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":183,"context_line":"is received, therefore Nova API-GW is responsible for the network creation in"},{"line_number":184,"context_line":"the bottom OpenStack instances."},{"line_number":185,"context_line":""},{"line_number":186,"context_line":"Nova API-GW needs to get the network type from Neutron API server in Tricircle,"},{"line_number":187,"context_line":"and deal with the networking automation according to the network type:"},{"line_number":188,"context_line":""},{"line_number":189,"context_line":"* Shared VLAN"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_c6351147","line":186,"range":{"start_line":186,"start_character":69,"end_line":186,"end_character":78},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: the Tricircle","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":184,"context_line":"the bottom OpenStack instances."},{"line_number":185,"context_line":""},{"line_number":186,"context_line":"Nova API-GW needs to get the network type from Neutron API server in Tricircle,"},{"line_number":187,"context_line":"and deal with the networking automation according to the network type:"},{"line_number":188,"context_line":""},{"line_number":189,"context_line":"* Shared VLAN"},{"line_number":190,"context_line":"  Nova API-GW creates network in bottom pod where the VM will reside with the"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_a63a8d34","line":187,"range":{"start_line":187,"start_character":40,"end_line":187,"end_character":52},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: based on","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":187,"context_line":"and deal with the networking automation according to the network type:"},{"line_number":188,"context_line":""},{"line_number":189,"context_line":"* Shared VLAN"},{"line_number":190,"context_line":"  Nova API-GW creates network in bottom pod where the VM will reside with the"},{"line_number":191,"context_line":"  VLAN segment id, network name and network type that retrieved from the Neutron"},{"line_number":192,"context_line":"  API server in the Tricircle."},{"line_number":193,"context_line":""}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_2647bdbc","line":190,"range":{"start_line":190,"start_character":62,"end_line":190,"end_character":68},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: \u0027run\u0027 or maybe \u0027be launched\u0027","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":187,"context_line":"and deal with the networking automation according to the network type:"},{"line_number":188,"context_line":""},{"line_number":189,"context_line":"* Shared VLAN"},{"line_number":190,"context_line":"  Nova API-GW creates network in bottom pod where the VM will reside with the"},{"line_number":191,"context_line":"  VLAN segment id, network name and network type that retrieved from the Neutron"},{"line_number":192,"context_line":"  API server in the Tricircle."},{"line_number":193,"context_line":""}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_e63c9531","line":190,"range":{"start_line":190,"start_character":40,"end_line":190,"end_character":43},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: OpenStack instance","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":187,"context_line":"and deal with the networking automation according to the network type:"},{"line_number":188,"context_line":""},{"line_number":189,"context_line":"* Shared VLAN"},{"line_number":190,"context_line":"  Nova API-GW creates network in bottom pod where the VM will reside with the"},{"line_number":191,"context_line":"  VLAN segment id, network name and network type that retrieved from the Neutron"},{"line_number":192,"context_line":"  API server in the Tricircle."},{"line_number":193,"context_line":""}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_464ac1c6","line":190,"range":{"start_line":190,"start_character":44,"end_line":190,"end_character":49},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: in which","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":188,"context_line":""},{"line_number":189,"context_line":"* Shared VLAN"},{"line_number":190,"context_line":"  Nova API-GW creates network in bottom pod where the VM will reside with the"},{"line_number":191,"context_line":"  VLAN segment id, network name and network type that retrieved from the Neutron"},{"line_number":192,"context_line":"  API server in the Tricircle."},{"line_number":193,"context_line":""},{"line_number":194,"context_line":"* Shared VxLAN"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_066ef92e","line":191,"range":{"start_line":191,"start_character":54,"end_line":191,"end_character":63},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: are retrieved","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":188,"context_line":""},{"line_number":189,"context_line":"* Shared VLAN"},{"line_number":190,"context_line":"  Nova API-GW creates network in bottom pod where the VM will reside with the"},{"line_number":191,"context_line":"  VLAN segment id, network name and network type that retrieved from the Neutron"},{"line_number":192,"context_line":"  API server in the Tricircle."},{"line_number":193,"context_line":""},{"line_number":194,"context_line":"* Shared VxLAN"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_a611edae","line":191,"range":{"start_line":191,"start_character":19,"end_line":191,"end_character":48},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: network name and type","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":192,"context_line":"  API server in the Tricircle."},{"line_number":193,"context_line":""},{"line_number":194,"context_line":"* Shared VxLAN"},{"line_number":195,"context_line":"  Nova API-GW creates network in bottom pod where the VM will reside with the"},{"line_number":196,"context_line":"  VxLAN segment id, network name and network type which is retrieved from"},{"line_number":197,"context_line":"  Tricricle Neutron API server. After the network in the bottom is created"},{"line_number":198,"context_line":"  successfully, need to make this network in the bottom pod as one of the"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_667ee5e5","line":195,"range":{"start_line":195,"start_character":62,"end_line":195,"end_character":68},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: \u0027run\u0027 or \u0027 maybe \u0027be launched\u0027","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":192,"context_line":"  API server in the Tricircle."},{"line_number":193,"context_line":""},{"line_number":194,"context_line":"* Shared VxLAN"},{"line_number":195,"context_line":"  Nova API-GW creates network in bottom pod where the VM will reside with the"},{"line_number":196,"context_line":"  VxLAN segment id, network name and network type which is retrieved from"},{"line_number":197,"context_line":"  Tricricle Neutron API server. After the network in the bottom is created"},{"line_number":198,"context_line":"  successfully, need to make this network in the bottom pod as one of the"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_e623f503","line":195,"range":{"start_line":195,"start_character":40,"end_line":195,"end_character":43},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: OpenStack instance","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":192,"context_line":"  API server in the Tricircle."},{"line_number":193,"context_line":""},{"line_number":194,"context_line":"* Shared VxLAN"},{"line_number":195,"context_line":"  Nova API-GW creates network in bottom pod where the VM will reside with the"},{"line_number":196,"context_line":"  VxLAN segment id, network name and network type which is retrieved from"},{"line_number":197,"context_line":"  Tricricle Neutron API server. After the network in the bottom is created"},{"line_number":198,"context_line":"  successfully, need to make this network in the bottom pod as one of the"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_261e9dba","line":195,"range":{"start_line":195,"start_character":44,"end_line":195,"end_character":49},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: in which","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":193,"context_line":""},{"line_number":194,"context_line":"* Shared VxLAN"},{"line_number":195,"context_line":"  Nova API-GW creates network in bottom pod where the VM will reside with the"},{"line_number":196,"context_line":"  VxLAN segment id, network name and network type which is retrieved from"},{"line_number":197,"context_line":"  Tricricle Neutron API server. After the network in the bottom is created"},{"line_number":198,"context_line":"  successfully, need to make this network in the bottom pod as one of the"},{"line_number":199,"context_line":"  segments in the network in Tricircle."}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_e66ad519","line":196,"range":{"start_line":196,"start_character":56,"end_line":196,"end_character":68},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: are retrieved","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":193,"context_line":""},{"line_number":194,"context_line":"* Shared VxLAN"},{"line_number":195,"context_line":"  Nova API-GW creates network in bottom pod where the VM will reside with the"},{"line_number":196,"context_line":"  VxLAN segment id, network name and network type which is retrieved from"},{"line_number":197,"context_line":"  Tricricle Neutron API server. After the network in the bottom is created"},{"line_number":198,"context_line":"  successfully, need to make this network in the bottom pod as one of the"},{"line_number":199,"context_line":"  segments in the network in Tricircle."}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_c68351cb","line":196,"range":{"start_line":196,"start_character":20,"end_line":196,"end_character":49},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: network name and type","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":194,"context_line":"* Shared VxLAN"},{"line_number":195,"context_line":"  Nova API-GW creates network in bottom pod where the VM will reside with the"},{"line_number":196,"context_line":"  VxLAN segment id, network name and network type which is retrieved from"},{"line_number":197,"context_line":"  Tricricle Neutron API server. After the network in the bottom is created"},{"line_number":198,"context_line":"  successfully, need to make this network in the bottom pod as one of the"},{"line_number":199,"context_line":"  segments in the network in Tricircle."},{"line_number":200,"context_line":""}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_66654544","line":197,"range":{"start_line":197,"start_character":57,"end_line":197,"end_character":63},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: bottom OpenStack instance","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":195,"context_line":"  Nova API-GW creates network in bottom pod where the VM will reside with the"},{"line_number":196,"context_line":"  VxLAN segment id, network name and network type which is retrieved from"},{"line_number":197,"context_line":"  Tricricle Neutron API server. After the network in the bottom is created"},{"line_number":198,"context_line":"  successfully, need to make this network in the bottom pod as one of the"},{"line_number":199,"context_line":"  segments in the network in Tricircle."},{"line_number":200,"context_line":""},{"line_number":201,"context_line":"* Mixed VLAN/VxLAN"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_0655594f","line":198,"range":{"start_line":198,"start_character":16,"end_line":198,"end_character":20},"updated":"2016-05-29 01:49:51.000000000","message":"Add subject","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":195,"context_line":"  Nova API-GW creates network in bottom pod where the VM will reside with the"},{"line_number":196,"context_line":"  VxLAN segment id, network name and network type which is retrieved from"},{"line_number":197,"context_line":"  Tricricle Neutron API server. After the network in the bottom is created"},{"line_number":198,"context_line":"  successfully, need to make this network in the bottom pod as one of the"},{"line_number":199,"context_line":"  segments in the network in Tricircle."},{"line_number":200,"context_line":""},{"line_number":201,"context_line":"* Mixed VLAN/VxLAN"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_66cc2536","line":198,"range":{"start_line":198,"start_character":56,"end_line":198,"end_character":59},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: OpenStack instance","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":196,"context_line":"  VxLAN segment id, network name and network type which is retrieved from"},{"line_number":197,"context_line":"  Tricricle Neutron API server. After the network in the bottom is created"},{"line_number":198,"context_line":"  successfully, need to make this network in the bottom pod as one of the"},{"line_number":199,"context_line":"  segments in the network in Tricircle."},{"line_number":200,"context_line":""},{"line_number":201,"context_line":"* Mixed VLAN/VxLAN"},{"line_number":202,"context_line":"  Nova API-GW creates network in different bottom pods where the VM will reside"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_c6d191cf","line":199,"range":{"start_line":199,"start_character":29,"end_line":199,"end_character":38},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: the Tricircle","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":199,"context_line":"  segments in the network in Tricircle."},{"line_number":200,"context_line":""},{"line_number":201,"context_line":"* Mixed VLAN/VxLAN"},{"line_number":202,"context_line":"  Nova API-GW creates network in different bottom pods where the VM will reside"},{"line_number":203,"context_line":"  with the VLAN or VxLAN segment id respectively, network name and network type"},{"line_number":204,"context_line":"  which is retrieved from Tricricle Neutron API server. After the network in the"},{"line_number":205,"context_line":"  bottom is created successfully, need to update network in top with the"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_46e641b5","line":202,"range":{"start_line":202,"start_character":73,"end_line":202,"end_character":79},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: \u0027run\u0027 or \u0027 maybe \u0027be launched\u0027","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":199,"context_line":"  segments in the network in Tricircle."},{"line_number":200,"context_line":""},{"line_number":201,"context_line":"* Mixed VLAN/VxLAN"},{"line_number":202,"context_line":"  Nova API-GW creates network in different bottom pods where the VM will reside"},{"line_number":203,"context_line":"  with the VLAN or VxLAN segment id respectively, network name and network type"},{"line_number":204,"context_line":"  which is retrieved from Tricricle Neutron API server. After the network in the"},{"line_number":205,"context_line":"  bottom is created successfully, need to update network in top with the"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_06dc39e3","line":202,"range":{"start_line":202,"start_character":50,"end_line":202,"end_character":54},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: OpenStack instance","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":199,"context_line":"  segments in the network in Tricircle."},{"line_number":200,"context_line":""},{"line_number":201,"context_line":"* Mixed VLAN/VxLAN"},{"line_number":202,"context_line":"  Nova API-GW creates network in different bottom pods where the VM will reside"},{"line_number":203,"context_line":"  with the VLAN or VxLAN segment id respectively, network name and network type"},{"line_number":204,"context_line":"  which is retrieved from Tricricle Neutron API server. After the network in the"},{"line_number":205,"context_line":"  bottom is created successfully, need to update network in top with the"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_e6d815f2","line":202,"range":{"start_line":202,"start_character":55,"end_line":202,"end_character":60},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: in which","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":200,"context_line":""},{"line_number":201,"context_line":"* Mixed VLAN/VxLAN"},{"line_number":202,"context_line":"  Nova API-GW creates network in different bottom pods where the VM will reside"},{"line_number":203,"context_line":"  with the VLAN or VxLAN segment id respectively, network name and network type"},{"line_number":204,"context_line":"  which is retrieved from Tricricle Neutron API server. After the network in the"},{"line_number":205,"context_line":"  bottom is created successfully, need to update network in top with the"},{"line_number":206,"context_line":"  segmentation information of bottom netwoks."}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_26e33da5","line":203,"range":{"start_line":203,"start_character":50,"end_line":203,"end_character":79},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: network name and type","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":201,"context_line":"* Mixed VLAN/VxLAN"},{"line_number":202,"context_line":"  Nova API-GW creates network in different bottom pods where the VM will reside"},{"line_number":203,"context_line":"  with the VLAN or VxLAN segment id respectively, network name and network type"},{"line_number":204,"context_line":"  which is retrieved from Tricricle Neutron API server. After the network in the"},{"line_number":205,"context_line":"  bottom is created successfully, need to update network in top with the"},{"line_number":206,"context_line":"  segmentation information of bottom netwoks."},{"line_number":207,"context_line":""}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_66f38574","line":204,"range":{"start_line":204,"start_character":8,"end_line":204,"end_character":20},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: are retrieved","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":202,"context_line":"  Nova API-GW creates network in different bottom pods where the VM will reside"},{"line_number":203,"context_line":"  with the VLAN or VxLAN segment id respectively, network name and network type"},{"line_number":204,"context_line":"  which is retrieved from Tricricle Neutron API server. After the network in the"},{"line_number":205,"context_line":"  bottom is created successfully, need to update network in top with the"},{"line_number":206,"context_line":"  segmentation information of bottom netwoks."},{"line_number":207,"context_line":""},{"line_number":208,"context_line":"3. L2GW driver under Tricircle Plugin in Neutron API server"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_e6ff7532","line":205,"range":{"start_line":205,"start_character":34,"end_line":205,"end_character":38},"updated":"2016-05-29 01:49:51.000000000","message":"Add subject","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":202,"context_line":"  Nova API-GW creates network in different bottom pods where the VM will reside"},{"line_number":203,"context_line":"  with the VLAN or VxLAN segment id respectively, network name and network type"},{"line_number":204,"context_line":"  which is retrieved from Tricricle Neutron API server. After the network in the"},{"line_number":205,"context_line":"  bottom is created successfully, need to update network in top with the"},{"line_number":206,"context_line":"  segmentation information of bottom netwoks."},{"line_number":207,"context_line":""},{"line_number":208,"context_line":"3. L2GW driver under Tricircle Plugin in Neutron API server"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_c6e8717f","line":205,"range":{"start_line":205,"start_character":2,"end_line":205,"end_character":8},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: bottom OpenStack instances","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":202,"context_line":"  Nova API-GW creates network in different bottom pods where the VM will reside"},{"line_number":203,"context_line":"  with the VLAN or VxLAN segment id respectively, network name and network type"},{"line_number":204,"context_line":"  which is retrieved from Tricricle Neutron API server. After the network in the"},{"line_number":205,"context_line":"  bottom is created successfully, need to update network in top with the"},{"line_number":206,"context_line":"  segmentation information of bottom netwoks."},{"line_number":207,"context_line":""},{"line_number":208,"context_line":"3. L2GW driver under Tricircle Plugin in Neutron API server"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_46fda139","line":205,"range":{"start_line":205,"start_character":60,"end_line":205,"end_character":63},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: the Tricircle","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":207,"context_line":""},{"line_number":208,"context_line":"3. L2GW driver under Tricircle Plugin in Neutron API server"},{"line_number":209,"context_line":""},{"line_number":210,"context_line":"Tricircle plugin needs to support multi-segment network extension[3]."},{"line_number":211,"context_line":""},{"line_number":212,"context_line":"For Shared VxLAN or Mixed VLAN/VxLAN L2 network type, it’ll be a multi-segment"},{"line_number":213,"context_line":"network in Neutron API server in Tiricircle. Each network in the bottom"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_26fa1d43","line":210,"range":{"start_line":210,"start_character":65,"end_line":210,"end_character":69},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: .[3]","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":209,"context_line":""},{"line_number":210,"context_line":"Tricircle plugin needs to support multi-segment network extension[3]."},{"line_number":211,"context_line":""},{"line_number":212,"context_line":"For Shared VxLAN or Mixed VLAN/VxLAN L2 network type, it’ll be a multi-segment"},{"line_number":213,"context_line":"network in Neutron API server in Tiricircle. Each network in the bottom"},{"line_number":214,"context_line":"OpenStack will be a segment for the whole cross pod L2 network in Tricircle."},{"line_number":215,"context_line":""}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_669a6516","line":212,"range":{"start_line":212,"start_character":54,"end_line":212,"end_character":56},"updated":"2016-05-29 01:49:51.000000000","message":"what is \u0027it\u0027?","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":210,"context_line":"Tricircle plugin needs to support multi-segment network extension[3]."},{"line_number":211,"context_line":""},{"line_number":212,"context_line":"For Shared VxLAN or Mixed VLAN/VxLAN L2 network type, it’ll be a multi-segment"},{"line_number":213,"context_line":"network in Neutron API server in Tiricircle. Each network in the bottom"},{"line_number":214,"context_line":"OpenStack will be a segment for the whole cross pod L2 network in Tricircle."},{"line_number":215,"context_line":""},{"line_number":216,"context_line":"After the network in the bottom was created successfully, Nova API-GW is"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_a6a44d57","line":213,"range":{"start_line":213,"start_character":33,"end_line":213,"end_character":43},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: the Tricircle","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":211,"context_line":""},{"line_number":212,"context_line":"For Shared VxLAN or Mixed VLAN/VxLAN L2 network type, it’ll be a multi-segment"},{"line_number":213,"context_line":"network in Neutron API server in Tiricircle. Each network in the bottom"},{"line_number":214,"context_line":"OpenStack will be a segment for the whole cross pod L2 network in Tricircle."},{"line_number":215,"context_line":""},{"line_number":216,"context_line":"After the network in the bottom was created successfully, Nova API-GW is"},{"line_number":217,"context_line":"responsible to call Neutron server api to update the network in Tricircle"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_068a79bf","line":214,"range":{"start_line":214,"start_character":0,"end_line":214,"end_character":9},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: OpenStack instance","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":211,"context_line":""},{"line_number":212,"context_line":"For Shared VxLAN or Mixed VLAN/VxLAN L2 network type, it’ll be a multi-segment"},{"line_number":213,"context_line":"network in Neutron API server in Tiricircle. Each network in the bottom"},{"line_number":214,"context_line":"OpenStack will be a segment for the whole cross pod L2 network in Tricircle."},{"line_number":215,"context_line":""},{"line_number":216,"context_line":"After the network in the bottom was created successfully, Nova API-GW is"},{"line_number":217,"context_line":"responsible to call Neutron server api to update the network in Tricircle"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_e68655b8","line":214,"range":{"start_line":214,"start_character":55,"end_line":214,"end_character":62},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: networking","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":211,"context_line":""},{"line_number":212,"context_line":"For Shared VxLAN or Mixed VLAN/VxLAN L2 network type, it’ll be a multi-segment"},{"line_number":213,"context_line":"network in Neutron API server in Tiricircle. Each network in the bottom"},{"line_number":214,"context_line":"OpenStack will be a segment for the whole cross pod L2 network in Tricircle."},{"line_number":215,"context_line":""},{"line_number":216,"context_line":"After the network in the bottom was created successfully, Nova API-GW is"},{"line_number":217,"context_line":"responsible to call Neutron server api to update the network in Tricircle"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_469481e1","line":214,"range":{"start_line":214,"start_character":66,"end_line":214,"end_character":75},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: the Tricircle","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":213,"context_line":"network in Neutron API server in Tiricircle. Each network in the bottom"},{"line_number":214,"context_line":"OpenStack will be a segment for the whole cross pod L2 network in Tricircle."},{"line_number":215,"context_line":""},{"line_number":216,"context_line":"After the network in the bottom was created successfully, Nova API-GW is"},{"line_number":217,"context_line":"responsible to call Neutron server api to update the network in Tricircle"},{"line_number":218,"context_line":"with a new segment from the network in the bottom pod."},{"line_number":219,"context_line":""}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_26917df1","line":216,"range":{"start_line":216,"start_character":25,"end_line":216,"end_character":31},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: bottom OpenStack instance","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":214,"context_line":"OpenStack will be a segment for the whole cross pod L2 network in Tricircle."},{"line_number":215,"context_line":""},{"line_number":216,"context_line":"After the network in the bottom was created successfully, Nova API-GW is"},{"line_number":217,"context_line":"responsible to call Neutron server api to update the network in Tricircle"},{"line_number":218,"context_line":"with a new segment from the network in the bottom pod."},{"line_number":219,"context_line":""},{"line_number":220,"context_line":"If the network in the bottom was removed successfully, Nova API-GW is"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_c6b6b189","line":217,"range":{"start_line":217,"start_character":64,"end_line":217,"end_character":73},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: the Tricircle","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":213,"context_line":"network in Neutron API server in Tiricircle. Each network in the bottom"},{"line_number":214,"context_line":"OpenStack will be a segment for the whole cross pod L2 network in Tricircle."},{"line_number":215,"context_line":""},{"line_number":216,"context_line":"After the network in the bottom was created successfully, Nova API-GW is"},{"line_number":217,"context_line":"responsible to call Neutron server api to update the network in Tricircle"},{"line_number":218,"context_line":"with a new segment from the network in the bottom pod."},{"line_number":219,"context_line":""},{"line_number":220,"context_line":"If the network in the bottom was removed successfully, Nova API-GW is"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_66c1c5e4","line":217,"range":{"start_line":216,"start_character":70,"end_line":217,"end_character":14},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: will","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":215,"context_line":""},{"line_number":216,"context_line":"After the network in the bottom was created successfully, Nova API-GW is"},{"line_number":217,"context_line":"responsible to call Neutron server api to update the network in Tricircle"},{"line_number":218,"context_line":"with a new segment from the network in the bottom pod."},{"line_number":219,"context_line":""},{"line_number":220,"context_line":"If the network in the bottom was removed successfully, Nova API-GW is"},{"line_number":221,"context_line":"responsible to call Neutron server api to remove the segment in the bottom"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_06b1d98f","line":218,"range":{"start_line":218,"start_character":50,"end_line":218,"end_character":53},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: OpenStack instance","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":217,"context_line":"responsible to call Neutron server api to update the network in Tricircle"},{"line_number":218,"context_line":"with a new segment from the network in the bottom pod."},{"line_number":219,"context_line":""},{"line_number":220,"context_line":"If the network in the bottom was removed successfully, Nova API-GW is"},{"line_number":221,"context_line":"responsible to call Neutron server api to remove the segment in the bottom"},{"line_number":222,"context_line":"pod from network in Tricircle."},{"line_number":223,"context_line":""}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_e6adb532","line":220,"range":{"start_line":220,"start_character":22,"end_line":220,"end_character":28},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: bottom OpenStack instance","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":217,"context_line":"responsible to call Neutron server api to update the network in Tricircle"},{"line_number":218,"context_line":"with a new segment from the network in the bottom pod."},{"line_number":219,"context_line":""},{"line_number":220,"context_line":"If the network in the bottom was removed successfully, Nova API-GW is"},{"line_number":221,"context_line":"responsible to call Neutron server api to remove the segment in the bottom"},{"line_number":222,"context_line":"pod from network in Tricircle."},{"line_number":223,"context_line":""},{"line_number":224,"context_line":"When L2GW driver under Tricircle Plugin in Neutron API server receives the"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_46abe11d","line":221,"range":{"start_line":220,"start_character":67,"end_line":221,"end_character":14},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: will","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":219,"context_line":""},{"line_number":220,"context_line":"If the network in the bottom was removed successfully, Nova API-GW is"},{"line_number":221,"context_line":"responsible to call Neutron server api to remove the segment in the bottom"},{"line_number":222,"context_line":"pod from network in Tricircle."},{"line_number":223,"context_line":""},{"line_number":224,"context_line":"When L2GW driver under Tricircle Plugin in Neutron API server receives the"},{"line_number":225,"context_line":"segment update request, L2GW driver is responsible to start async job to"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_8663091a","line":222,"range":{"start_line":222,"start_character":0,"end_line":222,"end_character":3},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: OpenStack instance","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":219,"context_line":""},{"line_number":220,"context_line":"If the network in the bottom was removed successfully, Nova API-GW is"},{"line_number":221,"context_line":"responsible to call Neutron server api to remove the segment in the bottom"},{"line_number":222,"context_line":"pod from network in Tricircle."},{"line_number":223,"context_line":""},{"line_number":224,"context_line":"When L2GW driver under Tricircle Plugin in Neutron API server receives the"},{"line_number":225,"context_line":"segment update request, L2GW driver is responsible to start async job to"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_6668a5f6","line":222,"range":{"start_line":222,"start_character":20,"end_line":222,"end_character":29},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: the Tricircle","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":222,"context_line":"pod from network in Tricircle."},{"line_number":223,"context_line":""},{"line_number":224,"context_line":"When L2GW driver under Tricircle Plugin in Neutron API server receives the"},{"line_number":225,"context_line":"segment update request, L2GW driver is responsible to start async job to"},{"line_number":226,"context_line":"orchestrate L2GW api for L2 networking automation[1][2]."},{"line_number":227,"context_line":""},{"line_number":228,"context_line":""}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_c66d1106","line":225,"range":{"start_line":225,"start_character":36,"end_line":225,"end_character":53},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: will","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"2cbc04b399f663f9258fccb1e533731977ad606b","unresolved":false,"context_lines":[{"line_number":223,"context_line":""},{"line_number":224,"context_line":"When L2GW driver under Tricircle Plugin in Neutron API server receives the"},{"line_number":225,"context_line":"segment update request, L2GW driver is responsible to start async job to"},{"line_number":226,"context_line":"orchestrate L2GW api for L2 networking automation[1][2]."},{"line_number":227,"context_line":""},{"line_number":228,"context_line":""},{"line_number":229,"context_line":"Data model impact"}],"source_content_type":"text/x-rst","patch_set":22,"id":"9abb7d3a_a6728de3","line":226,"range":{"start_line":226,"start_character":49,"end_line":226,"end_character":56},"updated":"2016-05-29 01:49:51.000000000","message":"Minor: .[1][2]","commit_id":"7bf214c517a44ece56fdf11da16dce61c0ad97d6"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"8f7b3f78144b039bcbadcacd39e52a7f5dba42a7","unresolved":false,"context_lines":[{"line_number":24,"context_line":"Nova API-GW is the functionality to trigger automatic networking creation when"},{"line_number":25,"context_line":"new VMs are being provisioned. Neutron Tricircle plug-in is the functionality"},{"line_number":26,"context_line":"to create cross OpenStack L2/L3 networking for new VMs. After the binding of"},{"line_number":27,"context_line":"tenant-id and pod finished in the Tricircle. Cinder API-GW and Nova API-GW"},{"line_number":28,"context_line":"will pass the cinder api or nova api request to appropriate bottom OpenStack"},{"line_number":29,"context_line":"instance."},{"line_number":30,"context_line":""}],"source_content_type":"text/x-rst","patch_set":23,"id":"9abb7d3a_df335512","line":27,"range":{"start_line":27,"start_character":43,"end_line":27,"end_character":45},"updated":"2016-06-02 03:06:07.000000000","message":". -\u003e ,\n\nPlease go through your patch after you submitted for review","commit_id":"1aced7420bec3abeb8d0b84119f4668282c69e33"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"8f7b3f78144b039bcbadcacd39e52a7f5dba42a7","unresolved":false,"context_lines":[{"line_number":39,"context_line":"specify the \u0027availability_zone_hints\u0027(AZ or az will be used for short for"},{"line_number":40,"context_line":"availability zone) during network creation[7], in the Tricircle, the"},{"line_number":41,"context_line":"\u0027az_hints\u0027 means which AZ the network should be spreaded into. It\u0027s a little"},{"line_number":42,"context_line":"different from the network multiple provider extension[4] in Neutron. If no"},{"line_number":43,"context_line":"\u0027az_hints\u0027 was specified during network creation, this created network will be"},{"line_number":44,"context_line":"spreaded into any AZ. If there is a list of \u0027az_hints\u0027 during the network"},{"line_number":45,"context_line":"creation, that means the network should be able to be spread into these AZs"}],"source_content_type":"text/x-rst","patch_set":23,"id":"9abb7d3a_da4fe368","line":42,"range":{"start_line":42,"start_character":27,"end_line":42,"end_character":57},"updated":"2016-06-02 03:06:07.000000000","message":"availability zone attribute.     \nthe reference is 5, not for.\n\nPlease go through your patch after you submitted for review and check carefullly","commit_id":"1aced7420bec3abeb8d0b84119f4668282c69e33"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"8f7b3f78144b039bcbadcacd39e52a7f5dba42a7","unresolved":false,"context_lines":[{"line_number":47,"context_line":""},{"line_number":48,"context_line":"When a user creates VM or Volume, there is also one parameter called"},{"line_number":49,"context_line":"availability zone. The AZ parameter is used for Volume and VM co-location, so"},{"line_number":50,"context_line":"that the Volume and VM will be created into same bottom OpenStack instance."},{"line_number":51,"context_line":""},{"line_number":52,"context_line":"When a VM is being attached to a network, the Tricircle will check whether a"},{"line_number":53,"context_line":"VM\u0027s AZ is inside in the network\u0027s AZs scope. If a VM is not in the network\u0027s"}],"source_content_type":"text/x-rst","patch_set":23,"id":"9abb7d3a_da76c3a2","line":50,"range":{"start_line":50,"start_character":74,"end_line":50,"end_character":75},"updated":"2016-06-02 03:06:07.000000000","message":"If there are more than one pod in one AZ, refer to https://review.openstack.org/#/c/306224/ for dynamic pod binding.","commit_id":"1aced7420bec3abeb8d0b84119f4668282c69e33"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"8f7b3f78144b039bcbadcacd39e52a7f5dba42a7","unresolved":false,"context_lines":[{"line_number":64,"context_line":""},{"line_number":65,"context_line":"* Capacity expansion: tenants add VMs more and more, the capacity of one"},{"line_number":66,"context_line":"  OpenStack may not be enough, then a new OpenStack instance has to be added"},{"line_number":67,"context_line":"  to the cloud. "},{"line_number":68,"context_line":""},{"line_number":69,"context_line":"* Cross OpenStack network service chaining. Service chaining is based on"},{"line_number":70,"context_line":"  the port-pairs. Leveraging the cross pod L2 networking capability which"}],"source_content_type":"text/x-rst","patch_set":23,"id":"9abb7d3a_fa7d876d","line":67,"range":{"start_line":67,"start_character":9,"end_line":67,"end_character":14},"updated":"2016-06-02 03:06:07.000000000","message":"Please remove the unnecessary blank space.\n\nPlease go through your patch after you submitted for review and check carefully. Such a low level fault is not acceptable","commit_id":"1aced7420bec3abeb8d0b84119f4668282c69e33"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"8f7b3f78144b039bcbadcacd39e52a7f5dba42a7","unresolved":false,"context_lines":[{"line_number":96,"context_line":"  help the VMs migration in this case and it\u0027s not necessary change the"},{"line_number":97,"context_line":"  IP/MAC/Security Group configuration during VM migration."},{"line_number":98,"context_line":""},{"line_number":99,"context_line":"The spec[5] is to explain how one AZ can support more than one pod, and how"},{"line_number":100,"context_line":"to schedule a proper pod during VM or Volume creation."},{"line_number":101,"context_line":""},{"line_number":102,"context_line":"And this spec is to deal with the cross OpenStack L2 networking automation in"}],"source_content_type":"text/x-rst","patch_set":23,"id":"9abb7d3a_1ac96bac","line":99,"range":{"start_line":99,"start_character":7,"end_line":99,"end_character":11},"updated":"2016-06-02 03:06:07.000000000","message":"reference number is incorrect","commit_id":"1aced7420bec3abeb8d0b84119f4668282c69e33"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"8f7b3f78144b039bcbadcacd39e52a7f5dba42a7","unresolved":false,"context_lines":[{"line_number":521,"context_line":""},{"line_number":522,"context_line":""},{"line_number":523,"context_line":"Work Items"},{"line_number":524,"context_line":"----------"},{"line_number":525,"context_line":""},{"line_number":526,"context_line":""},{"line_number":527,"context_line":"Dependencies"}],"source_content_type":"text/x-rst","patch_set":23,"id":"9abb7d3a_7aeb57dc","line":524,"range":{"start_line":524,"start_character":0,"end_line":524,"end_character":10},"updated":"2016-06-02 03:06:07.000000000","message":"need to test the rst document format is correct or not using online rst tools","commit_id":"1aced7420bec3abeb8d0b84119f4668282c69e33"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"f19459cdb04b7ae2bbd28a7f024988380467d939","unresolved":false,"context_lines":[{"line_number":21,"context_line":"* XJob"},{"line_number":22,"context_line":"* DB"},{"line_number":23,"context_line":""},{"line_number":24,"context_line":"Nova API-GW is the functionality to trigger automatic networking creation when"},{"line_number":25,"context_line":"new VMs are being provisioned. Neutron Tricircle plug-in is the functionality"},{"line_number":26,"context_line":"to create cross OpenStack L2/L3 networking for new VMs. After the binding of"},{"line_number":27,"context_line":"tenant-id and pod finished in the Tricircle, Cinder API-GW and Nova API-GW"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_f6490290","line":24,"range":{"start_line":24,"start_character":12,"end_line":24,"end_character":14},"updated":"2016-06-06 03:40:37.000000000","message":"change to \"provides\"? automatic networking is just one of the functions","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"f19459cdb04b7ae2bbd28a7f024988380467d939","unresolved":false,"context_lines":[{"line_number":41,"context_line":"\u0027az_hints\u0027 means which AZ the network should be spreaded into. It\u0027s a little"},{"line_number":42,"context_line":"different from the network multiple provider extension[4] in Neutron. If no"},{"line_number":43,"context_line":"\u0027az_hints\u0027 was specified during network creation, this created network will be"},{"line_number":44,"context_line":"spreaded into any AZ. If there is a list of \u0027az_hints\u0027 during the network"},{"line_number":45,"context_line":"creation, that means the network should be able to be spread into these AZs"},{"line_number":46,"context_line":"which are suggested by a list of \u0027az_hints\u0027."},{"line_number":47,"context_line":""}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_31571404","line":44,"range":{"start_line":44,"start_character":0,"end_line":44,"end_character":8},"updated":"2016-06-06 03:40:37.000000000","message":"s/spreaded/spread","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"f19459cdb04b7ae2bbd28a7f024988380467d939","unresolved":false,"context_lines":[{"line_number":87,"context_line":"  is E-W (East-West) traffic for these VMs, the E-W traffic should be only"},{"line_number":88,"context_line":"  visible to the tenant, and isolation is needed. If the traffic goes through"},{"line_number":89,"context_line":"  N-S (North-South) via tenant level VPN, overhead is too much, and the"},{"line_number":90,"context_line":"  orchestration for multiple site to  site VPN connection is also complicated."},{"line_number":91,"context_line":"  Therefore cross OpenStack L2 networking to bridge the tenant\u0027s routers in"},{"line_number":92,"context_line":"  different OpenStack instances can provide more light weight isolation."},{"line_number":93,"context_line":""}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_d1785092","line":90,"range":{"start_line":90,"start_character":36,"end_line":90,"end_character":38},"updated":"2016-06-06 03:40:37.000000000","message":"remove one space","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"f19459cdb04b7ae2bbd28a7f024988380467d939","unresolved":false,"context_lines":[{"line_number":93,"context_line":""},{"line_number":94,"context_line":"* In hybrid cloud, there is cross L2 networking requirement between the"},{"line_number":95,"context_line":"  private OpenStack and the public OpenStack. Cross pod L2 networking will"},{"line_number":96,"context_line":"  help the VMs migration in this case and it\u0027s not necessary change the"},{"line_number":97,"context_line":"  IP/MAC/Security Group configuration during VM migration."},{"line_number":98,"context_line":""},{"line_number":99,"context_line":"The spec[5] is to explain how one AZ can support more than one pod, and how"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_1173f8b2","line":96,"range":{"start_line":96,"start_character":51,"end_line":96,"end_character":67},"updated":"2016-06-06 03:40:37.000000000","message":"necessary to change","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"f19459cdb04b7ae2bbd28a7f024988380467d939","unresolved":false,"context_lines":[{"line_number":212,"context_line":"  Nova API-GW creates network in bottom OpenStack instance in which the VM will"},{"line_number":213,"context_line":"  run with the VxLAN segment id, network name and type which are retrieved from"},{"line_number":214,"context_line":"  Tricricle Neutron API server. After the network in the bottom OpenStack"},{"line_number":215,"context_line":"  instance is created successfully, Nova API-GW need to make this network in the"},{"line_number":216,"context_line":"  bottom OpenStack instance as one of the segments in the network in the Tricircle."},{"line_number":217,"context_line":""},{"line_number":218,"context_line":"* Mixed VLAN/VxLAN"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_310f14e3","line":215,"range":{"start_line":215,"start_character":48,"end_line":215,"end_character":52},"updated":"2016-06-06 03:40:37.000000000","message":"s/need/needs","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"18d402b3593908f29f73aa4f1f1dc46259bc8f2b","unresolved":false,"context_lines":[{"line_number":219,"context_line":"  Nova API-GW creates network in different bottom OpenStack instance in which the"},{"line_number":220,"context_line":"  VM will run with the VLAN or VxLAN segment id respectively, network name and type"},{"line_number":221,"context_line":"  which are retrieved from Tricricle Neutron API server. After the network in the"},{"line_number":222,"context_line":"  bottom OpenStack instances is created successfully, Nova API-GW need to update"},{"line_number":223,"context_line":"  network in the Tricircle with the segmentation information of bottom netwoks."},{"line_number":224,"context_line":""},{"line_number":225,"context_line":"3. L2GW driver under Tricircle Plugin in Neutron API server"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_18204a9b","line":222,"range":{"start_line":222,"start_character":66,"end_line":222,"end_character":70},"updated":"2016-06-04 13:23:07.000000000","message":"Minor: needs","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"5205f8665b6d276dc7eff771ca88f4a9eec8e898","unresolved":false,"context_lines":[{"line_number":219,"context_line":"  Nova API-GW creates network in different bottom OpenStack instance in which the"},{"line_number":220,"context_line":"  VM will run with the VLAN or VxLAN segment id respectively, network name and type"},{"line_number":221,"context_line":"  which are retrieved from Tricricle Neutron API server. After the network in the"},{"line_number":222,"context_line":"  bottom OpenStack instances is created successfully, Nova API-GW need to update"},{"line_number":223,"context_line":"  network in the Tricircle with the segmentation information of bottom netwoks."},{"line_number":224,"context_line":""},{"line_number":225,"context_line":"3. L2GW driver under Tricircle Plugin in Neutron API server"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_5f5e3446","line":222,"range":{"start_line":222,"start_character":66,"end_line":222,"end_character":70},"in_reply_to":"7aa08908_18204a9b","updated":"2016-06-05 05:17:52.000000000","message":"Done","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"f19459cdb04b7ae2bbd28a7f024988380467d939","unresolved":false,"context_lines":[{"line_number":226,"context_line":""},{"line_number":227,"context_line":"Tricircle plugin needs to support multi-segment network extension.[3]"},{"line_number":228,"context_line":""},{"line_number":229,"context_line":"For Shared VxLAN or Mixed VLAN/VxLAN L2 network type, L2GW driver will be a"},{"line_number":230,"context_line":"multi-segment network in Neutron API server in the Tiricircle. Each network in the"},{"line_number":231,"context_line":"bottom OpenStack instance will be a segment for the whole cross pod L2 networking"},{"line_number":232,"context_line":"in the Tricircle."}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_f1a0eca7","line":229,"range":{"start_line":229,"start_character":66,"end_line":229,"end_character":73},"updated":"2016-06-06 03:40:37.000000000","message":"\"will create\"? or \"will maintain\"?","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"18d402b3593908f29f73aa4f1f1dc46259bc8f2b","unresolved":false,"context_lines":[{"line_number":226,"context_line":""},{"line_number":227,"context_line":"Tricircle plugin needs to support multi-segment network extension.[3]"},{"line_number":228,"context_line":""},{"line_number":229,"context_line":"For Shared VxLAN or Mixed VLAN/VxLAN L2 network type, L2GW driver will be a"},{"line_number":230,"context_line":"multi-segment network in Neutron API server in the Tiricircle. Each network in the"},{"line_number":231,"context_line":"bottom OpenStack instance will be a segment for the whole cross pod L2 networking"},{"line_number":232,"context_line":"in the Tricircle."},{"line_number":233,"context_line":""}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_58413239","line":230,"range":{"start_line":229,"start_character":54,"end_line":230,"end_character":43},"updated":"2016-06-04 13:23:07.000000000","message":"L2GW driver \u003d a multi-segment network?\n\n... driver \u003d ... network?","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"18d402b3593908f29f73aa4f1f1dc46259bc8f2b","unresolved":false,"context_lines":[{"line_number":228,"context_line":""},{"line_number":229,"context_line":"For Shared VxLAN or Mixed VLAN/VxLAN L2 network type, L2GW driver will be a"},{"line_number":230,"context_line":"multi-segment network in Neutron API server in the Tiricircle. Each network in the"},{"line_number":231,"context_line":"bottom OpenStack instance will be a segment for the whole cross pod L2 networking"},{"line_number":232,"context_line":"in the Tricircle."},{"line_number":233,"context_line":""},{"line_number":234,"context_line":"After the network in the bottom OpenStack instance was created successfully, Nova"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_984b9a59","line":231,"range":{"start_line":231,"start_character":34,"end_line":231,"end_character":43},"updated":"2016-06-04 13:23:07.000000000","message":"How do we define this word in this context?","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"5205f8665b6d276dc7eff771ca88f4a9eec8e898","unresolved":false,"context_lines":[{"line_number":228,"context_line":""},{"line_number":229,"context_line":"For Shared VxLAN or Mixed VLAN/VxLAN L2 network type, L2GW driver will be a"},{"line_number":230,"context_line":"multi-segment network in Neutron API server in the Tiricircle. Each network in the"},{"line_number":231,"context_line":"bottom OpenStack instance will be a segment for the whole cross pod L2 networking"},{"line_number":232,"context_line":"in the Tricircle."},{"line_number":233,"context_line":""},{"line_number":234,"context_line":"After the network in the bottom OpenStack instance was created successfully, Nova"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_3f2248ba","line":231,"range":{"start_line":231,"start_character":34,"end_line":231,"end_character":43},"in_reply_to":"7aa08908_984b9a59","updated":"2016-06-05 05:17:52.000000000","message":"No matter the network type of bottom OpenStack instances are Shared VxLAN or Mixed VLAN/VxLAN, both a segment of whole cross pod L2 networking.  \n\nIn this context， my understanding is \"a segment \u003d a part\".","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"18d402b3593908f29f73aa4f1f1dc46259bc8f2b","unresolved":false,"context_lines":[{"line_number":232,"context_line":"in the Tricircle."},{"line_number":233,"context_line":""},{"line_number":234,"context_line":"After the network in the bottom OpenStack instance was created successfully, Nova"},{"line_number":235,"context_line":"API-GW will call Neutron server api to update the network in the Tricircle with a"},{"line_number":236,"context_line":"new segment from the network in the bottom OpenStack instance."},{"line_number":237,"context_line":""},{"line_number":238,"context_line":"If the network in the bottom OpenStack instance was removed successfully, Nova"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_d881a24f","line":235,"range":{"start_line":235,"start_character":32,"end_line":235,"end_character":35},"updated":"2016-06-04 13:23:07.000000000","message":"Minor: API","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"5205f8665b6d276dc7eff771ca88f4a9eec8e898","unresolved":false,"context_lines":[{"line_number":232,"context_line":"in the Tricircle."},{"line_number":233,"context_line":""},{"line_number":234,"context_line":"After the network in the bottom OpenStack instance was created successfully, Nova"},{"line_number":235,"context_line":"API-GW will call Neutron server api to update the network in the Tricircle with a"},{"line_number":236,"context_line":"new segment from the network in the bottom OpenStack instance."},{"line_number":237,"context_line":""},{"line_number":238,"context_line":"If the network in the bottom OpenStack instance was removed successfully, Nova"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_df17c452","line":235,"range":{"start_line":235,"start_character":32,"end_line":235,"end_character":35},"in_reply_to":"7aa08908_d881a24f","updated":"2016-06-05 05:17:52.000000000","message":"Done","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"18d402b3593908f29f73aa4f1f1dc46259bc8f2b","unresolved":false,"context_lines":[{"line_number":239,"context_line":"API-GW will call Neutron server api to remove the segment in the bottom OpenStack"},{"line_number":240,"context_line":"instance from network in the Tricircle."},{"line_number":241,"context_line":""},{"line_number":242,"context_line":"When L2GW driver under Tricircle Plugin in Neutron API server receives the"},{"line_number":243,"context_line":"segment update request, L2GW driver will start async job to orchestrate L2GW api"},{"line_number":244,"context_line":"for L2 networking automation.[1][2]"},{"line_number":245,"context_line":""}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_78b6ae3e","line":242,"range":{"start_line":242,"start_character":33,"end_line":242,"end_character":39},"updated":"2016-06-04 13:23:07.000000000","message":"Minor: plugin","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"5205f8665b6d276dc7eff771ca88f4a9eec8e898","unresolved":false,"context_lines":[{"line_number":239,"context_line":"API-GW will call Neutron server api to remove the segment in the bottom OpenStack"},{"line_number":240,"context_line":"instance from network in the Tricircle."},{"line_number":241,"context_line":""},{"line_number":242,"context_line":"When L2GW driver under Tricircle Plugin in Neutron API server receives the"},{"line_number":243,"context_line":"segment update request, L2GW driver will start async job to orchestrate L2GW api"},{"line_number":244,"context_line":"for L2 networking automation.[1][2]"},{"line_number":245,"context_line":""}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_bf1c7878","line":242,"range":{"start_line":242,"start_character":33,"end_line":242,"end_character":39},"in_reply_to":"7aa08908_78b6ae3e","updated":"2016-06-05 05:17:52.000000000","message":"Done","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"18d402b3593908f29f73aa4f1f1dc46259bc8f2b","unresolved":false,"context_lines":[{"line_number":240,"context_line":"instance from network in the Tricircle."},{"line_number":241,"context_line":""},{"line_number":242,"context_line":"When L2GW driver under Tricircle Plugin in Neutron API server receives the"},{"line_number":243,"context_line":"segment update request, L2GW driver will start async job to orchestrate L2GW api"},{"line_number":244,"context_line":"for L2 networking automation.[1][2]"},{"line_number":245,"context_line":""},{"line_number":246,"context_line":""}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_187cca71","line":243,"range":{"start_line":243,"start_character":77,"end_line":243,"end_character":80},"updated":"2016-06-04 13:23:07.000000000","message":"Minor: API","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"5205f8665b6d276dc7eff771ca88f4a9eec8e898","unresolved":false,"context_lines":[{"line_number":240,"context_line":"instance from network in the Tricircle."},{"line_number":241,"context_line":""},{"line_number":242,"context_line":"When L2GW driver under Tricircle Plugin in Neutron API server receives the"},{"line_number":243,"context_line":"segment update request, L2GW driver will start async job to orchestrate L2GW api"},{"line_number":244,"context_line":"for L2 networking automation.[1][2]"},{"line_number":245,"context_line":""},{"line_number":246,"context_line":""}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_1f12ec62","line":243,"range":{"start_line":243,"start_character":77,"end_line":243,"end_character":80},"in_reply_to":"7aa08908_187cca71","updated":"2016-06-05 05:17:52.000000000","message":"Done","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"18d402b3593908f29f73aa4f1f1dc46259bc8f2b","unresolved":false,"context_lines":[{"line_number":247,"context_line":"Data model impact"},{"line_number":248,"context_line":"-----------------"},{"line_number":249,"context_line":""},{"line_number":250,"context_line":"In database, we are considering setting physical_network in top OpenStack as"},{"line_number":251,"context_line":"``bottom_physical_network#bottom_pod_id`` to distinguish segmentation"},{"line_number":252,"context_line":"information in different bottom OpenStack."},{"line_number":253,"context_line":""}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_f880de48","line":250,"range":{"start_line":250,"start_character":64,"end_line":250,"end_character":73},"updated":"2016-06-04 13:23:07.000000000","message":"Minor: OpenStack instance","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"5205f8665b6d276dc7eff771ca88f4a9eec8e898","unresolved":false,"context_lines":[{"line_number":247,"context_line":"Data model impact"},{"line_number":248,"context_line":"-----------------"},{"line_number":249,"context_line":""},{"line_number":250,"context_line":"In database, we are considering setting physical_network in top OpenStack as"},{"line_number":251,"context_line":"``bottom_physical_network#bottom_pod_id`` to distinguish segmentation"},{"line_number":252,"context_line":"information in different bottom OpenStack."},{"line_number":253,"context_line":""}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_ff160054","line":250,"range":{"start_line":250,"start_character":64,"end_line":250,"end_character":73},"in_reply_to":"7aa08908_f880de48","updated":"2016-06-05 05:17:52.000000000","message":"Done","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"18d402b3593908f29f73aa4f1f1dc46259bc8f2b","unresolved":false,"context_lines":[{"line_number":248,"context_line":"-----------------"},{"line_number":249,"context_line":""},{"line_number":250,"context_line":"In database, we are considering setting physical_network in top OpenStack as"},{"line_number":251,"context_line":"``bottom_physical_network#bottom_pod_id`` to distinguish segmentation"},{"line_number":252,"context_line":"information in different bottom OpenStack."},{"line_number":253,"context_line":""},{"line_number":254,"context_line":"REST API impact"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_38da6679","line":251,"range":{"start_line":251,"start_character":45,"end_line":251,"end_character":56},"updated":"2016-06-04 13:23:07.000000000","message":"distinguish from what?","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"5205f8665b6d276dc7eff771ca88f4a9eec8e898","unresolved":false,"context_lines":[{"line_number":248,"context_line":"-----------------"},{"line_number":249,"context_line":""},{"line_number":250,"context_line":"In database, we are considering setting physical_network in top OpenStack as"},{"line_number":251,"context_line":"``bottom_physical_network#bottom_pod_id`` to distinguish segmentation"},{"line_number":252,"context_line":"information in different bottom OpenStack."},{"line_number":253,"context_line":""},{"line_number":254,"context_line":"REST API impact"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_ba03e60c","line":251,"range":{"start_line":251,"start_character":45,"end_line":251,"end_character":56},"in_reply_to":"7aa08908_38da6679","updated":"2016-06-05 05:17:52.000000000","message":"distinguish from the segmentation information such as \"bottom_physical_network#bottom_pod_id\"","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"f19459cdb04b7ae2bbd28a7f024988380467d939","unresolved":false,"context_lines":[{"line_number":248,"context_line":"-----------------"},{"line_number":249,"context_line":""},{"line_number":250,"context_line":"In database, we are considering setting physical_network in top OpenStack as"},{"line_number":251,"context_line":"``bottom_physical_network#bottom_pod_id`` to distinguish segmentation"},{"line_number":252,"context_line":"information in different bottom OpenStack."},{"line_number":253,"context_line":""},{"line_number":254,"context_line":"REST API impact"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_b176643c","line":251,"range":{"start_line":251,"start_character":45,"end_line":251,"end_character":56},"in_reply_to":"7aa08908_38da6679","updated":"2016-06-06 03:40:37.000000000","message":"each bottom pod has one network, so save pod id in \"physical_network\" field to tell which pod the segment belongs to.","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"18d402b3593908f29f73aa4f1f1dc46259bc8f2b","unresolved":false,"context_lines":[{"line_number":249,"context_line":""},{"line_number":250,"context_line":"In database, we are considering setting physical_network in top OpenStack as"},{"line_number":251,"context_line":"``bottom_physical_network#bottom_pod_id`` to distinguish segmentation"},{"line_number":252,"context_line":"information in different bottom OpenStack."},{"line_number":253,"context_line":""},{"line_number":254,"context_line":"REST API impact"},{"line_number":255,"context_line":"---------------"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_788d0e7b","line":252,"range":{"start_line":252,"start_character":32,"end_line":252,"end_character":41},"updated":"2016-06-04 13:23:07.000000000","message":"Minor: OpenStack instance","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"5205f8665b6d276dc7eff771ca88f4a9eec8e898","unresolved":false,"context_lines":[{"line_number":249,"context_line":""},{"line_number":250,"context_line":"In database, we are considering setting physical_network in top OpenStack as"},{"line_number":251,"context_line":"``bottom_physical_network#bottom_pod_id`` to distinguish segmentation"},{"line_number":252,"context_line":"information in different bottom OpenStack."},{"line_number":253,"context_line":""},{"line_number":254,"context_line":"REST API impact"},{"line_number":255,"context_line":"---------------"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_7f033010","line":252,"range":{"start_line":252,"start_character":32,"end_line":252,"end_character":41},"in_reply_to":"7aa08908_788d0e7b","updated":"2016-06-05 05:17:52.000000000","message":"Done","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"18d402b3593908f29f73aa4f1f1dc46259bc8f2b","unresolved":false,"context_lines":[{"line_number":290,"context_line":"Implementation"},{"line_number":291,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":292,"context_line":""},{"line_number":293,"context_line":"**Local Network Implementation:**"},{"line_number":294,"context_line":""},{"line_number":295,"context_line":"For Local Network, L2GW is not required. In this scenario, no cross pod L2/L3"},{"line_number":296,"context_line":"networking is required."}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_98e71a40","line":293,"range":{"start_line":293,"start_character":2,"end_line":293,"end_character":31},"updated":"2016-06-04 13:23:07.000000000","message":"Delete: \":\"","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"5205f8665b6d276dc7eff771ca88f4a9eec8e898","unresolved":false,"context_lines":[{"line_number":290,"context_line":"Implementation"},{"line_number":291,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":292,"context_line":""},{"line_number":293,"context_line":"**Local Network Implementation:**"},{"line_number":294,"context_line":""},{"line_number":295,"context_line":"For Local Network, L2GW is not required. In this scenario, no cross pod L2/L3"},{"line_number":296,"context_line":"networking is required."}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_1a095a2d","line":293,"range":{"start_line":293,"start_character":2,"end_line":293,"end_character":31},"in_reply_to":"7aa08908_98e71a40","updated":"2016-06-05 05:17:52.000000000","message":"Done","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"18d402b3593908f29f73aa4f1f1dc46259bc8f2b","unresolved":false,"context_lines":[{"line_number":297,"context_line":""},{"line_number":298,"context_line":"A user creates network Net1 with single AZ1 in az_hint, the Tricircle plugin"},{"line_number":299,"context_line":"checks the configuration, if ``tenant_network_type`` equals ``local_network``,"},{"line_number":300,"context_line":"it will invoke Local Network type driver. Local_Network driver under the"},{"line_number":301,"context_line":"Tricircle plugin will update network with ``network_type`` to DB."},{"line_number":302,"context_line":""},{"line_number":303,"context_line":"For exmaple, a user creates VM1 in AZ1 which has only one pod ``POD1``, and"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_b83bf69b","line":300,"range":{"start_line":300,"start_character":42,"end_line":300,"end_character":55},"updated":"2016-06-04 13:23:07.000000000","message":"Local network, instead Local_Network?","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"5205f8665b6d276dc7eff771ca88f4a9eec8e898","unresolved":false,"context_lines":[{"line_number":297,"context_line":""},{"line_number":298,"context_line":"A user creates network Net1 with single AZ1 in az_hint, the Tricircle plugin"},{"line_number":299,"context_line":"checks the configuration, if ``tenant_network_type`` equals ``local_network``,"},{"line_number":300,"context_line":"it will invoke Local Network type driver. Local_Network driver under the"},{"line_number":301,"context_line":"Tricircle plugin will update network with ``network_type`` to DB."},{"line_number":302,"context_line":""},{"line_number":303,"context_line":"For exmaple, a user creates VM1 in AZ1 which has only one pod ``POD1``, and"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_fa0d6e38","line":300,"range":{"start_line":300,"start_character":42,"end_line":300,"end_character":55},"in_reply_to":"7aa08908_b83bf69b","updated":"2016-06-05 05:17:52.000000000","message":"Done","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"18d402b3593908f29f73aa4f1f1dc46259bc8f2b","unresolved":false,"context_lines":[{"line_number":298,"context_line":"A user creates network Net1 with single AZ1 in az_hint, the Tricircle plugin"},{"line_number":299,"context_line":"checks the configuration, if ``tenant_network_type`` equals ``local_network``,"},{"line_number":300,"context_line":"it will invoke Local Network type driver. Local_Network driver under the"},{"line_number":301,"context_line":"Tricircle plugin will update network with ``network_type`` to DB."},{"line_number":302,"context_line":""},{"line_number":303,"context_line":"For exmaple, a user creates VM1 in AZ1 which has only one pod ``POD1``, and"},{"line_number":304,"context_line":"connects it to network Net1. ``Nova API-GW`` will send network creation"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_584bf22b","line":301,"range":{"start_line":301,"start_character":59,"end_line":301,"end_character":64},"updated":"2016-06-04 13:23:07.000000000","message":"Delete this.","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"18d402b3593908f29f73aa4f1f1dc46259bc8f2b","unresolved":false,"context_lines":[{"line_number":298,"context_line":"A user creates network Net1 with single AZ1 in az_hint, the Tricircle plugin"},{"line_number":299,"context_line":"checks the configuration, if ``tenant_network_type`` equals ``local_network``,"},{"line_number":300,"context_line":"it will invoke Local Network type driver. Local_Network driver under the"},{"line_number":301,"context_line":"Tricircle plugin will update network with ``network_type`` to DB."},{"line_number":302,"context_line":""},{"line_number":303,"context_line":"For exmaple, a user creates VM1 in AZ1 which has only one pod ``POD1``, and"},{"line_number":304,"context_line":"connects it to network Net1. ``Nova API-GW`` will send network creation"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_98555ac8","line":301,"range":{"start_line":301,"start_character":29,"end_line":301,"end_character":36},"updated":"2016-06-04 13:23:07.000000000","message":"network information","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"18d402b3593908f29f73aa4f1f1dc46259bc8f2b","unresolved":false,"context_lines":[{"line_number":298,"context_line":"A user creates network Net1 with single AZ1 in az_hint, the Tricircle plugin"},{"line_number":299,"context_line":"checks the configuration, if ``tenant_network_type`` equals ``local_network``,"},{"line_number":300,"context_line":"it will invoke Local Network type driver. Local_Network driver under the"},{"line_number":301,"context_line":"Tricircle plugin will update network with ``network_type`` to DB."},{"line_number":302,"context_line":""},{"line_number":303,"context_line":"For exmaple, a user creates VM1 in AZ1 which has only one pod ``POD1``, and"},{"line_number":304,"context_line":"connects it to network Net1. ``Nova API-GW`` will send network creation"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_78522edf","line":301,"range":{"start_line":301,"start_character":37,"end_line":301,"end_character":41},"updated":"2016-06-04 13:23:07.000000000","message":"of","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"18d402b3593908f29f73aa4f1f1dc46259bc8f2b","unresolved":false,"context_lines":[{"line_number":298,"context_line":"A user creates network Net1 with single AZ1 in az_hint, the Tricircle plugin"},{"line_number":299,"context_line":"checks the configuration, if ``tenant_network_type`` equals ``local_network``,"},{"line_number":300,"context_line":"it will invoke Local Network type driver. Local_Network driver under the"},{"line_number":301,"context_line":"Tricircle plugin will update network with ``network_type`` to DB."},{"line_number":302,"context_line":""},{"line_number":303,"context_line":"For exmaple, a user creates VM1 in AZ1 which has only one pod ``POD1``, and"},{"line_number":304,"context_line":"connects it to network Net1. ``Nova API-GW`` will send network creation"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_18584afa","line":301,"range":{"start_line":301,"start_character":22,"end_line":301,"end_character":64},"updated":"2016-06-04 13:23:07.000000000","message":"or just:\n\nupdate ``network_type`` in database.","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"5205f8665b6d276dc7eff771ca88f4a9eec8e898","unresolved":false,"context_lines":[{"line_number":298,"context_line":"A user creates network Net1 with single AZ1 in az_hint, the Tricircle plugin"},{"line_number":299,"context_line":"checks the configuration, if ``tenant_network_type`` equals ``local_network``,"},{"line_number":300,"context_line":"it will invoke Local Network type driver. Local_Network driver under the"},{"line_number":301,"context_line":"Tricircle plugin will update network with ``network_type`` to DB."},{"line_number":302,"context_line":""},{"line_number":303,"context_line":"For exmaple, a user creates VM1 in AZ1 which has only one pod ``POD1``, and"},{"line_number":304,"context_line":"connects it to network Net1. ``Nova API-GW`` will send network creation"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_5a13e25c","line":301,"range":{"start_line":301,"start_character":22,"end_line":301,"end_character":64},"in_reply_to":"7aa08908_18584afa","updated":"2016-06-05 05:17:52.000000000","message":"Done","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"18d402b3593908f29f73aa4f1f1dc46259bc8f2b","unresolved":false,"context_lines":[{"line_number":301,"context_line":"Tricircle plugin will update network with ``network_type`` to DB."},{"line_number":302,"context_line":""},{"line_number":303,"context_line":"For exmaple, a user creates VM1 in AZ1 which has only one pod ``POD1``, and"},{"line_number":304,"context_line":"connects it to network Net1. ``Nova API-GW`` will send network creation"},{"line_number":305,"context_line":"message to ``POD1`` and the VM will be booted in AZ1 (There should be only one"},{"line_number":306,"context_line":"pod in AZ1). Network will be created in ``POD1``."},{"line_number":307,"context_line":""}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_f85c5eef","line":304,"range":{"start_line":304,"start_character":23,"end_line":304,"end_character":27},"updated":"2016-06-04 13:23:07.000000000","message":"``Net1``","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"5205f8665b6d276dc7eff771ca88f4a9eec8e898","unresolved":false,"context_lines":[{"line_number":301,"context_line":"Tricircle plugin will update network with ``network_type`` to DB."},{"line_number":302,"context_line":""},{"line_number":303,"context_line":"For exmaple, a user creates VM1 in AZ1 which has only one pod ``POD1``, and"},{"line_number":304,"context_line":"connects it to network Net1. ``Nova API-GW`` will send network creation"},{"line_number":305,"context_line":"message to ``POD1`` and the VM will be booted in AZ1 (There should be only one"},{"line_number":306,"context_line":"pod in AZ1). Network will be created in ``POD1``."},{"line_number":307,"context_line":""}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_3a10964e","line":304,"range":{"start_line":304,"start_character":23,"end_line":304,"end_character":27},"in_reply_to":"7aa08908_f85c5eef","updated":"2016-06-05 05:17:52.000000000","message":"Done","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"18d402b3593908f29f73aa4f1f1dc46259bc8f2b","unresolved":false,"context_lines":[{"line_number":302,"context_line":""},{"line_number":303,"context_line":"For exmaple, a user creates VM1 in AZ1 which has only one pod ``POD1``, and"},{"line_number":304,"context_line":"connects it to network Net1. ``Nova API-GW`` will send network creation"},{"line_number":305,"context_line":"message to ``POD1`` and the VM will be booted in AZ1 (There should be only one"},{"line_number":306,"context_line":"pod in AZ1). Network will be created in ``POD1``."},{"line_number":307,"context_line":""},{"line_number":308,"context_line":"If a user wants to create VM2 in AZ2 or ``POD2`` in AZ1, and connect it to"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_386f0694","line":305,"range":{"start_line":305,"start_character":0,"end_line":305,"end_character":7},"updated":"2016-06-04 13:23:07.000000000","message":"request","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"5205f8665b6d276dc7eff771ca88f4a9eec8e898","unresolved":false,"context_lines":[{"line_number":302,"context_line":""},{"line_number":303,"context_line":"For exmaple, a user creates VM1 in AZ1 which has only one pod ``POD1``, and"},{"line_number":304,"context_line":"connects it to network Net1. ``Nova API-GW`` will send network creation"},{"line_number":305,"context_line":"message to ``POD1`` and the VM will be booted in AZ1 (There should be only one"},{"line_number":306,"context_line":"pod in AZ1). Network will be created in ``POD1``."},{"line_number":307,"context_line":""},{"line_number":308,"context_line":"If a user wants to create VM2 in AZ2 or ``POD2`` in AZ1, and connect it to"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_9a1d4a69","line":305,"range":{"start_line":305,"start_character":0,"end_line":305,"end_character":7},"in_reply_to":"7aa08908_386f0694","updated":"2016-06-05 05:17:52.000000000","message":"Done","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"18d402b3593908f29f73aa4f1f1dc46259bc8f2b","unresolved":false,"context_lines":[{"line_number":303,"context_line":"For exmaple, a user creates VM1 in AZ1 which has only one pod ``POD1``, and"},{"line_number":304,"context_line":"connects it to network Net1. ``Nova API-GW`` will send network creation"},{"line_number":305,"context_line":"message to ``POD1`` and the VM will be booted in AZ1 (There should be only one"},{"line_number":306,"context_line":"pod in AZ1). Network will be created in ``POD1``."},{"line_number":307,"context_line":""},{"line_number":308,"context_line":"If a user wants to create VM2 in AZ2 or ``POD2`` in AZ1, and connect it to"},{"line_number":309,"context_line":"network Net1 in the Tricircle, it would be failed. Because the Net1 is"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_180faae2","line":306,"range":{"start_line":306,"start_character":13,"end_line":306,"end_character":48},"updated":"2016-06-04 13:23:07.000000000","message":"More elaborated explanation would be helpful.","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"5205f8665b6d276dc7eff771ca88f4a9eec8e898","unresolved":false,"context_lines":[{"line_number":303,"context_line":"For exmaple, a user creates VM1 in AZ1 which has only one pod ``POD1``, and"},{"line_number":304,"context_line":"connects it to network Net1. ``Nova API-GW`` will send network creation"},{"line_number":305,"context_line":"message to ``POD1`` and the VM will be booted in AZ1 (There should be only one"},{"line_number":306,"context_line":"pod in AZ1). Network will be created in ``POD1``."},{"line_number":307,"context_line":""},{"line_number":308,"context_line":"If a user wants to create VM2 in AZ2 or ``POD2`` in AZ1, and connect it to"},{"line_number":309,"context_line":"network Net1 in the Tricircle, it would be failed. Because the Net1 is"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_ff48c089","line":306,"range":{"start_line":306,"start_character":13,"end_line":306,"end_character":48},"in_reply_to":"7aa08908_180faae2","updated":"2016-06-05 05:17:52.000000000","message":"Should this sentence changed like this:\n\n\"The network which was used to server VM1 on bottom OpenStack instance will be created in ``POD1``.","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"f19459cdb04b7ae2bbd28a7f024988380467d939","unresolved":false,"context_lines":[{"line_number":303,"context_line":"For exmaple, a user creates VM1 in AZ1 which has only one pod ``POD1``, and"},{"line_number":304,"context_line":"connects it to network Net1. ``Nova API-GW`` will send network creation"},{"line_number":305,"context_line":"message to ``POD1`` and the VM will be booted in AZ1 (There should be only one"},{"line_number":306,"context_line":"pod in AZ1). Network will be created in ``POD1``."},{"line_number":307,"context_line":""},{"line_number":308,"context_line":"If a user wants to create VM2 in AZ2 or ``POD2`` in AZ1, and connect it to"},{"line_number":309,"context_line":"network Net1 in the Tricircle, it would be failed. Because the Net1 is"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_03f3ab74","line":306,"range":{"start_line":306,"start_character":13,"end_line":306,"end_character":48},"in_reply_to":"7aa08908_180faae2","updated":"2016-06-06 03:40:37.000000000","message":"i think this sentence is not needed. it\u0027s already mentioned that nova api-gw will send network creation message to pod1","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"18d402b3593908f29f73aa4f1f1dc46259bc8f2b","unresolved":false,"context_lines":[{"line_number":309,"context_line":"network Net1 in the Tricircle, it would be failed. Because the Net1 is"},{"line_number":310,"context_line":"local_network type network and it is limited to present in ``POD1`` in AZ1 only."},{"line_number":311,"context_line":""},{"line_number":312,"context_line":"**Shared VLAN Implementation:**"},{"line_number":313,"context_line":""},{"line_number":314,"context_line":"For Shared VLAN, L2GW is not required. This is the most simplest cross pod"},{"line_number":315,"context_line":"L2 networking for limited scenario. For example, with a small number of"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_78e4ee3a","line":312,"range":{"start_line":312,"start_character":2,"end_line":312,"end_character":29},"updated":"2016-06-04 13:23:07.000000000","message":"Delete: \":\"","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"5205f8665b6d276dc7eff771ca88f4a9eec8e898","unresolved":false,"context_lines":[{"line_number":309,"context_line":"network Net1 in the Tricircle, it would be failed. Because the Net1 is"},{"line_number":310,"context_line":"local_network type network and it is limited to present in ``POD1`` in AZ1 only."},{"line_number":311,"context_line":""},{"line_number":312,"context_line":"**Shared VLAN Implementation:**"},{"line_number":313,"context_line":""},{"line_number":314,"context_line":"For Shared VLAN, L2GW is not required. This is the most simplest cross pod"},{"line_number":315,"context_line":"L2 networking for limited scenario. For example, with a small number of"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_7a1a1e70","line":312,"range":{"start_line":312,"start_character":2,"end_line":312,"end_character":29},"in_reply_to":"7aa08908_78e4ee3a","updated":"2016-06-05 05:17:52.000000000","message":"Done","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"18d402b3593908f29f73aa4f1f1dc46259bc8f2b","unresolved":false,"context_lines":[{"line_number":312,"context_line":"**Shared VLAN Implementation:**"},{"line_number":313,"context_line":""},{"line_number":314,"context_line":"For Shared VLAN, L2GW is not required. This is the most simplest cross pod"},{"line_number":315,"context_line":"L2 networking for limited scenario. For example, with a small number of"},{"line_number":316,"context_line":"networks, all VLANs are extended through physical gateway to support cross"},{"line_number":317,"context_line":"site VLAN networking, or all pods under same core switch with same visible"},{"line_number":318,"context_line":"VLAN ranges that supported by the core switch."},{"line_number":319,"context_line":""},{"line_number":320,"context_line":"when a user creates network called Net1, the Tricircle plugin checks the"},{"line_number":321,"context_line":"configuration, if ``tenant_network_type`` equals ``shared_vlan``, the"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_98039ab8","line":318,"range":{"start_line":315,"start_character":36,"end_line":318,"end_character":45},"updated":"2016-06-04 13:23:07.000000000","message":"What do you would like to tell readers through this sentence?","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"f19459cdb04b7ae2bbd28a7f024988380467d939","unresolved":false,"context_lines":[{"line_number":314,"context_line":"For Shared VLAN, L2GW is not required. This is the most simplest cross pod"},{"line_number":315,"context_line":"L2 networking for limited scenario. For example, with a small number of"},{"line_number":316,"context_line":"networks, all VLANs are extended through physical gateway to support cross"},{"line_number":317,"context_line":"site VLAN networking, or all pods under same core switch with same visible"},{"line_number":318,"context_line":"VLAN ranges that supported by the core switch."},{"line_number":319,"context_line":""},{"line_number":320,"context_line":"when a user creates network called Net1, the Tricircle plugin checks the"},{"line_number":321,"context_line":"configuration, if ``tenant_network_type`` equals ``shared_vlan``, the"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_03360b03","line":318,"range":{"start_line":317,"start_character":25,"end_line":318,"end_character":45},"updated":"2016-06-06 03:40:37.000000000","message":"this is not a sentence. all words after \"all pods\" are just modifier on \"all pods\"","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"5205f8665b6d276dc7eff771ca88f4a9eec8e898","unresolved":false,"context_lines":[{"line_number":312,"context_line":"**Shared VLAN Implementation:**"},{"line_number":313,"context_line":""},{"line_number":314,"context_line":"For Shared VLAN, L2GW is not required. This is the most simplest cross pod"},{"line_number":315,"context_line":"L2 networking for limited scenario. For example, with a small number of"},{"line_number":316,"context_line":"networks, all VLANs are extended through physical gateway to support cross"},{"line_number":317,"context_line":"site VLAN networking, or all pods under same core switch with same visible"},{"line_number":318,"context_line":"VLAN ranges that supported by the core switch."},{"line_number":319,"context_line":""},{"line_number":320,"context_line":"when a user creates network called Net1, the Tricircle plugin checks the"},{"line_number":321,"context_line":"configuration, if ``tenant_network_type`` equals ``shared_vlan``, the"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_fa5bae2c","line":318,"range":{"start_line":315,"start_character":36,"end_line":318,"end_character":45},"in_reply_to":"7aa08908_98039ab8","updated":"2016-06-05 05:17:52.000000000","message":"In this sentence， we try to explain why L2GW is not required for Shared VLAN and give a example how the Shared VLAN worked without L2GW.","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"18d402b3593908f29f73aa4f1f1dc46259bc8f2b","unresolved":false,"context_lines":[{"line_number":318,"context_line":"VLAN ranges that supported by the core switch."},{"line_number":319,"context_line":""},{"line_number":320,"context_line":"when a user creates network called Net1, the Tricircle plugin checks the"},{"line_number":321,"context_line":"configuration, if ``tenant_network_type`` equals ``shared_vlan``, the"},{"line_number":322,"context_line":"Tricircle will invoke shared VLAN type driver. Shared VLAN driver will"},{"line_number":323,"context_line":"creates ``segment``, and assign ``network_type`` with VLAN, update"},{"line_number":324,"context_line":"``segment`` and ``network_type`` and ``physical_network`` in DB."}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_d82b6232","line":321,"range":{"start_line":321,"start_character":13,"end_line":321,"end_character":14},"updated":"2016-06-04 13:23:07.000000000","message":".","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"18d402b3593908f29f73aa4f1f1dc46259bc8f2b","unresolved":false,"context_lines":[{"line_number":318,"context_line":"VLAN ranges that supported by the core switch."},{"line_number":319,"context_line":""},{"line_number":320,"context_line":"when a user creates network called Net1, the Tricircle plugin checks the"},{"line_number":321,"context_line":"configuration, if ``tenant_network_type`` equals ``shared_vlan``, the"},{"line_number":322,"context_line":"Tricircle will invoke shared VLAN type driver. Shared VLAN driver will"},{"line_number":323,"context_line":"creates ``segment``, and assign ``network_type`` with VLAN, update"},{"line_number":324,"context_line":"``segment`` and ``network_type`` and ``physical_network`` in DB."}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_b83016a0","line":321,"range":{"start_line":321,"start_character":15,"end_line":321,"end_character":17},"updated":"2016-06-04 13:23:07.000000000","message":"If","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"5205f8665b6d276dc7eff771ca88f4a9eec8e898","unresolved":false,"context_lines":[{"line_number":318,"context_line":"VLAN ranges that supported by the core switch."},{"line_number":319,"context_line":""},{"line_number":320,"context_line":"when a user creates network called Net1, the Tricircle plugin checks the"},{"line_number":321,"context_line":"configuration, if ``tenant_network_type`` equals ``shared_vlan``, the"},{"line_number":322,"context_line":"Tricircle will invoke shared VLAN type driver. Shared VLAN driver will"},{"line_number":323,"context_line":"creates ``segment``, and assign ``network_type`` with VLAN, update"},{"line_number":324,"context_line":"``segment`` and ``network_type`` and ``physical_network`` in DB."}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_9a4b8a59","line":321,"range":{"start_line":321,"start_character":15,"end_line":321,"end_character":17},"in_reply_to":"7aa08908_b83016a0","updated":"2016-06-05 05:17:52.000000000","message":"Done","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"5205f8665b6d276dc7eff771ca88f4a9eec8e898","unresolved":false,"context_lines":[{"line_number":318,"context_line":"VLAN ranges that supported by the core switch."},{"line_number":319,"context_line":""},{"line_number":320,"context_line":"when a user creates network called Net1, the Tricircle plugin checks the"},{"line_number":321,"context_line":"configuration, if ``tenant_network_type`` equals ``shared_vlan``, the"},{"line_number":322,"context_line":"Tricircle will invoke shared VLAN type driver. Shared VLAN driver will"},{"line_number":323,"context_line":"creates ``segment``, and assign ``network_type`` with VLAN, update"},{"line_number":324,"context_line":"``segment`` and ``network_type`` and ``physical_network`` in DB."}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_7a485e5c","line":321,"range":{"start_line":321,"start_character":13,"end_line":321,"end_character":14},"in_reply_to":"7aa08908_d82b6232","updated":"2016-06-05 05:17:52.000000000","message":"Done","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"18d402b3593908f29f73aa4f1f1dc46259bc8f2b","unresolved":false,"context_lines":[{"line_number":320,"context_line":"when a user creates network called Net1, the Tricircle plugin checks the"},{"line_number":321,"context_line":"configuration, if ``tenant_network_type`` equals ``shared_vlan``, the"},{"line_number":322,"context_line":"Tricircle will invoke shared VLAN type driver. Shared VLAN driver will"},{"line_number":323,"context_line":"creates ``segment``, and assign ``network_type`` with VLAN, update"},{"line_number":324,"context_line":"``segment`` and ``network_type`` and ``physical_network`` in DB."},{"line_number":325,"context_line":""},{"line_number":326,"context_line":"A user creates VM1 in AZ1, and connects it to network Net1. If VM will be"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_f82a9e2b","line":323,"range":{"start_line":323,"start_character":0,"end_line":323,"end_character":7},"updated":"2016-06-04 13:23:07.000000000","message":"create","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"5205f8665b6d276dc7eff771ca88f4a9eec8e898","unresolved":false,"context_lines":[{"line_number":320,"context_line":"when a user creates network called Net1, the Tricircle plugin checks the"},{"line_number":321,"context_line":"configuration, if ``tenant_network_type`` equals ``shared_vlan``, the"},{"line_number":322,"context_line":"Tricircle will invoke shared VLAN type driver. Shared VLAN driver will"},{"line_number":323,"context_line":"creates ``segment``, and assign ``network_type`` with VLAN, update"},{"line_number":324,"context_line":"``segment`` and ``network_type`` and ``physical_network`` in DB."},{"line_number":325,"context_line":""},{"line_number":326,"context_line":"A user creates VM1 in AZ1, and connects it to network Net1. If VM will be"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_da7352b3","line":323,"range":{"start_line":323,"start_character":0,"end_line":323,"end_character":7},"in_reply_to":"7aa08908_f82a9e2b","updated":"2016-06-05 05:17:52.000000000","message":"Done","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"18d402b3593908f29f73aa4f1f1dc46259bc8f2b","unresolved":false,"context_lines":[{"line_number":321,"context_line":"configuration, if ``tenant_network_type`` equals ``shared_vlan``, the"},{"line_number":322,"context_line":"Tricircle will invoke shared VLAN type driver. Shared VLAN driver will"},{"line_number":323,"context_line":"creates ``segment``, and assign ``network_type`` with VLAN, update"},{"line_number":324,"context_line":"``segment`` and ``network_type`` and ``physical_network`` in DB."},{"line_number":325,"context_line":""},{"line_number":326,"context_line":"A user creates VM1 in AZ1, and connects it to network Net1. If VM will be"},{"line_number":327,"context_line":"booted in ``POD1``, ``Nova API-GW`` needs to get the network information and"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_381d4610","line":324,"range":{"start_line":324,"start_character":61,"end_line":324,"end_character":63},"updated":"2016-06-04 13:23:07.000000000","message":"In this spec file, there is this word, DB.\nDoes it mean database, or one of the Tricircle component?","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"5205f8665b6d276dc7eff771ca88f4a9eec8e898","unresolved":false,"context_lines":[{"line_number":321,"context_line":"configuration, if ``tenant_network_type`` equals ``shared_vlan``, the"},{"line_number":322,"context_line":"Tricircle will invoke shared VLAN type driver. Shared VLAN driver will"},{"line_number":323,"context_line":"creates ``segment``, and assign ``network_type`` with VLAN, update"},{"line_number":324,"context_line":"``segment`` and ``network_type`` and ``physical_network`` in DB."},{"line_number":325,"context_line":""},{"line_number":326,"context_line":"A user creates VM1 in AZ1, and connects it to network Net1. If VM will be"},{"line_number":327,"context_line":"booted in ``POD1``, ``Nova API-GW`` needs to get the network information and"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_5a6802bb","line":324,"range":{"start_line":324,"start_character":61,"end_line":324,"end_character":63},"in_reply_to":"7aa08908_381d4610","updated":"2016-06-05 05:17:52.000000000","message":"one of the Tricircle component.\nIn this spec， the abbreviations of database has not been used","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"47d38eb728aec0edc724b924236e07083fe43a64","unresolved":false,"context_lines":[{"line_number":321,"context_line":"configuration, if ``tenant_network_type`` equals ``shared_vlan``, the"},{"line_number":322,"context_line":"Tricircle will invoke shared VLAN type driver. Shared VLAN driver will"},{"line_number":323,"context_line":"creates ``segment``, and assign ``network_type`` with VLAN, update"},{"line_number":324,"context_line":"``segment`` and ``network_type`` and ``physical_network`` in DB."},{"line_number":325,"context_line":""},{"line_number":326,"context_line":"A user creates VM1 in AZ1, and connects it to network Net1. If VM will be"},{"line_number":327,"context_line":"booted in ``POD1``, ``Nova API-GW`` needs to get the network information and"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_5cd8ffef","line":324,"range":{"start_line":324,"start_character":61,"end_line":324,"end_character":63},"in_reply_to":"7aa08908_5a6802bb","updated":"2016-06-05 08:31:26.000000000","message":"This is not about database but one of our components. In this case, describing \"in DB\" does not make sense, does it?\n\n\"DB\" is not database. \"In DB\", what are you pointing to?\n\nIf subject of this sentence should be \"Shared VLAN driver\", it may be more better to describe \"with DB\" not \"in DB\".\n\nWhat do you think?","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"47960ce28ea0ef1aa278e48ea6bb614686f3be3c","unresolved":false,"context_lines":[{"line_number":321,"context_line":"configuration, if ``tenant_network_type`` equals ``shared_vlan``, the"},{"line_number":322,"context_line":"Tricircle will invoke shared VLAN type driver. Shared VLAN driver will"},{"line_number":323,"context_line":"creates ``segment``, and assign ``network_type`` with VLAN, update"},{"line_number":324,"context_line":"``segment`` and ``network_type`` and ``physical_network`` in DB."},{"line_number":325,"context_line":""},{"line_number":326,"context_line":"A user creates VM1 in AZ1, and connects it to network Net1. If VM will be"},{"line_number":327,"context_line":"booted in ``POD1``, ``Nova API-GW`` needs to get the network information and"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_51f620d8","line":324,"range":{"start_line":324,"start_character":61,"end_line":324,"end_character":63},"in_reply_to":"7aa08908_5cd8ffef","updated":"2016-06-06 01:56:32.000000000","message":"yes, your suggestion is very good.","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"77f79dac14b2b5c0e5c5964275206388d6ddbd2c","unresolved":false,"context_lines":[{"line_number":323,"context_line":"creates ``segment``, and assign ``network_type`` with VLAN, update"},{"line_number":324,"context_line":"``segment`` and ``network_type`` and ``physical_network`` in DB."},{"line_number":325,"context_line":""},{"line_number":326,"context_line":"A user creates VM1 in AZ1, and connects it to network Net1. If VM will be"},{"line_number":327,"context_line":"booted in ``POD1``, ``Nova API-GW`` needs to get the network information and"},{"line_number":328,"context_line":"send create network message to ``POD1``. Create network message includes"},{"line_number":329,"context_line":"``network_type`` and ``segment`` and ``physical_network``."}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_dae87219","line":326,"range":{"start_line":326,"start_character":63,"end_line":326,"end_character":65},"updated":"2016-06-05 03:45:15.000000000","message":"VM1","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"5205f8665b6d276dc7eff771ca88f4a9eec8e898","unresolved":false,"context_lines":[{"line_number":323,"context_line":"creates ``segment``, and assign ``network_type`` with VLAN, update"},{"line_number":324,"context_line":"``segment`` and ``network_type`` and ``physical_network`` in DB."},{"line_number":325,"context_line":""},{"line_number":326,"context_line":"A user creates VM1 in AZ1, and connects it to network Net1. If VM will be"},{"line_number":327,"context_line":"booted in ``POD1``, ``Nova API-GW`` needs to get the network information and"},{"line_number":328,"context_line":"send create network message to ``POD1``. Create network message includes"},{"line_number":329,"context_line":"``network_type`` and ``segment`` and ``physical_network``."}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_fa9d6e5a","line":326,"range":{"start_line":326,"start_character":63,"end_line":326,"end_character":65},"in_reply_to":"7aa08908_dae87219","updated":"2016-06-05 05:17:52.000000000","message":"Done","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"77f79dac14b2b5c0e5c5964275206388d6ddbd2c","unresolved":false,"context_lines":[{"line_number":325,"context_line":""},{"line_number":326,"context_line":"A user creates VM1 in AZ1, and connects it to network Net1. If VM will be"},{"line_number":327,"context_line":"booted in ``POD1``, ``Nova API-GW`` needs to get the network information and"},{"line_number":328,"context_line":"send create network message to ``POD1``. Create network message includes"},{"line_number":329,"context_line":"``network_type`` and ``segment`` and ``physical_network``."},{"line_number":330,"context_line":""},{"line_number":331,"context_line":"Then the user creates VM2 in AZ2, and connects it to network Net1. If VM will"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_1af31a0c","line":328,"range":{"start_line":328,"start_character":5,"end_line":328,"end_character":63},"updated":"2016-06-05 03:45:15.000000000","message":"\"network creation message\" is a bit better.\nBut it\u0027s really up to you.","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"5205f8665b6d276dc7eff771ca88f4a9eec8e898","unresolved":false,"context_lines":[{"line_number":325,"context_line":""},{"line_number":326,"context_line":"A user creates VM1 in AZ1, and connects it to network Net1. If VM will be"},{"line_number":327,"context_line":"booted in ``POD1``, ``Nova API-GW`` needs to get the network information and"},{"line_number":328,"context_line":"send create network message to ``POD1``. Create network message includes"},{"line_number":329,"context_line":"``network_type`` and ``segment`` and ``physical_network``."},{"line_number":330,"context_line":""},{"line_number":331,"context_line":"Then the user creates VM2 in AZ2, and connects it to network Net1. If VM will"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_5aa3e29e","line":328,"range":{"start_line":328,"start_character":5,"end_line":328,"end_character":63},"in_reply_to":"7aa08908_1af31a0c","updated":"2016-06-05 05:17:52.000000000","message":"Done","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"18d402b3593908f29f73aa4f1f1dc46259bc8f2b","unresolved":false,"context_lines":[{"line_number":333,"context_line":"send create network message to ``POD2``. Create network message includes"},{"line_number":334,"context_line":"``network_type`` and ``segment`` and ``physical_network``."},{"line_number":335,"context_line":""},{"line_number":336,"context_line":"**Shared VxLAN Implementation:**"},{"line_number":337,"context_line":""},{"line_number":338,"context_line":"A user creates network Net1, Tricircle plugin checks the configuration, if"},{"line_number":339,"context_line":"``tenant_network_type`` equals “shared_vxlan”, it will invoke shared VxLAN"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_d8cfe2b1","line":336,"range":{"start_line":336,"start_character":2,"end_line":336,"end_character":30},"updated":"2016-06-04 13:23:07.000000000","message":"Delete: \":\"","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"5205f8665b6d276dc7eff771ca88f4a9eec8e898","unresolved":false,"context_lines":[{"line_number":333,"context_line":"send create network message to ``POD2``. Create network message includes"},{"line_number":334,"context_line":"``network_type`` and ``segment`` and ``physical_network``."},{"line_number":335,"context_line":""},{"line_number":336,"context_line":"**Shared VxLAN Implementation:**"},{"line_number":337,"context_line":""},{"line_number":338,"context_line":"A user creates network Net1, Tricircle plugin checks the configuration, if"},{"line_number":339,"context_line":"``tenant_network_type`` equals “shared_vxlan”, it will invoke shared VxLAN"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_1aa5da03","line":336,"range":{"start_line":336,"start_character":2,"end_line":336,"end_character":30},"in_reply_to":"7aa08908_d8cfe2b1","updated":"2016-06-05 05:17:52.000000000","message":"Done","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"77f79dac14b2b5c0e5c5964275206388d6ddbd2c","unresolved":false,"context_lines":[{"line_number":335,"context_line":""},{"line_number":336,"context_line":"**Shared VxLAN Implementation:**"},{"line_number":337,"context_line":""},{"line_number":338,"context_line":"A user creates network Net1, Tricircle plugin checks the configuration, if"},{"line_number":339,"context_line":"``tenant_network_type`` equals “shared_vxlan”, it will invoke shared VxLAN"},{"line_number":340,"context_line":"driver. Shared VxLAN driver will allocate ``segment``, and assign"},{"line_number":341,"context_line":"``network_type`` with VxLAN, and update network with ``segment`` and"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_3ac1b681","line":338,"range":{"start_line":338,"start_character":29,"end_line":338,"end_character":38},"updated":"2016-06-05 03:45:15.000000000","message":"the Tricircle","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"5205f8665b6d276dc7eff771ca88f4a9eec8e898","unresolved":false,"context_lines":[{"line_number":335,"context_line":""},{"line_number":336,"context_line":"**Shared VxLAN Implementation:**"},{"line_number":337,"context_line":""},{"line_number":338,"context_line":"A user creates network Net1, Tricircle plugin checks the configuration, if"},{"line_number":339,"context_line":"``tenant_network_type`` equals “shared_vxlan”, it will invoke shared VxLAN"},{"line_number":340,"context_line":"driver. Shared VxLAN driver will allocate ``segment``, and assign"},{"line_number":341,"context_line":"``network_type`` with VxLAN, and update network with ``segment`` and"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_3aa09690","line":338,"range":{"start_line":338,"start_character":29,"end_line":338,"end_character":38},"in_reply_to":"7aa08908_3ac1b681","updated":"2016-06-05 05:17:52.000000000","message":"Done","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"77f79dac14b2b5c0e5c5964275206388d6ddbd2c","unresolved":false,"context_lines":[{"line_number":336,"context_line":"**Shared VxLAN Implementation:**"},{"line_number":337,"context_line":""},{"line_number":338,"context_line":"A user creates network Net1, Tricircle plugin checks the configuration, if"},{"line_number":339,"context_line":"``tenant_network_type`` equals “shared_vxlan”, it will invoke shared VxLAN"},{"line_number":340,"context_line":"driver. Shared VxLAN driver will allocate ``segment``, and assign"},{"line_number":341,"context_line":"``network_type`` with VxLAN, and update network with ``segment`` and"},{"line_number":342,"context_line":"``network_type`` to DB."}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_faf72ef3","line":339,"range":{"start_line":339,"start_character":31,"end_line":339,"end_character":45},"updated":"2016-06-05 03:45:15.000000000","message":"``shared_vxlan``","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"5205f8665b6d276dc7eff771ca88f4a9eec8e898","unresolved":false,"context_lines":[{"line_number":336,"context_line":"**Shared VxLAN Implementation:**"},{"line_number":337,"context_line":""},{"line_number":338,"context_line":"A user creates network Net1, Tricircle plugin checks the configuration, if"},{"line_number":339,"context_line":"``tenant_network_type`` equals “shared_vxlan”, it will invoke shared VxLAN"},{"line_number":340,"context_line":"driver. Shared VxLAN driver will allocate ``segment``, and assign"},{"line_number":341,"context_line":"``network_type`` with VxLAN, and update network with ``segment`` and"},{"line_number":342,"context_line":"``network_type`` to DB."}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_9aad4a8b","line":339,"range":{"start_line":339,"start_character":31,"end_line":339,"end_character":45},"in_reply_to":"7aa08908_faf72ef3","updated":"2016-06-05 05:17:52.000000000","message":"Done","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"77f79dac14b2b5c0e5c5964275206388d6ddbd2c","unresolved":false,"context_lines":[{"line_number":339,"context_line":"``tenant_network_type`` equals “shared_vxlan”, it will invoke shared VxLAN"},{"line_number":340,"context_line":"driver. Shared VxLAN driver will allocate ``segment``, and assign"},{"line_number":341,"context_line":"``network_type`` with VxLAN, and update network with ``segment`` and"},{"line_number":342,"context_line":"``network_type`` to DB."},{"line_number":343,"context_line":""},{"line_number":344,"context_line":"A user creates VM1 in AZ1, and connects it to network Net1. If VM will be"},{"line_number":345,"context_line":"booted in ``POD1``, ``Nova API-GW`` needs to get the network information and send"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_5adda26f","line":342,"range":{"start_line":342,"start_character":20,"end_line":342,"end_character":22},"updated":"2016-06-05 03:45:15.000000000","message":"Let me tell you again. This description is ambiguous. We need to describe more clearly.\n\nWhich is this word being intended to describe one the Tricircle components or database?","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"77f79dac14b2b5c0e5c5964275206388d6ddbd2c","unresolved":false,"context_lines":[{"line_number":341,"context_line":"``network_type`` with VxLAN, and update network with ``segment`` and"},{"line_number":342,"context_line":"``network_type`` to DB."},{"line_number":343,"context_line":""},{"line_number":344,"context_line":"A user creates VM1 in AZ1, and connects it to network Net1. If VM will be"},{"line_number":345,"context_line":"booted in ``POD1``, ``Nova API-GW`` needs to get the network information and send"},{"line_number":346,"context_line":"create network message to ``POD1``, create network message includes"},{"line_number":347,"context_line":"``network_type`` and ``segment``."}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_3ada5679","line":344,"range":{"start_line":344,"start_character":63,"end_line":344,"end_character":65},"updated":"2016-06-05 03:45:15.000000000","message":"VM1","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"5205f8665b6d276dc7eff771ca88f4a9eec8e898","unresolved":false,"context_lines":[{"line_number":341,"context_line":"``network_type`` with VxLAN, and update network with ``segment`` and"},{"line_number":342,"context_line":"``network_type`` to DB."},{"line_number":343,"context_line":""},{"line_number":344,"context_line":"A user creates VM1 in AZ1, and connects it to network Net1. If VM will be"},{"line_number":345,"context_line":"booted in ``POD1``, ``Nova API-GW`` needs to get the network information and send"},{"line_number":346,"context_line":"create network message to ``POD1``, create network message includes"},{"line_number":347,"context_line":"``network_type`` and ``segment``."}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_fab44ed2","line":344,"range":{"start_line":344,"start_character":63,"end_line":344,"end_character":65},"in_reply_to":"7aa08908_3ada5679","updated":"2016-06-05 05:17:52.000000000","message":"Done","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"77f79dac14b2b5c0e5c5964275206388d6ddbd2c","unresolved":false,"context_lines":[{"line_number":346,"context_line":"create network message to ``POD1``, create network message includes"},{"line_number":347,"context_line":"``network_type`` and ``segment``."},{"line_number":348,"context_line":""},{"line_number":349,"context_line":"``Nova API-GW`` should update Net1 in Tricircle with the segment information"},{"line_number":350,"context_line":"got from ``POD1``."},{"line_number":351,"context_line":""},{"line_number":352,"context_line":"Then the user creates VM2 in AZ2, and connects it to network Net1. If VM will"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_9ae70a40","line":349,"range":{"start_line":349,"start_character":38,"end_line":349,"end_character":47},"updated":"2016-06-05 03:45:15.000000000","message":"top OpenStack instance","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"5205f8665b6d276dc7eff771ca88f4a9eec8e898","unresolved":false,"context_lines":[{"line_number":346,"context_line":"create network message to ``POD1``, create network message includes"},{"line_number":347,"context_line":"``network_type`` and ``segment``."},{"line_number":348,"context_line":""},{"line_number":349,"context_line":"``Nova API-GW`` should update Net1 in Tricircle with the segment information"},{"line_number":350,"context_line":"got from ``POD1``."},{"line_number":351,"context_line":""},{"line_number":352,"context_line":"Then the user creates VM2 in AZ2, and connects it to network Net1. If VM will"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_faebaeae","line":349,"range":{"start_line":349,"start_character":38,"end_line":349,"end_character":47},"in_reply_to":"7aa08908_9ae70a40","updated":"2016-06-05 05:17:52.000000000","message":"Nova API-GW should update Net in the Tricircle, even the Tricircle is in the top OpenStack instance. I think it is better to use \"the Tricircle\".\n\nwhat do you think?","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"77f79dac14b2b5c0e5c5964275206388d6ddbd2c","unresolved":false,"context_lines":[{"line_number":347,"context_line":"``network_type`` and ``segment``."},{"line_number":348,"context_line":""},{"line_number":349,"context_line":"``Nova API-GW`` should update Net1 in Tricircle with the segment information"},{"line_number":350,"context_line":"got from ``POD1``."},{"line_number":351,"context_line":""},{"line_number":352,"context_line":"Then the user creates VM2 in AZ2, and connects it to network Net1. If VM will"},{"line_number":353,"context_line":"be booted in ``POD2``,  ``Nova API-GW`` needs to get the network information and"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_7ae4de3a","line":350,"range":{"start_line":350,"start_character":0,"end_line":350,"end_character":8},"updated":"2016-06-05 03:45:15.000000000","message":"given by","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"5205f8665b6d276dc7eff771ca88f4a9eec8e898","unresolved":false,"context_lines":[{"line_number":347,"context_line":"``network_type`` and ``segment``."},{"line_number":348,"context_line":""},{"line_number":349,"context_line":"``Nova API-GW`` should update Net1 in Tricircle with the segment information"},{"line_number":350,"context_line":"got from ``POD1``."},{"line_number":351,"context_line":""},{"line_number":352,"context_line":"Then the user creates VM2 in AZ2, and connects it to network Net1. If VM will"},{"line_number":353,"context_line":"be booted in ``POD2``,  ``Nova API-GW`` needs to get the network information and"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_5ad122fb","line":350,"range":{"start_line":350,"start_character":0,"end_line":350,"end_character":8},"in_reply_to":"7aa08908_7ae4de3a","updated":"2016-06-05 05:17:52.000000000","message":"Done","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"77f79dac14b2b5c0e5c5964275206388d6ddbd2c","unresolved":false,"context_lines":[{"line_number":349,"context_line":"``Nova API-GW`` should update Net1 in Tricircle with the segment information"},{"line_number":350,"context_line":"got from ``POD1``."},{"line_number":351,"context_line":""},{"line_number":352,"context_line":"Then the user creates VM2 in AZ2, and connects it to network Net1. If VM will"},{"line_number":353,"context_line":"be booted in ``POD2``,  ``Nova API-GW`` needs to get the network information and"},{"line_number":354,"context_line":"send create network message to ``POD2``, create network message includes"},{"line_number":355,"context_line":"``network_type`` and ``segment``."}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_dacfd2b1","line":352,"range":{"start_line":352,"start_character":70,"end_line":352,"end_character":72},"updated":"2016-06-05 03:45:15.000000000","message":"VM1 or VM2, or a new one?","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"5205f8665b6d276dc7eff771ca88f4a9eec8e898","unresolved":false,"context_lines":[{"line_number":349,"context_line":"``Nova API-GW`` should update Net1 in Tricircle with the segment information"},{"line_number":350,"context_line":"got from ``POD1``."},{"line_number":351,"context_line":""},{"line_number":352,"context_line":"Then the user creates VM2 in AZ2, and connects it to network Net1. If VM will"},{"line_number":353,"context_line":"be booted in ``POD2``,  ``Nova API-GW`` needs to get the network information and"},{"line_number":354,"context_line":"send create network message to ``POD2``, create network message includes"},{"line_number":355,"context_line":"``network_type`` and ``segment``."}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_3aced65a","line":352,"range":{"start_line":352,"start_character":70,"end_line":352,"end_character":72},"in_reply_to":"7aa08908_dacfd2b1","updated":"2016-06-05 05:17:52.000000000","message":"VM2","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"77f79dac14b2b5c0e5c5964275206388d6ddbd2c","unresolved":false,"context_lines":[{"line_number":351,"context_line":""},{"line_number":352,"context_line":"Then the user creates VM2 in AZ2, and connects it to network Net1. If VM will"},{"line_number":353,"context_line":"be booted in ``POD2``,  ``Nova API-GW`` needs to get the network information and"},{"line_number":354,"context_line":"send create network message to ``POD2``, create network message includes"},{"line_number":355,"context_line":"``network_type`` and ``segment``."},{"line_number":356,"context_line":""},{"line_number":357,"context_line":"``Nova API-GW`` should update Net1 in Tricircle with the segment information"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_bad48647","line":354,"range":{"start_line":354,"start_character":5,"end_line":354,"end_character":27},"updated":"2016-06-05 03:45:15.000000000","message":"network creation message","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"77f79dac14b2b5c0e5c5964275206388d6ddbd2c","unresolved":false,"context_lines":[{"line_number":351,"context_line":""},{"line_number":352,"context_line":"Then the user creates VM2 in AZ2, and connects it to network Net1. If VM will"},{"line_number":353,"context_line":"be booted in ``POD2``,  ``Nova API-GW`` needs to get the network information and"},{"line_number":354,"context_line":"send create network message to ``POD2``, create network message includes"},{"line_number":355,"context_line":"``network_type`` and ``segment``."},{"line_number":356,"context_line":""},{"line_number":357,"context_line":"``Nova API-GW`` should update Net1 in Tricircle with the segment information"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_1acafaa1","line":354,"range":{"start_line":354,"start_character":41,"end_line":354,"end_character":63},"updated":"2016-06-05 03:45:15.000000000","message":"same as well","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"5205f8665b6d276dc7eff771ca88f4a9eec8e898","unresolved":false,"context_lines":[{"line_number":351,"context_line":""},{"line_number":352,"context_line":"Then the user creates VM2 in AZ2, and connects it to network Net1. If VM will"},{"line_number":353,"context_line":"be booted in ``POD2``,  ``Nova API-GW`` needs to get the network information and"},{"line_number":354,"context_line":"send create network message to ``POD2``, create network message includes"},{"line_number":355,"context_line":"``network_type`` and ``segment``."},{"line_number":356,"context_line":""},{"line_number":357,"context_line":"``Nova API-GW`` should update Net1 in Tricircle with the segment information"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_da035275","line":354,"range":{"start_line":354,"start_character":5,"end_line":354,"end_character":27},"in_reply_to":"7aa08908_bad48647","updated":"2016-06-05 05:17:52.000000000","message":"Done","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"77f79dac14b2b5c0e5c5964275206388d6ddbd2c","unresolved":false,"context_lines":[{"line_number":354,"context_line":"send create network message to ``POD2``, create network message includes"},{"line_number":355,"context_line":"``network_type`` and ``segment``."},{"line_number":356,"context_line":""},{"line_number":357,"context_line":"``Nova API-GW`` should update Net1 in Tricircle with the segment information"},{"line_number":358,"context_line":"get from ``POD2``."},{"line_number":359,"context_line":""},{"line_number":360,"context_line":"The Tricircle plugin detects that the network includes more than one segment"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_face0eb3","line":357,"range":{"start_line":357,"start_character":38,"end_line":357,"end_character":47},"updated":"2016-06-05 03:45:15.000000000","message":"top OpenStack instance","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"5205f8665b6d276dc7eff771ca88f4a9eec8e898","unresolved":false,"context_lines":[{"line_number":354,"context_line":"send create network message to ``POD2``, create network message includes"},{"line_number":355,"context_line":"``network_type`` and ``segment``."},{"line_number":356,"context_line":""},{"line_number":357,"context_line":"``Nova API-GW`` should update Net1 in Tricircle with the segment information"},{"line_number":358,"context_line":"get from ``POD2``."},{"line_number":359,"context_line":""},{"line_number":360,"context_line":"The Tricircle plugin detects that the network includes more than one segment"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_1afe7a6b","line":357,"range":{"start_line":357,"start_character":38,"end_line":357,"end_character":47},"in_reply_to":"7aa08908_face0eb3","updated":"2016-06-05 05:17:52.000000000","message":"Nova API-GW should update Net in the Tricircle, even the Tricircle is in the top OpenStack instance. I think it is better to use \"the Tricircle\".\nwhat do you think?","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"77f79dac14b2b5c0e5c5964275206388d6ddbd2c","unresolved":false,"context_lines":[{"line_number":355,"context_line":"``network_type`` and ``segment``."},{"line_number":356,"context_line":""},{"line_number":357,"context_line":"``Nova API-GW`` should update Net1 in Tricircle with the segment information"},{"line_number":358,"context_line":"get from ``POD2``."},{"line_number":359,"context_line":""},{"line_number":360,"context_line":"The Tricircle plugin detects that the network includes more than one segment"},{"line_number":361,"context_line":"network, calls L2GW driver to start async job for cross pod networking for"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_5ac48291","line":358,"range":{"start_line":358,"start_character":0,"end_line":358,"end_character":8},"updated":"2016-06-05 03:45:15.000000000","message":"given by","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"77f79dac14b2b5c0e5c5964275206388d6ddbd2c","unresolved":false,"context_lines":[{"line_number":360,"context_line":"The Tricircle plugin detects that the network includes more than one segment"},{"line_number":361,"context_line":"network, calls L2GW driver to start async job for cross pod networking for"},{"line_number":362,"context_line":"Net1. The L2GW driver will create L2GW1 in ``POD1`` and L2GW2 in ``POD2``. In"},{"line_number":363,"context_line":"``POD1``, L2GW1 will connect the local Net1 and create L2GW remote connection"},{"line_number":364,"context_line":"to L2GW2, then populate the information of MAC/IP which resides in L2GW1. In"},{"line_number":365,"context_line":"``POD2``, L2GW2 will connect the local Net1 and create L2GW remote connection"},{"line_number":366,"context_line":"to L2GW1, then populate remote MAC/IP information which resides in ``POD1`` in L2GW2."}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_7abb3e0f","line":363,"range":{"start_line":363,"start_character":60,"end_line":363,"end_character":66},"updated":"2016-06-05 03:45:15.000000000","message":"for remote\n\nor just\n\nfor connection to L2GW2","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"77f79dac14b2b5c0e5c5964275206388d6ddbd2c","unresolved":false,"context_lines":[{"line_number":361,"context_line":"network, calls L2GW driver to start async job for cross pod networking for"},{"line_number":362,"context_line":"Net1. The L2GW driver will create L2GW1 in ``POD1`` and L2GW2 in ``POD2``. In"},{"line_number":363,"context_line":"``POD1``, L2GW1 will connect the local Net1 and create L2GW remote connection"},{"line_number":364,"context_line":"to L2GW2, then populate the information of MAC/IP which resides in L2GW1. In"},{"line_number":365,"context_line":"``POD2``, L2GW2 will connect the local Net1 and create L2GW remote connection"},{"line_number":366,"context_line":"to L2GW1, then populate remote MAC/IP information which resides in ``POD1`` in L2GW2."},{"line_number":367,"context_line":""}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_da36b2b3","line":364,"range":{"start_line":364,"start_character":8,"end_line":364,"end_character":9},"updated":"2016-06-05 03:45:15.000000000","message":".","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"77f79dac14b2b5c0e5c5964275206388d6ddbd2c","unresolved":false,"context_lines":[{"line_number":361,"context_line":"network, calls L2GW driver to start async job for cross pod networking for"},{"line_number":362,"context_line":"Net1. The L2GW driver will create L2GW1 in ``POD1`` and L2GW2 in ``POD2``. In"},{"line_number":363,"context_line":"``POD1``, L2GW1 will connect the local Net1 and create L2GW remote connection"},{"line_number":364,"context_line":"to L2GW2, then populate the information of MAC/IP which resides in L2GW1. In"},{"line_number":365,"context_line":"``POD2``, L2GW2 will connect the local Net1 and create L2GW remote connection"},{"line_number":366,"context_line":"to L2GW1, then populate remote MAC/IP information which resides in ``POD1`` in L2GW2."},{"line_number":367,"context_line":""}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_ba3be69b","line":364,"range":{"start_line":364,"start_character":10,"end_line":364,"end_character":14},"updated":"2016-06-05 03:45:15.000000000","message":"Then L2GW1 will","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"77f79dac14b2b5c0e5c5964275206388d6ddbd2c","unresolved":false,"context_lines":[{"line_number":361,"context_line":"network, calls L2GW driver to start async job for cross pod networking for"},{"line_number":362,"context_line":"Net1. The L2GW driver will create L2GW1 in ``POD1`` and L2GW2 in ``POD2``. In"},{"line_number":363,"context_line":"``POD1``, L2GW1 will connect the local Net1 and create L2GW remote connection"},{"line_number":364,"context_line":"to L2GW2, then populate the information of MAC/IP which resides in L2GW1. In"},{"line_number":365,"context_line":"``POD2``, L2GW2 will connect the local Net1 and create L2GW remote connection"},{"line_number":366,"context_line":"to L2GW1, then populate remote MAC/IP information which resides in ``POD1`` in L2GW2."},{"line_number":367,"context_line":""}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_5a4be22b","line":364,"range":{"start_line":364,"start_character":43,"end_line":364,"end_character":49},"updated":"2016-06-05 03:45:15.000000000","message":"Whose mac/ip?","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"77f79dac14b2b5c0e5c5964275206388d6ddbd2c","unresolved":false,"context_lines":[{"line_number":362,"context_line":"Net1. The L2GW driver will create L2GW1 in ``POD1`` and L2GW2 in ``POD2``. In"},{"line_number":363,"context_line":"``POD1``, L2GW1 will connect the local Net1 and create L2GW remote connection"},{"line_number":364,"context_line":"to L2GW2, then populate the information of MAC/IP which resides in L2GW1. In"},{"line_number":365,"context_line":"``POD2``, L2GW2 will connect the local Net1 and create L2GW remote connection"},{"line_number":366,"context_line":"to L2GW1, then populate remote MAC/IP information which resides in ``POD1`` in L2GW2."},{"line_number":367,"context_line":""},{"line_number":368,"context_line":"L2GW driver in Tricircle will also detect the new port creation/deletion api"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_1a415a0c","line":365,"range":{"start_line":365,"start_character":60,"end_line":365,"end_character":66},"updated":"2016-06-05 03:45:15.000000000","message":"for remote\n\nor just\n\nfor connection to L2GW1","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"77f79dac14b2b5c0e5c5964275206388d6ddbd2c","unresolved":false,"context_lines":[{"line_number":363,"context_line":"``POD1``, L2GW1 will connect the local Net1 and create L2GW remote connection"},{"line_number":364,"context_line":"to L2GW2, then populate the information of MAC/IP which resides in L2GW1. In"},{"line_number":365,"context_line":"``POD2``, L2GW2 will connect the local Net1 and create L2GW remote connection"},{"line_number":366,"context_line":"to L2GW1, then populate remote MAC/IP information which resides in ``POD1`` in L2GW2."},{"line_number":367,"context_line":""},{"line_number":368,"context_line":"L2GW driver in Tricircle will also detect the new port creation/deletion api"},{"line_number":369,"context_line":"calling, if port (MAC/IP) created or deleted in ``POD1``, then needs to refresh"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_fa456e17","line":366,"range":{"start_line":366,"start_character":8,"end_line":366,"end_character":14},"updated":"2016-06-05 03:45:15.000000000","message":". Then L2GW2 will","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"77f79dac14b2b5c0e5c5964275206388d6ddbd2c","unresolved":false,"context_lines":[{"line_number":365,"context_line":"``POD2``, L2GW2 will connect the local Net1 and create L2GW remote connection"},{"line_number":366,"context_line":"to L2GW1, then populate remote MAC/IP information which resides in ``POD1`` in L2GW2."},{"line_number":367,"context_line":""},{"line_number":368,"context_line":"L2GW driver in Tricircle will also detect the new port creation/deletion api"},{"line_number":369,"context_line":"calling, if port (MAC/IP) created or deleted in ``POD1``, then needs to refresh"},{"line_number":370,"context_line":"the L2GW2 MAC/IP information. If port (MAC/IP) created or deleted in ``POD2``,"},{"line_number":371,"context_line":"then needs to refresh the L2GW1 MAC/IP information."}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_3a48962d","line":368,"range":{"start_line":368,"start_character":15,"end_line":368,"end_character":24},"updated":"2016-06-05 03:45:15.000000000","message":"the Tricircle","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"5205f8665b6d276dc7eff771ca88f4a9eec8e898","unresolved":false,"context_lines":[{"line_number":365,"context_line":"``POD2``, L2GW2 will connect the local Net1 and create L2GW remote connection"},{"line_number":366,"context_line":"to L2GW1, then populate remote MAC/IP information which resides in ``POD1`` in L2GW2."},{"line_number":367,"context_line":""},{"line_number":368,"context_line":"L2GW driver in Tricircle will also detect the new port creation/deletion api"},{"line_number":369,"context_line":"calling, if port (MAC/IP) created or deleted in ``POD1``, then needs to refresh"},{"line_number":370,"context_line":"the L2GW2 MAC/IP information. If port (MAC/IP) created or deleted in ``POD2``,"},{"line_number":371,"context_line":"then needs to refresh the L2GW1 MAC/IP information."}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_9af26a99","line":368,"range":{"start_line":368,"start_character":15,"end_line":368,"end_character":24},"in_reply_to":"7aa08908_3a48962d","updated":"2016-06-05 05:17:52.000000000","message":"Done","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"77f79dac14b2b5c0e5c5964275206388d6ddbd2c","unresolved":false,"context_lines":[{"line_number":366,"context_line":"to L2GW1, then populate remote MAC/IP information which resides in ``POD1`` in L2GW2."},{"line_number":367,"context_line":""},{"line_number":368,"context_line":"L2GW driver in Tricircle will also detect the new port creation/deletion api"},{"line_number":369,"context_line":"calling, if port (MAC/IP) created or deleted in ``POD1``, then needs to refresh"},{"line_number":370,"context_line":"the L2GW2 MAC/IP information. If port (MAC/IP) created or deleted in ``POD2``,"},{"line_number":371,"context_line":"then needs to refresh the L2GW1 MAC/IP information."},{"line_number":372,"context_line":""}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_da5d12ee","line":369,"range":{"start_line":369,"start_character":7,"end_line":369,"end_character":8},"updated":"2016-06-05 03:45:15.000000000","message":".","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"77f79dac14b2b5c0e5c5964275206388d6ddbd2c","unresolved":false,"context_lines":[{"line_number":366,"context_line":"to L2GW1, then populate remote MAC/IP information which resides in ``POD1`` in L2GW2."},{"line_number":367,"context_line":""},{"line_number":368,"context_line":"L2GW driver in Tricircle will also detect the new port creation/deletion api"},{"line_number":369,"context_line":"calling, if port (MAC/IP) created or deleted in ``POD1``, then needs to refresh"},{"line_number":370,"context_line":"the L2GW2 MAC/IP information. If port (MAC/IP) created or deleted in ``POD2``,"},{"line_number":371,"context_line":"then needs to refresh the L2GW1 MAC/IP information."},{"line_number":372,"context_line":""}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_1a583afa","line":369,"range":{"start_line":369,"start_character":9,"end_line":369,"end_character":11},"updated":"2016-06-05 03:45:15.000000000","message":"If","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"77f79dac14b2b5c0e5c5964275206388d6ddbd2c","unresolved":false,"context_lines":[{"line_number":366,"context_line":"to L2GW1, then populate remote MAC/IP information which resides in ``POD1`` in L2GW2."},{"line_number":367,"context_line":""},{"line_number":368,"context_line":"L2GW driver in Tricircle will also detect the new port creation/deletion api"},{"line_number":369,"context_line":"calling, if port (MAC/IP) created or deleted in ``POD1``, then needs to refresh"},{"line_number":370,"context_line":"the L2GW2 MAC/IP information. If port (MAC/IP) created or deleted in ``POD2``,"},{"line_number":371,"context_line":"then needs to refresh the L2GW1 MAC/IP information."},{"line_number":372,"context_line":""}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_9a554ac8","line":369,"range":{"start_line":369,"start_character":0,"end_line":369,"end_character":7},"updated":"2016-06-05 03:45:15.000000000","message":"request","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"5205f8665b6d276dc7eff771ca88f4a9eec8e898","unresolved":false,"context_lines":[{"line_number":366,"context_line":"to L2GW1, then populate remote MAC/IP information which resides in ``POD1`` in L2GW2."},{"line_number":367,"context_line":""},{"line_number":368,"context_line":"L2GW driver in Tricircle will also detect the new port creation/deletion api"},{"line_number":369,"context_line":"calling, if port (MAC/IP) created or deleted in ``POD1``, then needs to refresh"},{"line_number":370,"context_line":"the L2GW2 MAC/IP information. If port (MAC/IP) created or deleted in ``POD2``,"},{"line_number":371,"context_line":"then needs to refresh the L2GW1 MAC/IP information."},{"line_number":372,"context_line":""}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_5a3f6225","line":369,"range":{"start_line":369,"start_character":0,"end_line":369,"end_character":7},"in_reply_to":"7aa08908_9a554ac8","updated":"2016-06-05 05:17:52.000000000","message":"Done","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"77f79dac14b2b5c0e5c5964275206388d6ddbd2c","unresolved":false,"context_lines":[{"line_number":366,"context_line":"to L2GW1, then populate remote MAC/IP information which resides in ``POD1`` in L2GW2."},{"line_number":367,"context_line":""},{"line_number":368,"context_line":"L2GW driver in Tricircle will also detect the new port creation/deletion api"},{"line_number":369,"context_line":"calling, if port (MAC/IP) created or deleted in ``POD1``, then needs to refresh"},{"line_number":370,"context_line":"the L2GW2 MAC/IP information. If port (MAC/IP) created or deleted in ``POD2``,"},{"line_number":371,"context_line":"then needs to refresh the L2GW1 MAC/IP information."},{"line_number":372,"context_line":""},{"line_number":373,"context_line":"Whether to populate MAC/IP information should be configurable according to"},{"line_number":374,"context_line":"L2GW capability. And only populate MAC/IP information for the ports that are"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_5a72c27d","line":371,"range":{"start_line":369,"start_character":9,"end_line":371,"end_character":51},"updated":"2016-06-05 03:45:15.000000000","message":"Please reconsider this sentence and rewrite up.","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"5205f8665b6d276dc7eff771ca88f4a9eec8e898","unresolved":false,"context_lines":[{"line_number":366,"context_line":"to L2GW1, then populate remote MAC/IP information which resides in ``POD1`` in L2GW2."},{"line_number":367,"context_line":""},{"line_number":368,"context_line":"L2GW driver in Tricircle will also detect the new port creation/deletion api"},{"line_number":369,"context_line":"calling, if port (MAC/IP) created or deleted in ``POD1``, then needs to refresh"},{"line_number":370,"context_line":"the L2GW2 MAC/IP information. If port (MAC/IP) created or deleted in ``POD2``,"},{"line_number":371,"context_line":"then needs to refresh the L2GW1 MAC/IP information."},{"line_number":372,"context_line":""},{"line_number":373,"context_line":"Whether to populate MAC/IP information should be configurable according to"},{"line_number":374,"context_line":"L2GW capability. And only populate MAC/IP information for the ports that are"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_3a3c162f","line":371,"range":{"start_line":369,"start_character":9,"end_line":371,"end_character":51},"in_reply_to":"7aa08908_5a72c27d","updated":"2016-06-05 05:17:52.000000000","message":"should we change this sentence like this:\n\nif port (MAC/IP) created or deleted in ``POD1`` or ``POD2``, then it needs to refresh the L2GW1 MAC/IP information.","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"77f79dac14b2b5c0e5c5964275206388d6ddbd2c","unresolved":false,"context_lines":[{"line_number":370,"context_line":"the L2GW2 MAC/IP information. If port (MAC/IP) created or deleted in ``POD2``,"},{"line_number":371,"context_line":"then needs to refresh the L2GW1 MAC/IP information."},{"line_number":372,"context_line":""},{"line_number":373,"context_line":"Whether to populate MAC/IP information should be configurable according to"},{"line_number":374,"context_line":"L2GW capability. And only populate MAC/IP information for the ports that are"},{"line_number":375,"context_line":"not resides in the same pod."},{"line_number":376,"context_line":""}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_7a697e8b","line":373,"range":{"start_line":373,"start_character":20,"end_line":373,"end_character":26},"updated":"2016-06-05 03:45:15.000000000","message":"Please describe those kind of words more clearly.","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"5205f8665b6d276dc7eff771ca88f4a9eec8e898","unresolved":false,"context_lines":[{"line_number":370,"context_line":"the L2GW2 MAC/IP information. If port (MAC/IP) created or deleted in ``POD2``,"},{"line_number":371,"context_line":"then needs to refresh the L2GW1 MAC/IP information."},{"line_number":372,"context_line":""},{"line_number":373,"context_line":"Whether to populate MAC/IP information should be configurable according to"},{"line_number":374,"context_line":"L2GW capability. And only populate MAC/IP information for the ports that are"},{"line_number":375,"context_line":"not resides in the same pod."},{"line_number":376,"context_line":""}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_fa10ceaa","line":373,"range":{"start_line":373,"start_character":20,"end_line":373,"end_character":26},"in_reply_to":"7aa08908_7a697e8b","updated":"2016-06-05 05:17:52.000000000","message":"we describe this sentence like this:\n\nWhether to populate the information of port(MAC/IP)...\n\nwhat do you think?","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"18d402b3593908f29f73aa4f1f1dc46259bc8f2b","unresolved":false,"context_lines":[{"line_number":374,"context_line":"L2GW capability. And only populate MAC/IP information for the ports that are"},{"line_number":375,"context_line":"not resides in the same pod."},{"line_number":376,"context_line":""},{"line_number":377,"context_line":"**Mixed VLAN/VxLAN:**"},{"line_number":378,"context_line":""},{"line_number":379,"context_line":"To achieve cross pod L2 networking, L2GW will be used to connect L2 network in"},{"line_number":380,"context_line":"different pods, using L2GW should work for Shared VxLAN and Mixed VLAN/VxLAN"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_b8d49647","line":377,"range":{"start_line":377,"start_character":2,"end_line":377,"end_character":19},"updated":"2016-06-04 13:23:07.000000000","message":"Delete: \":\"","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"5205f8665b6d276dc7eff771ca88f4a9eec8e898","unresolved":false,"context_lines":[{"line_number":374,"context_line":"L2GW capability. And only populate MAC/IP information for the ports that are"},{"line_number":375,"context_line":"not resides in the same pod."},{"line_number":376,"context_line":""},{"line_number":377,"context_line":"**Mixed VLAN/VxLAN:**"},{"line_number":378,"context_line":""},{"line_number":379,"context_line":"To achieve cross pod L2 networking, L2GW will be used to connect L2 network in"},{"line_number":380,"context_line":"different pods, using L2GW should work for Shared VxLAN and Mixed VLAN/VxLAN"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_ba9f66b3","line":377,"range":{"start_line":377,"start_character":2,"end_line":377,"end_character":19},"in_reply_to":"7aa08908_b8d49647","updated":"2016-06-05 05:17:52.000000000","message":"Done","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"f19459cdb04b7ae2bbd28a7f024988380467d939","unresolved":false,"context_lines":[{"line_number":382,"context_line":""},{"line_number":383,"context_line":"When L2GW connected with local network in the same OpenStack instance, no"},{"line_number":384,"context_line":"matter it\u0027s VLAN or VxLAN or GRE, the L2GW should be able to connect the"},{"line_number":385,"context_line":"local network, and because L2GW is extension of Neutron, so only network"},{"line_number":386,"context_line":"UUID should be enough for L2GW to connect the local network."},{"line_number":387,"context_line":""},{"line_number":388,"context_line":"When admin user creates network in Tricircle, he/she specifies the network"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_66f39d0b","line":385,"range":{"start_line":385,"start_character":57,"end_line":385,"end_character":60},"updated":"2016-06-06 03:40:37.000000000","message":"\"so\" is not needed since you have used \"because\"","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"f19459cdb04b7ae2bbd28a7f024988380467d939","unresolved":false,"context_lines":[{"line_number":415,"context_line":"in Tricircle ``Neutron API Server``."},{"line_number":416,"context_line":""},{"line_number":417,"context_line":"Then the user creates another VM2, and with AZ info AZ2, then the VM should be"},{"line_number":418,"context_line":"able to be booted in bottom ``POD2`` which is located in AZ2, And when VM2 should"},{"line_number":419,"context_line":"be able to be booted in AZ2, ``Nova API-GW`` also creates a network in ``POD2``,"},{"line_number":420,"context_line":"and queries the network information including segment and network type,"},{"line_number":421,"context_line":"updates this new segment to the Net1 in Tricircle ``Neutron API Server``."}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_e655cdc6","line":418,"range":{"start_line":418,"start_character":60,"end_line":418,"end_character":61},"updated":"2016-06-06 03:40:37.000000000","message":"change to \".\"","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":19060,"name":"Shinobu KINJO","email":"shinobu@redhat.com","username":"shinobu"},"change_message_id":"18d402b3593908f29f73aa4f1f1dc46259bc8f2b","unresolved":false,"context_lines":[{"line_number":437,"context_line":"L2GW capability. And only populate MAC/IP information for the ports that are"},{"line_number":438,"context_line":"not resides in the same pod."},{"line_number":439,"context_line":""},{"line_number":440,"context_line":"**L3 bridge network:**"},{"line_number":441,"context_line":""},{"line_number":442,"context_line":"Current implementation without cross pod L2 networking."},{"line_number":443,"context_line":""}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_f8ce1eb3","line":440,"range":{"start_line":440,"start_character":2,"end_line":440,"end_character":20},"updated":"2016-06-04 13:23:07.000000000","message":"Delete: \":\"","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":21023,"name":"Ronghui Cao","email":"CR_hui@126.com","username":"CR_hui"},"change_message_id":"5205f8665b6d276dc7eff771ca88f4a9eec8e898","unresolved":false,"context_lines":[{"line_number":437,"context_line":"L2GW capability. And only populate MAC/IP information for the ports that are"},{"line_number":438,"context_line":"not resides in the same pod."},{"line_number":439,"context_line":""},{"line_number":440,"context_line":"**L3 bridge network:**"},{"line_number":441,"context_line":""},{"line_number":442,"context_line":"Current implementation without cross pod L2 networking."},{"line_number":443,"context_line":""}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_da9a32c5","line":440,"range":{"start_line":440,"start_character":2,"end_line":440,"end_character":20},"in_reply_to":"7aa08908_f8ce1eb3","updated":"2016-06-05 05:17:52.000000000","message":"Done","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"f19459cdb04b7ae2bbd28a7f024988380467d939","unresolved":false,"context_lines":[{"line_number":442,"context_line":"Current implementation without cross pod L2 networking."},{"line_number":443,"context_line":""},{"line_number":444,"context_line":"* A special bridge network is created and connected to the routers in"},{"line_number":445,"context_line":"  different  bottom OpenStack. We configure the extra routes of the routers"},{"line_number":446,"context_line":"  to route the  packets from one OpenStack to another. In current"},{"line_number":447,"context_line":"  implementation, we create this special bridge network in each bottom"},{"line_number":448,"context_line":"  OpenStack with the same ``VLAN ID``, so we have an L2 network to connect"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_4614a1f4","line":445,"range":{"start_line":445,"start_character":20,"end_line":445,"end_character":29},"updated":"2016-06-06 03:40:37.000000000","message":"OpenStack instances","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"f19459cdb04b7ae2bbd28a7f024988380467d939","unresolved":false,"context_lines":[{"line_number":442,"context_line":"Current implementation without cross pod L2 networking."},{"line_number":443,"context_line":""},{"line_number":444,"context_line":"* A special bridge network is created and connected to the routers in"},{"line_number":445,"context_line":"  different  bottom OpenStack. We configure the extra routes of the routers"},{"line_number":446,"context_line":"  to route the  packets from one OpenStack to another. In current"},{"line_number":447,"context_line":"  implementation, we create this special bridge network in each bottom"},{"line_number":448,"context_line":"  OpenStack with the same ``VLAN ID``, so we have an L2 network to connect"}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_660f1de2","line":445,"range":{"start_line":445,"start_character":11,"end_line":445,"end_character":13},"updated":"2016-06-06 03:40:37.000000000","message":"remove one space","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"f19459cdb04b7ae2bbd28a7f024988380467d939","unresolved":false,"context_lines":[{"line_number":443,"context_line":""},{"line_number":444,"context_line":"* A special bridge network is created and connected to the routers in"},{"line_number":445,"context_line":"  different  bottom OpenStack. We configure the extra routes of the routers"},{"line_number":446,"context_line":"  to route the  packets from one OpenStack to another. In current"},{"line_number":447,"context_line":"  implementation, we create this special bridge network in each bottom"},{"line_number":448,"context_line":"  OpenStack with the same ``VLAN ID``, so we have an L2 network to connect"},{"line_number":449,"context_line":"  the routers."}],"source_content_type":"text/x-rst","patch_set":25,"id":"7aa08908_a6f905cb","line":446,"range":{"start_line":446,"start_character":14,"end_line":446,"end_character":16},"updated":"2016-06-06 03:40:37.000000000","message":"remove one space","commit_id":"f993f7f9df629313f666609215d8a302b2b2b2d5"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"26dab48b84ec0a683452fdb19d8eab8f5be45877","unresolved":false,"context_lines":[{"line_number":227,"context_line":"Tricircle plugin needs to support multi-segment network extension.[3]"},{"line_number":228,"context_line":""},{"line_number":229,"context_line":"For Shared VxLAN or Mixed VLAN/VxLAN L2 network type, L2GW driver will utilize the"},{"line_number":230,"context_line":"multi-segment network in Neutron API server to build the L2 network in the Tiricircle."},{"line_number":231,"context_line":"Each network in the bottom OpenStack instance will be a segment for the whole cross"},{"line_number":232,"context_line":"pod L2 networking in the Tricircle."},{"line_number":233,"context_line":""}],"source_content_type":"text/x-rst","patch_set":26,"id":"7aa08908_9b9ffb02","line":230,"range":{"start_line":230,"start_character":0,"end_line":230,"end_character":21},"updated":"2016-06-06 09:17:23.000000000","message":"\"multi-segment network extension\", I think","commit_id":"e67de00ee68a7bb4818388b8ad95fd6eddcc9f3b"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"26dab48b84ec0a683452fdb19d8eab8f5be45877","unresolved":false,"context_lines":[{"line_number":227,"context_line":"Tricircle plugin needs to support multi-segment network extension.[3]"},{"line_number":228,"context_line":""},{"line_number":229,"context_line":"For Shared VxLAN or Mixed VLAN/VxLAN L2 network type, L2GW driver will utilize the"},{"line_number":230,"context_line":"multi-segment network in Neutron API server to build the L2 network in the Tiricircle."},{"line_number":231,"context_line":"Each network in the bottom OpenStack instance will be a segment for the whole cross"},{"line_number":232,"context_line":"pod L2 networking in the Tricircle."},{"line_number":233,"context_line":""}],"source_content_type":"text/x-rst","patch_set":26,"id":"7aa08908_fb90bfee","line":230,"range":{"start_line":230,"start_character":75,"end_line":230,"end_character":85},"updated":"2016-06-06 09:17:23.000000000","message":"s/Tircircle/Tricircle","commit_id":"e67de00ee68a7bb4818388b8ad95fd6eddcc9f3b"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"26dab48b84ec0a683452fdb19d8eab8f5be45877","unresolved":false,"context_lines":[{"line_number":313,"context_line":""},{"line_number":314,"context_line":"For Shared VLAN, L2GW is not required. This is the most simplest cross pod"},{"line_number":315,"context_line":"L2 networking for limited scenario. For example, with a small number of"},{"line_number":316,"context_line":"networks, all VLANs are extended through physical gateway to support cross"},{"line_number":317,"context_line":"site VLAN networking, or all pods under same core switch with same visible"},{"line_number":318,"context_line":"VLAN ranges that supported by the core switch."},{"line_number":319,"context_line":""},{"line_number":320,"context_line":"when a user creates network called ``Net1``, the Tricircle plugin checks the"},{"line_number":321,"context_line":"configuration. If ``tenant_network_type`` equals ``shared_vlan``, the"}],"source_content_type":"text/x-rst","patch_set":26,"id":"7aa08908_664d5272","line":318,"range":{"start_line":316,"start_character":10,"end_line":318,"end_character":45},"updated":"2016-06-06 09:17:23.000000000","message":"if we remove the modifiers from this sentence, it will become \"all VLANs are extended, or all pods\", there is no predicate in the second part.","commit_id":"e67de00ee68a7bb4818388b8ad95fd6eddcc9f3b"},{"author":{"_account_id":12076,"name":"Zhiyuan Cai","email":"luckyvega.g@gmail.com","username":"zhiyuan_cai"},"change_message_id":"26dab48b84ec0a683452fdb19d8eab8f5be45877","unresolved":false,"context_lines":[{"line_number":381,"context_line":""},{"line_number":382,"context_line":"When L2GW connected with local network in the same OpenStack instance, no"},{"line_number":383,"context_line":"matter it\u0027s VLAN or VxLAN or GRE, the L2GW should be able to connect the"},{"line_number":384,"context_line":"local network, and because L2GW is extension of Neutron, because only network"},{"line_number":385,"context_line":"UUID should be enough for L2GW to connect the local network."},{"line_number":386,"context_line":""},{"line_number":387,"context_line":"When admin user creates network in Tricircle, he/she specifies the network"}],"source_content_type":"text/x-rst","patch_set":26,"id":"7aa08908_86467e21","line":384,"range":{"start_line":384,"start_character":57,"end_line":384,"end_character":64},"updated":"2016-06-06 09:17:23.000000000","message":"well, i meant removing \"so\" in the previous comment, not replacing \"so\" with \"because\", since you have used \"because\" in \"because L2GW is extension of Neutron\". i meant \"have used\" not \"have to use\"","commit_id":"e67de00ee68a7bb4818388b8ad95fd6eddcc9f3b"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"880bb0ea441e5e28e4901ad0a80ed717f48f79fa","unresolved":false,"context_lines":[{"line_number":39,"context_line":"specify the \u0027availability_zone_hints\u0027(AZ or az will be used for short for"},{"line_number":40,"context_line":"availability zone) during network creation[5], in the Tricircle, the"},{"line_number":41,"context_line":"\u0027az_hints\u0027 means which AZ the network should be spreaded into. It\u0027s a little"},{"line_number":42,"context_line":"different from the network multiple provider extension[4] in Neutron. If no"},{"line_number":43,"context_line":"\u0027az_hints\u0027 was specified during network creation, this created network will be"},{"line_number":44,"context_line":"spread into any AZ. If there is a list of \u0027az_hints\u0027 during the network"},{"line_number":45,"context_line":"creation, that means the network should be able to be spread into these AZs"}],"source_content_type":"text/x-rst","patch_set":27,"id":"7aa08908_ffe3f9d6","line":42,"range":{"start_line":42,"start_character":19,"end_line":42,"end_character":57},"updated":"2016-06-08 09:13:07.000000000","message":"the \u0027az_hints\u0027 meaning in Tricircle is a little different from the \u0027az_hints\u0027 meaning in Neutron[5].\n\n:(","commit_id":"5907822776f8e5a842a10e0467eab527d842505e"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"880bb0ea441e5e28e4901ad0a80ed717f48f79fa","unresolved":false,"context_lines":[{"line_number":57,"context_line":"network associated with one AZ. That means currently a tenant\u0027s network will"},{"line_number":58,"context_line":"be presented only in one bottom OpenStack instance, that also means all VMs"},{"line_number":59,"context_line":"connected to the network will be located at one bottom OpenStack instance."},{"line_number":60,"context_line":"If there are more than one pod in one AZ, refer to the dynamic pod binding.[6]"},{"line_number":61,"context_line":""},{"line_number":62,"context_line":"There are lots of use cases where a tenant needs a network being able to be"},{"line_number":63,"context_line":"spread out into multiple bottom OpenStack instances in one AZ or multiple AZs."}],"source_content_type":"text/x-rst","patch_set":27,"id":"7aa08908_5f0a0d7a","line":60,"range":{"start_line":60,"start_character":74,"end_line":60,"end_character":78},"updated":"2016-06-08 09:13:07.000000000","message":"[6].","commit_id":"5907822776f8e5a842a10e0467eab527d842505e"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"880bb0ea441e5e28e4901ad0a80ed717f48f79fa","unresolved":false,"context_lines":[{"line_number":64,"context_line":""},{"line_number":65,"context_line":"* Capacity expansion: tenants add VMs more and more, the capacity of one"},{"line_number":66,"context_line":"  OpenStack may not be enough, then a new OpenStack instance has to be added"},{"line_number":67,"context_line":"  to the cloud."},{"line_number":68,"context_line":""},{"line_number":69,"context_line":"* Cross OpenStack network service chaining. Service chaining is based on"},{"line_number":70,"context_line":"  the port-pairs. Leveraging the cross pod L2 networking capability which"}],"source_content_type":"text/x-rst","patch_set":27,"id":"7aa08908_9f56355a","line":67,"range":{"start_line":67,"start_character":14,"end_line":67,"end_character":15},"updated":"2016-06-08 09:13:07.000000000","message":". But the tenant still wants to add new VMs into same network.","commit_id":"5907822776f8e5a842a10e0467eab527d842505e"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"880bb0ea441e5e28e4901ad0a80ed717f48f79fa","unresolved":false,"context_lines":[{"line_number":131,"context_line":"  Network in each bottom OpenStack instance is VxLAN type and has the same"},{"line_number":132,"context_line":"  VxLAN ID."},{"line_number":133,"context_line":""},{"line_number":134,"context_line":"  Leverage L2GW[1][2] to implement this type of L2 networking."},{"line_number":135,"context_line":""},{"line_number":136,"context_line":"* Mixed VLAN/VxLAN"},{"line_number":137,"context_line":""}],"source_content_type":"text/x-rst","patch_set":27,"id":"7aa08908_3fb9017a","line":134,"range":{"start_line":134,"start_character":16,"end_line":134,"end_character":20},"updated":"2016-06-08 09:13:07.000000000","message":"[2][3]","commit_id":"5907822776f8e5a842a10e0467eab527d842505e"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"880bb0ea441e5e28e4901ad0a80ed717f48f79fa","unresolved":false,"context_lines":[{"line_number":138,"context_line":"  Network in each bottom OpenStack instance may have different types and/or"},{"line_number":139,"context_line":"  have different segment IDs."},{"line_number":140,"context_line":""},{"line_number":141,"context_line":"  Leverage L2GW[1][2] to implement this type of L2 networking."},{"line_number":142,"context_line":""},{"line_number":143,"context_line":"There is another network type called “Local Network”. For “Local Network”,"},{"line_number":144,"context_line":"the network will be only presented in one bottom OpenStack instance. And the"}],"source_content_type":"text/x-rst","patch_set":27,"id":"7aa08908_7faf092a","line":141,"range":{"start_line":141,"start_character":15,"end_line":141,"end_character":21},"updated":"2016-06-08 09:13:07.000000000","message":"[2][3]","commit_id":"5907822776f8e5a842a10e0467eab527d842505e"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"880bb0ea441e5e28e4901ad0a80ed717f48f79fa","unresolved":false,"context_lines":[{"line_number":185,"context_line":"* Type driver to allocate VxLAN segment id for shared VxLAN L2 networking."},{"line_number":186,"context_line":""},{"line_number":187,"context_line":"* Type driver for mixed VLAN/VxLAN to allocate VxLAN segment id for the"},{"line_number":188,"context_line":"  network connecting L2GWs.[1][2]"},{"line_number":189,"context_line":""},{"line_number":190,"context_line":"* Type driver for Local Network only updating ``network_type`` for the"},{"line_number":191,"context_line":"  network by the DB of Tricircle."}],"source_content_type":"text/x-rst","patch_set":27,"id":"7aa08908_9f0e3539","line":188,"range":{"start_line":188,"start_character":25,"end_line":188,"end_character":33},"updated":"2016-06-08 09:13:07.000000000","message":"[2][3]","commit_id":"5907822776f8e5a842a10e0467eab527d842505e"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"880bb0ea441e5e28e4901ad0a80ed717f48f79fa","unresolved":false,"context_lines":[{"line_number":188,"context_line":"  network connecting L2GWs.[1][2]"},{"line_number":189,"context_line":""},{"line_number":190,"context_line":"* Type driver for Local Network only updating ``network_type`` for the"},{"line_number":191,"context_line":"  network by the DB of Tricircle."},{"line_number":192,"context_line":""},{"line_number":193,"context_line":"When a network creation request is received in Neutron API Server in the"},{"line_number":194,"context_line":"Tricircle, the type driver will be called based on the configured network"}],"source_content_type":"text/x-rst","patch_set":27,"id":"7aa08908_ca18f977","line":191,"range":{"start_line":191,"start_character":10,"end_line":191,"end_character":16},"updated":"2016-06-08 09:13:07.000000000","message":"to the Tricircle Neutron DB","commit_id":"5907822776f8e5a842a10e0467eab527d842505e"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"880bb0ea441e5e28e4901ad0a80ed717f48f79fa","unresolved":false,"context_lines":[{"line_number":224,"context_line":""},{"line_number":225,"context_line":"3. L2GW driver under Tricircle Plugin in Neutron API server"},{"line_number":226,"context_line":""},{"line_number":227,"context_line":"Tricircle plugin needs to support multi-segment network extension.[3]"},{"line_number":228,"context_line":""},{"line_number":229,"context_line":"For Shared VxLAN or Mixed VLAN/VxLAN L2 network type, L2GW driver will utilize the"},{"line_number":230,"context_line":"multi-segment network extension in Neutron API server to build the L2 network in the"}],"source_content_type":"text/x-rst","patch_set":27,"id":"7aa08908_2a841d5c","line":227,"range":{"start_line":227,"start_character":65,"end_line":227,"end_character":69},"updated":"2016-06-08 09:13:07.000000000","message":"[4].","commit_id":"5907822776f8e5a842a10e0467eab527d842505e"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"880bb0ea441e5e28e4901ad0a80ed717f48f79fa","unresolved":false,"context_lines":[{"line_number":241,"context_line":""},{"line_number":242,"context_line":"When L2GW driver under Tricircle plugin in Neutron API server receives the"},{"line_number":243,"context_line":"segment update request, L2GW driver will start async job to orchestrate L2GW API"},{"line_number":244,"context_line":"for L2 networking automation.[1][2]"},{"line_number":245,"context_line":""},{"line_number":246,"context_line":""},{"line_number":247,"context_line":"Data model impact"}],"source_content_type":"text/x-rst","patch_set":27,"id":"7aa08908_aac64d97","line":244,"range":{"start_line":244,"start_character":28,"end_line":244,"end_character":35},"updated":"2016-06-08 09:13:07.000000000","message":"[2][3].","commit_id":"5907822776f8e5a842a10e0467eab527d842505e"}]}