Changes between Version 38 and Version 39 of KOGEMINITesting
- Timestamp:
- 05/31/13 08:38:21 (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
KOGEMINITesting
v38 v39 324 324 325 325 -It would be helpful to have instruction on setting up the PATH in the beginning and knowing where it should go.[[BR]] 326 -When it has the user decrypt their key in step 3, the key name from Portal doesn't match the example.[[BR]]327 - Unclear where Flack should be launched from. With the Portal account I had a difficult time launching Flack from protogeni.net/flack. So I launched it from the Portal.[[BR]]326 -When the tutorial has the user decrypt their key in step 3, the key name from Portal doesn't match the example. However, we try to decrypt it before going into the omni_config file and seeing that they are different.[[BR]] 327 -It is unclear where Flack should be launched from. With the Portal account I had a difficult time launching Flack from protogeni.net/flack. I launched it from the Portal because that was easiest.[[BR]] 328 328 -In step 4 where it states "Click on the "i" on each node to configure additional properties, such as the node name and the desired IP addresses", it would be nice if it told you to click on the grey link tab after initially clicking the "i".[[BR]] 329 329 -In step 4 when it instructs on how to enable GEMINI it says: "To allow for GEMINI instrumentation, enable the GEMINI extensions in the right-most tab as shown in the screenshot." I think it would be clearer if it also acknowledged that the icon is a yellow puzzle piece or had an arrow on the screenshot.[[BR]] 330 330 -When it's time to renew a slice Omni uses your default project. If that isn't the project you created your slice in, how do you switch projects?[[BR]] 331 331 -When I tried to call ./gdesktop-init.py I had to install paramiko using the command "sudo apt-get install python_paramiko".[[BR]] 332 -When I tried to call ./gdesktop-init.py again I had to use:./gdesktop-init.py -n KOPhoebusTut -f ~/.ssl/geni_cert_portal.pem -k ~/.ssh/geni_key .There is either a different behavior with the GENI CH certificate or the instructions are not quite right. The private cert in the CH cert file does not work to SSH into the nodes.333 332 -When I tried to call ./gdesktop-init.py again I had to add -k ~/.ssh/geni_key to the end of the command(making: ./gdesktop-init.py -n KOPhoebusTut -f ~/.ssl/geni_cert_portal.pem -k ~/.ssh/geni_key). There is either a different behavior with the GENI CH certificate or the instructions are not quite right. The private cert in the CH cert file does not work to SSH into the nodes. 333