85 | | |
| 85 | == !StartSegment == |
| 86 | |
| 87 | This is the operation where the plug-in has the most to do. The resources described in the segment description are attached to the allocation and configured to provide the various services, including interconnection with other testbeds. |
| 88 | |
| 89 | The request has the format: |
| 90 | |
| 91 | {{{ |
| 92 | request = { |
| 93 | 'allocID' { 'fedid': fedid_obj }, |
| 94 | 'segmentdescription': { |
| 95 | 'topdldescription': { |
| 96 | # a topdl description as a dict (see below) |
| 97 | }, |
| 98 | }, |
| 99 | 'service': [ |
| 100 | # The meta service 'export_project' in the request has become 2 actual service descriptions with the same ID as the request |
| 101 | { 'id': '0001', 'name': 'SMB', 'visibility': 'export', 'fedAttr: [ { 'attribute': 'att_name', 'value': 'val1'} ] } ] }, |
| 102 | { 'id': '0001', 'name': 'userconf', 'visibility': 'export', 'fedAttr: [ { 'attribute': 'att_name', 'value': 'val1'} ] }, |
| 103 | ], |
| 104 | 'connection': [ |
| 105 | { |
| 106 | 'type': 'transit', |
| 107 | 'portal': 'hostname', |
| 108 | 'peer': 'remote_hostname', |
| 109 | 'parameter': [ |
| 110 | { |
| 111 | # The parameter |
| 112 | 'name': 'ssh_port', |
| 113 | # Where to get it (local part of a url) |
| 114 | 'key': 'djfahlshl/val', |
| 115 | # where to get it (host running the synchronized store) |
| 116 | 'store': 'https://users.isi.deterlab.net:13232', |
| 117 | # Whether we need to send or receive the value |
| 118 | 'type': 'output', |
| 119 | }, |
| 120 | ] |
| 121 | } |
| 122 | ], |
| 123 | } |
| 124 | }}} |