Kitfox contact point - Volodymyr Kartsev
Here is the main tenant https://bugfest-orchid.int.aws.folio.org/
Tenant #2 https://bugfest-orchid-plus.int.aws.folio.org/
Tenant #3 https://bugfest-orchid-aqa.int.aws.folio.org/
Orchid BugFest preparation EPIC - BF-422 - Getting issue details... STATUS
Morning Glory Bugfest general info
Overall Orchid BF prep status
Outstanding tasks
Completed tasks
| # | Date | Action | Status | Description/Comments | Jira | Responsible Team |
|---|---|---|---|---|---|---|
| 0 | OKAPI token expiration - Check with CP → Oleksii Petrenko | |||||
| 1 |
| Prepare pre-orchid bugfest environment | DONE | BF-423 - Getting issue details... STATUS | Kitfox | |
| 2 |
| Pre-bugfest-clean-up | TO DO | 1) Circulation - tons of policies, locations, etc - Need to identify that is not used before deletion - Verify Jira tickets - Oleksii Petrenko 2) Inventory - Settings - Verify Jira tickets - Oleksii Petrenko 3) Verify data import 4) All requests should be closed and removed Reference data 5) Double check reference data related to ISBN - Ask Magda - BF-245 - Getting issue details... STATUS | Kitfox/DevTeams | |
| 3 |
| Clean up data Import jobs and most of the data import custom mapping and job profiles | TO DO |
Done in MG - BF-291 - Getting issue details... STATUS Just to double check for Orchid BF | ||
| 4 |
| Update the Inventory HRID prefix settings to reflect the Morning Glory release | TO DO | To minimize chances of problems with Inventory HRID settings, as of Morning Glory Bugfest, we will be adding the flower prefix to the HRID settings for Bugfest, increasing the start number, and then asking testers to ensure that any users they create for testing DO NOT have the permission: Settings (Inventory): Create, edit and delete HRID handling. | None | Ann-Marie Breaux |
| 5 |
| Remove stale permission sets from Settings > Users (Added by Erin Nettifee ) | IN PROGRESS | Discuss with Erin and Zak, FSE Schedule separate meeting or bring it up to POs meeting It would really help to clean up this list of test permissions, but it may be hard to identify what to cleanup If a permission set isn't assigned to any users, the permission set should be removed If a permission set is assigned to a user, but that user account is expired, the permission set should be removed If a permission set is assigned to a user, but the user account hasn't been modified in more than a year, the permission set should be removed | BF-444 - Getting issue details... STATUS | |
| 6 | Have historical data that could be affected by migration to simulate production upgrade | TO DO | Not to skip migration errors, not to delete records during migration | Kitfox | ||
| 7 |
| Deadline for wipe actions | TO DO | POs/Devteams | ||
| 8 |
| Trigger re-index | IN PROGRESS | BF-436 - Getting issue details... STATUS | Kitfox | |
| 9 |
| Enable RW split | TO DO | Kitfox | ||
| 10 |
| Update authority data application | IN PROGRESS | BF-436 - Getting issue details... STATUS | Kitfox | |
| 11 |
| Adjust data at new bugfest env → POs | IN PROGRESS | POs | ||
| 12 |
| Scripts are ready for new modules deployment: | DONE | BF-440 - Getting issue details... STATUS | Kitfox | |
| 13 |
| Create a data snapshot for Pre-Orchid | TO DO | BF-424 - Getting issue details... STATUS | Kitfox | |
| 14 |
| Prepare master branch for planform-complete with Orchid modules versions | TO DO | BF-425 - Getting issue details... STATUS | Kitfox | |
| 15 |
| Migrate Nolana env to Orchid Bugfest | TO DO |
BF-426
-
Getting issue details...
STATUS
| Kitfox | |
| 16 |
| Deploy new modules | TO DO |
BF-427
-
Getting issue details...
STATUS
| Kitfox | |
| 17 |
| Add the default permission sets and users (the ones in the hosted ref envs) | TO DO | BF-428 - Getting issue details... STATUS | Kitfox | |
| 18 |
| Verify permissions for existing users | TO DO | Discuss with CP | ||
| 19 |
| Deployment to Orchid bugfest env is competed. Data set is ready Snapshot will be used for Poppy bf env preparation | TO DO | These are the outstanding items that need to be verified/changed in bugfest-orchid env:
| BF-429 - Getting issue details... STATUS | Kitfox |
| 20 |
| Verify that Spitfire's script for Inventory storage update executed properly | TO DO | BF-441 - Getting issue details... STATUS | Kitfox | |
| 21 |
| Verify that modules configuration is updated in FSE branch | TO DO | BF-430 - Getting issue details... STATUS | Kitfox | |
| 22 |
| Create a data snapshot for Orchid | TO DO | BF-431 - Getting issue details... STATUS | Kitfox | |
| 23 |
| Turn emails on for Orchid Bugfest | BF-438 - Getting issue details... STATUS | |||
| 24 |
| Prepare and share links to MG BF logs | TO DO | How to get logs from MG bugfest environment (Logs are updated every 15 minutes)Couple of ways to access logs:
| BF-433 - Getting issue details... STATUS | Kitfox |
| 25 |
| Prepare sFTP access to Orchid BF env | TO DO | BF-434 - Getting issue details... STATUS | Kitfox | |
| 26 | - | Smoke test - Manual & Automated | Results: - | Oleksandr Bashtynskyi | ||
| 27 | 3 days - | POs check the Bugfest env | TO DO | POs | ||
| 28 |
| Tests claimed | TO DO | |||
| 29 |
| DB Schema comparison - | DONE | ticket is created in rally | FSE | |
| 30 |
| High Availability verification | TO DO | Discuss with Taras Spashchenko | DevTeams | |
| 31 |
| Re-index time measurement | TO DO | Denis Kovtun → Ask FSE | FSE | |
| 32 |
| Multi Tenant verification | TO DO | DevTeams | ||
| 33 |
| Migration from Nolana to Orchid time measuring → | TO DO | Please create ticket at Jira/Rally Denis Kovtun | ticket is created in rally | FSE |
| 34 |
| Prepare R1-2023 branch for planform-complete | TO DO | BF-442 - Getting issue details... STATUS | Kitfox | |
| 35 |
| Review release notes with DevOps (FSE + Community) and discuss deployment approach | TO DO | BF-439 - Getting issue details... STATUS | RM |