Custom Query (5 matches)
Results (1 - 3 of 5)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#6 | fixed | lamp-sendmanifest.py does not handle flack extensions | ||
Description |
If the gemini slice is created using FLACK, the manifest has some FLACK extensions in it too which are all legal. But the "lamp-sendmanifest.py" script that the bootstrap procedure calls breaks on those FLACK specific extension Outoput snip ======== Received: <SOAP-ENV:Envelope xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
<nmwg:message xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/" id="message.7583613" type="ErrorResponse"><nmwg:metadata id="metadata.12781939"><nmwg:eventType>error.transport.parse_error</nmwg:eventType></nmwg:metadata><nmwg:data metadataIdRef="metadata.12781939" id="data.8233425"><nmwgr:datum xmlns:nmwgr="http://ggf.org/ns/nmwg/result/2.0/">Error parsing request: Parse failed: :62: namespace error : Namespace prefix flack on interface_info is not defined
:92: namespace error : Namespace prefix flack on interface_info is not defined
:102: namespace error : Namespace prefix flack on interface_info is not defined
:132: namespace error : Namespace prefix flack on interface_info is not defined
</nmwgr:datum></nmwg:data></nmwg:message> </SOAP-ENV:Body> </SOAP-ENV:Envelope> |
|||
#4 | fixed | Investigate bottlenecks in instrumentize process | ||
Description |
The instrumentize script is reportedly taking about 30 minutes to complete. This ticket will track the investigation of what is taking the majority of the time in hopes of further optimizing for the tutorial. I am assigning to Hussam to begin because he initially reported the 30 minutes. Reassign as necessary. |
|||
#3 | fixed | Main page only shows one node (PCA) | ||
Description |
Using the same 4-node slice with MPs PCA, PCB, and PCC. When I click on the "Main page" button for the GN, only PCA shows up in the left nav bar. |