Project

General

Profile

Actions

Question #3393

closed

Best way to upgrade techniques

Added by Dennis Cabooter almost 11 years ago. Updated about 9 years ago.

Status:
Resolved
Priority:
2
Category:
System techniques
Target version:
Regression:

Description

My Rudder server is on Ubuntu 12.04. Yesterday I only upgraded the rudder-techniques packages to match the nightly build. What is the best practice to upgrade only the techniques without upgrading everything. Maybe using git? If so, how can I accomplish this? In my opinion the manual is not very clear about this.

Actions #1

Updated by Matthieu CERDA almost 11 years ago

  • Category set to System techniques
  • Status changed from New to Discussion
  • Assignee set to Dennis Cabooter
  • Priority changed from N/A to 2
  • Target version set to 2.6.0~beta1
  • % Done changed from 0 to 20

You are right, this part of the documentation should be improved.

Basically, yes you must do it via git, the quick'n'dirty way which is:

cd /var/rudder/configuration-repository/techniques
cp -a /opt/rudder/share/techniques/* .
git add .
git commit -m "Dennis: Upgrade the Rudder Techniques" 

And then, in the Rudder interface, in the "Configuration Policy -> Techniques" pane, click on the big "Reload" button.

This is to be done ONLY if you did not customize any technique in the standard Rudder tree, if not please tell me the ones you did modify so I can adapt the commands.

I will also update the documentation with this procedure so there is no confusion anymore.

Actions #2

Updated by Nicolas PERRON almost 11 years ago

  • Target version changed from 2.6.0~beta1 to 2.6.0~rc1
Actions #3

Updated by Matthieu CERDA almost 11 years ago

  • Target version changed from 2.6.0~rc1 to 2.6.0
Actions #4

Updated by Jonathan CLARKE almost 11 years ago

  • Target version changed from 2.6.0 to 2.6.1
Actions #5

Updated by Nicolas PERRON almost 11 years ago

  • Target version changed from 2.6.1 to 2.6.2
Actions #6

Updated by Nicolas PERRON almost 11 years ago

  • Target version changed from 2.6.2 to 2.6.3
Actions #7

Updated by Nicolas PERRON over 10 years ago

  • Target version changed from 2.6.3 to 2.6.4
Actions #8

Updated by Nicolas PERRON over 10 years ago

  • Target version changed from 2.6.4 to 2.6.5
Actions #9

Updated by Nicolas PERRON over 10 years ago

  • Target version changed from 2.6.5 to 2.6.6
Actions #10

Updated by Nicolas PERRON over 10 years ago

  • Target version changed from 2.6.6 to 2.6.7
Actions #11

Updated by Nicolas PERRON over 10 years ago

  • Target version changed from 2.6.7 to 2.6.8
Actions #12

Updated by Nicolas PERRON over 10 years ago

  • Target version changed from 2.6.8 to 2.6.9
Actions #13

Updated by Nicolas PERRON over 10 years ago

  • Target version changed from 2.6.9 to 2.6.10
Actions #14

Updated by Vincent MEMBRÉ about 10 years ago

  • Target version changed from 2.6.10 to 2.6.11
Actions #15

Updated by Vincent MEMBRÉ about 10 years ago

  • Target version changed from 2.6.11 to 2.6.12
Actions #16

Updated by Vincent MEMBRÉ about 10 years ago

  • Target version changed from 2.6.12 to 2.6.13
Actions #17

Updated by Vincent MEMBRÉ almost 10 years ago

  • Target version changed from 2.6.13 to 2.6.14
Actions #18

Updated by Jonathan CLARKE almost 10 years ago

  • Target version changed from 2.6.14 to 2.6.16
Actions #19

Updated by Jonathan CLARKE almost 10 years ago

  • Target version changed from 2.6.16 to 2.6.17
Actions #20

Updated by Nicolas PERRON over 9 years ago

  • Target version changed from 2.6.17 to 2.6.18
Actions #21

Updated by Matthieu CERDA over 9 years ago

  • Target version changed from 2.6.18 to 2.6.19
Actions #22

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 2.6.19 to 2.6.20
Actions #23

Updated by François ARMAND about 9 years ago

  • Status changed from Discussion to Resolved
  • Target version changed from 2.6.20 to 2.10.10
Actions

Also available in: Atom PDF