Issue 97 in ogf-nsi-project: Add ServiceType element to reservation criteria.
Status: Accepted Owner: jmacauley Labels: Type-Defect Priority-Medium FoundInVersion-2.0 FixedInVersion-2.0 New issue 97 by jmacauley: Add ServiceType element to reservation criteria. http://code.google.com/p/ogf-nsi-project/issues/detail?id=97 As part of service definition decoupling from the NSI CS core protocol we need to add a ServiceType string value to reservation criteria to indicate the type of service being requested. This string value will correspond to the service definition template for the service being offered. Based on this ServiceType string value, and NSA will be able to determine the serviceAttributes required to meet the service request, and look up the service definition template. The current ReservationRequestCriteriaType definition is: <xsd:complexType name="ReservationRequestCriteriaType"> <xsd:sequence> <xsd:element name="schedule" type="tns:ScheduleType" minOccurs="0" /> <xsd:element name="bandwidth" type="xsd:int" minOccurs="0" /> <xsd:element name="serviceAttributes" type="ftypes:TypeValuePairListType" minOccurs="0" /> <xsd:element name="path" type="tns:PathType" minOccurs="0" /> </xsd:sequence> <xsd:attribute name="version" type="xsd:int" use="optional" /> </xsd:complexType> This will be modified to: <xsd:complexType name="ReservationRequestCriteriaType"> <xsd:sequence> <xsd:element name="schedule" type="tns:ScheduleType" minOccurs="0" /> <xsd:element name="serviceType" type="xsd:string" /> <xsd:element name="bandwidth" type="xsd:int" minOccurs="0" /> <xsd:element name="serviceAttributes" type="ftypes:TypeValuePairListType" minOccurs="0" /> <xsd:element name="path" type="tns:PathType" minOccurs="0" /> </xsd:sequence> <xsd:attribute name="version" type="xsd:int" use="optional" /> </xsd:complexType> All other types containing criteria will also be modified to contain the serviceType element. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings
Comment #1 on issue 97 by thost...@gmail.com: Add ServiceType element to reservation criteria. http://code.google.com/p/ogf-nsi-project/issues/detail?id=97 Isn't this suggestion different than the one presented in NSI_Service_Decoupling.pdf? There the criteria was essentially a schedule along with a bunch of serviceAttributes -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings
Comment #2 on issue 97 by thost...@gmail.com: Add ServiceType element to reservation criteria. http://code.google.com/p/ogf-nsi-project/issues/detail?id=97 Hi, so the current suggestion: <criteria version="1"> <schedule> <startTime>2013-‐09-‐30T09:30:10Z</startTime> <endTime>2013-‐09-‐30T10:30:10Z</endTime> </schedule> <serviceAttributes> <p2p:p2pService> .. Could we consider dumping the serviceAttributes alltogether, and going for something like this: <criteria version="1"> <schedule> <startTime>2013-‐09-‐30T09:30:10Z</startTime> <endTime>2013-‐09-‐30T10:30:10Z</endTime> </schedule> <p2p:p2pService> ... I.e., having a single ANY element. The QName of the element would define the service request type. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings
Comment #3 on issue 97 by jmacauley: Add ServiceType element to reservation criteria. http://code.google.com/p/ogf-nsi-project/issues/detail?id=97 In response to comment #1 - I added the serviceType issue separately from the removal of service parameters into serviceAttributes. In response to comment #2 - Yes we could definitely do this, but I thought encapsulating the elements in the serviceAttributes sub element would provide a cleaner separation. I am okay with this change. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings
Updates: Status: Fixed Comment #4 on issue 97 by jmacauley: Add ServiceType element to reservation criteria. http://code.google.com/p/ogf-nsi-project/issues/detail?id=97 This issue was closed by revision r77. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings
participants (1)
-
ogf-nsi-project@googlecode.com