Duty3G/Duty3G 5.1 Release Notes
From Documentation
| Revision as of 23:37, 6 August 2007 Moff (Talk | contribs) (→Technical Notes: Using duty3G V5.1) ← Previous diff |
Revision as of 23:38, 6 August 2007 Moff (Talk | contribs) (→New Features in this Release) Next diff → |
||
| Line 159: | Line 159: | ||
| *You can write your own program or script to determine if the current date and time is to be included in the schedule. | *You can write your own program or script to determine if the current date and time is to be included in the schedule. | ||
| - | + | :{{Note| As with schedtime, scheduling of automatic jobs is still implemented via CRON.}} | |
| - | {{Note| As with schedtime, scheduling of automatic jobs is still implemented via CRON.}} | + | |
| <br> | <br> | ||
| Line 170: | Line 169: | ||
| Previously, you may also have prefixed duties with a number series so that they will display in the duty console in the order they should be performed. Now you can re-order duties, using drag and drop, into what ever order you like using <em style="color:darkslategray;font-weight:bold">Duty3G configuration > Duty > Reorder</em>. Duties can only be re-ordered for a given Duty List. | Previously, you may also have prefixed duties with a number series so that they will display in the duty console in the order they should be performed. Now you can re-order duties, using drag and drop, into what ever order you like using <em style="color:darkslategray;font-weight:bold">Duty3G configuration > Duty > Reorder</em>. Duties can only be re-ordered for a given Duty List. | ||
| - | {{Note| Overdue duties will still display at the top of the duty list. Dependencies of duties will always display just above that duty.}} | + | :{{Note| Overdue duties will still display at the top of the duty list. Dependencies of duties will always display just above that duty.}} |
| <br> | <br> | ||
| Line 199: | Line 198: | ||
| You can now attach a HTML or text file of documentation to a duty. This file can be viewed by the user from the duty console at any time. | You can now attach a HTML or text file of documentation to a duty. This file can be viewed by the user from the duty console at any time. | ||
| - | + | :{{Note| There is no facility provided to create notes files—you can simply use your favourite text editor (vi, emacs etc.). Notes files should be created in the <tt>duty_5.1/local/notes</tt> directory.}} | |
| - | {{Note| There is no facility provided to create notes files—you can simply use your favourite text editor (vi, emacs etc.). Notes files should be created in the <tt>duty_5.1/local/notes</tt> directory.}} | + | |
| <br> | <br> | ||
Revision as of 23:38, 6 August 2007
Contents |
Overview and Features
Duty3G
Duty3G 5.1 encourages sound management practices by making it possible to perform the regular operations workload on UNIX, Linux and Windows servers in a way that is efficient, reliable, verifiable, compliant, and repeatable whilst protecting privileged user access. With duty3G you define the command or commands that carry out a process, you assign the privilege to the duty, and then assign the duty to the user.
New features in duty3G 5.1
Key features of the new release are:
Enhanced operations
- Enhanced schedules, for example, a Weekday schedule can now exclude public holidays.
- You can now assign duties to a class/folder, so the duty name no longer needs to be prefixed with a Class or Category. Now it is much easier to locate that ‘XYZ’ duty.
- You can now order duties in the order they should be performed, so the duty name no longer needs to be prefixed with a Sequence number
- You can now force the user to re-authenticate before running certain duties giving added security.
- Duties can now be auto disabled and/or auto re-enabled on given dates. This is useful during system rollouts or migration projects.
- Duties are now run asynchronously, meaning if you have a long running duty it no longer stops you from running another duty.
- As a duty is performed, that duty is now “locked” so no other user can run the same duty with possible undesirable results.
- End user's can set their own start-up view (at-request or outstanding duties) and start-up Class, along with a reminder period before duties become overdue.
- End user’s can now view upcoming scheduled duties for a selected day or date in the future – “What has to be done on Friday?”. This is also useful for Administrators to check that duties have been scheduled correctly, for example, making sure certain duties are not scheduled for Christmas Day.
- You can now filter your view of duties:
- for a selected class
- that run on a selected host
- for a selected users' role
Improved auditing
- Filtering has been added to make viewing the Duty audit trail more meaningful:
- by selected time period
- that have ended in error
- for selected duty
- for selected user
- for selected mode
- Duty audit trail entries are now colour coded to make it easier to spot abnormal entries.
- New duty compliance reports are generated daily and can be viewed at any time. These reports highlight failed, missed and skipped duties – exceptions that affect operations compliance.
Documentation
- An HTML or text document can now be associated with a duty, so end users can see what Policies and Procedures the duty is supporting.
- You can now link directly to online help (user guide), release notes and other documentation, and even report a bug via duty3G.
Installation Requirements
Software prerequisites
To install and run duty3G 5.1 on a host, you must have:
- COSmanager 4.2.5 or later already installed on the host (see the COSmanager User Guide for instructions)
- a duty3G distribution
- a valid license key for this host (see your COSmanager distributor if you don’t have a valid license key)
- sufficient disk space
- COSmanager Manager access, or equivalent
- the ability to open a root shell
Disk space required
| Software | Approximately 1 MB in the duty3G home directory. |
|---|---|
| Temporary Files | While installing duty3G: less than 1 MB, to hold a copy of the software distribution. While duty3G is running: less than 1 MB in /tmp. |
| Audit Trail | For the duty3G audit trail, about 10 - 50 MB in the system spool area. The actual amount will depend on the activity on your system (e.g. how many duties are run), and how often you archive and delete the log files. |
| Compliance Reports | For the duty3G compliance reports, about 5 - 20 MB in the system spool area. |
Running Remote Duties on Windows
The current duty3G release supports running remote duties on Windows hosts which have the EWC (Enterprise Windows Client) 3.1.1 installed. This product may be purchased separately.
Upgrading COSduty 3.0
- Download the distribution file to /tmp on the target host.
- From the Configuration menu, select COSmanager configuration > Applications.
- Select Application > Install.
- Press Choose. You will see a list of the applications that can be installed. Choose the entry titled duty3G, and press Accept.
- COSmanager copies the duty3G files from the distribution file to the target directory, updates the duty3G audit trail and creates the duty3g compliance report directory.
- To migrate your existing COSduty 3.0 database to the newly installed version press Copy. Your existing database is copied and updated with new table columns.
- To make the newly installed duty3G the default version press Accept, then press Continue.
- Any automatic duties are added or re-added to the cosmos crontab.
- This completes the upgrade installation. You must now restart COSmanager for the new version of duty3G to come into affect.
Technical Notes: Using duty3G 5.1
This section contains some technical notes and tips about using duty3G 5.1.
Temporary or trial licensing
Duty3G may be issued with a temporary license for use in trials or demonstrations. Temporary licenses have an in-built expiry date. You must obtain a permanent license or a new temporary license from your COSmanager distributor to keep using duty3G after the expiry date.
 | Note |
| Duty3G won’t install if the license key is due to expire within the next 7 days. In this case you will need to obtain a new license key from your COSmanager distributor. | |
COSmanager framework version required for duty3G 5.1
Duty3G 5.1 requires COSmanager 4.2.5 or newer.
Schedules and Schedtime
Duty3G 5.1 the newer, more generalised scheduling provided in COSmanager 4.2.X. These include the datelist and schedule tables, which supersede the schedtime table (as used in COSduty 3.0). The schedtime table is now deprecated. It is important to note that the schedtime and schedule tables are maintained separately, and so changes to one table will not be reflected in the other. You should only maintain the schedule and datelist tables. You can do this via:
- Duty3G configuration > Tools > Schedules, or
- COSmanager configuration > Other tables > Schedule.
Audit Trails and Compliance Reports
When duty3G is installed, two new audit trails are created: duty_log and duty_compl. By default, these are created in the system spool area (usually /usr/spool or /var/spool). The duty_log audit trail is the primary audit trail, recording all user actions, such as:
- running a duty, noting the exit status;
- marking a duty as done;
- any added user comments;
- re-authentication failures;
- attempts to run disabled duties.
The duty_compl audit trail is used to store all the Daily Duty Compliance Reports created, by default, at midnight on a daily basis.
Depending on the volume of duties run, these directories may become large, so it is important that audit trail cycling be configured correctly for your site to prevent these files from growing unbounded. By default the audit trails are cycled:
duty_log monthly, retaining up to 15 archive copies duty_compl daily, retaining each report for up to one year.
New Features in this Release
Generalised Calendaring for Automatic Duties
Duty3G V5.1 uses the new schedule and datelist tables which provide more features than the old schedtime table:
- You can create named datelists, which, as the name implies, contain lists of arbitrary dates which can be used to either be included or excluded from a schedule.
- You can write your own program or script to determine if the current date and time is to be included in the schedule.
| | Note |
| As with schedtime, scheduling of automatic jobs is still implemented via CRON. | |
Grouping and Ordering Duties
Previously you may prefixed duties with a Class or Category (for example, STACKER: Inventory media) so that like duties were listed together on the duty console. Now you can define a duty with a Duty List, or you can move a selected group duties to a Duty List using Duty3G configuration > Duty > Move to duty list.
Previously, you may also have prefixed duties with a number series so that they will display in the duty console in the order they should be performed. Now you can re-order duties, using drag and drop, into what ever order you like using Duty3G configuration > Duty > Reorder. Duties can only be re-ordered for a given Duty List.
| | Note |
| Overdue duties will still display at the top of the duty list. Dependencies of duties will always display just above that duty. | |
Duty Locking
Startup View
Disabling and Enabling Duties
Viewing Upcomping Duties
Re-authentication
Viewing the Duty Audit Trail
Daily Duty Compliance Reports
Notes Facility
You can now attach a HTML or text file of documentation to a duty. This file can be viewed by the user from the duty console at any time.
| | Note |
| There is no facility provided to create notes files—you can simply use your favourite text editor (vi, emacs etc.). Notes files should be created in the duty_5.1/local/notes directory. | |
Known Problems in this Release
Duty3G Console Refresh
The duty3G console has been designed to refresh the data automatically within 5 seconds of any duty or status change. It has been observed on some platforms that very occasionally the duty3G console may miss a status change, and hence it does not refresh itself correctly. If you find this to be the case, select View > Outstanding (or whatever view you are in), which will force a refresh.