Session given at SPTechCon Boston 2012 on Moving your SharePoint Development sandbox to the Cloud. Builds a use case, explains tools, and process.

1. Moving your SharePoint
Development
To The:
1 | CONFIDENTIAL

2. Agenda
 Who are you? Who am I?
 The 4 Pillars of this session
 Why Dev/Test in the Cloud?
 The Tools
 The Process
 The Pitfalls
 Best Practices
 Demo
2 | CONFIDENTIAL

3. Who is Chris?
A guy who knows some stuff
about SharePoint
ECM Speaker and Author
Expert in: ECM, Virtualization, Cloud
A guy with acronyms
Chris Riley - @HoardingInfo
Product Manager / Evangelist
3 | CONFIDENTIAL

4. What is CloudShare?
A Cloud solution built for Pre-Production
4 | CONFIDENTIAL

5. Some definitions
Cloud
The server is not near you, virtualization
is used, and it’s accessible. It’s an
infrastructure term.
5 | CONFIDENTIAL

6. The “Cloud”
Internet, Servers
SaaS, PaaS, IaaS
Apps, Storage, Virtualization
Hybrid, Private, Public
ECM, BPM, WCM, BI
Your Mom
6 | CONFIDENTIAL

7. Some definitions
PaaS:
Just a service, you don’t have access to
the Virtual Machine
7 | CONFIDENTIAL

8. Some definitions
IaaS:
You get the virtual machine
8 | CONFIDENTIAL

9. Some definitions
Pre-Production:
All the activity that happens outside of
production. Demos, Development,
Testing, Proof-of-Concept
9 | CONFIDENTIAL

10. Four Pillars
10 | CONFIDENTIAL

11. What do you think of when you hear “Cloud”?
Production
11 | CONFIDENTIAL

12. Pillar 1
“Cloud” can be a solution for
pre-production and this if often its best use.
12 | CONFIDENTIAL

13. The great thing about SharePoint is you
can build anything!
13 | CONFIDENTIAL

14. The bad thing about SharePoint is you
can build anything!
14 | CONFIDENTIAL

15. Pillar 2:
SharePoint Dev/Test should happen in isolation
from SharePoint production.
YOU DON’T LISTEN!
15 | CONFIDENTIAL

16. 16 | CONFIDENTIAL

17. Moving to the cloud all at once is very difficult
17 | CONFIDENTIAL

18. Pillar 3:
Organizations should move to the
cloud in baby-steps.
18 | CONFIDENTIAL

19. Developers don’t typically control
infrastructure, even in the cloud!
19 | CONFIDENTIAL

20. Pillar 4:
In pre-production, not giving developers
control results in time wasted
20 | CONFIDENTIAL

21. The Pilars
=
Move your SharePoint development
to the cloud!
21 | CONFIDENTIAL

22. Why move to the cloud?
It takes a developer an average of 2 weeks
per request of infrastructure to receive the
infrastructure. Unless they have a machine
under their Desk.
22 | CONFIDENTIAL

23. Why move to the cloud?
During a project a developer will build and re-
build on average 7 or more VMs before initial
deployment.
23 | CONFIDENTIAL

24. Why move to the cloud?
At two weeks per VM for preparation, that is
greater then $500 per VM of just resources,
not to mention wasted time, and capital
expenses.
24 | CONFIDENTIAL

25. Why move to the cloud?
Cloud Benefits:
 Available anywhere
 Avoid local network and machine contamination
 Reduced infrastructure costs
25 | CONFIDENTIAL

26. Why Do It?
Make developers HAPPY
Make IT Managers HAPPY– yes, even them
Optimize production infrastructure investment
Predictable development costs
Reduced barriers to entry for any project
Eliminate Capital Expense for Dev/Test work
Make developers more effective
26 | CONFIDENTIAL

27. Is it Secure?
27 | CONFIDENTIAL

28. What you need
Visual Studio
SharePoint Dev/Test farm(s)
Cloud Provider – IaaS + SaaS
 Amazon
 Azure
 CloudShare
 Rackspace
Browser
28 | CONFIDENTIAL

29. What do you need
 Connectivity
 RDP
 File Transfers
 Web Access / Viewing
 Migration Tools/Method
 Content DB
 WPS
 Code
 3rd Party tools
29 | CONFIDENTIAL

30. The Process
Identify your types of projects
Where does the IDE live?
Source Repository: Yes or No?
Testing and Staging Environments?
30 | CONFIDENTIAL

31. Process
• Dev On-Prem with Testing in the Cloud
• Dev and Testing in the Cloud
31 | CONFIDENTIAL

32. Process
TFS Location Development Location Testing Location
PaaS
Dev Cloud On-Premise Dev Cloud On-Premise Dev Cloud
(TFS, GIT)
Scenario 1
X X X
Scenario 2
X X X
Scenario 3
X X X
Scenario 4
X X X
Scenario 5
X X X
Scenario 6
X X X
32 | CONFIDENTIAL

33. Process
 Build base templates ( VM Library )
 Give Developers access to templates
 Take snapshots of every major version
 Single Server farm vs. Multi-Server
33 | CONFIDENTIAL

34. Common Pitfalls
 Not planning for migration upfront
 Fear of failure
 Using PaaS as Dev/Test
 Rolling Dev/Test into all other IT operations
34 | CONFIDENTIAL

35. Best Practices
 Fail fast and often
 Plan for migration at the beginning
 Give developers control
 Don’t share logins!
 Forget about infrastructure
 Script your deployments and use Solution
Packages WSP
35 | CONFIDENTIAL

36. Contact
Chris Riley
Product Management / Evangelism
Email: Chris@CloudShare.com
Twitter: @HoardingInfo
Phone: 925-640-4361
36 | CONFIDENTIAL