What is new: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
(8 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
[[Documentation]] / [[UserMan|User Manual]] / [[ | [[Documentation]] / [[UserMan|User Manual]] / [[What is new | What is new]] __NOEDITSECTION__ | ||
---- | ---- | ||
= | The summary of changes between the old AMS(v8.x)/ABS(v3.x) and next major version AMS(v9.x)/ABS(v4.x) of Infinity. | ||
{| class="wikitable" | |||
! Scope | |||
! Old AMS(v8.x)/ABS(v3.x) | |||
! New AMS(v9.x)/ABS(v4.x) | |||
! Comment | |||
|- | |||
| user | |||
| No mailing list | |||
| '''Users must be registered into the Infinity user mailing list.''' | |||
| '''In the near future, Infinity will be accessible only for registered users in Matacentrum.''' | |||
|- | |||
| technical, AMS | |||
| One monolithic module cache per site | |||
| Several module caches are organized into module bundles, which are site-independent. | |||
| Users can define their own modules. | |||
|- | |||
| technical, AMS | |||
| The default site is selected by hostname lookup into the host group database | |||
| The default site is selected by the host group name, which must be provided prior to the Infinity activation | |||
| Simpler administration | |||
|- | |||
| technical, AMS | |||
| Complex and not always working set-up of user creation mask (umask). | |||
| Simpler, well-defined set-up of user creation mask (umask). Umask is set in all new (child) shell instances. | |||
| Guaranteed data access management. | |||
|- | |||
| technical, AMS | |||
| AMS_SITE contains SiteID, composed of the site name and UUID. | |||
| AMS_SITE contains the site name. SiteID is defined for each site but not executively used. | |||
| Simpler administration. | |||
|- | |||
| technical, AMS | |||
| Autoloaded modules can be defined per site and user. | |||
| Autoloaded modules can be defined per host config, host group, site, and user. | |||
| Simpler administration. | |||
|- | |||
| technical, AMS | |||
| Autoloaded modules are always added when they are valid. | |||
| The module bundle administrator can disable selected autoloaded modules. | |||
| This option can help to solve compatibility issues between certain modules and operating system environments. | |||
|- | |||
| user interface, AMS, | |||
| Fine-tuned colour preferences for printing into terminals can be defined by a user (ams-config). | |||
| Only predefined colour profiles can be selected now (ams-config). The administrator defines their list, which can be extended by a user. | |||
| | |||
|- | |||
|} |
Latest revision as of 12:31, 18 January 2024
Documentation / User Manual / What is new
The summary of changes between the old AMS(v8.x)/ABS(v3.x) and next major version AMS(v9.x)/ABS(v4.x) of Infinity.
Scope | Old AMS(v8.x)/ABS(v3.x) | New AMS(v9.x)/ABS(v4.x) | Comment |
---|---|---|---|
user | No mailing list | Users must be registered into the Infinity user mailing list. | In the near future, Infinity will be accessible only for registered users in Matacentrum. |
technical, AMS | One monolithic module cache per site | Several module caches are organized into module bundles, which are site-independent. | Users can define their own modules. |
technical, AMS | The default site is selected by hostname lookup into the host group database | The default site is selected by the host group name, which must be provided prior to the Infinity activation | Simpler administration |
technical, AMS | Complex and not always working set-up of user creation mask (umask). | Simpler, well-defined set-up of user creation mask (umask). Umask is set in all new (child) shell instances. | Guaranteed data access management. |
technical, AMS | AMS_SITE contains SiteID, composed of the site name and UUID. | AMS_SITE contains the site name. SiteID is defined for each site but not executively used. | Simpler administration. |
technical, AMS | Autoloaded modules can be defined per site and user. | Autoloaded modules can be defined per host config, host group, site, and user. | Simpler administration. |
technical, AMS | Autoloaded modules are always added when they are valid. | The module bundle administrator can disable selected autoloaded modules. | This option can help to solve compatibility issues between certain modules and operating system environments. |
user interface, AMS, | Fine-tuned colour preferences for printing into terminals can be defined by a user (ams-config). | Only predefined colour profiles can be selected now (ams-config). The administrator defines their list, which can be extended by a user. |