RSpecs: Avoid 2 nodes with same interfaces/links

[ahelsing@bbn.com]

Current Ad shows several examples of 2 nodes with the exact same interfaces and links. That makes constructing a topology difficult.

EG: urn:publicid:IDN+geni-orca.renci.org+node+bbnvmsite.rdf#bbnvmsite/Domain/vm urn:publicid:IDN+geni-orca.renci.org+node+bbnvmsite.rdf#bbnvmsite/Domain/vlan

which both have interfaces: urn:publicid:IDN+geni-orca.renci.org+interface+bbnvmsite.rdf#Bbn/ExoGeni/TenGigabitEthernet/1/ethernet

and a link: urn:publicid:IDN+geni-orca.renci.org+interface+bbnvmsite.rdf#Bbn/ExoGeni/TenGigabitEthernet/1/ethernet urn:publicid:IDN+geni-orca.renci.org+interface+bbnNet.rdf#BbnNet/IBM/G8052/TenGigabitEthernet/1/1/ethernet

[ahelsing@bbn.com]

Ilia says remove the second Orca AM that's responsible for internal networking and is not of interest for stitching

[ahelsing@bbn.com]

This remains true - looking at the BBN rack Ad. The interfaces in 2 nodes are identical, and so the matching stitching port/links are identical. And I believe, as a result, there are duplicate links (ticket #65)

[ahelsing@bbn.com]

Ilia says:

The xcat nodes and the OpenStack nodes currently attach to the same group of ports that are not distinguished internally. So they are the same. The 'nodes' advertised in the ad rspec are essentially the 'openstack cloud' and the 'xcat cloud'. The user is not allowed to see inside of them, which is why the whole question of components is moot for us. ProtoGENi allows multiple components within an aggregate to produce the same resource type. In ORCA's current deployment in ExoGENI there is always only one component producing a particular resource type within a domain/site/rack.

So we have to live with it.