Architecture #2668
Updated by Nicolas PERRON almost 12 years ago
Since we're trying to let the server be managed by itself (#1971), itself, we need to use rudder-agent instead of rudder-cfengine-community. Nevertheless, it seems that somes differences are present: * Not the same versions of BerkeleyDB for SLES 11 between rudder-agent and rudder-cfengine-community * _db43-devel_ for rudder-agent * _libdb-4_5-devel_ for rudder-cfengine-community * Not the same requirement for build * _make db4-devel byacc_ for rudder-agent * _db4-devel openssl-devel_ for rudder-cfengine-community * A patch about header (fix-missing-headers) is applied only on rudder-agent * Options about BerkeleyDB are used in build command only in rudder-agent (that's normal because rudder-cfengine-community is not used on SLES10 and options are differents from SLES 11) * All logic about fusionInventory are only in rudder-agent package * Initial promises are installed only with rudder-agent packages and only initial promises for nodes * node's initial promises are installed in rudder-agent * root's initial promises are installed in rudder-server-root * Init daemon and default files are differents * the names are differents: rudder-agent and cfengine-community * the default file use the name of the init daemon, which are differents like said in the point above * UUID are generated only in rudder-agent * UUID is checked and created if needed in rudder-agent * UUID is checked and created if needed in rudder-server-root