diff --git a/product_docs/docs/biganimal/release/getting_started/01_check_resource_limits.mdx b/product_docs/docs/biganimal/release/getting_started/01_check_resource_limits.mdx deleted file mode 100644 index 1f000f4e240..00000000000 --- a/product_docs/docs/biganimal/release/getting_started/01_check_resource_limits.mdx +++ /dev/null @@ -1,52 +0,0 @@ ---- -title: Raising Azure resource limits ---- - -By default, Azure sets a very low limit on the number of virtual machines and cores per region and on the number of Public IP Addresses per region that are available in a given subscription. - -The default number of total cores per subscription per region is 20. See [Virtual Machines limits - Azure Resource Manager](https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/azure-subscription-service-limits#virtual-machines-limits---azure-resource-manager) for more information. You need to increase the total cores to account for the total number of cores you expect to use in each region and reserve these cores to be used by EDB. See [Virtual Machine Quota Requirements](#virtual-machine-quota-requirements) for more information. - -The default Public IP address limits for Public IP Addresses Basic and Public IP Addresses Standards is set to 10. See [Public IP address limits](https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/azure-subscription-service-limits#publicip-address) for more information. You need to increase the limit of `Public IP Addresses - Basic` and `Public IP Addresses - Standard` to the total number of clusters you plan to deploy in a particular region. - - -## Virtual machine quota requirements -In each region, BigAnimal uses eight Dv4 virtual machine cores to manage your BigAnimal infrastructure. Your Postgres clusters deployed in the region use separate ESv3 virtual machine cores. The number of cores depends on the **Instance Type** and **High Availability** options of the clusters you provision. You can calculate the number of ESv3 cores required for your cluster based on the following: - -* Virtual machine instance of type E{N}Sv3 uses {N} cores. For example, an instance of type E64Sv3 uses 64 ESv3 cores. -* Cluster running on an E{N}Sv3 instance with high availability not enabled uses exactly {N} ESv3 cores. -* Cluster running on an E{N}Sv3 instance with high availability enabled uses 3 * {N} ESv3 cores. - -As an example, if you provision the largest virtual machine E64Sv3 with high availability enabled, it requires (3 * 64)=192 ESv3 cores per region. BigAnimal infrastructure requires an additional eight Dv4 virtual machine cores per region. - -## Check current utilization - -You can check whether you have adequate Azure resources to provision new clusters. - -1. In the [Azure portal](https://portal.azure.com/), select **Subscription**. -2. Select your specific subscription. -3. In the **Settings** section, select **Usage + quotas**. -4. Search for _Total Regional vCPUs_ and select the location to check the regional vCPUs limits. -5. Search for _DSv2_ and _ESv3_ to view virtual machines limits. -6. Search for Public IP to view networks limits. - - -## Increasing network quota - -You can increase the number of public IP addresses for your account either by using Azure's portal, if you have appropriate privileges, or by submitting a support request. See: - -- [Request Networking quota increase at subscription level using Help + support](https://docs.microsoft.com/en-us/azure/azure-portal/supportability/networking-quota-requests#request-networking-quota-increase-at-subscription-level-using-help--support) - -- [Request networking quota increase at subscription level using Usages + quotas](https://docs.microsoft.com/en-us/azure/azure-portal/supportability/networking-quota-requests#request-networking-quota-increase-at-subscription-level-using-usages--quotas) - - -## Increasing virtual machine quota - -You can increase the number of ESv3 Series virtual machines per region for your account either by using Azure's portal, if you have appropriate privileges, or by submitting a support request. See: - -- [Request a quota increase by region from Help + support](https://docs.microsoft.com/en-us/azure/azure-portal/supportability/regional-quota-requests#increase-a-regional-quota-from-help--support) - -- [Request a quota increase by region from subscriptions](https://docs.microsoft.com/en-us/azure/azure-portal/supportability/regional-quota-requests#increase-a-regional-vcpu-quota) - - - - diff --git a/product_docs/docs/biganimal/release/getting_started/01_preparing_azure/01_understanding_qotas_in_azure.mdx b/product_docs/docs/biganimal/release/getting_started/01_preparing_azure/01_understanding_qotas_in_azure.mdx new file mode 100644 index 00000000000..a2e3c1c0e79 --- /dev/null +++ b/product_docs/docs/biganimal/release/getting_started/01_preparing_azure/01_understanding_qotas_in_azure.mdx @@ -0,0 +1,68 @@ +--- +title: "Understanding requirements in Azure" + +--- + +The following sections explain BigAnimal's requirements and recommended resource limits in Azure. + +## Azure Service Provider registrations + +BigAnimal creates and manages some of the Azure resources using service providers. For example, if you want to store keys you require the Microsoft.KeyVault service provider. This service provider offers a resource type called vaults for creating the key vault. For more information, see [Azure resource providers and types](https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/resource-providers-and-types). + +To prevent failures while creating your clusters, ensure that each of the following Azure Service Providers are registered in your Azure subscription. + + +| Provider Namespace | Description | +| ------------------------------ | --------------------------------------------------------------------------------------------------------------- | +| Microsoft.Compute | Runs cluster workloads on a virtual machine managed by the Azure Kubernetes Service. +Microsoft.Capacity | Checks the Azure resource quota. | +Microsoft.AlertsManagement | Monitors failure anomalies. | | +| Microsoft.ContainerService | Manages cluster workloads run on the Azure Kubernetes Service. | +| Microsoft.KeyVault | Encrypts and stores keys of the clusters' data volume and Azure's credential information. | +| Microsoft.Storage | Backs up data to the Azure Service Account. | +| Microsoft.ManagedIdentity | Manages software access to the local Azure services using Azure Managed-Identity. | +| Microsoft.Network | Manages cluster workloads run in the Azure Kubernetes Service in the dedicated VNet. | +| Microsoft.OperationalInsights | Manages clusters and performs workload logging (log workspace).. | +| Microsoft.OperationsManagement | Monitors workloads and provides container insight. | +| Microsoft.Portal | Provides a dashboard to monitor the running status of the clusters (using aggregated logs and metrics). | + +## Virtual machine SKU restrictions + +When you deploy your clusters in HA mode, BigAnimal uses multiple availability zones in the region where you plan to deploy the cluster. Ensure that all regions designated for the deployment of your clusters have no virtual machine SKU restrictions for the Esv3 and Dv4 VM size families in zone 1, 2, and 3. + +## Public IP addresses limits + +Every BigAnimal cluster with public network access is assigned a single public IP address, and this IP address counts against the quota for both *Basic* and *Standard* IP address types in a region. BigAnimal cannot create more clusters if the IP address limit is reached. + +##### Default Azure limit + +The default Public IP addresses limits for *Basic* and *Standard* type are set to 10. See [Public IP address limits](https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/azure-subscription-service-limits#publicip-address) for more information. + +##### Recommended limit + +EDB recommends that you increase the Public IP addresses limits for *Basic* and *Standard* type to 50. For a requirement of more than 50 clusters, ensure that you increase the limit to the number of clusters you plan to deploy. + +## vCPU limits + +Any time a new VM is deployed in Azure, the vCPUs for the VMs must not exceed the total vCPU limits for the region. + +Clusters deployed in the region use Esv3 virtual machine cores. The number of cores depends on the *Instance Type* and *High Availability (HA)* options of the clusters. You can calculate the number of Esv3 cores required for your cluster based on the following: + +* A virtual machine instance of type E{N}sv3 uses {N} cores. For example, an instance of type E64sv3 uses 64 Esv3 cores. +* A cluster running on an E{N}sv3 instance with HA not enabled uses exactly {N} Esv3 cores. +* A cluster running on an E{N}sv3 instance with HA enabled uses 3 * {N} Esv3 cores. + +For example, if you provision the largest virtual machine E64sv3 with high availability enabled, it requires (3 * 64) = 192 Esv3 cores per region. + +BigAnimal requires an additional eight Dv4 virtual machine cores per region. + +##### Default limit + +The default number of total vCPU (cores) per subscription per region is 20. For more information, see [Virtual Machines limits - Azure Resource Manager](https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/azure-subscription-service-limits#virtual-machines-limits---azure-resource-manager). + +##### Recommended limits + +BigAnimal recommends the following per region when requesting virtual machine resource limit increases: +* Total Regional vCPUs: minimum of 60 per designated region +* Standard Esv3 Family vCPUs: minimum of 50 per designated region +* Standard Dv4 Family vCPUs: minimum of 10 per designated region \ No newline at end of file diff --git a/product_docs/docs/biganimal/release/getting_started/01_preparing_azure/index.mdx b/product_docs/docs/biganimal/release/getting_started/01_preparing_azure/index.mdx new file mode 100644 index 00000000000..b6e5fa6137f --- /dev/null +++ b/product_docs/docs/biganimal/release/getting_started/01_preparing_azure/index.mdx @@ -0,0 +1,200 @@ +--- +title: "Preparing your Azure account" +redirects: + - ../01_check_resource_limits +--- + +BigAnimal requires you to configure your Azure subscription before you deploy your clusters. The configurations that you perform ensure that your Azure subscription is prepared to meet your clusters' requirements and resource limits, such as: + + * Are the necessary Azure Service Providers registered for your subscription? + * Is there a restriction on SKUs for the Standard Esv3 and Standard Dv4 VM size families? + * Is there a sufficient limit on the number of vCPU or Public IP addresses in your region? + +!!! Note + Before proceeding, see [Understanding requirements in Azure](../01_preparing_azure/01_understanding_qotas_in_azure) for details on planning for your clusters' requirements and resource limits in Azure. + +## Check for requirements + +EDB recommends using the `biganimal-preflight-azure` script to check whether all requirements and resource limits are met in your subscription. However, you can also manually check the requirements using the Azure CLI or the Azure Portal. + + * [Method 1: Use EDB's shell script](#method-1-use-edbs-shell-script) (recommended) + * [Method 2: Manually check requirements](#method-2-manually-check-requirements) + +### Method 1: Use EDB's shell script + +EDB provides a shell script called [`biganimal-preflight-azure`](https://github.com/EnterpriseDB/cloud-utilities/blob/main/azure/biganimal-preflight-azure), which automatically checks whether requirements and resource limits are met in your Azure subscription based on the clusters you plan to deploy. + +1. Open the [Azure Cloud Shell](https://shell.azure.com/) in your browser. + +1. From the Azure Cloud Shell, use the following command to run the `biganimal-preflight-azure` script. + + ```sh + curl -sL https://raw.githubusercontent.com/EnterpriseDB/cloud-utilities/main/azure/biganimal-preflight-azure | bash -s \ + -- \ + --instance-type \ + --high-availability \ + --endpoint \ + --activate-region \ + --onboard + ``` + + Replace the variables in the arguments and options as follows: + - ``: Enter the Azure subscription ID of your BigAnimal deployment. + - ``: Enter the Azure region where your clusters are being deployed. + - ``: Enter **e2s_v3**, which indicates the type of virtual machine instance (Esv3 with 2 cores) used in BigAnimal. + - `--high-availability` or `-a`: Indicates that high availability is enabled in your clusters. + - ``: Indicates either **public** or **private** endpoints. + - `--activate-region` or `-r`: Indicates that no clusters are currently deployed in the region. + - `--onboard`: Checks if the user and subscription are correctly configured. + + For example, if you want to deploy a cluster in an Azure subscription having an ID of `12412ab3d-1515-2217-96f5-0338184fcc04`, in the `eastus2` region, in a `public` network, and with no existing cluster deployed, run the following command: + + ```sh + curl -sL https://raw.githubusercontent.com/EnterpriseDB/cloud-utilities/main/azure/biganimal-preflight-azure | bash -s \ + -- 12412ab3d-1515-2217-96f5-0338184fcc04 eastus2 \ + --instance-type e2s_v3 \ + --high-availability \ + --endpoint public \ + --activate-region + ``` + +The script displays the following output: + + * A list of required Azure Service Providers and their registeration status. Ensure that you register the service providers that are displayed as `NotRegistered` in the `RegistrationState` column. See [Register Azure service providers](#register-azure-service-providers). + ``` + ####################### + # Provider # + ####################### + + Namespace RegistrationPolicy RegistrationState ProviderAuthorizationConsentState + --------------------------------------- -------------------- ----------------- + Microsoft.Capacity RegistrationRequired NotRegistered + Microsoft.ContainerInstance RegistrationRequired NotRegistered + Microsoft.Compute RegistrationRequired NotRegistered + Microsoft.ContainerService RegistrationRequired NotRegistered + Microsoft.KeyVault RegistrationRequired NotRegistered + Microsoft.ManagedIdentity RegistrationRequired NotRegistered + Microsoft.Network RegistrationRequired NotRegistered + Microsoft.OperationalInsights RegistrationRequired NotRegistered + Microsoft.OperationsManagement RegistrationRequired NotRegistered + Microsoft.Portal RegistrationFree Registered + Microsoft.Storage RegistrationRequired Registered + Microsoft.AlertsManagement RegistrationRequired NotRegistered + ``` + + + * Whether your Azure subscription restricts vCPUs for the `Standard_D2_v4` and `Standard_E2s_v3` VM size families in your region (and availability zone, if HA is enabled). Open a support request to remove SKU restrictions for the VM families with `NotAvailableForSubscription` displayed in the `Restrictions` column. See [Fix issues with SKU restrictions](#fix-issues-with-sku-restrictions). + ``` + ####################### + # Virtual-Machine SKU # + ####################### + + ResourceType Locations Name Zones Restrictions + ------------ --------- ---- ----- ------------ + virtualMachines eastus2 Standard_D2_v4 1,2,3 None + virtualMachines eastus2 Standard_E2s_v3 1,2,3 NotAvailableForSubscription, type: Zone, locations: eastus2, zones: 1,3 + + ``` + + * Whether your Azure subscription has sufficient limits on vCPUs and IP addresses for your region. Open a support request to raise limits for the vCPUs and IP addresses if they exceed the available VM families with `NotAvailableForSubscription` displayed in the `Restrictions` column. See [Increase Public IP addresses](#increase-public-ip-addresses-limits) and [Increase vCPU limits](#increase-vcpu-limits). + + ``` + ####################### + # Quota Limitation # + ####################### + + Resource Limit Used Available Gap Suggestion + Total Regional vCPUs 130 27 103 89 OK + Standard D2v4 Family vCPUs 20 14 6 0 Need Increase + Standard E2sv3 Family vCPUs 20 4 16 8 OK + Public IP Addresses — Basic 20 11 9 8 OK + Public IP Addresses — Standard 20 3 17 16 OK + ``` + + +### Method 2: Manually check requirements +If you are manually checking the requirements instead of using the `biganimal-preflight-azure` script, perform the following procedures: + +#### Check Azure Service Provider registrations using Azure Cloud Shell + +To check if a Azure service provider is registered in Azure use the following command. + +``` +az provider show -n Microsoft.ContainerService + +Namespace RegistrationPolicy RegistrationState +-------------------------- -------------------- ------------------- +Microsoft.ContainerService RegistrationRequired Registered + +``` + +#### Check for vCPU restrictions for the VM size family + +You can check vCPU limits for the VM size family using the Azure Cloud Shell. For example, to check the Standard_D2_v4 VM SKU restriction in `eastus2` location for all zones, run the following command: + +```sh +az vm list-skus -l eastus2 --zone --size Standard_D2_v4 + +ResourceType Locations Name Zones Restrictions +--------------- ----------- --------------- ------- ------------ +virtualMachines eastus2 Standard_D2_v4 1,2,3 NotAvailableForSubscription, type: Zone, locations: eastus2, zones: 3,2 +``` + +Alternatively, to check for SKU restrictions using the Azure Portal, see [Solution 3 - Azure portal](https://docs.microsoft.com/en-us/azure/azure-resource-manager/templates/error-sku-not-available#solution-3---azure-portal). + +#### Check the resource limits for vCPUs and Public IP Addresses for your region + +To check if you have adequate Azure resources to provision new clusters: + +1. In the [Azure Portal](https://portal.azure.com/), select **Subscription**. +2. Select your specific subscription. +3. Select **Usage + quotas** in the **Settings** section. +4. Search for *Total Regional vCPUs* and select the **Location** to check the regional vCPUs limits. +5. Search for *Dv4* and *Esv3* to view virtual machine limits. +6. Search for Public IP addresses to view network limits. + +## Configure your Azure subscription + +After checking whether the requirements and resource limits are met, configure your Azure subscription. + +!!! Note + Before proceeding, see [Understanding requirements in Azure](../01_preparing_azure/01_understanding_qotas_in_azure) for details on planning for your clusters' requirements and resource limits in Azure. + +### Register Azure Service Providers +To register Service Providers using the Azure Portal: + +1. In the [Azure Portal](https://portal.azure.com/), select **Subscription**. +2. Select your specific subscription. +3. In the navigation panel **Settings** group, select **Resource providers**. +4. Review the status of the required providers. To register a provider, select the provider, and, on the top menu, select **Register**. + +To register Service Providers using the Azure CLI, +use the [register command](https://docs.microsoft.com/en-us/cli/azure/provider?view=azure-cli-latest#az_provider_register). For example: + +```sh +az provider register -n Microsoft.ContainerService +Registering is still on-going. You can monitor using 'az provider show -n Microsoft.ContainerService +``` + +### Fix issues with SKU restrictions + +[Open a support request](https://docs.microsoft.com/en-us/troubleshoot/azure/general/region-access-request-process) to remove SKU restrictions in a particular region. + +### Increase Public IP Addresses limits + +Increase the limit of `Public IP Addresses - Basic` and `Public IP Addresses - Standard` for the regions where you plan to deploy your clusters with the total number of clusters you plan to use. + +You can increase the number of public IP addresses for your account either by using the Azure portal or by submitting a support request. See: + +* [Request networking quota increase at subscription level using Usages + quotas](https://docs.microsoft.com/en-us/azure/azure-portal/supportability/networking-quota-requests#request-networking-quota-increase-at-subscription-level-using-usage--quotas) + +* [Request Networking quota increase at subscription level using Help + support](https://docs.microsoft.com/en-us/azure/azure-portal/supportability/networking-quota-requests#request-networking-quota-increase-at-subscription-level-using-help--support) + + +### Increase vCPU limits + +You can increase the number of Dv4 or Esv3 family virtual machines per region by using the Azure Portal or by submitting a support request. See: + + * [Request a quota increase at a subscription level using Usages + quotas](https://docs.microsoft.com/en-us/azure/azure-portal/supportability/classic-deployment-model-quota-increase-requests#request-quota-increase-for-the-classic-deployment-model-from-usage--quotas) + + * [Request a quota increase by region from Help + support](https://docs.microsoft.com/en-us/azure/azure-portal/supportability/regional-quota-requests#request-a-quota-increase-by-region-from-help--support) diff --git a/product_docs/docs/biganimal/release/getting_started/images/SKUNotAvailable.png b/product_docs/docs/biganimal/release/getting_started/images/SKUNotAvailable.png new file mode 100644 index 00000000000..af8493643c6 --- /dev/null +++ b/product_docs/docs/biganimal/release/getting_started/images/SKUNotAvailable.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:783eff6922a252c850c85b23e7fa244d07345f673033ab8e3606da0c9442548c +size 300789 diff --git a/product_docs/docs/biganimal/release/getting_started/images/assign-roles.png b/product_docs/docs/biganimal/release/getting_started/images/assign-roles.png deleted file mode 100644 index 8d04df0cb41..00000000000 --- a/product_docs/docs/biganimal/release/getting_started/images/assign-roles.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c2c1b79bb06257df4ddb28e9b93316fabc5240727b34d884e1816ec4734ee64c -size 49339 diff --git a/product_docs/docs/biganimal/release/getting_started/images/clusters.png b/product_docs/docs/biganimal/release/getting_started/images/clusters.png deleted file mode 100644 index 5630738020a..00000000000 --- a/product_docs/docs/biganimal/release/getting_started/images/clusters.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:efd4e3cc5d4ed1a5b4d59bdeca7226304b554d8b66bdd2abc28a900870f213dd -size 66049 diff --git a/product_docs/docs/biganimal/release/getting_started/images/create-cluster-1.png b/product_docs/docs/biganimal/release/getting_started/images/create-cluster-1.png deleted file mode 100644 index 83c5df26799..00000000000 --- a/product_docs/docs/biganimal/release/getting_started/images/create-cluster-1.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c15d2826de005a40a0192802e2a444eb5d7391e5efe2df84ea721778f932f5b -size 86948 diff --git a/product_docs/docs/biganimal/release/getting_started/images/create-cluster-2.png b/product_docs/docs/biganimal/release/getting_started/images/create-cluster-2.png deleted file mode 100644 index e26442434fe..00000000000 --- a/product_docs/docs/biganimal/release/getting_started/images/create-cluster-2.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:27e7c6e20c3526e9b14d5e50909e7d779f4ddd40b334587dcc316726942ebd23 -size 78499 diff --git a/product_docs/docs/biganimal/release/getting_started/images/edbcloud.png b/product_docs/docs/biganimal/release/getting_started/images/edbcloud.png deleted file mode 100644 index feaa2e0f6af..00000000000 --- a/product_docs/docs/biganimal/release/getting_started/images/edbcloud.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ad606ecae8f612ecefb25faa69778752822abd217aef4783290d3f7036b3697e -size 33814 diff --git a/product_docs/docs/biganimal/release/getting_started/images/marketplace-preview.png b/product_docs/docs/biganimal/release/getting_started/images/marketplace-preview.png deleted file mode 100644 index 5d4eea5dcca..00000000000 --- a/product_docs/docs/biganimal/release/getting_started/images/marketplace-preview.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:25fbcb44bffd12dcb02b34e25c21cb9bc09d35d20de7427fbdfcddaaeeb3d158 -size 39126 diff --git a/product_docs/docs/biganimal/release/getting_started/images/quotalimitation.png b/product_docs/docs/biganimal/release/getting_started/images/quotalimitation.png new file mode 100644 index 00000000000..c6d0e00cf4f --- /dev/null +++ b/product_docs/docs/biganimal/release/getting_started/images/quotalimitation.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f42f781ddd6e22b497c608e6bd1d5ce5ac849785cbf6658a7cb78f1db14cc1e0 +size 88152 diff --git a/product_docs/docs/biganimal/release/getting_started/images/raising-limits-video.png b/product_docs/docs/biganimal/release/getting_started/images/raising-limits-video.png deleted file mode 100644 index 399c6d9b69d..00000000000 --- a/product_docs/docs/biganimal/release/getting_started/images/raising-limits-video.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:24764ccb2ba37c72b41a81f2c3e7d7a23993a13282ebfb4ae10187537c2e429a -size 488736 diff --git a/product_docs/docs/biganimal/release/getting_started/images/roles.png b/product_docs/docs/biganimal/release/getting_started/images/roles.png deleted file mode 100644 index 54ce305b9f8..00000000000 --- a/product_docs/docs/biganimal/release/getting_started/images/roles.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:67f855b34e09ba465e6b17a25aeaef6c28a0210a27c72b86f85b2748faacfa99 -size 47295 diff --git a/product_docs/docs/biganimal/release/getting_started/images/setup-edbcloud.png b/product_docs/docs/biganimal/release/getting_started/images/setup-edbcloud.png deleted file mode 100644 index d5f3789ce5d..00000000000 --- a/product_docs/docs/biganimal/release/getting_started/images/setup-edbcloud.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1f6714986e1cfae9330ca6e9804b18b160390f6f14d17f876c0408141f7bb8e0 -size 76128 diff --git a/product_docs/docs/biganimal/release/getting_started/images/subscribe-to-dbaas.png b/product_docs/docs/biganimal/release/getting_started/images/subscribe-to-dbaas.png deleted file mode 100644 index 98f0fbe1908..00000000000 --- a/product_docs/docs/biganimal/release/getting_started/images/subscribe-to-dbaas.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:126318b8dba65be21b624ae49e5e74ee1bddb93eb0ecdc16766d2e93febcdcf7 -size 80494 diff --git a/product_docs/docs/biganimal/release/getting_started/images/subscription-process.png b/product_docs/docs/biganimal/release/getting_started/images/subscription-process.png deleted file mode 100644 index 92db0dfc4ce..00000000000 --- a/product_docs/docs/biganimal/release/getting_started/images/subscription-process.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2f96c2121786f0b7d5fff627ff22f3993f6563407567f7ce2fc52550102d749b -size 68212 diff --git a/product_docs/docs/biganimal/release/getting_started/images/users.png b/product_docs/docs/biganimal/release/getting_started/images/users.png deleted file mode 100644 index 5d00a9e7bcc..00000000000 --- a/product_docs/docs/biganimal/release/getting_started/images/users.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:064865d5ac5192fd7a772fe5c8765e445e4577093ab73001192a8c2bed83b655 -size 55022