Opened 6 years ago

Closed 6 years ago

#1400 closed (fixed)

AL2S AM cannot handle disk_image elements with URL attributes

Reported by: Owned by:
Priority: critical Milestone:
Component: STITCHING Version: SPIRAL7
Keywords: GENI Network Stitching Cc:


I was standing up a stitched slice between nysernet-ig and illinois-ig with an RSpec that used to work with the ION AM. As of the transition of nysernet-ig over to AL2S, stitching is now required to go through AL2S for this slice.

When stitcher calls createsliver on the AL2S AM, it fails with the following error:

22:54:00 ERROR   :  {'output': "Element '{}disk_image', attribute 'url': The attribute 'url' is not allowed., line 19", 'code': {'geni_code': 1}}

Any disk_image elements in the RSpec are destined for other component managers within the GENI racks, and should therefore be ignored by the AL2S AM. I am attaching my request RSpec and the expanded RSpec.

Attachments (2)

fsfw-two-site-request.xml (10.7 KB) - added by 6 years ago.
Original request RSpec
fsfw-expanded-request-rspec.xml (14.6 KB) - added by 6 years ago.
Expanded request RSpec

Download all attachments as: .zip

Change History (6)

Changed 6 years ago by

Attachment: fsfw-two-site-request.xml added

Original request RSpec

Changed 6 years ago by

Expanded request RSpec

comment:1 Changed 6 years ago by

It looks like this problem is happening for all FOAM aggregates. This is a big issue, because the AL2S AM will be a part of the stitching workflow most of the time, and it means that experimenters cannot use custom images referenced by URL with stitching.

comment:2 Changed 6 years ago by

I don't know the ins-and-outs of FOAM, but maybe updating the schemas could fix this? The schemas in bitbucket's FOAM repo for barnstomer are mostly timestamped 2012. The "DiskImageContents" listed under do not include a URL attribute, but they do include a URL attribute for the current authoritative location of the same schema:

comment:3 Changed 6 years ago by

Priority: majorcritical

comment:4 Changed 6 years ago by

Resolution: fixed
Status: newclosed

Luke made a quick fix of pulling down the latest schema from, which fixed things up. It took me a while to set up a successful test slice due to failed slivers in the racks I was using, but I was eventually able to verify that the fix is working.

This should be all set!

Note: See TracTickets for help on using tickets.