Custom Query (1408 matches)

Brecht discovered that the authority portion of sliver URNs from the ION (and therefore also MAX) AMs is the authority of the _slice_, where it should be the authority of the _AM_.

A sample sliver status showing the error:

              "geni_urn": "urn:publicid:IDN+ch.geni.net:CHtest+slice+st3",
              "geni_resources": [
                     {
                        "geni_urn": "urn:publicid:IDN+ch.geni.net:CHtest+sliver+st3_vlan_ion.internet2.edu-116301",
                        "geni_error": "",
                        "geni_status": "ready"
                        }
                     ],

The authority portion of the sliver URN should be that of the aggregate, so ion.internet2.edu The sliver name should be unique within the aggregate. In this case it names the circuit ID and aggregate and slice name, so that should be sufficient. Alternatively you could add the slice authority name there as part of the sliver name, making the full name: ch.geni.net.st3_vlan_ion.internet2.edu-116301 or some such.

If a request has multiple paths, a hop_exclusion_list on only one of the paths gets ignored.

Request RSpec is attached.

Failure case:

12:39:01 DEBUG   : Calling SCS with options {'geni_workflow_paths_merged': True, 'geni_routing_profile': {'link-gpo-stan': {'hop_inclusion_list': ['urn:publicid:IDN+instageni.stanford.edu+interface+procurve2:1.24.ion.salt.xe-0_1_1']}, u'link-stan-miss': {'hop_exclusion_list': [u'urn:publicid:IDN+al2s.internet2.edu+interface+sdn-sw.kans.net.internet2.edu:eth5/1:*=1164', u'urn:publicid:IDN+al2s.internet2.edu+interface+sdn-sw.sunn.net.internet2.edu:e5/1:*=1644']}}}
12:39:18 DEBUG   : SCS gave hop urn:publicid:IDN+instageni.rnet.missouri.edu+interface+procurve2:1.19.al2s.kans.eth5_1 suggested VLAN 1164, avail: '1161-1165'
12:39:18 DEBUG   : SCS gave hop urn:publicid:IDN+al2s.internet2.edu+interface+sdn-sw.kans.net.internet2.edu:eth5/1:* suggested VLAN 1164, avail: '1161-1165'
12:39:18 DEBUG   : SCS gave hop urn:publicid:IDN+al2s.internet2.edu+interface+sdn-sw.sunn.net.internet2.edu:e5/1:* suggested VLAN 1643, avail: '1640-1644,1650-1669'
12:39:18 DEBUG   : SCS gave hop urn:publicid:IDN+instageni.stanford.edu+interface+procurve2:1.24.al2s.sunn.e5_1 suggested VLAN 1643, avail: '1640-1644'

As you can see, the SCS picked a tag I specifically asked it not to.

Works:

12:30:08 DEBUG   : Calling SCS with options {'geni_workflow_paths_merged': True, 'geni_routing_profile': {u'link-gpo-stan': {'hop_exclusion_list': [u'urn:publicid:IDN+al2s.internet2.edu+interface+sdn-sw.kans.net.internet2.edu:eth5/1:*=1164', u'urn:publicid:IDN+al2s.internet2.edu+interface+sdn-sw.sunn.net.internet2.edu:e5/1:*=1644'], 'hop_inclusion_list': ['urn:publicid:IDN+instageni.stanford.edu+interface+procurve2:1.24.ion.salt.xe-0_1_1']}, u'link-stan-miss': {'hop_exclusion_list': [u'urn:publicid:IDN+al2s.internet2.edu+interface+sdn-sw.kans.net.internet2.edu:eth5/1:*=1164', u'urn:publicid:IDN+al2s.internet2.edu+interface+sdn-sw.sunn.net.internet2.edu:e5/1:*=1644']}}}
...
12:30:24 DEBUG   : SCS gave hop urn:publicid:IDN+instageni.rnet.missouri.edu+interface+procurve2:1.19.al2s.kans.eth5_1 suggested VLAN 1165, avail: '1161-1163,1165'
12:30:24 DEBUG   : SCS gave hop urn:publicid:IDN+al2s.internet2.edu+interface+sdn-sw.kans.net.internet2.edu:eth5/1:* suggested VLAN 1165, avail: '1161-1163,1165'
12:30:24 DEBUG   : SCS gave hop urn:publicid:IDN+al2s.internet2.edu+interface+sdn-sw.sunn.net.internet2.edu:e5/1:* suggested VLAN 1642, avail: '1640-1643,1650-1669'
12:30:24 DEBUG   : SCS gave hop urn:publicid:IDN+instageni.stanford.edu+interface+procurve2:1.24.al2s.sunn.e5_1 suggested VLAN 1642, avail: '1640-1643'

This is the desired behavior. The SCS excluded the tag that I said was unavailable from the vlanRangeRequest - both at the hop where I said it was unavailable, AND at the hop where that hop actually imports tags.

A circuit from Utah DDC to PG Utah shows no dependencies between the hops at the SCS. One of those should depend on the other, though it doesn't matter which.