https://wiki.openstack.org/w/api.php?action=feedcontributions&user=Liz+Blanchard&feedformat=atomOpenStack - User contributions [en]2024-03-28T16:53:21ZUser contributionsMediaWiki 1.28.2https://wiki.openstack.org/w/index.php?title=Past_internship_ideas&diff=89835Past internship ideas2015-09-09T15:02:18Z<p>Liz Blanchard: /* Horizon Concept Review and Usability Testing */</p>
<hr />
<div>== Documentation ==<br />
<br />
Mentors:<br />
** loquacities on IRC / openstack at lanabrindley dot com<br />
** asettle on IRC/ alexandra dot settle at rackspace dot com<br />
<br />
* Assist with the RST conversion of the Admin User Guide<br />
<br />
* Help with the Networking Guide: either with content, copyediting, or the RST conversion.<br />
<br />
* General bug work (find something interesting and work on it). This would look great on her resume as it's a solid visible contribution, but would also hopefully pay down some of our technical debt.<br />
<br />
* Choose a book/section of interest, and research and update that section. A good candidate here would be the API guides.<br />
<br />
== Community ==<br />
<br />
''To be announced'' <br />
<br />
Mentors:<br />
** hodepodge on IRC / chris at openstack org<br />
** EmilienM on IRC / emilien at redhat com<br />
** reed in IRC / stefano at openstack org<br />
<br />
<br />
== Coding ==<br />
<br />
See also [[:Category:Internship_idea|Ideas pages]].<br />
<br />
=== Neutron - metering agent add port statistics ===<br />
<br />
Description: <br />
<br />
In Neutron the metering agent [https://wiki.openstack.org/wiki/Neutron/Metering/Bandwidth] collects statistics regarding bandwidth usage. Right now it only measure the bandwidth used by routers. The idea is to extend it and provide statistics also for ports. In the first implementation only openvswitch will be supported, since we will use openvswitch tools to get the port statistics. <br />
The first step will be getting familiar with the metering agent and with Neutron in general. Then you will approach openvswitch tools and think about how to use them for this project. After that you can reach out to the community to collect and discuss ideas. Neutron folks are pretty active on #openstack-neutron channel most of the time and would be willing to share their opinions on this or any other project. You'll submit your code upstream and address the comments you get till your patch gets merged.<br />
<br />
Related blueprint: https://blueprints.launchpad.net/neutron/+spec/port-statistics<br />
<br />
Expected results: Patchsets submitted for review, reviewed by community members.<br />
<br />
Knowledge prerequisites: programming knowledge<br />
<br />
Nice-to-have knowledge: Python, Openvswitch<br />
<br />
Mentors: [[User:Rossella|Rossella Sblendido]]<br />
<br />
=== Redis jobboards ===<br />
<br />
The spec @ https://review.openstack.org/#/c/105298/ basically explains all of this (the why, what and where).<br />
<br />
{| class="wikitable"<br />
|-<br />
| Difficulty ||<br />
|-<br />
| Topics || [[TaskFlow|TaskFlow]], Distributed Systems<br />
|-<br />
| Required skills || Python <br />
|-<br />
| Extra skills || Distributed Systems <br />
|-<br />
| Mentor || Joshua Harlow (harlowja)<br />
|}<br />
<br />
=== Policy | Policy enforcement in OpenStack: Nova Scheduling and Policy integration ===<br />
<br />
{| class="wikitable"<br />
|-<br />
| Difficulty ||<br />
|-<br />
| Topics || [[GroupBasedPolicy|Policy]], [[Nova|Nova]]<br />
|-<br />
| Required skills ||<br />
|-<br />
| Extra skills ||<br />
|-<br />
| Mentor ||<br />
|}<br />
<br />
<br />
=== Test results dashboard ===<br />
<br />
Tasks:<br />
* Create an infra hosted dashboard view of testing results (both check/gate and periodic)<br />
<br />
{| class="wikitable"<br />
|-<br />
| Difficulty ||<br />
|-<br />
| Topics ||<br />
|-<br />
| Required skills ||<br />
|-<br />
| Extra skills ||<br />
|-<br />
| Mentor ||<br />
|}<br />
<br />
<br />
=== Policy | Policy-based intent-driven OpenStack Cloud Infrastructure ===<br />
<br />
See an example case study here: [http://www.openstack.org/vote-vancouver/presentation/meta-data-driven-cloud-running-openstack-scale-using-a-policy-framework-intel Meta-data Driven Cloud - Running OpenStack @ Scale Using a Policy Framework]<br />
<br />
Tasks:<br />
* Extension of intent-based policy framework to Compute and Storage<br />
* Policy-based service composition integration with OpenDaylight<br />
<br />
{| class="wikitable"<br />
|-<br />
| Difficulty || Moderate to Advanced<br />
|-<br />
| Topics || Functional and scenario testing framework<br />
|-<br />
| Required skills || OpenStack, Python<br />
|-<br />
| Extra skills ||<br />
|-<br />
| Mentor || Sumit Naiksatam, Magesh GV<br />
|}<br />
<br />
=== Rich Network Services in a Federated OpenStack Public Cloud ===<br />
<br />
L4-7 Services' integration, NFV, service function chaining, OpenDaylight<br />
<br />
{| class="wikitable"<br />
|-<br />
| Difficulty || Moderate to Advanced<br />
|-<br />
| Topics || Functional and scenario testing framework<br />
|-<br />
| Required skills || OpenStack, Python<br />
|-<br />
| Extra skills ||<br />
|-<br />
| Mentor || Sumit Naiksatam, Magesh GV<br />
|}<br />
<br />
=== Understand OpenStack Operations via Insights from Logs and Metrics: A Data Science Perspective ===<br />
<br />
Tasks:<br />
* How do we make sense out of logs?<br />
* How do we set up alarms based on specific events (identify events)<br />
* Anomaly detection from Logs<br />
<br />
{| class="wikitable"<br />
|-<br />
| Difficulty ||<br />
|-<br />
| Topics ||<br />
|-<br />
| Required skills || Experience/interest in algorithms<br />
|-<br />
| Extra skills ||<br />
|-<br />
| Mentor ||<br />
|}<br />
<br />
<br />
=== Keystone | Dynamic Policy ===<br />
<br />
The general idea is described at the blog post [http://adam.younglogic.com/2014/11/dynamic-policy-in-keystone/ Dynamic Policy in Keystone], by Adam Young.<br />
<br />
{| class="wikitable"<br />
|-<br />
| Difficulty || Medium<br />
|-<br />
| Topics || [[Keystone|Keystone]]<br />
|-<br />
| Required skills || Python<br />
|-<br />
| Extra skills ||<br />
|-<br />
| Mentor || David Stanek (dstanek), Samuel de Medeiros Queiroz (samueldmq)<br />
|}<br />
<br />
=== Keystone | Tokenless Operations ===<br />
<br />
The general idea is described at the blog post [http://adam.younglogic.com/2014/10/who-can-sign-for-what/ Who can sign for what?], by Adam Young.<br />
In few words, the fact of the signature on a document be valid does not mean that the signer was authorized to sign it.<br />
<br />
The proposed challenge is to create, based on existing mechanisms, an extension to Keystone client able to check if the the signer of a token was effectively authorized to sign tokens.<br />
<br />
Tasks:<br />
* Extract signer data out of the certificates;<br />
* Fetch the complete list of certificate from Keystone using the OS-SIMPLE-CERT extension;<br />
* Match the signer to the cert to validate the signature and extract the domain data for the token;<br />
* Fetch the mapping info from the Federation extension;<br />
* Use the mapping info to convert from the signing cert to a keystone user and groups;<br />
* Fetch the effective roles from Keystone for the user/groups for that domain;<br />
* Fetch policy from Keystone;<br />
* Execute the policy check to validate that the signer could sign for the data.<br />
<br />
{| class="wikitable"<br />
|-<br />
| Difficulty || Medium<br />
|-<br />
| Topics || [[Keystone|Keystone]]<br />
|-<br />
| Required skills || Python<br />
|-<br />
| Extra skills ||<br />
|-<br />
| Mentor || David Stanek (dstanek), Samuel de Medeiros Queiroz (samueldmq)<br />
|}<br />
<br />
=== Ceilometer ===<br />
<br />
Mentor: [[DinaBelova|Dina Belova]]<br />
<br />
Ceilometer team is currently working on new Time-Series storage concept for metrics. For now Gnocchi (Telemetry Stackforge project where we're trying to implement this kind of effort) lacks of the backend support (only Swift in place, InfluxDB and OpenTSDB still in progress). There is some interest to use Ceph directly instead of it. So we need direct-to-ceph usage from<br />
Gnocchi, possibly via the rados gateway REST API (as opposed to ceph-sitting-behind-swift-proxy as an alternative storage driver for Swift itself).<br />
<br />
=== Trove ===<br />
<br />
Mentor: [[User:iccha-sethi|Iccha Sethi]]<br />
<br />
Description: MySQL replication enhancements<br />
<br />
Work on trove enhancements for mysql replication.<br />
<br />
=== Glance - Swift ranged uploads ===<br />
<br />
Note(nikhil_k): This is a really challenging project. It would need a lot of research and motivation from candidate to perform the tasks. The tasks would also need to be defined by the candidate themselves to have a good "concurrent" distributed system as a end-result.<br />
<br />
Description: We currently retry the entire upload process if it fails. Need to add the ranged uploads logic from swift store to improve performance. Target repo - openstack/glance_store<br />
<br />
Glance folks are pretty active on #openstack-glance channel most of the time and would be willing to share their opinions on this or any other project.<br />
Please reach out on IRC to get a detailed information on this.<br />
<br />
Related blueprint: TBA<br />
<br />
Expected results: Patchsets submitted for review, reviewed by community members.<br />
<br />
Knowledge prerequisites: programming knowledge<br />
<br />
Nice-to-have knowledge: Python<br />
<br />
Mentors: [[User:nikhil|Nikhil Komawar]]<br />
<br />
=== Swift - storage server OPTIONS support and checker tool ===<br />
<br />
Many times new deployers get mysterious errors after first setting up their Swift clusters. Most of the time, the errors are because the values in the ring are incorrect (e.g. a bad port number). We need a way to validate that the rings actually match the deployment.<br />
<br />
http://tools.ietf.org/html/rfc7231#section-4.3.7 talks about the OPTIONS verb. Swift's proxy server already supports OPTIONS, but the storage nodes do not. The first task is to implement OPTIONS on the account, container, and object servers.<br />
<br />
Once the "OPTIONS *" functionality is implemented, swift-recon can be updated to include a ring checker. This checker would look at the ring and validate that there is something running on the server endpoints listed in the ring. Furthermore it would be able to actually check that the endpoint, if it's a real endpoint, is the right kind of endpoint (e.g. actually check that it's an object server). swift-recon would then generate a report of any found issues in the cluster.<br />
<br />
Expected results: patches written, submitted for review, and reviewed by the community<br />
<br />
Knowledge prerequisites: Python programming knowledge<br />
<br />
Nice-to-have knowledge: familiarity with HTTP protocols<br />
<br />
Mentors: [[User:notmyname|John Dickinson]]<br />
<br />
WIP Schedule: https://etherpad.openstack.org/p/iaR4TQZ7NP<br />
<br />
<br />
=== Swift - Improving the security of Swift's internal network ===<br />
<br />
Today all internal messages within a Swift cluster are unencrypted and unsigned. This means that all Swift deployments must be configured with a private, secure network for internal requests. This project is to add a cryptographic signature to all messages sent between Swift processes.<br />
<br />
Blueprint: https://blueprints.launchpad.net/swift/+spec/secure-internal-network-requests<br />
<br />
Expected results: patches written, submitted for review, and reviewed by the community<br />
<br />
Knowledge prerequisites: good Python programming knowledge, Swift's architecture, familiarity with HTTP<br />
<br />
Nice-to-have knowledge: familiarity with PKI<br />
<br />
Mentors: [[User:notmyname|John Dickinson]]<br />
<br />
WIP Schedule: https://etherpad.openstack.org/p/Wp3Hn7YY8p<br />
<br />
<br />
=== Swift/Swift3 - Improve S3 compatibility layer ===<br />
<br />
Improve the Swift3 middleware to get better S3 API coverage<br />
<br />
https://github.com/stackforge/swift3<br />
<br />
Mentors: [[User:notmyname|John Dickinson]]<br />
<br />
=== Proposed by applicants ===<br />
<br />
==== Keystone - Implementation of Attribute and Graph Based Access Control Model (AGBAC) for Openstack ====<br />
<br />
Proposed by: Tahmina Ahmed - Tahmina<br />
<br />
Description: The Core Openstack Access Control Module according to identity API V3 (user, token,project, domain, group, role association) [0] can be abstracted as a graph:<br />
<br /><br />
<br />
[[File:OSACFinal.jpg|Openstack Access Control According to Identity API V3 ]]<br />
<br /><br />
<br />
Attribute of different entities and the relationship between them and attribute of the relationship can be expressed through property graph [2] where entities are nodes and relationships are edges and both nodes and edges has attribute. Using entities and their attributes and relationship between entities and attribute of relationship to specify authorization policy will allow a system to have more finer grained access control model. For this representation, OpenStack entities (user, group, role, project, domain) are represented as nodes in the graph and the attributes and association between any two of them can be depicted as attributed edges. Given that a role is associated with a user and a project where the association is temporal, if we can say that the association is only active from 8am to 5pm this is something to say about the user- project- role association. We can express this as an attribute of the user- project and project - role association edge and use this for authorization to findout active roles. <br />
<br />
This implementation plan is to make minimum impact on services outside keystone.So the plan is to like computing authorization path specification for a certain time when user requests for a token and and return a list of active roles. In that case this extension to the authorization model is transparent to all other openstack services like nova, glance, cynder etc. <br />
<br />
Steps to Implement AGBAC in Openstack <br />
<br />
1. Define API and Storage for Specifying Attributes of different entities <br />
2. Define storage Assignment Attributes.<br />
3. Define API to set the entity attributes<br />
4. Define API to set the association attributes<br />
5. A Policy specification storage that would specify path based policy to compute roles.<br />
6. A Compute function that would compute the roles using entites, their attributes relationship between entities attribute of relationships and policy.<br />
<br />
[0] Bo Tang and Ravi Sandhu, Extending Openstack Access Control With Domain Trust. In Proceedings 8th International Conference on Network and System Security (NSS 2014), Xi'an, China, October 15-17, 2014, 15 pages<br />
<br />
[1] http://neo4j.com/<br />
<br />
[2] Rodriguez, Marko A., and Peter Neubauer. "Constructions from dots and lines." Bulletin of the American Society for Information Science and Technology 36.6 (2010): 35-41.<br />
<br />
== Design ==<br />
<br />
=== Persona research and design for Horizon UI ===<br />
<br />
Description: <br />
There has been some initial work done in a few different areas around generating Personas for the Horizon UI. This task/project would allow someone to lead the effort to pull the research together, perhaps perform further end-user interviews or surveys, analyze data, form groups of personas, and put together an initial set of target Horizon personas that we can use during requirements gathering, design phases, and general discussion.<br />
<br />
Related blueprint: https://blueprints.launchpad.net/openstack-ux/+spec/horizon-personas<br />
<br />
Expected results: Initial set of Personas for people to use during requirements gathering, design phases, and general discussion of our target Horizon users.<br />
<br />
Knowledge prerequisites: basic interviewing skills, willingness to talk with a lot of new people, readiness to listen and report back findings<br />
<br />
Nice-to-have knowledge: User Experience Design basics<br />
<br />
Mentors: [[User:julim|Ju Lim]]<br />
<br />
=== Redesign for the Object Storage -> Containers section in Horizon ===<br />
<br />
Description: <br />
<br />
Currently, there is a section under the Object Storage panel that allows users (e.g. Consumers and/or Project Administrators) to Create, Delete, and Edit Containers. It would be great to do a little bit of research into identifying the use cases around these features and then proposing a redesign of these features based on the findings. This will include learning some basic Usability best practices and applying them to a design. The design would be done in wireframe format, so it could be done in any tool that allows for this. The design would be reviewed on the UX AskBot site, a new blueprint would need to be created as well. This would take a new designer through the process that currently exists for proposing an updated design to a current feature in Horizon.<br />
<br />
Related blueprint: N/A (To be created by intern as part of process)<br />
<br />
Expected results: Redesign of "Containers" section in Object Storage panel proposed and approved by Horizon community.<br />
<br />
Knowledge prerequisites: basic sketching or wireframing skills<br />
<br />
Nice-to-have knowledge: User Experience Design basics<br />
<br />
Mentor: [[User:julim|Ju Lim]]<br />
<br />
=== Horizon Concept Review and Usability Testing ===<br />
<br />
Description: There has been very little work done around Horizon UI concept reviews and usability testing. This task/project would allow someone to lead the effort to put together a test plan, identify customers as test participants, conduct (contextual) inquiry / interview, survey users, analyze data to share results / findings with the community findings regarding how current production OpenStack users are using the software, their use cases, and whether the Horizon UI meets their needs. Along the way, you may identify areas of improvement, concepts that need further refinement, and new use cases or opportunities that have not yet been addressed.<br />
<br />
Related blueprint: https://blueprints.launchpad.net/openstack-ux/+spec/ux-users-community-testing<br />
<br />
Expected results: (1) Identify a community of users willing to participate in Horizon UI usability testing and participate in various OpenStack concept reviews. (2) Share usability test findings with the community that will be used for design and general Horizon discussions.<br />
<br />
Knowledge prerequisites: usability testing skills, basic interviewing skills, willingness to talk with a lot of new people, readiness to listen and report back findings, ability to analyze data to find patterns.<br />
<br />
Nice-to-have knowledge: User Experience Design and/or User Research basics<br />
<br />
Mentors: [[User:julim|Ju Lim]]</div>Liz Blanchardhttps://wiki.openstack.org/w/index.php?title=Past_internship_ideas&diff=89834Past internship ideas2015-09-09T15:01:50Z<p>Liz Blanchard: /* Redesign for the Object Storage -> Containers section in Horizon */</p>
<hr />
<div>== Documentation ==<br />
<br />
Mentors:<br />
** loquacities on IRC / openstack at lanabrindley dot com<br />
** asettle on IRC/ alexandra dot settle at rackspace dot com<br />
<br />
* Assist with the RST conversion of the Admin User Guide<br />
<br />
* Help with the Networking Guide: either with content, copyediting, or the RST conversion.<br />
<br />
* General bug work (find something interesting and work on it). This would look great on her resume as it's a solid visible contribution, but would also hopefully pay down some of our technical debt.<br />
<br />
* Choose a book/section of interest, and research and update that section. A good candidate here would be the API guides.<br />
<br />
== Community ==<br />
<br />
''To be announced'' <br />
<br />
Mentors:<br />
** hodepodge on IRC / chris at openstack org<br />
** EmilienM on IRC / emilien at redhat com<br />
** reed in IRC / stefano at openstack org<br />
<br />
<br />
== Coding ==<br />
<br />
See also [[:Category:Internship_idea|Ideas pages]].<br />
<br />
=== Neutron - metering agent add port statistics ===<br />
<br />
Description: <br />
<br />
In Neutron the metering agent [https://wiki.openstack.org/wiki/Neutron/Metering/Bandwidth] collects statistics regarding bandwidth usage. Right now it only measure the bandwidth used by routers. The idea is to extend it and provide statistics also for ports. In the first implementation only openvswitch will be supported, since we will use openvswitch tools to get the port statistics. <br />
The first step will be getting familiar with the metering agent and with Neutron in general. Then you will approach openvswitch tools and think about how to use them for this project. After that you can reach out to the community to collect and discuss ideas. Neutron folks are pretty active on #openstack-neutron channel most of the time and would be willing to share their opinions on this or any other project. You'll submit your code upstream and address the comments you get till your patch gets merged.<br />
<br />
Related blueprint: https://blueprints.launchpad.net/neutron/+spec/port-statistics<br />
<br />
Expected results: Patchsets submitted for review, reviewed by community members.<br />
<br />
Knowledge prerequisites: programming knowledge<br />
<br />
Nice-to-have knowledge: Python, Openvswitch<br />
<br />
Mentors: [[User:Rossella|Rossella Sblendido]]<br />
<br />
=== Redis jobboards ===<br />
<br />
The spec @ https://review.openstack.org/#/c/105298/ basically explains all of this (the why, what and where).<br />
<br />
{| class="wikitable"<br />
|-<br />
| Difficulty ||<br />
|-<br />
| Topics || [[TaskFlow|TaskFlow]], Distributed Systems<br />
|-<br />
| Required skills || Python <br />
|-<br />
| Extra skills || Distributed Systems <br />
|-<br />
| Mentor || Joshua Harlow (harlowja)<br />
|}<br />
<br />
=== Policy | Policy enforcement in OpenStack: Nova Scheduling and Policy integration ===<br />
<br />
{| class="wikitable"<br />
|-<br />
| Difficulty ||<br />
|-<br />
| Topics || [[GroupBasedPolicy|Policy]], [[Nova|Nova]]<br />
|-<br />
| Required skills ||<br />
|-<br />
| Extra skills ||<br />
|-<br />
| Mentor ||<br />
|}<br />
<br />
<br />
=== Test results dashboard ===<br />
<br />
Tasks:<br />
* Create an infra hosted dashboard view of testing results (both check/gate and periodic)<br />
<br />
{| class="wikitable"<br />
|-<br />
| Difficulty ||<br />
|-<br />
| Topics ||<br />
|-<br />
| Required skills ||<br />
|-<br />
| Extra skills ||<br />
|-<br />
| Mentor ||<br />
|}<br />
<br />
<br />
=== Policy | Policy-based intent-driven OpenStack Cloud Infrastructure ===<br />
<br />
See an example case study here: [http://www.openstack.org/vote-vancouver/presentation/meta-data-driven-cloud-running-openstack-scale-using-a-policy-framework-intel Meta-data Driven Cloud - Running OpenStack @ Scale Using a Policy Framework]<br />
<br />
Tasks:<br />
* Extension of intent-based policy framework to Compute and Storage<br />
* Policy-based service composition integration with OpenDaylight<br />
<br />
{| class="wikitable"<br />
|-<br />
| Difficulty || Moderate to Advanced<br />
|-<br />
| Topics || Functional and scenario testing framework<br />
|-<br />
| Required skills || OpenStack, Python<br />
|-<br />
| Extra skills ||<br />
|-<br />
| Mentor || Sumit Naiksatam, Magesh GV<br />
|}<br />
<br />
=== Rich Network Services in a Federated OpenStack Public Cloud ===<br />
<br />
L4-7 Services' integration, NFV, service function chaining, OpenDaylight<br />
<br />
{| class="wikitable"<br />
|-<br />
| Difficulty || Moderate to Advanced<br />
|-<br />
| Topics || Functional and scenario testing framework<br />
|-<br />
| Required skills || OpenStack, Python<br />
|-<br />
| Extra skills ||<br />
|-<br />
| Mentor || Sumit Naiksatam, Magesh GV<br />
|}<br />
<br />
=== Understand OpenStack Operations via Insights from Logs and Metrics: A Data Science Perspective ===<br />
<br />
Tasks:<br />
* How do we make sense out of logs?<br />
* How do we set up alarms based on specific events (identify events)<br />
* Anomaly detection from Logs<br />
<br />
{| class="wikitable"<br />
|-<br />
| Difficulty ||<br />
|-<br />
| Topics ||<br />
|-<br />
| Required skills || Experience/interest in algorithms<br />
|-<br />
| Extra skills ||<br />
|-<br />
| Mentor ||<br />
|}<br />
<br />
<br />
=== Keystone | Dynamic Policy ===<br />
<br />
The general idea is described at the blog post [http://adam.younglogic.com/2014/11/dynamic-policy-in-keystone/ Dynamic Policy in Keystone], by Adam Young.<br />
<br />
{| class="wikitable"<br />
|-<br />
| Difficulty || Medium<br />
|-<br />
| Topics || [[Keystone|Keystone]]<br />
|-<br />
| Required skills || Python<br />
|-<br />
| Extra skills ||<br />
|-<br />
| Mentor || David Stanek (dstanek), Samuel de Medeiros Queiroz (samueldmq)<br />
|}<br />
<br />
=== Keystone | Tokenless Operations ===<br />
<br />
The general idea is described at the blog post [http://adam.younglogic.com/2014/10/who-can-sign-for-what/ Who can sign for what?], by Adam Young.<br />
In few words, the fact of the signature on a document be valid does not mean that the signer was authorized to sign it.<br />
<br />
The proposed challenge is to create, based on existing mechanisms, an extension to Keystone client able to check if the the signer of a token was effectively authorized to sign tokens.<br />
<br />
Tasks:<br />
* Extract signer data out of the certificates;<br />
* Fetch the complete list of certificate from Keystone using the OS-SIMPLE-CERT extension;<br />
* Match the signer to the cert to validate the signature and extract the domain data for the token;<br />
* Fetch the mapping info from the Federation extension;<br />
* Use the mapping info to convert from the signing cert to a keystone user and groups;<br />
* Fetch the effective roles from Keystone for the user/groups for that domain;<br />
* Fetch policy from Keystone;<br />
* Execute the policy check to validate that the signer could sign for the data.<br />
<br />
{| class="wikitable"<br />
|-<br />
| Difficulty || Medium<br />
|-<br />
| Topics || [[Keystone|Keystone]]<br />
|-<br />
| Required skills || Python<br />
|-<br />
| Extra skills ||<br />
|-<br />
| Mentor || David Stanek (dstanek), Samuel de Medeiros Queiroz (samueldmq)<br />
|}<br />
<br />
=== Ceilometer ===<br />
<br />
Mentor: [[DinaBelova|Dina Belova]]<br />
<br />
Ceilometer team is currently working on new Time-Series storage concept for metrics. For now Gnocchi (Telemetry Stackforge project where we're trying to implement this kind of effort) lacks of the backend support (only Swift in place, InfluxDB and OpenTSDB still in progress). There is some interest to use Ceph directly instead of it. So we need direct-to-ceph usage from<br />
Gnocchi, possibly via the rados gateway REST API (as opposed to ceph-sitting-behind-swift-proxy as an alternative storage driver for Swift itself).<br />
<br />
=== Trove ===<br />
<br />
Mentor: [[User:iccha-sethi|Iccha Sethi]]<br />
<br />
Description: MySQL replication enhancements<br />
<br />
Work on trove enhancements for mysql replication.<br />
<br />
=== Glance - Swift ranged uploads ===<br />
<br />
Note(nikhil_k): This is a really challenging project. It would need a lot of research and motivation from candidate to perform the tasks. The tasks would also need to be defined by the candidate themselves to have a good "concurrent" distributed system as a end-result.<br />
<br />
Description: We currently retry the entire upload process if it fails. Need to add the ranged uploads logic from swift store to improve performance. Target repo - openstack/glance_store<br />
<br />
Glance folks are pretty active on #openstack-glance channel most of the time and would be willing to share their opinions on this or any other project.<br />
Please reach out on IRC to get a detailed information on this.<br />
<br />
Related blueprint: TBA<br />
<br />
Expected results: Patchsets submitted for review, reviewed by community members.<br />
<br />
Knowledge prerequisites: programming knowledge<br />
<br />
Nice-to-have knowledge: Python<br />
<br />
Mentors: [[User:nikhil|Nikhil Komawar]]<br />
<br />
=== Swift - storage server OPTIONS support and checker tool ===<br />
<br />
Many times new deployers get mysterious errors after first setting up their Swift clusters. Most of the time, the errors are because the values in the ring are incorrect (e.g. a bad port number). We need a way to validate that the rings actually match the deployment.<br />
<br />
http://tools.ietf.org/html/rfc7231#section-4.3.7 talks about the OPTIONS verb. Swift's proxy server already supports OPTIONS, but the storage nodes do not. The first task is to implement OPTIONS on the account, container, and object servers.<br />
<br />
Once the "OPTIONS *" functionality is implemented, swift-recon can be updated to include a ring checker. This checker would look at the ring and validate that there is something running on the server endpoints listed in the ring. Furthermore it would be able to actually check that the endpoint, if it's a real endpoint, is the right kind of endpoint (e.g. actually check that it's an object server). swift-recon would then generate a report of any found issues in the cluster.<br />
<br />
Expected results: patches written, submitted for review, and reviewed by the community<br />
<br />
Knowledge prerequisites: Python programming knowledge<br />
<br />
Nice-to-have knowledge: familiarity with HTTP protocols<br />
<br />
Mentors: [[User:notmyname|John Dickinson]]<br />
<br />
WIP Schedule: https://etherpad.openstack.org/p/iaR4TQZ7NP<br />
<br />
<br />
=== Swift - Improving the security of Swift's internal network ===<br />
<br />
Today all internal messages within a Swift cluster are unencrypted and unsigned. This means that all Swift deployments must be configured with a private, secure network for internal requests. This project is to add a cryptographic signature to all messages sent between Swift processes.<br />
<br />
Blueprint: https://blueprints.launchpad.net/swift/+spec/secure-internal-network-requests<br />
<br />
Expected results: patches written, submitted for review, and reviewed by the community<br />
<br />
Knowledge prerequisites: good Python programming knowledge, Swift's architecture, familiarity with HTTP<br />
<br />
Nice-to-have knowledge: familiarity with PKI<br />
<br />
Mentors: [[User:notmyname|John Dickinson]]<br />
<br />
WIP Schedule: https://etherpad.openstack.org/p/Wp3Hn7YY8p<br />
<br />
<br />
=== Swift/Swift3 - Improve S3 compatibility layer ===<br />
<br />
Improve the Swift3 middleware to get better S3 API coverage<br />
<br />
https://github.com/stackforge/swift3<br />
<br />
Mentors: [[User:notmyname|John Dickinson]]<br />
<br />
=== Proposed by applicants ===<br />
<br />
==== Keystone - Implementation of Attribute and Graph Based Access Control Model (AGBAC) for Openstack ====<br />
<br />
Proposed by: Tahmina Ahmed - Tahmina<br />
<br />
Description: The Core Openstack Access Control Module according to identity API V3 (user, token,project, domain, group, role association) [0] can be abstracted as a graph:<br />
<br /><br />
<br />
[[File:OSACFinal.jpg|Openstack Access Control According to Identity API V3 ]]<br />
<br /><br />
<br />
Attribute of different entities and the relationship between them and attribute of the relationship can be expressed through property graph [2] where entities are nodes and relationships are edges and both nodes and edges has attribute. Using entities and their attributes and relationship between entities and attribute of relationship to specify authorization policy will allow a system to have more finer grained access control model. For this representation, OpenStack entities (user, group, role, project, domain) are represented as nodes in the graph and the attributes and association between any two of them can be depicted as attributed edges. Given that a role is associated with a user and a project where the association is temporal, if we can say that the association is only active from 8am to 5pm this is something to say about the user- project- role association. We can express this as an attribute of the user- project and project - role association edge and use this for authorization to findout active roles. <br />
<br />
This implementation plan is to make minimum impact on services outside keystone.So the plan is to like computing authorization path specification for a certain time when user requests for a token and and return a list of active roles. In that case this extension to the authorization model is transparent to all other openstack services like nova, glance, cynder etc. <br />
<br />
Steps to Implement AGBAC in Openstack <br />
<br />
1. Define API and Storage for Specifying Attributes of different entities <br />
2. Define storage Assignment Attributes.<br />
3. Define API to set the entity attributes<br />
4. Define API to set the association attributes<br />
5. A Policy specification storage that would specify path based policy to compute roles.<br />
6. A Compute function that would compute the roles using entites, their attributes relationship between entities attribute of relationships and policy.<br />
<br />
[0] Bo Tang and Ravi Sandhu, Extending Openstack Access Control With Domain Trust. In Proceedings 8th International Conference on Network and System Security (NSS 2014), Xi'an, China, October 15-17, 2014, 15 pages<br />
<br />
[1] http://neo4j.com/<br />
<br />
[2] Rodriguez, Marko A., and Peter Neubauer. "Constructions from dots and lines." Bulletin of the American Society for Information Science and Technology 36.6 (2010): 35-41.<br />
<br />
== Design ==<br />
<br />
=== Persona research and design for Horizon UI ===<br />
<br />
Description: <br />
There has been some initial work done in a few different areas around generating Personas for the Horizon UI. This task/project would allow someone to lead the effort to pull the research together, perhaps perform further end-user interviews or surveys, analyze data, form groups of personas, and put together an initial set of target Horizon personas that we can use during requirements gathering, design phases, and general discussion.<br />
<br />
Related blueprint: https://blueprints.launchpad.net/openstack-ux/+spec/horizon-personas<br />
<br />
Expected results: Initial set of Personas for people to use during requirements gathering, design phases, and general discussion of our target Horizon users.<br />
<br />
Knowledge prerequisites: basic interviewing skills, willingness to talk with a lot of new people, readiness to listen and report back findings<br />
<br />
Nice-to-have knowledge: User Experience Design basics<br />
<br />
Mentors: [[User:julim|Ju Lim]]<br />
<br />
=== Redesign for the Object Storage -> Containers section in Horizon ===<br />
<br />
Description: <br />
<br />
Currently, there is a section under the Object Storage panel that allows users (e.g. Consumers and/or Project Administrators) to Create, Delete, and Edit Containers. It would be great to do a little bit of research into identifying the use cases around these features and then proposing a redesign of these features based on the findings. This will include learning some basic Usability best practices and applying them to a design. The design would be done in wireframe format, so it could be done in any tool that allows for this. The design would be reviewed on the UX AskBot site, a new blueprint would need to be created as well. This would take a new designer through the process that currently exists for proposing an updated design to a current feature in Horizon.<br />
<br />
Related blueprint: N/A (To be created by intern as part of process)<br />
<br />
Expected results: Redesign of "Containers" section in Object Storage panel proposed and approved by Horizon community.<br />
<br />
Knowledge prerequisites: basic sketching or wireframing skills<br />
<br />
Nice-to-have knowledge: User Experience Design basics<br />
<br />
Mentor: [[User:julim|Ju Lim]]<br />
<br />
=== Horizon Concept Review and Usability Testing ===<br />
<br />
Description: There has been very little work done around Horizon UI concept reviews and usability testing. This task/project would allow someone to lead the effort to put together a test plan, identify customers as test participants, conduct (contextual) inquiry / interview, survey users, analyze data to share results / findings with the community findings regarding how current production OpenStack users are using the software, their use cases, and whether the Horizon UI meets their needs. Along the way, you may identify areas of improvement, concepts that need further refinement, and new use cases or opportunities that have not yet been addressed.<br />
<br />
Related blueprint: https://blueprints.launchpad.net/openstack-ux/+spec/ux-users-community-testing<br />
<br />
Expected results: (1) Identify a community of users willing to participate in Horizon UI usability testing and participate in various OpenStack concept reviews. (2) Share usability test findings with the community that will be used for design and general Horizon discussions.<br />
<br />
Knowledge prerequisites: usability testing skills, basic interviewing skills, willingness to talk with a lot of new people, readiness to listen and report back findings, ability to analyze data to find patterns.<br />
<br />
Nice-to-have knowledge: User Experience Design and/or User Research basics<br />
<br />
Mentors: [[User:julim|Ju Lim]], [[User:lblanchard|Liz Blanchard]]</div>Liz Blanchardhttps://wiki.openstack.org/w/index.php?title=Internship_ideas&diff=75499Internship ideas2015-03-12T18:35:07Z<p>Liz Blanchard: </p>
<hr />
<div><!-- ## page was renamed from [[GnomeOutreachWomen]]/Ideas --><br />
= Outreachy Ideas List =<br />
<br />
The GNOME Foundation provides an outreach program for women. You can learn more here: https://www.gnome.org/outreachy/.<br />
<br />
OpenStack would like to participate as a project for the May 2015 to August 2015 round. We are still identifying mentors and have sponsorship from the OpenStack Foundation. This page should collect the ideas for applicants to work on. <br />
<br />
Outreachy emphasizes that applicants may not have ever worked on FLOSS before. There are several stages to the program, but the first stage is to mentor during the application process itself. Joining mailing lists, IRC, understanding the channels of communication are good first steps. Logging bugs and fixing bugs are also good ideas. <br />
<br />
Interns are expected to spend 40 hours a week on the project. <br />
<br />
So, feel free to list ideas here:<br />
<br />
== Coding ==<br />
<br />
=== Zaqar: zaqar-pythonclient support for Zaqar API v1.1 ===<br />
<br />
Mentor: [[User:Vkmc|Victoria Martinez de la Cruz]]<br />
<br />
Currently there are three versions of Zaqar API: v1, v1.1 and v2.0 (under heavy development). zaqar-pythonclient has full support for all the features in API v1, but its missing support for some features in API v1.1. This task would require to learn and understand the new features provided in API v1.1 and add support for them client side.<br />
<br />
Difficulty: Normal<br />
Required skills: Python<br />
<br />
=== Zaqar: Creation of a Zaqar panel for Horizon ===<br />
<br />
Mentor: [[User:Vkmc|Victoria Martinez de la Cruz]]<br />
<br />
Right now the only way to use Zaqar is through the API. The creation of a panel for Horizon would make Zaqar more user friendly. This task would require to learn and understand how panels are created in Horizon, to select Zaqar features to expose, to create a UI for it and do the implementation afterwards.<br />
<br />
Difficulty: Hard<br />
Required skills: Python, Django, Javascript<br />
<br />
=== Neutron - metering agent add port statistics ===<br />
<br />
Description: <br />
<br />
In Neutron the metering agent [https://wiki.openstack.org/wiki/Neutron/Metering/Bandwidth] collects statistics regarding bandwidth usage. Right now it only measure the bandwidth used by routers. The idea is to extend it and provide statistics also for ports. In the first implementation only openvswitch will be supported, since we will use openvswitch tools to get the port statistics. <br />
The first step will be getting familiar with the metering agent and with Neutron in general. Then you will approach openvswitch tools and think about how to use them for this project. After that you can reach out to the community to collect and discuss ideas. Neutron folks are pretty active on #openstack-neutron channel most of the time and would be willing to share their opinions on this or any other project. You'll submit your code upstream and address the comments you get till your patch gets merged.<br />
<br />
Related blueprint: https://blueprints.launchpad.net/neutron/+spec/port-statistics<br />
<br />
Expected results: Patchsets submitted for review, reviewed by community members.<br />
<br />
Knowledge prerequisites: programming knowledge<br />
<br />
Nice-to-have knowledge: Python, Openvswitch<br />
<br />
Mentors: [[User:Rossella|Rossella Sblendido]]<br />
<br />
== Documentation ==<br />
<br />
Mentors:<br />
** loquacities on IRC / lana dot brindley at rackspace dot com<br />
** asettle on IRC/ alexandra dot settle at rackspace dot com<br />
<br />
* Assist with the RST conversion of the Admin User Guide<br />
<br />
* Help with the Networking Guide: either with content, copyediting, or the RST conversion.<br />
<br />
* General bug work (find something interesting and work on it). This would look great on her resume as it's a solid visible contribution, but would also hopefully pay down some of our technical debt.<br />
<br />
* Choose a book/section of interest, and research and update that section. A good candidate here would be the API guides.<br />
<br />
<big>'''Ideas below this point correspond to the last Outreachy round (December 2014 - March 2015). This means that they may not be available anymore. Please ask the mentor listed about it'''</big><br />
<br />
<br />
== Community ==<br />
<br />
* Write puppet scripts to automatically deploy/manage Ask OpenStack<br />
<br />
Mentors:<br />
** hodepodge on IRC / chris at openstack org<br />
** EmilienM on IRC / emilien at redhat com<br />
<br />
== Coding ==<br />
<br />
=== Ceilometer ===<br />
<br />
Mentor: [[DinaBelova|Dina Belova]]<br />
<br />
Ceilometer team is currently working on new Time-Series storage concept for metrics. For now Gnocchi (Telemetry Stackforge project where we're trying to implement this kind of effort) lacks of the backend support (only Swift in place, InfluxDB and OpenTSDB still in progress). There is some interest to use Ceph directly instead of it. So we need direct-to-ceph usage from<br />
Gnocchi, possibly via the rados gateway REST API (as opposed to ceph-sitting-behind-swift-proxy as an alternative storage driver for Swift itself).<br />
<br />
=== Zaqar: Split data/control planes ===<br />
<br />
Mentor: [[User:flaper87|Flavio Percoco]]<br />
<br />
Zaqar has 2 different logical "data-planes". One is used to control the state of the system and other administrative operations - pools, flavors, etc - and the other is used for the actual data going through Zaqar - queues, messages, etc. These 2 data planes currently share lots of things like config options, modules and more. The team has been willing to split these 2 logically different planes into isolated modules and configs.<br />
<br />
This task will give the mentee great insights on Zaqar's architecture, logic and also more general information on how some messaging patterns are implemented in the system. This task is a great intro to Zaqar, to OpenStack and to messaging technologies with enough complexity to help the mentee grow.<br />
<br />
* Expected Results: Both planes should be completely separate<br />
* Required Knowedge: Python<br />
<br />
=== Trove ===<br />
<br />
Mentor: [[User:iccha-sethi|Iccha Sethi]]<br />
<br />
Description: MySQL replication enhancements<br />
<br />
Work on trove enhancements for mysql replication.<br />
<br />
=== Glance - Implement Tasks scrubber ===<br />
<br />
Description: Glance Tasks are currently never deleted. This project would involve writing a scrubber logic for soft-deleting tasks as a part of Glance codebase.<br />
<br />
Glance folks are pretty active on #openstack-glance channel most of the time and would be willing to share their opinions on this or any other project.<br />
Please reach out on IRC to get a detailed information on this.<br />
<br />
Initial blueprint: https://blueprints.launchpad.net/glance/+spec/async-glance-workers . A new BP would be needed to get this implemented. It would also be a responsibility of the candidate.<br />
<br />
Expected results: Patchsets submitted for review, reviewed by community members.<br />
<br />
Knowledge prerequisites: programming knowledge<br />
<br />
Nice-to-have knowledge: Python<br />
<br />
Mentors: [[User:nikhil|Nikhil Komawar]]<br />
<br />
=== Glance - Swift ranged uploads ===<br />
<br />
Note(nikhil_k): This is a really challenging project. It would need a lot of research and motivation from candidate to perform the tasks. The tasks would also need to be defined by the candidate themselves to have a good "concurrent" distributed system as a end-result.<br />
<br />
Description: We currently retry the entire upload process if it fails. Need to add the ranged uploads logic from swift store to improve performance. Target repo - openstack/glance_store<br />
<br />
Glance folks are pretty active on #openstack-glance channel most of the time and would be willing to share their opinions on this or any other project.<br />
Please reach out on IRC to get a detailed information on this.<br />
<br />
Related blueprint: TBA<br />
<br />
Expected results: Patchsets submitted for review, reviewed by community members.<br />
<br />
Knowledge prerequisites: programming knowledge<br />
<br />
Nice-to-have knowledge: Python<br />
<br />
Mentors: [[User:nikhil|Nikhil Komawar]]<br />
<br />
=== Swift - storage server OPTIONS support and checker tool ===<br />
<br />
Many times new deployers get mysterious errors after first setting up their Swift clusters. Most of the time, the errors are because the values in the ring are incorrect (e.g. a bad port number). We need a way to validate that the rings actually match the deployment.<br />
<br />
http://tools.ietf.org/html/rfc7231#section-4.3.7 talks about the OPTIONS verb. Swift's proxy server already supports OPTIONS, but the storage nodes do not. The first task is to implement OPTIONS on the account, container, and object servers.<br />
<br />
Once the "OPTIONS *" functionality is implemented, swift-recon can be updated to include a ring checker. This checker would look at the ring and validate that there is something running on the server endpoints listed in the ring. Furthermore it would be able to actually check that the endpoint, if it's a real endpoint, is the right kind of endpoint (e.g. actually check that it's an object server). swift-recon would then generate a report of any found issues in the cluster.<br />
<br />
Expected results: patches written, submitted for review, and reviewed by the community<br />
<br />
Knowledge prerequisites: Python programming knowledge<br />
<br />
Nice-to-have knowledge: familiarity with HTTP protocols<br />
<br />
Mentors: [[User:notmyname|John Dickinson]]<br />
<br />
WIP Schedule: https://etherpad.openstack.org/p/iaR4TQZ7NP<br />
<br />
<br />
=== Swift - Improving the security of Swift's internal network ===<br />
<br />
Today all internal messages within a Swift cluster are unencrypted and unsigned. This means that all Swift deployments must be configured with a private, secure network for internal requests. This project is to add a cryptographic signature to all messages sent between Swift processes.<br />
<br />
Blueprint: https://blueprints.launchpad.net/swift/+spec/secure-internal-network-requests<br />
<br />
Expected results: patches written, submitted for review, and reviewed by the community<br />
<br />
Knowledge prerequisites: good Python programming knowledge, Swift's architecture, familiarity with HTTP<br />
<br />
Nice-to-have knowledge: familiarity with PKI<br />
<br />
Mentors: [[User:notmyname|John Dickinson]]<br />
<br />
WIP Schedule: https://etherpad.openstack.org/p/Wp3Hn7YY8p<br />
<br />
<br />
=== Swift/Swift3 - Improve S3 compatibility layer ===<br />
<br />
Improve the Swift3 middleware to get better S3 API coverage<br />
<br />
https://github.com/stackforge/swift3<br />
<br />
Mentors: [[User:notmyname|John Dickinson]]<br />
<br />
=== Proposed by applicants ===<br />
<br />
==== Keystone - Implementation of Attribute and Graph Based Access Control Model (AGBAC) for Openstack ====<br />
<br />
Proposed by: Tahmina Ahmed - Tahmina<br />
<br />
Description: The Core Openstack Access Control Module according to identity API V3 (user, token,project, domain, group, role association) [0] can be abstracted as a graph:<br />
<br /><br />
<br />
[[File:OSACFinal.jpg|Openstack Access Control According to Identity API V3 ]]<br />
<br /><br />
<br />
Attribute of different entities and the relationship between them and attribute of the relationship can be expressed through property graph [2] where entities are nodes and relationships are edges and both nodes and edges has attribute. Using entities and their attributes and relationship between entities and attribute of relationship to specify authorization policy will allow a system to have more finer grained access control model. For this representation, OpenStack entities (user, group, role, project, domain) are represented as nodes in the graph and the attributes and association between any two of them can be depicted as attributed edges. Given that a role is associated with a user and a project where the association is temporal, if we can say that the association is only active from 8am to 5pm this is something to say about the user- project- role association. We can express this as an attribute of the user- project and project - role association edge and use this for authorization to findout active roles. <br />
<br />
This implementation plan is to make minimum impact on services outside keystone.So the plan is to like computing authorization path specification for a certain time when user requests for a token and and return a list of active roles. In that case this extension to the authorization model is transparent to all other openstack services like nova, glance, cynder etc. <br />
<br />
Steps to Implement AGBAC in Openstack <br />
<br />
1. Define API and Storage for Specifying Attributes of different entities <br />
2. Define storage Assignment Attributes.<br />
3. Define API to set the entity attributes<br />
4. Define API to set the association attributes<br />
5. A Policy specification storage that would specify path based policy to compute roles.<br />
6. A Compute function that would compute the roles using entites, their attributes relationship between entities attribute of relationships and policy.<br />
<br />
[0] Bo Tang and Ravi Sandhu, Extending Openstack Access Control With Domain Trust. In Proceedings 8th International Conference on Network and System Security (NSS 2014), Xi'an, China, October 15-17, 2014, 15 pages<br />
<br />
[1] http://neo4j.com/<br />
<br />
[2] Rodriguez, Marko A., and Peter Neubauer. "Constructions from dots and lines." Bulletin of the American Society for Information Science and Technology 36.6 (2010): 35-41.<br />
<br />
== Design ==<br />
<br />
=== Persona research and design for Horizon UI ===<br />
<br />
Description: <br />
There has been some initial work done in a few different areas around generating Personas for the Horizon UI. This task/project would allow someone to lead the effort to pull the research together, perhaps perform further end-user interviews or surveys, analyze data, form groups of personas, and put together an initial set of target Horizon personas that we can use during requirements gathering, design phases, and general discussion.<br />
<br />
Related blueprint: https://blueprints.launchpad.net/openstack-ux/+spec/horizon-personas<br />
<br />
Expected results: Initial set of Personas for people to use during requirements gathering, design phases, and general discussion of our target Horizon users.<br />
<br />
Knowledge prerequisites: basic interviewing skills, willingness to talk with a lot of new people, readiness to listen and report back findings<br />
<br />
Nice-to-have knowledge: User Experience Design basics<br />
<br />
Mentors: [[User:julim|Ju Lim]]<br />
<br />
=== Redesign for the Object Storage -> Containers section in Horizon ===<br />
<br />
Description: <br />
<br />
Currently, there is a section under the Object Storage panel that allows users (e.g. Consumers and/or Project Administrators) to Create, Delete, and Edit Containers. It would be great to do a little bit of research into identifying the use cases around these features and then proposing a redesign of these features based on the findings. This will include learning some basic Usability best practices and applying them to a design. The design would be done in wireframe format, so it could be done in any tool that allows for this. The design would be reviewed on the UX AskBot site, a new blueprint would need to be created as well. This would take a new designer through the process that currently exists for proposing an updated design to a current feature in Horizon.<br />
<br />
Related blueprint: N/A (To be created by intern as part of process)<br />
<br />
Expected results: Redesign of "Containers" section in Object Storage panel proposed and approved by Horizon community.<br />
<br />
Knowledge prerequisites: basic sketching or wireframing skills<br />
<br />
Nice-to-have knowledge: User Experience Design basics<br />
<br />
Mentors: [[User:julim|Ju Lim]], [[User:lblanchard|Liz Blanchard]]<br />
<br />
=== Horizon Concept Review and Usability Testing ===<br />
<br />
Description: There has been very little work done around Horizon UI concept reviews and usability testing. This task/project would allow someone to lead the effort to put together a test plan, identify customers as test participants, conduct (contextual) inquiry / interview, survey users, analyze data to share results / findings with the community findings regarding how current production OpenStack users are using the software, their use cases, and whether the Horizon UI meets their needs. Along the way, you may identify areas of improvement, concepts that need further refinement, and new use cases or opportunities that have not yet been addressed.<br />
<br />
Related blueprint: https://blueprints.launchpad.net/openstack-ux/+spec/ux-users-community-testing<br />
<br />
Expected results: (1) Identify a community of users willing to participate in Horizon UI usability testing and participate in various OpenStack concept reviews. (2) Share usability test findings with the community that will be used for design and general Horizon discussions.<br />
<br />
Knowledge prerequisites: usability testing skills, basic interviewing skills, willingness to talk with a lot of new people, readiness to listen and report back findings, ability to analyze data to find patterns.<br />
<br />
Nice-to-have knowledge: User Experience Design and/or User Research basics<br />
<br />
Mentors: [[User:julim|Ju Lim]], [[User:lblanchard|Liz Blanchard]]</div>Liz Blanchardhttps://wiki.openstack.org/w/index.php?title=User:Lblanchard&diff=75498User:Lblanchard2015-03-12T18:33:58Z<p>Liz Blanchard: Created page with "I'm a User Experience Designer looking to help improve the Usability of all things OpenStack. Catch me in the #openstack-ux channel if you want to chat more."</p>
<hr />
<div>I'm a User Experience Designer looking to help improve the Usability of all things OpenStack. Catch me in the #openstack-ux channel if you want to chat more.</div>Liz Blanchardhttps://wiki.openstack.org/w/index.php?title=Merlin/PoC&diff=61740Merlin/PoC2014-08-29T17:34:23Z<p>Liz Blanchard: /* Draft UI concept for PoC (visual editing of HOT templates) */</p>
<hr />
<div>== Draft UI concept for PoC (visual editing of HOT templates) ==<br />
To get familiar with HOT templates editing you can read either [http://docs.openstack.org/developer/heat/template_guide/hot_guide.html the guide] or more comprehensive [http://docs.openstack.org/developer/heat/template_guide/hot_spec.html#hot-spec specification]. I've tried to address the most basic cases for now, leaving behind:<br />
* parameters constraints editing (frankly speaking, I don't yet imagine how it should be done);<br />
* editing the type of link between properties and parameters, outputs and attributes;<br />
* joining the parameters into parameter groups (simple enough);<br />
* supporting intrinsic functions like '''str_replace''' or '''replace_facade''' (should be visually edited at all?).<br />
:comment [[User:Liz Blanchard|lblanchard]] 18:40, 22 August 2014 (UTC) I’m missing where these widgets fit into the overall Horizon application. Will this integrate with the Stacks section where the Heat UI work has been done?<br />
::comment [[User:Timur Sufiev|Timur Sufiev]] ([[User talk:Timur Sufiev|talk]]) 14:07, 26 August 2014 (UTC) Currently there is 'Topology' tab in each Stack Entry details - it shows more or less deployed stack with only Heat resources being shown, while the proposed HOT editor shows also Parameter and Output entities. I suspect it will confusing for users to have 2 graphical views for Heat - a topology view and template view, so they should eventually converge. Although deployed Heat stack is merely a HOT template with parameters bound to actual values and resources' attributes already calculated, HOT editor provides too much info to use it as is in the Topology tab. One of possible solutions I see here is provide Zoom In/Zoom Out feature, making HOT editor view look like Topology view when zoomed out. What do you think about it?<br />
:::comment [[User:Liz Blanchard|lblanchard]] 18:30, 29 August 2014 (UTC) This definitely makes sense to me. I'm glad to hear about any plans or ideas around making sure these two interfaces work well together.<br />
<br />
=== Adding a Resource entity ===<br />
[[File:merlin_poc_1.png|Resource entity]]<br />
:comment [[User:Liz Blanchard|lblanchard]] 18:40, 22 August 2014 (UTC) A few things...1) It’s not a very common practice to use right-click in a web UI and I think we should have these actions available always at the top of the canvas rather than buried in a right-click menu. 2) Should instance type be a drop down?<br />
::comment [[User:Timur Sufiev|Timur Sufiev]] ([[User talk:Timur Sufiev|talk]]) 14:07, 26 August 2014 (UTC) <br />
# To me the most obvious alternative to using context menus is a sidebar with accordion - with Resources, Parameters, Parameters Groups and Outputs section. To add an Entity to the Canvas user should drag-and-drop an entity there from the sidebar. I've recently run into very interesting demo of the analogous proprietary [https://www.youtube.com/watch?v=YsimXDFqSRM#t=510 HOT builder] made by IBM, presented at Atlanta Summit - that's how they did it (among with a dozen of other super-cool things). In case one side-bar is enough, there will still be enough space for canvas on modern desktops (given that Horizon left side-bar also eats some space). <br />
# No, the instance type should not be a drop-down, at least at template composing stage - because the available choices depend on a particular environment in which a template is deployed, which may differ from the environment in which template is composed. The difference between template compose and deploy phase should be elaborated a bit, but I didn't want to think about right from the beginning, because it seems to me very Heat-specific, while the purpose of the PoC is making a solution suitable for other projects like Murano or Mistral using HOT templates as an example.<br />
:::comment [[User:Liz Blanchard|lblanchard]] 18:30, 29 August 2014 (UTC) I like the idea of a sidebar for the user to choose from. It can be something that the user can show or hide based on if they need it. This would allow the entire canvas to be shown without the user losing real estate if they need to whole screen.<br />
<br />
=== Adding Parameter entity ===<br />
[[File:merlin_poc_2.png|Parameter entity]]<br />
:comment [[User:Liz Blanchard|lblanchard]] 18:40, 22 August 2014 (UTC) What are the interactions the user needs to take to create a connection on the screen? Do they have to select the resource in some way and choose an action? Do they drag and drop?<br />
::comment [[User:Timur Sufiev|Timur Sufiev]] ([[User talk:Timur Sufiev|talk]]) 14:07, 26 August 2014 (UTC) Is it okay to use right click -> context menu here? There are at least 2 actions available for a Parameter entity on canvas: 1) change some Parameter's properties 2) connect it to some Property. While changing Parameter's properties could be bound to left-click, connecting it to other entity requires either selecting this option via context menu, or pressing a button on a canvas toolbar. What is better?<br />
:::comment [[User:Liz Blanchard|lblanchard]] 18:30, 29 August 2014 (UTC) I'd suggest having a dropdown arrow for a selection menu right on the object itself that would show the user any options they could perform on the object including editing parameters and making connections. This way the user could left click. They right click interaction is not as intuitive in a browser since a lot of times this will only be used for browser functions.<br />
<br />
=== Enhancing Resource entity to display both Properties and Attributes ===<br />
[[File:merlin_poc_3.png|Parameters + Attributes]]<br />
:comment [[User:Liz Blanchard|lblanchard]] 18:40, 22 August 2014 (UTC) I like the idea of using an accordion for this design. Would this be sticky and remember the users preference if they refresh the page?<br />
::comment [[User:Timur Sufiev|Timur Sufiev]] ([[User talk:Timur Sufiev|talk]]) 14:07, 26 August 2014 (UTC) Yes, I think it's possible.<br />
<br />
=== Adding Output entity ===<br />
[[File:merlin_poc_4.png|Output entity]]<br />
:comment [[User:Liz Blanchard|lblanchard]] 18:40, 22 August 2014 (UTC) Again, how does the user create these connections?<br />
::comment [[User:Timur Sufiev|Timur Sufiev]] ([[User talk:Timur Sufiev|talk]]) 14:07, 26 August 2014 (UTC) Same as in comment for Parameter entity</div>Liz Blanchardhttps://wiki.openstack.org/w/index.php?title=Merlin/PoC&diff=61131Merlin/PoC2014-08-22T18:44:10Z<p>Liz Blanchard: </p>
<hr />
<div>== Draft UI concept for PoC (visual editing of HOT templates) ==<br />
To get familiar with HOT templates editing you can read either [http://docs.openstack.org/developer/heat/template_guide/hot_guide.html the guide] or more comprehensive [http://docs.openstack.org/developer/heat/template_guide/hot_spec.html#hot-spec specification]. I've tried to address the most basic cases for now, leaving behind:<br />
* parameters constraints editing (frankly speaking, I don't yet imagine how it should be done);<br />
* editing the type of link between properties and parameters, outputs and attributes;<br />
* joining the parameters into parameter groups (simple enough);<br />
* supporting intrinsic functions like '''str_replace''' or '''replace_facade''' (should be visually edited at all?).<br />
:comment [[User:Liz Blanchard|lblanchard]] 18:40, 22 August 2014 (UTC) I’m missing where these widgets fit into the overall Horizon application. Will this integrate with the Stacks section where the Heat UI work has been done?<br />
<br />
=== Adding a Resource entity ===<br />
[[File:merlin_poc_1.png|Resource entity]]<br />
:test-comment [[User:Serg Melikyan|smelikyan]] ([[User talk:Serg Melikyan|talk]]) 14:22, 22 August 2014 (UTC)<br />
:: another test-comment [[User:Timur Sufiev|Timur Sufiev]] ([[User talk:Timur Sufiev|talk]]) 14:23, 22 August 2014 (UTC)<br />
:comment [[User:Liz Blanchard|lblanchard]] 18:40, 22 August 2014 (UTC) A few things...1) It’s not a very common practice to use right-click in a web UI and I think we should have these actions available always at the top of the canvas rather than buried in a right-click menu. 2) Should instance type be a drop down?<br />
<br />
=== Adding Parameter entity ===<br />
[[File:merlin_poc_2.png|Parameter entity]]<br />
:comment [[User:Liz Blanchard|lblanchard]] 18:40, 22 August 2014 (UTC) What are the interactions the user needs to take to create a connection on the screen? Do they have to select the resource in some way and choose an action? Do they drag and drop?<br />
<br />
=== Enhancing Resource entity to display both Properties and Attributes ===<br />
[[File:merlin_poc_3.png|Parameters + Attributes]]<br />
:comment [[User:Liz Blanchard|lblanchard]] 18:40, 22 August 2014 (UTC) I like the idea of using an accordion for this design. Would this be sticky and remember the users preference if they refresh the page?<br />
<br />
=== Adding Output entity ===<br />
[[File:merlin_poc_4.png|Output entity]]<br />
:comment [[User:Liz Blanchard|lblanchard]] 18:40, 22 August 2014 (UTC) Again, how does the user create these connections?</div>Liz Blanchardhttps://wiki.openstack.org/w/index.php?title=Meetings/UX&diff=60810Meetings/UX2014-08-18T19:47:34Z<p>Liz Blanchard: </p>
<hr />
<div>The [https://wiki.openstack.org/wiki/UX OpenStack User Experience Team] regular IRC meetings (starting June 2, 2014)<br />
* Every other Monday at 1700 UTC<br />
* IRC channel: <code><nowiki>#openstack-meeting-3</nowiki></code><br />
* Chair: jcoufal (Jaromir Coufal)<br />
<br />
=== Agenda for next meeting (Monday, September 8, 2014, 17:00 UTC or 1:00pm US/EDT) ===<br />
* Wireframes review tool<br />
** https://etherpad.openstack.org/p/uxtools<br />
** It would be great to make a decision on this if we have enough people. If not, should we start a ML thread to finish the discussion?<br />
* Faceted Search<br />
** Is anyone in the UX group actively working on this? Has anyone given feedback in the past on it from a design perspective?<br />
** https://blueprints.launchpad.net/horizon/+spec/faceted-search<br />
* Horizon Pattern Library<br />
** https://docs.google.com/presentation/d/1OKy_oXZQSg8Feo0p6Es7giR6a-w_CK8H03D2R2yAUjs/edit?usp=sharing_eil<br />
** Any open questions here?<br />
** Chris will be moving on to merge this into docs.<br />
* Ops Meetup<br />
** http://www.openstack.org/blog/2014/07/ops-mid-cycle-meetup-august-2526/<br />
** Did anyone attend?<br />
** Any updates to share from this?<br />
* [UX] [Horizon] [Heat] Merlin project (formerly known as cross-project UI library for Heat/Mistral/Murano/Solum) plans for PoC and more<br />
** Review any questions/feedback given on PoC wireframes: https://wiki.openstack.org/wiki/Merlin/PoC#Draft_UI_concept_for_PoC_.28visual_editing_of_HOT_templates.29<br />
* New Launch Instance User Feedback Results<br />
** Will brief on findings and recommendations (Jacki?)<br />
<br />
=== Previous meetings ===<br />
* http://eavesdrop.openstack.org/meetings/ux/<br />
<br />
=== Previous agendas ===<br />
<br />
==== August 18 ====<br />
* Wireframes review tool<br />
** https://etherpad.openstack.org/p/uxtools<br />
* Faceted Search<br />
** Is anyone in the UX group actively working on this? Has anyone given feedback in the past on it from a design perspective?<br />
** https://blueprints.launchpad.net/horizon/+spec/faceted-search<br />
* Horizon Pattern Library<br />
** https://docs.google.com/presentation/d/1OKy_oXZQSg8Feo0p6Es7giR6a-w_CK8H03D2R2yAUjs/edit?usp=sharing_eil<br />
** Review feedback given since last meeting<br />
* Ops Meetup<br />
** http://www.openstack.org/blog/2014/07/ops-mid-cycle-meetup-august-2526/<br />
** Anyone attending?<br />
* [UX] [Horizon] [Heat] Merlin project (formerly known as cross-project UI library for Heat/Mistral/Murano/Solum) plans for PoC and more<br />
** Is anyone in the UX group actively working on this?<br />
** If not, does anyone has cycles or interest to help out with this effort? At least giving review feedback on some of the design proposals would be great.<br />
** http://lists.openstack.org/pipermail/openstack-dev/2014-August/042128.html<br />
* New Launch Instance User Feedback Results<br />
** Will brief on findings and recommendations<br />
<br />
==== August 4 ====<br />
* lblanchard will chair<br />
* Wireframes review tool<br />
** https://etherpad.openstack.org/p/uxtools<br />
* Faceted Search<br />
** Is anyone in the UX group actively working on this? Has anyone given feedback in the past on it from a design perspective?<br />
** https://blueprints.launchpad.net/horizon/+spec/faceted-search<br />
* Horizon Pattern Library<br />
** https://docs.google.com/presentation/d/1OKy_oXZQSg8Feo0p6Es7giR6a-w_CK8H03D2R2yAUjs/edit?usp=sharing_eil<br />
* UX Project name on StoryBoard<br />
** https://review.openstack.org/#/c/96549/<br />
<br />
<br />
==== July 7 ====<br />
* Meeting alternating times<br />
* Wireframes review tool<br />
** https://etherpad.openstack.org/p/uxtools<br />
* Faceted Search<br />
<br /><br />
<br />
==== June 18 ====<br />
<br />
* StoryBoard for UX and its progress<br />
* Wireframes review tool and its progress<br />
* [UX] [Heat] [Mistral] [Murano] [Neutron] [Solum] Cross-project UI library: gathering the requirements<br />
** Is anyone in the UX group actively working on this?<br />
** If not, does anyone has cycles or interest to help out with this effort? At least giving review feedback on some of the design proposals would be great.<br />
** http://lists.openstack.org/pipermail/openstack-dev/2014-June/037054.html<br />
** https://etherpad.openstack.org/p/9XQ7Q2NQdv<br />
** https://docs.google.com/document/d/19Q9JwoO77724RyOp7XkpYmALwmdb7JjoQHcDv4ffZ-I/edit#<br />
* Faceted Search<br />
** Is anoyone in the UX group actively working on this? Has anyone given feedback in the past on it from a design perspective?<br />
** https://blueprints.launchpad.net/horizon/+spec/faceted-search<br />
** Would anyone have cycles or interest to help out here?</div>Liz Blanchardhttps://wiki.openstack.org/w/index.php?title=Meetings/UX&diff=59674Meetings/UX2014-08-04T18:51:42Z<p>Liz Blanchard: </p>
<hr />
<div>The [https://wiki.openstack.org/wiki/UX OpenStack User Experience Team] regular IRC meetings (starting June 2, 2014)<br />
* Every other Monday at 1700 UTC<br />
* IRC channel: <code><nowiki>#openstack-meeting-3</nowiki></code><br />
* Chair: jcoufal (Jaromir Coufal)<br />
<br />
=== Agenda for next meeting (Monday, August 18, 2014, 17:00 UTC or 1:00pm US/EDT) ===<br />
* Wireframes review tool<br />
** https://etherpad.openstack.org/p/uxtools<br />
* Faceted Search<br />
** Is anyone in the UX group actively working on this? Has anyone given feedback in the past on it from a design perspective?<br />
** https://blueprints.launchpad.net/horizon/+spec/faceted-search<br />
* Horizon Pattern Library<br />
** https://docs.google.com/presentation/d/1OKy_oXZQSg8Feo0p6Es7giR6a-w_CK8H03D2R2yAUjs/edit?usp=sharing_eil<br />
** Review feedback given since last meeting<br />
* Ops Meetup<br />
** http://www.openstack.org/blog/2014/07/ops-mid-cycle-meetup-august-2526/<br />
** Anyone attending?<br />
<br />
=== Previous meetings ===<br />
* http://eavesdrop.openstack.org/meetings/ux/<br />
<br />
=== Previous agendas ===<br />
<br />
==== August 4 ====<br />
* lblanchard will chair<br />
* Wireframes review tool<br />
** https://etherpad.openstack.org/p/uxtools<br />
* Faceted Search<br />
** Is anyone in the UX group actively working on this? Has anyone given feedback in the past on it from a design perspective?<br />
** https://blueprints.launchpad.net/horizon/+spec/faceted-search<br />
* Horizon Pattern Library<br />
** https://docs.google.com/presentation/d/1OKy_oXZQSg8Feo0p6Es7giR6a-w_CK8H03D2R2yAUjs/edit?usp=sharing_eil<br />
* UX Project name on StoryBoard<br />
** https://review.openstack.org/#/c/96549/<br />
<br />
<br />
==== July 7 ====<br />
* Meeting alternating times<br />
* Wireframes review tool<br />
** https://etherpad.openstack.org/p/uxtools<br />
* Faceted Search<br />
<br /><br />
<br />
==== June 18 ====<br />
<br />
* StoryBoard for UX and its progress<br />
* Wireframes review tool and its progress<br />
* [UX] [Heat] [Mistral] [Murano] [Neutron] [Solum] Cross-project UI library: gathering the requirements<br />
** Is anyone in the UX group actively working on this?<br />
** If not, does anyone has cycles or interest to help out with this effort? At least giving review feedback on some of the design proposals would be great.<br />
** http://lists.openstack.org/pipermail/openstack-dev/2014-June/037054.html<br />
** https://etherpad.openstack.org/p/9XQ7Q2NQdv<br />
** https://docs.google.com/document/d/19Q9JwoO77724RyOp7XkpYmALwmdb7JjoQHcDv4ffZ-I/edit#<br />
* Faceted Search<br />
** Is anoyone in the UX group actively working on this? Has anyone given feedback in the past on it from a design perspective?<br />
** https://blueprints.launchpad.net/horizon/+spec/faceted-search<br />
** Would anyone have cycles or interest to help out here?</div>Liz Blanchardhttps://wiki.openstack.org/w/index.php?title=Meetings/UX&diff=59673Meetings/UX2014-08-04T18:40:18Z<p>Liz Blanchard: </p>
<hr />
<div>The [https://wiki.openstack.org/wiki/UX OpenStack User Experience Team] regular IRC meetings (starting June 2, 2014)<br />
* Every other Monday at 1700 UTC<br />
* IRC channel: <code><nowiki>#openstack-meeting-3</nowiki></code><br />
* Chair: jcoufal (Jaromir Coufal)<br />
<br />
=== Agenda for next meeting (Monday, August 18, 2014, 17:00 UTC or 1:00pm US/EDT) ===<br />
* Wireframes review tool<br />
** https://etherpad.openstack.org/p/uxtools<br />
* Faceted Search<br />
** Is anyone in the UX group actively working on this? Has anyone given feedback in the past on it from a design perspective?<br />
** https://blueprints.launchpad.net/horizon/+spec/faceted-search<br />
* Horizon Pattern Library<br />
** https://docs.google.com/presentation/d/1OKy_oXZQSg8Feo0p6Es7giR6a-w_CK8H03D2R2yAUjs/edit?usp=sharing_eil<br />
** Review feedback given since last meeting<br />
** Ops Meetup<br />
** http://www.openstack.org/blog/2014/07/ops-mid-cycle-meetup-august-2526/<br />
** Anyone attending?<br />
<br />
=== Previous meetings ===<br />
* http://eavesdrop.openstack.org/meetings/ux/<br />
<br />
=== Previous agendas ===<br />
<br />
==== August 4 ====<br />
* lblanchard will chair<br />
* Wireframes review tool<br />
** https://etherpad.openstack.org/p/uxtools<br />
* Faceted Search<br />
** Is anyone in the UX group actively working on this? Has anyone given feedback in the past on it from a design perspective?<br />
** https://blueprints.launchpad.net/horizon/+spec/faceted-search<br />
* Horizon Pattern Library<br />
** https://docs.google.com/presentation/d/1OKy_oXZQSg8Feo0p6Es7giR6a-w_CK8H03D2R2yAUjs/edit?usp=sharing_eil<br />
* UX Project name on StoryBoard<br />
** https://review.openstack.org/#/c/96549/<br />
<br />
<br />
==== July 7 ====<br />
* Meeting alternating times<br />
* Wireframes review tool<br />
** https://etherpad.openstack.org/p/uxtools<br />
* Faceted Search<br />
<br /><br />
<br />
==== June 18 ====<br />
<br />
* StoryBoard for UX and its progress<br />
* Wireframes review tool and its progress<br />
* [UX] [Heat] [Mistral] [Murano] [Neutron] [Solum] Cross-project UI library: gathering the requirements<br />
** Is anyone in the UX group actively working on this?<br />
** If not, does anyone has cycles or interest to help out with this effort? At least giving review feedback on some of the design proposals would be great.<br />
** http://lists.openstack.org/pipermail/openstack-dev/2014-June/037054.html<br />
** https://etherpad.openstack.org/p/9XQ7Q2NQdv<br />
** https://docs.google.com/document/d/19Q9JwoO77724RyOp7XkpYmALwmdb7JjoQHcDv4ffZ-I/edit#<br />
* Faceted Search<br />
** Is anoyone in the UX group actively working on this? Has anyone given feedback in the past on it from a design perspective?<br />
** https://blueprints.launchpad.net/horizon/+spec/faceted-search<br />
** Would anyone have cycles or interest to help out here?</div>Liz Blanchardhttps://wiki.openstack.org/w/index.php?title=Meetings/UX&diff=59671Meetings/UX2014-08-04T17:55:05Z<p>Liz Blanchard: </p>
<hr />
<div>The [https://wiki.openstack.org/wiki/UX OpenStack User Experience Team] regular IRC meetings (starting June 2, 2014)<br />
* Every other Monday at 1700 UTC<br />
* IRC channel: <code><nowiki>#openstack-meeting-3</nowiki></code><br />
* Chair: jcoufal (Jaromir Coufal)<br />
<br />
=== Agenda for next meeting (Monday, August 18, 2014, 17:00 UTC or 1:00pm US/EDT) ===<br />
* Wireframes review tool<br />
** https://etherpad.openstack.org/p/uxtools<br />
* Faceted Search<br />
** Is anyone in the UX group actively working on this? Has anyone given feedback in the past on it from a design perspective?<br />
** https://blueprints.launchpad.net/horizon/+spec/faceted-search<br />
* Horizon Pattern Library<br />
** https://docs.google.com/presentation/d/1OKy_oXZQSg8Feo0p6Es7giR6a-w_CK8H03D2R2yAUjs/edit?usp=sharing_eil<br />
** Review feedback given since last meeting<br />
<br />
=== Previous meetings ===<br />
* http://eavesdrop.openstack.org/meetings/ux/<br />
<br />
=== Previous agendas ===<br />
<br />
==== August 4 ====<br />
* lblanchard will chair<br />
* Wireframes review tool<br />
** https://etherpad.openstack.org/p/uxtools<br />
* Faceted Search<br />
** Is anyone in the UX group actively working on this? Has anyone given feedback in the past on it from a design perspective?<br />
** https://blueprints.launchpad.net/horizon/+spec/faceted-search<br />
* Horizon Pattern Library<br />
** https://docs.google.com/presentation/d/1OKy_oXZQSg8Feo0p6Es7giR6a-w_CK8H03D2R2yAUjs/edit?usp=sharing_eil<br />
* UX Project name on StoryBoard<br />
** https://review.openstack.org/#/c/96549/<br />
<br />
<br />
==== July 7 ====<br />
* Meeting alternating times<br />
* Wireframes review tool<br />
** https://etherpad.openstack.org/p/uxtools<br />
* Faceted Search<br />
<br /><br />
<br />
==== June 18 ====<br />
<br />
* StoryBoard for UX and its progress<br />
* Wireframes review tool and its progress<br />
* [UX] [Heat] [Mistral] [Murano] [Neutron] [Solum] Cross-project UI library: gathering the requirements<br />
** Is anyone in the UX group actively working on this?<br />
** If not, does anyone has cycles or interest to help out with this effort? At least giving review feedback on some of the design proposals would be great.<br />
** http://lists.openstack.org/pipermail/openstack-dev/2014-June/037054.html<br />
** https://etherpad.openstack.org/p/9XQ7Q2NQdv<br />
** https://docs.google.com/document/d/19Q9JwoO77724RyOp7XkpYmALwmdb7JjoQHcDv4ffZ-I/edit#<br />
* Faceted Search<br />
** Is anoyone in the UX group actively working on this? Has anyone given feedback in the past on it from a design perspective?<br />
** https://blueprints.launchpad.net/horizon/+spec/faceted-search<br />
** Would anyone have cycles or interest to help out here?</div>Liz Blanchardhttps://wiki.openstack.org/w/index.php?title=Talk:Calvin,_Developer_%26_Cloud_User,_CNBB_Securities&diff=59359Talk:Calvin, Developer & Cloud User, CNBB Securities2014-07-29T19:13:18Z<p>Liz Blanchard: </p>
<hr />
<div>[lblanchard 7-29-2014]<br />
<br />
1) Would it be possible to add in some of the common tasks that Calvin would do in his 10 minutes of using Horizon? Is he spinning up instances? Uploading files? Looking at the overview page to see how his instances are running? I think this would be nice when designing features specifically for this developer/cloud user role.<br />
<br />
2) Should we make it clear that when we say that Calvin is a developer he IS NOT a developer for OpenStack? Is this the intention? If not, I don’t think we should lump the Cloud user with the OpenStack developer. Based on interviews, these two roles are very different with respect to how they are involved/use OpenStack.<br />
<br />
3) Would Calvin even touch the Networking pieces in Horizon? I’ve questioned whether this is something we should be exposing to our Cloud users, so while I agree it would be very confusing to Calvin, I’m not sure this information is relevant to a persona.</div>Liz Blanchardhttps://wiki.openstack.org/w/index.php?title=Talk:Chuck_Davis,_Cloud_Administrator_%26_IT_Architect,_CNBB_Securities&diff=59358Talk:Chuck Davis, Cloud Administrator & IT Architect, CNBB Securities2014-07-29T19:12:36Z<p>Liz Blanchard: </p>
<hr />
<div>[lblanchard 7-29-2014]<br />
<br />
1) I found that the majority of Administrators that we talked to were actually quite involved in the community and have started to influence getting operators to be heard. I wonder if we could capture this in Chuck’s persona. Maybe he doesn’t have as much time to put towards the community because he is extremely busy and doesn’t work 24/7, but he is an early adopter of OpenStack and does care to be heard by the community.</div>Liz Blanchardhttps://wiki.openstack.org/w/index.php?title=Talk:CNBB_Securities_Comany_Overview&diff=59357Talk:CNBB Securities Comany Overview2014-07-29T19:09:11Z<p>Liz Blanchard: </p>
<hr />
<div>[lblanchard 7-29-2014]<br />
Thanks for taking the time to write these draft personas up! I have a few comments that I was hoping we could address for the final versions. I'll add some overall comments here and then additional comments specific to each persona on the personas pages...<br />
<br />
1) I feel like by all of these personas focused on one company (CNBB Securities), we are missing out on the range of data we got from the interviews with folks at small, medium, and large companies. Would it be possible to have a range within the three personas?<br />
<br />
2) We are missing the data we captured around some companies wanting to stay up to date with the latest and greatest releases of OpenStack and some hanging back on “stable” versions. Can we capture this somehow?<br />
<br />
3) There are companies who are using OpenStack in production and I think we need to represent a user who works in one of those companies. It doesn’t necessarily have to be the IT Director, but I don’t think we are doing all of the early adopters justice in this case. We should be highlighting the things that work well and why they use OpenStack today so that as we design we can keep these things in mind as we evolve and keep adding features.</div>Liz Blanchardhttps://wiki.openstack.org/w/index.php?title=Meetings/UX&diff=59258Meetings/UX2014-07-28T16:54:22Z<p>Liz Blanchard: </p>
<hr />
<div>The [https://wiki.openstack.org/wiki/UX OpenStack User Experience Team] regular IRC meetings (starting June 2, 2014)<br />
* Every other Monday at 1700 UTC<br />
* IRC channel: <code><nowiki>#openstack-meeting-3</nowiki></code><br />
* Chair: jcoufal (Jaromir Coufal)<br />
<br />
=== Agenda for next meeting (Monday, August 4, 2014, 17:00 UTC) ===<br />
* lblanchard will chair<br />
* Wireframes review tool<br />
** https://etherpad.openstack.org/p/uxtools<br />
* Faceted Search<br />
** Is anyone in the UX group actively working on this? Has anyone given feedback in the past on it from a design perspective?<br />
** https://blueprints.launchpad.net/horizon/+spec/faceted-search<br />
* Horizon Pattern Library<br />
** https://docs.google.com/presentation/d/1OKy_oXZQSg8Feo0p6Es7giR6a-w_CK8H03D2R2yAUjs/edit?usp=sharing_eil<br />
<br />
=== Previous meetings ===<br />
* http://eavesdrop.openstack.org/meetings/ux/<br />
<br />
=== Previous agendas ===<br />
<br />
==== July 7 ====<br />
* Meeting alternating times<br />
* Wireframes review tool<br />
** https://etherpad.openstack.org/p/uxtools<br />
* Faceted Search<br />
<br />
==== June 18 ====<br />
<br />
* StoryBoard for UX and its progress<br />
* Wireframes review tool and its progress<br />
* [UX] [Heat] [Mistral] [Murano] [Neutron] [Solum] Cross-project UI library: gathering the requirements<br />
** Is anyone in the UX group actively working on this?<br />
** If not, does anyone has cycles or interest to help out with this effort? At least giving review feedback on some of the design proposals would be great.<br />
** http://lists.openstack.org/pipermail/openstack-dev/2014-June/037054.html<br />
** https://etherpad.openstack.org/p/9XQ7Q2NQdv<br />
** https://docs.google.com/document/d/19Q9JwoO77724RyOp7XkpYmALwmdb7JjoQHcDv4ffZ-I/edit#<br />
* Faceted Search<br />
** Is anoyone in the UX group actively working on this? Has anyone given feedback in the past on it from a design perspective?<br />
** https://blueprints.launchpad.net/horizon/+spec/faceted-search<br />
** Would anyone have cycles or interest to help out here?</div>Liz Blanchardhttps://wiki.openstack.org/w/index.php?title=Meetings/UX&diff=55961Meetings/UX2014-06-16T14:02:45Z<p>Liz Blanchard: /* Agenda for next meeting (Wednesday, June 18, 2014, 14:30 UTC) */</p>
<hr />
<div>The [https://wiki.openstack.org/wiki/UX OpenStack User Experience Team] regular IRC meetings (starting June 2, 2014)<br />
* 1st Monday in a month at 1700 UTC<br />
* two weeks after on Wednesday at 1430 UTC<br />
* IRC channel: <code><nowiki>#openstack-meeting-3</nowiki></code><br />
* Chair: jcoufal (Jaromir Coufal)<br />
<br />
=== Agenda for next meeting (Wednesday, June 18, 2014, 14:30 UTC) ===<br />
<br />
* [UX] [Heat] [Mistral] [Murano] [Neutron] [Solum] Cross-project UI library: gathering the requirements<br />
** Is anyone in the UX group actively working on this?<br />
** If not, does anyone has cycles or interest to help out with this effort? At least giving review feedback on some of the design proposals would be great.<br />
** http://lists.openstack.org/pipermail/openstack-dev/2014-June/037054.html<br />
** https://etherpad.openstack.org/p/9XQ7Q2NQdv<br />
** https://docs.google.com/document/d/19Q9JwoO77724RyOp7XkpYmALwmdb7JjoQHcDv4ffZ-I/edit#<br />
* Faceted Search<br />
** Is anoyone in the UX group actively working on this? Has anyone given feedback in the past on it from a design perspective?<br />
** https://blueprints.launchpad.net/horizon/+spec/faceted-search<br />
** Would anyone have cycles or interest to help out here?<br />
<br />
=== Apologies for absence ===<br />
* none<br />
<br />
=== Previous meetings ===<br />
* http://eavesdrop.openstack.org/meetings/ux/</div>Liz Blanchardhttps://wiki.openstack.org/w/index.php?title=Meetings/UX&diff=55292Meetings/UX2014-06-09T21:01:39Z<p>Liz Blanchard: /* Agenda for next meeting (Wednesday, June 18, 2014, 14:30 UTC) */</p>
<hr />
<div>The [https://wiki.openstack.org/wiki/UX OpenStack User Experience Team] regular IRC meetings (starting June 2, 2014)<br />
* 1st Monday in a month at 1700 UTC<br />
* two weeks after on Wednesday at 1430 UTC<br />
* IRC channel: <code><nowiki>#openstack-meeting-3</nowiki></code><br />
* Chair: jcoufal (Jaromir Coufal)<br />
<br />
=== Agenda for next meeting (Wednesday, June 18, 2014, 14:30 UTC) ===<br />
<br />
* [UX] [Heat] [Mistral] [Murano] [Neutron] [Solum] Cross-project UI library: gathering the requirements<br />
** Is anyone in the UX group actively working on this?<br />
** If not, does anyone has cycles to help out with this effort? At least giving review feedback on some of the design proposals would be great.<br />
** http://lists.openstack.org/pipermail/openstack-dev/2014-June/037054.html<br />
** https://etherpad.openstack.org/p/9XQ7Q2NQdv<br />
** https://docs.google.com/document/d/19Q9JwoO77724RyOp7XkpYmALwmdb7JjoQHcDv4ffZ-I/edit#<br />
<br />
=== Apologies for absence ===<br />
* none<br />
<br />
=== Previous meetings ===<br />
* http://eavesdrop.openstack.org/meetings/ux/</div>Liz Blanchardhttps://wiki.openstack.org/w/index.php?title=Meetings/UX&diff=55291Meetings/UX2014-06-09T21:01:04Z<p>Liz Blanchard: /* Agenda for next meeting (Wednesday, June 18, 2014, 14:30 UTC) */</p>
<hr />
<div>The [https://wiki.openstack.org/wiki/UX OpenStack User Experience Team] regular IRC meetings (starting June 2, 2014)<br />
* 1st Monday in a month at 1700 UTC<br />
* two weeks after on Wednesday at 1430 UTC<br />
* IRC channel: <code><nowiki>#openstack-meeting-3</nowiki></code><br />
* Chair: jcoufal (Jaromir Coufal)<br />
<br />
=== Agenda for next meeting (Wednesday, June 18, 2014, 14:30 UTC) ===<br />
<br />
* [UX] [Heat] [Mistral] [Murano] [Neutron] [Solum] Cross-project UI library: gathering the requirements<br />
** Is anyone in the UX group actively working on this?<br />
** If not, does anyone has cycles to help out with this effort? At least giving review feedback on some of the design proposals would be great.<br />
** http://lists.openstack.org/pipermail/openstack-dev/2014-June/037054.html<br />
** https://etherpad.openstack.org/p/9XQ7Q2NQdv<br />
<br />
=== Apologies for absence ===<br />
* none<br />
<br />
=== Previous meetings ===<br />
* http://eavesdrop.openstack.org/meetings/ux/</div>Liz Blanchardhttps://wiki.openstack.org/w/index.php?title=People&diff=53943People2014-05-28T14:54:18Z<p>Liz Blanchard: Adding lblanchard</p>
<hr />
<div><br />
= Translation for IRC nicknames =<br />
Each name is linked to a bio page for that individual. Please add yourself<br />
{| border="1" cellpadding="2" cellspacing="0"<br />
| '''IRC Nickname''' <br />
| '''Real Name''' <br />
| '''Company or Role''' <br />
|-<br />
| _0x44 <br />
| [[_0x44|Christopher MacGown]] <br />
| Piston Cloud Founder, Nova Core Team member, Former Ozone developer <br />
|-<br />
| Vivek / VivekVC<br />
| [[Vivek / VivekVC|Vivek Varghese Cherian]] <br />
| Technical Specialist / Senior Project Lead - Syntel Inc, OpenStack Cloud Architect, DevOps Architect<br />
|-<br />
| adiantum <br />
| [[IlyaAlekseyev]] <br />
| Nova Developer <br />
|-<br />
| adrian17od <br />
| [[Adrian Smith]] <br />
| Software Engineer - Workday<br />
|-<br />
| akrivoka<br />
| [[User:Akrivokapic1|Ana Krivokapić]]<br />
| Red Hat<br />
|-<br />
| akscram <br />
| Ilya Kharin<br />
| Software Engineer, Mirantis<br />
|-<br />
| alexpilotti <br />
| Alessandro Pilotti<br />
| CEO, Cloudbase Solutions<br />
|-<br />
| vitola <br />
| [[Vitola|Alex Vitola]]<br />
| System Administrator - DevOps , [http://www.deserv.eti.br/ Deserv - Tecnologia & Serviços]<br />
|-<br />
| ameade <br />
| Alex Meade <br />
| Ozone Developer <br />
|-<br />
| amotoki <br />
| Akihiro Motoki <br />
| Quantum developer, NEC <br />
|-<br />
| andrewbogott <br />
| [[andrewbogott|Andrew Bogott]] <br />
| Developer, Wikimedia Foundation <br />
|-<br />
| annegentle <br />
| [[AnneGentle|Anne Gentle]] <br />
| [[OpenStack]] Technical Writer, Casual nick arriety<br />
|-<br />
| anotherjesse <br />
| [[JesseAndrews|Jesse Andrews]] <br />
| [[AnsoLabs]] co-founder, Nebula chief architect <br />
|-<br />
| anteaya <br />
| Anita Kuno <br />
| Monty's Team<br />
|-<br />
| alekibango <br />
| [[David Pravec]] <br />
| Free and Open Source Software Specialist <br />
|-<br />
| [[ArseneRei]] <br />
| Stephon Striplin <br />
| Developer, DreamHost <br />
|-<br />
| [http://adam.younglogic.com ayoung] <br />
| Adam Young <br />
| Senior Software Engineer, Red Hat <br />
|-<br />
| cleverdevil <br />
| [[JonathanLaCour|Jonathan LaCour]] <br />
| Vice President, Software Development, DreamHost <br />
|-<br />
| bcwaldon <br />
| Brian Waldon <br />
| Rackspace Cloud Builders Developer <br />
|-<br />
| bencherian <br />
| [[BenCherian|Ben Cherian]] <br />
| General Manager, Emerging Technologies, DreamHost <br />
|-<br />
| berendt <br />
| [[ChristianBerendt|Christian Berendt]] <br />
| Consultant/Developer, B1 Systems <br />
|-<br />
| BK_man <br />
| [[AndreyBrindeyev|Andrey Brindeyev]] <br />
| Grid Dynamics International <br />
|-<br />
| blamar <br />
| Brian Lamar <br />
| Ozone Developer <br />
|-<br />
| btorch <br />
| [[btorch|Marcelo Martins]] <br />
| Swift System Engineer <br />
|-<br />
| carlp <br />
| [[carlp|Carl Perry]] <br />
| System Administrator, DreamHost (New Dream Network) <br />
|-<br />
| cerberus <br />
| [[cerberus|Matt Dietz]] <br />
| Ozone Developer <br />
|-<br />
| chemikadze <br />
| [[NikolaySokolov|Nikolay Sokolov]] <br />
| [[GridDynamics]] Developer <br />
|-<br />
| chidical <br />
| [[chidical|Chidi Alams]] <br />
| Systems Engineer <br />
|-<br />
| chmouel <br />
| [[Chmouel|Chmouel Boudjnah]] <br />
| Rackspace Developer <br />
|-<br />
| colinnich <br />
| Colin Nicholson <br />
| Software Developer, iomart group <br />
|-<br />
| comstud <br />
| [[comstud|Chris Behrens]] <br />
| Ozone Developer <br />
|-<br />
| creiht <br />
| [[creiht|Chuck Thier]] <br />
| Swift Developer <br />
|-<br />
| cwright <br />
| [[CoryWright|Cory Wright]] <br />
| Rackspace Operations<br />
|-<br />
| dabo <br />
| [[dabo|Ed Leafe]] <br />
| Ozone Developer <br />
|-<br />
| dachary <br />
| [[dachary|Loic Dachary]] <br />
| [http://enovance.com/ eNovance] CRO and [https://alioth.debian.org/projects/openstack/ Debian GNU/Linux packager] <br />
|-<br />
| davidhadas <br />
| David Hadas <br />
| Swift, IBM Research <br />
|-<br />
| danwent <br />
| Dan Wendlandt <br />
| Quantum developer, PTL <br />
|-<br />
| dendrobates <br />
| [[RickClark|Rick Clark]] <br />
| [[OpenStack]] Project Lead & Chief Architect <br />
|-<br />
| devananda<br />
| [[Devananda|Devananda van der Veen]]<br />
| Nova Baremetal Driver, Openstack-on-Openstack, HP Cloud<br />
|-<br />
| devcamcar <br />
| [[DevinCarlen|Devin Carlen]] <br />
| Founder of Nebula Inc, Nova Core Member, PTL Horizon, [[OpenStack]] POC <br />
|-<br />
| dhellmann <br />
| [[DougHellmann|Doug Hellmann]] <br />
| DreamHost <br />
|-<br />
| dtroyer <br />
| Dean Troyer <br />
| Rackspace Cloudbuilders <br />
|-<br />
| DuncanT <br />
| Duncan Thomas <br />
| HP - Nova and Nova-volume team <br />
|-<br />
| eday <br />
| [[eday|Eric Day]] <br />
| Open Source Architect / Developer <br />
|-<br />
| egallen <br />
| [[egallen|Erwan Gallen]] <br />
| Cloudwatt<br />
|-<br />
| eharney<br />
| [[eharney|Eric Harney]]<br />
| Red Hat<br />
|-<br />
| emagana <br />
| Edgar Magana <br />
| Technical Lead, Cisco - CTO Cloud Computing <br />
|-<br />
| exlt <br />
| [[exlt|Michael Shuler]] <br />
| Swift Systems Engineer <br />
|-<br />
| fifieldt<br />
| [[User:Fifieldt|Tom Fifield]]<br />
| NeCTAR, OpenStack Foundation<br />
|-<br />
| fungi<br />
| [[User:fungi|Jeremy Stanley]]<br />
| project infrastructure, developer community resources and continuous integration systems<br />
|-<br />
| garyk <br />
| Gary Kotton <br />
| VMware <br />
|-<br />
| gholt <br />
| [[gholt|Greg Holt]] <br />
| Swift Developer <br />
|-<br />
| glange <br />
| [[glange|Greg Lange]] <br />
| Swift Developer <br />
|-<br />
| glenc <br />
| [[GlenCampbell|Glen Campbell]] <br />
| Architect/Analyst <br />
|-<br />
| gongys <br />
| Yong Sheng Gong <br />
| IBM <br />
|-<br />
| guitarzan<br />
| Cory Stone<br />
| Rackspace<br />
|-<br />
| gundlach <br />
| [[gundlach|Michael Gundlach]] <br />
| Ozone Developer <br />
|-<br />
| h1nch <br />
| [[h1nch|John Hincher]] <br />
| Systems Engineer <br />
|-<br />
| heckj <br />
| [[JosephHeck|Joe Heck]] <br />
| Developer / Systems Engineer <br />
|-<br />
| hemna<br />
| [[walter-boring|Walter A. Boring IV]] <br />
| HP - Cinder core member<br />
|-<br />
| ironcamel <br />
| Naveed Massjouni <br />
| Ozone Developer <br />
|-<br />
| jaypipes <br />
| [[jaypipes|Jay Pipes]] <br />
| Open Source Architect / Developer <br />
|-<br />
| jc_smith <br />
| [[jcsmith|Jean-Christophe "JC" Smith]] <br />
| Architect <br />
|-<br />
| jeblair <br />
| [[JamesBlair|James Blair]] <br />
| Developer and CI Infrastructure <br />
|-<br />
| jgriffith<br />
| [[JohnGriffith|John Griffith]] <br />
| BlockStorage Technical Lead<br />
|-<br />
| jk0 <br />
| [[jk0|Josh Kearney]] <br />
| Ozone Developer <br />
|-<br />
| jmeridth <br />
| [[jmeridth|Jason Meridth (JM)]] <br />
| Ozone Developer <br />
|-<br />
| johnthetubaguy <br />
| [[johngarbutt|John Garbutt]] <br />
| Senior Software Developer, Citrix Systems <br />
|-<br />
| johnpur <br />
| [[JohnPurrier|John Purrier]] <br />
| [[OpenStack]]/Rackspace liaison <br />
|-<br />
| joshuamckenty <br />
| [[joshuamckenty|Joshua McKenty]] <br />
| Piston Cloud Founder, Nova Core Team member, [[OpenStack]] POC, formerly NASA Nebula Architect <br />
|-<br />
| k4n0<br />
| [[k4n0|Rohan Rhishikesh Kanade]] <br />
| Izel Technologies, Senior Software Engineer <br />
|-<br />
| koolhead17 <br />
| Atul Jha <br />
| App Specialist, Csscorp <br />
|-<br />
| kpepple <br />
| [[KenPepple|Ken Pepple]] <br />
| Consultant / Architect / Developer <br />
|-<br />
| KMarsh <br />
| Kyle Marsh <br />
| Developer, DreamHost <br />
|-<br />
| lblanchard <br />
| [http://uxd-stackabledesign.rhcloud.com/?page_id=2 Liz Blanchard] <br />
| User Interaction Designer, Red Hat <br />
|-<br />
| [[LinuxJedi]] <br />
| [[LinuxJedi|Andrew Hutchings]] <br />
| Developer Infrastructure and Software Engineer, HP <br />
|-<br />
| littleidea <br />
| [[littleidea|Andrew Clay Shafer]] <br />
| Cloudscaling <br />
|-<br />
| letterj <br />
| [[letterj|Jay Payne]] <br />
| Data Catalyst <br />
|-<br />
| lloydde <br />
| [[lloydde|Lloyd Dewolf]] <br />
| Piston Cloud, Director of Customer Care <br />
|-<br />
| lorin1 <br />
| [[LorinHochstein|Lorin Hochstein]] <br />
| Lead Architect, Nimbis Services <br />
|-<br />
| Mandell <br />
| [[mdegerne|Mandell Degerness]] <br />
| Piston Cloud, Systems Analyst <br />
|-<br />
| maoy <br />
| [[maoy|Yun Mao]] <br />
| AT&T Labs - Research, Researcher <br />
|-<br />
| markmc <br />
| [[markmc|Mark McLoughlin]] <br />
| Principal Software Engineer, Red Hat <br />
|-<br />
| [[MarkAtwood]] <br />
| [[MarkAtwood|Mark Atwood]] <br />
| Director - Open Source Evangelism, HP <br />
|-<br />
| markvoelker <br />
| [[markvoelker|Mark Voelker]] <br />
| Software Development Manager, Cisco <br />
|-<br />
| markwash <br />
| Mark Washenberger <br />
| Ozone Developer <br />
|-<br />
| masayukig <br />
| Masayuki Igawa<br />
| Software Engineer, NEC Solution Innovators, Ltd.<br />
|-<br />
| matiu <br />
| [[matiu|Matthew Sherborne]] <br />
| Nova Dev - Rackspace <br />
|-<br />
| mattt <br />
| [[mattt|Matt Thompson]] <br />
| Systems Engineer <br />
|-<br />
| mattray <br />
| [[Matt Ray]] <br />
| Senior Technical Evangelist, Opscode <br />
|-<br />
| mestery <br />
| Kyle Mestery <br />
| Quantum developer <br />
|-<br />
| mikal <br />
| [[Michael Still]] <br />
| Rackspace Australia <br />
|-<br />
| mnot <br />
| [[mnottingham|Mark Nottingham]] <br />
| Rackspace <br />
|-<br />
| morellon <br />
| [[Thiago Morello]] <br />
| Locaweb <br />
|-<br />
| mtaylor <br />
| [[MontyTaylor|Monty Taylor]] <br />
| Developer Infrastructure and CI Manager, HP <br />
|-<br />
| murkk <br />
| [[murkk|Chris Blumentritt]] <br />
| Ozone Systems Engineer <br />
|-<br />
| n0ano <br />
| [[n0ano|Don Dugger]] <br />
| Software engineer, Intel <br />
|-<br />
| ncode <br />
| [[Juliano Martinez]] <br />
| Locaweb <br />
|-<br />
| ndipanov <br />
| Nikola Đipanov <br />
| Red Hat <br />
|-<br />
| notmyname <br />
| [[notmyname|John Dickinson]] <br />
| Swift Developer <br />
|-<br />
| nelson <br />
| [[nelson|Russ Nelson]] <br />
| Wikipedia Contractor <br />
|-<br />
| oubiwann <br />
| [[oubiwann|Duncan McGreggor]] <br />
| Cloud Engineering Manager, DreamHost <br />
|-<br />
| ozstacker <br />
| [[ozstacker|Tristan Goode]] <br />
| Australian [[OpenStack]] User Group Co-Ordinator, CEO Aptira <br />
|-<br />
| pandemicsyn <br />
| [[pandemicsyn|Florian Hines]] <br />
| Swift Engineering Monkey <br />
|-<br />
| patrocinio <br />
| Eduardo Patrocinio <br />
| IBM <br />
|-<br />
| pixelbeat <br />
| [[p-draigbrady|Pádraig Brady]] <br />
| Red Hat, Nove core team member <br />
|-<br />
| pknouff <br />
| Philip Knouff <br />
| Ozone Developer <br />
|-<br />
| [[PotHix]] <br />
| Willian Molinari <br />
| Locaweb <br />
|-<br />
| pvo <br />
| [[pvo|Paul Voccio]] <br />
| Ozone Manager <br />
|-<br />
| blakeyeager <br />
| [[blakeyeager|Blake Yeager]] <br />
| Product Manager, Rackspace Cloud <br />
|-<br />
| rackerhacker <br />
| [[major|Major Hayden]] <br />
| Systems Engineer <br />
|-<br />
| rahmu<br />
| [[rahmu|Joe Hakim Rahme]]<br />
| eNovance<br />
|-<br />
| rainya <br />
| Rainya Mosher <br />
| Ozone SDLC Project Manager <br />
|-<br />
| Razique <br />
| [[RaziqueMahroua|Razique Mahroua]] <br />
| Nevrotic Openstacker and Technical Writer <br />
|-<br />
| rbergeron <br />
| [[RobynBergeron|Robyn Bergeron]] <br />
| Fedora Marketing & Cloud Person <br />
|-<br />
| redbo <br />
| [[redbo|Michael Barton]] <br />
| Swift Developer <br />
|-<br />
| reed <br />
| [[StefanoMaffulli|Stefano Maffulli]] <br />
| OpenStack Community Manager <br />
|-<br />
| reldan <br />
| [[reldan|Eldar Nugaev]] <br />
| Software Developer <br />
|-<br />
| rgerganov<br />
| [[rgerganov|Radoslav Gerganov]] <br />
| VMware <br />
|-<br />
| rohitk<br />
| [[rohitk|Rohit Karajgi]] <br />
| Technical Lead, NTT Data<br />
|-<br />
| russellb <br />
| [[russellb|Russell Bryant]] <br />
| Red Hat <br />
|-<br />
| salv-orlando <br />
| [[SalvatoreOrlando|Salvatore Orlando]] <br />
| Quantum Core Dev <br />
|-<br />
| sandywalsh <br />
| [[sandywalsh|Sandy Walsh]] <br />
| Core developer (Rackspace - Ozone) <br />
|-<br />
| sarob <br />
| [[sarob|Sean Roberts]] <br />
| Infrastructure Strategy Yahoo! <br />
|-<br />
| sdague <br />
| [[sdague|Sean Dague]] <br />
| Developer, IBM <br />
|-<br />
| sirp <br />
| [[sirp|Rick Harris]] <br />
| Ozone Developer <br />
|-<br />
| s0mik <br />
| [[s0mik|Somik Behera]] <br />
| [[OpenStack]] Quantum Founding Member, Quantum Core Developer, Product@Nicira, Former VMware Core Developer <br />
|-<br />
| SergeyLukjanov <br />
| [[User:Sergey_Lukjanov|Sergey Lukjanov]] <br />
| Tech Lead / Senior Software Engineer / Mirantis<br />
|-<br />
| soren <br />
| [[soren|Soren Hansen]] <br />
| Open Source Architect / Developer <br />
|-<br />
| spy <br />
| [[ant|Antony Messerli]] <br />
| Ozone Systems Engineer <br />
|-<br />
| Sukhdev <br />
| Sukhdev Kapur<br />
| Arista Networks<br />
|-<br />
| termie <br />
| [[termie|Andy Smith]] <br />
| Nova Developer <br />
|-<br />
|thimble<br />
| André Nähring<br />
| Consultant, Developer, B1 Systems<br />
|-<br />
| thingee <br />
| Mike Perez <br />
| Developer, DreamHost <br />
|-<br />
| toanster<br />
| Toan Nguyen<br />
| [[OpenStack]] Software Development Manager, Rackspace<br />
|-<br />
| tonywolf <br />
| [[Wolf|Tony Wolf]] <br />
| Ozone Business Analyst <br />
|-<br />
| ttx <br />
| [[ThierryCarrez|Thierry Carrez]] <br />
| OpenStack Release Manager <br />
|-<br />
| tylesmit <br />
| Tyler Smith <br />
| Cisco Developer <br />
|-<br />
| vishy <br />
| [[vishy|Vish Ishaya]] <br />
| Nova Project Technical Lead <br />
|-<br />
| winston-d <br />
| Zhiteng Huang <br />
| Performance Engineer, Intel <br />
|-<br />
| wowdd1 <br />
| Zhao Dan <br />
| Developer <br />
|-<br />
| loquacity <br />
| Lana Brindley <br />
| Technical Writer, Rackspace<br />
|-<br />
| osier<br />
| Osier Yang <br />
| Software Engineer, Red Hat<br />
|-<br />
| vrovachev<br />
| Vadim Rovachev <br />
| QA Engineer, Mirantis<br />
|-<br />
| ylobankov<br />
| Yaroslav Lobankov <br />
| QA Engineer, Mirantis<br />
|}</div>Liz Blanchardhttps://wiki.openstack.org/w/index.php?title=Meetings/UX&diff=53818Meetings/UX2014-05-27T17:16:38Z<p>Liz Blanchard: </p>
<hr />
<div>The [https://wiki.openstack.org/wiki/UX OpenStack User Experience Team] regular IRC meetings<br />
* 1st and 3rd Monday in a month at 1700 UTC, starting June 2, 2014<br />
* IRC channel: <code><nowiki>#openstack-meeting-3</nowiki></code><br />
* Chair: jcoufal (Jaromir Coufal)<br />
<br />
=== Agenda for next meeting (June 2, 2014) ===<br />
<br />
* Meeting timing<br />
** Participants' timezones: https://etherpad.openstack.org/p/ux-meetings<br />
** Does this time work well for everybody?<br />
** Is alternating needed?<br />
<br />
* Storyboard project has been using invision [http://www.invisionapp.com/] for wireframe review.<br />
** lblanchard and jackibauer have used this a bit too passing designs back and forth and asking for comments.<br />
** Free but not open source.<br />
** Other ideas for tools to comment inline on designs?<br />
** lblanchard wants to check out Pencil Project if she can find time :) [http://pencil.evolus.vn/]<br />
<br />
* Should we get involved with helping in the CLI and API spaces?<br />
** Anyone have time/interest?<br />
** What's the best way to go about this?<br />
<br />
* Should we start tracking stories in Storyboard [https://storyboard.openstack.org/#!/] and move from Launchpad [https://blueprints.launchpad.net/openstack-ux]?<br />
** stevedoll has been giving feedback and updates are being continuously made.<br />
** I don't see many limitations of Storyboard in it's current state vs. Launchpad, could be a good idea to switch over and have actual usage feedback to give to the team.<br />
<br />
=== Apologies for absence ===<br />
* none<br />
<br />
=== Previous meetings ===<br />
* http://eavesdrop.openstack.org/meetings/ux/</div>Liz Blanchardhttps://wiki.openstack.org/w/index.php?title=Meetings/UX&diff=53786Meetings/UX2014-05-27T15:22:36Z<p>Liz Blanchard: </p>
<hr />
<div>The [https://wiki.openstack.org/wiki/UX OpenStack User Experience Team] regular IRC meetings<br />
* 1st and 3rd Monday in a month at 1700 UTC, starting June 2, 2014<br />
* IRC channel: <code><nowiki>#openstack-meeting-3</nowiki></code><br />
* Chair: jcoufal (Jaromir Coufal)<br />
<br />
=== Agenda for next meeting (June 2, 2014) ===<br />
<br />
* Meeting timing<br />
** Participants' timezones: https://etherpad.openstack.org/p/ux-meetings<br />
** Does this time work well for everybody?<br />
** Is alternating needed?<br />
<br />
* Storyboard project has been using invision [http://www.invisionapp.com/] for wireframe review.<br />
** lblanchard and jackibauer have used this a bit too passing designs back and forth and asking for comments.<br />
** Free but not open source.<br />
** Other ideas for tools to comment inline on designs?<br />
** lblanchard wants to check out Pencil Project if she can find time :) [http://pencil.evolus.vn/]<br />
<br />
* Should we get involved with helping in the CLI and API spaces?<br />
** Anyone have time/interest?<br />
** What's the best way to go about this?<br />
<br />
=== Apologies for absence ===<br />
* none<br />
<br />
=== Previous meetings ===<br />
* http://eavesdrop.openstack.org/meetings/ux/</div>Liz Blanchardhttps://wiki.openstack.org/w/index.php?title=Meetings/User_Experience&diff=53205Meetings/User Experience2014-05-22T19:12:25Z<p>Liz Blanchard: Created page with "The OpenStack User Experience Team holds public meetings in #openstack-meeting-alt. Everyone is encouraged to attend. * Time is TBD... == Apologies for absence == == Ag..."</p>
<hr />
<div>The [[OpenStack]] User Experience Team holds public meetings in #openstack-meeting-alt. Everyone is encouraged to attend. <br />
* Time is TBD...<br />
<br />
== Apologies for absence ==<br />
<br />
== Agenda for next meeting ==<br />
<br />
* Storyboard project has been using invision [http://www.invisionapp.com/] for wireframe review.<br />
** lblanchard and jackibauer have used this a bit too passing designs back and forth and asking for comments.<br />
** Free but not open source.<br />
** Other ideas for tools to comment inline on designs?<br />
** lblanchard wants to check out Pencil Project if she can find time :) [http://pencil.evolus.vn/]<br />
<br />
== Previous meetings ==<br />
<br />
http://eavesdrop.openstack.org/meetings/userexperience/</div>Liz Blanchardhttps://wiki.openstack.org/w/index.php?title=Meetings&diff=53204Meetings2014-05-22T19:06:49Z<p>Liz Blanchard: /* Containers Team Meeting */</p>
<hr />
<div>The OpenStack project holds its various public meetings on '''IRC''', in the <code><nowiki>#openstack-meeting</nowiki></code>, <code><nowiki>#openstack-meeting-alt</nowiki></code> and <code><nowiki>#openstack-meeting-3</nowiki></code> channels on Freenode. Everyone is encouraged to attend.<br />
<br />
You can also access the [https://www.google.com/calendar/ical/bj05mroquq28jhud58esggqmh4@group.calendar.google.com/public/basic.ics iCal feed for all OpenStack meetings].<br />
<br />
== OpenStack Project & Release Status meeting ==<br />
* Weekly on Tuesdays at 2100 UTC<br />
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code><br />
* Chair (to contact for more information): [[ThierryCarrez]]<br />
* See [[Meetings/ProjectMeeting]] for details<br />
<br />
== Technical Committee meeting ==<br />
* Weekly on Tuesdays at 2000 UTC<br />
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code><br />
* Chair (to contact for more information): [[ThierryCarrez]]<br />
* See [[Governance/TechnicalCommittee]] for details<br />
<br />
== OpenStack Compute (Nova) ==<br />
=== Nova team Meeting ===<br />
* Weekly on Thursdays, alternating times - 1400 UTC and 2100 UTC<br />
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code> (1400 UTC)<br />
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code> (2100 UTC) <br />
* Chair (to contact for more information): Russell Bryant<br />
* See [[Meetings/Nova]] for an agenda<br />
<br />
=== Nova Bug Scrub Meeting ===<br />
* Weekly on Wednesday at 1630 UTC<br />
* IRC channel: <code><nowiki>#openstack-meeting-3</nowiki></code><br />
* Chair (to contact for more information): Tracy Jones<br />
* See [[Meetings/NovaBugScrub]] for an agenda<br />
<br />
=== XenAPI team meeting ===<br />
* Weekly on Wednesdays at 1500 UTC<br />
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code><br />
* Chaired by: [[JohnGarbutt]]<br />
* See [[Meetings/XenAPI]] for agenda<br />
<br />
=== Nova Hyper-V team meeting ===<br />
* Weekly on Tuesdays at 1600 UTC<br />
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code><br />
* Chaired by primeministerp (Peter Pouliot)<br />
<br />
=== Gantt (Scheduler) team meeting ===<br />
* Weekly on Tuesdays at 1500 UTC<br />
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code><br />
* Chair (to contact for more information): n0ano (Don Dugger)<br />
* See [[Meetings/Scheduler]] for details<br />
<br />
=== VMwareAPI team meeting ===<br />
* Weekly on Wednesdays at 1700 UTC<br />
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code><br />
* Chair: [[TracyJones]]<br />
* See [[Meetings/VMwareAPI]] for details<br />
<br />
=== PCI Passthrough Meeting ===<br />
* Weekly on Tuesday at [http://www.worldclock.com/world_clock.html 1300 UTC] <br />
* Will change back to once weekly after agreements are reached.<br />
* IRC channel: #openstack-meeting-alt<br />
* Chair: baoli (Robert Li)<br />
* See [[Meetings/Passthrough]] for details<br />
<br />
=== Nova API meeting ===<br />
* Weekly on Friday at 00:00 UTC<br />
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code><br />
* Chair: Chris Yeoh<br />
* See [[Meetings/NovaAPI]] for details<br />
<br />
=== Libvirt Meeting ===<br />
* Weekly on Tuesday at [http://www.timeanddate.com/worldclock/fixedtime.html?hour=15&min=00&sec=0p1=0 15:00 UTC]<br />
* IRC channel <code><nowiki>#openstack-meeting-3</nowiki></code><br />
* Chair: Daniel Berrange (IRC: danpb)<br />
* See [[Meetings/Libvirt]] for details<br />
<br />
== Documentation team meeting ==<br />
* Every other Wednesday at alternating times, see [[Meetings/DocTeamMeeting]]<br />
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code><br />
* Chair (to contact for more information): [[AnneGentle]]<br />
* See [[Meetings/DocTeamMeeting]] for an agenda<br />
<br />
== Project Infrastructure team meeting ==<br />
* Weekly on Tuesdays at 1900 UTC<br />
* IRC channel: #openstack-meeting<br />
* Chair (to contact for more information): [[User:Corvus|James E. Blair (jeblair)]]<br />
* See [[Meetings/InfraTeamMeeting]] for an agenda<br />
<br />
== QA team meeting ==<br />
* Weekly on Thursdays at 1700/2200 UTC (alternating)<br />
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code><br />
* Chair (to contact for more information): Matt Treinish<br />
* See [[Meetings/QATeamMeeting]] for an agenda<br />
<br />
== DefCore / RefStack Development Meeting ==<br />
* Weekly on Thursdays at 10 am Pacific (will track daylight savings time) - now at 1700 UTC<br />
* IRC channel: <code><nowiki>#openstack-meeting-3</nowiki></code><br />
* PTL: David Lenwell (Piston Cloud)<br />
* DefCore Chairs (to contact for more information): Rob "zehicle" Hirschfeld & Joshua McKenty<br />
* See [[Meetings/DefCore]] for an agenda<br />
<br />
Face to Face Meetings planned (Piston HQ in SFO)<br />
* Friday 3/28 1pm for Web Front Page<br />
* Tuesday 4/15 10am for general working session<br />
<br />
== DefCore Progress Update Meeting ==<br />
* 4/1 DefCore meeting, 2pm PST, 90 minutes<br />
* Agenda & Connection Details at https://etherpad.openstack.org/p/DefCoreElephant.7<br />
* Chairs (to contact for more information): Rob "@zehicle" Hirschfeld & Joshua McKenty<br />
<br />
== State management team meeting ==<br />
* Weekly on Thursdays at 1900 UTC (http://weatherarc.com/utc-time-conversion) <br />
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code><br />
* Chair (to contact for more information): [[Harlowja]]<br />
* See [[Meetings/StateManagement]] for an agenda<br />
<br />
== Keystone team meeting ==<br />
* Weekly on Tuesdays at 1800 UTC<br />
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code><br />
* Chair (to contact for more information): [[DolphMathews]]<br />
* See [[Meetings/KeystoneMeeting]] for an agenda<br />
<br />
== Ironic (Bare Metal) team meeting ==<br />
* Weekly on Mondays at 1900 UTC<br />
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code><br />
* Chair (to contact for more infomation) Devananda van der Veen<br />
* see [[Meetings/Ironic]] for agenda<br />
<br />
== TripleO team meeting ==<br />
* Weekly on Tuesdays at 1900 UTC or Wednesdays at 0700 UTC (alternate weeks)<br />
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code><br />
* Chair (to contact for more infomation) Robert Collins (lifeless)<br />
* see [[Meetings/TripleO]] for agenda<br />
<br />
== OpenStack Networking (Neutron) ==<br />
=== Neutron team meeting ===<br />
* Weekly on Mondays at 2100 UTC<br />
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code><br />
* Chair (to contact for more infomation) Kyle Mestery (mestery)<br />
* see [[Network/Meetings]] for agenda<br />
<br />
=== LBaaS meeting ===<br />
* Weekly on Thursdays at 1400 UTC<br />
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code><br />
* Chair (to contact for more infomation) mestery (Kyle Mestery)<br />
* see [[Network/LBaaS]] for agenda<br />
<br />
=== ML2 Network sub-team meeting ===<br />
* Weekly on Wednesdays at 1600 UTC<br />
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code><br />
* Chair (to contact for more information): rkukura/Suhkdev (Bob Kukura / Sukhdev Kapur)<br />
* See [[Meetings/ML2]] for details<br />
<br />
=== Firewall as a Service (FWaaS) team meeting ===<br />
* Weekly on Wednesdays at [http://www.timeanddate.com/worldclock/fixedtime.html?msg=OpenStack+Neutron+FWaaS+IRC&iso=20140326T1830&p1=1440&ah=1 1830 UTC] <br />
* IRC channel: <code><nowiki>#openstack-meeting-3</nowiki></code><br />
* Chair: snaiksat (Sumit Naiksatam)<br />
* See [[Meetings/FWaaS]] for details<br />
<br />
=== Neutron Advanced Services' Common requirements team meeting ===<br />
* Weekly on Wednesdays at [http://www.timeanddate.com/worldclock/fixedtime.html?msg=OpenStack+Neutron+Adv+Services+IRC&iso=20140326T1730&p1=1440&ah=1 1730 UTC] <br />
* IRC channel: <code><nowiki>#openstack-meeting-3</nowiki></code><br />
* Chair: snaiksat (Sumit Naiksatam)<br />
* See [[Meetings/AdvancedServices]] for details<br />
<br />
=== Neutron IPv6 sub-team Meeting === <br />
* Weekly on Tuesdays at [http://www.worldclock.com/world_clock.html 1400 UTC] <br />
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code> <br />
* Chair: sc68cal (Sean M. Collins)<br />
* See [[Meetings/Neutron-IPv6-Subteam]] for details<br />
<br />
=== Neutron Group Policy Sub-Team Meeting ===<br />
* Weekly on Thursdays at 1800 UTC<br />
* IRC channel: #openstack-meeting-3<br />
* Chair: SumitNaiksatam (Sumit Naiksatam)<br />
* See [[Meetings/Neutron_Group_Policy]] for details<br />
<br />
=== Neutron Distributed Virtual Router meeting ===<br />
* Weekly on Wednesdays at [http://www.worldclock.com/world_clock.html 1500 UTC]<br />
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code><br />
* Chair:Swami (Swaminathan Vasudevan)<br />
* See [[Meetings/Distributed-Virtual-Router]] for details<br />
<br />
=== Neutron blueprint ovs-firewall-driver Meeting ===<br />
* Tentative: Monday, December 16 at 2000 UTC<br />
* IRC channel: #openstack-meeting<br />
* Chair: asadoughi (Amir Sadoughi)<br />
* Agenda: See [[Meetings/Neutron_blueprint_ovs-firewall-driver]]<br />
<br />
=== Neutron L3 Sub Team Meeting ===<br />
* Weekly on Thursday at 1500 UTC<br />
* IRC channel: <code><nowiki>#openstack-meeting-3</nowiki></code><br />
* Chair: carl_baldwin (Carl Baldwin)<br />
* Agenda: See [[Meetings/Neutron-L3-Subteam]]<br />
<br />
=== Neutron ServiceVM framework Sub Team Meeting ===<br />
* Weekly on Tuesdays at 500UTC<br />
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code><br />
* Chair: yamahata (Isaku Yamahata)<br />
* Agenda: See [[Meetings/ServiceVM]]<br />
<br />
=== Neutron DB Migrations Sub Team Meeting ===<br />
* Weekly on Tuesdays at 1300 UTC<br />
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code><br />
* Chair: HenryG (Henry Gessau)<br />
* Agenda: See [[Meetings/NeutronDB]]<br />
<br />
=== Neutron Quality of Service API Sub Team Meeting ===<br />
* Weekly on Tuesdays at 1800 UTC (TENTATIVE)<br />
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code> (TENTATIVE)<br />
* Chair: sc6c8al (Sean M. Collins) (TENTATIVE)<br />
<br />
== Cinder team meeting ==<br />
* Weekly on Wednesdays at 1600 UTC<br />
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code><br />
* Chaired by [[JohnGriffith]]<br />
* see [[CinderMeetings]] for agenda<br />
<br />
== Ceilometer team meeting ==<br />
* '''Every''' week on Thursdays at [http://www.timeanddate.com/worldclock/fixedtime.html?hour=15&min=0&sec=0 1500 UTC].<br />
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code><br />
* Chaired by eglynn (Eoghan Glynn)<br />
* see [[Meetings/Ceilometer]] for details<br />
<br />
== Designate (DNSaaS) meeting ==<br />
* Weekly Wednesdays at 1700 UTC<br />
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code><br />
* Chair (to contact for more information): Kiall Mac Innes (kiall)<br />
* See [[Meetings/Designate]] for details<br />
<br />
== Trove (DBaaS) meeting ==<br />
* Weekly on Wednesdays at 1800 UTC<br />
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code><br />
* Chair (to contact for more information): Michael Basnight (hub_cap) / Vipul Sabhaya (vipul) / Nikhil Manchanda (SlickNik) / Tim Simpson (grapex)<br />
* See [[Meetings/TroveMeeting]] for details<br />
* For BP Meeting, please see [[Meetings/TroveBPMeeting]] for more details<br />
<br />
== Marconi (queues) team meeting ==<br />
* Weekly on Tuesday at 1500 UTC<br />
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code><br />
* Chair: kgriffs (Kurt Griffiths)<br />
* See [[Meetings/Marconi]] for details<br />
<br />
== OpenStack Data Processing (Sahara) team meeting ==<br />
* Weekly on Thursdays at 1800 UTC<br />
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code><br />
* Chair (to contact for more info): SergeyLukjanov (Sergey Lukjanov)<br />
* See [[Meetings/SaharaAgenda]] for details<br />
<br />
== Mistral meeting ==<br />
* Weekly on Mondays at 1600 UTC<br />
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code><br />
* Chair: rakhmerov (Renat Akhmerov)<br />
* See [[Meetings/MistralAgenda]] for details<br />
<br />
== Murano meeting ==<br />
* Weekly on Tuesday at 1700 UTC<br />
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code><br />
* Chair: Georgiy Okrokvertskhov (Georgy_Ok)<br />
* See [[Meetings/MuranoAgenda]] for details<br />
<br />
== Heat (orchestration) team meeting ==<br />
* Weekly on Wednesdays at 2000 UTC or 1200 UTC (on alternate weeks)<br />
* IRC Channel: <code><nowiki>#openstack-meeting</nowiki></code><br />
* Chair (to contact for more information): Zane Bitter (zaneb)<br />
* See [[Meetings/HeatAgenda]] for details<br />
<br />
== Horizon team meeting ==<br />
* Weekly on Tuesdays at 1600 UTC<br />
* IRC channel: <code><nowiki>#openstack-meeting-3</nowiki></code><br />
* Chair: David Lyle (david-lyle)<br />
* See [[Meetings/Horizon]] for details<br />
<br />
== Swift team meeting ==<br />
* Weekly on Wednesdays at 1900 UTC<br />
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code><br />
* Chair: notmyname (John Dickinson)<br />
* See [[Meetings/Swift]] for details<br />
<br />
== OpenStack Security Group (OSSG) meeting ==<br />
* Weekly on Thursdays at 1800 UTC<br />
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code><br />
* Chair (to contact for more information): bdpayne (Bryan Payne)<br />
* See [[Meetings/OpenStackSecurity]] for an agenda<br />
<br />
== Python3 Compatibility Team meeting ==<br />
* Not planned anymore<br />
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code><br />
* Chair (to contact for more information): jd_ (Julien Danjou)<br />
* See [[Meetings/Python3]] for details<br />
<br />
== Glance Team meeting ==<br />
* Weekly on Thursdays at 1400/2000 UTC (alternating)<br />
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code><br />
* Chair (to contact for more information): markwash (Mark Washenberger)<br />
* See [[Meetings/Glance]] for details<br />
<br />
== Oslo Team meeting ==<br />
* On demand on Fridays at 1600 UTC ([http://www.timeanddate.com/worldclock/converted.html?iso=20140425T16&p1=0&p2=2133&p3=195&p4=224 timeanddate.com])<br />
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code><br />
* Chair (to contact for more information): dhellmann (Doug Hellmann)<br />
* See [[Meetings/Oslo]] for details<br />
<br />
== OpenStack Community Office Hours ==<br />
* Weekly on Tuesdays at [http://www.worldclock.com/world_clock.html 0800 UTC] and on Fridays at [http://www.worldclock.com/world_clock.html 1800 UTC] <br />
* IRC channel: <code><nowiki>#openstack-community</nowiki></code><br />
* Chair: fifieldt ([http://www.openstack.org/community/members/profile/369 Tom Fifield]) and reed ([http://www.openstack.org/community/members/profile/1372 Stefano Maffulli]) <br />
* See [[Meetings/Community]] for details<br />
<br />
== I18N Team meeting ==<br />
* Bi-weekly on Thursday, alternating between 0800 UTC and 0000 UTC<br />
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code><br />
* Chair: daisy<br />
* See [[Meetings/I18nTeamMeeting]] for details<br />
<br />
== Training-manuals Team meeting ==<br />
* Weekly on Monday at [http://www.worldclock.com/current-local-time-in-san-francisco_598.htm 1700 UTC] <br />
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code><br />
* Chair: sarob<br />
* See [[Meetings/training-manuals]] for details<br />
<br />
== Manila Team meeting ==<br />
* Weekly on Thursday at [http://www.worldclock.com/current-local-time-in-san-francisco_598.htm 1500 UTC] <br />
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code><br />
* Chair: bswartz<br />
* See [[Manila/Meetings]] for details<br />
<br />
== Stackalytics team meeting ==<br />
* Be-Weekly on Mondays (starting from October 21st) at [http://www.worldclock.com/world_clock.html 1500 UTC] <br />
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code><br />
* Chair: ilyashakhat (Ilya Shakhat)<br />
* See [[Meetings/Stackalytics]] for details<br />
<br />
== Climate (Reservations) team meeting ==<br />
* Weekly on Fridays at [http://www.worldclock.com/world_clock.html 1500 UTC] <br />
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code><br />
* Chair: bauzas (Sylvain Bauza), DinaBelova (Dina Belova)<br />
* See [[Meetings/Climate]] for details<br />
<br />
== Rally meeting ==<br />
* Weekly on Tuesdays at [http://www.worldclock.com/world_clock.html 1700 UTC] <br />
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code><br />
* Chair:boris-42 (Boris Pavlovic)<br />
* See [[Meetings/Rally]] for details<br />
<br />
== Solum Team Meeting ==<br />
* Weekly on Tuesdays at 1600/2200 UTC (alternating)<br />
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code><br />
* Chair: adrian_otto (Adrian Otto)<br />
* See [[Meetings/Solum]] for details<br />
<br />
== Congress Team Meeting ==<br />
* Weekly on Tuesdays at [http://www.worldclock.com/world_clock.html 1700 UTC], e.g. Feb 25, 2014<br />
* IRC channel: #openstack-meeting-3<br />
* Chair: pballand (Pete Balland) or thinrichs (Tim Hinrichs)<br />
* See [[Meetings/Congress]] for details<br />
<br />
== Barbican Meeting ==<br />
* Weekly on Mondays at [http://www.timeanddate.com/worldclock/fixedtime.html?iso=20130502T2000 2000 UTC]<br />
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code><br />
* Chair (to contact for more information): jraim (#openstack-barbican @ Freenode)<br />
* See [[Meetings/Barbican]] for an agenda<br />
<br />
== Chef Cookbook meeting ==<br />
* Weekly on Mondays at 1600 UTC<br />
* IRC channel: <code><nowiki>#openstack-chef</nowiki></code><br />
* Chair: mattray (Matt Ray)<br />
* See [[Meetings/ChefCookbook]] for details<br />
<br />
== Milk Meeting ==<br />
* Weekly on Monday at [http://www.worldclock.com/current-local-time-in-san-francisco_598.htm 2000 UTC] <br />
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code><br />
* Chair: sarob<br />
* See [[Meetings/milk]] for details<br />
<br />
== StoryBoard Meeting ==<br />
* Weekly on Thursdays at 1600 UTC<br />
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code><br />
* Chair: cody-somerville or ttx<br />
* See [[StoryBoard]] for details<br />
<br />
<br />
== Hierarchical Multitenancy Meeting ==<br />
* Weekly on Fridays at 1600 UTC<br />
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code><br />
* Chair: vishy<br />
* See [[HierarchicalMultitenancy]] for details<br />
<br />
== python-openstacksdk Meeting ==<br />
* Weekly on Tuesdays at [http://www.worldtimebuddy.com/?qm=1&lid=6,0,4726206,100&h=6&date=2014-2-11&sln=13-14 1900 UTC] starting 2/19/2014<br />
* IRC channel: <code><nowiki>#openstack-meeting-3</nowiki></code><br />
* Chair: jnoller<br />
* See [[PythonOpenStackSDK]] for details<br />
<br />
== Satori Team Meeting ==<br />
* Weekly on Mondays at [http://www.worldtimebuddy.com/?qm=1&lid=6,0,4726206,100&h=6&date=2014-2-11&sln=9-10 1500 UTC] starting Feb 24, 2014<br />
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code><br />
* Chair: Ziad_Sawalha<br />
* See [[Meetings/Satori]] for details<br />
<br />
== Fuel Team Meeting ==<br />
* Weekly on Thursdays at [http://www.worldtimebuddy.com/?qm=1&lid=100&h=100&date=2014-3-27&sln=16-17 1600 UTC] starting Feb 27, 2014<br />
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code><br />
* Chair: vkozhukalov<br />
* See [[Meetings/Fuel]] for details<br />
<br />
== Third Party Meeting ==<br />
* Weekly on Mondays at 1800 UTC<br />
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code><br />
* Chair: anteaya<br />
* See [[Meetings/ThirdParty]] for details<br />
<br />
== MagnetoDB Team meeting ==<br />
* Every second week on Mondays at 0900 UTC starting April 14th, 2014<br />
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code><br />
* Chair: isviridov<br />
<br />
== MagnetoDB Team daily scrum meeting notes ==<br />
* Every day at 1500 UTC starting April 8th, 2014<br />
* IRC channel: <code><nowiki>#magnetodb</nowiki></code><br />
* Chair: isviridov, setho, dukhlov, ikhudoshyn<br />
<br />
== PHP SDK Team Meeting ==<br />
* Weekly on Wednesdays at 1530 UTC<br />
* IRC channel: <code><nowiki>#openstack-meeting-3</nowiki></code> starting April 9, 2014<br />
* Chair: mfer (Matt Farina)<br />
* See [[Meetings/OpenStack-SDK-PHP]] for details<br />
<br />
== NFV Team Meeting ==<br />
* Weekly on Wednesdays at 1400 UTC<br />
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code> starting June 4, 2014<br />
* Chair: Russell Bryant (russellb)<br />
* See [[Meetings/NFV]] for details<br />
<br />
== Containers Team Meeting ==<br />
* Weekly on Tuesdays at 1600/2200 UTC (alternating)<br />
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code><br />
* Chair: adrian_otto (Adrian Otto)<br />
* See [[Meetings/Containers]] for details<br />
<br />
== User Experience (UX) Team Meeting ==<br />
* Every other week (1st and 3rd of month) on TBD at TBD<br />
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code><br />
* Chair: jcoufal (Jaromir Coufal)<br />
* See [[Meetings/User Experience]] for details</div>Liz Blanchardhttps://wiki.openstack.org/w/index.php?title=UX/Improvements_to_Inline_Help_in_Horizon&diff=52940UX/Improvements to Inline Help in Horizon2014-05-21T14:11:40Z<p>Liz Blanchard: /* Improvements to Inline Help in Horizon */</p>
<hr />
<div>===Improvements to Inline Help in Horizon===<br />
<br />
=====Currently, there is a solution to support inline help in forms.=====<br />
When the user clicks on a form field, they are presented with a pop-up containing some help text to guide them on what they might need to input into this field. During the usability testing we found that when these inline help pop-ups were presented to users, they were well received. Here is an example of what these pop-ups look like today:<br />
<br />
[[file:Inline_help.png]]<br />
<br />
=====Although the current solution was well received, there are cases in which we got feedback that things need to be improved:=====<br />
# These inline help pop-ups should be used within any/all forms that have open input fields that are not straightforward to users on what they are supposed to input. This could be either help with content and/or format of content.<br />
#* A proposal on where to add missing inline help fields:<br />
#** Create Volume -> Size (GB)<br />
#** Create an Image -> Architecture<br />
#** Create Host Aggregate -> Availability Zone<br />
#** Create Flavor -> VCPUs<br />
#** Create Flavor -> RAM MB<br />
#** Create Flavor -> Root Disk GB<br />
#** Create Flavor -> Ephemeral Disk GB<br />
#** Create Flavor -> Swap Disk MB<br />
#** Create an Image -> Architecture (Admin tab)<br />
# Certain fields that AREN’T open ended input fields still need to be able to allow for an extra explanation to the end user on what they fields are really asking. For example, there are a few check box fields that would be great to explain further what these mean to an end user:<br />
<br />
[[file:Inline_help_checkbox.png]]<br />
<br />
What does it mean to have a network in in Admin State? Some way to allow for an explanation of this field would be great for the user. Should we rely on the current “Help Text” styling to add a blurb of text under any fields that may need it?<br />
* http://getbootstrap.com/css/#forms-help-text<br />
* http://getbootstrap.com/2.3.2/base-css.html#forms<br />
<br />
Would it make more sense to have one solution that worked for any type of field? Perhaps something similar to this:<br />
<br />
[[file:Inline_help_suggestion.png]]</div>Liz Blanchardhttps://wiki.openstack.org/w/index.php?title=File:Inline_help_suggestion.png&diff=52939File:Inline help suggestion.png2014-05-21T14:08:07Z<p>Liz Blanchard: </p>
<hr />
<div></div>Liz Blanchardhttps://wiki.openstack.org/w/index.php?title=File:Inline_help_checkbox.png&diff=52938File:Inline help checkbox.png2014-05-21T14:07:54Z<p>Liz Blanchard: </p>
<hr />
<div></div>Liz Blanchardhttps://wiki.openstack.org/w/index.php?title=File:Inline_help.png&diff=52937File:Inline help.png2014-05-21T14:07:30Z<p>Liz Blanchard: </p>
<hr />
<div></div>Liz Blanchardhttps://wiki.openstack.org/w/index.php?title=UX/Improvements_to_Inline_Help_in_Horizon&diff=52936UX/Improvements to Inline Help in Horizon2014-05-21T14:06:49Z<p>Liz Blanchard: Created page with "===Improvements to Inline Help in Horizon=== =====Currently, there is a solution to support inline help in forms.===== When the user clicks on a form field, they are presente..."</p>
<hr />
<div>===Improvements to Inline Help in Horizon===<br />
<br />
=====Currently, there is a solution to support inline help in forms.=====<br />
When the user clicks on a form field, they are presented with a pop-up containing some help text to guide them on what they might need to input into this field. During the usability testing we found that when these inline help pop-ups were presented to users, they were well received. Here is an example of what these pop-ups look like today:<br />
<br />
[[file:image.png]]<br />
<br />
=====Although the current solution was well received, there are cases in which we got feedback that things need to be improved:=====<br />
# These inline help pop-ups should be used within any/all forms that have open input fields that are not straightforward to users on what they are supposed to input. This could be either help with content and/or format of content.<br />
#* A proposal on where to add missing inline help fields:<br />
#** Create Volume -> Size (GB)<br />
#** Create an Image -> Architecture<br />
#** Create Host Aggregate -> Availability Zone<br />
#** Create Flavor -> VCPUs<br />
#** Create Flavor -> RAM MB<br />
#** Create Flavor -> Root Disk GB<br />
#** Create Flavor -> Ephemeral Disk GB<br />
#** Create Flavor -> Swap Disk MB<br />
#** Create an Image -> Architecture (Admin tab)<br />
# Certain fields that AREN’T open ended input fields still need to be able to allow for an extra explanation to the end user on what they fields are really asking. For example, there are a few check box fields that would be great to explain further what these mean to an end user:<br />
<br />
[[file:image.png]]<br />
<br />
What does it mean to have a network in in Admin State? Some way to allow for an explanation of this field would be great for the user. Should we rely on the current “Help Text” styling to add a blurb of text under any fields that may need it?<br />
* http://getbootstrap.com/css/#forms-help-text<br />
* http://getbootstrap.com/2.3.2/base-css.html#forms<br />
<br />
Would it make more sense to have one solution that worked for any type of field? Perhaps something similar to this:<br />
<br />
[[file:image.png]]</div>Liz Blanchardhttps://wiki.openstack.org/w/index.php?title=UX&diff=52924UX2014-05-21T13:17:07Z<p>Liz Blanchard: /* Horizon Proposals */</p>
<hr />
<div>== OpenStack User Experience ==<br />
<br />
<p>'''Mission Statement:''' Enable OpenStack users to be efficient and make their experience consistent and pleasurable.</p><br />
<br />
User Experience (UX) is community-oriented and available for different audiences on several websites. This wiki serves as an informational source for UX-related activities (workstreams) that goes across multiple OpenStack projects.<br />
<br />
=== UX Workstreams ===<br />
[http://ask-openstackux.rhcloud.com UX Discussion Forum (new, temporary address)] <br/><br />
[https://wiki.openstack.org/wiki/Personas OpenStack Personas Working Group] <br/><br />
[https://wiki.openstack.org/wiki/HorizonUsability_Testing Usability Testing] <br/><br />
[https://launchpad.net/openstack-ux Features, Bugs, and Releases in Launchpad] <br/><br />
[https://wiki.openstack.org/wiki/UX/ProgramProposal OpenStack UX Program Proposal] <br/><br />
IRC: #openstack-ux (at FreeNode) <br/><br />
[https://wiki.openstack.org/wiki/UX/openstack-ux-videos OpenStack UX Videos] <br/><br />
<br />
===Getting Involved as a Developer with Designing for User Experience===<br />
<br />
<b>Are you a developer looking for feedback or help with designing new features? Are you looking for help on improving a current feature?</b><br/><br />
Please feel free to reach out to us via the openstack developer mailing list (openstack-dev@lists.openstack.org). In the subject use the tag [UX] and we will be sure to see your question/request. In the near future we will be holding UX specific meetings every other week on IRC. You are welcome to come attend those as well and ask any questions you may have during Open Discussion. Meeting information will be posted here as well as on the OpenStack Meetings[https://wiki.openstack.org/wiki/Meetings] page as soon as it's available. One additional way to get quick feedback or have a discussion with the UX group is to join our IRC channel on freenode (#openstack-ux). If you don't get an immediate response, feel free to ask again later or jump over to using the mailing list!<br />
<br/><br/><br />
<br />
===Getting Involved as a Designer with Designing for User Experience===<br />
<br />
<b>How do I get involved with OpenStack UX and work on blueprints?</b><br/><br />
We track the work that we are doing on our launchpad site[https://launchpad.net/openstack-ux]. If you aren't ready to contribute your own designs, start off by giving others feedback on launchpad or on AskOpenStack UX[http://ask-openstackux.rhcloud.com/questions/].<br />
<br/><br/><br />
<b>What's a blueprint in Launchpad?</b><br/><br />
It's a specification for a feature in OpenStack. In UX, this usually is presented as wireframes or prototypes, but it can be something else. There's lots more info on openstack.org[https://wiki.openstack.org/wiki/Blueprints].<br />
<br/><br/><br />
<b>How does this whole OpenStack contributor thing work anyway?</b><br/><br />
There is great getting started documentation on openstack.org. How to Contribute[https://wiki.openstack.org/wiki/How_To_Contribute] is a good place to start.<br />
<br/><br/><br />
<b>What is the process for getting a new design into Horizon?</b><br/><br />
Assign yourself a blueprint and get to work! When you have something, post a link to your design docs on AskOpenStack UX[http://ask-openstackux.rhcloud.com/questions/] and ask for feedback. There'll be the usual revisions. Designs that are ready to go can be added to a new or existing blueprint on the Horizon project site[https://launchpad.net/horizon]. Then, wait for a dev to implement your design. You will be expected to work with developers to answer questions or make updates to your design along the way.<br />
<br/><br/><br />
<b>That's a pretty vague process. Can't you give me a little more detail than that?</b><br/><br />
Nope, not yet. We're new to this so the process is pretty ad hoc. We'd love your help making it better! Make suggestions.<br />
<br/><br/><br />
<b>I don't see a blueprint for the work I want to do. What can I do? </b><br/><br />
Create a new blueprint! Here is a great guide on creating blueprints[https://wiki.openstack.org/wiki/Blueprints#Creation].<br />
<br/><br/><br />
<b>Is there any user research I can leverage?</b><br/><br />
Yes! Check out this group that is working on personas and usability[https://wiki.openstack.org/wiki/Personas]. Also, if you are going to do your own research, we'd love for you to contribute results or better yet, to collaborate with you.<br />
<br/><br/><br />
<b>Where can I ask questions or get feedback on my designs?</b><br/><br />
AskUX, Horizon weekly meeting[https://wiki.openstack.org/wiki/Meetings#Horizon_team_meeting], #openstack-ux on Freenode.<br />
<br/><br/><br />
<b>Where can I ask questions about technical feasibility or understanding the problem space?</b><br/><br />
AskUX, Horizon weekly meetings, Horizon Launchpad, openstack-dev@lists.openstack.org, #openstack-horizon on Freenode.<br />
<br />
=== Horizon Proposals ===<br />
[https://wiki.openstack.org/wiki/UX/Improve_User_Experience_of_Messaging_in_Horizon Improve User Experience of Messaging in Horizon]<br />
<br />
[https://wiki.openstack.org/wiki/UX/Improvements_to_Inline_Help_in_Horizon Improvements to Inline Help in Horizon]<br />
<br />
=== UX Archive ===<br />
[https://plus.google.com/u/0/communities/100954512393463248122 Community Sites (old, in transition)]<br />
</p></div>Liz Blanchardhttps://wiki.openstack.org/w/index.php?title=UX&diff=52919UX2014-05-21T13:09:10Z<p>Liz Blanchard: /* Getting Started with Designing for User Experience */</p>
<hr />
<div>== OpenStack User Experience ==<br />
<br />
<p>'''Mission Statement:''' Enable OpenStack users to be efficient and make their experience consistent and pleasurable.</p><br />
<br />
User Experience (UX) is community-oriented and available for different audiences on several websites. This wiki serves as an informational source for UX-related activities (workstreams) that goes across multiple OpenStack projects.<br />
<br />
=== UX Workstreams ===<br />
[http://ask-openstackux.rhcloud.com UX Discussion Forum (new, temporary address)] <br/><br />
[https://wiki.openstack.org/wiki/Personas OpenStack Personas Working Group] <br/><br />
[https://wiki.openstack.org/wiki/HorizonUsability_Testing Usability Testing] <br/><br />
[https://launchpad.net/openstack-ux Features, Bugs, and Releases in Launchpad] <br/><br />
[https://wiki.openstack.org/wiki/UX/ProgramProposal OpenStack UX Program Proposal] <br/><br />
IRC: #openstack-ux (at FreeNode) <br/><br />
[https://wiki.openstack.org/wiki/UX/openstack-ux-videos OpenStack UX Videos] <br/><br />
<br />
===Getting Involved as a Developer with Designing for User Experience===<br />
<br />
<b>Are you a developer looking for feedback or help with designing new features? Are you looking for help on improving a current feature?</b><br/><br />
Please feel free to reach out to us via the openstack developer mailing list (openstack-dev@lists.openstack.org). In the subject use the tag [UX] and we will be sure to see your question/request. In the near future we will be holding UX specific meetings every other week on IRC. You are welcome to come attend those as well and ask any questions you may have during Open Discussion. Meeting information will be posted here as well as on the OpenStack Meetings[https://wiki.openstack.org/wiki/Meetings] page as soon as it's available. One additional way to get quick feedback or have a discussion with the UX group is to join our IRC channel on freenode (#openstack-ux). If you don't get an immediate response, feel free to ask again later or jump over to using the mailing list!<br />
<br/><br/><br />
<br />
===Getting Involved as a Designer with Designing for User Experience===<br />
<br />
<b>How do I get involved with OpenStack UX and work on blueprints?</b><br/><br />
We track the work that we are doing on our launchpad site[https://launchpad.net/openstack-ux]. If you aren't ready to contribute your own designs, start off by giving others feedback on launchpad or on AskOpenStack UX[http://ask-openstackux.rhcloud.com/questions/].<br />
<br/><br/><br />
<b>What's a blueprint in Launchpad?</b><br/><br />
It's a specification for a feature in OpenStack. In UX, this usually is presented as wireframes or prototypes, but it can be something else. There's lots more info on openstack.org[https://wiki.openstack.org/wiki/Blueprints].<br />
<br/><br/><br />
<b>How does this whole OpenStack contributor thing work anyway?</b><br/><br />
There is great getting started documentation on openstack.org. How to Contribute[https://wiki.openstack.org/wiki/How_To_Contribute] is a good place to start.<br />
<br/><br/><br />
<b>What is the process for getting a new design into Horizon?</b><br/><br />
Assign yourself a blueprint and get to work! When you have something, post a link to your design docs on AskOpenStack UX[http://ask-openstackux.rhcloud.com/questions/] and ask for feedback. There'll be the usual revisions. Designs that are ready to go can be added to a new or existing blueprint on the Horizon project site[https://launchpad.net/horizon]. Then, wait for a dev to implement your design. You will be expected to work with developers to answer questions or make updates to your design along the way.<br />
<br/><br/><br />
<b>That's a pretty vague process. Can't you give me a little more detail than that?</b><br/><br />
Nope, not yet. We're new to this so the process is pretty ad hoc. We'd love your help making it better! Make suggestions.<br />
<br/><br/><br />
<b>I don't see a blueprint for the work I want to do. What can I do? </b><br/><br />
Create a new blueprint! Here is a great guide on creating blueprints[https://wiki.openstack.org/wiki/Blueprints#Creation].<br />
<br/><br/><br />
<b>Is there any user research I can leverage?</b><br/><br />
Yes! Check out this group that is working on personas and usability[https://wiki.openstack.org/wiki/Personas]. Also, if you are going to do your own research, we'd love for you to contribute results or better yet, to collaborate with you.<br />
<br/><br/><br />
<b>Where can I ask questions or get feedback on my designs?</b><br/><br />
AskUX, Horizon weekly meeting[https://wiki.openstack.org/wiki/Meetings#Horizon_team_meeting], #openstack-ux on Freenode.<br />
<br/><br/><br />
<b>Where can I ask questions about technical feasibility or understanding the problem space?</b><br/><br />
AskUX, Horizon weekly meetings, Horizon Launchpad, openstack-dev@lists.openstack.org, #openstack-horizon on Freenode.<br />
<br />
=== Horizon Proposals ===<br />
[https://wiki.openstack.org/wiki/UX/Improve_User_Experience_of_Messaging_in_Horizon Improve User Experience of Messaging in Horizon]<br />
<br />
=== UX Archive ===<br />
[https://plus.google.com/u/0/communities/100954512393463248122 Community Sites (old, in transition)]<br />
</p></div>Liz Blanchardhttps://wiki.openstack.org/w/index.php?title=UX/Improve_User_Experience_of_Messaging_in_Horizon&diff=52850UX/Improve User Experience of Messaging in Horizon2014-05-20T20:30:15Z<p>Liz Blanchard: </p>
<hr />
<div>===Improving the UX of Messages within Horizon===<br />
<br />
NOTE: There are certain items listed in the” Message Guidelines -- An Initial Proposal” section that Horizon does follow today, the Guidelines are meant to be a list to follow, not just to point out the gaps.<br />
<br />
----<br />
<br />
=====For reference, there have been a few blueprints that we’ve talked about in this space:=====<br />
* https://blueprints.launchpad.net/horizon/+spec/improve-error-message-details-for-usability<br />
* https://blueprints.launchpad.net/horizon/+spec/horizon-notifications<br />
* https://blueprints.launchpad.net/horizon/+spec/show-image-minimal-requirement-when-creating-instance<br />
<br />
<br />
====Current Usage of Errors====<br />
<br />
<br />
=====Pop-ups=====<br />
<br />
<br />
[[File:Popup.png]]<br />
<br />
=====Forms=====<br />
<br />
<br />
<br />
[[File:Form.png]]<br />
<br />
=====Visualizations=====<br />
<br />
<br />
[[File:Viz.png]]<br />
<br />
<br />
=====Issues with Current Approach=====<br />
<br />
In querying for “error message(s)” in Horizon, the query returned 49 bugs that were in various stages -- about 22 of them were being addressed (in progress or fix committed). This is a small subset of the list:<br />
* https://bugs.launchpad.net/horizon/+bug/1281679<br />
* https://bugs.launchpad.net/horizon/+bug/1155008<br />
* https://bugs.launchpad.net/horizon/+bug/1270984<br />
* https://bugs.launchpad.net/horizon/+bug/1274146<br />
* https://bugs.launchpad.net/horizon/+bug/1274234<br />
* https://bugs.launchpad.net/horizon/+bug/1275043<br />
* https://bugs.launchpad.net/horizon/+bug/1282232<br />
* https://bugs.launchpad.net/horizon/+bug/970693<br />
* https://bugs.launchpad.net/horizon/+bug/1018253<br />
* https://bugs.launchpad.net/horizon/+bug/1179607<br />
* https://bugs.launchpad.net/horizon/+bug/1261485<br />
* https://bugs.launchpad.net/horizon/+bug/1223361<br />
* https://bugs.launchpad.net/horizon/+bug/1237711<br />
* https://bugs.launchpad.net/horizon/+bug/1270817<br />
* https://bugs.launchpad.net/horizon/+bug/1276696<br />
* https://bugs.launchpad.net/horizon/+bug/1278482<br />
* https://bugs.launchpad.net/horizon/+bug/1285147<br />
* https://bugs.launchpad.net/horizon/+bug/1296430<br />
* https://bugs.launchpad.net/horizon/+bug/1283248<br />
* https://bugs.launchpad.net/horizon/+bug/1270738<br />
<br />
<br />
=====The issues seem to fall into the following categories:=====<br />
# Lack of human readable information to understand what to do next<br />
# Unclear or vague error message<br />
# Lack of error message when an error occurs<br />
# Error messages are sometimes inconsistent with what is seen in CLI<br />
# Lack of or no guidance provided to the user on how to resolve the error<br />
<br />
<br />
They seem to pertain to informational, warning, and error messages.<br />
<br />
<br />
NOTE: There are also many bugs for services outside Horizon that face similar challenges that can benefit from this effort.<br />
----<br />
====Message Guidelines -- An Initial Proposal====<br />
<br />
A message delivers information about an action or condition and optionally asks the user to confirm the situation. The scope of this document is limited to Error, Informational, and Warning messages.<br />
<br />
<br />
=====The following is a suggested set of guidelines for the following types of messages:=====<br />
* Error message -- this is used to report a problem and indicates to the user that some action must be taken before the System or Service can continue. E.g. an error message might indicate the user lacks permission to execute a requested action or show a problem found after a user chooses an action in a menu, dialog, or wizard.<br />
* Informational message -- it’s used to guide users through a workflow or convey a pertinent message. It can be used to provide the results of an action or indicate that the System or Service is in the process of performing some kind of action.<br />
* Warning message -- When you want to make users aware of a potentially harmful or problematic condition, give them a warning.<br />
<br />
<br />
=====The solution should be something that ultimately focuses on a few things when it comes to giving error messages to our users:=====<br />
# Continuing to place error messages in a visible area for the end user<br />
# Giving enough human readable information to understand what to do next<br />
# Ensuring every error will result in notifying the user<br />
# Consistency of messages between API, CLI, and UI<br />
<br />
<br />
=====Tips and Best Practices for all Messages:=====<br />
<br />
======Visibility:======<br />
* Ensure the message is prominent.<br />
<br />
======Human Readable:======<br />
* Whenever possible, provide names, locations, objects, and values of the objects involved.<br />
* Indicate what condition has occurred and which service or component is involved (if relevant).<br />
* If the application displays a message generated by another application (e.g. a pass-through message), include the name of the other application.<br />
* If the message was generated by an application (as opposed to a user), indicate the application name and/or relevant action.<br />
* Be concise, specific, and address the user as "you".<br />
* Don't blame the user.<br />
* Use active voice. Active voice makes writing more simple and direct.<br />
* Avoid the words "please" and "sorry."<br />
* Write complete sentences and use ending punctuation.<br />
* Make the object plural when the user selects more than one object. <br />
* Use language that is familiar to the user.<br />
* Do not use contractions. Contractions pose a problem for translators and for people who are not native English speakers.<br />
** Original: Can't connect to Horizon<br />
** Rewrite: Cannot connect to Horizon<br />
<br />
======Make sure the user knows where to go from here:======<br />
* State the specific error or warning and recommendation for how the user can correct the error.<br />
* If a problem exists, state why the problem occurred, and how to remedy the situation, even if the remedy is "Contact your Administrator."<br />
* If the recommendation is a series of tasks the user needs to perform,state the instructions in the correct sequence.<br />
* Avoid messages that are too general and do not highlight the problem in a way that makes sense in the context in which the message is displayed.<br />
* Ensure that users can copy the text in the message window and paste it elsewhere.<br />
<br />
======Consistency:======<br />
* Ensure consistent messages between UI, CLI, and API.<br />
* Use same name as the menu, action, or command button that opened the message box.<br />
* Tips and Best Practices for Forms Specifically:<br />
* It’s important to be proactive and stop users before they submit a form with an error when possible. If they do submit the form with an error, be sure to do the following:<br />
* Make it clear that something is wrong. <br />
* Show the user which field (or fields) are wrong in form errors. <br />
* Display error messages that help users get back on track. <br />
* Save what the user has entered—both good and bad so they do not have to repeat data entry.<br />
<br />
<br />
=====Tips and Best Practices for Visualizations Specifically:=====<br />
* We should be sure to include text explaining the error that the visualization is showing, whether this is near the visualization or on hover. Allowing the user to get more information on * why they are seeing an error and how to troubleshoot it in clear text is important for them to be able to choose what to do next.</div>Liz Blanchardhttps://wiki.openstack.org/w/index.php?title=File:Viz.png&diff=52849File:Viz.png2014-05-20T20:28:38Z<p>Liz Blanchard: </p>
<hr />
<div></div>Liz Blanchardhttps://wiki.openstack.org/w/index.php?title=File:Form.png&diff=52848File:Form.png2014-05-20T20:28:23Z<p>Liz Blanchard: </p>
<hr />
<div></div>Liz Blanchardhttps://wiki.openstack.org/w/index.php?title=File:Popup.png&diff=52847File:Popup.png2014-05-20T20:27:52Z<p>Liz Blanchard: </p>
<hr />
<div></div>Liz Blanchardhttps://wiki.openstack.org/w/index.php?title=UX&diff=52843UX2014-05-20T20:00:58Z<p>Liz Blanchard: /* Horizon Proposals */</p>
<hr />
<div>== OpenStack User Experience ==<br />
<br />
<p>'''Mission Statement:''' Enable OpenStack users to be efficient and make their experience consistent and pleasurable.</p><br />
<br />
User Experience (UX) is community-oriented and available for different audiences on several websites. This wiki serves as an informational source for UX-related activities (workstreams) that goes across multiple OpenStack projects.<br />
<br />
=== UX Workstreams ===<br />
[http://ask-openstackux.rhcloud.com UX Discussion Forum (new, temporary address)] <br/><br />
[https://wiki.openstack.org/wiki/Personas OpenStack Personas Working Group] <br/><br />
[https://wiki.openstack.org/wiki/HorizonUsability_Testing Usability Testing] <br/><br />
[https://launchpad.net/openstack-ux Features, Bugs, and Releases in Launchpad] <br/><br />
[https://wiki.openstack.org/wiki/UX/ProgramProposal OpenStack UX Program Proposal] <br/><br />
IRC: #openstack-ux (at FreeNode) <br/><br />
[https://wiki.openstack.org/wiki/UX/openstack-ux-videos OpenStack UX Videos] <br/><br />
<br />
===Getting Started with Designing for User Experience===<br />
<br />
<b>How do I get involved with OpenStack UX and work on blueprints?</b><br/><br />
We track the work that we are doing on our launchpad site[https://launchpad.net/openstack-ux]. If you aren't ready to contribute your own designs, start off by giving others feedback on launchpad or on AskOpenStack UX[http://ask-openstackux.rhcloud.com/questions/].<br />
<br/><br/><br />
<b>What's a blueprint in Launchpad?</b><br/><br />
It's a specification for a feature in OpenStack. In UX, this usually is presented as wireframes or prototypes, but it can be something else. There's lots more info on openstack.org[https://wiki.openstack.org/wiki/Blueprints].<br />
<br/><br/><br />
<b>How does this whole OpenStack contributor thing work anyway?</b><br/><br />
There is great getting started documentation on openstack.org. How to Contribute[https://wiki.openstack.org/wiki/How_To_Contribute] is a good place to start.<br />
<br/><br/><br />
<b>What is the process for getting a new design into Horizon?</b><br/><br />
Assign yourself a blueprint and get to work! When you have something, post a link to your design docs on AskOpenStack UX[http://ask-openstackux.rhcloud.com/questions/] and ask for feedback. There'll be the usual revisions. Designs that are ready to go can be added to a new or existing blueprint on the Horizon project site[https://launchpad.net/horizon]. Then, wait for a dev to implement your design. You will be expected to work with developers to answer questions or make updates to your design along the way.<br />
<br/><br/><br />
<b>That's a pretty vague process. Can't you give me a little more detail than that?</b><br/><br />
Nope, not yet. We're new to this so the process is pretty ad hoc. We'd love your help making it better! Make suggestions.<br />
<br/><br/><br />
<b>I don't see a blueprint for the work I want to do. What can I do? </b><br/><br />
Create a new blueprint! Here is a great guide on creating blueprints[https://wiki.openstack.org/wiki/Blueprints#Creation].<br />
<br/><br/><br />
<b>Is there any user research I can leverage?</b><br/><br />
Yes! Check out this group that is working on personas and usability[https://wiki.openstack.org/wiki/Personas]. Also, if you are going to do your own research, we'd love for you to contribute results or better yet, to collaborate with you.<br />
<br/><br/><br />
<b>Where can I ask questions or get feedback on my designs?</b><br/><br />
AskUX, Horizon weekly meeting[https://wiki.openstack.org/wiki/Meetings#Horizon_team_meeting], #openstack-ux on Freenode.<br />
<br/><br/><br />
<b>Where can I ask questions about technical feasibility or understanding the problem space?</b><br/><br />
AskUX, Horizon weekly meetings, Horizon Launchpad, openstack-dev@lists.openstack.org, #openstack-horizon on Freenode.<br />
<br />
=== Horizon Proposals ===<br />
[https://wiki.openstack.org/wiki/UX/Improve_User_Experience_of_Messaging_in_Horizon Improve User Experience of Messaging in Horizon]<br />
<br />
=== UX Archive ===<br />
[https://plus.google.com/u/0/communities/100954512393463248122 Community Sites (old, in transition)]<br />
</p></div>Liz Blanchardhttps://wiki.openstack.org/w/index.php?title=UX/Improve_User_Experience_of_Messaging_in_Horizon&diff=52840UX/Improve User Experience of Messaging in Horizon2014-05-20T19:57:43Z<p>Liz Blanchard: Liz Blanchard moved page Improve User Experience of Messaging in Horizon to UX/Improve User Experience of Messaging in Horizon</p>
<hr />
<div>===Improving the UX of Messages within Horizon===<br />
<br />
NOTE: There are certain items listed in the” Message Guidelines -- An Initial Proposal” section that Horizon does follow today, the Guidelines are meant to be a list to follow, not just to point out the gaps.<br />
<br />
----<br />
<br />
=====For reference, there have been a few blueprints that we’ve talked about in this space:=====<br />
* https://blueprints.launchpad.net/horizon/+spec/improve-error-message-details-for-usability<br />
* https://blueprints.launchpad.net/horizon/+spec/horizon-notifications<br />
* https://blueprints.launchpad.net/horizon/+spec/show-image-minimal-requirement-when-creating-instance<br />
<br />
<br />
====Current Usage of Errors====<br />
<br />
<br />
=====Pop-ups=====<br />
<br />
<br />
Image needed<br />
<br />
=====Forms=====<br />
<br />
<br />
<br />
Image needed<br />
<br />
=====Visualizations=====<br />
<br />
<br />
Image needed<br />
<br />
<br />
=====Issues with Current Approach=====<br />
<br />
In querying for “error message(s)” in Horizon, the query returned 49 bugs that were in various stages -- about 22 of them were being addressed (in progress or fix committed). This is a small subset of the list:<br />
* https://bugs.launchpad.net/horizon/+bug/1281679<br />
* https://bugs.launchpad.net/horizon/+bug/1155008<br />
* https://bugs.launchpad.net/horizon/+bug/1270984<br />
* https://bugs.launchpad.net/horizon/+bug/1274146<br />
* https://bugs.launchpad.net/horizon/+bug/1274234<br />
* https://bugs.launchpad.net/horizon/+bug/1275043<br />
* https://bugs.launchpad.net/horizon/+bug/1282232<br />
* https://bugs.launchpad.net/horizon/+bug/970693<br />
* https://bugs.launchpad.net/horizon/+bug/1018253<br />
* https://bugs.launchpad.net/horizon/+bug/1179607<br />
* https://bugs.launchpad.net/horizon/+bug/1261485<br />
* https://bugs.launchpad.net/horizon/+bug/1223361<br />
* https://bugs.launchpad.net/horizon/+bug/1237711<br />
* https://bugs.launchpad.net/horizon/+bug/1270817<br />
* https://bugs.launchpad.net/horizon/+bug/1276696<br />
* https://bugs.launchpad.net/horizon/+bug/1278482<br />
* https://bugs.launchpad.net/horizon/+bug/1285147<br />
* https://bugs.launchpad.net/horizon/+bug/1296430<br />
* https://bugs.launchpad.net/horizon/+bug/1283248<br />
* https://bugs.launchpad.net/horizon/+bug/1270738<br />
<br />
<br />
=====The issues seem to fall into the following categories:=====<br />
# Lack of human readable information to understand what to do next<br />
# Unclear or vague error message<br />
# Lack of error message when an error occurs<br />
# Error messages are sometimes inconsistent with what is seen in CLI<br />
# Lack of or no guidance provided to the user on how to resolve the error<br />
<br />
<br />
They seem to pertain to informational, warning, and error messages.<br />
<br />
<br />
NOTE: There are also many bugs for services outside Horizon that face similar challenges that can benefit from this effort.<br />
----<br />
====Message Guidelines -- An Initial Proposal====<br />
<br />
A message delivers information about an action or condition and optionally asks the user to confirm the situation. The scope of this document is limited to Error, Informational, and Warning messages.<br />
<br />
<br />
=====The following is a suggested set of guidelines for the following types of messages:=====<br />
* Error message -- this is used to report a problem and indicates to the user that some action must be taken before the System or Service can continue. E.g. an error message might indicate the user lacks permission to execute a requested action or show a problem found after a user chooses an action in a menu, dialog, or wizard.<br />
* Informational message -- it’s used to guide users through a workflow or convey a pertinent message. It can be used to provide the results of an action or indicate that the System or Service is in the process of performing some kind of action.<br />
* Warning message -- When you want to make users aware of a potentially harmful or problematic condition, give them a warning.<br />
<br />
<br />
=====The solution should be something that ultimately focuses on a few things when it comes to giving error messages to our users:=====<br />
# Continuing to place error messages in a visible area for the end user<br />
# Giving enough human readable information to understand what to do next<br />
# Ensuring every error will result in notifying the user<br />
# Consistency of messages between API, CLI, and UI<br />
<br />
<br />
=====Tips and Best Practices for all Messages:=====<br />
<br />
======Visibility:======<br />
* Ensure the message is prominent.<br />
<br />
======Human Readable:======<br />
* Whenever possible, provide names, locations, objects, and values of the objects involved.<br />
* Indicate what condition has occurred and which service or component is involved (if relevant).<br />
* If the application displays a message generated by another application (e.g. a pass-through message), include the name of the other application.<br />
* If the message was generated by an application (as opposed to a user), indicate the application name and/or relevant action.<br />
* Be concise, specific, and address the user as "you".<br />
* Don't blame the user.<br />
* Use active voice. Active voice makes writing more simple and direct.<br />
* Avoid the words "please" and "sorry."<br />
* Write complete sentences and use ending punctuation.<br />
* Make the object plural when the user selects more than one object. <br />
* Use language that is familiar to the user.<br />
* Do not use contractions. Contractions pose a problem for translators and for people who are not native English speakers.<br />
** Original: Can't connect to Horizon<br />
** Rewrite: Cannot connect to Horizon<br />
<br />
======Make sure the user knows where to go from here:======<br />
* State the specific error or warning and recommendation for how the user can correct the error.<br />
* If a problem exists, state why the problem occurred, and how to remedy the situation, even if the remedy is "Contact your Administrator."<br />
* If the recommendation is a series of tasks the user needs to perform,state the instructions in the correct sequence.<br />
* Avoid messages that are too general and do not highlight the problem in a way that makes sense in the context in which the message is displayed.<br />
* Ensure that users can copy the text in the message window and paste it elsewhere.<br />
<br />
======Consistency:======<br />
* Ensure consistent messages between UI, CLI, and API.<br />
* Use same name as the menu, action, or command button that opened the message box.<br />
* Tips and Best Practices for Forms Specifically:<br />
* It’s important to be proactive and stop users before they submit a form with an error when possible. If they do submit the form with an error, be sure to do the following:<br />
* Make it clear that something is wrong. <br />
* Show the user which field (or fields) are wrong in form errors. <br />
* Display error messages that help users get back on track. <br />
* Save what the user has entered—both good and bad so they do not have to repeat data entry.<br />
<br />
<br />
=====Tips and Best Practices for Visualizations Specifically:=====<br />
* We should be sure to include text explaining the error that the visualization is showing, whether this is near the visualization or on hover. Allowing the user to get more information on * why they are seeing an error and how to troubleshoot it in clear text is important for them to be able to choose what to do next.</div>Liz Blanchardhttps://wiki.openstack.org/w/index.php?title=Improve_User_Experience_of_Messaging_in_Horizon&diff=52841Improve User Experience of Messaging in Horizon2014-05-20T19:57:43Z<p>Liz Blanchard: Liz Blanchard moved page Improve User Experience of Messaging in Horizon to UX/Improve User Experience of Messaging in Horizon</p>
<hr />
<div>#REDIRECT [[UX/Improve User Experience of Messaging in Horizon]]</div>Liz Blanchardhttps://wiki.openstack.org/w/index.php?title=UX/Improve_User_Experience_of_Messaging_in_Horizon&diff=52839UX/Improve User Experience of Messaging in Horizon2014-05-20T19:56:00Z<p>Liz Blanchard: Initial cut at some UX guidelines around Messaging in Horizon</p>
<hr />
<div>===Improving the UX of Messages within Horizon===<br />
<br />
NOTE: There are certain items listed in the” Message Guidelines -- An Initial Proposal” section that Horizon does follow today, the Guidelines are meant to be a list to follow, not just to point out the gaps.<br />
<br />
----<br />
<br />
=====For reference, there have been a few blueprints that we’ve talked about in this space:=====<br />
* https://blueprints.launchpad.net/horizon/+spec/improve-error-message-details-for-usability<br />
* https://blueprints.launchpad.net/horizon/+spec/horizon-notifications<br />
* https://blueprints.launchpad.net/horizon/+spec/show-image-minimal-requirement-when-creating-instance<br />
<br />
<br />
====Current Usage of Errors====<br />
<br />
<br />
=====Pop-ups=====<br />
<br />
<br />
Image needed<br />
<br />
=====Forms=====<br />
<br />
<br />
<br />
Image needed<br />
<br />
=====Visualizations=====<br />
<br />
<br />
Image needed<br />
<br />
<br />
=====Issues with Current Approach=====<br />
<br />
In querying for “error message(s)” in Horizon, the query returned 49 bugs that were in various stages -- about 22 of them were being addressed (in progress or fix committed). This is a small subset of the list:<br />
* https://bugs.launchpad.net/horizon/+bug/1281679<br />
* https://bugs.launchpad.net/horizon/+bug/1155008<br />
* https://bugs.launchpad.net/horizon/+bug/1270984<br />
* https://bugs.launchpad.net/horizon/+bug/1274146<br />
* https://bugs.launchpad.net/horizon/+bug/1274234<br />
* https://bugs.launchpad.net/horizon/+bug/1275043<br />
* https://bugs.launchpad.net/horizon/+bug/1282232<br />
* https://bugs.launchpad.net/horizon/+bug/970693<br />
* https://bugs.launchpad.net/horizon/+bug/1018253<br />
* https://bugs.launchpad.net/horizon/+bug/1179607<br />
* https://bugs.launchpad.net/horizon/+bug/1261485<br />
* https://bugs.launchpad.net/horizon/+bug/1223361<br />
* https://bugs.launchpad.net/horizon/+bug/1237711<br />
* https://bugs.launchpad.net/horizon/+bug/1270817<br />
* https://bugs.launchpad.net/horizon/+bug/1276696<br />
* https://bugs.launchpad.net/horizon/+bug/1278482<br />
* https://bugs.launchpad.net/horizon/+bug/1285147<br />
* https://bugs.launchpad.net/horizon/+bug/1296430<br />
* https://bugs.launchpad.net/horizon/+bug/1283248<br />
* https://bugs.launchpad.net/horizon/+bug/1270738<br />
<br />
<br />
=====The issues seem to fall into the following categories:=====<br />
# Lack of human readable information to understand what to do next<br />
# Unclear or vague error message<br />
# Lack of error message when an error occurs<br />
# Error messages are sometimes inconsistent with what is seen in CLI<br />
# Lack of or no guidance provided to the user on how to resolve the error<br />
<br />
<br />
They seem to pertain to informational, warning, and error messages.<br />
<br />
<br />
NOTE: There are also many bugs for services outside Horizon that face similar challenges that can benefit from this effort.<br />
----<br />
====Message Guidelines -- An Initial Proposal====<br />
<br />
A message delivers information about an action or condition and optionally asks the user to confirm the situation. The scope of this document is limited to Error, Informational, and Warning messages.<br />
<br />
<br />
=====The following is a suggested set of guidelines for the following types of messages:=====<br />
* Error message -- this is used to report a problem and indicates to the user that some action must be taken before the System or Service can continue. E.g. an error message might indicate the user lacks permission to execute a requested action or show a problem found after a user chooses an action in a menu, dialog, or wizard.<br />
* Informational message -- it’s used to guide users through a workflow or convey a pertinent message. It can be used to provide the results of an action or indicate that the System or Service is in the process of performing some kind of action.<br />
* Warning message -- When you want to make users aware of a potentially harmful or problematic condition, give them a warning.<br />
<br />
<br />
=====The solution should be something that ultimately focuses on a few things when it comes to giving error messages to our users:=====<br />
# Continuing to place error messages in a visible area for the end user<br />
# Giving enough human readable information to understand what to do next<br />
# Ensuring every error will result in notifying the user<br />
# Consistency of messages between API, CLI, and UI<br />
<br />
<br />
=====Tips and Best Practices for all Messages:=====<br />
<br />
======Visibility:======<br />
* Ensure the message is prominent.<br />
<br />
======Human Readable:======<br />
* Whenever possible, provide names, locations, objects, and values of the objects involved.<br />
* Indicate what condition has occurred and which service or component is involved (if relevant).<br />
* If the application displays a message generated by another application (e.g. a pass-through message), include the name of the other application.<br />
* If the message was generated by an application (as opposed to a user), indicate the application name and/or relevant action.<br />
* Be concise, specific, and address the user as "you".<br />
* Don't blame the user.<br />
* Use active voice. Active voice makes writing more simple and direct.<br />
* Avoid the words "please" and "sorry."<br />
* Write complete sentences and use ending punctuation.<br />
* Make the object plural when the user selects more than one object. <br />
* Use language that is familiar to the user.<br />
* Do not use contractions. Contractions pose a problem for translators and for people who are not native English speakers.<br />
** Original: Can't connect to Horizon<br />
** Rewrite: Cannot connect to Horizon<br />
<br />
======Make sure the user knows where to go from here:======<br />
* State the specific error or warning and recommendation for how the user can correct the error.<br />
* If a problem exists, state why the problem occurred, and how to remedy the situation, even if the remedy is "Contact your Administrator."<br />
* If the recommendation is a series of tasks the user needs to perform,state the instructions in the correct sequence.<br />
* Avoid messages that are too general and do not highlight the problem in a way that makes sense in the context in which the message is displayed.<br />
* Ensure that users can copy the text in the message window and paste it elsewhere.<br />
<br />
======Consistency:======<br />
* Ensure consistent messages between UI, CLI, and API.<br />
* Use same name as the menu, action, or command button that opened the message box.<br />
* Tips and Best Practices for Forms Specifically:<br />
* It’s important to be proactive and stop users before they submit a form with an error when possible. If they do submit the form with an error, be sure to do the following:<br />
* Make it clear that something is wrong. <br />
* Show the user which field (or fields) are wrong in form errors. <br />
* Display error messages that help users get back on track. <br />
* Save what the user has entered—both good and bad so they do not have to repeat data entry.<br />
<br />
<br />
=====Tips and Best Practices for Visualizations Specifically:=====<br />
* We should be sure to include text explaining the error that the visualization is showing, whether this is near the visualization or on hover. Allowing the user to get more information on * why they are seeing an error and how to troubleshoot it in clear text is important for them to be able to choose what to do next.</div>Liz Blanchardhttps://wiki.openstack.org/w/index.php?title=UX&diff=52837UX2014-05-20T19:34:44Z<p>Liz Blanchard: </p>
<hr />
<div>== OpenStack User Experience ==<br />
<br />
<p>'''Mission Statement:''' Enable OpenStack users to be efficient and make their experience consistent and pleasurable.</p><br />
<br />
User Experience (UX) is community-oriented and available for different audiences on several websites. This wiki serves as an informational source for UX-related activities (workstreams) that goes across multiple OpenStack projects.<br />
<br />
=== UX Workstreams ===<br />
[http://ask-openstackux.rhcloud.com UX Discussion Forum (new, temporary address)] <br/><br />
[https://wiki.openstack.org/wiki/Personas OpenStack Personas Working Group] <br/><br />
[https://wiki.openstack.org/wiki/HorizonUsability_Testing Usability Testing] <br/><br />
[https://launchpad.net/openstack-ux Features, Bugs, and Releases in Launchpad] <br/><br />
[https://wiki.openstack.org/wiki/UX/ProgramProposal OpenStack UX Program Proposal] <br/><br />
IRC: #openstack-ux (at FreeNode) <br/><br />
[https://wiki.openstack.org/wiki/UX/openstack-ux-videos OpenStack UX Videos] <br/><br />
<br />
===Getting Started with Designing for User Experience===<br />
<br />
<b>How do I get involved with OpenStack UX and work on blueprints?</b><br/><br />
We track the work that we are doing on our launchpad site[https://launchpad.net/openstack-ux]. If you aren't ready to contribute your own designs, start off by giving others feedback on launchpad or on AskOpenStack UX[http://ask-openstackux.rhcloud.com/questions/].<br />
<br/><br/><br />
<b>What's a blueprint in Launchpad?</b><br/><br />
It's a specification for a feature in OpenStack. In UX, this usually is presented as wireframes or prototypes, but it can be something else. There's lots more info on openstack.org[https://wiki.openstack.org/wiki/Blueprints].<br />
<br/><br/><br />
<b>How does this whole OpenStack contributor thing work anyway?</b><br/><br />
There is great getting started documentation on openstack.org. How to Contribute[https://wiki.openstack.org/wiki/How_To_Contribute] is a good place to start.<br />
<br/><br/><br />
<b>What is the process for getting a new design into Horizon?</b><br/><br />
Assign yourself a blueprint and get to work! When you have something, post a link to your design docs on AskOpenStack UX[http://ask-openstackux.rhcloud.com/questions/] and ask for feedback. There'll be the usual revisions. Designs that are ready to go can be added to a new or existing blueprint on the Horizon project site[https://launchpad.net/horizon]. Then, wait for a dev to implement your design. You will be expected to work with developers to answer questions or make updates to your design along the way.<br />
<br/><br/><br />
<b>That's a pretty vague process. Can't you give me a little more detail than that?</b><br/><br />
Nope, not yet. We're new to this so the process is pretty ad hoc. We'd love your help making it better! Make suggestions.<br />
<br/><br/><br />
<b>I don't see a blueprint for the work I want to do. What can I do? </b><br/><br />
Create a new blueprint! Here is a great guide on creating blueprints[https://wiki.openstack.org/wiki/Blueprints#Creation].<br />
<br/><br/><br />
<b>Is there any user research I can leverage?</b><br/><br />
Yes! Check out this group that is working on personas and usability[https://wiki.openstack.org/wiki/Personas]. Also, if you are going to do your own research, we'd love for you to contribute results or better yet, to collaborate with you.<br />
<br/><br/><br />
<b>Where can I ask questions or get feedback on my designs?</b><br/><br />
AskUX, Horizon weekly meeting[https://wiki.openstack.org/wiki/Meetings#Horizon_team_meeting], #openstack-ux on Freenode.<br />
<br/><br/><br />
<b>Where can I ask questions about technical feasibility or understanding the problem space?</b><br/><br />
AskUX, Horizon weekly meetings, Horizon Launchpad, openstack-dev@lists.openstack.org, #openstack-horizon on Freenode.<br />
<br />
=== Horizon Proposals ===<br />
[[Improve User Experience of Messaging in Horizon]]<br />
<br />
=== UX Archive ===<br />
[https://plus.google.com/u/0/communities/100954512393463248122 Community Sites (old, in transition)]<br />
</p></div>Liz Blanchardhttps://wiki.openstack.org/w/index.php?title=Design_Summit/Juno/Etherpads&diff=50436Design Summit/Juno/Etherpads2014-04-29T14:59:33Z<p>Liz Blanchard: </p>
<hr />
<div>[[Category:Summit]]<br />
[[Category:Juno]]<br />
[[Category:Etherpad]]<br />
<br />
<br />
<div style="column-count:3;-moz-column-count:3;-webkit-column-count:3"><br />
__TOC__<br />
</div><br />
<br />
== Ceilometer ==<br />
== Cinder ==<br />
==Cross-Project==<br />
* Tues 11:15-11:55 [https://etherpad.openstack.org/p/juno-cross-project-future-of-python The Future of Python Support]<br />
* Tues 14:00-14:40 [https://etherpad.openstack.org/p/juno-cross-oslo-library-releases New Oslo Library Releases and Your Project]<br />
* Tues 14:50-16:20 [https://etherpad.openstack.org/p/juno-summit-cross-project-user-experience User Experience Designers Gathering]<br />
<br />
== Devstack ==<br />
* Fri 16:00 [https://etherpad.openstack.org/p/juno-summit-devstack-update DevStack Update]<br />
* Fri 16:50 [https://etherpad.openstack.org/p/juno-summit-devstack-project-support DevStack Project Support]<br />
<br />
== Documentation ==<br />
== Glance ==<br />
== Heat ==<br />
<br />
* Wed 9.00-9:40 [https://etherpad.openstack.org/p/juno-summit-heat-dev-ops Dev/Ops Session]<br />
* Wed 9.50-10:30 [https://etherpad.openstack.org/p/juno-summit-heat-sw-orch Next Steps for Software Orchestration]<br />
* Wed 11.00-11:40 [https://etherpad.openstack.org/p/heat-workflow-vs-convergence Scaling, Robustness and Convergence]<br />
* Wed 11.50-12:30 [https://etherpad.openstack.org/p/juno-summit-heat-notifications Augmenting Polling with Notifications]<br />
* Wed 13.50-14:30 [https://etherpad.openstack.org/p/juno-summit-heat-event Event notifications]<br />
* Wed 14.40-15:20 [https://etherpad.openstack.org/p/juno-summit-heat-callbacks Stack and Resource lifecycle callbacks]<br />
* Wed 15.30-16:10 [https://etherpad.openstack.org/p/juno-summit-heat-api-v2 API v2]<br />
* Wed 16.30-17:10 [https://etherpad.openstack.org/p/juno-summit-heat-plugin-versioning Resource Plugin Versioning]<br />
<br />
== Horizon ==<br />
* Wed 16:30-17:10 [https://etherpad.openstack.org/p/juno-summit-horizon-devops Horizon Dev/Ops Session]<br />
* Wed 17:20-18:00 [https://etherpad.openstack.org/p/juno-summit-horizon-usability-test-results Review Horizon Usability Test feedback, proposals]<br />
* Fri 9:00-9:40 [https://etherpad.openstack.org/p/juno-summit-horizon-static-files Handling of static files]<br />
* Fri 9:50-10:30 [https://etherpad.openstack.org/p/juno-summit-horizon-widgets Modular, widget-based views and more pluggability]<br />
* Fri 10:50-11:30 [https://etherpad.openstack.org/p/juno-summit-horizon-client-side Client side development]<br />
<br />
== Infrastructure ==<br />
== Ironic ==<br />
<br />
* Tues 11:15 [https://etherpad.openstack.org/p/juno-summit-ironic-python-agent Ironic Python Agent]<br />
* Tues 12:05 [https://etherpad.openstack.org/p/juno-summit-ironic-multitenancy Hardware Multitenancy Risk Mitigation]<br />
* Tues 14:50 [https://etherpad.openstack.org/p/juno-summit-ironic-performance Performance and Scalability]<br />
* Tues 15:40 [https://etherpad.openstack.org/p/juno-summit-ironic-arch Planning changes for Juno]<br />
<br />
== Keystone ==<br />
== Marconi ==<br />
== Neutron ==<br />
* Wed 9:00-9:40: [https://etherpad.openstack.org/p/juno-neutron-policies New Policies for Neutron in Juno]<br />
* Wed 9:50-10:30: Code Review Process Improvements<br />
* Wed 11:00-11:40: IPv6 status in Neutron<br />
* Wed 11:50-12:30: ML2 Juno Roadmap<br />
**[https://etherpad.openstack.org/p/ML2_mechanismdriver_extensions_support Extensions Support In ML2 Mechanism Drivers]<br />
* Wed 13:50-14:30: Refactoring the Neutron Server Core<br />
* Wed 14:40-15:20: [https://etherpad.openstack.org/p/novanet-neutron-migration Nova-Net to Neutron migration]<br />
* Wed 15:30-14:10: Integrating Tasks into Neutron<br />
* Wed 16:30-17:10: Neutron Advanced Services and Flavor Framework<br />
* Wed 17:20-18:00: Neutron Distributed Virtual Router Progress Update<br />
* Thu 9:00-9:40: Neutron QA and Testing<br />
** https://etherpad.openstack.org/p/TempestAndNeutronJuno<br />
* Thu 9:50-10:30: Sharing the load of operational responsibility<br />
* Thu 11:00-11:40: Neutron LBaaS Update<br />
* Thur 11:50-12:30: Modular Layer2 Agents<br />
** https://etherpad.openstack.org/p/JunoSummit-ovs-firewall-driver<br />
* Fri 10:50-11:30: Neutron Group Based Policy<br />
* Fri 11:40-12:30: Combined FWaaS and VPNaaS Session<br />
* Fri 13:20-14:00: LBaaS SSL L7 and automated scenarios<br />
* Fri 14:10-14:50: Hierarchical Network Topologies<br />
** https://etherpad.openstack.org/p/hierarchical_network_topology<br />
* Fri 15:00-15:40: [https://etherpad.openstack.org/p/L3-vendor-plugins L3 Vendor Plugins]<br />
* Fri 16:00-16:40: Dynamic routing and pluggable external networks<br />
* Fri 16:50-17:30: Service VM Discussion:<br />
** https://etherpad.openstack.org/p/servicevm<br />
<br />
== Nova ==<br />
== Ops ==<br />
* Mon 1115 – 1155 [https://etherpad.openstack.org/p/juno-summit-ops-askthedevs Ask the devs: Meet the PTLs and TC, How to get the best out of the design summit]<br />
* Mon 1205 – 1245 [https://etherpad.openstack.org/p/juno-summit-ops-reasonabledefaults Reasonable Defaults]<br />
* Mon 1400 – 1440 [https://etherpad.openstack.org/p/juno-summit-ops-upgradesdeployment Upgrades and Deployment Approaches]<br />
* Mon 1450 – 1620 [https://etherpad.openstack.org/p/juno-summit-ops-architecture Architecture Show and Tell, Tales and Fails]<br />
* Mon 1730 – 1810 [https://etherpad.openstack.org/p/juno-summit-ops-security Security]<br />
<br />
* Fri 9:00 – 9:40 [https://etherpad.openstack.org/p/juno-summit-ops-enterprise Enterprise Gaps]<br />
* Fri 9:50 – 10:30 [https://etherpad.openstack.org/p/juno-summit-ops-database Database]<br />
* Fri 10:50 – 11:30 [https://etherpad.openstack.org/p/juno-summit-ops-issuesatscale Issues at Scale]<br />
* Fri 11:40 – 12:20 [https://etherpad.openstack.org/p/juno-summit-ops-meta Meta Discussion – ops communication and governance]<br />
* Fri 1:20 – 2:00 [https://etherpad.openstack.org/p/juno-summit-ops-ansible Ansible]<br />
* Fri 2:10 – 2:50 [https://etherpad.openstack.org/p/juno-summit-ops-chef Chef]<br />
* Fri 3:00 – 3:40 [https://etherpad.openstack.org/p/juno-summit-ops-puppet Puppet]<br />
* Fri 4:00 – 4:40 [https://etherpad.openstack.org/p/juno-summit-ops-networking Networking]<br />
* Fri 4:50 – 5:30 [https://etherpad.openstack.org/p/juno-summit-ops-monitoringlogging Monitoring and Logging]<br />
<br />
== Oslo ==<br />
* Wed 9:00 - 9:40 [https://etherpad.openstack.org/p/juno-oslo-release-plan Release Plan for Low-level Libraries]<br />
* Wed 9:50 - 10:30 Semantic versioning and oslo<br />
* Wed 11:00 - 11:40 oslo.rootwrap: performance and other improvements<br />
* Thu 9:00 - 9:40 Oslo Library Teams Breakout Session<br />
* Thu 9:50 - 10:30 [https://etherpad.openstack.org/p/juno-infra-library-testing Testing pre-releases of Oslo libs with apps]<br />
* Thu 11:00 - 11:40 OpenStack cross service/project OpenStack profiler<br />
* Thu 15:10 - 16:00 [https://etherpad.openstack.org/p/juno-oslo-bayer Upstream chat with Mike Bayer]<br />
* Thu 16:10 - 17:00 [https://etherpad.openstack.org/p/juno-summit-oslo-messaging-rpc-proxy rpc proxy(oslo.messaging)]<br />
* Fri 14:10 - 15:50 oslo.messaging status and plans for Juno<br />
* Fri 15:00 - 16:40 AMQP 1.0 protocol driver<br />
* Fri 16:00 - 16:40 PKI for messaging<br />
<br />
== QA ==<br />
<br />
===Wednesday===<br />
* 2:40 – 3:20 Branchless Tempest<br />
* 3:30 – 4:10 Tempest Documentation Gaps<br />
* 4:30 – 5:10 Functional API Testing - post dev QA vs TDD<br />
* 5:20 – 6:00 Rally and Tempest Integration<br />
<br />
===Thursday===<br />
* 1:30 – 2:10 [https://etherpad.openstack.org/p/juno-summit-api-tests-with-jsonschema API tests with JSONSchema]<br />
* 2:20 – 3:00 Negative Testing: Fuzzy Test Framework<br />
* 3:10 – 3:50 How to improve the UX of our Testing Tools<br />
* 4:10 – 4:50 Tempest, GUI, Client, Server<br />
<br />
===Friday===<br />
* 1:20 – 2:00 Grenade Current Status and Next Steps<br />
* 2:10– 2:50 [https://etherpad.openstack.org/p/juno-summit-qa-policy QA Program Policy and Changes in Juno]<br />
<br />
== Release Management ==<br />
== Sahara (ex. Savanna) ==<br />
<br />
* [http://junodesignsummit.sched.org/event/b4f52627efa42f285978d5af3643e189 Thu 13:30] [https://etherpad.openstack.org/p/juno-summit-sahara-relmngmt-backward Releasing and backward compatibility]<br />
* [http://junodesignsummit.sched.org/event/c8774beefd9e9188a3e0729d2bd7131e Thu 14:20] [https://etherpad.openstack.org/p/juno-summit-sahara-testing-plugins CI/gating and plugin requirements]<br />
* [http://junodesignsummit.sched.org/event/10bc9a23eb43eb9df885586035fb2491 Thu 15:10] [https://etherpad.openstack.org/p/juno-summit-sahara-scale-integration Scalable Sahara and further OpenStack integration]<br />
* [http://junodesignsummit.sched.org/event/be842178a085fe95b7665a653f8ab541 Thu 16:10] [https://etherpad.openstack.org/p/juno-summit-sahara-ux UX improvements]<br />
* [http://junodesignsummit.sched.org/event/dfa603324c0bbf29c2f09a77efb82d1d Thu 17:00] [https://etherpad.openstack.org/p/juno-summit-sahara-edp Future of EDP: plugins, SPI, Oozie]<br />
* [http://junodesignsummit.sched.org/event/a64f771cf28ed3ad637730db828668ff Fri 09:00] [https://etherpad.openstack.org/p/juno-summit-sahara-v2-api Next major REST API - v2]<br />
* [http://junodesignsummit.sched.org/event/49089a1d9c8203c6a4c1f0001fa417af Fri 09:50] [https://etherpad.openstack.org/p/juno-summit-sahara-roadmap-retro Sahara in Icehouse and Juno]<br />
<br />
== Swift ==<br />
== TripleO (Deployment) ==<br />
* Fri 11:40 - 12:20 [https://etherpad.openstack.org/p/juno-summit-tripleo-tuskar-planning TripleO Tuskar Planning]<br />
* Fri<br />
* Fri 14:10 - 14:50 [https://etherpad.openstack.org/p/juno-summit-tripleo-and-docker TripleO and Docker]<br />
* Fri 15:00 - 15:40 [https://etherpad.openstack.org/p/juno-summit-tripleo-ci TripleO CI]<br />
* Fri 16:00 - 16:40 [https://etherpad.openstack.org/p/juno-summit-tripleo-neutron TripleO and Neutron]<br />
* Fri 16:50 - 17:30 [https://etherpad.openstack.org/p/juno-summit-tripleo-devops TripleO Dev/Ops Session]<br />
<br />
== Trove ==<br />
== User Committee ==</div>Liz Blanchardhttps://wiki.openstack.org/w/index.php?title=Design_Summit/Juno/Etherpads&diff=50430Design Summit/Juno/Etherpads2014-04-29T14:32:06Z<p>Liz Blanchard: </p>
<hr />
<div>[[Category:Summit]]<br />
[[Category:Juno]]<br />
[[Category:Etherpad]]<br />
<br />
<br />
<div style="column-count:3;-moz-column-count:3;-webkit-column-count:3"><br />
__TOC__<br />
</div><br />
<br />
== Ceilometer ==<br />
== Cinder ==<br />
==Cross-Project==<br />
*Tues 14:50-16:20 [https://etherpad.openstack.org/p/juno-summit-cross-project-user-experience User Experience Designers Gathering]<br />
<br />
== Devstack ==<br />
* Fri 16:00 [https://etherpad.openstack.org/p/juno-summit-devstack-update DevStack Update]<br />
* Fri 16:50 [https://etherpad.openstack.org/p/juno-summit-devstack-project-support DevStack Project Support]<br />
<br />
== Documentation ==<br />
== Glance ==<br />
== Heat ==<br />
<br />
* Wed 9.00-9:40 [https://etherpad.openstack.org/p/juno-summit-heat-dev-ops Dev/Ops Session]<br />
* Wed 9.50-10:30 [https://etherpad.openstack.org/p/juno-summit-heat-sw-orch Next Steps for Software Orchestration]<br />
* Wed 11.00-11:40 [https://etherpad.openstack.org/p/heat-workflow-vs-convergence Scaling, Robustness and Convergence]<br />
* Wed 11.50-12:30 [https://etherpad.openstack.org/p/juno-summit-heat-notifications Augmenting Polling with Notifications]<br />
* Wed 13.50-14:30 [https://etherpad.openstack.org/p/juno-summit-heat-event Event notifications]<br />
* Wed 14.40-15:20 [https://etherpad.openstack.org/p/juno-summit-heat-callbacks Stack and Resource lifecycle callbacks]<br />
* Wed 15.30-16:10 [https://etherpad.openstack.org/p/juno-summit-heat-api-v2 API v2]<br />
* Wed 16.30-17:10 [https://etherpad.openstack.org/p/juno-summit-heat-plugin-versioning Resource Plugin Versioning]<br />
<br />
== Horizon ==<br />
* Wed 16:30-17:10 [https://etherpad.openstack.org/p/juno-summit-horizon-devops Horizon Dev/Ops Session]<br />
* Fri 9:00-9:40 [https://etherpad.openstack.org/p/juno-summit-horizon-static-files Handling of static files]<br />
* Fri 9:50-10:30 [https://etherpad.openstack.org/p/juno-summit-horizon-widgets Modular, widget-based views and more pluggability]<br />
* Fri 10:50-11:30 [https://etherpad.openstack.org/p/juno-summit-horizon-client-side Client side development]<br />
<br />
== Infrastructure ==<br />
== Ironic ==<br />
<br />
* Tues 11:15 [https://etherpad.openstack.org/p/juno-summit-ironic-python-agent Ironic Python Agent]<br />
* Tues 12:05 [https://etherpad.openstack.org/p/juno-summit-ironic-multitenancy Hardware Multitenancy Risk Mitigation]<br />
* Tues 14:50 [https://etherpad.openstack.org/p/juno-summit-ironic-performance Performance and Scalability]<br />
* Tues 15:40 [https://etherpad.openstack.org/p/juno-summit-ironic-arch Planning changes for Juno]<br />
<br />
== Keystone ==<br />
== Marconi ==<br />
== Neutron ==<br />
* Wed 9:00-9:40: [https://etherpad.openstack.org/p/juno-neutron-policies New Policies for Neutron in Juno]<br />
* Wed 9:50-10:30: Code Review Process Improvements<br />
* Wed 11:00-11:40: IPv6 status in Neutron<br />
* Wed 11:50-12:30: ML2 Juno Roadmap<br />
**[https://etherpad.openstack.org/p/ML2_mechanismdriver_extensions_support Extensions Support In ML2 Mechanism Drivers]<br />
* Wed 13:50-14:30: Refactoring the Neutron Server Core<br />
* Wed 14:40-15:20: [https://etherpad.openstack.org/p/novanet-neutron-migration Nova-Net to Neutron migration]<br />
* Wed 15:30-14:10: Integrating Tasks into Neutron<br />
* Wed 16:30-17:10: Neutron Advanced Services and Flavor Framework<br />
* Wed 17:20-18:00: Neutron Distributed Virtual Router Progress Update<br />
* Thu 9:00-9:40: Neutron QA and Testing<br />
** https://etherpad.openstack.org/p/TempestAndNeutronJuno<br />
* Thu 9:50-10:30: Sharing the load of operational responsibility<br />
* Thu 11:00-11:40: Neutron LBaaS Update<br />
* Thur 11:50-12:30: Modular Layer2 Agents<br />
** https://etherpad.openstack.org/p/JunoSummit-ovs-firewall-driver<br />
* Fri 10:50-11:30: Neutron Group Based Policy<br />
* Fri 11:40-12:30: Combined FWaaS and VPNaaS Session<br />
* Fri 13:20-14:00: LBaaS SSL L7 and automated scenarios<br />
* Fri 14:10-14:50: Hierarchical Network Topologies<br />
** https://etherpad.openstack.org/p/hierarchical_network_topology<br />
* Fri 15:00-15:40: [https://etherpad.openstack.org/p/L3-vendor-plugins L3 Vendor Plugins]<br />
* Fri 16:00-16:40: Dynamic routing and pluggable external networks<br />
* Fri 16:50-17:30: Service VM Discussion:<br />
** https://etherpad.openstack.org/p/servicevm<br />
<br />
== Nova ==<br />
== Ops ==<br />
* Mon 1115 – 1155 [https://etherpad.openstack.org/p/juno-summit-ops-askthedevs Ask the devs: Meet the PTLs and TC, How to get the best out of the design summit]<br />
* Mon 1205 – 1245 [https://etherpad.openstack.org/p/juno-summit-ops-reasonabledefaults Reasonable Defaults]<br />
* Mon 1400 – 1440 [https://etherpad.openstack.org/p/juno-summit-ops-upgradesdeployment Upgrades and Deployment Approaches]<br />
* Mon 1450 – 1620 [https://etherpad.openstack.org/p/juno-summit-ops-architecture Architecture Show and Tell, Tales and Fails]<br />
* Mon 1730 – 1810 [https://etherpad.openstack.org/p/juno-summit-ops-security Security]<br />
<br />
* Fri 9:00 – 9:40 [https://etherpad.openstack.org/p/juno-summit-ops-enterprise Enterprise Gaps]<br />
* Fri 9:50 – 10:30 [https://etherpad.openstack.org/p/juno-summit-ops-database Database]<br />
* Fri 10:50 – 11:30 [https://etherpad.openstack.org/p/juno-summit-ops-issuesatscale Issues at Scale]<br />
* Fri 11:40 – 12:20 [https://etherpad.openstack.org/p/juno-summit-ops-meta Meta Discussion – ops communication and governance]<br />
* Fri 1:20 – 2:00 [https://etherpad.openstack.org/p/juno-summit-ops-ansible Ansible]<br />
* Fri 2:10 – 2:50 [https://etherpad.openstack.org/p/juno-summit-ops-chef Chef]<br />
* Fri 3:00 – 3:40 [https://etherpad.openstack.org/p/juno-summit-ops-puppet Puppet]<br />
* Fri 4:00 – 4:40 [https://etherpad.openstack.org/p/juno-summit-ops-networking Networking]<br />
* Fri 4:50 – 5:30 [https://etherpad.openstack.org/p/juno-summit-ops-monitoringlogging Monitoring and Logging]<br />
<br />
== Oslo ==<br />
* Wed 9:00 - 9:40 Release Plan for Low-level Libraries<br />
* Wed 9:50 - 10:30 Semantic versioning and oslo<br />
* Wed 11:00 - 11:40 oslo.rootwrap: performance and other improvements<br />
* Thu 9:00 - 9:40 Oslo Library Teams Breakout Session<br />
* Thu 9:50 - 10:30 Testing pre-releases of Oslo libs with apps<br />
* Thu 11:00 - 11:40 OpenStack cross service/project OpenStack profiler<br />
* Thu 15:10 - 16:00 Upstream chat with Mike Bayer<br />
* Thu 16:10 - 17:00 rpc proxy(oslo.messaging): https://etherpad.openstack.org/p/juno-summit-oslo-messaging-rpc-proxy<br />
* Fri 14:10 - 15:50 oslo.messaging status and plans for Juno<br />
* Fri 15:00 - 16:40 AMQP 1.0 protocol driver<br />
* Fri 16:00 - 16:40 PKI for messaging<br />
<br />
== QA ==<br />
<br />
===Wednesday===<br />
* 2:40 – 3:20 Branchless Tempest<br />
* 3:30 – 4:10 Tempest Documentation Gaps<br />
* 4:30 – 5:10 Functional API Testing - post dev QA vs TDD<br />
* 5:20 – 6:00 Rally and Tempest Integration<br />
<br />
===Thursday===<br />
* 1:30 – 2:10 [https://etherpad.openstack.org/p/juno-summit-api-tests-with-jsonschema API tests with JSONSchema]<br />
* 2:20 – 3:00 Negative Testing: Fuzzy Test Framework<br />
* 3:10 – 3:50 How to improve the UX of our Testing Tools<br />
* 4:10 – 4:50 Tempest, GUI, Client, Server<br />
<br />
===Friday===<br />
* 1:20 – 2:00 Grenade Current Status and Next Steps<br />
* 2:10– 2:50 [https://etherpad.openstack.org/p/juno-summit-qa-policy QA Program Policy and Changes in Juno]<br />
<br />
== Release Management ==<br />
== Sahara (ex. Savanna) ==<br />
<br />
* [http://junodesignsummit.sched.org/event/b4f52627efa42f285978d5af3643e189 Thu 13:30] [https://etherpad.openstack.org/p/juno-summit-sahara-relmngmt-backward Releasing and backward compatibility]<br />
* [http://junodesignsummit.sched.org/event/c8774beefd9e9188a3e0729d2bd7131e Thu 14:20] [https://etherpad.openstack.org/p/juno-summit-sahara-testing-plugins CI/gating and plugin requirements]<br />
* [http://junodesignsummit.sched.org/event/10bc9a23eb43eb9df885586035fb2491 Thu 15:10] [https://etherpad.openstack.org/p/juno-summit-sahara-scale-integration Scalable Sahara and further OpenStack integration]<br />
* [http://junodesignsummit.sched.org/event/be842178a085fe95b7665a653f8ab541 Thu 16:10] [https://etherpad.openstack.org/p/juno-summit-sahara-ux UX improvements]<br />
* [http://junodesignsummit.sched.org/event/dfa603324c0bbf29c2f09a77efb82d1d Thu 17:00] [https://etherpad.openstack.org/p/juno-summit-sahara-edp Future of EDP: plugins, SPI, Oozie]<br />
* [http://junodesignsummit.sched.org/event/a64f771cf28ed3ad637730db828668ff Fri 09:00] [https://etherpad.openstack.org/p/juno-summit-sahara-v2-api Next major REST API - v2]<br />
* [http://junodesignsummit.sched.org/event/49089a1d9c8203c6a4c1f0001fa417af Fri 09:50] [https://etherpad.openstack.org/p/juno-summit-sahara-roadmap-retro Sahara in Icehouse and Juno]<br />
<br />
== Swift ==<br />
== TripleO (Deployment) ==<br />
* Fri 11:40 - 12:20 [https://etherpad.openstack.org/p/juno-summit-tripleo-tuskar-planning TripleO Tuskar Planning]<br />
* Fri<br />
* Fri 14:10 - 14:50 [https://etherpad.openstack.org/p/juno-summit-tripleo-and-docker TripleO and Docker]<br />
* Fri 15:00 - 15:40 [https://etherpad.openstack.org/p/juno-summit-tripleo-ci TripleO CI]<br />
* Fri 16:00 - 16:40 [https://etherpad.openstack.org/p/juno-summit-tripleo-neutron TripleO and Neutron]<br />
* Fri 16:50 - 17:30 [https://etherpad.openstack.org/p/juno-summit-tripleo-devops TripleO Dev/Ops Session]<br />
<br />
== Trove ==<br />
== User Committee ==</div>Liz Blanchardhttps://wiki.openstack.org/w/index.php?title=UX&diff=44147UX2014-03-04T18:37:37Z<p>Liz Blanchard: /* Getting Started with Designing for User Experience */</p>
<hr />
<div>== OpenStack User Experience ==<br />
<br />
<p>'''Mission Statement:''' Enable OpenStack users to be efficient and make their experience consistent and pleasurable.</p><br />
<br />
User Experience (UX) is community-oriented and available for different audiences on several websites. This wiki serves as an informational source for UX-related activities (workstreams) that goes across multiple OpenStack projects.<br />
<br />
=== UX Workstreams ===<br />
[http://ask-openstackux.rhcloud.com UX Discussion Forum (new, temporary address)] <br/><br />
[https://wiki.openstack.org/wiki/Personas OpenStack Personas Working Group] <br/><br />
[https://wiki.openstack.org/wiki/HorizonUsability_Testing Usability Testing] <br/><br />
[https://launchpad.net/openstack-ux Features, Bugs, and Releases in Launchpad] <br/><br />
[https://wiki.openstack.org/wiki/UX/ProgramProposal OpenStack UX Program Proposal] <br/><br />
IRC: #openstack-ux (at FreeNode) <br/><br />
<br />
===Getting Started with Designing for User Experience===<br />
<br />
<b>How do I get involved with OpenStack UX and work on blueprints?</b><br/><br />
We track the work that we are doing on our launchpad site[https://launchpad.net/openstack-ux]. If you aren't ready to contribute your own designs, start off by giving others feedback on launchpad or on AskOpenStack UX[http://ask-openstackux.rhcloud.com/questions/].<br />
<br/><br/><br />
<b>What's a blueprint in Launchpad?</b><br/><br />
It's a specification for a feature in OpenStack. In UX, this usually is presented as wireframes or prototypes, but it can be something else. There's lots more info on openstack.org[https://wiki.openstack.org/wiki/Blueprints].<br />
<br/><br/><br />
<b>How does this whole OpenStack contributor thing work anyway?</b><br/><br />
There is great getting started documentation on openstack.org. How to Contribute[https://wiki.openstack.org/wiki/How_To_Contribute] is a good place to start.<br />
<br/><br/><br />
<b>What is the process for getting a new design into Horizon?</b><br/><br />
Assign yourself a blueprint and get to work! When you have something, post a link to your design docs on AskOpenStack UX[http://ask-openstackux.rhcloud.com/questions/] and ask for feedback. There'll be the usual revisions. Designs that are ready to go can be added to a new or existing blueprint on the Horizon project site[https://launchpad.net/horizon]. Then, wait for a dev to implement your design. You will be expected to work with developers to answer questions or make updates to your design along the way.<br />
<br/><br/><br />
<b>That's a pretty vague process. Can't you give me a little more detail than that?</b><br/><br />
Nope, not yet. We're new to this so the process is pretty ad hoc. We'd love your help making it better! Make suggestions.<br />
<br/><br/><br />
<b>I don't see a blueprint for the work I want to do. What can I do? </b><br/><br />
Create a new blueprint! Here is a great guide on creating blueprints[https://wiki.openstack.org/wiki/Blueprints#Creation].<br />
<br/><br/><br />
<b>Is there any user research I can leverage?</b><br/><br />
Yes! Check out this group that is working on personas and usability[https://wiki.openstack.org/wiki/Personas]. Also, if you are going to do your own research, we'd love for you to contribute results or better yet, to collaborate with you.<br />
<br/><br/><br />
<b>Where can I ask questions or get feedback on my designs?</b><br/><br />
AskUX, Horizon weekly meeting[https://wiki.openstack.org/wiki/Meetings#Horizon_team_meeting], #openstack-ux on Freenode.<br />
<br/><br/><br />
<b>Where can I ask questions about technical feasibility or understanding the problem space?</b><br/><br />
AskUX, Horizon weekly meetings, Horizon Launchpad, openstack-dev@lists.openstack.org, #openstack-horizon on Freenode.<br />
<br />
=== UX Archive ===<br />
[https://plus.google.com/u/0/communities/100954512393463248122 Community Sites (old, in transition)]<br />
</p></div>Liz Blanchardhttps://wiki.openstack.org/w/index.php?title=UX&diff=44146UX2014-03-04T18:34:59Z<p>Liz Blanchard: </p>
<hr />
<div>== OpenStack User Experience ==<br />
<br />
<p>'''Mission Statement:''' Enable OpenStack users to be efficient and make their experience consistent and pleasurable.</p><br />
<br />
User Experience (UX) is community-oriented and available for different audiences on several websites. This wiki serves as an informational source for UX-related activities (workstreams) that goes across multiple OpenStack projects.<br />
<br />
=== UX Workstreams ===<br />
[http://ask-openstackux.rhcloud.com UX Discussion Forum (new, temporary address)] <br/><br />
[https://wiki.openstack.org/wiki/Personas OpenStack Personas Working Group] <br/><br />
[https://wiki.openstack.org/wiki/HorizonUsability_Testing Usability Testing] <br/><br />
[https://launchpad.net/openstack-ux Features, Bugs, and Releases in Launchpad] <br/><br />
[https://wiki.openstack.org/wiki/UX/ProgramProposal OpenStack UX Program Proposal] <br/><br />
IRC: #openstack-ux (at FreeNode) <br/><br />
<br />
===Getting Started with Designing for User Experience===<br />
<br />
How do I get involved with OpenStack UX and work on blueprints?<br />
We track the work that we are doing on our launchpad site[https://launchpad.net/openstack-ux]. If you aren't ready to contribute your own designs, start off by giving others feedback on launchpad or on AskOpenStack UX[http://ask-openstackux.rhcloud.com/questions/].<br />
<br />
What's a blueprint in Launchpad?<br />
It's a specification for a feature in OpenStack. In UX, this usually is presented as wireframes or prototypes, but it can be something else. There's lots more info on openstack.org[https://wiki.openstack.org/wiki/Blueprints].<br />
<br />
How does this whole OpenStack contributor thing work anyway?<br />
There is great getting started documentation on openstack.org. How to Contribute[https://wiki.openstack.org/wiki/How_To_Contribute] is a good place to start.<br />
<br />
What is the process for getting a new design into Horizon?<br />
Assign yourself a blueprint and get to work! When you have something, post a link to your design docs on AskOpenStack UX[http://ask-openstackux.rhcloud.com/questions/] and ask for feedback. There'll be the usual revisions. Designs that are ready to go can be added to a new or existing blueprint on the Horizon project site[https://launchpad.net/horizon]. Then, wait for a dev to implement your design. You will be expected to work with developers to answer questions or make updates to your design along the way.<br />
<br />
That's a pretty vague process. Can't you give me a little more detail than that?<br />
Nope, not yet. We're new to this so the process is pretty ad hoc. We'd love your help making it better! Make suggestions.<br />
<br />
I don't see a blueprint for the work I want to do. What can I do? <br />
Create a new blueprint! Here is a great guide on creating blueprints[https://wiki.openstack.org/wiki/Blueprints#Creation].<br />
<br />
Is there any user research I can leverage?<br />
Yes! Check out this group that is working on personas and usability[https://wiki.openstack.org/wiki/Personas]. Also, if you are going to do your own research, we'd love for you to contribute results or better yet, to collaborate with you.<br />
<br />
Where can I ask questions or get feedback on my designs?<br />
AskUX, Horizon weekly meeting[https://wiki.openstack.org/wiki/Meetings#Horizon_team_meeting], #openstack-ux on Freenode.<br />
<br />
Where can I ask questions about technical feasibility or understanding the problem space?<br />
AskUX, Horizon weekly meetings, Horizon Launchpad, openstack-dev@lists.openstack.org, #openstack-horizon on Freenode.<br />
<br />
=== UX Archive ===<br />
[https://plus.google.com/u/0/communities/100954512393463248122 Community Sites (old, in transition)]<br />
</p></div>Liz Blanchardhttps://wiki.openstack.org/w/index.php?title=PersonaSurvey&diff=42305PersonaSurvey2014-02-14T15:46:12Z<p>Liz Blanchard: </p>
<hr />
<div>== Personas Survey ==<br />
<br />
The following is the proposed screener for usability:<br />
<br />
1. For this study, we need to speak to IT professionals whose primary job responsibility is designing and/or integrating infrastructure solutions into your datacenter, and the management of both virtual and physical servers within your datacenter. Which person in your organization best fits that description? <br />
A. No one………terminate<br />
B. No one, but I know someone at another company who does……… Ask for referral and then thank and terminate <br />
C. Myself………….Continue<br />
D. Myself and someone else ……… Ask for referral (record for later use) and then thank and continue<br />
E. Not myself, but someone else ………Ask for referral and then thank and terminate<br />
<br />
2. Do you work for any of the following companies?<br />
A. Dell<br />
B. HP<br />
C. Citrix<br />
D. VMWare<br />
E. Microsoft<br />
F. RackSpace<br />
G. IBM<br />
H. RightScale<br />
I. Oracle<br />
Recruiter – If the participant works for any of the companies listed above, thank and terminate<br />
<br />
5. Do your PRIMARY job responsibilities include any of the following? <br />
A. Server provisioning<br />
B. Ongoing server management<br />
C. Infrastructure configuration planning (e.g. Planning for how the servers, storage and networks tie together to meet the needs of the line of business end users)<br />
D. Managing physical and/or virtual machines <br />
Recruiter – Participants must select at least 1 in order to qualify<br />
<br />
6. Please list the cloud service providers and technology that you have good working knowledge of, that is, those that you can provide a description of and would be knowledgeable enough to answer questions about for a technically proficient audience.<br />
Recruiter – Pleas do not read list. Have participant generate the responses themselves, and record all that they generate. <br />
Participants must be knowledgeable of at least 1 in order to qualify. Please make sure at least 4 of the respondents indicated Open Stack (B).<br />
A. AWS (EC2)<br />
B. OpenStack<br />
C. Microsoft Azure<br />
D. Google Cloud<br />
E. HP Cloud<br />
F. HP Matrix<br />
G. Nebula<br />
<br />
7. Which of the following SERVER administration tasks do you perform on a regular basis (1-2 per month of more (circle all that apply)? <br />
A. Deploy and install an OS using an automated deployment tool such as RDP<br />
B. Automated/scripted multi server deployment<br />
C. Managed storage devices as part of your role as a server admin (interacting with storage admins); requesting resources from storage admin, configuration, troubleshooting<br />
D. Managed networking devices; requesting resources from network admin, configuration, troubleshooting, etc.<br />
E. Creating and managing virtual servers (at least 6)<br />
F. Manage a cloud (Matrix, OpenStack, vCloud Director, etc.)<br />
Recruiter: Participants must have experience with at least 4 of the above, and please recruit 3 that include F amongst their answers. <br />
<br />
8. Which of the following SERVER administration tasks have you performed in the past week (circle all that apply)? <br />
A. Deploy and install an OS using an automated deployment tool such as RDP<br />
B. Automated/scripted multi server deployment<br />
C. Managed storage devices as part of your role as a server admin (interacting with storage admins); requesting resources from storage admin, configuration, troubleshooting<br />
D. Managed networking devices; requesting resources from network admin, configuration, troubleshooting, etc.<br />
E. Created a virtual machine<br />
F. Managed a cloud (Matrix, OpenStack, vCloud Director, etc.)<br />
Recruiter: Participants must have done at least 2 of the above in the past week. <br />
<br />
10-1. In your daily software use as an IT professional, what percent of your time do you use:<br />
A. GUI (Graphical User Interface)______________%<br />
B. CLI (Command Line Interface) /REST (Representational State Transfer)_________%<br />
C. Other_________________(record name and percentage)<br />
Recruiter: Please record percentage for each. Total should = 100%<br />
<br />
10-2. Do you currently work with, or are involved with the implementation of, any of the following at your company?<br />
A. Infrastructure provisioning <br />
B. Virtual machine creation<br />
C. IT test and development projects<br />
D. Management software deployment and configuration<br />
<br />
11. How many physical servers are located in the datacenter(s) where the systems that you are responsible are housed? <br />
A. Less than 50………Continue<br />
B. 50 – 100……………Continue<br />
C. 101-500………………..Continue<br />
D. More than 500…………..Continue <br />
Recruiter – Record exact number, and please try to recruit on the high end of the range if possible. No more than 2 with less than 50.<br />
<br />
12. How many virtual servers are there in your server environment? <br />
A. Less than 100……………….. Thank and terminate<br />
B. More than 100…………..Record exact number__________and Continue <br />
Recruiter – at least half the participants recruited should have over 100 virtual servers.<br />
<br />
13. Does your IT department currently offer cloud computing services at you company? <br />
1. No<br />
2. Yes<br />
<br />
14. What platform(s) are you using or considering using in order to provide cloud computing services?_____________ <br />
A. AWS (EC2)<br />
B. OpenStack<br />
C. Microsoft Azure<br />
D. Google Cloud<br />
E. HP Cloud<br />
F. Nebula<br />
Recruiter – For any selected, please ask participant if this is something they are considering using, or if it is something that they are currently using, and record this.<br />
<br />
<br />
<br />
15. Is your location considered corporate headquarters or is it a division or branch of a company with headquarters elsewhere? <br />
A. Headquarters…….Continue<br />
B. Branch............ Continue <br />
<br />
<br />
<br />
16. How many people work for your organization worldwide? Please take into account all branches and locations. <br />
Record exact number: _______ <br />
A. <50………….Continue<br />
B. 50-100………..Continue<br />
C. 100-500………….Continue <br />
D. 501-1000………..Continue<br />
E. 1001-5000…………Continue<br />
F. 5001-10,000…………..Continue<br />
G. > 10,000………….Continue <br />
NOTE: RECRUIT NO MORE THAN 2 RESPONDENTS FROM COMPANIES WITH FEWER THAN 50 EMPLOYEES <br />
<br />
<br />
<br />
17. What is the primary business or industry of your company? (READ LIST, and ACCEPT ONE RESPONSE.) <br />
NOTE: Recruit a variety.<br />
1. Aerospace<br />
2. Internet Service Provider<br />
3. Engineering, architecture, R&D<br />
4. Education or non-profit<br />
5. Finance, banking, accounting, insurance, or real estate<br />
6. Healthcare or medical<br />
7. IT Consulting<br />
8. Legal<br />
9. Manufacturing<br />
10. Retailer, distributor, or wholesaler<br />
11. Reseller<br />
12. Transportation, utilities, or communication<br />
13. Oil and Gas (please specify)_______________________________<br />
14. Other: (please specify) __________________________ <br />
Please recruit a range. No more than 3 participants from the same industry should comprise the sample.<br />
<br />
<br />
<br />
18. How many physical servers are you personally responsible for? <br />
Please record response_______________ <br />
<br />
<br />
<br />
19. How many virtual servers are you personally responsible for? <br />
Please record response_______________ <br />
<br />
<br />
<br />
<br />
<br />
<br />
21. What is your primary job role?<br />
A. Server/system administration<br />
B. Network administration<br />
C. Capacity Planning<br />
D. System, Network Architect or Infrastructure Architect<br />
E. Application manager………..thank and terminiate<br />
F. Other (record response here__________________) <br />
<br />
24. How many years have you performed system administration and/or network management/administration?<br />
A. Less than 2 years……….thank and terminate<br />
B. 2 - 5 years....... (No more than 4)<br />
D. 5 - 10 years..... ..Continue<br />
E. More than 10 years……….Continue<br />
*Recruiter – Please recruit a range <br />
<br />
25. Who owns the servers in your company? <br />
A. centrally owned by IT<br />
B. owned by the business units<br />
C. other (define & submit response to HFE____________)<br />
D. I don’t know. <br />
<br />
26. What is your job title?______________________________________ <br />
<br />
27. What is the name of the department you work in?________________________<br />
Recruiter – please note, we are looking for individuals who are part of the IT department. If not, they will need to be screened by the HFE before scheduling. <br />
<br />
28. What is the job title of your direct supervisor?____________________________ <br />
<br />
29. What is the name of the company you work for?_________________________<br />
Recruiter – please recruit no more than one participant from a single company. <br />
DO not recruit participants who work for Cisco, VMWare, Microsoft, Citrix, Oracle, Sun, Dell, HP, or IBM – no computer HW or software virtualization vendors (this will need to be listed out). <br />
<br />
30. What is your age?<br />
A. 21-30<br />
B. 31-40<br />
C. 41-50<br />
D. 51-60<br />
E. 61+<br />
<br />
<br />
<br />
31. Do you have any kind of color vision impairment (this will not disqualify you from participating in the study)?<br />
A. Yes………please explain_________<br />
B. No<br />
<br />
<br />
<br />
32. How would you like to receive a reminder of your session time and date? <br />
a. Email – ask participant for email address and record it__________________<br />
b. Phone call – ask participant for phone number and record it____________________________ <br />
Participants should receive a reminder email or phone call one week before and again one day before their session.<br />
Recruiter – please remind participants to bring a valid ID, and their reading glasses should they need them.<br />
<br />
<br />
Return to [https://wiki.openstack.org/wiki/Personas Personas Wiki]</div>Liz Blanchardhttps://wiki.openstack.org/w/index.php?title=PersonaSurvey&diff=42303PersonaSurvey2014-02-14T15:45:34Z<p>Liz Blanchard: /* Personas Survey */</p>
<hr />
<div>== Personas Survey ==<br />
<br />
The following is the proposed screener for usability:<br />
<br />
1. For this study, we need to speak to IT professionals whose primary job responsibility is designing and/or integrating infrastructure solutions into your datacenter, and the management of both virtual and physical servers within your datacenter. Which person in your organization best fits that description? <br />
A. No one………terminate<br />
B. No one, but I know someone at another company who does……… Ask for referral and then thank and terminate <br />
C. Myself………….Continue<br />
D. Myself and someone else ……… Ask for referral (record for later use) and then thank and continue<br />
E. Not myself, but someone else ………Ask for referral and then thank and terminate<br />
<br />
2. Do you work for any of the following companies?<br />
A. Dell<br />
B. HP<br />
C. Citrix<br />
D. VMWare<br />
E. Microsoft<br />
F. RackSpace<br />
G. IBM<br />
H. RightScale<br />
I. Oracle<br />
Recruiter – If the participant works for any of the companies listed above, thank and terminate<br />
<br />
5. Do your PRIMARY job responsibilities include any of the following? <br />
A. Server provisioning<br />
B. Ongoing server management<br />
C. Infrastructure configuration planning (e.g. Planning for how the servers, storage and networks tie together to meet the needs of the line of business end users)<br />
D. Managing physical and/or virtual machines <br />
Recruiter – Participants must select at least 1 in order to qualify<br />
<br />
6. Please list the cloud service providers and technology that you have good working knowledge of, that is, those that you can provide a description of and would be knowledgeable enough to answer questions about for a technically proficient audience.<br />
Recruiter – Pleas do not read list. Have participant generate the responses themselves, and record all that they generate. <br />
Participants must be knowledgeable of at least 1 in order to qualify. Please make sure at least 4 of the respondents indicated Open Stack (B).<br />
A. AWS (EC2)<br />
B. OpenStack<br />
C. Microsoft Azure<br />
D. Google Cloud<br />
E. HP Cloud<br />
F. HP Matrix<br />
G. Nebula<br />
<br />
7. Which of the following SERVER administration tasks do you perform on a regular basis (1-2 per month of more (circle all that apply)? <br />
A. Deploy and install an OS using an automated deployment tool such as RDP<br />
B. Automated/scripted multi server deployment<br />
C. Managed storage devices as part of your role as a server admin (interacting with storage admins); requesting resources from storage admin, configuration, troubleshooting<br />
D. Managed networking devices; requesting resources from network admin, configuration, troubleshooting, etc.<br />
E. Creating and managing virtual servers (at least 6)<br />
F. Manage a cloud (Matrix, OpenStack, vCloud Director, etc.)<br />
Recruiter: Participants must have experience with at least 4 of the above, and please recruit 3 that include F amongst their answers. <br />
<br />
8. Which of the following SERVER administration tasks have you performed in the past week (circle all that apply)? <br />
A. Deploy and install an OS using an automated deployment tool such as RDP<br />
B. Automated/scripted multi server deployment<br />
C. Managed storage devices as part of your role as a server admin (interacting with storage admins); requesting resources from storage admin, configuration, troubleshooting<br />
D. Managed networking devices; requesting resources from network admin, configuration, troubleshooting, etc.<br />
E. Created a virtual machine<br />
F. Managed a cloud (Matrix, OpenStack, vCloud Director, etc.)<br />
Recruiter: Participants must have done at least 2 of the above in the past week. <br />
<br />
10-1. In your daily software use as an IT professional, what percent of your time do you use:<br />
A. GUI (Graphical User Interface)______________%<br />
B. CLI (Command Line Interface) /REST (Representational State Transfer)_________%<br />
C. Other_________________(record name and percentage)<br />
Recruiter: Please record percentage for each. Total should = 100%<br />
<br />
10-2. Do you currently work with, or are involved with the implementation of, any of the following at your company?<br />
A. Infrastructure provisioning <br />
B. Virtual machine creation<br />
C. IT test and development projects<br />
D. Management software deployment and configuration<br />
<br />
11. How many physical servers are located in the datacenter(s) where the systems that you are responsible are housed? <br />
A. Less than 50………Continue<br />
B. 50 – 100……………Continue<br />
C. 101-500………………..Continue<br />
D. More than 500…………..Continue <br />
Recruiter – Record exact number, and please try to recruit on the high end of the range if possible. No more than 2 with less than 50.<br />
<br />
12. How many virtual servers are there in your server environment? <br />
A. Less than 100……………….. Thank and terminate<br />
B. More than 100…………..Record exact number__________and Continue <br />
Recruiter – at least half the participants recruited should have over 100 virtual servers.<br />
<br />
13. Does your IT department currently offer cloud computing services at you company? <br />
1. No<br />
2. Yes<br />
<br />
14. What platform(s) are you using or considering using in order to provide cloud computing services?_____________ <br />
A. AWS (EC2)<br />
B. OpenStack<br />
C. Microsoft Azure<br />
D. Google Cloud<br />
E. HP Cloud<br />
F. Nebula<br />
Recruiter – For any selected, please ask participant if this is something they are considering using, or if it is something that they are currently using, and record this.<br />
<br />
<br />
<br />
15. Is your location considered corporate headquarters or is it a division or branch of a company with headquarters elsewhere? <br />
A. Headquarters…….Continue<br />
B. Branch............ Continue <br />
<br />
<br />
<br />
16. How many people work for your organization worldwide? Please take into account all branches and locations. <br />
Record exact number: _______ <br />
A. <50………….Continue<br />
B. 50-100………..Continue<br />
C. 100-500………….Continue <br />
D. 501-1000………..Continue<br />
E. 1001-5000…………Continue<br />
F. 5001-10,000…………..Continue<br />
G. > 10,000………….Continue <br />
NOTE: RECRUIT NO MORE THAN 2 RESPONDENTS FROM COMPANIES WITH FEWER THAN 50 EMPLOYEES <br />
<br />
<br />
<br />
17. What is the primary business or industry of your company? (READ LIST, and ACCEPT ONE RESPONSE.) <br />
NOTE: Recruit a variety.<br />
1. Aerospace<br />
2. Internet Service Provider<br />
3. Engineering, architecture, R&D<br />
4. Education or non-profit<br />
5. Finance, banking, accounting, insurance, or real estate<br />
6. Healthcare or medical<br />
7. IT Consulting<br />
8. Legal<br />
9. Manufacturing<br />
10. Retailer, distributor, or wholesaler<br />
11. Reseller<br />
12. Transportation, utilities, or communication<br />
13. Oil and Gas (please specify)_______________________________<br />
14. Other: (please specify) __________________________ <br />
Please recruit a range. No more than 3 participants from the same industry should comprise the sample.<br />
<br />
<br />
<br />
18. How many physical servers are you personally responsible for? <br />
Please record response_______________ <br />
<br />
<br />
<br />
19. How many virtual servers are you personally responsible for? <br />
Please record response_______________ <br />
<br />
<br />
<br />
<br />
<br />
<br />
21. What is your primary job role?<br />
A. Server/system administration<br />
B. Network administration<br />
C. Capacity Planning<br />
D. System, Network Architect or Infrastructure Architect<br />
E. Application manager………..thank and terminiate<br />
F. Other (record response here__________________) <br />
<br />
24. How many years have you performed system administration and/or network management/administration?<br />
A. Less than 2 years……….thank and terminate<br />
B. 2 - 5 years....... (No more than 4)<br />
D. 5 - 10 years..... ..Continue<br />
E. More than 10 years……….Continue<br />
*Recruiter – Please recruit a range <br />
<br />
25. Who owns the servers in your company? <br />
A. centrally owned by IT<br />
B. owned by the business units<br />
C. other (define & submit response to HFE____________)<br />
D. I don’t know. <br />
<br />
26. What is your job title?______________________________________ <br />
<br />
27. What is the name of the department you work in?________________________<br />
Recruiter – please note, we are looking for individuals who are part of the IT department. If not, they will need to be screened by the HFE before scheduling. <br />
<br />
28. What is the job title of your direct supervisor?____________________________ <br />
<br />
29. What is the name of the company you work for?_________________________<br />
Recruiter – please recruit no more than one participant from a single company. <br />
DO not recruit participants who work for Cisco, VMWare, Microsoft, Citrix, Oracle, Sun, Dell, HP, or IBM – no computer HW or software virtualization vendors (this will need to be listed out). <br />
<br />
30. What is your age?<br />
A. 21-30<br />
B. 31-40<br />
C. 41-50<br />
D. 51-60<br />
E. 61+<br />
<br />
<br />
<br />
31. Do you have any kind of color vision impairment (this will not disqualify you from participating in the study)?<br />
A. Yes………please explain_________<br />
B. No<br />
<br />
<br />
<br />
32. How would you like to receive a reminder of your session time and date? <br />
a. Email – ask participant for email address and record it__________________<br />
b. Phone call – ask participant for phone number and record it____________________________ <br />
Participants should receive a reminder email or phone call one week before and again one day before their session.<br />
<br />
Recruiter – please remind participants to bring a valid ID, and their reading glasses should they need them.<br />
<br />
<br />
Return to [https://wiki.openstack.org/wiki/Personas Personas Wiki]</div>Liz Blanchardhttps://wiki.openstack.org/w/index.php?title=PersonaSurvey&diff=42302PersonaSurvey2014-02-14T15:42:39Z<p>Liz Blanchard: /* Personas Survey */</p>
<hr />
<div>== Personas Survey ==<br />
<br />
The following is the proposed screener for usability:<br />
<br />
1. For this study, we need to speak to IT professionals whose primary job responsibility is designing and/or integrating infrastructure solutions into your datacenter, and the management of both virtual and physical servers within your datacenter. Which person in your organization best fits that description? <br />
A. No one………terminate<br />
B. No one, but I know someone at another company who does……… Ask for referral and then thank and terminate <br />
C. Myself………….Continue<br />
D. Myself and someone else ……… Ask for referral (record for later use) and then thank and continue<br />
E. Not myself, but someone else ………Ask for referral and then thank and terminate<br />
<br />
2. Do you work for any of the following companies?<br />
A. Dell<br />
B. HP<br />
C. Citrix<br />
D. VMWare<br />
E. Microsoft<br />
F. RackSpace<br />
G. IBM<br />
H. RightScale<br />
I. Oracle<br />
Recruiter – If the participant works for any of the companies listed above, thank and terminate<br />
<br />
5. Do your PRIMARY job responsibilities include any of the following? <br />
A. Server provisioning<br />
B. Ongoing server management<br />
C. Infrastructure configuration planning (e.g. Planning for how the servers, storage and networks tie together to meet the needs of the line of business end users)<br />
D. Managing physical and/or virtual machines <br />
Recruiter – Participants must select at least 1 in order to qualify<br />
<br />
6. Please list the cloud service providers and technology that you have good working knowledge of, that is, those that you can provide a description of and would be knowledgeable enough to answer questions about for a technically proficient audience.<br />
Recruiter – Pleas do not read list. Have participant generate the responses themselves, and record all that they generate. <br />
Participants must be knowledgeable of at least 1 in order to qualify. Please make sure at least 4 of the respondents indicated Open Stack (B).<br />
A. AWS (EC2)<br />
B. OpenStack<br />
C. Microsoft Azure<br />
D. Google Cloud<br />
E. HP Cloud<br />
F. HP Matrix<br />
G. Nebula<br />
<br />
7. Which of the following SERVER administration tasks do you perform on a regular basis (1-2 per month of more (circle all that apply)? <br />
A. Deploy and install an OS using an automated deployment tool such as RDP<br />
B. Automated/scripted multi server deployment<br />
C. Managed storage devices as part of your role as a server admin (interacting with storage admins); requesting resources from storage admin, configuration, troubleshooting<br />
D. Managed networking devices; requesting resources from network admin, configuration, troubleshooting, etc.<br />
E. Creating and managing virtual servers (at least 6)<br />
F. Manage a cloud (Matrix, OpenStack, vCloud Director, etc.)<br />
Recruiter: Participants must have experience with at least 4 of the above, and please recruit 3 that include F amongst their answers. <br />
<br />
8. Which of the following SERVER administration tasks have you performed in the past week (circle all that apply)? <br />
A. Deploy and install an OS using an automated deployment tool such as RDP<br />
B. Automated/scripted multi server deployment<br />
C. Managed storage devices as part of your role as a server admin (interacting with storage admins); requesting resources from storage admin, configuration, troubleshooting<br />
D. Managed networking devices; requesting resources from network admin, configuration, troubleshooting, etc.<br />
E. Created a virtual machine<br />
F. Managed a cloud (Matrix, OpenStack, vCloud Director, etc.)<br />
Recruiter: Participants must have done at least 2 of the above in the past week. <br />
<br />
10-1. In your daily software use as an IT professional, what percent of your time do you use:<br />
A. GUI (Graphical User Interface)______________%<br />
B. CLI (Command Line Interface) /REST (Representational State Transfer)_________%<br />
C. Other_________________(record name and percentage)<br />
Recruiter: Please record percentage for each. Total should = 100%<br />
<br />
10-2. Do you currently work with, or are involved with the implementation of, any of the following at your company?<br />
A. Infrastructure provisioning <br />
B. Virtual machine creation<br />
C. IT test and development projects<br />
D. Management software deployment and configuration<br />
<br />
11. How many physical servers are located in the datacenter(s) where the systems that you are responsible are housed? <br />
A. Less than 50………Continue<br />
B. 50 – 100……………Continue<br />
C. 101-500………………..Continue<br />
D. More than 500…………..Continue <br />
Recruiter – Record exact number, and please try to recruit on the high end of the range if possible. No more than 2 with less than 50.<br />
<br />
12. How many virtual servers are there in your server environment? <br />
A. Less than 100……………….. Thank and terminate<br />
B. More than 100…………..Record exact number__________and Continue <br />
Recruiter – at least half the participants recruited should have over 100 virtual servers.<br />
<br />
13. Does your IT department currently offer cloud computing services at you company? <br />
1. No<br />
2. Yes<br />
<br />
14. What platform(s) are you using or considering using in order to provide cloud computing services?_____________ <br />
A. AWS (EC2)<br />
B. OpenStack<br />
C. Microsoft Azure<br />
D. Google Cloud<br />
E. HP Cloud<br />
F. Nebula<br />
Recruiter – For any selected, please ask participant if this is something they are considering using, or if it is something that they are currently using, and record this.<br />
<br />
<br />
<br />
15. Is your location considered corporate headquarters or is it a division or branch of a company with headquarters elsewhere? <br />
A. Headquarters…….Continue<br />
B. Branch............ Continue <br />
<br />
<br />
<br />
16. How many people work for your organization worldwide? Please take into account all branches and locations. <br />
Record exact number: _______ <br />
A. <50………….Continue<br />
B. 50-100………..Continue<br />
C. 100-500………….Continue <br />
D. 501-1000………..Continue<br />
E. 1001-5000…………Continue<br />
F. 5001-10,000…………..Continue<br />
G. > 10,000………….Continue <br />
NOTE: RECRUIT NO MORE THAN 2 RESPONDENTS FROM COMPANIES WITH FEWER THAN 50 EMPLOYEES <br />
<br />
<br />
<br />
17. What is the primary business or industry of your company? (READ LIST, and ACCEPT ONE RESPONSE.) <br />
NOTE: Recruit a variety.<br />
1. Aerospace<br />
2. Internet Service Provider<br />
3. Engineering, architecture, R&D<br />
4. Education or non-profit<br />
5. Finance, banking, accounting, insurance, or real estate<br />
6. Healthcare or medical<br />
7. IT Consulting<br />
8. Legal<br />
9. Manufacturing<br />
10. Retailer, distributor, or wholesaler<br />
11. Reseller<br />
12. Transportation, utilities, or communication<br />
13. Oil and Gas (please specify)_______________________________<br />
14. Other: (please specify) __________________________ <br />
Please recruit a range. No more than 3 participants from the same industry should comprise the sample.<br />
<br />
<br />
<br />
18. How many physical servers are you personally responsible for? <br />
Please record response_______________ <br />
<br />
<br />
<br />
19. How many virtual servers are you personally responsible for? <br />
Please record response_______________ <br />
<br />
<br />
<br />
<br />
<br />
<br />
21. What is your primary job role?<br />
A. Server/system administration<br />
B. Network administration<br />
C. Capacity Planning<br />
D. System, Network Architect or Infrastructure Architect<br />
E. Application manager………..thank and terminiate<br />
F. Other (record response here__________________) <br />
<br />
24. How many years have you performed system administration and/or network management/administration?<br />
A. Less than 2 years……….thank and terminate<br />
B. 2 - 5 years....... (No more than 4)<br />
D. 5 - 10 years..... ..Continue<br />
E. More than 10 years……….Continue<br />
*Recruiter – Please recruit a range <br />
<br />
25. Who owns the servers in your company? <br />
A. centrally owned by IT<br />
B. owned by the business units<br />
C. other (define & submit response to HFE____________)<br />
D. I don’t know. <br />
<br />
26. What is your job title?______________________________________ <br />
<br />
27. What is the name of the department you work in?________________________<br />
Recruiter – please note, we are looking for individuals who are part of the IT department. If not, they will need to be screened by the HFE before scheduling. <br />
<br />
28. What is the job title of your direct supervisor?____________________________ <br />
<br />
29. What is the name of the company you work for?_________________________<br />
Recruiter – please recruit no more than one participant from a single company. <br />
DO not recruit participants who work for Cisco, VMWare, Microsoft, Citrix, Oracle, Sun, Dell, HP, or IBM – no computer HW or software virtualization vendors (this will need to be listed out). <br />
<br />
30. What is your age?<br />
A. 21-30<br />
B. 31-40<br />
C. 41-50<br />
D. 51-60<br />
E. 61+<br />
<br />
<br />
<br />
31. Do you have any kind of color vision impairment (this will not disqualify you from participating in the study)?<br />
A. Yes………please explain_________<br />
B. No<br />
<br />
<br />
<br />
32. How would you like to receive a reminder of your session time and date? <br />
a. Email – ask participant for email address and record it__________________<br />
b. Phone call – ask participant for phone number and record it____________________________ <br />
Participants should receive a reminder email or phone call one week before and again one day before their session.<br />
<br />
Recruiter – please remind participants to bring a valid ID, and their reading glasses should they need them.<br />
<br />
<br />
Return to [https://wiki.openstack.org/wiki/Personas Personas Wiki]</div>Liz Blanchardhttps://wiki.openstack.org/w/index.php?title=Meetings/Horizon&diff=38593Meetings/Horizon2013-12-17T21:31:04Z<p>Liz Blanchard: /* Agenda for next meeting (Dec 17) */</p>
<hr />
<div><br />
The [[OpenStack]] Horizon Team holds public meetings in #openstack-meeting. Everyone is encouraged to attend. <br />
* Tuesdays at [http://www.timeanddate.com/worldclock/fixedtime.html?hour=22&min=0&sec=0 22:00 UTC]<br />
<br />
== Apologies for absense ==<br />
<br />
<br />
== Agenda for next meeting (Dec 17) ==<br />
<br />
=== Meeting Time ===<br />
* As per the recent mailing list topic and previous discussions should we look to mix up the time for this meeting?<br />
<br />
=== Discuss integration of TripleO UI ===<br />
* Code Merge Plan<br />
* Core Merge Plan/Guidelines<br />
<br />
=== Persona Working Group Kick-Off Meeting Reminder ===<br />
* Tomorrow 2pm EST (1900 UTC)<br />
* Conference Telephone #<br />
* USA Toll #: 1-702-696-4520<br />
* USA Toll Free #: 1-866-409-2889<br />
* Conference Code (4351602479)<br />
* IRC: #openstack-ux<br />
* Etherpad: TBD (we'll provide the link in the IRC)<br />
<br />
== Previous meetings ==<br />
<br />
http://eavesdrop.openstack.org/meetings/horizon/</div>Liz Blanchardhttps://wiki.openstack.org/w/index.php?title=TripleO/Tuskar/IcehouseUserStories&diff=37677TripleO/Tuskar/IcehouseUserStories2013-12-09T15:43:28Z<p>Liz Blanchard: </p>
<hr />
<div>* As an infrastructure administrator, Anna wants to install the undercloud so she can use the UI.<br />
<br /><br />
<br />
* As an infrastructure administrator, Anna needs to deploy or update a set of resources that will run OpenStack (This isn't a very specific use case, but more of the larger end goal of Anna coming into the UI.)<br />
<br /><br />
<br />
* As an infrastructure administrator, Anna expects that the management node for the deployment services is already up and running and the status of this node is shown in the UI.<br />
<br /><br />
<br />
* As an infrastructure administrator, Anna wants to be able to quickly see the capacity that the nodes available to her deployment could sustain. She may want to drill in further to view a list of the unallocated nodes that she could use for her deployment of OpenStack. Ideally, she would not have to manually tell the system about these nodes. If she needs to manually register nodes for whatever reason, Anna would only want to have to define the essential data needed to register these nodes.<br />
<br /><br />
<br />
* As an infrastructure administrator, Anna needs confirm that the number of nodes being added to her deployment will allow for the necessary capacity requirements. She expects that the assigning of roles to each of the necessary nodes in her OpenStack deployment would be handled by the application, but in some cases she may need to perform this step manually. The nodes could be either controller, compute, networking, or storage resources depending on the needs of this deployment.<br />
<br /><br />
<br />
* As an infrastructure administrator, Anna wants to review the distribution of the nodes that she has assigned before kicking off the "Deploy" task. This would include the number of each type of node that would be deployed.<br />
<br /><br />
<br />
* As an infrastructure administrator, Anna wants to passively monitor the deployment process of all of the nodes that she has assigned through the UI. She expects that things will go well and will double check that this has happened after some time. She also expects to be notified right away if any errors have occurred.<br />
<br /><br />
<br />
* As an infrastructure administrator, Anna needs to be able to troubleshoot any errors that may occur during the deployment of nodes process through the UI.<br />
<br /><br />
<br />
* As an infrastructure administrator, Anna wants to monitor the availability and status of each node in her deployment.<br />
<br /><br />
<br />
* As an infrastructure administrator, Anna wants to be able to disabled or unallocate a node from a deployment if it is having maintenance performed or will no longer be needed in the cloud deployment.<br />
<br /><br />
<br />
* As an infrastructure administrator, Anna wants to be able to view the history of nodes that have been in a deployment. She may be interested in the historic trends and utilization of a node or be interested in bringing it back into the cloud deployment.<br />
<br /><br />
<br />
* As an infrastructure administrator, Anna needs to be notified of any important changes to nodes that are in the OpenStack deployment. This would include failures and information about any nodes that have broken certain thresholds that have been set up on metrics (e.g. CPU spikes over 80%). She does not want to be spammed with non-important notifications.</div>Liz Blanchardhttps://wiki.openstack.org/w/index.php?title=TripleO/Tuskar/IcehouseUserStories&diff=37676TripleO/Tuskar/IcehouseUserStories2013-12-09T15:37:18Z<p>Liz Blanchard: </p>
<hr />
<div>* As an infrastructure administrator, Anna wants to install the undercloud so she can use the UI.<br />
<br /><br />
<br />
* As an infrastructure administrator, Anna needs to deploy or update a set of resources that will run OpenStack (This isn't a very specific use case, but more of the larger end goal of Anna coming into the UI.)<br />
<br /><br />
<br />
* As an infrastructure administrator, Anna expects that the management node for the deployment services is already up and running and the status of this node is shown in the UI.<br />
<br /><br />
<br />
* As an infrastructure administrator, Anna wants to be able to quickly see the set of unallocated nodes that she could use for her deployment of OpenStack. Ideally, she would not have to manually tell the system about these nodes. If she needs to manually register nodes for whatever reason, Anna would only want to have to define the essential data needed to register these nodes.<br />
<br /><br />
<br />
* As an infrastructure administrator, Anna needs confirm that the number of nodes being added to her deployment will allow for the necessary capacity requirements. She expects that the assigning of roles to each of the necessary nodes in her OpenStack deployment would be handled by the application, but in some cases she may need to perform this step manually. The nodes could be either controller, compute, networking, or storage resources depending on the needs of this deployment.<br />
<br /><br />
<br />
* As an infrastructure administrator, Anna wants to review the distribution of the nodes that she has assigned before kicking off the "Deploy" task.<br />
<br /><br />
<br />
* As an infrastructure administrator, Anna wants to passively monitor the deployment process of all of the nodes that she has assigned through the UI. She expects that things will go well and will double check that this has happened after some time. She also expects to be notified right away if any errors have occurred.<br />
<br /><br />
<br />
* As an infrastructure administrator, Anna needs to be able to troubleshoot any errors that may occur during the deployment of nodes process through the UI.<br />
<br /><br />
<br />
* As an infrastructure administrator, Anna wants to monitor the availability and status of each node in her deployment.<br />
<br /><br />
<br />
* As an infrastructure administrator, Anna wants to be able to disabled or unallocate a node from a deployment if it is having maintenance performed or will no longer be needed in the cloud deployment.<br />
<br /><br />
<br />
* As an infrastructure administrator, Anna wants to be able to view the history of nodes that have been in a deployment. She may be interested in the historic trends and utilization of a node or be interested in bringing it back into the cloud deployment.<br />
<br /><br />
<br />
* As an infrastructure administrator, Anna needs to be notified of any important changes to nodes that are in the OpenStack deployment. She does not want to be spammed with non-important notifications.</div>Liz Blanchardhttps://wiki.openstack.org/w/index.php?title=TripleO/Tuskar/IcehouseUserStories&diff=37675TripleO/Tuskar/IcehouseUserStories2013-12-09T15:36:11Z<p>Liz Blanchard: </p>
<hr />
<div>* As an infrastructure administrator, Anna wants to install the undercloud so she can use the UI.<br />
<br /><br />
<br />
* As an infrastructure administrator, Anna needs to deploy or update a set of resources that will run OpenStack (This isn't a very specific use case, but more of the larger end goal of Anna coming into the UI.)<br /><br />
<br />
* As an infrastructure administrator, Anna expects that the management node for the deployment services is already up and running and the status of this node is shown in the UI.<br /><br />
<br />
<br />
* As an infrastructure administrator, Anna wants to be able to quickly see the set of unallocated nodes that she could use for her deployment of OpenStack. Ideally, she would not have to manually tell the system about these nodes. If she needs to manually register nodes for whatever reason, Anna would only want to have to define the essential data needed to register these nodes.<br />
<br />
* As an infrastructure administrator, Anna needs confirm that the number of nodes being added to her deployment will allow for the necessary capacity requirements. She expects that the assigning of roles to each of the necessary nodes in her OpenStack deployment would be handled by the application, but in some cases she may need to perform this step manually. The nodes could be either controller, compute, networking, or storage resources depending on the needs of this deployment.<br />
<br />
* As an infrastructure administrator, Anna wants to review the distribution of the nodes that she has assigned before kicking off the "Deploy" task.<br />
<br />
* As an infrastructure administrator, Anna wants to passively monitor the deployment process of all of the nodes that she has assigned through the UI. She expects that things will go well and will double check that this has happened after some time. She also expects to be notified right away if any errors have occurred.<br />
<br />
* As an infrastructure administrator, Anna needs to be able to troubleshoot any errors that may occur during the deployment of nodes process through the UI.<br />
<br />
* As an infrastructure administrator, Anna wants to monitor the availability and status of each node in her deployment.<br />
<br />
* As an infrastructure administrator, Anna wants to be able to disabled or unallocate a node from a deployment if it is having maintenance performed or will no longer be needed in the cloud deployment.<br />
<br />
* As an infrastructure administrator, Anna wants to be able to view the history of nodes that have been in a deployment. She may be interested in the historic trends and utilization of a node or be interested in bringing it back into the cloud deployment.<br />
<br />
* As an infrastructure administrator, Anna needs to be notified of any important changes to nodes that are in the OpenStack deployment. She does not want to be spammed with non-important notifications.</div>Liz Blanchardhttps://wiki.openstack.org/w/index.php?title=TripleO/Tuskar/IcehouseUserStories&diff=37674TripleO/Tuskar/IcehouseUserStories2013-12-09T15:35:47Z<p>Liz Blanchard: </p>
<hr />
<div>* As an infrastructure administrator, Anna wants to install the undercloud so she can use the UI.<br /><br />
<br />
* As an infrastructure administrator, Anna needs to deploy or update a set of resources that will run OpenStack (This isn't a very specific use case, but more of the larger end goal of Anna coming into the UI.)<br /><br />
<br />
* As an infrastructure administrator, Anna expects that the management node for the deployment services is already up and running and the status of this node is shown in the UI.<br /><br />
<br />
<br />
* As an infrastructure administrator, Anna wants to be able to quickly see the set of unallocated nodes that she could use for her deployment of OpenStack. Ideally, she would not have to manually tell the system about these nodes. If she needs to manually register nodes for whatever reason, Anna would only want to have to define the essential data needed to register these nodes.<br />
<br />
* As an infrastructure administrator, Anna needs confirm that the number of nodes being added to her deployment will allow for the necessary capacity requirements. She expects that the assigning of roles to each of the necessary nodes in her OpenStack deployment would be handled by the application, but in some cases she may need to perform this step manually. The nodes could be either controller, compute, networking, or storage resources depending on the needs of this deployment.<br />
<br />
* As an infrastructure administrator, Anna wants to review the distribution of the nodes that she has assigned before kicking off the "Deploy" task.<br />
<br />
* As an infrastructure administrator, Anna wants to passively monitor the deployment process of all of the nodes that she has assigned through the UI. She expects that things will go well and will double check that this has happened after some time. She also expects to be notified right away if any errors have occurred.<br />
<br />
* As an infrastructure administrator, Anna needs to be able to troubleshoot any errors that may occur during the deployment of nodes process through the UI.<br />
<br />
* As an infrastructure administrator, Anna wants to monitor the availability and status of each node in her deployment.<br />
<br />
* As an infrastructure administrator, Anna wants to be able to disabled or unallocate a node from a deployment if it is having maintenance performed or will no longer be needed in the cloud deployment.<br />
<br />
* As an infrastructure administrator, Anna wants to be able to view the history of nodes that have been in a deployment. She may be interested in the historic trends and utilization of a node or be interested in bringing it back into the cloud deployment.<br />
<br />
* As an infrastructure administrator, Anna needs to be notified of any important changes to nodes that are in the OpenStack deployment. She does not want to be spammed with non-important notifications.</div>Liz Blanchard