> [Chip] Perhaps a future enhancement would be to use the discovery service to > figure out what API's are being exposed by the specific management server, > and adjust the UI accordingly.
[Jessica] +1 It will be great if server-side is able to provide this info (what API's are being exposed). Then, yes, UI can definitely be adjusted accordingly. -----Original Message----- From: Chip Childers [mailto:chip.child...@sungard.com] Sent: Friday, September 06, 2013 12:33 PM To: Jessica Wang Cc: dev@cloudstack.apache.org; Animesh Chaturvedi; Edison Su; run...@gmail.com; Sateesh Chodapuneedi Subject: Re: Questions about 4.2 RC - listVmwareDcs API On Fri, Sep 06, 2013 at 06:30:52PM +0000, Jessica Wang wrote: > > This API is called by UI to implement toggle effect for icon "Add/Remove > > VMware Datacenter". > > [Jesisca] No, listVmwareDcs API was called by UI to get VMware DataCenter > info to display in zone detail page (which has 3 fields: "VMware dataCenter > Name", "VMware dataCenter vcenter", "VMware dataCenter Id"), NOT to toggle > effect for icon "Add/Remove VMware Datacenter". > > > > [Chip] 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)? > > [Jessica] There is no way for UI to know whether an API command is missing or > not before calling it. > After calling an API command, if API returns error "Unknown API command", UI > will suppress the error message (i.e. UI will not pop up a dialog showing > "Unknown API command"). > The error "Unknown API command" was seen in the log, NOT on UI. > However, I just checked in an UI enhancement to skip calling listVmwareDcs > API if a zone doesn't have any VMware cluster(s). Sounds like a good workaround. Perhaps a future enhancement would be to use the discovery service to figure out what API's are being exposed by the specific management server, and adjust the UI accordingly. -chip
