| 31 | | || 4 || [[Color(orange,Blocked)]] || || || blocked on sudo access to the control host || |
| 32 | | || 5 || [[Color(orange,Blocked)]] || || || blocked on access to an allocated OpenVZ host (e.g. via boss) || |
| 33 | | || 6 || [[Color(orange,Blocked)]] || || || blocked on access to the control switch || |
| | 31 | || 4 || [[Color(orange,Blocked)]] || || || blocked on sudo access to foam VM || |
| | 32 | || 5 || [[Color(orange,Blocked)]] || || || blocked on sudo access to the control host || |
| | 33 | || 6 || [[Color(orange,Blocked)]] || || || blocked on access to an allocated OpenVZ host (e.g. via boss) || |
| | 34 | || 7 || [[Color(orange,Blocked)]] || || || blocked on access to the control switch || |
| 106 | | == Step 4: identify network-listening software on the control host == |
| | 107 | == Step 4: identify network-listening software on the FlowVisor node == |
| | 108 | |
| | 109 | '''Using:''' |
| | 110 | * Using netstat, enumerate processes on flowvisor which listen for network connections from outside the node |
| | 111 | * For each process found: |
| | 112 | * Use the command-line to determine what executable file is running |
| | 113 | * Use dpkg commands to determine whether the executable file is part of a Debian package |
| | 114 | * Otherwise, use documentation or iterate with the InstaGENI team to determine the origin of the software |
| | 115 | * For each Debian package found, identify a location from which the source package can be obtained |
| | 116 | * For each non-Debian package found, identify a location from which the source code for that version can be obtained. |
| | 117 | |
| | 118 | '''Verify:''' |
| | 119 | * The source of each network-listening file can be identified |
| | 120 | * Source code or a source package can be identified for each Debian-sourced package |
| | 121 | * The source code and identifiable version (e.g. a git tag) can be found for each non-Debian software source |
| | 122 | |
| | 123 | == Step 5: identify network-listening software on the control host == |
