User story #3495: Add peristent classes when checking installation, update or remove of packages in order to reduce use of rug or zypper - Rudder - Issue Tracker

Actions

User story #3495

closed

User story #3494: (ex-PT/Technique) 'Package management for RHEL / CentOS / SuSE / RPM systems': Change behavior in order to reduce number of execution of rug, zypper or zmd

Add peristent classes when checking installation, update or remove of packages in order to reduce use of rug or zypper

Added by Nicolas PERRON over 11 years ago. Updated over 9 years ago.

Status:

Released

Priority:

1 (highest)

Assignee:

Jonathan CLARKE

Category:

Techniques

Target version:

2.3.12

Pull Request:

https://github.com/Normation/rudder-t...

UX impact:

Suggestion strength:

User visibility:

Effort required:

Name check:

Fix check:

Regression:

Description

Instead of checking installation, update or removing of packages with rug or zypper, we should be able to define the interval of time between each check and add it in a persistent class.

Actions

Copy link

Updated by Nicolas PERRON over 11 years ago

Status changed from New to Discussion
Assignee changed from Nicolas PERRON to Jonathan CLARKE

Jon, when defining the interval of time between each check, it seems logic to define it in the Technique 'Package management for RHEL / CentOS / SuSE / RPM systems'. The problem is that this Technique is multiinstance which will oblige to define this interval several times. I see options:

Define 'Package management for RHEL / CentOS / SuSE / RPM systems' as an unique instance Technique. It seems to be the simpliest way but is a big change for the user.
Define an interval of time between each check for each packages
Use of another Technique for configuring this interval but I don't see which other Technique use for that.

What's your opinion, Jon ?

Actions

Copy link

Updated by Nicolas PERRON over 11 years ago

Status changed from Discussion to 10
% Done changed from 0 to 100
Pull Request set to https://github.com/Normation/rudder-techniques/pull/97

Nicolas PERRON wrote:

Jon, when defining the interval of time between each check, it seems logic to define it in the Technique 'Package management for RHEL / CentOS / SuSE / RPM systems'. The problem is that this Technique is multiinstance which will oblige to define this interval several times. I see options:

Define 'Package management for RHEL / CentOS / SuSE / RPM systems' as an unique instance Technique. It seems to be the simpliest way but is a big change for the user.

Define an interval of time between each check for each packages

Use of another Technique for configuring this interval but I don't see which other Technique use for that.

What's your opinion, Jon ?

In Nicolas opinion, the use of unique variable for the interval of time is acceptable, even if the user have to set it at each instance of the Technique. The value used will be get from the most prior Directive.

Pull Request URL added: https://github.com/Normation/rudder-techniques/pull/97
Jon, could you review it please ?

Actions

Copy link