093049ov1 PDF

Preparing to Deploy Cloud Solutions
• Describe Interaction of Cloud Components and Services

• Describe Interaction of Non-cloud Components and Services
• Evaluate Existing Components and Services for Cloud Deployment
• Evaluate Automation and Orchestration Options
• Prepare for Cloud Deployment
Copyright (c) 2019 CompTIA Properties, LLC. All Rights Reserved. | CompTIA.org 1
Technical Benefits of Cloud Computing
• Resource pooling
• On-demand self service
• Rapid elasticity
• Measured services
• Broad network access
Business Benefits of Cloud Computing
• Move IT expenses from (CapEx) to (OpEx)

• Improves service quality
• Brings new technologies within reach of organizations of all sizes
Common Types of Cloud Services
Cloud Service Providers
The "Big 4" Cloud Service Providers

Provider Description
Amazon Web Services Offers SaaS, PaaS, IaaS, and many other cloud services at global scale.
(AWS)
Microsoft Azure Offers SaaS, PaaS, IaaS, and many other cloud services at global scale.
Google Cloud Platform Offers SaaS, PaaS, IaaS, and many other cloud services at global scale.
(GCP)
IBM Cloud Offers SaaS, PaaS, IaaS, and many other cloud services at global scale.
Cloud Service Providers (Cont.)
Smaller and "Niche" Cloud Service Providers
Provider Description
Heroku A large provider of PaaS services, including app development,
management, deployment, and scaling.
Digital Ocean Another large provider of PaaS services, including app development,
management, deployment, and scaling.
GitHub A large version control repository service used for collaborative app
development.
QuickBooks Online Provides a cloud-based SaaS version of QuickBooks accounting software.
BackBlaze Provides cloud-based data backup and data recovery for personal and
business uses.
ClearData Provides cloud-related services and solutions specific to the highly
regulated healthcare industry.
Core Cloud Solution Components
Component Description
Compute Processor and memory.
Virtual servers and Logically separated compute resources.

machines
Containers Lightweight, standalone executable that holds everything necessary to run a piece
of software.
Storage HDDs or SDDs for saving files and data.
Database SQL or NoSQL databases for storing and retrieving data.
Network and content Bandwidth for accessing cloud services and infrastructure for deploying cloud apps.
delivery
Security, identity, and Authentication, access control, and regulatory assurance for solutions and
compliance processes.
Application services Services for building and deploying cloud apps.
Developer tools Software to create cloud apps.
Additional Cloud Solution Components
Component Description
Analytics Tools for monitoring and measuring cloud solution performance.
Migration Service to help move data and apps to the cloud.
Management tools Tools for managing cloud apps and solutions.
Artificial intelligence Software that can perform analysis and critical decision making normally done by
humans.
Mobile services Tools and components that allow mobile devices to access cloud solutions.
Messaging Services that enable app-to-app communications.
Business productivity Software for common business tasks.
Desktop and streaming Solutions that allow users to work from a virtual computer “desktop.”
Software development Online stores and other tools to publish and monetize software.
and publishing
Internet of Things Cloud-connected devices that can communicate.
Common Cloud Deployments
Public Cloud Private Cloud
Cloud Service Provider Corporate Cloud Data

Cloud Data Center Center
Multiple, different cloud Corporate offices

clients connected to private cloud
Common Cloud Deployments (Cont.)
Hybrid Cloud
Cloud Service Provider One or more locations with

Cloud Data Center corporate data centers.
Community Cloud
Cloud Service Provider

Cloud Data Center
Multiple cloud clients with

similar needs
SLAs
Cloud Component Interaction
Database
Network
VMs running
on Host
CPU on
App running Host
on VMs
Host Host
Guidelines for Describing Cloud Component Interaction
• When justifying your cloud project to management and key stakeholders, remember
to map cloud benefits to organizational goals, increased organizational capabilities,
and costs savings.
• Research common cloud architectures used by other organizations that have
deployed cloud projects similar to those your organization is considering. Review the
pros and cons of each architecture to help decide which is best for you.
• Consider calling cloud administrators who have implemented cloud projects similar
to those you're considering, to see if they are happy with their architectural decisions
or if they would make changes or additions based on their experience.
• When planning a cloud project or moving into a cloud deployment, map out all cloud
components and how they will interact. Documenting this will help you identify
possible problem areas, and troubleshoot issues that might arise and may illuminate
the need for additional services or configuration.
• When considering cloud services, compare MSAs and SLAs from multiple vendors.
Activity: Describing Networking Component Interactions
• Rudison Technologies sells and supports human resources software to help keep
track of employee performance.
• The company is growing, and expanding into new regions. They’ve decided that they
should consider the cloud as an integral part of their growth strategy.
• They need more and more storage for the performance data they keep for clients’
employees in the five regions they serve.
• They also recently had a data loss event and the recovery didn’t go well, so having
data highly available, safe, and easily recoverable is a priority.
• As they have grown, and their workforce has started working remotely and from
different locations, authentication and providing access to resources from anywhere
has become increasingly challenging to maintain.
Activity: Describing Networking Component Interactions
(Cont.)
• Rudison would like to move Identity Access and Management services to the cloud to
allow easy authentication access management from anywhere.
• They have a new app that will provide robust analysis services of employee
performance data.
• They have built the app and deployed it on internal servers in a proof of concept
project.
• They would now like to pilot the app in the cloud.
• Leadership would like a way to easily deploy and test mobile app variants during the
pilot phase.
• The executive steering committee wants you to describe how components will
interact for the storage solution and the app deployment.
Activity: Reviewing SLAs
• The Executive Steering Committee now wants you to compare the SLAs of both
Microsoft Azure and Google Cloud to see:
• What service guarantees each has.
• If there are any concerns about using either provider.
• If either provider has a compelling reason to be selected.
Non-cloud Network Resources
Cloud
Network
Communications
Non-cloud Security Apparatus
Cloud
Network
Encryption Communications
On-premises Computing Services
Cloud
Database
Network
App running
on Server
File Server
Authentication
Authentication
Identity Management
Cloud
Database
Network
App running
on Server
File Server
Other Non-cloud Services
Authentication
Identity Management
Cloud
Database
Network
Monitoring
software,
Logging
software, etc.
App running
on Server
File Server
User Interaction Components
User Interaction Authentication

Components Identity Management
Cloud
Database
Network
Monitoring
software,
Logging
software, etc.
App running
on Server
File Server
Activity: Describing Non-cloud Component
Integration with Cloud Services
• The decision has been made to pilot the three services Rudison has been considering
for the cloud: storage, the new app deployment, and identity and access
management.
• You've been asked to answer questions from the Executive Steering Committee on
how the new app will interact with non-cloud and cloud components.
• The new app will have a front end, a database that currently is on-premises and uses
Active Directory credentials, and will require access to cloud-based services through
the API.
• Usage of the app will be logged to Google Analytics and other software that is on-
premises for when transactions are made.
Systems and Platforms
• When looking at which systems may be a good fit to move to the cloud, evaluate
both the operating system and the platform the operating system is running on.
• Specially built legacy systems may offer features or capabilities that aren't available
on cloud-based systems.
• The systems you wish to move to the cloud have to work with the systems and
architectures offered by your provider of choice.
Applications
When evaluating applications, look for these issues that may indicate the apps are not a
good choice for the cloud:
• Applications that require direct access to hardware.
• Applications that use or require hard-coded IP addresses.
• Latency sensitive apps.
• Apps that transfer very large files.
• Apps that use outdated APIs or APIs that are not supported by the CSP.
Cloud Elements and Target Objects
Cloud
Services
Other Components and Services
Verify that these other components and services are available when the deployment is
scheduled to occur:
• Authentication.
• Security.
• Compliance.
• Monitoring.
• Logging.
• Reporting.
• Integration.
Guidelines for Selecting Systems and
Applications for Cloud Deployment
• Look for systems, platforms, and apps that are x86-64-bit chipset architecture
compatible, as most providers offer compute resources for that architecture.
• Whenever you're considering moving a system or application to the cloud, have a
fallback plan in case cloud deployment fails.
• When evaluating which applications to deploy to the cloud, examine the business
goals that are driving consideration of the application.
• While your evaluation of systems, platforms, and apps for cloud deployment should
tell you the cloud services you must purchase, some providers can break out services
in unexpected ways.
• When preparing for a cloud deployment, it's often a good idea to review the full list
of cloud services available from the CSP and note any that you think may be required
to make your project successful.
Activity: Selecting Systems and
Applications for Migration to the Cloud
• One of the members of the Executive Steering committee has come to you asking
about an in-house application the Finance department uses extensively.
• He wants to know if this app is a good fit to move to the cloud.
• The application was developed 16 years ago using a now out-of-date language, and
runs on a legacy operating system.
• The developer who wrote the application is no longer with the company.
• The application provides a key service for the finance department and the app data is
stored within the application, not a database.
APIs
Administer, Manage, and

Monitor Cloud Services
Automation vs. Orchestration
Automation Orchestration
Deploy New VM
Deploy New VM
2
Install Application on VM
Install Application on VM Add VM to Web Farm
Cloud Automation Options
Automation Option Description

Command Line Provides administration from the command line where specific commands and their
Interface (CLI) parameters can be executed to perform administrative tasks from provisioning to
Commands configuration, and monitoring.
Web and graphical Provide a graphical interface that is often easier to use for manual administration
user interface (GUI) and configuration tasks.
tools
Cloud portal tools Many CSPs provide one or more portals, which are central management and
configuration tools.
Third-party tools Third-party solutions that integrate with cloud services to provide features,
capabilities, or an enhanced management experience. May also provide GUI or
command-line management tools.
Orchestration Techniques
The common uses for cloud orchestration are:

• Resource orchestration to provision and allocate resources to cloud environments or
solutions.
• Workload orchestration for management of apps and other cloud workloads and the
components essential to those workloads.
• Service orchestration to deploy services in cloud environments.
Orchestration for DevOps (Infrastructure as Code)
Development QA
DevOps
Operations
Custom Programming Options
Customer Code using

CSP APIs or CMP APIs
Third-Party Tools for Orchestration
Guidelines for Evaluating Automation and Orchestration
• It's best to create simple and standardized automation routines.

• When evaluating automation and orchestration options for cloud service vendors,
look for vendors that support tools and vendors that support languages and scripting
architectures your system operations staff is familiar with.
• Commit to a DevOps implementation to realize the full advantage of cloud
computing.
• Closely document security processes and process steps related to automation and
orchestration and put procedures in place to update automated and orchestrated
processes when security processes change.
• Refine processes before considering them for automation.
Activity: Evaluating Automation Processes
• The Executive Steering committee has asked you to evaluate automation in Azure
and some third-party tools.
• You will research three different options and explore which might be a good fit.
Cloud Deployment Plans
Item to be
Description
Addressed
Business goals and This should state both the six-twelve month, and the one-three year vision and goals
milestones for the project.
Key stakeholders and This includes executive sponsors and parties with a vested financial interest in the
personnel success of the project, which are critical in pre-deployment stages to state project
value.
Cloud deployment This may start at a very high level and drill down into specific steps, including
workflow specific commands to be executed.
Dependencies Dependencies are the relationships for preceding steps to succeeding tasks.
Risks and problems Risks can derail a project and many are based on dependencies.
Resources Identify all resources needed for the project.
Communications Make sure everyone on the team knows the plan.
Performance Measurement and Baselines
Cloud Structure Requirements
The cloud structure should be based on:

• Network requirements such as bandwidth, load balancing, high-availability, regional
access, and other requirements.
• Security and compliance requirements such as the need for encrypted connections
between clients, apps, and data sources, authentication and access controls, and
other security mechanisms.
• App architecture such as two-tier, where clients (client tier) access the data directly
(database tier), or three-tier, where an app running business logic sits between the
client and the data to perform additional processing (client tier, business tier, and
data tier).
Target Hosts and Commands
• You must identify target hosts provided by the CSP where guest VMs or containers
will be installed.
• The VMs and containers will have configuration specifications defining resource
requirements such as compute, memory, storage, and so forth.
• You should be able to identify the requirements for the CSP resource systems or
systems that will host the VMs and containers.
• Document any task steps or commands needed to provision hosts, VMs, containers,
or other CSP resources
Migration Tools
Benefits of DevOps Approach
A DevOps approach has many benefits, including:

• Fast implementation times, which can mean faster time to market and reduced ROI.
• More stable and reliable operations environments.
• Early detection and more rapid correction of issues (code or infrastructure).
• Improved collaboration between business, development, and operations, thus
improving business agility.
• Continuous release, deployment, testing, and monitoring of apps, thus facilitating
faster implementation and business agility.
Guidelines for Preparing for a Cloud Deployment
• Consider using an agile methodology in your project execution plan.

• For shorter deployments of one to four weeks in length, use a more rigid and less
flexible project execution plan.
• For longer running deployments, those taking longer than four weeks, make the plan
flexible.
• Take baseline measurements of key performance metrics, both front-end and back-
end, to use for comparison purposes once solutions are deployed to the cloud.
• If a problem materializes, be sure to assess the real impact of the problem on project
milestones and goals.
• When taking baseline measurements, work with end-users and service or app
experts to determine common task key back-end actions that should be measured to
determine the baseline for a service or app.
• Document CSP task steps, including GUI and command-line steps, thoroughly, and
cross-train cloud team members so that multiple people are able to provision and
configure CSP resources.
• Refer to CSP checklists and best practice guides when provisioning resources.
• Evaluate the benefits of a DevOps approach to cloud deployment and management.
Activity: Preparing for Cloud Deployment
• The Executive Steering Committee wants an estimate as to how much it will cost to
move some of the infrastructure to the cloud.
• You will need to research the options for moving to each cloud.
• You will also perform a migration assessment using the Microsoft Azure Total Cost of
Ownership (TCO) Calculator to help you estimate the cost of using cloud services.
Reflective Questions
1. Have you participated in deploying apps or services to the cloud already, or

are you in the process of evaluating the cloud for potential deployment?
2. What business or technical benefits could your organization see from

moving some apps or services to the cloud? Be as specific as possible.

093049ov1 PDF

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

093049ov1 PDF

Загружено:

Авторское право:

Доступные форматы

Preparing to Deploy Cloud Solutions

• Describe Interaction of Cloud Components and Services

• Move IT expenses from (CapEx) to (OpEx)

The "Big 4" Cloud Service Providers

Smaller and "Niche" Cloud Service Providers

Virtual servers and Logically separated compute resources.

Database SQL or NoSQL databases for storing and retrieving data.

Developer tools Software to create cloud apps.

Migration Service to help move data and apps to the cloud.

Management tools Tools for managing cloud apps and solutions.

Messaging Services that enable app-to-app communications.

Business productivity Software for common business tasks.

Public Cloud Private Cloud

Cloud Service Provider Corporate Cloud Data

Multiple, different cloud Corporate offices

Cloud Service Provider One or more locations with

Cloud Service Provider

Multiple cloud clients with

User Interaction Authentication

Administer, Manage, and

Install Application on VM Add VM to Web Farm

Automation Option Description

The common uses for cloud orchestration are:

Customer Code using

• It's best to create simple and standardized automation routines.

Resources Identify all resources needed for the project.

Communications Make sure everyone on the team knows the plan.

The cloud structure should be based on:

A DevOps approach has many benefits, including:

• Consider using an agile methodology in your project execution plan.

1. Have you participated in deploying apps or services to the cloud already, or

2. What business or technical benefits could your organization see from

Вам также может понравиться