Example Subscription and Resource Groups discovery scenarios - Adaptive Applications - BlueCat Gateway - 21.3.1

Cloud Discovery & Visibility Administration Guide

Locale
English (United States)
Product name
BlueCat Gateway
Version
21.3.1

Starting in Cloud Discovery & Visibility v21.2, you can now perform discovery at the Azure subscription level. The following topic outlines different example discovery scenarios based on each scenario.

There are 3 discovery scenarios in Azure:
  • Discovery of a specific subscription with a specific resource group.
  • Discovery of a specific subscription with all resource groups.
  • Discovery of all subscriptions with all resource groups.
Note: Within Cloud Discovery & Visibility, each resource group is a configuration with a corresponding discovery and visibility job.
In the following example scenarios outlined in this section, there are two subscriptions configured within the Azure infrastructure: eng-cloud-sub1 and eng-cloud-sub-2.
  • Subscription eng-cloud-sub-1 contains two resource groups: rg-1 and rg-2.
  • Subscription eng-cloud-sub2 contains two resource groups: rg-3 and rg-4

Discovery of a specific subscription with a specific resource group

In this scenario, eng-cloud-sub1 and resource group rg-1 are specified in the Azure Credentials page.

  1. When BLUECAT CONFIGURATION is empty and the Create Separate Configurations for Resource Groups option is checked, the discovery task imports the Azure infrastructure into Address Manager with the configuration name rg-1.
  2. When BLUECAT CONFIGURATION is set to custom-b and the Create Separate Configurations for Resource Groups option is checked, the discovery task imports the Azure infrastructure into Address Manager with the configuration name custom-b/rg-1.
  3. When BLUECAT CONFIGURATION is empty and the Create Separate Configurations for Resource Groups option is unchecked, the discovery task imports the Azure infrastructure into Address Manager with the configuration name rg-1.
  4. When BLUECAT CONFIGURATION is set to custom-d and the Create Separate Configurations for Resource Groups option is unchecked, the discovery task imports the Azure infrastructure into Address Manager with the configuration name custom-d.

Discovery of a specific subscription with all resource groups

In this scenario, eng-cloud-sub2 and all resource groups are specified in the Azure Credentials page.

  1. When BLUECAT CONFIGURATION is empty and the Create Separate Configurations for Resource Groups option is checked, the discovery task imports the Azure infrastructure into Address Manager with the two configurations named rg-3 and rg-4.
  2. When BLUECAT CONFIGURATION is set to custom-b and the Create Separate Configurations for Resource Groups option is checked, the discovery task imports the Azure infrastructure into Address Manager with two configurations named custom-b/rg-3 and custom-b/rg-4
  3. When BLUECAT CONFIGURATION is empty and the Create Separate Configurations for Resource Groups option is unchecked, the discovery task imports the Azure infrastructure into Address Manager with two configurations named rg-3 and rg-4.
  4. When BLUECAT CONFIGURATION is set to custom-2d, the Create Separate Configurations for Resource Groups option is unchecked, and the Override Configuration option is checked, the discovery task imports the Azure infrastructure into Address Manager with the a single configuration name custom-2d. This can result in unexpected errors and data loss during discovery and visibility.

    For example, if the resource group rg-3 has a virtual network of 10.2.0.0/24 with subnet 10.2.0.0/24 and resource group rg-4 has a virtual network of 10.2.0.0/24 with subnet 10.2.0.0/24 and virtual machine vm-2 linked to the subnet, after discovery and visibility is performed, only the network and subnet from rg-3 is imported into Address Manager. The 10.2.0.0/24 network and subnet from rg-4 is not imported into Address Manager; however, virtual machine vm-2 from rg-4 is imported successfully and linked to the 10.2.0.0/24 subnet of rg-3.

    If you delete the 10.2.0.0/24 virtual network of rg-3, Cloud Discovery & Visibility Azure processes the deletion of the 10.2.0.0/24 IPv4 Block in Address Manager and virtual machine vm-2 will no longer be linked to a network.

  5. When BLUECAT CONFIGURATION is set to custom-2e, the Create Separate Configurations for Resource Groups option is unchecked, and the Override Configuration option is unchecked, the discovery task imports the Azure infrastructure into Address Manager with the a single configuration name custom-2e. However, since the Override Configuration option is unchecked, an error occurs when attempting to import resource group rg-4 into Address Manager and only rg-3 is imported.

Discovery of all subscriptions with all resource groups

In this scenario, all subscriptions and all resource groups are specified in the Azure Credentials page.

  1. When BLUECAT CONFIGURATION is empty and the Create Separate Configurations for Resource Groups option is checked, the discovery task imports the Azure infrastructure into Address Manager with the four configurations named rg-1, rg-2, rg-3, and rg-4.
  2. When BLUECAT CONFIGURATION is set to custom-b and the Create Separate Configurations for Resource Groups option is checked, the discovery task imports the Azure infrastructure into Address Manager with four configurations named custom-b/rg-1, custom-b/rg-2, custom-b/rg-3, and custom-b/rg-4.
  3. When BLUECAT CONFIGURATION is empty and the Create Separate Configurations for Resource Groups option is unchecked, the discovery task imports the Azure infrastructure into Address Manager with four configurations named rg-1, rg-2, rg-3, and rg-4.
  4. When BLUECAT CONFIGURATION is set to custom-3d, the Create Separate Configurations for Resource Groups option is unchecked, and the Override Configuration option is checked, the discovery task imports the Azure infrastructure into Address Manager with the a single configuration name custom-3d. This can result in unexpected errors and data loss during discovery and visibility.

    For example, if the resource group rg-3 has a virtual network of 10.2.0.0/24 with subnet 10.2.0.0/24 and resource group rg-4 has a virtual network of 10.2.0.0/24 with subnet 10.2.0.0/24 and virtual machine vm-2 linked to the subnet, after discovery and visibility is performed, only the network and subnet from rg-3 is imported into Address Manager. The 10.2.0.0/24 network and subnet from rg-4 is not imported into Address Manager; however, virtual machine vm-2 from rg-4 is imported successfully and linked to the 10.2.0.0/24 subnet of rg-3.

    If you delete the 10.2.0.0/24 virtual network of rg-3, Cloud Discovery & Visibility Azure processes the deletion of the 10.2.0.0/24 IPv4 Block in Address Manager and virtual machine vm-2 will no longer be linked to a network.

  5. When BLUECAT CONFIGURATION is set to custom-3e, the Create Separate Configurations for Resource Groups option is unchecked, and the Override Configuration option is unchecked, the discovery task imports the Azure infrastructure into Address Manager with the a single configuration name custom-3e. However, since the Override Configuration option is unchecked, an error occurs when attempting to import resource groups rg-2, rg-3, and rg-4 into Address Manager, and only rg-1 is imported.