Hi folks, I am using gridengine to load tests on to an Ixia. Only one test can run at time so I configured the queue to resource quota configuration with a rule that says limit users * queues lt_np_13 to slots = 1 This has worked fine for years.
Now, however I have many Ixia blades and I still want to use gridengine to distribute jobs to the cluster nodes, but ultimately, there can only be one test running per ixia blade. I think what I need to do is to use a consumable attribute. A command like qsub -l ixiablade1=1 myjob.sh, will take a consumable resource for ixiablade1. However, lets' say I have three ixia blades, ixiablade1, 2 and 3. Somehow I need to have a way of saying you can take ixiablade1 or you can take ixiablade2 or you can take ixiablade3, but you can only take one. Presumably, tests will have to wait until one of the three consumables is available. Here is a diagram [queuemaster] [wasim01] <-----NETWORK -----> IXIA[wa-ixia-01] [wasim02] [slot 1 - ports 1 -4] <-- Direct Ethernet x 4 --> DUT 1 [wasim03] [slot 2 - ports 1 -4] <-- Direct Ethernet x 4 --> DUT 2 [wasim04] [slot 3 - ports 1 -4] <-- Direct Ethernet x 4 --> DUT 3 [wasim05] [wasim06] [wasim07] [wasim08] For example, I may have 100 individual tests queued to run on the grid, across 8 different machines, and because of resource quota or consumables, only three jobs can run at a time. When a job moves from the waiting to running, it will be because one of the consumables was available (and now taken again). When the test begins execution, the test will examine the environment to determine which consumable it was given and use that to select the appropriate config file (For slot1.cfg, slot2.cfg or slot3.cfg) which defines port connections and other DUT related configuration information. Any thoughts would be appreciated. Thanks Rich _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
