CWRU ITS Project Definition
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

CWRU ITS Project Definition

on

  • 410 views

 

Statistics

Views

Total Views
410
Views on SlideShare
410
Embed Views
0

Actions

Likes
0
Downloads
0
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

CWRU ITS Project Definition Document Transcript

  • 1. CWRU ITS Project Definition Project Name: Cisco iSCSI Test/Pilot A. Purpose and Goals: 1. Define the business problem or opportunity being addressed. 2. Describe in broad terms how it will be addressed. 3. Identify which divisional strategic objectives will be supported by this effort. 4. Identify any related goals or deliverables that are outside the scope of this project. 5. List the outcomes that would indicate successful project completion. 1. The existing Fibre Channel SAN (storage area network) can not be accessed from outside of the data center without building an expensive Fibre Channel infrastructure in parallel with the existing IP network. Use of iSCSI is expected to provide that access by leveraging the existing gigabit environment. If we don’t leverage the existing gigabit environment, we could lose the ability to make central storage available to a large amount of servers and we need to make the storage available to as many systems as possible. 2. This project is a pilot which is intended to determine whether iSCSI provides all of the functionality and performance needed to enable SAN applications over an iSCSI network instead of Fibre Channel. The pilot project will encompass testing of the primary server platforms used by CWRU ITS. • Solaris • Windows 2000 and • Linux 3. Infrastructure and access 4. The actual implementation of iSCSI is outside the scope of this project. It will take place internally if this test/pilot project is successful. There are also many external potential users of this technology. These include making network storage available to ATC partners and facilitating an implementation of a remote storage at a disaster recovery site. 5. Success of this project would be indicated when the Solaris, Windows 2000, and Linux servers are successfully using SAN storage via iSCSI, both in the data center and remote locations on campus. The use of SAN storage via iSCSI would be verified with system utilities and running typical applications on the test systems. E.g. Oracle, SQL, and streaming video. The successful testing will also include demonstrating full interoperability with EMC Clariion and Connectrix Fibre Channel switches. B. Basic Plan: 1. List the major project phases and their deliverables, including important project milestones.
  • 2. 2. Describe how the project will be integrated into ongoing operations, what support will be required, and what involvement the support and operations staff will have throughout the project. 1. Phase 1 - Hardware installation, configuration, and basic interoperability with EMC Clariion Phase 2 - Install and configure host operating system drivers Phase 3 - Establish interoperability with EMC Connectrix DS16-B2 switches Phase 4 - Final evaluation and conclusions Deliverables include: • The working systems, Solaris windows, etc. • The documentation that is produced at the end in terms of evaluation and conclusion. • Enhanced knowledge and skills gained by ITS staff Milestones include: • Connectivity between iSCSI switch and storage array • Establish connectivity between Clariion storage array and iSCSI host • Conclude successful application testing and • Establish the connectivity between Connectrix switches and Cisco switch 2. This project won’t be integrated into operations, except to the extent needed to test it for successful conclusion of this project. Support will not be required for this test/pilot project. C. Customers and Stakeholders: 1. Who are the project’s customers and what are their needs and expectations? 2. What important customer-specific issues must be addressed? 3. Who are the other stakeholders and how will this project impact them? 4. List the steps that will be taken during the course of the project to communicate with customers and other stakeholders. 1. There are no users in the test/pilot project. Technical architecture is this project’s customer. Technical architecture needs this pilot to prove the viability of iSCSI technology and its capability to provide remote SAN access without extending the existing Fibre Channel infrastructure. 2. The important issue is establishing technical functionality (does it work or not) and an operational validation. Is this something we can or want to use in the long term environment? 3. The intention is to reduce cost of access to the SAN and make the technology financially viable. Connecting ATC partners would probably be cost prohibitive unless this works. CWRU ITS has many potential customers/partners that are CWRU ITS Project Definition 20021216 Page 2 May 23, 2003
  • 3. very limited unless this works. Its primary purpose is internal but ITS has a stake hold in CWRU partnerships. Cisco is also a stakeholder; their primary purpose is to evaluate the hardware and software. 4. Communication will be provided in the ongoing project updates with ITS management and the Cisco project engineers. D. Required Schedule: 1. When must implementation be completed? 2. When must all post-implementation tasks be finished? 3. List the required completion dates for any deliverables that are needed for other projects or activities. 4. When must this project begin in order to meet these deadlines? 1. This project realistically depends on equipment and staff resource loans from Cisco. End of June 2003 is the expected completion date to be done with technical parts of the test. 2. There is no immediate need to begin the implementation. There is enough Fibre Channel to meet our internal needs for the next year. Once the technical goals are achieved and if we achieved our financial goal, we will evaluate the potential TCO for the next project. How quickly we do the financial wrap up and move into the TCO for next project depends on financial resources and needs driven by external users. 3. TBD 4. This project must begin April 21 2003. E. Required Resources: 1. What resources (people, capital, and expenses) are needed to produce the required deliverables by the due dates? 2. Describe any outside resources that will be required. 1. Hardware is being supplied by Cisco. ITS needs ¼-1/2 time of a FTE for duration of the project. 2. Technical resources are being supplied by Cisco for engineering and support staff. Cisco is providing the loaner hardware and staff resources because this is a beta project. F. Project Issues, Assumptions, and Interdependencies: 1. What significant issues must be resolved for this project to succeed? 2. List any major assumptions made when formulating how project goals will be met. 3. How do other current or anticipated projects affect this project? 1. There is a technical issue of interoperability between Cisco switch, the EMC Clariion, and the Connectrix switches. Establishment of high bandwidth fault tolerance to IP network. Does it work or not. The implementation project that follows will depend on the finishing core and backbone portions of the ITP CWRU ITS Project Definition 20021216 Page 3 May 23, 2003
  • 4. upgrade. 2. • There will be staff availability • Everything will work 3. Completion of ITP is required for this technology to be viable and the production implementation of iSCSI depends on this project. G. Major Risks: 1. Identify significant project risks. 2. Explain how you plan to manage each of these risks. 1. The production SAN is being used to provide storage for this project. This creates a potential impact on production applications. If anything goes wrong, service on the SAN could be interrupted. 2. Keep the test systems and data isolated to as great an extent as possible, using whatever appropriate methods are available. E.g. Using separate hardware connections and the test components should only be connected to half of the production system where available. H. Accountability and Management: 1. Identify the person who is responsible for this project, and will drive it to completion. 2. Identify the person who will manage the day-to-day project activities (if different from the person who is accountable). 1. Jim Nauer 2. CWRU ITS Project Definition 20021216 Page 4 May 23, 2003