Description

• Add parameters to Add-AzServiceFabricNodeType to facilitate easy alternate OS image creation for new node type.
  Parameters: VMImagePublisher, VMImageOffer, VMImageSku, VMImageVersion
  • Example usage: For a Ubuntu 16.04 cluster, add a new Ubuntu 18 node type:
    

  $resouceGroup="Group1"
  $clusterName="Contoso01SFCluster"
  $nodeTypeName="nt2"
  $securePassword = ConvertTo-SecureString -String 'Password$123456' -AsPlainText -Force
  
  Add-AzServiceFabricNodeType -ResourceGroupName $resouceGroup  -ClusterName $clusterName -NodeType $nodeTypeName -Capacity 5 -VmUserName adminuser -VmPassword $securePassword -DurabilityLevel Silver -Verbose -VMImageSku 18.04-LTS

• Add parameter IsPrimaryNodeType to Add-AzServiceFabricNodeType to be able to create an additional primary node type,
  for the purpose of transitioning the primary node type to another one in the case of OS migration.
• Add-AzServiceFabricNodeType now correctly copies the LinuxDiagnostic extension. This was previously not working for Linux.
• Add-AzServiceFabricNodeType now correctly copies the RDP/SSH load balancer inbound NAT port mapping to the new node type.
• Add template for UbuntuServer1804 for creating Ubuntu 18.04 clusters using New-AzServiceFabricCluster.
• Remove-AzServiceFabricNodeType was incorrectly blocking Bronze durability node types for removal, and this has been updated
  to only block when the Bronze durability level differs between the SF node type and VMSS setting.
• Added cmdlet Update-AzServiceFabricVmImage to update the delivered SF runtime package type. This must be changed when migrating from Ubuntu 16 to 18.
• Added cmdlet Update-AzServiceFabricNodeType to update the properties of a cluster node type. For now this is solely used to update whether the node type is primary via bool parameter -IsPrimaryNodeType $false.
• Update-AzServiceFabricReliability is now able to update reliability level when the cluster has more than one primary node type.
  To do this, the name of the node type is supplied via the new -NodeType parameter.

Checklist

• [ x ] I have read the Submitting Changes section of CONTRIBUTING.md
• [ x ] The title of the PR is clear and informative
• [ x ] The appropriate ChangeLog.md file(s) has been updated:
  • For any service, the ChangeLog.md file can be found at src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md
  • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header -- no new version header should be added
• [ x ] The PR does not introduce breaking changes
• [ x ] If applicable, the changes made in the PR have proper test coverage
• For public API changes to cmdlets:
  • a cmdlet design review was approved for the changes in this repository (Microsoft internal only)
    • {Please put the link here}
  • the markdown help files have been regenerated using the commands listed here