Bug 491467

The description is too generic,

Can you give me an example ?

In addition please check the help in the vdsClient to see whether it answers the issue.

In case this is not enough then please describe what do you expect to have (each build) and keep in mind we are still in the coding, and things are still rapidly changing.

(In reply to comment #1)
> The description is too generic,
> 
> Can you give me an example ?
> 
> In addition please check the help in the vdsClient to see whether it answers
> the issue.
> 
> In case this is not enough then please describe what do you expect to have
> (each build) and keep in mind we are still in the coding, and things are still
> rapidly changing.  

Compare vdsm-4.4-25694 in snap4 with vdsm-4.4-25304 in snap3,I make a diff to two help in the vdsClient.
For example:
   connectStoragePool
-        <spUUID>
+        <spUUID> <id> <scsi-key>

+spmStart
+        <spUUID> <prevID> <prevLVER> <recoveryMode> <scsiFencing>
+        Start SPM functionality

  It hards to clear how to get or set <id> <scsi-key> parameters.I checked storage API on wiki.It seems that it hasn't been updated for a long time.
  If add some update information,such as what the new parameters for and their type,it will be more clear.

The testing team need more details about the vdsClient usage.
for example:
1. desktopLock
when use it as "vdsClient 0 desktopLock <vmId>", get response:
"Guest agent non-responsive"
similar issue for the commands "desktopLogoff", "desktopLogin", "sendHcCmd"
we need to know how to use these commands or how to configure the environment to make them to work.

2. sendkeys
How the keys such as CTRL, ENTER, SHIFT should be represent in the command.

3. monitorCommand
What the "monitor command" means?

4. task management related commands
We need more information about the task management related commands in vdsClient.

There is little available information about vdsm we can get. It will be a great pleasure if we can get a detailed help page about the commands in vdsClient.

I'm not sure why you are doing this communication via bugzilla, and not over emails or IRC.

Information has to be track so during bug verification we know what's being fixed.

Moving to 1.1 as there's no client requirement to create the VM from RHEV-H. The docs in 1.0 is more for RHEV-H QE consumption.

It'll be better if develop team can supply a more detailed change log come along with every build of vdsm, such as that come along with vdsm-4.4-27666. And not only the bug fix info but also new feathers or important change of APIs should be included. Specially when some features can work from that build, it should be indicated clearly.

I think your team is spending too much time on VDSM - and not enough on lower layers. We test VDSM quite extensively.

(In reply to comment #7)
> It'll be better if develop team can supply a more detailed change log come
> along with every build of vdsm, such as that come along with vdsm-4.4-27666.
> And not only the bug fix info but also new feathers or important change of APIs
> should be included. Specially when some features can work from that build, it
> should be indicated clearly.  

There is a separate bug to track that issue (494762) so no need to replicate that particular request here.

postponed to 3.0

*** Bug 568004 has been marked as a duplicate of this bug. ***

Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.