cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kelven Yang (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CLOUDSTACK-5961) CLONE - API: synchronization on the object is broken
Date Tue, 06 May 2014 23:32:16 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-5961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kelven Yang resolved CLOUDSTACK-5961.
-------------------------------------

    Resolution: Fixed

> CLONE - API: synchronization on the object is broken
> ----------------------------------------------------
>
>                 Key: CLOUDSTACK-5961
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5961
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.3.0
>            Reporter: Nitin Mehta
>            Assignee: Kelven Yang
>            Priority: Critical
>             Fix For: 4.4.0
>
>
> There is a way to synchronize API commands on certain CS object. For example, when createFirewallRule
is called, synchronization on the Network is being done, so the next command won't be processed
till the last one is executed.  To enable it for the certain command, following methods have
to be added to corresponding *Cmd class:
> @Override
>     public String getSyncObjType() {
>         return BaseAsyncCmd.networkSyncObject;
>     }
>     @Override
>     public Long getSyncObjId() {
>         return getIp().getAssociatedWithNetworkId();
>     }
> This logic got broken after the changes for vmSync got merged in. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message