aws-samples/aws-cfn-windows-hpc-template

This sample CloudFormation template will launch a Windows-based HPC cluster running Windows Server 2012R2 and supporting core infrastructure including VPC, domain controllers and bastion servers.

aws-cfn-windows-hpc-template's Issues

Issue with Node.JS runtime

We have found another issue with the script. This is due to the runtime for nodejs:

"FindSnapshotFunction": {
			"Type" : "AWS::Lambda::Function",
			"Properties" : {
				"Code" : {
					"S3Bucket" : "<BUCKETNAME>",
					"S3Key" : "lambda/find-snapshot.zip"
				},
				"Description" : "AWS Lambda function for searching snapshot based on name",
				"Handler" : "find-snapshot.handler",
				"MemorySize" : "128",
				"Role" : { "Fn::GetAtt" : [ "FindSnapshotRole", "Arn" ] },
				"Runtime" : "**nodejs**",
				"Timeout" : "25"
}

The NODEJS runtime must now be changed to "nodejs4.3" for the runtime. Othewise the script will fail to run properly from within Lambda.

Issue with SnapshotID parameter in 2-cluster.json

{
"AWSTemplateFormatVersion" : "2010-09-09",
"Description" : "This CloudFormation stack creates a Microsoft HPC Pack 2012 R2 Cluster in an existing environment. WARNING This template creates two or more Amazon EC2 instances. You will be billed for the AWS resources used if you create a stack from this template.",
"Parameters" : {
"KeyName" : {
"Description": "Name of an existing EC2 Key Pair",
"Type" : "String",
"Default" : ""
},
"SnapshotID" : {
"Description" : "Snapshot Id of the HPC Installation data",
"Type" : "String",
"AllowedPattern" : "snap-([0-9a-fA-F]{8})",
"ConstraintDescription": "must be a valid snapshot ID."
},

Under SnapshotID, the "AllowedPattern" parameter failed for me. Granted, I had to copy my snapshot between regions, and I noticed the replicated snapshotID was larger than the original. So, I changed line 13 of the json file to this:

"AllowedPattern" : "snap-([0-9a-zA-Z]*)"

So the final version looks like this:

{
"AWSTemplateFormatVersion" : "2010-09-09",
"Description" : "This CloudFormation stack creates a Microsoft HPC Pack 2012 R2 Cluster in an existing environment. WARNING This template creates two or more Amazon EC2 instances. You will be billed for the AWS resources used if you create a stack from this template.",
"Parameters" : {
"KeyName" : {
"Description": "Name of an existing EC2 Key Pair",
"Type" : "String",
"Default" : ""
},
"SnapshotID" : {
"Description" : "Snapshot Id of the HPC Installation data",
"Type" : "String",
"AllowedPattern" : "snap-([0-9a-zA-Z]*)",
"ConstraintDescription": "must be a valid snapshot ID."
},

Issue with running this on base AWS Windows 2016 instance

Found a problem with the zip routine in the publish.ps file.
Publish,ps1 file called for the following assembly:
Add-Type -assembly "System.IO.Compression"
This does not work, and the zip function that follows fails as it cannot find the type:
Unable to find type [System.IO.Compression.ZipFile].

At C:\Users\Administrator\Downloads\aws-cfn-windows-hpc-template\publish.ps1:64 char:14
+   $archive = [System.IO.Compression.ZipFile]::Open($TmpName, [IO.Comp ...
+              ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (System.IO.Compression.ZipFile:TypeName) [], RuntimeException
    + FullyQualifiedErrorId : TypeNotFound

Found the following link:
https://blogs.technet.microsoft.com/heyscriptingguy/2015/03/09/use-powershell-to-create-zip-archive-of-folder/

This shows the following command:
Add-Type -assembly "system.io.compression.filesystem"

I've added the following to my copy and this seems to alleviate the problem:

Add-Type -assembly "System.IO.Compression"
Add-Type -assembly "System.IO.Compression.filesystem"