Jump to: navigation, search

Difference between revisions of "Trove/MeetingAgendaHistory"

Line 55: Line 55:
 
== Agenda for Apr. 23  ==
 
== Agenda for Apr. 23  ==
 
* Juno Mid-cycle Meetup - discuss venue/timing proposal and confirm
 
* 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. 
 +
 +
<br />
 +
Meeting Chat Logs: http://eavesdrop.openstack.org/meetings/trove/2014/
 +
<br />
 +
Meeting Agenda History: https://wiki.openstack.org/wiki/Trove/MeetingAgendaHistory#Trove_Weekly_Meeting_Agenda_History
 +
<br /><br />
 +
<big>Note: BP Meetings now have their own wiki page at: https://wiki.openstack.org/wiki/Meetings/TroveBPMeeting</big>
 +
  
 
= Trove Blueprint Meeting Agenda History =
 
= Trove Blueprint Meeting Agenda History =
Line 136: Line 161:
 
* Add ability to create read-only users via the users API
 
* Add ability to create read-only users via the users API
 
** https://blueprints.launchpad.net/trove/+spec/read-only-user
 
** 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
 +
<br />

Revision as of 10:01, 1 May 2014

Trove Weekly Meeting Agenda History

Agenda for Mar. 19

Agenda for Mar. 26

Agenda for Apr. 2

  • Icehouse RC1 cut and Juno branch open
  • ATL Dev Summit topics
  • Open discussion

Agenda for Apr. 9

Agenda for Apr. 16

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?
      • 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?
      • 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.


Meeting Chat Logs: http://eavesdrop.openstack.org/meetings/trove/2014/
Meeting Agenda History: https://wiki.openstack.org/wiki/Trove/MeetingAgendaHistory#Trove_Weekly_Meeting_Agenda_History

Note: BP Meetings now have their own wiki page at: https://wiki.openstack.org/wiki/Meetings/TroveBPMeeting


Trove Blueprint Meeting Agenda History

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:

Others:

Agenda for Apr. 7

Agenda for Apr. 14

Agenda for Apr. 21

Agenda for April 28


Retrieved from "https://wiki.openstack.org/w/index.php?title=Trove/MeetingAgendaHistory&oldid=50764"