Line 3: |
Line 3: |
| {| class="wikitable" | | {| class="wikitable" |
| |+ | | |+ |
− | Last Updated: September 30, 2019 | + | Last Updated: October 3, 2019 |
| !RI | | !RI |
| !Scope | | !Scope |
Line 19: |
Line 19: |
| |[https://ecollab.ncr.int.ec.gc.ca/theme/pnp-npp/priv/RI/RIAdmin/RI25.0-Scope.docx NinJo 3.4 (WPR1.5, Tsunami) + Scribe] | | |[https://ecollab.ncr.int.ec.gc.ca/theme/pnp-npp/priv/RI/RIAdmin/RI25.0-Scope.docx NinJo 3.4 (WPR1.5, Tsunami) + Scribe] |
| |RI25. 0-part1: September 24, 2019 (excluding NinJo 3.4). Deployment completed. | | |RI25. 0-part1: September 24, 2019 (excluding NinJo 3.4). Deployment completed. |
− | RI25. 0-part2: NinJo 3.4: DELAYED until November 13, 2019 | + | RI25. 0-part2: NinJo 3.4: November 13, 2019 |
| |RI25.0-part1 deployment completed. | | |RI25.0-part1 deployment completed. |
| | | |
| RI25.0-part2 is ready for deployment but is dependant on the 18.04 IFW being deployed first. | | RI25.0-part2 is ready for deployment but is dependant on the 18.04 IFW being deployed first. |
| |Testing completed. | | |Testing completed. |
− | |Synopsis: RI25.0-part1 (Scribe. WxO, WeatherCAN, DMS) was deployed on September 24. | + | |Synopsis: RI25.0-part1 (Scribe. WxO, WeatherCAN, DMS) was deployed on September 24. RI25.0-part2 (NinJo 3.4) is certified for deployment but is waiting for 18.04 IFW deployment to be completed. |
| | | |
− | RI Notes: RI25.0-part2 (NinJo 3.4) is delayed given delay in 18.04 IFW deployment. | + | RI Notes: RI25.0-part2 (NinJo 3.4) deployment date is at risk of further delays as it is dependant on 18.04 IFW deployment. |
| | | |
| . | | . |
Line 44: |
Line 44: |
| |- | | |- |
| |'''{{colour|green|25.1}}''' | | |'''{{colour|green|25.1}}''' |
− | |Aviation Changes | + | |[https://ecollab.ncr.int.ec.gc.ca/theme/pnp-npp/priv/RI/RIAdmin/RI25.1-Aviation-Scope.docx Aviation] |
| |October 10, 2019 | | |October 10, 2019 |
| |1. wxapps-beta testing: Sep 25-Oct 2, 2019 | | |1. wxapps-beta testing: Sep 25-Oct 2, 2019 |
Line 68: |
Line 68: |
| |[https://ecollab.ncr.int.ec.gc.ca/theme/pnp-npp/priv/RI/RIAdmin/RI25.X-URP2_13_2-Scope.docx URP 2.13.2] | | |[https://ecollab.ncr.int.ec.gc.ca/theme/pnp-npp/priv/RI/RIAdmin/RI25.X-URP2_13_2-Scope.docx URP 2.13.2] |
| |Oct 29, 2019 | | |Oct 29, 2019 |
− | |Package submission: Sep 30, 2019 | + | |1. Beta/Integration: now - Oct 11 |
− | 1. Beta: now - Sep 30 | + | 2. UAT: Oct 14 - 25 |
− | | + | |1. NTTO/URP dev team |
− | 2. Integration: Oct 1 - 11
| + | 2. PSD |
− | | |
− | 3. UAT: Oct 14 - 25
| |
− | |1. URP dev team | |
− | 2. NTTO | |
− | | |
− | 3. PSD
| |
| |a. Removal of all decommissioned C and X-bands | | |a. Removal of all decommissioned C and X-bands |
| b. Promotion of the remaining S-bands to Primary for SWP | | b. Promotion of the remaining S-bands to Primary for SWP |
| |1. RI Planning/Scoping/Components: Development is on track. | | |1. RI Planning/Scoping/Components: Development is on track. |
− | 2. RI Testing: Will be conducted on CMC urpx dev1 servers. | + | |
| + | 2. RI Testing: Beta/Integration testing in progress on CMC urpx dev1 servers. |
| | | |
| 3. RI Deployment: TBD | | 3. RI Deployment: TBD |
Line 92: |
Line 87: |
| |'''{{colour|red|25.X}}''' | | |'''{{colour|red|25.X}}''' |
| |[https://ecollab.ncr.int.ec.gc.ca/theme/pnp-npp/priv/RI/RIAdmin/IFWUU-Scope.docx IFW Ubuntu Upgrade (IFWUU)] | | |[https://ecollab.ncr.int.ec.gc.ca/theme/pnp-npp/priv/RI/RIAdmin/IFWUU-Scope.docx IFW Ubuntu Upgrade (IFWUU)] |
− | |**DELAYED** Completed by the week of Oct 28-31, 2019 | + | |Completed by the week of Oct 28-31, 2019 |
| + | <nowiki>**</nowiki>AT RISK OF FURTHER DELAY** |
| |Live UAT in progress on 18.04 IFW's (ops01/cmac01) | | |Live UAT in progress on 18.04 IFW's (ops01/cmac01) |
| |All forecasters | | |All forecasters |
| |Synopsis: Upgrade of IFW from Ubuntu12.04 to 18.04. Includes renaming of all IFW's according to new national SSC standard and 18.04 release of URP-IV (to accommodate 6 minute S-band data). | | |Synopsis: Upgrade of IFW from Ubuntu12.04 to 18.04. Includes renaming of all IFW's according to new national SSC standard and 18.04 release of URP-IV (to accommodate 6 minute S-band data). |
| | | |
− | RI Notes: Blocker display issues have resulted in delay of deployment. SSC are dedicating significant resources in an attempt to resolve these display issues. NTTO are meeting weekly with RI managers and PSH to provide updates and discuss issues. | + | RI Notes: Blocker display issues continue to pose a risk of further delays. SSC are dedicating significant resources in an attempt to resolve these display issues. NTTO are meeting weekly with RI managers and PSH to provide updates and discuss issues. |
| |1. RI Planning/Scoping/Components: | | |1. RI Planning/Scoping/Components: |
| - Upgrade 12.04 IFW to KDE 18.04. | | - Upgrade 12.04 IFW to KDE 18.04. |
Line 107: |
Line 103: |
| - 18.04 release of URP-IV (2.4.0) client to accommodate 6 minute S-band data. [http://msc-mantis.to.on.ec.gc.ca/mantis/view.php?id=19693 19693]. | | - 18.04 release of URP-IV (2.4.0) client to accommodate 6 minute S-band data. [http://msc-mantis.to.on.ec.gc.ca/mantis/view.php?id=19693 19693]. |
| | | |
− | 2. RI Testing: Live UAT in progress. | + | 2. RI Testing: Live UAT in progress. |
| | | |
| 3. RI Deployment: Blocker display issues have resulted in delay of deployment. SSC are dedicating significant resources in an attempt to resolve these display issues. NTTO are meeting weekly with RI managers and PSH to provide updates and discuss issues. SSC estimates it will take 1-2 hours to complete upgrade each IFW. The plan is to upgrade 2 IFW's at a time per office but multiple offices can be updated at the same time. | | 3. RI Deployment: Blocker display issues have resulted in delay of deployment. SSC are dedicating significant resources in an attempt to resolve these display issues. NTTO are meeting weekly with RI managers and PSH to provide updates and discuss issues. SSC estimates it will take 1-2 hours to complete upgrade each IFW. The plan is to upgrade 2 IFW's at a time per office but multiple offices can be updated at the same time. |
Line 247: |
Line 243: |
| '''2.''' RI Testing: TBD | | '''2.''' RI Testing: TBD |
| | | |
− | '''3.''' RI Deployment: The new servers will be hosted on VM containers. | + | '''3.''' RI Deployment: The new servers will be hosted on VM containers.- Data feeds to be handled by Sarracenia |
− | - Data feeds to be handled by Sarracenia | + | |
| - All applications and configurations to be deployed to servers via Debian packages. | | - All applications and configurations to be deployed to servers via Debian packages. |
| + | |
| - Incoming model data and processing to be standardized | | - Incoming model data and processing to be standardized |
| + | |
| - Ensure that current contingency plans are carried over to the new configuration | | - Ensure that current contingency plans are carried over to the new configuration |
| + | |
| '''4.''' RI Dependencies: Edigraf is dependent on forecast model fields. SPI (software at CMC) will be replacement for MAX. MSI (Multi Spectral Imagery) will be generated at CMC (migrated from local offices). | | '''4.''' RI Dependencies: Edigraf is dependent on forecast model fields. SPI (software at CMC) will be replacement for MAX. MSI (Multi Spectral Imagery) will be generated at CMC (migrated from local offices). |
| | | | | |
Line 339: |
Line 338: |
| |Scribe packages: February 21, 2020 (for Beta) | | |Scribe packages: February 21, 2020 (for Beta) |
| NinJo packages: March 25, 2020 (for Integration) | | NinJo packages: March 25, 2020 (for Integration) |
| + | |
| Beta: Feb 26-March 18, 2020 | | Beta: Feb 26-March 18, 2020 |
| + | |
| Integration: March 30-April 28, 2020 | | Integration: March 30-April 28, 2020 |
| + | |
| UAT: May 7-14, 2020 | | UAT: May 7-14, 2020 |
| |1. FSII only. CMAC for TAF Editor. | | |1. FSII only. CMAC for TAF Editor. |
− |
| |
| 2. 1 (2d) | | 2. 1 (2d) |
| | | |
Line 349: |
Line 350: |
| |Synopsis: NinJo 4.3 (TAF Editor) + Scribe | | |Synopsis: NinJo 4.3 (TAF Editor) + Scribe |
| | | |
− | RI Notes: Full deployment and operational activation of TAF Editor (including integration of autoTAF data into TAF Editor). | + | RI Notes: Full deployment and operational activation of TAF Editor (including integration of autoTAF data into TAF Editor). |
| |1. RI Planning/Scoping/Components: NinJo 4.3 + Scribe. Full deployment and operational activation of TAF Editor (including integration of autoTAF data into TAF Editor). | | |1. RI Planning/Scoping/Components: NinJo 4.3 + Scribe. Full deployment and operational activation of TAF Editor (including integration of autoTAF data into TAF Editor). |
− |
| |
| 2 Testing: TBD | | 2 Testing: TBD |
| | | |