72 | | For version control purposes, it is important to save the resource request specification (RSpec) at each step. Thus, when all VMs are ready for login, we save a copy of the current RSpec as `4node-v1.rspec`. |
73 | | We can do so by clicking the '''View''' and choosing '''Preview requested document(s)''' from the pull-down list. You will see the RSpec generated by Flack looks like the following: |
74 | | |
75 | | {{{ |
76 | | <rspec type="request" generated_by="Flack" generated="2014-08-07T22:23:33Z" xsi:schemaLocation="http://www.geni.net/resources/rspec/3 http://www.geni.net/resources/rspec/3/request.xsd " xmlns:flack="http://www.protogeni.net/resources/rspec/ext/flack/1" xmlns:client="http://www.protogeni.net/resources/rspec/ext/client/1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.geni.net/resources/rspec/3"> |
77 | | <node client_id="router-2" component_manager_id="urn:publicid:IDN+instageni.stanford.edu+authority+cm" exclusive="false" xmlns:rs="http://www.protogeni.net/resources/rspec/ext/emulab/1"> |
78 | | <rs:vnode name="pcvm3-13" xmlns="http://www.protogeni.net/resources/rspec/ext/emulab/1"/> |
79 | | <sliver_type name="emulab-xen"> |
80 | | <disk_image url="https://www.instageni.clemson.edu/image_metadata.php?uuid=5417bcef-224e-11e4-aa5a-000000000000"/> |
81 | | </sliver_type> |
82 | | <interface client_id="xen:if0"> |
83 | | <ip address="192.168.1.2" netmask="255.255.255.0" type="ipv4"/> |
84 | | <flack:interface_info addressBound="false" bound="false"/> |
85 | | </interface> |
86 | | <interface client_id="xen:if1"> |
87 | | <ip address="192.168.2.1" netmask="255.255.255.0" type="ipv4"/> |
88 | | <flack:interface_info addressBound="false" bound="false"/> |
89 | | </interface> |
90 | | <interface client_id="xen:if2"> |
91 | | <ip address="192.168.5.1" netmask="255.255.255.0" type="ipv4"/> |
92 | | <flack:interface_info addressBound="false" bound="false"/> |
93 | | </interface> |
94 | | <flack:node_info x="422" y="170" unbound="true"/> |
95 | | </node> |
96 | | }}} |
97 | | |
98 | | |
99 | | Choose '''Save to file''' to export the RSpec. In this tutorial, we assume the file is saved to `4node-v1.rspec`, but you can choose any name as you like. (You can download a sample RSpec for `4node-v1.rspec` at [http://www.gpolab.bbn.com/exp/sysexpr/rspec-for-wiki/4node-v1.rspec here]) |
| 72 | For version control purposes, it is important to save the resource request specification (RSpec) at each step. Thus, once we have defined the topology above, we select the ''' ''Download'' ''' button to save an intermediate version of your RSpec. |
| 73 | |
| 74 | [Image(SaveRSpec.jpg)] |
| 75 | |
| 76 | {{{ |
| 77 | #!html |
| 78 | <table border="0" cellpadding="0" cellspacing="0"><tr><td><img src="http://trac.gpolab.bbn.com/gcf/raw-attachment/wiki/Graphics/stock_notes.png" width="40" height="40" alt="Note"></td><td> The save command does not allow naming it simply used the slice name to generate a file. </td></tr></table> |
| 79 | </li> |
| 80 | </ol> |
| 81 | </td> |
| 82 | </tr> |
| 83 | </table> |
| 84 | }}} |
| 85 | |
| 86 | In this tutorial, we assume the file is saved to `4node-v1.rspec`, but you can choose any name as you like. (You can download a sample RSpec for `4node-v1.rspec` at [http://www.gpolab.bbn.com/exp/sysexpr/rspec-for-wiki/4node-v1.rspec here]) |
| 87 | |
| 88 | |
| 89 | Choose '''Save to file''' to export the RSpec. |