Opened 6 years ago

Closed 6 years ago

#1050 closed (invalid)

SCS request RSpec option not implemented.

Reported by: lnevers@bbn.com Owned by: xyang@maxgigapop.net
Priority: major Milestone:
Component: STITCHING Version: SPIRAL5
Keywords: Network Stitching Cc: Aaron Helsinger, tlehman@maxgigapop.net
Dependencies:

Description

Part of the stitching test plan verifies the SCS request RSpec options described at http://geni.maxgigapop.net/twiki/bin/view/GENI/NetworkStitchingAPI (geni_hold_path, geni_start_time, geni_end_time).

These functions are not yet available:

On 6/10/13 4:18 PM, Xi Yang wrote:

These three parameters are just placeholders for now. SCS does have advance scheduling capability in the core code to support start_time and end_time. I need to review these to see how to expose them in the GENI context. Resource holding is not implemented yet.

--Xi

Change History (4)

comment:1 Changed 6 years ago by xyang@maxgigapop.net

This is no defect. These params were placeholders for showing "possible" SCS options. We need to evaluate whether we need them before trying to "fix" them.

comment:2 Changed 6 years ago by lnevers@bbn.com

This ticket was written to track the fact that an item in the Network Stitching Test plan could not be tested. If this function is planned post-gec17, please let me know and I will move the validation of this feature to the post-gec17 section of the planned testing (and close this ticket).

comment:3 Changed 6 years ago by xyang@maxgigapop.net

Cc: Aaron Helsinger tlehman@maxgigapop.net added

yes. This is definitely post-gec17.

We might not need SCS to maintain states. So geni_hold_path could be irrelevant. We may need advance scheduling but not in near future.

comment:4 Changed 6 years ago by lnevers@bbn.com

Resolution: invalid
Status: newclosed

Updated test plan to check SCS request RSpec options after GEC17. Closing ticket.

Note: See TracTickets for help on using tickets.