airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nipurn Doshi <nido...@umail.iu.edu>
Subject Re: Concerns with Gateway Interface
Date Thu, 11 Dec 2014 19:31:32 GMT
I think that would work. Not allowing users with same queue name has been
taken care of, in the queue creation validation. This composite primary key
will have to be added to the queue object in the database+repo.

On Thu, Dec 11, 2014 at 2:24 PM, Shameera Rathnayaka <shameerainfo@gmail.com
> wrote:

>
>
> On Fri, Dec 12, 2014 at 12:45 AM, Nipurn Doshi <nidoshi@umail.iu.edu>
> wrote:
>
>> Hi Devs,
>>
>> I have a couple of concerns that I wanted to share -
>>
>>    - Queue objects in a Compute Resources do not have a unique primary
>>    key. Currently, queue names act as a primary key and the name cannot be
>>    changed after defining it once. What can be done for this?
>>
>>
> ​Can't we use computeResourcePrimary key + queue name as composite primary
> key? Because queue name can be duplicate across computeResources but one
> computeResource can't have two queues with the same name.
> ​
>
>
>>
>>    - An API is required that can help to get App Deployments by passing
>>    App Module Id and Compute Resource Id. Currently the interface shows all
>>    App Deployments and each deployment has to be checked out which module and
>>    resource it is connected to.
>>
>>
>> --
>> -Regards,
>> Nipurn Doshi
>>
>
>
>
> --
> Best Regards,
> Shameera Rathnayaka.
>
> email: shameera AT apache.org , shameerainfo AT gmail.com
> Blog : http://shameerarathnayaka.blogspot.com/
>



-- 
-Sincerely,
Nipurn Doshi

Mime
View raw message