)]}'
{"specs/wallaby/mgmt-driver-for-k8s-cluster.rst":[{"author":{"_account_id":25701,"name":"Yasufumi Ogawa","email":"yasufum.o@gmail.com","username":"yasufum"},"change_message_id":"bb776016be9e2d5737f28f518c7ff1042d508149","unresolved":false,"context_lines":[{"line_number":41,"context_line":""},{"line_number":42,"context_line":"* Additional information required for \"Kubernetes with Kube-adm\"."},{"line_number":43,"context_line":""},{"line_number":44,"context_line":"TODO: What type of distro or CNI in Kubernetes will be used in Tacker?"},{"line_number":45,"context_line":"It needs to be discussed in the community. Currently it is assumed that"},{"line_number":46,"context_line":"Kuryr-Kubernetes/Kube-adm will be used."},{"line_number":47,"context_line":""},{"line_number":48,"context_line":".. note:: Kubernetes v1.16.0 and Kubernetes python client v11.0 are supported"},{"line_number":49,"context_line":"          for Kubernetes VIM."}],"source_content_type":"text/x-rst","patch_set":1,"id":"1f621f24_5eacee9d","line":46,"range":{"start_line":44,"start_character":0,"end_line":46,"end_character":39},"updated":"2020-11-17 16:19:07.000000000","message":"Could I confirm this TODO is going to be removed because I remember we\u0027ve agreed to use kube-adm at this time, and consider to support kuryr-k8s then, in the previous vPTG?","commit_id":"676e1e9f68f8f7984698801ce1d9caf03b19eb2f"},{"author":{"_account_id":27880,"name":"Yoshito Ito","email":"yoshito.itou.dr@hco.ntt.co.jp","username":"yoshito-ito"},"change_message_id":"74b6b86ff79a125fb327160db883d9e97225330f","unresolved":false,"context_lines":[{"line_number":41,"context_line":""},{"line_number":42,"context_line":"* Additional information required for \"Kubernetes with Kube-adm\"."},{"line_number":43,"context_line":""},{"line_number":44,"context_line":"TODO: What type of distro or CNI in Kubernetes will be used in Tacker?"},{"line_number":45,"context_line":"It needs to be discussed in the community. Currently it is assumed that"},{"line_number":46,"context_line":"Kuryr-Kubernetes/Kube-adm will be used."},{"line_number":47,"context_line":""},{"line_number":48,"context_line":".. note:: Kubernetes v1.16.0 and Kubernetes python client v11.0 are supported"},{"line_number":49,"context_line":"          for Kubernetes VIM."}],"source_content_type":"text/x-rst","patch_set":1,"id":"1f621f24_ed02690b","line":46,"range":{"start_line":44,"start_character":0,"end_line":46,"end_character":39},"in_reply_to":"1f621f24_5eacee9d","updated":"2020-11-18 09:17:27.000000000","message":"Yes, that is the conclusion in the vPTG, so I deleted this TODO in the next patch.","commit_id":"676e1e9f68f8f7984698801ce1d9caf03b19eb2f"},{"author":{"_account_id":17255,"name":"Toshiaki Takahashi","email":"ts-takahashi@nec.com","username":"takahashi_ts"},"change_message_id":"e657abb6001aafd412b089be8649df73f26598d8","unresolved":true,"context_lines":[{"line_number":1136,"context_line":"Since CNF-B will be deployed on the Kubernetes cluster created inside VNF-A,"},{"line_number":1137,"context_line":"the operations performed on VNF-A will affect VNF-B."},{"line_number":1138,"context_line":""},{"line_number":1139,"context_line":"Termination of VNF-B"},{"line_number":1140,"context_line":"~~~~~~~~~~~~~~~~~~~~"},{"line_number":1141,"context_line":""},{"line_number":1142,"context_line":"This will destroy VNF-B and data being processed by VNF-B will become"}],"source_content_type":"text/x-rst","patch_set":2,"id":"2ec800ac_ab3bba48","line":1139,"range":{"start_line":1139,"start_character":15,"end_line":1139,"end_character":20},"updated":"2020-11-22 14:26:19.000000000","message":"VNF-A?\n\nIn my understanding, the following sentence explains that termination of VNF-A(K8S cluster) destroy VNF-B(CNF).","commit_id":"921b748b39a3d67e68c0960c934827183f5c3516"},{"author":{"_account_id":27880,"name":"Yoshito Ito","email":"yoshito.itou.dr@hco.ntt.co.jp","username":"yoshito-ito"},"change_message_id":"e08fa89b43ac5d5f56b9f41309098aff3f11299b","unresolved":true,"context_lines":[{"line_number":1136,"context_line":"Since CNF-B will be deployed on the Kubernetes cluster created inside VNF-A,"},{"line_number":1137,"context_line":"the operations performed on VNF-A will affect VNF-B."},{"line_number":1138,"context_line":""},{"line_number":1139,"context_line":"Termination of VNF-B"},{"line_number":1140,"context_line":"~~~~~~~~~~~~~~~~~~~~"},{"line_number":1141,"context_line":""},{"line_number":1142,"context_line":"This will destroy VNF-B and data being processed by VNF-B will become"}],"source_content_type":"text/x-rst","patch_set":2,"id":"b063c901_7ea526d6","line":1139,"range":{"start_line":1139,"start_character":15,"end_line":1139,"end_character":20},"in_reply_to":"2ec800ac_ab3bba48","updated":"2020-11-24 00:59:31.000000000","message":"Thank you, VNF-A is exactly correct. I fixed it in the next patch set.","commit_id":"921b748b39a3d67e68c0960c934827183f5c3516"}]}