Hi David,<br><br>Can you elaborate on the customizations that would be needed ? What kind of source-code modifications would be required ? <br><br>This might be useful as it will mimic a real cluster.<br><br>Thanks,<br>Kunal<br>

Kunal,<div><br></div><div>As of now each will report the same thing. If you wanted them to change each one, you&#39;d have to modify the code. It wouldn&#39;t be too hard to do (the mom daemons know that they&#39;re running multi-mom) but it would take some customization. </div>

<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi David,<br><br>Thanks for your quick response and for pointing to the multi-mom feature. The idea is similar i.e. make a small cluster look bigger with being as realistic as possible.<br><br>I read through that page and seems like it will do what I want. I had a follow up question on that :<br>

<br>- Does each mom read from /proc and report to the head node (pbs_server) ? In that case the total cpus , memory, load etc. will be reported same from each of them. Can that be isolated and different for each of them to mimic<br>

<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Kunal,<div><br></div><div>I have done a chroot environment with TORQUE - it worked fine. I was doing this for testing with sleep jobs, and the chroot was because I didn&#39;t want it to interact with anything else on the machine. I&#39;m not sure what you&#39;re attempting to accomplish, but you may want to consider looking into the multi-mom feature (available starting in 3.0.0) that we also use a lot for testing. I have actually abandoned my chroot environment in favor of using the multi-moms.</div>

<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div>
Hi All,<br><br>Has anyone tried chroot environment for Torque 3.0.3 or later version ? I&#39;m thinking of having multiple chroot environment on the same system, each representing a compute node and build a cluster.<br><br>

So, even though there are say only 2 physical machines ( 1 server and 1 compute node), we should be able to make a cluster of say 4 nodes. Assuming that the 1 physical compute node can have 3 chroot environment,<br>each having its own virtual IP and communicating with the master as 3 independent compute nodes. Head node / server will see as if there are 4 nodes and the scheduler will aallocate jobs accordingly.<br>