Presentation to the CSix Cloud Computing Group. Hello Cloud Project was a project that explored, developed, and deployed in The Cloud. Project Team consisted of CSIx Cloud Computing Members. Project Manager, Julie McDaniel; Dan Levin.

1. Hello Cloud(a cloud experience project)(a global, cross-functional, virtual, agile effort) January 29, 2010

3. Why, What and Who

4. Cloud stack

5. What everyone wants you to believe

6. Project details

7. Requirements, Proposed implementation

8. Final implementation

9. Architecture, Options, Cloud vs. Non-Cloud

10. Lessons learned

12. Increased utilization

13. Online collaboration

14. Rapid application deployment

15. On demand access to resources

16. Deployment can be done with little upfront costs & overhead

18. Number of licenses; include in SLA (service level agreement) details about number of licenses & potential business growth

19. Storage space; include in SLA details about potential for business growth (potential for storage expansion)

20. Storage key component – IT typically is concerned with security of data stored

21. Cost savings dependent upon IT personal resources. Need to determine if in house or partner with a vendor for a set amount of resource time/hours.

23. SaaS; PaaS; IaaS; Private; Public; Hybrid

24. When leveraging SaaS, you must evaluate the security of the provider

25. Data center location

26. Application Security: role based access control

27. Policy management: how are policies consumed & enforced

28. Identity Management

29. SPML - Service Provisioning Markup Language

31. Experience first hand

32. To get “our arms” around the Cloud concept

33. To gain and share information & knowledge about

34. "What is the process of working 'in the cloud'"

35. "How is it different - traditional vs. cloud computing processes?"

38. Software Engineers, Developers, Programmers, Architects

39. Business Analysts

40. Project & Program Managers

41. Sales, Marketing, & Product Professionals

42. Cross section of Silicon Valley Companies

44. The Cloud: Conceptual

46. The Cloud: Types

47. The Cloud: Architecture

48. Hello Cloud - Implementation

50. Used their search software to embed into a box (yellow/blue) and sell it to enterprise customers

51. Google desktop enterprise - ability to searches within the enterprise

52. Gmail launched in 2004

53. Apps for domain launched in 2006

54. Gmail, Calendar, Talk are born

55. Acquires Writely (for docs) and 2WebTechnologies(excel)

56. Acquires Jotspot in 2008. Revamps as Google Sites

57. Re-brand themselves as providing communication and collaboration tools for all business sizes

58. Comes out of beta after 3 years. Commercializes in 2009

60. It’s PaaS for development of cloud services

61. Two platforms

62. Python

63. Java

64. Provides “out-of-the-box” integration with all Google APIs

65. Google Apps, Maps

66. Allows enterprise to develop their apps on the App engine and link them to their domain

68. Anything that compiles JVM executable byte code can be used

69. Develop in Java, Closure, Scala, any other language runable on JVM

70. Java engine provides a rich application server to host Java EE applications

71. Google documentation

72. How to create a Java Servlet on Eclipse & deploy it to Google Apps

74. Installing virgin Eclipse easy with no other plug-ins installed

75. However, issues with installing other plug-ins once virgin Eclipse installed

76. Installed Eclipse Web Development Tools; could not install Google plug-in afterwords

77. So just use the stock, Eclipse for Java Developers flavor of Eclipse

78. Read David's "gory" details here

80. Easy to implement within current environment

81. Windows Azure: operating system as a service

82. Microsoft SQL Azure: fully relational database in the cloud

83. Visual Studio development environment to create applications

84. Structure storage; scales well

86. Development is well integrated with Visual Studio

87. Application deployment is relatively easy--again, Visual Studio integration is the key

89. Setting up is time consuming--get/install SDKs and tools, apply patches, etc.

90. Diagnosing deployment errors can be very difficult

92. Upload, download, store data across the Internet

93. Can use data with other Amazon web services e.g. EC2 (Elastic Compute Cloud)

94. Storage via buckets/containers

95. Up to 100 buckets

96. Store objects in a bucket

97. Up to 5 GB

98. Access to Amazon S3

100. Using S3 to host web sites can be extremely inexpensive

102. No server side services, e.g., database, are available

104. Enables to provision HW resources on the fly

105. You can get various flavors of compute power on tap

106. Pre-loaded machine images with OS + SW you choose

107. Billed by the hour to your CC (Opex)

108. Supported OS’es

109. Redhat Linux, Windows server, Oracle Enterprise linux, OpenSuse, Open Solaris

110. Supported software

111. Databases: DB2, MySql, Oracle, MS SQL

112. Web Hosting: Apache, IIS, IBM Lotus, Websphere

114. Little to no experience needed

115. Lowered risks for development & deployment

116. "Excercise" flexibility

117. Many resources available (Google Apps, AWS, MS, start-ups)

118. It only takes a major credit card - but read the fine print

119. Know what your needs are for development – databases

121. Not your traditional 40 hour work week

122. All volunteer group

123. Dynamic & diverse group

124. Yet local; face-to-face "opportunity"

125. Meetings & Resource Constraints

126. Where & when to meet - priorities; location

127. Junaid Qurashi; Bryan Wing; Chaganti Radhakrishna (RK)

129. http://sites.google.com/site/csixclhttp://sites.google.com/site/csixcloudcomp/member_content/cloud_membersoudcomp/member_content/cloud_members

130. Ted Franklin

131. "To Cloud or Not To Cloud; Clearing the Skies for the SMB" 9/25/2009

132. Jim Lee

133. "Musings On Cloud Computing" 11/20/2009

134. David Skyberg

135. "Security In The Cloud" 11/22/2009

136. Craig Prescott

137. "Amazon Simple Storage Service (S3) Authentication of REST Access" 12/12/2009

138. Hello Cloud Project Website (Demo; Technology; Project Execution - documents; meeting notes)

140. Backup

142. Develop best practices & standards within industry constorums