Bug 1052273
Summary: | [RFE] Remote system management | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Duncan Innes <duncan> |
Component: | Remote Execution | Assignee: | Ivan Necas <inecas> |
Status: | CLOSED ERRATA | QA Contact: | jcallaha |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | Nightly | CC: | achadha, bkearney, daobrien, jcallaha, londrack, mmccune, pmutha, riehecky, sthirugn, xdmoon |
Target Milestone: | Unspecified | Keywords: | FutureFeature, Triaged |
Target Release: | Unused | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-07-27 09:08:44 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1194493 | ||
Bug Blocks: | 1296726 |
Description
Duncan Innes
2014-01-13 14:44:08 UTC
Background: Under the current Satellite regime, if clients are configured with Push-to-Client, all scheduled tasks are carried out via osad. There is no option to allow a task to be picked up only on a regular rhnsd check-in. On small estates, this is not an issue. When estates are scaled up to thousands or tens of thousands of clients, there are implications to scheduling tasks across all clients. 1) On a highly (or completely) virtualised environment, loading on the virtual hosts could rise to alarm levels if complex tasks are scheduled immediately across all clients 2) Load on the central Katello/Satellite system/smart-proxies could rise to unacceptable levels It would be polite to the infrastructure if tasks could be jittered in a way that spreads the load. Certain tasks may be required immediately, so any jittering should be user defineable on a task by task basis. i.e. jitter=0 for urgent tasks, jitter=4 hours for tasks that I'm more relaxed about. Examples of such tasks: Urgent: A failure of my single (bad design I know) NTP server prompts me to build a temporary NTP server. I'll want to push out a new config and restart NTP immediately. Relaxed: IT Security require a report (RPM verify for example) from all my machines by tomorrow. I'd like to schedule the task to start outside business hours, but be jittered by 4 hours to ensure no spike load hits the virtual hosts. Thanks Duncan Moving to Sat6 to be tracked there. Upstream bugs are moving to redmine. Since this issue was entered in Red Hat Bugzilla, the release flag has been set to ? to ensure that it is properly evaluated for this release. Reset docs contact <> daobrien Verified in Satellite 6.2 Beta Snap 15.2 This feature has been fully delivered in Satellite 6.2 in the form of the Remote Execution plugin. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2016:1501 |