Module 2 App Assessment & Migration Planning Flashcards
(331 cards)
1
Q
First layer of the cloud stack
A
Applications
2
Q
Drive the decisions made throughout the rest of the stack in the VDC
A
Applications
3
Q
Has the most to gain from a well designed VDC
A
Application layer
4
Q
How can application deployment and management be simplified?
A
By using techniques and technologies available in other layers.
5
Q
How application uptime can be enhanced
A
By using features available in the hypervisor
6
Q
First step in application assessment
A
To understand the applications in the environment, their value to the organization, and their requirements.
7
Q
Examples of application requirements
A
Data security, accessibility, latency, etc.
8
Q
Four modern application delivery challenges
A
- Little attention to performance during development
- Security vulnerabilities
- Distributed employees
- Distributed applications & associated complexity
9
Q
Five new application delivery challenges
A
- Movement away from monolithic architectures
- Web 2.0 & rich content application requirements
- SLAs
- Legacy apps and application silos
- Consumerization of IT
10
Q
Three virtualization technology opportunities
A
- Increase flexibility
- Reduce cost
- Tighten security
11
Q
True or False:
Generally, the role of application performance & robustness has been pushed down the stack to the compute, network, and storage layers.
A
True
12
Q
How can employees be distributed?
A
Across organization facilities, small field offices, home offices, or at customer sites using mobile devices.
13
Q
How can applications be distributed?
A
With multiple presentation layers, residing on separate machines and locations from the business logic layers and data access layers.
14
Q
Two examples of Web 2.0 systems
A
15
Q
How can IT eliminate traditional costs and become leaner?
A
Through consolidation and standardization
16
Q
Makes a customer dependent on a vendor for hardware or software, creating a situation where they are unable to use another system without incurring substantial costs or data loss.
A
Vendor Lock-in
17
Q
Five items to evaluate to determine if vendor lock-in exists
A
- Proprietary hardware, software, APIs, file formats
- Software limited to certain hardware platforms or configurations
- Abandonware
- Availability of source code, documentation, skillsets
- Licensing
18
Q
Three legal issues pertaining to vendor lock-in
A
- Government laws
- Commercial licenses
- Open Source licenses
19
Q
True or False: Vendor lock-in is limited to large hardware / software / systems companies.
A
False.
20
Q
Three vendor lock-in scenarios for software
A
- Where software only runs on specific hardware.
- Where software uses unpublished APIs.
- Where software uses undocumented file formats.
21
Q
True or False: Systems developed in-house can lead to vendor lock-in scenarios.
A
True
22
Q
Category of software in which the product is not being maintained due to the vendor stopping work, going out of business, the in-house developer leaving the company, etc.
A
Abandonware
23
Q
True or False:
Hardware can also fall into the category of abandonware.
A
True
24
Q
Makes it much easier and less costly to work with vendor lock-in situations
A
Availability of source code
25
Contributing to the availability of software
Rise in popularity of the Open Source Software (OSS) movement
26
Included in many Open Source Software licenses
Responsibility to submit any changes made in the code back to the OSS community.
27
Three areas of savings
1. Reduced power, cooling, data center space.
2. Better management of licensing costs (be careful of VM sprawl).
3. OPEX
28
VDC Migration Planning Process
1. Survey the environment.
2. Identify systems that can be combined, commoditized, replaced, or obsoleted.
3. Plan goals, using a phased approach.
29
Question that must be asked when converting to a VDC
How much does it cost to save money?
In other words, what is the up-front CAPEX that will be required to eventually save money?
30
How should migrating to a VDC be done?
Perform the migration in phases, migrating a few applications and systems at a time.
31
Five considerations in VDC migration planning
1. Determine phases of migration.
2. Migrate a few applications and systems at a time.
3. Look for overlap and underutilization of resources.
4. Ask if some systems might be combined or replaced.
5. Identify servers to eliminate or reuse.
32
Technique that can take advantage of the dynamic nature of the VDC
Combine systems when demand is not high, then scale out as demand increases (since many IT purchases are done in order to handle maximum load).
33
Five migration plan goals
1. Use a phased approach
2. Free up hardware and repurpose systems
3. Consolidate the network
4. Reduce licensing and maintenance costs
5. TIme migrations when capacity demand is low
34
Tricky part of converting the data center into a private cloud
Migrating the legacy, business critical application(s).
35
Three details associated with Traditional Data Center to VDC phase
Identify applications.
Is decoupling possible?
Rewrite apps?
36
Detail needed for VDC phase
Application variability and latency
37
Details associated with VDC to Cloud
Migrating applications to Cloud.
Multi-tenancy.
High availability and eventual consistency (elasticity).
Bursting
38
True or False:
| Many large data centers have the infrastructure to become a Cloud.
True
39
Becomes even more of a deterrent when an organization is looking to outsource their IT to the Cloud
Migrating the legacy, business critical applications
40
Three options to consider for application migrations
1. Does the cost and effort of application rework, testing and redeployment outweigh the cost of maintaining the legacy app in-house?
2. Can the app run in the Cloud infrastructure?
3. Once migrated to the Cloud, consider vendor lock-in in case the app needs to move from the Cloud.
41
Dependencies for successful deployment of Clouds within organizations
1. Can the application be decoupled from the physical server (i.e., can the app be virtualized)?
2. Can the physical resource meet the demands of the application.
3. The application may be legacy and only operate on legacy hardware that is incompatible with the Cloud resources.
42
Most challenging element for moving the VDC to the Cloud
Applications
43
Advantage of moving toward the private Cloud
There may be little-to-no redesign efforts required for applications.
44
Six general application types
1. Legacy
2. Enterprise
3. Big Data
4. Web Scale and Horizontal
5. Mobile
6. Desktop Virtualization
45
Dated application that continues to serve a business need.
| Typically resides on older, slower servers.
Legacy application
46
Application type that:
- Solves and enterprise-wide problem.
- Software typically used for: order processing, procurement, production scheduling, customer information management, and accounting.
Enterprise Application
47
Application type that:
- Processes large quantities of data.
- Technologies include: Massively Parallel Processing (MPP) databases, data mining infrastructures (e.g., Apache Hadoop Framework), distributed file systems, distributed DBs, MapReduce algorithms, cloud computing platforms, Internet, & archival storage systems.
Big Data Applications
48
Application type that:
- Software uses over a broad group of users.
- Examples: word processing, bookkeeping software, social network
Web Scale and Horizontal Applications
49
Application type that:
- Usually runs on alternative end points such as phones and tablets.
- Uses web technologies: HTML, XML, etc.
Mobile Applications
50
Application type that:
- Adds a virtualization layer between the server and the desktop.
- Provides greater accessibility, tighter security, and ease of management.
Desktop Virtualization Application (VDI)
51
Six classifications or categories of applications
```
Legacy apps
Enterprise apps
Big Data apps
Web Scale and Horizontal apps
Mobile apps
Desktop Virtualization apps
```
52
Applications that typically do not adapt well to a VDC and can take significant work to migrate.
Legacy Applications
53
What can offset the cost of maintaining legacy apps?
Removing the legacy apps from obsolete hardware.
54
Disadvantages of Integrating Legacy Apps in the VDC Plan
- Hard to migrate & integrate into the VDC and Cloud.
- Typically built on non-x86 platforms.
- Tightly coupled w/ underlying platform & technologies.
- Application re-work is manual and time intensive.
55
Advantages of Integrating Legacy Apps in the VDC Plan
- Remove silos of infrastructure dedicated to a single application.
- Move to a modern platform - improve performance & longevity.
- Reduce IT resources needed to manage and maintain legacy apps.
56
Integration of legacy apps in the VDC plan can be both...
- a source of tremendous gains in a move to VDC.
| - a source of great expense in the process.
57
Three Legacy Application Migration Challenges
1. Incompatible dependencies
2. Interaction among shared resources - unanticipated problems
3. Cross-platform effort
58
Examples of incompatible dependencies when migrating legacy applications
Libraries
Middleware
Kernel modules
Drivers
59
Two questions to consider concerning application migrations
1. Does the cost & effort of application rework, testing, and redeployment outweigh the cost of maintaining the legacy app in-house?
2. Can the application run in the VDC or Cloud infrastructure?
60
True or False: Considering industry trends, data for legacy applications has little, if any, growth.
True.
Implication: It may not warrant the level of effort & cost a migration may impose.
2.11
61
5 Enterprise Application Business Characteristics
1. Mission-critical (downtime measured in $)
2. Typically enterprise wide (impacts all users)
3. Dedicated resources to manage & maintain
4. Distributed - may span VDCs
5. Stringent SLAs & recovery objectives
62
5 Enterprise Application Technical Characteristics
1. Clustered
2. Multi-processor
3. High memory usage
4. High bandwidth requirement
5. Large storage footprint
63
True or False: Traditional horizontal applications, such as email, are increasingly considered mission critical among organizations.
True
64
EAI
Enterprise Application Integration (EAI)
65
Established the sharing of functionality and data between separate islands.
Enterprise Application Integration (EAI)
66
3 Approaches to EAI
1. EAI Via Mesh
2. Enterprise Service Bus (ESB)
3. Service-Oriented Architecture (SOA)
67
SOA
Service-Oriented Architecture
68
ESB
Enterprise Service Bus (ESB)
69
Middleware layer that acts as an intermediary between separate systems
Enterprise Service Bus (ESB)
70
Architecture where systems are designed as reusable modules that can be called when and where needed.
Service Oriented Architecture (SOA)
71
Links disparate apps within an org to simplify & automate business processes to the greatest extent possible, while at the same time avoiding the need to make changes to existing apps or data structures.
Enterprise Application Integration (EAI)
72
Links disparate apps within an org to simplify & automate business processes to the greatest extent possible.
Enterprise Application Integration (EAI)
73
Avoids the need to make changes to existing apps or data structures.
Enterprise Application Integration (EAI)
74
Challenges to Accomplishing Enterprise Application Integration (EAI)
1. Systems developed in different programming languages.
2. Data may live in different database formats.
3. Systems may run on different operating systems.
75
Can lead to a complex mesh of connections & interfaces as each system establishes communications with the others in the enterprise.
Enterprise Application Integration (EAI) via Mesh
76
Framework (or software architecture) that forms a middleware layer, enabling integration of systems and applications across the enterprise.
Enterprise Service Bus (ESB)
77
Addresses the problem of inter-systems communication & allows sharing of data & business processes across connected apps or data sources.
Enterprise Application Integration (EAI) via Enterprise Service Bus (ESB)
78
Method used for implementing EAI
Enterprise Service Bus (ESB)
79
Acts as the mediator for the interaction and communication between software applications.
An Enterprise Service Bus (ESB)
80
Set of software development principles for designing and developing software as services.
Service-Oriented Architecture (SOA)
81
Well-defined business functions that are built as individual pieces of code with interface "hooks" or APIs.
Services within a Service-Oriented Architecture (SOA) environment
82
4 "V"s of Big Data
1. Variety
2. Velocity
3. Volume
4. Value
83
3 Characteristics of Big Data
1. Data volume
2. Processing complexity
3. Multiple combinations of structured & unstructured sources
84
Meaning of 'Variety' in a Big Data context
Data is not in a single format; email, tweets, images, standard relational DBs, text files, audio/video files
85
Meaning of 'Velocity' in a Big Data context
Data is generated or changed very quickly
86
Meaning of 'Volume' in a Big Data context
Huge quantities of data
87
Meaning of 'Value' in a Big Data context
Big Data is used to solve specific problems or to answer a specific question
88
True or False: Big Data is solely characterized by large data sets / sizes.
False
Big Data also focuses on processing complexity as well as combinations of structured & unstructured data sources.
89
Four challenges of Big Data applications
1. Can lead to app sprawl or VM density issues that can bottleneck VDC compute resources.
2. BC/DR, retention, & security become unmanageable.
3. Increased data load rates can bottleneck the VDCs network.
4. Typically computing that requires high-speed networks - 10GbE
90
Components for Handling Big Data
1. Inexpensive, reliable storage.
2. Analysis tools for unstructured & structured data.
3. Hadoop and MapReduce suited to support distributed computing on large data sets.
91
Typical percentage of historical data in most production systems
60%
| some organizations see upwards of 95%
92
True or False: Applications that load large data sets and run analytics typically require 10Gig Ethernet.
True
93
Why can using business intelligence applications on VMs be attractive?
Allows for greater utilization
94
Typical example of how business intelligence applications are run in a virtual environment.
1. Business intelligence app run analytics periodically (e.g., to generate a monthly report).
2. VMs can be started, the data analyzed, and a report generated.
3. Then the VMs can be shutdown and the resources released.
95
True or False: What constitutes a "large" data set is relative and can vary from one organization to another.
True
A large data set for one org may be 100s of gigabytes.
For another org, it may be hundreds of terabytes.
96
Definition of a "large" data set
A large data set can be defined as the point at which the organization has difficulty managing the data set.
97
Applications that:
- scale at an exponential rate;
- example: social networks;
- can handle rapid growth without bottlenecks;
- commonly NoSQL databases
Web Scale Applications
98
Type of application that is deployed and managed across a large user base
Horizontal Application
99
Examples of horizontal applications
Desktop applications
Email
100
Applications that will impact many users simultaneously
Horizontal applications
101
Example of a horizontal application impacting many users simultaneously
An anti-virus update being pushed to all user desktops and images within the organization
102
Enable BYOD and, to some extent, desktop virtualization
Mobile apps
103
Application type that performs a specific task
Mobile Applications
104
Two basic types of mobile apps
1. Native apps installed on the end point.
| 2. Web apps
105
In a Mobile application context, web apps are sometimes disguised as what?
Native apps
106
Applications often architected as traditional 3-tier applications
Mobile Applications
107
Generally written for a specific device or a target end point operating system
Native applications
108
Reside on a server and are accessed via the Internet or cell phone network
Web apps
109
Characteristics of web app software
1. Written using HTML and supporting technologies (e.g., XML & CSS).
2. Interactive parts are written in Java, Objective-C, or other language as the end point platform dictates.
110
Traditional 3-tier application architecture
1. Presentation layer (the end point)
2. Business logic layer (middleware)
3. Data access layer (data store or DB of some kind)
111
6 Benefits of Desktop Virtualization
1. Ease of management & security
2. VDI image library
3. Heterogeneous OSs
4. Snapshots
5. Green
6. Persistent and non-persistent desktops
112
Two types of virtual desktop solutions
1. Server Hosted
| 2. Client Hosted
113
Examples of Server Hosted virtual desktop solutions
1. VDI - stateful and stateless desktops
| 2. Remote Desktop Services (RDS)
114
Example of Client Hosted virtual desktop solution
Desktop running as a VM on client system: full virtualization and paravirtualization
115
Not the typical VDC deployment
Client Hosted Desktop Virtualization Solutions
116
Abstracts the OS, applications, and associated data from the PC.
Desktop virtualization
117
Most common desktop virtualization solution
Server hosted implementations (particularly VDI)
118
Desktop virtualization solution where the end users instantiate a session on a remote host machine
Server hosted implementation
119
Require a virtualization platform be installed on the local system.
Client hosted virtual desktops
120
Offers the ability to switch between several desktops - such as between a Linux environment, a Windows XP corporate environment, and a Windows 7 environment.
Client hosted virtual desktop
121
True or False: Both server hosted and client hosted desktop virtualization solutions require software installed on the client.
True
122
True or False: Remote and client virtualization software is available for Windows, Mac, and Linux
True
123
Benefit of Snapshots in a desktop virtualization solution
Ability to recover or rollback a user's desktop.
124
How do desktop virtualization solutions contribute to a greener IT environment?
Thin clients have reduced power needs.
Consolidated computing in data centers can use power more efficiently.
Reusing older end points reduces technology discarded in landfills.
125
Allows flexibility for stateless images to be used temporarily
Desktop state
126
Two examples of how desktop state can be used
1. A client for visitors that can be rolled back each day.
| 2. A stateful image where employee changes to their desktop image is preserved.
127
5 Key Considerations for Application Migration to VDC
1. Flexibility
2. Elasticity
3. Efficiency
4. Multi-tenancy
5. Costs
128
Three things that enable flexibility in application migration to VDC
1. Templates
2. Cloning
3. Snapshots
129
Enables quick scale out of application clusters to address burst and growth
Cloning
130
Reduces implementation and configuration times
Templates
131
Four ffficiency benefits for application migration to VDC
1. Better utilization of CPU, memory & bandwidth
2. VDI
3. Lower upgrade risks - snapshot rollbacks
4. Lower application testing time
132
Two benefits of Multi-Tenancy
1. Failure isolation
| 2. Improved resource utilization
133
Applications which cannot be migrated to VDC
1. Appliance-based applications
2. Applications with specific hardware requirements
3. Application that are not supported by the vendor when running in a virtual environment
4. Applications with data requiring isolation
134
Three examples of appliance applications
1. Storage controllers
2. Network devices
3. Highly specialized software that requires a vendor-supplied hardware platform
135
Examples of application hardware dependencies
CPU architecture
BIOS
Peripherals and drivers
136
Three drivers of data / application isolation
1. Legal or regulatory requirements
2. Political
3. Test / dev / production
137
Why multiple applications' data requirements should be distilled into a few categories or ranges
So standard data pools can be created
138
Goal when virtualizing the data center
Reduce (to zero if possible) the number of "special" cases.
139
Benefit of minimizing the number data classifications
Simplifies management and planning - enabling the benefits of standardization to be realized.
140
5 data classification dimensions
1. Size
2. Response time
3. Availability
4. RTO
5. RPO
141
Examples of RPOs
Zero data loss
< 4 hours loss
< 24 hours loss
142
Examples of RTOs
Immediate
< 4 hours
< 24 hours
143
Example availability requirement for email
99.999%
144
Example availability requirement for Accounts Payable / Accounts Receivable
99.9%
145
Example availability requirement for Expense Management
95%
146
Example compute requirement for email
Multiple 4 x 3 MHz
147
Example compute requirement for Accounts Payable / Accounts Receivable
2 x 3 MHz
148
Example compute requirement for Expense Management
1 x 2 MHz
149
Example storage requirement for Email
> 10 TB
150
Example storage requirement for Account Payable / Accounts Receivable
1GB to 1TB
151
Example storage requirement for Expense Management
< 1 TB
152
Example storage response time requirement for Email
< 1 ms
153
Example storage response time requirement for Accounts Payable / Accounts Receivable
< 10 ms
154
Example storage response time requirement for Expense Management
< 100 ms
155
Example network requirement for Email
Global
156
Example network requirement for Accounts Payable / Accounts Receivable
Intranet
157
Example network requirement for Expense Management
Local
158
Example access requirement for Email
Internal and External
159
Example access requirement for Accounts Payable / Accounts Receivable
Internal
160
Example access requirement for Expense Management
Limited internal
161
Example management requirement for Email
Fully automated
162
Example management requirement for Accounts Payable / Accounts Receivable
Semi-automated
163
Example management requirement for Expense Management
Manual
164
Example RTO/RPO requirements for Email
RTO: Immediate
RPO: Zero
165
Example RTO/RPO requirements for Accounts Payable / Accounts Receivable
RTO: < 4 hours
RPO: 4 hours
166
Example RTO/RPO requirements for Expense Management
RTO: < 24 hours
RPO: 24 hours
167
Example Regulatory / Compliance requirements for Email
High
168
Example Regulatory / Compliance requirements for Accounts Payable / Accounts Receivable
Medium
169
Example Regulatory / Compliance requirements for Expense Management
Low
170
Cost if Lost / Exposed for Email
Very high
171
Cost if Lost / Exposed for Accounts Payable / Accounts Receivable
High
172
Cost if Lost / Exposed for Expense Management
Medium
173
An email application can be compared very closely with what?
A utility.
When email fails, business can be stopped.
174
Six benefits of virtualizing applications
1. Multiple OSs can run on a single server
2. Reduced CAPEX
3. High Availability
4. Enhanced Business Continuity (BC)
5. Improved Disaster Recovery (DR)
6. Centralized Management
175
Two things that allow applications to be moved from one hypervisor server to another as needed to balance load and adjust for changes (failures) in the underlying server hardware or faults in the application servers themselves.
Hypervisor clustering
Application fault tolerance
176
How CAPEX is reduced when applications are virtualized
Increased energy efficiency
Less compute
Less network infrastructure
177
Three things determined by application SLAs
1. Amount of processing & memory needed in the compute space to meet the SLA
2. How much bandwidth is required
3. How much capacity is needed and how the life-cycle of the data is handled.
178
Network resources needed to support SLA
Bandwidth
179
Storage resources and technologies needed to support SLA
Tiering
180
Compute resources needed to support SLA
CPU
Memory
Connectivity
181
What dictates the technologies employed within the VDC infrastructure?
The applications that will use the resources
182
5 Challenges with Virtualized Applications
```
Resource allocation
Application visibility
Storage management
Management complexity
VM sprawl and abandoned machines
```
183
Resource allocation issue with virtualized applications
Shared environments can starve some applications
184
Application visibility issue with virtualized applications
Hypervisors monitor VMs, not the applications running on the VMs.
185
Storage management issue with virtualized applications
Moving from DAS to SAN / NAS
186
Management complexity issue with virtualized applications
Not only manage the application, but the VM and hypervisor as well
187
VM sprawl and abandoned machine issue with virtualized applications
Creating new machines becomes too easy
188
Usual source of first alert of poor application performance
End user
189
True or False: Most hypervisors have some concept of resource pooling that can detect, alert, cap, or proactively move applications that demand excessive resources to avoid starving other tenants.
True
190
Much of the mobility functionality of modern hypervisors (i.e., the ability to move a VM and its applications among multiple hypervisor hosts) is dependent on what.
Shared storage resources
191
Increasing node specifications is an example of what kind of scaling?
Vertical Scaling
192
Increasing node count is an example of what kind of scaling?
Horizontal Scaling
193
Increasing an application's capability to handle more data, more clients, or a broader geographic region
Scaling an application
194
True or False: Another way of upsizing an application is to decrease the application's response time.
True
195
Three ways to improve the architecture
1. Faster networks
2. Appropriate storage protocol
3. Faster physical disks
196
Migrating an applications hosted on a NL SAS-based LUN to an SSD-based LUN should provide a major increase in performance.
True
197
Provides a major opportunity to improve response time
Hard disk architecture
198
Used to solve a specific application problem, or in conjunction with virtual networks, or to address a scaling problem
Virtual Appliances
199
Encapsulates all application attributes inside a VM
Virtual appliance
200
Can be developed in-house, obtained via vendor, or community sites.
Virtual appliances
201
6 Examples of Virtual Appliances
1. Load balancers
2. Routers / firewalls
3. Databases
4. Web servers
5. Platform stacks
6. Desktops
202
A pre-build VM image
A virtual appliance
203
True or False: A virtual appliance is a pre-built VM image.
True
204
Used to quickly deploy standardized applications to solve a particular need.
Virtual appliance
205
Can be used to quickly and easily deploy specific applications encapsulated in their own self-contained Virtual Machine wrapper.
Virtual Appliances
206
Benefit of replacing application server clustering with a hypervisor fault tolerance feature.
Standardization
207
Hypervisor features that can be leveraged to replace application functionality
Fault tolerance and high availability
Snapshot backups
Clone VMs
208
True or False: There are many features available via hypervisors to support fault tolerance, high availability, disaster recovery, VM deployment, etc.
True
209
VDI
Virtual Desktop Infrastructure
210
A set of techniques and technologies that allows remote access to a desktop environment, usually residing in a data center.
Virtualized Desktop Infrastructure (VDI)
211
Benefits of VDI
Anywhere, anytime, multiple device access.
Standardized desktop.
Ease of managing multiple desktops.
Compliance.
Ease of support.
Centralized BC/DR and backup.
Reduced exposure to environmental hazards and theft.
212
Promises flexible access from any device capable of running the client-side software needed to connect to the virtual desktop.
VDI
213
Allows a desktop to reside in the data center and is under IT's control.
VDI
214
Cost savings of VDI
Offers relatively long-term cost savings.
Do not expect immediate cost savings.
215
Important in a VDI design
High Availability
216
Why VDI outages are serious
In VDI, user desktops become a data center application.
An outage can impact many end users.
217
What can cause huge I/O loads in VDI deployments?
Normal or trivial tasks, such as:
- Boot storms
- Virus scans
- Indexing
These and other rather mundane items take on a different personality when running across hundreds or thousands of user desktops at the same time.
218
Occurs when a VDC environment must start up hundreds or thousands of virtual desktop environments at the same time.
Boot Storm
219
Ways to minimize the effect of boot storms
Proper use of storage tiering, broad network access, sufficient compute resources, & hypervisor/VDI features.
220
Benefits of Desktop Virtualization
- Ease of large scale management
- Enables BYOD
- Data protection
- Reduce / eliminate environmental factors
- Standardize platform(s)
- Work anywhere
221
Impacting and transforming organizations' businesses
Consumer-class technologies & services such as mobile applications, Web 2.0 social networks, multimedia, and mobile devices.
222
Create challenges for IT departments and blur the boundaries between business and personal use.
Consumer-class technologies & services such as mobile applications, Web 2.0 social networks, multimedia, and mobile devices
223
Adoption of consumer-grade end user devices, supporting technologies, and the empowerment of choice given to the end user
Consumerization of IT
224
Traditionally known as Terminal Services
Remote Desktop Services (RDS)
225
The traditional Server Based Computing (SBC) technology
Remote Desktop Services (RDS), a.k.a., Terminal Services
226
VDI Benefits
- Recent technology
- Better fault tolerance
- Can deploy thin density
- True user segmentation
227
Primary benefit of RDS
User density - the ability to serve more user desktops per host CPU core
228
Drawback of RDS
Sessions are more dependent upon the stability of the underlying OS, resulting in a potential decrease in stability of the end user platforms.
229
How does VDI result in better fault tolerance?
VDI uses fully segregated VMs which offers additional fault tolerance, such as VM failover and redundancy.
230
Why is software compatibility with VDI generally greater than RDS?
RDS can have issues due to the single OS running underneath the sessions.
231
General comparison of RDS and VDI technologies
While RDS is by far the most mature technology, the decrease in storage and CPU costs is helping to mitigate the costs of VDI, leading to a huge growth in that area.
232
Outpacing the use of PCs
Use of thin clients
233
True or False: Many thin clients are being designed for VDI.
True
234
Manages server-hosted remote desktop to clients
VDI Connection Broker
235
Works in conjunction with authentication / authorization and hypervisor
VDI Connection Broker
236
True or False: a VDI implementation can consist of virtual desktops that clients can access with end-user credentials.
True
237
Preferred VDI implementation
Uses a connection broker to handle assignments of virtual desktops to clients
238
VDI Connection Broker Functions
- Assignment of a desktop from a pool or a dedicated virtual desktop.
- Web interface that can create secure SSL connections to remote desktops.
- Directory Services integration
- Full USB support
- Support for various display protocols
- Integration with Remote Desktop Services (former Terminal Services)
239
Techniques for separation of different types of data
- Home directories and group policies
- Roaming profiles and folder redirection
- VMware user data disks
- AppSense Environment Manager - Profile Management
- RTO TScale - Application Load Management
240
Optional, but reduces storage consumption
Data separation
241
Benefits of data separation
Separating user data reduces storage consumption.
Separating different types of data allows for proper storage policies to be set.
242
Prime reason for converting to VDI
Increased data security
243
In VDI, the only connection from outside the network
From the end users remotely controlling their desktop systems.
244
In VDI, where additional security and authentication is configured
Via the connection broker
245
Require just as much hardening as physical systems
The virtual desktops themselves
246
Does not negate the need for true security software to be installed
The temptation to use VM snapshot reversion to solve all virus and corruption issues
247
Should be part of a segmented end-user network, even though they may be physically hosted in the same rack as production servers, or perhaps on the same hypervisor itself
the VMs hosting the virtual desktops
248
Keeps data and application traffic on the secure corporate network
VDI
249
VDI Security on the Physical Client
Use secure protocols to access virtual desktops
250
VDI Security on the Virtual Desktop
Do not rely on "reversion" for security.
Have same anti-virus, restrictions as physical desktops.
251
VDI Security - Segmentation
Place user desktops in the same domain as physical desktops.
Segment from protected servers.
252
VDI Security - Physical Infrastructure
Standard security considerations
253
VDI is NOT recommended if the organization...
Is averse to complexity.
Does not have a solid infrastructure.
Does not have a budget for it.
254
Consider VDI if the organization...
```
Wants to reuse legacy desktops.
Supports a distributed workforce.
Wants to contain intellectual property.
Wants to standardize.
Has compliance issues.
Has a BYOD environment.
Is willing to relearn desktop management.
```
255
Can be used with or without VDI
Client-Side Application Virtualization
256
Access applications when / where / if needed
Client-Side Application Virtualization
257
Applications are streamed, thinly installed, or presented on the end point machine
Client-Side Application Virtualization
258
Users can access the latest version of the application without installing the entire application on their machine.
Client-Side Application Virtualization
259
Administrators have a single maintenance point.
Client-Side Application Virtualization
260
Applications with different or conflicting requirements can run on one device.
Client-Side Application Virtualization
261
Various products allow a level of deterministic behavior based on the location of the end point, such as inside the organizational network or a trusted remote location.
Client-Side Application Virtualization
262
Apps loaded on the end point as they are used
Application Streaming
263
Ways that applications can be handled in a Client-Side Application Virtualization environment
1. Streamed (loaded on end point as they are used).
2. Installed onto a lightweight VM on the end point.
3. Run remotely accepting keyboard & pointer input while returning video and optional sound.
264
One of the main benefits of application virtualization
Providing a central distribution point
265
Advantages of a central distribution point for applications that are virtualized
1. Users always have access to the latest version.
| 2. Provides administrators a single location to apply patches & monitor usage.
266
True or False: Application virtualization allows different versions of the same application.
True
267
True or False: Application virtualization allows applications that do not directly support the end point to be run either virtually, or via presentation to the end point.
True
268
Has tremendous implications to BYOD environments, or environments that wish to prolong the life of otherwise legacy hardware and software.
Application virtualization allowing applications that do not directly support the end point to be run either virtually, or via presentation to the end point.
269
True or False: Application Virtualization is separate from, and not dependent on, Desktop Virtualization
True
270
True or False: Application Virtualization and Desktop Virtualization complement each other nicely.
True
271
Two Basic Application Virtualization Architectures
1. Presentation Mode
| 2. Thin Install
272
Application Virtualization Architecture where:
1. Application runs on a remote machine.
2. Keystrokes & pointer sent.
3. Video, audio sent back.
Presentation Mode
273
Application Virtualization Architecture where the compute resources runs on a system that is remote from the end user, like in the data center.
Presentation mode
274
Application Virtualization Architecture where:
1. Application runs on the end point.
2. Application packaged to run inside a minimal VM wrapper.
3. Application might be streamed.
Thin Install
275
Application Virtualization Architecture where the software and needed support / config info is downloaded to the end point and executed in a virtual "bubble".
Thin Install
276
Isolates the program and the configuration information from the host OS
Virtual "bubble"
277
In this application virtualization architecture, the end point need only be compatible with the wrapper program that contains the virtual bubble.
Thin Install
278
True or False: In a Thin Install application virtualization architecture, different versions of the same program that are incompatible with each other could potentially run on the same machine at the same time.
True
279
True or False: In a Thin Install application virtualization architecture, software that does not support the end point architecture may be able to run on the end point in the virtual bubble.
True
280
Application and wrapper components are downloaded as needed.
Streaming
281
Only enough of the program needed to run is downloaded to the end point.
Streaming
282
Provides an opportunity to employ storage tiering to place this type of data in a pool that had different characteristics than, say, the storage holding the VDI image itself.
Storage of user and data
283
Requires the use of some kind of software tool that understands the requirements of the virtualized software and can package it for use in the environment.
Thin Install
284
Terms used to refer to the use of some kind of software tool that understands the requirements of the virtualized software and can package it for use in the environment.
Packaging or Sequencing
285
True or False: Thin install and streaming applications require a packager.
True
286
Ideal for horizontal applications
Greater efficiency of resources
Use with/without VDI
Deploying Application Virtualization with VDI
287
True or False: Application Virtualization is an emerging technology, which can be deployed even without VDI.
True
288
A natural enhancement to a VDI environment, because it allows more users to connect to simplified and pooled virtual desktops.
Application Virtualization
289
a standard corporate Windows 7 desktop with only the barest applications required
typical virtual desktop
290
Location of users roaming profile
NAS
291
Default documents and desktop storage for the user
Users Roaming Profile
292
True or False: In an application virtualization environment, since the NAS solution is also in the data center along with the virtual desktop, working with documents is provided at-near or at-local disk speeds.
True
293
May provide the greatest benefit in terms of managing user images and resiliency against hypervisor failure.
Application Virtualization Environments
294
True or False: The connection broker works from a pool of desktops, and is not tied to a specific desktop hosted on a single hypervisor.
True
295
Benefits of Client-Side Application Virtualization
1. Cross-platform execution
2. OS isolation
3. Deployment flexibility
4. Ease of license tracking
5. Ease of patch deployment
296
Drawbacks of Client-Side Application Virtualization
1. Some applications cannot be virtualized.
2. Different and additional management tools.
3. Complexity
297
Application Consideration Checklist Questions 1 - 4
1. If this is a legacy app, can app convert from physical to virtual (P2V).
2. What is the VDC users tolerance to latency?
3. How critical is this application to the business?
4. How many users use this application?
298
Application Consideration Checklist Questions 5 - 8
5. How sensitive is the data used by the application?
6. Are there regulatory concerns with the data?
7. Is the application slated to be decommissioned?
8. Is the source code available?
299
Application Consideration Checklist Questions 9 - 12
9. What is the application's stack? (OS/DB, n-tier, etc.)
10. What are the application's integration points with other apps?
11. Estimated storage space need?
12. Estimated storage latency requirement?
300
Application Consideration Checklist Questions 13 - 16
13. Is the application usage pattern predictable?
14. What are the monitoring needs of the application?
15. Have transient applications workloads been taken into consideration (test/dev, migrations, conversions)?
16. Can the app be simplified by breaking it into pieces or purchasing COTS or use SaaS to replace homegrown elements?
301
Application Consideration Checklist Questions 17 - 20
17. Can interprocess communications be replaced with more network centric technologies?
18. Are apps designed to dynamically scale across all components?
19. Are load balancers designed in the solution?
20. Can the application interface handle new data stream inputs?
302
Application Consideration Checklist Questions 21 - 22
21. What is the acceptable application response time?
| 22. What is the cloud tenant / VDC users tolerance to latency?
303
Applications should be built for what two attributes?
Resiliency
Fault Tolerance
304
How are resiliency and fault tolerance applied to a distributed application?
Any failed shard or cluster should not halt or bring down the entire application.
305
Design applications based on what assumption?
The assumption that applications will fail.
306
High Availability Considerations 1 - 4
1. Does the application require High Availability (HA)?
2. Is the application designed for HA?
3. Is the launching of an application cluster automated?
4. Is the application data persistent?
307
High Availability Considerations 5 - 8
5. How are backups managed?
6. What are the redundancy options in the event of a hardware failure?
7. What are the disaster recovery options?
8. What concurrency model is in place for multi-user edits (pessimistic, optimistic, or none)?
308
High Availability Considerations 9 - 10
9. Is the application designed with network-based interfaces?
10. Is the application in a shared cluster, shared instance, or dedicated cluster?
309
Brownfield
Existing systems in place
310
Greenfield
New installations
311
Insert or replace into existing environment
Phased installations
312
Complete replacement of systems
Forklift upgrades
313
1. Maintains parallel systems
2. Can be more expensive due to duplicate systems
3. Requires some planning
4. Whole sections of the environment are replaced at a time
Forklift Upgrade
314
1. May not have parallel systems.
2. Can be less expensive, repurpose systems.
3. Requires extensive planning.
4. Small sections of the environment are replaced at a time.
Phased Upgrade
315
If the goal of a project is to migrate from a legacy architecture to a VDC, how might a phased plan be broken up?
A phased plan might be broken up across layers - storage, network, compute, and application.
316
Citrix ICA Client
1. Create a VDI infrastructure with app virtualization using XenDesktop and Xen App.
2. Infrastructure / App servers & desktops run on separate clusters w/ EMC VNX providing storage for both.
3. Cisco UCS used for desktop images
4. Cisco Nexus switches for connectivity.
317
Example of virtual desktop client software
Citrix ICA Client
318
How can different desktop configurations be deployed for different users based on their role in the organization?
Through integration with Active Directory Services
319
Provides authentication and authorization, as well as Group Policies for managing the redirection of user data folders and user state persistence between sessions.
Active Directory Services
320
Function of XenApp 6.5 servers
Streaming of virtualized applications
321
Function of XenDesktop 5.5 controllers
Control of the desktops
322
Function of XenServer 6
Hypervisor platform for the VDI environment
323
True or False: All of the infrastructure components that make up the VDI environment are running as VMs.
True
324
How many virtualized Windows 7 desktops (approx) can 20 Ciscu UCS B-Series blade servers handle?
~1,000 Windows 7 Virtualized Desktops
325
Function of Cisco UCS B-Series blade servers
Used to run the actual desktop instances (compute and network)
326
Function of EMC VNX5300
Stores the VM images for the infrastructure and desktop images, as well as serves CIFS shares for the redirected user profiles and home directories.
327
Benefits of a VDI infrastructure using EMC VNX, XenDesktop, XenApp, XenServer, & Cisco UCS
1. Increased security by centralizing business-critical information.
2. Increased compliance, & ability to prove compliance as data is not stored on the end points.
3. Ease of managing desktops through standardization & centralization.
4. Empowerment of users to work from any location.
5. Embraces the consumerization of IT through multiple end point support.
6. Increased business agility & adaptability by allowing rapid, flexible desktops to support changes in the business landscape.
328
Function of EMC Fast VP Tiered Storage
Move active data sources to Enterprise Flash Drives (EFDs) while less active data is moved to a tier more suited to lower performance requirements.
329
Benefit of tiered storage pools
Allow workload granularity that does not require the DBA to tune the database to meet SLA requirements.
330
What drives the architecture?
Application Requirements
331
What needs to be inventoried?
Applications, data, and security requirements.
