TIP : activer la fonction « All tasks » du web client sous vCenter 6

Mise à jour du 7/05/2015 : la localisation du fichier webclient.properties sous windows est \ProgramData\VMware\vCenterServer\cfg\vsphere-client. Une fois modifié, redémarrer le service « VMWare vSphere Web Client »

tipVoici une petite astuce rapide qui permet d’activer la visualisation de toutes les tâches (et pas seulement les vôtres) dans le nouveau bandeau du webclient vSphere 6. Ce billet décrit l’opération sur vCSA, mais il est applicable également sous vCenter/Windows moyennant quelques adaptations.

En effet, par défaut après une installation ou une upgrade, lorsque vous essayez de basculer l’affichage sur « All tasks » via le commutateur en bas à gauche, l’interface vous indique que cette option est désactivée :
screenshot_152

Pour remédier à cela, connectez-vous sous root sur la vCSA :

VMware vCenter Server Appliance 6.0.0

Type: vCenter Server with an embedded Platform Services Controller
root@vcenter's password: 
Last login: Fri Mar 13 04:46:37 2015 from jupiter.milky.way
Connected to service

    * List APIs: "help api list"
    * List Plugins: "help pi list"
    * Enable BASH access: "shell.set --enabled True"
    * Launch BASH: "shell"

Command>

Première chose, activer le shell (bash Linux) :

Command> shell.set --enabled True
Command> shell
    ---------- !!!! WARNING WARNING WARNING !!!! ----------

Your use of "pi shell" has been logged!

The "pi shell" is intended for advanced troubleshooting operations and while
supported in this release, is a deprecated interface, and may be removed in a
future version of the product.  For alternative commands, exit the "pi shell"
and run the "help" command.

The "pi shell" command launches a root bash shell.  Commands within the shell
are not audited, and improper use of this command can severely harm the
system.

Help us improve the product!  If your scenario requires "pi shell," please
submit a Service Request, or post your scenario to the
communities.vmware.com/community/vmtn/server/vcenter/cloudvm forum.

vcenter:~ # 

Ensuite, éditez le fichier /etc/vmware/vsphere-client/webclient.properties avec vi et modifiez le paramètre show.allusers.tasks en le passant à « true ». En passant, vous pouvez aussi jeter un coup d’oeil aux autres paramètres relativement explicites qui peuvent vous intéresser :

(...)

# Flag to enable All Users' Tasks in the Recent tasks view (change takes effect immediatly)
# It is only recommended for small to medium sized inventories and a limited number of concurrent users.
show.allusers.tasks = true

# Web client session timeout in minutes, default is 120, i.e. 2 hours
session.timeout = 120

# This value configures the auto-refresh rate of the client, in seconds.  By default it is disabled (-1).
# Warning: auto-refresh prevents client sessions from expiring and can severely affect scalability with many clients!
refresh.rate = -1

# This value configures the auto-refresh rate of the Recent Tasks list when displaying all users' tasks, in seconds.
# Default is 60, value can be between 10 and 600 seconds, or use -1 to disable auto-refresh.
tasks.refresh.rate = 60

# This value configures the maximum number of tasks displayed in the Recent Tasks list.
# Count can between 1 and 100.  The default value is 50 if nothing is set.
tasks.display.count = 50

# This value configures the auto-refresh rate of the Alarms list. The default value is 60 seconds.
# Rate can between 10 and 600 seconds, or use -1 to disable auto-refresh.
alarms.refresh.rate = 60

# This value configures the maximum number of alarms displayed in the Alarms list.
# Count can between 1 and 100.  The default value is 30 if nothing is set.
alarms.display.count = 30

Enfin, une fois sauvegardé, relancez les webservices :

vcenter:/etc/vmware/vsphere-client # /etc/init.d/vmware-vws stop
HardwareHealth: Stopping /usr/java/jre-vmware/bin/vmware-vws
done
vcenter:/etc/vmware/vsphere-client # /etc/init.d/vmware-vws start
HardwareHealth: Starting /usr/lib/vmware-vws/bin/vws.sh
28841