| 34 | Before proceeding to uploading the manifest and keys, a non admin user must create a slice and a sliver. In this evaluation the |
| 35 | following rspec was used: |
| 36 | {{{ |
| 37 | $ more pg.rspec |
| 38 | <?xml version="1.0" encoding="UTF-8"?> |
| 39 | <rspec xmlns="http://protogeni.net/resources/rspec/0.2"> |
| 40 | <node virtual_id="geni1" |
| 41 | virtualization_type="emulab-vnode"> |
| 42 | tarfiles="/tmp http://mirage.hpl.hp.com/csi_protogeni.tar.gz" |
| 43 | startup_command="/bin/sh/tmp/deploy_initialize.sh"> |
| 44 | </node> |
| 45 | <node virtual_id="geni2" |
| 46 | virtualization_type="emulab-vnode"> |
| 47 | tarfiles="/tmp http://mirage.hpl.hp.com/csi_protogeni.tar.gz" |
| 48 | startup_command="/bin/sh/tmp/deploy_initialize.sh"> |
| 49 | </node> |
| 50 | </rspec> |
| 51 | }}} |
| 52 | '''Note:''' The tarfile and startup_command are required as stated by the S3 user guide. |
| 53 | |
| 54 | The slice and sliver were created and the output was captured to create the manifest file which is required by the S3 setup: |
| 55 | {{{ |
| 56 | |
| 57 | lnevers@sendaria:~/gcf-1.2$ ./src/omni.py createslice s3-slice |
| 58 | INFO:omni:Loading config file omni_config |
| 59 | INFO:omni:Using control framework pgeni |
| 60 | Created slice with Name s3-slice, URN urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+s3-slice |
| 61 | lnevers@sendaria:~/gcf-1.2$ ./src/omni.py -a https://www.emulab.net/protogeni/xmlrpc/am -n createsliver s3-slice pg.rspec > s3-manifest |
| 62 | }}} |
| 63 | |
| 64 | Now Upload Manifest File and select node addresses: |
| 65 | [[Image(2011-06-01-upload.jpg)]] |
| 66 | |
| 67 | [[Image(2011-06-01-upload1.jpg)]] |