| 94 | | <p>Next, you should load this topology into Flack. ...FIXME screenshot</p> |
| | 105 | <table><tr> |
| | 106 | <td> |
| | 107 | <p>Next, you should load this topology into Flack.</p> |
| | 108 | <p>From the "Import" menu (see figure), select the "Import from file" item.<p> |
| | 109 | <p>Now select the file you saved a moment ago and open it.</p> |
| | 110 | <p>Because this file contains a generic description of resources and does |
| | 111 | not specify any particular aggregate manager, Flack will report |
| | 112 | "There were resources detected without a manager selected, please select which manager you would like to use." |
| | 113 | Select "OK", and then choose the manager listed on your worksheet from the |
| | 114 | list. Then select "Accept", and a network topology (which might look |
| | 115 | familiar if you have completed earlier tutorials) should appear |
| | 116 | on the canvas.</p> |
| | 117 | </td> |
| | 118 | <td><img src="http://groups.geni.net/geni/attachment/wiki/GENIExperimenter/Tutorials/PortalOmniExample/ObtainResources/flack-import-small.png?format=raw" /></td> |
| | 119 | </tr></table> |
| 99 | | Click "i" on client |
| 100 | | |
| 101 | | + Add Install Service |
| 102 | | {{{ |
| | 124 | {{{ |
| | 125 | #!html |
| | 126 | <table><tr> |
| | 127 | <td><p>For this sample experiment, we'd like some additional software |
| | 128 | (<tt>Apache</tt>, <tt>iperf</tt>, and a couple of custom scripts) loaded |
| | 129 | onto the VMs to perform traffic measurements. In Flack, you can manipulate |
| | 130 | the details of the request for a node or link with the "<tt>i</tt>" button |
| | 131 | on the relevant component on the canvas (see figure). Do this now on the |
| | 132 | client node.</p></td> |
| | 133 | <td><img src="http://groups.geni.net/geni/attachment/wiki/GENIExperimenter/Tutorials/PortalOmniExample/ObtainResources/flack-node-info-small.png?format=raw" /></td> |
| | 134 | </tr></table> |
| | 135 | |
| | 136 | <table><tr> |
| | 137 | <td><p>When you open the node information, you should see options like those |
| | 138 | in the figure. The controls available to you will vary depending on the |
| | 139 | types of the aggregate manager and the component, but many features are |
| | 140 | widely available throughout GENI.</p> |
| | 141 | |
| | 142 | <p>The way we will request installation of the proper software and execution |
| | 143 | of our experiment is to add <i>install</i> and <i>execute</i> services. |
| | 144 | First, select "<tt>+ Add Install Service</tt>" as shown. Flack will now |
| | 145 | prompt you for an "Archive URL" and a location for installation. For this |
| | 146 | experiment, please enter the URL: |
| | 147 | <pre class="wiki"> |
| 112 | | |
| 113 | | Apply |
| 114 | | |
| 115 | | Same on server |
| | 163 | </pre></p> |
| | 164 | |
| | 165 | <p>Be very careful when entering this information -- these commands will not |
| | 166 | be executed yet, so it will be some time before you will see any relevant |
| | 167 | error messages if there is a mistake here.</p> |
| | 168 | |
| | 169 | <p>Once both the "install" and "execute" services are specified, please |
| | 170 | choose "Apply". Then repeat the procedure to add the same "install" and |
| | 171 | "execute" services on the server node.</p> |
| | 172 | |
| | 173 | <p>If you have time, it would be instructive to download the "<tt>hellogeni-install</tt>" file yourself, and inspect the contents. You will see the <tt>install-script.sh</tt> file referred to in the execute service, and this is a good example of how you can ask for GENI components to perform tasks for you without any manual intervention. This is a very useful facility for large experiments!</p> |
| | 174 | </td> |
| | 175 | <td><img src="http://groups.geni.net/geni/attachment/wiki/GENIExperimenter/Tutorials/PortalOmniExample/ObtainResources/flack-services-small.png?format=raw" /></td> |
| | 176 | </tr></table> |
| | 177 | }}} |
| 118 | | |
| 119 | | View rspec |
| 120 | | |
| 121 | | Save to file |
| | 180 | {{{ |
| | 181 | #!html |
| | 182 | <p>Now we will pull back some of the covers and inspect exactly what Flack has been doing for us when preparing the rspecs for the experiments we design. Each node and link has a corresponding element in the rspec, and the details of the component configuration (such as the install and execute services we requested above) are specified with attributes, or sometimes child elements, within those portions of the document.</p> |
| | 183 | |
| | 184 | <table><tr> |
| | 185 | <td> |
| | 186 | <p>Please use the "View" menu (see figure) and select the "Preview |
| | 187 | request document(s)" item. This will bring up a window showing the |
| | 188 | current rspec -- please take a moment to inspect it. The XML elements |
| | 189 | under the "<tt>flack</tt>" namespace were added for Flack's internal |
| | 190 | use (containing information about the canvas layout, editing history, etc.), |
| | 191 | and are ignored by aggregate managers. The "node" and "link" elements |
| | 192 | contain the specification for the components we will request, and if you |
| | 193 | look closely, you will be able to see the install and execute service |
| | 194 | elements you added earlier.</p> |
| | 195 | |
| | 196 | <p>Next, please use the "Save to file" button (in the upper left) to |
| | 197 | make a local copy of your rspec. We'll use this in the next step to |
| | 198 | demonstrate how other client tools also use rspec files to communicate |
| | 199 | requests to aggregate managers.</p> |
| | 200 | </td> |
| | 201 | <td><img src="http://groups.geni.net/geni/attachment/wiki/GENIExperimenter/Tutorials/PortalOmniExample/ObtainResources/flack-view-small.png?format=raw" /></td> |
| | 202 | </tr></table> |
| | 203 | }}} |
