Opened 11 years ago
Last modified 10 years ago
#1038 new
Manifest rspec for PG and IG does not pass rspeclint
Reported by: | lnevers@bbn.com | Owned by: | duerig@flux.utah.edu |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | STITCHING | Version: | SPIRAL5 |
Keywords: | Network Stitching | Cc: | duerig@flux.utah.edu, Aaron Helsinger |
Dependencies: |
Description
Running rspeclint on a stitched sliver manifest reports failures for PG and IG:
$ rspeclint stitch-gpo-utah-manifest-rspec-www-emulab-net-protogeni.xml Line 28: Failed validation with root at element: Schemas validity error : Element '{http://hpn.east.isi.edu/rspec/ext/stitch/0.1/}capabilities': This element is not expected. Expected is ( {http://hpn.east.isi.edu/rspec/ext/stitch /0.1/}switchingCapabilityDescriptor ).Schemas validity error : Element '{http://hpn.east.isi.edu/rspec/ext/stitch/0.1/}capabilities': This element is not expected. Expected is ( {http://hpn.east.isi.edu/rspec/ext/stitch /0.1/}switchingCapabilityDescriptor ). : stitching $ rspeclint stitch-gpo-utah-manifest-rspec-geni-am-net-internet2-edu.xml lnevers@arendia:~/gcf-2.3.1/stitch-test/adman$ rspeclint stitch-gpo-utah-manifest-rspec-utah-geniracks-net-protogeni.xml Ignoring node rs:vnode with unknown namespace http://www.protogeni.net/resources/rspec/ext/emulab/1 Line 28: Failed validation with root at element: Schemas validity error : Element '{http://hpn.east.isi.edu/rspec/ext/stitch/0.1/}capabilities': This element is not expected. Expected is ( {http://hpn.east.isi.edu/rspec/ext/stitch /0.1/}switchingCapabilityDescriptor ). Schemas validity error : Element '{http://hpn.east.isi.edu/rspec/ext/stitch/0.1/}capabilities': This element is not expected. Expected is ( {http://hpn.east.isi.edu/rspec/ext/stitch /0.1/}switchingCapabilityDescriptor ). : stitching
Attaching both manifests.
Attachments (3)
Change History (9)
comment:1 Changed 11 years ago by
Component: | GPO → STITCHING |
---|---|
Keywords: | Network Stitching added |
Changed 11 years ago by
Attachment: | stitch-gpo-utah-manifest-rspec-www-emulab-net-protogeni.xml added |
---|
Changed 11 years ago by
Attachment: | stitch-gpo-utah-manifest-rspec-utah-geniracks-net-protogeni.xml added |
---|
comment:2 Changed 11 years ago by
Changed 11 years ago by
Attachment: | ln-ext1-createsliver-request-11-emulab-net.xml added |
---|
comment:3 Changed 11 years ago by
Cc: | duerig@flux.utah.edu Aaron Helsinger added |
---|
comment:4 Changed 11 years ago by
Owner: | changed from somebody to duerig@flux.utah.edu |
---|
comment:5 Changed 10 years ago by
There is still be an issue with manifest files. The rspeclint for a GPO IG to PG Utah Manifest report the same errors as in the initial problem report.
For PG Utah:
$ rspeclint ig-gpo-pg-utah-manifest-rspec-emulab-net.xml Ignoring node rs:vnode with unknown namespace http://www.protogeni.net/resources/rspec/ext/emulab/1
For GPO Lab:
$ rspeclint ig-gpo-pg-utah-manifest-r spec-instageni-gpolab-bbn-com.xml Ignoring node rs:vnode with unknown namespace http://www.protogeni.net/resources/rspec/ext/emulab/1
comment:6 Changed 10 years ago by
On 6/30/14, 1:05 PM, Jonathon Duerig wrote:
This is a warning and not a fatal error. But I think that this is something that should be fixed in your invocation of rspeclint. Normally, you should be invoking it with the namespace/schema-location pairs that you know are canonical (either a local cache or the web addresses).
This error means that you are relying on the fallback in rspeclint where it inspects the rspec itself to see what it claims the pairs should be. Using this fallback mechanism is less reliable because it means that if the rspec is bogus and points to a bogus schema inside of it, rspeclint will still let it through as valid.
What are the values for the namespace/schema-location pair to be used for rspeclint to pass?
On 6/6/13 12:43 PM, Jonathon Duerig wrote:
On 6/6/13 12:52 PM, Luisa Nevers wrote:
Attaching the Stitcher request rspec.