Linux on Azure
Microsoft Endorsed some versions of Linux in the Azure
Marketplace in which,
·
The Linux Integration Services (LIS) drivers for Hyper-V and Azure are
kernel modules that are contributed directly from MS to the upstream Linux
kernel.
·
The Azure Linux Agent is already
pre-installed and the source code can be found on GitHub.
For Non-Endorsed Versions of Linux
- You can
bring your own Linux image by Creating and uploading a virtual hard disk
that contains the Linux OS.
Endorsed distributions - Linux
Azure
SLAs applies only to the Endorsed versions
- CentOS
6.3+
- CoreOS
494.4.0+
- Debian
7.9+, 8.2+
- Oracle
Linux 6.4+, 7.0+
- RHEL
6.7+, 7.1+
- SLES
11, SLES 12+, SLES for SAP11.3+
- Open
SUSE 13.2+
- Ubuntu
12.04, 14.04, 16.04
Accessing of Linux VMs
Once
the Linux VMs are created, it is required to access the VM.
Here
are the few ways to access the VMs,
- Azure
Cloud Shell (CLI)
- Bash
Shell from Windows 10
- Putty
software
To use Linux VMs using Windows OS, we need to install Bash
Shell
Managing Azure Virtual Machines
Once the VM is created, the following components must be
configured to provide consistency and high availability.
- IP Addresses
- Availability Set
- Auto Scaling
IP
address is assigned to Azure resources to communicate with other Azure
resources, on-premises network, and the Internet. It can be allocated in two
ways,
- Static Allocation
- Dynamic Allocation
Types of IP Addresses
- Public IP addresses - Used for communication with the Internet,
including Azure public-facing services.
E.g.: VMs,
Internet-facing LB, VPN GW, and Application GW.
- Private IP addresses - Used for communication within an Azure virtual
network (VNet), and on-premises network when a VPN is configured.
E.g.: VMs,
Internal LB, and Application GW.
Dynamic allocation is the default method for both Private and
Public IP Addresses.
Public
IP Allocation
Dynamic allocation method:
- The public IP address is
allocated when you start/create the associated resource (like a VM or load
balancer).
- The IP address is released when
you stop/delete the resource.
In this method IP
address can change.
Static allocation method:
- The IP address must be
configured in "NIC" properties for the associated resource.
- It is released only when you
delete the resource or change its allocation method to dynamic.
In this method IP
address will not change.
Private IP Addresses
Private IP Addresses
·
In both (dynamic or static) ways, the IP
address is allocated from the address range of the subnet to which the resource
is attached.
·
In Dynamic allocation method the IP
address is automatically allocated from the resource's subnet (using DHCP).
This IP address can change when the resource is stopped and started.
·
In Static allocation method, the IP
address must be assigned from the allocated subnet and remains the unchanged
till the VM is deleted.
Comments
Post a Comment