![]() ![]() For more information about the vCore model, see the Microsoft documentation. Note Azure SQL service instances use the vCore model and the Gen5 hardware generation unless you override this default by using the sku_name parameter. The table below shows the mapping of the number of cores to the corresponding Azure SKU: Coresįor a list of all valid SKUs, run: az sql db list-editions -l LOCATION -o tableįor information about the vCore purchasing model, see this Microsoft documentation.įor information about the DTU purchasing model, see this Microsoft documentation. If you do not define a SKU using the sku_name parameter, the SKU is computed from the number of cores in your plan. Where:Įxample SKUs are GP_S_Gen4_1 and GP_Gen5_8. Stock-keeping units (SKU) are usually formatted as TIER_FAMILY_NUMBER-OF-CORES. For more information about storage auto-grow, see the Microsoft documentation Initial storage sizes are per plan. Set if the service principal being used does not have the rights to register providers. Set to true to skip automatic Azure provider registration. For more information about configuring this parameter, see SKUs section. Maximum storage allocated to the database instance in GB. Number of vCores for the instance (up to the maximum allowed for the service tier). The subnet ID, in long form, of the Azure Virtual Network (VNet) or subnet that is attached to this instance to allow remote access. The value the operator entered for Client Secret in Ops Manager. The secret (password) for the Azure service principal to authenticate for service instance creation. The value the operator entered for Client ID in Ops Manager. ![]() The ID of the Azure service principal to authenticate for service instance creation. The value the operator entered for Subscription ID in Ops Manager. The ID of the Azure subscription for the service instance. The value the operator entered for Tenant ID in Ops Manager. The ID of the Azure tenant for the service instance. The Azure resource group in which to create the instance. If you configure a region that is unavailable, Cloud Service Broker for Azure fails. Important Currently, Azure SQL is not available in all regions. The Azure region in which to deploy the service instance. The name of the Azure instance to create. The table below lists the parameters that you can configure, using the -c flag, when provisioning a csb-azure-postgresql service: Parameter Name You can provision a service by running: cf create-service csb-azure-postgresql PLAN-NAME SERVICE-INSTANCE-NAME -c '' Note If you set a parameter at plan level, developers cannot change the value when creating or updating service instances. The following properties are useful to set in a plan: postgres_version, storage_gb, cores, sku. You can also add any of the configuration parameters listed in the parameters section to your plan. List of bullet points to display in Apps Manager. Name to use when displaying the plan in the Marketplace. The following table lists parameters which can only be configured for additional plans: Parameter Name For how to configure plans, see Configure Services with Cloud Service Broker for Azure. When configuring Cloud Service Broker for Azure you can add additional plans. ![]() The table below lists the plans available for the csb-azure-postgresql service: Plan It details the plans, configuration parameters, and binding credentials. This topic gives you reference information about the Azure PostgreSQL service (csb-azure-postgresql). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |