Automatic OVHcloud Maintenance Impact Alerts
Every morning, WebRun opens OVHcloud, lists the services and servers on your account with their datacenter locations, reads the published maintenance and incident notices, matches them to your own kit, opens a Trello card for each affected service, and files a dated notice summary in Google Drive.
How do I know which of my servers are affected by scheduled maintenance?
WebRun matches OVHcloud maintenance notices to your own servers every morning. It lists your services and their datacenter locations, reads the published maintenance and incident notices, and works out which of your kit is affected. Each match becomes a dated Trello card and the record is filed in Google Drive, so customers get warned before the reboot.
- You learn a window affects your kit before it starts, not after
- Each affected service gets a dated card in the maintenance backlog
- Recurring maintenance on one datacenter becomes visible over time
Built for sysadmins · hosting resellers · DevOps teams · managed service providers
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
www.ovhcloud.comin a real browser with your saved login - no setup, no API keys. -
1
OVHcloud - match notices to your servers
ovhcloud.com
WebRun opens OVHcloud to match notices to your servers. - Open your OVHcloud account and list the services and servers you run, with their datacenter locations
- Read the published scheduled maintenance and incident notices
- Match each notice to the services it touches, by location and by service type
- Capture the maintenance window, the expected impact, and the reference for each match
- Skip notices already actioned on a previous run
Done when Every open notice is matched against your own services or dismissed.
-
2
Trello - open a card per affected service
trello.com
WebRun opens Trello to open a card per affected service. - Open a Trello card for each of your services sitting behind an announced window
- Put the maintenance window, the expected impact, and the service name on the card
- Set the card due date to the start of the window so it surfaces in time
- Close cards for windows that have passed or notices that were withdrawn
Done when Every affected service has a dated Trello card.
-
3
Google Drive - file the maintenance record
drive.google.com
WebRun opens Google Drive to file the maintenance record. - Save a dated summary of today's notices and the services they touch to Google Drive
- Keep the full text of each notice so the record survives after the notice is archived
- Build a running history so recurring maintenance on one datacenter is visible
- Never open a support ticket or reply to a notice. WebRun reports, you act
Done when Today's maintenance record is filed in Google Drive.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it reschedule maintenance or open tickets?
No. WebRun never opens a support ticket, replies to a notice, reboots a server, or changes a service. It matches notices to your kit and writes cards and files you act on.
How does it know which notices affect me?
It reads the services on your own account, including their datacenter locations, then matches each published notice by location and service type. Notices touching nothing you run are skipped.
Does it warn my customers?
No. WebRun tells you which of your services sit behind a window and when. Any customer notice is written and sent by you, which is why the card carries the window and the impact.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.