v26

New Features:

• Support multiple resource group for VM resources #286. Please see more details here

• Support managed disks in Azure National Cloud (Germany, China and USGovernment) #288

• Support large disk, and add new available vm size #289

• Enable boot diagnostics when debug mode is on #295

Fixes:

• Set the correct OS disk size for Windows #290

Improvements:

• Refine locks #287

Development:

• Support multiple Azure environment in CI #288

• Add lifecycle test for Windows stemcell #291

v25

New Features:

• VM is created in the same location with the virtual network instead of the storage account. #274

Fixes:

• Handle the connection reset error to azure blob storage. #268

• Retry once and only once if CPI receives AzureConflictError when deleting a managed disk. #269

• Specify the disk size when attaching an unmanaged disk. Otherwise, the disk size can't be shown by Azure Portal or Azure CLI. #275

• Uses the same SCSI host device ID for AzureStack as Azure so that it works correctly with the stemcell v3232.5+. #276

• Update resource provider API versions for AzureStack. #285

Improvements:

• Bump bosh_cpi version from 1.3262.4.0 to 2.1.1. #273

• Upgrade azure-storage-ruby to v0.12.1-preview. #268

  • Please see the release notes of v0.12.1-preview and v0.12.0-preview.

Docs:

• Provide a checklist before migrating to managed disks. #271

Development:

• Bump rake & spec & other gems. #279

• Add the integration test cases for azure_cpi. #273

• Seperate test cases for cloud.rb into different files, and increase coverage rate. #277

v24

New Features:

• Support to set idle timeout in minutes for dynamic public IPs by configuring pip_idle_timeout_in_minutes in global Azure properties.
  • The default idle timeout of Azure public IPs is 4 minutes. The available value is [4, 30]. It must be integer.
  • If the interval that your applications send keep-alive is longer than the idle timeout, the TCP connections from/to the public IPs will be closed by Azure. So you need to increase the idle timeout of public IPs or decrease the interval in your applications.
  • If you set a too big value as the idle timeout, all ports associated with public IPs may be exhausted if your applications do not close TCP connections properly.
• Keep failed VM if the VM fails in provisioning.
  • Sometimes, the user needs to keep the VM for troubleshooting when the VM provisioning fails due to some platform or stemcell issues.

Fixes:

• Fix that some functions eat exceptions.

Docs:

• Add a doc about how to backup and restore Cloud Foundry

v23

New Features:

• Support Windows heavy and light stemcells for both managed disks and unmanaged disks.
  • Do not need to set windows.username and windows.password in bosh.yml. username and password are required when creating Windows VMs but BOSH never use it, so CPI automatically generates 15 secure random characters as username and 72 secure random characters as password.
  • Disable Windows AutoUpdate. Users always use new stemcells for update.
• Support AzureStack TP3.

Fixes:

• Fix #259: Use Json format to store light stemcell information.
• Redact credentials in logs
  • Credentials only can be logged when debug_mode is set to true.

v22

New Features:

• Support GermanCloud.

• Support light stemcells.

• Support to create Windows VM with managed disks.
  Need to add below configs in global azure properties in bosh.yml.

  azure:
    windows:
      username: xxxx # Admin user to use when spinning up new Windows VMs. Only available for Windows
      password: xxxx # Password to use when spinning up new Windows VMs. Only available for Windows
  

Fixes:

• Fix an issue in v21 that old compute API version does not support sku property in AzureChinaCloud
• Fix an issue in v21 that it wrongly sets permission of the container stemcell when storage accounts are premium.

Development:

• Add how to test interfaces with bosh_azure_console in docs/development.md

v21

NOTES: This version does NOT work in Mooncake now

New Features:

• Support managed disks. Please reference the guidance on how to deploy a new deployment, or migrate an existing deployment, utilizing the new Managed Disks Service on Azure.

  Below GitHub issues are fixed with managed disks.

  • #228: Can we support managed disks?
  • #225: Stripe storage account placement across each VM in an availability set
  • #178: Avoid using storage account tables to keep track of copying process
  • #116: user should be able to set storage_account_name on a persistent disk
  • #68: CID of VMs is not well named

Improvements:

• Upgrade azure-storage-ruby to v0.11.5.

  Please see release notes of azure-storage-ruby v0.11.5

• Auto retry when the connection to Azure AD or ARM is reset because of OpenSSL::SSL::SSLError or OpenSSL::X509::StoreError.

v20

Fixes:

• Delete the possible unexpected node resources before updating VMs.
  • When Azure Security Center is enabled in a subscription, Azure Security Monitoring extension will be installed in all VMs under this subscription. All VMs' information will contain a node resources. This node must be deleted before updating VMs. Otherwise, you will hit an error InvalidRequestContent.
  • About Azure Security Center, you can get more information here.
• Other minor fixes

v19

Improvements:

• Upgrade azure-storage-ruby to v0.11.3.
  • Please see release notes of azure-storage-ruby v0.11.3
• Support Azure US government.
  • You can set environment to AzureUSGovernment to deploy BOSH/CF on Azure US government.

v18

New Features:

• Support to assign dynamic public IPs to VMs in one resource pool automatically.

  • You can use below config to enable it.
  • You can see the background in the issue #217.

  resource_pools:
  - name: default
    cloud_properties:
      assign_dynamic_public_ip: true   # defaults to false
  

v17

Improvements:

• Upgrade azure-storage-ruby to v0.11.1.
  • Please see release notes of azure-storage-ruby v0.11.1
• Add and log x-ms-client-request-id for all storage requests.
  • You can find logs for every call to azure-storage-ruby by the keyword Calling.
  • You can find request-id(It is x-ms-client-request-id in every HTTP request) in the log with Calling and ask Azure support team to investigate Azure logs for every storage request.