Professional Documents
Culture Documents
and Services
Flavio Ishii
Computer Science Department
University of Saskatchewan
SK S7N 5C9, Canada
foi822@mail.usask.ca
Figure 2: Cloud Computing Visibility Levels. managing a system with multiple provider implementations
very difficult. Different APIs would need to be learned and
if changes occurred the system needs to deal with it through
commonly used. Applications in this visibility may deploy re-factoring or costly re-implementations. Until a proper
their own services for other applications to consume or con- Cloud Interoperability standard has been set, new services
sume exist may continue to emerge offering such interoperability man-
ing services from external sources. This visibility also con- agement for a lofty price.
tains the most CCS products available due to its accessibility Much work is required to establish an open cloud inter-
atttributes. When deploying to the Public Cloud the appli- operability standard, which is currently being spearheaded
cation’s time to develop, resources or cost, and custom scope by Open Grid Forum [9]. To show how Hybrid Clouds can
will play a key role in deciding which CCSP and CCS layer provide scalability, a simple scenario can be drawn up where
to choose. appropriate tasks are pushed to the Public Cloud in order
to offset the over loaded Private Cloud. Another scenario
2.2.2 Private Cloud could make use of a Virtual Private Network when offered
The only difference between a Private and a Public Cloud by the Public Cloud provider to handle sensitive and mis-
is that its services are only offered within a private virtual sion critical data. If company policies allow for the data
network setting. A Private Cloud can be hosted by a CCSP to be hosted in such an environment then the Public Cloud
like AWS Virtual Private Connection (VPC) and Rackspace can basically mirror the Private Cloud functionalities. Oth-
Private Hosting or they can be located internally, in the erwise only appropriate or safe tasks can be pushed to the
same premise as the organization utilizing it, for reasons of Public Cloud, to offset the workload from the Private Cloud.
performance and legal policies.
An internal Private Cloud is deployed with recent tools 3. PROBLEM AND METHODOLOGY
such as Eucalyptus [5] an open source IaaS or Aneka [6] a The remaining of this paper will focus on answering the
.NET PaaS. Such tools grant the ability to harness the re- following question: Given the system’s attributes, usage
sources within a network in similar ways that commercial properties, business and management concerns, and data
IaaS and PaaS providers accomplish it. Eucalyptus was in- privacy policies how should a software team cope with the ar-
troduced for the academic research arena and it has been chitectural decisions of implementing a cloud solution? We
adopted by the industry to create their own internal pri- illustrate the main decision process in Figure 3, starting with
vate clouds. Aneka is similarly deployed as a PaaS but it the assumption that the application components discussed
is market oriented with its built-in pricing and accounting in this section map nicely with the cloud, so that focus is
features. only placed on the cloud-based solution.
Ideally a solution already exists in a Public Cloud as a
2.2.3 Hybrid Cloud service that can be re-used or built on to. If the Public
A Hybrid Cloud is much like an extended Private Cloud Cloud can be selected as an option, the next step is to dis-
into the public domain [7], although it can remain com- cuss what CCS layer of abstraction to use (IaaS, PaaS, or
pletely private. Hybrid Clouds are the most complex cloud SaaS). Once the service layer has been chosen a CCSP is
solutions due to data consistency concerns across the vir- decided on. Each provider has their own payment model,
tual resources, security protocols involved, and management services, management tools and APIs, and if they are not
complexity. Cloud management tools like RightScale, Joyent using another’s infrastructure then they are using their own
Cloud Control, and AWS VPC become very useful in main- server farms. Another decision to consider is how interoper-
taining all the types of clouds involved and their server im- ability between the chosen public providers can be done to
ages. However, these tools are not very affordable for small cut down on development and management costs.
to medium sized companies, the only current alternative is System usage and requirements pose a lot of constraints,
to manage it manually. As pointed out in the [8] paper, resulting in the need to control many aspects of the infras-
the lack of standards between Cloud Provider APIs makes tructure and choosing a service that is less autonomous.
The MRP system is the core or heartbeat of the company,
without it nothing is produced nor sold. An online presence
is not advantageous for its core functionality due to potential
issues with the host or local ISP network. This component
manages the ever growing manufacturing process, resource
logs, and inventory management in a redundant and efficient
manner. System users: Floor Production Managers, Opera-
tors, and Administrative Professionals in the same physical
location as the Internal Private Cloud. Requirements: High
availability, redundancy, and performance so that services
provided to the manufacturing plant are not disrupted and
the operation is not halted. Portable and modular code so
that new technologies or new machines can be easily ported
and changed. Single-tenant machine infrastructure for bet-
ter stability and performance. Potential cloud-based tools:
Eucalyptus IaaS, Aneka PaaS
Figure 4: Implementation of the Cloud System Ex- 4.2 Milestone 2: Parallel Computing of Re-
ample.
ports (Hybrid Cloud Solution)
Periodic reports tend to be resource hogs due to the sheer
There is a trade off as between satisfying a system’s require- amount of data it needs to process and the time it takes
ments versus how autonomous the system can be, with more to execute on a single machine. If reports are securely out-
autonomous leaning toward Public Clouds as pointed out in sourced to a Public IaaS provider via a secured network
the discussion for Figure 2 in Section 2.2. Hence, if the appli- connection it can be economically sound as pointed out in
cation is not suited for the Public Cloud then the next step the examples given by [2]. The hosted Private Cloud can
is to look at whether a Hybrid Cloud solution is feasible. create as many instances required to receive the compressed
One of the likely cases for this option is if mission critical or data and process the result in parallel. As long as upload-
sensitive data handling application modules can be deployed ing the data fits the economies of scale then it is a fitting
in the Private Cloud and other less sensitive modules can be solution. System users: Professional Administrators, Man-
deployed in Public Cloud. The other likely case is if a Pub- agers, Accountants in the same physical location as the In-
lic Cloud provider can work in parallel with and provide a ternal Private Cloud. Requirements: Secured dedicated line
secure virtual network to connect with the Private Cloud, if from hosted Private Cloud IaaS to internal Private Cloud
there are no strict policies on data handling. IaaS. Web services running on the hosted Private Cloud IaaS
Lastly, if the Hybrid Cloud option is not feasible the sys- to accept requests only from the internal Private Cloud’s
tem is deployed strictly in a Private Cloud. This is the IP. The encryption and decryption is an additional security
result of strict policies, reliability, performance, and acces- measure as it is unsure what type of security standards are
sibility requirements forcing the entire system and data to met on different cloud providers. The hybrid management
reside within the physical premise of the organization. The tool is optional but it is good to have in case complexity rises.
necessary personnel, machine, and networking resources will Potential cloud-based tools: Any Public IaaS provider with
need to be procured to support this solution. a hybrid management tool (i.e. AWS VPC, RightScale) as
an option.