Going Green: Saving Cash and Carbon through Virtualization, Server Consolidation and Centralized Infrastructures

grrrgrapeInternet and Web Development

Oct 31, 2013 (3 years and 10 months ago)

65 views

GENII RESEARCH,
LLC


50 DIVISION AVENUE

SUITE 16

MILLINGTON
, NJ 07946

(866) MYGENII

(866) 694
-
3644

INFO@MYGENI I.ORG



Going Green: Saving Cash and Carbon
through Virtualization, Server Consolidation
and Centralized Infrastructures

Top Three Takaways

1.
An understanding of the differences between the
more common “distributed” network design model
(used by most nonprofits) and a centralized one.

2.
An understanding of how to save your organization
time and money with centralized network
infrastructures that make use of modern
virtualization technologies.

3.
End user tools and knowledge that will help you
decide whether this type of design strategy can help
your organization stretch IT dollars and, if so, by
how much.

Introductions

Paul D. Kerness, MSW, LSW, MCP

Chief Technical Officer

Genii Research, LLC

Microsoft Small Business Specialist

50 Division Avenue

Suite 16

Millington, NJ 07946


(866) MYGENII

(866) 694
-
3644

Overview


Centralized Infrastructure Design Concepts


History of Centralized Design Models


back to the future


Distributed vs. Centralized Network Architectures

Spam and virus
infected email
account for over
70% of all email
sent today

email is
becoming
more important
than the phone

Communication

Staff increasingly
want, need and
expect the ability
to work from
home or on the
road

Mobile

Workers

Units need to
work together
and share
information
more quickly
than ever

Collaboration

User tolerance
for email
downtime is
less than 30
minutes

Increasing
complexity,
security and
regulatory
concerns

The Infrastructure Challenge

+

+

+

+

Sources: Meta Group, Pew Research Center, Gartner,

Computer Security Institute/FBI, Dynamic Markets LTD. , Accenture

Escalating

End User

Needs

Increasing

IT Burden

Security

Service

Levels

Management

and Costs

Network Design Goals


Efficient Use of Resources


Economy of Scale


Provide a Secure Infrastructure


Reduce Organizational Risk


Provide Remote Access to Entire Network


Provide Collaboration Tools


Provide Document Management


Reduce Paper Forms


Increase Access to Real Time Organizational Information


Distributed or Centralized?

Centralized Network Design


Server
-
Based Computing


Nothing New


Mature Technology


Sometimes referred to as:


server
-
centric


application
-
server


Terminal server


Access Infrastructure


Software as a Service (SaaS)

Distributed Network Design


Resources are Distributed


Applications are deployed, supported, and executed on
geographically distributed PC’s and servers


Data is stored on hard disks of many geographically
distributed PC’s and Servers


Limited Access from Remote Locations

Distributed Resources Network

It’s really an infrastructure that
is independent of geography.

It makes use of the Internet to
connect scattered people,
devices and services together.

Relies on Shared Resources.

Centralized Network Design


Resources are Centralized


all applications are deployed, supported, and executed
at the server, not at the user desktop/PC.


All data is stored in the datacenter/server.


A single “locked down” desktop is shared by everyone


A single application installation is shared by everyone


Centralized Network Design


Resources are Centralized


Only keystrokes, mouse clicks, and the screen images travel
across the network (or the Internet).


All applications are displayed on the desktop device. This
desktop device can be a text terminal, a Mac, a PC, a
PDA/Mobile device, and/or a thin client.


Distributed vs. Centralized Network

Cable/DSL

More Efficient Resource Utilization

Change IT’s Role

Desktop &
Application
Support, 38%

Infrastructure, 19%

Management &
Strategy, 25%

Application
Development, 7%

End User
Training,
10%

Medium Sized Organization

Change IT’s Role

Desktop &
Application
Support, 10%

Infrastructure, 10%

Management &
Strategy, 35%

Application
Development, 30%

End User
Training, 15%

Medium Sized Organization

Centralized vs. Distributed

Virtualization


What is “Virtualization” and how does it work?


What can be virtualized?


Hardware Layer


Disk Virtualization


Operating System Layer


Presentation Layer


Application Layer


Common Virtualization Tools



Common Virtualization Tools


Softgrid


VMWare


Windows 2008 and Virtualization


Thin Clients


Server (Hardware) Virtualization


Server virtualization is a hot topic in the IT world
because of the potential for serious economic benefits.


Server virtualization enables multiple operating systems
to run on a single physical machine as virtual machines
(VMs).


You can consolidate workloads of underutilized server
machines onto a smaller number of fully utilized
machines.


Fewer physical machines can lead to reduced costs
through lower hardware, energy, and management
overhead, plus the creation of a more dynamic IT
infrastructure.


Application Virtualization


Benefits:


Data can be centralized in one location to improve security and
availability.


Management costs can be reduced by only having to manage a single
copy of the application on the server.


More basic terminal hardware and thin clients can be used in placed
of complete desktop systems, helping lower costs.


Bandwidth can be used more effectively, leading to potential
performance improvements.


Deploy applications that integrate seamlessly with the user’s local
desktop.


Provide access to centrally managed Windows desktops.


Enable remote access for existing “WAN
-
unfriendly” applications.


Highly secure applications and data within the data center

no need
to worry about lost laptops.



Accessing a Remote Application


Users can access TS RemoteApp in a number of
ways:


Double
-
clicking a program icon on their desktop or
Start

menu that has been created and distributed by their
administrator


Double
-
clicking a file which has an extension associated with a
TS RemoteApp


Accessing a link to the TS RemoteApp on a Web site by using
TS Web Access


Application Virtualization



Standard Operating System


Applications install their settings onto the
host operating system, hard
-
coding the
entire system to fit that application's
needs.


Other applications' settings can be
overwritten, possibly causing them to
malfunction or break.

Application Virtualization

Virtual Application Environment


Each application brings down its
own set of configurations on
-
demand


Each Application Executes in a way
so that only it sees its own settings.

Side
-
By
-
Side Virtualization


Each virtual application brings down its own
set of configurations and can run side
-
by
-
side
without the settings conflicting with each other


or the host operating system.



Despite this separation, inter
-
application
communication with other Virtual applications
and those installed locally is preserved


This allows for cut and paste, OLE, and all
other standard operations.

Application Virtualization

Typical Remote Session

Data Center

Internet

Keyboard Strokes & Mouse Movements

Screen Updates & Print Jobs

Any Internet
Connected PC

TS Session Directory with Load
-
Balancing

TS
-
1

TS
-
2

TS
-
3

Load
-
Balancer (LB
-
1)

Session Directory

TS
-
3

User Session
on TS
-
3

1. User
connects to
Load Balancer

2. Load Balancer routes
user to “least
-
busy”
server

3. Server
responds

4. User enters

credentials

SamanthaSmith

***********

5. Server authenticates
“SamanthaSmith” and checks
Session Directory for existing
session

6. SD informs TS that
user has a session on

TS

3

7. TS returns user
credentials with token
and tells client to
reconnect

LB
-
1

TS
-
3

SamanthaSmith

***********

8. Session broken down

on TS
-
2. Client reconnects
to load
-
balancer with token
and credentials

9. Load
-
balancer examines
token and directs connection
to TS3, passing through
credentials

10. Original
session from TS3
presented to user

SamanthaSmith

TS
-
1

TS
-
2

TS
-
3

Load
-
Balancer (LB
-
1)

Session Directory

1. User
connects to
Load Balancer

Putting It Together


Terminal Services and Centralization


Server Consolidation


Server Consolidation

Windows 2008 Host Server

Thin Computing Benefits


Less Environmental Impact


Production


Less to Transport


Use Less Energy


Endurance


Disposal


Infrastructure Benefits


Security


Manageability


Availability


Reliability


Total Cost of Ownership


Scalability



Thin Computing Benefits


Security


No local storage


not vulnerable to viruses and other malware


no way to store and remove proprietary information


nothing is stored on the desktop,


Security software is also easier to maintain, update, and
upgrade on a few servers instead of many desktop systems.

Thin Computing Benefits


Manageability


Thin clients are much easier to deploy and configure


Backing up data is also easy, since all the data resides on the
server.


updates are performed at the server level, eliminating the need
for manual updates of individual systems.

Thin Computing Benefits


Availability


solid
-
state technology,


no moving parts to fail. And with no local storage, there is


data is always instantly available from another system.

Thin Client Benefits


Reliability


Thin clients are many times more reliable than PCs


MTBF (Mean Time Between Failures) of 150,000 hours


By avoiding the introduction of downloaded software while
pushing storage and computing power to more reliable servers,
thin computing dramatically increases the reliability of the
entire infrastructure.

Thin Computing Benefits


Total Cost of Ownership


The average annual maintenance costs for a PC are four to
seven times the acquisition costs.


This is not true for thin clients. On average, thin clients can
save you more than $1000 per seat per year in maintenance
costs.


This can be as much as a 40
-
percent savings for most IT
departments

Thin Computing Benefits


Scalability


With thin computing, the only set up required for a new user
or in a remote office is plugging in three or four cables.


The rest of the set up can take place in the data center.


A well
-
designed thin
-
computing solution can support up to
40,000 thin clients.


Thin Client vs. PC
--

Energy Requirement with Server Share

Costs in Dollars
-

One Year



Thin Client

Thin Client with
server pro rata +
server cooling
3

PC

Power consumption 1

16 W

41 W

85 W

x 8 hours per day

128 Wh

328 Wh

680 Wh

x 220 working days per year

28 kWh

72 kWh

149 kWh

Costs for 1 working station per year 2


$ 5.67


$
14.54


$ 30.03

-

10 working stations


$ 56.70


$
145.40


$
300.30

-

100 working stations


$ 567.00


$
1,454.00


$ 3,003.00

-

1,000 working stations


$ 5,670.00


$
14,540.00


$ 30,030.00

Savings TC compared to PC

81%

51%



Note 1
--

average active power

Note 2
--

electricity tariff = 0.15 kWh

Note 3
--

Worst case: 20 User / Server

CO2 Wastage with Server Share

Pounds of CO2
-

One Year



Thin Client

Thin Client with
server pro rata +
server cooling 3

PC

Power consumption
1

16 W

41 W

85 W

x 8 hours per day

128 Wh

328 Wh

680 Wh

x 220 working days per year

28 kWh

72 kWh

149 kWh

CO2 resulting from 1 working station per year
2


38.89 lbs


100.00 lbs


206.95 lbs

-

10 working stations


388.90 lbs


1,000.00 lbs


2,069.50 lbs

-

100 working stations


3,889.00 lbs


10,000.00 lbs


20,695.00 lbs

-

1,000 working stations


38,890.00 lbs


100,000.00 lbs


206,950.00 lbs

Note 1
--

average active power

Note 2
--

The production of one kWh from the electricity network gives rise to 1.39 lbs CO2

Note 3
--

Worst case: 20 User / Server

Calculating ROI

Q & A