airavata-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chathuri Wimalasena (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AIRAVATA-1477) Host Aliases and IpAddresses not getting saved in Compute Resource Object
Date Fri, 24 Oct 2014 17:54:35 GMT

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

Chathuri Wimalasena commented on AIRAVATA-1477:
-----------------------------------------------

We change datatype from set to list.

> Host Aliases and IpAddresses not getting saved in Compute Resource Object
> -------------------------------------------------------------------------
>
>                 Key: AIRAVATA-1477
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-1477
>             Project: Airavata
>          Issue Type: Bug
>          Components: Application Catalog
>            Reporter: Nipurn Doshi
>            Assignee: Chathuri Wimalasena
>            Priority: Minor
>
> Hi,
> I'm trying to create interfaces to register and modify a Compute Resource using PHP.
When I use the following functions of AiravataClient -
> $airavataclient->registerComputeResource() 
> or
> $airavataclient->updateComputeResource() 
> the Compute Resource object which gets returned contains "hostAliases" and "ipAddresses"
 instead of having actual values in the array , actually contains only value - "1" in every
value of the array.
> An example Compute Resource object to understand it better -
> Airavata\Model\AppCatalog\ComputeResource\ComputeResourceDescription Object ( [computeResourceId]
=> abcd_ec3929da-a592-4f04-98d9-db7d934e3c69 [hostName] => some host 1010 [hostAliases]
=> Array ( [1] => 1 [0] => 1 ) [ipAddresses] => Array ( [0] => 1 ) [resourceDescription]
=> [batchQueues] => [fileSystems] => Array ( ) [jobSubmissionInterfaces] => [dataMovementInterfaces]
=> )
> Please let me know what can I do to resolve this issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message