...
...
...
...
240.psi-mis.org
The main testing environment is already running at 240.psi-mis.org. The database on this environment is a copy of production, which we refresh based on the schedule below.
Refresh | DHIS2 version | Planned/ executed date | status | ||||||
|---|---|---|---|---|---|---|---|---|---|
Late Jan | v40.3 |
|
| ||||||
Refresh late April | v40.X ? |
|
| ||||||
Refresh late May | v40.4 ? |
|
| ||||||
Refresh mid June | v40.X ? |
|
| ||||||
DECOMISSIONING | n/a |
|
|
dev.psi-mis.org - development server
dev.psi-mis.org will be upgraded to 2.40 in preparation to the go live. If you have any configuration in 2.38 that you want to move to production, please do before mid June, otherwise you will have to wait until early July so you avoid version incompatibilities. Estimated upgrade date: .
data.psi-mis.org, replica.psi-mis.org [retire?]
the production server and its companion replica server will be upgraded after the full set of test is completed. Expected date .
The replica server may be retired - TBC.
clone.psi-mis.org
shortly after the successful upgrade of production (data), the clone environment, which contains a copy of production with most recent backup (last night), will become available. This could take 2 o 3 days after completing production upgrade) - estimated: .
staging.psi-mis.org
Shortly after upgrading production, the staging server DB will receive a fresh database from prod, and run v40. The staging server is used to test patch releases of DHIS2 or other changes before they are applied to prod - estimated: .
dhis.psi-connect.org - CWS testing server [retire?]
TBD - this server may be retired.
dev-mphd.psi-mis.org / mphd.psi-mis.org
Dates to be decided. Both servers will be upgraded to v40.
OR NOT - Do we need to preserve compatibility with MPHD MKA server?