NICE:Landing page - Revision history

Mohammed at 14:26, 22 March 2017

2017-03-22T14:26:18Z

Mohammed: /* DCV End Station Installation Guide */

2017-03-22T14:24:31Z

DCV End Station Installation Guide

Mohammed at 14:00, 22 March 2017

2017-03-22T14:00:41Z

Mohammed: /* DCV Server Installation Guide */

2017-03-22T13:59:36Z

DCV Server Installation Guide

Mohammed at 13:58, 22 March 2017

2017-03-22T13:58:22Z

Show changes

Mohammed: /* Operation Guides */

2017-03-22T13:56:45Z

Operation Guides

Mohammed: /* X Server Requirements */

2017-03-22T13:37:54Z

X Server Requirements

Mohammed: /* X Server Requirements */

2017-03-22T13:37:29Z

X Server Requirements

Mohammed: /* X Server Requirements */

2017-03-22T13:36:50Z

X Server Requirements

Mohammed: /* X Server Requirements */

2017-03-22T13:33:41Z

X Server Requirements

@@ Line 190: / Line 190: @@
 <syntaxhighlight>
 sh nice-dcv-endstation-2016.0-xxx.run
 </syntaxhighlight>

← Older revision		Revision as of 14:24, 22 March 2017
Line 182:		Line 182:

	== DCV End Station Installation Guide ==		== DCV End Station Installation Guide ==
		+
		+	Installing Linux End Stations
		+
		+	* download the DCV End Station .run archive from https://www.nice-software.com/ dcv
		+	* from a terminal go to the directory containing the installation files
		+	* run the installer as the root user and follow the instructions:
		+	<syntaxhighlight>
		+	sh nice-dcv-endstation-2016.0-xxx.run
		+	</syntaxhighlight>

← Older revision		Revision as of 14:00, 22 March 2017
Line 180:		Line 180:
	On Windows		On Windows
	TODO		TODO
		+
		+	== DCV End Station Installation Guide ==

← Older revision		Revision as of 13:59, 22 March 2017
Line 177:		Line 177:

	Note: DCV is automatically enabled on completion of the installation process. In case you update your kernel version or graphics drivers, run the dcvadmin enable command as root to re-enable the software.		Note: DCV is automatically enabled on completion of the installation process. In case you update your kernel version or graphics drivers, run the dcvadmin enable command as root to re-enable the software.
		+
		+	On Windows
		+	TODO

@@ Line 159: / Line 159: @@
 * only when using Native Display mode on Linux with VNC in Service mode additional configuration is required to enable the vnc.so module.
-== Operation Guides ==
+== DCV Server Installation Guide ==
-*[[DCV: Access using the CLI | Access using the CLI]]
+On Linux
-*[[DCV: Uploading Images to the Piston Cloud | Uploading Images to the Piston Cloud]]
-*[[DCV: Command Line Cheatsheet Openstack | Command Line Cheatsheet Openstack ]]
+* log in as root on the node via SSH or directly from the console. Switch to runlevel 3:
 == Component Guides ==

@@ Line 155: / Line 155: @@
 * NVIDIA drivers must be correctly working on this display.
 * in case of multiple GPUs on the same node the suggested configuration is a single X Server for all GPUs, one Screen for each GPU. Example: :0.0 for the first accelerated GPU, :0.1 for the second accelerated GPU..
-* local UNIX connections to the 3D accelerated X Server displays must be granted to the users of the 3D applications. DCV libraries run inside the 3D applications launched by the users. They redirect 3D calls to the accelerated display and so the applications processes run by the users must be able to access it. When running dcvadmin enable, DCV automatically searches for well-known X or display manager startup scripts and adds a call to /opt/nice/dcv/bin/dcvxgrantaccess. By default dcvxgrantaccess executes xhost +local:. So when X is launched the display
+* local UNIX connections to the 3D accelerated X Server displays must be granted to the users of the 3D applications. DCV libraries run inside the 3D applications launched by the users. They redirect 3D calls to the accelerated display and so the applications processes run by the users must be able to access it. When running dcvadmin enable, DCV automatically searches for well-known X or display manager startup scripts and adds a call to /opt/nice/dcv/bin/dcvxgrantaccess. By default dcvxgrantaccess executes xhost +local:. So when X is launched the display access is granted. It is possible to change this behaviour, for example to restrict the access to a subset of users, providing a custom implementation of dcvxgrantaccess.
 * color depth must be 24-bit
 * only when using Native Display mode on Linux with VNC in Service mode additional configuration is required to enable the vnc.so module.

← Older revision		Revision as of 13:33, 22 March 2017
Line 152:		Line 152:

	== X Server Requirements ==		== X Server Requirements ==
		+	On Linux, the host equipped with 3D accelerated video adapters must run an accelerated X Server configured according to these requirements:
		+	* NVIDIA drivers must be correctly working on this display.
		+	* in case of multiple GPUs on the same node the suggested configuration is a single X Server for
		+	all GPUs, one Screen for each GPU. Example: :0.0 for the first accelerated GPU, :0.1 for the second accelerated GPU..
		+	* local UNIX connections to the 3D accelerated X Server displays must be granted to the users of the 3D applications.
		+	DCV libraries run inside the 3D applications launched by the users. They redirect 3D calls to the accelerated display and so the applications processes run by the users must be able to access it.
		+	When running dcvadmin enable, DCV automatically searches for well-known X or display manager startup scripts and adds a call to /opt/nice/dcv/bin/dcvxgrantaccess. By default dcvxgrantaccess executes xhost +local:. So when X is launched the display
		+	access is granted. It is possible to change this behaviour, for example to restrict the access to a subset of users,
		+	providing a custom implementation of dcvxgrantaccess.
		+	* color depth must be 24-bit
		+	* only when using Native Display mode on Linux with VNC in Service mode additional configuration is required to enable the vnc.so module.
		+
	== Operation Guides ==		== Operation Guides ==