-
Notifications
You must be signed in to change notification settings - Fork 15
[RFC] Suspending provider #41
Comments
That's not entirely true. There is no "stop / pause / suspend" button on the provider. But for the past 10+ years, we've recommended that users create a zone with no |
@bdunne There are PRs which adds pause/resume buttons to providers, which causes moving provider to zone without server. I'll update this issue after we'll finish discussion about it (I'm sure we're close to it) |
IIRC @zeari had added an EDIT: ah, I didn't notice you already mention it. |
@cben yes, this flag is used and extended for all providers and used for toolbar buttons |
Overview
It is not possible temporary stop/suspend provider including all its workers in case there is running maintenance (or for example network maintenance leading to connectivity issue to provider).
Usually there is a lot of error messages in logs related to workers that belongs to provider in maintenance.
RFE BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1455145
List of PRs: ManageIQ/manageiq#17489
Solution
Provider can be "paused" and "resumed". What does pausing mean?
Provider (manager and child managers) is disabled (by flag
ExtManagementSystem.enabled
)It stops provider specific workers (like Refresh worker)
Provider is moved to special zone with no servers in it, we call it "maintenance zone"
Maintenance zone
Special unique zone. Is identified by
MiqRegion.maintenance_zone
association so it can be one per region. Is marked as invisible (Zone.visible
) thus it shouldn't be visible by users.When EMS is put to maintenance zone, original zone is saved to
ExtManagementSystem.zone_before_pause
UI and API
UI shows buttons "Pause" and "Resume" in list and detail pages for providers.
Quadicon of provider has moon icon when paused.
Zone before pause is shown to users instead of maintenance zone.
Maintenance zone is invisible in Configuration's list of zones, choosing zone in new/edit provider pages and choosing zone for server.
Restrictions
The text was updated successfully, but these errors were encountered: