Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Communicate max slice expiration in SA get_version #512

Merged
merged 2 commits into from
Jun 8, 2016

Conversation

tcmitchell
Copy link
Member

Client programs have no way to no what the max slice expiration is. Add
the max expiration to the slice authority get_version response so that
clients can use the information to determine requested slice lifetimes.

Use the key '_GENI_MAX_SLICE_EXPIRATION_DAYS' and set the value
appropriately with the unit of days from the constant used in the SA.

Fixes #464

Client programs have no way to no what the max slice expiration is. Add
the max expiration to the slice authority get_version response so that
clients can use the information to determine requested slice lifetimes.

Use the key '_GENI_MAX_SLICE_EXPIRATION_DAYS' and set the value
appropriately with the unit of days from the constant used in the SA.
@tcmitchell tcmitchell added this to the 2.13 milestone Jun 8, 2016
@tcmitchell tcmitchell self-assigned this Jun 8, 2016
Handle some PEP 8 errors in slice authority while we're touching
the file. Still more to go.
@tcmitchell tcmitchell merged commit b7eceae into GENI-NSF:develop Jun 8, 2016
@tcmitchell tcmitchell deleted the iss464-max-slice-expiration branch June 8, 2016 13:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant