Implement MP FT 2.1 release

[Emily-Jiang]

We plan to release FT 2.1 in Feb. We need to implement this feature. The list of issues to be included in FT 2.1 is here.

[atosak]

Feature Ship readiness issue: https://github.com/OpenLiberty/open-liberty/issues/10304

[tevans78]

Targeting beta in 20.0.0.2

[Emily-Jiang]

UFO: https://ibm.ent.box.com/file/598281977051

[atosak]

---

List of Steps to complete or get approvals / sign-offs for Onboarding to the Liberty release (GM date)

Instructions:

• Do the actions below and mark them complete in the checklist when they are done.
• Make sure all feature readiness approvers put the appropriate tag on the epic to indicate their approval.

---

TARGET COMPLETION DATE Before Development Starts or 8 weeks before Onboarding

• [ ] POC Design / WAD Review Scheduled (David Chang) or N/A.

• [ ] POC Design / WAD Reviewed (Feature Owner) or N/A.

• [ ] Complete any follow-ons from the POC Review.

• [ ] Design / WAD Approval (Alasdair Nottingham) or N/A.

• [ ] No Design / No WAD Approval (Arthur De Magalhaes - cloud / Alasdair Nottingham - server) or N/A.

• [ ] SVT Requirements identified. (Epic owner / Feature owner with SVT focal point)

• [ ] ID Requirements identified. (Epic owner / Feature owner with ID focal point)

• [ ] Create a child task of the epic entitled "FAT Approval Test Summary". Add and fill in the template as described here: https://github.ibm.com/was-liberty/WS-CD-Open/wiki/Feature-Review-(Feature-Test-Summary-Process)

• ---

  TARGET COMPLETION DATE 3 weeks before Onboarding

• [ ] Identify all open source libraries that are changing or are new. Work with Legal Release Services (Cass Tucker or Release PM) to get open source cleared and approved. Or N/A. (Epic Owner). New or changed open source impacts license and Certificate of Originality.

• ---

  TARGET COMPLETION DATE 3 weeks before Onboarding

• [ ] All new or changed PII messages are checked into the integration branch, before the last translation shipment out. (Epic Owner)

• ---

  TARGET COMPLETION DATE 2 weeks before Onboarding

• [x] Implementation complete. (Epic owner / Feature owner)

• [x] All function tests complete. Ready for FAT Approval. (Epic owner / Feature owner)

• [ ] Review all known issues for Stop Ship. (Epic owner / Feature owner / PM)

• ---

  APPROVALS with TARGET COMPLETION DATE 2 to 1 week before Onboarding

  Prereq: You must have the Design Approved or No Design Approved label on the GitHub Epic.

• [x] Accessibility - (G Scott Johnston). Accessibility testing is complete or N/A. Approver adds label focalApproved:accessibility to the Epic in Github.

• [x] FAT Liberty SOE - (Kevin Smith). SOE FATS are running successfully or N/A . Approver adds label focalApproved:fat to the Epic in Github.

• [x] Globalization (Sam Wong - Liberty / Simy Cheeran - tWAS). Translation is complete or N/A. TVT - complete or N/A. Approver adds label focalApproved:globalization to the Epic in Github.

• [x] ID - (Kareen Deen). Documentation work is complete or N/A . Approver adds label focalApproved:id to the Epic in Github.

• [x] Performance - (Jared Anderson). Performance testing is complete with no high severity defects or N/A . Approver adds label focalApproved:performance to the Epic in Github.

• [x] Serviceability - (Don Bourne). Serviceability has been addressed.

• [x] STE - (Swati Kasundra). STE chart deck is complete or N/A . Approver adds label focalApproved:ste to the Epic in Github.

• [x] SVT - (Greg Ecock - Cloud, Brian Hanczaryk- APS). SVT is complete or N/A . Approver adds label focalApproved:svt to the Epic in Github.

• [x] Demo - (Liberty only - Tom Evans or Chuck Bridgham). Demo is scheduled for an upcoming EOI. Approver adds label focalApproved:demo to the Epic in Github.

• ---

  TARGET COMPLETION DATE 1 week before Onboarding

• [ ] No Stop Ship issues for the feature. (Epic owner / Feature owner / Release PM)

• [ ] Ship Readiness Review and Release Notes completed (Epic owner / Feature owner / Release PM)

• [ ] Github Epic and Epic's issues are closed / complete. All PRs are committed to the master branch. (Epic owner / Feature owner / Backlog Subtribe PM)

• ---

  NOT REQUIRED FOR A FEATURE

• [ ] OL Guides - (Yee-Kang Chang). Assessment for OL Guides is complete or N/A.

• [ ] WDT - (Leonard Theivendra). WDT work complete or N/A.

• ---

  Related Deliverables TARGET COMPLETION DATE General Availability

• [x] Blog article writeup (Epic owner / Feature owner / Laura Cowen)

[NottyCode]

@Emily-Jiang the design link has expired. Can you update it please?

[Emily-Jiang]

@NottyCode My apologies for the short lived url! I have updated the link, which should not expire.

[chirp1]

From MP weekly scrum 3/6/20, no ID is needed. Approving.

[Azquelt]

@samwatibm This feature didn't introduce any new messages. Can we have the globalization approval?

[Azquelt]

@gscottj This feature only provides APIs, it doesn't have any UI. Is there anything further that you need to give accessibility approval?

[Azquelt]

Serviceability Approval Comment - Please answer the following questions for serviceability approval:

1. UFO -- does the UFO identify the most likely problems customers will see and identify how the feature will enable them to diagnose and solve those problems without resorting to raising a PMR? Have these issues been addressed in the implementation?

Yes

2. Test and Demo -- As part of the serviceability process we're asking feature teams to test and analyze common problem paths for serviceability and demo those problem paths to someone not involved in the development of the feature (eg. L2, test team, or another development team).
   a) What problem paths were tested and demonstrated? b) Who did you demo to? c) Do the people you demo'd to agree that the serviceability of the demonstrated problem scenarios is sufficient to avoid PMRs for any problems customers are likely to encounter, or that L2 should be able to quickly address those problems without need to engage L3?

We have not explicitly demoed problem paths for Fault Tolerance 2.1. However, this feature adds incremental improvements over Fault Tolerance 2.0, and the expected problem paths are the same.

3. SVT -- SVT team is often the first team to try new features and often encounters problems setting up and using them. Note that we're not expecting SVT to do full serviceability testing -- just to sign-off on the serviceability of the problem paths they encountered. a) Who conducted SVT tests for this feature? Brian Hanczaryk b) Do they agree that the serviceability of the problems they encountered is sufficient to avoid PMRs, or that L2 should be able to quickly address those problems without need to engage L3? Yes, SVT agrees that serviceability was sufficient to avoid PMRs or allow L2 to quickly address those problems.

4. Which L2 / L3 queues will handle PMRs for this feature? Ensure they are present in the contact reference file and in the queue contact summary, and that the respective L2/L3 teams know they are supporting it. Ask Don Bourne if you need links or more info.

PMRs will be handled by the Hursley Injection L3 team

[Azquelt]

@donbourne I pinched the serviceability questions from another epic and have answered them in the comment above. Please could you let me know if there's anything else needed for serviceability approval? Thanks.

[Azquelt]

Service Transfer Education: https://ibm.box.com/s/lytmtk892ncl1m1ixbwlejt7chbvdbo6

@skasund - if this is ok, can you add the STE approval? Thanks.

[skasund]

@Azquelt Thanks for the slides. I've approved this feature.

[donbourne]

approving for serviceability based on this just being an update to the API that don't add to the kinds of problems operator is likely to encounter.

[Azquelt]

Release blog has now been done here: #11505