)]}'
{"specs/victoria/cnf-on-k8s-cluster-inside-vm.rst":[{"author":{"_account_id":17255,"name":"Toshiaki Takahashi","email":"ts-takahashi@nec.com","username":"takahashi_ts"},"change_message_id":"1bc166d04a2e7e7d2e2b6253a5fb7e6651226124","unresolved":false,"context_lines":[{"line_number":90,"context_line":"in `LCM-operation-with-user-data`_ specification. The reason is that the"},{"line_number":91,"context_line":"Kubernetes cluster will be set up with `Kuryr-Kubernetes`_. The cluster"},{"line_number":92,"context_line":"installation requires some essential network entities such as Router and"},{"line_number":93,"context_line":"LoadBalancer. TOSCA v1.2 has definition for LoadBalancer but it is not"},{"line_number":94,"context_line":"supported by heat-translator. Router definition is not present in TOSCA v1.2."},{"line_number":95,"context_line":""},{"line_number":96,"context_line":"TODO: What type of Kubernetes will be used in Tacker? It needs to be discussed"},{"line_number":97,"context_line":"in the community. Currently it is assumed that Kuryr-kubernetes will be used."}],"source_content_type":"text/x-rst","patch_set":1,"id":"bf51134e_a69cc85b","line":94,"range":{"start_line":93,"start_character":14,"end_line":94,"end_character":77},"updated":"2020-07-06 16:43:15.000000000","message":"Do you mean that we cannot create LoadBalancer nor Router using TOSCA with this spec\u0027s features?\nIf so, these sentences seem note.","commit_id":"82ea2f2504721353d6b750aa8ec09362abe84208"},{"author":{"_account_id":27880,"name":"Yoshito Ito","email":"yoshito.itou.dr@hco.ntt.co.jp","username":"yoshito-ito"},"change_message_id":"14f1146824acc780ddd412d618fd150c29428d92","unresolved":false,"context_lines":[{"line_number":90,"context_line":"in `LCM-operation-with-user-data`_ specification. The reason is that the"},{"line_number":91,"context_line":"Kubernetes cluster will be set up with `Kuryr-Kubernetes`_. The cluster"},{"line_number":92,"context_line":"installation requires some essential network entities such as Router and"},{"line_number":93,"context_line":"LoadBalancer. TOSCA v1.2 has definition for LoadBalancer but it is not"},{"line_number":94,"context_line":"supported by heat-translator. Router definition is not present in TOSCA v1.2."},{"line_number":95,"context_line":""},{"line_number":96,"context_line":"TODO: What type of Kubernetes will be used in Tacker? It needs to be discussed"},{"line_number":97,"context_line":"in the community. Currently it is assumed that Kuryr-kubernetes will be used."}],"source_content_type":"text/x-rst","patch_set":1,"id":"bf51134e_238b9c68","line":94,"range":{"start_line":93,"start_character":14,"end_line":94,"end_character":77},"in_reply_to":"bf51134e_a69cc85b","updated":"2020-07-22 00:00:10.000000000","message":"Yes, I mean we cannot. We need to use user-data based instantiation. I moved these sentences to a note.","commit_id":"82ea2f2504721353d6b750aa8ec09362abe84208"},{"author":{"_account_id":17255,"name":"Toshiaki Takahashi","email":"ts-takahashi@nec.com","username":"takahashi_ts"},"change_message_id":"1bc166d04a2e7e7d2e2b6253a5fb7e6651226124","unresolved":false,"context_lines":[{"line_number":93,"context_line":"LoadBalancer. TOSCA v1.2 has definition for LoadBalancer but it is not"},{"line_number":94,"context_line":"supported by heat-translator. Router definition is not present in TOSCA v1.2."},{"line_number":95,"context_line":""},{"line_number":96,"context_line":"TODO: What type of Kubernetes will be used in Tacker? It needs to be discussed"},{"line_number":97,"context_line":"in the community. Currently it is assumed that Kuryr-kubernetes will be used."},{"line_number":98,"context_line":""},{"line_number":99,"context_line":".. note:: Although VM resource information can be included in VNFD in future,"}],"source_content_type":"text/x-rst","patch_set":1,"id":"bf51134e_26a398b3","line":96,"updated":"2020-07-06 16:43:15.000000000","message":"This \"type\" means \"which CNI is used\"? or including other network components?\nIn other words, what is an example of \"another type Kubernetes\"?","commit_id":"82ea2f2504721353d6b750aa8ec09362abe84208"},{"author":{"_account_id":27880,"name":"Yoshito Ito","email":"yoshito.itou.dr@hco.ntt.co.jp","username":"yoshito-ito"},"change_message_id":"14f1146824acc780ddd412d618fd150c29428d92","unresolved":false,"context_lines":[{"line_number":93,"context_line":"LoadBalancer. TOSCA v1.2 has definition for LoadBalancer but it is not"},{"line_number":94,"context_line":"supported by heat-translator. Router definition is not present in TOSCA v1.2."},{"line_number":95,"context_line":""},{"line_number":96,"context_line":"TODO: What type of Kubernetes will be used in Tacker? It needs to be discussed"},{"line_number":97,"context_line":"in the community. Currently it is assumed that Kuryr-kubernetes will be used."},{"line_number":98,"context_line":""},{"line_number":99,"context_line":".. note:: Although VM resource information can be included in VNFD in future,"}],"source_content_type":"text/x-rst","patch_set":1,"id":"bf51134e_63eab40e","line":96,"in_reply_to":"bf51134e_26a398b3","updated":"2020-07-22 00:00:10.000000000","message":"I clarified that this \"type\" means \"distro and CNI\".","commit_id":"82ea2f2504721353d6b750aa8ec09362abe84208"},{"author":{"_account_id":17255,"name":"Toshiaki Takahashi","email":"ts-takahashi@nec.com","username":"takahashi_ts"},"change_message_id":"1bc166d04a2e7e7d2e2b6253a5fb7e6651226124","unresolved":false,"context_lines":[{"line_number":355,"context_line":""},{"line_number":356,"context_line":"The heal use case of VNF LCM sequence terminates existing VM and spawns a new"},{"line_number":357,"context_line":"replacement VM. The VM being terminated may be running Kubernetes cluster\u0027s"},{"line_number":358,"context_line":"master node. Hence it will be necessary to terminate VNF-B gracefully before"},{"line_number":359,"context_line":"performing heal operation on VNF-A. The required sequence will be described in"},{"line_number":360,"context_line":"the user guide."},{"line_number":361,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"bf51134e_c193a65b","line":358,"range":{"start_line":358,"start_character":43,"end_line":358,"end_character":58},"updated":"2020-07-06 16:43:15.000000000","message":"Is \"terminate VNF-B\" correct?\nThis is healing sequence, so I think VNF-B\u0027s service should not stop.\n\nIf VNF-A has multiple master nodes, we should just recreate a master node without stopping other master nodes. In this case, VNF-B should not be terminated.\n(I\u0027m not sure that how we can heal if VNF-A has 1 master node...)","commit_id":"82ea2f2504721353d6b750aa8ec09362abe84208"},{"author":{"_account_id":27880,"name":"Yoshito Ito","email":"yoshito.itou.dr@hco.ntt.co.jp","username":"yoshito-ito"},"change_message_id":"14f1146824acc780ddd412d618fd150c29428d92","unresolved":false,"context_lines":[{"line_number":355,"context_line":""},{"line_number":356,"context_line":"The heal use case of VNF LCM sequence terminates existing VM and spawns a new"},{"line_number":357,"context_line":"replacement VM. The VM being terminated may be running Kubernetes cluster\u0027s"},{"line_number":358,"context_line":"master node. Hence it will be necessary to terminate VNF-B gracefully before"},{"line_number":359,"context_line":"performing heal operation on VNF-A. The required sequence will be described in"},{"line_number":360,"context_line":"the user guide."},{"line_number":361,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"bf51134e_23a6fcac","line":358,"range":{"start_line":358,"start_character":43,"end_line":358,"end_character":58},"in_reply_to":"bf51134e_c193a65b","updated":"2020-07-22 00:00:10.000000000","message":"The VNF-B should not be affected by the operations on VNF-A, and the point here is Tacker cannot handle the dependency between VNFs so user need to be responsible for it.\n\nAs you mention, this example of \"terminate\" is not appropriate, and I changed it in the new patch. Could you confirm it?","commit_id":"82ea2f2504721353d6b750aa8ec09362abe84208"},{"author":{"_account_id":17255,"name":"Toshiaki Takahashi","email":"ts-takahashi@nec.com","username":"takahashi_ts"},"change_message_id":"7de57d612312117946c425038e0138ecf898fd36","unresolved":false,"context_lines":[{"line_number":158,"context_line":"        mgmt-drivers-kubernetes:"},{"line_number":159,"context_line":"          description: Management driver for kubernetes cluster"},{"line_number":160,"context_line":"          type: tosca.artifacts.Implementation.Python"},{"line_number":161,"context_line":"          file: /.../mgmt_drivers/kubernetes_mgmt.py"},{"line_number":162,"context_line":""},{"line_number":163,"context_line":"  # data_types:"},{"line_number":164,"context_line":"  #  MyCompany.datatypes.nfv.VnfInstantiateAdditionalParameters:"}],"source_content_type":"text/x-rst","patch_set":5,"id":"9f560f44_c80cd295","line":161,"updated":"2020-08-09 17:36:16.000000000","message":"Do you think this kubernetes setup script should be in Tacker repository? Basically, such scripts should not be included in Tacker\u0027s functionality. But if it\u0027s one of the Mgmt Drivers, it\u0027s just a sample (openwrt mgmtdriver is already included). In addtion, for the users, they can use kubernetes seting script with only installing Tacker.\nOf course, not including is also correct option.","commit_id":"1323a389f6c71ca915009a951304b3c74af302d0"},{"author":{"_account_id":27880,"name":"Yoshito Ito","email":"yoshito.itou.dr@hco.ntt.co.jp","username":"yoshito-ito"},"change_message_id":"779836555ec1c01edb20c17ca25ae10c9d5a8fa1","unresolved":false,"context_lines":[{"line_number":158,"context_line":"        mgmt-drivers-kubernetes:"},{"line_number":159,"context_line":"          description: Management driver for kubernetes cluster"},{"line_number":160,"context_line":"          type: tosca.artifacts.Implementation.Python"},{"line_number":161,"context_line":"          file: /.../mgmt_drivers/kubernetes_mgmt.py"},{"line_number":162,"context_line":""},{"line_number":163,"context_line":"  # data_types:"},{"line_number":164,"context_line":"  #  MyCompany.datatypes.nfv.VnfInstantiateAdditionalParameters:"}],"source_content_type":"text/x-rst","patch_set":5,"id":"9f560f44_9a1620f1","line":161,"in_reply_to":"9f560f44_c80cd295","updated":"2020-08-19 09:04:51.000000000","message":"I think the script can be in Tacker repository of \u0027tacker/sample\u0027 not to be included as Tacker\u0027s functionality as you mention. The Mgmt Driver for Kubernetes LCM will be stored in mgmt_driver directory as the openwrt case.","commit_id":"1323a389f6c71ca915009a951304b3c74af302d0"}]}