CHAPTER – 1

INTRODUCTION TO CLOUD COMPUTING

Cloud computing is an information technology (IT) paradigm, a model for enabling

ubiquitous access to shared pools of configurable resources (such as computer
networks, servers, storage, applications and services),which can be rapidly provisioned
with minimal management effort, often over the Internet. Cloud computing allows users
and enterprises with various computing capabilities to store and process data either in
a privately-owned cloud, or on a third-party server located in a data center - thus making
data-accessing mechanisms more efficient and reliable. Cloud computing relies on
sharing of resources to achieve coherence and economy of scale, similar to a utility.

Advocates note that cloud computing allows companies to avoid or minimize up-front
IT infrastructure costs. As well, third-party clouds enable organizations to focus on their
core businesses instead of expending resources on computer infrastructure and
maintenance. Proponents also claim that cloud computing allows enterprises to get their
applications up and running faster, with improved manageability and less maintenance,
and that it enables IT teams to more rapidly adjust resources to meet fluctuating and
unpredictable business demand. Cloud providers typically use a "pay-as-you-go"
model. This could lead to unexpectedly high charges if administrators are not
familiarized with cloud-pricing models.

In 2009 the availability of high-capacity networks, low-cost computers and storage

devices as well as the widespread adoption of hardware virtualization, service-oriented
architecture, and autonomic and utility computing led to a growth in cloud computing.
Companies can scale up as computing needs increase and then scale down again when
demands decrease. In 2013 it was reported that cloud computing had become a highly
demanded service or utility due to the advantages of high computing power, cheap cost
of services, high performance, scalability, and accessibility - as well as availability.
Some cloud vendors experience growth rates of 50% per year, but while cloud
computing remains in a stage of infancy, it has pitfalls that need to be addressed to
make cloud-computing services more reliable and user-friendly.

1
Cloud Computing

Fig. 1

2
1.1 History

Origin of the term

The origin of the term cloud computing is unclear. The word cloud is commonly
used in science to describe a large agglomeration of objects that visually appear from a
distance as a cloud and describes any set of things whose details are not further
inspected in a given context. Another explanation is that the old programs that drew
network schematics surrounded the icons for servers with a circle, and a cluster of
servers in a network diagram had several overlapping circles, which resembled a cloud
.In analogy to the above usage, the word cloud was used as a metaphor for the Internet
and a standardized cloud-like shape was used to denote a network on telephony
schematics. Later it was used to depict the Internet in computer network diagrams. With
this simplification, the implication is that the specifics of how the end points of a
network are connected are not relevant for the purposes of understanding the diagram.
The cloud symbol was used to represent networks of computing equipment in the
original ARPANET by as early as 1977,and the CSNET by 1981—both predecessors
to the Internet itself.

References to "cloud computing" in its modern sense appeared as early as 1996, with
the earliest known mention in a Compaq internal document. The popularization of the
term can be traced to 2006 when Amazon.com introduced its Elastic Compute Cloud.

1970s

During the 1960s, the initial concepts of time-sharing became popularized via
RJE (Remote Job Entry);this terminology was mostly associated with large vendors
such as IBM and DEC. Full time-sharing solutions were available by the early 1970s
on such platforms as Multics (on GE hardware), Cambridge CTSS, and the earliest
UNIX ports (on DEC hardware). Yet, the "data centre" model where users submitted
jobs to operators to run on IBM mainframes was overwhelmingly predominant.

1990s

In the 1990s, telecommunications companies, who previously offered primarily

dedicated point-to-point data circuits, began offering virtual private network (VPN)
services with comparable quality of service, but at a lower cost. By switching traffic as

3
they saw fit to balance server use, they could use overall network bandwidth more
effectively.

2000s

Since 2000, cloud computing has come into existence. In early 2008, NASA's
Open Nebula, enhanced in the RESERVOIR European Commission-funded project,
became the first open-source software for deploying private and hybrid clouds, and for
the federation of clouds.

In August 2006 Amazon introduced its Elastic Compute Cloud. Microsoft

Azure was announced as "Azure" in October 2008 and was released on 1 February 2010
as Windows Azure, before being renamed to Microsoft Azure on 25 March 2014.In
July 2010, Rack space Hosting and NASA jointly launched an open-source cloud-
software initiative known as Open Stack.

On March 1, 2011, IBM announced the IBM Smart Cloud framework to support
Smarter Planet. Among the various components of the Smarter Computing foundation,
cloud computing is a critical part. On June 7, 2012, Oracle announced the Oracle Cloud.

In April of 2008, Google released Google App Engine in beta. In May of 2012,
Google Compute Engine was released in preview, before being rolled out into General
Availability in December of 2013.

Similar concepts

Cloud computing is the result of the evolution and adoption of existing

technologies and paradigms. The goal of cloud computing is to allow users to take
benefi from all of these technologies, without the need for deep knowledge about or
expertise with each one of them. The cloud aims to cut costs, and helps the users focus
on their core business instead of being impeded by IT obstacles. The main enabling
technology for cloud computing is virtualization. Virtualization software separates a
physical computing device into one or more "virtual" devices, each of which can be
easily used and managed to perform computing tasks.

Users routinely face difficult business problems. Cloud computing adopts

concepts from Service-oriented Architecture (SOA) that can help the user break these
problems into services that can be integrated to provide a solution. Cloud computing

4
provides all of its resources as services, and makes use of the well-established standards
and best practices gained in the domain of SOA to allow global and easy access to cloud
services in a standardized way.

Cloud computing shares characteristics with:

Client–server model—Client–server computing refers broadly to any distributed

application that distinguishes between service providers (servers) and service
requestors (clients)

Computer bureau—A service bureau providing computer services, particularly from

the 1960s to 1980s.

Grid computing—"A form of distributed and parallel computing, whereby a 'super and
virtual computer' is composed of a cluster of networked, loosely coupled computers
acting in concert to perform very large tasks.”

Fog computing—Distributed computing paradigm that provides data, compute, storage

and application services closer to client or near-user edge devices, such as network
routers. Furthermore, fog computing handles data at the network level, on smart devices
and on the end-user client side (e.g. mobile devices), instead of sending data to a remote
location for processing.

Utility computing—The “packaging of computing resources, such as computation and

storage, as a metered service similar to a traditional public utility, such as electricity.”

5
1.2 Cloud Computing Types

Private cloud

Private cloud is cloud infrastructure operated solely for a single organization,

whether managed internally or by a third-party, and hosted either internally or
externally.[2] Undertaking a private cloud project requires significant engagement to
virtualize the business environment, and requires the organization to reevaluate
decisions about existing resources.

Public cloud

A cloud is called a "public cloud" when the services are rendered over a network
that is open for public use. Public cloud services may be free.[102] Technically there
may be little or no difference between public and private cloud architecture, however,
security consideration may be substantially different for services (applications, storage,
and other resources) that are made available by a service provider for a public audience
and when communication is effected over a non-trusted network.

Hybrid cloud

Hybrid cloud is a composition of two or more clouds (private, community or

public) that remain distinct entities but are bound together, offering the benefits of
multiple deployment models. Hybrid cloud can also mean the ability to connect
collocation, managed and/or dedicated services with cloud resources. Gartner, Inc.
defines a hybrid cloud service as a cloud computing service that is composed of some
combination of private, public and community cloud services, from different service
providers. A hybrid cloud service crosses isolation and provider boundaries so that it
can't be simply put in one category of private, public, or community cloud service. It
allows one to extend either the capacity or the capability of a cloud service, by
aggregation, integration or customization with another cloud service.

6
Intercloud

The Intercloud is an interconnected global "cloud of clouds" and an extension

of the Internet "network of networks" on which it is based. The focus is on direct
interoperability between public cloud service providers, more so than between
providers and consumers.

Cloud computing types

Cloud computing is divided into various types.

1. Public Cloud Computing

2. Private Cloud Computing

3. Hybrid Cloud Computing

4. Community Cloud Computing

Fig. 1.2.1

7
Architecture

Cloud architecture

The systems architecture of the software systems involved in the delivery of

cloud computing, typically involves multiple cloud components communicating with
each other over a loose coupling mechanism such as a messaging queue. Elastic
provision implies intelligence in the use of tight or loose coupling as applied to
mechanisms such as these and others.

Cloud engineering

Cloud engineering is the application of engineering disciplines to cloud

computing. It brings a systematic approach to the high-level concerns of
commercialization, standardization, and governance in conceiving, developing,
operating and maintaining cloud computing systems. It is a multidisciplinary method
encompassing contributions from diverse areas such as systems, software, web,
performance, information, security, platform, risk, and quality engineering.

Cloud computing sample architecture

Fig. 1.2.2
8
Cloud Computing Architecture refers to the components and subcomponents required
for cloud computing. These components typically consist of a front end platform (fat
client, thin client, mobile device), back end platforms (servers, storage), a cloud based
delivery, and a network (internet, intranet, intercloud).

The backend refers to the cloud itself. It consists of all the resources required to provide
cloud computing services. It comprises of huge data storage, virtual machines, security
mechanism, services, deployment models, servers, etc.

9
1.3 Service models
Though service-oriented architecture advocates "everything as a service" (with
the acronyms EaaS or XaaS, or simply aas), cloud-computing providers offer their
"services" according to different models, of which the three standard models per NIST
are Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and Software as a
Service (SaaS). These models offer increasing abstraction; they are thus often portrayed
as a layers in a stack: infrastructure-, platform- and software-as-a-service, but these
need not be related.

Cloud computing service models arranged as layers in a stack

Fig. 1.3.1

1. SaaS (Software as a Service)

2. PaaS (Platform as a Service)

3. IaaS (Infrastructure as a Service)

10
Infrastructure as a service (IaaS)

According to the Internet Engineering Task Force (IETF), the most basic cloud-
service model is that of providers offering computing infrastructure – virtual machines
and other resources – as a service to subscribers. Infrastructure as a service (IaaS) refers
to online services that provide high-level APIs used to dereference various low-level
details of underlying network infrastructure like physical computing resources,
location, data partitioning, scaling, security, backup etc. A hypervisor, such as Xen,
Oracle Virtual Box, Oracle VM, KVM, VMware ESX/ESXi, or Hyper-V, LXD, runs
the virtual machines as guests.

IaaS clouds often offer additional resources such as a virtual-machine disk-

image library, raw block storage, file or object storage, firewalls, load balancers, IP
addresses, virtual local area networks (VLANs), and software bundles.

IaaS-cloud providers supply these resources on-demand from their large pools
of equipment installed in data centers. For wide-area connectivity, customers can use
either the Internet or carrier clouds (dedicated virtual private networks). To deploy their
applications, cloud users install operating-system images and their application software
on the cloud infrastructure. In this model, the cloud user patches and maintains the
operating systems and the application software. Cloud providers typically bill IaaS
services on a utility computing basis: cost reflects the amount of resources allocated
and consumed.

Platform as a service (PaaS)

Some integration and data management providers have also embraced

specialized applications of PaaS as delivery models for data solutions. Examples
include iPaaS (Integration Platform as a Service) and dPaaS (Data Platform as a
Service). iPaaS enables customers to develop, execute and govern integration
flows.[80] Under the iPaaS integration model, customers drive the development and
deployment of integrations without installing or managing any hardware or
middleware.

dPaaS delivers integration—and data-management—products as a fully

managed service. Under the dPaaS model, the PaaS provider, not the customer,
11
manages the development and execution of data solutions by building tailored data
applications for the customer. dPaaS users retain transparency and control over data
through data-visualization tools. Platform as a Service (PaaS) consumers do not manage
or control the underlying cloud infrastructure including network, servers, operating
systems, or storage, but have control over the deployed applications and possibly
configuration settings for the application-hosting environment.

Software as a service (SaaS)

In the software as a service (SaaS) model, users gain access to application software and
databases. Cloud providers manage the infrastructure and platforms that run the
applications. SaaS is sometimes referred to as "on-demand software" and is usually
priced on a pay-per-use basis or using a subscription fee.[85] In the SaaS model, cloud
providers install and operate application software in the cloud and cloud users access
the software from cloud clients. Cloud users do not manage the cloud infrastructure and
platform where the application runs. This eliminates the need to install and run the
application on the cloud user's own computers, which simplifies maintenance and
support.

The pricing model for SaaS applications is typically a monthly or yearly flat fee
per user, so prices become scalable and adjustable if users are added or removed at any
point. Proponents claim that SaaS gives a business the potential to reduce IT operational
costs by outsourcing hardware and software maintenance and support to the cloud
provider. This enables the business to reallocate IT operations costs away from
hardware/software spending and from personnel expenses, towards meeting other
goals. In addition, with applications hosted centrally, updates can be released without
the need for users to install new software.

Security as a service (SECaaS)

Security as a service (SECaaS) is a business model in which a large service

provider integrates their security services into a corporate infrastructure on a
subscription basis more cost effectively than most individuals or corporations can
provide on their own, when total cost of ownership is considered. In this scenario,
security is delivered as a service from the cloud, without requiring on-premises

12
hardware avoiding substantial capital outlays. These security services often include
authentication, anti-virus, anti-malware/spyware, intrusion detection, and security
event management, among others.

Mobile "backend" as a service (MBaaS)

In the mobile "backend" as a service (m) model, also known as backend as a

service (BaaS), web app and mobile app developers are provided with a way to link
their applications to cloud storage and cloud computing services with application
programming interfaces (APIs) exposed to their applications and custom software
development kits (SDKs). Services include user management, push notifications,
integration with social networking services and more. This is a relatively recent model
in cloud computing, with most BaaS start ups dating from 2011 or later but trends
indicate that these services are gaining significant mainstream traction with enterprise
consumers.

Serverless computing

Serverless computing is a cloud computing code execution model in which the

cloud provider fully manages starting and stopping virtual machines as necessary to
serve requests, and requests are billed by an abstract measure of the resources required
to satisfy the request, rather than per virtual machine, per hour. Despite the name, it
does not actually involve running code without servers. Serverless computing is so
named because the business or person that owns the system does not have to purchase,
rent or provision servers or virtual machines for the back-end code to run on.

Cloud clients

Users access cloud computing using networked client devices, such as desktop
computers, laptops, tablets and smartphones and any Ethernet-enabled device such as
Home Automation Gadgets. Some of these devices—cloud clients—rely on cloud
computing for all or a majority of their applications so as to be essentially useless
without it. Examples are thin clients and the browser-based Chrome book. Many cloud

13
applications do not require specific software on the client and instead use a web browser
to interact with the cloud application. With Ajax and HTML5 these Web user interfaces
can achieve a similar, or even better, look and feel to native applications. Some cloud
applications, however, support specific client software dedicated to these applications
(e.g., virtual desktop clients and most email clients). Some legacy applications (line of
business applications that until now have been prevalent in thin client computing) are
delivered via a screen-sharing technology.

14
 Chapter 2
PROJECT WORK
1.1 AIM & OBJECTIVE

The aim of my project is to manage the student information/ data in a good

and in an effective manner.

Name of the project: Student Information Management

What we will Do?

As in the admin part of the cloud computing, we enter the data of a student on
the platform (Salesforce) by the student details (which is created by the organization
or institution which contains the required information). After adding the data of many
students we generate a report by applying some validations and schedule it then select
the user to whom it is going to be send. Then selected user will get a report by email
which contain the information of the selected students

2.2 Platform

Fig. 2.2.1
15
Salesforce.com, is an American cloud computing company headquartered in San
Francisco, California. Though its revenue comes from a customer relationship
management (CRM) product, Salesforce also capitalizes on commercial applications of
social networking through acquisition. As of early 2016, it is one of the most highly
valued American cloud computing companies with a market capitalization above $61
billion. In August 2017, Salesforce announced that it had breached the $10 billion
revenue run rate becoming the first enterprise cloud company to do so.

Future of Student Information Management

Student information Management System can be used by educational institutes to

maintain the records of students easily. Achieving this objectives is difficult using a
manual system as the information is scattered, can be redundant and collecting relevant
information may be very time consuming. All these problems are solved using online
registration forms.

The objective of student information management system is to allow the administrator

of any organization to edit and find out the personal details of a student and allows the
student to keep up to date his profile. It will also facilitate keeping all the records of the
student, such as their id, name, mailing address, phone number, DOB etc. So all the
information about a student will be available in a few seconds.

Overall, it will make Student Information Management an easier job for the
administrator and the student of any organization.

Future Scope

Without a student information management, managing and maintaining the details

of the student is a tedious job for any organization or institution.

Student information management system will store all the details of the students
including their background information, educational qualifications, personal details and
all the information related to their resume.

16
2.3 Project Snapshots

USER LOGIN PAGE

Fig. 2.3.1

This is the user login page by entering login id and password we enter into the salesforce
platform.

17
 Successfully Login

Fig. 2.3.2

This figure shows the successful login of the user into the salesforce platform. There is
a search box in the left side of the page where we can search for the apps, users, objects,
etc. to be built. Already builded apps are also shown on the page.

18
 Student Details Form (Clicked)
Shows entered data/forms

Fig. 2.3.3

Object Student Details is shown at the left side of the page by clicking on it we enter
into the page where the data of already registered students is shown along with a ‘new’
button.

19
 Student Details form for new data

Fig. 2.3.4

By clicking on ‘new’ button we reach the page where the form appears for entering the
new data into it. We can enter the new data here for any new student.

20
 Data enter by user

Fig. 2.3.5

This figure shows the data of new student enter by the users. Fields are shown along
with the description of the field. Like first name, last name, roll no., email, etc.

21
 Information Saved

Fig. 2.3.6

After entering the data of the student save button is clicked and the saved information
of the student is shown in this figure. Here the data of the student named Priyanka is
shown.

22
 Creating Report

Fig. 2.3.7

Now for creating report we need to click on ‘+’ icon on the left –top side of the page
by clicking on the new tab (‘+’) icon we reach the page shown in the figure. In the tabs
shown in the page click on ‘Report icon’ for creating report.

23
 New Report Button and List of existing report

Fig. 2.3.8

By clicking on the ‘Report icon’ we enter the page where there is a button for creating
new report and the list of already existing report is also shown below. New report button
is clicked for creating new report.

24
 Select object for report

Fig. 2.3.9

By clicking on the new report button a page get opened where we see all the objects.
Choose the required object on which we wish to create a report from the existing
objects.

25
 Report Menu

Fig. 2.3.10

Report Menu page is shown in the figure. Here we can see the data of all the registered
students. Along with the column shown on the left side of the page where all the fields
are shown.

26
 Applying Validation

Fig. 2.3.11

If we wish to generate the generic report for all the students then just click on ‘Run
Report’ button visible on the page. But if we wish to create a report of some specific
students then we need to apply a validation. As shown in figure a validation is applied
“ student branch equals me”. This means that students belonging to mechanical
branch are only selected students.

27
 Validation Applied

Fig. 2.3.12

After specifying a validation rule click on ‘OK’ button so that validation can be
applied. Now we can see only those students who had opt mechanical branch.

28
 Drag and Drop required fields

Fig. 2.3.13

On the left side of the page a column is appearing where we can see all the fields of the
student details form. Such as first name, last name, roll no., email address, etc.

Drag and Drop the required field.

29
 Run Report

Fig. 2.3.14

After applying validation and dropping the required field now we run the report by
clicking on run report button , a broke down list appears as shown in the figure
containing two rows –‘Run Report Now’ and ‘ Schedule Future Run’.

30
 Information for Schedule Run

Fig. 2.3.15
We can run report in two ways by clicking on run report now or by scheduling report
for future run. Figure shows the schedule of the report for future run.

31
 Select start date, end date, time for schedule run

Fig. 2.3.16

Now schedule is made for the report by filling the required column shown in the figure.
Select start date, end date, start time for making the schedule of the report. Also select
the email criteria for sending mail either to you or to another user.

32
 Saving Report Schedule

Fig. 2.3.17

After doing all the task the last task is to save the schedule of the report which we wish
to run in future. After saving the schedule for future run a mail is sent to the user
containing the report of the students having mechanical branch.

33
 Report via Mail

Fig. 2.3.18

Mail containing the Report of the students studying in mechanical

branch.

34
 Chapter 3

3.1 Result and Discussion

The above report via mail is the result of the student management system. Student
information management system lead to a better organization structure since the
information management of the students is well structured and also lead to better as
well as efficient utilization of resources.

Student information management system can be used by educational institutions to

maintain the records of students easily. Achieving this objective is difficult using a
manual system as the information is scattered.

35
 Chapter 4

4.1 Conclusion and Future Scope

 The Student Information Management System can be enhanced to include some

other functionality like marks, attendance management.
 Talent management of students based on their performance evaluation can be
added.
 Social networking can also be added wherein students can infract with each
other.
 Online class functionality can be added.
 Can evolve as an online institution.
 Functionality of chat and messages can be added.
 Online resume builder functionality can be added.

36