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: Questions about 4.2 RC
Date Fri, 06 Sep 2013 16:07:35 GMT
On Fri, Sep 06, 2013 at 03:21:24PM +0000, Sateesh Chodapuneedi wrote:
> > -----Original Message-----
> > From: Edison Su [mailto:Edison.su@citrix.com]
> > Sent: 06 September 2013 02:08
> > To: dev@cloudstack.apache.org; Animesh Chaturvedi
> > Subject: RE: Questions about 4.2 RC
> > 
> > 
> > 
> > > -----Original Message-----
> > > From: sebgoa [mailto:runseb@gmail.com]
> > > Sent: Thursday, September 05, 2013 1:22 AM
> > > To: dev@cloudstack.apache.org; Animesh Chaturvedi
> > > Subject: Questions about 4.2 RC
> > >
> > > Hi,
> > >
> > > I followed the testing procedure for the 4.2 RC, I am ready to vote +1
> > > but I have questions (hence the new thread, don't want to hijack the VOTE).
> > >
> > > 1. the CHANGES file points to the release notes, but where are the
> > > release notes ? I know that no-one really stepped up on the RN but
> > > can't we at a minimum do a JIRA query that lists the bugs fixed in 4.2
> > > and the new features ?
> > >
> > > 2. Under infrastructure when I view the DevCloud Zone, I get this in the log:
> > > WARN  [cloud.api.ApiServer] (642225853@qtp-111037821-10:) Unknown API
> > > command: listVmwareDcs This is not a deal breaker but why is our UI
> > > calling a non-implemented API ? This sounds like introducing known
> > > issues. If it's not implemented yet, remove it.
> > 
> > The command is only available in non-oss build, but is still listed in command.properties,
as there is no separate file for commands non-oss
> > build.
> Yes, this command is only available in non-oss build and had to be placed in command.properties
as no separate file available for non-oss build.
> This API is called by UI to implement toggle effect for icon "Add/Remove VMware Datacenter".
This icon is associated with a cloudstack zone.
> If we drop the toggle functionality from UI then we need to have 2 icons instead (one
for "Add" and other for "Remove").

Shouldn't we consider making the UI respond appropriately to a missing
API (i.e.: don't show that feature if the API response to
that call is an error saying that the API call doesn't exist)?

Mime
View raw message