v35.4.1

Fixes:

• Cannot create public IP addresses when using AZs (#608)

v35.5.0

Features:

• Support Azure managed identity. See the doc for details. (#591)

  1. Managed identity can be configured on VMs via vm_extensions;

  2. Managed identity can be used as credential source of CPI;

  3. Both system-assigned and user-assigned managed identity are supported.

• Refine the scenario of vm_resources. (#552)

  The CPI method calculate_vm_cloud_properties returns a list of instance types.

  1. The instance types are available in the location, which is specified in CPI global configuration.

  2. The instance types meet the requested 'vm_resources'.

  3. The instance types which support Premium storage are recommended.

  When creating VMs, CPI will:

  1. Check whether the disks are persistent disks. If so, use the instance types which support premium storage.

  2. Use the instance types which are available in the available sets.

• Upgrade Compute API version to 2018-04-01. (#495)

• Support a new cloud property type for the root & ephemeral disk. (#498)

• Support managed disk type StandardSSD_LRS. (#498)

• Support configuring the resource group for load balancer and security group. (#541)

• Support application security groups in Azure USGov Cloud and Azure German Cloud. (#463)

Fixes:

• Make independent tasks async when creating or deleting VMs. (#465)

• Use SAS token url to copy stemcell. CPI doesn't require the stemcell container to be public. (#511)

• Increase the data disk max count, because Azure documents update the Max data disks of each VM size. (#502)

• Delete the deprecated user image only once. (#567)

• Remove the disk path in the registry settings, since it's not used any longer. (#501)

Documents:

• Add a doc to use Standard SKU load balancers and migrate from basic load balancer to standard load balancer. (#494)

• Migrate NFS blobstore to Azure using goblob. (#526)

• Add steps to enable accelerated networking in PCF. (#582)

• Add a doc to deploy hybrid CF across Azure and Azure Stack. (#539)

• Add a Powershell script to deploy CF on ASDK. (#527)

• Add how to use Azure Stack storage blobstore. (#504)

• Add how to migrate from internal MySQL databases to Azure Databases for MySQL. (#486)

Development:

• Split integration test cases into different files. (#522)

• Create separate pipeline for develop branch. (#524)

Alpha for v35.4.0

This is for the basic verification.
Please don't use it in production.

v34.0.1

Fixes:

• Refine file locks for inter process communication (#561)

v35.4.0

Features:

• CPI Supports enabling accelerated networking for VM network interface. (#410)
  By default, accelerated networking is disabled. To enable it, you can set accelerated_networking in vm_types or vm_extensions or network configuration to true. The accelerated_networking in vm_types/vm_extensions can override the equivalent option in the network configuration. See the doc for details.
• CPI supports custom tags for VMs. (#425)
  A new cloud property tags is added in vm_types or vm_extensions. They are name-value pairs.
  • Before configuring it, please review the limitations apply to tags.
  • In Azure, each VM can have a maximum of 15 tag name-value pairs. Currently, BOSH director and Azure CPI use at most 10 tags. So it's not recommended to use more than 3 custom tags.

Fixes:

• Remove extra md5 calculation when uploading blobs. (#413)
• Split the low level retry (network errors) and the high level retry (http status code). (#421)
• Bump to ruby 2.4.4. (#409)

Documents:

• Deploy Cloud Foundry with Traffic Manager. (#406)
• Use goblob + minio to migrate blobs from an NFS blobstore to an Azure Storage blobstore. (#418)

Development:

• Enable the rubocop. (#407)
• Enable Jenkins CI for rubocop check and unit tests. (#414)
• Add a script to test the creating/deleting performance. (#416)

v35.3.0

Features:

• CPI sets the default option for diagnostic data collecting and VM boot diagnostics to false, allowing customer to turn it on. (#400)

  Collecting diagnotics data should be opt-in, not opt-out. #399.

  To turn on the diagnostics features, you can explicitly set value of enable_telemetry and / or enable_vm_boot_diagnostics in global configuration. Example:

  azure: &azure
    environment: AzureCloud
    ...
    enable_telemetry: true
    enable_vm_boot_diagnostics: true
  

• CPI supports enabling IP forwarding for VM network interface. (#382)

  By default, IP forwarding is disabled. To enable it, you can set ip_forwarding in VM type/extension or network configuration to true. The ip_forwarding in VM type/extension can override the equivalent option in the network configuration.

Fixes:

• When diagnostic metrics is turned on, CPI waits for logging to complete before finishing VM creation, This slows down the process. The fix allows CPI to proceed with VM creating in parallel of the diagnostic logging. (#394)

• The default value of disk type is Premium_LRS if instance type is the series B, Dsv3, Esv3 and Ls. (#389)

• When creating storage account, CPI will wait until its provisioning state becomes succeeded. (#387)

• Update Active Directory Endpoint of Azure USGovernment. (#391)

• Add EOFError as one of the retryable network errors. (#393)

Documents:

• Update CPI global configurations for Azure Stack. (#397)

Development:

• Create standard sku public ip using terraform in CI. (#390)

• Use master branch of bosh-acceptance-tests for CI. (#390)

v35.2.0

Features:

• CPI collects diagnostic metrics. (#374)

  The diagnostic data includes the VM and disk creating/deleting status and performance. This helps us to identify the issues quickly with better accuracy.

  You can set enable_telemetry in the Azure CPI global configurations to enable/disable the feature. The default value is true.

• CPI enables VM boot diagnostics by default. (#377)

  You can set enable_vm_boot_diagnostics in the Azure CPI global configurations to enable/disable the feature. The default value is true.

  When it's enabled, the diagnostics logs are automatically saved to a dedicated storage account created by CPI. The log is saved for trouble shooting, even after the VM is deleted by Bosh. We recommend you cleaning up the storage account on a regular basis. For more details, see the trouble shooting doc.

• Support AzureChinaCloud AD as Azure Stack authentication. (#381)

  If you deploy your Azure Stack using Azure China Cloud Active Directory as the identity provider, you need to set azure_stack.authentication to AzureChinaCloudAD in the Azure CPI global configurations.

Fixes:

• Bump azure-core gem to 0.1.14 to fix Azure/azure-storage-ruby#118 (#375)

Documents:

• Added a document to configure Cloud Foundry external databases using Azure MySQL/Postgres Service. (#373)

Development:

• Application security group is provisioned using terraform in CI. (#372)

v35.1.0

Fixes:

• CPI returns more granulated error messages for asynchronous errors when creating a storage account. (#361)

• When the specified storage account doesn't exist, previously there is a potential race condition when CPI tries to create the storage account. CPI now handles the race condition correctly. (#365)

• Previously exceptions are ignored when creating a storage account. CPI now handles the exceptions correctly. (#365)

Documents:

• Added a document and script to collect deployment error logs. (#369)

• Added a document for the CPI method calculate_vm_cloud_properties. (#362)

Development:

• Refined the development document. (#370)

  • Added how to setup the pipeline

  • BOSH CLI v2.0.36+ is required to create a release.

v35.0.0

Features:

• Support service principal with certificate #355

• Support ADFS authentication in Azure Stack #355

• Remove the Azure Stack properties skip_ssl_validation and use_http_to_access_storage_account #354

  Users need to specify CA root certificate (ca_cert) so that CPI can verify SSL. #308

• Allow not specifying the network security group (NSG). #356, #357

  If users don't sepcify the NSG in the vm_types/vm_extensions, network and global configuration, then CPI won't associate the NSG at a VM network interface level. Users can still associate the NSG at the subnet level outside of CPI.

Fixes:

• Change the default values of fault domains (FD) and update domains (UD) to 1 for Azure Stack #353

  Only single FD and UD are supported in Azure Stack. #350

• The disk is migrated only if the disk name starts with DATA_DISK_PREFIX #352

Documents:

• Add documents for Cloud Foundry on Azure Stack #354

• Add documents for using service principal with certificate #355

v34

New Features:

• Support a new CPI method info #346

  This includes the stemcell_formats for multi-cpi support.

Fixes:

• Use azure-storage-ruby 0.12.3-preview for compatibility with current version of Azure Stack. #347, #349

  In AzureStack 1711 update, the storage data service version is 2015-04-05 which azure-storage-ruby 0.14.0-preview doesn't support. Don't use Azure CPI v30 - v33 for Azure Stack. #345

• Fix an issue of has_disk?. #344

  When the managed disk is deleted, has_disk? will throw an unexpected error instead of returning false. #339