Unlocking Nested Virtualization in Azure: A Step-by-Step Guide

Azure

Nested virtualization in Azure is a powerful feature that enables running a Hyper-V hypervisor within an Azure virtual machine (VM). This capability is invaluable for developers, machine learning engineers, and data scientists who require flexible and scalable environments for testing, development, or containerized applications. This post provides a step-by-step guide to setting up nested virtualization, ensuring you can leverage its full potential.


Prerequisites and Supported VM Sizes

Before diving into the setup, ensure you choose an Azure VM that supports nested virtualization. Compatible VM sizes include:

  • Dv3, Dsv3
  • Dv4, Dsv4
  • Ddv4, Ddsv4
  • Ev3, Esv3
  • Ev4, Esv4
  • F2s_v2 to F72s_v2
  • FX4 to FX48
  • M series

For most use cases, the Dv3 and Ev3 series are excellent choices. Make sure the VM size meets the system requirements for your intended workloads, such as Docker Desktop.


Step 1: Deploying an Azure VM

  1. Create the VM:
    • Log in to the Azure Portal.
    • Select a Windows Server image and choose a compatible VM size.
  2. Configure Networking:
    • Set up the required inbound and outbound port rules.
  3. Deploy:
    • Review your configuration and deploy the VM.

Continue reading “Unlocking Nested Virtualization in Azure: A Step-by-Step Guide”

Azure Introduces Terraform Export Feature in Private Preview: A New Era for DevOps and IaC

AzTfm

Microsoft Azure has taken a significant step forward for Infrastructure as Code (IaC) enthusiasts with the latest private preview feature in the Azure Portal – the ability to export Terraform configurations directly. Previously, exporting configurations was limited to ARM templates, but now you can generate Terraform and Bicep configurations right from the portal. This enhancement makes Azure even more accessible and streamlined for DevOps workflows.

Currently in Private Preview

The new export feature is currently in private preview, so it’s not yet available to all users. However, Microsoft is preparing to announce the public preview very soon, making this tool accessible to a wider audience. In the meantime, if you want to stay updated on the latest news and announcements about this feature, you can sign up to receive updates directly from Microsoft using this form.

Why is This a Game-Changer?

For years, Azure users could only export configurations as ARM templates, which are powerful but have a steeper learning curve compared to Terraform. With Terraform’s growing popularity due to its flexibility and cross-platform capabilities, Microsoft’s decision to introduce direct Terraform exports marks a shift towards more inclusive DevOps practices.

This new capability not only simplifies the process of moving to Terraform but also bridges the gap for teams transitioning from ARM templates to more modern IaC approaches. Automating and streamlining this process accelerates workflows, reduces human error, and empowers teams to better manage their cloud infrastructure.

Continue reading “Azure Introduces Terraform Export Feature in Private Preview: A New Era for DevOps and IaC”

Integrate Other Clouds with Azure Using the Multicloud Connector

multi-cloud

Introduction

As businesses adopt multi-cloud strategies to leverage the unique strengths of various cloud providers, managing these environments can become complex. Microsoft’s Azure Arc Multicloud Connector provides a streamlined solution to integrate and manage resources across different cloud platforms, specifically focusing on AWS. This blog post will explore the capabilities of the Azure Arc Multicloud Connector and guide you through a step-by-step lab to connect AWS resources to Azure.

Key Features of the Multicloud Connector

1. Unified Inventory: The Multicloud Connector automatically collects metadata from external cloud resources, providing a comprehensive view within the Azure portal. This helps in maintaining a consistent inventory across cloud environments.
2. Arc Onboarding: It facilitates the onboarding of AWS EC2 instances to Azure Arc, allowing advanced management features like policy enforcement, monitoring, and configuration management.
3. Consistent Governance: Apply Azure policies and role-based access controls (RBAC) to resources in external clouds, ensuring uniform security and compliance standards across all environments.
4. Enhanced Management: Utilize Azure Arc capabilities for onboarded resources, including vulnerability scanning and deployment automation.

Implementation Steps

Prerequisites

– An Azure subscription with Contributor access.
– An AWS account with AmazonEC2FullAccess permissions.
– Azure Arc and required resource providers registered (Microsoft.HybridCompute, Microsoft.HybridConnectivity, Microsoft.AwsConnector).

image

Continue reading “Integrate Other Clouds with Azure Using the Multicloud Connector”

Cisco CUCM – Reports from SQL (show risdb)

Hey guys,

In my last post, I gave you some tips on how pull CDRs out from CUCM using SQL commands (Cisco CUCM – CDR through SQL). Today, I’m going to show other useful reports you can get using SQL commands.

As we are getting all the information from a CLI command, you will need to export the data to an excel file  to create something nice to be presented….or even use Python, PHP, to create something automatic for you.

Today I’m going to focus on one command, but with different variables and outputs: show risdb
This command displays RIS database table information.

Parameters

list : displays the tables that are supported in the Realtime Information Service (RIS) database.
query : displays the contents of the RIS tables

So, if you enter the command show risdb list, you will see a list of options in the table that you can explore.

image

The most common, and used, is the Phone.
To access this table, you must use this command: show risdb query phone.

image

This command is so powerful and useful!!! Here we see everything related to your phones: DeviceName, Descr, Ipaddr, Ipv6addr, Ipv4Attr, Ipv6Attr, MACaddr, RegStatus, PhoneProtocol, DeviceModel, HTTPsupport, #regAttempts, prodId, username, seq#, RegStatusChg TimeStamp, IpAddrType, LoadId, ActiveLoadId, InactiveLoadId, ReqLoadId, DnldServer, DnldStatus, DnldFailReason, LastActTimeStamp, Perfmon Object.

In other words, you can have a list of devices in your Cluster, check each phone is currently Registered or Unregistered, and its information such as IP, Protocol, Model……an excellent Report Smile

But, if you want to explore it a bit more, there are other interesting queries!
For example, if you want to have a report about your SIP Trunks, you can use this command: show risdb query sip.

Here you have information about your SIP Trunk, such as name, IPs, descriptions, Status, Peer Status.

This is the Trunk on CUCM:

image

image

The Status column (in red) corresponds to the “Service Status” field visible near the top of CCMAdmin’s SIP Trunk page.

0 – No service (The Trunk peer is reachable via TCP, but SIP Options ping is failing)
1 – Full service (All Trunk peers are up and SIP Options ping is successful)
2 – Partial service (A subset of Trunk peers are unreachable)
3 – Unknown (The Trunk peer is unreachable via TCP, or SIP Options ping is not enabled)

image

The PeerStatus column (in blue) corresponds to the “Status” field for each peer on the SIP Trunk page (near the bottom).

0 – Down
1 – Up

Now it’s up to you to choose a query from RSIDB list and start to explore it. You will find interesting options there, like CTIs, Gateways…..

Hope you’ve enjoyed it Smile

See ya!

Bruno