| Table of Contents | ||||
|---|---|---|---|---|
|
VM01: Time-
...
bounded “sale” rate
...
Summary
Resource Providers (RPs) should be able to set a “sale” price for a limited amount of time, with the goal of attracting users. This would be defined for a certain range of dates that would automatically revert at the end of the date range. For this to be useful, the allocation-request interface will need to highlight the “sale” price so that users are aware of it.
Status
Proposed
Proposed by: IU, PSC
Suggested Requirements:
...
Provide RPs with a UI that shows the regular exchange rate, and lets them enter a different exchange rate and start/end dates. During that time, the sale exchange rate takes precedence.
...
RP User Experience:
Resource Providers will log into a RP-specific page that lists all their resources with their baseline exchange rates.
RPs will have a interface that allows them to set a new temporary exchange rate, along with a date range that this exchange rate will be in effect.
(optional) RPs will be able to specify a short description of why the exchange rate is temporarily changed.
At the end of the specified time period, the exchange rate will revert to the default baseline exchange rate.
Researcher User Experience:
Upon viewing the “exchange credits” interface, some sort of visual indicator should be presented to the researcher that the specified resource has a temporarily discounted rate.
Additional details should be available to to the user that wishes to learn more (timespan of the discount, current rate, original rate, etc).
Once an exchange is requested with the discounted rate, that will be “locked in” for that exchange request, as long as the exchange request is submitted during the discounted time period.
Tagged allocations with special rates (for preemptible instances, different priority queues)
...