Difference between revisions of "Meetings/Performance"
< Meetings
(→Agenda for next meeting) |
Dina Belova (talk | contribs) (→Agenda for next meeting) |
||
Line 15: | Line 15: | ||
== Agenda for next meeting == | == Agenda for next meeting == | ||
− | [https://www.google.com/search?q=current+utc+time Tuesday, | + | [https://www.google.com/search?q=current+utc+time Tuesday, May 16th at 15:30 UTC] in <code>#openstack-performance</code> |
Please feel free to add items to the agenda below with your <code>name</code> or <code>irc_handle</code> and we'll cover them. | Please feel free to add items to the agenda below with your <code>name</code> or <code>irc_handle</code> and we'll cover them. | ||
Line 21: | Line 21: | ||
* Current progress on the planned tests | * Current progress on the planned tests | ||
* Open Discussion | * Open Discussion | ||
− | |||
− | |||
− | |||
− | |||
− | |||
* <please add your discussion points> | * <please add your discussion points> | ||
Revision as of 16:05, 25 April 2017
Contents
Weekly Performance Team Meeting
If you’re either running OpenStack clouds or developing and testing its components and you have seen performance issues on any scale, we meet every week to discuss these issues as well as more abstract items like what benchmarking tools need to become a standard, how to compare performance of different cloud deployments and so on.
Meeting Times
- On IRC in
#openstack-performance
, on Tuesday at 15:30 UTC.
Current Work Items
- Define what tools need to be used for benchmarking OpenStack performance
- Define what scenarios can verify cloud performance in the most unified way for all cloud deployments
- Share experience on what deployment patterns should be used for various workloads (eventually create document with recommendations)
Agenda for next meeting
Tuesday, May 16th at 15:30 UTC in #openstack-performance
Please feel free to add items to the agenda below with your name
or irc_handle
and we'll cover them.
- Action items
- Current progress on the planned tests
- Open Discussion
- <please add your discussion points>