Revision as of 11:58, 10 August 2016

Weekly Trove Team Meeting

We have weekly team meetings on Wednesdays at 18:00 UTC in #openstack-meeting-alt

Want to add an agenda item? Please append your item to the upcoming weekly agenda while keeping in mind:

Guidelines for Writing Clear Agenda Items

An agenda item should have a clearly defined objective.

• [owner/author/interested-party] Good: Review #xxxxx has comments on foobar.py from multiple folks and there seems to be a lack of consensus on how to solve problem ‘y’. Let’s quickly rehash the merits of both approaches in 2-5 minutes and call for a vote. Goal: choose an approach and move forward on implementation.
• Bad: Discuss blueprint ‘xyz’
• Bad: Revisit blueprint ‘abc’ that we talked about last week to get answers on remaining disagreements.

When referring to previous conversations or competing viewpoints, be sure to summarize them.

Please make sure to include your own name in the first line of the agenda item, or the name of the person who will be presenting the subject/leading the discussion.

Trove Meeting, August 10

Action items from last week's meeting

[amrith] review what kind(s) of machines we get in the gate and see if we can get some more beefy horses ...

• Ongoing, we can adjust flavors in our test scripts
  

[amrith] from discussions at the mid-cycle

• What's the status of adding the additional scenario tests to the gate?
• What's the status of flipping the existing (mysql and redis) to voting in the gate?
• Is someone able to take a look at the python35 job and why it is failing?
• Any word on the tempest plugin issue (that johnma fixed)?

Trove pulse update

• Pulse Update
  

• Top 5 list
  

Reviews that can be merged

The following reviews are awaiting approval and I'd like to merge them by end of week if there are no further negative comments.

• 348088 Add "clean" command to redstack
• 345554 Remove discover from test-requirements
• 343827 Remove times.dbm file for each tox run
• 345655 MySQL do not retrieve Password in get user
• 345651 Define safe pid-file and socket paths in config
• 286317 Add log retrieval to Cassandra
• 343920 Use proper queries to update user properties
• 348087 Fix MySql replication start from incr backup

Reviews that will be abandoned

I plan to abandon the following reviews and unassign any bugs that are attached to them by end of the week if there are no updates.

• 237184 Fixes the cluster issues
• 271781 Implement Couchdb Configuration Groups Implements : blueprint couchdb-configu...
• 199635 Fixes the detection of user with extra access
• 295274 Separate trove image build project based on libguestfs tools
• 288297 fix delete backup tenant_id error
• 208670 Update Management Console user and password
• 215775 Add support for extended_properties on cluster-create
• 308126 Create default datastore options
• 349624 test review stable/Mitaka, DO NOT MERGE

Open Discussion

Meeting Agenda History
Meeting Chat Logs

Running The Meeting

• To start the meeting, use #startmeeting trove
• Then, publish the link to the agenda for the meeting (this page).
• Use #topic to mark each topic change.
• You can find the near-full list of Meetbot commands here. Instructions for voting (which can be useful for a quick show of hands) live here.
• During the meeting, don't forget to liberally use #info, #agreed, #action or #link to make sure the critical discussion points will be highlighted in the meeting log. Attendees can use these Meetbot keywords as well.
• To end the meeting, use #endmeeting