| 174 | This operation basically undoes the resource assignemnt and configuration accomplished by !StartSegment. The sub-experiment resources are released and the connectivity and services terminated. Local facility rules on cleaning the resources and restoring them to use by others apply. |
| 175 | |
| 176 | The request message looks like: |
| 177 | |
| 178 | {{{ |
| 179 | request = { |
| 180 | 'allocID': { 'fedid': fedid_obj }, |
| 181 | 'force': True, |
| 182 | } |
| 183 | }}} |
| 184 | |
| 185 | AllocID identifies the sub-experiment to terminate. If {{{force}}} is True, remove resources even if they are in the middle of being allocate or if the plug-in would otherwise not do so. |
| 186 | |
| 187 | The response messgae looks like: |
| 188 | |
| 189 | {{{ |
| 190 | response = { |
| 191 | 'allocID': { 'fedid': fedid_obj }, |
| 192 | 'deallocationLog': 'A long string', |
| 193 | } |
| 194 | }}} |
| 195 | |
| 196 | The {{{allocID}}} tells which segment has been destroyed. A plug-in can also send the deallocation log to the experiment controller and on to the user. [FeddCommands#fedd_terminate.py fedd_terminate.py] provides an option to display or save these logs, if plug-ins send them. |
| 197 | |
| 198 | == !ReleaseAccess == |
| 199 | |