How to Identify Azure Elements Provisioned by Agora¶

The identifiers of the Azure elements provisioned by Agora in your Azure account can be obtained using the Agora Solution Manager, which can be opened by selecting the Manage environments button in the Environments section of your Agora subscription.

From the Agora Solution Manager, selecting the Overview option from the Environments menu displays an Overview of your environment. Clicking the button located next to the name of a cluster displays a summary of the main Azure elements provisioned by Agora for the cluster.

From the Overview, the Actions drop-down for each cluster includes an option to View all events. Selecting this option opens the Cluster events page displaying all the events for the cluster. A detailed list of the steps executed can be viewed by selecting the button for each event. Selecting the Execution output option under the Output drop-down for a step, lists details of the Azure elements provisioned in the step.

For example, to identify a particular Azure element created during a Cloud cluster creation event, expand the event and search the displayed details for the step with the desired Azure element in its name. The Execution output for the step will list the Azure identifier for the created element.

In the following image we can see an example of how to find the Azure identifier of a Virtual DataPort Network security group created during an event step.

List of Azure Elements Created by Agora in the User’s Account¶

This section lists all the dependent Azure elements created and used by Agora for a deployment. Agora does not create any App registrations, these must be created by the user for subsequent use by Agora.

The list is divided into two sections, one listing the elements which imply costs and one that lists elements that do not. A brief description for each element provided summarizing their role in the Agora deployment. Each element’s name is a hyperlink to more detailed information about their pricing.

Azure elements that do not imply costs:

• App registration: Identity to securely interact with Azure services and APIs. Please check the Azure section of the Agora Quick Start Guide for further details.

• Custom role: User-defined set of permissions to grant fine-grained access to Azure resources. Please check the Azure section of the Agora Quick Start Guide for further details.

• Availability set: Logical grouping of Azure Virtual Machines that allows Azure to distribute them across multiple physical hardware components in a single datacenter.

• Network Interface: An Azure Network Interface is a key component that enables an Azure Virtual Machine to communicate with other resources. It is the bridge that connects a Virtual Machine to a Virtual Network.

• Network security group: Its purpose is to filter network traffic to and from Azure resources, such as Virtual Machines, based on a set of security rules. They include the ports of each service, for example ports 9443 or 9090 for Denodo Virtual DataPort.

• Subnet: Subnet used by the Execution Plane. Optionally, Agora can create the Subnet or existing one can be used.

• Virtual machine scale set: Used when auto scaling is enabled, grouping Azure Virtual Machines for use during auto scaling.

• Virtual network: Virtual Network used by the Execution Plane. Optionally, Agora can create the Virtual Network or existing one can be used.

Azure elements that imply costs:

• Disk: Virtualized, block-level storage volume used with an Azure Virtual Machine. It functions just like a physical hard drive in a traditional on-premises server, but it’s managed by Azure. Azure Virtual Machine disks are a crucial component for any Virtual Machine, as they provide the persistent storage needed for the operating system, applications, and data.

• Image: Azure images are created for the configuration of TLS and some processes such as updating the Execution Plane. An Azure image is a template that provides the operating system, and often pre-installed applications and configurations, for a Virtual Machine. Azure images do not imply direct costs, however, The storage consumed by the image does have a cost implication.

• Load balancer: An Azure Load Balancer distributes incoming network traffic across virtual machines, to ensure high availability and scalability for your applications.

• NAT gateway: An Azure NAT Gateway is a fully managed, highly resilient, and scalable service that provides outbound-only internet connectivity for virtual networks. It’s the recommended method for providing secure and controlled outbound access for resources in a private subnet.

• Public IP address: For public communications between the internet and the Virtual Machines.

• Virtual machine: Azure Virtual Machines to host the Denodo services.

Azure Elements Created Deploying with Agora Production Template¶

Using a deployment with an Agora production template as an example. This template deploys 3 environments. One environment for development, with 1 Virtual DataPort and 1 Data Marketplace; and another two environments, staging and production, both with 1 Virtual DataPort, 1 Data Marketplace and 1 Scheduler. In this example we are choosing to create new Virtual Networks and subnets.