Custom Query (121 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (31 - 33 of 121)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
Ticket Resolution Summary Owner Reporter
#113 fixed sliver local_name is wrong pbohan@bbn.com sedwards@bbn.com
Description

My output is generating funny URNs:

		<sliver approved="0" created="1348885835" creator="urn:publicid:IDN+pgeni.gpolab.bbn.com+user+lnevers" expires="1350091835" local_name="urn:publicid:IDN+gmoc.geni.net+sliver+urn:publicid:IDN+exogeni.net:bbnvmsite+sliver+2acb3763-d043-4296-8ba5-b7af98eb3c8a#geni2" slice_urn="urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+acclne-2029400" slice_uuid="739e7b11-3318-4951-94de-3985fa1669af" state="Unknown" uuid="">
			<resource_mapping local_name="urn:publicid:IDN+gmoc.geni.net+sliver+urn:publicid:IDN+exogeni.net:bbnvmsite+sliver+2acb3763-d043-4296-8ba5-b7af98eb3c8a#geni2" resource="urn:publicid:IDN+exogeni.net:bbnvmsite+node+orca-vm-cloud" type="vm"/>

In particular, notice:

local_name="urn:publicid:IDN+gmoc.geni.net+sliver+urn:publicid:IDN+exogeni.net:bbnvmsite+sliver+2acb3763-d043-4296-8ba5-b7af98eb3c8a#geni2"

See also #119.

#112 fixed Aggregates referenced by ID cause backend to try (and fail) to update the Aggregate somebody sedwards@bbn.com
Description

Referencing an Aggregate by ID causes the back end to die with the following error:

DBD::mysql::st execute failed: Column 'version' cannot be null at xchange2db3 line 725.
Could not execute statement INSERT INTO aggregate_instantiation (aggregate_id, end_version_id, start_version_id, version, pop_id, organization_id) VALUES (?, -1, ?, ?, ?, ?).
#109 fixed gmoc.py serializes the slice creator and primary_contact as e-mail addresses rather than URNs somebody chaos@bbn.com
Description

Slice submission using gmoc.py is serialized as:

<slice
  created="1349214385"
  creator="chaos@bbn.com"
  expires="1349217985"
  operator="urn:publicid:IDN+gmoc.geni.net+organization+BBN"
  primary_contact="chaos@bbn.com"
  urn="urn:publicid:IDN+pgeni1.gpolab.bbn.com+slice+ecgtest"
  uuid="b3ec2d36-0cb0-11e2-adf1-000c29b09582"
/>

Once 105 is fixed, URNs will be the right way to uniquely identify people, and we will need to encode slice creator and contact as URNs rather than as e-mail addresses.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
Note: See TracQuery for help on using queries.