airavata-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Christie (Jira)" <j...@apache.org>
Subject [jira] [Commented] (AIRAVATA-3126) Implement compute resource reservation addition
Date Thu, 27 Feb 2020 15:29:00 GMT

    [ https://issues.apache.org/jira/browse/AIRAVATA-3126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17046735#comment-17046735
] 

Marcus Christie commented on AIRAVATA-3126:
-------------------------------------------

I discussed the above questions with Eroma. Here's what we decided on each:

bq. * reservations apply to a compute resource and a queue, right? Can a reservation apply
to more than one queue on a compute resource?

Yes, a reservation is applies to one or more queue/partitions on a compute resource

bq. * for that matter can a reservation apply to multiple compute resources?

No

bq. * can reservations have multiple date ranges or is there only the single start date/end
date range?

No, only the single start date/end date range.


> Implement compute resource reservation addition 
> ------------------------------------------------
>
>                 Key: AIRAVATA-3126
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-3126
>             Project: Airavata
>          Issue Type: Sub-task
>          Components: Django Portal
>    Affects Versions: 0.18
>         Environment: https://django.staging.seagrid.org
>            Reporter: Eroma
>            Assignee: Marcus Christie
>            Priority: Minor
>
> # In PGA portal implementation for a compute resource we could add a reservation
>  # Reservation is to have a dedicate computing time in a cluster queue/partition
>  # As for the existing PGA implementation we could provide a reservation name and a start
and end time for the particular reservation. 
>  # In Django the implementation does not exists.
>  # First we should have the previous implementation done in Django portal
>  # Next step would be to improve it by enabling
>  # Adding a reservation for a particular cluster queue/partition
>  # Then we should also be able to add multiple reservations for a particular queue/partition.
These multiples will have different reservation names and start and end dates.
> h5. Data Model
> - GroupComputeResourcePreference
> -- one or more Reservations
> --- list of queues
> --- reservation name
> --- start date
> --- end date
> A GroupComputeResourcePreference can have one or more Reservation records. Each Reservation
is applicable to one or more queue/partitions for the GroupComputeResourcePreference's compute
host. The Reservation also has a name, start date and end date.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message