[Nsi-wg] Issue 57 in ogf-nsi-project: should we define an NSI-UNI?
ogf-nsi-project at googlecode.com
ogf-nsi-project at googlecode.com
Thu Feb 16 07:24:30 EST 2012
Status: Accepted
Owner: jmacau... at gmail.com
Labels: Type-Defect Priority-Medium FoundInVersion-1.1 FixedInVersion-2.0
New issue 57 by guy.robe... at gmail.com: should we define an NSI-UNI?
http://code.google.com/p/ogf-nsi-project/issues/detail?id=57
Description of Issue:
The NSI WSDL has become complex leading to the observation that application
developers are likely to be discouraged from implementing NSI apps. Also,
current NSI design is not firewall friendly. A possible solution to this
would be to define a simplified NSI to be used as a UNI.
Discussion of Issue:
John MacAuley has proposed the following solution:
Define a simplified client-specific NSI-CS protocol interface (UNI)
o A simplified subset of the existing NSI-CS capabilities.
o Firewall safe.
This interface should use current best practices for client API development:
o RESTful definition.
o JSON/XML data representations.
o Useable from web-based clients.
Resolution of Issue:
More information about the nsi-wg
mailing list