)]}'
{"specs/victoria/support-scale-api-based-on-etsi-nfv-sol.rst":[{"author":{"_account_id":26588,"name":"Hiroyuki Jo","email":"joxyuki@gmail.com","username":"joxyuki"},"change_message_id":"3f7f43a995c13d38c5e0af14c5caa8dde2451124","unresolved":false,"context_lines":[{"line_number":187,"context_line":""},{"line_number":188,"context_line":"When scale-in (resource-signal) is executed using Heat, Heat operates to"},{"line_number":189,"context_line":"delete the VM which was created at first. Depending on the VNF, it may be"},{"line_number":190,"context_line":"necessary to delete the VM that is last created . Therefore, it is"},{"line_number":191,"context_line":"possible to select the order of VM removal in \u0027additionalParams\u0027 as"},{"line_number":192,"context_line":"scaling request parameter. If isReverse in \u0027additionalParams\u0027 is True,"},{"line_number":193,"context_line":"delete from the last registered VM. If not, delete from first registered"},{"line_number":194,"context_line":"VM. If \u0027additionalParams\u0027 is not set, the behavior is the same as False."},{"line_number":195,"context_line":""},{"line_number":196,"context_line":"Postcondition: VNF instance still in INSTANTIATED state and VNF has been"}],"source_content_type":"text/x-rst","patch_set":1,"id":"9f560f44_08fb6ac0","line":193,"range":{"start_line":190,"start_character":50,"end_line":193,"end_character":35},"updated":"2020-08-09 14:30:09.000000000","message":"This is a specification and expected behavior of ETSI NFV but not Heat. How to delete the newest VM using Heat? If it is not possible, you should note that as a limitation here.","commit_id":"fcacd8ad2989695cc719834170035867e5a7043a"},{"author":{"_account_id":27180,"name":"Keiko Kuriu","email":"kuriu.keiko@gmail.com","username":"keiko-k"},"change_message_id":"7d0afd50618c825a81ec7d2aebe00d7a969e2eea","unresolved":false,"context_lines":[{"line_number":187,"context_line":""},{"line_number":188,"context_line":"When scale-in (resource-signal) is executed using Heat, Heat operates to"},{"line_number":189,"context_line":"delete the VM which was created at first. Depending on the VNF, it may be"},{"line_number":190,"context_line":"necessary to delete the VM that is last created . Therefore, it is"},{"line_number":191,"context_line":"possible to select the order of VM removal in \u0027additionalParams\u0027 as"},{"line_number":192,"context_line":"scaling request parameter. If isReverse in \u0027additionalParams\u0027 is True,"},{"line_number":193,"context_line":"delete from the last registered VM. If not, delete from first registered"},{"line_number":194,"context_line":"VM. If \u0027additionalParams\u0027 is not set, the behavior is the same as False."},{"line_number":195,"context_line":""},{"line_number":196,"context_line":"Postcondition: VNF instance still in INSTANTIATED state and VNF has been"}],"source_content_type":"text/x-rst","patch_set":1,"id":"9f560f44_43b0cedd","line":193,"range":{"start_line":190,"start_character":50,"end_line":193,"end_character":35},"in_reply_to":"9f560f44_08fb6ac0","updated":"2020-08-25 05:36:26.000000000","message":"If additionalParams is True, Tacker will query VMs by \"creation_time\" to extract newest VM. Then Tacker send signal to Heat to mark \"unhealthy\" for the VM  then execute \"stack update\". Therefore Tacker will utilize Heat schema to realize those behavior. So I think there is no special limitation or precondition.","commit_id":"fcacd8ad2989695cc719834170035867e5a7043a"}]}