Project

General

Profile

Actions

User story #3164

closed

Technique "Zypper package manager configuration": add an option to specify repos per OS

Added by Jonathan CLARKE almost 12 years ago. Updated almost 3 years ago.

Status:
Rejected
Priority:
2
Assignee:
-
Category:
Techniques
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

Description

Sometimes, we need to add different package repos according to the OS we're on. One way of doing this in Rudder is to use groups, but this is not always practical. Repos are the classic example of when you know what you need on each OS, but don't really need a gruop to separate that out...

In the Technique, there is a multi-valued section to add repositories:

      <SECTION name="Repository" multivalued="true" component="true" componentKey="ZYPPER_NAME">

I suggest adding in here a variable "Only add this repository to if the OS is: " with a list of options SLES / SLES 10 / SLES 10 SP1 / SLES 10 SP2 / SLES 10 SP3 / SLES 10 SP4 / SLES 11 / SLES 11 SP1 / SLES 11 SP2 / RHEL / RHEL 5 / RHEL 6. The value of each options would be the corresponding CFEngine class, and we'd add to the promises something like "ifvarclass => ${os_to_apply_to}".


Subtasks 1 (0 open1 closed)

User story #3165: Technique "Zypper package manager configuration": implement option to specify repos per OSRejectedActions

Related issues 4 (0 open4 closed)

Related to Rudder - User story #3172: Technique Rug / YaST Pakcage Manager Configuration (ZMD) can't register services with signed RPMRejectedActions
Related to Rudder - User story #3178: Technique Rug / YaST Pakcage Manager Configuration (ZMD) Add possibility to add GPG Key with rugRejectedActions
Related to Rudder - Architecture #3312: Rework indentations from Techniques 'RUG / YaST package manager configuration (ZMD)' and 'Zypper package manager configuration'RejectedNicolas PERRON2013-02-22Actions
Related to Rudder - Architecture #3313: Rework indentations from Techniques 'RUG / YaST package manager configuration (ZMD)' and 'Zypper package manager configuration'RejectedNicolas PERRON2013-02-22Actions
Actions #1

Updated by Jonathan CLARKE almost 12 years ago

Jonathan CLARKE wrote:

I suggest adding in here a variable "Only add this repository to if the OS is: " with a list of options SLES / SLES 10 / SLES 10 SP1 / SLES 10 SP2 / SLES 10 SP3 / SLES 10 SP4 / SLES 11 / SLES 11 SP1 / SLES 11 SP2 / RHEL / RHEL 5 / RHEL 6. The value of each options would be the corresponding CFEngine class, and we'd add to the promises something like "ifvarclass => ${os_to_apply_to}".

Duh, this obvioulsy doesn't apply to RHEL/CentOS, since Zypper is SuSE-specific...

Actions #2

Updated by Matthieu CERDA almost 12 years ago

  • Target version changed from 2.3.10 to 2.3.11
Actions #3

Updated by Matthieu CERDA over 11 years ago

  • Target version changed from 2.3.11 to 2.3.12
Actions #4

Updated by Matthieu CERDA over 11 years ago

  • Target version changed from 2.3.12 to 2.3.13
Actions #5

Updated by Nicolas PERRON over 11 years ago

  • Target version changed from 2.3.13 to 84
Actions #6

Updated by Nicolas PERRON over 11 years ago

  • Target version changed from 84 to 2.4.7
Actions #7

Updated by Nicolas PERRON over 11 years ago

  • Target version changed from 2.4.7 to 2.4.8
Actions #8

Updated by Jonathan CLARKE over 11 years ago

  • Assignee changed from Jonathan CLARKE to Nicolas PERRON

Assigning to you, Nicolas, because the implementation ticket depends on another ticket you're working on.

Actions #9

Updated by Nicolas PERRON over 11 years ago

  • Target version changed from 2.4.8 to 2.4.9
Actions #10

Updated by Nicolas PERRON about 11 years ago

  • Target version changed from 2.4.9 to 2.4.10
Actions #11

Updated by Nicolas PERRON about 11 years ago

  • Target version changed from 2.4.10 to 2.4.11
Actions #12

Updated by Nicolas PERRON about 11 years ago

  • Target version changed from 2.4.11 to 2.4.12
Actions #13

Updated by Nicolas PERRON about 11 years ago

  • Target version changed from 2.4.12 to 2.4.13
Actions #14

Updated by Vincent MEMBRÉ almost 11 years ago

  • Target version changed from 2.4.13 to 2.6.11

Retargeting to 2.6 since 2.4 is not maintained anymore

Actions #15

Updated by Vincent MEMBRÉ almost 11 years ago

  • Target version changed from 2.6.11 to 2.6.12
Actions #16

Updated by Vincent MEMBRÉ almost 11 years ago

  • Target version changed from 2.6.12 to 2.6.13
Actions #17

Updated by Vincent MEMBRÉ over 10 years ago

  • Target version changed from 2.6.13 to 2.6.14
Actions #18

Updated by Jonathan CLARKE over 10 years ago

  • Target version changed from 2.6.14 to 2.6.16
Actions #19

Updated by Jonathan CLARKE over 10 years ago

  • Target version changed from 2.6.16 to 2.6.17
Actions #20

Updated by Nicolas PERRON over 10 years ago

  • Target version changed from 2.6.17 to 2.6.18
Actions #21

Updated by Matthieu CERDA about 10 years ago

  • Target version changed from 2.6.18 to 2.6.19
Actions #22

Updated by Vincent MEMBRÉ about 10 years ago

  • Target version changed from 2.6.19 to 2.6.20
Actions #23

Updated by François ARMAND almost 10 years ago

  • Status changed from 13 to Discussion
  • Assignee changed from Nicolas PERRON to Jonathan CLARKE
  • Target version changed from 2.6.20 to 3.1.0~beta1

I wonder if we still need that, given the possibility to do so with ncf builder on one hand, and generallity of the need on the other hand (i.e: what we really want is to be able to restrict some directive application to some condition (like the node OS) for a given rule, isn't it ?).

Jon, what do you thing of that ?

So, I would at least change the priority to much higher. It is certainly not 2 (and certainly not in progress, either).

Retargetting in 3.1 for the technique cleaning.

Actions #24

Updated by François ARMAND almost 10 years ago

Well, more generally, I think we have some architecture decesion to take regarding rug/yast/etc.

I added the relevant tickets as dependencies, as I thing they have to be taken as a whole.

Actions #25

Updated by Benoît PECCATTE almost 10 years ago

  • Project changed from 24 to Rudder
  • Category changed from Techniques to Techniques
Actions #26

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 3.1.0~beta1 to 3.1.0~rc1
Actions #27

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 3.1.0~rc1 to 3.1.0
Actions #28

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 3.1.0 to 3.1.1
Actions #29

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 3.1.1 to 3.1.2
Actions #30

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 3.1.2 to 3.1.3
Actions #31

Updated by Vincent MEMBRÉ about 9 years ago

  • Target version changed from 3.1.3 to 3.1.4
Actions #32

Updated by Vincent MEMBRÉ about 9 years ago

  • Target version changed from 3.1.4 to 3.1.5
Actions #33

Updated by Vincent MEMBRÉ about 9 years ago

  • Target version changed from 3.1.5 to 3.1.6
Actions #34

Updated by Vincent MEMBRÉ almost 9 years ago

  • Target version changed from 3.1.6 to 3.1.7
Actions #35

Updated by Vincent MEMBRÉ almost 9 years ago

  • Target version changed from 3.1.7 to 3.1.8
Actions #36

Updated by Vincent MEMBRÉ almost 9 years ago

  • Target version changed from 3.1.8 to 3.1.9
Actions #37

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 3.1.9 to 3.1.10
Actions #38

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 3.1.10 to 3.1.11
Actions #39

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 3.1.11 to 3.1.12
Actions #40

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 3.1.12 to 3.1.13
Actions #41

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 3.1.13 to 3.1.14
Actions #42

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 3.1.14 to 3.1.15
Actions #43

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 3.1.15 to 3.1.16
Actions #44

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 3.1.16 to 3.1.17
Actions #45

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 3.1.17 to 3.1.18
Actions #46

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 3.1.18 to 3.1.19
Actions #47

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.19 to 3.1.20
Actions #48

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.20 to 3.1.21
Actions #49

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.21 to 3.1.22
Actions #50

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.22 to 3.1.23
Actions #51

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.23 to 3.1.24
Actions #52

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 3.1.24 to 3.1.25
Actions #53

Updated by Benoît PECCATTE about 7 years ago

  • Target version changed from 3.1.25 to 4.1.9
Actions #54

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 4.1.9 to 4.1.10
Actions #55

Updated by Benoît PECCATTE almost 7 years ago

  • Status changed from Discussion to New
  • Assignee deleted (Jonathan CLARKE)
Actions #56

Updated by Benoît PECCATTE almost 7 years ago

  • Target version changed from 4.1.10 to Ideas (not version specific)
Actions #57

Updated by Alexis Mousset almost 3 years ago

This won’t be added to that technique, please use the technique editor for that. If you are missing some capabilities in it, please open a ticket for that need.

Actions #58

Updated by Alexis Mousset almost 3 years ago

  • Status changed from New to Rejected
Actions

Also available in: Atom PDF