opensm: suggestion to define new common port_groups file

opensm: suggestion to define new common port_groups file

[Eli Dorfman (Voltaire)]

Currently there is a duplication of port group definition in OpenSM configuration files.
Using a single configuration file for port groups will make it easier to manage and will allow using group name as keyword in other configuration files (i.e. partitions.conf, qos-policy.conf and opensm.conf)

The suggested format for port-groups.conf is a simple list:
GroupA: GUID1, GUID2, GUID3
GroupB: GUID4, GUID5, GUID6

All configuration files shall still support the old format (of specifying GUIDs explicitly) and will also recognize the new Groups.

Following an example of partitions.conf file with new group definition:
management=0x7fff,ipoib,defmember=full: GroupA=full, GroupB=limited, ALL_CAS=limited;

and qos-policy.conf with the new group definition:

port-groups
    port-group
        port-guid: GroupA, GroupB
        name: my.group
    end-port-group
end-port-groups


Thanks,
Eli
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: opensm: suggestion to define new common port_groups file

[Yevgeny Kliteynik]

On 03/Feb/10 11:43, Eli Dorfman (Voltaire) wrote:
> Currently there is a duplication of port group definition in OpenSM configuration files.
> Using a single configuration file for port groups will make it easier to manage and will allow using group name as keyword in other configuration files (i.e. partitions.conf, qos-policy.conf and opensm.conf)
>
> The suggested format for port-groups.conf is a simple list:
> GroupA: GUID1, GUID2, GUID3
> GroupB: GUID4, GUID5, GUID6
>
> All configuration files shall still support the old format (of specifying GUIDs explicitly) and will also recognize the new Groups.

I'm all for it!
  
> Following an example of partitions.conf file with new group definition:
> management=0x7fff,ipoib,defmember=full: GroupA=full, GroupB=limited, ALL_CAS=limited;
>
> and qos-policy.conf with the new group definition:
>
> port-groups
>      port-group
>          port-guid: GroupA, GroupB
>          name: my.group
>      end-port-group
> end-port-groups

Perhaps in qos-policy.conf we should be able to reference
GroupA and GroupB directly by its name, w/o the need to
create additional group like it is shown in the example.

Ideally, port-groups.conf parser should be able to
understand various keywords, such as what is used in
partitions.conf (ALL, SWITCHES, SELF, etc).

To complicate port-groups.conf parser a bit more, it would
be nice if it could support nested definition of port groups.

But no need to do it right away, we can start with something
simple.

-- Yevgeny

>
> Thanks,
> Eli
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: opensm: suggestion to define new common port_groups file

[Eli Dorfman]

On Wed, Feb 3, 2010 at 11:59 AM, Yevgeny Kliteynik
<kliteyn-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org> wrote:
> On 03/Feb/10 11:43, Eli Dorfman (Voltaire) wrote:
>>
>> Currently there is a duplication of port group definition in OpenSM
>> configuration files.
>> Using a single configuration file for port groups will make it easier to
>> manage and will allow using group name as keyword in other configuration
>> files (i.e. partitions.conf, qos-policy.conf and opensm.conf)
>>
>> The suggested format for port-groups.conf is a simple list:
>> GroupA: GUID1, GUID2, GUID3
>> GroupB: GUID4, GUID5, GUID6
>>
>> All configuration files shall still support the old format (of specifying
>> GUIDs explicitly) and will also recognize the new Groups.
>
> I'm all for it!
>
>>
>> Following an example of partitions.conf file with new group definition:
>> management=0x7fff,ipoib,defmember=full: GroupA=full, GroupB=limited,
>> ALL_CAS=limited;
>>
>> and qos-policy.conf with the new group definition:
>>
>> port-groups
>>     port-group
>>         port-guid: GroupA, GroupB
>>         name: my.group
>>     end-port-group
>> end-port-groups
>
> Perhaps in qos-policy.conf we should be able to reference
> GroupA and GroupB directly by its name, w/o the need to
> create additional group like it is shown in the example.

We can start with the simple suggestion as shown in the example and
then enhance as you suggest.

>
> Ideally, port-groups.conf parser should be able to
> understand various keywords, such as what is used in
> partitions.conf (ALL, SWITCHES, SELF, etc).
>
> To complicate port-groups.conf parser a bit more, it would
> be nice if it could support nested definition of port groups.
>
> But no need to do it right away, we can start with something
> simple.

I agree.

Eli
>
> -- Yevgeny
>
>>
>> Thanks,
>> Eli
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
>> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html