cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chip Childers <chip.child...@sungard.com>
Subject Re: [ACS41] Blocker and critical issues stopping me from spinning out a new RC for 4.1
Date Thu, 25 Apr 2013 17:37:18 GMT
On Thu, Apr 25, 2013 at 10:32:15AM -0700, Min Chen wrote:
> Totally agree. 
> 
> Chip and others, Prasanna and I exchanged ideas about CLOUDSTACK--2126,
> and we both agree that we should only return async job Id and job status
> in queryAsyncJob and listAsyncJob commands, not in any other APIs so that
> we can have consistent response return in various scenarios.  If we fix
> this way, the behavior for listXXX api is changed. In 4.0, CloudStack has
> used ApiServer.buildAsyncListResponse() routine to fill in async job Id
> and status for all listXXX Apis.  With the proposed fix, we will not show
> async job information in listXXX response as well. Not sure if anybody see
> any side effect on this slight change from 4.0? Anybody know the reason
> why we had that special code in 4.0 to return async job for listXXX api?
> Since the proposed change will affect all newly created db view in 4.1, we
> suggest that this can be fixed in 4.2 since current behavior is not
> breaking functionalities, just return more information. Any thoughts?

+1 to doing that change in 4.2.

Specific to that release, can you please start a new thread about this
topic?  I don't want a decision like this (for 4.2) to be buried in a
4.1.0 release thread.

-chip

Mime
View raw message