HP SaaS Migration
-
Upload
hp-software-solutions -
Category
Documents
-
view
1.433 -
download
1
description
Transcript of HP SaaS Migration
©2010 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice
Session ID: BTO-TU-1800-5 Twitter hashtag #HPSWU
©2010 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice
Speaker Name: Vijay Dahad, Environment Manager, Alcatel-Lucent
Mathieu Ayel, HP SaaS ProductsDate: 30th November 2010Session ID: BTOT-TU-1800-5
HP SaaS MigrationSeamless transitioning from on-premise Quality Center to QC on HP SaaS
The HP and Alcatel-Lucent alliance
3
1 2 3OEMITO JGTM
Joint go-to-market (JGTM)
Leading the convergence of IT and Communications to enable business transformation
Software Universe Communications WorldData Center &
Networking Transformation and Enterprise Communications: Booth A2
– Business Breakout Session: Unified Communications & Collaboration (UC&C): Join the next decade
– Technical Breakout Session: UC&C: Why other vendors have failed
Differentiate your cloud services offerings: Booth M4
– Breakout session: Transformation and Growth Through Cloud Services
HP and Alcatel-Lucent at Software Universe and Communications World
4
5 HP Confidential
Why move to HP SaaS?
– Enhanced support for the business:• Experience faster time to benefit from new features in latest version
• Improve support to global teams by minimizing downtime
• Overcome challenges of providing access globally and externally
– Maintaining on-premise instance requires a lot of effort and resources
– Cost effective way to upgrade to latest version
6 HP Confidential
Challenges faced at Alcatel-Lucent
– Large number of projects to be migrated
– Huge repository size
– Demanding project schedules required downtime be kept to a minimum
– Added complexity due to:• Migration to HP SaaS
• Upgrade from QC9.2 to QC10
7 HP Confidential
Essentials of a Successful Migration
– Planning
– Pilot
– Communication
– Minimize issues for a smooth migration• Ensure no loss of data
• Ensure no loss of access
• Minimal downtime
• Work on prevention of issues rather than resolving issues later
Key Tasks
8 HP Confidential
1. Analyze reports from existing instance 2. Conduct housekeeping on in-house instance 3. Identify project level and location based administrators
4. Identify & document possible issues and the resolutions
5. Plan internal communications
6. Define migration plan
Analyze Reports
9 HP Confidential
– Overall license usage report
– Project license usage to determine the priority for migration• Inactive Users
• Inactive Projects
10 HP Confidential
– Delete inactive users
– Delete other data not in use
Housekeeping on in-house instance
11 HP Confidential
Administrators
– Identify project level administrators
– Identify location based administrators
– Administrator should be made aware of:• The detailed plan
• Possible issues and resolutions
Internal Communication Plan
12
Sun Mon Tue Wed Thu Fri Sat
1 2 3 4 5 6
7 8 9 10 11 12 13
14 15 16 17 18 19 20
21 22 23 24 25 26 27
28 29 30 Migration!
1st
3rd
2nd
November, 2009
4th
HP Confidential
Phased ApproachMigration Plan
13 HP Confidential
1. Pilot 2. Real Migration
3. Verificatio
n
4. Handover
Pilot PhaseMigration Plan
14 HP Confidential
− Select a project for a pilot migration− Ensure the project has all type of data e.g. Defect Links,
Custom Fields− Verify any integrations like QTP, RequisitePro− Confirm that there is no loss of data once the migration is
completed
Real Migration PhaseMigration Plan
15 HP Confidential
− Grouping the projects into priority groups− Set priority sequences within each group
Real Migration Phase cont’ Migration Plan
16 HP Confidential
− Internal communication to download & install new version of QC Client to save time
− User migration on the day of migration
− Migrate Repository 1 week before the migration day
− Delta of the repository on the day of migration
− Project Databases migration on the day of migration
− Verification by internal team after migration completion; before it was made open to all
− In case of any issues with migration, in the worst case; the in-house instance could be started and migration rescheduled
Real Migration Phase cont’ Migration Plan
17 HP Confidential
– We used new phased approach to repository migration
One week delta of repository on the migration
day
Full Repository a week before
migration day
– This was a huge success with the migration completed a day ahead of schedule !!!
18 HP Confidential
Issues Encountered
– An interesting issue to share…• Initial slow performance on our HP SaaS QC instance
• Everything looked ok on both HP and Alcatel-Lucent side, yet the access was still slow
– Ultimate finding & resolution• Problem caused by the string “alcatel” in our HP SaaS QC URL
• Our firewall was treating this as an internal url, causing a delay in reaching the external URL
19 HP Confidential
Lessons Learned / Recommendations
– More internal communications to describe the changes in new version
– Internal communication – common issues and resolutions
– Two way call support for initial 2 months; especially as there were few known issues with QC10 (memory leak)
– The MORE you plan the EASIER it is!
20 HP Confidential
Benefits of QC10
– Reporting Dashboard• Integrated tool
• Simple to use
• Real-time data
– Improved Requirements Management
– Version Control
– Template Management
21 HP Confidential
Benefits of moving to HP SaaS
– Easy upgrade to the latest and greatest
– Globally Accessible
– Great support for global and diverse team
– QC on SaaS Admin Console
– Responsiveness of HP SaaS teams
Focus on your business: let us take care of running the
tools you need
HP ALM 11 is here – HP SaaS canhelp you get there quicker
Continue the conversation with your peers at the HP Software Community hp.com/go/swcommunity