isabella232 / azure-accessplatform-windows-gpu Goto Github PK

• Prereqs
• Deploy and Visualize
• PCoIP with Teradici and NVIDIA GRID Management on Azure for M60 Visualizations
• Optional Usage of Operational Management Suite
• Manual Install of OpendTect for Sanity
• MSFT OSCC
• Credits
• Reporting Bugs
• Patches and pull requests
• Deploying to existing Azure resource group with existing Azure Virtual Network

Obtain a Trial License Activation Code For the Teradici "Graphics Agent for Windows" from here to put in the template parameter. If that is not put in, Windows Server would be available over Personal Session Desktop for RDS using RDP 10

Please download PCoIP Software Clients 1.11 (Beta) for Windows from here to access over PCoIP

• NVIDIA GRID 4.2 (369.95) with NVIDIA GRID 4.2 latest Driver (Defaulted) and working.

• NVIDIA GRID 4.1 (369.71) with Azure NVIDIA GRID Driver (non-defaulted) and working

• All software installers and sample data are in D:\ and system installers like Teradici, Azure NVIDIA GRID Driver installers are in D:\DownloadInstallers

• Latest Teradici Cloud Access Software 2.8.0 (Beta) Agent- Graphics Edition for Windows. Includes the latest client PCoIP Software Clients 1.11 (Beta) for Windows.

• Manual Install of OpendTect for Sanity

• nView needs to be enabled manually. Right click Desktop-> nview-> enable User Guide

Tip: Map you local drive only when using Remote Desktop Client (not PCoIP) to transfer files to your virtual machine. Find more information here

• For GRID server interfaces for GPU management, please view the grid software management sdk user guide
• nView needs to be enabled manually. User Guide
• Collection of the user dumps for the NVIDIA Display Driver 369.95 or 369.71 from within the VM on Display Driver Crash if occurs.
• Details are here
• PCoIP Graphics Agent for Windows Log Collection (2.8.0.5813 (2.8 Beta Presently) and 2.7.0.4060) from the Teradici System Tray (right click Teradici Icon on System Tray) and collect Agent Logs (from the pop-up).
• PCoIP Graphics Agent for Windows 2.8.0.5813 (2.8 Beta Presently) and 2.7.0.4060 uses Multiple PCoIP encoding.
• The PCOIP Agent Logs v1.11 ~Beta from the Office Client machine of the end-user from C:\Users\user_name\AppData\Local\Teradici\PCoIPClient\logs
• The PCoIP Event filter can be increased to 3 for debug as per the following registry key entry.

            HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Teradici\PCoIP\pcoip_admin_defaults
               DWORD: pcoip.event_filter_mode
            Set the value to one of the following: 
               0 - (CRITICAL)
               1 - (ERROR)
               2 - (INFO)
               3 - (Debug)

OMS Setup (for mostly Security, compliance and backup in this case) is optional and the OMS Workspace Id and OMS Workspace Key can either be kept blank or populated post the steps below.

Create a free account for MS Azure Operational Management Suite with workspaceName

• Provide a Name for the OMS Workspace.
• Link your Subscription to the OMS Portal.
• Depending upon the region, a Resource Group would be created in the Sunscription like "mms-weu" for "West Europe" and the named OMS Workspace with portal details etc. would be created in the Resource Grou
• login to https://<>.portal.mms.microsoft.com
• Add The solutions "Agent Health", "Backup", "Security & Compliance", "Activity Log Analytics" and "Protection & Recovery" Solutions from the "Solutions Gallery" of the OMS Portal of the workspace.
• Logon to the OMS Workspace and Go to -> Settings -> "Connected Sources" -> "Windows Servers" -> Obtain the Workspace ID like ba1e3f33-648d-40a1-9c70-3d8920834669 and the "Primary and/or Secondary Key" like xkifyDr2s4L964a/Skq58ItA/M1aMnmumxmgdYliYcC2IPHBPphJgmPQrKsukSXGWtbrgkV2j1nHmU0j8I8vVQ==
• While Deploying the Template just the WorkspaceID and the Key are to be mentioned and all will be registered. The Windows Agent is already available in the VM once WorkspaceID and Key are put in during Template deployment.

• Then one can login to https://<>.portal.mms.microsoft.com and monitor VM and use Log Analytics and if Required perform automated backups using the corresponding Solutions for OMS.
• Or if the OMS Workspace and the Machines are in the same subscription, one can just connect the VM sources manually to the OMS Workspace as Data Sources.

• On using default options of the template, OpendTect Installer 6.0.6 would be available in D:\DownloadInstallers folder of the NV
• On using default options of the template, D:\opendtect empty folder would be available as OpendTect Data Root location post manual install.
• D: Drive of the NV is a NVMe SSD over PCIe interface and hence usage of the drive is preferred as the OpendTect Data Root directory.
• Post-installation of ALL features of OpendTect Pro and successfully in D:\OpendTect, ONLY zip file survey option should be chosen via OpendTect startup and the zip file for Netherlands North F3 Data should be downloaded directly from VM browser from here. It should be downloaded manually from browser in the NV prior to OpendTect manual installation.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.

• The NVIDIA GRID 4.1 (369.71) with "Azure" Driver silent install works with certificate force trust - Thanks to Mathieu Rietman's commit on fork for the -f option.

• The NVFBC stop start with time lag aka Driver Kick snippet uses the snippet as per specific commit in Teradici Branch on fork of master by Peter Longhurst.

• Dynamic Disk Selection with take function is as per the Azure quickstart template

Please report bugs by opening an issue in the GitHub Issue Tracker

Patches can be submitted as GitHub pull requests. If using GitHub please make sure your branch applies to the current master as a 'fast forward' merge (i.e. without creating a merge commit). Use the git rebase command to update your branch to the current master if necessary.

Though this is a malpractice since resource groups are for isolation of specific automated workloads, some personnel prefer it to reuse manually created NSGs which are non-automated procedures. It is possible to deploy this to existing resourcegroup with existing vnets, since all configurations are exposed including ipconfigurations. Internal IP Allocation method is Dynamic and external Allocation method is exposed as "Dynamic" or "Static". One has to judiciously choose the Address Space, subnet Range, nicname, existing virtual network name in existing resource group so that conflict does not occur. Output would be new subnet in existing vnet with new address range, new nic name. This would not be part of a cluster.

For clustering advanced network configurations, please view Azure Big Compute repo