Features with weight 1 will prevent the node from being allocated unless
the user specifically askes for that feature, so this behavior is
expected. If you want to prevent people from getting the pcr200 nodes
unless they ask for a NetFPGA, set the feature to 1. If you want assign
to perfer not to use the r200 nodes unless a NetFPGA is requested, set
it to some value between 0 and 1 (the higher the value, the harder
assign will try to avoid usng the node.)
Thus spake David A. Kotz on Sat, Sep 26, 2009 at 04:24:51PM -0500:
David A. Kotz wrote:
mysql> insert into node_type_features values("pcr200","hosts-netfpga",1.0);
Query OK, 1 row affected (0.00 sec)
mysql> select * from node_type_features;
+--------+---------------+--------+
| type | feature | weight |
+--------+---------------+--------+
| pcr200 | hosts-netfpga | 1 |
+--------+---------------+--------+
1 row in set (0.00 sec)
That solved the features problem. Now I just have the ethernet error.
It turns out that this solved the problem of allocating the NetFPGAs but
made it impossible to allocate r200s directly. I looked at the table
definition, saw that the default value was 0, hoped that meant I
wouldn't cause any divide-by-zero messes, and changed it to 0. Now I
can allocate NetFPGAs and r200s.