tecProTools
  • Home
  • Solution Automations
  • Install User Experiences
  • About us.
  • Contact us.
Digital tools for technical professionals

Azure arm virtual machines, nested loops, winRM and custom extensions

5/9/2019

0 Comments

 
This automation is used when an automation designer intends to implement, install, and provision one or more virtual machine assemblies.
 
This design extends the automation described in the previous article https://dzone.com/articles/arm-azure-resource-manager-templates-nested-loops to include the installation of 1 to n virtual machine assemblies, and to provision winRM, initialize data disks, and configure an application log on each virtual machine. A virtual machine is assembled from a collection of resource objects: compute e.g. vm; storage e.g. data managed disks, and; network e.g. network interface card and public ip address.
to edit.
azure-arm-vmas-nestedloops.pdf
File Size: 1941 kb
File Type: pdf
Download File

This design’s resource specification templates and scrips, intended for elucidation not for production, are available here, under an MIT license:
https://github.com/TecProTools/azure-arm-vmas-NestedLoops
​
0 Comments

ARM: Azure resource manager templates, nested loops – a commentary

1/15/2019

0 Comments

 
arm-nestedloops.pdf
File Size: 959 kb
File Type: pdf
Download File

0 Comments

Lean Engine Install Experience

5/29/2017

0 Comments

 
Algorithmic trader experiences
The algorithmic trader can utilise their azure subscription -- to host, their nominated github/<client name> sourced, installation of the open source, lean engine application project, e.g. github/<client name>/Lean nominated at 27 May 2017 -- to run their backtest cycles:
  • The algorithmic trader views the billing amount of their usage and the associated resource level charges via the azure portal and their Subscription > Billing > Pay As You Go.
  • The algorithmic trader’s automation engineer, installs the tecProtools lean engine demo solution automation into a resource group within the algorithmic trader's existing azure subscription. 
  • The algorithmic trader monitors their algorithm's output i.e.  -- over a remote desktop connection (rdc/rdp) session, through a Point-to-Site[1], aka P2S, vpn, connection to the trader’s azure, subscription, automation account and resource group -- by reviewing log.txt as with a locally hosted lean engine application installation.
  • The algorithmic trader installs onto azure vm and runs their proprietary algorithm.

Lean Engine deployment experience
The tecProtools, lean engine solution automation service, involves a sequence of configurations at github, visual studio team services, and azure resource manager, utilizing the trader's nominated credentials. Say, for example by employing the credentials for an automation engineer rbac [2] role with suitable permissions, authenticated and authorized by azure active directory.
Picture
​Footnotes
[1] A Point-to-Site (P2S) VPN gateway connection allows you to create a secure connection to your virtual network from an individual client computer. P2S is a VPN connection over SSTP (Secure Socket Tunnelling Protocol). P2S connections do not require a VPN device or a public-facing IP address to work. You establish the VPN connection by starting it from the client computer.
From <https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-about-vpngateways>
[2] Automation engineer rbac role has the role based access control permissions granted for the automation engineer role, i.e. Contributor, authenticated by azure active directory.
0 Comments

    Author

    Is an automation designer at tecProTools.com .

    Archives

    May 2017

    Categories

    All

    RSS Feed