DRussell4881 12000070EV 376 Visits
Cloud Computing Use Cases White Paper V5 - Moving to the Cloud published - http://cloudusecases.org/
Version 6 will focus on Cloud User Roles with comments posted at http://groups.google.com/group/cloud-computing-use-cases/.
DRussell4881 12000070EV 330 Visits
Cloud User Roles discussion - http://groups.google.com/group/cloud-computing-use-cases
In order to define the roles and the respective responsibilities in support of making the right decision to implement Cloud Computing it may be best to identify the tasks to be completed.
Let’s identify the tasks and then fill in who should be part of completing the task )NOTE: More than one area within the enterprise may need to work together to provide the required information to complete a task). Once we had identified the individuals, then we can start filling in the responsibilities for that individual. Where an individual shows up in more that one decision area, the activities in that role can be added to expand the overall responsibilities.
Let’s start with who makes the decision to adopt Cloud Computing. In otherwords, who is responsible for establishing the criteria for ensuring the right decision is made?
- What are the business criteria for making the move?
- Who sets the criteria?
- Who is the core set of decision makers required to define the decision process criteria, review the information provided and make the decision to implement a Cloud Computing solution?
Once the business criteria has been set, there are supporting activities to build the complete plan.
Here are some examples:
- Who defines the ROI criteria which is used to test each proposal to ensure a positive return to the business?
- Who develops and manages the Service Level agreement against expected service level?
- Who ensures that the resulting proposal addresses immediate, future business requirements and also will create a competitive advantage for the enterprise?
- Who describes the requirements / implications for Business Flexibility (i.e. Portability/Interoperability)?
- Who is responsible for setting the criteria for Date Privacy and Security?
- Who is responsible for ensuring the transition to Cloud Computing is transparent to the users?
- Who is responsible for setting the requirements / managing the resources for the development / acquisition of the services?
- Who is responsible for the managing the procurement of any new resources / assets?
- Who are the individuals needed to gather the information to make a recommendation for either a Public or Private Cloud?
- Who is responsible to do an assessment on the reuse of existing services and what is required to deploy those services into the Cloud?
- Other activities not listed here.
Look forward to your comments.
DRussell4881 12000070EV 330 Visits
Cloud User Roles discussion: http://groups.google.com/group/cloud-computing-use-cases
With the “Moving to the Cloud” version about to be completed, the question that comes to mind, “Who needs to be part of the decision process to ensure success in moving services to the Cloud”? As Cloud Computing continues to evolve, the decision process for Cloud or no cloud in an enterprise becomes more critical as enterprises are no longer looking to put non-trivial solutions into the cloud. If mission critical solutions are to be considered, then it is important that the right people have all the rationale available to make the right decision. It should also be noted, that in today’s world, decisions surrounding IT require that not only the IT line be involved, but the Business line must also be a core partner in the decision process. Therefore, let’s work on identifying the roles and the responsibilities of the decision makers.
The base assumption is that there can be two or three main parties to a successful partnership for identifying, providing and executing cloud services.
At minimum there are the:
Cloud consumer – The party who contracts for the Cloud service and is ultimately accountable to the users of the service for performance, accuracy of results and any improvements required to meet existing or new business requirements.
Cloud Provider – The party who provides the Cloud Consumer with a contracted service based on the requirements of the Cloud Consumer. The Cloud provider may also undertake subcontracting specific services to meet demands which temporarily exceed the capabilities of the primary provider.
Cloud Services Creator - The services creator can be a standalone entity or can reside in either the domain of the Cloud Consumer or the Cloud Provider. It is important to understand who is to provide the service and what role / responsibility is expected for the identified service.
To set the stage, let’s set up a series of questions that should be answered prior to making the final decision of a moving a solution / service / platform to the Cloud:
- What is the process to engage both the IT and Business communities of the enterprise to ensure that the new solution will meet the total needs of the business?
- What are the criteria to make the decision?
- The Enterprise had an application / platform / infrastructure – who needs to be involved make decision to make the move to the Cloud?
- Who is responsible for collecting the information to represent the criteria?
- Who makes the final decision?
- Who is the individual accountable for the final decision?
- Who is responsible for measuring the results to align with the expected ROI for the newly implemented Cloud Solution?
- Who is responsible for the cloud service once it is implemented?
- What metrics are in place to ensure the decision is meeting the intended goals?
- Who monitors availability / performance / etc. for the running service?
- Who is responsible to manage resolving failures or upgrades to the solution / service?
- Who is responsible to respond to queries should there be a problem with the service, to either in-house or external users or both?
- Who is responsible for the negotiations between any third parties?
- Who is responsible for the communications between the Cloud Consumer and the Cloud Provider(s)?
A further consideration in the decision process, there needs to be a decision as to the type of cloud to host the service – Private, public, hybrid or community. Each cloud type brings new decision points to consider.
All the above and any additional questions must be considered and answered as part of the decision process to ensure not only a successful implementation of a cloud service, but also the continued mapping of the service against documented expectations. As part of the answering of the questions, levels of responsibility must be assigned. To ensure continuity, the must be clearly linkages up and down the responsible areas (or individuals) to ensure that no decision is made in isolation.
A very critical of the element requires that there needs to be effective communications between the Cloud Consumer and the Cloud Provider and potentially a third party which could be a creator of cloud services which the cloud consumer wishes to acquire and have hosted by the cloud provider.
The bottom line is that the risks of moving services to the cloud can be significantly reduced if the owners of the decision are clearly identified, the right information is brought forward and the appropriate checks are put in place to manage the service after the decision is made.
Our goal should be to connect the responsible individuals from each the providers (Consumer, Provider and Creator). Being able to demonstrate both the vertical and horizontal communication lines, is the key to success to not having any surprises and the final decision will be made with all the facts required.
Examples of potential individuals who may be involved in the decision process are:
- Executive level decision maker ( VP, President, or CEO )
- Finance Manager
- Operations Manager
- Service Manager
- Development Manager
- IT Architect
- Business Architect
- Contracts Manager ( also includes Legal )
- Customer Relations
- Business Analyst
- Facilities Manager
- Procurement Manager
- Others as identified
Let’s begin to work thru the questions:
1. What is the process to engage both the IT and Business communities of the enterprise to ensure that the new solution will meet the total needs of the business?
2. What are the criteria to make the decision?
3. The Enterprise had an application / platform / infrastructure – who needs to be involved make decision to make the move to the Cloud?
4. Who is responsible for collecting the information to represent the criteria?
5. Who makes the final decision?
6. Who is the individual accountable for the final decision?
7. Who is responsible for measuring the results to align with the expected ROI for the newly implemented Cloud Solution?
8. Who is responsible for the cloud service once it is implemented?
9. What metrics are in place to ensure the decision is meeting the intended goals?
10. Who monitors availability / performance / etc. for the running service?
11. Who is responsible to manage resolving failures or upgrades to the solution / service?
12. Who is responsible to respond to queries should there be a problem with the service, to either in-house or external users or both?
13. Who is responsible for the negotiations between any third parties?
14. Who is responsible for the communications between the Cloud Consumer and the Cloud Provider(s)?
Potential outputs to develop:
a) Identification of the responsible individuals within each provider
b) Explanation of the role of the responsible individuals
c) Matrix showing the linkage of responsible individuals within each provider
d) Matrix showing the linkage of responsible individuals across the providers
We look forward to your responses at http://groups.google.com/group/cloud-computing-use-cases to the above questions as we move to capture inputs and develop the next version of the Cloud Computing Use Cases White Paper.
DRussell4881 12000070EV 409 Visits
The Cloud Computing Use Cases White Paper V4 has been translated into Korean. Special thanks to Yangwoo Paul Kim, a professor at Dongguk University in Seoul, Korea for completing this work.
The translated version can be found at http://cloudusecases.org/ .
DRussell4881 12000070EV 536 Visits
Draft 1 of V4, which focuses on Service Level Agreements (SLAs), has just been posted at http://su.pr/AS7FHa on the Cloud Computing Use Cases discussion group.
We are looking for your input on the following:
1 - New use cases in which the choice of cloud service or provider hinges on the terms of the SLA would be best. Use cases that stress the SLA-related aspects of the ones already in the paper would also be really helpful.
2 - Your input on where check boxes go in the table (Section 1.6 - Cross-Reference). We would also appreciate your input on the value of the table once the table is completed.
3 - Your overall comments on the draft, and identifying anything that is missing.
Comments can be posted to http://su.pr/2mStGR
There are some folks who may be nervous using shortened URLs. If that is the case, the Cloud Computing Use Case discussion group can be found at http://groups.google.com/group/cloud-computing-use-cases and look in the "FILES" section at the bottom of the home page for Draft 1 of the SLA section for V4.
Looking forward to your comments!
DRussell4881 12000070EV 464 Visits
A new discussion group has been launched today to capture the requirements for Cloud Computing to support IT in China - http://su.pr/1LUova. Requirements identified by this group will be added to the existing work that has been documented in the Cloud Computing Use Cases White Paper - http://su.pr/18XGhE. In addition to the paper being published in English, the paper will now be published in both Traditional and Simplified Chinese and can be accessed from the http://www.cloudusecases.org site.
The Use Cases White Paper has become a solid resource eliminating much of the initial confusion surrounding Cloud Computing. Customer scenarios form the foundation of the Paper and showcase how Cloud Computing can be leveraged using real world examples. The development of the paper is an iterative process and each new version builds on the previous version as shown in the following topics:
– Cloud Computing Concepts
– Application Programming Interfaces (APIs)
– Developer Requirements
– Security in the Cloud
– Service Level Agreements (SLAs) is currently being developed
As with the Cloud Computing Use Cases, http://su.pr/2Be9pA, discussion group, the China Cloud Computing Use Cases discussion group will use an open community approach. To follow all current and future activities surrounding Cloud Computing Use Cases, a new site has been established called CloudUseCases.Org (http://www.cloudusecases.org).
We look forward to hearing your requirements Cloud Computing in China as we develop new versions of the Cloud Computing Use Cases White Paper.
DRussell4881 12000070EV 587 Visits
Today, a draft of the table of the contents was posted. Is there anything missing that should be included? Please post your responses on the Cloud Computing Use Cases discussion group at - http://groups.google.com/group/cloud-computing-use-cases?hl=en .
Proposed Table of Contents
2 Definitions and Taxonomy
2.1 Definitions of Cloud Computing Concepts
2.3 Relationships Between Standards and Taxonomies
2.4 Application Programming Interfaces (APIs)
2.4.1 Developer Roles
2.4.2 Levels of APIs
2.4.3 A Taxonomy of APIs
2.4.4 APIs and Portability
3 Use Case Scenarios
3.1 End User to Cloud
3.2 Enterprise to Cloud to End User
3.3 Enterprise to Cloud
3.4 Enterprise to Cloud to Enterprise
3.5 Private Cloud
3.6 Changing Cloud Vendors
3.7 Hybrid Cloud
4 Customer Scenarios
4.1 Customer Scenario: Payroll Processing in the Cloud
4.2 Customer Scenario: Logistics and Project Management in the Cloud
4.3 Customer Scenario: Central Government Services in the Cloud
4.4 Customer Scenario: Local Government Services in a Hybrid Cloud
4.5 Customer Scenario: Astronomic Data Processing
5 Conclusions and Recommendations
2.1 Definitions and Taxonomy:
- Add definitions of APIs, etc.
2.4 Application Programming Interfaces (APIs) [new section]
2.4.1 Developer Roles:
- The different kinds of developers and their concerns: Somebody using cloud storage has different concerns than someone wrangling VMs. Wil Sinclair's post of August 19th is a good starting point:
2.4.2 Levels of APIs:
- The four levels from the September 14th post:
2.4.3 A Taxonomy of APIs:
- The seven categories from the September 3rd post:
2.4.4 APIs and Portability:
- A discussion of portability, including the value of common APIs and the use of adapters to hide the differences between APIs and subclasses to expose the differences by extending the common APIs.
3 Use Case Scenarios:
- Add cross-referencing here that links each scenario to the appropriate categories of APIs. At the end of this section, add new tables to show the relationships between requirements and APIs, between the seven use cases and the seven categories of APIs, between developer roles and use cases, etc. (Basically anything to make this information easier to understand.)
4 Customer Scenarios:
- Add more scenarios to fill in the gaps of our discussion. Also add cross-referencing to link each scenario to the appropriate API information.
Look forward to your comments.
DRussell4881 12000070EV 1,062 Visits
The first stage of the journey is just about complete. The work effort started on June 1st and the final draft has been posted on July 31st ( right on target). What makes this initiative unique is that the whitepaper has come together using an open community approach. And even more interesting, feedback to the posting of the final draft is meeting with questions, what is next. Clearly this approach to the development of this whitepaper has been successful.
DRussell4881 12000070EV 408 Visits
On July 13th, the second draft of the Cloud Computing whitepaper was posted ( http
What has changed from the first draft :
We are still on target to be able to have a final draft ready to go by July 31st.
Check out the paper and add your comments where applicable.
DRussell4881 12000070EV 405 Visits
Cloud Coordination Press Release ? July 13th( http://news.prnewswire.com/DisplayReleaseContent.aspx?ACCT=104&STORY=/www/story/07-13-2009/0005058709&EDATE= )
OMG ( The Object Management Group ) announced a collaboration with leading technology Standards Development Organizations (SDOs) to coordinate and communicate standards for Cloud computing and storage. Organizations expected to participate in this round-table style collaboration include: the Distributed Management Task Force (DMTF), the Open Grid Forum (OGF), the Storage Networking Industry Association (SNIA), Open Cloud Consortium (OCC) and the Cloud Security Alliance (CSA).
The organizations involved have created a wiki to describe each organization's standards and efforts in this space. Each SDO has representatives that keep the wiki up to date. The URL is http://cloud-standards.org.
This is a major step forward and an example of progress towards the core principles of the manifesto ( http://www.opencloudmanifesto.org/Open%20Cloud%20Manifesto.pdf).
For more information of other activities supporting Cloud Computing - http://www.opencloudmanifesto.org/resources.htm
cloud presents tremendous opportunity and value for organizations, the usual IT requirements ( security, integration, and so forth) still apply. In addition, some new issues come about because of the multu-tenant nature ( information from multiple companies may reside on the same physical hardware ) of cloud computing, the merger of applications and data, and the fact that a company's workloads might reside outside of their physical on-premise datacenter.
In order to address the challenges and take advantage of the opportunities of Cloud Computing, the Cloud must be open.
A dialogue has already started to define the requirements for an Open Cloud Computing environment. The Open Cloud Manifesto ( http://www.opencloudmanifesto.org/ ) was published in late March 2009. To date there are over 250 companies supporting the Manifesto and in order to continue the dialogue on the Manifesto, a LinkedIn Group ( http://www.linkedin.com/groups?gid=1864064&trk=hb_side_g ) was established. Very quickly there were over 1000 LinkedIn members participating. However, the work has not stopped there. The Manifesto supporters were asked as to next steps on continuing the dialogue and there was consensus that a whitepaper detailing the various use cases in Cloud Computing be developed. In order to be responsive to the requests of the Manifesto community we needed to develop the whitepaper in a timely manner, we needed to have community input and in order to achieve those goals we needed to have a different approach to its development versus attempting to develop the paper in a very structured environment.
The Cloud Computing Use Case Whitepaper is being developed using inputs captured via a Google Group ( http://groups.google.com/group/cloud-computing-use-cases?hl=en ). Since June 1st, we have over 500 members who have joined and an initial draft of the paper was posted on July 2nd ( which is based on the inputs from the Google Group ). Our goal was to have a final draft of the whitepaper completed by July 31st and given the current progress we are on track to meet that date.
The paper is discusses multiple use cases with the initial set being:
End User to Cloud - In this scenario, an end user is accessing data or applications in the cloud.
Private Cloud - This use case is different from the others in that the cloud within the enterprise.
Changing Cloud Vendors - This use case involves using a different a different cloud vendor. Working with a different cloud vendor could mean leaving the current cloud vendor permanently, or it could be introducing another cloud vendor that would be used alongside the original vendor.
Cloud Broker -This use case involves an enterprise that resells, aggregates or federates cloud services without hosting those services themselves.
Federation - This use case involves data that is stored in different places and federated together for processing.
We invite the IT community to join the Cloud Computing Use Case Google Group ( http://groups.google.com/group/cloud-computing-use-cases?hl=en ) and participate by adding comments to the section which is relevant to your or your customers' requirements.