15 | | '''Note 5:''' ExoGENI supports two sliver_types that map to a dedicated PC and they are: {{{<sliver_type name="raw-pc"/>}}} and {{{<sliver_type name="ExoGENI-M4"/> }}} |
16 | | '''Note 6:''' ExoGENI will not assign IP addresses if they are not specified in the RSpec. |
17 | | '''Note 7:''' Once ExoGENI assigns an IP address on the node it cannot be changed. The NEuca agent continously monitors the interfaces and reset the IP settings if changed. |
18 | | '''Note 8:''' If interfaces are configure and IP addresses are not specified on ExoGENI, the nodes only show eth0 in the ifconfig output, but eth1 is initialized and can be configured and brought up with a user-specified address which is not reset by the NEuca agent. |
19 | | '''Note 9:''' InstaGENI links that use GRE tunnels must specify and IP address in the RSpec, an address will not be automatically assigned in this case. |
20 | | '''Note 10:''' Unlike ExoGENI, for InstaGENI aggregates the request is submitted at each of the aggregate in the RSpec, and there is a limited amount of delay allowed between the requests to each aggregates. (few minutes) |
21 | | '''Note 11:''' The shared VLAN link definition in InstaGENI require one entry for each side of the VLAN. Combining the two link into one link entry fails. |
22 | | '''Note 12:''' There additional variables that are supported for postBootScript via flukes which are not supported via the GENI AM API. |
23 | | '''Note 13:''' Once the allocated node is up, you may view the results of the post boot script with the ''neuca-user-script'' command. |
24 | | '''Note 14:''' ExoGENI node groups are not supported via the GENI AM API, only via flukes. |
| 15 | - '''Note 5:''' ExoGENI supports two sliver_types that map to a dedicated PC and they are: {{{<sliver_type name="raw-pc"/>}}} and {{{<sliver_type name="ExoGENI-M4"/> }}} |
| 16 | |
| 17 | - '''Note 6:''' ExoGENI will not assign IP addresses if they are not specified in the RSpec. |
| 18 | |
| 19 | - '''Note 7:''' Once ExoGENI assigns an IP address on the node it cannot be changed. The NEuca agent continously monitors the interfaces and reset the IP settings if changed. |
| 20 | |
| 21 | - '''Note 8:''' If interfaces are configure and IP addresses are not specified on ExoGENI, the nodes only show eth0 in the ifconfig output, but eth1 is initialized and can be configured and brought up with a user-specified address which is not reset by the NEuca agent. |
| 22 | |
| 23 | - '''Note 9:''' InstaGENI links that use GRE tunnels must specify and IP address in the RSpec, an address will not be automatically assigned in this case. |
| 24 | |
| 25 | - '''Note 10:''' Unlike ExoGENI, for InstaGENI aggregates the request is submitted at each of the aggregate in the RSpec, and there is a limited amount of delay allowed between the requests to each aggregates. (few minutes) |
| 26 | |
| 27 | - '''Note 11:''' The shared VLAN link definition in InstaGENI require one entry for each side of the VLAN. Combining the two link into one link entry fails. |
| 28 | |
| 29 | - '''Note 12:''' There additional variables that are supported for postBootScript via flukes which are not supported via the GENI AM API. |
| 30 | |
| 31 | - '''Note 13:''' Once the allocated node is up, you may view the results of the post boot script with the ''neuca-user-script'' command. |
| 32 | |
| 33 | - '''Note 14:''' ExoGENI node groups are not supported via the GENI AM API, only via flukes. |