I agree with Morgan. We designed the current mapping functionality to
cover all the use cases we were aware of, but if there are more, then we
would love to hear about them and make the fixes that are necessary.
Attribute mapping is a critical component of federation, and it should
be fit for purpose

regards

David


On 03/11/2014 09:08, Morgan Fainberg wrote:
> 
> On Nov 2, 2014, at 22:21, Dolph Mathews <dolph.math...@gmail.com
> <mailto:dolph.math...@gmail.com>> wrote:
> 
>> On Sunday, November 2, 2014, John Dennis <jden...@redhat.com
>> <mailto:jden...@redhat.com>> wrote:
>>
>>     It was hoped we could simply borrow the Keystone mapping
>>     implementation but it was found to be too limiting and not
>>     sufficiently
>>     expressive. We could not find another alternative so we designed a new
>>     mapper which is described in this PDF.
>>
>>
>> In what way was it too limited? Did you consider extending the
>> existing grammar and extending the existing mapping engine?
> 
> I am very interested in knowing the limitations you ran into. I am
> fairly certain we are willing to update the engine to meet the needs of
> the deployers, but knowing what those limitations are and what this new
> proposed engine provides that we don't (for this use case) is important. 
> 
> --Morgan 
> 
> Sent via mobile
> 
> 
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 

_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to