Custom Query (98 matches)

Successfully created a sliver IG-EXP-6-exp2 at the Utah InstaGENI FOAM, which is attached to this ticket.

After the sliver was approved, checked the sliverstatus which showed that the sliver was "configuring" and "approved" for the past 30 minutes.

INFO:omni:{
  "geni_status": "configuring", 
  "geni_urn": "urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+IG-EXP-6-exp2:8c6ca8df-757b-4628-aae7-52a81f64cbc6", 
  "foam_pend_reason": null, 
  "foam_expires": "2013-01-11 00:00:00+00:00", 
  "geni_resources": [
    {
      "geni_urn": "urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+IG-EXP-6-exp2:8c6ca8df-757b-4628-aae7-52a81f64cbc6", 
      "geni_error": "", 
      "geni_status": "configuring"
    }
  ], 
  "foam_status": "Approved"
}

Trying to set up a sliver (IG-EXP-7) that has 3 VMs at GPO and 3 VMs at Utah, with two GRE tunnels between the sites. Each attempt to set up a sliver at GPO fails:

WARNING:omni: Failed CreateSliver for slice IG-EXP-7 at http://instageni.gpolab.bbn.com/protogeni/xmlrpc/am/2.0.  
Error from Aggregate: code 2. protogeni AM code: 2: Could not create aggregate for
 link-0 (PG error log: urn:publicid:IDN+instageni.gpolab.bbn.com+log+15496).

Each attempt at Utah fails with the following:

WARNING:omni:Failed CreateSliver for slice IG-EXP-7 at http://utah.geniracks.net/protogeni/xmlrpc/am/2.0.  
Error from Aggregate: code 2. protogeni AM code: 2: Could not create aggregate for 
link-0 (PG error log: urn:publicid:IDN+utah.geniracks.net+log+86718)

The Rspec passes rspeclint and is attached. Additionally, I am attaching a diagram of the topology.

Testing a scenario where GPO campus resources are used through the rack to access VLAN 1750 and GPO IG rack nodes are requested for VLAN 1750. No communication is available.

This issue is related to the email thread named "BBN VLAN IDs, Internet2 and NLR endpoints" and details for expected default use of port 23 and port 24 for VLAN 1750.

These are the last question from Josh:

JBS> Are we also on the same page about how VLAN 1750 in particular should
JBS> work, i.e. that it should be permanently on both ports 23 and 24, so
JBS> that if experimenters create a sliver with a node that links to it,
JBS> they automatically get linked to both of the ways out of the switch?

LS> Okay, this should be setup now. Let me know if you have problems with it.

Luisa and I finally tried this out, and it doesn't seem to be working as
expected.

A while back, I had created a sliver linking port 23 to VLAN 1750, this
one that Leigh had sent along:

  <?xml version="1.0" encoding="UTF-8"?>
  <rspec xmlns="http://www.geni.net/resources/rspec/3"
         xmlns:xs="http://www.w3.org/2001/XMLSchema-instance"
         xmlns:sharedvlan="http://www.geni.net/resources/rspec/ext/shared-vlan/1"
         xs:schemaLocation="http://www.geni.net/resources/rspec/3
             http://www.geni.net/resources/rspec/3/request.xsd
             http://www.geni.net/resources/rspec/ext/shared-vlan/1
             http://www.geni.net/resources/rspec/ext/shared-vlan/1/request.xsd"
         type="request">
    <node client_id="campus-port" component_id="urn:publicid:IDN+instageni.gpolab.bbn.com+node+interconnect-campus" exclusive="false">
      <sliver_type name="emulab-connect" />
      <interface client_id="campus-port:if0" />
    </node>
    <link client_id="campus-link">
      <bandwidth>100000</bandwidth>
      <interface_ref client_id="campus-port:if0" />
      <sharedvlan:link_shared_vlan name="mesoscale-openflow" />
    </link>
  </rspec>

That was still there, and Luisa was able to ping between a "campus
resource" machine, connected via that port, and a host in the rack.

I then deleted my sliver, to confirm that it's not necessary any more, but
then Luisa wasn't able to ping between her hosts any more.

Any ideas?

                                      -Josh (jbs@bbn.com)

Writing ticket to track resolution of this issue, which is blocking to IG-EXP-5 test case.