MS Azure Administrator AZ 104 Day-6 Session Tamil | Azure Virtual Machine Create & Overview & Types

Azure Virtual Machine Deployment Overview

Introduction to Azure Virtual Machines

• The session focuses on deploying Azure Virtual Machines (VMs), explaining how to create them and their purpose in running applications.

• The Azure portal is introduced as the platform from which VMs can be created, emphasizing the need for VMs in various application projects.

Purpose of Virtual Machines

• VMs are essential for installing and running application projects, serving as a simple concept within cloud computing.

• The physical infrastructure of Azure's data centers is discussed, highlighting the presence of numerous physical servers that host these virtual machines.

Data Center Infrastructure

• Physical servers are organized in racks within Azure data centers, illustrating the structured environment where VMs operate.

• A visual representation of the Azure portal is provided, showing how users can create a VM through this interface.

Components Required for a Virtual Machine

• Key components necessary for creating a VM include hardware resources such as RAM and CPU.

• Minimum requirements are specified: 2 GB RAM is needed to run a VM effectively, with higher specifications recommended based on usage needs.

Storage Requirements

• Storage options are explained; every VM requires disk space similar to hard drives found in personal computers.

• An OS disk is automatically created when setting up a VM, typically allocated around 128 GB by default.

Additional Disk Options

• Users may require additional disks for storing application-related files separately from the OS disk. These extra disks are referred to as "data disks" and have minimum size recommendations starting at 4 GB.

Virtual Machine Setup and Requirements

Disk Size and Network Connectivity

• The maximum disk size that can be allocated is 32 TB, which should be kept in mind for current setups. An additional data disk of 100 GB can also be created.

• A network interface card (NIC) is essential for connecting to the virtual machine (VM). Without it, access to the VM will not be possible.

• To connect to the internet via Wi-Fi, a driver must be installed on the laptop; without this driver, Wi-Fi connectivity will not function properly.

• Ethernet cables can also provide network connectivity when connected to the appropriate port on the laptop. This connection allows internet access through wired means.

• For proper detection of network connections, drivers for the network interface card must be installed; otherwise, connectivity issues may arise.

Importance of Network Interface Card

• The presence of a network interface card is crucial as it enables internet connectivity necessary for accessing virtual machines.

• An operating system (OS), such as Windows 2022, is required for running applications within the virtual machine environment.

Virtual Machine Components and Types

• Understanding components and prerequisites for creating a virtual machine is vital. These include hardware specifications and software requirements.

• Different types of virtual machines exist based on project requirements. Examples include gaming laptops or video editing systems that require specific configurations.

Scenarios and Use Cases

• Gaming laptops need specialized graphics drivers to run games effectively; standard laptops may not support these requirements due to insufficient specifications.

• Various types of virtual machines are available; one type mentioned is "computer optimized," which provides common setup requirements suitable for medium-level projects.

General Purpose Virtual Machines

• Computer optimized VMs are designed for general-purpose use but may not handle large-scale projects efficiently; they are best suited for medium-level tasks.

• Naming conventions help identify different types of VMs. For instance, those starting with "PS" indicate general-purpose computers suitable for various applications.

This structured overview captures key insights from the transcript while providing timestamps linked directly to relevant sections in order to facilitate further exploration or review.

Understanding CPU Optimization in General Purpose Machines

Overview of General Purpose Machines

• The speaker introduces the concept of general-purpose machines, explaining that they may cause confusion due to their specifications.

• These machines typically have optimized CPUs but limited memory compared to gaming systems, which require more processing power for software execution.

Importance of Processor Quality

• The discussion highlights the use of low-quality processors like Intel Pentium in laptops, which can lead to performance issues when running demanding applications.

• A good quality processor is essential for optimal performance; otherwise, applications may hang or fail to run efficiently.

Understanding CPU Optimization

• CPU optimization refers to having multiple processors allocated for running applications effectively. More processors allow better handling of tasks and improve overall performance.

• Applications requiring significant processing power cannot run smoothly on standard general-purpose machines without proper optimization.

Memory Optimization Explained

• Similar to CPU optimization, memory optimization ensures that sufficient memory space is available for applications. Low internal memory can lead to system hang-ups.

• When multiple applications are open simultaneously, each requires a certain amount of memory allocation; thus, balanced memory usage is crucial for server operations.

Types of Virtual Machines and Their Uses

• Different types of virtual machines are discussed based on specific requirements: general purpose (for basic tasks), specialized (for high-demand applications), and storage optimized (for data-heavy tasks).

• High-performance computing services are necessary for large-scale projects with millions of users interacting simultaneously, emphasizing the need for robust virtual machine capabilities.

This structured summary captures key insights from the transcript while providing timestamps for easy reference.

Understanding Virtual Machines and Their Configurations

Overview of Virtual Machine Types

• The discussion begins with a focus on the naming conventions for virtual machines, specifically differentiating between "B" and "D" series, emphasizing the importance of understanding these classifications.

• Standard versions are highlighted, indicating that general-purpose computers start with specific naming conventions to identify their functionality and purpose.

Minimum Requirements for Virtual Machines

• The minimum requirements for a standard D2sv3 virtual machine are introduced, noting it as a general-purpose machine with specific configurations.

• It is explained that the D2sv3 configuration includes 2 virtual CPUs (vCPUs), which represent the processing power allocated to the virtual machine.

Memory Allocation Insights

• The memory allocation for the D2sv3 is specified as 8 GB of RAM, crucial for understanding performance capabilities in various applications.

• Emphasis is placed on recognizing different types of virtual machines and their configurations to ensure optimal performance based on user needs.

Understanding Versioning in Virtual Machines

• A breakdown of versioning from v1 to v5 is provided, clarifying that only certain versions are currently available due to previous deletions or removals.

• The configuration specifics reiterate that a typical setup includes 2 CPUs and 8 GB RAM, essential for identifying suitable options based on workload requirements.

Higher Configuration Options

• Transitioning to higher versions like D4sv3 introduces more powerful configurations such as 4 vCPUs and increased memory capacity (32 GB).

• Further exploration into D8sv3 reveals an even higher configuration with 8 vCPUs and 32 GB RAM, showcasing scalability options within Azure's offerings.

Business Use Cases for Different VM Types

• Discussion shifts towards business-oriented VMs (P series), highlighting their suitability for tasks like Excel work or small meetings compared to general-purpose machines.

• The necessity of selecting appropriate VM types based on project size and budget constraints is emphasized; larger projects require more robust configurations while smaller tasks can utilize basic setups.

Cost Considerations in VM Selection

• Pricing structures are discussed concerning different VM types; Azure provides varied pricing based on usage scenarios tailored to user needs.

• Concluding thoughts suggest that understanding these distinctions helps users select cost-effective solutions aligned with their operational demands.

Overview of Virtual Machines and Storage Types

Introduction to Virtual Machines

• The discussion begins with an introduction to virtual machines, emphasizing the importance of understanding their requirements and types.

• Key components such as CPU and RAM are highlighted, along with the significance of storage in virtual machine setups.

Types of Storage in Virtual Machines

• The conversation shifts to different types of disks used in virtual machines, specifically Azure disk types.

• Various storage options are presented based on user requirements, focusing on cost-saving measures for different use cases.

Comparison of Disk Types

• A comparison is made between traditional hard disk drives (HDD) and solid-state drives (SSD), noting that SSDs are more advanced and costly.

• HDDs are described as older technology commonly found in laptops, while SSDs offer better performance despite higher costs.

Advanced Storage Options

• The discussion continues with the introduction of standard and premium SSD options, highlighting their differences in performance.

• Premium SSDs provide faster read/write operations compared to standard ones, catering to users needing high-speed data access.

Performance Considerations

• It is noted that all disk functions are similar; however, performance varies significantly between HDD and SSD technologies.

• Standard SSD offers better performance than HDD but may still lag behind premium options for intensive applications.

Creating a Virtual Network

• Transitioning from storage discussions, the focus moves towards creating a virtual network necessary for project security within Azure environments.

• The need for a private network is emphasized when deploying projects securely within a cloud infrastructure.

Conclusion on Resource Setup

• Finally, the setup process for resources within Azure is summarized, including creating resource groups and networks essential for hosting virtual machines.

Understanding Subnetting and Virtual Networks in Azure

Introduction to IP Addressing and Subnetting

• The discussion begins with the concept of creating a network using 1000 IP addresses, emphasizing the importance of subnetting within this network.

• A practical example is provided where 1000 IP addresses are divided into subnets for different projects, such as development and testing.

• The speaker explains that dividing the network into smaller subnets allows for better organization and management of resources.

Creating Subnets

• The process of dividing the main network into smaller subnets (e.g., subnet A and subnet B) is outlined, highlighting how virtual machines (VMs) will be placed within these subnets.

• Clarification is given on why understanding these concepts beforehand helps avoid confusion when discussing related topics later.

Setting Up Virtual Machines

• The speaker transitions to creating virtual machines, noting that a resource group and a network must exist before VM creation can occur.

• Instructions are provided on how to type "virtual" in the Azure portal to initiate the VM creation process.

Resource Group Creation

• Before creating VMs, it’s essential to create a resource group. This step ensures that all necessary components are organized under one umbrella.

• The speaker emphasizes that both a resource group and a network need to be established prior to proceeding with VM creation.

Step-by-Step Process Overview

• An overview of steps is presented: first create a resource group, then create a virtual network, followed by subnet creation, leading up to VM deployment.

• Specific terminology like "RG" (Resource Group), "VNet" (Virtual Network), and "subnet" is introduced as part of this structured approach.

Practical Application in Azure Portal

• The speaker demonstrates searching for existing resource groups in the Azure portal while explaining how new ones can be created if needed.

• A specific example is given where an existing resource group named “Learning-Hybrid-RG” is found; however, they opt to create a new one for clarity.

Naming Conventions and Regions

• Importance is placed on meaningful naming conventions for resource groups based on their purpose or environment (e.g., development).

• The region selection for deploying resources is discussed; multiple resources can be created within the same region without issues.

Conclusion: Successful Resource Group Creation

• Confirmation of successful resource group creation leads into planning further actions like creating virtual networks.

Creating a Virtual Network

Steps to Create a Virtual Network

• The process begins with the need to create a new virtual network, as no existing networks are available. A subscription is required for this activity.

• A free trial subscription is utilized, and the next step involves selecting a resource group that has already been created, named "Dev-Hyphen-RG."

• The user assigns a meaningful name to the virtual network, opting for "Testing" followed by "Hyphen-VNet," ensuring clarity in identification.

• The region for creating the virtual network is confirmed as East US, aligning with the previously designated location of the resource group.

• The user decides to create only one virtual network at this stage and will not explore other options or configurations yet.

Subnet Configuration

• A subnet configuration is discussed where 1000 IP addresses are needed. The range selected is 2100 to 23, indicating specific subnetting requirements.

• Two subnets (Subnet A and Subnet B) will be created from the total of 1000 IP addresses, each divided into two groups of 500.

• Default subnet settings are acknowledged; however, custom subnets (A and B), each assigned 256 IP addresses, will be established for better management.

• The division of IP addresses between Subnet A and Subnet B ensures efficient allocation while maintaining clarity in their respective functions within the network.

Deployment Process

• After configuring subnets, attention shifts towards deploying a virtual machine (VM). This deployment serves as an essential target for completion within approximately 10–15 minutes.

• The creation process of the virtual machine begins after confirming that all necessary components have been set up correctly in advance.

Finalizing Network Setup

• Upon successful creation of both the resource group and virtual network ("Testing-Hyphen-VNet"), along with its associated subnets (A and B), focus now turns toward deploying VMs within this framework.

• Instructions emphasize creating two VMs: one by the presenter and another by participants following along.

• Confirmation that all setups—including networks and resources—are complete before proceeding further into VM deployment steps.

Creating a Virtual Machine in Azure

Introduction to Virtual Machine Creation

• The process of creating a virtual machine (VM) is introduced, specifically using the "Create Virtual Machine" option hosted by Azure.

• The first step involves selecting the appropriate subscription for the VM creation, with a focus on utilizing a free trial subscription.

Resource Group Selection

• A resource group named "Dev Hyphen RG" is chosen for placing the new virtual machine, emphasizing its importance in organizing resources within Azure.

• The speaker mentions the need to assign a name to the virtual machine, suggesting "Testing Hyphen VM" as an example.

Configuration Settings

• The region for hosting the VM is specified as East US, with default settings being selected for availability options and security types.

• An operating system (OS) image must be selected; Windows Server 2022 is chosen from available options including versions from 2016 to 2022.

Architecture and Size Selection

• Discussion on architecture reveals that x64 (64-bit) OS will be used.

• Various sizes are presented for VMs, with emphasis on general-purpose sizes like Standard D2 v3 being suitable for this setup.

Finalizing User Credentials and Disk Options

• The configuration includes setting up user credentials; a username "Azure User" and password are established for logging into the VM.

• Default disk options are discussed, highlighting that an OS disk size of 128 GB will be utilized. Premium SSD is selected for better performance based on default recommendations.

Creating a Virtual Machine and Networking Setup

Initial Setup of Data Disk

• The speaker mentions that the data disk is already set to default, and no changes have been made. An additional data disk of 100 GB is required.

• The option to skip adding a data disk for now is discussed, with plans to create a virtual machine (VM) successfully logged in.

Networking Configuration

• The importance of selecting the correct subnet and network for the virtual machine is emphasized.

• A specific virtual network named "Testing-Hyphen-Net" has been created, which will be automatically selected if multiple networks are available.

Public IP Address Explanation

• The speaker introduces the concept of public IP addresses and their necessity for accessing VMs over the internet.

• A diagram illustrating how users access VMs from outside through public IP addresses is referenced.

Real-world Example: Accessing Flipkart

• The speaker explains how accessing websites like Flipkart requires an IP address, demonstrating this by checking Flipkart's IP address using a browser.

• It’s highlighted that without a public IP address, direct access to the VM from external sources would not be possible.

Finalizing VM Creation

• To enable external access to the VM, a public IP must be assigned. This process involves creating an automatic assignment linked to the VM name.

• Confirmation of successful validation before proceeding with creating the virtual machine is noted.

Cost Implications

• The cost associated with using this type of VM is mentioned as ₹15 per hour, indicating financial considerations when utilizing cloud resources.

Virtual Machine Deployment Process

Overview of the Task

• The speaker introduces the task of deploying a virtual machine, emphasizing that it is the first task in their project.

• Confirmation that the deployment process has been completed successfully, indicating progress in creating the virtual machine.

Accessing the Virtual Machine

• The created virtual machine is named "Testing Hyper-V" and will be accessed from a laptop.

• Instructions are provided on how to connect to the virtual machine using either private or public IP addresses, highlighting the need for correct IP usage based on network location.

Connection Steps

• The speaker explains how to find and use the public IP address associated with the virtual machine for remote connection.

• A specific public IP address (172.190.223.6) is mentioned as being allocated to this Azure virtual machine.

Remote Desktop Connection

• The importance of using Remote Desktop Protocol (RDP) for connecting to the virtual machine is discussed, along with instructions on how to enter user credentials.

• Upon entering valid credentials, a prompt appears confirming access to the testing virtual machine.

Operating within the Virtual Machine

• After successful login, users can operate within their testing environment just like they would on their local laptop.

• Details about maintaining server settings and configurations are shared, ensuring users understand how their connection mirrors local operations.

Project Implementation Insights

• The speaker outlines that once connected, users will install necessary software applications required for their work projects on this server.

• Emphasis is placed on closing RDP sessions properly after work completion to ensure data security and integrity of files stored on the server.

This structured overview captures key insights into deploying and accessing a virtual machine while providing timestamps for easy reference back to specific parts of the discussion.