Skip to content

Commit 08cc7d7

Browse files
committed
Document Met Office site deployment result
1 parent 39acf75 commit 08cc7d7

1 file changed

Lines changed: 27 additions & 0 deletions

File tree

docs/research/new-publisher-source-planning/Met_Office_Exeter_Portsmouth_Demo_Site_Check_2026-05-26.md

Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -79,3 +79,30 @@ For Global Spot, the same curated point labels and coordinates are added as virt
7979
Adding two Land Observations locations increases the default Met Office Land Observations cycle from 3 to 5 locations. With geohashes cached in config, the publisher should make one observation endpoint request per location per cycle, still far below the documented 360 calls/day free-plan limit at hourly cadence.
8080

8181
The Global Spot default set also increases from 3 to 5 locations. At one hourly forecast API request per location per hour, the default operational cadence is about 120 calls/day, still below the documented 360 calls/day free-plan allowance.
82+
83+
## Oracle Deployment Result
84+
85+
Commit `39acf75` (`Add Exeter and Portsmouth Met Office demo points`) was pushed and deployed to the Oracle Met Office Land Observations service copy.
86+
87+
Deployment actions completed:
88+
89+
- Updated durable checkout `/home/ubuntu/oshconnect-python-publishers` to `39acf75`.
90+
- Copied the expanded `publishers/met_office_datahub/stations.json` into `/home/ubuntu/met-office-datahub-publisher`.
91+
- Ran the idempotent Met Office Land Observations bootstrap with existing host-local service credentials.
92+
- Created two new systems:
93+
- `urn:os4csapi:system:met-office-datahub-land-observations:exeter-airport-area:v1` -> server id `05q0`
94+
- `urn:os4csapi:system:met-office-datahub-land-observations:portsmouth-thorney-island-area:v1` -> server id `05qg`
95+
- Created 18 new datastreams, 9 per new location.
96+
- Created two new deployments:
97+
- `urn:os4csapi:deployment:met-office-datahub-land-observations-exeter-airport-area:v1` -> server id `05ng`
98+
- `urn:os4csapi:deployment:met-office-datahub-land-observations-portsmouth-thorney-island-area:v1` -> server id `05o0`
99+
- Ran a dry publish cycle for only the two new stations: 0 errors.
100+
- Ran one live publish cycle for only the two new stations: 18 observations published, 0 errors.
101+
- Restarted `met-office-datahub-publisher.service`; it loaded all five stations and remains active.
102+
103+
Public CSAPI verification after deployment:
104+
105+
- Exeter Airport Area system `05q0` has 9 datastreams. Latest air temperature observation: `26.73 C` at `2026-05-26T18:00:00Z`.
106+
- Portsmouth / Thorney Island Area system `05qg` has 9 datastreams. Latest air temperature observation: `25.54 C` at `2026-05-26T18:00:00Z`.
107+
108+
Known follow-up: service restart logs still show the pre-existing Cairngorm datastream-list JSON parse fallback, and that fallback currently resolves only two Cairngorm datastreams for scheduled cycles. The new Exeter and Portsmouth sites are unaffected and resolved all 9 datastreams each. Treat the Cairngorm warning as a separate service-hardening item rather than part of this site addition.

0 commit comments

Comments
 (0)