Jump to: navigation, search

Difference between revisions of "Trove/MeetingAgendaHistory"

(Replaced content with "Historical meeting agendas are of limited value and meeting logs are available at [http://eavesdrop.openstack.org/meetings/trove/]")
 
(21 intermediate revisions by 2 users not shown)
Line 1: Line 1:
= Trove Weekly Meeting Agenda History (2016)  =
+
Historical meeting agendas are of limited value and meeting logs are available at [http://eavesdrop.openstack.org/meetings/trove/]
 
 
* [http://eavesdrop.openstack.org/meetings/trove/2016 2016 Chat History]
 
 
 
== No Trove meeting on May 4, 2016 ==
 
 
 
== No Trove meeting on April 27, 2016 ==
 
 
 
== Trove Meeting, April 20, 2016 ==
 
 
 
* Action items from last week's meeting
 
None
 
 
 
* Trove pulse update
 
** [http://bit.ly/1VQyg00 Pulse update]
 
** [https://gist.github.com/amrith/42a6772ff4ce22243381153596ef1a30 Top 5 list ]
 
 
 
* Announcements
 
** We won't have the IRC meeting next week as many of us will be at summit
 
 
 
* Proposal for review
 
 
 
* Ongoing review of projects. Any updates from project owners (list of Newton projects is below)
 
** [pmackinn] [https://review.openstack.org/#/c/295274/ Separate trove image build project based on libguestfs tools]
 
** [tellesnóbrega/vkmc] [https://review.openstack.org/#/c/256057/ Implementing CEPH as a backend for backups]
 
*** Has multiple -1's and appears to be in need of responses/updates
 
** [sonali/vkmc] [https://review.openstack.org/#/c/263980/ Configuration Groups for Couchdb]
 
*** spec fails the check and needs to be updated [vkmc?]
 
** [peterstac] [https://blueprints.launchpad.net/trove/+spec/replication-cluster-locality Locality for cluster/replication sets]
 
*** Code awaiting reviews [https://review.openstack.org/#/c/300669/], and [https://review.openstack.org/#/c/301936/]
 
** [petmal] [https://blueprints.launchpad.net/trove/+spec/couchbase-cluster-support Couchbase clusters]
 
*** Waiting for spec and code
 
** [vgnbkr] [https://review.openstack.org/#/c/302416/ Guest instance upgrade ]
 
*** Waiting for review comments
 
** [petmal] [https://blueprints.launchpad.net/trove/+spec/postgresql-incremental-backup PostgreSQL incremental backup/restore]
 
*** [https://review.openstack.org/#/c/259167/ Is this change set still the right one? ] It needs some TLC.
 
** [petmal] [https://blueprints.launchpad.net/trove/+spec/replication-affinity PostgreSQL replication]
 
*** [https://review.openstack.org/#/c/288712/ Is this change set still the right one? ] It needs some TLC.
 
** [mvandijk] [https://blueprints.launchpad.net/trove/+spec/associate-volume-type-datastore Associate volume-type with datastore]
 
*** Waiting for spec and code
 
** [vgnbkr] [https://review.openstack.org/#/c/294213/ Multi-Region Support]
 
*** Spec is currently WIP
 
** [amrith] [https://review.openstack.org/302952 extending trove to better utilize storage capabilities]
 
*** Looking for reviews
 
** [haypo] Python 3 support
 
*** Moving along well, change sets need reviews
 
 
 
 
 
* Work on branches other than master
 
** Bug fixes for [https://bugs.launchpad.net/trove/mitaka/+bugs Mitaka] and [https://bugs.launchpad.net/trove/liberty/+bugs Liberty]
 
 
 
 
 
* Summit planning
 
** Please update your etherpads
 
 
 
 
 
* Planning for mid-cycle
 
** Tentative date week of R-7, New York City
 
 
 
 
 
* Open Discussion
 
 
 
Meeting Notes: http://eavesdrop.openstack.org/meetings/trove/2016/trove.2016-04-20-18.01.txt
 
 
 
== Trove Meeting, April 13, 2016 ==
 
 
 
* Action items from last week's meeting
 
None
 
 
 
* Trove pulse update
 
** http://bit.ly/1VQyg00 [http://bit.ly/1VQyg00]
 
 
 
* Announcements
 
** python-troveclient v2.2.0 has been released and is now on pypi. For newton, g-r and u-c have been set to v2.2.0
 
 
 
* Proposal for review
 
** [amrith] Changes from the proposal bot (requirements, translations) can be approved on master by a single +2.
 
** [amrith] I propose that we approve [https://review.openstack.org/#/c/304030/ make python34 job gating]
 
 
 
* Clearing up the review backlog
 
** [amrith] the review backlog is building again, we need to pick up the pace on reviews
 
 
 
* Ongoing review of projects. Any updates from project owners (list of Newton projects is below)
 
** [pmackinn] [https://review.openstack.org/#/c/295274/ Separate trove image build project based on libguestfs tools]
 
** [tellesnóbrega/vkmc] [https://review.openstack.org/#/c/256057/ Implementing CEPH as a backend for backups]
 
** [sonali/vkmc] [https://review.openstack.org/#/c/263980/ Configuration Groups for Couchdb]
 
** [johnma] [https://review.openstack.org/#/c/255437/ Enable CouchDB replication in Trove]
 
** [peterstac] [https://blueprints.launchpad.net/trove/+spec/replication-cluster-locality Locality for cluster/replication sets]
 
** [petmal] [https://blueprints.launchpad.net/trove/+spec/couchbase-cluster-support Couchbase clusters]
 
** [vgnbkr] Guest instance upgrade - BP coming
 
** [petmal] [https://blueprints.launchpad.net/trove/+spec/postgresql-incremental-backup PostgreSQL incremental backup/restore]
 
** [petmal] [https://blueprints.launchpad.net/trove/+spec/replication-affinity PostgreSQL replication]
 
** [mvandijk] [https://blueprints.launchpad.net/trove/+spec/associate-volume-type-datastore Associate volume-type with datastore]
 
** [vgnbkr] [https://review.openstack.org/#/c/294213/ Multi-Region Support]
 
** [amrith] [https://review.openstack.org/302952 extending trove to better utilize storage capabilities]
 
** [haypo] Python 3 support
 
*** [https://blueprints.launchpad.net/trove/+spec/trove-python3 Blueprint]
 
*** [https://review.openstack.org/225912 Port run_tests.py to Python 3] Merged
 
*** [https://review.openstack.org/279098 Add a minimal py34 test environment] Merged
 
*** [https://review.openstack.org/300491 encrypt_data(): don't encode IV to base64] Merged
 
*** [https://review.openstack.org/279108 Add non-voting gate-trove-python34-db check] Merged
 
*** [https://review.openstack.org/279119 Port test_template unit test to Python 3]
 
*** [https://review.openstack.org/298952 Port more common unit tests to Python 3]
 
*** [https://review.openstack.org/297888 Port crypto_utils to Python 3]
 
 
 
 
 
* Summit planning
 
 
 
* Planning for mid-cycle
 
** Tentative date week of R-7, New York City
 
 
 
* Open Discussion
 
 
 
[http://eavesdrop.openstack.org/meetings/trove/2016/trove.2016-04-13-18.00.html Meeting Minutes]
 
 
 
 
 
== Trove Meeting, April 6, 2016 ==
 
 
 
* Action items from last week's meeting
 
** [cp16net] Confirm sending email to Horizon team re: RC2 [DONE]
 
** [amrith] Fill out the schedule for summit sessions [In Progress]
 
 
 
* Trove pulse update
 
** http://bit.ly/1VQyg00 [http://bit.ly/1VQyg00]
 
 
 
* Announcements
 
** We released Trove RC2 last week to address issues with Routes 3.2
 
 
 
* Ongoing review of projects. Any updates from project owners (list of Newton projects is below)
 
** [pmackinn] [https://review.openstack.org/#/c/295274/ Separate trove image build project based on libguestfs tools]
 
** [tellesnóbrega/vkmc] [https://review.openstack.org/#/c/256057/ Implementing CEPH as a backend for backups]
 
** [sonali/vkmc] [https://review.openstack.org/#/c/263980/ Configuration Groups for Couchdb]
 
** [johnma] [https://review.openstack.org/#/c/255437/ Enable CouchDB replication in Trove]
 
** [amrith] [https://review.openstack.org/#/c/256079/ Add support for hbase in Trove]
 
** [peterstac] [https://blueprints.launchpad.net/trove/+spec/replication-cluster-locality Locality for cluster/replication sets]
 
** [petmal] [https://blueprints.launchpad.net/trove/+spec/couchbase-cluster-support Couchbase clusters]
 
** [vgnbkr] Guest instance upgrade - BP coming
 
** [petmal] [https://blueprints.launchpad.net/trove/+spec/postgresql-incremental-backup PostgreSQL incremental backup/restore]
 
** [petmal] [https://blueprints.launchpad.net/trove/+spec/replication-affinity PostgreSQL replication]
 
** [mvandijk] [https://blueprints.launchpad.net/trove/+spec/associate-volume-type-datastore Associate volume-type with datastore]
 
** [vgnbkr] [https://review.openstack.org/#/c/294213/ Multi-Region Support]
 
** [haypo] Python 3 support
 
*** [https://blueprints.launchpad.net/trove/+spec/trove-python3 Blueprint]
 
*** [https://review.openstack.org/225912 Port run_tests.py to Python 3] Merged
 
*** [https://review.openstack.org/279098 Add a minimal py34 test environment] Merged
 
*** [https://review.openstack.org/300491 encrypt_data(): don't encode IV to base64] Merged
 
*** [https://review.openstack.org/279108 Add non-voting gate-trove-python34-db check] Merged
 
*** [https://review.openstack.org/279119 Port test_template unit test to Python 3]
 
*** [https://review.openstack.org/298952 Port more common unit tests to Python 3]
 
*** [https://review.openstack.org/297888 Port crypto_utils to Python 3]
 
 
 
 
 
* Summit planning
 
** [https://etherpad.openstack.org/p/trove-newton-proposed-sessions Propose sessions for the summit]
 
** [http://markmail.org/message/avbqqzwhog36tme2 Conference room allocations announced] (Trove: 3fb, 6wr, cm:half)
 
** [https://etherpad.openstack.org/p/trove-newton-summit-overview Session overview]
 
** [http://openstack.markmail.org/thread/yeg57r5yyddveoka Austin Design Summit track layout] The Trove sessions are as follows, please mark your calendars.
 
*** (WR1) Wednesday 0950 to 1030
 
*** (WR2) Wednesday 1350 to 1430
 
*** (WR3) Wednesday 1530 to 1610
 
*** (WR4) Thursday 1150 to 1230
 
*** (WR5) Thursday 1330 to 1410
 
*** (WR6) Thursday 1420 to 1500
 
*** (FB1) Wednesday 1720 to 1800
 
*** (FB2) Thursday 0950 to 1030
 
*** (FB3) Thursday 1100 to 1140
 
*** (CM) Friday 0900 to 1230.
 
 
 
* Planning for mid-cycle
 
** Tentative date week of R-7, New York City
 
 
 
* Open Discussion
 
 
 
Meeting Minutes [http://eavesdrop.openstack.org/meetings/trove/2016/trove.2016-04-06-18.00.html]
 
 
 
== Trove Meeting, March 30, 2016 ==
 
 
 
* Action items from last week's meeting
 
** [all] If you have a patch set that you intend to resume work on, please put an update in it to that effect so we don't go abandon it under you ...
 
** [all]  if any of the abandoned patches looks like something you would like to pick up feel free
 
** cp16net reply to trove-dashboard ML question for RC2
 
** [all] please review changes [ https://review.openstack.org/#/c/262289/], [ https://review.openstack.org/#/c/262287/], and link [ http://openstack.markmail.org/thread/jepcqu335mrb5c7l] in agenda and update the reviews
 
** flaper87 to WF+1 the patches in question [ https://review.openstack.org/#/c/262289/] and [ https://review.openstack.org/#/c/262287/] [DONE]
 
* Trove pulse update
 
** http://bit.ly/1VQyg00 [http://bit.ly/1VQyg00]
 
* Announcements
 
** [http://releases.openstack.org/newton/schedule.html Newton release schedule has been published ]
 
*** Some things I've learned from the Mitaka cycle
 
**** The schedule is known so far in advance that it is prudent to plan for it
 
**** The dates for things that are listed as "Final" are in fact final and not subject to FFE's
 
***** If we want to push any code into OSLO, R-6 is a hard deadline.
 
***** R-5, is the '''hard''' freeze for the python-troveclient. We '''must''' get all new functionality we need in the client into a version by that date or it won't be available for the release.
 
***** R-5 is the '''target date''' by which all new functionality should be in, you need to request FFE's for anything that does not merge by that date
 
***** R-3 is the RC1 '''target date''', not a hard date. In the Mitaka cycle, I mistakenly believed that R-3 is a hard RC1 date. My mistake.
 
** [https://review.openstack.org/#/c/164035/ Getting rid of eventlet and replacing it with something else]
 
 
 
* Ongoing review of projects. At the mid-cycle in Raleigh, one of the action items that we took away was that we should start tracking and monitoring all projects under way to completion through the release cycle. I'm going to start this up with the projects that we know are under way, and begin to highlight them so that people can focus time on reviewing them.
 
** [pmackinn] [https://review.openstack.org/#/c/295274/ Separate trove image build project based on libguestfs tools]
 
** [tellesnóbrega/vkmc] [https://review.openstack.org/#/c/256057/ Implementing CEPH as a backend for backups]
 
** [sonali/vkmc] [https://review.openstack.org/#/c/263980/ Configuration Groups for Couchdb]
 
** [johnma] [https://review.openstack.org/#/c/255437/ Enable CouchDB replication in Trove]
 
** [amrith] [https://review.openstack.org/#/c/256079/ Add support for hbase in Trove]
 
** [peterstac] [https://blueprints.launchpad.net/trove/+spec/replication-cluster-locality Locality for cluster/replication sets]
 
** [petmal] [https://blueprints.launchpad.net/trove/+spec/couchbase-cluster-support Couchbase clusters]
 
** [vgnbkr] Guest instance upgrade - BP coming
 
** [petmal] [https://blueprints.launchpad.net/trove/+spec/postgresql-incremental-backup PostgreSQL incremental backup/restore]
 
** [petmal] [https://blueprints.launchpad.net/trove/+spec/replication-affinity PostgreSQL replication]
 
** [mvandijk] [https://blueprints.launchpad.net/trove/+spec/associate-volume-type-datastore Associate volume-type with datastore]
 
** [vgnbkr] [https://review.openstack.org/#/c/294213/ Multi-Region Support]
 
* Summit planning
 
** [https://etherpad.openstack.org/p/trove-newton-proposed-sessions Propose sessions for the summit]
 
** [http://markmail.org/message/avbqqzwhog36tme2 Conference room allocations announced] (Trove: 3fb, 6wr, cm:half)
 
** [http://openstack.markmail.org/thread/yeg57r5yyddveoka Austin Design Summit track layout] The Trove sessions are as follows, please mark your calendars.
 
*** (WR1) Wednesday 0950 to 1030
 
*** (WR2) Wednesday 1350 to 1430
 
*** (WR3) Wednesday 1530 to 1610
 
*** (WR4) Thursday 1150 to 1230
 
*** (WR5) Thursday 1330 to 1410
 
*** (WR6) Thursday 1420 to 1500
 
*** (FB1) Wednesday 1720 to 1800
 
*** (FB2) Thursday 0950 to 1030
 
*** (FB3) Thursday 1100 to 1140
 
*** (CM) Friday 0900 to 1230.
 
* Planning for mid-cycle
 
** It seems like this is a long way off but it really isn't.
 
** I'd like to propose R-7, in the New York City area.
 
* Recent instability in the gate/check
 
* Open Discussion
 
 
 
* Meeting minutes at: http://eavesdrop.openstack.org/meetings/trove/2016/trove.2016-03-30-18.01.html
 
 
 
 
 
== Trove Meeting, March 23, 2016 ==
 
 
 
* Action items from last week's meeting
 
** [amrith] get more information about creating and distributing a trove wide dashboard
 
** [amrith] contact Victor Stinner re: python3 session at summit [DONE]
 
** [amrith] Add new projects discussion topic for summit agenda. [DONE]
 
** [pmackinn] I've tagged you on some topics based on mid-cycle, please confirm [DONE, during the meeting]
 
** [amrith] get leaders for all sessions that we want to actually conduct ;) [ONGOING]
 
* Trove pulse update
 
** http://bit.ly/1VQyg00 [http://bit.ly/1VQyg00]
 
* Announcements
 
** http://releases.openstack.org/mitaka/schedule.html
 
** Mitaka is now stable/mitaka, master is now heading to Newton
 
*** Please triage your bugs accordingly
 
*** Stable branch rules now in effect for stable/mitaka branches on trove, trove-dashboard, and python-troveclient
 
** Other announcements
 
* Health check on outstanding blueprints and features for Mitaka
 
** https://review.openstack.org/#/q/starredby:amrith+status:open [https://review.openstack.org/#/q/starredby:amrith+status:open]
 
* Do we '''really''' need these two fixes in stable/liberty:
 
** https://review.openstack.org/#/c/262289/ [https://review.openstack.org/#/c/262289/]
 
** https://review.openstack.org/#/c/262287/ [https://review.openstack.org/#/c/262287/]
 
** See mail thread [http://openstack.markmail.org/thread/jepcqu335mrb5c7l]
 
* Summit planning
 
** '''Propose sessions at https://etherpad.openstack.org/p/trove-newton-proposed-sessions [https://etherpad.openstack.org/p/trove-newton-proposed-sessions]'''
 
** Conference room allocations announced (Trove: 3fb, 6wr, cm:half) [http://markmail.org/message/avbqqzwhog36tme2]
 
* Using 'reno' for release notes
 
** Documentation at [http://docs.openstack.org/developer/reno/]
 
** When you check in new code, please also add a release note. That makes it easy when we are releasing new software. To add a release note, see: [http://docs.openstack.org/developer/reno/usage.html#creating-new-release-notes]
 
* [cp16net] trove dashboard update
 
** https://review.openstack.org/#/c/292451/
 
* Open Discussion
 
 
 
As the meeting bot died during the meeting, the transcript and summary of the meeting are posted at
 
 
 
https://gist.github.com/amrith/5ce3e4a0311f2cc4044c [https://gist.github.com/amrith/5ce3e4a0311f2cc4044c]
 
 
 
== Trove Meeting, March 16, 2016 ==
 
 
 
* Action items from last week's meeting
 
** [amrith] figure out who has to send FFE acceptances
 
* Trove pulse update
 
** http://bit.ly/1VQyg00 [http://bit.ly/1VQyg00]
 
* Announcements
 
** http://releases.openstack.org/mitaka/schedule.html
 
** [amrith] Cross project Quotas library/project
 
*** see [http://lists.openstack.org/pipermail/openstack-dev/2016-March/089453.html]
 
*** see [https://review.openstack.org/#/c/284454/]
 
** [amrith] Take a look at [https://review.openstack.org/#/c/292451/]
 
*** Was proposed by Flavio. I'm not sure it addresses the things that we've discussed in the past. But worth taking a look at and posting your thoughts on the things you'd like in the project-wide dashboard.
 
** Other announcements
 
* Health check on outstanding blueprints and features for Mitaka
 
** https://review.openstack.org/#/q/starredby:amrith+status:open [https://review.openstack.org/#/q/starredby:amrith+status:open]
 
** [amrith] The change(s) for module management [https://review.openstack.org/#/c/290177/] that went into python-troveclient will be in 2.2.0. But 2.2.0 won't be available in Mitaka as the request was after the hard freeze for the client. So we'll have to resubmit the request to tag 2.2.0 [https://review.openstack.org/#/c/292650/] against Newton and upper-constraints.txt [https://review.openstack.org/#/c/292652/1] will only be bumped for Newton. For Newton, let's remember that the client hard freeze is a hard freeze and is not extended by an FFE.
 
* Summit planning
 
** Propose sessions at https://etherpad.openstack.org/p/trove-newton-proposed-sessions [https://etherpad.openstack.org/p/trove-newton-proposed-sessions]
 
** Conference room allocations announced (Trove: 3fb, 6wr, cm:half) [http://markmail.org/message/avbqqzwhog36tme2]
 
* Open Discussion
 
 
 
* Meeting minutes at: http://eavesdrop.openstack.org/meetings/trove/2016/trove.2016-03-16-18.00.html
 
 
 
== Trove Meeting, March 9, 2016 ==
 
 
 
* [amrith] Trove pulse update
 
** http://bit.ly/1VQyg00
 
* Announcements
 
** [amrith] http://releases.openstack.org/mitaka/schedule.html
 
** Other announcements
 
* [amrith] Health check on outstanding blueprints and features for Mitaka
 
** https://launchpad.net/trove/+milestone/mitaka-3
 
** https://review.openstack.org/#/q/starredby:amrith+status:open
 
* [amrith] Summit planning
 
** Propose sessions at https://etherpad.openstack.org/p/trove-newton-proposed-sessions
 
* Open Discussion
 
 
 
* Meeting minutes at: http://eavesdrop.openstack.org/meetings/trove/2016/trove.2016-03-09-18.00.html
 
 
 
== Trove Meeting, March 2, 2016 ==
 
 
 
* [amrith] Trove pulse update
 
** http://bit.ly/1VQyg00
 
* Announcements
 
** [amrith] http://releases.openstack.org/mitaka/schedule.html
 
** Other announcements
 
* Health check on outstanding blueprints and features for Mitaka
 
** [amrith] https://launchpad.net/trove/+milestone/mitaka-3
 
* Feature Freeze Exceptions
 
** [amrith] The process for feature freeze exceptions is that by tomorrow (March 3rd) an email must be sent to the dev mailing list. If you have a BP/Project that will not merge before the m-3 deadline, we need to send out an email about an FFE. What is the list of FFE's that Trove requires for Mitaka? Typically the PTL would send this out so I'll work with Craig to get this sent out in time. I need the list.
 
* Open Discussion
 
 
 
== Trove Meeting, Feb 23, 2016 ==
 
 
 
* [cp16net] Trove pulse update
 
** http://bit.ly/1VQyg00
 
* Announcements
 
** http://lists.openstack.org/pipermail/openstack-dev/2016-February/086362.html
 
* Health check on outstanding blueprints and features for Mitaka
 
** https://launchpad.net/trove/+milestone/mitaka-3
 
* Open Discussion
 
** [abramley] Recently all of the trove horizon code was moved into a separate plugin - trove-dashboard. Who in the community is responsible for creating ubuntu, rhel etc packages for this trove-dashboard plugin and ensuring that it installs and plugs into horizon on the various platforms?
 
 
 
 
 
== Trove Meeting, Feb 17, 2016 ==
 
 
 
* [cp16net] Trove pulse update
 
** http://bit.ly/1VQyg00
 
* Announcements
 
** http://lists.openstack.org/pipermail/openstack-dev/2016-February/086362.html
 
* Health check on outstanding blueprints and features for Mitaka
 
** https://launchpad.net/trove/+milestone/mitaka-3
 
* [imandhan, johnma] Follow up discussion from midcycle on handling of users while performing db2 backup and restore. Associated Review [https://review.openstack.org/#/c/246709/ #246709]
 
* Open Discussion
 
 
 
== Trove Meeting, Feb 10, 2016 ==
 
* Meeting canceled because of the Trove Midcycle
 
 
 
== Trove Meeting, Feb 3, 2016 ==
 
* [cp16net] Trove pulse update
 
** http://bit.ly/1VQyg00
 
* Announcements
 
** Trove Mid Cycle Meetup (Feb 9-11) Next week!
 
*** https://wiki.openstack.org/wiki/Sprints/TroveMitakaSprint
 
*** https://etherpad.openstack.org/p/liberty-trove-midcycle
 
** Cancel next weeks meeting (Feb 10th)
 
** Release News
 
*** Mitaka-3 is (March 1-3)
 
**** http://docs.openstack.org/releases/schedules/mitaka.html
 
* Open Discussion
 
 
 
== Trove Meeting, Jan 27, 2016 ==
 
* [cp16net] Trove pulse update
 
** http://bit.ly/1VQyg00
 
* Announcements
 
** gate issues were resolved
 
** Trove Mid Cycle Meetup (Feb 9-11) 2 weeks away!
 
*** https://etherpad.openstack.org/p/mitaka-trove-midcycle-rsvp
 
*** https://wiki.openstack.org/wiki/Sprints/TroveMitakaSprint
 
** Release News
 
*** Mitaka-2 was released
 
**** http://docs.openstack.org/releases/releases/mitaka.html#mitaka-trove
 
*** Mitaka-3 is (March 1-3)
 
**** http://docs.openstack.org/releases/schedules/mitaka.html
 
* Open Discussion
 
 
 
== Trove Meeting, Jan 20, 2016 ==
 
* [cp16net] Trove pulse update
 
** http://bit.ly/1VQyg00
 
* Announcements
 
** Trove Mid Cycle Meetup (Feb 9-11)
 
*** https://etherpad.openstack.org/p/mitaka-trove-midcycle-rsvp
 
** Mitaka-2 Release
 
*** http://docs.openstack.org/releases/schedules/mitaka.html
 
* Python 3 support in Trove
 
** Several changes (5 in all) are now showing up for review as part of a project to include Python 3 support for Trove
 
*** https://review.openstack.org/#/q/topic:bp/trove-python3
 
** I also see this page which indicates that Trove is one of the few projects not ready with Python 3
 
*** https://wiki.openstack.org/wiki/Python3
 
** What is the intention relative to Python 3 in the Mitaka timeframe?
 
*** There has been no cross-project spec on this, and Python 3 was a stretch goal for Mitaka (per conversations in Tokyo).
 
*** Other projects have support for Python 3 but they aren't "done".
 
** Do we want it, these changes, and the voting CI in the Mitaka timeframe?
 
** Will a trove-specs spec be submitted? Is one needed or is this self-explanatory and one is not needed?
 
** I have asked the question in some of the reviews but got no answer so am asking it here at the trove meeting.
 
* Open Discussion
 
 
 
== Trove Meeting, Jan 13, 2016 ==
 
* [cp16net] Trove pulse update
 
** http://bit.ly/1VQyg00
 
* [peterstac] Use of TODO in the source code
 
** I've noticed that we have a tendency to use the *TODO* marker in the code to remind ourselves of things that need to be done (usually out of scope of the current changeset).  While this is admirable, I believe that entering a bug in launchpad is a better solution.  I'd like to see how others feel about this.
 
* [amrith] Recent "Spam of Patches"
 
** See ML: http://openstack.markmail.org/thread/yx6hgouzu5wzrf5m
 
** The term "Spam of Patches" is not something I came up with
 
** These patches are taking a lot of bandwidth, from reviews, from the gate, and for merges that we really want to land into Mitaka
 
** How do we want to handle these from now to Mitaka release date?
 
* [amrith] HBase (again)
 
** Last week, I posted a message to the ML as promised
 
** See http://openstack.markmail.org/thread/yx6hgouzu5wzrf5m
 
** Later reposted with [sahara] in subject, http://openstack.markmail.org/thread/x5uirwolkknlorr3
 
** As expected, the feedback from several was that we should consider sahara for hbase full distributed mode
 
** Which we plan to do, anyway. But that's not for this phase.
 
** This phase is only standalone and pseudo-distributed, both of which are single node.
 
* Open Discussion
 
 
 
== Trove Meeting, Jan 6, 2016 ==
 
* [cp16net] Trove pulse update
 
** http://bit.ly/1VQyg00
 
* trove-dashboard reporting bugs/bp
 
* Announcements
 
* Looking for comments (Trove meets HBase)
 
** https://review.openstack.org/#/c/256079/
 
** I am not looking for comments on the spec in the meeting. Rather there seems to be an issue about whether Trove should even go hear HBase or whether we should just say that's Sahara's turf. A question was raised in the spec review of whether this has been discussed on the ML. I'm happy to post the question on the ML but before I did that, I wanted to poll the team to see what people felt. It is my belief that HBase is a database and offering support for HBase through Trove, where Trove provisions and manages the instances independent of Sahara, is something of value. I realize that there are others who feel differently. The code is up there for review as well (see https://review.openstack.org/#/c/262048/ and https://review.openstack.org/#/c/262815).
 
* Open Discussion
 
 
 
= Trove Weekly Meeting Agenda History (2015)  =
 
== Agenda for Jan 28th ==
 
* Review #147908: Try to gain some consensus on how to resolve the issues itemized in final review comment.
 
 
 
== Agenda for Jan 21st ==
 
 
 
* Review #131610 : Security concerns, continued from the previous meeting + general review
 
 
 
== Agenda for Feb 4th ==
 
* Meeting canceled due to mid-cycle in Seattle
 
 
 
== Agenda for February 18 2015 ==
 
* Trove pulse update:
 
** https://etherpad.openstack.org/p/trove-pulse-update
 
* Trove related presentations/talks in the Liberty Summit -- Please Vote!
 
** https://etherpad.openstack.org/p/liberty-summit-trove-talks
 
* Trove Liberty Mid Cycle Sprint -- Initial planning
 
** http://doodle.com/candscrt36hg38a7
 
* Continue discussion of proposal to classify datastores and strategies
 
** https://review.openstack.org/#/c/154119/4
 
** Has been updated with more details and review comments thus far. I would like to request discussion and hopefully get a green-light to complete implementation.
 
 
 
== Agenda for February 25 2015 ==
 
 
 
* Trove pulse update:
 
** https://etherpad.openstack.org/p/trove-pulse-update
 
* [amrith] Need reviewers for 157140 [https://review.openstack.org/#/c/157140/]
 
** Would like to have people look at this and consider it for merging quickly as there are other patch sets that will be impacted by it, especially the one reorganizing the guestagent code, anything that wants to add a new datastore, etc.,
 
** There have been some comments (Simon, Ashleigh, Sushil) that I've tried to address in a reply but I would like some positive (or negative) reviews. Ok, I'd like some positive reviews ;)
 
* [doug] Discuss 147908 [https://review.openstack.org/#/c/147908/]
 
** There are a couple of options for how to proceed on this change and it would be good to get it into Kilo-3.
 
* [schang] Discuss 136918 [https://review.openstack.org/#/c/136918/]
 
** Discuss the comment thread at point #3 under the Guest Agent section.  Need to decide what to do with the common code.
 
* [amrith] Trove Liberty Mid Cycle Sprint -- Initial planning
 
** http://doodle.com/candscrt36hg38a7
 
** Am hoping we can nail down a date.
 
** Currently, week of August 24th is winning.
 
* [sushilkm] Needed reviewers for Vertica work
 
** Looking forward for people to look at the Vertica work, the spec, trove-integration and trove patches.
 
** The list of patchsets for the work is as follows:
 
# trove-specs: https://review.openstack.org/151126
 
# trove-integration: https://review.openstack.org/156149
 
# trove: https://review.openstack.org/156486
 
 
 
== Agenda for March 4 2015 ==
 
 
 
* Trove pulse update:
 
** https://etherpad.openstack.org/p/trove-pulse-update
 
* Feature proposal freeze at the end of this week.
 
** Currently open specs: https://review.openstack.org/#/q/status:open+project:openstack/trove-specs,n,z
 
* Feature request (vkmc)
 
** SSH keys injection on Trove instance creation. Has it been discussed before? Are there any cons for adding it?
 
* Review #131610 - Anna
 
 
 
== Trove Meeting, March 11, 2015 ==
 
 
 
* [SlickNik] Trove pulse update:
 
** https://etherpad.openstack.org/p/trove-pulse-update
 
* [SlickNik] Feature Freeze Next Week (March 19)
 
** Please prioritize reviews for BPs : https://launchpad.net/trove/+milestone/kilo-3
 
** https://etherpad.openstack.org/p/TroveKilo3Blueprints
 
* [amrith] Coming down the pike for Liberty
 
** oslo-config-generator, look at http://docs.openstack.org/developer/oslo.config/generator.html
 
** Heads-up, I'll be submitting BP's or changes for these as appropriate and arrange to have the code ready post Kilo freeze.
 
 
 
== Trove Meeting, March 18, 2015 ==
 
 
 
* [SlickNik] Trove pulse update:
 
** https://etherpad.openstack.org/p/trove-pulse-update
 
* [SlickNik] Openstack Feature Freeze this week for kilo-3:
 
** https://launchpad.net/trove/+milestone/kilo-3
 
** https://etherpad.openstack.org/p/TroveKilo3Blueprints
 
* [SlickNik] Switch from oslo namespace packages to "oslo_" style modules
 
** https://review.openstack.org/#/c/150709/
 
** For context please see: http://lists.openstack.org/pipermail/openstack-dev/2015-March/059031.html
 
*[peterstac] Come up with a strategy to deal with Mock()ing utility methods
 
** We have several patchsets that are mocking execute_with_timeout, which can cause unexpected behaviour.
 
** For context see: https://review.openstack.org/#/c/156486/ and https://review.openstack.org/#/c/138719/
 
*[sushilkm] Different timeouts in configuration based per datastore
 
**https://review.openstack.org/#/c/164640/
 
 
 
== Trove Meeting, March 25, 2015 ==
 
 
 
* [SlickNik] Trove pulse update:
 
** https://etherpad.openstack.org/p/trove-pulse-update
 
* [vgnbkr] Instance Storage for Replication
 
** https://etherpad.openstack.org/p/trove-replication-storage
 
* [sushilkm] Different timeouts in configuration based per datastore
 
** https://review.openstack.org/#/c/164640/
 
 
 
== Trove Meeting, April 1, 2015 ==
 
 
 
* [SlickNik] Trove pulse update:
 
** https://etherpad.openstack.org/p/trove-pulse-update
 
 
 
 
 
== Trove Meeting, April 8, 2015 ==
 
 
 
* [SlickNik] Trove pulse update:
 
** https://etherpad.openstack.org/p/trove-pulse-update
 
* [vgnbkr] Exceptions in Unit Tests
 
** Propose that when unit tests test for generic errors such as RuntimeError, we check with assertRaisesWithRegexp to check the actual error message rather than just the type.  Propose this for all changes going forward, but not fixing existing tests at this time.
 
* [SlickNik] Liberty Design Summit sessions
 
** https://wiki.openstack.org/wiki/Design_Summit/Planning
 
** https://etherpad.openstack.org/p/trove-liberty-proposed-sessions
 
 
 
== Trove Meeting, April 15, 2015 CANCELED ==
 
 
 
== Trove Meeting, April 22, 2015 ==
 
 
 
* [SlickNik] Trove pulse update:
 
** https://etherpad.openstack.org/p/trove-pulse-update
 
* [SlickNik] Liberty Design Summit sessions
 
** https://wiki.openstack.org/wiki/Design_Summit/Planning
 
** https://etherpad.openstack.org/p/trove-liberty-proposed-sessions
 
* [pmalik] Implement dangling mock detector for unittests (and recommended mocking guidelines - see the below spec for more details)
 
** https://review.openstack.org/#/c/176158/
 
 
 
== Trove Meeting, April 29, 2015 CANCELED ==
 
 
 
== Trove Meeting, May 6, 2015 ==
 
 
 
* [SlickNik] Trove pulse update:
 
** https://etherpad.openstack.org/p/trove-pulse-update
 
* [schang]
 
** We need to discuss this patchset, vote for an implementation option, and move forward: https://review.openstack.org/#/c/164640/9
 
** '''Option 1:''' Define a default usage_timeout setting at the global level, the setting is optional at the datastore level, used only for the purpose of overriding the global default value.
 
** '''Option 2:''' Define a mandatory usage_timeout option for each datastore.
 
** These two options are mutually exclusive, meaning if we've already defined the option at the global level, and if the datastore is OK with the default value, it shouldn't be mandatory to re-specify the same default value at the datastore level.
 
** The current patchset is implementing BOTH option 1 and 2.
 
 
 
== Trove Meeting, May 27, 2015 ==
 
 
 
* [SlickNik] Trove pulse update:
 
** https://etherpad.openstack.org/p/trove-pulse-update
 
* [amrith] Do we need all these new hacking rules?
 
** Changes have been proposed for inclusion of the following hacking rules [copied from commit message without validation]. E128, E265, E713, H238, E111, E122, E123, E128, E251, E265, E713, H105, H306, H404. (four changes, 3 in trove, one in trove-client)
 
** When some hacking rule changes were proposed the last time (https://review.openstack.org/#/c/104616/ for example) the discussion at the Trove meeting was two-fold. First, that we didn't want to add all of these new hacking rules as they had limited upside. The second was that we'd consider reviewing them as a group before accepting changes. I'd like the group to consider all of these changes before we all spend time reviewing them. I would also like to have the ones for trove consolidated into one change to reduce the merge issues.
 
** Personally, I find many of these hacking rules to have minimal benefit (if any). But I would rather we discuss them as a group before we all spend cycles reviewing them and then deciding (correctly) not to incorporate them as we have done in the past.
 
* [amrith] Setting trove meeting agenda through git?
 
** I saw this email on the ML this morning [http://openstack.markmail.org/thread/3upba5r2ma7w3zd7]
 
** Does this change anything for us?
 
* [peterstac] Switching blueprint ownership/details
 
** There's an existing blueprint for Redis backup/restore https://blueprints.launchpad.net/trove/+spec/redis-backup-restore
 
** A new spec was created for it https://review.openstack.org/#/c/182910/
 
** The blueprint wasn't changed to point to the new spec (mainly because I couldn't edit it :{ )
 
** Now a review has appeared for an implementation of Redis backup/restore https://review.openstack.org/#/c/185892/
 
** Question: What is (should be?) our policy on taking over work that has a bp, but hasn't been started/completed?
 
* [vkmc] Trove production deploy. Security concerns and how are we going to tackle those.
 
** During the design sessions we talked about the security concern wrt RabbitMQ and the Trove instances living in public tenants.
 
There are several solutions proposed. Do we have a preference among those?
 
* [vkmc] Trove multitenancy.
 
** Has this came up in the past? What is the Trove community stand on that? Is it in our future plans?
 
 
 
== Trove Meeting, June 3, 2015 ==
 
 
 
* [SlickNik] Trove pulse update:
 
** https://etherpad.openstack.org/p/trove-pulse-update
 
* [amrith] Next steps on protected instance review.
 
** https://review.openstack.org/#/c/186357/
 
** http://paste.openstack.org/raw/260020/
 
 
 
== Trove Meeting, June 10, 2015 ==
 
 
 
* [SlickNik] Trove pulse update:
 
** https://etherpad.openstack.org/p/trove-pulse-update
 
* [SlickNik] Open Horizon Reviews.
 
** https://etherpad.openstack.org/p/trove-reviews-in-horizon
 
 
 
== Trove Meeting, July 01, 2015 ==
 
 
 
* [SlickNik] Trove pulse update:
 
** https://etherpad.openstack.org/p/trove-pulse-update
 
* [Slicknik] Liberty Mid-cycle sprint:
 
** https://wiki.openstack.org/wiki/Sprints/TroveLibertySprint
 
* [vkmc] Lightweight monitoring framework
 
** https://review.openstack.org/#/c/186040/
 
** https://etherpad.openstack.org/p/trove-monitoring
 
* [vkmc] Trove-compatible images creation automation
 
* [vkmc] MariaDB guestagent implementation
 
 
 
== Trove Meeting, July 08, 2015 ==
 
 
 
* [SlickNik] Trove pulse update:
 
** https://etherpad.openstack.org/p/trove-pulse-update
 
* [amrith] https://review.openstack.org/#/c/189837/
 
** To get to the bottom of the new/existing security hole.
 
* [amrith] Trove-compatible images creation automation
 
** This was touched upon last week and some discussion ensued. I don't think a conclusion was reached so I'd like to see if we could reach some finality on this. Specifically, who's doing what? What is the proposed 'feature' or 'implementation', could we have a BP for this, or use the review process to discuss this, which we've found to be effective with BP's (when we moved away from the BP meeting), etc.,
 
 
 
== Trove Meeting, July 15, 2015 ==
 
* [SlickNik] Trove pulse update:
 
** https://etherpad.openstack.org/p/trove-pulse-update
 
 
 
== Trove Meeting, July 22, 2015 ==
 
 
 
* [SlickNik] Trove pulse update:
 
** https://etherpad.openstack.org/p/trove-pulse-update
 
* [atomic77] mysql manager refactor WIP: https://review.openstack.org/#/c/204279/
 
** Currently in-development features will be impacted by the refactor of the mysql manager. Would like to do a checkpoint to give anyone potentially impacted by these changes the opportunity to raise concerns so that we can reduce merging difficulties later on.
 
 
 
== Trove Meeting, July 29, 2015 ==
 
* SlickNik out on vacation July 29, 30, 31. cp16net will chair the meeting.
 
* Trove pulse update:
 
** https://etherpad.openstack.org/p/trove-pulse-update
 
* [cp16net] Public voting for Tokyo Summit presentations is live through July 30 at 11:59pm PT.
 
** [https://www.openstack.org/summit/tokyo-2015/vote-for-speakers/presentation/4747 How much cluster can you muster?]
 
** [https://www.openstack.org/summit/tokyo-2015/vote-for-speakers/presentation/4248 An introduction to "Database-as-a-Service" and OpenStack Trove]
 
** [https://www.openstack.org/summit/tokyo-2015/vote-for-speakers/presentation/4332 Managing multiple database technologies with Trove]
 
** [https://www.openstack.org/summit/tokyo-2015/vote-for-speakers/presentation/4337 To use DBaaS with Trove or to build your own, that is the question!]
 
** [https://www.openstack.org/summit/tokyo-2015/vote-for-speakers/presentation/4357 DBaaS: #1 value added service for every Cloud Service Provider]
 
** [https://www.openstack.org/summit/tokyo-2015/vote-for-speakers/presentation/4511 Trove on Containers – Live and without a net!]
 
** [https://www.openstack.org/summit/tokyo-2015/vote-for-speakers/presentation/4640 Operating Trove in Production]
 
** [https://www.openstack.org/summit/tokyo-2015/vote-for-speakers/presentation/4641 OpenStack Trove -- Hands on the OpenStack Database Service]
 
** [https://www.openstack.org/summit/tokyo-2015/vote-for-speakers/presentation/4643 OpenStack Trove -- Building Databases on OpenStack]
 
** [https://www.openstack.org/summit/tokyo-2015/vote-for-speakers/presentation/4750 Happy, Happy, Trove Trove.]
 
** [https://www.openstack.org/summit/tokyo-2015/vote-for-speakers/presentation/4806 The cloud-enabled DBA of the 21st century]
 
** [https://www.openstack.org/summit/tokyo-2015/vote-for-speakers/presentation/4888 Multi-AZ HA of Trove DB Instances with DRBD]
 
** [https://www.openstack.org/summit/tokyo-2015/vote-for-speakers/presentation/5232 Table for Two: Trove and a Guest]
 
* [cp16net] Datastore registration spec open questions
 
** We talked a little about this in the channel but want to bring this around to close on it.
 
** Questions we need answered to move on this spec.
 
*** Should the api be simple CRUD operations on each object? (i.e. CRUD on datastores and versions separate) or make the API simplified where we really only care about the version when we update the image on an existing version or create a new version?
 
[cp16net] thoughts here on datastore registration spec
 
# the api should be modeled around the objects so that it makes sense in a restful way
 
# if we need a way to make things even easier like this helper that does multiple calls from a single command this might call for a new api call
 
# calling multiple api call from a single cmd gets the job done but seems wrong
 
[SlickNik] I'm personally leaning towards having a unified API (create of datastore and datastore-version in a single call). Some of my thoughts on the matter:
 
# This aims for simplifying our API, not simplifying our python-client experience -- simplifying our APIs would implicitly lead to a simpler client experience across all clients -- not just the python-troveclient.
 
# Having a one-to-one mapping between our REST resources and our data-access CRUD objects is not a necessity. It might even be undesirable in this case since it pushes a lot of the logic to the clients and introduces a tighter coupling between the logic on the client and the data access objects on the server.
 
# I've gotten feedback from multiple folks saying that there is currently not much purpose to defining a datastore separate from a datastore version. The experience would be much better if you're just able to define this in a single call.
 
# Having a unified API (datastore, datastore-version in a single call) does not prevent us from, in the future, adding new datastore CRUD calls if we feel like it is an absolute necessity that we must extend properties / metadata at a datastore level.
 
 
 
== Trove Meeting, Aug 5, 2015 ==
 
* Trove pulse update:
 
** https://etherpad.openstack.org/p/trove-pulse-update
 
 
 
* [sushilkm] Datastore registration spec open questions, https://review.openstack.org/188072
 
** We talked a little about this in last week but want to bring this around to close on it.
 
** Question which need to be answered to move on this spec.
 
*** Should the api be simple CRUD operations on each object? (i.e. CRUD on datastores and versions separate) or make the API simplified where we really only care about the version when we update the image on an existing version or create a new version?
 
** Thoughts from SlickNik and cp16net were there on last weeks agenda too, https://wiki.openstack.org/wiki/Trove/MeetingAgendaHistory#Trove_Meeting.2C_July_29.2C_2015,
 
 
 
== Trove Meeting, Aug 19, 2015 ==
 
* Trove pulse update:
 
** https://etherpad.openstack.org/p/trove-pulse-update
 
* Trove Liberty-3 BP priorities
 
** https://etherpad.openstack.org/p/TroveLibertyPriorities
 
 
 
== Trove Meeting, Sept 2, 2015 ==
 
* Trove pulse update:
 
** https://etherpad.openstack.org/p/trove-pulse-update
 
* Trove Liberty-3 BP priorities
 
** https://etherpad.openstack.org/p/TroveLibertyPriorities
 
 
 
== Trove Meeting, Sept 9, 2015 ==
 
* Trove pulse update:
 
** https://etherpad.openstack.org/p/trove-pulse-update
 
* Trove L release state
 
** The gate ...
 
** https://launchpad.net/trove/+milestone/liberty-rc1
 
* Open Discussion
 
 
 
== Trove Meeting, Sept 23, 2015 ==
 
* Trove pulse update:
 
** https://etherpad.openstack.org/p/trove-pulse-update
 
* Liberty RC1 release this week
 
** https://launchpad.net/trove/+milestone/liberty-rc1
 
* Mitaka Summit Design Sessions
 
** https://etherpad.openstack.org/p/mitaka-trove-summit
 
* Open Discussion
 
 
 
== Trove Meeting, Sept 30, 2015 ==
 
* Trove pulse update:
 
** https://etherpad.openstack.org/p/trove-pulse-update
 
* Action items
 
** cp16net look into troveclient tempest gate failures
 
** peterstac put together a graph for week over week
 
* Bugs that could be back ported for Liberty
 
** [trove] Fix promote for Redis datastore
 
*** https://review.openstack.org/#/c/226075/
 
** [trove] Fix publish_exists_event authentication exception
 
*** https://review.openstack.org/#/c/228696/
 
** [troveclient] Accepting network and availability zone for instances in cluster
 
*** https://review.openstack.org/#/c/184349/
 
* Mitaka Summit Design Sessions
 
** https://etherpad.openstack.org/p/mitaka-trove-summit
 
* Assert follows standard deprication
 
** http://governance.openstack.org/reference/tags/assert_follows-standard-deprecation.html
 
* Open Discussion
 
 
 
== Trove Meeting, Oct 7, 2015 ==
 
* Trove pulse update:
 
** https://etherpad.openstack.org/p/trove-pulse-update
 
 
 
* Trove community and containers [mlowery]
 
** Is there any plan to adopt containers (e.g. Docker) in any way in Trove within the community?
 
*** Example: Put the guest agent in a container. Upgrade it by replacing the container. (You no longer have to care about the current state of the guest (the existing bits)--just replace it.) The same approach could be taken with the datastore itself: put it in a container.
 
** Is there any plan to adopt container orchestration (e.g. Kubernetes) in any way in Trove within the community?
 
*** Example: Kubernetes handles scheduling, updating, and scaling (including auto-healing). Some of these are Nova/Heat-like. Some of these (like auto-healing) don't exist. Is auto-healing in Trove's charter? Could Kubernetes or Magnum be a pluggable "orchestration driver" within Trove?
 
 
 
* Refactor of Manager class [peterstac]
 
** We have previously discussed the merits of refactoring the Manager class structure (and there are many good reasons why we should), however the consensus has been that it would need to be done at the beginning of a cycle.  We're now at the beginning of a (Mitaka) cycle :).  As such, I'd like to draw some attention to the spec and make sure that the proposed solution has no glaring issues.
 
*** Blueprint: https://blueprints.launchpad.net/trove/+spec/datastore-manager-refactor
 
*** Spec: https://review.openstack.org/#/c/231572
 
** The refactor also addresses the issue of the instance state changing erroneously.  I have tested the proposed solution internally and it does fix the issue.
 
*** See https://bugs.launchpad.net/trove/+bug/1482795
 
*** See https://bugs.launchpad.net/trove/+bug/1487233
 
 
 
* Is it time to merge https://review.openstack.org/#/c/220288/1 [amrith]
 
** This change was made during the end of the last cycle to kick up the timeout for some jobs that were failing
 
** Is it time to merge this change (revert the earlier one) and work on the timeout issue properly?
 
 
 
== Trove Meeting, Oct 14, 2015 ==
 
* Trove pulse update
 
** https://etherpad.openstack.org/p/trove-pulse-update
 
** [cp16net working on graphs] link to come
 
* [cp16net] Mitaka Summit Sessions
 
** https://etherpad.openstack.org/p/mitaka-trove-summit
 
* [cp16net] Mitaka Mid-Cycle proposed dates (Feb 9-11 2016)
 
** [make wiki page info on mid-cycle]
 
* gate issues with tox tests
 
 
 
== Trove Meeting, Oct 21, 2015 ==
 
* Trove pulse update
 
** https://etherpad.openstack.org/p/trove-pulse-update
 
* [cp16net] Mitaka Summit Sessions
 
** https://etherpad.openstack.org/p/mitaka-trove-summit
 
** https://wiki.openstack.org/wiki/Design_Summit/Mitaka/Etherpads#Trove
 
** Volunteers to lead sessions
 
* No meeting next week since we will be in Tokyo (Oct 28th)
 
 
 
== Trove Meeting, Oct 28, 2015 ==
 
Skipped due to Summit
 
 
 
== Trove Meeting, Nov 4, 2015 ==
 
* Trove pulse update
 
** https://etherpad.openstack.org/p/trove-pulse-update
 
* Gate Jobs failing
 
** master branch has a segmentation fault
 
** stable branch is failing as well
 
* Summit update
 
 
 
== Trove Meeting, Nov 11, 2015 ==
 
* [cp16net] Trove pulse update
 
** https://etherpad.openstack.org/p/trove-pulse-update
 
** http://bit.ly/1VQyg00
 
* [cp16net] Mitaka 1 - Dec 1-3 (3 weeks away)
 
** https://wiki.openstack.org/wiki/Mitaka_Release_Schedule
 
* [cp16net] Lets get the stable/liberty patches reviewed
 
* [cp16net] Reno support
 
* [cp16net] datastore log operations blueprint
 
** https://review.openstack.org/#/c/188168/
 
 
 
== Trove Meeting, Nov 18, 2015 ==
 
* [cp16net] Trove pulse update
 
** https://etherpad.openstack.org/p/trove-pulse-update
 
** http://bit.ly/1VQyg00
 
* [ashleighfarnham] Adding trove to the openstack client
 
** https://wiki.openstack.org/wiki/Trove/OpenstackClient
 
* [amrith] Catch-22 with reviews
 
** https://review.openstack.org/#/c/245738/
 
** https://review.openstack.org/#/c/245845/
 
 
 
== Trove Meeting, Dec 2, 2015 ==
 
* [cp16net] Trove pulse update
 
** https://etherpad.openstack.org/p/trove-pulse-update
 
** http://bit.ly/1VQyg00
 
* Action Items
 
* M1 Branch Cut
 
** Reno patches required
 
* Specs approvals
 
 
 
== Trove Meeting, Dec 9, 2015 ==
 
* [cp16net] Trove pulse update
 
** https://etherpad.openstack.org/p/trove-pulse-update
 
** http://bit.ly/1VQyg00
 
* Action Items
 
* Experimental datastores
 
* Specs approvals
 
 
 
== Trove Meeting, Dec 16, 2015 ==
 
* [cp16net] Trove pulse update
 
** http://bit.ly/1VQyg00
 
* Specs approvals
 
* Announcements
 
* Open Discussion
 
 
 
== Trove Meeting, Dec 23, 2015 CANCELLED ==
 
Cancelled due to Holidays
 
 
 
== Trove Meeting, Dec 30, 2015 CANCELLED ==
 
Cancelled due to Holidays
 
 
 
= Trove Weekly Meeting Agenda History (2014) =
 
 
 
== Agenda for Mar. 19 ==
 
* https://blueprints.launchpad.net/trove/+spec/refactoring-datastore-options-in-cfg
 
* Moving away from mockito (https://blueprints.launchpad.net/trove/+spec/remove-mockito)
 
* Clustering API Container vs Joins approach.
 
 
 
== Agenda for Mar. 26 ==
 
* Summit sessions [hub_cap]* Data Store abstraction start/stop/status/control [amrith]
 
** https://blueprints.launchpad.net/trove/+spec/trove-guest-agent-datastore-control
 
* Icehouse, RC1, and juno
 
 
 
== Agenda for Apr. 2 ==
 
*Icehouse RC1 cut and Juno branch open
 
*ATL Dev Summit topics
 
*Open discussion
 
 
 
== Agenda for Apr. 9 ==
 
* Refactoring backup/restore strategies [denis_makogon]
 
** https://bugs.launchpad.net/trove/+bug/1287684
 
* Moving the docs [grapex]
 
* Design Summit Session Proposals
 
 
 
== Agenda for Apr. 16  ==
 
* Discuss the expectations of an agenda item for the weekly meeting [core/amcrn]
 
** Goal: Explain what is expected of an agenda item to guarantee the conversation stays on topic and is headed toward meeting a goal or resolving an issue.
 
** [[User:Amcrn|amcrn]] ([[User talk:Amcrn|talk]]) 07:13, 17 April 2014 (UTC):
 
*** Result: majority vote agrees that each agenda item should have an objective and be goal-oriented.
 
*** Solution: as a result, guidelines for agenda items have been added to the top of this wiki and the core team has agreed to shepherd folks for the next few weeks on how to fine tune their agenda items.
 
*** Next Steps: enforce guidelines/rules.
 
* Datastore and Datastore Version Concat in Trove Horizon Dashboard [michael-yu]
 
** Question to Answer: Should there be two columns in list-view, and two dropdowns in launch-view, for datastore and datastore-version respectively? Or should they be concatenated into one?
 
** See the ongoing conversation at https://review.openstack.org/#/c/75269/14/openstack_dashboard/dashboards/project/databases/tables.py and https://review.openstack.org/#/c/75269/14/openstack_dashboard/dashboards/project/databases/workflows/create_instance.py .
 
** [[User:Amcrn|amcrn]] ([[User talk:Amcrn|talk]]) 07:13, 17 April 2014 (UTC):
 
*** Result: majority vote agrees that datastore-type and datastore-version should be consolidated into one dropdown for the launch-instance workflow and one column for list-view. long-term, many believe this to be a hint/indication that datastore-type and datastore-version should be combined into a single field for the v2 api, but this is yet to be seen.
 
*** Next Steps: michael-yu updating his horizon patch-set (https://review.openstack.org/#/c/75269/) to be single dropdown/column and amcrn updating trove-integration to default to a naming scheme that plays well with this model (https://review.openstack.org/#/c/88119/)
 
* Perform integration testing for the heat based instances [Shivamshukla]
 
** https://blueprints.launchpad.net/openstack/?searchtext=test-heat-based-instance-workflow
 
** What could be the way to test instance workflow through heat.
 
** [[User:Amcrn|amcrn]] ([[User talk:Amcrn|talk]]) 07:39, 17 April 2014 (UTC)
 
*** Summary: some tests for a heat-based workflow (https://review.openstack.org/#/c/66499/) require changing trove-taskmanager conf values, which then require a restart of the trove-taskmanager. the problem with requiring a restart is that it makes the naive assumption that it's not a remote system.
 
*** Solution: add a test.conf flag that indicates whether non-remote tests should be run (i.e. tests that require the restart of trove-taskmanager). long-term, a majority agree that a separate heat gate should be birthed.
 
*** Next Steps: shivamshukla to update the patch-set to include the test.conf flag mentioned above.
 
* Neutron Support, SecGroup Management, and Networking [annashen, denis_makogon]
 
** https://blueprints.launchpad.net/trove/+spec/neutron-support + https://blueprints.launchpad.net/trove/+spec/secgroup-mgmt-via-neutron + https://blueprints.launchpad.net/trove/+spec/network-manager-spec
 
** [[User:Amcrn|amcrn]] ([[User talk:Amcrn|talk]]) 07:57, 17 April 2014 (UTC):
 
*** Result: annashen will unilaterally/single-handedly own the blueprint + implementation for supporting neutron in trove. the three related blueprints (https://blueprints.launchpad.net/trove/+spec/neutron-support + https://blueprints.launchpad.net/trove/+spec/secgroup-mgmt-via-neutron + https://blueprints.launchpad.net/trove/+spec/network-manager-spec) are to be merged into one (the final destination being https://blueprints.launchpad.net/trove/+spec/neutron-support). a majority agrees that this consolidated blueprint needs to clearly articulate the requirements, beyond just stating "support running neutron instead of nova-network".
 
*** Next Steps: annashen to deliver unified blueprint and implementation.
 
* Refactoring backup/restore strategies (re-visiting from previous meeting) [denis_makogon]
 
** https://launchpad.net/bugs/1287684
 
** [[User:Amcrn|amcrn]] ([[User talk:Amcrn|talk]]) 07:57, 17 April 2014 (UTC)
 
*** Result: Ran out of time, was not discussed in the meeting.
 
 
 
== Agenda for Apr. 23  ==
 
* Juno Mid-cycle Meetup - discuss venue/timing proposal and confirm
 
 
 
== Agenda for Apr. 30  ==
 
* Establish policy for disk image builder elements for datastores [mat-lowery]
 
** Do we require elements for both Ubuntu and Fedora when a Gerrit change introduces a new datastore or version?
 
*** Cassandra and Couchbase are examples of datastores that don't currently have Fedora elements. https://review.openstack.org/77461 and https://review.openstack.org/79413 are examples of Gerrit changes that have been -1ed because of lack of Fedora elements.
 
*** Isn't one working element better than none? If both are required, is that inviting lower quality on the other element the user is required to code but never uses?
 
*** Are Fedora elements tested in an automated way as the Ubuntu elements are? Reasoning: Yes they were submitted with the Gerrit change, but do they work?
 
*** Is the policy that Trove requires both Fedora and Ubuntu support for each manager on day one? There is already a lack of parity across datastore managers--not all can do backup and restore (but ultimately I assume they will). Why can't Trove take distro support piecemeal just like it does the datastore operations?
 
*** [[User:Mat-lowery|mat-lowery]] ([[User talk:Mat-lowery|talk]]) Wed Apr 30 19:17:28 UTC 2014
 
**** Result: <SlickNik> Let's table this for now.
 
** What about Package Install vs. Tarball Install vs. Source Install? Is there a requirement on how the bits are laid down?
 
*** If packages are required, what are the acceptable sources? (Example: Redis currently uses a PPA.)
 
*** Does the decision here have repercussions on datastore upgrades?
 
*** [[User:Mat-lowery|mat-lowery]] ([[User talk:Mat-lowery|talk]]) Wed Apr 30 19:17:28 UTC 2014
 
**** Result: <SlickNik> So allow [PPAs]. But let's make a best effort to follow this order: distro package, project maintainer PPA, some random PPA.
 
* Open Items
 
** Clarification on commit message style guidelines (slicknik): We've been having a lot of -1 reviews on commit message style and I wanted to clarify some of this so that we can reduce review churn caused by this. Goal: Have a clear understanding on when a commit message should be -1'ed. 
 
 
 
== Agenda for May 7  ==
 
 
 
* How do Gerrit changes get approved? [mat-lowery]
 
** Goal: To clarify the Gerrit change approval process used by Trove core (for the benefit of core and non-core).
 
*** Core potentially benefits by establishing a process that all core follows (and possibly swap best practices).
 
**** What if all core used a prioritized queue such as [http://status.openstack.org/reviews/ ReviewDay]? If you're not using a prioritized queue, how do you prevent starvation?
 
*** Non-core potentially benefits by making the process transparent and setting expectations.
 
**** "Hey core, please review <change>" is '''inefficient and unfair'''. The priority (such as that calculated by ReviewDay) should be the sole indicator of review/approval priority.
 
** Goal: To reduce the time from submittal to approval and prevent Gerrit change starvation.
 
*** My first-ever Trove [https://review.openstack.org/#/c/68015/ submittal] is nearly three months old. Why is that?
 
*** Establish Gerrit "etiquette."
 
**** No leaving -1s and then disappearing. A reviewer that leaves a -1 has an obligation to respond to follow up questions.
 
**** No leaving -1s for nice-to-haves. That's what 0 is for.
 
**** No leaving -1s for questions about why something was done. Again, use a 0.
 
**** No leaving -1s for something minor when there are five +1s.
 
**** Leaving a -1 has the potential to cause the author to "reset the counter" (because he has to submit a new revision) on age-influenced priorities (such as ReviewDay). Think hard before you leave that -1.
 
** More details on the [http://openstack-dev.markmail.org/search/?q=transparent#query:transparent+page:1+mid:76drvzxqepe7547y+state:results mailing list].
 
* Meetings cancelled next week since most folks will be at the ATL summit [slicknik]
 
 
 
== May 14 meeting canceled ==
 
 
 
== Agenda for May 21 ==
 
* Informational PSA on Openstack Logging Standards (cp16net)
 
** https://wiki.openstack.org/wiki/LoggingStandards
 
* Follow up on ATL discussion on Code Reviews
 
** https://etherpad.openstack.org/p/trove-review-juno
 
* Clustering python-troveclient Interface
 
** Reference to Clustering API: https://wiki.openstack.org/wiki/Trove/Replication-And-Clustering-With-Nodes-5#Create_Cluster_2
 
** Question: How to model heterogeneous instances for a cluster in a single python-troveclient command?
 
** See mockups at https://gist.github.com/amcrn/c4ae2210e9d9864c21fd
 
 
 
== Agenda for May 28 ==
 
* Refactor/Re-write notifications [denis_makogon]
 
** https://blueprints.launchpad.net/trove/+spec/ceilometer-integration
 
** We need to discuss the current contract/payload for all notifications since there are [http://osdir.com/ml/openstack-dev/2014-05/msg01619.html a lot of concerns of current design and implementation]
 
 
 
== Agenda for Jun 4 ==
 
* Juno-1 release to be cut next week (SlickNik)
 
** https://bugs.launchpad.net/trove/+milestone/juno-1
 
** https://bugs.launchpad.net/python-troveclient/+milestone/juno-1
 
** https://bugs.launchpad.net/trove-integration/+milestone/juno-1
 
 
 
== Agenda for Jun 11 ==
 
* Code reviews summary + state of the gate
 
** We've been doing a better job with code reviews, but we still need more reviews (both from non-core and core!). 
 
** Code Review summary for the last 30 days:
 
*** Total reviews: 542 (18.1 per day)
 
*** Total reviewers: 33 (0.5 per reviewer per day)
 
*** Total reviews by core team: 282 (9.4 per day)
 
*** Core team size: 6 (1.6 per core per day)
 
** RDJenkins gate is currently broken because image built doesn't use correct cloud-init data source
 
*** https://gist.github.com/anonymous/1cbeadc132736670c41c
 
*** steve-leon and slicknik investigating; likely due to https://review.openstack.org/#/c/95598/
 
* FYI We cut the Juno-1 trove release! (SlickNik)
 
** https://bugs.launchpad.net/trove/+milestone/juno-1
 
** https://github.com/openstack/trove/releases/tag/2014.2.b1
 
 
 
== Agenda for Jun 25 ==
 
* Integration-tests update (SlickNik)
 
* "Vertica Datastore patch review" why no reviews ? (SnowDust)
 
 
 
== Agenda for July 2 ==
 
* https://blueprints.launchpad.net/trove/+spec/per-datastore-volume-support ( Iccha, Rueben)
 
 
 
== Agenda for July 9 ==
 
* Scrub / Update Docs (SlickNik): The following need to be scrubbed. I'd like to get a few volunteers to take a look at each one of these, identify areas where they are deficient, and help fix them. Areas to update are tracked at https://etherpad.openstack.org/p/trove-doc-items.
 
** Developer Docs
 
** Deployment Guide
 
** API Doc
 
** Config Options help strings
 
** Manual Trove Install Doc
 
 
 
== Agenda for July 16 ==
 
* Propose and discuss initial Clustering UI options (michael-yu).
 
** https://wiki.openstack.org/wiki/Trove-Clustering-UI
 
* Doc Scrub Update :
 
** https://etherpad.openstack.org/p/trove-doc-items.
 
* Juno-2 next week :
 
** https://wiki.openstack.org/wiki/Juno_Release_Schedule
 
 
 
== Agenda for July 23 ==
 
* Juno-2 cut:
 
** https://launchpad.net/trove/+milestone/juno-2
 
* Doc Scrub Update :
 
** https://etherpad.openstack.org/p/trove-doc-items.
 
* Other matters:
 
** [amrith] adam_g raised the issue on IRC re: https://review.openstack.org/#/c/102301/  and the bug https://launchpad.net/bugs/1333852. I believe this can be fixed without breaking the API contract by extending the API to include a new parameter. If this proposal is acceptable, I'll volunteer to resubmit the patch set.
 
 
 
== Agenda for Aug 06 ==
 
* Juno Midcycle meetup proposed agenda
 
** https://wiki.openstack.org/wiki/Trove/JunoMidCycleMeetup
 
* Trove related talks for the Kilo Summit
 
** https://wiki.openstack.org/wiki/Trove/KiloSummitTalks
 
 
 
== Agenda for Aug 13 ==
 
* Juno Midcycle meetup proposed agenda
 
** https://wiki.openstack.org/wiki/Trove/JunoMidCycleMeetup
 
* Heads up: Clustering implementation has landed in Gerrit:
 
** API (https://review.openstack.org/#/c/113675/)
 
** TM (https://review.openstack.org/#/c/113692/)
 
** GA (https://review.openstack.org/#/c/113728/)
 
** CLI (https://review.openstack.org/#/c/113710/)
 
** UI (https://review.openstack.org/#/c/110411/)
 
 
 
== Agenda for Aug 27 ==
 
* Juno-3 cut next week
 
** https://launchpad.net/trove/+milestone/juno-3
 
** https://etherpad.openstack.org/p/trove-juno3-reviews
 
*Clusters
 
** See https://wiki.openstack.org/wiki/Trove/Clusters-MongoDB for a quick walkthrough of the operations and some notes.
 
 
 
== Agenda for Sep 3 ==
 
* Juno-3 cut this week
 
** https://launchpad.net/trove/+milestone/juno-3
 
** http://status.openstack.org/zuul/
 
 
 
== Agenda for Sep 10 ==
 
* Clusters Migration and Downgrades (''schang'')
 
** The new v32 clusters migration script creates a foreign key constraint between the clusters table and the database_versions table, but it's downgrade script do not cleanup the table and the foreign key constraint, causing the v16 downgrade to fail on dropping the database_versions table.
 
** To ensure error free downgrades moving forward, we have these options:
 
*** All migration scripts' downgrade needs to cleanup tables and foreign key constraints:
 
****Nobody currently do downgrade migrations on a production system. Shouldn't downgrade's purpose be allowing devs to perform hard resets on their test databases? If test data preservation is needed,  the dev should manually backup and restore the table.
 
**** Establish version points at which downgrade is not permitted. e.g. Downgrade v32 -> v25 is allowed, but you can't downgrade from latest to anything pre v25.
 
***Only test the upgrade path in the test script.
 
***Remove all downgrade routines and don't support downgrade migrations at all.
 
** Action Item: Discuss the above options and decide on an approach.
 
** Review: https://review.openstack.org/#/c/117291/
 
** Error log: http://logs.openstack.org/91/117291/3/check/gate-trove-python27/6074fb4/console.html.gz
 
** Related IRC discussions: http://eavesdrop.openstack.org/irclogs/%23openstack-trove/%23openstack-trove.2014-08-27.log
 
 
 
== Agenda for Sep 17 ==
 
* trove-specs is underway for Kilo (''slicknik'')
 
** https://wiki.openstack.org/wiki/Blueprints#Spec_.2B_Blueprints_lifecycle
 
** All blueprints going forward (for Kilo) must include a spec proposed to the trove-specs repo.
 
** Will give folks a lead time of a week -- so if you're submitting a bp on or after Sept 22, please make sure you a spec linked to it.
 
 
 
== Agenda for Sep 24 ==
 
* Juno RC1
 
** https://bugs.launchpad.net/trove/+milestone/juno-rc1
 
* Design Summit details
 
** http://ttx.re/kilo-design-summit.html
 
 
 
== Agenda for Oct 8 ==
 
* Discuss if change to rdservers related logic in load_mgmt_instance is acceptable as part of bugfix
 
** https://bugs.launchpad.net/trove/+bug/1376525
 
* FOSS Outreach Program Projects
 
** http://gnome.org/opw/
 
 
 
== Agenda for Oct 15th ==
 
* Discuss the timing of trove-guestagent refactoring. This is a big change and it would help to reduce rebasing if this was fast tracked or put on hold until other patches land. (rmyers)
 
** https://review.openstack.org/#/c/119425/
 
 
 
== Agenda for Oct 29th ==
 
* [denis_makogon]
 
** https://review.openstack.org/#/c/102838/ - During bug discussion (using report comments) was made unformal decision to mark all running backups as FAILED if instance is being deleted. But this checkin was marked with -2 from Auston (for more info see checkin comments). I'd like to discuss it and find suitable way for all of us.
 
** https://review.openstack.org/#/c/130519/ - As we are all know that incremental backup can silently be executed as full backup because there's no incremental strategy for given backup strategy. This fix aims to fix it. But Amrith keep voting with -1 because he thinks that fix can be shorter. More info you can find out checkin comments. My idea is to have common validation method that executes specific logic depending on operation type. So, i'd like to hear concrete feedback from other contributors and find suitable way to fix it.
 
** https://gist.github.com/denismakogon/15561df6dc5ddc60ba74 - We need to find proper way to handle cluster extension procedure using CLI. Also, as it was discussed, once clustering is merged we might proceed with changing existing python-troveclient framework (for more information see GIST).
 
 
 
* [amrith]
 
** Since the meeting next monday (BP meeting) will likely be preempted by the summit in Paris, I'd like to get some focus on a blueprint to allow users to retrieve guest log files. Please review https://review.openstack.org/#/c/131610/. I have re-written this specification and (with her permission) listed Iccha as the mentor of the person who will be implementing this.
 
 
 
== Agenda for Nov 19th ==
 
* Looking for reviews to oslo-incubator changes
 
** 129292, Obsolete oslo-incubator modules - unused modules
 
** 129294, Obsolete oslo-incubator modules - timeutils
 
** 129714, Obsolete oslo-incubator modules - gettextutils (now oslo.i18n)
 
** 129664, Obsolete oslo-incubator modules - network_utils (now netutils)
 
** 129654, Obsolete oslo-incubator modules - excutils
 
** 129295, Obsolete oslo-incubator modules - lockutils
 
** 129663, Obsolete oslo-incubator modules - strutils
 
** 129378, Obsolete oslo-incubator modules - importutils
 
** 129668, Obsolete oslo-incubator modules - jsonutils (now oslo.serialization)
 
** 133068, Obsolete oslo-incubator modules - wsgi
 
** 133051, Obsolete oslo-incubator modules - exception
 
* Better documentation for Image building
 
** Goal: This was identified as an area of confusion in the summit. Identify what the next steps here are and establish a timeline for fixing this.
 
* Trove Mid Cycle Sprint in Seattle, WA
 
** http://doodle.com/veabvxtc84czm9ep
 
** Goal: Close on a date for the mid-cycle sprint so that other logistics can follow
 
* Trove Cross Project Liasons
 
** https://wiki.openstack.org/wiki/CrossProjectLiaisons
 
** Goal: Identify volunteers for Cross Project Liasons
 
 
 
== Agenda for Nov 26th ==
 
* Dates for Trove Kilo Mid-Cycle sprint
 
* Trove BP meeting -- to bp or not to bp?
 
 
 
== Agenda for Dec 3rd ==
 
* [amrith] Discuss merge order for various OSLO related patches
 
* [amrith] Discuss status of moving guest agent to its own repository patch set
 
 
 
= Trove Blueprint Meeting Agenda History (2014) =
 
 
 
For those interested, we have blueprint meetings in #openstack-trove weekly, Mondays at 18:00 UTC. Feel free to add items in the agenda below.
 
 
 
== Agenda for Mar. 31 ==
 
Networking related blueprints:
 
* Network attribute management [denis_makogon]
 
** https://blueprints.launchpad.net/trove/+spec/network-manager-spec
 
* Neutron Support for Trove [annashen]
 
** https://blueprints.launchpad.net/trove/+spec/neutron-support
 
* Trove Managed Instances on Private Network [juice]
 
** https://blueprints.launchpad.net/trove/+spec/trove-guest-private-network
 
Others:
 
*Point in time recovery [denis_makogon]
 
** https://blueprints.launchpad.net/trove/+spec/point-in-time-recovery
 
*Data volume snapshot [denis_makogon]
 
** https://blueprints.launchpad.net/trove/+spec/volume-snapshot
 
*Instance metadata [imsplitbit]
 
** https://blueprints.launchpad.net/trove/+spec/trove-metadata
 
 
 
== Agenda for Apr. 7 ==
 
*Point in time recovery [denis_makogon]
 
** https://blueprints.launchpad.net/trove/+spec/point-in-time-recovery
 
*Data volume snapshot [denis_makogon]
 
** https://blueprints.launchpad.net/trove/+spec/volume-snapshot
 
*Networking [denis_makogon]
 
** https://blueprints.launchpad.net/trove/+spec/network-manager-spec
 
*Cross-region backups [esmute]
 
** https://blueprints.launchpad.net/trove/+spec/cross-region-backup-availability
 
*Descriptions to Datastore Configuration Group Parameters [cp16net]
 
** https://blueprints.launchpad.net/trove/+spec/add-descriptions-to-config-parameters-api
 
*Categorize the trove-manage commands [cp16net]
 
** https://blueprints.launchpad.net/trove/+spec/categorize-the-trove-manage-commands
 
*Neutron Network Support [annashen]
 
**https://blueprints.launchpad.net/trove/+spec/neutron-support
 
*Trove-Managed Instances [juice]
 
**https://blueprints.launchpad.net/trove/+spec/trove-managed-instances
 
 
 
== Agenda for Apr. 14 ==
 
* Datastore Capabilities [k-pom]
 
** https://blueprints.launchpad.net/trove/+spec/capabilities
 
*Descriptions to Datastore Configuration Group Parameters [cp16net]
 
** https://blueprints.launchpad.net/trove/+spec/add-descriptions-to-config-parameters-api
 
*Categorize the trove-manage commands [cp16net]
 
** https://blueprints.launchpad.net/trove/+spec/categorize-the-trove-manage-commands
 
*Point in time recovery [denis_makogon]
 
** https://blueprints.launchpad.net/trove/+spec/point-in-time-recovery
 
*Data volume snapshot [denis_makogon]
 
** https://blueprints.launchpad.net/trove/+spec/volume-snapshot
 
*Networking [denis_makogon]
 
** https://blueprints.launchpad.net/trove/+spec/network-manager-spec
 
*Neutron [annashen]
 
** https://wiki.openstack.org/wiki/Trove/neutron-support
 
* Move the Trove Guest Agent to its own module [robertmyers]
 
** https://blueprints.launchpad.net/trove/+spec/moving-trove-guestagent
 
* Unify common code in guest agent configurations [amrith and snowdust]
 
** https://blueprints.launchpad.net/trove/+spec/trove-unify-common-code-for-config-of-guest-agent-variants
 
* Adding datastore and version to the backup API [robertmyers]
 
** https://blueprints.launchpad.net/trove/+spec/backup-metadata
 
 
 
== Agenda for Apr. 21 ==
 
* Unify common code in guest agent configurations [amrith and snowdust]
 
** https://blueprints.launchpad.net/trove/+spec/trove-unify-common-code-for-config-of-guest-agent-variants
 
* Adding datastore and version to the backup API [robertmyers]
 
** https://blueprints.launchpad.net/trove/+spec/backup-metadata
 
* Move the Trove Guest Agent to its own module [robertmyers]
 
** https://blueprints.launchpad.net/trove/+spec/moving-trove-guestagent
 
* Database log files manipulations [denis_makogon]
 
** https://blueprints.launchpad.net/trove/+spec/dbinstance-log
 
* Resource management driver [denis_makogon]
 
** https://blueprints.launchpad.net/trove/+spec/resource-management-driver
 
* Add backup and restore support for single instance couchbase [michael-yu]
 
** https://blueprints.launchpad.net/trove/+spec/backups-single-instance-couchbase
 
** https://wiki.openstack.org/wiki/Trove/backup-restore-single-instance-couchbase
 
* Populate endpoint URLs from Keystone service catalog [esmute]
 
** https://blueprints.launchpad.net/trove/+spec/populate-endpoints-from-keystone-catalog
 
* Enable specification of Cinder Volume Types
 
** https://blueprints.launchpad.net/trove/+spec/cinder-volume-type
 
* Add ability to create read-only users via the users API
 
** https://blueprints.launchpad.net/trove/+spec/read-only-user
 
 
 
== Agenda for April 28 ==
 
* Percona support [mattgriffin]:
 
** https://blueprints.launchpad.net/trove/+spec/support-percona-xtrabackup-2.2
 
** https://blueprints.launchpad.net/trove/+spec/support-ps-5.6
 
** https://blueprints.launchpad.net/trove/+spec/support-pxc-5.5-and-5.6
 
* Support for Vertica [yogeshmehra]:
 
** https://blueprints.launchpad.net/trove/+spec/vertica-db-support
 
* Resource management driver [denis_makogon]
 
** https://blueprints.launchpad.net/trove/+spec/resource-manager-interface
 
* Managed Instances [juice]
 
** https://blueprints.launchpad.net/trove/+spec/trove-managed-instances
 
*List all datastore types and versions by a single API call [nehav]
 
** https://blueprints.launchpad.net/trove/+spec/list-datastore-type-and-versions
 
 
 
== Agenda for May 5 ==
 
* Percona support [mattgriffin]:
 
** https://blueprints.launchpad.net/trove/+spec/support-percona-xtrabackup-2.2
 
** [[User:Slicknik|slicknik]] ([[User talk:Slicknik|talk]]) We can look into this (streaming to Swift NA yet, but there are some new features)
 
** https://blueprints.launchpad.net/trove/+spec/support-ps-5.6
 
** [[User:Slicknik|slicknik]] ([[User talk:Slicknik|talk]]) This will be supported through our mysql datastore manager
 
** https://blueprints.launchpad.net/trove/+spec/support-pxc-5.5-and-5.6
 
** [[User:Slicknik|slicknik]] ([[User talk:Slicknik|talk]]) We do not support clustering yet, but we will look into this once v1 support for clustering arrives.
 
* Instance database log manipulations [denis_makogon]
 
** https://blueprints.launchpad.net/trove/+spec/dbinstance-log
 
** [[User:Slicknik|slicknik]] ([[User talk:Slicknik|talk]]) dmakagon to fix the wiki page conf section with exact API
 
* Update database instance name [nehav]
 
** https://blueprints.launchpad.net/trove/+spec/update-instance-name
 
** [[User:Slicknik|slicknik]] ([[User talk:Slicknik|talk]]) Approved to updated name (only in trove and not in nova)
 
* Allow configs to be rendered based on datastore version [cp16net]
 
** https://blueprints.launchpad.net/trove/+spec/datastore-configs-cant-use-multiple-versions
 
** [[User:Slicknik|slicknik]] ([[User talk:Slicknik|talk]]) Approved
 
 
 
== Meeting Cancelled May 12 ==
 
== Agenda for May 19 ==
 
* Trove client for cross-region-backup [esmute]
 
** https://blueprints.launchpad.net/trove/+spec/cross-region-backup-availability
 
** [[User:Amcrn|amcrn]] ([[User talk:Amcrn|talk]]) 18:24, 19 May 2014 (UTC): Meeting Minutes: this was originally scheduled due to concerns with introducing a new field called "region". at the time, there was no consensus as to whether namespacing should be used (arn-style), etc. during the summit, we reached a consensus (in the clustering talks) that a "region" field is the way to go, and therefore there's no action items here.
 
*  Add visibility filter to datastores [iccha]
 
** https://blueprints.launchpad.net/trove/+spec/datastore-visibility
 
** [[User:Amcrn|amcrn]] ([[User talk:Amcrn|talk]]) 18:24, 19 May 2014 (UTC): Meeting Minutes: consensus is that if is_active is 0, then only if the tenant-id is in a whitelist (new table?) will they be able to use and see the datastore-version. this is more aligned with how glance deals with images vs. what's proposed in the orginal spec here (a simple admin-only).
 
* Database log files manipulations [denis_makogon]
 
** https://blueprints.launchpad.net/trove/+spec/dbinstance-log
 
** [[User:Amcrn|amcrn]] ([[User talk:Amcrn|talk]]) 18:54, 19 May 2014 (UTC): Meeting Minutes: the following modifications are required for approval (1) adding posix created/modified timestamp fields on the response so that a user knows when the log was last touched and/or rotated (2) use configuration-groups for configuration parameters (vs. introducing the mapping in the code) (3) fix a few bugs in the blueprint, including inconsistent usage of underscore vs. hyphen in naming, and datastore_log_files should be an array.
 
<br>
 
[[User:Amcrn|amcrn]] ([[User talk:Amcrn|talk]]) 19:04, 19 May 2014 (UTC): the items below by boden are being tabled at the moment (pending confirmation of sponsorship and a discussion surrounding the precedent this sets). amrith to send an email to boden to sync up.
 
 
 
* Pluggable conductor manager [boden]
 
** https://blueprints.launchpad.net/trove/+spec/pluggable-conductor-manager
 
* Configurable DB plugins [boden]
 
** https://blueprints.launchpad.net/trove/+spec/configurable-db-plugins
 
* Multi-path plugin support; added notes to existing BP [boden]
 
** https://blueprints.launchpad.net/trove/+spec/extensions-update
 
 
 
== Agenda for Jun 2 ==
 
* Trove should use Keystone Trusts for Authentication instead of hard coding the credentials in configuration files.
 
** Please refer to this blueprint https://blueprints.launchpad.net/trove/+spec/trove-keystone-trusts
 
** Changes are similar to Keystone trusts blueprint in Tuskar https://blueprints.launchpad.net/tuskar/+spec/tuskar-keystone-trusts
 
** Using keystone trusts will eliminate the risk of keeping login credentials in a configuration file.
 
** Can be seen as Security Enchantment by better practice.
 
[[User:Slicknik|slicknik]] ([[User talk:Slicknik|talk]]) 21:22, 2 June 2014 (UTC) There were concerns around whether keystone trusts is fully done yet, and what other OpenStack projects are going to use this. We had a vote, and the unanimous result was to wait and watch for now.
 
* Flavor per datastore association [iccha]
 
**https://blueprints.launchpad.net/trove/+spec/associate-flavors-datastores
 
[[User:Slicknik|slicknik]] ([[User talk:Slicknik|talk]]) 21:22, 2 June 2014 (UTC) Approved. There was one small concern about backward-compat with the GET /flavors api call which should be addressed. 
 
* Conductor phase 2 [denis_makogon]
 
** https://blueprints.launchpad.net/trove/+spec/conductor-phase-2
 
[[User:Slicknik|slicknik]] ([[User talk:Slicknik|talk]]) 21:22, 2 June 2014 (UTC) Needs more detail as to what phase 2 will actually entail. Denis to update the bp with more details.
 
* Add created/updated timestamps and instance count to configuration groups list and details calls [tvoran and iccha]
 
** https://blueprints.launchpad.net/trove/+spec/minor-config-edits
 
[[User:Slicknik|slicknik]] ([[User talk:Slicknik|talk]]) 21:22, 2 June 2014 (UTC) Approved
 
* Pluggable conductor manager [boden]
 
** https://blueprints.launchpad.net/trove/+spec/pluggable-conductor-manager
 
[[User:Slicknik|slicknik]] ([[User talk:Slicknik|talk]]) 21:22, 2 June 2014 (UTC) Approved
 
* Configurable DB plugins [boden]
 
** https://blueprints.launchpad.net/trove/+spec/configurable-db-plugins
 
[[User:Slicknik|slicknik]] ([[User talk:Slicknik|talk]]) 21:22, 2 June 2014 (UTC) Needs more information regarding. Boden to update the BP.
 
* Multiple API extension paths [boden]
 
** https://blueprints.launchpad.net/trove/+spec/extensions-update
 
[[User:Slicknik|slicknik]] ([[User talk:Slicknik|talk]]) 21:22, 2 June 2014 (UTC) Ran out of time and didn't get to this. Tabled for a later meeting.
 
 
 
== Agenda for Jun 23 ==
 
* Heat integration [denis_makogon]
 
** https://blueprints.launchpad.net/trove/+spec/full-heat-integration
 
*** Brought up at http://eavesdrop.openstack.org/meetings/trove_bp_review/2014/trove_bp_review.2014-06-16-18.00.log.html
 
*** Also brought up on the mailing list at http://lists.openstack.org/pipermail/openstack-dev/2014-June/037836.html
 
* Configurable DB plugins [boden]
 
** https://blueprints.launchpad.net/trove/+spec/configurable-db-plugins
 
 
 
== Agenda for Jul 14 ==
 
* New API call to get the default configuration values for a specific datastore version flavor without an instance (cp16net)
 
** https://blueprints.launchpad.net/trove/+spec/default-config-values-for-datastore-version-flavor
 
* configurable db plugins -https://blueprints.launchpad.net/trove/+spec/configurable-db-plugins [boden]
 
** Based on our previous discussion I propose we drop this BP as (a) no other projects expose this level of integration and (b) this couples consumers into an internal impl detail which is not guaranteed to be supported long term.
 
*  multiple API extension paths https://blueprints.launchpad.net/trove/+spec/extensions-update [boden]
 
** See email note here (bullet c) : http://lists.openstack.org/pipermail/openstack-dev/2014-April/033904.html
 
<br />
 
 
 
== Agenda for Jul 21 ==
 
* [denis_makogon]
 
** Datastore log files operations [denis_makogon]
 
*** https://blueprints.launchpad.net/trove/+spec/dbinstance-log
 
* [boblebauce]
 
** Use oslo-rootwrap
 
*** https://blueprints.launchpad.net/trove/+spec/rootwrap-for-guest
 
* [denis_makogon]
 
** Disk space validation coefficient
 
*** https://blueprints.launchpad.net/trove/+spec/restore-disk-space-coefficient
 
** Ceilometer integration. Notifications (revisiting after fleshing out).
 
*** https://blueprints.launchpad.net/trove/+spec/ceilometer-integration
 
<br />
 
 
 
== Agenda for Jul 28 ==
 
* [boden]
 
** Dynamic extension loading using stevedore
 
*** https://blueprints.launchpad.net/trove/+spec/dynamic-extension-loading
 
 
 
== Aug 18 Meeting Canceled ==
 
* Most trove folks traveling for Trove Day + Midcycle event in Cambridge, MA
 
 
 
== Agenda for Aug 25 ==
 
* [amrith]
 
** What do we do about SUSE? There are bugs coming in at a steady clip fixing little things that don't work in SUSE but in some cases, no test cases are being proposed nor is there a clear plan to get SUSE on the supported platform list. How do we want to proceed? I raise this question because I don't want to use the review process as the place to discuss on a patch-by-patch basis whether a certain code change should be considered or not; rather raise it and address it as a larger issue of how we get to a supported SUSE platform including testing on an ongoing basis, etc.,
 
 
 
== Sep 1 Meeting Canceled ==
 
* Labor Day, so most folks are out
 
 
 
== Agenda for Sep 8 ==
 
* [iartarisi] - SUSE support
 
** I created a blueprint to track the SUSE support in trove. We could discuss this and see what else is needed and how to proceed. https://blueprints.launchpad.net/trove/+spec/suse-support (also see the full specification link)
 
* [kevinconway] - SSL support
 
** https://wiki.openstack.org/wiki/Trove/TroveSSL
 
* [denis_makogon]
 
** ceilometer integration
 
*** https://blueprints.launchpad.net/trove/+spec/ceilometer-integration
 
 
 
== Agenda for Sep 15 ==
 
* [zhiyan] - OSProfiler integration
 
** https://review.openstack.org/#/c/103825/
 
* [denis_makogon]
 
** Cassandra clustering
 
*** https://blueprints.launchpad.net/trove/+spec/cassandra-cluster
 
** Clustering int-tests
 
*** https://blueprints.launchpad.net/trove/+spec/clustering-int-tests
 
 
 
== Agenda for Sep 22 ==
 
* [denis_makogon]
 
** Cassandra clustering
 
*** https://blueprints.launchpad.net/trove/+spec/cassandra-cluster
 
** Oracle 12c support over Fedora 20
 
*** https://blueprints.launchpad.net/trove/+spec/oracle-db-over-fedora-20
 
* [zhiyan] - OSProfiler integration
 
** https://review.openstack.org/#/c/103825/
 
 
 
== Agenda for Oct 20 ==
 
* [amrith] Handle oslo-incubator module graduation. Please note that this encompasses two blueprints one for oslo.concurrency which I had filed earlier and a second one for other modules that have already graduated. Four commits have been provided as an example of some of the kinds of changes being contemplated. Changes (similar) are ready for all of the other modules (except rpc which is being handled independently). Please review the following:
 
** https://review.openstack.org/#/c/123571/
 
** https://etherpad.openstack.org/p/trove-kilo-do-not-use-obsolete-oslo-modules
 
** https://review.openstack.org/#/c/129292/
 
** https://review.openstack.org/#/c/129294/
 
** https://review.openstack.org/#/c/129295/
 
** https://review.openstack.org/#/c/129378/
 
 
 
 
 
== Agenda for Oct 22nd  ==
 
* [SlickNik] Discuss trove design summit sessions in the etherpad
 
** https://etherpad.openstack.org/p/kilo-trove-summit-topics
 
* [amcrn] Ask folks to review https://wiki.openstack.org/wiki/Bugs#Importance and (re-)categorize bugs accordingly.
 
* [amrith and AJaeger] AJaeger started working on https://review.openstack.org/#/c/129624/. This same issue was debated in https://review.openstack.org/#/c/104616/ and after some deliberation we eventually didn't take the change. My recollection is that this was discussed at the mid-cycle in Cambridge as part of the conversations that led to https://review.openstack.org/#/c/115778/ and we decided that we wouldn't take H301. Maybe that was a decision for the Juno cycle only; I don't recall. After speaking with AJaeger, I've put this on the agenda for this meeting because I would like to make sure that we're in favor of this change now before he spends much more time on it, and the attendant fixes to H302 and H304 which produce numerous failures.
 
* [robertmyers and schang] Discuss guestagent refactoring progress.
 
** https://review.openstack.org/#/c/119425/ passed and ready for review, but gate seems to be broken.
 
** Prepare for other guestagent merges. Discuss status of other in-flight commits.
 
 
 
== Agenda for Oct 27 ==
 
* https://review.openstack.org/#/c/129734/ (Add RAM, Cores, and Volume Count to Quotas)
 
* https://review.openstack.org/#/c/129740/ (Make Rsync Optional For Guest)
 
* https://review.openstack.org/#/c/129752/ (Enance Mgmt-Show To Support Deleted Instances)
 
* https://review.openstack.org/#/c/130392/ (Guest Agent RPC Ping Pong Mgmt API)
 
 
 
== Agenda for Nov 3 ==
 
* Allow users to retrieve guest log files
 
** https://review.openstack.org/#/c/131610/
 
 
 
== Agenda for Nov 5 ==
 
Meeting canceled
 
 
 
== Agenda for Nov 12 ==
 
Meeting canceled
 
 
 
== Agenda for Nov 17 ==
 
* Add support for DB2 Express-C datastore (https://review.openstack.org/#/c/133856/) - Mariam John
 
* Add support for Apache CouchDB datastore (https://review.openstack.org/#/c/133849/) - Mariam John
 
[grapex]
 
* Example Snippet Generator - Tim Simpson
 
[Riddhi]
 
* Flavors per datastore - https://blueprints.launchpad.net/trove/+spec/associate-flavors-datastores
 
* sgotliv (Sergey Gotliv) and peterstac (Peter Stachowski) wanted to discuss the relevant API changes.
 
 
 
== Agenda for Nov. 24 ==
 
* [flaper87, sgotliv, amrith] Switch Trove to use OSLO Messaging [https://review.openstack.org/#/c/136352/]
 
** Since a spec in trove-specs is required for all projects related to blueprints that are intended for merge in Kilo, this spec has been submitted for review based on a document that was already in the old wiki format. A procedural approval similar to the ones granted to other specs [flavor id's and datastore versions] is requested for this.
 
* [iccha, amrith] Allow users to retrieve guest log files [https://review.openstack.org/#/c/131610/]
 
* [dougshelley66] Add instance name as parameter to various CLI commands [https://review.openstack.org/#/c/136424/]
 

Latest revision as of 16:07, 12 October 2016

Historical meeting agendas are of limited value and meeting logs are available at [1]