On Tue, Jun 09, 2009 at 11:12:48PM +1000, Max Matveev wrote:
>
> HCA names are assigned in the order of discovery, if you add (not just
> change) an HCA then something which used to be mthca2 may become
> mthca3. With the config file you have a name to GUID mapping, if you
> add an HCA it will not be reported by the PMDA until the config file
> is updated. You need to decide what's more important - stable instance
> mapping or automatic adjustments in case of change. I've decided that
> stable instance mapping was more important.
>
> Perhaps a better way to deal with this would be to add some keywords
> to the config file to indicate local HCAs and to complain bitterly if
> they're not found.
I like this idea. Maybe that's the way to go...
>
> BTW, the config file can be an executable too - nasmgr used that to
> generate its own naming scheme.
I noticed that. I wasn't sure if anything actually used that
functionality.
mh
|