Cloud computing

Simply put, cloud computing is the delivery of computing services—servers, storage,

databases, networking, software, analytics and more—over the Internet (“the cloud”).
Companies offering these computing services are called cloud providers and typically
charge for cloud computing services based on usage, similar to how you are billed
for water or electricity at home.

Here are a few of the things you can do with the cloud:

 Create new apps and services

 Store, back up and recover data

 Host websites and blogs

 Stream audio and video

 Deliver software on demand

 Analyse data for patterns and make predictions

Top benefits of cloud computing
Cloud computing is a big shift from the traditional way businesses think about IT
resources. What is it about cloud computing? Why is cloud computing so popular?
Here are 6 common reasons organisations are turning to cloud computing services
1. Cost
Cloud computing eliminates the capital expense of buying hardware and software
and setting up and running on-site datacenters—the racks of servers, the round-the-
clock electricity for power and cooling, the IT experts for managing the infrastructure.
It adds up fast.
2. Speed
Most cloud computing services are provided self service and on demand, so even
vast amounts of computing resources can be provisioned in minutes, typically with
just a few mouse clicks, giving businesses a lot of flexibility and taking the pressure
off capacity planning.
3. Global scale
The benefits of cloud computing services include the ability to scale elastically. In
cloud speak, that means delivering the right amount of IT resources—for example,
more or less computing power, storage, bandwidth—right when its needed and from
the right geographic location.
4. Productivity
On-site datacenters typically require a lot of “racking and stacking”—hardware set
up, software patching and other time-consuming IT management chores. Cloud
computing removes the need for many of these tasks, so IT teams can spend time on
achieving more important business goals.
5. Performance
The biggest cloud computing services run on a worldwide network of secure
datacenters, which are regularly upgraded to the latest generation of fast and
efficient computing hardware. This offers several benefits over a single corporate
datacenter, including reduced network latency for applications and greater
economies of scale.
6. Reliability
Cloud computing makes data backup, disaster recovery and business continuity
easier and less expensive, because data can be mirrored at multiple redundant sites
on the cloud provider’s network.

Types of cloud services: IaaS, PaaS, SaaS

Most cloud computing services fall into three broad categories: infrastructure as a
service (IaaS), platform as a service (PaaS) and software as a service (Saas). These are
sometimes called the cloud computing stack, because they build on top of one
another. Knowing what they are and how they are different makes it easier to
accomplish your business goals.

Infrastructure-as-a-service (IaaS)

The most basic category of cloud computing services. With IaaS, you rent IT
infrastructure—servers and virtual machines (VMs), storage, networks, operating
systems—from a cloud provider on a pay-as-you-go basis. To learn more, see What
is IaaS?

Platform as a service (PaaS)

Platform-as-a-service (PaaS) refers to cloud computing services that supply an on-

demand environment for developing, testing, delivering and managing software
applications. PaaS is designed to make it easier for developers to quickly create web
or mobile apps, without worrying about setting up or managing the underlying
infrastructure of servers, storage, network and databases needed for development.
To learn more, see What is PaaS?

Software as a service (SaaS)

Software-as-a-service (SaaS) is a method for delivering software applications over the

Internet, on demand and typically on a subscription basis. With SaaS, cloud providers
host and manage the software application and underlying infrastructure and handle
any maintenance, like software upgrades and security patching. Users connect to the
application over the Internet, usually with a web browser on their phone, tablet or
PC.

Types of cloud deployments: public, private, hybrid

Not all clouds are the same. There are three different ways to deploy cloud
computing resources: public cloud, private cloud and hybrid cloud.

Public cloud

Public clouds are owned and operated by a third-party cloud service provider, which
deliver their computing resources like servers and storage over the Internet.
Microsoft Azure is an example of a public cloud. With a public cloud, all hardware,
software and other supporting infrastructure is owned and managed by the cloud
provider. You access these services and manage your account using a web browser.
Google App Engine,Microsoft Windows Azure,IBM Smart Cloud,Amazon EC2

Private cloud

A private cloud refers to cloud computing resources used exclusively by a single

business or organisation. A private cloud can be physically located on the company’s
on-site datacenter. Some companies also pay third-party service providers to host
 their private cloud. A private cloud is one in which the services and infrastructure are
maintained on a private network.
 Eucalyptus
 Ubuntu Enterprise Cloud - UEC (powered by Eucalyptus)
 Amazon VPC (Virtual Private Cloud)
 VMware Cloud Infrastructure Suite
 Microsoft Enrollment Core Infrasructure data center.

Hybrid cloud
 Hybrid clouds combine public and private clouds, bound together by
technology that allows data and applications to be shared between them. By
allowing data and applications to move between private and public clouds, hybrid
cloud gives businesses greater flexibility and more deployment options. Windows
Azure (capable of Hybrid Cloud)
 VMware vCloud (Hybrid Cloud Services)

Community cloud
The cloud infrastructure is shared by several organizations and supports a specific
community that has shared concerns (e.g., mission, security requirements, policy,
and compliance considerations).  Government departments, universities, central
banks etc. 
 Google Apps for Government
 Microsoft Government Community Cloud
EUCALYPTUS” stands for Elastic Utility Computing Architecture For Linking Your
Programs
To Useful Systems”
Explain what is the use of “EUCALYPTUS” in cloud computing?
“Eucalyptus” is an open source software infrastructure in cloud computing, which is
used to
implement clusters in cloud computing platform. It is used to build public, hybrid and
private
clouds. It has the ability to produce your own data center into a private cloud and
allows you to
use its functionality to many other organizations.
AZURE

Microsoft Azure, formerly known as Windows Azure, is Microsoft's public cloud

computing platform. It provides a range of cloud services, including those for
compute, analytics, storage and networking.
Microsoft Azure is widely considered both a Platform as a Service
(PaaS) and Infrastructure as a Service (IaaS) offering.
Microsoft introduced Azure in October 2008. The cloud platform was originally called
Windows Azure, but was rebranded to Microsoft Azure in April 2014. Azure
competes with other public cloud platforms, including Amazon Web Services
(AWS) and Google Cloud Platform.

What is azure

Azure is a comprehensive set of cloud services that developers and IT professionals

use to build, deploy, and manage applications through our global network of
datacenters.

Why azure
Organisations all over the world recognise Azure over AWS as the most trusted cloud,
because it offers:

More regions than any other cloud provider

Unmatched hybrid capabilities

The strongest intelligence

Difference between ssd(premium storage) and hdd(standard storage)

Attribute SSD (Solid State Drive) HDD (Hard Disk Drive)

Power Draw / Battery Life Less power draw, More power draw, averages 6 –
averages 2 – 3 watts, 7 watts and therefore uses more
resulting in 30+ minute battery
battery boost
Cost Expensive, roughly $0.20 per Only around $0.03 per
gigabyte (based on buying a gigabyte, very cheap (buying
1TB drive) a 4TB model)
Capacity Typically not larger than 1TB Typically around 500GB and
for notebook size drives; 4TB 2TB maximum for notebook
max for desktops size drives; 10TB max for
desktops
Operating System Boot Around 10-13 seconds Around 30-40 seconds average
Time average bootup time bootup time
Noise There are no moving parts Audible clicks and spinning can
 and as such no sound be heard
Vibration No vibration as there are The spinning of the platters can
no moving parts sometimes result in vibration
Heat Produced Lower power draw and no HDD doesn’t produce much
moving parts so little heat heat, but it will have a
is produced measurable amount more heat
than an SSD due to moving
parts and higher power draw
Failure Rate Mean time between failure Mean time between failure rate
rate of 2.0 million hours of 1.5 million hours
File Copy / Write Speed Generally above 200 MB/s The range can be anywhere
and up to 550 MB/s for from 50 – 120MB / s
cutting edge drives
Encryption Full Disk Encryption Full Disk Encryption (FDE)
(FDE) Supported on some Supported on some models
models
File Opening Speed Up to 30% faster than Slower than SSD
HDD

Magnetism Affected? An SSD is safe from any Magnets can erase data
effects of magnetism
Standard Storage is backed by HDDs, and delivers cost-effective storage while still being
performant. Standard storage can be replicated locally in one datacenter, or be geo-
redundant with primary and secondary data centers.

Premium Storage is backed by SSDs, and delivers high-performance, low-latency(delay) disk

support for VMs running I/O-intensive workloads. You can use Premium Storage with DS,
DSv2, GS, Ls, or FS series Azure VMs

MANAGED AND UNMANAGED DISKS

 Unmanaged disks
The original method is to use unmanaged disks. In an unmanaged disk, you
manage the storage accounts that you use to store the virtual hard disk (VHD)
files that correspond to your VM disks. VHD files are stored as page blobs in
Azure storage accounts.
 Managed disks
When you choose Azure Managed Disks, Azure manages the storage accounts
that you use for your VM disks. You specify the disk type (Premium or Standard)
and the size of the disk that you need. Azure creates and manages the disk for
you. You don't have to worry about placing the disks in multiple storage
accounts to ensure that you stay within scalability limits for your storage
accounts. Azure handles that for you.
STORAGE TYPES
BLOB,QUEUE,FILES,MESSAGE
Azure Blob Storage-Block blobs,append blobs,page blobs
Blog Storage is basically storage for unstructured data that can include pictures,
videos, music files, documents, raw data, and log data…along with their meta-data.
Blobs are stored in a directory-like structure called a “container”. If you are familiar
with AWS S3, containers work much the same way as S3 buckets. You can store any
number of blob files up to a total size of 500 TB and, like S3, you can also apply
security policies. Blob storage can also be used for data or device backup.
Blob Storage service comes with three types of blobs: block blobs, append
blobs and page blobs. You can use block blobs for documents, image files, and video
file storage. Append blobs are similar to block blobs, but are more often used for
append operations like logging. Page blobs are used for objects meant for frequent
read-write operations. Page blobs are therefore used in Azure VMs to store OS and
data disks.
Azure Table Storage
Table storage, as the name indicates, is preferred for tabular data, which is ideal for
key-value NoSQL data storage. Table Storage is massively scalable and extremely
easy to use. Like other NoSQL data stores, it is schema-less and accessed via a REST
API(REPRESENTATIONAL STATE TRANSFER-service endpoints that support http
operations)
Azure Queue Storage
The Queue Storage service is used to exchange messages between components
either in the cloud or on-premise (compare to Amazon’s SQS). You can store large
numbers of messages to be shared between independent components of applications
and communicated asynchronously via HTTP or HTTPS.
Locations
Azure Storage data is replicated multiple times across regions. There are four ways
you can make sure data is stored redundantly: Locally Redundant Storage (LRS),
Zone-Redundant Storage (ZNS), Geo-redundant Storage (GRS), and Read Access Geo-
redundant Storage (RA-GRS).
Using LRS, three copies of all data are maintained in a single facility within a single
region. With ZRS, three copies of your data will be stored in multiple facilities of two
or three regions. Obviously, this will achieve greater durability than LRS. For GRS, six
copies of data are stored across two regions, with three copies in a so-called primary
region, and the rest in a secondary region, usually geographically distant from your
primary region. In case of primary region failure, the secondary region is used as part
of a fail-over mechanism. RA-GRS data will be stored just like GRS, except that you
get read-only access to the secondary region.
Geo-redundant Storage (GRS) and Read Access Geo-redundant Storage (RA-GRS)
provide the highest level of durability, but at a higher cost. GRS is the default storage
redundancy mode. In case you need to switch from LRS to GRS or to RA-GRS, an
additional one-time data transfer cost will be applied. But if you chose ZRS, you
cannot subsequently change to any other redundancy mode.
VIRTUAL NETWORK
The Azure Virtual Network service enables you to securely connect Azure resources
to each other with virtual networks (VNets). A VNet is a representation of your own
network in the cloud. A VNet is a logical isolation of the Azure cloud dedicated to
your subscription. You can also connect VNets to your on-premises network.
PEERING
IT enables resources connected to different Azure VNets within the same Azure
location to communicate with each other. The bandwidth and latency across the
VNets is the same as if the resources were connected to the same VNet.
Address space
 You cannot add the following address spaces:
o 224.0.0.0/4 (Multicast)
o 255.255.255.255/32 (Broadcast)
o 127.0.0.0/8 (Loopback)
o 169.254.0.0/16 (Link-local)
the smallest subnet we support is a /29 and the largest is a /8 168.63.129.16/32
(Internal DNS)

VNET GATEWAY
virtual network gateway is composed of two or more virtual machines that are deployed
to a specific subnet called the GatewaySubnet. The VMs that are located in the
GatewaySubnet are created when you create the virtual network gateway. Virtual network
gateway VMs are configured to contain routing tables and gateway services specific to
the gateway. You can't directly configure the VMs that are part of the virtual network
gateway and you should never deploy additional resources to the GatewaySubnet.
When you create a virtual network gateway using the gateway type 'Vpn', it creates a
specific type of virtual network gateway that encrypts traffic; a VPN gateway. A VPN
gateway can take up to 45 minutes to create. This is because the VMs for the VPN
gateway are being deployed to the GatewaySubnet and configured with the settings
that you specified. The Gateway SKU that you select determines how powerful the
VMs are.
TRAFFIC MANAGER
Azure Traffic Manager gives you four methods for traffic routing: Failover, performance,
geography and weighted round-robin. Choose the one that is right for you or combine
using nested profiles.

Reduce application downtime

Traffic Manager can improve the availability of important applications by monitoring
your Azure services or external websites and services and it automatically directs your
customers to a new location when there is a failure.

Improve app performance and content delivery

 Traffic Manager makes your applications more responsive and improves content
delivery times by directing your customers to Azure or an external location with the
lowest network latency.

Distribute user traffic over multiple locations

Traffic Manager can direct your customer traffic to distribute it across multiple
locations, such as multiple cloud services or multiple Azure web apps. Traffic
Manager can use equal or weighted load distribution.

Use with your on-premises datacenter

Traffic Manager is a popular option for on-premises scenarios including burst-to-
cloud, migrate-to-cloud and failover-to-cloud. Use it to upgrade or perform
maintenance on your on-site datacenter without inconveniencing your customers.
The job of Azure Traffic Manager is to route traffic globally based on flexible policies,
enabling an excellent user experience that aligns with how you've structured your
application across the world.  Traffic Manager has several different policies:
 Latency.  Direct to the "closest service"
 Round Robin.  Distribute across all services
 Failover.  Direct to backup if primary fails
 Nested.  Flexible multi-level policies
LOAD BALANCER
The job of Azure Load Balancer is to direct traffic inside a region.  This is combined
with Azure Traffic Manager, where traffic manager routes interior to a region
between virtual machines.  If you combine the two you get global traffic management
combined with local failover.
Difference between arm and asm

One of the other major differences in Azure is the difference

between the service management and resource manager APIs and
interfaces
manage.windowsazure.com,new-portal.azure.com
Azure originally provided only the classic deployment model. In this model, each
resource existed independently; there was no way to group related resources
together. Instead, you had to manually track which resources made up your solution
or application, and remember to manage them in a coordinated approach. To deploy
a solution, you had to either create each resource individually through the classic
portal or create a script that deployed all the resources in the correct order. To delete
a solution, you had to delete each resource individually. You could not easily apply
and update access control policies for related resources. Finally, you could not apply
tags to resources to label them with terms that help you monitor your resources and
manage billing.
In 2014, Azure introduced Resource Manager, which added the concept of a resource
group. A resource group is a container for resources that share a common lifecycle.
The Resource Manager deployment model provides several benefits:
 You can deploy, manage, and monitor all the services for your solution as a
group, rather than handling these services individually.
 You can repeatedly deploy your solution throughout its lifecycle and have
confidence your resources are deployed in a consistent state.
 You can apply access control to all resources in your resource group, and
those policies are automatically applied when new resources are added to the
resource group.
 You can apply tags to resources to logically organize all the resources in your
subscription.
 You can use JavaScript Object Notation (JSON) to define the infrastructure for
your solution. The JSON file is known as a Resource Manager template.
 You can define the dependencies between resources so they are deployed in
the correct order.
NSG(ACL)
A network security group (NSG) contains a list of security rules that allow or deny
network traffic to resources connected to Azure Virtual Networks (VNet). NSGs can
be associated to subnets, individual VMs (classic), or individual network interfaces
(NIC) attached to VMs (Resource Manager). When an NSG is associated to a subnet,
the rules apply to all resources connected to the subnet. Traffic can further be
restricted by also associating an NSG to a VM or NIC.
JSON TEMPLATE
The template consists of JSON and expressions that you can use to construct values
for your deployment.
{
"$schema": "http://schema.management.azure.com/schemas/2015-01-
01/deploymentTemplate.json#",
"contentVersion": "",
"parameters": { },
"variables": { },
"resources": [ ],
"outputs": { }
}
"variables": {
"location": "[resourceGroup().location]",
"usernameAndPassword": "[concat(parameters('username'), ':',
parameters('password'))]",
"authorizationHeader": "[concat('Basic ',
base64(variables('usernameAndPassword')))]"
}
"parameters": {
"<parameter-name>" : {
 "type" : "<type-of-parameter-value>",
"defaultValue": "<default-value-of-parameter>",
"allowedValues": [ "<array-of-allowed-values>" ],
"minValue": <minimum-value-for-int>,
"maxValue": <maximum-value-for-int>,
"minLength": <minimum-length-for-string-or-array>,
"maxLength": <maximum-length-for-string-or-array-parameters>,
"metadata": {
"description": "<description-of-the parameter>"
}
}
}"resources": [

{
"condition": "<boolean-value-whether-to-deploy>",
"apiVersion": "<api-version-of-resource>",
"type": "<resource-provider-namespace/resource-type-name>",
"name": "<name-of-the-resource>",
"location": "<location-of-resource>",
"tags": {
"<tag-name1>": "<tag-value1>",
"<tag-name2>": "<tag-value2>"
},
The allowed types and values are:
 string
 secureString
 int
 bool
 object
 secureObject
 array
REMOTE DESKTOP PROTOCOL

Remote Desktop enables you to access the desktop of a role running in Azure. You
can use a Remote Desktop connection to troubleshoot and diagnose problems with
your application while it is running.
ORU WINDOW MACHINE LA ERUNTHU INNORU WINDOW MACHINE ACCESS
PANNALAM
VNET PEERING
Azure VNet peering is a feature available in Azure that allows customers to interconnect virtual networks
in the same region.
With VNet peering, a user defined route used in one virtual network can point to a virtual machine in a
peered virtual network. Using this approach one can create a hub-and-spoke environment where a Check
Point Security gateway resides in a hub virtual network and inspects traffic originating in another virtual
network before it is forwarded to a third virtual network.
VWhat are my cross-premises connection optionS

 Site-to-Site – VPN connection over IPsec (IKE v1 and IKE v2). This type of
connection requires a VPN device or RRAS. For more information, see Site-to-
Site.
 Point-to-Site – VPN connection over SSTP (Secure Socket Tunneling Protocol).
This connection does not require a VPN device. For more information,
see Point-to-Site.
 VNet-to-VNet – This type of connection is the same as a Site-to-Site
configuration. VNet to VNet is a VPN connection over IPsec (IKE v1 and IKE v2).
It does not require a VPN device. For more information, see VNet-to-VNet.
 Multi-Site – This is a variation of a Site-to-Site configuration that allows you to
connect multiple on-premises sites to a virtual network. For more information,
see Multi-Site.
 ExpressRoute – ExpressRoute is a direct connection to Azure from your WAN,
not a VPN connection over the public Internet. For more information, see
the ExpressRoute Technical Overview and the ExpressRoute FAQ.