[openstack-dev] [UX] Results Presentation: Managing OpenStack Quotas within Production Environments
The OpenStack UX team will be giving a results presentation from a series of interviews intended to understand how operators manage quotas at scale as well as the pain points associated with that process. The study was conducted by Danielle (IRC: uxdanielle) and included operators from CERN, Pacific Northwest National Laboratory, Workday, Intel and Universidade Federal de Campina Grande. The presentation begins in ~20 minutes. WebEx information to join the session can be found at the top of the UX wiki page: https://wiki.openstack.org/wiki/UX#Results_Presentation:_Managing_OpenStack_Quotas_within_Production_Environments Thanks for supporting UX research in the community! --Danielle __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [user-committee][scientific-wg][api][UX] Results Presentation: Managing OpenStack Quotas within Production Environments
(Apologies for cross-posting) The OpenStack UX team will be giving a presentation this Wednesday, 9/21 that summarizes results from a series of interviews intended to understand how operators manage quotas at scale as well as the pain points associated with that process. The study was conducted by Danielle Mundle (IRC: uxdanielle) and included operators from CERN, Pacific Northwest National Laboratory, Workday, Intel and Universidade Federal de Campina Grande and others. The presentation details can be found at the top of the OpenStack UX wiki: https://wiki.openstack.org/wiki/UX __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Ops] [UX] Video Posted - Results Presentation: Operator Information Needs
Hello all, We've recently uploaded a video presenting the findings from the recent UX research on information needs of operators. There will also be a session at the Ops Summit next week in NY around how to move forward with potential solutions. https://youtu.be/dktorTIqU5s Main findings: * Overall, operators tend to follow a similar process for information gathering: 1) Google or internal information search to isolate the problem 2) Reach out to an external source for alternate ideas – usually another co-worker or an operator in the community (indirectly via IRC or mailing list) 3) Comb through the code to check for more granular clues to pinpoint the issue * While participants acknowledged that total consolidation of all OpenStack information was out of scope, a common theme among ideal solutions was better organization of information. Potential solutions (in no particular order): - Create a knowledge base of problems encountered and solutions proposed - - Utilize a template to ensure a common structure for capturing environment info - - Collect “best practices” for common tasks - - Optimize search for Google results - - (Smaller company) access to other problem-solving resources provided by (larger) companies - More detailed OpenStack logging - - Having a greater number and/or better quality of operator-focused docs - - The ability to add comments to specific documentation pages - - Providing reference architectures as a learning tool Feel free to add your thoughts and comments! --Danielle IRC: uxdanielle __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
