1. Head in the Clouds Aligning for the future
Jack Wilson
Senior Client Consultant
Coretek Services

2. Cloud is not a religion Terminology: Private Cloud
Is a virtual infrastructure that exists with your organization’s or a hosted datacenter
Public Cloud
Is a virtual infrastructure that exists outside of your organization in a large remote site, not owned by you
Hybrid Cloud
Is a combination of the above, some applications/data in a Public Cloud site and some in your site.

3. The popularization of the term “Cloud Computing” can be traced to 2006 when Amazon.com introduced the Elastic Compute Cloud
Software-defined data center (SDDC) is the phrase used to refer to a data center where all infrastructure is virtualized and delivered as a service.
“Every twelve to eighteen months, computers double their capabilities, and so do the information technologies that use them.” EmergingFutures.com

4. Microsoft chief executive Satya Nadella promised a “mobile first, cloud first” strategy
As Microsoft turns 40, CEO Satya Nadella looks beyond Windows to the cloud / April 4th 2015

5. Where are the major players going?

6. The only installed apps will soon only be your legacy applications

7. The key is to move from the Complex Distributed Legacy to a Streamlined Virtual architecture

8. Preparing for a Cloud Future
First Step
Where are you now?
-solid assessment of the
evolved infrastructure
-”Legacy Drag”
-traditional distributed architecture
-maybe some server virtualization
-maybe some endpoint virtualization
-maybe using one or a few SaaS

9. Preparing for a Cloud Future
Second Step
Where do you want to go?
-Target environment
Flexible agile technology architecture
web-based delivery
anywhere, any device access
lower cost
easily supportable or better yet let someone else support

10. Hard to make one big leap
It usually takes a process to move from an organic evolved architecture to a more thoughtful cloud strategy
Moving a mess, won’t work 10

11. Preparing for a Cloud Future
Best Practice Approach
Virtualize & Streamline current environment
Two key components
Virtualize the servers and endpoints
Desktops, applications and data are in your datacenter
you’ve created a
PRIVATE CLOUD

12. Preparing for a Cloud Future
What steps are involved?
Discover all the application in your environment
discard what not being used (save $)
consolidate redundant functions
what are the core client facing applications
own and control these
what are the common function applications
no competitive advantage
routine functions

13. Preparing for a Cloud Future
Rationalize your applications portfolio
Streamline “Southwest Airline”
approach
Discover all the applications in your environment
(not an easy task, but necessary)
discard what’s not being used (save $)
consolidate redundant functions

14. Preparing for a Cloud Future
Left are the applications your business needs
Key decision
what are the core client facing applications own and control these
keep and support these in your
Private Virtual Cloud (at least for now)
what are the common function applications no competitive advantage
everybody needs and has them
move to SaaS model in the
Public Cloud

15. Centralized Virtualized Desktop
The Private Cloud Applications are published to a virtual desktop, supported in one central location
The Public Cloud Applications are accessed by a browser on the virtual desktop, vendor maintains and supports
Everything is accessed via a browser
Ready for an eventual all web-based world.
Endpoints are irrelevant
Mobile devices can access desktop and applications
BYOD is now possible
All data is now in the Private or Public cloud not on the endpoint

16. Preparing for a Cloud Future
Now you have a Virtual / Hybrid Cloud architecture that positions you for the future, while being transformative right now.
Business agility
Access anywhere,
Anytime, Any Device
Better Security
Lower cost
Focus on Critical applications and new functionality

17. Preparing for a Cloud Future
Now you positioned to look at PaaS or IaaS
Both of these are maturing technologies that are still in the Pioneer stage for the most part.
You can now develop web replacements for your Critical legacy applications in a PaaS environment
Since you have created a centralize private cloud, you could get out of the datacenter business and move that to a hosted datacenter or an IaaS environment in the future

18. Preparing for a Cloud Future
Few issues to consider
All Public Cloud vendors are not equal
Check security,
you’re now in a shared environment
Who owns the data?
you or the vendor
Interface between public cloud and private cloud
(now in different locations)
Vendors business continuity/disaster recovery
Exit options (if any)

19. Thank you / Questions Project Success NO Exceptions
Jack Wilson Senior Client Consultant
Project Success
NO Exceptions