Project

General

Profile

Actions

User story #10276

closed

I Can not migrate from old "package technique" to new one automatically

Added by François ARMAND about 7 years ago. Updated over 5 years ago.

Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
Web - Config management
UX impact:
Suggestion strength:
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Name check:
Fix check:
Regression:

Description

Rudder 4.0 introduced a much better and saner package technique which abstract upon the underlying package manager correctly and allows basic requirement like "ensure present" (not install [or exclusive] update).

So anybody using Rudder 4.0 should use these new techniques. But there is no automatic way to migrate existing directive from an old "package management for debian" (for ex) to the new "package management".

The problem was for example reported in http://www.rudder-project.org/redmine/issues/9859

The current solution is to migrate by hand, one by one, each directive to the new technique. It is not a good solution.

Dmitry Svyatogorov created a python script which use Rudder API to do most of the grunt work for you. One can find it here: https://github.com/ds-voix/VX-PBX/blob/master/RUDDER/api.py
This is a better solution, and something alike, able to correctly process 90% of the cases, should be included in some fashion into Rudder.


Related issues 3 (0 open3 closed)

Related to Rudder - Bug #9859: "Migrate" button is displayed for deprecated techniques even if all version are deprecatedReleasedFrançois ARMANDActions
Related to Rudder - User story #9125: Add a technique using new package promisesReleasedNicolas CHARLES2016-09-27Actions
Related to Rudder - User story #12710: Add a package techniques migration scriptReleasedBenoît PECCATTEActions
Actions

Also available in: Atom PDF