Changes between Version 10 and Version 11 of Omni
- Timestamp:
- 09/13/10 12:38:25 (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Omni
v10 v11 46 46 47 47 3. Run omni listresources > avail-resources.omnispec 48 a. When you do this, Omni will contact your designated Clearinghouse, using your framework-specific user credentials. 49 b. The clearinghouse will list the Aggregates it knows about. EG for GCF, the am_* entries in gcf_config. For SFA, it will 48 a. When you do this, Omni will contact your designated Clearinghouse, using 49 your framework-specific user credentials. 50 b. The clearinghouse will list the Aggregates it knows about. EG for GCF, 51 the am_* entries in gcf_config. For SFA, it will 50 52 return the contents of /etc/sfa/geni_aggregates.xml. 51 c. Omni will then contact each of the Aggregates that the Clearinghouse told it about, and use the GENI AM API to ask 52 each for its resources. Again, it will use your user credentials. So each Aggregate Manager must trust the signer of your 53 user credentials, in order for you to talk to it. This is why you add the CH certificate to /etc/sfa/trusted_roots or to the 54 -r argument of your GCF gcf-am.py. 53 c. Omni will then contact each of the Aggregates that the Clearinghouse 54 told it about, and use the GENI AM API to ask each for its resources. Again, 55 it will use your user credentials. So each Aggregate Manager must trust the 56 signer of your user credentials, in order for you to talk to it. This is why 57 you add the CH certificate to /etc/sfa/trusted_roots or to the -r argument of 58 your GCF gcf-am.py. 55 59 d. Omni will then convert the proprietary RSPecs into a single 'omnispec'. 56 60 … … 115 119 Deletes the slice in your chosen control framework 116 120 121 ==== getversion ==== 122 * format: omni.py getversion [-a AM-URL] 123 * examples: 124 * omni.py getversion 125 * omni.py getversion -a http://localhost:12348 117 126 118 127 ==== listresources ==== 119 * format: omni.py listresources [slice-name] [-a AM-URL] [-n] 120 * example: omni.py listresources 121 omni.py listresources myslice 122 omni.py listresources myslice -a http://localhost:12348 123 omni.py listresources myslice -a http://localhost:12348 -n 128 * format: omni.py listresources [-a AM-URL [-n]] [slice-name] 129 * examples: 130 * omni.py listresources 131 * omni.py listresources myslice 132 * omni.py listresources -a http://localhost:12348 myslice 133 * omni.py listresources -a http://localhost:12348 -n myslice 124 134 125 135 This command will list the rspecs of all geni aggregates available … … 128 138 to set up a reservation RSpec, suitable for use in a call to 129 139 createsliver. 140 130 141 If a slice name is supplied, then resources for that slice only 131 142 will be displayed. 143 132 144 If an Aggregate Manager URL is supplied, only resources 133 145 from that AM will be listed. 146 134 147 If the "-n" flag s used the native RSpec is returned instead of an 135 148 omnispec. The "-n" flag requires the "-a" flag also be used to … … 138 151 139 152 ==== createsliver ==== 140 * format: omni.py createsliver <slice-name> [-a AM-URL -n] <spec file> 141 * example: omni.py createsliver myslice resources.ospec 142 omni.py createsliver myslice -a http://localhost:12348 -n resources.rspec 153 * format: omni.py createsliver [-a AM-URL [-n]] <slice-name> <spec file> 154 * examples: 155 * omni.py createsliver myslice resources.ospec 156 * omni.py createsliver -a http://localhost:12348 -n myslice resources.rspec 143 157 144 158 * argument: the spec file should have been created by a call to … … 154 168 155 169 ==== deletesliver ==== 156 * format: omni.py deletesliver <slice-name> 157 * example: omni.py deletesliver myslice 170 * format: omni.py deletesliver [-a AM-URL] <slice-name> 171 * examples: 172 * omni.py deletesliver myslice 173 * omni.py deletesliver -a http://localhost:12348 myslice 158 174 159 175 This command will free any resources associated with your slice. 160 176 161 177 162 163 178 ==== renewsliver ==== 164 * format: omni.py renewsliver <slice-name> "<time>" 165 * example: omni.py renewsliver myslice "12/12/10 4:15pm" 166 * example: omni.py renewsliver myslice "12/12/10 16:15" 179 * format: omni.py renewsliver [-a AM-URL] <slice-name> "<time>" 180 * examples: 181 * omni.py renewsliver myslice "12/12/10 4:15pm" 182 * omni.py renewsliver myslice "12/12/10 16:15" 183 * omni.py renewsliver -a http://localhost:12348 myslice "12/12/10 16:15" 167 184 168 185 This command will renew your resources at each aggregate up to the … … 173 190 174 191 ==== sliverstatus ==== 175 * format: omni.py sliverstatus <slice-name> 176 * example: omni.py sliverstatus myslice 192 * format: omni.py sliverstatus [-a AM-URL] <slice-name> 193 * examples: 194 * omni.py sliverstatus myslice 195 * omni.py sliverstatus -a http://localhost:12348 myslice 177 196 178 197 This command will get information from each aggregate about the … … 181 200 182 201 ==== shutdown ==== 183 * format: omni.py shutdown <slice-name> 184 * example: omni.py shutdown myslice 202 * format: omni.py shutdown [-a AM-URL] <slice-name> 203 * examples: 204 * omni.py shutdown myslice 205 * omni.py shutdown -a http://localhost:12348 myslice 185 206 186 207 This command will stop the resources from running, but not delete