<!DOCTYPE html>
<html><head>
<meta charset="UTF-8">
</head><body style=""><div>Hi,<br>we're trying to use the Heat Software configuration APIs, but we're facing a problem with the signaling.</div>
<div>We quite well know how to use Software config/deployment inside stack Templates, and in that case what we got on the target VM is something like this:<br><br></div>
<div>#os-collect-config --print<br>inputs:[<br>…<br> {<br> "type": "String", <br> "name": "deploy_signal_transport", <br> "value": "CFN_SIGNAL", <br> "description": "How the server should signal to heat with the deployment output values."<br> }, <br> {<br> "type": "String", <br> "name": "deploy_signal_id", <br> "value": "http://ctrl-liberty.nuvolacsi.it:8000/v1/signal/arn%3Aopenstack%3Aheat%3A%3Ab570fe9ea2c94cb8ba72fe07fa034b62%3Astacks%2FStack_test_from_view_galera-53040%2F15d0e95a-e422-4994-9f17-bb2f543952f7%2Fresources%2Fdeployment_sw_mariadb2?Timestamp=2016-11-24T16%3A35%3A12Z&SignatureMethod=HmacSHA256&AWSAccessKeyId=72ef8cef2e174926b74252754617f347&SignatureVersion=2&Signature=H5QcAv7yIZgBQzhztb4%2B0NJi7Z3qO%2BmwToqINUiKbvw%3D", <br> "description": "ID of signal to use for signaling output values"<br> }, <br> {<br> "type": "String", <br> "name": "deploy_signal_verb", <br> "value": "POST", <br> "description": "HTTP verb to use for signaling output values"<br> }</div>
<div><br>This part, we suppose, is generated by heat during the Template processing and is pushed to the target so that, when the deployment is finished, the os-apply-config uses CFN to signal to the orchestrator the SUCCESS/FAILED job.</div>
<div> </div>
<div>The problem is that, when we try to use directly the software config creation API and the deployment one, what we got in the target VM is something like this:</div>
<div> </div>
<div>#os-collect-config --print<br>...<br> {<br> "inputs": [], <br> "group": null, <br> "name": "test_key_gen_9aznXZ7DE9", <br> "outputs": [], <br> "creation_time": "2016-11-24T15:50:50", <br> "options": {}, <br> "config": "#!/bin/bash\ntouch /tmp/test \nhostname > /tmp/test \n", <br> "id": "d9395163-4238-4e94-902f-1e8abdbfa2bb"<br> }</div>
<div><br>This appens because we pass to the create SW config API no explicit parameter in the “inputs” key. <br>Of course, this config causes no signaling back to Heat.<br><br>So the questions are:</div>
<div> </div>
<div>Is it possible to use the cfn signaling with the software configuration/deployment creation APIs? <br><br>How?<br><br>Is it possible to have a signaling back to the orchestration without passing manually a deploy_signal_id inside the API's configuration parameters?<br><br>If not, another way to give a signal back to Orchestrator, could be a workaround creating a self-standing stack containing only “OS::Heat::WaitCondition” and “OS::Heat::WaitConditionHandlewaitsignals” resources, but before using this workaround we want to be sure that is not possible in other ways.<br><br>Thanks<br><br>Pasquale</div></body></html>