Custom Query (138 matches)

Configure an IP address which can be used for testing connectivity to the BBN ExoGENI rack on shared OpenFlow-controlled VLAN 1750.

The serial consoles of the two BBN rack switches, 8052.bbn.xo and 8264.bbn.xo, should be reachable from bbn-hn.

Using version??? on 04/25/2012.

While creating a sliver at the BBN SM using an RSpec that includes a resource from the component_manager_id "urn:publicid:IDN+rcivmsite+authority+cm"(RENCI Aggregate), an exception was reported, which does not give a good insight into the source of the problem. Here is the error:

$ ./src/omni.py -a https://bbn-hn.exogeni.gpolab.bbn.com:11443/orca/xmlrpc createsliver lnevers6orca orca-2site.rspec        
INFO:omni:Loading config file omni_config
INFO:omni:Using control framework pgeni
INFO:omni:Slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+lnevers6orca expires within 1 day on 2012-04-25 22:43:34 UTC
INFO:omni:Creating sliver(s) from rspec file orca-2site.rspec for slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+lnevers6orca
INFO:omni:Asked https://bbn-hn.exogeni.gpolab.bbn.com:11443/orca/xmlrpc to reserve resources. Result:
INFO:omni:<!-- Reserved resources for:
	Slice: lnevers6orca
	At AM:
	URL: https://bbn-hn.exogeni.gpolab.bbn.com:11443/orca/xmlrpc
 -->
INFO:omni: ------------------------------------------------------------
INFO:omni: Completed createsliver:

  Options as run:
		aggregate: https://bbn-hn.exogeni.gpolab.bbn.com:11443/orca/xmlrpc
		framework: pgeni
		native: True

  Args: createsliver lnevers6orca orca-2site.rspec

  Result Summary: Slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+lnevers6orca expires within 1 day(s) on 2012-04-25 22:43:34 UTC
Asked https://bbn-hn.exogeni.gpolab.bbn.com:11443/orca/xmlrpc to reserve resources. No manifest Rspec returned. Other Exception: java.lang.Exception: ERROR: Unknown slice urn urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+lnevers6orca 
INFO:omni: ============================================================

Replacing the component_manager_id "urn:publicid:IDN+rcivmsite+authority+cm" with the correct one "urn:publicid:IDN+bbnvmsite+authority+cm" resolves the failure.

The exception should be handled more gracefully.