Re: [Condor-users] Separate machine roles in Condor

["Ian Chesal" <ICHESAL@xxxxxxxxxx>]

> While source codes of Condor 7.0.0 is now available, is there any
possibility to compile
> different machine roles separately? For example, can I build execution
machine only
> for Windows or Linux platforms? And what/how should I do after
compilation (create
> windows services/ linux daemons and so on)?

The role of machine is defined by the condor configuration file. And
what you put in there determins *which* condor_* executables Condor runs
on the machine so it takes on that role. If you're trying to cut down
the footprint of Condor on say, a Windows machine that will only ever
execute jobs, you can trim out the unused condor_* binaries. You don't
need to recompile Condor to do this.

What you trim out depends on how much or how little functionality you
want to retain on the machine. If you don't want to be able to query the
state of the machine *from* the machine you can lose command as well as
deamon executables.

Here's a short list of binaries I *think* you can delete to make it the
smallest install possible for an executor that can run vanilla jobs:

condor_advertise.exe
condor_birdwatcher.exe
condor_c-gahp.exe
condor_c-gahp_worker_thread.exe
condor_check_userlogs.exe
condor_chirp.exe
condor_cod.exe
condor_cod_request.exe
condor_collector.exe
condor_config_val.exe
condor_dagman.exe
condor_dbmsd.exe
condor_fetchlog.exe
condor_findhost.exe
condor_gridmanager.exe
condor_had.exe
condor_history.exe
condor_hold.exe
condor_negotiator.exe
condor_procd.exe
condor_q.exe
condor_qedit.exe
condor_quill.exe
condor_reconfig.exe
condor_release.exe
condor_replication.exe
condor_reschedule.exe
condor_rm.exe
condor_schedd.exe
condor_shadow.exe
condor_stats.exe
condor_status.exe
condor_submit.exe
condor_submit_dag.exe
condor_userlog.exe
condor_userprio.exe
condor_vacate.exe
condor_vacate_job.exe
condor_vm-gahp.exe
condor_vm_vmware.pl

Of course, if you run into problems, you'll have to start adding things
back in. But all those seem superfluous to running vanilla jobs.

> Another question is what for there are files like condor_negotiator
and
> condor_collector in the "condor\bin" directory for Windows
installation? 

Well, any machine might want to take on any particular role in the pool.
So all the binaries it might need are shipped with the package. You can
trim down the installation on a case by case basis in your pool. But
really, the disk you're saving here is pretty small. Unless disk space
is *really* tight you're better off just keeping all the binaries there.
Just in case.

For example: if you remove all the stuff in the list above you can't
administer the machine locally, you can't tell it to reconfigure itself.
Your only choice is to edit the configuration files and then stop and
start the service. Which is pretty invasive and not necessary if you
keep a few more binaries around.

- Ian


Confidentiality Notice.  This message may contain information that is confidential or otherwise protected from disclosure.
If you are not the intended recipient, you are hereby notified that any use, disclosure, dissemination, distribution, 
or copying of this message, or any attachments, is strictly prohibited.  If you have received this message in error, 
please advise the sender by reply e-mail, and delete the message and any attachments.  Thank you.