Bug 697214
| Summary: | RHUI Manager: Sync Status and Schedule Screen | ||
|---|---|---|---|
| Product: | Red Hat Update Infrastructure for Cloud Providers | Reporter: | Jay Dobies <jason.dobies> |
| Component: | Documentation | Assignee: | Lana Brindley <lbrindle> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | wes hayutin <whayutin> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 2.0 | CC: | kbidarka, mhideo, tsanders |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-07-29 04:44:06 UTC | Type: | --- |
| 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: | |||
| Bug Blocks: | 695556 | ||
Trigger an Individual Repo Sync
sr trigger an individual repository sync
Repo syncs only apply to Red Hat repositories. In RHUI 2.0, custom repositories do not sync as they have no parent feed (packages are uploaded by the user instead).
Displays all repositories and relevant information the user may want when determining whether or not to trigger the sync:
(these result descriptions apply to CDS syncs and the two display menu options listed later in this BZ, so it can probably be moved to more of an introduction to this screen)
- Last sync result - This will be one of the following states:
- "scheduled" - A sync has not yet occurred for the repo but is scheduled to do so in the future.
- "running" - A sync is in progress. Trying to trigger a sync while one is already running for that repo will have no effect.
- "finished" - The last sync successfully finished.
- "error" - The last sync failed for some reason. More information can be found on the RHUA server.
- Next scheduled sync - The user may see that the next sync is occurring shortly and elect not to trigger the sync for that repo.
The user selects one or more repositories to sync and is prompted to confirm:
Sample:
------------------------------------------------------------------------------
rhui (sync) => sr
Select one or more repositories to schedule to be synchronized before its scheduled time.
The sync will happen as soon as possible depending on other tasks that may be executing
in the RHUI.
Last Result Next Sync Repository
------------------------------------------
- 1 : scheduled 04-16-2011 21:42 Red Hat Update Infrastructure 1.2 (RPMs) (5Server-i386)
- 2 : scheduled 04-16-2011 23:44 Red Hat Update Infrastructure 1.2 (RPMs) (5Server-x86_64)
- 3 : scheduled 04-16-2011 23:44 Red Hat Update Infrastructure 1.2 (SRPMS) (5Server-i386)
- 4 : scheduled 04-16-2011 23:44 Red Hat Update Infrastructure 1.2 (SRPMS) (5Server-x86_64)
Enter value from (1-4) to toggle selection, 'c' to confirm selections, or '?' for more commands: 1-2
Select one or more repositories to schedule to be synchronized before its scheduled time.
The sync will happen as soon as possible depending on other tasks that may be executing
in the RHUI.
Last Result Next Sync Repository
------------------------------------------
x 1 : scheduled 04-16-2011 21:42 Red Hat Update Infrastructure 1.2 (RPMs) (5Server-i386)
x 2 : scheduled 04-16-2011 23:44 Red Hat Update Infrastructure 1.2 (RPMs) (5Server-x86_64)
- 3 : scheduled 04-16-2011 23:44 Red Hat Update Infrastructure 1.2 (SRPMS) (5Server-i386)
- 4 : scheduled 04-16-2011 23:44 Red Hat Update Infrastructure 1.2 (SRPMS) (5Server-x86_64)
Enter value from (1-4) to toggle selection, 'c' to confirm selections, or '?' for more commands: c
The following repositories will be scheduled for synchronization:
Red Hat Update Infrastructure 1.2 (RPMs) (5Server-i386)
Red Hat Update Infrastructure 1.2 (RPMs) (5Server-x86_64)
Proceed? (y/n)
Scheduling sync for Red Hat Update Infrastructure 1.2 (RPMs) (5Server-i386)...
... successfully scheduled for the next available timeslot.
Scheduling sync for Red Hat Update Infrastructure 1.2 (RPMs) (5Server-x86_64)...
... successfully scheduled for the next available timeslot.
------------------------------------------------------------------------------
rhui (sync) =>
Display Sync Schedules and Status
dr display repo synchronization schedules
This is unlike other areas in RHUI Manager. Control does not immediately return to the prompt. The output is constantly displayed, updating itself at regular intervals (defaults to 5 seconds). To exit the screen and return to the RHUI prompt, the user pressed ctrl+c.
The display itself should be pretty self-explanatory. The only thing that warrants explanation are the result status codes, which are explained in the previous comment.
Sample:
------------------------------------------------------------------------------
-= Red Hat Update Infrastructure Management Tool =-
-= Repository Synchronization Status =-
Last Refreshed: 17:59:31
(updated every 5 seconds, ctrl+c to exit)
Next Sync Last Sync Last Result
------------------------------------------------------------------------------
Red Hat Update Infrastructure 1.2 (RPMs) (5Server-i386)
04-16-2011 21:42 04-16-2011 21:58 finished
Red Hat Update Infrastructure 1.2 (RPMs) (5Server-x86_64)
04-16-2011 23:44 04-16-2011 21:58 finished
Red Hat Update Infrastructure 1.2 (SRPMS) (5Server-i386)
04-16-2011 23:44 Never scheduled
Red Hat Update Infrastructure 1.2 (SRPMS) (5Server-x86_64)
04-16-2011 23:44 Never scheduled
Connected: guardian
------------------------------------------------------------------------------
CDS Trigger Sync and Display Schedules/Status: dc display CDS synchronization schedules sc trigger an individual CDS sync There really isn't anything to say/show here. It looks exactly the same as it does for repos, except it applies to CDS syncs instead. A CDS sync synchronizes *all* repositories on the CDS, deleting repos that have been unassociated. Only updates to previously syncced repos are sent, so after the initial sync future syncs only send new information (and thus should be pretty quick). Operation/Status & Scheduling LKB I lied about there being no differences. In addition to showing sync schedules, the CDS status screen shows the current state of each CDS. This state is updated regularly through a heartbeat from the CDS and will be either "UP" or "DOWN"
Sample:
------------------------------------------------------------------------------
-= Red Hat Update Infrastructure Management Tool =-
-= CDS Synchronization Status =-
Last Refreshed: 14:25:05
(updated every 5 seconds, ctrl+c to exit)
US East Region CDS .......................................... [ UP ]
Next Sync Last Sync Last Result
------------------------------------------------------------------------------
US East Region CDS
04-18-2011 17:27 Never scheduled
Connected: guardian
------------------------------------------------------------------------------
Revision 1-6. LKB The latest doc covers all the above mentioned features. This book is now available at http://docs.redhat.com/docs/en-US/Red_Hat_Update_Infrastructure/2.0/html/Installation_Guide/index.html Please raise a new bug for any further changes. LKB |
Accessed from the Home screen: s synchronization status and scheduling Used to view recent sync status information and manually trigger syncs, both CDS and repo. I feel like I explained this before, but I might be thinking about the demo instead of BZ entries. A sync triggered from this screen does not execute *immediately*. If the server is too busy with other stuff, it gets put in a queue to run as soon as the server has some free cycles to spare. The typical use is a situation where the server shows the next sync will not occur for another few hours and the user wants to do the sync sooner. This doesn't reschedule the sync that was to execute later, it just adds a new one. That felt kinda wonky to explain, maybe an example would help. If repo A is scheduled to sync at 8pm and I manually trigger a sync at 7:30pm, the 8pm sync will still occur. It's not rescheduled for 6 hours later than the 7:30 one (6 is the current default between syncs). All of the above applies to both CDS and repo syncs. There is very little difference in UI between the two, so any explanations apply to both. Menu: ------------------------------------------------------------------------------ -= Red Hat Update Infrastructure Management Tool =- -= Synchronization Status =- dr display repo synchronization schedules sr trigger an individual repository sync dc display CDS synchronization schedules sc trigger an individual CDS sync Connected: guardian ------------------------------------------------------------------------------ rhui (sync) =>