1 / 90

Workplace System Test, Build & Performance Status/Biweekly Report February 14, 2008

Workplace System Test, Build & Performance Status/Biweekly Report February 14, 2008. Build Summary for Notes/Domino & Extended Products pls update. Build Summary for Notes/Domino Extended Products and Unyte pls update.

soll
Download Presentation

Workplace System Test, Build & Performance Status/Biweekly Report February 14, 2008

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Workplace System Test, Build & PerformanceStatus/Biweekly ReportFebruary 14, 2008

  2. Build Summary for Notes/Domino & Extended Products pls update

  3. Build Summary for Notes/Domino Extended Products and Unyte pls update

  4. Build Summary for Expeditor, Mobile Connect, Notes Traveler, WECM & WEA pls update

  5. Build Summary for Portal/WCM, Quickr, Designer, Learning, Business Solutions pls update

  6. Summary of Products Built by Other pls update

  7. Highlights and Challenges: Build & Config-Mgmt Support pls update

  8. Interoperability Solutions Test Team pls update

  9. Interoperability Solutions Test Team (cont’d) pls update

  10. Quickr 8.1 Status pls update

  11. Quickr 8.1 SVT Status pls update • Accomplishments: • Execution ahead of schedule for Domino and J2EE, mainly due to utilizing borrowed resources • TAP: Completed reliability run on Domino Quickr Beta1 build, agreed planning for next run on Windows cluster. • First run on Linux cluster for J2EE – all J2EE runs on now attempted • First run on iSeries for Domino • First run of Quickr entry to be kicked off Wednesday • Successful run on Windows Single server with reduced memory leak. • Risks/Issues/Concerns: • Release recovery planning • Targeting 100% attempted by the end of Jan but at risk due to blocking defects. • Additional work for Lotus Quickr Content Integrator • TAP: Aligning our reliability runs with builds for TAP. • J2EE Reliability run failures on all configs (defect 201189) • AIX crash on Domino: SPR #CCLI79ZAXW • Availability of Domino developers during Lotusphere • Key Milestones/Upcoming Work: • IVT and Reliability Execution • Plan for covering Chinese new year with resources from Dublin • Input to release recovery planning

  12. Quickr Domino 8.1 Reliability Runs pls update

  13. Quickr J2EE 8.1 Reliability Runs pls update

  14. Quickr 8.1 TTT Charts pls update

  15. Quickr 8.1 SVT Defect Charts pls update • Overall builds have been stable and we are finding less defects than expected

  16. Quickr 8.1 SVT Defect Charts pls update

  17. Main Defects pls update

  18. Quickr Domino 8.1 – Performance Measurement Mohamed Bachiripls update • Updated LoadRunner scripts for 8.1 UI changes • Installed build QRD8.1_20071210.2200 & Domino 8.01 (from Domino 7.03 which was used with Quickr 8.002) • First run completed. Performance results show 8.002 and 8.1 have same capacity with no regression • Upgraded to build QRD8.1_20080101.0400  • Executed performance run again. Results: server Crash. SPR #LZHG7AP5F3. This crash happens at 700 concurrent users and 10 TPS. • Crash also happens with all these builds: • QRD8.1_20080108.2200QRD8.1_20080117.1150QRD8.1_20080117.2200 

  19. Quickr J2EE 8.0.0.2 & 8.1 Performance Status pls update

  20. Beta Green IBM Lotus Connections 2.0 Early Release program pls update Accomplishments & Goals • Hosted 2nd meeting to review current nominations to aid decisions for iteration 3 and provide customer information for Lotusphere attendees • Mailed nominators requesting more detail for customer goals for Connections. • Met with Diane Copenhaver to review dev contact points, and discussed topics and presenters for customer roll out. Assumptions • 3 design partners • 11 Early Program (7 new, 4 existing customers) • 10 Partners Dependencies: • Beta site requires license info Risks & Issues • Need to identify topics/presenters for Customer rollout. Note this falls shortly after LotusSphere. We may be able to utilize topics from there if appropriate. • *Forum is useable, waiting on Dev contacts to populate lists • Expectation is we'll receive more nomination post-Lotusphere

  21. 21 Lotus Connections Overall Release Status (SVT) pls update

  22. 22 LLotus Connections 2.0 Iteration 1 + 2 pls update

  23. 23 LC 2.0 SVT – IVT Status (Iteration 1 + 2 ) pls update

  24. 24 LC 2.0 SVT – Reliability Status (Iteration 1 + 2 ) pls update

  25. 25 Lotus Connections 2.0 (Iteration 1+2) - S Curve Status pls update Complete Status:Completed Attempts Status:Completed

  26. 26 LLotus Connections 2.0 Iteration 3 pls update

  27. 27 LC 2.0 SVT – Reliability Status (Iteration 3) pls update

  28. 28 LC 2.0 SVT – IVT Status (Iteration 3 ) pls update

  29. 29 LC 2.0 SVT – Automation Status pls update *A=Activities, B=Blogs, C=Communities, D=Dogear, P=Profiles, H=Homepage Achievements : • Sharing our scripts with the Lotus Connections FVT team. • Support for GVT Taiwan team - Shared our non-cluster installation scripts to them. Upcoming Work : • 2 Node Cluster installation for all Platforms • Upgrade Automation from Lotus Connections 1.02 -> 2.0 • Regression Automation

  30. Connections 2.0 Performance – Iteration 2 pls update Yellow Accomplishments & Goals • Blogs and Dogear scripts completed with iteration-2 feature functions. • 1.0.2 Integrated workload environment set up for baseline measurement. Upcoming Work • Execute Integrated workload baseline • Script communities • Script Homepage scenario • Follow up with Profiles development on build issues Issues/Concerns/Risks • Profiles builds continuosly broken • Majority of Activities feature functions not ready yet to script against 30

  31. Connections 2.0 Performance – Iteration 2 pls update Yellow Accomplishments & Goals • Data populations agreed upon with development and populating on blogs, communities and dogear Upcoming Work • Identify server in RTP for Oracle DB • Migrate DB2 DB’s to Oracle Issues/Concerns/Risks • Profiles builds continuosly broken 31

  32. Connections 2.0 Performance – Iteration 2 pls update Yellow Accomplishments & Goals Upcoming Work • Migrate DB2 DB’s to SQL Server Issues/Concerns/Risks • Profiles builds continuosly broken 32

  33. Lotus Sametime Advanced Server 8.0 – (Early Program) pls update Accomplishments • Ray is at Lotusphere this week • 13 customer downloads • Light feedback via forum. Expected due to Lotusphere • Pre-Req files bundled with beta1 images • Target beta1 delivered on Dec. 17th • “on premise” customers will be provided with re-requisite software • Target list of customers selected • Early Program Mgmt tool employed • Web pages updated to reflect Sametime Adv. 8.0 • Customer Targeted: • On Premise • Verizon • EY • GE • Connectria • 3M • Rohm & Haas • Dept of Defense • US Government (a.k.a CIA) • Greenhouse • Teradyne, • HSBC, • Federal Reserve of Cleveland • Thomson Multimedia • Genentech • Seagate

  34. Lotus Sametime Unified Telephony (SUT) 8.0 – (Early Program) pls update Accomplishments • Will provide customers with hardware/software turnkey offering • Still flushing out details for Early program activities • Key SUT Focus Areas: • Aggregated Telephony/IM presence • Incoming call management • Embedded softphone • PBX Integration • Click-to-call/click-to-conference Customers Targeted:

  35. Dependencies/ Schedule Status Issues/Risks/ Mitigation Plans Primary Owners: Tim Giambra 8.0 Advanced INTEROP pls update INTEROP: attempts: On time completes: One Day Ahead Last Week: • Clusters are initiated on all systems (Windows, AIX, Linux) • New severity 1 defect on Windows cluster • Reviewed testing with development, adding coverage on: • SSL (persistent chat and broadcast suite) • SSO (Siteminder and TAM: need development instructions) • LDAP configuration (during Install shield and post) Next 2 weeks: • Get clusters functional • Initiate cluster / failover test cases • Attempt clustering MQ/EB ATT=45%, COMP=34%, BLOCK/FAIL=22% Issues/Concerns • Unable to get a functional cluster: some SPRs addressed, still seeing issue: HSMH7B3MTN: installing the dmgr can't connect to db2 stadv db) • ECLD7AUMPS: Losing connection to broadcast server • DWOD7AWUK3: ST8adv location based services NLSSoapBindingImpl arguments don't match signature • Need development guidance on testing SSO (Siteminder / TAM) Risks & Mitigations • Performance Team for load tool / API Slide 35

  36. Dependencies Status Issues/Risks/ Mitigation Plans Primary Owners: Tim Giambra System Test RELIABILITY pls update RELIABILITY: attempts: 4 Days Behindcompletes: 4 Days Behind Last Week: • Manual persistent chat functions, workload attempted, potential issue with tool / defect • Location services tool development • Tool will generate two workloads: “where am I now” and “where was I” • “where am I now” tool written (now debugging) from unit test code, still need functional “where was I” Next 2 weeks: • Get persistent chat workloads running • Retry broadcast suite at higher levels • Start 1st pass all traffic workload • Complete location services workload tool • Target tool development is 1/22 • Target workload running against windows is 1/29 ATT=37%, COMP=24%, BLOCK/FAIL=32% Issues/Defects: • Need all cluster configurations complete • Persistent chat functions manually, load tool does not: debugging • Need locations services tooling fully functional Risks & Mitigations • Performance Team for load tool / API Slide 36

  37. [ST 8.0] – [Status Date 1/21/08] pls update Slide 37

  38. [ST 8.01] – [Status Date 1/21/08] pls update Accomplishments/Status • SVT focus will be on 3 areas: 1. Client memory in Citrix server • Configuration: Citrix server hosting approximately 40 Sametime clients • Drive clients with Rational Functional Tester • Validate functionality and memory usage on Citrix server 2. Five day Reliability run on Windows 2003 Enterprise Edition with 8 GB of RAM 3. Some basic SPR validation (note SVT will NOT setup Gateways in RTP, any Gateway validation will be done on Rehovot or other systems) Issues and Concerns Dependencies Slide 38

  39. [ST 8.0 SUT] – [1/21/08] pls update Sametime SUT SVT Team Status Accomplishments/Status • Developing resource requirements (Ogle) • Target first draft test plan is 1/31/08 Issues and Concerns Tools: - We need to determine how to drive simulated client workload Staffing: - Need 7-8 people in addition to the required head count for ST 8.5, ST maintenance, and other 2008 ST SVT requirements Hardware / Configurations: - Need to determine exact configurations and platform coverage (proposed matrix below) - Need to determine range of PBXs we will test with - Need requested capital dollars to cover required hardware / PBXs Dependencies • 8.0 Advanced must complete on time • Support from Siemens as needed Slide 39

  40. IBM Gateway Pilot – [Status Date 1/7/08] pls update Carol Talton, Dave Curley, Ivan Dell’era Accomplishments/Status All components are in place. An email has been sent to the first 200 users telling them about the pilot and what their passwords are for the pilot. Dependencies Road Blocks Encountered: Problems with the IBM Blue client - Workaround given to customer. Problem with missing chat data reported to Dev. Current debugging in progress Other IBM Gateway Testing: No Change in Status Slide 40

  41. Sametime Performance – Mohamed Bachiri pls update • ST 8.0: • Performing measurements on 8.0 gold for benchmark report. • Web Conferencing: discovered another Domino performance problems - Web Conferencing scenario 2 (multiple 5 person meetings) • Working with Domino dev to resolve

  42. ST 8.0 Advanced – Mohamed Bachiri pls update General Status: • We were blocked by performance bottleneck on WAS app server DB2 server. • Received WAS app server code changes from development team on 1/18. • Drastic improvement experienced in the Persistence chat scenario workload. Ran 20 hours workload with 800 Virtual Users (246,000 chats initiated). Can do a lot more. • Now working on the Broadcast suite scenario workload. • Presently blocked by a JMS memory limitation issue (Event Broker is limited by ½ GB independent of settings). Need Event Broker expertise. List of performance Issues resolved so far: • (1/04/08) - Log-in issue resolved with system tuning • (01/10/08) - Excessive DB2 CPU utilization resolved with DB2 indexes • (01/10/08)Server Connections issue resolved with HTTP server tuning • (01/21/08)8: Excessive CPU usage on WAS and DB2 CPU improved with code changes and DB2 indexes.

  43. ST Unyte– Mohamed Bachiri pls update • Completed Performance plan • Scenarios to measure: • Scenario 1 • Maximum number of users in a single meeting. • Scenario 2 • Maximum number of meetings on a single server. • Scenario Variations • Publish mode (exclusively) • Application Share mode (exclusively) • Waiting for Unyte development team to get free time to initiate contact • Started doing network traces to understand client/server interactions

  44. Performance Objectives: Sametime Unified Telephony – Mohamed Bachiri pls update Empirix Hammer tool: • Empirix made a demo of the product in Westford on 1/18 • Getting an evaluation license and 2nd demo on 1/18

  45. SUT - High Level Architecture – Mohamed Bachiri pls update Telephony Application Server Sametime Server Telephony SDK (VP, REST, RTC4Web, Web Services) Sametime Client TCSPI Adapter Presence Adapter Communications Adapter Telephony Plug-ins SIP Proxy / Registrar OpenSOA Presence Aggregation Workflow Soft Phone BComm Telephony Control Server HiPath 8000 (ONS Server) SIP B2BUA CSTA Existing IBM Components New IBM Components Telephony Gateway Siemens PBX IP-PBX Siemens Components External Telephony Equipment

  46. Portlet Factory v61 (SVT) pls update 46 46 46 46

  47. Portlet Factory – Performance Mohamed Bachiri pls update • New test application being used for Portlet Factory (with more portlets, more code coverage)‏ • LoadRunner script completed • Started execution of workloads to compare performance of (6.0.2.1and 6.0.2) builds • Memory consumption of session data on Java heap is similar. See next chart.

  48. Portlet Factory – Performance Mohamed Bachiri pls update

  49. Green Portal 6.0.1.3 Performance pls update

  50. Portal 6.1 SVT pls update

More Related