User story #11851
Updated by Nicolas CHARLES over 6 years ago
We need to port a maximum of techniques in the multi-versionned technique format Some are more easy to port than others, and here I'll list the assessed level of complexity h1. h3. Easy set_vars: it uses only ncf, so it's direct h1. h3. Ok ManageFileAndFolder, FileAlterationMonitoring: we need to change the kept_if_else to rudder_common_classes, and it will be straitfoward groupManagement, services_management: seem quite easy h1. h3. Hard or long fileSecurity: it loads its data from an external file - the complexity of changing that seems quite high jobScheduling: the code is really complex, it looks simple to port to multi-versionned, but the risk seems quite high partitionSizeMoniroting: a body to move in lib, and everything is straightforward conConfiguration: we need to restart only once cron at the end of changes h1. h3. Unknwown generic*Definition: current implementation doesn't look compatible with the multiversionned format (variable erasure) variable_from_json, userManagement: we need to evaluate in details how to do it sshKeyDistribution: we need to reevaluate how we implement the purge of keys fstabConfiguration: there are a lot of classes defined in namespace, so we need to evaluate more