Q.) Write short note on Cloud Deployment Model.

=> Cloud is about outsourcing of IT services and infrastructure to make them accessible
remotely via the Internet. Utilizing cloud-computing models boosts not only productivity but
also provide a competitive edge to organizations. The growing popularity of cloud
computing has given rise to different types of cloud service deployment models and
strategies. Therefore, today there exists a variety of enterprise cloud solutions depending on
the degree of desired outsourcing needs.

Types of Cloud Computing Deployment Models

Most cloud hubs have tens of thousands of servers and storage devices to enable fast
loading. It is often possible to choose a geographic area to put the data “closer” to users.
Thus, deployment models of cloud computing are categorized based on their location.

• Private Cloud
It is a cloud-based infrastructure used by stand-alone organizations. It offers greater
control over security. The data is backed up by a firewall and internally, and can be
hosted internally or externally. Private clouds are perfect for organizations that have
high-security requirements, high management demands, and availability
requirements.

• Public Cloud
This type of cloud services is provided on a network for public use. Customers have
no control over the location of the infrastructure. It is based on a shared cost model
for all the users, or in the form of a licensing policy such as pay per user. Public
deployment models in the cloud are perfect for organizations with growing and
fluctuating demands. It is also popular among businesses of all sizes for their web
applications, webmail, and storage of non-sensitive data.

• Community Cloud
It is a mutually shared model between organizations that belong to a particular
community such as banks, government organizations, or commercial enterprises.
Community members generally share similar issues of privacy, performance, and
security. This type of deployment model of cloud computing is managed and hosted
internally or by a third-party vendor.

• Hybrid Cloud
This model incorporates the best of both private and public clouds, but each can
remain as separate entities. Further, as part of this deployment of cloud computing
model, the internal, or external providers can provide resources. A hybrid cloud is
ideal for scalability, flexibility, and security. A perfect example of this scenario would
be that of an organization who uses the private cloud to secure their data and
interacts with its customers using the public cloud.
Q.) Explain SDN architecture in detail?

=> Software Defined Networking (SDN) refers to the network architecture model that
allows programmatic management, control and optimization of network resources. SDN
decouples network configuration and traffic engineering from the underlying hardware
infrastructure to ensure holistic and consistent control of the network using open APIs.

The exploding volumes of data traffic, complex network architecture and growing demands
to improve network performance renders the traditional approach to network management
as obsolete. Traditional network architecture offers minimal flexibility to coordinate between
fixed function network devices that must be configured manually. A single change can have a
cascading effect on the network performance and has the potential to bring down the entire
network.

It is the static nature of the traditional network architecture model that fails to meet the
demands of a modern business IT. Organizations require network infrastructure to allow the
flexibility to scale and support dynamic computing environments based on rapidly-evolving
technology and business landscape. Software Defined Network offers the following key
characteristics to address these concerns:

1. Decoupled Architecture Planes

A classic communication network architecture consists of three main components: data

plane, control plane and management plane. Control Plane refers to the network
architecture component that defines the traffic routing and network topology. Data
Plane is the network architecture layer that physically handles the traffic based on the
configurations supplied from the Control Plane. The Management Plane takes care of
the wider network configuration, monitoring and management processes across all
layers of the network stack. In the traditional network architecture, control plane and
data plane are integrated and any changes to the system are dependent upon physical
network devices, the protocols and software they support. Limited changes can be
performed to the overall system as the network devices bottleneck logical network
traffic flows. Devices function autonomously and offer limited logical awareness toward
the wider network.
In contrast, SDN decouples the Control Plane from the Data Plane and centrally
integrates the network logic at the controller level. A controller separated between the
two Planes logically centralizes the network intelligence such that users can choose
which programmable features can be moved from network devices onto the application
server or controller.
The logically centralized and decoupled controller operations allow organizations the
enhanced agility to automate, extend, monitor, maintain, manage, extend, provision and
troubleshoot the network infrastructure. Applications interact directly with the controller
to obtain a global view of the network state. The dynamic, scalable and flexible network
infrastructure leads to simplified operations and the ability to test new business
opportunities that are otherwise limited due to network architectural bottlenecks.
2. Network Programmability
Imagine programming 10 routers, one by one and then keeping track of how every
device was configured and supposed to behave. Scale it to hundreds and thousands of
devices, and the manual processes involved in device monitoring, configuration and
management are rendered ineffective. Even the network management systems (NMS)
won’t suffice to eliminate network bottlenecks, errors and performance issues.

With SDN algorithms, the number of repeatable device configuration and management
processes is not a limitation. An SDN would see 1000 routers in a similar way it sees 10
routers and algorithms can incorporate the changing dynamics of the network
configurations realized in scaled environments. The SDN capability essentially lets
sysadmins tell the network “what to do” in response to network changes or dynamic
traffic flow patterns.

Additionally, network programmability is key to achieve global optimization toward a

consistent network-wide state. Networks don’t converge to a single state when each
component is programmed individually without awareness of the surrounding network
environment, state and configuration patterns. SDN lets users replace local optimization
with a logically centralized intelligence and control of network resources. The underlying
dependencies and limitations don’t apply (at least in the same way) considering the
decoupled nature of Data and Control Plane components of the network architecture.
Instead of having to tweak settings on hundreds of individual management consoles,
applications can interact with the appropriate network devices through APIs and
maintain consistent overall network performance, functionality and control.

3. Openness and Interoperability

Vendor interoperability and network integration is a primary criterion for network traffic
engineering – ranging from device planning and purchase to configuration and
management. Vendor neutrality allows organizations to optimize infrastructure
investments for technical and business requirements. Consider the two layers of SDN
interoperability: the infrastructure and the service. At the infrastructure layer, SDN
supports standard protocols for communication between devices from multiple vendors
and maintain a common software environment. At the service layer, SDN manages
infrastructure-wide organizational policies, systems and network applications. These can
be divided into multiple open and modular dimensions.

In an SDN system, the open network orchestration, service and network management
systems simplify deployment. For instance, RESTful APIs can be used for communication
via open protocols supported by all network device vendors. As a result, the network
infrastructure is easy to extend and the overall system doesn’t run into network
performance and scalability bottleneck. The architecture abstraction layer allows
controllers to manage traffic easily using open standards such as OpenFlow or other
extensible protocols. Finally, the SDN controller platform itself operates as an open
 system that allows users to extend functionality, add applications via APIs or modules to
perform specific network management functionality.

Q.) Differentiate between M2M and IoT?

=>

M2M loT
• Simple device-to-device • Grand-scale projects and want-it-
communication usually within an all approach.
embedded software at client site.
• Isolated systems of devices using • Integrates devices, data and
same standards. applications across varying
standards.

• Limited scalability options. • Inherently more scalable.

• Wired or cellular network used • Usually devices require active

for connectivity. Internet connection.

• Extensive background of • State-of-the-art approach with

historical applications. roots in M2M.

Q.) Write short note on data storage in cloud?

=> Cloud storage involves at least one data server that a user connects to via the internet.
The user sends files manually or in an automated fashion over the Internet to the data server
which forwards the information to multiple servers. The stored data is then accessible
through a web-based interface.

Cloud storage systems involve vast numbers of data servers to ensure their availability. That
way, if one server requires maintenance or fails, the user can rest assured that the data has
been replicated elsewhere to ensure availability. For example, the Amazon AWS Cloud spans
55 availability zones in 18 geographic regions at the present time.

While the data in a public cloud is replicated in different physical locations for fault tolerance
and disaster recovery purposes, the primary or local location tends to be nearer physically to
the company's facility using it so the data can be processed faster and at lower costs then,
say choosing a primary location halfway around the globe.