Cloud Computing Mechanisms
Chapter 7 – Infrastructure
Chapter 8 – Specialized
Chapter 9 – Management
Chapter 10 – Security (Will be discussed doing the security
module)
What is a mechanism?
a system of parts working together in a machine; a piece of
machinery.
Learning Outcomes
Understand basic concepts and terminology relating to cloud
computing
Understand virtualization technology
Cloud Characteristics mentioned in Chapter 4
The following six specific characteristics are common to the
majority of cloud environments:
• on-demand usage
• ubiquitous access
• multitenancy (and resource pooling)
• elasticity
• measured usage
• resiliency
Cloud CharacteristicsCloud Mechanisms
On – Demand UsageHypervisorVirtual ServerReady-Made
EnvironmentResource ReplicationRemote Administration
EnvironmentResource Management SystemSLA Management
SystemBilling Management SystemUbiquitous AccessLogical
Network PerimeterMulti-Device Broker
Multitenancy / Resource PoolingLogical Network
PerimeterHypervisorResource ReplicationResource
ClusterResource Management System
ElasticityHypervisorCloud Usage MonitorAutomated Scaling
ListenerResource ReplicationLoad BalancerResource
Management System
Measured UsageHypervisorCloud Usage MonitorSLA
MonitorPay-Per-Use MonitorAudit MonitorSLA Management
SystemBilling Management System
ResiliencyHypervisorResource ReplicationFailover
SystemResource ClusterRemote Management System
Cloud Infrastructure Mechanisms
Chapter 7
Cloud Infrastructure Mechanisms
7.1 Logical Network Perimeter
7.2 Virtual Server
7.3 Cloud Storage Device
7.4 Cloud Usage Monitor
7.5 Resource Replication
7.6 Ready-Made Environment
7.1 Logical Network Perimeter
Logical Network Perimeter
Defined as the isolation of a network environment from the rest
of a communications network, the logical network perimeter
establishes a virtual network boundary that can encompass and
isolate a group of related cloud-based IT resources that may be
physically distributed
This mechanism can be implemented to:
isolate IT resources in a cloud from non-authorized users
isolate IT resources in a cloud from non-users
isolate IT resources in a cloud from cloud consumers
control the bandwidth that is available to isolated IT resources
Logical Network Perimeter
Logical network perimeters are typically established via
network devices that supply and control the connectivity of a
data center and are commonly deployed as virtualized IT
environments that include:
• Virtual Firewall – An IT resource that actively filters network
traffic to and from the isolated network while controlling its
interactions with the Internet.
• Virtual Network – Usually acquired through VLANs, this IT
resource isolates the network environment within the data
center infrastructure.
7.2 Virtual Server
Virtual Server
A virtual server is a form of virtualization software that
emulates a physical server. Virtual servers are used by cloud
providers to share the same physical server with multiple cloud
consumers by providing cloud consumers with individual virtual
server instances.
Virtual Server
7.3 Cloud Storage Device
Cloud Storage Device
The cloud storage device mechanism represents storage devices
that are designed specifically for cloud-based provisioning.
Instances of these devices can be virtualized, similar to how
physical servers can spawn virtual server images
Cloud Storage Levels
Cloud storage device mechanisms provide common logical units
of data storage, such as:
• Files – Collections of data are grouped into files that are
located in folders.
• Blocks – The lowest level of storage and the closest to the
hardware, a block is the smallest unit of data that is still
individually accessible.
• Datasets – Sets of data are organized into a table-based,
delimited, or record format.
• Objects – Data and its associated metadata are organized as
Web-based resources.
Network Storage Interfaces
Object Storage Interfaces
database storage interfaces
Relational Data Storage
Non-Relational Data Storage
7.4 Cloud Usage Monitor
Parent monitoring mechanism
Monitoring agent
Resource agent
Polling agent
Cloud Usage Monitor
Monitoring Agent
Cloud Usage Monitor
resource agent
Cloud Usage Monitor
Polling Agent
7.5 Resource Replication
Resource Replication
Creating multiple instances of the same IT resource
7.6 Ready – Made Environment
READY-MADE ENVIRONMENT
Is a defining component of the PaaS cloud delivery model that
represents a pre-defined, cloud-based platform comprised of a
set of already installed IT resources.
Typical pre-installed IT resources are:
Databases
Middleware
Development tools
Governance tools
READY-MADE ENVIRONMENT
Business and Technical Perspectives of Cloud Mechanisms
Specialized Cloud Mechanisms
Chapter 8
Cloud CharacteristicsCloud Mechanisms
On – Demand UsageHypervisorVirtual ServerReady-Made
EnvironmentResource ReplicationRemote Administration
EnvironmentResource Management SystemSLA Management
SystemBilling Management SystemUbiquitous AccessLogical
Network PerimeterMulti-Device Broker
Multitenancy / Resource PoolingLogical Network
PerimeterHypervisorResource ReplicationResource
ClusterResource Management System
ElasticityHypervisorCloud Usage MonitorAutomated Scaling
ListenerResource ReplicationLoad BalancerResource
Management System
Measured UsageHypervisorCloud Usage MonitorSLA
MonitorPay-Per-Use MonitorAudit MonitorSLA Management
SystemBilling Management System
ResiliencyHypervisorResource ReplicationFailover
SystemResource ClusterRemote Management System
Specialized Cloud Mechanisms
8.1 Automated Scaling Listener
8.2 Load Balancer
8.3 SLA Monitor
8.4 Pay-Per-Use Monitor
8.5 Audit Monitor
8.6 Failover System
8.7 Hypervisor
8.8 Resource Cluster
8.9 Multi-Device Broker
8.10 State Management Database
Automated Scaling Listener
Automated scaling listener mechanism
Monitors and tracks communication
Deployed near firewall
Track workload status information
IT resources can be scaled out or in
Automatic notification to cloud consumer with workloads
exceed or fall below thresholds
Load Balancer
A common approach to horizontal scaling is to balance
workload across two or more IT resources
Goal is to increase performance
Can perform specialized work load distribution functions:
Asymmetric
Workload Prioritization
Content-Aware Distribution
Load Balancer
Have configured set of performance and QoS rules for
optimizing performance for IT resources
Located between the IT Resource generating and performing the
workload
Can be hidden from the cloud consumers
SLA Monitor
Observes the runtime performance of cloud services that are
fulfilling the contractual QoS requirements
Data collected by the monitor is process by the SLA
management system to be aggregated into SLA reporting
metrics
The system can proactively repair or failover cloud services
Pay-Per-Use Monitor
Measures cloud-based IT resources usage in accordance with
predefined pricing parameters
Typical monitoring variables are:
Request / response message quantity
Transmitted data volume
Bandwidth consumption
Data collected by the pay-per-user monitor is processed by a
billing management system
Audit Monitor
Collects audit tracking data for networks and IT resources in
support of regulatory and contractual obligations
Failover System
Increase reliability and availability of IT resources
Is configured to automatically switch over to a redundant or
standby IT resource
Are commonly used for mission critical programs and reusable
services that can introduce a single point of failure
The resource replication mechanism is sometimes utilized by
the failover system
Failovers two basic configurations:
Active – Active, redundant implementations of the IT resources
– synchronously
Active – Passive, standby or inactive implementation is
activated
Hypervisor
Used to generate virtual server instances of a physical server
Limited to one physical server
Hypervisors have limited virtual server management features
Hypervisor software can be installed directly in bare metal
servers
Resource Cluster
Cloud-based IT resources that are geographically diverse can be
logically combined into groups to improve allocation and use
Groups multiple IT resources so they can operate as one - This
increases:
Computing capacity
Load balancing
Availability
Resource Cluster
Common resource cluster types:
Server Cluster
Database Cluster
Large Dataset Cluster
Two basic resource clusters:
Load Balanced
High Availability
Provision of cluster is more expensive than a single IT resource
Multi-Device Broker
Mechanism use to facilitate runtime data transformation so as to
make a cloud service accessible to a wider range of cloud
service consumer programs and devices
Mutli-device brokers commonly exist as gateways or
incorporate gateway components such as:
XML
Cloud stage gateway
Mobile device gateway
State Management Database
Is a storage device that is used to temporarily persist state data
for software programs.
Is an alternative to caching state data in memory
Chapter 9. Cloud Management Mechanisms
Chapter 9. Cloud Management Mechanisms
9.1 Remote Administration System
9.2 Resource Management System
9.3 SLA Management System
9.4 Billing Management System
Remote Administration System
The remote administration system mechanism (Figure 9.1)
provides tools and user-interfaces for external cloud resource
administrators to configure and administer cloud-based IT
resources
Remote Administration System
Two primary types of portals created with the Remote
Administration System:
Usage and Administration Portal
Self-Service Portal
Remote Administration System
Usage and Administration Portal – A general purpose portal that
centralizes management controls to different cloud-based IT
resources and can further provide IT resource usage reports.
Remote Administration System
Self-Service Portal – This is essentially a shopping portal that
allows cloud consumers to search an up-to-date list of cloud
services and IT resources that are available from a cloud
provider (usually for lease). The cloud consumer submits its
chosen items to the cloud provider for provisioning
Tasks that can commonly be performed by cloud consumers via
a remote administration console include:
• configuring and setting up cloud services
• provisioning and releasing IT resource for on-demand cloud
services
• monitoring cloud service status, usage, and performance
• monitoring QoS and SLA fulfillment
• managing leasing costs and usage fees
• managing user accounts, security credentials, authorization,
and access control
• tracking internal and external access to leased services
• planning and assessing IT resource provisioning
• capacity planning
Resource Management System
The resource management system mechanism helps coordinate
IT resources in response to management actions performed by
both cloud consumers and cloud providers
Core to this system is the virtual infrastructure manager (VIM)
that coordinates the server hardware so that virtual server
instances can be created from the most expedient underlying
physical server.
A VIM is a commercial product that can be used to manage a
range of virtual IT resources across multiple physical servers.
For example, a VIM can create and manage multiple instances
of a hypervisor across different physical servers or allocate a
virtual server on one physical server to another (or to a resource
pool).
Resource management system functions can be accessed by
cloud resource administrators employed by the cloud provider
or cloud consumer. Those working on behalf of a cloud provider
will often be able to directly access the resource management
system’s native console.
SLA Management System
The SLA management system mechanism represents a range of
commercially available cloud management products that provide
features pertaining to the administration, collection, storage,
reporting, and runtime notification of SLA data
An SLA management system deployment will generally include
a repository used to store and retrieve collected SLA data based
on pre-defined metrics and reporting parameters. It will further
rely on one or more SLA monitor mechanisms to collect the
SLA data that can then be made available in near-real time to
usage and administration portals to provide on-going feedback
regarding active cloud services
A cloud service consumer interacts with a cloud service (1). An
SLA monitor intercepts the exchanged messages, evaluates the
interaction, and collects relevant runtime data in relation to
quality-of-service guarantees defined in the cloud service’s SLA
(2A). The data collected is stored in a repository (2B) that is
part of the SLA management system (3). Queries can be issued
and reports can be generated for an external cloud resource
administrator via a usage and administration portal (4) or for an
internal cloud resource administrator via the SLA management
system’s native user-interface (5).
BILLING MANAGEMENT SYSTEM
The billing management system mechanism is dedicated to the
collection and processing of usage data as it pertains to cloud
provider accounting and cloud consumer billing. Specifically,
the billing management system relies on pay-per-use monitors
to gather runtime usage data that is stored in a repository that
the system components then draw from for billing, reporting,
and invoicing purposes
A cloud service consumer exchanges messages with a cloud
service (1). A pay-per-use monitor keeps track of the usage and
collects data relevant to billing (2A), which is forwarded to a
repository that is part of the billing management system (2B).
The system periodically calculates the consolidated cloud
service usage fees and generates an invoice for the cloud
consumer (3). The invoice may be provided to the cloud
consumer through the usage and administration portal (4).
A Business Case for Google Apps for Education
Problem Statement
Goldfarb School of Nursing (GSON)’s lack of technology
enhancement is a weakness. This weakness causes problems
with: accreditation organizations, students’ satisfaction,
aspiring nurse preparation, budget management, student
retention, and student recruitment.
Analysis of Situation
BJC’s GroupWise email and messenger limit communication
and collaboration among GSON stakeholders. GroupWise
Messenger is not accessible outside the organization firewall,
nor are students able to connect to the organization’s email
system using a mobile device without incurring a cost. Because
instant communication is lost and external communication is
limited, students may be dissatisfied. Student dissatisfaction
may have an effect on student retention, student recruitment,
and the reputation of the organization. Moreover, the
technology enhancements could allow better user experiences,
like students learning in the way they want to learn, with
technology.
Beyond email and messenger, other innovative communication
mediums exist. Documents can be shared and collaborated on
in real time and videos can be shared, as with YouTube. These
same approaches can be used in an educational environment to
enhance operational efficiency as well as teaching and learning.
Document sharing would allow students to collaborate with
their peers and professors on projects or homework
assignments. Video sharing can be used for nurse preparation,
student orientation, or to share information related to drug or
alcohol abuse, which is a compliance requirement for Title IX.
Because GSON is limited by the lack of technology
enhancements, third party solutions have been considered for
procurement. For example, Mediacore, a video sharing product,
was reviewed. The purpose of the product would be to share
videos among different stakeholders throughout the College.
Various departments would have the ability to share videos.
While this is a great tool, as you will see in the cost benefit
analysis section of this document, sound fiscal management
would be remiss.
The Higher Learning Commission (HLC), an accrediting body
of the College, requires a plan for innovation and technology.
1. Criterion/standard 5.C.5 states: Institutional planning
anticipates emerging factors, such as technology, demographic
shifts, and globalization.
2. Criterion/standard 3.D.4. states: The institution provides to
students and instructors the infrastructure and resources
necessary to support effective teaching and learning
(technological infrastructure, scientific laboratories, libraries,
performance spaces, clinical practice sites, museum collections,
as appropriate to the institution’s offerings).
To address the problems presented in this business case, Google
Apps for Education is recommended.
Solution
The solution to the problems presented in this business case is
to implement Google Apps for Education (GAE). GAE is
chosen because it addresses the main problem and sub-problems
initially presented in this business case.
Student mobile access - The issue of mobile access for students
will be addressed because this platform allows for access at no
cost to students. This solution also mitigates BJC’s risk
because stakeholders’ email will not be going through the main
email system.
Increases stakeholders’ use and return on investment (ROI) -
The benefit is twofold. We hope to capitalize on stakeholders’
prior knowledge and use of Google Apps that way we increase
our return on investment. The ROI would be faster because
time to full implementation would be less.
Purchase of third party platforms -Google Apps for Education
provides similar solutions to those we are seeking from third
party vendors. This allows us (Administration) to be good
stewards of our budget.
Mission of College/Teaching and Learning - Teaching and
learning / nurse preparation is why we exist. Today’s students
are tech savvy and want to learn that way. To that end, this
solution addresses this problem because it provides a platform
for 21st century teaching and learning to take place. In
addition, because of our ability to better prepare aspiring
nurses, there may be a positive impact on the College’s
reputation that would help sustain and increase our market share
and create a competitive advantage.
Accreditation – This problem is addressed by GAE creating an
environment that provides students and instructors the
infrastructure and resources necessary to support effective
teaching and learning.
Table 1 is a snapshot of how Google Apps for Education
addresses the problems presented in this business case by app.
Table 1
Current Structure vs. Google Apps for Education with benefits
Applications
Current Structure
Google Apps for Education
Benefits
Email
X
X
Adds familiar platform stakeholders know – increase use / ROI
Email mobile access
X – cost for students
X
No cost to students
Messenger
X – not external
X
Increases communication by adding external access
Video Conference – Google Hangout
X
Eliminates need for third party platform / decrease budget
implications
Shared Documents anytime /anywhere
X
Increases collaboration among stakeholders
Video Sharing
X
Eliminates need for third party platform / decrease budget
implications
Calendar
X
X
Increases use among stakeholders because users have prior
knowledge of the system
Appointments
X
Eliminates need for third party platform / decrease budget
implications
Implementation
To implement this solution change would have to take place
from structural, human resource, political, and symbolic
perspectives.
Structural
To implement this project the following platforms or utilities
will be needed:
Google Apps for Education (GAE) - is the platform that allows
us access to the different apps that address the problems
presented in this case.
Google Active Directory (GADS) – is a utility provided by
Google that allows user accounts to be created using
automation. At a given time, the GADS tool will execute by
looking inside of the designated OU in Active Directory. Then,
any changes will be synced with GAE. This process is
encrypted.
Google Apps Password Sync (GAPS) – is a utility provided by
Google that automatically keeps your users’ Google Apps
passwords in sync with their Active Directory passwords.
Whenever a user's Active Directory password is changed, GAPS
pushes the change to Google Apps immediately
Active Directory (AD) – AD is used throughout the organization
for access control. Our students complete clinical experiences
throughout the BJC system; therefore, they still need network
access. For Google Apps for Education, we would need a
student’s “mail” attribute to end in barnesjewishcollege.edu.
Domain Name Services – In the domain control panel for
barnesjewishcollege.edu, the MX record would need to be
changed to point to Google’s mail servers. These mail servers
are provided once we are approved by Google. We would also
need the CNAME setup that points to
webmail.barnesjewishcollege.edu.
Website – The website is used to verify the
barnesjewishcollege.edu domain.
Additional Deployment Information:
https://docs.google.com/document/d/1ixVHcT85nhaU8yYUzi4S
EaEMocqkRSSC_Y5GpUtUCVI/edit
Human Resources
At this point, no new employees are needed; however, technical
and non-technical stakeholders will be affected by this change.
The technical stakeholders are:
1. BJC IS Security – We will need them to make sure that the
risk to BJC infrastructure will not be compromised.
2. BJC IS Email Server Group – We will need this group to
make sure our approach to adding GAE as an email platform
will not interfere with GroupWise.
3. BJC IS Domain Name Services Group – We will need this
group to make the domain changes to the
barnesjewishcollege.edu domain.
4. BJC IS Help Desk Group – This group will need to
understand how to help a student calling for support due to
migrating over to GAE.
5. GSON – Angela Trower – She has access to make changes to
the College’s website.
6. GSON – Information Systems – Information Systems will
need to understand the technology implications as they relates
to GAE.
7. GSON - Instructional Technology – Instructional Technology
would be responsible for communicating the change and
developing a student and faculty training program.
8. GSON - Administrators, Faculty, Staff, and Students
Political
The two key political areas that need to be addressed are:
1. BJC IS approval to implement the proposed solution.
2. GSON stakeholders’ attitude toward change.
To address issue one, this business case has been submitted, and
we are having monthly meetings with BJC IS to work through
the details and build relationships. Issue two will be addressed
by developing a communication and training plan that addresses
GSON stakeholders’ concerns.
Symbolic
Part of the communication plan created by the Instructional
Technology department will mentioned how making this change
prepares the college for future and allows 21st Century teaching
and learning. Change champions would also be identified to
help with this transition.
Cost benefit analysis (CBA)
The cost benefit analysis includes quantitative and qualitative
benefits.
Quantitative Benefits
The cost for not changing our current practice will be a $66,118
initial investment. Every year after until year 5 will cost 49%
of the initial investment or $32,728. Year 5, the cost will
increase due to the SharePoint server equipment replacement
cycle. See tables below.
This CBA does not include labor; however Google Apps
compared to our given structure (GroupWise) and third party
applications is the most appropriate. The fact that GAE is free
is not the only reason for this choice. GAE meets our needs.
Table 2
Current Structure with Third Party Calculations
Applications & Hardware
Use
QTY
Year 1 Cost
Comments
BJC Email Mobile
Mobile Email
800 Students X $10
$8000
1. Recurring cost for new students each year.
2. Paid by students
Mediacore
Video Share
1
$30,000
Annually
BJC-SharePoint Server
Document Share
1
$15,000
Every 5 years
BJC-SharePoint Cals
Document Share
1000 ($11)
$11,000
BJC DropBox
Document Share
1
$390
Appointments
e-Appointments
1
$1728
Annually
TOTAL
$66,118
Does not include labor
Table 3
3 Year Cost Forecast
Application
Year 1 Cost
Year 2 Cost
Year 3 Cost
Comments
Email Mobile
$8000
$1000
$1000
Recurring cost for new students each year
Mediacore
$30,000
$30,000
$30,000
Annually
SharePoint Server
$15,000
Every 5 years
SharePoint Cals
$11,000
BJC DropBox
$390
Appointments
$1728
$1728
$1728
Annually
TOTAL
$66,118
$32,728
$32,728
Annually
Qualitative benefits
The qualitative benefits gained from this implementation are
satisfied students and increased student learning outcomes.
These qualitative benefits also have a positive effect on data
required by the accreditation agencies, student recruitment, and
GSON’s reputation.
Total Cost of Ownership
I do not have the labor costs; therefore, I could not determine
the TCO.
Conclusion - What is the impact of not implementing this new
application?
The price for not addressing these problems presented in this
case study may have an effect on the College:
1. Accreditation;
2. Student experience and satisfaction;
3. Market share and competitive advantage;
4. Over spending; and
5. Antiquated teaching practices.
G.1. BUSINESS CASE IDENTIFICATION
This section provides information that specifies the details of
the business case, such as the following:
• Business Case Name
• Description – A brief summary of the business case’s purpose
and goals.
• Sponsor – Identification of business case stakeholders.
• List of Revisions (optional) – Revisions by date, author, and
approval if control or historical logging is required.
G.2. BUSINESS NEEDS
The expected benefits and requirements that are to be addressed
and fulfilled by cloud adoption are detailed in this part of the
template:
• Background – A description of relevant historical information
that spurred on the motivation for the business case.
• Business Goals – A list of the tactical and strategic business
objectives that are associated with the business case.
• Business Requirements – A list of the business requirements
that are expected to be fulfilled by the achievement of the
business goals.
• Performance Objectives – A list of any relevant performance
objectives related to the business goals and business
requirements.
• Priorities – Business goals, business requirements, and
performance objectives listed in order of priority.
• Affected On-Premise

Cloud Computing MechanismsChapter 7 – InfrastructureChapter .docx

  • 1.
    Cloud Computing Mechanisms Chapter7 – Infrastructure Chapter 8 – Specialized Chapter 9 – Management Chapter 10 – Security (Will be discussed doing the security module) What is a mechanism? a system of parts working together in a machine; a piece of machinery. Learning Outcomes Understand basic concepts and terminology relating to cloud computing Understand virtualization technology Cloud Characteristics mentioned in Chapter 4 The following six specific characteristics are common to the majority of cloud environments: • on-demand usage • ubiquitous access • multitenancy (and resource pooling) • elasticity • measured usage • resiliency Cloud CharacteristicsCloud Mechanisms
  • 2.
    On – DemandUsageHypervisorVirtual ServerReady-Made EnvironmentResource ReplicationRemote Administration EnvironmentResource Management SystemSLA Management SystemBilling Management SystemUbiquitous AccessLogical Network PerimeterMulti-Device Broker Multitenancy / Resource PoolingLogical Network PerimeterHypervisorResource ReplicationResource ClusterResource Management System ElasticityHypervisorCloud Usage MonitorAutomated Scaling ListenerResource ReplicationLoad BalancerResource Management System Measured UsageHypervisorCloud Usage MonitorSLA MonitorPay-Per-Use MonitorAudit MonitorSLA Management SystemBilling Management System ResiliencyHypervisorResource ReplicationFailover SystemResource ClusterRemote Management System Cloud Infrastructure Mechanisms Chapter 7 Cloud Infrastructure Mechanisms 7.1 Logical Network Perimeter 7.2 Virtual Server 7.3 Cloud Storage Device 7.4 Cloud Usage Monitor 7.5 Resource Replication 7.6 Ready-Made Environment
  • 3.
    7.1 Logical NetworkPerimeter Logical Network Perimeter Defined as the isolation of a network environment from the rest of a communications network, the logical network perimeter establishes a virtual network boundary that can encompass and isolate a group of related cloud-based IT resources that may be physically distributed This mechanism can be implemented to: isolate IT resources in a cloud from non-authorized users isolate IT resources in a cloud from non-users isolate IT resources in a cloud from cloud consumers control the bandwidth that is available to isolated IT resources Logical Network Perimeter Logical network perimeters are typically established via network devices that supply and control the connectivity of a data center and are commonly deployed as virtualized IT environments that include: • Virtual Firewall – An IT resource that actively filters network traffic to and from the isolated network while controlling its interactions with the Internet. • Virtual Network – Usually acquired through VLANs, this IT resource isolates the network environment within the data center infrastructure.
  • 4.
    7.2 Virtual Server VirtualServer A virtual server is a form of virtualization software that emulates a physical server. Virtual servers are used by cloud providers to share the same physical server with multiple cloud consumers by providing cloud consumers with individual virtual server instances. Virtual Server 7.3 Cloud Storage Device Cloud Storage Device The cloud storage device mechanism represents storage devices that are designed specifically for cloud-based provisioning. Instances of these devices can be virtualized, similar to how physical servers can spawn virtual server images
  • 5.
    Cloud Storage Levels Cloudstorage device mechanisms provide common logical units of data storage, such as: • Files – Collections of data are grouped into files that are located in folders. • Blocks – The lowest level of storage and the closest to the hardware, a block is the smallest unit of data that is still individually accessible. • Datasets – Sets of data are organized into a table-based, delimited, or record format. • Objects – Data and its associated metadata are organized as Web-based resources. Network Storage Interfaces Object Storage Interfaces database storage interfaces Relational Data Storage Non-Relational Data Storage 7.4 Cloud Usage Monitor Parent monitoring mechanism Monitoring agent Resource agent Polling agent
  • 6.
    Cloud Usage Monitor MonitoringAgent Cloud Usage Monitor resource agent Cloud Usage Monitor Polling Agent 7.5 Resource Replication Resource Replication Creating multiple instances of the same IT resource 7.6 Ready – Made Environment
  • 7.
    READY-MADE ENVIRONMENT Is adefining component of the PaaS cloud delivery model that represents a pre-defined, cloud-based platform comprised of a set of already installed IT resources. Typical pre-installed IT resources are: Databases Middleware Development tools Governance tools READY-MADE ENVIRONMENT Business and Technical Perspectives of Cloud Mechanisms Specialized Cloud Mechanisms Chapter 8 Cloud CharacteristicsCloud Mechanisms On – Demand UsageHypervisorVirtual ServerReady-Made EnvironmentResource ReplicationRemote Administration EnvironmentResource Management SystemSLA Management SystemBilling Management SystemUbiquitous AccessLogical Network PerimeterMulti-Device Broker Multitenancy / Resource PoolingLogical Network PerimeterHypervisorResource ReplicationResource
  • 8.
    ClusterResource Management System ElasticityHypervisorCloudUsage MonitorAutomated Scaling ListenerResource ReplicationLoad BalancerResource Management System Measured UsageHypervisorCloud Usage MonitorSLA MonitorPay-Per-Use MonitorAudit MonitorSLA Management SystemBilling Management System ResiliencyHypervisorResource ReplicationFailover SystemResource ClusterRemote Management System Specialized Cloud Mechanisms 8.1 Automated Scaling Listener 8.2 Load Balancer 8.3 SLA Monitor 8.4 Pay-Per-Use Monitor 8.5 Audit Monitor 8.6 Failover System 8.7 Hypervisor 8.8 Resource Cluster 8.9 Multi-Device Broker 8.10 State Management Database Automated Scaling Listener Automated scaling listener mechanism Monitors and tracks communication Deployed near firewall Track workload status information IT resources can be scaled out or in Automatic notification to cloud consumer with workloads
  • 9.
    exceed or fallbelow thresholds Load Balancer A common approach to horizontal scaling is to balance workload across two or more IT resources Goal is to increase performance Can perform specialized work load distribution functions: Asymmetric Workload Prioritization Content-Aware Distribution Load Balancer Have configured set of performance and QoS rules for optimizing performance for IT resources Located between the IT Resource generating and performing the workload Can be hidden from the cloud consumers SLA Monitor Observes the runtime performance of cloud services that are fulfilling the contractual QoS requirements Data collected by the monitor is process by the SLA management system to be aggregated into SLA reporting metrics The system can proactively repair or failover cloud services Pay-Per-Use Monitor Measures cloud-based IT resources usage in accordance with predefined pricing parameters Typical monitoring variables are: Request / response message quantity
  • 10.
    Transmitted data volume Bandwidthconsumption Data collected by the pay-per-user monitor is processed by a billing management system Audit Monitor Collects audit tracking data for networks and IT resources in support of regulatory and contractual obligations Failover System Increase reliability and availability of IT resources Is configured to automatically switch over to a redundant or standby IT resource Are commonly used for mission critical programs and reusable services that can introduce a single point of failure The resource replication mechanism is sometimes utilized by the failover system Failovers two basic configurations: Active – Active, redundant implementations of the IT resources – synchronously Active – Passive, standby or inactive implementation is activated Hypervisor Used to generate virtual server instances of a physical server Limited to one physical server Hypervisors have limited virtual server management features Hypervisor software can be installed directly in bare metal servers Resource Cluster
  • 11.
    Cloud-based IT resourcesthat are geographically diverse can be logically combined into groups to improve allocation and use Groups multiple IT resources so they can operate as one - This increases: Computing capacity Load balancing Availability Resource Cluster Common resource cluster types: Server Cluster Database Cluster Large Dataset Cluster Two basic resource clusters: Load Balanced High Availability Provision of cluster is more expensive than a single IT resource Multi-Device Broker Mechanism use to facilitate runtime data transformation so as to make a cloud service accessible to a wider range of cloud service consumer programs and devices Mutli-device brokers commonly exist as gateways or incorporate gateway components such as: XML Cloud stage gateway Mobile device gateway State Management Database Is a storage device that is used to temporarily persist state data for software programs.
  • 12.
    Is an alternativeto caching state data in memory Chapter 9. Cloud Management Mechanisms Chapter 9. Cloud Management Mechanisms 9.1 Remote Administration System 9.2 Resource Management System 9.3 SLA Management System 9.4 Billing Management System Remote Administration System The remote administration system mechanism (Figure 9.1) provides tools and user-interfaces for external cloud resource administrators to configure and administer cloud-based IT resources Remote Administration System Two primary types of portals created with the Remote Administration System: Usage and Administration Portal Self-Service Portal
  • 13.
    Remote Administration System Usageand Administration Portal – A general purpose portal that centralizes management controls to different cloud-based IT resources and can further provide IT resource usage reports. Remote Administration System Self-Service Portal – This is essentially a shopping portal that allows cloud consumers to search an up-to-date list of cloud services and IT resources that are available from a cloud provider (usually for lease). The cloud consumer submits its chosen items to the cloud provider for provisioning Tasks that can commonly be performed by cloud consumers via a remote administration console include: • configuring and setting up cloud services • provisioning and releasing IT resource for on-demand cloud services • monitoring cloud service status, usage, and performance • monitoring QoS and SLA fulfillment • managing leasing costs and usage fees • managing user accounts, security credentials, authorization, and access control • tracking internal and external access to leased services • planning and assessing IT resource provisioning • capacity planning
  • 14.
    Resource Management System Theresource management system mechanism helps coordinate IT resources in response to management actions performed by both cloud consumers and cloud providers Core to this system is the virtual infrastructure manager (VIM) that coordinates the server hardware so that virtual server instances can be created from the most expedient underlying physical server. A VIM is a commercial product that can be used to manage a range of virtual IT resources across multiple physical servers. For example, a VIM can create and manage multiple instances of a hypervisor across different physical servers or allocate a virtual server on one physical server to another (or to a resource pool). Resource management system functions can be accessed by cloud resource administrators employed by the cloud provider or cloud consumer. Those working on behalf of a cloud provider will often be able to directly access the resource management system’s native console. SLA Management System The SLA management system mechanism represents a range of commercially available cloud management products that provide
  • 15.
    features pertaining tothe administration, collection, storage, reporting, and runtime notification of SLA data An SLA management system deployment will generally include a repository used to store and retrieve collected SLA data based on pre-defined metrics and reporting parameters. It will further rely on one or more SLA monitor mechanisms to collect the SLA data that can then be made available in near-real time to usage and administration portals to provide on-going feedback regarding active cloud services A cloud service consumer interacts with a cloud service (1). An SLA monitor intercepts the exchanged messages, evaluates the interaction, and collects relevant runtime data in relation to quality-of-service guarantees defined in the cloud service’s SLA (2A). The data collected is stored in a repository (2B) that is part of the SLA management system (3). Queries can be issued and reports can be generated for an external cloud resource administrator via a usage and administration portal (4) or for an internal cloud resource administrator via the SLA management system’s native user-interface (5). BILLING MANAGEMENT SYSTEM The billing management system mechanism is dedicated to the collection and processing of usage data as it pertains to cloud provider accounting and cloud consumer billing. Specifically, the billing management system relies on pay-per-use monitors to gather runtime usage data that is stored in a repository that the system components then draw from for billing, reporting, and invoicing purposes
  • 16.
    A cloud serviceconsumer exchanges messages with a cloud service (1). A pay-per-use monitor keeps track of the usage and collects data relevant to billing (2A), which is forwarded to a repository that is part of the billing management system (2B). The system periodically calculates the consolidated cloud service usage fees and generates an invoice for the cloud consumer (3). The invoice may be provided to the cloud consumer through the usage and administration portal (4). A Business Case for Google Apps for Education Problem Statement Goldfarb School of Nursing (GSON)’s lack of technology enhancement is a weakness. This weakness causes problems with: accreditation organizations, students’ satisfaction, aspiring nurse preparation, budget management, student retention, and student recruitment. Analysis of Situation BJC’s GroupWise email and messenger limit communication and collaboration among GSON stakeholders. GroupWise Messenger is not accessible outside the organization firewall, nor are students able to connect to the organization’s email system using a mobile device without incurring a cost. Because instant communication is lost and external communication is limited, students may be dissatisfied. Student dissatisfaction may have an effect on student retention, student recruitment, and the reputation of the organization. Moreover, the technology enhancements could allow better user experiences, like students learning in the way they want to learn, with technology. Beyond email and messenger, other innovative communication mediums exist. Documents can be shared and collaborated on
  • 17.
    in real timeand videos can be shared, as with YouTube. These same approaches can be used in an educational environment to enhance operational efficiency as well as teaching and learning. Document sharing would allow students to collaborate with their peers and professors on projects or homework assignments. Video sharing can be used for nurse preparation, student orientation, or to share information related to drug or alcohol abuse, which is a compliance requirement for Title IX. Because GSON is limited by the lack of technology enhancements, third party solutions have been considered for procurement. For example, Mediacore, a video sharing product, was reviewed. The purpose of the product would be to share videos among different stakeholders throughout the College. Various departments would have the ability to share videos. While this is a great tool, as you will see in the cost benefit analysis section of this document, sound fiscal management would be remiss. The Higher Learning Commission (HLC), an accrediting body of the College, requires a plan for innovation and technology. 1. Criterion/standard 5.C.5 states: Institutional planning anticipates emerging factors, such as technology, demographic shifts, and globalization. 2. Criterion/standard 3.D.4. states: The institution provides to students and instructors the infrastructure and resources necessary to support effective teaching and learning (technological infrastructure, scientific laboratories, libraries, performance spaces, clinical practice sites, museum collections, as appropriate to the institution’s offerings). To address the problems presented in this business case, Google Apps for Education is recommended. Solution
  • 18.
    The solution tothe problems presented in this business case is to implement Google Apps for Education (GAE). GAE is chosen because it addresses the main problem and sub-problems initially presented in this business case. Student mobile access - The issue of mobile access for students will be addressed because this platform allows for access at no cost to students. This solution also mitigates BJC’s risk because stakeholders’ email will not be going through the main email system. Increases stakeholders’ use and return on investment (ROI) - The benefit is twofold. We hope to capitalize on stakeholders’ prior knowledge and use of Google Apps that way we increase our return on investment. The ROI would be faster because time to full implementation would be less. Purchase of third party platforms -Google Apps for Education provides similar solutions to those we are seeking from third party vendors. This allows us (Administration) to be good stewards of our budget. Mission of College/Teaching and Learning - Teaching and learning / nurse preparation is why we exist. Today’s students are tech savvy and want to learn that way. To that end, this solution addresses this problem because it provides a platform for 21st century teaching and learning to take place. In addition, because of our ability to better prepare aspiring
  • 19.
    nurses, there maybe a positive impact on the College’s reputation that would help sustain and increase our market share and create a competitive advantage. Accreditation – This problem is addressed by GAE creating an environment that provides students and instructors the infrastructure and resources necessary to support effective teaching and learning. Table 1 is a snapshot of how Google Apps for Education addresses the problems presented in this business case by app. Table 1 Current Structure vs. Google Apps for Education with benefits Applications Current Structure Google Apps for Education Benefits Email X X Adds familiar platform stakeholders know – increase use / ROI Email mobile access X – cost for students X
  • 20.
    No cost tostudents Messenger X – not external X Increases communication by adding external access Video Conference – Google Hangout X Eliminates need for third party platform / decrease budget implications Shared Documents anytime /anywhere X Increases collaboration among stakeholders Video Sharing X Eliminates need for third party platform / decrease budget implications Calendar X X Increases use among stakeholders because users have prior knowledge of the system Appointments
  • 21.
    X Eliminates need forthird party platform / decrease budget implications Implementation To implement this solution change would have to take place from structural, human resource, political, and symbolic perspectives. Structural To implement this project the following platforms or utilities will be needed: Google Apps for Education (GAE) - is the platform that allows us access to the different apps that address the problems presented in this case. Google Active Directory (GADS) – is a utility provided by Google that allows user accounts to be created using automation. At a given time, the GADS tool will execute by looking inside of the designated OU in Active Directory. Then, any changes will be synced with GAE. This process is encrypted. Google Apps Password Sync (GAPS) – is a utility provided by Google that automatically keeps your users’ Google Apps
  • 22.
    passwords in syncwith their Active Directory passwords. Whenever a user's Active Directory password is changed, GAPS pushes the change to Google Apps immediately Active Directory (AD) – AD is used throughout the organization for access control. Our students complete clinical experiences throughout the BJC system; therefore, they still need network access. For Google Apps for Education, we would need a student’s “mail” attribute to end in barnesjewishcollege.edu. Domain Name Services – In the domain control panel for barnesjewishcollege.edu, the MX record would need to be changed to point to Google’s mail servers. These mail servers are provided once we are approved by Google. We would also need the CNAME setup that points to webmail.barnesjewishcollege.edu. Website – The website is used to verify the barnesjewishcollege.edu domain. Additional Deployment Information: https://docs.google.com/document/d/1ixVHcT85nhaU8yYUzi4S EaEMocqkRSSC_Y5GpUtUCVI/edit Human Resources At this point, no new employees are needed; however, technical and non-technical stakeholders will be affected by this change. The technical stakeholders are: 1. BJC IS Security – We will need them to make sure that the risk to BJC infrastructure will not be compromised.
  • 23.
    2. BJC ISEmail Server Group – We will need this group to make sure our approach to adding GAE as an email platform will not interfere with GroupWise. 3. BJC IS Domain Name Services Group – We will need this group to make the domain changes to the barnesjewishcollege.edu domain. 4. BJC IS Help Desk Group – This group will need to understand how to help a student calling for support due to migrating over to GAE. 5. GSON – Angela Trower – She has access to make changes to the College’s website. 6. GSON – Information Systems – Information Systems will need to understand the technology implications as they relates to GAE. 7. GSON - Instructional Technology – Instructional Technology would be responsible for communicating the change and developing a student and faculty training program. 8. GSON - Administrators, Faculty, Staff, and Students Political The two key political areas that need to be addressed are: 1. BJC IS approval to implement the proposed solution. 2. GSON stakeholders’ attitude toward change. To address issue one, this business case has been submitted, and we are having monthly meetings with BJC IS to work through the details and build relationships. Issue two will be addressed
  • 24.
    by developing acommunication and training plan that addresses GSON stakeholders’ concerns. Symbolic Part of the communication plan created by the Instructional Technology department will mentioned how making this change prepares the college for future and allows 21st Century teaching and learning. Change champions would also be identified to help with this transition. Cost benefit analysis (CBA) The cost benefit analysis includes quantitative and qualitative benefits. Quantitative Benefits The cost for not changing our current practice will be a $66,118 initial investment. Every year after until year 5 will cost 49% of the initial investment or $32,728. Year 5, the cost will increase due to the SharePoint server equipment replacement cycle. See tables below. This CBA does not include labor; however Google Apps compared to our given structure (GroupWise) and third party applications is the most appropriate. The fact that GAE is free is not the only reason for this choice. GAE meets our needs. Table 2 Current Structure with Third Party Calculations Applications & Hardware
  • 25.
    Use QTY Year 1 Cost Comments BJCEmail Mobile Mobile Email 800 Students X $10 $8000 1. Recurring cost for new students each year. 2. Paid by students Mediacore Video Share 1 $30,000 Annually BJC-SharePoint Server Document Share 1 $15,000 Every 5 years BJC-SharePoint Cals Document Share 1000 ($11) $11,000
  • 26.
    BJC DropBox Document Share 1 $390 Appointments e-Appointments 1 $1728 Annually TOTAL $66,118 Doesnot include labor Table 3 3 Year Cost Forecast Application Year 1 Cost Year 2 Cost Year 3 Cost Comments Email Mobile
  • 27.
    $8000 $1000 $1000 Recurring cost fornew students each year Mediacore $30,000 $30,000 $30,000 Annually SharePoint Server $15,000 Every 5 years SharePoint Cals $11,000 BJC DropBox $390 Appointments
  • 28.
    $1728 $1728 $1728 Annually TOTAL $66,118 $32,728 $32,728 Annually Qualitative benefits The qualitativebenefits gained from this implementation are satisfied students and increased student learning outcomes. These qualitative benefits also have a positive effect on data required by the accreditation agencies, student recruitment, and GSON’s reputation. Total Cost of Ownership I do not have the labor costs; therefore, I could not determine the TCO. Conclusion - What is the impact of not implementing this new application?
  • 29.
    The price fornot addressing these problems presented in this case study may have an effect on the College: 1. Accreditation; 2. Student experience and satisfaction; 3. Market share and competitive advantage; 4. Over spending; and 5. Antiquated teaching practices. G.1. BUSINESS CASE IDENTIFICATION This section provides information that specifies the details of the business case, such as the following: • Business Case Name • Description – A brief summary of the business case’s purpose and goals. • Sponsor – Identification of business case stakeholders. • List of Revisions (optional) – Revisions by date, author, and approval if control or historical logging is required. G.2. BUSINESS NEEDS The expected benefits and requirements that are to be addressed and fulfilled by cloud adoption are detailed in this part of the template: • Background – A description of relevant historical information that spurred on the motivation for the business case.
  • 30.
    • Business Goals– A list of the tactical and strategic business objectives that are associated with the business case. • Business Requirements – A list of the business requirements that are expected to be fulfilled by the achievement of the business goals. • Performance Objectives – A list of any relevant performance objectives related to the business goals and business requirements. • Priorities – Business goals, business requirements, and performance objectives listed in order of priority. • Affected On-Premise