FOSSology

On Apr 12, 2012, at 10:30 AM, Ma, Dong (Vincent, Open Source Program Office) wrote:
Vincent>> I am trying to avoid that but catch the issue to discuss with team. In my thought:

fossology-common > create user/groups
fossology-db > fo-postinstall –database > dbcreate
fossology-web > fo-postinstall –webonly --licenseref > fossinit –l and fo_dbcheck
fossology-scheduler > fo-postinstall –scheduleronly
fossology-ununpack/.. > fo-postinstall –agent but need to remove fo_dbcheck and create user/groups part.

I'm thinking along the same lines as you but what happens in --agent and --web would change:

fossology-common > runs fo-postinstall to create system user and group, create repository, set directory permissions
These are currently done in --web and --agent

like you said fossology-db > run fo-postinstall to create the db (dbcreate)

fossology-web > requires fossology-db, fossology-common; populates the db (like you said)

fossology-scheduler > requires fossology-db, fossology-common; fo-postinstall --scheduleronly

fossology-ununpack > requires fossology-db, fossology-common;

fossology-copyright > requires fossology-db, fossology-common;
etc.

I don't see why this wouldn't work for both single systems and clusters.
Mary and I were just talking about this and the only issue we could think of where we need to know if we are installing to a cluster or single system is really if we are installing to the db server or an agent. In other words, we need to know what to put in Db.conf for a host. fossology-db is never run on an agent machine but Db.conf needs to be manually updated on the agent to point to the db server host.

Bob