[openstack-dev] [keystone] Feedback for upcoming user survey questionnaire

Steve Martinelli s.martinelli at gmail.com
Wed Jan 4 16:07:32 UTC 2017


I quite like Boris' last suggestion, with a minor tweak:

"In your opinion, what keystone feature(s) requires more attention (select
all that apply): "federation", "performance", "policy", "scaling out",
"backend support", "ldap"."

Unless someone has another suggestion I'll stick to the above.

On Wed, Jan 4, 2017 at 9:18 AM, Lance Bragstad <lbragstad at gmail.com> wrote:

> ++ to the suggestions Boris threw out. Answers to any of those would be
> valuable. In addition to that, I'd find any information about policy
> useful. Maybe something along the lines of "what changes to the policy
> files are you making, if any". This could be something that is asked
> OpenStack-wide (which I'm sure we've done at some point in the past) but it
> would also be interesting on a per-project basis.
>
> On Tue, Jan 3, 2017 at 3:05 PM, Boris Bobrov <bbobrov at mirantis.com> wrote:
>
>> "What were you trying to accomplish with keystone but failed"
>> "What functionality in keystone did you try to use but it wasn't good
>> enough"
>> "In your opinion, what in keystone requires most attention"
>> with choices "federation", "performance", "policy", "backend support"
>> and some other options.
>>
>> On 12/30/2016 11:54 PM, Steve Martinelli wrote:
>> > We have the opportunity to ask one question on the
>> > upcoming user survey and we get to decide the audience to which we serve
>> > the question.____
>> >
>> > __ __
>> >
>> > Our audience options are: USING, TESTING, or INTERESTED in Keystone (I
>> > think we should aim for USING or TESTING)
>> >
>> > __ __
>> >
>> > The question can take one of several forms; multiple choice (select one
>> > or more), or short answer.____
>> >
>> > __ __
>> >
>> > Post your suggestions here or email them to me privately ASAP so I can
>> > respond to the team assembling the survey in sufficient time.
>> >
>> >
>> >
>> > stevemar
>> >
>> >
>> > ____________________________________________________________
>> ______________
>> > OpenStack Development Mailing List (not for usage questions)
>> > Unsubscribe: OpenStack-dev-request at lists.op
>> enstack.org?subject:unsubscribe
>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> >
>>
>> ____________________________________________________________
>> ______________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170104/549948e1/attachment.html>


More information about the OpenStack-dev mailing list