cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Sorensen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-5843) registering templates/isos should be either async or changed to non-blocking
Date Fri, 10 Jan 2014 06:32:50 GMT

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

Marcus Sorensen commented on CLOUDSTACK-5843:
---------------------------------------------

We probably want to create a new async command and wrap the existing sync call in it, to maintain
api compatibility until we move to the next major version.

> registering templates/isos should be either async or changed to non-blocking
> ----------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-5843
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5843
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.2.0, 4.3.0, 4.4.0
>            Reporter: Marcus Sorensen
>             Fix For: 4.4.0
>
>
> The call to register templates and isos does more than most sync calls do, it seems to
talk to the ssvm and have it run commands that can potentially time out. I ran into this in
a test system when we tried to register a template with a non-routable URL. The cloudstack
API call just hung. I realize that there was a problem (ssvm could not reach the template
host), but no sync call should do anything like this that would block.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message