Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Download
Standard view
Full view
of .
Save to My Library
Look up keyword
Like this
0Activity
0 of .
Results for:
No results containing your search query
P. 1
Rp1i3 Report Moving Sne to the Cloud

Rp1i3 Report Moving Sne to the Cloud

Ratings: (0)|Views: 2 |Likes:
Published by Nadia Metoui

More info:

Published by: Nadia Metoui on Mar 11, 2012
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

03/11/2012

pdf

text

original

 
UNIVERSITY OF AMSTERDAM
Moving SNE to the Cloud
RP1.3 Report 
Sudesh Jethoe30-12-2011
Summary: In this research the OpenStack framework is used to build a private, public and hybridcloud for the System and Networking education of the University of Amsterdam. Discussed are thesetup used and problems encountered while building it.*[27]
 
Moving SNE to the Cloud0 Index
1/21
 
Index
Fout! Bladwijzer niet gedefinieerd.
 3 Research Questions ............................................................................................................... 44 Theory ...............................................................................
Fout! Bladwijzer niet gedefinieerd.
Fout! Bladwijzer niet gedefinieerd.
Fout! Bladwijzer niet gedefinieerd.
 
Moving SNE to the Cloud1 Introduction
2/21
 
1
 
Introduction
The cloud is these days often considered as a valuable resource not only in businesses, but also ineducational environments. The advantages of improved scalability, agility, consolidation and costefficiency in comparison to regular server based computing are leveraged already for some servicesin universities [1]. One might ask, how are these advantages achieved?
1.1
 
Clustering, Scalability
In classic server based computing a user would log in to a physical machine which runs the requiredservice. An example of a service which such a physical server would host is e-mail. A physical serverhas a maximum amount of users it is able to serve. This, because a physical machine can only hold acertain amount of physical resources (being disks for storage and processors for computationalpower).Due to increasing amounts of users, more and more expensive servers needed to be bought or theyneeded to be upgraded. To be able to serve the same amount of users as one big server, a methodwas developed to cluster smaller (and cheaper) machines together. By using clusters, services couldbe spread over multiple machines and as a side effect risks of downtime were also mitigated. Thismitigation was achieved by making sure that the software running on top of these system would takecare of outages of not only disks or processors, but complete machines in a cluster. As an addedeffect, these systems had the advantage of being more scalable than classic servers, since serverscould be added and removed when needed.A downside to clusters however, is that programs written for classical operating systems cannot run on a cluster. Since classical applications needed to be run on physical servers, running non-cluster operating systems, the advantages of cluster computing could only be utilized to a certainextent.
1.2
 
Consolidation, Virtualization
The increasing capabilities of physical servers (more computational power and storage) on the otherhand, lead to the development of methods to do the exact opposite of clustering, consolidation.Consolidation being methods to run multiple services on a single server as opposed to running asingle service on multiple servers. Although the UNIX time sharing system enabled concurrent usageof systems already in the early stages of server based computing, methods of extended segregationof processes were deviced
for added security. Examples of these so called “Sandbox”
methods arethe BSD jails and Unix chroot environments.A method developed at a later time, allowed to run not only one but multiple of these classical
operating systems not directly on physical hardware, but on top of a so called “hypervisor”.
Thismethod is known as virtualization and consists of a software layer running on the physical hardwareand takes care of the distribution of physical resources amongst the operating systems which run ontop of it.
Virtualized operating systems are also known as virtual machines (VM’s).
Virtualizationincreased security by ensuring services did not run in the same environment and increased optionsfor consolidation, since it became possible to run services running on different operating systems tobe hosted on the same physical machine.
1.3
 
Provisioning, Agility
Fully utilizing the capacity of clusters was also an issue. When running services directly on top of physical hardware, it is not possible to plan the capacity of a server on the average amount of users.Servers should be prepared to handle a peak capacity. Unfortunately this means that servers are idle

You're Reading a Free Preview

Download
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->