Move your SharePoint Development to the Cloud

1,034 views

Published on

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

Published in: Technology, Business
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,034
On SlideShare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
0
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide
  • Networking, bandwidth, IP addresses, CPU usage, and maintenance
  • Networking, bandwidth, IP addresses, CPU usage, and maintenance
  • Networking, bandwidth, IP addresses, CPU usage, and maintenance
  • Networking, bandwidth, IP addresses, CPU usage, and maintenance
  • Networking, bandwidth, IP addresses, CPU usage, and maintenance
  • Networking, bandwidth, IP addresses, CPU usage, and maintenance
  • Networking, bandwidth, IP addresses, CPU usage, and maintenance
  • Networking, bandwidth, IP addresses, CPU usage, and maintenance
  • Networking, bandwidth, IP addresses, CPU usage, and maintenance
  • Networking, bandwidth, IP addresses, CPU usage, and maintenance
  • Networking, bandwidth, IP addresses, CPU usage, and maintenance
  • Networking, bandwidth, IP addresses, CPU usage, and maintenance
  • Networking, bandwidth, IP addresses, CPU usage, and maintenance
  • Networking, bandwidth, IP addresses, CPU usage, and maintenance
  • Networking, bandwidth, IP addresses, CPU usage, and maintenance
  • Networking, bandwidth, IP addresses, CPU usage, and maintenance
  • Networking, bandwidth, IP addresses, CPU usage, and maintenance
  • Networking, bandwidth, IP addresses, CPU usage, and maintenance
  • Networking, bandwidth, IP addresses, CPU usage, and maintenance
  • Networking, bandwidth, IP addresses, CPU usage, and maintenance
  • Networking, bandwidth, IP addresses, CPU usage, and maintenance
  • Networking, bandwidth, IP addresses, CPU usage, and maintenance
  • Networking, bandwidth, IP addresses, CPU usage, and maintenance
  • Networking, bandwidth, IP addresses, CPU usage, and maintenance
  • Networking, bandwidth, IP addresses, CPU usage, and maintenance
  • Move your SharePoint Development to the Cloud

    1. 1. Moving your SharePoint Development To The:1 | CONFIDENTIAL
    2. 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 Demo2 | CONFIDENTIAL
    3. 3. Who is Chris?A guy who knows some stuffabout SharePointECM Speaker and AuthorExpert in: ECM, Virtualization, CloudA guy with acronyms Chris Riley - @HoardingInfo Product Manager / Evangelist3 | CONFIDENTIAL
    4. 4. What is CloudShare? A Cloud solution built for Pre-Production4 | CONFIDENTIAL
    5. 5. Some definitions CloudThe server is not near you, virtualization is used, and it’s accessible. It’s an infrastructure term.5 | CONFIDENTIAL
    6. 6. The “Cloud” Internet, Servers SaaS, PaaS, IaaS Apps, Storage, Virtualization Hybrid, Private, Public ECM, BPM, WCM, BI Your Mom6 | CONFIDENTIAL
    7. 7. Some definitions PaaS:Just a service, you don’t have access to the Virtual Machine7 | CONFIDENTIAL
    8. 8. Some definitions IaaS: You get the virtual machine8 | CONFIDENTIAL
    9. 9. Some definitions Pre-Production: All the activity that happens outside of production. Demos, Development, Testing, Proof-of-Concept9 | CONFIDENTIAL
    10. 10. Four Pillars10 | CONFIDENTIAL
    11. 11. What do you think of when you hear “Cloud”? Production11 | CONFIDENTIAL
    12. 12. Pillar 1 “Cloud” can be a solution for pre-production and this if often its best use.12 | CONFIDENTIAL
    13. 13. The great thing about SharePoint is you can build anything!13 | CONFIDENTIAL
    14. 14. The bad thing about SharePoint is you can build anything!14 | CONFIDENTIAL
    15. 15. Pillar 2:SharePoint Dev/Test should happen in isolation from SharePoint production. YOU DON’T LISTEN!15 | CONFIDENTIAL
    16. 16. 16 | CONFIDENTIAL
    17. 17. Moving to the cloud all at once is very difficult17 | CONFIDENTIAL
    18. 18. Pillar 3: Organizations should move to the cloud in baby-steps.18 | CONFIDENTIAL
    19. 19. Developers don’t typically control infrastructure, even in the cloud!19 | CONFIDENTIAL
    20. 20. Pillar 4: In pre-production, not giving developers control results in time wasted20 | CONFIDENTIAL
    21. 21. The Pilars = Move your SharePoint development to the cloud!21 | CONFIDENTIAL
    22. 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. 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. 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. 25. Why move to the cloud? Cloud Benefits:  Available anywhere  Avoid local network and machine contamination  Reduced infrastructure costs25 | CONFIDENTIAL
    26. 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 effective26 | CONFIDENTIAL
    27. 27. Is it Secure?27 | CONFIDENTIAL
    28. 28. What you need Visual Studio SharePoint Dev/Test farm(s) Cloud Provider – IaaS + SaaS  Amazon  Azure  CloudShare  Rackspace Browser28 | CONFIDENTIAL
    29. 29. What do you need  Connectivity  RDP  File Transfers  Web Access / Viewing  Migration Tools/Method  Content DB  WPS  Code  3rd Party tools29 | CONFIDENTIAL
    30. 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. 31. Process • Dev On-Prem with Testing in the Cloud • Dev and Testing in the Cloud31 | CONFIDENTIAL
    32. 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 X32 | CONFIDENTIAL
    33. 33. Process  Build base templates ( VM Library )  Give Developers access to templates  Take snapshots of every major version  Single Server farm vs. Multi-Server33 | CONFIDENTIAL
    34. 34. Common Pitfalls  Not planning for migration upfront  Fear of failure  Using PaaS as Dev/Test  Rolling Dev/Test into all other IT operations34 | CONFIDENTIAL
    35. 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 WSP35 | CONFIDENTIAL
    36. 36. Contact Chris Riley Product Management / Evangelism Email: Chris@CloudShare.com Twitter: @HoardingInfo Phone: 925-640-436136 | CONFIDENTIAL

    ×